syncOrderExpressions caught its errors and logged them, and returned quietly when there was nothing to build. Those two outcomes are indistinguishable from the outside -- the Bucket and Segment columns are simply absent -- which is most of why this has taken several rounds to pin down. A restore() rejection now raises a message in the status bar, and the no-ordering case logs the inputs it saw: the version's bucket_order and every log entry carrying a seq. One reload should say which of the two is happening. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| assets | ||
| components | ||
| views | ||
| App.css | ||
| App.jsx | ||
| auth.jsx | ||
| index.css | ||
| main.jsx | ||
| theme.jsx | ||