personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: add curl fallback to /debug-report when MCP tools unavailable #103

Merged
lmiranda merged 4 commits from fix/issue-100-debug-report-fallback into development 2026-01-22 20:01:33 +00:00
Conversation 0 Commits 4 Files Changed 2 +88 -3
lmiranda commented 2026-01-22 19:19:55 +00:00
Owner
Copy Link

Summary

  • Adds curl fallback to /debug-report when MCP tools are unavailable
  • Implements secure temp file handling with restrictive permissions
  • Provides three-tier graceful degradation: MCP → curl → local file

Problem

When MCP tools are not available in a session (the very scenario /debug-report is designed to diagnose), the command could not create the diagnostic issue, defeating its purpose.

Solution

Step 6 now offers two options:

  • Option A: Use MCP tools (preferred, when available)
  • Option B: Curl fallback with proper security measures

Security measures implemented:

  • mktemp -m 600 for restrictive file permissions
  • jq --rawfile for safe JSON construction (avoids command substitution vulnerabilities)
  • Proper cleanup of temporary files

Test plan

  • Test /debug-report when MCP tools ARE available (Option A should work)
  • Test /debug-report when MCP tools are NOT available with credentials configured
  • Test /debug-report when MCP tools are NOT available without credentials (should save locally)

Fixes #100

🤖 Generated with Claude Code

## Summary - Adds curl fallback to `/debug-report` when MCP tools are unavailable - Implements secure temp file handling with restrictive permissions - Provides three-tier graceful degradation: MCP → curl → local file ## Problem When MCP tools are not available in a session (the very scenario `/debug-report` is designed to diagnose), the command could not create the diagnostic issue, defeating its purpose. ## Solution Step 6 now offers two options: - **Option A**: Use MCP tools (preferred, when available) - **Option B**: Curl fallback with proper security measures Security measures implemented: - `mktemp -m 600` for restrictive file permissions - `jq --rawfile` for safe JSON construction (avoids command substitution vulnerabilities) - Proper cleanup of temporary files ## Test plan - [ ] Test `/debug-report` when MCP tools ARE available (Option A should work) - [ ] Test `/debug-report` when MCP tools are NOT available with credentials configured - [ ] Test `/debug-report` when MCP tools are NOT available without credentials (should save locally) Fixes #100 --- 🤖 Generated with [Claude Code](https://claude.ai/code)
lmiranda added 3 commits 2026-01-22 19:19:55 +00:00
Merge pull request 'Release: suggest_labels fix' (#96) from development into main 620173eef6
Merge pull request 'development' (#102) from development into main 9b0e9a69b1 
Reviewed-on: #102
fix: add curl fallback to /debug-report when MCP tools unavailable b7829dca05 
When MCP tools are not available in a session (the very scenario
/debug-report is designed to diagnose), the command now falls back to:

1. Check for Gitea credentials at ~/.config/claude/gitea.env
2. Use curl + jq to create the issue via Gitea REST API
3. If no credentials, save report to local file for manual submission

Security measures:
- Uses mktemp -m 600 for restrictive file permissions
- Uses jq --rawfile for safe JSON construction (no command substitution)
- Proper cleanup of temporary files

Fixes #100

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
lmiranda added 1 commit 2026-01-22 19:28:11 +00:00
fix: switch to development branch before adding issue comments 71987ee537 
The MCP server's branch-aware security blocks write operations on
protected branches (main, fix/*, etc). After pushing a feature branch
and creating a PR, we must switch back to development before adding
comments to issues via MCP tools.
lmiranda merged commit 0b23a02886 into development 2026-01-22 20:01:33 +00:00
lmiranda deleted branch fix/issue-100-debug-report-fallback 2026-01-22 20:01:33 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#103
Delete Branch "fix/issue-100-debug-report-fallback"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?