Open theorlovsky opened 4 years ago
Hmm, it works with other MRs, it was just one case so far
Thank you for using the plugin.
I guess this bug happens because Gitlab & IDE have different way to create diff. So with IDE it maybe a actual line change but for Gitlab it's not, so sometime it doesn't work when you try to comment in certain position of code.
I keep this issue open and will find the way to improve it.
So yeah, that isn't the only case anymore, it happens from time to time. Thank you, looking forward to see a patch. The plugin is awesome!
I have 32 drafts and no way to tell which covered the error. As a stop-gap measure, please augment the error message with information about the offending comment. As an alternative, just skip error drafts and submit all others, leaving only those we have to move.
FWIW, this can also happen in the web UI when adding a comment on a line GitLab doesn't consider part of the MR. For example, you can't add comments on lines in renamed (but otherwise unchanged) files. Same for (some) unchanged parts of changed files. I've been having issues with deleted lines as well, IIRC. So, the underlying issues are probably weird choices on the GitLab side of things. All we can hope for here is a UI that handles unexpected errors like that reasonably well.
When I try to add a comment, I get this error:
I've tried both
+
gutter icon and the context menu, no difference. Replying inside an existing thread works fine.Here's a stacktrace as well:
I'm using the EE plugin version on MacOS 10.15.3 and WebStorm 2020.1