-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[mono][hotreload] Ignore if we receive an empty update. #120333
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
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.
Pull Request Overview
This PR adds a check to ignore empty hot reload updates in the Mono runtime. This prevents unnecessary processing when ASP.NET Core sends empty updates in WebAssembly debugger scenarios where the debugger itself applies the real updates.
Key Changes
- Added early return when both metadata and IL byte counts are zero
- Prevents redundant processing of empty hot reload updates
Co-authored-by: Copilot <[email protected]>
/backport to release/10.0 |
Started backporting to release/10.0: https://github.com/dotnet/runtime/actions/runs/18202185862 |
/backport to release/9.0-staging |
Started backporting to release/9.0-staging: https://github.com/dotnet/runtime/actions/runs/18202189764 |
Do we need a test? |
Can we pull that off in runtime? |
I think it's not possible to add a test here. Not super sure. |
This PR adds a check to ignore empty hot reload updates in the Mono runtime. This prevents unnecessary processing when ASP.NET Core sends empty updates in WebAssembly debugger scenarios where the debugger itself applies the real updates.
And also avoids assertion for receiving updates from System.Reflection.Metadata.MetadataUpdater.ApplyUpdate and from debugger even if one of them was empty.