Skip to content

fix: attempt to query resource-specific protected resource metadata before root PRM #2171

fix: attempt to query resource-specific protected resource metadata before root PRM

fix: attempt to query resource-specific protected resource metadata before root PRM #2171

Triggered via pull request July 15, 2025 00:06
Status Failure
Total duration 2m 31s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
17s
checks / pre-commit
checks  /  readme-snippets
9s
checks / readme-snippets
Matrix: checks / test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 16 warnings
checks / pre-commit
Process completed with exit code 1.
checks / test (3.11, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0t5t1aAAAAAAMU7xdhJGiSrUzDwhWRTh1QkwyQUEyMDMwMTA1MDMxAEVkZ2U=
checks / test (3.11, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0uZt1aAAAAADUsf77JVvXR4DU5ljsV6nhQ0hJMzBFREdFMDIxMgBFZGdl
checks / test (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0uZt1aAAAAABcFSFycm4qT6IMGa63Ym8ZUEhYMzFFREdFMDIxNgBFZGdl
checks / test (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0u5t1aAAAAAAojKvPhgj5QpUwOkwyOK2WUEFPRURHRTA1MDgARWRnZQ==
checks / test (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>095t1aAAAAADYdg+kRGV0Q543ELtpvzIvQkwyQUEyMDMwMTA1MDM1AEVkZ2U=
checks / test (3.10, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Apx1aAAAAABj5NA9E784S6+nhb+HmwFAQkwyQUEyMDMwMTA2MDIzAEVkZ2U=
checks / test (3.13, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0BJx1aAAAAAACbLnv+Ve8TI/enbuR8k/4UEhYMzFFREdFMDUwNgBFZGdl
checks / test (3.12, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0DJx1aAAAAACCKTipSuxhS6k92D3rzRSvQlkzRURHRTAxMjEARWRnZQ==
checks / test (3.11, windows-latest)
Failed to restore: Cache service responded with 400