fsanyoto commited on
Commit
0ab3e74
·
verified ·
1 Parent(s): 099ed35

Deploy AIOS web (React glide grid + FastAPI slice)

Browse files
RELEASES.json CHANGED
@@ -1,4 +1,4 @@
1
  {
2
- "current": "3ba892f",
3
  "releases": []
4
  }
 
1
  {
2
+ "current": "f6781fe",
3
  "releases": []
4
  }
VERSION CHANGED
@@ -1 +1 @@
1
- 3ba892f
 
1
+ f6781fe
api/test_odoo_rank_refresh.py CHANGED
@@ -139,7 +139,15 @@ class RankRefreshTests(unittest.TestCase):
139
  _resolve_resync_cadence=lambda: dict(resolvedSeconds=60, manual=False,
140
  tenant='synthetic', tenantSource='test', tenantSeconds=60,
141
  envSeconds=60, disagreement=None),
 
 
 
 
 
 
 
142
  _resync_mirror_pass=sync, _pull_meta=lambda *_: True,
 
143
  _rebuild_odoo_relational=rebuild,
144
  _rebuild_meta_relational=lambda *_: {},
145
  _rebuild_amazon_relational=lambda *_: {})
 
139
  _resolve_resync_cadence=lambda: dict(resolvedSeconds=60, manual=False,
140
  tenant='synthetic', tenantSource='test', tenantSeconds=60,
141
  envSeconds=60, disagreement=None),
142
+ # ⛔ THIS NAMESPACE IS HAND-MAINTAINED, so a NEW collaborator inside
143
+ # `_store_resync_loop` arrives here as a bare `NameError` from a synthetic
144
+ # module rather than as a readable failure. W59-T42 added `_pull_amazon`
145
+ # one line after `_pull_meta` at `main.py:1416`, and all four resident-loop
146
+ # tests died on it -- in the MERGED tree only: lane G does not run this
147
+ # gate and lane D's run predates lane G. The real `main.py` defines the
148
+ # function at module scope and the deployed Space boots fine.
149
  _resync_mirror_pass=sync, _pull_meta=lambda *_: True,
150
+ _pull_amazon=lambda *_: True,
151
  _rebuild_odoo_relational=rebuild,
152
  _rebuild_meta_relational=lambda *_: {},
153
  _rebuild_amazon_relational=lambda *_: {})
web/src/shell/Shell.tsx CHANGED
@@ -473,7 +473,17 @@ function ApplicationWizard({
473
  }
474
  if (shareEntries.length > 0) {
475
  try {
476
- const shareResponse = await fetch(`${API_V1}/nav/applications/${encodeURIComponent(body.application.id)}`, {
 
 
 
 
 
 
 
 
 
 
477
  method: "PATCH",
478
  credentials: CREDENTIALS,
479
  headers: { "Content-Type": "application/json" },
 
473
  }
474
  if (shareEntries.length > 0) {
475
  try {
476
+ // ⛔⛔ FIXED AT THE WAVE-59 COMBINE: this PATCHed `/nav/applications/{id}`, and NO
477
+ // SUCH ROUTE EXISTS -- `routes_nav.py` mounts only `POST /nav/applications`. Every
478
+ // create therefore fell into the catch below and reported "sharing did not save",
479
+ // so W59-T26's done-when ("creating the app persists those grants") could not hold.
480
+ // The reviewed door is `PATCH /applications/{id}` in `routes_assets.py`, which
481
+ // passes the body to `application_registry.mutate` -- and that is the writer that
482
+ // already understands `{share: {mode, users}}`, the exact shape sent below.
483
+ // ⚠ Only api_api's D-48 leg could see this: it is the one check that matches every
484
+ // decidable client fetch path against a route the app actually MOUNTED, it belongs
485
+ // to lane F, and lane E owned neither it nor `routes_nav.py`.
486
+ const shareResponse = await fetch(`${API_V1}/applications/${encodeURIComponent(body.application.id)}`, {
487
  method: "PATCH",
488
  credentials: CREDENTIALS,
489
  headers: { "Content-Type": "application/json" },