Fork me on GitHub
#onyx
<
2016-09-29
>
aengelberg00:09:30

👍 👍 (as someone already bit by that exact issue)

Travis00:09:53

So what is the exact issue? Not sure I follow

aengelberg01:09:59

@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

aengelberg01:09:13

So there's no backwards compatibility in mind

michaeldrogalis01:09:06

Oh it's in mind -- it just hasn't been achieved very often. Yet. 🙂

Travis01:09:56

Guess I haven't hit the issue since we are still in early phases

michaeldrogalis01:09:41

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.

greywolve15:09:29

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

greywolve15:09:24

read-log is an input task that uses onyx-datomic. I can't reproduce this locally, everything works fine

greywolve15:09:34

Tried clearing ZK data, aeron data, etc

greywolve15:09:06

It's a single node

gardnervickers15:09:30

Are you setting :onyx/pending-timeout or :onyx/input-retry-timeout on the task?

greywolve15:09:49

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?

greywolve15:09:35

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

greywolve15:09:43

It's up again 🙂

gardnervickers15:09:05

You need to satisfy (zero? (mod :onyx/pending-timeout :onyx/input-retry-timeout))

colinhicks19:09:18

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

colinhicks19:09:04

I have a proposal if you're still looking for help, @michaeldrogalis

colinhicks19:09:03

Cool. Writing up an issue, now. Will link shortly.

aaelony19:09:59

wow, noticing that the catalog example snippets on the main info page (http://www.onyxplatform.org/) are now in json (no longer in EDN)...

michaeldrogalis20:09:39

@colinhicks Ah, a Leiningen plugin is a fantastic idea.

michaeldrogalis20:09:31

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.

colinhicks20:09:28

Yeah, to the extent the expositions need to be adjacent with the generated stuff, we might need something more complex

michaeldrogalis20:09:08

I don't mind making tweaks where it makes sense to accomodate.

colinhicks20:09:23

I was trying to avoid the route where the README is a template with directives, but we could do something like that with pandoc

lucasbradstreet20:09:24

We can use a README template for each plugin too

michaeldrogalis20:09:56

Right. We could invert the plugin and have it take a template file as a parameter, perhaps.

colinhicks20:09:26

Yep. Makes sense

colinhicks20:09:51

@lucasbradstreet, yeah static.doc-gen helped frame my thoughts when I came across it

colinhicks20:09:59

The lein plugin could make use of it, which is a question I raised in the issue ...

michaeldrogalis20:09:40

We can just pull that out, doesn't need to exist in core if we're going to have a plugin for it.

michaeldrogalis20:09:41

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. 🙂

colinhicks20:09:41

np, seems like a good challenge. I should be able to take a crack at it starting tonight

colinhicks20:09:17

assuming the lein plugin needs its on repo, where should that live?

michaeldrogalis20:09:49

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

michaeldrogalis20:09:52

Cool. I like this plan.