The reason is because datetime.datetime.utcnow() will take current time and transfer to etc zone. E.g., if you live in zone -7 and it is 5am, it will make a min_schedule_time to be 12pm of UTC. Which will show an error "cannot schedule in 20 minutes", until you schedule something in advance for 7 hours 20 minutes.
There is a bug in
uploader.py
when checking boundaries for scheduling time. Instead ofshould use
The reason is because datetime.datetime.utcnow() will take current time and transfer to etc zone. E.g., if you live in zone
-7
and it is 5am, it will make amin_schedule_time
to be 12pm of UTC. Which will show an error "cannot schedule in 20 minutes", until you schedule something in advance for 7 hours 20 minutes.