Jon Pretty

It happens when they come from different binary dependencies...

(Sorry I'm not always catching your replies quickly, @astefanich!) This is one of the problems with using binaries with Fury at the moment: it does nothing clever to resolve them,...

This also seems to cause Fury to hang when attempting to add a remote `repo` which doesn't exist.

We have the possibility of inconsistent layers, though, which may have broken dependencies or project name conflicts, and in those cases, the `Universe` won't exist, and hence the `Compilation` object...

What's the state of this issue at the moment, @odisseus?

Hi @Reina-39, Sorry for the confusion around the docs. I'm working on a complete overhaul of the documentation, which is happening in parallel with some crucial bugfixing. (There's no point...

One thing I had not fully appreciated before is that having Scala 2.13 and Scala 3 share a standard library will enable some degree of mixing of Scala 2 and...

I agree. Are the first two issues caused by the third? We also shouldn't use `killall` because it's not standard on every machine.

Yes, there's definitely some work required here. At least part of it is a UI issue: `require` and `obviate` affect the layer definition (while `grant` automatically grants the permission), and...

We should calculate the dependents efficiently, though. It would be easy to come up with an O(n³) algorithm, I think...