1. 02 May, 2020 7 commits
  2. 01 May, 2020 4 commits
  3. 06 Apr, 2020 2 commits
  4. 04 Apr, 2020 10 commits
  5. 29 Mar, 2020 4 commits
    • Maxime Buquet's avatar
      Merge branch 'fix-0198' into 'master' · a16e2a0f
      Maxime Buquet authored
      XEP-0198: unset end_session_on_disconnect on resume/enable
      See merge request poezio/slixmpp!36
    • Maxime Buquet's avatar
      Merge branch 'fix-reconnect-2.0' into 'master' · 842aa3be
      Maxime Buquet authored
      Reset reconnect delay on manual reconnect, add delay event
      See merge request poezio/slixmpp!35
    • ge0rg's avatar
    • ge0rg's avatar
      Reset reconnect delay on manual reconnect, add delay event · 62125502
      ge0rg authored
      This is just a hotfix workaround for an underlying problem. The
      `_connect_routine` code is "blocking" (in an async way) for
      `connect_loop_wait` seconds, so that a fresh-started manual reconnect
      will be silenty delayed. This code does the following changes:
      1. It moves the delay to before the DNS resolution (with the exponential
         back-off it might well be that the DNS records are changed while
         slixmpp is waiting).
      2. It adds a new event `reconnect_delay` that gets passed the number of
         seconds it will delay before actually reconnecting
      3. It resets the `connect_loop_wait` timer on a manual connect/reconnect
         call to fix the interactive experience.
      A *proper fix* would replace the sleep in `_connect_routine` with a
      properly timered re-invocation of it, but I don't understand enough of
      asyncio for pulling off that magic, and this is actually a proper
      improvement. Also I tested this and it works!
  6. 28 Mar, 2020 5 commits
  7. 23 Mar, 2020 1 commit
    • ge0rg's avatar
      reconnect: fix callback when not currently connected · d85efec7
      ge0rg authored
      The 'disconnected' event is normally fired from connection_lost(), which
      is called by the connection code when the connection is lost after being
      established. However, if the connection wasn't successfully established,
      a manual /reconnect no-ops because it waits for the 'disconnected'
      callback which never fires. This patch does two things:
      1. Immediately fire a 'disconnected' event in disconnect() if there is
         no transport.
      2. Register the 'disconnected' event handler in reconnect() *before* it
         can be fired.
  8. 27 Dec, 2019 7 commits