[config] set override unsafeTimeoutOverride to false by default #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes and provide context
e.g sei-protocol/sei-cosmos#153
Based on the logs, the data race is between QueryContext and the Finalizeblock for app.checkState.ctx.
I narrowed it cause and it seems like with UnsafeBypassCommitTimeoutOverride=true on by default, the single node consensus is much faster as it doesn't need to wait for timeout, all the datarace failures are happening in the query cli unit tests so i suspect that the queries and the async network are handled in different gorountines and thus have async access to checkState.Ctx (one is updating through finalizeBlock while the unit test is querying it)
Its fine to set to false, since it's mainly exposing the behavior that CLI queries do not have a freshness guarantee, which is expected as the data is constantly changing
Testing performed to validate your change
Tag has this change to set to false, will tag from main after this merges
sei-protocol/sei-cosmos#152