Using `fork` for Long-Running Processes and Handling Results
What's the appropriate pattern to call an effect of a long running process, and get its results later. Sounds like you should
so would you yield* fork(effect) and then handle the Exit value when you get it back? Do you just call an Effect.never so the effect itself doesn't stop?
For more context I have a cli command that will call a github workflow, and my goal is to wait for its results which can be minutes. I maybe want to poll the job to get its current results or where its at but for now, just invoke a workflow from the cli and then make sure i can wait for its results
forkso would you yield* fork(effect) and then handle the Exit value when you get it back? Do you just call an Effect.never so the effect itself doesn't stop?
For more context I have a cli command that will call a github workflow, and my goal is to wait for its results which can be minutes. I maybe want to poll the job to get its current results or where its at but for now, just invoke a workflow from the cli and then make sure i can wait for its results
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
