-
Notifications
You must be signed in to change notification settings - Fork 446
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
t8n test #7744
base: master
Are you sure you want to change the base?
t8n test #7744
Conversation
@rubo should we add it to github actions? |
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.
Would be better if we could have testdata
as submodule, discussed options on slack. If not possible, it is acceptable to leave as is.
@@ -29,7 +29,7 @@ public ReceiptForRpc(Hash256 txHash, TxReceipt receipt, TxGasInfo gasInfo, int l | |||
BlobGasPrice = gasInfo.BlobGasPrice; | |||
From = receipt.Sender; | |||
To = receipt.Recipient; | |||
ContractAddress = receipt.ContractAddress; | |||
ContractAddress = receipt.ContractAddress ?? Address.Zero; |
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 would we serialize Address.Zero
for transactions that don't create contracts?
This will also affect all the RPC method, are we sure we want to do it?
If we don't want to change RPC methods, but we want to change it here, you can inherit ReceiptForRpc
and add this logic in the derived class.
} | ||
|
||
[Test] | ||
public void Test6() |
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.
Can you name tests in some sensible way? I see it is based on testdata
so Test13_txs_London
?
@@ -95,6 +95,6 @@ private static (ISpecProvider, IReleaseSpec) GetSpec(T8nCommandArguments argumen | |||
specProvider.UpdateMergeTransitionInfo(env.CurrentNumber, 0); | |||
} | |||
|
|||
return (specProvider, overridableReleaseSpec); | |||
return (specProvider, overridableReleaseSpec, spec); |
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 do you need to differentiate between 2x release specs?
{ | ||
public IReleaseSpec Spec { get; set; } = spec; | ||
public IReleaseSpec OverridableReleaseSpec { get; set; } = overridableReleaseSpec; |
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.
confusing
added t8n tests, fixed t8n code
What types of changes does your code introduce?
Testing
Requires testing
If yes, did you write tests?
Notes on testing
Optional. Remove if not applicable.
Documentation
Requires documentation update
If yes, link the PR to the docs update or the issue with the details labeled
docs
. Remove if not applicable.Requires explanation in Release Notes
If yes, fill in the details here. Remove if not applicable.
Remarks
Optional. Remove if not applicable.