Stream: Covid-19 Response
Topic: Sushi builds
Josh Mandel (Mar 25 2020 at 14:18):
Yeah @John Moehrke you were following the topic just fine; I was just noting that the topic had drifted quite a bit :)
Michael Donnelly (Mar 25 2020 at 15:09):
Thanks - I didn't want to mute SANER but don't need to know about sushi builds. :)
Chris Moesel (Mar 25 2020 at 19:44):
From @Grahame Grieve :
Grahame Grieve: @Chris Moesel what's a reasonable upper limit for sushi before I give up waiting and kill it? 1 minute?
Grahame Grieve: sigh... npm... the install has failed, and it's also broken other parts of my system
Chris Moesel (Mar 25 2020 at 19:45):
SUSHI is pretty fast. For the sample project I posted, less than 10 seconds should be sufficient. That said, if you don't have a local fhir cache and it needs to download the FHIR R4 package, then longer...
Chris Moesel (Mar 25 2020 at 19:47):
As for it failing and breaking other parts of your system... how did it fail? And how is it breaking other parts of your system? Installation of NPM modules shouldn't really be messing with too much else in your system, so I find that a little surprising.
Grahame Grieve (Mar 25 2020 at 19:59):
actually it might not have been npm. but something (re-?)installed python.
Grahame Grieve (Mar 25 2020 at 19:59):
I hate python.
Grahame Grieve (Mar 25 2020 at 20:00):
anyway, my release build process for the IG publisher uses python
Grahame Grieve (Mar 25 2020 at 20:00):
I'll leave the dead switch at 1 minute, and see how that goes
Chris Moesel (Mar 25 2020 at 20:01):
SUSHI has no dependencies on python -- so I doubt if it is the culprit.
Grahame Grieve (Mar 25 2020 at 20:02):
npm not sushi. it happened before I installed sushi but after I installed npm. But I did install some microsoft tools as well. so maybe that was it
Grahame Grieve (Mar 25 2020 at 20:07):
okay, it works fine. I'm working on getting a release out now, but I have to finish breaking the package infrastructure in order to do the release
Grahame Grieve (Mar 25 2020 at 20:08):
sorry, I have to finish fixing the broken infrastructure
Grahame Grieve (Mar 25 2020 at 20:08):
though I do seem to be breaking things...
Chris Moesel (Mar 25 2020 at 20:14):
Phew! I was worried there for a second about you breaking the package infrastructure. We use that in SUSHI!
BTW -- thanks, Grahame! This is really awesome.
Grahame Grieve (Mar 25 2020 at 20:15):
none of my tools would work without the package infrastructure. As everyone noticed when it broke
Grahame Grieve (Mar 25 2020 at 22:04):
ok released
Grahame Grieve (Mar 25 2020 at 22:04):
@Keith Boone feel free to test it out now...
Keith Boone (Mar 26 2020 at 08:11):
It's awfull close, last problem for me appears to be on Sushi side of the house. I think I might be able to fudge it for now by eliminating my ig.ini in fsh folder, and hopefully Sushi will leave my original one alone then.
Grahame Grieve (Mar 27 2020 at 12:48):
I've been working on this all evening (fixing other bugs) and I'm nearly there - but I must sleep. I'll do a new release that should support sushi first thing in the morning
Chris Moesel (Mar 27 2020 at 15:32):
Thanks for working this, @Grahame Grieve!
Hans Buitendijk (Apr 02 2020 at 15:47):
Where is the link to the latest IG build?
Hans Buitendijk (Apr 02 2020 at 15:52):
Never mind. Got it.
John Moehrke (Apr 02 2020 at 15:52):
Hans, the readme.md in the github has links to continuous build https://github.com/AudaciousInquiry/saner-ig
Last updated: Apr 12 2022 at 19:14 UTC
