+ Q(iRt^RIt^RIt^RIHt^RIt^RIHt^RIH t ^RI H t ] !R4t ]!4t ]P!RRR 7tR R lt]P"RR R ll4tR#)z-FastMCP tasks CLI for Docket task management.N) Annotated)Console)load_and_merge_config) get_loggerz cli.taskstasksz,Manage FastMCP background tasks using Docket)namehelpcV^8dQhRR/#)returnN)formats"W/Users/agent/.openclaw/workspace/venv/lib/python3.14/site-packages/fastmcp/cli/tasks.py __annotate__rs##4#c^RIpVPPPpVP R4'd.\ P R4\P!^4R#R#)zCheck if Docket is configured with a distributed backend. The CLI worker runs as a separate process, so it needs Redis/Valkey to coordinate with the main server process. Raises: SystemExit: If using memory:// URL Nz memory://up[bold red]✗ In-memory backend not supported by CLI[/bold red] Your Docket configuration uses an in-memory backend (memory://) which only works within a single process. To use [cyan]fastmcp tasks[/cyan] CLI commands (which run in separate processes), you need a distributed backend: [bold]1. Install Redis or Valkey:[/bold] [dim]macOS:[/dim] brew install redis [dim]Ubuntu:[/dim] apt install redis-server [dim]Valkey:[/dim] See https://valkey.io/ [bold]2. Start the service:[/bold] redis-server [bold]3. Configure Docket URL:[/bold] [dim]Environment variable:[/dim] export FASTMCP_DOCKET_URL=redis://localhost:6379/0 [bold]4. Try again[/bold] The memory backend works great for single-process servers, but the CLI commands need a distributed backend to coordinate across processes. Need help? See: [cyan]https://gofastmcp.com/docs/tasks[/cyan]) fastmcpsettingsdocketurl startswithconsoleprintsysexit)r docket_urls rcheck_distributed_backendrsU!!((,,J[))  L (  +*rczV^8dQhR\\R,\P!RR73,RR/#)r server_specNzWPython file to run, optionally with :object suffix, or None to auto-detect fastmcp.json)rr )rstrcyclopts Parameter)r s"rrr=s@11 d j  1 1rcaa^RIo\4\V4wr\ P!XPP44oVV3Rlp\ P!V!44R# \d\P !^4Lvi;i \d0\PR4\P !^4R#i;i)a0Start an additional worker to process background tasks. Connects to your Docket backend and processes tasks in parallel with any other running workers. Configure via environment variables (FASTMCP_DOCKET_*). Example: fastmcp tasks worker server.py fastmcp tasks worker examples/tasks/server.py Nc\<"SP4;_uu_4GRjxL \PRSP R24\PRSPP P 24\PRSPP P 24\PRSPP P 24\P!R4GRjxL K!LL +GRjxL 'giR#;i5i)z'Enter server lifespan and camp forever.Nu7[bold green]✓[/bold green] Starting worker for [cyan]z[/cyan]z Docket: z Backend: z Concurrency: i) _lifespan_managerrrrrrr concurrencyasynciosleep)rserversr run_workerworker..run_worker\s++--- MMI&++V]^  MMJw'7'7'>'>'C'C&DE F MMK(8(8(?(?(C(C'DE F MMOG,<,<,C,C,O,O+PQ RmmD))).*.---sKD,D D,C DD D D, DD) D D) !D) # D,z [yellow]Worker stopped[/yellow]) rrrFileNotFoundErrorrrr&runsource load_serverKeyboardInterruptrr)rconfig_resolved_specr)rr(s& @@rworkerr2<s&!6{!C [[224 5F * JL!+   ,  9:  s# A2B2!BB6CC)N)__doc__r&rtypingrr rich.consolerfastmcp.utilities.clirfastmcp.utilities.loggingrloggerrApp tasks_apprcommandr2r rrr<sb3  70 K  ) LL  7  #L 11r