Paul Schoenfelder

@binarylogic yeah I mean the Timex release for 1.3 ;)

@binarylogic 1.3 introduced calendar types, so the types Timex introduced a long time ago are no longer necessary. Because of the new calendar API, I'm refactoring Timex to use those...

It is, I just haven't had the time or need to work on this yet. It is definitely something I'd be glad to merge if someone wants to take on...

I just came across this issue, but something to be aware of is that the shadow stack used by LLVM is separate from the host stack (i.e. the "real" stack),...

I'm a little surprised by the first point - that a node with the same name but different version would be considered permanently down. In many consistency models, Raft for...

@Arthien The reason why it doesn't matter how long a node is down in Raft (for example) is because when a node comes back, it is caught up by the...

The topology by definition would be responsible for translating the node name to something meaningful for its transport. The most trivial example could be using DNS A records to get...

This is going to require a clustering abstraction (for both the topology and the messaging), so I would recommend we leverage [firenest](https://github.com/phoenixframework/firenest) for that. Firenest abstracts out node communication and...

I'm certainly interested in working on this, so I'll set aside some time to read the paper again and catch up on some of the other links you mentioned here....

So my take on this is that while an explicit API is nice to have (particularly for testing), it is possible to make this automatic using node monitoring (where we...