Re: radicale broken in 7.8 due to py3-bcrypt changes

On July 28, 2026 18:55:36 GMT+02:00, Stuart Henderson <[email protected]> wrote:
>On 2026/07/28 16:55, Lydia Sobot wrote:
>> On July 23, 2026 8:00:04 GMT+02:00, [email protected] wrote:
>> >Same on amd64:
>> >
>> >=================================== FAILURES ===================================
>> >_ PollPollerSocketEventsTestCase.test_which_events_are_set_after_local_shuts_rdwr _
>> >tests/unit/select_connection_ioloop_tests.py:1040: in test_which_events_are_set_after_local_shuts_rdwr
>> >    self.which_events_are_set_with_varying_eventmasks(
>> >tests/unit/select_connection_ioloop_tests.py:834: in which_events_are_set_with_varying_eventmasks
>> >    ioloop.start()
>> >pika/adapters/select_connection.py:583: in start
>> >    self._poller.start()
>> >pika/adapters/select_connection.py:845: in start
>> >    self.poll()
>> >pika/adapters/select_connection.py:1259: in poll
>> >    self._dispatch_fd_events(fd_event_map)
>> >pika/adapters/select_connection.py:947: in _dispatch_fd_events
>> >    handler(fileno, events)
>> >tests/unit/select_connection_ioloop_tests.py:819: in handle_socket_events
>> >    self.assertTrue(
>> >E   AssertionError: 0 is not true : watching=12: Out.Err.; indicated=16: Hup.
>> >----------------------------- Captured stderr call -----------------------------
>> >[PollPoller] @ Local shut RDWR: watching=13: In.Out.Err.; indicated=17: In.Hup.; sockerr=0
>> >[PollPoller] @ Local shut RDWR: watching=5: In.Out.; indicated=17: In.Hup.; sockerr=0
>> >[PollPoller] @ Local shut RDWR: watching=1: In.; indicated=17: In.Hup.; sockerr=0
>> >[PollPoller] @ Local shut RDWR: watching=12: Out.Err.; indicated=16: Hup.; sockerr=0
>> >_ PollPollerSocketEventsTestCase.test_which_events_are_set_when_failed_to_connect _
>> >tests/unit/select_connection_ioloop_tests.py:866: in test_which_events_are_set_when_failed_to_connect
>> >    self.which_events_are_set_with_varying_eventmasks(
>> >tests/unit/select_connection_ioloop_tests.py:834: in which_events_are_set_with_varying_eventmasks
>> >    ioloop.start()
>> >pika/adapters/select_connection.py:583: in start
>> >    self._poller.start()
>> >pika/adapters/select_connection.py:845: in start
>> >    self.poll()
>> >pika/adapters/select_connection.py:1259: in poll
>> >    self._dispatch_fd_events(fd_event_map)
>> >pika/adapters/select_connection.py:947: in _dispatch_fd_events
>> >    handler(fileno, events)
>> >tests/unit/select_connection_ioloop_tests.py:819: in handle_socket_events
>> >    self.assertTrue(
>> >E   AssertionError: 0 is not true : watching=12: Out.Err.; indicated=16: Hup.
>> >----------------------------- Captured stderr call -----------------------------
>> >[PollPoller] @ Failed to connect: watching=13: In.Out.Err.; indicated=17: In.Hup.; sockerr=61 (Connection refused)
>> >[PollPoller] @ Failed to connect: watching=5: In.Out.; indicated=17: In.Hup.; sockerr=0
>> >[PollPoller] @ Failed to connect: watching=1: In.; indicated=17: In.Hup.; sockerr=0
>> >[PollPoller] @ Failed to connect: watching=12: Out.Err.; indicated=16: Hup.; sockerr=0
>> >=========================== short test summary info ============================
>> >FAILED tests/unit/select_connection_ioloop_tests.py::PollPollerSocketEventsTestCase::test_which_events_are_set_after_local_shuts_rdwr
>> >FAILED tests/unit/select_connection_ioloop_tests.py::PollPollerSocketEventsTestCase::test_which_events_are_set_when_failed_to_connect
>> >============= 2 failed, 592 passed, 18 skipped in 78.69s (0:01:18) =============
>> >--
>> >
>> >Ran twice.
>> >
>> >Is that expected?
>> No idea, anyone?
>
>*shrug* it's your port, I just enabled the tests...
Understood, however I to be honest just ported it over because it became a dependency, I have no use for its features nor do I know anything about MQTT, but I didn't notice any operational issues when running Radicale whatsoever