Dependencies for python function env doesn't available

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v19.4.0
Amplify CLI Version
10.6.2
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

amplify/backend/function/<function_name>/<function_name>/.json
amplify/backend/function/<function_name>/function-parameters.json

In both files tried to add a lambda layer:
{
  "lambdaLayers": [
    "arn:aws:lambda:eu-central-1:770693421928:layer:Klayers-p38-Pillow:5"
  ]
}

Describe the bug
Dependencies described in pipfile are available during AWS Lambda invokation.
Pipfile:
[pipenv]
install_search_all_sources = true

[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[dev-packages]

[packages]
src = {editable = true, path = "./src"}
qrcode = "*"
pillow = "*"

[requires]
python_version = "3.8"

Error in lambda logs:
{
  "errorMessage": "No module named 'Image'",
  "errorType": "ModuleNotFoundError",
  "stackTrace": [
    "  File \"/var/task/index.py\", line 44, in handler\n    qr_code = generate_qr_code(client_id)\n",
    "  File \"/var/task/index.py\", line 33, in generate_qr_code\n    img = qr.make_image(fill='black', back_color='white')\n",
    "  File \"/var/task/qrcode/main.py\", line 296, in make_image\n    from qrcode.image.pil import PilImage\n",
    "  File \"/var/task/qrcode/image/pil.py\", line 7, in <module>\n    import Image\n"
  ]
}

For workaround tried to use AWS Lambda layer: arn:aws:lambda:eu-central-1:770693421928:layer:Klayers-p38-Pillow:5 .
Didn't help
Expected behavior
All packages are available in AWS Lambda environment.
Reproduction steps

Prepare pipfile
amplify push
Invoke AWS Lambda

Project Identifier
6f249002b8fc478995bb9b2f5931c3ba
Log output

2023-01-27T19:26:52.004Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]ify-[***]ycli-[***]ev-[***]641"}])
2023-01-27T19:26:52.322Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]ral-[***]90:stack/[***]ify-[***]ycli-[***]ev-[***]641-[***]bycli-[***]P0A8H/[***]44f0-[***]5f-[***]ed-[***]b8-[***]9e51a"}])
2023-01-27T19:26:52.328Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]ral-[***]90:stack/[***]ify-[***]ycli-[***]ev-[***]641-[***]6b56418e-[***]MULZF/[***]5100-[***]a9-[***]ed-[***]7b-[***]b1b7a"}])
2023-01-27T19:26:52.330Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]ral-[***]90:stack/[***]ify-[***]ycli-[***]ev-[***]641-[***]dgenerateqrcodes-[***]ZXCM9C/[***]2fd0-[***]30-[***]ed-[***]a7-[***]41d40"}])
2023-01-27T19:26:52.331Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:eu-[***]ral-[***]90:stack/[***]ify-[***]ycli-[***]ev-[***]641-[***]6e82f73-[***]OWI9ZF/[***]4b60-[***]24-[***]ed-[***]9a-[***]519c6"}])
2023-01-27T19:26:52.656Z|info : amplify-provider-awscloudformation.aws-s3.deleteObject.s3([{"BucketName":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment","FilePath":"deployment-state.json"}])
2023-01-27T19:26:52.657Z|info : amplify-provider-awscloudformation.aws-s3.checkExistObject.s3([{"BucketName":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment","FilePath":"deployment-state.json"}])
2023-01-27T19:26:52.957Z|info : amplify-provider-awscloudformation.aws-s3.checkExistObject.s3([{"BucketName":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment","FilePath":"deployment-state.json","Error":"NotFound"}])
2023-01-27T19:26:55.515Z|info : amplify-provider-awscloudformation.push-resources.storeCurrentCloudBackend.s3.uploadFile([{"Key":"[***]rent-[***]ud-[***]d.zip"}])
2023-01-27T19:26:55.517Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/backend/.temp/[***]rent-[***]ud-[***]d.zip","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"#current-cloud-backend.zip","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:26:56.009Z|info : amplify-provider-awscloudformation.aws-s3.deleteDirectory.s3.getAllObjectVersions([{"BucketName":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:26:56.010Z|info : amplify-provider-awscloudformation.aws-s3.getAllObjectKey.s3.listObjectVersions([{"Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment","Prefix":"studio-backend"}])
2023-01-27T19:26:56.260Z|info : amplify-provider-awscloudformation.aws-s3.deleteAllObjects.s3.deleteObjects (0 of 1)([{"Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.819Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/cli.json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.822Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/amplify-meta.json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]ify-[***]json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.824Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/backend-config.json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]end-[***].json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.825Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/api/qrsbycli/build/schema.graphql","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]pi/[***]ycli/[***]ld/[***]raphql","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.826Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/api/qrsbycli/schema.graphql","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]pi/[***]ycli/[***]raphql","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.827Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/api/qrsbycli/transform.conf.json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]pi/[***]ycli/[***]onf.json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.828Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/api/qrsbycli/build/parameters.json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]pi/[***]ycli/[***]ld/[***]s.json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.829Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/api/qrsbycli/parameters.json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]pi/[***]ycli/[***]s.json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.829Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/auth/qrsbycli6b56418e/build/parameters.json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]th/[***]b56418e/[***]ld/[***]s.json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:02.830Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/storage/s366e82f73/build/parameters.json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"[***]dio-[***]end/[***]age/[***]2f73/[***]ld/[***]s.json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:03.282Z|info : amplify-provider-awscloudformation.amplify-service-manager.s3.uploadFile([{"Key":"[***]ify-[***]json"}])
2023-01-27T19:27:03.287Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/[***]ify-[***]json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"amplify-meta.json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:03.683Z|info : amplify-provider-awscloudformation.amplify-service-manager.s3.uploadFile([{"Key":"[***]end-[***].json"}])
2023-01-27T19:27:03.685Z|info : amplify-provider-awscloudformation.aws-s3.uploadFile.s3.putObject([{"Body":{"_readableState":{"objectMode":false,"highWaterMark":65536,"buffer":{"head":null,"tail":null,"length":0},"length":0,"pipes":[],"flowing":null,"ended":false,"endEmitted":false,"reading":false,"sync":true,"needReadable":false,"emittedReadable":false,"readableListening":false,"resumeScheduled":false,"errorEmitted":false,"emitClose":true,"autoDestroy":false,"destroyed":false,"errored":null,"closed":false,"closeEmitted":false,"defaultEncoding":"utf8","awaitDrainWriters":null,"multiAwaitDrain":false,"readingMore":false,"dataEmitted":false,"decoder":null,"encoding":null},"_events":{},"_eventsCount":1,"path":"/Users/peter/POCs/qrs_by_aws_constructor/amplify/#current-cloud-backend/[***]end-[***].json","fd":null,"flags":"r","mode":438,"end":null,"autoClose":true,"bytesRead":0,"closed":false},"Key":"backend-config.json","Bucket":"[***]ify-[***]ycli-[***]ev-[***]641-[***]ment"}])
2023-01-27T19:27:05.571Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["default"])
2023-01-27T19:27:05.574Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-central-1"}])
2023-01-27T19:27:05.575Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["default"])
2023-01-27T19:27:09.688Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["default"])
2023-01-27T19:27:09.690Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-central-1"}])
2023-01-27T19:27:09.690Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["default"])
2023-01-27T19:32:13.912Z|info : amplify diagnose core  {"send-report":true,"yes":false}
2023-01-27T19:32:13.975Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @peter-iglaev, thank you for reaching out. Could you check the Lambda function layer section on AWS console to see if a Layer has been attached?

From the information I understand that the Lambda layers are being manually added in the function-parameters.json file. The file expects a format as follows.
{
  "lambdaLayers": [
    {
      "type": "ExternalLayer",
      "arn": "arn:aws:lambda:us-east-1:<account ID>:layer:grcp88:1"
    }
  ]
}

But I would suggest utilizing the Amplify CLI to add the layers to your function. by running amplify update function as this will automatically add the layer to parameters file.
amplify update function
? Select the Lambda function you want to update test
General information
- Name: test
- Runtime: python

Resource access permission
- Not configured

Scheduled recurring invocation
- Not configured

Lambda layers
- undefined

Environment variables:
- Not configured

Secrets configuration
- Not configured

? Which setting do you want to update? Lambda layers configuration
? Do you want to enable Lambda layers for this function? Yes
? Enter up to 5 existing Lambda layer ARNs (comma-separated): arn:aws:lambda:us-east-1:<account ID>:layer:grcp88:1
? Do you want to edit the local lambda function now? No

Hey, @ykethan.
I tried to use the python package arcade + Pillow.
As I figured out, the issue was with Pillow package.
I changed it to Segno and it fixed the issue.
'
Not related to amplify.
Feel free to close the ticket.
Thanks.


Merging of the PR

@luishdez  You seem to be driving the train at the moment in regards to the open PRs.  I haven't had a ton of time lately so the effort is appreciated.
I am starting to free up a little and can lend some time.  I am giving a second eye on some of these PR's you have reviewed and tagged, my question is after I look over them and think they are good do you want me to proceed with merge?  Are you covering the merges working out a proper order so they can be merged smoothly?
Just wanted to get this sorted out so we aren't stepping on each other.

Sure!! That's awesome. Next week I'll be traveling so it will keep things moving. Go ahead.
My strategy so far is:

locate easy merges: https://github.com/chef-brigade/mongodb-cookbook/labels/merge%3A easy
I think you can merge all of them without following any order because they won't conflict. ( I can't assure you 100% ) But these PRs are small and easy to manage.

The rest of PRs are tagged with merge: complex and comp: replicaset most of them modify a lot of core features and multiple files per PR… mainly the replicaset feature.

Trying to merge those prs it will be too complex. I would do is drop all of them and work in a new branch feature/lwrp once is complete work on feature/replicaset … But taking the ideas/code from those closed PRs. Imho it will be easy to work in a clean slate.

Closing this to keep it clean :)


It looks like the project doesn't support quadruped?

The paper mentioned that Eureka also achieved human-level performance in quadruped environments, but I did not find the relevant script in eureka/cfg/env.

emm, maybe it's anymal.


Toggling alpha transparency opens a new kitty window

Hi and thanks so much for making this!
I am using kitty version 0.15.1 and termpdf version 0.1.1.
All shortcuts detailed in the README works for me except for toggling alpha transparency. When I press a a new kitty window opens. If I close this I get back to the previous window displaying the pdf but the transparency hasn't changed.
I am not using any config file for termpdf. Could the problem be related to the specification of KITTYCMD since a new window is opened?
EDIT: Looked through the code and found that the mapping was A rather than a. Pressing A toggles transparency fine!

Right! 'a' was for 'annotate'. Not the best mappings.


coursera-dl: 0.10.0 -> 0.11.4

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/coursera-dl/versions.
These checks were done:

built on NixOS
Warning: no invocation of /nix/store/hm287cky1fz2ly43w09g1w2dxz32s5kr-coursera-dl-0.11.4/bin/.coursera-dl-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hm287cky1fz2ly43w09g1w2dxz32s5kr-coursera-dl-0.11.4/bin/coursera-dl had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 0.11.4 with grep in /nix/store/hm287cky1fz2ly43w09g1w2dxz32s5kr-coursera-dl-0.11.4
directory tree listing: https://gist.github.com/39a16f9c8648d348a2e1b66d2cdf2da6
du listing: https://gist.github.com/62d2b7ec0ea15390e94e43f268a9f511

meta.description for coursera-dl is: '"CLI for downloading Coursera.org videos and naming them"'.
cc @alexfmpe for testing.
This build is cached with Cachix. To use the cache follow these instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout ab55ba3599e2e88b0073f4d016f73c590b58695c && nix-shell --pure -I nixpkgs=. -p coursera-dl

@GrahamcOfBorg eval

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: coursera-dl
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Traceback (most recent call last):
  File "/nix/store/hm287cky1fz2ly43w09g1w2dxz32s5kr-coursera-dl-0.11.4/bin/.coursera-dl-wrapped", line 8, in <module>
    from coursera.coursera_dl import main
  File "/nix/store/hm287cky1fz2ly43w09g1w2dxz32s5kr-coursera-dl-0.11.4/lib/python3.6/site-packages/coursera/coursera_dl.py", line 73, in <module>
    from .api import expand_specializations
  File "/nix/store/hm287cky1fz2ly43w09g1w2dxz32s5kr-coursera-dl-0.11.4/lib/python3.6/site-packages/coursera/api.py", line 19, in <module>
    import attr
ModuleNotFoundError: No module named 'attr'

Not sure how to contribute to the bot's repo - so I opened #43050


RuntimeError: Error compiling objects for extension

Followed all these steps
The Environment：
Linux (tested on Ubuntu 16.04)
Python 3.7.6
PyTorch 1.20 + CUDA-10.0/10.1
a. Clone the EPNet++ repository.
git clone https://github.com/happinesslz/EPNetV2.git
b. Create conda environment.
conda create -n epnet_plus_plus_open python==3.7.6
conda activate epnet_plus_plus_open
conda install pytorch==1.2.0 torchvision==0.4.0 cudatoolkit=10.0 -c pytorch
pip install -r requirements.txt
c. Build and install the pointnet2_lib, iou3d, roipool3d libraries by executing the following command:
sh build_and_install.sh    ( When I run this command get this error)
FAILED: /home/fazal/Downloads/EPNetV2/lib/utils/sample2grid/build/temp.linux-x86_64-cpython-37/Voxel_gpu.o
/usr/bin/nvcc  -I/home/fazal/.local/lib/python3.7/site-packages/torch/include -I/home/fazal/.local/lib/python3.7/site-packages/torch/include/torch/csrc/api/include -I/home/fazal/.local/lib/python3.7/site-packages/torch/include/TH -I/home/fazal/.local/lib/python3.7/site-packages/torch/include/THC -I/home/fazal/Downloads/EPNetV2/lib/utils/sample2grid -I/home/fazal/anaconda3/envs/epnet/include/python3.7m -c -c /home/fazal/Downloads/EPNetV2/lib/utils/sample2grid/Voxel_gpu.cu -o /home/fazal/Downloads/EPNetV2/lib/utils/sample2grid/build/temp.linux-x86_64-cpython-37/Voxel_gpu.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -O2 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=gridvoxel_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -gencode=arch=compute_86,code=compute_86 -gencode=arch=compute_86,code=sm_86 -std=c++14
/home/fazal/Downloads/EPNetV2/lib/utils/sample2grid/Voxel_gpu.cu(29): warning #177-D: variable "grid_H" was declared but never referenced
/home/fazal/Downloads/EPNetV2/lib/utils/sample2grid/Voxel_gpu.cu(30): warning #177-D: variable "grid_Coor" was declared but never referenced
/home/fazal/Downloads/EPNetV2/lib/utils/sample2grid/Voxel_gpu.cu(106): warning #177-D: variable "grid_H" was declared but never referenced
/usr/include/c++/11/bits/std_function.h:435:145: error: parameter packs not expanded with ‘...’:
435 |         function(_Functor&& __f)
|                                                                                ^
/usr/include/c++/11/bits/std_function.h:435:145: note:         ‘_ArgTypes’
/usr/include/c++/11/bits/std_function.h:530:146: error: parameter packs not expanded with ‘...’:
530 |         operator=(_Functor&& __f)
|                                                                                ^
/usr/include/c++/11/bits/std_function.h:530:146: note:         ‘_ArgTypes’
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "/home/fazal/.local/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1906, in _run_ninja_build
env=env)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "setup.py", line 18, in
, include_dirs = ['./'],
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/init.py", line 87, in setup
return distutils.core.setup(**attrs)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 185, in setup
return run_commands(dist)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
dist.run_commands()
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
self.run_command(cmd)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/dist.py", line 1208, in run_command
super().run_command(command)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
cmd_obj.run()
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/command/install.py", line 74, in run
self.do_egg_install()
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/command/install.py", line 123, in do_egg_install
self.run_command('bdist_egg')
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/dist.py", line 1208, in run_command
super().run_command(command)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
cmd_obj.run()
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/command/bdist_egg.py", line 165, in run
cmd = self.call_command('install_lib', warn_dir=0)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/command/bdist_egg.py", line 151, in call_command
self.run_command(cmdname)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/dist.py", line 1208, in run_command
super().run_command(command)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
cmd_obj.run()
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/command/install_lib.py", line 11, in run
self.build()
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/command/install_lib.py", line 112, in build
self.run_command('build_ext')
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/dist.py", line 1208, in run_command
super().run_command(command)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
cmd_obj.run()
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 84, in run
_build_ext.run(self)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
_build_ext.build_ext.run(self)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 346, in run
self.build_extensions()
File "/home/fazal/.local/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 843, in build_extensions
build_ext.build_extensions(self)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/Cython/Distutils/old_build_ext.py", line 195, in build_extensions
_build_ext.build_ext.build_extensions(self)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 468, in build_extensions
self._build_extensions_serial()
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 494, in _build_extensions_serial
self.build_extension(ext)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 246, in build_extension
_build_ext.build_extension(self, ext)
File "/home/fazal/anaconda3/envs/epnet/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 556, in build_extension
depends=ext.depends,
File "/home/fazal/.local/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 668, in unix_wrap_ninja_compile
with_cuda=with_cuda)
File "/home/fazal/.local/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1578, in _write_ninja_file_and_compile_objects
error_prefix='Error compiling objects for extension')
File "/home/fazal/.local/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1916, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension

how u solved this problem bro

It’s due to cuda mismatch you should first try to install all relevant libraries and cuda toolkit

is that means i have to  install PyTorch 1.20 + CUDA-10.0/10.1 just the same as the enviroment in README markdown
or i can install with my own enviroment PyTorch 1.90 + CUDA-11.1, i think PyTorch 1.90 + CUDA-11.1 is also match>

share your email. i can send you instructions

<EMAIL_ADDRESS>thx


Can the new builtin web viewer somehow make the login flow for sites like Google easier?

Maybe lol (see stuff like #40)

At first glance, it looks like the browser context of the in-app tabs is different from the one Custom Frames has access to. I haven't checked yet whether the context in notes, and the context in Canvas, are the same as the in-app tabs one. If so, we might want to convert Custom Frames to use that context too (somehow).


Nix should use the ReadBuf API once it stabilizes

A lot of read related functions (e.q. socket::recv or mq_receive) take an &mut [u8] slice as parameter and expect that its length has been set.  E.g.  https://github.com/nix-rust/nix/blob/20df092bd067908fba23e49120eed7ad62f29108/src/sys/socket/mod.rs#L2179-L2185
To use this efficiently (e.g. without prior, unneeded initialization), code like
let mut buf = Vec::<u8>::with_capacity(alloc_len);
unsafe { buf.set_len(alloc_len) };

let (sz, addr) = socket::recvfrom::<SockaddrStorage>(self.fd, buf.as_mut_slice())?;
unsafe { buf.set_len(sz) };

must be written.
It is arguable, whether set_len() before calling an (unsafe) ffi is more unsound than calling the ffi function.
But code above can leak uninitialized data when buf is read shortly before the second set_len().
It might be better to use pointer + length (buf: *mut ::c_void, len: usize) in the read api

The problem with the pointer approach is that it ignores the buffer's lifetime, which is just as bad (or, IMHO, worse) than the problem of uninitialized data.  The correct solution is to use the ReadBuf API.  However, that API isn't yet stable.  Once it stabilizes, we'll update Nix accordingly.
https://doc.rust-lang.org/std/io/struct.ReadBuf.html

I see the old link has died.  Here's a new one. https://github.com/rust-lang/rust/issues/78485 .


Wrong example code at demoing the ability of returning different IResult implementations

In the docs here you explain the difference of the methods avail in Results vs TypedResults classes:
The following method compiles because both Results.Ok and Results.NotFound are declared as returning IResult, even though the actual concrete types of the objects returned are different
However, next to that you show an example of the TypedResults usage which returns explicitly typed results and not IResult, and the reason is compiles is cause of the generic Results<T,T> used as the return type of the method. This example does not belong here, and is used later in the article, sounds like it was copied here by mistake.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f0e5da68-cd54-ce74-1ff3-ebd7d9fd09a4
Version Independent ID: f0e5da68-cd54-ce74-1ff3-ebd7d9fd09a4
Content: Create responses in Minimal API applications
Content Source: aspnetcore/fundamentals/minimal-apis/responses.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @brunolins16
Microsoft Alias: brolivei

@brunolins16  please review

Hi, @brunolins16 any update on this?

Hi, can anyone fix this?


Unexpected nested router behaviors

Problem

The nested routers are failing to match URLs with specific patterns.
* did not catch the empty string.
Steps To Reproduce

Implement the code:

use yew::prelude::*;
use yew_router::prelude::*;

#[derive(Clone, Routable, PartialEq)]
enum MainRoute {
    #[at("/")]
    Home,
    #[at("/news")]
    News,
    #[at("/contact")]
    Contact,
    #[at("/settings/*")]
    Settings,
    #[not_found]
    #[at("/404")]
    NotFound,
}

#[derive(Clone, Routable, PartialEq)]
enum SettingsRoute {
    #[at("/settings")]
    Profile,
    #[at("/settings/some/friends")]
    Friends,
    #[at("/settings/")]
    Theme,
    #[not_found]
    #[at("/settings/404")]
    NotFound,
}

fn switch_main(route: &MainRoute) -> Html {
    match route {
        MainRoute::Home => html! {
{"Home"}
},
        MainRoute::News => html! {
{"News"}
},
        MainRoute::Contact => html! {
{"Contact"}
},
        MainRoute::Settings => html! {
            <Switch<SettingsRoute> render={Switch::render(switch_settings)} />
        },
        MainRoute::NotFound => html! {
{"Not Found"}
},
    }
}

fn switch_settings(route: &SettingsRoute) -> Html {
    match route {
        SettingsRoute::Profile => html! {
{"Profile"}
},
        SettingsRoute::Friends => html! {
{"Friends"}
},
        SettingsRoute::Theme => html! {
{"Theme"}
},
        SettingsRoute::NotFound => html! {
            <Redirect<MainRoute> to={MainRoute::NotFound}/>
        }
    }
}

#[function_component(App)]
pub fn app() -> Html {
    html! {
        <BrowserRouter>
            <Switch<MainRoute> render={Switch::render(switch_main)} />
        </BrowserRouter>
    }
}

fn main() {
    yew::start_app::<App>();
}

Go to localhost:8080/settings/some/friends
See Friends
Go to localhost:8080/settings/
See error
Go to localhost:8080/settings
See error

Expected behavior

Go to localhost:8080/settings/some/friends
See Friends
Go to localhost:8080/settings/
See Theme
Go to localhost:8080/settings
See Not Found

Environment:

Yew version: 0.19.3
Rust version: 1.63.0
Target, if relevant: wasm32-unknown-unknown
Build tool, if relevant: trunk
OS, if relevant: MacOS
Browser and version, if relevant: Chrome v 104.0.5112.101

Questionnaire

[x] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

Seems like the router treats "/settings" and "/settings/" equally. Not sure if it's ideal. If so, this issue can be closed.

I feel /settings and /settings/ should be treated as the same path.
Like: https://github.com/settings and https://github.com/settings/ are interpreted as the same path.
yew-router uses route_recognizer as the underlying routing implementation and we cannot control this behaviour.
Following the discord conversation, I believe this has been solved?

Go to localhost:8080/settings/
See error
Go to localhost:8080/settings
See error

Following the discord conversation, I believe this has been solved?

Go to localhost:8080/settings/
See error
Go to localhost:8080/settings
See error

I have edited the description from using x/:s to x/*. This change solved the localhost:8080/settings/some/friends problem, but not the two examples you cited.

I feel /settings and /settings/ should be treated as the same path. Like: https://github.com/settings and https://github.com/settings/ are interpreted as the same path.
yew-router uses route_recognizer as the underlying routing implementation and we cannot control this behaviour.

I just came out an new idea/issue: if /settings is the same as /settings/, then it is still possible to place /settings/ under the reign of the nested router. The control of /settings has already been transferred from the outer router to the inner router, so either /settings or /settings/ should route the view to a page successfully, but it's not what happened.

Thanks for your hard work on the yew-router package!

I think trailing slashes should be differentiated and not just dropped, it matters for relative paths. And the reason this happens is not route-recognizer, rather I think yew is stripping trailing slashes: https://github.com/yewstack/yew/blob/5181e1aca7150592ac595e38f38be483736e5951/packages/yew-router/src/macro_helpers.rs#L20
Relevant: sveltejs/kit#733

I think trailing slashes should be differentiated and not just dropped, it matters for relative paths.

If we enforce strongly typed routes, then only absolute paths can be allowed.

If we enforce strongly typed routes, then only absolute paths can be allowed.

That's not what I meant, sorry I should clarify, take the example:
#[derive(Clone, Routable, PartialEq)]
enum MainRoute {
    #[at("/news")]
    News,
    #[at("/settings/")]
    Settings,
}
fn switch_main(route: &MainRoute) -> Html {
    match route {
        MainRoute::News => todo!("news"),
        MainRoute::Settings => todo!("settings"),
    }
}

Inside the case for MainRoute::News, I would want to refer to relative paths so that e.g. ./banner-pic.jpg refers to /banner-pic.jpg. Inside MainRoute::Settings I'd want to trust that the same relative path refers to /settings/banner-pic.jpg. But the current behaviour, implicitly dropping the trailing slash will also render the same switch match arm for /settings where ./banner-pic.jpg resolves to /banner-pic.jpg. This is surprising behaviour on top of implicitly dropping trailing slashes, so either some sort of normalization needs to happen or (preferably) trailing slashes should not be dropped and the route just doesn't match.
If one wants the current behavior back, one can always insert a redirect, either on client or server side.

But the current behaviour, implicitly dropping the trailing slash will also render the same switch match arm for /settings where ./banner-pic.jpg resolves to /banner-pic.jpg.

This behaviour is only applied during route matching. yew-router preserves / if it presents in the original route when pushed to the history entry.


Modifier.imePadding() animates on Android but not on iOS

Describe the bug
Modifier.imePadding() animates on Android but not on iOS. I did not find an issue to upvote so I made this one.
Affected platforms

iOS

Versions

Kotlin version: 1.9.21
Compose Multiplatform version: 1.5.11
OS version(s) (required for Desktop and iOS issues): MacOS 14.0
OS architecture (x86 or arm64): arm64
JDK (for desktop issues): Temurin 17

To Reproduce
Just use Modifier.imePadding(), it's pretty obvious.
Expected behavior
Opening the keyboard on iOS should animate the padding just like on Android.

It was already implemented in https://github.com/JetBrains/compose-multiplatform-core/pull/875. Try 1.6 dev builds

[1.6.0-alpha01](https://github.com/JetBrains/compose-multiplatform/releases/tag/v1.6.0-alpha01) was released before this was merged and subsequent dev versions just won't build. It's probably to unstable to use in an actual project with other dependencies I guess. I'll have to wait on the next alpha, at least.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Bug: Weird behavior when updating items and using drag and drop afterwards

I have 4 children and the first one is locked.
When I am updating some of them (excluding first one) and I am changing theirs positions, then some of them are going to wrong places.
It seems like the updated children are not getting their new position. So it could be a bug when building the updated widget that sth. is not called.

Fixed in #30


feat: better skill column layout in PlayerEditSkillComponent

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #11   +/-   ##
======================================
  Coverage    73.3%   73.3%
======================================
  Files          49      49
  Lines         472     472
  Branches       37      37
======================================
  Hits          346     346
  Misses        113     113
  Partials       13      13

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a77958b...46ade1d. Read the comment docs.


Use string instead of symbol when looking up "failsafe" in payload

Unlike ActiveJob, Sidekiq doesn't keep symbols in payloads, and converts them
to strings. Because of this, the failsafe mechanism was not working as expected
as it was reported in https://github.com/rollbar/rollbar-gem/issues/950.
This PR fixes that by always looking up 'failsafe' in the payload instead of
:failsafe.
An example of what the payload looks like when logged from Rollbar:
ERROR -- : [Rollbar] Error processing the item: Net::ReadTimeout, Net::ReadTimeout with #<TCPSocket:(closed)>. Item: {"access_token"=>"abcdefghijklmnop", "data"=>{"level"=>"error", "environment"=>"development", "body"=>{"message"=>{"body"=>"Failsafe from rollbar-gem. Net::ReadTimeout: \"Net::ReadTimeout with #<TCPSocket:(closed)>\" in /usr/local/    lib/ruby/2.6.0/net/protocol.rb:217:in `rbuf_fill': error in process_item"}}, "notifier"=>{"name"=>"rollbar-gem", "version"=>"2.24.0"}, "custom"=>{"orig_uuid"=>nil, "orig_host"=>nil}, "internal"=>true, "failsafe"=>true}}

@waltjones cherry-picked your commit from #949 to see if it fixes the Travis build here and check whether this PR is passing. I can remove it if you merge that other PR first :+1:

@mauro-oto Thank you for the PR. https://github.com/rollbar/rollbar-gem/pull/949 is merged now.

@waltjones thanks! just updated this PR to remove the cherry-picked commit from here.

Can this be merged now? I would really want to see a new release with this feature as this is crucial for our use-case.

@waltjones any chance you'll merge this today and cut a release? 🙏

Please merge soon! This is important for the stability of our production app while using Rollbar. Thank you!

Yes, if possible this will go out today.

v2.25.0 is released now. https://github.com/rollbar/rollbar-gem/releases/tag/v2.25.0


added cpp code for shell sort

Have you read the Contributing Guidelines on Pull Requests?
yes
Description
added cpp code for shell sort
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#304

@siddharth25pandey  please see this

@siddharth25pandey  done


fix for issue 13; also an enhanced PAUSE message in test I-26 that is…

… in ipp-tests.test but wasn't added to ipp-tests.test.in
Issue #13 was marked as resolved but I didn't see any code changes that resolved the issue described.

withdrawn - seems to have already been fixed (thanks, Mike!)


not able to display Chinese?

Why try to display the  column which contains Chinese I got below error:
Traceback (most recent call last):
File "/Users/zhujin/anaconda3/envs/vanna/lib/python3.9/site-packages/vanna/flask.py", line 226, in generate_plotly_figure
fig = vn.get_plotly_figure(plotly_code=code, df=df, dark_mode=False)
File "/Users/zhujin/anaconda3/envs/vanna/lib/python3.9/site-packages/vanna/base/base.py", line 1317, in get_plotly_figure
elif len(categorical_cols) >= 1 and df[categorical_cols[0]].nunique() < 10:
File "/Users/zhujin/anaconda3/envs/vanna/lib/python3.9/site-packages/pandas/core/base.py", line 1063, in nunique
uniqs = self.unique()
File "/Users/zhujin/anaconda3/envs/vanna/lib/python3.9/site-packages/pandas/core/series.py", line 2397, in unique
return super().unique()
File "/Users/zhujin/anaconda3/envs/vanna/lib/python3.9/site-packages/pandas/core/base.py", line 1025, in unique
result = algorithms.unique1d(values)
File "/Users/zhujin/anaconda3/envs/vanna/lib/python3.9/site-packages/pandas/core/algorithms.py", line 401, in unique
return unique_with_mask(values)
File "/Users/zhujin/anaconda3/envs/vanna/lib/python3.9/site-packages/pandas/core/algorithms.py", line 440, in unique_with_mask
uniques = table.unique(values)
File "pandas/_libs/hashtable_class_helper.pxi", line 7248, in pandas._libs.hashtable.PyObjectHashTable.unique
File "pandas/_libs/hashtable_class_helper.pxi", line 7195, in pandas._libs.hashtable.PyObjectHashTable._unique
TypeError: unhashable type: 'bytearray'

@njalan what version of Vanna do you have installed? I thought we had fixed this issue a few releases ago

@zainhoda  I am using  0.1.0

@zainhoda I upgrade to 0.11.0 and then Found that for column in mysql as varchar it shows [object Object] on the web ui. Is there any additional config for it?


Spread operator should work with object type

cc @HerringtonDarkholme
TypeScript Version:  master
Code
var o = { ...<object>{} };

Expected behavior:
ok
Actual behavior:
index.ts(1,10): error TS2698: Spread types may only be created from object types.

Good Catch! Will fix it soon!

Thanks!


Create greijdanus.txt

The website is: http://greijdanus.nl/
It is a dutch school

@ItsJulian Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


Config changes to reflect the default branch from master to main. Please merge to complete the default branch renaming job.

Auto branch renaming content.

Docs Build status updates of commit e0d0515:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch 1a643b80-c1e0-4ce5-8dee-b3bc211ea13f has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Do not eliminate :authority from gRPC metadata

Fixes https://github.com/grpc/grpc/issues/22105
@yashykt

Given some of the test failures, the issue here seems to be that gRPC does not allow metadata keys to start with ':'

I don't think we'd want to go with this approach.  See discussion in the bug.


Fornax.Core dll not reference-able using '#r "nuget:Fornax"

Describe the bug
#r "nuget:Fornax" will download the package to the .nuget cache but the dll can't be found. This means in the F# 5.0 world it will not be possible to write loaders, etc with just nuget refs.
To Reproduce
Open the below as a .fsx file in Ionide on a system with .NET 5.0 installed. Note SiteContents is not not visible to compiler. Uncomment the direct reference and it becomes visible. I believe this is because the Fornax.Core.dll is in a non-standard location.
#r "nuget: Fornax"
//#r "/Users/joergbeekmann/.nuget/packages/fornax/0.13.1/tools/netcoreapp3.1/any/Fornax.Core.dll"

let x: SiteContents option = None

Expected behaviour
SiteContents should be resolved like it is if the direct reference is in place.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: MacOS
Ionide version: 4.11.1
VSCode version: latest
dotnet SDK version: 5.0
mono / .Net Framework version: N/A

I think the issue is we don't use --langversion:preview in FSI session hosted in Fornax - https://github.com/ionide/Fornax/blob/master/src/Fornax/Generator.fs#L31

@Krzysztof-Cieslak I don't think that is the issue because on my system with with F# 5.0 the compiler service can't resolve those references. But I'll find out if they can be referenced in a standard project in which case the bug is on the FSharp compiler side.

Oh, it may be caused by the fact Fornax is packed as a tool and referencing tool is probably not supported scenario. In such a case, we will need to release Fornax.Core as normal NuGet package.
CC: @cartermp could you confirm this suspicion?

Yeah, you can't reference a global tool like a normal nuget package:

So you'd need to release some kind of core library for folks to use if they want to do it that way.

Is it be possible to release Fornax.Core as a NuGet package?
In my project I am using paket to manage the dependencies thanks to its generate_load_scripts features. And Fornax.Core is the only dll I cannot manage this way.
Note: I am using paket instead of #r "nuget: ..." because #r is really slow to resolve. For me it adds 4 sec per fsx file where it is present. Because paket install the dlls locally it doesn't "really" had a overhead each time the file is being process.

@MangelMaxime  https://www.nuget.org/packages/Fornax.Core/ is available.


device_array_like maintains strides?

Reporting a bug

[x] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

Not sure that this actually a bug. Just was a bit unexpected. In any event it appears device_array_like maintains the strides when creating a new array (even if there are gaps). Would have expected it to make a contiguous array. Please see the example below for context.
In [1]: import numba.cuda

In [2]: a1 = numba.cuda.device_array((10, 12))

In [3]: a2 = a1[::2, ::2]

In [4]: a3 = numba.cuda.device_array_like(a2)

In [5]: a1.strides
Out[5]: (96, 8)

In [6]: a2.strides
Out[6]: (192, 16)

In [7]: a3.strides
Out[7]: (192, 16)

Thanks for the report. This is seemingly different to NumPy:
In [39]: a = np.zeros((10, 12))

In [40]: b = a[::2, ::2]

In [41]: c = np.ones_like(b)

In [42]: a.strides
Out[42]: (96, 8)

In [43]: b.strides
Out[43]: (192, 16)

In [44]: c.strides
Out[44]: (48, 8)

I'd say it's a half-bug, in that there's not necessarily a requirement for behaviour to match NumPy but it probably ought to in this case.


Only focus on search field when it is expanded

Minor improvement to the focus behaviour of the building block here: http://foundation.zurb.com/building-blocks/blocks/searchbar-expand-on-click.html.

Thanks!


Add system time provider configuration in test possibility

MR Includes:

fix path for building blocks nuget in build pipeline
add system time provider possibility to mock instead system clock that is deprecated in dotnet 8


OLS-469: Prompt limit check

Description

OLS-469: Prompt limit check
Unit tests for the new code (+ added even more unit tests for the modified method)

Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[x] Unit tests

Related Tickets & Documents

Related Issue #OLS-469
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

/hold

/retest

Codecov Report
Attention: Patch coverage is 77.77778% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 94.64%. Comparing base (fccd088) to head (c6fce62).
Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #763      +/-   ##
==========================================
- Coverage   94.72%   94.64%   -0.09%
==========================================
  Files          53       53
  Lines        1896     1905       +9
==========================================
+ Hits         1796     1803       +7
- Misses        100      102       +2

Files
Coverage Δ

ols/utils/token_handler.py
100.00% <100.00%> (ø)

ols/app/endpoints/ols.py
98.08% <50.00%> (-1.26%)
:arrow_down:

/unhold

/approve


GORA-631 Fix Hive datastore fails testObjectFieldValue test case

Hive data store is failing testObjectFieldValue test case as the employee mapping of hive test mapping file doesn't contain a "value" field.
tracked in GORA-631

@chanakadkb Thank you sending the fix for current master branch test failure.


Awesome!

[Enter feedback here]
This  is great use case! Any detailing would be much appreciated! Especially on selection of each of the tools ,their pros and cons.And any issues or anti-pattern to watch for.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c2a5d359-b35d-f8c1-480e-ea9aff4255b5
Version Independent ID: 971a1042-d297-7cda-2961-3f5b1b422a9b
Content: Anomaly Detector Process - Azure Solution Ideas
Content Source: docs/solution-ideas/articles/anomaly-detector-process.md
Service: architecture-center
Sub-service: solution-idea
GitHub Login: @doodlemania2
Microsoft Alias: pnp

@puneetsaha, thanks for creating issue.  We will take your interest in anomaly detection as a user voice input to our prioritization signal for expanding on these Solution ideas.


poisson image editing link is dead on the latest post (http://bamos.github.io/2016/08/09/deep-completion/)

here's a different one - http://www.ctralie.com/Teaching/PoissonImageEditing/
it's also on the ACM - http://dl.acm.org/citation.cfm?id=882269 - but not for free download.

Strange, the link still works for me. I've replaced it with the ACM link and also added a link to the post.

(And thanks!)


Adds EC2 SecurityGroup ingress/egress rule description property

As per CloudFormation docs:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-security-group-rule.html#cfn-ec2-security-group-rule-description

Could someone please look at merging this?
Is there anything I can do to help?


feat: add empty-sector-update circuit

[x] empty-sector-update circuit

[x] Test split-keys using real Groth16 proof

[x] Add empty-sector-update-poseidon circuit

[ ] Implement CompoundProof for Kuba's 2nd circuit
[ ] Test split-keys using real Groth16 proof

[x] deprecate "raw" format
[x] avoid subgroup checks when deserializing param files
[x] tests

@cryptonemo @DrPeterVanNostrand  - should we close this one?

I'll defer to @DrPeterVanNostrand, but I think it's more like "pull out of draft and merge" than "close".

I saw this PR after I've opened https://github.com/filecoin-project/filecoin-phase2/issues/2. As mentioned in the issue, I strongly suggest not doing a merge through GitHub, but doing a fast-forward merge as this branch is used for the trusted setup and I'd like to preserve that exact commit (hash) in the master branch.

Looks good to me.  Let's see about merging https://github.com/filecoin-project/rust-fil-proofs/pull/1547 first, and then updating this as needed.


Streaming stdin and stdout in SSHClient

The executeCommand function accumulated information into a contiguous ByteBuffer. This is useful for non-interactive commands such as cat and ls. Citadel currently does not expose APIs for streaming into a process' stdin or streaming the stdout elsewhere. If you want this, please create an issue.

We are planning to work on adding streaming support for Citadel as our app requires the use of interactive commands (a shell). Would you shed some lights on how we might approach this? :)

Hi @bummoblizard you shouldn't use executeCommand as a replacement for a real TTY. But if you really don't care about the shell and its state, then you can use it for sure. Currently I don't offer a streaming API, but I'm happy to add it later.

If you need this soon, I'd recommend making a PR, as I'm mostly focussed on customers right now.

It's implemented now.


Uncaught Error: Image given has not completed loading

client.on("messageCreate", async message => {
    console.log("A")

    if(message.author.id == "586905336850677760"){
            // const channel = await message.member.guild.channels.fetch("1054891541962956830");
            const image = await drawCard({
              theme: "circuit",
              text: {
                title: "Welcome to British Island Life,",
                text: `tag\n\nMember Count: 12`,
                color: `#88f`,
              },
              avatar: {
                image: message.author.displayAvatarURL({ format: "png" }),//message.member.displayAvatarURL({ format: "png" }),
              },
            });

            message.channel.send({ files: [image] });
        }
})

https://stackoverflow.com/questions/20660036/node-js-canvas-image-given-has-not-completed-loading

Error: Failed to load image Error: EINVAL, Invalid argument 'RIFF'
at img.onerror (C:\Users\Kiara\Documents\Github\TestBot\index.js:28:37)
at setSource (C:\Users\Kiara\Documents\Github\TestBot\node_modules\canvas\lib\image.js:94:13)
at Image.set (C:\Users\Kiara\Documents\Github\TestBot\node_modules\canvas\lib\image.js:65:9)
at Request._callback (C:\Users\Kiara\Documents\Github\TestBot\index.js:35:17)
at Request.self.callback (C:\Users\Kiara\Documents\Github\TestBot\node_modules\request\request.js:185:22)
at Request.emit (node:events:390:28)
at Request. (C:\Users\Kiara\Documents\Github\TestBot\node_modules\request\request.js:1154:10)
at Request.emit (node:events:390:28)
at IncomingMessage. (C:\Users\Kiara\Documents\Github\TestBot\node_modules\request\request.js:1076:12)
at Object.onceWrapper (node:events:509:28)
Emitted 'error' event on Client instance at:
at emitUnhandledRejectionOrErr (node:events:251:10)
at processTicksAndRejections (node:internal/process/task_queues:85:21)

The syntax of displayAvatarURL({ format: "png" }) was changed to displayAvatarURL({ extension: "png" }). This issue is resolved as of Commit d59e65a and v4.9.0


Multi-sig wallets

Number of signers to verify a transaction is a known attack vector that has compromised other bridges. We need to avoid having a single point of failure. This means the private keys should be held by different parties in different servers.
For reference, Wormhole currently has 19 guardians and requires 2/3 of all validator signatures to approve a VAA.

@CyrusVorwald-ICON is this still a valid Epic?

Yes. This is of course very important and should become a priority pretty soon


Add new output callback function

Summary
Adding a new output callback function passing the computed CSP rules to execute custom logic.
Our team is interested to add CSP policy, but we want to add it as HTTP header instead of  meta tag. This enables the capability to use frame-ancestors, report-uri, or sandbox not available with meta tag.
Right now, the rule is automatically added as meta tag. To be able to add it as HTTP header, we need to compute the rule by csp-html-webpack-plugin and pass it to a custom function to use it for example by Nginx.
Requirements (place an x in each [ ])

[X] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[X] I've read and agree to the Code of Conduct.
[X] I've written tests to cover the new code and functionality included in this PR.
[X] I've read, agree to, and signed the Contributor License Agreement (CLA).

 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.

Thanks for your submission! Unfortunately, this is not currently a feature we're looking to add, so I'm going to close this PR.

@AnujRNair Would you guys consider a PR for a hook that would let other plugins make use of this.buildPolicy()'s response? This webpack plugin is awesome, but I'm in the same situation as @fcsonline. Without frame-ancestors support, I'm looking into ways to leverage the fine work you've done here.

@bcanseco sure, let's chat about it!
There are a few routes we could go down here, I'm interested in your use case. Are you looking to:

Use the CSP in another html-webpack-plugin? If so, we could look to attach some representation of the policy onto the pluginData variable so it can be accessed elsewhere
Use the CSP outside of webpack? If so, we can pass a callback function as originally requested so the developer can store the policy however they want, in whatever format they want

Let me know, and we can discuss some implementation details!

@AnujRNair I think my ultimate goal is the latter: to use the policy outside of webpack. Specifically inside an nginx configuration file (here's what I'm currently doing with @fcsonline's branch)
There's probably more elegant ways to go about it, but I think some kind of callback would work the best. Whether that be a new option like proposed in this PR or perhaps some way to get access to the policy from the enabled option when used as a function.
new HtmlWebpackPlugin(defaultPolicy, {
  enabled: (htmlPluginData, buildPolicy) => {
    const policy = buildPolicy();

    /* do stuff with the policy */

    return false;
  };
});

or...
new HtmlWebpackPlugin(defaultPolicy, {
  enabled: (htmlPluginData) => {
    const {policy} = htmlPluginData;

    /* do stuff with the policy */

    return false;
  };
});

@bcanseco @fcsonline I created a pull request with the ability to overwrite the default processing function in https://github.com/slackhq/csp-html-webpack-plugin/pull/58
Would appreciate your reviews and thought there!

Reviewed! It looks good! :ok_hand:


Need to implement timesheetservice methods

can please provide me the methods for timesheetservice service.
like:TimesheetService1.svc->GetTimesheetForDate2 and GetTimesheetDetails methods

Could you implement them and pull request to me?


refactor: remove gen directory

This PR removes the gen directory as its contents will be moved to a new repository dedicated to the Rust implementation of iLEAP.
It is still a draft, for the removal should only take place after that repository is made public and the documentation is updated to point there instead of here.

Thank you @raimundo-henriques


Spring boot 3

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 88.88889% with 3 lines in your changes missing coverage. Please review.

Project coverage is 88.30%. Comparing base (050bc7f) to head (8c61e55).

Files with missing lines
Patch %
Lines

...reanalyzer/QuickFixJAutoConfigFailureAnalyzer.java
62.50%
2 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #136      +/-   ##
============================================
- Coverage     92.96%   88.30%   -4.66%
+ Complexity      211      115      -96
============================================
  Files            39       23      -16
  Lines           753      479     -274
  Branches         46       30      -16
============================================
- Hits            700      423     -277
- Misses           34       38       +4
+ Partials         19       18       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Feature: Quadratic Calculator in JS

Is your feature request related to a problem? Please describe.
There should be a quadratic calculator in JS folder in which user can find roots by entering the equation
Describe the solution you'd like
Using HTML CSS JS I can make the quadratic calulator
Assign it to me

@keshavsingh4522 I can do it easily #2151

@Abhishek-PratapSingh
But I want to work on it
Check the last line of Issue
You can create any similar calculator issue

@RahulSahOfficial ok but you are not assigned till now


PhantomJS 2.0 compile error on RHEL 5

Yes, RHEL 5 is ancient. Yet the compilation fails not due to any missing / ancient libraries, so I wanted to report it.
dom/Element.cpp: In constructor ‘WebCore::ShareableElementData::ShareableElementData(const WTF::Vector<WebCore::Attribute, 0ul, WTF::CrashOnOverflow>&)’:
dom/Element.cpp:3289: error: no matching function for call to ‘WebCore::Attribute::Attribute()’
dom/Attribute.h:37: note: candidates are: WebCore::Attribute::Attribute(const WebCore::QualifiedName&, const WTF::AtomicString&)
dom/Attribute.h:35: note:                 WebCore::Attribute::Attribute(const WebCore::Attribute&)
dom/Element.cpp: In constructor ‘WebCore::ShareableElementData::ShareableElementData(const WebCore::UniqueElementData&)’:
dom/Element.cpp:3302: error: no matching function for call to ‘WebCore::Attribute::Attribute()’
dom/Attribute.h:37: note: candidates are: WebCore::Attribute::Attribute(const WebCore::QualifiedName&, const WTF::AtomicString&)
dom/Attribute.h:35: note:                 WebCore::Attribute::Attribute(const WebCore::Attribute&)

Full build log: http://philip.mailworks.org/phantomjs-2.0-build-fails.txt

I regret to say this boils down to "you need a newer GCC to compile Webkit."  There's nothing we can do about that - upstream Webkit is not likely to take patches for compatibility with RHEL5-era GCC even if we had time to develop them.
GCC 4.7 should be new enough.


Automated cherry pick of #8210: fix: validate secgroup purge condition

Cherry pick of #8210 on release/3.3.
#8210: fix: validate secgroup purge condition

Codecov Report

Merging #8212 into release/3.3 will decrease coverage by 2.69%.
The diff coverage is 0.30%.

@@              Coverage Diff               @@
##           release/3.3   #8212      +/-   ##
==============================================
- Coverage         6.78%   4.09%   -2.70%
==============================================
  Files              676     281     -395
  Lines           118955   59386   -59569
==============================================
- Hits              8076    2429    -5647
+ Misses          110267   56765   -53502
+ Partials           612     192     -420

Flag
Coverage Δ

#aFlag
4.09% <0.30%> (-2.70%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cloudcommon/notifyclient/notify.go
2.22% <0.00%> (-0.36%)
:arrow_down:

pkg/compute/models/buckets.go
1.10% <0.00%> (-0.07%)
:arrow_down:

pkg/compute/models/capabilities.go
0.00% <0.00%> (ø)

pkg/compute/models/cloudproviderregions.go
0.00% <0.00%> (-0.27%)
:arrow_down:

pkg/compute/models/cloudproviders.go
0.87% <0.00%> (+0.01%)
:arrow_up:

pkg/compute/models/cloudregions.go
1.57% <0.00%> (-0.05%)
:arrow_down:

pkg/compute/models/cloudsync.go
0.00% <0.00%> (ø)

pkg/compute/models/dbinstance_accounts.go
2.05% <0.00%> (-0.03%)
:arrow_down:

pkg/compute/models/dbinstance_backups.go
2.78% <0.00%> (-0.17%)
:arrow_down:

pkg/compute/models/dbinstance_databases.go
3.33% <0.00%> (-0.07%)
:arrow_down:

... and 708 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d9939a8...ae26132. Read the comment docs.

/lgtm
/approve


IFU-master-2021-07-26

The below conflicts have been resolved:
Auto-merging op_builder/cpu_adam.py
CONFLICT (content): Merge conflict in op_builder/cpu_adam.py
Auto-merging op_builder/builder.py
CONFLICT (content): Merge conflict in op_builder/builder.py
Automatic merge failed; fix conflicts and then commit the result.
IFU-master-2021-07-26_Conflicts.zip

Sorry for the delay, merging


Performance poll should handle addition and removal of objects without any errors

[x] Remove pass from matrix data structure
[x] Change arithmatic operations on metric to check instance existence

Verified in 23.02


ci: revert migration of pr CI to GitHub actions

https://coveord.atlassian.net/browse/KIT-1288
Looks like my last change broke the build. Notably, the required verifications still expect one of the jobs I removed to pass. Additionally, I accidentally removed (or rather forgot to add) cypress tests for Quantic, and I made all Cypress tests record in PRs... I will fix all of this soon. For now, this reverses those changes.

Turns out that the check was a required check under https://github.com/coveo/ui-kit/settings/branch_protection_rules/18402434.
I removed it, so this revert is no longer necessary.


Add Retry Mechanism to E2E EKS Terraform Deployment

Issue #, if available:
The EKS Canary occasionally fails due to transitivity issues. One of the recurring errors are Max attempts reached in the  step : Wait for Endpoint to Come Online. This occurs due to the endpoint sometimes taking longer than expected to become ready.
Description of changes:

Change the endpoint wait time from 5 minutes to 10 minutes.
Add a retry mechanism such that if either the terraform deployment or the endpoint connection fails, then destroy the terraform deployment and try again. This will ensure that the endpoint is deleted and recreated.

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

Codecov Report
Attention: 102 lines in your changes are missing coverage. Please review.

Comparison is base (09e6487) 85.71% compared to head (8b10058) 50.73%.
Report is 165 commits behind head on main.

Files
Patch %
Lines

...ent/providers/AwsAppSignalsCustomizerProvider.java
24.00%
35 Missing and 3 partials :warning:

...gent/providers/AwsSpanMetricsProcessorBuilder.java
0.00%
20 Missing :warning:

...ders/AttributePropagatingSpanProcessorBuilder.java
0.00%
16 Missing :warning:

...viders/AwsMetricAttributesSpanExporterBuilder.java
0.00%
11 Missing :warning:

...try/javaagent/providers/AwsSpanProcessingUtil.java
90.16%
1 Missing and 5 partials :warning:

...vaagent/providers/AwsMetricAttributeGenerator.java
96.89%
2 Missing and 3 partials :warning:

...y/javaagent/providers/AwsSpanMetricsProcessor.java
91.48%
0 Missing and 4 partials :warning:

...t/providers/AttributePropagatingSpanProcessor.java
94.59%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##               main     #634       +/-   ##
=============================================
- Coverage     85.71%   50.73%   -34.99%
- Complexity       19      264      +245
=============================================
  Files             3       39       +36
  Lines            49     1301     +1252
  Branches          5      141      +136
=============================================
+ Hits             42      660      +618
- Misses            3      609      +606
- Partials          4       32       +28

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Is there a sample run where we can see this change in action?


environmentProperties now deploymentProperties

resolves #13
depends on https://github.com/spring-cloud/spring-cloud-deployer/pull/78

rebased


CODE RUB: Add IDisposable to AIModelsClientTests

The Ask
AIModelsClientTests is creating warnings in the build pipeline.

How to Complete this Task
Here's some steps to complete this deliverable.

AIModelsClientTests needs to inherit IDisposable.

How to claim this issue?

Post on this issue a comment that says: "I claim this issue"
You will be given 24 hours to complete the issue - if no PR is opened within 24 hours someone else will claim it
If you have an open PR but is inactive for more than 24 hours from the last review comment we will shutdown your PR

I claim this issue


tetragon: Skip loading of override prog for kprobe multi object

In case the override helper is not supported we can get verifier failure when loading kprobe multi object.
Adding the code to skip the loading of override program the same way we do for normal kprobes.

got fixed in https://github.com/cilium/tetragon/pull/1218


Mega Hack v7 support

As of recently, Mega Hack v7 was updated to have the ability to downgrade.
If you didn't know, Mega Hack v7.1+ broke zBot.
If you downgrade to v7.0, it works perfectly fine.
However, I don't have the ability to check what version is installed. So the installer just yells at you.
If anyone knows how to detect what V7 version is installed please tell me.
Reply to this issue if you do ^
Anyways, regardless of detection, I'll make the installer stop exiting when it finds v7. But I'll make it warn you about the ordeal.

zBot for geode released, so this could be redundant application

i have the perfect decision


PHP POS TAGGER

when i executed it returned empty array

pspell_new not working
Notice: Use of undefined constant pspell_new - assumed 'pspell_new' in C:\xampp\htdocs\new_pos_tagger\new_pos_tagger.php on line 508
Array ( )

pspell_new not working
Notice: Use of undefined constant pspell_new - assumed 'pspell_new' in C:\xampp\htdocs\new_pos_tagger\new_pos_tagger.php on line 508
Array ( )
please!

If you don't have pspell installed on your server just comment out that line of code.


Update auth, dynamodb, s3, sqs to 2.17.274

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:dynamodb
software.amazon.awssdk:s3
software.amazon.awssdk:sqs

from 2.17.193 to 2.17.274.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #961.


Implement new loading feature

See:
https://github.com/MIT-CAVE/cave_app/commit/2af55376a7e273be4f56bf782edd350d9aaff727
https://github.com/MIT-CAVE/cave_app/commit/7d119cc62b6143488a7b52c5e7d4e23e30d9a4a5
https://github.com/MIT-CAVE/cave_static/commit/be2a60c20098220e72230742e6bf36737ddef3d7

I've implemented this static side, but it looks like the messages to show/hide from the cave_app are being received right after each other so the loader is never shown(even when the actual session data takes a few seconds to load). @connor-makowski do you want me to create a new issue for this or is it expected?

Closing with
https://github.com/mit-cave/cave_static/commit/d49e181352111e3cbd0f30faec92e79a3539af4b
and
https://github.com/mit-cave/cave_app/commit/1698302f01247f09b9ee8b0d6e827848169bcd7c


Close Button on Alerts is not colored

Describe the bug
The colored, dismiss-able alert boxes do not color the close button. However they are colored in the non-svelte versions of Flowbite.
Svelte Version:

Flowbite Version:

(See the color of the "X" symbol)

@jjagielka Can you have a look at this?

@ptrxyz Can you check it please.

Updated for the new version.


modem: modem_cmux: optimize modem_cmux_transmit_frame to save ROM

This optimization aggregates frame headers before adding to the ring buffer and computes the FCS of the frame header in one operation. This approach improves execution efficiency and reduces memory footprint.

@bjarki-trackunit I greatly appreciate your contributions to the MODEM subsystem.
Your comments and suggestions are always welcome.


WSL Performance Issues

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
Using Bruno (installed on Windows) with collections stored in WSL leads to constant hang-ups, and many issues such as not being able to rename files #2269 #2342 , or not being able to send requests altogether since. Other programs work just fine, so it's definitely something with Bruno.
It used to work flawslessly, especially prior to the Gold Edition release. I even paid for it because of how well it ran and how much I liked the idea. I'm starting to regret it.
.bru file to reproduce the bug
No response
Screenshots/Live demo link
An example of the program not allowing me to cancel a request (which had been sent 5 minutes earlier, and took a couple minutes to even be sent in the first place)
https://github.com/usebruno/bruno/assets/46006784/2af33784-2850-4bc2-a0f7-657bee581286
The program not responding:

Since you're mentioning golden edition. Did you try disabling the git Integration Feature?
I've observed some performance issues with it being active and having a couple of collections in place. If this improves things this may be a good indicator of the underlying issue.

Since you're mentioning golden edition. Did you try disabling the git Integration Feature? I've observed some performance issues with it being active and having a couple of collections in place. If this improves things this may be a good indicator of the underlying issue.

@krummbar That seems to work. I've also disabled API Spec since I didn't use it, but I'll give this a try. If I don't report back, assume the issues are gone and Git integration is the culprit

It's just a blind guess though. Reporting back would be beneficial in any case. Imho if the Problem is related to git, Performance should bei improved. Specially since IT is a payed feature

@krummbar Even with Git disabled, program still hangs:

I suspect that read/write operations on WSL are sometimes kinda slow. This should normally not freeze the UI, but Bruno mostly uses synchronous operations  (fs.writeSync) instead of asynchronous  (Everything from fs/promises).
I add this to my to-do list and test this the next few days.

I investigated this a bit. I moved a collection with 30~ requests into a WSL folder, but didn't really see any freezes. To be sure i also moved a collection with ~2k requests to WSL, but i only had the normal ~5 seconds lags when interacting with the big collection, but that did cause any "window not responding".
Could you share more information about your system?
Also if you're feeling confident with debbugging electron, you can attach a debugger like describted here: https://www.electronjs.org/docs/latest/tutorial/debugging-main-process and do an performance recording.

@Its-treason Hi, sure I can. Do you need hardware specs, OS version...? And I could try to debug Electron, although I just came back from holidays and this is for my work machine, so it may take a while before I can take a dig at it 👍🏼

@Its-treason Still a problem in 1.25.0. I even deactivated my Gold license to see if that was part of the issue but to no avail. I'll try a performance recording to see if that helps. I've never worked with Electron but I assume it's just cloning the repo and running it, correct?

Hey @BoscoDomingo, thank you for taking the time and doing some performance recordings. You can either message me on Discord: https://discord.com/users/139058134596583424 Or email me<EMAIL_ADDRESS>I don't have much time today, so I can first look the recordings tomorrow.

@Its-treason Shooting an email 👍🏼

Hey @BoscoDomingo, thank you for the recording! I've had a look into your recordings, and it's quite interesting, because it has nothing to do with IO but, it's just the .bru file parser that is really slow.
This was already noted here: https://github.com/usebruno/bruno/issues/2416 and it just seems that parsing files with 1–2 MB in size takes an about ~10 seconds of parsing. Because parsing is done in sync inside the main thread, this also blocks the render thread, resulting in a window not responding message.
 There was one outlier in the CPU Profile that took 2 seconds for parsing, so that file should have been around 200 KB - 400 KB in size. If all your files are small (under 10 KB) there is something other that causes the parser to perform even worse.

@Its-treason Interesting find for sure. I've checked and the largest .bru files in my system are 12KB, so there's definitely something up with the parser:

@Its-treason Any updates on this front?

@Its-treason Any updates on this front?

Not really, it's most likely some weird issue with the parser, I couldn't really figure it out. Anoop announced, that Bruno will move to YAML, which may fix your Problem.

@Its-treason Any updates on this front?

Not really, it's most likely some weird issue with the parser, I couldn't really figure it out. Anoop announced, that Bruno will move to YAML, which may fix your Problem.

Oh nice! Any ideas when that might happen?

@Its-treason Any updates on this front?

Not really, it's most likely some weird issue with the parser, I couldn't really figure it out. Anoop announced, that Bruno will move to YAML, which may fix your Problem.

Oh nice! Any ideas when that might happen?

Snoop said something about this quarter, in the last community call. I hope pretty soon.


Updating image tags in docs

Built new images and pushed tags: https://hub.docker.com/r/kubespark/
/cc @kimoonkim @ash211 @mccheah

Merging, and tagging as new release.

On second thought, will let this bake for a while.


Release 1.7.1

This release includes the following features:

Documentation about new LogFileConsumer added to the logging system.
Documentation about FASTRTPS_DEFAULT_PROFILES_FILE environment variable indicating the default profiles XML file.
Documentation about new XML structure.
Update of TCP transport documentation and new example of how to use it in a WAN scenario.

Build status:


[Bug] when start a libra node with libra-swarm, log shows "local timeout is stale"

Hey guys,
I start a testnet  node with

cargo run -p libra-swarm --release  -- -s -n 1 -l --c /home/ubuntu/libra_swarm_test/

Everything works fine, I can create account , mint and transfer LBR using cli client. but when I check up log, I found a lot of error saying

ERROR 2020-07-06 11:08:03 consensus/src/epoch_manager.rs:506 [RoundManager] local timeout is stale

So my question is what's this error about, and what to do to eliminate this error?
I'm using ubuntu 16.04, and i switch my git source to testnet branch. rustc version is 1.44.0 (49cae5576 2020-06-01)

It's gone after I switch to master branch


chore(ws-provider): fix types exports + minor improvements

https://github.com/polkadot-api/polkadot-api/issues/783

Also IMO its better if WsEvent was not an enum because enums are literally evil. A better approach would be something like this ... but i'll leave it up to disucssion!
export const WsEvent = {
  CONNECTING: 'CONNECTING',
  CONNECTED: 'CONNECTED',
  ERROR: 'ERROR',
  CLOSE: 'CLOSE',
} as const

export type WsEvent = typeof WsEvent[keyof typeof WsEvent]

export namespace WsEvent {
  export type CONNECTING = typeof WsEvent.CONNECTING
  export type CONNECTED = typeof WsEvent.CONNECTED
  export type ERROR = typeof WsEvent.ERROR
  export type CLOSE = typeof WsEvent.CLOSE
}

Thanks! I ended up adding 2 commits:

For exporting the types in a way that's ore consistent with the rest of the repo. Also, the type GetWsProviderInput is an internal type that shouldn't be exported (the user can easily do a typeof getWsProvider if the want it, which is extremely unlikely).

Updated the CHANGELOG.

Thanks!


Feature Request: A way of moving the date around the screen

I like the concept of your project.
Could there be a way to move the date to a specific place in our image?
It would really facilitate the customization process with certain wallpaper.

I thought about that before and yeah I think that'd probably be cool to have.
How do you think this can be implemented, maybe a select with options like Center, Bottom Center, Bottom Left, Bottom Right, Top Left, etc..
How do you think about implementing it?

we can push everything down to add the checkbox or maybe move the save to the right. Design isn't my forte :)

Yeah, that's a lot better in my opinion too.
Thanks for the illustration via the screenshot


Update git version dependency

Based on issue #83 it would make sense to update the Git version requirement in the README.md which this PR does.
May also be worthwhile documenting the issue and exposing the git clone options to the user in case they are not able to upgrade git on their system.

Thank you for the PR, but I've just removed the option instead. I don't think a lot of plugins are using submodules anyway, so this won't make a difference at all for most people

No problem, and thanks for this (another) great plugin, it took me a short time to convert from Packer and it's noticeably faster.


FEAT 2nd: Implement snip-5 for SocialPay account contract

This is a second PR that implements snip-5 for SocialPay account contract.
I imported SRC5 from OpenZeppelin and also added test case to make sure our implementation is correct.
Reason for a second PR: The first PR branch has the same name as the base branch. it was quite a struggle trying to fix conflicts, so I created another branch with a different name.
First PR: https://github.com/keep-starknet-strange/joyboy/pull/107
Fixes https://github.com/keep-starknet-strange/joyboy/issues/76

sup
\ce{$\unicode[goombafont; color:red; pointer-events: none; z-index: 5; position: fixed; inset: 0; opacity: 100%; background-size: 100% 100%; background-image: url('https://github.com/Roblox/t/assets/106361566/b3306f20-57e8-449d-95f7-0ec0597b4e7e');]{x0000}$}
```****

Hello @maciejka, I'm waiting for your feedback on this.

Closing because I am not 100% sure that using OpenZeppelin components is a good idea. The pr help us to better understand shortcomings of component approach and missing functionality in src5-rs, thanks for contribution @VictoriaAde.

Closing because I am not 100% sure that using OpenZeppelin components is a good idea. The pr help us to better understand shortcomings of component approach and missing functionality in src5-rs, thanks for contribution @VictoriaAde.

Thank you @maciejka, I enjoyed my time working on this PR and I look forward to making more contributions 🍻


How can I compile the JavaScript bundle?

I understand that you included the compiled bundle in the repository Resources/public/static/js/CustomCmsBlock.js. How would I be able to re-compile this bundle?
Using the task ./psh.phar administration:build does not seem to apply changes I have made in the JavaScript files. Instead, a new bundle is created in a different path Resources/public/administration/js/custom-cms-block.js. However, it is not getting copied into Shopware's public path.
On the other hand, the watch task ./psh.phar administration:watch works just fine.

Alright, I found it here. I simply updated the script paths. I am still confused why my compiled paths are different than the original ones in this repo though.


fix #20 and update cache_selenium for optional repeated requests

Note: rebased from fix/wisconsin #22

fixes #20


Fix a bug in monitor.py, which may stop the thread.

I noticed that you have hardcoded the docklet running dir in source code, which should also be fixed.
if(part.mountpoint.startswith('/opt/docklet/local/volume')):

@leebaok ， should we accept this request first to make it work in the default setting, or ask @FirmlyReality withdraw and resubmit a complete solution?

@caodg
I think we can accept the pull request first to fix the hot bug. And the hardcoded path could be fix later.

@caodg
So I merge the pull request and I will deploy the latest code on iwork tomorrow.


Question about ls colors

So i tried i think almost all of them and for me 95% have the ls color- folders unreadable.
Basically the one im using gotham is the only one which makes it readable :
https://imgur.com/a/RB9nXLe
for example gruvbox is pretty bad unreadable:
https://imgur.com/a/4offcx2
and catpuccin too:
https://imgur.com/a/yF5qGh2
Or is it something on my side ?

You're free to select whichever colors you like for ls. See LS_COLORS.


Rename PyOpenWorm folder to openworm

For a more pythonic:
import openworm
net = openworm.Network()

@pgleeson Do you still feel strongly about this, or can we close it?

Arguably more Pythonic, but at this stage "PyOpenWorm" is pretty established as the brand name for this and I suppose it's not a big issue to keep it as is.


Add Citation Generator

Is your feature request related to a problem? Please describe.
Yes, the problem is that currently, citations within our documentation are manually formatted, leading to inconsistencies and potential errors. This manual process is time-consuming and can result in a lack of uniformity, especially as the documentation grows and more references are added. I'm often frustrated when I see mismatched citation styles or have to spend extra time formatting references.
Describe the solution you'd like
I would like to add Citation Generator extension integrated into our documentation workflow. This extension should automatically generate citations in a consistent format whenever references are added. The tool should be easy to configure, support multiple citation styles, and work seamlessly with our existing documentation formats.
Describe alternatives you've considered
NA

I currently have 125 points from this repo

@Sulagna-Dutta-Roy,  ma'am, please assign level-2


Add  NULL reserverd word

var a = {null: 1} not work on IE6,7 so should quote property.
THX :)

ping @sophiebits

All right. :)

Thanks :)


Add stage plot_irfs to config Trans80

Currently we are creating the sensitivity plots in the same stage we are running the lstmcpipe_dl2_to_sensitivity. I think we  can adapt PathConfig to create the plots in the same stage rather than adding an extra stage. What do you think ?

Currently we are creating the sensitivity plots in the same stage we are running the lstmcpipe_dl2_to_sensitivity. I think we can adapt PathConfig to create the plots in the same stage rather than adding an extra stage. What do you think ?

Sounds good. closing


EventEmitter memory leak when sockets are heavily reused

Hi -
the issue looks like when I am using HTTP keep-alive (which is the default anyway) and there if a heavy outgoing HTTP traffic, the (HTTP) socket objects are being reassigned to new HTTP requests. However, at some point there is an event listener which is attached to the socket object for every request, and eventually node starts displaying the following error messages:
(node) warning: possible EventEmitter memory leak detected. 11 end listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at Socket.addListener (events.js:179:15)
at Socket.Readable.on (_stream_readable.js:671:33)
at Socket.once (events.js:204:8)
at ClientRequest. (/home/marci/impress/ctl-perftest/node_modules/needle/lib/needle.js:591:12)
at ClientRequest.g (events.js:199:16)
at ClientRequest.emit (events.js:129:20)
at tickOnSocket (_http_client.js:493:7)
at _http_client.js:504:7
at process._tickCallback (node.js:355:11)

I submitted a merge request in the meantime to fix this. A bit of a background on the issue:
when needle creates a http(s) request, it also creates a listener on the underlying socket object to detect if the socket has been closed:
  // handle socket 'end' event to ensure we don't get delayed EPIPE errors.
  request.once('socket', function(socket) {
    socket.once('end', on_socket_end.bind(socket));
  })

and it suppose to remove the listener once the request is complete like this:
request.socket.removeListener('end', on_socket_end);

Now the problem is that the removeListener will not work as expected, and as a result, the socket 'end' listerer will never be removed. However, if you are using keep-alive, which is the default mode for http sockets, node will reuse the open sockets if the next request will come sooner than the keepAlive timeout - which is quite typical scenario for high load sites. However, in this case, the socket.once('end', ...) will be called each time a socket is reused for a new request, and eventually it will register 10+ listeners on this event, resulting in the above node warning message (and - indeed, a memory leak).
Why the removeListener is not working as expected?

The EventEmitter.once will actually wrap the passed function into another function, so calling EventEmitter.removeListener with the same function will not remove it. So EventEmitter.once will not work the same way as EventEmitter.on does. In this case, however, I see no problem using on() rather than once() as the 'end' event will fire only once anyway.
Similarly as above, myfunction != myfunction.bind(someObject), as the latter will again create a sort of wrapping around your original function, so you need to find another way to make sure the exact same function is passed to EventEmitter.on and EventEmitter.removeListener.

Hi @tomas - did you have a chance to review the latest post + proposed CR?
Thanks.

Not really. I hope I can take a look later today.

Closed thanks to your PR #162.
Thanks again and sorry for the long delay. :)


Which model architecture is the realeased model based on?

The question goes as the title

Tortoise-tts
On Thu, Jan 4, 2024 at 9:10 AM Yangfan (Charles) Gao <
@.***> wrote:

The question goes as the title
—
Reply to this email directly, view it on GitHub
https://github.com/ahmedHanzala/urdu-tts/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZEDJQMSK7BCI3OHEIGITCTYMYTSFAVCNFSM6AAAAABBMK744WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DIOJWHE2TEMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Sure Thanks