Skip to content

Surface trigger profile context in result tables - #216

Merged
yoshifuminakamura merged 1 commit into
developfrom
feature/result-activity-profile-context
Sep 16, 2026
Merged

yoshifuminakamura merged 1 commit into
developfrom
feature/result-activity-profile-context

Conversation

@yoshifuminakamura

@yoshifuminakamura yoshifuminakamura commented Sep 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • snapshot execution profile activity/allocation context into Portal trigger run payloads
  • show Result table activity/allocation using Result JSON first, trigger variables second, and trigger payload snapshots as fallback
  • use the same fallback in trigger run summaries

Tests

  • python -m pytest result_server/tests/test_results_loader.py result_server/tests/test_trigger_display.py
  • python result_server/tests/run_result_server_tests.py
  • python -m py_compile result_server/utils/results_loader.py result_server/trigger_runner.py result_server/utils/result_table_rows.py result_server/utils/trigger_display.py
  • git diff --check

Manual verification

  • confirmed the rendered Result table shows the Activity / Allocation column and allocation fallback values

Signed-off-by: yoshifuminakamura <nakamura@riken.jp>
@yoshifuminakamura
yoshifuminakamura merged commit 85ed167 into develop Sep 16, 2026
8 checks passed
@yoshifuminakamura
yoshifuminakamura deleted the feature/result-activity-profile-context branch September 16, 2026 15:14
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.

1 participant