* correct-r-limits:
nix: removes unnecessary use of `cat` in ivory-header build
u3: correctly sets RLIMIT_NOFILE cross-platform
Signed-off-by: Jared Tobin <jared@tlon.io>
This is why basically all packets are going through the galaxies right
now. Most of the time, the flow right now is:
* talking to ~dopzod but don't know where it is, so ask ~zod to forward,
which it does
* ~dopzod responds both directly (on the origin lane) and through ~zod
* (if NAT, the direct response doesn't get back, but the one through
~zod does. Then you respond directly to ~dopzod because their lane
piggybacked on the response. ~dopzod responds both directly and
through ~zod, and the story picks up the same as if you weren't behind a
NAT)
* now you have a direct lane to ~dopzod, so all is well.
* now the duplicate response from ~dopzod through ~zod comes in (takes a
little longer because it's bouncing off ~zod), resetting your lane to
"provisional"
* since your lane is provisional, you send your next packet both
directly and through ~zod
* GOTO 2
This change says "if I already have a direct lane, don't overwrite it
with a provisional one". This way, the only way the direct lane can be
overwritten is if they stop responding on it (cleared on "not
responding; still trying").
I also added |- to +send-blob to make |ames-verb %rot less confusing.
This changes sole.js to handle cursor behaviour for tabbing.
It does so by overriding the cursor position in transpose if it's greater
than it expects. This could produce errant results if other sole apps
use insert behind text, but that seems like an edge case. Flagged for
future with a comment.
If you clicked in the input field, the cursor would stay where it was.
This adds the cursor as a way of controlling the component, fixing the behaviour.
* rc: (451 commits)
ping: delay kick until after ames processes breach
aqua: make faster so moon-az can finish
ping: fix comments
ping: avoid fragile state transitions
ames: don't say not responding if we haven't been talking
eth-watcher; don't start timer if already started
chat: hotfixing a class name
chat: fix sidebar toggle on chat update
dojo: set prompt on watch
gen: add comments on new generators
chat-cli: our-self with bowl set
keys: add +keys for diagnostics
verb: add +verb %bowl to print bowl on every event
azimuth-tracker: add |kick
clay: don't make |cancel require argument
jael: allowed skipped rifts
ames: make life printf helpful
Revert "|ames-verb: fix generator sample type"
|ames-verb: fix generator sample type
gall: correctly construct wire for ap-specific-take
...
Signed-off-by: Jared Tobin <jared@tlon.io>
We were calling it directly, rather than through the (initialized) tc core,
causing the bowl in its context to be the *bowl, resulting in [~zod /] audience.
