Mikaël Capelle

So apparently there is a bug in the version of tensorflow used for the test (2.1.2?). The `k` parameter for `tf.linalg.diag` and `tf.linalg.diag_part` is completely neglected. - https://github.com/tensorflow/tensorflow/issues/38434 - https://github.com/tensorflow/tensorflow/issues/37492...

> > > Let's call the method `diag` not `_diag`. No need limit `diag` to `ep.diag`. Might be nice to chain `diag` like other methods. Done. I've also reverted the...

> > > Thanks! Seems a couple of tests fail because the frameworks return inconsistent results. Yes, as I said in a previous comment, the tensorflow version used in the...

I've rebased the PR from `master` to get the upgraded TF in tests, hopefully this should fix the bug previously mentioned.

Thanks for the answer, I can try to make a PR but I never used JAX. Side question: Is there a way to extend `eagerpy.*` by using, e.g., entry points...

So I started to write a PR for this but I'm kind of confused with your test sets... Currently I have something like this: ```python @compare_all def test_diag_1(dummy: Tensor) ->...

Actually, the issue seems unrelated to the strategy or argparse, it simply occurs from time to time. I tried to debug it, and for what I understand, there is a...

I also notice from the comment on `finder` (*"point to (one of) the solver(s) which found a solution"*) that this is likely expected, but I don't really understand how... I...

That's an issue when looking for all solutions to a satisfaction problem. My current workaround is to add a `IMonitorSolution` to all the solvers and use it to fill the...

> I don't think there is a way to certify that each solution appears once when looking for all of them in a portfolio. I can totally understand a solution...