Nothing published on fix topic, no reconnection to gpsd

I am running gpsd_client on ROS Noetic / Debian 10 "buster". However, /gps/fix messages do not get published. There is nothing in the rosout / stdout of the gpsd_client node.
I can confirm that gpsmon shows up to date GPGGA and GPVTG messages being received. If I manually connect to gpsd's socket, I see:
$ nc localhost 2947
{"class":"VERSION","release":"3.17","rev":"3.17","proto_major":3,"proto_minor":12}
?WATCH={"enable":true,"json":true}
{"class":"DEVICES","devices":[{"class":"DEVICE","path":"udp://<IP_ADDRESS>:22335","driver":"NMEA0183","activated":"2022-04-22T20:56:34.300Z","flags":1}]}
{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false}
{"class":"TPV","device":"udp://<IP_ADDRESS>:22335","mode":3,"lat":41.524765833,"lon":-70.669887167,"alt":-2.970}
{"class":"TPV","device":"udp://<IP_ADDRESS>:22335","mode":3,"lat":41.524765833,"lon":-70.669887167,"alt":-2.970}
{"class":"TPV","device":"udp://<IP_ADDRESS>:22335","mode":3,"lat":41.524765833,"lon":-70.669887167,"alt":-2.970}
...

I am launching gpsdclient like so, and rosnode info confirms it (should be) publishing to /gps/fix as desired.
    <node name="gps" pkg="gpsd_client" type="gpsd_client">
        <remap from="/fix" to="~fix" />
        <remap from="/extended_fix" to="~extended_fix" />
    </node>

It looks from the output of lsof that maybe the connection was interrupted, but not automatically re-established.
COMMAND     PID USER   FD      TYPE  DEVICE SIZE/OFF    NODE NAME
gpsd_clie 20886 ifcb   10u     IPv6 1908883      0t0     TCP localhost:36308->localhost:gpsd (CLOSE_WAIT)
gpsd_clie 20886 ifcb   11u     IPv4 1909129      0t0     TCP ifcb152:56593->localhost:41384 (ESTABLISHED)
gpsd_clie 20886 ifcb   12u     IPv4 1983298      0t0     TCP ifcb152:56593->localhost:45266 (ESTABLISHED)
gpsd_clie 20886 ifcb   13u     IPv4 1908903      0t0     TCP ifcb152:56593->localhost:41214 (ESTABLISHED)
gpsd_clie 20886 ifcb   14u     IPv4 1908907      0t0     TCP ifcb152:56593->localhost:41216 (ESTABLISHED)
gpsd_clie 20886 ifcb   15u     IPv4 1908920      0t0     TCP ifcb152:56593->localhost:41232 (ESTABLISHED)
gpsd_clie 20886 ifcb   16u     IPv4 1908510      0t0     TCP ifcb152:56593->localhost:41234 (ESTABLISHED)

Is the node expected to handle this error condition? I am surprised it would not attempt to re-connect or at least log something and/or crash.

Note based on the file descriptor numbers this means that the connection to gpsd died almost immediately, before any of the other nodes were able to subscribe.
From the gpsd logs, it looks like it hit an error trying to open /dev/ttyUSB0 (which is not a GPS receiver). I disabled USBAUTO in my /etc/defaults/gpsd in the hope that this will avoid this error in the future and maybe prevent gpsd_client's connection from failing.

If gpsmm:read() returns NULL the client node just silently ignores it, rather than handling this condition.
(Also looks like there's a leak with not running delete gps; in stop() ?)

I can see with tcpdump that packets are being received by the client, here I've confirmed localhost:47456 corresponds to gpsd_client's connection:
17:37:54.506983 IP6 localhost.gpsd > localhost.47456: Flags [P.], seq 230:345, ack 1, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 115
        0x0000:  6003 2274 0093 0640 0000 0000 0000 0000<EMAIL_ADDRESS>        0x0010:  0000 0000 0000 0001 0000 0000 0000 0000  ................
        0x0020:  0000 0000 0000 0001 0b83 b960 d841 8ec6  ...........`.A..
        0x0030:  9a75 73bc 8018 0200 009b 0000 0101 080a  .us.............
        0x0040:  d20a d010 d20a cc28 7b22 636c 6173 7322  .......({"class"
        0x0050:  3a22 5450 5622 2c22 6465 7669 6365 223a  :"TPV","device":
        0x0060:  2275 6470 3a2f 2f31 3932 2e31 3638 2e31  "udp://192.168.1
        0x0070:  332e 3235 353a 3232 3333 3522 2c22 6d6f  3.255:22335","mo
        0x0080:  6465 223a 332c 226c 6174 223a 3431 2e35  de":3,"lat":41.5
        0x0090:  3234 3735 3130 3030 2c22 6c6f 6e22 3a2d  24751000,"lon":-
        0x00a0:  3730 2e36 3639 3838 3233 3333 2c22 616c  70.669882333,"al
        0x00b0:  7422 3a30 2e34 3030 7d0d 0a              t":0.400}..

Fix is silently being rejected because of this:
      if (std::isnan(p->fix.epx) && check_fix_by_variance) {
        return;
      }

Yes, we want to completely fill out the message before we publish it. Depending on what protocol you use, there's going to be different requirements on what provides this. GPSD supports a whole host of protocols, so we can't just specify NMEA 0183 messages. I think we can publish a throttled debug message there to help people out though.


Additional logging

Proposed changes
Log SelenideTargetLocator methods except alert one
alert is skipped to avoid duplicated logging with Modal methods (prompt/confirm/dismiss)
E.g.

Element
Subject

frame(index: 1)
switch to()

frame(mainFrame)
switch to()

parent frame
switch to()

default context
switch to()

active element
switch to()

window(index: 1)
switch to()

window(mainWindow)
switch to()

Log Selenide.closeWindow method call
Especially helpful when we operate with several windows in a test
E.g.

Element
Subject

current window
close()

Improve Modal methods log messages
Specify element as modal and subject as action for the element. See:
was:

Element
Subject

dismiss

dismiss
Are you sure?

prompt
->

prompt
Sure do ->

prompt
Sure do -> You really want it?

confirm

confirm
You really want it?

now:

Element
Subject

modal()
dismiss()

modal(Are you sure?)
dismiss()

modal()
prompt()

modal()
prompt(Sure do)

modal(Are you sure?)
prompt(Sure do)

modal()
confirm()

modal(Are you sure?)
confirm()

Checklist

[ ] Checkstyle and unit tests are passed locally with my changes by running gradlew check chrome_headless firefox_headless command
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

But I am not sure about the goal. Now we have a longer output (with lot of duplicate string "modal()") which doesn't give any more information. Is it worth it?

@asolntsev I am agree that now we produce a bit long output and I am ready to any proposals how to make them more clear and shorter. Currently Modal logging is implemented by SelenideTargetLocator analogy (please see updated PR description). As options here we can:

omit modal if expectedDialogText is set
replace modal with dialog
omit ()

E.g.

Element
Subject

dialog
dismiss()

Are you sure?
dismiss()

Any thoughts?

@fokinp In the beginning, I didn't realise we don't have any logging at all. I thought this PR is just an refactoring of an existing logging.
Thanks, merged.


More Themes is closed, but that doesn't mean I'm not going to stop adding themes. It's just, now I have a good amount of them, so I don't need a milestone. <3


[unitaryHACK] (#2) Qsharp support

These are changes I implemented for Qsharp platform. Please check it and then I'll make the commits to master.

Alright @Avhijit-codeboy great work! I will take it from here 😉


search_v2 not supported?

I figured out that Dropbox.Api.DropboxClient.Files.SearchAsync with parameters path, query, start, maxResults, mode maps to version 1 of the /search endpoint.
According to https://www.dropbox.com/developers/documentation/http/documentation this endpoint is DEPRECATED BY version 2. Version 2 also seems to be more powerful, e.g. search by file extension   (file_extensions).
How can I access the version 2 endpoint with the .NET SDK?

SearchV2 is supported as of 5.0.0, closing for now, let me know if there is any other issues.

Thanks for the update. I confirmed that SearchV2Async works as expected.
Only the Obsolete attributes in FileUserRoutes,cs look wrong.
    [sys.Obsolete("This function is deprecated, please use BeginCreateFolder instead.")]
    public sys.IAsyncResult BeginCreateFolder(string path, ...

-> BeginCreateFolder is deprecated use BeginCreateFolder instead? Same for most of the following methods.

@PaulBol Thanks for the note. You're correct, the generation of these deprecation warnings is currently broken. That's open with engineering to fix that up.


[Docs]Update jaxlib build from source

Most AWS EC2 docker images come with gcc 9.4 but will run into issues if trying to build Alpa from source. Updating to gcc 10 with clean bazel cache fixes it, thus updating developer guide for the community.

I think these instructions are already in  https://github.com/alpa-projects/alpa/blob/d1d9aa8fab31bec6f51d063b731cc0159009e73e/docs/install.rst#method-2-install-from-source

i see, this is indeed duplicated info then. I think my confusion mostly come from structure of the doc since developer guide part didn't mention the info needed to build & iterate tensorflow-alpa that is included in install section. How about I change this PR to link developer guide to installation ?

I don't think we need this because "Install" is the default place to find instructions for building the project.


How to debug istio's pilot component

How to debug the pilot component of istio? I try to use telepresence, but telepresence can only forward traffic on a specific port to the local.
I prefer a way to debug the pilot all the way (meaning from the start). Is there any way or suggestion?
Thanks.

What exactly are you looking to debug? if you need access tocertain ports you can use kubectl port-forward

Hi, I want to debug the entire life cycle of istio components. Take the pilot as an example. I want to debug its startup, accept configuration, push configuration to sidecar, etc.
Just like using dlv to remotely debug a normal golang project. I want to know how it works. Is there any good way?

You can use dlv (https://medium.com/@linsun_unc/debug-istio-components-with-goland-b0f9f9f60384 may help) just like any other golang app. You can also run it locally in a debugger connected to a remote k8s cluster. otherwise the localhost:8080/debug/* endpoints and logs are a good start

Thanks for answering. I will try the approach you mentioned.

You can also run it locally in a debugger connected to a remote k8s cluster.

This way seems better, any docs for help ?

hi, I tried to start pilot-discovery locally, and it seems to be working properly. I can receive config changes from k8s.
But there is still a problem, I cannot link to the sidecar in the k8s cluster. This means that I cannot debug the actual push process. What do I need to do, can some one help?
By the way, I think there is currently a lack of documentation on debugging code line by line in our documentation. Will this doc welcome?

Sure, you are welcome to suggest additional docs from http://github.com/istio/istio/wiki

@howardjohn
sorry for bothering.
I tried to let sidecar in the k8s cluster to connect to the local pilot to debug the information in the push process.
I add an annotation to the injected deployment file like this:
sidecar.istio.io/discoveryAddress: myhost:15010

to tell the sidecar connect to my pilot address.
After that, seems sidecar start failed..

May I ask what went wrong?
If this way is not correct, how can I connect the sidecar to the local pilot?

apiVersion: v1
kind: Service
metadata:
  name: helloworld
  labels:
    app: helloworld
spec:
  ports:
  - port: 5000
    name: http
  selector:
    app: helloworld
---
apiVersion: apps/v1
kind: Deployment
metadata:
  creationTimestamp: null
  labels:
    version: v1
  name: helloworld-v1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: helloworld
      version: v1
  strategy: {}
  template:
    metadata:
      annotations:
        prometheus.io/path: /stats/prometheus
        prometheus.io/port: "15020"
        prometheus.io/scrape: "true"
        sidecar.istio.io/interceptionMode: REDIRECT
        sidecar.istio.io/status: '{"version":"8e6e902b765af607513b28d284940ee1421e9a0d07698741693b2663c7161c11","initContainers":["istio-init"],"containers":["istio-proxy"],"volumes":["istio-envoy","istio-data","istio-podinfo","istiod-ca-cert"],"imagePullSecrets":null}'
        traffic.sidecar.istio.io/excludeInboundPorts: "15020"
        traffic.sidecar.istio.io/includeInboundPorts: "5000"
        traffic.sidecar.istio.io/includeOutboundIPRanges: '*'
        sidecar.istio.io/discoveryAddress: <IP_ADDRESS>:15010
      creationTimestamp: null
      labels:
        app: helloworld
        istio.io/rev: ""
        security.istio.io/tlsMode: istio
        version: v1
    spec:
      containers:
      - image: docker.io/istio/examples-helloworld-v1
        imagePullPolicy: IfNotPresent
        name: helloworld
        ports:
        - containerPort: 5000
        resources:
          requests:
            cpu: 100m
      - args:
        - proxy
        - sidecar
        - --domain
        - $(POD_NAMESPACE).svc.cluster.local
        - --serviceCluster
        - helloworld.$(POD_NAMESPACE)
        - --proxyLogLevel=warning
        - --proxyComponentLogLevel=misc:error
        - --trust-domain=cluster.local
        - --concurrency
        - "2"
        env:
        - name: JWT_POLICY
          value: first-party-jwt
        - name: PILOT_CERT_PROVIDER
          value: istiod
        - name: CA_ADDR
          value: istiod.istio-system.svc:15012
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: INSTANCE_IP
          valueFrom:
            fieldRef:
              fieldPath: status.podIP
        - name: SERVICE_ACCOUNT
          valueFrom:
            fieldRef:
              fieldPath: spec.serviceAccountName
        - name: HOST_IP
          valueFrom:
            fieldRef:
              fieldPath: status.hostIP
        - name: CANONICAL_SERVICE
          valueFrom:
            fieldRef:
              fieldPath: metadata.labels['service.istio.io/canonical-name']
        - name: CANONICAL_REVISION
          valueFrom:
            fieldRef:
              fieldPath: metadata.labels['service.istio.io/canonical-revision']
        - name: PROXY_CONFIG
          value: |
            {"proxyMetadata":{"DNS_AGENT":""}}
        - name: ISTIO_META_POD_PORTS
          value: |-
            [
                {"containerPort":5000}
            ]
        - name: ISTIO_META_APP_CONTAINERS
          value: helloworld
        - name: ISTIO_META_CLUSTER_ID
          value: Kubernetes
        - name: ISTIO_META_INTERCEPTION_MODE
          value: REDIRECT
        - name: ISTIO_META_WORKLOAD_NAME
          value: helloworld-v1
        - name: ISTIO_META_OWNER
          value: kubernetes://apis/apps/v1/namespaces/default/deployments/helloworld-v1
        - name: ISTIO_META_MESH_ID
          value: cluster.local
        - name: DNS_AGENT
        - name: ISTIO_KUBE_APP_PROBERS
          value: '{}'
        image: docker.io/istio/proxyv2:1.7.3
        imagePullPolicy: Always
        name: istio-proxy
        ports:
        - containerPort: 15090
          name: http-envoy-prom
          protocol: TCP
        readinessProbe:
          failureThreshold: 30
          httpGet:
            path: /healthz/ready
            port: 15021
          initialDelaySeconds: 1
          periodSeconds: 2
        resources:
          limits:
            cpu: "2"
            memory: 1Gi
          requests:
            cpu: 10m
            memory: 40Mi
        securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            drop:
            - ALL
          privileged: false
          readOnlyRootFilesystem: true
          runAsGroup: 1337
          runAsNonRoot: true
          runAsUser: 1337
        volumeMounts:
        - mountPath: /var/run/secrets/istio
          name: istiod-ca-cert
        - mountPath: /var/lib/istio/data
          name: istio-data
        - mountPath: /etc/istio/proxy
          name: istio-envoy
        - mountPath: /etc/istio/pod
          name: istio-podinfo
      initContainers:
      - args:
        - istio-iptables
        - -p
        - "15001"
        - -z
        - "15006"
        - -u
        - "1337"
        - -m
        - REDIRECT
        - -i
        - '*'
        - -x
        - ""
        - -b
        - '*'
        - -d
        - 15090,15021,15020
        env:
        - name: DNS_AGENT
        image: docker.io/istio/proxyv2:1.7.3
        imagePullPolicy: Always
        name: istio-init
        resources:
          limits:
            cpu: "2"
            memory: 1Gi
          requests:
            cpu: 10m
            memory: 10Mi
        securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            add:
            - NET_ADMIN
            - NET_RAW
            drop:
            - ALL
          privileged: false
          readOnlyRootFilesystem: false
          runAsGroup: 0
          runAsNonRoot: false
          runAsUser: 0
      securityContext:
        fsGroup: 1337
      volumes:
      - emptyDir:
          medium: Memory
        name: istio-envoy
      - emptyDir: {}
        name: istio-data
      - downwardAPI:
          items:
          - fieldRef:
              fieldPath: metadata.labels
            path: labels
          - fieldRef:
              fieldPath: metadata.annotations
            path: annotations
        name: istio-podinfo
      - configMap:
          name: istio-ca-root-cert
        name: istiod-ca-cert
status: {}
---

injected file like this, use istio 1.7.3.

2020-11-19T13:30:27.298249Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers. reset reason: connection failure
2020-11-19T13:30:31.139021Z	warn	Envoy proxy is NOT ready: config not received from Pilot (is Pilot running?): cds updates: 0 successful, 0 rejected; lds updates: 0 successful, 0 rejected

sidecar.istio.io/controlPlaneAuthPolicy: "NONE"

Also not worked.. Seems like envoy can't connect to my local host, some suggestions? @howardjohn

ping...

Hi, is this problem solved？I get this problem while there is a envoyfilter configed and solve it by deleting this envoyfilter.
I don't know why but it is certain that this problem will  make us unable to update POD properly

Hi, is this problem solved？I get this problem while there is a envoyfilter configed and solve it by deleting this envoyfilter.
I don't know why but it is certain that this problem will  make us unable to update POD properly


404 at /compose/install/%E2%80%A8

I found a broken link : https://docs.docker.com/compose/install/

I arrived on this page through: https://yoandev.co/

Looks like a broken link on https://yoandev.co/ the correct URL should be https://docs.docker.com/compose/install/
If you know on what page the broken link was, I suggest reporting this to the owner of https://yoandev.co/.
I'm closing this ticket, because this is not something we can fix in our docs, but feel free to continue the conversation

Looks like a broken link on https://yoandev.co/ the correct URL should be https://docs.docker.com/compose/install/
If you know on what page the broken link was, I suggest reporting this to the owner of https://yoandev.co/.
I'm closing this ticket, because this is not something we can fix in our docs, but feel free to continue the conversation


Replace OrbitCodeEditor

This replaces the Qt-example-based OrbitCodeEditor by our own implementation that is feature-wise on par and won't
give us potential license/copyright headaches.
The dialog looks slighty different:

The new dialog has a "Close" button at the bottom. This is mainly for Linux users, where - depending on the desktop environment - dialogs are supposed to have a close button, because the window decorations don't include one.
Furthermore this PR removes all the appearances of the old code tab which will come back differently.

Very well ordered PR, I liked it!
I have a last question, did you realize that in long functions, there is almost no coloring at all in the left?

This is intended/how the data is. Most functions are basically "just" calling other functions. So I will only see the call instruction coloured. For the rest, you will have a hard time finding a sample that hits another instruction. There should be actually already code, to make smaller hits more visible (it used to be done by sqrt(percentage)).

Very well ordered PR, I liked it!
I have a last question, did you realize that in long functions, there is almost no coloring at all in the left?

This is intended/how the data is. Most functions are basically "just" calling other functions. So I will only see the call instruction coloured. For the rest, you will have a hard time finding a sample that hits another instruction. There should be actually already code, to make smaller hits more visible (it used to be done by sqrt(percentage)).

There should be actually already code, to make smaller hits more visible (it used to be done by sqrt(percentage)).

Yes, I was speaking on something like "sqrt" to color a little bit more. Sorry if I missed context, I didn't use to pay attention to coloring before.

There should be actually already code, to make smaller hits more visible (it used to be done by sqrt(percentage)).

Yes, I was speaking on something like "sqrt" to color a little bit more. Sorry if I missed context, I didn't use to pay attention to coloring before.

Very well ordered PR, I liked it!
I have a last question, did you realize that in long functions, there is almost no coloring at all in the left?

No. I haven't seen that. Do you have a screenshot?

Very well ordered PR, I liked it!
I have a last question, did you realize that in long functions, there is almost no coloring at all in the left?

No. I haven't seen that. Do you have a screenshot?

There should be actually already code, to make smaller hits more visible (it used to be done by sqrt(percentage)).

Yes, I was speaking on something like "sqrt" to color a little bit more. Sorry if I missed context, I didn't use to pay attention to coloring before.

I didn't change the coloring behaviour. So the sqrt is still in there. If something can be improved in that logic, I'd prefer to do it in another PR.

There should be actually already code, to make smaller hits more visible (it used to be done by sqrt(percentage)).

Yes, I was speaking on something like "sqrt" to color a little bit more. Sorry if I missed context, I didn't use to pay attention to coloring before.

I didn't change the coloring behaviour. So the sqrt is still in there. If something can be improved in that logic, I'd prefer to do it in another PR.

Hi Henning! Nice PR! I'm only reviewing the first commit here.
I have 2 general comments:
1- Zooming is having issues because we aren't updating the font-size of the line numbers. This is having issues both with zooming-in and also zooming-out. Attached a screenshot:

Hmmm. That's weird. Zooming definitely worked at some point. I will test again.

2- When the code is loading, we are having a very strange state. What do you think about having everything black until we load the code?

Hmmm. It seems the draw calls don't get through. I have to investigate further. How long does it actually take for you to load long functions?

Hi Henning! Nice PR! I'm only reviewing the first commit here.
I have 2 general comments:
1- Zooming is having issues because we aren't updating the font-size of the line numbers. This is having issues both with zooming-in and also zooming-out. Attached a screenshot:

Hmmm. That's weird. Zooming definitely worked at some point. I will test again.

2- When the code is loading, we are having a very strange state. What do you think about having everything black until we load the code?

Hmmm. It seems the draw calls don't get through. I have to investigate further. How long does it actually take for you to load long functions?

Hmmm. It seems the draw calls don't get through. I have to investigate further. How long does it actually take for you to load long functions?

~300 lines -> 6 seconds

Hmmm. It seems the draw calls don't get through. I have to investigate further. How long does it actually take for you to load long functions?

~300 lines -> 6 seconds

LGTM!! Feel free to address the zooming and the coloring in another PR

Thanks Pablo. Zooming is a bug. I will address this here. Coloring is a different story though - so definitely in another PR.

LGTM!! Feel free to address the zooming and the coloring in another PR

Thanks Pablo. Zooming is a bug. I will address this here. Coloring is a different story though - so definitely in another PR.

Hey, good changes so far!
I just tested again on Linux and the results might help you:

Zooming behaves (almost) as intended in the Demo. It still does not in Orbit. "Almost" because in the demo, a white bar appears in some zoom levels.
Left side of screenshot: Orbit; right side: CodeViewerDemo

The cutoff of numbers I reported earlier is still there, even with your fix of the function and tests

Since the first bullet point is not very critical and the second one only happens on Linux, I would be okay to merge this as is. I am not sure if these small cosmetic problems are worth your time.

Hey, good changes so far!
I just tested again on Linux and the results might help you:

Zooming behaves (almost) as intended in the Demo. It still does not in Orbit. "Almost" because in the demo, a white bar appears in some zoom levels.
Left side of screenshot: Orbit; right side: CodeViewerDemo

The cutoff of numbers I reported earlier is still there, even with your fix of the function and tests

Since the first bullet point is not very critical and the second one only happens on Linux, I would be okay to merge this as is. I am not sure if these small cosmetic problems are worth your time.

Hey, good changes so far!
I just tested again on Linux and the results might help you:

Zooming behaves (almost) as intended in the Demo. It still does not in Orbit. "Almost" because in the demo, a white bar appears in some zoom levels.
Left side of screenshot: Orbit; right side: CodeViewerDemo

Yes, that helped. Thanks! Fix follows in a minute.

The cutoff of numbers I reported earlier is still there, even with your fix of the function and tests

It's basically the same problem as in bullet point 1. When font information is not propagated properly, Qt will pick a different (system-defined) font than used for the size calculations. If that font happens to be wider than the intended font (as in your case), then the numbers are cut off.

Since the first bullet point is not very critical and the second one only happens on Linux, I would be okay to merge this as is. I am not sure if these small cosmetic problems are worth your time.

I will fix 1. and like described above, I'm confident that this also fixes 2.

Hey, good changes so far!
I just tested again on Linux and the results might help you:

Zooming behaves (almost) as intended in the Demo. It still does not in Orbit. "Almost" because in the demo, a white bar appears in some zoom levels.
Left side of screenshot: Orbit; right side: CodeViewerDemo

Yes, that helped. Thanks! Fix follows in a minute.

The cutoff of numbers I reported earlier is still there, even with your fix of the function and tests

It's basically the same problem as in bullet point 1. When font information is not propagated properly, Qt will pick a different (system-defined) font than used for the size calculations. If that font happens to be wider than the intended font (as in your case), then the numbers are cut off.

Since the first bullet point is not very critical and the second one only happens on Linux, I would be okay to merge this as is. I am not sure if these small cosmetic problems are worth your time.

I will fix 1. and like described above, I'm confident that this also fixes 2.


Redeploy of bundle fails with "changing network in service is not supported"

When trying to redeploy an application stack I get an error.
Output of docker-compose version:
docker-compose version 1.8.0-rc1, build 9bf6bc6
docker-py version: 1.8.1
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.2h  3 May 2016

Output of docker version:
Client:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:
 OS/Arch:      linux/amd64
 Experimental: true

Server:
 Version:      1.12.0-rc3
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   91e29e8
 Built:
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:
Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 4
Server Version: 1.12.0-rc3
Storage Driver: devicemapper
 Pool Name: docker-253:1-102770625-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 860 MB
 Data Space Total: 107.4 GB
 Data Space Available: 88.78 GB
 Metadata Space Used: 2.003 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.107-RHEL7 (2015-12-01)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null overlay host bridge
Swarm: active
 NodeID: 9e8nin7xym2f8664naactgohw
 IsManager: Yes
 Managers: 1
 Nodes: 3
 CACertHash: sha256:a20a2e0e1fcae3973390598ebcb5526f9d780a97ec8ba3e081ddcb2ef8804de5
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-327.18.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 6
Total Memory: 15.51 GiB
Name: tckjenkins
ID: 5ZUJ:X7XR:2NQD:CGMT:LKLI:5OBB:HMMX:I5X6:5EMP:EVLG:RGLO:OCVK
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Experimental: true
Insecure Registries:
 tckdockertest1.ticket.se:5000
 tckjenkins.ticket.se:5000
 tckjenkins:5000
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
This is a vmware machine.
Steps to reproduce the issue:

docker stack deploy docker -f docker.dsb
docker stack deploy docker -f docker.dsb

Describe the results you received:
Output of docker stack deploy docker -f docker.dsb:
Loading bundle from docker.dsb
Updating service docker_metaws (id: 02gekibnc4m52nbg45v056fok)
Error response from daemon: rpc error: code = 2 desc = changing network in service is not supported

The bundle files is generated with docker-compose from a docker-compose.yml without any network settings. Each service in the bundle file then got this network setting:
      "Networks": [
        "default"
      ],

Describe the results you expected:
That the stack would be redeployed.
Additional information you deem important (e.g. issue happens only occasionally):
Happens every time.

The docker commands where run on the machine with the docker engine that is the leader of the swarm.
Output of docker swarm ls:
ID                           HOSTNAME        MEMBERSHIP  STATUS  AVAILABILITY  MANAGER STATUS
3xci8topyonumln761nhy9ny8    dockertest1  Accepted    Ready   Active
9e8nin7xym2f8664naactgohw *  jenkins      Accepted    Ready   Drain         Leader
dufrizm707ilwrqyd7xzdvm5b    dockertest2  Accepted    Ready   Active

@msvticket thanks for reporting the issue.
The error happens here : https://github.com/docker/swarmkit/blob/master/manager/controlapi/service.go#L249
But since this is just a service update with the same network, the DeepEqual should have worked.
It could be an issue in the bundle deploy code. I will confirm it.


Hailo8L on Raspberry Pi 5 on Ubuntu24

No package located for Ubuntu 24
ubuntu@rpi5-orso-1:~$ sudo apt install hailo-all Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package hailo-all
Ubuntu 24 does detect the Halio accelerator and it is running at PCIe speed 3.0
`
ubuntu@rpi5-orso-1:~$ sudo lshw
*-pci:1
description: PCI bridge
product: BCM2712 PCIe Bridge
vendor: Broadcom Inc. and subsidiaries
physical id: 101
bus info: pci@0001:00:00.0
version: 21
width: 32 bits
clock: 33MHz
capabilities: pci pm pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:166 ioport:1800000000(size=1048576)
*-processor UNCLAIMED
description: Co-processor
product: Hailo-8 AI Processor
vendor: Hailo Technologies Ltd.
physical id: 0
bus info: pci@0001:01:00.0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm cap_list
configuration: latency=0
resources: iomemory:40-3f iomemory:40-3f iomemory:40-3f memory:1800000000-1800003fff memory:1800008000-1800008fff memory:1800004000-1800007fff
ubuntu@rpi5-orso-1:~$ sudo lspci -vv | grep -E 'PCI bridge|LnkCap'
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
LnkCap: Port #0, Speed 5GT/s, Width x4, ASPM L1, Exit Latency L1 <2us
LnkCap2: Supported Link Speeds: 2.5-5GT/s, Crosslink- Retimer- 2Retimers- DRS+
LnkCap: Port #0, Speed 5GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <1us, L1 <2us
LnkCap2: Supported Link Speeds: 2.5-5GT/s, Crosslink- Retimer- 2Retimers- DRS-
0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <2us
LnkCap2: Supported Link Speeds: 2.5-5GT/s, Crosslink- Retimer- 2Retimers- DRS+
LnkCap: Port #0, Speed 8GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <1us, L1 <2us
LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
`

That makes sense since the instructions  (https://github.com/hailo-ai/hailo-rpi5-examples/blob/main/doc%2Finstall-raspberry-pi5.md) have latest Raspberry Pi OS (not Ubuntu-24.04) as prerequisite.
Hopefully if should be straighforward to port (or just install) hailo-all package on  Ubuntu 24.04, but I have no first-hand experience with Hailo hardware to comment.

Maybe this document could be useful: https://github.com/hailo-ai/tappas/blob/master/docs%2Finstallation%2Fmanual-install.rst
However it supports only Ubuntu 20.04 and 22.04, therefore be prepared to run into issues with 24.04.

Is there any update on this?

I have find a docker image https://hub.docker.com/layers/alwaysai/edgeiq/hailo-amd64-latest/images/sha256-17c678f8889e842dea327000c1273c4e599f83c00c4a18af303ff3d8479f34a0?context=explore , but it is Private.


Enhancement save schedule, is lost on each deploy

Hi,
Very nice node 👍 keep it going.
I'm planning to make my node to accept also your schedule format. My node needs an interface for scheduling. Currently, I use a json in admin interface but I would like to have something that you did for a friendly interface and I don't have time to implement that and to be honest, if you are maintaining yours is ok.
My node controls a heater heater-controller.
And I've installed  ui-time-scheduler on my node-red dev instance and I noticed that you don't save the schedules and on every deploy the user has to input again the values
Maybe you are thinking to save that because when you are working with node-red you do a lot of changes and you have to redeploy offen the flows.
Have have fun!
Sergiu

Hi,
it is very easy to save schedules already. You can save and reinject them on every deploy.
The Readme even shows a screenshot of how it is done:

Did you see that?

Hi,
it is very easy to save schedules already. You can save and reinject them on every deploy.
The Readme even shows a screenshot of how it is done:

Did you see that?

Yes I saw it :) I know that there are ways to do that I think you can save it in flow or in general but when you have a schema like this .... you want to have less nodes :D

Yes I saw it :) I know that there are ways to do that I think you can save it in flow or in general but when you have a schema like this .... you want to have less nodes :D

The node red API does not allow the alter a nodes property from the UI - or at least not in a very good way - because you would have to hit the deploy button from the flow editor after (see here).

The node red API does not allow the alter a nodes property from the UI - or at least not in a very good way - because you would have to hit the deploy button from the flow editor after (see here).

I don't understand why, I could do it and works fine.

I don't understand why, I could do it and works fine.

Your node saves the schedule directly within the flow editor - after that you just deploy and it is all good. Unfortunately it is not that easy if you want to change properties from anywhere else.
Do you have an example of where you changed your properties from outside the (flow editor) node settings?

Your node saves the schedule directly within the flow editor - after that you just deploy and it is all good. Unfortunately it is not that easy if you want to change properties from anywhere else.
Do you have an example of where you changed your properties from outside the (flow editor) node settings?

Yes, I'm saving on node context with node.context().set("config", values);
like the topic setCalendar ? the schedule be set in editor in a text field but also can be send as input message. but I think is not changing the editor content ... or that's your problem?
Nevertheless the implementation of an ui node is a nightmare, I have to do so many hacks to have a clean flow.... I'm currently doing a heavy refactoring on it because after a year or so is hard to read the code and now I know better what I want

Yes, I'm saving on node context with node.context().set("config", values);
like the topic setCalendar ? the schedule be set in editor in a text field but also can be send as input message. but I think is not changing the editor content ... or that's your problem?
Nevertheless the implementation of an ui node is a nightmare, I have to do so many hacks to have a clean flow.... I'm currently doing a heavy refactoring on it because after a year or so is hard to read the code and now I know better what I want

Like for example to change refresh value which appear in flow editor but to do it from interface or? what do you  mean by Properties?

Like for example to change refresh value which appear in flow editor but to do it from interface or? what do you  mean by Properties?

Yes with properties I meant values like the refresh property but I see now that you were talking about the nodes context. By default, whenever something is stored into a nodes context then it is gone after a redeploy as well. I suppose you are using "localfilesystem" for your "contextStorage"?

Yes with properties I meant values like the refresh property but I see now that you were talking about the nodes context. By default, whenever something is stored into a nodes context then it is gone after a redeploy as well. I suppose you are using "localfilesystem" for your "contextStorage"?

yes I'm using LocalFileSystem.
If you want to messages from front to change the properties, maybe a config/server node can solve your problem. I did not test that but are some how different;
you can take a look on mqtt node, there is a server node. I don't know too much about that but I think it worth's to take a look.

Well... it shouldn't be a big issue to replace the local variable, that currently holds the timers, with the nodes context. That way users with unmodified contextStorage settings wouldn't notice any differences and users (like you) with a contextStorage/localfilesystem would not have to save separately.
I am going to take a deeper look at it this week and let you know as soon as I know more.

I've done it like this, to be honest, because I can see what is the status in context tab :D

1.7.0 now stores everything within the nodes context - it should be available on npm soon! I'd appreciate  your feedback!


Error when npm package readme is utf-8 encoded: "readme_file.rb:42:in `match': invalid byte sequence in US-ASCII (ArgumentError)"

Hi,
I continue to play with licensed under docker...
I encounter an issue when I add uuid to my package.json file. Here are the necessary files to reproduce this behaviour:
.licensed.yaml
name: 'placement-back'
cache_path: '/app/test2/.licenses'
source_path: '/app/test2'
sources:
  npm: true
allowed:
  - mit

package.json
{
  "name": "placement-back",
  "version": "0.0.0",
  "dependencies": {
    "uuid": "^3.2.1"
  }
}

And the commands/output within my docker image:
$ cd /app/test2
$ npm update -f
$ licensed cache
Caching licenses for placement-back:
  npm dependencies:
/usr/local/bundle/gems/licensed-1.1.0/lib/licensed/shell.rb:17:in `execute': command exited with status 1 (Licensed::Shell::Error)
  npm list --parseable --production --long
    npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/source/npm.rb:66:in `npm_list_command'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/source/npm.rb:55:in `package_location_command'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/source/npm.rb:23:in `dependencies'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/command/cache.rb:29:in `block (3 levels) in run'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/command/cache.rb:20:in `map'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/command/cache.rb:20:in `block (2 levels) in run'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/command/cache.rb:17:in `chdir'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/command/cache.rb:17:in `block in run'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/command/cache.rb:12:in `each'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/command/cache.rb:12:in `flat_map'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/command/cache.rb:12:in `run'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/cli.rb:48:in `run'
	from /usr/local/bundle/gems/licensed-1.1.0/lib/licensed/cli.rb:17:in `cache'
	from /usr/local/bundle/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
	from /usr/local/bundle/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
	from /usr/local/bundle/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
	from /usr/local/bundle/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
	from /usr/local/bundle/gems/licensed-1.1.0/exe/licensed:5:in `<top (required)>'
	from /usr/local/bundle/bin/licensed:23:in `load'
	from /usr/local/bundle/bin/licensed:23:in `<main>'

I think this occurs when the README.md file is utf-8 encoded; I also see this behaviour for other packages.
I'm not sure this is a licensed bug; maybe a licensee bug as the error occurs in /usr/local/bundle/gems/licensee-9.9.1/lib/licensee/project_files/readme_file.rb:42 file?
As a workaround; I simply seach and overwrite all README/AUTHORS files with an empty content:
	find . -type f -name "README.md" -exec bash -c "echo > '{}'" \;
	find . -type f -name "Readme.md" -exec bash -c "echo > '{}'" \;
	find . -type f -name "readme.md" -exec bash -c "echo > '{}'" \;
	find . -type f -name "AUTHORS" -exec bash -c "echo > '{}'" \;

Then if I re-run the licensed command:
$ licensed cache
Caching licenses for placement-back:
  npm dependencies:
    Caching uuid (3.2.1)
License caching complete!
* placement-back npm dependencies: 1

Without (utf-8) content, it works; but I guess this is not a good workaround.
Any idea for a better process?
Regards,
Chris

:wave: @cnaslain glad to see things are still moving along.
It looks like the error you posted is from a missing package, e.g. not having run npm install first.  Since the issue is about utf-8 encoded content I'm assuming this is the wrong stack trace and you already got past that 👍
There's a long term and a (probable) short term fix for this.
Long term: If you have the time and are feeling up to it, you can fix this in licensee!  This was reported in licensee awhile back but it looks like the fix was never followed up on and didn't make it into the gem.
Short term:  Try adding ENV LANG C.UTF-8 to your Dockerfile.  That's fixed what I think is the same issue for me, when I was playing around with docker + licensed 😄

@jonabc Thanks for the tip! Adding ENV LANG C.UTF-8 to my dockerfile did the job :-)


The Microsoft.Extensions.Caching.Redis is not support netcoreapp1.0?

When I import Microsoft.Extensions.Caching.Redis package from nuget,error occured:
The dependency Microsoft.Extensions.Caching.Redis 1.0.0-rc2-final does not support framework .NETCoreApp,Version=v1.0.
My "frameworks" config in project.json just like this:
"frameworks": {
    "netcoreapp1.0": {
      "imports": [
        "dotnet5.6",
        "dnxcore50",
        "portable-net45+win8"
      ]
    }
  }

Duplicate: https://github.com/aspnet/Caching/issues/121

So what should I do to solve this problem?

@xbuilder read the linked issue. It doesn't work on .NET Core yet and won't work until 1.0.1.


the browser cannot access <IP_ADDRESS>:8082

Upgrade Intellij Idea from 2021.3.3 to 2022.2.3. Run the./gradlew ui-test-example:runIdeForUiTests command to bring up the Welcome to Intellij IDEA interface.  However, the browser cannot access <IP_ADDRESS>:8082.  netstat -nlp | grep 8082 command did not query to the process, using the JDK and JBR version is 17, configuration:
systemProperty "robot-server.port", "8082"
systemProperty "ide.mac.message.dialogs.as.sheets", "false"
systemProperty "jb.privacy.policy.text", ""
systemProperty "jb.consents.confirmation.enabled", "false"

Hi, could you please clarify the version of remote-robot-server plugin, you can check it in Settings -> Plugins in idea which was lanched with runIdeForUiTests.

here is the configuration:
def remoteRobotVersion = "0.11.3"
dependencies {
testImplementation 'org.junit.jupiter:junit-jupiter-api:5.7.0'
testImplementation 'com.intellij.remoterobot:remote-robot:' + remoteRobotVersion
testImplementation 'com.intellij.remoterobot:remote-fixtures:' + remoteRobotVersion
}
The old version is 0.11.3. And I tried 0.11.16 and 0.11.17.

can you try to set last robot-server version by configuring downloadRobotServer task?
downloadRobotServerPlugin  {
    version.set('0.11.18')
}

thanks


TestCafe 0.23.1 hangs indefinitely on concurrency

What is your Test Scenario?
Running tests in concurrency in Windows 10 and Node 6.10.3 with TestCafe 0.23.1
What is the Current behavior?
The tests start to run normally, but the status for the first test is the only one that shows in the command prompt.  Eventually the browsers either show the TestCafe start page or are on the start pageURL and are just awaiting further commands from hammerhead.  They just stay this way until I abort by pressing CTRL + C.
What is the Expected behavior?
Concurrent tests should just as they did in TestCafe 0.22.0
What is your web application and your TestCafe test code?
I can't put the actual tests on here but I could probably make a sample eventually.
Execute this command...
See the error...

Your Environment details:

testcafe version:                   0.23.1
node.js version:                    6.10.3
command-line arguments:
browser name and version: Chrome 70
platform and version:          Windows 10
other:

Unfortunately, I can't reproduce this behavior. Could you please provide a HAR report or record a screencast of your test session?
Judging by the description, the problem can be caused by Chrome's background tabs throttling feature. When Chrome suspends a background tab, it can't respond to the TestCafe server and thus can't execute any test command. Try to specify the --disable-background-timer-throttling flag in the TestCafe CLI parameters:
testcafe "chrome --disable-background-timer-throttling" tests.jd

and manually focus each Chrome window when it is opened.

Hi @AndreyBelym ,
Thank you so much for your response.  I don't think the Chrome background tabs throttling feature is the issue, because I tried the tests in concurrency with Firefox and was also getting the same problems.
What's strange is that concurrency works if things are simple. I tried to run concurrency if only one test is used and it worked fine.
I tried tests in https://github.com/DevExpress/testcafe/tree/master/examples/basic , and they also worked fine.
I then added two roles which caused the tests not to update status on the console till the end, but eventually they did.
However once I added a test-cafe-vue-selector it repeated the same behavior.  Essentially the test code runs, but the status only gets updated for the first or second tests and the process then hangs indefinitely.
So I think the problem is with the latest version of TestCafe (0.23.1) and testcafe-vue-selectors.
I pushed up the code to my GitHub here.
You can clone and just run npm test to reproduce.  Thanks so much again!
-Dave

Thank you for your feedback!
I've found that your example works fine with the -c 2 argument on my machine. The relation between resources of your machine and the maximum number of browsers that you can use in a testing session is not linear. We will try to keep TestCafe responsive even when the performance capabilities are not enough to run all requested browsers and use browser resources more efficiently in no article here concurrency mode.

My pleasure!
What's interesting here though is if you run these tests with Test Cafe v 0.22.0, everything finishes.   This repo illustrates problems with my current tests because they run concurrently in v 0.22.0 with -c 4 without a hitch, but they become problematic when run concurrently with TestCafe 0.32.1 with -c -4.
I made another repo with everything being same except using Test Cafe v 0.22.0 that runs in a stable state with 4 concurrent instances if you'd like to check it out:  https://github.com/dbschwartz/test-cafe-error-demo-stable
Note the test statuses take about 10 seconds before they start updating, but they eventually do and everything finishes and closes as normal.
My guess is that maybe there was some new server code introduced that might have lent itself to this.  Perhaps it's related to handling the unhandled promise rejection errors that were happening in concurrency before.  Again just a guess.
When I have use concurrency in other applications, its usually recommended to somewhat match instances with the number of cores on the machine, maybe using one less, i.e. If there are 7 cores, use  6 instances, etc.. I have been testing on machines with more than 4 processors.  Should Test Cafe be run fairly conservatively with concurrency?
Thank you so much for all your help!

Apologies if you recently cloned the repo, my changes weren't pushed till now.  The other abnormal thing I realized is that with v 0.23.1 it seems only 2 of the concurrent instances are actually being used during the test execution.  The other 2 just seem to be idle on the Test Cafe example page for most of the test run without any actions, commands, assertions being run.  Granted this isn't the ideal scenario, but still strange none-the-less.  This does not happen in v 0.22.0

Also, after I run concurrency with -c -4 in v 0.22.0 I also get the following:
(node:15240) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
This is just a warning, but might concern some users.  Maybe those who use concurrency should increase their max listeners in Node.

I tried to reproduce the problem with<EMAIL_ADDRESS>on my machine but it seems to be fixed. Could you please try to update the TestCafe version in your package.json and run tests in your environment?

Yes!! I tried it!  Looks great!!  Only thing I might want to add is these two tests seem to be failing randomly.  They fail on testcafe 0.22.0 too so I don't think it's due to a bug in the package.  I think perhaps maybe the Test Cafe Example site was updated (https://devexpress.github.io/testcafe/example/).  Might just want to update your tests to reflect the change.  Minor, but just wanted to let you know.  Thanks again for all your help! Love this software.

@dbschwartz, it seems that the bug is caused by using a role in the test: https://github.com/dbschwartz/test-cafe-error-demo-stable/blob/master/tests/testsCafeExamples1/test3.js#L7. I've created separate ticket #3232  about this issue.


Show Directory view of build_[city] chapters

Context
In order to get additional context about any build_[city] chapter, it is necessary to have a directory view that shows users and their associated digital + physical communities.
User Stories
As a user, I want to be able to see a directory of all the users in a build_[city] chapter, their associated networks, and their associated country chapters.
As a user, I want to access another user's profile
As a user, I want to be able to apply filters for my preferred digital network communities
As a user, I want to be able to access my favorite city chapters at any time
As a user, I want to explore build_[city] chapters that I have not yet joined
Requirements
General Requirements
-Users cannot join more than 5 cities
-Users can have no more than 5 associated digital networks/community filters
-Will need to associate and display an emoji flag for the country that each city is a part of (current and future cities)
Data Requirements
-Available City Chapters are located in attached
build__-_City_NFTs_1.csv
CSV file
Discord API Data:
-Server Icon
-Discord ID
-Discord Picture
Internal Data:
-Selected Networks
-Associated Cities
-User-defined ID (if changed from Discord)
-User profile photo (if changed from Discord)
-Associated country emoji flags to match user city selections
Relevant Links
https://www.figma.com/file/ZEEkd0VqeQT1b97S60WMrL/Build_dApp?node-id=714%3A31734
https://www.figma.com/file/ZEEkd0VqeQT1b97S60WMrL/Build_dApp?node-id=714%3A31759
https://www.figma.com/file/ZEEkd0VqeQT1b97S60WMrL/Build_dApp?node-id=714%3A31786
https://www.figma.com/file/ZEEkd0VqeQT1b97S60WMrL/Build_dApp?node-id=714%3A31836
https://www.figma.com/file/ZEEkd0VqeQT1b97S60WMrL/Build_dApp?node-id=714%3A31811

Subtasks and Acceptance Criteria

[ ] Filters allow for up to 5 cities + global directory
[ ] Filters allow for up to 5 networks + global directory
[ ] Ability to click into a profile directly from the directory
[ ] Ability to add/remove city filters
[ ] Ability to add/remove network filters
[ ] Ability to navigate to a city that they have not joined (CC: @psa-psa still refining this ability)


Ability to locally debug E2E tests

PR for issue #1420
What is being addressed
Debug the E2E tests without setting any .ENV files
How is this addressed

Streamline some ENV vars
Add correct launch settings
Amend Smoke Tests to use AUTOMATION ACCOUNT

/test

/test


Remove support for deprecated annotations without hashtag

We have deprecated annotations that do not start with a hashatag since 2021-05-18 ( 03e036d8 ). We should now fully remove those to reduce code complexity.

Fixed by #130


Fix related assemblies count and Thoas gRPC bug

JIRA Ticket
https://www.ebi.ac.uk/panda/jira/browse/EA-1131
Changes

Fixed IndexError: list index out of range when returning related assembly count

I mistakingly used fetch_organisms_group_counts()
Added a fetch_related_assemblies_count() which does the count for a given species_taxonomy_id

Fixed a bug where GraphQL gRPC request was able to fetch unreleased data (EA-1131)

JIRA Ticket
https://www.ebi.ac.uk/panda/jira/browse/EA-1131
Changes
* Fixed `IndexError: list index out of range` when returning related assembly count

  * I mistakingly used `fetch_organisms_group_counts()`
  * Added a `fetch_related_assemblies_count()` which does the count for a given `organisms_id`

* Fixed a bug where GraphQL gRPC request was able to fetch unreleased data ([EA-1131](https://www.ebi.ac.uk/panda/jira/browse/EA-1131))

Response in web which was broken earlier
curl 'http://localhost:8014/api/metadata/genome/d1d26e8d-cd86-4c69-b2d3-13bfd702b033/explain' | jq
{
  "genome_id": "d1d26e8d-cd86-4c69-b2d3-13bfd702b033",
  "genome_tag": null,
  "species_taxonomy_id": "10089",
  "common_name": "Ryukyu mouse",
  "scientific_name": "Mus caroli",
  "type": {
    "kind": "strain",
    "value": null
  },
  "is_reference": false,
  "assembly": {
    "accession_id": "GCA_900094665.2",
    "name": "CAROLI_EIJ_v1.1"
  }
}


Use configured proxy port for containers.

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "661",
    "commit-sha": "9445d2185cd58665d60cc6a4c175a3bf1f38b3d4"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "661",
    "commit-sha": "9445d2185cd58665d60cc6a4c175a3bf1f38b3d4"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "661",
    "commit-sha": "9445d2185cd58665d60cc6a4c175a3bf1f38b3d4"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "661",
    "commit-sha": "a96c8546865f5fac1eebc3efc05f256105a25afb"
  }
]


SearchIndex.from_dict Modifies Input Dictionary by Removing Keys

When using the from_dict method of the SearchIndex class, the input dictionary is modified, and certain keys, in this specific example "kind", are removed from the dictionary. This can cause unexpected behavior for the caller.
Reproduction Steps
Here is a minimal example to reproduce the issue:
from azure.search.documents.indexes.models import SearchIndex
azure_params = {
    "name": "my_index",
    "fields": [
        {
            "name": "HotelId",
            "type": "Edm.String",
            "key": True,
            "searchable": True,
            "filterable": False,
            "sortable": False,
            "facetable": False,
        },
        {
            "name": "HotelName",
            "type": "Edm.String",
            "key": False,
            "searchable": True,
            "filterable": False,
            "sortable": False,
            "facetable": False,
        },
        {
            "name": "HotelDescription",
            "type": "Edm.String",
            "key": False,
            "searchable": True,
            "filterable": False,
            "sortable": False,
            "facetable": False,
        },
        {
            "name": "embedding",
            "type": "Collection(Edm.Single)",
            "searchable": True,
            "filterable": False,
            "sortable": False,
            "facetable": False,
            "vector_search_dimensions": 384,
            "vector_search_profile_name": "default",
        },
    ],
    "semantic_search": {
        "default_configuration_name": "default",
        "configurations": [
            {
                "name": "default",
                "prioritized_fields": {
                    "title_field": {"field_name": "HotelName"},
                    "content_fields": [{"field_name": "HotelDescription"}],
                    "keywords_fields": [],
                },
            }
        ],
    },
    "vector_search": {
        "profiles": [{"name": "default", "algorithm_configuration_name": "hnsw"}],
        "algorithms": [
            {
                "name": "hnsw",
                "kind": "hnsw",
                "parameters": {
                    "m": 10,
                    "ef_construction": 200,
                    "ef_search": 200,
                    "metric": "cosine",
                },
            }
        ],
        "vectorizers": [],
        "compressions": [
            {
                "compression_name": "myCompression",
                "kind": "scalarQuantization",
                "rerank_with_original_vectors": True,
            }
        ],
    },
}

index = SearchIndex.from_dict(azure_params)
print(azure_params['vector_search'])

Expected Behavior
The azure_params dictionary should remain unchanged after calling SearchIndex.from_dict(azure_params), and the kind key should still be present within the algorithms and compressions elements of the vector_search dictionary.
Actual Behavior
The kind key is removed from the algorithms and compressions elements of the vector_search dictionary, as shown in the output:
{
    'profiles': [{'name': 'default', 'algorithm_configuration_name': 'hnsw'}],
    'algorithms': [{'name': 'hnsw', 'parameters': {'m': 10, 'ef_construction': 200, 'ef_search': 200, 'metric': 'cosine'}}],
    'vectorizers': [],
    'compressions': [{'compression_name': 'myCompression', 'rerank_with_original_vectors': True}]
}

Workaround
To avoid this issue, I currently use copy.deepcopy to create a deep copy of the dictionary before passing it to from_dict, like so:
index = SearchIndex.from_dict(copy.deepcopy(azure_params))

Suggested Fix
The from_dict method should avoid altering the input dictionary, ensuring that all keys remain intact after the method is called.

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hi @AndreaArmx thanks for the feedback, we will get back to you asap

Thanks, this does seem like a bug, and I opened an issue in the python codegen repo about this.

Thanks for reaching out.
As I replied in https://github.com/Azure/azure-sdk-for-python/issues/36975#issuecomment-2305910589.
Did you have a chance to try it?


Price API endpoint

/stats/price/WEM error
support regions
remove get_scada_range (#88)

Investigate stale date issue in common with 274

No longer an error on /stats/price/WEM on prod. Looks to have already been deployed.


Mac OSX dmg

I need to figure out how to package this as a proper Mac application image. I've made very little progress here. Probably going to order a Mac Mini or something soon. There is a non-zero chance I will be unable to finish this by January without one.

I have no way to see how well it works yet, but this section of Makefile gets sent to travis-ci and travis-ci ends up with a dmg file. It contains the linux shell script launcher and adds two scripts to the volume which launch the browser. Hopefully.


Please add Property Web Builder

[x] verified that the CMS I'm adding is still maintained.
[x] read CONTRIBUTING.md.
[x] did not generate README.md.

Thanks, @etewiah!


[ISSUES #850] Support AdminBrokerProcessor get_topic_config.

Which Issue(s) This PR Fixes(Closes)

Fixes #850
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥


swift-module-digester: output ABI/API diagnostics to a path instead of stdout.

This is handy for scripts on top of the digester tool.

@swift-ci please smoke test and merge


Implement correct exceptions

Right now, we just throw RuntimeExceptions when there's an error. We can and should map errors to the correct client exceptions.

This is blocking the release of Concierge. Need top-level exceptions. Example is....
DefaultCatalogInfoService used to catch (IndexRequestFailedException) now it has to catch RuntimeException which is not ideal.

can you provide a repro case?


A doubt about question No.74

Given an array C that is a bincount, how to produce an array A such that np.bincount(A) == C? (★★★)

The given answer is shown as below.
C = np.bincount([1,1,2,3,4,4,6]) A = np.repeat(np.arange(len(C)), C) print(A)
There maybe a problem with the description of question No.74,the answer given can only solve the problem of Non-strictly increasing 1-d array not for all kind of 1-d array.

Do you have an example where this fails?

Do you have an example where this fails?

Do you have an example where this fails?

problem
The example in given answer is created by direct assignment,not by common means like np.random.randint(0,10,7)
The correct example must be a Non-strictly increasing 1-d array like the answer given [1,1,2,3,4,4,6],whose the next adjacent element is larger than the previous one.

A counterexample is like [2,1,1,1,1,1,1]
`C = np.bincount([2,1,1,1,1,1,1,1])
A = np.repeat(np.arange(len(C)), C)
C= [0 7 1]
A= [1 1 1 1 1 1 1 2]
`
We can see [2,1,1,1,1,1,1,1] is not equal to [1,1,1,1,1,1,1,2],we get the wrong answer.
The key point is np.repeat() is sequential.

Possible solutions
Adding the notion of non-strictly increasing 1-d array in the title description of No.74 is the most convenient way.

Do you have an example where this fails?

problem
The example in given answer is created by direct assignment,not by common means like np.random.randint(0,10,7)
The correct example must be a Non-strictly increasing 1-d array like the answer given [1,1,2,3,4,4,6],whose the next adjacent element is larger than the previous one.

A counterexample is like [2,1,1,1,1,1,1]
`C = np.bincount([2,1,1,1,1,1,1,1])
A = np.repeat(np.arange(len(C)), C)
C= [0 7 1]
A= [1 1 1 1 1 1 1 2]
`
We can see [2,1,1,1,1,1,1,1] is not equal to [1,1,1,1,1,1,1,2],we get the wrong answer.
The key point is np.repeat() is sequential.

Possible solutions
Adding the notion of non-strictly increasing 1-d array in the title description of No.74 is the most convenient way.

Thanks for the ifnromation. We could simply add sorted in C description: "Given a sorted array C that corresponds to a bincount". Can you make a PR?

Thanks for the ifnromation. We could simply add sorted in C description: "Given a sorted array C that corresponds to a bincount". Can you make a PR?

Thanks for the ifnromation. We could simply add sorted in C description: "Given a sorted array C that corresponds to a bincount". Can you make a PR?

It`s my pleasure :)

Thanks for the ifnromation. We could simply add sorted in C description: "Given a sorted array C that corresponds to a bincount". Can you make a PR?

It`s my pleasure :)

#138

#138

Thanks, merged.

Thanks, merged.


[2.5] Permit use of Project Network Isolation with other compatible RKE network providers

Backport of https://github.com/rancher/rancher/pull/31344
#31338

Closing in favour of broader solution as discussed


feat(apps): Describe application command

Description of change
Show more detailed information for an application and its functions
Fixes https://github.com/meroxa/turbine-project/issues/43
Type of change

[x]  New feature
[ ]  Bug fix
[ ]  Refactor
[ ]  Documentation

How was this tested?

[x]  Unit Tests
[ ]  Tested in staging

Demo

Additional references

Documentation updated

open to other formats


[BUG] Unable to start the instance manager or csi-plugin due to path "/" is mounted on "/" but it is not a shared mount"

Describe the bug
The longhorn-csi-plugin and instance-manager do not start due to a shared mount issue with "/", however, I am unable to make / a shared mount as it is an initramfs.  I have made various mount shared to get to this point, i.e. /var/run and /var/lib/longhorn
To Reproduce
Steps to reproduce the behavior:
kubectl create ns harvester-system
helm install harvester harvester --namespace harvester-system --set longhorn.enabled=true,minio.persistence.storageClass=longhorn,service.harvester.type=NodePort

Expected behavior
longhorn-system should start and run
Log
E0204 10:29:45.200333   20951 remote_runtime.go:227] CreateContainer in sandbox "ee5dce0aaebd7ada299f2ce5f2848e76f8c7191595a8445f4cd3a489ab277d6e" from runtime service failed: rpc error: code = Unknown desc = failed to generate container "37cc286e27778749892d6ce3050084010088c6d8d108c0734992489ec94b6d5b" spec: failed to generate spec: path "/" is mounted on "/" but it is not a shared or slave mount
E0204 10:29:45.200492   20951 kuberuntime_manager.go:829] container &Container{Name:replica-manager,Image:longhornio/longhorn-instance-manager:v1_20201021,Command:[],Args:[longhorn-instance-manager --debug daemon --listen <IP_ADDRESS>:8500],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{cpu: {{250 -3} {<nil>} 250m DecimalSI},},},VolumeMounts:[]VolumeMount{VolumeMount{Name:host,ReadOnly:false,MountPath:/host,SubPath:,MountPropagation:*HostToContainer,SubPathExpr:,},VolumeMount{Name:longhorn-service-account-token-vsvvk,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:&Probe{Handler:Handler{Exec:&ExecAction{Command:[/usr/local/bin/grpc_health_probe -addr=:8500],},HTTPGet:nil,TCPSocket:nil,},InitialDelaySeconds:3,TimeoutSeconds:1,PeriodSeconds:5,SuccessThreshold:1,FailureThreshold:3,},ReadinessProbe:nil,Lifecycle:nil,TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:nil,Privileged:*true,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:nil,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,} start failed in pod instance-manager-r-81ca54f3_longhorn-system(056a36cc-404e-40e3-b65f-fae4182e15b7): CreateContainerError: failed to generate container "37cc286e27778749892d6ce3050084010088c6d8d108c0734992489ec94b6d5b" spec: failed to generate spec: path "/" is mounted on "/" but it is not a shared or slave mount
E0204 10:29:45.200535   20951 pod_workers.go:191] Error syncing pod 056a36cc-404e-40e3-b65f-fae4182e15b7 ("instance-manager-r-81ca54f3_longhorn-system(056a36cc-404e-40e3-b65f-fae4182e15b7)"), skipping: failed to "StartContainer" for "replica-manager" with CreateContainerError: "failed to generate container \"37cc286e27778749892d6ce3050084010088c6d8d108c0734992489ec94b6d5b\" spec: failed to generate spec: path \"/\" is mounted on \"/\" but it is not a shared or slave mount"

E0204 10:29:32.200186   20951 remote_runtime.go:227] CreateContainer in sandbox "3dd3ff8d4e07cbbf3191f2154bed95527797276f89851907b6576ad0e6c7923f" from runtime service failed: rpc error: code = Unknown desc = failed to generate container "a10a386994ebdfee991c69fbb64a7312f4617cef0772fe598c7ceea796e980a8" spec: failed to generate spec: path "/" is mounted on "/" but it is not a shared mount
E0204 10:29:32.200382   20951 kuberuntime_manager.go:829] container &Container{Name:longhorn-csi-plugin,Image:longhornio/longhorn-manager:v1.1.0-rc2,Command:[],Args:[longhorn-manager -d csi --nodeid=$(NODE_ID) --endpoint=$(CSI_ENDPOINT) --drivername=driver.longhorn.io --manager-url=http://longhorn-backend:9500/v1],WorkingDir:,Ports:[]ContainerPort{},Env:[]EnvVar{EnvVar{Name:NODE_ID,Value:,ValueFrom:&EnvVarSource{FieldRef:&ObjectFieldSelector{APIVersion:v1,FieldPath:spec.nodeName,},ResourceFieldRef:nil,ConfigMapKeyRef:nil,SecretKeyRef:nil,},},EnvVar{Name:CSI_ENDPOINT,Value:unix:///csi/csi.sock,ValueFrom:nil,},},Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},},VolumeMounts:[]VolumeMount{VolumeMount{Name:kubernetes-csi-dir,ReadOnly:false,MountPath:/var/lib/kubelet/plugins/kubernetes.io/csi,SubPath:,MountPropagation:*Bidirectional,SubPathExpr:,},VolumeMount{Name:socket-dir,ReadOnly:false,MountPath:/csi/,SubPath:,MountPropagation:nil,SubPathExpr:,},VolumeMount{Name:pods-mount-dir,ReadOnly:false,MountPath:/var/lib/kubelet/pods,SubPath:,MountPropagation:*Bidirectional,SubPathExpr:,},VolumeMount{Name:host-dev,ReadOnly:false,MountPath:/dev,SubPath:,MountPropagation:nil,SubPathExpr:,},VolumeMount{Name:host-sys,ReadOnly:false,MountPath:/sys,SubPath:,MountPropagation:nil,SubPathExpr:,},VolumeMount{Name:host,ReadOnly:false,MountPath:/rootfs,SubPath:,MountPropagation:*Bidirectional,SubPathExpr:,},VolumeMount{Name:lib-modules,ReadOnly:true,MountPath:/lib/modules,SubPath:,MountPropagation:nil,SubPathExpr:,},VolumeMount{Name:longhorn-service-account-token-vsvvk,ReadOnly:true,MountPath:/var/run/secrets/kubernetes.io/serviceaccount,SubPath:,MountPropagation:nil,SubPathExpr:,},},LivenessProbe:nil,ReadinessProbe:nil,Lifecycle:&Lifecycle{PostStart:nil,PreStop:&Handler{Exec:&ExecAction{Command:[/bin/sh -c rm -f /csi//*],},HTTPGet:nil,TCPSocket:nil,},},TerminationMessagePath:/dev/termination-log,ImagePullPolicy:IfNotPresent,SecurityContext:&SecurityContext{Capabilities:&Capabilities{Add:[SYS_ADMIN],Drop:[],},Privileged:*true,SELinuxOptions:nil,RunAsUser:nil,RunAsNonRoot:nil,ReadOnlyRootFilesystem:nil,AllowPrivilegeEscalation:*true,RunAsGroup:nil,ProcMount:nil,WindowsOptions:nil,SeccompProfile:nil,},Stdin:false,StdinOnce:false,TTY:false,EnvFrom:[]EnvFromSource{},TerminationMessagePolicy:File,VolumeDevices:[]VolumeDevice{},StartupProbe:nil,} start failed in pod longhorn-csi-plugin-r572r_longhorn-system(abd021a5-f6bb-4568-b75d-4203dc55d55e): CreateContainerError: failed to generate container "a10a386994ebdfee991c69fbb64a7312f4617cef0772fe598c7ceea796e980a8" spec: failed to generate spec: path "/" is mounted on "/" but it is not a shared mount
E0204 10:29:32.200432   20951 pod_workers.go:191] Error syncing pod abd021a5-f6bb-4568-b75d-4203dc55d55e ("longhorn-csi-plugin-r572r_longhorn-system(abd021a5-f6bb-4568-b75d-4203dc55d55e)"), skipping: failed to "StartContainer" for "longhorn-csi-plugin" with CreateContainerError: "failed to generate container \"a10a386994ebdfee991c69fbb64a7312f4617cef0772fe598c7ceea796e980a8\" spec: failed to generate spec: path \"/\" is mounted on \"/\" but it is not a shared mount"

kubectl get pod -n longhorn-system -o wide
NAME                                        READY   STATUS                 RESTARTS   AGE   IP           NODE   NOMINATED NODE   READINESS GATES
csi-snapshotter-96bfff7c9-m474p             1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
csi-attacher-5dcdcd5984-jqmlh               1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
csi-attacher-5dcdcd5984-d8kp7               1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
csi-provisioner-5c9dfb6446-vnqlb            1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
csi-resizer-54d484bf8-fltxb                 1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
longhorn-ui-5dd4454bfc-wkcq9                1/1     Running                2          65m   <IP_ADDRESS>    nc1    <none>           <none>
csi-resizer-54d484bf8-n4hm9                 1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
csi-snapshotter-96bfff7c9-6gfpx             1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
csi-snapshotter-96bfff7c9-2rxtc             1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
csi-provisioner-5c9dfb6446-496vh            1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
csi-attacher-5dcdcd5984-zsp44               1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
csi-resizer-54d484bf8-kfg69                 1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
engine-image-ei-2938e020-chmjr              1/1     Running                1          49m   <IP_ADDRESS>   nc1    <none>           <none>
csi-provisioner-5c9dfb6446-bxm4v            1/1     Running                1          48m   <IP_ADDRESS>   nc1    <none>           <none>
longhorn-manager-z7rts                      1/1     Running                7          55m   <IP_ADDRESS>   nc1    <none>           <none>
longhorn-driver-deployer-7f7668bfcc-jmb67   1/1     Running                1          65m   <IP_ADDRESS>   nc1    <none>           <none>
instance-manager-e-931a6eba                 1/1     Running                0          38m   <IP_ADDRESS>   nc1    <none>           <none>
instance-manager-r-81ca54f3                 0/1     CreateContainerError   0          38m   <IP_ADDRESS>   nc1    <none>           <none>
longhorn-csi-plugin-r572r                   1/2     CreateContainerError   1          48m   <IP_ADDRESS>   nc1    <none>           <none>

You can also attach a Support Bundle here. You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment:

Longhorn version: v1.1.0
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3s v1.20.0+k3s2

Number of management node in the cluster: 1
Number of worker node in the cluster: 1

Node config

OS type and version: Fedora 30 (customized kernel and trimmed OS)
CPU per node: 8
Memory per node:32Gb
Disk type(e.g. SSD/NVMe):SSD
Network bandwidth between the nodes: 1Gb

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): Baremetal
Number of Longhorn volumes in the cluster: 1

Additional context
Add any other context about the problem here.

Since replica instance manager pods need to access the mount points of all disks on a node, host directory / must be mounted to the pods. It's a hard requirement based on the current architecture.
I am not sure if mount options of initramfs are configurable. Since you said I am unable to make / a shared mount as it is an initramfs, do you mean mount --make-rshared doesn't work?

Yes I can mount / as --make-rshared, however, once I do this some process seems to be unmounting /proc because the /proc path becomes empty.  To continue, I tried mounting proc using mount -t proc proc /proc but then mtab no longer can find the mount points:
mtab -> ../proc/self/mounts
[root@nc1 etc]# ll ../proc/self
ls: cannot read symbolic link '../proc/self': No such file or directory
lrwxrwxrwx 1 root root 0 Feb  5 05:38 ../proc/self

So I tried bypassing that by directly linking mtab to /proc/self/mounts to at least link the mounts file, but that produces another error message
E0205 05:41:29.965292    6484 remote_runtime.go:116] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed to create containerd task: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:117: jailing process inside rootfs caused: invalid argument: unknown

If the code is trying to do a pivot_root, that's not going to work on an initramfs.  So that might be doa for this. Appreciate the support!

@shuo-wu, is it correct that it is performing a pivot_root, I see the function in the instance manager code, so the assumption is yes. No option to use native/nopivotroot?
Thanks again for investigating.

Yes. That's required. Right now I have not found a possible workaround.

We currently don't have a workaround for this, we want to have another look at this issue when we are closer to the 1.2 release.


Up kevincox's limit.

I didn't realize that this counted all GitHub activity. I was way over the previous values but understanding how it works makes me comfortable to commit more 🙂

Great! Do not hesitate to lower the limit again if it ends up being too much -- I don't want this bot to become an annoyance, as that negative feeling would then just trickle down to PR authors.
As mentioned here I think the rate-limiting approach doesn't work very well. It might be nice in theory, but its very hard to work with. I plan to change this, but it might take a long time since I don't have very much time to work on marvin.

I took the liberty to change the commit message in a squash&merge. Will deploy shortly.

FYI:

Nov 03 17:01:02 marvin-mk2: Selecting reviewer from candidates: ['turion', 'symphorien', 'timokau', 'fgaz', 'glittershark', 'kevincox']
Nov 03 17:01:02 marvin-mk2: Testing fgaz
Nov 03 17:01:06 marvin-mk2: Limit (2/7d) exceeded until 2020-11-08 16:38:11+00:00.
Nov 03 17:01:06 marvin-mk2: Testing timokau
Nov 03 17:01:09 marvin-mk2: Limit (1/1d) exceeded until 2020-11-04 16:43:12+00:00.
Nov 03 17:01:09 marvin-mk2: Testing glittershark
Nov 03 17:01:12 marvin-mk2: Limit (2/7d) exceeded until 2020-11-07 18:27:53+00:00.
Nov 03 17:01:12 marvin-mk2: Testing symphorien
Nov 03 17:01:16 marvin-mk2: Limit (3/7d) exceeded until 2020-11-08 21:14:02+00:00.
Nov 03 17:01:16 marvin-mk2: Testing kevincox
Nov 03 17:01:19 marvin-mk2: Limit (7/7d) exceeded until 2020-11-08 20:07:28+00:00.
Nov 03 17:01:19 marvin-mk2: Testing turion
Nov 03 17:01:23 marvin-mk2: Limit (3/7d) exceeded until 2020-11-10 13:59:15+00:00.
Nov 03 17:01:23 marvin-mk2: No reviewer found for #95751.

(The given dates show for how long marvin caches the "rate limit reached" result).


The examples aren't self-contained

I tried copying over the code from the antd Form List, added the necessary dependencies and ran into this issue:
config.tsx:62 Uncaught Error: Widget 'form-list' not defined. Did you define it?
    at Object.getWidgetDef (config.tsx:62:15)
    at NiceForm.tsx:65:26
    at Array.map (<anonymous>)
    at NiceForm (NiceForm.tsx:24:25)
    at renderWithHooks (react-dom.development.js:16305:18)
    at mountIndeterminateComponent (react-dom.development.js:20074:13)
    at beginWork (react-dom.development.js:21587:16)
    at HTMLUnknownElement.callCallback2 (react-dom.development.js:4164:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:4213:16)
    at invokeGuardedCallback (react-dom.development.js:4277:31)

By copying this over from packages/examples-antd/src into the example code, it does work:
import { config as niceFormConfig } from '@ebay/nice-form-react';
import antdAdapter from '@ebay/nice-form-react/adapters/antdAdapter';

niceFormConfig.addAdapter(antdAdapter);

Because antdAdapter defines the form-list widget.
This is most likely the same for the formik form-list, but might happen in even more files.
To make it easier for developers to play around with nice-form-react, it'd be better if the example code is self-contained.

I'll see if I can come up with a solution for this.
Due to all examples being imported non lazily from App.tsx, it would seem like example B that is missing the adapter works after example A has been opened, due to the import of example A already having added the adapter. That way it isn't easy to spot where the adapter needs to be added and where it is unnecessary. I'll try and refactor it so App.tsx lazily imports the examples.


Rust 1.74: move lints to Cargo.toml

Stack:

#1163
#1162 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5037f35) 67.27% compared to head (2559ef0) 67.27%.

:exclamation: Current head 2559ef0 differs from pull request most recent head 2b352bb. Consider uploading reports for the commit 2b352bb to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1162   +/-   ##
=======================================
  Coverage   67.27%   67.27%
=======================================
  Files          52       52
  Lines        6742     6742
  Branches     6742     6742
=======================================
  Hits         4536     4536
  Misses       1791     1791
  Partials      415      415

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


numpy.array(...) LoweringError

LoweringError:
Failed at object (object mode backend)
make_function(name=$const48.11, code=<code object  at 0x10cb9ab70, file "/Users/victor/Documents/PyDojo/dojo/linear/LinearRegression.py", line 26>, closure=None, defaults=None)
File "dojo/linear/LinearRegression.py", line 26:
    def fit(self, X, y):
        <source elided>
        X = np.hstack((
            np.array([[1] for _ in range(m)]),
            ^

This should not have happened, a problem has occurred in Numba's internals.
This is the whole method I am calling:
    @jit
    def fit(self, X, y):
        if type(X) is not np.ndarray:
            X = np.array(X)

        if type(y) is not np.ndarray:
            y = np.array(y)

        m, _ = X.shape
        X = np.hstack((
            np.array([[1] for _ in range(m)]),
            X
        ))

        res = linalg.inv(X.T @ X) @ X.T @ y
        self.set_params(intercept=res[0], coefs=res[1:])
        return self

Use np.ones((m, 1)) instead of np.array([[1] for _ in range(m)]). That ought to work.
This is fundamentally an issue with the fact that you're passing a list of lists. Tuple of lists or the fix above will work. :)

Thanks for the report. Adjusting this as a stand alone example:
from numba import jit, njit
from numpy import linalg
import numpy as np

@jit
def fit(X, y):
    if type(X) is not np.ndarray:
        X = np.array(X)

    if type(y) is not np.ndarray:
        y = np.array(y)

    m, _ = X.shape
    X = np.hstack((
        np.array([[1] for _ in range(m)]),
        X
    ))

    res = linalg.inv(X.T @ X) @ X.T @ y
    intercept=res[0]
    coefs=res[1:]
    return intercept, coefs

fit(np.arange(10).reshape(1,10), np.arange(10).reshape(1,10))

gives:
    assert name in self._live_vars, name
AssertionError: array.22

<more traceback stuff>

numba.errors.LoweringError: Failed in object mode pipeline (step: object mode backend)
array.22

File "issue3239.py", line 15:
def fit(X, y):
    <source elided>
    X = np.hstack((
        np.array([[1] for _ in range(m)]),
        ^
[1] During: lowering "$48.18 = array.22" at issue3239.py (15)

on current master.
If forceobj is set it gives this:
Traceback (most recent call last):
  File "issue3239.py", line 24, in <module>
    fit(np.arange(10).reshape(1,10), np.arange(10).reshape(1,10))
NameError: global name 'unsafe_empty_inferred' is not defined

Ping @sklam

Getting to a simpler reproducer:
from numba import jit, njit
import numpy as np

@jit
def fit(X):
    return np.array([[1] for _ in range(2)])

fit(np.arange(10))

Note that the following works:
@jit
def fit(X):
    return np.array([1 for _ in range(2)])

The difference being that it's producing a flat list instead of a list-of-list.


Bug: 'devspace enter' & 'devspace dev' command exit code is lost

What happened?
When running devspace dev or devspace enter with a command, the exit code of the command is not reflected by devspace
What did you expect to happen instead?
If devspace is able to execute the command, I would expect it to exit with the same exit code as the command.
How can we reproduce the bug? (as minimally and precisely as possible)
> devspace dev -- bash -c 'exit 1'
> echo $? # 0

Local Environment:

Operating System: mac
Deployment method: helm

Kubernetes Cluster:

Cloud Provider: minikube
Kubernetes Version: [use kubectl version]

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-19T22:12:47Z", GoVersion:"go1.12.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.9", GitCommit:"e09f5c40b55c91f681a46ee17f9bc447eeacee57", GitTreeState:"clean", BuildDate:"2019-05-27T15:58:45Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}

Anything else we need to know?

/kind bug

Fixed in v3.5.13


/dev/shm support is broken (Was: What options does the --tmpfs flag in the run statement allow)

I'm trying to a run an Oracle  Database in a Docker image in a lima environment on macOS and get a lot of errors related to the shm volume.
lima nerdctl run --detach --name="oracledb" --network="oraclenet" --memory="4g" --publish="1521:1521" --volume="/dev/shm" --tmpfs="/dev/shm:rw,exec,size=1g" qualiant/database

As there is no specific documentation, I wanted to ask a few specific questions:

Does nerdctl all the options --tmpfs="/dev/shm:rw,exec,size=1g" in the --tmpfs flag ?
nerdctl support the --memory option but how does this relate to lima? Is it guaranteed that the container gets 4g when using the --memory flag independently from lima?

Thank you!

After some more testing , it seems as if at least the exec would option not be observed when using
--tmpfs="/dev/shm:rw,exec,size=1g"

All the tmpfs options are supported, however, there seems to be a bug specific to /dev/shm path, as nerdctl mounts its own /dev/shm

$ nerdctl run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts
shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k,uid=1001,gid=1001,inode64 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,uid=1001,gid=1001,inode64 0 0

$ docker run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,inode64 0 0

(nerdctl v0.14.0)

Unrelated. Lima memory is an amount of QEMU memory (which looks like the physical memory to the Linux guest), and nerdctl memory is just cgroup memory limits.

@AkihiroSuda Thank you for your very helpful feedback. Do you expect this problem to be fixed in the near future?

@AkihiroSuda I would be most appreciated, if you could give some update on this bug.

@doberkofler I tried to fix this, but I don't have an oracle/database image to verify that works :(

@doberkofler I tried to fix this, but I don't have an oracle/database image to verify that works :(

I can test it when a version becomes available.

@AkihiroSuda Will the fix in nerdctl be available in the next release of lima?

Yes, in a few days, but upgrading Lima does not automatically upgrade nerdctl in existing Lima instances, so you will have to either recreate the Lima instance, or just overwrite /usr/local/bin/nerdctl in the existing instance with the newer version of nerdctl binary.

@doberkofler An easy way to help you build from source:
make nerdctl && sudo make install

@Junnplus I've just downloaded the latest version of lima (0.8.2) and upgraded nerdctl (0.16.1) and run my tests again but unfortunately the Installation of natively compiled code in an Oracle Database still fails in a lima/nerdctl container.
I'm starting my Oracle container using:
lima nerdctl run --detach --name="oracledb" --memory="4g" --publish="31521:1521" --volume="/dev/shm" --tmpfs="/dev/shm:rw,exec,size=1g" oracle/database-prebuild:19.3.0-se2

and get an error:
ORA-00600: internal error code, arguments: [pesldl02_Make_Object: shm_open failed: errno 13 errmsg Permissio], [/PESLD_ORCLCDB_3_f0d63c6400000000], [], [], [], [], [], [], [], [], [], []

that according to the Oracle Tech Support is related to an error in tmpfs device, but when checking the new version independently from Oracle it seems as if the problem has been resolved:
/ $ lima nerdctl run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,uid=501,gid=1000,inode64 0 0
/ $ docker run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k 0 0

When running the exact same container on Docker everything works as expected.
Maybe there is some other problem. Any help would be greatly appreciated.

looks like it is related to lima;  lima add uid=501,gid=1000 to the mount so you are not mouting /dev/shm as user 0 and you need be user `0 to open shm
nerdctl run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k 0 0

lima nerdctl run --rm --tmpfs="/dev/shm:rw,exec,size=1g,uid=1,gid=1" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,uid=100000,gid=100000,inode64 0 0

I assume that lima using vm user to make this mount which is logic, but When I tried to force user 0 , it dosen't wort
lima nerdctl run --rm --tmpfs="/dev/shm:rw,exec,size=1g,uid=0,gid=0" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,uid=501,gid=1000,inode64 0 0

WDYT @AkihiroSuda  @Junnplus  ?

@AkihiroSuda @Junnplus Can this issue be reopened this problem or should I open a new one?

@doberkofler Your docker should be in rootful mode, correspondingly you should try the rootful mode of nerdctl.
$ sudo docker run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,inode64 0 0
$ docker run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,uid=501,gid=1000,inode64 0 0
$ sudo nerdctl run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,inode64 0 0
$ nerdctl run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,uid=501,gid=1000,inode64 0 0

Set containerd.systemd to true to enable rootful containerd.
https://github.com/lima-vm/lima/blob/v0.8.2/pkg/limayaml/default.yaml#L89

@Junnplus Thank you for he feedback, but I'm not sure I understand.
I have tried just changing the containerd.system option in the default.yaml file but it did not make a difference when trying to run the Oracle Database.
Could you elaborate on what the problem might be or what I'm doing wrong?
When trying to run sudo lima nerdctl run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts the error FATA[0000] must not run as the root is shown.
Running lima nerdctl run --rm --tmpfs="/dev/shm:rw,exec,size=1g" alpine grep /dev/shm /proc/mounts shows tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime,size=1048576k,uid=501,gid=1000,inode64 0 0.

@doberkofler Try the following steps:

Set containerd.system to true.
And restart lima instance: limactl stop && limactl start.
Using lima sudo nerdctl run ... to instead of lima nerdctl run ....

@Junnplus Thank you for all your help and sorry for being of so little help!

I've changed default.yaml used limactl start and stop.

containerd:
  # Enable system-wide (aka rootful)  containerd and its dependencies (BuildKit, Stargz Snapshotter)
  # Default: false
  system: true
  # Enable user-scoped (aka rootless) containerd and its dependencies
  # Default: true
  user: null

Is there way to check if the "rootful" mode is activated?
I actually also had to import the oracle/database-prebuild:19.3.0-se2 image again after changing the setting. Is this normal?

This is how I start the Oracle database in the container

lima sudo nerdctl run --detach --name="oracledb" --memory="4g" --publish="31521:1521" --volume="/dev/shm" --tmpfs="/dev/shm:rw,exec,size=1g" oracle/database-prebuild:19.3.0-se2

Unfortunately I still get the same error message when trying to compile to native in the Oracle Database

* ORA-00600: internal error code, arguments: [pesldl02_Make_Object: shm_open failed: errno 13 errmsg Permissio], [/PESLD_ORCLCDB_3_6030696600000000], [], [], [], [], [], [], [], [], [], []

Is there way to check if the "rootful" mode is activated?
Run lima sudo nerdctl info successfully.

I actually also had to import the oracle/database-prebuild:19.3.0-se2 image again after changing the setting. Is this normal?
Yes.

I using oracle docker image and  tried to reproduce this error but it works.

@Junnplus The error only appears when Oracle uses the tmpfs device to (for example) compile natively.


Use an IBufferWriter when decompressing a JWT

Instead of creating a Sequence then copying to an array, use a IBufferWriter

Fixed in #509


Notebook Extension Test Update

This is a work in progress, this should update all of our tests to actually test the notebook-extension.
Currently working tests:

Dfcells package:    ${\color{Green}\textsf{ALL Pass}}$
Dfnotebook package: ${\color{Green}\textsf{ALL Pass}}$
Dfgraph package: WIP
Dfoutputarea: ${\color{Green}\textsf{ALL Pass}}$

Seeing an error. Ran jlpm install followed by jlpm build:test
❯ jlpm build:test
(node:13622) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
lerna notice cli v8.1.3
lerna info versioning independent

   ✔  @dfnotebook/dfgraph:build:test (3s)
   ✔  @dfnotebook/dfoutputarea:build:test (4s)

———————————————————————————————————————————————————————————————————————————————
   ✖  @dfnotebook/dfcells:build:test
      src/widget.ts(351,22): error TS2339: Property 'createGraph' does not exist on type 'GraphManager'.
      test/widget.spec.ts(31,29): error TS2307: Cannot find module '@dfnotebook/dfcells/lib/testutils' or its corresponding type declarations.

Needed to do a jlpm:build before building the tests since testutils.ts is in the dfnotebook package.


updating face detecting in pictures with class and functions

Adding face detected with img. class and function
contributing a little of what I know, for hacktoberfest, I hope I have been helpful with my contribution

@Efr41nT2 Thanks for the contribution
Hacktober will start in the month of October, If you will make pull-request in September it will count.
Please Make your PR on 1st October.

Make sure to create an issue and be assigned before making PR. So we will know what you are planning to change.
please create an issue and create your PR again on 1st October.
best of luck for hacktober.
@Efr41nT2


IOError: [Errno 2] No such file or directory: './light_weight_refinenet/resnet50.pth.tar'

Hi
I have tried to run the code using this command

python main.py

I got this error
IOError: [Errno 2] No such file or directory: './light_weight_refinenet/resnet50.pth.tar'
I have check the path I did not get the resnet50.pth.tar
may you help  to fix this issue

Did you try to download the weight files by running downloads.sh?