-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Bug] UnbondSupplier with 0 balance causes consensus failure #841
Comments
Seems to be a similar but a different issue.
|
Replicated to gather logs. Note:
|
Another similar but different issue:
Attaching relayminer logs - though nothing there seems relevant. |
@okdas Regarding the origin document in the description: it seems to me that what's happening is the supplier module account has a 0 balance (as opposed to any individual supplier).
|
This 👆 doesn't seem to be the case, given what's in config.yml. 🤔 Could it be that the supplier is being slashed to 0? |
Just replicated and checked the balances (apps, suppliers, modules) - they didn't seem to go to |
Just replicated this on main branch, the bug is still active:
|
I was working on a service that consumes events and there were a couple of events I randomly caught before the node died:
|
@red-0ne Could you provide an update on whether this is fixed or not? |
This will be investigated this week. Was planning to have Path integrated first, but I think I'll do without it. |
## Summary This PR fixes a few bugs that were dependent to each other: 1. Gracefully unbond suppliers that have 0upokt due to off-stake slashing. 2. Fix access to an expired session tree on the realy miner 3. Fix proof block hash seed used on chain. @okdas , One case I didn't manage to reproduce is having the application module account go to `0`. Please tell me if you encounter it again. ## Issue - #841 ## Type of change Select one or more from the following: - [ ] New feature, functionality or library - [ ] Consensus breaking; add the `consensus-breaking` label if so. See #791 for details - [x] Bug fix - [ ] Code health or cleanup - [ ] Documentation - [ ] Other (specify) ## Testing - [ ] **Documentation**: `make docusaurus_start`; only needed if you make doc changes - [x] **Unit Tests**: `make go_develop_and_test` - [x] **LocalNet E2E Tests**: `make test_e2e` - [ ] **DevNet E2E Tests**: Add the `devnet-test-e2e` label to the PR. ## Sanity Checklist - [x] I have tested my changes using the available tooling - [x] I have commented my code - [x] I have performed a self-review of my own code; both comments & source code
This issue has been addressed - thank you @red-0ne |
Objective
There's an issue on main branch that can cause a chain halt.
Origin Document
Steps to reproduce
hey -n 10000 -c 2 -m POST -H "Content-Type: application/json" -d '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' http://localhost:42069/anvil
.0
the exception will appear.Goals
Deliverables
Non-goals / Non-deliverables
General deliverables
Creator: @okdas
Co-Owners: TBD
The text was updated successfully, but these errors were encountered: