mirror of
https://github.com/PrefectHQ/fastmcp.git
synced 2026-08-24 14:34:17 +02:00
ba283ddb4c* Support CallArgument and Depends bindings from uncalled-for 0.4.0 uncalled-for 0.4.0 adds explicit argument references: CallArgument() lets a dependency factory read an argument of the function it serves, and Depends(factory, **bindings) supplies factory arguments at the declaration site (https://github.com/chrisguidry/uncalled-for/pull/12). FastMCP's resolver now opens a frame_scope() around dependency resolution, with the sanitized user arguments as the frame's provided values. A CallArgument can reference a tool call's public parameters, but a caller-supplied value for a dependency parameter name is still stripped before resolution. CallArgument and CycleError are re-exported from fastmcp.dependencies, and the dependency-injection docs cover both features. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Raise the pydocket floor to 0.24.0 outside Windows pydocket 0.24.0 resolves TaskArgument and CallArgument through uncalled-for 0.4.0's call-scoped frames. Windows keeps the 0.20.0 floor: the burner-redis<0.1.7 pin there transitively caps pydocket to <0.20.2, and burner-redis has shipped no fixed release yet. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Bump the pydocket floor to 0.24.1 for reliable worker shutdown docket 0.24.1 fixes a lost cancellation in worker shutdown on Python 3.10 and 3.11 (chrisguidry/docket#456): asyncio.wait_for swallowed a cancellation delivered in the same event-loop tick that its inner future completed, so cancelling run_forever during our lifespan teardown left the worker running and hung the test session. That is what timed out the Python 3.10 and lowest-direct jobs here. The floor stays platform-split; Windows keeps >=0.20.0 under the burner-redis pin. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Drop the Windows burner-redis pin and unify the pydocket floor at 0.24.1 The pin blamed the wrong package. The Windows "interpreter crash" that motivated it (#4618) was pydocket 0.23.1 losing an external cancellation during worker teardown; pytest-timeout's hard kill of the hung xdist worker discarded its stdout and looked like a native fault. Capping burner-redis also dragged pydocket below 0.20.2, so the two variables were never separated. The repro matrix on prefectlabs/burner-redis#7 shows the July environment failing as resolved, passing with only pydocket rolled back, and passing with pydocket 0.24.1 alongside burner-redis 0.1.7 on Windows. pydocket 0.24.1 carries the fix (chrisguidry/docket#456), so every platform now shares one floor. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: nate nowack <thrast36@gmail.com> |
||
|---|---|---|
| .. | ||
| auth | ||
| providers | ||
| transforms | ||
| authorization.mdx | ||
| completions.mdx | ||
| composition.mdx | ||
| context.mdx | ||
| dependency-injection.mdx | ||
| elicitation.mdx | ||
| extensions.mdx | ||
| icons.mdx | ||
| lifespan.mdx | ||
| logging.mdx | ||
| middleware.mdx | ||
| pagination.mdx | ||
| progress.mdx | ||
| prompts.mdx | ||
| resources.mdx | ||
| sampling.mdx | ||
| server.mdx | ||
| sessions.mdx | ||
| storage-backends.mdx | ||
| tasks.mdx | ||
| telemetry.mdx | ||
| testing.mdx | ||
| tool-fingerprinting.mdx | ||
| tools.mdx | ||
| versioning.mdx | ||
| visibility.mdx | ||