Skip to content

Bad publishing on sepolia v34 #19104

@wmitsuda

Description

@wmitsuda

this is about: https://github.com/erigontech/erigon-snapshot/pull/1075/changes

2 things happened here and need to be addressed:

  • it published 2 accounts.0-256.vi files -> I suspect this is due to recent bump (unrelated to the step size conversion which only do renames) + combination of forced index regeneration during publishing. I'm going to investigate that.
  • there should be some integrity check to prevent that; it didn't, and the PR was opened. Need to create a check to block multiple versions from the same range. Not only it was published, but that lead to a new sync to download both and as expected my node went broke.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions