Crashing when set in distributed multi-node environment

We have a 15 node cluster where swoosh is available on a multitude of the nodes, however when one node crashes or there's a few going down and coming up, other nodes that we're testing with (that are literally doing nothing but idling) get crashed by swoosh and taken down which in turn crashes the entire node.
[info] global: Name conflict terminating {Swoosh.Adapters.Local.Storage.Memory, #PID<42923.3171.0>}
[info] global: Name conflict terminating {Swoosh.Adapters.Local.Storage.Memory, #PID<42922.3174.0>}
[info] Application swoosh exited: shutdown
{"Kernel pid terminated",application_controller,"{application_terminated,swoosh,shutdown}"}
Kernel pid terminated (application_controller) ({application_terminated,swoosh,shutdown})

We're not using swoosh in any way on the other nodes so I'm going to remove the dependency from there, but never the less this is strange behaviour I wanted to report.
This is probably related to #333

Midnight in Australia ATM, I'll get to this tomorrow. Feel free to ping me if I forget.

🙏  no worries

Is there anyway to provide different names to the Swoosh.Adapters.Local.Storage.Memory when clustering nodes?

Nope. There's no point doing it. It's for dev only.

Thanks. I'll have to figure out how to disable swoosh for certain development and tests.

For specific cases you can disable the local memory process with https://github.com/swoosh/swoosh#production


Blazor Client - "Unable to render component 14" error with deferred .OrderByDescending evaluation

Consider this code:
@foreach (var option in optionsVotes.OrderByDescending(i => i.Key))             {
Option: @option.Key Votes: @option.Value
             }
optionVotes is a dictionary<string, int>
Here it doesn't work and says in console something like "unable to render component 14". Then I moved this code to @code section and looped through a ready to consume IEnumerable (i.e without calling any methods) like that:
@foreach (var option in optionsVotes)             {
Option: @option.Key Votes: @option.Value
             }
it started to work. However, it's not only about moving it to @code section. In @code section, I also added .ToArray() after .OrderByDescending. So maybe the problem lies in deferred evaluation.
For more details, you can compare there two versions of my .razor page file:
version 1 - not working
version 2 - working

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal project (ideally a GitHub repo) that illustrates the problem.

Unfortunately I couldn't attach the project as it is too big in terms of size. It also contains more than a hundred files, so I couldn't upload it as a new public repository either. However, you can find links to the page code in the issue description, with non-working and working versions, respectively. You can skip the api call in the code and mock it with ready-to-use values. It won't work that way either. You can also ignore all fields except for "optionVotes".

We tried using the first app and it works fine by default. Your suspicions about deferred evaluations being problematic might be it. If you still think this is specific to Blazor, feel free to reply here and we can try and help.

Hello @pranavkm
here you have the github repo for the project this issue was spotted in: Repo
The file you should look for is located at this path: TempRepoForBlazorIssue/Votings/Votings/Client/Pages/VotingState.razor


Stackoverflow occurred (difficult to diagnose) when accidentally leaving .sql suffix off file.

Environment
Linux
Liquibase Version:  4.8.0
Liquibase Integration & Version:  CLI
Liquibase Extension(s) & Version:
Database Vendor & Version:  postgres
Operating System Type & Version:   Linux
Description
I have been maintaining a set of SQL change logs, I failed to put an ".sql" suffix on one of the change logs.  Note the topmost change log was specified like this:
databaseChangeLog:
  - includeAll:
      path: changelogs

which recursively searches the "./changelogs/" directory.
I placed a "--liquibase formatted sql" changelog in this directory, without the ".sql" suffix.
The console reported this rather unhelpful error.
Unexpected error running Liquibase: Unknown reason

Inspecting the log, I saw a stackoverflow with thousands of recursions here:
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:302)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
	at liquibase.resource.ClassLoaderResourceAccessor.listFromClassLoader(ClassLoaderResourceAccessor.java:312)
        ...

Ideally this should fail gracefully, or report some error.   I believe this should be easily reproducible.

@jpz Thanks for the suggestion! We will look into improving the error. Definitely would be helpful.

Following the steps you listed I tried having 2 changelogs with the same changeset, one with .sql suffix and other one with .txt suffix, didnt get the same error, and got a warning.
[2022-07-25 12:43:10] INFO [liquibase.changelog] Reading resource: changelogs/test.sql
[2022-07-25 12:43:10] INFO [liquibase.changelog] Reading resource: changelogs/test2.txt
[2022-07-25 12:43:10] WARNING [liquibase.changelog] included file mchangelog.postgresql.yml/changelogs/test2.txt is not a recognized file type

Maybe it got fixed or has to do with the specific content  of your changelog.
If you keep having the same issue, can you share your full stack trace? Thanks!


Where to enter

Hi, I wonder where to enter the code to verify the installation. I'm a freshman here! Looking forward to your reply!

Looks like you figured this out based on the other issue


feat: show challenges count

Hi, great project.
I think showing the number of unsolved challenges of a user would be a useful feature.
(EDIT: Also added the count on compare)

Hi @ndavd! Thanks for the contribution. Could you kindly show an image of the new feature in action? I tried to clone your repository and run it locally to see the change, but the website was hanging (which wasn't happening with the main branch)

Hi @diksown! Updating the branch against main fixed it. Try it now, please.


(RFC) refactor: new linting rules

This PR tweaks the linting rules mainly to help readability and enforce consistency across the Dysnomia codebase.
What's changed as of now

strict is now enforced as an error - this means that strict mode will be consistently required
eqeqeq is also now enforced as an error to help avoid using loose == which is slower (== null is still allowed)
spacing between keywords is now enforced - this is mainly to combat these } catch{ constructs introduced in #46, secondly because I like it more
anything else? open to comments and suggestions on what rules to enable/disable/fine-tune

Regarding the imposition of "use strict", perhaps this is useful.

Hello! Sorry that it took me a bit to reach out on this.
As far as the "use strict"; requirement is concerned, it is going to stay as most code in the library is a part of a class, and class bodies per the ECMAScript standard are already strict mode code. So I believe it only makes sense to require it across the whole code base when it is already implicitly the majority.


Unfinished UI in the title bar (new tab icon and drop down)

There seem to be unfinished UI elements in the tile bar, namely new tab (plus icon) and dropdown icon. As I understand it, the core team is going for chromium style title bar - if so, there should be a uniform padding and the icon itself should have a highlighted square with rounded corner in background when hovered,

instead it appears there is no space netween the existing tabs and new tab icon when hovered or a clear background.

Also, there seem to be a weird bug (maybe?) when I click on the dropdown as both the new tab and dropdown are highlighted with an unusual background.

Environment
Windows build number: Windows 10 version 2004, build 21277.1000
Windows Terminal version (if applicable): Windows Terminal Preview / Version: 1.5.3242.0
Steps to reproduce
Simply click on plus icon, or dropdown
Expected behavior

Actual behavior

No, that UI is definitely finished. The split button control in the Windows UI toolkit highlights both halves when the dropdown is open, and it has tab styling so that it lines up with each tab (including spacing). Thanks for the report!

But the new tab overlaps or touches the existing tabs, shouldn't there be some padding. I mean there is a clear space separating new tab icon and dropdown. I mean it looks bad, should I expect changes to UI anytime soon?


Add ThreadX_RTApp_MT3620_AzureRTOS

@aiden-ct Fixed a bug now I can see printed message. please verify

@aiden-ct Fixed a bug now I can see printed message. please verify

Hi @xiongyu0523 - yes it works now. Just a couple of minor issues, otherwise looks good.
Cheers!


CI: K8sServicesTest Checks graceful termination of service endpoints Checks if terminating service endpoint doesn't serve new connections: Pods [app=graceful-term-server] failed to come up

Test Name
Suite-k8s-1.22.K8sServicesTest Checks graceful termination of service endpoints Checks if terminating service endpoint doesn't serve new connections

Failure Output
Pods [app=graceful-term-server] failed to come up

Stack Trace
/home/jenkins/workspace/Cilium-PR-K8s-1.22-kernel-4.19/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:465
Pods [app=graceful-term-server] failed to come up
Expected
    <*errors.errorString | 0xc0009b1780>: {
        s: "timed out waiting for pods with filter -l app=graceful-term-server to be ready: 4m0s timeout expired",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-K8s-1.22-kernel-4.19/src/github.com/cilium/cilium/test/k8sT/Services.go:1649

Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Cilium pods: [cilium-72jc6 cilium-qfjp2]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod   Ingress   Egress
Cilium agent 'cilium-72jc6': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 28 Failed 0
Cilium agent 'cilium-qfjp2': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 24 Failed 0
Cilium pods: [cilium-72jc6 cilium-qfjp2]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod   Ingress   Egress
Cilium agent 'cilium-72jc6': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 28 Failed 0
Cilium agent 'cilium-qfjp2': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 24 Failed 0

Standard Error
19:59:49 STEP: Running BeforeEach block for EntireTestsuite K8sServicesTest Checks graceful termination of service endpoints
19:59:49 STEP: WaitforPods(namespace="default", filter="-l app=graceful-term-server")
20:03:49 STEP: WaitforPods(namespace="default", filter="-l app=graceful-term-server") => timed out waiting for pods with filter -l app=graceful-term-server to be ready: 4m0s timeout expired
20:03:49 STEP: cmd: kubectl describe pods -n default -l app=graceful-term-server
Exitcode: 0
Stdout:

Stderr:
 	 No resources found in default namespace.

FAIL: Pods [app=graceful-term-server] failed to come up
Expected
    <*errors.errorString | 0xc0009b1780>: {
        s: "timed out waiting for pods with filter -l app=graceful-term-server to be ready: 4m0s timeout expired",
    }
to be nil
20:03:49 STEP: Running JustAfterEach block for EntireTestsuite K8sServicesTest
===================== TEST FAILED =====================
20:03:49 STEP: Running AfterFailed block for EntireTestsuite K8sServicesTest Checks graceful termination of service endpoints
cmd: kubectl get pods -o wide --all-namespaces
Exitcode: 0
Stdout:
 	 NAMESPACE           NAME                              READY   STATUS      RESTARTS   AGE     IP              NODE   NOMINATED NODE   READINESS GATES
	 cilium-monitoring   grafana-5747bcc8f9-sxxcx          0/1     Running     0          28m     <IP_ADDRESS>        k8s2   <none>           <none>
	 cilium-monitoring   prometheus-655fb888d7-mkrgh       1/1     Running     0          28m     <IP_ADDRESS>       k8s2   <none>           <none>
	 default             graceful-term-client              0/1     Completed   0          4m17s   <IP_ADDRESS>      k8s2   <none>           <none>
	 default             testclient-5wmmb                  1/1     Running     0          4m17s   <IP_ADDRESS>      k8s1   <none>           <none>
	 default             testclient-8hpzj                  1/1     Running     0          4m17s   <IP_ADDRESS>       k8s2   <none>           <none>
	 kube-system         cilium-72jc6                      1/1     Running     0          4m42s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         cilium-operator-98689654b-bxq7w   1/1     Running     0          4m42s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         cilium-operator-98689654b-f4pf4   1/1     Running     0          4m42s   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         cilium-qfjp2                      1/1     Running     0          4m42s   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         coredns-69b675786c-vs9sc          1/1     Running     0          4m31s   <IP_ADDRESS>       k8s2   <none>           <none>
	 kube-system         etcd-k8s1                         1/1     Running     0          31m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-apiserver-k8s1               1/1     Running     0          31m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-controller-manager-k8s1      1/1     Running     0          31m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-proxy-crhcw                  1/1     Running     0          31m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-proxy-drzgr                  1/1     Running     0          29m     <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         kube-scheduler-k8s1               1/1     Running     0          31m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         log-gatherer-cpvhz                1/1     Running     0          28m     <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         log-gatherer-mlcb7                1/1     Running     0          28m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         registry-adder-65bc6              1/1     Running     0          29m     <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         registry-adder-76tml              1/1     Running     0          29m     <IP_ADDRESS>   k8s1   <none>           <none>

Stderr:

Fetching command output from pods [cilium-72jc6 cilium-qfjp2]
cmd: kubectl exec -n kube-system cilium-72jc6 -c cilium-agent -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend              Service Type   Backend
	 1    <IP_ADDRESS>:443         ClusterIP      1 => <IP_ADDRESS>:6443
	 2    <IP_ADDRESS>:9153       ClusterIP      1 => <IP_ADDRESS>:9153
	 3    <IP_ADDRESS>:53         ClusterIP      1 => <IP_ADDRESS>:53
	 4    <IP_ADDRESS>:3000    ClusterIP
	 5    <IP_ADDRESS>:9090      ClusterIP      1 => <IP_ADDRESS>:9090
	 6    <IP_ADDRESS>:8081   ClusterIP

Stderr:

cmd: kubectl exec -n kube-system cilium-72jc6 -c cilium-agent -- cilium bpf lb list
Exitcode: 0
Stdout:
 	 SERVICE ADDRESS       BACKEND ADDRESS
	 <IP_ADDRESS>:9153       <IP_ADDRESS>:9153 (2)
	                       <IP_ADDRESS>:0 (2) [ClusterIP, non-routable]
	 <IP_ADDRESS>:443         <IP_ADDRESS>:6443 (1)
	                       <IP_ADDRESS>:0 (1) [ClusterIP, non-routable]
	 <IP_ADDRESS>:3000    <IP_ADDRESS>:0 (4) [ClusterIP, non-routable]
	 <IP_ADDRESS>:9090      <IP_ADDRESS>:0 (5) [ClusterIP, non-routable]
	                       <IP_ADDRESS>:9090 (5)
	 <IP_ADDRESS>:8081   <IP_ADDRESS>:0 (6) [ClusterIP, non-routable]
	 <IP_ADDRESS>:53         <IP_ADDRESS>:53 (3)
	                       <IP_ADDRESS>:0 (3) [ClusterIP, non-routable]

Stderr:

cmd: kubectl exec -n kube-system cilium-qfjp2 -c cilium-agent -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend              Service Type   Backend
	 1    <IP_ADDRESS>:9090      ClusterIP      1 => <IP_ADDRESS>:9090
	 2    <IP_ADDRESS>:443         ClusterIP      1 => <IP_ADDRESS>:6443
	 3    <IP_ADDRESS>:53         ClusterIP      1 => <IP_ADDRESS>:53
	 4    <IP_ADDRESS>:9153       ClusterIP      1 => <IP_ADDRESS>:9153
	 5    <IP_ADDRESS>:3000    ClusterIP
	 6    <IP_ADDRESS>:8081   ClusterIP

Stderr:

cmd: kubectl exec -n kube-system cilium-qfjp2 -c cilium-agent -- cilium bpf lb list
Exitcode: 0
Stdout:
 	 SERVICE ADDRESS       BACKEND ADDRESS
	 <IP_ADDRESS>:443         <IP_ADDRESS>:6443 (2)
	                       <IP_ADDRESS>:0 (2) [ClusterIP, non-routable]
	 <IP_ADDRESS>:9090      <IP_ADDRESS>:9090 (1)
	                       <IP_ADDRESS>:0 (1) [ClusterIP, non-routable]
	 <IP_ADDRESS>:9153       <IP_ADDRESS>:0 (4) [ClusterIP, non-routable]
	                       <IP_ADDRESS>:9153 (4)
	 <IP_ADDRESS>:3000    <IP_ADDRESS>:0 (5) [ClusterIP, non-routable]
	 <IP_ADDRESS>:8081   <IP_ADDRESS>:0 (6) [ClusterIP, non-routable]
	 <IP_ADDRESS>:53         <IP_ADDRESS>:0 (3) [ClusterIP, non-routable]
	                       <IP_ADDRESS>:53 (3)

Stderr:

===================== Exiting AfterFailed =====================
===================== TEST FAILED =====================
20:04:01 STEP: Running AfterFailed block for EntireTestsuite K8sServicesTest
cmd: kubectl get pods -o wide --all-namespaces
Exitcode: 0
Stdout:
 	 NAMESPACE           NAME                              READY   STATUS      RESTARTS   AGE     IP              NODE   NOMINATED NODE   READINESS GATES
	 cilium-monitoring   grafana-5747bcc8f9-sxxcx          0/1     Running     0          28m     <IP_ADDRESS>        k8s2   <none>           <none>
	 cilium-monitoring   prometheus-655fb888d7-mkrgh       1/1     Running     0          28m     <IP_ADDRESS>       k8s2   <none>           <none>
	 default             graceful-term-client              0/1     Completed   0          4m30s   <IP_ADDRESS>      k8s2   <none>           <none>
	 default             testclient-5wmmb                  1/1     Running     0          4m30s   <IP_ADDRESS>      k8s1   <none>           <none>
	 default             testclient-8hpzj                  1/1     Running     0          4m30s   <IP_ADDRESS>       k8s2   <none>           <none>
	 kube-system         cilium-72jc6                      1/1     Running     0          4m55s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         cilium-operator-98689654b-bxq7w   1/1     Running     0          4m55s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         cilium-operator-98689654b-f4pf4   1/1     Running     0          4m55s   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         cilium-qfjp2                      1/1     Running     0          4m55s   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         coredns-69b675786c-vs9sc          1/1     Running     0          4m44s   <IP_ADDRESS>       k8s2   <none>           <none>
	 kube-system         etcd-k8s1                         1/1     Running     0          32m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-apiserver-k8s1               1/1     Running     0          32m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-controller-manager-k8s1      1/1     Running     0          32m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-proxy-crhcw                  1/1     Running     0          31m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-proxy-drzgr                  1/1     Running     0          29m     <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         kube-scheduler-k8s1               1/1     Running     0          32m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         log-gatherer-cpvhz                1/1     Running     0          29m     <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         log-gatherer-mlcb7                1/1     Running     0          29m     <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         registry-adder-65bc6              1/1     Running     0          29m     <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         registry-adder-76tml              1/1     Running     0          29m     <IP_ADDRESS>   k8s1   <none>           <none>

Stderr:

Fetching command output from pods [cilium-72jc6 cilium-qfjp2]
cmd: kubectl exec -n kube-system cilium-72jc6 -c cilium-agent -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend              Service Type   Backend
	 1    <IP_ADDRESS>:443         ClusterIP      1 => <IP_ADDRESS>:6443
	 2    <IP_ADDRESS>:9153       ClusterIP      1 => <IP_ADDRESS>:9153
	 3    <IP_ADDRESS>:53         ClusterIP      1 => <IP_ADDRESS>:53
	 4    <IP_ADDRESS>:3000    ClusterIP
	 5    <IP_ADDRESS>:9090      ClusterIP      1 => <IP_ADDRESS>:9090
	 6    <IP_ADDRESS>:8081   ClusterIP

Stderr:

cmd: kubectl exec -n kube-system cilium-72jc6 -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                                  IPv6       IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 840        Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s2                                                                           ready
	                                                            reserved:host
	 926        Disabled           Disabled          52005      k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system   fd02::28   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=coredns
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=kube-dns
	 2475       Disabled           Disabled          4          reserved:health                                                              fd02::f3   <IP_ADDRESS>   ready
	 3783       Disabled           Disabled          12880      k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default       fd02::a2   <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDSClient

Stderr:

cmd: kubectl exec -n kube-system cilium-qfjp2 -c cilium-agent -- cilium service list
Exitcode: 0
Stdout:
 	 ID   Frontend              Service Type   Backend
	 1    <IP_ADDRESS>:9090      ClusterIP      1 => <IP_ADDRESS>:9090
	 2    <IP_ADDRESS>:443         ClusterIP      1 => <IP_ADDRESS>:6443
	 3    <IP_ADDRESS>:53         ClusterIP      1 => <IP_ADDRESS>:53
	 4    <IP_ADDRESS>:9153       ClusterIP      1 => <IP_ADDRESS>:9153
	 5    <IP_ADDRESS>:3000    ClusterIP
	 6    <IP_ADDRESS>:8081   ClusterIP

Stderr:

cmd: kubectl exec -n kube-system cilium-qfjp2 -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                                              IPv6        IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 2265       Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s1                                                                        ready
	                                                            k8s:node-role.kubernetes.io/control-plane
	                                                            k8s:node-role.kubernetes.io/master
	                                                            k8s:node.kubernetes.io/exclude-from-external-load-balancers
	                                                            reserved:host
	 3332       Disabled           Disabled          4          reserved:health                                                          fd02::13b   <IP_ADDRESS>    ready
	 3572       Disabled           Disabled          12880      k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=default   fd02::10d   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=default
	                                                            k8s:zgroup=testDSClient

Stderr:

===================== Exiting AfterFailed =====================
20:04:12 STEP: Running AfterEach for block EntireTestsuite

[[ATTACHMENT|e1d5072f_K8sServicesTest_Checks_graceful_termination_of_service_endpoints_Checks_if_terminating_service_endpoint_doesn't_serve_new_connections.zip]]
20:04:14 STEP: Running AfterAll block for EntireTestsuite K8sServicesTest Checks graceful termination of service endpoints

Resources

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.22-kernel-4.19/401/testReport/junit/Suite-k8s-1/22/K8sServicesTest_Checks_graceful_termination_of_service_endpoints_Checks_if_terminating_service_endpoint_doesn_t_serve_new_connections/
ZIP file(s):

Anything else?
No response

I hit this in a PR (#18448), but only for the first time now after running these tests several times over the last couple of days.
I see this in the kubectl get pods output:
	 default             graceful-term-client              0/1     Completed   0          4m17s   <IP_ADDRESS>      k8s2   <none>           <none>

Is it possible that the previous test didn't fully clean up this Completed pod and that somehow disrupts this test from successfully provisioning the graceful termination client pod?
cc @aditighag

My current theory is that this is not a problem on master because the AfterEach of the Describe for this test will ensure that the pods are removed after the individual It tests. However, PR #18448 moved this into an AfterAll in the Context of this specific test. This commit will switch that over to an AfterEach and hopefully address the issue. https://github.com/cilium/cilium/pull/18448/commits/d4739ad757d8d84dd65302e0e85e985b51198d69

Believed to be fixed, please reopen / ping if you observe this in future.


Hook up skip token handling

Coverage increased (+0.005%) to 99.738% when pulling ddd125ff82dfb9790a7ba9b75448e4f4eae17350 on CyberiaResurrection:HookUpSkipTokenHandling into 5e1fd5b564057f8479cfeff5f3ac385bb5de578b on Algo-Web:master.

Coverage increased (+0.005%) to 99.738% when pulling fb20b31bc439648126b9da81cbec68e5e3efff35 on CyberiaResurrection:HookUpSkipTokenHandling into 5e1fd5b564057f8479cfeff5f3ac385bb5de578b on Algo-Web:master.


updated gke-istio & gke versions

/test

/test now

test this please

test this please

test this please

test this please

Thanks for your PR Mahesh.  Closing as this was incorporated with #32


it takes so much time from minimize to maximize

VSCode Version: 1.40.1
OS Version: windows 10 1903

Steps to Reproduce:

minimize vscode
maximize vscode
the UI will take very long time to refresh, it is blank, (may be black by the default vscode theme)
If the version is lower than 1.40, it was very quick.

Does this issue occur when all extensions are disabled?: Yes

/duplicate of #84343


Still not downloading all likes.

Went from 300 ish to 3000. But wont go further. Whatever you did worked however. Still needs some tweaking though.

Follow-up to #77.

Unfortunately , this still happens. Got more than 3600 likes, but only 500 gets downloaded :(

Like I've said before, no url, no help. I'm really tired of repeating this over and over again in every issue.

@johanneszab
I guess the problem here is, that the user wants to download his own likes. Therefore he knows, that there are 3000+ likes. But the https://www.tumblr.com/liked/by/user/ page actually does not show all of the likes (for example I think likes of posts in hidden/18+ blogs are nor shown) as this page is a "public page". This could be solved by allowing to crawl the private page https://www.tumblr.com/likes/ which includes all liked posts.

Therefore he knows, that there are 3000+ likes. But the https://www.tumblr.com/liked/by/user/ page actually does not show all of the likes (for example I think likes of posts in hidden/18+ blogs are nor shown) as this page is a "public page".

I was sure that I've already seen some "public" (i.e. https://www.tumblr.com/liked/by/user/) liked/by-blogs with NSFW content, so I just searched for some, and these here surely contain 18+ content:
https://www.tumblr.com/liked/by/swissescort
https://www.tumblr.com/liked/by/panties69/page/2/1507013037
Thus, I just added some NSFW content played around with my settings, and you'll have to enable these two options under your blogs settings (https://www.tumblr.com/settings/blog/blogname) to fully download your photo/video likes with TumblThree:

Settings-> blog -> Likes (to enable the public liked/by page)
Settings -> blog -> Visibility -> blog is explicit. (to see NSFW content)

Thus, if you don't change the visibility option, the public liked/by page will not show NSFW content. I'll update the instructions for downloading likes on my website and in the README.md to reflect this.
Thanks for the tip!


Possibility of collision on ticket codes

Since ticket codes are randomized, there is a remote possibility of collision, which should be avoided.

Implemented in commit 0ee3668.


Show Image Transform unwanted padding in the window

I'm sure my image input is 100x100 which looks like this:

But when I use show image transform to show it.
I got some unwanted padding in the right of the window.

This doesn't happen here with the ImagePipelineExample. Could you provide a few lines of code to reproduce this? Thanks!

alright, maybe it's my machine problem


Test case. Validator test. Changes in test case naming. Changes in class who called create.

testValidateAttributes instead testValidate because validate method not to be tested here.
Called:
public function validateAttributes($model, $attributes = null),
public function validateAttribute($model, $attribute),
protected function validateValue($value)
Validator instead TestValidator
because functional of  TestValidator is not used in this case.

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
yes

Merged. Thanks!


error when requesting list of NDs with listnd

udacimak version 1.6.0
thank you in advance for feedback
when I run:
udacimak listnd
I get:
⠴ Fetch user information via Udacity API2020-04-07T12:52:25.759Z [error]: uncaughtException: Unexpected token a in JSON at position 0
SyntaxError: Unexpected token a in JSON at position 0
at JSON.parse ()
at Request._callback (/home//stefan.heyer/.nvm/versions/node/v13.9.0/lib/node_modules/udacimak/lib/api/fetchApiUdacityGraphql.js:53:30)
at Request.self.callback (/home//stefan.heyer/.nvm/versions/node/v13.9.0/lib/node_modules/udacimak/node_modules/request/request.js:185:22)
at Request.emit (events.js:321:20)
at Request. (/home//stefan.heyer/.nvm/versions/node/v13.9.0/lib/node_modules/udacimak/node_modules/request/request.js:1154:10)
at Request.emit (events.js:321:20)
at IncomingMessage. (/home//stefan.heyer/.nvm/versions/node/v13.9.0/lib/node_modules/udacimak/node_modules/request/request.js:1076:12)
at Object.onceWrapper (events.js:427:28)
at IncomingMessage.emit (events.js:333:22)
at endReadableNT (_stream_readable.js:1201:12)
2020-04-07T12:52:25.761Z [error]: Uncaught Exception:
SYNTAXERROR: Unexpected token a in JSON at position 0
STACK: SyntaxError: Unexpected token a in JSON at position 0
at JSON.parse ()
at Request._callback (/home//stefan.heyer/.nvm/versions/node/v13.9.0/lib/node_modules/udacimak/lib/api/fetchApiUdacityGraphql.js:53:30)
at Request.self.callback (/home//stefan.heyer/.nvm/versions/node/v13.9.0/lib/node_modules/udacimak/node_modules/request/request.js:185:22)
at Request.emit (events.js:321:20)
at Request. (/home//stefan.heyer/.nvm/versions/node/v13.9.0/lib/node_modules/udacimak/node_modules/request/request.js:1154:10)
at Request.emit (events.js:321:20)
at IncomingMessage. (/home//stefan.heyer/.nvm/versions/node/v13.9.0/lib/node_modules/udacimak/node_modules/request/request.js:1076:12)
at Object.onceWrapper (events.js:427:28)
at IncomingMessage.emit (events.js:333:22)
at endReadableNT (_stream_readable.js:1201:12)

btw... I get the same error when trying to download anything with "udacimak download nd***"

@stefanheyer
Could you please send me the Udacity authentication token to<EMAIL_ADDRESS>or in the reply box so that i can test it on my workspace for the above stated issue..
You can get the Udacity authentication token by visiting the link below 👇  and following the steps:
https://github.com/udacimak/udacimak/wiki/How-to-Use#settoken-set-udacity-authentication-token

@1871vinayak thank you for the quick response. While you were responding I figured that my token probably expired. I am currently resetting it and will check if this resolves the problem (It probably will). Please be aware of the fact that the Udacity authentication token is strictly personal can not be shared. Nevertheless, thank you for the support.

Indeed as expected my token had expired. I fixed my issues with listnd and download by resetting it. Unfortunately, the status 500 error remains unresolved.

Indeed as expected, my key had expired. By resetting it I managed to fix my listnd and download error. Next time I will read the documentation more carefully before opening an issue. My bad :)

@stefanheyer
I very well know that the Udacity authentication token is strictly personal, As i was trying to help you i needed the JSON files for testing it but according to your first comment you were unable to download the JSON file so i cannot expect it from you so that's why i asked for the Udacity authentication token to rectify the issue.
And from next time make sure you open valid issue with detailed explanation which occur due to any faults or bugs in the program.

@1871vinayak will do. Thank you for the feedback and super fast assistance.


IE 11/Edge: injecting scoped styles using require tag for custom element is not wokring

Hi,
I'm testing your framework and I noticed issue for custom elements that are using shadow dom namely scoped styles that are beeing injected through require tag in template is not working on IE11/Edge. (On IE <= 10 templates are not even being loaded in body tag)
Here is an example:
http://plnkr.co/edit/uMIe2H?p=preview
As you can see on Chrome and FF button is blue and on IE/Edge it has default background.
Styles are visible in inspector but for some reason IE is not taking them into consideration.

Fixed in master and releasing tomorrow-ish.


pytorch2caffe, I test the caffe model,but the result is terriable

I convert the pytorch model to caffe , I test the caffe model,but the result is terriable

Hi,
I have wrote a example/testify_pytorch_to_caffe_example.py, that will tell you which layer is wrong. I need more information about your network to find out the problem.
Thank you.


Fixes to running on iOS 13

On current version the app just doesn't build because of some compatibility/deprecated issues on iOS 13
Also re-ran flutter create . on the example folder, somehow couldn't run it locally
Updated Dart sdk requirement to 2.1.0

@kmcgill88 Since you worked on the iOS version, can you please take a look? 🙏

@gildaswise @kmcgill88 Awesome, thank you so much! Published under 0.3.3


Question: Getting "Could not obtain Bundle ID for app at path..." when trying to run XamarinUI Tests

Hi!
I am having issues with running tests with Xamarin on a simulator because their device agent app can not be installed on the sim. They internally use your FBSimulatorControl. The error I get is pointing to the .app file from Xamarin and is stating that getting the bundle id is not working:
SetUp : System.Exception : Test Initialize failed!
----> Calabash.XDB.Core.Exceptions.DeviceAgentException : Failed to install DeviceAgent
ExitCode: 134
0   CoreFoundation                      0x00007fff9ae5b4f2 __exceptionPreprocess + 178
1   libobjc.A.dylib                     0x00007fff8bb3773c objc_exception_throw + 48
10  iOSDeviceManager                    0x00000001057dac0c +[CLI process:] + 1142
11  iOSDeviceManager                    0x00000001057ae5ed main + 121
12  libdyld.dylib                       0x00007fff978045ad start + 1
2   CoreFoundation                      0x00007fff9ae601ca +[NSException raise:format:arguments:] + 106
3   Foundation                          0x00007fff8c8d7856 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 198
4   FBSimulatorControl                  0x00000001059c136f -[FBSimulator(Helpers) installedApplicationWithBundleID:error:] + 221
5   FBSimulatorControl                  0x00000001059c06b6 -[FBSimulatorApplicationCommands isApplicationInstalledWithBundleID:error:] + 83
6   iOSDeviceManager                    0x00000001057e0150 +[Simulator appIsInstalled:deviceID:] + 164
7   iOSDeviceManager                    0x00000001057df834 +[Simulator installApp:deviceID:updateApp:codesignID:] + 606
8   iOSDeviceManager                    0x00000001057d6f91 +[Device installApp:deviceID:updateApp:codesignID:] + 146
9   iOSDeviceManager                    0x00000001057c05ec +[InstallAppCommand execute:] + 419
(
)
*** First throw call stack:
2016-12-20 08:49:17.966 iOSDeviceManager[1082:31727] *** Assertion failure in -[FBSimulator installedApplicationWithBundleID:error:], /Users/moody/git/calabash/FBSimulatorControl/FBSimulatorControl/Management/FBSimulator+Helpers.m:126
2016-12-20 08:49:17.968 iOSDeviceManager[1082:31727] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: bundleID'
Error creating SimulatorApplication for path /var/folders/s9/bljw34rd6dqcy0w46xssrvrw0000gp/T/xdb/DeviceAgent.iOS.Dependencies/54daf9e58e37a80353a99c2b3139b615/app/DeviceAgent-Runner.app: Error Domain=com.facebook.FBControlCore Code=0 "Could not obtain Bundle ID for app at path /var/folders/s9/bljw34rd6dqcy0w46xssrvrw0000gp/T/xdb/DeviceAgent.iOS.Dependencies/54daf9e58e37a80353a99c2b3139b615/app/DeviceAgent-Runner.app" UserInfo={NSLocalizedDescription=Could not obtain Bundle ID for app at path /var/folders/s9/bljw34rd6dqcy0w46xssrvrw0000gp/T/xdb/DeviceAgent.iOS.Dependencies/54daf9e58e37a80353a99c2b3139b615/app/DeviceAgent-Runner.app}
libc++abi.dylib: terminating with uncaught exception of type NSException
I have checked the Info.plist of the app and there is a key with CFBundleIdentifier inside with a follwing string com.apple.test.DeviceAgent-Runner. For me this seemed legit, but I am like John Snow, so I know nothing about that.

Can you provide me any input why this could appear only on my machine. Genrally this stuff from xamarin seems to work for most people.
Thanks in advance!

 If the issue still occurs, are you by any chance using a case-sensitive file system?

Hi!
Thanks for your reply!
I am on Mac OS so yes I am on a case sensitive file system!
I have tried deleting the folder but without any luck.
Best Regards
Hubertus
From: Tama Waddell<EMAIL_ADDRESS>Sent: Wednesday, February 8, 2017 10:02 AM
To: facebook/FBSimulatorControl<EMAIL_ADDRESS>Cc: Hubertus Grabner<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [facebook/FBSimulatorControl] Question: Getting "Could not obtain Bundle ID for app at path..." when trying to run XamarinUI Tests (#359)
Have you tried deleting the /var/folders/s9/bljw34rd6dqcy0w46xssrvrw0000gp/T/xdb/ directory? If the issue still occurs, are you by any chance using a case-sensitive file system?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/FBSimulatorControl/issues/359#issuecomment-278270195, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVbgh9ye1i6sow8H4tYf_f92WLgrBzoyks5raYSDgaJpZM4LRpdh.

I was getting the exact same exception as you on a case sensitive file system.
I'm guessing there's probably some reference to the Info.plist file which has the wrong casing causing it to fail extracting the BundleId.
I've actually reformatted my Mac on a case insensitive file system and it is working as advertised. Although there's a lot of variables gone by completely reinstalling everything but if you are still having this problem and would like to give it a shot, it could help narrow the cause down.

Is there something that you need from FBSimulatorControl here, or a bug that needs addressing in the way files are handled?

I do not know this for sure because I am just using Xamarin for testing and noticed that the way how they use your FBSimulatorControl does not work on my case sensitive file system.  I cannot tell if the bug is in the FBSimulatorControl or in the code around where the xamarin guys are using it.
From: Lawrence Lomax<EMAIL_ADDRESS>Sent: Wednesday, February 15, 2017 2:37 PM
To: facebook/FBSimulatorControl<EMAIL_ADDRESS>Cc: Hubertus Grabner<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [facebook/FBSimulatorControl] Question: Getting "Could not obtain Bundle ID for app at path..." when trying to run XamarinUI Tests (#359)
Is there something that you need from FBSimulatorControl here, or a bug that needs addressing in the way files are handled?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/FBSimulatorControl/issues/359#issuecomment-280012206, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVbghyKEZANafaN2404RtdnQpKs_lwf9ks5rcv-FgaJpZM4LRpdh.

Hi, I stumbled on this bug and I'm on a case sensitive file system as well. I created a PR for it:
https://github.com/facebook/FBSimulatorControl/pull/427


Prevent multiple background workers without global cache

This PR enforces a single background worker if global caching (e.g. via redis) is not enabled.
This is because without a global cache, there is no way to properly  lock the individual workers to ensure that a scheduled task is only run once.
If global cache is enabled (currently we support redis) then multiple workers can be run in parallel, as the global cache allows tasks to be scheduled correctly.
The underlying issue was discovered as part of https://github.com/inventree/InvenTree/pull/8399 - some very hard-to-observe race conditions!

@matmair good idea about the breaking change. I'll mark it as such and add a note to the docs too


Latest b42 not working with iPad Pro A9X, keeps rebooting after got gc at xx breaking message

Describe the bug
Upgraded unc0ver to b42 after restoring rootfs using b41 and now every time I click jailbreak it reports got gc at xx breaking and reboots, tried both reload system daemons turned off and on.
To Reproduce
Steps to reproduce the behavior:

Go to unc0ver
Click on jailbreak
Messages start scrolling and last message is "got gc at xx: breaking"
iPad reboots

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version: 12.1.1b3
iOS Device: iPad Pro 12.9" 1st Generation A9X
unc0ver Version: v3.0.0b42

Place an "x" between the brackets if true:

[x] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[x] this issue is present after a rootfs restore
[x] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.

Sometimes the last message in the unc0ver app is fakeport xxxxxxxxxx and then reboots.

Was getting "got gc at -9: breaking" and rebooting, once I disabled "Airplane Mode" and jailbreak, it was: got gc at 21: breaking" but it did work

No luck disabling "Airplane Mode" but if I change the kernel exploit to VS (voucher_swap) from MS (machswap) it works, must be issue with Machswap.

Can you try this version?  I made it less aggressive with the GC detection.  It works on MY slowest and fastest devices but I don't have an iPad Pro to test with.

sbingner, Unfortunately I tried the version you posted and it just reboots after the line fakeport: xxxxxxxxx line is displayed.  I have tried with reload system daemons on and off and also airplane mode on and off and always the same results. Sorry.

Can you post the diags for that?

Can you post the diags for that?

Is this what you are looking for?
diagnostics.plist.zip

@sbingner The GC process is too aggressive on A9(X) devices. I sticked to the original GC function but only changed gc_ports_cnt to 50, which gains almost 100% success rate (commit).

@sbingner The GC process is too aggressive on A9(X) devices. I sticked to the original GC function but only changed gc_ports_cnt to 50, which gains almost 100% success rate (commit).

@sbingner Will this change be released as a new beta?


UHF-4788: Rest endpoint to check helfi package versions

To test this:

Run composer require drupal/helfi_api_base:dev-UHF-4788
Run drush updb
Send request to /api/v1/package?name=drupal/helfi_api_base&version=2.1.1

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@46ea948). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             main     #58   +/-   ##
======================================
  Coverage        ?   9.35%
  Complexity      ?     273
======================================
  Files           ?      35
  Lines           ?     780
  Branches        ?       0
======================================
  Hits            ?      73
  Misses          ?     707
  Partials        ?       0

Continue to review full report at Codecov.

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

Functionality works as described. If code check is ok, then good job, ready to merge! 🚀


Fix removing specialist sector tags

https://github.com/alphagov/whitehall/pull/2692 changed the specialist sector tags table in the database to disallow edition_id to be set to null, in order to fix an issue where tags could not be added to new editions. This inadvertently created a new issue where editions with tags could not have these tags removed, since ActiveRecord was trying to set edition_id to null when a tag was removed from an edition.
This commit changes the behaviour of ActiveRecord in this case to delete removed tags from the database table.
Trello: https://trello.com/c/IjjV13t3/169-trying-to-remove-a-specialist-tag-in-whitehall-publisher-results-in-an-error

🎉 Well found.
Would love to see a failing test case though :)

Yup, looking at getting a test for this.

OK, got a test for this


Dataset Viewer issue for hendrycks_test

Link
https://huggingface.co/datasets/hendrycks_test
Description
The dataset viewer is not working for dataset hendrycks_test.
Error details:
Error code:   ExternalFilesSizeRequestConnectionError
Exception:    ConnectionError
Message:      HTTPSConnectionPool(host='people.eecs.berkeley.edu', port=443): Max retries exceeded with url: /~hendrycks/data.tar (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fdb011d5cd0>: Failed to establish a new connection: [Errno 111] Connection refused'))
Traceback:    The previous step failed, the error is copied to this step:  kind='config-parquet' dataset='hendrycks_test' config='philosophy' split=None---The previous step failed, the error is copied to this step:  kind='config-parquet-and-info' dataset='hendrycks_test' config='philosophy' split=None---Traceback (most recent call last):
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/connection.py", line 174, in _new_conn
                  conn = connection.create_connection(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/util/connection.py", line 95, in create_connection
                  raise err
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/util/connection.py", line 85, in create_connection
                  sock.connect(sa)
              ConnectionRefusedError: [Errno 111] Connection refused

              During handling of the above exception, another exception occurred:

              Traceback (most recent call last):
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 703, in urlopen
                  httplib_response = self._make_request(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 386, in _make_request
                  self._validate_conn(conn)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn
                  conn.connect()
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/connection.py", line 363, in connect
                  self.sock = conn = self._new_conn()
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/connection.py", line 186, in _new_conn
                  raise NewConnectionError(
              urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7fdb011d5cd0>: Failed to establish a new connection: [Errno 111] Connection refused

              During handling of the above exception, another exception occurred:

              Traceback (most recent call last):
                File "/src/services/worker/.venv/lib/python3.9/site-packages/requests/adapters.py", line 489, in send
                  resp = conn.urlopen(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 787, in urlopen
                  retries = retries.increment(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/urllib3/util/retry.py", line 592, in increment
                  raise MaxRetryError(_pool, url, error or ResponseError(cause))
              urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='people.eecs.berkeley.edu', port=443): Max retries exceeded with url: /~hendrycks/data.tar (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fdb011d5cd0>: Failed to establish a new connection: [Errno 111] Connection refused'))

              During handling of the above exception, another exception occurred:

              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 624, in raise_if_too_big_from_external_data_files
                  for i, size in enumerate(pool.imap_unordered(get_size, ext_data_files)):
                File "/usr/local/lib/python3.9/multiprocessing/pool.py", line 870, in next
                  raise value
                File "/usr/local/lib/python3.9/multiprocessing/pool.py", line 125, in worker
                  result = (True, func(*args, **kwds))
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 519, in _request_size
                  response = http_head(url, headers=headers, max_retries=3)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/utils/file_utils.py", line 413, in http_head
                  response = _request_with_retry(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/utils/file_utils.py", line 324, in _request_with_retry
                  raise err
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/utils/file_utils.py", line 320, in _request_with_retry
                  response = requests.request(method=method.upper(), url=url, timeout=timeout, **params)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/requests/api.py", line 59, in request
                  return session.request(method=method, url=url, **kwargs)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/requests/sessions.py", line 587, in request
                  resp = self.send(prep, **send_kwargs)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/requests/sessions.py", line 701, in send
                  r = adapter.send(request, **kwargs)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/requests/adapters.py", line 565, in send
                  raise ConnectionError(e, request=request)
              requests.exceptions.ConnectionError: HTTPSConnectionPool(host='people.eecs.berkeley.edu', port=443): Max retries exceeded with url: /~hendrycks/data.tar (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fdb011d5cd0>: Failed to establish a new connection: [Errno 111] Connection refused'))

Thanks for reporting, @surya-narayanan.
Yesterday we had an outage affecting multiple Hugging Face services. It is fixed now and the viewers are progressively updating.
The viewer for "hendrycks_test" is working now. See:


Java 9 - protobuf-java 3.0.0 warnings

In running something with latest Datastore client, I see the following:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/Users/lesv/.m2/repository/com/google/protobuf/protobuf-java/3.0.0/protobuf-java-3.0.0.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

https://github.com/google/protobuf/issues/3781

Note the current version of java protobuf appears to be 3.4.1 so com.google.cloud should update

Actually it appears that veneer is using 3.3.1

@lesv can you please clarify if this issue is reproducible with 3.3.1 or only with 3.0.0?

Since this is just a warning message, and one that is emitted by a dependency of ours, and they already have a tracking issue, I am going to close out the present issue.

This is not a good reason to close the bug... People are now adopting Java11, and Google libraries should not have warnings worrying folks.

@ludoch, I beg to differ.  it's a great reason to close THIS bug. The right people are looking at the issue.  There's nothing we can do here, and the right people are looking at it.  Please feel free to follow up on protocolbuffers/protobuf#3781.


[main] Update community files

Cron -knative-prow-robot
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads
Produced by: knative-sandbox/knobots/actions/update-community
Details:

/retest

/retest
/lgtm
/approve


Add PointerRouter

This patch is the first step towards implementing gestures. The pointer router
allows the gesture detectors to hook in at the end of the pointer event
propagation chain.
Related to #145

LGTM


Return a meaningful error for missing template

Currently if the template isn't found we fail silently since err is always nil at this point.

@jhernand please review

Looks good, thanks @moolitayer.


Switch kindelia name to an attribute

To make it more homogenous with the new function attributes

When merging this, we need to do a fix for Wikind at the same time as not to break everything.

Here https://github.com/Kindelia/Wikind/pull/71


Request for collaboration!

Description
Hi! I wanted to work on youtube video downloader from your code-n-stitch repo!
Technologies and Languages
List of all the technologies and languages which you think are required for solving this issue
Aditional Work
Any optional work you want to add.

The issue is already present. Check this out. #8


[enhancement]: Need a optimization guide on RTX 4090

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
<EMAIL_ADDRESS>What should this feature add?
In your demo video about version 2.2., what are these crazy generation speeds?
Significant acceleration of image generation. What I see now in InvokeAI is 9-10 it/s at 512x512 and 50 steps.
With some manipulation in Automatic1111 I overclocked up to 23 it/s at the same settings.
https://disk.yandex.ru/i/EITGEi5M4XG8uQ
one more test 1280 https://disk.yandex.ru/d/IXjTxBSknuS2cg
Alternatives
It would be great if you could somehow add VoltaML it works with tensor cores and reaches as much as 30 it/s, but I have only seen it on screenshots of github, how to install it locally, I do not even understand.
Aditional Content
I watched a video about how you have all well and good works on version 2.2, tried to replace the small to do on the image field 192x192 and do not know how you, but I have downscale is working out of the blue. To put it bluntly, it's horrible.
https://disk.yandex.ru/i/pxh87YPuphyWRQ

The demo video speeds past the generation parts to focus on the features. Maybe @hipsterusername can overlay a :fast_forward: icon or something in future videos to reduce confusion about that.
We're planning on xformers support in a later release, which will help significantly with NVIDIA RTX cards and be more competitive with the speeds you're currently seeing in A1111.
The VoltaML demos do look awesome, but I haven't yet set that up locally either. It's one of a number of a number of similar different implementations that are coming up with ways to optimize these neural networks. It's not yet clear which is the best to integrate with a project like this, but definitely something to keep an eye on!

No longer an issue on v3


want to set the height of bottomController as per embedded content view's Heigh.

Hello,
I set tableview as content view in bottomController, I want to set dynamic height of bottomController cause data comes 2 or more than that. if two data comes then slider should not slide and if more than 2 comes then it should slide.
need help.
Thanks.

There are couple of options:

You can wrap your bottom view in another view and use that as a parent(See safe area support part of the ReadMe).
You can use setExpandedTopMargin(pixels: CGFloat) in combination of some other constrains. And just disable sliding when not necessary setSlideEnabled(bool)

Hello,
I did that but sliding view is not resize as per the content view.
Please check the below image if there is two row then sliding resize as per that and disable the sliding.
Do I need to set sliding disable/enable manually ?

You can try experimenting with different constraints and changing different parameters of the library.
Sorry, but I can't exactly tell you how to do it.


fix MPI test failures

Purpose
BCReader and Regridder tests are failing sometimes (but not every time) with an error LoadError: Unable to find compatible target in system image. For example, here.
closes #552
Failure examples

seabreeze branch

Host name	hpc-92-37.cm.cluster
Operating System	CentOS 7.9.2009
Agent Version	3.59.0

seabreeze branch 2

Host name	hpc-92-37.cm.cluster
Operating System	CentOS 7.9.2009
Agent Version	3.59.0

bucket debug branch

Host name	hpc-92-37.cm.cluster
Operating System	CentOS 7.9.2009
Agent Version	3.59.0

atm-ocn-lnd branch

Host name	hpc-92-37.cm.cluster
Operating System	CentOS 7.9.2009
Agent Version	3.59.0

docs branch

Host name	hpc-24-12.cm.cluster
Operating System	CentOS 7.9.2009
Agent Version	3.59.0

Passing examples

seabreeze branch

Host name	hpc-92-37.cm.cluster
Operating System	CentOS 7.9.2009
Agent Version	3.59.0

seabreeze branch 2

Host name	hpc-92-37.cm.cluster
Operating System	CentOS 7.9.2009
Agent Version	3.59.0

done in #501


Put miri in super-strict mode

Specifically:

-Zmiri-strict-provenance: validate that the code respects strict provenance (roughly: usize as ptr doesn't produce a usable pointer).
-Zmiri-check-number-validity: validate that numbers are initialized and do not carry provenance (i.e. transmute<ptr, usize> is banned).
-Zmiri-symbolic-alignment-check (SPICY): validate alignment is statically correct, not just "happens to be" correct.

Everything works with the strict mode flags 🎉 (modulo #31)

(Reminder: nightly fails due to #31, not this PR.)

(ah jeez sorry about the env/command syntax issue I'm a Windows/Powershell user who doesn't use that syntax)


Datatype

nested pattern match.
e.g.
data MList = MNil | MCons Int MList;
let f (x:MList) =
case x of MNil -> 0
| (MCons x (MCons y _)) -> x + y
| _ -> 2
constructor can be partially applied.
e.g.
let g (x:MList -> MList) = x MNil;
g (MCons 3)
This is a primitive version. May need further optimization.

are there any tests that use datatype in the test suite?

@tomtau  No. There are a few examples living in the examples folder.

@xnning currently, the backend will be rewritten - in order to be sure that one does not break these new cases when rewriting it, there should be some tests in the test suite. Please add some - I think the standard test suite is still in migration ( @zhiyuanshi ?), so you can use make test2 instead

Right. make test2 is the standard right now.


west_commands: Fix parsing of extra args for test-item

An arg --test-item makes west loading twister's test configurations form sample/testcase.yaml. It has to mirror twister's behavior. It was not the case with "extra_args" section. Quotation  marks were not removed in west as they were in twister. The quotation marks have to be removed from the extra_args section but left in extra_configs. The commit adds differentiation for those.
fixes: #60297

Tested with
west build -p -b qemu_riscv32 -T samples/subsys/tracing/sample.tracing.user for extra_args as reported in #60297
west build -p -b nrf52dk_nrf52832 -T tests/subsys/mgmt/mcumgr/os_mgmt_info/os.mgmt.info_bt for extra_configs as reported in #56248

Can you try this with https://github.com/zephyrproject-rtos/zephyr/pull/59747 as well?

@nordicjm It seems west --test-item ignores common section from .yaml files. I got your test building when I moved sysbuild: true from common directly to a given item from tests

@nordicjm I don't plan to add a fix for reading "common" into this PR. A proper handling of commons requires coping a twister workflow (some commons are overwritten, some expanded). I think this is not a way to proceed. I created this RFC to discuss how west/twister alignment should be approached #60502.

@PerMac
dealing with common:
--- a/scripts/west_commands/build.py
+++ b/scripts/west_commands/build.py
@@ -270,6 +270,7 @@ class Build(Forceable):
                     y = yaml.safe_load(stream)
                 except yaml.YAMLError as exc:
                     log.die(exc)
+            common = y.get('common')
             tests = y.get('tests')
             if not tests:
                 log.die(f"No tests found in {yf}")
@@ -277,22 +278,26 @@ class Build(Forceable):
             if not item:
                 log.die(f"Test item {test_item} not found in {yf}")

-            for data in ['extra_args', 'extra_configs']:
-                extra = item.get(data)
-                if not extra:
+            for section in [item, common]:
+                if not section:
                     continue
-                if isinstance(extra, str):
-                    arg_list = extra.split(" ")
-                else:
-                    arg_list = extra
-                if data == 'extra_configs':
-                    args = ["-D{}".format(arg.replace('"', '\"')) for arg in arg_list]
-                elif data == 'extra_args':
-                    args = ["-D{}".format(arg.replace('"', '')) for arg in arg_list]
-                if self.args.cmake_opts:
-                    self.args.cmake_opts.extend(args)
-                else:
-                    self.args.cmake_opts = args
+                for data in ['extra_args', 'extra_configs']:
+                    extra = section.get(data)
+                    if not extra:
+                        continue
+                    if isinstance(extra, str):
+                        arg_list = extra.split(" ")
+                    else:
+                        arg_list = extra
+                    if data == 'extra_configs':
+                        args = ["-D{}".format(arg.replace('"', '\"')) for arg in arg_list]
+                    elif data == 'extra_args':
+                        args = ["-D{}".format(arg.replace('"', '')) for arg in arg_list]
+                    if self.args.cmake_opts:
+                        self.args.cmake_opts.extend(args)
+                    else:
+                        self.args.cmake_opts = args
+
             self.args.sysbuild = item.get('sysbuild')
         return found_test_metadata


feat: scope bound connection object

Pull Request Checklist

[ ] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR
[ ] Pre-Commit Checks were ran and passed
[ ] Tests were ran and passed

Description

Close Issue(s)

I've realized that this approach won't work because it binds the request to the receive() and send() coros before they are passed through the middleware stack where they might later be wrapped.


Segmentation fault with large genomes

Dear authors,
Thank you for creating accel-aligner. It is very fast and sensitive in my tests.
I have been trying to apply accel-aligner to bisulfite sequencing reads and was able to successfully aligned reads. However, as bisulfite reads must be aligned to both the converted forward and converted reverse complement DNA references, I thought about generating an index that is comprised of both references. However, I would get segmentation fault errors when running the aligner against the combined references whereas I do not have this problem when mapping against each reference separately.
Is this a problem caused by a limitation in the size of the reference index?
Best,
Dinh

hey Dinh,
Thanks for using Accel Align. Could you please give us step by step information about how you prepare the combined reference? Perhaps scripts to do it if you already have it? We would like to reproduce the error on our side to see what is wrong.
Raja

Please see the attached shell script for generating this error!
generate_accel_align_test.txt


README images not showing up properly in jazzy docs/cocoapods page

Issue resides in using relative links for all images in Assets folder.
Currently bypassing jazzy docs issue with an extra copy phase in Makefile. Cocoapods images are broken.
We should switch to using absolute references to images.

what about the raw data link like https://raw.githubusercontent.com/quanvo87/WQNetworkActivityIndicator/master/WQNetworkActivityIndicator/Assets/screenshot.png or is that what you're talking about

yup! thats exactly what I was talking about. I was originally just calling Assets/screenshot.png. I switched everything in the PR to use the raw data link like you listed above.


[rbdl] Add new port

RBDL - Rigid Body Dynamics Library

What does your PR fix?

This PR adds a new port for the RDBL for Windows and Linux. It builds the library downloading it from official repository and making compilation through CMake according to Packaging Zipfiles guide.

The port only builds the core library and not the optional addons (future work for features).

Port was tested in vcpkg 2020.07 with RBDL 2.6.0

Which triplets are supported/not supported?

Expected supported triplets: !arm & !uwp & !linux & !osx

Have you updated the CI baseline?

Not updated the CI baseline.

Does your PR follow the maintainer guide?

All the implementation has been done taking into account the Maintainer Guidelines and Policies.

I am going to update Supports  field. It works perfectly for Windows and I am using on Windows.
Linux and OSX remains as future work. ok?

I don't understand... 🤔
The previous build was: https://dev.azure.com/vcpkg/public/_build/results?buildId=43808&view=logs&j=d3670d0c-cc82-50c9-762c-eccde036829f
And the new one: https://dev.azure.com/vcpkg/public/_build/results?buildId=43818&view=logs&j=a83b7983-e539-5449-9e09-337ff5f52283

Between 2 builds starts failing x86-windows when in the previous one was marked as success
I exclude linux and osx in Supports field and using vcpkg_fail_port_install and they continue failing in CI

@NancyLi1013 any idea or recommendation about that?
Thanks in advance.

Hi @RDCH106
I checked the build results here https://dev.azure.com/vcpkg/public/_build/results?buildId=43808&view=logs&j=d3670d0c-cc82-50c9-762c-eccde036829f and found that:
The failures on Linux and osx are due to this:
c++: error: /bigobj: No such file or directory
Since /bigobj is only used in MSVC.
The failures on uwp are due to this:
CMake Error at ports/rbdl/portfile.cmake:29 (file):
  file COPY cannot find "D:/buildtrees/rbdl/x64-uwp-dbg/rbdl.dll": No error.
Call Stack (most recent call first):
  scripts/ports.cmake:79 (include)

Generally, CMake will install the targets to the related directory automatically and we don't need to handle it manually.
So this part might not be needed.
if(VCPKG_LIBRARY_LINKAGE STREQUAL dynamic)
    if(VCPKG_TARGET_IS_WINDOWS)
        if(NOT DEFINED VCPKG_BUILD_TYPE OR VCPKG_BUILD_TYPE STREQUAL "debug")
            file(COPY ${CURRENT_BUILDTREES_DIR}/${TARGET_TRIPLET}-dbg/rbdl.dll DESTINATION ${CURRENT_PACKAGES_DIR}/debug/bin)
        endif()
        if(NOT DEFINED VCPKG_BUILD_TYPE OR VCPKG_BUILD_TYPE STREQUAL "release")
            file(COPY ${CURRENT_BUILDTREES_DIR}/${TARGET_TRIPLET}-rel/rbdl.dll DESTINATION ${CURRENT_PACKAGES_DIR}/bin)
        endif()
    endif()
endif()

You can make a patch to add
 RUNTIME DESTINATION ${CMAKE_INSTALL_LIBDIR} to install targets in dynamic build.
Based on the above situation, I think this port supports all platform. So we can remove Supports field now and try to fix the failures and rebuild this.
Note: You can merge the master branch to this PR when you do the changes.

Just one more question to be more self-reliant next time. The error due /bigobj only supported by MSVC is not showed here: https://dev.azure.com/vcpkg/public/_build/results?buildId=43808&view=logs&j=d3670d0c-cc82-50c9-762c-eccde036829f

But how can I inspect /mnt/vcpkg-ci/buildtrees/rbdl/install-x64-linux-dbg-out.log? Is it any way to access the log produced by the CI to see that file?
Thanks in advance and sorry for my many questions

@NancyLi1013 removing Supports field and vcpkg_fail_port_install function produces global failure. It have no sense for me...

I begin to understand... The successfully builds are because they are skipping CMake building 😅, but I don't know how to resolve it because have no idea how to see CMake logs in Azure DevOps.

Hi @RDCH106
The failures are caused by the patch. It seems you didn't update the patch. So It failed to apply.
CMake Error at scripts/cmake/vcpkg_apply_patches.cmake:54 (message):
  Applying patch failed.  error: corrupt patch at line 16

Call Stack (most recent call first):
  scripts/cmake/vcpkg_extract_source_archive_ex.cmake:141 (vcpkg_apply_patches)
  scripts/cmake/vcpkg_from_github.cmake:139 (vcpkg_extract_source_archive_ex)
  ports/rbdl/portfile.cmake:7 (vcpkg_from_github)
  scripts/ports.cmake:79 (include)

You need to make a new patch.

You can check the results here https://dev.azure.com/vcpkg/public/_build/results?buildId=43865&view=logs&j=5dffab7c-3299-5a76-7b02-e037cd868fad&t=1294d155-2ef8-5412-c4b1-d5b95781dd72&l=1574.
Other triplets are the same as this.

I think it's ready 😁
@NancyLi1013, thank you again for your huge job and patient with me.

Thanks for your efforts to this PR. @RDCH106
LGTM now.


MGMT-2792 Rename host's Known state to "Ready to install"

These changes should be accompanied by changes within backend messages: https://github.com/openshift/assisted-service/pull/643

Thanks! I think this will be a lot clearer for users. FYI @nirfarkas


quartus-prime-lite: add missing libcrypt.so.1

Description of changes

Add the libxcrypt to the default.nix, fixing the following error
quartus: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@Math-42 wrong branch?

@Math-42 wrong branch?

@Math-42 wrong branch?

sorry, fixed!

@Misterio77

Result of nixpkgs-review pr 208972 run on x86_64-linux 1

1 package built:

quartus-prime-lite


New app ends up in a blank screen

Describe the bug
Step to reproduce:

pnpm dlx ignite-cli@next new PizzaApp --install-deps=false
cd PizzaApp && pnpm i
pnpm dlx pod-install
pnpm start
pnpm run ios

The app loads, but after the splash screen, you get a blank screen. That happens because areFontsLoaded remains on false. If you destructure the second argument of useFonts, which is the error message, and log it, this is what I get:
 LOG  [Error: The method or property expo-file-system.downloadAsync is not available on ios, are you sure you've linked all the native dependencies properly?]

Ignite version
v8.0.0-beta.7
Additional info
System
  platform           darwin
  arch               arm64
  cpu                8 cores       Apple M1
  directory          PizzaApp   /Users/frontendwizard/code/PizzaApp

JavaScript (and globally-installed packages)
  node                16.16.0                                                                             /Users/frontendwizard/.volta/tools/image/node/16.16.0/bin/node
  npm                 8.15.0                                                                              /Users/frontendwizard/.volta/tools/image/npm/8.15.0/bin/npm
    corepack          0.10.0
    npm               8.11.0
  yarn                1.22.11                                                                             /Users/frontendwizard/.volta/tools/image/yarn/1.22.11/bin/yarn
    create-next-app   12.3.0
  pnpm                7.12.1                                                                              /Users/frontendwizard/Library/pnpm/pnpm
                      <no pnpm global package info available>
  expo                46.0.10 -> ./node_modules/.pnpm/expo@46.0.10_<EMAIL_ADDRESS> managed

Ignite
  ignite-cli         8.0.0-beta.7   /Users/frontendwizard/.npm/_npx/2351a7c35afcf833/node_modules/.bin/ignite
  ignite src         build          /Users/frontendwizard/.npm/_npx/2351a7c35afcf833/node_modules/ignite-cli/build

Android
  java               11.0.12      /opt/homebrew/opt/openjdk@11/bin/java
  android home       -            /Users/frontendwizard/Library/Android/sdk

iOS
  xcode              13.4.1
  cocoapods          1.11.2       /opt/homebrew/bin/pod

I managed to fix this issue by adding expo-file-system as dependency. I can open a PR for it if y'all would like to add this fix to the boilerplate. :)

Your PR works like a charm! Thanks for filing the issue and PR. I was able to follow along all your steps without a hitch


crash: #[path="/dev/null"]  attr

This code causes rustfmt to crash
#[path="/dev/null"]
pub mod null;

thread 'main' panicked at 'path is expected to be under the root', /cargo/registry/src/github.com-1ecc6299db9ec823/ignore-0.4.16/src/gitignore.rs:227:9
stack backtrace:
   0:     0x5587c3e2eaa7 - std::backtrace_rs::backtrace::libunwind::trace::h746c3e9529d524bc
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/../../backtrace/src/backtrace/libunwind.rs:90:5
   1:     0x5587c3e2eaa7 - std::backtrace_rs::backtrace::trace_unsynchronized::h86340908ff889faa
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x5587c3e2eaa7 - std::sys_common::backtrace::_print_fmt::h43f85f9b18230404
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/sys_common/backtrace.rs:67:5
   3:     0x5587c3e2eaa7 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hc132ae1a5b5aa7cd
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/sys_common/backtrace.rs:46:22
   4:     0x5587c3e5283c - core::fmt::write::hdf023a0036d2a25f
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/core/src/fmt/mod.rs:1078:17
   5:     0x5587c3e2b462 - std::io::Write::write_fmt::h8580846154bcb66a
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/io/mod.rs:1519:15
   6:     0x5587c3e30a75 - std::sys_common::backtrace::_print::h7ee55fed88d107a3
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/sys_common/backtrace.rs:49:5
   7:     0x5587c3e30a75 - std::sys_common::backtrace::print::h54a7d3e52a524177
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/sys_common/backtrace.rs:36:9
   8:     0x5587c3e30a75 - std::panicking::default_hook::{{closure}}::h60921e857bf55a40
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/panicking.rs:208:50
   9:     0x5587c3e305ca - std::panicking::default_hook::hf0f9afb1017317fc
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/panicking.rs:225:9
  10:     0x5587c3e31211 - std::panicking::rust_panic_with_hook::h8d66bf42b407aaea
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/panicking.rs:591:17
  11:     0x5587c3ae67c4 - std::panicking::begin_panic::{{closure}}::hbe262b95ef2ff8f9
  12:     0x5587c3ae66bc - std::sys_common::backtrace::__rust_end_short_backtrace::hd70d74b6b6dc38ff
  13:     0x5587c3a2ddac - std::panicking::begin_panic::h998094cd3d11af60
  14:     0x5587c3a5e258 - ignore::gitignore::Gitignore::matched_path_or_any_parents::h687892c59c3a1cae
  15:     0x5587c3b66149 - rustfmt_nightly::syntux::session::ParseSess::ignore_file::h60741d92df2c771d
  16:     0x5587c39bfae0 - rustfmt_nightly::formatting::format_project::h75f3cb078ea2edba
  17:     0x5587c39c93ee - scoped_tls::ScopedKey<T>::set::h46570b94864b4223
  18:     0x5587c39c3789 - rustfmt_nightly::Session<T>::format::h16e5c985cca65c6b
  19:     0x5587c39d38fb - rustfmt::format_and_emit_report::h34b4f1b50145fd6f
  20:     0x5587c39c309d - rustfmt_nightly::Session<T>::override_config::h588d4c0abb82dcad
  21:     0x5587c39d0f8d - rustfmt::execute::hbead43f61fce9ab6
  22:     0x5587c39cd9fd - rustfmt::main::hdc579be80dab480f
  23:     0x5587c39c58b3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h425146d795f70aec
  24:     0x5587c39c5c09 - std::rt::lang_start::{{closure}}::h1a880688683e8956
  25:     0x5587c3e31727 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h54c39b9b8451875a
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/core/src/ops/function.rs:259:13
  26:     0x5587c3e31727 - std::panicking::try::do_call::hcdfba51a06e21b42
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/panicking.rs:379:40
  27:     0x5587c3e31727 - std::panicking::try::hb36953ccd24f930d
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/panicking.rs:343:19
  28:     0x5587c3e31727 - std::panic::catch_unwind::hbb374cd03beb3824
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/panic.rs:396:14
  29:     0x5587c3e31727 - std::rt::lang_start_internal::h97dca9624db2aa85
                               at /rustc/2225ee1b62ff089917434aefd9b2bf509cfa087f/library/std/src/rt.rs:51:25
  30:     0x5587c39d4552 - main
  31:     0x7f0254b48152 - __libc_start_main
  32:     0x5587c39b9f59 - <unknown>

rustfmt 1.4.29-nightly (70ce182 2020-12-04)

Admittedly not the most graceful of exits, but I'm also a little puzzled by the use case of the snippet provided in the description.
This isn't reproducible in source though I'm pretty confident that's due to some changes that haven't been backported. Is there a more realistic use case where this is occurring or am I perhaps missing something with the original snippet?

The code is from a rustdoc test in the rustc repo src/test/rustdoc/issue-26995.rs
I was running rustfmt on all files in the rustc repo to find crashes. :)


Gem theme

Yay! Gem-based theme that works with GitHub pages 😄
Closes #6.

The MACSio page is now using the new remote theme feature (and it works!!!), but using my personal repo. I'll update those settings once this PR is merged.


Fixes grid fixed height after sorting, enables redrawer tests.

How is supposed to review this? using reviewable or just in github ?
If we merge this here a batch process will override it from gerrit, so you have to manually commit to gerrit.
I like PR, could we move components from vaadin gerrit to gerrithub, so as we can use both at the same time?

How is supposed to review this? using reviewable or just in github ?
You can try both and see how they feel to use.

If we merge this here a batch process will override it from gerrit, so you have to manually commit to gerrit.
Yes, no biggie.

I like PR, could we move components from vaadin gerrit to gerrithub, so as we can use both at the same time?
Didn't gerrithub close the PRs when you import them?

Review status: 0 of 6 files reviewed, 3 unresolved discussions, all commit checks successful.

Comments from the review on Reviewable.io

Review status: 0 of 6 files reviewed, 3 unresolved discussions, all commit checks successful.

vaadin-components-gwt/src/main/java/com/vaadin/components/grid/GridComponent.java, line 446 [r1] (raw file):
Excellent, I'll modify the changes accordingly.
I'm going to do a small experiment and amend the changes and force push the new commits just to see how badly it breaks the comments in this pull request :smiley:
Hold on to your :tophat:

Comments from the review on Reviewable.io

Review status: 0 of 6 files reviewed, 4 unresolved discussions, some commit checks broke.

vaadin-components-gwt/src/main/java/com/vaadin/components/grid/GridComponent.java, line 442 [r1] (raw file):
Done.

vaadin-components-gwt/src/main/webapp/vaadin-grid/vaadin-grid.html, line 778 [r2] (raw file):
As an interesting side-note: changing this to _this breaks stuff, because _this.contentDocument seems to be undefined.  So apparently this on line 778 doesn't refer to <v-grid> object? Any idea where it refers to?
@tomivirkki ?

Comments from the review on Reviewable.io

Review status: 0 of 6 files reviewed, 4 unresolved discussions, all commit checks successful.

vaadin-components-gwt/src/main/webapp/vaadin-grid/vaadin-grid.html, line 778 [r2] (raw file):
The listener executes in the context of the measure object so that's what this refers to in this case.

Comments from the review on Reviewable.io

Review status: 0 of 6 files reviewed, 4 unresolved discussions, all commit checks successful.

vaadin-components-gwt/src/main/java/com/vaadin/components/grid/GridComponent.java, line 291 [r1] (raw file):
GWT compiler allows overload, but not in JsInterop classes. So in order to make it work create a new refresh() method and mark refresh(boolean) as @JsNoexport

Comments from the review on Reviewable.io

Review status: 0 of 6 files reviewed, 2 unresolved discussions, all commit checks successful.

vaadin-components-gwt/src/main/java/com/vaadin/components/grid/GridComponent.java, line 442 [r1] (raw file):
The datasource may be not be defined at this point so a null check is required also

Comments from the review on Reviewable.io

Review status: 0 of 4 files reviewed, 2 unresolved discussions, some commit checks pending.

vaadin-components-gwt/src/main/java/com/vaadin/components/grid/GridComponent.java, line 446 [r1] (raw file):
Done.

Comments from the review on Reviewable.io


minor: help of sub-commands and options is not clear

Make the sub-commands and their options more intuitive.
Example: substratee-client trusted -m ... list-accounts fails although the syntax looks correct. The options -m must be added after the sub-command.

this should be resolved with #197


ISSUE-147 Implement integration tests for drive.py

This issue addresses #147
@noah-de I think the credentials for the podaacdemo account have expired. I need to check with Jessica Hausman and it was her that created the account. If this is the case then I will simply create a new account. I also found some bugs in drive.py so this exercise was well worth it.
Let me know what you think. You can run the tests from the top-level directory by simply running
nosetests --verbosity=3

Right now some of the tests will fail... this is due to the account credentials not being valid. I will update the PR with new credentials once I've confirmed what is going on.

Also it looks like there are some issues with Python 2.7 build
NameError: global name 'PermissionError' is not defined

I am not a fan of supporting Python 2.7 but just last week I was asked to continue support for it so i will.


Add glslang-dev key

Please add the following dependency to the rosdep database.
Package name:
glslang-dev
Package Upstream Source:
https://github.com/KhronosGroup/glslang
Purpose of using this:
Needed by gz_ogre_next_vendor
Distro packaging links:
Links to Distribution Packages

Debian: https://packages.debian.org/

https://packages.debian.org/bookworm/glslang-dev

Ubuntu: https://packages.ubuntu.com/

https://packages.ubuntu.com/noble/glslang-dev

Fedora: https://packages.fedoraproject.org/

https://packages.fedoraproject.org/pkgs/glslang/glslang-devel/

Arch: https://www.archlinux.org/packages/

https://archlinux.org/packages/extra/x86_64/glslang/

Gentoo: https://packages.gentoo.org/

https://packages.gentoo.org/packages/dev-util/glslang

macOS: https://formulae.brew.sh/

skipped

Alpine: https://pkgs.alpinelinux.org/packages

skipped

NixOS/nixpkgs: https://search.nixos.org/packages

skipped

openSUSE: https://software.opensuse.org/package/

skipped

rhel: https://rhel.pkgs.org/

skipped

The bot thinks that we can satisfy this key on opensuse, rhel, and alpine as well, so it is probably a good idea to do that.

Done in 98297e3


Cocoapods Support

Cocoapods now allows support Swift & I'd be glad to see this library available as a pod :)
PS. Converting it to Swift 1.2 will be needed too.

:+1: Waiting for this as well.


PLUGIN-1090: spanner timeout issue on new DB

spanner timeout issue on new DB

@itsankit-google @rmstar Please review

LGTM. Please test and verify the changes before merge.

@itsankit-google Tested, and document attached on jira by @sahilkapoor301992

LGTM. Please test and verify the changes before merge.

@itsankit-google Tested, and document attached on jira by @sahilkapoor301992

@sumitnigamcs Testing with e2e tests enabled is not yet done with these changes. Please check with @sawantpritam.

LGTM. Please test and verify the changes before merge.

@itsankit-google Tested, and document attached on jira by @sahilkapoor301992

@sumitnigamcs Testing with e2e tests enabled is not yet done with these changes. Please check with @sawantpritam.

@itsankit-google tested with e2e tests and it is working as expected.

LGTM. Please test and verify the changes before merge.

@itsankit-google Tested, and document attached on jira by @sahilkapoor301992

@sumitnigamcs Testing with e2e tests enabled is not yet done with these changes. Please check with @sawantpritam.

@itsankit-google tested with e2e tests and it is working as expected.

Thanks @ksahilCF for the update, please ensure it is cherry-picked to release/0.20 for 6.7.


No module named 'cv2'

Everything went smooth till this appeared after I run "Install and import dependencies"

You probably forgot to install opencv - in your terminal run:

conda` install opencv -c conda-forge

And let me know if that fixes it for you

Closing as I haven't heard back

I had the same issue. I had to pip install opencv instead, which fixed that particular problem.

This solution worked for me:
pip install opencv-python-headless
sudo apt-get install -y libgl1-mesa-dev
Reference: https://stackoverflow.com/questions/63977422/error-trying-to-import-cv2opencv-python-package


Any good news for this framework?

Hi, Ethan,
I found the framework very good. It own clearly code structure. I guess it will be powerful. Do you continue, or give it up?  I'm studying, try to know how to use it. But there is no more API document, no more comments. Actually that's feel not good.

@one-next Thank you for your interest. We use this framework for our service in Korea. So we continue to improve and support for this framework and our service. But this framework has lack documentations, so will fill API, example, etc. documentations.

@hide1202  thanks your reply & your team's selflessness. Waiting for more API , examples and so on .  I will continue follow your steps. Can you share toast-haste run-time environment? BTW,  the framework contain the Database solution(No-SQL or others)?

@one-next We run a service using TOAST Haste on CentOS 6.X, JVM(OpenJDK 8). If you want to run a application using TOAST Haste, you run on JVM, any operating systems.
And we develop the framework for real-time multi-play game, so this framework doesn't contain DB solutions.
A our service contains Redis for user sessions. If you want to use databases, just use them. TOAST Haste supports various callbacks, for example callbacks when connecting a user, disconnecting a user, receiving a message, etc.
But you consider network latency, because the framework contains RTT calculation. So you MUST not long tasks.

Cool, thanks very much. Our  linux is CentOS 6.9, JDK 7(Switch to 8).  I will try it in my free time. @hide1202


Error encountered loading a remote context when providing proofType: LD_PROOF in signatory API

When providing the proofType: LD_PROOF in a request to /credentials/issue in the signatory API, an error is encountered with the following response:
{
  "details": [],
  "status": 500,
  "title": "There was a problem encountered loading a remote context [code=LOADING_REMOTE_CONTEXT_FAILED].",
  "type": null
}

An example request that resulted in this error is:
curl -X 'POST' \
  'http://localhost:7001/v1/credentials/issue' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '
{
"templateId": "VerifiableId",
"config": {
     "issuerDid": "did:key:z6MkmE21F2dAHkM71tnYdBEGaSvnPpxBFZYi2wtzYbTwqvgK",
     "subjectDid": "did:key:z6MkmE21F2dAHkM71tnYdBEGaSvnPpxBFZYi2wtzYbTwqvgK",
     "proofType": "LD_PROOF"
     },
"credentialData": {

     }
}
'

seemed to be a temporary down time of the LD contexts hosted by w3c.


Work queue!

Details

@lslunis helped me design this. Thanks, Luke!
I designed the worker tasks to automatically restart when they finish. This might be more complicated than useful.
map_async now requires module fixtures and utils.set_work_queue to work across pytests. This is because pytest/anyio create new event loops for each async test. I don't think we need (or even necessarily want) to add more magic s.t. devs don't need to write these fixtures in future test files. Happy to be wrong about this, though :)
I tested that the concurrency limits seemingly work by:

pytest
poking around with some traces generated by pytest (after running rm -rf ~/.ought-ice/cache and rm -rf ~/.ought-ice/traces)
seeing that lots of queries work with seq 100 | xargs -L1  zsh -c "rm -rf ~/.ought-ice/cache/; python ~/my_dir/qa_simple.py" (for qa_simple.py from the primer.)

Some important unknowns to me

Is it important to rewrite work_queue.py to use anyio concurrency tooling as opposed to asyncio tooling? My guess is 'no' based on the presence of asyncio primitives throughout the codebase; it would already be a fair amount of effort to move away from asyncio.

I tried a bit to build it, anyway, using anyio tooling. But I couldn't find a way to cleanly have the same semantics: TaskGroups seem way more ergonomic for workflows like 'spawn all these tasks and wait until they're done', which we don't want to do for the worker tasks.

Is the error handling inside _spawn_worker sufficient? I think it works well with the setup in _work, but I'm not 100% sure.

Thanks Jess! I didn't get much sleep today, so I plan to take a look at this over the weekend when I'm fresh.

Closing for now, feel free to reopen.


Update .gitlab-ci.yml

the docu section should get an additional section:
https://github.com/byte-physics/igor-unit-testing-framework/blob/7fcc8d26d057790454509d2e9466e66b69809a7f/.gitlab-ci.yml#L11-L21
  only:
    changes:
      - docu/sphinx/source/*.rst
      - procedures/*.ipf

@ukos-git Thx. Will do.

Is this working as expected? I think it's the question if this is "OR" or "AND" for the tags.
https://github.com/byte-physics/igor-unit-testing-framework/blob/7fcc8d26d057790454509d2e9466e66b69809a7f/.gitlab-ci.yml#L47-L48

@ukos-git On second thought. Is that really a gain?

The tags are and. But we need a new one so that the shell jobs don't end up in docker. I've added shell as tags.

But we need a new one so that the shell jobs don't end up in docker. I've added shell as tags.

sounds more like "or" to me.

@ukos-git Ready for review.


Add linode filtering

Closes #2260

Coverage increased (+0.002%) to 78.166% when pulling b0aec47ba6c11f6172a17fe17892adab60aa4441 on eatonphil:add-linode-filtering into 9e1a9629dbe3d6c5788a64f06991e062183e5f31 on linode:develop.

Coverage decreased (-0.02%) to 78.067% when pulling 5b262cdc32d1cfb3e06bb417943c6ceefd3f289b on eatonphil:add-linode-filtering into d235b10568ab84bb181ab82fdba63410b880e6bf on linode:develop.

is the checked state fix-able?

@mparke that's being fixed in the nodebalancer filtering PR.

Coverage decreased (-7.3%) to 70.828% when pulling d8acaf37db02c899bf42d55104d191596b114114 on eatonphil:add-linode-filtering into d235b10568ab84bb181ab82fdba63410b880e6bf on linode:develop.

Looks good.

thank you!


LD-470 - Fixes multiple instances of show opening on tap

https://artsyproduct.atlassian.net/browse/LD-470

#trivial

👍 merge on green


NathanOliver: Blacklist hypothetical.spam.domain.com

NathanOliver requests blacklist of domains:

hypothetical.spam.domain.com

@gunr2171 Yeah, that's on the list. Could be hard because of how CE hands us data, but I haven't dug into it much,


CORE-5279 revert temp change that allowed multiple CPKs to be added to a CPB without blowing up a flow

…o a CPB without blowing up a flow

As mentioned in slack I had commented this out as a temp fix until [CORE-5279] was resolved. It looks like you resolved this and merged it before my pr went in today, so reverting this change.


Pathrow stuff doesn't work in loader anymore

If we migrate for coastlines sake (if nothing else), we should like use the most common grid (or somehow see which pathrow has the largest area in the cell based on the stac bbox?)

I've added new pathrow search functionality on the develop branch.
According to https://github.com/opendatacube/odc-stac/issues/135 the most common crs is used by default in odc.stac.load