Uncaught Error: Graph Container Element Not Found
Hey Community, i have a Problem with my Plugin. Im developing a Plugin for creating an ajax form dialog, thats extending the normal dialog. In this Plugin.
Uncaught Error: Graph Container Element Not Found Dead
# Userink, v0. 1 (active)julia -client, v0. 10 (active)language -julia, v0. 0 (active)latex -completions, v0. 2 (active)project -plus, v0. 0 (active)tool -bar, v1.
1 (active)uber -juno, v0. 1 (active)atom -dark -syntax, v0. 0 (inactive)atom -dark -ui, v0. 0 (inactive)atom -light -syntax, v0.
0 (inactive)atom -light -ui, v0. 0 (inactive)base16 -tomorrow -dark -theme, v1. 0 (inactive)base16 -tomorrow -light -theme, v1. 0 (inactive)one -dark -ui, v1.
Uncaught Type Error Javascript
2 (inactive)one -light -ui, v1. 2 (active)one -dark -syntax, v1. 0 (inactive)one -light -syntax, v1. 0 (active)solarized -dark -syntax, v1. 5 (inactive)solarized -light -syntax, v1. 5 (inactive)about, v1. 0 (active)archive -view, v0.
0 (active)autocomplete -atom -api, v0. 0 (active)autocomplete -css, v0.
1 (active)autocomplete -html, v0. 2 (active)autocomplete -plus, v2. 4 (active)autocomplete -snippets, v1. 0 (active)autoflow, v0. 0 (inactive)autosave, v0.
1 (active)background -tips, v0. 1 (active)bookmarks, v0.
0 (active)bracket -matcher, v0. 2 (active)command -palette, v0. 0 (active)deprecation -cop, v0. 1 (active)dev -live -reload, v0. 0 (active)encoding -selector, v0.
0 (active)exception -reporting, v0. 0 (active)find - and -replace, v0. 2 (active)fuzzy -finder, v1. 0 (active)git -diff, v1. 0 (active)go -to -line, v0. 0 (active)grammar -selector, v0.
2 (active)image -view, v0. 0 (active)incompatible -packages, v0. 1 (active)keybinding -resolver, v0. 0 (active)line -ending -selector, v0. 0 (active)link, v0.
2 (inactive)markdown -preview, v0. 8 (active)metrics, v1.
2 (active)notifications, v0. 1 (active)open - on -github, v1. 1 (inactive)package -generator, v1. 1 (inactive)settings -view, v0. 1 (active)snippets, v1. 4 (active)spell -check, v0.
4 (active)status -bar, v1. 1 (active)styleguide, v0.
2 (active)symbols -view, v0. 1 (inactive)tabs, v0. 0 (active)timecop, v0. 2 (active)tree -view, v0.
0 (active)update - package -dependencies, v0. 0 (active)welcome, v0. 1 (active)whitespace, v0. 0 (active)wrap -guide, v0. 2 (active)language -c, v0. 0 (active)language -clojure, v0.
1 (active)language -coffee -script, v0. 0 (active)language -csharp, v0. 0 (active)language -css, v0.
1 (active)language -gfm, v0. 0 (active)language -git, v0. 0 (active)language -go, v0. 0 (active)language -html, v0.
1 (active)language -hyperlink, v0. 1 (active)language -java, v0. 0 (active)language -javascript, v0.
0 (active)language -json, v0. 3 (active)language -less, v0. 6 (active)language -make, v0.
2 (active)language -mustache, v0. 0 (active)language -objective -c, v0. 1 (active)language -perl, v0.
0 (active)language -php, v0. 3 (active)language -property -list, v0. 0 (active)language -python, v0. 1 (active)language -ruby, v0. 2 (active)language -ruby - on -rails, v0. 1 (active)language -sass, v0. 0 (active)language -shellscript, v0.
0 (active)language -source, v0. 0 (active)language -sql, v0. 0 (active)language -text, v0. 1 (active)language -todo, v0. 1 (active)language -toml, v0. 1 (active)language -xml, v0. 12 (active)language -yaml, v0.
1 (active)# Dev No dev packages. I can't reproduce the issue with local projects, but it happens constantly when opening the project takes some time (for example, the project is stored in a VM or on a remote filesystem). Steps to reproduce:. Install. Set up a remotely-stored project.
Close all windows. Open a new window.
Open the project from CMD CTRL P. Toggle the blank tree view twice (close & open) CMD.
Click in the empty tree view areaInterestingly enough, clicking on the tree view header (the title Projects) fixes the issue. I started getting this today. It was triggered by me being curious about the tabs at the top of the tree view, and I right clicked on the tab and clicked 'Split up':I now can't get the tree view to display anything, and receive the error described in this report.Edit: managed to fix this by opening atom from a different project folder, removing the project folder from the tree view, adding the project folder I was having trouble with, and accepting the message that popped up regarding discarding the old project folder state. In the interest of trying to get people help with the problems they're running into, I'm going to lock the conversation on this issue and leave some instructions for people to follow:. If you are having a problem with the or packages, you'll need to file issues on those packages' repos.
The has information on. If you are wanting to report an issue that you are experiencing with Atom that you can reproduce when running in, please open a new issue and fill in the required template. This way we will have the information we need to help fix things.Thanks everyone for your passion for and interest in Atom.