-
Notifications
You must be signed in to change notification settings - Fork 48
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
Problems about Submission #215
Comments
hi, what team are you on? I'll verify your credentials |
hi, our team is 'fly_eagle', which is the parameter when running 'bash mbzirc_submit.bash', if that's what is needed. By the way, by 23rd Aug, is it an upper limit of submits we can do? What is the maximum times we can submit? |
hi, the team name should be
Yes. 23rd is the last day for submitting dry run. Each time you submit, it's going overwrite the previous one. So you can re-submit if something went wrong. Each submission does not automatically trigger a run. We will be manually launching and running your solution during dry-run. If we find anything wrong with the run, we'll get in touch with you. If you are able to fix the issue before dry run period ends, we can potentially run it again. |
Hi, thanks a lot for the reply! We will try to submit as early as possible. |
Hi, we are the same team. We have tried change the team name to fly-eagle. But the problem still exists by "An error occurred (AccessDenied) when calling the PutObject operation: Access Denied". |
I have just re-sent the credentials to the main and alternative contact emails addresses we have. Please check the credentials in case they are different from the ones sent before. I have also just tested submitting a solution using your credentials and I was able to submit. Make sure when configuring aws command line tool, you're using |
Hi, thanks a lot for the reply!By using the credentials you provide us, we are able to submit the solution. |
thanks I see your submissions. For dry-run, can you submit with the upstream tag |
Definitely Ian, we will set the upstream tag only |
Hello Sir,
We are facing a problem during submission. When we try to use AWS to submit the docker image, the output of submission tell that the upload failed by "An error occurred (AccessDenied) when calling the PutObject operation: Access Denied". Amazon's official explanation for this issue is as follows: "Your users need to have the s3;PutObject permission." Could you please tell us how to solve this problem?
Thanks.
The text was updated successfully, but these errors were encountered: