-
Notifications
You must be signed in to change notification settings - Fork 375
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
fix: add support for custom node config file #1240
fix: add support for custom node config file #1240
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1240 +/- ##
==========================================
+ Coverage 47.50% 47.85% +0.34%
==========================================
Files 367 372 +5
Lines 62221 62989 +768
==========================================
+ Hits 29561 30142 +581
- Misses 30242 30390 +148
- Partials 2418 2457 +39
☔ View full report in Codecov by Sentry. |
While working on this PR I've come to the conclusion that our node init command is a total mess. There is are many side effects happening when specifying the configuration file (inits happening behind the scenes, private key load-in circus...). I patch one thing, and another problem pops up. It's practically impossible to test the I've been discussing with @gfanton internally, and we would like to tackle this problem head on - the node initialization flow needs to be crystal clear and cannot be blocking efforts as it is now |
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.
lgtm 👍
@moul ping for review 🙏 |
## Description This PR adds support for specifying a custom node configuration file using the `--tm2-node-config` flag. Resolves gnolang#1234 <details><summary>Contributors' checklist...</summary> - [x] Added new tests, or not needed, or not feasible - [x] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory - [x] Updated the official documentation or not needed - [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message was included in the description - [x] Added references to related issues and PRs - [x] Provided any useful hints for running manual tests - [x] Added new benchmarks to [generated graphs](https://gnoland.github.io/benchmarks), if any. More info [here](https://github.com/gnolang/gno/blob/master/.benchmarks/README.md). </details>
## Description This PR adds support for specifying a custom node configuration file using the `--tm2-node-config` flag. Resolves gnolang#1234 <details><summary>Contributors' checklist...</summary> - [x] Added new tests, or not needed, or not feasible - [x] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory - [x] Updated the official documentation or not needed - [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message was included in the description - [x] Added references to related issues and PRs - [x] Provided any useful hints for running manual tests - [x] Added new benchmarks to [generated graphs](https://gnoland.github.io/benchmarks), if any. More info [here](https://github.com/gnolang/gno/blob/master/.benchmarks/README.md). </details>
Description
This PR adds support for specifying a custom node configuration file using the
--tm2-node-config
flag.Resolves #1234
Contributors' checklist...
BREAKING CHANGE: xxx
message was included in the description