mirror of
https://github.com/urbit/shrub.git
synced 2024-11-24 04:58:08 +03:00
40 lines
1.6 KiB
Markdown
40 lines
1.6 KiB
Markdown
---
|
|
name: Kernel or runtime bug report
|
|
about: Use this template to file a bug for low-level system components, e.g. Hoon,
|
|
Arvo, Zuse, the vanes, Vere, etc.
|
|
title: ''
|
|
labels: bug
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
<!-- A good bug report, description of a crash, etc., should ideally be *reproducible*, with clear steps as to how another developer can replicate and examine your problem. That said, this isn't always possible; some bugs depend on having created a complicated or unusual state, or can otherwise simply be difficult to trigger again (say, you encountered it in the last continuity era).
|
|
|
|
Your issue should thus at a minimum be *informative*. The best advice here is probably "don't write bad issues," where "bad" is a matter of judgment and taste. Issues that the maintainers don't judge to be sufficiently useful or informative may be closed. -->
|
|
|
|
**Describe the bug**
|
|
A clear and concise description of what the bug is.
|
|
|
|
**To Reproduce**
|
|
Steps to reproduce the behaviour:
|
|
1. ...
|
|
2. ...
|
|
3. ...
|
|
|
|
**Expected behaviour**
|
|
A clear and concise description of what you expected to happen.
|
|
|
|
**Screenshots**
|
|
If applicable, add screenshots to help explain your problem.
|
|
|
|
**System (please supply the following information, if relevant):**
|
|
- OS: [e.g. macOS, linux64, FreeBSD]
|
|
- Vere and Urbit OS versions
|
|
- Your ship's `%base` hash (use `+trouble` to check)
|
|
|
|
**Additional context**
|
|
Add any other context about the problem here.
|
|
|
|
**Notify maintainers**
|
|
If you happen to know who the appropriate maintainers are, consider mentioning them with an @ here. You may want to use `git blame` to see who has last touched any relevant code.
|