-
Notifications
You must be signed in to change notification settings - Fork 176
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: empty REST chain-id #1146
fix: empty REST chain-id #1146
Conversation
- chain-id flag was changed to chain
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1146 +/- ##
===========================================
+ Coverage 76.40% 76.59% +0.19%
===========================================
Files 53 53
Lines 5929 5922 -7
===========================================
+ Hits 4530 4536 +6
+ Misses 1139 1128 -11
+ Partials 260 258 -2 ☔ View full report in Codecov by Sentry. |
@@ -76,7 +75,7 @@ func StartRestServer(mainCtx ctx.Context, cdc *codec.Codec, registerRoutesFn fun | |||
logger.Info( | |||
fmt.Sprintf( | |||
"Starting application REST service (chain-id: %q)...", | |||
viper.GetString(flags.FlagChainID), |
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.
I see this value comes from our fork of cosmos-sdk
.
I'd probably change the flag value here and raise a PR against maticnetwork/cosmos-sdk
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.
That actually came to my mind too, but didn't want to touch that repo. Btw, let's close this PR once that sdk is modified since that already fixes the issue.
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.
Hey @mrostamii, would you be raising the PR on our cosmos fork ?
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.
@marcello33 @Raneet10 Maybe better to change FlagChainID
to FlagChain
in both repositories? Tested locally and it was fine, but not sure if it's an accepted strategy.
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.
Yeah that sounds good, please proceed @mrostamii
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.
Hey @mrostamii any update on this? Also, please change target branch to develop
. Thank you.
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.
Done.
CC @marcello33 @Raneet10
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.
@mrostamii once the cosmos PR is merged, the version in heimdall should be updated with a new release and this field flags.FlagChainID
(now changed to string "chain
") needs to be updated to flags.FlagChain
- from heimdall level and cosmos-sdk
Related PR on cosmos-sdk: |
Thanks @mrostamii |
@marcello33 CI got failed because |
Right, thanks, that's what I mentioned here |
This PR is stale because it has been open 21 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
@mrostamii @marcello33 Have approved the cosmos PR. Feel free to proceed. |
Closing this in favour of #1169 |
Hi @mrostamii
I believe renaming that var from Please, keep in mind that the commands for Also, we were not able to fully understand what issues the empty rest chain-id causes to you, as it is anyway working on all networks, and no error is thrown. Thank you for your understanding, and again for your contribution. |
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.
As per latest comment, heimdallcli
to be fixed and conflicts resolved
Description
The REST service's initial log had an empty value of
chain-id
.Changes
Checklist
Testing
Cross repository changes
This PR requires changes to cosmos-sdk
Manual tests
out of this PR
in this PR