Skip to content
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

Debug Archive filesize / GitHub file upload limitation #4306

Closed
tryallthethings opened this issue Feb 20, 2022 · 10 comments
Closed

Debug Archive filesize / GitHub file upload limitation #4306

tryallthethings opened this issue Feb 20, 2022 · 10 comments

Comments

@tryallthethings
Copy link

Not 100% a Desktop Client bug, and probably a corner case scenario. But for me, it fits better than enhancement due to GitHub's behavior. Feel free to reassign.

Expected behaviour

Easily be able to upload the Debug Archive to an issue.

Actual behaviour

My Debug Archive for #4304 was ~34MB in file size. GitHub only allows 25MB for other file attachments and throws useless errors if you exceed the limit:

image
image

Therefor, I had to manually split the file into 2 separate. IMHO, this should already be handled during file creation. At the very least, a hint should be given to the user after Debug Archive creation in case the file size exceeds 25MB.

Steps to reproduce

  1. Have large Desktop client logs / .sync.db files
  2. Create debug archive

Client configuration

Client version: 3.4.2
Operating system: Windows 10 Pro 21H1
OS language: en-us
Installation path of client: default (C:\Program Files\Nextcloud)

@github-actions
Copy link

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label Mar 20, 2022
@tryallthethings
Copy link
Author

As this received no attention so far, I suppose the issue is still present in 3.4.4. In my test today, it only created a single 22,3MB file.

@github-actions github-actions bot removed the stale label Mar 20, 2022
@github-actions
Copy link

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions github-actions bot added the stale label Apr 17, 2022
@tryallthethings
Copy link
Author

Could someone please at least acknowledge this bug, so it doesn't go stale every 30 days?

@github-actions
Copy link

github-actions bot commented May 2, 2022

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

@github-actions github-actions bot closed this as completed May 2, 2022
@tryallthethings
Copy link
Author

open please

@github-actions
Copy link

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

@tryallthethings
Copy link
Author

Thanks useless bot!

@github-actions
Copy link

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

@github-actions
Copy link

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants