chore(tokio): remove unused enable_all

[BohuTANG]

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/

Summary

Summary about this PR

Closes #issue

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated
databend	⬜️ Ignored (Inspect)			Jan 30, 2023 at 1:34PM (UTC)

[drmingdrmer]

It enables io and timer. Don't we relies on them?:

  pub fn enable_all(&mut self) -> &mut Self {
        #[cfg(feature = "io-driver")]
        self.enable_io();
        #[cfg(feature = "time")]
        self.enable_time();

        self
    }

[drmingdrmer]

@BohuTANG unit test fails with:
thread 'Inner' panicked at 'A Tokio 1.x context was found, but timers are disabled. Call enable_time on the runtime builder to enable timers.', src/common/base/tests/it/runtime_tracker.rs:36:13

[BohuTANG]

@BohuTANG unit test fails with: thread 'Inner' panicked at 'A Tokio 1.x context was found, but timers are disabled. Call enable_time on the runtime builder to enable timers.', src/common/base/tests/it/runtime_tracker.rs:36:13

enable_io will panic miri, so i removed it and added enable_time.

[drmingdrmer]

enable_io will panic miri, so i removed it and added enable_time.

Interesting...

[BohuTANG]

Now we can run miri on some unit test, for example:

MIRIFLAGS='-Zmiri-disable-isolation' cargo miri test --test it pipelines::processors::port_test::test_port_drop

But we don't have many unit tests related to unsafe, FYI @zhang2014 @sundy-li

[BohuTANG]

oops:

ailures:

---- grpc_client::test_grpc_client_action_timeout stdout ----
thread 'meta-client-rt' panicked at 'A Tokio 1.x context was found, but IO is disabled. Call `enable_io` on the runtime builder to enable IO.', /opt/rust/cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.23.1/src/net/tcp/stream.rs:161:18

[BohuTANG]

It seems we can't disable IO in Databend, wait for rust-lang/miri#602