Skip to content

Update FastMCP constructor to respect Pydantic settings configuration #2562

Update FastMCP constructor to respect Pydantic settings configuration

Update FastMCP constructor to respect Pydantic settings configuration #2562

Triggered via pull request August 28, 2025 19:21
@saqadrisaqadri
synchronize #1244
saqadri:main
Status Success
Total duration 1m 36s
Artifacts

pull-request-checks.yml

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

Annotations

32 warnings and 8 notices
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>0WKywaAAAAACg1tR5zNfWTZejPYI1+hFPQkwyQUEyMDMwMTA2MDExAEVkZ2U=
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>0WqywaAAAAAD4rgt8xvGLQaPNLx1fbKP4QkwyQUEyMDMwMTA2MDM3AEVkZ2U=
checks / test (3.13, 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>0WqywaAAAAAA0gTt26ssYRJ0w2FCiOVorRE0yRURHRTEwMjIARWRnZQ==
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>0W6ywaAAAAACn840eqirnT6qilOOw9dMTQ0hJMzBFREdFMDIyMQBFZGdl
checks / test (3.11, 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>0W6ywaAAAAADfxNMy1+TcTZ2QmWmEIknsQ0hJMzBFREdFMDIxMgBFZGdl
checks / test (3.10, 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>0W6ywaAAAAACU7tBaIzjuQJ/pvHo+kX6zUEFPRURHRTA2MjAARWRnZQ==
checks / test (3.10, highest, ubuntu-latest)
Failed to restore: Cache service responded with 400
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>0W6ywaAAAAACG197aLDlPQ42Gz6jT5VQrUEFPRURHRTA2MTQARWRnZQ==
checks / test (3.11, 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>0a6ywaAAAAADVxUNBS+Z3TL3iHjj7EpErQkwyQUEyMDMwMTA3MDExAEVkZ2U=
checks / test (3.13, lowest-direct, ubuntu-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>0gqywaAAAAADzdwVS3DyjQo/WAW6+dA6hRE0yRURHRTA4MjIARWRnZQ==
checks / test (3.10, highest, 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>0hKywaAAAAAD1kCMqaM/2TpnCWXdSMLz6QkwyQUEyMDMwMTA3MDI5AEVkZ2U=
checks / test (3.13, 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>0hKywaAAAAADwoe3Z1LB+SofSZojldpt8Q0hJMzBFREdFMDMxNQBFZGdl
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>0haywaAAAAAB6pvKBNc5dQITzOLx+mCG1Q0hJMzBFREdFMDQwNwBFZGdl
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>0hqywaAAAAABI/zVS7Y/mQLngtxcT0B3JQkwyQUEyMDMwMTEwMDE3AEVkZ2U=
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>0hqywaAAAAACKZoN2Xgy9TZxKZfPjbivhQ0hJMzBFREdFMDIwOQBFZGdl
checks / test (3.11, 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>0iaywaAAAAADTxf8trSqYQIRGSHunQnylUEhYMzFFREdFMDUxMgBFZGdl
checks / test (3.10, lowest-direct, 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>0laywaAAAAAAkCtYYYIMxQrBN31L1r1OSQkwyQUEyMDMwMTA4MDA3AEVkZ2U=
checks / test (3.12, highest, windows-latest)
Failed to restore: Cache service responded with 400
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.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.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.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.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.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