Aurélien Manteaux
Aurélien Manteaux
Thank you for your feedback and your interest in Wisp! Actually this feature is already available through: 1. Keeping a reference of the job after the scheduling or getting one...
Do you think you can elaborate your use case? I am not sure I get the goal of this. Because if you are trying to build some table that gives...
Hi @newnewcoder, Sorry for the late answer, can you detail your use case? The Scheduler class is the root of the Wisp Scheduler, making another implementation would mean that nothing...
I have a doubt, do you want to execute the same jobs on both nodes, or do you want to load balance your jobs to your node instances (so if...
Ok I see! The "easy" solution is to have a dedicated node that run jobs. But that is actually a good idea to provide in the future a way to...
One external service must be used to provide the cluster synchronization feature. For a first version, a database service will be used for that. Maybe in the future other implementations...
Hi @muhdkhokhar I very glad to hear about your feedback! Thank you a lot! It is great to know Wisp is used on large projects, even outside our company. Do...
Until this is solved in micro-observables, this issue can be mitigated through the `.yarnrc.yml` file by adding: ```yml packageExtensions: micro-observables@*: dependencies: react-dom: "*" ```
See https://github.com/Coreoz/HTTP-Gateway for sample
@Wail-LT Tu pourras référencer cette issue pour traiter ce point, et supprimer les surcharges côté Kotlin