veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

297
active users

#dotnet

70 posts53 participants7 posts today

Feeling like I should be able to publish the new API documentation site for @xunit in the next day or two.

The last big issue to resolve is dealing with DocFX's `uid` collisions when trying to have more than one version of an API documented on the site at a time. Should be a fairly mechanical YML + JSON transformation after `docfx metadata`. #DotNet #DocFX

Trying to test something that was implemented with Ssh.Net library. API of the library is derived from IBaseClient which is cool, and I can mock it. But the RunCommand("cmd") method returns "SshCommand" object, which does not implement any interface and only has internal constructor.

By some miracle of introspection I created SshCommand in my test mocks. But it has complex async logic inside it. Can't they just return an interface? :sadness:

#ssh#dotnet#testing

When using named pipes, what's #docker expecting to signal the end of a `stdin` stream in an exec session? Used to work with a 0-byte `WriteFile()` (Windows Native API) in #dotnet, now seems broken. Writing input via `Docker.DotNet` never gets processed: github.com/testcontainers/Dock. Any idea?

Docker.DotNet doesn't support running commands that require inputs. It seems like attaching to stdin and writing to the stream doesn't work. Executing a command like /bin/sh -c "echo Done" and read...
GitHub[Bug]: Writing to `stdin` fails while command expects input (`/exec/{id}/start`). · Issue #20 · testcontainers/Docker.DotNetBy HofmeisterAn