randy3k / remote-atom

rmate for atom
https://atom.io/packages/remote-atom
MIT License
85 stars 16 forks source link

Uncaught TypeError: Cannot read property 'lastChild' of undefined #10

Closed ny-shao closed 9 years ago

ny-shao commented 9 years ago

Uncaught TypeError: Cannot read property 'lastChild' of undefined

Atom Version: 0.157.0 System: linux 3.13.0-43-generic Thrown From: remote-atom package, v1.1.9

Steps To Reproduce

  1. ...
  2. ...

    Stack Trace

At /home/nshao/.atom/packages/remote-atom/lib/status-message.coffee:9

TypeError: Cannot read property 'lastChild' of undefined
  at new StatusMessage (/home/nshao/.atom/packages/remote-atom/lib/status-message.coffee:19:35)
  at Object.module.exports.display (/home/nshao/.atom/packages/remote-atom/lib/status-message.coffee:37:28)
  at Object.module.exports.stopserver (/home/nshao/.atom/packages/remote-atom/lib/remote-atom.coffee:156:17)
  at Object.module.exports.startserver (/home/nshao/.atom/packages/remote-atom/lib/remote-atom.coffee:127:14)
  at atom-workspace.<anonymous> (/home/nshao/.atom/packages/remote-atom/lib/remote-atom.coffee:118:68)
  at atom-workspace.handler (/opt/atom/resources/app/src/space-pen-extensions.js:115:32)
  at atom-workspace.jQuery.event.dispatch (/opt/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4681:9)
  at atom-workspace.elemData.handle (/opt/atom/resources/app/node_modules/space-pen/vendor/jquery.js:4359:46)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/opt/atom/resources/app/src/command-registry.js:243:29)
  at CommandRegistry.handleCommandEvent (/opt/atom/resources/app/src/command-registry.js:3:61)
  at CommandRegistry.module.exports.CommandRegistry.dispatch (/opt/atom/resources/app/src/command-registry.js:156:19)
  at Ipc.<anonymous> (/opt/atom/resources/app/src/window-event-handler.js:65:30)
  at Ipc.emit (events.js:107:17)
  at process.<anonymous> (/opt/atom/resources/atom/renderer/api/lib/ipc.js:22:29)
  at process.emit (events.js:110:17)

/cc @atom/core

randy3k commented 9 years ago

I guess you haven't upgraded to 1.1.9. It was solved in 1.1.9, see #9.