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

Engine: Remove optionality of contract ID Seeding. #5966

Merged
merged 5 commits into from
May 13, 2020

Conversation

remyhaemmerle-da
Copy link
Collaborator

Pull Request Checklist

  • Read and understand the contribution guidelines
  • Include appropriate tests
  • Set a descriptive title and thorough description
  • Add a reference to the issue this PR will solve, if appropriate
  • Include changelog additions in one or more commit message bodies between the CHANGELOG_BEGIN and CHANGELOG_END tags
  • Normal production system change, include purpose of change in description

NOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with /AzurePipelines run to
trigger the build.

@remyhaemmerle-da remyhaemmerle-da force-pushed the remy-drop-relative-contract-id branch from 6ec6ea4 to 4bceaf7 Compare May 13, 2020 15:44
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

This is my kind of pull request.

remyhaemmerle-da and others added 3 commits May 13, 2020 17:53
@remyhaemmerle-da remyhaemmerle-da force-pushed the remy-drop-relative-contract-id branch from da04792 to 1c31fcd Compare May 13, 2020 16:46
@remyhaemmerle-da remyhaemmerle-da changed the title Engine: Remove optionality of seeding. Engine: Remove optionality of contract ID Seeding. May 13, 2020
@remyhaemmerle-da remyhaemmerle-da merged commit deedec9 into master May 13, 2020
@remyhaemmerle-da remyhaemmerle-da deleted the remy-drop-relative-contract-id branch May 13, 2020 18:29
@remyhaemmerle-da remyhaemmerle-da mentioned this pull request May 13, 2020
6 tasks
@@ -1380,6 +1371,9 @@ class EngineTest extends WordSpec with Matchers with EitherValues with BazelRunf
"fetching contracts that have keys correctly fills in the transaction structure" when {
val fetchedCid = toContractId("#1")
val now = Time.Timestamp.now()
val submissionSeed = crypto.Hash.hashPrivateKey(
"fetching contracts that have keys correctly fills in the transaction structur")
Copy link
Contributor

Choose a reason for hiding this comment

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

...transaction structure

@@ -388,13 +388,15 @@ object Value extends CidContainer1WithDefaultCidResolver[Value] {
}

object V1 {
val maxSuffixLength = 94
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm just wondering: from where does that magic number come from? If you would like to follow the Scala style guide this constant should be MaxSuffixLength.

remyhaemmerle-da added a commit that referenced this pull request Jun 11, 2020
remyhaemmerle-da added a commit that referenced this pull request Jun 11, 2020
remyhaemmerle-da added a commit that referenced this pull request Jun 11, 2020
CHANGELOG_BEGIN
CHANGELOG_END
remyhaemmerle-da added a commit that referenced this pull request Jun 11, 2020
CHANGELOG_BEGIN
CHANGELOG_END
remyhaemmerle-da added a commit that referenced this pull request Jun 11, 2020
CHANGELOG_BEGIN
CHANGELOG_END
remyhaemmerle-da added a commit that referenced this pull request Jun 12, 2020
CHANGELOG_BEGIN
CHANGELOG_END
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/daml-engine DAML-LF Engine & Interpreter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants