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

Faulty ephemeral uploads staying seemingly forever #7

Open
tahirazim opened this issue Mar 13, 2012 · 5 comments
Open

Faulty ephemeral uploads staying seemingly forever #7

tahirazim opened this issue Mar 13, 2012 · 5 comments

Comments

@tahirazim
Copy link
Member

Uploaded ephemeral meshes, for which the upload process does not complete successfully, seem to stay in my pending upload queue forever. See, for example, the list of pending uploads under my account on singular.stanford.edu. The process did not complete for these meshes because of the bug in sirikata, where a "Content-Length" header in the response was deemed an error condition.

@jterrace
Copy link
Member

Is the status "PENDING" and there's no button to remove it?

@tahirazim
Copy link
Member Author

I don't see a button to remove them, neither next to their names on the pending list, nor when I click on them. Maybe I'm not looking at the right place?

@jterrace
Copy link
Member

How many are there? This can happen if the task to process the upload gets fired to celery, but then it never successfully completes. I think this happened briefly when you were uploading to the Princeton side and the celery worker was broken?

@tahirazim
Copy link
Member Author

There are 9 of them.

@jterrace
Copy link
Member

Okay, right now there's no good mechanism for getting rid of them. I guess the right thing to do would be to have a celerybeat task running that checks for tasks that are still pending but are not running or queued and then re-fires the task off to celery.

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