savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2024-03-28T00:05:08Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/959Call-Swarm/Rdv: wrong audio is attached2024-03-28T00:05:08ZSébastien BlinCall-Swarm/Rdv: wrong audio is attached# Scenario
+ In a call swarm (alice is the host), bob calls
+ Alice is detached, but audio is playing
# Expected
Alice should not ear anything, Bob should not ear alice# Scenario
+ In a call swarm (alice is the host), bob calls
+ Alice is detached, but audio is playing
# Expected
Alice should not ear anything, Bob should not ear alicehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/953Call Swarm: full pass2024-03-28T00:05:08ZSébastien BlinCall Swarm: full pass# TODO
+ Check performance
+ Check call ending announcement
+ Check support on all platforms
+ Fallback
+ ask for hosts
+ audio binding
+ test with 8 devices
+ Performance# TODO
+ Check performance
+ Check call ending announcement
+ Check support on all platforms
+ Fallback
+ ask for hosts
+ audio binding
+ test with 8 devices
+ PerformanceSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/958Call-swarm: Joining in audio make the host join2024-03-25T18:36:16ZSébastien BlinCall-swarm: Joining in audio make the host join# Scenario
* Alice, Bob in a swarm
* Alice is default host
* Bob joins in audio
# Expected
Alice doesn't join the call
# Current
Alice is attached# Scenario
* Alice, Bob in a swarm
* Alice is default host
* Bob joins in audio
# Expected
Alice doesn't join the call
# Current
Alice is attachedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1493Add option Kick and kick and block2024-03-24T20:41:43ZElysAdd option Kick and kick and blockall supported OS:
I would like to have option to
either
- (only) kick a participant
or
- kick **AND block** a participant (at the same time) (so that the participant can't joint again or call me again)
maybe we should also name this ...all supported OS:
I would like to have option to
either
- (only) kick a participant
or
- kick **AND block** a participant (at the same time) (so that the participant can't joint again or call me again)
maybe we should also name this option "(Permanent) ban" and if you tap the button you'll see a display text like "This will make it impossible that this contact can reach you anymore (text messaging and all call types) until you manually unblock the contact"
I would like to have these option if I'm in conference and/or as soon as (Multi-)Swarm-Calls will be available.
Not sure if it makes sense for 1:1 calls and/or 1:1 chat.
If these option are already available we can close.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/931Message cannot be sent2024-03-23T15:49:25Zsession 21Message cannot be sentI have two accounts, one logged in on my computer and the other on my phone. After logging in to my computer for more than a period of time, my phone starts the software, and then my computer cannot receive messages sent by my phone.
Mo...I have two accounts, one logged in on my computer and the other on my phone. After logging in to my computer for more than a period of time, my phone starts the software, and then my computer cannot receive messages sent by my phone.
Mobile version: 379 (376)
Equipment model: Samsung s20+5g
Android 12
Computer version: 202307111203
Win 10 (22H2)
I think I have reproduced this error. On September 16th, when I was in version 376, I encountered this error and it reappeared tonight. I give these two examples because I have the Jami logs on my phone during these two errors.
In the previous time, I encountered this error at least ten times, but it was all between computers, and the computer's records were not complete. I hoped to - d start, but this error will not reappear after restarting.
**The important thing is that this error may not occur until the computer's client is started for an hour (if that happens, the log will be large, so I did not attempt to record the log on the computer)**
**Actual result: My computer cannot receive any messages.**
**Expected results: Message transmission should be normal.**
**Public network dynamic ipv6 is working normally.**
Yesterday, I thought it might be an issue with the Android version being too low, so I didn't provide any feedback on this issue because I heard from a friend that Jami seemed to have fixed an error that could cause abnormal messages.
However, today I encountered this problem again.
And I have two days of logs, so I decided to upload it.
[log0.log](/uploads/2d1ef596bfeabf76eaaabb538c4a15a5/log0.log)
[log1.log](/uploads/240c35be47e58df87db612c0930256a2/log1.log)
In the two logs, there is a description of "message sent successfully", but in reality it is not.
In the second log paragraph, it was not until my account received a message from the computer that both parties' information reception and transmission resumed normal.
The reason for returning to normal is that I performed the "close account and then re enable account" operation on my computer.
During this period, the abnormal state of the message lasted for 20 minutes.
**I can't find how to upload the file, so if there is any sensitive information, could you please help me cover it up.**
**Thank you. I admire your hard work.**Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1579Call-Swarm: Host popup appears twice2024-02-29T14:12:14ZSébastien BlinCall-Swarm: Host popup appears twice# Scenario
* Alice, Bob in a swarm
* Alice default hosts
* Bob calls Alice
* Alice answers then kill jami
# Current result
* Bob calls will stop and the host popup appears twice
# Expected
* Popup should appears only once# Scenario
* Alice, Bob in a swarm
* Alice default hosts
* Bob calls Alice
* Alice answers then kill jami
# Current result
* Bob calls will stop and the host popup appears twice
# Expected
* Popup should appears only onceSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1461Swarm-call: meta2024-02-27T14:50:25ZSébastien BlinSwarm-call: meta# To test
+ Check that call message is updating if call is current or not
+ Check join in audio/video
+ Check all buttons if the action is correct (join call or launch new call on the host)
# TODO
+ getActiveCalls() to retrieve curren...# To test
+ Check that call message is updating if call is current or not
+ Check join in audio/video
+ Check all buttons if the action is correct (join call or launch new call on the host)
# TODO
+ getActiveCalls() to retrieve current active calls when opening Jami
+ Show in smartlist a visual indication that a call is in progress?
+ Check text (should be homogeneous with client-qt) for banner and join call messages
+ Ability to change current host in the settings (and show current host)
+ Fallback to be the default host if call fails (https://docs.jami.net/developer/calls-in-swarm.html)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/957Call-swarm: join in audio fails2024-02-26T20:30:19ZSébastien BlinCall-swarm: join in audio fails# Scenario
* Alice, Bob, Carla in a swarm
* Alice is default host
* Bob call in audio
* Carla calls (audio or video)
# Expected result
Carla should ear Bob
# Current result
No sound# Scenario
* Alice, Bob, Carla in a swarm
* Alice is default host
* Bob call in audio
* Carla calls (audio or video)
# Expected result
Carla should ear Bob
# Current result
No soundhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/948Improve AccountStatusMessage synchronization2024-02-23T13:52:34ZSébastien BlinImprove AccountStatusMessage synchronization# Problems
On current master:
+ when you send a message, the message is marked as SENT as soon as one device got the messages
+ state is not kept after a reboot
+ if we say that a message is sent as soon as one other member get the mess...# Problems
On current master:
+ when you send a message, the message is marked as SENT as soon as one device got the messages
+ state is not kept after a reboot
+ if we say that a message is sent as soon as one other member get the message, this must take into account the fact that Jami is distributed and the contact may fetch the message from another device, so this information MUST be synced
+ status wasn't designed for swarm until nowSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1378Message cannot be sent2024-02-14T15:43:53Zsession 21Message cannot be sentI have two accounts, one logged in on my computer and the other on my phone. After logging in to my computer for more than a period of time, my phone starts the software, and then my computer cannot receive messages sent by my phone.
Mo...I have two accounts, one logged in on my computer and the other on my phone. After logging in to my computer for more than a period of time, my phone starts the software, and then my computer cannot receive messages sent by my phone.
Mobile version: 379 (376)
Equipment model: Samsung s20+5g
Android 12
Computer version: 202307111203
Win 10 (22H2)
I think I have reproduced this error. On September 16th, when I was in version 376, I encountered this error and it reappeared tonight. I give these two examples because I have the Jami logs on my phone during these two errors.
In the previous time, I encountered this error at least ten times, but it was all between computers, and the computer's records were not complete. I hoped to - d start, but this error will not reappear after restarting.
**The important thing is that this error may not occur until the computer's client is started for an hour (if that happens, the log will be large, so I did not attempt to record the log on the computer)**
**Actual result: My computer cannot receive any messages.**
**Expected results: Message transmission should be normal.**
**Public network dynamic ipv6 is working normally.**
Yesterday, I thought it might be an issue with the Android version being too low, so I didn't provide any feedback on this issue because I heard from a friend that Jami seemed to have fixed an error that could cause abnormal messages.
However, today I encountered this problem again.
And I have two days of logs, so I decided to upload it.
[log0.log](/uploads/1b5a914986eedff40e514fd962dab3aa/log0.log)
[log1.log](/uploads/7059a3a393a8998e853a1066d07b73d3/log1.log)
In the two logs, there is a description of "message sent successfully", but in reality it is not.
In the second log paragraph, it was not until my account received a message from the computer that both parties' information reception and transmission resumed normal.
The reason for returning to normal is that I performed the "close account and then re enable account" operation on my computer.
During this period, the abnormal state of the message lasted for 20 minutes.
**I can't find how to upload the file, so if there is any sensitive information, could you please help me cover it up.**
**Thank you. I admire your hard work.**https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/311Swarm-history: Use history loaded by daemon2024-01-29T19:26:40ZSébastien BlinSwarm-history: Use history loaded by daemonhttps://review.jami.net/q/topic:swarm-history
# TODO
+ Use `loadConversation` instead of `loadConversationMessages`
+ Use `SwarmLoaded` instead of `conversationLoaded`
+ This gives the following structure:
```
struct SwarmMessage
{
...https://review.jami.net/q/topic:swarm-history
# TODO
+ Use `loadConversation` instead of `loadConversationMessages`
+ Use `SwarmLoaded` instead of `conversationLoaded`
+ This gives the following structure:
```
struct SwarmMessage
{
std::string id;
std::string type;
std::string linearizedParent;
std::map<std::string, std::string> body;
std::vector<std::map<std::string, std::string>> reactions;
std::vector<std::map<std::string, std::string>> editions;
};
```
Containing the reactions, editions (previous bodies) directly inside the message
+ Remove custom logic to linearize the history, filter merge messages (they are removed by the daemon), build reaction/editions
+ Use new signals `SwarmMessageReceived`, `SwarmMessageUpdated` (if edited, deleted or parent changes), `ReactionAdded`, `ReactionRemoved` to update the view/reactionshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1494Swarm-history: Use history loaded by daemon2024-01-25T19:45:27ZSébastien BlinSwarm-history: Use history loaded by daemonhttps://review.jami.net/q/topic:swarm-history
# TODO
+ Use `loadConversation` instead of `loadConversationMessages`
+ Use `SwarmLoaded` instead of `conversationLoaded`
+ This gives the following structure:
```
struct SwarmMessage
{
...https://review.jami.net/q/topic:swarm-history
# TODO
+ Use `loadConversation` instead of `loadConversationMessages`
+ Use `SwarmLoaded` instead of `conversationLoaded`
+ This gives the following structure:
```
struct SwarmMessage
{
std::string id;
std::string type;
std::string linearizedParent;
std::map<std::string, std::string> body;
std::vector<std::map<std::string, std::string>> reactions;
std::vector<std::map<std::string, std::string>> editions;
};
```
Containing the reactions, editions (previous bodies) directly inside the message
+ Remove custom logic to linearize the history, filter merge messages (they are removed by the daemon), build reaction/editions
+ Use new signals `SwarmMessageReceived`, `SwarmMessageUpdated` (if edited, deleted or parent changes), `ReactionAdded`, `ReactionRemoved` to update the view/reactionsAlexander Lussier-CullenAlexander Lussier-Cullenhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/946Profile update cause invalid messages to be generated2024-01-24T13:12:27ZSébastien BlinProfile update cause invalid messages to be generated# Scenario
Alice got 2 devices:
Windows BEta 20221221
Android 20231228-01
+ Windows creates a swarm
+ Android updates the profile, then send a text message
# Expected result
Windows should get new profile
# Current result
Windows g...# Scenario
Alice got 2 devices:
Windows BEta 20221221
Android 20231228-01
+ Windows creates a swarm
+ Android updates the profile, then send a text message
# Expected result
Windows should get new profile
# Current result
Windows get an invalid commit detectedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1534Profile update cause invalid messages to be generated2024-01-19T14:46:29ZSébastien BlinProfile update cause invalid messages to be generated# Scenario
Alice got 2 devices:
Windows BEta 20221221
Android 20231228-01
+ Windows creates a swarm
+ Android updates the profile, then send a text message
# Expected result
Windows should get new profile
# Current result
Windows g...# Scenario
Alice got 2 devices:
Windows BEta 20221221
Android 20231228-01
+ Windows creates a swarm
+ Android updates the profile, then send a text message
# Expected result
Windows should get new profile
# Current result
Windows get an invalid commit detectedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/831Add abstraction layer around conversation2024-01-19T13:25:49ZPierre NicolasAdd abstraction layer around conversationConversation are very complex partly because we keep history (git system).
Deamon should manage the data to give a simplified version to clients.
Then it will be cleaner and reduce bugs in the client conversation implementation.Conversation are very complex partly because we keep history (git system).
Deamon should manage the data to give a simplified version to clients.
Then it will be cleaner and reduce bugs in the client conversation implementation.Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1465Swarm-history: Use history loaded by daemon2024-01-09T17:48:34ZSébastien BlinSwarm-history: Use history loaded by daemonhttps://review.jami.net/q/topic:swarm-history
# TODO
+ Use `loadConversation` instead of `loadConversationMessages`
+ Use `SwarmLoaded` instead of `conversationLoaded`
+ This gives the following structure:
```
struct SwarmMessage
{
...https://review.jami.net/q/topic:swarm-history
# TODO
+ Use `loadConversation` instead of `loadConversationMessages`
+ Use `SwarmLoaded` instead of `conversationLoaded`
+ This gives the following structure:
```
struct SwarmMessage
{
std::string id;
std::string type;
std::string linearizedParent;
std::map<std::string, std::string> body;
std::vector<std::map<std::string, std::string>> reactions;
std::vector<std::map<std::string, std::string>> editions;
};
```
Containing the reactions, editions (previous bodies) directly inside the message
+ Remove custom logic to linearize the history, filter merge messages (they are removed by the daemon), build reaction/editions
+ Use new signals `SwarmMessageReceived`, `SwarmMessageUpdated` (if edited, deleted or parent changes), `ReactionAdded`, `ReactionRemoved` to update the view/reactionsSébastien BlinAndreas TraczykSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/937Windows: kicking failed, invalid path2024-01-09T16:53:26ZSébastien BlinWindows: kicking failed, invalid path# Scenario
+ Alice admin (windows) ban a member from a conversation
# Current result
+ Member not banned
# Expected result
+ Member banned
# Logs
```
[1704486353.315|1280|conversation.cpp :958 ] Kicking ad2a7baf15ee3957bea...# Scenario
+ Alice admin (windows) ban a member from a conversation
# Current result
+ Member not banned
# Expected result
+ Member banned
# Logs
```
[1704486353.315|1280|conversation.cpp :958 ] Kicking ad2a7baf15ee3957beaef2271a7bb8e08c63cca5 failed
[1704486367.260|6552|conversationrepository.cpp:886 ] Error when adding file: invalid path: 'votes/ban/members/ad2a7baf15ee3957beaef2271a7bb8e08c63cca5\bda3200d605f7ff2b08e1c2a7eaa84c0a8a5f13e'
[1704486367.262|6552|conversation.cpp :958 ] Kicking ad2a7baf15ee3957beaef2271a7bb8e08c63cca5 failed
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1535Swarm: Should be able to create a swarm with members of another swarm2024-01-05T20:35:07ZSébastien BlinSwarm: Should be able to create a swarm with members of another swarm# Scenario
+ Click on Start swarm
# Expected
We should see all conversations and be able to click on a swarm to add all members of this swarm to a new one
# Current result
We only see contacts# Scenario
+ Click on Start swarm
# Expected
We should see all conversations and be able to click on a swarm to add all members of this swarm to a new one
# Current result
We only see contactshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1128Continue swarm support with multiple participants - Missing features2023-12-18T14:41:38ZSébastien BlinContinue swarm support with multiple participants - Missing features1. Add members
2. Kick members (if admin)
5. Show profile for conversation's requests
8. Start a swarm without other members1. Add members
2. Kick members (if admin)
5. Show profile for conversation's requests
8. Start a swarm without other membersAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/924Double conversation on bad presence sync2023-12-05T21:02:29ZSébastien BlinDouble conversation on bad presence sync# Scenario
+ Disable the presence in AccountManager::startSync
+ Alice adds Bob, Bob adds Alice => 1 conversation both side
+ Re-enable presence
+ Alice sends a message
# Current result
Bob receives a new trust request and doesn't acc...# Scenario
+ Disable the presence in AccountManager::startSync
+ Alice adds Bob, Bob adds Alice => 1 conversation both side
+ Re-enable presence
+ Alice sends a message
# Current result
Bob receives a new trust request and doesn't accept it automatically
# Expected
Alice and Bob should uses only 1 conversationSébastien BlinSébastien Blin