| Age | Commit message (Collapse) | Author |
|---|
|
Change-Id: I8ab3d5affb3f040dd9630687fb20aedbd7510070
|
|
If the timeout is not specified, we don't need the overhead of
creating a watchdog and event.
Change-Id: I53ff891af24d4c27fb16bf4bb35910dd1d19d238
|
|
Change-Id: I2e081c606b75b7f8d3d1ee82d93c3d9f3bdcfcbe
|
|
This feature enables to set a timeout while executing a git
command. After this timeout is over, the process will be killed.
If not explicitly specified, the default functionality will not
be affected.
Change-Id: I2dd5f0de7cb1f5f1b4253dd7ce92d23551d5f9a7
|
|
for the executable.
|
|
This allows us to use the main thread to parse stderr to get progress,
and resolve assertion failures hopefully once and for all.
Relates to #301
|
|
* Previously we could fail to parse the last line within a read buffer,
which is now fixed.
* Added a test to verify our *slow* line parsing works as expected.
|
|
When the code is run without setting up loggers, the loggers have no
handlers for the emitted messages. The logging module displays:
`No handlers could be found for logger "git.cmd"` on the
console. By adding a NullHandler (a no-op) the message disappears,
and doesn't affect logging when other handlers are configured.
|
|
This is a pre-emptive measure based on http://goo.gl/l74GC8 .
Related to #290
|
|
Previously, only program messages where forced to the C-locale, now
we force the entire program. That way, we should assure a remote
will not provide us with branch information in any other language but
english.
Related to #290
|
|
... if it is not found. Previously, especially on windows, this wasn't
explicit.
Fixes #248, affects #126
|
|
While at it, all other invocations of .git in remote.py were reviewed
Fixes #262
|
|
However, I kept information on how to achieve the same thing with
`custom_environment()` in the test.
Related to #234
|
|
Need latest master to proceed with test
Conflicts:
doc/source/tutorial.rst
|
|
Renamed context manager 'with_environment' to 'custom_environment'.
On my way to implement sshkey test.
|
|
|
|
|
|
|
|
|
|
GIT_PYTHON_TRACE would actually fail (now) if we debugged archive operations.
Related to #239
|
|
Now travisci tests should work once again.
Related to #239
|
|
There have been rather obvious errors in there, as we forgot to unregister
the filehandles. Now we will read from a buffer ourselves, which should be
faster and ideally, doesn't lead to spurious errors anymore.
Related to #232
|
|
Fixes #7
[ci skip]
|
|
It does not necessarily seem to work, but at least we don't access a
dict concurrently anymore.
|
|
However, it does so only on posix. The test-case will run on posix only
as well.
Please note that in theory, even on windows we will attempt to run hooks,
even though I am not sure that this will actually work.
Fixes #81
|
|
Fixes #74
|
|
Fixes #48
|
|
At least leakage is considerably reduced.
Additionally, a test-case was added which triggers failure if auto-disposal
of resources wouldn't work.
Fixes #60
|
|
|
|
|
|
|
|
Next up is using threads
|
|
Fixes #140
|
|
See #177
|
|
|
|
|
|
And I have to wonder why git-daemon serves under py2.7, but really
wants receive-pack to be allowed under 3.4. Maybe it's a repository
override which for some reason doesn't work in py3.4 ? Maybe because
the change is not flushed ?
|
|
|
|
Kind of tackling the tasks step by step, picking low-hanging fruit first,
or the ones that everyone depends on
|
|
However, StringIO really is ByteIO in most cases, and py2.7 should
run but doesn't.
This should be made work first.
|
|
More to come, especially when it's about strings
|
|
All performance tests still print to stderr, but do so in a py3 compatible way
|
|
There is more work to do though, as many imports are still incorrect.
Also, there are still print statements
|
|
* GIT_PYTHON_TRACE now behaves correctly for fetch, and pull (i.e. if as_process is used)
* Improved parsing of fetch head information
However, there is still a messy bit that tries to bring together fetch progress information
with fetch head information. Even though it works now, an alternative implementation should
be attempted.
|
|
Commandline was
autopep8 -j 8 --max-line-length 120 --in-place --recursive --exclude "*gitdb*,*async*" git/
|
|
Git utilizes multiple environment variables to control various
behaviours. Make sure to set LC_MESSAGES on a copy of the environment
instead of discarding any variables that may be set by the user or
default shell environment such as EDITOR.
Add test to assert that when overriding GIT_EDITOR via os.environ that
the modified value will be picked up by and git commands called.
|
|
boppreh-patch-1
Adjusted patch to only run git command in shell mode on windows.
Conflicts:
git/cmd.py
|
|
Remove Byte Order Mark from git/cmd.py
|
|
The Unicode Byte Order Mark is usually unwanted. git/cmd.py had one
inserted in 2008 by cf37099e, a commit that fix a Windows related issue
which indicate the file has most probably be edited with a text editor
that automatically insert the Byte Order Mark.
Remove the BOM from git/cmd.py
For details aboute the BOM:
https://en.wikipedia.org/wiki/Byte_order_mark
|
|
W291 trailing whitespace
|
