Skip to content

fix: explicit typing for LOGGER and restore unified logger usage (#2870)#5724

Open
majd102-p wants to merge 5 commits into
ossf:mainfrom
majd102-p:fix-logger-type-2870
Open

fix: explicit typing for LOGGER and restore unified logger usage (#2870)#5724
majd102-p wants to merge 5 commits into
ossf:mainfrom
majd102-p:fix-logger-type-2870

Conversation

@majd102-p
Copy link
Copy Markdown

This PR addresses the type-checking issues in #2870:

  1. Added explicit logging.Logger type hint to the global LOGGER in log.py to satisfy mypy.
  2. Reverted the workaround in output_engine/html.py to use the shared package LOGGER.
  3. Unified logger usage in test/pages/html_report.py and test/test_output_engine.py for consistency.

This ensures full type safety while following the maintainer's preference for a centralized logging solution.

…#2870)

Signed-off-by: majd102-p <32015333020@std.bau.edu.jo>
@majd102-p majd102-p force-pushed the fix-logger-type-2870 branch from 196406d to acbef20 Compare April 25, 2026 12:20
Signed-off-by: Majd Ayoub <majd.redmi102@gmail.com>
@majd102-p majd102-p force-pushed the fix-logger-type-2870 branch from 826e557 to 3f999d8 Compare May 11, 2026 12:37
@majd102-p
Copy link
Copy Markdown
Author

majd102-p commented May 11, 2026

Updated the PR: I have fixed the isort formatting and ensured all commits are DCO signed-off
Regarding the failure in Python 3.13 (synchronous), it appears to be a network-related issue (Network is unreachable) within the CI environment and is unrelated to my changes. Ready for your review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant