Browse through the questions and answers listed below or filter and sort to narrow down your results.
YAML_FILE_ERROR: mapping values are not allowed in this context at line 1
DOWNLOAD_SOURCE - YAML_FILE_ERROR: mapping values are not allowed in this context at line 1 Reference YAML file: buildspec.yaml version: 0.2 `phases: pre_build: commands: - echo Logging in to Amazon ECR... - $(aws ecr get-login --no-include-email --region $AWS_DEFAULT_REGION) build: commands: - echo Build started on `date` - echo Building the Docker image... - docker build -t web:1 . - docker tag web:1 020861552741.dkr.ecr.ap-southeast-1.amazonaws.com/hasib_cloud post_build: commands: - echo Build completed on `date` - echo Pushing the Docker image... - docker push 020861552741.dkr.ecr.ap-southeast-1.amazonaws.com/hasib_cloud ~ ![screenshot](/media/postImages/original/IMD8WJYdlxT_6k-v3PKRmBGA)
use study link embedded in the same window of amazon mturk (iframe)
Hello, I am trying to create a study that opens in the mturk webpage instead of a new window. In the study we are using webcam and I got this message when publish the study in sandbox (so I could try it out). Warning message says: Unable to connect to your webcam, please try again. Perhaps it is being used by another application. So what should I edit in the HTML format so I can give access to webcam using the same page? Is that the solution or should I try to search something else?
X-Ray not working like expecting
The idea is the following: * Codecommit has a notification rule. * Notification's target it's an sns topic. * The topic's target is a lambda function. * Minimally I want lambda X-Ray trace when the notification occurs. If all trace better. I post a message from the SNS Topic console, the X-Ray trace is generated with SNS and Lambda. However, if I trigger a notification, the trace is not generated (Lambda runs correctly). I would like to know if I can make the complete or partial trace be generated when generating a notification in CodeCommit. # Update My lambda logs insights: * Post message from SNS Topic:```"_X_AMZN_TRACE_ID": "Root=1-62gd6bfa-6ag9233f49fe8faf6ef7ed16;Parent=4b19513e742ad199;Sampled=1"``` * Codecommit notification: ```"_X_AMZN_TRACE_ID": "Root=1-62d56c36-3bg3f6fbaa075b171b9fdba6;Parent=2f5f68ffyf25388e;Sampled=0"``` My lambda Function has active tracing, and has permissions, but I don't know why the second case don't get sampled. It should be tracing all the invocations, being sampled or not sampled...
Pull requests wrongly marked as "Merged"?
We like to create pull requests early for new branches, meaning the developer who makes the branch will immediately create one or more pull requests to signal the intended destination branch(es) (for example both "dev" and "main" for hot-fixes). While the task is in progress, the related, pending pull request(s) are marked with status "Open" But sometimes a pull request changes status to "Merged" even before the developer has had time to push any changes. However, when we click on the "Changes" tab, we see that nothing has actually been merged, and instead there is a message saying: > Differences between the source branch and the destination branch cannot be displayed for this pull request. The branch specified as the destination branch includes all the changes in the branch specified as the source branch as well as additional changes. You might have mixed up which branch should be the source, and which branch should be the destination. We suspect this happens when another pull request is being merged, and that this triggers some kind of global check of all pull requests in the repo, to see if there is a diff, and if a pull request has no diff, AWS CodeCommit "helps" us clean up our "obsolete" PRs. However, to us this is just counter-productive and confusing: Pull requests that nobody has merged are marked as merged, when the exact opposite is true. Had there been at least another status, like "Nothing to merge", then it would have been less mysterious, but still very counter-productive: Whenever this happens, we need to click on the "Changes" tab to make sure that this is actually a "Nothing to merge" status, and create a NEW pull request for anything that has been pushed to the branch after this unwanted "clean up". Question: Is there a way to avoid early pull requests from being updated automatically like this, so that it will be entirely up to the developers to decide when a pull request should be marked as merged (i.e. have it marked as merged when it is actually merged, and only then)? Thanks, and best regards, wab
RangeError: Array buffer allocation failed
Hello AWSome folks! I am trying to do the "Build a serverless web application" workshop and I'm on the User Management part. I am on to initialize Amplify CLI by executing the command "`amplify init`" and it is supposed to initialize the project but I am getting this error: `RangeError: Array buffer allocation failed at new ArrayBuffer (<anonymous>) at new Uint8Array (<anonymous>) at new FastBuffer (node:internal/buffer:959:5) at createUnsafeBuffer (node:internal/buffer:1062:12) at allocate (node:buffer:410:10) at Function.allocUnsafe (node:buffer:375:10) at Function.concat (node:buffer:553:25) at Extract.<anonymous> (/home/ec2- user/.nvm/versions/node/v16.15.0/lib/node_modules/@aws-amplify/cli/lib/binary.js:127:37) at Extract.emit (node:events:539:35) at finishMaybe (/home/ec2-user/.nvm/versions/node/v16.15.0/lib/node_modules/@aws-amplify/cli/node_modules/readable-stream/lib/_stream_writable.js:624:14)` What could be causing this?
No such file or directory/.bashrc
Good afternoon dear experts. Help solve the issue. I run the sh file (with rights) through the terminal, I get No such file or directory/.bashrc Google didn't help. I'm beating this wall for the 3rd evening). sh file content: ` source ~/.bashrc cd ~/data python file.py ` Contents of the .bashrc file: ` # .bashrc export PATH="~/.pyenv/bin:$PATH" eval "$(pyenv init -)" eval "$(pyenv virtualenv-init -)" # Source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi # Uncomment the following line if you don't like systemctl's auto-paging feature: # export SYSTEMD_PAGER= # User specific aliases and functi # >>> conda initialize >>> # !! Contents within this block are managed by 'conda init' !! __conda_setup="$('/home/ec2-user/.pyenv/versions/anaconda3-2020.11/bin/conda' 'shell.bash' 'hook' 2> /dev/null)" if [ $? -eq 0 ]; then eval "$__conda_setup" else if [ -f "/home/ec2-user/.pyenv/versions/anaconda3-2020.11/etc/profile.d/conda.sh" ]; then . "/home/ec2-user/.pyenv/versions/anaconda3-2020.11/etc/profile.d/conda.sh" else export PATH="/home/ec2-user/.pyenv/versions/anaconda3-2020.11/bin:$PATH" fi fi unset __conda_setup # <<< conda initialize <<< `
How to use codecommit submodules in CodeBuild
I am trying to use CodeBuild with submodule in CodeCommit repository, but when the build reach **DOWNLOAD_SOURCE** phase, I got following error: > Submodule error repository not found for primary source and source version refs/heads/master I used the relative path in submodule registration like `../another-repository`. In the documentation of CodeBuild, I can't find anything about usages of submodules, nor anything to the *git submodules* checkbutton in Source setup section. How to use submodules correctly in CodeBuild?
Does Git-LFS (Large File Storage) have support in Code Commit?
Does AWS Code Commit have support for git-lfs? There are many modern day use cases where committing large files to git makes sense. These are all explained on the official site: [git-lfs](https://git-lfs.github.com/) Many of the other code repository services support this. It feels well overdue for Code Commit to catch up. There is an old AWS forum post that explains the history of this request: [forum](https://forums.aws.amazon.com/thread.jspa?messageID=785850#785850) A useful and intuitive approach would be to use an S3 bucket as the actual backing store so that costs can be controlled. Linking the repo to S3 that way would make sense.