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

Celery queue names inconsistent #3066

Closed
PrivacyDragon opened this issue Oct 28, 2023 · 0 comments · Fixed by #3068
Closed

Celery queue names inconsistent #3066

PrivacyDragon opened this issue Oct 28, 2023 · 0 comments · Fixed by #3068

Comments

@PrivacyDragon
Copy link

Is your feature request related to a problem? Please describe.
In the admin interface, the Celery Status tab shows all the current queues.
They seemed to be only ever-increasing recently, so I had to look into why that happened.
After a lot of wasting of time, I figured out how to properly get into Flower, (and how to start it...)
Here, I discovered that the Celery worker was ignoring all but four of the queues, so I had to manually add them.
This did not really seem to be a problem. However, when I entered broadcasts, as that is what the queue is named in the admin interface, nothing happened. An investigation later I found out that the queue was actually called broadcast, singular.

Describe the solution you'd like
So, please fix that. Either change the name of the queue, or change it in the admin interface, so that someone can look at the admin interface to know what the queue names are...

Describe alternatives you've considered
N/A

Additional context
N/A

hughrun added a commit to hughrun/bookwyrm that referenced this issue Oct 29, 2023
- changes 'broadcasts' to 'broadcast' in Celery page in admin section
- re-orders celery queues on admin page to be in English alphabetical order (other than priority levels) - this makes them consistent with the Flower interface
- fixes bookwyrm-social#3066
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

Successfully merging a pull request may close this issue.

1 participant