starred/asynq

Fork 0

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

[GH-ISSUE #555] [BUG] UNKNOWN: redis command error: SADD failed: redis: client is closed #2290

New issue

Open

opened 2026-03-15 19:58:18 +03:00 by kerem · 6 comments

kerem commented

2026-03-15 19:58:18 +03:00

Owner

Originally created by @linchao0815 on GitHub (Oct 11, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/555

Originally assigned to: @hibiken on GitHub.

Describe the bug
client.Enqueue(task)

To Reproduce
Steps to reproduce the behavior (Code snippets if applicable):

Setup background processing ...
Enqueue tasks ...
See Error ...
There is a low chance of this problem occurring.

How do I handle this error ?

Originally created by @linchao0815 on GitHub (Oct 11, 2022). Original GitHub issue: https://github.com/hibiken/asynq/issues/555 Originally assigned to: @hibiken on GitHub. **Describe the bug** client.Enqueue(task) **To Reproduce** Steps to reproduce the behavior (Code snippets if applicable): 1. Setup background processing ... 2. Enqueue tasks ... 3. See Error ... 4. There is a low chance of this problem occurring. How do I handle this error ?

kerem added the

bug

label

2026-03-15 19:58:18 +03:00

kerem commented

2026-03-15 19:58:29 +03:00

Author

Owner

@domgolonka commented on GitHub (Oct 12, 2022):

I am getting the same thing

@domgolonka commented on GitHub (Oct 12, 2022): I am getting the same thing

kerem commented

2026-03-15 19:58:35 +03:00

Author

Owner

@domgolonka commented on GitHub (Oct 12, 2022):

@linchao0815 I figured it out, the asynq.Client was closing too early.

@domgolonka commented on GitHub (Oct 12, 2022): @linchao0815 I figured it out, the asynq.Client was closing too early.

kerem commented

2026-03-15 19:58:40 +03:00

Author

Owner

@linchao0815 commented on GitHub (Oct 13, 2022):

@domgolonka

@linchao0815 I figured it out, the asynq.Client was closing too early.
My case isn't it!

@linchao0815 commented on GitHub (Oct 13, 2022): @domgolonka > @linchao0815 I figured it out, the asynq.Client was closing too early. My case isn't it!

kerem commented

2026-03-15 19:58:45 +03:00

Author

Owner

@MetaverseMan commented on GitHub (Apr 20, 2023):

@linchao0815 I figured it out, the asynq.Client was closing too early.

Figure it out,Same situation, thanks

@MetaverseMan commented on GitHub (Apr 20, 2023): > @linchao0815 I figured it out, the asynq.Client was closing too early. Figure it out,Same situation, thanks

kerem commented

2026-03-15 19:58:50 +03:00

Author

Owner

@avvari-da commented on GitHub (Apr 5, 2024):

How do you fix asynq.Client was closing too early ?

@avvari-da commented on GitHub (Apr 5, 2024): How do you fix `asynq.Client was closing too early` ?

kerem commented

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

Author

Owner

@refuse2speak commented on GitHub (Jul 7, 2024):

How do you fix asynq.Client was closing too early ?

When you create the client you probably have added a defer function as shown in the example. This is called too early, eg. when the enclosing function returns. You could add the defer function to the main() function so the Task Client is not closed before your main function returns.

@refuse2speak commented on GitHub (Jul 7, 2024): > How do you fix `asynq.Client was closing too early` ? When you create the client you probably have added a defer function as shown in the example. This is called too early, eg. when the enclosing function returns. You could add the defer function to the main() function so the Task Client is not closed before your main function returns. <img width="741" alt="image" src="https://github.com/hibiken/asynq/assets/96352231/e7eda631-ac80-4387-a2d1-e480aeea6e49">

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#2290

No description provided.

Rows
Columns