s

    Sven Teresniak

    2 years ago
    2020-07-20T12:09:58.139Z {"message":"Variable \"$input\" got invalid value { flow_id: \"80de1b39-fed7-47ab-a5a5-fc22ac6f87d2\", idempotency_key: \"e82df5c1-d197-46f1-9bb1-f18f9335e0f8\" }; Field \"idempotency_key\" is not defined by type create_flow_run_input.","locations":[{"line":1,"column":10}],"extensions":{"code":"INTERNAL_SERVER_ERROR"}}
    Is this a bug? Every component of my Prefect Cluster (v0.12.4) is running in K8S but its a static setup with every component is one container and everything together in one pod (so everything can communicate using localhost). I have a Dask-Worker pod running and all other flows (not calling other flows) this far are working.
    m

    Matt Wong-Kemp

    2 years ago
    suspect that either server (which I'm guessing you're running, not cloud?) doesn't accept the idempotency key parameter that was added as default in
    FlowRunTask
    , or you've got a version mismatch? This works OK in cloud.
    s

    Sven Teresniak

    2 years ago
    I do not use the Cloud. All server components are stock Docker images taken from dockerhub,
    prefecthq/*
    , e.g.
    prefecthq/server:0.12.4
    for graphql and prefect scheduler,
    prefecthq/apollo:0.12.4
    for apollo,
    prefecthq/ui:0.12.4
    for ui. For Agent, for the Dask Worker and the Dask Scheduler (master) I have a own image build. Thats because I need some dependencies (Presto, Spark, etc.). But this image is simple and not much more than
    pip install --no-cache-dir "prefect[$PREFECT_EXTRAS]==$PREFECT_VERSION"
    in a
    python:3
    base image. Of course the Version matches and is
    0.12.4
    , too
    I checked the source code for v0.12.4 on github. I found a schema definition for this RPC here: https://github.com/PrefectHQ/prefect/blob/0.12.4/server/src/prefect_server/graphql/schema/schema.graphql#L114 There is no key
    idempotency_key
    in that structure. And thats exactly what the errormesage said. 😕
    m

    Matt Wong-Kemp

    2 years ago
    suspect this is a bug in the server schema definitions then
    s

    Sven Teresniak

    2 years ago
    I will create an issue.