[PR #404] [MERGED] fix: resolve onboarding session not found warnings and frontend build… #711

Closed
opened 2026-03-13 21:05:04 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/AJaySi/ALwrity/pull/404
Author: @AJaySi
Created: 3/9/2026
Status: Merged
Merged: 3/9/2026
Merged by: @AJaySi

Base: mainHead: feature/website-maker-phase1


📝 Commits (1)

  • b3cc83e fix: resolve onboarding session not found warnings and frontend build OOM

📊 Changes

13 files changed (+1708 additions, -20 deletions)

View changed files

📝 backend/api/onboarding_utils/endpoints_config_data.py (+88 -0)
📝 backend/api/onboarding_utils/endpoints_core.py (+2 -2)
📝 backend/api/onboarding_utils/onboarding_control_service.py (+2 -2)
📝 backend/api/onboarding_utils/step_management_service.py (+4 -4)
backend/api/onboarding_utils/website_automation_service.py (+250 -0)
backend/models/user_website_request.py (+121 -0)
📝 backend/services/onboarding/api_key_manager.py (+12 -9)
backend/services/onboarding/website_automation_service.py (+206 -0)
backend/services/onboarding/website_intake_service.py (+285 -0)
backend/services/onboarding/website_style_service.py (+439 -0)
backend/services/user_website_service.py (+295 -0)
📝 frontend/package.json (+2 -1)
📝 frontend/src/stores/workflowStore.ts (+2 -2)

📄 Description

… OOM

  • Use canonical Clerk user id (clerk_user_id) across all onboarding entrypoints to ensure consistent OnboardingSession.user_id lookup
  • Fix API key persistence in api_key_manager.py to use correct APIKey model columns (session_id, provider, key)
  • Increase Node heap for frontend build to 8GB and add build:nomap script to disable sourcemaps and reduce memory usage
  • Update onboarding endpoints (endpoints_core.py, onboarding_control_service.py, step_management_service.py) to prefer clerk_user_id over id
  • Fix frontend workflowStore.ts TypeScript error by returning WorkflowError instance
  • Add website_automation_service.py for onboarding automation

Pull Request

📝 Description

Brief description of changes made in this PR.

🔄 Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🎨 Style/UI changes
  • ♻️ Code refactoring
  • Performance improvements
  • 🧪 Test additions/updates

Closes #(issue number)
Fixes #(issue number)
Related to #(issue number)

🧪 Testing

  • Backend tests pass
  • Frontend tests pass
  • Manual testing completed
  • Cross-browser testing (if applicable)
  • Mobile testing (if applicable)

📸 Screenshots (if applicable)

Add screenshots to help explain your changes.

Before

After

🏷️ Component/Feature

Which component or feature is affected?

  • Blog Writer
  • SEO Dashboard
  • Content Planning
  • Facebook Writer
  • LinkedIn Writer
  • Onboarding
  • Authentication
  • API
  • Database
  • GSC Integration
  • Subscription System
  • Monitoring/Billing
  • Documentation
  • Other: _______________

📋 Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published

ALwrity-Specific Checklist

  • API endpoints follow RESTful conventions
  • AI service integrations handle rate limits and errors gracefully
  • Content generation includes proper validation and sanitization
  • Database migrations are included if schema changes are made
  • Environment variables are documented in env_template.txt
  • Security considerations have been addressed
  • Performance impact has been considered
  • User experience is consistent with existing features

🔍 Code Quality

  • Code is properly formatted
  • No console.log statements left in production code
  • Error handling is implemented where needed
  • Performance considerations have been addressed
  • Security considerations have been addressed

📚 Documentation

  • README updated (if needed)
  • API documentation updated (if needed)
  • Code comments added for complex logic
  • Changelog updated (if applicable)

🚀 Deployment Notes

Any special deployment considerations or environment variables needed.

🔗 Additional Context

Add any other context about the pull request here.

👥 Reviewers

Tag specific reviewers if needed:
@AJaySi @uniqueumesh @DikshaDisciplines


Thank you for contributing to ALwrity! 🎉


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/AJaySi/ALwrity/pull/404 **Author:** [@AJaySi](https://github.com/AJaySi) **Created:** 3/9/2026 **Status:** ✅ Merged **Merged:** 3/9/2026 **Merged by:** [@AJaySi](https://github.com/AJaySi) **Base:** `main` ← **Head:** `feature/website-maker-phase1` --- ### 📝 Commits (1) - [`b3cc83e`](https://github.com/AJaySi/ALwrity/commit/b3cc83ed6e2a88fac491be7d4b74922dc3a07526) fix: resolve onboarding session not found warnings and frontend build OOM ### 📊 Changes **13 files changed** (+1708 additions, -20 deletions) <details> <summary>View changed files</summary> 📝 `backend/api/onboarding_utils/endpoints_config_data.py` (+88 -0) 📝 `backend/api/onboarding_utils/endpoints_core.py` (+2 -2) 📝 `backend/api/onboarding_utils/onboarding_control_service.py` (+2 -2) 📝 `backend/api/onboarding_utils/step_management_service.py` (+4 -4) ➕ `backend/api/onboarding_utils/website_automation_service.py` (+250 -0) ➕ `backend/models/user_website_request.py` (+121 -0) 📝 `backend/services/onboarding/api_key_manager.py` (+12 -9) ➕ `backend/services/onboarding/website_automation_service.py` (+206 -0) ➕ `backend/services/onboarding/website_intake_service.py` (+285 -0) ➕ `backend/services/onboarding/website_style_service.py` (+439 -0) ➕ `backend/services/user_website_service.py` (+295 -0) 📝 `frontend/package.json` (+2 -1) 📝 `frontend/src/stores/workflowStore.ts` (+2 -2) </details> ### 📄 Description … OOM - Use canonical Clerk user id (clerk_user_id) across all onboarding entrypoints to ensure consistent OnboardingSession.user_id lookup - Fix API key persistence in api_key_manager.py to use correct APIKey model columns (session_id, provider, key) - Increase Node heap for frontend build to 8GB and add build:nomap script to disable sourcemaps and reduce memory usage - Update onboarding endpoints (endpoints_core.py, onboarding_control_service.py, step_management_service.py) to prefer clerk_user_id over id - Fix frontend workflowStore.ts TypeScript error by returning WorkflowError instance - Add website_automation_service.py for onboarding automation # Pull Request ## 📝 Description Brief description of changes made in this PR. ## 🔄 Type of Change - [ ] 🐛 Bug fix (non-breaking change which fixes an issue) - [ ] ✨ New feature (non-breaking change which adds functionality) - [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] 📚 Documentation update - [ ] 🎨 Style/UI changes - [ ] ♻️ Code refactoring - [ ] ⚡ Performance improvements - [ ] 🧪 Test additions/updates ## 🎯 Related Issues Closes #(issue number) Fixes #(issue number) Related to #(issue number) ## 🧪 Testing - [ ] Backend tests pass - [ ] Frontend tests pass - [ ] Manual testing completed - [ ] Cross-browser testing (if applicable) - [ ] Mobile testing (if applicable) ## 📸 Screenshots (if applicable) Add screenshots to help explain your changes. ### Before <!-- Add before screenshots here --> ### After <!-- Add after screenshots here --> ## 🏷️ Component/Feature Which component or feature is affected? - [ ] Blog Writer - [ ] SEO Dashboard - [ ] Content Planning - [ ] Facebook Writer - [ ] LinkedIn Writer - [ ] Onboarding - [ ] Authentication - [ ] API - [ ] Database - [ ] GSC Integration - [ ] Subscription System - [ ] Monitoring/Billing - [ ] Documentation - [ ] Other: _______________ ## 📋 Checklist - [ ] My code follows the project's style guidelines - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published ### ALwrity-Specific Checklist - [ ] API endpoints follow RESTful conventions - [ ] AI service integrations handle rate limits and errors gracefully - [ ] Content generation includes proper validation and sanitization - [ ] Database migrations are included if schema changes are made - [ ] Environment variables are documented in env_template.txt - [ ] Security considerations have been addressed - [ ] Performance impact has been considered - [ ] User experience is consistent with existing features ## 🔍 Code Quality - [ ] Code is properly formatted - [ ] No console.log statements left in production code - [ ] Error handling is implemented where needed - [ ] Performance considerations have been addressed - [ ] Security considerations have been addressed ## 📚 Documentation - [ ] README updated (if needed) - [ ] API documentation updated (if needed) - [ ] Code comments added for complex logic - [ ] Changelog updated (if applicable) ## 🚀 Deployment Notes Any special deployment considerations or environment variables needed. ## 🔗 Additional Context Add any other context about the pull request here. ## 👥 Reviewers Tag specific reviewers if needed: @AJaySi @uniqueumesh @DikshaDisciplines --- **Thank you for contributing to ALwrity!** 🎉 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-13 21:05:04 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ALwrity#711
No description provided.