"Download repository as zip" doesn't work most of the time. #72
Labels
No Label
Service
Buildbot
Service
Chat
Service
Gitea
Service
Translate
Type
Bug
Type
Config
Type
Deployment
Type
Feature
Type
Setup
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-projects-platform#72
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Original Report by @Strike_Digital : blender/blender-manual#104563
When trying to download this repository as a zip file, most of the time, the server doesn't respond and nothing happens:
![image](/infrastructure/blender-projects-platform/attachments/342f5454-56e2-467f-9dda-3b44fcb36b18)
Rarely, the file will download instantly, and sometimes it will start downloading after a couple of minutes.
Going to the zip url directly gives a time-out error:
Occurs on both Chrome and Firefox.
I'm working on an addon to view the manual directly in Blender, so being able to reliably download the zip file for different versions would be valuable.
Edit:
It seems that after waiting a couple of minutes to download initially, subsequent downloads will begin immediately. I assume this is caused by the zip file being built from scratch the first time, and then cached after that.
It seems that the cache isn't persistent though, as I downloaded the 3.6 zip a while ago (which hasn't changed since), but I still had to wait for it to download today.
Any chance the zip cache could be rebuilt automatically with each commit, at least for important branches? (assuming that this is the problem)
edited.
I thought this was the ticket relating to downloads from docs.blender.org failing.. but projects should not be affected by the same issue.
I'll investigate this.
From what I can tell, this is the same underlying bug as #73 and should be fixed now.
If not, we can reopen the issue.