Upgrade from 0.2.1 to 0.3.3 don't work

I'm using metrics-server on many clusters in a multi-cloud environment. We have some clusters in Azure and some in AWS. On all is installed the metrics-server 0.2.1 (with the latest helm chart) and works properly.
If I try to update to version 0.3.3 I get these errors:
Cluster 1 (on AWS, K8s 1.13.6 deployed with KOPS)
E0729 11:53:55.155439       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/nginx-ingress-controller-76f8c5db55-48hxs: no metrics known for pod E0729 11:53:55.155464       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/nginx-ingress-controller-76f8c5db55-4zq7l: no metrics known for pod E0729 11:54:10.172521       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/nginx-ingress-controller-76f8c5db55-48hxs: no metrics known for pod E0729 11:54:10.172693       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/nginx-ingress-controller-76f8c5db55-4zq7l: no metrics known for pod E0729 11:54:19.417368       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:k8s-minion-22546418-vmss000005: unable to fetch metrics from Kubelet k8s-minion-22546418-vmss000005 (k8s-minion-22546418-vmss000005): Get https://k8s-minion-22546418-vmss000005:10250/stats/summary/: x509: certificate signed by unknown authority, unable to fully scrape metrics from source kubelet_summary:k8s-minion-22546418-vmss000006: unable to fetch metrics from Kubelet k8s-minion-22546418-vmss000006 (k8s-minion-22546418-vmss000006): Get https://k8s-minion-22546418-vmss000006:10250/stats/summary/: x509: certificate signed by unknown authority, unable to fully scrape metrics from source kubelet_summary:k8s-master-22546418-0: unable to fetch metrics from Kubelet k8s-master-22546418-0 (k8s-master-22546418-0): Get https://k8s-master-22546418-0:10250/stats/summary/: x509: certificate signed by unknown authority] E0729 11:54:21.749158       1 reststorage.go:128] unable to fetch node metrics for node "k8s-minion-22546418-vmss000006": no metrics known for node E0729 11:54:21.749178       1 reststorage.go:128] unable to fetch node metrics for node "k8s-minion-22546418-vmss000005": no metrics known for node E0729 11:54:21.749183       1 reststorage.go:128] unable to fetch node metrics for node "k8s-master-22546418-0": no metrics known for node E0729 11:54:21.755184       1 reststorage.go:147] unable to fetch pod metrics for pod kube-system/tiller-deploy-7f656b499f-5jqbq: no metrics known for pod E0729 11:55:47.809132       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:k8s-minion-22546418-vmss000005: unable to fetch metrics from Kubelet k8s-minion-22546418-vmss000005 (k8s-minion-22546418-vmss000005): Get https://k8s-minion-22546418-vmss000005:10250/stats/summary/: x509: certificate signed by unknown authority, unable to fully scrape metrics from source kubelet_summary:k8s-minion-22546418-vmss000006: unable to fetch metrics from Kubelet k8s-minion-22546418-vmss000006 (k8s-minion-22546418-vmss000006): Get https://k8s-minion-22546418-vmss000006:10250/stats/summary/: x509: certificate signed by unknown authority, unable to fully scrape metrics from source kubelet_summary:k8s-master-22546418-0: unable to fetch metrics from Kubelet k8s-master-22546418-0 (k8s-master-22546418-0): Get https://k8s-master-22546418-0:10250/stats/summary/: x509: certificate signed by unknown authority] I0729 12:02:38.455719       1 healthz.go:170] healthz check healthz failed: there was an error collecting or saving metrics in the last collection tick I0729 12:02:38.455873       1 wrap.go:47] GET /healthz: (1.912627ms) 500 goroutine 377 [running]: github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/httplog.(*respLogger).recordStatus(0xc420714bd0, 0x1f4) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/httplog/httplog.go:204 +0xd2 github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/httplog.(*respLogger).WriteHeader(0xc420714bd0, 0x1f4) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/httplog/httplog.go:183 +0x35 github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters.(*baseTimeoutWriter).WriteHeader(0xc4206afb20, 0x1f4) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters/timeout.go:205 +0xac net/http.Error(0x7f0f17273318, 0xc42000c6e0, 0xc4203563f0, 0x82, 0x1f4) 	/usr/local/go/src/net/http/server.go:1959 +0xda github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/healthz.handleRootHealthz.func1(0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/healthz/healthz.go:184 +0x697 net/http.HandlerFunc.ServeHTTP(0xc420434140, 0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/usr/local/go/src/net/http/server.go:1947 +0x44 github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/mux.(*pathHandler).ServeHTTP(0xc420080500, 0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/mux/pathrecorder.go:241 +0x514 github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/mux.(*PathRecorderMux).ServeHTTP(0xc420761f80, 0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/mux/pathrecorder.go:234 +0x8a github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server.director.ServeHTTP(0x16ac99d, 0xe, 0xc420108bd0, 0xc420761f80, 0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/handler.go:154 +0x6a8 github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters.WithAuthorization.func1(0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters/authorization.go:64 +0x4bd net/http.HandlerFunc.ServeHTTP(0xc4203ed0c0, 0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/usr/local/go/src/net/http/server.go:1947 +0x44 github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters.WithMaxInFlightLimit.func1(0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters/maxinflight.go:160 +0x4dc net/http.HandlerFunc.ServeHTTP(0xc42077ac30, 0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/usr/local/go/src/net/http/server.go:1947 +0x44 github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters.WithImpersonation.func1(0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters/impersonation.go:50 +0x1cf6 net/http.HandlerFunc.ServeHTTP(0xc4203ed100, 0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/usr/local/go/src/net/http/server.go:1947 +0x44 github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters.WithAuthentication.func1(0x7f0f17273318, 0xc42000c6e0, 0xc4207f1000) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters/authentication.go:81 +0x33b net/http.HandlerFunc.ServeHTTP(0xc420774870, 0x7f0f17273318, 0xc42000c6e0, 0xc4207f0f00) 	/usr/local/go/src/net/http/server.go:1947 +0x44 github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP.func1(0xc420673b60, 0xc4207807e0, 0x1840da0, 0xc42000c6e0, 0xc4207f0f00) 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters/timeout.go:108 +0xb3 created by github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP 	/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters/timeout.go:97 +0x1b8 logging error output: "[+]ping ok\n[+]log ok\n[+]poststarthook/generic-apiserver-start-informers ok\n[-]healthz failed: reason withheld\nhealthz check failed\n"
Cluster 2 (on Azure, K8s 1.14.3 deployed with AKS)
`E0729 11:59:34.776273       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:k8s-minion-22546418-vmss000005: unable to fetch metrics from Kubelet k8s-minion-22546418-vmss000005 (k8s-minion-22546418-vmss000005): request failed - "401 Unauthorized", response: "Unauthorized", unable to fully scrape metrics from source kubelet_summary:k8s-minion-22546418-vmss000006: unable to fetch metrics from Kubelet k8s-minion-22546418-vmss000006 (k8s-minion-22546418-vmss000006): request failed - "401 Unauthorized", response: "Unauthorized", unable to fully scrape metrics from source kubelet_summary:k8s-master-22546418-0: unable to fetch metrics from Kubelet k8s-master-22546418-0 (k8s-master-22546418-0): request failed - "401 Unauthorized", response: "Unauthorized"]
I0729 11:59:35.719022       1 healthz.go:170] healthz check healthz failed: there was an error collecting or saving metrics in the last collection tick
I0729 11:59:35.719921       1 wrap.go:47] GET /healthz: (4.613209ms) 500
goroutine 355 [running]:
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/httplog.(*respLogger).recordStatus(0xc4207a9570, 0x1f4)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/httplog/httplog.go:204 +0xd2
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/httplog.(*respLogger).WriteHeader(0xc4207a9570, 0x1f4)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/httplog/httplog.go:183 +0x35
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters.(*baseTimeoutWriter).WriteHeader(0xc4209f55c0, 0x1f4)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters/timeout.go:205 +0xac
net/http.Error(0x7fbcee55d448, 0xc42099aa00, 0xc4207aa870, 0x82, 0x1f4)
/usr/local/go/src/net/http/server.go:1959 +0xda
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/healthz.handleRootHealthz.func1(0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/healthz/healthz.go:184 +0x697
net/http.HandlerFunc.ServeHTTP(0xc420650120, 0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/usr/local/go/src/net/http/server.go:1947 +0x44
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/mux.(*pathHandler).ServeHTTP(0xc4204c8400, 0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/mux/pathrecorder.go:241 +0x514
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/mux.(*PathRecorderMux).ServeHTTP(0xc420417ab0, 0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/mux/pathrecorder.go:234 +0x8a
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server.director.ServeHTTP(0x16ac99d, 0xe, 0xc42010abd0, 0xc420417ab0, 0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/handler.go:154 +0x6a8
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters.WithAuthorization.func1(0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters/authorization.go:64 +0x4bd
net/http.HandlerFunc.ServeHTTP(0xc42032fdc0, 0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/usr/local/go/src/net/http/server.go:1947 +0x44
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters.WithMaxInFlightLimit.func1(0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters/maxinflight.go:160 +0x4dc
net/http.HandlerFunc.ServeHTTP(0xc420017aa0, 0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/usr/local/go/src/net/http/server.go:1947 +0x44
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters.WithImpersonation.func1(0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters/impersonation.go:50 +0x1cf6
net/http.HandlerFunc.ServeHTTP(0xc42032fe00, 0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/usr/local/go/src/net/http/server.go:1947 +0x44
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters.WithAuthentication.func1(0x7fbcee55d448, 0xc42099aa00, 0xc420aa0700)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/endpoints/filters/authentication.go:81 +0x33b
net/http.HandlerFunc.ServeHTTP(0xc42071a780, 0x7fbcee55d448, 0xc42099aa00, 0xc420aa0600)
/usr/local/go/src/net/http/server.go:1947 +0x44
github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP.func1(0xc420ad8360, 0xc4204cf040, 0x1840da0, 0xc42099aa00, 0xc420aa0600)
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters/timeout.go:108 +0xb3
created by github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters.(*timeoutHandler).ServeHTTP
/go/src/github.com/kubernetes-incubator/metrics-server/vendor/k8s.io/apiserver/pkg/server/filters/timeout.go:97 +0x1b8
logging error output: "[+]ping ok\n[+]log ok\n[+]poststarthook/generic-apiserver-start-informers ok\n[-]healthz failed: reason withheld\nhealthz check failed\n"`
Any suggestion?

A small note: I installed it with the plain helm values except this args --logtostderr --kubelet-insecure-tls --v=4

v0.3.2 and v0.3.3 was installed with this options:
`  - --v=4

--kubelet-insecure-tls
--kubelet-preferred-address-types=InternalIP`

I installed metrics-server 0.3.3 on another cluster on Azure (deployed with Kubespray) and there I noticed that is working only inside the kube-system namespace. :(

I tried to update on a third cluster deployed with aks-engine and I get the same problem.
Ref: https://github.com/Azure/aks-engine/issues/1707

I found a solution: https://github.com/kubernetes-incubator/metrics-server/pull/296

With my solution metrics-server works but only on kubernetes 1.12 😢

kubectl top pods
Result:
W0827 14:26:49.076592   81772 top_pod.go:266] Metrics not available for pod default/busybox, age: 332h53m37.076586606s
error: Metrics not available for pod default/busybox, age: 332h53m37.076586606s

kubectl logs <metrics-server-pod-name>
Result:
E0827 13:37:10.001523       1 reststorage.go:147] unable to fetch pod metrics for pod default/busybox: no metrics known for pod
I face the same issue when I run kubectl top pods command which worked earlier without an issue. Initially, I had about 2-5 pods and now it has around 15-20 pods. top pods command doesnt work now but top nodes command works correctly.
I tried with increasing replicas and editing the metrics-server-deployment.yaml file and adding parameters below to fix the error. but it also doesn't work for me.
command:
        - /metrics-server
        - --kubelet-insecure-tls
        - --kubelet-preferred-address-types=InternalIP

Also the helm chart fails during the test with version 0.3.3
Ref: https://github.com/helm/charts/pull/16656/

Found the solution https://github.com/kubernetes-incubator/metrics-server/issues/278#issuecomment-515370587

I solved with this: https://github.com/kubernetes-incubator/metrics-server/issues/278#issuecomment-515370587

https://github.com/kubernetes-incubator/metrics-server/issues/272


Freeze Rubocop in Hound CI at version 0.54.0

As you all know, we use Hound CI to validate our commits against the style guide contained in this repository. Unfortunately, our previous experience is that Rubocop version bumps may cause headaches if they introduce breaking changes—and they frequently do.
Recently, Hound CI added a new feature: we may now enforce specific Rubocop version. This pull request enforces version 0.54.0, which is a default one at the moment I am writing this message.
This pull request should break nothing, however will prevent us from problems in future. I suppose everyone will agree on merging this one, nevertheless I am open for discussion.
cc @opoudjis @ronaldtse @ribose-jeffreylau
Also, we should discuss upgrading Rubocop to 0.59.2, but that's a separate concern. I'll create a proper pull request for that as soon as we merge in current one.

Eh, that means that if any of us are running Rubocop on the command line (which is the real point of Rubocop), we need to downgrade to Rubocop 0.54.0; otherwise we have unnecessary conflict between Hound and command line Rubocop. Moreover, if we ever do a gem update, Rubocop is going to upgrade regardless.
Out of courtesy, you should be warning Ribose staff that they need to downgrade Rubocop:
gem uninstall rubocop
gem install rubocop -v 0.54.0

@opoudjis Quite contrary.
This pull request adds version constraint to .hound.yml, which is recognized by Hound CI only. It does not affect Rubocop on local machine. You can still use any Rubocop version you want, be it defined in gemspec, gemfile (Hound disregards these files), or installed manually, provided that it is compatible with this guide (AFAIK the newest one is compatible).
The purpose of this pull request is to save us surprises like ones we had in the past, when Hound CI upgraded Rubocop version on their end, and we had to cope with breaking changes. By setting a specific version in .hound.yml, we are taking control over these upgrades.
Finally, I suppose that Hound will remain conservative and won't change the default Rubocop version eagerly. Therefore, if we want to keep this style guide up-to-date with newest Rubocop releases, then at some point we'll likely have_to enforce some specific Rubocop version which is newer than default one.

Hound and local Rubocop working from different versions sounds like bad news to me, particular given the recurring cop breakages to me. But it's not like I've had time to run Rubocop in months.

@opoudjis The .hound.yml is the only way to set a specific Rubocop version in Hound CI. So we have two choices: rely on defaults (which is expected to be extremely conservative, and may change in future without our control), or set some version ourselves. Taking into account that previous Rubocop version bumps in Hound CI often led to issues, it becomes obvious that the latter is better.
You can override Rubocop version in project's .hound.yml if you want. But I know it isn't a very useful solution. Supported Rubocop versions are listed in Hound docs.


Galoshes 1984

changelog
-galoshes slow you down
-fuck you

Why
If someone has galoshes then arrest them and give the boots to the role that actually needs and uses it
Unless you’re a syndie then steal em all

This is excessive and really overkill. Just make it so that blood puddles dont slip people. Theres no need to nerf such a mundane item.

In fact blood puddles are due to have this changed. Galoshes work as-is, there is no reason to nerf them.

Imo no need to nerf them, it's like insulated gloves they're a benefit of the job and sought after. Jani just needs to report them stolen.
Maybe blood puddles under a certain size don't slip and only big puddles do? And small ones dry to a decal faster idk.

Honestly mixed on this one so I threw this out to start more discussion on it.

just some context. In most ss13 servers they do actually have a SLIGHT move speed debuff, enough to where if you were being nefarious they could be a detriment.  I don't think that sec would ever really police galoshes.

damn I actually agreed with this one


Enable compilation on Android

This pull request contains changes that are necessary to compile Lomse library for Android. Similar to #135, it was necessary to replace ftello64, fseeko64 and fopen64 functions which are not present on Android. In addition to that, I have added a change to ioapi.h which disables using 64-bit flavors of these functions when building for Android. This was necessary to get compressed files support in Lomse working on Android versions earlier than Android 7 (API level 24) since those versions didn't have 64-bit fseeko/ftello functions. This change disables support of compressed files larger than 4GB on that platform, but it doesn't seem to be needed for musical file formats anyway.
A similar change has also been done in another fork of minizip, so synchronizing minizip code with that fork can also be another option to resolve compilation issues on some platforms.

Hi Dmitri, thank you for the PR.
I do not think that the limitation to 4GB is important. Zip support is only needed for dealing with MusicXML files and, in future, with MNX files. And music files greater than 4GB probably do not exist, or if any, it must be an unusual exception, perhaps a file containing collections of music sheets. Thus, I do not see any problem with this PR.
As to your suggestion of basing Lomse in the minizip fork maintained by nmoinvaz, I didn't know about that fork. It is important to ensure that all third party code used in Lomse is properly maintained, as Lomse depends on it. The original minizip package, found in zlib distribution, has not been updated since October 2009. And it is clear that some maintenance is needed, at least to fix compilation warnings and some minor changes to deal with issues in other platforms, such as the ones addressed by your PR. Fork by nmoinvaz seems to be better maintained, so I wouldn't mind basing Lomse on it.
But the problem for doing this move is that the minizip package maintained by nmoinvaz has a totally different structure from the original minizip package. Probably nmoinvaz has done a very good job refactoring and updating the code but now, to use it it is necessary to determine what is needed for Lomse and doing some tests. Currently Lomse only uses two files from the minizip package (ioapi.c, unzip.c) and these files no longer exist in nmoinvaz fork. Thus, taking into account that:
a) minizip is very stable and it is rarely updated, and that Lomse only requires just unzip functionality, and
b) basing Lomse in minizip fork maintained by nmoinvaz requires some work to determine how to do it and do some testing, and do not have it now.
So I would vote to just apply your PR to current minizip code, and leave the move to nmoinvaz/minizip fork future, when more time available to do it or when forced by an important bug. Other ideas?

Yes, I agree that patching the current version of minizip would be fine. Moving to another fork may be a good option to make use of fixes that have already been added there, but if there are no serious issues with the old code I think it would be fine to stay with the current version of minizip.

Merged! Thank you.


Stylistic and more idiomatic code

A few incredibly minor edits:

Use test instead of [ ... ], in accordance with documentation and the rest of the code. https://github.com/fish-shell/fish-shell/issues/1850 says that use of the square brackets for test is highly discouraged.
Use 2>/dev/null instead of 2> /dev/null. This is preferred by fish_indent. I can demonstrate this if you wish.
Use string escape "$blah" instead of echo $blah | string escape

Hi again, boy how many times have you read through my code? Really appreciate my thoroughness.


Sections should redirect to the beginning of the flow if all entries are deleted

Context
If a candidate deletes all of their entries on a qualification or work/volunteering section, they should be redirected to the beginning of the sections flow.
Currently the following sections they are returned to the empty review page on the following sections

work history
volunteering
degrees
other qualifications

Changes proposed in this pull request

Redirect from the work history review controller to the work history length page if there are no jobs/work break explanations
Redirect to the volunteering experience page after destroying the last volunteering experience
Redirect to the degree type page when the last degree is destroyed
Redirect to the new other qualification type page if the last other qualification is destroyed

Guidance to review
Going to leave a comment on one section explaining the thought process for an additional link in
Link to Trello card
https://trello.com/c/rMMKY1rS/1949-bug-candidates-seeing-empty-review-page-not-section-start-page
Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

Thanks Steve. Yea I'll ask Paul when he's back from leave.


Rebuild for gsl27

This PR is a manual migration to gsl2.7, for some reason this feedstock is listed as 'not solvable' on the migration status with the following error
Encountered problems while solving:
- nothing provides requested libllvm9 9.0.1.* 2

which I don't understand.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Thanks for this @duncanmmacleod!
I'll also push patches for tbb 2021 and the update to 6.24.4 so I can stick to a single set of new osx-arm64 builds. Updating tbb will cause this PR to be blocked by https://github.com/conda-forge/numba-feedstock/pull/83 but I think that's now ready for merging so it shouldn't delay this PR by much.


utoronto nbgitpuller in rstudio tries to pull to /home/jovyan which is ro

Ref: https://2i2c.freshdesk.com/a/tickets/726
nbgitpuller doesn’t seem to be working on https://r.datatools.utoronto.ca
For example trying to pull https://github.com/ntaback/learnr_test2 into the hub with
https://r.datatools.utoronto.ca/hub/user-redirect/git-pull?repo=https%3A%2F%2Fgithub.com%2Fntaback%2Flearnr_test2&urlpath=rstudio%2F&branch=main
Throws the error …
rstudio@jupyter-pris-2enasrat-40utoronto-2eca:~$ pwd
/home/rstudio
rstudio@jupyter-pris-2enasrat-40utoronto-2eca:~$ ls /home/jovyan/
shared
rstudio@jupyter-pris-2enasrat-40utoronto-2eca:~$ id
uid=1000(rstudio) gid=1000(rstudio) groups=1000(rstudio),50(staff),100(users)
rstudio@jupyter-pris-2enasrat-40utoronto-2eca:~$ cd /home/jovyan/
rstudio@jupyter-pris-2enasrat-40utoronto-2eca:/home/jovyan$ ls -al
total 9
drwxr-xr-x 3 root    root    4096 May 19 14:40 .
drwxr-xr-x 1 root    root    4096 May 19 14:40 ..
drwxr-xr-x 2 rstudio rstudio   64 Dec 13 04:51 shared
rstudio@jupyter-pris-2enasrat-40utoronto-2eca:/home/jovyan$

This can be worked around by forcing a targetPath https://r.datatools.utoronto.ca/user/pris.nasrat@utoronto.ca/git-pull?repo=https%3A%2F%2Fgithub.com%2Fntaback%2Flearnr_test2.git&urlpath=rstudio%2F&branch=main&redirects=1&targetPath=/home/rstudio/foo

Possibly jupyterhub/nbgitpuller#268

jupyter serverextension list
config dir: /srv/conda/etc/jupyter
    jupyter_server_proxy  enabled
    - Validating...
      jupyter_server_proxy  OK
    jupyter_resource_usage  enabled
    - Validating...
      jupyter_resource_usage 0.7.1 OK
    jupyter_server_ydoc  enabled
    - Validating...
      X is jupyter_server_ydoc importable?
    jupyterlab  enabled
    - Validating...
      jupyterlab 3.6.3 OK
    nbgitpuller  enabled
    - Validating...
      nbgitpuller 1.1.1 OK
    retrolab  enabled
    - Validating...
      retrolab 0.3.21 OK

Hmm ok so cwd of PID 1 which is jupyterhub singleuser is /home/jovyan. So maybe we are not seetting notebook_dir or server_root_dir correctly here.
ls -al /proc/1/cwd
lrwxrwxrwx 1 rstudio rstudio 0 May 19 15:19 /proc/1/cwd -> /home/jovyan

    volumeMounts:
    - mountPath: /home/rstudio
      name: home
      subPath: pris-2enasrat-40utoronto-2eca
    - mountPath: /etc/gitconfig
      name: files
      subPath: gitconfig
    - mountPath: /etc/github/github-app-private-key.pem
      name: files
      subPath: github-app-private-key.pem
    - mountPath: /usr/local/etc/ipython/ipython_kernel_config.json
      name: files
      subPath: ipython_kernel_config.json
    - mountPath: /usr/local/etc/jupyter/jupyter_notebook_config.json
      name: files
      subPath: jupyter_notebook_config.json
    - mountPath: /usr/local/etc/jupyter/jupyter_server_config.json
      name: files
      subPath: jupyter_server_config.json
    - mountPath: /home/jovyan/shared
      name: home
      readOnly: true
      subPath: _shared
    workingDir: /home/jovyan

@pnasrat  yep, https://github.com/2i2c-org/infrastructure/issues/2559#issuecomment-1554766238 is the root of the problem. I think we should modify r-common to set workingDir to /home/rstudio. I also felt some deja-vu with this problem, and behold, I had encountered it at UC Berkeley a few years ago and fixed it the exact same way https://github.com/berkeley-dsep-infra/datahub/blob/70447314413e15f41b1e870badae11acaff340c4/deployments/stat20/config/common.yaml#L25
We should add this as a piece of documentation somewhere, but not sure where.

deployed fix to r-staging and tested via
https://r-staging.datatools.utoronto.ca/hub/user-redirect/git-pull?repo=https%3A%2F%2Fgithub.com%2Fntaback%2Flearnr_test2&urlpath=rstudio%2F&branch=main


Use new css @scope for components styles

With css scopes, we can restrict style declarations to components without affecting children.

See https://github.com/unyt-org/uix-dom/issues/4


[Feature request]: Support for the Eufy Dual Video Door (Model T8213)

Describe the solution you'd like
I current have my Eufy account setup with Home Assistant but it seems like it doesn't detect Model T8213 as a camera.

https://github.com/bropat/eufy-security-client/issues/126


added support for CheckForOverflowUnderflow in csproj

We now respect <CheckForOverflowUnderflow> setting when constructing compilation options.
This is equivalent to passing /checked switch to csc.

resolved conflicts - should be good to go


Evm can run with SpecId::Cancun hardfork without KZG point evaluation precompile

The addition of the KZG point evaluation precompile to the list of precompiles is hidden behind the c-kzg feature flag:
    /// Returns precompiles for Cancun spec.
    ///
    /// If the `c-kzg` feature is not enabled KZG Point Evaluation precompile will not be included,
    /// effectively making this the same as Berlin.
    pub fn cancun() -> &'static Self {
        static INSTANCE: OnceBox<Precompiles> = OnceBox::new();
        INSTANCE.get_or_init(|| {
            let precompiles = Self::berlin().clone();

            // Don't include KZG point evaluation precompile in no_std builds.
            #[cfg(feature = "c-kzg")]
            let precompiles = {
                let mut precompiles = precompiles;
                precompiles.extend([
                    // EIP-4844: Shard Blob Transactions
                    kzg_point_evaluation::POINT_EVALUATION,
                ]);
                precompiles
            };

            Box::new(precompiles)
        })
    }

This resulted in silent failures when running EIP-4844 transactions on an Evm with SpecId::CANCUN. Instead, I would have expected it to be forbidden to run revm with SpecId::CANCUN if the c-kzg feature flag was missing.

This would mean no wasm support for revm Cancun, even if not all TX are using this precompile.
I didn't success in compaling c-kzg for no std platforms, and there is not alternative (afaik) in rust that we can switch to (similar what we have done with k256 and secp256k1 libs)

It seems there is an alternative in rust: https://github.com/grandinetech/rust-kzg/tree/main/kzg
worth investigating

Closed in: https://github.com/bluealloy/revm/pull/1558 alternative is not audited or tested but for no_std environment can be useful
And if no features are enabled a fatal error will be thrown https://github.com/bluealloy/revm/pull/1589


Support configuration of sslcontext

Is your feature request related to a problem? Please describe.
Allow simple configuration of the sslcontext similar to hato's: https://github.com/gnarroway/hato/blob/7862f9e3ab692ea499b935842978688831e61bfd/src/hato/client.clj#L91.
Otherwise, I would have to configure the script with system properties or use interop code.
Additional context
Chat in slack: https://clojurians.slack.com/archives/C04J0N76E2G/p1679865379426629

@sdmoralesma Can you describe how you would like the API to look like, roughly?


fix, refactor, chore(egen): follows new template, adds dataflow enable step, refactor

The associated notebook follows an old template and doesn't explicitly enable the dataflow API which is essential for running the evaluation components.
This PR includes the following updates:

Restructures the notebook according to the new template.
Replaces REGION with LOCATION.
Removes IS_TESTING condition in the Cleaning up section.
Adds clean up steps for the locally generated files.
Adds a step to enable the dataflow API.
Minor sentence/word corrections.

REQUIRED: Fill out the below checklists or remove if irrelevant

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

/gcbrun

/gcbrun


Errors after setup with install GPU (Windows)

It´s really frustrating. I can´t get it running, even i did everything according instruction. Also have Python and GIT installed, ffmpeg and also set PATH in windows.  Installed CUDA drivers for Windows and choosed CUDA batch of course.
After successfull running of script, downloading and installing here and there (no error messages during installation) i start with run_on_windows.bat and get new window (.venv) E:\Ultrasinger\src>
When typing py Ultrasinger.py it takes a while and than i get following messages and do not know what to do
Traceback (most recent call last):
File "E:\Ultrasinger\src\UltraSinger.py", line 21, in
from modules.Audio.youtube import (
File "E:\Ultrasinger\src\modules\Audio\youtube.py", line 12, in
from modules.musicbrainz_client import search_musicbrainz
File "E:\Ultrasinger\src\modules\musicbrainz_client.py", line 6, in
from src.Settings import Settings
ModuleNotFoundError: No module named 'src'
Anybody could help and solve my issues? I´m not an expert and also not familar with python etc.
Thanks

Hi,
py is probably linked to your native python installation and not the venv. Try executing with python Ultrasinger.py :) Testing myself now

Are you by any chance using PowerShell as your default? If so, the .venv does not get properly activated. Try running the installer from "Command Prompt" (not terminal or powershell).

Finally i´ve got it running. With CUDA there was some problems, so I made clean install with CPU now. After running script and start Ultrasinger i´ve got same problems and messages as before. I´ve checked the musicbrainz_client.ply and changed
from "src Settings import Setting"
to "from Settings import Settings"
Now Ultrasinger is running, doing all the steps and gerenarted several files and txt file. Did not checked final results in Ultrastar, but programm is running, this was my main goal to reach.
Okay, the names and title muscbrainz put out is nonsense, but if this is the "only" problem i can accept and rename my files manually.
I will give it a try to use command promt to run installer (for sure on another pc) and report in next days if this is better result

I was going to investigate. Thanks for catching that. I just put  PR #203 in for that.

Does this run now with the changes from #203?
We could provide an extra run script for activation in PS. #205
For Musicbrainz. I think we should provide options for an manual search. #207

I am not sure if the installer is an issue after all. I had trouble in the past where the activation was not successful and the packages were installed in my main installation. Nonetheless, I created a small PR #209  to fix any possible issues, regardless of the shell. Rather than activating the venv (which we don't need to unless we are doing something more complicated), we can just run the python.exe within the venv to install into the venv

I think the issue was #203
His log says -> ModuleNotFoundError: No module named 'src'


Users Storage used no longer has edit option

[Enter feedback here]
This section is incorrect as these options are no longer available.
Select the OneDrive tab.
Under Storage used click Edit.

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

ID: feeb9370-51c8-dbb3-57b9-792f4d22624d
Version Independent ID: 7337e3b2-278f-f12f-a041-fc7e372205f0
Content: Change a specific user's OneDrive storage space - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/change-user-storage.md
Service: one-drive
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@abates100 : I followed the rules and it works like the article
(The only difference: I use the tenant admin, not the SharePoint Admin)

@abates100 I was able to follow the procedure using a SharePoint admin-only user.

@scanum


Improvements to the background workers

The main improvements are:

bulk add/remove from mmContainer
bulk eviction
better scheduling of background threads and calculating batch sizes
improved stats (including those from https://github.com/guptask/CacheLib/tree/dsa_bgknd_bulk_evictions)
ability for background workers to evict/promote without mark moving bit - we can use acquire instead

The results are - nearly 20% improvement in multi-tier (develop branch) performance with this config:
simple_tiers_test_bg.txt

This change is

@byrnedj  could you please split the changes logically into commits (and remove commits with fixes after review, etc.)? I would prefer not to squash all of them on merge, so that it's easier to upstream it.
Also, would it be possible to share the implementation of findEvictionBatch with findEviction? Or should we consider that after merging this and rebasing (since there are some change in upstream I think).

@byrnedj could you please split the changes logically into commits (and remove commits with fixes after review, etc.)? I would prefer not to squash all of them on merge, so that it's easier to upstream it.
Also, would it be possible to share the implementation of findEvictionBatch with findEviction? Or should we consider that after merging this and rebasing (since there are some change in upstream I think).

I have done so. Once the rebase is finished I will rebase this branch and we can merge it.

@byrnedj could you please split the changes logically into commits (and remove commits with fixes after review, etc.)? I would prefer not to squash all of them on merge, so that it's easier to upstream it.
Also, would it be possible to share the implementation of findEvictionBatch with findEviction? Or should we consider that after merging this and rebasing (since there are some change in upstream I think).

I have done so. Once the rebase is finished I will rebase this branch and we can merge it.

Sounds good. Regarding sharing the implementation - we can probably do it later, there might be some refactoring needed anyway or some comments from meta.


Update valid Protocol to include UDP

Allow UDP streams

https://github.com/j-holub/Node-MPV/pull/91
Solution is here ready for PR.

Oops meant for v2


Updated to node20 and dependencies

Closes #22

@adcreare https://github.com/checkdigit/hash/actions/runs/8442321597/job/23123476131 seems audit signature failed


support display id for data updates

tested with a composite track locally and successfully updated the track data after this change

Thanks so much @jordansafer!


Question about conn_str variable in _settings.py

Quick question about the settings.py file we need to update. It asks for the “URL database where submissions should be stored”. What is this in reference to and what purpose does it serve?
We don’t currently have our database systems in place, so is there a way to run the reporter.py script without this information? Currently, I’m getting a “Login failed” when I leave the default value in the conn_str variable.

Hi @melia-fernandez, thanks for submitting this. First, let's make sure the following assumptions are correct:

You have omop csv files ready.
You are running the reporter.py script in order to validate your csv files before submitting them via secure file transfer.

If so, settings.py will tell the tool where to find the local csv files and how to connect to the database where it can load the files, do some simple validation routines and log any errors it might encounter along the way. Those depend on operating system and the database type you are taretting. What OS are you on?
You should be able to set conn_str to a SQLite connection string if you don't have a full-fledged server handy. I will confirm this for you by the end of the week.

Hi @mark-velez,
You are correct on the two assumptions above. We are running Windows Server 2012.
Thanks,
Melia

@melia-fernandez try using the setting below. After you run reporter.py the file docs/_data/log.json will be updated with file validation checks that were performed.
conn_str = 'sqlite:///pmi_sprint_2.db'

@mark-velez looks like we were able to run it!
Attached is a copy of what the log.json file said. Looks like we had an error with one of the files...
va_log.txt

@melia-fernandez, that's great! Just resolve that issue (drug_exposure_start_date cannot be NULL) and submit the files as described here and VA will have met the requirement!
@cukarthik am I right that the job no longer executes automatically and that remaining sites must submit an issue here to have it run manually and show up in the report? I will close this issue once this is clear.

@mark-velez Thanks! We fixed the issue and got it to work. All tables were validated (text of the log file attached).
We are not able to transfer this data. Someone on my team tested the data transfer piece previously.
va_log.txt

@melia-fernandez I'm glad you were able to achieve a valid submission. Is the issue with transfer related to something on the VA side (e.g. firewall)? @cukarthik let me know any ideas of how we may give VA proper credit.

Hi @mark-velez Sorry for the delay! We cannot transfer the data for a couple of reasons, but mainly because it is real data and the ISA isn't in place.

Hi @melia-fernandez sorry for the delay as well! If it helps- the data sprints do not require real data (synthetic data would suffice).


[FEATURE] Allow custom certificates in Static Web Apps

Some customers uses a single corporate certificate chain and will want to be able to use it for this service as well as others, and managing different chains can become a burden, so, allowing them to customize the cert, perhaps even integrating that feature with azure keyvault is worth working on as a feature for Static Web Apps.

I fully support the request. In the company I work (+50K employees) this is a big problem that may lead to do not accept it.
And I am sure there are many more that would welcome such feature.
Looking forward for this feature. Thanks.

Any update on this?


Is tensorflow consuming much more memory than torch?

I am trying to replicate the stacked hourglass architecture which is implemented in torch, https://github.com/anewell/pose-hg-train/. However, I am unable to train it using settings in the opts.lua file which set the train batch size as 6, number of train iteration as 8000, test batch size as 1 and number of test iteration as 1000. I understand that I can reduce the batch size or iteration number to fit the network. However, I just want to know if tensorflow is consuming more memory than torch, if the same architecture and settings can be implemented in tensorflow.

They have similar memory usage in general, although there are some special cases where it may differ substantially. You can see track down memory usage by looking at memory allocator statistics you get when running with FULL_TRACING options (see https://github.com/tensorflow/tensorflow/issues/1824#issuecomment-225754659
)

do you what are the special cases?

calling tf.gradients on graph which has tf.while loop can take unexpectedly large amounts of memory

@yxchng : Were you able to obtain memory allocator statistics mentioned above?

@yaroslavvb : can you elaborate on using FULL_TRACING to get memory allocator stats?
I managed to get the timing information via:
from tensorflow.python.client import timeline
run_options = tf.RunOptions(trace_level=tf.RunOptions.FULL_TRACE)
run_metadata = tf.RunMetadata()
sess.run(some_stuff, options=run_options, run_metadata=run_metadata)

# for visualization
tl = timeline.Timeline(run_metadata.step_stats)
ctf = tl.generate_chrome_trace_format()
with open('timeline.json', 'w') as f:
    f.write(ctf)

But how would I assess the memory allocation from run_metadata?

If you print run_metadata, you'll see messages like this:
  output {
    tensor_description {
      dtype: DT_FLOAT
      shape {
      }
      allocation_description {
        requested_bytes: 4
        allocator_name: "cpu"
        ptr:<PHONE_NUMBER>
      }
    }
  }

That means 4 bytes got allocated
On Thu, Oct 20, 2016 at 5:17 AM, redst4r<EMAIL_ADDRESS>wrote:

@yaroslavvb https://github.com/yaroslavvb : can you elaborate on using
FULL_TRACING to get memory allocator stats?
I managed to get the timing information via:
from tensorflow.python.client import timeline
run_options = tf.RunOptions(trace_level=tf.RunOptions.FULL_TRACE)
run_metadata = tf.RunMetadata()
sess.run(some_stuff, options=run_options, run_metadata=run_metadata)
for visualization
tl = timeline.Timeline(run_metadata.step_stats)
ctf = tl.generate_chrome_trace_format()with open('timeline.json', 'w') as f:
f.write(ctf)
But how would I assess the memory allocation from run_metadata?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/4709#issuecomment-255089531,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABaHAUCSGUxmaSCC8P-Wonypmt8AT3nks5q11vVgaJpZM4KLzWI
.

You can also get raw memory allocator messages in your log like this:
http://stackoverflow.com/questions/36331419/tensorflow-how-to-measure-how-much-gpu-memory-each-tensor-takes/36505898#36505898
On Thu, Oct 20, 2016 at 10:17 AM, Yaroslav Bulatov<EMAIL_ADDRESS>wrote:

If you print run_metadata, you'll see messages like this:
  output {
    tensor_description {
      dtype: DT_FLOAT
      shape {
      }
      allocation_description {
        requested_bytes: 4
        allocator_name: "cpu"
        ptr:<PHONE_NUMBER>
      }
    }
  }

That means 4 bytes got allocated
On Thu, Oct 20, 2016 at 5:17 AM, redst4r<EMAIL_ADDRESS>wrote:

@yaroslavvb https://github.com/yaroslavvb : can you elaborate on using
FULL_TRACING to get memory allocator stats?
I managed to get the timing information via:
from tensorflow.python.client import timeline
run_options = tf.RunOptions(trace_level=tf.RunOptions.FULL_TRACE)
run_metadata = tf.RunMetadata()
sess.run(some_stuff, options=run_options, run_metadata=run_metadata)
for visualization
tl = timeline.Timeline(run_metadata.step_stats)
ctf = tl.generate_chrome_trace_format()with open('timeline.json', 'w') as f:
f.write(ctf)
But how would I assess the memory allocation from run_metadata?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/4709#issuecomment-255089531,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABaHAUCSGUxmaSCC8P-Wonypmt8AT3nks5q11vVgaJpZM4KLzWI
.

thanks for the hint, I'll play around with that

found this very convenient show_memory flag, which allows you to display mem-allocation over time in chrome-trace:
ctf = tl.generate_chrome_trace_format(show_memory=True)

@yxchng have you come to any actionable bugs or issues with memory usage after looking at it more?

@aselle I am busy with other stuff at the moment. I will try to look into it as soon as possible. Really sorry.

Automatically closing due to lack of recent activity, we will reopen if further information becomes available. Thanks!


Rebuild 2.0.1 with MKL on Windows

Rebuild 2.0.1 with MKL on Windows.
Depends on:

https://github.com/AnacondaRecipes/intel_repack-feedstock/pull/25

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/build.sh:189: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:78: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:104: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/build.sh:189: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:78: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:104: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/build.sh:189: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:78: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:104: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

2023-11-08T17:12:28.882993+00:00  | INFO     |     -- MKL_THREADING = OMP
2023-11-08T17:12:28.89854+00:00   | INFO     |     -- Looking for sys/types.h
2023-11-08T17:12:29.475091+00:00  | INFO     |     -- Looking for sys/types.h - found
2023-11-08T17:12:29.490638+00:00  | INFO     |     -- Looking for stdint.h
2023-11-08T17:12:30.085244+00:00  | INFO     |     -- Looking for stdint.h - found
2023-11-08T17:12:30.100899+00:00  | INFO     |     -- Looking for stddef.h
2023-11-08T17:12:30.599862+00:00  | INFO     |     -- Looking for stddef.h - found
2023-11-08T17:12:30.61547+00:00   | INFO     |     -- Check size of void*
2023-11-08T17:12:31.286684+00:00  | INFO     |     -- Check size of void* - done
2023-11-08T17:12:31.302313+00:00  | INFO     |     -- Checking for [mkl_intel_lp64 - mkl_intel_thread - mkl_core - libiomp5md]
2023-11-08T17:12:31.317932+00:00  | INFO     |     --   Library mkl_intel_lp64: C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/lib/mkl_intel_lp64_dll.lib
2023-11-08T17:12:31.335006+00:00  | INFO     |     --   Library mkl_intel_thread: C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/lib/mkl_intel_thread_dll.lib
2023-11-08T17:12:31.351598+00:00  | INFO     |     --   Library mkl_core: C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/lib/mkl_core_dll.lib
2023-11-08T17:12:31.368843+00:00  | INFO     |     --   Library libiomp5md: C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/lib/libiomp5md.lib
2023-11-08T17:12:31.389147+00:00  | INFO     |     -- Looking for cblas_sgemm
2023-11-08T17:12:32.009652+00:00  | INFO     |     -- Looking for cblas_sgemm - found
2023-11-08T17:12:32.12672+00:00   | INFO     |     -- MKL library found
2023-11-08T17:12:32.142344+00:00  | INFO     |     -- MKL libraries: C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/lib/mkl_intel_lp64_dll.lib;C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/lib/mkl_intel_thread_dll.lib;C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/lib/mkl_core_dll.lib;C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/lib/libiomp5md.lib
2023-11-08T17:12:32.159463+00:00  | INFO     |     -- MKL include directory: C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/include
2023-11-08T17:12:32.176694+00:00  | INFO     |     -- MKL OpenMP type: Intel
2023-11-08T17:12:32.192367+00:00  | INFO     |     -- MKL OpenMP library: C:/b/abs_ead5hcfhda/croot/pytorch_1699463340211/_h_env/Library/lib/libiomp5md.lib

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/build.sh:189: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:104: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/build.sh:189: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:104: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found


Original Sample Code is Innacurate

Challenge Waypoint: Iterate Odd Numbers With a For Loop has an issue.
User Agent is: Mozilla/5.0 (X11; CrOS x86_64 7520.63.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
In the sidebar text description of how to solve the waypoint it reads:
"Let's change our initialization and final-expression so we can count by odd numbers."
But it should read: "Let's change our initialization so we can count by odd numbers."
There's no need to change the final-expression to count by odd numbers, as changing the initialization to 1 will suffice.
My code:
var ourArray = [];

for (var i = 0; i < 10; i += 2) {
  ourArray.push(i);
}

var myArray = [];

// Only change code below this line.

for (var i = 1; i < 10; i += 2) {
  myArray.push(i);
}

// Only change code above this line.

if(typeof myArray !== "undefined"){(function(){return myArray;})();}

IMO, this is a problem with the original sample code, in the editor window (Can be seen if you do areset).
Instead of below
for (var i = 0; i < 10; i += 2)

it should be
for (var i = 0; i < 10; i += 1)

because the point of the exercise is to illustrate the significance of altering the loop iteration by changing the initialization and the final-expression values.

Good point, raisedadead. I've edited the subject text to reflect this.

I concur.  I'm editing these waypoints right now, so this will be resolved in the new Basic Javascript release.


Allow user to create new dataproject from AnnoRep

Use Case
As a user of AnnoRep I want to create a new dataproject without leaving the AnnoRep interface.
Solution
In UX testing people are getting fatigued by moving back and forth between new browser tabs ...
Instead of sending them to QDR to create a new data project, we could just allow them to fill out the required elements of a dataproject using a webform on AnnoRep. Since we have the user's credentials and API token, we could use the webform to create a new project in Dataverse.
Alternatives
NA

I understand the need to limit switching between tabs.
I want to piggy back on @adam3smith 's point. There should be a clear separation between QDR and AnnoRep. If users are allowed to create new data projects on QDR, the expectation would be that users would be able to edit the data project on QDR. If we port only some of functionalities of editing the data project to AnnoRep, it might create some confusion. If users are able to create a data project on AnnoRep, they might have expectations to edit the metadata, delete project, edit/modify/delete/preview data sources, and maybe all the other functionalities provided by QDR.
Plus, there might unnecessary and unwanted coupling between QDR and AnnoRep, code-wise. AnnoRep will copy some of code in QDR.


Better error output

🚀 Feature Proposal
Add the plugin name to the output of the errors
Motivation
Right now if a module need a fastify version the error is this one:

Error: fastify-plugin - expected '<2.12.0' fastify version, '2.12.0' is installed

But I don't know which plugin is throwing the error
Example

Error: fastify-module-name - expected '<2.12.0' fastify version, '2.12.0' is installed

+1 from me

+1, would you like to send a PR?


feat: introduce cache loaded extensions in OpenAPIDeserializer

This PR provides a cache mechanism that stores the extensions loaded per classloader.
Due to the caching mechanism the performance for loading the extensions (jsonSchemaParserExtensions) is improved.
This PR closes #1909

thanks!


[style]: Whole UI Needs Improvement #433

Hey @vivekBoii You have work really good but this is not we are looking for. This is issue already under process. First you have to ask for assigning the issue than start working on it.
Closing this, you can add your profile by opening a new PR.


Fix typo in _pkcs11.pyx

Changed typo on L380 from CK_OBJECT_HANDLE to CK_SESSION_HANDLE.
Resolves #147

Thanks!


Upgrade stellar-sdk to v11.0.0-beta.3

Preview is available here:http://stellar-demo-wallet-client-pr325.previews.kube001.services.stellar-ops.com/


fix(nullattributes): Accepting null attributes and eventTags

NULL support for attributes and eventTags.

build

@msohailhussain can you close this pr and open it against master?  thanks

@thomaszurkan-optimizely Closing this PR. And created new PR.
https://github.com/optimizely/objective-c-sdk/pull/335


A question about async await with native promise.(try to implement zone.js for async/await)

The following code
async function detect() { }
const r = detect();
const nativeThen = r.proto.then;
r.proto.then = function () {
console.log('promise.then');
return nativeThen.apply(this, arguments);
}
async function test1() {
console.log('before await');
const r = await test();
console.log('after await');
}
test1();
console.log('end');
// the output will be
// before await
// end
// promise.then, question is why promise.then is after end?
// after await
The nativePromise.then will be executed after end, I don't understand why, any help will be appreciated.
And What is the current status of zone proposal? Thanks!

This is because the Promise callbacks are always scheduled on the microtask queue. Which happens after the current execution context finishes.


While LZO compression is supported by the Parquet format in general, it is currently not supported by the C++ implementation.

I used Broker Load to import LZO compressed data on COS, reporting this exception.And when will LZO be supported

@Dshadowzh


Release Pull Request

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Question about alias map

Hi,
Thanks for your great work! Super cool.
I have one question about the alias map generation.
As I have seen in the alias2qids_kore50.json and alias2qids_rss500.json files, the same alias in different examples may have different candidate sets.
e.g. in alias2qids_kore50.json, the candidate list of "david_0" and "david_1" are not identical.
In details:
In "david_1" but not in "david_0":
{'Q5240660', 'Q5236763', 'Q5240530', 'Q16079082', 'Q27827705', 'Q17318723', 'Q18632066', 'Q5238957', 'Q768479', 'Q3017915', 'Q5239424', 'Q20684456', 'Q5234065', 'Q5234667', 'Q5230766', 'Q10264386', 'Q672856', 'Q1174097', 'Q5240118', 'Q583264'}
In "david_0" but not in "david_1":
{'Q312649', 'Q1173922', 'Q19668637', 'Q5236091', 'Q178517', 'Q2420499', 'Q353983', 'Q24248231', 'Q5239917', 'Q336640', 'Q5241350', 'Q184903', 'Q338628', 'Q2071', 'Q1175688', 'Q41564', 'Q1173934', 'Q214601', 'Q5236705', 'Q1177021'}
So I am wondering how was the candidates are generated? are they context dependent?
by the way, could you please explain the score (e.g. ["Q8016", 5947]) associated with each candidate entity? What does it mean and how does it is calculated?
Thanks a lot.

Hello! Great question.
So we do have a contextual candidate generator that we used for kore50 and rss500. This takes into account contextual similarities between an entity's Wikipedia page and the sentence itself. So because the sentences are different, the lists are different.
The score for a candidate is based on a few features that we used for this contextual generation: the similarity between the mention, the overall entity popularity, and the similarity between the sentence and the entity's Wikipedia page. We only use this score for filtering the lists.

@lorr1 Thanks for answer! How about the the score in data/wiki_entity_data/entity_mappings/alias2qids.json file? Is it generated by averaging the same alias-entity pairs in Wikipedia anchor texts?
Thanks.

So that one is used just for training so is not contextual. We could certainly make it that way (and are exploring these ideas!) but didn't use a contextual one for training. That score based on an overall entity's occurrence in Wikipedia. So it's a ranking based on entity popularity. Note that this is not conditioned on a specific alias - it's just overall entity popularity. We found that this was necessary when incorporating aliases from Wikidata that may never have been seen in Wikipedia yet still be valid aliases.

Great. Got it. Well understood. Thanks!


Migrate to docker compose v2

Migrate to docker compose v2

cc: @ucatbas

@shivam-sharma7 can you provide more context?

@ucatbas please give a read https://docs.docker.com/compose/releases/migrate/ and idea is we should be update with latest for future.

I'm aware of this change actually. According to their documentation, both naming conventions are supported. For the sake of readability in file names, we’ll continue using docker-compose.yml. You can refer to the specific documentation here: https://docs.docker.com/reference/cli/docker/compose/

I'm aware of this change actually. According to their documentation, both naming conventions are supported. For the sake of readability in file names, we’ll continue using docker-compose.yml. You can refer to the specific documentation here: https://docs.docker.com/reference/cli/docker/compose/

@ucatbas I actually investigate more and I found the docker compose v2 integrates into the Docker CLI platform not only this there are lot of things such as -> allows users to build, deploy, stop, or delete multiple containers simultaneously and Build multi-arch images with Compose. you can aslo check this- https://www.docker.com/blog/new-docker-compose-v2-and-v1-deprecation/


Podcast description is missing in RSS feed

Episodes 810 and 811 don't have a description in the RSS feed. It is empty:
<description><![CDATA[]]></description>

thanks a ton - getting our editor on it right now!

fixed! thanks again for the heads up

My pleasure!
Thank you for the awesome podcast!


.NET Core 3.0 and EF Core 3.0.0 support

The EF Core nuget packages needs to be updated to support .NET Core 3.0. When migrating from .NET Core 2.2 to 3.0 and EF Core to 3.0.0 assembly cannot be loaded:
System.TypeLoadException: Method 'get_Info' in type 'EntityFrameworkCore.Cacheable.CacheableOptionsExtension' from assembly 'EntityFrameworkCore.Cacheable, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' does not have an implementation.

yes, I have same issue. I have to remove this reference to upgrade EF Core to 3.0.

This is still an issue for .NET Core 3.1

Still a problem with this, I'm looking in implementation.

when we will get fix ?
or any other workaround for these issue ?

Any update on this?

Any update on this? I have same issue.

I fixed that. I replaced IDbContextOptionsExtension from library to custom and then update DbContext registration to next
 services.AddDbContext<ApplicationContext>(options =>             {                ....                 options.ReplaceService<IQueryCompiler, CustomQueryCompiler>();                 ((IDbContextOptionsBuilderInfrastructure)options).AddOrUpdateExtension(new DbCacheableOptionsExtension(new MemoryCacheProvider())); ....             });
`public class DbCacheableOptionsExtension : IDbContextOptionsExtension
{
ICacheProvider _cacheProvider;
internal DbCacheableOptionsExtension(ICacheProvider cacheProvider)
{
	_cacheProvider = cacheProvider;
}

public string LogFragment => $"Using {_cacheProvider.GetType().Name}";

public bool ApplyServices(IServiceCollection services)
{
	services.AddSingleton<ICacheProvider>(_cacheProvider);

	return false;
}

public long GetServiceProviderHashCode() => 0L;

public void Validate(IDbContextOptions options)
{
}

void IDbContextOptionsExtension.ApplyServices(IServiceCollection services)
{
	throw new System.NotImplementedException();
}

/// <summary>
///     The option set from the <see cref="DbContextOptionsBuilder.UseSecondLevelMemoryCache" /> method.
/// </summary>
public virtual ICacheProvider CacheProvider => _cacheProvider;

public DbContextOptionsExtensionInfo Info => throw new System.NotImplementedException();}`


Fix file uploading

Fixes #316
WhatsApp changed something again. I have no idea if I did this right, but it seems to work.

Thanks, It works

Is this branch going to be merged?

@tulir Thanks, that works! Can you tell us how did you get this solutions?

Basically just looked at what web.whatsapp.com did using firefox devtools:

query mediaConn is used, action encr_upload isn't, so the former is probably the replacement for the latter. It's sent unencrypted in the websocket, so you can easily see the request and response in the websocket message viewer.
the upload request itself only contained random bytes, so I guessed it's the raw encrypted data instead of multipart form data like before.
the URL was just first hostname returned by mediaConn and there was /mms/image after that. Not sure if the other hostnames that mediaConn return should be used in some cases.
there was no content-type header or f=j query param like before, so I removed those.
auth query param was the auth field returned by mediaConn.
token param looked like url-safe base64 and the old code had a base64 of the encrypted file sha256, so I tried passing that as the token and it worked.

is it me or thumbnails isn't working?

is it me or thumbnails isn't working?

Its working fine here.

Has this update been updated on the master yet?

Is it working with thumbnails! and when it will be available on master

@tulir
1- Is it working with thumbnails!
2- What about audio and other documents type?
since:

the URL was just first hostname returned by mediaConn and there was /mms/image after that. Not sure if the other hostnames that mediaConn return should be used in some cases.

Path:     fmt.Sprintf("/mms/image/%s", token)  why don't you use what filetype function which it is return the correct media path?
Whatsapp is using the following mms paths so please use the filetype function to determinate the correct path.
            audio: "/mms/audio",
            document: "/mms/document",
            gif: "/mms/gif",
            image: "/mms/image",
            ppic: "/pps/photo",
            product: "/mms/image",
            ptt: "/mms/ptt",
            sticker: "/mms/sticker",
            video: "/mms/video"

Other file types are working fine even with the wrong path (at least audio and documents), it's not like WhatsApp can see what type of data is inside the file. But yeah, those paths would make sense so I'll change it to use those.

@Rhymen hi.
I would like to ask you when this update will going to be merged

When will this get merged?

Thanks for the amazing work!

Dear all, i still get an error 404 while sending media.
Media sent successfully, but this strange, why i got this error....

Please update the latest release with these changes. 🙂
It took me 3 hrs to debug to find out that the version go get was fetching was the latest release and not from the master.
The current latest-release was done on 1st Jan 2020. But this error fix was merged on 8th Apr 2020. Please release a new update as this is breaking my app.

@Piyushhbhutoria Can you just clone the repo?
As for file uploading, I've noticed I'm still unable to send GIFs, not sure if that's in the pipeline or if I should submit a new feature request.


Display story details

title
description
assignee
creator
comments
attachments
labels
estimate

Attachments may be difficult, seems like the get/show is missing from their official lib: https://github.com/clubhouse/clubhouse-lib/blob/master/src/index.js


Introduce fetch all timeout (closes #721)

Hmmm I can't do a fast-forward pull 🤔

Both git machete and git status tell that local branch is behind remote... yet an attempt to do a Pull current branch right after doing a Fetch tells me that the merge would be non-fast-forward 😯
Can you see any obvious reason for that? I can provide more details on the repo state if needed


Add more user management capabilities in the CLI

Describe the problem you'd like to have solved
Please add ability to search and delete users using the CLI.
While developing an application, it is very useful to quickly search and delete users. I'd like to request the following functionality:

Search users by their email, Auth0 ID or their name
Delete a user with the given Auth0 ID

Describe the ideal solution
Search users:
auth0 users search --email<EMAIL_ADDRESS>auth0 users search auth0|123456
auth0 users search --name "John Doe"
Delete users:
auth0 users delete auth0|123456
Alternatives and current work-arounds
Use the Auth0 dashboard, which is much slower than using the CLI.
Additional context
None.

Hi @haroldadmin, thanks for requesting this feature. It certainly is in our roadmap, though there's no ETA.
I'll leave this issue open to track it.

Implemented by #279.

@haroldadmin this is now out on v0.7.0.


Timestamps are marked unsigned

When selecting from a timestamp column, the result is marked unsigned, triggering failwith "unexpected unsigned type" in Field.convert_unsigned.  To reproduce it, create a table:
create table test (t timestamp);
insert into test values (now());

and run
OCAML_MARIADB_QUERY="SELECT ?, t FROM test" _build/examples/blocking/blocking_example.native

This would solve this case at least,
diff --git a/lib/field.ml b/lib/field.ml
index 73eca28..cbb0488 100644
--- a/lib/field.ml
+++ b/lib/field.ml
@@ -90,6 +90,7 @@ let convert_unsigned field = function
   | `Short -> `Int (Unsigned.UInt.to_int (cast_to uint field))
   | `Int24 | `Long -> `Int (Unsigned.UInt32.to_int (cast_to uint32_t field))
   | `Long_long -> `Int (Unsigned.UInt64.to_int (cast_to uint64_t field))
+  | `Timestamp as kind -> `Time (to_time field kind)
   | _ -> failwith "unexpected unsigned type"

 let value field =

though maybe it would be better to dispatch on both datatype and signedness in one, or datatype optionally followed by signedness.

It seems that timestamps are always marked as unsigned on the server (in sql/field.cc):
Field_timestamp::Field_timestamp(...)
...
{
    /* For 4.0 MYD and 4.0 InnoDB compatibility */
    flags|= UNSIGNED_FLAG;
    ....

And in the same file, in the Create_field::check method:
  case MYSQL_TYPE_TIMESTAMP:
  case MYSQL_TYPE_TIMESTAMP2:
    ...
    flags|= UNSIGNED_FLAG;
    break;

which is not done for other date types. So it seems that simply moving the Timestamp case to convert_unsigned would be safe.
However, just skimming through that file I noticed that MYSQL_TYPE_BIT seems to always be set to unsigned too... And since this seems to only be documented in code, I think I'll go with your idea of dispatching on type and signedness.

Commit c0a2c43 makes that change.

I'll try to make a new release by the end of the week.
Thanks for your work in finding and fixing these bugs. I haven't had a chance to use the library in production yet as other things got in the way, so you're saving me a lot of time here :)

Great, I expect to follow up with a caqti release with mariadb support shortly after.

I've just submitted 0.8.0 to the opam repo. Should be available soon.


Control available scene modes in SceneModePicker

The BaseLayerPicker allows you to pass an array of which imagery layers should be available. It would be nice if the SceneModePicker had a similar option.
This was requested on the forum. Currently it's hardcoded to show all 3. I think it should be easy to add an option to control this. I think you'd need to edit https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/Widgets/SceneModePicker/SceneModePicker.js and https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/Widgets/SceneModePicker/SceneModePickerViewModel.js.

Here's a Sandcastle with Columbus View turned off.  Be sure to check out the code.

I'll reproduce it here for better visibility.
<style>
    @import url(../templates/bucket.css);

    .cesium-sceneModePicker-dropDown-icon[data-bind*="COLUMBUS_VIEW"] {
        display: none;
    }

    /* This one is for 2D mode.
    .cesium-sceneModePicker-dropDown-icon[data-bind*="SCENE2D"] {
        display: none;
    }
    */

</style>

I had quite the experience gazing in disbelief at the feature working with no custom code, until it occurred to me check the CSS!

The CSS is a good short-term workaround, but it would be easy for the SceneModePickerViewModel to have booleans to control whether each mode is included or not.

Thank you for the CSS example!   Unfortunately, I can't replicate it in a production webpack environment.   (There is no bucket.css) - I use require('cesium/Widgets/widget.css') in my javascript file, and my own CSS file, and adding
.cesium-sceneModePicker-dropDown-icon[data-bind*="COLUMBUS_VIEW"] {
    display: none;
}

to my CSS file does not remove the option from my drop down list.    The CSS Solution would be fine for me, through an API solution would work just as well.

@ognjenb If you right-click the offending button and hit "inspect", and then make sure the <button element is selected, can you confirm that (a) it includes class cesium-sceneModePicker-dropDown-icon and (b) it includes a data-bind attribute that mentions COLUMBUS_VIEW?  If both of those things are true, the CSS rule should apply to the button element.  Is another rule overriding it?

It does have the class
class="cesium-button cesium-toolbar-button cesium-sceneModePicker-dropDown-icon cesium-scemeModePicker-visible"
In the data-bind section it has a lot of things that say things like sceneMode === _sceneMode.COLUMBUS_VIEW or !==  and the title of course of the button is "Columbus View".
I don't have any rules overriding any of the default widgets other then the ones disabling some of them from the viewer.

Another thing you can try @owensjp is to get the button with JS and modify its CSS that way. For example, I used the browser inspector get the CSS selector for the button, and then the following line in JS can hide it:
document.querySelector("#cesiumContainer > div > div.cesium-viewer-toolbar > span.cesium-sceneModePicker-wrapper.cesium-toolbar-button > button:nth-child(4)").style.display = 'none';

Thanks Omar!  That worked!


Support for Pathfinder 2e

Just wanted to ask on progress on this? It would be highly beneficial for the PF2e system as there is no other module that I am aware that could do a functionality like this for it.

Alright... If you could, at least take it off of the "In Progress" category given that development then.

As I said, I will get around to it when I get a chance.

Alright... If you could, at least take it off of the "In Progress" category given that development then.
Never found any resistance to this module being on PF2e, just a lot of requests, but if that was the reaction, sure.
EDIT: Ok, found it, while it is from Drental, it was an answer to "would PF2e benefit from this" and the answer being "No, this will be hard to do". Not a resounding no that it won't be useful, even quoting

"If you got Ideas on how to handle that of course, Item macros are what you need to make some very very neat shinies work"

and himself saying that he's biased.

"Yeah, nice stuff could be done. I personally am biased against it, so I should stop around "trip isn't an item either, but rage is" - there's certainly merit in this."

I will be tackling this for 10.X as long as the system isn't completely broken for it.
I will probably be in contact with you MrVauxs for any questions.


Update the naming scheme of RDF and SHACL

Previously, the naming scheme of the RDF and SHACL schemas were
inconsistent with the JSON and XML schemas in their naming of
abbreviations.
This patch fixes the naming by applying the same rules on the RDF
and SHACL schemas. Furthermore we update the examples.
This fixes #263.

@sebbader-sap please double-check my answers & open the conversations again if necessary.
@s-heppner the schemas and the test data have been regenerated in aas-core-codegen and testgen repositories so you can update this pull request.

I updated the schemata from aas-core, using

aas-core-meta 8f18a8c and
aas-core-codegen 0e16f63.

To my understanding, this should make this PR ready to be merged.

@s-heppner both this PR and #268 look good to me - but before merging let's quickly agree on the release steps right after. We should immediately go for a V3.0.7 release, right? If so, we need to prepare an update of the release section in the README including the new release links.

Imo, we should also definitely include #269 in the release, since that fixes a major bug in the XSD.
Other than that, I don't have a strong opinion on release numbering (though 3.0.7 seems sensible). Is there anyone else we should clarify our further action with?


Added skip dialog for seed backup step

Ubuntu 18.10 Local Build

[x] Skip mnemonic confirmation
[x] Incomplete seed verification returns warning message and return to verification page
[x] Complete seed verification boots up wallet

Will approve it later after finish testing on windows.

A new build of 5fb05b4d5520cdf714b093829a0dde42d30a02a1 has completed succesfully!
Binaries available at https://build.nav.community/binaries/mnemonic-import-gui-changes

tested osx gitian


Oracle user info is not accurate

Description
DBeaver does not accurately display Oracle User information.  For example, the Lock date:
Security->Users->[user id]->View User
Select u., v.
from sys.DBA_USERS u, sys.v_$pwfile_users v
where u.username = 'MDMCUBE'
and u.username = v.username(+);

DBeaver Version
23.1.2
Operating System
Windows 10 Enterprise
Database and driver
Oracle
oracle.jdbc.OracleDriver
Steps to reproduce

connect to an Oracle database
Navigate to Security->Users->[choose a locked user id]->View User
Notice the Lock Date is not filled
execute the query below for the same user id
Select u., v.
from sys.DBA_USERS u, sys.v_$pwfile_users v
where u.username = :lockeduser
and u.username = v.username(+);

Additional context
No response

Hello @Jasonlawsondukeenergy
Could you please try to turn on this setting and recheck your User tab info?

Thank you for the quick response!  That resolved the issue.
-Jason
From: Anastasiya @.>
Sent: Tuesday, October 17, 2023 5:12 AM
To: dbeaver/dbeaver @.>
Cc: Lawson, Jason @.>; Mention @.>
Subject: [EXTERNAL] Re: [dbeaver/dbeaver] Oracle user info is not accurate (Issue #21545)
*** CAUTION! EXTERNAL SENDER *** STOP. ASSESS. VERIFY!! Were you expecting this email? Are grammar and spelling correct? Does the content make sense? Can you verify the sender? If suspicious report it, then do not click links, open attachments or enter your ID or password.
Hello @Jasonlawsondukeenergyhttps://github.com/Jasonlawsondukeenergy
Could you please try to turn on this setting and recheck your User tab info?
[2023-10-17 12_10_15-Connect to a database]https://user-images.githubusercontent.com/45152336/275777550-d9648a13-defc-4adb-acbb-f4adf8a5952c.png
—
Reply to this email directly, view it on GitHubhttps://github.com/dbeaver/dbeaver/issues/21545#issuecomment-1766001386, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDKCVEO5PUYSOWSX7VM3WODX7ZDVDAVCNFSM6AAAAAA6CQUDKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRWGAYDCMZYGY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>