remove the MPL2.0 license pkg

[CaiYueTing]

Summary by CodeRabbit

• Bug Fixes

  • Simplified error handling in the message cloning process, improving clarity and performance when encountering issues.

• Chores

  • Removed unnecessary dependencies, leading to a cleaner and more efficient project structure.

[coderabbitai]

Walkthrough

The recent changes streamline the error handling in the Clone method of the Message struct by removing the multierror dependency. The revised approach utilizes a simpler mechanism for error collection, enhancing code clarity and potentially improving performance. Additionally, the go.mod file reflects the removal of related dependencies, indicating a shift towards a less complex dependency graph.

Changes

File	Change Summary
go.mod	Removed dependencies: github.com/hashicorp/go-multierror and github.com/hashicorp/errwrap.
message/pool/message.go	Simplified error handling in the Clone method; replaced multierror with a slice of errors.

Poem

In the meadow, hops a clever hare,
Simplifying errors, with tender care!
Dependencies now light as a breeze,
A joyful leap, oh what a tease!
With each hop, clarity shines bright,
In the code where all feels right! 🐰✨

---

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

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between de76143 and cb34896.

Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

Files selected for processing (2)

• go.mod (2 hunks)
• message/pool/message.go (2 hunks)

Files skipped from review due to trivial changes (1)

• go.mod

Additional comments not posted (3)

message/pool/message.go (3)

620-620: Simplify error handling by using a slice of error strings.

The use of a slice of error strings (errStr) simplifies error handling by avoiding the multierror dependency.

---

623-623: Ensure error messages are appended correctly.

Appending the error message from the seek operation ensures all errors are captured.

---

625-625: Return a formatted error string.

Returning a formatted error string with the count of errors and the collected error messages improves clarity and readability.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cb34896 and c1d9fb8.

Files selected for processing (1)

• message/pool/message.go (2 hunks)

Additional comments not posted (3)

message/pool/message.go (3)

619-619: Simplified error collection.

The error collection mechanism has been simplified by using a slice of errors. This improves readability and maintainability.

---

622-622: Correctly appending seek error to the error slice.

The seek error is correctly appended to the error slice if it occurs.

---

624-624: Combining errors using errors.Join.

The use of errors.Join to combine errors is a good practice and aligns with modern Go error handling.

[jkralik]

Good job 👍

[Danielius1922]

@jkralik maybe we should add the licence scanner (fossa) that we have in other repositories here, hopefully it can be setup in such way to mark MPL as problematic. Because I'll forget about it in a week and we use the multierror package in other repositories, so I can easily see myself re-adding it in the future. 🤓