Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught Error: ENOENT, open 'undefined//Users/vijay/dev/ruby/oss/XXX/project.json' #45

Closed
vraravam opened this issue Jan 6, 2015 · 6 comments

Comments

@vraravam
Copy link

vraravam commented Jan 6, 2015

[Enter steps to reproduce below:]

  1. Quit and reopen atom when a project was previously open.
  2. My settings will try to reopen files that were previously open while quitting.
  3. But, there is no file called 'project.json' in that folder.
  4. Also noticed that the preference setting for ''dataSaveFolder' (which was set to '/Users/vijay/.atom/packages/save-session/projects') keeps getting removed from the '.atom/config.cson' file and this could be the reason for the beginning value of 'undefined' when this plugin is trying to figure out the location of the 'project.json' file.
  5. btw, this was working fine in atom v 0.165

Atom Version: 0.166.0
System: Mac OS X 10.10.1
Thrown From: Atom Core

Stack Trace

Uncaught Error: ENOENT, open 'undefined//Users/vijay/dev/ruby/oss/XXX/project.json'

At fs.js:75

Error: ENOENT, open 'undefined//Users/vijay/dev/ruby/oss/XXX/project.json'
  at Error (native)

Commands

  2x -30:00.0 tree-view:reveal-active-file (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-atom-light-syntax.theme-atom-light-ui)

Config

{
  "core": {
    "excludeVcsIgnoredPaths": false,
    "followSymlinks": true,
    "disabledPackages": [
      "language-c",
      "archive-view",
      "welcome",
      "jshint",
      "language-clojure",
      "language-coffee-script",
      "language-csharp",
      "language-gfm",
      "language-go",
      "language-make",
      "language-mustache",
      "language-objective-c",
      "language-perl",
      "language-php",
      "language-python",
      "language-toml",
      "package-generator"
    ],
    "themes": [
      "atom-light-ui",
      "atom-light-syntax"
    ]
  },
  "editor": {
    "fontSize": 13,
    "showIndentGuide": true,
    "preferredLineLength": 120,
    "softWrap": true,
    "softWrapAtPreferredLineLength": true,
    "invisibles": {}
  }
}

Installed Packages

# User
auto-update-packages, v0.2.2
autocomplete-plus-async, v0.22.0
change-case, v0.4.0
coffee-compile, v0.8.4
file-type-icons, v0.5.3
git-tab-status, v1.3.0
highlight-line, v0.9.2
highlight-selected, v0.7.0
language-rspec, v0.2.1
linter, v0.9.1
linter-csslint, v0.0.11
linter-jshint, v0.1.0
linter-less, v0.3.1
linter-rubocop, v0.2.1
linter-scss-lint, v0.0.11
minimap, v3.5.0
minimap-git-diff, v3.1.0
omnisharp-atom, v0.1.6
recent-files, v0.3.0
recent-projects, v0.2.6
ruby-block-converter, v2.5.0
save-session, v0.11.2
syntax-settings, v0.7.1
tab-history, v0.4.0
tree-ignore, v0.1.1

# Dev
No dev packages
@teabyii
Copy link

teabyii commented Jan 7, 2015

I have the same problem.. After installing save-session, when open every file, atom throw ENOENT error.

clhynfield added a commit to clhynfield/save-session that referenced this issue Jan 7, 2015
As of Atom 0.166, `dataSaveFolder` is being removed from save-session's config.
Per @maxbrunsfeld in mpeterson2#43, Atom now requires that
dataSaveFolder be added explicitly to the config schema.

Fixes mpeterson2#43, mpeterson2#45, and
mpeterson2#46.
@mpeterson2
Copy link
Owner

Should be fixed in 0.11.3

@victorhooi
Copy link

I just upgraded to 0.11.3, and it also seemed to blow away my last saved session =(.

@mpeterson2
Copy link
Owner

Unfortunately, there's not much you can do about that. At the moment, if something bad happens like this, and it is unable to save, it will probably break it 😢. #32 suggests creating a snapshot of the state, which would be nice to be able to prevent that.

@victorhooi
Copy link

Hmm, fair enough. Yeah, git snapshots would be neat.

If I'd know the update to 0.11.3 to fix this issue was going to break everything, I would have manually saved all my files first.

I know it's open-source, and I do appreciate your awesome work =), however, next time maybe just mention it on the relevant ticket (e.g. this one, in this case) - if you restart after this, your session won't be saved.

@mpeterson2
Copy link
Owner

Next time I'll be sure to do that. Thanks for the feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants