Skip to content
Turbo build

fix(entropy): Use the block number of event instead of request data for revelation api #1293

Sign in to view logs

fix(entropy): Use the block number of event instead of request data for revelation api

fix(entropy): Use the block number of event instead of request data for revelation api #1293

Triggered via pull request April 23, 2025 22:09
@m30mm30m
opened #2607
block-based-revelation
Status Failure
Total duration 2m 20s
Artifacts –

ci-turbo-build.yml

on: pull_request
build
2m 10s
build
Fit to window
Zoom out
Zoom in

Annotations

12 errors
build
Unable to query cache: Error: Cache service responded with 422
build
Unable to reserve cache: TypeError: reserveCacheResponse.readBody is not a function
build
Unable to query cache: Error: Cache service responded with 422
build
Unable to query cache: Error: Cache service responded with 422
build
Unable to query cache: Error: Cache service responded with 422
build
Unable to query cache: Error: Cache service responded with 422
build
Unable to query cache: Error: Cache service responded with 422
build
Unable to query cache: Error: Cache service responded with 422
build
Unable to query cache: Error: Cache service responded with 422
build
Unable to query cache: Error: Cache service responded with 422
build
@pythnetwork/entropy-debugger#build: command (/home/runner/work/pyth-crosschain/pyth-crosschain/apps/entropy-debugger) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)
build
Process completed with exit code 1.