##// END OF EJS Templates
localrepo: handle ValueError during repository opening...
localrepo: handle ValueError during repository opening Python 3.8 can raise ValueError on attempt of an I/O operation against an illegal path. This was causing test-remotefilelog-gc.t to fail on Python 3.8. This commit teaches repository opening to handle ValueError and re-raise an Abort on failure. An arguably better solution would be to implement this logic in the vfs layer. But that seems like a bag of worms and I don't want to go down that rabbit hole. Until users report uncaught ValueError exceptions in the wild, I think it is fine to patch this at the only occurrence our test harness is finding it. Differential Revision: https://phab.mercurial-scm.org/D7944

File last commit:

r45036:fdc802f2 default
r45469:9e5b4dbe default
Show More
ext-phase-report.py
31 lines | 1.0 KiB | text/x-python | PythonLexer
# tiny extension to report phase changes during transaction
from __future__ import absolute_import
def reposetup(ui, repo):
def reportphasemove(tr):
for revs, move in sorted(tr.changes[b"phases"], key=lambda r: r[0][0]):
for rev in revs:
if move[0] is None:
ui.write(
(
b'test-debug-phase: new rev %d: x -> %d\n'
% (rev, move[1])
)
)
else:
ui.write(
(
b'test-debug-phase: move rev %d: %d -> %d\n'
% (rev, move[0], move[1])
)
)
class reportphaserepo(repo.__class__):
def transaction(self, *args, **kwargs):
tr = super(reportphaserepo, self).transaction(*args, **kwargs)
tr.addpostclose(b'report-phase', reportphasemove)
return tr
repo.__class__ = reportphaserepo