We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I had weird results. Scheduling with a 5s interval resulted in this:
1437117604.32 :calling update() thread: MainProcess - Thread-10 1437117605.6 :calling update() thread: MainProcess - Thread-14 1437117609.35 :calling update() thread: MainProcess - Thread-10 1437117610.62 :calling update() thread: MainProcess - Thread-14 1437117614.32 :calling update() thread: MainProcess - Thread-13 1437117615.61 :calling update() thread: MainProcess - Thread-17 1437117619.32 :calling update() thread: MainProcess - Thread-10
Solution is to use the monkey patch from gevent by putting this above all other imports in your app.py:
from gevent import monkey monkey.patch_all()
The text was updated successfully, but these errors were encountered:
@piejanssens
Have you tried GeventScheduler? It might solve your issue too.
The following code is just a guess, I have not tried running it.
from apscheduler.schedulers.gevent import GeventScheduler from flask_apscheduler import APScheduler sched = APScheduler(GeventScheduler())
Cheers!
Sorry, something went wrong.
That's even better! The monkey patch caused this ugly thing: http://stackoverflow.com/questions/8774958/keyerror-in-module-threading-after-a-successful-py-test-run
No branches or pull requests
I had weird results. Scheduling with a 5s interval resulted in this:
Solution is to use the monkey patch from gevent by putting this above all other imports in your app.py:
The text was updated successfully, but these errors were encountered: