INTERFACE hyperlink is broken

Links to an unrelated xml reference page

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

ID: 6f43c82b-fe09-fd84-ab9c-85c5c68f699a
Version Independent ID: 19ebc355-cd07-e705-c3c7-1adf10fc3b88
Content: WdfFdoQueryForInterface function (wdffdo.h) - Windows drivers
Content Source: wdk-ddi-src/content/wdffdo/nf-wdffdo-wdffdoqueryforinterface.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Thanks @PFroese for the report.  I found 62 occurrences of this bad link!  Just pushed the update to replace them with https://docs.microsoft.com/windows-hardware/drivers/ddi/content/wdm/ns-wdm-_interface.  That change should appear on the live site within an hour.  Thanks again for your eagle eye!


[Consul] Asset revamp

What does this PR do?

This PR adds a new OOTB dashboard for Consul. It also adds a new monitor and logs saved view
Motivation

https://datadoghq.atlassian.net/browse/AI-3763
https://datadoghq.atlassian.net/browse/AI-3781
https://datadoghq.atlassian.net/browse/AI-3759
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

Created DOCS-7395 for docs review.


nodeFit is set to true, but is still evicted for services with only one node available

What version of descheduler are you using?
descheduler version:
0.20.0
Does this issue reproduce with the latest release?
I don't know.
Which descheduler CLI options are you using?
lownodeutilization
Please provide a copy of your descheduler policy config file
"LowNodeUtilization":
enabled: true
params:
nodeFit: true
nodeResourceUtilizationThresholds:
targetThresholds:
cpu: 70
memory: 70
thresholds:
cpu: 20
memory: 20
What k8s version are you using (kubectl version)?
kubectl version Output
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"clean", BuildDate:"2021-07-15T21:04:39Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.11-aliyun.1", GitCommit:"757dfe7e010afcfa31591df65f26b4b80540975e", GitTreeState:"clean", BuildDate:"2022-04-20T09:01:29Z", GoVersion:"go1.15.15", Compiler:"gc", Platform:"linux/amd64"}

What did you do?

deployment is setting:
nodeSelector:
node-type: debezium-prod
There is only one node for this label：

pod is evicted
I0727 00:31:54.392273       1 evictions.go:117] "Evicted pod" pod="debezium-prod/debezium-postgres-cp-kafka-connect-7c6f4b446b-mg255" reason=" (LowNodeUtilization)"
I0727 00:31:54.392327       1 lownodeutilization.go:376] "Evicted pods" pod="debezium-prod/debezium-postgres-cp-kafka-connect-7c6f4b446b-mg255" err=
What did you expect to see?
only one node for this label，do not evict pods for this service
What did you see instead?

Hi, NodeFit was added in v0.21.0, so setting it in v0.20.0 will not work.
Please try again after upgrading your version of descheduler, and if the issue persists then please feel free to reopen this bug. Thanks!
/close

Hi, NodeFit was added in v0.21.0, so setting it in v0.20.0 will not work.
Please try again after upgrading your version of descheduler, and if the issue persists then please feel free to reopen this bug. Thanks! /close

hi，Can k8s v1.20 use deschduler v0.24?

hi，Can k8s v1.20 use deschduler v0.24?

We don't technically support or test v0.24 on v1.20, so it may work, but if there are any issues then the recommendation is to upgrade


Question - Why did you move security sources?

Why did you move security sources from https://github.com/aspnet/Security ?

See https://github.com/aspnet/Announcements/issues/320

@davidfowl thank you for the response. Do you plan ship Microsoft.AspNetCore.Authorization as separate package like now?

No plans to ship that as an individual package after 3.0. The API is still available via FrameworkReference instead of PackageReference. See https://github.com/aspnet/AspNetCore/issues/3756.


Replace fftw interface with Eigen fftw

would allow us to use eigen internal implementation without fftw library
and otherwise we could use fftw or MKL as a backend.
https://eigen.tuxfamily.org/dox/unsupported/group__FFT__Module.html
https://gitlab.math.ethz.ch/NumCSE/NumCSE/blob/43c3152296a97f4a927cd82fe3c19ac0c64537e4/CMake/Macros/set_eigen_fft_backend.cmake

Sounds good to me, that would give us an option to keep functionality even if fftw isn't there.

Yeah unfortunately, the eigen interface does not yet support mkl, but it would still be a nice extension

Huh? Doesn't the eigen documentation say MKL is supported?

Got it, src/FFT/ei_imklfft_impl.h is missing.

jop


Cards on Homepage are not clickable which is not good i think

Right!
The cards should be clickable.
Do you wanna make a PR for the same? @arbazalam01

Yes

is this pr will be eligible for cross woc?


v0.13

According to semantic versioning syntax changes require a new minor version, so this will wait for v0.13.

Closing as obsolete


gpg hangs in proxy environment.

The .devcontainers.json below will install terraform in the development container in the internet environment.
$ cat .devcontainer/devcontainer.json
{
        "name": "Ubuntu",
        "image": "mcr.microsoft.com/devcontainers/base:jammy",
        "features": {
                "ghcr.io/devcontainers/features/terraform:1": {}
        }
}

If you use the same code to start the development container in a proxy environment, gpg will fail to start with an error as shown below.
[2023-02-01T08:54:07.550Z] TERRAFORM_VERSION=1.3.7
[2023-02-01T08:54:08.097Z] TFLINT_VERSION=0.44.1
[2023-02-01T08:54:08.772Z] TERRAGRUNT_VERSION=0.43.1
[2023-02-01T08:54:08.774Z] Downloading terraform...
[2023-02-01T08:54:09.484Z] (*) Downloading GPG key...
[2023-02-01T08:57:11.356Z] gpg: keyserver receive failed: Connection timed out
[2023-02-01T08:57:11.357Z] (*) Failed getting key, retring in 10s...
[2023-02-01T08:57:21.359Z] (*) Downloading GPG key...
[2023-02-01T09:00:21.756Z] gpg: keyserver receive failed: Connection timed out
[2023-02-01T09:00:21.757Z] (*) Failed getting key, retring in 10s...
[2023-02-01T09:00:31.759Z] (*) Downloading GPG key...
[2023-02-01T09:03:32.231Z] gpg: keyserver receive failed: Connection timed out
[2023-02-01T09:03:32.233Z] (*) Failed getting key, retring in 10s...
[2023-02-01T09:03:42.235Z] (*) Downloading GPG key...
[2023-02-01T09:06:42.690Z] gpg: keyserver receive failed: Connection timed out
[2023-02-01T09:06:42.691Z] (*) Failed getting key, retring in 10s...
[2023-02-01T09:06:52.693Z] (*) Downloading GPG key...
[2023-02-01T09:09:53.113Z] gpg: keyserver receive failed: Connection timed out
(*) Failed getting key, retring in 10s...
[2023-02-01T09:10:03.115Z] (!) Failed to get gpg key.
[2023-02-01T09:10:03.115Z] ERROR: Feature "Terraform, tflint, and TFGrunt" (ghcr.io/devcontainers/features/terraform) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/terraform for help troubleshooting this error.
[2023-02-01T09:10:03.304Z] The command '/bin/sh -c cd /tmp/build-features/terraform_2 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh' returned a non-zero code: 1
[2023-02-01T09:10:03.306Z] Stop (956886 ms): Run: docker build --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/base:jammy --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-awslambda-012d3e83ba62a57a96c4db53135dedc8-features -f /tmp/devcontainercli-ubuntu/container-features/0.25.2-1675241641697/Dockerfile.extended /tmp/devcontainercli-ubuntu/empty-folder
[2023-02-01T09:10:03.302Z] Error: Command failed: docker build --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/base:jammy --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-awslambda-012d3e83ba62a57a96c4db53135dedc8-features -f /tmp/devcontainercli-ubuntu/container-features/0.25.2-1675241641697/Dockerfile.extended /tmp/devcontainercli-ubuntu/empty-folder
[2023-02-01T09:10:03.303Z]     at Aoe (/home/ubuntu/.vscode-remote-containers/dist/dev-containers-cli-0.266.1/dist/spec-node/devContainersSpecCLI.js:1893:1355)
[2023-02-01T09:10:03.303Z]     at uT (/home/ubuntu/.vscode-remote-containers/dist/dev-containers-cli-0.266.1/dist/spec-node/devContainersSpecCLI.js:1893:1291)
[2023-02-01T09:10:03.304Z]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[2023-02-01T09:10:03.304Z]     at async Poe (/home/ubuntu/.vscode-remote-containers/dist/dev-containers-cli-0.266.1/dist/spec-node/devContainersSpecCLI.js:1899:2128)
[2023-02-01T09:10:03.305Z]     at async Zf (/home/ubuntu/.vscode-remote-containers/dist/dev-containers-cli-0.266.1/dist/spec-node/devContainersSpecCLI.js:1899:3278)
[2023-02-01T09:10:03.305Z]     at async aue (/home/ubuntu/.vscode-remote-containers/dist/dev-containers-cli-0.266.1/dist/spec-node/devContainersSpecCLI.js:2020:15276)
[2023-02-01T09:10:03.306Z]     at async oue (/home/ubuntu/.vscode-remote-containers/dist/dev-containers-cli-0.266.1/dist/spec-node/devContainersSpecCLI.js:2020:15030)
[2023-02-01T09:10:03.307Z] Stop (962330 ms): Run in Host: /home/ubuntu/.vscode-remote-containers/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/node /home/ubuntu/.vscode-remote-containers/dist/dev-containers-cli-0.266.1/dist/spec-node/devContainersSpecCLI.js up --workspace-folder /home/ubuntu/ghq/gitlab.com/ksaito11/awslambda --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/ubuntu/ghq/gitlab.com/ksaito11/awslambda --log-level debug --log-format json --config /home/ubuntu/ghq/gitlab.com/ksaito11/awslambda/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2023-02-01T09:10:03.308Z] Exit code 1
[2023-02-01T09:10:03.314Z] Command failed: /home/ubuntu/.vscode-remote-containers/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534/node /home/ubuntu/.vscode-remote-containers/dist/dev-containers-cli-0.266.1/dist/spec-node/devContainersSpecCLI.js up --workspace-folder /home/ubuntu/ghq/gitlab.com/ksaito11/awslambda --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/ubuntu/ghq/gitlab.com/ksaito11/awslambda --log-level debug --log-format json --config /home/ubuntu/ghq/gitlab.com/ksaito11/awslambda/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root true
[2023-02-01T09:10:03.314Z] Exit code 1

I removed the feature, started the development container, and manually ran the relevant part of install.sh.
A proxy is set in the environment variable.
Running the same as install.sh times out with the same result.
I get another error when proxy is set in gpg options.
vscode ➜ ~ $ TERRAFORM_GPG_KEY="72D7468F"
vscode ➜ ~ $ GPG_KEY_SERVERS="keyserver hkp://keyserver.ubuntu.com
keyserver hkps://keys.openpgp.org
keyserver hkp://keyserver.pgp.com"
vscode ➜ ~ $ export GNUPGHOME="/tmp/tmp-gnupg"
vscode ➜ ~ $ mkdir -p ${GNUPGHOME}
vscode ➜ ~ $ chmod 700 ${GNUPGHOME}
vscode ➜ ~ $ echo -e "disable-ipv6\n${GPG_KEY_SERVERS}" > ${GNUPGHOME}/dirmngr.conf
vscode ➜ ~ $ gpg --recv-keys $TERRAFORM_GPG_KEY
gpg: keybox '/tmp/tmp-gnupg/pubring.kbx' created
gpg: keyserver receive failed: Connection timed out
vscode ➜ ~ $ gpg --keyserver-options http-proxy=$http_proxy --recv-keys $TERRAFORM_GPG_KEY
gpg: keyserver receive failed: No data
vscode ➜ ~ $ gpg --recv-keys $TERRAFORM_GPG_KEY
gpg: keyserver receive failed: Connection timed out
vscode ➜ ~ $

I'm not familiar with gpg, so I may be doing something wrong.

Hi 👋
I tried to reproduce with the devcontainer, however, my container was successful.
In the install.sh, can you append :80 to the ubuntu keyserver and give it a try?
GPG_KEY_SERVERS="keyserver hkp://keyserver.ubuntu.com:80
keyserver hkps://keys.openpgp.org
keyserver hkp://keyserver.pgp.com

@samruddhikhandale
Thank you for your support.
With the settings you gave me, the error disappeared!
Is it possible to specify this setting for features?
vscode ➜ /workspaces/devcon2 $ GPG_KEY_SERVERS="keyserver hkp://keyserver.ubuntu.com:80
keyserver hkps://keys.openpgp.org
keyserver hkp://keyserver.pgp.com"
vscode ➜ /workspaces/devcon2 $ export GNUPGHOME="/tmp/tmp-gnupg"
vscode ➜ /workspaces/devcon2 $ mkdir -p ${GNUPGHOME}
vscode ➜ /workspaces/devcon2 $ chmod 700 ${GNUPGHOME}
vscode ➜ /workspaces/devcon2 $ echo -e "disable-ipv6\n${GPG_KEY_SERVERS}" > ${GNUPGHOME}/dirmngr.conf
vscode ➜ /workspaces/devcon2 $ gpg --recv-keys $TERRAFORM_GPG_KEY
gpg: keybox '/tmp/tmp-gnupg/pubring.kbx' created
vscode ➜ /workspaces/devcon2 $ gpg --keyserver-options http-proxy=$http_proxy --recv-keys $TERRAFORM_GPG_KEY
vscode ➜ /workspaces/devcon2 $ gpg --recv-keys $TERRAFORM_GPG_KEY
vscode ➜ /workspaces/devcon2 $

@ksaito1125
I made a mistake.
I didn't set TERRAFORM_GPG_KEY.
I will try again.

@samruddhikhandale
I got an error.
vscode ➜ /workspaces/devcon $ GPG_KEY_SERVERS="keyserver hkp://keyserver.ubuntu.com:80
keyserver hkps://keys.openpgp.org
keyserver hkp://keyserver.pgp.com"
vscode ➜ /workspaces/devcon $ export GNUPGHOME="/tmp/tmp-gnupg"
vscode ➜ /workspaces/devcon $ mkdir -p ${GNUPGHOME}
vscode ➜ /workspaces/devcon $ chmod 700 ${GNUPGHOME}
vscode ➜ /workspaces/devcon $ echo -e "disable-ipv6\n${GPG_KEY_SERVERS}" > ${GNUPGHOME}/dirmngr.conf
vscode ➜ /workspaces/devcon $ cat /tmp/tmp-gnupg/dirmngr.conf
disable-ipv6
keyserver hkp://keyserver.ubuntu.com:80
keyserver hkps://keys.openpgp.org
keyserver hkp://keyserver.pgp.com
vscode ➜ /workspaces/devcon $ TERRAFORM_GPG_KEY="72D7468F"
vscode ➜ /workspaces/devcon $ gpg --recv-keys $TERRAFORM_GPG_KEY
gpg: keyserver receive failed: Connection timed out
vscode ➜ /workspaces/devcon $ gpg --keyserver-options http-proxy=$http_proxy --recv-keys $TERRAFORM_GPG_KEY
gpg: keyserver receive failed: No data
vscode ➜ /workspaces/devcon $

From https://github.com/devcontainers/features/issues/441, the error is gpg: keyserver receive failed: No name and we've seen gpg: keyserver receive failed: Connection timed out from this issue.

gpg --keyserver keyserver.ubuntu.com --recv-key 72D7468F
gpg --keyserver hkps://keys.openpgp.org --recv-key 72D7468F

@ksaito1125 @iLem0n Can you locally run any of these commands? I wonder if there's a proxy/VPN issue.

Below are the results of running some patterns.
vscode ➜ /workspaces/devcon $ gpg --keyserver keyserver.ubuntu.com --recv-key 72D7468F
gpg: keyserver receive failed: Connection timed out
vscode ➜ /workspaces/devcon $ gpg --keyserver-options http-proxy=$http_proxy --keyserver keyserver.ubuntu.com --recv-key 72D7468F
gpg: keyserver receive failed: End of file
vscode ➜ /workspaces/devcon $ gpg --keyserver-options http-proxy=$http_proxy --keyserver hkps://keys.openpgp.org --recv-key 72D7468F
gpg: keyserver receive failed: No data
vscode ➜ /workspaces/devcon $

The gpg command doesn't seem to use http_proxy, https_proxy.
vscode ➜ /workspaces/devcon $ strace gpg --keyserver keyserver.ubuntu.com --recv-key 72D7468F
...

openat(AT_FDCWD, "/usr/share/locale-langpack/en.utf8/LC_MESSAGES/gnupg2.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale-langpack/en/LC_MESSAGES/gnupg2.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, "gpg: keyserver receive failed: C"..., 51gpg: keyserver receive failed: Connection timed out) = 51
write(2, "\n", 1
)                       = 1
write(3, "BYE", 3)                      = 3
write(3, "\n", 1)                       = 1
close(3)                                = 0
munmap(0x7f6bcb2e1000, 65536)           = 0
unlink("/tmp/tmp-gnupg/.#lk0x000055d5b08daec0.049acdb81ea2.56760") = 0
exit_group(2)                           = ?
+++ exited with 2 +++
vscode ➜ /workspaces/devcon $

The environment variables are set, but the gpg command doesn't use the proxy.
vscode ➜ /workspaces/devcon $ env | grep -i http | sed -e 's/'$MASK'/xxx/'
https_proxy=http://proxy.xxx.co.jp:8080
HTTPS_PROXY=http://proxy.xxx.co.jp:8080
HTTP_PROXY=http://proxy.xxx.co.jp:8080
http_proxy=http://proxy.xxx.co.jp:8080

Setting proxy in the argument gives another error.
vscode ➜ /workspaces/devcon $ strace gpg --keyserver-options http-proxy=$http_proxy --keyserver hkps://keys.openpgp.org --recv-key 72D7468F
...

read(3, "OK", 1002)                     = 2
read(3, "\n", 1000)                     = 1
write(3, "OPTION http-proxy=http://proxy."..., 49) = 49
write(3, "\n", 1)                       = 1
read(3, "OK", 1002)                     = 2
read(3, "\n", 1000)                     = 1
write(3, "KEYSERVER --clear hkps://keys.op"..., 41) = 41
write(3, "\n", 1)                       = 1
read(3, "OK", 1002)                     = 2
read(3, "\n", 1000)                     = 1
write(3, "KS_GET -- 0x72D7468F", 20)    = 20
write(3, "\n", 1)                       = 1
read(3, "ERR 167772346 No keyserver avail"..., 1002) = 46
read(3, "\n", 956)                      = 1

...

write(2, "gpg: keyserver receive failed: N"..., 53gpg: keyserver receive failed: No keyserver available) = 53
write(2, "\n", 1
)                       = 1
write(3, "BYE", 3)                      = 3
write(3, "\n", 1)                       = 1
close(3)                                = 0
munmap(0x7f3356d1e000, 65536)           = 0
unlink("/tmp/tmp-gnupg/.#lk0x000055d8a81f5e90.049acdb81ea2.57289") = 0
exit_group(2)                           = ?
+++ exited with 2 +++
vscode ➜ /workspaces/devcon $

The proxy has a self-signed intermediate certificate. I'm not sure how to properly set up intermediate certificates in gpg.

From #441, the error is gpg: keyserver receive failed: No name and we've seen gpg: keyserver receive failed: Connection timed out from this issue.

gpg --keyserver keyserver.ubuntu.com --recv-key 72D7468F

gpg --keyserver hkps://keys.openpgp.org --recv-key 72D7468F

@ksaito1125 @iLem0n Can you locally run any of these commands? I wonder if there's a proxy/VPN issue.

Tried it locally:
$> gpg --keyserver hkps://keys.openpgp.org --recv-key 72D7468F
gpg: keyserver receive failed: Network is unreachable

but network works fine and site itself is reachable. Tested it with: curl keyserver.ubuntu.com which returns the full html of the site.
Same happens when I leave the corporate network and bypass the proxy with
HTTP_PROXY="" HTTPS_PROXY="" http_proxy="" https_proxy="" gpg --keyserver keyserver.ubuntu.com --recv-key 72D7468F

Few clarifying questions,

Are you able to use other Features which uses gpg signing? (eg. ruby, python, powershell, nix) - I would like to narrow down if the problem is with one Feature or every Feature which uses GPG.
Can you pin the terraform Feature to 1.1.0, rebuild the container and see if the issue is resolved? That's when we switched to not using port 80 for keyservers - https://github.com/devcontainers/features/pull/353/files
As mentioned in this PR https://github.com/devcontainers/features/pull/397/files, does adding the <IP_ADDRESS> nameserver fix the issue for you? We have seen cases where company DNS doesn't auto resolve servers and are flakey on some company machines due to network policies.

After changing the protocol of the key server to hkps with reference to Use HKPS (HKP over TLS) on stackoverflow below, the error disappeared.
https://serverfault.com/questions/168826/how-to-install-gpg-keys-from-behind-a-firewall
codespace ➜ /workspaces/devcon-sandbox (terraform) $ TERRAFORM_GPG_KEY="72D7468F"
codespace ➜ /workspaces/devcon-sandbox (terraform) $ GPG_KEY_SERVERS="keyserver hkps://keyserver.ubuntu.com
> keyserver hkps://keys.openpgp.org
> keyserver hkps://keyserver.pgp.com"
codespace ➜ /workspaces/devcon-sandbox (terraform) $ export GNUPGHOME="/tmp/tmp-gnupg"
codespace ➜ /workspaces/devcon-sandbox (terraform) $ mkdir -p ${GNUPGHOME}
codespace ➜ /workspaces/devcon-sandbox (terraform) $ chmod 700 ${GNUPGHOME}
codespace ➜ /workspaces/devcon-sandbox (terraform) $ echo -e "disable-ipv6\n${GPG_KEY_SERVERS}" > ${GNUPGHOME}/dirmngr.conf
codespace ➜ /workspaces/devcon-sandbox (terraform) $ gpg --keyserver-options http-proxy=$http_proxy --recv-keys $TERRAFORM_GPG_KEY
gpg: keybox '/tmp/tmp-gnupg/pubring.kbx' created
gpg: /tmp/tmp-gnupg/trustdb.gpg: trustdb created
gpg: key 34365D9472D7468F: public key "HashiCorp Security (hashicorp.com/security<EMAIL_ADDRESS>imported
gpg: Total number processed: 1
gpg:               imported: 1
codespace ➜ /workspaces/devcon-sandbox (terraform) $

I created a pull request.
@samruddhikhandale

Thank you @ksaito1125 , much appreciated. Left some thoughts.

Few clarifying questions,

Are you able to use other Features which uses gpg signing? (eg. ruby, python, powershell, nix) - I would like to narrow down if the problem is with one Feature or every Feature which uses GPG.
Can you pin the terraform Feature to 1.1.0, rebuild the container and see if the issue is resolved? That's when we switched to not using port 80 for keyservers - https://github.com/devcontainers/features/pull/353/files
As mentioned in this PR https://github.com/devcontainers/features/pull/397/files, does adding the <IP_ADDRESS> nameserver fix the issue for you? We have seen cases where company DNS doesn't auto resolve servers and are flakey on some company machines due to network policies.

Greetings. to answer your question # 1 : I discovered the same issue attempting to use the python feature using:
		"ghcr.io/devcontainers/features/python:1": { 			"version":"3.7" 		}
Following your fix, I ran the install.sh script from within my postCreateCommand script and it did install correctly.

Hello @ksaito1125, @samruddhikhandale,
thank you so much for the fix 🙏🏻
Unfortunately I still have problems getting the feature to work. With 1.3.0 using the HttpProxy option I get the following:
#0 0.149 ===========================================================================
#0 0.149 Feature       : Terraform, tflint, and TFGrunt
#0 0.149 Description   : Installs the Terraform CLI and optionally TFLint and Terragrunt. Auto-detects latest version and installs needed dependencies.
#0 0.149 Id            : ghcr.io/devcontainers/features/terraform
#0 0.149 Version       : 1.3.0
#0 0.149 Documentation : https://github.com/de
[2023-03-07T08:19:02.875Z] vcontainers/features/tree/main/src/terraform
#0 0.149 Options       :
#0 0.149     VERSION="1.3.7"
#0 0.149     TFLINT="0.44.1"
#0 0.149     TERRAGRUNT="0.42.8"
#0 0.149     INSTALLSENTINEL="false"
#0 0.149     INSTALLTFSEC="true"
#0 0.149     INSTALLTERRAFORMDOCS="false"
#0 0.149     HTTPPROXY="http://<my-proxy-user>:<my-proxy-pass>@<corporate-proxy-url>:<corporate-proxy-port>"
#0 0.149 ===========================================================================
#0 0.222 fatal: unable to access 'https://github.com/hashicorp/terraform/': Empty reply from server
#0 0.226 Invalid TERRAFORM_VERSION value: 1.3.7
#0 0.226 Valid values:
#0 0.226
#0 0.226 ERROR: Feature "Terraform, tflint, and TFGrunt" (ghcr.io/devcontainers/features/terraform) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/terraform for help troubleshooting this error.

dev container.json:
{
	"name": "Minimal example",
	"build": {
		"dockerfile": "Dockerfile",
		"args": {
			"HTTP_PROXY": "http://<my-proxy-user>:<my-proxy-pass>@<corporate-proxy-url>:<corporate-proxy-port>",
			"HTTPS_PROXY": "http://<my-proxy-user>:<my-proxy-pass>@<corporate-proxy-url>:<corporate-proxy-port>",
			"http_proxy": "http://<my-proxy-user>:<my-proxy-pass>@<corporate-proxy-url>:<corporate-proxy-port>",
			"https_proxy": "http://<my-proxy-user>:<my-proxy-pass>@<corporate-proxy-url>:<corporate-proxy-port>"
		}
	},
	"features": {
		"ghcr.io/devcontainers/features/terraform:1.3.0": {
			"version": "1.3.7",
			"tflint": "0.44.1",
			"terragrunt": "0.42.8",
			"installTFsec": true,
			"httpProxy": "http://<my-proxy-user>:<my-proxy-pass>@<corporate-proxy-url>:<corporate-proxy-port>"
		}
	}
}

@iLem0n hello!
In my environment, the code below is working.
{
	"name": "Ubuntu",
	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
	"image": "mcr.microsoft.com/devcontainers/base:jammy",
	"features": {
		"ghcr.io/devcontainers/features/terraform:1": {}
	}
}

Step 12/15 : RUN chmod -R 0700 /tmp/build-features/terraform_1 && cd /tmp/build-features/terraform_1 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh
 ---> Running in a4753f2d4a6f
===========================================================================
Feature       : Terraform, tflint, and TFGrunt
Description   : Installs the Terraform CLI and optionally TFLint and Terragrunt. Auto-detects latest version and installs needed dependencies.
Id            : ghcr.io/devcontainers/features/terraform
Version       : 1.3.0
Documentation : https://github.com/devcontainers/features/tree/main/src/terraform
Options       :
    VERSION="latest"
    TFLINT="latest"
    TERRAGRUNT="latest"
    INSTALLSENTINEL="false"
    INSTALLTFSEC="false"
    INSTALLTERRAFORMDOCS="false"
    HTTPPROXY=""
===========================================================================
TERRAFORM_VERSION=1.3.9
TFLINT_VERSION=0.45.0
TERRAGRUNT_VERSION=0.44.4
Downloading terraform...
(*) Downloading GPG key...
gpg: Signature made Wed Feb 15 17:25:31 2023 UTC
gpg:                using RSA key 374EC75B485913604A831CC7C820C6D5CD27AB87
gpg: Good signature from "HashiCorp Security (hashicorp.com/security<EMAIL_ADDRESS>[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: C874 011F 0AB4 0511 0D02  1055 3436 5D94 72D7 468F
     Subkey fingerprint: 374E C75B 4859 1360 4A83  1CC7 C820 C6D5 CD27 AB87
terraform_1.3.9_linux_amd64.zip: OK
Archive:  terraform_1.3.9_linux_amd64.zip
  inflating: terraform
Downloading tflint...
gpg: Signature made Sun Feb 12 16:04:43 2023 UTC
gpg:                using RSA key 1780244FBAEB62C74476BE498CE69160EB3F2FE9
gpg: Good signature from "Kazuma Watanabe<EMAIL_ADDRESS>[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 2DA7 A4B1 1347 B217 3852  31D1 131A 2054 C7B3 FB65
     Subkey fingerprint: 1780 244F BAEB 62C7 4476  BE49 8CE6 9160 EB3F 2FE9
tflint_linux_amd64.zip: OK
Archive:  /tmp/tf-downloads/tflint_linux_amd64.zip
  inflating: tflint
Downloading Terragrunt...
terragrunt_linux_amd64: OK
Done!
Removing intermediate container a4753f2d4a6f
 ---> 4dfbf6428bd4

Setting the same option worked as well.
{
	"name": "Ubuntu",
	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
	"image": "mcr.microsoft.com/devcontainers/base:jammy",
	"features": {
		"ghcr.io/devcontainers/features/terraform:1": {
			"version": "1.3.7",
			"tflint": "0.44.1",
			"terragrunt": "0.42.8",
			"installTFsec": true,
			"httpProxy": "http://proxy.xxx.co.jp:8080"
		}
	}
}

@iLem0n
My docker environment has two proxies:
I hope it will be helpful.
This setting is required when the docker daemon pulls images.
ubuntu@ip-10-15-83-125:~/.docker$ head -2 /etc/systemd/system/docker.service.d/override.conf | sed -e 's/'$MASK'/xxx/g'
[Service]
Environment="HTTP_PROXY=http://proxy.xxx.co.jp:8080" "HTTPS_PROXY=http://proxy.xxx.co.jp:8080" "NO_PROXY=localhost,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,.xxx.co.jp"

I've followed this documentation to set up a proxy in docker.
By using this setting, the http_proxy will be set in the started container.
ubuntu@ip-10-15-83-125:~$ cat ~/.docker/config.json | jq '.proxies' | sed -e 's/'$MASK'/xxx/g'
{
  "default": {
    "httpProxy": "http://proxy.xxx.co.jp:8080",
    "httpsProxy": "http://proxy.xxx.co.jp:8080",
    "noProxy": "localhost,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,xxx.co.jp"
  }
}


filter view with multiple tags

Right now when clicking on a tag when another tag filter is already applied, the new tag replaces the old one.

solved by #12


Em 6168 update sanitise method

Jira link (if applicable)
https://tools.hmcts.net/jira/browse/EM-6168
Change description
Em 6168 update sanitise method due to error in pdf box lookup table

NOt required as of now


Update xcall interface to not use structs, and CallParams to include all info used to generate transferIds

1887 merged into 1807, closing this one out


Word wrap plain text project descriptions

What's the problem this feature will solve?
Since https://github.com/pypi/warehouse/commit/2116945657693114231d22697d7ec7f6cfe08578 (I suppose), plain text project descriptions (eg, "readme.txt") are displayed on pypi as html pre-formatted text (<pre>). This is good. However, this means they don't word wrap, which makes them far more annoying to read; if the line is significantly long, the user must horizontally scroll a lot. Here's a screenshot from my project, https://pypi.org/project/golgotha/

Describe the solution you'd like
The pre-formatted text should word-wrap.
This is (should be?) absolutely trivial in modern HTML&CSS. You just have to add white-space: pre-wrap; to the style of the element.
Additional context
I would open up a pull request to make this change myself, but I'm not sure what this project considers the "right" way to add CSS (which file does it go in, or does it just get attached to the element, does it go in a pre {} rule or some more specific class rule, etc).

Hi, thanks for the issue. One of the reasons why we haven't applied word-wrapping to plaintext project descriptions is because sometimes this may have the effect of wrapping descriptions that users don't want to wrap, for example if a description has an ASCII table, ASCII art, etc, without any way to prevent it from happening.
For users that do want word wrapping, we would recommend using Markdown for your description instead, but I'm curious if there there is any reason why this won't work for you in this case?

Good considerations. I think anyone making ASCII art/tables that are quite wide must suspect that systems won't display them properly, but I can see the argument for supporting them anyway, even at the expense of The presentation of normal text. If the design decision here has been resolved definitively, feel free to close this issue.
There's no particular reason I can't use markdown for my readme — except, of course, the inconvenience of making sure everything in the markdown file is properly escaped if it needs to be.

Good considerations. I think anyone making ASCII art/tables that are quite wide must suspect that systems won't display them properly, but I can see the argument for supporting them anyway, even at the expense of The presentation of normal text.

Consider also that PyPI is also frequently browsed on mobile devices, so a plaintext description would not have to be very wide to trigger horizontal scrolling or word wrapping.

There's no particular reason I can't use markdown for my readme — except, of course, the inconvenience of making sure everything in the markdown file is properly escaped if it needs to be.

I suspect that you would be able to change the extension of your readme to .md and it will just work, Markdown only requires additional syntax if you are trying to move beyond plaintext to formatted text.

If the design decision here has been resolved definitively, feel free to close this issue.

I don't think we have any plans to change this for now, so I will close, but thanks for raising it!


Metronome 0.4.2 Bump for DCOS 1.10.next

High-level description
Metronome bump 0.4.2 on DCOS 1.10.6
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

METRONOME-248Metronome metrics breaking change

Related tickets (optional)
Checklist for all PRs

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): diff 0.4.1...0.4.2
[x] Test Results: https://jenkins.mesosphere.com/service/jenkins/view/Metronome/job/Metronome/job/metronome-pipelines/job/master/67/
[ ] Code Coverage (if available): N/A

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@kensipe, you must be a member of the Mesosphere organization to issue this command.

@mesosphere-mergebot bump-ee

@kensipe, you must be a member of the Mesosphere organization to issue this command.

@mesosphere-mergebot label ready for review

The EE PR has a ship-it. Applying a ship-it with owner perms.

The EE was not updated after the open bump.

@mesosphere-mergebot bump-ee

Your pull request's branch is not based on the most recent version of 1.10. Please rebase your changes against this repo's 1.10 branch.

@mesosphere-mergebot label  ship-it

Applying a ship-it with owner perms.

As PR was created 2 days ago and we were dealing with mergebot infra issues (due to rate limiting).

We will testing this as part of train again.


pageYOffset has better support than scrollTop

win.scrollTop is undefined on IE 10/11/Edge, this change fixed it.
The option useStickyClasses is irrelevant if the scroll value is undefined, that's why I made this change.

@eddiesigner thank you! Will add this asap 🙏


Battery status 'FAIL'

Hi Community,
since today my dashboard is frozen wit the status 'FAIL'.

I already restarted the docker host, recreated the images & restarted the battery unit. Any help on what I should do next for investigation would be awesome!
Thank you all in advance & kind regards
Timo

wrong repo


Finish upgrade to M67

Finish upgrade to M67:

Copy SurfaceViewRenderer from latest version of WebRTC
Get rid of org.webrtc.VideoRenderer.Callbacks in TextureViewRenderer
Fix merge conflicts in WebRTCView

@bvic23 It's a new interface in WebRTC, it's meant to replace org.webrtc.VideoRenderer.Callbacks


[WIP]feat(*): developer focused demo using StoryBook - I315

Signed-off-by: elit-altum<EMAIL_ADDRESS>Issue #315
Changes

Currently added @storybook/react as a dev dependency and script to start storybook.
This is currently for staging purpose

Related Issues

Issue #315

@sanyamdogra I think we can start from here.
Please go through  https://stackoverflow.com/questions/41588025/git-github-push-to-someone-elses-fork-of-my-repo. I think this is a good way to collaborate on a single PR. What do you say?

@irmerk needed your thoughts on some initial settings

Where should we write and store the stories, as in what directory should we use? Storybook recommends co-locating in the src folder itself.
Is the script to run storybook okay? I used the recommended npm run storybook

@sanyamdogra I think we can start from here.
Please go through https://stackoverflow.com/questions/41588025/git-github-push-to-someone-elses-fork-of-my-repo. I think this is a good way to collaborate on a single PR. What do you say?

Well I don't think I'll be comfortable on working on a same PR. It'll lead to discrepancies in future. This might make sense have made sense if we use the same fork.

@irmerk needed your thoughts on some initial settings

Where should we write and store the stories, as in what directory should we use? Storybook recommends co-locating in the src folder itself.
Is the script to run storybook okay? I used the recommended npm run storybook

We will include a . stories.js for every component present in the project.
Yes npm run storybook looks good to me.

@sanyamdogra I think we can start from here.
Please go through https://stackoverflow.com/questions/41588025/git-github-push-to-someone-elses-fork-of-my-repo. I think this is a good way to collaborate on a single PR. What do you say?

Well I don't think I'll be comfortable on working on a same PR. It'll lead to discrepancies in future. This might make sense have made sense if we use the same fork.

Unsure of what you asked for. Are you referring to collaborator access to a fork? Yes I will have to provide you that on my fork.

I think working off a fork and building a draft PR from that fork would be best.
Script seems fine. And I would presume to follow what they say in their docs, so colocating sounds fine.

@sanyamdogra I think we can start from here.
Please go through https://stackoverflow.com/questions/41588025/git-github-push-to-someone-elses-fork-of-my-repo. I think this is a good way to collaborate on a single PR. What do you say?

Well I don't think I'll be comfortable on working on a same PR. It'll lead to discrepancies in future. This might make sense have made sense if we use the same fork.

Unsure of what you asked for. Are you referring to collaborator access to a fork? Yes I will have to provide you that on my fork.

Alright then. Provide me access to your fork. I hope it doesn't affect mine. Let us also discuss about a roadmap but on this issue #355.

@sanyamdogra fixed the failing builds. Separated other's commits for easy squashing at the end.

Hi @elit-altum, can you please fix the build? After that, I guess initial setup of the Storybook is done. We can get it reviewed by the team. I have added dummy stories that can be tackled one at a time.

@elit-altum I guess you'll have to change the directed PR to development rather than master.

Screenshots:

This looks like a good starting point! What are the next steps? With this in place, people will be able to go ahead and update the individual .stories files and add new .stories files for components that don't get have one?

Yes, we'll be able to write stories for every component that is used in cicero-ui.They can be checked in isolation and even tested. We'll still have to write stories for these components but that can be covered in individual PRs.

This looks like a good starting point! What are the next steps? With this in place, people will be able to go ahead and update the individual .stories files and add new .stories files for components that don't get have one?

Yes, we'll be able to write stories for every component that is used in cicero-ui.They can be checked in isolation and even tested. We'll still have to write stories for these components but that can be covered in individual PRs.

Sounds great to me!
It looks like some of your commits are missing the DCO signoff. You'll have to update your PR so that there no no commits without the signoff.

This looks like a good starting point! What are the next steps? With this in place, people will be able to go ahead and update the individual .stories files and add new .stories files for components that don't get have one?

Yes, we'll be able to write stories for every component that is used in cicero-ui.They can be checked in isolation and even tested. We'll still have to write stories for these components but that can be covered in individual PRs.

Sounds great to me!
It looks like some of your commits are missing the DCO signoff. You'll have to update your PR so that there no no commits without the signoff.

Me and @elit-altum tried hard to fix the build. The last commit has the DCO, somehow the travis is not building.

I don't know how it messed up the package-lock.json. Me and @elit-altum have tried to fix this but it's all scrambled. Closing this PR and making a new one.

Closing for #353, @elit-altum make sure that PR isn't missing anything from this one.


Unable to subscribe to futures options greeks

          I tested it and can get `equity option` quotes and `future options` quotes.

          interestingly, I can get option quotes for `SPX`, but not for `SPX` itself.

          `greeks` seem not to work

Originally posted by @zlymeda in https://github.com/tastytrade/tastytrade-api-js/issues/7#issuecomment-2051106604

I'll check on the greeks. We might only offer the quote market event.
As for SPX, our offering only covers nasdaq basic equities, not indices.

I'll check on the greeks. We might only offer the quote market event for api users.
As for SPX, our offering only covers nasdaq basic equities, not indices.

Hi @dmoss18, I'm the maintainer of the unofficial Python SDK and we're getting a lot of complaints over the last week. We were using the /quote-streamer-tokens endpoint (for DXLink) and were unaware that it had changed. So now I'm looking to move to /api-streamer-tokens to fix connection issues that recently came up, but we're having issues with unsupported symbols (namely, SPX). Is this something the Tastytrade team is working on? From my experience the number of people doing SPX-related strategies on Tasty is surprisingly high.

can you share code on how you're pulling options on futures quotes? I'm able to pull options on equities but not futures? TIA!

@syaffa12 I just updated the README with an example for you. Lmk if works for you.
https://github.com/tastytrade/tastytrade-api-js?tab=readme-ov-file#market-data

Thank you very much. Unfortunately I'm not much of a coder and it looks
like I need to pay for  @dxfeed
https://github.com/dxFeed/dxLink/blob/main/dxlink-javascript/dxlink-api/README.md
anyways,
so I'm going to use Barchart instead for my analysis purposes.
Interestingly, I was able to pull options for stocks quite easily. It's
proving more complicated for options on futures.
On Thu, Jul 11, 2024 at 2:52 PM Devin Moss @.***> wrote:

@syaffa12 https://github.com/syaffa12 I just updated the README with an
example for you. Lmk if works for you.
https://github.com/tastytrade/tastytrade-api-js?tab=readme-ov-file#market-data
—
Reply to this email directly, view it on GitHub
https://github.com/tastytrade/tastytrade-api-js/issues/40#issuecomment-2223666317,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDZO5MEE7SZCDX5FWC2PJTZL3H6VAVCNFSM6AAAAABGEPRO6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRTGY3DMMZRG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
@.***


GroupingChooserModel.dimensions should be settable/updatable

Adding to backlog - if there is any extra priority or push from a client around this pls give a shout.

No push or priority. I'm just using a less desirable component to achieve my ends. The client has no problem with what they have now.

One thing to check here is to ensure that the model handles things reasonably in the case where it already has a current value (a list of selected dimensions to group on) and then a new set of available dimensions is set via this new API. If the current value includes a dimension that is no longer supported, we need to modify it.
We could either clear out the value entirely, or we could strip out only dimensions that are no longer supported.  I.e. a groupingChooserModel with value [portfolio, strategy, trader] would have its value automatically reset to [portfolio, trader] if a caller set groupingChooserModel.dimensions = [portfolio, trader, country]


Reference Template Modification Required (Variables to Parameters)

The revised template example need to be modified from... variables('appServicePlanName') to parameters('appServicePlanName')
Else it produces the error:
Azure Error: InvalidTemplate
Message: Deployment template validation failed: 'The template variable 'appServicePlanName' is not found.

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

ID: 6282c12f-4b27-34ae-db61-6db7e36cb06f
Version Independent ID: f30d8eee-f902-db26-66a4-e5c45a3e68dd
Content: Tutorial - Use Azure Quickstart templates
Content Source: articles/azure-resource-manager/template-tutorial-quickstart-template.md
Service: azure-resource-manager
GitHub Login: @mumian
Microsoft Alias: jgao

@AErmie Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update.

The feedback is being shared with the content owner for visibility, further review and document enhancement considerations.


Document the --open option

I've just found the --open option by accident (https://github.com/lwsjs/local-web-server/commit/c77b6234bc7d6d209254ec6d92579c17ee44a1f6). Maybe add it to the readme?

I've added the following link to the wiki:

How to launch a browser together with the server

Let me know if you find anything else. 👍

Cool, thank you @75lb!


Migrate UIImage APIs to using UIImageAsset on iOS13

The code about UIImage change is basically from #79
DMTraitCollection.currentTraitCollection is marked as deprecated for all OSes including iOS 11 & 12

@zhuorantan @li-bei this should be a trivial change, and is ready for review


feat(model): Support Mixtral-8x7B

Closes #956
Other

Refactor model adapter

The idea of abstracting an adapter into a standalone module to manage the adaptation of models under different architectures and different inference frameworks is brilliant. I will take a look at the related code later to continuously improve.

The idea of abstracting an adapter into a standalone module to manage the adaptation of models under different architectures and different inference frameworks is brilliant. I will take a look at the related code later to continuously improve.

Yes, we can also import only the required dependencies.

With the introduction of chat_templating in huggingface, most model adaptations will be simpler, and we do not have to rely on FastChat.


Missing edges between the ECS-demo containers

Steps to reproduce.

Launch the scope variant of the ECS demo (which uses scope:latest)

git clone -b aws-ecs-scope git@github.com:weaveworks/guides.git
cd guides/aws-ecs
./setup

   Which should output three urls let's call them `u1`, `u2`, `u3`.

2. Make sure that the Http Servers are communicating with the Data Producers:

  ```bash
  while true; do
    for I in u1 u2 u3; do
      curl $I
    done
  done

Open Scope in any of the three instances (e.g. u1:4040)
The HttpServer and DataProducers ( the ecs-weave-ecs... containers) should be connected since they are communicating with each other. However they are not.

In fact, I also expect an edge between all the weavescope containers since every probe is reporting to all the apps.

@2opremio attaching the contents of /api/report and /api/topology/containers to bugs like this will massively help narrow it down.

There you go https://gist.github.com/2opremio/9494a1f48b340a620526

I've figured this out.
My bad.

Great that you figured it out. Out of curiosity, can you elaborate on what's causing it?

I thought I had it but I didn't. Sorry.  Still working on it.

Any update here? This is the only remaining release-blocker.

The attached or fixes some issues but doesn't fix it 100%.
I've got two test cases: cross host communication over the weave network,
and cross host communication via docker port mapping.  (1) works now, (2)
doesn't.
I don't know why it doesn't work yet.
Feel free to review the pr, I see no reason why it can't go in.
On Saturday, September 12, 2015, Peter Bourgon<EMAIL_ADDRESS>wrote:

Any update here? This is the only remaining release-blocker.
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/issues/446#issuecomment-139602851.

This is mostly fixes - pseudo nodes are working again, and short lived connections from containers to the internet are working.
But the short lived connection code doesn't deal with connections coming from the internet, as they go to the hosts IP, not the containers.  We know the port mapping for containers, so we should be able to fix this.  See #493


Fix python model parsing from meder

resolves https://github.com/dbt-labs/dbt-core/issues/6976
Bring #7740 over finish line by adding a unittest. Thanks @mederka for adding it!

Opened a new issue in dbt-labs/docs.getdbt.com: https://github.com/dbt-labs/docs.getdbt.com/issues/4838


Add user-assigned identity sample.

Sample includes creating a user-assigned identity, then adding and
removing one from a VM.
Thanks for your contribution! Please let us know what problems this PR addresses or what functionality it adds. Please link to other related issues and PRs to speed up review. Thank you!

Hi @jhendrixMSFT , are there sample golang project for pacakge resourcegraph from azure-sdk-for-go? (https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/services/resourcegraph/mgmt/2019-04-01/resourcegraph?tab=overview)

Hello @grumblegirl, unfortunately there isn't a sample for that package at present.  Please feel free to open an issue to track this request however I don't know when we'll be able to get to it.
CC @ArcturusZhang


Cosmos DB account does not have a "Replicate data globally" menu option

I'm attempting to change the region my Cosmos DB account is in following this documentation "https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-manage-database-account#addremove-regions-from-your-database-account". It states that I need to select the "Replicate data globally" menu from the account page but there is nothing called that on the Cosmos DB account page.
Was that renamed to something different? Does this documentation need to be updated?

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

ID: 1555e87b-459c-1f2b-1591-46730e141189
Version Independent ID: d48e5b51-745c-8ee2-e3e1-ccca4c5426b4
Content: Learn how to manage database accounts in Azure Cosmos DB
Content Source: articles/cosmos-db/how-to-manage-database-account.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @seesharprun
Microsoft Alias: sidandrews

@jberry777 We are looking into this and will get back shortly.

#reassign:seesharprun

Hello Sidney,
Thank you for the follow up email and the screenshot. I've included a
screenshot of the Cosmos DB account resource page as I see it and that
option is missing.
[image: image.png]
On Tue, Jul 19, 2022 at 6:36 AM Sidney Andrews @.***>
wrote:

@jberry777 https://github.com/jberry777, the Replicate data globally
option is in the resource menu:
[image: image]
https://user-images.githubusercontent.com/5067401/179763409-8c19a22d-79e6-4595-a29c-fc7febeb0f6a.png
The doc will be updated shortly to be a bit clearer about this. Thanks!
#please-close
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/95893#issuecomment-1189063613,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK5HIRUEXB52DXGRCWNCEDLVU2VMZANCNFSM5357RU4A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Regards,
Joshua Berry
Cloud Security

Unfortunately the image did not get posted correctly.

Do you have a serverless account? This option won't show up for a serverless account:

Thanks, yes this is a serverless account. It turns out I don't need to  change regions. Cosmos DB is able to communicate with the Function App when placed into the same Vnet subnet.


Added Editing and Delete feature for Admin Resources Page

@fardinGG Yo could you check the node server file to make sure I covered everything once.


[v10] LocalOsmosis Mainnet State

Background
Smart contract developers have expressed a desire to be able to spin up a local net that mirrors the current mainnet state.
Suggested Design
In order to run a local network based on mainnet, you need to posses a majority of the voting power in order to produce blocks. The way we currently achieve this is we change the private key and self delegation address of one of the top validators to one we own and mint a lot of coins to that address. This has worked relatively well until superfluid staking. Superfluid intermediary accounts are created based on the address of the validator being delegated to along with the denom being delegated. Since we are changing the validator address, these intermediary accounts break and cause panics on genesis initialization. @p0mvn created a branch to temporarily fix this (https://github.com/osmosis-labs/osmosis/pull/1473), but this needs to be addressed prior to creating a semi-automated method for smart contract developers to use locally.
Potential courses of action:

[ ] Figure out a way to programmatically fix these intermediary accounts. We could make this simpler by forcing people to use the same test account, therefore making the resulting intermediary accounts the same every time and we could find and replace them. Even if we have the same address every time, there are endless denoms that will be created, so it might be a cat and mouse game unless someone can create a fully automated way to switch these intermediary accounts out.
OR
[ ] Create a validator on mainnet with this dummy account. Now on all future state exports, instead of replacing Sentinels address we replace this address. Since it has no superfluid connections, this wont produce any errors on initialization. Downside: we don't get to utilize all of the account connections that Sentinel has, thereby making the local state less closer to prod.

Acceptance Criteria

[ ] Chose one of the two options above (or any other option that someone else can think of)
[ ] Create a simple to follow process that smart contract developers can follow to clone mainnet state onto to their local testing environment
[ ] Ensure users understand the time and system requirements to run this

@p0mvn @sunnya97 @ValarDragon, please advise on which option you feel is best, or if there is another option that is better.

Do we actually need to change the validator operator address of the top validator?  Could we not just change the consensus key, and then mint them a lot more coins?

The operator address is linked to the priv_validator_key correct? If we dont change their pubkey to match the one we have locally, then we cant sign blocks right? I could be wrong and could be misunderstanding

Validators have two keys, their account keys (on which operator addresses are generated) and consensus keys (what they use for signing tendermint blocks).
Operator keys are probably widespread used for indexing in different places like superfluid and stuff, but I imagine that consensus keys are not.  Pretty sure the only place they're stored is in the validator struct
https://github.com/cosmos/cosmos-sdk/blob/main/x/staking/types/validator.go#L50

I will look into doing this then, as that would be the least intrusive option. Thanks!


Add jemalloc compat functions.

This adds the full set of jemalloc functions that FreeBSD's libc
exposes, including some (the *allocm family) that are gone from newer
versions of jemalloc and the *allocx family that replaced them.  These
are not necessarily efficient implementations but they should allow
snmalloc to replace jemalloc without any ABI breakage (in the loosest
possible sense).
Jemalloc provides a very generic sysctl-like mechanism for setting and
getting some values.  These are all implemented to return the
not-supported error code.  This may break code that expects that they
will succeed.
In particular, these APIs are used to register custom backing-store
allocators and to manage caches and arenas.  These concepts don't map
directly onto snmalloc and attempting to do so would almost certainly
not provide the same performance characteristics and so it's better to
LD_PRELOAD jemalloc (or explicitly link to it) for programs that gain
a significant speedup from this.

Note: We are currently missing tests for all of these.  I intend to fix that before it is merged.

@davidchisnall I also wonder if this would be better in a
override/jemalloc_compat.cc

or
override/freebsd_libc_extras.cc

Just to make it more separated out.  There is already quite a lot of functionality in malloc.cc.


Update dependencies

Codecov Report

Merging #97 (fe829ff) into master (105ad23) will decrease coverage by 0.16%.
The diff coverage is 100.00%.

:exclamation: Current head fe829ff differs from pull request most recent head b3635ab. Consider uploading reports for the commit b3635ab to get more accurate results

@@            Coverage Diff             @@
##           master      #97      +/-   ##
==========================================
- Coverage   93.90%   93.73%   -0.17%
==========================================
  Files          14       13       -1
  Lines         705      623      -82
==========================================
- Hits          662      584      -78
+ Misses         43       39       -4

Impacted Files
Coverage Δ

src/core/options.jl
100.00% <ø> (ø)

src/core/data.jl
100.00% <100.00%> (ø)

src/plots/plot.jl
96.15% <100.00%> (-0.21%)
:arrow_down:

src/core/configuration.jl
77.77% <0.00%> (-11.12%)
:arrow_down:

src/core/utils.jl
88.46% <0.00%> (-6.14%)
:arrow_down:

src/experimental/experimental.jl
51.51% <0.00%> (-1.43%)
:arrow_down:

src/layouts/common.jl
94.33% <0.00%> (-0.40%)
:arrow_down:

src/core/types.jl
100.00% <0.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


[Feature Request] Selective Logging to TensorBoard - mainly image observations

Hi,
I am currently finding that long runs are using a lot of disk space and memory in the tensorboard logs.
Being able to selectively log what data I need in tensorboard would be helpful in reducing space used.
My current solution involves commenting out the relevant logging lines in the RL Algorithm code but this solution isn't elegant for others.

This high disk usage will be fixed when #185 is merged.


Getting error while sending test data using curl in local server

Getting error while sending test data using curl in local server
app.py: return self.view_functionsrule.endpoint
File "app.py", line 28, in get_prediction
data = np.array(data)[np.newaxis, :]  # converts shape from (4,) to (1, 4)
IndexError: too many indices for array
<IP_ADDRESS> - - [31/Mar/2020 16:06:23] "POST /predict HTTP/1.1" 500 -_
Curl post: _curl -X POST <IP_ADDRESS>:5000/predict -H 'Content-Type:application/json' -d '[5.9,3.0,5.1,1.8]'

500 Internal Server Error
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application._

request.json() is returning none @Abhijit5676  thats the cause of this error

@Abhijit5676  try this it works
curl -i -X POST -H "Content-Type:application/json" -d "[5.9,3.0,5.1,1.8]" http://localhost:5000/predict


Create Enum for Bot Events

Hi there,
In your discord bot, I found this example:
  _ = client.On("ready", event.OnReady(client, cmdManager))
  _ = client.On("interactionCreate", cmdManager.Handler(client))
  _ = client.On("guildMemberAdd", event.OnGuildMemberAdd(client))

and as a professional software developer I want to have a list of possible server events suggested by my ide, so I would suggest to create a custom type of string, so the code could look like this:
  import "github.com/Goscord/goscord/goscord/events"
  _ = client.On(events.EventReady, event.OnReady(client, cmdManager))
  _ = client.On(events.EventInteractionCreate, cmdManager.Handler(client))
  _ = client.On(events.EventGuildMemberAdd, event.OnGuildMemberAdd(client))

see in the node js documentation: https://discordjs.guide/creating-your-bot/event-handling.html#individual-event-files

ima push something in dev branch.

For documentation reason, I would appreciate it if you could also paste the future answer to this issue so people from Google can find it as well :)

Refactored event system

For documentation reason, I would appreciate it if you could also paste the future answer to this issue so people from Google can find it as well :)

On the next version of our website, we are preparing more relevant documentation and examples.
This should arrive at the same time as the V1 of Goscord.


Style attribute not being returned

The Quill editor on my page saves both the delta and the HTML content to the DB. Since I don't want to load a Quill instance to display the HTML in view-only pages, i use the saved HTML(from my understanding having the HTML is better from an SEO perspective).  This HTML page will then have an Edit button that would then open the editor in a modal where i use the saved delta from the DB to populate the editor. This works fine (with a fixed caveat, please see comments and code snippet for the fix at the end).
I also have a requirement to translate the content in the editor to a different language by tapping on an appropriate button. I use the Google translate API(on the server) and send it the HTML (innerHTML) from the editor and i get back proper translated HTML. Still on the server, just after the translation, i call convertHtmlToDelta with this translated HTML and send back the returned delta to the client. I then update the value of the editor with this new delta information and my editor shows the translated content. Works great and the whole operation seems almost seamless.  But there seems to be just one issue: the styles attribute doesn't seem to be present in the delta returned from convertHtmlToDelta. Everything else remains intact thus far.
So assuming this is the original delta for an image that has a float style:
ops: [
....
{
attributes:{
link: "https://quilljs.com",
style: "display: inline; margin: 0px 1em 1em 0px; float: left;",
width: "181",
},
insert{
image: ""https://source.unsplash.com/featured?art"
}
...
]

This gets rendered to:
<img src="https://source.unsplash.com/featured?art" style="display: inline; margin: 0px 1em 1em 0px; float: left;" width="181" />
After convertHtmlToDelta the delta becomes
ops: [
....
{
attributes:{
link: "https://quilljs.com",
width: "181",
},
insert{
image: ""https://source.unsplash.com/featured?art"
}
...
]

I originally had the problem with the Quill editor itself when i was preloading it with delta from the DB and from some net research i found that i had to add width,alt, height and style to the formats object. Additionally i had to add the following snippet as well:
const ImageFormatAttributesList = [
    'alt',
    'height',
    'width',
    'style'
];

class ImageFormat extends BaseImageFormat {
  static formats(domNode) {
    return ImageFormatAttributesList.reduce(function(formats, attribute) {
      if (domNode.hasAttribute(attribute)) {
        formats[attribute] = domNode.getAttribute(attribute);
      }
      return formats;
    }, {});
  }
  format(name, value) {
    if (ImageFormatAttributesList.indexOf(name) > -1) {
      if (value) {
        this.domNode.setAttribute(name, value);
      } else {
        this.domNode.removeAttribute(name);
      }
    } else {
      super.format(name, value);
    }
  }
}

Quill.register(ImageFormat, true);

Is there some way i could get the styles attribute as well in the returned delta? What are the possibilities of any other attribute getting stripped similarly?

Hi @arunmenon1975 . Thanks for reaching out. I appreciate your write up of the issue. I'm a little backed up at work. I'll do my best to review this and get back to you soon!


Test the Linux build with build.sh

Currently the only the build.ps1 is tested on Windows. Test the build.sh on Linux, too.
Add the Linux test to the Test task in the build.cake file

Linux build test works but the Windows test throws an "BadImage..." exception while executing Cake.dll

Seems to be a problem related to the .Net Core 2.1 Preview and not with the build scripts.


Overriding deprecated methods on an instance of NumberEntity

Describe the bug
Just a log message saying something is deprecated. Likely already know but I couldn't find an existing issue mentioning it so felt I should open a tracking issue for it.
Reproduction steps
N/A
Expected behaviour
N/A
Tariff Code
No response
Integration Version
7.5.0
Home Assistant Version
2023.7.2
Fresh Install?
Fresh install
Home Assistant Logs
Logger: homeassistant.components.number
Source: components/number/init.py:114
Integration: Number (documentation, issues)
First occurred: 03:56:49 (1 occurrences)
Last logged: 03:56:49
custom_components.octopus_energy.intelligent.charge_limit::OctopusEnergyIntelligentChargeLimit is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.

Thanks for raising. I saw this in another raised issue, but good to have it tracked separately.

Hello. This has been fixed in the latest release https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v8.0.0


The problem of not being able to transfer to the wallet after a transaction failure

I staked New York City Coin in 2022. It was marked as a success at the time.
I was waiting for it to be going well, and recently checked the Hiro Wallet.
But as a result, it was changed after 3 days due to staking failure?
Then, the New York City Coin I requested for staking must be in the wallet or can be transferred to the wallet by claiming it.
While this feature is not supported
New York City Coin went from V1 to V2
Then I have to change the staked New York City Coin V1 to V2 after sending it to my Hiro wallet.
The function to change to V2 seems to be in Hero Wallet.
It seems that V1 does not have the function itself to return the failed part of the transaction to my wallet.
https://explorer.hiro.so/txid/0xf5293dae0518685ced8fb76a89127f32306a7d8d357b507ddfff49ec41ba555a?chain=mainnet
Please let me know how to solve that problem. If not, this seems to be the problem.

This isn't a problem of the Explorer, please ask for help in Stacks Discord.


User/ryanbod/issue 2060 telemetry for build features

Summary of the Pull Request
Adds the following Telemetry Events.

Module
Event
Property:Values
Property:Values
Property:Values
Relevant  Spec Item

Settings
SettingsEnabledModuleEvent
ModuleName:{"FancyZones",File Explorer","Image Resizer","Keyboard Manager","PowerRename","Run","Shortcut Guide","Window Walker"}
Value:0=disabled,1=Enabled

N/A

Launcher
LauncherBootEvent
BootTimeMs:int

Requirement 1

Launcher
LauncherQueryEvent
QueryTimeMs:int
QueryLength:int
NumResults:int
Requirement 2

Launcher
LauncherFirstDeleteEvent

Requirement 3

Launcher
LauncherShowEvent

Requirement 5

Launcher
LauncherHideEvent

Requirement 5

Launcher
LauncherResultActionEvent
Trigger:{"Click","KeyboardShortcut}"
PluginName:Microsoft.Plugins.*
ActionName:{"Copy Path", "Run As Administrator" etc}
Requirements 6/7

Note:  Requirement 5 in the Launcher spec is covered by the SettingsEnabledModuleEvent

References

PR Checklist

[x] Applies to #2060
[x] CLA signed. If not, go over here and sign the CLA
[] Tests added/passed
[x] Requires documentation to be updated
[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments
TelemetryBase will need to be replaced at runtime.  Note:  This is a 'link' reference in each of the managed projects.

Validation Steps Performed
Validated Events in wpr / WPA.  Screenshots inbound

@Lavius. / @somil55 / @udit3333 .   I don't get telemetry events for Svg and Markdown settings.  This is because the Settings V2 doesn't use the EnabledModules property of General Settings.  Does this get serialized anywhere, or is this a special case because it needs to update the registry.

I'm confused with the table, it has 3 identical Property:Values columns.

I'm confused with the table, it has 3 identical Property:Values columns.

@riverar Yep.. Sorry I can see how that's confusing.  I'm serializing an [EventData] object.  Those aren't fixed columns.   Basically they just map to Field 1, 2, 3.. n in WPA.    There are only up to 3 fields in each of the data events that are being serialized to the EventSource.
For each field I'm showing Property : Values where property is the name of the property in the event data object, and Values is the list of possible values that it could be.

@ryanbodrug-microsoft Ah, got it now, thanks.

I think we are not setting the Plugin Name for the Calculator and WindowWalker plugins.

Yes.  Those plugins don't have context menus so we don't have any events firing for the buttons being pressed.


Mention Curry dependency in README

fixes #270
Perhaps it would be worthwhile to show an example of a curried create method in case people don't want to add an additional dependency?

I was thinking it might get more visibility being either before the example or right after the install guide

Yeah I had it above the example initially. Happy to move it back there.

On Oct 20, 2015, at 2:58 PM, Tony DiPasquale<EMAIL_ADDRESS>wrote:
I was thinking it might get more visibility being either before the example or right after the install guide
—
Reply to this email directly or view it on GitHub.

@tonyd256 thoughts on providing an example of a curried create method?

I think an example of a curried create is something we want to have in our documentation. Then we could have a link in that blurb that pointed to the appropriate docs

Good call, I think that makes more sense than adding clutter to the README


I get 500 Server Error for restaurants in any city in Bulgaria

All Errors are resolved in latest update


How to embed it into a webpage?

Hello,
I am interested in using your scheme interpreter repository on Github, but I am not sure how to embed it into a webpage like the CS61A textbook. Could you please provide some guidance on how to do this?
I was wondering if I should use an iframe or if there is another technique that can be used? Any help or suggestions would be greatly appreciated.
Thank you for your time and for creating this valuable resource.

There was a library that was adding exactly this that used BiwaScheme and a bunch of other programming languages, but I don't remember that name and I can't find it right now.

I was able to find it, it was Klipse.

I was able to find it, it was Klipse.
I'll try it, thank you!


pawn 'P_SC' cannot enter RunningState

Repro: shoot the scrake as commando, observe no raging despite health visibly dropping below 75%

Fixed via 374f5ff.


CRYSTAL_BIO error when requiring third-party lib

Pulled in Crustache last week into a project doing simple template rendering and running specs works perfectly fine, but attempting to build the project, I get the following error:
crystal build src/biplane.cr
Error in /usr/local/Cellar/crystal-lang/0.15.0/src/openssl/bio.cr:11: instantiating 'IO#write(Slice(UInt8))'

      io.write Slice.new(data, len)
         ^~~~~

in /usr/local/Cellar/crystal-lang/0.15.0/src/openssl/bio.cr:5: constant OpenSSL::BIO::CRYSTAL_BIO requires initialization of Crustache::Parser::NEWLINE_N, which is initialized later. Initialize Crustache::Parser::NEWLINE_N before OpenSSL::BIO::CRYSTAL_BIO

  CRYSTAL_BIO = begin
  ^~~~~~~~~~~

make: *** [build] Error 1

Not sure why a stdlib is complaining about a constant defined in a third-party lib here. That's also the full extent of the stack trace so I'm not really sure how to track down further info about where this is occurring. Let me know what I can do to help figure this one out.

Hmm, on a whim, I moved around some require statements for crustache much farther up the chain and the issue went away. Still would love to see this one solved or at least commented on as to why.

@plukevdh I'm creator of crustache. Thanks for using it. Hmm, that's strange and interesting. Then, I tried below code and got a following error.
require "../src/crustache"
require "openssl"

p OpenSSL::BIO::CRYSTAL_BIO

Error in /usr/lib/crystal/openssl/bio.cr:9: expected block to return Int32, not NoReturn

    crystal_bio.bwrite = LibCrypto::BioMethodWrite.new do |bio, data, len|
                         ^

So, I guess, this error was caused by Crustache::IndentIO#write method and that Crystal's type inference rule was changed. However, I can't find problem in my code. What do you think, @asterite ?

Crustache::IndentIO#write was inferred as NoReturn..?

It happens also with this:
require "openssl"

OpenSSL::BIO::CRYSTAL_BIO

Oh, thanks!  月曜日, 25 4月 2016, 11:52午後 +09:00 from Ary Borenszweig <<EMAIL_ADDRESS>:

It happens also with this:
require "openssl"

OpenSSL::BIO::CRYSTAL_BIO
—
You are receiving this because you commented.
Reply to this email directly or  view it on GitHub

Reduced to:
lib LibFoo
  struct Some
    x : ->
  end
end

X = LibFoo::Some.new
p X

❤  thanks for quick work on this!

@plukevdh Note that the original error seems to be unrelated to the problem I fixed. If you could share a snippet of code (or instructions) that reproduce the "constant ... requires initialization of ..." problem, that would be great.

Will investigate and report back if I can create a reduced reproducible example.

Haven't managed a scaled down version, but I can give you a branch with the code that causes a compilation error: https://github.com/articulate/biplane/tree/env-interpolation

Oddly enough, that branch builds successfully on CI (Travis) but still fails locally. So it may be something getting cached locally between builds?


cyan and lime colors are not working

As you can see in these pages, and this, and this, cyan and lime colors are not working.

Fixed.


how do i fix this

i wanted to  create a splitter to obtain a list of bboxes with 5km side
and i got the error code
C:\Users\SurfaceBook\anaconda3\lib\site-packages\sentinelhub\constants.py:113: SHUserWarning: sentinelhub-py supports only WGS 84 coordinate reference system with coordinate order lng-lat. Given pyproj.CRS(4326) has coordinate order lat-lng. Be careful to use the correct order of coordinates.   warnings.warn(message, category=SHUserWarning) C:\Users\SurfaceBook\anaconda3\lib\site-packages\shapely\set_operations.py:133: RuntimeWarning: invalid value encountered in intersection   return lib.intersection(a, b, **kwargs)
how  do i change the parraters inother to suit  ukraine  which is the country im using instead of Slovenia

The first error is just a regular warning about the WGS84 coordinate system. In most cases you can ignore it, but you should be careful since you say you want BBoxes with 5km sides. Thw WGS84 system does not use meters as it's units, so you need to select an appropriate splitter, perhaps a UtmZoneSplitter
The second warning could be for a variety of reasons, I advise you to check the result by hand (plot the geometry of the country and the geometries of all bboxes) to see if the result makes sense. Very often the results are still fine even if such a warning happens.

Solution provided, closing due to inactivity.


Using docker-compose to run the app and connect successfully to a pos…

What does this PR do?
Setup docker-compose to run backend and database applications
Description of Task to be completed

Installing docker/docker-compose
Creating docker images for node backend & postgres database applications
Making sure the node backend can connect to postgres database

installed packages

sequelize (for testing db connection)

How should this be manually tested

Install docker & docker compose
cd to/project/directory (after cloning)
npm install
docker build -t node-backend .
'docker-compose up`

If you see "Database connected successfully", it's working!
Any background context you want to
n/a

LGTM

I think the title of your PR is lacking the pivot tracker id

He should rename his PR the way it is supposed to be.

I think the title of your PR is lacking the pivot tracker id

He should rename his PR the way it is supposed to be.

My bad title fixed!


Remove two-deployment mode

As agreed in https://github.com/open-telemetry/opentelemetry-helm-charts/issues/91, we need remove the two-deployment mode and simplify the configuration.
Instead of agentCollector and standaloneCollector, we should have another config option mode which can have one of the following values: daemonset or deployment. All the nested configuration options from agentCollector and standaloneCollector should be moved to the root level. Some of them can be no-op based on the selected mode.
Ideally we need to provide backward compatibility with existing interface for now. It means that we translate agentCollector and standaloneCollector configs into the new config and show deprecation warning if they are used.
If user has both modes enabled (agentCollector.enabled=true and standaloneCollector.enabled=true) the upgrade should fail. This can be achieved by updating schema.values.json. For this use case we need to provide a detailed upgrade guideline on how to replace it with two separate helm installations.

I will take a look at this.

If we are willing to break backwards compatibility for both modes enabled, should we just rip the bandaid off and make agentCollector and standaloneCollector break the install as well?  Since we aren't giving the both-mode-enabled customers a chance to convert before failure should we take that stance across the board and force anyone using this version of the charts to update their values.yaml?

I think majority of the use cases is enabled one mode or another. So I would say we should not break their upgrade

The situation I dislike is that since agentCollector.enabled is true by default, there will be customers the have configurations like:
agentCollector:
  resources:
    limits:
      cpu: 2
      memory: 4Gi

which relies on agentCollector.enabled to be true by default.  To continue to support these customers after this refactor we need to make sure their config continues to work, which means we have to keep agentCollector.enabled true by default.  This results in strange values.yamls for users who want to use the new mode: daemonset and root-level config options.  To use the new mode and config options your values.yaml would look like
// daemonset is the default so this technically isn't needed
mode: daemonset
agentCollector:
  enabled: false
resources:
  limits:
    cpu: 2
    memory: 4Gi

I don't love that the default values.yaml would still be using the agentCollector configs and any new user would have to reference the old config setting even though we are trying to deprecate it :(

Sorry I don't think I understand your concern. Are you saying that user have to set agentCollector.enabled: true in their values.yaml even if they have mode: daemonset?

If users want to use the mode: daemonset, and the other new configurations at the root level such as resources or podAnnotations they will have to explicitly list agentCollector.enabled: false in their values.yaml since we have to keep agentCollector.enabled: true  in the chart's default values.yaml to maintain backwards compatibility.

What if we don't set mode by default and use it to distinguish whether used updated their config or not? The following expression can help with that eq (toString .Values.mode) "<nil>".

If mode is unset, we use the old format and throw a deprecation warning.
If mode is set, we completely ignore agentCollector and agentCollector configurations.

Later we will just drop agentCollector and agentCollector.

Yes I like that a lot.  I will get the PR updated with that strategy, see how it comes out.


Reduce/Eliminate User Prompts for Keychain Access

When using granted/assume users may experience prompts for their password to access the Keychain items, particularly on macOS:

This can be reproduced easily on macOS by running assume for a valid AWS SSO profile then running granted sso-tokens clear --all to clear out the entry.
I suspect this is related to some combination in an oddity with the code signing of the 2 separate binaries, the ACLs on the keychain items or the significantly older version of https://github.com/99designs/go-keychain used by granted, however more investigation is required.

Upon further investigation using https://github.com/its-a-feature/LockSmith (see also Lock Picking the macOS Keychain talk at OBTS 5.0), we can see the ACLs on a keychain item created using the signed v0.10.0 release:
Account:       https://<snip>.awsapps.com/start
Label:         granted-aws-sso-tokens
Service:       granted-aws-sso-tokens
Creation Date: 2023-04-12 21:08:51
Modify Date:   2023-04-12 21:08:51
Class:         genp
Owner Authorizations based on ACLAuthorizationPartitionID
Owner Authorizations:
    ACLAuthorizationEncrypt
    ACLAuthorizationDecrypt
    ACLAuthorizationDerive
    ACLAuthorizationExportClear
    ACLAuthorizationExportWrapped
    ACLAuthorizationMAC
    ACLAuthorizationSign
    ACLAuthorizationIntegrity
    ACLAuthorizationPartitionID
------------ACLS------------
    --- Entry 0
        Description: (null)
        All applications are trusted
        Authorizations:
             ACLAuthorizationEncrypt
    --- Entry 1
        Description:
        Trusted App: /usr/local/Cellar/granted/0.10.0/bin/assumego
            Requirement String: identifier assumego and anchor apple generic and certificate 1[field.1.2.840.1136<IP_ADDRESS>.6] /* exists */ and certificate leaf[field.1.2.840.1136<IP_ADDRESS>.13] /* exists */ and certificate leaf[subject.OU] = VXC4RPMSUJ
        Authorizations:
             ACLAuthorizationDecrypt
             ACLAuthorizationDerive
             ACLAuthorizationExportClear
             ACLAuthorizationExportWrapped
             ACLAuthorizationMAC
             ACLAuthorizationSign
    --- Entry 2
        Description: 80912843e85942c565983c435cfa730ad00ce0664d7671d7da763950f0848f5f
        All applications are trusted
        Authorizations:
             ACLAuthorizationIntegrity
    --- Entry 3
        Allowed Code Signatures: teamid:VXC4RPMSUJ
            TeamID doesn't match current application: nil
        Description: 3c3f786d6c2076657273696f6e3d22312e302220656e636f64696e673d225554462d38223f3e0a3c21444f435459504520706c697374205055424c494320222d2f2f4170706c652f2f44544420504c49535420312e302f2f454e222022687474703a2f2f7777772e6170706c652e636f6d2f445444732f50726f70657274794c6973742d312e302e647464223e0a3c706c6973742076657273696f6e3d22312e30223e0a3c646963743e0a093c6b65793e506172746974696f6e733c2f6b65793e0a093c61727261793e0a09093c737472696e673e7465616d69643a5658433452504d53554a3c2f737472696e673e0a093c2f61727261793e0a3c2f646963743e0a3c2f706c6973743e0a
        All applications are trusted
        Authorizations:
             ACLAuthorizationPartitionID
    --- Entry 4
        Description:
        No applications are trusted
        Authorizations:
             ACLAuthorizationChangeACL

As expected, this is the default ACL that macOS populates on new keychain items if the application does not otherwise specify.

The root-cause appears to be related to the ACL on the keychain item:

Requirement String: identifier assumego and anchor apple generic and certificate 1[field.1.2.840.1136<IP_ADDRESS>.6] /* exists / and certificate leaf[field.1.2.840.1136<IP_ADDRESS>.13] / exists */ and certificate leaf[subject.OU] = VXC4RPMSUJ

macOS is setting the ACL so only binaries named assumego signed by the Common Fate code signing certificate can access this item. Because granted is a different binary (although signed by the same certificate) it fails this check triggering a prompt for the user to grant access.

One solution for this would be to use an "access group" to grant multiple binaries signed by the same certificate access to the keychain items. This does not appear to be easily configurable via the keyring library and could introduce complexity for migrating existing keychain items.
A simpler solution that would also be cross-platform would be to use a single binary for both granted/assumego and automatically change the behavior based on the filename provided as os.Args[0]. This would probably mean granted is the actual binary and assume is a symlink to the granted binary. This may introduce some complexity into the installer/packages such as the homebrew formula but could also cutdown on the overall package/release size.

This was resolved via #404 and released as v0.11.0


Copyright

Switch to using the AUTHORS file to refer to all of the authors of PEG.js/Peggy.  I created the list by exporting from the git log, then matching up everyone's github handle, except for a few people I couldn't figure out.  For everyone listed, please let me know ASAP if you'd like to be removed, if you'd like different information, etc.
Also let me know if I missed you, please.
@dmajda @sampsyo @atavakoli @almad @andreineculau @arlolra @bkutil @chearon @phpnode @futagoza @vrana @jasondavies @joseph-onsip @hyperpape @Mingun @tonylukasavage @chunpu @fatfisz @fpirsch

OK, it's been a day, so I'm moving ahead.  Anyone who wants can still send a PR if they want something changed.


Don't error when finding blocks by pools not in the stake distribution

Issue Number
#1442 potential solution.

Overview
The erroring was originally a precaution.

While I haven't checked, it must be that jormungandr removes pools in
the stake-distribution... _before_ they are retired?

This patch seems to solve the problem.

Comments

⚠ We should investigate more what is going on ⚠
[ ] TODO: If we do this, we should remove the now unused ErrMetricsInconsistency.

@Anviking what is going on is that stake pool de-registration have landed into jcli and jormungandr's API. So operators are starting to de-register pools. While I thought that would originally only impact the listing view (in the sense that de-registered pools would still show up) I didn't quite realize this would also affect the metrics calculations.
Thanks for the PR but I think I'll take it even further and actually have correct support for de-registration certificates. We already parse them at the binary level but simply do nothing with them. I am still not quite sure how to properly test that from the wallet since the self node we use for testing behaves weirdly when it comes to pool registration. We have fixtures for submitting de-registration certificates but the pool we may registered via this way simply don't produce.

Superseded by #1444


[BUG] The horizontalBar chart skips the first value from dataset.

Expected Behavior
In the line chart (second dataset), the line should also be drawn for the first value, as it is in the horizontalBar chart(first dataset).
Current Behavior
In the line graph, the line is drawn from the second value, the horizontalBar graph is drawn from the first value. When I only draw a Gaussian curve, all points are drawn correctly. Inversion of histogram doesn't help.

Possible Solution
Steps to Reproduce (for bugs)
https://codepen.io/krna/pen/ejzqwg
var ctx = document.getElementById("myChart"); var myChart = new Chart(ctx, {     type: 'horizontalBar',     data: {         labels: [0,1,2,3,4,5,6,7,8,                 9,10,11,12,13,14,15],         datasets: [{             borderWidth: 1,             backgroundColor: 'rgba(255, 99,                               132,0.5)',             borderColor: 'rgb(255, 99, 132)',             data: [3,1,0,0,0,2,0                   ,2,0,2,0,0,0,0,0,0]         },{           type: 'line',           fill: false,           borderWidth: 1,           data: [   {     "x": 0.4175611241375584,     "y": 0   },   {     "x": 0.5959532140041752,     "y": 1   },   {     "x": 0.7859097829567998,     "y": 2   },   {     "x": 0.9576386017705346,     "y": 3   },   {     "x": 1.0781992198876187,     "y": 4   },   {     "x": 1.1216692215727766,     "y": 5   },   {     "x": 1.0781992198876187,     "y": 6   },   {     "x": 0.9576386017705346,     "y": 7   },   {     "x": 0.7859097829567998,     "y": 8   },   {     "x": 0.5959532140041752,     "y": 9   },   {     "x": 0.4175611241375584,     "y": 10   },   {     "x": 0.27033132329127463,     "y": 11   },   {     "x": 0.1617115734967744,     "y": 12   },   {     "x": 0.08938286189552247,     "y": 13   },   {     "x": 0.045649479432087706,     "y": 14   },   {     "x": 0.02154199016167806,     "y": 15   } ],           borderColor: 'rgb(54, 162, 235)',           radius: 2         }]     },     options: {         scales: {             yAxes: [{                categoryPercentage : 1,                barPercentage: 1             }],             xAxes: [{               type: 'linear',               position: 'bottom',               ticks: {                 stepSize: 1,                 min: 0,                 max: 4               }             }]         }     } });
Context
I'm trying to draw a histogram with a gaussian curve.
Environment

Chart.js version: 2.6.0, 2.7.2
Browser name and version: Chrome 67.0.3396.99

Not sure this is a bug or not, but "y": 0 is probably interpreted as null instead of '0'.
It's not about the first value. Since -1 and anything else work as first value.
add:
{
    "x": 0.4175611241375584,
    "y": -1
  },

and
labels: [-1,0.0,1,2,3,4,5,6,7,8,
                9,10,11,12,13,14,15],

And the first value does work, only 0 doesn't work.
You can make this work however, by making the labels and y values a string. Since y value correspondents with the label, and labels can be strings:
labels: ['0','1','2','3','4','5','6','7','8','9','10','11','12','13','14','15'],

data: [
  {
    "x": 0.4175611241375584,
    "y": '0'
  },
  {
    "x": 0.5959532140041752,
    "y": '1'
  },
  {
    "x": 0.7859097829567998,
    "y": '2'
  },
  {
    "x": 0.9576386017705346,
    "y": '3'
  },
  {
    "x": 1.0781992198876187,
    "y": '4'
  },
  {
    "x": 1.1216692215727766,
    "y": '5'
  },
  {
    "x": 1.0781992198876187,
    "y": '6'
  },
  {
    "x": 0.9576386017705346,
    "y": '7'
  },
  {
    "x": 0.7859097829567998,
    "y": '8'
  },
  {
    "x": 0.5959532140041752,
    "y": '9'
  },
  {
    "x": 0.4175611241375584,
    "y": '10'
  },
  {
    "x": 0.27033132329127463,
    "y": '11'
  },
  {
    "x": 0.1617115734967744,
    "y": '12'
  },
  {
    "x": 0.08938286189552247,
    "y": '13'
  },
  {
    "x": 0.045649479432087706,
    "y": '14'
  },
  {
    "x": 0.02154199016167806,
    "y": '15'
  }
]
...

Example: https://codepen.io/hedva/pen/OwpjGO

@etimberg Although this issue is marked as closed, and there is a solution for this, I'm not sure this should be marked as a bug or not. 0 should probably not be interpreted as null.

@krna do you remember maybe how did you generate the datset that follows normal distribution on the 0-15 interval?

Hey,
Because this is part of a commercial application, I can not attach the code. But I can describe how I solve it. I use this library http://mathjs.org/ and the theory from this page https://en.wikipedia.org/wiki/Normal_distribution. First, I divide the data into intervals and count the values in each range. Then I calculate the mean, standard deviation and variance. Then I calculate the probability density for each interval and voila.

Thanks @krna !
I've taken the same approach and it work correctly, although the curve is not completely smooth. Tried with a different number of data points but haven't fixed that part of the issue. It's probably some Chart.js config option waiting somewhere to be found :)
Except for that, all good on my end!

Hi,
I think it could be about data, not Chart.js control. Could you paste screen of your example and data for it?

Ok. This should be Chart.js config not a data. I suspected earlier that problem is bigger and the data is non-standardized. :)


Feature Request: Implement Context Management and Message Editing for Improved LLM Performance

Background
When implementing a feature, I've noticed that as I get deeper into the task, the LLM starts to struggle with solving issues. Each iteration doesn't necessarily contribute to solving the problem, as the growing context seems to impair its problem-solving abilities.
Observations

Starting a new task, even without the full context of the previous work, often results in higher quality problem-solving and better handling of errors and sub-tasks.
The base message sent with every request grows larger over time, potentially polluting the context.

Proposed Solutions
1. Context Management
Implement a system to manage the context of tasks. This could include:

Displaying information about how many tokens are already used up for chat history (maybe the cached prompts would be the size of this?). There could be an indicator with green, yellow and red, so users can quickly see if they're reaching the maximum possible tokens per request.
Allowing users to start from an earlier state when beginning a new task.

2. Message Editing
Add the ability to edit previously sent messages that didn't result in a satisfactory response from the LLM. This could significantly improve efficiency in using the tool.
3. Context Addition Optimization
Investigate and potentially optimize how information is added to the context. The exact logic behind this process I haven't investigated, but there may be room for improvement.
Benefits

These changes would help users strategically finish tasks before hitting the 200,000 token limit (related to issue #106).
Improved LLM performance by maintaining a more relevant and focused context.
Enhanced user control over the conversation flow and context.

Next Steps

[ ] Research current context management implementation
[ ] Design UI for displaying token usage and context management options
[ ] Implement prototype of message editing feature
[ ] Investigate optimization possibilities for context addition logic
[ ] User testing and feedback collection

Related Issues

#106 (regarding the 200,000 token limit)

v1.5 now has sliding window context management that essentially removes messages from index 2 to ~n/2, this essentially keeps the most imporant message (task + relevant details given to claude in the first message) while also getting rid of older messages. By getting rid of several messages at once we can take advantage of prompt caching, rather than a more dynamic sliding window that might remove 1 message at a time which would keep breaking the cache.
Keeping this issue open for the other suggestions though, I'll update here as I get to them.

v1.5 now has sliding window context management that essentially removes messages from index 2 to ~n/2, this essentially keeps the most imporant message (task + relevant details given to claude in the first message) while also getting rid of older messages. By getting rid of several messages at once we can take advantage of prompt caching, rather than a more dynamic sliding window that might remove 1 message at a time which would keep breaking the cache.
Keeping this issue open for the other suggestions though, I'll update here as I get to them.

I understand you can set up to four separate cache breakpoints. There is probably some optimum way to do this.

@CiberNin I use 1 breakpoint for the system prompt and 2 for the latest messages, so we have 1 left to use how we want. If you have suggestions about how to use it in terms of context management I'd love to hear. I'll think on this and report back if I update it

If 2/3 are still something you'd like to see added, please feel free to add it in the ideas board so people can vote on it. Thank you!


cordova.plugins is undefined

Need to reopen:
https://github.com/Telerik-Verified-Plugins/LocalNotification/issues/17#issuecomment-241636040

Check again if you have included the cordova.js library!