Hi, has anyone encountered a similar problem like me? I cannot submit zip files anymore as a private data set. Error message simply states - \"Unfortunately we could not create your dataset.\". I am reasonably sure that nothing has changed on my side, and I was able to submit zip files before. \nI also tested with very small .pkl files wrapped in zip (to check if it is not about size issue), and this failed in the same way.\nIf I remove \".zip\" ending from the file, it is being loaded without error, but I cannot interact with that file anymore in the same way in kernel. \nSo something is probably happening with the way \".zip\" ending files are being treated.
\n\nAnyone knows how to solve this?
", "messages": [ { "id": "548163", "postDate": "06/08/2019 22:47:33", "content": "Hi, has anyone encountered a similar problem like me? I cannot submit zip files anymore as a private data set. Error message simply states - \"Unfortunately we could not create your dataset.\". I am reasonably sure that nothing has changed on my side, and I was able to submit zip files before. \nI also tested with very small .pkl files wrapped in zip (to check if it is not about size issue), and this failed in the same way.\nIf I remove \".zip\" ending from the file, it is being loaded without error, but I cannot interact with that file anymore in the same way in kernel. \nSo something is probably happening with the way \".zip\" ending files are being treated.
\n\nAnyone knows how to solve this?
", "rawMarkdown": "Hi, has anyone encountered a similar problem like me? I cannot submit zip files anymore as a private data set. Error message simply states - \"Unfortunately we could not create your dataset.\". I am reasonably sure that nothing has changed on my side, and I was able to submit zip files before. \nI also tested with very small .pkl files wrapped in zip (to check if it is not about size issue), and this failed in the same way.\nIf I remove \".zip\" ending from the file, it is being loaded without error, but I cannot interact with that file anymore in the same way in kernel. \nSo something is probably happening with the way \".zip\" ending files are being treated. \n\nAnyone knows how to solve this?", "votes": null }, { "id": "548168", "postDate": "06/08/2019 22:57:59", "content": "Have you checked the free volume of your private dataset? there is 20GB size limit.
", "rawMarkdown": "Have you checked the free volume of your private dataset? there is 20GB size limit.", "votes": null }, { "id": "548172", "postDate": "06/08/2019 23:12:17", "content": "zip files I was trying to upload were 1.5Gb and then I tested much smaller (less than 1Mb, in case it was size related), but both failed in the same way. Also, if I just removed .zip ending in file name, both files were uploaded, but I lost zip interface to them. So I doubt this is size related, unfortunately.
", "rawMarkdown": "zip files I was trying to upload were 1.5Gb and then I tested much smaller (less than 1Mb, in case it was size related), but both failed in the same way. Also, if I just removed .zip ending in file name, both files were uploaded, but I lost zip interface to them. So I doubt this is size related, unfortunately.", "votes": null }, { "id": "548212", "postDate": "06/09/2019 01:52:51", "content": "Umm, it's mysterious. Are you sure you have free volume? File volume is limited based on the total of your private datasets, not each dataset.
", "rawMarkdown": "Umm, it's mysterious. Are you sure you have free volume? File volume is limited based on the total of your private datasets, not each dataset.", "votes": null }, { "id": "548733", "postDate": "06/09/2019 19:50:08", "content": "Yeah, I used up only 5Gb of private volumes. I now have a suspicion that there is a limit on number of files you can upload as well. If I try to upload 50 weights files zipped, it does not work. If I create python dictionary, save it as pkl, I can upload that file. If I have only 10 or so weights zipped, I can upload that as well. So I will just use pkl work-around for now. But disadvantage of that is that I now need to load into memory all weights at once, instead of iterating through them and loading one by one.
", "rawMarkdown": "Yeah, I used up only 5Gb of private volumes. I now have a suspicion that there is a limit on number of files you can upload as well. If I try to upload 50 weights files zipped, it does not work. If I create python dictionary, save it as pkl, I can upload that file. If I have only 10 or so weights zipped, I can upload that as well. So I will just use pkl work-around for now. But disadvantage of that is that I now need to load into memory all weights at once, instead of iterating through them and loading one by one.", "votes": null }, { "id": "573703", "postDate": "07/12/2019 16:21:14", "content": "It happened to me today too. The first time I dragged a 1.5g zip data and it worked. The progress bar was shown and running. Then I found that I forgot something so I cancel the upload. Then the whole system didn't work anymore. Any file, zip or not zip, big or small, they all turned red and with a red x on the right. Wonder what went wrong?
", "rawMarkdown": "It happened to me today too. The first time I dragged a 1.5g zip data and it worked. The progress bar was shown and running. Then I found that I forgot something so I cancel the upload. Then the whole system didn't work anymore. Any file, zip or not zip, big or small, they all turned red and with a red x on the right. Wonder what went wrong?", "votes": null }, { "id": "628184", "postDate": "09/16/2019 22:49:37", "content": "Did you find any solution? Run into the exact same problem @huohsien had...
", "rawMarkdown": "Did you find any solution? Run into the exact same problem @huohsien had...", "votes": null } ], "comments": [ { "id": 548168, "author_name": "osciiart", "author_url": "", "post_date": "06/08/2019 22:57:59", "content": "Have you checked the free volume of your private dataset? there is 20GB size limit.
", "votes": null, "replies": [ { "id": 548172, "author_name": "rytisva88", "author_url": "", "post_date": "06/08/2019 23:12:17", "content": "zip files I was trying to upload were 1.5Gb and then I tested much smaller (less than 1Mb, in case it was size related), but both failed in the same way. Also, if I just removed .zip ending in file name, both files were uploaded, but I lost zip interface to them. So I doubt this is size related, unfortunately.
", "votes": null, "replies": [] }, { "id": 548212, "author_name": "osciiart", "author_url": "", "post_date": "06/09/2019 01:52:51", "content": "Umm, it's mysterious. Are you sure you have free volume? File volume is limited based on the total of your private datasets, not each dataset.
", "votes": null, "replies": [] }, { "id": 548733, "author_name": "rytisva88", "author_url": "", "post_date": "06/09/2019 19:50:08", "content": "Yeah, I used up only 5Gb of private volumes. I now have a suspicion that there is a limit on number of files you can upload as well. If I try to upload 50 weights files zipped, it does not work. If I create python dictionary, save it as pkl, I can upload that file. If I have only 10 or so weights zipped, I can upload that as well. So I will just use pkl work-around for now. But disadvantage of that is that I now need to load into memory all weights at once, instead of iterating through them and loading one by one.
", "votes": null, "replies": [] } ] }, { "id": 573703, "author_name": "huohsien", "author_url": "", "post_date": "07/12/2019 16:21:14", "content": "It happened to me today too. The first time I dragged a 1.5g zip data and it worked. The progress bar was shown and running. Then I found that I forgot something so I cancel the upload. Then the whole system didn't work anymore. Any file, zip or not zip, big or small, they all turned red and with a red x on the right. Wonder what went wrong?
", "votes": null, "replies": [] }, { "id": 628184, "author_name": "xeroxm", "author_url": "", "post_date": "09/16/2019 22:49:37", "content": "Did you find any solution? Run into the exact same problem @huohsien had...
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "548163": "Hi, has anyone encountered a similar problem like me? I cannot submit zip files anymore as a private data set. Error message simply states - \"Unfortunately we could not create your dataset.\". I am reasonably sure that nothing has changed on my side, and I was able to submit zip files before. \nI also tested with very small .pkl files wrapped in zip (to check if it is not about size issue), and this failed in the same way.\nIf I remove \".zip\" ending from the file, it is being loaded without error, but I cannot interact with that file anymore in the same way in kernel. \nSo something is probably happening with the way \".zip\" ending files are being treated. \n\nAnyone knows how to solve this?", "548168": "Have you checked the free volume of your private dataset? there is 20GB size limit.", "548172": "zip files I was trying to upload were 1.5Gb and then I tested much smaller (less than 1Mb, in case it was size related), but both failed in the same way. Also, if I just removed .zip ending in file name, both files were uploaded, but I lost zip interface to them. So I doubt this is size related, unfortunately.", "548212": "Umm, it's mysterious. Are you sure you have free volume? File volume is limited based on the total of your private datasets, not each dataset.", "548733": "Yeah, I used up only 5Gb of private volumes. I now have a suspicion that there is a limit on number of files you can upload as well. If I try to upload 50 weights files zipped, it does not work. If I create python dictionary, save it as pkl, I can upload that file. If I have only 10 or so weights zipped, I can upload that as well. So I will just use pkl work-around for now. But disadvantage of that is that I now need to load into memory all weights at once, instead of iterating through them and loading one by one.", "573703": "It happened to me today too. The first time I dragged a 1.5g zip data and it worked. The progress bar was shown and running. Then I found that I forgot something so I cancel the upload. Then the whole system didn't work anymore. Any file, zip or not zip, big or small, they all turned red and with a red x on the right. Wonder what went wrong?", "628184": "Did you find any solution? Run into the exact same problem @huohsien had..." }, "source": "meta" }