-
Notifications
You must be signed in to change notification settings - Fork 46
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
Unmanaged exception in upload_file when attempting to upload non-existent file #288
Comments
I've created a new issue #292 regarding the last part of your message. |
The same obscure error is obtained when trying to create a function out of a file that references a non-existent file: unctions:
scar-alpine:
image: alpine
memory: 128
init_script: non-existent-file.sh scar init -f scar-function.yaml Info: installing 1.1.3 Expected behaviour: Output the error message from the exception (which is included in the log): |
Trying to upload a non-existent file through
scar put
yields the following error:while the
$HOME/.scar/scar.log
file clearly indicates the error:Expected behaviour: Indicate that the file does not exist.
Related to this, it would be convenient to have the following syntax:
This way, the input bucket and input folder would be obtained from the function description in order to reduce verbosity when dealing with Amazon S3.
Same for
scar get
andscar ls
:-DThe text was updated successfully, but these errors were encountered: