Description
Description
Event Timeline
Comment Actions
Directories I tried and failed:
- b1ed8c3c380b35c0a6546a04e526259d600c7a31
- 8fd378d35eb2c80a24d5a29e66b994ed2a275592
Directories I tried and failed before timeouts deployment:
- 3a97a721cb7de736b0bd9c62afa03bca146df93d
- 3a97a721cb7de736b0bd9c62afa03bca146df93d
Directories I tried and succeeded :
- 778418cdc5f511f34d323544bc2412c41116542b (very very small directory)
Comment Actions
For the new error where download stays at "new" for a long time, here are my 2 tests:
4a2875f69e68bb60a9e76414439c073fd2b20732
fb13b51abbcfd13de85d9ba8d070a23679576cd7
Comment Actions
Now this returned with internal server error: fb13b51abbcfd13de85d9ba8d070a23679576cd7
and this one is done: 4a2875f69e68bb60a9e76414439c073fd2b20732
Comment Actions
I just had two vault successes:
- d83b7dda887dc790f7207608474650d4344b8df9
- cf31343fd5744d56d7126b6cb99e96d29f5c0376
I'm not sure if the bug is fixed, but something changed..
Comment Actions
I think now we that we have proper error messages in the frontend for repositories that are too big, we can open new tasks for specific Vault failures.