Joe Bryan
4d08d874c6
vere: make full replay (play -f) command bypass corruption
2022-12-16 00:34:15 -05:00
Joe Bryan
f095679e02
Merge pull request #6167 from joemfb/ctrl-z-replay
...
vere: support ctrl-z in play command
2022-12-15 22:04:33 -05:00
Joe Bryan
124aec68ad
term: skip prompt refresh on ^c under -t
2022-12-15 21:48:34 -05:00
Joe Bryan
8671d3091d
u3: make the fault handler robust against initialization reorder
2022-12-15 21:26:30 -05:00
Joe Bryan
f7fd944e02
mars: cleanup event log on exit
2022-12-15 21:22:54 -05:00
Joe Bryan
f4235ebc91
vere: handle ctrl-z like ctrl-c in play command
2022-12-15 21:22:36 -05:00
Zach Alberico
0153d11972
Merge branch 'master' into lf/rebuild-wait-2
2022-12-15 17:36:44 -08:00
Zach Alberico
7714d642ed
Merge pull request #6166 from urbit/merge/master-to-next
...
Merge changes in master back into next/arvo
2022-12-15 14:50:39 -08:00
Zach Alberico
e60e15b022
Merge remote-tracking branch 'origin/master' into merge/master-to-next
2022-12-15 14:04:02 -08:00
Zach Alberico
1e09188065
Merge pull request #6165 from urbit/fix/azimuth-build-break
...
Fix build break typo in azimuth
2022-12-15 13:58:03 -08:00
Zach Alberico
fd766faa03
Fix build break typo in azimuth
...
Fixes typo introduced in 0e16d82a46
2022-12-15 13:21:19 -08:00
Joe Bryan
0901538df2
ci: updates gcp integration for uploading tarballs
2022-12-15 14:42:14 -05:00
Joe Bryan
967f600a7c
ci: updates gcp integration for setting release version strings
2022-12-15 14:38:04 -05:00
Joe Bryan
f8394b9e2b
ci: only save version string and setup gcp if we're uploading binaries
2022-12-15 14:37:13 -05:00
Joe Bryan
e0320ddfc2
vere: bumps version
2022-12-15 14:18:56 -05:00
Joe Bryan
8e677537c0
mars: fix bail:meme retry counter
2022-12-15 14:10:22 -05:00
Joe Bryan
98aa6ee728
Merge pull request #6159 from urbit/jb/mars/play
...
vere: adds dedicated replay command
2022-12-14 19:53:56 -05:00
Joe Bryan
a7880717e3
vere: adds --auto-meld for play subcommand
2022-12-14 18:30:09 -05:00
Joe Bryan
3843c6090f
vere: adds full replay option to play subcommand
2022-12-14 17:47:40 -05:00
Joe Bryan
82d5738df4
vere: adds dedicated replay command: play
2022-12-14 17:47:40 -05:00
Joe Bryan
67ef11117f
vere: updates command docs
2022-12-14 17:47:39 -05:00
Joe Bryan
c15b822087
mars: adds replay implementation
2022-12-14 17:47:39 -05:00
Joe Bryan
a5362f2af0
vere: ports u3_disk_read_list()
2022-12-14 17:47:39 -05:00
Joe Bryan
9daab2fd5a
vere: ports synchronous event log iterator
2022-12-14 17:47:33 -05:00
Joe Bryan
99a8ccda7b
vere: ports synchronous lmdb iterator
2022-12-14 17:47:33 -05:00
Joe Bryan
91f7818ab7
vere: factors out sift/etch functions event serialization
2022-12-14 17:47:33 -05:00
Joe Bryan
5a775d1c79
u3: ports meld measurement printfs
2022-12-14 17:47:33 -05:00
Joe Bryan
fdafdf1f12
u3: ports new arvo invocations for boot and +poke
2022-12-14 17:47:33 -05:00
Joe Bryan
535c49d2db
u3: factors out |mass-style memory measurement
2022-12-14 17:47:33 -05:00
Joe Bryan
5d4142eff8
u3: ports minor noun/ cleanup
2022-12-14 17:47:21 -05:00
Jared Tobin
ed2190dc19
Merge pull request #6146 from urbit/jt/merge-ota
...
ci: add ota-on-merge flow for next/arvo
2022-12-14 16:21:19 -03:30
Liam Fitzgerald
4df4a16881
group-store: add %rebuild poke
2022-12-14 13:29:17 -06:00
Liam Fitzgerald
48978bd940
group-store: allow rebuilding
2022-12-14 12:46:36 -06:00
fang
94dd77bb0e
jael: also send %ruin breaches to catch-all subs
...
Previously, fake breaches triggered by a %ruin task would only get sent to
subscribers watching for the affected ship specifically. Now, we send them to
both those subscribers, and the ones watching for pubkey changes on all ships.
2022-12-13 23:52:10 +01:00
Joe Bryan
a8dadedebf
vere: bumps version
2022-12-13 11:22:13 -05:00
Joe Bryan
6cab63d258
Merge pull request #6152 from urbit/jb/events-interface
...
u3: refactors snapshot system interface
2022-12-13 01:29:33 -05:00
Joe Bryan
af8607fde4
u3: adds comments to road pave implementations
2022-12-13 00:23:47 -05:00
Joe Bryan
ebf0ab49af
u3: adds facade for u3e_ward(), refactors watermarks
2022-12-13 00:23:47 -05:00
Joe Bryan
973cea6d91
u3: refactors u3e_save() facade and watermark calculations
2022-12-13 00:23:47 -05:00
Joe Bryan
c3821c3325
u3: adds facade for u3e_fault(), refactors error handling
2022-12-13 00:23:45 -05:00
Joe Bryan
d043a42128
u3: reimplements guard page w/out posts
2022-12-13 00:09:09 -05:00
Joe Bryan
4659b92d26
u3: factors out individual page protections
2022-12-13 00:09:01 -05:00
Joe Bryan
9fe6f3dde0
u3: refactors loom protect-south page-length calculation
...
blah
2022-12-13 00:07:56 -05:00
Joe Bryan
e378b497cb
u3: fixes compile-time conditionals around guard page impl
2022-12-13 00:07:55 -05:00
Joe Bryan
54e591b719
u3: simplifies u3e_live() signature
2022-12-13 00:07:55 -05:00
Joe Bryan
12229a50e8
u3: adds snapshot facade to manage.c
2022-12-13 00:07:52 -05:00
Hunter Miller
36deb95411
Merge pull request #6150 from urbit/philip/contact-fix
...
contact-store: no-op if adding old contact
2022-12-12 14:28:52 -06:00
Philip Monk
e1419d1787
contact-store: no-op if adding old contact
...
%contact-store is responsible for sending updates about contacts, eg
profile color. When it hears an update, it fans that out to its
subsribers, unless that update is stale. If you reguarly fan out stale
updates, then they reverberate across the network indefinitely -- we
call this "echoing".
To cut off this echoing, all edits have a timestamp, and we consider any
updates from before this timestamp to be stale. Additions are separate
from edits, and for them we instead do a value comparison on the contact
-- if it didn't change, we consider the update stale.
The problem with this scheme is that if an addition and edit happen one
after the other in quick succession, you might have the following
sequence:
- add comes in with timestamp T1
- edit comes in with timestamp T2 after T1
- we hear an echo of the add, and that errantly applies because it
passes our "did the contact actually change" check
- we hear an echo of the edit, which applies because T2 is after T1
- GOTO 3
Each time we apply the stale update, we fan that out to our subscribers,
and if any two hosts subscribe to each other, this will loop. This may
even loop unconditionally because the ship that made the profile changes
seems like it might not recognize that those changes didn't come from
itself, so it sends them to all the groups it's in. If so, that's an
important issue to fix.
Fixes tloncorp/landscape-issues#1442
2022-12-12 13:03:41 -07:00
Jared Tobin
716281cb0d
meta: target ota workflow at ~binnec-dozzod-marzod
2022-12-12 13:53:37 -03:30
Jared Tobin
a51353c4b6
Merge branch 'next/arvo' into jt/merge-ota
2022-12-12 05:29:30 -03:30
