refactor: disable Cloudflare Kv #167
Conversation
Abstracted CloudflareKv to KvStore interface and added EmptyStore class.
There was a problem hiding this comment.
In the future you should at least describe context in your pull body.
We decided to disable the use of KV because the original purpose of tracking state between runs was to be able to run plugin chains in series, with the potential to make use of the output of one plugin as an input to another, similar to Github Actions.
We decided that due to us constantly hitting KV limits, and that none of our plugins depend on this behavior, that we can run all of them concurrently and not track state anymore.
I don't see any changes related to concurrency. Is this finished?
|
I thought it would just be about the KV, I an add the concurrency here too. |
Utilize Promise.all to concurrently handle plugin chains and improve efficiency.
|
@0x4007 Yeah sorry cannot link the kernel logs here, so here is a screenshot Even in the screenshot it is not clear that it is concurrent but it runs with the code from this PR. |
Abstracted CloudflareKv to KvStore interface and added EmptyStore class.