Skip to content

fix: tracing validation fields always null (#448) - #476

Merged
hlship merged 1 commit into
masterfrom
hls/20260602-fix-448-tracing-validation
Jun 2, 2026
Merged

fix: tracing validation fields always null (#448)#476
hlship merged 1 commit into
masterfrom
hls/20260602-fix-448-tracing-validation

Conversation

@hlship

@hlship hlship commented Jun 2, 2026

Copy link
Copy Markdown
Member

Summary

  • ::tracing/validation was stored on the context map but execute-query reads it alongside ::tracing/parsing (which lives on the parsed-query map), causing validation startOffset and duration to always be nil in tracing output
  • Fix stores ::tracing/validation on the prepared query map, consistent with ::tracing/parsing, and reads it from parsed-query in execute-query
  • Adds regression test verifying both parsing and validation tracing phases have non-nil startOffset and positive duration

Fixes #448

🤖 Generated with eca

`::tracing/validation` was stored on the context map but read alongside
`::tracing/parsing` (which lives on the parsed-query map), causing the
validation startOffset and duration to always be nil in tracing output.

Store ::tracing/validation on the prepared query map, consistent with
::tracing/parsing, and read it from parsed-query in execute-query.

🤖 Generated with [eca](https://eca.dev)

Co-Authored-By: eca-agent <git@eca.dev>
@hlship
hlship merged commit f05c193 into master Jun 2, 2026
8 of 9 checks passed
@hlship hlship added this to the 1.3.0 milestone Jun 2, 2026
@hlship hlship added the bug label Jun 2, 2026
@hlship hlship self-assigned this Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

Tracing "validation" fields are always null

1 participant