Panic: Unknown transaction #6
Labels
No labels
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/monza#6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Current Behavior
./bin/monza explore -r http://morph-chain.frostfs.devenv:30333
Steps to Reproduce (for bugs)
make clean up
The problem arises due to chain cache. It's stored in ~/.config/monza by default. If you do some manipulations with one devenv and then make clean restart,
monza
does not clean up cache file - just opens it "as it is" without distinguishing old data from new. Thus if the block with the specified index already exists, it will take old block from cache instead of making request to get new. That's why some transactions are invalid andexplore
panics.For now just remove old cache file by yourself.
Can we have some chain-dependent cache?
One reasonable thing to do it to use network magic as the name, but network magic repeats in tests.
We can use the hash of the first block, though -- it contains timestamp, so should be unique.
And if we have no first block, we have nothing to cache anyway.
Added validation via the first block
That's brilliant, I like it.
Fixed in #7