Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow use of command deduplication in runtime components #7855

Open
bame-da opened this issue Nov 2, 2020 · 1 comment
Open

Allow use of command deduplication in runtime components #7855

bame-da opened this issue Nov 2, 2020 · 1 comment
Labels
component/daml-script component/json-api HTTP JSON API component/trigger-service Trigger service language Language team work team/ledger-clients Related to the Ledger Clients team's components.

Comments

@bame-da
Copy link
Contributor

bame-da commented Nov 2, 2020

Runtime components like JSON API, Script, Triggers and REPL use random UUIDs as commandIds at the moment, which means users can not make use of command deduplication. Starting the same trigger twice, for example, may lead to commands being committed twice.

Users should get enough control over commandIDs to be able to make use of command deduplication.

@cocreature
Copy link
Contributor

The JSON API does provide control over this via the meta field but I believe we don’t expose it in the JS bindings.

@stefanobaghino-da stefanobaghino-da added team/ledger-clients Related to the Ledger Clients team's components. component/daml-script component/json-api HTTP JSON API component/trigger-service Trigger service labels Aug 31, 2021
@cocreature cocreature added the language Language team work label Mar 10, 2022
@cocreature cocreature removed their assignment Mar 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/daml-script component/json-api HTTP JSON API component/trigger-service Trigger service language Language team work team/ledger-clients Related to the Ledger Clients team's components.
Projects
None yet
Development

No branches or pull requests

3 participants