@Marvin Flow run process exited with non-zero status code -7?

Hello Team!! I’m Jatin - founder of decube.io - unified platform for data observability, catalog and governance. Its a Singapore based startup launched in late-2022. More than 60+ companies are using decube to manage their stack. We are now planning to add support for Prefect which is the reason for joining this community and also wanted to understand use-cases.

GPT 4: https://openai.com/research/gpt-4

allow_failure

does not work as expected I am trying to see how can I continue with a workflow after a task failed all the allowed retries. Sample code:

from prefect import task, flow, get_run_logger, allow_failure
from time import sleep


@task(retries=2, timeout_seconds=3)
def test_1(o, test_retries):
    if test_retries:
        sleep(5)
    else:
        raise IOError('Raising some error')
    return True


@flow(name='test allow_failure')
def run_test_flow():
    result = test_1.submit(True, True)
    result = test_1.submit(result, False, wait_for=allow_failure(result))


if __name__ == "__main__":
    run_test_flow()

I expect this to run

test_1.submit

, fail twice, since the

sleep

is larger than the

timeout_seconds

, and then run the second

test_1.submit

But it does not appear to be working it does not run the second

test_1.submit

@User, @User do you have thoughts on this ?

Is it correct that in order to run tasks concurrently we need to us

submit

? Even if the flow is written in a way that there is no dependencies between tasks?

Question regarding resource management in Prefect 2.x when all tasks are async (i.e. “submitted”) and some tasks are optional, in 🧵

I wonder if there is a recommended way to clear task input cache? Details below. Suppose I've set up and ran a task with

cache_key_fn=task_input_hash

and

cache_expiration=timedelta(days=1)

. Now for some reason I want to clear cache and run the task again (suppose I've changed the logic in a module I'm using from the task). My options (including non-working): 1. Deleting cache files doesn't work. If I run a task after deleting files I get an error. Prefect doesn't check if the file exists before deciding on using cache. 2. Deleting flow runs or task runs does work. But it's not convenient for two reasons: a. I should delete history of runs. b. I have to remember which flow/task run to delete or delete all of them. 3. Adding extra parameter

cache_num

to task should work. I can just change it's value every time I want to avoid using cache. But it generates extra boilerplate code and I have to change flow/task code to change parameter value. It looks like a dirty duct tape to me) 4. Changing data in OrionDB maybe possible, but I'm sure that it's strongly not recommended. And I'd like to avoid it. Maybe there is a better option I don't know about? A perfect solution would be CLI or API with flow/task name as an input parameter.

I'm trying to pass a list as a parameter in the Prefect 2.3 UI, and I can't seem to get the format right. I want to start the run via UI interface. I've used square and curly brackets... single and double quotes, but I continue to get the same error:

ParameterTypeError('Flow run received invalid parameters:\n - part_list: value is not a valid list')

When starting a flow run via UI, what is the correct format that the UI expects when passing a list as a parameter?

I'm just starting with prefect v2 and when I try to run a deployment from Prefect cloud to a local agent running on a Windows server, the agent raises a NotImplementedError.

Hi all, I'm trying out Prefect server and got stuck with this error - any idea what can cause this?