-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
copr-pypi has stopped building packages #3056
Comments
FrostyX
added a commit
to FrostyX/copr
that referenced
this issue
Mar 6, 2024
Fix fedora-copr#3056 We are seeing the following error in the logs: RuntimeError: Working outside of application context. This typically means that you attempted to use functionality that needed the current application. To solve this, set up an application context with app.app_context(). See the documentation for more information.
FrostyX
added a commit
to FrostyX/copr
that referenced
this issue
Mar 7, 2024
Fix fedora-copr#3056 We are seeing the following error in the logs: RuntimeError: Working outside of application context. This typically means that you attempted to use functionality that needed the current application. To solve this, set up an application context with app.app_context(). See the documentation for more information.
praiskup
pushed a commit
that referenced
this issue
Mar 10, 2024
Fix #3056 We are seeing the following error in the logs: RuntimeError: Working outside of application context. This typically means that you attempted to use functionality that needed the current application. To solve this, set up an application context with app.app_context(). See the documentation for more information.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
looks like something died; no packages have been built since 2023-11-28, 17:07 UTC
timewise, this overlaps with #2964 / https://pagure.io/fedora-infrastructure/issue/11648
if this should be brought up somewhere else then please point me in the right direction 👍 and thx for the service!
The text was updated successfully, but these errors were encountered: