Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    饶琛琳
    @chenryn
    timechart can solve the issue, I'm glad to watch the new example too.
    Rodney Lopes Gomes
    @rlgomes
    @chenryn took me a bit to get things to work nicely but here's an example of shifting/lining up date from multiple days so they can be joined or simply overlayed in different views:
    sub shift_date(date) {
        put time = date + Duration.new(Date.get(time, 'hour')*60*60)
    }
    
    (
    emit -from :2016-01-01: -every :hour: -limit 24
    | put value1=10*Math.random()
    | shift_date -date :today:;
    emit -from :2016-02-01: -every :hour: -limit 24
    | put value2=100*Math.random()
    | shift_date -date :today:;
    )
    | join
    the sub shift_date is where all the magic happens
    now the above really only works for data that is lined up by the hour (let me think if there's a nicer way to handle any data by lining up based simply on milliseconds since the start of the day
    Rodney Lopes Gomes
    @rlgomes
    @chenryn now a solution where we can align your datas dates to a specific day
    sub shift_date(date) {
        put time = date + (time - Date.startOf(time, 'day'))
    }
    
    (
    emit -from :2016-01-01: -every :hour: -limit 24
    | put value1=10*Math.random()
    | shift_date -date :today:;
    
    emit -from :2016-02-01: -every :hour: -limit 24
    | put value2=100*Math.random()
    | shift_date -date :today:;
    )
    | join
    this new way means we simply subtract the current time field value from the midnight of that day figuring out exactly how far into the day that timestamp is and add that to the desired start of the day in the example above we're aligning to :today: which is basically midnight of today
    Rodney Lopes Gomes
    @rlgomes
    @chenryn we pushed out a fix to a dependency of juttle-engine that fixes your issue on Chrome v42 so you could do npm uninstall juttle-engine -g followed by npm install juttle-engine -g and let us know if the error has gone away on chrome and things look good again.
    饶琛琳
    @chenryn
    try again, there is no error in console now, but webpage report the same unexpected error
    Daria Mehra
    @dmehra
    The default values error?
    饶琛琳
    @chenryn
    a.default.values(...).find is not a function
    yes
    Daria Mehra
    @dmehra
    Strange, we tested in a docker container with your chrome version and it worked... Any chance you could update Chrome to latest, to get around this?
    饶琛琳
    @chenryn
    I open chrome://chrome/ then it tell me it's newest version...
    because I'm in China maybe...I will download a newer one manually.
    Daria Mehra
    @dmehra
    Does "about chrome" say 49? Or 48 which I have and also works fine? Your old one was 42
    Rodney Lopes Gomes
    @rlgomes
    @chenryn I'm back... can you check you share what the output of npm ls juttle-engine juttle-viewer juttle-client-library -g outputs ?
    饶琛琳
    @chenryn
    /opt/local/lib
    └─┬ juttle-engine@0.5.0
    └── juttle-viewer@0.3.2
    Rodney Lopes Gomes
    @rlgomes
    juttle-viewer seems to be at the right version so I'm very stumped
    oh you were running juttle-engine &... did you have one already running ? can you make sure to kill anything that was running ? ps aux | grep juttle if there's any juttle-engine then pkill -9 [pid] and start the juttle-engine again ?
    饶琛琳
    @chenryn

    just one process running.

    I install a version49, and everything right now.

    Rodney Lopes Gomes
    @rlgomes
    the TypeError: Object.assign is not a function {stack: (...), message: "Object.assign is not a function"} (anonymous function) @ index.js:25 issue was solved
    but I somehow forgot there was the a.default.values(...).find is not a function on the page so I'm going to see what that was about
    Rodney Lopes Gomes
    @rlgomes
    ok well @chenryn let us know if you run in to any other problems
    try out a few example programs and see that things are working fine with juttle-engine
    David Majda
    @dmajda
    We just released juttle 0.7.0: https://github.com/juttle/juttle/releases/tag/v0.7.0. Other components will follow shortly. Tracking issue is here: juttle/juttle-engine#96
    Mark Stemm
    @mstemm
    We just released juttle-engine 0.6.0: https://github.com/juttle/juttle-engine/releases/tag/v0.6.0. It’s available on npm now. We’ll be updating the docker images shortly. I’ll send another heads up once the docker images are available.
    Phil Rzewski
    @philrz
    Greetings to the Juttle community. So, as I've heard from its founders, and you can all confirm for yourselves in seeing the 404 returned at www.jut.io, the corporate sponsor of the Juttle project "Jut Inc." has closed up shop. I'd be curious to hear if anyone in the community has interest/skills in continuing to shepherd the project going forward. I know it's not going to be me, as I'm no JavaScript developer. :) But I've enjoyed my time with Juttle as a user, and I'd like to know it's there to consider for future data analytics/visualization projects. The degree to which that'd be easy/hard would largely depend on knowing if it has a future.
    Daria Mehra
    @dmehra
    Yes indeed we are now a true open source project with not a grain of corporatism
    I'll definitely keep watching the channel and assist users as needed (and will likely be a user myself)
    Phil Rzewski
    @philrz
    Yeah. What'll be interesting is to see what happens if someone actually puts up a PR for a bug fix, if anyone will have the stomach to review, etc.
    The cool thing is that it's easy enough to get started with that I'd probably give it a shot regardless. Like, I may start a new job where I need to store/visualize performance data. So it would not be difficult for me to start storing it in InfluxDB/Elasticsearch and visualize it with Juttle. If I get to some bug that makes Juttle unusable, I'll still have my data. Not much lost.
    Mark Stemm
    @mstemm
    I have a couple of minor cleanup things I want to push through so I’ll try to pester the other juttlers for a review. I’ll also keep an eye on prs.
    Michael Demmer
    @demmer
    I'm planning on continuing to keep an eye on things as time allows.
    Mark Stemm
    @mstemm
    FYI, I pushed version 0.6.0 of juttle-engine to docker hub (https://hub.docker.com/r/juttle/juttle-engine/tags/). It has a workaround for a bug related to module resolution so the example amazon programs still work.
    Daria Mehra
    @dmehra
    I realized that demo.juttle.io is now down but still linked from the readmes
    Mark Stemm
    @mstemm
    yeah that level of cleanup can happen later I’d say
    Daria Mehra
    @dmehra
    Should remove the links or maybe rehost the demo system? It would cost pennies to run...
    Mark Stemm
    @mstemm
    well juttle.io is technically owned by jut
    Daria Mehra
    @dmehra
    Ok, rehome with new name
    Michael Demmer
    @demmer
    @dmehra I we could transfer ownership of the juttle.io domain to some other entity that would want to continue to pay for it and any associated hosting fees to run a demo service.
    饶琛琳
    @chenryn
    I try to visit http://www.jut.io but got 404 not found. Is jut.io the company behind the juttle?
    Phil Rzewski
    @philrz
    @chenryn: Yes, Jut was that company but is no longer in business. The Juttle open source project still exists but it seems the community behind it is no longer very active. It's still a pretty cool project though, and several of the people who used to be involved in it probably watch the repo, so if you have questions/additions/etc. you might get some attention.
    Gopalakrishna Palem
    @KrishnaPG
    @demmer I can take the ownership (of juttle.io) and keep the demo running, if enough people are interested in it.
    Phil Rzewski
    @philrz
    I'm +1 to that idea. I've not had reason to use Juttle in my day-to-day right now, but I'm definitely in favor of anything that will keep it alive such that it might still have some life in it when the day comes that I need it.
    Gopalakrishna Palem
    @KrishnaPG
    It has the potential, if not now, in the future, especially if it can combined with the likes of https://nifi.apache.org/ (and leverage what is already existing there).
    Please PM me with the details of how to make the transition work - we can start, to keep the www.jut.io going
    Michael Demmer
    @demmer

    @KrishnaPG I’d be ok with transferring ownership or just setting up whatever links you might want for running the demo.

    Let’s take this off gitter and move to email. Shoot me a note at demmer@gmail.com with what you might actually want to run for the demo. Previously we had an instance of juttle-engine running on a pretty beefy node in AWS behind an ELB, which worked ok but it was a bit expensive to run.

    Tomasz Muszynski
    @herki
    Hi is this project officially dead? Any maintainers on github?
    Daria Mehra
    @dmehra
    There hasn't been active maintenance in a while... still a good core there, feel free to use / expand!