These are chat archives for juttle/juttle

11th
Feb 2016
David Cook
@davidbcook
Feb 11 2016 00:22
Hey juttle team, what are the chances I could export charts as svg?
Michael Demmer
@demmer
Feb 11 2016 00:41
@davidbcook This isn’t something we’ve really thought much about — maybe open a feature request against juttle-viz?

As a heads up to anyone that's been using outrigger, that project is now deprecated.

In its place, we've pulled together the same functionality (actually a bit more) in https://github.com/juttle/juttle-engine, which pulls together https://github.com/juttle/juttle-service (the node.js REST API), https://github.com/juttle/juttle-viewer (the client side app), along with the https://github.com/juttle/juttle runtime and all the adapters.

We've just pushed up new releases of all of these. Happy juttling!

David Cook
@davidbcook
Feb 11 2016 16:47
I'm trying to use the new juttle-engine in a demo to a client today, and I get this error in the browser window when I try to run a program: Cannot GET /?path=/Users/dcook/Lightwave/juttle-programs/PO-solo.juttle
Here is how I run the program: juttle-engine-client browser --path juttle-programs/PO-solo.juttle
Screen Shot 2016-02-11 at 8.46.21 AM.png
Mark Stemm
@mstemm
Feb 11 2016 16:48
I’m not exactly sure what you’re running into is related, but we just (minutes ago) figured out that juttle isn’t properly installed when juttle-engine is installed
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 16:48
you used the little drop down from the main page at http://localhost:8080/ to pick that file ?
Mark Stemm
@mstemm
Feb 11 2016 16:48
if you happen to have your npm install input and see a message like this
npm WARN cannot run in wd juttle@0.4.1 node scripts/peg.js (wd=/usr/local/lib/node_modules/juttle-engine/node_modules/juttle)
er, your npm install output lying around
David Cook
@davidbcook
Feb 11 2016 16:50
@mstemm I don't see that in the output of the npm install -g juttle-engine command @rlgomes no I ran that file from the command line
Mark Stemm
@mstemm
Feb 11 2016 16:51
as a second check, can you see what’s in /usr/local/lib/node_modules/jutle-engine/node_modules/juttle/lib/parser ?
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 16:51
try navigating to the file (just to see if it still says the same thing)
Mark Stemm
@mstemm
Feb 11 2016 16:51
this is assuming you’re using npm 2
the path will be different for npm 3 I think
David Cook
@davidbcook
Feb 11 2016 16:51
when I go to http://localhost:8080/ it just gives me a white screen that says Cannot GET /
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 16:51
ok so I think its what mstemm is talking about
David Cook
@davidbcook
Feb 11 2016 16:52
$ ls /usr/local/lib/node_modules/juttle-engine/node_modules/juttle/lib/parser/
index.js juttle-parser.js parser.js parser.pegjs
Mark Stemm
@mstemm
Feb 11 2016 16:52
yeah not the same thing
in fact, with this npm install problem juttle-engine won’t start at all
you got farther than that
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 16:53
@davidbcook nothing in the juttle-engine output ?
David Cook
@davidbcook
Feb 11 2016 16:54
the logs just say:
$ tail juttle-engine.log
[2016-02-10 14:47:07.112] [INFO] juttle-engine - Juttle engine listening at http://localhost:2000 with root directory:/
[2016-02-11 08:44:14.292] [INFO] juttle-engine - Juttle engine listening at http://localhost:8080 with root directory: /
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 16:55
two different listening at messages... :worried:
oh wait different dates ;)
David Cook
@davidbcook
Feb 11 2016 16:55
I installed juttle-engine yesterday then reinstalled this morning
Mark Stemm
@mstemm
Feb 11 2016 16:56
let me work around the other problem I’m having so I can get to the same state
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 16:57
if you're not getting an app at http://localhost:8080 lets see what we can do to figure out the issue... how did you install jutttle-engine ? globally ?
ie npm install juttle-engine -g ?
David Cook
@davidbcook
Feb 11 2016 16:57
yeah npm install -g juttle-engine
Oleg Seletsky
@go-oleg
Feb 11 2016 16:58
@davidbcook, i would npm uninstall -g juttle-engine and then make sure juttle-engine doesn’t work, and then install again
David Cook
@davidbcook
Feb 11 2016 16:59
did that and got the same error
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:00
@davidbcook lets just do a little side experiment
make a directory wherever you want
something like this
mkdir foo; cd foo ; touch package.json ; npm install juttle-engine
basically make a local install of juttle-engine
and then after you shut the other one you had running down just run within foo
./node_modules/.bin/juttle-engine and see how that one behaves
Oleg Seletsky
@go-oleg
Feb 11 2016 17:02
i think you’ll need to have package.json be valid JSON (add {} into it)
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:02
@go-oleg I totally only did a touch package.json and it worked ;)
don't ask me how that is a valid package.json but it is
Oleg Seletsky
@go-oleg
Feb 11 2016 17:03
almost
~/package-json-test$ touch package.json
~/package-json-test$ npm install underscore
/Users/olegseletsky/package-json-test
└── underscore@1.8.3

npm WARN Failed to parse json
npm WARN No data, empty input at 1:1
npm WARN
npm WARN ^
npm WARN File: /Users/olegseletsky/package-json-test/package.json
npm WARN package-json-test No description
npm WARN package-json-test No repository field.
npm WARN package-json-test No README data
npm WARN package-json-test No license field.
David Cook
@davidbcook
Feb 11 2016 17:03
how do I shut the running one down
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:03
ctrl+c ?
David Cook
@davidbcook
Feb 11 2016 17:04
it's not running in a terminal window
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:04
@go-oleg maybe because I have npm 3.6.0 ... meh npm
@davidbcook its daemonized ?
David Cook
@davidbcook
Feb 11 2016 17:04
yeah
(I think) that's what the -d option does right? ($ juttle-engine -d -o juttle-engine.log)
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:05
unless you have some other node process you care for just pkill -9 node
David Cook
@davidbcook
Feb 11 2016 17:06
$ ./node_modules/.bin/juttle-engine
/Users/dcook/Lightwave/foo/node_modules/juttle-service/lib/juttle-service.js:21
    Juttle.adapters.configure(options.config.adapters);
                    ^

TypeError: Juttle.adapters.configure is not a function
    at Object.configure (/Users/dcook/Lightwave/foo/node_modules/juttle-service/lib/juttle-service.js:21:21)
    at Object.run (/Users/dcook/Lightwave/foo/node_modules/juttle-engine/lib/juttle-engine.js:36:13)
    at Object.<anonymous> (/Users/dcook/Lightwave/foo/node_modules/juttle-engine/bin/juttle-engine:67:8)
    at Module._compile (module.js:425:26)
    at Object.Module._extensions..js (module.js:432:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Function.Module.runMain (module.js:457:10)
    at startup (node.js:138:18)
    at node.js:974:3
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:07
@mstemm is that the juttle bug we're fixing ?
Mark Stemm
@mstemm
Feb 11 2016 17:07
no
I haven’t seen that before
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:09
cook can you cdo the following (never seen that before) npm ls juttle in the foo directory
David Cook
@davidbcook
Feb 11 2016 17:09
$ npm ls juttle
/Users/dcook/Lightwave/foo
└── (empty)

npm ERR! code 1
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:12
my bad cd foo/node_modules/juttle-engine; npm ls juttle just to confirm its the right 0.4.1 like so:
rlgomes@x230> cd node_modules/juttle-engine
2016-02-11 09:11:45 $?=0 pwd=/home/rlgomes/jut/workspace/juttle-engine/caca/node_modules/juttle-engine branch=master duration=.007s                                     
rlgomes@x230> npm ls juttle
juttle-engine@0.2.1 /home/rlgomes/jut/workspace/juttle-engine/caca/node_modules/juttle-engine
`-- juttle@0.4.1
David Cook
@davidbcook
Feb 11 2016 17:16
$ npm ls juttle
juttle-engine@0.2.1 /Users/dcook/Lightwave/foo/node_modules/juttle-engine
└── juttle@0.4.1
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:17
to be sure the previously globally installed pakcages aren't messing with us lets do a quick
npm uninstall juttle outrigger juttle-engine -g
then see if ./node_modules/.bin/juttle-engine works in the foo local installation
David Cook
@davidbcook
Feb 11 2016 17:18
same error
Oleg Seletsky
@go-oleg
Feb 11 2016 17:20
@davidbcook, can you npm install juttle when you are in foo?
David Cook
@davidbcook
Feb 11 2016 17:21
$ npm install juttle

> juttle@0.4.1 postinstall /Users/dcook/Lightwave/foo/node_modules/juttle
> node scripts/peg.js

/Users/dcook/Lightwave/foo
└── juttle@0.4.1  extraneous

npm WARN EPACKAGEJSON foo No description
npm WARN EPACKAGEJSON foo No repository field.
npm WARN EPACKAGEJSON foo No license field.
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:21
warnings are "ok" see if the juttle-engine starts now from that local foo
David Cook
@davidbcook
Feb 11 2016 17:23
now it's running
Rodney Lopes Gomes
@rlgomes
Feb 11 2016 17:24
ok great (however bumpy it has been) will this work for demo purposes ? I bleieve you can acheive the global install also by doing npm install juttle-engine -g and then npm install juttle -g and we'll figure out how to fix this on our side to be just the single npm install juttle-engine -g
David Cook
@davidbcook
Feb 11 2016 17:30
awesome! this should be good for demo purposes. Thanks for the help @rlgomes @mstemm and @go-oleg!
oh shoot, the context charts aren't showing up anymore
Daria Mehra
@dmehra
Feb 11 2016 17:36
for a chart that is historical and otherwise fully loaded? not missing any final data points? (remember we had a bug on that, which was also preventing context charts from showing up, but it should be fixed in the release you have now)
David Cook
@davidbcook
Feb 11 2016 17:37
the program is the same program I ran in outrigger where the context charts appeared
but it does look like some of the data isn't showing up on the right side of the chart
Daria Mehra
@dmehra
Feb 11 2016 17:38
then it’s the same (similar?) websocket issue causing incomplete loading
let me double check that the fix is in this release
Daria Mehra
@dmehra
Feb 11 2016 17:45
sounds like the fix we made is included, and it was addressing the problem as i had reproduced it when you first reported
may we get some details about your program and amount of data going to the browser?
David Cook
@davidbcook
Feb 11 2016 18:16
sorry, super busy prepping for this demo. when I split the flow going into the timecharts to reduce count() | view table the tables say "waiting for data" so it looks like the same bug as before
Daria Mehra
@dmehra
Feb 11 2016 18:32
@davidbcook: i’m able to reproduce by increasing the number of charts in my program. looks like our fix moved the failure point out, but did not entirely address. sorry about that.
David Cook
@davidbcook
Feb 11 2016 18:33
ah ok, thanks for looking into it
good thing I didn't close my old outrigger tab!
Daria Mehra
@dmehra
Feb 11 2016 18:41
the tracking issue is juttle/juttle-service#9