Release v0.1.0-alpha.74

[raghavyuva]

Issue

Link to related issue(s):

---

Description

Short summary of what this PR changes or introduces.

---

Scope of Change

Select all applicable areas impacted by this PR:

• View (UI/UX)
• API
• CLI
• Infra / Deployment
• Docs
• Other (specify): ________

---

Screenshot / Video / GIF (if applicable)

Attach or embed screenshots, screen recordings, or GIFs demonstrating the feature or fix.

---

Related PRs (if any)

Link any related or dependent PRs across repos.

---

Additional Notes for Reviewers (optional)

Anything reviewers should know before testing or merging (e.g., environment variables, setup steps).

---

Developer Checklist

To be completed by the developer who raised the PR.

• Add valid/relevant title for the PR
• Self-review done
• Manual dev testing done
• No secrets exposed
• No merge conflicts
• Docs added/updated (if applicable)
• Removed debug prints / secrets / sensitive data
• Unit / Integration tests passing
• Follows all standards defined in Nixopus Docs

---

Reviewer Checklist

To be completed by the reviewer before merge.

• Peer review done
• No console.logs / fmt.prints left
• No secrets exposed
• If any DB migrations, migration changes are verified
• Verified release changes are production-ready

Summary by CodeRabbit

• Chores
  • Notifications and domains settings are temporarily unavailable.
  • SMTP banner notification has been disabled.
  • Related navigation items have been hidden.
• Bug Fixes / Reliability
  • Improved real-time messaging reliability by queuing messages while connecting and handling reconnects more robustly.
  • Fixed monitoring start/stop behavior so live system stats start and stop more reliably.
• Other
  • Release metadata timestamp updated.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR temporarily disables several UI features and navigation items (notifications, domains, SMTP banner) and implements WebSocket message queuing and safer monitoring lifecycle handling across socket and monitoring providers. A version timestamp in api/versions.json was also updated.

Changes

Cohort / File(s)	Summary
Notifications feature disable view/app/settings/notifications/page.tsx, view/app/dashboard/hooks/use-smtp-banner.ts	Comments out notification UI and related imports; replaces notifications page with a disabled-state header/message. use-smtp-banner now redirects to general settings instead of notifications and includes TODO about re-enabling notifications flow.
Dashboard SMTP banner removal view/app/dashboard/page.tsx	Removes/imports and usage of SMTP banner: SMTPBanner import and smtpConfig usage and SMTPBannerConditional component are commented out.
Domains page disable view/app/settings/domains/page.tsx	Wraps original domains page implementation in a block comment and replaces export with a minimal placeholder Page component returning null.
Navigation menu updates view/hooks/use-app-sidebar.ts	Comments out navigation.notifications and navigation.domains submenu items under Settings; adds TODOs for re-enablement.
WebSocket send queuing & reliability view/hooks/socket-provider.tsx	Adds messageQueueRef, queues messages while WS is CONNECTING, flushes queue on OPEN, clears queue on close, adjusts error/close handling, and memoizes send functions with useCallback.
Monitoring lifecycle & memoization view/app/dashboard/hooks/use-monitor.ts, view/hooks/system-stats-provider.tsx	Removes noisy logs; makes start/stop monitoring memoized with useCallback; guards monitoring actions on isReady/isMonitoring; reset initialization and stop monitoring when WS readiness becomes false.
Version metadata update api/api/versions.json	Updates v1.release_date timestamp value.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

• Heterogeneous changes: UI feature toggles across multiple pages + non-trivial WebSocket behavior changes.
• Areas needing extra attention:
  • view/hooks/socket-provider.tsx: verify queue semantics, race conditions, and correct cleanup on reconnects/close.
  • Monitoring lifecycle changes in use-monitor.ts and system-stats-provider.tsx: ensure no regressions or missed edge cases when readiness toggles.
  • Ensure no orphaned imports or unused code remain in commented blocks and navigation consistency across the app.
  • Confirm use-smtp-banner redirect destination is correct and does not break other flows.

Possibly related PRs

• feat: improve dashboard monitoring | reset cache feature flags #557 — Modifies view/app/dashboard/hooks/use-monitor.ts and touches monitoring lifecycle; directly related to monitoring changes here.
• chore: move sidebar nav-user items to footer #527 — Modifies view/hooks/use-app-sidebar.ts and sidebar items; related to the commented-out navigation entries.
• release v0.1.0-alpha.31 #428 — Updates api/api/versions.json (v1.release_date); directly related metadata change.

Poem

🐰 A nibble, a hop — the banners nap,
Menus tuck in, code folded on the map,
Sockets queue their letters tight,
Monitoring waits till day from night,
I'll guard these TODOs with carrot-light! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Release v0.1.0-alpha.74' accurately describes a release version bump, which aligns with the changes across multiple files (version update in api/api/versions.json, feature disablement for notifications/domains flows, and socket provider improvements).

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/develop

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 95fcf40 and c50c583.

📒 Files selected for processing (4)

• api/api/versions.json (1 hunks)
• view/app/dashboard/hooks/use-monitor.ts (2 hunks)
• view/hooks/socket-provider.tsx (6 hunks)
• view/hooks/system-stats-provider.tsx (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test

🔇 Additional comments (17)

api/api/versions.json (1)

4-6: No changes needed. The file correctly maintains API versioning (v1) separate from application versioning (0.1.0-alpha.74+). Release documentation is properly tracked in CHANGELOG.md. The timestamp update is appropriate.

Likely an incorrect or invalid review comment.

view/hooks/socket-provider.tsx (7)

3-11: LGTM!

Clean import restructuring with proper useCallback addition for the new memoized functions.

---

48-48: LGTM!

Good use of useRef for the message queue—avoids unnecessary re-renders while providing mutable storage for pending messages.

---

94-100: LGTM!

The queue flushing logic properly drains queued messages in FIFO order with appropriate readyState guards. Good defensive check on each iteration.

---

107-107: LGTM!

Clearing the queue on close prevents stale messages from being sent on subsequent reconnection.

---

118-121: LGTM!

Simplified error handler. Since onclose always fires after onerror per the WebSocket spec, reconnection logic is still triggered appropriately.

---

181-190: LGTM!

Proper use of useCallback with empty dependencies—refs are stable, and .current is read at call time ensuring fresh values. The queuing behavior for CONNECTING state is a nice improvement over dropping messages.

---

192-203: LGTM!

Consistent pattern with sendMessage. The memoization ensures stable function identity for downstream consumers.

view/hooks/system-stats-provider.tsx (6)

3-11: LGTM!

Clean import restructuring with useCallback addition.

---

62-74: LGTM!

Good guard conditions to prevent duplicate monitoring requests. Dependency array correctly includes all referenced values.

---

76-83: LGTM!

Proper guard to avoid sending unnecessary stop messages. Dependencies are correct.

---

90-94: LGTM!

Proper state reset when WebSocket disconnects. Correctly avoids sending a stop message since the socket is already unavailable.

---

101-101: LGTM!

Correct dependency update—startMonitoring is properly included since the effect uses it.

---

114-114: LGTM!

Proper dependency inclusion for startMonitoring.

view/app/dashboard/hooks/use-monitor.ts (3)

16-16: LGTM!

Clean simplification—removes verbose logging while maintaining the guard behavior.

---

79-82: LGTM!

Proper state reset when WebSocket readiness is lost. Mirrors the pattern in system-stats-provider.tsx for consistency across monitoring hooks.

---

69-69: LGTM!

Dependency array correctly includes startMonitoring, avoiding the stale closure issue.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between beba9e3 and 95fcf40.

📒 Files selected for processing (5)

• view/app/dashboard/hooks/use-smtp-banner.ts (1 hunks)
• view/app/dashboard/page.tsx (4 hunks)
• view/app/settings/domains/page.tsx (2 hunks)
• view/app/settings/notifications/page.tsx (2 hunks)
• view/hooks/use-app-sidebar.ts (1 hunks)

🔇 Additional comments (4)

view/hooks/use-app-sidebar.ts (1)

64-80: LGTM - Navigation items properly disabled.

The notifications and domains navigation items are cleanly removed with TODO comments for future re-enablement. The imports for their related APIs are correctly retained since they're still used in resetApiStates() at lines 131-142.

view/app/settings/notifications/page.tsx (1)

23-35: Good approach to disabled state handling.

The early return with an informative message provides better user experience than a blank page. This approach should be the standard for temporarily disabled features across the codebase.

view/app/dashboard/hooks/use-smtp-banner.ts (1)

25-28: LGTM - Appropriate fallback for disabled notifications.

The redirect to general settings is a reasonable fallback while the notifications feature is disabled. The hook logic is preserved for when the SMTP banner is re-enabled.

view/app/dashboard/page.tsx (1)

18-19: LGTM - Clean temporary removal of SMTP banner.

The SMTP banner feature is consistently disabled across all touchpoints (import, destructuring, rendering, component definition). The code structure is well-preserved with TODO comments for future re-enablement.

Also applies to: 38-39, 113-114, 195-199