networking

I'm opening this issue prepared to be declared blind and pointed at the relevant bit of documentation, but I've looked far and wide, and it's definitely not in this repo, not in a form that a grep can find.

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

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

If you want to work with a complete socket address type including port, we have a helper in SocketAddress. However, the moment you want to talk only about an IP address we force you to hold an in_addr or in_addr6 structure: hardly the friendliest versions of these data types.

We should provide a helpful wrapper IPAddress type that can be converted into those types as needed. This would

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

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

What version of Knative?

v1.0 at least

Expected Behavior

When creating a Revision with a pod which exits immediately, the Revision should (fairly quickly) report that Ready is False and terminate the Pods.

Actual Behavior

The pods stick around