Chris Talkington

should have a fix soon. was issue with fixing a bug in pyipp 0.12 that then exposed not all checked attributes were not being requested properly

@nielsvanvelzen so with recent changes, there should be a persistent client device id sent from config flow setup through to actual integration config entry coordinators. This is persistent per config...

@nielsvanvelzen also I did have a related question for you, with the jellyfin SupportsPersistentIdentifier device capability. Am I correct in that most the official clients don't support this because they...

hum did node change the buffer api again? I haven't read up on 16 but if it's not a documented breaking change it may be worth seeing if it's a...

likely a zip64 issue but its trickier to test. some builtin zip tools don't support zip64 as well.

it does look like we should be setting a different min version to extract here. working through some other compatibility fixes in node-compress-commons. would love to have you test once...

do you have example code? It could be the glob change since its more or less reading fs as needed vs huge swaths at a time.

hum have you tried using the built in `file` helper? I believe it should catch the error internally. It also has lazy reading of streams for performance in turns of...

you know, what point does the access error fire? I'm wondering if it's on creation of stream or the actual pipe. As we have code that listens and bubbles up...

thanks for the suggestion! I have been wanting to go more modern and i think weve finally got our minimum required version to a place we can start exploring such