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

Log streams not showing up #3458

Closed
timheuer opened this issue Apr 6, 2024 · 4 comments · Fixed by #3459
Closed

Log streams not showing up #3458

timheuer opened this issue Apr 6, 2024 · 4 comments · Fixed by #3459
Assignees
Milestone

Comments

@timheuer
Copy link
Member

timheuer commented Apr 6, 2024

Seems like after #3343 the log streams are not responding and printing to the screen.

2024-04-05_22-58-00.mp4
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Apr 6, 2024
@timheuer timheuer added area-dashboard and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Apr 6, 2024
@davidfowl davidfowl added this to the preview 6 (Apr) milestone Apr 6, 2024
@davidfowl
Copy link
Member

davidfowl commented Apr 6, 2024

Bug was caused by the log virtualization changes. Surprised nobody has seen this until now.

Bug was caused by #3436 (cc @ReubenBond)

Here's the error:

System.InvalidOperationException: 'The current thread is not associated with the Dispatcher. Use InvokeAsync() to switch execution to the Dispatcher when triggering rendering or component state.'

From

@ReubenBond
Copy link
Member

Thanks for investigating @davidfowl. Let's revert it and apply it only to the non-Blazor bits, which are the ones the test was complaining about anyway.

@davidfowl
Copy link
Member

I think most of them are fine, I reverted the one that touches ui.

@davidfowl davidfowl modified the milestones: preview 6 (Apr), 8.1 Apr 7, 2024
@davidfowl
Copy link
Member

Moving this out of p6 since it wasn't backported.

@github-actions github-actions bot locked and limited conversation to collaborators May 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants