tison
> Reusable containers are not suited for CI usage Just a comment to this statement: We reuse containers in the CI environment, and the runner will destroy everything once the...
@the-wondersmith Cool! Thanks everyone helps in this thread. I'll test this feature in this week.
I tried at https://github.com/tisonkun/morax/pull/19 @the-wondersmith it seems not work. See the PR for reproduce and fail logs.
@taiki-e Today I found a scenario where a `TryStreamExt::try_flat_map` may help. That is, take an `Ok` variant, returns a `Stream` (or `TryStream`?), and then the result streams will be flatten....
@rib any thoughts?
> Also, Image implementation can override [exec_after_start](https://docs.rs/testcontainers/latest/testcontainers/core/trait.Image.html#method.exec_after_start), returning ExecCommands with their own CmdWaitFor (including exit code) This seems the way I'd like to go. If `exec_after_start` can block `start` and...
@DDtKey I try: ``` fn exec_after_start(&self, _: ContainerState) -> Result { Ok(vec![ExecCommand::new([ "pg_isready", "-U", USERNAME, "-d", "postgres", ]) .with_cmd_ready_condition(CmdWaitFor::exit_code(0))]) } ``` But it panics with `called `Result::unwrap()` on an `Err`...
As the `clippy.toml` can be defined for workspace, I suppose `my_crate::f` should work as a design (but it doesn't work yet).
Besides, I may want to disallow trait method for a specific implementation. Given - ```rust trait A { fn f (); } Struct B; impl A for B { ......
> my_crate::f I checked this way works now (may be related to https://github.com/rust-lang/rust-clippy/pull/8852) and even with nested mod. My issue is the comment above https://github.com/rust-lang/rust-clippy/issues/7479#issuecomment-1664869201