also, it might be easier to just say that flow names must be unique within a repo rather than asking users to modify json files? in addition, maybe entries in the .history directory should be excluded from the output of

prefect deploy

?

I made a copy of

104/flows.py

, named it

104/flows_v2.py

, made some changes, ran locally with

python 104/flows_v2.py

and it ran successfully. But when i try to do a quick run from deployments (after having set that flow up as a deployment) I get below error. What could be the issue?

Flow could not be retrieved from deployment.
Traceback (most recent call last):
  File "<frozen importlib._bootstrap_external>", line 879, in exec_module
  File "<frozen importlib._bootstrap_external>", line 1016, in get_code
  File "<frozen importlib._bootstrap_external>", line 1073, in get_data
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpdflqaa6sprefect/pacc-2023/.history/104/flows_v2_20230718160512.py'

here's another question for later. when i add a print statement to the code, it shows up in the terminal but nowhere to be found in the Prefect UI for the given flow run. Just wondering I it is possible to view print statements in the UI? or maybe I'm overlooking it?

last Q promised 🙂 so I added a parameter to a function, redeployed it with

prefect deploy

, but can't see any parameter in the UI. If you could walk us through the steps I may be missing that would be great.

for the docker part, could you give us the docker pull command? I'm not too familiar with Docker. I checked out this page

<https://docs.prefect.io/2.10.21/concepts/infrastructure/#standard-python>

but not sure how that info is to be used with

docker pull prefecthq/prefect

update, got it:

docker pull prefecthq/prefect:2-latest

❄️ Ice breaker (in Slack 🧵) : What’s your favorite hot drink?

Does the Worker need to have access to all Pytyon libs included in the Flow Code?

on the "why don't we push your code" question: generally speaking, most of our users deploy via CI when they choose to push code to version control, so that's a big reason we don't assume responsibility for pushing your code by default

In the slides, it says scheduled flows go to work pools. Where in side 144 is the scheduling happening? What part of the system reacts to failures? Is checkpointing possible in this system?

Hey @Jeff Hale or @Nate can you answer a question in room 3 when you’re free?

We’ll regroup at 2:05pm ET

Install requirements documentation 💯

need to drop. Will catch up from recording. Nice to meet you all 🙂

If you really want to push your flow code to GitHub as part of your deployment creation process:

push:
    - prefect.deployments.steps.run_shell_script:
        id: git-push
        script: git push origin
        stream_output: false

We’ll get back together at 3:10pm. Feel free to take a stretch and coffee break before then. 🙂

Different task runners documentation

If you are using Prefect Cloud and use AWS ECR or GCP GCR (or soon Azure ACI) user and want to run your deployments and NOT have your own worker, you can use a Push work pool. Push work pools are in beta and new as of last Thurs.. GCR docs are out and ECR docs should be out on Thurs.

API Rate Limits: https://docs.prefect.io/2.10.21/cloud/rate-limits/

Modifying the poll settings of a worker

Push to GCP Cloud Run is amazing!

Yes, please share the GH action @Jeff Hale

Here are great examples of Prefect usescases in the recipe repo!

Please a take moment: https://forms.gle/7FaH6Dn8aXP8j8GC8

🚀 Thank you for all your hard work! Stay in touch in Slack and feel free to connect on LinkedIn! https://www.linkedin.com/in/-jeffhale/

Day 2 Recording; https://us06web.zoom.us/rec/share/D3Lkco7JeztvKlxXZGytJeAgGfD1XBzbgmEtl0sS86ZKM2R9W-PnOGnhS1qfx0VC.f2_M-COqvIHx5DEq Passcode: x?7m9QAJ

archived the channel