[vthumbe1503]

Description

Please include a brief summary of the changes, relevant motivation and context.

Fixes # (issue)

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refactoring

Changes

Please list the changes introduced in this PR:

• Change A
• Change B

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[greptile-apps]

Comments Outside Diff

These findings could not be posted inline.

•  Payload Errors Can Pass tests/pytorch/distributed/run_ep.py:548 ▶

  This comparison sums each received token’s features before sorting the rows. Swapped or compensating feature errors can leave those sums unchanged, so the MXFP8 dispatch test can pass with an incorrect token payload. Comparing complete rows in an order-independent way would preserve the test’s ability to detect those errors.

  Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!