-
Separating this from #6291 as its a different beast and different design, and at the moment not an issue hit by users
-
From #4572
> Rather than adding write responses, some kind of credit based flow control scheme seems appropriate here. For example (just brainstorming):
> - change the sender so that it only sen…
-
I've noticed that ET struggles with Flow Control. If you run
`cat /dev/zero | base64 -w 0`
it is not possible to send a ^C to the server. Using SSH directly it works fine.
-
Hello,
I tried version 15 and 17 and both are crashing when using Bogus Control Flow.
Doing Post-Run Cleanup
Hikari Out
Spend Time: 1.3452160s
Assertion failed: unsigned(ObjectIdx + NumFixedO…
-
- [ ] RNN
- [ ] KV Cache
- [ ] Sparse MoE
-
### Is there an existing issue for this feature request?
- [X] I have searched the existing issues
### Is your feature request related to a problem?
The problem and explanation:
I know I'm…
-
### Issue to be solved
Add cfi in the C flags to protect the package against non intended code execution flows in the package.
CFI only available on clang and linux, and can be added by extending…
-
# Navigation flow and form control
## Value Proposition
**As a user**
**I want to** have a clear navigation and the ability to show or hide the form on demand
**so that** I can have a more intuiti…
-
### Description
Implement support for the "no-flow-control" SSH extension, per [RFC 8308](https://tools.ietf.org/html/rfc8308#section-3.3).
### Motivation
This may bring some improvements on networ…
-
A significant portion of the garbling/evaluation time in our implementation is spent on branching while iterating over the gates of a circuit. We should optimize it without using `unsafe`.