Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix archive data bugs fix in Lily v0.8.8 #911

Closed
placer14 opened this issue Mar 10, 2022 · 2 comments
Closed

Fix archive data bugs fix in Lily v0.8.8 #911

placer14 opened this issue Mar 10, 2022 · 2 comments
Assignees
@iand
Labels
backfill required Alters data extraction such that backfilling is necessary kind/bug Kind: Bug P1 P1: Must be resolved

Comments

@placer14
Copy link
Contributor

Describe the bug:

There was missing and incorrect data and the following epochs/tasks require a re-run using Lily v0.8.8:

  • messages task (targeting malformed data in parsed_messages) from epoch 1594679 to current
  • actorstatesminer task (targeting missing data in miner_sector_events) from epoch 1594679 to current

Lily Version: v0.8.8
@placer14 placer14 added kind/bug Kind: Bug P1 P1: Must be resolved backfill required Alters data extraction such that backfilling is necessary labels Mar 10, 2022
@placer14 placer14 mentioned this issue Mar 10, 2022
Merged
@iand iand self-assigned this Mar 11, 2022
@iand
Copy link
Contributor

iand commented Mar 11, 2022

Need to create a partial or full lily snapshot to cover this range (highest we have is 1593203)

@iand
Copy link
Contributor

iand commented Mar 18, 2022

Completed and copied files to fil-archive. Nightly sync will push these to s3 tonight.

@iand iand closed this as completed Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iand iand

Labels
backfill required Alters data extraction such that backfilling is necessary kind/bug Kind: Bug P1 P1: Must be resolved
Projects
Sentinel
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iand @placer14