infinyon / future-aio Goto Github PK

To make Connection metadata OS independent

with_hostname_vertification_disabled here and with_certificate_vertification_disabled here.
verification was spelled vertification in both cases.

This can be used in TLS proxy. Some of technology we should leverage

• io_uring
• ebpf

danburkert/memmap-rs#90

Probably we should move to memmap2

This would be nice because it makes running clippy --all-features on downstream projects difficult.

• publish to crate.io
• create GitHub release with artifacts

Current implementation of sleep doesn't allow borrow which prevents use in the loop as below:

let mut sleep_ft = sleep(Duration::from_millis(10));
loop {
   select! {
          _ = &mut sleep_ft => {
                 break;
          }
    }
}

https://github.com/aws/s2n-tls

• memmap
• fs
• tls
• etc

see: infinyon/fluvio#1520

Send_file can go into infinite loop discovered during investigation of: infinyon/fluvio#2116.
This is caused by not handling EOF case

https://github.com/infinyon/future-aio/runs/3451458165?check_suite_focus=true.

Commented this out so we don't block CI process

Ensure flv-future-aio compiles and run in non unix platform. Features like Zero copy should be only be enabled in the unix platforms.

if zero copy didn't completed in a first attempt, it hangs. This is due to extra offset update.

Should re-write tests at

On a blank node-bindgen repo I ran nj-cli build and the build failed with:

error[E0433]: failed to resolve: use of undeclared type or module `futures_lite`
  --> /home/nick/.cargo/registry/src/github.com-1ecc6299db9ec823/fluvio-future-0.1.10/src/timer.rs:10:9
   |
10 |     use futures_lite::future::Future;
   |         ^^^^^^^^^^^^ use of undeclared type or module `futures_lite`

Looks like the timer feature needs futures_lite but does not enable it.

rustls version 0.20 has non compatible API changes.

Usage of RawFd prevents compilation on windows.

We should add windows compilation in CI to catch this.

To support ignore, attribute, we need to enhance async_test macro as below:

#[async_test(ignore)]
async fn fn_to_test

will be expanded as

#[test]
#[ignore]
fn wrapper_test_fn() {
  ... async wrapper
   
   async fn fn_test_ {
   }
}

also separate test attribute which remove unneeded for result which means you can write:

#[fluvio_future::test(ignore)]
async fn my_test() {
     assert!("a".len(),1);
}

Following on infinyon/fluvio#2216

We may want to support partial CA "Trust anchors" that are mediated by the intermediate CA certs under another CA.

Intermediate CAs are used to compartmentalize issuance and management in certain configurations.

However managing the full client CA chain in this case would become logistically cumbersome and the industry has moved to generally accept using intermediate CAs on the client end -

This follows the default Curl and typical kubectl behaviour.

Test scope to be added:

• Self-signed solo-CA with no intermediary certs
• Intermediary CA chain as in: infinyon/fluvio#2216

Potentially also we need integration tests that integrate with a real k8s cluster against different setups.

I think it is convention to log to stderr and reserve stdout for structured output. See issue tokio-rs/tracing#2492

Async dispatcher is simplest actor possible. It just implement async dispatch loop.
It will be added as unstable feature

similar to #[fluvio_future::test] but support non async function.

#[cfg(test)]
mod test {
 
     // same as cargo test but initialize logging
     #[fluvio_future::test]
     fn test_add() {
           assert_eq!(1+1,2);
     }

    // uses async runtime
     #[fluvio_future::test]
     async fn test_add() {
           assert_eq!(1+2);
    }

}

as part of 0.3.10, windows test has been disabled due to issue with certs generation. this need to be restored

Unit tests sometimes run endlessly (hits 5 minute timeout). Error message seemed to indicate zero-copy test. https://github.com/infinyon/future-aio/runs/1318014539?check_suite_focus=true