Skip to content

feat: Count special attachment items as error#5919

Draft
jjbayer wants to merge 1 commit intomasterfrom
feat/att-error
Draft

feat: Count special attachment items as error#5919
jjbayer wants to merge 1 commit intomasterfrom
feat/att-error

Conversation

@jjbayer
Copy link
Copy Markdown
Member

@jjbayer jjbayer commented Apr 30, 2026

Experiment for #5918

Comment on lines +128 to +132
if self.creates_event() {
// for minidumps, etc.
quantities.push((DataCategory::Error, 1));
}
quantities
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem with this is, if an envelope has two items which creates_event(), this will be wrong again :(.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But an envelope like that would get rejected anyway, right? My idea was: count an error for the item (a sensible default IMO), then manually fix the cases where this causes a mismatch.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can have a minidump and an error in the same envelope, each item individually counts as an error, but combined in an envelope it's just a single one.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough, I think I made the mistake of editing Item::quantities directly.

What I actually want is that a Managed<Item> containing a minidump reports error: 1, so that this affects only the few cases where we construct an envelope from individual managed items. Let's discuss on Monday.

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.

2 participants