[Snyk] Security upgrade python from 3.13.2 to 3.14-rc-slim-bookworm

[fronzec]

Snyk has created this PR to fix 3 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

• memkv/__scripts__/locust/reads/Dockerfile

We recommend upgrading to python:3.14-rc-slim-bookworm, as this image has only 37 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Cross-site Scripting (XSS) SNYK-DEBIAN12-MERCURIAL-9486687	586
	Cross-site Scripting (XSS) SNYK-DEBIAN12-MERCURIAL-9486687	586
	Integer Overflow or Wraparound SNYK-DEBIAN12-ZLIB-6008963	500
	Integer Overflow or Wraparound SNYK-DEBIAN12-ZLIB-6008963	500
	CVE-2024-55549 SNYK-DEBIAN12-LIBXSLT-9407504	436

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

Summary by CodeRabbit

• Chores
  • Updated the container’s runtime environment to a new Python version, enhancing performance and compatibility.

[coderabbitai]

Walkthrough

The Dockerfile used within the locust testing module has been updated. Specifically, the base image has been changed from python:3.13.2 to python:3.14-rc-slim-bookworm, adjusting the runtime environment for the container.

Changes

Files	Change Summary
memkv/scripts/locust/reads/Dockerfile	Updated the base image from python:3.13.2 to python:3.14-rc-slim-bookworm.

Poem

I’m a rabbit with a tweak so fine,
Hopping through lines of Docker design.
Python’s new base now leaps ahead,
A change so crisp, exactly as said.
Hooray for new code, in every line!
🐇✨

---

🪧 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[fronzec]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

memkv/__scripts__/locust/reads/Dockerfile (1)

3-3: Package Installation Check

The RUN pip3 install locust command installs the latest version of Locust without version pinning. For enhanced stability and reproducibility—especially considering the switch to an RC Python version—it may be beneficial to pin Locust to a known good version.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 72e9216 and b515810.

📒 Files selected for processing (1)

• memkv/__scripts__/locust/reads/Dockerfile (1 hunks)

🔇 Additional comments (2)

memkv/__scripts__/locust/reads/Dockerfile (2)

1-1: Base Image Upgrade Review

The Dockerfile now uses python:3.14-rc-slim-bookworm as its base image, which helps mitigate the vulnerabilities identified by Snyk. However, note that this is a release candidate version. Please verify that all your dependencies (e.g., Locust) and scripting within the container are fully compatible and stable with this RC release before deploying to production.

---

5-5: Environment Configuration Confirmation

Setting ENV PYTHONUNBUFFERED=1 is a standard and good practice in Docker containers to prevent output buffering. This configuration will help ensure that the logs are streamed directly to the console.