Re: [sc-users] 'Host not found' after OS upgrade

[Scott Wilson <i@xxxxxxxxxxxxxx>]

I have an idea about this, but I don't see it myself. Can either of you suggest a reproducer?

S.

On 26 Dec 2013, at 21:47, adc <alberto.decampo@xxxxxxxxx> wrote:

> Hi, 
> 
> I am seeing this on OSX 10.8.5 as well, so it is not linux specific. 
> Logging out and logging back in seems to help, but it keeps coming 
> back after several recompiles. 
> 
> I tried overwriting the NetAddr:isLocal like this: 
> 
> 	*matchLangIP { |ipstring|
> 		^ipstring == "127.0.0.1";
> 	}
> 
> 	// *matchLangIP {|ipstring|
> 	// 	_MatchLangIP
> 	// }
> 
> but strangely, I still get the same error. 
> 
> best, adc
> 
> 
> On 26/12/2013, at 19:32 , Phil Thomson <supercollider@xxxxxxxxxxxxxx> wrote:
> 
>> On Wed, 25 Dec 2013 08:45:45 +0800
>> James Harkins <jamshark70@xxxxxxxxx> wrote:
>> 
>>> On Dec 25, 2013 4:12 AM, "Phil Thomson" <supercollider@xxxxxxxxxxxxxx>
>>> wrote:
>>>> compile done
>>>> resolve: Host not found (authoritative)
>>>> ERROR: Non Boolean in test.
>>>> RECEIVER:
>>>> class NetAddr (0x39fe700) {
>>> 
>>> I don't know the solution, but I think this is what's happening.
>>> 
>>> The test that's failing is here, in Server:
>>> 
>>>  newScopeBufferAllocators {
>>>               if (isLocal)
>>> 
>>> The isLocal variable gets set in Server's init method: "isLocal =
>>> inProcess || { addr.isLocal };" which leads to NetAddr:
>>> 
>>> isLocal { ^this.class.matchLangIP(this.ip) }
>>> 
>>>       *matchLangIP {|ipstring|
>>>               _MatchLangIP
>>>       }
>>> 
>>> This primitive should return a boolean or throw a descriptive error,
>>> but instead, under this rare case, it simply returns the class
>>> itself, which is how NetAddr got into the "if" test.
>>> 
>>> If the SC code were fixed, though, you'd still have the "Host not
>>> found" problem, which depends on something in the OS. I'm afraid I
>>> haven't much time to look into that today, but I'm quite sure you'll
>>> have other problems with SC (maybe with networking in general)
>>> without dealing with this issue (and I don't believe it's an SC
>>> configuration problem).
>>> 
>>> hjh
>> 
>> Not sure what my next step is. Should I contact the CCRMA folks? Is
>> this an OS bug?
>> 
>> _______________________________________________
>> sc-users mailing list
>> 
>> info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
>> archive: https://listarc.bham.ac.uk/marchives/sc-users/
>> search: https://listarc.bham.ac.uk/lists/sc-users/search/
> 
> 
> _______________________________________________
> sc-users mailing list
> 
> info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
> archive: https://listarc.bham.ac.uk/marchives/sc-users/
> search: https://listarc.bham.ac.uk/lists/sc-users/search/


_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/