You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can't publish a 3.4.1 release until Eigen upstream itself releases it, as it is confusing for users if we make up releases and as otherwise what we will do when 3.4.1 is actually tagged?
If the fix for the crash can be backported to 3.4.0, probably it can make sense to backport the fix to 3.4.0 .
Solution to issue cannot be found in the documentation.
Issue
On the
eigen
project, on branch3.4
, a commit for an update to version 3.4.1 was pushed, but this release was not tagged: https://gitlab.com/libeigen/eigen/-/commit/bae907b8f6078b1df290729eef946360315bd312This release fixes a crash from this issue: https://gitlab.com/libeigen/eigen/-/merge_requests/1318
The recipe should be updated so this sha is pointed to so that the bug is fixed.
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: