-
Notifications
You must be signed in to change notification settings - Fork 163
Submission creates lots of blank pages #764
Comments
|
Same here, latest Atom, latest plugins and OSX |
same here |
Can confirm, getting 20-40 windows per commit now. |
|
Sorry about this guys. I haven't had the time or energy to address issues lately. @VAdamec in the issue you opened in the atom repo, you mentioned you've seen this happen with another package. Do you know which one? I'm looking into this now. Perhaps as a stop-gap, you can disable the setting for git-plus to split into a new pane and see if that helps. Can y'all provide some more information about the context where you see this happen? How many projects do you have in the window, list of installed packages which may have an impact, etc.? Something else that could be very helpful is if you could disable all other community packages but git-plus and see if the behavior still happens. That might be an inconvenience but it could help narrow down the problem area quickly. |
It seems to be reflective of the number of 'changed' files almost as in git-plus is trying to open a new window for each file thats been altered in the commit, instead of just 1 window per commit. |
That's very bizarre. Nothing about the code to open a pane for commits has changed in 2 years. @zdxn have you tried to reproduce this after disabling your other packages? |
Only packages i have are language packs, git-plus is the only external plugin i have that would affect this. |
I'll say this behaviour has been happening for almost 2 months. |
|
@akonwi it doesn't matter
|
For me it's creating hundreds of panes, when only one file has changed, and they even reappear after holding Ctrl+W for a while to close them all (and Atom itself). I had to disable the package to prevent endless panes opening. Atom 1.31.2 on Arch AMD64. |
@zdxn that's very interesting and good to know. This is so odd. I use atom beta and nightly to stay ahead of updates and hopefully catch issues like this in advance but this one has eluded me. @RenaKunisaki did you see my suggestion earlier?
Can you try that and let me know if that remedies the problem for now? |
|
|
|
So this is starting to seem more like an issue with atom. I'll inspect a bit and see if i can debug where the bug is in atom. @linjialiang Those templates are for atom notifications and aren't being generated directly by git-plus. I don't think that's an actual problem though. they shouldn't affect your user experience and I see them with any notification that gets created |
That does fix it! Also, the problem doesn't happen on my laptop (Arch Intel X64), but it does take ~30 seconds to open the pane there. |
Ok, I'm glad that works for now. Interesting though that it takes significantly longer to open the pane on another machine though. |
Now that I think about it, the delay might be caused by wifi, since I'm using sshfs there. |
yea that's plausible |
The text was updated successfully, but these errors were encountered: