Repository navigation
Develop - #117
Develop#117
Conversation
Task with lots of output would block when their pipe would get full. Drain our side of the pipe from time to time so the task can continue tasking. Ref gitx#97
We might get the termination/completion notification before we actually had a chance to read anything, so we would reallocate `standardOutputData` under the readability handler.
|
Thank you for all the updates! I'm now running this with @mangerlahn's branch merged in (it merged cleanly other than stray xcodeproj and xib conflicts). I'd suggest moving to the latest ObjectiveGit in this branch as well. The current version of ObjectiveGit/libgit2 that gitx is depending on is pretty old and has some problems that results in poor performance on repositories with lots of submodules (libgit2/libgit2#4016). |
|
I'm trying out the Key piece of info appears to be: |
|
PBTask throws an exception when trying to discard changes to a file. It looks like NSPipe doesn't allow calling |
This reverts commit 638e567.
This is a stop-gap measure: calling -reloadRefs from a background queue wrecks the KVO system because we're doing weird things with our notifications when reloading references.
|
Heads-up ! Those two issues should be gone now (first 2 commits above). I've also reworked the error reporting so we get (hopefully) nicer error messages when tasks fail. |
|
Discard changes is working again. Another regression that I found: Commit hooks aren't working. I have a pre-commit and commit-msg hook and no warning appears anymore when they fail. I haven't had a chance to debug it myself yet. |
With HEAD detached, the parseSymbolicReference code would find an OID as an unresolvedTarget, which would result in a nil branchRef, thus a nil _headOID, and a subsequent crash when trying to add this nil OID to a set "somewhere". Simplify all that by just using whatever our underlying HEAD reference says.
|
I'm merging, just because I find it cumbersome to follow too much branches. The issues you (various) reported should all be fixed, so if you find that something is not working, please open an issue (for real this time). |
Sorry for the dull name.
This is the result of a few years worth of
lovelow-level work on GitX innards. I'm now running that branch for the time being (I'll likely find bugs and squash them).The plan is :
Highlights are :
So if developers/users want to give a hand in testing, please give this a spin !
@gitx/core @ksuther @mangerlahn @muhqu