-
Notifications
You must be signed in to change notification settings - Fork 214
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
Validity and timelocks #3249
Validity and timelocks #3249
Conversation
e0217f4
to
cff3a8f
Compare
049430a
to
d9619f1
Compare
bors try |
tryBuild failed: Looks like an hlint failure. Will fix and retry. |
d9619f1
to
6143f89
Compare
bors try |
tryBuild failed: Failure log extract:
I'll try and reproduce locally. UPDATE: This PASSES for me locally. I tried it 10 times, and it succeeded every time. (Regardless of the seed.) |
revert flock
add Data.Interval add Data.IntervalSpec revert adding Data.Interval
Justification: - Using `fromIntegral` can hide unsafe integral narrowing conversions. - Using `intCast` eliminates this class of error statically. When creating values of `Data.Interval.Extended`, we can use the `Finite` constructor instead of `fromIntegral`. The following expressions are equivalent: > Finite 1000 :: Extended Int Finite 1000 > fromIntegral 1000 :: Extended Int Finite 1000 > Finite 1000 == fromIntegral 1000 True
4ee5534
to
1b83219
Compare
This function takes a script and returns a list of slot intervals, rather than just a single interval.
bors r+ |
{ "withdrawal": "self" | ||
, "validity_interval": | ||
{ "invalid_before": "unspecified" | ||
, "invalid_hereafter": "unspecified" |
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.
Canceled. |
bors r+ |
3249: Validity and timelocks r=paweljakubas a=paweljakubas <!-- Detail in a few bullet points the work accomplished in this PR. Before you submit, don't forget to: * Make sure the GitHub PR fields are correct: ✓ Set a good Title for your PR. ✓ Assign yourself to the PR. ✓ Assign one or more reviewer(s). ✓ Link to a Jira issue, and/or other GitHub issues or PRs. ✓ In the PR description delete any empty sections and all text commented in <!--, so that this text does not appear in merge commit messages. * Don't waste reviewers' time: ✓ If it's a draft, select the Create Draft PR option. ✓ Self-review your changes to make sure nothing unexpected slipped through. * Try to make your intent clear: ✓ Write a good Description that explains what this PR is meant to do. ✓ Jira will detect and link to this PR once created, but you can also link this PR in the description of the corresponding Jira ticket. ✓ Highlight what Testing you have done. ✓ Acknowledge any changes required to the Documentation. --> - [x] reading properly validity from request body - [x] add checks on boundary precedence and quantity - [x] simplify how asset quantity is called in constructTransaction (in line with decodeTransaction) - [x] slot check - [x] make either validity bound optional - [x] introduce before bound to transaction context and propagate this to node's tx - [x] extend decodeTransaction to detect txValidityInterval (with integration testing) - [x] introducing slot computation of scripts - [x] script vs validity check - [x] timelock minting test on - [x] add unit tests in MintBurnSpec ### Comments <!-- Additional comments, links, or screenshots to attach, if any. --> ### Issue Number adp-1193 <!-- Reference the Jira/GitHub issue that this PR relates to, and which requirements it tackles. Note: Jira issues of the form ADP- will be auto-linked. --> Co-authored-by: Pawel Jakubas <[email protected]> Co-authored-by: IOHK <[email protected]> Co-authored-by: Jonathan Knowles <[email protected]> Co-authored-by: Piotr Stachyra <[email protected]>
Build failed: |
0f9cfbc
to
b4be703
Compare
bors r+ |
3249: Validity and timelocks r=paweljakubas a=paweljakubas <!-- Detail in a few bullet points the work accomplished in this PR. Before you submit, don't forget to: * Make sure the GitHub PR fields are correct: ✓ Set a good Title for your PR. ✓ Assign yourself to the PR. ✓ Assign one or more reviewer(s). ✓ Link to a Jira issue, and/or other GitHub issues or PRs. ✓ In the PR description delete any empty sections and all text commented in <!--, so that this text does not appear in merge commit messages. * Don't waste reviewers' time: ✓ If it's a draft, select the Create Draft PR option. ✓ Self-review your changes to make sure nothing unexpected slipped through. * Try to make your intent clear: ✓ Write a good Description that explains what this PR is meant to do. ✓ Jira will detect and link to this PR once created, but you can also link this PR in the description of the corresponding Jira ticket. ✓ Highlight what Testing you have done. ✓ Acknowledge any changes required to the Documentation. --> - [x] reading properly validity from request body - [x] add checks on boundary precedence and quantity - [x] simplify how asset quantity is called in constructTransaction (in line with decodeTransaction) - [x] slot check - [x] make either validity bound optional - [x] introduce before bound to transaction context and propagate this to node's tx - [x] extend decodeTransaction to detect txValidityInterval (with integration testing) - [x] introducing slot computation of scripts - [x] script vs validity check - [x] timelock minting test on - [x] add unit tests in MintBurnSpec ### Comments <!-- Additional comments, links, or screenshots to attach, if any. --> ### Issue Number adp-1193 <!-- Reference the Jira/GitHub issue that this PR relates to, and which requirements it tackles. Note: Jira issues of the form ADP- will be auto-linked. --> Co-authored-by: Pawel Jakubas <[email protected]> Co-authored-by: IOHK <[email protected]> Co-authored-by: Jonathan Knowles <[email protected]>
Canceled. |
bors r+ |
Build succeeded: |
3267: Update tests / pending test against ADP-1738 r=piotr-iohk a=piotr-iohk - 58dbe4a Adjust e2e tests after API changes from #3249 - 71969cb Pending integration tests against ADP-1738 ### Comments Pending integration test `TRANS_NEW_CREATE_MINT_SCRIPTS` for ADP-1738 ![Screenshot from 2022-05-06 13-17-16](https://user-images.githubusercontent.com/42900201/167121713-6af508af-5670-4515-9ce7-37c42eaf04dd.png) ### Issue Number ADP-1738, ADP-1193 Co-authored-by: Piotr Stachyra <[email protected]>
3267: Update tests / pending test against ADP-1738 r=piotr-iohk a=piotr-iohk - 58dbe4a Adjust e2e tests after API changes from #3249 - 71969cb Pending integration tests against ADP-1738 ### Comments Pending integration test `TRANS_NEW_CREATE_MINT_SCRIPTS` for ADP-1738 ![Screenshot from 2022-05-06 13-17-16](https://user-images.githubusercontent.com/42900201/167121713-6af508af-5670-4515-9ce7-37c42eaf04dd.png) ### Issue Number ADP-1738, ADP-1193 Co-authored-by: Piotr Stachyra <[email protected]>
3267: Update tests / pending test against ADP-1738 r=piotr-iohk a=piotr-iohk - 58dbe4a Adjust e2e tests after API changes from #3249 - 71969cb Pending integration tests against ADP-1738 ### Comments Pending integration test `TRANS_NEW_CREATE_MINT_SCRIPTS` for ADP-1738 ![Screenshot from 2022-05-06 13-17-16](https://user-images.githubusercontent.com/42900201/167121713-6af508af-5670-4515-9ce7-37c42eaf04dd.png) ### Issue Number ADP-1738, ADP-1193 Co-authored-by: Piotr Stachyra <[email protected]>
3267: Update tests / pending test against ADP-1738 r=piotr-iohk a=piotr-iohk - 58dbe4a Adjust e2e tests after API changes from #3249 - 71969cb Pending integration tests against ADP-1738 ### Comments Pending integration test `TRANS_NEW_CREATE_MINT_SCRIPTS` for ADP-1738 ![Screenshot from 2022-05-06 13-17-16](https://user-images.githubusercontent.com/42900201/167121713-6af508af-5670-4515-9ce7-37c42eaf04dd.png) ### Issue Number ADP-1738, ADP-1193 Co-authored-by: Piotr Stachyra <[email protected]>
Comments
Issue Number
adp-1193