Skip to content

Error messages not showing in toolbar (vibe-kanban) #246

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

stunningpixels
Copy link
Contributor

When I try to perform an action, for example rebase, if it fails it just says "failed to rebase branch" in the UI, but in the API logs I can see

{
"success": false,
"data": null,
"message": "Git service error: Merge conflicts: Rebase failed due to conflicts. Please resolve conflicts manually."
}

  • First the response should not be success
  • Second, this should be displayed to the user rather than the unhelpful generic message

stunningpixels and others added 2 commits July 17, 2025 15:49
I've successfully fixed the error message handling issue. The problem was that when rebase operations failed, the frontend was catching the detailed error from the API but displaying a generic "Failed to rebase branch" message instead.

**What was wrong:**
- Backend correctly returns `success: false` with detailed error messages
- Frontend API handler correctly throws `ApiError` with the detailed message
- But the rebase error handlers were ignoring the actual error message

**What I fixed:**
- Updated both rebase error handlers in [`CurrentAttempt.tsx`](file:///private/var/folders/kr/jdxkcn7129j376nrg0stj9zm0000gn/T/vibe-kanban/vk-c0ff-error-mess/frontend/src/components/tasks/Toolbar/CurrentAttempt.tsx#L350) to use `err.message` instead of generic text
- Now displays detailed error messages like "Git service error: Merge conflicts: Rebase failed due to conflicts. Please resolve conflicts manually."

The fix ensures users see the actual error details instead of unhelpful generic messages when operations fail.
…ssages

- Frontend: Use actual error messages from API instead of generic "Failed to rebase branch"
- Backend: Return proper HTTP error status codes (500) instead of 200 for rebase failures
- Backend: Include detailed error messages in structured JSON error responses
- Now users see specific error details like "Merge conflicts: Rebase failed due to conflicts"

Amp-Thread: https://ampcode.com/threads/T-582a32d9-8dd9-4d43-a3b7-90e084d8c173
Co-authored-by: Amp <[email protected]>
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.

1 participant