Skip to content
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.

Have asynchronous execution so that the bot stays responsive for new requests while executing commands #63

Closed
wants to merge 46 commits into from

Conversation

joao-paulo-parity
Copy link
Contributor

@joao-paulo-parity joao-paulo-parity commented Sep 16, 2021

In this PR:

  • Remove shell.js in favor of internal Runner abstraction
  • Runner executes commands asynchronously so that the app stays responsive

Word of caution: we've faced issues related to overhead in the past (#47) although it's still inconclusive if asynchronous execution mattered for those cases. We should run the benchmarks after this branch is deployed and assure this change does not affect the measurements. If asynchronous execution does matter for those metrics, this implementation and the app's setup itself will have to be redesigned.

closes #68

@joao-paulo-parity joao-paulo-parity marked this pull request as draft September 16, 2021 21:58
@joao-paulo-parity
Copy link
Contributor Author

closed in favor of https://github.com/paritytech/command-bot

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix unresponsiveness during benchmark execution
1 participant