Diagnose GOC halt #595
Labels
scope: testing
Code review, testing, making sure the code is following the specification.
type: bug
Issues that need priority attention -- something isn't working
Problem
Lots of slack discussion, this is me documenting efforts to fully diagnose why the GOC halt happened.
Closing criteria
Be able to consistently replicate the GOC bug, and confirm that a specific patch prevents the bug from occurring.
Problem details
Our best guess at what happened is a deadlock caused by writing within iterators. Unfortunately, there are a good amount of unit and e2e tests covering the suspect code. But the halt/hang only occurred in the testnet.
The text was updated successfully, but these errors were encountered: