[Bug] An activity method with an annotated `self` receives its arguments without their types
I maintainer di solito rispondono entro 1 giorno
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Package: temporalio 1.35.0, the latest release, and main (d488ff5).
What happens
An activity defined as a method, async def m(self, loc: Loc), receives loc as a Loc. The same method with an annotated receiver, such as self: Self in a module with from __future__ import annotations, receives loc as a plain dict.
_type_hints_from_func in temporalio/common.py skips the first parameter only when it is named self and is unannotated, or its annotation's text is typing.Self:
if (
index == 0
and value.name == "self"
and (
value.annotation is inspect.Parameter.empty
or str(value.annotation) == "typing.Self"
)
):
continue
Under postponed annotations the text is Self, so arg_types gets an entry for the receiver. The Worker then has two types for one argument, and worker/_activity.py falls back to decoding without types (arg_types is not None and len(arg_types) != len(start.input)). The same holds for self: T with a TypeVar bound to the class, self: "Svc", and typing_extensions.Self on Python 3.10. It affects workflow.execute_activity_method and anything else that runs a registered bound method.
Reproduction
One file. It uses a local dev server (temporal CLI on PATH) and exits 1 when the method annotated self: Self receives a dict.
"""An activity method whose `self` is annotated receives its other arguments without their types.
Exits 1 when the method annotated `self: Self` receives a dict instead of a `Loc`.
"""
from __future__ import annotations
import asyncio
import dataclasses
import shutil
import sys
import uuid
from datetime import timedelta
from typing import Self
from temporalio import activity, workflow
from temporalio.testing import WorkflowEnvironment
from temporalio.worker import UnsandboxedWorkflowRunner, Worker
@dataclasses.dataclass
class Loc:
city: str
class Svc:
@activity.defn
async def plain(self, loc: Loc) -> str:
return type(loc).__name__
@activity.defn
async def annotated(self: Self, loc: Loc) -> str:
return type(loc).__name__
@workflow.defn
class LocWorkflow:
@workflow.run
async def run(self) -> list[str]:
timeout = timedelta(seconds=10)
return [
await workflow.execute_activity_method(
Svc.plain, Loc("Rome"), start_to_close_timeout=timeout
),
await workflow.execute_activity_method(
Svc.annotated, Loc("Rome"), start_to_close_timeout=timeout
),
]
async def main() -> None:
svc = Svc()
async with await WorkflowEnvironment.start_local(
dev_server_existing_path=shutil.which("temporal")
) as env:
async with Worker(
env.client,
task_queue="tq",
workflows=[LocWorkflow],
activities=[svc.plain, svc.annotated],
workflow_runner=UnsandboxedWorkflowRunner(),
):
plain, annotated = await env.client.execute_workflow(
LocWorkflow.run, id=str(uuid.uuid4()), task_queue="tq"
)
print(f"plain(self, loc: Loc) received: {plain}")
print(f"annotated(self: Self, loc: Loc) received: {annotated}")
sys.exit(0 if annotated == "Loc" else 1)
if __name__ == "__main__":
asyncio.run(main())
Output:
Python 3.13.16 temporalio 1.35.0
$ python annotated_self.py
plain(self, loc: Loc) received: Loc
annotated(self: Self, loc: Loc) received: dict
exit 1
Expected
The Worker registers the method bound to an instance, which supplies self however it is annotated. So annotated should receive a Loc, as plain does.
Proposed fix
When the first parameter is named self, skip it whatever its annotation, as for an unannotated self.
Found while reviewing temporalio/ai-integrations#206, which builds agent tools from activity methods.
- Lingua principale
- Python
- Stelle
- 1.2k
- Fork
- 285
- Merge medio
- 1g 23h
- PR unite (30g)
- 89
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di temporalio/sdk-python
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 18/100
temporalio/sdk-python#2080 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug] Sandboxed datetime hints can fail decoding and drop signalsForse già presa @VegetarianOrc l’ha presa oggi. Aperta
temporalio/sdk-python#2072 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug] TaskGroup cancellation of mixed Temporal operations can break replayForse già presa @VegetarianOrc l’ha presa oggi. Aperta
temporalio/sdk-python#2069 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
sdk-python
Difficoltà 4/5 3-5 giorni Idoneità per principianti 22/100
temporalio/sdk-python#2067 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug] lambda_worker otel.apply_defaults leaks a span exporter thread and gRPC channel on every warm invocationForse già presa @avanish-garg l’ha presa 5 giorni fa. Apertabug sdk-python
Difficoltà 4/5 1-2 giorni Idoneità per principianti 30/100
temporalio/sdk-python#2040 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di temporalio/sdk-python
Issue simili
-
DBFS append mode silently overwrites existing filesForse già presa @IlyaKhalafi l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
fsspec/filesystem_spec#2429 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Retrieval rerank fallback statistics stay zero after provider failureForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
volcengine/OpenViking#7014 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
fedora-copr/copr#4600 ·
I maintainer di solito rispondono entro 2 giorni
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
ansys/pydpf-core#3620 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno