Resolving scalar in nested type does not work

I am using graphq-tools to create an executable schema and then I am mocking the schema whilst preserving the resolver.
However when I try to run a query for a Date in a nested type the schema gives an error.
  scalar Date

  type Test {
    start: Date!
  }

  type Query {
  	test: Test
	test2: Date
  }

this is the schema. If I query test2 then it works fine. However, when I query test { start } I get an error stating "this is not a Date object.". Please refer to the launchpad that reproduces this issue.
Thanks in advance.

Thanks @excitement-engineer! I think the problem here has to do with preserveResolvers. In your case, there are resolvers for every field, so providing mocks while preserving resolvers should end up not using any mocks at all.
If you either set preserveResolvers to false, or you remove the resolver for that field, it works fine. I'm not 10% sure why things break, but I suspect it's because the mocks don't end up returning what the resolve function returns, but they return a function or an object instead, which is a problem if you expect it to be a scalar of type date.
I don't think it has anything to do with the nesting at all, rather it's an issue when preserveResolvers is used together with a scalar.

Thanks for the quick reply @helfer. I ran into this bug when building a larger schema where only a subset of the resolvers were implemented and the rest are mocked. So in this case setting preserveResolvers to false is not an option as it would mean the entire API returns mocked data.
It seems that if I remove the mock for Date in the addMockFunctionsToSchema then the root query test2 works but the nested type doesn't. I don't really understand why the root query does work and the nested doesn't. I have updated the launchpad accordingly. I'm not sure how the internals of mocking works but it does seem that it is returning an object or function or something and this is causing the implemented resolver to fail like you said.

Fixed in #355. Thank you @excitement-engineer!

Is it possible release a new version of graphql-tools on npm that includes this bug fix? I have been running into issues in my code because of it. Thanks!

@excitement-engineer I think @martijnwalraven just released a new version so it should work for you now.

Thanks!


feature: Custom highlight context

Describe the solution you'd like
I would like to change the color in the context highlight, for example:
I saw you have color palette named "Iris", I tried to change ["@type"] with this color("iris") using highlight_groups options, but I couldn't.
Additional context

Above the example of I had been trying.

Hmm, this seems to work for me:
require("rose-pine").setup({
	highlight_groups = {
		["@type"] = { fg = "iris" },
	},
})

Nice, you are right, but I didn't know that I should use this "string annotation/decoration"(["@type"]) form.
Now it's working great, thank you for your support.

That's a lua thing, because "@" is a special character. ["..."] enables more flexibility with the key names.


s390x: CI broken by "bump go-patricia to 2.2.4"?

Looks like PR #25283 (commit  3d714b5ed58cfdfd5872ddd3654d171b09bb02d3) introduced a problem for s390x.

Looks like 3d714b5ed58cfdfd5872ddd3654d171b09bb02d3 is indeed the reason for the failures on s390x.

----------------------------------------------------------------------
PASS: docker_cli_import_test.go:124: TestImportFileNonExistentFile.pN52_github_com_docker_docker_integration_cli.DockerSuite    0.098s

----------------------------------------------------------------------
FAIL: docker_cli_import_test.go:92: TestImportFileWithMessage.pN52_github_com_docker_docker_integration_cli.DockerSuite

docker_cli_import_test.go:121:
    c.Assert(out, checker.Equals, "", check.Commentf("command output should've been nothing"))
... obtained string = "An error occurred trying to connect: EOF\n"
... expected string = ""
... command output should've been nothing

OOPS: 1 passed, 2 FAILED

Revert commit and re-run Test:

root@04afededd74a:/go/src/github.com/docker/docker#  # git show | patch -p1 -R
patching file hack/vendor.sh
patching file vendor/src/github.com/tchap/go-patricia/patricia/children.go
patching file vendor/src/github.com/tchap/go-patricia/patricia/patricia.go

root@04afededd74a:/go/src/github.com/docker/docker# TESTFLAGS='-check.f DockerSuite.TestImportFile' DOCKER_GRAPHDRIVER=vfs DOCKER_EXECDRIVER=native TIMEOUT="120m" hack/make.sh gccgo test-integration-cli
PASS: docker_cli_import_test.go:45: TestImportFile.pN52_github_com_docker_docker_integration_cli.DockerSuite    5.860s
PASS: docker_cli_import_test.go:124: TestImportFileNonExistentFile.pN52_github_com_docker_docker_integration_cli.DockerSuite    0.099s
PASS: docker_cli_import_test.go:92: TestImportFileWithMessage.pN52_github_com_docker_docker_integration_cli.DockerSuite 4.065s
OK: 3 passed

The commit does not look not architecture specific. So perhaps a gccgo issue?

We currently don't have tests enabled on gccgo so could have missed this.
Can you test on amd64 gccgo?
BTW is s390x moving to normal Go in 1.7?
On 3 Aug 2016 20:35, "Michael Holzheu"<EMAIL_ADDRESS>wrote:

Looks like 3d714b5
https://github.com/docker/docker/commit/3d714b5ed58cfdfd5872ddd3654d171b09bb02d3
is indeed the reason for the failures on s390x.

PASS: docker_cli_import_test.go:124: TestImportFileNonExistentFile.pN52_github_com_docker_docker_integration_cli.DockerSuite    0.098s

FAIL: docker_cli_import_test.go:92: TestImportFileWithMessage.pN52_github_com_docker_docker_integration_cli.DockerSuite
docker_cli_import_test.go:121:
c.Assert(out, checker.Equals, "", check.Commentf("command output should've been nothing"))
... obtained string = "An error occurred trying to connect: EOF\n"
... expected string = ""
... command output should've been nothing
OOPS: 1 passed, 2 FAILED

Revert commit and re-run Test:

root@04afededd74a:/go/src/github.com/docker/docker#  # git show | patch -p1 -R
patching file hack/vendor.sh
patching file vendor/src/github.com/tchap/go-patricia/patricia/children.go
patching file vendor/src/github.com/tchap/go-patricia/patricia/patricia.go
root@04afededd74a:/go/src/github.com/docker/docker# TESTFLAGS='-check.f DockerSuite.TestImportFile' DOCKER_GRAPHDRIVER=vfs DOCKER_EXECDRIVER=native TIMEOUT="120m" hack/make.sh gccgo test-integration-cli
PASS: docker_cli_import_test.go:45: TestImportFile.pN52_github_com_docker_docker_integration_cli.DockerSuite    5.860s
PASS: docker_cli_import_test.go:124: TestImportFileNonExistentFile.pN52_github_com_docker_docker_integration_cli.DockerSuite    0.099s
PASS: docker_cli_import_test.go:92: TestImportFileWithMessage.pN52_github_com_docker_docker_integration_cli.DockerSuite 4.065s
OK: 3 passed
The commit does not look not architecture specific. So perhaps a gccgo
issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/25360#issuecomment-237328684,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdcPFOf2_fGLkptwS3DFBZCdUruPSeFks5qcN9rgaJpZM4JbdVh
.

Can you test on amd64 gccgo?

I tried the following on my laptop (Ubuntu 14.04):
# docker build --rm --force-rm -t docker:build -f Dockerfile.gccgo .
# docker run --rm -ti --privileged docker:build bash
# TESTFLAGS='-check.f DockerSuite.TestImportFile' DOCKER_GRAPHDRIVER=vfs DOCKER_EXECDRIVER=native TIMEOUT="120m" hack/make.sh gccgo test-integration-cli

Looks like it hangs in .ensure-httpserver in the step "docker build -t httpserver":
++++ tar -cC bundles/1.13.0-dev/test-integration-cli/frozen-images .
++++ docker load
++++ set +x
Untagged: hello-world:latest
---> Making bundle: .ensure-httpserver (in bundles/1.13.0-dev/test-integration-cli)

BTW is s390x moving to normal Go in 1.7?

Our current plan is to use golang 1.7 for Dockerfile.s390x when it is released in the next weeks.
Would you agree?

BTW with go1.7rc5 the tests work fine also on s390x:
# go version
go version go1.7rc5 linux/s390x
# git checkout 3d714b5ed58cfdfd5872ddd3654d171b09bb02d3
# TESTFLAGS='-check.f DockerSuite.TestImportFile' DOCKER_GRAPHDRIVER=vfs DOCKER_EXECDRIVER=native TIMEOUT="120m" hack/make.sh dynbinary test-integration-cli
INFO: Testing against a local daemon
PASS: docker_cli_import_test.go:45: DockerSuite.TestImportFile  1.713s
PASS: docker_cli_import_test.go:124: DockerSuite.TestImportFileNonExistentFile  0.009s
PASS: docker_cli_import_test.go:92: DockerSuite.TestImportFileWithMessage       1.487s
OK: 3 passed

@unclejack : I now tried the "go-patricia" testsuite on my laptop (amd64) with gccgo 6.1. It works with version v2.1.0 and fails with version v2.2.4. So it seems to be an architecture independent gccgo related problem.
Here the steps to reproduce:

Start gcc:6.1 image and get go-patricia code

$ docker run -ti --rm gcc:6.1 bash
root@a0f013b0c10a:~# mkdir -p /root/go/src
root@a0f013b0c10a:~# cd /root/go/src
root@a0f013b0c10a:~/go/src# export GOPATH=/root/go
root@a0f013b0c10a:~/go/src# go get github.com/satori/go.uuid
root@a0f013b0c10a:~/go/src# git clone https://github.com/tchap/go-patricia.git github.com/tchap/go-patricia

Try with version 2.1.0 (works):

root@a0f013b0c10a:~/go/src# cd github.com/tchap/go-patricia/patricia && git checkout v2.1.0 && cd -
Previous HEAD position was 0d76659... Fix Delete memory leak and other bugs found
HEAD is now at d87fea6... Merge pull request #14 from ishidawataru/fix_walk
root@a0f013b0c10a:~/go/src# go test github.com/tchap/go-patricia/patricia
ok      github.com/tchap/go-patricia/patricia   4.646s

Try with version 2.2.4 (fails):

root@a0f013b0c10a:~/go/src# cd github.com/tchap/go-patricia/patricia && git checkout v2.2.4 && cd -
HEAD is now at 0d76659... Fix Delete memory leak and other bugs found
root@a0f013b0c10a:~# go test github.com/tchap/go-patricia/patricia

--- FAIL: TestTrie_DeleteLeakageDense (0.00s)
panic: runtime error: index out of range [recovered]
        panic: runtime error: index out of range

        :0

        :0

github_com_tchap_go_patricia_patricia.remove.pN53_github_com_tchap_go_patricia_patricia.sparseChildList
        /root/go/src/github.com/tchap/go-patricia/patricia/children.go:73
github_com_tchap_go_patricia_patricia.Delete.pN42_github_com_tchap_go_patricia_patricia.Trie
        /root/go/src/github.com/tchap/go-patricia/patricia/patricia.go:302
github_com_tchap_go_patricia_patricia.TestTrie_DeleteLeakageDense
        /root/go/src/github.com/tchap/go-patricia/patricia/patricia_dense_test.go:196

        :0

goroutine 16 [chan receive]:

        :0

created by main
        /usr/src/gcc/libgo/runtime/go-main.c:54

        :0

        :0

goroutine 17 [syscall]:
        goroutine in C code; stack unavailable

goroutine 18 [finalizer wait]:

goroutine 19 [GC sweep wait]:
        :0

        :0
FAIL    github.com/tchap/go-patricia/patricia   0.044s

Yes, I was just thinking no one will care about gccgo after this...
On 4 Aug 2016 2:52 p.m., "Michael Holzheu"<EMAIL_ADDRESS>wrote:

BTW is s390x moving to normal Go in 1.7?
Our current plan is to use golang 1.7 for Dockerfile.s390x when it is
released in the next weeks.
Would you agree?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/25360#issuecomment-237543325,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdcPJ638HYNgqVUiH3at3aj1n9uy1TQks5qceCDgaJpZM4JbdVh
.

So it seems to be an architecture independent gccgo related problem.

Or it is a off-by-one problem with patricia that is discovered by gccgo ;-)

I opended issue tchap/go-patricia#26 to clarify the root cause of the problem

@michael-holzheu This issue seems to have nothing to do with Go itself or with the go-patricia code. If it works with Go and it breaks with gccgo, that means it's quite likely gccgo itself is broken in some way.
It might be a really bad idea to go after every individual package to fix it to make it work with gccgo (except for the architecture specific fixes, constants and quirks). This seems to imply that valid code needs to be modified in order to work around a certain compiler's bugs. A better course of action would be to address the underlying causes of those gccgo problems.
When Go 1.7 drops, the s390 Dockerfile should use Go 1.7. gccgo support shouldn't be removed from the Docker repository because that would allow us to help make gccgo better in the future.

it works with Go and it breaks with gccgo, that means it's quite likely gccgo itself is broken in some way.

@unclejack it's likely, but it can also be that gccgo detected a bug that golang did not. I just wanted to make sure that this is not the case before I open a gccgo bug.

It might be a really bad idea to go after every individual package to fix it to make it work with gccgo

That never was my intention.

Ok, this has been fixed upstream in patricia 2.2.5.

Should be fixed by https://github.com/docker/docker/pull/25510

Should be fixed by #25510

At least this one looks good now, thanks:
# git checkout 34877a41a8a6660a31ff3770566cc1341759b16c
# TESTFLAGS='-check.f DockerSuite.TestImportFile' DOCKER_GRAPHDRIVER=vfs DOCKER_EXECDRIVER=native TIMEOUT="120m" hack/make.sh gccgo test-integration-cli

PASS: docker_cli_import_test.go:45: TestImportFile.pN52_github_com_docker_docker_integration_cli.DockerSuite    4.781s
PASS: docker_cli_import_test.go:124: TestImportFileNonExistentFile.pN52_github_com_docker_docker_integration_cli.DockerSuite    0.128s
PASS: docker_cli_import_test.go:92: TestImportFileWithMessage.pN52_github_com_docker_docker_integration_cli.DockerSuite 4.218s
OK: 3 passed

But with https://jenkins.dockerproject.org/job/Docker Master (z)/197 we have another problem.
Investigating...

But with https://jenkins.dockerproject.org/job/Docker Master (z)/197 we have another problem.
Investigating...

I opened issue #25533 for the new problem

@unclejack : FYI: Perhaps we should consider updating to go-patricia version v2.2.6, because of commit tchap/go-patricia@666120de432aea38ab06bd5c818f04f4129882c9? See also comment https://github.com/tchap/go-patricia/issues/26#issuecomment-239687539.

@michael-holzheu see https://github.com/docker/docker/pull/25809

@michael-holzheu see #25809

Thanks!


Add Jess to alumni

Because this was still missing :heart:
ping @docker/core-engine-maintainers @jfrazelle

sadly LGTM :cry:

LGTM :crying_cat_face:

thanks @thaJeztah! :heart:
LGTM

LGTM :heart:

LGTM 💓

Thanks <3
On Tue, May 10, 2016 at 11:34 AM, Vincent Demeester <
<EMAIL_ADDRESS>wrote:

LGTM 💓
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/22634#issuecomment-218248705

--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC  511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

Thank you, Jess


chore: add setRemoveElement and tests

Added setRemoveElement since this operation is needed to implement flush for MomentoTaggedCache (https://github.com/momentohq/laravel-cache/issues/9).
Also, added tests for this operation.

lgtm other than I'm not sure if we want that vscode file committed to vcs


increase timeouts for downloads

it might ease with errors like https://github.com/microsoft/vcpkg/issues/7207, https://github.com/microsoft/vcpkg/issues/18734
see also https://github.com/microsoft/vcpkg/pull/18171 for related issues with using vcpkg as a download tool

I'm not really convinced using a 2 minute timeout is likely to resolve the issue over the existing 1 minute timeout? Keep in mind that timeout is time-to-first-byte. If you get not a single packet back from the server in a whole minute something is probably toast?

nope, it's common with some cloud proxies that start with Z that they stop responding for 30 seconds for the last few bytes of your download, while they do whatever they like.
Your download just go timeout in vcpkg (not in the browsers, or in aria, we can copy/paste their timeout if you prefer) and you are left with a .part file "almost" complete (everything apart the last few kb missing).
This is alleviating the issue completely, but i agree it's not nice to be seen. It works.

Your download just go timeout in vcpkg (not in the browsers, or in aria, we can copy/paste their timeout if you prefer) and you are left with a .part file "almost" complete (everything apart the last few kb missing).

It would surprise me if that would change that then, since all of these timeouts are about starting the download, not anything during the download. The timeouts are only resolve, connect, and send.

receive, the last one?

receive, the last one?

You're correct, I misread because of the word wrapping 😭
If it's intending to workaround a specific proxy configuration perhaps we should use 0, 60000,  30000, 120000?
I'm a little nervous to mess with timeouts like that because it's a symptom treatment rather than a cause treatment, if you know what I mean, so I think we should be as conservative in what is changed as possible. Other maintainers may have different ideas though....

receive, the last one?

You're correct, I misread because of the word wrapping 😭
If it's intending to workaround a specific proxy configuration perhaps we should use 0, 60000, 30000, 120000?
I'm a little nervous to mess with timeouts like that because it's a symptom treatment rather than a cause treatment, if you know what I mean, so I think we should be as conservative in what is changed as possible. Other maintainers may have different ideas though....

i agree it's not nice to be seen. It works.

as i said before, i already agree with you. If anyone has a better solution, for me it would be perfect.
I put 120k everywhere just for consistency, so not to have to come back here again later…
(for the wrap, the original commit was better, but the clang format then complained and i had to make it “wrong” to make test happy)

so any news on this front? is this PR considered unacceptable or are you thinking about it?

so any news on this front? is this PR considered unacceptable or are you thinking about it?

I personally am hesitant to sign off due to the aforementioned "seems like addressing a symptom rather than a problem" issues but I'm not "request changes" either. I poked other folks to take a look...

I mean, if it fixes real issues, I'm not that against it.

Thanks for your contribution!


Image widget size only dependent on width

I think there's actually 2 connected issues here.
First is that no matter what configuration I set for the image, it will always fill width, even if width is set to Length::Shrink and height is set to Length::Fill.
Second is that the image cannot be bound within a container. By this I mean that if the image is taller than the container is tall, it will overflow out of the canvas instead of shrinking the height. Here is the code snippet for the the image and the screenshots to show what I mean:
Container::new(
    Image::new("/home/user/Pictures/tall.png")
        .width(Length::Shrink)
        .height(Length::Fill)
)
    .width(Length::Fill)
    .center_x()

Image being shrunk by narrow window:

Image being cut off in a wide window:

I see that there is a TODO in the Image widget's layout method, so this could just be functionality not yet implemented. A possible solution (albeit maybe a naive one) is to modify that method to look something like this:
let mut size = limits.width(width).height(height).resolve(Size::ZERO);

size.height = size.width / aspect_ratio

// new code
if size.height > limits.max().height {
    size.height = limits.max().height;
    size.width = size.height / (1 as f32 /aspect_ratio);
}
// end new code

layout::Node::new(size)

This solution, while fixes it for my use case (having the entire image visible at all times), it removes the ability to have the image flow off the screen, if that is at all desired. I'm interested to hear your thoughts on this.

Hey @Shootertrex,
I think this may have been fixed by #90 here: https://github.com/hecrj/iced/blob/1f60e2820463ef9f7fe9dda5d8b8fa040fdd8666/native/src/widget/image.rs#L70-L93
Have you tried it with the latest master changes? For instance, the pokedex example shows how the Image always stays visible:

Thanks for the quick response. You are correct that #90 fixed it. I had ran into this earlier in the week, but I wasn't expecting it to have already been fixed!
I'll close this issue then.


fix: minor infra issues with ports

Codecov Report

Merging #461 into master will decrease coverage by 2.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #461      +/-   ##
==========================================
- Coverage   65.07%   62.97%   -2.11%
==========================================
  Files          69       69
  Lines        4238     3754     -484
==========================================
- Hits         2758     2364     -394
+ Misses       1254     1168      -86
+ Partials      226      222       -4

Impacted Files
Coverage Δ

pkg/network/pubsub_handler.go
33.33% <0.00%> (-9.53%)
:arrow_down:

pkg/peer/peer.go
25.00% <0.00%> (-8.34%)
:arrow_down:

pkg/object/type_hint.go
10.00% <0.00%> (-5.22%)
:arrow_down:

pkg/migration/migration.go
31.14% <0.00%> (-5.22%)
:arrow_down:

internal/nat/nat.go
17.64% <0.00%> (-4.58%)
:arrow_down:

pkg/crypto/ed25519.go
61.11% <0.00%> (-4.16%)
:arrow_down:

pkg/network/filters.go
36.84% <0.00%> (-3.90%)
:arrow_down:

pkg/object/object.go
75.37% <0.00%> (-3.55%)
:arrow_down:

pkg/object/map.go
85.96% <0.00%> (-2.45%)
:arrow_down:

pkg/resolver/lookup_options.go
53.33% <0.00%> (-2.23%)
:arrow_down:

... and 58 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 f13ee71...53e1545. Read the comment docs.


Improve imagenet example performance

The dtype of mean is numpy.float32.
Division operation is slow.

LGTM! #2000 :)

Thank you!


Suggestion: Add allow="microphone; camera"

I was having problems with the webcam in the Chatroom (I have the paid version) where Chrome and Opera browsers would not allow the cam and mic functions but Firefox and Edge were working fine.
To fix this I edited the following file _protected/app/system/modules/chat/views/base/tpl/home/index.tpl
I added     allow="microphone; camera"

Thanks for the suggestion! 🎉

For further information: https://www.chromium.org/Home/chromium-security/deprecating-permissions-in-cross-origin-iframes


(SP: 2) Check useChangeConfirm hook on certain requirements

Check useChangeConfirm hook on certain requirements
Check if the next requirements are implemented in PR #2410. If not, then implement it:

[ ] Confirm message should display all courses AND cooperations that have the current resource that the user wants to edit or delete. It seems that it checks only courses but not includes cooperations:

[ ] Confirm message should display all ACTIVE cooperations that have the current resource that the user wants to edit or delete.

IMPORTANT:
Also, you need to ask our tech lead and designer for a mockup - because in the requirements, if a resource is added to an active AND closed cooperation or a course is added to an active and closed cooperation, and the tutor wants to make this change or delete, then the tutor must send a request to all students to ask for permission on changing or deleting the current resource/course.

the hook deleted in PR #2553

the hook deleted in PR #2553


Example for changing the setting

This sounds like a very useful extension, thanks for making it available!
I have some difficulty changing the settings. I want to set the style to numpy. From your documentation, I couldn't figure out exactly how to change the style in setting.json. I tried adding "docstring.type": "numpy", but it didn't work.

Hello, thank you for your feedback!
I understand you're looking to change the "style type" similar to numpy or google within the extension. While the extension doesn't offer a direct option to switch between these specific styles, it does provide a feature for theming through the use of scopes. You can explore this in the customization section (customization). Here, you'll find that some scopes are designed to target specific style types, including ones like "numpy".
This functionality is particularly beneficial when dealing with third-party libraries, whose documentation styles may vary. When you introspect the code from these libraries, the extension's highlighting feature will highlight documentation no matter what style is used.
Keep in mind this extension is for highlighting only, it doesn't enforce any style rules.

I see. So, out of the box, it should support numpy-style docstring highlighting. I always used this style for my docstrings, but when I installed this extension, it didn't correctly highlight the args, like the demo. Here's what I see when I open a function from numpy:

So, it's not detecting arg names or types, and seems to be working partially.

I think the issue is with your theme that may blends the scopes color. Bellow you'll see what I get with the modern dark theme in VSCode:

You can analyze this on your side:

Run the VSCode command Developer - Inspect Editor Tokens and Scopes (using Cmd+Shift+P)
Left click on a character in your source to inspect the available scopes (you can enable/disable the extension to see which scopes it adds to the source code, see Available Scopes :

As you can see, the extension adds a bunch of scopes and VSCode will look up for the first scope that implements a style. In my example, it's the punctuation.definition.tag style that is used (standard scope as I don't have custom theming). You can override this behavior by adding this in you settings.json file for instance:
"editor.tokenColorCustomizations": {
  "textMateRules": [
    {
      "scope": "docstring.variable",
      "settings": {
        "fontStyle": "bold underline",
        "foreground": "#569cd6",
      }
    },
  ]
}

Then you can play around to make it as you like!

Ah, that's right. I am using One Dark. That's neat! I ended up using this:
    "editor.tokenColorCustomizations": {
        "textMateRules": [
            {
                "scope": "docstring.variable.placeholder",
                "settings": {
                    "fontStyle": "bold",
                    "foreground": "#569cd6",
                },
            },
            {
                "scope": "docstring.variable.end",
                "settings": {
                    "foreground": "#a1c1dc92",
                },
            }
        ]
    }

to get:

Thanks for the help!


Low performance at adding new element to list

Version
2.4.4
Reproduction link
https://jsfiddle.net/go14z0yh/1/
Steps to reproduce

Open link
Start recording performance (chrome developer tools -> performance)
Click on the button
Stop recording

What is expected?
It is expected that adding 1 message does not require heavy calculations (less then 1ms).
What is actually happening?
In practice, it turns out that the list is completely rendered again (in a virtual DOM). These calculations take about 30ms (core i7 4770k).

I think this point can obviously be optimized.

This is expected behavior. VDOM by definition needs to generate 10,000 virtual elements and iterate through them to find diffs. If you have an "obvious" way to optimize them, please submit a PR.

Why can not you add a wrapper for example for Array.push, Array.filter and so on? To make it possible to do the computed properties on their basis and vue understood which elements of the array have changed.

these calculations take about 30ms

I think it's pretty decent score for such a large array :) Out of curiosity i checked how React is doing in such a case and it takes around 130-160 ms to render this size of an on my pc (i5-4690). Vue as you said ~30 ms

In native JS this action takes 0.68 ms (with the exception of the 'layout' and 'update layer tree'), in vue 30-60 ms. A huge difference. I'm sure that you can make it possible to tell vue which particular part of the array has changed.

Modifying the DOM manually will always be faster, because you skip all the data update, virtual DOM diffing parts. The thing is you can't realistically write all the DOM manipulations directly when building a medium to big app because it will become too complex and you will eventually end up with buggy/un-maintenable code.

I understand this, but I still think it should be possible to prompt vue on what changes in the data you need to pay attention to, and which ones do not. I do not propose to get rid of VDOM, I just want it to be possible to more flexibly organize the rendering. If I could tell vue.js that I just added 1 element to the array, and did not change it all, then vue could take the previous version of VDOM and just add one element to it, not rerendering all the rest. It's the same with synchronizing VDOM and DOM. In this case, vue would know that all the other elements have not changed and it would have just added one new one. I think this is quite feasible and would greatly enhance the rendering performance.

I'm not sure it could be applied in this case, but dividing into multiple components is a way to cache parts of the VDOM.

Adding one item to the array does not always means adding one element to the DOMList, it may be more complicated.
What if your template looks like:

  <button @click="add" v-if="messages.length < 10002">
    Add 1 message
  </button>

 10000 && index === 9999)">{{ message }}


.pyc files still pushing to master

Every time i run the server the .pyc files still are needed for commiting etc. even with the gitignore instructions Judah has added

https://stackoverflow.com/questions/26021040/remove-pyc-files-from-git-remote-repository

Have fixed the issue by removing the .pyc files from our remote repository and then editing the gitignore to ignore all .pyc files


GoSec fixes and improvements

Fixes some issues identified by GoSec, and incorporates the scan into CI here so it will fail when other issues are found.

/cc @dhaiducek
I don't know if something like this gosec change would be better in a common makefile?

/hold
I found the other test issue

/cc @dhaiducek
I don't know if something like this gosec change would be better in a common makefile?

I was going to do it, but if you have a moment, it can go here: https://github.com/stolostron/governance-policy-framework/blob/02d52d5811bfa706ec84fcd9a2f153a46ae9aa5b/build/common/Makefile.common.mk#L108

/unhold 🤞


Fixes #2418: Enhance wiggle to generate its UserErrorConverstion trait with a function that returns Result<abi_err, String>

Long-time listener, first-time caller.
I am submitting this WIP PR for issue #2418.  Please see issue #2418 for a description.

[x] This has been introduced in issue #2418.
[x] This PR contains refactored test cases.
[x] This has been discussed in issue #2418.
[x] Reviewer request: @pchickey

@alexcrichton -- I believe this is ready to merge.  I appreciate you!

👍


Can I get pronunciation score using the sdk version?

If I want to get the pronScore - fluency - accuracy should I use the Rest-API or can I get it using the sdk version?
I'm using it in android and I was able to get the confidence score using this:
SpeechConfig config = SpeechConfig.fromSubscription(speechSubscriptionKey, serviceRegion);

config.setServiceProperty("wordLevelConfidence","true", ServicePropertyChannel.UriQueryParameter);
config.setServiceProperty("format", "detailed", ServicePropertyChannel.UriQueryParameter);

But how can I get the other information like word pronunciation and ext.

@ziadhassan7 Thanks a lot for your query. We will get back to you asap.

@ziadhassan7 The feature is under development. If you can explain your use case and business we can plan to prioritize it higher.

I'm working on something to train and develop the speaking skill to non-English natives; so, it would be great if I could show the user how much accurate they pronounced each word.
I've been also trying to do that on the REST-API using Postman to check if I could do it there, and to figure out what parameter should I pass to the url; So, maybe I could do that on the sdk version as well, but it didn't work with me neither!!
I should pass pronunciationScoreParams as the parameter and a JSON Base64 encoded text as the value of the parameter right? Or should I convert the json first to UTF8?
I tried both and nothing worked for me and I used those websites: to Base64 - to UTF8
And I used the example JSON from documentations without spaces:
{
  "ReferenceText": "Good morning.",
  "GradingSystem": "HundredMark",
  "Granularity": "FullText",
  "Dimension": "Comprehensive"
}

@ziadhassan7 do you mind sharing your code to call the REST API, so that I can check where the issue locates?
 This can help us judge the priority of the SDK support.

@yinhew I haven't written the code yet, i'm using a software called Postman to test the API first.
I converted this JSON {"ReferenceText":"Good morning."}
to this UTF-8 code:
\x7b\x22\x52\x65\x66\x65\x72\x65\x6e\x63\x65\x54\x65\x78\x74\x22\x3a\x22\x47\x6f\x6f\x64\x20\x6d\x6f\x72\x6e\x69\x6e\x67\x2e\x22\x7d
and then from UTF-8 to Base64:
XHg3Ylx4MjJceDUyXHg2NVx4NjZceDY1XHg3Mlx4NjVceDZlXHg2M1x4NjVceDU0XHg2NVx4Nzhc
eDc0XHgyMlx4M2FceDIyXHg0N1x4NmZceDZmXHg2NFx4MjBceDZkXHg2Zlx4NzJceDZlXHg2OVx4
NmVceDY3XHgyZVx4MjJceDdk

So now, the url looks like that:
https://westus.stt.speech.microsoft.com/speech/recognition/conversation/cognitiveservices/v1?language=en-US&Ocp-Apim-Subscription-Key=[API-KEY]&Content-Type=audio/wav; codecs=audio/pcm; samplerate=16000&pronunciationScoreParams=XHg3Ylx4MjJceDUyXHg2NVx4NjZceDY1XHg3Mlx4NjVceDZlXHg2M1x4NjVceDU0XHg2NVx4Nzhc
eDc0XHgyMlx4M2FceDIyXHg0N1x4NmZceDZmXHg2NFx4MjBceDZkXHg2Zlx4NzJceDZlXHg2OVx4
NmVceDY3XHgyZVx4MjJceDdk
And that's the result;
{
    "RecognitionStatus": "Success",
    "DisplayText": "Figure 2 shows an example of processing of speech using human ear models. He acted swiftly when his time came, taking all Miller. Last year the NBA playoffs. The boys humiliated themselves against Detroit control activities. It's important for the first time in 10 years research and development spending in the federal budget program. She's proprietary Macintosh graphic displays.",
    "Offset": 200000,
    "Duration": 214200000
}

@ziadhassan7 can you replace the "conversation" in the URL into "interactive" and try again?
We currently still don't support the pronunciation assessment feature on "conversation" route, and only "interactive" route is support. Sorry for the misleading in the doc.
The "conversation" support should come out in the coming 1~2 weeks.

Ok, this is great! now it says this:
Unexpected json in 'pronunciationScoreParams' parameter. Unexpected character encountered while parsing value: . Path '', line 0, position 0. Please make sure the JSON string is encoded with UTF8 and then base64.
Those are the websites that I used:
UTF-8 Encoder
UTF-8 to Base64
Maybe there is a setting in the website that i used wrong, any suggestion?
And also, Is there is any turnaround for using pronunciation in SDK ?

@ziadhassan7 I looked at your base64 string. I found its generated from string "\x7b\x22\x52\x65\x66\x65\x72\x65\x6e\x63\x65\x54\x65\x78\x74\x22\x3a\x22\x47\x6f\x6f\x64\x20\x6d\x6f\x72\x6e\x69\x6e\x67\x2e\x22\x7d". This is not the right way to do the base64 encoding.
For your JSON, the right base64 should be eyJSZWZlcmVuY2VUZXh0IjoiR29vZCBtb3JuaW5nLiJ9

Thanks, mr @yinhew ! That worked.
It's weird that is says "Please make sure the JSON string is encoded with UTF8 and then base64." but it worked by encoding the JSON to Base64 directly. Maybe, the converter did the job by itself .
Again, Thanks a lot and I hope the SDK version support pronunciationScoreParams soon. :D

Any update on when dimension=Comprehensive will be available from the Python SDK? It's just more convenient to use the SDK than use the REST API. Also, the discrepancies between the two make room for confusion.
For anyone else stumbling upon this:

The dimension parameter for Pronunciation Assessment is [usable and documented here in the REST API].(https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/rest-speech-to-text-short#pronunciation-assessment-parameters)
The same parameter is missing (not supported) from the Python examples and docs, because it's not yet part of the SDK.

Time spent clarifying such things up would be best spent coding and building something :)


Definition of the isFullyDecrypted() and isFullyEncrypted()

I wanted to migrate to PGPainless variant of fullyDecrypted, but found out following:
In our code we currently have following:
    val fullyDecrypted = if (keyRing is PGPSecretKeyRing) {
      // did the test again for Smart Cast encryption algorithm.
      // 0 means not encrypted. See https://tools.ietf.org/html/rfc4880#section-5.5.3
      keyRing.secretKeys.asSequence().all { it.keyEncryptionAlgorithm == 0 }
    } else {
      null // public key
    }

But in PGPainless it is:
    // class KeyInfo

    public boolean isFullyDecrypted() {
        if (!isSecretKey()) {
            return true;
        }
        for (PGPSecretKey secretKey : getSecretKeys()) {
            if (!KeyInfo.hasDummyS2K(secretKey) && KeyInfo.isEncrypted(secretKey)) {
                return false;
            }
        }
        return true;
    }

    public static boolean isEncrypted(PGPSecretKey secretKey) {
        return secretKey.getS2KUsage() != 0;
    }

Is it equivalent or not? Which one's is more correct (judging by keyEncryptionAlgorithm or S2KUsage)?
Same thing affects fullyEncrypted.

@tomholub @vanitasvitae @Jerbell which one you think is more correct?

Paul's implementation is more appropriate with regards to dummy keys.
As for the public key, we decided to go with null (not appropriate to encrypt) and Paul went with true, and neither is wrong, imo.

Both are correct. Personally I would have public key = true but it's not a big deal.

I'll close this as resolved. Feel free to reopen if there are any more questions :)


Issue 166: Current offset for byte stream writer

Change log description
Byte stream writer maintains a write_offset that is used for conditional append. If conditional append failed when calling flush, user can deicide to panic or call seek_to_tail to fetch the latest write_offset of that segment and continue to do the append.
Purpose of the change
Fix #166
This PR is based on another PR that's about to be merged, right now the git diff is messy, please wait until that PR is merged to have a better review.

Codecov Report

Merging #176 into master will decrease coverage by 0.35%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##           master     #176      +/-   ##
==========================================
- Coverage   78.73%   78.37%   -0.36%
==========================================
  Files          50       50
  Lines        9422     9215     -207
==========================================
- Hits         7418     7222     -196
+ Misses       2004     1993      -11

Impacted Files
Coverage Δ

src/byte_stream.rs
88.70% <85.71%> (-0.29%)
:arrow_down:

shared/src/naming_utils.rs
93.65% <0.00%> (-2.81%)
:arrow_down:

controller-client/src/mock_controller.rs
44.71% <0.00%> (-0.25%)
:arrow_down:

src/lib.rs
96.66% <0.00%> (+4.35%)
:arrow_up:

This PR is depending on this to work.

@claudiofahey This PR now is depending on this PR. Instead of adding a new wirecommand, we decide to modify the existing one. We probably should not merge this PR until that modification is merged into Pravega.


Hide packages and releases if not being used

If the packages and releases are not being used, it is good to hide it :)

Packages I am hiding, but releases can be used

Okay. I thought you should hide it until you use it 🤔

You can open up a issue for using them ;)

haha lol


Shell-Curl doesn't add Content-Type header

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
The code generated from a request is not equivalent to that sent from bruno.
To reproduce:

run an http server

from flask import Flask, request, jsonify

app = Flask(__name__)

@app.route('/', methods=['POST'])
def handle_post_request():
    data = request.get_json()

    response = {
        "data": data
    }

    return jsonify(response), 200

if __name__ == '__main__':
    app.run(debug=True)

send a request through bruno (temp.bru), (returns 200)
send the request generated for shell using curl, (returns 415)

curl --request POST \
  --url http://localhost:5000/ \
  --data '"test request body"'

.bru file to reproduce the bug
meta {
name: temp
type: http
seq: 2
}
post {
url: http://localhost:5000
body: json
auth: none
}
body:json {
"test request body"
}
Screenshots/Live demo link

What version of bruno are you using? This use to be the behavior but was resolved in v1.24.0.

1.22.0
Sorry, didn't notice recent updates. I'll pull from nixpkgs unstable instead of 24.05.
https://search.nixos.org/packages?channel=unstable&from=0&size=50&sort=relevance&type=packages&query=bruno

Looks like the unstable is still behind but not as much.


Random texture appearing in some parts of the vs code window

Whenever I am using VS Code(VSC) and then I put the laptop to sleep, and after a while I open and unlock my laptop, some random texture appears over the window in some parts as shown in the picture. The texture appearing is also not part of any background app or the wallpaper.
Interestingly, some texture goes away way I bring my mouse over it and some go away when I click it. Clicking it becomes a problem coz idk what I am clicking over and sometimes leads to closing something I am working on.
Also the internal terminal seems all cleared out.
This does not happen in other windows/programs so must not be an OS related or DE bug.

VSCode Version:1.34.0
OS Version:Linux x64 4.15.0-50-generic
Linux Mint 19.1 Cinnamon

Steps to Reproduce:
1.Open VS Code
2.Turn the laptop to sleep
3.Reopen the laptop and unlock to open vs code

Does this issue occur when all extensions are disabled?: Yes

Are you on Linux? This appears to be a problem with Mesa.
More info here: https://www.reddit.com/r/archlinux/comments/btnbpr/awful_artifacts_lately_in_all_chromium_based/

We are building exploration builds that use a much newer version of our UI framework (Electron version 4.0.x). I wonder if this issue reproduces with one of these builds, could you try? Download:

macOS: Download
Linux: Download
Windows: Download

I believe I have the same issue. In my case, the problem happens only on the terminal. I have the same VS code version on my laptop and it does not have the issue.
@bpasero if you have an RPM version of the exploration builds, I can give it a try as well.

@orpiske https://az764295.vo.msecnd.net/exploration/fb34c44351af7e0abdf493d6fd70072b35f93edf/code-exploration-1.35.0-1559036183.el7.x86_64.rpm

@bpasero Thanks. I verified that the problem persists with the exploration build. I attached the screenshot for reference.

Do you also get this problem with other Chromium based apps? This appears to be a problem with Mesa.
More info here: https://www.reddit.com/r/archlinux/comments/btnbpr/awful_artifacts_lately_in_all_chromium_based/

I don't really know what electron here means. I have spotify but that does not have this problem. About messa, I am using Linux Mint which is based off of Ubuntru and Debian but the post is from Arch Linux. so I'm guessing it's not it. Not sure what Messa means either.

Can you see if it still reproduces when disabling the GPU support in VSCode? You can do that by running VSCode from the command line like this: code --disable-gpu
Unfortunately due to the nature of this flag, we currently cannot support a setting to set this on each startup.

Can you see if it still reproduces when disabling the GPU support in VSCode? You can do that by running VSCode from the command line like this: code --disable-gpu
Unfortunately due to the nature of this flag, we currently cannot support a setting to set this on each startup.

This solves the problem for me.

/duplicate https://github.com/microsoft/vscode/issues/15211


feat: Doc updates, Issue and PR templates are added

What does this PR do
Changes Included:
README Update: The main README.md now features the Kubeflow header and includes a new link to our updated Slack channel, facilitating better community engagement.
PR Template Addition: Added a new pull request template to the .github folder to streamline future contributions.
Workflow Update: Updated references to the container registry in our GitHub workflows to use ghcr.io, ensuring consistency with our current infrastructure.
Contributing Guidelines Revision: Removed the requirement for Google CLA from our contributing guidelines to simplify the contribution process.
Issue Templates Creation: Created new issue templates for Bugs, Features, and Questions to organize and prioritize incoming issues more efficiently.

One of the workflow is failed due to the bug introduced by recent PRs. Ignore this and this will be addressed in the next PR

@vara-bonthu fixed it in my PR. this PR has only changes in README.md, but has no changes in README.md template. workflow validates if there are changes in README.md after make helm-docs execution

@vara-bonthu Just run make helm-docs and commit the changes. I have updated README.go.tmpl in https://github.com/kubeflow/spark-operator/pull/1958. If there are any changes to the chart, like chart version, the command make helm-docs should be run to update the README.md file.

@ChenYi015 It might be beneficial to include the pre-commit instructions in the contributing.md file to assist contributors.

@ChenYi015 It might be beneficial to include the pre-commit instructions in the contributing.md file to assist contributors.

Agree, I will do it.


Clustering

Hi,
Do you will add the clustering feature?
Thanks

We do not plan on adding clustering to this project. Any advanced features like clustering will likely be implemented in our inline mapping project which you can find here


Add 4 new command line options:

-scale= to set pdfSettings.scale_factor
-delay= to delay after page load before rendering pdf (in my case allowed D3 charts to finish animating before creating the PDF)
-viewwidth= to set viewport width (in my case setting the width to 1600 fixed a table that was trying to size to 100% and getting cut off at 128px wide, which is the default)
-viewheight= added for parity, could be useful if element was specified as height=100%

Nice!
I think -delay is fragile, because the necessary timeout differs depending on host machine specs, system load, input size, etc. In long-term, I'd want a callback for the page to fire when ready. For one-shots, -delay is useful as-is.

I just noticed that -delay doesn't seem to work consistently in the release build. I'm not sure why it's different than the debug build, but maybe just doing a sleep in Client::OnLoadEnd() isn't allowing the message loop to run?  I was thinking it may be better to set a flag in OnLoadEnd() that the load is finished and then call m_jobManager->Process() from elsewhere after the timeout has expired.  Do you have any ideas on where we could call it from?  Thanks!

I changed to using CefPostDelayedTask() instead of sleeping, and now --delay works reliably on both builds.

The CefRefPtr is declared as CefRefPtr, not to our
derived CefRefPtr, so I either have to downcast it, or I
need to change the declaration to CefRefPtr in Client.h.
Which would you prefer?
On Sun, Apr 14, 2019 at 4:41 PM Sebastian Pająk<EMAIL_ADDRESS>wrote:

@spajak commented on this pull request.
In src/Client.cpp
https://github.com/spajak/cef-pdf/pull/29#discussion_r275173359:

@@ -308,4 +322,16 @@ void Client::OnRenderProcessTerminated(
DLOG(INFO) << "Client::OnRenderProcessTerminated";
}

+void Client::SetViewWidth(int viewWidth)
+{

RenderHandler renderHandler = (RenderHandler)(m_renderHandler.get());

Use CefRefPtr instead
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spajak/cef-pdf/pull/29#pullrequestreview-226412366,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AtaTBsPngZy22h01YdQgN8WFmdWz_Ecbks5vg5KEgaJpZM4a6tQ8
.

Yes. Change declaration. It should not break anything

Thanks


[FEATURE] ZTE-F680

Hello everyone,
I recently came across a challenge with decoding and decrypting configuration files from ZTE F680 v6 , specifically the db_user_cfg.xml file. This file contains important configuration details, including the superuser account and password of GPON, and is typically located in the /userconfig/cfg directory of ZTE routers.
THE ISSUE CANNOT DECRYPT IT WITH zte-config-utility  . we dont have an option to export the config.bin in the router closed :
HERE THE FILES THAT I'VE GOT FROM THE ROUTER :
dataprotocol
db_backup_cfg.xml
db_user_cfg.xml
hardcode
paramtag
ANY WAN CAN HELP . I NEED TO UNDERSTAND HOW TO DO IT !
THANKS IN ADVANCE

Can you upload those files, or email them to me ? Can you also grab the /bin/cspd file and upload that?

ztefiles.zip
Thanks in advance here the files requested

Can you upload those files, or email them to me ? Can you also grab the /bin/cspd file and upload that?

Hope that a solution will be finded !

I have a config.bin file from the zte F680 that I was able to extract when it asked for admin credentials on my modem, but unfortunately those credentials only lasted for 24 hours and I only made a backup of the configuration, but I would like to be able to edit that configuration in the file and just upload it with my normal credentials. I hope someone can decipher it.
config.zip

@mkst  . Any update please ?

I think the method to decrypt the hardcodefiles/* is different,

undefined4 CspHardCodeParamGet(char *param_1,char *param_2,int param_3,undefined4 param_4)

{
  char cVar1;
  size_t sVar2;
  char *pcVar3;
  __pid_t _Var4;
  long lVar5;
  FILE *__stream;
  uint uVar6;
  int iVar7;
  int iVar8;
  uint uVar9;
  int iVar10;
  bool bVar11;
  bool bVar12;
  char acStack_2b8 [36];
  char acStack_294 [36];
  char local_270 [36];
  char local_24c [36];
  char acStack_228 [256];
  char local_128 [64];
  undefined auStack_e8 [196];

  memset(acStack_228,0,0x100);
  memset(acStack_2b8,0,0x21);
  memset(acStack_294,0,0x21);
  if (((param_1 != (char *)0x0 && (param_3 != 0 && param_2 != (char *)0x0)) &&
      (sVar2 = strlen(param_2), sVar2 != 0)) &&
     (pcVar3 = strstr(param_1,"/etc/hardcodefile/"), pcVar3 != (char *)0x0)) {
    sVar2 = strlen("/etc/hardcodefile/");
    _Var4 = getpid();
    lVar5 = syscall(0xe0);
    snprintf(acStack_228,0x100,"%s%s%d%lu%s","/var/tmp/",pcVar3 + sVar2,_Var4,lVar5,"-decry");
    memset(local_270,0,0x21);
    memset(local_24c,0,0x21);
    memset(local_128,0,0x100);
    __stream = fopen("/etc/hardcode","r");
    if (__stream != (FILE *)0x0) {
      pcVar3 = fgets(local_128,0x100,__stream);
      if (pcVar3 == (char *)0x0) {
        fclose(__stream);
      }
      else {
        fclose(__stream);
        iVar7 = 0;
        do {
          cVar1 = local_128[iVar7];
          if (cVar1 == '\r' || cVar1 == '\n') {
            local_128[iVar7] = '\0';
            break;
          }
          iVar7 = iVar7 + 1;
        } while (iVar7 != 0x100);
        iVar10 = 0;
        iVar7 = 0;
        uVar9 = 0;
        do {
          iVar8 = iVar7;
          if (iVar10 - 5U < 0x10) {
            iVar8 = iVar7 + 1;
            local_270[iVar7] = local_128[iVar10] + '\x03';
          }
          uVar6 = iVar10 - 7;
          bVar12 = 0x1e < uVar6;
          bVar11 = uVar6 == 0x1f;
          if (uVar6 < 0x20) {
            bVar12 = 0x1f < uVar9;
            bVar11 = uVar9 == 0x20;
          }
          uVar6 = uVar9;
          if (!bVar12 || bVar11) {
            uVar6 = uVar9 + 1;
            local_24c[uVar9] = local_128[iVar10] + '\x01';
          }
          iVar10 = iVar10 + 1;
          iVar7 = iVar8;
          uVar9 = uVar6;
        } while (iVar10 != 0x40);
        snprintf(acStack_2b8,0x21,"%s%s",local_270,auStack_e8);
        snprintf(acStack_294,0x21,"%s",local_24c);
        iVar7 = CspHardCodeDecry(param_1,acStack_228,acStack_2b8,acStack_294);
        if (iVar7 == 0) {
          iVar7 = CspHCReadParam(acStack_228,param_2,param_3,param_4);
          if (iVar7 == 0) {
            unlink(acStack_228);
            return 0;
          }
          unlink(acStack_228);
        }
      }
    }
  }
  return 0xffffffff;
}


[Question]:  How to coordinate different people working on different parsers?

Question
Once other people from the lehrstuhl start participating, we should watch out for duplicate work.
Furthermore, what about started but abandoned parsers? Maybe someone is interested in building on this code.
I propose that we add a table to the wiki where we gather news sources and encourage contributors to claim a source before working on it.

Is this still relevant? It seems to have worked well enough during this semester‘s course.


Improve graph generation for sessions

[x] Improve implementation of Graph (cf. https://github.com/Componolit/RecordFlux/pull/382#discussion_r465180242)
[ ] Integrate graph generation into graph subparser in cli
[x] Improve graph layout

@treiher I'm not quite sure what the second item was meant to be. AFAICT it is integrated. It that outdated?

@treiher I'm not quite sure what the second item was meant to be. AFAICT it is integrated. It that outdated?

I'm not sure either. Looks outdated to me.


Add Voice Assistant Feature to PetMe Website

Description:
We propose the addition of a Voice Assistant feature to the PetMe website. This enhancement will provide an interactive and accessible experience for users, allowing them to navigate and interact with the website using voice commands. The Voice Assistant will improve the overall user experience and make the website more inclusive for individuals with disabilities or those who prefer voice-based interactions.
Expected Behavior:

The Voice Assistant should be accessible through a designated button or voice trigger on the website.
Upon activation, the Voice Assistant should provide audio feedback to indicate its readiness.
Users should be able to perform key website actions using voice commands, such as:

Navigating to different sections/pages of the website.
Adopting a pet or donating a pet through voice prompts.
Requesting emergency care for stray animals.
Initiating a call with a team member using the "Contact" page.

The Voice Assistant should be able to respond to common queries or provide relevant information about the project, its features, and the adoption process.
The feature should be compatible with a wide range of devices and browsers, ensuring a seamless experience for users across different platforms.

Additional Considerations:

The Voice Assistant should have a clear and natural-sounding voice.
It should be capable of handling errors gracefully and provide informative responses in case of any issues or misunderstandings.
Integration with speech recognition technologies and natural language processing libraries should be explored to improve the accuracy and responsiveness of the Voice Assistant.

Implementation Approach:
We suggest leveraging existing voice assistant frameworks or libraries such as Web Speech API, Alan AI, or Dialogflow to implement the Voice Assistant feature. These tools provide functionalities for speech recognition and natural language understanding, making it easier to develop voice interaction capabilities.
Expected Benefits:

Improved accessibility: The addition of a Voice Assistant will enable users with visual impairments or motor disabilities to access and interact with the PetMe website more effectively.
Enhanced user experience: Voice-based interactions offer a more intuitive and hands-free experience, allowing users to navigate the website effortlessly.
Inclusivity: By incorporating voice commands, the website will cater to a broader audience, including individuals who prefer voice-based interactions or have difficulty using traditional input methods.

I look forward to implementing this Voice Assistant feature to enhance the PetMe website and make it more accessible and user-friendly.

@aakshitaa

@akshitagupta15june  please assign me to this issue


chore: allow setting oneauth version via env variable when installing

Description
Uses env variable to install a specific version of oneauth or falls back to 1.15.0
Task Item
#minor

Coverage decreased (-0.02%) to 55.837% when pulling 72d358da7d2f168cfebf4df17815517f004064d2 on abrown/electron-oneauth into 0efa350cdb85c32a0f13a84a822e31e46030681a on main.


Clarify fingerprint log messages

I had to look up the source to figure out which side was the old value for a RUSTFLAGS fingerprint mismatch.
Making the logs a bit more explicit about which value is old and new would've helped me.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thank you!
@bors r+

:pushpin: Commit 4538ade2d55d7353cfac8a0ce320e3c4a29bc450 has been approved by Eh2406

:hourglass: Testing commit 4538ade2d55d7353cfac8a0ce320e3c4a29bc450 with merge cf8800a15093f57bb524f03fd22ecbb871ab409b...

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing cf8800a15093f57bb524f03fd22ecbb871ab409b to master...


Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0

Hi
i dont know whats wrong but i am getting this error continuously. Even i tried all with the fresh version also.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
27 actionable tasks: 27 executed
Note: D:\KikleeApp\master2\kikleeapp\android\app\src\debug\java\com\kikleeapp\ReactNativeFlipper.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Unable to install D:\KikleeApp\master2\kikleeapp\android\app\build\outputs\apk\debug\app-debug.apk
com.android.ddmlib.InstallException: INSTALL_FAILED_USER_RESTRICTED
        at com.android.ddmlib.Device.installRemotePackage(Device.java:1133)
        at com.android.ddmlib.Device.installPackage(Device.java:963)
        at com.android.ddmlib.Device.installPackage(Device.java:939)
        at com.android.ddmlib.Device.installPackage(Device.java:928)
        at com.android.builder.testing.ConnectedDevice.installPackage(ConnectedDevice.java:126)
        at com.android.build.gradle.internal.tasks.InstallVariantTask.install(InstallVariantTask.java:175)
        at com.android.build.gradle.internal.tasks.InstallVariantTask.doTaskAction(InstallVariantTask.java:106)
        at com.android.build.gradle.internal.tasks.NonIncrementalTask$taskAction$$inlined$recordTaskAction$1.invoke(AndroidVariantTask.kt:51)
        at com.android.build.gradle.internal.tasks.NonIncrementalTask$taskAction$$inlined$recordTaskAction$1.invoke(AndroidVariantTask.kt:31)
        at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:91)
        at com.android.build.gradle.internal.tasks.NonIncrementalTask.taskAction(NonIncrementalTask.kt:34)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:49)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:42)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:28)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:727)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:694)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$3.run(ExecuteActionsTaskExecuter.java:568)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:402)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:394)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:92)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:553)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:536)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$300(ExecuteActionsTaskExecuter.java:109)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.executeWithPreviousOutputFiles(ExecuteActionsTaskExecuter.java:276)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:265)
        at org.gradle.internal.execution.steps.ExecuteStep.lambda$execute$1(ExecuteStep.java:33)
        at java.util.Optional.orElseGet(Optional.java:267)
        at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:33)
        at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:26)
        at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:67)
        at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:36)
        at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:49)
        at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:34)
        at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:43)
        at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:73)
        at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:54)
        at org.gradle.internal.execution.steps.CatchExceptionStep.execute(CatchExceptionStep.java:34)
        at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:44)
        at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:54)
        at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:38)
        at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:49)
        at org.gradle.internal.execution.steps.CacheStep.executeWithoutCache(CacheStep.java:153)
        at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:67)
        at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:41)
        at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:44)
        at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:33)
        at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:38)
        at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:24)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:92)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:85)
        at java.util.Optional.map(Optional.java:215)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:55)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:39)
        at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:76)
        at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:37)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:36)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:26)
        at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:94)
        at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:49)
        at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:79)
        at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:53)
        at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:74)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.lambda$execute$2(SkipEmptyWorkStep.java:78)
        at java.util.Optional.orElseGet(Optional.java:267)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:78)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:34)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:39)
        at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:40)
        at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:28)
        at org.gradle.internal.execution.impl.DefaultWorkExecutor.execute(DefaultWorkExecutor.java:33)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:192)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:184)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:114)
        at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
        at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:416)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:406)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:102)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
        at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:372)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:359)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:352)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:338)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
        at java.lang.Thread.run(Thread.java:748)

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:installDebug'.
> com.android.builder.testing.api.DeviceException: com.android.ddmlib.InstallException: INSTALL_FAILED_USER_RESTRICTED

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2m 12s

i tried all my procedures like for instance

Fresh installation of android studio
downgrade the jdk version
removing buil, grade folder these things are different. Because i tried this all with a new fresh version also where it giving me the same error.

info Fetching system and libraries information...
System:
OS: Windows 10 10.0.18363
CPU: (4) x64 Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
Memory: 1.43 GB / 5.59 GB
Binaries:
Node: 13.9.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-193.69<IP_ADDRESS>26763
Visual Studio: Not Found
Languages:
Java: 1.8.0_161
Python: 2.7.17
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.2 => 0.63.2
npmGlobalPackages:
react-native: Not Found

info Fetching system and libraries information...
System:
OS: Windows 10 10.0.18363
CPU: (4) x64 Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
Memory: 1.43 GB / 5.59 GB
Binaries:
Node: 13.9.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-193.69<IP_ADDRESS>26763
Visual Studio: Not Found
Languages:
Java: 1.8.0_161
Python: 2.7.17
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.2 => 0.63.2
npmGlobalPackages:
react-native: Not Found

Recent react native version having huge issues with android gradle. still i am finding its solution

Hi @wontone18, I looks like the Flipper version is causing issues.
We have an open PR for it here: https://github.com/facebook/react-native/pull/29787
Could you apply the diff to your project and see if it helps?

I will check the above point. But in my thinking its some where else is the issue. It making all the package components invalid and deprecated. Some of those packages we are regularly using

asyncstorage
webview

etc. gradle is somewhere making all these issues.
I can see several users are facing this issue but nobody getting a better result.

Hi @wontone18, I looks like the Flipper version is causing issues.
We have an open PR for it here: #29787
Could you apply the diff to your project and see if it helps?

Same issue by using your flipper github version.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.3/userguide/command_line_interface.html#sec:command_line_warnings
24 actionable tasks: 24 executed
Note: D:\sourcetest\reactnative\flipper\android\app\src\debug\java\com\mrltestnative\ReactNativeFlipper.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Unable to install D:\sourcetest\reactnative\flipper\android\app\build\outputs\apk\debug\app-debug.apk

Hi at last issue is resolve. There are few things to be check.

check the project structure from android studio (suggestion option and instead of using + in the version put the version no)
npm cache
if debugging from mobile be sure developer mode should be switch off and on. Or else try with another device.
i also deleted my npm_module and fresh install the npm packages but be sure to clean the npm cache.

@wontone18 glad you found a solution.
Currently React Native is not supporting Gradle 7.0, we are using v6.6. Is there any specific reason you need v7 support at this time?

@wontone18 glad you found a solution.
Currently React Native is not supporting Gradle 7.0, we are using v6.6. Is there any specific reason you need v7 support at this time?

nah i am not using gradle 7 at all. React native already having a gradle plugin package in gradle wrapper. which 6 but based on jdk version.

@wontone18 glad you found a solution.
Currently React Native is not supporting Gradle 7.0, we are using v6.6. Is there any specific reason you need v7 support at this time?

nah i am not using gradle 7 at all. React native already having a gradle plugin package in gradle wrapper. which is 6 but based on jdk version.

Has anyone managed to solve this problem? I tried everything I found in this post and others, but without success.

I solved the error creating a new 'react-native init' with the same name of the app, in another folder. Then I deleted the android folder of my app, and pasted the android folder of the new app. Now everything is working again.

@wontone18 glad you found a solution.
Currently React Native is not supporting Gradle 7.0, we are using v6.6. Is there any specific reason you need v7 support at this time?

nah i am not using gradle 7 at all. React native already having a gradle plugin package in gradle wrapper. which is 6 but based on jdk version.

Has anyone managed to solve this problem? I tried everything I found in this post and others, but without success.

I solved the error creating a new 'react-native init' with the same name of the app, in another folder. Then I deleted the android folder of my app, and pasted the android folder of the new app. Now everything is working again.

Hi at last issue is resolve.

Based on the fact that original issue filer seems unblocked, closing this issue.

I ran into the same error while debugging from the phone. The cause was I had manually uploaded and installed my app apk. After deleting the app from the phone, and all was fine after

Do we have a boiler player it fix these incompatible issues for RN setup?

for me the ./greadlew clean worked

I had the same error and fixed it by deleting the \android\app\build\generated\not_namespaced_r_class_sources\debug\r\androidx folder. It was empty and saw something about not being able to delete this folder in the error text.
If that does not work, please try PereiraDiegoMiguel answer.
NOTE: React Native seems to have no problem building with the gradle errors. So expect to look for other errors than just gradle errors. I still get the gradle 7.0 error but it builds fine.

I have the same problem :c

Hello everyone,
Just sharing my experience as I could solve it on my side, so if it can help...
Context:
THIS IS A NEW ERROR. I had not touched RN for a while and I just wanted to create a new project. I got the same error only after running react-native init and react-native run-android.
Solution:

I followed this previous answer on a similar issue
This brings you on the Gradle versions correspondances
I updated the classpath("com.android.tools.build:gradle:X.X.X") in android/build.gradle (it was version 3.5.3, I now use version 4.1.0)
It triggered another error telling me to update gradle from verion 6.2 to 6.5. So, I updated distributionUrl=https\://services.gradle.org/distributions/gradle-6.5-all.zip in android/gradle/wrapper/gradle-wrapper.properties

If you still have other errors that you did not have before, please notice:

You may need to touch /home/$USER/.android/repositories.cfg
You may need to sudo chown $USER:$USER $ANDROID_HOME -R
You may need to update your SDK (use command /opt/android/tools/android update sdk --no-ui --all --filter "android-XX" or something similar and please use an adapted version, currently "android-29")
You may need to accept licences you had not accepted before (use command /opt/android/tools/bin/sdkmanager --licenses)

I hope it could help as I know it is not pleasant to just try to start a project needing to fix things.

Still have the same issue with fresh project. Anyone solve this issue ?
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 967 file(s) to forward-jetify. Using 4 workers...
info JS server already running.
info Installing the app...

Task :app:compileDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
14 actionable tasks: 3 executed, 11 up-to-date
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Could not find tools.jar. Please check that /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home contains a valid JDK installation.

"react": "16.13.1",
"react-native": "0.63.4"
gradle-wrapper: distributionUrl=https\://services.gradle.org/distributions/gradle-6.2-all.zip
classpath("com.android.tools.build:gradle:3.5.3")

Still have the same issue with fresh project. Anyone solve this issue ?
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 967 file(s) to forward-jetify. Using 4 workers...
info JS server already running.
info Installing the app...

Task :app:compileDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
14 actionable tasks: 3 executed, 11 up-to-date
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Could not find tools.jar. Please check that /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home contains a valid JDK installation.

"react": "16.13.1",
"react-native": "0.63.4"
gradle-wrapper: distributionUrl=https\://services.gradle.org/distributions/gradle-6.2-all.zip
classpath("com.android.tools.build:gradle:3.5.3")

@Abdalmajid
I came across this issue today while running a native react app on android emulator from terminal
Quick checks:

In your terminal type echo $path to see whether gradle is in your environment file this is where your environment variable are for your programs.

If its not in there run brew install gradle

If all went well you will get following or similar output in your terminal

Welcome to Gradle 6.7.1!
Here are the highlights of this release:

File system watching is ready for production use
Declare the version of Java your build requires
Java 15 support

Now your environment variable knows about gradle when you run your project your build should be successful!
If you get further errors you may need other dependencies to build or run your project.

@Abdalmajid
I came across this issue today while running a native react app on android emulator from terminal
Quick checks:

In your terminal type echo $path to see whether gradle is in your environment file this is where your environment variable are for your programs.

If its not in there run brew install gradle

If all went well you will get following or similar output in your terminal

Welcome to Gradle 6.7.1!
Here are the highlights of this release:

File system watching is ready for production use
Declare the version of Java your build requires
Java 15 support

Now your environment variable knows about gradle when you run your project your build should be successful!
If you get further errors you may need other dependencies to build or run your project.

@Abdalmajid
I came across this issue today while running a native react app on android emulator from terminal
Quick checks:

In your terminal type echo $path to see whether gradle is in your environment file this is where your environment variable are for your programs.
If its not in there run brew install gradle
If all went well you will get following or similar output in your terminal

Welcome to Gradle 6.7.1!
Here are the highlights of this release:

File system watching is ready for production use
Declare the version of Java your build requires
Java 15 support

Now your environment variable knows about gradle when you run your project your build should be successful!
If you get further errors you may need other dependencies to build or run your project.

Finally it works for me when I do this after doing @CanYouHearTheEcho 's answer

@Abdalmajid
I came across this issue today while running a native react app on android emulator from terminal
Quick checks:

In your terminal type echo $path to see whether gradle is in your environment file this is where your environment variable are for your programs.
If its not in there run brew install gradle
If all went well you will get following or similar output in your terminal

Welcome to Gradle 6.7.1!
Here are the highlights of this release:

File system watching is ready for production use
Declare the version of Java your build requires
Java 15 support

Now your environment variable knows about gradle when you run your project your build should be successful!
If you get further errors you may need other dependencies to build or run your project.

Finally it works for me when I do this after doing @CanYouHearTheEcho 's answer

Try to choose other gradle versions in https://services.gradle.org/distributions/

I fixed updating 'build.grade' from:
classpath("com.android.tools.build:gradle:3.5.3")
to
classpath("com.android.tools.build:gradle:3.5.4")
See more info in: https://developer.android.com/studio/releases/gradle-plugin#4-0-0

I fixed this by updating 'gradle-wrapper.properties' dirstributionUrl from:
distributionUrl=https\://services.gradle.org/distributions/gradle-6.2-all.zip
to
distributionUrl=https\://services.gradle.org/distributions/gradle-6.3-all.zip
and then running
cd android && ./gradlew clean && cd ../
Finally I uninstalled the old app and then reinstalled by react-native run-android

For my case this fix helped me.
I had the build failure after I tried to remove error due to async-storage.

This is sort of nuts. I can't even get the minimum install working because of this gradle 7.0 version thing. Flutter works like a charm. I may use that

我固定它从更新“build.grade”：
classpath("com.android.tools.build:gradle:3.5.3")
以
classpath("com.android.tools.build:gradle:3.5.4")
在以下位置查看更多信息：https : //developer.android.com/studio/releases/gradle-plugin#4-0-0

This works for me, Thx

I fixed it updating 'build.grade' from:
classpath("com.android.tools.build:gradle:3.5.3")
to
classpath("com.android.tools.build:gradle:3.5.4")
See more info in: https://developer.android.com/studio/releases/gradle-plugin#4-0-0

This works for me, Thx

the problem for me was I had apply plugin: 'com.google.gms.google-services' inside android/app/build.gradle
which is making this error: Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0
because I already have classpath 'com.google.gms:google-services:4.3.5' inside android/build.gradle.
I just commented apply plugin: 'com.google.gms.google-services' and it worked for me.
Maybe any of you have the same situation as me.
Hope this can help.

Hi, everyone!
what is the main reason for this error?

"incompatible with Gradle 7.0" error appears out of nowhere anytime.
I copy one project to another directory.
Originally it works well.
And then when I installed the React-Native-OpenCV module, there appears an error.
I removed the npm node module and clean the cache, then reinstall the npm module.
And the above error appears.
I am not sure what is happening behind the scene.
Can anyone explain the reason of this error?
And how to fix these kinds of errors?

I have the same problem. Any reason to explain this error?

I recently encountered this with an error related to Firebase:
RNPushNotification.java:37: error: cannot find symbol
import com.google.firebase.iid.FirebaseInstanceId;
And this solution worked for me. (adding firebaseMessagingVersion = "21.1.0" to ext {...})

I got this error as well today: "Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0."
It looks like it complains about bunch of libraries such as: react-native-async-storage_async-storage, react-native-gesture-handler,  react-native-webview, react-native-screens, react-native-firebase_app.
Any updates about this issue?

I got this error as well today: "Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0."
It looks like it complains about bunch of libraries such as: react-native-async-storage_async-storage, react-native-gesture-handler, react-native-webview, react-native-screens, react-native-firebase_app.
Any updates about this issue?

I have the same problem too

Hi at last issue is resolve. There are few things to be check.

check the project structure from android studio (suggestion option and instead of using + in the version put the version no)
npm cache
if debugging from mobile be sure developer mode should be switch off and on. Or else try with another device.
i also deleted my npm_module and fresh install the npm packages but be sure to clean the npm cache.

its not working

Reopening since RN still doesn’t work with Gradle 7 it seems. A workaround to downgrade to Gradle 6 is helpful but not long term feasible.

Most of the issues I see reported in this thread seem unrelated to actual Gradle 7 upgrade. The actual warning (from the issue title) is from Gradle 6, notifying that some things WILL break with the upgrade.
It is a bit misleading step from the Gradle side, but should not be a cause of the build failure.

Even after downgrading Gradle on my system, I still have the same issue. Anyone else?

I still have the issue, and it's caused by unimodules-core (the dependency of react-native-unimodules)
> Task :unimodules-core:compileDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warnings
420 actionable tasks: 420 executed

And my react native is 0.63.4, "react-native-unimodules" is "~0.13.3". My project is ejected from Expo.

Same here. react native cli builds good without uni module android confuguration. Once I apply the changes from https://docs.expo.io/bare/installing-unimodules/. Build break with message
Task :app:processDebugResources FAILED
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugResources'.

A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
Android resource linking failed
\app\node_modules\expo-file-system\android\build\intermediates\library_manifest\debug\AndroidManifest.xml:16:5-22:15: AAPT: error: unexpected element  found in .

And I am using react native version 0.63.2.

I still have the issue, and it's caused by unimodules-core (the dependency of react-native-unimodules)
> Task :unimodules-core:compileDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warnings
420 actionable tasks: 420 executed

And my react native is 0.63.4, "react-native-unimodules" is "~0.13.3", and my @unimodules/core is 7.1.0. My project is ejected from Expo.

An update on my issue, I added org.gradle.java.home in gradle.properties to point to my correct jdk location, then run expo run:android or npm run android, it suddenly works.

Experienced the same issue, while migrating RN from 0.62.2 to 0.63.4
Used Gradle setup:
distributionUrl=https\://services.gradle.org/distributions/gradle-6.2-all.zip
classpath 'com.android.tools.build:gradle:3.5.3'
Initial Steps:
On Mac terminal, ./gradlew clean - was not helpful
On Android Studio, invalidate cache & restart - was not helpful
Next Steps :
While doing Gradle sync in android studio, found out that android studio is configured to wrong jdk location (Applications/Android Studio.app/Contents/jre/jdk/Contents/Home). JDK location is changed as per ./bash_profile JAVA_HOME='/Library/Java/JavaVirtualMachines/jdk1.8.0_191.jdk/Contents/Home'. point to be noted - Different JDK location for Different process might cause gradle to spawn multiple deamons
Moreover, after taking the stacktrace for react-native run-android --variant=release--stacktrace, found out that some junks were added unexpectedly at android/app/src/main/res/raw/* which throws Error: Duplicate resources, Those are trashed.
Then, cleanup of junks at all levels of cache (Project, User/username/.gradle, /var/root/.gradle) is done
Then, now able to generate the release mode build. Issue is fixed
Note - Weird thing here is no issue on debug mode build
Thanks

After a long time dealing with this, I got it by trying all Gradle distributions from top to bottom until one of them works. In my case it has been 6.9.
After changing the following line:
distributionUrl=https\://services.gradle.org/distributions/gradle-6.9-all.zip in android/gradle/wrapper/gradle-wrapper.properties

Only needed to change the version number.

I ran the following command:
cd android && ./gradlew clean
I hope this helps!

what worked for me was after initing up new react native project I have cleared android folder and created fresh new android app in android studio. Pasted that app inside the empty android folder and run-android worked

@RickameCua  ya its working this tips for my project

I believe we can close this as the upcoming version of RN will run on Gradle 7.3.3. Is there anything else to be done here?

Try this solution worked for me.
If you have another app with the same name (or package name) on the device: Rename the app or delete it from your device.

I am still having this issue - not a signle solution worked for me. :(
`> Task :app:processDebugGoogleServices FAILED
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.`

I solved the error creating a new 'react-native init' with the same name of the app, in another folder. Then I deleted the android folder of my app, and pasted the android folder of the new app. Now everything is working again.

Awesome! It works well on my end. Thank you so much.

Unfortunately, it was a good experience using react native to develop mobile apps but I found my self wasting a lot of time just solving issue after issue, it's been more than 1 week now of headaches with those errors. I hope RN team work on this side and try to solve those problems


modifying the upgradation config file validations

Integrating upgradation validation scripts.
upgradation_validate.sh
aws_s3_upgradation_validate.sh
local_storage_upgradation_validate.sh
azure_storage_upgradation_validate.sh


Investigate current setup of iOS UI tests

Do we need to run them on AWS Device farm?
Do we update the iOS version or disable old iOS versions?
Is the output of the tests on CI right now actually used?

Notes on the how & why of iOS UI Tests, specifically designed for automated testing on AWS Device Farm:
https://github.com/maplibre/maplibre-gl-native/issues/39

They run fine in the simulator and are running on CI now.
https://github.com/maplibre/maplibre-native/blob/c1ba70ec00367f29f448f78d338263ef4f35616f/.github/workflows/ios-ci.yml#L140


2D and 3D printing pages

updated the designs of the 2D and 3D printing pages
3d printing:

2d printing:

How to test

run frontend, backend and mongodb
sign in as a user with at least member priviledge
navigate to the 2d and 3d printing pages with expected visuals above

@jessabelledelen
Hi! Earlier in the semester, I showed my designs to Allen and Andrew and we agreed that the drop-downs would be easier to implement currently. If you still want to do the buttons, I can change the code. I chose to go with the URL for the .stl file versus a file upload since the backend currently isn't set up to support file uploads.
I'll fix the other issues! :)


please allow a filter on not installed extensions too

Issue Type: Feature Request
now you can only filter on the installed ones , but the inverse woul be much more interesting , especially in combo with publisher
VS Code version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:13:11.295Z)
OS version: Windows_NT x64 10.0.20197

@t2kx Can you please explain more about what filters you are talking about?

@t2kx Can you please explain more about what filters you are talking about?

in the extension blade/side bar one can filter on the extensions

please add a filter to also only select the NOT INSTALLED extensions too, e.g. let's say for instance you want to install all extensions by a certain publisher Microsoft. if this publisher has 200 extensions then i'm not interested in the ones I have already installed. I then want to FILTER on the NOT INSTALLED ones, minimizing the list.

I think this would be handy, I Found this issue by trying to filter by: @popular !@installed


iframe "edit in Compile Explorer" button is not working

The buttons opens default page with Compile Explorer and not my code. Probably issue with new url shortener. The link is just "https://compiler-explorer.com/#version:4". There is no information in the link.

Hi @hanickadot, great catch! It's a bit embarassing that I did not check the link before releasing the new shortener stuff.
I'll try to see if it can be fixed. Thanks for the report :)

Also, note that compiler-explorer.com isn't properly set up yet (my fault!) -- will fix... did you hit compiler-explorer.com for the original link?

Yep, it's from compiler-explorer.com I think :)

Thanks Hana, I didn't realise people were using that! I'll fix that (but I don't think that';s the cause of this bug)

Turns out, it was working when we first released the short links! But I broke it when implementing the dynamic url changes!
Thanks again! :D


Update README.md as a makeshift

Fixes #103
Updated README as a makeshift to clarify that when you declare TaskCompletionSource, you need to specify what Generics type the declaring Task handles when calling create(), just like Task.<Object>create();

Thanks for helping us keep our documentation up to date! This syntax actually changed with #84 and should be either of the following:
TaskCompletionSource<Void> tcs = Task.create();
TaskCompletionSource<Void> tcs = new TaskCompletionSource<>();

@grantland Oops! Sorry I missed that part.. I'll revise my PR to write both syntax on the doc.

Oh sorry I wrote that I'll revise my previous PR, but I now thought I should not; I think the explanation about other APIs should to be updated as well if the README tells the up-to-date way of TaskCompletionSource declaration. Since I am not confident enough to say that I'm aware of all the changes and I can revise the whole API information, I am not sure only revising this part is right. Can I have your opinion as well @grantland ?

Sorry, but I'm not sure I'm following what you're trying to say.

I think the whole documentation has to be revised and up-to-date; not just the section of TaskCompletionSource, so I'll close this PR.