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

[release/7.0] [wasm][debugger] Fixing when trying to call mono functions in a non wasm page #77501

Merged
merged 2 commits into from
Nov 3, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 26, 2022

Backport of #77496 to release/7.0

/cc @thaystg

Customer Impact

The customer is trying to login in its blazor wasm app. During some redirections to other pages caused by the login process, the BrowserDebugProxy receives a new debug context from the browser and try to check if it’s a wasm app evaluating some commands, the first one works well the second one throws an exception. This is not something easy to reproduce, but sometimes while login this may happen, then the debugger crashes and the debug session is terminated.

Testing

Manually tested.

Risk

Low risk, only adding a try catch to ignore any error that we can get on RuntimeReady method, because it's not a wasm page.

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

@ghost
Copy link

ghost commented Oct 26, 2022

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #77496 to release/7.0

/cc @thaystg

Customer Impact

Testing

Risk

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

Author: github-actions[bot]
Assignees: -
Labels:

area-Debugger-mono

Milestone: -

@carlossanlop
Copy link
Member

@thaysg When this is ready, please add the servicing-consider label, then send the email to Tactics requesting approval.

@thaystg thaystg added the Servicing-consider Issue for next servicing release review label Oct 31, 2022
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Nov 3, 2022
@rbhanda rbhanda added this to the 7.0.1 milestone Nov 3, 2022
@carlossanlop
Copy link
Member

@thaystg can you please get a code review sign-off?

@carlossanlop
Copy link
Member

CI failures are:

@carlossanlop
Copy link
Member

Approved by Tactics, signed off by code reviewer. CI failures unrelated. No OOB package authoring changes needed for this PR. Ready to merge. :shipit:

@carlossanlop carlossanlop merged commit 96c24ea into release/7.0 Nov 3, 2022
@carlossanlop carlossanlop deleted the backport/pr-77496-to-release/7.0 branch November 3, 2022 18:12
@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Debugger-mono Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants