I apologize in advance if this question has already been answered. I've looked at several posts and have yet to find the info to resolve my issue.
I'm trying to work with Kaggle's API to download some data sets. I've installed Kaggle with pip3 and have downloaded the Kaggle.json file and moved it to c:/users//appdata/local/programs/pythoncodingpack/lib/site-packages/kaggle. I did not specifiy this particular path, this is where pip3 automatically saved the kaggle folder. The .json folder is definitely in there, but when I try to run the API command "kaggle datasets download -d victorsoeiro/netflix-tv-shows-and-movies" I get the error included in the title.
What I have noticed is that there is an executable file called kaggle.exe on the path c:/users//appdata/local/programs/pythoncodingpack/scripts/kaggle.exe. I was wondering if maybe the computer was finding that file and stopping before finding the kaggle folder on the ./lib/site-packages/kaggle/ path.
I have tried granting permission with the chmod 600 command on the ./kaggle/kaggle.json path and I have tried including the whole path when executing the command. Nothing I've done so far has resolved the error when I try to run the API command. Can anyone help out?
Don't know how to fix this error, eventough I read several articles and watched a few videos. I already made my #web directory read- and writeable with chmod 777 -R.
I am able to upload files in different locations out of the #web folder. Unfortunately, I am unable to display pictures at my website, which are out of the #web directory.
Please help :)
Please make sure your path should be proper with needed permission. Try with adding static path and check if it works then add dynamic path
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 months ago.
The community reviewed whether to reopen this question 7 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
For a while now, I've been unable to send files or folders to Zipped folder from windows explorer. The option is there, but when I click on it, nothing happens.
It seems others have had similar problems, but in their cases, the option has been greyed out, or another program has taken over as the default .zip program.
If I type "regsvr32 %windir%/system32/zipfldr.dll" into a run command, I get the following error:
_______________________________
[Window Title]
RegSvr32
[Content]
The module "C:\WINDOWS/system32/zipfldr.dll" was loaded but the entry-point DllRegisterServer was not found.
Make sure that "C:\WINDOWS/system32/zipfldr.dll" is a valid DLL or OCX file and then try again.
[OK]
_______________________________
Very annoying, I'm not sure what is causing this.
I ran into this issue as well. However my fix was much easier. My file names and paths were too long to be zipped. There was no warning.
I resolved it by copy-pasting the directory to another with a shorter path.
e.g. from /this/path/is/way/too/ooo/ooo/oo/long to /home/Desktop
I've copied the comments from this link mentioned earlier - http://david-homer.blogspot.com.br/2014/06/when-using-send-to-compressed-zipped.html
When using the "Send to compressed (zipped) folder" context menu item nothing happens
I've recently had a problem when using the "Send to
compressed (zipped) folder" context menu item nothing happens on
Windows 8.1.
Looking further into this I found that it worked most folders just not
the one I wanted to ZIP.
After a while I realised that I had a Visual Studio project source
code in this folder that had that annoying deep object folder problem and it
seems that when you click "Send to compressed (zipped) folder" if
there is an exceptionally deep directory structure in the folder you
are zipping, the compression may fail but show no error.
I use the following tried and tested RoboCopy method for removing
these broken directories with exceptionally deep paths that you can't
delete with Windows Explorer.
#echo off
cls
mkdir emptyfolder
robocopy emptyfolder "path\to\obj" /MIR
rmdir emptyfolder
rmdir "path\to\obj"
pause
Why not check out our User Provisioning Tool on our web site
I can see that this could be a potential problem, however at the moment this is working fine again as far as I can see - if I have the issue again I guess I'll have to check out the file structure, maybe that could be the issue.
I had the same problem, when clicked on send to compressed file nothing happened, then i found out that when you have a deep folder structure, windows fails to zip and doesn't show any errors. As it is explained here: http://david-homer.blogspot.com.br/2014/06/when-using-send-to-compressed-zipped.html
Check whether your file does not have the extension. Remember that Windows explorer does not allow creating folders beginning with dot, even though the underlying system can handle them.
I realise that I'm quite late to answering this question but I was having the same problem when trying to zip a folder and it seemed that nothing happened and no error was shown.
I right clicked and copied the folder, then pasted it to the same directory, during the copy a dialog told me there were several files in the folder that where too long to be copied, so I clicked skip. Then right clicked the copied folder and sent to zip and it worked.
I know it is way too late but it might help someone. Does your folder have other sub-folders inside it? In my case, I tried zipping the folders which have sub-folders and it did not work (no response just like in your case). Try to zip the folders which have files only and no any sub folders inside.
I too ran into this problem while I was attempting to zip Android Studio Source code from 10 different projects. Initially having a overly deep structure seemed to be the case, and for me too Windows did not show an error initially.
So I did some more file digging and I found that this error usually occurs if you have an empty folder somewhere in your file structure of the file you are trying to zip. Each level down I was able to find the folder containing the mystery folder and each time the windows error would appear showing me the error saying that it could not zip an empty folder!
I went down the Rabbit hole and added a simple READ_ME.*txt file to each empty folder and viola!
I am using Windows 10 updated version on 10.2018.
Hope this helps someone!
Also way late, but maybe this will help others:
I had this problem, but could not find this mysterious folder, or deep directory, in fact, one of the folders that wouldn't zip had just one Word document in it.
What I did was to find a folder that would zip (or create one) and then copy the folder that wouldn't zip into it.
Worked like a charm!
I worked around the problem by using 7-Zip instead.
I've been trying to submit my app to the mac app store and I've been trying to figure out how to solve this issue:
Files Only Readable By The Root User - The installer package includes files that are only readable by the root user. This will prevent verification of the application's code signature when your app is run. Ensure that non-root users can read the files in your app.
I haven't been able to fix this problem for a while and does anyone have a solution?
In my case, none of the files were owned by root, but one had no read permissions for group and everyone, but only for my user. I found this by using this cmd in Terminal:
ls -lR /path/to/app
I then searched for "-----" inside the output from the ls command, which found the problematic file.
I had the same problem, but my solution was to run:
cd myApp.app
chmod a+rX *
This fixes the permissions and makes the Application Loader happy.
I found the answer:
I deleted some files that weren't readable by the system, files that showed a white blank icon
For anyone who has been banging their head on this one my experience is the error is erroneous or at best very misleading.
After looking over all the permissions then dragging files in and out of the bundle to test Application Loader the error magically disappeared and the same files with the same permissions ceased to give the same error.
This really isn't a solution but it may be important to know that this error may not be what it seems (tested on 10.9.4).
I've created an iOS 4.3 iPhone app in Xcode 4. When I use the Application Loader, I get this error:
Unable to create configuration directory:
/Users/myusername/.itmstransporter
I'm not sure it is permissions but believe it most likely is. Any ideas how to resolve it?
It seems similar to What does "The dwarfdump binary must exist and must be executable" mean?, which I ran
sudo ln -s /Developer/usr/bin/dwarfdump /usr/bin/
and resolved that issue.
VanceG's answer got me to a solution, which was to change the permissions on my /Users/myusername folder to allow writing (the link he refers to does the same for the /Users/Shared folder which not surprisingly didn't solve this error as the app is complaining about writing to my user folder).
In terminal sudo chmod 777 /Users/myusername (or chmod 1777 depending on version of OSX as discussed in http://support.apple.com/kb/TS1277).
I had the same problem, and it turned out to be a problem with the Shared users folder, which also was causing problems with iTunes home sharing. For me, following these instructions fixed both problems: http://support.apple.com/kb/TS1277
Hope it works for you too.