-
Notifications
You must be signed in to change notification settings - Fork 387
A cancellation doesn't work in some cases and app hangs. #351
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
Conversation
I'm running into the same issue. It looks like microsoft kind of ignores this repo, in the meanwhile does anyone have a good workaround? (Other than just keeping all my tasks alive, which does not sound great.) |
Hello @gurustron Would you check if MonitorEventsAsync is working? I haven't managed to |
@dgvives - Unrelated to this PR but if you are going to do that I would prefer that we just remove tools/specgen anymore and just manually update the models. Docker changed how all of this worked long ago when the broke the branches into EE/CE and made specgen less than helpful. I'm all for updating the models I just think that specgen is not worth the effort anymore. I no longer have the time to really contribute here but I am happy to merge PR's if you want to do this work. Thanks! |
@jterry75 @galvesribeiro Some of the models overridden on modeldefs.go are missing the required rest tag for correct model generation. I've updated some I found broken, but not all of them. Code generation using specgen is what I've used. All the generated models are based on specgen details, as I think they should be at least for now. Continue on #480 |
@dgvives I will try to take a look into it this week. |
@gurustron I confirm these changes have been incorporated in the last merge, However, this behaviour is not the most appropriate as it produces slightly different results when running tests on different environments. I expect to submit a PR with a different approach to this, and include references to yours and others' work as contributor |
I've played a little bit with an issue raised here it seems that without setting NamedPipeClientStream to PipeOptions.Asynchronous after disposing stream it endlessly waits in PipeStream.Read for local Windows connection.
Steps to repro:
create console app (NET71, .NETCORE) on Windows machine with empty Docker.