Workaround!!!
Here I am again.
I found a workaround for the PipeableOSProcess and the Big Sur update. It is
the usage of LibC, I was not aware of that class, it's useful.
I was able to reproduce my logic with LibC, this article
(https://fuhrmanator.github.io/2019/03/16/LibC-Pharo-experiments.htm
Hi Stephane
> On Saturday, February 5, 2022, 10:58:37 AM GMT+1, stephane.duca...@free.fr
> wrote:
>Hi david
>
>Can you tell us on which version of os-x you are?
I'm on Big Sur, see my original message:
https://www.mail-archive.com/pharo-users@lists.pharo.org/msg40530.html
And the
Hi David,
I do not think I can help, maybe someone with Big Sur can take a look?
I am on Linux. I did a fresh download of Pharo 8 and loaded OSProcess,
and I cannot reproduce the problem on my system.
Dave
On Fri, Feb 04, 2022 at 03:54:57PM +, Davide Varvello via Pharo-users wrote:
> Hi D
Hi David,I don't think is an issue of warning, even if I apply your patch I
have the same error, see: https://imgur.com/a/pYcLLWx
To reproduce the bug: Be on Big Sur 11.6.3 (20G415)
https://support.apple.com/en-us/HT213055Download Pharo 8: curl
https://get.pharo.org/64/80+vm|bash
Open the i
Hi Davide,
Actually the warning has been removed in newer versions of OSProcess.
I do not have time to do an update for Pharo now, but in the mean time
you can apply this change in your image to remove the notifier:
AioEventHandler>>initializeForExceptions: exceptionEventFlag readEvents:
readEve
Hi David,That's weird because if the AioPlugin is not present in my VM,
PipeableOSProcess shouldn't have worked till this morning... when I upgraded my
mac :-)
The warning is not skippable, it stops me at: MessageNotUnderstood: IRJump>>
#nextBytecodeOffsetAfterJumpCheersDavide
On Friday, F
On Fri, Feb 04, 2022 at 01:46:46PM +, Davide Varvello via Pharo-users wrote:
> Hi guys,
> Suddenly evaluating a simple: (PipeableOSProcess command: 'ps') output, or
> any other PipeableOSProcess command, Pharo gives me: "aio event forwarding
> not supported".
> I guess it is something related
