1. 04 Jan, 2021 2 commits
    • Sebastian Dröge's avatar
      Merge branch 'backport-1827-win32-fd-read-glib-2-66' into 'glib-2-66' · 55ebcf05
      Sebastian Dröge authored
      Backport !1827 “Windows: fix FD_READ condition flag still set on recoverable UDP socket errors.” to glib-2-66
      See merge request !1836
    • Marco Mastropaolo's avatar
      Windows: fix FD_READ condition flag still set on recoverable UDP socket errors. · 6900d53e
      Marco Mastropaolo authored
      Contrary to what the WSARecvFrom seem to imply, a UDP socket is perfectly recoverable and usable after a WSAECONNRESET error (and, I assume, WSAENETRESET).
      However GSocket condition has the FD_READ bit set after a UDP socket fails with WSAECONNRESET, even if no data is available on the socket anymore; this causes select calls to report the socket as readable when, in fact, it's not.
      The change resets FD_READ flag on a socket upon the above error conditions; there's no 'if' to filter between datagram and stream sockets as the change should be harmless in the case of stream sockets which are, however, very unlikely to be usable after a WSAECONNRESET.
  2. 21 Dec, 2020 3 commits
  3. 17 Dec, 2020 3 commits
  4. 13 Dec, 2020 1 commit
  5. 12 Dec, 2020 3 commits
  6. 11 Dec, 2020 2 commits
  7. 09 Dec, 2020 6 commits
  8. 29 Nov, 2020 1 commit
  9. 25 Nov, 2020 1 commit
  10. 16 Nov, 2020 1 commit
  11. 03 Nov, 2020 2 commits
    • Emmanuele Bassi's avatar
      Merge branch 'backport-1734-hidden-cache-glib-2-66' into 'glib-2-66' · e18a6a85
      Emmanuele Bassi authored
      Backport !1734 “glocalfileinfo: Use a single timeout source at a time for hidden file cache” to glib-2-66
      See merge request !1736
    • Carlos Garnacho's avatar
      glocalfileinfo: Use a single timeout source at a time for hidden file cache · 92c19ebd
      Carlos Garnacho authored
      As hidden file caches currently work, every look up on a directory caches
      its .hidden file contents, and sets a 5s timeout to prune the directory
      from the cache.
      This creates a problem for usecases like Tracker Miners, which is in the
      business of inspecting as many files as possible from as many directories
      as possible in the shortest time possible. One timeout is created for each
      directory, which possibly means gobbling thousands of entries in the hidden
      file cache. This adds as many GSources to the glib worker thread, with the
      involved CPU overhead in iterating those in its main context.
      To fix this, use a unique timeout that will keep running until the cache
      is empty. This will keep the overhead constant with many files/folders
      being queried.
  12. 28 Oct, 2020 3 commits
    • Simon McVittie's avatar
      Merge branch 'backport-1725-gdbus-fds-glib-2-66' into 'glib-2-66' · 4daaf303
      Simon McVittie authored
      Backport !1725 “gdbus: Cope with sending fds in a message that takes multiple writes” to glib-2-66
      See merge request !1727
    • Simon McVittie's avatar
      gio/tests/gdbus-peer: Exercise fds attached to a large message · 60c3c948
      Simon McVittie authored
      This incidentally also exercises the intended pattern for sending fds in
      a D-Bus message: the fd list is meant to contain exactly those fds that
      are referenced by a handle (type 'h') in the body of the message, with
      numeric handle value n corresponding to g_unix_fd_list_peek_fds(...)[n].
      Being able to send and receive file descriptors that are not referenced by
      a handle (as in OpenFile here) is a quirk of the GDBus API, and while it's
      entirely possible in the wire protocol, other D-Bus implementations like
      libdbus and sd-bus typically don't provide APIs that make this possible.
      Reproduces: #2074
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
    • Simon McVittie's avatar
      gdbus: Cope with sending fds in a message that takes multiple writes · 40cd84d9
      Simon McVittie authored
      Suppose we are sending a 5K message with fds (so data->blob points
      to 5K of data, data->blob_size is 5K, and fd_list is non-null), but
      the kernel is only accepting up to 4K with each sendmsg().
      The first time we get into write_message_continue_writing(),
      data->total_written will be 0. We will try to write the entire message,
      plus the attached file descriptors; or if the stream doesn't support
      fd-passing (not a socket), we need to fail with
      "Tried sending a file descriptor on unsupported stream".
      Because the kernel didn't accept the entire message, we come back in.
      This time, we won't enter the Unix-specific block that involves sending
      fds, because now data->total_written is 4K, and it would be wrong to try
      to attach the same fds again. However, we also need to avoid failing
      with "Tried sending a file descriptor on unsupported stream" in this
      case. We just want to write out the data of the rest of the message,
      starting from (blob + total_written) (in this exaple, the last 1K).
      Resolves: #2074
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
  13. 27 Oct, 2020 2 commits
    • Emmanuele Bassi's avatar
      Merge branch 'backport-1711-socket-fix-glib-2-66' into 'glib-2-66' · cfbab734
      Emmanuele Bassi authored
      Backport !1711 “Fix race in socketclient-slow test” to glib-2-66
      See merge request !1723
    • Michael Catanzaro's avatar
      Fix race in socketclient-slow test · 832d09ad
      Michael Catanzaro authored
      This test ensures that g_socket_client_connect_to_host_async() fails if
      it is cancelled, but it's not cancelled until after 1 millisecond. Our
      CI testers are hitting that race window, and Milan is able to reproduce
      the crash locally as well. Switching it from 1ms to 0ms is enough for
      Milan to avoid the crash, but not enough for our CI, so let's move the
      cancellation to a GSocketClientEvent callback where the timing is
      completely deterministic.
      Hopefully fixes #2221
  14. 26 Oct, 2020 2 commits
    • Philip Withnall's avatar
      Merge branch 'backport-1713-main-context-check-glib-2-66' into 'glib-2-66' · 614d4094
      Philip Withnall authored
      Backport !1713 “gmain: g_main_context_check() can skip updating polled FD sources” to glib-2-66
      See merge request !1721
    • Claudio Saavedra's avatar
      gmain: g_main_context_check() can skip updating polled FD sources · fa45688f
      Claudio Saavedra authored
      If there is a file descriptor source that has a lower priority
      than the one for sources that are going to be dispatched,
      all subsequent file descriptor sources (internally sorted by
      file descriptor identifier) do not get an update in their GPollRec
      and later on wrong sources can be dispatched.
      Fix this by first finding the first GPollRec that matches the current
      GPollFD, instead of relying on it to be the current one. At
      the same time, document the assumptions about the ordering of the
      file descriptor records and array and make explicit in the documentation
      that the array needs to be passed to g_main_context_check() as it was
      received from g_main_context_query().
      Added a new test that reproduces the bug by creating two file
      descriptor sources and an idle one. Since the first
      file descriptor created has a lower identifier and a low priority,
      the second one is not dispatched even when it has the same, higher,
      priority as the idle source. After fixing this bug, both
      higher priority sources are dispatched as expected.
      While this patch was written independently, a similar fix for this
      bug was first submitted by Eugene M in !562. Having a
      second fix that basically does the same is a reassurance that we
      are in the right here.
      Fixes #1592
  15. 23 Oct, 2020 2 commits
  16. 19 Oct, 2020 4 commits
  17. 16 Oct, 2020 2 commits
    • LRN's avatar
      Fix the 6-days-until-the-end-of-the-month bug · 807e4fdc
      LRN authored
      The addition causes the date to shift
      forward into 1st of the next month, because a 0-based offset
      is compared to be "more than" the days in the month instead of "more than
      or equal to".
      This is triggered by corner-cases where transition date is 6 days
      off the end of the month and our calculations put it at N+1th day of the
      month (where N is the number of days in the month). The subtraction should
      be triggered to move the date back a week, putting it 6 days off the end;
      for example, October 25 for CET DST transition; but due to incorrect comparison
      the date isn't shifted back, we add 31 days to October 1st and end up
      at November 1st).
      Fixes issue #2215.
    • LRN's avatar
      Add a test for the 6-days-until-EOM bug · 3a0e7744
      LRN authored