## Error Details

[hyper-charlie]

Description

Error Details

Error Message: Test bug from Devin - testing automated issue creation and Devin session trigger pipeline

Stack Trace:

Error: Test error for pipeline verification
    at TestComponent (test.tsx:42)
    at renderWithHooks (react-dom.js:1234)

Device Information

Platform: linux
Architecture: x86_64
OS Version: 5.10.223
App Version: 0.0.0-test

---

This issue was submitted from the Hyprnote desktop app.

[hyper-charlie]

Log Analysis

Summary

2026-02-11T17:25:00Z [ERROR] Test log entry - pipeline verification
2026-02-11T17:25:01Z [WARN] This is a test warning for verifying the feedback pipeline

Raw Logs (last 10KB)

2026-02-11T17:25:00Z [ERROR] Test log entry - pipeline verification
2026-02-11T17:25:01Z [WARN] This is a test warning for verifying the feedback pipeline

[devin-ai-integration]

Codebase Context

This issue was created via the feedback submission pipeline — specifically the POST /feedback/submit endpoint backed by the submit_bug_report function. Here's how the pipeline works and the relevant files:

Issue Creation Flow

1. Desktop app submits feedback via the support chat MCP tools or the REST feedback endpoint.
2. crates/api-support/src/routes/feedback.rs — FeedbackRequest is validated (description >= 10 chars), then routed by FeedbackType::Bug or Feature.
3. crates/api-support/src/github.rs — submit_bug_report() renders the issue body using the Jinja template, calls create_issue() via the GitHub API (octocrab), and optionally attaches AI-analyzed logs via attach_log_analysis().
4. Templates: crates/api-support/assets/bug_report.md.jinja + _device_info.md.jinja produce the issue body format seen here.
5. Title generation (make_title at github.rs:112): Takes the first line of the description (up to 100 chars) as the title, which is why this issue's title is "## Error Details" — it used the first line of the markdown description verbatim.

MCP Tool Path (alternative)

Issues can also be created via the SupportMcpServer (crates/api-support/src/mcp/server.rs) → create_issue tool (crates/api-support/src/mcp/tools/create_issue.rs), which calls github::create_issue() directly with a title/body/labels. The desktop UI for this is at apps/desktop/src/components/chat/message/tool/create-issue.tsx.

Assessment

This is a test issue for verifying the automated issue creation and Devin session trigger pipeline — not a real bug. The error message and stack trace are synthetic test data (TestComponent, test.tsx:42). The device info (linux, x86_64, app version 0.0.0-test) confirms this.

Recent Changes in This Area

Recent commits touching the feedback/issue pipeline:

• 435a647 — refactor: API compatibility for apps/api and apps/ai (refactor: API compatibility for apps/api and apps/ai #3851)
• 0dc03cd — feat(desktop): enhance support MCP with Tauri transport, generic tool UI, and context (feat(desktop): enhance support MCP with Tauri transport, generic tool UI, and context #3823)
• d043420 — refactor: replace support MCP tools with create_issue, add_comment, search_issues (refactor: replace support MCP tools with create_issue, add_comment, search_issues #3811)
• ff0eef5 — scaffold crates/api-support to replace apps/api/src/routes/feedback.ts (scaffold crates/api-support to replace apps/api/src/routes/feedback.ts #3745)

No action needed — this issue can be closed as a pipeline verification test.