sl silently fails on macosx if python3.11 is used

[mhlakhani]

I installed sapling from the website (on an apple silicon mac) following the instructions on the website: https://sapling-scm.com/docs/introduction/installation (I tried both brew install sapling and the prebuilt bottles instructions)

Expected behavior: Commands work fine Actual behavior: Running any sl command (even --help) just silently exits with a nonzero exit code, and there's no way to debug what's wrong.

I suspect https://github.com/facebook/sapling/issues/714 might share a root cause, but that focuses on installation from source, while my complaint is on the behavior at runtime following the official instructions on the site

[quark-zju]

Sorry for the late response. If you were able to reproduce, could you share the output of:

CHGDISABLE=1 CHGDEBUG=1 SAPLING_LOG=debug sl version
echo $?

?

[ahupp]

If I see it again I'll give that a try, but I'm not sure what made it happen in the first place.

[mhlakhani]

@quark-zju : It went away for me after a reboot.

It's been a bit so my memory is fuzzy but I do remember working on and doing a brew install pytorch around that time which might have installed a different version of python which could have conflicted. Uninstalling that, and reinstalling sapling/the right python version at that time didn't work but a reboot did

[alex-statsig]

@quark-zju : It went away for me after a reboot.

It's been a bit so my memory is fuzzy but I do remember working on and doing a brew install pytorch around that time which might have installed a different version of python which could have conflicted. Uninstalling that, and reinstalling sapling/the right python version at that time didn't work but a reboot did

Possibly the same issue as https://github.com/facebook/sapling/issues/659 in that case

[uhthomas]

@quark-zju

❯ CHGDISABLE=1 CHGDEBUG=1 SAPLING_LOG=debug sl version
using chg: false, because CHGDISABLE=1
Sapling 0.2.20230523-092610+f12b7eee
❯ echo $?
0

❯ python3 --version
Python 3.11.5

[uhthomas]

A system reboot fixed it, as observed by others.