This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (42)
- # boot (12)
- # cider (3)
- # cljs-dev (277)
- # cljsrn (44)
- # clojure (127)
- # clojure-austin (9)
- # clojure-austria (1)
- # clojure-brasil (14)
- # clojure-canada (1)
- # clojure-dev (22)
- # clojure-dusseldorf (1)
- # clojure-italy (4)
- # clojure-russia (24)
- # clojure-spec (33)
- # clojure-taiwan (1)
- # clojure-uk (21)
- # clojure-ukraine (8)
- # clojurescript (134)
- # core-async (41)
- # core-logic (8)
- # cursive (1)
- # datomic (3)
- # ethereum (1)
- # events (4)
- # funcool (1)
- # leiningen (12)
- # off-topic (21)
- # om (19)
- # onyx (45)
- # overtone (1)
- # parinfer (2)
- # pedestal (3)
- # proton (2)
- # re-frame (103)
- # reagent (48)
- # test-check (27)
- # untangled (51)
- # vim (3)
@camechis The issue is that different Onyx versions treat the data in Zookeeper differently, under the assumption that two different versions of Onyx will never touch the same tenancy id
I'd like to make a policy of keeping backwards compatibility after 1.0. Still too early to lock in subpar design and API decisions though.
Anyone seen this exception before in the onyx logs? Our staging server just started doing this, and I can't get the node up again, really weird
read-log is an input task that uses onyx-datomic. I can't reproduce this locally, everything works fine
Are you setting
:onyx/input-retry-timeout on the task?
Ahh I see that's probably what's causing it, I did a random commit to get our tenancy id to update (we use an appended git sha). So it has to be an even number?
Thanks, I guess I needed to clear all the data out, and I was getting stuck on that error all the time due to my commit lol
You need to satisfy
(zero? (mod :onyx/pending-timeout :onyx/input-retry-timeout))
Hey, folks - I was lurking the other day and saw the exchange about plugin info model documentation existing in multiple places. Context: https://clojurians.slack.com/archives/onyx/p1474905742001319
wow, noticing that the catalog example snippets on the main info page (http://www.onyxplatform.org/) are now in json (no longer in EDN)...
This is a good plan. One thing we need to keep in mind is that there are prose parts to almost every plugin README. A summary, a hint here and there, maybe a warning. So we'll need to account for those, too.
Yeah, to the extent the expositions need to be adjacent with the generated stuff, we might need something more complex
@colinhicks: @michaeldrogalis I had a whack at generating the tables a long time back, so this might help a little bit https://github.com/onyx-platform/onyx/blob/686ca2a8bb1fed8cd3a6dbe63d75923460f46888/src/onyx/static/doc_gen.clj
I was trying to avoid the route where the README is a template with directives, but we could do something like that with pandoc
Right. We could invert the plugin and have it take a template file as a parameter, perhaps.
@lucasbradstreet, yeah static.doc-gen helped frame my thoughts when I came across it
The lein plugin could make use of it, which is a question I raised in the issue ...
We can just pull that out, doesn't need to exist in core if we're going to have a plugin for it.
Thanks for volunteering. This is one of those things we've been meaning to get to for ages. Helps a ton to get some community support on issues like this. 🙂
np, seems like a good challenge. I should be able to take a crack at it starting tonight
If you want to make that on your personal account, we can start with it there and move it into onyx-platform when it's ready -- if that's okay