Giters

b3by / atom-clock

Place a clock or calendar in your status bar

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Failed to activate the atom-clock package

GLaDO8 opened this issue · comments

commented

[Enter steps to reproduce:]

  1. ...
  2. ...

Atom: 1.14.3 x64
Electron: 1.3.13
OS: Mac OS X 10.12.2
Thrown From: atom-clock package 0.1.5

Stack Trace

Failed to activate the atom-clock package

At Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.

Error: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.
    at Error (native)
    at /app.asar/node_modules/status-bar/lib/status-bar-view.js:93:23)
    at AtomClockView.drawElement (/packages/atom-clock/lib/atom-clock-view.js:54:20)
    at AtomClockView.start (/packages/atom-clock/lib/atom-clock-view.js:13:10)
    at Object.consumeStatusBar (/packages/atom-clock/lib/atom-clock.js:45:24)
    at Provider.module.exports.Provider.provide (/app.asar/node_modules/service-hub/lib/provider.js:29:52)
    at ServiceHub.module.exports.ServiceHub.consume (/app.asar/node_modules/service-hub/lib/service-hub.js:50:18)
    at Package.module.exports.Package.activateServices (/app.asar/src/package.js:404:75)
    at Package.module.exports.Package.activateNow (/app.asar/src/package.js:221:16)
    at /app.asar/src/package.js:190:32
    at Package.module.exports.Package.measure (/app.asar/src/package.js:96:15)
    at /app.asar/src/package.js:183:26
    at Package.module.exports.Package.activate (/app.asar/src/package.js:180:34)
    at PackageManager.module.exports.PackageManager.activatePackage (/app.asar/src/package-manager.js:550:34)
    at /app.asar/node_modules/settings-view/lib/package-manager.js:439:29
    at exit (/app.asar/node_modules/settings-view/lib/package-manager.js:69:16)
    at triggerExitCallback (/app.asar/src/buffered-process.js:303:11)
    at /app.asar/src/buffered-process.js:333:11)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)

Commands

     -5:23 autocomplete-plus:confirm (input.hidden-input)
  7x -5:22.1.0 core:backspace (input.hidden-input)
     -5:20 editor:newline (input.hidden-input)
  2x -5:17.6.0 core:backspace (input.hidden-input)
     -5:13.3.0 core:move-down (input.hidden-input)
     -5:13.1.0 autocomplete-plus:confirm (input.hidden-input)
     -5:13.1.0 snippets:expand (atom-text-editor.editor.is-focused.autocomplete-active)
 11x -5:10.5.0 core:move-right (input.hidden-input)
 38x -5:07.8.0 core:backspace (input.hidden-input)
     -3:29.8.0 core:confirm (input.hidden-input)
 10x -1:47 core:backspace (input.hidden-input)
     -1:41.7.0 core:confirm (input.hidden-input)

Non-Core Packages

ariake-dark-syntax 0.1.3 
atom-clock 0.1.5 
atom-material-syntax 1.0.2 
atom-material-ui 1.3.9 
genesis-ui 0.5.0 
solarized-dark-ui 0.3.2 
solarized-seti-ui 0.8.6
commented

Thanks for notifying me this. I'll look into it as soon as possible!

commented

I am not able to reproduce this bug. Is it still active? According to the stack trace, something seems to be wrong in the status-bar package.
Have you tried starting Atom in safe mode and checking if the package activation still works?

commented

It seems like this issue is becoming fairly common lately in most atom packages including atom itself. Here is an issue where someone had the same sort of issue..

Try disabling your linter and restart atom and see if this fixes the problem!

commented

So, the problem is actually related to the status-bar package itself? I don't use the linter package, maybe that's the reason I was not able to reproduce the issue.

commented

my work space is messed right now I
'm overwhelmed