Smapp users should not be affected by the removal of auto-benchmarking, but if you run the node via command line or in a containerized setup and you receive the error failed to compute labels: initializing scrypter: no provider specified here is how to proceed:
In your node config add the following to re-enable auto-benchmarking:
The node will log warnings during startup informing you that you are using a deprecated feature, perform the auto benchmark and log the provider ID it selected due to the results of the benchmark.
Use that provider ID instead of -1 in your config. -1 as a workaround will be removed in a future release.
postcli with the CLI flag -printProviders can be used to see which providers are available on your system together with their Provider ID. You can run it instead to find out the ID of the provider of your choice.
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 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/spacemeshos/go-spacemesh from 1.0.2 to 1.1.0.
Release notes
Sourced from github.com/spacemeshos/go-spacemesh's releases.
... (truncated)
Commits
b23bc52
miner oracle use ref ballot for active set (#4876)8ba3b49
support existing multiple bootstrap files (#4875)b9f3333
Make grpc servers' start methods be synchronous (#4866)c8ad829
Fix out of memory issue when recovering and processing layers in tortoise (#4...c479d5b
Update Dockerfile comment and update curl usage (#4873)7c14f60
build(deps): Bump github.com/spacemeshos/post from 0.9.0 to 0.9.1 (#4870)aac7f79
sync: new protocol to fetch layer hash and certificate (#4846)bfa734e
Update go-libp2p dependency (#4800)9b10e8e
serve malfeasance proof over grpc (#4851)6518d2b
Update to go 1.20 (#4864)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