Is there a reason for \x06\x16 to be used as priority separator?
See original GitHub issueIt makes it really difficult to query redis from command line.
I tried redis-cli type "queue_name\x06\x163"
and many other variants with some sort of escaping, but couldn’t make it work.
Also as far as I understand the naming convention in redis is to use ‘:’ as a separator. redis.io
Could we maybe make it configurable via an environment variable or otherwise?
Issue Analytics
- State:
- Created 9 years ago
- Reactions:1
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Change celery's \x06\x16 priority separator - CK's Tech Blog
“Emulated” means that celery is putting the tasks into multiple internal priority queues and that it consumes from them in priority order, so ......
Read more >Routing Tasks — Celery 5.2.7 documentation
The simplest way to do routing is to use the task_create_missing_queues ... a separator (by default x06x16 ) and their priority number appended...
Read more >Kombu Documentation - Read the Docs
Binding exchanges and queues to a connection will make it use that ... represents a queue we used the hardcored value \x06\x16 separator....
Read more >How to DRASTICALLY Lower Input Delay in ALL GAMES!
Thank you so much for watching ❤️ Make sure to Like & Subscribe if this video helped you!In this video, I show you...
Read more >Diff - kernel/common.git - Google Git
+ +State 1: All writes to the device cause the underlying data to be backed up ... but _not_ scaled by task priority...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The flower project seems to have a solid implementation of what you want probably, see here.
This raises an issue with the documentation, which says that you can use the following to get the number of tasks in a queue:
We should tweak these docs to mention that that query will only return P0 tasks.