Skip to content

Conversation

@klauspost
Copy link
Owner

@klauspost klauspost commented Jul 2, 2025

Fixes #1081 (unreleased)

Summary by CodeRabbit

  • Bug Fixes

    • Corrected the order of input and output arguments in the compression function to ensure proper encoding behavior.
  • Tests

    • Added a new test to verify that compressed data can be correctly decompressed, ensuring data integrity across a range of files.
    • Improved test code organization by relocating variable declarations closer to their usage within benchmarks.

@coderabbitai
Copy link

coderabbitai bot commented Jul 2, 2025

📝 Walkthrough

"""

Walkthrough

The changes reverse the argument order in the EncodeAll call within the EncodeTo function to match the expected signature. A new test file for Go 1.24 is added to verify compression and decompression correctness using test data. Additionally, a benchmark variable is relocated for improved code locality.

Changes

File(s) Change Summary
zstd/simple_go124.go Reversed argument order in EncodeAll call within EncodeTo function.
zstd/simple_go124_test.go Added new Go 1.24-specific test verifying EncodeTo and DecodeTo with multiple test files.
zstd/zstd_test.go Moved data variable from package scope to local scope within BenchmarkMem function.

Sequence Diagram(s)

sequenceDiagram
    participant Test as TestEncodeTo
    participant File as Test File
    participant Zstd as zstd.EncodeTo/DecodeTo

    Test->>File: Open and read file content
    Test->>Zstd: EncodeTo(src, dst)
    Zstd-->>Test: Compressed data
    Test->>Zstd: DecodeTo(compressed, dst)
    Zstd-->>Test: Decompressed data
    Test->>Test: Compare decompressed to original
Loading

Assessment against linked issues

Objective Addressed Explanation
Correct argument order in EncodeTo to match Encoder.EncodeAll (Issue #1081)

Possibly related PRs


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 08c53b9 and 605b105.

📒 Files selected for processing (1)
  • zstd/simple_go124_test.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • zstd/simple_go124_test.go
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: fuzz-s2 ("noasm,nounsafe")
  • GitHub Check: fuzz-zstd ("noasm,nounsafe")
  • GitHub Check: build (1.24.x, windows-latest)
  • GitHub Check: build (1.23.x, windows-latest)
  • GitHub Check: build (1.24.x, ubuntu-latest)
  • GitHub Check: build (1.24.x, macos-latest)
  • GitHub Check: build (1.22.x, macos-latest)
  • GitHub Check: build (1.23.x, ubuntu-latest)
  • GitHub Check: fuzz-other ("noasm,nounsafe")
  • GitHub Check: build (1.22.x, ubuntu-latest)
  • GitHub Check: fuzz-other (nounsafe)
  • GitHub Check: fuzz-zstd (nounsafe)
  • GitHub Check: build (1.23.x, macos-latest)
  • GitHub Check: build (1.22.x, windows-latest)
  • GitHub Check: fuzz-s2 (nounsafe)
  • GitHub Check: build-special
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0792fc5 and 08c53b9.

📒 Files selected for processing (3)
  • zstd/simple_go124.go (1 hunks)
  • zstd/simple_go124_test.go (1 hunks)
  • zstd/zstd_test.go (1 hunks)
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: klauspost
PR: klauspost/compress#1014
File: s2/encode_amd64.go:38-45
Timestamp: 2024-10-04T06:29:01.060Z
Learning: In `s2/encode_amd64.go`, when handling temporary buffers, arrays are required instead of slices.
Learnt from: klauspost
PR: klauspost/compress#1014
File: s2/encode_amd64.go:38-45
Timestamp: 2024-10-16T10:14:26.389Z
Learning: In `s2/encode_amd64.go`, when handling temporary buffers, arrays are required instead of slices.
zstd/zstd_test.go (2)
Learnt from: klauspost
PR: klauspost/compress#1014
File: s2/encode_amd64.go:38-45
Timestamp: 2024-10-04T06:29:01.060Z
Learning: In `s2/encode_amd64.go`, when handling temporary buffers, arrays are required instead of slices.
Learnt from: klauspost
PR: klauspost/compress#1014
File: s2/encode_amd64.go:38-45
Timestamp: 2024-10-16T10:14:26.389Z
Learning: In `s2/encode_amd64.go`, when handling temporary buffers, arrays are required instead of slices.
zstd/simple_go124.go (2)
Learnt from: klauspost
PR: klauspost/compress#1014
File: s2/encode_amd64.go:38-45
Timestamp: 2024-10-04T06:29:01.060Z
Learning: In `s2/encode_amd64.go`, when handling temporary buffers, arrays are required instead of slices.
Learnt from: klauspost
PR: klauspost/compress#1014
File: s2/encode_amd64.go:38-45
Timestamp: 2024-10-16T10:14:26.389Z
Learning: In `s2/encode_amd64.go`, when handling temporary buffers, arrays are required instead of slices.
zstd/simple_go124_test.go (2)
Learnt from: klauspost
PR: klauspost/compress#1014
File: s2/encode_amd64.go:38-45
Timestamp: 2024-10-04T06:29:01.060Z
Learning: In `s2/encode_amd64.go`, when handling temporary buffers, arrays are required instead of slices.
Learnt from: klauspost
PR: klauspost/compress#1014
File: s2/encode_amd64.go:38-45
Timestamp: 2024-10-16T10:14:26.389Z
Learning: In `s2/encode_amd64.go`, when handling temporary buffers, arrays are required instead of slices.
⏰ Context from checks skipped due to timeout of 90000ms (11)
  • GitHub Check: build (1.24.x, ubuntu-latest)
  • GitHub Check: build (1.24.x, windows-latest)
  • GitHub Check: build (1.24.x, macos-latest)
  • GitHub Check: build (1.22.x, ubuntu-latest)
  • GitHub Check: build (1.22.x, macos-latest)
  • GitHub Check: fuzz-zstd ("noasm,nounsafe")
  • GitHub Check: fuzz-other ("noasm,nounsafe")
  • GitHub Check: fuzz-zstd (nounsafe)
  • GitHub Check: fuzz-other (nounsafe)
  • GitHub Check: build-special
  • GitHub Check: Analyze (go)
🔇 Additional comments (4)
zstd/simple_go124.go (1)

33-33: LGTM! Parameter order fix looks correct.

The change from enc.EncodeAll(dst, src) to enc.EncodeAll(src, dst) aligns with the consistent pattern used in DecodeTo (line 55) and follows typical compression API conventions where source comes before destination.

zstd/zstd_test.go (1)

124-124: Good refactoring: improved code locality.

Moving the data variable to local scope within the benchmark function improves code locality and reduces package-level scope pollution.

zstd/simple_go124_test.go (2)

48-57: Excellent test coverage for the parameter fix.

The round-trip test properly validates that the EncodeTo/DecodeTo parameter order fix works correctly by ensuring compressed data can be decompressed back to match the original input exactly.


18-60: Well-structured comprehensive test.

The test design using real data from the ZIP archive provides robust validation of compression/decompression correctness, with proper error handling and short test mode support.

@klauspost klauspost merged commit d140606 into master Jul 2, 2025
22 checks passed
@klauspost klauspost deleted the fix-simple-encoder branch July 2, 2025 11:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New EncodeTo function has its arguments swapped

2 participants