[msaroufim]

Summary

• Set Modal runner functions to a one-hour platform timeout.
• Match kernelbot's in-function alarm timeout to the same one-hour envelope.

Root Cause

Production Modal logs for discord-bot-runner show B200 runner inputs being cancelled at Modal's default 300 second function timeout, including a cancellation at 2026-06-18 22:19:32 UTC that lines up with the 814188 failure window:

Task's current input ... hit its timeout of 300s
[modal-client] Received a cancellation signal while processing input ...
[modal-client] Successfully canceled input ...

The deployed runner functions were registered without a Modal timeout= argument, so the platform default could cancel the function before kernelbot's own timeout handling ran. Raising only the Modal platform timeout is not enough because modal_run_config still had an internal 600s alarm; this PR sets both to the same one-hour envelope.

Validation

• uv run ruff check src/runners/modal_runner.py src/runners/modal_runner_archs.py
• uv run python -m py_compile src/runners/modal_runner.py src/runners/modal_runner_archs.py
• git diff --check

Deployment Note

After merge, the Modal runner app needs to be redeployed so the new function-level timeout=3600 is applied. Deploying only the Northflank service is not enough for this part.

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
src/libkernelbot
utils.py
Project Total

This report was generated by python-coverage-comment-action