ci: bound IPFS publish timeouts#555
Merged
Merged
Conversation
lthibault
force-pushed
the
lthibault/ipfs-publish-timeout
branch
from
11dd183 to
0d92da2
Compare
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
1 participant
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.
Summary
timeout 12mipfs add,ipfs pin add,ipfs name publish, and DHT provide with explicit timeoutsWhy
The post-merge master run after the Synapse deploy fix reached a clean deploy but then hung in
Publish to IPFS via VPSwith no logs available while the job was in progress. This keeps future publish issues fail-fast and retryable instead of silently occupying the workflow.Validation
bash tests/test_ipfs_release_publish.shshellcheck scripts/ipfs_publish_release.sh tests/test_ipfs_release_publish.shruby -e 'require "yaml"; YAML.load_file(".github/workflows/rust.yml"); puts "yaml ok"'\n-git diff --check