Skip to content
Snippets Groups Projects
  1. Nov 17, 2018
  2. Nov 16, 2018
    • Jenkins's avatar
      i18n: automatic bump · 58da4ffa
      Jenkins authored and Adrien Béraud's avatar Adrien Béraud committed
      Change-Id: Id1ebb21f1a74bc6a49ea73319b00eeffb4790ed9
      58da4ffa
    • Philippe Gorley's avatar
      file transfer: rename duplicate files · edc60bb9
      Philippe Gorley authored and Adrien Béraud's avatar Adrien Béraud committed
      Add duplicate number after filename, but before extension, and start
      count at 1 instead of 0.
      
      Before, it would be '(0)file.jpg', now it is 'file (1).jpg'.
      
      Change-Id: I0e1f74c172c3c4a66baca8b94302ddf9f42f35d1
      edc60bb9
    • Kateryna Kostiuk's avatar
      newaccountmodel: account creation · 87a901cb
      Kateryna Kostiuk authored and Sébastien Blin's avatar Sébastien Blin committed
      
      This patch fixes next problems:
      -check profile type after adding account to accounts list and
      updating account details. Otherwise profile type is always INVALID
      -add option to create SIP account with URI, to avoid creating an entry
      with empty uri in db
      -do not save ring account with empty uri
      -set account credentials before saving configuration to save a new
      credentials in .yml
      
      Gitlab: #402
      
      Change-Id: I98b2f00d0f879930067bcbe2d305569d27ec90a2
      Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      87a901cb
  3. Nov 05, 2018
  4. Oct 31, 2018
  5. Oct 30, 2018
  6. Oct 23, 2018
  7. Oct 22, 2018
  8. Oct 12, 2018
  9. Oct 05, 2018
  10. Oct 02, 2018
  11. Oct 01, 2018
  12. Sep 28, 2018
    • Hugo Lefeuvre's avatar
      call state machine: fix SEARCHING state transition · 2e90d869
      Hugo Lefeuvre authored
      
      The call state machine expects a two step state transition: the
      daemon should first transition to a terminating state, and then to
      OVER. This is almost always the case, expect for the SEARCHING state.
      
      In fact this state is a bit special since it does not correspond to
      any well defined daemon state. In order to avoid issues resulting
      from an invalid SEARCHING -> ENDED transition, add a temporary state
      transition to TERMINATING.
      
      Change-Id: I074d9a1beba2e39ef3089733485b57311e834214
      Gitlab: #392
      Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      2e90d869
  13. Sep 27, 2018
    • Hugo Lefeuvre's avatar
      ringing timeout: implement let a message feature · fc1d0348
      Hugo Lefeuvre authored
      
      Use dedicated states to represent BUSY and PEER_BUSY daemon status.
      
      Do not emit showChatView when call ends in PEER_BUSY status. In this
      case emit newly added showLeaveMessage signal. When receiving this
      signal, the client should ask the user whether it wants to record a
      message.
      
      Continue to emit showChatView in the BUSY state.
      
      Change-Id: I03882ada77366332443b835760034c8e370d9694
      Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      fc1d0348
  14. Sep 24, 2018
  15. Sep 20, 2018
    • Hugo Lefeuvre's avatar
      call management: avoid signal duplication · 0b540bbc
      Hugo Lefeuvre authored and Andreas Traczyk's avatar Andreas Traczyk committed
      
      At the end of a call the state machine goes through several state
      changes. The daemon guarantees that we will first go through HUNGUP,
      INACTIVE, BUSY or FAILURE, and then through OVER.
      
      Currently FAILURE is considered to be the same as OVER by the LRC.
      This is wrong because FAILURE is a transitional state just like
      HUNGUP, not a final state like OVER. Because of that FAILURE should
      translate to TERMINATING and not ENDED.
      
      Also, we should always emit a signal during the first state
      transition, that is when we switch to HUNGUP, INACTIVE, BUSY or
      FAILURE, not when we switch to OVER. It is not meaningful to emit
      signals in both cases because it might result in contradictory
      actions, graphical glitches and obviously in a waste of resources.
      
      Change-Id: I2356ef133ba504555314d603a80bcebf3d112e02
      Reviewed-by: default avatarAndreas Traczyk <andreas.traczyk@savoirfairelinux.com>
      0b540bbc
    • Hugo Lefeuvre's avatar
      uri: fix broken ring infoHash support · 9470ab5f
      Hugo Lefeuvre authored and Adrien Béraud's avatar Adrien Béraud committed
      Change-Id: I0d1ce3db21ebb3e13b8fc0c6df01564fea281c0d
      Gitlab: #391
      9470ab5f
    • Allan Nordhøy's avatar
      Spelling: Id -> ID. Uid -> UID · 24f35997
      Allan Nordhøy authored
      Change-Id: I582190d3a54038b2e6bc301b1710d96ac5ab7e03
      24f35997
  16. Sep 19, 2018
  17. Sep 18, 2018
  18. Sep 15, 2018
  19. Sep 14, 2018
  20. Sep 12, 2018
    • Hugo Lefeuvre's avatar
      uri: take ProtocolHint in account in format() · a10fb62a
      Hugo Lefeuvre authored and Sébastien Blin's avatar Sébastien Blin committed
      
      20e8d7b3 unintentionally dropped ProtocolHint support in format().
      ProtocolHint is meant to improve format() output when no scheme was
      provided in the original uri. This commit addresses this issue.
      
      20e8d7b3 intentionally dropped "active defaulting" in the URI class,
      meaning that if no URI scheme was provided in the original URI and if
      the scheme couldn't be guessed by ProtocolHint then no scheme will be
      present in format()'s output. However this breaks quite a few things
      in the old LRC. This commit reintroduces active defaulting to
      URI::SchemeType::RING.
      
      Also, finish to cleanup strip() scheme detection.
      
      Change-Id: Ibc9decfb9d9f72d070302702de46d376eecf5c48
      Gitlab: #390
      Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      a10fb62a
    • Sébastien Blin's avatar
      conversationmodel: improve searchContactMethod and fix segfault · 85f03e35
      Sébastien Blin authored
      + The filter should use a regex match only if possible and a simple
      find for every queries.
      + Searching a SIP contact with a single quote should not crash!
      
      Change-Id: Ib874aebaad79ae0566f1e8ed380350153ae48e98
      Gitlab: #388
      85f03e35
  21. Sep 11, 2018
  22. Sep 10, 2018
    • Jenkins's avatar
      i18n: automatic bump · a071950d
      Jenkins authored
      Change-Id: I7553abc38b4e1c2b56a46ff4be47d739a9de7114
      a071950d
    • Hugo Lefeuvre's avatar
      conversationmodel: fix exception chain at call end · 17878722
      Hugo Lefeuvre authored and Sébastien Blin's avatar Sébastien Blin committed
      
      slotCallEnded: in our case the call is always in OVER state
      otherwise this callback wouldn't be executed. This means
      that getCallFromURI(conversation.participants[0], true)
      will always throw std::out_of_range, i.e. we don't even need
      to call getCallFromURI and can directly set callId to ""
      instead.
      
      selectConversation: in the case where callId is "" there is
      no need to call getCall() because it is going to throw
      std::out_of_range anyways. Instead we should directly call
      showChatView.
      
      Simplify if condition in getCallFromURI.
      
      Change-Id: I0ff09c02c7a846836c69e0757959a67767dabff1
      Gitlab: #385
      Reviewed-by: default avatarSebastien Blin <sebastien.blin@savoirfairelinux.com>
      17878722
  23. Sep 03, 2018
  24. Aug 30, 2018
Loading