Skip to content

I've got a really tough problem right now! I'm looking for someone who can help me solve it, and I'm ready to pay a generous reward! If you can handle it, please follow me and reach out! #2468

@20261688fafa-commits

Description

@20261688fafa-commits

Use a concise sentence-case title that describes the broken behavior. Do not add Bug or bracket prefixes to the title.

Summary

What failed, in one or two sentences (user-visible symptom or test failure).

Problem

What happened vs what you expected, impact, and steps to reproduce (ordered, minimal). Include version / platform (app version, OS, desktop vs dev) if known.

Solution (optional)

Suspected cause, workaround, or proposed fix. Skip if unknown.

Acceptance criteria

  • Repro gone — Bug no longer reproduces on the stated environment (or root cause documented if intentional).
  • Regression safety — Unit, integration, or E2E coverage added or updated if this should not come back.
  • Diff coverage ≥ 80% — the fix PR meets the changed-lines coverage gate (Vitest + cargo-llvm-cov, enforced by .github/workflows/coverage.yml).
  • — Other verify-before-close items.

Related

Links to issues, PRs, logs, or prior discussion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions