-
-
Notifications
You must be signed in to change notification settings - Fork 290
ValueError: not enough values to unpack (expected 2, got 1) #697
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
Comments
It looks like rq changed how the job_ids are parsed for the |
terencehonles
added a commit
to terencehonles/django-rq
that referenced
this issue
Apr 19, 2025
This change uses the new ``registry.get_job_and_execution_ids`` instead of the updated ``registry.get_job_id`` which no longer returns the execution id. fixes: rq#697
terencehonles
added a commit
to terencehonles/django-rq
that referenced
this issue
Apr 19, 2025
This change uses the new ``registry.get_job_and_execution_ids`` instead of the updated ``registry.get_job_id`` which no longer returns the execution id. fixes: rq#697
terencehonles
added a commit
to terencehonles/django-rq
that referenced
this issue
Apr 19, 2025
This change uses the new ``registry.get_job_and_execution_ids`` instead of the updated ``registry.get_job_id`` which no longer returns the execution id. fixes: rq#697
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I keep getting this error when trying to view active jobs when there's at least 1 active job.
It's being caused by this function:
Why is a colon expected to be in the job_id?
I tried adding one to bypass this error but rq explicitly doesn't allow this either and errors out with:
ValueError: id must not contain ":"
get_executions
seems to have been added in django-rq v3.0 for rq v2.0 but rq v2.0.1 added the no-colon requirement.How can I solve this?
The text was updated successfully, but these errors were encountered: