forked from trent_larson/crowd-funder-for-time-pwa
2d17bfd3b4
- Update BUILDING.md with current build system information - Modernize various README files across the project - Update CHANGELOG.md with recent changes - Improve documentation consistency and formatting - Update platform-specific documentation (iOS, Electron, Docker) - Enhance test documentation and build guides
97 lines
3.1 KiB
Markdown
97 lines
3.1 KiB
Markdown
# Error Diagnostics Log
|
|
|
|
This file tracks console errors observed during development for future investigation.
|
|
|
|
## 2025-07-07 08:56 UTC - ProjectsView.vue Migration Session
|
|
|
|
### Migration Context
|
|
|
|
- **Current Work**: Completed ProjectsView.vue Triple Migration Pattern
|
|
- **Migration Status**: 21 complete, 4 appropriately incomplete components
|
|
- **Recent Changes**:
|
|
- ProjectsView.vue: databaseUtil → PlatformServiceMixin
|
|
- Added notification constants and literal string extraction
|
|
- Template logic streamlining with computed properties
|
|
|
|
### Observed Errors
|
|
|
|
#### 1. HomeView.vue API Rate Limit Errors
|
|
|
|
```
|
|
GET https://api.endorser.ch/api/report/rateLimits 400 (Bad Request)
|
|
Source: endorserServer.ts:1494, HomeView.vue:593, HomeView.vue:742
|
|
```
|
|
|
|
**Analysis**:
|
|
|
|
- API server returning 400 for rate limit checks
|
|
- Occurs during identity initialization and registration status checks
|
|
- **Migration Impact**: None - HomeView.vue was migrated and tested earlier
|
|
- **Likely Cause**: Server-side authentication or API configuration issue
|
|
|
|
**Action Items**:
|
|
|
|
- [ ] Check endorser.ch API documentation for rate limit endpoint changes
|
|
- [ ] Verify authentication headers being sent correctly
|
|
- [ ] Consider fallback handling for rate limit API failures
|
|
|
|
#### 2. ProjectViewView.vue Project Not Found Error
|
|
|
|
```
|
|
GET https://api.endorser.ch/api/claim/byHandle/...01JY2Q5D90E8P267ABB963S71D 404 (Not Found)
|
|
Source: ProjectViewView.vue:830 loadProject() method
|
|
```
|
|
|
|
**Analysis**:
|
|
|
|
- Attempting to load project ID: `01JY2Q5D90E8P267ABB963S71D`
|
|
- **Migration Impact**: None - error handling working correctly
|
|
- **Likely Cause**: User navigated to non-existent project or stale link
|
|
|
|
**Action Items**:
|
|
|
|
- [ ] Consider adding better user messaging for missing projects
|
|
- [ ] Investigate if project IDs are being generated/stored correctly
|
|
- [ ] Add breadcrumb or "return to projects" option on 404s
|
|
|
|
#### 3. Axios Request Stack Traces
|
|
|
|
Multiple stack traces showing Vue router navigation and component mounting cycles.
|
|
|
|
**Analysis**:
|
|
|
|
- Normal Vue.js lifecycle and routing behavior
|
|
- No obvious memory leaks or infinite loops
|
|
- **Migration Impact**: None - expected framework behavior
|
|
|
|
### System Health Indicators
|
|
|
|
#### ✅ Working Correctly
|
|
|
|
- Database migrations: `Migration process complete! Summary: 0 applied, 2 skipped`
|
|
- Platform service factory initialization: `Creating singleton instance for platform: development`
|
|
- SQL worker loading: `Worker loaded, ready to receive messages`
|
|
- Database connection: `Opened!`
|
|
|
|
#### 🔄 For Investigation
|
|
|
|
- API authentication/authorization with endorser.ch
|
|
- Project ID validation and error handling
|
|
- Rate limiting strategy
|
|
|
|
### Migration Validation
|
|
|
|
- **ProjectsView.vue**: Appropriately incomplete (3 helpers + 1 complex modal)
|
|
- **Error Handling**: Migrated components showing proper error handling
|
|
- **No Migration-Related Errors**: All errors appear to be infrastructure/data issues
|
|
|
|
### Next Steps
|
|
|
|
1. Continue migration slog with next component
|
|
2. Monitor these same error patterns in future sessions
|
|
3. Address API/server issues in separate debugging session
|
|
|
|
---
|
|
*Log Entry by: Migration Assistant*
|
|
*Session: ProjectsView.vue Triple Migration Pattern*
|