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

helia migration: bug reproviding the same file #140

Open
SgtPooki opened this issue Oct 8, 2024 · 0 comments
Open

helia migration: bug reproviding the same file #140

SgtPooki opened this issue Oct 8, 2024 · 0 comments
Labels
effort/days Estimated to take multiple days, but less than a week exp/expert Having worked on the specific codebase is important kind/bug A bug in existing code (including security flaws) need/analysis Needs further analysis before proceeding P1 High: Likely tackled by core team if no one steps up status/blocked Unable to be worked further until needs are met

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Oct 8, 2024

Issue to address after merging #138

When publishing a file that has already been published to known peers, it will fail to get "FINAL_PEER" records again, probably because it's already been published.. need to investigate further.
@SgtPooki SgtPooki added the need/triage Needs initial labeling and prioritization label Oct 8, 2024
@SgtPooki SgtPooki changed the title helia migration: bug helia migration: bug reproviding the same file Oct 8, 2024
@SgtPooki SgtPooki added kind/bug A bug in existing code (including security flaws) exp/expert Having worked on the specific codebase is important P1 High: Likely tackled by core team if no one steps up status/blocked Unable to be worked further until needs are met need/analysis Needs further analysis before proceeding effort/days Estimated to take multiple days, but less than a week and removed need/triage Needs initial labeling and prioritization labels Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/days Estimated to take multiple days, but less than a week exp/expert Having worked on the specific codebase is important kind/bug A bug in existing code (including security flaws) need/analysis Needs further analysis before proceeding P1 High: Likely tackled by core team if no one steps up status/blocked Unable to be worked further until needs are met
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SgtPooki