Skip to content
This repository was archived by the owner on Dec 1, 2025. It is now read-only.

Small updates to aggregate error reporting explainer#178

Open
alexmturner wants to merge 4 commits into
mainfrom
pending-report-limit
Open

Small updates to aggregate error reporting explainer#178
alexmturner wants to merge 4 commits into
mainfrom
pending-report-limit

Conversation

@alexmturner
Copy link
Copy Markdown
Collaborator

@alexmturner alexmturner commented Mar 7, 2025

Adjusts pending report limit error handling: previously, the description
implied that the pending report limit error would only be triggered when
there is no space for the report. To avoid such reports always being
dropped (or needing to add special case exemptions), we modify the
trigger to occur when the limit is just reached.

Adjusts insufficient budget condition to handle the situation where some
(but not all) of a report's contributions are dropped due to
insufficient budget. This could not occur before this feature.

Explains the two-phase processing: to avoid complexity and
self-referential loops, we process reports in two phases, meaning that
errors are only triggered based on unconditional contributions.

@alexmturner alexmturner force-pushed the pending-report-limit branch from d35de63 to e9c1e39 Compare March 11, 2025 19:50
@alexmturner alexmturner changed the title Adjust pending report limit error handling Small updates to aggregate error reporting explainer Mar 11, 2025
Comment thread error_reporting.md Outdated
Adjusts pending report limit error handling: previously, the description
implied that the pending report limit error would only be triggered when
there is no space for the report. To avoid such reports always being
dropped (or needing to add special case exemptions), we modify the
trigger to occur when the limit is just reached.

Adjusts insufficient budget condition to handle the situation where some
(but not all) of a report's contributions are dropped due to
insufficient budget. This could not occur before this feature.

Explains the two-phase processing: to avoid complexity and
self-referential loops, we process reports in two phases, meaning that
errors are only triggered based on unconditional contributions.
@alexmturner alexmturner force-pushed the pending-report-limit branch from ac51492 to d8c60a3 Compare April 11, 2025 18:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants