| Age | Commit message (Collapse) | Author |
|---|
|
still inconsistencies that need to be fixed, but it already improved, especially the 4-thread performance which now is as fast as the dual-threaded performance
|
|
for up to 2 threads, but 4 are killing the queue
|
|
least in tests, and with multiple threads. There is still an sync bug in regard to closed channels to be fixed, as the Task.set_done handling is incorrecft
|
|
changing tasks
Now processing more items to test performance, in dual-threaded mode as well, and its rather bad, have to figure out the reason for this, probably gil, but queues could help
|
|
multiple connected pools
Reduced waiting time in tests to make them complete faster
|
|
single task for now, but next up are dependent tasks
|
|
related to our channel closed flag, which is the only way not to block forever on read(0) channels which were closed by a thread 'in the meanwhile'
|
|
chunking test. Next up, actual async processing
|
|
including own tests, their design improved to prepare them for some specifics that would be needed for multiprocessing support
|
|
is handled by the task system
graph: implemented it including test according to the pools requirements
pool: implemented set_pool_size
|
|
while going. Tests will be written soon for verification, its still quite theoretical
|
|
going on. The default implementation uses threads, which ends up being nothing more than async, as they are all locked down by internal and the global interpreter lock
|
|
to do with the object db. If that really works the way I want, it will become an own project, called async
|
|
inter-dependent tasks
|
|
Git-Python. I have the feeling it can do much good here :)
|
|
restructured odb tests, they are now in an own module to keep the modules small
|
|
will always be compressed if generated by the system ( even future memory db's will compress it )
loose db: implemented direct stream copy, indicated by a sha set in the IStream, including test. This will be the case once Packs are exploded for instance
|
|
for streams starts to show up, but its not yet there
|
|
but next there will have to be more through testing
|
|
multi-threading implementation of all odb functions
|
|
|
|
parsing which truncated newlines although it was ilegitimate. Its up to the reader to truncate therse, nowhere in the git code I could find anyone adding newlines to commits where it is written
Added performance tests for serialization, it does about 5k commits per second if writing to tmpfs
|
|
|
|
missing ) and added performance tests which are extremely promising
|
|
efficiently considering that it copies string buffers all the time
|
|
|
|
appears to be working
|
|
objects will be written using our utilities, and certain object retrieval functionality moves into the GitObjectDatabase which is used by the repo instance
Added performance test for object database access, which shows quite respectable tree parsing performance, and okay blob access. Nonetheless, it will be hard to beat the c performance using a pure python implementation, but it can be a nice practice to write it anyway to allow more direct pack manipulations. Some could benefit from the ability to write packs as these can serve as local cache if alternates are used
|
|
bug of course which just didn't kick in yet
|
|
from their object information directly. This is faster, and resolves issues with the rev-list format and empty commit messages
Adjusted many tests to go with the changes, as they were still mocked. The mock was removed if necessary and replaced by code that actually executes
|
|
tests to work on larger repositories
|
|
|
|
performance is slightly better
git.cmd: added method to provide access to the content stream directly. This is more efficient if large objects are handled, if it is actually used
test.helpers: removed unnecessary code
|
|
objects if it could serialize itself
|
|
convenience)
|
|
newline at the end of the split line was not split away automatically. Added test for this, and the trivial fix
Wow, at least two people reviewd the code, but it slipped through anyway :)
|
|
Cmd: AutoInterrupt handles boundary cases more gracefully as it can be that the os module suddenly becomes None if the interpreter is going down
|
|
|
|
different path in the index than the actual one on disk ( from which the object will be created )
Fixed bug the way newlines were handled, which hopefully fixes occasional hangs as well. It works fine with git 1.7.1
Most of the changes are due to the tab-space conversion - its weird once more as I thought it was all in spaces before ... .
|
|
repo.is_dirty: Will not fail on empty repo ( anymore )
index.entries: will just be empty if the repository is empty
refs: added to_full_path method which can be used to create fully synthetic instances of Reference types, added a test for it
Converted all touched files to spaces, which is why git reports so many changed files. Actually I was thinking every file would use spaces, but apparently not
|
|
Fixed test which required to be on master to work - it now uses the HEAD symbolic ref instead.
|
|
This commit includes
- an update to git.objects.utils:parse_actor_and_date to parse the timezone offset
- updates to the git.objects.Commit and git.objects.Tag objects to support *_tz_offset attributes
- updates to tests in test.git.test_commit and test.git.test_refs to check for appropriate *_tz_offset attributes
|
|
mistaken for disabled tests, although they are actually called by the test cases as utility functions
|
|
|
|
to paths anymore as it will only append '--' if paths are actually given.
Added unittest to verify this
|
|
test.helpers: temporary rw repository creators now set the working dir of the program, easing working with relative paths a lot
|
|
regarding its parents
|
|
Repo.init: fixed incorrect use of the path which was to optionally specify where to initialize the repository. Update test as well
|
|
available at some point natively, within the git suite
Progress parsing now deals properly with Ascii_Escape characters that are meant for the tty - git might stop sending this at some point, but we can deal with it no matter what
|
|
allowing the keys to contain slashes; adjusted test to check for this
|
