-
Notifications
You must be signed in to change notification settings - Fork 967
Resolve syncing conflicts from FromPrivateLiveToMaster to main #5138
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
Conversation
This has caused customer issues. https://stackoverflow.com/q/78776898
Thread callable must not exit the thread
update vector link
12/09/2024 AM Publish
@learn-build-service-prod[bot] : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit 84c48e9: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. For any questions, please:
|
@TylerMSFT - This sync PR appears to be stuck because of a merge conflict. Can you resolve the conflict and, if appropriate, merge the PR? Thanks! |
Learn Build status updates of commit 09d8747: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
#sign-off |
Pull request opened by Docs to resolve syncing conflicts from FromPrivateLiveToMaster to main.