You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This introduces a new `Tunnel` widget that shows
the status of tunnels in the dashboard. This
allows users to see what's currently happening.
There are some caveats to this though:
- Egress starts up immediately and is `listening`.
- Ingress is only on incoming connections and
switches to `inactive` when the connection is
closed.
Additionally, this:
- Standardizes the `Session` "writers" into a
broadcast that can be either for a single
channel or all channels.
- No longer hangs indefinitely when a source
channel is closed (via ingress tunnel) but the
destination is still open (warp::serve keeps the
connection open for example).
- Stops trying to close all channels that EOF.
This is because the tunnel channels now manage
their lifecycle themselves. Unfortunately, the
pty and sftp requests do not.
`Session::channels` now has a `None` inserted if
a channel has been consumed but it is still
open.
- Passing a `StringError` that is clone-able
instead of `Report` which is not. This results
in the source needing to render the error but it
makes everything much easier to work with.
- Rewords `StatusError` to no longer exist -
instead being constructed as a `Report` by
`PodExt`.
- Moves as much of the verbose logging as possible
to `debug` from `info`. See `DEVELOPMENT.md` for
how to enable this.
- Allow `Table` to have an optional header and
selection style.
0 commit comments