@darwin: https://github.com/elasticpath/rest-resource-viz/blob/dirac-script/scripts/dirac.sh

@richiardiandrea cool, but doesn’t really work for me on my mac

oh cool that you tested 😄 I was going to ask some colleague here

mktemp seems different, will debug it

btw. naked path args to mkdir are dangerous, imagine spaces in the filename: https://github.com/elasticpath/rest-resource-viz/blob/dirac-script/scripts/dirac.sh#L55

yeah I know, it slipped, tnx

does mktemp -d dirac.XXXXXXX works for you?

yes

also, do you think it is something I can contribute somewhere? Maybe the wiki?

--directory flag was invalid

kk

ok works fine here too

refresh the page to see it anew 😄

you could mention it in the https://github.com/binaryage/dirac/tree/master/docs somewhere

but I’m afraid that the script will be quite fragile, so at some point it will break and I won’t know about it / or are you going to maintain it?

ah ah yeah I think I am going to maintain it in that repo, haven't thought about that part yet

btw. still does not work, btw $OSTYPE is not a thing on mac https://gist.github.com/darwin/ddabaa0e7cb93af73fc78dd9cb496c0c

maaan, that SO post was lying then

at least it is not defined on my machine

uname is the way to go

yep I am reading

do they have x86 versions for linux? I have seen on x86_64

don’t remember

lol I was wondering, what if you release one they and there have been more than 100 builds ? you'll miss it...and now then I understand why you release so frequently 😄

that’s not the reason 🙂

that 100 number means “scan for last 100 versions to find last valid build”

ah ah I am joking

chrome devs would have to break 100+ versions so there would be no binaries for them

I had to increase to 150 for Mac now

hmm, this seems unlikely

btw. the reason I release quite often is that I want to be merging official changes in smaller chunks and I don’t want to fall too far behind canary builds with dirac

very weird the ''

returns 478483 but Mac position is 478480

I’m sorry, cannot help, I wrote those scripts many months ago

ah, now when I think about it

different platforms have different positions for official “build numbers”

or rather “might have”

no problem, you've helped a lot already...probably...yeah...it seems like 😄

imagine chrome build breaking on linux and passing on mac, the mac one will be tagged and released, but linux one will be delayed a few positions until it starts passing again

yeah now I need a way to detect that...but thanks for the heads-up

you don’t, you know which platform the user is on, so you scan for valid position on given platform

oh there is this: https://omahaproxy.appspot.com/all.json

I ended up fetching links for Dirac's release notes

I think this will be most robust solution

yeah and parsing a json is more difficult if you want to be cross platform so...will test it on Mac too

my colleague just went away for a Friday company beer lol 😄

I have to go as well, it is 1am here 🙂

thanks for your help as usual

np, thanks for caring about dirac’s usability 🙂