Fabian Holler
Fabian Holler
@mPokornyETM could you please have another look?
ok, thanks for the fast response nonetheless. Maybe something else sees it and has an opinion or even a better idea. I experimented a bit more in the meantime: The...
@tebeka I'm getting the same error with some of our testcases. Maybe it's related to that some of our testcases print something in json format to the console? I ran:...
@tebeka yes, sorry, you are right. In the attached `output.txt`, I ran `go test` without the `-v` flag. The `orphan end test` error happens reproducibly for multiple of our unit...
Yes, those tests were using t.parallel
I think I run into this issue with docker 19.03.12-ce + docker-compose 1.27.0-rc2. I have a docker container running in status unhealthy. ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS...
I'm getting the same error when running safesql for our applications
@jspizziri duplicating all those fields with the descriptions in the data source will be a pain to maintain. I guess it's not possible to reuse the same `map[string]*schema.Schema` definition from...
@jspizziri I was also checking other provides and could not find one that was reusing the schema definition. Often data sources also have a different structure then the related resource....
@jspizziri `pullZoneToResource()` calls `d.Set()` for all keys in the resource schema. You are calling `pullZoneToResource()` and are passing the datasource schema, which only has a subset of the keys. `d.Set`...