build(deps): update module github.com/dgraph-io/ristretto to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/dgraph-io/ristretto	v0.1.1 -> v2.1.0

---

Release Notes

dgraph-io/ristretto (github.com/dgraph-io/ristretto)

v2.1.0: Ristretto v2.1.0

Compare Source

What's Changed

• refactor: using defer m.Unlock in store.go by @​hoo47 in https://github.com/dgraph-io/ristretto/pull/425
• Add getting started doc by @​flymedllva in https://github.com/dgraph-io/ristretto/pull/428
• fix memory leak on incor calc of cleanup bucket by @​flymedllva in https://github.com/dgraph-io/ristretto/pull/429
• chore(deps): bump golang.org/x/sys from 0.28.0 to 0.29.0 in the minor group by @​dependabot in https://github.com/dgraph-io/ristretto/pull/430
• Add ShouldUpdate in config by @​harshil-goel in https://github.com/dgraph-io/ristretto/pull/427

Full Changelog: dgraph-io/ristretto@v2.0.1...v2.1.0

v2.0.1

Compare Source

Fixed

• Wait for goroutines to finish (#​423)
• Bump golang.org/x/sys from 0.27.0 to 0.28.0 in the minor group (#​421)
• Bump github.com/stretchr/testify from 1.9.0 to 1.10.0 in the minor group (#​420)
• Bump golang.org/x/sys from 0.26.0 to 0.27.0 in the minor group (#​419)

Full Changelog: dgraph-io/ristretto@v2.0.0...v2.0.1

v2.0.0

Compare Source

Breaking

• Support generic API
• Restrict generic key type to only those supported

Added

• Fix build with GOOS=js GOARCH=wasm

Fixed

• Disable mmap size check on arm arch as well as arm64
• Upgrade xxhash dependency to v2.2.0
• fix: race in close
• Fix some memory leaks in TTL implementation
• stop using rand.Seed()
• chore(deps): bump the actions group with 4 updates
• chore(deps): bump the minor group with 3 updates
• chore(deps): bump golang.org/x/sys from 0.25.0 to 0.26.0 in the minor group
• Remove the policy interface
• Perform validation to ensure that the three parameters, NumCounters, …
• set min version to go 1.21 in go.mod

Full Changelog: dgraph-io/ristretto@v0.2.0...v2.0.0

v1.0.1

Compare Source

This release is deprecated

v1.0.0

Compare Source

This release is deprecated

v0.2.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Finishing Touches

• 📝 Generate Docstrings

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

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.