-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Server v2 start & helpers #20288
Server v2 start & helpers #20288
Conversation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Can we have a PR targeting main first with the simplification of server context? |
core/go.mod
Outdated
@@ -4,27 +4,66 @@ go 1.21 | |||
|
|||
require ( | |||
cosmossdk.io/log v1.3.1 | |||
github.com/cometbft/cometbft v0.38.7 |
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.
big no no
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.
So we shouldn't import comet into core?
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.
Yes, no comet, no sdk and as little as dep as possible in core.
core/context/server_context.go
Outdated
type ServerContext interface { | ||
GetLogger() log.Logger | ||
GetViper() *viper.Viper | ||
GetConfig() *cmtcfg.Config | ||
} | ||
|
||
func GetServerContextFromCmd(cmd *cobra.Command) ServerContext { | ||
if v := cmd.Context().Value(ServerContextKey); v != nil { | ||
fmt.Println("serverCtxPtr", v) | ||
serverCtxPtr := v.(ServerContext) | ||
return serverCtxPtr | ||
} | ||
return nil | ||
} |
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.
this is specific to server/v2 it can live there. Ideally there is no comet deep in server/v2 as well
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.
Make sense, I will make *cmtcfg.Config
as an interface
@hieuvubk your pull request is missing a changelog! |
As think we can close this. As there is a or targeting main. And we do not put anything in the release branch anymore. |
Description
Closes: #19720
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
ServerContext
v2. Will get config from viper.ServerContext
as interface. v1 & v2 context should be used around this interfaceReviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...