Missing config from pulled images

After using img to pull and save and docker to load an image, data appears to be missing from the image.
Am I using this incorrectly?
Maybe this is related to #187?
Comparing the manifests shows some differences:
busybox:latest pulled by docker
chin@ubuntu:~|⇒  docker inspect busybox:latest
[
    {
        "Id": "sha256:59788edf1f3e78cd0ebe6ce1446e9d10788225db3dedcfd1a59f764bad2b2690",
        "RepoTags": [
            "busybox:latest"
        ],
        "RepoDigests": [
            "busybox@sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812"
        ],
        "Parent": "",
        "Comment": "",
        "Created": "2018-10-02T17:19:34.239926273Z",
        "Container": "547a7f4181dc7c44a00961f3e6d3342f3d5d3c2095883b60fefff8d9de9be116",
        "ContainerConfig": {
            "Hostname": "547a7f4181dc",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": [
                "/bin/sh",
                "-c",
                "#(nop) ",
                "CMD [\"sh\"]"
            ],
            "ArgsEscaped": true,
            "Image": "sha256:8f4ffec338c4203118ad2ad56a01139b499e2ec244fdceda8ada658aa442b07a",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": {}
        },
        "DockerVersion": "17.06.2-ce",
        "Author": "",
        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": [
                "sh"
            ],
            "ArgsEscaped": true,
            "Image": "sha256:8f4ffec338c4203118ad2ad56a01139b499e2ec244fdceda8ada658aa442b07a",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": null
        },
        "Architecture": "amd64",
        "Os": "linux",
        "Size": 1154353,
        "VirtualSize": 1154353,
        "GraphDriver": {
            "Data": {
                "MergedDir": "/var/lib/docker/overlay2/0ba19bf93f9e791abf5e5f3c4b375ec22b92f55c0d15642363d4990521d462ad/merged",
                "UpperDir": "/var/lib/docker/overlay2/0ba19bf93f9e791abf5e5f3c4b375ec22b92f55c0d15642363d4990521d462ad/diff",
                "WorkDir": "/var/lib/docker/overlay2/0ba19bf93f9e791abf5e5f3c4b375ec22b92f55c0d15642363d4990521d462ad/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:8a788232037eaf17794408ff3df6b922a1aedf9ef8de36afdae3ed0b0381907b"
            ]
        },
        "Metadata": {
            "LastTagTime": "0001-01-01T00:00:00Z"
        }
    }
]

busybox:latest pulled and saved by img - a bunch of values are missing from "Config"
img pull busybox:latest
img save --output busybox-latest busybox:latest
docker load -i busybox-latest

 docker inspect busybox
[
    {
        "Id": "sha256:620190d140bbe2da982fac16475312eccacddd87c3235d50f3893e9ae499f28e",
        "RepoTags": [
            "busybox:latest"
        ],
        "RepoDigests": [],
        "Parent": "",
        "Comment": "buildkit.exporter.image.v0",
        "Created": "2018-11-28T20:00:13.279842672Z",
        "Container": "",
        "ContainerConfig": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": null,
            "Cmd": null,
            "Image": "",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": null
        },
        "DockerVersion": "",
        "Author": "",
        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": null,
            "Image": "",
            "Volumes": null,
            "WorkingDir": "/",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": null
        },
        "Architecture": "amd64",
        "Os": "linux",
        "Size": 1154353,
        "VirtualSize": 1154353,
        "GraphDriver": {
            "Data": {
                "MergedDir": "/var/lib/docker/overlay2/5b5bb696c6a7b85f5b411f3291dbf1f8eb352dbcbef02e4a225d0c6e3bd330ee/merged",
                "UpperDir": "/var/lib/docker/overlay2/5b5bb696c6a7b85f5b411f3291dbf1f8eb352dbcbef02e4a225d0c6e3bd330ee/diff",
                "WorkDir": "/var/lib/docker/overlay2/5b5bb696c6a7b85f5b411f3291dbf1f8eb352dbcbef02e4a225d0c6e3bd330ee/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:8a788232037eaf17794408ff3df6b922a1aedf9ef8de36afdae3ed0b0381907b"
            ]
        },
        "Metadata": {
            "LastTagTime": "0001-01-01T00:00:00Z"
        }
    }
]

Even after just pulling, it seems the digest is different.
chin@ubuntu:~|⇒  docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:24:56 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:23:21 2018
  OS/Arch:          linux/amd64
  Experimental:     false
chin@ubuntu:~|⇒  docker pull busybox:latest
latest: Pulling from library/busybox
90e01955edcd: Pull complete
Digest: sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812
Status: Downloaded newer image for busybox:latest
chin@ubuntu:~|⇒  docker images --digests
REPOSITORY          TAG                 DIGEST                                                                    IMAGE ID            CREATED             SIZE
busybox             latest              sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812   59788edf1f3e        8 weeks ago         1.15MB
chin@ubuntu:~|⇒
chin@ubuntu:~|⇒
chin@ubuntu:~|⇒  img version
img:
 version     : v0.5.2
 git hash    : 0b967de
 go version  : go1.11.1
 go compiler : gc
 platform    : linux/amd64
chin@ubuntu:~|⇒  img pull -d busybox:latest
DEBU[0000] using backend: overlayfs
Pulling busybox:latest...
DEBU[0000] serving grpc connection
DEBU[0000] resolving
DEBU[0000] do request                                    request.headers="map[Accept:[application/vnd.docker.distribution.manifest.v2+json, application/vnd.docker.distribution.manifest.list.v2+json, application/vnd.oci.image.manifest.v1+json, application/vnd.oci.image.index.v1+json, *]]" request.method=HEAD url="https://registry-1.docker.io/v2/library/busybox/manifests/latest"
DEBU[0000] fetch response received                       response.headers="map[Strict-Transport-Security:[max-age=31536000] Content-Type:[application/json; charset=utf-8] Docker-Distribution-Api-Version:[registry/2.0] Www-Authenticate:[Bearer realm=\"https://auth.docker.io/token\",service=\"registry.docker.io\",scope=\"repository:library/busybox:pull\"] Date:[Wed, 28 Nov 2018 19:45:39 GMT] Content-Length:[158]]" status="401 Unauthorized" url="https://registry-1.docker.io/v2/library/busybox/manifests/latest"
DEBU[0000] Unauthorized                                  header="Bearer realm=\"https://auth.docker.io/token\",service=\"registry.docker.io\",scope=\"repository:library/busybox:pull\""
DEBU[0000] do request                                    request.headers="map[Accept:[application/vnd.docker.distribution.manifest.v2+json, application/vnd.docker.distribution.manifest.list.v2+json, application/vnd.oci.image.manifest.v1+json, application/vnd.oci.image.index.v1+json, *]]" request.method=HEAD url="https://registry-1.docker.io/v2/library/busybox/manifests/latest"
DEBU[0000] fetch response received                       response.headers="map[Docker-Distribution-Api-Version:[registry/2.0] Etag:[\"sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812\"] Date:[Wed, 28 Nov 2018 19:45:40 GMT] Strict-Transport-Security:[max-age=31536000] Content-Length:[2699] Content-Type:[application/vnd.docker.distribution.manifest.list.v2+json] Docker-Content-Digest:[sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812]]" status="200 OK" url="https://registry-1.docker.io/v2/library/busybox/manifests/latest"
DEBU[0000] resolved                                      desc.digest="sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812"
DEBU[0000] fetch                                         digest="sha256:2a03a6059f21e150ae84b0973863609494aad70f0a80eaeb64bddd8d92465812" mediatype=application/vnd.docker.distribution.manifest.list.v2+json size=2699
DEBU[0000] fetch                                         digest="sha256:915f390a8912e16d4beb8689720a17348f3f6d1a7b659697df850ab625ea29d5" mediatype=application/vnd.docker.distribution.manifest.v2+json size=527
DEBU[0000] fetch                                         digest="sha256:90e01955edcd85dac7985b72a8374545eac617ccdddcc992b732e43cd42534af" mediatype=application/vnd.docker.image.rootfs.diff.tar.gzip size=727978
DEBU[0000] fetch                                         digest="sha256:59788edf1f3e78cd0ebe6ce1446e9d10788225db3dedcfd1a59f764bad2b2690" mediatype=application/vnd.docker.container.image.v1+json size=1496
Pulled: sha256:304340d8663fcddb7ce8a3071e4d625aea7bb609954b7d1179f2635dfd4b4566
Size: 711.9KiB
chin@ubuntu:~|⇒  img ls
NAME					SIZE		CREATED AT	UPDATED AT	DIGEST
docker.io/library/busybox:latest	711.9KiB	2 seconds ago	2 seconds ago	sha256:304340d8663fcddb7ce8a3071e4d625aea7bb609954b7d1179f2635dfd4b4566

seems like a bug thanks! will look into!

I got hit by this pesky bug. In our CI pipeline we promote images by retagging them. I.e.:
img pull some/imgage:tag
img tag some/image:tag some/image:new-tag
img push some/image/new-tag

When some/image:new-tag is deployed in our kubernetes cluster, workdir is lost as well as default command CMD ["node", "index.js"].
Workaround is to rebuild image with new tag (which feels painful).

This issue bit me too, I was going to report it before finding it was done already.
Just in case it's any use to anybody who wants to have a look, I made a minimal reproducing example, in a workflow similar to @djupudga's : https://gitlab.com/toadjaune/minimal-example-img-corruption
Basically, we pull the hello-world image, re-tag it, and push it back to gitlab's docker registry, both with docker and with img.
Here are the resulting images (publicly pullable) :

registry.gitlab.com/toadjaune/minimal-example-img-corruption/docker (re-tagged with docker)
registry.gitlab.com/toadjaune/minimal-example-img-corruption/img (re-tagged with img)

Here is what happens when trying to run these images :
$ docker run registry.gitlab.com/toadjaune/minimal-example-img-corruption/img
Unable to find image 'registry.gitlab.com/toadjaune/minimal-example-img-corruption/img:latest' locally
latest: Pulling from toadjaune/minimal-example-img-corruption/img
1b930d010525: Already exists
Digest: sha256:6174fe2d8851516bec70ade197b5ae7f9cb78451e5963260fb7ecafbf77ffcf7
Status: Downloaded newer image for registry.gitlab.com/toadjaune/minimal-example-img-corruption/img:latest
docker: Error response from daemon: No command specified.
See 'docker run --help'.
$ docker run registry.gitlab.com/toadjaune/minimal-example-img-corruption/docker
Unable to find image 'registry.gitlab.com/toadjaune/minimal-example-img-corruption/docker:latest' locally
latest: Pulling from toadjaune/minimal-example-img-corruption/docker
Digest: sha256:92c7f9c92844bbbb5d0a101b22f7c2a7949e40f8ea90c8b3bc396879d95e899a
Status: Downloaded newer image for registry.gitlab.com/toadjaune/minimal-example-img-corruption/docker:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

The img version gives us a No command specified error similar to #187 (which is likely a duplicate)
Not sure if this is any use to anybody since the issue was pretty clear already

docker pull plugins/docker
docker tag plugins/docker <IP_ADDRESS>:5000/plugins/docker
docker push <IP_ADDRESS>:5000/plugins/docker
docker run  <IP_ADDRESS>:5000/plugins/docker

The docker version is good.
img pull plugins/docker
img tag plugins/docker <IP_ADDRESS>:5000/plugins/docker
img push <IP_ADDRESS>:5000/plugins/docker
docker run  <IP_ADDRESS>:5000/plugins/docker

The img version gives us a No command specified  error

To see the difference you can simply run an inspect on both images
dockerhub.xxxxx/pickle-rick-sharenow   release-1           2f55c01e4825        About an hour ago   431MB
dockerhub.xxxxxxx/pickle-rick-sharenow   f7bb392b            71ff7edcbe1e        About an hour ago   431MB

release-1 was is the second tag for f7bb created with img
here is the diff with the working image f7bb on the left and the tagged release-1 on the right side
3c3
<         "Id": "sha256:71ff7edcbe1e37a7c2d7a4384d0d37fa1304063ba201433f08b709b7a6857b38",
---
>         "Id": "sha256:2f55c01e4825cd132f5f3ce7ba0cf34a4b8fa5ff619f3c0431e67164165e1891",
5c5
<             "dockerhub.xxxxxxxxxxxx/pickle-rick-sharenow:f7bb392b"
---
>             "dockerhub.xxxxxxxxxxxx/pickle-rick-sharenow:release-1"
8c8
<             "dockerhub.xxxxxxxxxxxx/pickle-rick-sharenow@sha256:6e7f88ccb28a1a09f0321c7e8de674a37c15481cb76fd5453afb59dd25117600"
---
>             "dockerhub.xxxxxxxxxxxx/pickle-rick-sharenow@sha256:9864aa875ae0cd6230fc743e8043f3cab82ee30e3abec05161e5c7404b1a39ab"
11,12c11,12
<         "Comment": "buildkit.dockerfile.v0",
<         "Created": "2019-11-05T14:46:30.332202608Z",
---
>         "Comment": "buildkit.exporter.image.v0",
>         "Created": "2019-11-05T14:55:39.248957399Z",
46,54c46
<                 "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
<                 "NODE_VERSION=10.17.0",
<                 "YARN_VERSION=1.19.1",
<                 "APP=sharenow",
<                 "THEME=sharenow",
<                 "OPTIMIZELY_ENV=",
<                 "CUBA_URL=https://xxxxxxxxxxxxxxx",
<                 "BASE_URL=https://xxxxxxxxxxxxxxx",
<                 "REDESIGN="
---
>                 "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
56,61c48
<             "Cmd": [
<                 "npm",
<                 "start",
<                 "--silent"
<             ],
<             "ArgsEscaped": true,
---
>             "Cmd": null,
64,67c51,52
<             "WorkingDir": "/app",
<             "Entrypoint": [
<                 "docker-entrypoint.sh"
<             ],
---
>             "WorkingDir": "/",
>             "Entrypoint": null,

as you can see a lot of the environment is lost as well ass the WORKDIR and CMD

tried to use "img" to build images here and have same problem - CMD, ENTRYPOINT and WORKDIR are missing, therefor images cannot be run easily anymore.
build with img v0.5.10 (static linux amd64 binary or latest docker image).

I just opened a PR to fix this: https://github.com/genuinetools/img/pull/326

I just opened a PR to fix this: https://github.com/genuinetools/img/pull/326


Frequent "no method named as_encoded_bytes" error

Problem
I get this error I think every time I launch VS Code. Is it possibly a version mismatch, and installing with --locked would solve it?
Thank you!
Logs

OS: darwin (23.5.0)
VSCode: 1.91.1
Error message
    Updating crates.io index
  Installing flowistry_ide v0.5.41
    Updating crates.io index
   Compiling proc-macro2 v1.0.86
   Compiling unicode-ident v1.0.12
   Compiling serde v1.0.204
   Compiling equivalent v1.0.1
   Compiling hashbrown v0.14.5
   Compiling winnow v0.5.40
   Compiling camino v1.1.7
   Compiling log v0.4.22
   Compiling cfg-if v1.0.0
   Compiling byteorder v1.5.0
   Compiling serde_json v1.0.121
   Compiling anyhow v1.0.86
   Compiling semver v1.0.23
   Compiling index_vec v0.1.3
   Compiling splitmut v0.2.1
   Compiling ryu v1.0.18
   Compiling memchr v2.7.4
   Compiling smallvec v1.13.2
   Compiling itoa v1.0.11
   Compiling fxhash v0.2.1
   Compiling clap_lex v0.7.2
   Compiling adler v1.0.2
   Compiling intervaltree v0.2.7
error[E0599]: no method named `as_encoded_bytes` found for reference `&OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:187:26
    |
187 |         let bytes = self.as_encoded_bytes();
    |                          ^^^^^^^^^^^^^^^^ method not found in `&OsStr`

error[E0599]: no method named `as_encoded_bytes` found for reference `&OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:196:26
    |
196 |         let bytes = self.as_encoded_bytes();
    |                          ^^^^^^^^^^^^^^^^ method not found in `&OsStr`

   Compiling heck v0.5.0
error[E0599]: no method named `as_encoded_bytes` found for reference `&OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:202:26
    |
202 |         let bytes = self.as_encoded_bytes();
    |                          ^^^^^^^^^^^^^^^^ method not found in `&OsStr`

error[E0599]: no function or associated item named `from_encoded_bytes_unchecked` found for struct `OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:207:29
    |
207 |             unsafe { OsStr::from_encoded_bytes_unchecked(s) }
    |                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `OsStr`

error[E0599]: no method named `as_encoded_bytes` found for reference `&OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:211:26
    |
211 |         let bytes = self.as_encoded_bytes();
    |                          ^^^^^^^^^^^^^^^^ method not found in `&OsStr`

error[E0599]: no method named `as_encoded_bytes` found for reference `&OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:226:29
    |
226 |         let haystack = self.as_encoded_bytes();
    |                             ^^^^^^^^^^^^^^^^ method not found in `&OsStr`

error[E0599]: no function or associated item named `from_encoded_bytes_unchecked` found for struct `OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:234:24
    |
234 |                 OsStr::from_encoded_bytes_unchecked(first),
    |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `OsStr`

error[E0599]: no function or associated item named `from_encoded_bytes_unchecked` found for struct `OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:235:24
    |
235 |                 OsStr::from_encoded_bytes_unchecked(second),
    |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `OsStr`

error[E0599]: no method named `as_encoded_bytes` found for reference `&OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:277:24
    |
277 |         let bytes = os.as_encoded_bytes();
    |                        ^^^^^^^^^^^^^^^^ method not found in `&OsStr`

error[E0599]: no function or associated item named `from_encoded_bytes_unchecked` found for struct `OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:280:20
    |
280 |             OsStr::from_encoded_bytes_unchecked(first),
    |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `OsStr`

error[E0599]: no function or associated item named `from_encoded_bytes_unchecked` found for struct `OsStr` in the current scope
   --> /Users/maximilian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_lex-0.7.2/src/ext.rs:281:20
    |
281 |             OsStr::from_encoded_bytes_unchecked(second),
    |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function or associated item not found in `OsStr`

   Compiling anstyle v1.0.8
For more information about this error, try `rustc --explain E0599`.
error: could not compile `clap_lex` (lib) due to 11 previous errors
warning: build failed, waiting for other jobs to finish...
error: failed to compile `flowistry_ide v0.5.41`, intermediate artifacts can be found at `/var/folders/wf/s6ycxvvs4ln8qsdbfx40hnc40000gn/T/cargo-install7DNtCm`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Full log: https://paste.rs/yc1dt

Ah yes I was missing a --locked on the cargo install. I just released v0.5.42 which fixes this issue, and your VSCode should automatically update. Please let me know if the error persists.}

Thanks! That fixed that one :)


Upgrade rook-ceph chart to v1.3.0

I'll let the dist settle a few days before upgrading.
https://github.com/rook/rook/releases/tag/v1.3.0

Done


Server-side version?

I tested this on my Fabric 1.18.2 server and though it does allow vanilla clients to connect, the mod does not function correctly (no errors are found in the console). I would love to see a server-side version of this mod.
Thanks!

hey Gryzle, I have no plans to create a server side version of this mod.


add a search for experience worlds in experience world section

Description
Since when you asign an experince world to a category you've got a search bar to search your experience world. Add the same search bar to the shopping experience section so that you can find your world faster.

Hello,
thank you for creating this issue.
I have opened a ticket on our Issue Tracker for you. See the ticket link: https://issues.shopware.com/issues/NEXT-7119
Please use this ticket to track the state of your issue.

Hi @MortisReturns
since this is a feature request I have imported this into a ticket where other community members can vote for it.
If you don't have anything to discuss here I'd like to close this issue since this is not an "Issue" :)
Sunny Regards
Pantrtxp


OCI template default version

When adding OCI charts as templates, if we do not enter the version, an un-descriptive error will pop up. This is because the OCI charts do not have a default fallback for version → currently, you must enter a valid version of the OCI chart.
We should implement a default that resolves to the latest released version.
Steps to reproduce:

go to Templates tab

click on Add template reference

try connecting an OCI chart, but do not input the version
### For example:
repo: oci://registry-1.docker.io/bitnamicharts
path: wordpress
version:

You will receive an error!

But if you put x.x.x in the version field, the template will be successfully added

Hello,
May I take this?

Hi @pithecuse527, of course you can!
I assigned you 🙂

Here is the PR :)
https://github.com/cyclops-ui/cyclops/pull/461

Resolved with #461


New version: LinwoodCloud.Butterfly.Nightly version 2.0.0-beta.16

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-Executable-Error


[Tracking] Remove all uses of lib.mdDoc

Since https://github.com/NixOS/nixpkgs/pull/237557 was merged, lib.mdDoc has been a no-op. Let's remove the places that use it.
$ rg -w '(lib\.)?mdDoc' -o --no-filename | sort | uniq -c
  12356 lib.mdDoc
   1242 mdDoc

as this seems to break the current home-manager project - wouldn't it be reasonable to wait a bit longer / issue a warning when this is used instead of removing it alltogether?

wouldn't it be reasonable to wait a bit longer / issue a warning

There is a warning, unfortunately it's broken.
nix-repl> lib.options.mdDoc "test"
trace: warning: lib.mdDoc was removed from nixpkgs. Option descriptions are now in Markdown by default, you can remove any remaining uses of it.
"test"

nix-repl> lib.mdDoc "test"
error: attribute 'mdDoc' missing
       at «string»:1:1:
            1| lib.mdDoc "test"
             | ^

as this seems to break the current home-manager project - wouldn't it be reasonable to wait a bit longer / issue a warning when this is used instead of removing it alltogether?

I'm mostly interested in removing the use of lib.mdDoc in nixpkgs itself. Obviously there's a much longer period where it remains accessible from lib, likely originating from lib/deprecated.nix.

Closed by https://github.com/NixOS/nixpkgs/pull/303841 (thanks @stuebinm!)

ah sorry for the breakage everyone — I added that warning assuming it would be fine, but missed that mdDoc was only exposed via an inherit into lib.mdDoc (which of course got automatically removed along with all the other inherits).

No worries, it'll be fixed soon enough. Thanks for the original PR; maybe this will get HM to remove the usages sooner too ;)

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nix-darwin-is-broken/43497/2

Giving a reasonable deprecation period is how we should handle anything removed from lib. In this case it was removed from hm and nix-darwin fairly quickly, but apparently we still have a lot more consumers using this function. At the very least they should know why they are getting this error for now.

Currently, lib.mdDoc still seems to exist but print a warning (see #304277) which consequently makes our builds fail

Besides, I do find it a little strange that simply defining the function in nixpkgs without using it would fail the CI.

@lorenzleutgeb you should only get this warning if the lib.mdDoc function is actually used somewhere within the code you're evaluating. Unfortunately, due to how builtins.trace works, there is no easy way to find out where that use site is, which can indeed be annoying if it's not in your own code but somewhere in your dependencies (indeed the definition of lib.warn in lib/trivial.nix has a TODO item attached to it that essentially says "figure out a way to show users where the warning came from").
but from quickly looking at your repo, a reasonable bet is that you're getting it since dream2nix still has some uses of mdDoc in it, and you depend on it.

@stuebinm The offending option is actually printed: https://github.com/ngi-nix/ngipkgs/actions/runs/8780863139/job/24091654727#step:4:108 It seems that this occurrence of lib.mdDoc has been removed in the meantime, so I'll try updating the nixpkgs input of that Flake. We evaluate all of NixOS since we're generating Option documentation, so it's not really relevant to trace down single occurrences. If it's somewhere in NixOS, it will fail our build.

seems like it was fixed in #305379, so you'd need a commit after d9ad2e5a1a4ed119546f026aad1f167b1678b061


Tibialyzer <IP_ADDRESS>-beat

downloaded all fine and unzipped to desktop
but was it went to run it a Windows SmartScreen popped>
saying it prevented an unrecognised application from starting as it  may harm my pc
is this ok to run ?

This only happened with <IP_ADDRESS> but not with older versions?

no not with the older one that still works ok
sorry for late feedback something popped up


Increase browser session duration

Is your feature request related to a problem? Please describe.
I keep SEPAL open in a browser tab. My session seems to expire pretty regularly, requiring me to re-log in.
Describe the solution you'd like
Increase the session duration to at least one week, and extend it with each activity.

Sessions stay open for a lot longer now. Let me know if this seems enough.


work nicely with 'docker service ...'

Does weave work "nicely" with the new Docker 1.12 docker service ... functionality?
In particular...

does it work when using the proxy?
does it work when using the default 'weave' plugin network?
does it work when using custom networks created from 'weave' driver?
does it work when the service is using VIPs (a feature of docker services)

The objective of this issue is to:

answer the above
write a blog post, provided some things do work
tweak docs, if necessary, to explain how to make things work
file issues, if necessary, to make things work

Going to comment here instead of making a new issue. Is there any progress on this? As far as I can tell weave doesn't work at all with services in swarm mode.
root@localhost:~# docker service create --replicas 1 --name nginx --network weave nginx
Error response from daemon: network weave is not eligible for docker services

Is there any way to use docker services and weave, or is it currently impossible?

From https://docs.docker.com/engine/extend/plugins_network/#/network-driver-plugins-and-swarm-mode

Docker Engine running in swarm mode currently only supports the built-in overlay driver for networking. Therefore existing networking plugins will not work in swarm mode.

@rade Thanks, that's what I suspected. I guess it's time to consider kubernetes.

Note #2727 made most of this work with a new "v2" plugin; we still have to document it.


fix potential memory leaks when errors happen

==3709953== HEAP SUMMARY:
==3709953==     in use at exit: 276,541 bytes in 23 blocks
==3709953==   total heap usage: 29 allocs, 6 frees, 280,682 bytes allocated
==3709953==
==3709953== 1 bytes in 1 blocks are still reachable in loss record 1 of 23
==3709953==    at 0x4866EC0: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-arm64-linux.so)
==3709953==    by 0x48E2BC3: ub_initstate (random.c:85)
==3709953==    by 0x489B067: ub_ctx_create_nopipe (libunbound.c:114)
==3709953==    by 0x489B31F: ub_ctx_create (libunbound.c:180)
==3709953==    by 0x10E203: main (unbound-host.c:433)
==3709953==
......
==3709953== 8,192 bytes in 1 blocks are still reachable in loss record 22 of 23
==3709953==    at 0x4866EC0: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-arm64-linux.so)
==3709953==    by 0x48E427B: regional_create_custom (regional.c:94)
==3709953==    by 0x48DEA03: edns_strings_create (edns.c:57)
==3709953==    by 0x489B0F3: ub_ctx_create_nopipe (libunbound.c:157)
==3709953==    by 0x489B31F: ub_ctx_create (libunbound.c:180)
==3709953==    by 0x10E203: main (unbound-host.c:433)
==3709953==
==3709953== 262,144 bytes in 1 blocks are still reachable in loss record 23 of 23
==3709953==    at 0x486933C: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-arm64-linux.so)
==3709953==    by 0x48C826F: config_create (config_file.c:179)
==3709953==    by 0x48C85AF: config_create_forlib (config_file.c:383)
==3709953==    by 0x489B0BB: ub_ctx_create_nopipe (libunbound.c:130)
==3709953==    by 0x489B31F: ub_ctx_create (libunbound.c:180)
==3709953==    by 0x10E203: main (unbound-host.c:433)
==3709953==
==3709953== LEAK SUMMARY:
==3709953==    definitely lost: 0 bytes in 0 blocks
==3709953==    indirectly lost: 0 bytes in 0 blocks
==3709953==      possibly lost: 0 bytes in 0 blocks
==3709953==    still reachable: 276,541 bytes in 23 blocks
==3709953==         suppressed: 0 bytes in 0 blocks
==3709953==
==3709953== For lists of detected and suppressed errors, rerun with: -s
==3709953== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

@wcawijngaards @gthess could you review these commits?

Thanks for this, the code looks cleaner that way.


Light Switch Block Entity Crashes Server

It appears that on 1.20.1 fabric, the light switch block, it can cause a crash when updating the tick pattern.
Full error log from the crash:
java.lang.Error: Watchdog
	at java.base@21.0.4/jdk.internal.misc.Unsafe.park(Native Method)
	at java.base@21.0.4/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:269)
	at net.minecraft.class_1255.method_20813(class_1255.java:151)
	at net.minecraft.class_1255.method_18857(class_1255.java:141)
	at net.minecraft.class_3215.method_12121(class_3215.java:140)
	at net.minecraft.class_3215.method_20586(class_3215.java:123)
	at net.minecraft.class_3215$$Lambda/0x000071a972f16ee0.get(Unknown Source)
	at java.base@21.0.4/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
	at net.minecraft.class_1255.method_18859(class_1255.java:156)
	at net.minecraft.class_3215$class_4212.method_18859(class_3215.java:564)
	at net.minecraft.class_1255.method_16075(class_1255.java:130)
	at net.minecraft.class_3215$class_4212.method_16075(class_3215.java:573)
	at net.minecraft.class_1255.method_18857(class_1255.java:139)
	at net.minecraft.class_3215.method_12121(class_3215.java:140)
	at net.minecraft.class_1937.method_8402(class_1937.java:204)
	at net.minecraft.class_4538.method_22342(class_4538.java:156)
	at net.minecraft.class_1937.method_8497(class_1937.java:198)
	at net.minecraft.class_1937.method_8320(class_1937.java:370)
	at net.minecraft.class_7159$class_7161.method_41707(class_7159.java:131)
	at net.minecraft.class_7159.method_41702(class_7159.java:78)
	at net.minecraft.class_7159.method_41706(class_7159.java:65)
	at net.minecraft.class_7159.method_41705(class_7159.java:47)
	at net.minecraft.class_3218.method_8452(class_3218.java:1018)
	at net.minecraft.class_3218.method_8408(class_3218.java:1433)
	at net.minecraft.class_1937.method_30092(class_1937.java:246)
	at net.minecraft.class_1937.method_8652(class_1937.java:213)
	at com.mrcrayfish.furniture.refurbished.blockentity.LightswitchBlockEntity.setNodePowered(LightswitchBlockEntity.java:50)
	at com.mrcrayfish.furniture.refurbished.electricity.IModuleNode.updateNodePoweredState(IModuleNode.java:39)
	at com.mrcrayfish.furniture.refurbished.electricity.IModuleNode.moduleTick(IModuleNode.java:58)
	at com.mrcrayfish.furniture.refurbished.electricity.ElectricityTicker$$Lambda/0x000071a972c8af90.accept(Unknown Source)
	at com.mrcrayfish.furniture.refurbished.electricity.ElectricityTicker.tickSet(ElectricityTicker.java:78)
	at com.mrcrayfish.furniture.refurbished.electricity.ElectricityTicker.tick(ElectricityTicker.java:61)
	at net.minecraft.class_1937.handler$eic000$refurbished_furniture$refurbishedFurniture$TickBlockEntitiesHead(class_1937.java:4553)
	at net.minecraft.class_1937.method_18471(class_1937.java)
	at net.minecraft.class_3218.method_18765(class_3218.java:390)
	at net.minecraft.server.MinecraftServer.method_3813(MinecraftServer.java:897)
	at net.minecraft.class_3176.method_3813(class_3176.java:283)
	at net.minecraft.server.MinecraftServer.method_3748(MinecraftServer.java:824)
	at net.minecraft.server.MinecraftServer.method_29741(MinecraftServer.java:671)
	at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer.java:265)
	at net.minecraft.server.MinecraftServer$$Lambda/0x000071a97274c000.run(Unknown Source)
	at java.base@21.0.4/java.lang.Thread.runWith(Thread.java:1596)
	at java.base@21.0.4/java.lang.Thread.run(Thread.java:1583)

This has happened twice within 5 minutes on our server. Any other information I can provide, let me know and I will be happy to share what I am able to.

Will do! Sorry for the delay, I'll get that though when I am home. This whole weekend was just focused on getting the server back to a stable state.

@MrCrayfish https://mclo.gs/8FNhrAZ Sorry again for the delay! If you end up finding that it might be something else, more than happy to share any other logs with you.

Just based on the log, I assume you are using a Fabric + Spigot hybrid server? Although the error looks to be triggered by my mod, it may actually be your server software. I searched up Watchdog, and it seems to purposely crash the server if the max-tick-time reaches a certain threshold. Try going through your server configuration to boost this value. Adding mods will definitely slow your tick rate, and the default max-tick-time may be only suitable for a minimal amount of mods.

Might not be exactly related by here is the article I found on Watchdog
https://help.ggservers.com/en-us/article/what-is-watchdog-and-why-does-it-crash-my-server-n8aex/

It's just Fabric, no spigot :)

Apologies for the late reply @MrCrayfish! I am not getting any emails from Github right now for some reason. (I will be more diligent on checking notifications on Github though)
Max tick time is set to 60000ms.

I've searched up the error and Dynmap seems to be a potential cause (and the 1.20.1 version is a beta version). Seeing as you have it installed, try removing it.
I am confident that the issue is not caused my mod, simply due to the fact that I am calling vanilla code to update the lightswitch from an unpowered to powered blockstate. This is identical to a vanilla furnace going from an unlit to lit state.
Let me know how that goes


Update the Warm Aggregation trigger for SQL

In the SQL table, that we write to for the Stream Analytics output (warm aggregation) we need to update the behavior of the trigger.
It appears tha Stream Analytics does a bulk insert into the table. We cannot guarantee the ordering of the inserts.
The desired behavior is:

we don't want duplicate entries
we want to make sure that we are writing the latest

This issue is related to #67.  The SQL is killing Streaming Analytic's job


Following links should stay in the computing language of the previous page

its seems bad that we end up on a C# page despite this originating page being the Winrt C++ page - https://github.com/MicrosoftDocs/winrt-api/issues/580

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

ID: a4db0aab-b906-9dec-381c-ceccc1e90c45
Version Independent ID: 493a4c50-ffa1-5e32-c757-92306c952887
Content: XAML controls; bind to a C++/WinRT property - UWP app developer
Content Source: windows-apps-src/cpp-and-winrt-apis/binding-property.md
Product: windows
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Hi, @Bluesman74, thanks for filing the issue. The source topic is a conceptual topic about the C++/WinRT language projection, but the destination topic is a WinRT API reference topic. And reference topics are all language-agnostic (there isn't a notion of a C# API reference topic). If you scroll to the top of any WinRT API reference topic you'll see (in the top-right corner) Feedback, Share, Theme, and Language icons. If you click the Language icon then you'll be able to choose a language (C#, C++/WinRT, etc.) to view the API's syntax block in. The browser remembers your choice for next time. There's no mechanism for overriding that choice (nor setting it to a different default) based on web page navigation; and I don't think that feature would work well in enough cases. In this case if you program primarily in C++/WinRT then I'd recommend choosing that from an API reference topic and then you'll be all set. ~Steve

@Bluesman74, I'll go ahead and close this issue now since it's been a while, and it feels resolved. Please reopen if I made a mistake in closing. ~Steve


feat: upgrade core-utils

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Behat 3 - Issue communicating between contexts - registration error?

I'm following the instructions in:
http://docs.behat.org/en/latest/cookbooks/accessing_contexts_from_each_other.html
I have a number of contexts registered in behat.yml:
    suites:
        testSuite:
            paths:
              - %paths.base%/features
            contexts:
              - \BehatTests\AbstractContext
              - \BehatTests\AbstractReviewContext
              - \BehatTests\ActivityContext
              - \BehatTests\ApiContext
              - \BehatTests\BrowseContext
              - \BehatTests\BrowserSessionContext
              - \BehatTests\ChangeContext
              - \BehatTests\CommentContext
              - \BehatTests\CommonContext
              - \BehatTests\DashboardContext
              - \BehatTests\EmailContext
              - \BehatTests\FeatureContext
              - \BehatTests\FeatureMinkContext
              - \BehatTests\FileContext
              - \BehatTests\GroupContext
              - \BehatTests\JobContext
              - \BehatTests\LoginContext
              - \BehatTests\NotificationContext
              - \BehatTests\P4Context
              - \BehatTests\ProjectContext
              - \BehatTests\ReviewContext
              - \BehatTests\UserContext

All of my contexts except the FeaureMinkContext, extend AbstractContext in order to share a number of common methods from there, however, due to needing the extend MinkContext, I can't do this with my FeatureMinkContext...
As such, I implemented the suggestion in the linked manual page, however, whenever behat calls my BeforeScenario method that should set my AbstractContext instance from within FeatureMinkContext (or any other context from within any other context), I see the following error:
'AbstractContext' context is not found in the suite environment. Have you registered it?
I've tried passing the context name including the namespace as they're loaded in behat.yml but with no luck.
Any suggestions on what I'm doing wrong?

Just look at the InitializedContextEnvironment.
Try dump all existing contexts in your suite:
/**
 * @BeforeScenario
 */
public function gatherContexts(BeforeScenarioScope $scope)
{
    $environment = $scope->getEnvironment();
    var_dump($environment->getContextClasses());
    exit;
}

Thanks, for some reason my IDE wasn't showing me that method - shall have a proper dig around the class structure and find out why.
Seems the method expects the same as behat.yml but without the leading forwardslash, in case anyone else is having the same issue.


update specs so they cover the correct Actions

Turns out these two were wrong. So I want to make sure they're being covered correctly.

Any idea why those specs failed?


ENH: generalization of continuous and discrete Riccati solvers and a new wrapper "balance"

Recently, in gh-6572, a more accurate solver has introduced.
This PR makes it more accurate such that all examples in the test cases pass (with acceptable accuracy). In a few cases, surpasses the matlab equivalent solutions.
Now the tests actually check the accuracy with number of decimals required to be acceptable per test case
The improvement is due to the better preconditioning of the data matrices which is known as balancing. Balancing can also be used by the users prior to matrix decompositions as a standalone fashion and hence the new basic function "balance".
More details are added to both function docstrings and tested are modified accordingly.

Can anyone check what the following gives ?
from scipy.linalg import get_lapack_funcs
A = np.array([[1, 0, 1e-4],[1, 1, 1e-2],[1e4, 1e2, 1]])
gebal = get_lapack_funcs(('gebal'),(A,))
ba, lo, hi, ps, info = gebal(A, scale=1, permute=1,overwrite_a=0)

I get [-9,-3,4] but the test gives [-13,-7,0]

Speaking of which, could you please let me know how things go in "refguide" ?
For the previous point, I really don't know what is happening. I tried in a few more machines and it goes through.

Add any new routines to scipy/linalg/__init__.py docstring, so that it
gets linked to the documentation.

It's possible details of the balancing differ in different LAPACK
versions. If so, the tests probably cannot test the exact results but
only some invariant properties.

In the LAPACK version 3.5.0 they have modified GEBAL family so that is indeed possible but still, that's really strange that it varies four orders of magnitude. But anyways, I'll just find another way to test it.

I was playing around with the solver and decided to upgrade the solver to full-fledged generalized solver to take the extra terms into account. With balancing, I think the solver is at least competent with other numerical software on this particular type of equation solutions.

Can anyone check what the following gives ?

In [3]: from scipy.linalg import get_lapack_funcs
   ...: A = np.array([[1, 0, 1e-4],[1, 1, 1e-2],[1e4, 1e2, 1]])
   ...: gebal = get_lapack_funcs(('gebal'),(A,))
   ...: ba, lo, hi, ps, info = gebal(A, scale=1, permute=1,overwrite_a=0)
   ...:

In [4]: ba
Out[4]:
array([[ 1.        ,  0.        ,  0.8192    ],
       [ 0.015625  ,  1.        ,  1.28      ],
       [ 1.22070312,  0.78125   ,  1.        ]])

In [5]: lo
Out[5]: 0

In [6]: hi
Out[6]: 2

In [7]: ps
Out[7]: array([  1.22070312e-04,   7.81250000e-03,   1.00000000e+00])

In [8]: info
Out[8]: 0

Thank you @rgommers . Apparently not everyone is using the latest LAPACK (probably depends on Linux distro variety). I've changed the test to take that into account by forcing the test produce something equivalent up to an offset and check the difference

Apparently not everyone is using the latest LAPACK

Indeed. We support down to 3.1.0 IIRC. In gh-6051 there's an effort underway to up the minimum version to 3.3.1. But we'll need to support a reasonably wide set of versions, otherwise building from source can get very painful.

I was playing around with the solver and decided to upgrade the solver to full-fledged generalized solver to take the extra terms into account.

Sounds like a good idea. For next time: I would have opened a separate PR for gdare based on this one. Smaller PRs are a lot easier to review and merge.

@ArmstrongJ as the original author of these solvers you may be interested in this PR and in gh-6622. If you have time for a review or some comments, that'd be great.

In terms of the code, nothing much changes but the functionality is more general. Indeed I might be misleading in that sense probably. As a summary, from the previous PR, the main differences are : on the solver itself

balancing
more items in the matrix pencil (e and s terms)

I'm still getting used to using branches and interaction of them. Since there is a crucial dependency to balance I went this way. But I get your point.

OK as per Ralf's comment. I'll delay the continuous time version to another PR depending on the outcome of this one.
What will happen roughly is that I'll refactor the argument checks to another _are_argument_check() function because continuous-time solver is doing the same checks. Also CAREX tests will be added for the continuous-time solver. Hopefully that will conclude this stream of PRs. 😄

Thanks for contacting me, @rgommers, but I have long since moved on from using Python for any scientific computing.  I haven't even thought about an alegbraic Riccati equation in years.  As this is now quite outside my field, I'll happily defer to others concerning the pull request.
I should point out that my solvers were relatively basic and not particularly robust.  While theoretically correct, they definitely had issues.  Any improvements in the solvers should be accepted (after review, of course).  Best of luck!

Cool, thanks for the feedback @ArmstrongJ

Ralf already mentioned that PRs should be smaller to review. However I think since the rest is reviewed and also the continous_are is almost a duplicate addition, I think this is ready for decision if the tests pass

Anyone knows why Circle CI exits with
Encoding error:
'ascii' codec can't decode byte 0xe2 in position 7463: ordinal not in range(128)
The full traceback has been saved in /tmp/sphinx-err-jKBuO_.log, if you want to report the issue to the developers.
make: *** [html-scipyorg] Error 1
make: Leaving directory `/home/ubuntu/scipy/doc'

from solve_continuous_are ?

Sounds like there's a non-ascii character somewhere in the docstring--didn't see one upon first scan though.

Had a browse through the codecov report, looks all right. Except for the many checks for incorrect inputs and singularity, almost all code is tested.

Ah yes, let me add those.

I've checked a few other details and I think this is pretty much the finalized version.

@pv @rgommers @person142 . In the last comments, @ev-br brought up a good point. The function name might indeed be a bit too generic for general use. What's your take on this ?
Some background: The balancing term is well-defined in the matrix community. BALancing for GEneral matrices is also the name xGEBAL in the LAPACK routines. Also related concepts such as balanced realizations of state space representations use this word. The relevant names from matlab routines are, e.g., balance, balreal, balred (model reduction) and so on. But at the same time we have mscale, matscale, lrscale etc. for two sided matrix scaling.
This doesn't imply that we should follow the trail but still might be good to retain some relation to it. In the rank case, I see that we went on with matrix_rank. So I guess an obvious choice is matrix_balance. What do you think ?

matrix_balance sounds fine, relatively standard term afaik

Hi everyone, could you please let me know your decision about this when you have time?

matrix_balance sounds good to me to, so we're all agreed on that.
will try to have a look at the latest changes this weekend.

@rgommers if the size of the commit is frightening, it is mostly pep8 of the tests file. I had some free time so I went through whole files. The actual commit is still the same as before :)

@rgommers if the size of the commit is frightening,

no not frightening, just a heavy review load and todo list (i.e. business as usual). will get back to this soon

The only thing I didn't try to review was the linalg for the generalized dare. I do note that there are no tests added for that - that needs fixing.

Tests added and look fine. Last added commits and pep8 changes also look good. So hitting the green button. Thanks @ilayn, all!

Ah thank you. Pleasure is mine indeed.

hi, this is my first comment on github, so i'm not sure, where to actually post this...
i am trying to solve a generalized dare where i have s but not e.... this case throws an error in line 577 where e is None.... i temporarily fixed it  by adding
       if e is None:             u, _ = qr(np.vstack((u[:m, :m], u[m:, :m])))         else:             u, _ = qr(np.vstack((e.dot(u[:m, :m]), u[m:, :m])))
but there is probably a more elegant solution to this.....

Hi @simonmarwitz
I don't have access to a machine right now until this evening but can you also add a small set of matrices to replicate the error. It might be a case where I have missed the generalized case. It is not tested as rigorously as the regular case. So we can add it as a test case for future.

I've checked again a bit on the phone. You are right, I should have checked for the existence of E instead of gen_are flag.
If not confidential, could you still please send your problem? I am having difficulty finding relevant examples for testing.

Thanks for taking the time to check on my problem. I have attached the matrices i use and the code that produces the mentioned error. ( I am using P for further computations which still do not produce satisfying results, but this may be due to many other things in my code. I am still investigating the issue)
print(np.allclose(S.T,S_T)) print(np.allclose(Q,Q.T)) print(np.allclose(R,R.T)) Q = (Q + Q.T)/2 S = (S + S_T.T)/2 R = (R + R.T)/2 P = scipy.linalg.solve_discrete_are(a=a, b=b, q=Q, r=R, s=S)
dare_matrices.zip

@simonmarwitz I've opened a PR linked above for this. Thanks for the data. Please let us know if you encounter further issues.
Just a reminder: You can report bugs much more conveniently if you use the New Issue machinery in the Issues tab. It also has a better visibility to everyone rather than only the ones who follow this thread.

thanks for fixing it.... i am very happy with the results i get so far....


protocol kwarg in get_tags not working

Passing any protocol kwargs to _get_tags  makes no sense, because it is not passed to _get_request_headers, which leads to exception in _get_auth_token, because of resolving from DEFAULT_PROTOCOL here.

If I'm following correctly, the issue being reported is that the default value of DEFAULT_PROTOCOL (https) is not aligned with the passed value of the protocol parameter, because it is not exposed via the call stack to the method the populates the auth headers ...?
Without knowing the use case (assuming that protocol is being provided to disable TLS, for local testing -- e.g. http), it might be easier to override the value of DockerRegistryClientAsync.DEFAULT_PROTOCOL directly, which would align the protocols used for any / all invoked methods.
If the scenario is different, such as synchronizing content between two registries of mixed protocols, it would be helpful to better understand the specifics of the protocols involved.

that the default value of DEFAULT_PROTOCOL (https) is not aligned with the passed value of the protocol parameter, because it is not exposed via the call stack to the method that populates the auth headers

Not exactly.
The issue is about the protocol parameter, which is not passed to method, that populates auth headers.
In other words, the only way to populate auth token over http is to change DockerRegistryClientAsync.DEFAULT_PROTOCOL, and also it changes only globally, not per client instance.

assuming that protocol is being provided to disable TLS, for local testing -- e.g. http

Yes, exactly. In my case, I need at one time access my local registry over http and also the global docker registry over https.

It's been a while since I worked on this package; had to migrate off docker-compose, update a few tests, and defer some dockerhub changes, but I think I managed to isolate a scenario that gives some confidence that the expose protocol parameter is working. Give it a try, let me know if you run into an edge-case.


Interface 'ElectronOptions' cannot simultaneously extend types 'Options' and 'NodeOptions'.

I have this added as npm dependency:
  "dependencies": {
    "@sentry/electron": "0.15.0"
}

And using it in the code like this, both on renderer and main proccess:
import * as Sentry from '@sentry/electron';

Sentry.init({
  dsn: AppConfig.sentryDsn
});

After npm install, I run npm start and I am getting this error. Are the typings wrong ?

Any idea how to get it to work?

From the linked PR it looks like you got this sorted!


Mesh cannot be accessed when running in Docker on @graphql/cli versions >= 0.20.0

Describe the Bug
Since @graphql-mesh/cli v0.20.0, the mesh (as gateway) cannot be accessed when running inside of a Docker container. Versions before v0.20.0 (e.g. v0.19.2) work.
To Reproduce
Steps to reproduce the behavior:

Create the following files:

Dockerfile:FROM node:alpine
WORKDIR /app
COPY . .
RUN yarn install
CMD ["yarn", "start"]

package.json:{
    "scripts": {
        "start": "mesh serve"
    },
    "dependencies": {
        "@graphql-mesh/cli": "0.20.0",
        "@graphql-mesh/openapi": "^0.15.0",
        "graphql": "^15.5.0"
    }
}

.meshrc.yaml:sources:
- name: Wiki
  handler:
    openapi:
      source: https://api.apis.guru/v2/specs/wikimedia.org/1.0.0/swagger.yaml

CodeSandbox containing the above files: https://codesandbox.io/s/serverless-pine-5x8hg?file=/package.json
After running yarn start, you should be able to access the mesh successfully on http://localhost:4000. Try to run in a Docker container as follows:

docker build . in project directory
docker run -p 4000:4000 --rm -it ${BUILT_CONTAINER_NAME}

Try to access the mesh on http://localhost:4000, and you should not be able to connect. Try the docker build and run process again with @graphql-mesh/cli version 0.19.2, and it should work. Versions above 0.20.0 should also not work.
Expected Behavior
The mesh can be accessed inside of a Docker container on @graphql-mesh/cli versions >= 0.20.0.
Environment

OS: Arch Linux x64, kernel 5.11.11-arch1-1
@graphql-mesh/cli: v0.20.0
@graphql-mesh/openapi: v0.15.0
graphql: v15.5.0

Additional Context
I looked through the changes introduced on the v0.20.0 release notes, and looked through the mesh gateway documentation. I may have missed something, such as a new setting to configure this to work ― forgive me if so.

I think you mean @graphql-mesh/cli by @graphql/cli.
Could you try it with the following change after updating to the latest version<EMAIL_ADDRESS>sources:
  - name: Wiki
    handler:
      openapi:
        source: https://api.apis.guru/v2/specs/wikimedia.org/1.0.0/swagger.yaml
serve:
  hostname: <IP_ADDRESS> # << Add this

Oops, you are correct, I meant @graphql-mesh/cli. Updated the original post to prevent confusion in case people look at this in the future.
That worked! Thank you, Arda.


Add gui for an easier usage

The gui should be builded by QT
The gui will be part of an extra example

an gui 2D examples has been added


[BUG] First argument is skipped

Good morning and thank you so much for writing this tool.
I'm using it and despite it serves the same purpose as modGRUBShell.efi it's way more portable (especially when having ESPs with low space issues).
Anyway, I'm experiencing a weird bug while trying to execute the tool via OpenCore. I don't know if you ever had any Hackintoshing experience in the past or not, but basically it's a bootloader and for what concerns us, it can be used also for creating custom tools entries (e.g. CFG Lock unlock entry which runs .\setup_var.efi CFG_LOCK_OFFSET 0x00 -n VarStoreId).
What basically happens is that after adding the tool in the bootloader configuration file, it skips the first argument.
Below the code that I added to the bootloader configuration file:
<dict>
	<key>Arguments</key>
	<string>0x527 0x00 -n Setup</string>
	<key>Auxiliary</key>
	<true/>
	<key>Comment</key>
	<string>UEFI command-line tool for read/write access of variables - CFG Lock unlock</string>
	<key>Enabled</key>
	<true/>
	<key>Flavour</key>
	<string>Auto</string>
	<key>FullNvramAccess</key>
	<true/>
	<key>Name</key>
	<string>setup_var - CFG Unlock</string>
	<key>Path</key>
	<string>setup_var.efi</string>
	<key>RealPath</key>
	<true/>
	<key>TextMode</key>
	<true/>
</dict>

What concerns us is the Arguments key with the value 0x527 0x00 -n Setup. If I run that custom entry, it doesn't write in the offset but rather reads the value of 0x00 under Setup VarStoreName, so it skips the first argument.
I already discussed this with the devs of the bootloader (you can read more here), and they pointed out this line which may be the reason of the bug.
The only way I could find to temporarily fix it is adding .\setup_var.efi (potentially can be literally any string, as it doesn't need to be any particular value) so the tool correctly parses the argument.
Do you think this can be fixed? Thank you so much and have a great day
--
dreamwhite

I temporarily commented line 172 and the tool works using OpenCore, but if I try running it from a UEFI shell (such as OpenShell.efi) then it raises the following error:

I'm definitely not a RUST nor a UEFI developer, but I think the right thing to do is:

if booting from a UEFI shell environment, then skip the first argument
if booting via other methods, such as OpenCore, then don't skip the first argument

I've added some checks to mitigate this problem in 0.2.0.
In short, if the program detects the first arg as a named argument (i.e. starts with '-'), or as a valid number, it will not drop it. Though it's a simple check, I think it could cover most common cases.


typeHandlers {typeName:(value,index,parent)=>any}

Status
IN DEVELOPMENT
Description
jsonexport(contacts, {
    handleObject: function(element, item, originalHandler){
        if (element instanceof Buffer) return [
            {item: element,
            value: element.toString(),}
        ];
        return originalHandler(element, item);
    }
}, function(err, csv){
    if(err) return console.log(err);
    console.log(csv);
});

I think this pull request shows promise.... However, you are complete right in its awkwardness to request a user to pass back a specific formatted array of objects.
 Expect for one item related to bitHound that I can't figure out.
Here is what I came up with:

handleCustoms - [{type:constructor, each:(value, index, parent)=>any}] Use this to define an array of constructors to match by to convert by the each function (see example)

handleCustoms
Define types by constructors and what function to run when that type is encountered
var jsonexport = require('jsonexport');

//definitions to type cast
var customs = [{
  type:Buffer,
  each:function(value,index,parent){
    return value.toString()
  }
}]

//data
var contacts = {
  'a' : Buffer.from('a2b', 'utf8'),
  'b' : Buffer.from('other field', 'utf8')
};

var options={
  handleCustoms:customs
}

jsonexport(contacts, options, function(err, csv){
  console.log( csv )
});

@AckerApple I like this implementation a lot! but i think we should use an object instead of an array and we should cast Buffers to string by default, i think thats what most users from this module will expect.
What you think about this implementation:
jsonexport(data, {
  typeHandler: {
      Buffer: (value,index,parent) => value.toString(),
  }
}, (err, csv) => {

});

I think its better this way because we make sure there is no duplicate handlers for the same type and its easier to extend the default handlers.
To support this we probably need to use instanceof, since typeof Buffer.from() returns object.
So we would need to loop in all props from typeHandler and check if there is one that matches.
Buffer.from('a2b', 'utf8') instanceof global['Buffer']
https://github.com/kauegimenes/jsonexport/pull/49/files#diff-d765e64fa489e3c85242992214ffb983R42

Ok, I like that too. Even simpler as an object instead on an array.
I’m using constructor to type check. I think instance of allow for inheritance checking as well. So I’m all good here.
I will work on it tomorrow. Passing out right now

YES! All checks flipping' finally passed.... Good grief BitHound and I got into a fight!
Do to the deprecation of existing handlers, I have moved the package.version to 2.1.0
This is what I came up with:
typeHandlers
Define types by constructors and what function to run when that type is matched
var jsonexport = require('jsonexport');

//data
var contacts = {
  'a' : Buffer.from('a2b', 'utf8'),
  'b' : Buffer.from('other field', 'utf8'),
  'z' : 22
};

var options={
  //definitions to type cast
  typeHandlers:{
    Array:function(value,index,parent){
      return 'replaced-array';
    },
    Boolean:function(value,index,parent){
      return 'replaced-boolean';
    },
    Number:function(value,index,parent){
      return 'replaced-number';
    },
    String:function(value,index,parent){
      return 'replaced-string';
    },
    Buffer:function(value,index,parent){
      return value.toString()
    }
  }
}

jsonexport(contacts, options, function(err, csv){
  console.log( csv )
});

The output would be:
a,a2b
b,other field
z,replaced-number

I wonder if we should document the following:
Do NOT do this
var options={
  typeHandlers:{
    Object:function(value,index,parent){
      return 'EVERYTHING IS AN OBJECT';
    }
  }
}

It's not an error and an developer will notice the terrible results anyhow.
Just thought I'd note it here

Wow nice work @AckerApple as aways =)
Looks good to merge for me!
I think its a nice idea to add the everything is an object example to the README  https://github.com/kauegimenes/jsonexport/pull/49#issuecomment-384975543
What other basic types we can handle by default? Maybe functions?

I’ll consider your last comment into another push and then will merge

Done and done. Please approve readme file addition of Contributors and then merge or I can merge but lets get this on NPM please.
New Contributors section as follows:
Contributors

Kauê Gimenes
Pierre Guillaume
Acker Apple
And many more...

Nice! Just published<EMAIL_ADDRESS>on npm!
Thanks @AckerApple =)


Not compabile with latest .Net 8 previews

I tried using this library with the latest .Net 8 preview 7 and am getting some runtime errors.  Is this something supported?  .Net 8 RC is around the corner...
e.g.:  The following runtime error:
Method not found: 'System.Collections.Generic.IEnumerable`1<Microsoft.EntityFrameworkCore.Metadata.IProperty> Microsoft.EntityFrameworkCore.Metadata.IEntityType.GetProperties()'.

Also seeing this. Look forward to an 8-compatible version.

Tried to make Prev. with v 8.0.0-preview.7.23375.4
With few changes build passes but can not run test, throws:

System.MissingMethodException
HResult=0x80131513
Message=Method not found: 'Void CoreTypeMappingParameters..ctor(System.Type, Microsoft.EntityFrameworkCore.Storage.ValueConversion.ValueConverter, Microsoft.EntityFrameworkCore.ChangeTracking.ValueComparer, Microsoft.EntityFrameworkCore.ChangeTracking.ValueComparer, Microsoft.EntityFrameworkCore.ChangeTracking.ValueComparer, System.Func`3<Microsoft.EntityFrameworkCore.Metadata.IProperty,Microsoft.EntityFrameworkCore.Metadata.IEntityType,Microsoft.EntityFrameworkCore.ValueGeneration.ValueGenerator>)'.
Source=EntityFrameworkCore.SqlServer.HierarchyId

Have found the issue, entity HierarchyId with prop type HierarchyId was the cause.

Published 8.0.0-preview.7
Added multitarget:
net8.0;net7.0;net6.0

Thanks!

published v rc.1.2
HierarchyId is using Microsoft.EntityFrameworkCore.SqlServer.HierarchyId
instead of EntityFrameworkCore.SqlServer.HierarchyId
MySql now also works since they have released 8.0.0-beta.1


Traefik is always installed, even when disable used.

I have cloned your repo, and just changed the addresses to match my infrastructure.  When I run it, the playbook runs with no errors, however, on checking I notice that Traefik is still installed, even though I have the default of --disable traefik.

When --disable traefik is entered Traefik should be omitted from the installation.

Steps to Reproduce

Clone your repo
Change IP addresses to match our server ( we are testing on a single master)
Run the playbook, this runs with no errors
Run kubectl get pods --all-namespaces on the target host, Traefik is installed.

Context (variables)
Target OS is Ubuntu 20.04
All variables are per your repo except the target IP addresses.
Variables Used
Directly from your repo
Hosts
host.ini
[master]
k3s0_test ansible_host=<IP_ADDRESS> ansible_user=?????? nasible_ssh_pass=??????

[node]

[k3s_cluster:children]
master
node

Possible Solution

[x] I've checked the General Troubleshooting Guide

Hey, can you please fill out the full template?  It seems that what you are experiencing is actually something wrong with your configuration in the template.  Thank you!

It is basically your all.yaml, with just ip addresses changed.
`---
k3s_version: v1.24.12+k3s1
this is the user that has ssh access to these machines
ansible_user: ansibleuser
systemd_dir: /etc/system/system
Set your timezone
system_timezone: "Your/Timezone"
interface which will be used for flannel
flannel_iface: "eth0"
apiserver_endpoint is virtual ip-address which will be configured on each master
apiserver_endpoint: "<IP_ADDRESS>"
k3s_token is required  masters can talk together securely
this token should be alpha numeric only
k3s_token: "some-SUPER-DEDEUPER-secret-password"
The IP on which the node is reachable in the cluster.
Here, a sensible default is provided, you can still override
it for each of your hosts, though.
k3s_node_ip: '{{ ansible_facts[flannel_iface]["ipv4"]["address"] }}'
Disable the taint manually by setting: k3s_master_taint = false
k3s_master_taint: "{{ true if groups['node'] | default([]) | length >= 1 else false }}"
these arguments are recommended for servers as well as agents:
extra_args: >-
--flannel-iface={{ flannel_iface }}
--node-ip={{ k3s_node_ip }}
change these to your liking, the only required are: --disable servicelb, --tls-san {{ apiserver_endpoint }}
extra_server_args: >-
{{ extra_args }}
{{ '--node-taint node-role.kubernetes.io/master=true:NoSchedule' if k3s_master_taint else '' }}
--tls-san {{ apiserver_endpoint }}
--disable servicelb
--disable traefik
extra_agent_args: >-
{{ extra_args }}
image tag for kube-vip
kube_vip_tag_version: "v0.5.11"
metallb type frr or native
metal_lb_type: "native"
metallb mode layer2 or bgp
metal_lb_mode: "layer2"
bgp options
metal_lb_bgp_my_asn: "64513"
metal_lb_bgp_peer_asn: "64512"
metal_lb_bgp_peer_address: "<IP_ADDRESS>"
image tag for metal lb
metal_lb_frr_tag_version: "v7.5.1"
metal_lb_speaker_tag_version: "v0.13.9"
metal_lb_controller_tag_version: "v0.13.9"
metallb ip range for load balancer
metal_lb_ip_range: "<IP_ADDRESS>-<IP_ADDRESS>"
Only enable if your nodes are proxmox LXC nodes, make sure to configure your proxmox nodes
in your hosts.ini file.
Please read https://gist.github.com/triangletodd/02f595cd4c0dc9aac5f7763ca2264185 before using this.
Most notably, your containers must be privileged, and must not have nesting set to true.
Please note this script disables most of the security of lxc containers, with the trade off being that lxc
containers are significantly more resource efficent compared to full VMs.
Mixing and matching VMs and lxc containers is not supported, ymmv if you want to do this.
I would only really recommend using this if you have particularly low powered proxmox nodes where the overhead of
VMs would use a significant portion of your available resources.
proxmox_lxc_configure: false
the user that you would use to ssh into the host, for example if you run ssh some-user@my-proxmox-host,
set this value to some-user
proxmox_lxc_ssh_user: root
the unique proxmox ids for all of the containers in the cluster, both worker and master nodes
proxmox_lxc_ct_ids:

200
201
202
203
204`

I can confirm this issue. It started 2-3 weeks ago.
I use this extra for the server args - and k3s or Tim's script simply doesn't care. It used to work before.
  --disable traefik
  --disable local-storage

Here my workaround:
    helm --namespace kube-system uninstall traefik || true
    helm --namespace kube-system uninstall traefik-crd || true

    kubectl delete storageclass local-path || true

I don't understand why these flags are no longer working.

Sorry, the flags still work.  Everything is working as expected.  I just created a new cluster and it works fine.  I would check the troubleshooting guide again and reset your cluster.
➜  k3s-ansible git:(master) ✗ kubectl get pods --all-namespaces
NAMESPACE        NAME                                      READY   STATUS    RESTARTS      AGE
default          nginx-6fb79bc456-c6jmz                    1/1     Running   0             12m
default          nginx-6fb79bc456-cmrr9                    1/1     Running   0             12m
default          nginx-6fb79bc456-d2kwv                    1/1     Running   0             12m
kube-system      coredns-7b5bbc6644-l4qxg                  1/1     Running   1 (16m ago)   17m
kube-system      kube-vip-ds-sq5ng                         1/1     Running   1 (16m ago)   17m
kube-system      kube-vip-ds-sqhjp                         1/1     Running   1 (16m ago)   17m
kube-system      kube-vip-ds-xc67x                         1/1     Running   1 (16m ago)   17m
kube-system      local-path-provisioner-687d6d7765-7pzxm   1/1     Running   1 (16m ago)   17m
kube-system      metrics-server-667586758d-7sbkf           1/1     Running   1 (16m ago)   17m
metallb-system   controller-c6c466d64-l4h6j                1/1     Running   0             17m
metallb-system   speaker-968vb                             1/1     Running   0             17m
metallb-system   speaker-dmlpw                             1/1     Running   0             17m
metallb-system   speaker-k5tpz                             1/1     Running   0             17m
metallb-system   speaker-tlbmj                             1/1     Running   0             15m
metallb-system   speaker-x9d2j                             1/1     Running   0             15m


[otp_ctrl] HW_CFG partition question

Hi Michael,
1). Current otp_ctrl_img_raw.hjson needs a mubi type as default value. Otherwise we will see assertion failures.
So I think we will need to add a hw_cfg section in raw_img.hjson as PR: https://github.com/lowRISC/opentitan/pull/12427
2). With this change, I do not think user can write from False -> True or True -> False in OTP_CTRL even though the HW cfg partition is not locked, because it is an 8 bit mubi type.
Writing them again will have a write-blank error.
Do you think this will be an issue? Will we ever have a usecase where we needs to update the access from False to True?
Thanks,
Cindy

Hi @cindychip!
Good catch - that is indeed an issue.
While we will likely burn MUBI values into OTP as either true or false during provisioning, we do expect the unprogrammed all-zero values to be interpreted as false.
There are two potential solutions to this that I can think of:

either we loosen up the assertions on MUBI signals that come from OTP
or we "rectify" all MUBI values stored in OTP so that they have the correct encoding when they leave the OTP controller.

@tjaychen WDYT? This is similar to the rectification problem we discussed in CSRs - but in this case we have no way to set the reset state to a legal value.

i feel like rectifying all of it might be a bit overkill, since we've so far required all downstream users to consume these MUBi's in a specific way.  Especially if the users are in a different clock domain, they have flops along the way, which are even more vulnerable. So I feel like correcting at the source isn't quite worth it.  If we were to map this to the csr case we discussed, I think it makes a bit more sense to ensure that the input program must be MUBI of some kind, and that if the value ever becomes non-mubi, we automatically trigger an alert instead of correcting (perhaps when locked).
In this case I feel like just loosening the assertion is probably more reasonable. We probably won't have many tests with a completely blank OTP right? For others it seems like @cindychip PR will do the trick?

Thanks @tjaychen for the feedback. So I guess that means - once we stream in the initial OTP image at raw stage with the mubi values, these values are set to either true or false, and cannot be changed. Is that expected?

o sorry. I misread this. I read it as "rma" and not "raw".
We can't do this for raw, since it would completely invalidate the definition of raw.
Do we have a lot of cases where we need to use a raw hjson? I was thinking for those we could loosen the assertion.

No worries! There have not been much use-cases - this is probably the only one so far.
Yeah, loosen the assertion should solve the issue :)

does my rationale on not correcting make sense? I'm not sure it's worth a detect and reconstruct there...since it doesn't decrease the downstream's burden of checking, and may create another vulnerable attack point.
So to me it makes more sense to regulate on program, and potentially detect as alert once locked.

I agree, I do not think it is necessary to correct it at the beginning.

Agreed, I would also prefer not to add rectifyers to the HW because it adds more complexity and thereby vulnerable points. The downstream logic should still work correctly when all-zero values are present due to the use of the strict MUBI checking functions.

sounds good. I am going to disable the assertion then! Feel free to re-open this issue if you think we need to discuss more on it.


Site changes for Re-OAB Launch

Related to #188 Combining our various take action pages into one to focus site vistors on what we'd like them to do.
Style of /action on ODB is good. Add in the map and "people need access to research / What can you do to help" boxes from /action on OAB.

Many done, much closable.


Time.epoch is not there anymore

Hello,
Trying out examples and got this:
In lib/discordcr/src/discordcr/mappings/channel.cr:16:5

 16 | JSON.mapping(
      ^
Warning: expanding macro

There was a problem expanding macro 'mapping'

Called macro defined in /usr/share/crystal/src/json/mapping.cr:232:3

 232 | macro mapping(**_properties_)

Which expanded to:

 > 1 |     ::JSON.mapping({type: {type: MessageType, converter: MessageTypeConverter}, content: String, id: Snowflake, channel_id: Snowflake, author: User, timestamp: {type: Time, converter: TimestampConverter}, tts: Bool, mention_everyone: Bool, mentions: Array(User), mention_roles: Array(Snowflake), attachments: Array(Attachment), embeds: Array(Embed), pinned: ::Union(Bool, ::Nil), reactions: ::Union(Array(Reaction), ::Nil), activity: ::Union(Activity, ::Nil)})
   2 |
Warning: Deprecated JSON.mapping. use JSON::Serializable instead (the legacy behaviour is also available in a shard at github:crystal-lang/json_mapping.cr)

A total of 1 warnings were found.
Showing last frame. Use --error-trace for full trace.

In lib/discordcr/src/discordcr/rest.cr:56:31

 56 | reset_time = Time.epoch(response.headers["X-RateLimit-Reset"].to_u64) # gotta prevent that Y2k38
                        ^----
Error: undefined method 'epoch' for Time.class

Renaming epoch to unix fixes it: https://crystal-lang.org/api/0.35.1/Time.html#unix(seconds:Int):Time-class-method


Is it available for Delphi XE6 and Delphi 7?

Hello Roman,
I'm usin Delphi 7 and XE6. Can I use your samples?
So, Could you elaborate any online tutorial or a course?
Please send me an email<EMAIL_ADDRESS>

Hello @tonnarruda. Delphi 7 isn't available. But it's supported in XE6. There is a folder that contains an samples "https://github.com/RomanYankovsky/DelphiSpec/tree/master/Demo". If you need to help send me a message.
Hugs


Origins I added often disappears for no reason

I often find my requests fail, because the origin I added disappears for no reason, and I have to add it again and refresh my page. It happens several days a time in microsoft edge.

I am also facing same issue. I am using self hosted instance.


Add pod anti-affinity to odh-model-controller manifests

Motivation
See https://github.com/opendatahub-io/odh-model-controller/pull/51
PR checklist
Checklist items below are applicable for development targeted to both fast and stable branches/tags

[x] Unit tests pass locally
[x] FVT tests pass locally
[ ] If the PR adds a new container image or updates the tag of an existing image (not build within cpaas), is the corresponding change made in live-builder and cpaas-midstream to add/update the image tag in the operator CSV? Link the PRs if applicable

Checklist items below are applicable for development targeted to both fast and stable branches/tags

[ ] Tested modelmesh serving deployment with odh-manifests and ran odh-manifests-e2e tests locally

@israel-hdez this looks good to me. Could you please create another PR for the release branch? stable related folder must be synced with release branch too.

Could you please create another PR for the release branch? stable related folder must be synced with release branch too.

This PR is covering both folders :-)

I know but the stable folder will be used for deploying stable images in the stable branch as well so it should be synced with stable branch as well

I know but the stable folder will be used for deploying stable images in the stable branch as well so it should be synced with stable branch as well

Hmmm... I think I understand.
I see two branches: release-v0.11.0-alpha and release-v0.11.0-rc0. The alpha one is the correct one, right?

Correct. I will remove the other.

Could you please create another PR for the release branch? stable related folder must be synced with release branch too.

@Jooho Here is the PR: #120

/approve cancel

You should change openshift-ci build-root part : https://github.com/openshift/release/pull/40548/files#r1239020973

/retest


Device communication failed

Hello I have problem in connecting the last version of website with my ledger, I have only 1 browser that show me a old version of myhbarwallet and work (maybe old cache) all the other browser and different system not work for me, attached the different version (the old work, the last not work) What I need to do?

I have similar problem

I have similar problem

my bad, I should open ledger HBAR first before clicking on continue.


remove unnecessary broadcasts from functions.l2_normalization

Same as https://github.com/chainer/chainer/pull/6680

Jenkins, test this please.

Jenkins CI test (for commit 205dbf9c42136fd47147147e31a3d6743a95de7f, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins CI test (for commit 205dbf9c42136fd47147147e31a3d6743a95de7f, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)


Added Location Parameter to Log Visit Lambda

Added a parameter to log_visit.py to take in a location body parameter. This code also pushes it into the DynamoDB table.

In testing my code, I did run into an issue where I couldn't test the lambda from the console with { "username": "jmdanie", "location": "Watt" }. To test the code and make sure it pushed to the DynamoDB, I edited lines 134 and 135 in log_visit.py to be:
username = request["username"]
location = request["location"]

In testing, I found that the username and location were being pushed to my DynamoDB.
dynamo_output.csv

In testing my code, I did run into an issue where I couldn't test the lambda from the console with { "username": "jmdanie", "location": "Watt" }.

The lambda is looking for a json object as the value for the body key. You'll need to escape the quotes inside the json object.
{
  "body": "{\"username\":\"oap\",\"location\":\"watt\"}"
}

Try something like that & your tests in the lambda console should succeed.

In testing my code, I did run into an issue where I couldn't test the lambda from the console with { "username": "jmdanie", "location": "Watt" }.

The lambda is looking for a json object as the value for the body key. You'll need to escape the quotes inside the json object.
{
  "body": "{\"username\":\"oap\",\"location\":\"watt\"}"
}

Try something like that & your tests in the lambda console should succeed.

Got it! Tested it with the following code snippet:
{
  "body": "{\"username\":\"jmdanie\",\"location\":\"watt\"}"
}

So I have 2 test events. One tests with the locaiton and one does not. They produce the following DynamoDB output: results (1).csv
These were my test events:
{
  "body": "{\"username\":\"jmdanie\",\"location\":\"watt\"}"
}

{
  "body": "{\"username\":\"jmdanie\"}"
}


Chunked array docs

Builds upon #7911

[x] Documentation for #7019
[ ] Tests added
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

I tried to include part of the internal API but that messed up how the subheadings link bar on the left is built

Also I've obviously messed up a bunch of link formatting, will fix those.

Okay I've fixed those things, this is ready for review

Thanks for the reviews @dcherian !


Data on farmer's markets accepting SNAP available through app

See https://hackpad.com/Project-Snapfresh.org-jNHpAeYS5rQ comments under Farmers Market heading. We have data available and scraped. But need to make scrape repeatable and memory efficient, then integrate into APP's data.

Migrated to primary repo. https://github.com/SnapFresh/SnapFresh/issues/54


Add support for AKS Node Pool name

default_node_pool.0.name must start with a lowercase letter, have max length of 12, and only have characters a-z0-9

Added implementation in V.0.3.1

Closing as addressed in #38


[FEATURE]Horovod support for training transformer (PART 2)

Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

add horovodrun example in machine_translation/README.md
transformer base/large result (test and valid bleu)
ShardedIterator (to split sampler) and testcase
add test case to test situation that fail downloading in test_util_misc.py

For the diff check failure, it might be caused by the fact that the exception is not triggered:
https://github.com/dmlc/gluon-nlp/blob/32e87d4d4aa20a6eb658ee90d765ccffbd160571/src/gluonnlp/utils/misc.py#L562-L568
Thus, we may try to add a test-case which downloads an non-existing file and use pytest.assertRaises.

I find that the codecov is not very stable, especially the diff hit. @szha @leezu Would you know how could we improve it?

assuming no race issue in result upload, this can be a result of non-determinism in tests, and the code path in the same test can vary.
if that's the case, we can mock the randomness to deterministically test each path. or if we still require the randomness, we can increase the trial number


Allow custom analysis implementations

In an analysis session, the end-user must be able to implement its own analysis.

Done, the end-user can use a Jupiter notebook to create an analysis


[3653] Publish course enrichments validations

If a course does not have an enrichment we now present back errors as
if the course did have an enrichment
This gives more meaningful errors to the user
Rather than the enrichment is missing

Context
Changes proposed in this pull request
Guidance to review
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Missing/broken error summaries when trying to Publish a course in rollover


💡[FEATURE]

Description
I will add suitable hover effects for the login and signup button
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I have read the Contributing Guidelines
[X] I have read the Code Of Conduct
[X] The changes don't break the code

duplicate


[android] Player > Long press on Song > Menu has no icons

I will look at it again today, but I had a hard time with finding a right way to do this as I said before. This happens in other sections of My Music as well, on long press. Context menu as stated do not support icons. https://developer.android.com/reference/android/view/ContextMenu.html

Done with https://github.com/frostwire/frostwire/commit/46f2ab824f250cfd4ee3eda9f56d224ad5989816
@marcelinkaaa I need you to take care of the icons, see https://github.com/frostwire/frostwire/commit/46f2ab824f250cfd4ee3eda9f56d224ad5989816#diff-06a97ed34f25645106d0de9a97651e43R237


Server2022 update

Updated Base OS image to Server 2022 for the Azure VM and the Mgmt VM.

Updated Sandbox to use Server 2022 as base OS.


Challenges: allow keeping track of piece identity

Would allow us to implement things like

Chess, but Edward switches sides. Your opponent's Edward is indestructible and is given way to promotion. The game continues on otherwise.

Chess, but the enemy queen is an evil witch.  While the enemy queen is still alive, only pawns and bishops can move. Defeating her frees the other pieces from their immobility. // (unclear if a newly promoted queen should have the witch power, but can playtest both)

Can just, like, number pieces from 0 and store indices in a map


Right or Left flow depending on Locale

Description
The translations all have a lable called "interface_direction", its used to load a value of either "ltr" (left to right) or "rtl" (right to left).
The issue
The Dir value is set in the body tag wich will move the navigation icons to the other side, but the language selection still loads on the right side.
The solution
The language selector is loaded as an ionic object and loads with a value called side. Setting it to either Right or Left will swap the position of this button.
Design decisions
Even though navigation buttons move to the other side the icon still loads on the right side of the text. Maybe it shouldn't? Ping design team?

Someone told us that because we are centralizing the content we dont really need to account for rtl and ltr for html tags.


RUM-1308: Add more HTTP methods to RUM

What does this PR do?
Fixes #1816.
This PR adds support of CONNECT, TRACE, OPTIONS to the RumMonitor#startResource call.
Both RUM resources view and traces/spans created by RUM2APM are working fine for these methods.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1826 (2284a01) into develop (7d96d64) will decrease coverage by 0.16%.
Report is 4 commits behind head on develop.
The diff coverage is 81.25%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1826      +/-   ##
===========================================
- Coverage    83.57%   83.41%   -0.16%
===========================================
  Files          467      467
  Lines        16462    16442      -20
  Branches      2480     2475       -5
===========================================
- Hits         13757    13714      -43
- Misses        2033     2042       +9
- Partials       672      686      +14

Files
Coverage Δ

...otlin/com/datadog/android/rum/RumResourceMethod.kt
100.00% <100.00%> (ø)

...g/android/rum/internal/domain/scope/RumEventExt.kt
93.47% <100.00%> (-0.56%)
:arrow_down:

...n/com/datadog/android/okhttp/DatadogInterceptor.kt
73.47% <100.00%> (+0.55%)
:arrow_up:

.../android/rum/internal/monitor/DatadogRumMonitor.kt
84.25% <0.00%> (-0.18%)
:arrow_down:

... and 29 files with indirect coverage changes


Firefox Floating Dropdown Items Not Accessible

Bug Report
Steps

Open up Firefox - 60.6.0esr (64-bit)
Go to https://react.semantic-ui.com/modules/dropdown/#types-floating
Click on the arrow of the floating button example
Hover over any elements on floated dropdown

My coworker pointer out that none of the elements are clickable on the dropdown on Firefox. I apologize I don't have screen shots, but essentially the cursor doesn't change to the pointer like it should, and you cannot interact with those elements including click and hover.
Expected Result
Be able to interact with the dropdown items
Actual Result
Cannot interact with any of the elements in the dropdown. Clicking only closes the dropdown list without actually clicking on an item.
Version
0.86.0
Testcase
https://react.semantic-ui.com/modules/dropdown/#types-floating

PR is ready, it's not issue with component, so you can just pick up these changes.
Thanks for the report 👍


Predicting next values using LSTM

Hello!
I have a large time-series (each point is vector of length 30), and I need to predict the following time-series point using the previous ones.
So I have some amount of independent training sets (each represents a time-series of length 1mln+).
And I know that there is a long-term dependence of the points.
I'm trying to figure out how to use LSTM => Dense in this case.
First of all, I don't understand the issue of the input shape. I found that It should be (timesteps, 30) in my case. Does it mean, that if assume that the point Xi depends on the previous ten points, my i-th training example should be of shape (10,30) and include concatenateed X_i-10...X_i-1? It seems like a lot of replicated data. It seems like this "timesteps" should mean the length of sequence, while in my case I have a sequence of 1.2mln...
Also this is important because I'm going to use this model on the absolutely new data, feeding test examples one by one, so for the first points there will be no previous points.
I have also found the idea of the stateful RNN. Should I use it in this case? And if so, what about the shape again.
Thanks a lot!

Have you checked the char-lstm generation example? It would help understanding how to preprocess the sequence. Adjusting maxlen and step in the example would let you get the data prepared - probably maxlen=10 and step for something shorter than 10.

@keunwoochoi I will check it out, also I have already studied some examples. But most of them (and yours too) cover text prediction, while I am interested in prediction of the next vector of 30  floats.
I'm  now trying to use stateful option and batches of size 1, and not quite sure how often should I reset the state. The model performance is very poor now.
So it's more question on the concept on solving my problem...

Yes, but I assume the same architecture would work whether it's one-hot vector or vectors with continuous values (I haven't used it on RNN layers but other types of layer work for both of them).

Hi, related question here. The prediction will always be t+1 or is there any way to get the next 3 values t+1,t+2,t+3, for example?


Skip unneeded calculation in naive diploid Viterbi

Partially address #65

This only shaved about 20 sec off on CI...

No need to do this. Deleting branch.


⚠ Rumah123 has degraded performance

In d6fd145, Rumah123 (https://www.rumah123.com) experienced degraded performance:

HTTP code: 200
Response time: 8917 ms

Resolved: Rumah123 performance has improved in 029792c.


Moc labs review patch 13

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by viggithub on behalf of MOC Labs Review


Moving to doctest examples

Most if it is rather straightforward. Still need to change some existing code blocks. But I also need to change the way the python API is embedded into the doc to include the doctest which is in the python code. See change
.. autoclass:: skmatter.feature_selection.CUR
   :members:
   :undoc-members:
   :inherited-members:
   :show-inheritance:

@rosecers Are you okay with this? Check out https://scikit-matter--201.org.readthedocs.build/en/201/selection.html#cur
Then I continue doing it for the other classes.

:books: Documentation preview :books:: https://scikit-matter--201.org.readthedocs.build/en/201/

Works for me! Will review when it's ready.

Its ready


Azure connection error on macOS using FreeTDS (port issue)

I was having connection problems to Azure.
Using the ODBC driver I was getting this error:
Connection:
  database: sm_analysis
  schema: dbt_kim
  UID: hostmaster
  windows_login: False
libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: collate_byname<char>::collate_byname failed to construct for C/en_US.UTF-8/C/C/C/C
[1]    5062 abort      dbt debug
/Users/Kim/.pyenv/versions/3.6.5/lib/python3.6/multiprocessing/semaphore_tracker.py:143: UserWarning: semaphore_tracker: There appear to be 1 leaked semaphores to clean up at shutdown
  len(cache))

Then I tried using FreeTDS, but was getting this error:
dbt was unable to connect to the specified database.
The database returned the following error:

  >Database Error
  ('08S01', '[08S01] [FreeTDS][SQL Server]Unable to connect: Adaptive Server is unavailable or does not exist (20009) (SQLDriverConnect)')

Check your database credentials and try again. For more information, visit:
https://docs.getdbt.com/docs/configure-your-profile

I finally narrowed down the problem to the fact that the port is not specified in the connection string.
After making these changes I was able to connect:
diff --git a/dbt/adapters/sqlserver/connections.py b/dbt/adapters/sqlserver/connections.py
index e336dcc..5a9568c 100644
--- a/dbt/adapters/sqlserver/connections.py
+++ b/dbt/adapters/sqlserver/connections.py
@@ -19,6 +19,7 @@ class SQLServerCredentials(Credentials):
     host: str
     database: str
     schema: str
+    port: Optional[int] = 1433
     UID: Optional[str] = None
     PWD: Optional[str] = None
     windows_login: Optional[bool] = False
@@ -87,6 +88,7 @@ class SQLServerConnectionManager(SQLConnectionManager):
             con_str = []
             con_str.append(f"DRIVER={{{credentials.driver}}}")
             con_str.append(f"SERVER={credentials.host}")
+            con_str.append(f"PORT={credentials.port}")
             con_str.append(f"Database={credentials.database}")

             if not getattr(credentials, 'windows_login', False):

Thanks!
I'll add that asap :-)

Fixed in branch master, commit 1cf0f061e06f1f17ba22b46c26675ff32dcd00b8 . Thanks for reporting!