Skip to content

Use LoggerMessageGenerator for core logging messages#9274

Closed
Meir017 wants to merge 1 commit intodotnet:mainfrom
Meir017:use-logger-message-generator
Closed

Use LoggerMessageGenerator for core logging messages#9274
Meir017 wants to merge 1 commit intodotnet:mainfrom
Meir017:use-logger-message-generator

Conversation

@Meir017
Copy link
Copy Markdown
Contributor

@Meir017 Meir017 commented Dec 22, 2024

Update core logging messages to use LoggerMessageGenerator for logging.

  • Modify src/Orleans.Core/Diagnostics/MessagingTrace.cs to use LoggerMessageGenerator for logging instead of LoggerMessage.Define.
  • Modify src/Orleans.Core/Manifest/ClientClusterManifestProvider.cs to use LoggerMessageGenerator for logging instead of logger.IsEnabled.
  • Modify src/Orleans.Core/Messaging/ClientMessageCenter.cs to use LoggerMessageGenerator for logging instead of logger.IsEnabled.
  • Modify src/Orleans.Core/Messaging/GatewayManager.cs to use LoggerMessageGenerator for logging instead of logger.IsEnabled.
Microsoft Reviewers: Open in CodeFlow
  • github copilot workspace reached the quota limit for this

Update core logging messages to use LoggerMessageGenerator for logging.

* Modify `src/Orleans.Core/Diagnostics/MessagingTrace.cs` to use LoggerMessageGenerator for logging instead of `LoggerMessage.Define`.
* Modify `src/Orleans.Core/Manifest/ClientClusterManifestProvider.cs` to use LoggerMessageGenerator for logging instead of `logger.IsEnabled`.
* Modify `src/Orleans.Core/Messaging/ClientMessageCenter.cs` to use LoggerMessageGenerator for logging instead of `logger.IsEnabled`.
* Modify `src/Orleans.Core/Messaging/GatewayManager.cs` to use LoggerMessageGenerator for logging instead of `logger.IsEnabled`.
@Meir017 Meir017 marked this pull request as draft December 22, 2024 21:29
@ReubenBond
Copy link
Copy Markdown
Member

How did you implement this, was there a tool which was used? If so, which

@Meir017
Copy link
Copy Markdown
Contributor Author

Meir017 commented Feb 6, 2025

How did you implement this, was there a tool which was used? If so, which

@ReubenBond I tried using the github copilot workspace

@ReubenBond ReubenBond requested a review from Copilot February 6, 2025 14:57
@ReubenBond
Copy link
Copy Markdown
Member

How did you implement this, was there a tool which was used? If so, which

@ReubenBond I tried using the github copilot workspace

Ok, great :) I will keep that in mind when reviewing.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 6 out of 18 changed files in this pull request and generated no comments.

Files not reviewed (12)
  • src/Orleans.Runtime/Lifecycle/SiloLifecycleSubject.cs: Evaluated as low risk
  • src/Orleans.Runtime/Silo/Silo.cs: Evaluated as low risk
  • src/Orleans.Runtime/Scheduler/ActivationTaskScheduler.cs: Evaluated as low risk
  • src/Orleans.Runtime/Placement/PlacementService.cs: Evaluated as low risk
  • src/Orleans.Runtime/Messaging/Gateway.cs: Evaluated as low risk
  • src/Orleans.Runtime/Placement/Repartitioning/ActivationRepartitioner.MessageSink.cs: Evaluated as low risk
  • src/Orleans.Core/Diagnostics/MessagingTrace.cs: Evaluated as low risk
  • src/Orleans.Core/Manifest/ClientClusterManifestProvider.cs: Evaluated as low risk
  • src/Orleans.Runtime/Manifest/ClusterManifestProvider.cs: Evaluated as low risk
  • src/Orleans.Runtime/Hosting/EndpointOptionsProvider.cs: Evaluated as low risk
  • src/Orleans.Core/Messaging/ClientMessageCenter.cs: Evaluated as low risk
  • src/Orleans.Runtime/Core/HostedClient.cs: Evaluated as low risk

@Meir017 Meir017 closed this Feb 12, 2025
@Meir017 Meir017 deleted the use-logger-message-generator branch February 12, 2025 18:53
@github-actions github-actions bot locked and limited conversation to collaborators Mar 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants