Page MenuHomePhabricator

Fix a looping workflow when trying to submit a partially-effectless transaction group
ClosedPublic

Authored by epriestley on May 23 2019, 6:45 PM.
Tags
None
Referenced Files
F15407111: D20552.diff
Tue, Mar 18, 3:48 PM
Unknown Object (File)
Sun, Feb 23, 7:15 PM
Unknown Object (File)
Sat, Feb 22, 1:19 PM
Unknown Object (File)
Fri, Feb 21, 8:39 PM
Unknown Object (File)
Fri, Feb 21, 8:08 PM
Unknown Object (File)
Jan 30 2025, 3:46 PM
Unknown Object (File)
Jan 29 2025, 3:17 AM
Unknown Object (File)
Jan 26 2025, 7:55 PM
Subscribers
None

Details

Summary

Ref T13289. If you do this:

  • Subscribe to a task (so we don't generate a subscribe side-effect later).
  • Prepare a transaction group: sign with MFA, change projects (don't make any changes), add a comment.
  • Submit the transaction group.

...you'll get prompted "Some actions don't have any effect (the non-change to projects), apply remaining effects?".

If you confirm, you get MFA'd, but the MFA flow loses the "continue" confirmation, so you get trapped in a workflow loop of confirming and MFA'ing.

Instead, retain the "continue" bit through the MFA.

Also, don't show "You can't sign an empty transaction group" if there's a comment.

See also T13295, since the amount of magic here can probably be reduced. There's likely little reason for "continue" or "hisec" to be magic nowadays.

Test Plan
  • Went through the workflow above.
  • Before: looping workflow.
  • After: "Continue" carries through the MFA gate.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable