Skip to content

test(verify): give every operator the same table to read - #8360

Open
kz930 wants to merge 1 commit into
apache:mainfrom
kz930:feat/verify-canonical-table
Open

test(verify): give every operator the same table to read#8360
kz930 wants to merge 1 commit into
apache:mainfrom
kz930:feat/verify-canonical-table

Conversation

@kz930

@kz930 kz930 commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

What changes were proposed in this PR?

One table, thirty-four columns and fifteen rows, holding a column of every
type an operator can ask for and the awkward values each type admits: an empty
cell, a zero, a negative, a string that looks like a number, a date at a
boundary.

An operator that needs something the table cannot hold — a pair of tables
sharing a key, a numeric projection — names a projection of it rather than a
fixture of its own, so what every operator reads stays one thing.

Any related issues, documentation, discussions?

Part of #8325, 6 of 20; that issue lists the set in order.

How was this PR tested?

The tests in this change cover it. The whole set is exercised together once the last piece lands: every operator run through the engine and through its generated script, and the two answers compared.

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 5)

One table, thirty-four columns and fifteen rows, holding a column of every
type an operator can ask for and the awkward values each type admits: an empty
cell, a zero, a negative, a string that looks like a number, a date at a
boundary.

An operator that needs something the table cannot hold — a pair of tables
sharing a key, a numeric projection — names a projection of it rather than a
fixture of its own, so what every operator reads stays one thing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added feature platform Non-amber Scala service paths labels Sep 2, 2026
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

  • No candidates found from git blame history.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.11%. Comparing base (7976744) to head (52052df).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #8360   +/-   ##
=========================================
  Coverage     94.11%   94.11%           
  Complexity     4811     4811           
=========================================
  Files          1197     1197           
  Lines         48813    48813           
  Branches       5906     5906           
=========================================
  Hits          45939    45939           
  Misses         1420     1420           
  Partials       1454     1454           
Flag Coverage Δ *Carryforward flag
access-control-service 81.00% <ø> (ø)
agent-service 99.32% <ø> (ø) Carriedforward from 7976744
amber 90.08% <ø> (ø) Carriedforward from 7976744
computing-unit-managing-service 73.67% <ø> (ø)
config-service 87.00% <ø> (ø)
file-service 87.91% <ø> (ø) Carriedforward from 7976744
frontend 96.86% <ø> (ø) Carriedforward from 7976744
notebook-migration-service 79.31% <ø> (ø)
pyamber 98.47% <ø> (ø) Carriedforward from 7976744
workflow-compiling-service 77.19% <ø> (ø) Carriedforward from 7976744

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature platform Non-amber Scala service paths

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants