Skip to content

Commit 1b154a5

Browse files
Create issue templates
1 parent bd7090b commit 1b154a5

4 files changed

+106
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
name: "✍️ Other Issue"
3+
about: For issues not covered by the other templates.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
Please proviede a concise description of your issue. Proviede as much information as possible, including, if required, your system hardware, software version... and any other info that could be usefull to find a solution.
11+
12+
Please, If you want to report a bug, or any error you found while running the code, use the "Bug report and Issues" Template.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
name: "\U0001F41B Bug report and Issues"
3+
about: Submit a bug report to help us improve GoLLIE
4+
title: "[BUG] Bug or issue report"
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the task**
11+
1. Model: Which GoLLIE model are you attemping to run?
12+
2. Task: Which task are you attemping to run (training, evaluation, generate the dataset,...)?
13+
14+
**Describe the bug**
15+
A clear and concise description of what the bug is. You can add the error traceback or screenshots here.
16+
17+
**To Reproduce**
18+
Steps to reproduce the behavior:
19+
1. Load model X
20+
```Python
21+
model, tokenizer = load_model(
22+
inference=True,
23+
model_weights_name_or_path="HiTZ/GoLLIE-7B",
24+
quantization=None,
25+
use_lora=False,
26+
force_auto_device_map=True,
27+
use_flash_attention=True,
28+
torch_dtype="bfloat16"
29+
)
30+
```
31+
2. Run X function
32+
```Python
33+
model_ouput = model.generate(
34+
**model_input.to(model.device),
35+
max_new_tokens=128,
36+
do_sample=False,
37+
min_new_tokens=0,
38+
num_beams=1,
39+
num_return_sequences=1,
40+
)
41+
```
42+
3. Any other step required to reproduce the behaviour
43+
44+
**Expected behavior**
45+
A clear and concise description of what you expected to happen.
46+
47+
**System Info**
48+
1. GPU: (i.e Nvidia A100)
49+
2. Pytorch version:
50+
3. Transformers version:
51+
4. Model configuration: Are you using 4 / 8 bits quantization? Are you using mGPU? etc..
52+
5. Any other relevant information:
53+
54+
55+
**Additional context**
56+
Add any other context about the problem here.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: "\U0001F4D1 New Task/Dataset Proposals"
3+
about: Submit a proposal/request for a new task support in GoLLIE
4+
title: "[TASK] I want task X to be supported by GoLLIE"
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the task you'd like to implement**
11+
A clear and concise description of the task/dataset. If you want to propose a new dataset, please explain if the task is already supported by GoLLIE (i.e Named Entity Recognition, Event Extraction, Relation Extraction...). If it is not, explain how you would implement it.
12+
13+
**Data**
14+
Is the data for the task publicly available? If it is, provide a link to it. If it is not, explain how the data can be obtained.
15+
16+
**Guidelines**
17+
Are guidelines available? If guidelines are available, provide a link to them. If they are not, describe how you would generate them.
18+
19+
**Your contribution**
20+
Is there any way that you could help, e.g. by submitting a PR?
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
name: "\U0001F680 Feature request"
3+
about: Submit a proposal/request for a new transformers feature
4+
title: "[FEATURE] I want feature X supported by GoLLIE"
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Feature request**
11+
A clear and concise description of the feature proposal.
12+
13+
**Motivation**
14+
Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too.
15+
16+
17+
**Your contribution**
18+
Is there any way that you could help, e.g. by submitting a PR?

0 commit comments

Comments
 (0)