Mehul Arora

I will fix the inconsistencies, once someone can confirm here

currently, we do have tests for - read - write - open (this is tested through read/write, so we dont need an explicit test) - openat - lseek

@thedanvail it would be nice if we could just figure cases where python calls `f` family functions i.e. some real world scenarios and replicate them for the E2E. The tests...

Also we should probably separate the tests for open into various scenarios, so that we know which case went wrong

hi @thedanvail, just wanted to check in with you if you were able to get the tests to work.. please feel free to reach out in case you need any...

Can you add #[trace] and #[notrace]? https://docs.rs/rstest/latest/rstest/attr.rstest.html#trace-input-arguments

> > Can you add #[trace] and #[notrace]? https://docs.rs/rstest/latest/rstest/attr.rstest.html#trace-input-arguments > > ``` > 641 | pub async fn test_remote_env_vars_exclude_works(#[future] service: EchoService) { > | ^^^^^^^ `impl futures_util::Future` cannot be formatted...

openat was fixed in #151, detours for ls still pending but low priority

Had the same issue on MacOS, but reinstalling rustup fixes it. One of the comments on https://github.com/rust-lang/vscode-rust/issues/622 mentions adding `"rust-client.rustupPath": "$HOME/.cargo/bin/rustup"` to the settings.json file but that didn't work for...

> @infiniteregrets how do you know IPv6 is not enabled on the pod? What about the IPv6 addresses in the `ifconfig`? > ``` > inet6 fe80::1cad:11ff:fe4a:c713 prefixlen 64 scopeid 0x20...