Fix PowerShell regex syntax error in start.ps1

.kiro/specs/powershell-regex-fix/design.md

@@ -0,0 +1,78 @@
+# Design Document
+
+## Overview
+
+The PowerShell startup script (start.ps1) contains a syntax error where a regex pattern used for parsing environment variables is incorrectly split across multiple lines. This design document outlines the solution to fix this issue by ensuring the regex pattern is properly formatted on a single line.
+
+## Architecture
+
+The fix involves modifying the environment variable parsing section of the PowerShell script. The current implementation attempts to use a regex pattern that spans multiple lines, which is invalid PowerShell syntax.
+
+### Current Implementation Issue
+
+```powershell
+if ($value -match '^[''"](.*)[''"]\s*
+</content>
+</file>) {
+    $value = $matches[1]
+}
+```
+
+### Proposed Solution
+
+```powershell
+if ($value -match '^[''"](.*)[''"]\s*$') {
+    $value = $matches[1]
+}
+```
+
+## Components and Interfaces
+
+### Environment Variable Parser
+- **Location**: start.ps1, lines 10-15
+- **Function**: Reads .env file and processes key-value pairs
+- **Interface**: Processes each line of the .env file and sets environment variables
+
+### Regex Pattern Matcher
+- **Pattern**: `^[''"](.*)[''"]\s*$`
+- **Purpose**: Matches quoted values and extracts the content without quotes
+- **Input**: Environment variable value string
+- **Output**: Cleaned value without surrounding quotes
+
+## Data Models
+
+### Environment Variable Entry
+- **Key**: String representing the environment variable name
+- **Value**: String representing the environment variable value (may be quoted)
+- **Processed Value**: String with quotes removed if present
+
+## Error Handling
+
+### Current Error Scenarios
+1. **Syntax Error**: The malformed regex causes PowerShell parsing errors
+2. **Runtime Failure**: Script may fail to execute due to syntax issues
+
+### Proposed Error Handling
+1. **Syntax Validation**: Ensure the regex pattern is syntactically correct
+2. **Pattern Matching**: Handle cases where values are not quoted
+3. **Graceful Degradation**: If regex fails, use the original value
+
+## Testing Strategy
+
+### Unit Testing
+- Test the regex pattern with various input formats:
+  - Single-quoted values: `'value'`
+  - Double-quoted values: `"value"`
+  - Unquoted values: `value`
+  - Values with spaces: `"value with spaces"`
+  - Empty values: `""`
+
+### Integration Testing
+- Test the complete environment variable parsing process
+- Verify that all environment variables are correctly set
+- Ensure the PowerShell script executes without errors
+
+### Manual Testing
+- Run the PowerShell script on a Windows system
+- Verify that Docker services start correctly
+- Confirm that the application initializes properly

.kiro/specs/powershell-regex-fix/requirements.md

@@ -0,0 +1,25 @@
+# Requirements Document
+
+## Introduction
+
+This document outlines the requirements for fixing a syntax error in the PowerShell startup script (start.ps1) where a regex pattern is incorrectly split across multiple lines, causing potential parsing issues.
+
+## Glossary
+
+- **PowerShell Script**: The start.ps1 file used to initialize the Potpie application on Windows systems
+- **Regex Pattern**: A regular expression pattern used to match and extract quoted values from environment variables
+- **Environment Variable Parser**: The code section that reads and processes .env file contents
+
+## Requirements
+
+### Requirement 1
+
+**User Story:** As a Windows developer, I want the PowerShell startup script to execute without syntax errors, so that I can successfully start the Potpie application.
+
+#### Acceptance Criteria
+
+1. WHEN the PowerShell script is executed, THE PowerShell_Script SHALL parse without syntax errors
+2. WHEN processing environment variables with quoted values, THE Environment_Variable_Parser SHALL correctly extract the values using a properly formatted regex pattern
+3. WHEN the regex pattern is defined, THE PowerShell_Script SHALL contain the complete pattern on a single line
+4. IF the regex pattern spans multiple lines, THEN THE PowerShell_Script SHALL fail to parse correctly
+5. WHERE the environment variable contains quoted values, THE Environment_Variable_Parser SHALL remove surrounding quotes using the corrected regex pattern

.kiro/specs/powershell-regex-fix/tasks.md

@@ -0,0 +1,27 @@
+# Implementation Plan
+
+- [x] 1. Fix the regex pattern syntax error in start.ps1
+
+
+  - Locate the malformed regex pattern on line 11-12 of start.ps1
+  - Correct the regex pattern to be on a single line: `'^[''"](.*)[''"]\s*$'`
+  - Ensure proper PowerShell syntax for the if statement
+  - _Requirements: 1.1, 1.3_
+
+- [ ] 2. Create test cases for environment variable parsing
+  - Write test cases for quoted and unquoted environment variables
+  - Test edge cases like empty values and values with special characters
+  - Verify regex pattern matches expected inputs
+  - _Requirements: 1.2, 1.5_
+
+- [ ] 3. Validate the PowerShell script syntax
+  - Run PowerShell syntax validation on the corrected script
+  - Ensure the script can be parsed without errors
+  - Test the script execution in a safe environment
+  - _Requirements: 1.1_
+
+- [ ] 4. Document the fix and add comments
+  - Add inline comments explaining the regex pattern purpose
+  - Update any relevant documentation about the startup process
+  - Document the bug fix for future reference
+  - _Requirements: 1.2_

start.ps1

@@ -80,4 +80,4 @@ Start-Process -NoNewWindow powershell -ArgumentList "uvicorn app.main:app --host
 Write-Host "Starting Celery worker"
 Start-Process -NoNewWindow powershell -ArgumentList "celery -A app.celery.celery_app worker --loglevel=debug -Q ${Env:CELERY_QUEUE_NAME}_process_repository,${Env:CELERY_QUEUE_NAME}_agent_tasks -E --pool=solo"
 
-Write-Host "All services started successfully!"
+Write-Host "All services started successfully!"