Atom Editor Opens Strange Window Upon Launch - atom-editor

I installed atom about a week ago and it worked fine until last night when it suddenly ceased working and opens some dev-tool stuff when I launch Atom.
I get this in the console:
index.js:87 Error: EPERM: operation not permitted, open 'C:\Users\Noah Hefner\.atom\compile-cache\less\40e22529c8729b65e1d700a7ae3f73d57ed1288f\imports.json'
at Error (native)
at Object.fs.openSync (fs.js:640:18)
at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:168:20)
at Object.fs.writeFileSync (fs.js:1343:33)
at Proxy.writeFileSync (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\node_modules\fs-plus\lib\fs-plus.js:298:29)
at LessCache.module.exports.LessCache.writeJson (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\node_modules\less-cache\lib\less-cache.js:212:23)
at LessCache.module.exports.LessCache.setImportPaths (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\node_modules\less-cache\lib\less-cache.js:161:18)
at new LessCache (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\node_modules\less-cache\lib\less-cache.js:68:18)
at new LessCompileCache (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\src\less-compile-cache.js:21:26)
at ThemeManager.module.exports.ThemeManager.loadLessStylesheet (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\src\theme-manager.js:283:32)
at ThemeManager.module.exports.ThemeManager.loadStylesheet (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\src\theme-manager.js:271:27)
at ThemeManager.module.exports.ThemeManager.requireStylesheet (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\src\theme-manager.js:191:30)
at ThemeManager.module.exports.ThemeManager.reloadBaseStylesheets (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\src\theme-manager.js:252:25)
at ThemeManager.module.exports.ThemeManager.loadBaseStylesheets (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\src\theme-manager.js:248:25)
at AtomEnvironment.module.exports.AtomEnvironment.initialize (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\src\atom-environment.js:339:25)
at module.exports (C:\Users\Noah Hefner\AppData\Local\atom\app-1.18.0\resources\app\src\initialize-application-window.js:102:29)
at setupWindow (file:///C:/Users/Noah%20Hefner/AppData/Local/atom/app-1.18.0/resources/app/static/index.js:106:12)
at window.onload (file:///C:/Users/Noah%20Hefner/AppData/Local/atom/app-1.18.0/resources/app/static/index.js:67:9)handleSetupError # index.js:87
Here is a picture of the window I get.

This happens when it's installed somewhere that your account lacks read/write permissions. You should find the properties of directory C:\Users\Noah Hefner\.atom and give SYSTEM full permissions.
If that does not work, you could always just reinstall Atom.

Related

Deno 500 error from dev.jspm.io installing dependencies

I'm trying to run my first deno script which is pretty much from the denoDB docs, it just tries to connect to a database with a SQLite3 connector (I'm on a Macbook pro so it should be installed):
import { Database, SQLite3Connector } from 'https://deno.land/x/denodb/mod.ts';
const connector = new SQLite3Connector({
filepath: './db.sqlite',
});
export const db = new Database(connector);
I'm running deno run api/db.ts and I get this error after a few successful downloads:
Download https://deno.land/std#0.149.0/encoding/hex.ts
Download https://deno.land/std#0.149.0/hash/_wasm/lib/deno_hash.generated.mjs
error: Import 'https://dev.jspm.io/inherits#2.0' failed: 500 Internal Server Error
at https://raw.githubusercontent.com/Zhomart/dex/930253915093e1e08d48ec0409b4aee800d8bd0c/lib-dyn/deps.ts:4:26
I've deleted my /Users/<me>/Library/Caches/deno/deps/https and reran the script a few times but I still can't get past this. In my browser trying to follow the URL https://dev.jspm.io/inherits#2.0 does give me an error. What is going on here? There's not much code and I imagine it's not broken for everybody. What do I need to do to get this script to run without issues?
EDIT: it seems to be a library error https://github.com/eveningkid/denodb/issues/348
This is an error caused by a nested depedency, from a project that is not maintained.
See this for more info: [https://jspm.org/jspm-dev-release]
The point is dev.jspm.io is now jspm.dev
A way to fix this is to fork and update depedencies.
Another thing, if you're not using deno deploy, you can just use this as a replacement for your denodb: https://raw.githubusercontent.com/joeldesante/denodb/master/mod.ts
Just note that this script is no more maintained either, but it will fix your problem
Edit
I just made a dirty quick fix for deno deploy use this as a depedency isntead of denodb: https://raw.githubusercontent.com/ninjinskii/denodb/master/mod.ts
Again, i may not maintain this script forever.
The best thing that can happen is an update from these libs maintainers

Modelsim shows an unknown warning about vmap command

I created the library "work", but then when I try to use the command "vmap work work" I get the following warning about 20 times in a row: " ** Warning: (vmap-7) Failed to open lock file "C:/intelFPGA/20.1/modelsim_ase/win32aloem/../modelsim.ini_lock" in create mode.
Permission denied. (errno = EACCES)".
Afterwards it shows the following error: "-- Giving up waiting on lock. Lockfile is "C:/intelFPGA/20.1/modelsim_ase/win32aloem/../modelsim.ini_lock".
** Error: WriteIniString C:/intelFPGA/20.1/modelsim_ase/win32aloem/../modelsim.ini failed: 2".
I couldn't find anything about this create mode or modelsim.ini_lock in my pc, google or this site. However, the vhd files run as expected.
Does someone know how to fix this?
Did you change the permission settings of modelsim_ase?
I had the same problem occur after I modified the settings.
My solution is to open the property settings of the file "modelsim.ini" in modelsim_ase folder and make it "read-only".

Unable to login to RStudio Server after changing user id in Ubuntu? RStudio Initialization Error - Error occured during transmission

I'm unable to login to my RStudio Server installed on a ubuntu container. I've created the accounts and changed the user ids.
Screenshot of error:
Looking at /var/log/syslog there are Operation not Permitted errors on temporary files under /tmp/rstudio-rsessions - I just had to change the ownership or delete the files user-d and user-d.pid.

Atom beautify spawn EACCES

I am trying to install an add-on to clean up my PHP called Atom beautify.
Every time I run the plugin to make my PHP file pretty (Atom Beautify) I get this showing up:
Error: spawn EACCES
at exports._errnoException (util.js:1026:11)
at ChildProcess.spawn (internal/child_process.js:313:11)
at exports.spawn (child_process.js:392:9)
at /Users/myusername/.atom/packages/atom-beautify/src/beautifiers/beautifier.coffee:349:13
at Promise._execute (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/debuggability.js:300:9)
at Promise._resolveFromExecutor (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:483:18)
at new Promise (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:79:10)
at PHPCSFixer.module.exports.Beautifier.spawn (/Users/myusername/.atom/packages/atom-beautify/src/beautifiers/beautifier.coffee:346:16)
at /Users/myusername/.atom/packages/atom-beautify/src/beautifiers/beautifier.coffee:308:10
at tryCatcher (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:693:18)
at Promise._fulfill (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:638:18)
at PromiseArray._resolve (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise_array.js:126:19)
at PromiseArray._promiseFulfilled (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise_array.js:144:14)
at Promise._settlePromise (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:574:26)
at Promise._settlePromise0 (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:693:18)
at Async._drainQueue (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:133:16)
at Async._drainQueues (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:143:10)
at Async.drainQueues (/Users/myusername/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:17:14)
I am currently using a Mac computer if that matters at all.
Line 349 of beautifier.coffee is:
cmd = spawn(exe, args, options)
This is where it would make a call to the beautify program. For PHP, that seems to default to php-cs-fixer, as shown in php.coffee:
defaultBeautifier: "PHP-CS-Fixer"
So you probably want to verify that PHP-CS-Fixer is installed and that it is set up properly (the program is readable / executable, preferably in your PATH).
The PHP-CS-Fixer README has installation instructions.

Use qjson in my Qt symbain app

I'm using Qt to develop a Symbian app.
I downloaded qjson from the link. I followed the instructions in that link and yes, I have the qjson.sis file. Now I need to use it in my app. When I tried, I got this error.
Launch failed: Command answer [command error], 1 values(s) to request: 'C|101|Processes|start|""|"MyProject.exe"|[""]|[]|true'
{"Code":-46,Format="Failed to create the process (verify that the executable and all required DLLs have been transferred) (permission denied)"}
Error: 'Failed to create the process (verify that the executable and all required DLLs have been transferred) (permission denied)' Code: -46
And when I press the launch icon, it shows, "Unable to execute file for security reasons".
Then I install the qjson.sis in my mobile and then tried to install my app, I got this error.
:-1: error: Installation failed: 'Failed to overwrite file owned by another package: c:\sys\bin\qjson.dll in ' Code: 131073; see http://wiki.forum.nokia.com/index.php/Symbian_OS_Error_Codes for descriptions of the error codes
In my .pro file I have this.
symbian: {
addFiles.sources = qjson.dll
addFiles.path = /sys/bin
DEPLOYMENT += addFiles
}
symbian: {
LIBS += -lqjson
}
Any ideas...?
Ok, I've just resolved a similar issue: it seems that your current build of QJson's library has different UID3 than the previous one that you installed on the phone.
Each .SIS file that is installed on the device has an identifier. The phone OS tracks which file was installed by which packacge, and if some new package wants to overwrite an existing file, the OS checks whether the new package has the same 'identity' than the previous owner of the file to be overwritten.
If the identity does not match, this error pops up.
There are number of reasons why this could have happened. For example, you could have simply changed the UID3 of the QJson before the build. Or, maybe you have forgot to set the library's UID3? Check the "src.pro' in the QJson project and go to the half of the file, you'd see lines:
#TARGET.UID3 =
TARGET.CAPABILITY = ReadDeviceData WriteDeviceData
If there's #, then you have forgot to set it and the build process assumed, well, letssay 'a random value'. So, now, set it to something, ie. TARGET.UID3 = 0xE0123456. Remember to correct that once you are ready to publish the application.
If a package with broken UID3 gets onto your phone and is blocking something - simply: uninstall it. Go to Settings/Installations/Installed, then find "qjson" and uninstall it. Afterwards, next installtion of qjson should succeed with no problems.

Resources