Debug Flags

These flags can be passed on the brz command line or (without the -D prefix) put in the debug_flags variable in breezy.conf.


Trace authentication sections used.


Print out how many bytes were transferred


Trace dirstate activity (verbose!)


Instead of normal error handling, always print a traceback on error.


Capture call sites that do expensive or badly-scaling operations.


Trace history copying between repositories.


Emit information for debugging content filtering.


Force use of inventory deltas during generic streaming fetch.


Trace graph traversal.


Log every time a working file is read to determine its hash.


Trace hook execution.


Trace smart protocol requests and responses.


More hpss details.


Traceback on vfs access to Remote objects.


Trace http connections, requests and responses.


Trace major index operations.


Trace knit operations.


Trace when lockdir locks are taken or released.


If a connection is reset, fail immediately rather than retrying the request.


Trace progress bar operations.


Dump memory to a file upon an out of memory error.


Emit information for debugging merges.


Don’t use apport to report crashes.


Don’t show transport activity indicator in progress bar.


Emit information about pack operations.


Emit a message every time a branch or repository object is unlocked then relocked the same way.


Trace SFTP internals.


Error when a tuple is used where a StaticTuple is expected


Trace fetch streams.


Trace when OS locks are potentially used in a non-portable manner.


Some errors during unlock are treated as warnings.


Never use InterDifferingSerializer when fetching.


Always use InterDifferingSerializer to fetch if appropriate for the format, even for non-local fetches.