3 ms·
So much second this. It actually feels like it is getting slower on each upgrade, and more buggy. Am I the only one who finds that the "go to next unresolved" b
by ulrikrasmussen 6y ago
So much second this. It actually feels like it is getting slower on each upgrade, and more buggy. Am I the only one who finds that the "go to next unresolved" button now often goes into an inconsistent non-working state that requires a (slow) refresh? Given that I spend most of my time on GitLab reviewing, this is a real pain point for me.
- phikai 6y ago> Am I the only one who finds that the "go to next unresolved" button now often goes into an inconsistent non-working state that requires a (slow) refresh? I don't think I've seen that reported before and we have been working through some interesting to reproduce issues in recent milestones. Would you mind opening an issue for this? Feel free to tag me (same name).
- acdha 6y agoThere's an open issue for one thing I notice all the time: the next/previous unresolved commands update some internal state but scrolling and other navigation do not. This means that if you use any other navigation mechanism (e.g. search) the next time you hit “go to next unresolved” button it will instead scroll backwards to whatever thread follows the last one you navigated to using the “go to next unresolved” mechanism even if that's scrolling hundreds of lines back.
- shubhamaggarwal 6y agoThere’s already an issue for this: https://gitlab.com/gitlab-org/gitlab/-/issues/281947 https://gitlab.com/gitlab-org/gitlab/-/issues/281947
- ulrikrasmussen 6y agoYes. This is it. Thanks! I wasn't actually sure when it broke, but this issue describes it perfectly.
- adobeslabs 6y agoevery day I wish I could just drop a comment in the webIDE for an MR.. https://gitlab.com/gitlab-org/gitlab-foss/-/issues/48790 https://gitlab.com/gitlab-org/gitlab-foss/-/issues/48790