Use a Mattermost animation icon when loading a page in the app

I confirm (by marking "x" in the [ ] below):

[X] This is not a troubleshooting question. Troubleshooting questions go here: http://www.mattermost.org/troubleshoot/.
[X] This doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[X] I have read contributing guidelines.

Summary
Use a Mattermost animation icon when loading a page in the app
Steps to reproduce
Launch the app
Expected behavior
Some form of loading indicator to inform the user that the app is loading
Observed behavior

Possible fixes
We can use the attached loading animation GIF. Might need

Closed via #638


runserver and runserver_plus for local dev

Already been implemented, BUT for sandbox, we want to use Daphne as per #71


Add MIDI enumeration and event support for USB OTG host

Current codebase does not support a single USB Midi device to be plugged into Daisy's OTG host. It is the feature request to add support and integrate into the midi event handler.
Further improvement can be when Hub support added, so multiple USB Midi devices can be plugged in.

Any eta in this?

Any eta in this?

Any eta in this?

Any eta in this?

Any eta in this?

Any eta in this?

Any eta in this?

Any eta in this?

Any eta in this?

There are few things related to the MIDI parser, and adding USB MIDI Device support that are next up in the priority list before beginning to add USB Host support.
Hoping to address those in the next week or two, and then we'll be able to put some time into this.

Good.
The midi parse will support the sysex message?


kubectl completion, config current-context and version commands are too slow

What happened?
Commands kubectl completion zsh, kubectl config current-context, kubectl version and many others are too slow because they are trying to connect to the server.
This is very annoying behaviour which causes slow opening of new terminal (~0.5s with VPN and ~5s without VPN, when connection isn't possible).
I don't see any reason for those commands to connect to any server, they should just return output locally.
What did you expect to happen?
All the commands run ~0.05s, like they do without any network connection:
$ time kubectl completion zsh > /dev/null
kubectl completion zsh > /dev/null  0.05s user 0.01s system 126% cpu 0.044 total

How can we reproduce it (as minimally and precisely as possible)?
Without VPN:
$ time kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.9-dispatcher", GitCommit:"8b508a33aafcd3ba51641b6b2ef203adbdd9de1e", GitTreeState:"clean", BuildDate:"2023-12-21T23:22:51Z", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Unable to connect to the server: dial tcp 10.xxx.xxx.xxx:443: i/o timeout
kubectl version  0.05s user 0.03s system 0% cpu 35.058 total

$ time kubectl completion zsh > /dev/null
kubectl completion zsh > /dev/null  0.05s user 0.05s system 1% cpu 5.075 total

$ time kubectl config current-context
XXXXXXXXX
kubectl config current-context  0.07s user 0.03s system 1% cpu 5.078 total

With VPN connected (still annoyingly slow):
$ time kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.9-dispatcher", GitCommit:"8b508a33aafcd3ba51641b6b2ef203adbdd9de1e", GitTreeState:"clean", BuildDate:"2023-12-21T23:22:51Z", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.8-gke.1067000", GitCommit:"3936242da351c64ea89912f00faa0b28fb7eab76", GitTreeState:"clean", BuildDate:"2023-12-06T20:41:34Z", GoVersion:"go1.20.11 X:boringcrypto", Compiler:"gc", Platform:"linux/amd64"}
kubectl version  0.07s user 0.03s system 9% cpu 1.087 total

$ time kubectl completion zsh > /dev/null
kubectl completion zsh > /dev/null  0.04s user 0.03s system 16% cpu 0.414 total

$ time kubectl config current-context
XXXXXXXXX
kubectl config current-context  0.06s user 0.03s system 20% cpu 0.444 total

Anything else we need to know?
There was previous issue https://github.com/kubernetes/kubernetes/issues/82883, which was closed without resolution, also please do not mark this as feature: it's a bug because kubecli can and should run the commands for ~0.05s but run for 0.5s or even 5s.
Kubernetes version

$ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.9-dispatcher", GitCommit:"8b508a33aafcd3ba51641b6b2ef203adbdd9de1e", GitTreeState:"clean", BuildDate:"2023-12-21T23:22:51Z", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.8-gke.1067000", GitCommit:"3936242da351c64ea89912f00faa0b28fb7eab76", GitTreeState:"clean", BuildDate:"2023-12-06T20:41:34Z", GoVersion:"go1.20.11 X:boringcrypto", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider

GCP

OS version

# On Linux:
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

$ uname -a
Linux xxxxx 6.6.9-amd64 kubernetes/kubernetes#1 SMP PREEMPT_DYNAMIC Debian 6.6.9-1 (2024-01-01) x86_64 GNU/Linux

Install tools

$ apt policy kubectl
kubectl:
  Installed: 1:460.0.0-0
  Candidate: 1:460.0.0-0
  Version table:
 *** 1:460.0.0-0 500
        500 https://packages.cloud.google.com/apt cloud-sdk/main amd64 Packages
        100 /var/lib/dpkg/status

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

I'm not sure there is a completion functionality in kubectl version. For example, as you can see in kubectl annotate command, this defines the completion https://github.com/kubernetes/kubernetes/blob/eb1ae05cf040346bdb197490ef74ed929fdf60b7/staging/src/k8s.io/kubectl/pkg/cmd/annotate/annotate.go#L158. On the other hand, there isn't any for https://github.com/kubernetes/kubernetes/blob/eb1ae05cf040346bdb197490ef74ed929fdf60b7/staging/src/k8s.io/kubectl/pkg/cmd/version/version.go#L75-L91.
Have you run these commands with -v=9 to see for what reason is communication with api server?.

Unfortunately only kubectl version respects -v=9. Here is output of all the commands:
$ time kubectl version -v=9
I0119 14:18:55.658263 3484916 loader.go:373] Config loaded from file:  /home/yorik/.kube/config
I0119 14:18:55.658919 3484916 round_trippers.go:466] curl -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.27.9 (linux/amd64) kubernetes/8b508a3" 'https://10.xxxxxxxx/version?timeout=32s'
I0119 14:19:25.660146 3484916 round_trippers.go:508] HTTP Trace: Dial to tcp:10.xxxxxxxx:443 failed: dial tcp 10.xxxxxxxx:443: i/o timeout
I0119 14:19:25.660682 3484916 round_trippers.go:553] GET https://10.xxxxxxxx/version?timeout=32s  in 30001 milliseconds
I0119 14:19:25.660736 3484916 round_trippers.go:570] HTTP Statistics: DNSLookup 0 ms Dial 30001 ms TLSHandshake 0 ms Duration 30001 ms
I0119 14:19:25.660766 3484916 round_trippers.go:577] Response Headers:
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.9-dispatcher", GitCommit:"8b508a33aafcd3ba51641b6b2ef203adbdd9de1e", GitTreeState:"clean", BuildDate:"2023-12-21T23:22:51Z", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
I0119 14:19:25.661042 3484916 helpers.go:264] Connection error: Get https://10.xxxxxxxx/version?timeout=32s: dial tcp 10.xxxxxxxx:443: i/o timeout
Unable to connect to the server: dial tcp 10.xxxxxxxx:443: i/o timeout
kubectl version -v=9  0.49s user 0.09s system 1% cpu 35.075 total

$ time kubectl completion zsh -v=9                                                                                [removed completion code]
kubectl completion zsh -v=9  0.05s user 0.03s system 1% cpu 5.068 total

$ time kubectl config current-context  -v=9
I0119 14:20:30.727520 3486678 loader.go:373] Config loaded from file:  /home/yorik/.kube/config
XXXXXXXXXXXXXXX
kubectl config current-context -v=9  0.05s user 0.02s system 1% cpu 5.053 total

You can use --client flag in kubectl version to skip the server's version retrieval.

I don't think that kubectl completion has any relation with sending any requests to API server.

I think, there is some confusion. This issue is about https://github.com/kubernetes/kubernetes/issues/82883 completion functionality works slowly. Because completion relies on retrieval data from server and if the connection is slow, completion does not work performant.
On the other hand, the commands in this issue are not related to the completion;

kubectl version --client is suggested
kubectl completion just generates a completion script and no relation with server
kubectl config current-context, I haven't checked that it sends request to server but even if it requires some data from server, that would work slowly as expected if the connection is slow.

I don't see any bug or issue and I'd prefer closing this as not a bug. Thanks for spending time and effort on this.

--client doesn't help, it's still very slow:
$ time kubectl version --client -v=9                                                                                [14:47:22]
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.9-dispatcher", GitCommit:"8b508a33aafcd3ba51641b6b2ef203adbdd9de1e", GitTreeState:"clean", BuildDate:"2023-12-21T23:22:51Z", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
kubectl version --client -v=9  0.11s user 0.02s system 2% cpu 5.109 total

kubectl completion does try to connect to current context API server:
$ strace -e trace=open,openat,close,read,write,connect,accept -ff kubectl completion zsh
openat(AT_FDCWD, "/sys/kernel/mm/transparent_hugepage/hpage_pmd_size", O_RDONLY) = 3
read(3, "2097152\n", 20)                = 8
close(3)                                = 0
strace: Process 3519957 attached
strace: Process 3519958 attached
strace: Process 3519959 attached
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
strace: Process 3519960 attached
[pid 3519956] openat(AT_FDCWD, "/usr/lib/google-cloud-sdk/bin/kubectl", O_RDONLY|O_CLOEXEC) = 3
[pid 3519956] close(3)                  = 0
strace: Process 3519961 attached
strace: Process 3519962 attached
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519962] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
strace: Process 3519963 attached
strace: Process 3519964 attached
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
strace: Process 3519965 attached
[pid 3519961] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
strace: Process 3519966 attached
[pid 3519960] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519964] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519963] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519959] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519961] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519966] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519964] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
strace: Process 3519967 attached
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519961] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] openat(AT_FDCWD, "/home/yorik/.kube/config", O_RDONLY|O_CLOEXEC) = 3
[pid 3519956] read(3, "apiVersion: v1\nclusters:\n- clust"..., 36080) = 36079
[pid 3519956] read(3, "", 1)            = 0
[pid 3519956] close(3)                  = 0
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519966] write(7, "\0", 1strace: Process 3519968 attached
)         = 1
[pid 3519963] read(6, "\0", 16)         = 1
[pid 3519966] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519963] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519956] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519960] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519966] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519966] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
[pid 3519966] --- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=3519956, si_uid=1000} ---
strace: Process 3519969 attached
[pid 3519966] close(10)                 = 0
[pid 3519966] read(9, "", 8)            = 0
[pid 3519966] close(9)                  = 0
[pid 3519966] close(8)                  = 0
[pid 3519956] read(3, 0xc0005ce400, 512) = -1 EAGAIN (Resource temporarily unavailable)
[pid 3519969] openat(AT_FDCWD, "/sys/kernel/mm/transparent_hugepage/hpage_pmd_size", O_RDONLY) = 3
[pid 3519969] read(3, "2097152\n", 20)  = 8
[pid 3519969] close(3)                  = 0
strace: Process 3519970 attached
strace: Process 3519971 attached
strace: Process 3519972 attached
strace: Process 3519973 attached
[pid 3519969] openat(AT_FDCWD, "/home/yorik/.kube/gke_gcloud_auth_plugin_cache", O_RDONLY|O_CLOEXEC) = 3
[pid 3519969] read(3, "{\n    \"current_context\": \"XXXXXX"..., 512) = 360
[pid 3519969] read(3, "", 152)          = 0
[pid 3519969] close(3)                  = 0
[pid 3519969] openat(AT_FDCWD, "/home/yorik/.kube/config", O_RDONLY|O_CLOEXEC) = 3
[pid 3519969] read(3, "apiVersion: v1\nclusters:\n- clust"..., 36080) = 36079
[pid 3519969] read(3, "", 1)            = 0
[pid 3519969] close(3)                  = 0
[pid 3519969] write(1, "{\n    \"kind\": \"ExecCredential\",\n"..., 464) = 464
[pid 3519961] read(3, "{\n    \"kind\": \"ExecCredential\",\n"..., 512) = 464
[pid 3519972] +++ exited with 0 +++
[pid 3519971] +++ exited with 0 +++
[pid 3519970] +++ exited with 0 +++
[pid 3519961] read(3, 0xc000bdc1d0, 560) = -1 EAGAIN (Resource temporarily unavailable)
[pid 3519973] +++ exited with 0 +++
[pid 3519969] +++ exited with 0 +++
[pid 3519966] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3519969, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
[pid 3519961] read(3, "", 560)          = 0
[pid 3519961] close(3)                  = 0
[pid 3519961] connect(3, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("10.xxxxxxxx")}, 16) = -1 EINPROGRESS (Operation now in progress)
[pid 3519956] close(3)                  = 0
[pid 3519966] write(7, "\0", 1)         = 1
[pid 3519956] read(6, "\0", 16)         = 1
[pid 3519966] write(1, "#compdef kubectl\ncompdef _kubect"..., 42#compdef kubectl
compdef _kubectl kubectl
) = 42

To be honest, I don't care about speed of kubectl version, but there is no reason for kubectl completion and kubectl config current-context to do server request. I can't say that my connection to the server is slow (ping ~100ms), but it's still annoying.
Also even kubectl foo tries to connect to API server before returning usage error, which should never happen.
I've also found this in strace:
[pid 3529894] newfstatat(AT_FDCWD, "/usr/sbin/gke-gcloud-auth-plugin", 0xc0000aa928, 0) = -1 ENOENT (No such file or directory)
[pid 3529894] newfstatat(AT_FDCWD, "/usr/local/bin/gke-gcloud-auth-plugin", 0xc0000aaac8, 0) = -1 ENOENT (No such file or directory)
[pid 3529894] newfstatat(AT_FDCWD, "/usr/bin/gke-gcloud-auth-plugin", {st_mode=S_IFREG|0755, st_size=11243480, ...}, 0) = 0
[pid 3529894] faccessat2(AT_FDCWD, "/usr/bin/gke-gcloud-auth-plugin", X_OK, AT_EACCESS) = 0

So maybe it's /usr/bin/gke-gcloud-auth-plugin fault.

I saw in your logs about gke_gcloud_auth_plugin_cache. you may use credentials exec plugin in your kubeconfig and that plugin might be the responsible that sending a request to server or gke_gcloud_auth_plugin_cache plugin

So maybe it's /usr/bin/gke-gcloud-auth-plugin fault.

I'd not consider as a fault but perhaps this plugin sends requests for authentication, etc.

Running without the config helps:
$ time KUBECONFIG=/dev/null kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.9-dispatcher", GitCommit:"8b508a33aafcd3ba51641b6b2ef203adbdd9de1e", GitTreeState:"clean", BuildDate:"2023-12-21T23:22:51Z", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
The connection to the server localhost:8080 was refused - did you specify the right host or port?
KUBECONFIG=/dev/null kubectl version  0.03s user 0.02s system 128% cpu 0.042 total

I have something like this in my config:
users:
- name: gke_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args: null
      command: gke-gcloud-auth-plugin
      env: null
      installHint: Install gke-gcloud-auth-plugin for use with kubectl by following
        https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke
      interactiveMode: IfAvailable
      provideClusterInfo: true

But my main point that for commands which can be processed locally kubectl should not open any connections.
I've run gke-gcloud-auth-plugin separately and it doesn't connect to API server itself, but makes kubectl to connect.
I can "fix" kubectl completion zsh with KUBECONFIG=/dev/null, but kubectl config current-context (which is called from kubectx) is still annoyingly and without out a reason too slow.
Just in case:
$ gke-gcloud-auth-plugin --version                                                                                Kubernetes v1.28.2-alpha+58ec6ae34b7dcd9699b37986ccb12b3bbac88f00

I've tried to downgrade to kubectl package version 1:459.0.0-0, but it has the same version of the binary:
Client Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.9-dispatcher", GitCommit:"8b508a33aafcd3ba51641b6b2ef203adbdd9de1e", GitTreeState:"clean", BuildDate:"2023-12-21T23:22:51Z", GoVersion:"go1.20.12", Compiler:"gc", Platform:"linux/amd64"}

I'll try to build kubectl from the repo and test it during weekend.

If kubectl completion or kubectl version --client or any other command that has a --local flag whose are designed not to send request to api server sends a request to api server when kubeconfig has a credentials exec plugin, I think that is a bug.

I've tested it with kubectl built from https://github.com/kubernetes/kubernetes at 2d4100335e4c4ccc28f96fac78153f378212da4c and I wasn't able to reproduce the problem.
Also I wasn't able to find git commit 8b508a33aafcd3ba51641b6b2ef203adbdd9de1e in the repo from kubectl version installed from https://packages.cloud.google.com/apt, so maybe there are some google's patches added.

Not only kubectl completion, config current-context and version, but also kubectl get pod, kubectl get node and kubectl describe.  This problem will not appear when I use<EMAIL_ADDRESS>but it will appear switch kubectl into v1.29.1.
bytefly@ByteFlys-MBP ~ % kubectl version
Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.1
bytefly@ByteFlys-MBP ~ % time kubectl version
Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.1
kubectl version  0.04s user 0.02s system 1% cpu 5.083 total
bytefly@ByteFlys-MBP ~ % time kubectl get pod
No resources found in default namespace.
kubectl get pod  0.06s user 0.02s system 1% cpu 5.092 total
bytefly@ByteFlys-MBP ~ % time kubectl get node
NAME             STATUS   ROLES           AGE    VERSION
docker-desktop   Ready    control-plane   167m   v1.29.1
kubectl get node  0.06s user 0.02s system 1% cpu 5.087 total
bytefly@ByteFlys-MBP ~ %
bytefly@ByteFlys-MBP ~ %
bytefly@ByteFlys-MBP ~ %
bytefly@ByteFlys-MBP ~ % cd go/bin
bytefly@ByteFlys-MBP bin % time ./kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.5", GitCommit:"c285e781331a3785a7f436042c65c5641ce8a9e9", GitTreeState:"clean", BuildDate:"2022-03-16T15:58:47Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"darwin/arm64"}
Server Version: version.Info{Major:"1", Minor:"29", GitVersion:"v1.29.1", GitCommit:"bc401b91f2782410b3fb3f9acf43a995c4de90d2", GitTreeState:"clean", BuildDate:"2024-01-17T15:41:12Z", GoVersion:"go1.21.6", Compiler:"gc", Platform:"linux/arm64"}
WARNING: version difference between client (1.23) and server (1.29) exceeds the supported minor version skew of +/-1
./kubectl version  0.04s user 0.02s system 73% cpu 0.081 total
bytefly@ByteFlys-MBP bin % time ./kubectl get pod
No resources found in default namespace.
./kubectl get pod  0.07s user 0.06s system 34% cpu 0.353 total
bytefly@ByteFlys-MBP bin % time ./kubectl get node
NAME             STATUS   ROLES           AGE    VERSION
docker-desktop   Ready    control-plane   170m   v1.29.1
./kubectl get node  0.05s user 0.02s system 84% cpu 0.078 total
bytefly@ByteFlys-MBP bin %

/remove-lifecycle rotten

I have same behavior.
Each time than the current cluster where I am "configured" is not available (private one, removed, ..) there is a 5 sec delay on any command with kubectl.
Checking the network traffic I can see there is some tcp resync during this period :

even for some local one like the version  --client or get-current-context which should not initiate server connection.
even if connection is normal, we should have some way to custom this "5s timeout" I think.

Same here with gcloud config, if I remove the kubectl it's fast again. Agree that some commands should never make a connection like the zsh completion generation.


No option to add or create a new workshop

Summary:
/workshop view should have an option to add a new workshop. This should be visible for only an Admin. There is an existing URL /workshop/create which seems to throw an error.
GIF/Screenshots:

Assigned to Raghvendra Vijaya

Assigned to Shobitha


KAFKA-13461: Don't re-initialize ZK client session after auth failure if connection still alive

If JAAS configuration does not contain a Client section for ZK clients, an auth failure event is generated. If this occurs after the connection is setup in the controller, we schedule reinitialize(), which causes controller to resign. In the case where SASL is not mandatory and the connection is alive, controller maintains the current session and doesn't register its watchers, leaving it in a bad state.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@junrao Thanks for the review, merging to trunk, 3.1 and 3.0


Handle primitive REPEATED field not contained in LIST annotated group

Which issue does this PR close?
Closes #6648
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

@tustvold / @etseidl
Can anyone merge my test file PR so the new UT I added to this PR can pass?

@tustvold / @etseidl  How do I trigger the checks again without commiting new changes? The test file I added is not merged into parquet-testing so the new UT should pass now

I lack permissions. Perhaps @alamb  can kick off the tests again.

@tustvold / @etseidl My new test file is merged into parquet-testing, my local branch runs the UT successfully, but the CI fails on the UT not finding the file, any ideas why that is?
Is there some step required after commiting a new test file to update the test environment?

@zeevm I admit to not being an expert here. Looking at the error logs, CI is pulling an older commit. Pure speculation, but based on this I wonder if you need to do git submodule update --remote in your branch, create a new commit and push it. That may cause CI to pick up the recent changes.
Anyone with more git/github/workflow knowledge please chime in if I'm just embarrassing myself here 😅

@etseidl you suggestion works, and the UT now passes, can you merge?

can you merge?

I'm afraid I cannot as I'm not a committer. I know committer bandwidth is very constrained at the moment, so it may take little while.

@tustvold is this good for merge?

Yes, I plan to merge this PR tomorrow unless there are any more comments

🚀

Thanks again @zeevm  and @etseidl

Sorry for the late reply. I'm not sure whether we should fix reading or totally prohibit writing repeated primitive fields without LIST annotation as a list type. This is a gray area from the spec and should be discussed prior to the fix. The file added to parquet-testing is for interoperability across parquet implementations to have the same behavior. I have opened https://github.com/apache/parquet-format/pull/466 to clarify it.

Sorry for the late reply. I'm not sure whether we should fix reading or totally prohibit writing repeated primitive fields without LIST annotation as a list type. This is a gray area from the spec and should be discussed prior to the fix. The file added to parquet-testing is for interoperability across parquet implementations to have the same behavior. I have opened apache/parquet-format#466 to clarify it.

Than you @wgtmac -- given there are parquet files (such as what is in parquet-format) that do have this structure, I think supporting reads makes sense. If we decide it would be good to prohibit writers fro writing such files that sounds like a good follow on to me, but it still adds value to parquet-rs to read such files from my perspective.


Access message metadata in a scheduled message

Is it possible to obtain metadata in client.chat.scheduledMessages.list()?
I am successfully scheduling a message with some metadata. However, when I retrieve the scheduled messages I don't get the metadata. Only a list of messages like so:
{
      id: 'Q05EGQVAJ64',
      channel_id: 'C05A988M6UD',
      post_at:<PHONE_NUMBER>,
      date_created:<PHONE_NUMBER>,
      text: 'Have you had your nano-connection yet?'
    }

Reproducible in:
The Slack SDK version
"slack/bolt": "^3.12.1",
Node.js runtime version
v16.18.1
OS info
ProductName:            macOS
ProductVersion:         13.3.1
BuildVersion:           22E261
Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
Steps to reproduce:
(Share the commands to run, source code, and project settings)

Expected result:
(Tell what you expected to happen)
Actual result:
(Tell what actually happened with logs, screenshots)
Requirements
For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. :bow:
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @guillewu thanks for writing in 💯
You are correct there does not seem to be a way to retrieve the metadata of scheduledMessages until they are posted, once the are posted you should be able to use conversation.list to find the message

@WilliamBergamin thanks for the quick response.
Would it be possible to request this feature? It'd be quite useful to filter out scheduled messages to delete. Right now as a hack I'm filtering the messages with the text parameter and adding a lot of extra space to hide the data so it doesn't show in the notification.. but that's probably not the cleanest solution.
{
      id: 'Q05EGQVAJ64',
      channel_id: 'C05A988M6UD',
      post_at:<PHONE_NUMBER>,
      date_created:<PHONE_NUMBER>,
      text: `Have you had your nano-connection yet?                                                                      someId: 123abc`
    }

Since this feature is at the API level and not just bolt-js specific, you should be able to use the /feedback command to submit a request for it
I was not able to figure out a cleaner work around either


Enhancement: Code block styling

The defaults from mintlify don't match our branding super well. This PR adds a bespoke stylesheet mapped from the prefect.io hljs theme to fit a bit better.

Before
After


Utilize speaker full name

Current dependencies on/for this PR:

main

PR #21   👈

This stack of pull requests is managed by Graphite.


[next] Portal children removed after recreation of PortalTarget

Hi, I ran into a problem where when the state that controls the conditional rendering of the PortalTarget is changed, the portal child is destroyed, but the portal is preserved and the child is not recreated.

I created a demo, just double click the change camera button and you can see that the light under the camera is missing.
It worked well with older versions of Threlte.
{#if perspective_camera}
  <T.PerspectiveCamera
    position={[10, 10, 10]}
    makeDefault
    fov={30}
  >
    <OrbitControls enableZoom={false} />
    <PortalTarget id="light" />
  </T.PerspectiveCamera>
{:else}
<T.PerspectiveCamera
  position={[100, 10, 10]}
  makeDefault
  fov={60}
>
  <OrbitControls enableZoom={false} />
  <PortalTarget id="light" />
</T.PerspectiveCamera>
{/if}

Link to live example - https://stackblitz.com/edit/vitejs-vite-frwawdb1?file=src%2Fexample%2FScene.svelte&terminal=dev
I think there is some desynchronisation with the destructor of portal/portalTarget in Svelte 5.

I think here, for the time being, i'd go with using the "attach" prop that exists on  components. https://next.threlte.xyz/docs/reference/core/t#attach.
i forked your example and simplified it a little to use the attach prop. https://stackblitz.com/edit/vitejs-vite-rgvjh4cg?file=src%2Fexample%2FScene.svelte
essentially the attach is saying "i want you to attach to whatever is the camera store. it's reactive so updating the default camera causes the light helper to detach and attach as needed.
I've found that most of the time, you can use the attach prop for simple portaling like this. Not sure the future of the <Portal> and ` components.

i made an issue about obsoleting these components https://github.com/threlte/threlte/issues/1285. i don't know if we had plans to do that but it feels like the everything they can do right now is also doable with attach.


Unable to see Netlify Build logs for pull requests

This is a Bug Report

Problem:
I can't see logs from this neltfiy hugo build at link https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/6594a8398c43840008a4b062 It just says "You do not have permissions to view logs for this resource".
For any PR i can't see the logs!!!
It might be some new setting for PR that I don't know but i think for old PRs I saw the logs and it was useful for seeing failures. Maybe something is changed now to restrcit access.
Proposed Solution:
The build logs should be made visible to see the errors or log message when change in pull request is build.

/area web-development

@steve-hardman - Have you logged in to Netlify with your GitHub a/c to see the logs? Could you please paste a screencap of what you see when trying to view it after logging in with the a/c?

You need to be a Netlify user in our organization to see the build logs. As far as I know, we don't have an easy way to change that.
We could look at building a complicated way, but:

you can build any branch locally (and documenting how to do that is way easier)
we don't really have a good use case for it IMO, especially given the effort and extra costs it would involve

Tangentially:
/sig testing

(I wonder if Netlify changed a setting about default visibility)

I've observed a similar behavior over the past few weeks. However, as of today (at the time of writing this comment), it seems like the issue has been resolved, and the Deploy Preview logs are once again visible. This could have been due to an intermittent Netlify glitch or perhaps someone has restored the deploy log visibility to public logs in the build settings, as it was before.
@steve-hardman, could you kindly confirm whether the issue still persists for you? It looks like things are back to normal.

Clsoing this issue as resolved. Thanks for help with this.


When Camera is  enabled, the ParallaxLayer/Tilemap Physics Layer is calculated inaccurately using is_on_floor()

Tested versions
v4.3.dev3.official [36e943b6b]
System information
Linux Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8
Issue description
The is_floor() function reports incorrectly (or is off) when being applied to a ParallaxLayer Tilemap and a Player with Camera enabled. If camera is disabled, then is_floor() works correctly.
Steps to reproduce
Create a CharacterBody2D Player with a camera. Also create a ParallaxLayer and a TileMap floor with a physics layer collider.  When the Player drops to the floor it will not stop at the floor but somewhere else depending on the ParalaxLayers position.
Project

Camera Enabled

Camera Disabled

Minimal reproduction project (MRP)
Archive.zip

Hi I'm new here and would like to work on this.

shot im doin it

@josesantoscorte You should read these guidelines. https://docs.godotengine.org/en/stable/contributing/workflow/index.html

Hi I'm new here and would like to work on this.


Make neato sensor

The commit aaf95100406138966a8dc1d3eb53f7392bab912a should be working nicely, however, I can't get the neato state to update via websocket to dashboard without refreshing the whole page in the browser.
Commit 7717eaa2f988b759b837cd0f8afdd8858f598415 has a suggestion on how to poll for the robot state in a smarter way without constantly spamming beehive.

let's move this into a separate project!
do you want to take the initiative or shall I? 😃

If I can steal your mqtt boilerplate code I can then move more of the neato api stuff into a new project 👌

Yess go ahead, the boilerplate is worth something now too when it's able to function after reconnects 🤪

This should be working now https://github.com/Pingviinituutti/neato-mqtt


'module' object has no attribute 'signal'

Now I'm working on two machines; one iMac and the other on linux server.
iMac: MacOsX, python 2.7.6. theano 0.7.0, keras installed with sudo pip.
server: python 2.7.10 Anaconda, theano 0.6.0, keras was cloned with local folder with sys.path.append(''), then I tested after install it by python setup.py install --user.
Symptoms: keras throws an error for my code, cifar10_cnn and mnist_cnn examples while all of them works well on my iMac.
---before re-install---
File "/home1/irteam/users/keunwoo/learning_audio.py", line 55, in buildConvNetModel
model.compile(loss='categorical_crossentropy', optimizer=sgd)
File "build/bdist.linux-x86_64/egg/keras/models.py", line 287, in compile
File "build/bdist.linux-x86_64/egg/keras/layers/containers.py", line 51, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 223, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 356, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 198, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 356, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 198, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 356, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 277, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 198, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/convolutional.py", line 167, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 198, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/convolutional.py", line 210, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/convolutional.py", line 167, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 198, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/convolutional.py", line 210, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/convolutional.py", line 167, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/convolutional.py", line 211, in get_output
TypeError: max_pool_2d() got an unexpected keyword argument 'st'
---now---
File "mnist_cnn.py", line 59, in
model.compile(loss='categorical_crossentropy', optimizer='adadelta')
File "build/bdist.linux-x86_64/egg/keras/models.py", line 351, in compile
File "build/bdist.linux-x86_64/egg/keras/layers/containers.py", line 53, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 257, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 392, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 232, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 257, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 392, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 313, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 232, in get_output
File "build/bdist.linux-x86_64/egg/keras/layers/core.py", line 31, in get_input
File "build/bdist.linux-x86_64/egg/keras/layers/convolutional.py", line 210, in get_output
AttributeError: 'module' object has no attribute 'signal'
The messages are the same for all three codes.
It could be problem on the way I installed keras, theano version, or even python version, or something else that I can't imagine. Sadly I'm not allowed to use sudo on the server, now I'm going to try on virtualenv. I'd appreciate any comments!

Upgrade Theano to its latest version.

I had the same issue with Theano 0.7 version. I added:
import theano.tensor.signal.conv
from theano.tensor.signal import downsample
to convolutional.py and it solved the problem.

@michael-ermolenko It solved my problem, thanks.

I had the same two problems after I installed keras by cloning. sudo pip install keras --upgrade solves the "TypeError: max_pool_2d() got an unexpected keyword argument 'st'" problem and @michael-ermolenko 's answer solves the "AttributeError: 'module' object has no attribute 'signal'" problem. Maybe making a PR with this solution would help?

+1 for PR with @michael-ermolenko 's solution

+2 for PR with @michael-ermolenko's solution - worked like a charm.

@michael-ermolenko <-- your solution solved the problem. :)


Update from View.propTypes to ViewPropTypes to match RN v0.44.0

Update the ViewPropTypes to match the last revision of React Native V0.44.0

View.propTypes to ViewPropTypes (53905a5) - @bvaughn

https://github.com/facebook/react-native/releases

The update of the package.json is a buffer. I made a pull request for the react-native-windows package for the same reason.

Would be fantastic if this could please be merged. As View.propTypes is deprecated and will be removed very soon.

This is a really simple pull request people, would love this to get merged.

Any updates on this PR?

This brakes on RN 0.49 and above now, since it's now React 16 beta.5, so this warning is now a fatal error...
Is this repo a bit "dead" for quite some time in general?

@asgvard Yes, the PR you mentioned fixes the problem. Update your package.json like this:
 "react-native-video": "git://github.com/react-native-community/react-native-video.git#master",
@mattapperson This PR can be closed.

This has been addressed by #824


Add last opened time

Add last request time metric for each subject which will denote when the app was last opened since the notification requests are sent whenever the app is opened.

This can also probably be sent to KAFKA as an event log


"Translator is missing window functions" warning on filter

I'm getting a bit of an overactive warning message from using a filter in sparklyr.  I imagine this might actually be closer to a d(b)plyr/DBI problem.
Could any advice be offered about squashing these? Apologies if this issue is in the wrong repo.
Thanks,
Akhil
> library(sparklyr)
> library(dplyr)
>
> sc = spark_connect(master = 'local', spark_home=spark_home_dir())
> iris_tbl <- copy_to(sc, iris)
> iris_tbl %>% filter(Species == "setosa")
# Source:   lazy query [?? x 5]
# Database: spark_connection
   Sepal_Length Sepal_Width Petal_Length Petal_Width Species
          <dbl>       <dbl>        <dbl>       <dbl>   <chr>
 1          5.1         3.5          1.4         0.2  setosa
 2          4.9         3.0          1.4         0.2  setosa
 3          4.7         3.2          1.3         0.2  setosa
 4          4.6         3.1          1.5         0.2  setosa
 5          5.0         3.6          1.4         0.2  setosa
 6          5.4         3.9          1.7         0.4  setosa
 7          4.6         3.4          1.4         0.3  setosa
 8          5.0         3.4          1.5         0.2  setosa
 9          4.4         2.9          1.4         0.2  setosa
10          4.9         3.1          1.5         0.1  setosa
# ... with 40 more rows
Warning messages:
1: Translator is missing window functions:
count, n_distinct
2: Translator is missing window functions:
count, n_distinct
3: Translator is missing window functions:
count, n_distinct
4: Translator is missing window functions:
count, n_distinct

Session Info
> sessionInfo()
R version 3.4.0 (2017-04-21)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Debian GNU/Linux 9 (stretch)

Matrix products: default
BLAS/LAPACK: /usr/lib/libopenblasp-r0.2.19.so

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C
 [3] LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8
 [5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=C
 [7] LC_PAPER=en_US.UTF-8       LC_NAME=C
 [9] LC_ADDRESS=C               LC_TELEPHONE=C
[11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
[1] dplyr_0.7.1         sparklyr_0.5.6-9008

loaded via a namespace (and not attached):
 [1] Rcpp_0.12.11     dbplyr_1.1.0     compiler_3.4.0   git2r_0.18.0
 [5] plyr_1.8.4       bindr_0.1        base64enc_0.1-3  tools_3.4.0
 [9] digest_0.6.12    jsonlite_1.5     memoise_1.1.0    tibble_1.3.3
[13] nlme_3.1-131     lattice_0.20-35  pkgconfig_2.0.1  rlang_0.1.1
[17] psych_1.7.5      shiny_1.0.3      DBI_0.7          rstudioapi_0.6
[21] yaml_2.1.14      curl_2.6         parallel_3.4.0   bindrcpp_0.2
[25] stringr_1.2.0    withr_1.0.2      httr_1.2.1       knitr_1.16
[29] rappdirs_0.3.1   devtools_1.13.2  rprojroot_1.2    grid_3.4.0
[33] glue_1.1.1       R6_2.2.2         foreign_0.8-69   tidyr_0.6.3
[37] reshape2_1.4.2   magrittr_1.5     backports_1.1.0  htmltools_0.3.6
[41] assertthat_0.2.0 mnormt_1.5-5     mime_0.5         xtable_1.8-2
[45] httpuv_1.3.3     config_0.2       stringi_1.1.5    lazyeval_0.2.0
[49] broom_0.4.2

I opened a similar question in tidyverse/dplyr#2926 in case this is the wrong place - Feel free to close if so.

Yeah this is an issue on the sparklyr side; we need a corresponding window translation for each function listed under aggregate. You can close the dbplyr issue.

Thanks, have done.


Unable to stop recompile the app Flutter drive/test cmd with iOS simulator

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Build the app with flutter run
Try to run with flutter test or flutter drive --use-existing-app={{url}}
with flutter test, the installed app get to rebuild/reinstall again
And for flutter driver, getting error and the app goes into white screen

Actual results

with flutter test, the installed app get to rebuild/reinstall again
And for flutter driver, getting error and the app goes into white screen

Logs

Logs

<!-- Paste your logs here -->

Flutter Doctor output

Doctor output

<!-- Paste your output here -->
Flutter 3.10.6
Android SDK-34
JAVA-17.0.6
Xcode - 14.3.1
CocoaPods 1.12.1
Android studio- 2022.3

@darshankawar For now I am just building for iOS
CMD-
flutter drive --use-existing-app=http://<IP_ADDRESS>:55547/NXiTEM3Ud2Q\=/\#/vm --driver=test_driver/integration_test_driver.dart --target=integration_test/login_test.dart --timeout=360

Some error log
VMServiceFlutterDriver: Connecting to Flutter application at http://<IP_ADDRESS>:55547/NXiTEM3Ud2Q=/#/vm
VMServiceFlutterDriver: Isolate found with number:<PHONE_NUMBER>155099
VMServiceFlutterDriver: Isolate is not paused. Assuming application is ready.

 Or what is the difference, I know that there is page on flutter home page that about the migration.

@ckxddd0324
flutter test command is part of the test framework itself and using it leverages the test widgets and methods that comes along with the test framework. In order to use flutter drive, it was not possible to read the properties and states of the test widgets. Hence, it is now migrated to flutter test integration_test.


Script error in installation

Running the install scripts I get the following error:

cloud-native-starter$ scripts/deploy-web-api-java-jee.sh
scripts/deploy-web-api-java-jee.sh: 8: scripts/deploy-web-api-java-jee.sh: Syntax error: "(" unexpected

on an Ubuntu 16.04 host

I guess it's about replacing "sh" with "bash" in the shebang line

Thanks for creating the issues @fachat. @Harald-U will return tomorrow and take a look at the Linux related ones.

@fachat You are right, it is the shebang "#!/bin/sh". Interstingly, it does work on Fedora. I replaced all occurences. Thnaks for pointing it out!!!


Package overhaul

Fixes https://github.com/LM-SAL/aiapy/issues/117
Fixes https://github.com/LM-SAL/aiapy/issues/315
TODO:

[x] Changelog for the min python change to 3.9
[x] Mention removal of setup and need of modern pip for this to work.
[x] Mention the use of * in some functions now
[x] Fix CI

I noticed that RTD is still not triggering on this PR.

I noticed that RTD is not reporting its build status back to this PR. Is that just because there hasn't been a push since it was configured for this repo?

closed and reopened, both it and codecov are now live

That RTD build is just spinning: Here is the older one https://aiapy--313.org.readthedocs.build/en/313/ with the same content.

Doc changes removed.


Bug: RPC not working with anyio <4.0

Describe the bug
I'm currently using faststream with anyio==3.7.1 and python3.10.10 which both seems to meet the requirements.
When publishing with rpc=True, I encounter this error:
File "/***/python3.10/site-packages/faststream/rabbit/publisher/producer.py", line 209, in __aenter__
    ) = anyio.create_memory_object_stream[AbstractIncomingMessage](
TypeError: 'function' object is not subscriptable

From my understanding of their docs bracket notation wasn't introduced until v4.0. (above this version works as expected)
How to reproduce
send.py
import asyncio
from faststream.rabbit import RabbitBroker, RabbitExchange, RabbitQueue

exchange = RabbitExchange('ai')
queue = RabbitQueue('test')
broker = RabbitBroker()

async def t():
    await broker.connect()
    await send(1, broker)

async def send(num, broker):
    out = await broker.publish(num, queue=queue, exchange=exchange, rpc=True)
    print(out)

asyncio.run(t())

app.py
import asyncio

from faststream import FastStream, Logger
from faststream.rabbit import RabbitBroker, RabbitExchange, RabbitQueue

broker = RabbitBroker()
app = FastStream(broker)

exchange = RabbitExchange('ai')
queue = RabbitQueue('test')

@broker.subscriber(queue=queue, exchange=exchange)
async def handler(msg, logger: Logger):
    logger.info(msg)
    return msg

Environment
Running FastStream 0.5.12 with CPython 3.10.10 on Darwin

Thank your for the Issue! I'll fix it soon


Add check for socket file permissions

Return error when the systemd created socket file has wrong permissions.

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.
Commands are simple Github comments of the format: "jenkins: COMMAND"

This one is involved, as it also needs a fix for #1307, but I got a bit lost to where to send a PR for that fix.

I don't think we want this fix. Folks should be able to change their systemd unit to use a different mode on their socket. Fixing the systemd unit is the right fix for this.


Update revolt.js

New update was published and there are a few changes that need to be addressed

Rough update and testing done - problems may occur if I didn't find it

No bugs have been encountered for the current beta version of rjs v7
might be reopened later when new versions get published


WaitForADDomain: Adds optional parameter IgnoreAuthenticationErrors

Pull Request (PR) description

Changes to WaitForADDomain

An optional parameter IgnoreAuthenticationErrors can be set to $true
to tell the resource to ignore authentication errors (issue #478).

This Pull Request (PR) fixes the following issues

Fixes #478

Task list

[x] Added an entry under the Unreleased section in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in resource directory README.md.
[x] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[x] Conceptual help topic added/updated (cultureFolder\about_ResourceName.help.txt).
[x] Localization strings added/updated in all localization files as appropriate.
[x] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #481 into dev will increase coverage by <1%.
The diff coverage is 100%.

@@         Coverage Diff          @@
##            dev   #481    +/-   ##
====================================
+ Coverage    98%    98%   +<1%
====================================
  Files        23     23
  Lines      3007   3023    +16
  Branches     10     10
====================================
+ Hits       2958   2974    +16
  Misses       39     39
  Partials     10     10

Hi @johlju. This functionality will be very useful, but I think a different parameter name would be more useful, such as something like WaitForADUser. This would give a better idea of its intended usage.

@X-Guardian Happy to change to another name, but it actually ignores authentication errors, it does not wait for a user. My thought was that using IgnoreAuthenticationErrors make the user opt-in to potential problems with the provided credential even when the domain is available (but the credentials cannot be used to check that the domain is available). Using the WaitForADUser could indicate that the resource is some logic to wait for the correct user to be created and if it is not for a certain of amount of time it will report that it could not be found even if the domain is available which is not possible since we might not have the correct credentials to do that check in the first place. 🤔
What are your thoughts around this? I thought the opt-in was important in this case. The description for the parameter IgnoreAuthenticationErrors is currently

Specifies that the resource will not throw an error if authentication fails using the provided credentials and continue wait for the timeout. This can be used if the credentials are known to eventually exist but there are a potential timing issue before they are accessible.

Yes, I'm fine with the opt-in, and the description of the parameter. Totally makes sense. If you opt-in though, what the user is wanting to achieve is to wait until the credentials that have been specified are valid, or timeout with an error. Within the module, that is achieved by continuing to wait even if the domain controller responds with an authentication exception, but I feel that for the user, IgnoreAuthenticationErrors as a parameter isn't informative of its usage.

How about something like WaitForCredentialValidation?

I like WaitForCredentialValidation better, but the word 'validation' still sound a bit towards something the resource have no logic for, but what about WaitForCredentialToExist, or WaitForValidCredentials?

WaitForValidCredentials looks good to me.


Failed to ingest events

Failed to ingest events .catch() Failed to fetch
Machine ID: 3922cd78-830b-496c-aa98-ad85124df704

[!NOTE]
Book a call

key
value

id
kaxBkqRAQBQ9dmV1amXs8

url

wifi
4g

cpu
8

mem
8

gpu
ANGLE (Apple, ANGLE Metal Renderer: Apple M1 Pro, Unspecified Version)

time
1722864426934

items
0

bytes
0

Hi @snigdha920 , we've just deployed a fix for you. Can you try running the setup script npx million@latest. Once it's done, please restart your VSCode/Cursor. Let me know if that works for you!


gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/os.js/node_modules/node-sass/build'

NPM version (npm -v):
Node version (node -v): 10.14.1
Node Process (node -p process.versions):
Node Platform (node -p process.platform): linux
Node architecture (node -p process.arch): amd64
node-sass version (node -p "require('node-sass').info"):
npm node-sass versions (npm ls node-sass): whatever one os.js uses

I was installing this as root with --unsafe-perm=true --allow-root because I'm installing this in a chroot.
gyp verb download contents checksum {"node-v11.3.0-headers.tar.gz":"ec21aa45c8790e3ab8df531f760458222237a3b8fe61aeef0532d7a11d0aa2bd"}
gyp verb validating download checksum for node-v11.3.0-headers.tar.gz (ec21aa45c8790e3ab8df531f760458222237a3b8fe61aeef0532d7a11d0aa2bd == ec21aa45c8790e3ab8df531f760458222237a3b8fe61aeef0532d7a11d0aa2bd)
gyp verb get node dir target node version installed: 11.3.0
gyp verb build dir attempting to create "build" dir: /opt/os.js/node_modules/node-sass/build
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/os.js/node_modules/node-sass/build'
gyp ERR! System Linux 4.19.4-arch1-1-ARCH
gyp ERR! command "/usr/bin/node" "/opt/os.js/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /opt/os.js/node_modules/node-sass
gyp ERR! node -v v11.3.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-12-09T03_49_39_632Z-debug.log

try npm install --unsafe-perm

already did

The log say v11.3.0 rather than 10.14.1. Sorry, but we're not going to be able to troubleshoot an issue with os.js, I suggest you file an issue over there or on SO.

already did

Hi. I am having the same problem. Did you find any answer??

No fix has been found.

i solved, these are the scripts to run as root user.
$ rm -rf node_modules/ package-log.json
$ npm cache clean --force
$ npm install node-sass --unsafe-perm
$ npm install --unsafe-perm

Yeah but this is being done on a fresh directory/package


The FormStrategy constructor doesn't accept any arguments.

It looks like the constructor is broken in the v1.5.0 version.
Expected 0 arguments, but got 1.ts(2554)

The constructor seems to be missing in index..d.ts
import { AppLoadContext, SessionStorage } from "@remix-run/server-runtime";
import { AuthenticateOptions, Strategy } from "remix-auth";
export interface FormStrategyVerifyParams {
    /**
     * A FormData object with the content of the form used to trigger the
     * authentication.
     *
     * Here you can read any input value using the FormData API.
     */
    form: FormData;
    /**
     * An object of arbitrary for route loaders and actions provided by the
     * server's `getLoadContext()` function.
     */
    context?: AppLoadContext;
    /**
     * The request that triggered the authentication.
     */
    request: Request;
}
export declare class FormStrategy<User> extends Strategy<User, FormStrategyVerifyParams> {
    name: string;
    authenticate(request: Request, sessionStorage: SessionStorage, options: AuthenticateOptions): Promise<User>;
    private readFormData;
}

The constructor is not needed because FormStrategy uses the same one used by Strategy class from Remix Auth, that's why it's not in the type.
The tests of the packages shows TS doesn't complain against the constructor argument, even when importing from the built files instead of the source files.
If you can, try to create a reproduction repo with this TS issue.


Add non-upgradeable version of ERC-3525

This PR adds a non-upgradeable version of ERC-3525 for those that want it. A separate set of tests run on this non-upgradeable version to ensure full compatibility with the existing token mechanics.
It also adds NatSpec support for inherited functions and adds a remappings.txt file to get Go to definition working on imported files in vscode.

Thank you for your work.
It's better to transpiling non-upgradeable contracts to upgradeable contracts by scripts.
The release v1.1.0 includes non-upgradeable and upgradeable contracts in this way.


Add LibreTranslate template

Changes

Add LibreTranslate template

I have tested this service and it seems to work properly. Thanks for your PR 💜.


WebSocket port cannot be set to 80/443

livereload.js decides which WebSocket port to use by examining the src attribute of its script element (see options.coffee). So if I load livereload.js on port 1234 then the WebSocket connection will use port 1234, too:
<script src="http://localhost:1234/livereload.js"></script>

Unfortunately, this does not work when using the standard HTTP/HTTPS 80/443 ports because browsers strip the default ports 80/443 from the script element's src attribute such that livereload.js does not see them (tested in Chrome 35 and Firefox 30). Therefore all three following embed methods use the fallback port 35729 instead of 80 or 443:
<script src="https://localhost:443/livereload.js?snipver=1"></script>
<script src="http://localhost:80/livereload.js?snipver=1"></script>
<script src="/livereload.js?snipver=1"></script>

I've setup livereload behind an nginx proxy on port 80/443 for two reasons:

Only ports 80/443 are needed and not port 35729 (firewall, port forwarding, ...).
I do not have to configure SSL/HTTPS in tiny-lr because SSL/HTTPS is already configured in nginx.

At the moment I've patched the livereload.js file to use the fallback port 80/443 instead of 35729 (see https://github.com/mklabs/tiny-lr/pull/45). But this may break existing setups. How can this be solved in a clean way? Maybe a new "keep-port=1" URL parameter?

Exactly the same issue on Hugo v0.55.0-DEV.

Please report this to the Hugo project. As the solution described above has been applied previously.


After pasting, focus all pasted files/folders instead of just one

Resolved / Related Issues
Fixes #8333
Details of Changes
Validation
How did you test these changes?

[x] Built and ran the app

Before:
https://user-images.githubusercontent.com/25117425/171063890-7f921d9c-7468-466e-80b1-3b69584bf49e.mp4
After:
https://user-images.githubusercontent.com/25117425/171063899-223eb360-da14-43b5-9dd4-38164e631681.mp4

@IgorKordiukiewicz thank you for the pr, can you check the validation check box in the PR description?

@IgorKordiukiewicz thank you for the pr, can you check the validation check box in the PR description?

Updated

Well, it kind of gets reset every time the ProcessOperationQueue is called sine its created there, so I don't think this will be a problem and I didn't notice this bug happening.

I believe this introduces a bug where future pastes will focus on the previous ones since we never reset the itemsAdded list. This may be a little tricky to fix since we flatten out multi-paste operations into sequential ones.

I didn't notice this bug happening during testing, are you able to provide steps?

Sure, a way to reproduce is to copy and paste some files, and then in the same directory, copy and paste some other files. You'll see the previous paste will be included as well. I've prepared a gif that demonstrates this issue.

Ah thank you. I was misunderstanding the method to replicate.


Allow to compile on Raspbian GNU/Linux 8.0 (jessie)

Hi Nenad,
This Pull Request allows to compile piHomeEasy on Raspbian GNU/Linux 8.0 (jessie).
Best regards,
CYOSP

Nenad,
I've also updated your great job with makefile usage.
Best regards,
CYOSP

Thanks CYOSP


fixthe common type of decimalv2 and decimalv3 shoud be decimalv3 in BinaryArithmetic operator

the common type of decimalv2 and decimalv3 shoud be decimalv3 in BinaryArithmetic operator
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall


new installation

Hi Sjoerd.
It is nice and useful that you write how to use it in case of an upgrade. But how do we start a new one?
Thank You
Jan

Hi Jan,
It's described here: https://github.com/sjoerdmulder/teamcity-docker#how-to-use-this-image-with-postgres


Video rotation issue

I'm using this to reduce the size of my Dropbox uploads folder. I have some iPhone videos there, and for some of them this is great, but portrait videos are being rotated to landscape, and some landscape videos are turned upside down. Is there any parameter to avoid this from happening?
Thanks for this scripts, they are very useful

Thanks and you are very welcome. I'm glad the scripts are useful to you.
The problem you're seeing is caused by missing metadata, specifically matrix rotation information to compensate for how you were holding your iPhone when you shot the video. HandBrake does not copy this metadata during transcoding so you're videos are sometimes strangely oriented.
If you don't want to re-transcode your videos, you can use a tool like "Video Rotate" (in "fast" mode) to apply the rotation metadata after the fact. Keep in mind that not many non-Apple software or hardware players will honor this rotation metadata.
Or, to answer your original question, you can rotate your videos as you transcode them. HandBrake has a filter for this which you can access using transcode-video.sh with the --filter option. You would use it like this:
transcode-video.sh --filter rotate[=MODE] "/path/to/Movie.mkv"

...where MODE is an integer with one of four values:

1 for vertical flip
2 for horizontal flip
3 for both vertical and horizontal flip (this is the default)
4 to rotate clockwise 90 degrees

So, you could perform a rotation with value 4 like this:
transcode-video.sh --filter rotate=4 "/path/to/Movie.mkv"

I hope that helps.
Thanks again for your question. I'll close this issue now but feel free to continue commenting here.

Thanks! Actually I had seen this option, but I hadn't thought how this could solve it. Thanks for you help


Bonfire: Sum All Odd Fibonacci Numbers  FREEZEEEE ~

Challenge [Bonfire: Sum All Odd Fibonacci Numbers]
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36.
My code:
var sumFibs = function(num) {
  var prev0 = 0;
  var prev1 = 1;
  var fib = 1;
  var sum = 1;

  //start from the second fibonacii
  while(fib <= num) {
    sum += fib;
    prev0 = prev1;
    prev1 = fib;
    fib = prev0 + prev1;
  }
  var boundary = fib;
  // star means odd, and o means even, and $ means argument : 'num'
  // * * o * * o * * $ o
  if(boundary % 2 === 0) {
    sum += boundary;
    return sum / 2;
  }
  // * * o * * o * $ *
  if((boundary % 2) && (prev1 % 2)) {
    sum -= prev1;
    return sum / 2 + prev1;
  }
  //* * o * * o $ *
  if((boundary % 2) && (0 === prev1 % 2)) {
    return sum / 2;
  }
}

When I click the button to Run Tests, the Chrome Dev Tool  logs a message below
Uncaught TypeError: Cannot read property 'length' of null
bonfireExecute @ commonFramework-0ad89d818f.js:1049
(anonymous function) @ commonFramework-0ad89d818f.js:1132
n.event.dispatch @ jquery.js:4430
r.handle @ jquery.js:4116

And nothing happened...

Clear chrome://setting/cookies  for freecodecamp cannot help

oh... Great Fire Wall  = == =

@KwenString thanks for pointing this out! I've created a PR to fix this. Your code is correct. You'll be able to pass this challenge if you change your comment //* * o * * o $ * to // * * o * * o $ *.

Please review the Guidelines for Contributing, thank you!.

So it's a RegExp problem, thanks for your suggestion,
for safety consideration, the asterisk symbol shouldn't appears in code comment

Might be related to #3763

Closing this issue as now editor catches this: Error: SyntaxError: Unfinished multi-line comment.

i also have this its annoying i cannot run tests

this is happening to me yet.


Conditional hooks

We have some conditional execution of hooks in the src/app/proposals/TimeRemainingColumn.tsx.

I get that it is an optimisation, but this is not allowed in react. This can be seen in the error that results from this.

It appears to be used here as well:

Please see https://react.dev/warnings/invalid-hook-call-warning for (dis-)allowed patterns.

Seems to be resolved with #272.

Actually it's not yet resolved. Reopening...

Actually it's not yet resolved. Reopening...

Indeed

Solved here #272


Add confirmation on repos reset

Summary
It's way too easy to do this accidentally, this context will definitely be useful for people going forward
Also added a reinstall utility as this can sometimes be useful too on cluster recreates
Test Plan
n/a
Checklist

[x] If required, I have updated the Plural documentation accordingly.
[x] I have added tests to cover my changes.
[x] I have added a meaningful title and summary to convey the impact of this PR to a user.
[x] I have added relevant labels to this PR to help with categorization for release notes.

Looks like the unit test needs to be updated though


Feature/issue 896 fix empty lat lng bug

@ian-lin-PG please make sure to review the changes I made to this PR as examples to follow in the future.

@ian-lin-PG please make sure to review the changes I made to this PR as examples to follow in the future.

The refactor been reviewed and I have no objections.


Can not lock horizontal surface plane finding mode

 fragment.getArSceneView().getSession().getConfig().setPlaneFindingMode(Config.PlaneFindingMode.HORIZONTAL);
This code is not working. It does not meter where to place this code - still finding vertical surfaces.

Try extending ArFragment and overriding the method getSessionConfiguration

@dsternfeld7 Thanks. It works if I override getSessionConfiguration like this:
 @Override
    protected Config getSessionConfiguration(Session session) {
        Config config = new Config(session);
        config.setPlaneFindingMode(Config.PlaneFindingMode.HORIZONTAL);
        return config;
    }

Hi! How about if I want to switch between modes? As @dementia2029 , I find fragment.getArSceneView().getSession().getConfig().setPlaneFindingMode(Config.PlaneFindingMode.HORIZONTAL); to do nothing. I want to switch between finding and not finding planes. Thanks a lot!

@dementia2029 found a way to toggle it in runtime.
Config config = fragment.getArSceneView().getSession().getConfig();
config.setPlaneFindingMode(Config.PlaneFindingMode.HORIZONTAL);
fragment.getArSceneView().getSession().configure(config);
Hope it helps someone!

@dementia2029 found a way to toggle it in runtime.
Config config = fragment.getArSceneView().getSession().getConfig();
config.setPlaneFindingMode(Config.PlaneFindingMode.HORIZONTAL);
fragment.getArSceneView().getSession().configure(config);
Hope it helps someone!

@dementia2029
Where do you place this? I get session null in onCreate.

@EdwinMurari Hi. You need to extend ArFragment class and override getSessionConfiguration()

@EdwinMurari do you want to be able to toggle between different plane finding modes or simply create a session with a finding mode different from HORIZONTAL_AND_VERTICAL?
If you want the latter, just extend ArFragment class, like @dementia2029 said:
class CustomArFragment : ArFragment () {
override fun getSessionConfiguration(session: Session?): Config {
val config = super.getSessionConfiguration(session)
config.planeFindingMode = Config.PlaneFindingMode.DISABLED //Whatever mode you would like
return config
}
}
If, on the other hand, you would like to be able to toggle between modes during the use of the application (say, by pressing a button), then the way I found to do so is this:
This is a function that you can call inside an onClickListener, for example, that will disable plane finding asuming your ArFragment is stored in a global variable in your activity:
fun disablePlaneFinding() {
val config = fragment?.arSceneView?.session?.config
config?.planeFindingMode = Config.PlaneFindingMode.DISABLED
fragment?.arSceneView?.session?.configure(config)
}

PS: Sorry formatting, first time posting on GH

@EdwinMurari do you want to be able to toggle between different plane finding modes or simply create a session with a finding mode different from HORIZONTAL_AND_VERTICAL?
If you want the latter, just extend ArFragment class, like @dementia2029 said:
class CustomArFragment : ArFragment () {
override fun getSessionConfiguration(session: Session?): Config {
val config = super.getSessionConfiguration(session)
config.planeFindingMode = Config.PlaneFindingMode.DISABLED //Whatever mode you would like
return config
}
}
If, on the other hand, you would like to be able to toggle between modes during the use of the application (say, by pressing a button), then the way I found to do so is this:
This is a function that you can call inside an onClickListener, for example, that will disable plane finding asuming your ArFragment is stored in a global variable in your activity:
fun disablePlaneFinding() {
val config = fragment?.arSceneView?.session?.config
config?.planeFindingMode = Config.PlaneFindingMode.DISABLED
fragment?.arSceneView?.session?.configure(config)
}

Thanks a lot man, I did by extending ArFragment, I thought there was another way to do it, maybe in onCreate.

I have successfully changed it to horizontal plane detection only.
But i have another issue which is in my ontaparfragment i have used that if plane().type==horizontal_upward_facing return;
but as i move my device towards ceiling . its also detecting the ceiling which is downward facing. so how can i correct this?


Creation of Galaxy user

Creating Ansible galaxy user for RH consulting, which will allow us to publish the roles from rhconsultling/jboss_eap repo

@kameshsampath this isn't need. See https://www.ansible.com/blog/ansible-galaxy-2-release. Just make sure you import the role from rhtconsulting repo and not your personal repo. I just test this and it works fine.

@sherl0cks, i can do that but when the role is exposed to outside world it will be exposed with the user who has imported the role from rhtconsulting/jboss_eap, for instance currently the role is available with my user kameshsampath.jboss_eap but I did import the role from rhtconsulting/jboss_eap. but for better branding and authenticity I personally feel to have a RH Consulting specific user so that its independent of the contributors.  thoughts ?

May you have the wrong permissions? https://galaxy.ansible.com/rhtconsulting/jboss_eap/ was done the way I described...

@sherl0cks, my bad i thought the galaxy user prefix would be added to it, but I see the organisation name is added as role's prefix


"The file (./src/ts) does not exist." after "ng add @ng-toolkit/universal"

I'm submitting a...

[ ] Bug report (Angular CLI: 6.0.8)

In package

[ ] @ng-toolkit/universal

Current behavior
after running ng add @ng-toolkit/universal I see error =>

INFO: Project property is set to 'fornida-ng6'.
ERROR: The file (./src/ts) does not exist.`

Repo
https://github.com/ohabash/fornida-ng6/
What else can i provide to help debug?

@maciejtreder Have you seen this before... I did ng add @ng-toolkit/universal in a brand new project and it worked fine. now I am trying to add it to an existing project https://github.com/ohabash/fornida-ng6


error running az aks install-cli

Issue
I tried to run the command below and got the resulting error:
c:\Program Files>az aks install-cli
The command failed with an unexpected error. Here is the traceback:
<urlopen error [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond>
Traceback (most recent call last):
File "urllib\request.py", line 1348, in do_open
File "http\client.py", line 1282, in request
File "http\client.py", line 1328, in _send_request
File "http\client.py", line 1277, in endheaders
File "http\client.py", line 1037, in _send_output
File "http\client.py", line 975, in send
File "http\client.py", line 1454, in connect
File "ssl.py", line 512, in wrap_socket
File "ssl.py", line 1070, in _create
File "ssl.py", line 1341, in do_handshake
TimeoutError: [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 663, in execute
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 726, in _run_jobs_serially
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 697, in _run_job
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 333, in call
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/acs/custom.py", line 2398, in k8s_install_cli
File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/acs/custom.py", line 2417, in k8s_install_kubectl
File "urllib\request.py", line 216, in urlopen
File "urllib\request.py", line 519, in open
File "urllib\request.py", line 536, in _open
File "urllib\request.py", line 496, in _call_chain
File "urllib\request.py", line 1391, in https_open
File "urllib\request.py", line 1351, in do_open
urllib.error.URLError: <urlopen error [WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond>
To open an issue, please run: 'az feedback'
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
I ran the command again and got the same error
Expected Behavior
Environment Summary
Windows-10-10.0.19042-SP0
Python 3.10.4
Installer: MSI

azure-cli 2.37.0

Additional Context

route to CXP team

@bwatkins449 Apologies for the late reply. Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.

@bwatkins449 The error message indicates that the issue seems to be at the network level. Do you have any proxy / firewall inside your corporate network ? If yes, this seems to be causing the socket connectivity to fail.
Could you please try to bypass this firewall / proxy and test again ? Alternatively you could try running this command from a different network and check if that works ? Awaiting your reply.

@bwatkins449 I wanted to do quick follow-up to check if you had a chance to look at my above comment. Please let us know if you need any further assistance on this. Awaiting your reply.

@bwatkins449 The action is currently pending on you. Please let us know if you still face the same issue after following the above plan. Please feel free to reopen this thread. We would be happy to help.


ESP32-H2 Deep Sleep Wakeup Resources (IDFGH-11523)

Hai
ESP-IDF Version V.5.1.2
Chip: ESP32-H2
I want to implement deep sleep in esp32-h2. I tried Deep Sleep Example wakeup using timer, its working fine.
I'm not able to Enable GPIO wakeup in esp32-h2.
what are the wakeup mode esp32-h2 support? (Like Timer, EXT0, EXT1, GPIO..)
How to enable GPIO wakeup?

hello, GPIO wakeup can be used in ESP32H2 when deepsleep, May I ask where you found information stating that the H2 can be woken up from deep sleep using GPIO wakeup?

esp-32h2 support GPIO wakeup, EXT1 wakeup and LP timer wakeup when lightsleep, and support EXT1 wakeup and LP timer wakeup when deepsleep.

hello, GPIO wakeup can be used in ESP32H2 when deepsleep, May I ask where you found information stating that the H2 can be woken up from deep sleep using GPIO wakeup?

Hai @10086loutianhao
In deep sleep example, Readme file  (This wake-up source is unavailable on ESP32, ESP32-S2, and ESP32-S3.) In this H2 was not mentioned. So, I thought It will support.

esp-32h2 support GPIO wakeup, EXT1 wakeup and LP timer wakeup when lightsleep, and support EXT1 wakeup and LP timer wakeup when deepsleep.

Hai @10086loutianhao
Thank you for your Information.
I want to use wakeup using EXT1 from deep sleep mode. What are the gpio can use for that?
We already designed Board for GPIO_11 and one more board with GPIO_5

esp-32h2 support GPIO wakeup, EXT1 wakeup and LP timer wakeup when lightsleep, and support EXT1 wakeup and LP timer wakeup when deepsleep.

Hai @10086loutianhao Thank you for your Information. I want to use wakeup using EXT1 from deep sleep mode. What are the gpio can use for that? We already designed Board for GPIO_11 and one more board with GPIO_5

hello, you can choose GPIO7-14 to use EXT1, but GPIO_5 is unavailable. Please refer to deepsleep example, and you can use idf.py menuconfig ->Example Configuration ->EXT1 wakeup configuration

hello, GPIO wakeup can be used in ESP32H2 when deepsleep, May I ask where you found information stating that the H2 can be woken up from deep sleep using GPIO wakeup?

Hai @10086loutianhao In deep sleep example, Readme file  (This wake-up source is unavailable on ESP32, ESP32-S2, and ESP32-S3.) In this H2 was not mentioned. So, I thought It will support.

Thanks

esp-32h2 support GPIO wakeup, EXT1 wakeup and LP timer wakeup when lightsleep, and support EXT1 wakeup and LP timer wakeup when deepsleep.

Hai @10086loutianhao Thank you for your Information. I want to use wakeup using EXT1 from deep sleep mode. What are the gpio can use for that? We already designed Board for GPIO_11 and one more board with GPIO_5

hello, you can choose GPIO7-14 to use EXT1, but GPIO_5 is unavailable. Please refer to deepsleep example, and you can use idf.py menuconfig ->Example Configuration ->EXT1 wakeup configuration

Hai @10086loutianhao
Thank you for your quick support.
I tried Deep sleep example with wakeup source EXT1.
It's working. Thank you. I'm closing this.


Add support for puppeteer headers and footers

Hi, this is a really useful tool but I wanted page numbers so I have added pass through arguments for the puppeteer headers/footers. Let me know if I missed anything.

I think this closes #7

Also perhaps #4

@meddbase-steve Thanks for your awesome PR 💯


Version 1.4.1

Added (for new features)

tool for showing introduction and general notes in Translation Notes
show obs-tn title comment
show obs-sq summary comment
support TSV Translation Questions

Changed (for changes in existing functionality)

update DialogUI
removed StrictMode as there were errors in the console

Fixed (for any bug fixes)

minor fixes in the code
clean console errors
update dependencies
colors for PWA

did'n t work correctly in intro some steps. maybe with class we have problems


pass parameters to workflow using API in Docker

Hi David,
I'm using txtai Docker API image according to the documentation: docker build -t txtai-api .
If I want to use the zero-shot classifier I have to provide the labels in the config.yml
# Zero-shot labeling labels:   path: MoritzLaurer/mDeBERTa-v3-base-xnli-multilingual-nli-2mil7
# Workflow definitions workflow:     entity:         tasks:             - action: entity               args: [null, "average", false, false]     labels:         tasks:             - action: labels               args: [["Addresse", "Klausel", "Deckungssumnme", "Postleitzahl", "Wohungsgröße", "Tarif", "Jahresprämie", "Versicherungslaufzeit", "Name", "Versicherungsbeginn", "AGB", "Ausnahmen", "Besondere Bedingungen"]]
This means when I change labels, I always have to rebuild the Docker image. This goes against the main advantages of the zero shot classifier. I do have a UI where I could provide labels and provide them to txtai. Is there a way I can pass labels dynamically to the API without having to rebuild the Docker image everytime?
Thanks in advance

Perhaps using the labels API method would work? It takes both the text and labels are parameters.
An example of this is here: https://colab.research.google.com/github/neuml/txtai/blob/master/examples/08_API_Gallery.ipynb

Hi David, what would be the correct endpoint (URL) to call the API method?

When calling the above mentioned endpoint it returns "not found". The same endpoint using "extract" is working fine

The end points are /label and /batchlabel

Thanks! That worked


Build name and errors without stacktrace in CC report

Allows displaying build name in the report to tell reports apart
Ensures that errors that don't have stacktraces are still indicated with an error icon

The merge queue build has started. Click here to see all failures if any.

The merge queue build has failed. Click here to see all failures.

The merge queue build has started. Click here to see all failures if any.


proto migrate v0.20 panic on windows

What version?
0.20.2
Which command?
proto migrate
What happened?
On Windows, proto migrate v0.20 crashes when "updating shell profile".
The output is slightly misleading, since I think proto exclusively update the path with setx, not by updating the PowerShell profile script.
Any logs?

.\.proto\bin\proto.exe setup --shell powershell --log debug
[DEBUG 2023-10-23 12:35:22] proto  Running proto v0.20.2  args=["C:\\Users\\dan\\.proto\\bin\\proto.exe", "setup", "--shell", "powershell", "--log", "debug"]
[DEBUG 12:35:22] proto::commands::setup:setup  Updating PATH with setx command

proto migrate v0.20
[ INFO 2023-10-23 11:42:17] proto::commands::migrate::v0_20:migrate  Loading tools...
[ INFO 11:42:18] proto::commands::migrate::v0_20:migrate  Deleting old shims...
[ INFO 11:42:18] proto::commands::migrate::v0_20:migrate  Generating new shims...
[ INFO 11:42:18] proto::commands::migrate::v0_20:migrate  Linking new binaries...
[ INFO 11:42:18] proto::commands::migrate::v0_20:migrate  Updating shell profile...
Error:   × Main thread panicked.
  ├─▶ at crates\cli\src\commands\migrate\v0_20.rs:63:66
  ╰─▶ called `Option::unwrap()` on a `None` value
  help: set the `RUST_BACKTRACE=1` environment variable to display a backtrace.

Operating system?
Windows
Architecture?
x64

I always forget about Windows 😓
This should do it https://github.com/moonrepo/proto/pull/253

I'm getting a similar error in a Gitlab CI/CD Pipeline
Error:   × Main thread panicked.
  ├─▶ at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/
  │   thread/mod.rs:686:29
  ╰─▶ failed to spawn thread: Os { code: 11, kind: WouldBlock, message:
      "Resource temporarily unavailable" }
         0: 0x557c34c73fe2 - rust_begin_unwind
         1: 0x557c3436d273 - core::panicking::panic_fmt::hd1e971d8d7c78e0e
         2: 0x557c3436d67a - core::result::unwrap_failed::hccb456d39e9c31fc
         3: 0x557c349a726a -
      proto_core::helpers::is_offline_no_cache::h0fe940672761bc32
         4: 0x557c349a7d27 - proto_core::helpers::is_offline::hd37aeadc9bf7b345
         5: 0x557c3498e384 - once_cell::imp::OnceCell<T>::initialize::
      {{closure}}::h46e8e7006ff087ce
         6: 0x557c347571cd -
      once_cell::imp::initialize_or_wait::h3d9515472a105be3
         7: 0x557c343a4ff2 -
      once_cell::imp::OnceCell<T>::initialize::h2ed9aba8fb4049ec
         8: 0x557c3476db78 - proto_core::tool_loader::load_tool::
      {{closure}}::he278257c180732be
         9: 0x557c3493c7e5 - proto::commands::run::run::{{closure}}::
      {{closure}}::h34d26e47daa16711
        10: 0x557c348770ca - <T as starbase::system::SystemFunc>::call::
      {{closure}}::hb3f42077714f70e8
        11: 0x557c34c23357 - <starbase::system::CallbackSystem as
      starbase::system::System>::run::{{closure}}::h25d7154cf0a60a43
        12: 0x557c348bc4f8 - starbase::app::App::run_systems_in_parallel::
      {{closure}}::{{closure}}::hc656cddc6183fd5f
        13: 0x557c348932f1 - tokio::runtime::task::raw::poll::h1fe6c71126eea60f
        14: 0x557c34cc0480 -
      tokio::runtime::scheduler::multi_thread::worker::Context::run_task::h364
      22c09498893[50](https://gitlab.rialtic.dev/gitlab-engineering/gitlab-ui/console-ui/-/jobs/808383#L50)
        15: 0x[55](https://gitlab.rialtic.dev/gitlab-engineering/gitlab-ui/console-ui/-/jobs/808383#L55)7c34cbe7fe -
      tokio::runtime::scheduler::multi_thread::worker::run::h270df6a4db17[56](https://gitlab.rialtic.dev/gitlab-engineering/gitlab-ui/console-ui/-/jobs/808383#L56)72
        16: 0x5[57](https://gitlab.rialtic.dev/gitlab-engineering/gitlab-ui/console-ui/-/jobs/808383#L57)c34cc434e - tokio::runtime::task::raw::poll::h3e94ad39d32fff[82](https://gitlab.rialtic.dev/gitlab-engineering/gitlab-ui/console-ui/-/jobs/808383#L82)

@ackushiw That seems weird. What version of proto is that?
This error seems like proto is unable to create a system thread? Not sure why that would be the case.

It's called Windows because it breaks all the time :-).
I think this can be made much more intuitive:

The detected shell should be shown in stderr with proto setup --profile. Maybe this should even be shown on stderr.
The current behavior on Windows should probably be given a name like proto setup --shell winreg.

I do think proto setup --shell powershell should update the powershell profile script, and proto setup should update the powershell profile if it already exists.
I currently have the following in my profile, which works despite the comment here.
$env:PROTO_HOME=(Join-Path $HOME ".proto")
$env:PATH=(Join-Path $env:PROTO_HOME "shims")+";"+$env:PATH
$env:PATH=(Join-Path $env:PROTO_HOME "bin")+";"+$env:PATH

And my execution policy is:
Set-ExecutionPolicy -Scope CurrentUser RemoteSigned

@milesj I think I had the CI setup for v0.19 but it get's the latest version every time it runs.
Can I install a specific version using the example in https://github.com/moonrepo/proto/issues/138?

@rotu I don't know anything about Windows shells/dev environments, or how they work. I'm probably not the best choice to implement this functionality. Always open to PRs.
@ackushiw Are you using the install script or the github actions? Install script should work using a version without "v", like "0.19.0".

@milesj should I open a new issue? Seems like it's unrelated to the original

Yeah, new issue is probably best.


Github tags outdated

The version tags in Github have not been updated since 0.1.6 whereas the changelog is at 0.1.10. The version tags are useful for bower installations, please keep them up to date.

0.1.11 is now tagged. Sorry about the delay :)


Create Docker Action exercise.

This workshop should include an exercise for creating Docker Actions.

Closing as project is being archived.