Can't use !ImportValue in custom resource YAML w/ v4.50.0

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm install -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v14.15.0
Amplify CLI Version
4.50.0
What operating system are you using?
Mac Big Sur
Amplify Categories
Not applicable
Amplify Commands
push
Describe the bug
I have a custom resource that uses !ImportValue to reference an SNS topic from another CloudFormation stack. With 4.50.0 I get the following error when running amplify push
An error occurred when pushing the resources to the cloud

unknown tag !<!ImportValue> (26:41)

 23 |  ... tMissingData: notBreaching
 24 |  ... istic: Sum
 25 |  ... tions:
 26 |  ... !ImportValue tools-AwsAlertsOk
-----------------------------------------^
 27 |  ... mActions:
 28 |  ... !ImportValue tools-AwsAlertsAlarm
An error occurred during the push operation: unknown tag !<!ImportValue> (26:41)

 23 |  ... tMissingData: notBreaching
 24 |  ... istic: Sum
 25 |  ... tions:
 26 |  ... !ImportValue tools-AwsAlertsOk
-----------------------------------------^
 27 |  ... mActions:
 28 |  ... !ImportValue tools-AwsAlertsAlarm

I had no problems with this using 4.48.0 this morning. Then upgraded to 4.50.0 and immediately got the error. The custom resource template is:
AWSTemplateFormatVersion: 2010-09-09
Description: CloudWatch Alarm Configuration
Parameters:
  env:
    Type: String
  functionIterableRequestName:
    Type: String
Resources:
  IterableRequestAlarm:
    Type: AWS::CloudWatch::Alarm
    Properties:
      Namespace: AWS/Lambda
      AlarmName: !Sub pace-IterableRequestAlarm-${env}
      MetricName: Errors
      Threshold: 1
      Period: 60
      EvaluationPeriods: 1
      AlarmDescription: This alarm signifies that we are having trouble processing Iterable API requests.
      Dimensions:
        - Name: FunctionName
          Value: !Ref functionIterableRequestName
      ComparisonOperator: GreaterThanOrEqualToThreshold
      TreatMissingData: notBreaching
      Statistic: Sum
      OKActions:
        - !ImportValue tools-AwsAlertsOk
      AlarmActions:
        - !ImportValue tools-AwsAlertsAlarm
      InsufficientDataActions:
        - !ImportValue tools-AwsAlertsInsufficientData

Expected behavior
Don't choke 🤮  on yaml !ImportValue.
Maybe also explain why the CLI even cares about the contents of my custom resource yaml.
Reproduction steps
See above
GraphQL schema(s)
N/A
Log output

2021-05-03T21:16:18.587Z|info : amplify version core  {"version":true,"yes":false}
2021-05-03T21:20:37.351Z|info : amplify push core  {"yes":true}
2021-05-03T21:20:45.498Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["amplify-temp"])
2021-05-03T21:20:45.499Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"us-east-1"}])
2021-05-03T21:20:45.499Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["amplify-temp"])
2021-05-03T21:20:45.510Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["amplify-temp"])
2021-05-03T21:20:45.510Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"us-east-1"}])
2021-05-03T21:20:45.510Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["amplify-temp"])
2021-05-03T21:20:45.515Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2021-05-03T21:20:45.521Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]ce-[***]j-[***]143-[***]ment"}])
2021-05-03T21:21:00.763Z|info : amplify-provider-awscloudformation.initialize-env.run.cfn.updateamplifyMetaFileWithStackOutputs([{"StackName":"[***]ify-[***]ce-[***]j-[***]143"}])
2021-05-03T21:21:00.776Z|info : amplify-provider-awscloudformation.aws-cfn.updateamplifyMetaFileWithStackOutputs.cfn.describeStackResources([{"StackName":"[***]ify-[***]ce-[***]j-[***]143"}])
2021-05-03T21:21:01.390Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]Connect-[***]UVAWKK/[***]25c0-[***]70-[***]eb-[***]bd-[***]8a65b"}])
2021-05-03T21:21:01.392Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]nueCat-[***]S9437U/[***]88f0-[***]41-[***]eb-[***]ee-[***]84415"}])
2021-05-03T21:21:01.393Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]Connect-[***]750T5/[***]2530-[***]fc-[***]eb-[***]2c-[***]a3521"}])
2021-05-03T21:21:01.394Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]ace-[***]5PWXQV/[***]ab00-[***]70-[***]eb-[***]b4-[***]eaed9"}])
2021-05-03T21:21:01.395Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]tore-[***]E46PV/[***]c5e0-[***]70-[***]eb-[***]f3-[***]3ee85"}])
2021-05-03T21:21:01.396Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]pple-[***]704P2O/[***]1f50-[***]e6-[***]eb-[***]1c-[***]0849f"}])
2021-05-03T21:21:01.397Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]pace-[***]LXDXJ1/[***]b950-[***]70-[***]eb-[***]c1-[***]c1ae9"}])
2021-05-03T21:21:01.398Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]EventStore-[***]C7USM/[***]5590-[***]78-[***]eb-[***]c4-[***]225b5"}])
2021-05-03T21:21:01.399Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]onChangeEvent-[***]9XW0Z/[***]2b30-[***]3a-[***]eb-[***]b2-[***]5bdc7"}])
2021-05-03T21:21:01.400Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]onaChangeEvent-[***]MLUPN/[***]3950-[***]54-[***]eb-[***]ee-[***]2d5f1"}])
2021-05-03T21:21:01.401Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]dbackRequest-[***]YHQ2I/[***]1100-[***]71-[***]eb-[***]db-[***]d803b"}])
2021-05-03T21:21:01.402Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]inConnect-[***]Z950G/[***]4fb0-[***]70-[***]eb-[***]45-[***]fabf5"}])
2021-05-03T21:21:01.403Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]bleRequest-[***]OYPYS8/[***]6ea0-[***]fc-[***]eb-[***]65-[***]de975"}])
2021-05-03T21:21:01.404Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]FileSamples-[***]B7ZMU/[***]ebb0-[***]3a-[***]eb-[***]83-[***]d20e2"}])
2021-05-03T21:21:01.405Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]venueCat-[***]0G9SC/[***]2d10-[***]41-[***]eb-[***]f1-[***]30a9d"}])
2021-05-03T21:21:01.405Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]uleRequest-[***]PUEEHA/[***]9bd0-[***]71-[***]eb-[***]00-[***]ba9df"}])
2021-05-03T21:21:01.406Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]gChangeEvent-[***]5JFVJ2/[***]18e0-[***]1c-[***]eb-[***]f4-[***]9d7c1"}])
2021-05-03T21:21:01.407Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]chUsageEvent-[***]BDHCXY/[***]e9d0-[***]df-[***]eb-[***]e9-[***]d258f"}])
2021-05-03T21:21:01.409Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]vaConnect-[***]JXZG1S/[***]8e10-[***]fc-[***]eb-[***]ce-[***]55b13"}])
2021-05-03T21:21:01.410Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]hangeEvent-[***]QTM8M5/[***]4390-[***]fc-[***]eb-[***]be-[***]8f74f"}])
2021-05-03T21:21:01.410Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]ChangeEvent-[***]PQI40/[***]9250-[***]02-[***]eb-[***]0f-[***]26083"}])
2021-05-03T21:21:01.411Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]ctionCache-[***]S3RCG/[***]7a80-[***]fc-[***]eb-[***]2f-[***]4d2e3"}])
2021-05-03T21:21:01.412Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]nceHistory-[***]4TNUJT/[***]1850-[***]6d-[***]eb-[***]a7-[***]9077b"}])
2021-05-03T21:21:03.738Z|error : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]nceHistory-[***]4TNUJT/[***]1850-[***]6d-[***]eb-[***]a7-[***]9077b"}])
Throttling: Rate exceeded
2021-05-03T21:21:03.756Z|error : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]bleRequest-[***]OYPYS8/[***]6ea0-[***]fc-[***]eb-[***]65-[***]de975"}])
Throttling: Rate exceeded
2021-05-03T21:21:03.775Z|error : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]ace-[***]5PWXQV/[***]ab00-[***]70-[***]eb-[***]b4-[***]eaed9"}])
Throttling: Rate exceeded
2021-05-03T21:21:03.891Z|error : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]chUsageEvent-[***]BDHCXY/[***]e9d0-[***]df-[***]eb-[***]e9-[***]d258f"}])
Throttling: Rate exceeded
2021-05-03T21:21:03.964Z|error : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]inConnect-[***]Z950G/[***]4fb0-[***]70-[***]eb-[***]45-[***]fabf5"}])
Throttling: Rate exceeded
2021-05-03T21:21:08.742Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]nceHistory-[***]4TNUJT/[***]1850-[***]6d-[***]eb-[***]a7-[***]9077b"}])
2021-05-03T21:21:08.759Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]bleRequest-[***]OYPYS8/[***]6ea0-[***]fc-[***]eb-[***]65-[***]de975"}])
2021-05-03T21:21:08.775Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]ace-[***]5PWXQV/[***]ab00-[***]70-[***]eb-[***]b4-[***]eaed9"}])
2021-05-03T21:21:08.891Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]chUsageEvent-[***]BDHCXY/[***]e9d0-[***]df-[***]eb-[***]e9-[***]d258f"}])
2021-05-03T21:21:08.964Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:us-[***]st-[***]92:stack/[***]ify-[***]ce-[***]j-[***]143-[***]inConnect-[***]Z950G/[***]4fb0-[***]70-[***]eb-[***]45-[***]fabf5"}])
2021-05-03T21:21:09.626Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]ify-[***]json","Bucket":"[***]ify-[***]ce-[***]j-[***]143-[***]ment"}])
2021-05-03T21:21:14.464Z|error : amplify-provider-awscloudformation.push-resources.run([{"resourcesToBeCreated":[{"service":"[***]hAlarms","providerPlugin":"[***]rmation","dependsOn":[{"category":"function","resourceName":"[***]equest","attributes":["Name"]}],"resourceName":"[***]hAlarms","category":"custom"}],"resourcesToBeUpdated":[],"resourcesToBe[***][***][***]Synced":[],"resourcesToBeDeleted":[],"tagsUpdated":false,"allResources":[{"service":"Cognito","providerPlugin":"[***]rmation","dependsOn":[],"customAuth":false,"output":{"UserPoolId":"[***]s-[***]st-[***]MkoTj","AppClientIDWeb":"[***]c81b40lum5u","AppClientID":"[***]enl2t25rodh","HostedUIDomain":"[***]32782-[***]2782-[***]j","OAuthMetadata":"{\"AllowedOAuthFlows\":[\"code\"],\"AllowedOAuthScopes\":[\"phone\",\"email\",\"openid\",\"profile\",\"aws.cognito.signin.user.admin\"],\"CallbackURLs\":[\"com.peaksware.[***]ce://socialsignin/\"],\"LogoutURLs\":[\"com.peaksware.[***]ce://socialsignout/\"]}","UserPoolName":"[***]ce"},"lastPushTimeStamp":"2021-05-03T21:21:09.580Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-[***]ce-kj-153143-deployment/amplify-cfn-templates/auth/[***]ce-cloudformation-template.yml","logicalId":"[***][***]ce"},"resourceName":"[***]ce","category":"auth"},{"service":"Cognito","providerPlugin":"[***]rmation","dependsOn":[{"category":"auth","resourceName":"[***]ce","attributes":["UserPoolId"]}],"output":{},"lastPushTimeStamp":"2021-05-03T21:21:09.582Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/auth/auth-[***]le-template.yaml","logicalId":"[***]pple"},"resourceName":"apple","category":"auth"},{"service":"AppSync","providerPlugin":"[***]rmation","output":{"authConfig":{"defaultAuthentication":{"authenticationType":"AMAZON_COGNITO_USER_POOLS","userPoolConfig":{"userPoolId":"[***][***]ce"}},"additionalAuthenticationProviders":[{"authenticationType":"AWS_IAM"}]},"GraphQLAPIIdOutput":"[***]f7judvvpyda","GraphQLAPIEndpointOutput":"https://oegl47zfj5gnrkjjx3xcqwtsra.appsync-api.us-east-1.amazonaws.com/graphql"},"lastPushTimeStamp":"2021-05-03T21:21:09.584Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/api/cloudformation-template.json","logicalId":"[***]ace"},"resourceName":"[***]ce","category":"api"},{"service":"API Gateway","providerPlugin":"[***]rmation","dependsOn":[{"category":"function","resourceName":"[***]onnect","attributes":["Name","Arn"]}],"output":{"ApiName":"[***]onnect","RootUrl":"https://[***]0nid.execute-api.us-east-1.amazonaws.com/kj","ApiId":"lcvfs70nid"},"lastPushTimeStamp":"2021-05-03T21:21:09.586Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/api/[***]onnect-cloudformation-template.json","logicalId":"[***]Connect"},"resourceName":"[***]onnect","category":"api"},{"service":"API Gateway","providerPlugin":"[***]rmation","dependsOn":[{"category":"function","resourceName":"[***]eCat","attributes":["Name","Arn"]}],"output":{"ApiName":"[***]eCat","RootUrl":"https://[***]qrlb.execute-api.us-east-1.amazonaws.com/kj","ApiId":"1c9bweqrlb"},"lastPushTimeStamp":"2021-05-03T21:21:09.588Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/api/[***]eCat-cloudformation-template.json","logicalId":"[***]nueCat"},"resourceName":"[***]eCat","category":"api"},{"service":"API Gateway","providerPlugin":"[***]rmation","dependsOn":[{"category":"function","resourceName":"[***]onnect","attributes":["Name","Arn"]}],"output":{"ApiName":"[***]onnect","RootUrl":"https://[***]xyhh.execute-api.us-east-1.amazonaws.com/kj","ApiId":"[***]ke5m0xyhh"},"lastPushTimeStamp":"2021-05-03T21:21:09.589Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/api/[***]onnect-cloudformation-template.json","logicalId":"[***]Connect"},"resourceName":"[***]onnect","category":"api"},{"service":"AssetStore","providerPlugin":"[***]rmation","dependsOn":[],"output":{"BucketName":"[***]ce-[***]ets-[***]gpeaks-[***]om-[***]j","DistributionId":"[***]59FIM8","DistributionDomainName":"[***]oudfront.net"},"lastPushTimeStamp":"2021-05-03T21:21:09.591Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/asset/asset-[***]re-template.yaml","logicalId":"[***]tore"},"resourceName":"store","category":"asset"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"api","resourceName":"[***]ce","attributes":["GraphQLAPIIdOutput","GraphQLAPIEndpointOutput"]},{"category":"storage","resourceName":"[***]eHistory","attributes":["Name","Arn"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:[***]ce-[***]equest-[***]j","Name":"[***]ce-[***]equest-[***]j","LambdaExecutionRole":"[***]ceLambdaRole3aeb5546-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.593Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/function/[***]equest-cloudformation-template.json","logicalId":"[***]uleRequest"},"s3Bucket":{"deploymentBucketName":"[***]ify-[***]ce-[***]j-[***]143-[***]ment","s3Key":"[***]ify-[***]lds/[***]equest-[***]6e6a6b72-[***].zip"},"resourceName":"[***]equest","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"api","resourceName":"[***]ce","attributes":["GraphQLAPIIdOutput","GraphQLAPIEndpointOutput"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:[***]ce-[***]kRequest-[***]j","Name":"[***]ce-[***]kRequest-[***]j","LambdaExecutionRole":"paceLambdaRoleb0925631-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.594Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/function/[***]kRequest-cloudformation-template.json","logicalId":"[***]dbackRequest"},"s3Bucket":{"deploymentBucketName":"[***]ify-[***]ce-[***]j-[***]143-[***]ment","s3Key":"[***]ify-[***]lds/[***]kRequest-[***]37447378-[***].zip"},"resourceName":"[***]kRequest","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"api","resourceName":"pace","attributes":["GraphQLAPIIdOutput","GraphQLAPIEndpointOutput"]},{"category":"storage","resourceName":"[***]ionCache","attributes":["Name","Arn"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]onnect-[***]j","Name":"[***]ce-[***]onnect-[***]j","LambdaExecutionRole":"paceLambdaRole44713824-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.596Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/function/GarminConnect-cloudformation-template.json","logicalId":"[***]inConnect"},"s3Bucket":{"deploymentBucketName":"[***]ify-[***]ce-[***]j-[***]143-[***]ment","s3Key":"[***]ify-[***]lds/[***]onnect-[***]436d6d63-[***].zip"},"resourceName":"GarminConnect","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"function","resourceName":"[***]ageEvent","attributes":["Name"]},{"category":"api","resourceName":"pace","attributes":["GraphQLAPIIdOutput"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]hangeEvent-[***]j","Name":"[***]ce-[***]hangeEvent-[***]j","LambdaExecutionRole":"paceLambdaRole3e3e495a-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.598Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/[***]ify-[***]ce-[***]j-[***]143-[***]ment/amplify-cfn-templates/function/[***]hangeEvent-cloudformation-template.json","logicalId":"[***]onaChangeEvent"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]hangeEvent-[***]63565967-[***].zip"},"resourceName":"AthletePersonaChangeEvent","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]ageEvent-[***]j","Name":"[***]ce-[***]ageEvent-[***]j","LambdaExecutionRole":"paceLambdaRoleaa3b778d-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.601Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/function/[***]ageEvent-cloudformation-template.json","logicalId":"[***]chUsageEvent"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]ageEvent-[***]2f345754-[***].zip"},"resourceName":"StoreCoachUsageEvent","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"api","resourceName":"pace","attributes":["GraphQLAPIIdOutput","GraphQLAPIEndpointOutput"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]hangeEvent-[***]j","Name":"[***]ce-[***]hangeEvent-[***]j","LambdaExecutionRole":"paceLambdaRole8cf78945-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.603Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/function/[***]hangeEvent-cloudformation-template.json","logicalId":"[***]onChangeEvent"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]hangeEvent-[***]39757a50-[***].zip"},"resourceName":"AppConnectionChangeEvent","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"api","resourceName":"pace","attributes":["GraphQLAPIIdOutput","GraphQLAPIEndpointOutput"]}],"output":{},"lastPushTimeStamp":"2021-05-03T21:21:09.604Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/function/function-[***]eSamples-template.json","logicalId":"[***]FileSamples"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]eSamples-[***]6142306b-[***].zip"},"resourceName":"ProcessFileSamples","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"api","resourceName":"pace","attributes":["GraphQLAPIIdOutput"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]eCat-[***]j","Name":"[***]ce-[***]eCat-[***]j","LambdaExecutionRole":"paceLambdaRoleb802b8e1-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.606Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/function/RevenueCat-cloudformation-template.json","logicalId":"[***]venueCat"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]eCat-[***]6a324d62-[***].zip"},"resourceName":"RevenueCat","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"function","resourceName":"CoachFeedbackRequest","attributes":["Name"]},{"category":"api","resourceName":"pace","attributes":["GraphQLAPIIdOutput"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]ngeEvent-[***]j","Name":"[***]ce-[***]ngeEvent-[***]j","LambdaExecutionRole":"paceLambdaRolea6a48e75-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.608Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/function/[***]ngeEvent-cloudformation-template.json","logicalId":"[***]ChangeEvent"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]ngeEvent-[***]677a466e-[***].zip"},"resourceName":"WorkoutChangeEvent","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"api","resourceName":"pace","attributes":["GraphQLAPIIdOutput","GraphQLAPIEndpointOutput"]},{"category":"function","resourceName":"ScheduleRequest","attributes":["Name"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]angeEvent-[***]j","Name":"[***]ce-[***]angeEvent-[***]j","LambdaExecutionRole":"paceLambdaRole96dfcc5c-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.609Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/function/[***]angeEvent-cloudformation-template.json","logicalId":"[***]gChangeEvent"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]angeEvent-[***]73756845-[***].zip"},"resourceName":"SchedulingChangeEvent","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"api","resourceName":"pace","attributes":["GraphQLAPIIdOutput","GraphQLAPIEndpointOutput"]},{"category":"storage","resourceName":"[***]ionCache","attributes":["Name","Arn"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]onnect-[***]j","Name":"[***]ce-[***]onnect-[***]j","LambdaExecutionRole":"paceLambdaRolea86c38a3-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.611Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/function/StravaConnect-cloudformation-template.json","logicalId":"[***]vaConnect"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]onnect-[***]69613555-[***].zip"},"resourceName":"StravaConnect","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]equest-[***]j","Name":"[***]ce-[***]equest-[***]j","LambdaExecutionRole":"paceLambdaRole6f386ea1-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.613Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/function/[***]equest-cloudformation-template.json","logicalId":"[***]bleRequest"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]equest-[***]74573170-[***].zip"},"resourceName":"[***]equest","category":"function"},{"build":true,"providerPlugin":"[***]rmation","service":"Lambda","dependsOn":[{"category":"api","resourceName":"pace","attributes":["GraphQLAPIIdOutput","GraphQLAPIEndpointOutput"]},{"category":"function","resourceName":"[***]equest","attributes":["Name"]}],"output":{"Region":"us-east-1","Arn":"[***]mbda:us-[***]st-[***]unction:pace-[***]eEvent-[***]j","Name":"[***]ce-[***]eEvent-[***]j","LambdaExecutionRole":"paceLambdaRoled60f104c-kj"},"lastPushTimeStamp":"2021-05-03T21:21:09.614Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/function/[***]eEvent-cloudformation-template.json","logicalId":"[***]hangeEvent"},"s3Bucket":{"deploymentBucketName":"amplify-pace-kj-153143-deployment","s3Key":"[***]ify-[***]lds/[***]eEvent-[***]4e36626d-[***].zip"},"resourceName":"UserChangeEvent","category":"function"},{"service":"DynamoDB","providerPlugin":"[***]rmation","output":{"PartitionKeyName":"[***]k","Region":"us-east-1","Arn":"[***]amodb:us-[***]st-[***]92:table/[***]ce-[***]ionCache-[***]j","StreamArn":"[***]amodb:us-[***]st-[***]92:table/[***]ce-[***]ionCache-[***]j/[***]eam/[***]21-[***]4-[***]30.052","PartitionKeyType":"S","Name":"[***]ce-[***]ionCache-[***]j"},"lastPushTimeStamp":"2021-05-03T21:21:09.616Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/storage/[***]ionCache-cloudformation-template.json","logicalId":"[***]ctionCache"},"resourceName":"AppConnectionCache","category":"storage"},{"service":"DynamoDB","providerPlugin":"[***]rmation","output":{"PartitionKeyName":"[***]k","SortKeyName":"sk","SortKeyType":"S","Region":"us-east-1","Arn":"[***]amodb:us-[***]st-[***]92:table/[***]ce-[***]eHistory-[***]j","StreamArn":"[***]amodb:us-[***]st-[***]92:table/[***]ce-[***]eHistory-[***]j/[***]eam/[***]21-[***]3-[***]32.838","PartitionKeyType":"S","Name":"[***]ce-[***]eHistory-[***]j"},"lastPushTimeStamp":"2021-05-03T21:21:09.618Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/storage/[***]eHistory-cloudformation-template.json","logicalId":"[***]nceHistory"},"resourceName":"PerformanceHistory","category":"storage"},{"service":"QLDB","providerPlugin":"[***]rmation","output":{"RoyaltiesLedgerName":"[***]ce-[***]ties"},"lastPushTimeStamp":"2021-05-03T21:21:09.619Z","providerMetadata":{"s3TemplateURL":"https://s3.amazonaws.com/amplify-pace-kj-153143-deployment/amplify-cfn-templates/custom/[***]entStore-cloudformation-template.json","logicalId":"[***]EventStore"},"resourceName":"RoyaltiesEventStore","category":"custom"},{"service":"CloudWatchAlarms","providerPlugin":"[***]rmation","dependsOn":[{"category":"function","resourceName":"IterableRequest","attributes":["Name"]}],"resourceName":"CloudWatchAlarms","category":"custom"}]}])
YAMLException: unknown tag !<!ImportValue> (26:41)

 23 |  ... tMissingData: notBreaching
 24 |  ... istic: Sum
 25 |  ... tions:
 26 |  ... !ImportValue tools-AwsAlertsOk
-----------------------------------------^
 27 |  ... mActions:
 28 |  ... !ImportValue tools-AwsAlertsAlarm

Additional information
No response

@kjones thanks for reporting the issue, just to give some background, the CLI runs through all the templates it discovers to look for S3 deployment keys as we need to pass those in as parameters in case the template references some automatically uploaded resources.
I marked it as a bug as roundtripping YAML -> Object -> YAML should not have side effects.

@kjones as a temporary workaround, the longform of the intrinsic function (Fn::ImportValue) should work

This should be resolved in v4.50.2, so I'll close this out.

Sorry, https://github.com/aws-amplify/amplify-cli/pull/7245 has not been merged yet. Reopening and removing the pending-release label.


Loading (Static Query) issue

Hey guys,
I'm hitting an issue when trying to view my site. I got it working previously, but something changed and now the site just says Loading (Static Query)
I'm not sure what I did, but can see this https://github.com/gatsbyjs/gatsby/issues/6350 has already been raised here.
What do I need to do to get this working again?
Thanks

I fixed this by removing the StaticQuery and reverting to this.
const Layout = ({ children }) => (
    <LayoutContainer className="div">
                <Global styles={[globalStyles, typeStyles]} />
                <div className="Layout">
                    <Header />
                    <main className="Layout__content">
                        {children}
                    </main>
                    <Footer />
                </div>
            </LayoutContainer>
)

export const query = graphql`
        query SiteTitleQuery {
            site {
                siteMetadata {
                    title
                }
            }
        }
    `

Not sure what else there was to do, but it got it working.

This saved me, thanks!
Also I can confirm this error happened to me too on first project start. Using the code above fixes it.

Amazing @mcclntck. That did it. 🙌


Fixed typo

Thx for your contrib ;)
I have integrated your change manually because of you make pull request on master branch instead develop branch.


Created a mini Python Project of "Automated sorting of folder contents"

Python project of  "Automated sorting of folder contents".

add more information on readme file you can use images


Enable tests on Windows

Currently, the scaffolding used to run the tests is not working on Windows

I think I have most of the changes required to enable tests on Windows, but there're an unfortunate bump - an amusing MSVC++ bug:
tf_runtime\external\llvm-project\mlir\include\mlir/IR/Location.h(120): error C2440: 'reinterpret_cast': cannot convert from 'T' to 'uintptr_t'
        with
        [
            T=uintptr_t
        ]
tf_runtime\external\llvm-project\mlir\include\mlir/IR/Location.h(120): note: Conversion is a valid standard conversion, which can be performed implicitly or by use of static_cast, C-style cast or function-style cast
cpp_tests/bef_converter/bef_location_emitter_test.cc(56): note: see reference to function template instantiation 'mlir::Location mlir::OpaqueLoc::get<uintptr_t>(T,mlir::MLIRContext *)' being compiled
        with
        [
            T=uintptr_t
        ]


Enable breakpoints in rust files

Allow VS code extension users to add breakpoints to Rust file. This avoids configuring debug.allowBreakpointsEverywhere.

Allow VS code extension users to add breakpoints to Rust file. This avoids configuring debug.allowBreakpointsEverywhere.

Thanks!
What does it do? Breakpoints appear to work fine even without it:

The Microsoft C/C++ extension doesn't enable Rust breakpoints.

I'm not opposed to this, but I think it's better to add them there: you can debug Rust code without rust-analyzer, but you can't debug it without a debugging extension.


Sync with Fabric API 0.54.0

PS: This PR doesn't do a verbump, there are still plans to handle #12 (and maybe #15?) before a new release

Who's Working on this?


kong migrations reset returns an error

/kong # kong migrations reset -y
Database not bootstrapped, nothing to reset
/kong # echo $?
1
/kong #

If there is nothing to reset, the desired state has been achieved, and the command should return exit status 0

My intent is to do something like this:
kong migrations reset -y && kong migrations bootstrap

@Tieske we discussed offline about this and closed #5606 and decided to add -f to address this instead.

The -f is added to reset so closing this.

Oh, migrations bootstrap got -f, thus closing this.


ADD APPLICATIONS AND REQUESTS BACKEND MODULES

The following are the feature added to the project
#Provide Models and Controllers  that allow a  property owner to view applications and requests:
1. App/Model/ApplicationModel.php entails all the details of the data and the structure of the result obtained by using joins on the existing tables of the database
2.App/Controller/ Application.php calls functions from the Model and also will be used to resolve action from the  view files under the same circumstances

 1. App/Model/RequestsModel.php  defines the data obtained from joints between specific tables. Also provide details implementation of the structure of the data retrieved from the database
 2. App/Controller/Request.php resolve actions from the view files and also provide method that loads the view files

#Include Mock Up views (tables with the needed data)
App/Views/Application.php and App/Views/Requests.php
Some quick tables were implemented for testing purposes
CSS file under the folder Nyumbani/public/css
Authors: Joseph and Leo

In case of any issue or conflict with the existing code. Please mention the part/area concerned


Reset zoom, pitch and heading  upon city switch

Iteration on https://artsyproduct.atlassian.net/browse/LD-407
When interacting with the map, it's possible to get into a permutation of custom zoom, heading (rotating away from north), and pitch (tilting away from camera-pointing down)
For example, facing down Canal St towards the Manhattan Bridge.

Currently when we switch to another city, we reset the zoom, but leave the heading and pitch unchanged, which leads to an unexpected initial experience:

We can instead reset all three — zoom, pitch and heading in order to restore a neutral initial vantage point into the new city.
Furthermore, by taking advantage of an easing animation with a generous duration, we can also mitigate the perceived delays associated with the initial fetch of a new city's data.
Putting that all together looks something like this:

Duration is currently set to 2 seconds, but that's up for grabs of course.
I would love to see this bit of finish added to v1.1 IF it is reasonable to do so with solid Q/A. But if not, I don't want to rush things. Wondering what the best way to test this is outside of the beta. I looked into side-loading onto my own device but hit all kinds of walls with that. Would love some help if there's time tomorrow.

Fails

:no_entry_sign:

No CHANGELOG added.

  Generated by :no_entry_sign: dangerJS

Can you interact with the screen during this animation? (If you already had most of the same values then that 2 seconds is gonna feel like it's unresponsive)

Good point —  I was testing against the worst case, which benefits from a longer duration. Should test it with more typical cases and shorter durations too.

Example when only the zoom needs to change. Imho this 2s transition actually works well in conjunction with the spinner, but I'm open whatev duration people think is reasonable.

@l2succes and I tested on-device with with various permutations of city/zoom/pitch/heading.
We've decided to go with 1000ms for the transition duration.
Also noting that the final zoom level that results from this seems to be not fully deterministic, which is true of the current implementation as well.


Added function to check if modals or panes active in editor

Fixes #596
Description

Added: isEditorOverlaysActive method to check if any editor modals/panes are active

Checklist

[x] I have made corresponding changes to the documentation.
[x] I have added the necessary label (patch/minor/major - If package publish is required).

Reviewers
@AbhayVAshokan _a

@AbhayVAshokan _a Please verify the changes, Once this is merged I will start implementing this in neetoPlanner codebase.


Highlight enables features in cargo info

Problem
As described in #14141, the following thing should be displayed for features:

For features enabled by users, a + prefix and colored output are now used for better visibility.
For features enabled automatically, colored output is used to distinguish them.
For disabled features, non-colored output is used to clearly indicate their status.

The enabled/disabled features are ignored in the cargo info output. There is always just a "+" for default features. Enabled features via Cargo.toml are not displayed as enabled.
Steps
$ grep "^reqwest =" Cargo.toml
reqwest = { version = "*", features = ["blocking", "json", "cookies", "rustls-tls-native-roots"], default-features = false }

$ cargo +nightly info reqwest
reqwest #http #request #client
higher level HTTP client library
version: 0.12.8
license: MIT OR Apache-2.0
rust-version: 1.63.0
documentation: https://docs.rs/reqwest
repository: https://github.com/seanmonstar/reqwest
crates.io: https://crates.io/crates/reqwest/0.12.8
features:
 +default                             = [default-tls, charset, http2, macos-system-configuration]
  __tls                               = [dep:rustls-pemfile, tokio/io-util]
  charset                             = [dep:encoding_rs]
  default-tls                         = [dep:hyper-tls, dep:native-tls-crate, __tls, dep:tokio-native-tls]
  h2                                  = [dep:h2]
  http2                               = [h2, hyper/http2, hyper-util/http2, hyper-rustls?/http2]
  macos-system-configuration          = [dep:system-configuration]
  25 deactivated features
note: to see how you depend on reqwest, run `cargo tree --invert --package<EMAIL_ADDRESS>
Possible Solution(s)
No response
Notes
No response
Version
cargo 1.83.0-nightly (80d82ca22 2024-09-27)
release: 1.83.0-nightly
commit-hash: 80d82ca22abbee5fb7b51fa1abeb1ae34e99e88a
commit-date: 2024-09-27
host: x86_64-unknown-linux-gnu
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Fedora 41.0.0 (FortyOne) [64-bit]

That was stale information and we've only been supporting default atm.
The question is which set of features to be considered enabled

For the parent package
For all workspace members
Across the entire resolve graph

And what should we do when the package isn't depended on by you?

I have no experience with multiple workspace members, but here is what I expect:

1st column "+" and colored output for root dependencies (the same features which are shown when running "cargo add ")

$ cargo add reqwest
    Updating crates.io index
      Adding reqwest v0.12 to dependencies
             Features as of v0.12.0:
             + __rustls
             + __tls
             + blocking
             + cookies
             + json
             + rustls-pki-types
             + rustls-tls-native-roots
             24 deactivated features

for non-root dependencies enabling a feature, maybe add a list of these packages (maybe including their dependency path) behind the feature in parentheses or (in non-verbose mode) just print "enabled by X non-root dependencies)

(BTW: cargo add feature list is broken when using version="*" in Cargo.toml - I will open a separate ticket for this.)


docs: scrollbar-hide community presets

@reslear  I think this preset has too few preset rules and is more for customization.
I think you can send a PR to this community preset https://github.com/action-hong/unocss-preset-scrollbar.
/cc @action-hong

No, because many people do not need scrollbar customization, but only visual hiding. also my tailwind css plugin https://github.com/reslear/tailwind-scrollbar-hide most polular.
Example tailwind plugins:
scrollbar: https://www.npmjs.com/package/tailwind-scrollbar 54k downloads
scrollbar hide: https://www.npmjs.com/package/tailwind-scrollbar-hide 65k downloads

hi @antfu thanks, done, have a good day  :)


Home Page

An overview of the org as well  as summarize all the sections of the website with our goals:
Check:  GirlScript Chennai  Website for reference

Assign this to me !! Willing to work on it @smaranjitghose

Kindly assign is to me sir!
@smaranjitghose
Team Femmetech!

This will be continued with the new UI


Fix a corner case in stall detection

The waker at start is actually for self.next + wakers.len(), not self.next. The max_polled_idx case (line 284) can also put self.next in the list. Having two zeros in the list (when self.next is zero) results in an underflow computing num - 1 in to_ranges.
I am not sure how best to test this (either a regression test for the fix, or to make sure the change doesn't break anything else). But opening a PR anyways so it's less likely the issue just gets lost.

thanks for fixing it. I've never tested it properly, was waiting for https://github.com/tokio-rs/tracing/tree/master/tracing-mock to be released


Possible to deserialize into existing struct

Hello, is it possible to deserialize a serde_json::Value into an existing struct? Something along the lines of Golang's unmarshal for JSON?

If you mean taking a serde_json::Value and deserializing it into a struct, yes the method you want is from_value. The call will look like let s: MyStruct = try!(serde_json::from_value(v));
If you mean taking a serde_json::Value and deserializing it over top of an existing instance of a struct with some fields already populated, that is not supported. You should use #[serde(default="...")] attributes instead as illustrated here.

I am looking to use one struct as a temporary instance and then fill its' fields with a json, as opposed to creating a new instance each time. I see it is now supported. Thanks for the response.

I am looking to use one struct as a temporary instance and then fill its' fields with a json, as opposed to creating a new instance each time.

Is this for performance reasons? In Rust (unlike Java or Go) there is typically no performance penalty for creating a new instance of a struct vs reusing an existing one. Please don't make your code more confusing unless you have benchmarked the simple approach and find that creating instances is a bottleneck.

Not for performance. I have a use case where a json has portions of it that I deserialize to a serde_json::Value which is then matched to a struct by a String also in the json.
For example:
    "symbols": {
      "A": {
        "modifier": {
          "type": "exchange",
          "config": {
            "value": "a"
          }
        },
        "provider": {
          "type": "local",
          "config": {
            "path": "./a.txt"
          }
        }
      }

where  type is the name of the struct that i use stringify! to match against and then the config is the serde_json::Value that I use to populate the fields. I am attempting to pass these structs in to a macro
macro_rules! deploy {
    ($requisites: ident: $r: expr, $directives: ident: $d: expr, $($modifier: ty), * => $($provider: ty), * => $($deployer: ty), *) => {{
        ...
    }}
}

where I would like to create the structs one time and off load any future Values with the same type into that struct. Creating one struct at a time adds more complexity to my code in this case. I would like to "register" these structs as a sort of service but I cannot register them because the Value is not known until later in the code. Sure that makes zero sense without code but it is a bit of a WIP right now.

Got it, thanks for the explanation. Let us know if you get stuck or if there is anything Serde could provide to make this easier.

The option to deserialize into a temporary struct would be nice 😉

If it's not about performance, would this be sufficient?
fn deserialize_into<T>(v: serde_json::Value, t: &mut T) -> Result<(), serde_json::Error>
    where T: Deserialize
{
    *t = try!(serde_json::from_value(v));
    Ok(())
}

fn main() {
    let v: serde_json::Value = /* ... */;
    let mut s: Struct = /* ... */;
    deserialize_into(v, &mut s).unwrap();
}

I may still be misunderstanding the use case. It would help if you could give a function signature that you want.

This is exactly what I need! Things are a bit mixed around right now as I have been refactoring things to get around not having this so I can't test it immediately. Should this work as is?

Yes just copy the deserialize_into function into your code. I would prefer not to include it in Serde yet until we get some indication that this would be useful to more people than just you.

You can make it a little more readable by making it a method instead of a function.
Option 1:
trait DeserializeFrom: Deserialize {
    fn deserialize_from(&mut self, v: serde_json::Value) -> Result<(), serde_json::Error> {
        *self = try!(serde_json::from_value(v));
        Ok(())
    }
}
impl<T> DeserializeFrom for T where T: Deserialize {}

fn main() {
    let v: serde_json::Value = /* ... */;
    let mut s: Struct = /* ... */;
    s.deserialize_from(v).unwrap();
}

Option 2:
trait DeserializeInto {
    fn deserialize_into<T>(self, t: &mut T) -> Result<(), serde_json::Error>
        where T: Deserialize;
}

impl DeserializeInto for serde_json::Value {
    fn deserialize_into<T>(self, t: &mut T) -> Result<(), serde_json::Error>
        where T: Deserialize
    {
        *t = try!(serde_json::from_value(self));
        Ok(())
    }
}

fn main() {
    let v: serde_json::Value = /* ... */;
    let mut s: Struct = /* ... */;
    v.deserialize_into(&mut s).unwrap();
}

Thanks for the options! Here is a bit of a contrived example of a use case, but I am seeing now that it might now work as expected
#![feature(custom_derive)]

extern crate serde;
extern crate serde_json;
extern crate serde_macros;

use std::collections::HashMap;
use serde_json::Value;
use serde::de::Deserialize;

trait NameChanger {
    fn change(self: Box<Self>) -> String;
}

pub struct Registry {
    things: HashMap<String, Box<NameChanger>>,
}

impl Default for Registry {
    fn default() -> Registry {
        Registry {
            things: HashMap::new(),
        }
    }
}

#[derive(Serialize, Deserialize, Debug)]
pub struct Thing {
    name: String
}

impl Default for Thing {
    fn default() -> Thing {
        Thing {
            name: "Thingy".to_owned(),
        }
    }
}

impl NameChanger for Thing {
    fn change(self: Box<Self>) -> String {
        self.name + "thing"
    }

}

fn deserialize_into<T>(v: serde_json::Value, t: &mut T) -> Result<(), serde_json::Error>
    where T: Deserialize
{
    *t = try!(serde_json::from_value(v));
    Ok(())
}

fn get_value() -> Value {
    let s = "{\"name\": \"my name\"}";
    let value: Value = serde_json::from_str(s).unwrap();
    value
}

macro_rules! unload_those_things {
    ($($t:ty), * => $($e:expr), *) => {{
        let mut registry: Registry = Default::default();
        $(
            let t: $t = Default::default();
            registry.things.insert(stringify!($t).to_lowercase(), Box::new(t));
        )*

        $(
            let value = get_value();
            let name_changer = registry.things.get_mut($e).unwrap();
            deserialize_into(value, name_changer);
            // let name = name_changer.change();
            // println!("{}", name);
        )*
    }}
}

fn main() {
    unload_those_things!(Thing => "thing");
}

Can't deserialize a trait:
Compiling example v0.1.0 (file:///home/user/example)
src/main.rs:70:13: 70:29 error: the trait bound `NameChanger: std::marker::Sized` is not satisfied [E0277]
src/main.rs:70             deserialize_into(value, name_changer);
                        ^~~~~~~~~~~~~~~~
src/main.rs:78:5: 78:44 note: in this expansion of unload_those_things! (defined in src/main.rs)
src/main.rs:70:13: 70:29 help: run `rustc --explain E0277` to see a detailed explanation

src/main.rs:70:13: 70:29 note: `NameChanger` does not have a constant size known at compile-time
src/main.rs:70:13: 70:29 note: required because of the requirements on the impl of `serde::Deserialize` for `Box<NameChanger>`
src/main.rs:70:13: 70:29 note: required by `deserialize_into`
src/main.rs:70:13: 70:29 error: the trait bound `NameChanger: serde::Deserialize` is not satisfied [E0277]
src/main.rs:70             deserialize_into(value, name_changer);
                        ^~~~~~~~~~~~~~~~
src/main.rs:78:5: 78:44 note: in this expansion of unload_those_things! (defined in src/main.rs)
src/main.rs:70:13: 70:29 help: run `rustc --explain E0277` to see a detailed explanation
src/main.rs:70:13: 70:29 note: required because of the requirements on the impl of `serde::Deserialize` for `Box<NameChanger>`
src/main.rs:70:13: 70:29 note: required by `deserialize_into`
error: aborting due to 2 previous errors
error: Could not compile `example`.

I am imaging a library that allows arbitrary NameChangers to be passed in and utilized.

Here is a much simpler approach without Boxes, without registry, without deserialize_into, without trait objects. See if you can make this work for the real case.
#![feature(plugin, custom_derive)]
#![plugin(serde_macros)]

extern crate serde_json;
use serde_json::Value;

trait NameChanger {
    fn change(self) -> String;
}

#[derive(Serialize, Deserialize, Debug)]
pub struct Thing {
    name: String
}

impl NameChanger for Thing {
    fn change(self) -> String {
        self.name + "thing"
    }
}

fn get_value() -> Value {
    let s = "{\"name\": \"my name\"}";
    serde_json::from_str(s).unwrap()
}

macro_rules! unload_those_things {
    ($($t:ty),* => $($e:expr),*) => {{
        for ty in &[$($e),*] {
            let v = get_value();
            match *ty {
                $(
                    t if t == stringify!($t).to_lowercase() => {
                        let name_changer: $t = serde_json::from_value(v).unwrap();
                        let name = name_changer.change();
                        println!("{}", name);
                    }
                )*
                _ => panic!("unexpected thing: {}", ty)
            }
        }
    }}
}

fn main() {
    unload_those_things!(Thing => "thing");
}

A bit new to macros in Rust, didn't know I could match like this:
            match *ty {
                $(
                    t if t == stringify!($t).to_lowercase() => {
                        let name_changer: $t = serde_json::from_value(v).unwrap();
                        let name = name_changer.change();
                        println!("{}", name);
                    }
                )*
                _ => panic!("unexpected thing: {}", ty)
            }

Indeed this is a cleaner solution! Thanks for the help.


Autolink dependency of dependency

React Native version:
Run react-native info in your terminal and copy the results here.
System:
OS: Windows 10 10.0.19041
CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
Memory: 827.51 MB / 7.88 GB
Binaries:
Node: 14.5.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - C:\Program Files\nodejs\yarn.CMD
npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-201.87<IP_ADDRESS>42882
Visual Studio: Not Found
Languages:
Java: javac 15
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.0 => 0.64.0
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
1.I have created library with create-react-native-library
2.I have react-native-webview dependency and its got installed in node_modules but autolink is not happening  for react-native-webview
What is the solution for autolink of dependency of dependency

This is not currently supported, and is related to the CLI (hence I'm closing it)
There is an ongoing effort to support it here:

https://github.com/react-native-community/cli/pull/2054


DSA : Binary tree to DLL

Description 📜
Added documentation with implementation for Binary tree to DLL inplace conversion in Linked List folder.
Fixes #8070

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[x] DSA
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] JavaScript_#Domain
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@nimisha-yadav please review the PR.

Add references as requested.
Please check

Add references as well for your content.

Add references as requested.
Please check


update certificate endpoint api version

When using the option certs.use_k8s_cm: true the operator fails to create the cert for the kubernetes-dashboard because it still calls the v1beta1 endpoint forcertificates.k8s.io
Approving CSR
Problem calling '/apis/certificates.k8s.io/v1beta1/certificatesigningrequests/kubernetes-dashboard.kubernetes-dashboard.svc/approval' - 404
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}

Retrieving signed certificate
Problem calling '/apis/certificates.k8s.io/v1beta1/certificatesigningrequests/kubernetes-dashboard.kubernetes-dashboard.svc' - 404
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}

could you please update the operator so it uses the v1 endpoint or at least tries both?

We were actually thinking of removing that feature. The reason we originally built it was to make it easier to integrate with ingress controllers, but it turned out to not matter (and doesn't work for hosted clusters like eks). What was your goal by using certs signed by the kubernetes CA?

I had no specific goal in mind. I just noticed while trying out openunison and thought you might wanted to know. If you plan on removing it anyways that is fine with me.

I updated the name of this issue to reflect that we need to remove this feature since it's never used and as pointed out the API its using is out of date.  I'll keep this open until we officially remove it.

the latest version of our operator has removed this feature, closing


Storage::URL() returns the URL with '/storage/' appended in front.

Laravel Version:  5.4
PHP Version: 7
Database Driver & Version:

Description:
Calling Storage::URL returns the path of the file with '/storage/' appended in front, but only in artisan tinker
Steps To Reproduce:
Storage::URL(config('constants.PROJECT_LIST')."myfile"))
returns
/storage/C:\path\to\my\file\myfile
only in artisan tinker; doesn't work while the app is running (debug shows /storage/myfile only)

Please share more information about your issue, nobody can guess what's stored in your config('constants.PROJECT_LIST'), please share an example we can copy and paste in a fresh laravel installation to understand your issue.

Looks like it was some weird behavior from artisan tinker as I can not reproduce it.


RWA-2547: Fix idempotency functional test

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/RWA-2547
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ x ] No

Not needed as the Nightly master build runs without any issues.


Implement From<AccountId20> for Location

Motivation
Configuring FeeManager enforces the boundary Into<[u8; 32]> for the AccountId type.
Here is how it works currently:
Configuration:
    type FeeManager = XcmFeeManagerFromComponents<
        IsChildSystemParachain<primitives::Id>,
        XcmFeeToAccount<Self::AssetTransactor, AccountId, TreasuryAccount>,
    >;

XcmToFeeAccount struct:
/// A `HandleFee` implementation that simply deposits the fees into a specific on-chain
/// `ReceiverAccount`.
///
/// It reuses the `AssetTransactor` configured on the XCM executor to deposit fee assets. If
/// the `AssetTransactor` returns an error while calling `deposit_asset`, then a warning will be
/// logged and the fee burned.
pub struct XcmFeeToAccount<AssetTransactor, AccountId, ReceiverAccount>(
	PhantomData<(AssetTransactor, AccountId, ReceiverAccount)>,
);

impl<
		AssetTransactor: TransactAsset,
		AccountId: Clone + Into<[u8; 32]>,
		ReceiverAccount: Get<AccountId>,
	> HandleFee for XcmFeeToAccount<AssetTransactor, AccountId, ReceiverAccount>
{
	fn handle_fee(fee: Assets, context: Option<&XcmContext>, _reason: FeeReason) -> Assets {
		deposit_or_burn_fee::<AssetTransactor, _>(fee, context, ReceiverAccount::get());

		Assets::new()
	}
}

deposit_or_burn_fee() function:
/// Try to deposit the given fee in the specified account.
/// Burns the fee in case of a failure.
pub fn deposit_or_burn_fee<AssetTransactor: TransactAsset, AccountId: Clone + Into<[u8; 32]>>(
	fee: Assets,
	context: Option<&XcmContext>,
	receiver: AccountId,
) {
	let dest = AccountId32 { network: None, id: receiver.into() }.into();
	for asset in fee.into_inner() {
		if let Err(e) = AssetTransactor::deposit_asset(&asset, &dest, context) {
			log::trace!(
				target: "xcm::fees",
				"`AssetTransactor::deposit_asset` returned error: {:?}. Burning fee: {:?}. \
				They might be burned.",
				e, asset,
			);
		}
	}
}

In order to use another AccountId type (for example, 20 byte addresses for compatibility with Ethereum or Bitcoin), one has to duplicate the code as the following (roughly changing every 32 to 20):
/// A `HandleFee` implementation that simply deposits the fees into a specific on-chain
/// `ReceiverAccount`.
///
/// It reuses the `AssetTransactor` configured on the XCM executor to deposit fee assets. If
/// the `AssetTransactor` returns an error while calling `deposit_asset`, then a warning will be
/// logged and the fee burned.
pub struct XcmFeeToAccount<AssetTransactor, AccountId, ReceiverAccount>(
    PhantomData<(AssetTransactor, AccountId, ReceiverAccount)>,
);
impl<
        AssetTransactor: TransactAsset,
        AccountId: Clone + Into<[u8; 20]>,
        ReceiverAccount: Get<AccountId>,
    > HandleFee for XcmFeeToAccount<AssetTransactor, AccountId, ReceiverAccount>
{
    fn handle_fee(fee: XcmAssets, context: Option<&XcmContext>, _reason: FeeReason) -> XcmAssets {
        deposit_or_burn_fee::<AssetTransactor, _>(fee, context, ReceiverAccount::get());

        XcmAssets::new()
    }
}

pub fn deposit_or_burn_fee<AssetTransactor: TransactAsset, AccountId: Clone + Into<[u8; 20]>>(
    fee: XcmAssets,
    context: Option<&XcmContext>,
    receiver: AccountId,
) {
    let dest = AccountKey20 { network: None, key: receiver.into() }.into();
    for asset in fee.into_inner() {
        if let Err(e) = AssetTransactor::deposit_asset(&asset, &dest, context) {
            log::trace!(
                target: "xcm::fees",
                "`AssetTransactor::deposit_asset` returned error: {:?}. Burning fee: {:?}. \
                They might be burned.",
                e, asset,
            );
        }
    }
}

This results in code duplication, and it is not an elegant solution.
I submitted and merged https://github.com/paritytech/polkadot-sdk/pull/4959 which relaxed the trait bound for XcmFeeToAccount, and now it accepts everything that implements Get<Location>.
When this change is released in the next polkadot-sdk version:
AccountId20 should also implement From trait to Location in order to allow frontier users to easily configure FeeManager.

I'll soon submit the PR that solves this issue


Activities missing from IATI Tables

Data from multiple publishers is currently missing from IATI Tables.
It looks like it is all publishers after a certain point alphabetically (datasette query)

This seems to be okay this morning. I've added an Uptime Robot check that the last publisher alphabetically exists in that query.


Bundle not modifying config or injecting bundled .js into my application

Hi,
I ran gulp serve and then gulp bundle. It created a bundle called app-build.js and aurelia.js.
However when I reload the browser, it's still calling same amount of requests to get all the libraries and not the bundle.
Config.js seems untouched as well
Here is my bundle.js file
var gulp = require('gulp');
var bundler = require('aurelia-bundler');
var bundles = require('../bundles.json');

var config = {
  force: true,
  baseURL: '.',
  configPath: './config.js',
  bundles: bundles.bundles
};

gulp.task('bundle', ['unbundle', 'build'], function() {
  return bundler.bundle(config);
});

gulp.task('unbundle', function() {
  return bundler.unbundle(config);
});

and bundles.json file
{
  "bundles": {
    "dist/app-build": {
      "includes": [
        "[*]",
        "*.html!text",
        "*.css!text"
      ],
      "options": {
        "inject": true,
        "minify": true
      }
    },
    "dist/aurelia": {
      "includes": [
        "aurelia-framework",
        "aurelia-bootstrapper",
        "aurelia-fetch-client",
        "aurelia-router",
        "aurelia-animator-css",
        "aurelia-templating-binding",
        "aurelia-templating-resources",
        "aurelia-templating-router",
        "aurelia-loader-default",
        "aurelia-history-browser",
        "aurelia-logging-console",
        "bootstrap",
        "bootstrap/css/bootstrap.css!text"
      ],
      "options": {
        "inject": true,
        "minify": true
      }
    }
  }
}

What could have went wrong?
Thanks

update SystemJS with jspm dl-loader. update bundler to v0.3.0 and finally change [*] to [*.js] in the bundle config above.

I have a similar issue. I have the most recent version of SystemJS (0.19.17), am running v0.3.1 of the bundler, and have changed the [*] to [*.js], but still have the same file count requests.
My config and gulp process is as follows:
var gulp = require('gulp');
var bundler = require('aurelia-bundler');

var config = {
  force: true,
  baseURL: './wwwroot',
  configPath: './wwwroot/config.js',
  bundles: {
    "dist/app-build": {
      "includes": [
        "[*.js]",
        "*.svg!text",
        "*.html!text",
        "*.css!text"
      ],
      "options": {
        "inject": true,
        "minify": true
      }
    },
    "dist/aurelia": {
      "includes": [
        "aurelia-framework",
        "aurelia-bootstrapper",
        "aurelia-fetch-client",
        "aurelia-router",
        "aurelia-animator-css",
        "aurelia-templating-binding",
        "aurelia-templating-resources",
        "aurelia-templating-router",
        "aurelia-loader-default",
        "aurelia-history-browser",
        "aurelia-logging-console",
      ],
      "options": {
        "inject": true,
        "minify": true
      }
    }
  }
};

gulp.task('bundle', function() {
  return bundler.bundle(config);
});

gulp.task('unbundle', function() {
 return bundler.unbundle(config);
});

I thought I had this same issue a second ago (hence the link), however it was a stupid mistake on my end (I was loading up the wrong index file... yah...). There's always those pesky little errors that require what we call in the office 'stupid checks'. Can you confirm that you are actually loading up the same index file that you're using in the bundled project?
Also, have you tried unbundling, cleaning the dist folder, building, and then rebundling?

Closing this one. @zenvisuals If you still have the problem feel free to raise a new issue. Thanks.


Fix an implicit conversion warning

As one operand (the diff member of the float_num_t structure) is of a double float type, there is no point for the other operand to be of a single float type.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Okarss:x: MaJerleYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks. Which flag triggers this warning for test?

I'm using GCC v10.3 and the warning is triggered by the -Wdouble-promotion. This flag is very useful to catch all the unintended and unnecessary double precision operations. Especially important on devices with a single precision FPU or no FPU at all, but also helps improving efficiency on all devices.
I'll read that licence agreement first... :)


Modifier -> SwiftUI -> Modal presentations: presentationBackground(_:) [BETA]

Doc: https://developer.apple.com/documentation/swiftui/view/presentationbackground(_:)

[ ] Swift implementation
[ ] Elixir implementation

#655 for all presentationBackground modifiers. Rejecting


Remove package-based event systems from example scenes for Unity 2018 compat

Overview
Removes package-based event systems from example scenes for Unity 2018 compat. Also adds a pipeline validator to prevent additional scenes with this event system from being checked in.
Changes

Fixes: additional scenes with the behavior described in https://github.com/microsoft/MixedRealityToolkit-Unity/issues/9812

/azp run

Running an initial test pass with the new validator, which should fail! Then I'll fix the rest of the scenes.

/azp run


Build failed

I am following instructions under this link https://docs.google.com/document/d/1ebFQ-8BGoiamKO4K0ZiL1nH6b8wulJ-ORyZKiDEYi-8/edit
Also I add this setting to local.properties
readium.ndk_experimental=true readium.ndk_clang=false readium.ndk_skipARM=false readium.ndk_skipX86=false
I am getting the following error
Information:Gradle tasks [:app:generateArmDebugSources, :app:generateArmDebugAndroidTestSources, :app:prepareArmDebugUnitTestDependencies, :app:mockableAndroidJar, :app:compileArmDebugSources, :app:compileArmDebugAndroidTestSources, :app:compileArmDebugUnitTestSources, :lcp:generateArm7DebugSources, :lcp:prepareArm7DebugUnitTestDependencies, :lcp:mockableAndroidJar, :lcp:generateArm7DebugAndroidTestSources, :lcp:compileArm7DebugSources, :lcp:compileArm7DebugUnitTestSources, :lcp:compileArm7DebugAndroidTestSources] Error:error: 'C:/SDKLauncher-Android/readium-sdk/Platform/Android/epub3/libs/armeabi-v7a/libepub3.so', needed by '../../../../build/intermediates/cmake/arm7/debug/obj/armeabi-v7a/liblcp.so', missing and no known rule to make it Information:BUILD FAILED Information:Total time: 7.042 secs Information:1 error Information:0 warnings Information:See complete output in console
Could you help me ? Thank's

Because you are using the feature/lcp branch and readium-lcp-client which has a revised Gradle / CMake build system, you need to build the ReadiumSDK library separately (so that its independent reference from the LCP lib can be resolved adequately). See the additional local.properties configuration (readium.sdk_lib_dir and readium.sdk_include_dir), as per the README:
https://github.com/readium/readium-lcp-client/blob/develop/platform/android/README.md
https://github.com/readium/readium-lcp-client/blob/cd65c5e5615828c41aded659a9d518059149c1f9/platform/android/build.gradle#L25-L35
(note: the LCP lib can also be built without the ReadiumSDK, in cases where app developers only want to use a minimal version of the library without dependencies on the Readium engine)
You should be able to build the ReadiumSDK directly from its Gradle script (command line or Android Studio):å
https://github.com/readium/readium-sdk/blob/develop/Platform/Android/build.gradle
CC @clebeaupin @llemeurfr

Thank you @danielweck, your answer was helpful. I checked out develop branches for readium-lcp-client and redium-sdk, also I set addition properties that you adviced and was able to build this two projects.
But the problem with build of SDKLauncher-Android was still actual, I found the workaround - create necessary directory manualy and put there libepub3.so. With such solution gradle build passed.
Now I see FilePickerActivity with directory '/storage/emulated/0/epubtest' that looks empty instead of I put there two files - one *.epub and *.lcpl Then I click Ok button and app crashes with the following stacktrace
09-12 12:26:56.156 7660-7660/org.readium.sdk.android.launcher E/AndroidRuntime: FATAL EXCEPTION: main                                                                                Process: org.readium.sdk.android.launcher, PID: 7660                                                                                java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "__aeabi_memclr4" referenced by "/data/app/org.readium.sdk.android.launcher-2/lib/arm/libepub3.so"...                                                                                at java.lang.Runtime.loadLibrary(Runtime.java:372)                                                                                at java.lang.System.loadLibrary(System.java:1076)                                                                                at org.readium.sdk.android.EPub3.<clinit>(EPub3.java:44)                                                                                at org.readium.sdk.android.launcher.ContainerList.onCreate(ContainerList.java:252)                                                                                at android.app.Activity.performCreate(Activity.java:6251)                                                                                at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1107)                                                                                at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2369)                                                                                at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2476)                                                                                at android.app.ActivityThread.-wrap11(ActivityThread.java)                                                                                at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344)                                                                                at android.os.Handler.dispatchMessage(Handler.java:102)                                                                                at android.os.Looper.loop(Looper.java:148)                                                                                at android.app.ActivityThread.main(ActivityThread.java:5417)                                                                                at java.lang.reflect.Method.invoke(Native Method)                                                                                at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)                                                                                at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

note that the "launcher app" is really just a tech demo / integration examplar, so the FilePickerActivity is a quick and dirty UI to allow the user to choose a source folder on the device's internal storage (by default "epubtest").

what is your ndk version?

Android v6.0.1
NDK 15.2.4203891
It is very similar to this issue https://github.com/android-ndk/ndk/issues/126
I've checked the app on android 7.0 and it works

could you please try NDK 14 (GCC, we don't support Clang yet)

A lot of thanks @danielweck, will try it later, and provide you results, as now app is working with android v7
Now I am getting this toast when try to open lcpl file LCP EPUB license failed to initiate.
I suggest this is issut with root cetrificate and jks. Can you advice with this issue? And what is the connection between this certificate and the one on the lcp-server?

LCP server 10013 is with the certificate for "basic profile", which is the default one shipped with the launcher apps:
https://github.com/readium/SDKLauncher-OSX/blob/feature/lcp/Resources/LCP Root Certificate.crt
https://github.com/readium/SDKLauncher-iOS/blob/feature/lcp/Resources/LCP Root Certificate.crt
https://github.com/readium/SDKLauncher-Android/blob/feature/lcp/SDKLauncher-Android/app/src/main/assets/lcp/lcp.crt

LCP server 11013 is the "1.0 Profile". Please ask @llemeurfr :)

A ContentFilter object that supports byte ranges should only make RangeFilterContext objects.
What can be the reason of this exception and how it can be fixed?

@danielweck I just checked your suggestion about ndk14 and now app is works perfectly without any issues on android v6
Thank you a lot!

please contact EDRLab to have access to an LCP test server + exchange about your use case.

New issue about NDK 14 vs. 15
https://github.com/readium/SDKLauncher-Android/issues/125
Thank you!!

Possibly-related to NDK v14 vs. v15: https://github.com/readium/readium-lcp-client/issues/42


Grid Seq Rnd Gates

Thanks for the modules! I'm enjoying them.
I've noticed an issue with the gate buttons.
After I hit Rnd Gates it seems like the first click on a gate button that is off has no effect.
I'm on Rack 0.5.1 on Linux.

kinda funny but i think i finally fixed this 😆  it only took almost 3 years 😄

should be fixed - submitting to library

Thx @jeremywen !


Replace sidekiq with sucker_punch

This PR removes sidekiq with sucker_punch. Using sucker_punch we can get rid of separate sidekiq process that sucks a lot of memory.

ping @nevalla

Looks good. One minor thing: there are still some debug output in clean up job.


In a Listener the attribute "doc" is always empty for start_test

When creating a listener the event method receives a set of attributes. For the start_suite the doc attribute is filled with the Documentation of the suite.
For the start_test the doc attibute is there, but it's always empty. I would have expected this to be mapped to the Documentation of the individual test case. Below is the received attributes list.
'{critical': 'yes',
 'doc': u'Test case level documentation',
 'id': 's1-s1-t1',
 'longname': u'TestB.Test Pass Fail Etc Matrix.Force Pass trivial',
 'starttime': '20161229 11:12:53.311',
 'tags': [u'DIM-002',
          u'feature:my_first_feature',
          u'story:my_first_story',
          u'trivial'],
 'template': ''}

At least the included example clearly has doc with value Test case level documentation. Or did I get something wrong? Could you clarify?

You didn't get anything wrong and I'm virtually face slapping myself for not seeing this earlier when I posted it. Let's put it down as reduced focus due to a long session of intense working.
In any case, it now appears I've uncovered a bug in Allure, as there are two sections showing the test-case/test-steps overview and the description for the test-case tag is shown in one, but not the other. Seems that they're not reusing code as much as they should.

:)


Add color and material card

Definition of Done

[x] The code does at least what is defined in the ticket and does not affect any other functionality
[x] The PR has a meaningful title
[ ] There is a link to the issue-id
[x] There are no 'hacks' or shortcuts refactoring is preferred
[ ] The happy case of the app was tested at least once manually

Warning: The material page won't work after this PR

Wie besprochen verwerfen wir diesen PR und mergen in zusammen mit dem dev/material-card-PR (#998)


Add Win-N to shortcut guide

Description of the new feature / enhancement
WindowsKey+N opens notification center.
It took me a while to find out that a shortcut actually existed because PowerToys did not list this one.
Scenario when this would be used?
Open shortcut guide
Supporting information
Should not be much work, I would have contributed it myself, but I could not locate the right place in the code.

tracked by https://github.com/microsoft/PowerToys/issues/179 and #890
/dup https://github.com/microsoft/PowerToys/issues/179


Can't use 'npm run ios' to run SimpleApp

Before adding react-navigation in my project, when I follow the get started instructions of react-native project, I can use 'npm run ios' to test my app via Exop on iPhone simulator, and when I edit App.js (eg:change text), the preview will update automatically.
But after following instructions of https://reactnavigation.org/docs/intro, when I try 'npm run ios' in SimpleApp, it cannot run the project, instead I need to run 'react-native run-ios' to rebuild each time when I change my code. Does react-navigation support live reload? if not, do I need to run 'react-native run-ios' to refresh my app once I start using react-navigation?

Do you have live reloading enabled in your emulator? You can activate the React Native development settings on the emulator by pressing CMD + M on your keyboard while the iOS emulator is open. Let me know if this issue persists while live reloading is enabled.

did you yarn add the dependencies? you're less likely to run into issues if you yarn add install npm install

my step to reproduce it:

I followed the instruction of creating a new react-native project:

npm install -g create-react-native-app
create-react-native-app AwesomeProject
cd AwesomeProject

add react-navigation into my project:

npm install --save react-navigation

replace the App.js with the following (react-navigation HelloWorld):

import React from 'react';
import {
AppRegistry,
Text,
} from 'react-native';
import { StackNavigator } from 'react-navigation';
class HomeScreen extends React.Component {
static navigationOptions = {
title: 'Welcome',
};
render() {
return Hello, Navigation!;
}
}
const SimpleApp = StackNavigator({
Home: { screen: HomeScreen },
});
AppRegistry.registerComponent('SimpleApp', () => SimpleApp);
After replacing App.js, it is failed to run the app using 'npm run ios':
Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object. You likely forgot to export your component from the file it's defined in.
Check the render method of AwakeInDevApp.
in AwakeInDevApp (at registerRootComponent.js:21)
in ExponentRootComponent (at renderApplication.js:35)
in RCTView (at View.js:127)
in View (at AppContainer.js:93)
in RCTView (at View.js:127)
in View (at AppContainer.js:92)
in AppContainer (at renderApplication.js:34)
Note 1: I can run the app if I follow Hello Mobile Navigation in https://reactnavigation.org which uses 'react-native run-ios' instead of creating project from react-native tutorial (https://facebook.github.io/react-native/docs/getting-started.html)
Note 2: seems I started knowing what is happening, I'm using react-native, and should I use react-native-nagivation instead of react-nagivation?

@amuseamuse This is an issue with unclear documentation, and thank you for reporting this issue. When you use create-react-native-app, you do not need to use AppRegistry in your root component. This is handled for you. Your root component is exported, which means that some other file will be using AppRegistry. If you use the react-native CLI to generate a new project (i.e. react-native init HelloWorld), you will have to use AppRegistry to render your root component (similar to ReactDOM.render in React).
If you are using create-react-native-app, your root component would look like this, given your example:
import React from 'react';
import {
  Text,
  View
} from 'react-native';
import { StackNavigator } from 'react-navigation';

// Creating a simple Hello World home screen
class HomeScreen extends React.Component {
  static navigationOptions = {
    title: 'Welcome'
  };

  render() {
    return (
      <View>
        <Text>Hello, Navigation!</Text>
      </View>
    );
  }
}

const SimpleApp = StackNavigator({
  Home: { screen: HomeScreen }
});

export default SimpleApp; // Export your root navigator as the root component

I hope this resolves your issue and makes sense. The React Native documentation is pushing for new React Native users to get up and running with create-react-native-app, which is great. However, the original Hello World example for React Navigation was created before CRNA was released.
 I suggest that you look into both libraries and see which works best for your use case. React Navigation is still not yet at v1.0, although there is a roadmap.

Thanks @matthamil for that clarification.

How about when you use react-native init to create a project? I still can't register to AppRegistery.
Here is my route settings.
import React, { Component } from 'react';
import {
  AppRegistry,
  StyleSheet,
  Text,
  View
} from 'react-native';
import {StackNavigator} from "react-navigation"
import mainScreen from "./views/login/_mainScreen"

class MainScreen extends Component{
  render(){
    return(
      <mainScreen />
    );
  }
}
const ProjectApp = StackNavigator({
  Login_MS:{screen: MainScreen},
},
{
  initialRouteName:"Login_MS"
});

AppRegistry.registerComponent(  'LessonTimeApp', () => ProjectApp,);

It's saying expected a component class, got [object Object] when I try to run the app.
I've been using react-navigation on react-native version: 0.44 and It was working fine in my previous project. Now I'm using react-native 0.47.1 and I'm failing on react-navigation integration.
P.S: I checked react-navigation docs and there was no change.

Instructions will be clarified when #2491 is merged

Closing since #2491 was merged and the docs should be good now.


Documentation: Lack of a Quick Start/Basic Usage section

I've been learning about some lower level networking fundamentals recently and decided to learn hyper as a part of that. However, I've run into some problems with the lack of documentation.
For example, the page on docs.rs here, links to this page on GitHub to show an example usage of the client. However, I don't think this is as clear as it could be. For example, it doesn't make it clear that the TokioIo object is from a separate hyper_utils crate.
Additionally, I think a "quick start" page would be useful to help newcomers get up to speed on the basics. I think Axum does a good job with this.
Hyper's own website has great documentation on the other hand. I just think the docs.rs page would benefit from either some polishing or explicitly linking to Hyper's website (since docs.rs is the first place most developers will go for documentation on a rust library).

I wasn't sure if by closing you already found it, but there is https://hyper.rs/guides/1/
I'm always interested in making them better (https://github.com/hyperium/hyper/issues/3411), and also in making sure that it's easy to find them from where people would expect to find them.

Yeah, I found the hyper.rs site. It pretty much solves what I had initially submitted the issue for, but I also agree with (#3411) in that it could have some more extensive docs. After I get a chance to dive deeper into hyper, I also plan on contributing to the guides.


Firefox Issue

When you select the Year or the Month from the dropdown the calendar doesn't update.
This happen with FireFox Browser, on chrome works fine

Can you describe the problem in detail? @gabriel-cliqz

Hi!
We're also see this issues, and have cloned the repo to see if we can try and solve it. Don't know how far we will get (this is a timeboxed issue for us) but any work on this would be greatly appreciated by us too! :)

Hi there
@wethil on it now. We will release new alpha version asap ⌨


Not loading all data for isobaricInPa

I am attempting to read a GRIB2 file -https://nomads.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gfs.20210812/12/atmos/gfs.t12z.pgrb2full.0p50.f000 and to retrieve the isobaric wind data for both the u and v components.  Looking at this file in Panoply, I can see it contains all of the data I want (at all isobaric surface Pas from 1 to 100000).

However, when I load the file using your API, it only provides the data from Pa 1 to 70.
Msg 6: v-component of wind  isobaricInPa  1
Msg 10: v-component of wind  isobaricInPa  2
Msg 14: v-component of wind  isobaricInPa  4
Msg 18: v-component of wind  isobaricInPa  7
Msg 22: v-component of wind  isobaricInPa  10
Msg 26: v-component of wind  isobaricInPa  20
Msg 30: v-component of wind  isobaricInPa  40
Msg 34: v-component of wind  isobaricInPa  70
This is the query I am using:
var result = gribFile.Where(m => m.ParameterShortName == "u" && m.TypeOfLevel == "isobaricInPa");
I get the same result whether I try using the query or just iterating over all messages in the grib file object.
Any idea what I may be doing wrong?
Thanks!

@Wicrules  You might need to set the field EnableMultipleFieldMessages to true. I think by default it is set to false.

Thanks for getting back with me.  I'm pretty sure I tried that already and it didn't seem to make any difference.  I'll try it again just to double-check, however.
Chad
On Friday, August 13, 2021, 03:56:44 PM CDT, Robert @.***> wrote:
@Wicrules You might need to set the field EnableMultipleFieldMessages to true. I think by default it is set to false.
It is on the GribContext.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

OK, enabled multiple field messages and I'm getting the same results:
gribFile = new GribFile(files.First());
gribFile.Context.EnableMultipleFieldMessages = true;
var results = gribFile.Where(m => m.ParameterShortName == MESSAGE_WIND_U_SHORT_NAME && m.TypeOfLevel == "isobaricInPa");

Thoughts?   Other suggestions?
Thanks!


feat: enable versioning by default

Thoughts about this MR:

Should we make make siteVersion parameter optional on public methods getPage() and getPages()?
Should we make the siteVersion parameter an object parameter like this?

async getGlobalElement(id, { siteVersion })

I think for "internal methods" like getSwatch, we need to make the siteVersion required, because otherwise we will forget to pass the siteVersion when we use it internally. But for external API, I'm making those optional for now, not sure which one is better here.
On that note, it's so weird to have a Makeswift client, but we expose our "internal methods" like getSwatch. In the future, it might be better to separate Makeswift client that users will use, and a Makeswift client that we use internally.

It seems I'm still able to pass the siteVersions parameter to the API handler config, although it isn't having any effect.
Could we make this a type error?

export default MakeswiftApiHandler(process.env.MAKESWIFT_SITE_API_KEY!, {
  appOrigin: process.env.MAKESWIFT_APP_ORIGIN,
  apiOrigin: process.env.MAKESWIFT_API_ORIGIN,
  siteVersions: false,
})

It seems I'm still able to pass the siteVersions parameter to the API handler config, although it isn't having any effect.
Could we make this a type error?

export default MakeswiftApiHandler(process.env.MAKESWIFT_SITE_API_KEY!, {
  appOrigin: process.env.MAKESWIFT_APP_ORIGIN,
  apiOrigin: process.env.MAKESWIFT_API_ORIGIN,
  siteVersions: false,
})

Oh yeah thanks for catching that. I removed the type from manifest but I forgot to remove it from the API handler. Thanks!

It seems I'm still able to pass the siteVersions parameter to the API handler config, although it isn't having any effect.
Could we make this a type error?

export default MakeswiftApiHandler(process.env.MAKESWIFT_SITE_API_KEY!, {
  appOrigin: process.env.MAKESWIFT_APP_ORIGIN,
  apiOrigin: process.env.MAKESWIFT_API_ORIGIN,
  siteVersions: false,
})

Oh yeah thanks for catching that. I removed the type from manifest but I forgot to remove it from the API handler. Thanks!

alright, confirmed fixed!

Thoughts about this MR:

Should we make make siteVersion parameter optional on public methods getPage() and getPages()?

We could make it optional but it feels better to make them required so that it's harder to make a mistake

Should we make the siteVersion parameter an object parameter like this?

async getGlobalElement(id, { siteVersion })

I would prefer named parameter like this, yes, but it seems that they ended up being positional parameters.

I think for "internal methods" like getSwatch, we need to make the siteVersion required, because otherwise we will forget to pass the siteVersion when we use it internally. But for external API, I'm making those optional for now, not sure which one is better here.

Yes! For the same reasons we can make the external API required.

On that note, it's so weird to have a Makeswift client, but we expose our "internal methods" like getSwatch. In the future, it might be better to separate Makeswift client that users will use, and a Makeswift client that we use internally.

I think in the future we're wanting to expose all these things as part of our public API. But in the mean time, yeah, might make sense to have separate private and public clients.

It seems I'm still able to pass the siteVersions parameter to the API handler config, although it isn't having any effect.
Could we make this a type error?

export default MakeswiftApiHandler(process.env.MAKESWIFT_SITE_API_KEY!, {
  appOrigin: process.env.MAKESWIFT_APP_ORIGIN,
  apiOrigin: process.env.MAKESWIFT_API_ORIGIN,
  siteVersions: false,
})

We could do that by doing siteVersions?: never

I would prefer named parameter like this, yes, but it seems that they ended up being positional parameters.

During my first iteration, I actually used a named parameter. But I found it weird to mix a  required named parameter together with a required positional parameter like this:
async getGlobalElement(id, { siteVersion })

It's a different story if the named parameter is an optional parameter like connection. But we can always change this later.


Optionally open resume in a new tab

Added an option to open resume in a new tab. This can be turned on/off in config under newPage.

Thanks @MichalLauer  ❤


amplify init failed to complete and created an undeletable app

Describe the bug
I have been trying to learn amplify, and today in one of my tests amplify init failed to complete due to:
DeploymentBucket amplify-test-dev-155008-deployment already exists
After that I was unable to do anything so I deleted the folder and went into the amplify console to delete that test app (so I can restart) however it failed with the following error:
Removing backend envs for app d3c4lmqph8kggw failed
I tried to delete the dev env directly however that resulted in the following error:
Deleting backend env: dev from app: d3c4lmqph8kggw failed
Is there anything I can do to remove this app right now?
To Reproduce
Steps to reproduce the behavior:

Go to 'AWS Amplify Console'
Select the app you wish to delete
Click on 'Actions' and select 'Delete'
Type 'delete' on the input and click on 'Delete'
See error "Removing backend envs for app d3c4lmqph8kggw failed"

Expected behavior
The test app to be deleted
Screenshots

Desktop:

OS: manjaro
Browser firefox
Version 83.0

@joscarras could you try to delete the application from Amplify console again and see if it gets deleted now. We had some issue in the service earlier which is fixed now.
Could you also share the steps that you followed when you got the error  DeploymentBucket amplify-test-dev-155008-deployment already exists. The bucket names are generated to such that they are unique

The same situation.
I tried to create first demo project with Amplify CLI, but in init process my Mac was crashed! I tries it several times and always was this result. And now I have several non-deletable demo apps :((

@makiyov  Did your Mac crash or the CLI crash? And did you try to init the app in the same folder after the first crash

The same situation.
I tried to create first demo project with Amplify CLI, but in init process my Mac was crashed! I tries it several times and always was this result. And now I have several non-deletable demo apps :((

@makiyov Did your Mac crash or the CLI crash? And did you try to init the app in the same folder after the first crash

My Mac crash! I have iMac with macOS Big Sur 11.0.1.
But, my MacBook Pro with macOS Catalina 10.15.7 works fine!
And yes, I try to init this app several time, result was the same - crash.
A little bit later I will update iMar to Big Sur 11.1 11.1 and check again.

Do you have any stack trace from the crash? What version of NodeJs is being used? and what is the version of Amplify CLI do you have installed?

Do you have any stack trace from the crash? What version of NodeJs is being used? and what is the version of Amplify CLI do you have installed?

So, now I have already updated all of these components to: macOS Big Sur 11.1, Node v15.4.0, Amplify CLI 4.40.0.
And you know, after that everything works great!!!
Thanks a lot for your attention!
Having latest versions is so important :))

@joscarras The delete issue from the Amplify Console should be working now.
@makiyov Glad upgrading the CLI version worked for you :)

Apologies for the late response!
@yuth I was messing really hard around for testing / learning so I don't remember the steps I did to get the error, however it was probably something I did in my end and not something with amplify. If I remember correct I was messing with the build folder.
@kaustavghosh06 I was able to delete the project just fine today, so yes I can confirm this issue is resolved!
Thank you both for your assistance!