This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-08
Channels
- # admin-announcements (1)
- # arachne (3)
- # beginners (17)
- # boot (36)
- # bristol-clojurians (1)
- # cider (4)
- # clara (10)
- # cljsjs (11)
- # cljsrn (20)
- # clojure (134)
- # clojure-austin (2)
- # clojure-boston (1)
- # clojure-czech (1)
- # clojure-greece (128)
- # clojure-norway (1)
- # clojure-romania (1)
- # clojure-russia (17)
- # clojure-spec (106)
- # clojure-sweden (1)
- # clojure-taiwan (1)
- # clojure-uk (41)
- # clojurescript (122)
- # component (4)
- # cursive (1)
- # datomic (34)
- # editors (57)
- # emacs (12)
- # events (5)
- # hoplon (18)
- # instaparse (1)
- # jobs (9)
- # keechma (9)
- # lein-figwheel (3)
- # luminus (1)
- # om (47)
- # onyx (31)
- # proton (2)
- # re-frame (7)
- # reagent (3)
- # rethinkdb (1)
- # specter (25)
- # sql (2)
- # untangled (21)
- # yada (1)
I have a weird problem after updating to onyx 0.9.7 where my dashboard shows everything up to a first :submit-job
and then doesn't show any jobs on the left side. Dashboard was updated to 0.9.7 as well.
Unfortunately there are no errors in JS console, only one message which appears even before choosing a tenancy:
Unhandled event: [:chsk/handshake [086172ee-44bb-4915-a915-470ba37cf2b8 qREL48+j7/OnGKNz2CsX5aCM6PP7Axz+hsoTYW0N4QiblkW8xXTNvpvnEhmR6Ka0bfqJd2RzleE6M704]]
Not sure it's related thoughThat should be fine as long as it isn’t throwing an exception on that event
@asolovyov: are you playing back a version of the log that is from a previous version of Onyx?
Alrighty. Just checking
Yeah I’m seeing something similar
You can see the submit-job entry, but it doesn’t list the job?
@asolovyov: I believe I’ve fixed the problem. onyx-dashboard 0.9.7.1 is releasing now
I need to get more selenium tests working again. It used to perform more checks
@lucasbradstreet: wow, cool!
Uncaught #error {:message "Malformed event (wrong type). Event should be of `[ev-id ?ev-data]` form: :chsk/bad-package", :data {:malformed-event :chsk/bad-package}}
Hmm. New issue, right?
I’ve had bad package issues when the data was too big I think
Or there might be something in it that is not serializable
here is the error (it's in the end of the snippet): (Error: Could not find tag parser for schema.core.OptionalKey in ("inst" "uuid" "queue" "js"))
There’s some schema data in it
Is that something you’ve put in your job data?
The schema definitions I mean