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

Request data_column_sidecars_by_root and data_column_sidecars_by_range to corresponding custody peers, not randomly #5

Open
hangleang opened this issue Oct 14, 2024 · 0 comments · Fixed by #7
Open

Request data_column_sidecars_by_root and data_column_sidecars_by_range to corresponding custody peers, not randomly #5

hangleang opened this issue Oct 14, 2024 · 0 comments · Fixed by #7
Labels
bug Something isn't working

Comments

@hangleang
Copy link
Owner

hangleang commented Oct 14, 2024 •
edited
Loading

for context: grandine is asking a nimbus full node for all these columns in a range request, while it's not this nimbus' full nodes custody

nimbus-report
@hangleang hangleang added the bug Something isn't working label Oct 14, 2024
@hangleang hangleang changed the title Request data_column_sidecars_by_root to corresponding custody peers, not randomly Request data_column_sidecars_by_root and data_column_sidecars_by_range to corresponding custody peers, not randomly Oct 16, 2024
@hangleang hangleang linked a pull request Oct 18, 2024 that will close this issue
fix: request data column sidecar to random peer #7
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
1 participant
@hangleang