-
Notifications
You must be signed in to change notification settings - Fork 11
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
Error An HTTP Client raised and unhandled exception: 's3' #173
Comments
Sorry for the delay @ambrosiozack That is quite an odd bug. Seems like something weird is going on in botocore. Could you give me the version of botocore you have on your system? (you can paste the output of |
This is the result:
|
these seem to work for me. Could you try running |
alright lets see what we can find by running it with try running the following command
That will drop you into a pdb shell which will hit a breakpoint as soon as the error hits. Once you're there. Could you try investigate the state of variables and see what stands out as being odd? Let me know if you are not familiar with python debugging and need some help with this. |
Type It will then stop at the point that the error occurs. When you get to that point enter |
oh right sorry about that - errors are being suppressed atm so this is actually harder than I expected. I'll think of something and get back to you :) |
I put more information, I had read wrong and interpreted "11" instead of "ll" |
I saw that - the issue is that |
OK thanks for the help. I wait your answer. |
Hi friend |
sorry about that @ambrosiozack. Its been a busy few weeks for me. Could you perhaps paste the contents of Please make sure to remove your keys before pasting to github |
A few things:
|
Issue Details
Hello

When trying to make the command "s4 sync / folder" I get the following error:
Any idea? Thanks
Operating System (uname -a)
Linux debian-dhcp 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux
s4 version (s4 version)
0.4.1
python version (python --version)
Python 2.7.13
Steps to reproduce the issue
When executing the command "s4 sync socios"
DEBUG log output (run with
s4 --log-level=DEBUG
)The text was updated successfully, but these errors were encountered: