You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried out the new shell adapter in #800 in a non-test hubot, and seeing problems:
Hubot> hubot hel[Fri Dec 05 2014 18:19:08 GMT-0500 (EST)] ERROR Error: EBADF, bad file descriptor
at Object.fs.writeSync (fs.js:429:18)
at Interface.rl._addHistory (/Users/technicalpickles/github/hubot-classic/node_modules/hubot/node_modules/readline-history/readline-history.js:106:20)
at Interface._line (readline.js:516:19)
at Interface._ttyWrite (readline.js:736:14)
at ReadStream.onkeypress (readline.js:97:10)
at ReadStream.EventEmitter.emit (events.js:126:20)
at emitKey (readline.js:1058:12)
at ReadStream.onData (readline.js:807:7)
at ReadStream.EventEmitter.emit (events.js:96:17)
at TTY.onread (net.js:397:14)
And on a different run:
ERROR Error: UNKNOWN, unknown error
at Object.fs.writeSync (fs.js:429:18)
at Interface.rl._addHistory (/Users/technicalpickles/github/hubot-classic/node_modules/hubot/node_modules/readline-history/readline-history.js:106:20)
at Interface._line (readline.js:516:19)
at Interface._ttyWrite (readline.js:736:14)
at ReadStream.onkeypress (readline.js:97:10)
at ReadStream.EventEmitter.emit (events.js:126:20)
at emitKey (readline.js:1058:12)
at ReadStream.onData (readline.js:807:7)
at ReadStream.EventEmitter.emit (events.js:96:17)
at TTY.onread (net.js:397:14)
The .hubot_history file does exist, but it's empty.
The text was updated successfully, but these errors were encountered:
If you used sudo to run hubot the first time it creates a .hubot_history as root then if you try to run hubot not as root you get an error like that. Try chowning the .hubot_history file. It worked for me.
I tried out the new shell adapter in #800 in a non-test hubot, and seeing problems:
And on a different run:
The .hubot_history file does exist, but it's empty.
The text was updated successfully, but these errors were encountered: