Ben Randall comments

Results 67 comments of


                                            Ben Randall

ITestRunner.Run() does not pass Activity.Current to underlying test

Nope but that was my next plan. I’m a _little_ worried that it has something to do with the SDK that it was built with so I wanted to verify...

ITestRunner.Run() does not pass Activity.Current to underlying test

After FAR too much work into this I've determined that there's a difference between `netcoreapp2.1` (and earlier, like `netstandard2.0`) and `net6.0` and greater. There were a lot of project/framework/versioning changes...

ITestRunner.Run() does not pass Activity.Current to underlying test

I've validated this as far back as 3.17.0 which produced both a netcoreapp3.1 binary (which fails) AND netcoreapp2.1 binary (which succeeds).

Site down

Any updates on this? I use this daily. If there was a way to easily self-host it I'd be interested in trying to do that.

Using different namespaces for authentication vs. secret requests

We have almost this exact same code in our library where we set the namespace for login and then immediately change it after login succeeds.

What should the default setting be for internal trace logging?

We have warning as our default log level for many of our services so having the same for test libraries seems totally reasonable.

Missing null check for array items

Here's an example of the generated validation code that explicitly ignores `nil` values in an array. ```go func (m *QueryRequest) validateOrder(formats strfmt.Registry) error { if swag.IsZero(m.Order) { // not required...