Commit f638b3c
1 parent 725f360 commit f638b3c
1 file changed
+1
-1
lines changedLines changed: 1 addition & 1 deletion
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
133 | 133 |
| |
134 | 134 |
| |
135 | 135 |
| |
136 |
| - | |
| 136 | + | |
137 | 137 |
| |
138 | 138 |
| |
139 | 139 |
| |
|
1 parent 725f360 commit f638b3c
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
133 | 133 |
| |
134 | 134 |
| |
135 | 135 |
| |
136 |
| - | |
| 136 | + | |
137 | 137 |
| |
138 | 138 |
| |
139 | 139 |
| |
|
4 commit comments
ghtmtt commentedon Feb 24, 2018
Hi @alexbruy I think you are taking care of https://issues.qgis.org/issues/18198. I re-build QGIS and I still have a stack trace:
I don't know if other commits are coming and/or comments like this help you. In case just ignore them ;)
Thanks for all this work!
alexbruy commentedon Feb 24, 2018
@ghtmtt thanks for the information. I can't reproduce it (as well as #18198). Looking now.
alexbruy commentedon Feb 24, 2018
@ghtmtt can you try with f3af22e?
ghtmtt commentedon Feb 24, 2018
I get this stack trace: