Preserve internal dispatch timings and add AI harness guidance#3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2
Summary
docs/engineering/skills/, including the PR rule that AI models must run the formatter and linter before the final commit.Root Cause
Internal dispatch requests created their own request-level timing dictionary. Those request logs are intentionally suppressed, so endpoint segment timings could disappear from the visible
modal_worker_dispatchorcloud_run_worker_dispatchoperation log.Validation
uv run --extra dev ruff format .uv run --extra dev ruff check .uv run --extra dev --extra all coverage run -m pytestuv run --extra dev --extra all coverage report