Slicer 5.12.3 plans and fixing the macOS stable extension packages

Development
1

Yesterday we merged Slicer#9302 which worked out the cause of the issue with macOS C++ extension packages on Slicer 5.12, and which hopefully resolved the issue.

Today there’s good evidence from the nightly packages that the issue is resolved:

  • Yesterday’s MarkupsToModel: SPKC (see the large file size, indicating duplicated libraries)
  • Today’s: SPKC (much smaller!)

Time to cut Slicer 5.12.3? @lassoan @pieper @Sam_Horvath @jamesobutler ? Any other commits we should include besides 2c4c53a?

I am thinking this time I will keep the pre_release attribute as True until we test that the problem is really resolved on macOS, preventing anything from becoming available on the download page until we are ready.

2

Confirmed - MarkupsToModel and SlicerRT work for me on today’s mac build. Yes for 5.12.3 :+1:

3

Here is a signed and notarized macOS 5.12.3 package:

https://slicer-packages.kitware.com/api/v1/file/hashsum/SHA512/2076f23458936a028d3d1a91686369b5979d3373012f11db0e90c30fdb34874eec2b150da4d5225b2ac6b1bf5552795e1783e621a8ae3c39c01983593b07283a/download

It is still marked as pre-release so it is not going to be available on the download page yet.
Once we confirm the issue is really solved, I will remove the pre-release tag.

Can someone try this out on macOS and confirm that C++ extensions work?

4

I’ve installed 5.12.3 along with SegmentEditorExtraEffects which pulls in MarkupsToModel that was previously impacted. I can confirm that on restart the MarkupsToModel now loads successfully and I can use the “Surface cut” segment editor effect successfully which utilizes the MarkupsToModel logic.

image
image1877×952 282 KB

5

Yay! Taking the patch release to the finish line

6

Yes, working for me too. Thank you.