-
Notifications
You must be signed in to change notification settings - Fork 2
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
Added debug to help figure out why this won't work in blazor wasm #642
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -113,6 +113,13 @@ private async Task ConnectAsync() | |
_client.DisconnectionHappened.Subscribe(info => | ||
{ | ||
_logger.LogWarning("WebSocket disconnected: {Type}", info.Type); | ||
|
||
// TODO: Remove | ||
_logger.LogWarning("CloseStatus: {CloseStatus}", info.CloseStatus); | ||
_logger.LogWarning("CloseStatusDescription: {CloseStatusDescription}", info.CloseStatusDescription); | ||
_logger.LogWarning("SubProtocol: {SubProtocol}", info.SubProtocol); | ||
_logger.LogWarning("Exception: {Exception}", info.Exception); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Potential exposure of sensitive exception details in log statement.
Tell me moreThe log statement 💡 Does this comment miss the mark? Tell us why and Korbit will adapt to your team’s feedback. |
||
|
||
_reconnectTrigger.OnNext(Unit.Default); | ||
}); | ||
|
||
|
@@ -152,6 +159,9 @@ private void HandleMessage(ResponseMessage message) | |
return; | ||
} | ||
|
||
// TODO: Remove | ||
_logger.LogInformation("Received message: {Message}", message.Text); | ||
Comment on lines
+162
to
+163
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Raw WebSocket Message Logging in Production
Tell me moreWhat is the issue?Another temporary debug logging statement is left in the code that logs raw WebSocket messages. Why this mattersLogging raw WebSocket messages in production could expose sensitive information and significantly increase log volume, potentially impacting system performance and log storage costs. 💡 Does this comment miss the mark? Tell us why and Korbit will adapt to your team’s feedback. |
||
|
||
var response = JsonSerializer.Deserialize<RealtimeMessage>(message.Text!); | ||
|
||
if (response is null) | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
namespace PinguApps.Appwrite.Shared; | ||
public static class Constants | ||
{ | ||
public const string Version = "2.0.0"; | ||
public const string Version = "2.0.1"; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Temporary Debug Logs Left in Production Code
Tell me more
What is the issue?
Temporary debug logging statements are marked with TODO: Remove but left in the code. This was only intended for troubleshooting.
Why this matters
Leaving temporary debug logs in production code can flood the logs with unnecessary information, making it harder to identify actual issues and potentially impacting performance.
💡 Does this comment miss the mark? Tell us why and Korbit will adapt to your team’s feedback.
💬 Chat with Korbit by mentioning @korbit-ai.