Also see 2f8f685 😉

@ischoegl Can you clarify if that is part of a particular PR or is it merged to master? If merged to master, why is #804 still open? Thanks

@bryanwweber ... the commit I referenced is part of #805, which is awaiting review. I stumbled across this while working on #805 and submitted an issue then.

I don't have a problem with @sin-ha's resolution, as it is virtually identical (#805 does depend on slicable SolutionArrays though, so the fix should be applied first in whichever way).

hey, @ischoegl @bryanwweber I am eager to work on related problems can you guide me? on #805

@sin-ha ... pull request #805 is currently awaiting review by one of the developers, so there's nothing to do there apart from reviewing.

For things to work on, the issue tracker is a good start. Look for open issues that do not have a linked pull request yet (you should see an icon on the overview; linked pull requests contain proposed fixes). You probably already read through the contributor's guide.

Codecov Report

Merging #816 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #816   +/-   ##
=======================================
  Coverage   71.39%   71.39%           
=======================================
  Files         372      372           
  Lines       43482    43482           
=======================================
  Hits        31045    31045           
  Misses      12437    12437           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 24599b8...678a432. Read the comment docs.