text:
fix(deployment): forward interrupt from list groups operation

Issue #, if available:
Description of changes:
If DefaultDeploymentTask is interrupted while performing listThingGroupsForDevice, forward the interrupt, rather than marking the deployment as FAILED_NO_STATE_CHANGE
Why is this change necessary:
Customer logs show an Error occurred while processing deployment error for a deployment that was actually canceled in favor of a newer deployment.
2023-10-13T11:12:30.506Z [INFO] (pool-2-thread-17) com.aws.greengrass.deployment.ThingGroupHelper: get-thing-group-hierarchy. task failed and will be retried. {task-attempt=1}
software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: No supported CertificateVerify signature algorithm for RSA  key
	at software.amazon.awssdk.core.exception.SdkClientException$BuilderImpl.build(SdkClientException.java:102)
	at software.amazon.awssdk.core.exception.SdkClientException.create(SdkClientException.java:47)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.utils.RetryableStageHelper.setLastException(RetryableStageHelper.java:211)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:83)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:36)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56)
	at software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:60)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:42)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallMetricCollectionStage.execute(ApiCallMetricCollectionStage.java:48)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallMetricCollectionStage.execute(ApiCallMetricCollectionStage.java:31)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:37)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:26)
	at software.amazon.awssdk.core.internal.http.AmazonSyncHttpClient$RequestExecutionBuilderImpl.execute(AmazonSyncHttpClient.java:193)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.invoke(BaseSyncClientHandler.java:103)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.doExecute(BaseSyncClientHandler.java:171)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.lambda$execute$1(BaseSyncClientHandler.java:82)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.measureApiCallSuccess(BaseSyncClientHandler.java:179)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:76)
	at software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45)
	at software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:56)
	at software.amazon.awssdk.services.greengrassv2data.DefaultGreengrassV2DataClient.listThingGroupsForCoreDevice(DefaultGreengrassV2DataClient.java:303)
	at com.aws.greengrass.deployment.ThingGroupHelper.lambda$listThingGroupsForDevice$2(ThingGroupHelper.java:83)
	at com.aws.greengrass.util.RetryUtils.runWithRetry(RetryUtils.java:50)
	at com.aws.greengrass.deployment.ThingGroupHelper.listThingGroupsForDevice(ThingGroupHelper.java:73)
	at com.aws.greengrass.deployment.DefaultDeploymentTask.getNonTargetGroupToRootPackagesMap(DefaultDeploymentTask.java:198)
	at com.aws.greengrass.deployment.DefaultDeploymentTask.call(DefaultDeploymentTask.java:115)
	at com.aws.greengrass.deployment.DefaultDeploymentTask.call(DefaultDeploymentTask.java:50)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: javax.net.ssl.SSLException: No supported CertificateVerify signature algorithm for RSA  key
	at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133)
	at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
	at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:340)
	at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:296)
	at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:287)
	at java.base/sun.security.ssl.CertificateVerify$T12CertificateVerifyMessage.<init>(CertificateVerify.java:598)
	at java.base/sun.security.ssl.CertificateVerify$T12CertificateVerifyProducer.produce(CertificateVerify.java:761)
	at java.base/sun.security.ssl.SSLHandshake.produce(SSLHandshake.java:436)
	at java.base/sun.security.ssl.ServerHelloDone$ServerHelloDoneConsumer.consume(ServerHelloDone.java:182)
	at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:392)
	at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:443)
	at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:421)
	at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:183)
	at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:172)
	at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1507)
	at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1417)
	at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:456)
	at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:427)
	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:436)
	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384)
	at software.amazon.awssdk.http.apache.internal.conn.SdkTlsSocketFactory.connectSocket(SdkTlsSocketFactory.java:75)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
	at software.amazon.awssdk.http.apache.internal.conn.ClientConnectionManagerFactory$DelegatingHttpClientConnectionManager.connect(ClientConnectionManagerFactory.java:86)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
	at software.amazon.awssdk.http.apache.internal.impl.ApacheSdkHttpClient.execute(ApacheSdkHttpClient.java:72)
	at software.amazon.awssdk.http.apache.ApacheHttpClient.execute(ApacheHttpClient.java:254)
	at software.amazon.awssdk.http.apache.ApacheHttpClient.access$500(ApacheHttpClient.java:104)
	at software.amazon.awssdk.http.apache.ApacheHttpClient$1.call(ApacheHttpClient.java:231)
	at software.amazon.awssdk.http.apache.ApacheHttpClient$1.call(ApacheHttpClient.java:228)
	at software.amazon.awssdk.core.internal.util.MetricUtils.measureDurationUnsafe(MetricUtils.java:63)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.executeHttpRequest(MakeHttpRequestStage.java:77)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:56)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:39)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:73)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:42)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:78)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:40)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:50)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:36)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:81)
	... 32 more

2023-10-13T11:17:14.019Z [INFO] (AwsEventLoop 3) com.aws.greengrass.deployment.ShadowDeploymentListener: Added shadow deployment job. {ID=arn:aws:greengrass:eu-central-1:****:configuration:thing/****:82}
2023-10-13T11:17:23.289Z [INFO] (pool-2-thread-16) com.aws.greengrass.deployment.DeploymentService: Canceling current device deployment. {DeploymentId=arn:aws:greengrass:eu-central-1:****:configuration:thing/****:81, GreengrassDeploymentId=738e982c-ee2c-49a3-8dbd-29d4650b92c5, serviceName=DeploymentService, currentState=RUNNING}
2023-10-13T11:17:23.293Z [ERROR] (pool-2-thread-17) com.aws.greengrass.deployment.DeploymentService: Error occurred while processing deployment. {deploymentId=738e982c-ee2c-49a3-8dbd-29d4650b92c5, serviceName=DeploymentService, currentState=RUNNING}
com.aws.greengrass.deployment.exceptions.DeploymentTaskFailureException: Error fetching thing group information
	at com.aws.greengrass.deployment.DefaultDeploymentTask.getNonTargetGroupToRootPackagesMap(DefaultDeploymentTask.java:216)
	at com.aws.greengrass.deployment.DefaultDeploymentTask.call(DefaultDeploymentTask.java:115)
	at com.aws.greengrass.deployment.DefaultDeploymentTask.call(DefaultDeploymentTask.java:50)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.InterruptedException: sleep interrupted
	at java.base/java.lang.Thread.sleep(Native Method)
	at com.aws.greengrass.util.RetryUtils.runWithRetry(RetryUtils.java:66)
	at com.aws.greengrass.deployment.ThingGroupHelper.listThingGroupsForDevice(ThingGroupHelper.java:73)
	at com.aws.greengrass.deployment.DefaultDeploymentTask.getNonTargetGroupToRootPackagesMap(DefaultDeploymentTask.java:198)
	... 6 more

How was this change tested:

[x] Updated or added new unit tests.
[ ] Updated or added new integration tests.
[ ] Updated or added new end-to-end tests.
[ ] If my code makes a remote network call, it was tested with a proxy.

Any additional information or context required to review the change:
Documentation Checklist:

[ ] Updated the README if applicable.

Compatibility Checklist:

[ ] I confirm that the change is backwards compatible.
[ ] Any modification or deletion of public interfaces does not impact other plugin components.
[ ] For external library version updates, I have reviewed its change logs and Nucleus does not consume
any deprecated method or type.

Refer to Compatibility Guidelines for more information.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Still want this?

repo: aws-greengrass/aws-greengrass-nucleus


text:
feat: Add argocd_projects field to Argocd addons

What does this PR do?

Adding new argocd_projects field to ArgoCD addons. This feature allows users to create additional ArgoCD projects during the creation and update.

Motivation

Resolves #12 https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/issues/56

More

[x] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[x] Yes, I ran pre-commit run -a with this PR

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes
I want to provide docs as well unfortunately there is no docs directory in this repo. But I wrote docs in this PR - https://github.com/aws-ia/terraform-aws-eks-blueprints/pull/1413

@bryantbiggs why is this PR only left always? what do I need to do?

I will defer to @csantanapr for review - I was simply updating the PR to see if we were able to resolve the pr-title check issue (which it seems we have not, yet. not related to this PR)

source: gharchive/pull-request

authors: bryantbiggs dtherhtun

license_type: permissive

license_source: github-api


text:
Fix css missing semicolons

Some semicolons were giving an error, others not.
Overview
Added some missing semicolons in the css file.
Testing/Steps taken to ensure quality
They are just css small fixes. Shouldn't give any error.
Notes
Also fixed a misspelled css keyword. (L. 139)
    border-bottom-: 1px solid #C1C3D1;

Codecov Report

Merging #428 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #428      +/-   ##
==========================================
- Coverage   76.61%   76.57%   -0.04%
==========================================
  Files          30       30
  Lines        2771     2771
==========================================
- Hits         2123     2122       -1
- Misses        648      649       +1

Impacted Files
Coverage Δ

taskcat/_cfn/template.py
84.31% <0%> (-0.99%)
:arrow_down:

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 c280356...7acc55f. Read the comment docs.

authors: codecov-io ekzGuille

repo: aws-quickstart/taskcat

license_source: bigquery


text:
Enhancement: Generate QR Code For Invite Link

It would be awesome if the app could generate a QR code and display it in a dialog when clicking the 'Copy Invite Link' button. This would make it very easy to demo this application during a presentation or workshop so that a guest can scan the code and quickly join the session.

@recursivecodes - I've implemented a basic version of this in the following branch: https://github.com/aws-samples/amazon-ivs-real-time-basic-web-demo/pull/4.
Please check out the branch and let me know if it works for you use-case. Thanks!

Merged #4

source: gharchive/issue

authors: recursivecodes slee-aws


text:
Update CF template to support Fault Tolerant Elastic Search domain (2xinstances)

Expected Behavior
Customer lost QnA Content after node failure on default single instance ES domain.
While the blog does state that the dafault ES domain should be increased to 2 instances for production deployments, we could increase awareness if QnABot CF template supported provisioning fault tolerant elastic search domain (2 x Instances) by default. User should still be allowed to provision single node non-fault-tolerant domain for non-production / non-critical deployments.

fixed in v2

authors: JohnCalhoun rstrahan

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


text:
add missing pieces of schema.graphql

Description of changes:
I opened a case with AWS support (Case #: 6541224261) after finding myself unable to run "amplify push" after making any Graphql API changes in this sample project. Alan M. from AWS support determined this was caused by some missing parts of the schema.graphql file and gave me the following workaround to generate the missing code using the AWS CLI.
1. Clone the repo
2. Run the following commands (without the '$'):
   $ cd aws-appsync-visualization-with-athena-app
   $ yarn
3. Modify the bucket configuration in parameters.json as described in the README.
4. Run the following commands to initialise the app and create the stack:
   $ amplify init
   $ amplify push
5. Wait for the stack creation to complete and run the following to open the AppSync API in the web console:
   $ amplify console api
   Choose 'GraphQL'. A browser tab/window should open with the associated API. Go to the "Settings" page of the API and note the "API ID"
6. Change directory to the api configuration folder:
   $ cd amplify/backend/api/appsyncathenaviz
7. Run the following CLI command to get the correct schema.graphql file. Replace <API_ID> with the ID noted in step 5.
   $ aws appsync get-introspection-schema --api-id <API_ID> --format SDL schema.graphql
8. Update the stack:
   $ amplify push
   After this change, you should be able to modify API using the schema.graphql file.

This PR replaces the existing schema.graphql file with a schema.graphql generated by the AppSync service/AWS CLI after deploying the base sample project.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

the reason the schema was essentially blank is because the Amplify CLI did not support Multi-Auth until recently. The API was first being created and then updated to support Multi-Auth via the CustomResources.json.
We just pushed a change to support this. closing the PR.

authors: onlybakam rkeiii


text:
Enhancement: Automate TAO dashboard refresh

The current TAO dashboard is updated manually using a set of shell commands. The process is time consuming and not convenient for organizations that want to schedule Trusted Advisor reports generation.

https://www.wellarchitectedlabs.com/cost/300_labs/300_optimization_data_collection/

authors: megareez sdpoueme


text:
fixing typo on to our

Issue #, if available:
Description of changes:
Updating readme instructions for module 5 under Amazon API Gateway Rest API
"Doing so would require us to manage AWS credentials within on frontend code to authorize those API requests to the PutRecord API"
to
"Doing so would require us to manage AWS credentials within our frontend code to authorize those API requests to the PutRecord API"
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thanks for catching this too!


text:
Provide cost usage

Hi,
Could be helpful to provide a cost usage for this workshop in case customers would like to run it on their own.
Br,

Some safe guards we could use to help slow down costs would be helpful too.  At this point I'm abandoning running the cluster and plan to just read through the material due due to costs.
This is after figuring out how to replace the M5.Large machines with T3.Smalls - which helped with billing, but I've no idea how it's negatively impacted the workshop.  A few things haven't gone as designed and it's made it difficult to tell if it's performance due to my action or something else.  Restarting the Cloud9 session by doing this over days has caused me to run into variables missing at times too because it was assumed my session still had the required information.

Just got burnt by this. $50 bill and only this much thanks to the limit alert email that also had a link to the billing page. Incidentally, the 'free' tier allowance must be really meagre if a handful of chapters from the workshop can exhaust it within days.
IMO the problem is this page. The YAML doesn't show the instance type, which I understand defaults to m5.large, and if shown might have at the very least prompted me to research the cost. No information on the page itself on the cost involved either.
The guys in the video here mention to choose t2.micro for Cloud9 if you "really want to save money", which is peanuts compared to the trap that awaits the participant of the workshop later on.
As things stand, if you're following the workshop at a casual pace, by the time you get to cleanup you can expect a nasty surprise.
This is my first experience with AWS, not impressed.

@johnnybaloney I'm sorry to hear that!
We've been noodling on how to get the cost down, and these are the ideas that we seem to be circling around:

swap to T series worker nodes
swap managed nodegroups to spot priced nodes
as part of the cloud9 setup, also set a daily billing alarm... something like "alarm if we spend more than $2/day" (amount to be validated)

@johnnybaloney can you reach out to me via twitter, or email? twitter: @brentContained and email: blangs@amazon.com

authors: Rick-2CA brentley gfediere johnnybaloney

repo: aws-samples/eks-workshop


text:
adding pytorch files

Initial add of the PyTorch training notebook for module 3.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Initial add of the PyTorch training notebook for module 3.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ccrngd1 Thanks men! 2 small changes and we can merge this.

create tensorflow and pytorch folder structure in module 3 training.  Have a separate folder for each framework (check out module 4 as an example).

What kernel did you use? If use used Data Science kernel, can you add the pip install for these? If you used a different kernel, can you update the markdown notes and the readme file?

import torchvision, torch
import torchvision.transforms as transforms

@jingswu ok, added the ReadMe notes and added the Tensorflow/Pytorch folder structure.  Let me know if this looks right now.


text:
Search Error : index_not_found_exception'

Hello
The stack is well deployed in us-east-1. No problem.
Videos are well indexed. And GenAI Playground works
But the search doesn't work
errorMessage	"NotFoundError(404, 'index_not_found_exception', 'no such index [video_frame_76cf8707-5c8d-420d-b117-f986cb8126e4]', video_frame_76cf8707-5c8d-420d-b117-f986cb8126e4, index_or_alias)"
errorType	"NotFoundError"
requestId	"864f1749-198c-4c28-9e2f-0f323d56eb63"
stackTrace	[ ' File "/var/task/extr-srv-get-video-tasks.py", line 71, in lambda_handler\n embedding_result = search_text_embedding(search_text, task_ids, score_threshold)\n', ' File "/var/task/extr-srv-get-video-tasks.py", line 211, in search_text_embedding\n response = opensearch_client.search(\n', ' File "/opt/python/opensearchpy/client/utils.py", line 181, in _wrapped\n return func(*args, params=params, headers=headers, **kwargs)\n', ' File "/opt/python/opensearchpy/client/__init__.py", line 1742, in search\n return self.transport.perform_request(\n', ' File "/opt/python/opensearchpy/transport.py", line 448, in perform_request\n raise e\n', ' File "/opt/python/opensearchpy/transport.py", line 409, in perform_request\n status, headers_response, data = connection.perform_request(\n', ' File "/opt/python/opensearchpy/connection/http_urllib3.py", line 290, in perform_request\n self._raise_error(\n', ' File "/opt/python/opensearchpy/connection/base.py", line 316, in _raise_error\n raise HTTP_EXCEPTIONS.get(status_code, TransportError)(\n' ]
0	' File "/var/task/extr-srv-get-video-tasks.py", line 71, in lambda_handler\n embedding_result = search_text_embedding(search_text, task_ids, score_threshold)\n'
1	' File "/var/task/extr-srv-get-video-tasks.py", line 211, in search_text_embedding\n response = opensearch_client.search(\n'
2	' File "/opt/python/opensearchpy/client/utils.py", line 181, in _wrapped\n return func(*args, params=params, headers=headers, **kwargs)\n'
3	' File "/opt/python/opensearchpy/client/__init__.py", line 1742, in search\n return self.transport.perform_request(\n'
4	' File "/opt/python/opensearchpy/transport.py", line 448, in perform_request\n raise e\n'
5	' File "/opt/python/opensearchpy/transport.py", line 409, in perform_request\n status, headers_response, data = connection.perform_request(\n'
6	' File "/opt/python/opensearchpy/connection/http_urllib3.py", line 290, in perform_request\n self._raise_error(\n'
7	' File "/opt/python/opensearchpy/connection/base.py", line 316, in _raise_error\n raise HTTP_EXCEPTIONS.get(status_code, TransportError)(\n'

Resolved in the latest version.

authors: gmarchand lanazhang


text:
Add feature to save schemas

Users have to map schemas each time they upload a file.
Possible to use the API rather than the frontend for this?

We should use the following file picker:
https://bootstrap-vue.org/docs/components/form-file

authors: andrewmarriott-aws ianwow


text:
Cherry-pick: Reintroduce MBT to CMake and the windows test project. (#2222)

Cherry picks the following commit from master:

Reintroduce MBT to CMake and the windows test project.

Checklist:

[x ] I have tested my changes. No regression in existing tests.
[x ] My code is Linted.

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

/bot run checks

/bot run checks

/bot run checks

/cbmc run checks

repo: aws/amazon-freertos

license: MIT


text:
Update mbedtls to v2.16.10

Description
Updates mbedtls library pointer to the latest version of the 2.16 LTS release.
Checklist:

[x] I have tested my changes. No regression in existing tests.
[x] My code is Linted.

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

/bot run checks


text:
Would like to better understand the benefits of using AWS Amplify Authentication.

This looks like an awesome new tool. Can you help me answer the following question?
When not using aws-amplify-react or aws-amplify-react-native what is the main benefit of using the AWS Amplify Auth module over using Cognito directly?

Goal of AWS Amplify Auth is to make common tasks easy, let developer focus on their business differentiators.
Amazon Cognito signUp:
var poolData = {
        UserPoolId : '...', // Your user pool id here
        ClientId : '...' // Your client id here
    };
    var userPool = new AWSCognito.CognitoIdentityServiceProvider.CognitoUserPool(poolData);

    var attributeList = [];

    var dataEmail = {
        Name : 'email',
        Value : 'email@mydomain.com'
    };

    var dataPhoneNumber = {
        Name : 'phone_number',
        Value : '+15555555555'
    };
    var attributeEmail = new AWSCognito.CognitoIdentityServiceProvider.CognitoUserAttribute(dataEmail);
    var attributePhoneNumber = new AWSCognito.CognitoIdentityServiceProvider.CognitoUserAttribute(dataPhoneNumber);

    attributeList.push(attributeEmail);
    attributeList.push(attributePhoneNumber);

    userPool.signUp('username', 'password', attributeList, null, function(err, result){
        if (err) {
            alert(err);
            return;
        }
        cognitoUser = result.user;
        console.log('user name is ' + cognitoUser.getUsername());
    });

AWS Amplify signUp:
Amplify.configure(aws_exports);

Auth.signUp('username', 'password', 'email@mydomain.com', '+15555555555')
    .then(user => console.log(user))
    .catch(err => console.log(err));

Amplify also manages AWS Credentials gathered from Amazon Cognito Federated Identities (the above example is for Amazon Cognito User Pools). For example Instead of following this process and then signing, such as sending requests to Amazon API Gateway, Amplify does this all under the covers for you.

authors: palafranchise richardzcode undefobj

repo: aws/aws-amplify


text:
Undefined reference to SIGPIPE when curl enabled on windows.

What platform/OS are you using?
Windows 10
What compiler are you using? what version?
VS Pro 2015
Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24210 for x64
What's your CMake arguments?
cmake -G "Ninja" ^
-DBUILD_ONLY="core;s3" ^
-DCMAKE_BUILD_TYPE=Release ^
-DCMAKE_INCLUDE_PATH=D:/drb/vs14_x64/deps/include ^
-DCMAKE_INSTALL_PREFIX=D:/drb/vs14_x64/deps ^
-DCMAKE_LIBRARY_PATH=D:/drb/vs14_x64/deps/lib ^
-DENABLE_OPENSSL_ENCRYPTION=ON ^
-DFORCE_CURL=ON ^
D:/drb/vs14_x64/aws/aws-sdk-cpp-1.3.19
Can you provide a TRACE level log? (sanitize any sensitive information)
Compiler error in file:
Trying to use curl on windows.
File:  aws-sdk-cpp-1.3.19/aws-cpp-sdk-core/source/http/HttpClientFactory.cpp this code references undefined SIGPIPE (linux signal)
#if ENABLE_CURL_CLIENT
static void LogAndSwallowHandler(int signal)
{
switch(signal)
{
case SIGPIPE:
AWS_LOGSTREAM_ERROR(HTTP_CLIENT_FACTORY_ALLOCATION_TAG, "Received a SIGPIPE error");
break;
default:
AWS_LOGSTREAM_ERROR(HTTP_CLIENT_FACTORY_ALLOCATION_TAG, "Unhandled system SIGNAL error"  << signal);
}
}
#endif
Also:
SignalHandlerTest.cpp needs to be fixed...

So... you were using Ninja to generate VS build artifact and using CURL on windows.?

Yes, Ninja is just the build system. Will get the same results with nmake. We'd like to experiment using curl instead of win inet under the hood.  I did hack the code and got everything to compile but code crashed. I did not have time to dig into where it crashed.  If I compile the aws sdk without curl everything works. I was wondering if anyone has had success with aws+curl on windows?

"Undefined reference" is a linker error and is misleading. What you have is an undefined symbol.

SIGPIPE is not defined on windows. It's a linux signal. On my system it's defined in:
/usr/include/asm/signal.h (Fedora 27).
Code in:
aws/latest/aws-cpp-sdk-core/source/http/HttpClientFactory.cpp
Line: 55 if referencing SIGPIPE here:
#if ENABLE_CURL_CLIENT
static void LogAndSwallowHandler(int signal)
{
switch(signal)
{
case SIGPIPE:
AWS_LOGSTREAM_ERROR(HTTP_CLIENT_FACTORY_ALLOCATION_TAG, "Received a SIGPIPE error");
break;
default:
AWS_LOGSTREAM_ERROR(HTTP_CLIENT_FACTORY_ALLOCATION_TAG, "Unhandled system SIGNAL error"  << signal);
}
}
#endif
Thanks...

Build error:
[166/373] Building CXX object aws-cpp-sdk-core\CMakeFiles\aws-cpp-sdk-core.dir\source\http\HttpClientFactory.cpp.obj
FAILED: aws-cpp-sdk-core/CMakeFiles/aws-cpp-sdk-core.dir/source/http/HttpClientFactory.cpp.obj
C:\PROGRA~2\MICROS~1.0\VC\bin\amd64\cl.exe  /nologo /TP -DAWS_CORE_EXPORTS=1 -DENABLE_BCRYPT_ENCRYPTION -DENABLE_CURL_CLIENT -DPLATFORM_WINDOWS -DUSE_IMPORT_EXPORT=1 -DUSE_WINDOWS_DLL_SEMANTICS -Daws_cpp_sdk_core_EXPORTS -ID:\drb\vs14_x64\deps\include -ID:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\include\aws\core\platform\refs -ID:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\include /DWIN32 /D_WINDOWS /W4 /GR /EHsc /MP /bigobj /WX /MD /O2 /Ob2 /DNDEBUG /Zi /showIncludes /Foaws-cpp-sdk-core\CMakeFiles\aws-cpp-sdk-core.dir\source\http\HttpClientFactory.cpp.obj /Fdaws-cpp-sdk-core\CMakeFiles\aws-cpp-sdk-core.dir\ /FS -c D:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\source\http\HttpClientFactory.cpp
D:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\source\http\HttpClientFactory.cpp(64): error C2065: 'SIGPIPE': undeclared identifier
D:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\source\http\HttpClientFactory.cpp(64): error C2131: expression did not evaluate to a constant
D:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\source\http\HttpClientFactory.cpp(64): note: failure was caused by non-constant arguments or reference to a non-constant symbol
D:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\source\http\HttpClientFactory.cpp(64): note: see usage of 'SIGPIPE'
D:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\source\http\HttpClientFactory.cpp(64): error C2051: case expression not constant
D:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\source\http\HttpClientFactory.cpp(71): warning C4065: switch statement contains 'default' but no 'case' labels
D:\drb\vs14_x64\aws\aws-sdk-cpp-1.3.19\aws-cpp-sdk-core\source\http\HttpClientFactory.cpp(129): error C2065: 'SIGPIPE': undeclared identifier

Fixed at https://github.com/aws/aws-sdk-cpp/commit/1e5c0604259e3f08d3387747fbb677ee369b5b3b

authors: Bu11etmagnet dburken singku

repo: aws/aws-sdk-cpp


text:
Unity 2017.2 Multipart UploadPartResponse missing ETag

In Unity 2017.2, the ETag property from the UploadPartResponse is missing, although it is present in the HTTP response. (Checked with Fiddler). This causes CompleteMultiPartUploadAsync to fail with a malformed XML error, due to the missing ETags.
Expected Behavior
UploadPartResponse should not have a null ETag.
Current Behavior
UploadPartResponse ETag is null.
Possible Solution
Downgrading from Unity 2017.2 to Unity 2017.1 is a temporary work-around that resolves the issue. Unity 2017.2 changed the behaviour of UnityWebRequest, maybe this is related?
Your Environment

AWSSDK.Core version used: 3.3.174.0
Service assembly and version used: 3.3.174.0
Operating System and version: Windows 10 Home 64-Bit
Visual Studio version: Visual Studio Community 2017
Targeted .NET platform: 3.5

Any update on whether or not this issue has been resolved for Unity 2017.2? I have no time to look into this, and have rolled Unity back to 2017.1 as a result.

It's been a while, but I will be attempting to upgrade our project to Unity 2018 tomorrow, and get back to this issue with the results.

This bug has disappeared in Unity 2018.1.6f1 with AWS SDK version 3.3.307.0 so I am closing the issue.

repo: aws/aws-sdk-net


text:
Add alpine tag for container

Using Amazon 2 will detected the CVEs by Trivy

CVE-2021-3177
CVE-2016-2183
CVE-2019-20907
CVE-2020-26116

Although we are not using python, it still exist in the OS. Could we add more tags for different OS or delete some unused packages(e.g. usr/lib64/python2.7/lib-dynload/Python-2.7.18-py2.7.egg-info) when building image?

Hi @evan361425
Thanks for bringing this to our notice. Adding some links for the CVEs so that they are easier to find.
https://nvd.nist.gov/vuln/detail/CVE-2021-3177
https://nvd.nist.gov/vuln/detail/CVE-2016-2183
https://nvd.nist.gov/vuln/detail/CVE-2019-20907
https://nvd.nist.gov/vuln/detail/CVE-2020-26116
Did you find these CVEs in the Dockerhub image or the public ECR image?
I believe that since the public ECR image is built from scratch as base image, it shouldn't contain these python related vulnerabilities. Can you verify that?

I found it in Docker Hub image.
I do confirm the image have the python files (that is why Trivy shown the vulnerabilities):
$ docker run --net=host -e AWS_REGION=ap-northeast-1 -d amazon/aws-xray-daemon -o
87a4e6fc6975816793ca648a42f116fedfc242e0d9d427f84357622a98269110

$ ls -l /usr/lib64 | grep python
-rwxr-xr-x  1 root root 1790912 Jun 10  2021 libpython2.7.so.1.0
drwxr-xr-x 27 root root   20480 Dec  1 18:20 python2.7

Hi @evan361425
Would it be possible for you to use the public ECR image instead of the DockerHub one?
At this point I'm not sure if we remove the Python module from the image, it won't break its functionality or have other implications. Since the daemon itself is a GoLang program and doesn't use Python in any form, I believe these vulnerabilities are not exploitable for the daemon.

Hi @srprash.
If removing the vulnerable package will break the functionality then we are using the vulnerable package implicitly and we should fix it.
If not then removing it makes this issue kind of enhancement request.
Making container image more tiny is a good practice anyway.
The reason I open this issue is Trivy detect the vulnerable package and start warning. Trivy don't know whether application use the package or not. It just detect the existence of vulnerability.
For your information I have remove the package and commit a new tag myself to fix Trivy warning and it works fine in lab environment.

repo: aws/aws-xray-daemon


text:
Support build-your-own Ubuntu AMI through image-builder CLI

This PR adds support for building your own AMIs via the image-builder CLI. At the moment, only Ubuntu is supported as the OS. With this change, Ubuntu AMI builds in CI will use the image-builder CLI instead of invoking Packer directly.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test aws-image-builder-presubmit

/approve

/cherrypick release-0.12

repo: aws/eks-anywhere-build-tooling


text:
Bump bottlerocket-bootstrap to Go 1.22, rename Go modules for consistency

This PR bumps the Go version for bottlerocket-bootstrap project to Go 1.22 and renames the Go module name of this project and the aws/upgrader project to the format github.com/aws/eks-anywhere-build-tooling/<project name>, similar to aws/image-builder.
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.

/lgtm
/approve


text:
Bring in Cobra and Viper

Closes: https://github.com/aws/eks-anywhere-packages/issues/656

Closes: https://github.com/aws/eks-anywhere-packages/issues/656

The new main.go almost looks quite slim and maybe not too useful to have anymore.
Everything else looks good.
/lgtm
/approve

/unapprove

you can /approve when you're ready to merge.

/approve

authors: TerryHowe jonahjon

repo: aws/eks-anywhere-packages


text:
Add tinkerbell chart presubmits

Issue #, if available:
Description of changes:
Add presubmits for the upstream tinkerbell chart and tinkerbell crds projects
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

repo: aws/eks-anywhere-prow-jobs


text:
eksctl install instructions invalid

The current manual Linux install instructions for Linux are invalid. EKSCTL changed homes to github/eksctl-io
These instructions, https://anywhere.eks.amazonaws.com/docs/getting-started/install/
Need to be updated to match these instructions
https://eksctl.io/introduction/#for-unix

Fixed by #6803

authors: abhay-krishna raykrueger

repo: aws/eks-anywhere


text:
Strip superfluous Tinkerbell configuration from DatacenterConfig

Remove superfluous Tinkerbell configuration.
The removed configuration items were only necessary when deploying the stack independently of cluster provisioning. Having Kubeified and implemented the --setup-tinkerbell functionality we no longer need the configuration as its configured in a different way without user input.

/cc @ptrivedi @pokearu @abhinavmpandey08 @panktishah26 @gwesterfieldjr @jacobweinstock

I just noticed a bunch of formatting changes - my fault! They aren't particularly extensive and those PR is entirely about removing the unused datacenterconfig fields so I'll leave as is.


text:
Remove curated package list from concepts page

Description of changes:
This PR removes the curated package list from concepts page as it is already being referenced on the same page above as a hyperlink to the updated list in the package management section. It makes sense to have a single source of truth for the updated list of curated packages.
Testing (if applicable):
make build
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.21

/cherry-pick release-0.20

/cherry-pick release-0.19

/approve


text:
Configure base image Prowjobs to push to eks-distro-build-tooling ECR public registry

We want to push the builder-base and eks-distro-base images to the eks-distro-build-tooling public registry in a verified account.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold
Holding until the account is verified and we have the custom alias.

/unhold

repo: aws/eks-distro-prow-jobs


text:
Python: add BZPOPMIN and BZPOPMAX commands

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

redis docs:

https://redis.io/docs/latest/commands/bzpopmin/
https://redis.io/docs/latest/commands/bzpopmax/

includes value conversion:

BZPOPMIN/BZPOPMAX returns an array containing a key, member, and score. RESP2 returns the score as a string, but RESP3 returns the score as a double. The value conversion added in this PR ensures the score is always returned as a double

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

@shohamazon Thanks for the review, all comments are addressed now

repo: aws/glide-for-redis


text:
Cannot build interface necessary for flink.Application property

:bug: Bug Report
Affected Languages

[ ] TypeScript or Javascript
[X] Python
[ ] Java
[ ] .NET (C#, F#, ...)
[ ] Go

What is the problem?
Following the documentation described in the Flink readme will result in a build failure
        flink.Application(self, 'app',
            property_groups=flink.PropertyGroups(FlinkApplicationProperties={
                "input_stream_name": "MyName"
            })
        )

There doesn't seem to be any other ways of properly inputting the property here either. Maybe there's something I'm missing?
Error message
TypeError: __init__() got an unexpected keyword argument 'FlinkApplicationProperties'
The interface PropertyGroups is defined in typescript here
Other
This was originally reported and is described in further detail here

I can confirm that this affects the Java CDK as well (at least through CDK v1, I haven't tested on CDK v2). This is also documented on StackOverflow with no current answer or workaround (from 10 months ago): https://stackoverflow.com/questions/67878668/aws-cdk-java-api-propertygroups-builder-not-working

authors: hindmanj peterwoodworth

repo: aws/jsii


text:
chore: Enable userAgent version specification in operator

Fixes #N/A
Description
This PR enables version to be specified and injected during the binary build to log the version and add the version to the userAgent that is stored in the metadata information when Karpenter makes calls to the apiserver.
You can inject the version when you build the binary by running the following:
go build cmd/controller/main.go GOFLAGS="-ldflags=-X=github.com/aws/karpenter-core/pkg/operator.Version=$(shell git describe --tags --always)"

How was this change tested?
make apply
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build 6570988105

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.04%) to 82.285%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/provisioning/scheduling/topology.go
2
86.49%

pkg/controllers/provisioning/scheduling/topologygroup.go
2
96.75%

Totals

Change from base Build 6570607328:
-0.04%

Covered Lines:
9183

Relevant Lines:
11160

💛  - Coveralls

authors: coveralls jonathan-innis

repo: aws/karpenter-core


text:
Official documentation for fallback from spot to on-demand configuration.

What karpenter features are relevant?
Spot, on-demand.
How should the docs be improved?
I know there is no native karpenter solution to fallback to on-demand instances if spot is not available yet and you are working on that. If it's true, that we can configure karpenter in this way (within fallback to on-demand if spot is not available (no spot capacity / quota is reached / other)) will be super to see how to do that in the official karpenter information (as a 'fallback to on-demand' section').
I can understand that it's not a karpenter feature but rather pod configuration but if you can describe it (e.g. within some example of provisioner configuration and pod configuration (within nodeAffinity / preference section ?)) it can be really helpful.
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 "me too" comments, 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

🤔 I can see documentation is changing dynamically (so cool and tx a lot!) 😄 I can see there is such section now: https://karpenter.sh/v0.5.3/tasks/running-pods/#node-affinity-nodeaffinity and I think it's mostly what I was asking for.
As there is no information directly about fallback to on-demand I don't close this gentle request and want to ask you to decide if you want to close it (as actual documentation is good enough for spot vs ondemand case) or you want to back to that later and add such direct example.

We can revisit this once we have the fallback to OD support available in Karpenter.
I guess at the moment you found what you were looking for :)
I will close this issue for now :)

We need to document this more explicitly. If your provisioner supports capacitytype=[spot, on-demand], karpenter will prioritize spot, and launch on demand if every instance type is out of capacity. Leaving this open as a docs issue.

The link above is no longer works, however this link currently has the documentation: https://karpenter.sh/docs/concepts/nodepools/#capacity-type

Thanks @bitshop for helping point anyone who comes here to the right place 🎉

authors: Miszcz-AndY andy-miszcz bitshop ellistarn jonathan-innis prateekgogia

repo: aws/karpenter-provider-aws


text:
Why is the package rate so high, but no new machines are started.

Description
version: 0.30.0
Why is the package rate so high, but no new machines are started.  Is it possible to control this value, e.g. if it is higher than 80% a new machine is started.

(use this tool to observe node package rate: https://github.com/awslabs/eks-node-viewer)

Why is the package rate so high

You can't tune this value right now since we are assuming that you have set your application requests correctly which means that we are maximizing the utilization of your nodes, driving down the cost of the cluster. What's the reason you want overhead on your nodes and don't want them fully utilized?

I think there might be cases when you need to deploy something on top of everything that is already running and daemon-sets won't trigger new nodes or any kind of rescheduling. So they sit their infinitively and won't get scheduled which makes it sometimes really hard to use temporary troubleshooting or security tools, like Trivy, Kubeshark, etc.
A setting that would allow to control the max. utilisation of any node would be great to leave some room for emergency use cases.

If you schedule a DaemonSet with a higher priority class, it should result in pods with less priority to be evicted from the node to make room.  I can understand if you don't want to accept that impact to the workload though.
You can self-tune things a bit by adjusting the instance type sizes that you want and disable consolidation, but you also lose a lot of the efficiency gains that Karpenter offers when doing that.

authors: bwagner5 jonathan-innis kayahk txjjjjj

repo: aws/karpenter


text:
Unable to launch PartiQL/JSON/YAML server after certain upgrade

Describe the bug
PartiQL / JSON / YAML server are not able to launch after #328 and #326.
In #328, some renaming there got a bit missed up in partiql and in JSON/YAML. It seems to be "LSP_SERVER": "${workspaceFolder}/app/aws-lsp-partiql-runtimes/build/aws-lsp-partiql-binary.js" for PartiQL server and "LSP_SERVER": "${workspaceFolder}/app/aws-lsp-yaml-runtimes/build/aws-lsp-yaml-standalone.js" instead.
Then after the change of #326, these three servers just can't be launched via run and debug.

To reproduce
Steps to reproduce the behavior:

Check out to head 9226fb4ed10dc54f1719b14a5b1dac1807641f79 (#326).
Go to file .vscode/launch.json line 60.
Change the line to "LSP_SERVER": "${workspaceFolder}/app/aws-lsp-partiql-runtimes/build/aws-lsp-partiql-binary.js".
Run npm installand npm run package in the terminal.
Go to RUN AND DEBUG mode, switch to PartiQL Server and click the green RUN button.
AWS Documents Language Server can't be launched.

Expected behavior

Screenshots for Errors

Your Environment

OS: macOS Sonoma Version 14.5

Thanks for submitting the issue.
The fix (https://github.com/aws/language-servers/pull/376) has been merged to main. Please check if all is working well for you now

authors: XuechunHHH rahmaniaam

repo: aws/language-servers


text:
fork/exec /var/task/main: permission denied: PathError  on ./3-invoke.sh

Hi there,
I am consistently getting the above error when running ./3-invoke.sh
I have checked the AWS Lambda console and the function is there.  If I paste the event json into the test feature then I can replicate the same error message.
Any ideas?

I dived into the labyrinth of AWS docs and eventually discovered that the Lambda/Go combination doesn't work if you use a Windows10 PC !!!  Strongly suggest this is made more prominent as it is a huge omission. https://aws.amazon.com/premiumsupport/knowledge-center/lambda-deployment-package-errors/

repo: awsdocs/aws-lambda-developer-guide


text:
amazon-ebs: ctr: failed to resolve reference "602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/pause:3.5"

What happened:
Failed to pause
What you expected to happen:
to create ami
How to reproduce it (as minimally and precisely as possible):
make k8s=1.31 arch=arm64 aws_region=eu-north-1 os_distro=al2023
Environment:

AWS Region: eu-north-1
Instance Type(s): m6g.large
Cluster Kubernetes version: 1.31
Node Kubernetes version: 1.31
AMI Version:

Looks like it is fixed by changing 602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/pause:3.5 to public.ecr.aws/eks-distro/kubernetes/pause:v1.31.2-eks-1-31-latest in variables-default.json in templates/al2023/variables-default.json

This is expected behavior now on AL2023 builds. Please see https://github.com/awslabs/amazon-eks-ami/blob/main/doc/usage/al2023.md#pause-container-image for details and suggested image URIs.
The image you ought to be using needs the right region: 602401143452.dkr.ecr.eu-north-1.amazonaws.com

repo: awslabs/amazon-eks-ami


text:
EFS Supporting

What would you like to be added:
Support for EFS. Can be installed by "yum -y install amazon-efs-utils"
Why is this needed:
EFS doesn't work on EKS Managed Node Groups, until you install this package. Such as we don't manage these AMI and nodes, it would be good to have such package inside AMI and on the nodes.

Hey @romanpanov1, efs-utils is included as part of installing the EFS CSI driver
https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/Dockerfile#L28

I faced with issues like that
https://github.com/kubernetes-sigs/aws-efs-csi-driver/issues/192
And it was resolved by installing amazon-efs-utils on nodes.
But after your answer, I investigated additionally and tried to use another version of EFS CSI driver release and it works now. Thank you.


text:
[CI] separate unittest in parallel nodes

Issue #, if available:
Description of changes:
Separate modular unittests into parallel jenkins nodes, to speed up the tests
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@zhreshold any idea why CI failed for only two of the unittest runs? It looks like some kind of transient error.

Job PR-773-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-773/3/index.html

@Innixma it's green now

@Innixma it's green now

Happy to merge this, but do you have any idea what occurred in the failed run? We'd ideally like to eliminate any CI instability.

authors: Innixma szha zhreshold

repo: awslabs/autogluon


text:
Autoscaling for Fargate services does not support new ECS ARN format

Auto scaling of a Fargate service fails, if the new ECS ARN format has already been activated.
The following snippet creates an auto scaling Fargate service:
export class AwsSummitDemoStack extends cdk.Stack {
  constructor(scope: cdk.App, id: string, props?: cdk.StackProps) {
    super(scope, id, props);

    const vpc = new ec2.VpcNetwork(this, 'MyVpc', { maxAZs: 3 });

    const cluster = new ecs.Cluster(this, 'MyCluster', {
      vpc: vpc
    });

    const demo = new ecs.LoadBalancedFargateService(this, 'MyFargateService', {
      cluster: cluster,
      image: ecs.ContainerImage.fromDockerHub('amazon/amazon-ecs-sample'),
    });

    const scaling = demo.service.autoScaleTaskCount({ maxCapacity: 10 });
    scaling.scaleOnCpuUtilization('CpuScaling', {
      targetUtilizationPercent: 50
    });
  }
}

When the account (or user) already opted in to the new ECS ARN format, the Fargate service can be created, but autoscaling fails, as it generates the wrong service name:
MyFargateService/Service/TaskCount/Target (MyFargateServiceTaskCountTargetFD19DCA5) ECS service doesn't exist: service/AwsSummitDemoStack-MyCluster4C1BA579-UUFVS0WJMFMG/AwsSummitDemoStack-MyCluster4C1BA579-UUFVS0WJMFMG (Service: AWSApplicationAutoScaling; Status Code: 400; Error Code: ValidationException; Request ID: ...)

Hi, we turned on the new ECS ARN format today and it has broken a number of our stacks. It would be great to see this fixed.

Hi @pgarbe,
Apologies about the delay in getting back to you. Was the error generated when you ran cdk deploy? I assume you opted into the new ECS ARN format as root user?

Hi @SoManyHs, after a bit of investigation this is actually a CloudFormation bug https://forums.aws.amazon.com/thread.jspa?threadID=294793 I’m not sure there is a work around that will work for both formats? Given the CloudFormation issue has been open for a while some extra voices may encourage a faster fix.

@matthewtapper Thanks for that info. I am still curious about the steps you took. I was unable to reproduce this bug using the stack in our integ test, so curious what I'm missing.

@SoManyHs we enabled the new ECS ARN format in order to add some cost allocation tags to ecs. This was done as follows:
aws ecs put-account-setting-default --name serviceLongArnFormat --value enabled
aws ecs put-account-setting-default --name taskLongArnFormat --value enabled
aws ecs put-account-setting-default --name containerInstanceLongArnFormat --value enabled

With the above setting enabled a valid CloudFormation is generated by cdk however the below portion of the stack fails as the Fn::GetAtt returns a cluster name as apposed to the service name
Fn::Join:
          - ""
          - - service/notifications-cluster/
            - Fn::GetAtt:
                - notificationsservicewebService8520C0F2
                - Name

+1.  I've also seen this consistently since enabling the new ARN format. I'm pretty sure that integ test will start failing as soon as the new format is enabled on the CDK integ account.

authors: PaulMaddox SoManyHs matthewtapper pgarbe

repo: awslabs/aws-cdk


text:
fix: reference documentation is missing + bump to v0.24.1

There was a missing newline in the reference.rst.template file
which caused the toc not to include the module docs.

Pull Request Checklist

[ ] Testing

Unit test added
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[ ] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated

[ ] Title and Description

Change type: title prefixed with fix, feat will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[ ] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

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

Don't see the version bump in here btw.

So don't merge just yet :)

Yes, I am waiting for it to build. No wowries.


text:
Reuse s3 client across threads for s3 range requests

Issue #: N/A
Description of changes:
Boto3 sessions, upon creation, scan the file system to load service definitions and cache them per instance of the session. Sessions are not thread-safe so it is recommended to create a session per thread. With lots of threads, this is causing the threads to spend significant portion of time reading service definitions, especially over NFS.
Clients, however, are thread-safe. In some cases, it is possible to reuse the clients in multiple threads, and avoid loading service definitions. I will use this PR to address them, starting with S3 range requests.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-sDRE8Pq0duHT
Commit ID: ed023d5ef537076242515c22b47aaacd662b1bac
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

authors: jaidisido kukushking

repo: awslabs/aws-data-wrangler


text:
Error "can't find valid container" that is ocasionally when trying to access dashboards

Describe the bug
A customer raised this issue when accessing its dashboard. Sometimes, an error message appear "can't find valid container".
How to Reproduce
Create some dashboards in data.all, and see if the error appears.
Expected behavior
No error message should be raised.
Your project
No response
Screenshots
No response
OS
Llinux
Python version
3.10
AWS data.all version
1.0.0
Additional context
No response

Hi @mvidhu can you provide more info? In which UI view does it appear?
Do you have any screenshots?
Let's see if we can solve it

Hi @mvidhu can you provide more info? In which UI view does it appear? Do you have any screenshots?
Let's see if we can solve it

We see the error in dashboard UI. Dashboard List View. I will ask user to provide screenshot.I don't get the error when I access.

Hi @mvidhu can you provide more info? In which UI view does it appear? Do you have any screenshots?
Let's see if we can solve it

We see the error in dashboard UI. Dashboard List View. I will ask user to provide screenshot.I don't get the error when I access.

I was also able to reproduce the error, although it appears in the console it does not seem to affect the functionality

authors: dlpzx louishourcade mvidhu

repo: awslabs/aws-dataall


text:
[request]: aws-config: Allow to set load_timeout when constructing with DefaultCredentialsChain

A note for the community

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 "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

Tell us about your request
Provide a way to set load_timeout on LazyCachingCredentialsProvider when constructing with DefaultCredentialsChain. Right now I don't see a way to override it without reimplementing DefaultCredentialsChain.
Tell us about the problem you're trying to solve.
I was getting Error: failed to construct request: Failed to load credentials from the credentials provider: Credentials provider timed out after 5 seconds when trying to get secret from aws_sdk_secretsmanager::Client.
Are you currently working around this issue?
I had to use WebIdentityTokenCredentialsProvider directly, which is not recommended AFAIK.
Additional context
aws-config = "0.6.0"
aws-sdk-secretsmanager = "0.6.0"
aws-types = "0.6.0"

This code was causing the issue.
let config = aws_config::from_env().load().await;
let client = Client::new(config);
let response = client.get_secret_value().secret_id("secret").send().await?;

Had to change into this
let provider = WebIdentityTokenCredentialsProvider::builder()
        .configure(&ProviderConfig::with_default_region().await)
        .build();
let config = aws_config::from_env()
        .credentials_provider(provider)
        .load()
        .await;
let client = Client::new(config);
let response = client.get_secret_value().secret_id("secret").send().await?;

Thanks for bringing this to our attention!
As of v0.8.0, it is now possible to set the load timeout (among other things) on the default credential chain. For example:
let default_provider = DefaultCredentialsChain::builder()
    .load_timeout(Duration::from_secs(20))
    .build();
let config = aws_config::from_env()
    .credentials_provider(default_provider)
    .load()
    .await;
let client = Client::new(config);

authors: jdisanti yerke

repo: awslabs/aws-sdk-rust


text:
Refresh Token Support

What would you like to be added:
Unless I am missing something it looks like the refresh token is saved as a cookie but not used to refresh the access token after it expires. Using defaults, this means re-logging in once every 60 minutes.
Why is this needed:
So that authorization can survive beyond the expiration limit of the access token.

Hi Cameron,
Thanks you for creating this issue. You're not missing anything, the Cognito@Edge package currently does not support the use of refresh tokens. That's would definitely be in scope for the package though, so we'd accept a PR to add this functionality or we (the maintainers) may work on it in the future.
Cheers,
Jean

I already forked the project and have some initial work done. It will probably be a month or so before I can get back to it though. Hopefully I'll have something good to contribute before too much time passes.

@cameroncf would you be able to share your approach to implementing this? Happy to help out if there is a well-lit path

Could a maintainer (@jeandek) take a look at #51 and see if it's ready to merge? This functionality is pretty important and @maverick089 went through the effort of submitting a PR for it.

Hi @DanielLaberge ,
Sorry for the lack of communication on this. Unfortunately, we haven't had the bandwidth required to review and test this PR, and will likely not have it until at least a couple of weeks. We will definitely do so as soon as we can though.
Regards,
Jean

authors: DanielLaberge cameroncf eddie-atkinson jeandek

repo: awslabs/cognito-at-edge


text:
Sqoop does not like . followed by number, changing auto-generated buc…

…ket name to have hypens instead

Closing in favor of more recent PR

authors: dpl-dev-austin stmcpherson

repo: awslabs/data-pipeline-samples


text:
Agent: mypy problems in 0.1.148 version

Describe the bug
Hey, thanks for this project, this is helping a lot to create examples of how to work with Bedrock Agents using CDK.
I'm trying to update from 0.1.146 to 0.1.148 and getting this error with mypy:
poetry run mypy --pretty aws_lambda_powertools examples
examples/event_handler_bedrock_agents/cdk/bedrock_agent_stack.py: note: In member "__init__" of class "AgentsCdkStack":
examples/event_handler_bedrock_agents/cdk/bedrock_agent_stack.py:34:9: error:
Unexpected keyword argument "action_group_name" for "add_action_group" of
"Agent"; did you mean "action_group"?  [call-arg]
            agent.add_action_group(
            ^
/home/runner/.cache/pypoetry/virtualenvs/aws-lambda-powertools-2Yi3cwHL-py3.11/lib/python3.11/site-packages/cdklabs/generative_ai_cdk_constructs/bedrock/__init__.py:751:5: note: "add_action_group" of "Agent" defined here
examples/event_handler_bedrock_agents/cdk/bedrock_agent_stack.py:34:9: error:
Unexpected keyword argument "description" for "add_action_group" of "Agent"
[call-arg]
            agent.add_action_group(
            ^
/home/runner/.cache/pypoetry/virtualenvs/aws-lambda-powertools-2Yi3cwHL-py3.11/lib/python3.11/site-packages/cdklabs/generative_ai_cdk_constructs/bedrock/__init__.py:751:5: note: "add_action_group" of "Agent" defined here
examples/event_handler_bedrock_agents/cdk/bedrock_agent_stack.py:34:9: error:
Unexpected keyword argument "action_group_executor" for "add_action_group" of
"Agent"  [call-arg]
            agent.add_action_group(
            ^
/home/runner/.cache/pypoetry/virtualenvs/aws-lambda-powertools-2Yi3cwHL-py3.11/lib/python3.11/site-packages/cdklabs/generative_ai_cdk_constructs/bedrock/__init__.py:751:5: note: "add_action_group" of "Agent" defined here
examples/event_handler_bedrock_agents/cdk/bedrock_agent_stack.py:34:9: error:
Unexpected keyword argument "action_group_state" for "add_action_group" of
"Agent"; did you mean "action_group"?  [call-arg]
            agent.add_action_group(
            ^
/home/runner/.cache/pypoetry/virtualenvs/aws-lambda-powertools-2Yi3cwHL-py3.11/lib/python3.11/site-packages/cdklabs/generative_ai_cdk_constructs/bedrock/__init__.py:751:5: note: "add_action_group" of "Agent" defined here
examples/event_handler_bedrock_agents/cdk/bedrock_agent_stack.py:34:9: error:
Unexpected keyword argument "api_schema" for "add_action_group" of "Agent"
[call-arg]
            agent.add_action_group(
            ^
/home/runner/.cache/pypoetry/virtualenvs/aws-lambda-powertools-2Yi3cwHL-py3.11/lib/python3.11/site-packages/cdklabs/generative_ai_cdk_constructs/bedrock/__init__.py:751:5: note: "add_action_group" of "Agent" defined here

To make debugging easier, here is the code:
from aws_cdk import (
    Stack,
)
from aws_cdk.aws_lambda import Runtime
from aws_cdk.aws_lambda_python_alpha import PythonFunction
from cdklabs.generative_ai_cdk_constructs.bedrock import (
    Agent,
    ApiSchema,
    BedrockFoundationModel,
)
from constructs import Construct

class AgentsCdkStack(Stack):

    def __init__(self, scope: Construct, construct_id: str, **kwargs) -> None:
        super().__init__(scope, construct_id, **kwargs)

        action_group_function = PythonFunction(
            self,
            "LambdaFunction",
            runtime=Runtime.PYTHON_3_12,
            entry="./lambda",  # (1)!
            index="app.py",
            handler="lambda_handler",
        )

        agent = Agent(
            self,
            "Agent",
            foundation_model=BedrockFoundationModel.ANTHROPIC_CLAUDE_INSTANT_V1_2,
            instruction="You are a helpful and friendly agent that answers questions about insurance claims.",
        )
        agent.add_action_group(  # type: ignore[call-arg]
            action_group_name="InsureClaimsSupport",
            description="Use these functions for insurance claims support",
            action_group_executor=action_group_function,
            action_group_state="ENABLED",
            api_schema=ApiSchema.from_asset("./lambda/openapi.json"),  # (2)!
        )

Expected Behavior
May it work as in version 0.1.146.
Current Behavior
Mypy errors.
Reproduction Steps
1 - Create a venv
2 - Install mypy and cdklabs.generative-ai-cdk-constructs
3 - Create a stack with the code I sent
4 - Run mypy --pretty DIRECTORY/FILE
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
aws-cdk-lib (2.141.0)
Framework Version
No response
Node.js Version
I'm not deploying the code, so, I don't have nodejs installed
OS
Linux
Language
Python
Language Version
No response
Region experiencing the issue
I'm not deploying the code
Code modification
I don't know
Other information
No response
Service quota

[X] I have reviewed the service quotas for this construct

Hi @leandrodamascena ! Thank you for reporting this. There were indeed some changes in the latest version as we migrated from custom resources to use the official L1 bedrock constructs under the hood. You can have a look at the code snippets in the bedrock readme or this PR in the samples: https://github.com/aws-samples/generative-ai-cdk-constructs-samples/pull/59 which provides updated samples with the latest version.
Closing this issue, please let us know if you need any additional information ! Thank you !

authors: krokoko leandrodamascena

repo: awslabs/generative-ai-cdk-constructs


text:
get_model_summary

Description
I would like to print my model summary (keras style) or access the network and take a look at layers, weights, collect_params, and number of parameters.
It would be nice to add a get_network_summary or an immutable network object returned by the estimator.

Hi @cyrusmvahid
The example examples/evaluate_model.py can be adapted as follow:
train_transformation, train_model = estimator.train_model(dataset.train)
print(train_model.collect_params())

This will give you access to network weights if you want to investigate weights.
For printing model summary, we could do something but the print will be dependent on whether the network is hybridized or not.
E.g., we could add in the trainer code something like this that may do the trick:
...
loss.backward()
trainer.step(batch_size)

first_batch = batch_no == 1 and epoch_no == 0

if not self.hybridize and first_batch:
    net.summary(*inputs)

authors: cyrusmvahid geoalgo

repo: awslabs/gluon-ts


text:
Refactor Dataloading and Dataset

Issue #, if available:
#755
#756
Description of changes:
Change the Dataloader API and Dataset API according to #755 and #756.
Update the unit tests accordingly
Update the training and inference codes accordingly.
TODO: Update examples
TODO: Update docs.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

One major concern of the new GSgnnData is about how it provides the metadata to avoid conflicts with the given arguments, e.g., node_feat_field and edge_feat_field.
For example, if users want to extract all node feature fields of a graph data, will the data.node_feat_field() method return a dictionary of all nodes with feature fields? The current implementation will return "None" is not set this argument in the constructor, or the given values. This may cause confusion.
So can we have a set of dedicate methods in the GSgnnData to return the metadata of a graph dataset, e.g., get_all_node_feat_fields(), get_all_edge_feat_fields(), and etc.

One major concern of the new GSgnnData is about how it provides the metadata to avoid conflicts with the given arguments, e.g., node_feat_field and edge_feat_field.
For example, if users want to extract all node feature fields of a graph data, will the data.node_feat_field() method return a dictionary of all nodes with feature fields? The current implementation will return "None" is not set this argument in the constructor, or the given values. This may cause confusion.
So can we have a set of dedicate methods in the GSgnnData to return the metadata of a graph dataset, e.g., get_all_node_feat_fields(), get_all_edge_feat_fields(), and etc.

Even with get_all_node_feat_fields and get_all_edge_feat_fields does not solve the problem. The key problem is because data.node_feat_field is from the argument node_feat_field.

One major concern of the new GSgnnData is about how it provides the metadata to avoid conflicts with the given arguments, e.g., node_feat_field and edge_feat_field.
For example, if users want to extract all node feature fields of a graph data, will the data.node_feat_field() method return a dictionary of all nodes with feature fields? The current implementation will return "None" is not set this argument in the constructor, or the given values. This may cause confusion.
So can we have a set of dedicate methods in the GSgnnData to return the metadata of a graph dataset, e.g., get_all_node_feat_fields(), get_all_edge_feat_fields(), and etc.

Even with get_all_node_feat_fields and get_all_edge_feat_fields does not solve the problem. The key problem is because data.node_feat_field is from the argument node_feat_field.

As we discuss, we need to have a get_graph_metadata() method to return all information of a given graph.

repo: awslabs/graphstorm


text:
Build KTF without using host system's libc headers

Fixes #89
Make necessary changes so that we can compile KTF without accidentally pulling in the build system's type definitions.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Testing:
make clean
make
make boot
succeed as before.

repo: awslabs/ktf


text:
development/v1.10.2 rc.1

fix(asea): fix iam role trust logic
fix(asea): fix depends on for ssm parameters
fix(asea): fix asea hosted zones
fix(asea):  Prevent adding asea managed sg rules from being added to LZA stack
fix(uninstaller): correct syntax for debug log

Superseded by :

https://github.com/awslabs/landing-zone-accelerator-on-aws/pull/672

repo: awslabs/landing-zone-accelerator-on-aws


text:
clang-format and sample run of reformat.sh

Description of changes:
An example run of clang-format, using the C ESDK config.
Style might need some rework.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request head (clang_format@33f5764). Click here to learn what that means.
The diff coverage is n/a.

I had tried using the very simple clang-format
---
BasedOnStyle: WebKit
AlignConsecutiveAssignments: true
AlignTrailingComments: true
PointerAlignment: Right
---

And it gave results that were pretty close to what s2n already had.

Anywhere the code looks ugly, we can just add /* clang-format off */

refactoring without applying the style to all code.

authors: codecov-io danielsn dougch


text:
fix: Update go mod to fix CVE-2024-45338

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

@coderbirju you forgot to do a go mod tidy in cmd/

authors: austinvazquez coderbirju

repo: awslabs/soci-snapshotter


text:
Bulk actions

Bulk insert
Bulk update
Bulk delete

This issue will be reopened if requested in the future.

repo: axe-api/axe-api


text:
Reanimated 2 example

Hi, thanks for working on this library. I was trying to make it work on with Reanimated 2 but I failed.
const [num, setNum] = useState(0);

  const text = useSharedValue(num);

  const animatedText = useDerivedValue(() => `Hello ${text.value}`);
  const animatedProps = useAnimatedProps(() => {
    return {
      text: animatedText.value,
    };
  });

return (
    <Animated.View style={[styles.container, style]}>
      <Touchable onPress={() => setNum(10)} rippleColor={colors.green[700]}>
        <ContentContainer>
          <ButtonIcon name="plus" />
          <AnimateableText
            animatedProps={animatedProps}
            // same other props as Text component
          />
        </ContentContainer>
      </Touchable>
    </Animated.View>
  );

Anything I'm missing. When pressing the touchable the text does not change.

@radko93 were you able to fix this? The onPress is not triggered for me as well

repo: axelra-ag/react-native-animateable-text


text:
JobSystem creates too many threads

JobSystem creates way too many threads. For example, on a Samsung S10e phone with 8 core CPU it creates 12 threads. On a high load these threads will be stomping on each other and on the main game thread. It should create at most hardware threads - 1 threads and leave one core free for the main thread. Though, on mobile devices it probably should be - 2 to leave one more core free for the OS and background processes, since resources there are more tight than on desktop PCs.
Also, an interesting thing to note, is that on the same Samsung S10e, other systems (like Android's Java and GPU driver) create only 4 worker threads for each system (there are 4 "Runtime worker", 4 "Binder", 4 "mali-utility-wo" threads). But it's difficult to say if they have 4 hardcoded, or if it's 8 cores / 2, or because this CPU has 4 high performance cores.

it's configurable: https://github.com/axmolengine/axmol/blob/dev/core/base/Director.cpp#L119

Maybe same with emscripten: clamp(hardware_concurrency(), 2, 8) ?

Yeah, emscripten also should be at least -1.

repo: axmolengine/axmol


text:
How to manage bpf map only via aya

Hi team,
Newbie for aya here. I'd like to manage bpf map only without any bpf program attached. I tried the code below:
    // init bpf object without any actual bpf program
    let bpf = aya::Bpf::load(&[])?;
    // init map
    let mut array = Array::try_from(bpf.map_mut("ARRAY").unwrap())?;
    array.set(1, 42, 0)?;
    assert_eq!(array.get(&1, 0)?, 42);
    println!("map done");

But I got errors below:
Error: error parsing BPF object

Caused by:
    0: error parsing ELF data
    1: Could not read file magic

The error message does make sense, but I wanna init bpf map without any bpf program. Any ideas?

Does your map already exist and was your eBPF program with its definition loaded by sometthing else?
If not, I think you are asking for the impossible. To create maps, you need to load an eBPF object with their definitions.
If yes, that would be definitely possible (I mean - interacting with an already existing map), but we don't support that in Aya. For now, Aya allows you to interact with maps which are defined in the ELF object you load.

@vadorovsky thx for reply. It looks like I have misunderstood the process of bpf map creation. I will load an eBPF object to do  so. Thank you very much :).

authors: nevermosby vadorovsky

repo: aya-rs/aya


text:
integration-test: Use veth pair instead of lo

Fixes #422. I split the initial codegen commit out to #919 to clean this PR up.
I would like some help debugging the last 4 test failures:
---- tests::smoke::list_loaded_maps stdout ----
Entered network namespace aya-test-404672-4
thread 'tests::smoke::list_loaded_maps' panicked at test/integration-test/src/tests/smoke.rs:117:23:
called `Result::unwrap()` on an `Err` value: LoadError { io_error: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }, verifier_log:  }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Exited network namespace aya-test-404672-4

---- tests::smoke::list_loaded_programs stdout ----
Entered network namespace aya-test-404672-5
thread 'tests::smoke::list_loaded_programs' panicked at test/integration-test/src/tests/smoke.rs:84:23:
called `Result::unwrap()` on an `Err` value: LoadError { io_error: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }, verifier_log:  }
Exited network namespace aya-test-404672-5

---- tests::xdp::af_xdp stdout ----
Entered network namespace aya-test-404672-6
thread 'tests::xdp::af_xdp' panicked at test/integration-test/src/tests/xdp.rs:57:22:
called `Result::unwrap()` on an `Err` value: Errno(19: No such device)
Exited network namespace aya-test-404672-6

---- tests::xdp::cpumap_chain stdout ----
Entered network namespace aya-test-404672-7
thread 'tests::xdp::cpumap_chain' panicked at test/integration-test/src/tests/xdp.rs:182:5:
assertion `left == right` failed
  left: 0
 right: 1
Exited network namespace aya-test-404672-7

I'm not sure if introducing the network namespace caused behavior to now be different.

Additionally you consider using dummy interfaces here rather than veth pairs? (as mentioned in #422) ?

@astoycos I saw a comment in #561 suggesting veth pairs instead of dummies so that's why I went with this approach. I'll look into why the macOS VM tests are failing.

Ack just read that, sounds good thanks!

@astoycos I'm having trouble debugging the exact issue as I'm unable to get the QEMU setup working locally, so have been (slowly) trying to debug while pushing changes to CI.
My current hypothesis is that since the integration tests run as the /init process on initramfs, perhaps some veth module is not yet loaded which causes creation to fail. I ran the equivalent ip link command to try to create a veth and ran into similar issues. It's also possible that veth creation relies on something on the filesystem that it can't access for some reason during the /init script.

authors: astoycos kevinji


text:
how to make an annotation for list of custom types?

I can not understand how to make a proper workable annotation for list of custom types, I have tried
// @type CustomType
CustomType = {}
CustomType.columns = []
// @param {CustomType[]} tables
// @param {list<CustomType>} tables
// @param {[]CustomType} tables

tables[0].co // <- here, IDE do not give me any  auto-completion

Am I doing something wrong ot there is no such feature?

Unfortunately you cannot define lists with types. It's the same with objects. That's something which I may add in the future.
Anyway I recommend to do the following instead:
// @type OtherCustomType
// @property {string} foo
// @property {number} test
OtherCustomType = {}

// @type CustomType
CustomType = {}
CustomType.columns = []

// @param {number}
// @return {CustomType|OtherCustomType}
CustomType.getColumnsItem = function(idx)
	return self.columns[idx]
end function

item = CustomType.getColumnsItem(2) // <- will return CustomType or OtherCustomType

item.test // <-- shows number

I see, okay I will consider it. Thank you for the answer :)

authors: AmsTaFFix ayecue

repo: ayecue/greybel-vs


text:
[BUG] Memory leak can occur during interactive UI test

Describe the bug
Memory leak occurred during interactive UI test for game_board
To Reproduce
Unsure about how to reproduce; will report again later
Expected behavior
No memory leaks
Screenshots

Leak occurred after selecting the '2' at row 1, column 5
Screenshotted from the VSCode terminal.

Leaving a note here that this bug may have similar problem roots to this issue

Update: error occurs due to stack overflow -- will need to fix the recursive function in select()

I think this bug is fixed with https://github.com/ayoshi007/cpp-minesweeper/commit/0d886313998cfa9b0b3fd58fb9b0d917db3cbd78, will test locally later

The bug seems to be fixed, closing


text:
Which rockpro64 LXDE/other image does have sound output.

Hi, I am using rockpro64. And flashed Ubuntu18 LXDE Desktop image (build - 0.8.3-11.41)with pine-installer. Here i am able to hear sound from audio jack. But it seems 32 bit image and i am having trouble installing ComputeLibrary and other projects. So can you please verify which LXDE 64 bit ubuntu image does have sound output support for rockpro64?
I have used "bionic lxde-rockpro64-0.8.0rc16-1136-arm64.img". But no sound is there.
Thanks.

Change sound output.
On Wed, 10 Jul 2019 at 07:20, rahulsharma11 notifications@github.com
wrote:

Hi, I am using rockpro64. And flashed Ubuntu18 LXDE Desktop image (build -
0.8.3-11.41)with pine-installer. Here i am able to hear sound from audio
jack. But it seems 32 bit image and i am having trouble installing
ComputeLibrary and other projects. So can you please verify which LXDE 64
bit ubuntu image does have sound output support for rockpro64?
I have used "bionic lxde-rockpro64-0.8.0rc16-1136-arm64.img". But no sound
is there.
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ayufan-rock64/linux-build/issues/380?email_source=notifications&email_token=AASOSQPMVF7L35UVDGZTMVTP6VWRNA5CNFSM4H7LRPKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G6IGHAQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASOSQLWB5MRNULBUZ3P3ETP6VWRNANCNFSM4H7LRPKA
.

Got this.
Thanks.


text:
API Directive/Exception Handler to return 4xx status codes

Currently, post requests which fail due to a database exception cause the API to return a 500 error.  This includes errors such as unique key constraints when creating a new user.  This middleware should cause the API to return a 400 error with an appropriate message, while letting other errors pass through to cause a 500.

This is an overview of all the instances where we are returning InternalServerError in the app and their current justification:

Authentication.scala:47: Error when creating a new entry in users or user_to_organizations. I'm actually not sure why we are automatically creating a new entry in the users table when checking for authentication: that seems like it should be a more deliberate action than such an automated one.
Authentication.scala:71: Legitimate error when the default account is not found.
bucket/Routes.scala:53: Legitimate error when inserting a new bucket. It can't be a duplicate because we give the new bucket a fresh UUID.
bucket/Routes.scala:89: Legitimate error when deleting a bucket, and it was neither found nor not found.
bucket/Routes.scala:120: Legitimate error when deleting scene from bucket, and it is was neither found nor not found.
images/Routes.scala:51: Legitimate error when creating a new image that cannot be duplication.
images/Routes.scala:94: Legitimate error when deleting an image that was neither found nor not found.
organization/Routs.scala:101: Error when updating more than one rows at a time. This seems a little odd: on one hand in the "Success" case we are returning no data, whereas RESTful design would prefer returning the entire resource. On the other hand, this should never happen: there should be UNIQUE constraints on the tables that prevent duplication of IDs, and since this endpoint takes IDs the result should always be a single row.
organization/Routes.scala:112: Legitimate error when removing a user from an organization, and it is neither found nor not found.
scene/Routes.scala:44: Legitimate error when inserting a new scene that cannot be duplication.
scene/Routes.scala:80: Legitimate error when deleting a scene and it is neither found nor not found.
thumbnail/Routes.scala:63: Legitimate error when inserting new thumbnail that cannot be duplication.
thumbnail/Routes.scala:75: Legitimate error when deleting a thumbnail and it is neither found nor not found.
user/Routes.scala:41: Error when unable to retrieve immediately created user from the user_to_organizations table.
user/Routes.scala:43: Error when unable to create a user in the database, maybe due to duplication.

Of these, 1 and 15 seem suspicious. Also maybe 14. There's some suspicious shadowing of user in user/Routes.scala which may be hurting matters. Another thing I noticed was that in some cases we throw an exception, and in others we return an InternalServerError. I imagine that a 500 would be returned even in cases of exception, so wouldn't it be preferable to always throw the exception rather than swallow it?

We've refactored error handling a bit - I don't think this is relevant, if there are specific problems we can reopen or create new issues

authors: Lknechtli notthatbreezy rajadain

repo: azavea/raster-foundry


text:
React (nested) code splitting and SASS results in component not loaded

I've got a strange problem using sass and code splitting, probably with nesting only.
What happened is, my imported component (using loadable) did not load in production build. I din't get any kind of error or indication what's wrong.
Structure is as follows:

When I import the sass file person-list.scss in PersonList.tsx it requires me to import a (dummy) sass file in PersonsRoot.tsx too, otherwise the component PersonsList will not get loaded.
This is what I use in my project: create-react-app (react-scripts-ts), react-router 4, redux 4, react-app-rewired, react-app-rewire-scss
Here I uploaded a project to github for easy reproduction:
Am I doing something wrong or is it maybe a bug?
I'have also posted this issue on stackoverflow
Update:
Webpack seems to have an array of 545 modules but tries to access the element with index 545 which is of course undefined (0 based index).

TypeError: Cannot read property 'call' of undefined
o (main.9cac5c4f.js:formatted:26)
544 (persons-list.scss:1)
o (main.9cac5c4f.js:formatted:26)
543 (persons-list.scss?3174:4)
o (main.9cac5c4f.js:formatted:26)
542 (1.56e5fc78.chunk.js:1)
o (main.9cac5c4f.js:formatted:26)
Promise.then (async)
loader (routes.ts:6)
f (main.9cac5c4f.js:formatted:6499)
v (main.9cac5c4f.js:formatted:6566)
n (main.9cac5c4f.js:formatted:6591)
Ii (main.9cac5c4f.js:formatted:11110)
da (main.9cac5c4f.js:formatted:11833)
ha (main.9cac5c4f.js:formatted:11854)
Ga (main.9cac5c4f.js:formatted:12109)
Ya (main.9cac5c4f.js:formatted:12068)
Ha (main.9cac5c4f.js:formatted:12056)
za (main.9cac5c4f.js:formatted:12011)
ba (main.9cac5c4f.js:formatted:11941)
enqueueSetState (main.9cac5c4f.js:formatted:10547)
O.setState (main.9cac5c4f.js:formatted:7392)
t (main.9cac5c4f.js:formatted:6630)
(anonymous) (main.9cac5c4f.js:formatted:6638)
Promise.then (async)
n._loadModule (main.9cac5c4f.js:formatted:6637)
n.componentWillMount (main.9cac5c4f.js:formatted:6608)
li (main.9cac5c4f.js:formatted:10594)
Ii (main.9cac5c4f.js:formatted:11117)
da (main.9cac5c4f.js:formatted:11833)
ha (main.9cac5c4f.js:formatted:11854)
Ga (main.9cac5c4f.js:formatted:12109)
Ya (main.9cac5c4f.js:formatted:12068)
Ha (main.9cac5c4f.js:formatted:12056)
za (main.9cac5c4f.js:formatted:12011)
ba (main.9cac5c4f.js:formatted:11941)
ou (main.9cac5c4f.js:formatted:12498)
au (main.9cac5c4f.js:formatted:12508)
hu.render (main.9cac5c4f.js:formatted:12705)
(anonymous) (main.9cac5c4f.js:formatted:12599)
eu (main.9cac5c4f.js:formatted:12435)
vu (main.9cac5c4f.js:formatted:12598)
render (main.9cac5c4f.js:formatted:12755)
(anonymous) (main.9cac5c4f.js:formatted:7334)
o (main.9cac5c4f.js:formatted:26)
(anonymous) (main.9cac5c4f.js:formatted:6753)
o (main.9cac5c4f.js:formatted:26)
(anonymous) (main.9cac5c4f.js:formatted:100)
(anonymous) (main.9cac5c4f.js:formatted:101)

guess this is related https://github.com/webpack/webpack/issues/7499
Could be a problem with sideEffects of webpack treeshaking...

and https://github.com/webpack/webpack/issues/7425

@aze3ma
Did you have any chance to look into this?

@martinoss
Unfortunately there is no plan/time to maintain react-app-rewired:
https://github.com/timarney/react-app-rewired/issues/162#issuecomment-417872507

Guess it's caused by create-react-app-typescript/react-scripts-ts
https://github.com/wmonk/create-react-app-typescript/issues/390

authors: AndyOGo martinoss


text:
User Friendly Progress Output

User Friendly Progress Output
Progress Rendering
During command execution, to provide understandable output, we should have:

Progress bars
Elapsed time
Estimated time remaining
Enough information -- not too little, not too much.
Color/Colour indicating importance of information, as well as status (queued/pending, success, in progress, failure, error)

Progress Data Model
Because peace is intended to support:

interactive command line
build logging
machine readable output
web request output

Then:

The progress information needs to be serializable.
It should contain enough information to be rendered.
On a web page, detail may be collapsible, so including more information may be okay to avoid additional round trip time.

Bonus
For a CLI process / web request that is executed separately to the process that is running the command execution, the progress information needs to be retrievable independently. So:

Progress information needs to be retrievable by a separate process -- perhaps written to / read from disk, or exposed on a well-known port.

Available Libraries
The libraries should ideally support async Rust with tokio, since that's what peace uses.

prodash: Good for CLI usage and build logging, and uses tokio.
indicatif: Good for CLI usage, spawns its own threads. This is used in choochoo / ops_ux.
zzz: Minimal progress bar, tokio ready.

Should consider:

Library agnostic progress types.

Allows us to serialize the progress output for web and native targets

Allows another process to read the progress of an existing running process.

indicatif spawns its own threads and writes to stdout/stderr or something TermLike.
Ideally we want something that:

Writes to W: AsyncWrite
Uses tokio's executor instead of spawning more threads.
Uses rich types for its unit of work, so that progress bars can be styled for the point of err.

Translatable progress messages, e.g. with fluent
Something to consider for error messages as well.


text:
🛑 Sakai Wolford Bot is down

In 9068440, Sakai Wolford Bot (https://sakaibot-discord.uzumekiulee.repl.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sakai Wolford Bot is back up in 244df31 after 15 minutes.

repo: azrielbsi/monitor


text:
CDC ECM packet pool drop

What target device are you using?
LPC55S69
Which version of Azure RTOS?
6.1
What toolchain and environment?
arm-none-eabi-* + WSL
Hi,
I am developping a embedded application on a MCU that runs Azure RTOS with the netxduo/usbx layers to manage TCP/IP sockets & packets.
This MCU communicates with a laptop through an Ethernet over USB protocol (USB CDC-ECM). The laptop runs Ubuntu and can open TCP ports through netcat command and send a various range of command.
Everything is running fine most of the time but we sometimes experience random problem where all the opened TCP ports get frozen.
Indeed, it is no longer possible to open sockets on these ports, or even to send commands on ports that have already been opened.
I was suspecting packet pool leak with NetX/UsbX so I've added a debug log trace on _nx_packet_allocate() and _nx_packet_release() to find out which thread is taking a packet from which packet pool and what are the number of packet left.
Thanks to this, I can see that, when the problem is happening, the "ux_slave_class_cdc_ecm_bulkout_thread" thread requests one packet per second without ever releasing it, as you can see on the screen attached. As soon as the packet pool drops to 0, my application is stuck (no TCP port available, everything seems to be frozen).
After several minutes (5/10/15?), all packets are released at once, but I can no longer communicate with the MCU. It's as if the USB link had been removed. I have to reboot my MCU to make it work again.
Such behavior is not acceptable, as it will not be possible to unplug/replug in the final product.
Do you have any idea of the cause and how to solve this bug?
Thanks in advance,
Best regards,
Antoine

teraterm3.log

ux_slave_class_cdc_ecm_bulkout_thread keeps polling CDC-ECM ethernet packets from USB bulkout endpoint, when there is packets received, they will be passed to NX to handle (and released in NX). From your description it seems there are real ethernet inputs from USB ethernet, but input packets are too many for NX to process and release in time. Maybe you can consider increasing the pool size to buffer more packets for processing.

Thanks for the answer.
It also happens in cases of low use (very few exchanges), and not necessarily in intensive use (curl downloads for 12 hours in a row, for example). It seems purely random.
We tried increasing the number of packets, but the problem remained the same, but a little later (time to empty the packet pool).
We're currently already at the ram limit...

On USB side, the packets are received and passed to upper layer (maybe application) and upper layer take the ownership to free them, so I think application may need optimization on ethernet packets handling, while we are checking if there is something could be done on USB side.
BTW, it seems CDC-ECM only recognized by linux. I'm not sure if you can share your way to make CDC-ECM recognized on windows for WSL so it's easier for us to reproduce the issue.

Thanks !
What do you have in mind when you say "application"? In NetX or in our application even higher up?
You can find attached a tutorial to use our application with WSL. It will probably help you.
CM connect-3-5.pdf

Thanks for sharing.
When I say "application", I mean your application or even higher up. The packets allocated and filled in USBX is passed to upper layers and the packets ownership is also passed to upper layers, they should process and free the packets in time.

A possible improvement for ethernet packets handling in USBX is, in ux_device_class_cdc_ecm_bulkout_thread.c, if no free packet is available, host bulk out transfers are NAKed currently. Such a blocking of host bulk out transfer may cause host behavior to reset the device (just a guess, from your observation of deactivate and activate again, it's host specific behavior), maybe you can try to allocate NX packet after USB bulk out transfer, if no packet free the packet is dropped by discarding the data. In this way the host is not resetting the device, but network packets are dropped until free packet available.
Note that the upper logic change does not help on packets handling and releasing, upper layers still need to be checked to find the real issue (why packets are not handled and released).

We've clearly understood that packet pool creation takes place in the application part. However, when all goes well (for a CURL via WIFI, for example), the entire packet release mechanism does not leave the NetX layer. At least, that's what the stack frame suggests...

Some packets are indeed released by the application layer, but not in very specific cases of important network exchange.

For TCP packets, some are indeed queued by TCP control block.

Incoming SYN packets for TCP server. The max counter is set while doing listening. Application should call accept to consume them.
Incoming data packets. Application should call receive to consume them.
Outgoing data packets. As long as the network is still alive, all the packets will be released in 1 second. If connection is dead, call disconnect to release them all.

authors: TiejunMS ZerAtaii xiaocq2001

repo: azure-rtos/usbx


text:
feat: Implement the TreeWalker API

Ref: https://developer.mozilla.org/en-US/docs/Web/API/TreeWalker

Yeah, it's on the list of things to implement when I get some time.

@b-fuze , I presume you didn't do https://developer.mozilla.org/en-US/docs/Web/API/NodeIterator ?
TreeWalker is the faster way to walk the DOM, NodeIterator only slightly slower
Traversing is SLOW
https://www.measurethat.net/Benchmarks/Show/5581/2/traverse-function-vs-nodeiterator-vs-treewalker#latest_results_block

@Danny-Engelman no, I didn't do either of them. But TreeWalker is on the plan to to do list.

https://github.com/b-fuze/deno-dom/pull/37

#37

This issue is blocking my integration of lit-html in a project.

repo: b-fuze/deno-dom