Bots QA

[alexwykoff]

• Fix bots for Arena

  • Add logging
  • Investigate and open breakout issues based on discovery
  • Write tests then fix

• Investigate Apollo1 / Botfactory.

  • Bump up logging and possibly console view of bot resource usage
  • Cull bots which are long running, but inactive.

[alexwykoff]

• Bot Factory is out-of-date, but alpha quality is indeterminate.
• Bot kill process is async and likely has deconstruction/cleanup issues.
• Need a QA Kube
• Add the ability to kill a bot from the console Bot listing & controls dxos/console#54
• Signal console - add hostnames Hostname in signal pane dxos/console#50

[egorgripasov]

Some updates on logging/QA Kube:

• more logging in botkit (including bot process state) -> in alpha of botkit (sdk)
• alpha of cli with the latest botkit

Things to do @telackey :

• run DEBUG='dxos:botkit' wire bot factory start on apollo kubes
• run DEBUG='*' wire bot factory start on QA kubes

More findings:

Botkit disruption could be caused by ipfs and signal issues, not vise versa. We do BF reset quite often, and all the artifacts get removed from BotFactory, so it tries to downloads bots from IPFS quite often these days

[egorgripasov]

Updates:

• Added sufficient level of logging;
• Introduced QA kubes;
• Botkit resource management: Tested with https://github.com/dxos/sdk/blob/main/bot/testing/test/process.test.js

TODO: Bots hibernation #380

[egorgripasov]

Further updates:

• Kube BotFactory QA
  • List of running bots in kube fix: Add running bots tab. dxos/console#56
  • Kill switch for bot fix: Add running bots tab. dxos/console#56
  • Deploy latest console to QA kube
• Update Bots to latest echo/halo
  • Update Botkit
  • Update StoreBot
  • Update ChessBot
  • Update GithubBot
  • Update Kubes to latest CLI
  • Deploy latest bots

[alexwykoff]

@telackey would you mind picking up Kube update tasks

• update Kubes to latest CLI
• update Kubes to the latest console

[egorgripasov]

@telackey we might need to publish beta and release of cli as well, since it was recently published and might be broken in release.