-
-
Notifications
You must be signed in to change notification settings - Fork 115
feat: pre-messages / next version of download on demand #7371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
Simon-Laux
wants to merge
11
commits into
main
Choose a base branch
from
pre-messages
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or 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
6fe6723 to
8140ebc
Compare
2f1c383 to
6bcc795
Compare
26 tasks
8443b17 to
702771f
Compare
Hocuri
reviewed
Dec 11, 2025
126c64f to
bb0fd7c
Compare
- Remove partial downloads (remove creation of the stub messages) (#7373) - Remove "Download maximum available until" and remove stock string `DC_STR_DOWNLOAD_AVAILABILITY` (#7369) - Send pre-message on messages with large attachments (#7410) - Pre messages can now get read receipts (#7433) Co-authored-by: Hocuri <hocuri@gmx.de>
bb0fd7c to
a98fe05
Compare
Hocuri
reviewed
Dec 18, 2025
Comment on lines
+1475
to
+1478
| "CREATE TABLE download_new ( | ||
| rfc724_mid TEXT NOT NULL DEFAULT '', | ||
| msg_id INTEGER NOT NULL DEFAULT 0 | ||
| ) STRICT; |
Collaborator
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@link2xt I'm wondering whether this should be UNIQUE on rfc724_mid or msg_id? I guess it doesn't really make sense to have the same message in there twice?
Previously, the uid_next wasn't advanced, which didn't create any problems, but it also was inefficient, because another loop was done trying to fetch the message again (and then finally skipping it, because it's already known).
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.
DC_STR_DOWNLOAD_AVAILABILITY#7369This is the branch for #7367
closes #7367
Currently removed tests
Progress of the tests
Overview about the recycled(♻️) and dropped(🗑️) tests of the tests that I removed in #7373
All the recycled tests were already recycled/re-made except for some which are still to do:
Furthermore there need to be new tests to test the downloading/scheduling changes.
TODO Tests
postponed to do tests
discarded/ignored test ideas
maybe we should reconsider / discuss those?