Skip to content

Docker and VM: remove "path does not exist" warning#2168

Merged
limetech merged 7 commits into
unraid:masterfrom
bergware:master
Apr 24, 2025
Merged

Docker and VM: remove "path does not exist" warning#2168
limetech merged 7 commits into
unraid:masterfrom
bergware:master

Conversation

@bergware

@bergware bergware commented Apr 24, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Bug Fixes
    • Removed warnings about non-existent directory paths in Docker and VM settings; only a caution message is shown if the array is not started.
  • Style
    • Improved formatting and clarity of warning messages in VM settings.
    • Modernized code style and spacing in WireGuard update module for better readability.
  • Chores
    • Updated copyright years in VM settings.
    • Simplified diagnostics script by removing error logging and improving locale handling during command execution.
  • New Features
    • Enhanced network interface detection in WireGuard update module using dynamic system commands.

@coderabbitai

coderabbitai Bot commented Apr 24, 2025

Copy link
Copy Markdown
Contributor
## Walkthrough

The changes simplify the warning logic in the Docker and VM settings pages by removing conditional checks and warnings related to the existence of directory paths. Now, the only warning displayed is when the array is not started, eliminating previous checks for whether specific paths exist. Additionally, in the VM settings page, copyright years were updated, and PHP conditional blocks were reformatted for clarity. In the WireGuard update script, the method for retrieving network interface and IP details was changed from parsing a static ini file to using dynamic system commands, alongside comprehensive code style and spacing improvements. Function signatures were adjusted for spacing and the removal of a parameter in `thisNet()`. No changes were made to exported or public entities beyond these signature formatting and parameter adjustments.

## Changes

| File(s)                                                                                   | Change Summary                                                                                           |
|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|
| emhttp/plugins/dynamix.docker.manager/DockerSettings.page                                | Removed conditional checks and warnings for non-existent paths; now only warns if the array is not started. Simplified warning logic for Docker storage driver selection. |
| emhttp/plugins/dynamix.vm.manager/VMSettings.page                                        | Updated copyright years to 2025; reformatted PHP conditional blocks; removed warnings for non-existent paths, leaving only the array-not-started warning.                |
| emhttp/plugins/dynamix/include/update.wireguard.php                                     | Refactored `thisNet()` to use system commands instead of ini file parsing for network info; comprehensive code style and spacing improvements; minor function signature spacing adjustments. |
| emhttp/plugins/dynamix/scripts/diagnostics                                              | Removed `log_error()` function; simplified `write()` function to directly publish diagnostics messages; modified `run()` to prepend `LC_ALL=en_US.UTF-8` to commands and removed error logging and return code checks. |

## Possibly related PRs

- unraid/webgui#2163: Also modifies the diagnostics script by updating the `write()` function and command execution, closely related to changes in diagnostics message publishing and locale handling.  
- unraid/webgui#2002: Modifies DockerSettings.page with new functions and UI logic for wireless interfaces, related through changes to the same file’s conditional rendering and warnings.

## Poem

> In settings deep where warnings lay,  
> The checks for paths have gone away.  
> Now only when arrays won’t start,  
> A single caution will impart.  
> WireGuard’s net now finds its way,  
> With cleaner code to save the day.  
> 🐇✨

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between e45853b and 854a02b.

📒 Files selected for processing (1)
  • emhttp/plugins/dynamix/scripts/diagnostics (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • emhttp/plugins/dynamix/scripts/diagnostics

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

@limetech limetech merged commit 664daff into unraid:master Apr 24, 2025
ljm42 added a commit that referenced this pull request Apr 24, 2025
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.

2 participants