Can not build for front-proxy of examples

Can't build front-proxy example with docker-compose.
It has been failed when pulling python images used in shared resources (flask and tracing).
And I have solved to change the image from 3.10-slim-bullseye to 3.11.0a7-bullseye
I think it could be a docker registry problem rather than the example.
I'll register the issue just in case.
And the detailed error log is below.
=> ERROR [internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye

[internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye:

failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorizatio
ERROR: Service 'tracing' failed to build : Build failed

It works for me, from the log it says it wants to pull docker.io/library/flask_service:python-3.10-slim-bullseye, which we all know it needs to build.

this seems to be the same issue reported in #20897
im struggling to understand the circumstances under which this is failing - wfm locally, and ci is testing this without issue i think

I think it could be a docker registry problem rather than the example.

im inclined to think the same, but the error messages are confusing

And I have solved to change the image from 3.10-slim-bullseye to 3.11.0a7-bullseye

im trying to understand how that makes a difference, but we need 3.10 anyway

Are you behind a corporate proxy? @kakaru1331 You may want to configure your docker to use proxy.

@bryanwux Yes I am. I think you're right.
When I see other people make it without trouble.
Thank you.

I am running into the same issue I believe,
everything else , i can pull from dockerhub except for envoyproxy:tracing
trying to follow the example mentioned here
❯ docker pull envoyproxy:tracing
Error response from daemon: pull access denied for envoyproxy, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
❯ docker pull flask_service:python-3.10-slim-bullseye
Error response from daemon: pull access denied for flask_service, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

but without making any changes to docker config locally , I can easily pull these other images
❯ docker pull envoyproxy/envoy-debug:v1.21-latest
v1.21-latest: Pulling from envoyproxy/envoy-debug
88736512a147: Pull complete
31b4a15ab3d8: Pull complete
140d66700333: Pull complete
7ffb1f2904d0: Pull complete
2ea894474077: Pull complete
4f4fb700ef54: Pull complete
2f57144d871a: Pull complete
4eafd179850f: Pull complete
Digest: sha256:2a4ef9f4759541ab6b28c030bac5f95568cc031078e91f5bcca41e279aee5a1a
Status: Downloaded newer image for envoyproxy/envoy-debug:v1.21-latest
docker.io/envoyproxy/envoy-debug:v1.21-latest

as well as
❯ docker pull envoyproxy/envoy-debug-dev
Using default tag: latest
latest: Pulling from envoyproxy/envoy-debug-dev
88736512a147: Already exists
a44bc9fc528e: Already exists
45cd4c5b4f89: Already exists
b544f25b87e4: Pull complete
e626fa42a7d5: Pull complete
e39c66366821: Pull complete
b2bb448924cf: Pull complete
74c46a1431a2: Pull complete
Digest: sha256:feacbbc32d02f33e80a0ba62be7645daa5f012cb475102d9494e38a3c95a6ca8
Status: Downloaded newer image for envoyproxy/envoy-debug-dev:latest
docker.io/envoyproxy/envoy-debug-dev:latest

This issue still exists. May I ask is there a plan to fix it?

Oh , sorry , i meant to bring up that docker pull itself was failing but i see what you mean.
docker-compose build --pull is not the same as docker pull, i agree and please ignore that last comment.
So, trying verbatim instructions from the front-proxy tutorial and no corporate vpn or firewall or proxy in place
❯ docker-compose images
Container           Repository          Tag                 Image Id            Size
❯ docker-compose build --pull
[+] Building 2.6s (18/21)
 => [flask_service:python-3.10-slim-bullseye internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 32B                                                                                0.0s
 => [envoyproxy:tracing internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 32B                                                                                0.0s
 => [front-proxy_front-envoy internal] load build definition from Dockerfile-frontenvoy                                                                                0.0s
 => => transferring dockerfile: 43B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [envoyproxy:tracing internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [front-proxy_front-envoy internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load metadata for docker.io/library/python:3.10-slim-bullseye                                                                                0.5s
 => [front-proxy_front-envoy internal] load metadata for docker.io/envoyproxy/envoy-dev:latest                                                                                1.0s
 => ERROR [envoyproxy:tracing internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye                                                                                2.3s
 => [flask_service:python-3.10-slim-bullseye internal] load build context                                                                                0.0s
 => => transferring context: 38B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye 1/4] FROM docker.io/library/python:3.10-slim-bullseye@sha256:ad719a882ac0594bdc92abccff22e5b6713bbf9893320264fd9e8affd8a6f470                                                               0.0s
 => CACHED [flask_service:python-3.10-slim-bullseye 2/4] ADD requirements.txt /tmp/flask-requirements.txt                                                                                0.0s
 => CACHED [flask_service:python-3.10-slim-bullseye 3/4] RUN pip3 install -r /tmp/flask-requirements.txt                                                                                0.0s
 => CACHED [flask_service:python-3.10-slim-bullseye 4/4] RUN mkdir /code                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye] exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:5d1720ed6c341c07d756daf3cc11458d8a7c9595bd7d50ff387523623cfa81ed                                                                                0.0s
 => => naming to docker.io/library/flask_service:python-3.10-slim-bullseye                                                                                0.0s
 => [auth] library/flask_service:pull token for registry-1.docker.io                                                                                0.0s
 => [front-proxy_front-envoy internal] load build context                                                                                0.0s
 => => transferring context: 7.53kB                                                                                0.0s
 => CANCELED [front-proxy_front-envoy 1/4] FROM docker.io/envoyproxy/envoy-dev:latest@sha256:d1a3abbdd6b2d22e279d0e1e567163b00a6b9920dd12bd63831dfaf914369fa3                                                                            1.2s
 => => resolve docker.io/envoyproxy/envoy-dev:latest@sha256:d1a3abbdd6b2d22e279d0e1e567163b00a6b9920dd12bd63831dfaf914369fa3                                                                                0.0s
 => => sha256:d1a3abbdd6b2d22e279d0e1e567163b00a6b9920dd12bd63831dfaf914369fa3 743B / 743B                                                                                0.0s
 => => sha256:8a3af097d0aba441bdc1ac127f2131b17e73f149015e95b0b9571e418dad7949 3.24kB / 3.24kB                                                                                0.0s
 => => sha256:5b00803bf604d4ff96e49a9429626ab8b1bcb408b26849fc2fb909b5326d9c03 3.49MB / 3.49MB                                                                                0.9s
 => => sha256:911bdf7868835753f088d4544541951228a9f07cb69848f261fa3b13d8d7f8a4 120B / 120B                                                                                0.2s
 => => sha256:0e506b9cf69eef0b2d16a08a3db1851ffd98db3bf5d95c13846f1adc1a721683 1.99kB / 1.99kB                                                                                0.0s
 => => sha256:88736512a147458c580cd28c969698561f236abba2ef04dbf0d7940cb3d7375e 13.63MB / 26.71MB                                                                                1.3s
 => => sha256:31bd94bf0a15a4ac1fa7440287028fef34c64bccd179772f2bc3dd2bef80dbcb 8.39MB / 21.34MB                                                                                1.3s
 => => sha256:e45b20545c21afbdf8d5ad31336db1b22e390331cb2b180897d0cbe0d4bf1eb5 4.39kB / 4.39kB                                                                                1.2s
 => => sha256:a3646bb5138b918d6547eb3e6a2e30746bed5a6524df21d3b215d453486b0a95 0B / 797B                                                                                1.3s
------
 > [envoyproxy:tracing internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye:
------
failed to solve: failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

It didnt require any kind of authorization before
❯ docker login
Authenticating with existing credentials...
Login Succeeded
❯ vi $HOME/.docker/config.json
{
        "auths": {
                "https://index.docker.io/v1/": {}
        },
        "credsStore": "osxkeychain"
}

trying again with --verbose flag
❯ docker images
REPOSITORY                TAG                         IMAGE ID       CREATED          SIZE
flask_service             python-3.10-slim-bullseye   5d1720ed6c34   13 minutes ago   137MB

❯ docker-compose --verbose build --pull
DEBU[0000] serving grpc connection
DEBU[0000] stopping session                              span="load buildkit capabilities"
DEBU[0000] serving grpc connection
DEBU[0000] serving grpc connection
DEBU[0000] serving grpc connection
[+] Building 0.7s (12/15)
[+] Building 2.5s (16/21)
 => [flask_service:python-3.10-slim-bullseye internal] load build definition from Dockerfile                                                                                0.0s
[+] Building 2.6s (18/21)
 => [flask_service:python-3.10-slim-bullseye internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 32B                                                                                0.0s
 => [envoyproxy:tracing internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 32B                                                                                0.0s
 => [front-proxy_front-envoy internal] load build definition from Dockerfile-frontenvoy                                                                                0.0s
 => => transferring dockerfile: 43B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [envoyproxy:tracing internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [front-proxy_front-envoy internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load metadata for docker.io/library/python:3.10-slim-bullseye                                                                                0.5s
 => [front-proxy_front-envoy internal] load metadata for docker.io/envoyproxy/envoy-dev:latest                                                                                1.1s
 => ERROR [envoyproxy:tracing internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye                                                                                2.2s
 => [flask_service:python-3.10-slim-bullseye internal] load build context                                                                                0.0s
 => => transferring context: 38B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye 1/4] FROM docker.io/library/python:3.10-slim-bullseye@sha256:ad719a882ac0594bdc92abccff22e5b6713bbf9893320264fd9e8affd8a6f470                                                               0.0s
 => CACHED [flask_service:python-3.10-slim-bullseye 2/4] ADD requirements.txt /tmp/flask-requirements.txt                                                                                0.0s
 => CACHED [flask_service:python-3.10-slim-bullseye 3/4] RUN pip3 install -r /tmp/flask-requirements.txt                                                                                0.0s
 => CACHED [flask_service:python-3.10-slim-bullseye 4/4] RUN mkdir /code                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye] exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:5d1720ed6c341c07d756daf3cc11458d8a7c9595bd7d50ff387523623cfa81ed                                                                                0.0s
 => => naming to docker.io/library/flask_service:python-3.10-slim-bullseye                                                                                0.0s
 => [auth] library/flask_service:pull token for registry-1.docker.io                                                                                0.0s
 => CANCELED [front-proxy_front-envoy 1/4] FROM docker.io/envoyproxy/envoy-dev:latest@sha256:d1a3abbdd6b2d22e279d0e1e567163b00a6b9920dd12bd63831dfaf914369fa3                                                                            1.2s
 => => resolve docker.io/envoyproxy/envoy-dev:latest@sha256:d1a3abbdd6b2d22e279d0e1e567163b00a6b9920dd12bd63831dfaf914369fa3                                                                                0.0s
 => => sha256:88736512a147458c580cd28c969698561f236abba2ef04dbf0d7940cb3d7375e 19.92MB / 26.71MB                                                                                1.3s
 => => sha256:5b00803bf604d4ff96e49a9429626ab8b1bcb408b26849fc2fb909b5326d9c03 3.49MB / 3.49MB                                                                                0.7s
 => => sha256:911bdf7868835753f088d4544541951228a9f07cb69848f261fa3b13d8d7f8a4 120B / 120B                                                                                0.5s
 => => sha256:d1a3abbdd6b2d22e279d0e1e567163b00a6b9920dd12bd63831dfaf914369fa3 743B / 743B                                                                                0.0s
 => => sha256:0e506b9cf69eef0b2d16a08a3db1851ffd98db3bf5d95c13846f1adc1a721683 1.99kB / 1.99kB                                                                                0.0s
 => => sha256:8a3af097d0aba441bdc1ac127f2131b17e73f149015e95b0b9571e418dad7949 3.24kB / 3.24kB                                                                                0.0s
 => => sha256:31bd94bf0a15a4ac1fa7440287028fef34c64bccd179772f2bc3dd2bef80dbcb 5.24MB / 21.34MB                                                                                1.3s
 => => sha256:e45b20545c21afbdf8d5ad31336db1b22e390331cb2b180897d0cbe0d4bf1eb5 4.39kB / 4.39kB                                                                                0.9s
 => => sha256:a3646bb5138b918d6547eb3e6a2e30746bed5a6524df21d3b215d453486b0a95 797B / 797B                                                                                1.2s
 => [front-proxy_front-envoy internal] load build context                                                                                0.0s
 => => transferring context: 38B                                                                                0.0s
------
 > [envoyproxy:tracing internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye:
------
failed to solve: failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

Tried running a different sandbox (mysql) and everything works properly, no errors.
❯ cd ..
❯ ls
BUILD                   cors                    ext_authz               jaeger-native-tracing   lua                     skywalking-tracing      verify-common.sh        win32-front-proxy
DEVELOPER.md            csrf                    fault-injection         jaeger-tracing          mysql                   tls                     vrp-litmus              zipkin-tracing
_extra_certs            double-proxy            front-proxy             load-reporting-service  postgres                tls-inspector           vrp-local               zstd
brotli                  dynamic-config-cp       grpc-bridge             local_ratelimit         redis                   tls-sni                 wasm-cc
cache                   dynamic-config-fs       gzip                    locality-load-balancing shared                  udp                     websocket
❯ cd mysql
❯ docker-compose build --pull
[+] Building 15.9s (14/14) FINISHED
 => [mysql_proxy internal] load build definition from Dockerfile-proxy                                                                                0.0s
 => => transferring dockerfile: 203B                                                                                0.0s
 => [mysql_mysql internal] load build definition from Dockerfile-mysql                                                                                0.0s
 => => transferring dockerfile: 58B                                                                                0.0s
 => [mysql_proxy internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [mysql_mysql internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [mysql_proxy internal] load metadata for docker.io/envoyproxy/envoy-contrib-dev:latest                                                                                2.8s
 => [mysql_mysql internal] load metadata for docker.io/library/mysql:5.7                                                                                2.7s
 => [auth] envoyproxy/envoy-contrib-dev:pull token for registry-1.docker.io                                                                                0.0s
 => [auth] library/mysql:pull token for registry-1.docker.io                                                                                0.0s
 => [mysql_mysql 1/1] FROM docker.io/library/mysql:5.7@sha256:e767595ba3408fbb2dda493be3594b9a148178df58325fafe8b0363662935624                                                                                13.0s
 => => resolve docker.io/library/mysql:5.7@sha256:e767595ba3408fbb2dda493be3594b9a148178df58325fafe8b0363662935624                                                                                0.0s
 => => sha256:8aa3ac85066b123f51dc3116666eaa90f904194f8ccbbb38edef3f75382bde5a 4.18MB / 4.18MB                                                                                0.7s
 => => sha256:4be315f6562fccf08fd6c749557e31e45ab6d987370e20e2c4933ddb04ddd5ff 27.14MB / 27.14MB                                                                                1.8s
 => => sha256:8aa4b5ffb001f0092b491bdd8a48a83cb2ab2b721646db139d4cda64dea93600 7.08kB / 7.08kB                                                                                0.0s
 => => sha256:96e2eb237a1b01f5f7102bf13d4d92bc60937a8f75fcfd4bea0d6f37f29e36ad 1.73kB / 1.73kB                                                                                0.3s
 => => sha256:9519054fe27aa84758d6303f66a6059c47f4bfbfc9d2ce32e4f6fed63cf93a8c 2.62kB / 2.62kB                                                                                0.0s
 => => sha256:e767595ba3408fbb2dda493be3594b9a148178df58325fafe8b0363662935624 320B / 320B                                                                                0.0s
 => => sha256:ac7e524f6c89f7c75ef7a9ad752e344967db67ebf0a0a1248a2e40c120290bf8 1.39MB / 1.39MB                                                                                0.9s
 => => sha256:f6a88631064fc8f7cd0d269d71800a9fe2768e1bf3c32ffd10489e620ab52b32 149B / 149B                                                                                0.9s
 => => sha256:15bb3ec3ff50c5b6a064dd106f3ece814edc88c72e3d9672434e1c014784585e 14.06MB / 14.06MB                                                                                3.1s
 => => sha256:ae65dc337dcb723acc14fda695c58c87adbf9e0c85b631185c6158f9c447a0df 2.55kB / 2.55kB                                                                                1.1s
 => => sha256:a4c4c43adf52f5de087a3de9cbbe44961b77501325a167b6e276b1beb16e0f1d 254B / 254B                                                                                1.2s
 => => sha256:c6cab33e8f91f2158824d485f04855550f65a994841cdea4496d0a7faf0d299f 115.68MB / 115.68MB                                                                                8.3s
 => => extracting sha256:4be315f6562fccf08fd6c749557e31e45ab6d987370e20e2c4933ddb04ddd5ff                                                                                1.9s
 => => sha256:2e1c4f2c43f66ed8d87c2d72149baa14bd693f2decdd241b1df1ae5bb1d84632 5.14kB / 5.14kB                                                                                2.0s
 => => sha256:2e5ee322af488c94e1fa00b5d075340197f93a00fdbae2e3ac5b9ff68fe8d502 118B / 118B                                                                                2.1s
 => => extracting sha256:96e2eb237a1b01f5f7102bf13d4d92bc60937a8f75fcfd4bea0d6f37f29e36ad                                                                                0.1s
 => => extracting sha256:8aa3ac85066b123f51dc3116666eaa90f904194f8ccbbb38edef3f75382bde5a                                                                                0.3s
 => => extracting sha256:ac7e524f6c89f7c75ef7a9ad752e344967db67ebf0a0a1248a2e40c120290bf8                                                                                0.1s
 => => extracting sha256:f6a88631064fc8f7cd0d269d71800a9fe2768e1bf3c32ffd10489e620ab52b32                                                                                0.0s
 => => extracting sha256:15bb3ec3ff50c5b6a064dd106f3ece814edc88c72e3d9672434e1c014784585e                                                                                1.5s
 => => extracting sha256:ae65dc337dcb723acc14fda695c58c87adbf9e0c85b631185c6158f9c447a0df                                                                                0.0s
 => => extracting sha256:a4c4c43adf52f5de087a3de9cbbe44961b77501325a167b6e276b1beb16e0f1d                                                                                0.0s
 => => extracting sha256:c6cab33e8f91f2158824d485f04855550f65a994841cdea4496d0a7faf0d299f                                                                                4.3s
 => => extracting sha256:2e1c4f2c43f66ed8d87c2d72149baa14bd693f2decdd241b1df1ae5bb1d84632                                                                                0.0s
 => => extracting sha256:2e5ee322af488c94e1fa00b5d075340197f93a00fdbae2e3ac5b9ff68fe8d502                                                                                0.0s
 => [mysql_proxy internal] load build context                                                                                0.0s
 => => transferring context: 1.02kB                                                                                0.0s
 => [mysql_proxy 1/3] FROM docker.io/envoyproxy/envoy-contrib-dev:latest@sha256:14e560cd6b9497bfb44e64bce16ccf3b04de7cdf5c5d15995703606ec166fd68                                                                                9.2s
 => => resolve docker.io/envoyproxy/envoy-contrib-dev:latest@sha256:14e560cd6b9497bfb44e64bce16ccf3b04de7cdf5c5d15995703606ec166fd68                                                                                0.0s
 => => sha256:0a9de54728b4c1054ce3c47ce8bcb599202fdd5b7b9ba1cc7e5ab4ba19158972 1.99kB / 1.99kB                                                                                0.0s
 => => sha256:14e560cd6b9497bfb44e64bce16ccf3b04de7cdf5c5d15995703606ec166fd68 743B / 743B                                                                                0.0s
 => => sha256:a9af2600710859b152c2f49932e34a7a4442b25b7395ec62765d1d68eac4f1a2 3.24kB / 3.24kB                                                                                0.0s
 => => sha256:88736512a147458c580cd28c969698561f236abba2ef04dbf0d7940cb3d7375e 26.71MB / 26.71MB                                                                                4.7s
 => => sha256:5b00803bf604d4ff96e49a9429626ab8b1bcb408b26849fc2fb909b5326d9c03 3.49MB / 3.49MB                                                                                3.8s
 => => sha256:911bdf7868835753f088d4544541951228a9f07cb69848f261fa3b13d8d7f8a4 120B / 120B                                                                                3.9s
 => => sha256:832cbcbab2d023839528405a0b805f8d12bdba01a4466f3940675c7e7e37febf 27.01MB / 27.01MB                                                                                6.1s
 => => sha256:943fc4d9d7e70b68038069d096cfb3c60dac3ba5533b8dcb36dbbd1326f13c02 4.39kB / 4.39kB                                                                                4.9s
 => => extracting sha256:88736512a147458c580cd28c969698561f236abba2ef04dbf0d7940cb3d7375e                                                                                2.2s
 => => sha256:be279a5d3358755d10d45cc18950c8d3d432da61695b51b490d4adc6a9d9d742 799B / 799B                                                                                5.2s
 => => sha256:de37dc9fa1fab445998d6f16dcb8c1ebe1f70cb3e28af76a3c9eeb39b41d2a72 490B / 490B                                                                                5.4s
 => => sha256:14429aa6c0beba742132d274f1ccbd815d4b3602f9bfd2ef6c48a148e0c3a338 1.46kB / 1.46kB                                                                                5.7s
 => => extracting sha256:5b00803bf604d4ff96e49a9429626ab8b1bcb408b26849fc2fb909b5326d9c03                                                                                0.3s
 => => extracting sha256:911bdf7868835753f088d4544541951228a9f07cb69848f261fa3b13d8d7f8a4                                                                                0.0s
 => => extracting sha256:832cbcbab2d023839528405a0b805f8d12bdba01a4466f3940675c7e7e37febf                                                                                1.2s
 => => extracting sha256:943fc4d9d7e70b68038069d096cfb3c60dac3ba5533b8dcb36dbbd1326f13c02                                                                                0.0s
 => => extracting sha256:be279a5d3358755d10d45cc18950c8d3d432da61695b51b490d4adc6a9d9d742                                                                                0.0s
 => => extracting sha256:de37dc9fa1fab445998d6f16dcb8c1ebe1f70cb3e28af76a3c9eeb39b41d2a72                                                                                0.0s
 => => extracting sha256:14429aa6c0beba742132d274f1ccbd815d4b3602f9bfd2ef6c48a148e0c3a338                                                                                0.0s
 => [mysql_proxy 2/3] COPY ./envoy.yaml /etc/envoy.yaml                                                                                0.6s
 => [mysql_proxy 3/3] RUN chmod go+r /etc/envoy.yaml                                                                                0.3s
 => [mysql_mysql] exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:29345e830982c0c7eba2edd75bf683782db389ee5e80b9a4702bf4c8de07db5a                                                                                0.0s
 => => naming to docker.io/library/mysql_proxy                                                                                0.0s
 => => writing image sha256:3c79753649e111d827af25a1f91251a28b2c1071ab2a9905c3323bb4e636dc02                                                                                0.0s
 => => naming to docker.io/library/mysql_mysql                                                                                0.0s
❯ docker-compose ps
NAME                COMMAND             SERVICE             STATUS              PORTS
❯ docker-compose up --build -d
[+] Building 0.7s (12/12) FINISHED
 => [mysql_mysql internal] load build definition from Dockerfile-mysql                                                                                0.0s
 => => transferring dockerfile: 37B                                                                                0.0s
 => [mysql_mysql internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [mysql_proxy internal] load build definition from Dockerfile-proxy                                                                                0.0s
 => => transferring dockerfile: 38B                                                                                0.0s
 => [mysql_mysql internal] load metadata for docker.io/library/mysql:5.7                                                                                0.5s
 => [mysql_proxy internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [mysql_proxy internal] load metadata for docker.io/envoyproxy/envoy-contrib-dev:latest                                                                                0.5s
 => CACHED [mysql_mysql 1/1] FROM docker.io/library/mysql:5.7@sha256:e767595ba3408fbb2dda493be3594b9a148178df58325fafe8b0363662935624                                                                                0.0s
 => [mysql_proxy] exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:3c79753649e111d827af25a1f91251a28b2c1071ab2a9905c3323bb4e636dc02                                                                                0.0s
 => => naming to docker.io/library/mysql_mysql                                                                                0.0s
 => => writing image sha256:29345e830982c0c7eba2edd75bf683782db389ee5e80b9a4702bf4c8de07db5a                                                                                0.0s
 => => naming to docker.io/library/mysql_proxy                                                                                0.0s
 => [mysql_proxy internal] load build context                                                                                0.0s
 => => transferring context: 32B                                                                                0.0s
 => [mysql_proxy 1/3] FROM docker.io/envoyproxy/envoy-contrib-dev:latest@sha256:14e560cd6b9497bfb44e64bce16ccf3b04de7cdf5c5d15995703606ec166fd68                                                                                0.0s
 => CACHED [mysql_proxy 2/3] COPY ./envoy.yaml /etc/envoy.yaml                                                                                0.0s
 => CACHED [mysql_proxy 3/3] RUN chmod go+r /etc/envoy.yaml                                                                                0.0s
[+] Running 3/3
 ⠿ Network envoymesh        Created                                                                                0.0s
 ⠿ Container mysql-proxy-1  Started                                                                                0.5s
 ⠿ Container mysql-mysql-1  Started                                                                                0.5s
❯ docker-compose ps
NAME                COMMAND                  SERVICE             STATUS              PORTS
mysql-mysql-1       "docker-entrypoint.s…"   mysql               running             33060/tcp
mysql-proxy-1       "/docker-entrypoint.…"   proxy               running             <IP_ADDRESS>:1999->1999/tcp, <IP_ADDRESS>:8001->8001/tcp

so, may be the issue is not my local terminal 's connection to dockerhub.

ok, thanks, ill go through the sandbox and see if i can repro

I ran in to the same problem. I do not think it is related python version.
It is failing while building tracer image and it is trying to pull flask_service:python-3.10-slim-bullseye from  docker.io/library/flask_service:python-3.10-slim-bullseye instead of local.
I removed --pull and ran docker-compose build and it seems to work. May be docker desktop version issue?

I removed --pull and ran docker-compose build and it seems to work. May be docker desktop version issue?

i suspect it is something like this - the flask_service:python-3.10-slim-bullseye  is not supposed to be pulled, it should be created, but the images it depends on should be pulled - ill check further...

same issue
May be, problem raised from  cannot find envoyproxy:tracing image in docker hub?
ref: https://hub.docker.com/search?q= envoyproxy%3Atracing

yep, same issue - altho dockerhub is not really relevant as the images are expected to be built rather than pulled
ill try and have a look at this today and see if i can figure why it works in some situations and not others

thx, docker-compose file ref: https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/skywalking_tracing

Encountered same error, I found that the flask_service is build from  flask_service:python-3.10-slim-bullseye, And I can't find it on dockerhub, is that's the reason? @daixiang0

Sorry, I recheck the problem and found it may due to a feature named "buildkit"  which is enabled by default for some version of docker engine, you can find more detail here, and you can use export DOCKER_BUILDKIT=0 to close buildkit.

I was facing this error when running docker compose build --pull at front-proxy example:
1 error occurred:
	* Status: pull access denied for flask_service, repository does not exist or may require 'docker login': denied: requested access to the resource is denied, Code: 1

In my case, export DOCKER_BUILDKIT=0 proposed solution didn't work, but running first docker compose build and then  docker compose up -d solved the issue for me.

--pull                  Always attempt to pull a newer version of the image.

Since you specify --pull, docker-compose will always attempt to pull, that is why you can not build.

the point is this - it should only pull for images that can be pulled, and build for the image that should be built
clearly this is an issue, so will prioritize
as it "works" in CI i havent made this a prio so far (apologies) - maybe following the docs never works and only the way its done in CI does - or perhaps something else - will check further...

so when i follow the steps in the docs for the cache sandbox i see the following:

$ docker-compose pull
Pulling flask_service ... done
Pulling front-envoy   ... done
Pulling service1      ... done
Pulling service2      ... done
WARNING: Some service image(s) must be built from source by running:
    docker-compose build flask_service

this is expected - as the warning states one of the images - flask_service cannot be pulled it must  be built
if others are seeing this turn into an error im guessing it must be related to the docker or more liikely docker-compose version
please post versions if you are seeing error when following the docs exactly and we can try and figure out when this is happening
it should be noted that the docker-compose pull step is optional and is documented mostly to avoid situations where people have old (envoy) images that dont match the current docs

docker compose will not work i think
you need to use docker-compose

@dhjack
cd envoy/examples/front-proxy/
docker-compose build

works for me

ive managed to repro this one of the examples (cors) - not sure why exactly - but will try to track down (ci skips the --pull step)

i think i have a fix for this - i need to test further to confirm but looks promising - i will PRing some cleanups for the examples and will include there

this will be fixed in #21962
for avoidance of doubt, and contrary to what i said previously

there was an issue
docker compose may work altho is untested atm

apologies if it seemed i doubted - not sure why i didnt manage to repro - either way this should be fixed shortly

This is still an issue.
Thanks for the easy commands, @dhjack
I think the issue can be fixed by specifying the Dockerfile path in docker-compose. Similar to this: https://github.com/grpc/grpc-web/blob/master/docker-compose.yml

To reproduce, open up: https://gitpod.io/#https://github.com/envoyproxy/envoy and run cd examples/front-proxy/ && docker-compose up

@SunnyAureliusRichard i have just followed those steps (again) and it works as expected - the issue raised here creates the following warning:
WARNING: Image for service service2 was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`

previously, in some cases this was throwing an error i believe
my first question is whether you are running from current Envoy main

I think the issue can be fixed by specifying the Dockerfile path in docker-compose

the Dockerfile path should not need to be set as the context is set

hi @phlax . Thanks for taking an interest in this.
I've tried a few things, and couldn't get it to work. Turns out that the image "grpcweb/prereqs" mentioned in the link above is in the docker hub as well, therefore their builds don't fail. Their use case seemed very similar to this one.
docker-compose build doesn't work either. I'm happy following the steps layed out by @dhjack , they solve both issues (running build or up first)
logs for docker-compose build:
gitpod /workspace/envoy (main) $ cd examples/front-proxy/
gitpod /workspace/envoy/examples/front-proxy (main) $ docker-compose build
[+] Building 0.9s (8/11)
 => [front-proxy-front-envoy internal] load build definition from Dockerfile-frontenvoy                                                   0.0s
 => => transferring dockerfile: 496B                                                                                0.0s
 => [front-proxy-service2 internal] load build definition from Dockerfile                                                                 0.0s
 => => transferring dockerfile: 438B                                                                                0.0s
 => [front-proxy-service1 internal] load build definition from Dockerfile                                                                 0.0s
 => => transferring dockerfile: 438B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load build definition from Dockerfile                                              0.0s
 => => transferring dockerfile: 303B                                                                                0.0s
 => [front-proxy-front-envoy internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [front-proxy-service2 internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [front-proxy-service1 internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load .dockerignore                                                                 0.0s
 => => transferring context: 2B                                                                                0.0s
 => [front-proxy-front-envoy internal] load metadata for docker.io/envoyproxy/envoy-dev:latest                                            0.8s
 => ERROR [front-proxy-service1 internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye                     0.8s
 => [flask_service:python-3.10-slim-bullseye internal] load metadata for docker.io/library/python:3.10.6-slim-bullseye@sha256:2124d4f8cc  0.8s
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xf0ce38]

goroutine 86 [running]:
github.com/docker/buildx/build.Build.func4.1()
        github.com/docker/buildx@v0.8.2/build/build.go:769 +0x4d8
golang.org/x/sync/errgroup.(*Group).Go.func1()
        golang.org/x/sync@v0.0.0-20220722155255-886fb9371eb4/errgroup/errgroup.go:75 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
        golang.org/x/sync@v0.0.0-20220722155255-886fb9371eb4/errgroup/errgroup.go:72 +0xa5
gitpod /workspace/envoy/examples/front-proxy (main) $
gitpod /workspace/envoy/examples/front-proxy (main) $
gitpod /workspace/envoy/examples/front-proxy (main) $
gitpod /workspace/envoy/examples/front-proxy (main) $
gitpod /workspace/envoy/examples/front-proxy (main) $
gitpod /workspace/envoy/examples/front-proxy (main) $ docker-compose build
[+] Building 0.6s (11/11) FINISHED
 => [front-proxy-service1 internal] load build definition from Dockerfile                                                                 0.0s
 => => transferring dockerfile: 438B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load build definition from Dockerfile                                              0.0s
 => => transferring dockerfile: 303B                                                                                0.0s
 => [front-proxy-front-envoy internal] load build definition from Dockerfile-frontenvoy                                                   0.0s
 => => transferring dockerfile: 496B                                                                                0.0s
 => [front-proxy-service2 internal] load build definition from Dockerfile                                                                 0.0s
 => => transferring dockerfile: 438B                                                                                0.0s
 => [front-proxy-service1 internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load .dockerignore                                                                 0.0s
 => => transferring context: 2B                                                                                0.0s
 => [front-proxy-front-envoy internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [front-proxy-service2 internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => ERROR [front-proxy-service1 internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye                     0.5s
 => CANCELED [flask_service:python-3.10-slim-bullseye internal] load metadata for docker.io/library/python:3.10.6-slim-bullseye@sha256:2  0.5s
 => CANCELED [front-proxy-front-envoy internal] load metadata for docker.io/envoyproxy/envoy-dev:latest                                   0.5s
------
 > [front-proxy-service1 internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye:
------
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
gitpod /workspace/envoy/examples/front-proxy (main) $

what version of Envoy are you testing this with (eg commit hash)

looking through the logs it seems as though this already failed with:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xf0ce38]

which is not the original error that was raised here
im not familiar with gitpod - but im wondering if there is some issue there
i would like to reproduce and track down any issue - but i need to know the versions of:

envoy
docker
docker-compose

sometimes i get that invalid memory address error, it's only happened with this repo. it could be some issue with their system. Unfortunately it's the only dev environment I have access to at the moment, so I can't reproduce it anywhere else.
envoy main: 9e7fba8f90180a3868d6322e6c9ac3782ff400a1
docker: Docker version 20.10.17, build 100c701
docker-compose: Docker Compose version 2.8.0-gitpod.0
If you'd like to reproduce it, I've put a link above.

sometimes i get that invalid memory address error, it's only happened with this repo

i have never seen this issue before so i think it is more to do with gitpod

If you'd like to reproduce it, I've put a link above.

i have tried reproducing and it works as expected in my env
could you try and reproduce the problem somewhere other than on gitpod

docker-compose: Docker Compose version 2.8.0-gitpod.0

this is a docker compose version i think - i dont know if it will work
https://pypi.org/project/docker-compose/

Getting the same error. MacOS 12.6 on M1 using Docker Desktop.
Head: 362e415045
Docker Compose: 2.10.2
Docker: 20.10.17, build 100c701
> docker-compose build
[+] Building 0.3s (14/14) FINISHED
 => [front-proxy-service2 internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 438B                                                                                0.0s
 => [front-proxy-service2 internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => CANCELED [front-proxy-front-envoy internal] load metadata for docker.io/envoyproxy/envoy-dev:latest                                                                                0.3s
 => ERROR [front-proxy-service2 internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye                                                                                0.3s
 => [front-proxy-front-envoy internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [front-proxy-front-envoy internal] load build definition from Dockerfile-frontenvoy                                                                                0.0s
 => => transferring dockerfile: 496B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [flask_service:python-3.10-slim-bullseye internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 686B                                                                                0.0s
 => CANCELED [flask_service:python-3.10-slim-bullseye internal] load metadata for docker.io/library/python:3.10.7-slim-bullseye@sha256:f2ee145f3bc4e061f8dfe7e6ebd427a410121495a0bd26e7622136db060c59e0                                 0.2s
 => [front-proxy-service1 internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [front-proxy-service1 internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 438B                                                                                0.0s
 => [auth] envoyproxy/envoy-dev:pull token for registry-1.docker.io                                                                                0.0s
 => [auth] library/python:pull token for registry-1.docker.io                                                                                0.0s
 => [auth] library/flask_service:pull token for registry-1.docker.io                                                                                0.0s
------
 > [front-proxy-service2 internal] load metadata for docker.io/library/flask_service:python-3.10-slim-bullseye:
------
failed to solve: flask_service:python-3.10-slim-bullseye: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

Tried to logout and login to docker hub, same results.

so when i follow the steps in the docs for the cache sandbox i see the following:
$ docker-compose pull
Pulling flask_service ... done
Pulling front-envoy   ... done
Pulling service1      ... done
Pulling service2      ... done
WARNING: Some service image(s) must be built from source by running:
    docker-compose build flask_service

this is expected - as the warning states one of the images - flask_service cannot be pulled it must be built
if others are seeing this turn into an error im guessing it must be related to the docker or more liikely docker-compose version
please post versions if you are seeing error when following the docs exactly and we can try and figure out when this is happening
it should be noted that the docker-compose pull step is optional and is documented mostly to avoid situations where people have old (envoy) images that dont match the current docs

Hi, I hit this issue also.  I followed the instructions here:(https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/front_proxy.html).
❯ docker-compose pull
[+] Running 3/4
 ⠿ service2 Skipped                                                                                0.0s
 ⠿ front-envoy Skipped                                                                                0.0s
 ⠿ service1 Skipped                                                                                0.0s
 ⠿ flask_service Error                                                                                1.1s
WARNING: Some service image(s) must be built from source by running:
    docker compose build flask_service
Error response from daemon: pull access denied for flask_service, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Running docker-compose up --build -d also errors out trying the pull the image.
After running docker compose build flask_service, the example runs fine for me.
I'm running docker desktop 4.10.1 on mac, Engine 20.10.17 and Compose v2.6.1.  Hope this helps.
Thanks!

it appears your docker-compose is really docker compose from the logs
this is known to not work atm
its on my radar to switch the examples -> docker compose but it will take some time

heads up to anyone tracking the issues discussed here ...
we have finally switched the examples/documentation to using docker compose that comes with Docker rather than the python versions - and fixed the CI at least to work with that
i believe that the examples should still work with the python docker-compose but i didnt get to testing that
the documentation is still being updated to reflect the changes, feedback, prs etc appreciated


Test protobuf c ext

cc @dwsupplee @jdpedrie Once https://github.com/GoogleCloudPlatform/google-cloud-php/pull/600 is merged we should create a similar PR for google-cloud-php
Note that this doesn't test all combinations of platforms and c extension presence/absence - this is only to be a good citizen for Travis, as the extra testing combinations are (IMHO) unlikely to find issues.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #96   +/-   ##
=======================================
  Coverage   90.52%   90.52%
=======================================
  Files          33       33
  Lines        2249     2249
=======================================
  Hits         2036     2036
  Misses        213      213

Continue to review full report at Codecov.

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

Gentle ping on this


ImmutableImage isn't actually immutable

ImmutableImage is immutable in the sense that the user can't submit commands that modify the image contents. But there is one other kind of operation that is not considered in this: layout transitions. A layout transition is a write operation, and while ImmutableImage will normally be in the ShaderReadOnlyOptimal layout, doing a copy_image with the image as the source will transition it to TransferSrcOptimal. For the user this is invisible, but this matters a lot for synchronisation within the GPU, because such a write operation can't happen while another queue is accessing the image. This could create unexpected errors for the user when submitting command buffers, because the user thinks the image isn't ever written and thus concurrent access is possible, when it actually is written to, just invisibly to the user.
I have been thinking for a while about whether the immutable buffer and image types are even really needed in Vulkano. I suppose they signal the intent of the user, that they never intend to ever write to the buffer or image again, but to call it "immutable" is also misleading as demonstrated above. There may be a speed argument to be made, since the synchronisation for immutable resources is a little simpler, but that needs to be tested by comparing performance with the mutable resource variants.

Here are some ideas or thoughts, that could be unsound or not valid, but overall I think it might be a good idea to generalize images into a single type. This would mean that users would have to create the own staging buffers unless we provide helper methods to do that.

All layout transitions are done manually.

Images could be initialized with an initial layout.
Command buffers would provide a method to transition the image.
All command would check the layout and error out if it isn't in a valid layout.

Create a ImageLayoutUsage type that would handle transitions automatically.

Would be supplied at image creation.
Any method that requires a transition to be made requires the image to be used exclusively.
This could maybe be automatically derived from the ImageUsage?
A general use image that would require only one transition.

Used anywhere, but slow.

ImageLayoutUsage {
    initial: ImageLayout::Undefined,
    transfer_src: ImageLayout::General,
    transfer_dst: ImageLayout::General,
    attachment: ImageLayout::General,
    descriptor: ImageLayout::General,
}

A more optimized version that would require more transitions.

Used for sampled images & input attachments

ImageLayoutUsage {
    initial: ImageLayout::Undefined,
    transfer_src: ImageLayout::TransferSrcOptimal,
    transfer_dst: ImageLayout::TransferDstOptimal,
    attachment: ImageLayout::ShaderReadOnlyOptimal,
    descriptor: ImageLayout::ShaderReadOnlyOptimal,
}

A transient attachment imageImageLayoutUsage {
    initial: ImageLayout::ColorAttachmentOptimal,
    transfer_src: ImageLayout::None, // Not allowed
    transfer_dst: ImageLayout::None, // Not allowed
    attachment: ImageLayout::ColorAttachmentOptimal,
    descriptor: ImageLayout::None, // Not allowed
}

Your second point already exists, it's the descriptor_layouts method on the ImageAccess trait. It doesn't contain all the items you mentioned, but the basic idea is there. I've been thinking that it would be nice if the user could specify these layouts themselves when creating an image, but that would require some extra code to check that the specified layouts are valid for each use and for the image.


Data not accurate

Hi all,
I checked If the data that has been received is accurate. Its not. My friend is at Ziggo Dome for BlackPink Concert but his location is still at his work. I check find my friends and live view is in Ziggo Dome.
The information from iCloud3 is still at his work...

Without an error message or programming exception message, it is probably a data change issue rather than a program problem. It sounds like iC3 did not get a trigger to update the devices location. This can be caused by no OS App exit zone trigger or the next location update time had not been reached so iC3 had nor requested a new location. A poor cell area can also generate errors and the device has been paused. The Event Log should show what is going on. Using Event Log > Actions > Show Tracking Monitors can give more detailed info.


bigtable: inmem ReadModifyWrite won't return cell timestamp.

https://github.com/GoogleCloudPlatform/google-cloud-go/blob/master/bigtable/bttest/inmem.go#L907
comparing to:
https://cloud.google.com/bigtable/docs/reference/data/rpc/google.bigtable.v2#google.bigtable.v2.ReadModifyWriteRowResponse

it seems this will fix it:
f.Columns = append(f.Columns, &btpb.Column{
			Qualifier: []byte(qual),
			Cells: []*btpb.Cell{{
				TimestampMicros: cell.ts,
				Value:           cell.value,
			}},
		})

is PR welcomed?

Yes, absolutely! We don't use github for that, though. See CONTRIBUTING.md for details.

@garye saw it... seems too much hassle for one line of code changes :)
wonder if priority of this can be bumped, since it blocks using inmem for testing.

Are you using the inmem stuff from Go or from the Cloud SDK emulator?

I have a fix out for review. Thanks for the bug report and suggested change.

@garye for go.


Create calibration firmware for teensy 3.6

Currently all of the measurements are done by hand measuring the voltage input/outputs. To make the SPSs more usable, a calibration routine can be written using the Teensys ADCs. One analog pin will output the voltage, while other pins will read the voltage and current measurements.

The following relavent information is pulled from https://www.pjrc.com/store/teensy36.html
Analog Inputs
25 pins can be used an analog inputs, for reading sensors or other analog signals. Basic analog input is done with the analogRead function. The default resolution is 10 bits (input range 0 to 1023), but can be adjusted with analogReadResolution. The hardware allows up to 16 bits of resolution, but in practice only up to 13 bits are normally usable due to noise. More advanced use is possible with the ADC library. Analog inputs can also receive audio signals with the Audio library, but the sound quality is lower than using the Audio shield.
Analog Outputs / Digital To Analog (DAC)
Two true analog output DACs are present on pins A21 & A22. These may be used with analogWrite, or the Audio library.

Added recorder.py to allow for automated control of measuring from teensy and SMU simulated a voltage load


feat: add external content download to octets:store directive

Documentation, feature.
Discussed request limit is not implemented. https://github.com/toa-io/toa/issues/688

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

Project coverage is 49.35%. Comparing base (a59a16f) to head (6ac72db).
Report is 167 commits behind head on dev.

Files
Patch %
Lines

...sions/exposition/source/directives/octets/Store.ts
0.00%
17 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #689      +/-   ##
==========================================
- Coverage   50.18%   49.35%   -0.84%
==========================================
  Files         358      366       +8
  Lines       11886    12543     +657
  Branches     1276     1318      +42
==========================================
+ Hits         5965     6190     +225
- Misses       5921     6353     +432

Flag
Coverage Δ

unit
49.35% <0.00%> (-0.84%)
:arrow_down:

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

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


Appears to be horizontal overflow on homepage only

there's 'horizontal jiggle' on the homepage that shouldn't be there - doesn't seem to be set to 100% the width of the page -- only happened after top banner was introduced so I'm sure that's the cause.

Can you provide more details? (e.g. browser? viewport size?)
A screencast would be great, I'm unable to replicate this issue.

it occurs on chrome, firefox, and edge - that's all i tested. and pretty much every viewport width except mobile
not a huge deal --- i'll just show you next week

Is this it? (sorry for the crappy gif)

yes

@ryconn888 has this been fixed in the recent updates?

indeed it has. i will close now


[Bug] Unity 2021.2 "Internal build system error. Backend exited with code" error after import Firebase SDK 8.8.0

[REQUIRED] Please fill in the following fields:

Unity editor version: Unity 2021.2.9f1
Firebase Unity SDK version: 8.8.0
Source you installed the SDK:  Unity Package Manager by point to the path where tar file is.
(tar file and how to install SDK with tar file is follow the guide here: https://developers.google.com/unity/instructions#install-tgz)
Problematic Firebase Component: com.google.firebase.app (Auth, Database, etc.)
Other Firebase Components in use: Auth, Database, Storage, messaging, remote-config, crashlytics, analytics (Auth, Database, etc.)
Additional SDKs you are using: External dependency manager (Facebook, AdMob, etc.)
Platform you are using the Unity editor on: MacBook Pro with M1 chip and OS version is 12.3 Beta （The OS version may not a reason due to the same issue occur on macOS 12.2）
Platform you are targeting: Android/iOS (iOS, Android, and/or desktop)
Scripting Runtime: IL2CPP (Mono, and/or IL2CPP)

[REQUIRED] Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
Once I import the Firebase SDK the Unity Editor show the message likes "Internal build system error. Backend exited with code", "Backend produced unparsable log entry" and then the compile backend of Unity Editor is totally crash so I cannot compile my game script after the script is modified.
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
What's the issue repro rate? (eg 100%, 1/5 etc)

Create empty Unity project and import Firebase SDK by tar file and EDM4U. (Basically I just import "com.google.firebase.app" package and issue comes)
Create a new .cs script and do some modify on the script.
Issue reproduce.
100% reproduce.
Reproduced on Unity 2021.2.9, 2021.2.10

What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Relevant Code:
// TODO(you): code here to reproduce the problem

Extra information:
I also got error looks like #835
I'm sure the python is installed in the computer
When I tested the python install status by those command I got the result like this.
`
which python
/opt/homebrew/bin/python
python --version
Python 3.9.10
`
And some updates, after deleting the file /Asstes/Firebase/Editor/Firebase.Editor.dll the error message is gone and everything on Editor works fine. (Not tested the Firebase is works great or not on the built player)

Unfortunately Mac with M1 chip is not yet supported by Firebase Unity SDK.
Adding support is on the internal roadmap and you can track the status in the following issue:
https://github.com/firebase/quickstart-unity/issues/1100
There are also some comments in that issue of other firebase users building from source on the M1 and sharing generated bundles, so you could try to see if those work as a temporary workaround.

I don't think it is similar issue to #1100.
Due to I can use Firebase SDK and everything works great, when I was using Unity 2020.3.x and the other thing on the environment is same as current one.
(Same machine, same OS, same Unity project, same python install status, different Unity Editor)
But once I upgrade project to Unity 2021.2, the issue comes.
(And after delete the Firebase.Editor.dll, the issue gones)
Since during the whole testing the only thing change is Unity Editor version, so I would say the Firebase SDK may has something wrong under Unity 2021.2.

Hello, I am researching on this issue these days.
And have some new discovery, please see #1232, I'm not sure the issue is the same issue or not, so I create a new GitHub issue.
I don't have Intel Mac right now, I guess if Intel Mac can reproduce the problem on macOS 12.3, then the issue should positioned as the removing of Python2 on new OS version and the usage of Python2 inside the Firebase Editor C# script.

solved :
https://github.com/techyworm10/firebase-unity-sdk-editor-python-fix

I'm afraid that this might not be fixed by fixing Firebase.Editor.dll and seems to only occurs with Unity 2021.2.
Here is the way I reproduced this.

Use Unity 2021.2.17f1
Create an empty project
Install EDM4U and FirebaseApp (either .tgz or .unitypackage)
Patch the Firebase.Editor.dll with python fix (we have an internal build that fixes that issue)
Build an iOS build, or Android build.

Seems like the following log will always appears, even after clearing the log.
Internal build system error. Backend exited with code 2.
STDOUT:
Finished compiling graph: 245 nodes, 2781 flattened edges (2781 ToBuild, 0 ToUse), maximum node priority 99
STDERR:
tundra: error: Unexpected stdin

After initiating the build, Unity editor logs the following:
Build completed with a result of 'Failed' in 1 seconds (631 ms)
UnityEngine.StackTraceUtility:ExtractStackTrace () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/StackTrace.cs:37)
UnityEngine.DebugLogHandler:LogFormat (UnityEngine.LogType,UnityEngine.Object,string,object[])
UnityEngine.Logger:Log (UnityEngine.LogType,object)
UnityEngine.Debug:LogError (object)
UnityEditor.BuildPlayerWindow/DefaultBuildMethods:BuildPlayer (UnityEditor.BuildPlayerOptions) (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:192)
UnityEditor.BuildPlayerWindow:CallBuildMethods (bool,UnityEditor.BuildOptions) (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:94)
UnityEditor.BuildPlayerWindow:GUIBuildButtons (UnityEditor.Modules.IBuildWindowExtension,bool,bool,bool,UnityEditor.Build.BuildPlatform,UnityEditor.Modules.IBuildPostprocessor) (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindow.cs:1171)
UnityEditor.BuildPlayerWindow:ShowBuildTargetSettings () (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindow.cs:1017)
UnityEditor.BuildPlayerWindow:OnGUI () (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindow.cs:517)
UnityEditor.HostView:InvokeOnGUI (UnityEngine.Rect) (at /Users/bokken/buildslave/unity/build/Editor/Mono/HostView.cs:448)
UnityEditor.DockArea:DrawView (UnityEngine.Rect) (at /Users/bokken/buildslave/unity/build/Editor/Mono/GUI/DockArea.cs:387)
UnityEditor.DockArea:OldOnGUI () (at /Users/bokken/buildslave/unity/build/Editor/Mono/GUI/DockArea.cs:378)
UnityEngine.UIElements.IMGUIContainer:DoOnGUI (UnityEngine.Event,UnityEngine.Matrix4x4,UnityEngine.Rect,bool,UnityEngine.Rect,System.Action,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:351)
UnityEngine.UIElements.IMGUIContainer:HandleIMGUIEvent (UnityEngine.Event,UnityEngine.Matrix4x4,UnityEngine.Rect,System.Action,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:693)
UnityEngine.UIElements.IMGUIContainer:HandleIMGUIEvent (UnityEngine.Event,System.Action,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:665)
UnityEngine.UIElements.IMGUIContainer:HandleIMGUIEvent (UnityEngine.Event,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:658)
UnityEngine.UIElements.IMGUIContainer:SendEventToIMGUIRaw (UnityEngine.UIElements.EventBase,bool,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:618)
UnityEngine.UIElements.IMGUIContainer:SendEventToIMGUI (UnityEngine.UIElements.EventBase,bool,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:607)
UnityEngine.UIElements.IMGUIContainer:HandleEvent (UnityEngine.UIElements.EventBase) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:535)
UnityEngine.UIElements.CallbackEventHandler:HandleEventAtTargetPhase (UnityEngine.UIElements.EventBase) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/Events/EventHandler.cs:151)
UnityEngine.UIElements.MouseCaptureDispatchingStrategy:DispatchEvent (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/Events/MouseCaptureDispatchingStrategy.cs:88)
UnityEngine.UIElements.EventDispatcher:ApplyDispatchingStrategies (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:381)
UnityEngine.UIElements.EventDispatcher:ProcessEvent (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:344)
UnityEngine.UIElements.EventDispatcher:ProcessEventQueue () (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:306)
UnityEngine.UIElements.EventDispatcher:OpenGate () (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:270)
UnityEngine.UIElements.EventDispatcherGate:Dispose () (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:75)
UnityEngine.UIElements.EventDispatcher:ProcessEvent (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:372)
UnityEngine.UIElements.EventDispatcher:Dispatch (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel,UnityEngine.UIElements.DispatchMode) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:222)
UnityEngine.UIElements.BaseVisualElementPanel:SendEvent (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.DispatchMode) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/Panel.cs:419)
UnityEngine.UIElements.UIElementsUtility:DoDispatch (UnityEngine.UIElements.BaseVisualElementPanel) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/UIElementsUtility.cs:468)
UnityEngine.UIElements.UIElementsUtility:UnityEngine.UIElements.IUIElementsUtility.ProcessEvent (int,intptr,bool&) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/UIElementsUtility.cs:211)
UnityEngine.UIElements.UIEventRegistration:ProcessEvent (int,intptr) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/UIElementsUtility.cs:74)
UnityEngine.UIElements.UIEventRegistration/<>c:<.cctor>b__1_2 (int,intptr) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/UIElementsUtility.cs:28)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /Users/bokken/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:189)

(Filename: /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs Line: 192)

UnityEditor.BuildPlayerWindow+BuildMethodException: Error building Player because scripts have compile errors in the editor
  at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.BuildPlayer (UnityEditor.BuildPlayerOptions options) [0x002cc] in /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:193
  at UnityEditor.BuildPlayerWindow.CallBuildMethods (System.Boolean askForBuildLocation, UnityEditor.BuildOptions defaultBuildOptions) [0x00080] in /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:94
UnityEngine.StackTraceUtility:ExtractStackTrace () (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/StackTrace.cs:37)
UnityEngine.DebugLogHandler:LogFormat (UnityEngine.LogType,UnityEngine.Object,string,object[])
UnityEngine.Logger:Log (UnityEngine.LogType,object)
UnityEngine.Debug:LogError (object)
UnityEditor.BuildPlayerWindow:CallBuildMethods (bool,UnityEditor.BuildOptions) (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs:99)
UnityEditor.BuildPlayerWindow:GUIBuildButtons (UnityEditor.Modules.IBuildWindowExtension,bool,bool,bool,UnityEditor.Build.BuildPlatform,UnityEditor.Modules.IBuildPostprocessor) (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindow.cs:1171)
UnityEditor.BuildPlayerWindow:ShowBuildTargetSettings () (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindow.cs:1017)
UnityEditor.BuildPlayerWindow:OnGUI () (at /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindow.cs:517)
UnityEditor.HostView:InvokeOnGUI (UnityEngine.Rect) (at /Users/bokken/buildslave/unity/build/Editor/Mono/HostView.cs:448)
UnityEditor.DockArea:DrawView (UnityEngine.Rect) (at /Users/bokken/buildslave/unity/build/Editor/Mono/GUI/DockArea.cs:387)
UnityEditor.DockArea:OldOnGUI () (at /Users/bokken/buildslave/unity/build/Editor/Mono/GUI/DockArea.cs:378)
UnityEngine.UIElements.IMGUIContainer:DoOnGUI (UnityEngine.Event,UnityEngine.Matrix4x4,UnityEngine.Rect,bool,UnityEngine.Rect,System.Action,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:351)
UnityEngine.UIElements.IMGUIContainer:HandleIMGUIEvent (UnityEngine.Event,UnityEngine.Matrix4x4,UnityEngine.Rect,System.Action,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:693)
UnityEngine.UIElements.IMGUIContainer:HandleIMGUIEvent (UnityEngine.Event,System.Action,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:665)
UnityEngine.UIElements.IMGUIContainer:HandleIMGUIEvent (UnityEngine.Event,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:658)
UnityEngine.UIElements.IMGUIContainer:SendEventToIMGUIRaw (UnityEngine.UIElements.EventBase,bool,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:618)
UnityEngine.UIElements.IMGUIContainer:SendEventToIMGUI (UnityEngine.UIElements.EventBase,bool,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:607)
UnityEngine.UIElements.IMGUIContainer:HandleEvent (UnityEngine.UIElements.EventBase) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/IMGUIContainer.cs:535)
UnityEngine.UIElements.CallbackEventHandler:HandleEventAtTargetPhase (UnityEngine.UIElements.EventBase) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/Events/EventHandler.cs:151)
UnityEngine.UIElements.MouseCaptureDispatchingStrategy:DispatchEvent (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/Events/MouseCaptureDispatchingStrategy.cs:88)
UnityEngine.UIElements.EventDispatcher:ApplyDispatchingStrategies (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel,bool) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:381)
UnityEngine.UIElements.EventDispatcher:ProcessEvent (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:344)
UnityEngine.UIElements.EventDispatcher:ProcessEventQueue () (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:306)
UnityEngine.UIElements.EventDispatcher:OpenGate () (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:270)
UnityEngine.UIElements.EventDispatcherGate:Dispose () (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:75)
UnityEngine.UIElements.EventDispatcher:ProcessEvent (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:372)
UnityEngine.UIElements.EventDispatcher:Dispatch (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.IPanel,UnityEngine.UIElements.DispatchMode) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/EventDispatcher.cs:222)
UnityEngine.UIElements.BaseVisualElementPanel:SendEvent (UnityEngine.UIElements.EventBase,UnityEngine.UIElements.DispatchMode) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/Panel.cs:419)
UnityEngine.UIElements.UIElementsUtility:DoDispatch (UnityEngine.UIElements.BaseVisualElementPanel) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/UIElementsUtility.cs:468)
UnityEngine.UIElements.UIElementsUtility:UnityEngine.UIElements.IUIElementsUtility.ProcessEvent (int,intptr,bool&) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/UIElementsUtility.cs:211)
UnityEngine.UIElements.UIEventRegistration:ProcessEvent (int,intptr) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/UIElementsUtility.cs:74)
UnityEngine.UIElements.UIEventRegistration/<>c:<.cctor>b__1_2 (int,intptr) (at /Users/bokken/buildslave/unity/build/ModuleOverrides/com.unity.ui/Core/UIElementsUtility.cs:28)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /Users/bokken/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:189)

(Filename: /Users/bokken/buildslave/unity/build/Editor/Mono/BuildPlayerWindowBuildMethods.cs Line: 99)

There are some online posts but nothing really works for my case.
https://forum.unity.com/threads/how-do-i-resolve-this.1153742/
Will need to ask the team to look into this.

Seems like this issue is not unique to Firebase SDK.
I tried Facebook Unity SDK in an empty project and got the same error.

I've got this build error also.
Upgraded to v8.9.0 today, expected python macos problem resolved; however, nothing changed :(

With EDM4U 1.2.169 + Python patched Firebase 8.8.0 this issue will not happen.
But EDM4U 1.2.170 + official Firebase 8.9.0 the issue back.
All tested on Unity 2021.2.X
So Unity has issue, and some part of the EDM4U + Firebase will trigger this issue.
And the Python issue patched Firebase 8.8.0 are just no problem?
That's all clues we have.

@sableangle
Odd... most of the change in EDM4U 1.2.170 are related to iOS Resolver.
https://github.com/googlesamples/unity-jar-resolver/releases/tag/v1.2.170
What happens if you downgrade EDM4U to 1.2.169
You will need to remove Assets/ExternalDependencyManager first before installing the older version, if you imported it through .unitypackage.

With EDM4U 1.2.169 + Python patched Firebase 8.8.0 this issue will not happen. But EDM4U 1.2.170 + official Firebase 8.9.0 the issue back.

When you attempt using the 8.9.0 SDK, does it print anything in your error log about finding a python executable?
(The updated version should log an error if it was unable to find Python.)

When you attempt using the 8.9.0 SDK, does it print anything in your error log about finding a python executable?
(The updated version should log an error if it was unable to find Python.)

No python relative error logs found when using 8.9.0 SDK in my case.

In IOS "Internal build system error. Backend exited with code" error after last update of the Operating system and import Firebase SDK 8.9.0.
Unity 2021.2.5 - 2021.2.15, on an older 2021.1.Х version everything is ok.
External Dependency Manager 1.2.168, 1.2.169, 1.2.170.
Firebase SDK 8.9.0
macOS 12.3.1 (21E258)
MacBook Pro(MacBookPro12,1 Dual-Core Intel Core i5)
Are there any ideas how to fix this?

Uniy 2021.3 + Firebase 8.9.0 + Apple M1
DllNotFoundException: FirebaseCppApp-8_9_0 assembly:<unknown assembly> type:<unknown type> member:(null)
Firebase.AppUtilPINVOKE+SWIGExceptionHelper..cctor () (at Z:/tmp/tmp.GOobKx5vLv/firebase/app/client/unity/proxy/AppUtilPINVOKE.cs:117)
Rethrow as TypeInitializationException: The type initializer for 'SWIGExceptionHelper' threw an exception.
Firebase.AppUtilPINVOKE..cctor () (at Z:/tmp/tmp.GOobKx5vLv/firebase/app/client/unity/proxy/AppUtilPINVOKE.cs:137)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.AppUtilPINVOKE' threw an exception.
Firebase.AppUtil.SetLogFunction (Firebase.LogUtil+LogMessageDelegate arg0) (at Z:/tmp/tmp.GOobKx5vLv/firebase/app/client/unity/proxy/AppUtil.cs:64)
Firebase.LogUtil..ctor () (at Z:/tmp/tmp.GOobKx5vLv/firebase/app/client/unity/proxy/LogUtil.cs:81)
Firebase.LogUtil..cctor () (at Z:/tmp/tmp.GOobKx5vLv/firebase/app/client/unity/proxy/LogUtil.cs:37)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.LogUtil' threw an exception.
Firebase.FirebaseApp..cctor () (at Z:/tmp/tmp.GOobKx5vLv/firebase/app/client/unity/proxy/FirebaseApp.cs:67)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.FirebaseApp' threw an exception.
FirebaseChecker.Start () (at Assets/Scripts/FirebaseChecker.cs:13)

Unity 2021.3 (Intel version) + Firebase 8.9.0 + Apple M1 + Android Build = working perfectly

I also have encountered this issue and nothing still works as expected.

I have same issue Internal build system error. Backend exited with code 2. Unity 2020.2.10, any solution?

Unity 2021.3 (Intel version) + Firebase 8.9.0  same issue (backend exited with code 2)
Fixed with the workaround.

Based on my testing so far, this issue does not occur when using the just-released version 8.10.0 of the Firebase Unity SDK
I was able to just add the relevant 8.10.0 packages to a project that had been failing, restarted Unity, and then builds succeeded.
I'll continue to look into why the issue occurs in 8.9.0, but in the meantime using 8.10.0 is a possible workaround

The relevant change that fixes this in 8.10.0 seems to be the change to try Python3 before trying Python (https://github.com/firebase/firebase-unity-sdk/pull/249). I tried to debug further, but it's still not entirely clear to me why trying Python is causing it to fail despite the exception handling present in the code.
But since it seems to be working in 8.10.0 for now, I am going to close this issue and recommend updating to 8.10.x if this issue occurs.
If anyone encounters this issue despite using firebase unity SDK 8.10.x or later, please reopen.


ws: allow filtering notification by parameters

Closes #3624.

Some questions:

Is there any full test for client-to-server communication to check that filtering works? Not just unmarshalling but also creating notifications and receiving only the important ones. Have not found it.
Are type limitations correct?
What limit should be used for parameter filters? Why should we have it (the issue says)? Just not to have some OOMs on a server side or it is possible to abuse a node somehow?

Is there any full test for client-to-server communication to check that filtering works?

Use and extend the following tests:
https://github.com/nspcc-dev/neo-go/blob/990634a43af5be0609270b2fce6b103f92686998/pkg/services/rpcsrv/subscription_test.go#L130
https://github.com/nspcc-dev/neo-go/blob/990634a43af5be0609270b2fce6b103f92686998/pkg/services/rpcsrv/client_test.go#L2131
That's the way how we test subscriptions. If it's not enough, then create your own test based on https://github.com/nspcc-dev/neo-go/blob/990634a43af5be0609270b2fce6b103f92686998/pkg/services/rpcsrv/client_test.go#L1895

Are type limitations correct?

Will be answered in review.

What limit should be used for parameter filters?

Let's limit the number of parameters to 16 for now, it's pretty enough for notifications used by NeoFS and at the same time it won't allow to DoS the node with useless filtering process for large notifications/filters. Also, parameter types should be limited by non-compound types (simple Integer, String, Hash160 and etc.; excluding Arrays, Structs and Maps), we don't need compounds for now and NeoFS contracts don't use them in notifications; in future the set of supported types may be extended.

Why should we have it (the issue says)?

Avoid filters misuse and unwanted load for RPC server. This extension will be available on public RPC nodes.

it is possible to abuse a node somehow?

Deploy contract that emits thousands of notifications (it's possible, hi, https://github.com/nspcc-dev/neo-go/issues/3490), then subscribe to RPC server with matching filters.

@carpawell tests are failing.


[FEATURE] Support FMPP Freemarker Templates

https://www.npmjs.com/package/freemarker.js

I do not like the concept of requiring Java to operate this library. Support is fine, but requirement in unacceptable


Add Asset Storage library

This MVP will implement the basic client support for interacting with the Asset Storage API.
ToDo

[ ] New robocorp.storage package dealing with the assets in a similar way to Work Items.
[ ] Listing, creating, retrieving and deleting assets support.
[ ] Basic direct asset upload when saving data into the asset.
[ ] Basic documentation.

⚠ This first iteration won't include (destined for a follow-up post-release work):

Updating an asset. (no upstream API support atm)
Uploading payloads bigger than 6MB. (requires URL-based asset upload support)
Uploading assets of other types than text. (like JSON, bytes, files etc.)
Working locally with assets. (requires the Adapter pattern which mimics the flow with local files)
Detailed documentation aligned well with the rest of the library.
Production-ready Portal example show-casing the usage.
Legacy rpaframework support with RF keywords.

Once this is done, the next step is to wrap this functionality into RF keywords by adding robocorp-storage as a dependency into the rpaframework legacy library. (https://github.com/robocorp/rpaframework/issues/957)


Ben Scripts and Qualitative Analysis Code

Changes:

diff3 analysis script
README
style fixes
repo.py cones repo to a specified path. Alternative to the clone_repo method since it takes a string for the path and returns a different git repo obj

I will close this PR for now


clang -march not supported on arm x64

Compiling with clang on android with termux, got error about unsupported option -march=native.
My temp solution here: https://mikhail-yudin.ru/blog/android/termux-resolve-compile-troubles

Currently also encountering this error, have you had any luck since your last message?

nope...

This might help: https://stackoverflow.com/questions/35446440/getting-three-346-cannot-locate-for-ztvn10-cxxabiv-symbols

Having same issue

This worked for me:
gem install sassc --version=2.2.1 -- --disable-march-tune-native

This worked for me:
gem install sassc --version=2.2.1 -- --disable-march-tune-native

This worked for me:
gem install sassc --version=2.2.1 -- --disable-march-tune-native

Worked for me, thanks :)

This worked for me:
gem install sassc --version=2.2.1 -- --disable-march-tune-native

Worked for me, thanks :)

if working with bundler, you can run
bundle config build.sassc --disable-march-tune-native


Migrate to Androidx

Till this moment we are avoiding using libraries that support AndroidX.
We should migrate to androidx and upgrade dependencies.

The job #111 assigned to @bahaaib/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @ammaratef45/z

Bug was reported, see §29: +15 point(s) just awarded to @ammaratef45/z

@ammaratef45 Copy that

@bahaaib/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.


Integrate error responses w/ what web5-js expects

web5-js was built in conjunction w/ dwn-server, and right now the proxy doesn't properly format the error responses

lots of good inspo to pull from starting at this line and going down https://github.com/tbdeng/pfi-prototype/blob/main/src/api.ts#L44

presumably this'll happen in the dwn-http-server.ts so if we yank that out into a dedicated dwn-http-js package (or however we choose to organize it) then it's no longer relevant here


Emoji Panel Does Not Work Properly Anymore

Issue Type: Bug
Steps to Reproduce

Windows Key + . (period) => Opens up the emoji panel
Writing anything while the panel is showing searches an emoji that matches the text that is being written.
The emoji panel reacts correctly to whatever emoji we search for but the search text being written doesn't show up like it used to before.
It used to show up covered in a highlighted way so it is distinct from other letters that doesn't come under the emoji search query.

This stopped working after the recent updates.
Writing anything does not show up while the emoji panel is on.
Disabling all the extensions does not help the problem.
This was not a problem on earlier versions.
I noticed it while putting emojis in the commit messages but it doesn't work on the normal code area either

VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19042

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz (4 x 3193)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.94GB (1.65GB free)

Process Argv
--crash-reporter-id 3ac050ed-0dbb-4ec8-b92d-2b91c4699d0f

Screen Reader
no

VM
50%

Extensions (31)

Extension
Author (truncated)
Version

better-comments
aar
2.1.0

html-snippets
abu
0.2.1

notes
can
1.1.0

bracket-pair-colorizer
Coe
1.0.61

gitlens
eam
11.2.1

vscode-html-css
ecm
1.10.2

vsc-material-theme
Equ
33.1.2

vsc-material-theme-icons
equ
1.2.2

prettier-vscode
esb
5.9.2

auto-close-tag
for
0.5.10

auto-rename-tag
for
0.1.6

vscode-styled-components
jpo
1.5.0

react-native-snippet
jun
0.5.6

kite
kit
0.141.0

graphql-for-vscode
kum
1.15.3

vscode-language-babel
mgm
0.0.30

vscode-docker
ms-
1.10.0

debugger-for-chrome
msj
4.12.12

vscode-react-native
msj
1.4.0

vscode-css-peek
pra
4.1.0

live-sass
rit
3.0.0

LiveServer
rit
5.6.1

vscode-scss-formatter
sib
2.1.0

js-jsx-snippets
sky
10.1.0

code-spell-checker
str
1.10.2

highlight-matching-tag
vin
0.10.0

vscodeintellicode
Vis
1.2.11

vscode-icons
vsc
11.1.0

omi-snippets
Wsc
2.2.8

material-theme
zhu
3.9.15

html-css-class-completion
Zig
1.20.0

(3 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vstry244:30256636
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt600cf:30251589
pythontbcf:30258532

Same issue on Mac OS Big Sur (v 11.4) and VS Code 1.57.0.
The keyboard shortcut is Control + Command + Spacebar. It used to work, but stopped working after my Big Sur upgrade.
Other apps (like my browser) still allow that shortcut to show the emoji widget. 🤔

@jeff-r-koyaltech For macOS, please see https://github.com/microsoft/vscode/issues/135480#issuecomment-963946617 . If you use a laptop with a Touch Bar, then the keybinding is changed dynamically, by macOS to be the globe symbol that is displayed on the Touch Bar.

@d-e-v-esh With the steps from #135153 , I was able to reproduce something similar to what you describe also in Chrome and in Notepad, not just in VS Code. If I switch my keyboard layout to Chinese - Pinyin, open the emoji picker using win+., and press A, nothing happens. The emoji picker does not react to my pressing A. Only pressing Escape will dismiss the emoji picker. If I try the same steps with the English keyboard layout, then the emoji picker appears to filter based on A. Given this issue reproduces in all kind of other software on Windows, not just VS Code, I will close this issue as upstream.


⚠ SolarOscp has degraded performance

In 52c9dfc, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 417 ms

Resolved: SolarOscp performance has improved in ec1f100 after 10 minutes.


Some models in sct_deepseg cannot be run in standalone

There are currently tasks and models available on sct_deepseg. One task can require multiple models (e.g., seg_tumor_t2 task will use two models: findcord_tumor and t2_tumor). Some models are not standalone and raise an error when used alone (e.g. t2_tumor: see image).

Possible solutions:

To avoid confusion, models that can't be used alone could be excluded from the list of models and it would be impossible to call them.
Another option would be to call the task seg_tumor_t2 when the model t2_tumor is called. In this case, we might want to get rid of tasks and only keep models (since models and tasks can get confusing for the user).

another solution:

do not expose the "-models"