1 reply
but I can take it out if it's troublesome
it's so much extra overhead, even if it is the standard way to share microdata. grr. everything now requires an entire html parser to get at what's essentially an api
Just wish there was a way to get both
Or that the web hadn't developed like this lol
I wish for a world where we could just say accept content type application/JSON and get back the API
(but it's one more dependency, if you aren't already using it)
It's still 'messy', though, totally.
Hah, no worries, I was just going to say you're on your own in ruby land, but python seems okay-ish :)
I'm looking at it now, but on the live site (and a locally built one) when you click on the hopkins job you get NEB, etc.
All the FAQ links under https://galaxyproject.org/support/ report as missing. Tried adding in an "index.md" and that didn't fix it. This is a known right?
Was Ok earlier today...
Yeah, that doesn't look good. I don't see the error (yet), but something was weird with the last build for galaxyproject/galaxy-hub@c61b2de
I'm going to kick it.
I have a backup -- so don't worry about me. I can send the user was trying to help a link to that instead. WAY too much to type out fresh
Just some content edits
I kicked jenkins already to see if it was a fluke; building locally too.
local build failed
So... I need to get that testing branch merged in and we need to wait for tests to pass for merging ;)
I am a bit surprised the build failure didn't prevent the upload though; that's another thing to follow up on.
Looking through jenkins log, the commands were run with
-xe, which should have bailed given the first failure, but I'm wondering if make+docker are masking the exit code. Something to dig through tomorrow.
Ah-ha. Yep:
39 | }
at throwError (/tmp/hub/node_modules/gridsome/lib/app/build/executeQueries.js:22:13)
at pMap.concurrency (/tmp/hub/node_modules/gridsome/lib/app/build/executeQueries.js:59:9)
Done in 53.46s.
[dannon@inneoin:~/work/galaxy-hub] echo $? master ✭
0
It's not docker or the make, it's actually the gridsome build step that doesn't return a failing error code. If
yarn build returned an appropriate error code on fail, this couldn't happen.
Anyway, that's a problem for tomorrow.
@jennaj: It's back up and should be fine now; got the thing you wanted to link?