hi, i asked this a while ago, and got into somethign else and was never able to try it. I was trying to figure out the best way to debug my workflows, etc. I beleive someone posted something some sort of “spy” key you could put on a catalog entry. I think it pointed to a user function that would get a look at the segments. But I don’t see it in the documentatoin

@eoliphant I think they were referring to sticking a spy onyx/fn on your input tasks

the spy fn would just be

(defn myspy [segment] (println segment) segment))

ah yeah

just found it in the user guide lol

thanks

ah nice

So, I'm getting a "clojure.lang.ExceptionInfo: Unfreezable type: class clojure.lang.ExceptionInfo" error. One of my tasks is throwing an exception, and Onyx appears to be having trouble passing the exception on to the next task, so it then throws this unfreezable type exception. Is that a thing?

@stephenmhopper Exceptions can’t be passed between tasks.

You can use a flow condition handler to turn it into something serializable and pass it downstream.

ah, okay. Can I just use clojure.core/Throwable->map?

What do you typically use?

@stephenmhopper I’ve usually taken apart the map myself with ex-data, but that should work

I just learned about that function recently. 🙂

@michaeldrogalis okay, thank you!

Anytime!