Skip to content
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

refactor(server/v2/cometbft): add codec.Codec and clean-up APIs #22566

Merged
merged 4 commits into from
Nov 20, 2024

Conversation

julienrbrt
Copy link
Member

@julienrbrt julienrbrt commented Nov 20, 2024

Description

Closes: #21105

Use codec.Codec as issue described.
Clean-up APIs by leaking fewer types and APIs.
The comet server now exposes the cometbft.Application instead of the internal consensus type.


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...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers 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.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features

    • Enhanced streaming management and snapshot handling capabilities.
    • Introduction of a new interface for transaction simulation in gRPC services.
  • Bug Fixes

    • Improved error handling in various consensus-related methods and commands.
  • Refactor

    • Renamed Consensus to consensus for clarity across multiple components.
    • Streamlined initialization processes for the consensus server and related services.
  • Documentation

    • Updated comments for clarity in the commands and server initialization.

Copy link
Contributor

coderabbitai bot commented Nov 20, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request introduces significant refactoring of the Consensus structure and its associated methods across multiple files in the server/v2/cometbft package. Key changes include renaming the Consensus type to consensus, modifying method signatures, and enhancing error handling. Structural adjustments were made to improve clarity and maintainability, including the addition of new fields and interfaces. The changes affect how instances are created and managed, particularly in relation to gRPC service registration and consensus state handling.

Changes

File Path Change Summary
server/v2/cometbft/abci.go Renamed Consensus to consensus, updated method receivers, removed NewConsensus, and modified error handling.
server/v2/cometbft/abci_test.go Refactored setUpConsensus to return *consensus[mock.Tx], altered initialization logic.
server/v2/cometbft/commands.go Simplified command logic by removing Consensus layer in BootstrapStateCmd, updated error handling.
server/v2/cometbft/grpc.go Introduced appSimulator interface, modified GRPCServiceRegistrar, updated service registration logic.
server/v2/cometbft/options.go Added StreamingManager and SnapshotExtensions fields to ServerOptions, updated initialization logic.
server/v2/cometbft/query.go Updated method receivers from Consensus[T] to consensus[T], maintained existing query handling logic.
server/v2/cometbft/server.go Changed Consensus field to abci.Application, modified constructor and added GRPCServiceRegistrar method.
server/v2/cometbft/snapshots.go Updated method receivers to consensus[T], preserved existing snapshot handling logic.
server/v2/cometbft/streaming.go Renamed receiver from Consensus[T] to consensus[T], replaced streaming field with streamingManager.
server/v2/cometbft/utils.go Updated method receivers to consensus[T], modified types in GetConsensusParams.
simapp/v2/simdv2/cmd/commands.go Updated InitRootCmd to pass simApp.AppCodec() for ConsensusServer initialization, refined comments.

Assessment against linked issues

Objective Addressed Explanation
Use codec to parse gRPC requests (#[21105])

Possibly related PRs

Suggested labels

C:server/v2 api, C:Store

Suggested reviewers

  • kocubinski
  • facundomedica
  • sontrinh16
  • hieuvubk
  • tac0turtle
  • testinginprod

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Nov 20, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🧹 Outside diff range and nitpick comments (11)
server/v2/cometbft/options.go (1)

50-52: Consider more robust default initialization

The current initialization with empty values might lead to runtime issues if not properly overridden.

Consider this approach:

-StreamingManager:           streaming.Manager{},
+StreamingManager:           streaming.NewManager(), // if available
-SnapshotExtensions:         []snapshots.ExtensionSnapshotter{},
+SnapshotExtensions:         make([]snapshots.ExtensionSnapshotter, 0),
server/v2/cometbft/query.go (1)

Line range hint 14-33: Consider enhancing error messages for better debugging

The implementation looks good with proper validation and error handling. However, the error messages could be more specific to help with debugging.

Consider including the actual path length in the error message:

-		return nil, errorsmod.Wrap(cometerrors.ErrUnknownRequest, "path should be p2p filter <addr|id> <parameter>")
+		return nil, errorsmod.Wrapf(cometerrors.ErrUnknownRequest, "path should be p2p filter <addr|id> <parameter>; got %d elements", len(path))
server/v2/cometbft/streaming.go (3)

Line range hint 22-42: Consider extracting transaction result conversion logic

The transaction result conversion logic could be moved to a separate helper function to improve readability and maintainability.

+func convertToStreamingTxResults(txResults []server.TxResult, cfg Config) ([]*streaming.ExecTxResult, error) {
+    streamingTxResults := make([]*streaming.ExecTxResult, len(txResults))
+    for i, txResult := range txResults {
+        space, code, log := errorsmod.ABCIInfo(txResult.Error, cfg.AppTomlConfig.Trace)
+
+        events, err := streaming.IntoStreamingEvents(txResult.Events)
+        if err != nil {
+            return nil, err
+        }
+
+        streamingTxResults[i] = &streaming.ExecTxResult{
+            Code:      code,
+            Codespace: space,
+            Log:       log,
+            GasWanted: uint64ToInt64(txResult.GasWanted),
+            GasUsed:   uint64ToInt64(txResult.GasUsed),
+            Events:    events,
+        }
+    }
+    return streamingTxResults, nil
+}

Line range hint 43-58: Optimize events conversion by moving it outside the loop

The events conversion is currently performed for each listener, which is inefficient. Consider moving it outside the loop.

+    events, err := streaming.IntoStreamingEvents(events)
+    if err != nil {
+        return err
+    }
     for _, streamingListener := range c.streamingManager.Listeners {
-        events, err := streaming.IntoStreamingEvents(events)
-        if err != nil {
-            return err
-        }
         if err := streamingListener.ListenDeliverBlock(ctx, streaming.ListenDeliverBlockRequest{

Line range hint 59-104: Multiple TODOs referencing issue #22009 need implementation

There are several TODOs related to header and JSON handling that need to be addressed. These are currently tracked in issue #22009.

Would you like me to help create implementation proposals for these TODOs or create subtasks in the issue tracker?

server/v2/cometbft/snapshots.go (1)

Line range hint 68-91: Consider pre-allocating the response snapshots slice

While the implementation is correct, consider pre-allocating the slice to avoid potential reallocations:

- resp := &abci.ListSnapshotsResponse{}
+ resp := &abci.ListSnapshotsResponse{
+    Snapshots: make([]*abci.Snapshot, 0, len(snapshots)),
+ }
server/v2/cometbft/utils.go (2)

Line range hint 271-304: Add documentation for height validation cases

While the implementation is correct, consider adding documentation to explain the different height validation scenarios:

  1. First block with initial height > 1
  2. First block with initial height = 1
  3. Subsequent blocks

This will help future maintainers understand the logic more easily.


305-323: Improve error handling in type assertion

The type assertion error handling could be enhanced to provide more context about the failure.

Consider this improvement:

-	if r, ok := res.(*types.QueryParamsResponse); !ok {
-		return nil, errors.New("failed to query consensus params")
+	r, ok := res.(*types.QueryParamsResponse)
+	if !ok {
+		return nil, fmt.Errorf("unexpected response type %T, expected *types.QueryParamsResponse", res)
server/v2/cometbft/grpc.go (2)

35-41: Consider grouping function parameters into a struct

The gRPCServiceRegistrar function has multiple parameters, which may affect readability. Consider grouping related parameters into a configuration struct to simplify the function signature and improve maintainability.


221-223: Wrap consensus info error with gRPC status

When s.consensus.Info returns an error, it's advisable to convert it into a gRPC status error for consistency in error handling.

Apply this diff to wrap the error:

	if err != nil {
-		return nil, err
+		return nil, status.Errorf(codes.Internal, "failed to get consensus info: %v", err)
	}
server/v2/cometbft/server.go (1)

372-374: Add proper doc comment for exported function GRPCServiceRegistrar

The comment for the exported function GRPCServiceRegistrar should start with the function name to comply with Go conventions.

Apply this diff to correct the documentation comment:

- // gRPCServiceRegistrar returns a function that registers the CometBFT gRPC service
+ // GRPCServiceRegistrar returns a function that registers the CometBFT gRPC service
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3d618f5 and 8daaa0f.

📒 Files selected for processing (11)
  • server/v2/cometbft/abci.go (14 hunks)
  • server/v2/cometbft/abci_test.go (3 hunks)
  • server/v2/cometbft/commands.go (1 hunks)
  • server/v2/cometbft/grpc.go (7 hunks)
  • server/v2/cometbft/options.go (3 hunks)
  • server/v2/cometbft/query.go (3 hunks)
  • server/v2/cometbft/server.go (5 hunks)
  • server/v2/cometbft/snapshots.go (4 hunks)
  • server/v2/cometbft/streaming.go (2 hunks)
  • server/v2/cometbft/utils.go (4 hunks)
  • simapp/v2/simdv2/cmd/commands.go (3 hunks)
🧰 Additional context used
📓 Path-based instructions (11)
server/v2/cometbft/abci.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

server/v2/cometbft/abci_test.go (2)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

server/v2/cometbft/commands.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

server/v2/cometbft/grpc.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

server/v2/cometbft/options.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

server/v2/cometbft/query.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

server/v2/cometbft/server.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

server/v2/cometbft/snapshots.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

server/v2/cometbft/streaming.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

server/v2/cometbft/utils.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

simapp/v2/simdv2/cmd/commands.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

🔇 Additional comments (22)
server/v2/cometbft/options.go (3)

11-12: LGTM: Clean import additions

The new imports for streaming and snapshots are properly organized and align with the new functionality being added.


27-28: LGTM: Improved documentation

The added comment clarifies the purpose of the Mempool field, enhancing code readability.


29-34: Consider adding validation for StreamingManager and SnapshotExtensions

While the new fields are well-documented, consider adding validation in the server initialization to ensure these components are properly configured, especially since they're critical for consensus operations.

For example, you might want to:

  1. Validate that StreamingManager is properly initialized before server start
  2. Ensure SnapshotExtensions implementations are compatible with your snapshot strategy
server/v2/cometbft/query.go (1)

Line range hint 86-134: Address TODO comment and verify proof handling

The implementation looks good overall, but there are two points to consider:

  1. There's a TODO comment about fastpath optimization that should be addressed
  2. The proof handling creates a new ProofOps struct with a single operation, which might not be the intended behavior if multiple proof operations are expected

Would you like me to help investigate the fastpath optimization mentioned in the TODO comment?

server/v2/cometbft/streaming.go (1)

Line range hint 15-21: LGTM! Verify impact of receiver type change.

The method signature follows Go best practices. The change from Consensus[T] to consensus[T] aligns with the PR objectives to reduce type exposure.

server/v2/cometbft/snapshots.go (3)

Line range hint 37-65: LGTM! Well-structured error handling and logging

The implementation properly handles different error cases with appropriate ABCI responses and includes contextual error logging.


Line range hint 94-112: LGTM! Comprehensive error handling with contextual logging

The implementation includes proper nil checks and detailed error logging with relevant context.


Line range hint 115-164: Review and update the IAVL stores comment

The implementation is solid, but there's a comment that might need review:

// We currently don't support resetting the IAVL stores and retrying a
// different snapshot, so we ask CometBFT to abort all snapshot restoration.

Please verify if this limitation still applies or if it should be updated to reflect current capabilities.

simapp/v2/simdv2/cmd/commands.go (3)

43-43: LGTM: Minor documentation improvement

The comment wording enhancement provides slightly better clarity.


109-114: LGTM: Proper codec integration

The addition of simApp.AppCodec() aligns with the PR objective of implementing codec.Codec for proper request parsing. The parameter ordering is correct, with the codec injected before the global config.


133-136: LGTM: Improved API structure

The simplified path to GRPCServiceRegistrar reduces API surface area and improves maintainability while preserving functionality. This change aligns well with the PR's objective of cleaning up APIs.

server/v2/cometbft/utils.go (3)

22-22: LGTM: Import addition is appropriate

The addition of the consensus types import is necessary for the new query parameter types.


Line range hint 324-378: LGTM: Well-structured block retention logic

The implementation effectively handles all edge cases and includes clear documentation explaining the retention height calculation process.


Line range hint 379-394: LGTM: Clear halt condition implementation

The halt condition checking is well-implemented with informative error messages.

server/v2/cometbft/commands.go (1)

391-394: LGTM: API simplification aligns with refactoring goals

The change simplifies store access by removing the unnecessary Consensus layer while maintaining the same functionality and error handling. This aligns well with the PR's objective of cleaning up APIs and reducing exposure of internal types.

server/v2/cometbft/abci_test.go (3)

9-9: LGTM: Import addition for sync package

The sync package import is correctly added to support the new OnceValues functionality used in consensus initialization.


Line range hint 641-713: Verify test coverage for new consensus initialization

The setUpConsensus function has been updated to use the new consensus type and initialization pattern. While the changes look correct, consider adding specific test cases to verify:

  1. The behavior of getProtoRegistry with the new sync.OnceValues implementation
  2. Edge cases around registry initialization

Consider extracting the consensus configuration into a separate test helper function to improve test maintainability:

func getTestConsensusConfig() Config {
    return Config{
        AppTomlConfig: DefaultAppTomlConfig(),
    }
}

Line range hint 641-713: Add test cases for proto registry initialization

While the test suite provides good coverage for consensus operations, consider adding specific test cases for:

  • Proto registry initialization behavior
  • Concurrent access patterns to the registry
  • Error cases in registry initialization

Example test case structure:

func TestConsensus_ProtoRegistry(t *testing.T) {
    c := setUpConsensus(t, 100_000, mempool.NoOpMempool[mock.Tx]{})
    
    // Test concurrent access
    var wg sync.WaitGroup
    for i := 0; i < 10; i++ {
        wg.Add(1)
        go func() {
            defer wg.Done()
            registry := c.getProtoRegistry()
            require.NotNil(t, registry)
        }()
    }
    wg.Wait()
}
server/v2/cometbft/grpc.go (3)

28-30: LGTM: Definition of appSimulator interface

The appSimulator interface is correctly defined and enhances abstraction.


99-100: LGTM: Updates to txServer struct

Adding txCodec and app fields to the txServer struct aligns with the new architecture and is implemented correctly.


200-202: LGTM: Updates to nodeServer struct

The addition of cfg, cometBFTAppConfig, and consensus fields to the nodeServer struct is appropriate and fits the refactoring objectives.

server/v2/cometbft/server.go (1)

55-55: Verify that consensus[T] implements abci.Application interface

The assignment of &consensus[T]{...} to srv.Consensus requires that consensus[T] implements the abci.Application interface. Please ensure that consensus[T] fully implements all required methods for seamless integration.

Also applies to: 167-192

server/v2/cometbft/query.go Outdated Show resolved Hide resolved
server/v2/cometbft/grpc.go Show resolved Hide resolved
server/v2/cometbft/grpc.go Show resolved Hide resolved
server/v2/cometbft/grpc.go Outdated Show resolved Hide resolved
server/v2/cometbft/abci.go Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (3)
server/v2/cometbft/abci.go (3)

Line range hint 292-375: Consider adding debug logs for state initialization steps

While the implementation is solid, adding debug logs for key initialization steps would help with troubleshooting.

 func (c *consensus[T]) InitChain(ctx context.Context, req *abciproto.InitChainRequest) (*abciproto.InitChainResponse, error) {
     c.logger.Info("InitChain", "initialHeight", req.InitialHeight, "chainID", req.ChainId)
+    c.logger.Debug("Starting genesis state initialization")
     
     // store chainID to be used later on in execution
     c.chainID = req.ChainId

Line range hint 446-535: Consider batching mempool removals

The current implementation removes transactions from the mempool one by one. Consider batching these operations for better performance.

-// remove txs from the mempool
-for _, tx := range decodedTxs {
-    if err = c.mempool.Remove(tx); err != nil {
-        return nil, fmt.Errorf("unable to remove tx: %w", err)
-    }
-}
+// remove txs from the mempool in batch
+if err = c.mempool.RemoveBatch(decodedTxs); err != nil {
+    return nil, fmt.Errorf("unable to remove txs: %w", err)
+}

Line range hint 554-635: Consider consolidating vote extension enablement checks

The duplicate logic for checking vote extension enablement could be extracted into a helper method for better maintainability.

+func (c *consensus[T]) isVoteExtensionEnabled(cp *consensustypes.MsgUpdateParams, height int64) bool {
+    if cp.Feature.VoteExtensionsEnableHeight != nil && 
+       height >= cp.Feature.VoteExtensionsEnableHeight.Value && 
+       cp.Feature.VoteExtensionsEnableHeight.Value != 0 {
+        return true
+    }
+    return cp.Abci != nil && 
+           height >= cp.Abci.VoteExtensionsEnableHeight && 
+           cp.Abci.VoteExtensionsEnableHeight != 0
+}
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8daaa0f and 65b56ec.

📒 Files selected for processing (3)
  • server/v2/cometbft/abci.go (15 hunks)
  • server/v2/cometbft/grpc.go (7 hunks)
  • server/v2/cometbft/query.go (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • server/v2/cometbft/query.go
🧰 Additional context used
📓 Path-based instructions (2)
server/v2/cometbft/abci.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

server/v2/cometbft/grpc.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

🔇 Additional comments (7)
server/v2/cometbft/grpc.go (4)

27-29: LGTM: Well-defined generic interface

The appSimulator[T] interface is well-designed with clear generic constraints and a focused single responsibility for transaction simulation.


34-47: LGTM: Clean dependency injection

The refactored function follows good design principles by:

  • Accepting specific dependencies rather than a large consensus object
  • Using the new codec interface for transaction handling
  • Properly registering all required gRPC services

97-99: LGTM: Clean separation of concerns

The txServer struct now properly separates transaction coding and simulation responsibilities.


Line range hint 219-231: LGTM: Proper error handling in Status method

The Status method correctly uses the ABCI Application interface and properly handles potential errors from the Info call.

server/v2/cometbft/abci.go (3)

49-66: LGTM! Good encapsulation of the consensus type

The change to make consensus unexported and the addition of appCodec improve encapsulation and codec handling respectively.


Line range hint 201-291: LGTM! Error handling improvements

The error wrapping format has been improved as per previous review suggestions.


Line range hint 376-445: LGTM! Robust implementation with proper validations

The implementations include proper height validation and clear error handling.

@julienrbrt julienrbrt requested a review from Copilot November 20, 2024 11:06

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 5 out of 11 changed files in this pull request and generated no suggestions.

Files not reviewed (6)
  • server/v2/cometbft/server.go: Evaluated as low risk
  • server/v2/cometbft/query.go: Evaluated as low risk
  • server/v2/cometbft/streaming.go: Evaluated as low risk
  • server/v2/cometbft/snapshots.go: Evaluated as low risk
  • server/v2/cometbft/commands.go: Evaluated as low risk
  • server/v2/cometbft/abci.go: Evaluated as low risk
@julienrbrt julienrbrt enabled auto-merge November 20, 2024 15:24
@julienrbrt julienrbrt disabled auto-merge November 20, 2024 15:47
@julienrbrt julienrbrt added this pull request to the merge queue Nov 20, 2024
Merged via the queue into main with commit efc05e8 Nov 20, 2024
75 of 76 checks passed
@julienrbrt julienrbrt deleted the julien/cleanup-cometbft branch November 20, 2024 15:57
mergify bot pushed a commit that referenced this pull request Nov 20, 2024
julienrbrt added a commit that referenced this pull request Nov 20, 2024
alpe added a commit that referenced this pull request Nov 21, 2024
* main:
  build(deps): Bump cosmossdk.io/math from 1.3.0 to 1.4.0 (#22580)
  fix(server/v2/api/telemetry): enable global metrics  (#22571)
  refactor(server/v2/cometbft): add `codec.Codec` and clean-up APIs (#22566)
  feat(core/coretesting): make memDB satisfy db.Db interface (#22570)
  Merge commit from fork
  fix(server(/v2)): fix fallback genesis path (#22564)
  fix: only overwrite context chainID when necessary (#22568)
  docs(client): Update setFeeGranter and setFeePayer comments (#22526)
  fix(baseapp): populate header info in `NewUncachedContext` (#22557)
  build(deps): Bump buf.build/gen/go/cometbft/cometbft/protocolbuffers/go from 1.35.1-20240701160653-fedbb9acfd2f.1 to 1.35.2-20240701160653-fedbb9acfd2f.1 in /api (#22551)
  build(deps): Bump github.com/creachadair/atomicfile from 0.3.5 to 0.3.6 in /tools/confix (#22552)
  docs: Update reference of Approximation (#22550)
  fix(server/v2/comebft): wire missing services + fix simulation (#21964)
  ci: fix permissions for GITHUB_TOKEN on dependabot workflows (#22547)
  ci: fix permissions for GITHUB_TOKEN in spell check workflow (#22545)
  build(deps): Bump google.golang.org/protobuf from 1.35.1 to 1.35.2 (#22537)
  fix(cosmovisor): premature upgrade on restart (#22528)
  fix(store/v2/pebble): handle version 0 in keys (#22524)
  refactor(server/v2/telemetry): swap redirects (#22520)
  docs: Update content in  CODE_OF_CONDUCT.md (#22518)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release C:server/v2 cometbft C:server/v2 Issues related to server/v2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

change(serverv2/comet): use codec to parse gRPC requests
5 participants