-
Notifications
You must be signed in to change notification settings - Fork 82
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
Fix sudden CI errors #609
Fix sudden CI errors #609
Conversation
Hmm, looks like Uno-check isn't it...
@jeromelaban did something else change this year we should be aware of? This build on main passed at the end of 2024: https://github.com/CommunityToolkit/Windows/actions/runs/12550855416 And our next one with a simple typo fixed failed (and subsequent are failing): https://github.com/CommunityToolkit/Windows/actions/runs/12934722557 |
Yes, there is, it's a breaking changes for wasm in .NET 9.0.102 that we fixed with the uno.wasm.bootstrap 9.0.10, there's also a workaround in unoplatform/uno#19232 (comment) if you cannot update yet. |
Thanks Jerome! FYI @Arlodotexe - We should just be able to update the bootstrapper, eh? As we've moved to .NET 9? |
Huge thanks @jeromelaban, I'll give that a go!
Notice how the other platforms are now failing after updating tooling. There are various "missing xml comment" error-warnings to resolve now, at least a dozen or two. Got that done locally, will push soon! |
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.
Think we can use inheritdoc in a few more places, but LGTM. Approving so we'll be unblocked once we get a clean CI and merge the submodule in before. Thanks!
Looks like still have some XML clean-up. Not sure how we weren't catching that before. We've had that check on in the past. |
I'd been building wasm locally to test and made sure to build all multitargets, but hadn't thought to build all heads. Should be easy to fix... |
The error that's appearing on UWP:
Very strange that these are only appearing now. Does the platform even ship with generic versions of |
Possibly related: dotnet/roslyn#51013 |
@michael-hawker We're thinking this may be caused by CommunityToolkit/Tooling-Windows-Submodule#245 Since this is clearly a platform bug, we'll suppress this for now. |
This PR
Prerequisite PR CommunityToolkit/Tooling-Windows-Submodule#249