fsanyoto commited on
Commit
3d2b5ca
·
verified ·
1 Parent(s): b53e972

Deploy Data Management Platform (rename + sales forecast removed)

Browse files
Files changed (1) hide show
  1. app.py +11 -1
app.py CHANGED
@@ -5599,7 +5599,17 @@ def _cl_handle_one(event, uname, allowed_pids, fields, measure_keys=(),
5599
  # If the top-of-run read of the component's own value already covered it, this is False
5600
  # and nothing extra happens; if that read is ever stale, this is what stops the
5601
  # condition hanging unresolved.
5602
- unresolved = {str(r.get('id') or '') for r in _measure_leaves(filters)} - set(resolved_ids)
 
 
 
 
 
 
 
 
 
 
5603
  return bool(unresolved - {''})
5604
 
5605
  if kind == 'view_delete':
 
5599
  # If the top-of-run read of the component's own value already covered it, this is False
5600
  # and nothing extra happens; if that read is ever stale, this is what stops the
5601
  # condition hanging unresolved.
5602
+ #
5603
+ # ⚠ COMPLETE rules only (wave-6 item 3, found by the live roundtrip on this rev):
5604
+ # picking a measure FIELD mints a valueless rule whose autosave used to land here as
5605
+ # "unresolved" and trigger a rerun that could resolve NOTHING — `rule_complete` refuses
5606
+ # half-asked questions — so the only effect was a remount that closed the builder
5607
+ # popover mid-build (the wave-5 "gate flake" runs, now explained). A rule still being
5608
+ # typed stays client-side PENDING by design; the run that matters fires when its VALUE
5609
+ # arrives and the question becomes answerable.
5610
+ from harness import measure_filter as _mfc
5611
+ unresolved = {str(r.get('id') or '') for r in _measure_leaves(filters)
5612
+ if _mfc.rule_complete(r)} - set(resolved_ids)
5613
  return bool(unresolved - {''})
5614
 
5615
  if kind == 'view_delete':