You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast.
Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on https://community.boltops.com
Code sample: Have you put together a code sample to reproduce the issue and make it available? Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.
My Environment
Software
Version
Operating System
MacOS 14.6
Jets
6.0.3
Ruby
3.2.1
Expected Behaviour
When I try to run a Job from another Job (or the same one) I should be able to run it with perform_later and start another function. Basically the same behavior like we have from controller.
Current Behavior
The function crashes.
Step-by-step reproduction instructions
This is the error I'm getting:
WARN: JETS_QUEUE_URL_LINKEDIN not set. Unable to get queue url.
When I got a little bit into it, I noticed that in controller Lambda function we have ENV for all the functions:
JETS_QUEUE_URL_DEFAULT=...
besides DEFAULT, we have all the URLs from config.job.additional_queues, e.g. JETS_QUEUE_URL_ANY_NAME. This URLs are not present in the functions created from Jobs.
Code Sample
Solution Suggestion
It would be great to have those ENV values everywhere or at least to have somewhere in docs an explanation of how we could add them on our own in a project. Calling a Job from another Job is not that exotic request and it simplifies some processes.
The text was updated successfully, but these errors were encountered:
Checklist
My Environment
Expected Behaviour
When I try to run a Job from another Job (or the same one) I should be able to run it with
perform_later
and start another function. Basically the same behavior like we have from controller.Current Behavior
The function crashes.
Step-by-step reproduction instructions
This is the error I'm getting:
WARN: JETS_QUEUE_URL_LINKEDIN not set. Unable to get queue url.
When I got a little bit into it, I noticed that in controller Lambda function we have ENV for all the functions:
JETS_QUEUE_URL_DEFAULT=...
besides DEFAULT, we have all the URLs from config.job.additional_queues, e.g. JETS_QUEUE_URL_ANY_NAME. This URLs are not present in the functions created from Jobs.
Code Sample
Solution Suggestion
It would be great to have those ENV values everywhere or at least to have somewhere in docs an explanation of how we could add them on our own in a project. Calling a Job from another Job is not that exotic request and it simplifies some processes.
The text was updated successfully, but these errors were encountered: