Closed reaver330 closed 1 year ago
@reaver330 thanks for the pull request! I need time for a review, I think I'll do it this weekend
@smolchanovsky its my pleasure! Thanks for the advice on the other PR 👍.
Thanks @smolchanovsky, I am studying this week (and maybe next) but will get to this after
Hi @smolchanovsky, sorry for the delays I was studying and then a week on holiday. I have updated and pushed the changes. Please let me know if there is more that requires attention. Cheers 👍
Hi @smolchanovsky, welcome back! That was a long break, i hope everything is ok?
I have added some code so that the _pipelineCanceller is initialised like this:
_pipelineCanceler = default!;
My build was passing locally and all the tests were passing; so I'm curious what the circumstances were that your build picked up this problem?
Hi @smolchanovsky, welcome back! That was a long break, i hope everything is ok?
I have added some code so that the _pipelineCanceller is initialised like this:
_pipelineCanceler = default!;
My build was passing locally and all the tests were passing; so I'm curious what the circumstances were that your build picked up this problem?
Thank you, everything is ok :) however, I had to move to another country
About the failed build: ci/cd of the project uses a zero tolerance policy for warnings. So build is run with warnaserror
option: dotnet build /warnaserror
@reaver330 all tests were successful, the pull request is merged, thank you!
Now you are the contributor of NClient :)
This small change became somewhat large as time went by and things were uncovered :)
IPipelineCanceller
interface and a basic implementation of it inPipelineCanceller
were added, that useCancellationToken
under the hood.clientInterceptorFactory
creation to the ctor of theClientValidator