rusackas opened a new pull request, #41304:
URL: https://github.com/apache/superset/pull/41304

   ### SUMMARY
   
   `init_extensions` caught extension-initialization exceptions and emitted 
them via `print(ex)` to stdout, bypassing the configured structured logging 
pipeline (formatting, severity levels, configured destinations). Initialization 
failures were therefore invisible to operators relying on log aggregation.
   
   This routes those failures through `logger.exception(...)`, which records 
the failing extension id and a full traceback at error level through the 
standard logger.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   
   N/A — logging behavior.
   
   ### TESTING INSTRUCTIONS
   
   Unit test added in `tests/unit_tests/test_init_extensions_logging.py`: an 
extension entrypoint that raises during init is logged via `logger.exception`, 
and the failing extension id is included in the log args.
   
   Run: `pytest tests/unit_tests/test_init_extensions_logging.py`
   
   ### ADDITIONAL INFORMATION
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to