Thomas Eizinger
Thomas Eizinger
Generally good practice and it would make it otherwise really hard to monitor the CLI if spawned from within another program like a GUI.
It would be nice if the `http` crate would have a `serde` feature that makes things like `StatusCode` serializable. I am currently in the progress of refactoring the [`http-api-problem`](https://github.com/chridou/http-api-problem) crate...
This adds a feature `serde` that for now just enables serialization and deserialization of `StatusCode`. Other types can easily be added later based on this. Resolves #273.
Since its inception, `testcontainers-rs` had an API that focused on first creating a `Client` before one could `run` a `Container`. This was deemed acceptable as a `Client` is typically only...
New lints are coming in clippy that will break our build eventually if not fixed: https://github.com/testcontainers/testcontainers-rs/runs/6659770330?check_suite_focus=true.
The docker daemon can be hosted on a remote machine, hence in addition to the `port` of a container, we should also expose the `host` on which the docker container...
Help in maintaining this project would be greatly appreciated. Please comment if you are interested or ping me on matrix: https://matrix.to/#/@thomaseizinger:matrix.org
Not sure if this is documented anywhere but I've since learned about this very nifty pattern for doing `async` work in a `Drop` implementation: 1. Have a `Void` async, oneshot...
Unfortunately, the podman test started to hang forever. We had to disable it to unblock current work happening. @ctron Do you know of any reason why podman would suddenly start...
We should extend the contribution guidelines to make it clear that we expect people to keep the images they are adding working or they will be removed again.