delta/libgit2.git/tests/core, branch cmn/http-error github.com: libgit2/libgit2.git errors: tighten up git_error_state OOMs a bit more 2015-08-03T23:44:51+00:00 Edward Thomson ethomson@edwardthomson.com 2015-08-03T21:50:27+00:00 ef4857c2b3d4a61fd1d840199afc92eaf2e15345 When an error state is an OOM, make sure that we treat is specially and do not try to free it. 
When an error state is an OOM, make sure that we treat is specially
and do not try to free it.
Test: check restored oom error points to static buffer 2015-08-03T14:23:17+00:00 Michael Procter michael@procter.org.uk 2015-07-27T09:13:49+00:00 988ea59443b71f4a07b19fff837ccaa1659dbcc0 






Add failing test for capture/restore oom error
2015-08-03T14:23:17+00:00

Michael Procter
michael@procter.org.uk

2015-07-23T12:16:19+00:00

5ef4b86015309c157b20260905cb5d0c9bb47ca8












filebuf: remove lockfile upon rename errors
2015-07-24T21:02:11+00:00

Carlos Martín Nieto
cmn@dwim.me

2015-07-24T17:22:41+00:00

19d9beb7ffbde3e171c17fc3544d508304a30fbf

When we have an error renaming the lockfile, we need to make sure
that we remove it upon cleanup. For this, we need to keep track of
whether we opened the file and whether the rename succeeded.

If we did create the lockfile but the rename did not succeed, we
remove the lockfile. This won't protect against all errors, but
the most common ones (target file is open) does get handled.





When we have an error renaming the lockfile, we need to make sure
that we remove it upon cleanup. For this, we need to keep track of
whether we opened the file and whether the rename succeeded.

If we did create the lockfile but the rename did not succeed, we
remove the lockfile. This won't protect against all errors, but
the most common ones (target file is open) does get handled.







filebuf: failing test for leaving the lockfile when failing to rename
2015-07-24T20:55:43+00:00

Carlos Martín Nieto
cmn@dwim.me

2015-07-24T16:44:29+00:00

668053befecfd0979ff790bc9a2a3c308c38a9be

When we fail to rename, we currently leave the lockfile laying
around. This shows that behaviour.





When we fail to rename, we currently leave the lockfile laying
around. This shows that behaviour.







git__getenv: utf-8 aware env reader
2015-07-02T16:35:43+00:00

Edward Thomson
ethomson@edwardthomson.com

2015-07-02T14:25:48+00:00

e069c621bdd62e603b048eb536f5a978a905b310

Introduce `git__getenv` which is a UTF-8 aware `getenv` everywhere.
Make `cl_getenv` use this to keep consistent memory handling around
return values (free everywhere, as opposed to only some platforms).





Introduce `git__getenv` which is a UTF-8 aware `getenv` everywhere.
Make `cl_getenv` use this to keep consistent memory handling around
return values (free everywhere, as opposed to only some platforms).







buffer: make use of EINVALID for growing a borrowed buffer
2015-06-24T21:49:10+00:00

Carlos Martín Nieto
cmn@dwim.me

2015-06-24T17:32:56+00:00

a65992355dac71490f4b22b3f2c0d55a1beca01b

This explains more closely what happens. While here, set an error
message.





This explains more closely what happens. While here, set an error
message.







buffer: don't allow growing borrowed buffers
2015-06-24T21:49:10+00:00

Carlos Martín Nieto
cmn@dwim.me

2015-06-23T13:41:58+00:00

caab22c0d468e90b6a95072f3092d5dcf331b3ef

When we don't own a buffer (asize=0) we currently allow the usage of
grow to copy the memory into a buffer we do own. This muddles the
meaning of grow, and lets us be a bit cavalier with ownership semantics.

Don't allow this any more. Usage of grow should be restricted to buffers
which we know own their own memory. If unsure, we must not attempt to
modify it.





When we don't own a buffer (asize=0) we currently allow the usage of
grow to copy the memory into a buffer we do own. This muddles the
meaning of grow, and lets us be a bit cavalier with ownership semantics.

Don't allow this any more. Usage of grow should be restricted to buffers
which we know own their own memory. If unsure, we must not attempt to
modify it.







git_buf_text_lf_to_crlf: allow mixed line endings
2015-06-22T16:00:23+00:00

Edward Thomson
ethomson@microsoft.com

2015-06-08T17:51:28+00:00

8293c8f9a3ea18131af98b71fa9100dcba0ad438

Allow files to have mixed line endings instead of skipping processing
on them.





Allow files to have mixed line endings instead of skipping processing
on them.







Merge pull request #3219 from libgit2/cmn/racy-diff
2015-06-17T06:15:49+00:00

Carlos Martín Nieto
cmn@dwim.me

2015-06-17T06:15:49+00:00

a56db99234017eb7814258dfe8bcdec365417a3b

Zero out racily-clean entries' file_size




Zero out racily-clean entries' file_size