Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make VerificationRequest more robust against double events #12567

Closed
bwindels opened this issue Feb 28, 2020 · 1 comment
Closed

Make VerificationRequest more robust against double events #12567

bwindels opened this issue Feb 28, 2020 · 1 comment

Comments

@bwindels
Copy link
Contributor

bwindels commented Feb 28, 2020 •
edited
Loading

for robustness sake, only allow 1 event of each type for each participating party to be processed by a verification request.

This is also good mitigation against #12479
@bwindels bwindels changed the title for robustness sake, only allow 1 event of each type for each participating party to be processed by a verification request. Make VerificationRequest more robust against double events Feb 28, 2020
@bwindels
Copy link
Contributor Author

bwindels commented Mar 3, 2020

Not doing this for now, as the double .accept bug was because a different client was sending a second .accept event.

@bwindels bwindels closed this as completed Mar 3, 2020
t3chguy added a commit that referenced this issue Oct 17, 2024
@renovate @t3chguy
Update dependency @sentry/browser to v8 (#12567)
6fedf89 
* Update dependency @sentry/browser to v8

* Migrate

Signed-off-by: Michael Telatynski <[email protected]>

* prettier

Signed-off-by: Michael Telatynski <[email protected]>

---------

Signed-off-by: Michael Telatynski <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Michael Telatynski <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bwindels