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

Uncaught Error: EPERM: operation not permitted, lstat '/\CNFCNPL40E\ISHomeDir02\' #18807

Closed
JackHartCNB opened this issue Feb 6, 2019 · 5 comments

Comments

@JackHartCNB
Copy link

[Enter steps to reproduce:]

  1. ...
  2. ...

Atom: 1.34.0 x64
Electron: 2.0.16
OS: Microsoft Windows 10 Enterprise
Thrown From: Atom Core

Stack Trace

Uncaught Error: EPERM: operation not permitted, lstat '\CNFCNPL40E\ISHomeDir02'

At fs.js:1621

Error: EPERM: operation not permitted, lstat '\\CNFCNPL40E\ISHomeDir02\'
    at Proxy.realpathSync (fs.js:1621:13)
    at Proxy.fs.realpathSync (ELECTRON_ASAR.js:336:29)
    at atom.project.getPaths.map.e (~/AppData/Local/atom/app-1.34.0/resources/app/static/<embedded>:11:788946)
    at Array.map (<anonymous>)
    at Object.startTask (~/AppData/Local/atom/app-1.34.0/resources/app/static/<embedded>:11:788937)
    at Object.startLoadPathsTask (~/AppData/Local/atom/app-1.34.0/resources/app/static/<embedded>:11:186974)
    at get_process.nextTick (~/AppData/Local/atom/app-1.34.0/resources/app/static/<embedded>:11:185036)
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)

Commands

Non-Core Packages


@rsese
Copy link
Contributor

rsese commented Feb 6, 2019

Thanks for contributing!

We noticed that this looks like a duplicate of atom/fuzzy-finder#289 so you can subscribe there for updates if you'd like.


Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.

For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.

@rsese rsese closed this as completed Feb 6, 2019
@JackHartCNB
Copy link
Author

JackHartCNB commented Feb 6, 2019 via email

@rsese
Copy link
Contributor

rsese commented Feb 7, 2019

Hey @JackHartCNB - it's a known issue without specific steps to reproduce so if you have very specific repro steps, let us know in atom/fuzzy-finder#289. But otherwise yes, if you subscribe to it, you'll get notified on any activity on the issue. We can't promise a timeline for any issue to get resolved, but we definitely need repro steps in general for bug reports.

@JackHartCNB
Copy link
Author

JackHartCNB commented Feb 7, 2019 via email

@lock
Copy link

lock bot commented Aug 6, 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 Aug 6, 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

2 participants