Skip to content

(#377) Fix for possible concurrent query during pull #378

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 1 commit into from
Jun 23, 2025

Conversation

StefanCuypers
Copy link
Contributor

Fixes the exception during pull that sometimes occurs. "A second operation was started on this context instance before a previous operation completed."

@StefanCuypers
Copy link
Contributor Author

@dotnet-policy-service agree

@adrianhall adrianhall requested review from Copilot and adrianhall June 23, 2025 16:40
Copy link
Contributor

@Copilot 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.

Pull Request Overview

This PR addresses an exception occurring during pull operations by preventing concurrent queries on the context instance.

  • Refactored pull request logic to queue operations sequentially
  • Separated retrieval and enqueueing of pull requests to avoid concurrent context access

@adrianhall
Copy link
Collaborator

Thank you for the contribution!

@adrianhall adrianhall merged commit 83eb0be into CommunityToolkit:main Jun 23, 2025
5 checks passed
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.

Pull: System.InvalidOperationException: A second operation was started on this context instance before a previous operation completed.
2 participants