Cleanup 20221107

minor grab bag of fixes. Please check the commit messages for details.

thanks for the cleanup!


amplify push --y results in FeatureFlags is not initialized error

Before opening, please confirm:

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

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v15.9.0
Amplify CLI Version
4.52.0
What operating system are you using?
Mac
Amplify Categories
auth
Amplify Commands
push
Describe the bug
as per this link - https://aws.amazon.com/getting-started/hands-on/build-react-app-amplify-graphql/module-three/?e=gs2020&p=build-a-react-app-two
In the Deploy the authentication service step
I used amplify add auth in cli to add cognito as the authentication provider for my react app. Next step when pushing changes to cloud using amplify push --y , get this error

Category
Resource name
Operation
Provider plugin

Auth
friendsmoviereview108d712e
Create
awscloudformation

✖ An error occurred when pushing the resources to the cloud

FeatureFlags is not initialized
An error occurred during the push operation: FeatureFlags is not initialized
Expected behavior
Local changes ( addition of cognito as auth provider ) to be pushed up to the cloud ( hosted amplify url )
Reproduction steps
amplify add auth ( choose the default options ) , amplify push --y throws this error
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

Hi @karthikmBGO, do you have a cli.json file in your /amplify folder? If so, can you share it here?

Here is my cli.json contents

{
"features": {
"graphqltransformer": {
"addmissingownerfields": true,
"validatetypenamereservedwords": true,
"useexperimentalpipelinedtransformer": false,
"enableiterativegsiupdates": true,
"secondarykeyasgsi": true,
"skipoverridemutationinputtypes": true
},
"frontend-ios": {
"enablexcodeintegration": true
},
"auth": {
"enablecaseinsensitivity": true,
"useinclusiveterminology": true,
"breakcirculardependency": true
},
"codegen": {
"useappsyncmodelgenplugin": true,
"usedocsgeneratorplugin": true,
"usetypesgeneratorplugin": true,
"cleangeneratedmodelsdirectory": true,
"retaincasestyle": true,
"addtimestampfields": true,
"handlelistnullabilitytransparently": true
},
"appsync": {
"generategraphqlpermissions": true
}
}
}

Is there is an issue with the latest amplify cli thats triggering this issue ?

Not that we're aware of @karthikmBGO. I just went through the guide you mentioned and was able to push after adding auth on the latest version of the CLI (4.52.0).

oh man. Is there any conditions on folder /root folder etc where the amplify push --y should happen from ? Could this be an issue with npm, node or any other tool versions ? All I am trying to do is get the React App added with the sign in sign up functionality from the cognito pool

@karthikmBGO, yes there is. amplify push and any other project related commands should be run from the root folder of your project.

yes , confirmed. this is the folder I am at and running the amplify push --y

I am using npm instead of yarn

no issues on the cli.json file ?

Both npm and yarn should be fine, that shouldn't be an issue. The cli.json file you posted looks good, and is identical to the one in my sample project. The only difference that I can think of is that I'm running the LTS version of NodeJS 14.17.0.

Perhaps there's a file permission issue somewhere in your project. @karthikmBGO did you use sudo to run any of the commands in the tutorial?

@karthikmBGO can you share the file at ~/.amplify/plugins.json here?

{
"pluginDirectories": [
"cli-local-node-modules",
"cli-parent-directory",
"global-node-modules"
],
"pluginPrefixes": [
"amplify-"
],
"userAddedLocations": [],
"lastScanTime": "2021-06-10T22:32:34.910Z",
"maxScanIntervalInSeconds": 86400,
"plugins": {
"core": [
{
"packageName": "@aws-amplify/cli",
"packageVersion": "4.52.0",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/",
"manifest": {
"name": "core",
"type": "core",
"commands": [
"categories",
"configure",
"console",
"delete",
"env",
"help",
"init",
"logout",
"migrate",
"plugin",
"publish",
"push",
"pull",
"run",
"status",
"uninstall",
"upgrade",
"version"
],
"commandAliases": {
"h": "help",
"serve": "run",
"ls": "status"
}
}
}
],
"analytics": [
{
"packageName": "amplify-category-analytics",
"packageVersion": "2.21.9",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-analytics",
"manifest": {
"name": "analytics",
"type": "category",
"commands": [
"add",
"remove",
"push",
"update",
"console",
"help"
],
"commandAliases": {
"configure": "update"
},
"eventHandlers": []
}
}
],
"api": [
{
"packageName": "amplify-category-api",
"packageVersion": "2.31.10",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-api",
"manifest": {
"name": "api",
"type": "category",
"commands": [
"add-graphql-datasource",
"add",
"console",
"gql-compile",
"push",
"remove",
"update",
"help"
],
"commandAliases": {
"configure": "update"
},
"eventHandlers": []
}
}
],
"auth": [
{
"packageName": "amplify-category-auth",
"packageVersion": "2.33.0",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-auth",
"manifest": {
"name": "auth",
"type": "category",
"commands": [
"add",
"console",
"enable",
"import",
"push",
"remove",
"update",
"help"
],
"eventHandlers": []
}
}
],
"function": [
{
"packageName": "amplify-category-function",
"packageVersion": "2.31.10",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function",
"manifest": {
"name": "function",
"type": "category",
"commands": [
"add",
"build",
"console",
"invoke",
"push",
"remove",
"update",
"help"
],
"commandAliases": {
"configure": "update"
},
"eventHandlers": []
}
}
],
"hosting": [
{
"packageName": "amplify-category-hosting",
"packageVersion": "2.7.9",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-hosting",
"manifest": {
"name": "hosting",
"displayName": "Amazon CloudFront and S3",
"type": "category",
"commands": [
"add",
"configure",
"console",
"push",
"remove",
"help"
],
"commandAliases": {
"enable": "add",
"update": "configure"
},
"services": [
"S3AndCloudFront"
]
}
},
{
"packageName": "amplify-console-hosting",
"packageVersion": "1.9.0",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-console-hosting",
"manifest": {
"name": "hosting",
"type": "category",
"commands": [
"add",
"configure",
"remove",
"help",
"serve"
],
"commandAliases": {
"console": "serve",
"configure": "update"
},
"displayName": "Hosting with Amplify Console (Managed hosting with custom domains, Continuous deployment)",
"services": [
"amplifyhosting"
]
}
},
{
"packageName": "amplify-container-hosting",
"packageVersion": "1.3.10",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-container-hosting",
"manifest": {
"name": "hosting",
"displayName": "Container-based hosting with AWS Fargate",
"type": "category",
"commands": [
"add",
"configure",
"console",
"push",
"remove",
"help"
],
"commandAliases": {
"enable": "add",
"update": "configure"
},
"services": [
"ElasticContainer"
]
}
}
],
"interactions": [
{
"packageName": "amplify-category-interactions",
"packageVersion": "2.6.2",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-interactions",
"manifest": {
"name": "interactions",
"aliases": [
"interaction"
],
"type": "category",
"commands": [
"add",
"push",
"remove",
"update",
"help"
],
"commandAliases": {
"configure": "update"
},
"eventHandlers": []
}
}
],
"notifications": [
{
"packageName": "amplify-category-notifications",
"packageVersion": "2.19.2",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-notifications",
"manifest": {
"name": "notifications",
"aliases": [
"notification"
],
"type": "category",
"commands": [
"add",
"configure",
"console",
"remove",
"status",
"help"
],
"commandAliases": {
"enable": "add",
"update": "configure",
"disable": "remove",
"delete": "remove",
"list": "status",
"ls": "status"
},
"eventHandlers": []
}
}
],
"predictions": [
{
"packageName": "amplify-category-predictions",
"packageVersion": "2.9.0",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-predictions",
"manifest": {
"name": "predictions",
"aliases": [
"Predictions"
],
"type": "category",
"commands": [
"add",
"console",
"remove",
"update",
"help"
],
"commandAliases": {
"configure": "update"
},
"eventHandlers": []
}
}
],
"storage": [
{
"packageName": "amplify-category-storage",
"packageVersion": "2.11.10",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-storage",
"manifest": {
"name": "storage",
"type": "category",
"commands": [
"add",
"import",
"console",
"push",
"remove",
"update",
"help"
],
"commandAliases": {
"configure": "update"
},
"eventHandlers": []
}
}
],
"xr": [
{
"packageName": "amplify-category-xr",
"packageVersion": "2.8.9",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-xr",
"manifest": {
"name": "xr",
"aliases": [
"XR"
],
"type": "category",
"commands": [
"add",
"console",
"push",
"remove",
"update",
"help"
],
"commandAliases": {
"configure": "update"
},
"eventHandlers": []
}
}
],
"codegen": [
{
"packageName": "amplify-codegen",
"packageVersion": "2.25.1",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-codegen",
"manifest": {
"name": "codegen",
"type": "util",
"commands": [
"add",
"codegen",
"configure",
"remove",
"statements",
"types",
"models"
],
"commandAliases": {
"update": "configure",
"statement": "statements",
"model": "models"
},
"eventHandlers": []
}
}
],
"functionRuntime": [
{
"packageName": "amplify-dotnet-function-runtime-provider",
"packageVersion": "1.5.4",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-dotnet-function-runtime-provider",
"manifest": {
"name": "functionRuntime",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionRuntime": {
"pluginId": "amplify-dotnet-function-runtime-provider",
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda"
]
},
"runtimes": [
{
"name": ".NET Core 3.1",
"value": "dotnetcore3.1"
}
]
}
}
},
{
"packageName": "amplify-go-function-runtime-provider",
"packageVersion": "1.8.2",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-go-function-runtime-provider",
"manifest": {
"name": "functionRuntime",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionRuntime": {
"pluginId": "amplify-go-function-runtime-provider",
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda"
]
},
"runtimes": [
{
"name": "Go",
"value": "go"
}
]
}
}
},
{
"packageName": "amplify-java-function-runtime-provider",
"packageVersion": "1.8.2",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-java-function-runtime-provider",
"manifest": {
"name": "functionRuntime",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionRuntime": {
"pluginId": "amplify-java-function-runtime-provider",
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda"
]
},
"runtimes": [
{
"name": "Java",
"value": "java"
}
]
}
}
},
{
"packageName": "amplify-nodejs-function-runtime-provider",
"packageVersion": "1.5.5",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-nodejs-function-runtime-provider",
"manifest": {
"name": "functionRuntime",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionRuntime": {
"pluginId": "amplify-nodejs-function-runtime-provider",
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda",
"LambdaLayer"
]
},
"runtimes": [
{
"name": "NodeJS",
"value": "nodejs"
}
]
}
}
},
{
"packageName": "amplify-python-function-runtime-provider",
"packageVersion": "1.8.2",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-python-function-runtime-provider",
"manifest": {
"name": "functionRuntime",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionRuntime": {
"pluginId": "amplify-python-function-runtime-provider",
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda",
"LambdaLayer"
]
},
"runtimes": [
{
"name": "Python",
"value": "python"
}
]
}
}
}
],
"functionTemplate": [
{
"packageName": "amplify-dotnet-function-template-provider",
"packageVersion": "1.5.9",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-dotnet-function-template-provider",
"manifest": {
"name": "functionTemplate",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionTemplate": {
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda"
],
"runtime": [
"dotnetcore3.1"
]
},
"templates": [
{
"name": "Hello World",
"value": "hello-world"
},
{
"name": "Serverless",
"value": "serverless"
},
{
"name": "Trigger (DynamoDb, Kinesis)",
"value": "trigger"
},
{
"name": "CRUD function for DynamoDB (Integration with API Gateway)",
"value": "crud"
}
]
}
}
},
{
"packageName": "amplify-go-function-template-provider",
"packageVersion": "1.3.7",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-go-function-template-provider",
"manifest": {
"name": "functionTemplate",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionTemplate": {
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda"
],
"runtime": "go1.x"
},
"templates": [
{
"name": "Hello World",
"value": "hello-world"
}
]
}
}
},
{
"packageName": "amplify-java-function-template-provider",
"packageVersion": "1.5.6",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-java-function-template-provider",
"manifest": {
"name": "functionTemplate",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionTemplate": {
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda"
],
"runtime": "java"
},
"templates": [
{
"name": "Hello World",
"value": "hello-world"
}
]
}
}
},
{
"packageName": "amplify-nodejs-function-template-provider",
"packageVersion": "1.6.9",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-nodejs-function-template-provider",
"manifest": {
"name": "functionTemplate",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionTemplate": {
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda"
],
"runtime": "nodejs"
},
"templates": [
{
"name": "Hello World",
"value": "hello-world"
},
{
"name": "CRUD function for DynamoDB (Integration with API Gateway)",
"value": "crud"
},
{
"name": "Serverless ExpressJS function (Integration with API Gateway)",
"value": "serverless"
},
{
"name": "Lambda trigger",
"value": "trigger"
}
]
}
}
},
{
"packageName": "amplify-python-function-template-provider",
"packageVersion": "1.3.9",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-python-function-template-provider",
"manifest": {
"name": "functionTemplate",
"type": "util",
"commands": [],
"eventHandlers": [],
"functionTemplate": {
"conditions": {
"provider": "awscloudformation",
"services": [
"Lambda"
],
"runtime": "python"
},
"templates": [
{
"name": "Hello World",
"value": "hello-world"
}
]
}
}
}
],
"android": [
{
"packageName": "amplify-frontend-android",
"packageVersion": "2.15.3",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-frontend-android",
"manifest": {
"name": "android",
"type": "frontend",
"commands": [
"help"
],
"eventHandlers": []
}
}
],
"flutter": [
{
"packageName": "amplify-frontend-flutter",
"packageVersion": "0.4.3",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-frontend-flutter",
"manifest": {
"name": "flutter",
"type": "frontend",
"commands": [
"help"
],
"eventHandlers": []
}
}
],
"ios": [
{
"packageName": "amplify-frontend-ios",
"packageVersion": "2.20.2",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-frontend-ios",
"manifest": {
"name": "ios",
"type": "frontend",
"commands": [
"help"
],
"eventHandlers": [
"PostInit",
"PostCodegenModels",
"PostPull"
]
}
}
],
"javascript": [
{
"packageName": "amplify-frontend-javascript",
"packageVersion": "2.22.2",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-frontend-javascript",
"manifest": {
"name": "javascript",
"aliases": [
"js"
],
"type": "frontend",
"commands": [
"help"
],
"eventHandlers": []
}
}
],
"awscloudformation": [
{
"packageName": "amplify-provider-awscloudformation",
"packageVersion": "4.51.0",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation",
"manifest": {
"name": "awscloudformation",
"aliases": [
"awscfn",
"aws"
],
"type": "provider",
"commands": [
"configure",
"console",
"reset-cache",
"setupNewUser",
"help"
],
"commandAliases": {
"resetCache": "reset-cache",
"setup-new-user": "setupNewUser",
"newUser": "setupNewUser",
"new-user": "setupNewUser"
}
}
},
{
"packageName": "amplify-provider-awscloudformation",
"packageVersion": "4.29.0",
"packageLocation": "/usr/local/lib/node_modules/amplify-provider-awscloudformation",
"manifest": {
"name": "awscloudformation",
"aliases": [
"awscfn",
"aws"
],
"type": "provider",
"commands": [
"configure",
"console",
"reset-cache",
"setupNewUser",
"help"
],
"commandAliases": {
"resetCache": "reset-cache",
"setup-new-user": "setupNewUser",
"newUser": "setupNewUser",
"new-user": "setupNewUser"
}
}
}
],
"mock": [
{
"packageName": "amplify-util-mock",
"packageVersion": "3.32.0",
"packageLocation": "/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-util-mock",
"manifest": {
"name": "mock",
"type": "util",
"commands": [
"api",
"function",
"mock",
"storage",
"help"
],
"eventHandlers": []
}
}
]
},
"excluded": {}
}

@karthikmBGO, everything looks good from what I can see. Can you try uninstalling the CLI and reinstalling?
npm uninstall -g @aws-amplify/cli
npm install -g @aws-amplify/cli
amplify -v // should be 4.52.0
amplify plugin scan
Then, from your project's root directory:
amplify push -y

the npm install and unstall can be run from any folder including project root folder as well I guess ?

did the above steps , amplify -v is 4.52.0 ,
amplify push -y still gives this
Current Environment: staging

Category
Resource name
Operation
Provider plugin

Auth
friendsmoviereview108d712e
Create
awscloudformation

✖ An error occurred when pushing the resources to the cloud

FeatureFlags is not initialized
An error occurred during the push operation: FeatureFlags is not initialized

actually this is the entire output - for amplify push -y when run from the project root
✔ Successfully pulled backend environment staging from the cloud.
Current Environment: staging

Category
Resource name
Operation
Provider plugin

Auth
friendsmoviereview108d712e
Create
awscloudformation

✖ An error occurred when pushing the resources to the cloud

FeatureFlags is not initialized
An error occurred during the push operation: FeatureFlags is not initialized

the npm install and unstall can be run from any folder including project root folder as well I guess ?

Correct. As long as it's a global installation (which is necessary)

Reinstalled npm and node on my Mac. Now in module 2 -  https://aws.amazon.com/getting-started/hands-on/build-react-app-amplify-graphql/module-two/?e=gs2020&p=build-a-react-app-one
was configure is throwing an error - can you please help and point me where the issue is

Cannot find module 'body-parser'
Require stack:

/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/utils/admin-login-server.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/admin-login.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/utils/admin-helpers.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/configuration-manager.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/attach-backend.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/index.js
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>/usr/local/lib/node_modules/@aws-amplify/cli/bin/amplify
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/utils/admin-login-server.js:1
Error: Cannot find module 'body-parser'
Require stack:
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/utils/admin-login-server.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/admin-login.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/utils/admin-helpers.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/configuration-manager.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/attach-backend.js
/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/index.js
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>/usr/local/lib/node_modules/@aws-amplify/cli/bin/amplify
at Object. (/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/utils/admin-login-server.js:9:39)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object. (/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/admin-login.js:10:30)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object. (/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/utils/admin-helpers.js:11:23)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object. (/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/configuration-manager.js:38:25)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object. (/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/attach-backend.js:9:30)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object. (/usr/local/lib/node_modules/amplify-provider-awscloudformation/lib/index.js:4:29)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at /usr/local/lib/node_modules/@aws-amplify/cli/lib/configure-new-user.js:42:26
at Array.forEach ()
at Object.configureNewUser (/usr/local/lib/node_modules/@aws-amplify/cli/lib/configure-new-user.js:41:23)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Object.run (/usr/local/lib/node_modules/@aws-amplify/cli/lib/commands/configure.js:57:9)
at async Object.executeAmplifyCommand (/usr/local/lib/node_modules/@aws-amplify/cli/lib/index.js:238:9)
at async executePluginModuleCommand (/usr/local/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:164:5)
at async Object.executeCommand (/usr/local/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:35:9)
at async Object.run (/usr/local/lib/node_modules/@aws-amplify/cli/lib/index.js:114:9)

Hi @karthik2872  @karthikmBGO
Can you paste logs for the error in ampify push -y, you can found these at ~/.amplify/logs/amplify-cli-<issue-date>.log.
Also second error seems like installation issue , Can you try uninstallng cli and installing it again?

I have installed and reinstalled amplify cli globally and amplify -v shows 4.52.0
The amplify configure is working now - regarding amplify push failure
These are the logs for 6/11,12
2021-06-11T17:20:18.174Z|info : amplify pull core  {"appId":"[]tknfbw","envName":"[]ing","yes":false}
2021-06-11T17:21:55.088Z|info : amplify pull core  {"appId":"[]tknfbw","envName":"[]ing","yes":false}
2021-06-11T17:24:25.201Z|info : amplify add auth
2021-06-11T17:36:15.025Z|info : amplify push core  {"yes":true}
2021-06-11T17:37:09.142Z|info : amplify push core  {"yes":true}
2021-06-11T17:48:48.719Z|info : amplify version core  {"version":true,"yes":false}
2021-06-11T17:49:09.809Z|info : amplify version core
2021-06-11T18:12:31.585Z|info : amplify push core  {"yes":true}
2021-06-11T18:29:23.807Z|info : amplify push core  {"yes":true}
2021-06-11T21:39:38.354Z|info : amplify push core  {"yes":true}
2021-06-11T21:43:35.562Z|info : amplify version core  {"version":true,"yes":false}
2021-06-11T22:02:48.318Z|info : amplify add auth
2021-06-11T22:02:57.754Z|info : amplify update auth
2021-06-11T22:04:47.111Z|info : amplify push core  {"yes":true}
2021-06-11T22:06:22.455Z|info : amplify publish core  {"yes":true}
2021-06-11T22:06:40.838Z|info : amplify help core
2021-06-11T22:07:06.903Z|info : amplify add hosting
2021-06-11T22:08:21.553Z|info : amplify publish core  {"yes":true}
2021-06-11T22:42:17.254Z|info : amplify version core  {"version":true,"yes":false}
2021-06-11T22:42:36.486Z|info : amplify push core  {"yes":true}
2021-06-12T00:29:33.986Z|info : amplify push core
2021-06-12T00:30:16.525Z|info : amplify push core  {"yes":true}
2021-06-12T01:42:16.833Z|info : amplify console core
2021-06-12T01:42:37.220Z|info : amplify configure core
2021-06-12T02:05:50.658Z|info : amplify help core  {"g":"aws-amplify","yes":false}
2021-06-12T02:20:03.123Z|info : amplify version core  {"version":true,"yes":false}
2021-06-12T02:28:51.386Z|info : amplify configure core project
2021-06-12T02:33:59.319Z|info : amplify version core  {"version":true,"yes":false}
2021-06-12T03:19:15.284Z|info : amplify version core  {"version":true,"yes":false}
2021-06-12T04:33:14.074Z|info : amplify version core  {"version":true,"yes":false}
2021-06-12T14:17:26.601Z|info : amplify version core  {"version":true,"yes":false}
2021-06-14T21:10:52.924Z|info : amplify version core  {"version":true,"yes":false}

Is it still stuck with FeatureFlags not initialized  error after reinstalling amplify?

I am in this step amplify pull --appId d3mo2wp0r6e9my --envName staging
(https://aws.amazon.com/getting-started/hands-on/build-react-app-amplify-graphql/module-two/?e=gs2020&p=build-a-react-app-one)
This is taking me to a browser  https://us-east-1.admin.amplifyapp.com/admin/d3mo2wp0r6e9my/staging/verify/
asking me to sign into amplify backend - WHY SHOULD I SIGN into amplify backend when I am signed into the console already ?
Amplify is lot confusing and nowhere as simple as the instructions are - lots of dependencies and headaches.

the user you need to sign in as is the amplify admin ui user you're taking the role of when you pull. So this extra login step is required for AdminUI apps.
This the original FeatureFlag issue still happening after reinstalling amplify?

Hey @karthik2872 :wave: are you still experiencing this issue after reinstalling Amplify or with the latest version of the CLI?

I have not had a chance to try this again. I have worked around the need to use amplify the backend by setting up serverless end points over express for my backend apis that need authentication to be passed from client side calls. Using amplify only for the ReactJS front end for my project

Hey @karthik2872 no worries! For the web page (Admin UI) asking to sign in, when Admin UI is enabled for that backend we will need to launch Admin UI from the Console for the first time before authenticating with the CLI if AdminUI is chosen as the preferred authentication method. This is an issue the team is actively tracking!
I'll close this issue for now, but if you experience this issue again with the latest version of the CLI please reply back to this thread and we can re-open to investigate further, or file a new bug report


ImportError: No module named 'zipline.utils.calendars._calendar_helpers'

Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: (Windows Version or $ uname --all)
Python Version: $ python --version
Python Bitness: $ python -c 'import math, sys;print(int(math.log(sys.maxsize + 1, 2) + 1))'
How did you install Zipline: (pip, conda, or other (please explain))
Python packages: $ pip freeze or $ conda list

Now that you know a little about me, let me tell you about the issue I am
having:
Description of Issue

What did you expect to happen?
What happened instead?

Here is how you can reproduce this issue on your machine:
Reproduction Steps

...
What steps have you taken to resolve this already?
...
Anything else?
...
Sincerely,
$ whoami

I hit the same issue.  Looks like you need to build pyx.

I was able to load zipline after this.
import pyximport
import numpy as np
pyximport.install(setup_args={'include_dirs': np.get_include()})

This builds .so files in the same source directory
$ python setup.py build_ext --inplace

Hi @yadongcao sorry for the late response here. Going to close this b/c of no follow-up but if you still have issues, please open a new issue with the template completely filled out.
Thanks,
Freddie


[BUG] Serialization of CloudEvent through Jackson does not include the serialized data object

Describe the bug
Due to the current implementation of CloudEvent, the data attribute of the CloudEvent is represented as org.example.functions.SerializableContent instead of the desired class.
To Reproduce
Steps to reproduce the behavior:

Serialize a CloudEvent with Jackson

Code Snippet
package org.example.functions;

import com.azure.core.models.CloudEvent;
import com.azure.core.models.CloudEventDataFormat;
import com.azure.core.util.BinaryData;
import com.fasterxml.jackson.databind.ObjectMapper;

public class Jackson {

    private static class Foo {
        private final String bar;

        public Foo(String bar) {
            this.bar = bar;
        }

        public String getBar() {
            return bar;
        }
    }

    public static void main(String[] args) throws Exception {
        ObjectMapper objectMapper = new ObjectMapper();
        BinaryData binaryData = BinaryData.fromObject(new Foo("bar"));
        CloudEvent cloudEvent = new CloudEvent("mySource", "myType", binaryData, CloudEventDataFormat.JSON, "application/json");
        System.out.println(objectMapper.writeValueAsString(cloudEvent));
    }
}

Expected behavior
The data object contains a correct representation:
{"id":"c4c53894-46ab-40ff-abe7-9fe2bc8c215e","source":"mySource","data":{"bar":"bar"},"data_base64":null,"type":"myType","time":null,"specversion":"1.0","dataschema":null,"datacontenttype":"application/json","subject":null}

instead of
{"id":"c4c53894-46ab-40ff-abe7-9fe2bc8c215e","source":"mySource","data":{"replayable":true,"length":13},"data_base64":null,"type":"myType","time":null,"specversion":"1.0","dataschema":null,"datacontenttype":"application/json","subject":null}

Setup (please complete the following information):

OS: MacOs
IDE: IntelliJ
Library/Libraries: com.azure:azure-core:1.41.0
Java version: 8
App Server/Environment: N.A.
Frameworks: N.A

Additional context

Related issue in function worker: https://github.com/Azure/azure-functions-java-worker/issues/720
There is a @JsonIgnore annotation on com.azure.core.models.CloudEvent#binaryData
There is a @JsonProperty annotation on com.azure.core.models.CloudEvent#data
The getData implementation returns BinaryData instead of JsonNode
Jackson serializes the data attribute through the getter method (getData) resulting in a mismatch and a loss of content.

  @JsonProperty("data")
    private JsonNode data;
    @JsonProperty("data_base64")
    private String dataBase64;
    @JsonIgnore
    private BinaryData binaryData;

    public BinaryData getData() {
        if (this.binaryData == null) {
            if (this.data != null) {
                this.binaryData = BinaryData.fromObject(this.data, SERIALIZER);
            } else if (this.dataBase64 != null) {
                this.binaryData = BinaryData.fromBytes(Base64.getDecoder().decode(this.dataBase64));
            }
        }

        return this.binaryData;
    }

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[X] Repro Steps Added
[X] Setup information Added

@joshfree if possible, I'd like to make a PR myself. Let me know!

Hi @tomsnor, we gladly accept any contributions to the repository, so please feel free to submit a PR if you wish.
I'll add some context on what is likely happening here.
BinaryData is mostly just a wrapper around different implementations of BinaryDataContent that handle different data formats. These contents are bucketed into a few broad categories of BINARY, OBJECT, and TEXT which are then used by an internal Jackson Modules that determine how to handle serialization and deserialization of BinaryData. It looks like this is where the issue is coming from in your example as you're using an ObjectMapper external to the Azure SDKs, which we should work on having this scenario being handled correctly.
My thoughts on the design for this, BinaryData is just an object wrapper around the true handling managed by BinaryDataContent, so the BinaryDataContent property in BinaryData should be annotated with JsonValue. Then, BinaryDataContent should be annotated with JsonSerializer and JsonDeserializaer to handle serialization and deserialization without having to rely on JacksonAdapter. You can look to JsonPatchDocument and JsonPatchOperation for some guidance as this is roughly equivalent in functionality.

Hi @tomsnor, I had the same issue, you can see the development here -> #35579

Hi @tomsnor and @alzimmermsft
I see that the proposed PR has been closed without being merged and I am facing the same issue. I am trying to write a CloudEvent as JSON but the data property is not correctly serialized.

message_body is a column of type json in my postgresql database. I expect it to have the the serialized CloudEvent but CloudEvent.data is not correctly serialized.

mentioning @joshfree as well

HI @mrksph, could you include which version of azure-core is being used?


Addressed issues from QA scan report

Didn't see this addressed:
sparqlQuery.jsp, line 32 (Open Redirect)
Fortify Priority: Critical Folder Critical
Kingdom: Input Validation and Representation
Abstract: The file sparqlQuery.jsp passes unvalidated data to an HTTP redirect function on line
32. Allowing unvalidated input to control the URL used in a redirect can aid phishing
attacks.
Source: sparqlQuery.jsp:23 javax.servlet.ServletRequest.getParameter()
21 <%@ page import="java.net.*" %>
22 <%
23 String sparql=request.getParameter("sparql");
24 String infer=request.getParameter("infer");
25 String auth=request.getParameter("auth");
Sink: sparqlQuery.jsp:32 javax.servlet.http.HttpServletResponse.sendRedirect()
30 String sparqlEnc = URLEncoder.encode(sparql,"UTF-8");
31 String urlTo =
"queryrdf?query.infer="+infer+"&query.auth="+auth+"&query.resultformat="+resultFormat+
"&padding="+padding+"&query="+sparqlEnc;
32 response.sendRedirect(urlTo);
33 }
34 %>
sparqlQuery.jsp, line 32 (Open Redirect)
Fortify Priority: Critical Folder Critical
Kingdom: Input Validation and Representation
Abstract: The file sparqlQuery.jsp passes unvalidated data to an HTTP redirect function on line
32. Allowing unvalidated input to control the URL used in a redirect can aid phishing
attacks.
Source: sparqlQuery.jsp:25 javax.servlet.ServletRequest.getParameter()
23 String sparql=request.getParameter("sparql");
24 String infer=request.getParameter("infer");
25 String auth=request.getParameter("auth");
26 String resultFormat = request.getParameter("emit");
27 String padding = request.getParameter("padding");
Sink: sparqlQuery.jsp:32 javax.servlet.http.HttpServletResponse.sendRedirect()
30 String sparqlEnc = URLEncoder.encode(sparql,"UTF-8");
31 String urlTo =
"queryrdf?query.infer="+infer+"&query.auth="+auth+"&query.resultformat="+resultFormat+
"&padding="+padding+"&query="+sparqlEnc;
RyaAccumuloSailConfig.java, line 55 (Password Management: Hardcoded Password)
Fortify Priority: Critical Folder Critical
Kingdom: Security Features
Abstract: Hardcoded passwords can compromise system security in a way that cannot be easily
remedied.
Sink: RyaAccumuloSailConfig.java:55 FieldAccess: password()
53
54 private String user = "root";
55 private String password =******
56 private String instance = "dev";
57 private String zookeepers = "zoo1,zoo2,zoo3";
I'm also not sure about what was implemented for these:
NamespaceManager.java, line 59 (Unreleased Resource: Streams)
Fortify Priority: High Folder High
Kingdom: Code Quality
Abstract: The function initialize() in NamespaceManager.java sometimes fails to release a
system resource allocated by getResourceAsStream() on line 59.
Sink: NamespaceManager.java:59 cacheConfigStream =
getResourceAsStream(...)
57 this.namespaceManager = ryaDAO.getNamespaceManager();
58
59 InputStream cacheConfigStream =
Thread.currentThread().getContextClassLoader().getResourceAsStream("ehcache.xml");
60 if (cacheConfigStream == null) {
61 this.cacheManager = CacheManager.create()
RyaConsoleCommands.java, line 162 (Unreleased Resource: Streams)
Fortify Priority: High Folder High
Kingdom: Code Quality
Abstract: The function load() in RyaConsoleCommands.java sometimes fails to release a
system resource allocated by FileInputStream() on line 162.
Sink: RyaConsoleCommands.java:162 new FileInputStream(...)
160 //diff types of urls
161 try {
162 ntrips_parser.parse(new FileInputStream(file), "");
163 } catch (Exception e) {
164 LOG.log(Level.SEVERE, "", e);
And the same one on the SparqlQueryPigEngine -- I think you need to close the stream in a finally block.
Didn't see this addressed:
SparqlQueryPigEngine.java, line 153 (Log Forging)
Fortify Priority: High Folder High
Kingdom: Input Validation and Representation
Abstract: The method runQuery() in SparqlQueryPigEngine.java writes unvalidated user input
to the log on line 153. An attacker could take advantage of this behavior to forge log
entries or inject malicious content into the log.
Source: SparqlQueryPigEngine.java:192 main(0)
190
191
192 public static void main(String[] args) {
193 try {
194 Preconditions.checkArgument(args.length == 7, "Usage: java -cp
:$PIG_LIB  sparqlFile hdfsSaveLocation cbinstance cbzk cbuser cbpassword
rdfTablePrefix.\n " +
Sink: SparqlQueryPigEngine.java:153 org.apache.commons.logging.Log.info()
151 Preconditions.checkNotNull(sparql, "Sparql query cannot be null");
152 Preconditions.checkNotNull(hdfsSaveLocation, "Hdfs save location cannot be
null");
153 logger.info("Running query[" + sparql + "]\n to Location[" + hdfsSaveLocation

"]");
154 pigServer.deleteFile(hdfsSaveLocation);
155 try {
ConfigUtils.java, line 153 (Log Forging)
Fortify Priority: High Folder High
Kingdom: Input Validation and Representation
Abstract: The method createTableIfNotExists() in ConfigUtils.java writes unvalidated user
input to the log on line 153. An attacker could take advantage of this behavior to
forge log entries or inject malicious content into the log.
Source: SparqlQueryPigEngine.java:192 main(0)
190
191
192 public static void main(String[] args) {
193 try {
194 Preconditions.checkArgument(args.length == 7, "Usage: java -cp
:$PIG_LIB  sparqlFile hdfsSaveLocation cbinstance cbzk cbuser cbpassword
rdfTablePrefix.\n " +
Sink: ConfigUtils.java:153 org.apache.log4j.Category.info()
151 TableOperations tops = getConnector(conf).tableOperations();
152 if (!tops.exists(tablename)) {
153 logger.info("Creating table: " + tablename);
154 tops.create(tablename);
155 return true;

You can just delete those log calls if thats easier.
Didn't see this addressed:
SparqlQueryPigEngine.java, line 197 (Path Manipulation)
Fortify Priority: High Folder High
Kingdom: Input Validation and Representation
Abstract: Attackers can control the filesystem path argument to FileInputStream() at
SparqlQueryPigEngine.java line 197, which allows them to access or modify
otherwise protected files.
Source: SparqlQueryPigEngine.java:192 main(0)
190
191
192 public static void main(String[] args) {
193 try {
194 Preconditions.checkArgument(args.length == 7, "Usage: java -cp
:$PIG_LIB  sparqlFile hdfsSaveLocation cbinstance cbzk cbuser cbpassword
rdfTablePrefix.\n " +
Sink: SparqlQueryPigEngine.java:197 java.io.FileInputStream.FileInputStream()
195 "Sample command: java -cp java -cp cloudbase.pig-2.0.0-SNAPSHOTshaded.
jar:/usr/local/hadoop-etc/hadoop-0.20.2/hadoop-0.20.2-core.jar:/srv_old/hdfstmp/
pig/pig-0.9.2/pig-0.9.2.jar:$HADOOP_HOME/conf
mvm.rya.accumulo.pig.SparqlQueryPigEngine " +
196 "tstSpqrl.query temp/engineTest stratus stratus13:2181 root
password l_");
197 String sparql = new String(ByteStreams.toByteArray(new
FileInputStream(args[0])));
198 String hdfsSaveLocation = args[1];
199 SparqlToPigTransformVisitor visitor = new SparqlToPigTransformVisitor();
IndexWritingTool.java, line 93 (Path Manipulation)
Fortify Priority: Critical Folder Critical
Kingdom: Input Validation and Representation
Abstract: Attackers can control the filesystem path argument to File() at IndexWritingTool.java
line 93, which allows them to access or modify otherwise protected files.
Source: IndexWritingTool.java:81 run(0)
79
80 @Override
81 public int run(final String[] args) throws Exception {
82 Preconditions.checkArgument(args.length == 7, "java " +
IndexWritingTool.class.getCanonicalName()
83 + " hdfsSaveLocation sparqlFile cbinstance cbzk cbuser cbpassword
rdfTablePrefix.");
Sink: IndexWritingTool.java:93 java.io.File.File()
91 final String tablePrefix = args[6];
Didn't see this addressed:
AccumuloStorage.java, line 91 (Password Management: Empty Password)
Fortify Priority: High Folder High
Kingdom: Security Features
Abstract: Empty passwords can compromise system security in a way that cannot be easily
remedied.
Sink: AccumuloStorage.java:91 FieldAccess: password()
89 protected String zookeepers;
90 protected String user = "";
91 protected String password =******
92 protected String table;
93 protected Text tableName;
Fortify Security Report
Copyright
Didn't see this addressed:
RdfController.java, line 269 (System Information Leak: External)
Fortify Priority: High Folder High
Kingdom: Encapsulation
Abstract: The function performUpdate() in RdfController.java might reveal system data or
debugging information by calling print() on line 269. The information revealed by
print() could help an adversary form a plan of attack.
Source: RdfController.java:269 java.lang.Throwable.getLocalizedMessage()
267 } catch (UpdateExecutionException e) {
268 os.print(String.format("Update could not be successfully completed for
query: %s\n\n", query));
269 os.print(String.format("\n\n%s", e.getLocalizedMessage()));
270 }
Sink: RdfController.java:269 javax.servlet.ServletOutputStream.print()
267 } catch (UpdateExecutionException e) {
268 os.print(String.format("Update could not be successfully completed for
query: %s\n\n", query));
269 os.print(String.format("\n\n%s", e.getLocalizedMessage()));
270 }
You can delete the logging in this case.

WRT sparqlQuery.jsp, line 32 - it's either we need to validate incoming data on the client side (which required format or something to indicate the data is valid or not) or on the server side.

If you want to validate the data on the client side, I need to know the logic to do so
Otherwise do nothing here and let the server side validates the data

WRT RyaAccumuloSailConfig.java, line 55 (Password Management: Hardcoded Password) it's either it needs to be passed in or encrypted it, don't know what the tool wants to do here

WRT AccumuloStorage.java, line 91 (Password Management: Empty Password), here is my note in the attached file that I sent in the email
Category: Password Management: Empty Password (1 Issues)

[pig/accumulo.pig] AccumuloStorage.java
protected String password = "";
-> for now, let's considered this as false positive but an empty string password could be a default password

Otherwise, again, we either need to pass in the value or encrypted the value. I can put an encrypted value here but not sure if fortify will complain about it or not.

Fixed -> RdfController.java, line 269 (System Information Leak: External)

WRT NamespaceManager.java, line 59 (Unreleased Resource: Streams), use try-with-resource to close the open stream when exception is thrown

Fixed -> SparqlQueryPigEngine.java, line 153 (Log Forging)
Fixed -> SparqlQueryPigEngine.java, line 197 (Path Manipulation)
Fixed -> IndexWritingTool.java, line 93 (Path Manipulation)
Fixed -> AccumuloStorage.java, line 91 (Password Management: Empty Password)


Callback?

Hi there. How do my device "tells" homebridge some status changing? For instance, lights have been turned off directly. Could you be provide some example? Thanks.

If you turn a lamp off manually, I don't see how homebridge would ever get the message, unless you had somesort of 'smartsocket' that could self monitor electrical usage.  Then that would have to 'report back' via a Homebridge plugin https://www.npmjs.com/search?q=homebridge-plugin


color box plots from .color( ) method

https://groups.google.com/forum/#!topic/d3plus/CeQcRpzISTE

I would like this, but I'd like to choose the color per box based on a field in the data. I'm willing to work on this, but I want to make sure that it's something that would be accepted and some direction on how I should go about doing it.
I'm thinking something like:
.data([{ "some_field": "some_value"}])
.color({ "field": "some_field", "values": { "some_value": "blue" } })

I'd be interested in getting something done in the next couple weeks, so I'd appreciate timely feedback if possible. Is this the best place for that discussion, or should it happen on the mailing list?


Lankfiles.com

Any possible fix/trick for this
@uBlock-user
https://github.com/uBlockOrigin/uAssets/issues/7593

No, because site never serves the download link, I get sent to ad-servers and some crapping domains on an endless redirect until Peter's list starts strict blocking such domains.


💡[FEATURE]: Stress Testing Financial Portfolios with RL

Is your feature request related to a problem? Please describe.
Use RL to stress test financial portfolios by simulating extreme market conditions and adjusting portfolio allocations accordingly.
Describe the solution you'd like
Steps:
Define Environment: Model stress scenarios with extreme market conditions.
State Representation: Include current portfolio allocations and market indicators.
Reward Function: Reward for maintaining portfolio stability and minimizing losses during stress conditions.
Training the Agent: Use RL to optimize portfolio allocations under stress scenarios.

pls assign it me @Akshat111111


[🐞] Playground: useStylesScoped does not HMR

Which component is affected?
Starters / CLI
Describe the bug

open this playground link

try to edit the color to green or something else. Styles will will not reload in the REPL

Reproduction
Playground Link
Steps to reproduce
No response
System Info
n/a

Additional Information
No response

I suffer from this as I try to build components with storybooks, but I need to restart it whenever I change something in my scoped styles. In general, I do inline my styles, and curiously the template does update fine, just the styles getting ignored.


[Android] Continuous usage causes local references leak and app crash

Hi! Thanks for the great library.
We use your library in our project and faced with an issue. We start new thread in native code and perform operations including generating of multiple uuids. After some time the application crashes with native stacktrace like following:
art/runtime/indirect_reference_table.cc:115] JNI ERROR (app bug): local reference table overflow (max=512)
art/runtime/indirect_reference_table.cc:115] local reference table dump:
art/runtime/indirect_reference_table.cc:115]   Last 10 entries (of 512):
...
art/runtime/indirect_reference_table.cc:115]       508: 0x12d94490 java.util.UUID
...
art/runtime/indirect_reference_table.cc:115]       505: 0x12c05f30 java.util.UUID
...
art/runtime/indirect_reference_table.cc:115]       502: 0x12c05ec8 java.util.UUID
art/runtime/indirect_reference_table.cc:115]   Summary:
...
art/runtime/indirect_reference_table.cc:115]       181 of java.util.UUID (181 unique instances)

It seems that jobject javaUuid local reference in Guid newGuid(), returned from randomUUID() java method should be deleted after bits evaluation.
Also, as far as newGuid() is callable from different threads after initJni() AndroidGuidInfo.uuidClass must be a global reference to prevent illegal usage and crash.
Is it suitable to open PR with implementation of this behaviour?

Sorry, the issue is intended for previous version of code. I reviewed the new version of code and found that javaUuid is deleted now.
However, AndroidGuidInfo.uuidClass is local reference yet.

thanks


EnderIO thinks the RF API is lower than 1.4.0 while it's actually 1.7.0

What happens:
I have made my own modpack based on FTB Beyond. 60% of the mods are the same. When I try to launch the game it crashes on launch 90% of the time.
The error log crashes because Ender IO apparently doesn't work with the current RF API from CoFHCore. The error log outputs the following:
An unsupportted RF API is installed (1.7.0 .. )
Ender IO needs at least 1.4.0 and will NOT work with older versions.
This error message obviously makes no sense. The RF API is 1.7.0, but Ender IO thinks it's lower than 1.4.0?
Weird thing is, that 10% of the time, the launch of the game is succesful.
The game has never crashed while playing. Only at launch.
What you expected to happen:
A succesful game launch.
Steps to reproduce:

Install this modpack in the Twitch client with forge <IP_ADDRESS>1: https://drive.google.com/open?id=0B7jk0SKCFY9yN3d6djNpbjhZRmc
Launch the game
Crash on launch
...

Affected Versions (Do not use "latest"):

EnderIO: 1.10.2-3.1.183
EnderCore: 1.10.2-<IP_ADDRESS>
Minecraft: 1.10.2
Forge: <IP_ADDRESS>1

Your most recent log file where the issue was present:
https://pastebin.com/8uaNTkLd

EnderIo only checks for 2 specific versions of the RF API:
https://github.com/SleepyTrousers/EnderIO/blob/master/src/main/java/crazypants/enderio/tool/EnderIOCrashCallable.java
everything else is marked as "unsupported" - it doesn't even try to compare the version strings.
As your versions also says "1.7.0" but without the "R1.0.0" or "R1.0.1" suffix it's hard to say if your version is newer or older as the 2 versions known to EnderIO.
But in any case the crash in your log is not related to EnderIO. Try starting the game without the resource packs.

Thanks for a quick an useful response. Unfortunately the same thing happens without the resource packs.
Since all mods are up to date, that means many of them are in beta, and I guess there are a lot of bugs or inconsistencies.
I have duplicated the beyond pack, added a few mods of my own and now use the same forge version. It works perfectly now, so I guess that is my solution for now.

That link goes to the 1.7-version, here's the one for the 1.10-version: https://github.com/SleepyTrousers/EnderIO/blob/1.10/src/main/java/crazypants/enderio/diagnostics/EnderIOCrashCallable.java#L46-L80
You get that message because we had problems with people using an RF-API for Minecraft 1.7.x on Minecraft 1.10. Now that the RF-API has progressed to version 1.7, it is a false alarm.
To find which mod crashes the game, use a binary search. That is:

Remove half of the mods
If it still crashes, the bad mod must be in the half that stayed, if not, it must be in the half that was removed
Put the removed mods back
Remove half of those mods you identified in step 2 as "must contain the bad one"
Go to step 2


fix: add back missing favicon

Also removed the default unused astro favicon

Hmm doesn't work in the preview ...
Says the image is not present. This was working perfectly locally.

I might need some help here. Is it just a preview oddity or have I misused lfs maybe?

@orhun how did you test it? It doesn't work for me in the preview link.
@Valentin271 if you move it to the public folder and using/favicon.png it should work.

I checked out main and checked if favicon exists after running npm run dev.
Then I did the same for this branch and the favicon appeared.

npm run dev will show the favicon because it looks in the source directory.
What you want to try is npm run build && npm run preview. I'm assuming that will not work and you'll get the same error as the preview.

Interesting the build failed, it passed locally.
I don't have the rights to check the exact error on cloudflare.

npm run dev will show the favicon because it looks in the source directory.
What you want to try is npm run build && npm run preview. I'm assuming that will not work and you'll get the same error as the preview.

You're absolutely right, preview doesn't work with the image in assets and it does with the image in public.

Well weirdly enough it worked for me after doing npm run build && npm run preview :o

@orhun try git clean -fxd dist first?

Seems like the build error was a one-off, preview is working with the favicon now

I see two things to improve (happy to merge and fix later):

It would be nice to get an icon that is better pixelated (crisp diagonal lines)
If possible can we make the background transparent rather than black?

It would be nice to get an icon that is better pixelated (crisp diagonal lines)

Would have to test which one looks better, it renders well on my screen and on your capture

If possible can we make the background transparent rather than black?

Tried this logo before submitting but thought it was too discrete

Ah yeah, I didn't think about light tabs. I suspect the best approach for the pixelating would be manual tweaks rather than relying on automatic scaling to get it right.

I didn't think about light tabs

And we can't (at least easily, requires some css hack) use different favicons according to the theme.
Also worth mentioning the favicon will be shown in those kind of places (we can specify a different one here though):

I've manually scaled to favicon to 32x32, I don't see any difference on my machine. Does it look any better to anyone?
At least now it's easier to scale up to 64x64, 196x196 ...

LGTM

TIL: https://stackoverflow.com/questions/48956465/favicon-standard-2023-svg-ico-png-and-dimensions
TL;DR: 16x16, 32x32, 48x48, 167x167!!!, 192x192, and 228x228 are all common favicon sizes.

Oh right, I see the difference now.
I saw that thread, I'm pretty sure those are preferred sizes. If there are available, the browser will use the preferred one, otherwise it will try other sizes. (except maybe for apple touch icon which will only use one size)
Anyway we may add those later on a case by case basis.


Use makefile for terraform

Context

This PR implements https://trello.com/c/oio959xP/442-apply-use-makefile-to-run-terraform-in-deploy-workflow
Changes proposed in this pull request

(roughly) Align deploy steps with public
Ensure deploy.yml uses Makefile for infra deploys

Guidance to review

Link to Trello card

Things to check

[x] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] Required environment variables have been updated added to the Azure KeyVault

 Apply: Use Makefile to run terraform in deploy workflow


bug: ion-refresher not working when jsScrolling disable

Type: bug
Platform: android 4.4 webview
I have referred some forum topics and i found a great way to disable the jsScrolling to have the native scrolling to work. Forum topic i followed. I have disabled the jsScrolling to get the native kind of scrolling on the android device. When i do so, the scroll performance is good. But it is leading to another issue. ion-refresher is not working at all. If i enable the default scrolling(jsScrolling) in the app, ion-refresher is working fine, but the scrolling performance is not good.
And even the side menu bar is not moving right side when we swipe right. When we click on the toggle button, the menu bar is moving right side.
Can some one please let me know the solution for this issue.

This is a tricky problem. Android 4.4 and lower fire off a touchcancel event when scrolling, preventing the touchmove events we listen for. It should work fine on Android 5 or devices with crosswalk enabled. Can you confirm this?

I have tried with crosswalk too. But still no use. I haven't tested in android v5, as i don't have mobile with Android v5.

fixed in 71e89715eec85a03ceb04d53f8406dab75ac71dc
Thanks


Why this doesn't have MQTT feature.

Why this doesn't have MQTT feature. If MQTT option there its wonderful piece of firmware in the world.
Please add that MQTT IR receive & send feature support

MQTT via Amazon's IoT on the ESP8266 is crippled by the lack of memory on the ESP8266. Not enough to handle TLS 1.2 which is the minimum requirement Amazon enforces for authentication. There's are a couple Websocket workarounds than can sort of get it working but hasn't been reliable in my testing.
Switching to MQTT would also require a complete rewrite of the server backend and accompanying Amazon skill which I simply do not have time to undertake right now.


Can't bind to 'mat-dialog-close' since it isn't a known property of 'button'.

Bug, feature request, or proposal:
Hi, I'm trying to work with a tutorial about modal in angular 5 -> https://material.angular.io/components/dialog/overview
and it's not working it giving me the error
Can't bind to 'mat-dialog-close' since it isn't a known property of 'button'.
here is my HTML code:
Warning

Are you sure you want to delete the book {{data.title}} ?

Ok
No Thanks

thanks.

Did you import the MatDialogModule ?

WOW!!! that was the problem thank you very very much!! :)

I think you can close the issue as it is not Angular Material's fault ;).

If you're opening a dialog with dialog.open in one module and your control is defined in another you must add the Dialog module import to both modules.
This is very easy to forget, and the dialog will open - it's just that then all dialog directives (including mat-dialog-actions / mat-dialog-title and mat-dialog-content will not work).


Get federation config from URL if available

@futurepaul can you test this out now? Should try to parse it correctly.

I'll try this out now

still seeing nulls sry:

Feel free to get in here and do it yourself, since you know how to test it and you know how to get it properly.

I'll give it a shot

This seems to work. No idea if I did the right thing in the merge_values section, I was just doing whatever the red squigglies told me to do

Nice. Only thing that's not coming through is the sites parameter. I think it just needs to be turned to a Vec and it would work? Otherwise just remove it, we don't need it.


PHP: update memory leak tests

remove a couple of unnecessary unit test style asserts
update port numbers to be consistent with other similar PHP tests

Test failure: #20355


Llama 3 speed

I tested the speed of lama models using exlama and noticed that the speed of 8b models is much slower than 7b (although this is not the case with other inferences. Can you tell me what the problem might be?
| tokens/s | tokens first second | symbols/sec
-- | -- | -- | --
suzume-llama-3-8B-multilingual-gptq_on1000_ja | 63.96 ± 7.37 | 56.48 ± 16.76 | 96.78 ± 14.76
Swallow-7b-instruct-v0.1-gptq_on1000_ja | 194.56 ± 22.83 | 166.34 ± 40.23 | 165.04 ± 37.06
shisa-v1-llama3-8b-gptq_on1000_ja | 60.01 ± 9.03 | 58.92 ± 14.76 | 90.45 ± 15.50

GPTQ doesn't quantize the output layer, so with the much larger vocabulary of Llama3, the output tensor alone is about 750 MB larger. This adds a significant amount of latency.
Llama3 also uses GQA, which means you have a similar amount of computation for attention with somewhat lower VRAM overhead, but then the weights that would be assigned to keys/values are instead added to the MLP inner layer, making that slower instead.
I don't know that this accounts for the entire difference you're seeing, but certainly some of it. You could try with EXL2 models which do have quantized output layers, perhaps. I would need to know more about the hardware setup before I could attempt to reproduce it.

I tested the speed of lama models using exlama and noticed that the speed of 8b models is much slower than 7b (although this is not the case with other inferences. Can you tell me what the problem might be?
A100 80gb
tokens/s	tokens first second	symbols/sec
suzume-llama-3-8B-multilingual-gptq	63.96 ± 7.37	56.48 ± 16.76	96.78 ± 14.76
Swallow-7b-instruct-v0.1-gptq	194.56 ± 22.83	166.34 ± 40.23	165.04 ± 37.06
shisa-v1-llama3-8b-gptq	60.01 ± 9.03	58.92 ± 14.76	90.45 ± 15.50

GPTQ doesn't quantize the output layer, so with the much larger vocabulary of Llama3, the output tensor alone is about 750 MB larger. This adds a significant amount of latency.
Llama3 also uses GQA, which means you have a similar amount of computation for attention with somewhat lower VRAM overhead, but then the weights that would be assigned to keys/values are instead added to the MLP inner layer, making that slower instead.
I don't know that this accounts for the entire difference you're seeing, but certainly some of it. You could try with EXL2 models which do have quantized output layers, perhaps. I would need to know more about the hardware setup before I could attempt to reproduce it.

I think quantized output layers definitely make differences. I am benchmarking my constrained decoding library and even with A5000 I obtained 1.5x speedup in comparison to @freQuensy23-coder benchmark.


Cluster Checker Leadership Task

This pull request adds a leadership task called Cluster Checker which as the name implies checks the state of the cluster.
Primarily it uses the JobExecutions table to determine what nodes currently have running jobs. Using this list of hostnames it pings all the hosts health endpoints (by default /actuator/health) and if it doesn't get a 200 it flags it as currently being unable to reach it. If this occurs a certain number of times in a row (3 by default) it will mark all the jobs running on that node as FAILED due to the node being presumed lost.
Functionality can be extended later if there are other things to check or update when a node is unreachable. This functionality replaces the "zombie" functionality in earlier iterations of Genie which relied on the job monitors providing a heartbeat into the database which resulted in too much database locking and churn.
Properties added:
genie:
  leader:
    clusterChecker:
      scheme: http
      port: 8080
      rate: 300000
      lostThreshold: 3

Scheme and port are for what protocol and port the system should try to call other hosts with. The rate is how frequent the task should be run in milliseconds (defaults to every 5 minutes). lostThreshold is how many consecutive invocations a node needs to be unreachable for the jobs on it to be marked as failed.

Coverage increased (+0.1%) to 87.967% when pulling 87c06c5f71fc6814cc64c2a88821c9597331f5bc on tgianos:develop into 60afac68bae631df77f1d79c2522027f91fa4647 on Netflix:develop.


Remote Hosting + Server side rendering

Im having trouble geting my app deployed, using rehype-pretty-code as a unified plugin w/ server side rending and next js
tested on netifly and vercel, bpth providers seem not to bundle it with node modules at server side...
I tried setting the CDN and moving the to public/ with no luck in production.
any thoughts?

i feel like this should work but does not

https://github.com/vercel/next.js/issues/52711
people asking some question on vercel repo

lmfao not even going to speculate WHY this works, and server side version doesnt but
TLDR

vercel / netfily dont include shiki in node modules
using setCDN in the client side works
using setCDN in server side Doesnt work
static will always work cuz next is built wit all deps on vercel

I had the same issue trying to get ISR working and managed to fix it by adding this into my next.config.js
experimental: {
  outputFileTracingIncludes: {
    '/blog/[slug]': ['node_modules/shiki/**/*'],
  },
},

requires the newest version of next (13.4). This makes the shiki folder available for the route.

Works!!! tysm !!! @joinemm

The answer provided by joinemm above did not work for me.
I found this answer solved the whole mystery for me and made it all work:
https://github.com/shikijs/shiki/issues/138#issuecomment-1057471160
basically in nextjs there are 3 states:

build-time, on server -> this is getStaticProps
run-time, on server -> this is getServerSideProps, or getStaticProps in case of ISR, which is this issue
run-time, on client

We want Shiki on getServerSideProps. This means:

ALL languages are available
ALL themes are available
NONE of them are bundled into client side

The trick is:

Copy shiki/themes and shiki/languages to somewhere outside of node_modules, maybe under lib/shiki
Touch these folders in a server side function (e.g. fs.readdirSync)
Done!

The key here is to let Vercel nft to know about the existence of Shiki/themes and shiki/languages so they are included in the production run-time
Sample code: https://github.com/thien-do/memos.pub/blob/a3babb1f149f05c43012278331f885d81f5fcfac/lib/mdx/plugins/code.ts
credit to thien-do

The answer provided by joinemm above did not work for me.
I found this answer solved the whole mystery for me and made it all work: shikijs/shiki#138 (comment)
basically in nextjs there are 3 states:

build-time, on server -> this is getStaticProps
run-time, on server -> this is getServerSideProps, or getStaticProps in case of ISR, which is this issue
run-time, on client

We want Shiki on getServerSideProps. This means:

ALL languages are available
ALL themes are available
NONE of them are bundled into client side

The trick is:

Copy shiki/themes and shiki/languages to somewhere outside of node_modules, maybe under lib/shiki
Touch these folders in a server side function (e.g. fs.readdirSync)
Done!

The key here is to let Vercel nft to know about the existence of Shiki/themes and shiki/languages so they are included in the production run-time
Sample code: https://github.com/thien-do/memos.pub/blob/a3babb1f149f05c43012278331f885d81f5fcfac/lib/mdx/plugins/code.ts
credit to thien-do

Been tinkering with this for a bit. My setup is trying to parse mdx using next-remote-mdx in a page in the app directory and I still can't get this to work for me. My code structure for the lib portion is exactly the same, and then I have a function called FetchMDXFiles that I call within my page component which contains:
// inside my fetchMDXFile();
  const { content } = await compileMDX({
            components: defaultComponents,
            source: mdx.data,
            options: {
              mdxOptions: {
                remarkPlugins: [remarkGfm],
                rehypePlugins: [
                  serializeClipboardContent,
                  ...(getMDXCode as any), // dealing with some ts-bs atm
                  deserializeClipboardContent,
                ],
              },
            },
          });

Then for my page I have:
async function MyPage() {
const MDX = await fetchMDXFile();
// ... more code

I would think that calling these functions within my app dir page would be sufficient to 'mark' the files, but nonetheless when it hits this line of code const getShikiPath = (): string => pathJoin(process.cwd(), 'lib/mdx/shiki'); from the example in the solution, it can't find the file. My folder structure for lib is exactly the same as in the example. If anyone has any thoughts or has gotten this working in app dir page with next-mdx-remote lmk, it's be greatly appreciated.


Add methods for parsing tabulated results files?

I think it would be great if we had a method/some methods for parsing the results data fetched from FEM-Design via .bsc batch files.
This could handle the information in the headers, instead of the user having to implement some custom method for parsing the tab (\t) separated values. Also dynamo can read csv files but not tsv.

#7


Add GitHub Pages link to README

Pull Request Test Coverage Report for Build 5fdd0082113d2f1df4beaca3f8c58fdc12fd3324-PR-3

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

Totals

Change from base Build 7b1b6d31187f559c178b2321a26544010ab89957:
0.0%

Covered Lines:
177

Relevant Lines:
177

💛  - Coveralls


does it have ability to collect multiple controls in one button?

Hi, one thing in animschool picker is that we were able to select multiple controls and create a button for that, which is very handy and helpful, I didn't see that option in the picker, wonder if i missed it somewhere. It's not a bug though, but I don't know where else I should wrote this.

sorry I found it has, don't know how to close this.

Auto resolved ticket ! The best ones :)


Added missing AGSI and ALSI Codes

Hi Frank
I added some missing AGSI and ALSI EIC Codes and kept you structure. Hope this works for you.

ah great! I didnt check for some time so great that people like you add them when needed ;) same structure is indeed nice will merge!

Perfect, thank you! 😄


[SPARK-23821][SQL] Collection function: flatten

What changes were proposed in this pull request?
This PR adds a new collection function that transforms an array of arrays into a single array. The PR comprises:

An expression for flattening array structure
Flatten function
A wrapper for PySpark

How was this patch tested?
New tests added into:

CollectionExpressionsSuite
DataFrameFunctionsSuite

Can one of the admins verify this patch?

Thanks for your contribution! Try to improve your test cases by reading the other open source code (e.g., this)?

ok to test

Test build #88758 has started for PR 20938 at commit 755d6db.

Test build #88758 has finished for PR 20938 at commit 755d6db.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Flatten(child: Expression) extends UnaryExpression

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88758/
Test FAILed.

Merged build finished. Test FAILed.

Rewrote test cases. @gatorsmile  Please let me know if it's OK.

Test build #88836 has started for PR 20938 at commit ad46962.

Test build #88836 has finished for PR 20938 at commit ad46962.

This patch fails from timeout after a configured wait of `300m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88836/
Test FAILed.

retest this please

Any other comments?

Test build #89055 has started for PR 20938 at commit a50d42e.

Test build #89055 has finished for PR 20938 at commit a50d42e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89055/
Test FAILed.

Can't reproduce it locally and seems to unrelated...

retest this please

Test build #89093 has started for PR 20938 at commit e213341.

Test build #89093 has finished for PR 20938 at commit e213341.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89093/
Test FAILed.

retest this please

Test build #89104 has started for PR 20938 at commit e213341.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89104/
Test FAILed.

Any idea why those tests are failing?

Test build #89119 has started for PR 20938 at commit b9d99f7.

cc @ueshin

Test build #89119 has finished for PR 20938 at commit b9d99f7.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
sealed trait Node extends Serializable
sealed trait ClassificationNode extends Node
sealed trait RegressionNode extends Node
sealed trait LeafNode extends Node
sealed trait InternalNode extends Node
case class ExprCode(var code: String, var isNull: ExprValue, var value: ExprValue)
case class SubExprEliminationState(isNull: ExprValue, value: ExprValue)
abstract class ExprValue
class LiteralValue(val value: String, val javaType: String) extends ExprValue
case class VariableValue(
case class StatementValue(
case class GlobalValue(val value: String, val javaType: String) extends ExprValue

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89119/
Test PASSed.

Merged build finished. Test PASSed.

Test build #89303 has started for PR 20938 at commit 0e0def4.

Test build #89303 has finished for PR 20938 at commit 0e0def4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89303/
Test PASSed.

Test build #89393 has started for PR 20938 at commit 1a3ec1f.

Test build #89404 has started for PR 20938 at commit 2ceb53b.

Test build #89393 has finished for PR 20938 at commit 1a3ec1f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89393/
Test PASSed.

Test build #89404 has finished for PR 20938 at commit 2ceb53b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89404/
Test PASSed.

Test build #89442 has started for PR 20938 at commit e21c306.

Test build #89453 has started for PR 20938 at commit 207eb5a.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89442/
Test FAILed.

Test build #89454 has started for PR 20938 at commit 10849d7.

Test build #89454 has finished for PR 20938 at commit 10849d7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89454/
Test FAILed.

Test build #89492 has finished for PR 20938 at commit 10849d7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89492/
Test PASSed.

Test build #89503 has started for PR 20938 at commit 57f554b.

Test build #89503 has finished for PR 20938 at commit 57f554b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class Summarizer(object):
class SummaryBuilder(JavaWrapper):
case class Reverse(child: Expression) extends UnaryExpression with ImplicitCastInputTypes
class ArrayDataIndexedSeq[T](arrayData: ArrayData, dataType: DataType) extends IndexedSeq[T]

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89503/
Test FAILed.

Test build #89518 has started for PR 20938 at commit 9081291.

Test build #89518 has finished for PR 20938 at commit 9081291.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89518/
Test FAILed.

retest this please

Test build #89559 has started for PR 20938 at commit f11aa7b.

Test build #89574 has started for PR 20938 at commit 88c4971.

Test build #89575 has started for PR 20938 at commit 37b68cd.

Test build #89559 has finished for PR 20938 at commit f11aa7b.

This patch fails from timeout after a configured wait of `300m`.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ArrayPosition(left: Expression, right: Expression)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89559/
Test FAILed.

Jenkins, retest this please.

Test build #89582 has started for PR 20938 at commit 37b68cd.

Test build #89574 has finished for PR 20938 at commit 88c4971.

This patch fails from timeout after a configured wait of `300m`.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ElementAt(left: Expression, right: Expression) extends GetMapValueUtil
abstract class GetMapValueUtil extends BinaryExpression with ImplicitCastInputTypes
case class GetMapValue(child: Expression, key: Expression)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89574/
Test FAILed.

Test build #89575 has finished for PR 20938 at commit 37b68cd.

This patch fails from timeout after a configured wait of `300m`.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ElementAt(left: Expression, right: Expression) extends GetMapValueUtil

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89575/
Test FAILed.

Test build #89582 has finished for PR 20938 at commit 37b68cd.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ElementAt(left: Expression, right: Expression) extends GetMapValueUtil

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89582/
Test PASSed.

LGTM pending Jenkins.

Jenkins, retest this please.

Test build #89631 has started for PR 20938 at commit 939fc23.

Test build #89631 has finished for PR 20938 at commit 939fc23.

This patch fails from timeout after a configured wait of `300m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89631/
Test FAILed.

retest this please

Test build #89658 has finished for PR 20938 at commit 939fc23.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89658/
Test PASSed.

retest this please

Test build #89775 has started for PR 20938 at commit 939fc23.

Test build #89775 has finished for PR 20938 at commit 939fc23.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89775/
Test FAILed.

retest this please

Test build #89783 has started for PR 20938 at commit 939fc23.

Test build #89783 has finished for PR 20938 at commit 939fc23.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89783/
Test FAILed.

retest this please

Test build #89788 has started for PR 20938 at commit 939fc23.

Test build #89788 has finished for PR 20938 at commit 939fc23.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.


STORM-2058: Fix Maven warnings about missing reporting.plugins.plugin.version

Add versions for maven-javadoc-plugin and maven-surefire-report-plugin to the parent pom.xml.

+1

+1


Add ability to insert script / style content to the head a la Helmet

possibly wrap content in custom element <enhance-head></enhance-head>?

<enhance-halo></enhance-halo>
<enhace-hooves></enhance-hooves>

<enhance-head></enhance-head> <enhace-toes></enhance-toes>

Quick and dirty:
Strip all script tags from template and add them to the  bottom of the body.
Strip all Style tags from template and add them to the head.

Closed for now. v2.3.0 now copies style tags with scope="global" to the head and ALL script tags to the end of the bottom.


Extend coverage on uniswapPair mint()

I just finished part 3 of the echidna streaming series and I noticed that coverage didnt marked  * on liquidity mint after the intial scenario were totalSupply was cero. I modified our invariant test to extend this and have full coverage on UniswapPair mint() function.

I moved the initial preconditions and action to a public function: mintLiquidty() that can be called previous to our target test testProvideLiquidity(). Additionaly, I modified the amount bounding to only account for the initial liquidity minting which is the only moment where we need to provide at least 1000 tokens.

Looking forward to get some feedback and keep learning from the streaming series!

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hmm, that's a bit odd. The fuzzer should be able to get that line just by calling testProvideLiquidity multiple times. In fact I tested this with testLimit: 20000 and it could hit that line.

I see, It makes sense if it calls  testProvideLiquidity multiple times. I will try running the fuzzer with testLimit: 20000 looking for this then.
Just a thought, after the first call to testProvideLiquidity there is no need to bound the amount between 1000 and uint(-1), correct?
Thanks for the help!


Check for scheme and host before fetching url content

Some html content gets misinterpreted as URL, which causes Addressable::URI::InvalidURIError.
To prevent this error, we can check for a valid schema and host set in src before we attempt to fetch the URL.
Sample HTML:
<!DOCTYPE html>
<html>
  <head>
    <meta name="twitter:title" property="og:title" itemprop="title name" content="OpenGraph Title" />
    <meta property="og:url" content="https://www.example.com/page.html" />
  </head>
</html>

Closing in favor of https://github.com/mobomo/opengraph


Make CryptoScrypt method public and include keyLength option

Makes CryptoScrypt method public and includes a keyLength option
Also bumps netstandard to 2.0.
We needed this exposed to get hash compatibility with an existing app of ours.
It's a bit of a shame the Scrypt algorithm isn't exposed at all right now, using reflection on unsafe methods is almost impossible.

Thanks so much for merging this quickly!
We're running a forked version right now but...
Would a release be in the cards by any chance soon?


fix(e2e): disable pipelines operator

Description
Disabled the installation of pipelines operator to allow namespace deletion
Which issue(s) does this PR fix
https://issues.redhat.com/browse/RHIDP-4752
PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

/retest

Recent merged PRs by @gustavolira make this redundant.


Rebuild

Rebuilding because we are missing artifacts on linux-aarch64 and linux-s390x.

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_0esklgfq9j/clone/recipe/meta.yaml:40: missing_description: The recipe is missing a description
Warnings were found


Fix variable shadowing warnings

Should fix #51
For the PINCache's objectForKey method I added a clang compiler pragma to suppress showing up the shadowing warnings. This is only for the weakSelf / strongSelf variables. There should be no other variables be shadowed anymore.
We could certainly go without the clang pragma, we should just come up with good names for all of this shadowed weakSelf / strongSelf variables than :)

I think the pragma makes sense in this case. Thanks for doing this!


Add memo text service and bump python-velbus to 2.0.37

Proposed change

Add service to set the memo text to be displayed at Velbus glass control modules like VMBGPO(D) and VMBELO
Type of change

[x] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[x] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

Updates the python-velbus lib to version 2.0.37 to support "Memo text" feature.
Link to documentation pull request: #11892

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist
[x] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

[ ] No score or internal
[x] 🥈 Silver
[ ] 🥇 Gold
[ ] 🏆 Platinum

can someone have a look at this one?
it would be good if we can get this merged


currently not support the newly added format CL_ABGR?

after mesa2204 updated, the format CL_ABGR is not support yet. If following code is added in function read_image_pixel (imageHelpers.h), the test case for CL_ABGR will be passed.
 else if (format->image_channel_order == CL_ABGR)     {         outData[0] = tempData[3];         outData[1] = tempData[2];         outData[2] = tempData[1];         outData[3] = tempData[0];     }

Hello!  This seems reasonable for me.  Would you mind making a PR with this addition?  Thanks!

The PR has committed.  https://github.com/KhronosGroup/OpenCL-CTS/pull/1474,  please help to review, Thanks!


Unnecesary .js

Is included in misc.html
I had made this pull request, but I was correcting it wrong. This is the correct solution.

Today is not my day, I had an old version of the misc.html file, sorry!


[WIP] Update to ReactiveCocoa 3.0

:warning: NOT READY TO MERGE :warning:
Depends on ReactiveCocoa/ReactiveCocoa#966.
To do:

[ ] Refactor -fetch… methods to return cold signals
[ ] Use more idiomatic RAC 3.0 names for methods returning signals

Produits Madame on morocco


Update consolidate to get Liquid support.

Closes issue #4.

Would really like to see liquid support.


I added zoho MX records

Requirements

[ ] You have completed your website.
[ ] The website is reachable.
[ ] The CNAME record doesn't contain https:// or /.
[ ] There is sufficient information at the owner field.

Description

Website Link / Preview

Hi,
I just want to make sure you saw my request for adding Zoho MX records.
Please contact me if this operation can't be performed for one reason or another.
Mohamed Blaiech
email<EMAIL_ADDRESS>


Access to vault with custom certificate

I have configured  the plugin to connect to a remote delinea server. Unfortunaltely I got an x509: certificate signed by unknown authority error.
I've tried to :

add the CA chain in sidecar container image trust store
add the CA chain in argocd `/app/config/tls.
use VAULT_SKIP_VERIFY option

As the solutions doesn't work. Is there a documentation who list where the plugin is retreiving the trusted CA ?

https://github.com/argoproj-labs/argocd-vault-plugin/issues/503

thanks !


Using existing coordinates as an initial condition

I have a graph which already has coordinates on the nodes. Is there a way to leverage those to use as a starting point for the algorithm, to reduce the computation ?
I was also wondering if it was possible to fix the coordinates of some nodes so they have a fixed position ?
If these features are not available, I don't mind changing the code source but some pointers would really help me
Thanks

I have same requirement (fix coordinates of some nodes) - let me know if you have made any progress on this topic


⚠ Spryr has degraded performance

In 9720dc0, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3102 ms

Resolved: Spryr performance has improved in 1bf61c5 after 25 minutes.


Start using esbuild

No idea where the original issue went, i remember discussing this with the team as well.
Suggestion:

Use esbuild for the webview stuff (will be faster)

Going to try out esbuild. Start with ipywidgets.

Gave up on this idea. There's a lot of stuff that esbuild doesn't support.

Biggest problem - dynamic requires. Jupyterlab does this in a bunch of spots.

https://github.com/evanw/esbuild/issues/1921

All we now need is esbuild for the main bundle,
All of the following are done

IPyWidgets,
Renderers
Variable viewer
Plot viewer
DF viewer

Closing this for now, as we have implemented this in all places except for the main bundles.


Searching multiple terms on multiple fields with different boost using Index.query

I would like to know to write the search query efficiently for searching multiple terms on multiple fields with different boost
I have set of fields

title with boost 10
heading with boost 5
text with boost 3
keywords with boost 6

and would like to search "foo bar" or "foo bar*"
Since build time boost is not supported in 2.1.2, I am using query time boost.
However would like to use to search with and without trailing wildcard
and with/without usepipeline to get the best results.
Please let me know an efficient way to write query using Index.query or Index.search.

You could use something like this (tested in 2.1.0):
const query = 'foo bar';
const idx = ...;
const matches =  idx.query(q => {
    q.term(query, { fields: [ 'title' ], boost: 10 });
    q.term(query, { fields: [ 'heading' ], boost: 5 });
    q.term(query, { fields: [ 'text' ], boost: 3 });
    q.term(query, { fields: [ 'keywords' ], boost: 6 });

    q.term(query, { fields: [ 'title' ], boost: 10, wildcard: lunr.Query.wildcard.TRAILING });
    q.term(query, { fields: [ 'heading' ], boost: 5, wildcard: lunr.Query.wildcard.TRAILING });
    q.term(query, { fields: [ 'text' ], boost: 3, wildcard: lunr.Query.wildcard.TRAILING });
    q.term(query, { fields: [ 'keywords' ], boost: 6, wildcard: lunr.Query.wildcard.TRAILING });
  });
});

You can add usePipeline: false, editDistance: ... etc. as normal inside there. We're using something similar in production.

What @jakeapeters has looks good, one thing to be careful of though is that the query string passed to q.term will not be split into multiple tokens by lunr. I.e. if query is the string "foo bar" it will search for "foo bar" not "foo", "bar", with the default index builder this will mean you won't get any results.
You can borrow Lunr's tokenizer, or use the regex it uses directly:
idx.query(function (q) {
  lunr.tokenizer(queryString).forEach(function (token) {
    q.term(token.toString(), { fields: [ 'title' ], boost: 10 })
    // etc....
  })
})

or, just borrow the regex:
idx.query(function (q) {

  queryString.split(lunr.tokenizer.separator).forEach(function (term) {
    q.term(term, { fields: [ 'title' ], boost: 10 })
    // etc....
  })
})

thanks @jakeapeters  and @olivernn.

@olivernn , do you plan to support build time boost?

@myalgo please open a new issue requesting build time boost.
I'm going to close this issue now as I think the original problem is solved.


RFC: update FS API for readdir consistency

The filesystem fs_readdir() API does not specify whether the special directory entries "." (representing the current directory) and ".." (representing the parent directory) are included in the results.
Existing file systems FatFS (by default) and NFFS (always?) do not produce these directories in the underlying function.  littlefs does produce them.  The result is that applications that switch between file system providers may need to update code that processes fs_readdir results.
There is little value in providing these paths, since the fs_dirent_t doesn't provide useful information about directories.  But there is less value in having the behavior of the Zephyr abstraction layer inconsistent without acknowledging that it can happen.
Two candidate resolutions:

(1) Specify that fs_readdir returns every entry provided by the underlying implementation, whether or not the corresponding entry is provided by other implementations;
(2) Specify that fs_readdir at the abstraction level will discard directory entries "." and ".." without returning them if the underlying implementation produces them.

I'm excluding the option of doing filtering only in underlying implementations that might/do produce these entries: there's a greater risk of a new implementation forgetting to do the filtering, and it complicates a potential future option to synthesize them at the abstraction layer (e.g. when they're desired).
Note that in either case this does not change the API signature, it only clarifies the expected behavior.
If no clear preference is found the results of fs_readdir will remain inconsistent across file system implementations.

See: https://github.com/zephyrproject-rtos/zephyr/pull/17749#discussion_r309771674
which supports option 2 so POSIX compliance and other users of the abstraction don't have to deal with inconsistent lower-level behavior.

Fixed in #17749.


sorry if in wrong spot - but can this make a 3xl look like an xl?

sorry if in wrong spot - but can this make a 3xl look like an xl? i'd like to spoof my 3xl into appearing as an xl thx

You can always try the device simulation feature.
If that's not enough you can try changing more props with the "Add/edit custom props" feature. "But which ones should I change", you ask.You'd have to do that research yourself, I have no idea...


Add fancytree.js to dependencies

Why you don't add "bower-asset/fancytree": "*" in dependencies of composer.json?

Hello, guys.
When I do composer uptate after add
"wbraganca/yii2-fancytree-widget": "*"
in "require-dev", it shows:
Problem 1
- Installation request for wbraganca/yii2-fancytree-widget * -> satisfiable by wbraganca/yii2-fancytree-widget[dev-master].
- wbraganca/yii2-fancytree-widget dev-master requires bower-asset/fancytree * -> no matching package found.
How can I fix it? I searched on packagist.org for bower-asset/fancytree and it really doesn't exist.

any update on this?

I solved my problem inserting this in composer.json (require):
"dantleech/fancytree": "dev-composer"


Build connection between User and Observation

We need to figure out the concept of group in this app and build the connection accordingly

Considering the fact that this connection be by no means directly used, we decide to not build relationship between the two.


Unable to create a project from AZURE SQL Database

Issue Type: Bug
When I try to create project from Azure SQL Database getting error cannot read property 'exports' of undefined
Azure Data Studio version: azuredatastudio 1.31.1 (65fb22cc7c36db9c53af1ed2fdbdf48f66c682be, 2021-07-28T21:03:21.018Z)
OS version: Windows_NT x64 10.0.18363
Extensions (8)

Extension
Author (truncated)
Version

admin-pack
Mic
0.0.2

agent
Mic
0.48.0

asde-deployment
Mic
0.4.1

dacpac
Mic
1.8.0

import
Mic
1.3.1

profiler
Mic
0.11.0

schema-compare
Mic
1.11.0

sql-database-projects
Mic
0.11.0

@seemaht can you try the latest sql database projects extension (0.12.0) and see if this error is still happening?