Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add missing exception logging #130

Merged
merged 2 commits into from
Feb 13, 2025
Merged

Add missing exception logging #130

merged 2 commits into from
Feb 13, 2025

Conversation

justinshannon
Copy link
Contributor

@justinshannon justinshannon commented Feb 13, 2025

Summary by CodeRabbit

  • Refactor
    • Improved error handling across several application areas to capture detailed context when issues occur.
  • Chores
    • Updated system dependencies for structured logging, enhancing overall diagnostics and troubleshooting.

Copy link
Contributor

coderabbitai bot commented Feb 13, 2025

Walkthrough

This pull request enhances error logging across several modules of the vATIS.Desktop project. Changes include improved contextual messages for exceptions in methods such as updating IDS, audio requests, sandbox refreshing, ATIS station handling, and bot management. The modifications introduce additional catch blocks and integrate the Serilog logging library in select view models. The overall aim is to provide more detailed and structured error messages without altering the existing control flow of the application.

Changes

File(s) Change Summary
vATIS.Desktop/Atis/AtisBuilder.cs Enhanced error logging in UpdateIds: replaced generic error logs with detailed context for HttpRequestException and general exceptions.
vATIS.Desktop/TextToSpeech/TextToSpeechService.cs Added a new catch block for Exception in RequestAudio, including a clarifying comment for handling OperationCanceledException.
vATIS.Desktop/Ui/ViewModels/SandboxViewModel.cs
vATIS.Desktop/Ui/ViewModels/MainWindowViewModel.cs
Introduced Serilog dependency; updated methods (HandleRefreshSandboxAtis, PopulateAtisStations) to log exceptions with contextual error messages.
vATIS.Desktop/Ui/ViewModels/AtisStationViewModel.cs Inserted logging statements in multiple methods (voice recording, network status/connect, METAR response, preset and letter changes) to capture exceptions.
vATIS.Desktop/Voice/Network/VoiceServerConnection.cs Added logging in AddOrUpdateBot and RemoveBot methods to catch and log exceptions during bot management operations.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant Method
    participant ExceptionHandler as CatchBlock
    participant Logger

    Caller->>Method: Invoke operation
    Note right of Method: Operation executes normally
    Method-->>ExceptionHandler: Exception thrown
    ExceptionHandler->>Logger: Log error with contextual message
    Logger-->>ExceptionHandler: Error recorded
    ExceptionHandler->>Caller: (Optionally rethrow exception)
Loading

Poem

I'm a rabbit on the run with logs so neat,
Hopping over errors, making debugging sweet.
Carrots of clarity crunch in every log bite,
Guiding my hops from dark exceptions to light.
Each caught error makes my code a delight!
🥕🐇


📜 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 732254d and 2cca48a.

📒 Files selected for processing (4)
  • vATIS.Desktop/TextToSpeech/TextToSpeechService.cs (1 hunks)
  • vATIS.Desktop/Ui/ViewModels/AtisConfiguration/SandboxViewModel.cs (2 hunks)
  • vATIS.Desktop/Ui/ViewModels/MainWindowViewModel.cs (2 hunks)
  • vATIS.Desktop/Voice/Network/VoiceServerConnection.cs (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (4)
  • vATIS.Desktop/Voice/Network/VoiceServerConnection.cs
  • vATIS.Desktop/TextToSpeech/TextToSpeechService.cs
  • vATIS.Desktop/Ui/ViewModels/MainWindowViewModel.cs
  • vATIS.Desktop/Ui/ViewModels/AtisConfiguration/SandboxViewModel.cs
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: build (macos-latest)
  • GitHub Check: build (windows-latest)
  • GitHub Check: Analyze (cpp)
  • GitHub Check: Analyze (csharp)
  • GitHub Check: build (ubuntu-latest)
  • GitHub Check: Analyze (cpp)
  • GitHub Check: Analyze (csharp)

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
🪧 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. (Beta)
  • @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
Contributor

@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: 0

🧹 Nitpick comments (5)
vATIS.Desktop/TextToSpeech/TextToSpeechService.cs (1)

93-96: Consider adding more context to the error message.

While the error logging is good, the message could be more descriptive to help with debugging.

-            Log.Error(ex, "Error requesting audio");
+            Log.Error(ex, "Error requesting audio for voice {Voice}", VoiceList.FirstOrDefault(v => v.Name == station.AtisVoice.Voice)?.Id ?? "default");
vATIS.Desktop/Voice/Network/VoiceServerConnection.cs (2)

93-94: Consider adding more context to the error message.

The error message could be more descriptive by including the callsign and bot details.

-            Log.Error(ex, "AddOrUpdateBot failed.");
+            Log.Error(ex, "AddOrUpdateBot failed for callsign {Callsign}", callsign);

113-114: Consider adding more context to the error message.

The error message could be more descriptive by including the callsign.

-            Log.Error(ex, "RemoveBot failed.");
+            Log.Error(ex, "RemoveBot failed for callsign {Callsign}", callsign);
vATIS.Desktop/Ui/ViewModels/MainWindowViewModel.cs (1)

350-350: Consider adding more context to the error message.

The error message could be more descriptive by including the station details.

-                Log.Error(ex, "Error Populating ATIS Station");
+                Log.Error(ex, "Error Populating ATIS Station {StationId} {Identifier}", station.Id, station.Identifier);
vATIS.Desktop/Ui/ViewModels/AtisConfiguration/SandboxViewModel.cs (1)

413-416: Consider adding more context to the error message and improve error handling.

The error message could be more descriptive, and the error handling could be improved.

-            Log.Error(ex, "HandleRefreshSandboxAtis Exception");
+            Log.Error(ex, "Failed to refresh sandbox ATIS for station {StationId} {Identifier} with preset {PresetId}", 
+                SelectedStation?.Id, SelectedStation?.Identifier, SelectedPreset?.Id);
             SandboxTextAtis = "";
             SandboxSpokenTextAtis = "";
-            throw;
+            SandboxTextAtis = "Error: " + ex.Message;
+            SandboxSpokenTextAtis = "Error: " + ex.Message;
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3e58287 and 732254d.

📒 Files selected for processing (6)
  • vATIS.Desktop/Atis/AtisBuilder.cs (1 hunks)
  • vATIS.Desktop/TextToSpeech/TextToSpeechService.cs (1 hunks)
  • vATIS.Desktop/Ui/ViewModels/AtisConfiguration/SandboxViewModel.cs (2 hunks)
  • vATIS.Desktop/Ui/ViewModels/AtisStationViewModel.cs (12 hunks)
  • vATIS.Desktop/Ui/ViewModels/MainWindowViewModel.cs (2 hunks)
  • vATIS.Desktop/Voice/Network/VoiceServerConnection.cs (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: build (macos-latest)
  • GitHub Check: build (windows-latest)
  • GitHub Check: Analyze (cpp)
  • GitHub Check: build (ubuntu-latest)
  • GitHub Check: Analyze (csharp)
  • GitHub Check: Analyze (cpp)
  • GitHub Check: Analyze (csharp)
🔇 Additional comments (11)
vATIS.Desktop/TextToSpeech/TextToSpeechService.cs (1)

91-92: LGTM! Clear comment for ignored exception.

The comment clearly indicates that OperationCanceledException is intentionally ignored, which is a good practice for documenting exception handling decisions.

vATIS.Desktop/Ui/ViewModels/MainWindowViewModel.cs (1)

23-23: LGTM! Added Serilog import.

The import is correctly placed with other system imports.

vATIS.Desktop/Ui/ViewModels/AtisConfiguration/SandboxViewModel.cs (1)

21-21: LGTM! Added Serilog import.

The import is correctly placed with other system imports.

vATIS.Desktop/Atis/AtisBuilder.cs (2)

140-143: LGTM! Improved error logging for HTTP request failures.

The addition of a contextual message "HttpRequestException updating IDS" helps identify the source of the HTTP request failure.


144-148: LGTM! Added error logging before throwing the exception.

Good practice to log the error before throwing the exception, as this ensures the error details are captured in logs even if the exception is caught and handled differently upstream.

vATIS.Desktop/Ui/ViewModels/AtisStationViewModel.cs (6)

857-860: LGTM! Added error logging for voice recording failures.

Proper error logging for exceptions during voice ATIS recording.


889-894: LGTM! Added comprehensive error logging for network status changes.

Good error logging coverage for:

  • Voice server connection failures
  • Voice server disconnection issues
  • General network status change errors

Also applies to: 911-915, 927-930


997-1004: LGTM! Added error logging for network connection failures.

Proper error logging for both specific connection failures and general network connect exceptions.

Also applies to: 1012-1023


1123-1140: LGTM! Added comprehensive error logging for METAR processing.

Good error logging coverage for:

  • METAR property update failures
  • Text-to-speech ATIS generation errors
  • General METAR response handling errors

Also applies to: 1200-1205, 1208-1219


1353-1364: LGTM! Added error logging for preset change failures.

Proper error logging when handling ATIS preset changes.


1533-1537: LGTM! Added error logging for ATIS letter change failures.

Good error logging coverage for both task-level and general ATIS letter change errors.

Also applies to: 1544-1555

@justinshannon justinshannon added this pull request to the merge queue Feb 13, 2025
Merged via the queue into main with commit 834564c Feb 13, 2025
9 checks passed
@justinshannon justinshannon deleted the fix/exception-logging branch February 13, 2025 16:25
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.

1 participant