Andrew Lane
03/17/2022, 5:01 PMretry_delay
attribute of Task
objects. Based on the description of state signals here, I’d expect to be able to raise signals.RETRY()
and have the task wait retry_delay
before the task is run again. However, the retries appear to be being carried out immediately. Can someone explain where I’m going wrong in the wait_until_success
task in the trailing code snippet?Nico Neumann
03/17/2022, 5:03 PMflow.schedule = Schedule(clocks=[CronClock("* * * * *")])
which works fine and later want to add another schedule or delete the current one. My idea is to use GraphQL with the set_flow_group_schedule
and delete_flow_group_schedule
methods.Chris Reuter
03/17/2022, 5:50 PMMarc Lipoff
03/17/2022, 6:11 PMMarvin
03/17/2022, 6:55 PMMarvin
03/17/2022, 6:56 PMStéphan Taljaard
03/17/2022, 6:56 PMcrontab * * * * *
😆Stéphan Taljaard
03/17/2022, 7:16 PMtask
or flow
(i.e. subflows)?alex
03/17/2022, 7:35 PMx slots
used in the late runs section, even though the flow does not have any tags associated with the concurrency limit (I have some other flows that do). Any ideas on how I can resolve this issue?Stéphan Taljaard
03/17/2022, 7:55 PMConstantino Schillebeeckx
03/17/2022, 7:56 PM{parameters: {_contains: {"foo": "bar"}},
but the syntax isn't quite right, I get the error
Syntax Error: Expected Name, found String "date".
can someone help?Philip MacMenamin
03/17/2022, 7:58 PMcommand
which is a return from a prev Task?
eg
with Flow(name='t') as f:
a = task_a()
b = shell_task(a)
Serge Tarkovski
03/17/2022, 8:42 PM$ python flow1.py
Traceback (most recent call last):
File "/home/tarkovskyi/miniconda3/envs/prefect_exp/lib/python3.10/site-packages/prefect/client.py", line 257, in api_healthcheck
await self._client.get("/health")
File "/home/tarkovskyi/miniconda3/envs/prefect_exp/lib/python3.10/site-packages/prefect/utilities/httpx.py", line 102, in get
return await self.request(
File "/home/tarkovskyi/miniconda3/envs/prefect_exp/lib/python3.10/site-packages/prefect/utilities/httpx.py", line 47, in request
request = self.build_request(
TypeError: BaseClient.build_request() got an unexpected keyword argument 'extensions'
Jared Robbins
03/17/2022, 9:01 PMJared Robbins
03/17/2022, 9:16 PMJacqueline Riley Garrahan
03/17/2022, 9:19 PMSerge Tarkovski
03/17/2022, 10:02 PMDarshan
03/17/2022, 10:40 PMBrad
03/18/2022, 3:07 AMlialzm
03/18/2022, 6:56 AMAaron Ash
03/18/2022, 7:56 AMexecutor
and `run_config`s of the flows somehow?Aaron Ash
03/18/2022, 7:58 AMKubernetesRun()
environmentsAaron Ash
03/18/2022, 7:59 AMVladimir Bolshakov
03/18/2022, 8:23 AMprovide_task_policy
/ provide_flow_policy
). So my question is about orchestration settings that will be released in the future. Is custom orchestration policies will be parameters of API requests to set state of task/flow? Or orchestration concepts and APIs will be seriously changed in the near future? How orchestration policies will be serialized/deserialized between server and agent’s engines?Clovis
03/18/2022, 10:24 AMFailed
status but, I don't know why, prefect considers the task as successful (cf. my screenshot in attachment).
It's a blocking point from my point of view as it prevents me from relying on prefect and therefore forces me to double-check each time with Airbyte.
Maybe this issue comes from my code but I don't see why ?
sync_airbyte_connection = AirbyteConnectionTask(
max_retries=3, retry_delay=timedelta(seconds=10), timeout=timedelta(minutes=30),
)
with Flow("my flow", run_config=UniversalRun()) as flow:
airbyte_sync = sync_airbyte_connection(
<connection_infos>,
)
[...]
flow.set_reference_tasks([
airbyte_sync
])
Malthe Karbo
03/18/2022, 1:28 PMVadym Dytyniak
03/18/2022, 2:46 PMAdam Roderick
03/18/2022, 3:41 PMprefect.exceptions.ClientError: [{'path': ['secret_value'], 'message': 'An unknown error occurred.', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}]
Chris Reuter
03/18/2022, 4:32 PMAram Panasenco
03/18/2022, 5:16 PM