[claude] fix(benchmarks-server): include commit_sha in measurement_id hash#7642
Merged
connortsui20 merged 1 commit intoct/benchmarks-v3from Apr 26, 2026
Merged
Conversation
Without commit_sha in the hash input, every (dim tuple) collapses to one row across commits via INSERT ... ON CONFLICT DO UPDATE, so the chart pages render at most one point per series. Adding commit_sha to the per-table hashers makes each (commit, dim) pair its own row, which is the time series the UI is built around. Re-emission of the same (commit, dim) is still the upsert case. The web-ui chart_page_query snapshot now correctly shows three commits with three points per series, matching the test fixture. No public API change; measurement_id is server-internal. Signed-off-by: Claude <noreply@anthropic.com>
connortsui20
added a commit
that referenced
this pull request
Apr 26, 2026
… hash (#7642) Without commit_sha in the hash input, every (dim tuple) collapses to one row across commits via INSERT ... ON CONFLICT DO UPDATE, so the chart pages render at most one point per series. Adding commit_sha to the per-table hashers makes each (commit, dim) pair its own row, which is the time series the UI is built around. Re-emission of the same (commit, dim) is still the upsert case. The web-ui chart_page_query snapshot now correctly shows three commits with three points per series, matching the test fixture. No public API change; measurement_id is server-internal. <!-- Thank you for submitting a pull request! We appreciate your time and effort. Please make sure to provide enough information so that we can review your pull request. The Summary and Testing sections below contain guidance on what to include. --> ## Summary <!-- If this PR is related to a tracked effort, please link to the relevant issue here (e.g., `Closes: #123`). Otherwise, feel free to ignore / delete this. In this section, please: 1. Explain the rationale for this change. 2. Summarize the changes included in this PR. A general rule of thumb is that larger PRs should have larger summaries. If there are a lot of changes, please help us review the code by explaining what was changed and why. If there is an issue or discussion attached, there is no need to duplicate all the details, but clarity is always preferred over brevity. --> Closes: #000 <!-- ## API Changes Uncomment this section if there are any user-facing changes. Consider whether the change affects users in one of the following ways: 1. Breaks public APIs in some way. 2. Changes the underlying behavior of one of the engine integrations. 3. Should some documentation be updated to reflect this change? If a public API is changed in a breaking manner, make sure to add the appropriate label. You can run `./scripts/public-api.sh` locally to see if there are any public API changes (and this also runs in our CI). --> ## Testing <!-- Please describe how this change was tested. Here are some common categories for testing in Vortex: 1. Verifying existing behavior is maintained. 2. Verifying new behavior and functionality works correctly. 3. Serialization compatibility (backwards and forwards) should be maintained or explicitly broken. --> Signed-off-by: Claude <noreply@anthropic.com> Co-authored-by: Claude <noreply@anthropic.com>
connortsui20
added a commit
that referenced
this pull request
Apr 26, 2026
… hash (#7642) Without commit_sha in the hash input, every (dim tuple) collapses to one row across commits via INSERT ... ON CONFLICT DO UPDATE, so the chart pages render at most one point per series. Adding commit_sha to the per-table hashers makes each (commit, dim) pair its own row, which is the time series the UI is built around. Re-emission of the same (commit, dim) is still the upsert case. The web-ui chart_page_query snapshot now correctly shows three commits with three points per series, matching the test fixture. No public API change; measurement_id is server-internal. <!-- Thank you for submitting a pull request! We appreciate your time and effort. Please make sure to provide enough information so that we can review your pull request. The Summary and Testing sections below contain guidance on what to include. --> ## Summary <!-- If this PR is related to a tracked effort, please link to the relevant issue here (e.g., `Closes: #123`). Otherwise, feel free to ignore / delete this. In this section, please: 1. Explain the rationale for this change. 2. Summarize the changes included in this PR. A general rule of thumb is that larger PRs should have larger summaries. If there are a lot of changes, please help us review the code by explaining what was changed and why. If there is an issue or discussion attached, there is no need to duplicate all the details, but clarity is always preferred over brevity. --> Closes: #000 <!-- ## API Changes Uncomment this section if there are any user-facing changes. Consider whether the change affects users in one of the following ways: 1. Breaks public APIs in some way. 2. Changes the underlying behavior of one of the engine integrations. 3. Should some documentation be updated to reflect this change? If a public API is changed in a breaking manner, make sure to add the appropriate label. You can run `./scripts/public-api.sh` locally to see if there are any public API changes (and this also runs in our CI). --> ## Testing <!-- Please describe how this change was tested. Here are some common categories for testing in Vortex: 1. Verifying existing behavior is maintained. 2. Verifying new behavior and functionality works correctly. 3. Serialization compatibility (backwards and forwards) should be maintained or explicitly broken. --> Signed-off-by: Claude <noreply@anthropic.com> Co-authored-by: Claude <noreply@anthropic.com> Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
connortsui20
added a commit
that referenced
this pull request
Apr 27, 2026
… hash (#7642) Without commit_sha in the hash input, every (dim tuple) collapses to one row across commits via INSERT ... ON CONFLICT DO UPDATE, so the chart pages render at most one point per series. Adding commit_sha to the per-table hashers makes each (commit, dim) pair its own row, which is the time series the UI is built around. Re-emission of the same (commit, dim) is still the upsert case. The web-ui chart_page_query snapshot now correctly shows three commits with three points per series, matching the test fixture. No public API change; measurement_id is server-internal. <!-- Thank you for submitting a pull request! We appreciate your time and effort. Please make sure to provide enough information so that we can review your pull request. The Summary and Testing sections below contain guidance on what to include. --> ## Summary <!-- If this PR is related to a tracked effort, please link to the relevant issue here (e.g., `Closes: #123`). Otherwise, feel free to ignore / delete this. In this section, please: 1. Explain the rationale for this change. 2. Summarize the changes included in this PR. A general rule of thumb is that larger PRs should have larger summaries. If there are a lot of changes, please help us review the code by explaining what was changed and why. If there is an issue or discussion attached, there is no need to duplicate all the details, but clarity is always preferred over brevity. --> Closes: #000 <!-- ## API Changes Uncomment this section if there are any user-facing changes. Consider whether the change affects users in one of the following ways: 1. Breaks public APIs in some way. 2. Changes the underlying behavior of one of the engine integrations. 3. Should some documentation be updated to reflect this change? If a public API is changed in a breaking manner, make sure to add the appropriate label. You can run `./scripts/public-api.sh` locally to see if there are any public API changes (and this also runs in our CI). --> ## Testing <!-- Please describe how this change was tested. Here are some common categories for testing in Vortex: 1. Verifying existing behavior is maintained. 2. Verifying new behavior and functionality works correctly. 3. Serialization compatibility (backwards and forwards) should be maintained or explicitly broken. --> Signed-off-by: Claude <noreply@anthropic.com> Co-authored-by: Claude <noreply@anthropic.com> Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
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
2 participants
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.
Without commit_sha in the hash input, every (dim tuple) collapses to one row across commits via INSERT ... ON CONFLICT DO UPDATE, so the chart pages render at most one point per series. Adding commit_sha to the per-table hashers makes each (commit, dim) pair its own row, which is the time series the UI is built around. Re-emission of the same (commit, dim) is still the upsert case.
The web-ui chart_page_query snapshot now correctly shows three commits with three points per series, matching the test fixture.
No public API change; measurement_id is server-internal.
Summary
Closes: #000
Testing