kiteco
Atom closes when accessing docs
Required Information To help us triage your issue effectively, please make sure you've completed these steps before opening this issue. Issues with not enough information may be deprioritized or ignored.
- [x] Read our guide on how to report an issue.
- [ ] Include your Kite application logs, taken while you are experiencing your issue.
- [ ] If reporting a performance problem, include your resource usage logs, taken while you are experiencing your issue.
- [x] If reporting an issue with Kite's editor plugin, include which editor you are using and the version, and any accompanying logs from your editor's console.
Atom closes when accessing docs or accessing kite docs using the kite icon on atom. Using Atom version 1.56. This made me close unsaved work, which is really annoying. Have a recording of the issue with opening the docs.
https://user-images.githubusercontent.com/57991110/115815250-eab5d700-a3f6-11eb-8623-f155df3a5dd2.mp4
Hi @NilsPotet ,
Thanks for letting us know about this issue, it's definitely annoying! It seems like this is due to one of the changes of Atom 1.56.0.
As a workaround while we continue to investigate this issue, you can download version 1.55.0 of Atom here. Make sure you turn off auto-updates if you do so to prevent it from downloading 1.56.0 again.
Hello!
I am experiencing this issue too. I am also using Atom version 1.56.0 with Kite Co-pilot 1.2021.310.0 and Kite plugin 0.204.0 on Windows 10. If I may add some information, from what I can tell and have experienced, it seems that any interaction with the plugin makes the window disappear. The Atom processes still run but the window is not recoverable - restarting atom fixes this.
Here is the link to the log files.
I hope that this can help. Thanks for the workaround!
- Theo
To add to Theo's comment, when running atom in multiple windows, only the active window is closed, and other windows are unaffected. Also, the "reopen project" button on Atom doesn't work on whatever project was just closed, but you can add project folders, including the one that was just closed. Presumably, Atom thinks the project is still open and so tries to send you to the now-nonexistent window of that project rather than opening it. Here are my logs. I'm running macOS Big Sur version 11.1.
Just wanted to add I'm having the same issue with 1.58. Is there a workaround other than installing an earlier version of atom
Issue persists with atom version 1.59.0 x64. It's been a long time since this has been reported. Is this being actively investigated?
To add to Theo's comment, when running atom in multiple windows, only the active window is closed, and other windows are unaffected. Also, the "reopen project" button on Atom doesn't work on whatever project was just closed, but you can add project folders, including the one that was just closed. Presumably, Atom thinks the project is still open and so tries to send you to the now-nonexistent window of that project rather than opening it. Here are my logs. I'm running macOS Big Sur version 11.1.
I had made some changes to a file that I hadn't saved, yet. Just reopening Atom and readding the project folder and reopening the file didn't bring those changes back back. Your hint helped a lot! I closed the reopended Atom window, opened the Task manager, scrolled down do find some active Atom processes, randomly closed the first one to let Atom "properly" crash. All Atom processes stopped. Then I reopened Atom, et violà, I got my changes back! Atom version 1.58.0 on a windows 10 computer
