Skip to content

Conversation

@tarikBensalem-DA
Copy link

Pull Request Checklist

Cluster Testing

  • If a cluster test is required, comment /cluster_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If a hard-migration test is required (from the latest release), comment /hdm_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.

PR Guidelines

  • Include any change that might be observable by our partners or affect their deployment in the release notes.
  • Specify fixed issues with Fixes #n, and mention issues worked on using #n
  • Include a screenshot for frontend-related PRs - see README or use your favorite screenshot tool

Merge Guidelines

  • Make the git commit message look sensible when squash-merging on GitHub (most likely: just copy your PR description).

Signed-off-by: tarikBensalem-DA <tarik.bensalem@digitalasset.com>
@martinflorian-da martinflorian-da added the static Used to label PRs for which static tests suffice label Oct 15, 2025
Co-authored-by: Itai Segall <itai.segall@digitalasset.com>
Signed-off-by: tarikBensalem-DA <164049054+tarikBensalem-DA@users.noreply.github.com>
Signed-off-by: tarikBensalem-DA <164049054+tarikBensalem-DA@users.noreply.github.com>
val parties = participant.parties.list (<participantIdentifier>)
You can assign a party to a variable using the following command, where <index> is the zero-based position of the party in the list:
Copy link
Contributor

Choose a reason for hiding this comment

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

I suggest we remove this. They need to have separate consoles open (one for the old participant, one for the new), so I don't know if writing to a variable will really be of help to anyone...

Copy link
Contributor

@martinflorian-da martinflorian-da left a comment

Choose a reason for hiding this comment

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

@tarikBensalem-DA this PR has gotten a bit stale and now has conflicts with main... LMK if you want to get it merge-ready again, if not I suggest we close it.

Also FYI: past and ongoing improvements to the recover-from-key process:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

static Used to label PRs for which static tests suffice

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants