Dotnet-IO-logger / core

Dotnet Input output logger
https://marketplace.visualstudio.com/items?itemName=Diol.diol
MIT License
29 stars 1 forks source link

Response logs #26

Closed OlzhabaevSh closed 3 months ago

OlzhabaevSh commented 1 year ago

Describe the bug The Diol extension for Visual Studio doesn't show response's logs.

To Reproduce Steps to reproduce the behavior:

  1. Open a asp.net project. You can take this one PlaygroundApi
  2. Start debugging
  3. In Diol windows click Play
  4. Trigger /api/default-client/bing
  5. Look at Diol. In Http you will see the request but no response.

Expected behavior If you check Diagnostics tab you will see that we recieve response's logs. But the problem is the key. The good news is the bug is not releated with our code. For some reasons Visual Studio brokes ActivityIds and you will not see the issue if you run the app with dotnet run from ternminal.

You can read more here

What we can do:

  1. Sync with EventSource owners and ask regiarding this issue.
  2. Use a workaround (from Additional context)

Screenshots Not need

Desktop (please complete the following information):

Smartphone (please complete the following information): Not need

Additional context Let me cope small workaround from documentation:

There is a known issue where Visual Studio debugger may cause invalid Activity IDs to be generated. Either don't run this sample under the debugger or set a breakpoint at the beginning of Main and evaluate the expression 'System.Threading.Tasks.TplEventSource.Log.TasksSetActivityIds = false' in the immediate window before continuing to work around the issue.

OlzhabaevSh commented 1 year ago

We found a comment to the documentation where they mentioned regarding this bug: https://github.com/dotnet/docs/pull/28826

OlzhabaevSh commented 1 year ago

Link for the issue: https://github.com/dotnet/runtime/issues/39353

OlzhabaevSh commented 1 year ago

For development purposes you can go to Services -> 'VSStandardCollectorService150' and disable it

OlzhabaevSh commented 5 months ago

The bug is fixed and will be available in VS 17.11. We will use that date as a release day for the extension

OlzhabaevSh commented 3 months ago

VS 17.11.x has been released and it fixed the bug!

we are good to go!