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.

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

fix: claim duplications #542

Merged
merged 5 commits into from Mar 29, 2024
Merged

fix: claim duplications #542

merged 5 commits into from Mar 29, 2024

Conversation

dni
Copy link
Member

@dni dni commented Mar 28, 2024

closes #509

the effect in TxClaimed was triggering the claim, i think this is not necessary because the sweapchecker handles it. tested it manually and it works.

@michael1011 i think you introduced that any reasoning behind that?

introduction of claim queue so websocket updates do not overlap each other

@dni dni requested review from michael1011 and kilrau March 28, 2024 07:30
Copy link

vercel bot commented Mar 28, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
webapp ✅ Ready (Inspect) Visit Preview Mar 29, 2024 2:53pm
webapp-mainnet ✅ Ready (Inspect) Visit Preview Mar 29, 2024 2:53pm

the effect in TxClaimed was triggering the claim, i think this is not necessary because the sweapchecker handles it. tested it manually and it works.

@michael1011 i think you introduced that any reasoning behind that?

introduction of claim queue so websocket updates do not overlap each other
tests/utils/lock.spec.ts Outdated Show resolved Hide resolved
@michael1011 michael1011 merged commit 00c253c into main Mar 29, 2024
6 checks passed
@michael1011 michael1011 deleted the fix-claiming branch March 29, 2024 14:55
michael1011 added a commit that referenced this pull request Mar 29, 2024
* fix: claim duplications

the effect in TxClaimed was triggering the claim, i think this is not necessary because the sweapchecker handles it. tested it manually and it works.

@michael1011 i think you introduced that any reasoning behind that?

introduction of claim queue so websocket updates do not overlap each other

* refator: queue of WebSocket messages to handle

* fixup!

* fix: handle rejected promises in lock

* chore: fix wording of test

---------

Co-authored-by: michael1011 <me@michael1011.at>
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.

Rebroadcasting claims causes errors
2 participants