starred/asynq

Fork 0

mirror of https://github.com/hibiken/asynq.git synced 2026-04-26 07:25:56 +03:00

[GH-ISSUE #292] [BUG] message always pending #2142

New issue

Closed

opened 2026-03-15 19:22:55 +03:00 by kerem · 3 comments

kerem commented

2026-03-15 19:22:55 +03:00

Owner

Originally created by @moulo1982 on GitHub (Jul 14, 2021).
Original GitHub issue: https://github.com/hibiken/asynq/issues/292

Originally assigned to: @hibiken on GitHub.

Describe the bug
message always pending

To Reproduce
Steps to reproduce the behavior (Code snippets if applicable):
Queue Name is “CamelCase”，Enqueue method use QueueOpting （

// Queue name is case-insensitive and the lowercased version is used.
func Queue(qname string) Option {
return queueOption(strings.ToLower(qname))
}

）， but Server “asynq.Config”‘s Queues not “ToLower”。so， message always pending。

Sorry， My English is very pool。

Originally created by @moulo1982 on GitHub (Jul 14, 2021). Original GitHub issue: https://github.com/hibiken/asynq/issues/292 Originally assigned to: @hibiken on GitHub. **Describe the bug** message always pending **To Reproduce** Steps to reproduce the behavior (Code snippets if applicable): Queue Name is “CamelCase”，Enqueue method use QueueOpting （ // Queue name is case-insensitive and the lowercased version is used. func Queue(qname string) Option { return queueOption(strings.ToLower(qname)) } ）， but Server “asynq.Config”‘s Queues not “ToLower”。so， message always pending。 Sorry， My English is very pool。

kerem

2026-03-15 19:22:55 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-15 19:23:11 +03:00

Author

Owner

@hibiken commented on GitHub (Jul 14, 2021):

@moulo1982 Thank you so much for spotting this bug!

Now that I'm thinking about this, I think it doesn't make much sense to make queue names case-insensitive?
Do you think we should just use the queue name provided as is (without normalize it to lowercase)?

What do you think? /cc @crossworth

@hibiken commented on GitHub (Jul 14, 2021): @moulo1982 Thank you so much for spotting this bug! Now that I'm thinking about this, I think it doesn't make much sense to make queue names case-insensitive? Do you think we should just use the queue name provided as is (without normalize it to lowercase)? What do you think? /cc @crossworth

kerem commented

2026-03-15 19:23:16 +03:00

Author

Owner

@crossworth commented on GitHub (Jul 14, 2021):

I think we can use as provided, I don't see any problem with it, simple is better.

@crossworth commented on GitHub (Jul 14, 2021): I think we can use as provided, I don't see any problem with it, simple is better.

kerem commented

2026-03-15 19:23:21 +03:00

Author

Owner

@moulo1982 commented on GitHub (Jul 15, 2021):

I think we can use as provided, I don't see any problem with it, simple is better.

I think it's good

@moulo1982 commented on GitHub (Jul 15, 2021): > I think we can use as provided, I don't see any problem with it, simple is better. I think it's good

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/asynq#2142

No description provided.

Rows
Columns