Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Uncaught Error: ENOENT, open '/Users/jocampbell/Documents/github/sre_dev/repos/snapshotter/spec/lib/hip_chat_helper_spec.rb' #4965

Closed
seajoshc opened this issue Jan 9, 2015 · 4 comments

Comments

@seajoshc
Copy link

seajoshc commented Jan 9, 2015

[Enter steps to reproduce below:]

  1. Changed to a different branch in git repo

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

Stack Trace

Uncaught Error: ENOENT, open '/Users/jocampbell/Documents/github/sre_dev/repos/snapshotter/spec/lib/hip_chat_helper_spec.rb'

At /Applications/Atom.app/Contents/Resources/app/node_modules/pathwatcher/node_modules/q/q.js:126

Error: ENOENT, open '/Users/jocampbell/Documents/github/sre_dev/repos/snapshotter/spec/lib/hip_chat_helper_spec.rb'
  at Error (native)

Commands

Config

{
  "core": {
    "themes": [
      "atom-light-ui",
      "solarized-light-syntax"
    ],
    "audioBeep": false
  },
  "editor": {
    "showIndentGuide": true,
    "fontSize": 18
  }
}

Installed Packages

# User
atom-lint, v0.20.0
autocomplete-plus, v0.21.0
preview-tabs, v0.1.6

# Dev
No dev packages
@benogle
Copy link
Contributor

benogle commented Jan 10, 2015

Did you have this file open when you changed branches? Had you opened this file during the editing session? I assume this file didnt exist in the switched-to branch?

@seajoshc
Copy link
Author

I believe the file was already open and it did exist in the switched-to branch. I don't remember if I was making edits to the file before I decided to switch, I don't think so.

@kevinsawicki
Copy link
Contributor

I believe this is a duplicate of #4850 and will be fixed by #4906

@lock
Copy link

lock bot commented Jan 24, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants