Skip to content

ladder: post-merge follow-ups from #1362 pre-merge review (multi-account test gap + nits) #1370

Closed

Description

@cristim

Non-blocking findings from the final pre-merge adversarial review of #1362 (merged as 7adacd7):

  1. Test gap (LOW): no positive test asserts SkippedMultiAccount==1 - only ==0 assertions exist (handler_ladder_test.go ~889). The code path (handler_ladder.go ~232-234, configs whose cloud account does not match the resolved caller account) is real but unexercised. Add a one-config mismatched-ExternalID test asserting the config is visibly counted skipped, nothing persisted for it, and other configs still process (isolation).
  2. NIT: handler_ladder.go ~256 variable cap shadows the builtin; rename to capability.
  3. NIT: handler_ladder.go ~437-439 comment says the unknown-cadence error surfaces "during Allocate"; it actually surfaces in ladderConfigToEngine (still pre-persist, fail-loud). Fix the comment.

Small, single-PR scope. Part of LeanerCloud/cloud-commitments-platform#70 / tracker LeanerCloud/cloud-commitments-go#27.

Activity

  1. cristim commented on Jul 16, 2026

    @cristim
    MemberAuthor

    Implementation is up as PR #1371 (branch fix/ladder-1370-followups): positive multi-account skip test (fails when the account comparison is inverted, proving the invariant), cap->capability rename, and the corrected cadence comment. Gates green (build/vet 0, internal/server 402 tests, gocyclo clean). Awaiting CodeRabbit, then it merges in the queue.

  2. added a commit that references this issue on Jul 16, 2026
    005494e
  3. added 5 commits that reference this issue on Jul 16, 2026
    8b93b4a
    7360e94
    8dfb1d9
    ce5d176
    3b68d9a
  4. added a commit that references this issue on Sep 27, 2026
    7ba72a7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions