Skip to content

fix(query): carry execution_time_ms through async poll path - #184

Merged
zfarrell merged 1 commit into
mainfrom
fix/async-execution-time-null
Jun 25, 2026
Merged

zfarrell merged 1 commit into
mainfrom
fix/async-execution-time-null

Conversation

@zfarrell

Copy link
Copy Markdown
Contributor

Slow queries (>~1s) fall back to async execution, and the Arrow result fetch hardcoded execution_time_ms: None, so hotdata query reported null timing for exactly the queries you most want to time. The async execute poll loop and query status now stamp the run's own execution_time_ms onto the displayed result.

Closes #183

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Carries execution_time_ms through the async poll/status paths correctly. Helper mirrors the inline path's negative clamp, null stays None (em dash) rather than a fabricated 0, and both call sites are updated consistently. Tests cover the double-option mapping cases plus a regression integration test for #183. LGTM.

@codecov

codecov Bot commented Jun 25, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 81.03448% with 11 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/query.rs 81.03% 11 Missing ⚠️

📢 Thoughts on this report? Let us know!

@zfarrell
zfarrell merged commit a6dce54 into main Jun 25, 2026
14 checks passed
@zfarrell
zfarrell deleted the fix/async-execution-time-null branch June 25, 2026 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

hotdata query: execution_time_ms is null for queries that fall back to async execution

1 participant