Closed tintoy closed 8 years ago
Thanks for the report!
That is really weird; the only place where we call statSync (outside of the tests) we catch all errors and return null
. What's supposed to happen is that you just wouldn't see Config.msi
in the file listing at all.
I'll see what I can do about replicating this locally.
I can't replicate this locally (not a surprise, I'm on OSX). I still also can't figure out why this would happen; the line numbers don't match up with what's in the repo and we catch errors in the one place we call statSync
.
If you're still reliably getting this error, could you post a gist of the contents of the models.js
file listed in the stack trace?
Closing due to lack of a response. If anyone else can replicate this and provide more details, please reopen!
Hi.
Steps to reproduce:
FWIW, that folder is a system folder (Windows Installer file cache for rolling back failed installations). Ordinary users are not meant to have access to this folder. Since I didn't try to navigate to it, this error message should not be displayed.
Atom Version: 1.2.4 System: Microsoft Windows 10 Pro Thrown From: advanced-open-file package, v0.13.0
Stack Trace
Uncaught Error: EPERM: operation not permitted, stat 'C:\Config.Msi'
Commands
Config
Installed Packages