Hello Prefect engineers. Experiencing what might b...
# ask-communityc
Chris L.
08/31/2022, 9:59 AMHello Prefect engineers. Experiencing what might be a regression bug from the new 2.3.0 release. This error does not occur in Prefect 2.2.0. Nothing about the flow or deployment was changed between the Prefect update. Unfortunately, I am unable to create a minimally reproducible example without revealing our company code...but happy to share it with a Prefect engineer over a call. Thanks in advance! However, been using the new arguments for deployments in our CICD pipeline and it's been working great 🙏
🙏 1
✅ 1
j
Jeff Hale
08/31/2022, 11:57 AMThank you, Chris. Are you able to open as an issue with as much description as you can give (even without MRE)?
Glad the new args are working great!
c
Chris L.
08/31/2022, 11:59 AMLooks like somebody beat me to it: https://github.com/PrefectHQ/prefect/issues/6641
Chris L.
08/31/2022, 12:00 PM@Jeff Hale Wondering where I can find the community guidelines on when and where to post! With disqus, slack, and github issues, should I post these potential bugs on GitHub issues as default from now on? Would be great to clarify the protocols here. Many thanks!
j
Jeff Hale
08/31/2022, 12:05 PMGood question, Chris!
If it might be a bug, good to check GitHub and see if it someone has identified it.
If you aren’t sure if it’s a bug, great to post here and if someone can resolve, that’s great. If no one can, then great to make an issue in GitHub as a bug.
Discourse is designed primarily for recipes to do show specific use cases.
It’s a lot of support channels and there can be a bit of overlap - but each has a purpose. 🙂
Just wish we could fit more in the Slack channel description - ran up against the character limit today. 😂
💯 1
s
Sander
08/31/2022, 1:14 PMI also ran into the bug with the minimal code provided in the bug report. Looking forward to the fix!