-
Notifications
You must be signed in to change notification settings - Fork 618
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
feat: adding cross_contract_calls integration test for the V1->V2 resharding #9402
Changes from all commits
8319833
7998eda
0f6edbb
368ba9d
51f81a9
0302b06
6b8b0ca
bb682a5
d2b6e3f
2809487
b93c48a
5a101eb
53087c4
bd6a273
8a91db0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -61,4 +61,4 @@ rusty-tags.vi | |
# Estimator generated files | ||
costs-*.txt | ||
names-to-stats.txt | ||
data_dump_*.bin | ||
data_dump_*.bin | ||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,6 +18,8 @@ rand_hc.workspace = true | |
serde_json.workspace = true | ||
smart-default.workspace = true | ||
tracing.workspace = true | ||
# itertools has collect_vec which is useful in quick debugging prints | ||
itertools.workspace = true | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same here: are you actually using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah I usually use collect_vec when printing debug logs. How would you feel about leaving that in? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Generally speaking, I don't really like adding dependencies that aren't used in committed code. It's the kind of thing I personally might create a PR, just to remove a dead dependency. So at least a comment why it's in would be useful to prevent that sort of engineers canceling out each others "improvements". But that said, itertools wouldn't be the worst to have pulled in for no reason, so I won't stop you from adding it if you hate writing There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, thanks, I'll leave that in and add a comment. |
||
|
||
near-crypto.workspace = true | ||
near-primitives.workspace = true | ||
|
@@ -28,7 +30,9 @@ near-cache.workspace = true | |
|
||
[features] | ||
expensive_tests = [] | ||
protocol_feature_fix_staking_threshold = ["near-primitives/protocol_feature_fix_staking_threshold"] | ||
protocol_feature_fix_staking_threshold = [ | ||
"near-primitives/protocol_feature_fix_staking_threshold", | ||
] | ||
nightly = [ | ||
"nightly_protocol", | ||
"protocol_feature_fix_staking_threshold", | ||
|
@@ -43,7 +47,4 @@ nightly_protocol = [ | |
"near-store/nightly_protocol", | ||
] | ||
no_cache = [] | ||
new_epoch_sync = [ | ||
"near-store/new_epoch_sync", | ||
"near-primitives/new_epoch_sync" | ||
] | ||
new_epoch_sync = ["near-store/new_epoch_sync", "near-primitives/new_epoch_sync"] |
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.
nit: we should not be changing this file