Page MenuHomeSoftware Heritage

fuse: use logging.exception() instead of .debug()
ClosedPublic

Authored by haltode on Mon, Nov 16, 1:26 PM.

Details

Summary

During development of new features, enabling the DEBUG log-level every
time to hunt down a runtime exception is unpractical since the DEBUG
level is very verbose and does not include the exception traceback.
Using the logging.exception() method fixes all these issues.

Diff Detail

Repository
rDFUSE FUSE virtual file system
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

haltode created this revision.Mon, Nov 16, 1:26 PM
seirl accepted this revision.Mon, Nov 16, 1:27 PM
This revision is now accepted and ready to land.Mon, Nov 16, 1:27 PM

Build is green

Patch application report for D4478 (id=15890)

Rebasing onto 604665ab40...

Current branch diff-target is up to date.
Changes applied before test
commit 1e09b9b1b2ca30cde4fc60f8d4742e9fb443e21a
Author: Thibault Allançon <haltode@gmail.com>
Date:   Mon Nov 16 13:19:02 2020 +0100

    fuse: use logging.exception() instead of .debug()
    
    During development of new features, enabling the DEBUG log-level every
    time to hunt down a runtime exception is unpractical since the DEBUG
    level is very verbose and does not include the exception traceback.
    Using the logging.exception() method fixes all these issues.

See https://jenkins.softwareheritage.org/job/DFUSE/job/tests-on-diff/152/ for more details.

This revision was automatically updated to reflect the committed changes.