Skip to content

rfc13: sync wire protcol ABNF with MPICH protocol specs - #549

Merged
mergify[bot] merged 4 commits into
flux-framework:masterfrom
garlick:pmi_errors
Sep 2, 2026
Merged

rfc13: sync wire protcol ABNF with MPICH protocol specs#549
mergify[bot] merged 4 commits into
flux-framework:masterfrom
garlick:pmi_errors

Conversation

@garlick

@garlick garlick commented Sep 2, 2026

Copy link
Copy Markdown
Member

Problem: RFC 13 contains a few minor errors in its wire protocol ABNF when compared to the MPICH protocol specs.

The MPICH protocol specification files should be considered authoritative. Fix the bugs and add citations to those files.

@garlick garlick changed the title rfc13: sync wire protcol ABNF if MPICH protocol specs rfc13: sync wire protcol ABNF with MPICH protocol specs Sep 2, 2026
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

⚠️ linkcheck failed with status code 2

Problem: RFC 13 does not cite the (new?) MPICH wire protocol
definition files.

Add citations.

Assisted-by: Claude:claude-opus-4.8
Problem: the RFC 13 abort ABNF disagrees with the MPICH wire protocol
definition files on three points:
1. it fails to define the required abort "exitcode" attribute
2. it fails to define the optional abort "message" attribute
3. it defines an abort response that should not exist

Fix the abort ABNF.

Assisted-by: Claude:claude-opus-4.8
Problem: the RFC 13 get_result ABNF (the response to the KVS get)
omits an optional "found" attribute described by the MPICH protocol
definition files.

Update ABNF and add some description to the Error Handling section.

Assisted-by: Claude:claude-opus-4.8
Problem: RFC 13 requires the kvsname key on put and get, but the
MPICH protocol definition files show it as optional.

Make kvsname optional.

Assisted-by: Claude:claude-opus-4.8
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

⚠️ linkcheck failed with status code 2

@grondo grondo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mergify

mergify Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Queued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • Entered queue2026-09-02 21:24 UTC · Rule: default · triggered by rule rebase and merge when passing all checks
  • Checks skipped · PR is already up-to-date
  • Merged2026-09-02 21:25 UTC · at 587805ed7a003c4cd2dcb03b337bb561ef10863e · merge

This pull request spent 14 seconds in the queue, including 3 seconds running CI.

Required conditions to merge
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:flux-rfc
    • check-neutral = docs/readthedocs.org:flux-rfc
    • check-skipped = docs/readthedocs.org:flux-rfc
  • any of [🛡 GitHub branch protection]:
    • check-success = make check
    • check-neutral = make check
    • check-skipped = make check
  • any of [🛡 GitHub branch protection]:
    • check-success = validate commits
    • check-neutral = validate commits
    • check-skipped = validate commits

@mergify
mergify Bot merged commit 587805e into flux-framework:master Sep 2, 2026
7 of 8 checks passed
@mergify mergify Bot removed the queued label Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants