Skip to content

Expose RequestParams._meta in ClientSession.call_tool #2722

Expose RequestParams._meta in ClientSession.call_tool

Expose RequestParams._meta in ClientSession.call_tool #2722

Triggered via pull request September 23, 2025 12:43
Status Failure
Total duration 2m 12s
Artifacts

pull-request-checks.yml

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

Annotations

1 error, 32 warnings, and 8 notices
checks / pre-commit
Process completed with exit code 1.
checks / test (3.11, highest, 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>0H5bSaAAAAABoCEARSDy0Q6JuHmqwa9MrQkwyQUEyMDMwMTEwMDI5AEVkZ2U=
checks / test (3.11, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, highest, 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>0IJbSaAAAAAAEQbIdIMsPQZJSzzICpM3pQkwyQUEyMDMwMTA5MDM1AEVkZ2U=
checks / test (3.12, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, lowest-direct, 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>0IJbSaAAAAAAS3+Q/52t5Q51I+ovqZP8IQ0hJMzBFREdFMDMxMQBFZGdl
checks / test (3.11, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, highest, 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>0IZbSaAAAAAB5ocziHMJ3TZ7h1+cg3eBaQ0hJMzBFREdFMDIxMABFZGdl
checks / test (3.10, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, lowest-direct, 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>0IpbSaAAAAAAXovPO6rk5RoxKWn9ov5r9Q0hJMzBFREdFMDMxMQBFZGdl
checks / test (3.10, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, lowest-direct, 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>0I5bSaAAAAAAqJUSUWrcgRb/RpYF+b2pzQ0hJMzBFREdFMDMxNABFZGdl
checks / test (3.13, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, lowest-direct, 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>0I5bSaAAAAABdB6Q1n8iTQIKRgeWei3+UQlkzRURHRTAzMDgARWRnZQ==
checks / test (3.12, lowest-direct, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, highest, 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>0KZbSaAAAAACcE0uRTwiER7HW52M/5kWcQlkzRURHRTAzMTUARWRnZQ==
checks / test (3.13, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, highest, 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>0UJbSaAAAAAChAnH/m0H6SaJK1uwjVkLTUEhYMzFFREdFMDYxMABFZGdl
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, highest, 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>0UZbSaAAAAACM2RdV+6u6TqIH367tJyxIQ0hJMzBFREdFMDQwNgBFZGdl
checks / test (3.10, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, lowest-direct, 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>0UpbSaAAAAAAGRipjxNpOTaWwciyD2IllQ0hJMzBFREdFMDQwNgBFZGdl
checks / test (3.11, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, lowest-direct, 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>0V5bSaAAAAAAZ95qI0JPkRoDEYEn8UrI7RE0yRURHRTEwMjIARWRnZQ==
checks / test (3.13, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.10, lowest-direct, 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>0XpbSaAAAAAA2nXwbGtdzTIcYsPyHZ2+qQ0hJMzBFREdFMDQxNQBFZGdl
checks / test (3.10, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.13, highest, 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>0Y5bSaAAAAABvtMBKbGeEQ4xWM3nMvR+XQ0hJMzBFREdFMDEyMgBFZGdl
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, lowest-direct, 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>0ZJbSaAAAAAD0w81SJyjJQ5k4ovpYCwsTREVOMzAxMDAwMTA2MDE5AEVkZ2U=
checks / test (3.12, lowest-direct, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.11, highest, 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>0fZbSaAAAAABcFzGUIja0SZs6XVhZ5rZQRE0yRURHRTA0MTMARWRnZQ==
checks / test (3.11, highest, windows-latest)
Failed to restore: Cache service responded with 400
checks / test (3.12, highest, 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.10, highest, 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, lowest-direct, 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, lowest-direct, 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.10, lowest-direct, 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, highest, 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, lowest-direct, 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, highest, 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