fix: fix test result sha256

[njzjz]

Summary by CodeRabbit

• Tests
  • Updated the reaction_sha256 field to support multiple values, improving test coverage.

[coderabbitai]

Walkthrough

Walkthrough

The recent modification involves changing the reaction_sha256 field in the test.json file from a single string to an array of strings. This update aims to accommodate multiple SHA-256 reactions within the same field, enhancing the flexibility and scalability of data storage.

Changes

File	Change Summary
tests/test.json	Modified reaction_sha256 field from a single string to an array of strings.

Sequence Diagram(s)

This section is not applicable as the changes are straightforward and do not impact control flow or introduce new features.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8e22614 and 09ac547.

Files selected for processing (1)

• tests/test.json (1 hunks)

Additional comments not posted (3)

tests/test.json (3)

43-46: LGTM! The change from a single string to an array of strings is correctly formatted.

The reaction_sha256 field now holds an array of valid SHA256 hashes.

---

Line range hint 63-66:
LGTM! The change from a single string to an array of strings is correctly formatted.

The reaction_sha256 field now holds an array of valid SHA256 hashes.

---

Line range hint 83-87:
LGTM! The change from a single string to an array of strings is correctly formatted.

The reaction_sha256 field now holds an array of valid SHA256 hashes.

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.04%. Comparing base (8e22614) to head (09ac547).
Report is 21 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2256      +/-   ##
==========================================
- Coverage   95.18%   95.04%   -0.14%     
==========================================
  Files          18       18              
  Lines        1432     1432              
==========================================
- Hits         1363     1361       -2     
- Misses         69       71       +2     

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

[codspeed-hq]

CodSpeed Performance Report

Merging #2256 will not alter performance

_{Comparing njzjz:fix-sha256 (09ac547) with master (8e22614)}

Summary

✅ 8 untouched benchmarks