fix: core lint

[trajan0x]

Description

Fix lint issue introduced in #2802

[coderabbitai]

Warning

Rate limit exceeded

@trajan0x has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 41 minutes and 34 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 78123ff and 11889c0.

---

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

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.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

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.

[greptile-apps]

PR Summary

• Modified TestBytesToJSONString to use index-based iteration
• Addressed linting issue in core/bytes_test.go

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 25.61996%. Comparing base (1f4a910) to head (11889c0).
Report is 1 commits behind head on master.

Additional details and impacted files

@@                 Coverage Diff                 @@
##              master       #2807         +/-   ##
===================================================
- Coverage   25.70782%   25.61996%   -0.08787%     
===================================================
  Files            700         758         +58     
  Lines          51673       54399       +2726     
  Branches          80          80                 
===================================================
+ Hits           13284       13937        +653     
- Misses         37026       39035       +2009     
- Partials        1363        1427         +64     

Flag	Coverage Δ
agents	34.35651% <ø> (+0.25887%)	⬆️
cctp-relayer	31.93780% <ø> (?)
core	61.31616% <ø> (-0.10445%)	⬇️
ethergo	48.47467% <ø> (-0.02799%)	⬇️
explorer	4.97877% <ø> (ø)
git-changes-action	23.69615% <ø> (ø)
omnirpc	33.03403% <ø> (-0.04727%)	⬇️
opbot	0.22305% <ø> (ø)
promexporter	9.86717% <ø> (?)
rfq	27.12163% <ø> (ø)
screener-api	30.50847% <ø> (ø)
scribe	18.17597% <ø> (ø)
tools	30.55118% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cloudflare-workers-and-pages]

Deploying sanguine-fe with    Cloudflare Pages

Latest commit:	11889c0
Status:	✅  Deploy successful!
Preview URL:	https://dcd7c52f.sanguine-fe.pages.dev
Branch Preview URL:	https://fix-core-test.sanguine-fe.pages.dev

View logs