Skip to content
This repository has been archived by the owner on Mar 4, 2022. It is now read-only.

strange terminal character output #12

Open
jmcneese opened this issue Oct 13, 2016 · 8 comments
Open

strange terminal character output #12

jmcneese opened this issue Oct 13, 2016 · 8 comments

Comments

@jmcneese
Copy link

added import to my server entrypoint:
import 'nodejs-dashboard';

added npm script like so:
"start:dev": "NODE_ENV=development nodemon --watch server --exec \"npm run build:schema && nodejs-dashboard babel-node server/index.js\""

get these escape characters after running for a minute or so:
screenshot 2016-10-12 22 26 43

this only occurs when my terminal is in rxvt mode, not in ansi mode.

@joshontheweb
Copy link

joshontheweb commented Oct 13, 2016

I have had a similar issue running
forever -c "nodejs-dashboard node" server.js

It just spits out the escape characters when I move the mouse but I don't even get to the dashboard view.

It seems to work fine running without forever.

It's worth noting that it seems to work ok doing:
nodejs-dashboard forever server.js

If I try and specify log outputs it doesn't show event loop delays though
nodejs-dashboard forever -o app.out server.js

@jlc467
Copy link

jlc467 commented Oct 15, 2016

Just curious, are you using iTerm2 with mouse reporting enabled? If so, try disabling and report back. It solved the issue for me.

node-dash-issue12

@vitosamson
Copy link

I was able to work around this by running nodemon inside of nodejs-dashboard: nodejs-dashboard -- nodemon -x 'node .'

@jasonwilson
Copy link
Contributor

@jmcneese were you able to get around this issue?

@joshontheweb
Copy link

@jlc467 Yes, I am using iterm with the mouse reporting so that makes sense.

In the end this worked fine for me:
nodejs-dashboard forever server.js

@tanepiper
Copy link

I've tried @vitosamson's solution but it doesn't work for me fully. The dashboard starts but the event loop, memory and cpu are not working. Other wise I get the same character rendering issue.

I tried forever too in watch mode but couldn't get it to work, it would just crash but spawn an instance.

@p77u4n
Copy link

p77u4n commented Dec 5, 2016

I have same problem :(

@jjasonclark
Copy link
Contributor

Adding link to related Blessed issue chjj/blessed#235

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants