How to report a duplicate issue that was previously fixed & closed but has resurfaced?
I have found that a previously fixed issue has resurfaced (it no longer gives the intended error message, instead it just segfaults). Should I revive (comment on) the old issue (a year old) or create a new one?
5 Replies
Let's just create a new GH issue, tag it with regression label, and refer to the old issue as well please.
@Joe Loser I don't think I have permissions to add labels to issues, except the ones automatically added with a pre-existing template
I see, can you point me at your new issue and I'll take a look? It's on my list to look into labels/assignees permission issues for contributors.
GitHub
[BUG][Regression] Struct definition with recursive reference (no lo...
Bug description I believe the issue #74 has resurfaced. The following code will segfault: #crash.mojo struct Node: var rec: Node fn init(inout self): pass But I expected the error message: $🍔 m...
I'd also like to add the "mojo-tooling" label to this other issue I opened https://github.com/modularml/mojo/issues/2206