-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[release/6.0] Fix null being passed to g_path_get_dirname when probing in wasm #84740
[release/6.0] Fix null being passed to g_path_get_dirname when probing in wasm #84740
Conversation
Co-authored-by: Aleksey Kliger (λgeek) <akliger@gmail.com>
Tagging subscribers to this area: Issue DetailsBackport of #60445 to release/6.0-staging Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Retargeting from 6.0-staging to 6.0 accidentally brought the branding change we did in that branch (staging should always be one version ahead when the base branches are closed).
Reverting via code suggestions. The May Release is 6.0.17.
Backport of #60445 to release/6.0-staging
fixes the failures in dotnet/aspnetcore#47652
/cc @lewing @kg
Customer Impact
Blazor can fail at startup due to code reordering
Testing
This code is included in 7.0 and works correctly there
Risk
Tiny change is already in 7 and 8
.