"Effect": "Allow",
              "Action": [
                "cognito-idp:DescribeUserPoolClient"
              ],
              "Resource": {
                "Fn::GetAtt": [
                  "UserPool",
                  "Arn"
                ]
              }
            }
          ]
        },
        "PolicyName": "dashbo85950a7d_userpoolclient_lambda_iam_policy",
        "Roles": [
          {
            "Ref": "UserPoolClientRole"
          }
        ]
      },
      "DependsOn": [
        "UserPoolClientLambda"
      ]
    },
    "UserPoolClientLogPolicy": {
      "Type": "AWS::IAM::Policy",
      "Properties": {
        "PolicyDocument": {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Action": [
                "logs:CreateLogGroup",
                "logs:CreateLogStream",
                "logs:PutLogEvents"
              ],
              "Resource": {
                "Fn::Sub": [
                  "arn:aws:logs:${region}:${account}:log-group:/aws/lambda/${lambda}:log-stream:*",
                  {
                    "region": {
                      "Ref": "AWS::Region"
                    },
                    "account": {
                      "Ref": "AWS::AccountId"
                    },
                    "lambda": {
                      "Ref": "UserPoolClientLambda"
                    }
                  }
                ]
              }
            }
          ]
        },
        "PolicyName": "dashbo85950a7d_userpoolclient_lambda_log_policy",
        "Roles": [
          {
            "Ref": "UserPoolClientRole"
          }
        ]
      },
      "DependsOn": [
        "UserPoolClientLambdaPolicy"
      ]
    },
    "UserPoolClientInputs": {
      "Type": "Custom::LambdaCallout",
      "Properties": {
        "ServiceToken": {
          "Fn::GetAtt": [
            "UserPoolClientLambda",
            "Arn"
          ]
        },
        "clientId": {
          "Ref": "UserPoolClient"
        },
        "userpoolId": {
          "Ref": "UserPool"
        }
      },
      "DependsOn": [
        "UserPoolClientLogPolicy"
      ],
      "UpdateReplacePolicy": "Delete",
      "DeletionPolicy": "Delete"
    },
    "IdentityPool": {
      "Type": "AWS::Cognito::IdentityPool",
      "Properties": {
        "AllowUnauthenticatedIdentities": {
          "Ref": "allowUnauthenticatedIdentities"
        },
        "CognitoIdentityProviders": [
          {
            "ClientId": {
              "Ref": "UserPoolClient"
            },
            "ProviderName": {
              "Fn::Sub": [
                "cognito-idp.${region}.amazonaws.com/${client}",
                {
                  "region": {
                    "Ref": "AWS::Region"
                  },
                  "client": {
                    "Ref": "UserPool"
                  }
                }
              ]
            }
          },
          {
            "ClientId": {
              "Ref": "UserPoolClientWeb"
            },
            "ProviderName": {
              "Fn::Sub": [
                "cognito-idp.${region}.amazonaws.com/${client}",
                {
                  "region": {
                    "Ref": "AWS::Region"
                  },
                  "client": {
                    "Ref": "UserPool"
                  }
                }
              ]
            }
          }
        ],
        "IdentityPoolName": {
          "Fn::If": [
            "ShouldNotCreateEnvResources",
            "dashboardXXXXXXXX_identitypool_85950a7d",
            {
              "Fn::Join": [
                "",
                [
                  "dashboardXXXXXXXX_identitypool_85950a7d__",
                  {
                    "Ref": "env"
                  }
                ]
              ]
            }
          ]
        }
      },
      "DependsOn": [
        "UserPoolClientInputs"
      ]
    },
    "IdentityPoolRoleMap": {
      "Type": "AWS::Cognito::IdentityPoolRoleAttachment",
      "Properties": {
        "IdentityPoolId": {
          "Ref": "IdentityPool"
        },
        "Roles": {
          "unauthenticated": {
            "Ref": "unauthRoleArn"
          },
          "authenticated": {
            "Ref": "authRoleArn"
          }
        }
      },
      "DependsOn": [
        "IdentityPool"
      ]
    }
  },
  "Outputs": {
    "IdentityPoolId": {
      "Description": "Id for the identity pool",
      "Value": {
        "Ref": "IdentityPool"
      }
    },
    "IdentityPoolName": {
      "Value": {
        "Fn::GetAtt": [
          "IdentityPool",
          "Name"
        ]
      }
    },
    "UserPoolId": {
      "Description": "Id for the user pool",
      "Value": {
        "Ref": "UserPool"
      }
    },
    "UserPoolArn": {
      "Description": "Arn for the user pool",
      "Value": {
        "Fn::GetAtt": [
          "UserPool",
          "Arn"
        ]
      }
    },
    "UserPoolName": {
      "Value": {
        "Ref": "userPoolName"
      }
    },
    "AppClientIDWeb": {
      "Description": "The user pool app client id for web",
      "Value": {
        "Ref": "UserPoolClientWeb"
      }
    },
    "AppClientID": {
      "Description": "The user pool app client id",
      "Value": {
        "Ref": "UserPoolClient"
      }
    },
    "AppClientSecret": {
      "Value": {
        "Fn::GetAtt": [
          "UserPoolClientInputs",
          "appSecret"
        ]
      },
      "Condition": "ShouldOutputAppClientSecrets"
    },
    "CreatedSNSRole": {
      "Description": "role arn",
      "Value": {
        "Fn::GetAtt": [
          "SNSRole",
          "Arn"
        ]
      }
    }
  }
}

your-project/#current-cloud-backend/auth/your-project/cli-inputs.json
{
  "version": "1",
  "cognitoConfig": {
    "identityPoolName": "dashboardXXXXXXX_identitypool_85950a7d",
    "allowUnauthenticatedIdentities": false,
    "resourceNameTruncated": "dashbo85950a7d",
    "userPoolName": "dashboardXXXXXXX_userpool_85950a7d",
    "autoVerifiedAttributes": [
      "email"
    ],
    "mfaConfiguration": "OFF",
    "mfaTypes": [
      "SMS Text Message"
    ],
    "smsAuthenticationMessage": "Your authentication code is {####}",
    "smsVerificationMessage": "Your verification code is {####}",
    "emailVerificationSubject": "Your verification code",
    "emailVerificationMessage": "Your verification code is {####}",
    "defaultPasswordPolicy": false,
    "passwordPolicyMinLength": 8,
    "passwordPolicyCharacters": [],
    "requiredAttributes": [
      "email",
      "name"
    ],
    "aliasAttributes": [],
    "userpoolClientGenerateSecret": false,
    "userpoolClientRefreshTokenValidity": 30,
    "userpoolClientWriteAttributes": [
      "email"
    ],
    "userpoolClientReadAttributes": [
      "email"
    ],
    "userpoolClientLambdaRole": "dashbo85950a7d_userpoolclient_lambda_role",
    "userpoolClientSetAttributes": false,
    "sharedId": "85950a7d",
    "resourceName": "dashboardXXXXXXX",
    "authSelections": "identityPoolAndUserPool",
    "useDefault": "default",
    "usernameAttributes": [
      "email"
    ],
    "userPoolGroups": true,
    "adminQueries": false,
    "triggers": {
      "PostConfirmation": [
        "custom"
      ]
    },
    "hostedUI": false,
    "userPoolGroupList": [
      "Admin",
      "Agent",
      "Client"
    ],
    "serviceName": "Cognito",
    "usernameCaseSensitive": false,
    "useEnabledMfas": false,
    "authRoleArn": {
      "Fn::GetAtt": [
        "AuthRole",
        "Arn"
      ]
    },
    "unauthRoleArn": {
      "Fn::GetAtt": [
        "UnauthRole",
        "Arn"
      ]
    },
    "breakCircularDependency": true,
    "dependsOn": [
      {
        "category": "function",
        "resourceName": "dashboardXXXXXXXdPostConfirmation",
        "triggerProvider": "Cognito",
        "attributes": [
          "Arn",
          "Name"
        ]
      }
    ],
    "permissions": [],
    "authTriggerConnections": "[\n  {\n    \"triggerType\": \"PostConfirmation\",\n    \"lambdaFunctionName\": \"dashboardforninjagqlXXXXXXXXdPostConfirmation\"\n  }\n]",
    "authProviders": [],
    "parentStack": {
      "Ref": "AWS::StackId"
    }
  }
}

your-project/#current-cloud-backend/auth/your-project/build/your-project-cloudformation-template.json
{
  "Description": "Amplify Cognito Stack for AWS Amplify CLI",
  "AWSTemplateFormatVersion": "2010-09-09",
  "Parameters": {
    "env": {
      "Type": "String"
    },
    "functiondashboardXXXXXXPostConfirmationArn": {
      "Type": "String",
      "Default": "functiondashboardXXXXXXXXdPostConfirmationArn"
    },
    "functiondashboardXXXXXXXXPostConfirmationName": {
      "Type": "String",
      "Default": "functiondashboardXXXXXXXdPostConfirmationName"
    },
    "identityPoolName": {
      "Type": "String"
    },
    "allowUnauthenticatedIdentities": {
      "Type": "String"
    },
    "resourceNameTruncated": {
      "Type": "String"
    },
    "userPoolName": {
      "Type": "String"
    },
    "autoVerifiedAttributes": {
      "Type": "CommaDelimitedList"
    },
    "mfaConfiguration": {
      "Type": "String"
    },
    "mfaTypes": {
      "Type": "CommaDelimitedList"
    },
    "smsAuthenticationMessage": {
      "Type": "String"
    },
    "smsVerificationMessage": {
      "Type": "String"
    },
    "emailVerificationSubject": {
      "Type": "String"
    },
    "emailVerificationMessage": {
      "Type": "String"
    },
    "defaultPasswordPolicy": {
      "Type": "String"
    },
    "passwordPolicyMinLength": {
      "Type": "String"
    },
    "passwordPolicyCharacters": {
      "Type": "CommaDelimitedList"
    },
    "requiredAttributes": {
      "Type": "CommaDelimitedList"
    },
    "aliasAttributes": {
      "Type": "CommaDelimitedList"
    },
    "userpoolClientGenerateSecret": {
      "Type": "String"
    },
    "userpoolClientRefreshTokenValidity": {
      "Type": "String"
    },
    "userpoolClientWriteAttributes": {
      "Type": "CommaDelimitedList"
    },
    "userpoolClientReadAttributes": {
      "Type": "CommaDelimitedList"
    },
    "userpoolClientLambdaRole": {
      "Type": "String"
    },
    "userpoolClientSetAttributes": {
      "Type": "String"
    },
    "sharedId": {
      "Type": "String"
    },
    "resourceName": {
      "Type": "String"
    },
    "authSelections": {
      "Type": "String"
    },
    "useDefault": {
      "Type": "String"
    },
    "usernameAttributes": {
      "Type": "CommaDelimitedList"
    },
    "userPoolGroups": {
      "Type": "String"
    },
    "adminQueries": {
      "Type": "String"
    },
    "triggers": {
      "Type": "String"
    },
    "hostedUI": {
      "Type": "String"
    },
    "userPoolGroupList": {
      "Type": "CommaDelimitedList"
    },
    "serviceName": {
      "Type": "String"
    },
    "usernameCaseSensitive": {
      "Type": "String"
    },
    "useEnabledMfas": {
      "Type": "String"
    },
    "authRoleArn": {
      "Type": "String"
    },
    "unauthRoleArn": {
      "Type": "String"
    },
    "breakCircularDependency": {
      "Type": "String"
    },
    "dependsOn": {
      "Type": "CommaDelimitedList"
    },
    "permissions": {
      "Type": "CommaDelimitedList"
    },
    "authTriggerConnections": {
      "Type": "CommaDelimitedList"
    },
    "authProviders": {
      "Type": "CommaDelimitedList"
    },
    "parentStack": {
      "Type": "String"
    }
  },
  "Conditions": {
    "ShouldNotCreateEnvResources": {
      "Fn::Equals": [
        {
          "Ref": "env"
        },
        "NONE"
      ]
    },
    "ShouldOutputAppClientSecrets": {
      "Fn::Equals": [
        {
          "Ref": "userpoolClientGenerateSecret"
        },
        true
      ]
    }
  },
  "Resources": {
    "SNSRole": {
      "Type": "AWS::IAM::Role",
      "Properties": {
        "AssumeRolePolicyDocument": {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Sid": "",
              "Effect": "Allow",
              "Principal": {
                "Service": "cognito-idp.amazonaws.com"
              },
              "Action": [
                "sts:AssumeRole"
              ],
              "Condition": {
                "StringEquals": {
                  "sts:ExternalId": "dashbo85950a7d_role_external_id"
                }
              }
            }
          ]
        },
        "Policies": [
          {
            "PolicyDocument": {
              "Version": "2012-10-17",
              "Statement": [
                {
                  "Effect": "Allow",
                  "Action": [
                    "sns:Publish"
                  ],
                  "Resource": "*"
                }
              ]
            },
            "PolicyName": "dashbo85950a7d-sns-policy"
          }
        ],
        "RoleName": {
          "Fn::If": [
            "ShouldNotCreateEnvResources",
            "dashbo85950a7d_sns-role",
            {
              "Fn::Join": [
                "",
                [
                  "sns85950a7d",
                  {
                    "Fn::Select": [
                      3,
                      {
                        "Fn::Split": [
                          "-",
                          {
                            "Ref": "AWS::StackName"
                          }
                        ]
                      }
                    ]
                  },
                  "-",
                  {
                    "Ref": "env"
                  }
                ]
              ]
            }
          ]
        }
      }
    },
    "UserPool": {
      "Type": "AWS::Cognito::UserPool",
      "Properties": {
        "AutoVerifiedAttributes": [
          "email"
        ],
        "EmailVerificationMessage": {
          "Ref": "emailVerificationMessage"
        },
        "EmailVerificationSubject": {
          "Ref": "emailVerificationSubject"
        },
        "MfaConfiguration": {
          "Ref": "mfaConfiguration"
        },
        "Policies": {
          "PasswordPolicy": {
            "MinimumLength": {
              "Ref": "passwordPolicyMinLength"
            },
            "RequireLowercase": false,
            "RequireNumbers": false,
            "RequireSymbols": false,
            "RequireUppercase": false
          }
        },
        "Schema": [
          {
            "Mutable": true,
            "Name": "name",
            "Required": true
          }
        ],
        "SmsAuthenticationMessage": {
          "Ref": "smsAuthenticationMessage"
        },
        "SmsConfiguration": {
          "ExternalId": "dashbo85950a7d_role_external_id",
          "SnsCallerArn": {
            "Fn::GetAtt": [
              "SNSRole",
              "Arn"
            ]
          }
        },
        "SmsVerificationMessage": {
          "Ref": "smsVerificationMessage"
        },
        "UsernameAttributes": {
          "Ref": "usernameAttributes"
        },
        "UsernameConfiguration": {
          "CaseSensitive": false
        },
        "UserPoolName": {
          "Fn::If": [
            "ShouldNotCreateEnvResources",
            {
              "Ref": "userPoolName"
            },
            {
              "Fn::Join": [
                "",
                [
                  {
                    "Ref": "userPoolName"
                  },
                  "-",
                  {
                    "Ref": "env"
                  }
                ]
              ]
            }
          ]
        }
      }
    },
    "UserPoolClientWeb": {
      "Type": "AWS::Cognito::UserPoolClient",
      "Properties": {
        "UserPoolId": {
          "Ref": "UserPool"
        },
        "ClientName": "dashbo85950a7d_app_clientWeb",
        "RefreshTokenValidity": {
          "Ref": "userpoolClientRefreshTokenValidity"
        }
      },
      "DependsOn": [
        "UserPool"
      ]
    },
    "UserPoolClient": {
      "Type": "AWS::Cognito::UserPoolClient",
      "Properties": {
        "UserPoolId": {
          "Ref": "UserPool"
        },
        "ClientName": "dashbo85950a7d_app_client",
        "GenerateSecret": {
          "Ref": "userpoolClientGenerateSecret"
        },
        "RefreshTokenValidity": {
          "Ref": "userpoolClientRefreshTokenValidity"
        }
      },
      "DependsOn": [
        "UserPool"
      ]
    },
    "UserPoolClientRole": {
      "Type": "AWS::IAM::Role",
      "Properties": {
        "AssumeRolePolicyDocument": {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Principal": {
                "Service": "lambda.amazonaws.com"
              },
              "Action": "sts:AssumeRole"
            }
          ]
        },
        "RoleName": {
          "Fn::If": [
            "ShouldNotCreateEnvResources",
            {
              "Ref": "userpoolClientLambdaRole"
            },
            {
              "Fn::Join": [
                "",
                [
                  "upClientLambdaRole85950a7d",
                  {
                    "Fn::Select": [
                      3,
                      {
                        "Fn::Split": [
                          "-",
                          {
                            "Ref": "AWS::StackName"
                          }
                        ]
                      }
                    ]
                  },
                  "-",
                  {
                    "Ref": "env"
                  }
                ]
              ]
            }
          ]
        }
      },
      "DependsOn": [
        "UserPoolClient"
      ]
    },
    "UserPoolClientLambda": {
      "Type": "AWS::Lambda::Function",
      "Properties": {
        "Code": {
          "ZipFile": "const response = require('cfn-response');\nconst aws = require('aws-sdk');\nconst identity = new aws.CognitoIdentityServiceProvider();\nexports.handler = (event, context, callback) => {\n  if (event.RequestType == 'Delete') {\n    response.send(event, context, response.SUCCESS, {});\n  }\n  if (event.RequestType == 'Update' || event.RequestType == 'Create') {\n    const params = {\n      ClientId: event.ResourceProperties.clientId,\n      UserPoolId: event.ResourceProperties.userpoolId,\n    };\n    identity\n      .describeUserPoolClient(params)\n      .promise()\n      .then(res => {\n        response.send(event, context, response.SUCCESS, { appSecret: res.UserPoolClient.ClientSecret });\n      })\n      .catch(err => {\n        response.send(event, context, response.FAILED, { err });\n      });\n  }\n};\n"
        },
        "Role": {
          "Fn::GetAtt": [
            "UserPoolClientRole",
            "Arn"
          ]
        },
        "Handler": "index.handler",
        "Runtime": "nodejs12.x",
        "Timeout": 300
      },
      "DependsOn": [
        "UserPoolClientRole"
      ]
    },
    "UserPoolClientLambdaPolicy": {
      "Type": "AWS::IAM::Policy",
      "Properties": {
        "PolicyDocument": {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Action": [
                "cognito-idp:DescribeUserPoolClient"
              ],
              "Resource": {
                "Fn::GetAtt": [
                  "UserPool",
                  "Arn"
                ]
              }
            }
          ]
        },
        "PolicyName": "dashbo85950a7d_userpoolclient_lambda_iam_policy",
        "Roles": [
          {
            "Ref": "UserPoolClientRole"
          }
        ]
      },
      "DependsOn": [
        "UserPoolClientLambda"
      ]
    },
    "UserPoolClientLogPolicy": {
      "Type": "AWS::IAM::Policy",
      "Properties": {
        "PolicyDocument": {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Action": [
                "logs:CreateLogGroup",
                "logs:CreateLogStream",
                "logs:PutLogEvents"
              ],
              "Resource": {
                "Fn::Sub": [
                  "arn:aws:logs:${region}:${account}:log-group:/aws/lambda/${lambda}:log-stream:*",
                  {
                    "region": {
                      "Ref": "AWS::Region"
                    },
                    "account": {
                      "Ref": "AWS::AccountId"
                    },
                    "lambda": {
                      "Ref": "UserPoolClientLambda"
                    }
                  }
                ]
              }
            }
          ]
        },
        "PolicyName": "dashbo85950a7d_userpoolclient_lambda_log_policy",
        "Roles": [
          {
            "Ref": "UserPoolClientRole"
          }
        ]
      },
      "DependsOn": [
        "UserPoolClientLambdaPolicy"
      ]
    },
    "UserPoolClientInputs": {
      "Type": "Custom::LambdaCallout",
      "Properties": {
        "ServiceToken": {
          "Fn::GetAtt": [
            "UserPoolClientLambda",
            "Arn"
          ]
        },
        "clientId": {
          "Ref": "UserPoolClient"
        },
        "userpoolId": {
          "Ref": "UserPool"
        }
      },
      "DependsOn": [
        "UserPoolClientLogPolicy"
      ],
      "UpdateReplacePolicy": "Delete",
      "DeletionPolicy": "Delete"
    },
    "IdentityPool": {
      "Type": "AWS::Cognito::IdentityPool",
      "Properties": {
        "AllowUnauthenticatedIdentities": {
          "Ref": "allowUnauthenticatedIdentities"
        },
        "CognitoIdentityProviders": [
          {
            "ClientId": {
              "Ref": "UserPoolClient"
            },
            "ProviderName": {
              "Fn::Sub": [
                "cognito-idp.${region}.amazonaws.com/${client}",
                {
                  "region": {
                    "Ref": "AWS::Region"
                  },
                  "client": {
                    "Ref": "UserPool"
                  }
                }
              ]
            }
          },
          {
            "ClientId": {
              "Ref": "UserPoolClientWeb"
            },
            "ProviderName": {
              "Fn::Sub": [
                "cognito-idp.${region}.amazonaws.com/${client}",
                {
                  "region": {
                    "Ref": "AWS::Region"
                  },
                  "client": {
                    "Ref": "UserPool"
                  }
                }
              ]
            }
          }
        ],
        "IdentityPoolName": {
          "Fn::If": [
            "ShouldNotCreateEnvResources",
            "dashboardforninjagql85950a7d_identitypool_85950a7d",
            {
              "Fn::Join": [
                "",
                [
                  "dashboardforninjagql85950a7d_identitypool_85950a7d__",
                  {
                    "Ref": "env"
                  }
                ]
              ]
            }
          ]
        }
      },
      "DependsOn": [
        "UserPoolClientInputs"
      ]
    },
    "IdentityPoolRoleMap": {
      "Type": "AWS::Cognito::IdentityPoolRoleAttachment",
      "Properties": {
        "IdentityPoolId": {
          "Ref": "IdentityPool"
        },
        "Roles": {
          "unauthenticated": {
            "Ref": "unauthRoleArn"
          },
          "authenticated": {
            "Ref": "authRoleArn"
          }
        }
      },
      "DependsOn": [
        "IdentityPool"
      ]
    }
  },
  "Outputs": {
    "IdentityPoolId": {
      "Description": "Id for the identity pool",
      "Value": {
        "Ref": "IdentityPool"
      }
    },
    "IdentityPoolName": {
      "Value": {
        "Fn::GetAtt": [
          "IdentityPool",
          "Name"
        ]
      }
    },
    "UserPoolId": {
      "Description": "Id for the user pool",
      "Value": {
        "Ref": "UserPool"
      }
    },
    "UserPoolArn": {
      "Description": "Arn for the user pool",
      "Value": {
        "Fn::GetAtt": [
          "UserPool",
          "Arn"
        ]
      }
    },
    "UserPoolName": {
      "Value": {
        "Ref": "userPoolName"
      }
    },
    "AppClientIDWeb": {
      "Description": "The user pool app client id for web",
      "Value": {
        "Ref": "UserPoolClientWeb"
      }
    },
    "AppClientID": {
      "Description": "The user pool app client id",
      "Value": {
        "Ref": "UserPoolClient"
      }
    },
    "AppClientSecret": {
      "Value": {
        "Fn::GetAtt": [
          "UserPoolClientInputs",
          "appSecret"
        ]
      },
      "Condition": "ShouldOutputAppClientSecrets"
    },
    "CreatedSNSRole": {
      "Description": "role arn",
      "Value": {
        "Fn::GetAtt": [
          "SNSRole",
          "Arn"
        ]
      }
    }
  }
}

@voyagebagage
OK, I think I might be able to help. These are the key parts of how you files look now:
your-project/backend/auth/your-project/cli-inputs.json
{
...
"requiredAttributes": ["name"],
...
}
your-project/backend/auth/your-project/build/your-project-cloudformation-template.json
{
...
"Schema": [
{
"Mutable": true,
"Name": "name",
"Required": true
}
],
...
}
your-project/#current-cloud-backend/auth/your-project/cli-inputs.json
{
...
"requiredAttributes": [
"email",
"name"
],
...
}
your-project/#current-cloud-backend/auth/your-project/build/your-project-cloudformation-template.json
{
...
"Schema": [
{
"Mutable": true,
"Name": "name",
"Required": true
}
],
...
}
Right.  Your first pair does, second doesn't. My guess is you added "email" to your-project/#current-cloud-backend/auth/your-project/cli-inputs.json? Check against your user pool or source control and revert the file that changed.
Secondly, the files in #current-cloud-backend represent what's currently live. You need to change the other pair to match this pair.
In short, I think if you remove "email" from your-project/#current-cloud-backend/auth/your-project/cli-inputs.json it will work.
Try that, hope it works

@DuncanHouston
I didn't add "email" like I said it is required because when I do like you suggest and remove it I have that error:
Cognito configuration in the cloud has drifted from local configuration. Present changes cannot be pushed until drift is fixed. requiredAttributes requested is ["name"], but ["email","name"] is required by Cognito configuration. Update /Users/sedatif2/iCloud Drive (Archive)/Documents/DEV-World/dashboard/amplify/backend/auth/dashboardXXXXX/cli-inputs.json to continue.
when I remove it and do my amplify push --yes at the fetching time I get that error and the "email" puts itself back in the file and the error shows up
but I'm not sure to understand you when you say:

Check against your user pool or source control and revert the file that changed.

check in the console ? what is source control ?
Thanks anyway for your help

@DuncanHouston I didn't add "email" like I said it is required because when I do like you suggest and remove it I have that error:
Cognito configuration in the cloud has drifted from local configuration. Present changes cannot be pushed until drift is fixed. requiredAttributes requested is ["name"], but ["email","name"] is required by Cognito configuration. Update /Users/sedatif2/iCloud Drive (Archive)/Documents/DEV-World/dashboard/amplify/backend/auth/dashboardXXXXX/cli-inputs.json to continue.
when I remove it and do my amplify push --yes at the fetching time I get that error and the "email" puts itself back in the file and the error shows up
but I'm not sure to understand you when you say:

Check against your user pool or source control and revert the file that changed.

check in the console ? what is source control ?
Thanks anyway for your help

I'm trying to get this to work might be a solution

@voyagebagage I believe I may have been in a similar situation as you and I was able to work through it. The following worked for me:

Revert to the amplify-cli version that was being used before trying to update (in my case 7.6.8)
Edit the cli-inputs.json to remove the problem requiredAttributes (the ones not in the cloudformation template)
amplify push
Update amplify-cli (in my case to 7.6.15)
amplify push --force

@voyagebagage then perhaps you should try adding email to your-project/#current-cloud-backend/auth/your-project/build/your-project-cloudformation-template.json, since removing it from your-project/#current-cloud-backend/auth/your-project/cli-inputs.json didn't work. The 2 files need to match each other.
So you will be adding:
{
"Mutable": true,
"Name": "email",
"Required": true
}
to your-project/#current-cloud-backend/auth/your-project/build/your-project-cloudformation-template.json with a "," after the current single entry.
Try that.

@voyagebagage then perhaps you should try adding email to your-project/#current-cloud-backend/auth/your-project/build/your-project-cloudformation-template.json, since removing it from your-project/#current-cloud-backend/auth/your-project/cli-inputs.json didn't work. The 2 files need to match each other.
So you will be adding: { "Mutable": true, "Name": "email", "Required": true } to your-project/#current-cloud-backend/auth/your-project/build/your-project-cloudformation-template.json with a "," after the current single entry.
Try that.

this I tried before and still :
UPDATE_FAILED      UserPool AWS::Cognito::UserPool Wed Feb 09 2022 14:21:00 GMT+0100 (heure normale d’Europe centrale) Invalid AttributeDataType input, consider using the provided AttributeDataType enum. (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException; Request ID: 29185cd8-8b7c-445e-9b7f-1e01ea55c45f; Proxy: null)

@voyagebagage I believe I may have been in a similar situation as you and I was able to work through it. The following worked for me:

Revert to the amplify-cli version that was being used before trying to update (in my case 7.6.8)
Edit the cli-inputs.json to remove the problem requiredAttributes (the ones not in the cloudformation template)
amplify push
Update amplify-cli (in my case to 7.6.15)
amplify push --force

now downgrading doesn't work any CLI cmd through me the error:
Invalid feature flag configuration
These feature flags are defined in the "amplify/cli.json" configuration file and are unknown to the currently running Amplify CLI:

graphqltransformer.showfieldauthnotification

This issue likely happens when the project has been pushed with a newer version of Amplify CLI, try updating to a newer version.
Learn more about feature flags: https://docs.amplify.aws/cli/reference/feature-flags
I think I will restart my project only solution left

well I got this when I pushed --force might be a problem of iCloud directory

So it looks like I'm having this issue again. Two weeks ago I solved this same problem by following @jladdison's solution. Today I came back to publish some changes, before that I was requested to update the cli version to the 7.6.15 version.
When I try to do amplify push I get the following error:
Cognito configuration in the cloud has drifted from local configuration. Present changes cannot be pushed until drift is fixed. requiredAttributes requested is ["phone_number"], but ["email","family_name","given_name","name","phone_number"] is required by Cognito configuration. Update your_amplify_project/amplify/backend/auth/my_userpool/cli-inputs.json to continue.
And here comes the weirdest part of it all, my Cognito configuration in the AWS Management Console asks only for phone_number:

If I check my amplify/#current-cloud-backend/auth/my_userpool/cli-inputs.json everything looks right:
"requiredAttributes": ["phone_number"]
Also, my amplify/#current-cloud-backend/auth/my_userpool/buildmy_userpool-UserPool-cloudformation-template.json has only the phone_number attribute declared:
"Schema": [           {             "Mutable": true,             "Name": "phone_number",             "Required": true           } ],
When I do amplify push with this configuration (it should work since the only required attribute is the phone_number!) I get the following error:
Invalid AttributeDataType input, consider using the provided AttributeDataType enum. (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException
Finally, if I go to my Stack Detail -> Parameters in the CloudFormation Console I see the following info:

I think this is the first time in this thread that we mention this last part Stack-related. I think the error comes from this drift, but I do not know whether we can modify this stack or how this happened. I'm just sharing all this documentation so we can solve it.
I'm going to keep looking for a solution for this.

@d-cifuentes does it still happen if you remove your amplify dir and re-pull?

Yes, I have just tried that and is really weird. I did remove the whole amplify folder and pulled again, then I added a new environment variable for one of my functions and pushed again to try.
This is the status of all of my resources in this amplify project:

There is no change in the Auth section!

Ok, so I found the solution for this error. While reviewing the error logs I found out this message:
An error occurred during the push operation: Resource is not in the state stackUpdateComplete
Googling it I found this StackOverflow question from two years ago, the answer states that we can try and run amplify update auth.
From here I followed these steps:

Walkthrough all the auth configurations
Do not change anything of your current configuration, just press enter
Reached the 'Do you want to specify the user attributes this app can read and write?' question and selected yes
In the 'Specify write attributes' section, all of the required attributes for sign up were selected and I kept them that way
Finally, pushed again and it worked

It looks like updating the auth configuration and re-writing the configuration we selected in the creation of the user pool solves the drift problem.
I hope this can help you guys.

@d-cifuentes thanks for your solution, I try removing the the amplify dir and update auth like you suggested but still doesn't work for me

I am stuck on this...can't go forward or backwards...

Looks like a lot of others are having the issue here: https://github.com/aws/aws-cdk/issues/8585

So the current template has:
"Schema": [
{
"Mutable": true,
"Name": "phone_number",
"Required": true
}
],
and the one I am generating has:
"Schema": [
{
"Mutable": true,
"Name": "email",
"Required": true
},
{
"Mutable": true,
"Name": "family_name",
"Required": true
},
{
"Mutable": true,
"Name": "given_name",
"Required": true
},
{
"Mutable": true,
"Name": "phone_number",
"Required": true
}
],
The console shows all four items as required...
Removing them results in an error, that I need all four...
Having them results in the AttributeDataType input error...
I have pulled...and same result...

I have two custom fields, not sure if they are impacting this as well...

team provider seems a bit weird:
"jcmobile": {
"facebookAppId": "xxx",
"googleClientId": "xxx.apps.googleusercontent.com"
},
"userPoolGroups": {},
"true": {
"facebookAppId": "xxx",
"googleClientId": "xxx.apps.googleusercontent.com"
}

@GeorgeBellTMH I have exactly the same problem. My previous schema is:
"Schema": [
{
"Mutable": true,
"Name": "family_name",
"Required": true
}
]
and my new schema is:
    "Schema": [
      {
        "Mutable": true,
        "Name": "email",
        "Required": true
      },
      {
        "Mutable": true,
        "Name": "given_name",
        "Required": true
      },
      {
        "Mutable": true,
        "Name": "family_name",
        "Required": true
      }
    ],

and I've made no change to the cli-inputs except upgrade amplify-cli

So, my workaround was to amplify override auth...then manually set the schema to the old settings, and ensure the read/write attributes include my custom attributes...
import { AmplifyAuthCognitoStackTemplate } from "@aws-amplify/cli-extensibility-helper"
export function override(resources: AmplifyAuthCognitoStackTemplate) {
resources.userPool.schema = resources.userPool.schema = [
{ name: "phone_number", required: true, mutable: true },
]
resources.userPoolClient.readAttributes = [
"address",
"birthdate",
"email",
"family_name",
"middle_name",
"gender",
"locale",
"given_name",
"name",
"nickname",
"phone_number",
"preferred_username",
"picture",
"profile",
"updated_at",
"website",
"zoneinfo",
"email_verified",
"phone_number_verified",
"custom:orgName",
"custom:isOrg",
]
resources.userPoolClient.writeAttributes = [
"address",
"birthdate",
"middle_name",
"gender",
"locale",
"name",
"nickname",
"preferred_username",
"picture",
"profile",
"updated_at",
"website",
"zoneinfo",
"email",
"family_name",
"given_name",
"phone_number",
"custom:orgName",
"custom:isOrg",
]
resources.userPoolClientWeb.readAttributes = [
"address",
"birthdate",
"email",
"family_name",
"middle_name",
"gender",
"locale",
"given_name",
"name",
"nickname",
"phone_number",
"preferred_username",
"picture",
"profile",
"updated_at",
"website",
"zoneinfo",
"email_verified",
"phone_number_verified",
"custom:orgName",
"custom:isOrg",
]
resources.userPoolClientWeb.writeAttributes = [
"address",
"birthdate",
"middle_name",
"gender",
"locale",
"name",
"nickname",
"preferred_username",
"picture",
"profile",
"updated_at",
"website",
"zoneinfo",
"email",
"family_name",
"given_name",
"phone_number",
"custom:orgName",
"custom:isOrg",
]
}

@GeorgeBellTMH
This works perfectly, thank you so much!
I'll try and track down exactly which version of the amplify cli was used to produce my original cloudformation template so the developers can reproduce the drift bug.

@voyagebagage I believe I may have been in a similar situation as you and I was able to work through it. The following worked for me:

Revert to the amplify-cli version that was being used before trying to update (in my case 7.6.8)
Edit the cli-inputs.json to remove the problem requiredAttributes (the ones not in the cloudformation template)
amplify push
Update amplify-cli (in my case to 7.6.15)
amplify push --force

@jeremy-white THANKS! This did it for me.
The only missing step is to remove the two lines the new CLI version added to amplify/cli.json after downgrading to the previous version.
My problem was:

#current-cloud-backend CF template contained only phone_number
All other CF templates and cli-inputs contained both phone_number and email
Removing email from cli-inputs-json resulted in drift error message when using current (7.6.23) amplify-cli
But it worked when I removed the attribute and pushed using the CLI 7.6.5
Then I can update and do push with no problems

Thanks again @jeremy-white

@oookoook good to know, thanks.
I did go to 7.6.6 and didnt tried with the 5 unfortunately,
I rebuilt and know it is even better

Hey @Shomari and folks in the thread :wave: are you still experiencing this issue? There's quite a few comments here describing the affected workflow and a fix has since gone out for this issue, though I wanted to be sure this was taken care of 🙂

Just happened to me two days ago.
UPDATE_FAILED UserPool AWS::Cognito::UserPool Thu May 05 2022 15:38:02 GMT-0400 (Eastern Daylight Time) Invalid AttributeDataType input, consider using the provided AttributeDataType enum.
My #current-cloud-backend cloudformation-template.json lacks the email variable and only has name:
          {
            "Mutable": true,
            "Name": "name",
            "Required": true
          }

Both email and name are present in my local cloudformation-template.json. Both local and cloud cli-inputs.json have
"requiredAttributes": [
      "email",
      "name"
    ],

When I delete "name" from the local cli-inputs.json and push, I receive a drift error message.
Cognito configuration in the cloud has drifted from local configuration. Present changes cannot be pushed until drift is fixed. `requiredAttributes` requested is ["name"], but ["email","name"] is required by Cognito configuration.
I have tried downgrading the CLI and pushing to no avail.

Hi @josefaidt , I still have the issue even after updating the cli to v 8.1.0. Everything works fine, until i trigger the migration. After the mirgration the push fails with Invalid AttributeDataType input, consider using the provided AttributeDataType enum.
After removing the surplus requiredAttributes ('email' in  my case), I also receive a drift error message.

Adding these screenshots in case it helps at all.
Current develop env Congito required attributes -- which pushes just fine. (This env is a clone of my production env).

Current prod env Congito required attributes -- which fails. (Notice email is not checked anymore. Used to match develop env.)

Cognito required attributes according to Amplify Studio (which fails to deploy with the same Invalid AttributeDataType input error).

@josefaidt any update on this? I've been stuck here almost two weeks.

Hey @djsjr :wave: apologies for the delay! Are you still experiencing this? Do you have any custom attributes applied to your User Pool?

Hi @josefaidt. Yes I am still having the issue and no I do not have any custom attributes.
My current workaround is creating a temporary new environment from scratch (prod wouldn't clone - error) and importing the prod auth pool when adding auth plugin to the new environment. Seems to be working so far.

Hey @djsjr :wave: apologies for the delay here! Would you be open to  hopping on a quick call with us to take a look at this issue and identify the root cause and workaround? Please reach out to<EMAIL_ADDRESS>or ping me (josef) on our community Discord server

Hey @djsjr :wave: thanks for meeting with me! I've removed the pending-close... ahead of a deeper investigation

@djsjr @thingstiger @isaac-rosterlab anyway you can
1/ install the latest version of the CLI and re-try
2/ run amplify diagnose --send-report
3/ share your project ID (displayed by the Diagnose command) with us after you run diagnose

Initial fix addressed part of this. Additional documentation to describe high level approach for migration of user pool.

Hi, I've just setup a test environment for the migration of the user pool. If you want me to try something just let me know.
When updating the CLI from 7.6.24 to 8.0.3, and after running the auth migration, then amplify push will fail with "Invalid AttributeDataType input"
Unfortunately I can't use a CLI later than 8.0.3 because 8.1.0 introduces another cloudformation issue, and it's probably easier to only deal with one problem at a time.
I believe the reason why in our case #9590 doesn't work correctly is that we have no required attributes (which is a valid cognito configuration), so it will bail out before showing the drift message (see https://github.com/aws-amplify/amplify-cli/pull/9590/files#diff-954df67660f658f84cca55ff16ddea59e5a45c8bd547c19c0baf92b22ce3f7f6R284) and will then continue and later fall over when deploying the new cloudformation templates.

Hi,
@johnpc 's PR #9590 didn't detect the attribute drift for me (using cli 8.0.2). I agree with his analysis of the root cause.
I recommend to read #9590 and fully understand it.
Next you need to manually fix an incorrect parameters in your project config.

create an environment before running the auth migration (don't run any amplify auth commands)
update your amplify/backend/auth/webfrontendauth/parameters.json file to match what is configured in cognito (in my case i had to delete 'email', but this will be different for each app)
then trigger the auth migration by running amplify auth update. You will see a message that amplify wants to migrate your auth stack (this is important. if you don't see this message the migration has already been run or there is some other issue). By accepting all the defaults your auth stack should remain unchanged, but verify all the values. If you find a mismatch between what the CLI suggests and what you think your config should be, that would indicate a problem to look into.
Verify the changes to your files.
amplify push your changes, run your tests. if it all works merging into main should work fine.

Sorry for the long delay, but maybe this helps someone.

I have updated the cli to the newest version, but I still get the error. I have sent a diagnostic report.
Project ID: 5c8c983e49b7f9ef7d272af952c0ad21

What's the latest on this? We've hit this issue.
Similar to @Shomari, @dbeck121 , and @djsjr,  our deployed user pool, cli-inputs.json, and the #current-cloud-backend cloudformation JSON are all in sync as far as the requiredAttributes go (and other user pool config as far as I can tell).
As with @Shomari , it only manifested when we did amplify add analytics.
The issue occurs in amplify CLI 10.3.1 (downgrading to 7.6.8 gives us the same error).
amplify diagnose --send-report gives: Project Identifier: 85116e8e08029dc0bc4466b8b6573fec .
Below are our cli-inputs.json and root-cloudformation-stack.json.
(aside: This in our CloudFormation Template looks very suspect but I think it's unrelated: "dependsOn": "[object Object],[object Object],[object Object]",)
My amplify/backend/auth/bpedsysauth/cli-inputs.json :
{
  "version": "1",
  "cognitoConfig": {
    "identityPoolName": "bpedsys_identitypool",
    "allowUnauthenticatedIdentities": false,
    "resourceNameTruncated": "bpedsy2e2f5307",
    "userPoolName": "bpedsys_userpool",
    "autoVerifiedAttributes": [
      "email"
    ],
    "mfaConfiguration": "OPTIONAL",
    "mfaTypes": [
      "TOTP"
    ],
    "smsAuthenticationMessage": "Your authentication code is {####}",
    "smsVerificationMessage": "Your verification code is {####}",
    "emailVerificationSubject": "Your verification code",
    "emailVerificationMessage": "Your verification code is {####}",
    "defaultPasswordPolicy": false,
    "passwordPolicyMinLength": 8,
    "passwordPolicyCharacters": [
      "Requires Lowercase",
      "Requires Uppercase",
      "Requires Numbers"
    ],
    "requiredAttributes": [
      "name",
      "email"
    ],
    "aliasAttributes": [],
    "userpoolClientGenerateSecret": true,
    "userpoolClientRefreshTokenValidity": 30,
    "userpoolClientWriteAttributes": [
      "phone_number",
      "email",
      "name"
    ],
    "userpoolClientReadAttributes": [
      "email",
      "phone_number",
      "email_verified",
      "phone_number_verified"
    ],
    "userpoolClientLambdaRole": "bpedsy2e2f5307_userpoolclient_lambda_role",
    "userpoolClientSetAttributes": false,
    "authSelections": "identityPoolAndUserPool",
    "resourceName": "bpedsysauth",
    "useDefault": "manual",
    "userPoolGroupList": [
      "Admins",
      "Users"
    ],
    "userPoolGroups": false,
    "usernameAttributes": [
      "email"
    ],
    "verificationBucketName": "bpedsysauthverificationbucket",
    "adminQueries": true,
    "adminQueryGroup": "Admins",
    "hostedUI": false,
    "thirdPartyAuth": false,
    "triggers": {
      "CustomMessage": [
        "verification-link"
      ],
      "PostConfirmation": [
        "add-to-group"
      ],
      "PreTokenGeneration": [
        "alter-claims"
      ]
    },
    "authRoleArn": {
      "Fn::GetAtt": [
        "AuthRole",
        "Arn"
      ]
    },
    "unauthRoleArn": {
      "Fn::GetAtt": [
        "UnauthRole",
        "Arn"
      ]
    },
    "breakCircularDependency": false,
    "useEnabledMfas": false,
    "dependsOn": [
      {
        "category": "function",
        "resourceName": "bpedsysauthCustomMessage",
        "triggerProvider": "Cognito",
        "attributes": [
          "Arn",
          "Name"
        ]
      },
      {
        "category": "function",
        "resourceName": "bpedsysauthPostConfirmation",
        "triggerProvider": "Cognito",
        "attributes": [
          "Arn",
          "Name"
        ]
      },
      {
        "category": "function",
        "resourceName": "bpedsysauthPreTokenGeneration",
        "triggerProvider": "Cognito",
        "attributes": [
          "Arn",
          "Name"
        ]
      }
    ],
    "permissions": [
      "{\"policyName\":\"AddToGroupCognito\",\"trigger\":\"PostConfirmation\",\"effect\":\"Allow\",\"actions\":[\"cognito-idp:AdminAddUserToGroup\",\"cognito-idp:GetGroup\",\"cognito-idp:CreateGroup\"],\"resource\":{\"paramType\":\"!GetAtt\",\"keys\":[\"UserPool\",\"Arn\"]}}"
    ],
    "authTriggerConnections": [
      "{\"triggerType\":\"CustomMessage\",\"lambdaFunctionName\":\"bpedsysauthCustomMessage\"}",
      "{\"triggerType\":\"PostConfirmation\",\"lambdaFunctionName\":\"bpedsysauthPostConfirmation\"}",
      "{\"triggerType\":\"PreTokenGeneration\",\"lambdaFunctionName\":\"bpedsysauthPreTokenGeneration\"}"
    ],
    "serviceName": "Cognito",
    "authProviders": [],
    "parentStack": {
      "Ref": "AWS::StackId"
    }
  }
}

The relevant part of my amplify/#current-cloud-backend/awscloudformation/build/root-cloudformation-stack.json :
    "authbpedsysauth": {
      "Type": "AWS::CloudFormation::Stack",
      "Properties": {
        "TemplateURL": "https://s3.amazonaws.com/amplify-bpedsys-develop-174413-deployment/amplify-cfn-templates/auth/bpedsysauth-cloudformation-template.json",
        "Parameters": {
          "identityPoolName": "bpedsys_identitypool",
          "allowUnauthenticatedIdentities": false,
          "resourceNameTruncated": "bpedsy2e2f5307",
          "userPoolName": "bpedsys_userpool",
          "autoVerifiedAttributes": "email",
          "mfaConfiguration": "OPTIONAL",
          "mfaTypes": "TOTP",
          "smsAuthenticationMessage": "Your authentication code is {####}",
          "smsVerificationMessage": "Your verification code is {####}",
          "emailVerificationSubject": "Your verification code",
          "emailVerificationMessage": "Your verification code is {####}",
          "defaultPasswordPolicy": false,
          "passwordPolicyMinLength": 8,
          "passwordPolicyCharacters": "Requires Lowercase,Requires Uppercase,Requires Numbers",
          "requiredAttributes": "name,email",
          "aliasAttributes": "",
          "userpoolClientGenerateSecret": true,
          "userpoolClientRefreshTokenValidity": 30,
          "userpoolClientWriteAttributes": "phone_number,email,name",
          "userpoolClientReadAttributes": "email,phone_number,email_verified,phone_number_verified",
          "userpoolClientLambdaRole": "bpedsy2e2f5307_userpoolclient_lambda_role",
          "userpoolClientSetAttributes": false,
          "authSelections": "identityPoolAndUserPool",
          "resourceName": "bpedsysauth",
          "useDefault": "manual",
          "userPoolGroupList": "Admins,Users",
          "userPoolGroups": false,
          "usernameAttributes": "email",
          "verificationBucketName": "bpedsysauthverificationbucket",
          "adminQueries": true,
          "adminQueryGroup": "Admins",
          "hostedUI": false,
          "thirdPartyAuth": false,
          "triggers": "{\"CustomMessage\":[\"verification-link\"],\"PostConfirmation\":[\"add-to-group\"],\"PreTokenGeneration\":[\"alter-claims\"]}",
          "authRoleArn": {
            "Fn::GetAtt": [
              "AuthRole",
              "Arn"
            ]
          },
          "unauthRoleArn": {
            "Fn::GetAtt": [
              "UnauthRole",
              "Arn"
            ]
          },
          "breakCircularDependency": false,
          "useEnabledMfas": false,
          "dependsOn": "[object Object],[object Object],[object Object]",
          "permissions": "{\"policyName\":\"AddToGroupCognito\",\"trigger\":\"PostConfirmation\",\"effect\":\"Allow\",\"actions\":[\"cognito-idp:AdminAddUserToGroup\",\"cognito-idp:GetGroup\",\"cognito-idp:CreateGroup\"],\"resource\":{\"paramType\":\"!GetAtt\",\"keys\":[\"UserPool\",\"Arn\"]}}",
          "authTriggerConnections": "{\"triggerType\":\"CustomMessage\",\"lambdaFunctionName\":\"bpedsysauthCustomMessage\"},{\"triggerType\":\"PostConfirmation\",\"lambdaFunctionName\":\"bpedsysauthPostConfirmation\"},{\"triggerType\":\"PreTokenGeneration\",\"lambdaFunctionName\":\"bpedsysauthPreTokenGeneration\"}",
          "serviceName": "Cognito",
          "authProviders": "",
          "parentStack": {
            "Ref": "AWS::StackId"
          },
          "functionbpedsysauthCustomMessageArn": {
            "Fn::GetAtt": [
              "functionbpedsysauthCustomMessage",
              "Outputs.Arn"
            ]
          },
          "functionbpedsysauthCustomMessageName": {
            "Fn::GetAtt": [
              "functionbpedsysauthCustomMessage",
              "Outputs.Name"
            ]
          },
          "functionbpedsysauthPostConfirmationArn": {
            "Fn::GetAtt": [
              "functionbpedsysauthPostConfirmation",
              "Outputs.Arn"
            ]
          },
          "functionbpedsysauthPostConfirmationName": {
            "Fn::GetAtt": [
              "functionbpedsysauthPostConfirmation",
              "Outputs.Name"
            ]
          },
          "functionbpedsysauthPreTokenGenerationArn": {
            "Fn::GetAtt": [
              "functionbpedsysauthPreTokenGeneration",
              "Outputs.Arn"
            ]
          },
          "functionbpedsysauthPreTokenGenerationName": {
            "Fn::GetAtt": [
              "functionbpedsysauthPreTokenGeneration",
              "Outputs.Name"
            ]
          },
          "env": "develop"
        }
      }
    },

OK this still happens if I do nothing else other than change the order of requiredAttributes in cli-inputs.json from:
    "requiredAttributes": ["name", "email"]

to:
    "requiredAttributes": ["email", "name"]

I have the same problem after upgrading the Amplify cli from 9.2.1 to 10.4.0. Please help

I am also still getting it on 10.4.0. It seems not much is happening on this issue.

Hi team @josefaidt @Straubulous any updates on this issue, my team is blocked for almost two weeks now with this error. I have sent my project my project identification number: 8917f531808b98396e5b186f78b710ba. I have read through the whole discussions and none of the suggestions worked.
Thanks

Not currently feeling the "Customer Obsession" here.

I have talked for more than 10 engineers at aws support team and they haven't solved this issue, paying for more than 400 USD.
AWS support does not work.

Hi @cuneen @gorjant
I check your project Identifier.
Lets say your current required attributes are : [ 'email' , 'name'].
when upgraded to v7.3 to v7.6.9 due to a bug this required attributes in cfn changes to [ 'name'] which is a successful deployment.
After upgrading to version > v7.6.9 , amplify changes your required attributes back to normal which was previous : ['email' , 'name']. This deployment will result in same error Invalid AttributeDataType input, consider using the provided AttributeDataType enum.
Can you try to push by changing your cli-inputs.json and parameters.json to specific requited attribute which is [ 'name'] ?
As an example:
Current cli-inputs.json requited attributes: [ 'email' ,'name']
Change to cli-inputs.json requited attributes: [ ''name'] ;
Change parameters.json requited attributes: [ ''name'] ;
amplify push ( this should change schema section is user pool to only name attribute)
Let me know if these steps works for you ?
@owboateng
Your problem seems different by looking at project. Can you try removing userNameCaseSensitive field from cli-inputs.json and try to push again ?
Let me know if this works for you ?

Hi @akshbhu thanks for looking into this; We can't push right now as AWS Premium Support engineers are looking into this for us, but we did previously try what you described (based on @johnpc's comments above) and we still encountered the error.

Can you tell me which comment is this ?
I reproduced the issue with creating an amplify project with v4.5.x and upgrading to v7.3.0 ( which has the bug in required attributes)  (up till here push works fine )and after than upgrading to v10.5.1. I received similar error as above, which got resolved based on my comment above

Hi @akshbhu I don't think the message you're quoting was in this thread?

Can you tell me which comment is this ?
I reproduced the issue with creating an amplify project with v4.5.x and upgrading to v7.3.0 ( which has the bug in required attributes) (up till here push works fine )and after than upgrading to v10.5.1. I received similar error as above, which got resolved based on my comment above

Hi @cunneen
Apologies for being unclear.
When you mentioned :but we did previously try what you described (based on @johnpc's comments above) and we still encountered the error.
I was trying to confirm which comment was it in this thread.
Also this is my investigation on this issue : I reproduced the issue with creating an amplify project with v4.5.x and upgrading to v7.3.0 ( which has the bug in required attributes) (up till here push works fine )and after than upgrading to v10.5.1. I received similar error as above, which got resolved based on my comment above

Hi @akshbhu , sorry for misunderstanding earlier. AWS support resolved this for us; it looks like their resolution was similar to what you suggested as our cli-inputs.json file now only has ["name"] .
We're no longer encountering this issue; we're on v10.8.1 .

I used @julienlaurent-migso  solution and it worked.
went to the cli-inputs.json and inserted a newline then amplify push, which deployed properly.


setting USER_ID_FIELD with custom user

I would like to hide the database primary key of the User model. This is described in:
https://djoser.readthedocs.io/en/latest/settings.html#user-id-field
The documentation is not very clear on how to do this.
The CustomUser model is set via AUTH_USER_MODEL in the Django settings. The Djoser setting USER_ID_FIELD needs the full model (as it requires access to the models ._meta.pk). However, in the Django settings, that model is not yet available (error: django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.).
I do not see another method of defining the  USER_ID_FIELD.

How do I get this done?
Where do I set the USER_ID_FIELD setting, and if it is the Django settings then the question is:
How do I set the USER_ID_FIELD setting.

Oké. I figured it out.
It should be the name of the field as a string. Easy-peasy.
Will close.


DatabaseView throws error when starting with WITH statement

@DatabaseView("WITH lastMessages as (SELECT *, MAX(creationTimestamp) creationTimestamp FROM chat_message GROUP BY chatid) SELECT chat.*, lastMessages.* FROM chat INNER JOIN lastMessages ON chat.id = lastMessages.chatid")
class ChatWithLastMessage { ... }
This query throws an error: There is no SELECT query defined on the database view ChatWithLastMessage.
Rewriting to @DatabaseView("SELECT chat.*, (SELECT *, MAX(creationTimestamp) creationTimestamp FROM chat_message GROUP BY chatid) as lastMessages FROM chat INNER JOIN lastMessages ON chat.id = lastMessages.chatid") seems to work.

Thanks for your report. Common table expressions (temporary views created with "WITH") are currently not supported. I might be able to look into this in the next days. If you're interested in contributing, you can take a look at the ViewProcessor which currently checks if a view query starts with SELECT. You can find the relevant code here: https://github.com/vitusortner/floor/blob/1a49c0f3c3cc49e32846e15472ce13ecea2d6ce2/floor_generator/lib/processor/view_processor.dart#L49
A solution could be to allow queries staring with WITH that additionally contain at least one SELECT.

So I can basically just make a pull request changing:
if (query == null || !query.trimLeft().toLowerCase().startsWith('select')) {
  throw _processorError.missingQuery;
}

to
if (query == null || (!query.trimLeft().toLowerCase().startsWith('select') && !(query.trimLeft().toLowerCase().startsWith('with') && query.toLowerCase().contains('select')))) {
  throw _processorError.missingQuery;
}

?

Sounds perfect. Please don't forget to add tests 👌

Sounds perfect. Please don't forget to add tests 👌

I'll give it a shot... I've never actually written tests :p

Closed by #443

Closed by #443


Expansion board!

These are the goals with this approach:

Support split layouts (this will still require two boards and a TRRS connection)
Support larger non-split layouts (this requires more I/O pins than the 17 we have on the main board)
Keep the existing height of the board because I think making it any taller (with something with more I/O pins like an ATmega32A) would look bad
Allow connecting other devices that support I2C/TWI

The approach is to create a second PCB that's an expansion board and provides more I/O pins:

Probably 2U wide, same height as main board
Use the MCP23008
Connect with I2C/TWI to main board

Some details still need to be worked out.

Correction: we have 18 I/O pins available on the main board (I forgot we can use the pin that's connected to the boot switch as an I/O pin too!). 18 pins will support my desired use case (which is why I started designing this board in the first place) but will still not easily support a 60% layout without widening the PCB to include a port expander, or designing an expansion board with a port expander on it (this is pretty much done, I'm just not sure it's worth prototyping/printing).
To-do: post an interest check with pics of the completed 5x13 build with the new version of the PCB with 18 I/O pins, and include a question to gauge interest in a wider PCB or an expansion board to support 60%/TKL/etc. layouts.

Oh and I2C connections have been added. They're 2.54 mm pitch so you could add pin headers or sockets to them (or just solder wire directly to them), but headers or sockets won't be included in any kit.

Moving this to v2.1.0 milestone since v2.0.0 will work for my intended layout without an expansion board.


Can you add language shortnames to the documentation?

I often look through this page https://pygments.org/languages/ to check which languages I can use with Pygments, but it lacks an important piece of information - the short name for specifying the language.
By "short name", I mean the "language name" part after the opening fence, as shown below:
```ruby
#  ^^^^ This part
```

It's too common the case that I have to iterate through the Python code in pygments/lexers to determine which short name I should use. For example, it wasn't intuitive enough that the Python console session has a short name of pycon, when we usually don't refer to that feature with "console", but rather "REPL".
May I ask that the short names for each supported language be listed on the documentation page? As far as I am concerned, one short name for each language would be enough.

They are all listed on https://pygments.org/docs/lexers/ which is automatically generated from the source code. Maintaining that list manually on /languages would get out of date quickly.


Error on creating service integration by changing aiven_service_integration_endpoint endpoint_name

What happened?
By aiven terraform provider, we manage one datadog integration endpoint named 'datadog_endpoint' linked to our PostgreSQL Aiven service through aiven_service_integration resource. When we want to rename the datadog integration endpoint, we meet this error :
╷
│ Error: error creating service integration: 409: {"errors":[{"message":"Only 1 integration(s) of this type allowed per service","status":409}],"message":"Only 1 integration(s) of this type allowed per service"} -
│
│   with module.core_33_sbox_stack_resources.module.aiven_postgresql["toto-core-33-sbox-agvk-pg-db1"].aiven_service_integration.pg_datadog_integration[0],
│   on ../../modules/aiven/pg/service_pg.tf line 111, in resource "aiven_service_integration" "pg_datadog_integration":
│  111: resource "aiven_service_integration" "pg_datadog_integration" {

What did you expect to happen?
The expected behavior should be just to rename the aiven_service_integration resource that it have been expected by the plan below.
What else do we need to know?
The expected output plan:
  # module.core_33_sbox_stack_resources.aiven_service_integration_endpoint.datadog_endpoint["toto-core-33-sbox-agvk"] must be replaced
+/- resource "aiven_service_integration_endpoint" "datadog_endpoint" {
      ~ endpoint_config = {} -> (known after apply)
      ~ endpoint_name   = "datadog_endpoint" -> "datadog_endpoint_agvk" # forces replacement
      ~ id              = "toto-core-33-sbox-agvk/826e1855-1f15-40d7-950c-xxxxxxxxxxx" -> (known after apply)
        # (2 unchanged attributes hidden)

      ~ datadog_user_config {
          - disable_consumer_stats         = false -> null
          - kafka_consumer_check_instances = 0 -> null
          - kafka_consumer_stats_timeout   = 0 -> null
          - max_partition_contexts         = 0 -> null
            # (2 unchanged attributes hidden)
        }
    }

  # module.core_33_sbox_stack_resources.module.aiven_postgresql["toto-core-33-sbox-agvk-pg-db1"].aiven_service_integration.pg_datadog_integration[0] must be replaced
+/- resource "aiven_service_integration" "pg_datadog_integration" {
      ~ destination_endpoint_id = "toto-core-33-sbox-agvk/826e1855-1f15-40d7-950c-xxxxxxxxxxx" -> (known after apply) # forces replacement
      ~ id                      = "toto-core-33-sbox-agvk/35ebe5e5-96c8-43ba-824c-xxxxxxxxxxx" -> (known after apply)
      ~ integration_id          = "35ebe5e5-96c8-43ba-824c-xxxxxxxxxxx" -> (known after apply)
        # (3 unchanged attributes hidden)

      ~ datadog_user_config {
          - datadog_dbm_enabled        = false -> null
          - datadog_pgbouncer_enabled  = false -> null
          - exclude_consumer_groups    = [] -> null
          - exclude_topics             = [] -> null
          - include_consumer_groups    = [] -> null
          - include_topics             = [] -> null
          - kafka_custom_metrics       = [] -> null
          - max_jmx_metrics            = 0 -> null
          - mirrormaker_custom_metrics = [] -> null

          ~ datadog_tags {
                # (1 unchanged attribute hidden)
            }
          ~ datadog_tags {
                # (1 unchanged attribute hidden)
            }
          ~ datadog_tags {
                # (1 unchanged attribute hidden)
            }
          ~ datadog_tags {
                # (1 unchanged attribute hidden)
            }
          ~ datadog_tags {
                # (1 unchanged attribute hidden)
            }
        }
    }

But in real life (in Aiven console), it creates a new 'aiven_service_integration_endpoint' with the new name and don't remove the old 'aiven_service_integration_endpoint' so this old endpoint is still configured in Aiven Postgresql service integration.

Hey, I couldn't reproduce this on v4.26.0. The endpoint is replaced. Which version of Terraform and the provider did you use?

Closing this due to inactivity. Please feel free to reopen if needed.


Design fixes

This fixes the following issues:
resolve #207
resolve #208
resolve #209

I fixed a few of the design issues. @lehkost, @markschwindt please review.

Very good changes, thanks, tested them all and they are good to go from my side.


Support Eleventy’s Id Attribute plugin

Eleventy’s IdAttributePlugin automatically adds IDs to headings, so that markdown-it-anchor extension is not needed any more.
Unfortunately, this plugin is not working for me with Eleventy’s built-in plugin, but only with the markdown-it extension.

Unfortunately, this plugin is not working for me with Eleventy’s built-in plugin, but only with the markdown-it extension.

This is because Eleventy's IdAttributePlugin runs as a transform, after the HTML is generated. Therefore, at the time the toc filter is run - in the process of turning (markdown) content into HTML - the ID attributes have not yet been added to headings, so the toc plugin has nothing to work with. The markdown-it-anchor plugin works because it runs before the filter is applied, so there are heading IDs to work from.


LocalS3Path doesn’t support glob on non-existing directories

The implementations of S3Path and LocalS3Path diverge in the following way which disqualifies using LocalS3Path as a testing tool.
from cloudpathlib.s3 import S3Path

path = S3Path("s3://this/path/does/not/exist")
path.mkdir(parents=True) # does nothing (because S3 doesn't have directories)
print(list(path.glob("*"))) # returns []

from cloudpathlib.local import LocalS3Path

path = LocalS3Path("s3://this/path/does/not/exist")
path.mkdir(parents=True) # again, does nothing
print(list(path.glob("*"))) # raises exception

To fix this in my own codebase, I added a check to LocalS3Path.glob  to return an empty generator when the path is not a directory. However, I’m unsure if this fixes the issue in all cases and there might be other issues caused by directories not existing in S3 but locally.

Verified this bug.
I'd be happy with a fix that overrides glob in the LocalPath implementation to try globbing and return an empty generator on FileNotFoundError.


Add support for primitive/derived containers

Distribution: Ubuntu
Distribution version: LTS-16-04

Kernel version: 4.13.0-37-generic
LXC version: 2.21
LXD version: 2.21
Storage backend in use: DIR

Hi,
Could it be considered to add support for one main primitive container that could be derived into as many containers as wanted. Let me explain :
I use many containers that are exactly the same, save for some well-known folders (/var and /etc).
So, in this use case, I have many containers that use much disk space for... nothing else than using disk space.
The idea would be to have one container, a "main" one, that could be ran only to achieve software updates for example and that would mount all disks it requires read-write. Then, I would like to have the ability to create derived containers that would bind-mount all from this first main container read-only, and have what is specific out of the rootfs mounted as specified in it's configuration.
For example, I have ~50 containers that serves each apache2 sites (spip-ones).
The idea would be to have something like this :
One main container (spip-main) that would have it's rootfs in /lxd/spip-main/rootfs
And each of these spip-xx containers be configured this way :
/lxd/spip-xx/rootfs -> bind mount (ro) of /lxd/spip-main/rootfs
/lxd/spip-xx/etc -> bind mount (rw) of /lxd/devices/spip-xx/etc
/lxc/spip-xx/var -> bind mount (rw) of /lxd/devices/spip-xx/var
I've searched a way to achieve this, but apart from hacking what is done after a container creation, I haven't seen a native way. This could save much space (each of my spip-xx container is ~1.2 Gb) and would help have things centralized.
Hoping that this idea could be useful.

Read-only rootfs rarely works the way you'd expect with modern distros. Read-write overlays is the usual way around those issues, but they come with their own problems (mostly breaks inotify which breaks part of the init process and anything that performs inode tracking).
LXC itself (C library and tools) lets you do things like that, but we've made the conscious decision not to carry that "feature" when we designed LXD as we noticed it was doing more harm than good and would also make some of LXD's features near impossible to implement properly, thinking of things like snapshot, publishing and containers copy and move between machines.
In your scenario, you could save a lot of space by using anything but the "dir" backend as all other backends get you copy-on-write copies of your container. So when copying from your initial container, only what changes will use disk space rather than doubling the entire disk usage on copy.
To save even further, you could use ZFS with online deduplication enabled. This will trade some memory usage for significant disk savings by hashing every file that's written in any of your containers and making sure that only a single copy is ever kept on disk. With this, you can have containers temporarily diverge, taking more space and when they converge again, their files are deduplicated and you get your disk space back.


Filter Theater names by country and city

Hello, I suggest to filter the names of the theaters by country and by city, what do you think about it ?
You can assign me this issue if you agree.

Hello hello @abstractHunter
It is ok for me. I assigned you this issue. Feel free to make a pull request about it. I will be glad to review it with you ;-)


[improve][pulsar-shell] Use singleton custom command factories (#20064)

cherry picked from 3efdc9af3bede77b018146caf1cd11730701ba4f

@aymkhalil I already cherry-picked it into 2.10_ds, thanks


have the encryption icon toggle

this is just candy, would be nice if the icon reflected the current tiddler's state
closed lock => encrypted
open lock => not encrypted

Hello Tobias
That was my initial intention, but then I thought about the camouflage feature. After one tiddler is encrypted you can change it's appearance so it doesn't look like an encrypted tiddler. If I provide that visual feedback I will totally kill this feature.
Regards

@danielo515
There is several drawback with this feature right now

The tiddler content display the tiddler is encrypted
The encrypt filed shows the tiddler is encrypted
How the author of wiki can realize if a tiddler is encrypted or not?

In my opinion the padlock should change from open to close! If not it is better to use a setting tab to encrypt decrypt and do not use padlock icon.

I think that most users rely on the padlock to change, and almost nobody takes advantage of the fact that it does not. I'll change that then.

while your at it, could you make it possible to toggle the visibility of the padlock, like with the other buttons in the tiddler (from info > tools). This way, you could take the padlock out of sight, and kind of hide the encryption status, as original intended.
this would also make it more concistent with the rest of TW

while your at it, could you make it possible to toggle the visibility of the padlock, like with the other buttons in the tiddler (from info > tools). This way, you could take the padlock out of sight, and kind of hide the encryption status, as original intended.
this would also make it more concistent with the rest of TW

Yes, I will. But note that the pop-up will probably not work on that scenario.
The reason this is not possible now is because this plugin is old, and I was just a young unexperienced boy testing this proof of concept 😁


Add support for Singapore country

Add support for new country: Singapore
http://www.mom.gov.sg/newsroom/press-releases/2017/0405-singapore-public-holidays-2018

If you could contribute with your help I would surely apply to integrating your code in the project mainstream ASAP.
Your contribution is much appreciated, thank you very much.


GS-Table Crashes Page After Large INSERT

The INSERT completes, but the page crashes.
The data was 5108 lines in a single column with an average 200 character length.

Actually, this only happens if the console is open.

I've removed what I think was the problem: A console.log that logs the inserted data, in your case many thousands of characters of inserted data.
I inserted 40,000 rows with a single column containing 1000 characters, it works properly with the console open.


Incorrect minStorageBufferOffsetAlignment for Metal device

As shown in this commit, _properties.limits.minStorageBufferOffsetAlignment was changed from _metalFeatures.mtlBufferAlignment to a constant number 4.
While I was using ncnn with Vulkan SDK to do the image super-resolution neural network forwarding, Metal API complained that
validateComputeFunctionArguments:848: failed assertion `Compute Function(pooling_global_pack4_fp16s): the offset into the buffer _187 that is bound at buffer index 1 must be a multiple of 8 but was set to 8514276.'

which suggested that the buffer alignment should be 8 or _metalFeatures.mtlBufferAlignment instead of 4, a constant value.
Indeed, it can run normally if I don't use Xcode to debug the program or turn off the Metal API Validation, but I have absolutely no idea about the reason that _properties.limits.minStorageBufferOffsetAlignment was set to a constant value 4.
Environment
ProductName:	Mac OS X
ProductVersion:	10.14.6
BuildVersion:	18G103
Xcode Version: 11.3.1 (11C504)

The docs say:

For buffers in the device address space, align the offset to the data type consumed by the compute function (which is always less than or equal to 16 bytes).

This implies that the minimum alignment could be as low as 1... but that only applies if your buffer uses a byte-aligned data item. It looks like you're using something like float2 or uint2, which has an 8-byte alignment. We should probably set it to 16, since that is the maximum alignment of something you could put in a buffer.

We should probably set it to 16, since that is the maximum alignment of something you could put in a buffer.

Done now in PR #834.
@BlueCocoa  Please retest with latest code and close this issue if it fixes the error you encountered.

I've tested with the latest code and it worked as intended. Thank you very much :)


Resources For Roles Not Found

I'm trying to get a clustered redis instance running on mesos/marathon using a role called 'redis'. My configuration for this is as follows:
I'm starting the mesos master with the following flag:
--roles=redis
The mesos slaves with:
--resources=ports(*):[some_ports];ports(redis):[6379-6379,16379-16379,9696-9696]
And marathon with the flag:
--mesos_role redis
The JSON I'm submitting includes the property:
"acceptedResourceRoles": [
"redis"
]
In marathon 0.9.0, when I initially posted the request to Marathon to launch the redis app it would not launch and nothing would show up in the logs. However, if I suspended the app and then scaled up it would work just fine. We just upgraded to 0.10.0 and now it simply won't work (with the same configuration). The logs indicate the following:
role: "redis"
role: "redis"
role: "redis"
[2015-09-13 13:14:54,749] INFO Offer [20150914-202456-1694804160-5050-10639-093479]. Insufficient resources for [/redis] (need cpus=1.0, mem=1024.0, disk=0.0, ports=([6379,16379,9696] required), available in offer:
role: "redis"
The ports 6379, 16379 and 9696 are all open. I decided to try earmarking resources specifically for this role to see if that made a difference, launching the slave with the following resources:
--resources=cpu(redis):1;mem(redis):1024.0;ports(*):[some_ports];ports(redis):[6379-6379,16379-16379,9696-9696]
This produces the same 'insufficient resources' error as before. If I eliminate the concept of roles all together everything starts up fine, we're just trying to use a role for redis because their clustering automatically adds 10000 to the port for cluster communication and we were running into conditions where that port was being taken by other apps.

Hey @ryanorr, thanks for reporting this.
Can you share more of the log with us? Including the full offer that is rejected? Only resources with a role in "acceptedResourceRoles" are considered and scalar resources of different roles are not merged yet. Mesos also subtracts some resources for book keeping sometimes, therefore just configuring the exact resources that you need for that role might not be sufficient.

This ticket looks orphaned and will be closed. Please reopen, if this is a Marathon problem, that still exists.


Reporting/overview system for collection/process metadata merging issues

follow up of #4 (merging of process metadata) and  #5 (merging of collection metadata):
It turns out that there can be quite some issues when merging metadata, of varying degrees of importance/impact.
It would be good if we have some kind of system to get an overview or report issues

still needs a bit of brainstorm to make more concrete, but some things to consider:

allow this to run as kind of integration tests (e.g. critical merge issues have to be resolved before merging
allow to run continuously as cron and report (e.g. daily health check)
keep it simple as cli tool (which reporting format then?), or make it a web view (with auth?)

some more follow up issues:

[ ] https://github.com/Open-EO/openeo-aggregator/issues/80
[ ] https://github.com/Open-EO/openeo-aggregator/issues/81

most follow up TODO's are done or moved to separate tickets.
I think we can close this  #76 now.
thanks!


define submit title via schema object?

Hi,
I can't find tutorial for definition own submit value via schema object.
There is only way via the Form component's children: https://github.com/mozilla-services/react-jsonschema-form#form-action-buttons but I want to define all items, titles via one object for easy translation in future.
Is there another way?

Ok, now I see that isn't:
https://github.com/mozilla-services/react-jsonschema-form/blob/master/src/components/Form.js#L249-L256
I can send PR, can you please tell me how should I detect submit widget in schema to Form.js?

@doncesarts, I also think, this feature doesn't needed.
We can directly pass children, the way we want. Why do we need this feature?

@james-gc this feature would just be useful as a convenience, if the user doesn't want to override the entire submit button but just wants to change the text.


Add .editorconfig

Please do check to make sure these are the correct values for your code style! This will automatically configure editors which support .editorconfig (which is basically all of them) when editing files in the sb-edit directory. Once we're sure these are the right values, we should add a .editorconfig scratch-js too - it makes development quite a bit more convenient for anyone working on the project.

Once we're sure these are the right values, we should add a .editorconfig scratch-js too

That's already done!


Add start_crossover_tolerance option

Reference issue

https://github.com/scipy/scipy/pull/12043
What does this implement/fix?

add start_crossover_tolerance
add choose dual simplex edge weight options

Additional information

I know you just requested some reviewers to take a look, but looks like these changes got fast tracked upstream.  Happy to let them sit here for now while reviews happen or we can try to get them in real quick.  You might want to test out start_crossover_tolerance to make it's doing what we think it's doing, I wasn't able to test it much.

I think we should wait. I suggest we do nothing not required by reviewers until the PR gets merged. We can change whatever we like after that.


Configuring SQL statement using XSD

Using DTD is simple and not easy to extend

related with #579 and #939.

Hi @harawata ,
Sorry for late reply...
I think your patch is correct!!
Remarks:
I propose to call the System#clearProperty(String) method at finally clause for avoiding affecting other tests.

Thank you, @kazuki43zoo !
I'll update the tests and open a PR.


visualize trajectory

hello，i am learning about this pedestrian trajectory prediction recently， and i try to visualize this trajectory in the raw videoes， but i failed. I saw you have done this job in your paper. so i want to know whether you can share the code? thank you

Hi @Dong3759!
In addition to the video for trajectory visualization, it's necessary to redesign the dataloader to incorporate the homography matrix, frames, and more. The visualization source code contains several files, so I will send them to you if you request them by email!

I am glad to recive your email. And I would be very thankful if you could send the visualization code. And best wishes to you.Hope your researches go well and win all your submissions!
---Original---
From: "Inhwan @.>
Date: Tue, Dec 26, 2023 23:16 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [InhwanBae/GPGraph] visualize trajectory (Issue #6)
Hi @Dong3759!
In addition to the video for trajectory visualization, it's necessary to redesign the dataloader to incorporate the homography matrix, frames, and more. The visualization source code contains several files, so I will send them to you if you request them by email!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @Dong3759,
I'm sharing the visualization source code with you via a public repository because I haven't received any mail from you. Check it out!
If you need any other code, please contact me at my personal email address listed in the paper.
https://github.com/InhwanBae/ETH-UCY-Trajectory-Visualizer


Feat/126 rust language bindings

Fixes #126
This PR merges the repo https://github.com/fluctuo/gbfs_types big thanks to @tdelmas 🎉
Whats been done in this PR

updated readme
changed naming from v3.0-rc2 to v3.0

What's next

CICD configuration
publishing

 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.2 out of 3 committers have signed the CLA.:white_check_mark: tdelmas:white_check_mark: Alessandro100:x: renovate[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


How to get back the 1 line verbosity like v1.5

Now it takes 3 lines for 1 result which to me is quite frustrating

Hi, thanks for opening the issue. This is a bug in case you have no
scrapers enabled. With no scrapers it should default to single-line output,
but the check for it seems to be broken.
However in the case you are using scrapers, the multi-line output is the
only possible output format.
On Sun 12. Feb 2023 at 8.15, C4lputer @.***> wrote:

Now it takes 3 lines for 1 result which to me is quite frustrating
[image: image]
https://user-images.githubusercontent.com/93414512/218296059-d04d2ac2-3ca8-41e5-845a-638f1e521b8e.png
—
Reply to this email directly, view it on GitHub
https://github.com/ffuf/ffuf/issues/645, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABH6DJPYVFEP5IYVH26QIS3WXB5XDANCNFSM6AAAAAAUZD4RRY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

ffuf -w /opt/SecLists/Discovery/Web-Content/raft-medium-directories-lowercase.txt -u "http://google.com/FUZZ"
I just fuzz like I always do, but when I update to version 2 this happened. So I supposed this is a bug and there will be a fix soon?
Thank you for the quick response.

Same problem here. AFAIK it's not possible to create filters like:
(HTTP code 400) OR (HTTP code 404) OR (HTTP code 301 AND Words 456)
So I was filtering out using egrep since the results were present in one line.
Now I'm getting 3 lines per result even with no scrapers.

I'm experiencing the same issue. Seems like ffuf 2.0 now takes 3 lines for a result without using scrapers, which is frustrating indeed.

Hope it will be fixed soon, but until that go install<EMAIL_ADDRESS>Anyway, thanks for your work!

Hi there,
Fuzzing like i used to do (no -scrapers)
ffuf -u http://example.com -w wordlist.txt -H 'Host: FUZZ.example.com' -mc all -fw 1288

but the output is really weird, like 3 lines for 1 hit.
Just like @C4lputer, too much for me as well.

Just wanted to say I also am having this issue and look forward to this being fixed. Thank you.

Hi,
I've the same issue with a previous update at this date.

Hi,
I've the same issue (previously updated the tool) at this date.

If you need, the issue is fixed in the not-yet-merged https://github.com/ffuf/ffuf/pull/656
Best regards,

It's work.
Thank you sir Rémi, @p0dalirius.

Yeah. This makes ffuf unusable for me. Would love to see it back in a compact line. Back to wfuzz until then.

The PR made by p0dalirius referenced here: https://github.com/ffuf/ffuf/issues/645#issuecomment-1453979462 can be build locally by checking out their branch and following the steps for building from source.
Doing so will fix the problem described in here.

Given the nature of the issue and the PR fix that has been submitted, is this project a bit on hold/unmaintained right now ?

Hey,
Any progress on this @tomikoski @joohoi ?
Best regards,

This fix has now been merged. Thanks @p0dalirius !

Given the nature of the issue and the PR fix that has been submitted, is this project a bit on hold/unmaintained right now ?
Nope, but I've been very busy recently. Now back to it.

Thanks a lot @joohoi !
Maybe there should be a way for some serious/recurrent/trusted contributors to the project (after for instance 5/10/15 good PRs) that they could ask to be set as co-maintainers (or recommended by other users) in order to avoid this kind of situation, maybe @p0dalirius could want to have those rights since he fixed this bug pretty fast and his maintaining quite a lot of tools on GitHub already, but I can't just speak for him like this, he might be very busy and not a right fit for that.
But it would be something to consider as an improvement for contributors/contributions, I'd guess !

I'd personally rather have to compile a pull request from sources rather than see random folks be allowed to simply merge changes to the main repo without vetting by the owner. This tool is primarily used by people who hack in one way or another. If all I takes is 15 good PRs before they can sneak in their own agenda.... 😂

Yeah you're not incorrect @HeckerBirb, then the hacker would need to have a provable record of being someone "ethical" in the community, but this is was just an idea, it can be expanded, or there should be at least 2 others contributors who have 100 PRs merged in vouching for him. But I understand it's risky.


Handle Io errors in storage_read syscall

Also removes PartialEq + Eq derive traits from StateError

Codecov Report

Merging #651 (488a301) into main (1dc3f02) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #651   +/-   ##
=======================================
  Coverage   92.03%   92.03%
=======================================
  Files          49       49
  Lines       10207    10212    +5
=======================================
+ Hits         9394     9399    +5
  Misses        813      813

Impacted Files
Coverage Δ

src/business_logic/state/cached_state.rs
93.45% <100.00%> (ø)

src/business_logic/state/in_memory_state_reader.rs
91.11% <100.00%> (ø)

src/business_logic/state/mod.rs
99.29% <100.00%> (+<0.01%)
:arrow_up:

src/core/errors/state_errors.rs
100.00% <100.00%> (ø)

src/syscalls/deprecated_syscall_handler.rs
98.97% <100.00%> (+<0.01%)
:arrow_up:


Better install

Can we merge this?  Is it better?  I have noticed something a bit funny w/ the install of this package.

Not yet! Still trying to clean stuff up, but yeah, we will make it easier to install


Cmorizer for the ESACCI-OC dataset is broken

Describe the bug
While testing the cmorizers in #1657, I realized that the ESACCI-OC one is broken because the time coordinate is non-monotonous:
2021-09-28 14:24:24,718 UTC [36665] WARNING /work/bd0854/b309192/soft/miniconda3/envs/tool/lib/python3.9/site-packages/iris/fileformats/_pyke_rules/compiled_krb/fc_rules_cf_fc.py:2383: UserWarning: Failed to create 'time' dimension coordinate: The 'time' DimCoord points array must be strictly monotonic.
Gracefully creating 'time' auxiliary coordinate instead.
  warnings.warn(msg.format(name=str(cf_coord_var.cf_name),

2021-09-28 14:24:24,723 UTC [36665] INFO    Fixing latitude...
2021-09-28 14:24:24,794 UTC [36665] INFO    Fixing longitude...
Traceback (most recent call last):
  File "/work/bd0854/b309192/soft/miniconda3/envs/tool/bin/cmorize_obs", line 33, in <module>
    sys.exit(load_entry_point('ESMValTool', 'console_scripts', 'cmorize_obs')())
  File "/mnt/lustre01/pf/b/b309192/ESMValTool/esmvaltool/cmorizers/obs/cmorize_obs.py", line 365, in main
    _cmor_reformat(config_user, obs_list)
  File "/mnt/lustre01/pf/b/b309192/ESMValTool/esmvaltool/cmorizers/obs/cmorize_obs.py", line 424, in _cmor_reformat
    _run_pyt_script(in_data_dir, out_data_dir, dataset, config)
  File "/mnt/lustre01/pf/b/b309192/ESMValTool/esmvaltool/cmorizers/obs/cmorize_obs.py", line 314, in _run_pyt_script
    module.cmorization(in_dir, out_dir, cmor_cfg, user_cfg)
  File "/mnt/lustre01/pf/b/b309192/ESMValTool/esmvaltool/cmorizers/obs/cmorize_obs_esacci_oc.py", line 170, in cmorization
    extract_variable(var_info, raw_info, out_dir, glob_attrs)
  File "/mnt/lustre01/pf/b/b309192/ESMValTool/esmvaltool/cmorizers/obs/cmorize_obs_esacci_oc.py", line 70, in extract_variable
    fix_coords(cube)
  File "/mnt/lustre01/pf/b/b309192/ESMValTool/esmvaltool/cmorizers/obs/utilities.py", line 178, in fix_coords
    cube_coord.points = \
  File "/work/bd0854/b309192/soft/miniconda3/envs/tool/lib/python3.9/site-packages/iris/coords.py", line 1438, in points
    self._values = points
  File "/work/bd0854/b309192/soft/miniconda3/envs/tool/lib/python3.9/site-packages/iris/coords.py", line 2547, in _values
    self._new_points_requirements(points)
  File "/work/bd0854/b309192/soft/miniconda3/envs/tool/lib/python3.9/site-packages/iris/coords.py", line 2535, in _new_points_requirements
    raise ValueError(emsg.format(self.name(), self.__class__.__name__))
ValueError: The 'longitude' DimCoord points array must be strictly monotonic.

I guess this may not have been an issue at the time this cmorizer was releases. @tomaslovato: could you please have a look since you authored this cmorizer? Thanks!
Please attach

Command used: cmorize_obs -c config-user.yml -o ESACCI-OC
The main_log_debug.txt file, this can also be found in the run directory in the output directory:
main_log_debug.txt

@remi-kazeroni I'll have a look in next days to this (and #2322), but I would definitely prefer to do it only after we complete and close PR #1812

it's funny how iris gracefully creates time as aux coord even if points are not monotonic, but then belches out at longitude for the same reason. This is something that should probably raised with the ESACCI guys, maybe they'll thank us for it :grin: Can you post the time and lon points for us to have a look and see how bad it is maybe? :beer:

Please note that we have picked this up in #2055.

good pointer @zklaus - that PR is dusty, I can give it a one go next week if need still be :+1:

Please note that we have picked this up in #2055.

Thanks for the info. Hopefully the updated cmorizer from that PR won't suffer from this problem. Let's keep the issue open for now until #2055 is merged.

it's funny how iris gracefully creates time as aux coord even if points are not monotonic, but then belches out at longitude for the same reason. This is something that should probably be raised with the ESACCI guys, maybe they'll thank us for it 😁 Can you post the time and lon points for us to have a look and see how bad it is maybe? 🍺

Both the time and longitude contain duplicated points:
mass_concentration_of_chlorophyll_a_in_sea_water / (milligram m-3) (-- : 530; latitude: 1280; longitude: 2561)

time (first few points):
AuxCoord([1997-09-04 00:00:00, 1997-09-04 00:00:00, 1997-10-01 00:00:00,
       1997-10-01 00:00:00, 1997-11-01 00:00:00, 1997-11-01 00:00:00,
       1997-12-01 00:00:00, 1997-12-01 00:00:00, 1998-01-01 00:00:00,
       1998-01-01 00:00:00, 1998-02-01 00:00:00, 1998-02-01 00:00:00,

longitude (a few points):
-128.875      -128.875      -128.625      -128.625      -128.375
 -128.375      -128.125      -128.125      -127.875      -127.87499237
 -127.625      -127.62499237 -127.375      -127.37499237 -127.125
 -127.12499237 -126.875      -126.87499237 -126.625      -126.62499237
 -126.375      -126.37499237 -126.125      -126.12499237 -125.875

Closing this since #2055 is merged. The ESACCI-OC cmorizer has been updated (fv5.0) and the problem mentioned here is not relevant anymore.


Activating Beeftext could be easier

Expected behavior
If Beeftext is running in the background and you try to launch it again, it should show the configuration window. The new instance could quite easily request the running instance to maximize.
 An option to maximize that instance is not given.
Steps to reproduce the behavior
Run Beeftext, and minimize/hide it.
Run Beeftext again. You get the message, but not access to the program.
Operating system
Windows 10
Background
At Komputer for alle, Scandinavias largest computer magazine, we have several readers reporting their inconvenience over this behaviour.

Hi @HenrikRClausen
This has already been changed (it was requested in #128), and it is included in Beeftext v1.9 that was released earlier this week.
If you still have the problem with v1.9, please re-open the issue.

Thanks, excellent. We will upgrade to the latest version and have happy
readers.
Best regards
Henrik Ræder Clausen
Komputer for alle
A programmer is ideally an essayist who works with traditional aesthetic
and literary forms, as well as with mathematical concepts, to communicate
the way that an algorithm works.”
― Donald E. Knuth, Computer Science God
fre. 29. mar. 2019 06.39 skrev Xavier Michelon<EMAIL_ADDRESS>
Closed #147 https://github.com/xmichelo/Beeftext/issues/147.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/xmichelo/Beeftext/issues/147#event-2238276255, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ArE4VFoP153saGBqveJR9qPYQx6QykWLks5vbacLgaJpZM4cRLYw
.


Handle spaces in BrowseEverything paths.

So this throws an error on the LDP side for some reason..


Fix view blogs

Coverage remained the same at 77.651% when pulling d59dbdd006f560a428c724a996ab2b430ef51e11 on ft-blogs-153728018 into 046f1fec7fe9b3c3d38cb10fccc4d2baf0a08edc on develop.

Coverage remained the same at 77.651% when pulling d59dbdd006f560a428c724a996ab2b430ef51e11 on ft-blogs-153728018 into 046f1fec7fe9b3c3d38cb10fccc4d2baf0a08edc on develop.


plugin incompatible with goland 2023.3

awesome json viewer!
that's what i need for my json
i didn't find any other plugins can do the same thing,most of them only pretty json printer
hope if you can update the plugin

Thanks @yo-kel for the feedback.
Will try to update to latest version once free.

Hi @yo-kel I have updated the codebase to support latest IDE versions. Kindly validate if working for you with the latest update.

the plugin now works,thanks for your effort.