networking

It seems to me that if you have a wrapper function
https://github.com/libuv/libuv/blob/a39009a5a9252a566ca0704d02df8dabc4ce328f/test/runner-unix.c#L45
for close, then in this places you can use it.
https://github.com/libuv/libuv/blob/a39009a5a9252a566ca0704d02df8dabc4ce328f/test/runner-unix.c#L336
https://github.com/libuv/libuv/blob/a39009a5a9252a566ca0704d02df8dabc4ce328f/test/runner-unix.c#

Currently we use a pretty naive removal of testing dependencies for SwiftPM by setting an environment variable. We should be able to use Rocket and update our Rakefile script to just remove testing dependencies on each release, and keep it in the development process thanks to that.

The idea came from this PR that I saw RxSwiftCommunity/RxOptional#83, which sounds reall

Sometimes in NIO programs you're stuck in this situation:

doSomething().flatMap { result in
    guard iLikeTheShape(of: result) else {
        struct IDontLikeIt: Error {}
        //     vvvvvvvvv---- where do I get that from?
        return eventLoop.makeFailedFuture(IDontLikeIt())
    }
    return doMore()
}

that's all okay, but where do we get eventLoop from? In ma

It would be useful to be able to toggle/flag into a process-level mode to group by pid and display more process-level information like the full command line.

• For the "Utilization by process name" window, we could group by pid rather than process name so that it's easier to find specific heavy network resource consumers.
• For the "Utilization by connection" window, including the pid + cmdlin

All of the CI builds are flavors of linux. It'd be great to add some Windows / Mac ones.

Anybody know github actions and want to help out?

RustScan has an accessible mode, rustscan --accessible which should promise not to have any weird ASCII text in it.

Write CI that runs RustScan with --accessible a few times, with different flags / options and check the terminal output to see if it contains one of these:

1. [!]
2. [~]
3. [>]
4. | {}

If any of these characters appear in any of the tests, fail the CI. E

What should happen if deliver_cancel raises an exception? In the current implementation, the shielded cancel scope will prevent it from propagating until the process exits, which might take a while if the crash occurred before signaling the process in any way. Maybe on exception from a user-specified deliver_cancel we should call the default deliver_cancel to kill the process? Or just kill() since

What version of Knative?

1.0 (probably all since multi-container adoption). This affects init containers too.

Expected Behavior

Webhook ksvc validation should reject duplicate container names. K8s api valdiation logic dictates so.

Actual Behavio

Add following Contents to Cloud Providers - https://github.com/Tikam02/DevOps-Guide/tree/master/Cloud_providers

• Add basic concepts of following providers:
  • AWS
  • GCP
  • Azure
• Add tips & tricks
• Add commands