You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
User-facing warnings are hidden by the ERROR-level user logger #284
Found by independent verifiers during #281. #281 fixed the warnings it added (fermi2D and FermiPlotter.plot "No Fermi surface found" now raise a UserWarning); these older sites have the same problem on dev.
The user logger's level is ERROR (utils/log_utils.py:78), so user_logger.warning(...) prints nothing in a default call unless something first calls set_verbose_level.
FermiHandler.plot_fermi_cross_section_box_widget (~line 717) logs "No Fermi surface found" to the user logger.
bandsplot's "fermi is not set" warning.
FermiSlicePlotter's scalar/vector name warnings.
fermi2D ignores its documented verbose argument (never calls set_verbose_level).
Decide one rule (warnings a user must see go through warnings.warn, or the user logger defaults to WARNING) and apply it everywhere.
Fixed in dev by #294. Messages a user must act on now go through warnings.warn (pyprocar.utils.log_utils.warn_user) and name the caller's line in scripts, notebooks and threads. tests/test_user_warnings.py fails on any new user-logger warning or raw warnings.warn in pyprocar/. The verdicts are on #294.
Activity
fix: show user-facing warnings through warnings.warn
test: fail while user-facing warnings go to the hidden user logger
fix: show user-facing warnings through warnings.warn
test: fail while user-facing warnings go to the hidden user logger
fix: show user-facing warnings through warnings.warn
test: fail while user-facing warnings go to the hidden user logger
fix: show user-facing warnings through warnings.warn
test: fail while user-facing warnings go to the hidden user logger
fix: show user-facing warnings through warnings.warn
fix(warnings): show user-facing warnings through warnings.warn (#294)
lllangWV commentedon Oct 4, 2026
Fixed in dev by #294. Messages a user must act on now go through warnings.warn (pyprocar.utils.log_utils.warn_user) and name the caller's line in scripts, notebooks and threads. tests/test_user_warnings.py fails on any new user-logger warning or raw warnings.warn in pyprocar/. The verdicts are on #294.