Files
willtools-demo/.github/ISSUE_TEMPLATE/bug_report.md
T
will 52d94303bc
ci / test (push) Has been cancelled
WillTools: precast shop-ticket QC and panel handling tools
Public demo snapshot of an in-house pyRevit extension for precast concrete
shop-ticket QC (37 checks / 46 checklist rows) and a standalone panel
handling solver (PCI Chapter 8).

- No client, job, plant or product data: knowledge layers ship as
  structural templates only.
- Ticket QC's model-read escalation targets a LAN model server endpoint
  (configurable), not a cloud provider.
- Built from the private development repo via tools/make_dist.py.
2026-09-03 16:33:47 -05:00

77 lines
2.0 KiB
Markdown

---
name: Bug report
about: Something ran and gave a wrong or crashing answer
title: ''
labels: bug
assignees: ''
---
<!--
Before filing: is this a WRONG answer, or a REFUSAL to answer?
WillTools refuses rather than guesses, by design -- a "NOT JUDGED" result
with a stated reason is often the tool working CORRECTLY (an unmapped
parameter, a missing knowledge layer, a check that legitimately has nothing
to say about this piece). If the tool told you clearly why it would not
answer, that is very likely not this template -- it's the tool doing what it
is supposed to. File that as a "refused, and I think it shouldn't have"
report instead (see the Question template), because that is knowledge-layer
work, not a code fix.
This template is for: it crashed, it gave two different answers to the same
input, or it silently produced a wrong number with no stated reason.
-->
## What happened
<!-- Paste the exact error, verbatim, in a code block. Do not summarize it or
retype it from memory -- the exact text (including any traceback) is what
gets this fixed fast. -->
```
paste it here
```
## What you expected instead
## Steps to reproduce
1.
2.
3.
## Environment
Run this and paste its ENTIRE output below, unedited -- it is the single
most diagnostic thing you can attach. It is plain text with no color codes,
so it pastes cleanly into this box:
```
python tools/setup_machine.py --check
```
<details>
<summary>setup_machine.py --check output</summary>
```
paste it here
```
</details>
- Windows version:
- `python --version`:
- Revit version (if this involves a ribbon button):
- pyRevit version (if this involves a ribbon button):
## Which button or command
<!-- e.g. "Ticket QC" on the ribbon, or `python -m panellift ...` -->
## No client or job data, please
Screenshots, pasted output, and job files should carry no real client name,
job name, or job number. If a screenshot or a job file shows one, use a
placeholder (`sample_client`, `sample_job`) or ask the owner how to share it
privately instead of pasting it here.