tdesktop
tdesktop copied to clipboard
telegramdesktop
"send now" multiple selected sheduled messages, order is unexpected (follows compose time, not sheduled time)
Steps to reproduce
We will need three dates for sheduled messages A, B, C, such that A < B < C (eg tomorrow, in 2 days, in 3 days)
- schedule message "a" at date A
- schedule message "c" at date C (⚠️ C first, then B)
- schedule message "b" at date B
- now select them and send them now
Expected behaviour
order should of sent messages should be determined by the time of which they are sheduled for
like this
so "a", "b", "c"
Actual behaviour
order is determined by the time of which the messages were composed, not to when they were sheduled
so "a", "c", "b"
Operating system
Windows 10 LTSC
Version of Telegram Desktop
4.16.4 x64
Installation source
Static binary from official website
Crash ID
No response
Logs
No response
on mobile (at least android) you don't have the "send now" option, thus this isn't a problem.
Screenshot
If you wish, you can test a nightly debug build. It should be better now. https://github.com/telegramdesktop/tdesktop/actions/runs/8866982405
The telegram publication timer is not working correctly. Publication may occur 5-10 minutes later than the scheduled time. The time of publication in the post also changes.
@23rd I confirmed in the Telegram_x64 version, that the behaviour now works as expected. Thanks for implementing!
@kartavenko1983 comment seems unrealated, I think it has to do with diferent local time vs server time. My sheduled was "early" by like 8 seconds comapred to local machine time, but that is probably just my machine I assume.
Detailed testing:
Sheduled mesages (order of creation: a, c then b):
after sending all three now:
I also tried multiple messages sheduled to same time => will send in the order in which they were displayed in the sheduled messages preview. I also tried having sheduled messages A C B, resheduling B to order A B C => sends in the correct order that is also shown in the sheduled messages preview (A B C).
As a programmer inexperienced with c++, the code looks fine too.
@SVNKoch Of course, I understand that there may be a delay, but not for 10 minutes, but for a couple of seconds. In addition, there was a case once that the record was not published at all
@kartavenko1983 you might have a valid bug here. However I don't see the relation of that problem to this issue. It has nothing to do with my original problem and is not effected by the proposed solution. You should create a new bug ticket and best to attach some logs / more details other than just that it sent with delay.