Sun, 04 Mar 2018 21:16:36 -0500 sslutil: some more forcebytes() on some exception messages
Augie Fackler <augie@google.com> [Sun, 04 Mar 2018 21:16:36 -0500] rev 36747
sslutil: some more forcebytes() on some exception messages At this point, test-https.t no longer dumps tracebacks everywhere. Instead, we get some results that look like we're not adequately finding things in hg's configuration, which should be manageable (if somewhat annoying to find and fix.) Differential Revision: https://phab.mercurial-scm.org/D2690
Sun, 04 Mar 2018 21:15:37 -0500 sslutil: sslcontext needs the cipher name as a sysstr
Augie Fackler <augie@google.com> [Sun, 04 Mar 2018 21:15:37 -0500] rev 36746
sslutil: sslcontext needs the cipher name as a sysstr Differential Revision: https://phab.mercurial-scm.org/D2689
Sun, 04 Mar 2018 18:03:55 -0500 sslutil: lots of unicode/bytes cleanup
Augie Fackler <augie@google.com> [Sun, 04 Mar 2018 18:03:55 -0500] rev 36745
sslutil: lots of unicode/bytes cleanup In general, we handle hostnames as bytes, except where Python forces them to be unicodes. This fixes all the tracebacks I was seeing in test-https.t, but there's still some ECONNRESET weirdness that I can't hunt down... Differential Revision: https://phab.mercurial-scm.org/D2687
Tue, 13 Feb 2018 11:35:32 -0800 revlog: do not use delta for lfs revisions stable
Jun Wu <quark@fb.com> [Tue, 13 Feb 2018 11:35:32 -0800] rev 36744
revlog: do not use delta for lfs revisions This is similar to what we have done for changegroups. It is needed to make sure the delta application code path can assume deltas are always against vanilla (ex. non-LFS) rawtext so the next fix becomes possible. Differential Revision: https://phab.mercurial-scm.org/D2068
Tue, 06 Feb 2018 19:08:25 -0800 changegroup: do not delta lfs revisions stable
Jun Wu <quark@fb.com> [Tue, 06 Feb 2018 19:08:25 -0800] rev 36743
changegroup: do not delta lfs revisions There is no way to distinguish whether a delta base is LFS or non-LFS. If the delta is against LFS rawtext, and the client trying to apply it has the base revision stored as fulltext, the delta (aka. bundle) will fail to apply. This patch forbids using delta for LFS revisions in changegroup so bad deltas won't be transmitted. Note: this does not solve the problem entirely. It solves LFS delta applying to non-LFS base. But the other direction: non-LFS delta applying to LFS base is not solved yet. Differential Revision: https://phab.mercurial-scm.org/D2067
Tue, 06 Feb 2018 16:08:57 -0800 lfs: add a test showing bundle application could be broken stable
Jun Wu <quark@fb.com> [Tue, 06 Feb 2018 16:08:57 -0800] rev 36742
lfs: add a test showing bundle application could be broken When a bundle containing LFS delta uses non-LFS delta-base, or vice-versa, the bundle will fail to apply. Differential Revision: https://phab.mercurial-scm.org/D2066
Mon, 05 Mar 2018 20:22:34 -0500 debugwireproto: handle unimplemented util.poll() for Windows
Matt Harbison <matt_harbison@yahoo.com> [Mon, 05 Mar 2018 20:22:34 -0500] rev 36741
debugwireproto: handle unimplemented util.poll() for Windows This is the same logic used in sshpeer.doublepipe. It doesn't completely fix test-ssh-proto{,-unbundle}.t ("read(-1) -> X" is changed to "read(X) -> X", the order of some lines are changed, and abort messages seem to be missing), but it cuts down a ton on the failure spew.
Sun, 04 Mar 2018 16:55:51 -0500 py3: byte-stringify test-blackbox.t
Yuya Nishihara <yuya@tcha.org> [Sun, 04 Mar 2018 16:55:51 -0500] rev 36740
py3: byte-stringify test-blackbox.t
Sun, 04 Mar 2018 16:54:14 -0500 py3: byte-stringify blackbox-readonly-dispatch.py
Yuya Nishihara <yuya@tcha.org> [Sun, 04 Mar 2018 16:54:14 -0500] rev 36739
py3: byte-stringify blackbox-readonly-dispatch.py # skip-blame because just adding some b''
Sun, 04 Mar 2018 16:50:35 -0500 py3: make blackbox-readonly-dispatch.py use ui instead of print()
Yuya Nishihara <yuya@tcha.org> [Sun, 04 Mar 2018 16:50:35 -0500] rev 36738
py3: make blackbox-readonly-dispatch.py use ui instead of print()
(0) -30000 -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip