-
Notifications
You must be signed in to change notification settings - Fork 413
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
Flows: job.getChildrenValues is not a function for sandboxed workers #753
Comments
Yes, we are missing some proxies for flow related methods in Flows. Thanks for reporting. |
Current workout: import { Job, Queue } from "bullmq"
export default async function(sandboxedJob) {
const queue = new Queue(sandboxedJob.queueName, { connection }) // pass the same connection settings
const job = await Job.fromId(queue, sandboxedJob.id)
const childrenValues = await job.getChildrenValues()
} |
Any updates on this? |
I am also looking for this to be resolved. |
+1 |
right before starting a child, get and pass children values along side other job data. This should be okay as the parent job runs only after all children have finished. We then use this data to implement `getChildrenValues` function for sanboxed jobs. "fix taskforcesh#1306", "fix taskforcesh#753".
An updates on this? |
I just got bit by this thinking it was supported. Rewrote a large chunk of my app and ran into this issue. I should've checked it first with a small example 😞. |
We have a PR for this, seems like it could be merged anytime now #1417 |
An update on this? |
Version 1.46.6
The below line works as documented for normal workers, but throws the error
job.getChildrenValues is not a function
for sandboxed processors.Below are code snippets used to test, sans imports for brevity.
A nested job added to a FlowProducer:
Processed by sandboxed worker processes:
Processor definitions:
processors.ts:
The text was updated successfully, but these errors were encountered: