Skip to content

Fix missing chromium template error for apps#104

Merged
JoshuaAFerguson merged 2 commits into
mainfrom
claude/fix-chromium-template-error-01W23Qkn7Bod65aB6dJdysw6
Nov 19, 2025
Merged

Fix missing chromium template error for apps#104
JoshuaAFerguson merged 2 commits into
mainfrom
claude/fix-chromium-template-error-01W23Qkn7Bod65aB6dJdysw6

Conversation

@JoshuaAFerguson

Copy link
Copy Markdown
Member

No description provided.

This change improves application launching reliability and error messages:

- Modified CreateSession API to accept optional applicationId parameter
- When applicationId is provided, the API now looks up the installed
  application to get the correct template name
- Added validation for application enabled status and installation state
- Provides specific error messages for:
  - Application not found
  - Application disabled
  - Installation failed
  - Installation still pending
  - Missing template configuration
- Updated frontend Dashboard to send applicationId instead of templateName
- Updated CreateSessionRequest interface to support applicationId

This fixes the "Template not found" error when launching applications from
the dashboard by ensuring the correct template name is resolved from the
installed application record.
Enhanced error messages to include contextual information for debugging:

Database layer (sessions.go):
- All session operations now wrap errors with session ID, user ID context
- Error messages include operation type (create, update, delete, query)

API handlers improved:
- quotas.go: 23 errors with user/team IDs, quota values
- batch.go: 11 errors with user ID, session counts, operation types
- scheduling.go: 12 errors with schedule ID, user ID, template info
- loadbalancing.go: 8 errors with policy names, node info, scaling details
- preferences.go: 15 errors with user ID, preference keys
- security.go: 16 errors with MFA IDs, user IDs, IP addresses
- collaboration.go: 11 errors with collaboration ID, user ID, annotation ID

All errors now follow consistent pattern:
- "error": Short description of what failed
- "message": Detailed context with IDs and underlying error

This makes debugging significantly easier by showing exactly what
operation failed, which entity was involved, and the root cause.
@JoshuaAFerguson JoshuaAFerguson merged commit 3af8551 into main Nov 19, 2025
0 of 8 checks passed
@JoshuaAFerguson JoshuaAFerguson deleted the claude/fix-chromium-template-error-01W23Qkn7Bod65aB6dJdysw6 branch November 19, 2025 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants