basak
basak
> I have temporarily fixed this by applying the following patch: This worked for me. Thank you! I have a Google Calendar with entries from 2011 through 2024 that wouldn't...
Sorry for the delay in responding. I've been away. This works now, using `Faikin-S3-MINI-N4-R2: 90143f3 2024-05-18T08:45:12 S21`. Thank you!
> tldr: As architected right now, the hotplugd.socket will be active after cloud-init.service has finished, enqueueing udev hotplug events, hotplugd.service will process the events, one at the time, after cloud-final.service...
> and hotplugd.service has started nor hotplugd.socket, for that matter.
On Fri, Apr 09, 2021 at 07:44:15AM -0700, Nathaniel J. Smith wrote: > If you put the nursery into a fixture, then you're scoping the entire test to run inside...
> I've never found it to onerous to write async with open_nursery() as nursery: inside my tests when I wanted a more narrowly scoped nursery... it's only one line :-)...
That works for me too. Thanks!
FWIW, I packaged this for myself locally, and overrode the tests to not test at all to work around this for now.
> I packaged this for myself locally (for Debian/Ubuntu, not Gentoo)
BTW, the error checking of `atol` is also non-functional. `atol` returns 0 on error, not -1, and setting `syspids` to -1 in the previous line is redundant as the `atol`...