Has anyone seen issues with :trigger/emit? I'm running Onyx 0.10.0, and I see the following exception when I use :trigger/emit, but not with :trigger/sync

Unfreezable type: class
   onyx.refinements$discarding_create_state_update
   {:type onyx.refinements$discarding_create_state_update, :as-str "#function[onyx.refinements/discarding-create-state-update]", :original-exception :clojure.lang.ExceptionInfo}

@fellows I haven’t seen that one. Using trigger/emit with the discarding refinement?

that looks pretty similar to what we’re doing in the test https://github.com/onyx-platform/onyx/blob/0.10.x/test/onyx/windowing/emit_aggregate_test.clj#L97

do you think you could try to reproduce it in that test?

Thanks. I'll give it a try.

Finally. 🙂 https://twitter.com/OnyxPlatform/status/885239185287688192

@lucasbradstreet -- I'm unable to repro that error running that test in conjunction with my project and config settings. But, I can reproduce the error if I start with lein new onyx-app <name>, change the onyx version to "0.10.0", and add use the following window and trigger settings.

(when running the basic-test)

@fellows thanks. If you created a new project would you mind pushing up the fresh project to github? No worries if not, but it'd make my life a little easier

Hmm, it appears my corp network won't let me do that...

Ah, no worries then. Should be easy enough anyway. Thanks!

I might be able to zip it and upload it here

that would be perfect

There you go

thanks for taking a look

thanks

@fellows oh, it’s because you’re trying to return the window-data arg which is basically a lot of metadata about the event. Unfortunately that record includes a lot of extra stuff that isn’t serializable, such as the refinement fn

Argh. I was afraid it was something dumb like that. Thanks a lot for looking at it.

No worries, it’d be nice if we checked for that but validating on every submit would cost a lot perf wise.