Skip to content
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

Ordering fix (#19220) #19221

Merged
merged 1 commit into from
Dec 9, 2019
Merged

Ordering fix (#19220) #19221

merged 1 commit into from
Dec 9, 2019

Conversation

cincuranet
Copy link
Contributor

Fixes #19220.

@cincuranet
Copy link
Contributor Author

Looks like the checks are lost now. Will reopen new PR.

@cincuranet cincuranet closed this Dec 7, 2019
@cincuranet
Copy link
Contributor Author

Didn't help at all. Can somebody re-trigger this or maybe #19225...

@roji, @ajcvickers

@cincuranet cincuranet reopened this Dec 7, 2019
This was referenced Dec 7, 2019
@smitpatel
Copy link
Contributor

The PR is in draft mode so checks won't run. Once you hit ready for review and make it normal PR it will trigger automatically.

@cincuranet cincuranet marked this pull request as ready for review December 8, 2019 07:59
@cincuranet
Copy link
Contributor Author

cincuranet commented Dec 8, 2019

@smitpatel Not really. It already did run here (and here), but the Azure DevOps somewhat failed and now GitHub is confused. But I marked it as ready for review anyway.

Will force push one more time and see whether the machines will cooperate.

@cincuranet
Copy link
Contributor Author

Voila. :shipit:

@ajcvickers ajcvickers merged commit f76e14c into dotnet:master Dec 9, 2019
@ajcvickers
Copy link
Member

Thanks!

(Note: ran Cosmos tests locally before merging.)

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.

Where_subquery_anon_nested is missing explicit order
3 participants