-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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.
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
Provide easy/clear notification/error if falling behind reproviding #9702
Comments
Closed
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
May 19, 2023
Fixes: ipfs#9704 Fixes: ipfs#9702 Fixes: ipfs#9482 Depends on: ipfs/boxo#273
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
May 22, 2023
Fixes: ipfs#9704 Fixes: ipfs#9702 Depends on: ipfs/boxo#273
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
May 31, 2023
Fixes: ipfs#9704 Fixes: ipfs#9702 Depends on: ipfs/boxo#273
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 1, 2023
Fixes: ipfs#9704 Fixes: ipfs#9702 Fixes: ipfs#9703 Fixes: ipfs#9419 Depends on: ipfs/boxo#273
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 2, 2023
Fixes: ipfs#9704 Fixes: ipfs#9702 Fixes: ipfs#9703 Fixes: ipfs#9419 Depends on: ipfs/boxo#273
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 2, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 2, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 2, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 2, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 2, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 7, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 7, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 7, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 7, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 8, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 8, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 8, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 8, 2023
Jorropo
added a commit
to Jorropo/go-ipfs
that referenced
this issue
Jun 8, 2023
Jorropo
added a commit
that referenced
this issue
Jun 8, 2023
github-project-automation
bot
moved this from 🏃♀️ In Progress
to 🎉 Done
in IPFS Shipyard Team
Jun 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Done Criteria
There is a clear error message in logs AND metric for when we fail to provide within the configured interval.
Why Important
This makes it more self-service for content providers to understand why their content may not be discoverable by others. Kubo maintainers have seen various cases of content not being discoverable because a provider was unknowingly not refreshing the DHT before record expiration.
User/Customer
Mostly like operators with large pinsets.
Notes
Ideally any error message, should have suggestions of what can do. For example, if they don’t have the accelerated DHT enabled, that should be considered.
We want log messages and a metric to increase the the likelihood for an operator to detect this failure mode.
The text was updated successfully, but these errors were encountered: