Hey folks 👋 I’m getting these warnings while running tests on a new collection I’m working on

../../../.pyenv/versions/3.10.9/envs/prefect-huggingface/lib/python3.10/site-packages/prefect/testing/standard_test_suites/task_runners.py:155
  /Users/alessandro.lollo/.pyenv/versions/3.10.9/envs/prefect-huggingface/lib/python3.10/site-packages/prefect/testing/standard_test_suites/task_runners.py:155: PytestUnknownMarkWarning: Unknown pytest.mark.flaky - is this a typo?  You can register custom marks to avoid this warning - for details, see <https://docs.pytest.org/en/stable/how-to/mark.html>
    @pytest.mark.flaky(max_runs=4)  # Threads do not consistently yield

Not sure what’s the issue here, anyone experiencing this?

tests/test_tasks.py::test_get_inference_result_fails
  /Users/alessandro.lollo/.pyenv/versions/3.10.9/envs/prefect-huggingface/lib/python3.10/site-packages/prefect/orion/database/migrations/versions/sqlite/2022_04_25_135207_b75d279ba985_replace_version_with_checksum.py:102: RemovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings.  Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: <https://sqlalche.me/e/b8d9>)
    meta_data = sa.MetaData(bind=connection)

tests/test_tasks.py::test_get_inference_result_fails
  /Users/alessandro.lollo/.pyenv/versions/3.10.9/lib/python3.10/contextlib.py:142: SAWarning: Skipped unsupported reflection of expression-based index ix_flow_run__coalesce_start_time_expected_start_time_desc
    next(self.gen)

tests/test_tasks.py::test_get_inference_result_fails
  /Users/alessandro.lollo/.pyenv/versions/3.10.9/lib/python3.10/contextlib.py:142: SAWarning: Skipped unsupported reflection of expression-based index ix_flow_run__coalesce_start_time_expected_start_time_asc
    next(self.gen)

-- Docs: <https://docs.pytest.org/en/stable/how-to/capture-warnings.html>

These seems to be related to SQLAlchemy 2.0. However, in my environment I have

prefect==2.7.11

and

sqlalchemy==1.4.46

Anyone experiencing the same? Is this something I should be worried about? 😅

Hi everyone, I am currently trying to setup an ECS agent with aws. However, the task seems to stop and exit with the error

essential container in task exited

. The prefect ecs agent also does not appear in the UI. I have been able to start the ECS agent locally, but am unable to start it through aws. Another thing to mention is that when I try to add the logConfiguration to try to see what could be going wrong with the service it will give me an error of

ResourceInitializationError: failed to validate logger args: : signal: killed

. I’ve double checked with devOps that the IAM roles and network configurations should be correct too. Any ideas on how to debug this or why this is happening?

@Marvin What does this warning mean?

<frozen runpy>:128: RuntimeWarning: 'prefect.engine' found in sys.modules after import of package 'prefect', but prior to execution of 'prefect.engine'; this may result in unpredictable behaviour

hi! - I'm trying to sent environment variables for a deployment that will run in a docker image. I am using this example, but

MY_SECRET_KEY

is rendering as a string -

{{ prefect.secret('MY_SECRET_KEY') }}

. Is it possible to get the rendered prefect secret in a deployment?

deployment = Deployment.build_from_flow(
    flow=my_flow,
    name="my-flow-deployment",
    infrastructure=docker_infrastructure,
    work_pool_name="my-docker-pool",
    job_variables={
        "env": {
            "MY_SECRET_KEY": "{{ prefect.secret('MY_SECRET_KEY') }}"
        }
    }
)

Hi, is there a way to pull an image from AWS ECR and run the image? the only one I found is to pull from Docker server which doesn’t apply to my case.

@Marvin, my flows are getting stuck at pending state, can I somehow manually create the state from db so that it can be picked up by workers ?

Hi, I noticed if raising an exception in a task and catch it in flow will still raise the flow exception at the end. Is there way to avoid raise it again? Please see in thread for code example.

Hey guys, has anyone considered using Celery as the executor for prefect tasks? ie, A part of the workflow have CPU intensive tasks and need more level of concurrent distribution, which can’t be achieved with prefect agents. So Prefect agent will submit the tasks to a message queue with necessary parameters and Celery will manage such executions. Open for Triage!

I am looking for a comparison with Mage. I read a comparison that is really favourable to Mage with respect to Prefect and I would like to read an opposite one 😄

i have created a docker worker on a server and trying to run my private docker image, but this error occues as it could not fetch docker image due to docker not able to login to registry.