{
 "usecase": "issue-triage",
 "date": "2026-10-14",
 "raw_outputs": {
  "c01": "{\"type\": \"bug\", \"missing\": [\"error_output\"], \"reply\": \"Thanks for the report, and for confirming that 3.1.4 works. To investigate the crash, we need the exact error output you get when running `plumb serve --config prod.toml` on 3.2.0. Please paste the full error message, any error code, and the log lines printed just before the crash, as plain text rather than a screenshot. With that, the maintainers can compare what changed between 3.1.4 and 3.2.0 and triage the issue.\"}",
  "c02": "{\"type\": \"bug\", \"missing\": [], \"reply\": \"Thanks for the detailed report. It includes the version (3.2.0), your OS and Python version, the exact steps and command, the expected and actual results, and the log output. That is everything the maintainers need to reproduce the problem, so it will be triaged. We will follow up here once it has been reviewed. The log line about the skipped table name should help the team find the cause.\"}",
  "c03": "{\"type\": \"bug\", \"missing\": [\"steps_to_reproduce\", \"version\", \"expected_behaviour\", \"environment\"], \"reply\": \"Thanks for the report, and sorry the broken export is blocking you. To help us reproduce it, please reply with the following. Steps to reproduce: the exact actions you take, including which export and format you use. Version: the specific version number you are running, not just a word like latest. Expected behaviour: what you expected to happen instead. Environment: your operating system, plus your runtime or browser. Once we have these, we will look into it as soon as we can.\"}",
  "c04": "{\"type\": \"bug\", \"missing\": [], \"reply\": \"Thanks for the report. It includes the version (1.4), a snippet that reproduces the problem, the value you got (3.99) and the value you expected (4.00 under round-half-up, as the docs describe), so it has what the maintainers need. It will now be triaged, and the maintainers will look at why tally.vat(19.99, rate=0.2) returns 3.99 rather than the documented result. Thanks again for taking the time to write this up.\"}",
  "c05": "{\"type\": \"bug\", \"missing\": [\"version\"], \"reply\": \"Thanks for the report, and for the details on file sizes and the Windows 11 setup. Could you tell us the exact version number of fennel you are running, such as 2.4.1? 'Latest release' does not tell us which build hangs, so we need the specific version to check whether this is a regression. Once we have it, we will try to reproduce the hang with a file of the same size.\"}",
  "c06": "{\"type\": \"bug\", \"missing\": [\"version\", \"expected_behaviour\"], \"reply\": \"Thank you for the report, and for including the macOS and Python details and the full traceback. To help the maintainers reproduce and fix this, we need two more things. First, the version of Fennel you are running, such as 2.4.1 or 0.9. Second, what you expected `fennel migrate up` to do on a fresh database instead of raising KeyError: 'head'. Once we have those, the issue will be triaged.\"}",
  "c07": "{\"type\": \"bug\", \"missing\": [], \"reply\": \"Thanks for the report. You describe a regression: notifyr send --quiet batch.json printed nothing in 2.0.3 but prints a progress bar in 2.1.0. The report also gives the expected behaviour and your environment (Node 20.11 on Debian 12). That is everything the maintainers need to reproduce and investigate the problem, so the issue will now go through triage. No further details are needed from you at this stage.\"}",
  "c08": "{\"type\": \"bug\", \"missing\": [\"version\"], \"reply\": \"Thanks for the report, and for the clear steps and the iPhone 15 and Safari details. Could you tell us which version of Kestrel you were running when the Settings page overflowed? We need Kestrel's own version number, such as 2.4.1, not your iOS or device version. That lets us check whether the problem is already fixed in a release. Once we have it, we will look into the layout problem.\"}",
  "c09": "{\"type\": \"bug\", \"missing\": [], \"reply\": \"Thanks for the report. It includes the version you upgraded to (4.0.0), your operating system (Arch Linux), the steps that led to the problem (upgrading from 3.x to 4.0.0 with settings in ~/.config/plumb) and what you expected to happen. That gives the maintainers what they need, so the issue will be triaged. Losing settings during an upgrade is a serious problem, and the report is clear enough to act on.\"}",
  "c10": "{\"type\": \"bug\", \"missing\": [\"steps_to_reproduce\", \"version\", \"environment\"], \"reply\": \"Thanks for the report, and sorry the app is crashing when you open a report. To help us reproduce it, please share the steps to reproduce, meaning the exact actions you take before the crash, including which report you open. Please also tell us the version you are running, and your environment, including your operating system, runtime or browser. With those details we can look into this properly. Thanks again for raising it.\"}",
  "c11": "{\"type\": \"bug\", \"missing\": [\"error_output\"], \"reply\": \"Thanks for the report! You mention the container being OOM-killed after about nine days, but the report does not include the exact error output. Please paste the exact error output or log excerpt from around the time of the kill, including any messages printed by fennel serve and any relevant entries from the Docker container logs. With that, the maintainers can see what happened at the point of failure, and the issue can be triaged.\"}",
  "c12": "{\"type\": \"bug\", \"missing\": [\"environment\"], \"reply\": \"Thanks for the report! A --retries flag that is ignored sounds like a real problem, and we want to get it fixed. To reproduce it on our side, we need to know your environment. Please tell us which operating system you are running notifyr on, and which runtime or browser it runs under, for example Node.js or Python. Once we have that, the maintainers will triage the issue.\"}",
  "c13": "{\"type\": \"bug\", \"missing\": [\"error_output\"], \"reply\": \"Thanks for the report! The steps, Kestrel version, browser and OS, and expected result are all clear, so we can work from them. The one thing missing is the exact error output. Could you copy the exact text of the error banner shown after you click Save? If the browser console (F12, then the Console tab) shows any red messages at that moment, please paste those too. The exact wording helps us find the cause quickly. Thank you for taking the time to write this up.\"}",
  "c14": "{\"type\": \"bug\", \"missing\": [\"steps_to_reproduce\", \"expected_behaviour\"], \"reply\": \"Thanks for the report! We are sorry the login does not work for you on Android with version 2.2. To help us investigate, please share the steps to reproduce the problem, meaning the exact actions you took before it failed. Please also tell us what you expected to happen instead.\\n\\n\u00a1Gracias por el reporte! Lamentamos que el login no funcione en la versi\u00f3n 2.2 en Android. Para poder reproducir el problema, ind\u00edcanos los pasos exactos que seguiste antes de que fallara. Tambi\u00e9n nos ayudar\u00eda saber qu\u00e9 esperabas que ocurriera en su lugar.\"}",
  "c15": "{\"type\": \"bug\", \"missing\": [], \"reply\": \"Thanks for the detailed report. It includes the exact commands, your version (3.2.0), your operating system (Ubuntu 24.04), and the row count you expected (1000). That gives the maintainers what they need to reproduce the mismatch in plumb stats, so the report will be triaged. Your request to have stats print the on-disk size in bytes is also noted and will be considered separately. No further information is needed at this stage.\"}",
  "c16": "{\"type\": \"bug\", \"missing\": [\"expected_behaviour\"], \"reply\": \"Thanks for the report. The Windows 11 and Python 3.11.9 details, the pip command and the error output are all helpful. One thing is still missing: what did you expect to happen instead? For example, did you expect tally-core 1.0.0 to install cleanly on your machine, without the Visual C++ build error? Once we have that, the maintainers can take the next step on the build failure.\"}",
  "c17": "{\"type\": \"feature\", \"missing\": [], \"reply\": \"Thanks for the suggestion! A dark theme would help people who run Kestrel in dim spaces, such as a wall screen in an ops room at night, so we will consider adding one. We have noted your use case: a bright white background is uncomfortable to look at in low light. Maintainers will review this request alongside other feature ideas and follow up here if it moves forward. Thanks again for explaining how you use Kestrel.\"}",
  "c18": "{\"type\": \"feature\", \"missing\": [], \"reply\": \"Thanks for the suggestion! Support for Parquet export will be considered by the maintainers. So we can weigh it properly, could you tell us the use case? For example, which tools or pipelines will read the exported files, how often you would export, and why CSV falls short for your work. Your answer will help us judge how much this matters to users. Thanks again for helping improve plumb.\"}",
  "c19": "{\"type\": \"feature\", \"missing\": [], \"reply\": \"Thanks for offering to contribute a Danish (da-DK) translation of the CLI messages. This will be considered as a feature request. Translations need ongoing upkeep as messages change, so we want to understand demand first. Could you tell us the use case? For example, who would use the CLI in Danish, and in what setting? Knowing how people would use it helps us judge whether it is worth adding. Thanks again for wanting to help the project.\"}",
  "c20": "{\"type\": \"feature\", \"missing\": [], \"reply\": \"Thanks for the suggestion! A keyboard shortcut to collapse and expand the sidebar would help anyone who switches between dashboards often, and the maintainers will consider it. Requests like this are weighed against the rest of the backlog, so we cannot promise a timeline yet. Thanks also for explaining how reaching for the mouse disrupts your workflow. That context helps us judge how much this matters to people who use the project every day.\"}",
  "c21": "{\"type\": \"feature\", \"missing\": [], \"reply\": \"Thanks for the suggestion. Making fennel.toml optional, so that fennel starts with its default settings when the file is absent, will be considered by the maintainers. To help us weigh it, could you describe your use case? For example, what you are running fennel for, and whether you would rely on the defaults in production or only while testing? That context would show how much the change matters to you.\"}",
  "c22": "{\"type\": \"feature\", \"missing\": [], \"reply\": \"Thanks for the suggestion, and for explaining how you run notifyr from a nightly cron job. Your use case is clear: you want a completion callback so the next job can start without polling the log. The maintainers will consider a --on-complete option that POSTs a summary JSON to a URL when a batch finishes. Thanks again for writing this up in such detail. The concrete use case will help them weigh it against other requests.\"}",
  "c23": "{\"type\": \"question\", \"missing\": [], \"reply\": \"Thanks for reaching out about the proxy setup. I can't confirm the exact proxy setting for plumb here, so I'd rather not guess at one. The project's discussions board is the best place to ask, since maintainers and other users can give you specifics. When you post there, include your operating system, your plumb version, and the proxy details your office network requires, so you get an answer that fits your setup. Thanks for asking!\"}",
  "c24": "{\"type\": \"question\", \"missing\": [], \"reply\": \"Thanks for the question. I can't confirm from this issue whether tally-core is tested on Python 3.13, so please take it to the project's discussions board, where other users may already have shared their experience. Before you upgrade, run your own test suite against Python 3.13 in a staging environment. That is the most reliable way to find out whether tally-core works correctly in your setup.\"}",
  "c25": "{\"type\": \"question\", \"missing\": [], \"reply\": \"Thanks for the question, and for pointing out the docs gap on the trade-offs between --mode fast and --mode safe. For an accurate answer, please ask on the project's discussions board, where maintainers and experienced users can explain what each mode does and when to choose it. Include your use case so the answer fits your situation. Feel free to link this issue there so others with the same question can find it.\"}",
  "c26": "{\"type\": \"question\", \"missing\": [], \"reply\": \"Thanks for your question about running Kestrel without Docker. Questions like this are best answered on the project's discussions board, where maintainers and other users can help. Please post there and include the operating system and runtime available on your hosting, along with any restrictions it places on what you can install. That gives people the detail they need to suggest a setup that fits your environment. Thanks again for reaching out.\"}",
  "c27": "{\"type\": \"question\", \"missing\": [], \"reply\": \"Thanks for the question, and for noting where the logs live on Linux. I don't know the Windows location for certain, so I won't guess a path. Please take this question to the project's discussions board, where maintainers and other users can point you to the right place. It would help to include your notifyr-cli version and whether you installed it with a package manager or downloaded it directly. Those details will make it easier for someone to answer.\"}",
  "c28": "{\"type\": \"unclear\", \"missing\": [], \"reply\": \"Thanks for opening an issue on Kestrel! The body is empty, so we cannot tell yet what you need. Could you tell us what you are trying to do with Kestrel and what went wrong? A short description is enough. If something failed, please include the error message you saw and the steps you took before it happened. Once we know more, a maintainer will take a look and follow up.\"}",
  "c29": "{\"type\": \"unclear\", \"missing\": [], \"reply\": \"Thanks for opening an issue on plumb. Your message says only asdf test test, so we cannot tell what you are trying to do or what went wrong. Could you tell us what you were trying to do with plumb and what went wrong when you tried it? If an error appeared, please paste the full message. A sentence or two is enough to get us started, and a maintainer will take a look once we hear from you.\"}",
  "c30": "{\"type\": \"unclear\", \"missing\": [], \"reply\": \"Thanks for getting in touch! This issue doesn't seem to be about the Fennel project, so we're not sure what you need. Could you tell us what you are trying to do with Fennel, and what went wrong, if anything? If you have a question about the project, please ask it on the discussions board. If you are looking for laptop advice, a general tech forum or community will serve you better than this tracker.\"}"
 }
}