Hi, can anyone help/explain to me what is needed to complete the last two check marks on my PR https://github.com/PrefectHQ/prefect/pull/5788

Hello all, I have just created my first opensource merge request and it's for Prefect !! https://github.com/PrefectHQ/prefect/pull/5846 Just a really tiny fix, but it feels good =]

Hi - I need a possibility to run multiple snowflake queries in one session and sometimes in a transaction I can probably easily add this - add parameter in SnowflakeQuery class: • transaction: bool = false • change query to queries that takes list of strings with queries - but this is not good for backward compatibility... I can maybe change that query is str or List[str]. Or maybe add another parameter: queries that will be taken into account when query is None.. or something But please let me know if this makes sense for you and if it has a chance to me merged when finished

Hi I ran the failed test here locally, successfully. Can someone please help me fix what's broken / have a look?

Hi, I have just created pull request with my proposal that allows to run multiple snowflake queries in one sessions and in a transaction: Maybe someone will be interested 🙂 https://github.com/PrefectHQ/prefect-snowflake/pull/9

Hi, I have seen Prefect does not use pipenv nor poetry. How do you virtualize the environments when working directly with pip? Do you use virtualenv to create multiple python distributions and then work with plain pip?

Hey folks 👋 If you are on Prefect 2.0 and you use Stitch to replicate your data, then you might find this new Prefect collection helpful!

Hey folks 👋 I’m currently working on an integration between Prefect 2.0 and MetricFlow. For testing purposes, I use

pyfakefs

, so that I can mock files on the file system. However, it seems something is not working as expected. It seems related to

pyfakefs

and

prefect

, but I’m not 100% sure. Anyone able to help me figuring out what’s going on? 😊 Stack trace in the thread! Thanks! 🙌

Hey folk 👋 Here’s the first release of the integration between Prefect 2.0 and MetricFlow 🎉

Hey folks 👋 I have a bunch of Prefect collections that might be useful to the whole community once people migrate to Prefect 2.0. How can I make my collections listed on the Prefect Collections landing page? 😊

Is Prefect 2.0 still using pip or poetry?

Hi, why was this closed ? https://github.com/PrefectHQ/prefect/pull/6009

Hi, I have just created https://github.com/PrefectHQ/prefect-snowflake/pull/29 that effectively enables running more than 4-5 concurrent snowflake queries

Any chance we can get a release of 1.3.x?

Hey folks 👋 I want to build a new collection with a task that execute a CLI command. Should I build the new collection by extending the

prefect-shell

one, or should I stark from scratch? If I extend

prefect-shell

, should I create my own task and use the

shell_run_command

inside my task? Quick example:

from prefect_shell import shell_run_command

@task 
def my_shell_task(command: str):
    return shell_run_command(command=command)

Would this work if I call

my_shell_task

in a flow?

Anyone willing to build an integration with Hex?? They’ve just announced v1 of their brand new public APIs. I’m definitely available to help!

Hi! I’m really curious if anyone in this group would be affected by the breaking change presented in https://github.com/PrefectHQ/prefect/pull/6926 tldr; are you calling

State.result()

in an async context? (does not apply to

Future.result()

)

Hey folks 👋 Cross posting from the Soda community --> https://soda-community.slack.com/archives/C02PC0WPRNC/p1664464535579609 Spoiler: Soda released a new Prefect collection that you can use to run data quality checks on your data! Thanks to Soda to provide me the opportunity to collaborate with them on this new collection! 🚀 🚀

Just published a new collection that allows monitoring the prefect server using opentelemetry. This is an initial version that publishes trace only at the moment on the server. https://pypi.org/project/prefect-opentelemetry/ github project https://github.com/davzucky/prefect-opentelemetry The next steps are • Add metrics • Enable Agent to support OTEL • Create a block for OTEL • Create a custom task that would generate traces on the run (Would be nice to be able o add plugins) on flow or task to do that. Please share your feedback

👋 You may have noticed I’m working on result configuration. There’s a bit more wiring up to do but the documentation is in a near-final form. Check out the preview at https://deploy-preview-6908--prefect-orion.netlify.app/concepts/results/ — feel free to share any feedback!

Happy Hacktoberfest! 🍻 Cross-posting that OpenMetadata and Airbyte are celebrating by giving 💰 and swag for contributing connectors. Specifically for OpenMetadata, if you are interested in helping contribute, QA or build examples/tutorials for the integration, feel free to ping me. Thanks to all contributors! 💙

Hi there, I have created a redis collection and am looking for the steps needed to become a part of the official prefect packages: https://github.com/C4IROcean/prefect-redis @alex - @Anna Geller mentioned you could help with this? https://prefect-community.slack.com/archives/CL09KU1K7/p1665169933380519?thread_ts=1665131857.359879&cid=CL09KU1K7

Hey folks 👋 Recently I started working on a new integration. I’ve started from the

prefect-collection-template

as usual. From time to time, I’m seeing the failures on the Github Action named “_Template Synchronization_”. The reported error is

Run tibdex/github-app-token@v1
  with:
    github_api_url: <https://api.github.com>
    repository: AlessandroLollo/prefect-sifflet
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.9.15/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.9.15/x64/lib/pkgconfig
    Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.9.15/x64
    Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.9.15/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.9.15/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.9.15/x64/lib
Error: Error: Input required and not supplied: app_id

Anyone knows how to solve it? Thanks! 🙌

Been working on an integration between Sifflet and Prefect. Not released yet, but you can find the code here. Feedbacks more than welcome as usual! 🙌 cc @Wajdi

Hey everyone 👋 I'm working on a general purpose integration between Google Sheets and Prefect. I've a first version ready and would like to publish it. I've read from the docs that I have to open a PR to the Prefect repo with a new yaml file under the

collections/catalog

path. My question is: how can I publish it on PyPi? Is there any automation? Something related to Github action? Thanks! 😄

Hello, what's the status on the prefect-twilio project? Has not been any activity for the past 7 months...and PYPI does not have a package which can be installed via pip

Hey folks 👋 I’m working on a new integration between Prefect and Huggingface 🚀 Here’s the code! Right now it only support Inference API, but I’m planning to extend it to support also Inference Endpoints

Hi, Maybe not smart questions but I didn't see them quick scrolling in the channel... how does one start when wanting to contribute? Is there a list of on-going projects where one can do PRs? Is there a list with prioritized projects based on demand of feature requests or something like that? Is it more useful contributing with a new Block, or with something else? Thanks!

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? 😅

Hey folks 👋, I am excited to announce that the integration between Prefect and Sifflet has been released: https://github.com/Siffletapp/prefect-sifflet . Sifflet is a full data stack observability; this integration is the first of many steps toward prefect data pipeline observability. I want to take a moment and thank @ale for leading this integration; it was a real plaisir working with him. We look forward to continuing our collaboration with you and other members of the open-source community.