text:
fix(start_planner): not run other modules when back pull out

Description

    setIsSimultaneousExecutableAsApprovedModule(false);
    setIsSimultaneousExecutableAsCandidateModule(false);

when backward driving of pull out.
this prevents LC from being approved when back and generating invalid path
Screencast from 2023年06月22日 11時24分17秒.webm
Related links

tier4 internal ticket
Tests performed

psim
https://github.com/autowarefoundation/autoware.universe/assets/39142679/1a5232e6-f99d-4d67-841a-44ba3cfbb0de
Notes for reviewers

Interface changes

none
Effects on system behavior

none
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

We tested this with real vehicle and works fine.


text:
feature(pointpainting): refined the fusion callback and updated the model

Description

refined the pointpainting_fusion callback

corrections for fusion callback and timer callback
use class names and order in config
multi thread
replace division with multiplication

updated the v3 model

Related links

Tests performed

Please refer to this page to test the package: https://tier4.atlassian.net/wiki/spaces/~459732634/pages/2788327823/pointpainting
 ros2 launch image_projection_based_fusion pointpainting_fusion.launch.xml input/rois0:=/perception/object_recognition/detection/rois0 input/camera_info0:=/sensing/camera/camera0/camera_info input/rois1:=/perception/object_recognition/detection/rois1 input/camera_info1:=/sensing/camera/camera1/camera_info input/rois2:=/perception/object_recognition/detection/rois2 input/camera_info2:=/sensing/camera/camera2/camera_info input/rois3:=/perception/object_recognition/detection/rois3 input/camera_info3:=/sensing/camera/camera3/camera_info input/rois4:=/perception/object_recognition/detection/rois4 input/camera_info4:=/sensing/camera/camera4/camera_info input/rois5:=/perception/object_recognition/detection/rois5 input/camera_info5:=/sensing/camera/camera5/camera_info input/rois_number:=6  input/pointcloud:=/sensing/lidar/top/outlier_filtered/pointcloud

Notes for reviewers

Interface changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@tzhong518
Cloud you check again? Bounding boxes don't matches the pointcloud.

https://github.com/autowarefoundation/autoware.universe/assets/37187849/1adc25c4-5443-4e7b-9944-de71e566faae

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
fix(dummy_perception_publisher, tier4_dummy_object_rviz_plugin): separate dummy object msg

Description
https://github.com/autowarefoundation/autoware.universe/pull/8818 and https://github.com/tier4/tier4_autoware_msgs/pull/146 should be merged first.
Separate dummy object message from dummy_perception_publisher package.

Remove messages from dummy_perception_publisher
Change message types to tier4_simulation_msgs

Related links
How was this PR tested?
Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

If you failed to build after this PR, please update https://github.com/tier4/tier4_autoware_msgs/


text:
Update http4s-blaze-client, ... from 0.21.25 to 0.22.1

Updates

org.http4s:http4s-blaze-client
org.http4s:http4s-blaze-server
org.http4s:http4s-client
org.http4s:http4s-dsl
org.http4s:http4s-server

from 0.21.25 to 0.22.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

github:http4s/http4s/v0_22?sha=v0.22.0

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-minor, scalafix-migrations

Superseded by #632.

repo: avast/scala-server-toolkit

license: MIT


text:
Update cats-effect to 2.5.4

Updates org.typelevel:cats-effect from 2.2.0 to 2.5.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

github:typelevel/cats-effect/v2_4_0?sha=v2.4.0

Documentation:

https://github.com/typelevel/cats-effect/blob/v2.4.0/scalafix/README.md

Files still referring to the old version number
The following files still refer to the old version number (2.2.0).
You might want to review and update them manually.
project/Dependencies.scala

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, semver-minor, scalafix-migrations, old-version-remains

Superseded by #297.


text:
JSON mode

Okay, show time! To be honest this has been a missing feature that has meant that I have not spent much time on this recently as it is vital for any meaningful generative usage that isn't plain chat.
Google added the feature to the API for both public and Vertex endpoints earlier in the week.
I will try to look at adding this in during the next week or so.

Fixed with #33

source: gharchive/issue

repo: avastmick/google-generative-ai-rs


text:
Improved text-to-speech.py

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #440 Text to Speech
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes
[ ] No

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] My documentation follows Template for README.md
[x] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.

I will create a README.md file for this script.

@mehabhalodiya you are using Linux and I am running it on windows, maybe that's an issue but it will be resolved if you delete the file generated as soon as the user gets the output. I had this thing in mind from the beginning because user expects the audio output and no unnecessary files.
Kindly delete the data.mp3 file uploaded in this PR, create the readme file for this script and implement file deletion mechanism in the script.

@mehabhalodiya This script is not updated yet after so many commits

Now what should I need to do?

Now what should I need to do?

https://github.com/avinashkranjan/Amazing-Python-Scripts/pull/449#issuecomment-796411780

Okay, I will do that by tomorrow.

Can you help me with file deletion mechanism?
import os

path = "/home/oem/Amazing-Python-Scripts/Text/Text-To-Speech/Data.mp3"

os.remove(path)

print("Data.mp3 has been deleted.")

Should I have to write this piece of code?

Can you help me with file deletion mechanism?
import os

path = "/home/oem/Amazing-Python-Scripts/Text/Text-To-Speech/Data.mp3"

os.remove(path)

print("Data.mp3 has been deleted.")

Should I have to write this piece of code?

Try this:
def Text_to_speech():
    Message = entry_field.get()
    speech = gTTS(text = Message)
    speech.save('Data.mp3')
    playsound('Data.mp3')
    os.remove('Data.mp3')

@santushtisharma10 @antrikshmisri

@santushtisharma10 @antrikshmisri

@all-contributors please add @mehabhalodiya for code and documentation

repo: avinashkranjan/Amazing-Python-Scripts


text:
Added Turkish translation

Application now supports Turkish language.

It was associated to #105

repo: avjinder/Minimal-Todo

license: mit

license_source: bigquery


text:
Update 14-leonpc-git.md

please check

Looks good

repo: avnet-dev-workshop/caption-this


text:
Questions about DDPG

Hi! I'm new to RL and currently doing a project in  music recommender system using DDPG. Its kinda similar with your DDPG project, and I got some things that I still confused..
If you don't mind, please answer my question..

How many user history data did you use for your movie recommendation?
Did epoch matter in RL especially DDPG? (Sorry if it sounds stupid, but I saw some tutorial and got really confused, some tutorial use randomize data for the environment initial state, which therefore I assume it didn't really care for epoch. But almost all RL environment like in openai gym use one initial state and train it for thousand episode, for example in continuous mountain car, the episode always start in the same position)
If I have an environment which have 15 steps for 1 episode, is it fine if i used discount factor 0.97

Sorry if it didn't really related to your github:( But I hope that you can help me because I got no expert to consult to..
Thank you so much.

I stack it by 10 items fixed. You can use LSTM or whatever
What is an epoch? As I said I stack 10 items rated by user as state, regress 1 and its rating item as a target action
I dont know. In the article I use various metrics like pairwise distances and VAE reconstruction error. Read under "Interpreting the results" section and find a value that suits you

By the way, I always like to look at what people make using my library. Make sure to share the progress when done!

Hey thank you so much for answering.
Epoch that I meant is the usual Epoch in Deep Learning. Like when you have 1k dataset, then you train the model using the dataset for 10 times, therefore you're using 10epochs.
Sorry if it confused you, let me explain my question then..
So, my dataset is consists of music sessions, where 1 session is consists of 20 songs that played sequentially by a user.
I'm confused like how many sessions I should use for training? Let say I used 1k sessions, therefore there's 1000*20=20000 rows of data. Can I used the 20k data for maybe 200k timesteps, so the model will learn each data 10 times. Or I should just use 20k rows for only 20k timesteps? Which is more efficient for DDPG?
(Sorry if this still confusing you..)
Thank you!

Do you realize that you can slide it like that:
Item IDs (state)          | Action
1 2 3 4 5 6 7 8   9 10 | 11
2 3 4 5 6 7 8 9 10 11 | 12
I used ML 20M Dataset with 1-3 epochs. As the name suggests, there are ~20 million ratings
I dont know? I'd say 90/10 train/test split is good. Also cross validation never hurts
Why do you say "timesteps"? The entire idea is sequential recommendation. Once user session ends, you need to reset lstm's hidden state. If you reset LSTM's state and then learn anew, it (sequentiality) will be possible
I used to sort users by items count so they are somewhat even in # of items. Then for each batch I trained the network and reset the state

Yes I actually do slide it like that but just did not explain for simplicity of the question..
I slide every 5, so:
State | Action
1 2 3 4 5 | 6
2 3 4 5 6 | 7
...
15 16 17 18 19 | 20
threrefore 1 episode can do 15 steps, and then move to another session.
I've tried using like only 42k dataset, but it just so time consuming (12-13 hours) for only 1 epoch, thought that i might something be wrong. How long did it take you to train 20M data with 1-3 epoch?
Btw, what I meant by timesteps is the number of the model learning steps.
And thankyou for answering!

Optimization is the key
When I first started working on dataloading, it took almost 30 hours
Now it takes 5 minutes to iterate though the dataset (i5, 1 core), 10 minutes with learning
You can use my loader if you choose, look working with your own data in the docs
Important dataloading functions are here: link

repo: awarebayes/RecNN


text:
Fixed: Unable to discover M2 Reader

Was also encountering some issue when discovering M2 Card Readers.
Going through the code, native code was actually able to discover the M2 Card Reader.
It seems that it was failing when parsing the json to StripeReader object.
When discovering an M2 Card reader, it was not having any originalJSON field which was causing it to fail.
e.g
Sample json object received when an M2 reader is discovered (I've only changed the serial number):
{locationStatus: 2, deviceType: 3, originalJSON: null, serialNumber: <SERIAL_NO>, batteryStatus: 0, locationId: null, simulated: false, availableUpdate: false, label: null}]
Added some null check into the field for it to not cause error.

This is already fixed on version 1.2.0. Thank you for your contribution.

authors: MichaelCadavillo awazgyawali


text:
whitenoise & django-compressor

The framework supplies and example shop uses a sekizai processor that uses django-compressor to optimise js and css files. Due to django-compressor issue 351 it appears this can't be used offline.
When trying to use whitenoise to serve static files it appears there is an incompatibility between the two. Is there any experience or advice of using both together or must django-compressor be removed?

For others with the same problem it seems that the django-compressor integration and whitenoise are incompatible and are different solutions for solving an overlapping problem.
The incompatibility is that whitenoise will only serve files that are in its manifest file which is generated by the collectstatic command. It seems to do this by pulling in all the files in all the static directories.
The django-compressor integration generates new files on the fly in a CACHE directory when a page is rendered by combining existing static files. There seems to be no way of generating these files beforehand. I guess this could be a problem in a production environment where the django app only has read permission on the static file directory.
So there seems to be two ways of solving it:

remove the django-compressor integration and use whitenoise solely
use the django-compressor integration and use dj-static/Cling

I think there are pros and cons to each. The main pro for whitenoise I can see is its header optimisations for caching.
Anyone trying to deploy django-SHOP on Heroku will run into this problem. I've picked number 2 and will update here if I find any other related issues. The reason I picked 2 is the combined static files seems like a neat solution, and dj-static also comes with the ability to serve media, which is another problem to solve.

Thanks for informing me about this issue. I never used Whitenoise, and hence am unaware of possible issues with django-compressor

Just as a reference for whoever would cross this, Whitenoise seems compatiblme with django-compressor offline mode: http://whitenoise.evans.io/en/stable/django.html#django-compressor

authors: jrief pakal racitup

repo: awesto/django-shop


text:
laravel 5 support?

Plans?

I definitely plan to - last time I tried to get the workspace working properly it wasn't working.  I'll see if I can work on the upgrade in the next week or so.

Hey awjudd, any progress on this?
If i had a spare hour or two, I'd try to make it L5-ready. Sadly that time hasn't presented itself yet

Sadly I've run into a similar lack of time.  I will try to do this within the next week.

On Mar 12, 2015, at 1:20 PM, Luke Edwards notifications@github.com wrote:
Hey awjudd, any progress on this?
If i had a spare hour or two, I'd try to make it L5-ready. Sadly that time hasn't presented itself yet
—
Reply to this email directly or view it on GitHub.

No rush on my end

Thanks, good work!

Awesome Thanks :)

authors: awjudd lukeed


text:
allow disabling self sign-up in auth, surface output to auto-configure Authenticator

Environment information
System:
  OS: macOS 14.5
  CPU: (10) arm64 Apple M1 Pro
  Memory: 98.95 MB / 32.00 GB
  Shell: /opt/homebrew/bin/fish
Binaries:
  Node: 20.14.0 - ~/.local/state/fnm_multishells/44106_1718394805068/bin/node
  Yarn: undefined - undefined
  npm: 10.7.0 - ~/.local/state/fnm_multishells/44106_1718394805068/bin/npm
  pnpm: 9.1.4 - ~/.local/state/fnm_multishells/44106_1718394805068/bin/pnpm
NPM Packages:
  @aws-amplify/backend: 1.0.3
  @aws-amplify/backend-cli: 1.0.4
  aws-amplify: 6.3.6
  aws-cdk: 2.144.0
  aws-cdk-lib: 2.144.0
  typescript: 5.4.5
AWS environment variables:
  AWS_PROFILE = josef-gen2
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
As a developer building an enterprise microsite, or an application using my existing enterprise identity provider with SAML, etc., I want to disable self sign-up on the Cognito User Pool and force end users to authenticate via SAML.
Today I can disable using CDK:
// amplify/backend.ts
import { defineBackend } from "@aws-amplify/backend"
import { auth } from "./auth/resource"

const backend = defineBackend({
  auth,
})

const { cfnUserPool } = backend.auth.resources.cfnResources

cfnUserPool.adminCreateUserConfig = {
  // disables self sign-up for non-federated users
  allowAdminCreateUserOnly: true,
}

However the property name to modify is a bit ambiguous compared to the construct prop selfSignUpEnabled.
Consider surfacing a method on backend.auth to easily disable
// amplify/backend.ts
import { defineBackend } from "@aws-amplify/backend"
import { auth } from "./auth/resource"

const backend = defineBackend({
  auth,
})

backend.auth.disableSelfSignUp()

Or provide a way of configuring an external provider without also enabling email sign-in by default
// amplify/auth/resource.ts
import { defineAuth } from "@aws-amplify/backend"

export const auth = defineAuth({
  loginWith: {
    // not specifying `email` here implicitly disables self sign-up
    externalProviders: {
	  /* details */
    }
  }
})

Marking this as feature request.

I came across this issue while trying to find out how to do this in Gen 1.
Is it possible to disable self sign-up by setting a value in cli-inputs.json or overrides.ts in amplify/backend/auth/<app>/?
Thanks!

authors: josefaidt pr0g ykethan

repo: aws-amplify/amplify-backend


text:
test: E2E tests for SQL support in CDK construct

Description of changes
Test 1 for SQL support in the CDK construct. This tests the basic case of specifying connection params for a pre-existing SQL database, and letting the transformer provision Lambda, VPC endpoint, and IAM resources via CDK.
Other changes:

Add a new env variable to allow local invocations to skip the 0-3 minute delay when setting up a new project folder
Add a create-env.sh script to write an .env file based on AWS environment variables in the current shell session

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.

Test stacks aren't being deleted after the test. Investigating.

Changes since last approval:

735094b39 - Rebased against feature/rds-support-preview2 & addressed merge conflicts
033626c94 - Fixed error destroying CDK project
4a1c64a92 - Added construct test reports to .prettierignore

repo: aws-amplify/amplify-category-api


text:
frontendModule.displayFrontendDefaults is not a function

How did you install the Amplify CLI?
npm install -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v19.7.0
Amplify CLI Version
11.0.3
What operating system are you using?
MacOS
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
None.  Amplify has been working fine for years, though I've not initiated a new project in a while
Describe the bug
amplify init fails
`% amplify init
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the project chat
The following configuration will be applied:
Project information
| Name: test
| Environment: dev
| Default editor: Visual Studio Code
🛑 frontendModule.displayFrontendDefaults is not a function`
Expected behavior
amplify init successfully initializes new project
Reproduction steps
amplify init
Project Identifier
`amplify diagnose --send-report
Learn more at https://docs.amplify.aws/cli/reference/diagnose/
⠋ Creating Zip
No Amplify backend project files detected within this folder.
✖ Creating Zip`
Log output

# Put your logs below this line

Additional information
no files are created
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 @pawelzebrowski :wave: thanks for raising this! Unfortunately I am not able to reproduce this issue using the provided steps and Amplify CLI v11.0.3. Can you confirm the version you are using with amplify version? Do you experience this regardless of your working directory?

Closing due to inactivity. @pawelzebrowski if you are still experiencing this please reply back to this thread and we can re-open to investigate further

authors: josefaidt pawelzebrowski

repo: aws-amplify/amplify-cli


text:
amplify env pull fails in Windows after adding a function

Describe the bug
amplify env pull fails in Windows after adding a function using amplify function add
To Reproduce
Steps to reproduce the behavior:

Add a function using amplify function add
Run npm install  inside the src/ folder in the function
Run amplify env pull or amplify init

There was an error initializing your environment.
init failed
{ Error: EPERM: operation not permitted, symlink '..\mime\cli.js' -> 'app\amplify.temp#current-cloud-backend\function\myfunction\src\node_modules.bin\mime'
errno: -4048,
code: 'EPERM',
syscall: 'symlink',
path: '..\mime\cli.js',
dest: '\app\amplify\.temp\#current-cloud-backend\function\myfunction\src\node_modules\.bin\mime' }

Expected behavior
Be able to pull, checkout or init an existing environment after adding a function.
Desktop (please complete the following information):

OS: Windows 10
amplify-cli 1.1.7

Additional context
Same error using windows cmd or a bash for Windows.

@kstro21 whats the version of CLI do you have installed?

@yuth I've updated the issue and added that info, I'm using amplify-cli 1.1.7

@kstro21 what do you have in the dependency block of your package.json

@yuth here is the complete stack trace

There was an error initializing your environment.
2019-03-11T18:40:55.173Z - error: uncaughtException: EPERM: operation not permitted, symlink '..\mime\cli.js' -> 'myapp\amplify.temp#current-cloud-backend\function\pgaapicourses\src\node_modules.bin\mime' date=Mon Mar 11 2019 14:40:55 GMT-0400 (Eastern Daylight Time), pid=14936, uid=null, gid=null, cwd=myapp, execPath=C:\Program Files (x86)\nodejs\node.exe, version=v8.11.4, argv=[C:\Program Files (x86)\nodejs\node.exe, C:\Users\MyUser\AppData\Roaming\npm\node_modules@aws-amplify\cli\bin\amplify, env, pull], rss=244527104, heapTotal=84357120, heapUsed=68813976, external=135429418, loadavg=[0, 0, 0], uptime=56806.6657181, trace=[], stack=[Error: EPERM: operation not permitted, symlink '..\mime\cli.js' -> 'myapp\amplify.temp#current-cloud-backend\function\pgaapicourses\src\node_modules.bin\mime']

Dependencies in my package.json
"dependencies": {
    "@material-ui/core": "3.9.2",
    "@material-ui/icons": "3.0.2",
    "classnames": "2.2.6",
    "cross-env": "5.2.0",
    "downshift": "3.2.4",
    "localforage": "1.7.3",
    "lodash": "4.17.11",
    "react": "16.8.1",
    "react-dom": "16.8.1",
    "react-router-dom": "4.3.1",
    "react-scripts-ts": "3.1.0"
  },
  "devDependencies": {
    "@types/classnames": "2.2.7",
    "@types/graphql": "14.0.7",
    "@types/history": "4.7.2",
    "@types/jest": "24.0.0",
    "@types/lodash": "4.14.121",
    "@types/node": "10.12.23",
    "@types/react": "16.8.2",
    "@types/react-dom": "16.8.0",
    "@types/react-router": "4.4.3",
    "@types/webpack-env": "1.13.7",
    "aws-amplify": "1.1.19",
    "aws-amplify-react": "2.3.0",
    "csstype": "2.6.2",
    "typescript": "3.3.3333"
  },

My Lambdas dependencies
  "dependencies": {
    "aws-sdk": "^2.49.0",
    "aws-serverless-express": "^3.3.5",
    "body-parser": "^1.17.1",
    "express": "^4.15.2"
  },

Hope it helps

The problem is due to Windows permissions to create symlinks, we need to run the cmd as administrator, then it works. Closing
Thanks, @yuth, for the time.

I am getting this error while running as administrator-
c:\Users\nitin\aws\aws3>amplify pull --appId dnq6aww8tlwm5
EPERM: operation not permitted, rename 'c:\Users\nitin\aws\aws3\amplify' -> 'c:\Users\nitin\aws\aws3\amplify-backup'
Error: EPERM: operation not permitted, rename 'c:\Users\nitin\aws\aws3\amplify' -> 'c:\Users\nitin\aws\aws3\amplify-backup'
at Object.renameSync (fs.js:772:3)
at rename (C:\Users\nitin\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\fs-extra\lib\move-sync\move-sync.js:31:8)
at doRename (C:\Users\nitin\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\fs-extra\lib\move-sync\move-sync.js:26:10)
at Object.moveSync (C:\Users\nitin\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\fs-extra\lib\move-sync\move-sync.js:17:10)
at backupAmplifyFolder (C:\Users\nitin\AppData\Roaming\npm\node_modules@aws-amplify\cli\lib\attach-backend.js:107:12)
at Object.attachBackend (C:\Users\nitin\AppData\Roaming\npm\node_modules@aws-amplify\cli\lib\attach-backend.js:35:5)
at Object.exports.run (C:\Users\nitin\AppData\Roaming\npm\node_modules@aws-amplify\cli\lib\commands\pull.js:62:32)
at Object.executeAmplifyCommand (C:\Users\nitin\AppData\Roaming\npm\node_modules@aws-amplify\cli\lib\index.js:182:29)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async executePluginModuleCommand (C:\Users\nitin\AppData\Roaming\npm\node_modules@aws-amplify\cli\lib\execution-manager.js:153:5)

@nitin3000
Try downgrading to 4.37.2
I just wasted 2 days on this.

@kfernandes29 Your 2 days of work just helped me out, thanks!  This happened to me when trying to move my repo to another amplify project.  It's still not working for me, but I think it's because of some config that the new admin ui threw in.

@lebull Glad it helped! That new admin UI + the new CLI has been nothing but headaches this week. It set me back quite a bit. I’m not sure how I got it all back to normal, but after 48 hours of frustration...it’s good again.

@kfernandes29
https://github.com/aws-amplify/amplify-cli/issues/6138#issuecomment-742730830


text:
configured env disappeared from amplify env list, resources still running

Describe the bug
I configured 2 environments for a project I'm building. Dev and Master using the same patterns described in the multi-env doc page. I have not done anything with the master environment for a couple of weeks and now it is no longer showing up when I type amplify env list. amplify env get --name master returns No environment found with the corresponding name provided
To Reproduce
I've not reproduced this since but here's what happened
Steps to reproduce the behavior:

Use amplify env add to add a new environment
Switch development back to a different environment
Wait for days (personal theory is that this is related to the timeout of API Keys like described in #980 but I'm not certain
run amplify env list

Expected behavior
I'd expect to see both the dev and the new env I created in the list
Observed Behavior
$ amplify env get --name master
No environment found with the corresponding name provided

All of the resources for that environment are still running - S3 buckets, API and Elasticsearch instances. I just can't control them anymore.
Desktop (please complete the following information):

OS: MacOS 10.14.3

Browser n/a

Amplify version 1.1.7 - may be worth noting that `amplify env add was run in 1.1.0

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

BTW - I find this very disconcerting and I am getting nervous about deploying on this platform when I lose the ability to manage it after a week or so between this issue and the chain of errors described in #980

@poppybank The envs are managed locally in your filesystem and shouldn’t disappear if your local filesystem hasn’t updated or changed in a week. Could you please check your amplify/team-provider-info.json file to check if you have keys corresponding to each of your envs?

Thanks @kaustavghosh06.  Only the dev environment is in the amplify/team-provider-info.json file.
Honestly I was expecting that these items would be stored in the cloud. Is there a way to rebuild the awscloudformation data if that version of the team-provider-info.json has been lost?

@poppybank If you didn't check in your team-provider-info.json file in a  VCS before you lost the reference to it, you could retrieve the "awscloudformation" information from the that environments corresponding to that environment from the parent Cloudformation stack (in the Outputs section) in the AWS Cloudformation console.

You can copy-paste this infoin the amplify/team-provider-info.json file (use your other enviornment as a reference) and then "amplify init" the project and select the environment that you just added to initialize and use the environment you just added to your team-provider-info.json file.

Once I add this information into amplify/team-provider-info.json as a second env, I would want to do amplify env checkout <envname> then right? The project already has been inited. Or is amplify init preferred over checkout if I'm just switching which environment I'm targeting?

When you amplify init, the CLI would ask you if you want to use an already exisiting environment and you would get a list of envs to choose from. You could alternatively use amplify env checkout <envname> as you've mentioned above which would do the same thing.

@kaustavghosh06 Thanks that help. The word init (to me) means it is configuring something for the first time so it would seem bad to do this with an enlistment that is already running.
One last question on the multi-env functionality, then. If I have an unattended build machine that needs to build my mobile apps, the build machine would need to have amplify installed but then it would checkout a branch from git and run amplify env checkout <envname> and would it then be ready to build or would it also need to run amplify api gql-compile to have the tree configured for a build?
This process needs to run unattended so things like amplify init  won't work well here.
Thanks

@poppybank That's exactly we support headless mode for our commands like init/push/publish etc so that these commands could be run on build systems.
Please take a look at https://aws-amplify.github.io/docs/cli/init#headless-usage-of-the-cli for more information around this.

I was sure you had it solved, just hadn't seen that documentation yet. thanks!!

@kaustavghosh06 I made a change to the graphql.schema and did amplify push but the files in src/graphql are not being updated to reflect that I removed a @model declaration.  Is there a way to force rebuild those? Doing amplify api gql-compile does not seem to do it.

@poppybank Since this question is not tied to this specific issue, could you please open another issue for this or reference me in the issue if you'e already opened for this?

@poppybank did you get rid of the model, or change its name?

I did not change its name. I did try removing a model (comments) and did amplify push when the @searchable thing was failing. That left comments in a state with the resolvers deleted but nothing else was gone even though the amplify push was rolled back

amplify pull --appId [APP_ID_HERE] --envName [ENV_NAME_HERE] did the trick for me.

authors: ezagala jkeys-ecg-nmsu kaustavghosh06 poppybank


text:
chore: undo custom resource exclusions on windows

Description of changes
This brings back custom resource tests previously included on windows.

Issue #, if available

Description of how you validated changes
Checklist

[x] PR description included
[x] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are 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 #12329 (ab1e9a2) into dev (984c0f8) will decrease coverage by 2.35%.
The diff coverage is 57.74%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##              dev   #12329      +/-   ##
==========================================
- Coverage   49.45%   47.11%   -2.35%
==========================================
  Files         692      837     +145
  Lines       33424    38148    +4724
  Branches     6840     7757     +917
==========================================
+ Hits        16529    17972    +1443
- Misses      15370    18533    +3163
- Partials     1525     1643     +118

Impacted Files
Coverage Δ

...mplify-appsync-simulator/src/resolvers/function.ts
15.38% <ø> (ø)

...s/amplify-appsync-simulator/src/type-definition.ts
100.00% <ø> (ø)

...sync-simulator/src/velocity/util/dynamodb-utils.ts
6.55% <0.00%> (ø)

...y-appsync-simulator/src/velocity/util/map-utils.ts
10.00% <ø> (ø)

...tor/src/velocity/util/transform/dynamodb-filter.ts
4.93% <0.00%> (ø)

...appsync-simulator/src/velocity/value-mapper/map.ts
86.88% <ø> (ø)

...ackages/amplify-category-auth/src/commands/auth.ts
0.00% <0.00%> (ø)

...ges/amplify-category-auth/src/commands/auth/add.ts
0.00% <ø> (ø)

...es/amplify-category-auth/src/commands/auth/help.ts
0.00% <0.00%> (ø)

.../amplify-category-auth/src/commands/auth/import.ts
0.00% <0.00%> (ø)

... and 93 more

... and 473 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter sobolk


text:
fix: handle modelFields for onSubmitBefore

Issue #, if available:
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.

Codecov Report

Merging #629 (ef099fd) into tagged-release/forms-and-views (940c2ec) will decrease coverage by 0.01%.
The diff coverage is 83.33%.

@@                        Coverage Diff                         @@
##           tagged-release/forms-and-views     #629      +/-   ##
==================================================================
- Coverage                           90.32%   90.31%   -0.02%
==================================================================
  Files                                  95       95
  Lines                                3505     3509       +4
  Branches                              951      952       +1
==================================================================
+ Hits                                 3166     3169       +3
- Misses                                317      318       +1
  Partials                               22       22

Impacted Files
Coverage Δ

packages/codegen-ui/lib/types/form/index.ts
100.00% <ø> (ø)

...codegen-ui-react/lib/forms/form-renderer-helper.ts
93.81% <75.00%> (-0.87%)
:arrow_down:

.../codegen-ui-react/lib/amplify-ui-renderers/form.ts
94.87% <100.00%> (+0.13%)
: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 940c2ec...ef099fd. Read the comment docs.

authors: SwaySway codecov-commenter

repo: aws-amplify/amplify-codegen-ui


text:
amplify push code generation fails on windows

Hi,
Sorry if this issue has been raised before but when I run amplify push on Windows I get an error generating the code despite everything else working correctly.  How can I fix this?
Describe the bug
when I run amplify push everything works except for code generation on Windows.  The error I get is: D:\dev\MyApp\D:\dev\MyApp\graphql contains invalid WIN32 path characters..  It seems the path is repeated.
Amplify CLI Version
4.45.2
To Reproduce
run amplify push with schema changes. I ran amplify init with defaults
Expected behavior
It should generate the code in the folder
Desktop (please complete the following information):

OS: Windows
Node Version. v14.6.0

Update:  Turns out this issue comes from when I first did amplify push.  It asks a few questions the first time, but after that it no longer asks.  So, ultimately I am able to get it to work by starting with a freshly created project, but that seems like a bad experience overall.  Also I have updated the amplify cli and not sure if something had changed from the first time.  Just some details for anyone who might fix the cli

repo: aws-amplify/amplify-codegen


text:
Get Build activity without logging in aws console

Is your feature request related to a problem? Please describe.
Get Build activity when tigger a build by web hook without logging in aws console.
We can see build activity in aws amplify console but is there any way to to get this info without logging in to console. maybe through API ?
Describe the solution you'd like
webhook response has something like this,
'{"SendMessageResponse":"ResponseMetadata":{"RequestId":"<RequestId>"}}'
so maybe we can make another request to get activity about that request by
https://webhooks.amplify.us-east-1.amazonaws.com/prod/webhooks?id=<ID>&token=<TOKEN>&requestid=<RequestId>&operation=getactivity

Are you referring to the build logs? or the history of builds?

I think both

We want to know if there is active build and if there is what is the status (Provision|Build|Deploy|Verify)
What is the status of all previous Jobs.

https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Amplify.html#getJob-property
You can use the same API to fetch status of previous jobs

authors: swaminator talebbits

repo: aws-amplify/amplify-console


text:
SSL verification is Running - [BRIEF DESCRIPTION]

App Id: d3m0wg6wtlsyor
Region: us-east-2
Step: Domain Activation
Status: Complete

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

Issue/question
I recently added a domain, matterintake.mosaic-consulting.com, and the first time I did it, it worked. I was able to use my subdomain (root excluded). Then, someone on my team didn't realize that I had done that, and they deleted it. I had to readd the domain. After readding the domain exactly the same and going through the same steps, it no longer works. It got all the way through domain activation, but going to my domain does not load anything anymore.
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.

@chrisgreatest Hi, do you still have problems? I checked your domain. Looks like it works now

authors: chrisgreatest garyleefight


text:
Improve deployment times for large sites

REF: https://twitter.com/jonlowforever/status/1166902193993084930
On a site with 5000 pages Amplify build speed is really fast (much faster than Netlify/Render etc). However uploads are quite slow in comparison (13 mins to upload 10,000 static files total). Is there anyway to config static file uploading to be faster? To give you guys some context, it's a @gatsbyjs site with almost 5000 pages, so it generates nearly 10K static files. Total deploy time is around 25 mins on Amplify, but file uploading/processing is more than half of this.

As a comparison, on Render, the uploads only took 3 mins (vs 13 mins). My guess is the difference in speed has to do with what "processing" is happening during upload. Perhaps Render simply upload the files blindly without any processing in place?
I've spoken to engineers at Netlify (who have a similar issue with deployment times on large sites), and they were able to list some processing tasks that happened during uploads (checking for forms, checking mixed http/s content).
I'm assuming that amplify has similar processing tasks. Ideally, anything that slows down uploads should be configurable, so the user can chose what features they want to ignore for faster deployments.

@jonlow we redesigned our deployment service to be much faster. Closing this issue.

authors: jonlow swaminator


text:
Bump dependency versions

Description of changes:
Bumps the version of package dependencies for the activity resource.
Testing:

mvn package
mvn test

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

Bumps the version of package dependencies for the activity resource.

Why?

Bumps the version of package dependencies for the activity resource.

Why?

These dependency bumps are expected to unblock internal build of the package.

authors: jormello wong-a


text:
Error messages need to be set for each check

What is the problem?
When writing a rule, any error message needs to be applied to every check.
So for example the s3_bucket_versioning_enabled rule is written like this:
rule S3_BUCKET_VERSIONING_ENABLED when %s3_buckets_versioning_enabled !empty {
  %s3_buckets_versioning_enabled.Properties.VersioningConfiguration exists
  %s3_buckets_versioning_enabled.Properties.VersioningConfiguration.Status == 'Enabled'
  <<
    Violation: S3 Bucket Versioning must be enabled.
    Fix: Set the S3 Bucket property VersioningConfiguration.Status to 'Enabled' .
  >>
}

The custom message there will only be shown in the JSON response for the %s3_buckets_versioning_enabled.Properties.VersioningConfiguration.Status == 'Enabled' check. If it fails at the exists check then the error message won't be shown.
Reproduction Steps
template
{
 "Resources": {
  "MyBucket": {
   "Type": "AWS::S3::Bucket",
   "Properties": {}
  }
}

rule s3_bucket_versioning_enabled
rule S3_BUCKET_VERSIONING_ENABLED when %s3_buckets_versioning_enabled !empty {
  %s3_buckets_versioning_enabled.Properties.VersioningConfiguration exists
  %s3_buckets_versioning_enabled.Properties.VersioningConfiguration.Status == 'Enabled'
  <<
    Violation: S3 Bucket Versioning must be enabled.
    Fix: Set the S3 Bucket property VersioningConfiguration.Status to 'Enabled' .
  >>
}

cfn-guard validate --data path/to/template --rules /path/to/rule
What did you expect to happen?
I would expect the output for each check to contain the custom error message.
What actually happened?
{
  "name": "",
  "metadata": {},
  "status": "FAIL",
  "not_compliant": [
    {
      "Rule": {
        "name": "S3_BUCKET_VERSIONING_ENABLED",
        "metadata": {},
        "messages": {
          "custom_message": null,
          "error_message": null
        },
        "checks": [
          {
            "Clause": {
              "Unary": {
                "context": " %s3_buckets_versioning_enabled[*].Properties.VersioningConfiguration EXISTS  ",
                "messages": {
                  "custom_message": "",
                  "error_message": "Check was not compliant as property [VersioningConfiguration] is missing. Value traversed to [Path=/Resources/MyConstructBucketA5944A03/Properties[L:4,C:17] Value={\"PublicAccessBlockConfiguration\":{\"BlockPublicAcls\":false,\"BlockPublicPolicy\":false,\"IgnorePublicAcls\":false,\"RestrictPublicBuckets\":false}}]."
                },
                "check": {
                  "UnResolved": {
                    "value": {
                      "traversed_to": {
                        "path": "/Resources/MyConstructBucketA5944A03/Properties",
                        "value": {
                          "PublicAccessBlockConfiguration": {
                            "BlockPublicAcls": false,
                            "BlockPublicPolicy": false,
                            "IgnorePublicAcls": false,
                            "RestrictPublicBuckets": false
                          }
                        }
                      },
                      "remaining_query": "VersioningConfiguration",
                      "reason": "Could not find key VersioningConfiguration inside struct at path /Resources/MyConstructBucketA5944A03/Properties[L:4,C:17]"
                    },
                    "comparison": [
                      "Exists",
                      false
                    ]
                  }
                }
              }
            }
          },
          {
            "Clause": {
              "Binary": {
                "context": " %s3_buckets_versioning_enabled[*].Properties.VersioningConfiguration.Status EQUALS  \"Enabled\"",
                "messages": {
                  "custom_message": ";    Violation: S3 Bucket Versioning must be enabled.;    Fix: Set the S3 Bucket property VersioningConfiguration.Status to 'Enabled' .;  ",
                  "error_message": "Check was not compliant as property [VersioningConfiguration.Status] to compare from is missing. Value traversed to [Path=/Resources/MyConstructBucketA5944A03/Properties[L:4,C:17] Value={\"PublicAccessBlockConfiguration\":{\"BlockPublicAcls\":false,\"BlockPublicPolicy\":false,\"IgnorePublicAcls\":false,\"RestrictPublicBuckets\":false}}]."
                },
                "check": {
                  "UnResolved": {
                    "value": {
                      "traversed_to": {
                        "path": "/Resources/MyConstructBucketA5944A03/Properties",
                        "value": {
                          "PublicAccessBlockConfiguration": {
                            "BlockPublicAcls": false,
                            "BlockPublicPolicy": false,
                            "IgnorePublicAcls": false,
                            "RestrictPublicBuckets": false
                          }
                        }
                      },
                      "remaining_query": "VersioningConfiguration.Status",
                      "reason": "Could not find key VersioningConfiguration inside struct at path /Resources/MyConstructBucketA5944A03/Properties[L:4,C:17]"
                    },
                    "comparison": [
                      "Eq",
                      false
                    ]
                  }
                }
              }
            }
          }
        ]
      }
    }
  ],
  "not_applicable": [],
  "compliant": []
}

CloudFormation Guard Version
2.1.3
OS
Ubuntu
OS Version
No response
Other information
One solution is to wrap all the checks inside a rule check (example from Control Tower rules)
rule s3_version_lifecycle_policy_check %s3_buckets not empty {
    check(%s3_buckets.Properties)
        <<
        [CT.S3.PR.3]: Require an Amazon S3 buckets to have versioning configured and a lifecycle policy
        [FIX]: Configure versioning-enabled buckets with at least one active lifecycle rule.
        >>
}

rule check(s3_bucket) {
    %s3_bucket {
        VersioningConfiguration exists
        VersioningConfiguration is_struct

        VersioningConfiguration {
            Status exists
            Status == "Enabled"
        }
    }
}

Thank you for submitting this issue. The check is using a basic AND operation which was put in there for backward compatibility at the time for older versions of cfn-guard. We are working with the cfn-guard team to make this work for custom error messages.
With the current version a single property value check will complete the exists and value check in one operation. What we can do is remove the exists check to eliminate this issue. There are a few other rules this is done and we can update those as well.

authors: corymhall grolston


text:
Developer roles for Test and Prod

These OUs and accounts exist, but nobody has access yet as we need reasonably-scoped roles for them.

Added AWSReadOnlyAccess to the Developer group.


text:
Implement CertificateAuthorityActivation deletion

Description of changes:
If a CertificateAuthorityActivation resource is deleted, set the corresponding CertificateAuthority resource's status to "DISABLED".
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/retest

/retest

/lgtm

authors: a-hilaly ndbhat


text:
new (but old) addon: Kubernetes Dashboard

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?
Since it is not clear what do you mean with "we have made a decision to only support the provisioning of a certain core set of add-ons" in this documentation section, I'm here to ask if you plan to re-add the support for the Kubernetes Dashboard install through Helm Chart.
The plugin was available in v4.32.1.
Describe the solution you would like
It would be awesome to have the same logic as other addons.
Describe alternatives you have considered
I'm not aware of other non vendor locking dashboards, but I'm open to suggestions.

There are no plans currently to re-add this. However, you can easily deploy the dashboard using this module or simply use a standalone helm_release resource. Here is an example of deploying any Helm chart with this module https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/blob/1b081736b7ef10626a19be20998ead8f6032262a/tests/complete/main.tf#L220-L235

Thats useful, I wasn't really aware of that module, thanks.
Is there an example of a helm_release with a ServiceAccount and an IAM Role?

Thats useful, I wasn't really aware of that module, thanks. Is there an example of a helm_releases with a ServiceAccount and an IAM Role?

I think that for this use case you could make use of terraform-aws-eks-blueprints-addon (without the final "s"). Is that right @bryantbiggs?

@LeoSpyke correct! The singular form is just for creating a single addon - and it can provide IRSA support if required by the addon. The plural form is a collection of addons, with most being implemented using the singular form module
For now, I am going to close this issue but happy to take any further questions

authors: LeoSpyke boatmisser bryantbiggs


text:
refactor(parser): add from future import annotations

Issue number: #4607
Summary
Changes
Add from __future__ import annotations to parser package
User experience
Discussed in #4607
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
[X] 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.

The code in this PR most probably fails in Python 3.8/3.9, like we saw with #4990.

repo: aws-powertools/powertools-lambda-python


text:
Maintenance: local documentation raises exception when run in docker

Summary
When running the documentation locally using Docker the mkdocs serve command seems to fail
Running docker run --rm -it -p 8000:8000 -v ${PWD}:/docs powertools-typescript/docs, causes this exception:
Traceback (most recent call last):
  File "/usr/local/bin/mkdocs", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mkdocs/__main__.py", line 268, in serve_command
    serve.serve(**kwargs)
  File "/usr/local/lib/python3.11/site-packages/mkdocs/commands/serve.py", line 54, in serve
    config = get_config()
             ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mkdocs/commands/serve.py", line 43, in get_config
    config = load_config(
             ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mkdocs/config/base.py", line 374, in load_config
    errors, warnings = cfg.validate()
                       ^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mkdocs/config/base.py", line 231, in validate
    run_failed, run_warnings = self._validate()
                               ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mkdocs/config/base.py", line 188, in _validate
    self[key] = config_option.validate(value)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mkdocs/config/base.py", line 55, in validate
    return self.run_validation(value)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mkdocs/config/config_options.py", line 868, in run_validation
    return theme.Theme(**theme_config)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mkdocs/theme.py", line 61, in __init__
    self._load_theme_config(name)
  File "/usr/local/lib/python3.11/site-packages/mkdocs/theme.py", line 126, in _load_theme_config
    theme_dir = utils.get_theme_dir(name)
                ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/mkdocs/utils/__init__.py", line 259, in get_theme_dir
    return os.path.dirname(os.path.abspath(theme.load().__file__))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen posixpath>", line 399, in abspath
TypeError: expected str, bytes or os.PathLike object, not NoneType
FATA[0000] exit status 1

The issue seem to have been introduced in this PR and only occurs when using Docker. If I run the docs using Python directly on my machine I am able to run it normally.
Likewise, the build for the docs is also unaffected.
We should investigate why this is happening.
Why is this needed?
So that contributors in this repo can run the docs locally without having to install Python on their machines.
Which area does this relate to?
Other
Solution
No response
Acknowledgment

[X] This request meets Powertools for AWS Lambda (TypeScript) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers
Please react with 👍 and your use case to help us understand customer demand.

Bumping docker image to 2a703999163cdb8257a85849fb2d39914a82587769f95c297bb3f01acf72a609 which is 9.5.35 fixes the issue.

Hey @am29d and @dreamorosi!  dedicated some time tonight to check this issue, and I believe I've identified the root cause. Before going into the details, I must say that I don't understand why we need to use pip-compile to generate a requirements.txt file with hashes and transitive dependencies in this situation. I mean, I understand that this approach can sometimes be useful to prevent conflicts, but in our current situation it seems to be having the opposite effect: it's actually creating conflicts.
Maybe in the past it was useful, but right now I don't see any need to use this.
So, can you try to reproduce the fix in your local environment? If it works, I can submit a PR:
1 - Remove the current docker image: docker image rm powertools-typescript/docs --force
2 - Clear the contents of the docs/requirements.txt file.
3 - Copy the content from docs/requirements.in to docs/requirements.txt
4 - Remove the flag --require-hashes from the docs/Dockerfile (line 5)
5 - Build the documentation: docker build -t powertools-typescript/docs ./docs/
6 - Run the documentation: docker run --rm -it -p 8000:8000 -v ${PWD}:/docs powertools-typescript/docs

I checked the pipeline for building the documentation and it should not be affected when using mkdocs build to build the documentation directly.
While we're at it, why don't you also use the Makefile to automate some things? This isn't exclusive to npm scripts and you can maintain them, but I think there's a universe of people who might take a while to figure out which npm script to run, whereas the Makefile is more straightforward.
Thanks

Hi @dreamorosi, thanks for sharing the OpenSSF scorecard check with me. There is actually a check for pinned dependencies if a pip install command is found.
The same issue is happening with Python and I figured out the problem. The dependabot is bumping packages and dependencies in the requirements.txt file, but it is not smart enough - don't ask me why - to detect that it should bump the transitive dependency mkdocs to 1.6.1, which is where the conflict is happening.
If you look here, you will see that it is using mkdocs 1.6.0, even though the latest is 1.6.1.
I created a new requirements.txt file with the dependencies updated and it's working now.
This is the first time this has happened and I don't know if it will happen again in the future, but it seems like we don't have many options now.

I'm sending a PR to fix this.

authors: am29d dreamorosi leandrodamascena


text:
Schema migration tool for Amazon Keyspaces

We are in the middle of migration to Amazon Keyspaces. I would like to know what is the best way to manage future Schema Migrations with Amazon Keyspaces?
It would be great if Amazon can provide with a tool that can mount a set of migration scripts and applies them incrementally.
Something like described https://medium.com/cobli/the-best-way-to-manage-schema-migrations-in-cassandra-92a34c834824

We also need this P.S: Asking for a friend :smile:

repo: aws-samples/amazon-keyspaces-toolkit


text:
Update attp-bootstrap.cfn.yaml

This part of the build project the url used to install the poetry is invalid, so i updated in my project. the error that shows with the default url installation: [Container] 2023/06/21 21:23:31 Running command set -ex

CODEBUILD_LAST_EXIT=0
export -p
pwd
exit 0

[Container] 2023/06/21 21:23:31 Running command curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/install-poetry.py | python -
File "", line 1
404: Not Found
^
SyntaxError: illegal target for annotation
[Container] 2023/06/21 21:23:33 Command did not exit successfully curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/install-poetry.py | python - exit status 1 [Container] 2023/06/21 21:23:33 Phase complete: PRE_BUILD State: FAILED [Container] 2023/06/21 21:23:33 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/install-poetry.py | python -. Reason: exit status 1
Issue #, if available:
Description of changes:
Testing done:

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

Hi, thanks for raising this & sharing the fix! Happy to merge


text:
adding note about https not working

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@abaird986 updated the language.


text:
Create AWS SAM Cloudformation template to auto deploy the Spark on Lambda

The objective is to create a SAM CloudFormation template that can automate the following tasks:

Build an image automatically
Sync it with AWS ECR
Create a Lambda function (with the option of creating an associated role if required)
Provide a VPC option
Allow access to the S3 folder
Define input and output folders
Specify the script location on S3.

By implementing this template, we aim to streamline the process and increase efficiency in these tasks.

Completed and tested and part of 0.2.0 release

Completed and tested and part of 0.2.0 release

repo: aws-samples/spark-on-aws-lambda


text:
Upgrade to version v1.0.1

[1.0.1] - 2023-10-26
Updated

Updated package versions to resolve security vulnerabilities.

Security scans of generative-ai-application-builder-on-aws < v1.1.0 will report a critical severity CVE due to use of the python package langchain-ai/langchain < v0.0.325
We can confirm that this version (v1.0.1) of Generative AI Application Builder on AWS is not directly impacted by the CVE because the solution does not use the LangChain Agents and the Python REPL capability identified in the CVE. However, we have released an update in v1.1.0 of the solution to incorporate the patch made available by the LangChain maintainers.


text:
STNO Spoke VPC Routing Update

Feature request?
We have been using STNO for some time now, its awesome, but only now we detected this behaviour.
STNO v3.1.0 since birth, on our setup we had a --parameter-overrides "DefaultRoute" = "Custom-Destinations" for a default-route 10.0.0.0/8.
We were able to backtrack the function tagging the route change.
"STNOStatus-RouteTable	: Route(s) added to the route table."
Cloudwatch logs also show that two route tables were changed:
2023-11-06 12:06:z1,zzz Adding route: 10.0.0.0/8
2023-11-06 12:06:z1,zzz Adding destination : 10.0.0.0/8 to TGW gateway: tgw-xxxxxxxxxxxx into the route table: rtb-yyyyyyyyyyyy
2023-11-06 12:07:z8,zzz Adding route: 10.0.0.0/8
2023-11-06 12:07:z8,zzz Adding destination : 10.0.0.0/8 to TGW gateway: tgw-xxxxxxxxxxxx into the route table: rtb-tttttttttttttttttt

vpc_handler
    def _update_route_table_with_cidr_blocks(self, existing_routes):
        cidr_blocks = convert_string_to_list_with_no_whitespaces(environ.get("CIDR_BLOCKS"))
        if len(cidr_blocks) > 0:
            for route in cidr_blocks:
                self.logger.debug(f"Adding route: {route}")
                self._find_existing_default_route(existing_routes, route)
                self._update_route_table(route)

...
def _update_route_table(self, route):
...
            if (
                self.event.get("Action") == "AddSubnet"
                or self.event.get("Action") == "CreateTgwVpcAttachment"
            ):
                # create route in spoke account route table
                self._create_route(ec2, route)
            elif (
                self.event.get("Action") == "RemoveSubnet"
                or self.event.get("Action") == "DeleteTgwVpcAttachment"
            ):
                # delete route from spoke account route table
                self._delete_route(ec2, route)
...
def _create_route(self, destination):
...
                else:
                    self.spoke_ec2_client.create_route_cidr_block(
                        destination,
                        self.event.get("RouteTableId"),
                        environ.get("TGW_ID"),
                    )
                self._create_tag(
                    self.event.get("RouteTableId"),
                    "RouteTable",
                    "Route(s) added to the route table.",
                )
...
ec2.py

    def create_route_cidr_block(
            self,
            vpc_cidr: str,
            route_table_id: str,
            transit_gateway_id: str
    ) -> CreateRouteResultTypeDef:
        response = self.ec2_client.create_route(
            DestinationCidrBlock=vpc_cidr,
            RouteTableId=route_table_id,
            TransitGatewayId=transit_gateway_id,
        )

The function _update_route_table_with_cidr_blocks to Update the Routing Table Logs "Adding route", then finds a route and updates it?  ( _find_existing_default_route + _update_route_table)
The real life result to us was that, our customer had a considerable impact/downtime because he had a default-route configured towards another TGW, and when STNO finished, inside the Action "default_route_crud_operations", we observed that 10.0.0.0/8 route changed to point towards the our newly configured tgw-attachment. This could be worse to roll-back if he didn't know what TGW was there before the change.
This might be doing its thing as coded/expected, but now we are considering changing default behaviour to DefaultRoute="Configure-Manually", just to avoid changing current routes that may exist, still we will loose the automated adding routes where they may be required...
Some thoughts/suggestions come to mind:

In the _update_route_table_with_cidr_blocks, shouldn't the log state "Updating route" instead of "Adding route"? if the function proceeds into a find + update.
There should be some protection/validation before updating an existing route.
Its risky to change routes thru an Automated procedure, may need a bit more controls on these changes, routing rules may differ from customer to customer.
Is the create-route ec2.py updating the route, instead of simply creating it, or is this done somewhere else? RollBack the route to previous TGW should exist if STNO process fails.
Just saw that there is a _delete_route inside the fn _update_route_table, but there was no log informing the deletion of 10.0.0.0/8. And found in the logs more info showing STNO was messing up the VPC routing tables for a while, ever since we did add, delete then add VPC TAGs again. The delete TAGs removed the route which is awful.
fn _find_existing_default_route logged no findings.
fn _update_route_table logged no findings.
In fact, it was observed that no route to 10.0.0.0/8 existed in 3x routing tables on tenants side, but no downtime was detected until a successfull STNO, where a new route was added to each RT on Monday 12h00: "Adding destination : 10.0.0.0/8 to TGW gateway: tgw-xxxxxxxxx into the route table:". No 10.0.0.0/8 existed during the weekend, and no issue was reported, only at 14h00-Monday after adding wrong TGW to routing tables.

We thank you for your thoughts, feed-back or anythings onto helping us is appreciated very much.
Thanks and keep up the good work guys.
Blue

Good morning,
Thanks for providing us the feedback and sharing details of this event.
It seems the user tagged a VPC that already had a route to a different transit gateway (from the one defined in the STNO solution stack).
By design, the solution creates route(s) in the VPC route table using the customer defined (CFN Params) destination and target. If the destination (example, 0/0, RFC-1918, Custom destinations) already exist in the route table with another target, STNO does not add the route or update the route with new destination to avoid impact to the customer network.
The supported use cases does not access all the existing routes and evaluate of all the possible scenarios. It would great if you can open a feature request to help us learn about new use cases.
As per the ticket, if we expect users to tag VPCs with existing routes to different TGWs, then using Configure-Manually option is the best option. IMO, if majority of the VPCs are new that needs to be attached with TGW, I would recommend to skip tagging the VPC with existing routes to unmanaged TGWs.
Second option could be the use of "Conditional" tags for TGW route tables. For example, if the VPCs that have existing routes to different TGW are in a different OU in the AWS Organization, you can use the complaince feature to auto-reject attachments and avoid impact to the network. (2, 3)
For 5, deletion of the routes added by the STNO workflow once you remove the tag is by design. The _delete_route function should add (this message)[https://github.com/aws-solutions/network-orchestration-for-aws-transit-gateway/blob/main/source/lambda/tgw_vpc_attachment/lib/handlers/vpc_handler.py#L270-L274] in the logs. Please feel free to share how we can improve this message.
For 6, 7 We have added backlog items to add specific log messages in the log group.
For 8, we are thinking about how we can help STNO user detection issues sooner. Any input/guidance based on your experience with STNO would be great.
If you prefer to share more details via a support ticket/TAM/SA, can you please refer the GitHub issue id to help us connect the two tickets.

Good Morning Sir.,
And thank you for your comprehensive reply.
"By design, the solution creates route(s) in the VPC route table using the customer defined (CFN Params) destination and target. If the destination (example, 0/0, RFC-1918, Custom destinations) already exist in the route table with another target, STNO does not add the route or update the route with new destination to avoid impact to the customer network."
This was exactly what we saw, probably our setup did delete the route 10.0.0.0/8 at some point (without impact to the customer), then when STNO process succeeded we saw the 10.0.0.0/8 being added. Before 6/11 we had issues with STNO Cloudformation permissions as AssumeRole wasn't applied on the central account to allow the new Region STNO.
Our setup is:
"DefaultRoute" = "Custom-Destinations"
CIDR_BLOCKS = "10.0.0.0/8"
I was able to filter the logs to give us a better view of this:
`
02/11/2023 16:18:51 | RouteTableId': 'rtb-00aaaaaaaaaaaaaaa' >> 'DestinationCidrBlock': '10.0.0.0/8', 'TransitGatewayId': 'tgw-00zzzzzzzzzzzzzzz'
02/11/2023 16:18:54 | RouteTableId': 'rtb-00bbbbbbbbbbbbbbb' >> 'DestinationCidrBlock': '10.0.0.0/8', 'TransitGatewayId': 'tgw-00zzzzzzzzzzzzzzz'
02/11/2023 16:19:02 | RouteTableId': 'rtb-00ccccccccccccccc' >> 'DestinationCidrBlock': '10.0.0.0/8', 'TransitGatewayId': 'tgw-00zzzzzzzzzzzzzzz'
02/11/2023 16:24:59 | RouteTableId': 'rtb-00bbbbbbbbbbbbbbb' >> 'DestinationCidrBlock': '10.0.0.0/8', 'TransitGatewayId': 'tgw-00zzzzzzzzzzzzzzz'
02/11/2023 16:24:59 | Removing destination : 10.0.0.0/8 to TGW gateway: tgw-0xxxxxxxxxxxxxxxx from the route table: rtb-00bbbbbbbbbbbbbbb
02/11/2023 16:25:03 | RouteTableId': 'rtb-00ccccccccccccccc' >> 'DestinationCidrBlock': '10.0.0.0/8', 'TransitGatewayId': 'tgw-00zzzzzzzzzzzzzzz'
02/11/2023 16:25:03 | Removing destination : 10.0.0.0/8 to TGW gateway: tgw-0xxxxxxxxxxxxxxxx from the route table: rtb-00ccccccccccccccc
02/11/2023 16:25:04 | RouteTableId': 'rtb-00aaaaaaaaaaaaaaa' >> 'DestinationCidrBlock': '10.0.0.0/8', 'TransitGatewayId': 'tgw-00zzzzzzzzzzzzzzz'
02/11/2023 16:25:04 | Removing destination : 10.0.0.0/8 to TGW gateway: tgw-0xxxxxxxxxxxxxxxx from the route table: rtb-00aaaaaaaaaaaaaaa
02/11/2023 16:32:46 | RouteTableId': 'rtb-00aaaaaaaaaaaaaaa' >> NO 10.0.0.0/8 ROUTE !!!
02/11/2023 16:32:46 | Adding route: 10.0.0.0/8
02/11/2023 16:32:49 | RouteTableId': 'rtb-00ccccccccccccccc' >> NO 10.0.0.0/8 ROUTE !!!
02/11/2023 16:32:49 | Adding route: 10.0.0.0/8
02/11/2023 16:56:31 | RouteTableId': 'rtb-00ccccccccccccccc' >> NO 10.0.0.0/8 ROUTE !!!
02/11/2023 16:56:31 | Adding route: 10.0.0.0/8
02/11/2023 16:58:41 | RouteTableId': 'rtb-00aaaaaaaaaaaaaaa' >> NO 10.0.0.0/8 ROUTE !!!
02/11/2023 16:58:41 | Adding route: 10.0.0.0/8
02/11/2023 16:58:48 | RouteTableId': 'rtb-00ccccccccccccccc' >> NO 10.0.0.0/8 ROUTE !!!
02/11/2023 16:58:48 | Adding route: 10.0.0.0/8
02/11/2023 16:58:52 | RouteTableId': 'rtb-00bbbbbbbbbbbbbbb' >> NO 10.0.0.0/8 ROUTE !!!
02/11/2023 16:58:52 | Adding route: 10.0.0.0/8
02/11/2023 17:33:26 | RouteTableId': 'rtb-00bbbbbbbbbbbbbbb' >> NO 10.0.0.0/8 ROUTE !!!
02/11/2023 17:33:26 | Adding route: 10.0.0.0/8
02/11/2023 17:33:28 | RouteTableId': 'rtb-00ccccccccccccccc' >> NO 10.0.0.0/8 ROUTE !!!
02/11/2023 17:33:28 | Adding route: 10.0.0.0/8
02/11/2023 17:33:31 | RouteTableId': 'rtb-00aaaaaaaaaaaaaaa' >> NO 10.0.0.0/8 ROUTE !!!
02/11/2023 17:33:31 | Adding route: 10.0.0.0/8
06/11/2023 12:03:52 | RouteTableId': 'rtb-00aaaaaaaaaaaaaaa' >> NO 10.0.0.0/8 ROUTE !!!
06/11/2023 12:03:52 | Adding route: 10.0.0.0/8
06/11/2023 12:03:52 | Adding destination : 10.0.0.0/8 to TGW gateway: tgw-0xxxxxxxxxxxxxxxx into the route table: rtb-00aaaaaaaaaaaaaaa
06/11/2023 12:06:02 | RouteTableId': 'rtb-00ccccccccccccccc' >> NO 10.0.0.0/8 ROUTE !!!
06/11/2023 12:06:02 | Adding route: 10.0.0.0/8
06/11/2023 12:06:02 | Adding destination : 10.0.0.0/8 to TGW gateway: tgw-0xxxxxxxxxxxxxxxx into the route table: rtb-00ccccccccccccccc
06/11/2023 12:07:38 | RouteTableId': 'rtb-00bbbbbbbbbbbbbbb' >> NO 10.0.0.0/8 ROUTE !!!
06/11/2023 12:07:38 | Adding route: 10.0.0.0/8
06/11/2023 12:07:38 | Adding destination : 10.0.0.0/8 to TGW gateway: tgw-0xxxxxxxxxxxxxxxx into the route table: rtb-00bbbbbbbbbbbbbbb
`
Since STNO is a Hub / Spoke solution, this means that a scenario will occur where we don't have all information to custom build routes on Spoke accounts. Our most common scenario is that the Hub is a LandingZone and the Spokes are remote tenant accounts. Therefore it would be impossible for us to know the remote TGWid (in this case tgw-00zzzzzzzzzzzzzzz), nor do we have implemented a way to point the 10.0.0.0/8 to other TGW other than the currently created by STNO (in this case tgw-0xxxxxxxxxxxxxxxx).
I will feedback more into this comment as I get some more time to continue replying to your notes.
Trying to feedback some value into this with our real life experience.
Thx.

Thanks for explaining the scenarios with the details. As you already understand it well that VPC tags are to define association and propagation in the TGW route tables. The Subnet tags helps with appending the subnets in TGW-VPC attachment and adding routes to the VPC route table associated with the tagged subnet.
Note: We introduced another tag "Route-to-tgw" in v3.3 to help customer update route tables associated with the other subnets in the same AZ. The reason is that you can only to append a single subnet per AZ in the TGW-VPC attachment. This helps updating routes in all the associated route tables.
Based on the information provided I plan add following items in our backlog and try ship in the next planned release.

STNO must ONLY delete an existing route if the destination is the tagged subnet (which is obvious in this case) AND target must be TGW ID defined in the CFN parameter. This would avoid change in route table not managed by the solution.
Add more metadata in the logs to easily identify the specific changes in the route table.

Can you please confirm if the items above meets the your expectation?
Thanks

Thank you , Yes, certainly it meets some of the thing that can be done!
I took the liberty of just to adding more details:

STNO must ONLY delete an existing route if the destination is the tagged subnet (which is obvious in this case) AND target must be TGW ID defined in the CFN parameter. This would avoid changing routes not managed by the solution. If "Route-to-tgw" is not defined, ANY routes should be added/deleted on Spoke account.
Add more metadata in the logs ( _create_tag, logger.debug, logger.info, logger. )* to easily identify the specific changes in the route table. Including CIDR's added/deleted and object added/deleted ( i.e. TGWid )

Thanks

authors: Cupidazul groverlalit


text:
Update travis to sync readme with dockerhub & run license test on release

Issue #, if available: N/A
Description of changes:

License test and sync read me to dockerhub scripts will execute on new Releases

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

Codecov Report

Merging #17 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #17   +/-   ##
=======================================
  Coverage   51.65%   51.65%
=======================================
  Files           5        5
  Lines         211      211
=======================================
  Hits          109      109
  Misses        100      100
  Partials        2        2

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 a5aae8b...7a92a57. Read the comment docs.

authors: brycahta codecov-commenter


text:
ecs-preview env show command design

Overview
Currently, ECS-CLI-v2 users are not able to access information about a project’s environment beyond ecs-preview env ls, which simply lists the environments of a project.
Ideally, ECS-CLI-v2 users should be able to type the command ecs-preview env show to see the resources ECS-CLI-v2 created in an environment. Because it handles so much of the work of spinning up environments behind the scenes, users may want quick and easy at-a-glance access to the details. For example, a user may deploy an app, then want to connect a database or additional service to it after the fact. They would want to know the VPC information and applicable resource ARNs in order to do that.
Design Proposal
Outputs
The output for ecs-preview env show -h should be as follows:
An environment represents a deployment stage.

Usage
  ecs-preview env show [flags]

Flags
  -h, --help            help for env
  -n, --name string     Name of the environment
  -p, --project string  Name of the project.
      --json            Optional. Output in JSON format.
      --resources       Optional. Resources of your environment.

Examples
  Shows information about the environment "test"
  `$ ecs-preview env show -e test`

Example of human output (with resources flag):
> ecs-preview env show --resources
? Which environment of "dinder" would you like to show?
test
prod

About
  Name           test
  Production     false
  Region         us-west-2
  AccountID      327148513104

Applications
  Name         Description
  ----         -----------
  api          LoadBalancedWebApp
  webapp       LoadBalancedWebApp

Tags
  Key              Value
  ---               -----
  ecs-project      dinder
  ecs-environment  test

Resources
  AWS::EC2::VPC                              vpc-0f04b55fa31b14b00
    AWS::EC2::InternetGateway                igw-0fa16e0d0cdcc79f5
    AWS::EC2::Subnet                         subnet-0c46d6b41cb7f6be6
    AWS::EC2::Subnet                         subnet-0a9341b4b4569ccaa
    AWS::EC2::RouteTable                     rtb-0407fb0a0a6d5d1aa
  Security Group:                            sg-032a6d38505077a9f
  PublicLoadBalancerDNSName:                 dinde-Publi-EXUI6JTIP4L3-185
  AWS::ElasticLoadBalancingV2::Listener      arn:aws:elasticloadbalancing:us-west-2:327148513104:listener/app/dinde-Publi-EXUI6JTIP4L3/920cda448591cfdd/1f183fe8dc2b118b
  AWS::ElasticLoadBalancingV2::TargetGroup   arn:aws:elasticloadbalancing:us-west-2:327148513104:targetgroup/dinde-Targe-1PE1CNOYB66R8/3180a7ad9aaf3ed8
  AWS::ECS::Cluster                          dinder-test-Cluster-UZNVB3MZCWSR
  ECR                                        327148513104.dkr.ecr.us-west-2.amazonaws.com/dinder/api
                                             327148513104.dkr.ecr.us-west-2.amazonaws.com/dinder/webapp

Example of JSON output (with resources flag):
> ecs-preview env show project --json --resources
? Which environment of "dinder" would you like to show?
test
prod

{
  "About": [
    {
      "envName": "test",
      "Project": "dinder",
      "Region": "us-west-2",
      "Prod": false,
      "AccountID: 327148513104
    }
  ],
  "Applications": [
    {
      "Name": "api",
      "URL": "http://dinde-Publi-EXUI6JTIP4L3-1856349916.us-west-2.elb.amazonaws.com/api/*"
    },
    {
      "Name": "webapp",
      "ULR": "http://dinde-Publi-EXUI6JTIP4L3-1856349916.us-west-2.elb.amazonaws.com/*"
    }
  ],
  "Tags": [
    {
    "Key": "ecs-project",
    "Value": "dinder"
    },
    {
    "Key": "ecs-environment",
    "Value": "test"
    }
  ],
  "Resources": [
    {
      "VPC": "vpc-0f04b55fa31b14b00",
      "AWS::EC2::VPC": "vpc-0f04b55fa31b14b00",
      "AWS::EC2::InternetGateway": "igw-0fa16e0d0cdcc79f5",
      "AWS::EC2::Subnet": "subnet-0a9341b4b4569ccaa",
      "AWS::EC2::RouteTable": "rtb-0407fb0a0a6d5d1aa",
      "Security Group": "sg-032a6d38505077a9f",
      "PublicLoadBalancerDNSName": "dinde-Publi-EXUI6JTIP4L3-185",
      "AWS::ElasticLoadBalancingV2::Listener": "arn:aws:elasticloadbalancing:us-west-2:327148513104:listener/app/dinde-Publi-EXUI6JTIP4L3/920cda448591cfdd/1f183fe8dc2b118b",
      "AWS::ElasticLoadBalancingV2::TargetGroup": "arn:aws:elasticloadbalancing:us-west-2:327148513104:targetgroup/dinde-Targe-1PE1CNOYB66R8/3180a7ad9aaf3ed8",
      "AWS::ECS::Cluster": "dinder-test-Cluster-UZNVB3MZCWSR",
      "ECR": [
         "327148513104.dkr.ecr.us-west-2.amazonaws.com/dinder/api",
         "327148513104.dkr.ecr.us-west-2.amazonaws.com/dinder/webapp"
      ]
    }
  ]
}

Interactive Experience:
$ ecs-preview env show
? Which project's environments would you like to show?  [Use arrows to move, type to filter, ? for more help]
> dinder
  e2e-init-1583862289

? Which environment would you like to show?  [Use arrows to move, type to filter]
> prod
> test

test:
About
  Name           test
  Production     false
  Region         us-west-2
  AccountID      327148513104

Applications
  Name         Description
  ----         -----------
  api          LoadBalancedWebApp
  webapp       LoadBalancedWebApp

Tags
  Key              Value
  ---              -----
  ecs-project      dinder
  ecs-environment  test

Related, for consistency: https://github.com/aws/amazon-ecs-cli-v2/issues/764

authors: SoManyHs huanjani


text:
Documentation for regenerating untrusted OTA certificates in tools/ota_e2e_tests/credentials

Is your feature request related to a problem? Please describe.
The documentation for recreating the untrusted certificate/key pairs for e2e testing either do not exist or the documentation is not easy to find.  Right now, the committed certificate/key pair fails to import with the following error at tag 202002.00.  The resulting ARN is required for e2e and IDT test configuration.
     #+begin_src bash :tangle /tmp/upload_untrusted.sh
SRC=/home/X/src/amazon-freertos-pic32mzef-ota
OTA_TOOLS=${SRC}//tools/ota_e2e_tests
KEY_UNTRUSTED=${OTA_TOOLS}/credentials/untrusted-ecdsa-sha256-signer.key.pem
CERT_UNTRUSTED=${OTA_TOOLS}/credentials/untrusted-ecdsa-sha256-signer.crt.pem

aws acm import-certificate \
    --certificate fileb://${CERT_UNTRUSTED} \
    --private-key fileb://${KEY_UNTRUSTED}
     #+end_src

     #+RESULTS:
An error occurred (ValidationException) when calling the ImportCertificate operation: The certificate is expired. You can Import a certificate only during its validity period.

Describe the solution you would like.
Documentation in README.md on how to recreate the key/certificate pair according to testing guidelines.

Hi @rpcme thanks for reporting the issue, I submitted a PR #1972 for this. Meanwhile, you can find the document for how to generate certificate here, https://docs.aws.amazon.com/freertos/latest/userguide/ota-code-sign-cert.html.

Hi @rpcme
Thank you for creating this issue. I will close it as PR #1972 has been merged.

authors: muneebahmed10 rpcme tgsong

repo: aws/amazon-freertos


text:
Change exported endpoint id delimiters, add ld flags to go run

Issue #, if available:
#84
Description of changes:
Change endpoint ID delimiters from . and :  back to _ to avoid R53 conflicts in DNS enabled namespaces. Separate protocol and port with -.
Add flags to go run to reflect running compiled executable behaviour.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #94 (c09fb8b) into main (a74d470) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #94      +/-   ##
==========================================
+ Coverage   70.30%   70.34%   +0.04%
==========================================
  Files          14       14
  Lines        1357     1359       +2
==========================================
+ Hits          954      956       +2
  Misses        330      330
  Partials       73       73

Impacted Files
Coverage Δ

pkg/model/types.go
67.30% <100.00%> (+0.64%)
: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 a74d470...c09fb8b. Read the comment docs.

authors: astaticvoid codecov-commenter


text:
Performance issue: Slow retrieval times from Parameter Store in .NET 8 Lambda functions

Describe the bug
Hello,
We have observed that Lambda functions using the .NET 8 runtime experience delays when fetching parameters from AWS Systems Manager Parameter Store. The delay ranges from 4 to 15 seconds, depending on the allocated memory size. This behavior is inconsistent and seems to be more pronounced during cold starts.
Regression Issue

[ ] Select this option if this issue appears to be a regression.

Expected Behavior
We expect a consistent and faster response when fetching parameters from the Parameter Store, regardless of the memory configuration or cold/warm start scenarios.
Current Behavior
Below are the observed results during cold and warm starts for both multiple Parameter Stores and a single Parameter Store:
Cold Start (Full Path Parameter Store):

128MB RAM: 18.637 seconds
512MB RAM: 4.30 seconds
1GB RAM: 1.69 seconds
2GB RAM: 0.81 seconds

Warm Start (Full Path Parameter Store):

128MB RAM: 0.439 seconds
512MB RAM: 0.151 seconds
1GB RAM: 0.127 seconds
2GB RAM: 0.113 seconds

Cold Start (Specific Path Parameter Store):

128MB RAM: 18.338 seconds
512MB RAM: 3.85 seconds
1GB RAM: 1.66 seconds
2GB RAM: 0.94 seconds

Warm Start (Specific Path Parameter Store):

128MB RAM: 0.378 seconds
512MB RAM: 0.036 seconds
1GB RAM: 0.079 seconds
2GB RAM: 0.051 seconds

Reproduction Steps

To reproduce the issue with the slow retrieval times from AWS Systems Manager Parameter Store, follow these steps:
Set up an AWS Lambda function with the .NET 8 runtime.
Use the following code for the Lambda function:

using Amazon.Lambda.Core;
using Microsoft.Extensions.Configuration;
using System.Diagnostics;

// Assembly attribute to enable the Lambda function's JSON input to be converted into a .NET class.
[assembly: LambdaSerializer(typeof(Amazon.Lambda.Serialization.SystemTextJson.DefaultLambdaJsonSerializer))]

namespace GetSSM.LambdaFunction
{
    public class Function
    {
        public string FunctionHandler(object input, ILambdaContext context)
        {
            var stopWatch = new Stopwatch();
            stopWatch.Start();

            var configuration = GetConfiguration();

            stopWatch.Stop();
            var elapsedTime = stopWatch.ElapsedMilliseconds;

            context.Logger.LogInformation($"Get Parameter Store: {elapsedTime} milliseconds");
            context.Logger.LogInformation($"Get Parameter Store: {elapsedTime / 1000.0} seconds");
            return "Hello World";
        }

        public static IConfiguration GetConfiguration()
        {
            var cb = new ConfigurationBuilder().AddSystemsManager(c =>
                {
                    c.Path = "/my/full/path/";
                });

            return cb.Build();
        }
    }
}

Deploy the function and configure an appropriate IAM role with permission to access Parameter Store.
Use AWS Systems Manager Parameter Store to create parameters under both:

A specific path (e.g., /my/full/path/parameter).
A full path structure with multiple parameters.

Test the Lambda function with different memory configurations (e.g., 128MB, 512MB, 1GB, 2GB) and log the results for both:

Cold starts: Ensure the function is invoked after an idle period or by deploying a new version.
Warm starts: Invoke the function repeatedly within a short time span.
Collect the execution times for each scenario and compare the results.

Possible Solution
No response
Additional Information/Context
We’ve also attached a graph visualizing the above results to provide more clarity. This issue seems closely tied to the allocated memory size and the runtime's handling of cold starts.
Key Questions:

Is this behavior expected due to some inherent limitation or design of the library?
Are there any recommendations to mitigate these cold start delays when fetching parameters?
Considering that the function only performs a single GetParameter operation, is it appropriate to scale the memory so significantly to improve performance? Or is there an alternative approach to address this latency without increasing the allocated memory?

Thank you for your assistance! Let us know if further details or tests are required.
AWS .NET SDK and/or Package version used
Amazon.Extensions.Configuration.SystemsManager 6.2.2
Amazon.Lambda.Core 2.2.0
Amazon.Lambda.Serialization.SystemTextJson v
Targeted .NET Platform
.NET 8
Operating System and version
.NET8 Lambda Runtime

@mcamacho97 Good morning. Lambda cold starts are expected for .NET runtime. One of the ways to reduce cold start time is to use Native AOT compilation.

Compile .NET Lambda function code to a native runtime format
Building .NET Lambda functions with Native AOT compilation in AWS SAM for guidance on how to do so.

You may also try to leverage new SnapStart Lambda feature (however, please check pricing considerations).

AWS Lambda SnapStart for Python and .NET functions is now generally available
Improving startup performance with Lambda SnapStart

Increasing memory size could help a bit, but cold start would still be an issue due to container initialization upon first request.
Thanks,
Ashish

repo: aws/aws-dotnet-extensions-configuration


text:
Trace tooling stopped working for newer AL2 instances

We are aware and are working on addressing a know regression with the latest Linux kernels.  It appears a change in the BPF handlers impacts this IMDS analyzer.

Resolved by commit 11bcb33fb74eed077798eff931975c22e288c4bf

repo: aws/aws-imds-packet-analyzer


text:
.AWSIotException: Too many publishes in progress (32202)

com.amazonaws.services.iot.client.AWSIotException: Too many publishes in progress (32202)
        at com.amazonaws.services.iot.client.mqtt.AwsIotMqttConnection.publishMessage(AwsIotMqttConnection.java:92)
        at com.amazonaws.services.iot.client.core.AwsIotConnection.publish(AwsIotConnection.java:161)
        at com.amazonaws.services.iot.client.core.AbstractAwsIotClient.publish(AbstractAwsIotClient.java:186)
        at com.amazonaws.services.iot.client.AWSIotMqttClient.publish(AWSIotMqttClient.java:793)
        at com.amazonaws.services.iot.client.core.AbstractAwsIotClient.publish(AbstractAwsIotClient.java:181)

this is how i'm sending messages to shadow. i'm executing the method which sends out data to the aws for 3 times without an time interval, and i'm getting this error saying too many publishes, is there a solution for this error.
                                    deviceMsg.setQos(AWSIotQos.QOS0);
				deviceMsg.setStringPayload(shadow);
				deviceMsg.setTopic(updateTopic);
				awsIotClient.publish(deviceMsg);

Thank you for your interest in AWS IoT. This message is coming from the Paho MQTT client which limits the maximum number of publishes being queued to the network layer. If you are sharing one MQTT client instance with multiple threads each publishing messages, you may reach the limit. Can you please clarify what you mean by "sends data ... 3 times without an time interval". Is this in a loop with no delay between these data?

what i meant was i am trying to publish data for multiple times without a regular interval inbetween them.
awsIotClient.publish(deviceMsg);

Let's start with basic troubleshooting steps. How often are you calling publish? What is your connectivity to AWS IoT (hardwired/wifi/cellular, latency, bandwidth, packet loss/reliability)?

i was publishing about 6 messages in 2 seconds.now im bundling the all the messages together instead of sending them one by one and the error is now gone. i have a wifi connection.never thought that i'd get an error cz i  have a stable internet connection.thanks for your help i think there should be a interval between publishing, i dont have a interval in between publishing in my application i thought i don't need a one because i'm using a non blocking publish  call

Glad you were able to figure out. Please let us know if you have any more questions about the Java SDK.

authors: hedeshianaws priyamalM

repo: aws/aws-iot-device-sdk-java


text:
[3.x] Enforcing Serial execution for Multi-nics tests and add them in release config

Description of changes

Adding Multple Nics integration tests in released.yaml
Enforcing sequential execution for Multiple-nics tests
Changing the headNode for Multiple-nics tests from p4d.24xlarge to c5n.18xlarge

Tests

Tested the changes in pipelines.

Checklist

[x] Make sure you are pointing to the right branch and add a label in the PR title (i.e. 2.x vs 3.x)
[x] Check all commits' messages are clear, describing what and why vs how.
[x] Make sure to have added unit tests or integration tests to cover the new/modified code.
[x] Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Can you please update the git commit message? It's important to have the most important info in the commit messages rather than in the PR description.
The commit history is our source of knowledge, so let's be sure to describe on it why we are doing a specific change.

repo: aws/aws-parallelcluster


text:
Incorrect AthenaError in Aws::Utils::Outcome<T, AthenaError> Template

Describe the bug
AthenaError exists twice: First one here and second time here.
Due to a namespace problem, the Outcome template uses the incorrect AthenaError (second one), same problem exists for all these methods as well.
This causes the following code not to compile:
auto outcome = client.ListNamedQueries(request);

// this should & used to work, now fails :(
outcome.GetError().GetExceptionName();

Expected behavior
auto outcome = client.ListNamedQueries(request);
outcome.GetError().GetExceptionName();

Should work and  probably use this class.
Current behavior
Aws::Utils::Outcome<T, AthenaError> template uses the incorrect AthenaError causing a compile error.
Steps to Reproduce
auto outcome = client.ListNamedQueries(request);
outcome.GetError().GetExceptionName();

Possible Solution
No response
AWS CPP SDK version used
main / e5dc51c
Compiler and Version used
Clang 13.0.0
Operating System and version
MacOS 11.6.1

Looks like this was fixed in pull/1988 and has been available since version 1.9.295

authors: livioso sbiscigl

repo: aws/aws-sdk-cpp