-
Notifications
You must be signed in to change notification settings - Fork 20
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
Support proxy.killPure #439
Conversation
I deployed a v2 of the squid, but some network fail for some obscure reasons (hence the tests failing too). It's testable locally, but not on the preview yet. I'll update when this is fixed, I'm in contact with the Subsquid team. |
ok it should be good now |
Looks good. I compared prod and this branch with the accounts that you provided (thanks!) . I was able to see the fix working :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks great! Thank you a lot!
closes #284
This shouldn't be a dangerous change, it's fixing a bug that very few ppl may have encountered.
I've tested it with the example from the original issue where watching for
5ForHKSnt3Cy96RFssfh8PSkA3uq9YBFgFMzwzfvjyCDdmkb
now doesn't show the pure that was killed ( this one, visible in prod5H2zstd4qCPjjNP7qQ5du3jEVSUDZUZKbgKjZxxMyFgZyP1e
)Also I've created and killed a pure almost right away, if you watch
5CACqqjMZUXEZsWFNETS3SWMmX85HMG6THF6EeQw43KjHcYY
on Rococo it shouldn't give you anything.5GnXakTjcrL8UJDd7QUrHXd7211U7c97Ydnq4ojBJghwJT6X
^ this one is also visible in prod, erroneously.