text:
Pixel2mesh training loss plateaus

Hello,
First of all, thanks for your amazing work!
I am currently trying to train your pixel2mesh implementation, but I am not able to obtain decent results and I was wondering if you changed something that is not tunable from its config file.
The code I am using doesn't have any modification and I downloaded your pre-processed data. After epoch 8 the loss plateaus around 30 and oscillates around that value at least until epoch 50 (then I stopped the training because didn't look like it was going to get better).
Here you can find the visualisation of a prediction and its GT at epoch 50.

Thanks in advance for your time.

Hi @simofoti,
thanks for reporting the issue - we will look into it! Maybe something was broken, when we prepared the public code release.
For reference: when we trained the model we achieved a training loss of about 4.
Sample visualization of prediction:

Hi @LMescheder,
Thanks for your quick answer! Your results looks much better for sure :)
Yesterday I launched another training  with the learning rate and weight decay reported in their original paper. It reached epoch 40 with a loss again around 30, but this time seems to be still decreasing (really slowly). Hopefully it is just a matter of training for longer... I'll let you know if I have any success.
Thanks for giving me some reference.

Hi @simofoti,
thanks for providing feedback!
We cloned this github repo yesterday night and started a new training for a pixel2mesh model with the config file provided in configs/img/pixel2mesh.yaml. These results indicate that training progresses as usual. For reference, below you can see the loss and the visualization for your example after one night of traning (~50k Iterations, Epoch 19).
Could it be that changed the pixel2mesh config or that something broke during the data downloading process?
Best of luck!

Hello,
Thanks for looking into it. I was able to make it work with my data and I stopped experimenting with ShapeNet. Now I have some time and I am trying to re-run the training on ShapeNet cloning again the repo and using the pre-processed data. I should be able to get some results tomorrow. I will let you know if I obtain the something.
PS. Just to let you know... OccupancyNet worked properly

Hello @m-niemeyer,
I have run the training over the whole weekend but I still don't get the same results as yours.
These are the steps I followed:

I cloned your repo again
Since I already had the environment in place, I have just compiled the extension modules
I executed the download script and it looks like it downloaded and unpacked the data automatically into the data/ShapeNet folder.
I started the training with python train.py config/img/pixel2mesh.yaml

Here is what I get:
Training loss:

Validation losses:

Prediction:

GT:

After the training I checked if something was different in the code (just to be sure that I didn't accidentally change something), but the repo is up-to-date with your origin/master branch (which seems to be the only one you released).
Do you have any idea of what could possibly go wrong?
Thanks in advance.

Hi @simofoti ,
thanks for your detailed report. To check again that our provided code and data works, I followed the complete pipeline as indicated in the readme. That is, cloning the repo, creating the anaconda environment, building the extensions, and downloading the provided data. After one night of training, the loss and visualizations looks the same as before (see below), hence it worked fine for me.

As it works fine for me, it is quite hard to "debug" what is going wrong in your case.
First, I would try to delete everything (including the anaconda environment and all cached packages) and follow the procedure again (you can also rename the environment to be sure). To do this, run conda env remove --name mesh_funcspaceandconda clean --all`. You can rename the environment in the environment.yaml file.
Good luck!

Problem seems to be resolved. Closing for now.

Could be related: #31

Hello @m-niemeyer,
I have run the training over the whole weekend but I still don't get the same results as yours.
These are the steps I followed:
...
The download script, as I said above, copied the data in the right folder. No errors were thrown by the script and for each object of each class in ShapeNet I have:

24 views,
the camera parameters (cameras.npz),
model.binvox,
pointcloud.npz,
points.npz.

Do you have any idea of what could possibly go wrong?
Thanks in advance.

Hello, @LMescheder , @simofoti and @m-niemeyer , I was trying to train pixel2mesh network out of the dataset constructed by my own. But after the data preprocessing according to this project, I found that for each object folder the camera parameters file (cameras.npz) does not exist. Could you please show me how to generate the camera parameters files (cameras.npz)? Thanks a lot

Hello,
First of all, thanks for your amazing work!
I am currently trying to train your pixel2mesh implementation, but I am not able to obtain decent results and I was wondering if you changed something that is not tunable from its config file.
The code I am using doesn't have any modification and I downloaded your pre-processed data. After epoch 8 the loss plateaus around 30 and oscillates around that value at least until epoch 50 (then I stopped the training because didn't look like it was going to get better).
Here you can find the visualisation of a prediction and its GT at epoch 50.

Thanks in advance for your time.

hi, when I trying to train pixel2mesh implementation,  I have the following problems
Visualizing
Traceback (most recent call last):
File "train.py", line 135, in
trainer.visualize(data_vis)
File "/home/zyz/Project/occupancy_networks/im2mesh/pix2mesh/training.py", line 287, in visualize
points_out = common.transform_points_back(pred_vertices_3, world_mat)
File "/home/zyz/Project/occupancy_networks/im2mesh/common.py", line 228, in transform_points_back
points_out = points_out @ b_inv(R.transpose(1, 2))
File "/home/zyz/Project/occupancy_networks/im2mesh/common.py", line 209, in b_inv
b_inv, _ = torch.gesv(eye, b_mat)
AttributeError: module 'torch' has no attribute 'gesv'
you have encountered this problem? I am looking forward to your help

I have the same issues as the OP. Below are the training graphs, and an example of a final reconstructed mesh. I also tried training a model on the car class only, and saw similar results.

Hi, the problem might be related to this file ordering issue. If this was the case, it should be fixed now. Thanks!

authors: LMescheder YokkaBear b7leung m-niemeyer simofoti zyz-1998


text:
fix(autoware_carla_interface): include "modules" submodule in release package and update setup.py

Description
This PR fixes an issue where the autoware_carla_interface package failed to include the "modules" submodule in the release package. This omission caused the following runtime error in the official universe-cuda Docker image:
ModuleNotFoundError: No module named 'autoware_carla_interface.modules'
The fix involves updating setup.py to:

Use find_packages(where="src") to automatically detect and include the "modules" subpackage.
Correct paths in data_files to comply with ROS 2 packaging conventions.

This ensures that the autoware_carla_interface module is properly packaged and resolves the runtime error.
Related links
Parent Issue:
None
How was this PR tested?

Built a Docker image based on this commit.
Verified the autoware_carla_interface module connects to CARLA Simulator without the ModuleNotFoundError.
Ensured compatibility with the ROS 2 colcon build system by running colcon build and confirming successful packaging.

Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.

Updated to latest main to make CI pass.
Reason:

https://github.com/autowarefoundation/autoware.universe/pull/9520#pullrequestreview-2477871346

source: gharchive/pull-request

authors: JesusAnaya xmfcx

license_type: permissive

license_source: github-api


text:
Migrate to GitHub Actions

Removes dependency on another platform (Travis) which recently silently broke.

Branch protection rule added for the master branch requiring approving review and CI checks to pass in order to merge.

Validated that binding to environment secret in a job w/o the environment set cannot access the secret:
https://github.com/auvsi-suas/interop/actions/runs/690058838
Validated that setting the environment on a non-protected branch is not allowed:
https://github.com/auvsi-suas/interop/actions/runs/690088975

Validated that the master branch can leverage the environment & seret:
https://github.com/auvsi-suas/interop/actions/runs/690104583
Removed environment review requirements so that it happens automatically, and because there isn't an admin override and we don't have additional reviewers at this time.

Successful push to Dockerhub. Revoked the Travis access token.

Uninstalled Travis app.

Deploy successful, migration complete.

source: gharchive/issue

repo: auvsi-suas/interop

license_source: bigquery


text:
ostimer unit test needs non-zero stack size parameter passed to OS_TaskCreate

The call to OS_TaskCreate in ostimer-test.c needs a non-zero stack-size.

Imported from trac issue 144.  Created by sseeger on 2016-01-06T13:12:59, last modified: 2016-01-14T11:33:37

Trac comment by sstrege on 2016-01-08 17:48:52:
Changeset [changeset:63116f2] ready for CCB review

Trac comment by sseeger on 2016-01-10 22:36:02:
I'm just here taking up space. Don't mind me (comment erased)

Trac comment by jphickey on 2016-01-11 14:31:23:
recommend accept

Trac comment by glimes on 2016-01-11 12:17:17:
recommend accept.

Trac comment by glimes on 2016-01-14 11:31:23:
Included in the 2016-01-11 CCB merge.

Trac comment by glimes on 2016-01-14 11:33:37:
Development advanced to include the 2016-01-11 merge.


text:
Create file7

@radlee

@radlee I was told to add a question not and answer

great!

repo: avermeulen/GitFlowPractise

license: MIT


text:
Pair Sum Problem Optimized

Hi, I am a participant of Hacktoberfest. I would like to add this question of pair sum which can be solved with the help of sets. Kindly assign me this issue under hacktoberfest. Thank you.
Question:
Find the pair which gives the sum same as assigned number
Input:  [1,4,6,2,5,3,0]
n=3
Output: [1,2]

Hii. please assign this to me. I will solve this issue as I am experienced in c++.


text:
A script to delete selected pages from PDF

Aim

A script that will delete input pages from a PDF file

Details

It will be a simple script using pdfrw or some other small python library and will remove the pages that the user enters as arguments from stdin.

I would want to work on this issue for SWOC.
Please assign this to me :)

I would want to work on this issue for SWOC.
Please assign this to me :)

Sure Go ahead @Rahul555-droid

Sure Go ahead @Rahul555-droid

repo: avinashkranjan/Amazing-Python-Scripts


text:
Certificate Generator

Aim

Generate thousands of certificates at just one click

Details

We need a list of names in CSV  we want to print it simple draw name in the image here

@kaustubhgupta  please assign me this issue

Can you provide the functionalities to add our own custom certificate and then generate others?

Can you provide the functionalities to add our own custom certificate and then generate others?

@kaustubhgupta No sir I can't  custom certificate user need add own certificate.

@soumik2012 hmm, okay then give it a try,

@soumik2012 Sorry for the confusion, this implementation already exist: https://github.com/avinashkranjan/Amazing-Python-Scripts/tree/master/Automatic Certificate Generator


text:
Progress Graph added

Description
The Assignment Progress Chart is a new feature added to the Home Screen of the app. It allows users to track their assignment progress visually through a chart representation. The chart displays the scores of completed assignments over time, helping users to monitor their performance and identify trends.
Here is the demo Screenshot -

The chart is placed within the Home Screen, providing users with a comprehensive overview of their recent alerts and homework, along with the visual representation of their assignment progress. The feature enhances the user experience by providing an intuitive and engaging way to track progress.
Additionally, the feature includes labels for the horizontal and vertical lines in the chart. The horizontal line is labeled as "Progress Line" to indicate the trend of assignment scores over time. The vertical line is labeled as "Score Reference Line" to provide a reference for score comparison at each data point.
Fixes #64
Have you read the Contributing Guidelines on Pull Requests?

Yes
[ ] No

Type of change

New feature (non-breaking change which adds functionality)

Checklist:

My code follows the style guidelines(Clean Code) of this project
I have performed a self-review of my own code
My changes generate no new warnings
I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

Resolve the Conflicts @andoriyaprashant

i think the conflicts are bcz of this

It seems that in a previous merged pull request, some dependencies were accidentally removed by someone, which resulted in merge conflicts between the branch of my pull request and the main branch.
I create an issue on this and solve it, maybe after that there won't be any merge conflicts in my pull request.
Thank you @avinashkranjan

I have re-added the dependencies. You can review them in this pull request #331 . After merging this, it will also resolve the merge conflicts with this pull request.
Thank you

Hello @avinashkranjan I have now resolved the merge conflicts that were occurring due to the 'home_screen.dart' file. Please take a look at them once

authors: andoriyaprashant avinashkranjan

repo: avinashkranjan/Friday


text:
(#60) - About layout does not respond on orientation change

Added ScrollView, so on orientation change user can scroll to see more

One change i would suggest is to exclude the toolbar from the linear layout, so it doesn't scroll away when the user scrolls down.
The view hierarchy i would suggest is-

Linear Layout

toolbar
Scroll View

Linear Layout (the rest of the layout)

@madscientist001 +1 Thanks Man!! updated the file, excluded ToolBar from ScrollView

repo: avjinder/Minimal-Todo

license: mit


text:
Update dependency ansible to v9

This PR contains the following updates:

Package
Type
Update
Change

ansible (source)
dependencies
major
^8.0.0 -> ^9.0.0

Release Notes

ansible-community/ansible-build-data
v9.0.1
Compare Source
v9.0.0
Compare Source
v8.6.1
Compare Source
v8.6.0
Compare Source

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: poetry.lock
Installing v1 tool poetry v1.7.1

  File "<stdin>", line 1
    404: Not Found
    ^^^
SyntaxError: illegal target for annotation

repo: avnes/ansible-role-kubectx


text:
Dynamic Component support for Page Create/Edit

we need a way to render dynamic component on page create/edit page. so dynamic component can be added and removed.

backend api is done.

repo: avored/avored-rust-cms


text:
feat: Set default to null when the field type is nullable (activable by the configuration)

Quick PR that have no impact on the existing features. I hope you will release it before the work of primitives in root :pray:

@Chuckame, do you want to join me in maintaining this repo?

@thake yes, why not!!

Thanks for the PR a really useful addition. It will certainly be merged before primitive types.

Good idea, did you worked on it since the last commit to your primitives in root branch?

Thanks for the PR a really useful addition. It will certainly be merged before primitive types.

Good idea, did you worked on it since the last commit to your primitives in root branch?

No, not yet. If you want, you can give it a try.

Yes I begun something similar to Json, proto, and other native serializers. I would like to lighten the Avro class, make some extensions and make it more configurable (starting with this pr)

By the way, how do you want me to make releases? That way we add a CONTRIBUTING.md 😁

By the way, how do you want me to make releases? That way we add a CONTRIBUTING.md grin

I've opened up an issue #143 for that. Maybe we'll have to change something on the release workflow.

Yes I begun something similar to Json, proto, and other native serializers. I would like to lighten the Avro class, make some extensions and make it more configurable (starting with this pr)

That sounds really awesome :) Do you want to talk me through before? That way I can give you some input and work out a solution together. You can find my contact details on my github profile, I think we should discuss this "face to face".

authors: Chuckame thake


text:
curl: 7.83.1 -> 7.86.0

Fixes:

CVE-2022-27779
CVE-2022-27780
CVE-2022-27781
CVE-2022-27782
CVE-2022-30115
CVE-2022-32205
CVE-2022-32206
CVE-2022-32207
CVE-2022-32208
CVE-2022-32221
CVE-2022-35252
CVE-2022-42915
CVE-2022-42916
CVE-2022-43551
CVE-2022-43552
CVE-2023-23914
CVE-2023-23915
CVE-2023-23916
CVE-2023-27533
CVE-2023-27534
CVE-2023-28319
CVE-2023-28320
CVE-2023-28321

There is one coming next week also (https://github.com/curl/curl/discussions/12026)

There is one coming next week also (https://github.com/curl/curl/discussions/12026)

Oh good call! Thank you!

repo: awakesecurity/nixpkgs


text:
Add a new blackbar detection mode for subtitles

Feature request

What problem does this feature solve?
When watching a movie with blackbars, subtitles un-trigger the detection and top and bottom LEDs are turned of, except for white where the subtitles are.
What does the proposed API look like?
How should this be implemented in your opinion?
Instead of detecting blackbars based on the whole red area, the bottom zone should be split in the middle, something like the green area

Are you willing to work on this yourself?
Sure I can write a little C++, but testing is a bit more complicated since HyperHDR is running on my webOS TV.

I was looking into this a little for myself, as I was having the same issue. I switched my blackbar detector to use letterbox mode and it solved (most) of my issues. (The only issue that remains is the case represented in your screenshot when there are 2 lines of subtitles - the bottom line is successfully ignored, but the top line will form part of the "image" and cause more white lighting than just the video content alone. This is a reasonable compromise though IMO.)
The original PR (here) that implemented the letterbox mode has a good screenshot to demonstrate how it works - at the top it checks points at 25%, 50%, and 75% across, and at the bottom only 25% and 75% (to avoid subtitles interfering, similar to how your screenshot suggests):

However I propose that the thresholds at the bottom should be user configurable - 25%/75% is a reasonable default, but I'd like to be able to use 15%/85% or 20%/80% for some content. And perhaps the documentation can clarify that it does actually make an effort to avoid the subtitle region.
I almost think there's an argument to rename letterbox mode to something like cinema (i.e. implying it's not just the letterbox black bars, but makes room for subtitles in TV/movies - which I think is a better default for most users), and default could get renamed to be more descriptive (like simple or naive). But that's a whole 'nother discussion out of scope of this issue.

Sorry for the silence on the subject for now but currently I'm working on LUT calibration. I have this feature in mind with the fact that... why should we limit ourselves? let the user activate as many scanlines as he needs from the pool available (every 10%)  at the top and bottom. this doesn't burden the processor so much even in the case of RPi. Blackborderdetection would have to be completely rewritten, but this is even better. Since I don't use this module I only have a doubt whether we should assume that the blackborder at the top has exactly the same height as the one at the bottom (+/- 2-3 pixels)? And if many vertical lines (from top and bottom) are enough or oblique are still necessary?

The only issue that remains is the case represented in your screenshot when there are 2 lines of subtitles - the bottom line is successfully ignored, but the top line will form part of the "image" and cause more white lighting than just the video content alone.

I know it's not what's being explicitly discussed in this issue, but I would love a solution to this, as I watch most things with subtitles enabled.
A naive implementation might be for the user to specify the color of the subtitle and its outline, and have HyperHDR ignore any pixels near the bottom of the screen that match those two colors when calculating the color to send to the LED.

authors: Jerroder awawa-dev chcore notjosh

repo: awawa-dev/HyperHDR


text:
Accents

Hi there,
I love this plugin, but I have one request. Would it be possible to broaden the search for accented characters in foreign language?
Let me explain with one concrete example:
In Spanish, I want to look for the word "adaptation", which would translate to "adaptación". If I type "adaptación", it works as expected. Now if I type "adaptacion", .i.e. without the accent on the "a", it fails to recognize that term.
In Spanish it is (unfortunately) a common practice to omit accents when searching for something because it requires for extra keystroke, and people are lazy.
Thanks.

+1

Hi, add this code to the plugin:

		var rExps = [{
			re: /[\xC0-\xC6]/g,
			ch: "A"
		}, {
			re: /[\xE0-\xE6]/g,
			ch: "a"
		}, {
			re: /[\xC8-\xCB]/g,
			ch: "E"
		}, {
			re: /[\xE8-\xEB]/g,
			ch: "e"
		}, {
			re: /[\xCC-\xCF]/g,
			ch: "I"
		}, {
			re: /[\xEC-\xEF]/g,
			ch: "i"
		}, {
			re: /[\xD2-\xD6]/g,
			ch: "O"
		}, {
			re: /[\xF2-\xF6]/g,
			ch: "o"
		}, {
			re: /[\xD9-\xDC]/g,
			ch: "U"
		}, {
			re: /[\xF9-\xFC]/g,
			ch: "u"
		}, {
			re: /[\xC7-\xE7]/g,
			ch: "c"
		}, {
			re: /[\xD1]/g,
			ch: "N"
		}, {
			re: /[\xF1]/g,
			ch: "n"
		}];
		$.each(rExps, function() {
			filter = filter.replace(this.re, this.ch);
			innerText = innerText.replace(this.re, this.ch);
		});

before :

if (innerText.toLowerCase().indexOf(filter) >= 0) {

authors: Thunderlab jacmaes rodolfobubb

repo: awbush/jquery-fastLiveFilter


text:
🛑 Puzzle API is down

In 8b600da, Puzzle API (https://api.puzzle.techtd.com.br/alive) was down:

HTTP code: 502
Response time: 739 ms

Resolved: Puzzle API is back up in de206ae after 11 minutes.

repo: aweiand/puzzle-status


text:
🛑 Site IFRS is down

In 5cc7df4, Site IFRS (https://ifrs.edu.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Site IFRS is back up in 64a9b77.

repo: aweiand/status-ifrs-osorio


text:
chore: bump data-schema deps

Changes

Minor version bump to data-schema packages
Validation

ran build, test, update:api, manually sanity-checked lockfile changes.

Checklist

[ ] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
[ ] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
[ ] If this PR requires a docs update, I have linked to that docs PR above.
[ ] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Can you try merging main and see if that fixes the PR check?

authors: edwardfoyle iartemiev

repo: aws-amplify/amplify-backend


text:
refactor: improved placeholders for error messages

Problem

Issue number, if available:
closes #1271
Changes

use named capturing groups and replace all {captureGroupName} placeholders with the matching value.
Corresponding docs PR, if applicable:
Validation

Checklist

[ ] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
[ ] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
[ ] If this PR requires a docs update, I have linked to that docs PR above.
[ ] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@Amplifiyer @awsluja
Thank you for your review and suggestion.

Thanks @fossamagna, please merge from main to make the github checks happy. We can then merge this.

@Amplifiyer I merged from main. Thanks.

authors: Amplifiyer fossamagna


text:
Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1

How did you install the Amplify CLI?
curl
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
10.5.2
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
I really did nothing I was just setting up Amplify for using it to upload some files to my s3 Bucket from the Android Mobile App.
Describe the bug
So basically the title says it all, "Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1"

Expected behavior
I was expecting the command I typed to put the required files in the deployment bucket.
Reproduction steps
I typed the following command after configuring Amplify with the command amplify configure:
amplify init
Project Identifier
9238984c8987c8a8b06cc18733f7beff
Log output

# Put your logs below this line

2023-01-03T19:15:16.025Z|info : amplify status core  {"yes":false}
2023-01-03T19:15:16.097Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-01-03T19:15:20.254Z|error : File at path: 'D:\80gb_2\Private\Desktop\University_Work\Senior_Year_Project\QuranTutor1218\QuranTutor\QuranTutor\amplify\#current-cloud-backend\amplify-meta.json' does not exist
UnknownFault: File at path: 'D:\80gb_2\Private\Desktop\University_Work\Senior_Year_Project\QuranTutor1218\QuranTutor\QuranTutor\amplify\#current-cloud-backend\amplify-meta.json' does not exist
2023-01-03T19:22:51.769Z|info : amplify env core
2023-01-03T19:23:01.989Z|info : amplify env core list
2023-01-03T19:23:02.120Z|error : Current environment cannot be determined.
EnvironmentNotInitializedError: Current environment cannot be determined.
2023-01-03T19:23:41.393Z|info : amplify env core list
2023-01-03T19:23:41.541Z|error : Current environment cannot be determined.
EnvironmentNotInitializedError: Current environment cannot be determined.
2023-01-03T19:46:39.558Z|info : amplify env core
2023-01-03T19:47:02.569Z|info : amplify env core get {"name":"[***]an","yes":false}
2023-01-03T19:48:39.767Z|info : amplify pull core  {"appId":"[***]y3xqfc","envName":"[***]an","yes":false}
2023-01-03T19:48:39.819Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-01-03T19:48:41.181Z|error : Backup folder at D:\80gb_2\Private\Desktop\University_Work\Senior_Year_Project\QuranTutor1218\QuranTutor\QuranTutor\amplify-backup already exists, remove the folder and retry the operation.
DirectoryAlreadyExistsError: Backup folder at D:\80gb_2\Private\Desktop\University_Work\Senior_Year_Project\QuranTutor1218\QuranTutor\QuranTutor\amplify-backup already exists, remove the folder and retry the operation.
2023-01-03T19:50:33.517Z|info : amplify init core
2023-01-03T19:50:33.575Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-01-03T19:51:23.319Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileRegion(["default"])
2023-01-03T19:51:23.323Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["default"])
2023-01-03T19:51:23.345Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileRegion(["default"])
2023-01-03T19:51:23.346Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["default"])
2023-01-03T19:51:23.358Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2023-01-03T19:51:23.362Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]utor-[***]an-[***]404-[***]ment"}])
2023-01-03T19:51:32.011Z|error : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
2023-01-03T19:51:34.376Z|error : Could not initialize platform for 'quran': Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
ProjectInitFault: Could not initialize platform for 'quran': Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
2023-01-03T19:52:52.256Z|info : amplify help core
2023-01-03T20:01:37.201Z|info : amplify init core
2023-01-03T20:01:37.265Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-01-03T20:01:48.221Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2023-01-03T20:01:48.224Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]utor-[***]an-[***]404-[***]ment"}])
2023-01-03T20:01:49.394Z|error : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
NoSuchKey: The specified key does not exist.
2023-01-03T20:01:51.731Z|error : Could not initialize platform for 'quran': The specified key does not exist.
ProjectInitFault: Could not initialize platform for 'quran': The specified key does not exist.
2023-01-03T20:02:02.455Z|info : amplify env core list
2023-01-03T20:05:20.592Z|info : amplify env core
2023-01-03T20:05:36.018Z|info : amplify env core add
2023-01-03T20:06:21.365Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileRegion(["default"])
2023-01-03T20:06:21.366Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["default"])
2023-01-03T20:06:21.376Z|info : amplify-provider-awscloudformation.amplify-service-permission-check.checkAmplifyServiceIAMPermission.amplifyClient.listApps([])
2023-01-03T20:06:22.595Z|info : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.listApps([{"maxResults":25}])
2023-01-03T20:06:23.424Z|info : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.getBackendEnvironment([{"appId":"[***]y3xqfc","environmentName":"[***]or"}])
2023-01-03T20:06:24.214Z|error : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.getBackendEnvironment([{"appId":"[***]y3xqfc","environmentName":"[***]or"}])
NotFoundException: BackendEnvironment tutor does not exist.
2023-01-03T20:06:24.215Z|info : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.getBackendEnvironment([{"appId":"[***]y3xqfc","environmentName":"[***]or","stackName":"[***]ify-[***]utor-[***]or-[***]21","deploymentArtifacts":"amplify-qurantutor-tutor-10621-deployment"}])
2023-01-03T20:06:24.994Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileRegion(["default"])
2023-01-03T20:06:24.995Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["default"])
2023-01-03T20:06:25.016Z|info : amplify-provider-awscloudformation.aws-cfn.cfnModel.createStack([{"StackName":"[***]ify-[***]utor-[***]or-[***]21","Capabilities":["CAPABILITY_NAMED_IAM","CAPABILITY_AUTO_EXPAND"],"TemplateBody":"{\n  \"AWSTemplateFormatVersion\": \"2010-09-09\",\n  \"Description\": \"{\\\"createdOn\\\":\\\"Windows\\\",\\\"createdBy\\\":\\\"Amplify\\\",\\\"createdWith\\\":\\\"10.5.2\\\",\\\"stackType\\\":\\\"root\\\",\\\"metadata\\\":{}}\",\n  \"Parameters\": {\n    \"[***]cketName\": {\n      \"Description\": \"Name of the common deployment bucket provided by the parent stack\",\n      \"Type\": \"String\",\n      \"Default\": \"DeploymentBucket\"\n    },\n    \"[***]eName\": {\n      \"Type\": \"String\",\n      \"Default\": \"AuthRoleName\"\n    },\n    \"[***]leName\": {\n      \"Type\": \"String\",\n      \"Default\": \"UnauthRoleName\"\n    }\n  },\n  \"Resources\": {\n    \"DeploymentBucket\": {\n      \"Type\": \"AWS::S3::Bucket\",\n      \"DeletionPolicy\": \"Retain\",\n      \"Properties\": {\n        \"BucketName\": {\n          \"Ref\": \"DeploymentBucketName\"\n        },\n        \"BucketEncryption\": {\n          \"ServerSideEncryptionConfiguration\": [\n            {\n              \"ServerSideEncryptionByDefault\": {\n                \"SSEAlgorithm\": \"AES256\"\n              }\n            }\n          ]\n        }\n      }\n    },\n    \"AuthRole\": {\n      \"Type\": \"AWS::IAM::Role\",\n      \"Properties\": {\n        \"RoleName\": {\n          \"Ref\": \"AuthRoleName\"\n        },\n        \"AssumeRolePolicyDocument\": {\n          \"Version\": \"2012-10-17\",\n          \"Statement\": [\n            {\n              \"Sid\": \"\",\n              \"Effect\": \"Deny\",\n              \"Principal\": {\n                \"Federated\": \"cognito-identity.amazonaws.com\"\n              },\n              \"Action\": \"sts:AssumeRoleWithWebIdentity\"\n            }\n          ]\n        }\n      }\n    },\n    \"UnauthRole\": {\n      \"Type\": \"AWS::IAM::Role\",\n      \"Properties\": {\n        \"RoleName\": {\n          \"Ref\": \"UnauthRoleName\"\n        },\n        \"AssumeRolePolicyDocument\": {\n          \"Version\": \"2012-10-17\",\n          \"Statement\": [\n            {\n              \"Sid\": \"\",\n              \"Effect\": \"Deny\",\n              \"Principal\": {\n                \"Federated\": \"cognito-identity.amazonaws.com\"\n              },\n              \"Action\": \"sts:AssumeRoleWithWebIdentity\"\n            }\n          ]\n        }\n      }\n    }\n  },\n  \"Outputs\": {\n    \"Region\": {\n      \"Description\": \"CloudFormation provider root stack Region\",\n      \"Value\": {\n        \"Ref\": \"AWS::Region\"\n      },\n      \"Export\": {\n        \"Name\": {\n          \"Fn::Sub\": \"${AWS::StackName}-Region\"\n        }\n      }\n    },\n    \"StackName\": {\n      \"Description\": \"CloudFormation provider root stack ID\",\n      \"Value\": {\n        \"Ref\": \"AWS::StackName\"\n      },\n      \"Export\": {\n        \"Name\": {\n          \"Fn::Sub\": \"${AWS::StackName}-StackName\"\n        }\n      }\n    },\n    \"StackId\": {\n      \"Description\": \"CloudFormation provider root stack name\",\n      \"Value\": {\n        \"Ref\": \"AWS::StackId\"\n      },\n      \"Export\": {\n        \"Name\": {\n          \"Fn::Sub\": \"${AWS::StackName}-StackId\"\n        }\n      }\n    },\n    \"DeploymentBucketName\": {\n      \"Description\": \"CloudFormation provider root stack deployment bucket name\",\n      \"Value\": {\n        \"Ref\": \"DeploymentBucketName\"\n      },\n      \"Export\": {\n        \"Name\": {\n          \"Fn::Sub\": \"${AWS::StackName}-DeploymentBucketName\"\n        }\n      }\n    },\n    \"AuthRoleArn\": {\n      \"Value\": {\n        \"Fn::GetAtt\": [\n          \"AuthRole\",\n          \"Arn\"\n        ]\n      }\n    },\n    \"UnauthRoleArn\": {\n      \"Value\": {\n        \"Fn::GetAtt\": [\n          \"UnauthRole\",\n          \"Arn\"\n        ]\n      }\n    },\n    \"AuthRoleName\": {\n      \"Value\": {\n        \"Ref\": \"AuthRole\"\n      }\n    },\n    \"UnauthRoleName\": {\n      \"Value\": {\n        \"Ref\": \"UnauthRole\"\n      }\n    }\n  }\n}","Parameters":[{"ParameterKey":"DeploymentBucketName","ParameterValue":"amplify-qurantutor-tutor-10621-deployment"},{"ParameterKey":"AuthRoleName","ParameterValue":"amplify-qurantutor-tutor-10621-authRole"},{"ParameterKey":"UnauthRoleName","ParameterValue":"amplify-qurantutor-tutor-10621-unauthRole"}],"Tags":[{"Key":"[***]tack","Value":"quran"},{"Key":"[***]ication","Value":"QuranTutor"}]}])
2023-01-03T20:06:26.523Z|info : amplify-provider-awscloudformation.aws-cfn.cfnModel.createStack([{"StackName":"[***]ify-[***]utor-[***]or-[***]21","Capabilities":["CAPABILITY_NAMED_IAM","CAPABILITY_AUTO_EXPAND"],"TemplateBody":"{\n  \"AWSTemplateFormatVersion\": \"2010-09-09\",\n  \"Description\": \"{\\\"createdOn\\\":\\\"Windows\\\",\\\"createdBy\\\":\\\"Amplify\\\",\\\"createdWith\\\":\\\"10.5.2\\\",\\\"stackType\\\":\\\"root\\\",\\\"metadata\\\":{}}\",\n  \"Parameters\": {\n    \"[***]cketName\": {\n      \"Description\": \"Name of the common deployment bucket provided by the parent stack\",\n      \"Type\": \"String\",\n      \"Default\": \"DeploymentBucket\"\n    },\n    \"[***]eName\": {\n      \"Type\": \"String\",\n      \"Default\": \"AuthRoleName\"\n    },\n    \"[***]leName\": {\n      \"Type\": \"String\",\n      \"Default\": \"UnauthRoleName\"\n    }\n  },\n  \"Resources\": {\n    \"DeploymentBucket\": {\n      \"Type\": \"AWS::S3::Bucket\",\n      \"DeletionPolicy\": \"Retain\",\n      \"Properties\": {\n        \"BucketName\": {\n          \"Ref\": \"DeploymentBucketName\"\n        },\n        \"BucketEncryption\": {\n          \"ServerSideEncryptionConfiguration\": [\n            {\n              \"ServerSideEncryptionByDefault\": {\n                \"SSEAlgorithm\": \"AES256\"\n              }\n            }\n          ]\n        }\n      }\n    },\n    \"AuthRole\": {\n      \"Type\": \"AWS::IAM::Role\",\n      \"Properties\": {\n        \"RoleName\": {\n          \"Ref\": \"AuthRoleName\"\n        },\n        \"AssumeRolePolicyDocument\": {\n          \"Version\": \"2012-10-17\",\n          \"Statement\": [\n            {\n              \"Sid\": \"\",\n              \"Effect\": \"Deny\",\n              \"Principal\": {\n                \"Federated\": \"cognito-identity.amazonaws.com\"\n              },\n              \"Action\": \"sts:AssumeRoleWithWebIdentity\"\n            }\n          ]\n        }\n      }\n    },\n    \"UnauthRole\": {\n      \"Type\": \"AWS::IAM::Role\",\n      \"Properties\": {\n        \"RoleName\": {\n          \"Ref\": \"UnauthRoleName\"\n        },\n        \"AssumeRolePolicyDocument\": {\n          \"Version\": \"2012-10-17\",\n          \"Statement\": [\n            {\n              \"Sid\": \"\",\n              \"Effect\": \"Deny\",\n              \"Principal\": {\n                \"Federated\": \"cognito-identity.amazonaws.com\"\n              },\n              \"Action\": \"sts:AssumeRoleWithWebIdentity\"\n            }\n          ]\n        }\n      }\n    }\n  },\n  \"Outputs\": {\n    \"Region\": {\n      \"Description\": \"CloudFormation provider root stack Region\",\n      \"Value\": {\n        \"Ref\": \"AWS::Region\"\n      },\n      \"Export\": {\n        \"Name\": {\n          \"Fn::Sub\": \"${AWS::StackName}-Region\"\n        }\n      }\n    },\n    \"StackName\": {\n      \"Description\": \"CloudFormation provider root stack ID\",\n      \"Value\": {\n        \"Ref\": \"AWS::StackName\"\n      },\n      \"Export\": {\n        \"Name\": {\n          \"Fn::Sub\": \"${AWS::StackName}-StackName\"\n        }\n      }\n    },\n    \"StackId\": {\n      \"Description\": \"CloudFormation provider root stack name\",\n      \"Value\": {\n        \"Ref\": \"AWS::StackId\"\n      },\n      \"Export\": {\n        \"Name\": {\n          \"Fn::Sub\": \"${AWS::StackName}-StackId\"\n        }\n      }\n    },\n    \"DeploymentBucketName\": {\n      \"Description\": \"CloudFormation provider root stack deployment bucket name\",\n      \"Value\": {\n        \"Ref\": \"DeploymentBucketName\"\n      },\n      \"Export\": {\n        \"Name\": {\n          \"Fn::Sub\": \"${AWS::StackName}-DeploymentBucketName\"\n        }\n      }\n    },\n    \"AuthRoleArn\": {\n      \"Value\": {\n        \"Fn::GetAtt\": [\n          \"AuthRole\",\n          \"Arn\"\n        ]\n      }\n    },\n    \"UnauthRoleArn\": {\n      \"Value\": {\n        \"Fn::GetAtt\": [\n          \"UnauthRole\",\n          \"Arn\"\n        ]\n      }\n    },\n    \"AuthRoleName\": {\n      \"Value\": {\n        \"Ref\": \"AuthRole\"\n      }\n    },\n    \"UnauthRoleName\": {\n      \"Value\": {\n        \"Ref\": \"UnauthRole\"\n      }\n    }\n  }\n}","Parameters":[{"ParameterKey":"DeploymentBucketName","ParameterValue":"amplify-qurantutor-tutor-10621-deployment"},{"ParameterKey":"AuthRoleName","ParameterValue":"amplify-qurantutor-tutor-10621-authRole"},{"ParameterKey":"UnauthRoleName","ParameterValue":"amplify-qurantutor-tutor-10621-unauthRole"}],"Tags":[{"Key":"[***]tack","Value":"quran"},{"Key":"[***]ication","Value":"QuranTutor"}]}])
2023-01-03T20:06:31.557Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:06:36.583Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:06:41.587Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:06:46.599Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:06:51.613Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:06:56.612Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:07:01.614Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:07:06.631Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:07:11.639Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:07:16.649Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:07:21.646Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:07:26.659Z|info : amplify-provider-awscloudformation.aws-cfn.getStackEvents.cfnModel.describeStackEvents([{"StackName":"[***]ify-[***]utor-[***]or-[***]21"}])
2023-01-03T20:07:29.526Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileRegion(["default"])
2023-01-03T20:07:29.526Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["default"])
2023-01-03T20:07:29.539Z|info : amplify-provider-awscloudformation.initializer.storeCurrentCloudBackend.s3.uploadFile([{"Key":"[***]rent-[***]ud-[***]d.zip"}])
2023-01-03T20:07:29.544Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"D:\\80gb_2\\Private\\Desktop\\University_Work\\Senior_Year_Project\\QuranTutor1218\\QuranTutor\\QuranTutor\\amplify\\backend\\.temp\\[***]rent-[***]ud-[***]d.zip","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"#current-cloud-backend.zip","Bucket":"[***]ify-[***]utor-[***]or-[***]21-[***]ment"}])
2023-01-03T20:07:40.368Z|error : Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
DeploymentFault: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
2023-01-03T20:08:40.184Z|info : amplify version core
2023-01-03T20:16:00.360Z|info : amplify diagnose core  {"send-report":true,"yes":false}
2023-01-03T20:16:00.441Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @maq796113 :wave: thanks for raising this! It appears the Amplify CLI is unable to fetch information from your project's deployment bucket.
from the logs:
2023-01-03T19:51:32.011Z|error : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1

Can you paste the contents of amplify/.config/local-aws-info.json redacting any sensitive information? Can you confirm whether the profile noted for the target environment exists in ~/.aws/credentials?

Closing due to inactivity

repo: aws-amplify/amplify-cli


text:
Failure to clone environment when Notifications category is added

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v18.15.0
Amplify CLI Version
12.4.0
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
After adding notifications to environment by amplify notifications add using amplify add env to clone this env fails.

Expected behavior
Having notifications/analytics (Pinpoint project added) doesn't affect cloning environment.
Reproduction steps

Create main env and add Auth category.
Add notifications category
Try to clone this environment

Project Identifier
75e2f18c9b268cfb1285dcab10f7a0ff
Log output

# Put your logs below this line

Additional information
Cloning environment with following categories: API, Authentication, Functions, Storage works fine.
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @szymondobrzanski , thank you for reaching out. I was able to reproduce the issue using the following reproduction steps.

amplify init
amplify add auth with social providers. I selected Sign in with Apple
amplify add notifications which pushed auth
selected APNS with certificate as option
amplify add env
failed with

does the reproduction steps align with the configuration in your project?
marking this as bug.

Hey @ykethan, thanks for checking. Yes I can confirm that.

Hello @ykethan, @josefaidt, @ashish-aws,
We are currently in the process of preparing for the release of our application, in which Notifications play a crucial role. Unfortunately this bug is roadblock for us. We are facing difficulties with Notifications across multiple environments, including our development and production environments. Cloning the environment with the Notifications category is failing, and manually adding them to each environment is not a feasible option for us. This is because our Flutter app requires the Amplify notifications dependencies to be added beforehand.
As a result, we've had to remove this Notifications category in order to continue working on other functionalities. I kindly request that you consider increasing the priority of this bug or provide any suggestions for a workaround.
Thank you for your assistance.

authors: szymondobrzanski ykethan


text:
Allow @key to reference non-required fields

Describe the bug
Today @key doesn't allow you to reference non-mandatory fields. This can hinder other transforms and custom revolvers that might take a null field and fill in a default if no value is given.
Amplify CLI Version
4.16.1
To Reproduce
An example:
type Answer @model @key(fields: ["owner", "gameID"])
@auth(
    rules: [
        {allow: owner, ownerField: "owner"}
    ]
)
{
    owner: String
    gameID: ID!
    answer: [Int]
}

This example, fails to compile today but should compile as the resolver will auto fill the owner field in if no value is provide due to the auth resolver.
Expected behavior
I expect a flag to be able to set in the @key transform that will allow me to disable the required non-nullable check. Or this should not stop the compile and should throw a warning letting me know that there could be possible issues down the road but will allow me to still push.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Mac
Node Version: v12.13.1

See duplicate #3275

See duplicate #3275

I would disagree but it does look like it does relate/might be a duplicate of #1657

authors: RossWilliams wizage


text:
Adding Cognito user pool groups using amplify auth update to an existing Cognito resource?

Which Category is your question related to?
amplify push
Amplify CLI Version
4.27.3
What AWS Services are you utilizing?
Auth
Provide additional details e.g. code snippets
I already use Cognito in my Amplify CLI app. Can I safely add Cognito user pool groups using amplify update auth? Below is what I get when I run the update.
amplify update auth
Please note that certain attributes may not be overwritten if you choose to use defaults settings.

You have configured resources that might depend on this Cognito resource.  Updating this Cognito
resource could have unintended side effects.

Using service: Cognito, provided by: awscloudformation
 What do you want to do? (Use arrow keys)
  Apply default configuration with Social Provider (Federation)
  Walkthrough all the auth configurations
❯ Create or update Cognito user pool groups
  Create or update Admin queries API

@christodupreez adding just the user pool group to an existing cognito resource should not have any unintended consequences. This warning is specifically intended for cases changing authorization service from User Sign-Up, Sign-In, connected with AWS IAM controls to User Sign-Up & Sign-In only (Best used with a cloud API only) and vice versa.

@yuth thank you for the feedback. Will give it a try.

authors: christodupreez yuth


text:
Add Storage for multi env is creating different names

when adding storage and using multi envs it is creating different buckets but within the end a kind of random number. This is not helpful when you want to set the "arn:aws:s3:::bucket........160007-${env}/*", policy.
Now I have to add two buckets to the policy which grants dev access to prod and vice versa.
bucket55217-master
bucket60007-develop
Before is was just
bucket-master
bucket-develop
then I was able to just add this policy:
"arn:aws:s3:::bucket-${env}/*"
I am using AWS Amplify CLI 4.28.2

Hi @rpostulart
The random number  is added from the stack name to make the S3  buckets  name unique as these buckets are global. If the Id is removed , this might get bucket already exists error. I think for this you have to add the bucket names manually for the IAM policies.

Yeah of course! I have also noticed that this variable is available so I can set access:
"STORAGE_1234_BUCKETNAME": {
"Ref": "storage1234BucketName"
}

authors: akshbhu rpostulart


text:
How to update AWS::AppSync::GraphQLApi authorization type to AWS_IAM?

** Which Category is your question related to? **
api
** What AWS Services are you utilizing? **
AWS AppSync
** Provide additional details e.g. code snippets **
I try to edit the cloudformation-template.json as below:
        "GraphQLAPI": {
            "Type": "AWS::AppSync::GraphQLApi",
            "Properties": {
                "Name": {
                    "Ref": "AppSyncApiName"
                },
                "AuthenticationType": "AWS_IAM"
            }
        },

And run amplify push. But the  gql-compile transform always generate a new cloudformation template with API_KEY (or AMAZON_COGNITOR_USER_POOLS) as previous CLI configuration. So how to update AWS::AppSync::GraphQLApi authorization type to AWS_IAM?

@phanviet The Amplify CLI currently only supports API Key and Cognito security types. But we have in our roadmap to support IAM as well.

@kaustavghosh06 Thanks for inform.

Hi
Has this changed with the recent api custom stacks/resolvers update ? or is it still under development ?
Regards

@jpbourgeon  We have put out an RFC and it still is not implemented

@phanviet I find a turn around to enable AWS_IAM for AppSync, that works for me now. You can add these two cloudformation stacks to your API stack:
https://gist.github.com/eelzinaty/f2e6eaf3f8282f3d66db1a0732e5c6dd
https://gist.github.com/eelzinaty/8d013575a02245aafacaf926226a870d
Then make sure that your API parameters.json has this:
.....
.....
.....
"authRoleName": "Name of your Amplify Auth Role"

Then, you run amplify push api.
Finally, you change your appsync security in aws_export.json to AWS_IAM.
....
....
....
"aws_appsync_authenticationType": "AWS_IAM"
};

We launched multi-auth support for AppSync API (which included public APIs - with API Keys + IAM) as a part of our CLI version 3.8+.
Please take a look at our documentation around it out here for more info - https://aws-amplify.github.io/docs/cli-toolchain/graphql#public-authorization

authors: eelzinaty jpbourgeon kaustavghosh06 phanviet yuth


text:
Defer root stack creation to first amplify push

Description of changes

When running amplify init or amplify env add no root stack is created until the first amplify push. To maintain backwards compatibility with headless scripts, when doing headless init or headless env add, a root stack will be pushed immediately.
Rough implementation details are:
On init / env add (which use the same codepath), it checks if the command has args or not. If not, it does not push the root stack or initialize the amplify app
On push, if the root stack does not exist, it is created. This also involves the "onSuccess" function from amplify-cli being passed into push as a callback because we now have to execute part of the init flow on push and need access to the function after the initial push completes. Passing this in as a callback seemed preferable over trying to orchestrate an "init" call internally from the cli before starting the push, especially since only a subset of the init flow needs to run in the case of a deferred root stack push.
Issue #, if available

This is part of the work to support IAM Role permission boundaries as it gives developers a chance to configure the env before any roles are created. However, it is also a standalone DX improvement that makes init faster and less confusing (new developers won't be confused about why CFN logs are being spit out on init).
Description of how you validated changes
manually tested and added new e2e tests
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #7174 (83d81f8) into master (ec1a5a7) will decrease coverage by 0.01%.
The diff coverage is 64.63%.

@@            Coverage Diff             @@
##           master    #7174      +/-   ##
==========================================
- Coverage   51.78%   51.76%   -0.02%
==========================================
  Files         486      487       +1
  Lines       25058    25092      +34
  Branches     4915     4926      +11
==========================================
+ Hits        12976    12989      +13
- Misses      11131    11157      +26
+ Partials      951      946       -5

Impacted Files
Coverage Δ

packages/amplify-cli-core/src/index.ts
95.23% <ø> (ø)

.../src/extensions/amplify-helpers/resource-status.ts
6.33% <0.00%> (-0.03%)
:arrow_down:

...ckages/amplify-cli/src/init-steps/postInitSetup.ts
19.04% <0.00%> (-0.96%)
:arrow_down:

packages/amplify-cli/src/initialize-env.ts
10.93% <0.00%> (-0.36%)
:arrow_down:

...ackages/amplify-cli/src/init-steps/s9-onSuccess.ts
14.42% <11.11%> (+0.28%)
:arrow_up:

...rovider-awscloudformation/src/ensure-root-stack.ts
41.66% <41.66%> (ø)

...y-provider-awscloudformation/src/push-resources.ts
10.61% <50.00%> (+0.17%)
:arrow_up:

...rc/extensions/amplify-helpers/envResourceParams.ts
84.81% <66.66%> (-0.91%)
:arrow_down:

...lify-provider-awscloudformation/src/initializer.ts
53.43% <87.50%> (ø)

...rc/extensions/amplify-helpers/get-root-stack-id.ts
88.88% <100.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ec1a5a7...83d81f8. Read the comment docs.

authors: codecov-commenter edwardfoyle


text:
chore: change form validation

Description of changes:

extend existing validation instead of replacing it if custom validation function
factor out the validation tasks so that it can be reused on submit later (currently only used on change)
fix logic for getting if form is valid.
remove empty error messages on mount

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

since the errors is starting with an object can we use optional chaining for instances like below?
errorMessage={errors.name.errorMessage}
hasError={errors.name.hasError}

good call. done

Codecov Report

Merging #597 (9186148) into tagged-release/forms-and-views (e71dfd4) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@                        Coverage Diff                         @@
##           tagged-release/forms-and-views     #597      +/-   ##
==================================================================
+ Coverage                           90.73%   90.74%   +0.01%
==================================================================
  Files                                  87       87
  Lines                                3281     3285       +4
  Branches                              892      891       -1
==================================================================
+ Hits                                 2977     2981       +4
  Misses                                285      285
  Partials                               19       19

Impacted Files
Coverage Δ

...codegen-ui-react/lib/forms/form-renderer-helper.ts
91.76% <100.00%> (+0.30%)
:arrow_up:

.../codegen-ui-react/lib/forms/react-form-renderer.ts
75.96% <100.00%> (+0.23%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e71dfd4...9186148. Read the comment docs.

authors: codecov-commenter hein-j

repo: aws-amplify/amplify-codegen-ui


text:
SSL configuration is Running - [BRIEF DESCRIPTION]

App Id: d1xetpik70f8tb
Region: us-east-2
Step: SSL configuration
Status: Running

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.
Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.

authors: aminshamim brnmye

repo: aws-amplify/amplify-console


text:
SSL Configuration stuck - Route 53 domain

Before opening, please confirm:

[X] I have checked the custom domains troubleshooting guide.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
dpm5giteybegs
Region
eu-west-2
Step
SSL Configuration
Status
SSL configuration
Issue or question
Im trying to set up another domain for my app. I have my domain hosted in Route53 in the same account and i can see that both the CNAMEs are configured perfectly.
Yet the domain registration is still stuck on SSL Configuration
Error message
No response
Additional information
No response

Hi @omri-shilton 👋 , I observed that you have been able to successfully connect a custom domain to your Amplify app dpm5giteybegs. Are you still running into this issue?

Observed similar, but temporary, behavior given the following environment:
Before opening, please confirm:

[x]  I have checked the custom domains troubleshooting guide.

[x]  I have read the guide for submitting bug reports.

[x]  I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
dy6ewpr2d09ta
Region
us-east-1
Step
SSL Configuration
Status
SSL configuration
Issue or question
Custom domain registration for Amplify app. Amplify app created 2023-08-15 @ 12:51:46 (EST). Once application was in running state, a custom domain (xptech.help) was registered via Route53 with "Domain registration successful" sent at 2023-08-15 13:31:39. Amplify Domain management process fired after verifying DNS records were had "INSYNC" status. SSL Configuration step creates CNAME record within Route53 instantly upon step initiation, but appears to hang until ~14:05 (~30min) which could lead to erronous ticket creation. Followed troubleshooting steps to verify name servers matched in meantime and typed out most of this comment checking back and forth.
TLDR - Suggest UX improvement of message to user during "SSL Verification" indicating process could take ~30min/1hr/2hr for recently created Route53 domains if not a fluke/recurring issue.
Appreciate the team, really simple workflows and overall great experience!

Hi @XPGeek 👋 , thanks for reaching out and for sharing detailed feedback on the domain activation process with Amplify Hosting for newly created domains with Route53. I'll relay this feedback to the team internally on improving the console experience.

authors: Jay2113 XPGeek omri-shilton

repo: aws-amplify/amplify-hosting


text:
remove ecr from soak-on-release service list

Description of changes:

While running soak test on every release of ecr-controller, there were resource leaks and no monitoring was set on those soak tests.
Since these soak tests were running in isolated e2e test account, it created friction on ecr-controller PR testing
For now I am removing the soak tests on every release of ecr controller and they can be enabled again once ecr team owns the controller and want this feature.

Error from soak-test-job
        # Create k8s resource
        ref = k8s.CustomResourceReference(CRD_GROUP, CRD_VERSION, RESOURCE_PLURAL,resource_name,namespace="default",)
        k8s.create_custom_resource(ref, resource_data)
        cr = k8s.wait_resource_consumed_by_controller(ref)
>      assert cr is not None
E      assert None is not None
tests/test_repository.py:148: AssertionError
 ------------------------------ Captured log call -------------------------------
ERROR    root:resource.py:227 Wait for resource default:ecr-repository-n87zogcx2 to be consumed by controller timed out

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


text:
Docs: Updates to the simple-build-pipeline example plan to ensure that it works

What were you searching in the docs?
There are two things that should be added to the simple-build-pipeline example plan to ensure that it works:

Add Helix Authentication Service dependency to Helix Core

There is a race condition where Helix Core can be created before Helix Authentication Service is up and running. This breaks the p4_configure.sh script as it initialized the HAS extension.

Add security group rules so that the three Helix services can communicate with each other.

Without the proper security group rules, the services cannot interact, which breaks things.
Is this related to an existing documentation section?
No response
How can we improve?

Add the following to module "perforce_helix_core":

  depends_on = [
    module.perforce_helix_authentication_service,
  ]

Add the following security group rules:

# Helix Swarm -> Helix Core
resource "aws_security_group_rule" "core_sg_internal_rule" {
  type                     = "ingress"
  from_port                = 1666
  to_port                  = 1666
  protocol                 = "tcp"
  source_security_group_id = module.perforce_helix_swarm.service_security_group_id
  security_group_id        = module.perforce_helix_core.security_group_id
}

# Helix Auth -> Helix Core
resource "aws_security_group_rule" "core_sg_internal_auth_rule" {
  type                     = "ingress"
  from_port                = 1666
  to_port                  = 1666
  protocol                 = "tcp"
  source_security_group_id = module.perforce_helix_authentication_service.service_security_group_id
  security_group_id        = module.perforce_helix_core.security_group_id
}

# Helix Core -> Helix Swarm
resource "aws_security_group_rule" "swarm_sg_internal_rule" {
  type                     = "ingress"
  from_port                = 443
  to_port                  = 443
  protocol                 = "tcp"
  cidr_blocks              = ["${module.perforce_helix_core.helix_core_eip_public_ip}/32"]
  security_group_id        = module.perforce_helix_swarm.alb_security_group_id
}

# Helix Core -> Helix Auth
resource "aws_security_group_rule" "auth_sg_internal_rule" {
  type                     = "ingress"
  from_port                = 443
  to_port                  = 443
  protocol                 = "tcp"
  cidr_blocks              = ["${module.perforce_helix_core.helix_core_eip_public_ip}/32"]
  security_group_id        = module.perforce_helix_authentication_service.alb_security_group_id
}

Got a suggestion in mind?
No response
Acknowledgment

[X] I understand the final update might be different from my proposed suggestion, or refused.

@keith-miller thanks for the heads up on this. Does the security.tf file of the Sample Build Pipeline mirror your expectations for SG creation?

@henrykie oh my bad! I see that now. Feel free to ignore that part of this ticket :D

authors: henrykie keith-miller


text:
[Bug]: Failed to query available provider packages

Welcome to Amazon EKS Blueprints!

[X] Yes, I've searched similar issues on GitHub and didn't find any.

Amazon EKS Blueprints Release version
latest
What is your environment, configuration and the example used?
Terraform version = 1.1.8
What did you do and What did you see instead?
The latest merge through that error and working fine with previous commit 854974d80304d736fce537699f86b8657c5fde98
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints >= 2.0.0, >= 2.23.0, >= 2.53.0,  >= 3.0.0, ~> 3.0, >= 3.2.0, >= 3.15.0, >= 3.34.0, >= 3.37.0, >= 3.63.0, >= 3.66.0, >= 3.72.0, >= 4.5.0

I don't know what the issue is exactly but after testing several times in another machine something is wrong with the latest 3 merges today. Thanks
Additional Information
No response

Hi @ZeroDeth
I have just tried running Terraform init and plan with Terraform Version 1.1.8 on the main branch and it works fine for me.
You may need to provide full example and the command you tried along with the logs. Have you done any further changes to the example you tried?

Hi @ZeroDeth
I have just tried running Terraform init and plan with Terraform Version 1.1.8 on the main branch and it works fine for me.
You may need to provide full example and the command you tried along with the logs. Have you done any further changes to the example you tried?

Hi @vara-bonthu
Working now after downgrade terraform-aws-s3-bucket https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/pull/149
Apologies and Thank you!

authors: ZeroDeth vara-bonthu

repo: aws-ia/terraform-aws-eks-blueprints


text:
refactor(event_handler): fix BedrockAgentResolver docstring

Issue number: #3644
Summary
Changes
Fixing issue about example docstring not displaying correctly because closing ``` is missing
User experience

Please share what the user experience looks like before and after this change

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[x] Meet tenets criteria
[x] I have performed a self-review of this change
[ ] Changes have been tested
[ ] Changes are documented
[x] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (1409499) 95.51% compared to head (f7f2a4a) 95.54%.
Report is 4 commits behind head on develop.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3645      +/-   ##
===========================================
+ Coverage    95.51%   95.54%   +0.02%
===========================================
  Files          211      213       +2
  Lines         9860     9961     +101
  Branches      1802      850     -952
===========================================
+ Hits          9418     9517      +99
- Misses         329      330       +1
- Partials       113      114       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter leandrodamascena

repo: aws-powertools/powertools-lambda-python


text:
Update templates with bug fixes

Includes fixes for #7 and #8.

@sshvans please review. TIA.

@rarsan Any reason we want to hard code the replication factor and not use the value provided in the parameters? Do we still need parameter "SplunkReplicationFactor" ?

Good catch @sshvans . The hardcoded replication factor is for search head tier which is of fixed size (3). The parameter replication factor is for indexer tier which is of variable size, and hence its replication factor is configurable.

authors: rarsan sshvans


text:
Application crashes with react-native version 0.63.4 when calling startRemoteVideo()

Describe the bug
I am trying to follow the steps to integrate amazon chime with my application. My current react-native version is 0.63.4 and I downloaded the latest Amazon chime sdk binaries for android.
To Reproduce
Run the app and whenever I enable it.audioVideo.startRemoteVideo(), the app crashes. Commenting that line will make it works, but no video of course. The issue opened here describes the same problem. But on my end, when the application crashes it does not produce any log.
As described in the the issue the solution was to downgrade the react-native version to 0.61.xx because from 0.62.xx and above the application crashes. Unfortunately, downgrading can not be an option because the application will give a lot of errors and warnings on other packages.
NativeMobileSDKBridge.kt
import android.Manifest
import android.content.pm.PackageManager
import androidx.core.content.ContextCompat
import com.callvita.srvy.RNEventEmitter.Companion.RN_EVENT_ERROR
import com.callvita.srvy.RNEventEmitter.Companion.RN_EVENT_MEETING_END
import com.amazonaws.services.chime.sdk.meetings.session.DefaultMeetingSession
import com.amazonaws.services.chime.sdk.meetings.session.MeetingSession
import com.amazonaws.services.chime.sdk.meetings.session.MeetingSessionConfiguration
import com.amazonaws.services.chime.sdk.meetings.session.MeetingSessionCredentials
import com.amazonaws.services.chime.sdk.meetings.session.MeetingSessionURLs
import com.amazonaws.services.chime.sdk.meetings.session.defaultUrlRewriter
import com.amazonaws.services.chime.sdk.meetings.utils.logger.ConsoleLogger
import com.amazonaws.services.chime.sdk.meetings.utils.logger.LogLevel
import com.facebook.react.bridge.ReactApplicationContext
import com.facebook.react.bridge.ReactContextBaseJavaModule
import com.facebook.react.bridge.ReactMethod
import com.facebook.react.bridge.ReadableMap
import com.facebook.react.modules.core.PermissionAwareActivity
import com.facebook.react.modules.core.PermissionListener

class NativeMobileSDKBridge(
        reactContext: ReactApplicationContext,
        private val eventEmitter: RNEventEmitter,
        private val meetingObservers: MeetingObservers) : ReactContextBaseJavaModule(reactContext), PermissionListener {

    companion object {
        private const val WEBRTC_PERMISSION_REQUEST_CODE = 1
        private const val TAG = "ChimeReactNativeSDKDemoManager"
        private const val KEY_MEETING_ID = "MeetingId"
        private const val KEY_ATTENDEE_ID = "AttendeeId"
        private const val KEY_JOIN_TOKEN = "JoinToken"
        private const val KEY_EXTERNAL_ID = "ExternalUserId"
        private const val KEY_MEDIA_PLACEMENT = "MediaPlacement"
        private const val KEY_AUDIO_FALLBACK_URL = "AudioFallbackUrl"
        private const val KEY_AUDIO_HOST_URL = "AudioHostUrl"
        private const val KEY_TURN_CONTROL_URL = "TurnControlUrl"
        private const val KEY_SIGNALING_URL = "SignalingUrl"

        var meetingSession: MeetingSession? = null
    }

    private val logger = ConsoleLogger(LogLevel.DEBUG)

    private val webRtcPermissionPermission = arrayOf(
            Manifest.permission.MODIFY_AUDIO_SETTINGS,
            Manifest.permission.RECORD_AUDIO,
            Manifest.permission.CAMERA
    )

    override fun getName(): String {
        return "NativeMobileSDKBridge"
    }

    @ReactMethod
    fun startMeeting(meetingInfo: ReadableMap, attendeeInfo: ReadableMap) {
        logger.info(TAG, "Called startMeeting")

        eventEmitter.sendReactNativeEvent(RN_EVENT_ERROR, "Called startMeeting")

        currentActivity?.let { activity ->
            if (meetingSession != null) {
                meetingSession?.audioVideo?.stop()
                meetingSession = null
            }

            try {
                val sessionConfig = createSessionConfiguration(meetingInfo, attendeeInfo)
                val meetingSession = sessionConfig?.let {
                    DefaultMeetingSession(
                            it,
                            logger,
                            activity.applicationContext
                    )
                }

                if (meetingSession != null) {
                    NativeMobileSDKBridge.meetingSession = meetingSession

                    if (!hasPermissionsAlready()) {
                        val permissionAwareActivity = activity as PermissionAwareActivity
                        permissionAwareActivity.requestPermissions(webRtcPermissionPermission, WEBRTC_PERMISSION_REQUEST_CODE, this)
                        return
                    }

                    startAudioVideo()
                } else {
                    logger.error(TAG, "Failed to create meeting session")
                    eventEmitter.sendReactNativeEvent(RN_EVENT_ERROR, "Failed to create meeting session")
                }
            } catch (exception: Exception) {
                logger.error(TAG, "Error starting the meeting session: ${exception.localizedMessage}")
                eventEmitter.sendReactNativeEvent(RN_EVENT_ERROR, "Error starting the meeting session: ${exception.localizedMessage}")
                return
            }
        }
    }

    private fun hasPermissionsAlready(): Boolean {
        return currentActivity?.let { activity ->
            webRtcPermissionPermission.all {
                ContextCompat.checkSelfPermission(activity, it) == PackageManager.PERMISSION_GRANTED
            }
        } ?: false
    }

    private fun startAudioVideo() {
        meetingSession?.let {
            it.audioVideo.addRealtimeObserver(meetingObservers)
            it.audioVideo.addVideoTileObserver(meetingObservers)
            it.audioVideo.addAudioVideoObserver(meetingObservers)
            it.audioVideo.start()
            it.audioVideo.startRemoteVideo()
        }
    }

    private fun createSessionConfiguration(meetingInfo: ReadableMap, attendeeInfo: ReadableMap): MeetingSessionConfiguration? {
        return try {
            val meetingId = meetingInfo.getString(KEY_MEETING_ID) ?: ""
            val attendeeId = attendeeInfo.getString(KEY_ATTENDEE_ID) ?: ""
            val joinToken = attendeeInfo.getString(KEY_JOIN_TOKEN) ?: ""
            val externalUserId = attendeeInfo.getString(KEY_EXTERNAL_ID) ?: ""
            var audioFallbackUrl = ""
            var audioHostUrl = ""
            var turnControlUrl = ""
            var signalingUrl = ""

            meetingInfo.getMap(KEY_MEDIA_PLACEMENT)?.let {
                logger.info(TAG, it.toString())
                audioFallbackUrl = it.getString(KEY_AUDIO_FALLBACK_URL) ?: ""
                audioHostUrl = it.getString(KEY_AUDIO_HOST_URL) ?: ""
                turnControlUrl = it.getString(KEY_TURN_CONTROL_URL) ?: ""
                signalingUrl = it.getString(KEY_SIGNALING_URL) ?: ""
            }

            MeetingSessionConfiguration(meetingId,
                    MeetingSessionCredentials(attendeeId, externalUserId, joinToken),
                    MeetingSessionURLs(audioFallbackUrl, audioHostUrl, turnControlUrl, signalingUrl, ::defaultUrlRewriter))
        } catch (exception: Exception) {
            logger.error(TAG, "Error creating session configuration: ${exception.localizedMessage}")
            eventEmitter.sendReactNativeEvent(RN_EVENT_ERROR, "Error creating session configuration: ${exception.localizedMessage}")
            null
        }
    }

    @ReactMethod
    fun stopMeeting() {
        logger.info(TAG, "Called stopMeeting")

        meetingSession?.audioVideo?.stop()
        eventEmitter.sendReactNativeEvent(RN_EVENT_MEETING_END, null)
    }

    @ReactMethod
    fun setMute(isMute: Boolean) {
        logger.info(TAG, "Called setMute: $isMute")

        if (isMute) {
            meetingSession?.audioVideo?.realtimeLocalMute()
        } else {
            meetingSession?.audioVideo?.realtimeLocalUnmute()
        }
    }

    @ReactMethod
    fun setCameraOn(enabled: Boolean) {
        logger.info(TAG, "Called setCameraOn: $enabled")

        if (enabled) {
            meetingSession?.audioVideo?.startLocalVideo()
        } else {
            meetingSession?.audioVideo?.stopLocalVideo()
        }
    }

    @ReactMethod
    fun bindVideoView(viewIdentifier: Double, tileId: Int) {
        logger.info(TAG, "Called bindVideoView for tileId: $tileId with identifier: $viewIdentifier")
    }

    @ReactMethod
    fun unbindVideoView(tileId: Int) {
        logger.info(TAG, "Called unbindVideoView for tileId: $tileId")

        meetingSession?.run {
            audioVideo.unbindVideoView(tileId)
        }
    }

    override fun onRequestPermissionsResult(requestCode: Int, permissions: Array<out String>?, grantResults: IntArray?): Boolean {
        return when (requestCode) {
            WEBRTC_PERMISSION_REQUEST_CODE -> {
                val isMissingPermission: Boolean =
                        grantResults?.isEmpty() ?: false || grantResults?.any { PackageManager.PERMISSION_GRANTED != it } ?: false

                if (isMissingPermission) {
                    eventEmitter.sendReactNativeEvent(RN_EVENT_ERROR, "Unable to start meeting as permissions are not granted")
                    false
                } else {
                    startAudioVideo()
                    true
                }
            }
            else -> false
        }
    }
}

RNVideoViewManager.kt
import com.amazonaws.services.chime.sdk.meetings.audiovideo.video.DefaultVideoRenderView
import com.amazonaws.services.chime.sdk.meetings.utils.logger.ConsoleLogger
import com.amazonaws.services.chime.sdk.meetings.utils.logger.LogLevel
import com.facebook.react.uimanager.SimpleViewManager
import com.facebook.react.uimanager.ThemedReactContext
import com.facebook.react.uimanager.annotations.ReactProp

class RNVideoViewManager : SimpleViewManager<DefaultVideoRenderView>() {
    private val logger = ConsoleLogger(LogLevel.DEBUG)

    companion object {
        // The React Native side is expecting a component named RNVideoView
        private const val REACT_CLASS = "RNVideoView"
        private const val TAG = "RNVideoViewManager"
    }

    override fun createViewInstance(reactContext: ThemedReactContext): DefaultVideoRenderView {
        logger.info(TAG, "Creating view instance")
        return DefaultVideoRenderView(reactContext)
    }

    override fun getName(): String {
        return REACT_CLASS
    }

    @ReactProp(name = "tileId")
    fun setTileId(renderView: DefaultVideoRenderView, tileId: Int) {
        logger.info(TAG, "Setting tileId: $tileId")

        NativeMobileSDKBridge.meetingSession?.let {
            it.audioVideo.bindVideoView(renderView, tileId)
        }
    }
}

Expected behavior
App does not crash, or at least give me a more meaningful crash log.
Logs
No logs produced when crashing.
Test environment Info:

Device: Samsung Galaxy A20s.
OS: Android 10
Version amazon-chime-sdk: 0.12.2
Version amazon-chime-sdk-media: 0.8.2

Additional context
It works when downgrading react native version to 0.61.xx, but this gives a lot of errors in other packages in the application.

Hi @youssefhaitham-callvita, can you try to downgrade NDK version as suggested in this issue?

I will close this issue as duplicate. Feel free to reopen if downgrading NDK does not resolve the issue

Hi @youssefhaitham-callvita, can you try to downgrade NDK version as suggested in this issue?

Hi @zhinang-amazon, I tried downgrading the NDK as mentioned in the repo but it did not work. The application still crashes when opening the video and does not produce any logs.

authors: youssefhaitham-callvita zhinang-amazon


text:
pca-main-noendra.template AllowedPattern

When running:
./publish-nokendra.sh jj-cfn-xxxxx "artifacts/pca"
The script fails at
Downloading witch file and upload into artifacts bucket
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 7368k  100 7368k    0     0  11.3M      0 --:--:-- --:--:-- --:--:-- 11.3M
upload: ../../../../tmp/witch-0eabcaf.zip to s3://jj-cfn-xxxxx/artifacts/pca/0.2.4/witch-0eabcaf.zip
Packaging Cfn artifacts

while scanning a double-quoted scalar
  in "<string>", line 50, column 21:
        AllowedPattern: "[+-_\/a-zA-Z0-9]*"
                        ^
found unknown escape character '/'
  in "<string>", line 50, column 27:
        AllowedPattern: "[+-_\/a-zA-Z0-9]*"
                              ^

From pca-main-nokendra.template I believe:
AllowedPattern: "[+-_\/a-zA-Z0-9]*"
Should be replaced with:
AllowedPattern: "[+-_/a-zA-Z0-9]*"
In both pca-main-nokendra.template and pca-main.template

This issue should be resolved.. Please verify with latest releases, and reopen with steps to reproduce, if it's still an issue. tx.

authors: jjessico rstrahan


text:
TypeError: Cannot read property 'afterEmit' of undefined

Environment: Python 3.6.8
user1-MacBook-Pro:website user1$ make dev
export NODE_ENV=dev; make build -B
../node_modules/.bin/webpack --config ./config/webpack.config.js
TypeError: Cannot read property 'afterEmit' of undefined
at t.exports.apply (/Users/user1/WorkDir/learn/aws/aws-ai-qna-bot/node_modules/webpack-s3-plugin/dist/s3_plugin.js:1:3252)
I updated webpack S3 plugin and webpack -- still not working.
Thanks for your help.

Solve Downgrade to 0.9.2 S3 plugin.

repo: aws-samples/aws-ai-qna-bot


text:
Attempting to run on mac os, field inventories not found in configuration

Attempting to run, having a bit of trouble:

Hi @omenking, thank you for opening this issue. It seems that the CLI can't find the config file. Make sure the config exists on the right path, you can read more about it here.
For example on Mac:
$ mv ~/.config/aws-auto-inventory/config.yaml ~/.config/aws-auto-inventory/config.bkp
$ ./dist/aws-auto-inventory-darwin-x86_64 --name cloudlab
Field inventories not found in configuration

I had this same issue. I had created config.yml instead of config.yaml

authors: omenking str3tch valter-silva-au

repo: aws-samples/aws-auto-inventory


text:
Isolated vpc example

Description

Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Understand the repository structure
[ ] Add yourself as an author
[ ] Add your pattern
[ ] Add a great SVG diagram for your pattern
[ ] Read our general contribution guidelines
[ ] Read our code of conduct
[ ] Confirm your pattern frontmatter lints correctly. i.e. run npm install && npm run lint locally from your dev environment

Preview available at: https://container-patterns-2167901491.d2vn5wspm16lm5.amplifyapp.com/pattern/ecs-cluster-isolated-vpc-no-nat-gateway

repo: aws-samples/container-patterns


text:
unable to access sqs queue from ecs task

I'm trying to understand how this worked. When I run it i'm able to create the SQS task and launch the task but when the ECS task tries to read from the queue it gets the following error, which I have reproduced by logging into the shell script container (after preventing it from exiting):
root@f9910bdcd9d6:/# aws sqs receive-message --queue-url=https://queue.amazonaws.com/831754492748/ecs-test-plepeskaQueue --region=us-east-1
An error occurred (AccessDenied) when calling the ReceiveMessage operation: Access to the resource https://queue.amazonaws.com/ is denied.
And this makes sense b/c although I can see that the ecsInstanceRole has a policy that gives it access to the S3 bucket I can't see where it is given access to the SQS queue.
Has something changed since this worked? Or, is there another reason why access to the queue is denied?

yes I definitely see your point... I get the same thing.  Anyway, the sample policy shows what needs to be added for s3, but will need to add similar access policy for SQS.

Anyone still maintaining this?  I'm running into the same issue.  Is there a more robust version of this pattern that has all the bits in working order?

my ecsinstance role has AwsFullAdmin access , still I am getting this error

authors: bizzbyster coldcam harsh3282 scottdear

repo: aws-samples/lambda-ecs-worker-pattern


text:
Removed CodeCommit clone from Cloud9

The purpose of this PR is to change the source repository available in the Cloud9 environment from the CodeCommit repository (removed now) to github.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

CC @bonclay7

repo: aws-samples/one-observability-demo


text:
README errors and incorrect SSM parameter name

Below issues were identified while executing the project

For the repository mlops-multi-account-tf, the template repository names are incorrect in the folder. The README uses different folder names
The SSM parameter name in the Terraform file is incorrect. The project template uses github_byoc_repo_template while the SSM created is github_container_repo_template

Closing this issue. Team has created separate repository for the project. Refer this issue in the new repository


text:
Step 3 shall be removed (we don't have confirmation to make since in the previsous prompt we said "not prompt")

I didn't get this prompt so i think it is not needed anymore
All Submissions:
IMPORTANT: Please do not create a Pull Request without creating an issue first.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature / Translation Submissions:

[x] Code Related: Have you checked for typos and prior to submission?
[x] Workshop Steps Related: Have you lint your code locally prior to submission?

Changes to Core Features:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you successfully ran tests with your changes locally?

Issue #, if available:
Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @benlec
First of all sorry for delayed answer, but it's for a good news.. The workshop was updated/migrated with a lot of fixes, you can find it here.
Thank for your help!


text:
Authorization code grant flow not working

If I turn off "Implicit grant" in my Cognito App client and leave only "Authorization code grant" then login fails and I get login#error_description=unauthorized_client&state=...&error=invalid_request.
If I turn on "Implicit grant" then the login works but I don't get a refresh token so I have to login every hour.

By default, the SDK use implicit grant flow.
To configure the code grant flow, you need to call useCodeGrantFlow on CognitoAuth
So the code snippet looks like:
// Initialize a cognito auth object.
function initCognitoSDK() {
var authData = {
ClientId : '<TODO: your app client ID here>', // Your client id here
AppWebDomain : '<TODO: your app web domain here>',
TokenScopesArray : '<TODO: your scope array here>',
RedirectUriSignIn : '<TODO: your redirect url when signed in here>',
RedirectUriSignOut : '<TODO: your redirect url when signed out here>'
};
var auth = new AWSCognito.CognitoIdentityServiceProvider.CognitoAuth(authData);
auth.userhandler = {
onSuccess: <TODO: your onSuccess callback here>,
onFailure: <TODO: your onFailure callback here>
/** E.g.
onSuccess: function(result) {
alert("Sign in success");
showSignedIn(result);
},
onFailure: function(err) {
alert("Error!" + err);
}*/
};
// The default response_type is "token", uncomment the next line will make it be "code".
auth.useCodeGrantFlow();
return auth;
}
Then when getting the URL which contains all these three kinds of tokens, the SDK will extract the tokens and set their values accordingly. Please refer to this function: getCodeQueryParameter(httpRequestResponse) in CognitoAuth.js.

By default, the SDK will use "implicit grant" flow. When you say "If I turn off "Implicit grant" in my Cognito App client and leave only "Authorization code grant" ", do you mean you put this setting on your user pool client setting on console?
And if you want to enable "Authorization code grant", you need to check this option on console, also in your code, you need to uncomment this line: auth.useCodeGrantFlow();
Then the SDK can use code grant flow.

Thank you very much for the reponse.
I now call auth.useCodeGrantFlow()
Unfortunately this does not work in my case. The sdk just keeps getting code tokens in an endless loop.
I get a login callback url that looks like this:
https://.../login?code=...&state=...
I then call parseCognitoWebResponse with the above url. Unfortunately parseCognitoWebResponse cannot parse this url.
parseCognitoWebResponse calls getCodeQueryParameter(httpRequestResponse) which calls getQueryParameters.
getQueryParameters fails to extract the code token from the url returns a map of:
Map(1) {"undefined" => undefined}
Because getQueryParameters is unsuccessful in extracting the query parameters my next call to auth.getSession just starts the whole process over again.
It looks to me like your this.getCognitoConstants().QUERYPARAMETERREGEX1 is wrong. It's value is:
/#(.+)/. This is why getQueryParameters fails to extract the code token.
This is wrong because as you can see in the callback url I posted above there is no # in the callback url from Cognito.
Am I doing something wrong? Should I not call parseCognitoWebResponse?

Your calling parseCognitoWebResponse() is correct. Please refer to the CognitoAuth.js code carefully.
Based on your login callback url that looks like this:
https://.../login?code=...&state=...
parseCognitoWebResponse(httpRequestResponse) {
if (httpRequestResponse.indexOf(this.getCognitoConstants().QUESTIONMARK) > -1) {
this.getCodeQueryParameter(httpRequestResponse);
} else if (httpRequestResponse.indexOf(this.getCognitoConstants().POUNDSIGN) > -1) {
// To parse the response to get tokens
this.getTokenQueryParameter(httpRequestResponse);
}
}
Because the callback url has "?", so in parseCognitoWebResponse(), it will call getCodeQueryParameter(),
getCodeQueryParameter(httpRequestResponse) {
const map = this.getQueryParameters(
httpRequestResponse,
this.getCognitoConstants().QUESTIONMARK
);
In which it uses question mark, not pound sign.  It should parse the url correctly.

My getCodeQueryParameter does not look like yours. How do I get an update with the correct getCodeQueryParameter?
Mine looks like this:
getCodeQueryParameter = function getCodeQueryParameter(httpRequestResponse) {
var mapSecond = new Map();
mapSecond = this.getQueryParameters(httpRequestResponse, mapSecond);
if (mapSecond.has(this.getCognitoConstants().CODE)) {
// if the response contains code
// To parse the response and get the code value.
var codeParameter = this.getCodeParameter(httpRequestResponse);
var url = this.getCognitoConstants().DOMAIN_SCHEME.concat(this.getCognitoConstants().COLONDOUBLESLASH, this.getAppWebDomain(), this.getCognitoConstants().SLASH, this.getCognitoConstants().DOMAIN_PATH_TOKEN);
var header = this.getCognitoConstants().HEADER;
var body = { grant_type: this.getCognitoConstants().AUTHORIZATIONCODE,
client_id: this.getClientId(),
redirect_uri: this.RedirectUriSignIn,
code: codeParameter };
var boundOnSuccess = this.onSuccessExchangeForToken.bind(this);
var boundOnFailure = this.onFailure.bind(this);
this.makePOSTRequest(header, body, url, boundOnSuccess, boundOnFailure);
npm list says I am on amazon-cognito-auth-js@1.0.0. npm view amazon-cognito-auth-js version says the latest published version is 1.0.0.
How do I get your version? When will you publish it?
Looks like you have last published to npm in August 2017 but you did this fix in September 2017.

Ok installing directly from github fixed this issue for me. Your repository is outdated on npm.
I got stuck on this for 2 weeks and even aws developer support was not able to resolve this.
The 2 things that tripped me up:

auth.useCodeGrantFlow() is not in your documentation I don't know how other people are getting this to work or maybe they are just logging in every hour.
You haven't updated your package on npm.

Glad that works! I am so sorry for the stuck. Thanks a lot for these two points, I just updated README.md to point out it. Will update my package on npm too. Thanks.

I am using codegrant flow and everything as per the documentation works, I'm sure I can work around the silent refresh as well based on the provided comments. But the only issue I've been facing is "unable to set my custom headers"
I have to send Authorization as "Basic xxxxxxxxxx" along with 'Content-Type': 'application/x-www-form-urlencoded' as per my requirement. Unfortunately I don't see any feasibility in doing so.
Let me know if you have any other workaround for achieving this. because I made some modifications in the library and it worked for me.
Below are the changes in file:

HEADER: this.headers  in constants
header = {  ...header  };  in makePOSTRequest method.

Below is the configuration:
authData: {
tenant: 'tenant',
ClientId: 'ClientId',
AppWebDomain: 'AppWebDomain',
TokenScopesArray: ['openid'],
RedirectUriSignIn: window.location.origin,
UserPoolId: 'UserPoolId',
RedirectUriSignOut: window.location.origin,
grant_type: 'grant_type',
client_secret: 'client_secret',
cacheLocation: 'localStorage',
IdentityProvider: 'IdentityProvider',
AdvancedSecurityDataCollectionFlag: false,
headers: {
'Content-Type': 'application/x-www-form-urlencoded',
Authorization: 'Basic XDXDXDXGFXHGGFXFXFXFXFXXDXDXDXDXDXDDXDXDX'
}
}
I have also attached the modified file here.
CognitoAuth.txt
I have a critical deadline to fix this issue.
Appreciate your quick thoughts on this.

authors: megyfexid patvyas srinuhamps yuntuowang

repo: aws/amazon-cognito-auth-js