Skip to content

Expose RequestParams._meta in ClientSession.call_tool #2366

Expose RequestParams._meta in ClientSession.call_tool

Expose RequestParams._meta in ClientSession.call_tool #2366

Triggered via pull request August 3, 2025 18:43
Status Failure
Total duration 2m 34s
Artifacts

pull-request-checks.yml

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

Annotations

1 error, 16 warnings, and 4 notices
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>0+a2PaAAAAADAyZ2fgU09R7Cn3vJgL1R9QkwyQUEyMDMwMTA1MDI3AEVkZ2U=
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>0+a2PaAAAAABYehUK6s1/QYYFrOjCnIoMQkwyQUEyMDMwMTA5MDA3AEVkZ2U=
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>0+a2PaAAAAAADfI7EbKJFSYjnZCjwzLFaQkwyQUEyMDMwMTA2MDUzAEVkZ2U=
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>0+62PaAAAAACjcFCSYIjDSJFn6fqrx/JVUEFPRURHRTA2MTMARWRnZQ==
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>0O66PaAAAAADBIZaBDBEzTLOrgt0fw/4AQ0hJMzBFREdFMDMxMwBFZGdl
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>0RK6PaAAAAAAJu2Mlml1xR6gL4pAeCIWMUEFPRURHRTA2MTYARWRnZQ==
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>0R66PaAAAAAB/fpzyJUJBQIq+fo6lv/stQ0gxRURHRTEyMTYARWRnZQ==
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>0Ua6PaAAAAABaObiK7PTGTK/X0KznbZnXQ0hJMzBFREdFMDQyMgBFZGdl
checks / test (3.11, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
checks / test (3.13, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
checks / test (3.12, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
checks / test (3.11, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677