Re: [Alphacocoa-devel] Package activation error

[Laurent L. <Lau...@un...>]

Hi Bernard,


> On 31 May 2021, at 17:35, Bernard Desgraupes <bde...@or...> wrote:
> 
> Hi Laurent,
> 
> thank you for the input.
> 
>> The port 51954 is not busy on my laptop: the « netstat… » command filtered by « | grep 51954 » returns nothing.
>> When I remove the filter, the listed ports do not contain 51954.
>> When I start Alpha and repeat the « netstat… » command, the port 60235 appears in the list, associated with …/Alpha.app/…/Alpha . From Alpha, alphaServer::port logically lists the same port.
>> 
>> (Note that when I launch Alpha from Spotlight search, I cannot switch from Terminal to Alpha by command-tab: I need to click the Alpha Icon in the Dock to get within Alpha, where I can then for instance open a Tcl shell window by command-Y. Once a window is open in Alpha, I can switch between Alpha and Terminal by command-tab.)
>> 
> 
> It is very strange that port 51954 is not busy and still Alpha fails to connect to it. Out of curiosity, could you try the following command (in the Tcl shell)  once Alpha is running (using any port it chose):
>    socket -server ::alphaServer::handleConnect -myaddr 127.0.0.1 51954
> 
> Does it fail ? 

No, it does not: sock7fe53e44c610 is returned.

(while using in that command the port number listed by alphaServer::port returns Error: couldn’t open socket: address already in use).

> Anyway, any port should do (there is absolutely nothing special with 51954).
> 
> Finally, there is no harm using the workaround I indicated and I modified the code in Alpha to implement something equivalent in the future version of Alpha.

What I does not understand is that I did not observe that behaviour « time ago » and have no idea what change in my macOS settings could have triggered that « new » behaviour of Alpha…

Thank you very much again for the quick support!

Laurent

> 
> Cheers,
> Bernard
> 
>