-
Notifications
You must be signed in to change notification settings - Fork 263
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
Stack overflow while running CAT #1208
Comments
Interesting find. Theoretically we should only be recursively calling this for the amount of peers we are connected to and no more. Will need to further investigate |
yeah, I'm still questioning how this gets hit this did fix it tho the first test introduced there will fail on main with the same recursive call, however I don't think that scenario should ever actually occur |
without this line in the first test delete(reactor.mempool.seenByPeersSet.set[wantedTx.Key()].peers, reactor.ids.GetIDForPeer(peers[1].ID())) the test on main will continually call |
## Description Closes: #1208 --- #### PR checklist - [ ] Tests written/updated - [ ] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments
## Description Closes: #1208 --- #### PR checklist - [ ] Tests written/updated - [ ] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments (cherry picked from commit 52b993c)
we are recursively calling
findNewPeerToRequest
, which can cause a stack overflow when removing a peerThe text was updated successfully, but these errors were encountered: