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.

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

chore(deps): bump github.com/ipfs/boxo from 0.24.2 to 0.25.0 #273

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 10, 2024

Bumps github.com/ipfs/boxo from 0.24.2 to 0.25.0.

Release notes

Sourced from github.com/ipfs/boxo's releases.

v0.25.0

Added

  • routing/http/server: added built-in Prometheus instrumentation to http delegated /routing/v1/ endpoints, with custom buckets for response size and duration to match real world data observed at the delegated-ipfs.dev instance. #718 #724
  • routing/http/server: added configurable routing timeout (DefaultRoutingTimeout being 30s) to prevent indefinite hangs during content/peer routing. Set custom duration via WithRoutingTimeout. #720
  • routing/http/server: exposes Prometheus metrics on prometheus.DefaultRegisterer and a custom one can be provided via WithPrometheusRegistry #722
  • gateway: NewCacheBlockStore and NewCarBackend will use prometheus.DefaultRegisterer when a custom one is not specified via WithPrometheusRegistry #722
  • filestore: added opt-in WithMMapReader option to FileManager to enable memory-mapped file reads #665
  • bitswap/routing ProviderQueryManager does not require calling Startup separate from New. #741
  • bitswap/routing ProviderQueryManager does not use liftcycle context.

Changed

  • bitswap, routing, exchange (#641):

    • ✨ Bitswap is no longer in charge of providing blocks to the newtork: providing functionality is now handled by a exchange/providing.Exchange, meant to be used with provider.System so that all provides follow the same rules (multiple parts of the code where handling provides) before.
    • 🛠 bitswap/client/internal/providerquerymanager has been moved to routing/providerquerymanager where it belongs. In order to keep compatibility, Bitswap now receives a routing.ContentDiscovery parameter which implements FindProvidersAsync(...) and uses it to create a providerquerymanager with the default settings as before. Custom settings can be used by using a custom providerquerymanager to manually wrap a ContentDiscovery object and pass that in as ContentDiscovery on initialization while setting bitswap.WithDefaultProviderQueryManager(false) (to avoid re-wrapping it again).
    • The renovated providedQueryManager will trigger lookups until it manages to connect to MaxProviders. Before it would lookup at most MaxInProcessRequests*MaxProviders and connection failures may have limited the actual number of providers found.
    • 🛠 We have aligned our routing-related interfaces with the libp2p routing ones, including in the reprovider.System.
    • In order to obtain exactly the same behaviour as before (i.e. particularly ensuring that new blocks are still provided), what was done like:
    	bswapnet := network.NewFromIpfsHost(host, contentRouter)
    	bswap := bitswap.New(p.ctx, bswapnet, blockstore)
    	bserv = blockservice.New(blockstore, bswap)
    • becomes:
    	// Create network: no contentRouter anymore
    	bswapnet := network.NewFromIpfsHost(host)
    	// Create Bitswap: a new "discovery" parameter, usually the "contentRouter"
    	// which does both discovery and providing.
    	bswap := bitswap.New(p.ctx, bswapnet, discovery, blockstore)
    	// A provider system that handles concurrent provides etc. "contentProvider"
    	// is usually the "contentRouter" which does both discovery and providing.
    	// "contentProvider" could be used directly without wrapping, but it is recommended
    	// to do so to provide more efficiently.
    	provider := provider.New(datastore, provider.Online(contentProvider)
    	// A wrapped providing exchange using the previous exchange and the provider.
    	exch := providing.New(bswap, provider)
    // Finally the blockservice
    bserv := blockservice.New(blockstore, exch)
    ...

    • The above is only necessary if content routing is needed. Otherwise:
    	// Create network: no contentRouter anymore

... (truncated)

Changelog

Sourced from github.com/ipfs/boxo's changelog.

[v0.25.0]

Added

  • routing/http/server: added built-in Prometheus instrumentation to http delegated /routing/v1/ endpoints, with custom buckets for response size and duration to match real world data observed at the delegated-ipfs.dev instance. #718 #724
  • routing/http/server: added configurable routing timeout (DefaultRoutingTimeout being 30s) to prevent indefinite hangs during content/peer routing. Set custom duration via WithRoutingTimeout. #720
  • routing/http/server: exposes Prometheus metrics on prometheus.DefaultRegisterer and a custom one can be provided via WithPrometheusRegistry #722
  • gateway: NewCacheBlockStore and NewCarBackend will use prometheus.DefaultRegisterer when a custom one is not specified via WithPrometheusRegistry #722
  • filestore: added opt-in WithMMapReader option to FileManager to enable memory-mapped file reads #665
  • bitswap/routing ProviderQueryManager does not require calling Startup separate from New. #741
  • bitswap/routing ProviderQueryManager does not use liftcycle context.

Changed

  • bitswap, routing, exchange (#641):

    • ✨ Bitswap is no longer in charge of providing blocks to the newtork: providing functionality is now handled by a exchange/providing.Exchange, meant to be used with provider.System so that all provides follow the same rules (multiple parts of the code where handling provides) before.
    • 🛠 bitswap/client/internal/providerquerymanager has been moved to routing/providerquerymanager where it belongs. In order to keep compatibility, Bitswap now receives a routing.ContentDiscovery parameter which implements FindProvidersAsync(...) and uses it to create a providerquerymanager with the default settings as before. Custom settings can be used by using a custom providerquerymanager to manually wrap a ContentDiscovery object and pass that in as ContentDiscovery on initialization while setting bitswap.WithDefaultProviderQueryManager(false) (to avoid re-wrapping it again).
    • The renovated providedQueryManager will trigger lookups until it manages to connect to MaxProviders. Before it would lookup at most MaxInProcessRequests*MaxProviders and connection failures may have limited the actual number of providers found.
    • 🛠 We have aligned our routing-related interfaces with the libp2p routing ones, including in the reprovider.System.
    • In order to obtain exactly the same behaviour as before (i.e. particularly ensuring that new blocks are still provided), what was done like:
    	bswapnet := network.NewFromIpfsHost(host, contentRouter)
    	bswap := bitswap.New(p.ctx, bswapnet, blockstore)
    	bserv = blockservice.New(blockstore, bswap)
    • becomes:
    	// Create network: no contentRouter anymore
    	bswapnet := network.NewFromIpfsHost(host)
    	// Create Bitswap: a new "discovery" parameter, usually the "contentRouter"
    	// which does both discovery and providing.
    	bswap := bitswap.New(p.ctx, bswapnet, discovery, blockstore)
    	// A provider system that handles concurrent provides etc. "contentProvider"
    	// is usually the "contentRouter" which does both discovery and providing.
    	// "contentProvider" could be used directly without wrapping, but it is recommended
    	// to do so to provide more efficiently.
    	provider := provider.New(datastore, provider.Online(contentProvider)
    	// A wrapped providing exchange using the previous exchange and the provider.
    	exch := providing.New(bswap, provider)
    // Finally the blockservice
    bserv := blockservice.New(blockstore, exch)
    ...

    • The above is only necessary if content routing is needed. Otherwise:

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/ipfs/boxo](https://github.com/ipfs/boxo) from 0.24.2 to 0.25.0.
- [Release notes](https://github.com/ipfs/boxo/releases)
- [Changelog](https://github.com/ipfs/boxo/blob/main/CHANGELOG.md)
- [Commits](ipfs/boxo@v0.24.2...v0.25.0)

---
updated-dependencies:
- dependency-name: github.com/ipfs/boxo
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Dec 10, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 20, 2024

Superseded by #274.

@dependabot dependabot bot closed this Dec 20, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/ipfs/boxo-0.25.0 branch December 20, 2024 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants