text:
Can not create new environment when adding New App (Host Web App)

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d34x9npy2tqygn
AWS Region
ca-central-1
Amplify Hosting feature
Backend environments
Frontend framework
Vue
Next.js version
Does not use Next
Next.js router
N/A
Describe the bug
I want to add a App and create a new backend environment which are not shared with other apps connected to the same branch.
In build settings I select create new environment and fill in name wcscanada both for app name and environment. Do not know why the pull down of App name does not reflect the app-name given (possible another bug).

Summary seems ok:

But the when I deploy it try to create an environment with the same name as the branch name (template).

One of the errors:

I my setup this does not work since I need to have separate environment per app.
Need also help to clean this up.
I tried first to deploy this app in another region where I also another app with this backend environment. However if I try to delete this app it will also delete the environment of the existing app. How do I delete an app and keep the environment?
See app id d38c3xshp5shlw  and d3h2imtpur0g0t  in region us-east-1
Expected behavior
Create app easy with separate environment so that database, Cognito and roles are unique.
Reproduction steps

Create new app - web hosted
Connect to git hub and a branch
Under build setting set Create new environment with a name other than the branch name
Should create this environment, but is does not. It use the branch name

Build Settings
No response
Log output

# Put your logs below this line

Additional information
No response

Hi @bergmorten 👋 , thanks for raising this and for providing detailed reproduction steps.
The behavior outlined in this issue seems related to #3745. Please refer to my comment here: https://github.com/aws-amplify/amplify-hosting/issues/3745#issuecomment-1754139394 which outlines a workaround to use the USER_BRANCH environment variable.
Closing this to keep all the communication in the same place. Please track #3745 for any further updates.

repo: aws-amplify/amplify-hosting


text:
Add EXISTS to concise rule as an Operator

Affects version
.49.2+
Description of issue
Feature request: add "EXISTS" an available operator for the concise rules in the TXT file. Example rule might look something like:
AWS::S3::Bucket BucketEncryption EXISTS ERROR S3 bucket must include encryption configuration

#2656 should solve your issue

Will be in the next release.

source: gharchive/issue

authors: kddejong kftsehk nathanagood

repo: aws-cloudformation/cfn-lint

license_type: permissive

license_source: github-api


text:
feat: Add support for self-managed CoreDNS addon and example of serverless cluster using Fargate Profiles

What does this PR do?

Adds support for self-managed CoreDNS addon
Adds example blueprint for Fargate Serverless cluster (data plane) using the self-managed CoreDNS addon; demonstrating how to modify the EKS provided CoreDNS deployment, etc.
Fixes pre-commit checks from prior PR

Motivation

Closes #549
Provides users with an example path on how to provision serverless EKS data planes using Fargate Profiles
Provides the start of how we might be able to manage the option to use either EKS managed addon or self-managed addon; this has come up before with requests like #523

More

[x] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)
[x] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)

⚠ No - I can add it to that repo but I think we need to test and validate that the GitOps route works first due to the tricky nature of how this is managed currently. Open to thoughts, feedback on how best to handle this

[x] Yes, I have updated the docs for this feature
[x] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.
For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

my only problem with this example is that it assumes creds are available to the null-exec.
but nor does it not take a profile flag, nor it accepts cross-account assume roles.
I've already spent days trying to work that out without much luck :(

my only problem with this example is that it assumes creds are available to the null-exec. but nor does it not take a profile flag, nor it accepts cross-account assume roles. I've already spent days trying to work that out without much luck :(

It uses an ephemeral kubeconfig which is contructed at apply time using an auth token. This means that all authorization/authentication is left with the provider which is left up to the users discretion. The current provider implementation uses the provider recommended exec which does accept --profile

source: gharchive/pull-request

authors: FernandoMiguel bryantbiggs

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


text:
Existing single Cluster Observability Pattern with AWS Mixed approach services

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.

@freschri Please fix the lint warnings, i see broken links.

@freschri Please fix the lint warnings, i see broken links.

done


text:
Unable to login

I just tried running the quickstart and deploying it into my existing VPC.  Everything in the cloud formation script completes successfully and I'm able to load the login page.  However, the username and password I configured earlier don't work.
I also noticed there is no output inside cloud formation and I ended up getting the URL from the load balancer page directly.
What else can I do to figure this out?  Thanks

did you by any chance try to set the username to admin? I believe an admin user is created by default for superset so If you try to use that as the username, you will be unable to login.
Changing my username to "superuser" in the quickstart parameters resolved the problem for me.

authors: frank-sorschak scottgeye


text:
Meeting Audio disconnect issue when end an external phone call

For handling external phone call we are using react-native-callkeep library, and we successfully hold the meeting and accept the phone call, but after some time the meeting attendee leave from the remote side automatically and trigger the - (void)audioSessionDidStopWithStatusWithSessionStatus:(MeetingSessionStatus * _Nonnull)sessionStatus; at our side(mobile user side) with status code 78
how to reconnect the audio session when getting sessionStatus code 78,
Got the same issue when we end the external phone call at caller side.
Test environment Info

Device: iPhone 7
OS: iOS 15.6.1
Version amazon-chime-sdk: 0.22.3
Version amazon-chime-sdk-media: 0.17.7

Hi @ashirkhan94,
78 means unknown error. you may need to increase the log level for the detail. For reconnecting, are you able to start the session again with the same meeting configuration?

Hi @georgezy-amzn
yes I can able to start the session again with the same meeting configuration, but after start the meeting session we are getting the OnMeetingEnd event from SDK side
Why this happening

Hi,
Any update

Hi @ashirkhan94 sorry for late response. I might have two questions.

How long were you on the call?
How many attendees were in the meeting?

Meeting ended automatically if there is not enough attendee, so wanted to make sure if that's the case.
An Amazon Chime SDK meeting ends when you invoke the [DeleteMeeting](https://docs.aws.amazon.com/chime/latest/APIReference/API_DeleteMeeting.html) API action.

Also, a meeting automatically ends after a period of inactivity, based on the following rules:

For [Amazon Chime SDK](https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_Operations_Amazon_Chime_SDK_Meetings.html) namespace:

No audio connections are present in the meeting for more than five minutes.
24 hours have elapsed since the meeting was created.
For [Amazon Chime](https://docs.aws.amazon.com/chime-sdk/latest/APIReference/API_Operations_Amazon_Chime.html) namespace:

No audio connections are present in the meeting for more than five minutes.
Only one audio connection is present in the meeting for more than 30 minutes.
24 hours have elapsed since the meeting was created.

Hi @hokyungh
there were 3 attendees in each meetings, and meeting duration is below 1 minute.
and the OnMeetingEnd event is coming with error error: audioFailedToStart
how to solve this issue

Hi @hokyungh
Any update

Hi @hokyungh there were 3 attendees in each meetings, and meeting duration is below 2 minute. and the OnMeetingEnd event is coming with error error: audioFailedToStart how to solve this issue

Hi Team
Any solution for this

authors: ashirkhan94 georgezy-amzn hokyungh


text:
Question: Confirming Cognito User

Hello,
I am running this command listed in the readme
aws cognito-idp admin-respond-to-auth-challenge --user-pool-id <> --client-id <> --challenge-name NEW_PASSWORD_REQUIRED --challenge-responses NEW_PASSWORD=<>,USERNAME=<>,userAttributes.name=<> --session “output_of_previous_command"

It prompts me in bash (on MAC) after I run this command and I am not sure what to put in the prompts. Any help you can give about this would really help me.
Thanks!
Dan

pls try:
aws cognito-idp admin-respond-to-auth-challenge --user-pool-id "change to user pool id" --client-id "change to user pool id" --challenge-name NEW_PASSWORD_REQUIRED --challenge-responses NEW_PASSWORD="change to new password",USERNAME="change to cognito user",userAttributes.name="change to cognito user" --session "change this to session variable from previous cmd"

authors: fadlihub thepersonclass


text:
[BUG][Functional] Unable to assume role created by the SEA

Bug reports which fail to provide the required information will be closed without action.
Required Basic Info

Accelerator Version:  v1.3.1
Install Type: Upgrade
Upgrade from version: v1.2.5

Describe the bug
After using the SEA to create a role in an OU workload AWS Account, it cannot be used. Any attempt to assume the role will fail. The cause is the SEA applies a tag to the created role, and this SCP guardrail prevents the role from being assumed:
{
      "Sid": "Tag2",
      "Effect": "Deny",
      "NotAction": [
        "iam:PassRole",
        "iam:GetRole",
        "iam:GetRolePolicy",
        "iam:ListAttachedRolePolicies",
        "iam:ListInstanceProfilesForRole",
        "iam:ListRolePolicies",
        "iam:ListRoles",
        "iam:GetInstanceProfile",
        "iam:GetLoginProfile",
        "iam:ListInstanceProfiles"
      ],
      "Resource": "*",
      "Condition": {
        "StringEquals": {
          "iam:ResourceTag/Accelerator": "${ACCELERATOR_NAME}"
        },
        "ArnNotLike": {
          "aws:PrincipalARN": ["arn:aws:iam::*:role/${ORG_ADMIN_ROLE}", "arn:aws:iam::*:role/${ACCELERATOR_PREFIX}*"]
        }
      }
    },

Failure Info

What error messages have you identified, if any:
An error occurred (AccessDenied) when calling the AssumeRole operation: User: arn:aws:sts::xxxxxxxxxx:assumed-role/TempAdmin/zzzzzzzz is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::bbbbbbbbbb:role/Demo-Role

Steps To Reproduce

Login to the "Operations" account
Create a role called "TempAdmin" and assign it AdministratorAccess permissions
Apply the following role to the 'Dev' OU 'roles' configuration.

{
            "role": "Demo-Role",
            "type": "other",
            "policies": ["AdministratorAccess"],
            "boundary-policy": "Default-Boundary-Policy",
            "source-account": "operations",
            "source-account-role": "TempAdmin",
            "trust-policy": "none"
}

Ensure that you have a workload account within the "Dev" OU. If not, create one.
Commit the config.json file
Run the statemachine
Confirm that the "Demo-Role" exists in an account in the DEV ou
While using the Operations "TempAdmin" role, attempt to assume role to "Demo-Role"

Expected behavior
When assuming the "Demo-Role" from within the "Operations" account, a successful role chain to an account in the "Dev" OU can be completed by assuming the "Demo-Role".
It is blocked because of the Tags assigned to the role.

Will be fixed in v1.3.3


text:
[BUG][Functional] Macie sensitive data findings not sent to Security Hub

Required Basic Info

Accelerator Version: v1.3.7
Install Type: Clean
Upgrade from version: N/A

Describe the bug
Macie is not configured to forward sensitive data findings to Security Hub.
Failure Info

What error messages have you identified, if any: N/A
What symptoms have you identified, if any: See screenshot

Required files
Default config
Steps To Reproduce

Go to Amazon Macie / Settings in any account
See that publishing of sensitive data findings is disabled

Expected behavior
Macie should be configured to forward sensitive data findings to Security Hub in all accounts.
Screenshots

Additional context
CLI workaround:
aws macie2 put-findings-publication-configuration --security-hub-configuration publishClassificationFindings=true,publishPolicyFindings=true

The addition of findings versus sensitive findings was a recent update to Macie
The ability to publish sensitive findings has already been added to the coming v1.5.0 release

see issue #752, item 6.


text:
End-to-End LLM Model Development with Torchtitan and Torchtune

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.

Progress update: I have created draft README.md and tested following scripts working:

0.configure-env-vars.sh
1.build-image.sbatch
3.pretrain.sbatch
4.finetune.sbatch
README.md in slurm subdirectory is still WIP.

Thanks @pbelevich  for the suggestion. I agree. Updated README.md to guide to clone the repository first.

Basic functionalities have been implemented. Allow me to iterate on the other PRs...

repo: aws-samples/awsome-distributed-training


text:
Need VOD file types that are supported by desktop browsers

Is your feature request related to a problem? Please describe.
Its frustrating that the package supports pretty much every kind of device browser - except desktop browsers.  The solution otherwise works beautifully.  It creates m3u8 files that work on all the handheld devices I've tested. BUT I need to install a special extension in my desktop browser (Chrome) so I can view the files.
Describe the feature you'd like
It would be great if the solution also generated vod files that are natively playable on desktop browsers (i.e. not just m3u8 files).
Additional context
I really like this solution. It works perfectly except for what I've described.  Hopefully, there is a "nerd knob" somewhere that I can change to give me the suggested vod file changes. Thank you for your time.

@raulmlamzn So, I guess what I'm asking for isn't possible right now?

nvm.  Found workaround.

repo: aws-solutions/video-on-demand-on-aws


text:
PKCS #11 MISRA Fixes

This commit contains various MISRA fixes and logic refactors.
Some MISRA violations that were fixed:
* 8.7
* 20.7
* 21.16
* 7.2
* 8.3
* 8.4
* 8.6
* 8.7
* 8.9
* 16.3
* 17.7
* 12.1
* 13.1
* 14.2
* 14.3
* 14.4
* 15.7
* 16.1
* 11.4
* 10.4

Description

Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] 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

The suppression of misra_c_2012_rule_10_5_violation occurs 53 times, like this one:
- CK_BBOOL xResult = CK_FALSE;
+ /* coverity[misra_c_2012_rule_10_5_violation] */
+ CK_BBOOL xResult = ( CK_BBOOL ) CK_FALSE;

Wouldn't it be better to add unsigned definitions of true and false?
    #define CK_FALSE_UNSIGNED  0U
    #define CK_TRUE_UNSIGNED   1U

The suppression of misra_c_2012_rule_10_5_violation occurs 53 times, like this one:
- CK_BBOOL xResult = CK_FALSE;
+ /* coverity[misra_c_2012_rule_10_5_violation] */
+ CK_BBOOL xResult = ( CK_BBOOL ) CK_FALSE;

Wouldn't it be better to add unsigned definitions of true and false?
    #define CK_FALSE_UNSIGNED  0U
    #define CK_TRUE_UNSIGNED   1U

Addition:
    #define CK_FALSE_UNSIGNED  ( ( CK_BBOOL ) 0U )
    #define CK_TRUE_UNSIGNED   ( ( CK_BBOOL ) 1U )

should also avoid the need for a cast.

These definitions are from the PKCS #11 standard.
The exception from MISRA:
"An integer constant expression with the value 0 or 1 of either signedness may be cast to a type which is defined as essentially Boolean. This allows the implementation of non-C99 Boolean models."
It would be best to use the standard, rather than implementing new data types in my opinion

/bot run checks

@gkwicker @aggarg apologies, I had to rebase to bring in the latest uncrustify config.

/bot run checks

repo: aws/amazon-freertos

license: MIT


text:
Improve Logging

Issue #, if available: Fixes https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/issues/102
Description of changes: Reduce the noise in the logging by adding a wrapper around the logr.Logger to take the advantage of zapr logging levels. zapr provides development mode which sets to logLevel=Debug, and the production mode to logLevel=Info. By default, production mode is enabled, unless explicit argument to set the development mode. Reference: https://sdk.operatorframework.io/docs/building-operators/golang/references/logging/
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #109 (8e1fdde) into main (7214c2c) will not change coverage.
The diff coverage is 40.90%.

@@           Coverage Diff           @@
##             main     #109   +/-   ##
=======================================
  Coverage   70.34%   70.34%
=======================================
  Files          14       14
  Lines        1359     1359
=======================================
  Hits          956      956
  Misses        330      330
  Partials       73       73

Impacted Files
Coverage Δ

pkg/controllers/serviceexport_controller.go
40.00% <33.33%> (ø)

pkg/controllers/cloudmap_controller.go
56.61% <37.50%> (ø)

pkg/cloudmap/client.go
77.57% <50.00%> (ø)

pkg/cloudmap/operation_poller.go
100.00% <100.00%> (ø)

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 7214c2c...8e1fdde. Read the comment docs.

authors: codecov-commenter runakash


text:
Improve compatibility with Dafny 4.4

Description of changes:
Improve compatibility with the upcoming Dafny 4.4 release. These are backward-compatible changes that should work with prior releases, as well.
The proof of AwsKmsMrkKeyring.AwsKmsMrkKeyring.OnDecrypt’ still needs to be updated for Dafny 4.4 in a way that's backward-compatible. (Using {:vcs_split_on_every_assert} allows it to go through with 4.4 but not 4.3 or 4.2.)
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Oh, yeah, this needs to be made from the AWS Repo or you cannot use the AWS Credentials.
I will move it over.

Closed by #129

authors: atomb texastony


text:
chore: add Rust release directory

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.

Since I cannot review all 2100 files (:sigh), to be sure, apart from the files .github/workflows/library_rust_tests.yml, DynamoDbEncryption/runtimes/rust/src/intercept.rs and DynamoDbEncryption/runtimes/rust/src/lib.rs, the change you made was copying the entire DynamoDBEncryption directory into releases/rust/db_esdk and run make polymorph_rust and make transpile_rust right?

Almost. I updated the files you mentioned in DynamoDbEncryption, then ran make polymorph_rust transpile_rust, and then copied the result to /releases/
Plus one other change -- I made a local copy of dafny_runtime_rust, since I can't point at the one in smithy-dafny from /releases/
Then I did cargo test and cargo run --example in the /releases/ directory, just to make sure.


text:
Status: parallelcluster-hpc002 - CREATE_FAILED

Environment:

AWS ParallelCluster / CfnCluster version
aws-parallelcluster-2.6.1
Configuration file (i.e. ~/.parallelcluster/config) without any credentials or personal data.
[aws]
aws_region_name = cn-northwest-1

[cluster sge]
key_name = shanxiong0511
vpc_settings = xiong
scheduler = sge
master_instance_type = t3.xlarge
compute_instance_type = m5.xlarge
initial_queue_size = 1
max_queue_size = 2
maintain_initial_size = true
cluster_type = spot
extra_json = { "cluster" : { "cfn_scheduler_slots" : "cores"} }
base_os = alinux
custom_ami = ami-056169db492793d02
compute_root_volume_size = 50
master_root_volume_size = 50
ebs_settings = genomes
scaling_settings = GATK-ASG
[ebs genomes]
shared_dir = genomes
ebs_snapshot_id = snap-040c71fd2bb5d4236
volume_type = gp2
volume_size =  1024
[scaling GATK-ASG]
scaledown_idletime = 5
[global]
cluster_template = sge
update_check = true
sanity_check = true
[aliases]
ssh = ssh {CFN_USER}@{MASTER_IP} {ARGS}
[vpc xiong]
vpc_id = vpc-335be65a
master_subnet_id = subnet-039e8ae1564970fe8
Bug description and how to reproduce:
A clear and concise description of what the bug is and the steps to reproduce the behavior.
[ec2-user@ip-172-20-0-208 ~]$ pcluster create -c ~/.parallelcluster/config hpc002 --norollback
Beginning cluster creation for cluster: hpc002
Creating stack named: parallelcluster-hpc002
Status: parallelcluster-hpc002 - CREATE_FAILED
Cluster creation failed.  Failed events:

AWS::CloudFormation::Stack parallelcluster-hpc002 The following resource(s) failed to create: [MasterServerWaitCondition, ComputeFleet].
AWS::AutoScaling::AutoScalingGroup ComputeFleet Resource creation cancelled
AWS::CloudFormation::WaitCondition MasterServerWaitCondition Failed to receive 1 resource signal(s) within the specified duration

i have try to create HPC cluster  serial times, all failure.
could you help me check my config file  or other some reason
thanks

attach file is the log

cfn-init-cmd.log
cfn-init.log
cloud-init.log
cloud-init-output.log

Hi @shanxiong001
I analyzed the logs you provided and I'm unable to find issues, so it seems the Master Server has been created correctly.
I see you set initial_queue_size = 1 so the cluster creation is probably failing during the creation of the compute instance.
You can retrieve the logs of the failing compute node by executing the pcluster create with the --norollback option and checking in the CloudWatch Groups created within the cluster.
In any case I see you're using a custom_ami. Which process did you follow to create it?
Thanks

repo: aws/aws-parallelcluster


text:
Remove ec2_iam_role validator

Removing ec2_iam_role validator until there is systematic way to check and generate permissions required by cluster

Signed-off-by: Rex shuningc@amazon.com
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Travis is stuck, merging in without travis to get unblocked


text:
aws-sdk-cpp-1.11.323 curlcode：35 SSL connect error

Describe the bug
In the aws-sdk-cpp-1.11.323 version, curlcode: 35 ssl connect error occurred while verifying a small demo, and verifySSL was disabled.
Here is the demo code:

Expected Behavior
It is expected that the execution will be successful and the size will be calculated as follows:

Current Behavior

Reproduction Steps

Possible Solution
No response
Additional Information/Context
demo g++ compilation command:

AWS CPP SDK version used
aws-sdk-cpp-1.11.323
Compiler and Version used
g++ 8.3.1
Operating System and version
Kernel :linux  Kernel version:5.14.21  x86_64 centos7

How are you building this sdk? and can you paste your code snippets in code block rather then in screenshots?

How are you building this sdk? and can you paste your code snippets in code block rather then in screenshots?你是如何构建这个SDK的？你能把你的代码片段粘贴到代码块中而不是屏幕截图中吗？

`#include <aws/s3/S3Client.h>
#include <aws/core/Aws.h>
#include <aws/core/auth/AWSCredentialsProvider.h>
#include <aws/transfer/TransferManager.h>
#include <aws/s3/model/HeadObjectRequest.h>
#include <aws/s3/model/HeadBucketRequest.h>
#include
#include
#include<sys/types.h>  /提供类型pid_t,size_t的定义/
#include<sys/stat.h>
#include<fcntl.h>
static const char* const ALLOCATION_TAG = "S3_HEADOBJECT";
int main(int argc, char* argv[]) {
Aws::SDKOptions options;
Aws::InitAPI(options);
{
// 自訂 S3 End Point
const Aws::String endPoint = "172.16.10.115:9000";
const Aws::String bucketName = "hcc-bucket";
//const Aws::String objectName = "project_id_1";
const Aws::String objectName = argv[1];
const Aws::String region = "us-west-2";
// 認證資訊
const Aws::String accessKey = "minioadmin";
const Aws::String secretKey = "minioadmin";
bool using_virtual_address = false;
// 建立 S3 Client
Aws::Client::ClientConfiguration config;
config.verifySSL = false;
config.scheme = Aws::Http::Scheme::HTTP;
config.region = region;

//bool using_virtual_address = bucket_cfg.s3_uri_style == 0 ? true : false;
Aws::Auth::AWSCredentials cred(accessKey, secretKey);

auto s3Client = Aws::MakeShared<Aws::S3::S3Client>(
             ALLOCATION_TAG,
             cred,
             config,
             Aws::Client::AWSAuthV4Signer::PayloadSigningPolicy::Never,
             using_virtual_address);
s3Client->OverrideEndpoint(endPoint);

// aws request
Aws::S3::Model::HeadObjectRequest aws_req;
aws_req.SetBucket(bucketName);
aws_req.SetKey(objectName);

Aws::S3::Model::HeadObjectOutcome aws_resp = s3Client->HeadObject(aws_req);
if (aws_resp.IsSuccess()) {
    long long size_total = aws_resp.GetResult().GetContentLength();
    std::cout << "objectName:" << objectName << ", size:" << size_total << std::endl;
} else {
    // has error
    auto err = aws_resp.GetError();
    std::cout << "head object error, objectName:"<< objectName << ", errno:" << (int)err.GetErrorType() << ", errmsg:" << err.GetMessage()<< std::endl;
}

}
Aws::ShutdownAPI(options);
return 0;
}`

Can you reproduce this error when using AWS s3 buckets? We can't guarantee that this sdk will work with third party buckets (i.e. minio). If you can reproduce this with an s3 bucket then we can take a closer look.

Can you reproduce this error when using AWS s3 buckets? We can't guarantee that this sdk will work with third party buckets (i.e. minio). If you can reproduce this with an s3 bucket then we can take a closer look.

Okay, I'll give it a try

Can you reproduce this error when using AWS s3 buckets? We can't guarantee that this sdk will work with third party buckets (i.e. minio). If you can reproduce this with an s3 bucket then we can take a closer look.

Okay, I'll give it a try

在使用AWS s3 bucket时，是否可以重现此错误？我们不能保证这个sdk将与第三方bucket（即minio）一起工作。如果你能用一个s3桶来复制这个，那么我们就可以仔细看看了。

好吧，我试试

After our discussion, we want to support third-party libraries. Do you have any other solutions to solve this problem?

Can you reproduce this error when using AWS s3 buckets? We can't guarantee that this sdk will work with third party buckets (i.e. minio). If you can reproduce this with an s3 bucket then we can take a closer look.

Okay, I'll give it a try

在使用AWS s3 bucket时，是否可以重现此错误？我们不能保证这个sdk将与第三方bucket（即minio）一起工作。如果你能用一个s3桶来复制这个，那么我们就可以仔细看看了。

好吧，我试试

After our discussion, we want to support third-party bucket like ceph and minio. Do you have any other solutions to solve this problem?

This sdk doesn't officially support and third-party buckets like ceph and minio. If they do work with this sdk, that is great. But we only guarantee compatibility with AWS s3 buckets. If the root cause is because of an issue with a third-party bucket, then you would need to contact the third-party bucket to see if they would fix the problem. The other possibility is that this is a problem with this sdk. To show that we need to be able to reproduce the same error (curlcode：35 SSL connect error) while using an AWS s3 bucket.
You can also use the respective sdk's for third-party buckets if you're using third-party buckets. This might be your best solution if you want to use ceph and minio.

This sdk doesn't officially support and third-party buckets like ceph and minio. If they do work with this sdk, that is great. But we only guarantee compatibility with AWS s3 buckets. If the root cause is because of an issue with a third-party bucket, then you would need to contact the third-party bucket to see if they would fix the problem. The other possibility is that this is a problem with this sdk. To show that we need to be able to reproduce the same error (curlcode：35 SSL connect error) while using an AWS s3 bucket.
You can also use the respective sdk's for third-party buckets if you're using third-party buckets. This might be your best solution if you want to use ceph and minio.
该sdk不正式支持ceph和minio等第三方桶。如果他们确实使用这个SDK，那就太好了。但我们仅保证与AWS s3桶的兼容性。如果根本原因是第三方存储桶的问题，那么您需要联系第三方存储桶，看看他们是否会解决该问题。另一种可能是这个sdk有问题。为了说明我们需要能够在使用AWS s3存储桶时重现相同的错误（curlcode：35 SSL connect error）。
如果你使用的是第三方bucket，你也可以使用第三方bucket的相应sdk。如果你想使用ceph和minio，这可能是你最好的解决方案。

This sdk doesn't officially support and third-party buckets like ceph and minio. If they do work with this sdk, that is great. But we only guarantee compatibility with AWS s3 buckets. If the root cause is because of an issue with a third-party bucket, then you would need to contact the third-party bucket to see if they would fix the problem. The other possibility is that this is a problem with this sdk. To show that we need to be able to reproduce the same error (curlcode：35 SSL connect error) while using an AWS s3 bucket.
You can also use the respective sdk's for third-party buckets if you're using third-party buckets. This might be your best solution if you want to use ceph and minio.

According to our testing of aws bucket, we can get the expected effect, but we still hope to get the support of a third-party bucket, and I wonder whether your company will make compatibility requirements in the future.

Sorry, but we don't plan to support third-party buckets at any point in the future. Closing this issue

repo: aws/aws-sdk-cpp


text:
Aws::Client::ClientConfiguration::ClientConfiguration(void)

What platform/OS are you using?
Windows
What compiler are you using? what version?
VS
What's your CMake arguments?

Can you provide a TRACE level log? (sanitize any sensitive information)

error LNK2019: unresolved external symbol "public: __thiscall Aws::Client::ClientConfiguration::ClientConfiguration(void)" (??0ClientConfiguration@Client@Aws@@QAE@XZ) referenced in function "public: __thiscall CppAmazonClient::CppAmazonClient(class std::basic_string<char,struct std::char_traits,class std::allocator > const &,class std::basic_string<char,struct std::char_traits,class std::allocator > const &,class std::basic_string<char,struct std::char_traits,class std::allocator > const &)" (??0CppAmazonClient@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@00@Z)

Could you please give us a more detailed description of how did this happened?

authors: mayovtester singku


text:
Segment assumed started under lambda results in exception

This is a regression from https://github.com/aws/aws-xray-sdk-python/pull/127
[ERROR]	cannot find the current segment/subsegment, please make sure you have a segment open
[WARNING]	No segment found, cannot begin subsegment foo.app.
[ERROR]		Exception on / [GET]
Traceback (most recent call last):
File "/var/task/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/var/task/flask/app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/var/task/flask_cors/extension.py", line 161, in wrapped_function
return cors_after_request(app.make_response(f(*args, **kwargs)))
File "/var/task/flask/app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/var/task/flask/_compat.py", line 35, in reraise
raise value
File "/var/task/flask/app.py", line 1811, in full_dispatch_request
rv = self.preprocess_request()
File "/var/task/flask/app.py", line 2087, in preprocess_request
rv = func()
File "/var/task/aws_xray_sdk/ext/flask/middleware.py", line 57, in _before_request
segment.save_origin_trace_header(xray_header)
AttributeError: 'NoneType' object has no attribute 'save_origin_trace_header'

For context this is under lambda execution of zappa/flask and aws-xray-sdk-python is initiated as follows:
from aws_xray_sdk.core import xray_recorder, patch_all
from aws_xray_sdk.core.lambda_launcher import check_in_lambda
from aws_xray_sdk.core.context import Context
from aws_xray_sdk.ext.flask.middleware import XRayMiddleware
[...snip...]
  if check_in_lambda():
      xray_recorder.configure(service=__name__, sampling=False, context=Context())
      XRayMiddleware(app, xray_recorder)
      patch_all()

Its obvious that this is related to application not being able to start segment (not entirely clear to me why that is happening), however if segment is not found for what ever reason expectation is that application starts (with warning) rather than crash with exception.
Assumption that if code is under lambda it must already have segment created is not entirely accurate?

Hey,
Thank you very much for letting us know about the issue you are having.
This new release added official support for the Serverless model. Prior to this, a common work around for customers to use middlewares in Lambda was to override the recorder to use the default context, which is what Context() is, and to not automatically use the LambdaContext.
This update changed the way middlewares behave in Lambda directly. They automatically create subsegments now instead of segments. So it is no longer necessary to override the recorder's Context.
So to fix your problem, all you have to do is remove the parameter context=Context() from your recorder configuration.

This does indicate an even deeper bug: The middleware should only opt to begin subsegments rather than segments when the LambdaContext is used. That way, middlewares would not suddenly change behaviors when custom contexts are used--even if it's being used in a lambda environment. #138

Awesome, removing context=Context() solved the problem. Thank you very much!

authors: IlyaSukhanov chanchiem

repo: aws/aws-xray-sdk-python


text:
Using pseudo-version for go mod replace

Description of changes:
Using the pseudo-version of release tag v.2.8.0 for dependency github.com/docker/distribution. Hopefully fixes issue
Testing:
go mod tidy
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

authors: abhay-krishna pokearu

repo: aws/eks-anywhere


text:
bump CLI bundle release trigger for release 0.9

Issue #, if available:
Description of changes:
bump CLI dev bundle release trigger for v0.9.0
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test eks-anywhere-release-tooling-presubmit

/override eks-anywhere-release-tooling-presubmit
/lgtm

/override eks-anywhere-release-tooling-presubmit
/override eks-anywhere-presubmit

authors: abhay-krishna danbudris


text:
Add Ops Tool to PROD for Distro-build-tooling

Issue #, if available:
Description of changes:
Added the Deployment and Service values that are pulled when adding the tool to prod. Added the image information for the tool in the public ecr.
Tested the tool against personal repo and got expected responses to opened issues.
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-distro-build-tooling


text:
move and revise AWS constraints

1. Issue, if available:
#589
2. Description of changes:

move AWS dir out from "cloud providers" to top level of docs nav
revise based on updates to provisioner crd
refactor into "spec.requirements" and "spec.constraints"

3. Does this change impact docs?

[X] Yes, PR includes docs updates

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

@ellistarn @akestner @chrisnegus
please review to see if the moving "spec.requirements" description to the "provisioner CRD" page (and included revisions), is in the general vicinity of being tolerable.

ready for review!

Now that AWS is not in a Cloud Providers section, it seems to sparse to me to just call the section AWS. Could we change the title from "AWS" to "AWS Cloud Provider" in the pre-docs/AWS/_index.md file?

/approve

revised; rebased;

authors: chrisnegus geoffcline

repo: aws/karpenter


text:
Please provide/document a way to create Rust extensions

Describe the problem
I would like to be able to add Rust extensions to postgres to perform complex server-side computations.
Describe alternatives
Host my own PostgreSQL and build a rust extension using one of many documented paths like this

pg_tle is language agnostic and can use any procedural language available on the database instance. If you'd like to use Rust, you'll want to explore PL/Rust https://github.com/tcdi/plrust

@jim-mlodgenski thanks for the link! I was looking at the list of extensions available on RDS, and plrust is not one of them, so I was hoping that pg_tle would somehow enable it, especially considering all AWS support of Rust.
The only relevant available extensions seem to be plcoffee, plls, plperl, plpgsql, pltcl, plv8.

@nyurik I'm interested in this problem as well. I found these slides from AWS re:Invent that lists PL/Rust as a trusted language

PL/Rust is an active community project that does provide an trusted language handler for PostgreSQL and works well with TLE today. It is a little complex to build and setup, but the PL/Rust community has some documentation on how to do that.
https://github.com/tcdi/plrust

@jim-mlodgenski could you link to documentation showing how to use pg_tle with PL/Rust? I can't find any documentation (or even comments) suggesting it's possible, other than your comment here.

I found this blog post:

In this post, we show how to deploy an RDS for PostgreSQL instance with PL/Rust enabled [...]

It references pg_tle only once, but information elsewhere indicates that pg_tle works with any "trusted" language installed in Postgres, and plrust installed this way is trusted.

authors: jim-mlodgenski kpamaran mogul nyurik seanlinsley


text:
2024-06-25_01-33-01_master-next_aws-crt-cpp

Automatically created.

/run

authors: aws-iot-embedded-linux-ci thomas-roos


text:
Instancecert input

when adding the instancecert for nodejs to my .ebextensions folder, what do I put in the following area. My certificate is a public one issues by AWS certificate manager.
Default: |
-----BEGIN CERTIFICATE-----
Paste your public certificate content here
-----END CERTIFICATE-----

AWS Certificate Manager (ACM) certificates can attach to load balancers, but not to EC2 instances. So in this case, when you need to terminate at an instance and attach a certificate to the instance, they won't work.
You'll need to use a non-ACM certificate on the instance.
An engineer on our team found this: https://stackoverflow.com/questions/48386839/aws-elastic-beanstalk-nodejs-get-certificate-ssl-from-letsencrypt-without-be

authors: dankhen fsajwani

repo: awsdocs/elastic-beanstalk-samples


text:
EKS bootstrap script setting wrong value for Max Pods in kubelet for CNI Custom Networking

What happened:
When we use Custom CNI. The number of interfaces available reduces to N-1
and accordingly the maximum ips available for pods changes. But currently when we use
Custom CNI , it still configures the kubelet with the same maximum pods as in this file
https://github.com/awslabs/amazon-eks-ami/blob/master/files/eni-max-pods.txt
eg: For a T3 medium with 3 interfaces and 6 ips per interface.
The maximum pods turn out to be (36-3) + 2( aws-node and kube-proxy)=17
For the same node in custom cni the maximum number of pods would be 12 (26-2)+2 ( aws-node and kube-proxy)
What you expected to happen:
It should configure the max pods to a different number.
How to reproduce it (as minimally and precisely as possible):
Configure Custom CNI  for EKS cluster and check the max pods setting on the kubelet.
Anything else we need to know?:
This is causing an issue as the pods get scheduled on node even if there is not sufficient Ip
and get stuck in container creating on the node.
The pods get scheduled to node as the controller is not aware of the maximum number of ips.
https://github.com/aws/amazon-vpc-cni-k8s/issues/18
https://github.com/kubernetes/kubernetes/issues/5507
The only way to stop the pod from getting scheduled is with max pods ip setting.
I would suggest to use a separate file for max pods rather than the same file for configuring max pods based on some environment variable.
Environment:

AWS Region: N/A
Instance Type(s): N/A
EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): N/A
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version):
AMI Version: N/A
Kernel (e.g. uname -a): N/A
Release information (run cat /etc/eks/release on a node): N/A

We need better documentation on how to work around this issue. Tracked in https://github.com/awsdocs/amazon-eks-user-guide/pull/72
Also related to https://github.com/aws/amazon-vpc-cni-k8s/issues/527

authors: mogren smrutiranjantripathy

repo: awslabs/amazon-eks-ami


text:
[ 68%] Linking C shared library libcproducer.dylib [ 68%] Built target cproducer make: *** [all] Error 2

after installed all build tools and run ./min-install-script
received:
[ 68%] Linking C shared library libcproducer.dylib
[ 68%] Built target cproducer
make: *** [all] Error 2
I am using macOS 10.15.6

Please use the latest code/release . Use the instructions in the readme.md and not the min install script. The documentation in the AWS docs is stale. The build is now based on cmake script

authors: MushMal RayChanDatalityLab


text:
Adding new notebook for Pipe mode with custom TensorFlow training script

Description of changes:
I have worked with multiple customers that are committed to TensorFlow as their core framework for deep learning. They want to build large scale models on SageMaker, but get frustrated when they cannot figure out how to use Pipe mode or distributed training. This notebook provides an end-to-end fully working example that gets them over that hump. As opposed to classic use cases based on image data, this one uses a synthetic dataset that aligns well to many classification and regression problems (fraud detection, medical condition identification, prediction of networking issues, ...).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Any feedback?

Any update on this proposed new notebook?

I am terribly sorry for lack of response.
Is it possible to update this example to use Tensorflow 2?

authors: markproy nadiaya

repo: awslabs/amazon-sagemaker-examples


text:
Tabular: Removed usage of catboost-dev

Issue #, if available:
Description of changes:

Removed usage of catboost-dev (can just use catboost for soft-class now that 0.24 is released)
NOTE: softclass is extremely slow for catboost due to unoptimized objective and metric for soft log loss. The below warnings are printed when trying to train with softclass (although it does train successfully, just 10x slower than would be expected).

Fitting model: CatBoost_DSTL ...
	Fitting CatBoost_DSTL with 'num_gpus': 0, 'num_cpus': 4
	Catboost model hyperparameters: {'iterations': 10000, 'learning_rate': 0.05, 'random_seed': 0, 'allow_writing_files': False, 'loss_function': <autogluon.tabular.models.catboost.catboost_softclass_utils.SoftclassObjective.SoftLogLossObjective object at 0x103bceb00>, 'eval_metric': <autogluon.tabular.models.catboost.catboost_softclass_utils.SoftclassCustomMetric.SoftLogLossMetric object at 0x11ba446a0>}
/Users/neerick/workspace/venvs/autogluon/lib/python3.6/site-packages/catboost/core.py:1464: UserWarning: Failed to optimize method "calc_ders_multi" in the passed object:
Failed in nopython mode pipeline (step: nopython frontend)
Untyped global name 'sum': Cannot determine Numba type of <class 'builtin_function_or_method'>
File "tabular/src/autogluon/tabular/models/catboost/catboost_softclass_utils.py", line 50:
        def calc_ders_multi(self, approxes, targets, weight):
            <source elided>
            exp_approx = [math.exp(val) for val in approxes]
            exp_sum = sum(exp_approx)
            ^
  self._object._train(train_pool, test_pool, params, allow_clear_pool, init_model._object if init_model else None)
/Users/neerick/workspace/venvs/autogluon/lib/python3.6/site-packages/catboost/core.py:1464: UserWarning: Failed to optimize method "evaluate" in the passed object:
Failed in nopython mode pipeline (step: nopython frontend)
Untyped global name 'soft_log_loss': Cannot determine Numba type of <class 'autogluon.core.metrics._ProbaScorer'>
File "tabular/src/autogluon/tabular/models/catboost/catboost_softclass_utils.py", line 36:
        def evaluate(self, approxes, target, weight):
            <source elided>
            approxes = np.multiply(approxes, 1/np.sum(approxes, axis=1)[:, np.newaxis])
            error_sum = soft_log_loss(np.array(target), np.array(approxes))
            ^
  self._object._train(train_pool, test_pool, params, allow_clear_pool, init_model._object if init_model else None)

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

Pushed a JIT compatible soft logloss to avoid these warnings

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

authors: Innixma jwmueller szha

repo: awslabs/autogluon


text:
Log the logs url

so that users can easily jump to logs of a particular step. When there are multiple parallel codebuild steps, it is not possible to go to the dashboard for every step. See https://github.com/awslabs/aws-codebuild-jenkins-plugin/issues/27
Alternative solution
If we log the cloudwatch logs url for the step, then the user can see the logs for each step in the logs of each step (see screen shot). This solves https://github.com/awslabs/aws-codebuild-jenkins-plugin/issues/27 to a certain extent because, the logs contain the phase information (though in a less nicer form).
So now users have to go through 3 steps (assuming a pipeline build)

Figure out which step failed

Go the logs of that step and click on the actual cloudwatch url

Go the cloudwatch dashboard and see why the build really failed

This contribution is under the Apache 2.0 license.

repo: awslabs/aws-codebuild-jenkins-plugin


text:
python/iam-unused-keys.py shows compliant even for non-compliant iam-user.

This config rule shows compliant even for non-compliant resources.

I have the same issue

Hello,
In https://github.com/awslabs/aws-config-rules/pull/71, I fixed the iam-unused-keys.py rule. The rule was broken due to some changes in AWS APIs. About merging iam-unused-keys.py and iam-unused-user.py, it looks like it was done in https://github.com/awslabs/aws-config-rules/pull/68.
Enjoy!

repo: awslabs/aws-config-rules

license_source: bigquery


text:
New custom rule for checking patch compliance

Hi,
This is my first time submitting a pull request on this repo. Please let me know if I need to modify something.
This is a new custom rule that I wrote to find out if a set of ec2 instances (filtered based on a given tag and value) is compliant to a SSM patch baseline.

As been launched as managed rules: https://docs.aws.amazon.com/config/latest/developerguide/ec2-managedinstance-patch-compliance-status-check.html

Thanks for the review. Sorry I just noticed this and missed replying on previous comments.

No worries. Keep pushing PR :)

authors: jongogogo lahirian


text:
InvokeRDSBootstrapDatabase throws the error while trying to connect to database

Database initialization functionality in SaaSBoost tried to access poastgresql and threw an exception. I got below error message in rdsbootstrap lambda log group.

Reproduction Steps

upload .sql file(UTF-8 encoded) in rds appconfig screen.
try to onboard a tenant, you will see the above error message.

What did you expect to happen?

At least the database connection should be established, even though some syntax error might be occurred.
What actually happened?

Can't connect to database host
Environment

AWS Region  : ap-northeast-2
AWS SaaS Boost Version : Version 798371c
Workload OS  (Linux or Windows) :  linux

Other

This is :bug: Bug Report

For someone who encounters this error like me.
Here's the root cause I found -
ResultSet had been closed within try block(line: 187) in RdsBootstrap.databaseExists before trying rs.next() (line:194)
I So I just moved while block while (rs.next()) {  into the try block as follows. You can fix this temporarily by changing this part and try to run it.

Of course, I understand that there will be many considerations for supporting DB engines from the team's perspectives.
I wrote this to reduce the # of developers who are wandering until then.

authors: bella-kwon rnlduaeo

repo: awslabs/aws-saas-boost


text:
aws-kinesisstreams-gluejob: Unknown Classification, classification instead set as table property

When you create a Glue Table using the KinesisstreamToGlue Job Construct, the classification is set to unknown. Instead, a table property "classification" : "json" is set.
Here is a screenshot of the resulting stream

Reproduction Steps

I created this with an existing stream, but I am not sure if this is what caused the bug, or if it also would be there without it.
SCHEMA: glue.CfnTable.ColumnProperty = [
    {
        "name": "user",
        "type": "string",
        "comment": "Name of the user"
    },
    {
        "name": "package_id",
        "type": "string",
        "comment": "A unique package id"
    },
    {
        "name": "product_id",
        "type": "int",
        "comment": "A list of product ids that are in the package"
    },
    {
        "name": "origin",
        "type": "string",
        "comment": "Which FC the package came from"
    },
    {
        "name": "destination",
        "type": "string",
        "comment": "The address where the package is delivered to"
    },
    {
        "name": "weight",
        "type": "float",
        "comment": "The weight of the package"
    }
]

input_data_stream = kinesis.Stream(self, "input-stream", stream_name="input-data-stream",
                                                shard_count=2,
                                                retention_period=core.Duration.hours(24))

streaming_job = KinesisstreamsToGluejob(self, "streaming-job", glue_job_props={"command": {
            "name": "gluestreaming",
            "pythonVersion": "3",
            "scriptLocation": assets.Asset(self, "SparkCode", path="spark_code/transform.py").s3_object_url,
        }}, field_schema=SCHEMA, existing_stream_obj=input_data_stream)

Error Log

I can't execute any jobs on the table as the classification is set to unknown
Environment

**CDK CLI Version      :1.104
**CDK Framework Version:1.99
**AWS Solutions Constructs Version     :1.99
**OS                   :MacOs
**Language             :Python

Other

This is :bug: Bug Report

This might be a glue issue, speaking to the service team about this.

Thanks - let us know what you hear.

authors: FinnIckler biffgaut

repo: awslabs/aws-solutions-constructs


text:
chore(merge-back): 2.55.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 67cece286400346093c62c9d6b1dedeaacb90870
Result: SUCCEEDED
Build Logs (available for 30 days)

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


text:
chore(merge-back): 1.131.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: efff55acebd4430af66aa6c31d37f4737289e159
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: efff55acebd4430af66aa6c31d37f4737289e159
Result: SUCCEEDED
Build Logs (available for 30 days)

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


text:
fix(aws-apigateway-iot and aws-cloudfront-apigateway-lambda): fixed deprecated warnings

Issue #551 , if available:
Description of changes:
-Replaces UsagePlanProp.apiKey with method addApiKey()
-options prop in LambdaRestApi has been deprecated since it now extends RestApiProps, removed options prop in test
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
fixes #551

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 0a7e0ff2abe730c02d76dea8d70fb765d33635ef
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 0a7e0ff2abe730c02d76dea8d70fb765d33635ef
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: a5eaacf6b0193c421407d3a00132ea7547844d23
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: a5eaacf6b0193c421407d3a00132ea7547844d23
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 23e4ab8c6e29c4f18080aef03677a81284509c3f
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 23e4ab8c6e29c4f18080aef03677a81284509c3f
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 9f4e139e99cb6f746a036a39c6d2b1c9e67f217d
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 9f4e139e99cb6f746a036a39c6d2b1c9e67f217d
Result: SUCCEEDED
Build Logs (available for 30 days)

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


text:
Can't submit job using slurm on mounted s3

I mounted s3 bucket using s3fs to the master node that was created by cfncluster. What I found out is I can submit jobs using slurm sbatch outside the s3 directory but not inside it. I've checked the file permissions and even made everyone can write and execute that job script inside the mounted s3. But it all seems slurm can't submit the job since squque gives nothing output.

Turned out it's not a slurm issue nor s3 permission issue. The s3 bucket was only mounted to the master node, all other compute nodes have no idea of this mounted s3. I'm trying to use the post_install to get this s3 mounted to all nodes.

repo: awslabs/cfncluster


text:
Refactor CLI package

This cleans up some of the internals of the CLI package.  I've also added the start of functional tests for this module.

Codecov Report

Merging #235 into master will increase coverage by 8.07%.

@@            Coverage Diff             @@
##           master     #235      +/-   ##
==========================================
+ Coverage   70.77%   78.84%   +8.07%
==========================================
  Files          12       13       +1
  Lines        1485     1489       +4
  Branches      191      191
==========================================
+ Hits         1051     1174     +123
+ Misses        383      259     -124
- Partials       51       56       +5

Impacted Files
Coverage Δ

chalice/cli/init.py
55.9% <100%> (+55.9%)
:white_check_mark:

chalice/cli/utils.py
84% <84%> (ø)

chalice/logs.py
23.52% <ø> (+23.52%)
:white_check_mark:

chalice/prompts.py
100% <ø> (+100%)
:white_check_mark:

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 5721e4a...eb9af73. Read the comment docs.

authors: codecov-io jamesls

repo: awslabs/chalice


text:
Import into eclipse workspace

Description
djl.ai did not compile after importing the gradle project into eclipse.
reasons are 2 issues which per default are flagged by eclipse as errors cause this can be seen as bad smells/bad coding practise.

cycle dependencies in the compile-classpath.
package-info.java files exists in src/main/java and in src/test/java in the same package. same file getting compiled to same package in the classpath is a bad smell and get flagged.

Both issue can be configured in eclipse workspace so that eclipse ignore this, but we have to do this after every new import - for example when clean checkout a new version of djl (like version 0.9.0 yesterday)
this can get automated through gradle -> this change set the settings for eclipse workspace and can be execute via "gradlew eclipse" before importing

package-info.java files exists in src/main/java and in src/test/java in the same package. same file getting compiled to same package in the classpath is a bad smell and get flagged.

We enabled checkstyle, if we remove those package-info.java, checkstyle will fail. I didn't find a way to workaround this issue.

package-info.java files exists in src/main/java and in src/test/java in the same package. same file getting compiled to same package in the classpath is a bad smell and get flagged.

We enabled checkstyle, if we remove those package-info.java, checkstyle will fail. I didn't find a way to workaround this issue.

package-info.java files exists in src/main/java and in src/test/java in the same package. same file getting compiled to same package in the classpath is a bad smell and get flagged.

We enabled checkstyle, if we remove those package-info.java, checkstyle will fail. I didn't find a way to workaround this issue.

this lines in the gradle, will advise eclipse to ignore the package-info files in src/test during building, so its fine for eclipse users
	sourceSets.test.java {
			srcDirs = ["src/test/java"]
			exclude "**/package-info.java"
		}

package-info.java files exists in src/main/java and in src/test/java in the same package. same file getting compiled to same package in the classpath is a bad smell and get flagged.

We enabled checkstyle, if we remove those package-info.java, checkstyle will fail. I didn't find a way to workaround this issue.

this lines in the gradle, will advise eclipse to ignore the package-info files in src/test during building, so its fine for eclipse users
	sourceSets.test.java {
			srcDirs = ["src/test/java"]
			exclude "**/package-info.java"
		}

authors: ebamberg frankfliu

repo: awslabs/djl


text:
Auth strategy

Background:
The SMART-on-FHIR specification only governs the exchange of scopes between the SMARTApp and the authorization server and does not take a position on how an authorization server and resource server ought to coordinate authorization. The latter is left up to the implementer.
The current implementation uses token introspection via the /userinfo url. However, The SMART-on-FHIR specification does not require the fhirUser claim to be present in the access_token or via the /userinfo endpoint on the authorization server. Therefore, other implementations of the authorization server (like Auth0) will not be able to comply with these expectations.
This is a proposal for a more flexible strategy pattern that will allow implementers to design their own token validation and authorization strategies.
Description of changes:
This change refactors the SMARTHandler.isAuthorized() method such that the specific authorization strategy used to implement SMART-on-FHIR can be encapsulated in classes that implement the (new) AuthStrategy interface. This allows other implementations to define their own strategies and inject them into the authorization flow via the SMARTConfig object.
Example config:
const authZConfig: SMARTConfig = {
    version: 1.0,
    scopeKey: 'scp',
    scopeValueType: 'array',
    scopeRule,
    expectedAudValue: expectedAud,
    expectedIssValue: expectedIss,
    expectedFhirUserClaimKey: 'fhirUser',
    fhirUserClaimRegex: /(\w+)\/(\w+)/g,
    authZUserInfoUrl: `${expectedIss}/userInfo`,
    authStrategies: [new UserInfoStrategy(`${expectedIss}/userInfo`, 'fhirUser')],
};

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

The use cases I had in mind for multiple strategies:

We can use different strategies for different types of users of the API. For example, one strategy can be implemented for a patient accessing their own data, another for an authorized representative accessing data on behalf of a patient, and a third for a hospital or plan admin accessing data on their patient population. Each strategy could skip validation altogether if the access context doesn't match, but the authorization module would be aware of all the available strategies for each access context.

This would allow us to implement strategies in a modular fashion and then combine them to form more complex strategies. For example, one strategy could validated clinical scopes against the operations permitted for those scopes, while another strategy can validate fine-grain access control against the specific resource being requested, while yet a final strategy can layer in vertical access control against the specific attributes being requested within the resource.

Now, I admit these are a bit contrived, but I also figured adding the flexibility now couldn't hurt. Thoughts?

I am going to archive this thought for now (as we have tabled it and this PR is now stale) -- but happy to revisit if interested

I am going to archive this thought for now (as we have tabled it and this PR is now stale) -- but happy to revisit if interested

authors: emilhdiaz rsmayda

repo: awslabs/fhir-works-on-aws-authz-smart


text:
Fix LSTNet observed indicator usage

Issue #, if available: Addresses the same issue as #802
Description of changes: This PR addresses the same issue as #802 (issues with scaling=False and hybridize=True) by

using the observed indicator as input to the model blocks (CNN and FF)

Furthermore

future observed indicator is added to the training network and used to mask the loss
tests updates are copied from #802, except that the number of test cases is here reduced

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

Thanks Lorenzo! this is a better solution. LGTM!

authors: ehsanmok lostella

repo: awslabs/gluon-ts


text:
Enable resampling for PandasDataset

When using PandasDataset we require that the index of each input DataFrame is uniform, meaning that it is complete (no missing timestamps) and the gap between two consecutive timestamps is equal to the desired frequency.
For a given DataFrame it is easy to fulfil the requirement using .resample:
df.resample(freq).agg(...)

However, this operation is relatively slow (~1 ms on my local machine, ~100x slower than checking the invariant) so we might want to only do this when required.
When resampling, values are grouped together for each new time step and then aggregated. When there are no values for a given time step the input to the aggregation is an empty frame and the result depends on the aggregation function used, e.g. 0 for sum and nan for mean.
Different columns might require different aggregations. For example, when considering ice-cream sales together with outside temperature given in daily frequency that should be aggregated to weekly frequency we would want to sum the number of sales for each week, but take some mean of the temperature instead. However, one might also use nan for number of sales when there are no sales recorded for a given week instead of falling back to 0 (maybe the store was closed and thus 0 doesn't reflect the actual demand).
Things to considers:

always require input freq instead of trying to guess it
always resample if needed
expose aggregation functions to customise behaviour, maybe default to sum for target but mean for dynamic features?

However, this operation is relatively slow (~1 ms on my local machine, ~100x slower than checking the invariant) so we might want to only do this when required.

But it needs to be done only once, right? (For inference this would still be a lot I guess; also it depends on the size of the dataframe?)
I think one drawback of having to do this manually is when using the from_long_dataframe constructor, in which case being able to control resampling would be very useful, I feel.

When using PandasDataset we require that the index of each input DataFrame is uniform, meaning that it is complete (no missing timestamps) and the gap between two consecutive timestamps is equal to the desired frequency.
For a given DataFrame it is easy to fulfil the requirement using .resample:
df.resample(freq).agg(...)

However, this operation is relatively slow (~1 ms on my local machine, ~100x slower than checking the invariant) so we might want to only do this when required.
When resampling, values are grouped together for each new time step and then aggregated. When there are no values for a given time step the input to the aggregation is an empty frame and the result depends on the aggregation function used, e.g. 0 for sum and nan for mean.
Different columns might require different aggregations. For example, when considering ice-cream sales together with outside temperature given in daily frequency that should be aggregated to weekly frequency we would want to sum the number of sales for each week, but take some mean of the temperature instead. However, one might also use nan for number of sales when there are no sales recorded for a given week instead of falling back to 0 (maybe the store was closed and thus 0 doesn't reflect the actual demand).

always require input freq instead of trying to guess it
always resample if needed

I'd say that resampling can be done by default if freq is given. Then freq remains optional, but will be required in case the data fails the test, so that resampling can work as intended.

However, this operation is relatively slow (~1 ms on my local machine, ~100x slower than checking the invariant) so we might want to only do this when required.

But it needs to be done only once, right? (For inference this would still be a lot I guess; also it depends on the size of the dataframe?)
I think one drawback of having to do this manually is when using the from_long_dataframe constructor, in which case being able to control resampling would be very useful, I feel.

What I meant is that the resampling is slow. What we should do is
if not is_uniform(df):
    df = df.resample(...)

always require input freq instead of trying to guess it
always resample if needed

I'd say that resampling can be done by default if freq is given. Then freq remains optional, but will be required in case the data fails the test, so that resampling can work as intended.

I think either df.index.freq must be defined or it needs to be passed, but what we should not do is to guess what the frequency of the data is.

authors: jaheba lostella

repo: awslabs/gluonts


text:
How do we obtain CLI credentials like with vanilla DCE?

e.g. in dce, the following cli command would reveal the cli credentials. I'm struggling to find out how to do the same using Sandbox Accounts for Events:
dce leases login --print-creds
(source: https://dce.readthedocs.io/en/latest/howto.html?highlight=credentials#logging-into-a-leased-account)

Sandbox Accounts for Events (SAfE) has been build for users that do not know how obtain or work with CLI credentials, so this functionality is not included. The easiest way to get credentials for your session would be to log into the AWS console via SAfE, open AWS CloudShell and run aws sts get-session-token. If you need to rely on vanilla DCE, you could also connect your local DCE CLI to the DCE backend in SAfE or deploy pure DCE only.
DCE is still a great tool in itself, it just lacks a user interface for non-developers (which might not be needed in your case).

authors: mmunem moellr

repo: awslabs/sandbox-accounts-for-events


text:
Use provided sleep_impl in aws-smithy-client::retry

Previously, aws_smithy_client was hard coded to use tokio::sleep. This change:

threads the sleep implementation into the retry controller
moves the integration test out of aws-hyper and into aws-smithy-client
takes a first pass at fixing the cargo features (cargo hack --feature-powerset passes now)

Motivation and Context

Description

Testing

Checklist

[x] I have updated CHANGELOG.md if I made changes to the smithy-rs codegen or runtime crates
[ ] I have updated aws/SDK_CHANGELOG.md if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates

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

I'm actually going to merge this as-is, then do a follow up. It ended up being a bit of a complex change that I want to review in isolation

repo: awslabs/smithy-rs


text:
Fix network retry integration test

Issue #, if available:
Fixes #1039
Description of changes:
Taken from @turan18's branch, this PR fixes the TestNetworkRetry logic.
The previous test worked strangely with iptables, and for some reason did not always process them. Additionally, the checks were not robust. So, even though it was always passing, in reality the errors were not being properly handled and thus always fell through. It also operated under the assumption that certain spans (specifically the ones associated with times binary) were fetched with background fetcher disabled, which we found to be incorrect. The setup also seemed to behave strangely on ARM machines, not catching the error and causing it to hang indefinitely. Still haven't figured out why yet.
This change fixes the logic by streamlining the read channels and only running one command, as no binaries should be expected to be fetched on container startup. This should also stop it from hanging as all buffered channel reads are now in select statements or goroutines.
This initially had issues and stayed hanging on ARM, but changing the timeout from 5 to 6 seconds seems to make it very consistent on ARM machines.
Thanks for the work done on this @turan18
Testing performed:
GO_TEST_FLAGS='-run TestNetworkRetry -count 1' make integration on ARM64 and AMD64
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

TL;DR I used testutil.LogMonitor to tie the stdout and stderr streams from sh.R to a new testreporter. This uses the same stdout and stderr that the logreporter uses, thus allowing sh.R's open pipes to be closed and the goroutines returned.
Ok, so I went back to the drawing board a bit and I think I found a solution I'm somewhat happy with. Instead of using our own goroutines that are not tied to any context or other structure, I opted to do what we previously did and just add a LogMonitor. This LogMonitor scans the given stdout and stderr readers and matches them with the writers for stdout and stderr, respectively. This fixes the issue we had previously with sh.R not properly exiting due to the pipes being left open.
I still kept the logic of not processing any of the data and just getting the raw string, though, i.e. any data from stdout = success, any data from stderr = failure. It felt a lot more elegant and removed the need to unmarshal into a json and whatnot.
This change was a comparatively significant refactor, and thus I opted to put it in its own commit so we can easily revert if needed, but I plan on squashing before we merge this.

The previous test attempted to check that both 1) reading files that are already downloaded works with no network and 2) reading files that are not already downloaded may or may not work depending on the retry policy/network interruption duration.

It's worth noting that, before changing to nerdctl run, I recall this test being fine. I was confused on why sh -c times worked before, though. Is it because with the entrypoint it would already have times loaded? But what's the guarantee there? Since as noted on ARM it did hang, which makes me wonder why that would be the case. Perhaps the image difference between architectures somehow made this a problem?

is there still value in a follow up test that verifies that the network can be interrupted after the image is downloaded?

Is this not what we're doing here though? Or do you mean fully download the image, wait for the background fetcher to finish, then run the snapshotter?

It's worth noting that, before changing to nerdctl run, I recall this test being fine. I was confused on why sh -c times worked before, though. Is it because with the entrypoint it would already have times loaded? But what's the guarantee there? Since as noted on ARM it did hang, which makes me wonder why that would be the case. Perhaps the image difference between architectures somehow made this a problem?

Yeah, the old logic was that by running the container before disabling the network, we force some amount of the image to be downloaded for sleep inf (probably span 0 which probably includes /bin/sh). We never had strong guarantees that would keep working, though.

is there still value in a follow up test that verifies that the network can be interrupted after the image is downloaded?

Is this not what we're doing here though? Or do you mean fully download the image, wait for the background fetcher to finish, then run the snapshotter?

The test now verifies that if we don't have the data we need and we have a network interruption, there will be retries until the network comes back and we can get the data.
The test that we lost is if do have the data we need, there is no network dependency and the container will work whether the network comes back or not (this is what we were trying to test with sh -c times although it didn't work reliably).
It doesn't have to be fully downloaded, but I think that makes it easy to make it more reliable. Assuming we had a way to determine that an image is fully downloaded, the test I'm imagining is:

Pull the image with the bg fetcher enabled
Wait for the image to be fully downloaded
Disable the network
run the container
Verify that the container runs successfully without requiring the network

I think it's possible. We could possibly just add something like this:
// Pull image
entrypointWithNetwork := ["sh", "-c", "times"]
sh.X(append(runSociCmd, "-d", "--rm", image, entrypointWithNetwork...)...)

// Disable network access here, or return if first test case
stdout, stderr, out := sh.R(append(runSociCmd, "-d", "--rm", image, entrypointWithNetwork...)...)) // In case any regression causes this to hang
// Setup listeners for this command

// Proceed with rest of test

There's no reasonable case for the first test to hang IMO, and the first run prefetches the required spans so the second command can then test our theory. WDYT?

LGTM. I don't think that blocks this PR, so we can defer that to a follow up issue.

Sure, will open that once this gets merged.

Squashed commits

I think it's possible. We could possibly just add something like this:

// Pull image

entrypointWithNetwork := ["sh", "-c", "times"]

sh.X(append(runSociCmd, "-d", "--rm", image, entrypointWithNetwork...)...)

// Disable network access here, or return if first test case

stdout, stderr, out := sh.R(append(runSociCmd, "-d", "--rm", image, entrypointWithNetwork...)...)) // In case any regression causes this to hang

// Setup listeners for this command

// Proceed with rest of test

There's no reasonable case for the first test to hang IMO, and the first run prefetches the required spans so the second command can then test our theory. WDYT?

Opened #1231 to track this

authors: Kern-- sondavidb

repo: awslabs/soci-snapshotter


text:
Docs update for S3 and ParameterStore starter coordinates.

This PR fixes the issue https://github.com/awspring/spring-cloud-aws/issues/524
Updated the docs to correct the S3 and ParameterStore starters maven coordinates to the following:
<dependency>
    <groupId>io.awspring.cloud</groupId>
    <artifactId>spring-cloud-aws-starter-s3</artifactId>
</dependency>
<dependency>
    <groupId>io.awspring.cloud</groupId>
    <artifactId>spring-cloud-aws-starter-parameter-store</artifactId>
</dependency>

Thanks @sivaprasadreddy!

authors: maciejwalkowiak sivaprasadreddy

repo: awspring/spring-cloud-aws


text:
Fix package.json main field.

Some JSON-LD tooling we have is using this package through rdfa and now Node.js 16+ complains about the package.json main field.  It looks like it should be index.js.  A patch release with this fix would be appreciated.

@davidlehn This should be fixed now, please let me know if you have any further issues.

authors: awwright davidlehn

repo: awwright/node-rdf

license: Unlicense


text:
Can't add package to XCode project

axmol version: 2.1.3
devices test on:
developing environments: XCode 15.4
Steps to Reproduce:

Create a new project (axmol new -p com.new.www -d ./ -l cpp Coloring -i)
Create an XCode project for the project (axmol build -p ios -a arm64 -c)
Try to add a package dependency to the project, specifically: https://github.com/tikhop/ASN1Swift
XCode stuck on "Preparing to validate..."

If I create a new random project in XCode I can add the package with no problem.

Just tested on axmol 2.1.4 and the problem persists.

I don't know how packages work in Xcode, but if they integrate into your Xcode project, then they will be gone the next time Xcode project is regenerated (e.g. after adding new source files, etc). This is not how Axmol workflow works. You should treat generated Xcode project as "readonly". You'll probably want to look into something that can be integrated from command line like CocoaPods.

Oh...
So it's not like the XCode project Cocos2d-x made where I edited it directly?

So it's not like the XCode project Cocos2d-x made where I edited it directly?

Cocos2d-x v3.17+ and V4 both use cmake, which generate the Xcode project, and Axmol also uses the cmake build system, so nothing has changed in that regard.  If you're referring to v2 of Cocos2d-x. then yes, a lot has changed.  Anything you want to add to the Xcode project would need to be done via cmake or CocoaPods.
The ASN1Swift project you linked has an example of how to add it via CocoaPods.

To expand on this: yes, you should not edit Xcode project directly, and do not add it to your source control. Basically, you want to have an easy runnable two steps setup:

Generate Xcode project - axmol build -p ios -a arm64 -c or similar.
Modify Xcode project - your custom automated step that makes the changes to the Xcode project. This could be done using CocoaPods or something else.

I was a bit wrong to say "treat generated Xcode project as "readonly"". You can certainly modify it, but it must be automated, cause you will lose changes the second that you modify CMake files, or CMake runs ZERO_CHECK task for some reason. It also hardcodes paths, so you would not be able to build that project on another machine, or if you moved your project to another folder.
Also, be aware that if you're running build in Xcode after editing CMake files (or if CMake reruns ZERO_CHECK task for some other reason), then Xcode project will be regenerated during the build, and Xcode will notice it and it will cancel the build to reload it. Then you need to execute your step 2, since your Xcode project changes will be gone, and then restart the build.

So it's not like the XCode project Cocos2d-x made where I edited it directly?

Cocos2d-x v3.17+ and V4 both use cmake, which generate the Xcode project, and Axmol also uses the cmake build system, so nothing has changed in that regard. If you're referring to v2 of Cocos2d-x. then yes, a lot has changed. Anything you want to add to the Xcode project would need to be done via cmake or CocoaPods.
The ASN1Swift project you linked has an example of how to add it via CocoaPods.

I am working with cocos 3.10 which created an XCode project when I created the project and I've been working on it directly all the time and it worked fine. I thought I could do the same with axmol.

To expand on this: yes, you should not edit Xcode project directly, and do not add it to your source control. Basically, you want to have an easy runnable two steps setup:
1. Generate Xcode project - `axmol build -p ios -a arm64 -c` or similar.

2. Modify Xcode project - your custom _automated_ step that makes the changes to the Xcode project. This could be done using CocoaPods or something else.

I was a bit wrong to say "treat generated Xcode project as "readonly"". You can certainly modify it, but it must be automated, cause you will lose changes the second that you modify CMake files, or CMake runs ZERO_CHECK task for some reason. It also hardcodes paths, so you would not be able to build that project on another machine, or if you moved your project to another folder.
Also, be aware that if you're running build in Xcode after editing CMake files (or if CMake reruns ZERO_CHECK task for some other reason), then Xcode project will be regenerated during the build, and Xcode will notice it and it will cancel the build to reload it. Then you need to execute your step 2, since your Xcode project changes will be gone, and then restart the build.

I have never worked directly with CMake. I created my project with cocos 3.10 and it created an XCode project and I've done all my work through XCode and it worked great.
Is there a way to work with axmol the same way?

I am working with cocos 3.10 which created an XCode project when I created the project and I've been working on it directly all the time and it worked fine. I thought I could do the same with axmol.

When the cmake build system was added to Cocos2d-x v3, the intention was never to use it in the way you are describing, and you would not be doing yourself any favors by attempting to continue working in this way.  The fact that it worked without issues is purely by chance.
Embracing the cmake build system should make things simpler, and less time consuming, especially if you wish to support multiple platforms for your application.
@halx99 I feel that this should be moved to the discussion section, since it's not an issue with Axmol.

authors: rh101 smilediver udirub

repo: axmolengine/axmol


text:
Enhance Docuware Connector

https://1ivy.atlassian.net/browse/MARP-967: Enhance Docuware Connector

Fix the variable syntax to make it work with LTS Ivy version
Support to put the index field with type Table

Hi @ivy-rew
Could you have a quick look at this PR since we renamed the variable of  "docuware-connector" to "docuwareConnector" & introduced a new property of "DocuWareFieldTableItem"?
Thank you so much

I think there's still something missing @ntqdinh-axonivy
the product/pom.xml must be updated in order to actually supply the contents for '@variables.yaml@' .
you'll need to add the maven-antrun invocation from the latest template to make this work
https://github.com/axonivy-market/market-product/blob/e79cb94fc737a7ea1fe12bff5d0220a0f95a5e30/MY-PRODUCT-NAME-product/pom.xml#L33

authors: ivy-rew ntqdinh-axonivy nvvi

repo: axonivy-market/docuware-connector


text:
Feature/ivyportal 16944 hide password forgotten function in specific cases le

Feature/ivyportal 16944 hide password forgotten function in specific cases le
_ unify logic
_ adapt document

Please merge

authors: chnam-axonivy nhthinh-axonivy

repo: axonivy-market/portal


text:
请问是否可以添加efm？

感谢，这个用起来很快，不知是否可以添加efm？谢谢

efm是啥？

efm-langserver，https://github.com/mattn/efm-langserver
可以配置自动格式化

好吧，刚刚看到format.nvim已经废弃了

19bbba3409b52644c376360ad5ac25de2a392470

昨天和今天测试之后我发现这个并不能提供快速的异步格式化，先把main分支revert回原来版本了，之后再dev里面配置efm吧

repo: ayamir/nvimdots


text:
🛑 Digizoo is down

In 8ff5872, Digizoo (https://www.digizoo.com.tr/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Digizoo is back up in 18c2558 after 36 minutes.

repo: aydgn/upptime


text:
Update OMVs configured to system hostname

This should do the trick... path is correct, works on a live system...

Yes. It does.
On Tue, Jul 25, 2017 at 1:40 PM, Peter notifications@github.com wrote:

@pfeerick commented on this pull request.
In package/root/usr/local/sbin/install_openmediavault.sh
https://github.com/ayufan-rock64/linux-build/pull/13#discussion_r129280567
:

@@ -67,6 +67,9 @@ xmlstarlet ed -L -u "/config/services/smb/extraoptions" -v "$(echo -e "${SMB_Opt

fix timezone
xmlstarlet ed -L -u "/config/system/time/timezone" -v "UTC" ${OMV_CONFIG_FILE}
+# fix hostname
+xmlstarlet ed -L -u "/config/system/network/dns/hostname" -v "$(hostname)" ${OMV_CONFIG_FILE}
ouch... so install_openmediavault.sh runs in the docker build? yeah,
reading the file will be better in that case ;)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ayufan-rock64/linux-build/pull/13#discussion_r129280567,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACTpQTUuiBdOyxVvv5FJ0Q3uUE0xh9Euks5sRdQqgaJpZM4Oibq3
.

authors: ayufan pfeerick


text:
Is it possible to not override the default video insert button?

Hello,
I would like to have two options to insert videos. One giving the URL, and another uploading a local video file.
Without the videoHandler specified, when I hit the 'video' button from the ngx-quill editor, a popup shows up asking for an URL. It is not pretty, but I would like to preserve this functionality as well.

With the videoHandler specified, the editor asks for an video file, the handler code uploads it and returns the URL which is embedded into the document. This works wonderfully.

Could it be possible to bind the video upload functionality to a different custom button?

I need the same feature!


text:
What's the idea behind the custom dispatcher and if there's an built-in one?

It may be a very stupid question, but i'm struggling to learn... and I've no one but you.
It all begins with me trying to learn a simple something, which's: HOW CAN I CREATE A CUSTOM EVENT.
I wanted to just, for example: When a timer finishes... make a callback function for people using my script or myself to do their job. like this:
myTimer.addEventListener('timerFinished', function (e) {
   myDiv.html('The timer has finished.');
});

Since this time i'm reading all world articles and books, and i get confused... i read about observer pattern and event emitter and dispatcher: AND I FEEL LIKE ALL OF THEM ARE THE SAME THING!
And finally i get you, your code is amazing and explained very very well, i understand it and i was able to use it and achieve my goal.
But my question, and please help me to understand this, please...
What is the different between your dispatcher, other custom made dispatcher like yours and emitters. AND THIS THING:
https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Creating_and_triggering_events
They are talking about something that's built-in! built in JS called "dispatchEvent"! Like it's an official way to dispatch and create custom event, actually the article title is:

Creating and triggering events

Thank you for your amazing work, and i'm very sorry to bring my confusion to your time and mind.

If there's any books or resources  for learning this, I wish your provide my with them.
Thanks. <3

Check this also, i was able to achieve a custom event using the built-in dispatcher:
var element = document;

element.addEventListener("OurSuperEvent", function (e) {
    console.log("The custom data of the event is : ", e.detail);
    console.log("Event is : ",e);
}, false);

var myData = {
    id: 1,
    name: "An imaginary name",
    customProperty:"I need to know this string when the event is dispatched",
    moreData: [1,2,4,5,6,7]
};

var event = new CustomEvent("OurSuperEvent", { detail: myData });

element.dispatchEvent(event);

Outputs:
The custom data of the event is :  {id: 1, name: "An imaginary name", customProperty: "I need to know this string when the event is dispatched", moreData: Array(6)}

Event is :  CustomEvent {isTrusted: false, detail: {…}, type: "OurSuperEvent", target: document, currentTarget: document, …}

It may be a very stupid question, but i'm struggling to learn... and I've no one but you.

It's not a stupid question. As far as I can remember now, the main points for custom event dispatcher were:

Restrict custom event dispatcher to a specific list of events (and throw if disallowed event name is used), so that consumers of your custom dispatcher can notice misspelled events in the code early;

Add additional event helpers (e.g. once and offAll);

Reduce overhead of CustomEvent - dispatching events through DOM has its own performance drawbacks: first you create event in Javascript and call Javascript function to pass the event, event is dispatched then to C++, and then it goes back to Javascript to call event handlers, you can easily see the difference with JSPerf or something;

Custom Events are tied to the DOM, but this implementation was supposed to be used in DOM-less environments too (e.g Node, Service Workers etc.).

Hope this helps.

authors: azasypkin institution-site

repo: azasypkin/event-dispatcher

license: mit


text:
Feature/add onroute notifications

+1 I dig this in the directions list

authors: CloudNiner flibbertigibbet

repo: azavea/nih-wayfinding


text:
Remove Tile Server from Application Server Task Definition

Tiles are no longer served from the application server. This will free up the required memory for the API service I think.

Where'd you pull this from? Looking at the source, these container definitions don't line up. app-server was replaced with api-server, and I don't see any container definitions for tile-server within any of the task definitions other than tile-server.

Huh, you're right it's not in prod any longer -- I took the screenshot this morning, but now I can't find it in the console anywhere.
I agree it doesn't line up with what is in our deployment code -- which I thought was a little odd. Maybe there was an old task definition hanging around because of our placement issues.

authors: hectcastro notthatbreezy

repo: azavea/raster-foundry


text:
Add controls for switching between light/dark basemaps

Related to #823 - controls need to be added in order to switch between light and dark maps so that when dark image overlays are added to the map users can still have nice looking label overlays.

Closed by #889

authors: alkamin notthatbreezy


text:
🛑 Sukri Online is down

In de9330f, Sukri Online (https://discord-aklx.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sukri Online is back up in b7073d9 after 10 minutes.

repo: azrielbsi/monitor


text:
Payload libinject.go

Hello.
Can you explain where to save the libinject.go on Termux ? And how to excecute it with brainfuck , please ?
https://github.com/aztecrabbit/libinject/blob/66586ad1041b5c9f7e49161a6c71b11495bf24f6/libinject.go?fbclid=IwAR1QOfpQk-boZE9iioSjjVLzVW2nDchMnXJh81QcXN_sNIkU4FufJlg8k9k#L210-L222

libinject.go is library only, that lib is used by this app. You can change Inject Type to 0 and Inject Payload to like in any injector app (https://github.com/aztecrabbit/libinject/blob/66586ad1041b5c9f7e49161a6c71b11495bf24f6/libinject.go?fbclid=IwAR1QOfpQk-boZE9iioSjjVLzVW2nDchMnXJh81QcXN_sNIkU4FufJlg8k9k#L210-L222) if you want to use direct or http proxy method with payload.

authors: aztecrabbit ingnelson

repo: aztecrabbit/brainfuck-psiphon-pro-go


text:
Create an Azure AD group for the level0 developers

Current version of the launchpad only authorize the developer who created the launchpad to deploy landing zones.
It would be great to have a security group to be able to add more developers contributing to the same launchpad environment.

Supported only in the launchad_opensource


text:
synced timeout to wall clock

I changed the setInterval to setTimeout with a proper timeout value.
My atom-clock changed immediately when my phone and laptop changed.  Actually, it changed a bit earlier than the laptop, which is hard to understand.  The chromebook code for the task bar is apparently worse than mine.  (grin)
This is only tested for 60 seconds, 50 seconds, and one second.  It will still function for odd times like 50 seconds as well as the old setInterval method, but that doesn't make much sense.  Maybe the interval config should be changed to a selection of 1 sec or 60 secs and a setInterval would run for 1 sec and setTimeout for 60.

Ok, I see what you've done here. It's quite a nice fix, since with the setInterval it might happen that the clock is always ~1 minute (let's say, 59 seconds if you're very unlucky) late compared to the wall clock.
My only concern here is, because of the nature of the modulus operator the user will always have a variable refresh time. May it rise any problem in your opinion?
Cheers!

the user will always have a variable refresh time.

Actually it will be variable only the first time.  Then it is almost
exactly every minute.
On Mon, Nov 23, 2015 at 10:02 AM, Antonio Bevilacqua <
notifications@github.com> wrote:

Ok, I see what you've done here. It's quite a nice fix, since with the
setInterval it might happen that the clock is always ~1 minute (let's
say, 59 seconds if you're very unlucky) late compared to the wall clock.
My only concern here is, because of the nature of the modulus operator the
user will always have a variable refresh time. May it rise any problem in
your opinion?
Cheers!
—
Reply to this email directly or view it on GitHub
https://github.com/b3by/atom-clock/pull/4#issuecomment-159013160.