Hi is it possible in the future to add a schedular type of functionality to the retrier component itself instead of creating a redundant wrapper like how it is shown above? Or maybe pass the retrier component to the schedular directly
#Can we schedule action retrier with scheduler ?
inland lily
frosty crane
@inland lily one thing to note is that you can call retrier.run from within a mutation already, if that's what you're looking for.
I put up a PR here.
Jamie's new abstraction (which combines the retrier with workpool) is slick, but also would need a function to schedule something in the future, if you don't want the wrapper
frosty crane
you mean with the initialDelayMs? I at first thought that was a backoff config
frosty crane
it'd be nice if it was runAfter to match the scheduler syntax
old rose
yeah, I can add that as a wrapper function
frosty crane
I think you want it internal so it can still return the ID
old rose
er.. wrapper method I suppose
maybe we should talk in person so I can make sure I follow you
frosty crane
Jamie was right, and I just updated my PR back to convenience functions.
Here's an alpha if you want to try it @inland lily @convex-dev/action-retrier@0.1.7-alpha.1
it also adds a runId argument to onComplete
royal peak
What a masterclass in collaboration!
inland lily
Thanks @frosty crane will integrate it today
frosty crane
Thanks <@897754604790480906> will integrate it today
Lmk if it meets your needs so I can release it as a non-alpha
inland lily
I will test it for a few days in prod but looking at PR it does meet the requirement
@frosty crane Hi Ian,
wanted to flag a security issue in the dependency chain. The current convex package depends on esbuild@0.24.2 which has a known vulnerability (CVE-2023-45131). The patched version is 0.25.0.
Impact:
Dev servers could be exposed to DNS rebinding attacks during local development.
https://github.com/advisories/GHSA-67mh-4wv8-2f99
