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 '/\afndc1.afnsolutions.local\users$\' #19433

Closed
negotiate-merge opened this issue Jun 2, 2019 · 3 comments

Comments

@negotiate-merge
Copy link

[Enter steps to reproduce:]

  1. ...
  2. ...

Atom: 1.37.0 x64
Electron: 2.0.18
OS: Microsoft Windows 10 Pro
Thrown From: Atom Core

Stack Trace

Uncaught Error: EPERM: operation not permitted, lstat '\afndc1.afnsolutions.local\users$'

At fs.js:1621

Error: EPERM: operation not permitted, lstat '\\afndc1.afnsolutions.local\users$\'
    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.37.0/resources/app/static/<embedded>:11:791546)
    at Array.map (<anonymous>)
    at Object.startTask (~/AppData/Local/atom/app-1.37.0/resources/app/static/<embedded>:11:791537)
    at Object.startLoadPathsTask (~/AppData/Local/atom/app-1.37.0/resources/app/static/<embedded>:11:188199)
    at get_process.nextTick (~/AppData/Local/atom/app-1.37.0/resources/app/static/<embedded>:11:186163)
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)

Commands

Non-Core Packages

autocomplete-python 1.14.0 
kite 0.164.0 
script 3.18.1 
@rsese
Copy link
Contributor

rsese commented Jun 3, 2019

Thanks for the report! Can you confirm a few things for us?

  • What were you doing at the time of the error?
  • Is the error is reproducible?
  • If reproducible, do you see the error in safe mode (atom --safe)?

@no-response
Copy link

no-response bot commented Jul 1, 2019

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@lock
Copy link

lock bot commented Dec 28, 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 Dec 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants