Improve Tracebacks for easier debugging

[ibro45]

Let's start using Rich, we can easily add it to Loguru .

The main reason though is to improve tracebacks. We could exclude fire and monai.bundle (I hope that excluding only a module of a framework would work).

Screenshot from here.

[surajpaib]

@ibro45 This sounds perfect. We should do this asap.

[ibro45]

#105 (comment):

To improve:

• Error messages can be very long. Ideally, we would like to shorten them for the same modules whose tracebacks we suppress. [REQUEST] Shortening error messages of certain modules similarly to frame suppression in tracebacks Textualize/rich#3271

• Patching warnings.showwarning cannot take into account the stacklevel argument from warnings.warn(). This is apparent in warnings from PL being shown as coming from the rank_zero module, instead of a level or few before, as they indicate through stacklevel. Capturing warnings with the correct source location Delgan/loguru#1076 (comment)

• Errors coming from DataLoader are off (as if logging isn't set up). I described it here, but I am still unsure how to fix it. [BUG] Inconsistent traceback logging Textualize/rich#3269

• I will create an issue for us to keep track of modules that we think should be suppressed

  lighter/lighter/logging.py

  Line 2 in a63195f

  SUPPRESSED_MODULES = [

---

The 1st and 2nd bullet points still need to be addressed.

The 3rd cannot be fixed.

The 4th should be tracked in this issue, report the modules in replies.