-
Notifications
You must be signed in to change notification settings - Fork 660
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
dispute-coordinator: subsystem stalls during dispute load test #689
Labels
I2-bug
The node fails to follow expected behavior.
Comments
Maybe it's caused by cycles somewhere? |
It is actually not solved, just reverted (postponed). |
the-right-joyce
added
I2-bug
The node fails to follow expected behavior.
T8-parachains_engineering
and removed
I3-bug
labels
Aug 25, 2023
claravanstaden
pushed a commit
to Snowfork/polkadot-sdk
that referenced
this issue
Dec 8, 2023
* encode to hex before call * added pruning archive * updated variable names * changed error message
helin6
pushed a commit
to boolnetwork/polkadot-sdk
that referenced
this issue
Feb 5, 2024
Bumps [log](https://github.com/rust-lang/log) from 0.4.14 to 0.4.17. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang/log/blob/master/CHANGELOG.md) - [Commits](rust-lang/log@0.4.14...0.4.17) --- updated-dependencies: - dependency-name: log dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@AndreiEres we need to check if this doesn't happen anymore, there were some issues when switching to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://grafana.parity-mgmt.parity.io/goto/6WbF6r-4k?orgId=1
This seems to be happening since paritytech/polkadot#6854 . Once I removed this change I got no more stalls.
I suspect this was introduced by paritytech/orchestra#36 or other changes in metered channel.
CC @vstakhov
The text was updated successfully, but these errors were encountered: