Failed to authenticate to GUI server and errors in operator log

Describe the bug
Failed to authenticate to GUI server and errors in operator log
How to Reproduce?

try to manual curl the url and success:

# curl --insecure -u 'user:password' -X GET https://<IP_ADDRESS>:30443/scalemgmt/v2/cluster
{
  "cluster" : {
    "clusterSummary" : {
      "clusterId" :<PHONE_NUMBER>846563007,
      "clusterName" : "master1.cluster.local",
      "primaryServer" : "master1.cluster.local",
      "rcpPath" : "/usr/bin/scp",
      "rcpSudoWrapper" : false,
      "repositoryType" : "CCR",
      "rshPath" : "/usr/bin/ssh",
      "rshSudoWrapper" : false,
      "uidDomain" : "master1.cluster.local"
    }
  },
  "status" : {
    "code" : 200,
    "message" : "The request finished successfully."
  }

Checked the secret by decode with base64 it's ok. checked the yaml and had set ssl to false.
In the operator log it always authentication fail

2023-10-08T08:17:30.113Z	INFO	csiscaleoperator_controller.checkPrerequisite	Secret resource gpfs101sceret found.
2023-10-08T08:17:30.113Z	INFO	csiscaleoperator_controller.Reconcile	Pre-requisite check passed.
2023-10-08T08:17:30.113Z	INFO	csiscaleoperator_controller.ValidateCRParams	Validating the Spectrum Scale CSI configurations of the resource CSIScaleOperator/ibm-spectrum-scale-csi
2023-10-08T08:17:30.113Z	INFO	csiscaleoperator_controller.Reconcile	The Spectrum Scale CSI configurations are validated successfully
2023-10-08T08:17:30.113Z	INFO	csiscaleoperator_controller.handleSpectrumScaleConnectors	Checking spectrum scale connectors
2023-10-08T08:17:30.113Z	INFO	csiscaleoperator_controller.newSpectrumScaleConnector	Creating new SpectrumScaleConnector for cluster with	{"ID": "1052530068846563007"}
2023-10-08T08:17:30.113Z	INFO	csiscaleoperator_controller.newSpectrumScaleConnector	Created Spectrum Scale connector without SSL mode for guiHost(s)
E1008 08:18:30.113987       1 rest_v2.go:1024] [] rest_v2 doHTTP: Error in authentication request on endpoint https://<IP_ADDRESS>:30443/: Get "https://<IP_ADDRESS>:30443/scalemgmt/v2/cluster": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
E1008 08:18:30.114047       1 rest_v2.go:193] [] Unable to get cluster ID: Get "https://<IP_ADDRESS>:30443/scalemgmt/v2/cluster": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2023-10-08T08:18:30.114Z	ERROR	csiscaleoperator_controller.handleSpectrumScaleConnectors	Failed to connect to the GUI of the cluster with ID:<PHONE_NUMBER>846563007	{"error": "Get \"https://<IP_ADDRESS>:30443/scalemgmt/v2/cluster\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}
github.com/IBM/ibm-spectrum-scale-csi/operator/controllers.(*CSIScaleOperatorReconciler).Reconcile
	/workspace/controllers/csiscaleoperator_controller.go:296
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:114
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:311
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:227
2023-10-08T08:18:30.114Z	ERROR	csiscaleoperator_controller.Reconcile	Error in getting connectors	{"error": "Get \"https://<IP_ADDRESS>:30443/scalemgmt/v2/cluster\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:114
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:311
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:227
2023-10-08T08:18:30.114Z	INFO	csiscaleoperator_controller.SetStatus	Assigning values to status sub-resource object.
2023-10-08T08:18:30.114Z	DEBUG	csiscaleoperator_controller.SetStatus	Setting status of CSIScaleOperator is successful
2023-10-08T08:18:30.114Z	DEBUG	events	Warning	{"object": {"kind":"CSIScaleOperator","namespace":"ibm-spectrum-scale-csi-driver","name":"ibm-spectrum-scale-csi","uid":"3d2cf54e-2113-428c-a048-8a34944b99bb","apiVersion":"csi.ibm.com/v1","resourceVersion":"14348088"}, "reason": "GUIConnFailed", "message": "Failed to connect to the GUI of the cluster with ID:<PHONE_NUMBER>846563007"}
2023-10-08T08:18:30.131Z	DEBUG	csiscaleoperator_controller.Reconcile	Updated resource status.	{"Status": {"versions":[{"name":"ibm-spectrum-scale-csi","version":"2.9.0"}],"conditions":[{"type":"Success","status":"False","lastTransitionTime":"2023-10-08T08:18:30Z","reason":"GUIConnFailed","message":"Failed to connect to the GUI of the cluster with ID:<PHONE_NUMBER>846563007"}]}}
2023-10-08T08:18:30.131Z	ERROR	controller.csiscaleoperator	Reconciler error	{"reconciler group": "csi.ibm.com", "reconciler kind": "CSIScaleOperator", "name": "ibm-spectrum-scale-csi", "namespace": "ibm-spectrum-scale-csi-driver", "error": "Get \"https://<IP_ADDRESS>:30443/scalemgmt/v2/cluster\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.1/pkg/internal/controller/controller.go:227

Expected behavior
A clear and concise description of what you expected to happen.
Data Collection and Debugging
Environmental output

What openshift/kubernetes version are you running, and the architecture?
kubectl get pods -o wide -n < csi driver namespace>
kubectl get nodes -o wide
IBM Storage Scale container native version
IBM Storage Scale version
Output for ./tools/spectrum-scale-driver-snap.sh -n < csi driver namespace> -v

Tool to collect the CSI snap:
./tools/spectrum-scale-driver-snap.sh -n < csi driver namespace>
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Add labels

Component:CSI
Severity:1
Customer Impact:high
Customer Probability:
Phase:deploy

Note : See labels for the labels

Hi @superleo , The most likely issue is gui host is not reachable from pod. Please do check the pod to guihost network communication if that is working.

Hi @superleo , The most likely issue is gui host is not reachable from pod. Please do check the pod to guihost network communication if that is working.

Thank you @deeghuge , I tried to ping the pod ip and the network from host to operator pod is ok. And from the log file I can see it's "authentication problem", not network problem.

I created a dnsutil pod in the namspace and could ping host GUI server IP as well
root@master1:/home/mccxadmin# kubectl get pods -n ibm-spectrum-scale-csi-driver
NAME                                              READY   STATUS    RESTARTS   AGE
dnsutils                                          1/1     Running   0          11s
ibm-spectrum-scale-csi-operator-bddd6d8f7-wjhp7   1/1     Running   0          27h
root@master1:/home/mccxadmin# kubectl exec -i -t dnsutils -n ibm-spectrum-scale-csi-driver -- ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.167 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.090 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.097 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=64 time=0.088 ms
c64 bytes from <IP_ADDRESS>: icmp_seq=5 ttl=64 time=0.095 ms
64 bytes from <IP_ADDRESS>: icmp_seq=6 ttl=64 time=0.315 ms

I notice the host is listen on 47443 port. After modify the guiport in csi driver yaml file to 47443 and it's ok now.  But don't know why, I cannot find any configuration related with 47443 port.

@superleo good to see that things are working for you. The question -  I cannot find any configuration related with 47443 port  by this do you mean that there is no documentation available on how and where to change the port or something else ?


cannot add homebridge to my home app after upgrade

Pre Steps

after upgrade of my homebridge installation I cannot add again into home app
Expected Behavior
I tried to remove persist and accessories folder but without success, I removed also the old bridge from home app but nothing. I changed the user and pin on the config but nothing :(
Versions

Homebridge: homebridge --version 4.5.0
Node:       node --version v10.16.3 npm":"6.12.0"
OS:         docker-compose image oznu/homebridge

Configuration

{
    "bridge": {
        "name": "HomeBridge",
        "username": "CA:22:3D:E3:CE:50",
        "port": 51826,
        "pin": "031-45-154"
    },
    "description": "",
    "accessories": [
        {
            "accessory": "webostv",
            "name": "TV Sala",
            "ip": "<IP_ADDRESS>",
            "mac": "38:8C:50:28:A6:4E",
            "keyFile": "/homebridge/lgtvKeyFile",
            "pollingInterval": 10,
            "inputs": [
                {
                    "appId": "com.webos.app.livetv",
                    "name": "Live TV"
                },
                {
                    "appId": "netflix",
                    "name": "Netflix"
                },
                {
                    "appId": "amazon",
                    "name": "Amazon Prime Video"
                },
                {
                    "appId": "com.webos.app.hdmi2",
                    "name": "Apple TV"
                },
                {
                    "appId": "com.webos.app.hdmi3",
                    "name": "Nintendo Switch"
                },
                {
                    "appId": "com.webos.app.hdmi4",
                    "name": "FireStick"
                },
                {
                    "appId": "youtube.leanback.v4",
                    "name": "youTube"
                },
                {
                    "appId": "com.ssiptv.app",
                    "name": "SS IPTV"
                },
                {
                    "appId": "com.webos.app.hdmi1",
                    "name": "PS4"
                }
            ],
            "showInputButtons": true,
            "volumeControl": "slider",
            "channelControl": true,
            "notificationButtons": [],
            "remoteControlButtons": [],
            "mediaControl": false
        },
        {
            "accessory": "Meross",
            "name": "Presa TV Sala",
            "deviceUrl": "http://<IP_ADDRESS>",
            "authToken": "Basic hhh",
            "channel": "1"
        },
        {
            "accessory": "Meross",
            "name": "Presa SoundBar",
            "deviceUrl": "http://<IP_ADDRESS>",
            "authToken": "Basic hhh",
            "channel": "2"
        },
        {
            "accessory": "Meross",
            "name": "Presa Apple TV",
            "deviceUrl": "http://<IP_ADDRESS>",
            "authToken": "Basic hhhh",
            "channel": "3"
        },
        {
            "accessory": "Meross",
            "name": "Presa FireStick Sala",
            "deviceUrl": "http://<IP_ADDRESS>",
            "authToken": "Basic hhhh",
            "channel": "4"
        },
        {
            "accessory": "SamsungTV",
            "name": "TV Camera",
            "ip_address": "<IP_ADDRESS>",
            "send_delay": 400
        },
        {
            "accessory": "DummySwitch",
            "name": "Finestra Bagno Timer",
            "time": 1800000
        },
        {
            "accessory": "DummySwitch",
            "name": "Finestra Camera Timer",
            "time": 1800000
        },
        {
            "accessory": "DummySwitch",
            "name": "Finestra Cameretta Timer",
            "time": 1800000
        },
        {
            "accessory": "DummySwitch",
            "name": "Finestra Sala Timer",
            "time": 1800000
        },
        {
            "accessory": "DummySwitch",
            "name": "Finestra Cucina Timer",
            "time": 1800000
        },
        {
            "accessory": "Samsung Air Conditioner",
            "name": "Climatizzatore Camera",
            "ip_address": "<IP_ADDRESS>",
            "mac": "bbbb",
            "token": "hhhh"
        },
        {
            "accessory": "Samsung Air Conditioner",
            "name": "Climatizzatore Cameretta",
            "ip_address": "<IP_ADDRESS>",
            "mac": "7bbbb",
            "token": "hhhhh"
        }
    ],
    "platforms": [
        {
            "name": "Config",
            "port": 4000,
            "auth": "form",
            "theme": "grey",
            "tempUnits": "c",
            "log": {
                "method": "custom",
                "command": "docker-compose logs -f | grep homebridge"
            },
            "ssl": {
                "key": "/ssl/privkey.pem",
                "cert": "/ssl/fullchain.pem"
            },
            "platform": "config"
        },
        {
            "platform": "MagicHome-Platform",
            "debug": true,
            "lights": [
                {
                    "name": "Letto LED Strip",
                    "ip": "<IP_ADDRESS>",
                    "setup": "RGB",
                    "purewhite": false,
                    "timeout": 10000
                }
            ]
        },
        {
            "platform": "eWeLink",
            "name": "eWeLink",
            "email": "hhhh",
            "password": "hhhh",
            "imei": "hhhh"
        },
        {
            "platform": "Shelly",
            "name": "Shelly",
            "admin": {
                "enabled": false,
                "port": 6000
            },
            "devices": []
        },
        {
            "platform": "TadoPlatform",
            "username": "hhh",
            "password": "hhh",
            "homeID": hhhh,
            "unit": "celsius",
            "polling": 10,
            "exclude": [
                "bbb-1",
                "bbb-2",
                "bbb-3",
                "bbb-4",
                "bbb-5"
            ],
            "reConfig": false,
            "occupancy": true,
            "anyone": true,
            "weather": true,
            "openWindow": true,
            "solarIntensity": true,
            "centralSwitch": true,
            "externalSensor": true,
            "deviceOptions": {
                "bbb-1": {
                    "active": false,
                    "heatValue": 5,
                    "coolValue": 5,
                    "maxDelay": 10,
                    "overrideMode": "manual",
                    "ID": 1,
                    "zoneName": "Bagno",
                    "zoneType": "HEATING",
                    "deviceType": "VA",
                    "serial": "bbb",
                    "type": "thermostat"
                },
                "bbb-2": {
                    "active": false,
                    "heatValue": 5,
                    "coolValue": 5,
                    "maxDelay": 10,
                    "overrideMode": "manual",
                    "ID": 2,
                    "zoneName": "Camera Matrimoniale",
                    "zoneType": "HEATING",
                    "deviceType": "VA",
                    "serial": "bbb",
                    "type": "thermostat"
                },
                "bbb-3": {
                    "active": false,
                    "heatValue": 5,
                    "coolValue": 5,
                    "maxDelay": 10,
                    "overrideMode": "manual",
                    "ID": 3,
                    "zoneName": "Cucina",
                    "zoneType": "HEATING",
                    "deviceType": "VA",
                    "serial": "bbb",
                    "type": "thermostat"
                },
                "bbb-4": {
                    "active": false,
                    "heatValue": 5,
                    "coolValue": 5,
                    "maxDelay": 10,
                    "overrideMode": "manual",
                    "ID": 4,
                    "zoneName": "Sala",
                    "zoneType": "HEATING",
                    "deviceType": "VA",
                    "serial": "bbb",
                    "type": "thermostat"
                },
                "bbb-5": {
                    "active": false,
                    "heatValue": 5,
                    "coolValue": 5,
                    "maxDelay": 10,
                    "overrideMode": "manual",
                    "ID": 5,
                    "zoneName": "Cameretta",
                    "zoneType": "HEATING",
                    "deviceType": "VA",
                    "serial": "bbb",
                    "type": "thermostat"
                }
            }
        },
        {
            "platform": "WeatherPlus",
            "name": "WeatherPlus",
            "service": "darksky",
            "key": "bbb",
            "locationGeo": [
                99.54553029,
                99.22624111
            ]
        },
        {
            "platform": "BroadlinkRM",
            "name": "Broadlink RM",
            "hideScanFrequencyButton": false,
            "hideLearnButton": false,
            "hideWelcomeMessage": true,
            "accessories": [
                {
                    "name": "Soundbar on/off",
                    "type": "switch",
                    "data": {
                        "on": [
                            {
                                "data": "bbb)"
                            }
                        ],
                        "off": [
                            {
                                "data": "bbb)"
                            }
                        ]
                    }
                },
                {
                    "name": "Soundbar Clear Voice",
                    "type": "switch",
                    "enableAutoOff": true,
                    "onDuration": 2,
                    "data": [
                        {
                            "data": "bbb)"
                        }
                    ]
                },
                {
                    "name": "Soundbar Bass Extended",
                    "type": "switch",
                    "enableAutoOff": true,
                    "onDuration": 2,
                    "data": [
                        {
                            "data": "bbb)"
                        }
                    ]
                }
            ]
        },
        {
            "name": "Alexa",
            "username": "bbb",
            "password": "bbb;bbb>x",
            "pin": "031-45-154",
            "routines": true,
            "refresh": 5,
            "platform": "Alexa"
        }
    ],
    "id": "config"
}

Homebridge Log / Command Output

homebridge    | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
homebridge    | [s6-init] ensuring user provided files have correct perms...exited 0.
homebridge    | [fix-attrs.d] applying ownership & permissions fixes...
homebridge    | [fix-attrs.d] done.
homebridge    | [cont-init.d] executing container initialization scripts...
homebridge    | [cont-init.d] 10-adduser: executing...
homebridge    |
homebridge    | -------------------------------------
homebridge    | GID/UID
homebridge    | -------------------------------------
homebridge    | User uid:    1000
homebridge    | User gid:    1000
homebridge    | -------------------------------------
homebridge    |
homebridge    | [cont-init.d] 10-adduser: exited 0.
homebridge    | [cont-init.d] 20-set-timezone: executing...
homebridge    | [cont-init.d] 20-set-timezone: exited 0.
homebridge    | [cont-init.d] 30-packages: executing...
homebridge    | [cont-init.d] 30-packages: exited 0.
homebridge    | [cont-init.d] 40-dbus-avahi: executing...
homebridge    | [cont-init.d] 40-dbus-avahi: exited 0.
homebridge    | [cont-init.d] 45-user-data: executing...
homebridge    | +<EMAIL_ADDRESS>homebridge    | added 39 packages from 47 contributors in 53.622s
homebridge    | npm WARN deprecated<EMAIL_ADDRESS>Please note that v5.0.1+ of superagent removes User-Agent header by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header).  This notice will go away with v5.0.2+ once it is released.
homebridge    | /usr/local/bin/homebridge-shelly -> /usr/local/lib/node_modules/homebridge-shelly/bin/homebridge-shelly
homebridge    | +<EMAIL_ADDRESS>homebridge    | added 90 packages from 58 contributors in 13.538s
homebridge    | npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
homebridge    | npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/wreck. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
homebridge    | npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
homebridge    | npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
homebridge    | npm WARN deprecated<EMAIL_ADDRESS>This module has moved and is now available at @hapi/bourne. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
homebridge    | npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"^10.15.3","homebridge":"^0.4.46"} (current: {"node":"12.13.0","npm":"6.12.0"})
homebridge    | npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>homebridge    |
homebridge    | +<EMAIL_ADDRESS>homebridge    | added 63 packages from 58 contributors in 33.258s
homebridge    | +<EMAIL_ADDRESS>homebridge    | added 56 packages from 79 contributors in 9.272s
homebridge    | +<EMAIL_ADDRESS>homebridge    | added 160 packages from 134 contributors in 43.486s
homebridge    | +<EMAIL_ADDRESS>homebridge    | added 55 packages from 67 contributors in 7.763s
homebridge    | +<EMAIL_ADDRESS>homebridge    | added 38 packages from 54 contributors in 9.582s

I disabled also ipv6 with this
sed -i '/^use-ipv6=/s/=.*/=no/' /etc/avahi/avahi-daemon.conf
I check the port 5353 and is already busy when the rpm go up from avahi deamon, I kill it before start homebridge but without any success.
I check it also with bonjour browser but i cannot see homebridge under hap interfaces. but if I exec the following command
sudo netstat -tulpn | grep :5353
the result is:
udp        0      0 <IP_ADDRESS>:5353            <IP_ADDRESS>:*                           21937/docker-proxy
I see the opening port of udp on 5353...
I tried also with this:
   "mdns": { "interface": "<IP_ADDRESS>" },
into my config but Homebridge cannot start with this config :(

if it is helpful this is my docker-compose.yml

version: '3'
services:
############################################################
Homebridge Server (51826 public port, 5353/udp)
############################################################
homebridge:
image: oznu/homebridge:latest
container_name: homebridge
restart: always
network_mode: bridge
ports:
# console
- 4000:4000
# Expose public port
- 51826:51826
- 6000:6000 #used by shelly admin page
# Avahi
- 5353:5353/udp
volumes:
- ./homebridge/config/:/homebridge
- ./ssl:/ssl
# - /etc/localtime:/etc/localtime:ro
logging:
driver: "json-file"
options:
max-size: "10m"
max-file: "5"
environment:
- PGID=1000
- PUID=1000
- TZ=Europe/Paris
- HOMEBRIDGE_CONFIG_UI=1
- HOMEBRIDGE_CONFIG_UI_PORT=4000

and my container server status:
IMAGE                     PORTS                                                                                NAMES
oznu/homebridge:latest    <IP_ADDRESS>:4000->4000/tcp, <IP_ADDRESS>:6000->6000/tcp, <IP_ADDRESS>:51826->51826/tcp, <IP_ADDRESS>:5353->5353/udp       homebridge
pihole/pihole:latest      <IP_ADDRESS>:53->53/udp, <IP_ADDRESS>:53->53/tcp, <IP_ADDRESS>:80->80/tcp, <IP_ADDRESS>:443->443/tcp, <IP_ADDRESS>:67->67/udp   pihole
portainer/portainer       <IP_ADDRESS>:9000->9000/tcp                                                                                portainer-app
eclipse-mosquitto:latest  <IP_ADDRESS>:1883->1883/tcp, <IP_ADDRESS>:9001->9001/tcp                                                         BrokerMQTT


not showing on android

I might have missed something on my side, I just ran npm install and react-native link and straight away plug in the code, but it is not showing on Android. On iOS, it is working seamless (I did follow the instruction to link ART.xcodeproj for iOS though)
Am I missing something on Android? I didn't see anything for android, it says for android it's already included.
Please enlighten me..

I have the same problem on Android Oreo.
There is an opened issue #89 related to Android Oreo (8.0+ ) or API 26+.
What is your your android version?

Also seeing this issue.
Gradle settings:
compileSdkVersion 25
buildToolsVersion "26.0.2"


Transcluded notes work differently in export

Describe the bug
I expect some differences between the HTML document structure in Obsidian vs the export. But the following broke some layout, in my case, and I couldn't find a reason for it.
In Obsidian, my internal embeds are a div>p>span:

vs the exported file, which is a div>p+div:

and also ends with another empty p:

Also, I use selectors for different types of embedded content, e.g. selecting on .internal-embed. My exported files don't include these classes (they were on the span), so I can't uniquely identify different cases for embeds. I relied on that to set --file-margins: 0; on transclusions, for example.
Operating System
Windows 11
To Reproduce
Create a couple of notes. Transclude one into the other. The note I transcluded used a section heading instead of the entire note, e.g. ![[Note name#Heading label]] instead of ![[Note name]].
Error Log
No errors; just logs.
obsidian.md-1683585876491.log

Transclusions are not officially supported by the plugin and if they work then it is a byproduct of generalized code. If I am understanding you correctly the problem is not that transclusions don't work, but just that the selectors are different and so your snippets don't work? Or is there more that is going wrong?

I see. They're pretty close, then -- all that's really missing is the top-level span, which contains the src and a class for the embed type.

I will modify it to make sure the transclusions have the same structure in the export as in obsidian's rendered view. Thanks for the report!

This is fixed in update 1.6.0, let me know if you have any more problems! And thanks for the report :)


Lumped RLC element support

Description: A clear and concise description of what the feature is.
Under Ansys HFSS I am able to assign a boundary condition on a 2d object which has it act like a lumped resistor inductor or capacitor, or some combination in parallel/series.  Is this something that can be done in Palace?  I am mostly interested in using this in the eigenmode simulation but other modes would be appreciated as well.
Add any other context or screenshots about the feature request here.
I am unsure of exactly how the mathematics underlying that boundary condition works but I know that when I assign the boundary in ansys I am required to supply a integration line along the direction of current flow. Is this something I could somehow adjust the surface impedance boundary condition to mimic or would it have to be a completely boundary setting?

Hi @nsluhrs, thanks for your question. What you are looking for is indeed already available in Palace using either the "Impedance" or "LumpedPort" boundaries.
If all you want to do is prescribe a surface impedance on a 2D boundary, the "Impedance" boundary allows you to specify an arbitrary R, L, and C for a resistor, inductor, and capacitor which add in parallel. The mapping between the surface R/L/C quantities and the circuit ones is described here.
The "LumpedPort" boundary is probably closer to what HFSS offers. It's the same boundary condition as the "Impedance" boundary, but adds functionality for postprocessing things like lumped voltage/current across the port once you have the electric and magnetic field solutions. The same principle of an "integration line" is specified using the "Direction" keyword, which takes either a cartesian direction ("+X", for example), or a 3D vector specifying the voltage direction across the port (direction between conductors).
For further information, I recommend taking a look at:

https://awslabs.github.io/palace/stable/guide/boundaries/#Impedance-boundary
https://awslabs.github.io/palace/stable/config/boundaries/#boundaries["Impedance"]
https://awslabs.github.io/palace/stable/config/boundaries/#boundaries["LumpedPort"]
https://awslabs.github.io/palace/stable/examples/cpw/ (here we use lumped ports to excite a coplanar waveguide structure, these are equivalent to lumped resistor boundaries).

The reference section of the docs might also be useful.
Let me know if you have any further questions or if something is not working for you. Thanks for your interest!

@sebastiangrimberg , thank you for your quick and thorough response. I suspected the impedance boundary might be the right thing to use, but clearly did not read the documentation thoroughly enough.


Unexpected Additional Input in Visual Shader Node

Godot version
4.1.1
System information
Windows 11
Issue description
I’ve encountered an issue with the visual shader node where it creates an additional input, despite the fact that it only supports one input. This behavior is unexpected and seems to be a bug.

Steps to reproduce

Open the Godot engine and navigate to the visual shader editor
Add a node structure similar to the screenshot above
Save the shader and close Godot
Open it again and observe that an additional input is created

Minimal reproduction project
shader_file_bug-report.zip

Can you explain what you mean by additional input? On the provided screenshot, it's not clear...

Can you explain what do you mean by additional input? On the provided screenshot, it's not clear...

The VectorOp node is designed to accommodate only a single connection for each input (a, b). However, as depicted in the screenshot, the second input (b) unexpectedly has two connections. This additional connection, originating from the Mix node on the left, appears randomly upon reopening Godot. It has no effect on the shader though. However, it makes it difficult to track the connected nodes on a more complicated shader

Ah, I see now, that's looks incorrect, yes.

Interesting，if you delete the additional link in the MRP and link it again, the bug will disappear. So there must be some corner case operation that caused the input check failed.


Docker Desktop FAQ updates

Updates to Docker Desktop Windows and Mac FAQs

Deploy preview for docsdocker ready!
Built with commit 62a720bbb716be3bcdb46fbe6d2a83b2bf530449
https://deploy-preview-9969--docsdocker.netlify.com

Thanks @traci-morrison. I've fixed the review comments. Could you PTAL?


Allow list items etc. to terminate paragraphs

This is another stab at #256. Unlike #291, I'm matching the paragraph imperatively rather than with a regex.
Fixes #256.

@probablyup bump!

Just wanted to quickly say I haven't forgotten about this! I've had COVID since the new year and am finally starting to feel normal again. Should have some time for OSS work this weekend.


Completed a kata but don't get any honor

I just completed a kata (ASCII Games: Dance Dance Evolution I) but don't get any point.
I found the honer change from 3870 to 3998 after the solution pass, but turn back to 3870 a few minutes later(also occur in Rank Breakdown). Is it a bug or something else.

Hi,
you didn't author that solution. The progress got removed.

Hi,
you didn't author that solution. The progress got removed.

This is my solution

Yes I know that.
Do you have a discord account? If so, poke at me (DM) on CW's server.

Do you have a discord account?

No

gitter, maybe, then?

gitter, maybe, then? (github account will do, for that)

I haven't use gitter before, I willI have a try.

Situation clarified. Completion revalidated.
Cheers

Thank you very much


Code formatting changes for readability

Description

Splits dictionaries into more digestible blocks and aligns them in a more readable way.
Fixes some formatting issues with the documentation.

Motivation and Context
This PR simply aims to make the code more readable.
How Has This Been Tested?
No logic changes were made. Existing tests were run and passed.

Did you submit a CLA?  Can't take any contributions without it. Thanks.

@billabt I have filled out and signed the CLA, but was unable to find the correct email address to send it to. The only address listed was a mailing address for @kweinmeister, who I reached out to on Twitter for an email but haven't heard back.

@billabt was delayed this weekend, but just sent out the signed CLA this morning.

You have the right email now?

The CLA was received. Thanks @alexpersian!


[data-tables] Avoid mutating client options parameter

Packages impacted by this PR
@azure/data-tables
Describe the problem that is addressed by this PR
If a consumer re-uses a single options argument when configuring multiple clients, they may run into issues because both the TableClient and TableServiceClient mutate the options bag directly instead of creating a copy.
Provide a list of related PRs (if any)
This issue was originally raised in the following community PR, but it was never merged:
https://github.com/Azure/azure-sdk-for-js/pull/26211

API change check
API changes are not detected in this pull request.


Impl human readable y axis(multipler of 1, 5, 10, 20, 50, ...)

Imple left one(right one is as-is)

Need to test on negative and very small scale


No way to set destination of inherited content files.  Puts them in root.

I have 3 packages, let call them A, B and C.
Their dependencies are as follows:
C references B, and B references A.
A has the following content:
 <Content Include="Startup\**\*.csv">
     <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </Content>

Inside of B, when referencing this project, the files show up correct in the Startup folder.
Now when packing B though, these content files are placed at the root.  So in C, the content files of A actually show up in the root directory.,
There is no way to set this using the package format.  I want to inherit the folder structures from child dependencies.
A picture of what happens in project C can be seen below (the original file structure does not stay intact):

A work around is as follows:
Exclude content files from B and directly reference A.
While this works, its not ideal, since consumers of package B need to know about package A.

Issue moved to NuGet/Home #8704 via ZenHub


Multporn change to all

Source name
Multporn
Source language
En
Describe your suggested feature
The site admin of multporn is planning to add more languages starting with German, I suggest changing it from en to all
Other details

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I have updated the app to version 0.15.3.
[X] I will fill out all of the requested information in this form.

I did tho

@stevenyomi please review, as we have been the ones that worked on the extension in this repo


Add socket.MSG_WAITALL to integration.py's run_framed()

This patch adds the MSG_WAITALL flag to integration.py's SingleSocketReceiver.run_framed() method.  Without the flag, it's possible for a integration test to fail due to a less-than-expected-sized read on the socket.

I'm afraid to ask about the amount of wat! moments that led to this.
Fix looks good!

Ha!  It was definitely more than one moment.


pp: fixed to return value like 'p'

Current implementation of pp returns nil always, but p returns printed value. It fixes to return printed value of 'pp' like p. I think its usability equals to p result value's.

Nice! That way one can wrap an expression with p and have it return the same value, super useful for debugging purposes. Thank you!


Token normalizing functions and improved word processing.

derepeat converts repeated chars to a single char.  E.g. foo --> fo
de1337 normalizes leet speak to latin chars E.g. 1337 #4x0rs --> leet haxors

Codecov Report

Merging #304 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #304      +/-   ##
==========================================
+ Coverage   85.33%   85.37%   +0.04%
==========================================
  Files         227      227
  Lines        7294     7318      +24
==========================================
+ Hits         6224     6248      +24
  Misses       1070     1070

Impacted Files
Coverage Δ

revscoring/datasources/meta/tests/test_gramming.py
100% <ø> (ø)
:arrow_up:

revscoring/datasources/meta/mappers.py
100% <100%> (ø)
:arrow_up:

revscoring/datasources/meta/gramming.py
100% <100%> (ø)
:arrow_up:

revscoring/datasources/meta/tests/test_mappers.py
100% <100%> (ø)
:arrow_up:

...scoring/features/wikitext/datasources/tokenized.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

One minor nitpick and we are good to go.


fix type test drafter

testing drafter

nice no gh action was triggered for drafter. These should only happen on main.


A list of layers like modules

Describe the feature
Hello,
Currently, modules are listed in nuxt.com/modules and nuxi allow us to easily add a module.
Layers seems to be a big part of Nuxt but I did not see anything related to them like a place to list all of them (and with studio, could be useful) and to add one using nuxi.
Additional information

[X] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

Transferring to (currently) private https://github.com/nuxt/nuxt.com repo to track there.


DrawingViewState has issues when "viewing" empty DrawingModels

Describe the bug
Opening IModelViewportControl with a DrawingViewState whose "base model" is an empty DrawingModel results in semi-broken view port. In this case, the camera cannot be zoomed in/out and other view manipulation tools (like rotate view) no longer work.
You can spot the troublesome code in DrawingViewState constructor where it assigns _modelLimits (its used for defaultExtentLimits implementation):
// extents.maxLength() returns 0 as there are no Elements in the DrawingModel
this._modelLimits = { min: Constant.oneMillimeter, max: 10 * extents.maxLength() };

To Reproduce
Can't suggest a good option for reproduction - create an empty DrawingModel and open a viewport to it (IModelViewportControl).
Expected behavior
Viewport should be usable when viewing an empty DrawingModel (e.g. view manipulation tools should work).
Screenshots
Getting spammed with errors while trying to zoom in or out.

Desktop (please complete the applicable information):

OS: Windows 11
Browser: Electron
Version: 24.0.0
iTwin.js Version: 4.1.0-dev.62

@raplemie

@ben-polinsky This would be an issue fixed within core-frontend DrawingViewState which would need to hanle it correctly (Ensure that Min is at least equal to Max I guess).
For the "Maximum Window" error, throttling/debouncing of the error messages should be implemented either in the toolAdmin, or in the ViewState.adjustViewDelta which are also in core-frontend.


Security risk with root certificate?

I'm looking at including this tool in a client's desktop application. As such, I would need to install a root certificate in order to allow for https handling. That said, is there a security risk to doing so? If so, what would be the recommended approach to making this work on an end user machine?

I would create a random unique root certificate for each installation on client machine rather than bundling one in your installation package. In that way the root certificate is not known to anyone else other than the client desktop. So if someone steals the root certificate from the desktop it can still only decrypt traffic from that specific client it was stolen from.


InputMenu increase padding when using backspace in Safari.

Environment

Operating System: Darwin
Node Version:     v20.8.0
Nuxt Version:     -
CLI Version:      3.10.1
Nitro Version:    -
Package Manager:  unknown
Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Version
v2.14.2
Reproduction
I believe the added files show the problem.
Description
Issue with Safari. Works without any issues with Chrome.
When focusing on an input menu and clearing all text using the backspace key, the top padding increases. However, this issue doesn't occur if you focus on the menu, then press CMD/CTRL + A followed by backspace. This issue is seen on the NuxtUI homepage as well. I have included some pictures from the homepage.

Additional context
No response
Logs
No response

Edit. One of the pictures wasn't added.

Thanks for the report! 😊


Add perplexity task on arbitrary JSON data

This adds a new magical task that uses arbitrary datasets in JSON format, specified like:
json=split:text-key:/path/to/data.json
For example:
json=train:text:c4-validation.json
To read the C4 validation split via the HF datasets library, taking the default train split created by datasets and selecting the text key from each JSON line for perplexity evaluation.

Merged from upstream in aca3634fffb6f7d120390aafdd72b257b866e8b5.


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20220522162500906 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20220522162500906 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.057%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
27997

Relevant Lines:
62269

💛  - Coveralls


CAMEL-20113: camel/tests consolidating

Description
org.apache.camel.itest.jms:
-AdviceWithTransactionIssueTest - moved to camel-jms;
-DynamicRouteTest - moved to camel-jms;
-FileToJmsTest - moved to camel-jms;
-JmsConsumerShutdownTest - moved to camel-jms;
-JmsIntegrationTest - jms sending to queue and processing with custom bean is checked in others tests, so it is deleted;
-JmsMediumQueuePerformanceTest - tests to play with the performance tuning are org.apache.camel.component.jms.tuning.PerformanceRouteTest and PerformanceRoutePojoTest, so this test is deleted;
-JmsPerformanceTest - tests to play with the performance tuning are org.apache.camel.component.jms.tuning.PerformanceRouteTest and PerformanceRoutePojoTest, so this test is deleted;
-JmsPollingConsumerTest - moved to camel-jms;
-JmsPollEnrichTest - moved to camel-jms;
-JMSNestedTransactionRollbackTest - moved to camel-jms;
-JmsResequencerTest - resequence is checked in other camel-jms tests, so this test is deleted;
-JmsValidatorTest - moved to camel-jms;
-SpringJmsValidatorTest - moved to camel-jms;
Tracking
https://issues.apache.org/jira/browse/CAMEL-20113

/component-test camel-jms

/component-test camel-jms

I wonder if this test fails for you also

org.apache.camel.component.jms.JmsDeliveryDelayTest.testInOnlyWithDelay
10.21s
FAILURE

I wonder if this test fails for you also
org.apache.camel.component.jms.JmsDeliveryDelayTest.testInOnlyWithDelay	10.21s	FAILURE

Yes, it have failed in the build job, but it passes in /component-test camel-jms and local runs

/component-test camel-jms

I wonder if this test fails for you also
org.apache.camel.component.jms.JmsDeliveryDelayTest.testInOnlyWithDelay	10.21s	FAILURE

Yes, it have failed in the build job, but it passes in /component-test camel-jms and local runs EDIT: it seems that sometimes it fails in /component-test camel-jms also. Should I look into why it fails?

Hi, yes. Ideally we want to reduce the flakiness of our tests, so we can trust the results from our CI.

I wonder if this test fails for you also
org.apache.camel.component.jms.JmsDeliveryDelayTest.testInOnlyWithDelay	10.21s	FAILURE

Yes, it have failed in the build job, but it passes in /component-test camel-jms and local runs EDIT: it seems that sometimes it fails in /component-test camel-jms also. Should I look into why it fails?

Hi, yes. Ideally we want to reduce the flakiness of our tests, so we can trust the results from our CI.

Hello, thanks for the reply! Ok, I'll look into it.
Do I understand correctly that it is failing due to assertion error?
Also, should I work on it into a separate pr? It seems nothing to do with the tests moved in this pr.

Do I understand correctly that it is failing due to assertion error?

I think so. It seems to be flaky, but unfortunately GH doesn't keep logs from multiple runs so I cannot double check (and add it here to make it easier for you to debug).

Also, should I work on it into a separate pr? It seems nothing to do with the tests moved in this pr.

Oh, my bad. I am sorry. I thought this test was one of the tests modified as part of the PR ... but after a second review, that's not the case.
In this case, it's something to be fixed later (feel free to contribute it if you want, otherwise we will fix it eventually).
Based on that, I think this one is ready to go.


Greatly speed up block height lookups and contains_key calls

Supersedes https://github.com/AleoHQ/snarkOS/pull/1538.
This reduces the time needed to validate inbound block locators from hundreds of ms to zero ms. It will also boost any other operation which calls get_block_height.

Rebased and added 2 extra commits:

perf: use Storage::get_raw in Storage::contains_key (we don't need to deserialize the value in those calls)
refactor: rewrite Storage::get using Storage::get_raw (code deduplication)

I'm currently working on some storage benchmarks and they confirm the gains from these changes (and the result below is just the get_block_height-specific improvement):
lookup_by_hash          time:   [858.88 ns 861.34 ns 864.27 ns]
                        change: [-99.998% -99.998% -99.998%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) high mild

And below are the effects of just perf: use Storage::get_raw in Storage::contains_key on the LedgerState::contains_X methods:
blocks_lookup_by_height time:   [479.89 ns 480.82 ns 481.87 ns]
                        change: [-30.139% -29.995% -29.856%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 100 measurements (2.00%)
  1 (1.00%) low mild
  1 (1.00%) high severe

txs_lookup_by_id        time:   [667.34 ns 668.88 ns 670.68 ns]
                        change: [-50.577% -50.430% -50.282%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 4 outliers among 100 measurements (4.00%)
  4 (4.00%) high mild

txs_lookup_by_commitment
                        time:   [812.51 ns 813.86 ns 815.13 ns]
                        change: [-14.584% -14.387% -14.202%] (p = 0.00 < 0.05)
                        Performance has improved.

txs_lookup_by_serial_number
                        time:   [789.79 ns 791.33 ns 792.81 ns]
                        change: [-20.740% -20.561% -20.391%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) low mild

An alternative approach without using get_raw would be to use the block_heights DataMap with some sort of iterator. Of course this will be much slower (O(N)), but will keep our base storage module simple.

DataMaps already use iterators internally; there's no going around this one, I'm afraid, if we want storage to be fast, and having plain lookups taking hundreds of milliseconds is unacceptable in terms of the negative influence on async operations.

@raychu86 I adjusted the first commit so that the partial deserialization doesn't involve any slicing and fixed lengths - instead, the values before the height get deserialized and dropped; this should still be cheap enough.

What exactly is the use case that motivates this change?
If we want to call directly into bytes, we might as well write snarkOS in C++.

The motivation is that get_block_height lookups take milliseconds, which is thousands of times longer than the other storage lookups are (hundreds of nanoseconds), which currently causes them to be blocking operations in async contexts, especially when validating block locators. This was reported by @HarukaMa, who indicated that an associated operator-related operation was noticably slow.
get_raw is intended to be used only in 3 scenarios:

in the implementation of contains_key (because then the values don't need to be deserialized at all, and this method allows that)
in the implementation of get (to deduplicate code, as it already does the same thing internally)
in specific, very limited cases like get_block_height, where the alternative is a blocking operation, which can and will disrupt all the other async operations of the node, especially with many peers

Rebased.


Fix #26: deploy powervm-rmc daemonset during ocp-customization

Signed-off-by: Sebastien Chabrolles<EMAIL_ADDRESS>
This uses k8s ansible module in order to apply k8s yaml in an idempotent and efficient way (need openshift python module to be installed on the bastion.
namespace creation, serviceaccount creation and daemonset creation use yaml and k8s ansible module.
giving "privileged" right to powervm-rmc service account is done via oc command (I don't find how to use yaml for this)
Need to load rpadlpar_io module on coreOS node to enable DLPAR for IO card (like veth, NPIV or SRIOV, or even Real PCI card). This is done with another Machineconfig for master and worker roles.

I added a reboot "pause" during ocp-customization. It should avoid the first "worker" and "master" to be rebooted several times due to multiple machineconfig changes. (Currently under test on my system)


Invalid options in vue.config.js: "baseUrl" is not allowed

Version
4.2.2
Environment info
 System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
  Binaries:
    Node: 11.13.0 - ~/.nvm/versions/node/v11.13.0/bin/node
    Yarn: 1.19.1 - /usr/local/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v11.13.0/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: 68.0.1
    Safari: 13.0.5
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0
    @vue/babel-plugin-transform-vue-jsx:  1.1.2
    @vue/babel-preset-app:  4.2.2
    @vue/babel-preset-jsx:  1.1.2
    @vue/babel-sugar-functional-vue:  1.1.2
    @vue/babel-sugar-inject-h:  1.1.2
    @vue/babel-sugar-v-model:  1.1.2
    @vue/babel-sugar-v-on:  1.1.2
    @vue/cli-overlay:  4.2.2
    @vue/cli-plugin-babel: ^4.2.2 => 4.2.2
    @vue/cli-plugin-eslint: ^4.2.2 => 4.2.2
    @vue/cli-plugin-router:  4.2.2
    @vue/cli-plugin-vuex:  4.2.2
    @vue/cli-service: ^4.2.2 => 4.2.2
    @vue/cli-shared-utils:  4.2.2 (3.12.1)
    @vue/component-compiler-utils:  3.1.1
    @vue/eslint-config-prettier: ^6.0.0 => 6.0.0
    @vue/preload-webpack-plugin:  1.1.1
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^6.1.2 => 6.1.2
    svg-to-vue:  0.6.0
    vue: ^2.6.11 => 2.6.11
    vue-cli-plugin-cordova: ^2.4.0 => 2.4.0
    vue-cli-plugin-electron-builder: ^1.4.5 => 1.4.5
    vue-context-menu: ^2.0.6 => 2.0.6
    vue-electron: ^1.0.6 => 1.0.6
    vue-eslint-parser:  7.0.0
    vue-hot-reload-api:  2.3.4
    vue-loader:  15.8.3
    vue-router: ^3.1.5 => 3.1.5
    vue-style-loader:  4.1.2
    vue-svg-loader: ^0.15.0 => 0.15.0
    vue-template-compiler: ^2.6.11 => 2.6.11
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: 4.2.2

Steps to reproduce
vue create my_app
vue ui
# Import project from current folder
# Go to config in vue ui & save
# Run the dev server by npm run serve from vue ui or CLI

What is expected?
No errors
What is actually happening?
Invalid options in vue.config.js: "baseUrl" is not allowed

Thanks for submitting this issue! Due to our limited time, we ask you to include a reproduction link to a minimal full reproduction of your problem (for example in a GitHub repository) so we can find what is causing the issue. Thank you for your understanding!

@sodatea This is not a coding issue, the problem is that vue ui still adds baseUrl to the vue config file on save, but it has been deprecated and replaced by publicPath.
See https://cli.vuejs.org/config/#baseurl
So because it is deprecated, vue cli will create an error by its own generated file ^^.

Can't reproduce. And I can't find any reference to baseUrl in the Vue CLI UI codebase.

I've tried myself. I thought baseUrl has replaced by publicPath. Here's the screenshot.


OSA [1588051] Resolve double-logging

Do NOT include any confidential information, this issue will be created on a public repo
This section is completed by the issue reporter
On which version(s) do you encounter this issue?
Please provide the output to 'git describe --all' for  all deployments where you have confirmed it occurs.
What type of issue is this? Please tick the appropriate box.

[x] bug - existing functionality that does not work for you as documented
[ ] feature - new functionality that you would like to see added

What is the expected behavior?
Double logging band-aid mentioned
https://bugs.launchpad.net/openstack-ansible/+bug/1588051
What is actually happening?
Double logging band-aid mentioned
https://bugs.launchpad.net/openstack-ansible/+bug/1588051
What were you attempting to do when you encountered this error (give as much detail as possible)?
Double logging band-aid mentioned
https://bugs.launchpad.net/openstack-ansible/+bug/1588051
How can we reproduce this issue?
Double logging band-aid mentioned
https://bugs.launchpad.net/openstack-ansible/+bug/1588051
How can we verify your issue is addressed?
Double logging band-aid mentioned
https://bugs.launchpad.net/openstack-ansible/+bug/1588051
If you are using or know of a workaround please describe the necessary steps?
Double logging band-aid mentioned
https://bugs.launchpad.net/openstack-ansible/+bug/1588051
What is your evaluation on the importance of this issue, and why?
Double logging band-aid mentioned
https://bugs.launchpad.net/openstack-ansible/+bug/1588051
This section is completed during the issue resolution process. If you are reporting an issue, please do not modify the section below.
Which branches are impacted by this issue?
Remove branches that are not impacted.
For each pull request, update the branch line to reference it.

[ ] master
[ ] liberty-12.2
[ ] kilo

Upgrade impact. Consider the impact on moving between major, minor and patch releases.

[ ] This change does not impact upgrades
[ ] This change addresses a potential upgrade impact
[ ] The upgrade impact is being tracked by another issue.

The issue tracking the upgrade impact is:
Testing impact

[ ] An issue/pull-request has been create or exists to track the testing gap, and is referenced below
[ ] This change includes additional testing
[ ] This change is tested by the existing setup

Additional testing links:
Release note

[ ] This change includes a release note.
[ ] This change does not require a release note.

Doc Impact
Does your change require documentation?

[ ] Yes, and I submitted an issue to Docs issues
[ ] Yes, and I contributed a documentation patch to docs-rpc
[ ] No documentation required for this change

Additional documentation links (please add links if you have ticked yes):

Looks like a patch for this has already been implemented.


Automatically fill size

Do you think you could use the measureElement API to make this fill the available space?

Do you think you could use the measureElement API to make this fill the available space?

Just use this:
import type React from 'react'
import { Box, type BoxProps } from 'ink'

/**
 * Props for the Divider component.
 */
export interface DividerProps extends BoxProps {
	/**
	 * Color of the divider's border. Matches the type of `borderColor` in the Ink `Box` component.
	 * Accepts standard Ink color names or hex codes.
	 * @default "blackBright"
	 */
	color?: BoxProps['borderColor']
}

/**
 * A horizontal divider component styled as a single border line.
 *
 * @param props - Properties to customize the divider.
 * @returns A styled Ink `Box` component representing a divider.
 */
const Divider: React.FC<DividerProps> = ({
	color = 'blackBright',
	...props
}) => (
	<Box
		borderColor={color}
		borderStyle="single"
		borderBottom={true}
		borderTop={false}
		borderLeft={false}
		borderRight={false}
		{...props}
	/>
)

I think in the near future I will create an updated module with automatic expansion of the Divider width on npm

@JureSotosek Do you accept PRs to this repository?

Yes, make a PR and i'll merge it.

Yes, make a PR and i'll merge it.

I thought this project was completely dead... 😅
Ok, my plan is to make it work in ink, rewrite the Divider logic so that it now works based on the Box component (as in the comment above) and also make it backwards compatible with existing projects so I don't break anything
If I don't have time to do it today, I'll finish it on Monday

Awesome, thanks 😀

Awesome, thanks 😀

And another question
Should I use this stack?

Bun (https://bun.sh) for building package
TypeScript
Biome formatter

@okineadev  If you make it with bun will it still be 100% compatible with node?

@okineadev Sure lets do that.

@okineadev Sent you a message on X!


Phi-3 Vision

Phi-3 is already supported, so I hope this should not be too difficult:
https://huggingface.co/microsoft/Phi-3-vision-128k-instruct

Is Phi-3-vision still have to be added in ollama?

https://github.com/ggerganov/llama.cpp/issues/7444

Looks like that llama.cpp convert HF to GGUF code can't support Phi3V yet.

Going to close this as a dupe.

@pdevine Can you please clarify whether Phi3-vision is supported or not? If yes, what is the proper template for it?

@levicki Unfortunately not yet. The dupe was to track it in #4560

@levicki Unfortunately not yet. The dupe was to track it in #4560

Thanks for the clarification. I am confused as to what the problem is with supporting that model? There's also a newer version (3.5) that came out in the meantime. Didn't llama.cpp already add support for it? Or is there perhaps some other issue with it?


"IS this the only way to set types in a dataframe?" The answer is no.…

… This is the also far more pythonic.
I want to see if I can help a bit more on this also and I'd love to try to increase the readable of this so others could more easily help improve FaST-LMM
Cheers!

Hopefully that fixes everything

Thanks, I'll leave to official review to CarlKCarlK.

Thanks for the fix. I’ll include it in the next release.
From: Christian<EMAIL_ADDRESS>Sent: Sunday, February 11, 2018 12:27 PM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Subject: Re: [MicrosoftGenomics/FaST-LMM] "IS this the only way to set types in a dataframe?" The answer is no.… (#27)
Thanks, I'll leave to official review to CarlKCarlK.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftGenomics%2FFaST-LMM%2Fpull%2F27%23issuecomment-364785129&data=02|01||bc7c74ba0f3042b724cb08d5718dd2d4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636539776293106361&sdata=qkCP33q4C0T%2FrPkG5aK9Q0qwEjmk4v22zXOyVdAlaM4%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGPuv3uxXpIejEDzsLjp-bRmJxPWPknrks5tT00bgaJpZM4R3zFe&data=02|01||bc7c74ba0f3042b724cb08d5718dd2d4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636539776293106361&sdata=2SGvofsfvFZIjefjITMVEEkikWiPBkIr1ydslDIDLR8%3D&reserved=0.


buildMozillaMach: addon signing and sideloading fixes

Description of changes
Properly passes through requireSigning and allowAddonSideload so the wrapper will accept valid browsers.
Additionally, makes requireSigning and allowAddonSideload overridable.
This fixes some issues introduced by #244591.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3402

how might one use this?

how might one use this?

https://nixos.org/manual/nixpkgs/unstable/#build-wrapped-firefox-with-extensions-and-policies
You need to wrap Firefox ESR, regular Firefox will not work.

As of recent Firefox ESR versions, that is no longer the case! I don't remember off of the top of my head, but I think you need to use either Firefox Dsveloper Edition and/or LibreWolf now. The trace in the wrapper file should say which.
If you want a specific Firefox version, you'll need to override the settings for requiring signing and allowing sideloading, and recompile.


is there a "skip" or "drop", like "take"?

Hi there,
Firstly, thank you so much for nom, it is a true pleasure to use. We use it regularly in production and it has been rock solid, and a real joy to develop with. Hopefully I will be able to open-source a parser we have written soon.
I have no issue to report, just a question:
I am wondering if there is a combinator that is similar to take, but drops/discards/skips the given number of bytes rather than returning them. Saying this another way, is there something like:
let s = skip(2usize)(s)?;

that simply returns the input with a certain number of prefix bytes removed, as opposed to using take like so:
let (s, _skipped_bytes) = take(2usize)(s)?;

I certainly can make a function that does this, I'm just curious if such a thing exists as a primitive in nom.
I have searched the documentation and the source and so far not been able to find anything, but I may have missed it. Thank you!

Hello! any updates?)

Since take can provide the same functionality at the same performance (I presume), I'm curious what your motivation is.  Is it to make the code more declarative / read as a grammar?

I'm trying to learn rust, and for the project I decided on, I need a parser and decided on nom.  I literally just started looking at this library 10 minutes ago, and I was looking for "skip". Since @ikrivosheev didn't provide a reasoning, I thought I'd provide mine.
My experience comes from nimble_parsec which, being Elixir, uses chaining heavily. It's a small thing, but I was just after the same type of streamlined code. You can see they have an ignore which will ignore the output of any combinator, so it wouldn't quite be skip(3) like take(3) but more generally, skip(take(3))(s).
Again, in my case, it was just about removing the unnecessary extra let (s, _) = ...., which I think decreases the readability of the code.
(I'm not suggesting that what's idiomatic in Elixir would make sense or belongs in Rust. Obviously, I need to adapt to the Rust-way.)

@karlseguin

Again, in my case, it was just about removing the unnecessary extra let (s, _) = ...., which I think decreases the readability of the code.

Except skip would just change the output type to () at best and you would still have let (s, ()) = ... which isn't much different.
That said, I feel like a generic combinator is better than specialized versions of each function.  combine does this with Parser::skip while chumsky does Parser::ignored.  As @Xiretza points out in #1566, we already do have value((), p) and proposes void(p).


Formatting heavily nested code

This is a please-change-formatting request.  I do not think it conflicts with existing rules.
Here is a piece of code that Black formatted, but it is a bit ugly:
    config = Config(
        **unwrap(
            set_default(
                {},
                config,
                {
                    "overrides": {
                        "run": {
                            # "hide": True,
                            "out_stream": self.stdout,
                            "err_stream": self.stderr,
                        }
                    }
                },
            )
        )
    )

If there is only one item enclosed in brackets, we can put it on the same line as the opening bracket:
    config = Config(**unwrap(set_default(
        {},
        config,
        {"overrides": {"run": {
            # "hide": True,
            "out_stream": self.stdout,
            "err_stream": self.stderr,
        }}},
    )))

Thank you.

I don't think the proposed formatting is more readable at all. In fact, I think both of them are pretty unreadable because of the amount of nesting going on.
I don't think there's much Black can do about this.


Calculate the default value of Miou_unix.{really_read,read,write} ?len only when necessary

Just a small optimization

This is a super-interesting PR. Thanks a lot for raising my attention to Option.value evaluating the default always.


shorten the display of Authors, if there are too many

I think that the look of the latest UD is really bad. We have to shorten the Authors field when there are too many authors. We don't have to be as strict as in bibliography (first 1 or 2, et al.), but this is way too much. http://hdl.handle.net/11234/1-3424
I think that the simple item record and also the display in the list of search results (or in the homepage's What's new section)  have to be modified. Maybe the full list could be available as a "title" of the <dd> element containing all the authors? (Btw, does each author have to be wrapped in a <span> with no attributes?)

I don't think it is much worse than UD 2.6. We need to have ONE list publicly on the web with ALL authors. Otherwise Google Scholar will never lit them, and authors with names in the second half of the alphabet will never get the credit...
JH

From: "Pavel Stranak"<EMAIL_ADDRESS>To: "ufal"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Sent: Friday, November 13, 2020 11:19:40 PM
Subject: [ufal/clarin-dspace] shorten the display of Authors, if there are too
many (#956)

I think that the look of the latest UD is really bad. We have to shorten the
Authors field when there are too many authors. We don't have to be as strict as
in bibliography (first 1 or 2, et al.), but this is way too much. [
http://hdl.handle.net/11234/1-3424 | http://hdl.handle.net/11234/1-3424 ]

I think that the simple item record and also the display in the list of search
results (or in the homepage's What's new section) have to be modified. Maybe
the full list could be available as a "title" of the  element containing
all the authors? (Btw, does each author have to be wrapped in a  with no
attributes?)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [ https://github.com/ufal/clarin-dspace/issues/956
| view it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ACEWWVSHUPZ26VHH3CKTSZTSPWWHZANCNFSM4TVDOLLQ
| unsubscribe ] .

On 13 Nov 2020, at 23:33, Jan Hajic<EMAIL_ADDRESS>wrote:
I don't think it is much worse than UD 2.6.

Yes, but that one is bad too. On the homepage when it was there (which is always) it takes quite a while before I can see something other than in this screenshot. And that is on a really big screen, not a phone. It serves zero purpose here, I think.

We need to have ONE list publicly on the web with ALL authors. Otherwise Google Scholar will never lit them, and authors with names in the second half of the alphabet will never get the credit...

I agree this is a priority. But I am also quote sure it can be solved. I.e. by hiding part of the text via CSS.
Which reminds me of one more place this long list should be avoided: the RefBox (formated text; not CMDI and probably not Bibtex).
-Pavel

JH

From: "Pavel Stranak"<EMAIL_ADDRESS>To: "ufal"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Sent: Friday, November 13, 2020 11:19:40 PM
Subject: [ufal/clarin-dspace] shorten the display of Authors, if there are too
many (#956)

I think that the look of the latest UD is really bad. We have to shorten the
Authors field when there are too many authors. We don't have to be as strict as
in bibliography (first 1 or 2, et al.), but this is way too much. [
http://hdl.handle.net/11234/1-3424 | http://hdl.handle.net/11234/1-3424 ]

I think that the simple item record and also the display in the list of search
results (or in the homepage's What's new section) have to be modified. Maybe
the full list could be available as a "title" of the  element containing
all the authors? (Btw, does each author have to be wrapped in a  with no
attributes?)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [ https://github.com/ufal/clarin-dspace/issues/956
| view it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ACEWWVSHUPZ26VHH3CKTSZTSPWWHZANCNFSM4TVDOLLQ
| unsubscribe ] .
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ufal/clarin-dspace/issues/956#issuecomment-727068392, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC2TIVEJWH7PG7R5HTQTA3SPWX5HANCNFSM4TVDOLLQ.

OK, CSS is probably a good solution, with Google getting it in full. Can there be a little box/arrow/anything that after clicking by the user will show full list? That would be ideal from my point of view.
Biblio must have all names for sure.
In the refbox, the same limit as for the css is probably OK.
JH

From: "Pavel Stranak"<EMAIL_ADDRESS>To: "ufal"<EMAIL_ADDRESS>Cc: "Jan Hajic"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Sent: Friday, November 13, 2020 11:41:32 PM
Subject: Re: [ufal/clarin-dspace] shorten the display of Authors, if there are
too many (#956)

On 13 Nov 2020, at 23:33, Jan Hajic<EMAIL_ADDRESS>wrote:

I don't think it is much worse than UD 2.6.

Yes, but that one is bad too. On the homepage when it was there (which is
always) it takes quite a while before I can see something other than in this
screenshot. And that is on a really big screen, not a phone. It serves zero
purpose here, I think.

We need to have ONE list publicly on the web with ALL authors. Otherwise Google
Scholar will never lit them, and authors with names in the second half of the
alphabet will never get the credit...

I agree this is a priority. But I am also quote sure it can be solved. I.e. by
hiding part of the text via CSS.

Which reminds me of one more place this long list should be avoided: the RefBox
(formated text; not CMDI and probably not Bibtex).

-Pavel

JH

From: "Pavel Stranak"<EMAIL_ADDRESS>To: "ufal"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Sent: Friday, November 13, 2020 11:19:40 PM
Subject: [ufal/clarin-dspace] shorten the display of Authors, if there are too
many (#956)

I think that the look of the latest UD is really bad. We have to shorten the
Authors field when there are too many authors. We don't have to be as strict as
in bibliography (first 1 or 2, et al.), but this is way too much. [
http://hdl.handle.net/11234/1-3424 | http://hdl.handle.net/11234/1-3424 ]

I think that the simple item record and also the display in the list of search
results (or in the homepage's What's new section) have to be modified. Maybe
the full list could be available as a "title" of the  element containing
all the authors? (Btw, does each author have to be wrapped in a  with no
attributes?)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [ https://github.com/ufal/clarin-dspace/issues/956
| view it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ACEWWVSHUPZ26VHH3CKTSZTSPWWHZANCNFSM4TVDOLLQ
| unsubscribe ] .
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ufal/clarin-dspace/issues/956#issuecomment-727068392, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC2TIVEJWH7PG7R5HTQTA3SPWX5HANCNFSM4TVDOLLQ.

—
You are receiving this because you commented.
Reply to this email directly, [
https://github.com/ufal/clarin-dspace/issues/956#issuecomment-727070487 | view
it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ACEWWVXXOHZXLSJHDMGLDJLSPWYZZANCNFSM4TVDOLLQ
| unsubscribe ] .

Refbox already does some sort of "... et al."
Scholar should use metadata embedded in html meta tags, but nobody actually knows.
I think there even might be an issue for the search & frontpage views, I dont think there ever was a preferred display format...
13. 11. 2020 23:49:32 Jan Hajic<EMAIL_ADDRESS>
OK, CSS is probably a good solution, with Google getting it in full. Can there be a little box/arrow/anything that after clicking by the user will show full list? That would be ideal from my point of view.
Biblio must have all names for sure.
In the refbox, the same limit as for the css is probably OK.
JH

From: "Pavel Stranak"<EMAIL_ADDRESS>To: "ufal"<EMAIL_ADDRESS>Cc: "Jan Hajic"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Sent: Friday, November 13, 2020 11:41:32 PM
Subject: Re: [ufal/clarin-dspace] shorten the display of Authors, if there are
too many (#956)

On 13 Nov 2020, at 23:33, Jan Hajic<EMAIL_ADDRESS>wrote:

I don't think it is much worse than UD 2.6.

Yes, but that one is bad too. On the homepage when it was there (which is
always) it takes quite a while before I can see something other than in this
screenshot. And that is on a really big screen, not a phone. It serves zero
purpose here, I think.

We need to have ONE list publicly on the web with ALL authors. Otherwise Google
Scholar will never lit them, and authors with names in the second half of the
alphabet will never get the credit...

I agree this is a priority. But I am also quote sure it can be solved. I.e. by
hiding part of the text via CSS.

Which reminds me of one more place this long list should be avoided: the RefBox
(formated text; not CMDI and probably not Bibtex).

-Pavel

JH

From: "Pavel Stranak"<EMAIL_ADDRESS>To: "ufal"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Sent: Friday, November 13, 2020 11:19:40 PM
Subject: [ufal/clarin-dspace] shorten the display of Authors, if there are too
many (#956)

I think that the look of the latest UD is really bad. We have to shorten the
Authors field when there are too many authors. We don't have to be as strict as
in bibliography (first 1 or 2, et al.), but this is way too much. [
http://hdl.handle.net/11234/1-3424 | http://hdl.handle.net/11234/1-3424 ]

I think that the simple item record and also the display in the list of search
results (or in the homepage's What's new section) have to be modified. Maybe
the full list could be available as a "title" of the  element containing
all the authors? (Btw, does each author have to be wrapped in a  with no
attributes?)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [ https://github.com/ufal/clarin-dspace/issues/956
| view it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ACEWWVSHUPZ26VHH3CKTSZTSPWWHZANCNFSM4TVDOLLQ
| unsubscribe ] .
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ufal/clarin-dspace/issues/956#issuecomment-727068392, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC2TIVEJWH7PG7R5HTQTA3SPWX5HANCNFSM4TVDOLLQ.

—
You are receiving this because you commented.
Reply to this email directly, [
https://github.com/ufal/clarin-dspace/issues/956#issuecomment-727070487 | view
it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ACEWWVXXOHZXLSJHDMGLDJLSPWYZZANCNFSM4TVDOLLQ
| unsubscribe ] .
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub[https://github.com/ufal/clarin-dspace/issues/956#issuecomment-727072793], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAOBZUORDERRTKHYLORU6VTSPWZXVANCNFSM4TVDOLLQ]. [https://github.com/notifications/beacon/AAOBZUODWVAX56J6K4FLUVDSPWZXVA5CNFSM4TVDOLL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFNLEAGI.gif]

Not sure if it's relevant or useful, but we have modified the refbox authors rule in our installation: https://github.com/clarinsi/clarin-dspace/issues/15.

closed by #979


[EOSF-657] Fix color of branded subjects on submit subject picker

Ticket
https://openscience.atlassian.net/browse/EOSF-657
Purpose
Fix color of branded subjects on submit subject picker
Changes
Move CSS around so it can be overwritten by brand, add right-arrow element to branded css

Before and after screenshots, please.


[Python] Magma/Landscape/Prospector example outdated

Link to example for Landscape code quality tool https://landscape.io/github/NLeSC/MAGMa says the project is not being checked.
Is there an up to date example?

MAGMa was added to landscape a while ago, seems it has been forgotten, I tried to re-add, but failed.
I just tried to add a repo, but it also failed with https://landscape.io/github/3D-e-Chem/sygma/1
In the tour they use https://landscape.io/github/akvo/akvo-rsr as the example repo.

The text that this issue refers to appears to be no longer in the guide.


hqz-week4-5

What problem does this PR solve?

What have you done or changed in this PR?
What test did you complete before submitting the PR?

新的提交做了一些改进：
①解决了内存泄露问题：LRU Replacer 析构时自定义的链表没有释放
②CMU Autograder 达到了160/160
③把直接对互斥锁的lock改为使用c++提供的lock_guard


refactor: Use async initialization of tests

It solves a problem that tests run into deadlock if test collections are more than available threads

There are the methods (RunSynchronously) that are became not used after this PR. I don't delete it because I don't know whether they are used in other projects or not.

Let me think a bit about this change.
Although, this seems nice, I'm worried that it might be confusing for developers, that they can't write the test-initialization code in constructors anymore (and have to override InitializeAsync method instead).
I mean, that changes like in webapi/tests/MccSoft.TemplateApp.ComponentTests/ProductControllerTests.cs are required in all tests, but developers are used to write initialization code in constructors (which seems like an obvious place, but it will not work anymore)


feat(espp-rtsp): use espp::RtspClient

Description

Moved RtspClient into espp submodule and use that
Updated main code accordingly

Motivation and Context

Using the submodule helps ensure the client and server stay in sync as changes come.
How has this been tested?

Building and running the main code. See also https://github.com/esp-cpp/espp/pull/58
Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update
[ ] Hardware (schematic, board, system design) change
[x] Software change

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have added / updated the documentation related to this change via either README or WIKI

Software

[ ] I have added tests to cover my changes.
[ ] I have updated the .github/workflows/build.yml file to add my new test to the automated cloud build github action.
[x] All new and existing tests passed.
[x] My code follows the code style of this project.

Related to #1


Removes unnecessary imports.

Removes imports in ActionConfiguration.ts. They must have come in by carelessly copying the configuration of the extpfeil package.

Looks good.  Merging.


Updated Action Hooks and Classes for Wordpress Coding Standards

Also fixed a couple “yoda condition” issues to make unit testing pass.

Also, and I feel like I am nitpicking here, but if we are to follow coding standards then The WordPress Naming Conventions say this about naming classes:

Class names should use capitalized words separated by underscores.

@Aetles you were totally right. I completely missed that in the menu walkers. It had actually happened in menu-walker.php as well, but I went ahead and changed it. It now reads:
$element->has_children && 1 !== $max_depth

Also thanks for reminding me of the true WP Standards definition for classes. I don't know why I was under the impression that it Classes were to be camel-case. Either way, it should all be changed now. I think I hit all the classes, but might need to have a double check on that.
The only thing that remains in question in my mind would be the text domain. WordPress doesn't seem to have a standard for the text-domain. However in the I18n Documentation found here it does state the following under the text domain section:
If you're translating a plugin or a theme, you'll need to use a text domain to denote all text belonging to that plugin. This increases portability and plays better with already existing WordPress tools. The text domain must match the “slug” of the plugin.

Great! About the text domain: I'd vote for changing FoundationPress to foundationpress as that is more "slug-like".

@olefredrik What do you think about the text domain change?

I agree that it could be okay to change the text-domain to foundationpress, as long as this change does not affect any existing translations (I see no reason why it should). In all cases, the FoundationPress repository is now build passing, due to your great contributions. Well done, guys! You are awesome!


BUG: Enhance RegisterSchema with Additional Validations

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
In backend there is no validation for password asking the password should be :

Lowercase & Uppercase
Number (0-9)
Special Character (!@#$%^&*)
Atleast 8 Character

user gets created successfully without password validation

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
In backend there is no validation for password asking the password should be :

Lowercase & Uppercase
Number (0-9)
Special Character (!@#$%^&*)
Atleast 8 Character

user gets created successfully without password validation

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue
assigned! tag me when you create a PR!


Minor Bug in resolving full name if suffix matches a salutation

The following Name: "PAUL M LEWIS MR"
returns the following
Array
(
    [0] => PAUL
    [1] => TheIconic\NameParser\Part\Initial Object
        (
            [value:protected] => M
        )

    [2] => LEWIS
    [3] => TheIconic\NameParser\Part\Salutation Object
        (
            [normalized:protected] => Mr.
            [value:protected] => MR
        )

)

making this break and getFirstname and getLastName returns nothing.
the issue seems to be the following line
https://github.com/theiconic/name-parser/blob/master/src/Language/English.php#L41
this probably going to happen with any of the salutations if they come at the end.
Edit:
Another Example:
"SUJAN MASTER"
"JAMES J MA"
"PETER K MA"

Hi @VinceG . Interesting. Yes, in it's current form the name parser expects the title up-front. The assumption is that if it's in the end, it would be separated by a comma. Do you have actual cases where the title is entered in the end without comma-separation? Theoretically (or rather from the mappers perspective) this should be possible to fix, but in the overall parse order scheme it could complicate things quite a bit as some of the mappers have to make assumptions about positioning.

@wyrfel Thank You for the quick reply and fix.
This seems to fix the issue where the last word matches a salutation in the first case. However this does not seem to fix the other issues
Here are our test cases
/** @test */
    public function it_can_parse_saluation_at_end()
    {
        $parsed = (new NameParser)->parse('PAUL M LEWIS MR');

        $this->assertEquals('Paul', $parsed->getFirstName());
        $this->assertEquals('Lewis', $parsed->getLastName());
    }

    /** @test */
    public function it_can_parse_saluation_lastname()
    {
        $parsed = (new NameParser)->parse('SUJAN MASTER');

        $this->assertEquals('Sujan', $parsed->getFirstName());
        $this->assertEquals('Master', $parsed->getLastName());
    }

    /** @test */
    public function it_can_parse_saluation_lastname_with_middlename()
    {
        $parsed = (new NameParser)->parse('JAMES J MA');

        $this->assertEquals('James', $parsed->getFirstName());
        $this->assertEquals('Ma', $parsed->getLastName());
    }

the first one passes the second and third fail. It's worth noting that "PAUL M LEWIS MR" the MR at the end is not the salutation but rather part of his last name the way they write it.
1) Tests\Unit\ExampleTest::it_can_parse_saluation_lastname
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'Sujan'
+''

/Users/vincentgabriel/Sites/fhalicenses/tests/Unit/ExampleTest.php:33

2) Tests\Unit\ExampleTest::it_can_parse_saluation_lastname_with_middlename
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'Ma'
+''

TheIconic\NameParser\Name Object
(
    [parts:protected] => Array
        (
            [0] => TheIconic\NameParser\Part\Lastname Object
                (
                    [value:protected] => SUJAN
                )

            [1] => TheIconic\NameParser\Part\Salutation Object
                (
                    [normalized:protected] => Mr.
                    [value:protected] => MASTER
                )

        )

)

TheIconic\NameParser\Name Object
(
    [parts:protected] => Array
        (
            [0] => TheIconic\NameParser\Part\Firstname Object
                (
                    [value:protected] => JAMES
                )

            [1] => TheIconic\NameParser\Part\Initial Object
                (
                    [value:protected] => J
                )

            [2] => TheIconic\NameParser\Part\Suffix Object
                (
                    [normalized:protected] => MA
                    [value:protected] => MA
                )

        )

)

"SUJAN MASTER"
"JAMES J MA"
"PETER K MA"
The above all fail since the last name is considered a salutation even though it's actually the last name. I am not entirely sure how to properly fix this without having breaking changes. One solution that came to mind is checking the number of parts, if we have 2 parts that is should be considered as first and lastname but then it might cause problems when the name has any other combination of two words such as salutation firstname or middle last name etc..
Thanks again for the help.

@VinceG All these cases should now be working in version 1.2.6.
I had misunderstood the issue originally, thank you for the clarifications.
I hope this solves the problem more generally for you.
Please see #16 for details.


Fix validate mapping

Codecov Report
Attention: Patch coverage is 91.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 77.49%. Comparing base (6d471c2) to head (51ee14b).
Report is 1 commits behind head on main.

Files
Patch %
Lines

experimental_experiment/xoptim/patterns_api.py
91.66%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #169      +/-   ##
==========================================
+ Coverage   77.43%   77.49%   +0.05%
==========================================
  Files         120      120
  Lines       13868    13881      +13
==========================================
+ Hits        10739    10757      +18
+ Misses       3129     3124       -5

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


doc/Language/traps.pod6 examples

This file is explicitly skipped when running examples compilation.
It should be removed from the skip list, and then the minimum of :skip-test added to fix the examples so they compile.
(in some cases, only an OUTPUT: tag is needed to mark output, in others, a section that is clearly marked as FAIL needs to be skipped, while the main portion of the example should be compiled)

To run just this file, use:
perl6 xt/examples-compilation.t doc/Language/traps.pod6

And when it passes, remove this line:
https://github.com/perl6/doc/blob/master/xt/examples-compilation.t#L30

Fixed in 17ad67fd63 and f65904cf2e


Dependencies for HTTP component have to be specified twice

First in the component definition:
(def-http-component Http "api.yaml" [db tokens])

Then in the system map:
(system/http-system-map configuration
                        map->Http [:db :tokens]
                        :db (db/make-db (:db configuration))
                        :tokens (oauth2/map->OAUth2TokenRefresher ...))

Maintaining these two places is error-prone and non-beginner-friendly.
This also relates to #48.

Hey @dryewo, can we close this issue? It's from May 2016.
Or, we could add a "Help Wanted" label.

Was covered in #97


[style] Use lowercase namespace name

Resolves https://github.com/openthread/ot-br-posix/issues/374

I'm touching ot::Ip6 code and when I used Ip6::in th Ip6  and got an unexpected error. The complier thinks of it as the namespace name rather than the class name.


Bugfix/home page typo

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: kavithamsk sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Add karma dashboard to the list of integrations

Signed-off-by: Łukasz Mierzwa<EMAIL_ADDRESS>@brian-brazil pointed that page as the best place to add this
I've added a new category for it since it didn't seem to be a good fit for any existing one. I hope the wording is correct.
It's would be a good idea to add a link to the API docs but I don't see those linked anywhere in docs, only in the README, so I wasn't sure about that. The least we could add right now is probably the API v2 is still under heavy development and thereby subject to change. note, but then I'm not sure if the integration page is the right place to track API status, so I decided to leave that decision to someone else.

I think the category is correct.

Should I then move it or not?

Updated

Thanks!


Fixed tablets scrolling without touching/clicking

Fixes #619
Pen pointers were previously allowing for scrolling even if no buttons were reported being pressed. Pens send a pointermove event every time they move, regardless of if any buttons are pressed.

Thanks!

@Silvea12 Thank you for this fix!
@noraesae The Github example needs an update to reflect this fix, right now the problem still occurs here. Can you update and bump the version?

Sure. The patch is released with v0.8.1

@noraesae Thank you, it works fine now!

We ran into this issue on Picarto.tv, we are using your scroll system. There is also one other weird bug but it keeps evading us whenever we test it. Will send a pull request when we find that.


Moving Social Activities Framework from kie-uberfire-extensions to uberfire-extensions

WIP (please wait some mins)

@ederign Looks like you've removed the dependency on Drools (hence it was in kie-uberfire-extensions) and introduced "fake" implementations of the classes that used to require Drools. What affect does this have on functionality. For example see SocialTimelineRulesQuery.

@ederign OK.. I'll wait.. I see the other PRs coming.. and (assume) a Drools specific implementation of the interfaces may be in one of the other PRs (e.g. kie-wb-common or somewhere).

jenkins retest this

jenkins retest this (I'll fix those tests in my next task)

Jenkins retest this

jenkins retest this


Can you upload the original design file of PCB? I want to change the packaging

Can you upload the original design file of PCB? I want to change the packaging

Done. But some custom models may be missing


iTunes Connect Analytics

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I'd like to download analytics, but I haven't found a Ruby library to do so. I poked around and didn't see a way to get analytics using Spaceship; is it supported? If not what is the interest in adding it?
Environment
fastlane version (run fastlane -v): fastlane 1.90.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? yes
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? rbenv

There are some issues for that already: https://github.com/fastlane/fastlane/search?q=iTunes+Connect+Analytics&type=Issues&utf8=✓
Some contributors already started building it (https://github.com/fastlane-old/spaceship/pull/190), however it doesn't seem like it got merged.
You might want to reach out on that issue and offer your help if you want to 👍

Closing this for now 👍


Open infrared & depth stream with rs2::syncer

Required Info

Camera Model
D400

Firmware Version
2.36

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
NVIDIA Jetson

SDK Version
2.36}

Language
C++

Issue Description
Simple question, although I can't find an example anywhere: how do I open an infrared stream (Infrared sensor #1) and depth stream on the stereo module at the same time using the rs2::syncer class.
This is obviously easy with pipe, config.enable_stream, etc., etc. although I am keen to use the syncer class instead.
doing depth_sensor.open(sp_ir) and depth_sensor.open(sp_dep) results in this error:
open(...) failed. UVC device is already opened!
fairly unsurprisingly. As the stream profiles for IR and depth both use stereo module numbering this figures although it is obviously possible.
Is rs2::syncer able to be used with IR and depth streams as they are by definition synced?
Please let me know.
Tom.

Hi @tom-garford
Please try something like depth_sensor.open({sp_dep, sp_ir}), the overload taking vector of stream profiles. The camera requires IR and depth to be opened at the same time.

Hi @dorodnic
Thanks very much for your swift answer. That works great, as does
std::vector<rs2::stream_profile>  sp_dep_ir = depth_sensor.get_stream_profiles()  -->  depth_sensor.open(sp_dep_ir)
when opening a rosbag with a depth and IR stream.
Thanks very much.
Tom.


Cannot write nulls to the database

If I try to pass a point like this to write_points, I get an error (the payload generator generates GPS.city=)
{ timestamp: point['time'], series: 'car', tags: { license: tags['license'] }, values: { 'GPS.city' => nil } }

Currently, that's intended: you simply cannot store null values. (I've stumbled upon thi myself, see influxdata/influxdb#6150).
For the moment, I recommend using something .select{|_,v| !v.nil? } (or .compact if ActiveSupport is available) on the hash you pass to write_point/write_points.
If you really need this in several places and projects, we could discuss an omit_nil_values option for InfluxDB::Client.

It's more that I actively want to overwrite existing values with nulls.
Some values that come into the database are invalid data on analysis, and
I'm looking for a way to remove them or to mark them as invalid.

I see.
Maybe it's easier to store raw and analyzed data in different measurements (that is what I do)?

I have that (of sorts), but it would still require recalculation of the whole (quite large) derived measurement when the algorithm changes for any one of the fields. But if InfluxDB doesn't allow for it, there's nothing much the ruby interface can do.

Indeed. Maybe influxdata/influxdb#6150 is too broad and you should to file a different issue.