Skip to content
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

line 14 in tasks.py in the demo app makes assumptions about the db which may not be valid for an async task #1

Open
xrotwang opened this issue Jan 11, 2012 · 2 comments

Comments

@xrotwang
Copy link

with two instances of pceleryd running, wild clicking on "delete" links in the web interface made it possible to schedule multiple delete-tasks for the same TaskItem, which resulted in an exception in the task (IndexError when trying to get the first item of an empty query) and in an BrokenPipe error in the web app server . While this is a minor bug, I think it would be a good thing to promote correct handling of asynchronous code in this demo app.

@xrotwang
Copy link
Author

btw: running two instances of pceleryd has nothing to do with this issue. "wild clicking" is enough to reproduce the behaviour.

@sontek
Copy link
Owner

sontek commented Jan 11, 2012

Yeah, I should probably clean the app up to show how to handle everything properly. I built it just as a sample to see how configuration of pyramid_celery was done. I'll clean up the demo tomorrow and push updates.

Thanks for the report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants