Skip to content

Added option to bypass FindReplyQueueForMe if you are on k8s #756

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

Merged
merged 3 commits into from
Apr 29, 2025

Conversation

GrevlingKake
Copy link
Collaborator

No description provided.

@@ -268,6 +272,11 @@ internal string FindReplyQueueForMe()
where s.Equals(Environment.MachineName, StringComparison.OrdinalIgnoreCase)
select s).FirstOrDefault();

if (SingleSyncreplyQueueEnabled && server == null)
Copy link
Collaborator

@kennethmyhra kennethmyhra Apr 28, 2025

Choose a reason for hiding this comment

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

Burde man i det hele tatt forsøke å hente ReplyQueueMapping dersom SingleSyncReplyQueueEnabled er satt til true? Virker på meg som hele den funksjonaliteten burde være slått av dersom SingleSyncReplyQueueEnabled er satt til true

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Oppdaterte sjekken til å skippe validering hvis den er true

@GrevlingKake GrevlingKake merged commit c141085 into master Apr 29, 2025
5 checks passed
@GrevlingKake GrevlingKake deleted the k8s-fix-FindReplyQueueForMe branch April 29, 2025 12:57
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.

3 participants