[TEST] Add base image from gitlab

Status
In Hold (Used to help gitlab ci with images - testing)

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>50
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>50

Docker Metadata

Image Size: 251.60 MB

Image ID: sha256:6e1de976d0b3715535cb348cdfa67b5c7ad444f4d02ff403acd7863d05e11ebf

Created: 2020-08-30T15:07:25.648546296Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>50

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:1d60c2a08f25c0b0fdbaabf23d09c756eafaac18
org.opencontainers.image.version:<IP_ADDRESS>50

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>51
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>51

Docker Metadata

Image Size: 251.91 MB

Image ID: sha256:109d53665a220090c55e76cda81ed9c905ad0972dfa4725224c07c2b6663a3e3

Created: 2020-08-30T15:48:29.046644284Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>51

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:6fee6da9dec134ff29ced51014a50076bb16debf
org.opencontainers.image.version:<IP_ADDRESS>51

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>52
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>52

Docker Metadata

Image Size: 298.43 MB

Image ID: sha256:e1c1aa7057638b52db56d317d8ee067fd0956a09dd5e60b98f8c3037a9f22421

Created: 2020-08-30T16:09:32.424933893Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>52

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:37a332434b934ea7ce217e05ac0439a93eff82f7
org.opencontainers.image.version:<IP_ADDRESS>52

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>82
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>82

Docker Metadata

Image Size: 298.44 MB

Image ID: sha256:63ef437fd976b7b34f0faa3811c6a4b757f1f9a2cbaf6a66061200c2f1d3037c

Created: 2020-09-01T15:22:31.468671282Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>82

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:6dd63724510016b390b250118a81d1240a6453ef
org.opencontainers.image.version:<IP_ADDRESS>82

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>28
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>28

Docker Metadata

Image Size: 302.52 MB

Image ID: sha256:142957745f935c98e03020fc945f5f699ada989e5adb48a8cd7ad21cd9f05221

Created: 2020-09-06T13:36:31.62681844Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>28

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:63b570037d4d3a873536fe4ba320e038e0bb0bdd
org.opencontainers.image.version:<IP_ADDRESS>28

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>42
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>42

Docker Metadata

Image Size: 332.32 MB

Image ID: sha256:932179a40207e31aa2b17a28c4a9152447b234af43d21e2c3dbb93dc48fed9fb

Created: 2020-09-08T09:15:08.211305019Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>42

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:f11a96a04daf23c4c2a2a3b87581f23a930987a7
org.opencontainers.image.version:<IP_ADDRESS>42

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>44
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>44

Docker Metadata

Image Size: 332.32 MB

Image ID: sha256:36f32fba7cd23deb7bb4d0571f2777c4b130701accd017451863954ec9d53071

Created: 2020-09-08T09:36:50.766042072Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>44

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:9bf31b5e177702f890f69f37aebdf618fa63a3b3
org.opencontainers.image.version:<IP_ADDRESS>44

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>80
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>80

Docker Metadata

Image Size: 561.01 MB

Image ID: sha256:63d0132c11f5ccaf94c3c5b00f5ad1732b2111f7a3f5ef709274a0ea57f0cfb9

Created: 2020-09-10T12:23:46.627621465Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>80

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:179f8ec5a493c8cf9c0af7e4f94c0c4db446cd5d
org.opencontainers.image.version:<IP_ADDRESS>80

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>93
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>93

Docker Metadata

Image Size: 561.01 MB

Image ID: sha256:baf9f9b8d6e36022dad6600fda949e7603885d624c5ebb28ee4c5b2ae0a7ea07

Created: 2020-09-10T13:57:32.320002941Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>93

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:7f528588f09506789f671fc5e8d31b1932050da9
org.opencontainers.image.version:<IP_ADDRESS>93

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>68
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>68

Docker Metadata

Image Size: 562.42 MB

Image ID: sha256:05d7a401c2bee6e969e10812a9c36ae695c6357951d0b0a0b20770f0ed8e2607

Created: 2020-09-15T15:53:23.037073788Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>68

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:4a0e97f4b751d6954c00aed6bc4581d5bf7a8f4b
org.opencontainers.image.version:<IP_ADDRESS>68

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>77
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>77

Docker Metadata

Image Size: 562.42 MB

Image ID: sha256:85123cb0c5990a36543245dd5f2706ed6afaf6338bfc9b0295ad6403243986d8

Created: 2020-09-16T08:02:20.879826321Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>77

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:f98538a0311a5132ffa7fc2a0320655a46f3d888
org.opencontainers.image.version:<IP_ADDRESS>77

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>89
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>89

Docker Metadata

Image Size: 562.43 MB

Image ID: sha256:8c065595e61eb2a6bccac99d3b79370e10ab96c593a7abc9fc15cd58e18b7c8e

Created: 2020-09-23T10:38:12.516688833Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>89

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:341ef0282eb8b7c140419941ebade0aeab08cbd1
org.opencontainers.image.version:<IP_ADDRESS>89

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>31
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>31

Docker Metadata

Image Size: 803.39 MB

Image ID: sha256:ae997b108a565d32139ca0d916d9a33a70b1d5e5f75449682e33a48dc806d570

Created: 2020-09-24T16:47:41.426651076Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>31

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:1e28cfa6f9a533de7cf0b803070542b391d6835e
org.opencontainers.image.version:<IP_ADDRESS>31

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>05
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>05

Docker Metadata

Image Size: 910.99 MB

Image ID: sha256:3395db543e6e1374c109f795c54cb922380ef7d252aedf937e687a59d464be65

Created: 2020-09-29T12:16:55.314284904Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>05

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:60b2445ed6fa82b463b0ccc332a191c85b1de134
org.opencontainers.image.version:<IP_ADDRESS>05

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>07
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>07

Docker Metadata

Image Size: 924.64 MB

Image ID: sha256:4193c04b09da7de77f9016b918073a5c43cbc06d811797cbb4852ce440057e2b

Created: 2020-09-29T12:48:18.380272312Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>07

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:e666706d54482c7fd4ed68a2d0f7e9eb189ce74d
org.opencontainers.image.version:<IP_ADDRESS>07

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>43
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>43

Docker Metadata

Image Size: 924.63 MB

Image ID: sha256:1fe1293dc55456306c75aea58312c19a160b4f2f76c3eba0fd0824e75bd2d957

Created: 2020-09-29T15:12:15.834731212Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>43

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:44c0f3192cecfad025a8eb6fa853cfc68370c7cf
org.opencontainers.image.version:<IP_ADDRESS>43

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>84
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>84

Docker Metadata

Image Size: 925.39 MB

Image ID: sha256:478e7d0927b6751ee09cdac9f512ec6c550996a381afef53e55f7ecea6ef1204

Created: 2020-10-12T11:15:42.794136799Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>84

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:ae21f2624f19db91b311a5b0d3e57e30bbccc1ec
org.opencontainers.image.version:<IP_ADDRESS>84

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>73
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>73

Docker Metadata

Image Size: 1029.83 MB

Image ID: sha256:de42e734f5d93cf4b8319e9d58aad24da9c3d5d282fe92b5fbc1129f1109620a

Created: 2020-10-19T14:10:58.449749678Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>73

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:1753676a839efc5a37d8f2e9629d5b7a38ddaf4c
org.opencontainers.image.version:<IP_ADDRESS>73

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/test-gitlab-ci:<IP_ADDRESS>82
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/test-gitlab-ci/tags
Get started by pulling the image:
docker pull devdemisto/test-gitlab-ci:<IP_ADDRESS>82

Docker Metadata

Image Size: 929.42 MB

Image ID: sha256:209ff606f917b8caeb91615c8afc2abcbfaad1b2e5e3aece96c945e145a9a9a9

Created: 2020-10-19T15:05:27.953997405Z

Arch: linux/amd64

Command: ["/bin/sh","-c","/bin/bash"]

Environment:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DOCKER_IMAGE=devdemisto/test-gitlab-ci:<IP_ADDRESS>82

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:981066373793a1168dbdc70f30be238457839900
org.opencontainers.image.version:<IP_ADDRESS>82

@agamm can we close this?

@agamm can we close this?

Not at all atm, we are using this as the base image for the gitlab-ci.
We could start a migration to a more production ready docker image if it is urgent from your side.

Change the name of the image (without test) and add secondly=true to build.conf and we can then merge.

Close this if https://github.com/demisto/dockerfiles/pull/3301 merged.


sporadic tests failures in SkillApprovalSpecs

Error:  Failures:
Error:    SkillApprovalSpecs.apply existing approval requests if the skill's self approval type to be 'HonorSystem':729 Condition not satisfied:

performedAfter == [ "TestProject1-skill2_user1", "TestProject1-skill2_user2", ]
|              |
|              false
[TestProject1-skill2_user2, TestProject1-skill2_user1]

PR: #817


feat: create oscd action icon component

closes #1

npm run build is adding the test and stories folder to the distribution. these should be excluded.
you can change it in the "files" section in config.json.

Couple of more general questions:

Why is there a tooltip that's showing the same value as the label?
If the tooltip is still needed, would it be nice to add a flag to optionally hide the tooltip?
Would it be nice to add a size attribute ? type Size = 'small' | 'medium' | 'large' | undefined. by default it's medium

The build doesn't work.
oscd-action-icon is depending on v0.22 of mwc-icon.
open-scd-core is depending on v0.27 of mwc-icon.

npm run build is adding the test and stories folder to the distribution. these should be excluded. you can change it in the "files" section in config.json.

Could you show me how this can be done properly? I can't exclude stories and run storybook

Couple of more general questions:

Why is there a tooltip that's showing the same value as the label?
If the tooltip is still needed, would it be nice to add a flag to optionally hide the tooltip?
Would it be nice to add a size attribute ? type Size = 'small' | 'medium' | 'large' | undefined. by default it's medium

I've put these suggestion in a new issue: #3

npm run build is adding the test and stories folder to the distribution. these should be excluded. you can change it in the "files" section in config.json.

Could you show me how this can be done properly? I can't exclude stories and run storybook

You're facing the issue that when you add the "include" section in your tsconfig.json, your npm test and npm run storybook doesn't work anymore. If you look at those npm scripts, you can see they both start with tsc. If you create a new tsconfig.json that extends from the current tsconfig.json, but overrides the "include" section, you can add this tsconfig.test.json as a flag to tsc.


[Accessibility]A11y_VSCode_ColorTheme_keyboard: after clicking on "Tab" key the opened "Screeen" get closed

Environment Details:
VSCode Version : 1.24.1
OS Version : Win10
Additional Details:
Keyboard, MAS2.1.1
Repro Steps:
1.Navigate to Settings icon in Activity Bar->Press Enter->Select "Color Theme" from dropdown.
2.Navigation through TAB
Actual:
after clicking on "Tab" key the opened "Screen" get closed
Expected:
after clicking on "Tab" key the opened "Screen"  should not be closed
Recommendations:
Refer below link which is repository of bug fixes code snippets:
[https://microsoft.sharepoint.com/teams/msenable/mas/Pages/browse-fixes.aspx
](url)
User`] Impact:
Colorblind and low vision user will not identify the screen content and controls.
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={a4bbd37d-ee11-485e-b5c8-0539f0ac94b2}

Attachment for Reference:
A11y_VSCode_ColorTheme_keyboard.pptx
[A11y_VSCode_ColorTheme_keyboard.pptx]
Does this issue occur when all extensions are disabled?: Yes

The root cause of this is with the "Quick pick" control that opens when you choose "Color Theme". The same control is shown in many different scenarios, so I'm going to close all but one instance of this problem.
(https://github.com/Microsoft/vscode/issues/51854)


Make configuration and dependency injection container immutable

Q
A

Type
feature

BC Break
yes

Fixed issues
-

Summary
This PR makes the configuration and dependency injection container immutable. (frozen state)
This avoids having other services hacking into the DI container or config object at runtime (avoiding inconsistent retrieval of services

This avoids having other services hacking into the DI container or config object at runtime (avoiding inconsistent retrieval of services).

This would look very nice as the body of your commit message, it doesn't have to be only in a PR on your fork

I wanted to have a more clean diff (for my self...)
I'm waiting for the main PR to be merged, and then will continue/start making pr on the main repo...
Did not find a better way to have a clear diff... I can understand that might be confusing for other people... Do not have better ideas for now except of waiting

What you did is the best way to get that diff IMO 👍 I wasn't questioning that at all. I'm just suggesting you use git commit --amend, then write
Make configuration and dependency injection container immutable

This avoids having other services hacking into the DI container or
config object at runtime (avoiding inconsistent retrieval of services

in your editor, and then forc epush. If you do that, the body of the commit message will be reused as the body of the PR you will create after the main PR is merged.

Aaaaaaaaa. Right! Will do! That's a good idea
On Sun, 27 Oct 2019, 11:20 Grégoire Paris<EMAIL_ADDRESS>wrote:

What you did is the best way to get that diff IMO 👍 I wasn't questioning
that at all. I'm just suggesting you use git commit --amend, then write
Make configuration and dependency injection container immutable
This avoids having other services hacking into the DI container or
config object at runtime (avoiding inconsistent retrieval of services
in your editor, and then forc epush. If you do that, the body of the
commit message will be reused as the body of the PR you will create after
the main PR is merged.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/goetas/migrations/pull/3?email_source=notifications&email_token=AAF5UJZNLWS7RCOOVVIUK5LQQVFMNA5CNFSM4JFQTRJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECKZ4RQ#issuecomment-546676294,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAF5UJ7UHHD2IYXEAUUZASDQQVFMNANCNFSM4JFQTRJQ
.

Moving to https://github.com/doctrine/migrations/pull/876
@greg0ire I have applied the reviews you have suggested


Extremely long error URLs that sometimes don't lead to anything

Sometimes I get really long error URLs in my Karma tests, like the one pasted below.
Try clicking on it, the only thing you'll get is:
Failed to instantiate module {0} due to:
{1}

that doesn't say a lot.
http://errors.angularjs.org/1.2.10/$injector/modulerr?p0=test%2Fmocks-inlined%2Flanguage-tags.json&p1=[%24injector%3Anomod] http%3A%2F%2Ferrors.angularjs.org%2F1.2.10%2F%24injector%2Fnomod%3Fp0%3Dtest%252Fmocks-inlined%252Flanguage-tags.json
x%2F<%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fdist%2Fbc6337f5.vendor.js%3F1391195095000%3A92
Vc%2Fb.module<%2F<%2Fb[e]<%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fdist%2Fbc6337f5.vendor.js%3F1391195095000%3A106
Vc%2Fb.module<%2F<%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fdist%2Fbc6337f5.vendor.js%3F1391195095000%3A106
e%2F<%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fdist%2Fbc6337f5.vendor.js%3F1391195095000%3A115
q%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fdist%2Fbc6337f5.vendor.js%3F1391195095000%3A93
e%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fdist%2Fbc6337f5.vendor.js%3F1391195095000%3A115
%24b%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fdist%2Fbc6337f5.vendor.js%3F1391195095000%3A118
workFn%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Ftest%2Funit%2Fvendor%2Fangular-mocks.js%3F1391195050000%3A2144
jasmine.Block.prototype.execute%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A1145
jasmine.Queue.prototype.next_%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2177
jasmine.Queue.prototype.start%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2130
jasmine.Spec.prototype.execute%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2458
jasmine.Queue.prototype.next_%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2177
jasmine.Queue.prototype.start%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2130
jasmine.Suite.prototype.execute%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2604
jasmine.Queue.prototype.next_%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2177
jasmine.Queue.prototype.start%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2130
jasmine.Suite.prototype.execute%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2604
jasmine.Queue.prototype.next_%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2177
jasmine.Queue.prototype.next_%2FonComplete%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2173
jasmine.Suite.prototype.finish%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2561
jasmine.Suite.prototype.execute%2F<%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2605
jasmine.Queue.prototype.next_%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2187
jasmine.Queue.prototype.next_%2FonComplete%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2173
jasmine.Spec.prototype.finish%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2432
jasmine.Spec.prototype.execute%2F<%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2459
jasmine.Queue.prototype.next_%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2187
jasmine.Queue.prototype.next_%2FonComplete%2F<%40http%3A%2F%2Flocalhost%3A8080%2Fbase%2Fnode_modules%2Fkarma-jasmine%2Flib%2Fjasmine.js%3F1374365571000%3A2167

I've just got a 374 thousand bytes long URL. :-) Such things are able to crash the browser.
It'd be good to pinpoint the issue but, in the meantime a hard limit on the length of the URL might help; this long URLs are not helpful anyway.
This was Angular 1.3.14, I'll check with 1.4 later.

How do I stop the noise in my testing console?  It's extremely irritating.

I agree, is there a way to switch to normal error reporting?
In the Chrome developer tools, this results in entirely useless error messages since the console cuts off long lines:

Is this still affecting chrome 45/46? I recall some cls landing which read like they would have addressed this issue, so i just assumed this had been resolved. Can you still reproduce this with Canary?

Version 46.0.2471.0 canary (64-bit)

Whilst this may not (or may be) still an issue in Chrome, it certainly is when running automated tests -- so much so that I imagine I am missing some flag that might produce errors that are not a hundred lines of URL-encoded URLs....

any recommended solutions for while in test?
IMO there should be an option to truncate urls in stack traces

Duplicate of #14744 and the the url length will be configurable (and capped by default) in the future: #15707


Match subscription to event on resource

Description

Ensuring lower case on resourcefilter. Will ensure lower case on events in later issue.

Related Issue(s)

#370

Verification

[x] Your code builds clean without any errors or warnings
[x] Manual testing done (required)
[x] Relevant automated test added (if you find this hard, leave it and we'll help out)
[ ] All tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Can confirm that this PR looks like it will address the issue we have escalated for OED.

Just curious, what was the argument for including "altinn" in the last part of this urn:
urn:altinn:resource:altinnapp.ttd.endring-av-navn-v2 vs
urn:altinn:resource:app.ttd.endring-av-navn-v2 or urn:altinn:resource:app:ttd.endring-av-navn-v2


Promises yes now, generators no

Generators require yield language support and * functions. But promises are just a nice bit of code, no new language


update example scripts

All the example scripts have to be adapted to the new changes.

Done as of #108 (e958ad145d89352aba88c2dbc7006bc3f7987d45).


Fluentd log delay on specific type of messages

What happened:
Hello Team,
We are getting strage issues where only specific type of messages are getting delayed by substantial amount of time like 30+ minutes.
Those messages are coming out of application only so looks like fluentd getting some issue processing these kinds of messages as its not correctly formed JSON. But eventually these events reach splunk.
The event looks like
2020-04-22 14:02:14.463109036 +0000 UTC m=+1830615.559689447 write error: Write timeout "{"level":"info","ts":"2020-04-22T14:02:14.463Z","msg":"Health: Retrying the health for the dependency hsmwrapper in case of error.","hostname":"ovk8hsmwrap-dev-epic-25-7-sy4io-58fcd958d-7jrqj","pid":"1","app":"HSM_Wrapper","version":"v0.1"}\n"
What you expected to happen:
We expect these events to reach Splunk on acceptable time like other events. we have validated no pressure on resources during the same time.
Anything else we need to know?:
Environment:
Kubernetes version (use kubectl version):v1.14.8
Ruby version (use ruby --version):
OS (e.g: cat /etc/os-release): CentOS 7.7
Splunk version: 7.x
Others:

Hey @dengalebr,
Do these events have any filters applied? A write timeout is interesting...how big is the event?

Hey Matt,
we have only one additional filter which is concat for multi line, but this is no different than other events.
The event  is just like above, Application continuously printing similar events but those are without write timeout and no issues for those.
Problematic event:
2020-04-22 14:02:14.463109036 +0000 UTC m=+1830615.559689447 write error: Write timeout "{"level":"info","ts":"2020-04-22T14:02:14.463Z","msg":"Health: Retrying the health for the dependency hsmwrapper in case of error.","hostname":"ovk8hsmwrap-dev-epic-25-7-sy4io-58fcd958d-7jrqj","pid":"1","app":"HSM_Wrapper","version":"v0.1"}\n"
Working event:
{"level":"info","ts":"2020-05-02T14:51:26.679Z","msg":"Health: Retrying the health for the dependency hsmwrapper in case of error.","hostname":"ovk8hsmwrap-dev-epic-25-7-sy4io-58fcd958d-42hx5","pid":"1","app":"HSM_Wrapper","version":"v0.1"}
I think there are few exceptions happening within fluentd output, Most of the other delayed messages as well some similar pattern.
Any idea, how we can drill further?
Regards,
Bala

Yes I would be drilling into the fluentd pod logs for the node this app is on and looking for any errors  in concat or processing that would cause it to be dropped.

Hey Matt,
This is the issue as I dont see any warning / error in fluentd pod, I see similar pattern with few other messages as well. Question is if its getting dropped how come eventually sent after 30/45 minutes? why only that event take long and event before / after reach on time.

Hey Bala, Its not being dropped, sounds like its either stuck in buffer or concat, etc/

hey Bala, I have a hunch. I think its because of retry timer and exponential back off. will ping you to explain.

Hey Bala, one more find for you that may explain any remaining delays. Can you please update your concat filters to use flush_interval 2 NOT flush_interval 2s
https://github.com/splunk/splunk-connect-for-kubernetes/issues/385#issuecomment-629888443

Ahhhh, Let me try this. I will keep you posted

@dengalebr Hello, were you able to resolve it?

@rockb1017 we reduced the delay with fluentd flush interval 2, but we could not resolved it completely.
We still see events delayed by hours during high traffic. In our environments we have spikes of 50k events/Sec from few applications, so delay is still ongoing issue for us.
We are working with @matthewmodestino for this challenge.

oh. thanks for the update.
on the cases of that much load, delay is due to throughput limit of fluentd. Fluentd is known to hit the ceiling around 3k eps. @matthewmodestino has a Universal Forwarder solution that can handle much better throughput.

Is there any docs which can be referred for limitations around 3k EPS? Fluentd limits are much higher and we do not have consistent load like this, this happen mostly 2/3 times in hour.
We know we are hitting limits but exploring how efficiently we process the buffer fine tuning.

https://docs.fluentd.org/deployment/performance-tuning-single-process
The exact eps depends on many factors, mostly filtering etc.
We are looking at options to make UF more k8s friendly at the node agent level for instances like this where the logging velocity is so high that you need a real deal enterprise grade collector ;)

Thanks Matt.
We are looking forward for UF.
What should be recommendations for multi-worker and thread count when volume grows in fluentd. It's good to get the standards for those fluentd settings. Also they way you published buffer parameters what should be max CPU and Memory resources we should keep. Fluentd pod always on high CPU and Memory.

Hey Bala! We have not recommended multi-proc at all as we did not see much benefit or improvement.
Generally, sharing has been easier and more successful.
The fluentd pod can only use one core, so we suggest you give it to it, and usually on a loaded cluster I see about 1GB of Mem...
Hard to say exactly is best, as clusters differ, but Id recommend 1 core and 1GB of ram.
What are you seeing for usage?

Hey @dengalebr have you see the OTel log engine numbers?
https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/advanced-configuration.md#performance-of-native-opentelemetry-logs-collection
Would suggest checking this out!

Hey @dengalebr , any updates on this ?

Closing this issue . Feel free to re-open it ,if you face the same issue again .


Fauxton only works on "/" route..

If you try and say setup an express route like '/db',
then go to  '/db/_utils' you get a totally broken webpage, adding an extra '/' eg.  '/db/_utils/', partly gets you there.  But then you get console errors because the fauxton interface is doing requests like '/_session', instead of '/db/_session'.
It looks like some urls inside the fauxton interface are absolute, but really want to be relative.
Also the redirect  I think needs a little tweak.->
if (req.originalUrl === '/_utils') {
     res.redirect(301, '/_utils/');

edit:  Looking at this, I believe it's more of a couchdb-fauxton problem,
as I've compiled the couchdb-fauxton-master same problem, and it has things like ->
I can hack it to work bit by bit, but I think I'm best reporting this to couchdb-fauxton-master..
  return window.location.origin + '/_all_dbs';
That of course is only going to work if the files are mounted at '/'.. :(

See: https://github.com/pouchdb/pouchdb-server/issues/180


[Feature] Prometheus alert for failing backups

It would be great if there was a Prometheus alert for failing backups.
It has just happened to me that backups were not completed successfully.
In such cases, it would be great to be alerted automatically without having to set up an alert yourself.

I'll implement this rule, but I am going to infer the value from the scheduled backups section with a much more reasonable default of sth like 2*schedule - 48h by default.
P.S. Base backups every 2h seems a bit excessive, but I imagine you generate a lot of WALs and want to decrease your RTO.

That sounds great, thank you very much.
2 * schedule sounds reasonable.
If I can help in any way, please let me know.
It's OT here, but briefly about the backup times:  Yes, my goal is to keep the RTO low. I want to have as little data loss as possible in the event of a failure. Is there a better way to solve this than with backups?


prompt command doesn't provide default values to Ms Teams

when executing await ctx.parameters.prompt you are able to provide BaseParameters to your requested parameters as in the below snippet
	owner: {
		required: false,
		description: "The owner or something",
		defaultValue: "Barry",
	},

The expectation would be that this would be shown to the user when the command is displayed, but this doesn't seem to occur

This is fixed now.


Check supported version for CreateNamespaces RPC

What type of PR is this?
/kind feature
What this PR does / why we need it:
We now pre-check if conmon-rs supports the CreateNamespaces RPC and return a wrapped defined error if not.
Which issue(s) this PR fixes:

Requires https://github.com/containers/conmon-rs/pull/1040
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

Check supported version for `CreateNamespaces` RPC

Codecov Report

Merging #1042 (300ee4b) into main (2e123a1) will decrease coverage by 0.63%.
The diff coverage is n/a.

:exclamation: Current head 300ee4b differs from pull request most recent head 187ea17. Consider uploading reports for the commit 187ea17 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1042      +/-   ##
==========================================
- Coverage   34.10%   33.48%   -0.63%
==========================================
  Files          13       13
  Lines        1126     1126
  Branches      389      390       +1
==========================================
- Hits          384      377       -7
- Misses        486      494       +8
+ Partials      256      255       -1

/hold
for https://github.com/containers/conmon-rs/pull/1040

/unhold
PTAL @haircommander @rphillips
I think after this one we can create a new release.

LGTM

/lgtm


Fix CSS entry making JS module empty

I had some trouble getting a bundle working in components. For some reason it created empty js modules whenever I would add a second CSS entry point. Required tweaking the webpack to get a working result. Bumps to 0.2.22 as well

@berekuk could you review this?

Oh wait, do we even need all this stuff?
I added import "!style-loader!css-loader!postcss-loader!../src/styles/main.css"; to storybook's preview.js recently, and I think we can just drop anything css-related from the main webpack config and it'll just work. Styles get built with postcss call at yarn build, not with webpack.

Oh wait, do we even need all this stuff?
I added import "!style-loader!css-loader!postcss-loader!../src/styles/main.css"; to storybook's preview.js recently, and I think we can just drop anything css-related from the main webpack config and it'll just work. Styles get built with postcss call at yarn build, not with webpack.

Good point, closing


App service plan

As far as I can tell with some quick experimentation, the inbound (virtual) and outbound addresses are the same across apps in the same App Service Plan. Is this guaranteed behavior?
I believe being in the same App Service Plan means the apps are deployed in the same region, but from what I can tell they can be in different resource groups (and the resource groups themselves in different regions) and still have the same IP addresses if they are in the same plan. Is that correct?

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

ID: 4ce77cde-5dc1-65c5-6c56-3fa425966a3b
Version Independent ID: 0958e461-ca92-2fea-dd67-143cc9f939f6
Content: IP addresses in Azure App Service
Content Source: articles/app-service/app-service-ip-addresses.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Hi @dcbrown16 Thank you for your feedback! We will investigate and get back to you with our findings.

@dcbrown16 All apps in the same App Service Plan (ASP) typically should have the same inbound and outbound IP addresses. The exceptions being when you start talking about App Service Environments (ASE) and if you bind an IP based SSL cert to your web app you can then have an app with unique IPs. Otherwise, if you're not using SSL or SNI SSL bindings and not using an ASE, they should be the same.
ASP is just simply the VM. The VM has the ability/capacity to host multiple app services at the same time.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Thanks @BryanTrach-MSFT :)


New version: LIJI32.SameBoy version 0.16.3

Pull request has been created with komac v2.2.1 :rocket:

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

Automatic Validation ended with:

2024-04-12 18:19:03.848 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!683B535B: (caller: 682B1A80) LogHr(1) tid(64c) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!683FB5DD: (caller: 684912BF) Exception(1) tid(64c) 8A15005E ]
2024-04-12 18:19:03.848 [REPO] Failed to open available source: msstore
2024-04-12 18:19:10.836 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\RepositorySource.cpp(757)\WindowsPackageManager.dll!5525535B: (caller: 55151A80) LogHr(1) tid(f0c) 8A15005E     Msg:[D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Rest\Schema\HttpClientHelper.cpp(30)\WindowsPackageManager.dll!5529B5DD: (caller: 553312BF) Exception(1) tid(f0c) 8A15005E ]
2024-04-12 18:19:10.836 [REPO] Failed to open available source: msstore
2024-04-12 18:19:11.800 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.38.33135.0

(Automated response - build 876.)


TopNav Menu

feature topnav based on figma design

Connect wallet using rainbow kit

I love the progress being made here. A couple things I'd like to see is the background color(s) more closely match the design background color 0B0B0B, and for the links to be updated on mobile too. It would be cool to use one variable for both lists of links in the navbar (mobile and laptop+).


Change SSL example notebook to use augmentation_utils

The notebook wouldn't work since augmentation utilities will move away from simclr and into their own module

Thanks for catching this and updating the notebook.


use different colors to distinguish logs

Description
Use different colors to distinguish logs
Related Issues
[LOGGING-IMPR] Use different colors to distinguish logs #2327
Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make unit_testing and make integration-testing successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

Thanks @EdwardLi-coder!


Fix. crash while closing the application

Fix cleanup errors on application close. clean deletion of created objects ...

https://github.com/devxkh/FrankE/commit/770b479bb6961c8d67f38b61c3b2a745167b8ee7


Add more description for .option directive

Changes:

Apply Jim's suggestions

@jrtc27 does this change look good to you after apply your revision?

@luismarques @asb @jrtc27 did you mind did a final round review?

Some linkers don't support relaxation, but that probably doesn't need to be explained here. if it does, then maybe something like "if the linker supports it" added to the relax explanation would be good enough.

I hadn't noticed your earlier comment, Jim. I think that phrasing ends up being misleading. When using this option the compiler will emit relaxation relocations without checking for linker support, and then the linker will complain if it doesn't actually support such relaxations. Maybe just state that the linker needs to support relaxations?

Changes:

Rebase
Address @luismarques's comment
Add NOTE to .option relax/.option norelax

Changes:

Add one more NOTE to recommend user should use .option push + .option norelax + .option pop  if they want to disable linker relaxation of specific code region

I don't think I have permission in this repo/org to approve anything, but the technical issues I pointed out seem to have been addressed, so it LGTM.

@luismarques @asb thanks you guys, I gonna merge this :)


For MacOS export the documentation says "leave Identity empty for ad-hoc signature" but Export Dialog does not allow it

Godot version
v3.5.rc6.official [f05cecdc4]
System information
Linux
Issue description
The documentation on Exporting for macOS says:

If you do not have an Apple Developer ID Certificate [...] Keep Code Signing enabled and leave the Identity option empty, in this case Godot will use a ad-hoc signature, which will make running an exported app easier for the end users.

But the Editor will give the error "Invalid bundle identifier. Identity is missing." and the export buttons become disabled. (Also, the otherwise yellow warning about notarization becomes red.)
Additionally, it's called Identity in the docs but Identifier in the export dialog. And the options for Timestamp and Hardened Runtime are missing but mentioned in the docs.
Steps to reproduce
Add export for MacOS.
Minimal reproduction project
No response

Identity (who you are as developer) and Identifier (the unique name of your app) are two different settings, maybe you're confusing them?

There is no property for anything resembling "who I am as a developer". There's Name but the placeholder is Game Name and for Identifier the placeholder is com.example.game. There is no tooltip description for any of the properties.

Invalid bundle identifier. Identity is missing.

That's not the correct message, it says "Identifier is missing."

That's the unique name of your app in reverse dns naming scheme which you need to fill.

Keep Code Signing enabled and leave the Identity option empty, in this case Godot will use a ad-hoc signature,

There is indeed no "Identity" option, the docs must be outdated. @bruvzg

There's codesign/identity option (which is hidden when exporting from non-macOS host, since only ad-hoc is supported) and application/bundle_identifier option. identity can be left empty for ad-hoc signing, or set to apple developer id for proper signung . bundle_identifier is always required.

There's codesign/identity option (which is hidden when exporting from non-macOS host, since only ad-hoc is supported)

I guess that part should be clarified in the docs as it's confusing when not on macOS since you don't see it, and as evidenced here it can be confused with "Identifier".

I think it was identifier at some point, then was renamed to bundle_identifier, but the message was not updated.

I guess that part should be clarified in the docs

Docs seem to still assume singing is only possible on macOS, so definitely should be updated.


policy: fix wildcarding at L7 for DNS

Previously, if there was L7 policy applying to DNS at a specific port, (e.g.
port 53), for a specific selector (e.g., the selector representing the
"kube-system" namespace), and another rule which allowed all at L3 for the
"kube-system" namespace, the behavior which was expected is to allow all DNS
traffic at L7 on port 53, since the second rule allows all at L3 (which thus
allows all at L4, and at L7). However, the FQDNSelector which was being used to
synthesize allow-all at L7 was an empty selector (with no "MatchName" nor no
"MatchPattern" specified). This is treated by the DNS proxying code as allowing
no DNS requests at all, which is incorrect. So, when wildcarding at L7, be
sure to specify allow-all via " "matchPattern": "*" " in the synthesized
selector which is utilized by the DNS proxy.
Signed-off by: Ian Vernon<EMAIL_ADDRESS>I still need to add testing for this. I performed manual testing to ensure that this worked. It's most likely simplest to add a basic Ginkgo test that piggybacks on top of the existing FQDN Ginkgo tests.

This change is

test-me-please

test-me-please

Coverage decreased (-0.02%) to 41.86% when pulling e1fadf69f2a193fa73ecca413a53acae40679e3b on pr/ianvernon/fix-allow-all-l7-dns-wildcard into 761854d23e2c427a64cec7166afc8406a242e13a on master.

Build failure: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/12539/testReport/junit/Suite-k8s-1/10/K8sServicesTest_Checks_ClusterIP_Connectivity_Checks_service_on_same_node/
Only test that failed is the one which checks the service connectivity on the same node, which is a known flake. Merging.


Containerize SolarShed

Added a Dockerfile + README update

multi-stage build
verified working on RPi4/raspbian
~110mb image size

thanks for this one @truncj !    I'm terribly behind here 😅 but I'll see if I can give this a try and get it merged.
I definitely think it'd be helpful to some folks.
Apologies for lack of response -- the rest of my life has been 🤹♂ a lot and I've just not been making it back to GitHub as much.


Azure Storage Local Emulator

Feature Request: Provide a way to access local azure storage emulator.

I, too, would appreciate this functionality.  Seems like it should be a feature of this, as the Storage Explorer standalone picks up the local emulator account already.

Just add a vscode command that lets specifying the connection string. Preferably it would support '
'UseDevelopmentStorage=true'

This feature was included in the 0.9.0 release. Thanks for suggesting!

@wwlorey This is awesome, thank you for taking it in consideration :)


Typo "a [Azure free account]"→"an [Azure free account]"

https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/upgrade-azure-subscription
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cost-management-billing/manage/upgrade-azure-subscription.md
#PingMSFTDocs

Thanks, @hyoshioka0128!


generate:project command is broken

Although it is not recommended to create a new project based on symfony1, it may sometimes be necessary to build a symfony1 project from scratch.
For a completely empty project, the project:generate command does not work.
Error:
PHP Warning: require_once(/Doctrine/Core.php): Failed to open stream: No such file or directory in .../vendor/friendsofsymfony1/symfony1/lib/plugins/sfDoctrinePlugin/config/sfDoctrinePluginConfiguration.class.php on line 36

PHP Fatal error: Uncaught Error: Failed opening required '/Doctrine/Core.php' (include_path='.:/Users/connor/.phpbrew/php/php-8.3.0/lib/php/pear') in .../vendor/friendsofsymfony1/symfony1/lib/plugins/sfDoctrinePlugin/config/sfDoctrinePluginConfiguration.class.php:36

Code fragment causing the error:
https://github.com/FriendsOfSymfony1/symfony1/blob/50c946b4415691df3d2ece73c63364777f70cd2e/lib/plugins/sfDoctrinePlugin/config/sfDoctrinePluginConfiguration.class.php#L35-L38
Reproduction steps:
mkdir folder
cd folder
composer require friendsofsymfony1/symfony1
vendor/bin/symfony generate:project gentest

We should check if the doctrine plugin can be detached from the project and moved to a separate repo.

It seems to work with --orm=none, because it defaults to Doctrine.
Anyway, I agree that having it shipped with the framework doesn't quite make sense, although I'm partial as I only use Propel with symfony1. Having it in a separate package would also facilitate upgrading one separate from the other.
That said, I'm not sure how much work it be to do that. Perhaps a easier route on the short term could be to have it run out of the plugins directory as I think it originally used to.

@mentalstring It does not seem very complicated. My biggest dilemma is how to do the separation: actually, or in a subtree layout, as the symfony does.


Repeated access to the same storage element in withdraw_shares

lp_position_id is fetched from storage OmniPositionId repeatedly in withdraw_shares and unlock_lp_position. The sample code is shown below:
https://github.com/galacticcouncil/HydraDX-node/blob/9c3c0e37c6c1f454f48c7f730bbb67b77131788e/pallets/omnipool-liquidity-mining/src/lib.rs#L909-L911
https://github.com/galacticcouncil/HydraDX-node/blob/2dd058bf02e90f6c0292800e4e04402425ee37fa/pallets/omnipool-liquidity-mining/src/lib.rs#L828-L829
It seems unnecessary when unlock_lp_position is only used in withdraw_shares.
It is recommended to reduce unnecessary interaction with storage since storage accesses are costly operations on the chain.

This is closed as an invalid issue. The following explanation from @martinfridrich makes sense.

unlock_lp_positon() happens only when the deposit is destroyed, and I need to read this storage in withdraw_shares() to get lp_positon_id.
try_mutate_exists() is the way to completely delete the value from storage(remove() - basically only set value to None but leave key in the storage).
try_mutate_exists() returns value anyway, so I can use it in unlock_lp_position()
Using try_mutate_exists() in the withdraw_shares() would add an unnecessary write every time this fn is called.


Feature Request: stdin Support

A lot of linting engines are designed to run with stdin so as to allow for checking buffers instead of only saved files. I've seen this done either as the default, or with a specific --stdin flag. Support for both check and fix would be great.
Specifically requesting this since it might be necessary for #10.

I've seen this done either as the default, or with a specific --stdin flag.

Understood. I did feel like a "streaming" option for all interactions was long overdue. I'll work on this over the weekend.

The latest release (v0.4.0) contains a -s, --stdin flag for statix check, statix fix and statix single. Every subcommand with the flag will accept exactly one file on stdin and output diagnostics on stdout.
The other flags will function as expected, for example, statix check -o errfmt -s will accept a file on stdin and output errorformat compatible output on stdout.
Feel free to reopen if something is not functioning as expected :)


feat: Implement 'prepare_for_training' for text classification datasets

This PR implements the prepare_for_training method for the DatasetForTextClassification. I modified the first tutorial to show the usage: https://rubrix.readthedocs.io/en/feat-prepare_for_training/tutorials/01-labeling-finetuning.html
I don't think I will manage to implement the prepare_for_training for all tasks before the release.
@dvsrepo @frascuchon For the TokenClassification task, should we rely on spacy utilities to make the conversion from spans to ner tags, or should we provide our own utilities? To me it would seem a bit strange if we required spacy to be installed, to prepare the dataset for training with transformers ... @dvsrepo Do you know of any other library that provides some utilities for converting spans to ner tags?

This PR implements the prepare_for_training method for the DatasetForTextClassification. I modified the first tutorial to show the usage: https://rubrix.readthedocs.io/en/feat-prepare_for_training/tutorials/01-labeling-finetuning.html I don't think I will manage to implement the prepare_for_training for all tasks before the release.
@dvsrepo @frascuchon For the TokenClassification task, should we rely on spacy utilities to make the conversion from spans to ner tags, or should we provide our own utilities? To me it would seem a bit strange if we required spacy to be installed, to prepare the dataset for training with transformers ... @dvsrepo Do you know of any other library that provides some utilities for converting spans to ner tags?

I agree we shouldn't rely on spaCy. Let me think of alternatives

This PR implements the prepare_for_training method for the DatasetForTextClassification. I modified the first tutorial to show the usage: https://rubrix.readthedocs.io/en/feat-prepare_for_training/tutorials/01-labeling-finetuning.html I don't think I will manage to implement the prepare_for_training for all tasks before the release.
@dvsrepo @frascuchon For the TokenClassification task, should we rely on spacy utilities to make the conversion from spans to ner tags, or should we provide our own utilities? To me it would seem a bit strange if we required spacy to be installed, to prepare the dataset for training with transformers ... @dvsrepo Do you know of any other library that provides some utilities for converting spans to ner tags?

I agree we shouldn't rely on spaCy. Let me think of alternatives

The server part computes tags at token level. You could use for this purpose. If i remember the computed tags are in the IOB format. It could be a begining

This PR implements the prepare_for_training method for the DatasetForTextClassification. I modified the first tutorial to show the usage: https://rubrix.readthedocs.io/en/feat-prepare_for_training/tutorials/01-labeling-finetuning.html I don't think I will manage to implement the prepare_for_training for all tasks before the release.
@dvsrepo @frascuchon For the TokenClassification task, should we rely on spacy utilities to make the conversion from spans to ner tags, or should we provide our own utilities? To me it would seem a bit strange if we required spacy to be installed, to prepare the dataset for training with transformers ... @dvsrepo Do you know of any other library that provides some utilities for converting spans to ner tags?

I agree we shouldn't rely on spaCy. Let me think of alternatives

The server part computes tags at token level. You could use for this purpose. If i remember the computed tags are in the IOB format. It could be a begining

Definitely, that's more than enough!

The server part computes tags at token level. You could use for this purpose. If i remember the computed tags are in the IOB format. It could be a begining

Nice, totally forgot about this. Hm, should I copy the logic to the client part? Shall we require the user to upload/load the records before calling prepare_for_training? Or is there an endpoint where I can send the records and get back the metrics/iob tags?

Not sure about the user flow here. We can discuss tomorrow in a  call @dcfidalgo


Kserve Triton inference Server unable to read from PureStorage S3 for multi model serving

/kind bug
What steps did you take and what happened:
I am trying to deploy a multi model triton inference server which loads the models from s3. I have followed the documentation. The CRDs are
Inference Server
apiVersion: serving.kubeflow.org/v1beta1
kind: InferenceService
metadata:
  name: multimodel-triton-serving-v1
spec:
  predictor:
    serviceAccountName: multimodel-sa
    triton:
      args:
      - --log-verbose=1
      resources:
        limits:
          cpu: "1"
          memory: 8Gi
        requests:
          cpu: "1"
          memory: 8Gi

Trained Model
apiVersion: "serving.kubeflow.org/v1alpha1"
kind: "TrainedModel"
metadata:
  name: "sentiment-triton"
spec:
  inferenceService: multimodel-triton-serving-v1
  model:
    framework: tensorflow
    storageUri: s3://.....
    memory: 5Gi

When the services are up the isvc fails to load the model. The logs are
Failed to download model sentiment-triton with err failed to download model: failed to download model: unable to get batch objects MissingRegion: could not find region configuration","stacktrace":"github.com/kubeflow/kfserving/pkg/agent.(*Puller).modelProcessor\n\t/go/src/github.com/kubeflow/kfserving/pkg/agent/puller.go:149"
Is there anything I am missing? I am trying to follow https://kserve.github.io/website/modelserving/storage/s3/s3/

What did you expect to happen:
Expected the isvc to load the model from s3. The service account has the necessary secrets
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
A standalone model (Inference Service with the s3 path) works fine. It uses the storage initializer to fetch the models.
I see that the multi model inference server uses a service agent to fetch the models. Is there a way to configure/test the agent standalone?
Environment:

Istio Version: 1.9.6
Knative Version: v0.22.1
KFServing Version: 0.6.1
Kubeflow version: 1.4.0
Kubernetes version: (use kubectl version): v1.19.15
OS (e.g. from /etc/os-release): Red Hat Enterprise Linux 8.5

The agent pod looks something like : I don't see the endpoint getting pulled from the sa
    - name: ENABLE_PROFILING
      value: "false"
    - name: SERVING_ENABLE_PROBE_REQUEST_LOG
      value: "false"
    - name: METRICS_COLLECTOR_ADDRESS
    - name: AWS_ACCESS_KEY_ID
      valueFrom:
        secretKeyRef:
          key: AWS_ACCESS_KEY_ID
          name: multimodel-s3-secret
    - name: AWS_SECRET_ACCESS_KEY
      valueFrom:
        secretKeyRef:
          key: AWS_SECRET_ACCESS_KEY
          name: multimodel-s3-secret
    image: kfserving/agent:v0.6.1
    imagePullPolicy: IfNotPresent
    name: agent
    readinessProbe:
      exec:
        command:
        - /ko-app/agent
        - --probe-period
        - "0"
      failureThreshold: 3
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 10
    resources:
      limits:
        cpu: "1"
        memory: 1Gi
      requests:
        cpu: 100m
        memory: 100Mi

From the error log, I see that your configuration is missing region information. Check if your s3 secret has the following annotation kv:  serving.kubeflow.org/s3-region: "us-east-2" # replace with the region the bucket is created
reference: docs/samples/storage/s3/s3_secret.yaml

It does have the region configuration
  annotations:
     serving.kserve.io/s3-endpoint: "..."
     serving.kserve.io/s3-region: "..."

But for some reason I don't see them getting translated into the agent.

Was able to resolve it. Thanks!

Hi, I think I got a similar issue, how did you solve it?


feat(curriculum): add inventory management lab

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

The lab is looking great!
A description in the beginning would be helpful.
I came up with this, feel free to change it:
In this lab, you will build an inventory management program that will allow you to add, update, find and remove products from the inventory. The inventory will be stored in an array of objects, where each object will have name and quantity as the keys.


remove defer client.deinit()

it errors on master

hmm i don't see why it should error. at least removing it isn't the best solution. what's the error you got?

It was erroring previously. Does not error on zig version: 0.11.0-dev.1580+a5b34a61a


Zombie mz_is_building: false in landuse layer

What did you see? Features in the landuse layer have mz_is_building: false.
What did you expect to see? That's an internal only attribute not meant for export. It should be dropped.
What map location are you having problems with? http://vector.dev.mapzen.com/osm/all/16/10471/25342.topojson?api_key=vector-tiles-HqUVidw

Looks like this regression is also present on prod (v0.8 tiles) :\
We originally removed them in v0.5, see: https://github.com/mapzen/vector-datasource/issues/333.

Examples:
{"kind":"university","source":"openstreetmap.org","sort_key":36,"area":1003630,
"mz_is_building":false,"min_zoom":9.0,"id":28965902},"arcs":[[255]]},
{"type":"Polygon","properties":

and
{"kind":"retail","source":"openstreetmap.org","sort_key":41,"area":211777,
"mz_is_building":false,"min_zoom":9.0,"id":147002139},"arcs":[[256]]},
{"type":"Polygon","properties":

LGTM


Fix #1058 : unique_base behavior dealing with relations

Note: I had to update Issue827 tests: as discussed in #1349 using sluggable field as identifier leads to unexpected behavior when not reloading entities afterwards.

great, it is possible to update all loaded entities, if you have a little more time: https://github.com/Atlantic18/DoctrineExtensions/blob/master/lib/Gedmo/Tree/Strategy/ORM/Nested.php#L598 I will merge it anyway in few days.

@l3pp4rd "It is possible to update all loaded entities"
You mean to resolve #1349 ? Looking at where UnitOfWork::entityIdentifiers is updated, I was more thinking of a custom id generation strategy.
I'll update the PR tomorrow morning, there are some checkstyle issues (snake case).

@l3pp4rd done

ok, thanks. if someone will have issues with $em->clear(); requirement will come back to it


Some special characters cannot be recognized in the target

For example, the triple pattern below cannot be recognized due to the character '&'. This is used in the LinkedGeoData Project.
:x={x}&y={y} a :Point .

Fixed by commit 7e639d80f900b1241c025a1e9684664870695d12.

Fixed by commit 7e639d80f900b1241c025a1e9684664870695d12.


[TVMSCRIPT]Fix script printters StructuralEqual check failed

fix print bug when call
      @tvm.script.tir
      def abs(a: ty.handle) -> None:
          A[()] = tir.abs(2.2)
          A[()] = tir.abs(tir.float32(2.2))

      func = abs
      rt_func = tvm.script.from_source(tvm.script.asscript(func, True))
      tvm.ir.assert_structural_equal(func, rt_func)

First parser result(func):
      A[vi, vj] = tir.fabs(tir.cast(tir.float32(2.2000000000000002), "float32"), dtype="float32")
      A[vi, vj] = tir.float32(2.2000000000000002)

Second parser result(rt_func):
      A[vi, vj] = tir.fabs(tir.cast(tir.cast(tir.float32(2.2000000000000002), "float32"), "float32"), dtype="float32")
      A[vi, vj] = tir.cast(tir.float32(2.2000000000000002), "float32")

Second structure has an extra tir.cast compared the first, because the first structure print the 2.2 to tir.float32(2.2) and the tir.float32(2.2) is parsed to tir.cast(tir.float32(2.2), "float32") in second structure.

Thanks @Beya2019 , can you please add a regression test to cover the case?

@jinhongyii and @MasterJH5574 encountered some precision issue if we didn’t print at least 18 digits of a FP32 number

@junrushao1994 I remember the issue is about printing a FP32 number to string and then read it back from the string. The finding/conclusion is that we need to print at least 17 digits so that the two numbers before and after the round trip is the same.
Before the fix, the printer only printed 16 digits for a FP32 number.

Sorry folks i mistakenly merged this PR. Will bring a followup that fixes the problem


Add homemade mime_content_type method to ImageHelper

Ticket: #1797
Issue
Version 1.8.0's is_svg method includes checking for whether or not a file is an SVG and includes a call to PHP's mime_content_type. Unfortunatley, this PHP method is not available in all installs and might require a PECL installation or enabling via PHP.ini:
https://stackoverflow.com/questions/14809054/mime-content-type-function-not-working
Solution
I rolled my own mime_content_type method using the finfo class.
Impact
I fear the performance on this might not be as good as the native method, but I haven't tested to validate
Usage Changes
None
Considerations

Maybe ImageHelper::\_mime_content_type could call the native if it's available and only use the "homemade" component if it's not
Maybe this is all stupid, and we should just check for the presence of .svg or .SVG in the file name and call it a day

Testing
All tests pass

Coverage decreased (-0.02%) to 94.004% when pulling 50ad330f19227699b499c762fff17f59b6997ad1 on 1797/mime_type into 5278a0ffcc701e796802ec14be9aa4e1883514d4 on master.

For now I'm going to go with ...
Maybe ImageHelper::_mime_content_type could call the native if it's available and only use the "homemade" component if it's not
Maybe in the future we can ditch it all for just a simple string check for .svg. I'm guessing that has performance benefits, but haven't tested to validate. I'm going to merge and plan to release as Timber 1.8.1 unless anyone has any suggestions or flags

No objections from my side against merging @jarednova


Add coverage configuration for istanbul

Is it possible to let travis pass with istanbul?

Yes it should ;p Taking a look now

How do you install it?
I get the same error ("Could not find WCT plugin named "istanbul"), when running local.
Bower install didn't work

You  must install the dependency globally too. I have added a section to the README to clarify this.

Confirming it works locally now.


SQL server

What a great project,
but our system has SQL-Server / sql-express.
Can you make an additional PDO connection possible to SQL server.
There are some LIMIT issues between SQL-server and MySQL.
But the sql commands are not explained in the API so it is not so clear what needs to change.
Can you make the software compatible for this connection?
https://www.microsoft.com/en-US/download/details.aspx?id=42299

Migrating to SQL Server would be a major change.
I don't believe it's easy to do that. It would probably need dozens of hours of work.

On Mar 31, 2020, at 9:30 PM, CabrioCar<EMAIL_ADDRESS>wrote:
What a great project,
but our system has SQL-Server / sql-express.
Can you make an additional PDO connection possible to SQL server.
There are some LIMIT issues between SQL-server and MySQL.
But the sql commands are not explained in the API so it is not so clear what needs to change.
Can you make the software compatible for this connection?
https://www.microsoft.com/en-US/download/details.aspx?id=42299 https://www.microsoft.com/en-US/download/details.aspx?id=42299
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/OWASP/rbac/issues/121, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKWGW4JXIBPL63A5LZ7EQLRKIZC5ANCNFSM4LX3FV6Q.

PDO was used and this is the transparent connection from the application to the database.
What special queries are used, or settings on the database.

The system is tightly coupled with performance of normal SQL servers and thus uses Nested Sets to improve this performance.
Databases like SQL Server may support tree structures already. I'm not sure. Regardless, all queries need to be tested and adjusted for it.

On Mar 31, 2020, at 10:02 PM, CabrioCar<EMAIL_ADDRESS>wrote:
PDO was used and this is the transparent connection from the application to the database.
What special queries are used, or settings on the database.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/OWASP/rbac/issues/121#issuecomment-606813464, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKWGW2A24Q2DEHTPZPGG43RKI42VANCNFSM4LX3FV6Q.


Improve in-code documentation

Any substantive/regularly-accessed class or function in Minipresto should be accompanied with detailed doc strings explaining what the code does, what it returns, and the meaning, type, and default of any parameters/properties. Will remove this once functions have been properly documented.

See PR #20


Rewrite the message in WrongScopeException

We should rewrite the WrongScopeException to something more descriptive. Ie there are two reasons for the WrongScopeException to be thrown.

You have misconfigured the scope
You have called the SettingsManager::get with the wrong amount of parameters. Either you forgot the $owner on Local scope or you used $owner on a Global scope.

Did you mean splitting WrongScopeException into two exceptions that will cover two options you mentioned?

I don't think it's possible for us to know what the reason for the error is. I just want the exception message to be more descriptive about what could have caused the exception to be thrown. So my suggestion is purely to rewrite the message.

Ah, I've got it. How about ScopeLogicException ?

Checkout #32


feat: add M+ source

Very-very-very-very WIP
Planning to just add mobile version of it for now.

Proto models and API stuff will be finalized tomorrow (real)

Having trouble with the API returning "version update"
Also same issue with MU! client which only support HTTP/1.1 for some reason


confused about Dilated convolution replace maxpooling

hello, I'm confused about this change in class PillarFeatureNet
https://github.com/SmallMunich/nutonomy_pointpillars/blob/68d3181d35702608d410e948608e9815815677b9/second/pytorch/models/pointpillars.py#L52-L73
use conv replace maxpooling op
although the shape are same, can this change equivalent? do you know some reference material about this

same question!


Possibly convert mod to pure babric

This would be accomplished by porting into MojangFix, and not by using this repo

Probably won't do this now that basic MP works and there is a PR to disable MojangFix when this mod is loaded


fully apply extension service attribute to hand physics service

Fixes #6999
The hand physics extension service was not fully utilizing the extension service attribute. Notably, it was missing:

Friendly name
Default profile
Profile folder root

Additionally, #6988 / #6133 introduced a new property to the attribute that informs the inspector as to whether or not the service requires a profile to properly function. This has been set to true for hand physics.
Verified:

When selecting the service type, the profile and friendly name values are properly set
When manually setting the profile to null, the appropriate warning message appears in the inspector

/azp run


Add Tenancy to Rack Reservations; Fixes #1592

Fixes:
#1592

Added tenant ownership, and created rack reservation stat on tenancy page, appended to api

Resolved the 2 conflicts

@jeremystretch Ok boss this is ready to go/for review!

What is the normal timeline for merge requests?

Was getting:
CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0050_rackreservation_tenant, 0049_rackreservation_change_user in dcim).
To fix them run 'python manage.py makemigrations --merge'
And merged originally to fix. But realized that just changing the dependency to be linear with yours fixes it too.


Prevent, fix, and/or test usage as property reference

I.e., does ::__FILE__ even work? Is that just { __FILE__ }?

Need to intercept with visitPropertyReference and replace it with a lambda returning a string.

Everything but __LINE__ working

Line aaea0ad6bbaa25083978d1eacb883b6c0e5470e8


[T3A3][T10-A3]Yu Jingchen

Ready for review

Some comments added. Please close the PR after reading comments.


Verify user count vs leader boards

Moved to backend : https://github.com/CotacolHunting/cotacol-strava-workers/issues/145


Render process (11786)'s crash wasn't handled by all associated webviews, triggering application crash.

Environment

Technology
Version

Flutter version
3.3.0

Plugin version
5.4.3+7

Android version
Android 10,level 29

iOS version

Xcode version

Stacktrace/Logcat
09-19 14:04:50.994 12140 12140 F chromium: [FATAL:crashpad_client_linux.cc(561)] Render process (17621)'s crash wasn't handled by all associated webviews, triggering application crash.

Possible Cause
https://www.jianshu.com/p/29a8dce65634

I'm having the exact same problem! Been stuck with for a week, is there any solution ?

onRenderProcessGone method should be implemented by all webviews in the app, otherwise once webview process crashes, it will crash the app
https://developer.android.com/reference/android/webkit/WebViewClient#onRenderProcessGone(android.webkit.WebView, android.webkit.RenderProcessGoneDetail)

@huangsir0 Are you have any solution?

@androideveloper Thanks for the hint on the onRenderProcessGone override.
I have implemented this method via androidOnRenderProcessGone in this plugin (on v5, I think it has changed in v6). Where I try to recreate the InAppWebView via a new Key.
However, I still see crashes with the error: [FATAL:crashpad_client_linux.cc(732)] Render process (2370)'s crash wasn't handled by all associated  webviews, triggering application crash. in the Play Console.
Example implementation:
    String inAppWebViewKeyString = Uuid().v4().toString();
    Uri? currentUri; // tracked via the controller

    final webview = InAppWebView(
      key: Key(inAppWebViewKeyString),
      initialUrlRequest: URLRequest(
        url: currentUri,
      ),
      initialOptions: InAppWebViewGroupOptions(
        android: AndroidInAppWebViewOptions(
          useOnRenderProcessGone: true,
        ),
      ),
      androidOnRenderProcessGone: (controller, details) {
        // reload the creashed webview
        setState(() {
          inAppWebViewKeyString = Uuid().v4().toString();
        });
      },
    );

Any ideas? I'd really appreciate any points anyone might have :)

Yor crashing webview might come from another internal dependency/sdk that you don't control.


Support environment variable for S3 addressing_style config

Describe the feature
Allow configuring boto3 to use the virtual host style (MY-BUCKET.s3.amazonaws.com) for talking to a bucket by providing the AWS_S3_ADDRESSING_STYLE environment variable.
Use Case
If you want to force boto3 to include the region in the hostname used for boto3.client("s3", region_name="us-east-1"), you can set the AWS_S3_US_EAST_1_REGIONAL_ENDPOINT=regional in the environment variables.
If you want to force boto3 to use the virtual host style (MY-BUCKET.s3.amazonaws.com) for talking to a bucket, you have to configure it either in application code or in an accessible shared config file. Sometimes, these two options are prohibitively difficult to configure correctly, and configuring this behavior via an environment variable may be significantly easier.
Proposed Solution
Add AWS_S3_ADDRESSING_STYLE to configprovider.py's DEFAULT_S3_CONFIG_VARS' addressing_style entry.
Other Information
No response
Acknowledgements

[X] I may be able to implement this feature request
[ ] This feature might incur a breaking change

SDK version used
botocore==1.34.90
Environment details (OS name and version, etc.)
macOS 14.4.1 (23E224)

Thanks for the feature request, but I think we need more information here. When I run the following:
import boto3
client = boto3.client('s3')
boto3.set_stream_logger('')
client.list_objects(Bucket='us-east-1-bucket')

Then the debug logs show this endpoint, which is the virtual style and contains the region:
Endpoint provider result: https://us-east-1-bucket.s3.us-east-1.amazonaws.com

And if I run this:
import boto3
from botocore.config import Config
boto3.set_stream_logger('')
client_config = Config(s3={"addressing_style": "path"})
client = boto3.client('s3', config=client_config)
client.list_objects(Bucket='us-east-1-bucket')

Then the debug logs show this:
Endpoint provider result: https://s3.us-east-1.amazonaws.com/us-east-1-bucket

So the default behavior is consistent with S3 virtual hosting format: https://bucket-name.s3.region-code.amazonaws.com/key-name
Based on that, I think it's already doing what you're looking for, right? Unless I'm missing something involving your region/version or use case. And there is a (delayed) plan for S3 to deprecate path style requests. So I don't think an environment variable would be considered here.

Ah, shoot. I looked closer, and it looks like this is the result of using a bucket name that doesn't work as a hostname. I had assumed I was configuring something wrong.
As a side note, will bucket names with underscores stop working at some point? Obviously, we'd rather migrate, but... there are lots of priorities.


fix unexpected isolation

add scope-with-reducer example
fix isolation

This fixes #16

Hi, thanks for working on this!
Can you quickly explain what was the bug? It seems that the PR diff includes both a fix and a refactor.

@dai-shi In fact, I can't figure out the real bug. I have read every code (both jotai, jotai-utils, jotai-scope), but all seem correct.
Finally, I guess that's because of the redundant createScopedAtom on the non-isolated atom, so I try to delete them (do a small refactor, mainly removing the un-need arguments and logic), and it works...

Okay, I will review the code again later.

Hi, I updated examples/02. There, I want to have doubledAnotherCount be in sync with anotherCount.

It breaks with this PR change. However, I'm not sure if we can cover both cases.

@dai-shi In my opinion, it's the developer's duty to keep two associated atoms both isolated or unisolated.
One is isolated and another is unisolated can be treated as undefined behavior, and we should only say "do not do this thing" in the document, not try to solve the problem.
I think not creating unexpected isolation is far more than handling this edge case.

This is actually requested by users, and I think it's a requirement, not an undefined behavior.
We strictly want to support, use cases like:
const countAtom = atom(0);
const anotherAtom = atom(1); // only this will be scoped
const mixedAtom = atom((get) => get(countAtom) + get(anotherAtom));

That's why the current implementation is very complicated. Maybe, it's impossible to cover all the edge cases.
If we want to isolate atoms totally, it would be much easier to implement with Provider and a React Context. We can explore such capability as a new util, but it's different from the goal of current ScopeProvider.

@dai-shi Got it!
For others, if you want to use the jotai-scope with reducer, you can use npm @singee/jotai-scope 0.4.3 ("jotai-scope": "npm:@singee/jotai-scope@0.4.3"). It's published based on this PR and can be used with reducer, but not with the above case.
I hope we can find a solution to both cases.

Fixed with #20


RegisterValidatorsFromAssemblyContaining does not register internal validators

System Details

FluentValidation version: 8.0.100
Web Framework version: ASP.NET Core 2.1

Issue Description
Using RegisterValidatorsFromAssemblyContaining<T> at application startup to automatically register:

all validators derived from AbstractValidator...

Does not register validators with the internal access modifier. Those validators need to be manually registered using services.AddTransient<IValidator<T>, Y>();
In my situation, validators are specific implementations of my different API methods, so I don't want to make them public.
I think this should be fixed to also automatically detect validators marked as internals. Or at least to specify in the documentation that only public validators will be detected to avoid confusion of way manual registration works but automatic one doesn't.

Hi, it's intentional that this only scans for public types. I'll update the documentation to make this clear.


latest release 2.8.1 vs 2.9 ?

github 2.8.1
https://mvnrepository.com/artifact/redis.clients/jedis 2.9
what is the right production version to use?

2.9 is prod ready. We just haven't had time to do the release notes :P


Docker image install instructions added

Added installation instructions for pg9182's docker image for hosting headless on linux

TODO:
Mention ports that need to be open.


No compatible source was found for this video. Firefox 35.01

hello
in firefox 35.0.1 i get No compatible source was found for this video.
any idea what the problem is
best regards

oh i see i have not intsalled flash on ff
why does this needs adobe flash?
best regrads

hello,
it's an HLS format and video js work with flash to play it


TypeError: e.velocity is not a function

I'm trying to use angular2-materialize with angular-cli@webpack.
I've managed to load the stub app without errors, but if I try to include a sideNav in the application, when I click on the menu button I get this exception:
EXCEPTION: TypeError: e.velocity is not a function

TypeError: e.velocity is not a function
    at HTMLAnchorElement.<anonymous> (materialize.js:3)
    at HTMLAnchorElement.dispatch (jquery.js:4737)
    at HTMLAnchorElement.elemData.handle (jquery.js:4549)
    at ZoneDelegate.invokeTask (zone.js:356)
    at Object.onInvokeTask (ng_zone_impl.js:44)
    at ZoneDelegate.invokeTask (zone.js:355)
    at Zone.runTask (zone.js:256)
    at HTMLAnchorElement.ZoneTask.invoke (zone.js:423)

Is there a way to fix this?

My main.ts file is:
import { bootstrap } from '@angular/platform-browser-dynamic';
import { enableProdMode } from '@angular/core';

// import angular2-materialize: once per project
import 'jquery';
import "materialize"
import "materialize-css"
import "angular2-materialize";

import { AppComponent, environment } from './app/';

if (environment.production) {
  enableProdMode();
}

bootstrap(AppComponent);

app.component.ts file:
import { Component } from '@angular/core';
import { MaterializeDirective } from 'angular2-materialize';

@Component({
  selector: 'app-root',
  templateUrl: 'app.component.html',
  styleUrls: ['app.component.scss'],
  directives: [ MaterializeDirective ]
})
export class AppComponent {

}

and app.component.html file

cloudFirst Link With Icon

  menu

Duplicate of https://github.com/InfomediaLtd/angular2-materialize/issues/20 and https://github.com/InfomediaLtd/angular2-materialize/issues/48

I think it's a little different because I am using angular-cli@webpack and not vanilla webpack. In angular-cli you do not have direct access to webpack configuration so I can not apply @camarrone workaround in #20. But I will check those issues to track updates

@camarrone workaround results in buggy behaviour with modals

@lucacox did you figure out how to solve this with angular-cli@webpack? I'm having the same issue.

@wceolin Unfortunately no...

There are some new instructions added by @leonardobazico in his latest PR (https://github.com/InfomediaLtd/angular2-materialize/pull/105) fixing issues for the angular-cli@webpack. Maybe try running through them using the latest version (5.1.1) that includes his fix.
If that doesn't work, maybe @leonardobazico can share his setup that works.

Thanks, @leonardobazico. I've just tried his instructions, and it's working now. :)
The missing part for me was adding jQuery to angular-cli.json.

@wceolin I'm having the same issue and done everything as described in the instructions, however, this velocity thing is still not found. Could you maybe share your setup so I could compare mine with it? Thanks in advance

@bernhardwaidacher are you adding this to your angular-cli.json file?
"scripts": [
  "../node_modules/jquery/dist/jquery.js",
  "../node_modules/materialize-css/dist/js/materialize.js"
],

Please, also note that you need the version 2.2.4 as jQuery 3 isn't compatible. You can have a look at my working repository.

@wceolin thanks for sharing
I've compared our projects, only difference seems that I have
"../node_modules/jquery/dist/jquery.min.js",
and you have it without the min. But if I do that, i have the problem that whole application is not working because jQuery.easing.swing' is mssing

@bernhardwaidacher did you manage to get it to work? I followed the instructions to install with angular-cli@webpack, but it doens't work.
When I use jquery.min.js, the e.velocity problem appears. When I change it to jquery.js, then the 'swign of undefined' appears.

@gdlm91 for me helped:
window.$ = window.jQuery;
in app.component.
I found what jQuery(selector).velocity works, but $(selector).velocity doesn't.

@n0mid : I have the same issue (angular2-materialize with angular-cli@webpack) that $(selector).velocity is not defined but jQuery(selector).velocity is but I don't understand from your post where you would put that bit of code.

@joelmarty I have put in constructor of app.component.

So i tried that same thing that worked for @n0mid, I put window['$'] = window['jQuery'] in my app.component,  and @bernhardwaidacher's solution, but I still get the same error trying to create and expandable fab with this code (which I took form materialize docs):
`
 {{title}}

menu

insert_chart
format_quote
publish
attach_file

`
in angular-cli v1.0.0
Error, caused when I try to expand the FAB:
Uncaught TypeError: d.find(...).velocity is not a function     at c (materialize.js:4)     at HTMLAnchorElement.<anonymous> (materialize.js:4)     at HTMLDocument.dispatch (jquery.js:4737)     at HTMLDocument.elemData.handle (jquery.js:4549)     at Zone.runTask (zone.js:165)     at HTMLDocument.ZoneTask.invoke (zone.js:460)
Does anyone else have fix for this?


If motion Module toggled, RGB overlay doesnt work anymore

librealsense
2.36.0 RELEASE

OS
Windows

Name
Intel RealSense L515

Serial Number
00000000f0211525

Firmware Version
<IP_ADDRESS>

Camera Locked
YES

Usb Type Descriptor
3.2

Product Line
L500

Asic Serial Number
00000003a9681eec

Firmware Update Id
00000003a9681eec

Please provide a description of the problem

@rasamaya, thanks for the report. This is a recognized issue with the viewer that will be addressed in next releases.
In the meanwhile you can use a workaround to troubleshoot the glitch - https://github.com/IntelRealSense/librealsense/issues/6992#issuecomment-667633901
Duplicate of #6992

Hi @rasamaya,,
Did that work for you? Will you be needing further help with this? If we don’t hear from you in 7 days, this issue will be closed.
Thanks


bwlimit is uneven in the presence of buffering

Because the bwlimit limits the io.Reader when reading into a buffer it only limits the speed of reading into the buffer, not the actual upload speed.
This is a problem in particular with S3/Drive and multipart files.
It is correct in the long term, but is burstier than it should be.
Could potentially fix by putting the limiter into the transport, or lower down the stack somehow.

B2 is also broken AFAICT, since it copies all files to temporary storage due to sha1 calculation.

There is now a method for fixing this in in 037a000 using fs.AccountByPart.  The b2 case is now fixed but the drive and s3 need fixing

This is now properly fixed for all remotes in #1443 except for s3 which does its own buffering and has its own issue.


WoodT7 macro is not adding to the bonfie properly

Submitter: Nissim
Email<EMAIL_ADDRESS>

There is a new wood macro that Huggz wrote, I noticed he forked this repo the other day but didnt push, I can put the working one if needs be

I can push my version.  I didn't because I haven't had an opportunity, due to lack of carrots, to test the carrot part.


Port SEE-Segment Tool to XSEDE

We could also work in tools like Scoop/CCTools into our work on the HPCC/XSEDE.

Dirk has a workflow that uses Open Science Grid (OSG).  Maybe we could look into other resources.


⚠ Processors has degraded performance

In 3f5e909, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 46 ms

Resolved: Processors performance has improved in 5ac961c.


I can't figure out why ImageRecordIter use only 1 thread for decoding

I modified src/io/iter_image_recordio_2.cc to add more log info like this:
LOG(INFO) << "ImageRecordIOParser2: " << param_.path_imgrec << ", use " << threadget << " threads for decoding..";
LOG(INFO) << "maxthread: " << maxthread;
LOG(INFO) << "param_.preprocess_threads: " << param_.preprocess_threads;
LOG(INFO) << "omp_get_num_procs(): " << omp_get_num_procs();

the console log out:
src/io/iter_image_recordio_2.cc:169: ImageRecordIOParser2: /data/imagenet_train.rec, use 1 threads for decoding..
src/io/iter_image_recordio_2.cc:171: maxthread: 1
src/io/iter_image_recordio_2.cc:172: param_.preprocess_threads: 1
src/io/iter_image_recordio_2.cc:173: omp_get_num_procs(): 1
src/io/iter_image_recordio_2.cc:169: ImageRecordIOParser2: /data/imagenet_val.rec, use 1 threads for decoding..
src/io/iter_image_recordio_2.cc:171: maxthread: 1
src/io/iter_image_recordio_2.cc:172: param_.preprocess_threads: 1
src/io/iter_image_recordio_2.cc:173: omp_get_num_procs(): 1

but I add the following code to another independent test file like this:
int preprocess_threads = 100, maxthread, threadget;
#pragma omp parallel
{
  maxthread = std::max(omp_get_num_procs() / 2 - 1, 1);
}
std::cout << "maxthread: " << maxthread << std::endl;
preprocess_threads = std::min(maxthread, preprocess_threads);
std::cout << "preprocess_threads: " << preprocess_threads << std::endl;
#pragma omp parallel num_threads(preprocess_threads)
{
  threadget = omp_get_num_threads();
}
preprocess_threads = threadget;
std::cout << "preprocess_threads: " << preprocess_threads << std::endl;
std::cout << "threadget: " << threadget << std::endl;
std::cout << "omp_get_num_procs(): " << omp_get_num_procs() << std::endl;

and the console log out:
maxthread: 5
preprocess_threads: 5
preprocess_threads: 5
threadget: 5
omp_get_num_procs(): 12

my cpu is 5930k, it has 6 physical cores,  omp_get_num_procs() should log out 12, so the test result is ok, but in  src/io/iter_image_recordio_2.cc it log out 1.

How are you installing MXNet. If you are building from source, Are you building MXNet with USE_OPENMP=1? I have MXNet compiled with USE_OPENMP=1 and I am not able to reproduce your issue.

I meet the same problem.  How to fix it?

I met the problem when compiled with OpenBLAS 0.2.20, but when I rolled back OpenBLAS to 0.2.19, it works! Maybe OpenBLAS 0.2.20 conflits with mxnet

I met the same problem too, I use openblas 0.2.20, too


passive event listener to make lighthouse best practices happy

Running google lighthouse audits I'm getting the following issue reported:

From what I can tell from the learn more link events can be passive unless they have the possibility of preventing the event (which I don't see why lazy hydration would need to do)
Marking as passive is supposed to be better for performance, from what I understand.
Thanks!

+1 for this addition

Thank you @danielkellyio and @Sshuichi for your contributions.
What happens when passive is applied to an unsupported event?

Agreed, that's what I avoided in this PR https://github.com/maoberlehner/vue-lazy-hydration/pull/60
(Sorry I didn't know this PR existed before I created mine, this is why I added my review here. )

To answer your question @maoberlehner, if passive is applied to 'unsupported' event, it will never call The preventDefault() method which cancels the event if it is cancelable, meaning that the default action that belongs to the event will not occur.

Closing this in favour of #60
Thanks @danielkellyio for getting the ball rolling.

To answer your question @maoberlehner, if passive is applied to 'unsupported' event, it will never call The preventDefault() method which cancels the event if it is cancelable, meaning that the default action that belongs to the event will not occur.

@Sshuichi after thinking closer about it I'm still not sure what's the problem with using passive on all events?

It's hard to come up with an example but I'll try:
Imagine you do your lazyhydration on a click event, if passive is there, you need to click twice, because the first event is canceled with passive.
I'm thinking of a link inside a component that is being lazyhydrated on click.
If you click on that link, nothing will happen. the link will work on the second click though.
🤔

That's a known issue that is not related to passive event listeners. See https://github.com/maoberlehner/vue-lazy-hydration/issues/40

Not really, I'm talking about an <a> link. That doesn't need JS to be hydrated, does it?
Imagine you have an anchor link inside a component hydrated on click, the link should work even if the parent component is not hydrated or am I mistaken?

 Made a quick CodePen (with plain JavaScript) and the Link works as expected 🤔
https://codepen.io/maoberlehner/pen/ExPeRor

Yes, you are right.
We need to test all events to make sure passive doesn't break any default behavior. But for precaution, let's do it only for scroll events since it's the one lighthouse is complaining about.

I get your point but if there is no known disadvantage to it I prefer the simpler solution.
Merging this and creating a new release later.
Thanks to all of you!

Thank you @maoberlehner for the fast review and interactivity and thanks to @danielkellyio for starting this!
Any idea when this will be published on npm?

Just published a new release!

I think we missed the fix for Lighthouse.
There are two parts of eventListeners and we should add passive to interactions as well.
Will create a PR for this.

Fixed here:
https://github.com/maoberlehner/vue-lazy-hydration/pull/61


Dependency checker should ignore pre-releases

description
currently the dependency checker doesnt discriminate pre-releases - eg https://github.com/envoyproxy/envoy/issues/19154

cc @kfaseela

I can work on this

Be aware that there is all manner of different release strategies being used by repos. Some repos don't have releases. Some repos have releases but never tag a latest release. Some repos have releases where everything is a pre release.
An example of a dependency we use that has only pre releases - https://github.com/grailbio/bazel-compilation-database/releases

hmm, thats annoying - not sure why they are doing that, altho i believe that repo is in "maintenance mode" so maybe related
in the main i think we only want notifying of actual releases rather than pre-releases - there are a couple already where its flagging the "wrong" version

That is one example - there are many in our full list

can we add a flag in the metadata use_prerelease or somesuch ?

For reference these are the currently flagged releases, that i think should not be, or have the wrong version:

https://github.com/envoyproxy/envoy/issues/19207
https://github.com/envoyproxy/envoy/issues/19156
https://github.com/envoyproxy/envoy/issues/19155
https://github.com/envoyproxy/envoy/issues/19154

not 100%, but i think this is a byproduct of the fixes/updates we made to the dep checker recently
either way - it would be good to have these flag the correct versions, and only when they are released etc
i had a quick look through repository locations and didnt see anything else pegged to a pre-release, but then it wasnt obv the situation with bazel-compilation-database either so not sure of any others