Fix outgoing messages stored in wrong thread #216
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Outgoing messages in 1-to-1 chats were stored in the note-to-self chat. This was broken in 6125534. This will be fixed by this MR. This also fixes the timestamp of identity verification messages, which are inserted into the store by presage. By convention, all timestamps used are in milliseconds, this one was in seconds. This was wrong since whisperfish#206.
Schmiddiii
force-pushed
the
fix-message-store
branch
from
2ee8cba
to
d688659
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Outgoing messages in 1-to-1 chats were stored in the note-to-self chat. This was broken in 6125534. This will be fixed by this MR.
This also fixes the timestamp of identity verification messages, which are inserted into the store by presage. By convention, all timestamps used are in milliseconds, this one was in seconds. This was wrong since #206.