feat: indie status page MVP -- FastAPI + SQLite
- 8 DB models (services, incidents, monitors, subscribers, etc.) - Full CRUD API for services, incidents, monitors - Public status page with live data - Incident detail page with timeline - API key authentication - Uptime monitoring scheduler - 13 tests passing - TECHNICAL_DESIGN.md with full spec
This commit is contained in:
commit
902133edd3
4655 changed files with 1342691 additions and 0 deletions
27
venv/lib/python3.11/site-packages/pluggy/_warnings.py
Normal file
27
venv/lib/python3.11/site-packages/pluggy/_warnings.py
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
from typing import final
|
||||
|
||||
|
||||
class PluggyWarning(UserWarning):
|
||||
"""Base class for all warnings emitted by pluggy."""
|
||||
|
||||
__module__ = "pluggy"
|
||||
|
||||
|
||||
@final
|
||||
class PluggyTeardownRaisedWarning(PluggyWarning):
|
||||
"""A plugin raised an exception during an :ref:`old-style hookwrapper
|
||||
<old_style_hookwrappers>` teardown.
|
||||
|
||||
Such exceptions are not handled by pluggy, and may cause subsequent
|
||||
teardowns to be executed at unexpected times, or be skipped entirely.
|
||||
|
||||
This is an issue in the plugin implementation.
|
||||
|
||||
If the exception is unintended, fix the underlying cause.
|
||||
|
||||
If the exception is intended, switch to :ref:`new-style hook wrappers
|
||||
<hookwrappers>`, or use :func:`result.force_exception()
|
||||
<pluggy.Result.force_exception>` to set the exception instead of raising.
|
||||
"""
|
||||
|
||||
__module__ = "pluggy"
|
||||
Loading…
Add table
Add a link
Reference in a new issue