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
Plt 5848 get contract #585
Conversation
a4fbb42
to
3278c19
Compare
4547500
to
5ce22bc
Compare
eb81595
to
0c1480d
Compare
5ce22bc
to
d98f552
Compare
0c1480d
to
2b7f9a1
Compare
d98f552
to
c98b678
Compare
2b7f9a1
to
a2d7ff7
Compare
c98b678
to
7c72e62
Compare
@@ -316,6 +315,7 @@ withLocalMarloweRuntime' MarloweRuntimeOptions{..} test = withRunInIO \runInIO - | |||
contractStore <- createContractStore ContractStoreOptions | |||
{ contractStoreDirectory = resolveWorkspacePath workspace "contract-store" | |||
, contractStoreStagingDirectory = resolveWorkspacePath workspace "contract-staging-area" | |||
, lockingSleepBetweenRetries = 100_000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Presumably this is microseconds. I wonder if lockingMicrosecondsBetweenRetries
might be more expressive and self documenting?
resultsVariations :: Tag query delimiter err results -> NonEmpty results | ||
|
||
instance ArbitraryQuery query => ArbitraryMessage (Query query) where | ||
class Request req => ArbitraryRequest req where |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why isn't this located in a separate package for test generators. Are these arbitrary instances needed by the protocol?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess to avoid orphan instances, it's been like this for quite a long time. presumably dead code elimination should cull this from the final executable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will the format/organization of the file store for contracts always be forward compatible, or do we have to version it? For some users, it might be the only record they have of the continuations, so they'll want it forever usable in new versions of Marlowe Runtime.
Good question. As long as the |
5bad0af
to
4d5dbf1
Compare
Changes in this PR:
marlowe-contract
marlowe-proxy
Pre-submit checklist: