Hi, I am trying to get my PR to pass some tests so it can be reviewed. It is getting hung-up here on, and I don't have access to see what is failing in CircleCI. I think it might be a module error, but I'm confused exactly how modules could properly work before being merged. Any help would be much appreciated, thanks! https://github.com/PrefectHQ/prefect/pull/4943/checks?check_run_id=3510950314

Looking to contribute? Here are some issues to look at • Add Soda Task to our API docs. Created on 2021-08-27 • Docs Issue: API key should be surrounded in double quotes. Created on 2021-07-01 • Ensure Task Library Tasks can be completely configured from the `run` method. Created on 2021-04-08 • Flow registration on custom server gives wrong URL. Created on 2021-02-06 • Add generate_skeleton method to Flow class for testing. Created on 2020-02-27

Looking to contribute? Here are some issues to look at • Docs Issue: API key should be surrounded in double quotes. Created on 2021-07-01 • Cron schedule link in Schedule Docs is Broken. Created on 2021-06-15 • Ensure Task Library Tasks can be completely configured from the `run` method. Created on 2021-04-08 • Having trouble using DatesClock.... Created on 2020-03-19 • Add `client.rest.ApiException` handling to k8s tasks. Created on 2019-05-21

Looking to contribute? Here are some issues to look at • Add Soda Task to our API docs. Created on 2021-08-27 • Cron schedule link in Schedule Docs is Broken. Created on 2021-06-15 • Typo in agent config flag in CLI. Created on 2021-05-27 • Prefect describe flows CLI Command Lacks RunConfig Info . Created on 2021-04-28 • Docs Issue. Created on 2021-04-22

Looking to contribute? Here are some issues to look at • Marshmallow Deprecation Warning. Created on 2021-05-17 • Docs Issue. Created on 2021-04-22 • More Detailed Warning Messaged Around Using Local Storage. Created on 2021-04-09 • Provide Kubernetes Tasks Examples. Created on 2020-08-21 • Add `client.rest.ApiException` handling to k8s tasks. Created on 2019-05-21

wondering if anyone was still planning to review and merge https://github.com/PrefectHQ/prefect/pull/4779

this would be a big help if I could at least use the master version for a project I am working on since the montecarlodata library has a dependency on requests 2.26.0

Looking to contribute? Here are some issues to look at • Found in the Documentation. Created on 2021-08-31 • Typo in agent config flag in CLI. Created on 2021-05-27 • Write an idiom to show using the renameFlowRun task. Created on 2021-03-23 • Provide Kubernetes Tasks Examples. Created on 2020-08-21 • Implement GCSFS Tasks for Prefect. Created on 2019-09-09

Looking to contribute? Here are some issues to look at • Add Soda Task to our API docs. Created on 2021-08-27 • Marshmallow Deprecation Warning. Created on 2021-05-17 • Azure Storage should have the option to use a secret name for the connection string. Created on 2021-04-27 • Write an idiom to show using the renameFlowRun task. Created on 2021-03-23 • Docs unit tests fail if an input argument has newlines. Created on 2019-01-07

Hey folks! I opened this PR to add support for creating dbt Cloud job runs https://github.com/PrefectHQ/prefect/pull/5085 Any feedback is welcome as usual! simple smile

I noticed the Orion pypi release seems to have moved ahead of the

prefect@orion

branch; I'm guessing development on that is still mostly private, what's the timeline for moving to a public branch with changelogs and stuff? playing around with the technical preview is a bit less appealing when I don't have access to the real repository 🙂

Hey folks simple smile I’ve added a new

SodaSparkScan

task. When Github CI/CD process, I get the error reported here. I’m not sure how to solve it. Anyone seen it before?

Hi everyone, I created a pull request to make a small enhancement to @ale’s excellent dbt Cloud task: https://github.com/PrefectHQ/prefect/pull/5273 Enterprise customers have a custom subdomain, and I created an argument to override the default domain. Even though I have read through the contributor guides, this is my first pull request to an open source repo of this size, and I expect there to be some stuff that needs fixing.

Hey folks 😊 👋 I have these two open PRs: • https://github.com/PrefectHQ/prefect/pull/5276 • https://github.com/PrefectHQ/prefect/pull/5278 where some core tests fails on Windows. To me, it is not clear if they are related to the new Prefect tasks introduced by each PR… Is there someone willing to take a look to help me understand how to fix? Thanks! 🙌

Hey folks 👋 I’m working on a Neo4j Cypher task (based on

py2neo

) The code is nearly ready. However, I’m struggling to find the right way to mock a Neo4j server for test purposes. Anyone with prior experience on this topic that is willing to provide some guidance? 😊 🙏

can post a proper issue about this but wanted to run it by folks first: I was chatting with Florian Jetter from Coiled about some performance issues and he mentioned that creating a whole lot of worker clients tends to bog down the scheduler and negatively affect stability. I noticed [this line](https://github.com/PrefectHQ/prefect/blob/master/src/prefect/executors/dask.py#L49) creates a worker client for every single task that's run, I guess to facilitate cancellation...for small flows that's probably fine, but for thousands of workers this seems to create a huge amount of extra overhead for the scheduler. I guess my q's are 1) is it absolutely necessary to create these worker clients for every task? and 2) could it be configurable somehow so that it's possible to opt-out (perhaps at the expense of less reliable task cancellation)? cc @Kevin Kho @Zanie @Chris White

set the channel topic: https://discourse.prefect.io/t/how-to-contribute-to-prefect/352/2

PR to add

kubernetes

authentication to the Hashicorp Vault

VaultSecret

class: https://github.com/PrefectHQ/prefect/pull/5412

Hi! Has anyone tried to implement a new type of prefect agent? I would like to read more about how it works. I don’t know if Prefect Agent is always asking Prefect Server/Cloud to run new flow runs, or if Prefect Server/Cloud sends actively the flow run to an active agent. I’m thinking of a Prefect Webhook Agent that, when there is a new flow run to be executed, invoke a webhook that executes the flow run. For example, in AWS it could be API Gateway running a AWS Lambda function or Fargate task to run the flow run. Do you think it would be possible? Thank you in advance!

we might be interested in taking a stab at finishing https://github.com/PrefectHQ/prefect/pull/3664, @Zanie @Chris White any more thoughts since your reviews in uh late 2020? 😬 tbh I would be happy with just

flow_run_name={today}

or anything along those lines, templating just seems like one way to achieve that

Hi. Where's

prefect-gcp

on your Collection roadmap? Depending on timelines, I might collaborate

Shout out to @davzucky for the first ever PR to one of our Prefect 2.0 Collections (prefect-aws)!

Hey folks 👋 Are there any guidelines to “convert” existing Prefect 1.0 tasks to make them work with Prefect 2.0?

I'm encountering this CI issue today, I didn't have it on Friday:

=========================== short test summary info ============================
ERROR tests/tasks/sodaspark/test_sodaspark_tasks.py - TypeError: argument of ...
ERROR gw2
SKIPPED [1] tests/tasks/asana/test_asana_task.py:8: could not import 'asana': No module named 'asana'
SKIPPED [1] tests/tasks/dbt/__init__.py:3: could not import 'dbt': No module named 'dbt'
SKIPPED [1] tests/tasks/great_expectations/__init__.py:3: could not import 'great_expectations': cannot import name 'contextfilter' from 'jinja2' (/usr/local/lib/python3.8/site-packages/jinja2/__init__.py)

Hey folks, I’ve created another collection! https://alessandrolollo.github.io/prefect-transform/tasks/ cc @Rahul Sompuram

Is squash-on-merge enabled?

Hey folks 👋 A

prefect-dbtcloud

collection is coming soon 🔥

Quick question regarding the Github Action that runs when pushing a change to a Prefect collection repo: the CodeQL step takes ~30 minutes to run each time. Is this expected?

Another question, this time related to Prefect 2.0 in general: looking at some of the available collections maintained by Prefect, I’ve noticed that the async pattern is frequently used. Are there any suggestions/best practices/recommendations regarding the use of the async pattern we should take into account when developing a new collection?

Last question for today (I promise): in Prefect 1.0, the

DbtShellTask

extends the

ShellTask

. With collections in Prefect 2.0, how would one leverage the

prefect-shell

collection to implement a

prefect-dbtcore

collection? 😊