Add POC disk cleanup

[coderabbitai[bot]]

Walkthrough

The recent update introduces a disk cleanup mechanism within the analysis processor. This addition is designed to monitor disk usage and automatically clear out files once certain thresholds are reached. It's a smart move towards ensuring the system remains efficient and avoids running out of storage space unexpectedly. The update encompasses both the implementation of the cleanup functionality and its testing.

Changes

File Path	Change Summary
.../processor/actions.go	Added disk cleanup functionality including usage calculation and file removal.
.../processor/actions_test.go	Introduced tests for the new disk cleanup mechanism.

🐇✨
In the land of code and byte,
Where disks do fill up in the night,
A clever rabbit hopped in sight,
With cleanup code, made storage light.
🌟📁✨
"Fear not," it said, "for I'll ensure,
Your space is free, forevermore."

---

Recent Review Status

**Configuration used: CodeRabbit UI**

Commits

Files that changed from the base of the PR and between 5f26da1eeaec81ee8163946739dad34066187ac2 and a22d719700c97faa50e3656f4e802074838bcd1e.

Files ignored due to path filters (2)

* `go.mod` is excluded by `!**/*.mod` * `go.sum` is excluded by `!**/*.sum`

Files selected for processing (2)

* internal/analysis/processor/actions.go (3 hunks) * internal/analysis/processor/actions_test.go (1 hunks)

Additional Context Used

GitHub Check Runs (1)

lint failure (3)

internal/analysis/processor/actions.go: [failure] 213-213: Error return value of `a.DiskCleanUp` is not checked (errcheck) --- internal/analysis/processor/actions_test.go: [failure] 5-5: SA1019: "io/ioutil" has been deprecated since Go 1.19: As of Go 1.16, the same functionality is now provided by package [io] or package [os], and those implementations should be preferred in new code. See the specific function documentation for details. (staticcheck)

Additional comments not posted (6)

internal/analysis/processor/actions_test.go (3)

`27-53`: Consider adding error handling for file creation and data writing in `initData`. While the current implementation uses `t.Fatalf` to halt the test on errors, ensuring clean file closure and deletion in case of failures can prevent resource leaks during test execution. --- `69-106`: Validate disk cleanup logic when disk is full. The test `TestDiskCleanUpFullDisk` correctly sets up a scenario where the disk is full and validates the cleanup process. It properly calculates the expected number of files after cleanup based on the mock disk usage and asserts the outcome. --- `108-139`: Ensure cleanup does not occur below threshold. The test `TestDiskCleanUpLessThanTreshold` effectively verifies that no files are removed when the disk usage is below the specified threshold. This test ensures that the cleanup logic is correctly applied only when necessary.

internal/analysis/processor/actions.go (3)

`91-95`: Implement sorting interface for file modification times. The `ByModTime` type and its methods correctly implement the `sort.Interface`, enabling sorting of files by modification time. This is essential for the disk cleanup logic to remove older files first. --- `97-100`: Define disk usage calculation interface. The `DiskUsageCalculator` interface is well-defined, encapsulating the necessary methods for calculating disk usage. This abstraction allows for easy testing and future extensions. --- `102-111`: Utilize actual disk usage for cleanup calculations. The `RealDiskUsage` type correctly implements the `DiskUsageCalculator` interface using the `go-disk-usage` library. This provides accurate disk usage metrics for the cleanup process.

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

---

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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.` 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 a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[isZumpo]

Sorry.... Was going to push a pr to my own fork such that I did not forget about the branch...