text:
Error in DynamoDb Client After upgrading to ASP.NET Core 8

Describe the bug
Message":"Value cannot be null. (Parameter 'path1')
at System.ArgumentNullException.Throw(String paramName)
at System.IO.Path.Combine(String path1, String path2)
at Amazon.Internal.RegionEndpointProviderV3.GetEndpointJsonSourceStream()
at Amazon.Internal.RegionEndpointProviderV3..ctor()
at Amazon.RegionEndpoint.get_RegionEndpointProvider()
at Amazon.RegionEndpoint.get_InternedRegionEndpoint()
at Amazon.RegionEndpoint.GetEndpointForService(String serviceName, GetEndpointForServiceOptions options)
at Amazon.Runtime.Internal.Auth.AWS4Signer.DetermineSigningRegion(IClientConfig clientConfig, String serviceName, RegionEndpoint alternateEndpoint, IRequest request)
at Amazon.Runtime.Internal.Auth.AWS4Signer.SignRequest(IRequest request, IClientConfig clientConfig, RequestMetrics metrics, String awsAccessKeyId, String awsSecretAccessKey)
at Amazon.Runtime.Internal.Auth.AWS4Signer.Sign(IRequest request, IClientConfig clientConfig, RequestMetrics metrics, String awsAccessKeyId, String awsSecretAccessKey)
at Amazon.Runtime.Internal.Auth.AWS4Signer.Sign(IRequest request, IClientConfig clientConfig, RequestMetrics metrics, ImmutableCredentials credentials)
at Amazon.Runtime.Internal.Auth.AbstractAWSSigner.SignAsync(IRequest request, IClientConfig clientConfig, RequestMetrics metrics, ImmutableCredentials credentials, CancellationToken token)
at Amazon.Runtime.Internal.Signer.SignRequestAsync(IRequestContext requestContext)
at Amazon.Runtime.Internal.Signer.PreInvokeAsync(IExecutionContext executionContext)
at Amazon.Runtime.Internal.Signer.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CredentialsRetriever.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.ErrorCallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
at Amazon.Runtime.Internal.MetricsHandler.InvokeAsync[T](IExecutionContext executionContext)
at TorchLake.Infrastructure.StateStore.Aws.AwsDynamoDbStateStoreClient._SaveStateAsync[TValue](String storeName, String key, TValue value, IReadOnlyDictionary2 metadata, CancellationToken cancellationToken)    at TorchLake.Infrastructure.StateStore.Aws.AwsDynamoDbStateStoreClient.SaveStateAsync[TValue](String storeName, String key, TValue value, StateOptions stateOptions, IReadOnlyDictionary2 metadata, CancellationToken cancellationToken)
This exception is exactly the same as this issue.  The only difference is 3110 is a Kinesis client and this is a DynamoDb client.
Expected Behavior
Validate that path1 is not null before it tries to combine with path2
Current Behavior
It isn't correctly validating path1.
Reproduction Steps
Use a test console application docker build it and deploy it to EKS.  This ONLY happens on EKS.  I have a Windows and a Mac development machine that I run locally and this doesn't happen locally.
Possible Solution
Validate that the code works correctly in Linux, specifically in a docker container running in EKS
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
ASP.NET 8.0.100
AWSSDK.DynamoDBv2 3.7.300.7"
Targeted .NET Platform
.NET 8
Operating System and version
AmazonLinux

Thanks for reporting this, we'll keep the investigation on #3110 (since it's the same problem).

authors: aaronolds dscpinheiro

repo: aws/aws-sdk-net


text:
chore: Prepare release 3.2.0

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

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 2800c6274437a7360239ef347b528c21c8ad0920
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: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 2800c6274437a7360239ef347b528c21c8ad0920
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: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 44ce34c42aee9bc55b6b37ce1b8f9fa606861684
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: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 44ce34c42aee9bc55b6b37ce1b8f9fa606861684
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: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 44ce34c42aee9bc55b6b37ce1b8f9fa606861684
Result: SUCCEEDED
Build Logs (available for 30 days)

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

source: gharchive/pull-request

authors: kukushking malachi-constant

repo: aws/aws-sdk-pandas

license_type: permissive

license_source: github-api


text:
Helm charts with no files.txt

I'd like to discourage use of this except for the values.yaml and Chart.yaml file. We should be patching everything else. There are a couple cases where we are running this on the README, but those don't matter.
Closes: https://github.com/aws/eks-anywhere-packages/issues/193

/lgtm

/approve

/approve

authors: TerryHowe jonahjon

repo: aws/eks-anywhere-build-tooling


text:
Run helm-docs in the middle of the helm build to update the README of the helm chart

We modify values.yaml and patch the helm chart without running helm-docs to regenerate the he README if there was one

Not worth it

source: gharchive/issue

repo: aws/eks-anywhere-packages


text:
EKS-A Bare Metal install fails when the node is turned off already

We have some old HW that we are trying to use for EKS-A Bare Metal testing.
For one of these servers impitool returns with an error if one tries to turn it off while it is already off:
# ipmitool -I lanplus -U root -P $(cat ~/bmc_pwd.txt) -H kls004-m power status
Chassis Power is off
# ipmitool -I lanplus -U root -P $(cat ~/bmc_pwd.txt) -H kls004-m power off
Set Chassis Power Control to Down/Off failed: Command not supported in present state
# echo $?
1

While with other servers impitool returns with 0:
# ipmitool -I lanplus -U root -P $(cat ~/bmc_pwd.txt) -H kls014-m power status
Chassis Power is off
# ipmitool -I lanplus -U root -P $(cat ~/bmc_pwd.txt) -H kls014-m power off
Chassis Power Control: Down/Off
# echo $?
0

Unfortunately, EKS-A installer does not handle this error as the bmt fails in such case:
# kubectl get bmt -n eksa-system
NAME                                                                       AGE
eks-a-bm-poc-control-plane-template-1664982789238-l542m-provision-task-0   8m43s
# kubectl get bmt eks-a-bm-poc-control-plane-template-1664982789238-l542m-provision-task-0 -n eksa-system -o yaml
apiVersion: bmc.tinkerbell.org/v1alpha1
kind: BMCTask
metadata:
  creationTimestamp: "2022-10-05T15:13:12Z"
  generation: 1
  managedFields:
  - apiVersion: bmc.tinkerbell.org/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:ownerReferences:
          .: {}
          k:{"uid":"220f1e44-017a-4635-9a8d-373999372c9b"}: {}
      f:spec:
        .: {}
        f:connection:
          .: {}
          f:authSecretRef:
            .: {}
            f:name: {}
            f:namespace: {}
          f:host: {}
          f:insecureTLS: {}
          f:port: {}
        f:task:
          .: {}
          f:powerAction: {}
    manager: manager
    operation: Update
    time: "2022-10-05T15:13:12Z"
  - apiVersion: bmc.tinkerbell.org/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:status:
        .: {}
        f:conditions: {}
        f:startTime: {}
    manager: manager
    operation: Update
    subresource: status
    time: "2022-10-05T15:13:14Z"
  name: eks-a-bm-poc-control-plane-template-1664982789238-l542m-provision-task-0
  namespace: eksa-system
  ownerReferences:
  - apiVersion: bmc.tinkerbell.org/v1alpha1
    controller: true
    kind: BMCJob
    name: eks-a-bm-poc-control-plane-template-1664982789238-l542m-provision
    uid: 220f1e44-017a-4635-9a8d-373999372c9b
  resourceVersion: "1955"
  uid: d25c080c-121f-4aa2-896b-30799591260a
spec:
  connection:
    authSecretRef:
      name: bmc-kls004-auth
      namespace: eksa-system
    host: REMOVED
    insecureTLS: true
    port: 0
  task:
    powerAction: "off"
status:
  conditions:
  - message: "failed to perform PowerAction: 2 errors occurred:\n\t* provider: ipmitool:
      Set Chassis Power Control to Down/Off failed: Command not supported in present
      state: exit status 1: Set Chassis Power Control to Down/Off failed: Command
      not supported in present state\n\n\t* failed to set power state\n\n"
    status: "True"
    type: Failed
  startTime: "2022-10-05T15:13:14Z"

If possible, please allow power off to fail when the node is off already.

Thanks for reaching out to us! We will have an internal discussion to see if it can be supported.

Hi @Cajga this looks like a specific use case on older hardware.
Could you please share the hardware details, like the bmc ipmi version? So we can investigate a bit more.

@Cajga We've had quite a number of updates since the issue was originally raised. Are you able to retest to see if this is still an issue?

No response. Closing.

authors: Cajga chrisdoherty4 pokearu vincentni

repo: aws/eks-anywhere


text:
TinkerbellTemplateConfig type for defining Tinkerbell workflow

Description of changes:
The changes involve adding a new type TinkerbellTemplateConfig. This type is used to define Tinkerbell workflow tasks and actions.
Key changes:

Adding new TinkerbellTemplateConfig type
Modifying TinkerbellMachineConfig to use a templateRef instead of large string.
Parsing the bundle during to generate clusterconfig to populate default images.
Updating marshaller and CRD config files

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

/lgtm

authors: pokearu ptrivedi


text:
[release-0.11] Changes to enable kube-rbac-proxy on CloudStack cluster controller's metrics port

Issue #, if available:
Description of changes:
Manual cherrypick of https://github.com/aws/eks-anywhere/pull/2888 into release-0.11
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.

/approve

authors: maxdrib vivek-koppuru


text:
Update optional steps for create cluster on all providers

Issue #, if available:
https://github.com/aws/eks-anywhere-internal/issues/1668
Description of changes:
Update optional steps for create cluster on all providers.
Testing (if applicable):

live docs testing + preview

Documentation added/planned (if applicable):

yes

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

/lgtm

/lgtm

/approve

/cherry-pick release-0.17

authors: chrisnegus cxbrowne1207 mitalipaygude


text:
Skipping the kubernetes-csi/external-snapshotter images to update

Issue #, if available:
Description of changes:
Skipping to update the images. for mpvarma/update-checking-csi-snapshotter as this image is bumped but not published to the external repo.
Error updating image digests: ImageNotFoundException: The image with imageId {imageDigest:'null', imageTag:'v8.2.0-eks-1-29-30'} does not exist within the repository with name 'kubernetes-csi/external-snapshotter/snapshot-validation-webhook' in the registry with id '316434458148'

https://prow.eks.amazonaws.com/view/s3/prowdataclusterstack-316434458-prowbucket7c73355c-1n9f9v93wpjcm/logs/dev-release-1-29-postsubmit/1869869112969138176#2:build-container-build-log.txt%3A8080
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/approved
/unhold

/approved

/lgtm

/approved

authors: varma-maryala vineeth-bandi

repo: aws/eks-distro-build-tooling


text:
Reuse golang rpm downloads instead of redownloading

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.

/hold

/unhold


text:
Add Go version trigger in kubernetes Unit tests

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve

/lgtm

repo: aws/eks-distro-prow-jobs


text:
Bumped production release number for 1.25

Issue #2265
New development release for 1.25
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
/unhold

repo: aws/eks-distro


text:
String Enum values compile to the key rather than source value

Describe the bug
In typescript, we can represent string enums like so:
export enum EnvironmentName {
  DEV = 'dev',
  QA = 'qa',
  FOO = 'bar'
}

However, in all languages besides js, jsii compiles these so that the key name is used. For instance, python output looks like:
@jsii.enum(jsii_type="@example/my-package.EnvironmentName")
class EnvironmentName(enum.Enum):
    DEV = "DEV"
    QA = "QA"
    FOO = "FOO"

When using the enum as a type, this doesn't matter, as the literal value is unimportant. But when outputting a string, Python developers are now outputting FOO whereas TS/JS users of the same construct output bar. This breaks interoperability.
Expected Behavior
The string representation of an enum value in all languages should match the source code. As noted in the jsii design tenants:

jsii applications behave identically regardless of the language they are written in. It favors correctness over performance.
Unsupported idioms will cause a compile-time error to be emitted.
When prohibiting an idiom, jsii strives to provide an error message that gives the user insight into why the pattern cannot be supported.

Applications should behave identically, and if that is not possible, there should be a compiler error for string enums where the key and value do not match.
Current Behavior
An application which uses runtime validation of enum values will fail in languages other than JS. For instance:
export const validateEnv = (env: EnvironmentName) => {
  if (Object.values(EnvironmentName).includes(env)) {
    throw new TypeError(`Value "${env}" is not a valid environment name.`);
  }
}

I believe this is because the JS assembly is used when calling Object.values(), and the value passed in doesn't match JS values due to the serialization differences.
Reproduction Steps

Create a construct library which uses a string enum's values inside functional code.
Publish package to NPM and another supported target.
Import the package in the target language and call the function.
Observe output.

Possible Solution
Rework how JSII models string enum values. Not sure how complicated this is, but it seems important for correctness.
Additional Information/Context
No response
SDK version used
jsii=5.2.8; jsii-pacmak=1.89.0
Environment details (OS name and version, etc.)
MacOS 11.7.10

Not entirely sure about the implications here. We might need to enforce that always enum keys == value

authors: mlkirkpatrick mrgrain

repo: aws/jsii


text:
feat: Adding CEL validation for the nodepool.spec.disruption

Fixes #N/A
Description

Adding CEL validation in the effort of moving away from webhook validation.
https://github.com/aws/karpenter-core/issues/103

How was this change tested?

make test

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

Pull Request Test Coverage Report for Build 6385070659

0 of 0   changed or added relevant lines in 0 files are covered.
10 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.09%) to 81.761%

Files with Coverage Reduction
New Missed Lines
%

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

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

pkg/controllers/deprovisioning/pdblimits.go
6
76.47%

Totals

Change from base Build 6382807011:
-0.09%

Covered Lines:
8903

Relevant Lines:
10889

💛  - Coveralls

authors: coveralls engedaam

repo: aws/karpenter-core


text:
Provisioner should default to amd64 if kubernetes.io/arch is not set under requirements

Version

Karpenter: v0.16.0

Kubernetes: v1.23.7
Expected Behavior

Using the default provisioner in the docs, I expect my non-multi-arch containers to run.
Actual Behavior

Karpenter is launching Graviton nodes, ie c6g and t4g nodes
Steps to Reproduce the Problem

Resource Specs and Logs

I'd argue that the default should be configurable.

I believe that if no arch is added to the provisioner, it will do amd64 only.
but if you are using a provisioner, you choose what arch you want to support.
can you share it @aaroniscode  ?

@sbkg0002 a default is a default... it's what it is if nothing is provided.
and arch is entirely customisable

authors: FernandoMiguel aaroniscode sbkg0002

repo: aws/karpenter


text:
chore: Improve Issue Templates

Fixes #
Description
We are currently using the old issue template markdown experience. This experience can be greatly improved by migrating to the new YAML-based issue templates that Github has introduced.
How was this change tested?

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

Release Note

None

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

Any way to preview this somewhere?

Any way to preview this somewhere?

You can view the file directly to see what the form will look like. Beyond that, there isn't really a way to model the whole UI flow of clicking New Issue and selecting the issue type, but that should stay consistent with before.

Any way to preview this somewhere?

You can view the file directly to see what the form will look like. Beyond that, there isn't really a way to model the whole UI flow of clicking New Issue and selecting the issue type, but that should stay consistent with before.

Ah, found it, thanks!

authors: jonathan-innis tzneal


text:
2024-10-10_01-35-07_master-next_s2n

Automatically created.

Backport failed for kirkstone-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin kirkstone-next
git worktree add -d .worktree/backport-9868-to-kirkstone-next origin/kirkstone-next
cd .worktree/backport-9868-to-kirkstone-next
git switch --create backport-9868-to-kirkstone-next
git cherry-pick -x 741f4e7480af2ec0dddad934225ade1e81b43c6f

Backport failed for scarthgap-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin scarthgap-next
git worktree add -d .worktree/backport-9868-to-scarthgap-next origin/scarthgap-next
cd .worktree/backport-9868-to-scarthgap-next
git switch --create backport-9868-to-scarthgap-next
git cherry-pick -x 741f4e7480af2ec0dddad934225ade1e81b43c6f

Backport failed for styhead-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin styhead-next
git worktree add -d .worktree/backport-9868-to-styhead-next origin/styhead-next
cd .worktree/backport-9868-to-styhead-next
git switch --create backport-9868-to-styhead-next
git cherry-pick -x 741f4e7480af2ec0dddad934225ade1e81b43c6f

license: MIT


text:
KeyError: 'estimator'

Hello Innixma,
I tried with the pre-release version and by getting rid of the searcher parameter, unfortunately I still get the "KeyError: 'estimator'" error. Here is my updated notebook: https://github.com/ClemPalf/SageMaker-Inventory-monitoring/blob/main/2)%20Model_choice_with_autogluon.ipynb
Cheers,
Clem
Ps: I tried with GPU-equipped instances but always ended up with workers from the data logger dying due to insufficient shared memory (I was using a ml.g4dn.xlarge). Do you have any tips on how to raise the shared memory limit on sagemaker notebook instances?
Originally posted by @ClemPalf in https://github.com/awslabs/autogluon/issues/1474#issuecomment-1009746515

Hi Clem,
I've tried to reproduce this issue on 1. a cpu ec2 instance 2. a gpu ec2 instance 3. a sagemaker cpu notebook, and I got no error on all of them. I cloned your repo, and hence was using the exact same data. On the sagemaker notebook, I directly cloned your repo and ran your example notebook. Maybe consider starting a new notebook and try again?
Regarding the sagemaker shared memory issue, it seems like there's no way to manipulate that and it is restricted to 64 megabytes. I would recommend launch up a gpu ec2 instance yourself (image classification with cpu is super slow).

Indeed, it is working fine now...
Sorry for the inconvenience! I really don't know what went wrong the first time.

authors: ClemPalf yinweisu

repo: awslabs/autogluon


text:
Raml examples fail on create with NullPointerException

Copy/pasted the raml examples and am getting the following error when attempting to create an api.
./aws-api-import.sh -t --create /tmp/schema.raml
2016-02-05 10:52:30,268 INFO - Using API Gateway endpoint https://apigateway.us-west-2.amazonaws.com
2016-02-05 10:52:32,302 INFO - Attempting to create API from RAML definition. RAML file: /tmp/schema.raml
2016-02-05 10:52:32,305 ERROR - Error importing API definition
java.lang.NullPointerException
   at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1025)
   at org.apache.commons.io.IOUtils.copy(IOUtils.java:999)
   at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:218)
   at org.raml.parser.utils.StreamUtils.reader(StreamUtils.java:45)
   at org.raml.parser.visitor.YamlDocumentBuilder.build(YamlDocumentBuilder.java:102)
   at org.raml.parser.visitor.YamlDocumentBuilder.build(YamlDocumentBuilder.java:78)
   at com.amazonaws.service.apigateway.importer.impl.ApiGatewayRamlFileImporter.parse(ApiGatewayRamlFileImporter.java:73)
   at com.amazonaws.service.apigateway.importer.impl.ApiGatewayRamlFileImporter.importApi(ApiGatewayRamlFileImporter.java:47)
   at com.amazonaws.service.apigateway.importer.ApiImporterMain.importRaml(ApiImporterMain.java:171)
   at com.amazonaws.service.apigateway.importer.ApiImporterMain.execute(ApiImporterMain.java:141)
   at com.amazonaws.service.apigateway.importer.ApiImporterMain.main(ApiImporterMain.java:83)

Could be an issue with the input file, possibly permissions. That's what the stack trace seems to indicate.

Yeah, the input is the raml file from the aws-apigateway-importer examples, so I'm stuck on what format is required if not this.

@sophieher it doesn't work with absolute path for some reason.
% cp tst/resources/raml/example.raml /tmp/example.raml
% ./aws-api-import.sh -r ap-northeast-1 -c /tmp/example.raml
2016-03-17 13:43:00,268 INFO - Using API Gateway endpoint https://apigateway.ap-northeast-1.amazonaws.com
2016-03-17 13:43:02,459 INFO - Attempting to create API from RAML definition. RAML file: /tmp/example.raml
2016-03-17 13:43:02,469 ERROR - Error importing API definition
java.lang.NullPointerException
	at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792)

% ./aws-api-import.sh -r ap-northeast-1 -c tst/resources/raml/example.raml
2016-03-17 13:43:12,915 INFO - Using API Gateway endpoint https://apigateway.ap-northeast-1.amazonaws.com
2016-03-17 13:43:14,398 INFO - Attempting to create API from RAML definition. RAML file: tst/resources/raml/example.raml
2016-03-17 13:43:14,617 INFO - Creating API with name Example API

raml-java-parser doesn't like absolute path. See https://github.com/raml-org/raml-java-parser/issues/74

interesting. Thanks @yyamano for the explanation. :+1:

authors: jackrk sophieher yyamano

repo: awslabs/aws-apigateway-importer

license_source: bigquery


text:
Wipe for failed init

Re-opening of PR 449 as a draft pull request. Updates proof of aws_array_list_init_dynamic and aws_priority_queue_init_dynamic to check for wiped structures in failure cases.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@danielsn @ColdenCullen @feliperodri

https://github.com/awslabs/aws-c-common/pull/453 is merged

@tegansiobhan CBMC reports **** WARNING: no body for function aws_array_list_is_wiped -- is this expected, or is there a call left over for a function that should no longer exist?

Looks like this just needs a clang-format run

@danielsn you're review is blocking this, whatchu thinking?

authors: ColdenCullen graebm tautschnig tegansiobhan

repo: awslabs/aws-c-common


text:
chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

AWS CodeBuild CI Report

CodeBuild project: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: 546574e6c6b7c5e355438bd20ed54a8b9e2dd6c8
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: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: 0673d127fe0b0cff3416ca870c56dfbbb74bd7ac
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: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: 79b0997788fe7a91811b4e9852d51d297c560932
Result: SUCCEEDED
Build Logs (available for 30 days)

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

repo: awslabs/aws-ddk


text:
Instructions to create amscli container image

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

Hello @n1t1nv3rma   Thanks for your earlier comment. I have updated the PR accordingly. Please help to review.

repo: awslabs/aws-managed-services


text:
Subtitles and wait operators for human in the loop subtitle workflow

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

Moved to #239

repo: awslabs/aws-media-insights-engine


text:
Allow for Proxy Configuration

Describe the feature
Allow connecting through a proxy server and configure proxy server settings (proxy host, port, and username/password).
Is your Feature Request related to a problem?
Our org is behind a proxy and this feature will allow us to use aws kotlin sdk
Proposed Solution
No response
Describe alternative solutions or features you've considered
AWS Java SDK support proxy configuration.
Acknowledge

[X] I may be able to implement this feature request

AWS Kotlin SDK version used
v0.13.1-beta
Platform (JVM/JS/Native)
JVM
Operating System and version
Linux

Hi @wasifaleem, thanks for your feature request.
We have existing issue smithy-kotlin#494 to track adding proxy support and configuration. Please feel free to add a 👍 reaction to that issue to help us prioritize.
Resolving in favor of smithy-kotlin#494.

authors: ianbotsf wasifaleem

repo: awslabs/aws-sdk-kotlin


text:
New Pattern: aws-lambda-sqs

Add your +1 👍  to help us prioritize
Overview:
This AWS Solutions Construct implements an AWS Lambda function connected to an Amazon SQS queue.
User provided props for the construct:

Either an existing instance of Lambda Function or the lambda.FunctionProps to deploy a new Lambda Function.
Optional sqs.QueueProps to override the default SQS queue props.
Optional flag to deploy the dead-letter queue.
Optional sqs.QueueProps to override the default dead-letter queue props.
Optional Maximum receives count (number of times that a message can be received before being sent to a dead-letter queue)

Default settings
Out of the box implementation of the Construct without any override will set the following defaults:
Amazon SQS Queue

Deploy SQS dead-letter queue for the source SQS Queue
Enable server-side encryption for source SQS Queue using AWS Managed KMS Key

AWS Lambda Function

Configure least privilege access IAM role for Lambda function
Enable reusing connections with Keep-Alive for NodeJs Lambda function

Released aws-lambda-sqs pattern in v1.52.0

repo: awslabs/aws-solutions-constructs


text:
chore(release): 1.132.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 6134ec6e3b94a34c3656c4264220e14338f5fd66
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: 6134ec6e3b94a34c3656c4264220e14338f5fd66
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: 220ba542f7c0395ea2563248f9e291e98fa7b77a
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: 220ba542f7c0395ea2563248f9e291e98fa7b77a
Result: SUCCEEDED
Build Logs (available for 30 days)

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


text:
chore(merge-back): 2.14.0

See CHANGELOG

AWS CodeBuild CI Report

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

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


text:
main branch

Let's get a main branch going if we could. this takes 2 minutes
https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx

And this manual will update all forks, local clones, scripts on the CI/CD servers and other related stuff in the some miracle way?

No not at all, just thought it would be great to get the convo started.
I was going to use my existing pre commit hooks to catch such wording with this tool.. then I also realized I'm referencing the master branch in my pre commit hooks.
I'm certainly not saying to blow away master and break everything so I apologize for being so vague initially

authors: jamesbrink vladimir-poleh

repo: awslabs/git-secrets


text:
DeepAR loss computed on context sequence ?

In DeepARTrainingNetwork, why is the loss computed on the context sequence as well ?
https://github.com/awslabs/gluon-ts/blob/02de6f308b4e6835fbbd30d728c61391f68fd2f3/src/gluonts/model/deepar/_network.py#L447-L458
Shouldn't it be computed only on future_target ?

Nevermind, this is actually mentioned in the paper (section 3.2), I was a little bit confused since other models such as the Transformer only use the future part.
Were there any experiements done wrt which way is better ?

repo: awslabs/gluon-ts


text:
controlsToDisable does not disable per region

Describe the bug
Security Hub docco recommends disabling SH controls that are assessing global services to reduce noise and cost.
https://docs.aws.amazon.com/securityhub/latest/userguide/controls-to-disable.html
LZA, which doesn't support SH Central Configuration, does not appear to provide a way to disable specific controls and deploy that configuration to a region.
To Reproduce
I've attempted this in a couple of ways but it appears I'm assuming I would need to "deploy" the standard to specific regions, one with controlsToDisable populated.
standards:
    - name: AWS Foundational Security Best Practices v1.0.0
      deploymentTargets:
      regions:
        - ap-southeast-2
      enable: true
      controlsToDisable: []
    - name: AWS Foundational Security Best Practices v1.0.0
      deploymentTargets:
      regions:
        - us-east-1
      enable: true
      controlsToDisable:
        - IAM.4
        - IAM.5

Expected behavior
With the config above I expect IAM.4 and IAM.5 to be disabled in us-east-1 only. The result of the above config is the controls are disabled in both regions.
Please complete the following information about the solution:

[x] Version: 1.6.1

To get the version of the solution, you can look at the description of the created AWS CloudFormation stack used to install the LZA (AWSAccelerator-InstallerStack). For example, "(SO0199) Landing Zone Accelerator on AWS. Version 1.5.1.". If the description does not contain the version information, you can look at the Parameters of the stack for the RepositoryBranchName as that should contain the version number.

[x] Region: ap-southeast-2, us-east-1
[x] Was the solution modified from the version published on this repository? No
[x] If the answer to the previous question was yes, are the changes available on GitHub?
[x] Have you checked your service quotas for the services this solution uses? Yes
[x] Were there any errors in the CloudWatch Logs?

Additional context
Both SH lambda logs showed the correct entries for disabling the controls. Albiet in both regions.

Hi @mongrol ! Thank you for utilizing the Landing Zone Accelerator on AWS solution. I have filed a feature request to help track exceptions around the global services (IAM, Route53, etc..) so that these resources aren't duplicated across multi-region configurations. If you have any questions or concerns in the meantime, please do not hesitate to ask.

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


text:
Update go dependencies

Issue #, if available: N/A
Description of changes:
Ran go get -u ./... && 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.

Will merge this and add these files to the triggers for integ tests in a followup pr.


text:
Documentation on edit payload format

While the demo UI is a great resource for getting a sense of the payload format, there's some things notably missing: format/quality, sharpen, blur, etc... I'm wondering if there's some more comprehensive documentation I'm missing?

@dzucconi Thanks for contacting us. As Serverless Image Handler is using sharp, you can visit sharp website to see what options are available.
Every sharp function can be key inside the edit payload, and you can put value of the key. For example,
{
  "bucket": "YOUR_BUCKET",
  "key": "YOUR_IMAGE.jpg",
  "edits": {
    "grayscale": true,
    "toFormat": "png",
    "png": {
      "quality": 50
    }
  }
}

This would return gray quality 50 png image of the original image.

Thanks!

authors: beomseoklee dzucconi

repo: awslabs/serverless-image-handler


text:
Update smithy client builder docs for resiliency config setters

❤ For Lucio ❤
update: retry config setter docs
update: timeout config setter docs
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

rip no blue check mark 😢

authors: LucioFranco Velfi

repo: awslabs/smithy-rs


text:
اضافة جديدة

قمت بتطوير اضافة لكليجا
أرجو الاطلاع عليها ان كانت مناسبة للرفع
http://henurl.com/kleeja-plg.zip

There is an error in zip file . Can not open it

هل بامكانك رفع الشفرة الى غيت هب ؟

هناك خطا بملف الارشيف، اعد ضغط الملفات وارفعه

This is a malware.

@nicolasnoble Thanks.
you are right, I'm on MacOS and it's only appears as corrupted archive.
https://www.virustotal.com/#/file/2697c9e38d1e081c8fa5f07db8e1500c0f90dca4f408e1b582f8f00c8ade9c52/detection

authors: MitanOmar abdumu nicolasnoble rikojilani

repo: awssat/kleeja


text:
Add IORING_SETUP_SQPOLL_SHARED_POLLTHREAD (feature request)

Background
Cleanup of discussion in #324
It's currently possible to use a single SQPOLL kernel thread by specifying a previously existing io_uring instances fd with wq_fd and setting IORING_SETUP_ATTACH_WQ.
For some (most?) use cases, one only wants a single polling kernel thread as multiple io_uring instances are commonly created by users of a framework (up to NCPU:s or sometimes even a few more...).
For robustness, I simply create a minimal SQPOLL-enabled io_uring instance the first time a user of the framework asks for SQPOLL, and then subsequently uses that  minimal io_uring instance ring fd for wq_fd for the rest of the io_urings as needed - this works fine, but it would be nice to avoid the minimal io_uring instance (or otherwise bookkeeping to keep track of valid instances), but doesn't work easily when there are multiple peer frameworks who might use independent rings it would be nice to let peer frameworks / libraries who use io_uring to be able to shared a single sqpoll kernel thread.
Feature request
Add a new flag: IORING_SETUP_SQPOLL_SHARED_POLLTHREAD which if set, will automatically attach to a shared sqpoll kernel thread if one exists, otherwise create a shared instance (for the process).
Benefits
This makes it trivial from the user side to share the sqpoll thread which is helpful for some (many?) use cases
It also makes it possible to share the kernel poll thread even if multiple peer frameworks use io_uring independently - this will likely become more important going forward as io_uring usage proliferates.

I'm on the side that the kernel should stay as slim as possible, and if something can be done from the usespace it should be it. I like the multi framework argument, but frankly using multiple rings sounds wrong -- you need to somehow bind them, e.g. for CQE waiting, adding something artificial like eventfd notifying from one ring to another or other option, and that's a huge burden. Anyway, frameworks if so necessary can provide some way/extension exposing rings/ring_fd/etc. outside.
So, tbh, I don't see a good reason why to put it into the kernel...

Ok, fair enough - it definitely possible to work around it, so let's close, thanks for consideration.

authors: hassila isilence

repo: axboe/liburing

license: mit


text:
chore(readme): clean up build steps in README

Description
Todos

[ ] Unit tests
[ ] Manual tests
[ ] Documentation
[ ] Connect epics/issues
[ ] Tag type of change
[ ] Upgrade handler

Steps to Test
Expected Behaviour
Other Notes

For some reason, actions from old commits are shown as stuck in the status checks, seems to be a github issue.

repo: axelarnetwork/axelar-core


text:
Dependency License Gathering

Something Something Software Build Of Materials Something Something Summary File? Not sure if there's a Good tool for this yet we should just use. Not sure if there's a Standard Format to produce (iirc linux distros have some tooling around this we should interop with).

https://github.com/opensbom-generator/spdx-sbom-generator exists and supports cargo, is probably the most mature tool. is written in go. but they do produce binaries so we may be able to install and orchestrate

authors: Gankra ashleygwilliams

repo: axodotdev/cargo-dist


text:
需求：添加一个后台管理页面，可以在线编辑

网站项目做的好很，但是不能直接在线编辑文档，希望以后能添加这个功能。

此项目暂无管理后台计划。
建议使用 CI 和 WebHooks 等手动实现提交后自动部署。


text:
feat: add cut_cross_entropy

Description

Add https://github.com/apple/ml-cross-entropy
Note: torch>=2.4
Motivation and Context

How has this been tested?

Run test comparison:

[x] llama
[x] mistral
[x] gemma2
[x] phi3

Misc:

[ ] Add guards check conflict against other patches

Screenshots (if appropriate)
Types of changes

Social Handles (Optional)

The cce e2e tests don't actually work since we don't install cce anywhere. We probably actually want an error when cce is configured but not installed/available.

There is a bug that plugins aren't loaded despite in the configs for our integration e2e tests. This has been fixed in https://github.com/axolotl-ai-cloud/axolotl/pull/2091/commits/a983c3bc73982c0aae428cb36b9b2b34893d40b3

The cce e2e tests don't actually work since we don't install cce anywhere. We probably actually want an error when cce is configured but not installed/available.

There were a few checks for installation. However, the plugin wasn't loaded leading to them not being checked. I have just fixed this.

I rebased this PR as there were some conflicts.

There's an integration issue since unsloth also requires cut-cross-entropy in it's pyproject.toml

repo: axolotl-ai-cloud/axolotl


text:
Hide Add Map Button for Validators

Overview
If the logged in user is a Validator, the Add Map button should be hidden:

Shares points with #216

repo: azavea/iow-boundary-tool


text:
Consolidate Map Logic

We only want/need a single map for browse/edit.
Note: consolidation may not be the best solution so investigate that in the process.

Roll browse map logic into editor, depends on #1440

repo: azavea/raster-foundry


text:
chore: update max-width headers table

ajuste no header de comparable table para não causar rolagem no container de 1280

:tada: This PR is included in version 1.69.13 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: cesaroeduardo robsongajunior

repo: aziontech/azion-webkit


text:
Job in pipeline mode is blocked by another execution, where the job is disabled

If a job is disabled for an execution, it seems that later execution for that job in pipeline mode is blocked for the entire flow execution. Job shouldn't be blocked on pipeline if the same job is not running or going to be run by a previously started execution.
Steps to reproduce
Let's say we have a flow with two jobs in it job_x -> job_y

Launch an execution, id=1, with job_x disabled
Now job_y is running in execution 1
Launch another execution, id=2, with job_y disabled
Now job_x of execution 2 is "queued" and is said to be blocked by the same job in execution 1

The bug here is that job_x of 2 is blocked until execution 1 has finished completely, although execution 1 never runs job_x.

Fixed by https://github.com/azkaban/azkaban/pull/1245

repo: azkaban/azkaban


text:
version: 3.7.0 : java.sql.SQLException

source code :   azkaban.executor.JdbcExecutorLoader
Caused by: java.sql.SQLException: Unknown column 'ex.executor_id' in 'on clause' Query: SELECT ex.exec_id exec_id, ex.enc_type enc_type, ex.flow_data flow_data, et.host host, et.port port, ax.update_time axUpdateTime, et.id executorId, et.active executorStatus FROM execution_flows ex INNER JOIN  active_executing_flows ax ON ex.exec_id = ax.exec_id INNER JOIN  executors et ON ex.executor_id = et.id

I just came across this too with 3.8. Seems that the update.execution_flows.3.0.sql file is when that column was added, but the sql file to create the table, create.execution_flows.sql, was never updated. Same for create.active_executing_flows.sql.
Work around, run the update scripts. Docs could be updated to say to run the update scripts, but I think the intention was to have a single sql file to run to set up the DB.

@fsi206914 you set up a new cluster not long ago. What do you think? Shall we update the scripts. It's been a long time the DB schema update. Maybe we can optimize for the new installations now.

@HappyRay Yes, I totally agree with you. It's time to updae the sql scripts to be consistent with AZ 3.8

@fsi206914 Maybe we can update the script as part of setting up a new staging cluster?

I see, Thanks everyone！


text:
Kafka Event trigger

This PR is to demonstrate how we can achieve a new feature to trigger workflows by events.
A trigger instance will wait for all dependency instances are available so as to kick-off until reaching the maximum waiting time. This feature enables users to specify all the dependencies <Topic, Event> pair. By the Trigger.flow example provided below, the user scheduled a flow depends on both event with regular expression match of rules "." and  "hadoop?.". All we can do is matching a Kafka event with Regex, however, one can implement an interface so as to extend this feature.
# Flow Trigger Example
trigger:
  maxWaitMins: 2880
  schedule:
    type: cron
    value: 0 0/2 * * * ?

  triggerDependencies:
    - name: dep1 # an unique name to identify the dependency
      type: kafka
      params:
        match: .*
        topic: AzEvent_Topic4
    - name: dep2 # an unique name to identify the dependency
      type: kafka
      params:
        match: hadoop?.*
        topic: AzEvent_Topic4

Pull Request Test Coverage Report for Build 3841

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 35.679%

Files with Coverage Reduction
New Missed Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/event/FlowWatcher.java
1
93.75%

azkaban-common/src/main/java/azkaban/executor/ExecutableFlowBase.java
1
80.42%

Totals

Change from base Build 3834:
0.0%

Covered Lines:
10114

Relevant Lines:
28347

💛  - Coveralls

Check out Event trigger PR #1858 for more information

authors: coveralls weidious


text:
Fix the race condition where two same flows are being submitted for execution.

Old code will execute two same flows if they are being submitted at the same time even though concurrent running option is disabled. We use combination of project name, flow name and a fixed suffix to synchronize on making sure submitting flow method is mutual exclusive to same flows' different submissions.
Add log before a scheduled flow starts.

Other synchronization options:

Convert the QueuedExecutions to a Queue instead of a PriorityQueue. Perform a peek instead of dequeuing it right away. This doesn't work in a PriorityQueue since the head can change
Manage locking in QueuedExecutions itself.


text:
Improvement/Clean Up API

Closes #11.

TODO: Provide stronger types, maybe expose codespan types for less boilerplate when implementing ErrorDetails.


text:
Azure Traffic Manager

We currently do not have any modules for Azure Traffic Manager. We have a requirement to bring this to CAF for a composition that contains Azure Traffic Manager profiles.

Thanks @hriaz, I will assign to you as discussed!

authors: arnaudlh hriaz

repo: aztfmod/terraform-azurerm-caf


text:
_ux_utility_memory_allocate调用方可以考虑字节对齐吗？

您好！_ux_utility_memory_allocate函数的调用方可以增加字节对齐的配置吗？我现在使用STM32H743，使用了USB DMA和高速缓存，因此我期望 传输的数据地址是32字节对齐的，并且这个数据缓冲区大小是32字节对齐的（实际传输的数据大小可以不是32字节倍数，但空间需要是32字节倍数，防止两种属性的数据在同一块高速缓存中）

Did you try the allocation with UX_ALIGN_32?
Another option, use MPU to setup a cache safe memory area for memory allocation, allocate cache safe memory to avoid caching issues.

是的，我希望我可以指定UX_ALIGN_32分配，至于MPU管理非缓存内存方案，和我当前方案区别不是太大。

或者我将UX_ALIGN_MIN修改为UX_ALIGN_32，可以吗？

Yes. You can try.

UX_ALIGN_MIN exported in ux_user_sample.h.
Closing.

repo: azure-rtos/usbx


text:
Cannot apply ARM template several with job schedule

Hi,
I have been using the sample 102-sample-automation-setup.
It confirmed the fact that it is impossible de use ARM templates to manage job schedules.
Anytime I try to apply twice the same ARM with jobSchedules, I get the error:
"Job with specified id already exists. Job id: 17887671-2bbd-4e79-bdee-40378a485a93"

Is there any way to work around this?

@r3dlin3
You can create a simple powershell script that will be executed before your arm template gets deployed. You powershell script can just remove your jobschedule resource
Something like this
Set-AzAutomationSchedule -AutomationAccountName "Contoso17" -Name "Schedule01" -Description "Automation Schedule" -ResourceGroupName "ResourceGroup01"

repo: azureautomation/automation-packs


text:
Add yield result

Q
A

Bug fix?
no

Breaking change?
no

New feature?
no

Deprecations?
no

Spec compliancy?
N/A

Tests added/pass?
yes

Fixed tickets
#100

License
MIT

I added test cases for yield result and yield result with parenthesis.

This PR shouldn't include the commits merged in #731

Yup, looks like this needs a rebase.

Sorry about that, I can fix it later (I am at school the rest of today sorry).

I rebased the repo, I am going to close this PR and create a new one. Thanks!

@pudility sounds good, but next time you can always force push to this branch too!

@existentialism Thanks for the tip! I will try to use that next time. I am pretty new to git and still learning about all of it's features.

authors: existentialism jridgewell nicolo-ribaudo pudility

repo: babel/babylon


text:
Move custom options to "ember-cli-babel" options hash

Resolves #102 and unblocks part of the journey to Babel 6
/cc @rwjblue @stefanpenner @nathanhammond

Tests? I think we can unit test the invocations to _getBabelOptions and shouldIncludePolyfill.
Are there other options we supported for ember-cli-babel under the babel namespace?

Are there other options we supported for ember-cli-babel under the babel namespace?

since those are the only two options that ember-cli-babel cares about I don't think there are more

Tests? I think we can unit test the invocations to _getBabelOptions and shouldIncludePolyfill

do we have some sort of test harness for that?

@nathanhammond got tests now for the new logic

After these changes I'm pretty sure it's good to go. Would like a bonus confirmation from @rwjblue.

Agreed, I am 👍 once the current round of requests are resolved.  We should followup with updates in ember-cli's beta branch ASAP though...

@rwjblue @nathanhammond addressed your requests

authors: Turbo87 nathanhammond rwjblue

repo: babel/ember-cli-babel


text:
Use database level collation for collatable datatypes for prepared statements

Description
Update collation for collatable datatypes to pick up database level collation for prepared statements. Till now, server level collation was being picked up. This commit updates that to pick correct database level collation.
Issues Resolved
BABEL-5203
Authored by: Shameem Ahmed shmeeh@amazon.com
Test Scenarios Covered

Use case based -

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Client tests -

Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build 10612867668
Details

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.001%) to 74.062%

Totals

Change from base Build 10599358782:
0.001%

Covered Lines:
44517

Relevant Lines:
60108

💛  - Coveralls

authors: ahmed-shameem coveralls


text:
Use the #[inline] macro on resampling functions

This should provide us a small performance boost when resampling
audio.

It looks like this optimization does not make anything faster.
It is possible that the Rust compiler already inlines functions when appropriate.

repo: babycat-io/babycat


text:
Success: SCT not enabled for

private void addCt(OkHttpClient.Builder okHttpBuilder,  Set hosts ){
Logger defaultLogger = new Logger() {
@Override
public void log(@NotNull String s, @NotNull VerificationResult verificationResult) {
LogUtil.w("--- verify s %s, result: "+verificationResult, s);
}
};
CTInterceptorBuilder builder = new CTInterceptorBuilder()
.setFailOnError(true)
.setLogger(defaultLogger)
;
for (String host : hosts) {
builder.addHost(host);
}
Interceptor networkInterceptor = builder.build();
okHttpBuilder.addNetworkInterceptor(networkInterceptor);
}
Why the log told me:
result: Success: SCT not enabled xxx
Thank you!

You get this message when connected to a host that you have not specifically added a host entry into the builder for. As such any hosts not listed are not verified for certificate transparency and simply passed through

When adding hosts, you have to be careful as:

Host example.com only matches example.com exactly
Host www.example.com only matches www.example.com exactly
Host *.example.com matches www.example.com (and other sub-domains) but does not match example.com with no sub-domain

Therefore, in some instances you may need to explicitly add in two entries, example.com and *.example.com to include the main domain and all sub-domains.
Additionally, if you want all domains and sub-domains to use certificate transparency (regardless of the domain) you can use the special host, *.*.

Thanks a lot.
By the way, *.* can not match the sub-domains like aa.bb.cc.com .
We could use *.bb.cc.com or aa.bb.cc.com to match.

Could you share some URLs which have no Certificate Transparency to test?
Because we wanna see the abnormal case.
BRs!

*.* will match any domain and subdomain, regardless of the number of dots (or indeed value), I'll add a unit test later to prove it, but basically it will match aa.bb.cc.com. In fact *.* is so special it even matches empty domain names 😂 i.e. really it accepts all values regardless of the value/structure.
I use https://no-sct.badssl.com in the integration tests for the "abnormal case" 😄 See https://github.com/babylonhealth/certificate-transparency-android/blob/main/lib/src/test/kotlin/com/babylon/certificatetransparency/internal/CertificateTransparencyInterceptorIntegrationTest.kt

Very grateful for your support!

When I set minifyEnabled true, some build error happened:
org.gradle.execution.MultipleBuildFailures: Build completed with 1 failures. 	at org.gradle.initialization.DefaultGradleLauncher$ExecuteTasks.run(DefaultGradleLauncher.java:358) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90) 	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) 	at org.gradle.initialization.DefaultGradleLauncher.runTasks(DefaultGradleLauncher.java:219) 	at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:149) 	at org.gradle.initialization.DefaultGradleLauncher.executeTasks(DefaultGradleLauncher.java:124) 	at org.gradle.internal.invocation.GradleBuildController$1.call(GradleBuildController.java:77) 	at org.gradle.internal.invocation.GradleBuildController$1.call(GradleBuildController.java:74) 	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:154) 	at org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks(StopShieldingWorkerLeaseService.java:38) 	at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:96) 	at org.gradle.internal.invocation.GradleBuildController.run(GradleBuildController.java:74) 	at org.gradle.tooling.internal.provider.runner.ClientProvidedBuildActionRunner.run(ClientProvidedBuildActionRunner.java:68) 	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35) 	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35) 	at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32) 	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.run(RunAsBuildOperationBuildActionRunner.java:50) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90) 	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) 	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:45) 	at org.gradle.tooling.internal.provider.SubscribableBuildActionRunner.run(SubscribableBuildActionRunner.java:51) 	at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:47) 	at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:44) 	at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:79) 	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:44) 	at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:30) 	at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:39) 	at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:25) 	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:80) 	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:53) 	at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:62) 	at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:34) 	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36) 	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25) 	at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:43) 	at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:29) 	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:59) 	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:31) 	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:59) 	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:44) 	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:46) 	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:30) 	at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:67) 	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36) 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) 	at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37) 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) 	at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26) 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) 	at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34) 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) 	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74) 	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72) 	at org.gradle.util.Swapper.swap(Swapper.java:38) 	at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72) 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) 	at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55) 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) 	at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:62) 	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36) 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) 	at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:81) 	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36) 	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122) 	at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50) 	at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:295) 	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) 	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) 	at java.lang.Thread.run(Thread.java:745) Caused by: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:transformClassesAndResourcesWithProguardForDebug'. 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:110) 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:77) 	at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51) 	at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59) 	at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54) 	at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:59) 	at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:101) 	at org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute(FinalizeInputFilePropertiesTaskExecuter.java:44) 	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:91) 	at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:62) 	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:59) 	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54) 	at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) 	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34) 	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.run(EventFiringTaskExecuter.java:51) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90) 	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) 	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:46) 	at org.gradle.execution.taskgraph.LocalTaskInfoExecutor.execute(LocalTaskInfoExecutor.java:42) 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:277) 	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:262) 	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:135) 	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:130) 	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.execute(DefaultTaskPlanExecutor.java:200) 	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.executeWithWork(DefaultTaskPlanExecutor.java:191) 	at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.run(DefaultTaskPlanExecutor.java:130) 	... 6 more Caused by: java.lang.RuntimeException: Job failed, see logs for details 	at com.android.build.gradle.internal.transforms.ProGuardTransform.transform(ProGuardTransform.java:209) 	at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java:239) 	at com.android.build.gradle.internal.pipeline.TransformTask$2.call(TransformTask.java:235) 	at com.android.builder.profile.ThreadRecorder.record(ThreadRecorder.java:102) 	at com.android.build.gradle.internal.pipeline.TransformTask.transform(TransformTask.java:230) 	at sun.reflect.GeneratedMethodAccessor317.invoke(Unknown Source) 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 	at java.lang.reflect.Method.invoke(Method.java:498) 	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73) 	at org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.doExecute(IncrementalTaskAction.java:50) 	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:39) 	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:26) 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:131) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174) 	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90) 	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:120) 	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:99) 	... 34 more Caused by: java.io.IOException: Please correct the above warnings first. 	at proguard.InputReader.execute(InputReader.java:149) 	at proguard.ProGuard.readInput(ProGuard.java:255) 	at proguard.ProGuard.execute(ProGuard.java:96) 	at com.android.build.gradle.internal.transforms.BaseProguardAction.runProguard(BaseProguardAction.java:66) 	at com.android.build.gradle.internal.transforms.ProGuardTransform.doMinification(ProGuardTransform.java:274) 	at com.android.build.gradle.internal.transforms.ProGuardTransform.access$000(ProGuardTransform.java:67) 	at com.android.build.gradle.internal.transforms.ProGuardTransform$1.run(ProGuardTransform.java:178) 	at com.android.builder.tasks.Job.runTask(Job.java:47) 	at com.android.build.gradle.tasks.SimpleWorkQueue$EmptyThreadContext.runTask(SimpleWorkQueue.java:41) 	at com.android.builder.tasks.WorkQueue.run(WorkQueue.java:282) 	... 1 more

If anybody meet:
class [META-INF/versions/9/module-info.class] unexpectedly contains class [module-info]
there were 2 classes in incorrectly named files.
kotlinx.coroutines.flow.FlowKt__MergeKt: can't find referenced class kotlinx.atomicfu.AtomicBoolean
there were 11 unresolved references to classes or interfaces.
Please try to add -dontwarn in your proguard-rules.pro file:
-dontwarn module-info
-dontwarn kotlinx.atomicfu.AtomicBoolean

It seems that pattern "." failed to match "https://github.com/"

authors: courysky mattmook


text:
🛑 SM Service is down

In caad032, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 7ddb6af.

repo: bachmannschumacher/upptime


text:
🛑 SM Service is down

In afd8002, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in a1f9d26.


text:
Make app-backend wait for backend startup before serving frontend

As reported in #10323, in some cases the frontend builds and starts too fast, before the relevant backend is ready for requests.
In this particular case it was the catalog page, and the catalog backend. We should one way or the other support this case - perhaps the frontend could perform retries, perhaps there could be some more explicit readiness endpoint that's polled by the app-backend before it lets through the first requests, or something else.

Will it be applicable for separate deployment use case ?
https://backstage.io/docs/deployment/docker#separate-frontend

authors: freben shailahir

repo: backstage/backstage


text:
TechDocs: Show status of build process similar to scaffolder

Feature Suggestion

If TechDocs is configured to build docs, tell the user about the progress. Something like this
-> Fetching documentation files from source
   Generating TechDocs site
   Storing files to storage

✅ Fetching documentation files from source
-> Generating TechDocs site
   Storing files to storage

✅ Fetching documentation files from source
✅ Generating TechDocs site
-> Storing files to storage

and then docs will appear.
Possible Implementation

Scaffolder creates a new job for each scaffolding process and then fetches the job status every second. Implement the feature here in a similar way.
Or perhaps, use web sockets?
Context
As of now, if a user opens a TechDocs site and if docs are being built before it loads, there is no status of the process. Given the waiting period could be 20-60 seconds, it's good to see some status.
Might be convenient to start work after https://github.com/backstage/backstage/pull/3432 is merged.

We'll probably end up doing significant work to build a little task coordination system for the new scaffolder. Looks like that may happen during Q1. This will be required to make it scale to multiple hosts.
This task is a great idea. Maybe our t goals overlap. Let's coordinate!

@freben Awesome to hear about the step towards a better approach. I'll be happy to help and/or follow closely.

This would also be a good place to show errors in the generation process. Till now they are only outputed to the stdout of the backend process, which normal users won't have access too.

Seems to be somewhat related: #4111

Parts of this are implemented now. We have a UI that's shows build logs and errors. But there is coordination for task in multiple backend replicas or parallel requests.

Thanks @Fox32 ! The problem described in the context of this issue seems to be resolved now. I'd like to close this!

authors: Fox32 OrkoHunter freben


text:
chore: update humanitec plugin

Hey, I just made a Pull Request!
The humanitec plugin moved to a new location.

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

👍 Humanitec folks are taking over their plugin because they will soupe it up.

authors: johanneswuerbach taras


text:
Namespace management

All functions in this service should belongs in a namespace, it's useful to organize and do better ownership of functions.

The thing about this tasks I believe is define the routes of the functions
The better way to define that is making all the routes in a rest way in a way that this should be the url of the resource
/functions/:namespace/:function_name
and to run the function call this route
/functions/:namespace/:funtion_name/run

@wpjunior finished with commit 	7101de8

authors: heitorsilva pedrosnk wpjunior

repo: backstage/functions


text:
Fetch wrapper breaks token for some providers when refreshing

I'm using Cognito as the OAuth provider. In this case, the tokens returned to the client when providing a refresh token do not include a new refresh token (nor the old one - no refresh token comes back at all). This means that https://github.com/badgateway/oauth2-client/blob/dfaa4622ff37217a62a8daa551257c385e8bd7b4/src/client.ts#L184 wipes out the refresh token and subsequent refreshes will fail. I've mentioned the fetch wrapper because that's where I noticed the behaviour, but it appears this will happen for any refresh.
The solution might be to check the returned token and add the old refresh token back if the new one is null. I can PR for this if you're happy with the approach.

Interesting! I wonder how normal this behavior is. Cognito is a big one, so it makes sense to have some kind of workaround for this.
What kind of grant_type was used for obtaining the original tokens?

Actually I had another look at the RFC and it seems pretty clear we should just keep using the old refresh_token:
https://datatracker.ietf.org/doc/html/rfc6749#section-6

Yup. The original grant type was code (with PKCE).
If you want me to PR let me know. It's a simple fix (a lot simpler than the ugly workaround I'm using).

authors: evert holmesjr


text:
Cookie in use

![GitHub All Releases](https://img.shields.io/github/downloads/sugarchain-project/sugarchain/total)

Hi, how to not use this cookie? I wanna remove this one. Any suggest?

Hi! The only way to turn it off is to host your own copy of Shields. Would suggest following #3026 which discusses the alternatives.

repo: badges/shields


text:
Move NPM package files out of /lib ; affects [resharper nuget myget dub chocolatey github]

The aim of this PR is to move all the files relating to the gh-badges package into a new location and give the package its own package.json and documentation while making as few other changes as possible.
The accomplishes several things:

We can distribute a package which only requires the necessary dependencies for the library (at the moment we force our users to install a bunch of other dependencies needed by shields.io but not gh-badges)
It is easier to provide more relevant documentation for the NPM package
It is step 1 on the road to further reducing the coupling between this package and the rest of the codebase

I've made the decision to keep all the npm devDependencies and scripts (for testing etc) in the repo root. There are several reasons for this:

npm install "file:gh-badges/" doesn't install the devDependencies of the child package and its (prod) dependencies go into the parent node_modules.
We'll need to amend our dependabot config to track/update dependencies across 2 package.jsons. We're going to get 2 PRs to review/merge for any packages which exist in both package.jsons. I'm keen to minimise that overhead. As it stands, is-css-color is the only dependency we need to have in both package.jsons.

I think this is the right choice for the way we organise things now, but if we want to move to a position where we store the package in a different repo we would need to change this.
A couple of other notes:

I haven't moved the logos dir into gh-badges. The logos dir was included in the package in 1.1.1, 1.3.0 and 2.0.0 but having looked into this a bit more, I don't think we've ever advertised/documented that they exist or documented logo as a valid format key. I think moving forwards, we should not include the logos in the package.
There is some further work that I would like to do around what we export in the package and how we import/require elsewhere in the application, but I don't want to clutter this PR more than we need to - that can happen in a future PR.
This PR modifies the service tests for powershellgallery but I haven't put [powershellgallery] in the title because they're failing for an unrelated reason. I think the temporary endpoint we switched to (see https://github.com/badges/shields/issues/2078 ) has gone away. Lets not get bogged down in that issue in this PR.

The only medium thing is the name of the folder. While gh-badges is the historical name of the npm package, it’s not very descriptive and I think does not convey to a new developer what to expect in the folder. I’d suggested some alternate names for the npm package. What do you think about using one of those names for this folder? If you want it to match the package name, we could deprecate the old package and re-release under a new name. In that case we should pick a name that’s available in npm.

Ideally the directory name should mirror the package name so if we're going to continue publishing at https://www.npmjs.com/package/gh-badges then the dir should be called gh-badges. If we're going to move it to a new name in NPM then we should call the directory whatever the new package name is. I think its confusing if we change the dir name but continue releasing with gh-badges as the package name.
I do agree that gh-badges is not the most descriptive name. It is not what I would choose today, but there is history. That said, I think I am in favour of sticking with it for now. It seems a bit odd not to put out a release for 2 years, then pop up and release 2.0 and then immediately deprecate the package a week later.
Perhaps another approach would be to call the dir 'package' or something - then we can change the package name at a later date without moving it?

it would be helpful to write a couple sentences in CONTRIBUTING.md

Yeah - good point. I'll have a look at the contributing docs too

if your intent is that contents of gh-badges is imported using relative imports rather than require('gh-badges') it'd be good to mention that.

I'm not entirely sure what the best approach is here. I think if we want to treat this more like a standalone package, we want to move away from relative imports but I think that will also mean we need to expose more of the guts of the module as public interface (e.g: if we want to use make-badge-test-helpers in other tests in /lib we need to expose it to package users too, but that's maybe not necessarily a massively useful thing to do). Maybe the answer is a mix. Thinking about this issue some more is what I was getting at when I said:

There is some further work that I would like to do around what we export in the package and how we import/require elsewhere in the application

I've just done everything with relative imports for the moment as I wanted to avoid changing too many things all at once in the same PR, but I think the next thing (or one of the next things) we should do is look at that issue.
Would be interested in your thoughts on the tradeoffs involved in this..

I'm not sure whether I agree or not. I do think the simple-icons support probably should be in gh-badges, perhaps as an optional peer dependency. That could happen in a follow-on.

Lets not address SimpleIcons in this PR. Do you think we should move the custom logos dir in this PR and keep them a part of the package?

I proposed a solution that simplifies font measuring in #2311. Let's get this in and then we can pick that up.

Hi sorry I didn't get a chance to check in on this yesterday. Thanks for responding to #2312 and adding some extra docs here.
I think I'm in favour of:

Plan to rename the package in a couple months, and move the files again when we do that. (i.e. folder temporarily uses legacy name)

One other thing to consider is that we're now we've started talking about stuff like changing the text measurer, supporting SVG only, changing the exported classes/functions, we might find we want to make another non backwards-compatible change in the medium-term future. That would require a major version bump to 3.0. That might also represent a natural milestone where changing the package name and deprecating would make sense. I don't think renaming the directory will be a complicated job when we do this.

Honestly when it comes to almost every decision about importing, I think the easiest solution is to refactor and rewrite these kludges away

:+1:


text:
[security] Bump nyc from 13.3.0 to 14.0.0

CI will pass after #3322 is merged.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against 08c65a3d4a26a3c6a153c45c0d045c9bd216ef86

I've been having some issues with v14 in some of my other projects where coverage isn't being reported correctly on Windows. I believe there's an open issue in the nyc repo along the same lines
Just sharing for awareness in case anyone else sees it in the short term.

The changelog mentions a change in instrumentation include/excludes. I wonder if that could be the problem? Though not sure why it would only take effect on Windows.
Should we hold off updating?

Should we hold off updating?

I'm going to check out this branch on Windows and check. If it looks there's a coverage problem on Win then I'd be inclined to hold off on this. This is the issue in the nyc repo I was thinking of, and it's the same type of thing I've been seeing as well

Coverage report definitely looks off to me on Windows (report from running all our coverage scripts)

It looks like it is not ignoring .next or .github. Why is .github even coming up?
It's not clear it's the same issue as istanbuljs/nyc#1065 though. Hmm…

It's not clear it's the same issue as istanbuljs/nyc#1065 though

I don't know about the OP's issue, but the simple example demonstrated in the last comment is something I'm seeing in a couple private projects. Coverage is fine on folks' Macs but not on Windows

I updated my local config to explicitly exclude those directories, and coverage looks better now.

My sense is that there's probably just a need to make some minor config tweaks with v14. I pushed the updates I made to my local config that fixed our coverage on Windows, so I believe this is good to merge

authors: calebcartwright paulmelnikow shields-ci


text:
Add badge for Packagist stars (favers)

Add a badge to show stars given to a PHP package on Packagist.
Test:
npm run test:services -- --only=packagist

New badge UI:

Closes #4912

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @pixelbrackets!

  Generated by :no_entry_sign: dangerJS against 95bb812fa6f698b8ed3e8708c5c796ef482fbd8b

authors: pixelbrackets shields-ci


text:
Changes to the contribution.md file

In the contribution.md file , these are the changes I have made:
-In the how to contribute section, I added a screenshot of an image showing the location of the fork button. Below is the link to the image added.

-In the code style and standards section, there was not enough information about the coding styles and standards; therefore, I've added a link to the site with more details.
-And finally, the issue tracking section mentions contacting maintainers in case help but fails to give information about the maintainers and how to contact them. I have added their names and links to their GitHub accounts.
The screenshot image is stored in the src folder, inside the assets folder in the images folder.

Hello @Poison-Iveey, welldone! Please sign off on your commits so your PR can pass the checks. Also indicate which issue your PR is resolving

Hello,

so I have been trying to properly sign off my commits but I keep getting an error message saying there's a merge conflict during the rebase that needs to be manually resolved. So I don't know whether to keep the code from the current branch or to keep the code from the rebased commit. What should I do?

Hello,
so I have been trying to properly sign off my commits but I keep getting an error message saying there's a merge conflict during the rebase that needs to be manually resolved. So I don't know whether to keep the code from the current branch or to keep the code from the rebased commit. What should I do?

Hi, can you walk me through the steps you took that led to this point?

Thank you @kaxada for the fix and advice. Cheers 🥂

authors: Poison-Iveey adeyinkaoresanya harmonyelendu misspee007

repo: badging/badging


text:
[Vue warn]: Error in directive validate bind hook: "TypeError: Cannot create property '_dateElement' on number '0'"

Versions:

VueJs: 2.5.8
Vee-Validate: v2.0.0-rc.23

Description:
`

`
Steps To Reproduce:

Do you mind providing a code snippet that produces this error?

@logaretm
import VeeValidateES from 'vee-validate/dist/locale/es';
import VeeValidate, { Validator } from 'vee-validate';
Validator.localize('es', VeeValidateES);
Vue.use(VeeValidate, {
locale: 'es'
});

                                        {{ Form::label('nro', 'Doc') }}
                                        {{Form::text('nro', null, ['v-validate'=>"'required|numeric'", 'v-model.trim'=>'nro',  'tabindex'=>'2','class' => 'rounded form-control'] )}}
                                        @{{ errors.first('nro') }}

Re installing vee validate fix the error.

repo: baianat/vee-validate


text:
LSTM running error !

HI, all
In quick start demo, I have tested LR, WE+LR, WE+CNN successfully.
But when i run WE+LSTM, the following error occurred:
I0905 12:50:46.881464 24807 Util.cpp:144] commandline: /data11/dis_ml/deeplearning/paddle/bin/../opt/paddle/bin/paddle_trainer --config=trainer_config.lstm.py --save_dir=./output_lstm --trainer_count=16 --log_period=1000 --num_passes=15 --use_gpu=false --show_parameter_stats_period=2000 --test_all_data_in_one_period=1
I0905 12:50:46.881670 24807 Util.cpp:113] Calling runInitFunctions
I0905 12:50:46.881896 24807 Util.cpp:126] Call runInitFunctions done.
[INFO 2016-09-05 12:50:47,468 networks.py:1122] The input order is [word, label]
[INFO 2016-09-05 12:50:47,468 networks.py:1125] The output order is [cost_0]
I0905 12:50:47.492952 24807 Trainer.cpp:169] trainer mode: Normal
I0905 12:50:47.660745 24807 PyDataProvider2.cpp:219] loading dataprovider dataprovider_emb::process
I0905 12:50:47.684976 24807 PyDataProvider2.cpp:219] loading dataprovider dataprovider_emb::process
I0905 12:50:47.685173 24807 GradientMachine.cpp:134] Initing parameters..
I0905 12:50:47.901549 24807 GradientMachine.cpp:141] Init parameters done.
I0905 12:50:48.229571 24813 ThreadLocal.cpp:39] thread use undeterministic rand seed:24814
I0905 12:50:48.229737 24821 ThreadLocal.cpp:39] thread use undeterministic rand seed:24822
I0905 12:50:48.230121 24818 ThreadLocal.cpp:39] thread use undeterministic rand seed:24819
I0905 12:50:48.230481 24814 ThreadLocal.cpp:39] thread use undeterministic rand seed:24815
I0905 12:50:48.230881 24810 ThreadLocal.cpp:39] thread use undeterministic rand seed:24811
I0905 12:50:48.232058 24820 ThreadLocal.cpp:39] thread use undeterministic rand seed:24821
Current Layer forward/backward stack is
LayerName: lstmemory_0
LayerName: fc_layer_0
LayerName: embedding_0
LayerName: word
*** Aborted at 1473079848 (unix time) try "date -d @1473079848" if you are using GNU date ***
I0905 12:50:48.248039 24822 ThreadLocal.cpp:39] thread use undeterministic rand seed:24823
Current Layer forward/backward stack is
PC: @           0x8024f0 (unknown)
I0905 12:50:48.253355 24811 ThreadLocal.cpp:39] thread use undeterministic rand seed:24812
I0905 12:50:48.254111 24812 ThreadLocal.cpp:39] thread use undeterministic rand seed:24813
I0905 12:50:48.256650 24816 ThreadLocal.cpp:39] thread use undeterministic rand seed:24817
I0905 12:50:48.259268 24823 ThreadLocal.cpp:39] thread use undeterministic rand seed:24824
I0905 12:50:48.260787 24819 ThreadLocal.cpp:39] thread use undeterministic rand seed:24820
I0905 12:50:48.263543 24815 ThreadLocal.cpp:39] thread use undeterministic rand seed:24816
I0905 12:50:48.264271 24808 ThreadLocal.cpp:39] thread use undeterministic rand seed:24809
I0905 12:50:48.265414 24817 ThreadLocal.cpp:39] thread use undeterministic rand seed:24818
I0905 12:50:48.271780 24809 ThreadLocal.cpp:39] thread use undeterministic rand seed:24810

Before building paddle, "version GLIBC_2.14 no found" occured, so i update glibc from 2.12 to 2.14. Is this OK?

It's very strange that PaddlePaddle didn't print call stack. If you are convenient, can you rebuild PaddlePaddle with flag '-DCMAKE_BUILD_TYPE=Debug', and rerun this training? Or can you give us the core dump files?
And you can refer this link http://stackoverflow.com/questions/17965/how-to-generate-a-core-dump-in-linux-when-a-process-gets-a-segmentation-fault

@reyoung
I0907 17:26:32.151026  1053 Util.cpp:144] commandline: /data11/dis_ml/deeplearning/paddle/bin/../opt/paddle/bin/paddle_trainer --config=trainer_config.lstm.py --save_dir=./output_lstm --trainer_count=4 --log_period=1000 --num_passes=15 --use_gpu=false --show_parameter_stats_period=2000 --test_all_data_in_one_period=1
I0907 17:26:32.151208  1053 Util.cpp:113] Calling runInitFunctions
I0907 17:26:32.151401  1053 Util.cpp:126] Call runInitFunctions done.
[INFO 2016-09-07 17:26:32,723 networks.py:1122] The input order is [word, label]
[INFO 2016-09-07 17:26:32,723 networks.py:1125] The output order is [cost_0]
I0907 17:26:32.740944  1053 Trainer.cpp:169] trainer mode: Normal
I0907 17:26:32.826501  1053 PyDataProvider2.cpp:219] loading dataprovider dataprovider_emb::process
I0907 17:26:32.856484  1053 PyDataProvider2.cpp:219] loading dataprovider dataprovider_emb::process
I0907 17:26:32.856694  1053 GradientMachine.cpp:134] Initing parameters..
I0907 17:26:33.070418  1053 GradientMachine.cpp:141] Init parameters done.
I0907 17:26:33.346114  1062 ThreadLocal.cpp:39] thread use undeterministic rand seed:1063
I0907 17:26:33.367995  1065 ThreadLocal.cpp:39] thread use undeterministic rand seed:1066
I0907 17:26:33.373780  1064 ThreadLocal.cpp:39] thread use undeterministic rand seed:1065
Current Layer forward/backward stack is
LayerName: lstmemory_0
LayerName: fc_layer_0
LayerName: embedding_0
LayerName: word
*** Aborted at 1473240393 (unix time) try "date -d @1473240393" if you are using GNU date ***
Current Layer forward/backward stack is
PC: @           0x8024f0 (unknown)
Current Layer forward/backward stack is
*** SIGILL (@0x8024f0) received by PID 1053 (TID 0x7f50fe12e700) from PID 8398064; stack trace: ***
Current Layer forward/backward stack is
@     0x7f510f76c710 (unknown)
Current Layer forward/backward stack is
@           0x8024f0 (unknown)
Current Layer forward/backward stack is
@           0x587470 paddle::LstmCompute::forwardOneSequence<>()
Current Layer forward/backward stack is
@           0x5879fa paddle::LstmCompute::forwardBatch<>()
Current Layer forward/backward stack is
@           0x581d4c paddle::LstmLayer::forwardBatch()
Current Layer forward/backward stack is
@           0x58538a paddle::LstmLayer::forward()
Current Layer forward/backward stack is
@           0x616d74 paddle::NeuralNetwork::forward()
Current Layer forward/backward stack is
@           0x6211c6 paddle::TrainerThread::forward()
Current Layer forward/backward stack is
@           0x623374 paddle::TrainerThread::computeThread()
Current Layer forward/backward stack is
@     0x7f510e8743d2 execute_native_thread_routine
Current Layer forward/backward stack is
@     0x7f510f7649d1 start_thread
Current Layer forward/backward stack is
@     0x7f510e0598fd clone
/data11/dis_ml/deeplearning/paddle/bin/paddle: line 46:  1053 Illegal instruction     ${DEBUGGER} $MYDIR/../opt/paddle/bin/paddle_trainer ${@:2}

@NIULQfromNJU Hello, it seems that PaddlePaddle use some CPU instructions that your CPU not support (AVX). Please try to rebuild your PaddlePaddle, disable the AVX support using
-DWITH_AVX=OFF, and rebuild it. That will solve your problem.
There is a TODO in CMake file to automatically select AVX flag depends on machine CPU, but it is still not developed.
Please set -DCMAKE_BUILD_TYPE=Debug -DWITH_AVX=OFF to rebuild PaddlePaddle, make sure there is no error. Then you can set -DCMAKE_BUILD_TYPE=RelWithDebInfo -DWITH_AVX=OFF, and install it to train your model.

hi @reyoung , i rebuild the paddle with -DWITH_AVX=OFF, and then i run the quick start demo. But I have the same problem as before: LR, WE+LR, WE+CNN run successfully while WE+LSTM aborted. So strange! Is there any other instruction that is not supported by CPU in LSTM example?
The following is the error print:
I0907 20:30:21.711181 10069 Util.cpp:144] commandline: /data11/paddle/pd/bin/../opt/paddle/bin/paddle_trainer --config=trainer_config.lstm.py --save_dir=./output --trainer_count=4 --log_period=20 --num_passes=15 --use_gpu=false --show_parameter_stats_period=100 --test_all_data_in_one_period=1
I0907 20:30:21.711364 10069 Util.cpp:113] Calling runInitFunctions
I0907 20:30:21.711556 10069 Util.cpp:126] Call runInitFunctions done.
[INFO 2016-09-07 20:30:22,156 networks.py:1122] The input order is [word, label]
[INFO 2016-09-07 20:30:22,157 networks.py:1129] The output order is [cost_0]
I0907 20:30:22.174654 10069 Trainer.cpp:169] trainer mode: Normal
I0907 20:30:22.262153 10069 PyDataProvider2.cpp:219] loading dataprovider dataprovider_emb::process
I0907 20:30:22.288261 10069 PyDataProvider2.cpp:219] loading dataprovider dataprovider_emb::process
I0907 20:30:22.288434 10069 GradientMachine.cpp:134] Initing parameters..
I0907 20:30:22.491011 10069 GradientMachine.cpp:141] Init parameters done.
I0907 20:30:22.681430 10100 ThreadLocal.cpp:39] thread use undeterministic rand seed:10101
I0907 20:30:22.683939 10101 ThreadLocal.cpp:39] thread use undeterministic rand seed:10102
I0907 20:30:22.699645 10098 ThreadLocal.cpp:39] thread use undeterministic rand seed:10099
I0907 20:30:22.701810 10099 ThreadLocal.cpp:39] thread use undeterministic rand seed:10100
Current Layer forward/backward stack is
LayerName: lstmemory_0
LayerName: fc_layer_0
LayerName: embedding_0
LayerName: word
*** Aborted at 1473251422 (unix time) try "date -d @1473251422" if you are using GNU date ***
Current Layer forward/backward stack is
PC: @           0x8024f0 (unknown)
Current Layer forward/backward stack is
*** SIGILL (@0x8024f0) received by PID 10069 (TID 0x7f92afa00700) from PID 8398064; stack trace: ***
Current Layer forward/backward stack is
@     0x7f92c202d710 (unknown)
Current Layer forward/backward stack is
@           0x8024f0 (unknown)
Current Layer forward/backward stack is
@           0x587470 paddle::LstmCompute::forwardOneSequence<>()
Current Layer forward/backward stack is
@           0x5879fa paddle::LstmCompute::forwardBatch<>()
Current Layer forward/backward stack is
@           0x581d4c paddle::LstmLayer::forwardBatch()
Current Layer forward/backward stack is
@           0x58538a paddle::LstmLayer::forward()
Current Layer forward/backward stack is
@           0x616d74 paddle::NeuralNetwork::forward()
Current Layer forward/backward stack is
@           0x6211c6 paddle::TrainerThread::forward()
Current Layer forward/backward stack is
@           0x623374 paddle::TrainerThread::computeThread()
Current Layer forward/backward stack is
@     0x7f92c11353d2 execute_native_thread_routine
Current Layer forward/backward stack is
@     0x7f92c20259d1 start_thread
Current Layer forward/backward stack is
@     0x7f92c091a8fd clone
/data11/paddle/pd/bin/paddle: line 46: 10069 Illegal instruction     ${DEBUGGER} $MYDIR/../opt/paddle/bin/paddle_trainer ${@:2}

OK, we locate the problem here.  It seems that the lstm layer is use some AVX instructions. We will fix it in few days.

@reyoung great！

@NIULQfromNJU Please give us your cpu info. just cat /proc/cpuinfo

@reyoung
processor       : 15
vendor_id       : GenuineIntel
cpu family      : 6
model           : 44
model name      : Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
stepping        : 2
cpu MHz         : 2401.000
cache size      : 12288 KB
physical id     : 0
siblings        : 8
core id         : 10
cpu cores       : 4
apicid          : 21
initial apicid  : 21
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt aes lahf_lm ida arat tpr_shadow vnmi flexpriority ept vpid
bogomips        : 4800.24
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:

@NIULQfromNJU  Code is under review.  #51

@NIULQfromNJU The fix code is merge into master branch. Please checkout and lstm should be ok now.

@reyoung Well done! Now updated paddle can run lstm successfully! thx~

@NIULQfromNJU You're welcome.
If there is anything I can help, don't hesitate to ask.
Thank you for your attention.

authors: NIULQfromNJU reyoung

repo: baidu/Paddle