Skip to content

Conversation

@tmat
Copy link
Member

@tmat tmat commented Sep 6, 2022

From the discussion on dotnet/aspnetcore#40587 it appears that these timeouts are causing failures in real world usage of dotnet watch.

I don't think we should use arbitrary timeouts on these code paths as long as they are cancellable. If some communication gets stuck during Hot Reload for some reason the user can always trigger cancelation of the change application.

Fixes dotnet/aspnetcore#40587

@tmat
Copy link
Member Author

tmat commented Sep 6, 2022

@SteveSandersonMS SteveSandersonMS self-requested a review September 12, 2022 09:24
Copy link
Member

@SteveSandersonMS SteveSandersonMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I don't have loads of context on this, I understand you're looking for someone on the Blazor team to approve, and it looks reasonable to me so approving.

It would be great to address @javiercn's comment if possible though.

@tmat tmat merged commit ae921da into dotnet:main Sep 14, 2022
@tmat tmat deleted the Timeouts-Blazor branch September 14, 2022 17:27
tmat added a commit to tmat/sdk that referenced this pull request Sep 14, 2022
* Remove timeouts from BlazorWebAssemblyDeltaApplier

* Remove timeout from delta applier.

* Remove comment

* Fail when capabilities can't be retrieved
@tmat tmat added this to the 7.0.1xx milestone Sep 14, 2022
tmat added a commit that referenced this pull request Sep 14, 2022
* Remove timeouts from BlazorWebAssemblyDeltaApplier

* Remove timeout from delta applier.

* Remove comment

* Fail when capabilities can't be retrieved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CLI Hot reload Blazor wasm just doesn't work.

5 participants