refactor: use t.TempDir() instead of os.MkdirTemp

[yuhangcangqian]

TempDir returns a temporary directory for the test to use.The directory is automatically removed when the test and
all its subtests complete. More info https://pkg.go.dev/testing#B.TempDir

Summary by CodeRabbit

• Tests
  • Streamlined temporary directory management during testing by leveraging built-in functionality that automatically handles error checking and cleanup. This update maintains the same overall functionality while simplifying the test code for improved clarity and maintainability.

[coderabbitai]

Walkthrough

The pull request simplifies temporary directory creation in the test file by replacing the manual os.MkdirTemp invocation with the built-in t.TempDir() method. This change removes explicit error handling and cleanup logic since t.TempDir() automatically manages these responsibilities. No public interfaces or features have been modified.

Changes

File	Change Summary
tree_random_test.go	Replaced os.MkdirTemp with t.TempDir(), removing manual error checking and deferred cleanup. Functionality remains the same, with cleaner code.

Poem

In the code-forest where I roam,
I found a simpler, cozier home.
With t.TempDir() my tests now play,
Clearing errors far away.
Hopping happily, I celebrate this neat display!
🐇

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (1.64.8)

Error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2
Failed executing command with error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2

---

📜 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 39c1280 and da1f121.

📒 Files selected for processing (1)

• tree_random_test.go (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• tree_random_test.go

---

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

[aljo242]

@Mergifyio backport release/v1.2.x

[aljo242]

@Mergifyio backport release/v1.3.x

[mergify]

backport release/v1.2.x

✅ Backports have been created

• #1076 refactor: use t.TempDir() instead of os.MkdirTemp (backport #1059) has been created for branch release/v1.2.x

[mergify]

backport release/v1.3.x

✅ Backports have been created

• #1077 refactor: use t.TempDir() instead of os.MkdirTemp (backport #1059) has been created for branch release/v1.3.x