Conversation
…enting overexposure
…to bes-mtk-ota
The console and CLI publish routes (POST /api/console/apps/:pkg/publish, POST /api/cli/apps/:pkg/publish) were setting appStoreStatus directly to PUBLISHED for any org admin, bypassing the admin approval flow entirely. Changes: - Add shared isMentraAdmin(email) utility that checks @mentra.glass, @mentraglass.com domains and the ADMIN_EMAILS env var - console.apps.service publishApp: non-Mentra-admins now set SUBMITTED (queued for review); Mentra admins can still publish directly - Hono admin.routes validateAdminEmail: use isMentraAdmin() instead of only checking ADMIN_EMAILS (adds @mentraglass.com support) - Hono developer.routes publishApp: add ownership verification before allowing submission (was missing entirely) - Express admin-auth.middleware: use shared isMentraAdmin() utility, adds @mentraglass.com domain support
- Add MetricsService singleton with Prometheus /metrics endpoint and enriched /health - Track: user sessions, miniapp sessions, event loop lag (current/avg/p99), UDP stats, WS client/miniapp messages in/out, HTTP requests by status, memory, uptime - Wire WS counters in bun-websocket.ts and AppManager.sendMessageToApp() - Wire HTTP counters in hono-app middleware - Add SONIOX_MODEL env var (default stt-rt-v4) for transcription + translation providers - Update porter-debug workflow to deploy from cloud/cloud-scaling - Add issue docs for 032-cloud-scaling and 033-soniox-model-update
…app does not have it
…equality The strict org-id comparison could false-403 multi-org users when the x-org-id header defaults to a different org than the app's owner. Use OrganizationService.isOrgAdmin against the app's actual org instead, matching the pattern used in console.apps.service and getAppByPackageName.
- REST handler validates requestId, success, photoUrl (on success) - Builds typed PhotoResponse before passing to PhotoManager - Error payloads lenient (crash path), fall back to UNKNOWN_ERROR - PhotoManager.handlePhotoResponse now takes PhotoResponse, not any - No unvalidated data flows downstream to apps
Root cause: BackgroundTimer (react-native-nitro-bg-timer) dispatches callbacks via JSI at higher priority than RN's WebSocket onmessage events. After CONNECTION_ACK, the JS thread is busy with REST calls and UDP setup. The NitroTimer liveness check fires before queued onmessage callbacks can update lastMessageTime -> false timeout. Fix: - Use plain setInterval for liveness timers (same priority as onmessage) - Add client-side ping sender (2s interval, as originally spec'd in 034) - Increase liveness timeout from 4s to 8s BackgroundTimer still used for reconnect interval (needs to fire when backgrounded). Verified via BetterStack: server was sending display events every 0.4-1.5s but client never received them. 170/180 closes on dev were code 1000 (client-initiated). Pattern: connect -> 5s -> timeout -> 5s reconnect -> repeat. See: cloud/issues/034-ws-liveness/post-mortem.md (Feb 18 update)
This reverts commit 4ee4922.
…rors cloud/photo-request-errors Fix: reject photo request Promise immediately on error instead of 30s timeout
…ream-dedup cloud/transcription-stream-dedup
dev to staging
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying prod-augmentos-account with
|
| Latest commit: |
1167c6a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6b1c343c.augmentos-e84.pages.dev |
| Branch Preview URL: | https://dev.augmentos-e84.pages.dev |
Deploying mentra-store-beta with
|
| Latest commit: |
1167c6a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://56cbab6e.mentra-store-beta.pages.dev |
Deploying mentra-live-ota-site with
|
| Latest commit: |
1167c6a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3d24e3e7.mentra-live-ota-site.pages.dev |
| Branch Preview URL: | https://dev.mentra-live-ota-site.pages.dev |
Deploying mentra-store-dev with
|
| Latest commit: |
1167c6a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://140ac46e.augmentos-appstore-2.pages.dev |
Deploying dev-augmentos-console with
|
| Latest commit: |
1167c6a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2c5277f4.dev-augmentos-console.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.