hey @Marvin; what's the easiest way to set HTTP header parameters for the prefect client when I'm calling a flow as if I were calling a function? We're running a prefect deployment on prem, so in order to schedule any flow runs to that deplyoment, all API requests need the HTTP headers to have a special field set, and I don't see any easy way to do that in the documentation

Has anyone run into this js error?

TypeError: crypto.randomUUID is not a function

I've installed prefect on a vm (ubuntu 22.04). Then I do the following: prefect config set PREFECT_API_URL=http://<my externalip>:4200/api prefect server start --host 0.0.0.0 And I've tried with prefect 2.10.14 and 2.10.15. I'm keep getting this error in both Edge and Chrome - and it breaks the page.

hi all, I'm trying to create a Prefect deployment from a custom Docker image and get this error when running it

botocore.exceptions.ClientError: An error occurred (AccessDenied) when calling the ListObjectsV2 operation: Access Denied

. It is uploading the file correctly, and even the image is building correctly but it is failing when I run the flow from the UI. From what I understand in the error message, when running the flow from the docker image, it can't access S3 to read the code. Here are a few more details: • Storage block --> S3. It uploads correctly • Docker image --> Custom image retrieved from ECR • Code --> It is the same code I use in other non-dockerized deployment. • The EC2 instances for the Prefect Agent, Prefect Server and S3 Bucket are all in the same AWS account • The EC2 instance for the PrefectAgent has S3 full access (should the EC2 instance for the Prefect Server also have full S3 access?) I leave in the image below with the full error I get in the Prefect UI and in the Agent's terminal. I saw a similar

AccessDenied

error in this channel when trying to upload the code to S3 but this seems different. The problem is when the flow is running in docker and can't retrieve the code. Any ideas why this could be? Thanks a lot for your help!

Hello experts~~ I'm using prefect 1.0! I say thank you so much for always answering me quickly before asking a question.💙 When the flow, which was well executed for small-scale data, tried to receive a large amount of data from the our web server as parameter, the following client error was encountered. I downloaded the log of the flow from prefect cloud UI and attached it.(logs.json) and wirte here, too.

Failed to set task state with error: ClientError([{'path': ['set_task_run_states'], 'message': 'State payload is too large.', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}])
Traceback (most recent call last):
  File "/home/da/enviorments/bdi/lib/python3.10/site-packages/prefect/engine/cloud/task_runner.py", line 91, in call_runner_target_handlers
    state = self.client.set_task_run_state(
  File "/home/da/enviorments/bdi/lib/python3.10/site-packages/prefect/client/client.py", line 1604, in set_task_run_state
    result = self.graphql(
  File "/home/da/enviorments/bdi/lib/python3.10/site-packages/prefect/client/client.py", line 464, in graphql
    raise ClientError(result["errors"])
prefect.exceptions.ClientError: [{'path': ['set_task_run_states'], 'message': 'State payload is too large.', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}]

Actually, it wasn't the first time that task failed, and before that, it ran for about 3 minutes and then informed me that no heartbeat detected. (

No heartbeat detected from the remote task; marking the run as failed.

) So, the solution I found was configure heartbeats to use threads instead of processes and worte about the flow run config in the .py file. When I did that, the task of receiving parameters was performed longer than the first... (1st try : 3 minutes running -> 2nd try: 12 minutes running) Although the task was executed for a longer time, it was still a failure. 😞 How can i solve this problem? What's the problem of my engineering? This flow may have been written in the wrong way, so I also wrote the flow code below..

import...
from prefect.run_configs import UniversalRun

def custom_function():
    '''some works'''
    return output 

@task
def parsing_waveforms(download):
    processing_target = download    
    '''some works by using above custom_function'''
    
with Flow('flow_waveforms')as flow:
    heir = Parameter('download')
    task1 = parsing_waveforms(download=heir)

flow.run_config = UniversalRun(env={'PREFECT__CLOUD__HEARTBEAT_MODE'}:'thread')
flow.register(project_name='data_factory')

I keep encountering the following Runtime error:

RuntimeError: Orion requires sqlite >= 3.24.0 but we found version 3.7.17

how do I go about fixing this error

Hi all, what goes into "An Azure storage bucket path" when creating an Azure storage block? A couple of things I tried lead to "Container does not exist" errors from Azure. This is latest build of Prefect 2.0.2 with today's fix for .prefectignore included. (Yeah, I know... noob)

After installed Prefect on Windows10, I got a error message when run 'prefect version'

Version:             2.0b12
API version:         0.7.0
Python version:      3.9.1
Git commit:          18d44c8c
Built:               Fri, Jul 22, 2022 4:23 PM
OS/Arch:             win32/AMD64
Profile:             default
Server type:         <client error>

Hey you all, I’m new to Prefect and I’ve managed set up a dev & deployment process for my team to start working with Prefect development in production, however I’m still trying to find a good solution to manage the Agents and automate that part of the deployment as well. The current deployment workflow (done in Github Actions) looks roughly like this: • Build & Push new Docker image (dev/prod) whenever project requirements in the related branch are changed • Build & register flows to Prefect Cloud (dev/prod project) whenever flow files (or default build configs) in the related branch are changed We currently have two Docker Agents running in an AWS EC2 instance. Each agent has its own environment variables and currently, if new env variables need to be added, this is my process: • SSH to EC2 • Start new agents with new environment variables e.g.

Nohup prefect agent docker start --label dev --env VAR1=<variable1> --env VAR2=<variable2> &

• Get the PIDs for the old agents with old environment variables

ps -ef | grep prefect

• Kill the old agents

kill <PID>

As this is not a very smooth approach, I’d like to hear how others have approached automating the Agent part when setting up CI processes. Any tips?

Is there a way to pass an existing dask client to Prefect (instead of pass a DaskExecutor which launches a cluster on its own) - asking in particular to be able to run coiled cluster commands to launch cluster, register some worker plugins, trigger a scale, then pass it to Prefect for execution.

Do you know where this error comes from?