feat(pyamber): resolve unset input port zero

[carloea2]

What changes were proposed in this PR?

Resolve input ports by protobuf value equality instead of direct dictionary hashing. This lets an unset protobuf representation of port zero find the canonical registered port while preserving a clear error for unknown ports.

Any related issues, documentation, discussions?

Closes #8263

How was this PR tested?

The untouched live probe showed equal port-zero identities with different hashes and raised KeyError. After the fix it reported lookup_succeeded=True with the hashes still different.

C:\Users\carlo\texera\texera\.venv312\Scripts\python.exe -c "import sys,pytest; sys.path[:0]=[r'C:\Users\carlo\texera\texera-worktrees\investigate-bug68\amber\src\main\python',r'C:\Users\carlo\texera\texera\amber\src\main\python']; raise SystemExit(pytest.main([r'amber/src/test/python/core/architecture/packaging/test_input_manager.py','-q','-p','no:cacheprovider']))"

C:\Users\carlo\texera\texera\.venv312\Scripts\ruff.exe check amber/src/main/python amber/src/test/python

C:\Users\carlo\texera\texera\.venv312\Scripts\ruff.exe format --check amber/src/main/python/core/architecture/packaging/input_manager.py amber/src/test/python/core/architecture/packaging/test_input_manager.py

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

Generated-by: Codex

[github-actions]

Backport auto-label report

This fix: PR was checked against each actively-supported release branch. release/* labels drive the post-merge backport, so add or remove one to change where this fix lands.

Release branch	Analysis
⚠️ release/v1.3	Not labeled automatically — none of the files this PR modifies exist on this branch (amber/src/main/python/core/architecture/packaging/input_manager.py, amber/src/test/python/core/architecture/packaging/test_input_manager.py). The fix may target code that isn't on this release, or the files were moved/renamed after the branch was cut. Please check and add release/v1.3 by hand if this fix should be backported here.
✅ release/v1.2	Change detected on this branch — label added; this fix is queued to backport here. Requested review from @xuang7.

Auto-label run.

[github-actions]

Automated Reviewer Suggestions

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

• Contributors with relevant context: @aglinxinyuan, @eugenegujing
  You can notify them by mentioning @aglinxinyuan, @eugenegujing in a comment.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 50.00000% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 93.86%. Comparing base (50321e4) to head (45335b1).
⚠️ Report is 11 commits behind head on main.

Files with missing lines	Patch %	Lines
...ython/core/architecture/packaging/input_manager.py	50.00%	2 Missing and 2 partials ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #8264      +/-   ##
============================================
- Coverage     93.93%   93.86%   -0.08%     
  Complexity     4762     4762              
============================================
  Files          1191     1191              
  Lines         48308    48315       +7     
  Branches       5377     5827     +450     
============================================
- Hits          45380    45351      -29     
- Misses         1494     1496       +2     
- Partials       1434     1468      +34     

Flag	Coverage Δ		*Carryforward flag
access-control-service	81.00% <ø> (ø)		Carriedforward from 50321e4
agent-service	99.32% <ø> (ø)		Carriedforward from 50321e4
amber	90.03% <ø> (ø)		Carriedforward from 50321e4
computing-unit-managing-service	73.67% <ø> (ø)		Carriedforward from 50321e4
config-service	86.86% <ø> (ø)		Carriedforward from 50321e4
file-service	87.91% <ø> (ø)		Carriedforward from 50321e4
frontend	96.41% <ø> (ø)		Carriedforward from 50321e4
notebook-migration-service	79.31% <ø> (ø)		Carriedforward from 50321e4
pyamber	98.09% <50.00%> (-0.78%)	⬇️
workflow-compiling-service	77.19% <ø> (ø)		Carriedforward from 50321e4

*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.

[github-actions]

⚠️ Benchmark changes need a look

🟢 4 better · 🔴 5 worse · ⚪ 6 noise (<±5%) · 0 without baseline

Compared against main 7d57cd6 benchmarked on this same runner, so the delta is largely free of cross-runner hardware noise. The "7d avg" column still reflects the gh-pages dashboard. Treat <±5% as noise unless repeated.

Dashboard · Run

	config	throughput	MB/s	latency	max Δ latest / 7d
🔴	bs=10 sw=10 sl=64	431	0.263	23,196/29,110/29,110 us	🔴 +15.4% / 🔴 +86.8%
🟢	bs=100 sw=10 sl=64	969	0.591	102,014/124,615/124,615 us	🟢 -28.1% / 🔴 +16.2%
🔴	bs=1000 sw=10 sl=64	1,111	0.678	892,604/985,234/985,234 us	🔴 +7.5% / 🟢 -9.1%

Baseline details

Latest main 7d57cd6 from same runner

config	metric	PR	latest main	7d avg	Δ latest	Δ 7d
bs=10 sw=10 sl=64	throughput	431 tuples/sec	472 tuples/sec	787.98 tuples/sec	-8.7%	-45.3%
bs=10 sw=10 sl=64	MB/s	0.263 MB/s	0.288 MB/s	0.481 MB/s	-8.7%	-45.3%
bs=10 sw=10 sl=64	p50	23,196 us	20,109 us	12,593 us	+15.4%	+84.2%
bs=10 sw=10 sl=64	p95	29,110 us	31,885 us	15,579 us	-8.7%	+86.8%
bs=10 sw=10 sl=64	p99	29,110 us	31,885 us	18,786 us	-8.7%	+55.0%
bs=100 sw=10 sl=64	throughput	969 tuples/sec	924 tuples/sec	1,008 tuples/sec	+4.9%	-3.9%
bs=100 sw=10 sl=64	MB/s	0.591 MB/s	0.564 MB/s	0.615 MB/s	+4.8%	-3.9%
bs=100 sw=10 sl=64	p50	102,014 us	102,261 us	100,701 us	-0.2%	+1.3%
bs=100 sw=10 sl=64	p95	124,615 us	173,429 us	107,244 us	-28.1%	+16.2%
bs=100 sw=10 sl=64	p99	124,615 us	173,429 us	116,122 us	-28.1%	+7.3%
bs=1000 sw=10 sl=64	throughput	1,111 tuples/sec	1,131 tuples/sec	1,042 tuples/sec	-1.8%	+6.6%
bs=1000 sw=10 sl=64	MB/s	0.678 MB/s	0.69 MB/s	0.636 MB/s	-1.7%	+6.6%
bs=1000 sw=10 sl=64	p50	892,604 us	879,093 us	981,959 us	+1.5%	-9.1%
bs=1000 sw=10 sl=64	p95	985,234 us	916,533 us	1,023,080 us	+7.5%	-3.7%
bs=1000 sw=10 sl=64	p99	985,234 us	916,533 us	1,051,697 us	+7.5%	-6.3%

Raw CSV

config_idx,batch_size,schema_width,string_len,num_batches,total_ms,total_tuples,total_bytes,tuples_per_sec,mb_per_sec,lat_p50_us,lat_p95_us,lat_p99_us
0,10,10,64,20,464.36,200,128000,431,0.263,23195.63,29110.20,29110.20
1,100,10,64,20,2064.82,2000,1280000,969,0.591,102013.84,124615.43,124615.43
2,1000,10,64,20,17997.20,20000,12800000,1111,0.678,892604.44,985233.90,985233.90

[Yicong-Huang]

This is changing O(1) to O(n). if we need a better error message, you can catch the keyerror and reraise?

[Yicong-Huang]

also this should be a feat instead of a fix.

[carloea2]

Kept the lookup O(1) by normalizing protobuf defaults before dictionary access. I also changed the title and commit to feat. I cannot change repository labels, so fix and release/v1.2 still need to be replaced with feature.