Skip to content

Expose RequestParams._meta in ClientSession.call_tool #2742

Expose RequestParams._meta in ClientSession.call_tool

Expose RequestParams._meta in ClientSession.call_tool #2742

Triggered via pull request September 24, 2025 15:14
Status Failure
Total duration 2m 43s
Artifacts

pull-request-checks.yml

on: pull_request
checks  /  pre-commit
38s
checks / pre-commit
checks  /  readme-snippets
15s
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>0FwvUaAAAAADEqpWVGfKGQpipWZTh4IcSUEhYMzFFREdFMDUxMwBFZGdl
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>0JwvUaAAAAACJXxc/EQmERJfz/SO6KqdcUEFPRURHRTA1MjAARWRnZQ==
checks / test (3.12, highest, 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>0KQvUaAAAAAA7kPocFVGKS7/TVDzrJUDQUEFPRURHRTA1MTUARWRnZQ==
checks / test (3.13, lowest-direct, 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>0KwvUaAAAAACE0fYMW1LLQ5mz7PEoV6bMQkwyQUEyMDMwMTA4MDQ1AEVkZ2U=
checks / test (3.10, 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>0LgvUaAAAAACj+KRzYyw6TYW3NHue4dWKUEFPRURHRTA2MTIARWRnZQ==
checks / test (3.13, 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>0PgvUaAAAAAAwmHvYGrM2QaCdyxG634uwQlkzRURHRTA1MTgARWRnZQ==
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>0UAvUaAAAAABmKDyeaF8ySpCHMFXuyFELREVOMzAxMDAwMTA4MDQ3AEVkZ2U=
checks / test (3.10, highest, 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>0UQvUaAAAAADvIn+ZAPEBRKM0JpQXXWOIUEFPRURHRTA2MjIARWRnZQ==
checks / test (3.12, lowest-direct, ubuntu-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>0VgvUaAAAAABWhYySEr92SYldXpbmCwy7QkwyQUEyMDMwMTEwMDQ1AEVkZ2U=
checks / test (3.13, lowest-direct, 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>0WwvUaAAAAABspzUJubvUS60GG/BX1zXzQkwyQUEyMDMwMTA4MDM5AEVkZ2U=
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>0XQvUaAAAAADEElYjjPGXR7NSwfbwOe+oQ0hJMzBFREdFMDQwOABFZGdl
checks / test (3.11, highest, windows-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>0XwvUaAAAAABxA60RKtaVTIoED111P/kNQkwyQUEyMDMwMTA4MDMzAEVkZ2U=
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>0YQvUaAAAAABBk0N3kMmNSbuvIzHrFtvLREVOMzAxMDAwMTA3MDMxAEVkZ2U=
checks / test (3.10, highest, 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>0ZwvUaAAAAAAk89j0P524S4Lqi/R84kyVQkwyQUEyMDMwMTA4MDQ1AEVkZ2U=
checks / test (3.10, lowest-direct, 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>0bAvUaAAAAADzI2r1lBGWTbJQeo0KhoPRQ0hJMzBFREdFMDExNQBFZGdl
checks / test (3.11, 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>0kAvUaAAAAAB9ISlGRlH4Q7VjPCSJMUxIQlkzRURHRTAyMTkARWRnZQ==
checks / test (3.13, highest, windows-latest)
Failed to restore: Cache service responded with 400
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.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
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.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.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, 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