@dspiteself: Our release process is another thing I need to eventually write about. It's set up so we can have fast turn around times. Every time we push to master of Onyx core, all 15 or so dependent projects/guides/tutorials/docs rebuild with the changeset from master to check for backward-compatibility issues.

Actually, just counted. 20 dependent projects.

Anyone available?

@conradj3: For a few minutes, yes.

I'm not sure where exactly it's thrown and I can't reproduce it in repl

@asolovyov: is this taken from onyx.log?

nope, that's from onyx dashboard

not seeing this exception in the logs at all 😞

oh

just found it

Hmm, that part is weird. Anyway, it looks like what happened is onyx-http got a 400 return code and threw an exception

yeah I guess so

well, not onyx-http

I'm just doing a request by hands 🙂

Oh

Looks like clj-http threw an exception as describe here: https://github.com/dakrone/clj-http#exceptions

Then flow conditions / handle-exception didn’t handle it, so your job was killed

yeah, that's ok, now I know where this happens and can discover more

weird thing is that it doesn't happen in repl 😕

Mmm strange

it still should be an error in my code of course

is this expected? 🙂

Ah, that one is fixed in 0.9.7. Not sure how it didn’t popup earlier

ah, ok

I'll need to update 🙂

Should be out v v soon

Once we fix our broken release process

I "fixed" it a couple of weeks okay. Now we're fixing it again. 😄