The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Skipping exec 'cargo publish --no-verify' in 'crates/fuel-streams-core' due to 'dry-run: true'

Skipping awaiting when 'fuel-streams-core 0.0.10' will be available due to 'dry-run: true'

Skipping exec 'cargo publish --no-verify' in 'crates/fuel-data-parser' due to 'dry-run: true'

Skipping awaiting when 'fuel-data-parser 0.0.10' will be available due to 'dry-run: true'

Skipping exec 'cargo publish --no-verify' in 'crates/fuel-streams-macros' due to 'dry-run: true'

Skipping awaiting when 'fuel-streams-macros 0.0.10' will be available due to 'dry-run: true'

Skipping exec 'cargo publish --no-verify' in 'crates/fuel-streams-macros/subject-derive' due to 'dry-run: true'

Skipping awaiting when 'subject-derive 0.0.10' will be available due to 'dry-run: true'

Skipping exec 'cargo publish --no-verify' in 'crates/fuel-streams' due to 'dry-run: true'

Skipping awaiting when 'fuel-streams 0.0.10' will be available due to 'dry-run: true'

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to save: Unable to reserve cache with key cargo-install-cross-ac4c11c-6ac834b650dc88249cdf, another job may be creating this cache. More details: {"$id":"1","innerException":null,"message":"Request was blocked due to exceeding usage of resource 'Count' in namespace ''.","typeName":"Microsoft.TeamFoundation.Framework.Server.RequestBlockedException, Microsoft.TeamFoundation.Framework.Server","typeKey":"RequestBlockedException","errorCode":0,"eventId":3000}

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to save: Cache service responded with 429 during commit cache.

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to save: Cache service responded with 429 during commit cache.

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to restore: Cache service responded with 429

Failed to save: Unable to reserve cache with key cargo-install-cross-ac4c11c-802bdc8a3ac3641e4374, another job may be creating this cache. More details: {"$id":"1","innerException":null,"message":"Request was blocked due to exceeding usage of resource 'Count' in namespace ''.","typeName":"Microsoft.TeamFoundation.Framework.Server.RequestBlockedException, Microsoft.TeamFoundation.Framework.Server","typeKey":"RequestBlockedException","errorCode":0,"eventId":3000}

Failed to restore: Cache service responded with 429

0% - 0 hits, 0 misses, 0 errors

0% - 0 hits, 0 misses, 0 errors

96% - 676 hits, 31 misses, 0 errors