-
Notifications
You must be signed in to change notification settings - Fork 39
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
Import Error from rq when trying to spin up a worker #582
Comments
hi @vfxcode Steps Taken to Fix:
Next Steps: Should we update the dependencies or document this change to prevent future issues? Let me know your thoughts! |
Hey thank you for taking a look, yes please go ahead!
…On Wed, 12 Mar 2025, 19:49 ***@***.***, ***@***.***> wrote:
hi @vfxcode <https://github.com/vfxcode>
Issue:
Getting ImportError: cannot import name 'Connection' from 'rq' when trying
to spin up the worker.
Steps Taken to Fix:
1. Checked the installed rq version.
2. Removed the deprecated Connection import.
3. Used Redis for connection instead.
4. Initialized the worker with the correct Redis connection.
5. Tested and confirmed the worker is running successfully.
Next Steps:
Should we update the dependencies or document this change to prevent
future issues? Let me know your thoughts!
—
Reply to this email directly, view it on GitHub
<#582 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMCRHSHOMN7U3UCPZUA6E32UCFVVAVCNFSM6AAAAABXLLV7AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJYHEZTMNRRGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
[image: Hardik301002]*Hardik301002* left a comment (OWASP/OpenCRE#582)
<#582 (comment)>
hi @vfxcode <https://github.com/vfxcode>
Issue:
Getting ImportError: cannot import name 'Connection' from 'rq' when trying
to spin up the worker.
Steps Taken to Fix:
1. Checked the installed rq version.
2. Removed the deprecated Connection import.
3. Used Redis for connection instead.
4. Initialized the worker with the correct Redis connection.
5. Tested and confirmed the worker is running successfully.
Next Steps:
Should we update the dependencies or document this change to prevent
future issues? Let me know your thoughts!
—
Reply to this email directly, view it on GitHub
<#582 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMCRHSHOMN7U3UCPZUA6E32UCFVVAVCNFSM6AAAAABXLLV7AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJYHEZTMNRRGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems there is an issue when we try to spin up a worker. The following error occurs:
We have validated that OpenCRE has a fully functioning Redis and OpenCRE is correctly configured to connect to it. We can after all see the jobs get queued in the respective redis keys.
The text was updated successfully, but these errors were encountered: