Trevor Campbell
09/07/2021, 6:34 AMСергей Романкевич
09/07/2021, 8:48 AMChhaya Vankhede
09/07/2021, 8:54 AMdeploying-->completed deployment-->returned with exit code -11!
, Attaching the screenshot. What is the exit code -11!
here and how can I solve this issue.Marko Herkaliuk
09/07/2021, 9:18 AMimage=f"project_name/prefect:etl_tools-{sha}"
where sha is a git commit SHA. And I have a registration bash file that call prefect register --project etl -p "/flows/etl/**/**.py"
. Obvious that every commit to repo change SHA, change the image, and registration process bump version for all flows. There is a way to NOT bump all version and exclude image name from the idempotency key?Fabrice Toussaint
09/07/2021, 2:37 PMfrom test.package1 import test1
Would result into "ModuleNotFoundError: No module named 'test'". We are not using Docker images thus on registering we want this to be resolved instead of installing our package somewhere, which we constantly need to update.
The same issue happens here https://github.com/PrefectHQ/prefect/issues/2797 except here they are using Docker images, while we are not.Danielle Dalton
09/07/2021, 2:41 PMUnable to locate credentials
. This happens right after the flow is scheduled and submitted (before any of the tasks can even begin to kick off). We don't think it is related to boto because our EC2 instance is able to read from aws buckets (confirmed by ssh'ing on the instance) via an iam policy attached to the EC2 instance. Unfortunately, running with debug mode didn't produce any more verbose results or a stack trace. We did have to reboot this instance recently after it became unresponsive due to an errant task we had running that consumed too much memory and stalled out. Has anyone experienced this before?Shyam
09/07/2021, 3:14 PMForbiddenError: HTTP Error 403: Forbidden
Marie
09/07/2021, 4:45 PMKathryn Klarich
09/07/2021, 5:48 PMset_schedule_active
is now defaulted to True
(use to be False
i believe) which causes a warning if you register your flow without a schedule in the prefect UI. I was wondering if this was intended as I didn't see anything about this change in the release notes.Luke Orland
09/07/2021, 6:20 PMFailed to find current tenant None in result {'data': {'tenant': [{'id': 'foo-400d-4288-8020-...', 'slug': '<redacted>'}]}}
when it attempts to trigger another flow run via StartFlowRun
.Leon Kozlowski
09/07/2021, 7:14 PM--tag
or --image-tag
override in the build
CLI command?Constantino Schillebeeckx
09/07/2021, 8:21 PMAWS_CREDENTIALS
secret to the Prefect Cloud UI but I"m unclear how exactly to format it, which one of these is it?
{"ACCESS_KEY": "abcdef", "SECRET_ACCESS_KEY": "ghijklmn"}
or
'{"ACCESS_KEY": "abcdef", "SECRET_ACCESS_KEY": "ghijklmn"}'
Also, which "type" should I choose when entering the secret?Frederick Thomas
09/07/2021, 8:44 PMIshavpreet Singh
09/08/2021, 2:24 AMIshavpreet Singh
09/08/2021, 2:24 AMIshavpreet Singh
09/08/2021, 2:25 AMWilliam Burdett
09/08/2021, 6:01 AMMatthias Roels
09/08/2021, 6:48 AMMichael
09/08/2021, 8:21 AMprefect get
(api here) in the Python client? In particular, is there any way to get a Flow ID by it’s name, project, & version as there is with the CLI?Bastian Röhrig
09/08/2021, 8:51 AMcreate_flow_run
and get_task_run_result
to interact with child flows. Now I would love to set some general task properties like state_handlers
and task_run_name
on these. Maybe I am missing something, but I can't figure out how to do this without writing my own wrapper task. Is there a way to do this?Richard Pelgrim
09/08/2021, 8:52 AMFile "/Users/rpelgrim/mambaforge/envs/prefect/lib/python3.9/multiprocessing/popen_spawn_posix.py", line 42, in _launch
prep_data = spawn.get_preparation_data(process_obj._name)
File "/Users/rpelgrim/mambaforge/envs/prefect/lib/python3.9/multiprocessing/spawn.py", line 154, in get_preparation_data
_check_not_importing_main()
File "/Users/rpelgrim/mambaforge/envs/prefect/lib/python3.9/multiprocessing/spawn.py", line 134, in _check_not_importing_main
raise RuntimeError('''
RuntimeError:
An attempt has been made to start a new process before the
current process has finished its bootstrapping phase.
This probably means that you are not using fork to start your
child processes and you have forgotten to use the proper idiom
in the main module:
if __name__ == '__main__':
freeze_support()
...
The "freeze_support()" line can be omitted if the program
is not going to be frozen to produce an executable.
Jeremy Phelps
09/08/2021, 9:14 AMUnexpected error: ValueError('Cell is empty')
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/distributed/protocol/pickle.py", line 49, in dumps
result = pickle.dumps(x, **dump_kwargs)
_pickle.PicklingError: Can't pickle <function create_job at 0x7fabe956fc20>: it's not the same object as tasks.common.create_job
None of my Prefect tasks have been working since it first appeared.
I tried this Stack Overflow answer but it didn't help: https://stackoverflow.com/a/1413299
What causes this error? The create_job
function is always referred to by its full Python import path (tasks.common.create_job
) due to the Stack Overflow answer.Anh Nguyen
09/08/2021, 12:07 PMchicago-joe
09/08/2021, 12:50 PMRichard Hughes
09/08/2021, 1:13 PM06:42:18
ERROR
CloudTaskRunner
Failed to set task state with error: HTTPError('400 Client Error: Bad Request for url: <https://api.prefect.io/graphql>')
Traceback (most recent call last):
File "c:\program files\python37\lib\site-packages\prefect\engine\cloud\task_runner.py", line 128, in call_runner_target_handlers
cache_for=self.task.cache_for,
File "c:\program files\python37\lib\site-packages\prefect\client\client.py", line 1407, in set_task_run_state
version=version,
File "c:\program files\python37\lib\site-packages\prefect\client\client.py", line 281, in graphql
retry_on_api_error=retry_on_api_error,
File "c:\program files\python37\lib\site-packages\prefect\client\client.py", line 237, in post
retry_on_api_error=retry_on_api_error,
File "c:\program files\python37\lib\site-packages\prefect\client\client.py", line 401, in _request
session=session, method=method, url=url, params=params, headers=headers
File "c:\program files\python37\lib\site-packages\prefect\client\client.py", line 333, in _send_request
response.raise_for_status()
File "c:\program files\python37\lib\site-packages\requests\models.py", line 941, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: <https://api.prefect.io/graphql>
Cory Jez
09/08/2021, 1:18 PMPatrick Valencio Leguizamon
09/08/2021, 1:36 PMTraceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/prefect/engine/task_runner.py", line 861, in get_task_run_state
value = prefect.utilities.executors.run_task_with_timeout(
File "/usr/local/lib/python3.8/site-packages/prefect/utilities/executors.py", line 327, in run_task_with_timeout
return task.run(*args, **kwargs) # type: ignore
File "/usr/local/lib/python3.8/site-packages/prefect/tasks/prefect/flow_run.py", line 235, in wait_for_flow_run
for log in watch_flow_run(
File "/usr/local/lib/python3.8/site-packages/prefect/backend/flow_run.py", line 94, in watch_flow_run
flow_run = flow_run.get_latest()
File "/usr/local/lib/python3.8/site-packages/prefect/backend/flow_run.py", line 422, in get_latest
return self.from_flow_run_id(
File "/usr/local/lib/python3.8/site-packages/prefect/backend/flow_run.py", line 568, in from_flow_run_id
flow_run_data = cls._query_for_flow_run(where={"id": {"_eq": flow_run_id}})
File "/usr/local/lib/python3.8/site-packages/prefect/backend/flow_run.py", line 620, in _query_for_flow_run
raise ValueError(
ValueError: No flow runs found while querying for flow runs where {'id': {'_eq': 'b1533b47-859e-46c7-acdc-dbe4976ac3e7'}}
Tim Enders
09/08/2021, 2:36 PMKarim Benjelloun
09/08/2021, 2:47 PMmax_scheduled_runs_per_flow
. Is there a way to configure it via ENV variable? (We use Prefect in docker-compose)Claire Herdeman
09/08/2021, 3:07 PMrun_config
of type ECSRun
, only LocalRun
is supported", the next scheduled flows will continue to fail until I restart the agentClaire Herdeman
09/08/2021, 3:07 PMrun_config
of type ECSRun
, only LocalRun
is supported", the next scheduled flows will continue to fail until I restart the agentDeploying flow run 9f8a7552-90f8-49d2-8091-31db5e7ed1f3 to execution environment...
, but it never says that the deployment has been completedKevin Kho
09/08/2021, 3:11 PMlabels
to avoid this with certainty. There is no guarantee just by using the ECSRun that an ECS Agent will pick it up. So it just seems that both the Local Agent and ECS Agent are polling and the Local Agent happens to pick it up. I think there is a race condition happening here with two agents that can pick up the flow, which is why you see that log. Either way, I would expect adding labels to the flow and agent would fix this.Claire Herdeman
09/08/2021, 3:16 PMKevin Kho
09/08/2021, 3:18 PMClaire Herdeman
09/08/2021, 3:19 PM