When we receive a watch-nack on a versioned subscription, we attempt to
resubscribe on an unversioned path. However, if we receive an unversioned
subscription request for which we are not compatible, we hold the
subscription open and never send any facts on unversioned subscriptions.
As the check for unversioned compatiblility occurs before retrieving the
initial-watch, subscriptions which are supposed to nack never do. Fixed
by moving the conditional.
Fixesurbit/landscape#795
If arvo indicates it needs a newer runtime to apply an upgrade, we now
display a persistent notification on the notifications screen and
turn the base hash background yellow.
This also gives a yellow notification dot, but it's overridden by the
blue one if there are regular notifications too.
* origin/lf/init-upd-log: (257 commits)
graph: bunt time to ensure deduplication
graph-store: initialise update logs
glob: update to 0v7.dmf2h.884m6.b2p1b.l1and.uv1lv
VirtualScroller: fix pendings and scroll after jump
hark: fix notification archival
interface: include iPad in UA check
graph-store: fix %add/remove-tag generators
chat: refocus and reset state on submit, allow enter linebreaks on mobile
glob: update to 0v3.m4922.94fro.soub7.2cod3.0rfhh
hooks: address L review
VirtualScroller: do not crash if ref is unset
interface: graph-reducer, put empty string when hash is null
ChatPane: invert showOurContact conditional
ChatResource: refactor to use ChatPane
ChatPane: add component
ShareProfile: refactor to remove dead props
ChatWindow: remove association prop
ChatInput: lift callbacks, refactor
ChatMessage: refactor to remove association prop
withStorage: fix typings
...
Signed-off-by: Matilde Park <matilde.park@gmail.com>
The varying timestamp in the %add-graph fact from graph-push-hook was
preventing deduplication of the jammed noun in ames. Prevents
unnecessary bail: memes upon sending many %add-graph facts
