[Bug] RayCluster fails to detect pods for 0.5.0-rc.0

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
Installed helm install kuberay-operator kuberay/kuberay-operator --version 0.5.0-rc.0 --namespace ray-system on kind cluster.
Run kubectl apply -f https://raw.githubusercontent.com/ray-project/kuberay/master/ray-operator/config/samples/ray_v1alpha1_rayjob.yaml
All the pods has been create successfully, but the job never started. When I checked the monitor logs, I found that the autoscaler never detected the pods.
After looking at the logs of the ray-operator, I found this error:
ClientConnectorError: Cannot connect to host <IP_ADDRESS>:52365 ssl:default [Connect call failed ('<IP_ADDRESS>', 52365)]\n
The port 52365 never appeared in pod's description. The ray port is 6379, metrics port 8080, serve port 8000, client port 10001, dashboard 8265 and gcs-server port is 6379.
Monitor logs:
6970Pending:71 (no pending nodes)72Recent failures:73 (no failures)7475Resources76---------------------------------------------------------------77Usage:7879Demands:80 (no resource demands)812023-04-16 23:55:31,117	INFO autoscaler.py:463 -- The autoscaler took 0.01 seconds to complete the update iteration.822023-04-16 23:55:36,137	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.832023-04-16 23:55:41,149	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.842023-04-16 23:55:46,169	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.852023-04-16 23:55:51,189	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.862023-04-16 23:55:56,212	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.872023-04-16 23:56:01,238	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.882023-04-16 23:56:06,264	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.892023-04-16 23:56:11,286	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.902023-04-16 23:56:16,301	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.912023-04-16 23:56:21,319	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.922023-04-16 23:56:26,331	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.932023-04-16 23:56:31,358	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.942023-04-16 23:56:36,368	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.952023-04-16 23:56:41,388	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.962023-04-16 23:56:46,409	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.972023-04-16 23:56:51,430	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.982023-04-16 23:56:56,451	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.992023-04-16 23:57:01,472	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.1002023-04-16 23:57:06,496	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.1012023-04-16 23:57:11,523	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.1022023-04-16 23:57:16,557	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
Ray operator logs:
controllers.RayJob	Submit a ray job	{"rayJob": "rayjob-sample", "jobInfo": "{\"entrypoint\":\"python /home/ray/samples/sample_code.py\",\"job_id\":\"rayjob-sample-5wzkg\",\"runtime_env\":{\"env_vars\":{\"counter_name\":\"test_counter\"},\"pip\":[\"requests==2.26.0\",\"pendulum==2.1.2\"]}}"} 2023-04-17T06:55:25.958Z	ERROR	controllers.RayJob	failed to submit job	{"error": "SubmitJob fail: Traceback (most recent call last):\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 980, in _wrap_create_connection\n    return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa\n  File \"/home/ray/anaconda3/lib/python3.7/asyncio/base_events.py\", line 962, in create_connection\n    raise exceptions[0]\n  File \"/home/ray/anaconda3/lib/python3.7/asyncio/base_events.py\", line 949, in create_connection\n    await self.sock_connect(sock, address)\n  File \"/home/ray/anaconda3/lib/python3.7/asyncio/selector_events.py\", line 473, in sock_connect\n    return await fut\n  File \"/home/ray/anaconda3/lib/python3.7/asyncio/selector_events.py\", line 503, in _sock_connect_cb\n    raise OSError(err, f'Connect call failed {address}')\nConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 52365)\n\nThe above exception was the direct cause of the following exception:\n\nTraceback (most recent call last):\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/ray/dashboard/modules/job/job_head.py\", line 292, in submit_job\n    resp = await job_agent_client.submit_job_internal(submit_request)\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/ray/dashboard/modules/job/job_head.py\", line 75, in submit_job_internal\n    f\"{self._agent_address}/api/job_agent/jobs/\", json=dataclasses.asdict(req)\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/client.py\", line 1141, in __aenter__\n    self._resp = await self._coro\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/client.py\", line 537, in _request\n    req, traces=traces, timeout=real_timeout\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 540, in connect\n    proto = await self._create_connection(req, traces, timeout)\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 901, in _create_connection\n    _, proto = await self._create_direct_connection(req, traces, timeout)\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 1206, in _create_direct_connection\n    raise last_exc\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 1187, in _create_direct_connection\n    client_error=client_error,\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 988, in _wrap_create_connection\n    raise client_error(req.connection_key, exc) from exc\naiohttp.client_exceptions.ClientConnectorError: Cannot connect to host <IP_ADDRESS>:52365 ssl:default [Connect call failed ('<IP_ADDRESS>', 52365)]\n"} 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-04-17T06:55:25.959Z	INFO	controllers.RayJob	reconciling RayJob	{"NamespacedName": "default/rayjob-sample"} 2023-04-17T06:55:25.959Z	INFO	controllers.RayJob	RayJob associated rayCluster found	{"rayjob": "rayjob-sample", "raycluster": "default/rayjob-sample-raycluster-7tb9w"} 2023-04-17T06:55:26.046Z	DEBUG	controllers.RayJob	RayJob information	{"RayJob": "rayjob-sample", "jobInfo": null, "rayJobInstance": ""} 2023-04-17T06:55:26.046Z	INFO	controllers.RayJob	Submit a ray job	{"rayJob": "rayjob-sample", "jobInfo": "{\"entrypoint\":\"python /home/ray/samples/sample_code.py\",\"job_id\":\"rayjob-sample-5wzkg\",\"runtime_env\":{\"env_vars\":{\"counter_name\":\"test_counter\"},\"pip\":[\"requests==2.26.0\",\"pendulum==2.1.2\"]}}"} 2023-04-17T06:55:26.146Z	ERROR	controllers.RayJob	failed to submit job	{"error": "SubmitJob fail: Traceback (most recent call last):\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 980, in _wrap_create_connection\n    return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa\n  File \"/home/ray/anaconda3/lib/python3.7/asyncio/base_events.py\", line 962, in create_connection\n    raise exceptions[0]\n  File \"/home/ray/anaconda3/lib/python3.7/asyncio/base_events.py\", line 949, in create_connection\n    await self.sock_connect(sock, address)\n  File \"/home/ray/anaconda3/lib/python3.7/asyncio/selector_events.py\", line 473, in sock_connect\n    return await fut\n  File \"/home/ray/anaconda3/lib/python3.7/asyncio/selector_events.py\", line 503, in _sock_connect_cb\n    raise OSError(err, f'Connect call failed {address}')\nConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 52365)\n\nThe above exception was the direct cause of the following exception:\n\nTraceback (most recent call last):\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/ray/dashboard/modules/job/job_head.py\", line 292, in submit_job\n    resp = await job_agent_client.submit_job_internal(submit_request)\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/ray/dashboard/modules/job/job_head.py\", line 75, in submit_job_internal\n    f\"{self._agent_address}/api/job_agent/jobs/\", json=dataclasses.asdict(req)\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/client.py\", line 1141, in __aenter__\n    self._resp = await self._coro\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/client.py\", line 537, in _request\n    req, traces=traces, timeout=real_timeout\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 540, in connect\n    proto = await self._create_connection(req, traces, timeout)\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 901, in _create_connection\n    _, proto = await self._create_direct_connection(req, traces, timeout)\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 1206, in _create_direct_connection\n    raise last_exc\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 1187, in _create_direct_connection\n    client_error=client_error,\n  File \"/home/ray/anaconda3/lib/python3.7/site-packages/aiohttp/connector.py\", line 988, in _wrap_create_connection\n    raise client_error(req.connection_key, exc) from exc\naiohttp.client_exceptions.ClientConnectorError: Cannot connect to host <IP_ADDRESS>:52365 ssl:default [Connect call failed ('<IP_ADDRESS>', 52365)]\n"} 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
Master pod yaml:
`apiVersion: v1
kind: Pod
metadata:
annotations:
ray.io/ft-enabled: "false"
ray.io/health-state: ""
creationTimestamp: "2023-04-17T06:55:05Z"
generateName: rayjob-sample-raycluster-7tb9w-head-
labels:
app.kubernetes.io/created-by: kuberay-operator
app.kubernetes.io/name: kuberay
ray.io/cluster: rayjob-sample-raycluster-7tb9w
ray.io/cluster-dashboard: rayjob-sample-raycluster-7tb9w-dashboard
ray.io/group: headgroup
ray.io/identifier: rayjob-sample-raycluster-7tb9w-head
ray.io/is-ray-node: "yes"
ray.io/node-type: head
name: rayjob-sample-raycluster-7tb9w-head-n8dqq
namespace: default
ownerReferences:

apiVersion: ray.io/v1alpha1
blockOwnerDeletion: true
controller: true
kind: RayCluster
name: rayjob-sample-raycluster-7tb9w
uid: b142f8d0-b9db-4331-812f-a58a8d659c31
resourceVersion: "2176"
uid: 4f9e2c9d-78b4-4673-aaad-c366e51bcc96
spec:
containers:
args:

'ulimit -n 65536; ray start --head  --block  --dashboard-host=<IP_ADDRESS>  --num-cpus=2  --metrics-export-port=8080 '
command:
/bin/bash
-lc

env:

name: RAY_CLUSTER_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.labels['ray.io/cluster']
name: RAY_PORT
value: "6379"
name: RAY_ADDRESS
value: <IP_ADDRESS>:6379
name: RAY_USAGE_STATS_KUBERAY_IN_USE
value: "1"
name: REDIS_PASSWORD
image: rayproject/ray:2.3.0
imagePullPolicy: IfNotPresent
name: ray-head
ports:
containerPort: 6379
name: gcs-server
protocol: TCP
containerPort: 8265
name: dashboard
protocol: TCP
containerPort: 10001
name: client
protocol: TCP
containerPort: 8000
name: serve
protocol: TCP
containerPort: 8080
name: metrics
protocol: TCP
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
mountPath: /home/ray/samples
name: code-sample
mountPath: /dev/shm
name: shared-mem
mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: kube-api-access-t2ljn
readOnly: true
dnsPolicy: ClusterFirst
enableServiceLinks: true
nodeName: kube-local-worker3
preemptionPolicy: PreemptLowerPriority
priority: 0
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
serviceAccount: default
serviceAccountName: default
terminationGracePeriodSeconds: 30
tolerations:

effect: NoExecute
key: node.kubernetes.io/not-ready
operator: Exists
tolerationSeconds: 300
effect: NoExecute
key: node.kubernetes.io/unreachable
operator: Exists
tolerationSeconds: 300
volumes:
configMap:
defaultMode: 420
items:

key: sample_code.py
path: sample_code.py
name: ray-job-code-sample
name: code-sample

emptyDir:
medium: Memory
name: shared-mem
name: kube-api-access-t2ljn
projected:
defaultMode: 420
sources:

serviceAccountToken:
expirationSeconds: 3607
path: token
configMap:
items:

key: ca.crt
path: ca.crt
name: kube-root-ca.crt

downwardAPI:
items:

fieldRef:
apiVersion: v1
fieldPath: metadata.namespace
path: namespace
status:
conditions:

lastProbeTime: null
lastTransitionTime: "2023-04-17T06:55:05Z"
status: "True"
type: Initialized
lastProbeTime: null
lastTransitionTime: "2023-04-17T06:55:05Z"
status: "True"
type: Ready
lastProbeTime: null
lastTransitionTime: "2023-04-17T06:55:05Z"
status: "True"
type: ContainersReady
lastProbeTime: null
lastTransitionTime: "2023-04-17T06:55:05Z"
status: "True"
type: PodScheduled
containerStatuses:
containerID: containerd://2290bf524ab4a88e139718ee2d7ad203f3672c96e1e027a3e12bbb7a81f3706c
image: docker.io/rayproject/ray:2.3.0
imageID: docker.io/rayproject/ray@sha256:ba406e5fe129a1f3dc9885f873f26c573cc3d2f5bd6e7179847f52acff315b89
lastState: {}
name: ray-head
ready: true
restartCount: 0
started: true
state:
running:
startedAt: "2023-04-17T06:55:05Z"
hostIP: <IP_ADDRESS>
phase: Running
podIP: <IP_ADDRESS>
podIPs:
ip: <IP_ADDRESS>
qosClass: BestEffort
startTime: "2023-04-17T06:55:05Z"`

Reproduction script
helm install kuberay-operator kuberay/kuberay-operator --version 0.5.0-rc.0 --namespace ray-system
kubectl apply -f https://raw.githubusercontent.com/ray-project/kuberay/master/ray-operator/config/samples/ray_v1alpha1_rayjob.yaml
Anything else
Is rayjob considered a stable object to work with for this version?
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Hi @davidLif, I checked your reproduction script, and autoscaler is not enabled in https://raw.githubusercontent.com/ray-project/kuberay/master/ray-operator/config/samples/ray_v1alpha1_rayjob.yaml. Could you double check the reproduction script and try to reproduce it on Kind cluster?

Based on ClientConnectorError: Cannot connect to host <IP_ADDRESS>:52365 ssl:default [Connect call failed ('<IP_ADDRESS>', 52365)]\n, it may be caused by your Kubernetes cluster networking restrictions.

@kevin85421 The cluster I am working on is a Kind cluster installed on my Mac, so the "nodes" have no networking restrictions between them.
Also, I know that the autoscaler isn't enabled by the job. This are simply the logs I see at monitor.log .
The monitor.log file looks like this:
`2023-04-16 23:55:15,803	INFO monitor.py:651 -- Starting monitor using ray installation: /home/ray/anaconda3/lib/python3.7/site-packages/ray/init.py
2023-04-16 23:55:15,806	INFO monitor.py:652 -- Ray version: 2.3.0
2023-04-16 23:55:15,806	INFO monitor.py:653 -- Ray commit: cf7a56b4b0b648c324722df7c99c168e92ff0b45
2023-04-16 23:55:15,806	INFO monitor.py:654 -- Monitor started with command: ['/home/ray/anaconda3/lib/python3.7/site-packages/ray/autoscaler/_private/monitor.py', '--logs-dir=/tmp/ray/session_2023-04-16_23-55-11_389145_14/logs', '--logging-rotate-bytes=536870912', '--logging-rotate-backup-count=5', '--gcs-address=<IP_ADDRESS>:6379', '--monitor-ip=<IP_ADDRESS>']
2023-04-16 23:55:15,909	INFO monitor.py:167 -- session_name: session_2023-04-16_23-55-11_389145_14
2023-04-16 23:55:15,922	INFO monitor.py:200 -- Starting autoscaler metrics server on port 44217
2023-04-16 23:55:15,934	INFO monitor.py:218 -- Monitor: Started
2023-04-16 23:55:15,993	INFO autoscaler.py:276 -- disable_node_updaters:False
2023-04-16 23:55:15,994	INFO autoscaler.py:285 -- disable_launch_config_check:False
2023-04-16 23:55:15,994	INFO autoscaler.py:296 -- foreground_node_launch:False
2023-04-16 23:55:15,994	INFO autoscaler.py:306 -- worker_liveness_check:True
2023-04-16 23:55:15,995	INFO autoscaler.py:314 -- worker_rpc_drain:True
2023-04-16 23:55:15,999	INFO autoscaler.py:364 -- StandardAutoscaler: {'cluster_name': 'default', 'max_workers': 0, 'upscaling_speed': 1.0, 'docker': {}, 'idle_timeout_minutes': 0, 'provider': {'type': 'readonly', 'use_node_id_as_ip': True}, 'auth': {}, 'available_node_types': {'ray.head.default': {'resources': {}, 'node_config': {}, 'max_workers': 0}}, 'head_node_type': 'ray.head.default', 'file_mounts': {}, 'cluster_synced_files': [], 'file_mounts_sync_continuously': False, 'rsync_exclude': [], 'rsync_filter': [], 'initialization_commands': [], 'setup_commands': [], 'head_setup_commands': [], 'worker_setup_commands': [], 'head_start_ray_commands': [], 'worker_start_ray_commands': [], 'head_node': {}, 'worker_nodes': {}}
2023-04-16 23:55:16,011	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:55:21,038	INFO autoscaler.py:144 -- The autoscaler took 0.0 seconds to fetch the list of non-terminated nodes.
2023-04-16 23:55:21,040	INFO autoscaler.py:419 --
======== Autoscaler status: 2023-04-16 23:55:21.039524 ========
Node status
Healthy:
1 node_d39ce353c0c40c6cfd9e9901d770e88f3f554d871699bcd8b34dcafd
Pending:
(no pending nodes)
Recent failures:
(no failures)
Resources
Usage:
0.0/2.0 CPU
0.00/8.365 GiB memory
0.00/4.182 GiB object_store_memory
Demands:
(no resource demands)
2023-04-16 23:55:21,059	INFO autoscaler.py:463 -- The autoscaler took 0.022 seconds to complete the update iteration.
2023-04-16 23:55:26,076	INFO autoscaler.py:144 -- The autoscaler took 0.0 seconds to fetch the list of non-terminated nodes.
2023-04-16 23:55:26,076	INFO load_metrics.py:163 -- LoadMetrics: Removed ip: d39ce353c0c40c6cfd9e9901d770e88f3f554d871699bcd8b34dcafd.
2023-04-16 23:55:26,077	INFO load_metrics.py:169 -- LoadMetrics: Removed 1 stale ip mappings: {'d39ce353c0c40c6cfd9e9901d770e88f3f554d871699bcd8b34dcafd'} not in {'bf83ec9c019c8af74d511593d724fd004e5a4a4eccf990d81cbe0f0b'}
2023-04-16 23:55:26,078	INFO autoscaler.py:419 --
======== Autoscaler status: 2023-04-16 23:55:26.077809 ========
Node status
Healthy:
1 node_bf83ec9c019c8af74d511593d724fd004e5a4a4eccf990d81cbe0f0b
Pending:
(no pending nodes)
Recent failures:
(no failures)
Resources
Usage:
0.0/5.0 CPU
0.00/10.060 GiB memory
0.00/4.311 GiB object_store_memory
Demands:
(no resource demands)
2023-04-16 23:55:26,081	INFO autoscaler.py:463 -- The autoscaler took 0.006 seconds to complete the update iteration.
2023-04-16 23:55:31,107	INFO autoscaler.py:144 -- The autoscaler took 0.0 seconds to fetch the list of non-terminated nodes.
2023-04-16 23:55:31,109	INFO load_metrics.py:163 -- LoadMetrics: Removed ip: bf83ec9c019c8af74d511593d724fd004e5a4a4eccf990d81cbe0f0b.
2023-04-16 23:55:31,109	INFO load_metrics.py:169 -- LoadMetrics: Removed 1 stale ip mappings: {'bf83ec9c019c8af74d511593d724fd004e5a4a4eccf990d81cbe0f0b'} not in set()
2023-04-16 23:55:31,111	INFO autoscaler.py:419 --
======== Autoscaler status: 2023-04-16 23:55:31.111456 ========
Node status
Healthy:
Pending:
(no pending nodes)
Recent failures:
(no failures)
Resources
Usage:
Demands:
(no resource demands)
2023-04-16 23:55:31,117	INFO autoscaler.py:463 -- The autoscaler took 0.01 seconds to complete the update iteration.
2023-04-16 23:55:36,137	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:55:41,149	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:55:46,169	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:55:51,189	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:55:56,212	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:01,238	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:06,264	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:11,286	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:16,301	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:21,319	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:26,331	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:31,358	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:36,368	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:41,388	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:46,409	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:51,430	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:56:56,451	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:01,472	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:06,496	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:11,523	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:16,557	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:21,580	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:26,612	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:31,637	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:36,665	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:41,699	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
2023-04-16 23:57:46,729	INFO monitor.py:389 -- Autoscaler has not yet received load metrics. Waiting.
`
With endless repetition of the last line.

The problem seems to have be resolved with one of the new updates to the version


Add ExchangeIssuancePerp.sol

Add ExchagneIssuancePerp without test script

Coverage decreased (-2.2%) to 82.959% when pulling 111a6f262fa32ad8dc87e72519caa648e02f3fc9 on crypto-ticky:master into fa0bff6e43843ff4cb7d4d2b60f3edf85290cca3 on IndexCoop:master.

Closing this in favor of #111


set up continuous integration

We should set up continuous integration to run on every PR and commit to the master branch:

bun run lint
bun test

Done with PR #12


Roadmap page is broken

Bug type
Docs (mudblazor.com)
Component name
No response
What happened?
Go here: https://www.mudblazor.com/mud/project/roadmap
The following errors show in the Console:
Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID
https://raw.githubusercontent.com/MudBlazor/MudBlazor/dev/ROADMAP.md

And
blazor.webassembly.js:1  crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: TypeError: Failed to fetch
System.Net.Http.HttpRequestException: TypeError: Failed to fetch
 ---> TypeError: Failed to fetch
   Exception_EndOfInnerExceptionStack
   at System.Net.Http.BrowserHttpInterop.<CancelationHelper>d__13`1[[System.Runtime.InteropServices.JavaScript.JSObject, System.Runtime.InteropServices.JavaScript, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].MoveNext()
   at System.Net.Http.BrowserHttpHandler.CallFetch(HttpRequestMessage , CancellationToken , Nullable`1 )
   at System.Net.Http.BrowserHttpHandler.<SendAsync>g__Impl|53_0(HttpRequestMessage , CancellationToken , Nullable`1 )
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage , HttpCompletionOption , CancellationTokenSource , Boolean , CancellationTokenSource , CancellationToken )
   at MudBlazor.Docs.Pages.Mud.Project.Roadmap.OnInitializedAsync()
   at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task , ComponentState )

Expected behavior
I expect to be able to see the Roadmap.
Reproduction link
https://www.mudblazor.com/mud/project/roadmap
Reproduction steps

Open up Microsoft Edge
Go here: https://www.mudblazor.com/mud/project/roadmap
Observe Error on screen and in console.

Relevant log output
Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID
https://raw.githubusercontent.com/MudBlazor/MudBlazor/dev/ROADMAP.md

blazor.webassembly.js:1  crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: TypeError: Failed to fetch
System.Net.Http.HttpRequestException: TypeError: Failed to fetch
 ---> TypeError: Failed to fetch
   Exception_EndOfInnerExceptionStack
   at System.Net.Http.BrowserHttpInterop.<CancelationHelper>d__13`1[[System.Runtime.InteropServices.JavaScript.JSObject, System.Runtime.InteropServices.JavaScript, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].MoveNext()
   at System.Net.Http.BrowserHttpHandler.CallFetch(HttpRequestMessage , CancellationToken , Nullable`1 )
   at System.Net.Http.BrowserHttpHandler.<SendAsync>g__Impl|53_0(HttpRequestMessage , CancellationToken , Nullable`1 )
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage , HttpCompletionOption , CancellationTokenSource , Boolean , CancellationTokenSource , CancellationToken )
   at MudBlazor.Docs.Pages.Mud.Project.Roadmap.OnInitializedAsync()
   at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task , ComponentState )

Version (bug)
2024-02-22
Version (working)
No response
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Works for me in Firefox, Microsoft Edge and Chrome.

Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID
https://raw.githubusercontent.com/MudBlazor/MudBlazor/dev/ROADMAP.md

The error suggest that the problem is not really with the MudBlazor, but browser is having a problem with the cert so it's either problem with githubusercontent or some MS bug.

Working for me.  Sounds like an OS/Browser cert chain issue


HDDS-8656: Do not log zero byte object creation

What changes were proposed in this pull request?
Do not log zero byte object creation
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8656
How was this patch tested?
Existing tests should cover this.

@tanvipenumudy can you please take a look ?

@Xushaohong please take a look


⚠ AGEG website (prod) has degraded performance

In 33f2f78, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 17851 ms

Resolved: AGEG website (prod) performance has improved in 62654a6.


Azure HDInsight on AKS Trino Connector Documentation

Contains:

Summary
Capabilities
Connection Instructions for Power BI Desktop
Advanced Options
Troubleshooting

Also:

Images in image folder
Logo in logo folder
Added to list of connectors
Added to TOC

@georgewfisher,
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.
We'll close this PR. Thank you.


BIG WEATHER ICONS UPDATE COMING UP!

Here I come with a huge weather icon update that can help you out!
New WeatherSTAR 4000+ Icon Package Update!.zip

Great work! 👏


[Logging] Debug logs

JIRA: EE-1345

As discussed this morning, renamed "debug" logs to "verbose" logs, diff there.


bug: Carousel of Cards does not behave as expected

What version of daisyUI are you using?
4.12.10
Which browsers are you seeing the problem on?
Chrome
Reproduction URL
https://play.tailwindcss.com/jCdSW9XQ2A
Describe your issue
Using the default Carousel example but swapping out the <img> elements in the example with the default Card example breaks the Carousel's horizontal scroll behavior, allowing the Cards to cause a horizontal page scroll instead.

Add a width to it. Like w-full
It's not a good idea if I add a default width to the library as default because the width depends on the content.
Let me know if you have a question.


Added PickerView with expansion cell

I see what you're trying to do here. It's a pretty good idea, but I think we can take it further.
What if we added this functionality to BOChoiceTableViewCell as an optional way to choose an option? I can think of a mode property defining whether the cell works via taps or the picker view itself.
What do you think?

@DavdRoman excellent idea! this way the user would be able to choose a preferred way

Good to hear your thoughts, @mythodeia :smile:

@DavdRoman at the beginning I was shared between including it into BOChoiceTableViewCell, or make it "independent" in case it would be pushed further in customization/functionnalities.
A mode option is a good idea, and I'm fine with it if you want to go this way ;-)

Exactly my thoughts too, although I think the case is simple enough to mix it into a simple cell.
I'll start working on it :+1:


[node] Add new port

Why building Node from source?
Because of embedding use case https://nodejs.org/api/embedding.html

@BillyONeal

node-api-headers provides C-api for writing nodejs addons (native DLLs to be used in javascript apps)
node-addon-api is a C++ wrapper for node-api-headers
node in this PR is a whole runtime build to be embedded into user apps see https://nodejs.org/api/embedding.html .

node is logically opposite to node-api-headers (while technically including node-api-headers headers)
node port is for embedding nodejs into your C++ app
node-api-headers is for writing a C++ dll (so called addon) to be embedded into JavaScript app

node is logically opposite to node-api-headers (while technically including node-api-headers headers)

Does this mean that node and node-api-headers can't be simultaneously installed because they stomp on the same paths?

@BillyONeal Good question. I'll make sure they can by utilizing a separate include subfolder or making node-api-headers a node dependency.
Converting back into draft till fixing this and x86 build

x86-windows has issues. disabled.
node-api-headers not conflicting anymore due to changed folder. it's make sense to keep versios of this port and node-api-headers unrelated because you may want to build an addon with node-api-headers version X and embed NodeJS with version Y, all in one project that shares a single manifest file.
@BillyONeal @FrankXie05 Reviews welcome


Update layout and scaling for desktop and mobile

Changes:

Add meta tag to allow scaling on mobile
Update opening paragraph size to scale correctly
Remove unused Angular references
Update layout to not be right-aligned on mobile

These changes center the layout on mobile/tablet devices, as well as allowing the screen to be collapsed down narrower on desktop due whilst keeping the correct layout.
 The desktop view is a little too wide for my taste now (I think good UX calls for slightly larger margins and padding?) but I'm happy enough as-is. Merging!


Logpoints feature request

Hello, would logpoints be possible with this extension, I use it in Löve2d development.

We have currently noone who activly adds features to this extension, but we would be happy to accept pull requests.


Allow Breakpoint#hit_condition=(nil)

Closes #739.
This MR modifies brkpt_set_hit_condition in ext/byebug/breakpoint.c to allow clearing a breakpoint's hit condition by setting it to nil. The documentation on the function indicates this should be possible, but passing nil will raise an exception, and no code path in the function will set the condition to HIT_COND_NONE.

Thanks @firelizzard18! Is there any user facing command to actually unset this?

Actually I now see from your issue and hit_condition is not really exposed and can only be used programamtically. Any ideas on how to better expose it?
In any case, this looks good!

Any ideas on how to better expose it?

ConditionCommand could be modified to support hit conditions. Possibly:

cond[ition] [expr[ession]] <n>[ expr]
cond[ition] hit[count] <n>[ <op> value]

Implemented as:

Since the code in the extension it's already there, makes sense to add it. I like your proposal :+1:.


Make example.py language independent

Add it.22000 into README.md.
If you want you could include the Italian model in the next release (0.4), and edit Italian model link into README.md.


html meta data

Hello, i search how i can set meta data from vue 3 ssr project. Anybody know?
I found empty project "vite-plugin-meta": "^0.0.1"

I'm not sure your code details, here has a example, may it can help you out.
server.get('*', (req, res) => {
  const app = createSSRApp(App);
   const html = await renderer.renderToString(app)
   res.end(`<!DOCTYPE html>

  <meta charset="UTF-8">
  <link rel="icon" href="/favicon.ico" />
  ${meta} // add your meta at here
  <title>Vite App</title>

${html}

`)
})

yes, but i need set meta from vue template, in vue 2 i use vue-meta, but in vue 3 i don't know... need hook

Here has a workaround https://github.com/nuxt/vue-meta/issues/558#issuecomment-718823772, it should help you out.


DocumentPasteEditProvider events intercepted by keybindings

VS Code Version: 1.80.0
OS Version: Google Chrome: Version 114.0.5735.143

Steps to Reproduce:

Define a ctrl+v (cmd+v for mac) keybinding for an extension. with example command (e.g. paste.test)
define a command listener for the example command (paste.test), which executes editor.action.clipboardPasteAction to apply the provided paste
create a DocumentPasteEditProvider & attach provideDocumentPasteEdits with some additional logging
trigger paste (ctrl+v), and wait for any logging from the provideDocumentPasteEdits

Expected behavior:
provideDocumentPasteEdits creates a log, as the paste has run through
ActualBehavior:
the paste is consumed by the keybinding, and is not rethrown in the copyPasteController, which means it won't propagate to the provideDocumentPasteEdits.
This interference can also happen in between extensions (e.g. one extension having the keybinding and other having DocumentPasteEditProvider).
Suggestion:
Trigger the dom paste event on the editor.action.clipboardPasteAction in copyPasteController, on the inputTextArea.
As this problem might be applying as well to copy/cut, it worth to safeguard both of those events in this way.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.80.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Please share a minimal example extension which demonstrates the issue

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Gilanyym

I'm guessing you didn't want to submit this. I'll close this PR

I'm guessing you didn't want to submit this. I'll close this PR


[DEM-863] basis gates added

Added S, Sdag, T, Tdag, SWAP and the binary controlled versions of these gates:

to the circuit parser
to the basis_gates configuration list
to the unit tests.

Coverage remained the same at 100.0% when pulling 80a0f2f7592b0cd5e0b94b5f86f8035df0b70670 on feature/dem-863/basis_gates into 7d9f0f26198e88fe564ef97981ca9d792815148d on dev.

Coverage remained the same at 100.0% when pulling 80a0f2f7592b0cd5e0b94b5f86f8035df0b70670 on feature/dem-863/basis_gates into 7d9f0f26198e88fe564ef97981ca9d792815148d on dev.


Adjust logic when finding approx matches for model or test matching

resolves # https://github.com/dbt-labs/dbt-core/issues/3835

Description

Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change

@jtcohen6 the failing flake 8 test seems unrelated (it's whitespace related on a file I'm not editing?) Is it okay to ignore?

I completely misread the error 🤦♀ . thanks @jtcohen6


RancherOS starts another default rancher/server:latest container on boot.

RancherOS Version: (ros os version) 1.2.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
AWS (from Marketplace) upgraded to 1.2.0
I have a Rancher/server container running on a non-default 4444 port with
docker run -d --restart=unless-stopped -p 4444:8080 -p 9345:9345 rancher/server --db-host xxxx-1.cluster-xxxx.xxxx-xxxx-1.rds.amazonaws.com --db-port 3306 --db-user xxxx --db-pass xxxxxxxx --db-name xxxx --advertise-address xxx.xxx.xxx.xxx
Every time I reboot an RancherOS I can see another rancher/server:latest container started on a default 8080 port. The docker ps -a + docker rm containerid doesn't help. I guess there's a setting somewhere to apply some default config & bring up the default rancher server container on boot?
Is there a way to prevent this?
What happens if I try to run my rancher server with external db (rds) on a default 8080 port? Will my container be replaced by this default one not pointing to my external db on boot?

If you change -p 8080:8080 to expose the HTTP port to a different port on the host, you will need to add --advertise-http-port <host_port> to the command.

@niusmallnan any comments on how to disable a default container starting after reboot?


Private class JsonParsers broke checks in third parties plugins

Hi, in the last commit you made the class JsonParsers private and this change breaks our opportunity to support json checks in plugins in the gatling way.
May we revert this changes?
affected repos:
https://github.com/galax-io/gatling-kafka-plugin/blob/132be41fb75652c9111452f4aaca4fec967cca8c/src/main/scala/org/galaxio/gatling/kafka/checks/KafkaCheckSupport.scala#L66
https://github.com/galax-io/gatling-amqp-plugin/blob/1accec7652e804f3fec8397b80ea3c0e01c9e43c/src/main/scala/org/galaxio/gatling/amqp/checks/AmqpCheckMaterializer.scala#L37
https://github.com/Amerousful/gatling-kafka/blob/4b79dcf7d14ff0b69d4940f4824c5c59aa06a9bc/src/main/scala/io/github/amerousful/kafka/check/KafkaCheckMaterializer.scala#L40

Hi,
My bad


ProfilePage now imports id from PAGE_IDS

Styled the navbar
Edited acceptance tests to be repeatable (commented out functionality testing of CreateProfile page)
Fixed bug in EditChallengeWidget (now imports withRouter from 'react-router-dom' instead of 'react-router')
Also had to re-install uniforms ¯_(ツ)_/¯
close #150

Had to merge main into branch Issue-150 to resolve minor merge conflict when approving PR.


Service component for internal dataset handling

Implement service component for managing forcing, configuration, and other category dataset handling.
This may need to be developed from the partially implementeddatarequestservice package, perhaps with some refactoring/renaming of things.

[x] #138
[x] #153
[x] #139
[x] Data service support for dataset catalog and querying/search for datasets based on matching DataDomain or sub-domain
[x] Data service support for checking if required data for a job is available
[x] Data service support for serving canonical forcing data (directly and/or indirectly; e.g., via object store dataset)
[x] Data service support for removing existing datasets

Work for this item is complete, but in the PR queue.  This is reflected in its Github Project status.  Once the launch_jobs/14_more_data_fixes branch is merged, the status can be changed from In Edge to Done.


Access keyserver.ubuntu.com on port 80

This resolves https://github.com/bflad/chef-docker/issues/264

Those Travis errors already exist on trunk, which forked a few minutes before submitting my pull request.

So I'm not super convinced that port 80 should be the default. I think it would be better to make a note in the README about this and to offer an example about how you would override this in your local environment.

I agree there @tduffield

@tduffield @rtrauntvein state reasons instead of opinions, this is a good workaround for users behind restrictive firewalls and should cause no-harm to everyone else.

@Sauraus if you rebase this PR on master and Travis passes I'll merge it in. Given that Docker itself uses port 80 in it's installation procedures I no longer see a reason to enforce the default.

@tduffield rebased and recommitted.


Hacktoberfest TODO: In need of 5 unique Science Fiction Quotes for API (96-100)

In Need of 5 Unique Science Fiction Quotes ids 96-100
Quotes MUST be from science fiction works (books or movies)
Quotes CANNOT be from a random celebrity or scientist that was interviewed
Quotes CANNOT already exist in the list (MUST be UNIQUE)
Do choose your favorite quotes if they meet the above requirements
Be sure to make your own branch
Add Quotes to quotes.json file in the /public directory
Make sure the quotes correspond with the id's that match the issue (96-100)
See that the fields match the example below
Submit a Pull Request when done
Exmaple
{
"id": 96,
"name": "Character speaking or narrator",
"line": "Your Quote",
"source": "Name of Book or Movie"
},

! Be sure to use the ids corresponding to the issue even if earlier quotes are not yet submitted.

I want to help on this

Great! I'll assign it to you!

@JWW127
This issue was taken care  of in #6
Please review it.

I want to contribute


Update any screenshots and descriptions in your README that are outdated

https://github.com/UBC-MDS/DSCI-532_2024_11_spotify-popularity/issues/77


[curl] Add http3 + remove ssl + openssl default ssl + remove other ssl/tls backend features.

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

@BillyONeal Do you want me to remove schannel and other ssl backend feature as well?

i.e. changing windows and osx backend to openssl.
Backend comparision: https://curl.se/docs/ssl-compared.html

no automatic CRL
no native cert check
extra deployment burden

alll for experimental http3 support.

i.e. changing windows and osx backend to openssl. Backend comparision: https://curl.se/docs/ssl-compared.html

no automatic CRL
no native cert check
extra deployment burden

alll for experimental http3 support.

You can enable native cert check, also for openssl. I wanted to enable it by default. I can make a patch for that.

i.e. changing windows and osx backend to openssl. Backend comparision: https://curl.se/docs/ssl-compared.html

no automatic CRL
no native cert check
extra deployment burden

alll for experimental http3 support.

Is this PR, or http3 with restriction, or without http3.

Do you want me to remove schannel and other ssl backend features as well?

As long as other backends exist, you have multi-ssl. And cannot have http3.

Do you want me to remove schannel and other ssl backend features as well?

As long as other backends exist, you have multi-ssl. And cannot have http3.

As you wish.

Correct, the expectation was that on osx | ios, the TLS backend selected is sectransp, on (windows & !uwp) | mingw the backend selected, and openssl selected otherwise.
Does http3 support only work with openssl?

This document write down all the options for curl with http3.
https://curl.se/docs/http3.html

This document write down all the options for curl with http3. https://curl.se/docs/http3.html

Hmmm... that's unfortunate. Adding some maintainers of https://github.com/microsoft/msquic
@nibanks @rzikm @csujedihy Do we have guidance for how normal Windows folks should get to http3 that complies with machine policy?

:sigh: I'm sorry for making the suggestion to do this, I didn't realize that removing the TLS features would make the platform default TLS backends non functional. I'm no longer sure this is the correct tradeoff. I asked some Windows folks about their thoughts...

@BillyONeal Don't be sorry, These PRs for that we check, test and learn. I am happy that we check all the options for http3.
My original offer to this PR is that openssl will check native certificate by default, include windows.
Then you can compile curl tool and test the new http3 connection.
I will make another commit later, with the command to test the curl http3 connection on windows (or any other os).

@BillyONeal I added the feature ca-native. also add it by default.
On windows you can try:
vcpkg install curl[tool,http3]
cd installed\x64-windows\tools\curl
curl --http3 https://curl.se/ -I

Try and let me know what do you think.
We can also go back to my previous PR that is on draft: #37146
Or if there is other option.
Also we can wait for maintainers of msquic for their respond.

Closing this as per https://github.com/microsoft/vcpkg/pull/37146#issuecomment-2026153067 ; sorry our misunderstanding sent you on this path :/


Pupils at expected standards

transformation and scripts change to

datasets.json
editions
versions

@bailed22 - I'll go into this in more detail tomorrow, but there's a test failing. It's not displaying correctly for some reason but the issue is the "desciption" in your version is too long. It can only be a maximum of 500 characters. There's also a loaf of Markdown in it and their shouldn't be. so you need to.

(a) remove the markdown
(b) if "make data" still fails, you'll need to shorten the description a bit to get it under 500 characters.

Hi Mike,
Thanks for this update
On Thu, 28 Dec 2023 at 10:17, Michael Adams @.***>
wrote:

@bailed22 https://github.com/bailed22 - I'll go into this in more
detail tomorrow, but there's a test failing. It's not displaying correctly
for some reason but the issue is the "desciption" in your version is too
long. It can only be a maximum of 500 characters. There's also a loaf of
Markdown in it and their shouldn't be. so you need to.

(a) remove the markdown
(b) if "make data" still fails, you'll need to shorten the
description a bit to get it under 500 characters.

—
Reply to this email directly, view it on GitHub
https://github.com/GSS-Cogs/idpd-api-poc/pull/176#issuecomment-1871026212,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWZSEUEBDYSKQZFYCMYFQNTYLVBL7AVCNFSM6AAAAABAHUNESKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZRGAZDMMRRGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


regeneratorRuntime is not defined in build output

Attempting packemon for a project. Its building the project fast without errors. But the output contains references to regeneratorRuntime which is not in scope. Checking this SO question it says the @babel/plugin-transform-runtime plugin should be used.. but I am not sure how to add that as packemon uses its internal babel configuration? Is there a way to extend it / add a plugin for it?
You can reproduce it by cloning the fix-web-api-issues branch here. Running node lib/bin.js should not throw.
Thanks 😁

That's odd since node platform enforces async/await always. Will take a look!

That's odd since node platform enforces async/await always. Will take a look!

Ok so Packemon has this feature where if multiple platforms (web/node) all write to lib, then it "merges" them to be compatible. What's happening is that node platform is actually being compiled for the browser, which is resulting in the regenerator runtime coming through.
I'll have to think of a way to improve this further.

Ok so Packemon has this feature where if multiple platforms (web/node) all write to lib, then it "merges" them to be compatible. What's happening is that node platform is actually being compiled for the browser, which is resulting in the regenerator runtime coming through.
I'll have to think of a way to improve this further.

Also, you seem to be using generators, which I have not accounted for. That's also the other reason why it's pulled in.
I currently convert async/await to promises, but have no way to handle generators. Will dig into.

Also, you seem to be using generators, which I have not accounted for. That's also the other reason why it's pulled in.
I currently convert async/await to promises, but have no way to handle generators. Will dig into.

Sounds complex! Thanks for taking a look. I can't remember using generators in the project, I may refactor those out to get it working.

Sounds complex! Thanks for taking a look. I can't remember using generators in the project, I may refactor those out to get it working.

No worries, adding support https://github.com/milesj/packemon/pull/22

No worries, adding support https://github.com/milesj/packemon/pull/22

@kaleidawave Released v0.10, can you give it a shot? You'll need to update your config to the following as there is more validation.
  "packemon": [
    {
      "inputs": {
        "index": "src/node.ts",
        "bin": "src/cli.ts"
      },
      "platform": "node"
    },
    {
      "inputs": {
        "web": "src/web.ts"
      },
      "platform": "browser",
      "support": "current"
    }
  ],

@kaleidawave Released v0.10, can you give it a shot? You'll need to update your config to the following as there is more validation.
  "packemon": [
    {
      "inputs": {
        "index": "src/node.ts",
        "bin": "src/cli.ts"
      },
      "platform": "node"
    },
    {
      "inputs": {
        "web": "src/web.ts"
      },
      "platform": "browser",
      "support": "current"
    }
  ],

Awesome, the node binary is working now! (and from v0.9 to v0.10 the compilation time has gone from 40s to 20s which is also great 👍)
Trying out esm/web.js now and having some issues:
First of all it does not like using the nodejs path module in the source: #24
Secondly seeing regeneratorRuntime in the web output without it being bundled / imported. I don't know a lot about regeneratorRuntime and why it is needed but at the moment it breaks doing import x from "./esm/web.js" as it can't read mark of undefined.
Once these hitches are fixed then it should be all working !!

Awesome, the node binary is working now! (and from v0.9 to v0.10 the compilation time has gone from 40s to 20s which is also great 👍)
Trying out esm/web.js now and having some issues:
First of all it does not like using the nodejs path module in the source: #24
Secondly seeing regeneratorRuntime in the web output without it being bundled / imported. I don't know a lot about regeneratorRuntime and why it is needed but at the moment it breaks doing import x from "./esm/web.js" as it can't read mark of undefined.
Once these hitches are fixed then it should be all working !!

I'll look into the node polyfills piece.
As for the runtime, you would need to add the @babel/runtime dep to your project, since it requires it. https://packemon.dev/docs/setup#transforming-generators

I'll look into the node polyfills piece.
As for the runtime, you would need to add the @babel/runtime dep to your project, since it requires it. https://packemon.dev/docs/setup#transforming-generators

Going to close this since the initial issue is fixed.

Going to close this since the initial issue is fixed.

Awesome thank you very much! BUT before this is closed I'll double check the web build is working with @babel/runtime, will check this afternoon

Awesome thank you very much! BUT before this is closed I'll double check the web build is working with @babel/runtime, will check this afternoon

Okay think I have got path working for different contexts. In terms of the regeneratorRuntime thing I am still a little stuck:
I installed regenerator-runtime and added import "regenerator-runtime/runtime.js"; to the top of the web entry point but am still getting this as the web output:
// Generated with Packemon: https://packemon.dev
// Platform: browser, Support: current, Format: lib
'use strict';

var _this3 = this;

function _typeof(obj) { ... }

var _marked = /*#__PURE__*/regeneratorRuntime.mark(variableReferenceWalker),
    _marked2 = /*#__PURE__*/regeneratorRuntime.mark(filesInFolder);

...

But this does not work through importing straight in to a browser as regeneratorRuntime is not defined at all before that part. I don't know if the build stripped out and did not bundle the import "regenerator-runtime/runtime.js"; part?? I am not really familiar with the babel ecosystem so am a little stuck ..?

Okay think I have got path working for different contexts. In terms of the regeneratorRuntime thing I am still a little stuck:
I installed regenerator-runtime and added import "regenerator-runtime/runtime.js"; to the top of the web entry point but am still getting this as the web output:
// Generated with Packemon: https://packemon.dev
// Platform: browser, Support: current, Format: lib
'use strict';

var _this3 = this;

function _typeof(obj) { ... }

var _marked = /*#__PURE__*/regeneratorRuntime.mark(variableReferenceWalker),
    _marked2 = /*#__PURE__*/regeneratorRuntime.mark(filesInFolder);

...

But this does not work through importing straight in to a browser as regeneratorRuntime is not defined at all before that part. I don't know if the build stripped out and did not bundle the import "regenerator-runtime/runtime.js"; part?? I am not really familiar with the babel ecosystem so am a little stuck ..?

Hmm, okay I was trying to reproduce the issue on replit and its working as expected there lol. Will check again tomorrow, probably a issue with my packemon config

Hmm, okay I was trying to reproduce the issue on replit and its working as expected there lol. Will check again tomorrow, probably a issue with my packemon config

@kaleidawave Have you tried installing the @babel/runtime dep? The babel config should be transforming the generators to:
var _regenerator = require("@babel/runtime/regenerator");

var _regenerator2 = _interopRequireDefault(_regenerator);

function _interopRequireDefault(obj) {
  return obj && obj.__esModule ? obj : { default: obj };
}

var _marked = [foo].map(_regenerator2.default.mark);

But to verify, this is for web platform only? Not for node yeah?

@kaleidawave Have you tried installing the @babel/runtime dep? The babel config should be transforming the generators to:
var _regenerator = require("@babel/runtime/regenerator");

var _regenerator2 = _interopRequireDefault(_regenerator);

function _interopRequireDefault(obj) {
  return obj && obj.__esModule ? obj : { default: obj };
}

var _marked = [foo].map(_regenerator2.default.mark);

But to verify, this is for web platform only? Not for node yeah?

I tested your branch and I don't see the word regenerator in any of the built files. Did you resolve it?

I tested your branch and I don't see the word regenerator in any of the built files. Did you resolve it?

Yep, ending up refactoring out the generators rather than dealing with babel. Project is now compiling and packemon is working really well! Issue can be closed

Yep, ending up refactoring out the generators rather than dealing with babel. Project is now compiling and packemon is working really well! Issue can be closed

Awesome, glad to hear!

Awesome, glad to hear!


Fix minor typos in xpanes and README.md

I ran a typo checker in the repo and changed corrected the typos accordingly.
Cheers.

Thank you!


How to validated row count between GS(csv file) and BQ(Table) using python code - Google Cloud

I have a csv file in google storage, Have loaded that csv file to BigQuery Table before loading into BQ table i have to validate to row count should match andavoid  duplicate row insertion,

This question is not related to init actions. But does this tutorial help? It teaches how to read files in GCS. Also check Spark tutorials on how to read CSV files.


Can't connect to Scaleway Object Storage (S3) for backups

Hi there,
I'm trying to use Scaleway Object Storage as my S3 backup, but I keep getting some strange errors.
I've Followed the documentations about Minio and the result is this:
I've created a secret called scaleway-secret, like this:
apiVersion: v1
kind: Secret
metadata:
  name: scaleway-secret
  namespace: longhorn-system
type: Opaque
data:
  AWS_ACCESS_KEY_ID: xxxx
  AWS_SECRET_ACCESS_KEY: xxxx
  AWS_ENDPOINTS: aHR0cHM6Ly9zMy5ubC1hbXMuc2N3LmNsb3Vk
  AWS_REGION: bmwtYW1z

which basically is the base64 to my configurations:
AWS_ACCESS_KEY_ID: xxxxx
AWS_SECRET_ACCESS_KEY: xxxxx
AWS_REGION: nl-ams
AWS_ENDPOINTS: https://s3.nl-ams.scw.cloud

the keys were altered to preserve security

and with this secret created, I gave longhorn the following configs:

But when I click on the Backup menu it returns me this error:
error listing backups: error listing backup volumes: Failed to execute: /var/lib/rancher/longhorn/engine-binaries/rancher-longhorn-engine-v0.4.0/longhorn [backup ls --volume-only s3://bucket-name@nl-ams/], output time="2019-03-06T18:53:59Z" level=error msg="{\n\n}" pkg=s3 time="2019-03-06T18:53:59Z" level=error msg="Fail to list s3: AWS Error: InvalidURI Couldn't parse the specified URI. <nil>\n400 \n" pkg=s3 time="2019-03-06T18:53:59Z" level=error msg="AWS Error: InvalidURI Couldn't parse the specified URI. <nil>\n400 \n" AWS Error: InvalidURI Couldn't parse the specified URI. <nil> 400 , error exit status 1

All configurations seems to be in order, I've even tried to take https off from the AWS_ENDPOINTS, but still got the same error.
Any ideas?

Can you try s3://bucket-name@us-east-1/ ? I am not familiar with Scaleway but we're using standard AWS library to connect, so nl-ams in the URI may not be recognized by AWS.

tryied,
got this:
AWS Error: AuthorizationHeaderMalformed The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'nl-ams' <nil> 400 , error exit status 1

nl-ams is the region in scaleway s3 access.

thanks @yasker
will wait for further actions on this.

@diegodorgam is there a way we can get an access key/secret key pair for debugging purpose? You can contact me privately using the email listed on my profile.

@diegodorgam Can you try if s3://bucket-name@nl-ams:/ works?

@yasker s3://bucket-name@nl-ams/longhorn/ it does not work, i tried it, we really need to fix this, we need it in our company.

@roonie007 Sorry we don't have access to Scaleway Object Storage. If it's possible, can you set up a test bucket for us and provide us with credentials so we can test and fix this? You can email the setup and credentials to<EMAIL_ADDRESS>

Yes I can, but the problem is that the same keys for the S3 gives you Full control over our account. since it's a support mail, many people can see and use the keys.
I can give them specifically to you, at least we know who is using them, is this ok for you ? or you can easily create an account and they will give you 500$ Credits .

@roonie007 Giving your original key to us wouldn't be a good idea if you cannot create another account/key pair. We can try to create an throwaway account instead if it's in fact free to do so.

You have to signup using this Input

@yasker Let me know if you need anything else.

@roonie007 It seems they require a mobile number and a credit card, which makes it hard for us to do. I've sent an email to<EMAIL_ADDRESS>to see if we can get a test account to help with this issue.

@yasker okay, keep me updated, but i know they are super active on their slack : https://slack.online.net/ , and you can lookup for these 2 channels :

#object-storage
#k8s

@yasker , is there any news about the progress of this bug ?

@roonie007 I've reached out to them and Remy Leone replied. But they still require a credit card to open an account. This is just before the KubeCon last month, and I have no update since then.
I will try to follow up again.

👋
I've just tested a basic installation of longhorn to test the S3 integration, it works.
apiVersion: v1
kind: Secret
metadata:
  name: scw-secret
  namespace: longhorn-system
type: Opaque
data:
  AWS_ACCESS_KEY_ID: XXX
  AWS_SECRET_ACCESS_KEY: XXX
  AWS_ENDPOINTS: aHR0cHM6Ly9zMy5mci1wYXIuc2N3LmNsb3Vk
  AWS_REGION: ZnItcGFy

aws s3 --profile par ls --recursive s3://zobity
2019-12-18 11:17:27        264 backupstore/volumes/10/e0/toto/backups/backup_backup-a0b7093f6e1c42b4.cfg
2019-12-18 11:17:27        171 backupstore/volumes/10/e0/toto/volume.cfg

backup target : s3://zobity@fr-par/
credential secret : scw-secret

I did this on the Paris region, but it should be the same for nl-ams.
The bucket has to be created in Scaleway's S3. Are you sure the bucket named bucket-name belongs to you ?

Thanks @newtoncorp ! Feel free to reopen the issue if it still doesn't work.


Fix grabbable struct input conflict

Currently when multiple grabbables are close, they each will see the input given to them and think they are being grabbed before the capturing of the input method happens the next frame. In protostar this causes massive issues.

Fixed by 7e751f3c322d0ed1112826f0b1506964035046bd


ARTEMIS-3901 Fix artemis perf client --durable fails on exception

https://issues.apache.org/jira/browse/ARTEMIS-3901

I added a tweak and merged it


No styles for list disks/circles on a dark background

Hey! I like your library a lot. But I noticed a little problem (at least for me)
Is your feature request related to a problem? Please describe.

List disks don't have an option to be placed on a dark bg, cause they are always dark.
Describe the solution you'd like

Please, add white disk lists :)
Describe alternatives you've considered

Additional context

Hello @ellenripley4.
I think this is a duplicated from #395 which was fixed on #396 in our develop branch, and will be available in the next release.
Please, take a look and if you have any questions or additional suggestions, just let me know.
Thank you.

Thanks @guastallaigor for pointing this out!


Finale needs a config/change to poll armor less often.

I can't find where it was called but somewhere the time for how often it updates durabilities is hard coded to a specific number of ticks or something and it's too often https://github.com/CivMC/Finale/blob/master/paper/src/main/java/com/github/maxopoly/finale/overlay/ScoreboardHUD.java

Wingzero54 - 2022

The issue with this if I remember rightly is if we dont update it every x ticks, the scoreboard will disappear, surely there is a work around for this?

https://jd.papermc.io/paper/1.18/org/bukkit/scoreboard/Scoreboard.html
Official documentation says no limit except garbage collection apparently, and CivScoreBoard doesnt implement a timer or something. So... I guess we need to test this. Comment on the PR please. https://github.com/CivMC/Finale/pull/18

https://github.com/CivMC/Finale/pull/18
Related PR


fix union type

Coverage decreased (-0.3%) to 95.707% when pulling eda4a37721bf8a61ab6402bb549cd68e5eb1867c on actually_fix_union_type into b1b76f109f30c2a6d8490af6b5261617a6edbc6d on master.

Coverage increased (+0.4%) to 96.422% when pulling 59df7709146b1a630033b8bb88ee2a4fe44cc452 on actually_fix_union_type into b1b76f109f30c2a6d8490af6b5261617a6edbc6d on master.


Minor: doc IMDB in benchmark README

Which issue does this PR close?

Closes #.
Rationale for this change
Recently @doupache and @austin362667 added a great IMDB benchmark, this PR wants to include it in benchmarks/README.md

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

+1 LGTM.
Thanks, @2010YOUY01, for the documentation.
Austin and I would like to add more documentation on which scenarios are most suitable for the JOB.


Getting started with Office 365 CAS

[Enter feedback here]
Please provide a similar page for getting started with the O365 CAS license
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8d3a8799-0915-2446-b772-cf5e3c80a238
Version Independent ID: 31f10a22-3c95-5ebe-622d-7431c5cb76f1
Content: Deploy Cloud App Security
Content Source: CloudAppSecurityDocs/getting-started-with-cloud-app-security.md
Service: cloud-app-security
GitHub Login: @shsagir
Microsoft Alias: shsagir

@DeanGross Thanks so much for taking the time to leave us your comment on our documentation. We're researching your issue to update the page based on your suggestions. If relevant, changes will be made in the next possible publish.
We're closing this as an open issue for now, but feel free to continue to comment here as necessary. We appreciate your contribution to our community.

Please don't close this until the changes have been implemented


How to create recurring event

Version

Not using yet
Development Environment

Current Behavior

Hi, from the documentation, its a bit unclear if recurrence is supported. Does Toast Calendar provide ability to create/modify recurring events? If recurrence is supported, how will an end user be able to create recurring tasks?
// Write example code

Expected Behavior

I should be able to create/modify an event and provide end user with ability to set/unset recurrence.

@gomzygba
TUI Calendar does not generate schedule data for repetition.
However, if you set any value in the recurrence rule when you createSchedules  (for example, an appointment that allows you to create a recurrence schedule in the Back End API), the schedule data will have this recurrenceRule prop.
With this recurrenceRule, you can handle it where we store the actual schedule data(backend).

Hello there,
I realise this is closed, but can anyone indicate where to find some info on recurrenceRule? The only definition I have managed to find in the documentation is: The recurrence rule.
Thanks a lot for the great project!

@egill31
Dooray! which uses TOAST UI Calendar uses RFC5545 recurrence rule.

@dongsik-yoo Any plans on implementing recurring events in the future?

Hello there,
I realise this is closed, but can anyone indicate where to find some info on recurrenceRule? The only definition I have managed to find in the documentation is: The recurrence rule.
Thanks a lot for the great project!

Hi @egill31
Were you able to integrate recurrence rule with toast UI calendar?

Hello there,
I realise this is closed, but can anyone indicate where to find some info on recurrenceRule? The only definition I have managed to find in the documentation is: The recurrence rule.
Thanks a lot for the great project!

Hi @egill31
Were you able to integrate recurrence rule with toast UI calendar?


Added new unit: triple shot star tank

Created a new unit:  triple shot star tank. This new tank is star-shaped,  blue, and periodically shoots three consecutive bullets when firing.

Modefied code as requested.


Reflecting the case-insensitivity of http headers

I recently went on a really unfun yak-shaving expedition when I:

Added an endpoint that uses the PATCH http method
Added a flow that exercised it
Discovered that the standard java HttpURLConnection stuff just doesn't support that
Refactored to use the new HTTPClient stuff in java 11
Found that HTTPHeaders only reports lower-case header names, even though we're confident that the service returns mixed-case. This breaks both the chunked transfer-encoding stuff that the HttpMsg types do, and required a bunch of tedious test-data updates.

HTTPHeaders's casing behaviour is the correct position, so we're going to adapt to that.

test?


amulet-map-editor: init at 0.10.37

Closes #201016
Got it to work for a brief moment before somehow it just starts to SIGBUS everywhere. Needs further investigation/reproduction

Things done

Built on platform(s)

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.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.

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

Does not build with the new default numpy 2.x. Tried updating one of the packages but requires more work. Maybe just use numpy_1 everywhere.
diff --git a/pkgs/development/python-modules/amulet-nbt/default.nix b/pkgs/development/python-modules/amulet-nbt/default.nix
index b5dd9de77247..ffdac00282b1 100644
--- a/pkgs/development/python-modules/amulet-nbt/default.nix
+++ b/pkgs/development/python-modules/amulet-nbt/default.nix
@@ -5,6 +5,8 @@
   pythonOlder,

   # build-system
+  cmake,
+  pybind11,
   setuptools,
   wheel,
   versioneer,
@@ -23,7 +25,7 @@
   nix-update-script,
 }:
 let
-  version = "2.1.3";
+  version = "4.0.0a10";
 in
 buildPythonPackage {
   pname = "amulet-nbt";
@@ -34,21 +36,28 @@ buildPythonPackage {
     owner = "Amulet-Team";
     repo = "Amulet-NBT";
     tag = version;
-    hash = "sha256-ucN/CFPYWEPPiqrK9v2VZ1l5s2jf0N0tNuxpYoTZQ4s=";
+    hash = "sha256-xTlgfSNTfU4zhqJwKJW226OSWOgVKwMAEgrL8VBUu68=";
   };

-  disabled = pythonOlder "3.9";
+  disabled = pythonOlder "3.11";

   postPatch = ''
-    # FIXME: Drop for 4.x
     substituteInPlace pyproject.toml \
-      --replace-fail 'versioneer-518' 'versioneer'
-
+      --replace-fail "pybind11[global]" "pybind11" \
+      --replace-fail '"amulet-compiler-target == 1.0",' ""
+    # FIXME: Drop for 4.x
     substituteInPlace setup.py \
       --replace-fail "versioneer.get_version()" "'${version}'"
   '';

+  dontUseCmakeConfigure = true;
+
+  nativeBuildInputs = [
+    cmake
+  ];
+
   build-system = [
+    pybind11
     setuptools
     wheel
     cython
@@ -77,14 +86,6 @@ buildPythonPackage {

   nativeCheckInputs = [ pytestCheckHook ];

-  # Source files interfere with tests :(
-  preCheck = ''
-    rm -r amulet_nbt
-  '';
-
-  # FIXME: Drop for 4.x, somehow it's just not implemented at all
-  disabledTestPaths = [ "tests/base_type_test.py" ];
-
   passthru.updateScript = nix-update-script { };

   meta = {

Yeah they probably need quite some time to migrate to NumPy 2... Will use NumPy 1 for now

Ack change to lib/licenses.nix.


Remove dead swing/graphviz code.

Untested and unreferenced, yet now results in the ghost java.awt
desktop window because for reasons unknown, the typelevel compiler
is loading the unused classes and transitively reaching something
in java.awt.* which loads Desktop.

Current coverage is 68.79% (diff: 100%)

Merging #1420 into master will increase coverage by 0.38%

@@             master      #1420   diff @@
==========================================
  Files           266        266
  Lines         13298      13223    -75
  Methods       13017      12944    -73
  Messages          0          0
  Branches        130        128     -2
==========================================
  Hits           9097       9097
+ Misses         4201       4126    -75
  Partials          0          0

Powered by Codecov. Last update e1fc666...1add270

@mossprescott This makes the java window go away, so I nominated you for review.

@mossprescott Any thoughts on this matter?

This stuff hasn't been used for a long time, so happy to see it go away. If it fixes the zombie UI thing, so much the better.


substitute/NERDtree/NERDTree

Hi!
I noticed a typo about NERDTree so I fixed.
I'm sorry.
Please check this fixing.

Thanks!

@chrisbra
I'm sorry...
Thank you!


Add GPIO Pins for SomfyiO Remote controll

Describe you new feature you'd like
I did my first Setup with a SomfyiO Remote and it works. Yay
I now also soldered the PROG and CH (Channel select) also to wires and would like to controll this from the ESP. Also it would be awesome to read the LED-Status. I also soldered some wires to the LED-input pin. Would love to get infos on the ESP about the selected channel (1, 2, 3, 4, 5=all LED)
Here another Project who does what i mean: https://github.com/robvdw2/somfy_situo5_io_esp32
my board

I'll have to give this some thought.  To do this the right way, there really would need to be a concept of setting up all the proper GPIO selections.  This is more of a configuration riddle than anything else.   The code to implement it would be very straightforward.

I don't understand what you mean with proper GPIO Selection concept. Is it not possible to use every Pin for everything? (Like now with the dropdown selector)
I guess you could add a "expert Mode" with a Warning and add These there.
If there is a concept even better
Can i help somehow?
(Amazing Work. Thanks. Also the HA-Integration💪🏻)
(What i was wondering:How can these connect to the esp without authentication?)

No I am referring to the UI flow.  Realistically there should be one definition in this case for the remote pins and each channel should be assigned to an individual motor.  If you look at the current structure, the shade definitions all revolve around a unique address.  In this instance there needs to be a page to define the IO-Remote then select the channels from it.

I understand what you mean and agree with you

No I am referring to the UI flow. Realistically there should be one definition in this case for the remote pins and each channel should be assigned to an individual motor. If you look at the current structure, the shade definitions all revolve around a unique address. In this instance there needs to be a page to define the IO-Remote then select the channels from it.

What have to admid: there are 1 channel (Situo 1 io) or 5 channel remotes (Situo 5 io) available. Maybe this can be selected somewhere to change available pin options

Hi there,
actually I'm currently working on a way to have temperarure control within my ESPomfy-enhousing to turn off electricity in case ot gets way too warm. First idea was to set up a separate ESP8266 just for that, which seems to be quite an overkill. As I'd need only one readout pin I thought I'd join this request and ask for some kind of expert mode where the use of a few of the free pins could be implemented.
I'm planning on using a DHT22 so besides a 3V3 and GND there would only be one readout pin that would be used.
As already mentioned in previous comments: AMAZING WORK and thanks so much for it! :)
All the best,
Anton


Add support for the AIX Big archive format

I haven't tested this code as I don't have a mainframe running AIX.
cc @ecnelises for https://rust-lang.zulipchat.com/#narrow/stream/233931-t-compiler.2Fmajor-changes/topic/New.20Tier-3.20target.20proposal.3A.20powerpc64-ibm.E2.80.A6.20compiler-team.23553
Fixes #1

Just verified this doesn't regress anything on Linux by applying
diff --git a/Cargo.lock b/Cargo.lock
index 5fddb408f8e..f66b4612c25 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -110,8 +110,7 @@ checksum = "c794e162a5eff65c72ef524dfe393eb923c354e350bb78b9c7383df13f3bc142"
 [[package]]
 name = "ar_archive_writer"
 version = "0.1.0"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "16f8a694a78724bb6f745ca5b987eada762c2b17c08d8344a20c633fb5d0f0fb"
+source = "git+https://github.com/rust-lang/ar_archive_writer?branch=aix_big#563333a1da68421b2fea1fb035da08feab628abe"
 dependencies = [
  "object 0.29.0",
 ]
diff --git a/compiler/rustc_codegen_ssa/Cargo.toml b/compiler/rustc_codegen_ssa/Cargo.toml
index a70650ab1c3..e5b0cee48c4 100644
--- a/compiler/rustc_codegen_ssa/Cargo.toml
+++ b/compiler/rustc_codegen_ssa/Cargo.toml
@@ -7,7 +7,7 @@ edition = "2021"
 test = false

 [dependencies]
-ar_archive_writer = "0.1.0"
+ar_archive_writer = { git = "https://github.com/rust-lang/ar_archive_writer", branch = "aix_big" }
 bitflags = "1.2.1"
 cc = "1.0.69"
 itertools = "0.10.1"
diff --git a/src/tools/tidy/src/extdeps.rs b/src/tools/tidy/src/extdeps.rs
index aad57cacbb4..de9c4241c3b 100644
--- a/src/tools/tidy/src/extdeps.rs
+++ b/src/tools/tidy/src/extdeps.rs
@@ -4,7 +4,10 @@
 use std::path::Path;

 /// List of allowed sources for packages.
-const ALLOWED_SOURCES: &[&str] = &["\"registry+https://github.com/rust-lang/crates.io-index\""];
+const ALLOWED_SOURCES: &[&str] = &[
+    "\"registry+https://github.com/rust-lang/crates.io-index\"",
+    "\"git+https://github.com/rust-lang/ar_archive_writer?branch=aix_big#563333a1da68421b2fea1fb035da08feab628abe\"",
+];

 /// Checks for external package sources. `root` is the path to the directory that contains the
 /// workspace `Cargo.toml`.

on top of https://github.com/rust-lang/rust/pull/97485.

Did a quick test on AIX using following code:
use std::fs::File;
use std::io::Read;
use ar_archive_writer::{write_archive_to_stream, ArchiveKind, NewArchiveMember};

fn main() {
    let mut file = File::create("tmp.a").unwrap();
    let mut first = Vec::new();
    let mut second = Vec::new();
    let mut first_file = File::open("first.o").expect("");
    let mut second_file = File::open("second.o").expect("");
    let _ = first_file.read_to_end(&mut first);
    let _ = second_file.read_to_end(&mut second);
    let _ = write_archive_to_stream(&mut file, &[
        NewArchiveMember {
            buf: Box::new(first),
            get_symbols: |_, _| Ok(false),
            member_name: String::from("first.o"),
            mtime: 0,
            uid: 500,
            gid: 1,
            perms: 0o644,
        },
        NewArchiveMember {
            buf: Box::new(second),
            get_symbols: |_, _| Ok(false),
            member_name: String::from("second.o"),
            mtime: 0,
            uid: 500,
            gid: 1,
            perms: 0o644,
        },
    ], true, ArchiveKind::AixBig, true, false);
}

However ar t tmp.a doesn't work as expected:
first.o
.
first.o
.
first.o
.
first.o
.
... (infinite loop)

I'm looking into it.

There seem to be two divergences with LLVM. The first is because I had to use {:<12o} instead of {:12o}. Currently investigating the other one.

Fixed both issues. This now results in identical archives as llvm-ar for empty object files.

Found another divergence when using actual object files.

Never mind. That was caused by using a dummy get_symbols instead of get_native_object_symbols.

I'm now fairly confident that this PR is correct.

Released as v0.1.1.

master works, thanks!

I've updated https://github.com/rust-lang/rust/pull/97485 with the new version of ar_archive_writer, but I haven't yet wired up aix big support. It should be a matter of adding a single arm to the match on sess.target.archive_format in compiler/rustc_codegen_ssa/src/back/archive.rs though. I prefer leaving it to the PR adding an AIX target to rustc though to keep the PR functionally identical to what we currently have.


ID3 submision

iphone7 ios 14.0.1
You can create a record with a random name and information without sending a document from the Notabene devolopment section.

rejected:ID3
reason:We cannot fully verify this submission. It looks like you are trying to submit ID3, however, it seems like there are no supporting details. What you mention in the comment is not related to the challenge. Notabele Development is supposed to have default credentials @Rookie23

rejected:ID3
reason:We cannot fully verify this submission. It looks like you are trying to submit ID3, however, it seems like there are no supporting details. What you mention in the comment is not related to the challenge. Notabele Development is supposed to have default credentials @Rookie23


logger:info only accepts type 'string'. Can support 'any'?

I will look into this.

PR https://github.com/ballerinalang/ballerina/pull/2840 addresses the issue hence closing.


remove duplicate 232 dk tier sets

Fixes #3278

when the duplicate tier were removed, the "of conquest" (232 tier) no longer counts for the "of triumph" (245/258) 4 set bonus


Updating kube-state-metrics builder & base images to be consistent with ART

Updating kube-state-metrics builder & base images to be consistent with ART
Reconciling with https://github.com/openshift/ocp-build-data/tree/f66c03011773dc3755ad874fc691be612914d65f/images/kube-state-metrics.yml
If you have any questions about this pull request, please reach out to @art-team in the #aos-art coreos slack channel.
Depends on https://github.com/openshift/images/pull/44 . Allow it to merge and then run /test all on this PR.

/retest

/lgtm


Add a new MarkdownBlade driver.

This would be similar to the Markdown driver - parse out the front-matter and compile the Markdown.
The difference would be that it parses the content as Blade as well, passing through the current model instance. So you could do something like:
---
title: My Awesome Post
tags:
  - laravel
  - php
---

# {{ $this->title }}

@foreach($this->tags as $tag)
    <span>{{ $tag }}</span>
@endforeach

⚠ The only data being passed through to the Blade would be the current model, but this doesn't stop anybody editing the file from using dangerous elements such as database queries etc, I'd generally recommend against using this driver when editing content via a GUI / CRUD form. If you want to enable that, use the regular Markdown driver and parse the content out yourself with shortcodes (or something similar).

It's worth noting that the Blade won't be stored in the database, Orbit would provide a CommonMark parser and do all the heavy lifting so that only HTML is being stored in the database.
It's down to the developer to ensure it's being safely output on the front-end, that's outside of Orbit's scope. (strip_tags or {{ }}).

I'm not going to go forward with this one right now.


Confused about build_production and .gitignore

Hi
I was getting this error when trying to push to Netlify:
failed during stage 'building site': Deploy directory 'build_production/' does not exist
After removing /build_production/ from my .gitignore file, the build was successful.
But when I look at the docs gitignore file & blog gitignore file I see that all of the build directories are ignored.
So which way is correct?
Thanks
Eric

What are your "Build command" and "Publish directory" in Netlify?

Hi
Thanks! Here's a screenshot from Netlify:

And here's my netlify.toml file:
[build]

  command = "npm run production"
  publish = "build_production/"
  PHP_VERSION = "7.2"

[context.staging]

  command = "npm run staging"
  publish = "build_staging"

[[redirects]]

  from = "/contact"
  to = "/hi"

Thanks!

Weird, yeah that setup seems identical to several of my own, and Jigsaw's actual docs site.
Can you also share your webpack.mix.js and try to reproduce this on a fresh install? Are you able to see anything in Netlify's logs that indicate why that folder isn't being created?

Hi
Thanks! Yeah, I think it's weird too. The other weird thing was that it was working fine for over a year. Then I did a big upgrade today (actually I ripped out all of the old code and replaced it with a brand new Jigsaw install) and that's when it started failing.
Now that I just said that... is it possible there's some residual "git" stuff in my repo that could be causing the issue? I ripped out everything from the old site except for the .git directory.
I've pasted in my webpack and Netlify log from one of my failed attempts below.
webpack.mix.js
const mix = require('laravel-mix');
require('laravel-mix-jigsaw');
const tailwindcss = require('tailwindcss')

mix.disableSuccessNotifications();
mix.setPublicPath('source/assets/build');

mix.jigsaw()
   .js('source/_assets/js/main.js', 'js')
   .options({
       processCssUrls: false,
       postCss: [
           tailwindcss('tailwind.config.js'),
       ]
   })
   .sass('source/_assets/sass/main.scss', 'css')
   .version();

Netlify Log
2:42:20 PM: Waiting for other deploys from your team to complete
2:42:58 PM: Build ready to start
2:43:00 PM: build-image version: 8e315e54bc4032a32e73290be556cde4f8348c12
2:43:00 PM: build-image tag: v2.8.2
2:43:00 PM: buildbot version: 45cd00068410d70db72c9672cdd014995488e12a
2:43:01 PM: Fetching cached dependencies
2:43:01 PM: Starting to download cache of 241.0MB
2:43:03 PM: Finished downloading cache in 2.399773303s
2:43:03 PM: Starting to extract cache
2:43:13 PM: Finished extracting cache in 9.819577979s
2:43:13 PM: Finished fetching cache in 12.302152265s
2:43:13 PM: Starting to prepare the repo for build
2:43:13 PM: Preparing Git Reference refs/heads/master
2:43:15 PM: Found netlify.toml. Overriding site configuration
2:43:15 PM: Different publish path detected, going to use the one specified in the toml file: 'build_production/' versus 'build_production' in the site
2:43:15 PM: Starting build script
2:43:15 PM: Installing dependencies
2:43:16 PM: Started restoring cached node version
2:43:18 PM: Finished restoring cached node version
2:43:19 PM: v8.17.0 is already installed.
2:43:20 PM: Now using node v8.17.0 (npm v6.13.4)
2:43:20 PM: Attempting ruby version 2.3.6, read from environment
2:43:21 PM: Using ruby version 2.3.6
2:43:21 PM: Using PHP version 7.2
2:43:21 PM: Started restoring cached node modules
2:43:21 PM: Finished restoring cached node modules
2:43:21 PM: Installing NPM modules using NPM version 6.13.4
2:43:42 PM: npm
2:43:42 PM:  WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack/node_modules/fsevents):
2:43:42 PM: npm
2:43:42 PM: WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:43:42 PM: npm
2:43:42 PM: WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2:43:42 PM: npm
2:43:42 PM: WARN
2:43:42 PM: notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2:43:42 PM: added 213 packages from 101 contributors, removed 307 packages, updated 319 packages and audited 1226 packages in 19.979s
2:43:43 PM: 31 packages are looking for funding
2:43:43 PM:   run `npm fund` for details
2:43:43 PM: found 4 vulnerabilities (3 low, 1 high)
2:43:43 PM:   run `npm audit fix` to fix them, or `npm audit` for details
2:43:43 PM: NPM modules installed
2:43:43 PM: Started restoring cached composer dependencies
2:43:43 PM: Finished restoring cached composer dependencies
2:43:45 PM: Loading composer repositories with package information
2:43:45 PM: Installing dependencies (including require-dev) from lock file
2:43:45 PM: Your requirements could not be resolved to an installable set of packages.
2:43:45 PM:   Problem 1
2:43:45 PM:     - The requested PHP extension ext-intl * is missing from your system. Install or enable PHP's intl extension.
2:43:45 PM: Started restoring cached go cache
2:43:47 PM: Finished restoring cached go cache
2:43:47 PM: Installing Go version 1.10
2:43:47 PM: unset GOOS;
2:43:47 PM: unset GOARCH;
2:43:47 PM: export GOROOT='/opt/buildhome/.gimme_cache/versions/go1.10.linux.amd64';
2:43:47 PM: export PATH="/opt/buildhome/.gimme_cache/versions/go1.10.linux.amd64/bin:${PATH}";
2:43:47 PM: go version >&2;
2:43:47 PM: export GIMME_ENV='/opt/buildhome/.gimme_cache/env/go1.10.linux.amd64.env';
2:43:47 PM: go version go1.10 linux/amd64
2:43:47 PM: Installing missing commands
2:43:47 PM: Verify run directory
2:43:47 PM: Executing user command: npm run production
2:43:48 PM: > @ production /opt/build/repo
2:43:48 PM: > cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --env=production --config=node_modules/laravel-mix/setup/webpack.config.js
2:43:50 PM: Could not find Jigsaw; please install it via Composer.
2:43:50 PM: Skipping functions preparation step: no functions directory set
2:43:50 PM: Caching artifacts
2:43:50 PM: Started saving node modules
2:43:50 PM: Finished saving node modules
2:43:50 PM: Started saving pip cache
2:43:50 PM: Finished saving pip cache
2:43:50 PM: Started saving emacs cask dependencies
2:43:50 PM: Finished saving emacs cask dependencies
2:43:50 PM: Started saving maven dependencies
2:43:50 PM: Finished saving maven dependencies
2:43:50 PM: Started saving boot dependencies
2:43:50 PM: Finished saving boot dependencies
2:43:50 PM: Started saving composer dependencies
2:43:50 PM: Finished saving composer dependencies
2:43:51 PM: Started saving go dependencies
2:43:52 PM: Finished saving go dependencies
2:43:52 PM: Build script success
2:43:52 PM: Failing build: Failed to build site
2:43:52 PM: failed during stage 'building site': Deploy directory 'build_production/' does not exist
2:43:52 PM: Finished processing build request in 52.056059746s

I just deployed my development repo (the repo I replaced all my original site files with yesterday) up to Netlify with no problems. The development repo did not include /build_production/ in my .gitignore file.
I'm at a loss as to why the other site is not deploying properly.

@EricBusch Jacob will likely be able to help you better than me, but I see this line:
Could not find Jigsaw; please install it via Composer.

Do you have Jigsaw in your composer.json? Or are you relying just on running it with it globally installed? If so, I'd add it to your composer.json so it's available to the NPM script.

Weird, I didn't even see that error. But what's even weirder is that I do have Jigsaw in my composer.json file. Here's the contents of that file.
{
  "require": {
    "tightenco/jigsaw": "^1.3",
    "samdark/sitemap": "^2.2",
    "ext-intl": "*",
    "ext-json": "*"
  },
  "autoload": {
    "psr-4": {
      "App\\Listeners\\": "listeners/"
    }
  }
}

And here's my package.json file in case I've messed up something in there...
{
    "private": true,
    "scripts": {
        "local": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --env=local --config=node_modules/laravel-mix/setup/webpack.config.js",
        "staging": "cross-env NODE_ENV=staging node_modules/webpack/bin/webpack.js --progress --hide-modules --env=staging --config=node_modules/laravel-mix/setup/webpack.config.js",
        "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --env=production --config=node_modules/laravel-mix/setup/webpack.config.js",
        "dev": "npm run local",
        "prod": "npm run production",
        "watch": "npm run local -- --watch"
    },
    "devDependencies": {
        "cross-env": "^3.2.3",
        "laravel-mix": "^4.0.0",
        "laravel-mix-jigsaw": "^1.1.0",
        "sass": "^1.15.2",
        "sass-loader": "^7.1.0",
        "vue-template-compiler": "^2.6.11"
    },
    "dependencies": {
        "@tailwindcss/typography": "^0.2.0",
        "@tailwindcss/ui": "^0.3.1",
        "alpinejs": "^2.4.1",
        "fuse.js": "^6.4.1",
        "tailwindcss": "^1.5.1"
    }
}

Okay, Composer is failing on ext-intl and doesn't even make it to installing tightenco/jigsaw. ext-intl was actually just recently added to Netlify's build images, so it should be installed, but I'm able to reproduce this now and it doesn't appear to be there. I'll follow up with them about that, in the meantime if you don't actually need ext-intl, remove that line from your composer.json and you should be good to go.

That was it! I removed the ext-intl package from my composer.json file and now were working again. My build_production folder is no longer being committed to Github,
Thanks for all your help! I really appreciate it!


docs ci: manually copy the files rather than use the postinstall hook

This PR has the following fixes:

[CI] uses a cp command rather than the postinstall hook of the target repository (docs) because it includes more logic (such as git submodules update which defeated the docs gh action)
[CLI docs] fixes the entrypoint to not use await import but good ol' require so oclif can generate the docs

Fixes celo-org/docs#1254


Pre-Publish: Update Title Dialog to match new visual style

Feature Description
Currently the Publish Flow shows a dialog when there is a missing title. Update it to reflect the new design language.

Alternatives Considered

Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Moved to backlog, while approved and QA'd this is on hold until the larger scope of re-design work is in play.

Moved to backlog, while approved and QA'd this is on hold until the larger scope of re-design work is in play.

This has been resolved with design system updates, moving to UAT


Address deprecations from persistence

Q
A

Type
bug

BC Break
no

Fixed issues
n/a

Summary
A backwards-compatibility layer has been added to persistence to help
consumers move to the new namespacing. It is based on class aliases,
which means the type declaration changes should not be a BC-break: types
are the same.
See doctrine/persistence#71
This means:

using the new namespaces
adding autoload calls for new types to types that may be extended and
use persistence types in type declarations of non-constructor methods,
so that signature compatibility is recognized by old versions of php.
More details on this at
https://dev.to/greg0ire/how-to-deprecate-a-type-in-php-48cf

The build fails because persistence requires php 7.1 . Could we drop php 7.0?

I think we can safely do that in 2.1 👍

:thinking: why not 2.0.4 ? Also, should we forbid persistence 1.4 and up on this branch? That way people don't get deprecations they cannot fix?

Oh this is targeting 1.3.x... Here we're still allowing 5.6 so no way we can bump to 7.1. I guess it'll deprecations from the common will be one more poke for folks to upgrade ODM.

why not 2.0.4 ?

PHP version can be bumped on a minor release, we even made a blog post about it :) https://www.doctrine-project.org/2017/07/25/php-7.1-requirement-and-composer.html

But… 2.0.x already requires 7.2, doesn't it?

Yeah, this is what happens when I'm replying in the night. I'm sorry @greg0ire you're right, we can totally include this in 2.0.4. I was confused by you saying we need to drop 7.0 and thought 2.0 is still supporting that version.

There! Got it to a mergeable state again :P

Thanks @greg0ire!


Sileo doesn’t work

I can’t fresh the source

This is a developer jailbreak, and there’s no tweak injection. Repos like Havoc aren’t updated for rootless either.


Normalize.min.css not found

When visiting a publicly shared note there is this error in developer tools:

Refused to apply style from 'https://.....com/assets/v0.90.12/libraries/normalize.min.css' because its MIME type ('application/json') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

it seems to come from this line in page.ejs:
https://github.com/zerebos/trilium.rocks/blob/2cdd2a0a543f0bced8284ca55bc94efadbc7c91f/src/templates/page.ejs#L9
Also see https://github.com/TriliumNext/Notes/issues/848
Host: TriliumNext v0.90.12 on PikaPods.com.

The fix for TriliumNext is to edit page.ejs and change that line to
    <link href="../<%= assetPath %>/node_modules/normalize.css/normalize.css" rel="stylesheet">

Hat tip to Eliandoran at https://github.com/orgs/TriliumNext/discussions/851#discussioncomment-11680326


Add Extra Arguments to Kaniko

Sometimes consumers of the library need to have an entrypoint to
add additional build arguments to kaniko. So, this defines an
environment variable you can add to manipulate the build args.
Signed-off-by: David Brown<EMAIL_ADDRESS>

Awesome. Thanks for contributing this. Looks very useful. Could you please add a little comment in the docs here about it too?
https://github.com/pnnl-miscscripts/gitlab-lib/blob/v1/gitlab-lib.yaml#L89-L94

Perfect. Thanks! :)