feat(proxyd): add smoke test

[felipe-op]

Description

Adds a simple smoke test case to check proxyd has initialized and shutdown correctly, with proper log output.

Tests

go test ./...

Additional context

• Regression introduced by Update op-geth dependency to upstream geth v1.13.8 and migrate to slog #8917
• Fix fix(proxyd): log initialization #9785

Metadata

Fixes https://github.com/ethereum-optimism/devinfra-pod/issues/109

[coderabbitai]

Walkthrough

The recent updates aim to streamline logging configuration and bolster testing capabilities in the proxyd project. Centralizing logging setup enhances code clarity. A new integration test and configuration file are introduced to validate proxyd service initialization and functionality through simulated environments and RPC requests.

Changes

File(s)	Change Summary
cmd/proxyd/main.go	Refactored logging setup to use proxyd.SetLogLevel.
integration_tests/smoke_test.go, integration_tests/testdata/smoke.toml	Introduced a new integration test and configuration file for testing proxyd initialization and functionality.
proxyd.go	Added SetLogLevel function for logging and updated Start to include the new logging setup. Added ConsensusHARedis field to BackendGroupConfig.

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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>.
  • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.