Re: "nw_endpoint_handler_set_adaptive…" coming from XPC service

2021-05-27 Thread Dragan Milić via Cocoa-dev
On 27 May 2021, at 20:48, Jens Alfke wrote:

>> On May 27, 2021, at 11:17 AM, Dragan Milić via Cocoa-dev 
>>  wrote:
>> 
>> I’ve got an application, which uses (a couple of) XPC service(s) to 
>> accomplish various tasks. Since recently, I don’t know when exactly but 
>> probably after some macOS update, I started seeing these messages coming out 
>> when XPC services are used:
>> 
>> [connection] nw_endpoint_handler_set_adaptive_read_handler [C1.1 
>> 140.82.121.6:443 ready socket-flow (satisfied (Path is satisfied), viable, 
>> interface: en1, ipv4, dns)] unregister notification for read_timeout failed
> 
> If your app works and isn't getting errors back through the API, then this is 
> probably just some internal logging used by Apple. There's a lot of that 
> stuff. It can be annoying to have it interspersed in your own logs, but I 
> don't think there's anything you can do about it.

Yeah, I assumed that as well, but since it's started happening recently and it 
annoys me, I thought there may be something I can do. Ah well…

-- Dragan
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: "nw_endpoint_handler_set_adaptive…" coming from XPC service

2021-05-27 Thread Jens Alfke via Cocoa-dev


> On May 27, 2021, at 11:17 AM, Dragan Milić via Cocoa-dev 
>  wrote:
> 
> I’ve got an application, which uses (a couple of) XPC service(s) to 
> accomplish various tasks. Since recently, I don’t know when exactly but 
> probably after some macOS update, I started seeing these messages coming out 
> when XPC services are used:
> 
> [connection] nw_endpoint_handler_set_adaptive_read_handler [C1.1 
> 140.82.121.6:443 ready socket-flow (satisfied (Path is satisfied), viable, 
> interface: en1, ipv4, dns)] unregister notification for read_timeout failed

If your app works and isn't getting errors back through the API, then this is 
probably just some internal logging used by Apple. There's a lot of that stuff. 
It can be annoying to have it interspersed in your own logs, but I don't think 
there's anything you can do about it.

—Jens
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


"nw_endpoint_handler_set_adaptive…" coming from XPC service

2021-05-27 Thread Dragan Milić via Cocoa-dev
Hi all,

I’ve got an application, which uses (a couple of) XPC service(s) to accomplish 
various tasks. Since recently, I don’t know when exactly but probably after 
some macOS update, I started seeing these messages coming out when XPC services 
are used:

[connection] nw_endpoint_handler_set_adaptive_read_handler [C1.1 
140.82.121.6:443 ready socket-flow (satisfied (Path is satisfied), viable, 
interface: en1, ipv4, dns)] unregister notification for read_timeout failed

or

[connection] nw_endpoint_handler_set_adaptive_write_handler [C1.1 
140.82.121.6:443 ready socket-flow (satisfied (Path is satisfied), viable, 
interface: en1, ipv4, dns)] unregister notification for write_timeout failed

This happens when the service want’s to use outgoing connection. Not that it 
only happens in Xcode during debugging, but the deployment version of the 
application/XPC emits these messages to the console as well. However, 
everything works correctly as it has before. I’d like to surpass those messages 
going into the console, but I’d also like to understand what they actually mean 
and why they appear in the first place. Searching the Internet didn’t really 
revealed any useful info, so I hope someone here can help me. Anyone else 
seeing those?

-- Dragan
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com