Repository navigation
Conversation
Contributor
Author
|
Closing as completed via #78. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
web3-storage v0.5 needs two engine changes. storage-provider-node 0.5.0 no longer has
--storage-modeor--enable-checkpoint-coordinator, so it exits on start witherror: unexpected argument '--storage-mode' found. Its storage is always RocksDB at--storage-path. The v0.5.0 runtime sets a relay parent offset of 1, which only the slot-based collator supports. With the default authoring, every block fails withInvalidNumberOfDescendants { expected: 2, received: 0 }and the chain stays at #0.Changes
storage-provider-nodeservice passes--storage-pathand drops both flags. An ephemeral run keeps the provider's RocksDB in the service's temp dir, next to the keyfile, which is removed on exit. This replaces theinmemorymode.WEB3_STORAGE_PROVIDER_STORAGE_MODEfromconfig/ports.envand from the generatedports.local.env.--authoring=slot-based, like the other parachains.networks/previewnet.jsonpins web3-storage tov0.5.1-paseoinstead oflatest, and the CI e2e step clones that tag. Withlatest, a web3-storage release changed what CI and unpinned runs got:v0.5.0-paseobroke main.Provider-node 0.4.1 defaults to in-memory storage when it does not get
--storage-mode disk, so a deployment has to move to this engine release and to web3-storagev0.5.1-paseotogether. paritytech/preview-net-v1#203 does both in one PR.