procutil: make stream detection in make_line_buffered more correct and strict In make_line_buffered(), we don’t want to wrap the stream if we know that lines get flushed to the underlying raw stream already. Previously, the heuristic was too optimistic. It assumed that any stream which is not an instance of io.BufferedIOBase doesn’t need wrapping. However, there are buffered streams that aren’t instances of io.BufferedIOBase, like Mercurial’s own winstdout. The new logic is different in two ways: First, only for the check, if unwraps any combination of WriteAllWrapper and winstdout. Second, it skips wrapping the stream only if it is an instance of io.RawIOBase (or already wrapped). If it is an instance of io.BufferedIOBase, it gets wrapped. In any other case, the function raises an exception. This ensures that, if an unknown stream is passed or we add another wrapper in the future, we don’t wrap the stream if it’s already line buffered or not wrap the stream if it’s not line buffered. In fact, this was already helpful during development of this change. Without it, I possibly would have forgot that WriteAllWrapper needs to be ignored for the check, leading to unnecessary wrapping if stdout is unbuffered. The alternative would have been to always wrap unknown streams. However, I don’t think that anyone would benefit from being less strict. We can expect streams from the standard library to be subclassing either io.RawIOBase or io.BufferedIOBase, so running Mercurial in the standard way should not regress by this change. Py2exe might replace sys.stdout and sys.stderr, but that currently breaks Mercurial anyway and also these streams don’t claim to be interactive, so this function is not called for them.

     1

Address commentary in manifest.excludedmanifestrevlog.add -

     2

specifically we should improve the collaboration with core so that

     3

add() never gets called on an excluded directory and we can improve

     4

the stand-in to raise a ProgrammingError.

     5

     6

Reason more completely about rename-filtering logic in

     7

narrowfilelog. There could be some surprises lurking there.

     8

     9

Formally document the narrowspec format. For bonus points, unify with the

    10

server-specified narrowspec format.

    11

    12

narrowrepo.setnarrowpats() or narrowspec.save() need to make sure

    13

they're holding the wlock.

    14

    15

The follinwg places do an unrestricted dirstate walk (including files outside the

    16

narrowspec). Some of them should perhaps not do that.

    17

    18

 * debugfileset

    19

 * perfwalk

    20

 * sparse (but restricted to sparse config)

    21

 * largefiles