The Wayback Machine - https://web.archive.org/web/20201113073338/https://github.com/dotnet/aspnetcore/issues/27775
Skip to content

/ aspnetcore

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

Jump to bottom

dotnet watch run infinite loop not honoring exclude/remove config #27775

Open
johan-v-r opened this issue Nov 12, 2020 · 1 comment
Open

dotnet watch run infinite loop not honoring exclude/remove config #27775

johan-v-r opened this issue Nov 12, 2020 · 1 comment
Labels
affected-very-few area-commandlinetools feature-dotnetwatch investigate severity-blocking
Milestone
Next sprint planning

Comments

@johan-v-r
Copy link

@johan-v-r johan-v-r commented Nov 12, 2020

Describe the bug

2 issues that seem related:

  1. Exclude/Remove watched files (configured in csproj) not honored.
  2. Saving scss files in different folders cause the watch to rebuild infinitely.

It looks like the build creates the css file, which is then watched and the cycle continues.

To Reproduce

Repro project available here: https://github.com/johan-v-r/Blazor-Wasm-Watch-Repro

Further technical details

VS 2019 16.8.0 with .NET 5.0.100

Able to replicate on 3 different Windows 10 machines, and just with CLI & notepad
@mkArtakMSFT mkArtakMSFT added investigate and removed enhancement labels Nov 12, 2020
@mkArtakMSFT mkArtakMSFT added this to the Next sprint planning milestone Nov 12, 2020
@msftbot
Copy link
Contributor

@msftbot msftbot bot commented Nov 12, 2020

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affected-very-few area-commandlinetools feature-dotnetwatch investigate severity-blocking
Projects
None yet
Milestone
Next sprint planning
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@johan-v-r @mkArtakMSFT
You can’t perform that action at this time.