fabiocaseri / dashing-js Goto Github PK

There is an annoying 404 error from mincer when I use chrome.

2013-06-21T23:17:29.812Z - error: Served asset /favicon.ico - 404 Not found (4ms)
2013-06-21T23:17:29.812Z - info: GET /assets/favicon.ico 404 5ms

I have no clue where this comes from, as I see no requests for /assets/favicon.ico in chrome dev tools, and I have no idea how mincer works, but putting a favicon.ico inside /assets/images fixes this.

Hi,
the Readme.md talks about putting optional js files into the Lib dir
"Lib — Optional js/coffee files to help out your jobs.",
but I can't figure out how to include/reference them (i.e. the functions etc. provided by them) in my jobs/*.job.js files.

Any hint will be appreciated,

Thx!

I have installed the node using the commands :
echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc

. ~/.bashrc
mkdir ~/local
mkdir ~/node-latest-install
cd ~/node-latest-install
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1
./configure --prefix=~/local
make install # ok, fine, this step probably takes more than 30 seconds...
curl https://www.npmjs.org/install.sh | sh

Listed in https://gist.github.com/isaacs/579814 (Top command)

After the successful installation I could get the node and npm versions as 7.10.0 and 4.5.0 respectively.

I tried to install dashing-js with the command "npm install -g dashing-js" which failed with the exception :

_(node:58704) DeprecationWarning: child_process: options.customFds option is deprecated. Use options.stdio instead.
make: Entering directory /home/bpmuser/local/lib/node_modules/dashing-js/node_modules/node-sass/build' CXX(target) Release/obj.target/binding/binding.o In file included from ../binding.cpp:7:0: ../sass_context_wrapper.h:10:3: error: ‘uv_work_t’ does not name a type uv_work_t request; ^ ../sass_context_wrapper.h:20:3: error: ‘uv_work_t’ does not name a type uv_work_t request; ^ ../binding.cpp:13:20: error: variable or field ‘WorkOnContext’ declared void void WorkOnContext(uv_work_t* req) { ^ ../binding.cpp:13:20: error: ‘uv_work_t’ was not declared in this scope ../binding.cpp:13:31: error: ‘req’ was not declared in this scope void WorkOnContext(uv_work_t* req) { ^ ../binding.cpp:19:22: error: variable or field ‘MakeOldCallback’ declared void void MakeOldCallback(uv_work_t* req) { ^ ../binding.cpp:19:22: error: ‘uv_work_t’ was not declared in this scope ../binding.cpp:19:33: error: ‘req’ was not declared in this scope void MakeOldCallback(uv_work_t* req) { ^ make: *** [Release/obj.target/binding/binding.o] Error 1 make: Leaving directory /home/bpmuser/local/lib/node_modules/dashing-js/node_modules/node-sass/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/home/bpmuser/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:194:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 4.2.0-30-generic
gyp ERR! command "/home/bpmuser/local/bin/node" "/home/bpmuser/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/bpmuser/local/lib/node_modules/dashing-js/node_modules/node-sass
gyp ERR! node -v v7.10.0
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok
Build failed
/home/bpmuser/local/lib
└── (empty)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: node build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node build.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/bpmuser/.npm/_logs/2017-05-15T11_02_12_185Z-debug.log

npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated [email protected]: Deprecated, use jstransformer
npm WARN deprecated [email protected]: use node-gyp@3+ instead
npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Use uuid module instead
npm ERR! tar.unpack error reading /home/bpmuser/.npm/graceful-fs/4.1.11/package.tgz
/home/bpmuser/local/lib
└── (empty)

npm ERR! code EBADF
npm ERR! errno -9
npm ERR! syscall fstat
npm ERR! EBADF: bad file descriptor, fstat

npm ERR! A complete log of this run can be found in:

Hey,

I have been trying to install Dashing-js for 1 day but without success.
I am not very familiar with NPM and have tried many things.
How to install dashing-js in 2020?

Every time I can't build my project because sass is out of date or because I have this error:
internal/modules/cjs/loader.js:775 throw err; ^ Error: Cannot find module 'C:\Users\Naografix\AppData\Roaming\npm\node_modules\dashing-js\bin\dashing-js' �[90m at Function.Module._resolveFilename (internal/modules/cjs/loader.js:772:15)�[39m �[90m at Function.Module._load (internal/modules/cjs/loader.js:677:27)�[39m �[90m at Function.Module.runMain (internal/modules/cjs/loader.js:999:10)�[39m �[90m at internal/main/run_main_module.js:17:11�[39m { code: �[32m'MODULE_NOT_FOUND'�[39m, requireStack: []

Tried community fork (in PR) but nothing...

Thanks for your help

Is this project planned to be maintained?

There's a number of projects I want to write to utilise dashing but only if it's to be continued. I'd be happy to contribute to work as well.

It would not be better to use 'nodemon' to watch for changes in jobs, dashoards, widgets, to avoid having to manually restart a deamonized proc. Also Supervisor and or Forever would be helpful in keeping the server alive for CICD.

I 've run the sample dashboard and the data don't appear !!

Is this module doesn't work or i missing something here ?

or at least it's depressing to see a down arrow on a metric that's not changing =)

Not much to add to the description. There're a couple of issues with IE9 support - for example EventSource is not supported and requires a Polyfill, and the CSS seems to be broken and not working.

I'm working on a patch right now. This task is for tracking and notifying you about the efforts and progress.

Generating a new dashboard throws an error during .ejs template processing:

Generating dashboard "test"
{ [ReferenceError: C:\Users\xxx\AppData\Roaming\npm\node_modules\dashing-js\
templates\dashboard\%name%.jade.tt:8
    6|   </ul>
    7| </div>
 >> 8| <%- contentFor('title') %>
    9| My dashboard title

contentFor is not defined]
  path: 'C:\\Users\\xxx\\AppData\\Roaming\\npm\\node_modules\\dashing-js\\te
mplates\\dashboard\\%name%.jade.tt' }
      create  dashboards\test.jade

Steps to reproduce:

dashing-js new test
npm install
cd test
dashing-js generate dashboard test

This error occurs in both Windows and Ubuntu.

gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:258:23)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.15063
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\sunka04\AppData\Roaming\npm\node_modules\dashing-js\node_modules\node-sass
gyp ERR! node -v v8.9.4
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\sunka04\AppData\Roaming\npm-cache\_logs\2018-02-17T19_18_14_829Z-debug.log

PS C:\Users\sunka04\Documents\Source> npm --version
5.6.0
PS C:\Users\sunka04\Documents\Source> node --version
v8.9.4

is there any way to let widgets save there data to redis?

Hi,

I tried to use one of the (many) existing dashing widgets:
https://gist.github.com/stephsharp/6484136

But couldn't get it work.. following the install instructions of the widget, I realised that some of the steps cannot be achieved as dashingJS was ported to node (and not using ruby).

Is there a way to use existing dashing widgets (https://github.com/Shopify/dashing/wiki/Additional-Widgets) or I need to port them as well? If so - any recommendation how to do such porting?

The application.css file fails to load.

I've looked for syntax errors in the sass file, but can't find any (ruby-sass compiles it without problems)

There are also no errors in the console.
I don't even see express saying anything about a request for the file.
So I have no idea where it's disappearing to.

make: Leaving directory /usr/lib/node_modules/dashing-js/node_modules/node-sass/build' gyp ERR! build error gyp ERR! stack Error:makefailed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23) gyp ERR! stack at emitTwo (events.js:87:13) gyp ERR! stack at ChildProcess.emit (events.js:172:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12) gyp ERR! System Linux 3.19.0-28-generic gyp ERR! command "/usr/bin/nodejs" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /usr/lib/node_modules/dashing-js/node_modules/node-sass gyp ERR! node -v v4.2.2 gyp ERR! node-gyp -v v3.0.3 gyp ERR! not ok Build failed npm WARN install:[email protected] [email protected] install:node build.js`
npm WARN install:[email protected] Exit status 1
/usr/lib
└── (empty)

npm ERR! code 1

on windows vista if that is pertinent.

latest version of node.

Fixed locally by fixing the version of sass in packages.json to 0.5.2.

Template Literal is fastest, smallest and simplest template engine, because it use JS's literal template feature.

It's 55 times faster than EJS, and it also use less CPU and RAM ressources, so it may be a good idea to use it instead of EJS 😀

When I try to load the localhost:3030, I receive the error and page below. Is this due to node incompatibilities? I am using 0.10.12

Has anyone run dashing-js with Express4?

You can test this by starting the server twice.

If lib directory is removed, the app is not going to start:

2014-02-14T19:30:02.323Z - info: Listening on http://0.0.0.0:3030, CTRL+C to stop
child process exited with code 1

Trying to install dashing-js on MacOS 10.11.6 with node 6.4.0 fails as follows:
npm install -g dashing-js
yields

$ npm install -g dashing-js
npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated [email protected]: Deprecated, use jstransformer
npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: use uuid module instead
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN excluding symbolic link test/fixtures/app/views/.#application.js.coffee.erb -> [email protected]
/usr/local/bin/dashing-js -> /usr/local/lib/node_modules/dashing-js/bin/dashing-js

> [email protected] install /usr/local/lib/node_modules/dashing-js/node_modules/node-sass
> node build.js

(node:46479) DeprecationWarning: child_process: options.customFds option is deprecated. Use options.stdio instead.
CXX(target) Release/obj.target/binding/binding.o
In file included from ../binding.cpp:7:
../sass_context_wrapper.h:10:3: error: unknown type name 'uv_work_t'
uv_work_t request;

If you add a image it resize's perfect in chrome and safari but firefox just show's the full image and doesn't resize it.

Hi,
I'm sorry if the question seems quite stupid but I do not have any experience using NodeJS.
I need to do a simple dashboard for my company, when running the sample dashboard I can see that under dashboards there are every-time 2 files one with the .ejs extension and one with the .jade extension.

Since I'm more familiar with the HTML syntax of EJS rather than the Jade syntax I wanted to edit the contents of the EJS template but whenever I make changes on the EJS template nothing happens on the dashboard whereas whenever I change anything on the Jade template the changes are visible.

Is there a particular reason for having these 2 formats? is it possible to only edit the EJS template and not the Jade one?

thanks

Ulises