bug: char_buf matchArgs works not as expected

I created such a TracingPolicy:
apiVersion: cilium.io/v1alpha1
kind: TracingPolicy
metadata:
  name: http
spec:
  tracepoints:
  - args:
    - index: 5
      returnCopy: false
      type: fd
    - index: 6
      returnCopy: false
      sizeArgIndex: 8
      type: char_buf
    - index: 7
      returnCopy: false
      type: size_t
    event: sys_enter_write
    selectors:
    - matchArgs:
      - index: 6
        operator: Prefix
        values:
        - HTTP
    subsystem: syscalls
  - args:
    - index: 5
      returnCopy: false
      type: fd
    - index: 6
      returnCopy: false
      sizeArgIndex: 8
      type: char_buf
    - index: 7
      returnCopy: false
      type: size_t
    event: sys_enter_read
    selectors:
    - {}
    subsystem: syscalls

i expected filter the events of tracepoint sys_enter_write, match char_buf prefix is "HTTP". but all events of sys_enter_write are filtered out.
example：
the TracingPolicy without selectors
apiVersion: cilium.io/v1alpha1
kind: TracingPolicy
metadata:
  name: http
spec:
  tracepoints:
  - args:
    - index: 5
      returnCopy: false
      type: fd
    - index: 6
      returnCopy: false
      sizeArgIndex: 8
      type: char_buf
    - index: 7
      returnCopy: false
      type: size_t
    event: sys_enter_write
    subsystem: syscalls
  - args:
    - index: 5
      returnCopy: false
      type: fd
    - index: 6
      returnCopy: false
      sizeArgIndex: 8
      type: char_buf
    - index: 7
      returnCopy: false
      type: size_t
    event: sys_enter_read
    subsystem: syscalls

logs added at:
// Notify implements Listener.Notify.
func (pm *ProcessManager) Notify(event notify.Message) error {
	processedEvent := event.HandleMessage()
	if processedEvent != nil {
		js, _ := json.Marshal(processedEvent)
		if strings.Contains(string(js),"/data/code/main") &&
			(strings.Contains(string(js), "sys_enter_read") ||
				strings.Contains(string(js), "sys_enter_write")){
			fmt.Printf("print events: %s\n",js)
		}
		pm.NotifyListener(event, processedEvent)
	}
	return nil
}

after i send a http request, logs:
time="2022-12-02T11:26:19Z" level=info msg="tracing policy added" policy="{[] [{syscalls sys_enter_write [{5 fd 0 false} {6 char_buf 8 false} {7 size_t 0 false}] []} {syscalls sys_enter_read [{5 fd 0 false} {6 char_buf 8 false} {7 size_t 0 false}] [{[] [] [] [] [] [] [] [] []}]}]}"
time="2022-12-02T11:26:19Z" level=info msg="BTF file: using metadata file" metadata=/sys/kernel/btf/vmlinux
time="2022-12-02T11:26:19Z" level=info msg="Loading sensor" name=gtp-sensor-5
time="2022-12-02T11:26:19Z" level=info msg="Loading kernel version 5.4.119"
time="2022-12-02T11:26:19Z" level=info msg="tetragon, map loaded." map=fdinstall_map path=/sys/fs/bpf/tetragon/gtp-sensor-5-gtp-0-fdinstall_map sensor=gtp-sensor-5
time="2022-12-02T11:26:19Z" level=info msg="tetragon, map loaded." map=tp_calls path=/sys/fs/bpf/tetragon/gtp-sensor-5-gtp-0-tp_calls sensor=gtp-sensor-5
time="2022-12-02T11:26:19Z" level=info msg="tetragon, map loaded." map=filter_map path=/sys/fs/bpf/tetragon/gtp-sensor-5-gtp-0-filter_map sensor=gtp-sensor-5
time="2022-12-02T11:26:19Z" level=info msg="tetragon, map loaded." map=argfilter_maps path=/sys/fs/bpf/tetragon/gtp-sensor-5-gtp-0-argfilter_maps sensor=gtp-sensor-5
time="2022-12-02T11:26:20Z" level=info msg="tetragon, map loaded." map=fdinstall_map path=/sys/fs/bpf/tetragon/gtp-sensor-5-gtp-1-fdinstall_map sensor=gtp-sensor-5
time="2022-12-02T11:26:20Z" level=info msg="tetragon, map loaded." map=tp_calls path=/sys/fs/bpf/tetragon/gtp-sensor-5-gtp-1-tp_calls sensor=gtp-sensor-5
time="2022-12-02T11:26:20Z" level=info msg="tetragon, map loaded." map=filter_map path=/sys/fs/bpf/tetragon/gtp-sensor-5-gtp-1-filter_map sensor=gtp-sensor-5
time="2022-12-02T11:26:20Z" level=info msg="tetragon, map loaded." map=argfilter_maps path=/sys/fs/bpf/tetragon/gtp-sensor-5-gtp-1-argfilter_maps sensor=gtp-sensor-5
time="2022-12-02T11:26:20Z" level=info msg="Loading registered BPF probe" Program=/var/lib/tetragon/bpf_generic_tracepoint_v53.o Type=generic_tracepoint
time="2022-12-02T11:26:25Z" level=info msg="Loading registered BPF probe" Program=/var/lib/tetragon/bpf_generic_tracepoint_v53.o Type=generic_tracepoint
time="2022-12-02T11:26:32Z" level=info msg="Loaded BPF maps and events for sensor successfully" sensor=gtp-sensor-5
print events: {"process_tracepoint":{"process":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjExNDg1NDIzNDU3ODo2MjA=","pid":620,"uid":0,"cwd":"/data/code","binary":"/data/code/main","flags":"execve clone","start_time":"2022-12-02T11:27:08.164884979Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-886f69fd4-lqfx7","container":{"id":"containerd://7dfd2996a4ecba47f3052ddeff1fc4f3c296b83fc72d7bcb9721376c326c7633","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:27:08Z","pid":8},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"886f69fd4"}},"docker":"7dfd2996a4ecba47f3052ddeff1fc4f","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjExNDg0MTAzNzUwMDo2MDc=","refcnt":1},"parent":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjExNDg0MTAzNzUwMDo2MDc=","pid":607,"uid":0,"cwd":"/data/code","binary":"/bin/bash","arguments":"-c /data/tmp/bd_dockerfile_cmdcommands.sh","flags":"execve clone","start_time":"2022-12-02T11:27:08.151687938Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-886f69fd4-lqfx7","container":{"id":"containerd://7dfd2996a4ecba47f3052ddeff1fc4f3c296b83fc72d7bcb9721376c326c7633","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:27:08Z","pid":1},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"886f69fd4"}},"docker":"7dfd2996a4ecba47f3052ddeff1fc4f","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg1MzAwMDAwMDA6NDk4"},"subsys":"syscalls","event":"sys_enter_read","args":[{"size_arg":"7"},{"bytes_arg":"Q2hhckJ1ZkVycm9yUGFnZUZhdWx0"},{"size_arg":"4096"}]},"node_name":"eklet-subnet-bxgkfn1q","time":"2022-12-02T11:29:30.714468650Z"}
print events: {"process_tracepoint":{"process":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjExNDg1NDIzNDU3ODo2MjA=","pid":620,"uid":0,"cwd":"/data/code","binary":"/data/code/main","flags":"execve clone","start_time":"2022-12-02T11:27:08.164884979Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-886f69fd4-lqfx7","container":{"id":"containerd://7dfd2996a4ecba47f3052ddeff1fc4f3c296b83fc72d7bcb9721376c326c7633","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:27:08Z","pid":8},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"886f69fd4"}},"docker":"7dfd2996a4ecba47f3052ddeff1fc4f","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjExNDg0MTAzNzUwMDo2MDc=","refcnt":1},"parent":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjExNDg0MTAzNzUwMDo2MDc=","pid":607,"uid":0,"cwd":"/data/code","binary":"/bin/bash","arguments":"-c /data/tmp/bd_dockerfile_cmdcommands.sh","flags":"execve clone","start_time":"2022-12-02T11:27:08.151687938Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-886f69fd4-lqfx7","container":{"id":"containerd://7dfd2996a4ecba47f3052ddeff1fc4f3c296b83fc72d7bcb9721376c326c7633","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:27:08Z","pid":1},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"886f69fd4"}},"docker":"7dfd2996a4ecba47f3052ddeff1fc4f","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg1MzAwMDAwMDA6NDk4"},"subsys":"syscalls","event":"sys_enter_write","args":[{"size_arg":"7"},{"bytes_arg":"SFRUUC8xLjEgMjAwIE9LDQpDb250ZW50LVR5cGU6IGFwcGxpY2F0aW9uL2pzb247IGNoYXJzZXQ9dXRmLTgNCkRhdGU6IEZyaSwgMDIgRGVjIDIwMjIgMTE6Mjk6MzAgR01UDQpDb250ZW50LUxlbmd0aDogMzENCg0KeyJjb2RlIjoiMCIsIm1lc3NhZ2UiOiJIZWxsbyEifQ=="},{"size_arg":"154"}]},"node_name":"eklet-subnet-bxgkfn1q","time":"2022-12-02T11:29:30.714662232Z"}
print events: {"process_tracepoint":{"process":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjExNDg1NDIzNDU3ODo2MjA=","pid":620,"uid":0,"cwd":"/data/code","binary":"/data/code/main","flags":"execve clone","start_time":"2022-12-02T11:27:08.164884979Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-886f69fd4-lqfx7","container":{"id":"containerd://7dfd2996a4ecba47f3052ddeff1fc4f3c296b83fc72d7bcb9721376c326c7633","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:27:08Z","pid":8},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"886f69fd4"}},"docker":"7dfd2996a4ecba47f3052ddeff1fc4f","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjExNDg0MTAzNzUwMDo2MDc=","refcnt":1},"parent":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjExNDg0MTAzNzUwMDo2MDc=","pid":607,"uid":0,"cwd":"/data/code","binary":"/bin/bash","arguments":"-c /data/tmp/bd_dockerfile_cmdcommands.sh","flags":"execve clone","start_time":"2022-12-02T11:27:08.151687938Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-886f69fd4-lqfx7","container":{"id":"containerd://7dfd2996a4ecba47f3052ddeff1fc4f3c296b83fc72d7bcb9721376c326c7633","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:27:08Z","pid":1},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"886f69fd4"}},"docker":"7dfd2996a4ecba47f3052ddeff1fc4f","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg1MzAwMDAwMDA6NDk4"},"subsys":"syscalls","event":"sys_enter_read","args":[{"size_arg":"7"},{"bytes_arg":"R0VUIC9oZWxsbyBIVFRQLzEuMQ0KSG9zdDogZGN0ZXN0cHJvLnRldHJhZ29uLm9kcGNsZGV2LndvYS5jb20NCkNhY2hlLUNvbnRyb2w6IG1heC1hZ2U9MA0KVXBncmFkZS1JbnNlY3VyZS1SZXF1ZXN0czogMQ0KVXNlci1BZ2VudDogTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfNykgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzEwNy4wLjAuMCBTYWZhcmkvNTM3LjM2DQpBY2NlcHQ6IHRleHQvaHRtbCxhcHBsaWNhdGlvbi94aHRtbCt4bWwsYXBwbGljYXRpb24veG1sO3E9MC45LGltYWdlL2F2aWYsaW1hZ2Uvd2VicCxpbWFnZS9hcG5nLCovKjtxPTAuOCxhcHBsaWNhdGlvbi9zaWduZWQtZXhjaGFuZ2U7dj1iMztxPTAuOQ0KQWNjZXB0LUxhbmd1YWdlOiB6aC1DTix6aDtxPTAuOQ0KQ29va2llOiB4LWhvc3Qta2V5LWlkY2JhY2s9NDU4Y2E5OTIyY2NmODk5ZGMwODIxNmY2MjljYTJlMWUxZDQ5MWI3Ml9zOyB4LWhvc3Qta2V5LW9hYmFjaz00NThjYTk5MjJjY2Y4OTlkYzA4MjE2ZjYyOWNhMmUxZTFkNDkxYjcyX3M7IHgtaG9zdC1rZXktZnJvbnQ9NDU4Y2E5OTIyY2NmODk5ZGMwODIxNmY2MjljYTJlMWUxZDQ5MWI3Ml9zOyB4X2hvc3Rfa2V5PTQ1OGNhOTkyMmNjZjg5OWRjMDgyMTZmNjI5Y2EyZTFlMWQ0OTFiNzJfczsgeC1ob3N0LWtleS1uZ249NDU4Y2E5OTIyY2NmODk5ZGMwODIxNmY2MjljYTJlMWUxZDQ5MWI3Ml9zOyB4LXRvZmFwaS1ob3N0LWtleT0xN2U1MWIyY2Q3Yy04ZGRmMDNmYjYwZTcyNTUxYjFlZWFkM2NkZDgwNzQ2OTRkNTc1ODJkOyBEaWdnZXJUcmFjZUlkPTJkMDgxNjMwLTc4MGYtMTFlYy1hODBkLTk1ZWZlZjAyOGM1YjsgeF9ob3N0X2tleV9hY2Nlc3M9NDU4Y2E5OTIyY2NmODk5ZGMwODIxNmY2MjljYTJlMWUxZDQ5MWI3Ml9zOyB4LWltcC1ob3N0LWtleT0xN2U5YTNkOWYyOC1hMzI2YzkyYmVmNWRhMjI1MGI2ZDIyMjU5ZDgyN2EwMGJkNzZlMmJlOyB0X3VpZD1kZWNoZW5neXVhbjsgYmx1ZWtpbmdfbGFu"},{"size_arg":"4096"}]},"node_name":"eklet-subnet-bxgkfn1q","time":"2022-12-02T11:29:30.714733452Z"}

sys_enter_write char_buf :
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Date: Fri, 02 Dec 2022 11:29:30 GMT
Content-Length: 31

{"code":"0","message":"Hello!"}

after i add the selectors in, logs:
time="2022-12-02T11:43:48Z" level=info msg="tracing policy added" policy="{[] [{syscalls sys_enter_write [{5 fd 0 false} {6 char_buf 8 false} {7 size_t 0 false}] [{[] [{6 Prefix [HTTP]}] [] [] [] [] [] [] []}]} {syscalls sys_enter_read [{5 fd 0 false} {6 char_buf 8 false} {7 size_t 0 false}] [{[] [] [] [] [] [] [] [] []}]}]}"
time="2022-12-02T11:43:48Z" level=info msg="BTF file: using metadata file" metadata=/sys/kernel/btf/vmlinux
time="2022-12-02T11:43:48Z" level=info msg="Loading sensor" name=gtp-sensor-6
time="2022-12-02T11:43:48Z" level=info msg="Loading kernel version 5.4.119"
time="2022-12-02T11:43:48Z" level=info msg="tetragon, map loaded." map=fdinstall_map path=/sys/fs/bpf/tetragon/gtp-sensor-6-gtp-0-fdinstall_map sensor=gtp-sensor-6
time="2022-12-02T11:43:48Z" level=info msg="tetragon, map loaded." map=tp_calls path=/sys/fs/bpf/tetragon/gtp-sensor-6-gtp-0-tp_calls sensor=gtp-sensor-6
time="2022-12-02T11:43:48Z" level=info msg="tetragon, map loaded." map=filter_map path=/sys/fs/bpf/tetragon/gtp-sensor-6-gtp-0-filter_map sensor=gtp-sensor-6
time="2022-12-02T11:43:48Z" level=info msg="tetragon, map loaded." map=argfilter_maps path=/sys/fs/bpf/tetragon/gtp-sensor-6-gtp-0-argfilter_maps sensor=gtp-sensor-6
time="2022-12-02T11:43:48Z" level=info msg="tetragon, map loaded." map=fdinstall_map path=/sys/fs/bpf/tetragon/gtp-sensor-6-gtp-1-fdinstall_map sensor=gtp-sensor-6
time="2022-12-02T11:43:48Z" level=info msg="tetragon, map loaded." map=tp_calls path=/sys/fs/bpf/tetragon/gtp-sensor-6-gtp-1-tp_calls sensor=gtp-sensor-6
time="2022-12-02T11:43:48Z" level=info msg="tetragon, map loaded." map=filter_map path=/sys/fs/bpf/tetragon/gtp-sensor-6-gtp-1-filter_map sensor=gtp-sensor-6
time="2022-12-02T11:43:48Z" level=info msg="tetragon, map loaded." map=argfilter_maps path=/sys/fs/bpf/tetragon/gtp-sensor-6-gtp-1-argfilter_maps sensor=gtp-sensor-6
time="2022-12-02T11:43:48Z" level=info msg="Loading registered BPF probe" Program=/var/lib/tetragon/bpf_generic_tracepoint_v53.o Type=generic_tracepoint
time="2022-12-02T11:43:51Z" level=info msg="Loading registered BPF probe" Program=/var/lib/tetragon/bpf_generic_tracepoint_v53.o Type=generic_tracepoint
time="2022-12-02T11:43:55Z" level=info msg="Loaded BPF maps and events for sensor successfully" sensor=gtp-sensor-6
print events: {"process_tracepoint":{"process":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg5NDAwMDAwMDA6NTY3","pid":567,"uid":0,"cwd":"/data/code","binary":"/data/code/main","flags":"procFS auid","start_time":"2022-12-02T11:43:25.546661009Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-6f8b5fcfcd-c4dzd","container":{"id":"containerd://f71dd550bc6a99ad046a38bdd0be58348cd418295bce5356ffd1851defdab4f4","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:43:25Z","pid":7},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"6f8b5fcfcd"}},"docker":"f71dd550bc6a99ad046a38bdd0be583","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg3NjAwMDAwMDA6NTU0","refcnt":1},"parent":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg3NjAwMDAwMDA6NTU0","pid":554,"uid":0,"cwd":"/data/code","binary":"/usr/bin/bash","arguments":"-c /data/tmp/bd_dockerfile_cmdcommands.sh","flags":"procFS auid","start_time":"2022-12-02T11:43:25.366661344Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-6f8b5fcfcd-c4dzd","container":{"id":"containerd://f71dd550bc6a99ad046a38bdd0be58348cd418295bce5356ffd1851defdab4f4","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:43:25Z","pid":1},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"6f8b5fcfcd"}},"docker":"f71dd550bc6a99ad046a38bdd0be583","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjc1MzAwMDAwMDA6NDY0"},"subsys":"syscalls","event":"sys_enter_read","args":[{"size_arg":"7"},{"bytes_arg":"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"},{"size_arg":"4096"}]},"node_name":"eklet-subnet-bxgkfn1q","time":"2022-12-02T11:44:20.665990376Z"}
print events: {"process_tracepoint":{"process":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg5NDAwMDAwMDA6NTY3","pid":567,"uid":0,"cwd":"/data/code","binary":"/data/code/main","flags":"procFS auid","start_time":"2022-12-02T11:43:25.546661009Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-6f8b5fcfcd-c4dzd","container":{"id":"containerd://f71dd550bc6a99ad046a38bdd0be58348cd418295bce5356ffd1851defdab4f4","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:43:25Z","pid":7},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"6f8b5fcfcd"}},"docker":"f71dd550bc6a99ad046a38bdd0be583","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg3NjAwMDAwMDA6NTU0","refcnt":1},"parent":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg3NjAwMDAwMDA6NTU0","pid":554,"uid":0,"cwd":"/data/code","binary":"/usr/bin/bash","arguments":"-c /data/tmp/bd_dockerfile_cmdcommands.sh","flags":"procFS auid","start_time":"2022-12-02T11:43:25.366661344Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-6f8b5fcfcd-c4dzd","container":{"id":"containerd://f71dd550bc6a99ad046a38bdd0be58348cd418295bce5356ffd1851defdab4f4","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:43:25Z","pid":1},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"6f8b5fcfcd"}},"docker":"f71dd550bc6a99ad046a38bdd0be583","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjc1MzAwMDAwMDA6NDY0"},"subsys":"syscalls","event":"sys_enter_read","args":[{"size_arg":"7"},{"bytes_arg":"R0VUIC9oZWxsbyBIVFRQLzEuMQ0KSG9zdDogZGN0ZXN0cHJvLnRldHJhZ29uLm9kcGNsZGV2LndvYS5jb20NCkNhY2hlLUNvbnRyb2w6IG1heC1hZ2U9MA0KVXBncmFkZS1JbnNlY3VyZS1SZXF1ZXN0czogMQ0KVXNlci1BZ2VudDogTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfNykgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzEwNy4wLjAuMCBTYWZhcmkvNTM3LjM2DQpBY2NlcHQ6IHRleHQvaHRtbCxhcHBsaWNhdGlvbi94aHRtbCt4bWwsYXBwbGljYXRpb24veG1sO3E9MC45LGltYWdlL2F2aWYsaW1hZ2Uvd2VicCxpbWFnZS9hcG5nLCovKjtxPTAuOCxhcHBsaWNhdGlvbi9zaWduZWQtZXhjaGFuZ2U7dj1iMztxPTAuOQ0KQWNjZXB0LUxhbmd1YWdlOiB6aC1DTix6aDtxPTAuOQ0KQ29va2llOiB4LWhvc3Qta2V5LWlkY2JhY2s9NDU4Y2E5OTIyY2NmODk5ZGMwODIxNmY2MjljYTJlMWUxZDQ5MWI3Ml9zOyB4LWhvc3Qta2V5LW9hYmFjaz00NThjYTk5MjJjY2Y4OTlkYzA4MjE2ZjYyOWNhMmUxZTFkNDkxYjcyX3M7IHgtaG9zdC1rZXktZnJvbnQ9NDU4Y2E5OTIyY2NmODk5ZGMwODIxNmY2MjljYTJlMWUxZDQ5MWI3Ml9zOyB4X2hvc3Rfa2V5PTQ1OGNhOTkyMmNjZjg5OWRjMDgyMTZmNjI5Y2EyZTFlMWQ0OTFiNzJfczsgeC1ob3N0LWtleS1uZ249NDU4Y2E5OTIyY2NmODk5ZGMwODIxNmY2MjljYTJlMWUxZDQ5MWI3Ml9zOyB4LXRvZmFwaS1ob3N0LWtleT0xN2U1MWIyY2Q3Yy04ZGRmMDNmYjYwZTcyNTUxYjFlZWFkM2NkZDgwNzQ2OTRkNTc1ODJkOyBEaWdnZXJUcmFjZUlkPTJkMDgxNjMwLTc4MGYtMTFlYy1hODBkLTk1ZWZlZjAyOGM1YjsgeF9ob3N0X2tleV9hY2Nlc3M9NDU4Y2E5OTIyY2NmODk5ZGMwODIxNmY2MjljYTJlMWUxZDQ5MWI3Ml9zOyB4LWltcC1ob3N0LWtleT0xN2U5YTNkOWYyOC1hMzI2YzkyYmVmNWRhMjI1MGI2ZDIyMjU5ZDgyN2EwMGJkNzZlMmJlOyB0X3VpZD1kZWNoZW5neXVhbjsgYmx1ZWtpbmdfbGFu"},{"size_arg":"4096"}]},"node_name":"eklet-subnet-bxgkfn1q","time":"2022-12-02T11:44:20.666174440Z"}
print events: {"process_tracepoint":{"process":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg5NDAwMDAwMDA6NTY3","pid":567,"uid":0,"cwd":"/data/code","binary":"/data/code/main","flags":"procFS auid","start_time":"2022-12-02T11:43:25.546661009Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-6f8b5fcfcd-c4dzd","container":{"id":"containerd://f71dd550bc6a99ad046a38bdd0be58348cd418295bce5356ffd1851defdab4f4","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:43:25Z","pid":7},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"6f8b5fcfcd"}},"docker":"f71dd550bc6a99ad046a38bdd0be583","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg3NjAwMDAwMDA6NTU0","refcnt":1},"parent":{"exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjg3NjAwMDAwMDA6NTU0","pid":554,"uid":0,"cwd":"/data/code","binary":"/usr/bin/bash","arguments":"-c /data/tmp/bd_dockerfile_cmdcommands.sh","flags":"procFS auid","start_time":"2022-12-02T11:43:25.366661344Z","auid":4294967295,"pod":{"namespace":"dctestpro","name":"tetragon-dev-v1-6f8b5fcfcd-c4dzd","container":{"id":"containerd://f71dd550bc6a99ad046a38bdd0be58348cd418295bce5356ffd1851defdab4f4","name":"tetragon-dev-v1","image":{"id":"odp-global.tencentcloudcr.com/dctestpro/tetragon@sha256:555bf0f336ecde2ba93cd6c74eb56bb2a019875f1f02dc2b2f63dff4247a96aa","name":"odp-global.tencentcloudcr.com/dctestpro/tetragon:v1.0.6"},"start_time":"2022-12-02T11:43:25Z","pid":1},"pod_labels":{"app":"tetragon-dev-v1","app-creator":"dechengyuan","app-env":"dev","app-id":"22502","devops-env":"release","env":"dev","k8s-app":"tetragon-dev-v1","node-type":"eks","paasid":"","paasname":"tetragon","pod-template-hash":"6f8b5fcfcd"}},"docker":"f71dd550bc6a99ad046a38bdd0be583","parent_exec_id":"ZWtsZXQtc3VibmV0LWJ4Z2tmbjFxOjc1MzAwMDAwMDA6NDY0"},"subsys":"syscalls","event":"sys_enter_read","args":[{"size_arg":"5"},{"bytes_arg":"AAAAAAAAAAAAAAAAAAAAAA=="},{"size_arg":"16"}]},"node_name":"eklet-subnet-bxgkfn1q","time":"2022-12-02T11:44:20.665948726Z"}

the sys_enter_write event whose char_buff prefix is HTTP is filtered out instead.

fixup #576

closing, as it was fixed by https://github.com/cilium/tetragon/pull/770


Test Issue

A test issue created to demonstrate how to create issues in Islandora.

This issue only exists so I could make a screen recording of how to make an issue in our queue.


Default Values

The technique described is inefficient for one reason. The reason is that the database engine already handles default values on any column with a DEFAULT constraint during inserts. These DEFAULT CONSTRAINTS are a defined in standards from the  ISO/IEC 9075-2:1999, Section 11.5 in the SQL Database engine. This is implemented effectively in the database engine at table design time, and the entire default constraint infrastructure is well tested on the database engine. What Use Case does Entity Framework have that would require an exception, wherein a default value would have to be created by EF Core when a row is inserted with no values for columns needing a default? Why not let the database engine do that?

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

ID: 1f32ff95-761b-279a-f5a9-7fe859121356
Version Independent ID: 63cc902d-8261-8185-d0a0-c48c627234b1
Content: Default Values - EF Core
Content Source: entity-framework/core/modeling/relational/default-values.md
Product: entity-framework
GitHub Login: @rowanmiller
Microsoft Alias: divega

@CubeSpark EF creates and/or uses the default constraint on the column. Not sure which "technique" you are referring to that is different from this.

@CubeSpark : @ajcvickers is referring to "code-first" development, where EFCore creates the tables.  This is useful for smaller projects / organizations, but impractical in most organizations because the database team is responsible for creating the tables.  I also dislike it because it requires the app to have table creation permissions.

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.


A dynamic link library (DLL) initialization routine failed.

I am trying to use naudiodon to stream audio in an Electron.js application.  When I attempt to use naudiodon, I get a series of errors related to a dll not being able to be initialized.
Here is my calling code:
const portAudio = require('naudiodon');

// get a list of devices
module.exports.getDeviceList = () => {
  let deviceNames = {};
  for(var x of portAudio.getDevices()) {
    if (x.maxOutputChannels > 0) {
      deviceNames[x] = x.id;
    }
  }
  return deviceNames;
}

The code in my Electron.js html page:
let deviceList = Object.keys(api.getDeviceList());
let optionsHtml = '';
for(var x of deviceList) {
     optionsHtml += `<option>${x}</option>`;
 }
 $('#device').html(optionsHtml);

With api being a reference to the first bit of code.
The traceback:
Error: A dynamic link library (DLL) initialization routine failed.
\\?\C:\--\node_modules\naudiodon\build\Release\naudiodon.node
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:172:20)
    at Object.Module._extensions..node (module.js:598:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:172:20)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at bindings (C:\--\node_modules\bindings\bindings.js:81:44)
    at Object.<anonymous>
(C:\--\node_modules\naudiodon\index.js:19:46)
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:172:20)
    at Object.Module._extensions..node (module.js:598:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:172:20)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at bindings (C:\--\node_modules\bindings\bindings.js:81:44)
    at Object.<anonymous> (C:\--\node_modules\naudiodon\index.js:19:46)
    at Object.exception
...

Part following the ellipsis appear to be irrelevant. (the error echoing up through my code)
I installed naudiodon with npm install naudiodon --save.
I am using the following version of npm and nodejs:
Nodejs: v8.10.0
npm: v5.6.0
And the module (naudiodon) version is: 0.4.6
I am on Windows 10 (64 bit OS)
Please reply as soon as possible.  Thanks!

There are two dlls associated with naudiodon that will need to be loaded - naudiodon.node (a dll really) and portaudio_x64.dll. You are 'require'ing one which will try to pull in the other. It isn't clear to me from your log whether one or both is not being found. Just a couple of thoughts:

Have you tried your JS code without electron ?

Depending on your configuration, electron has a bundle step that may need some configuration to be told to build naudiodon correctly and include the portaudio binary. A quick search yielded: https://electronjs.org/docs/tutorial/application-packaging & https://stackoverflow.com/questions/38361996/how-can-i-bundle-a-precompiled-binary-with-electron

Good luck!

I had this issue with this as well as some other packages. Installing native modules fixed it for me
npm install --save-dev electron-rebuild

# Every time you run "npm install", run this
./node_modules/.bin/electron-rebuild

# On Windows if you have trouble, try:
.\node_modules\.bin\electron-rebuild.cmd

https://github.com/electron/electron/blob/v0.37.2/docs/tutorial/using-native-node-modules.md#using-native-node-modules

Closing this issue.


Assign reviewers from YAML front matter (e.g. jekyll)

Feature Request
Is your feature request related to a problem? Please describe.
In static blog generators it is common to use front matter to define the article author or owner. These people should be assigned as reviewers.
Describe the solution you'd like
Provide a feature which can enable the automatic assignment of reviewers from a yaml key.
Describe alternatives you've considered
None seem to be available

Relates to question #5

Need to add support when the file is not on the base

Released


Add suport for QemuUserEmulation

This allows running containers and binaries for other archs,
like armhf, aarch64 and others without using qemu explicit.
For example run a armhf docker container:
docker run -i -t --rm arm32v7/debian:stable /bin/bash
Signed-off-by: Johann Neuhauser<EMAIL_ADDRESS>

Added check for fixed binary in binfmt_misc

For completeness, dbhi/qus is an alternative solution that works on either GNU/Linux or Windows (Docker for Windows) hosts. Precisely, the feature provided by this PR is equivalent to test r in https://github.com/dbhi/qus/blob/master/docs/tests.md. The advantage of dbhi/qus is that multiple target platforms are supported. Therefore, it might be useful for user that need to run containers for other architectures (e.g. arm64v8/*).

The advantage of dbhi/qus is that multiple target platforms are supported. Therefore, it might be useful for user that need to run containers for other architectures (e.g. arm64v8/*).

Why do you think we can not run a arm64 container with this PR?
I´m only checking for qemu-arm... But this means not that the other emulators are working too.
The full list of emulators is:
/usr/bin/qemu-aarch64-static
/usr/bin/qemu-aarch64_be-static
/usr/bin/qemu-alpha-static
/usr/bin/qemu-arm-static
/usr/bin/qemu-armeb-static
/usr/bin/qemu-cris-static
/usr/bin/qemu-hppa-static
/usr/bin/qemu-i386-static
/usr/bin/qemu-m68k-static
/usr/bin/qemu-microblaze-static
/usr/bin/qemu-microblazeel-static
/usr/bin/qemu-mips-static
/usr/bin/qemu-mips64-static
/usr/bin/qemu-mips64el-static
/usr/bin/qemu-mipsel-static
/usr/bin/qemu-mipsn32-static
/usr/bin/qemu-mipsn32el-static
/usr/bin/qemu-nios2-static
/usr/bin/qemu-or1k-static
/usr/bin/qemu-ppc-static
/usr/bin/qemu-ppc64-static
/usr/bin/qemu-ppc64abi32-static
/usr/bin/qemu-ppc64le-static
/usr/bin/qemu-riscv32-static
/usr/bin/qemu-riscv64-static
/usr/bin/qemu-s390x-static
/usr/bin/qemu-sh4-static
/usr/bin/qemu-sh4eb-static
/usr/bin/qemu-sparc-static
/usr/bin/qemu-sparc32plus-static
/usr/bin/qemu-sparc64-static
/usr/bin/qemu-tilegx-static
/usr/bin/qemu-x86_64-static
/usr/bin/qemu-xtensa-static
/usr/bin/qemu-xtensaeb-static

Why do you think we can not run a arm64 container with this PR?
I´m only checking for qemu-arm... But this means not that the other emulators are working too.

My bad. Since you check(ed) a single target platform, I thought you are/were not interested in others. In this context, advantages of dbhi/qus are;

Being able to register a subset of target archs only, instead of registering all of them at once.
Being able to register versions of QEMU which are different from the one in the package manager.
Not requiring QEMU or any other tool to be installed on the host. Actually, it wotks already.

Overall, I think this PR/feature is ok. The point of referencing dbhi/qus is for users to be aware of other alternatives when this PR falls short.

I have a repo demonstrate how to build alpine packages for {amd64, i386, arm64v8, arm32v6, arm32v7, ppc64le, s390x} using multiarch/qemu-user-static from Docker Hub.
During my test, I found that the qemu-user package from Ubuntu 18.04 is too old (or have some bug), and cannot build s390x packages correctly. While the qemu-user from multiarch/qemu-user-static works correctly.
IMHO, two years between Ubuntu LTS releases is too long for something like qemu-user. It is not that fundamental for CI environment either (qemu-user is super SLOW). I would prefer not including qemu-user into base image.

@zhangyoufu, you will find that multiarch/qemu-use-static is, actually, a sibling project of dbhi/qus. Precisely, the idea to support in-memory loading and to support multiple host architectures was borrowed from qus; see dbhi/qus#2 and multiarch/qemu-user-static#77.

It is not that fundamental for CI environment either (qemu-user is super SLOW).

I beg to disagree. Using DBM is the only solution to currently build non-amd64 images in GitHub Actions (or other amd64-only CI services). I do use this to generate multiarch/manifest images from GitHub Actions and/or Travis. See, for example, dbhi/docker.
However, I agree that it is not a requirement to have qemu-user installed in the base image.


Matcher returning object in old/incorrect format?

I'm seeing the following error when using .toEqualImmutable:
Unexpected return from a matcher function.
Matcher functions should return an object in the following format:
      {message?: string | function, pass: boolean}
'{"compare": [Function anonymous]}' was returned

@idolize I no longer use this library, but I'm open to merging PRs if you figure out what the issue is.

@unindented thanks for the quick merge. Can you publish the new package version into npm? I'm not sure I can do it.

@dimitriylol sorry for the delay. I've now published v3.0.0. Thanks all!

Thanks @dimitriylol and @unindented!


Clinical Safety - Add details to spec

The clinical safety work done will affect the design of the NEMS architecture as well as the structure and use of the event messages, but we also need to consider if any of the clinical safety decisions or information needs to be included in the specification to highlight any specific points.

Clinical safety has been considered and no additional detail needs adding. Closing issue.


sorting by work number

Sorting by work number only works if it is indeed a (pure) number. Most newer catalogues (e.g. Mendelssohn) are using a LETTER+NUMBER designation.
The function used for sorting by work number (MerMEId/trunk/xqueries/main_loop.xqm) should split letters from numbers before adding zeros, i.e. a work number like C 64 should be processed as C000000000000064 instead of<PHONE_NUMBER>0C 64.
(is the predicate in this line needed?

let $num:=$doc//m:workDesc/m:work/m:identifier[@label=$collection][1]/string()

The work number label is not always necessarily the same as the collection.)

We are actually using combinations of letters and numbers. It works for us because we make sure the numbers have the same length: For instance, we have A:003 instead of A:3. Admittedly that will not always be an acceptable option. I'll look into it and try to come up with a better (though probably not completely bullet-proof) solution. Something along the lines you are suggesting.
The predicate is needed because MerMEId by convention uses @label to find out which <identifier> is intended to be the work number. It does so by comparing the work identifier's @label with the seriesStmt/identifier[@type='file_collection']. This matching is necessary because a work may have several identifying numbers (Opus, older catalogue numbers etc.) and MerMEId needs to know which one to look for.

Thanks! Looks great!


xSQLServerAvailabilityGroupListener don't evaluate DHCP properly

When the Get-method shall evaluate DHCP on an existing Listner it can report that it's using DHCP when it doesn't. This was found when doing tests for the resource.
The row 42
$dhcp = [bool]( $presentIpAddress | Select-Object -First 1 IsDHCP )
Should be change to
$dhcp = [bool]( $presentIpAddress | Select-Object -First 1 -ExpandProperty IsDHCP )

I am on this. This will be fixed when I send in the PR with the tests.

This will be fixed when PR #98 is merged.

This was fixed in merged PR #98. Closing.


px4io: add safety_arm and safety_disarm commands

This will be used to make updating firmware on boot for vehicles with
no safety switch possible without power cycling. The startup script
needs to be able to force safety on to allow the reboot to work.

I find the terms used a bit confusing, since it contains arming - is there maybe a way to express this so it doesn't contain the word "arm", which is a different mechanism?

Applied via cherry pick - I renamed the commands to safety_on and safety_off to avoid confusion with the actual arming mechanism.


Check response

DESCRIPTION
Hi! I was reading your wonderful project and I came to index.js;
after short thinking, I decided to add a simple function to check the status code of a response so
that we can avoid repeating the various if statements in each async function!

Ciao @huchenme, any time to review this? 😃

:tada: This PR is included in version 2.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added additional guidance for signing off git commits when contributing

I realize that signing off git commits is explained in a few other places in the documentation, but I feel that an explanation of the --signoff flag is warranted in the "Set your signature and an upstream remote" section.

Thanks! I don't think it hurts to mention it here as well, so LGTM from me
ping @moxiegirl

@vdemeester can you move this over to docker/opensource? Apologies but we were moving things close to the release.

yes, will do as soon as I'm back home (in 3 hours ;-))


Compilation error

Hi mate, im sorry for my inexperince but i need a little help please, when i try to send the code this error appears
" void (*frameCallbacks[3])(int x, int y) = {drawFrame1, drawFrame2, drawFrame3}; "
" exit status 1
'drawFrame1' was not declared in this scope "
Can you please??
Many thanks and regards.

Sorry, Im refer about your ESP8266 Weather Station project.
Thanks.


chore: delete remote branch before release

Description
This PR partially fixes https://github.com/openedx/tutor-contrib-aspects/issues/227

@Ian2012 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


All (Popular) - Instructables Bridge failed with error 0

Error message: Unexpected response from upstream. cUrl error: Failed to connect to www.instructables.com port 443: Connection timed out (7) PHP error:
Query string: action=display&bridge=Instructables&context=Category&category=%2Fcircuits%2F&filter=popular%2F&format=Mrss
Version: git.master.b754d14

Works fine for me. https://i.imgur.com/16fBV3u.png
Possible internet problems on your side.


Int Oveflow in GenerateMarginCallOrder()

Reported error int overflow in the GenerateMarginCallOrder() method.
Code to reproduce: https://www.quantconnect.com/forum/discussion/1150
at System.Decimal.ToInt32 (Decimal d) [0x00000] in :0
  at System.Decimal.op_Explicit (Decimal value) [0x00000] in :0
  at QuantConnect.Securities.SecurityMarginModel.GenerateMarginCallOrder (QuantConnect.Securities.Security security, Decimal netLiquidationValue, Decimal totalMargin) [0x00000] in :0
  at QuantConnect.Securities.SecurityPortfolioManager.ScanForMarginCall (System.Boolean& issueMarginCallWarning) [0x00000] in :0
  at QuantConnect.Lean.Engine.AlgorithmManager.Run (QuantConnect.Packets.AlgorithmNodePacket job, IAlgorithm algorithm, IDataFeed feed, ITransactionHandler transactions, IResultHandler results, IRealTimeHandler realtime, ICommandQueueHandler commands, CancellationToken token) [0x00000] in Lean.Engine.AlgorithmManager.Run (QuantConnect.Packets.AlgorithmNodePacket job, IAlgorithm algorithm, IDataFeed feed, ITransactionHandler transactions, IResultHandler results, IRealTimeHandler realtime, ICommandQueueHandler commands, CancellationToken token) [0x00000] in :0
  at QuantConnect.Lean.Engine.Engine+c__AnonStorey1.<>m__0 () [0x00000] in Lean.Engine.Engine+c__AnonStorey1.<>m__0 () [0x00000] in :0

Resolved as issue with BRK.A data ticks


Initial implementation of the metadata log

Now this PR depends on #80.

I merged first 3 commits (after squashing 2 fixups as well), and continue the review, successfully merging stuff or commenting on found issues.


Installation fails with Flakes

Both installation methods fail if you have flakes enabled.
My understanding is that this is happening because flakes enforce pure evaluation, which requires you to lock you input.
Here is the error message:
error: in pure evaluation mode, 'fetchTree' requires a locked input, at «none»:0

I'm still learning Nix, so I was not able to fully solve the problem myself.
You probably need a rev instead of ref and a hash to lock the input.
I read the fetchGit documentation, and it doesn't look like fetchGit supports sha256 hashes.
I was able to solve the locked input issue by using fetchFromGitHub, but it ended up on a circular reference.
I'm still researching a solution, but wanted to share it here in case someone is able to find a solution.
Here is my failed attempt with fetchFromGitHub:
{pkgs, ...}: {
  imports = with pkgs; [
    (fetchFromGitHub {
        owner = "anthonyroussel";
        repo = "shadow-nix";
        rev = "v1.5.0";
        hash = "sha256-+kA4vmUb+gjb8uaMHfsuTTJHOOvLka0qfON9/l6PLrw=";
      }
      + "/import/home-manager.nix")
  ];

  programs.shadow-client = {
    # Enabled by default when using import
    # enable = true;
    channel = "preprod";
  };
}

Solved the issue.
Here is how to enable it on home-manager if you are are using flakes:
In your flake.nix file:
inputs = {
  # rest of your inputs config
  shadow-nix = {
    url = "github:anthonyroussel/shadow-nix/v1.5.0";
    flake = false;
  }
};

in your home-manager config:
  imports = ["${inputs.shadow-nix}/import/home-manager.nix"];

  programs.shadow-client = {
    channel = "preprod";
  };


Managing the reset CSS

When we use HTML tag it comes with default user agent styles. But this causes design problems according to our design system and we have to reset user agent styles in projects.
Maybe we can provide reset.css file to reset user agent styles. We should decide to whether add it to the baklava project.
There is an example for the p tag and ul tag. We don't want to see these paddings according to our typography Figma design.

This can be tracked in #390


Add a component to render placeholder text in empty cells

Adds a helper component for rendering placeholder text to explain why a cell has no content.
Closes https://github.com/github/primer/issues/1958
Screenshots

Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[x] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

I also considered adding this as a property on the columns object, but that locks the consumer into a single placeholder message for all empty cells in the column. I went with a helper component incase they have different text they want to render depending on why there is no content.
Reviewers, which direction do you prefer?


[subset] fix subsetting OT-SVG when glyph id attribute is on the root  element

/cc @frankrolf
Fixes https://github.com/fonttools/fonttools/issues/2548
I tested locally with Noto Emoji OT-SVG and it works now

Thank you!


Validate Array of Inputs

Versions:

VueJs: 2.3.4
Vee-Validate: 2.0.0-rc.6

Description:
More of a question than a bug.   Not entirely sure what should the places I've marked with ???

       <input type="text" name="number[]"  v-validate="'required'" v-bind:value="value" v-bind:class="[errors.has('???') ? 'form-control-danger' : fields.??? && fields.???.pristine ? '' : 'form-control-success' , 'form-control']">
       @{{ errors.first('???') }}

Steps To Reproduce:

Validating arrays has been a tricky subject so far, because for all intended purposes you might either want to validate each value in the array, or validate the array itself based other characteristics, for example:
An alpha rule: would validate every value inside the array, but a required rule would check its length instead. Built-in rules are easy to handle, the problem is how to determine the same logic for custom rules. so I was kind of dodging the subject until I find a solution.
Example of the rules that are suited to deal with arrays: all file validators, and required. Currently I think I would only equip the other built in rules to deal with arrays like alpha would validate each item. and leave the custom rules implementation to decide what to do with arrays.

Closing since next release should handle inputs array values (custom components) like repeaters.

Hello is there any solution regarding on validating input fields with array names? (e.g )

Closing since next release should handle inputs array values (custom components) like repeaters.

So are there any solutions on how to handle repeater fields in vee-validate. I want i.e. to check if a user has filled at least one input field in the array.


Avoid redirects to anything.com in Firefox.

See http://stackoverflow.com/a/32592759/901944
If you don't preventDefault, the drag succeeds, but afterwards Firefox tries to go to http://anything (because that's the text content of the drag), which it then updates to http://anything.com, which does exist.
This problem does not occur on Chrome.

Released in 2.0.0-beta.1.
@anlumo Thank you for your kind contribution and please excuse me for the delay in merging/releasing. 🙏

Glad that it's included now! I've been using my fork in production for two months now with no complaints by the users.


Documentation Standard Updates

This pull request was created automatically 🎉:

[x] Ensure .github/ files have been properly updated (templates are updated and auto releaser is included)
[x] Confirm all appropriate end models are included in the .quickstart/quickstart.yml file as public_models (only for transform repos)
Verify the README has made all necessary updates:

[x] Removal of emojis
[x] Replacing exclamation points with periods in sentences
[x] Adjusting all headers to ensure only one H1 heading
[x] Confirming a section header is included for Quickstart UI rendering (only for transform repos)
[ ] Renaming **models to **tables** (only for transform repos)
[x] Removal of Fivetran community and office hour resources (if necessary)

@fivetran-catfritz great callout. We will want to make sure the wording rendered in the Quickstart UI is referring to "tables". So in your callout we will want to make that update. But we can leave the other non UI references as models.
I just made the update. Let me know if you have other questions.


Responsive Map

Is there any way to make the center stay centered when resizing the window?
I found a simple responsive example, but the new center has already been calculated by the time I try to access it when using the component API.
https://codepen.io/hubpork/pen/xriIz

Please refer to Getting Help section in the README (or #469).

@michaelcpuckett, I have the same problem.
Did you find a solution for this?

I've tried with something like this, but it doesn't seem to work.
class GoogleMapPickup extends Component {

    constructor() {
        //...
       this.handleWindowResize = debounce(this.handleWindowResize.bind(this), 500);
    }

    componentDidMount() {
        window.addEventListener('resize', this.handleWindowResize);
    }

    handleWindowResize() {
        const nextCenter = this._map.getCenter();
        console.log( 'nextCenter: ' + JSON.stringify(nextCenter) );
        google.maps.event.trigger(this._mapComponent, "resize");
        this.setState({
            center: nextCenter
        });
    }

}

However, in console I get different values for nextCenter on every resize.

@andreivictor @michaelcpuckett Something like this worked for me:
constructor(props) {
    super(props);
    this.state = {
      latitude: null,
      longitude: null,
    };
  }

setMapCenter = () => {
   // pull out latitude longitude from wherever you're getting it from
    const { latitude, longitude } = this.props;
    this.setState({ latitude, longitude });
  };

  componentDidMount() {
    window.addEventListener('resize', this.setMapCenter);
  }
  componentWillUnmount() {
    window.removeEventListener('resize', this.setMapCenter);
  }

Then in your map component, set the defaultCenter to {lat: latitude, lng: longitude}. Just make sure to set the state when you receive the latitude and longitude values you want to use


Fixing link to CODE_OF_CONDUCT.md within README.md

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?

On https://github.com/Homebrew/brew/blob/master/README.md the link to the Code of Conduct page leads to a 404 page.
Updating the link allows a user to navigate to the correct page to view the resource.
Same issue as #3266

Thanks for your first contribution to Homebrew!  You rock!


Dynamic imports, usage instructions

Sorry for the late reaction. I realigned the code, my IDE was a bit overenthusiastic. I also generalized the switch, I think it works, but you might consider moving the NUMBER_OF_PLAYERS to a general constants file (or an args?)

Thank you for your PR! I've discovered a small bug afterhand but now fixed in master.
I am now thinking how to define NUMBER_OF_PLAYERS: maybe as an arg (like "splendor-2"). But in such case, NB_GODS in SantoriniConstants.py should also be a user-defined...

Thank you for your PR! I've discovered a small bug afterhand but now fixed in master. I am now thinking how to define NUMBER_OF_PLAYERS: maybe as an arg (like "splendor-2"). But in such case, NB_GODS in SantoriniConstants.py should also be a user-defined...

Yes, I would add maybe --nbplayers, but with a default value of 2. For the gods, maybe add an "--custom" argument which allows for custom arguments per game, e.g. "--custom NB_GODS=2".
You might want to consider using config/"ini" files which can be read with configparser, although a similar thing can be done with fromfile-prefix-chars
So launching python main.py splendor -m 800 -f 0.1 -l 0.0003 -D 0.3 -C ../results/mytest -V 74 could become python main.py @cfg/splendor2p.ini


Update repos for an Org Team

Thanks your your amazing work for creating this node module to easily rename branches in a bunch of repositorys.
This PR makes it easier to rename master  -> main branche only in repositories which are linked to a team in an organization.
If parameters org and team are provided all repos an existing team
are being looked up and updated. There is no functional change
on the existing org or user parameters.

Hi @mheap you are right, I did not exclude the full org lookup even if the team is provided. I've added the args.team condition for the listForOrg as well, so it should work now. Code does not look really DRY, but its still good readable.
I was thinking of adding the --team parameter into the front validation but decided to leave the front validation as it is, because it would only complicate stuff instead of making anything clearer.
I squashed the change into the existing commit, the PR is updated.

Thanks for this @marcohutzsch1234 - it's now released as github-default-branch v1.9.0


[Magefiles] - Remove developer/init.sh and replace with mage targets.

developer/init.sh effectively does:

Building the docker images, go mod tidy and protoc building
Building the Lookout UI optionally
Actually running armada.

This should become 3 mage targets instead, build, ui and run.
localdev would be replaced with run and localdevstop would be replaced with teardown

Hi @kannon92, what do you think about this? I would love to work on this.

/assign


fix empty deployedtemplate

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

https://github.com/aws-samples/aws-cudos-framework-deployment/issues/442


v0.17.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

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

Totals

Change from base Build<PHONE_NUMBER>4:
0.0%

Covered Lines:
11077

Relevant Lines:
13325

💛  - Coveralls


TendermintClient::verify_upgrade_and_update_state is not implemented

Related to: https://github.com/informalsystems/ibc-rs/issues/722
Summary
The TendermintClient::verify_upgrade_and_update_state is currently not implemented, even though it is called in the UpgradeClient handler.
https://github.com/informalsystems/ibc-rs/blob/efbf7d18512fe6efcb593de68735b7f8783fd652/modules/src/clients/ics07_tendermint/client_def.rs#L395-L403
https://github.com/informalsystems/ibc-rs/blob/efbf7d18512fe6efcb593de68735b7f8783fd652/modules/src/core/ics02_client/handler/upgrade_client.rs#L52-L57
Problem Definition
The UpgradeClient is therefore non-functional at the moment, as it will panic once the method is called.
Proposal
Implement the verify_upgrade_and_update_state method for TendermintClient.
Acceptance Criteria
The verify_upgrade_and_update_state is implemented in TendermintClient, and its behavior is captured in a test for the UpgradeClient handler.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Until we know how to implement this properly, we should return an Error instead of crashing (either at the tendermint light client level, or even at the core handler level).
Related: #141


how to get embeddings from a speaker

I wanted extract Embeddings from a Audio File...Because I wanted to do Voice Similarity.
I'm Confusing with ReadMe File......to get Embeddings,Any Simple Commands...
I found These code on README....

train.py for training.

run python train.py some_case_name

In Above case,what is some_case_name
And Also Some Help for Extracting Embeddings with embeddings.py....

I need it too, can you help me?

Hi,
I have the same question, what is some_case_name?
Have you solved it?


Fix error shows briefly while connecting NetSuite

Details

While connecting with NetSuite, we saw an error briefly, this PR fixes that.
Fixed Issues

$ https://github.com/Expensify/App/issues/49752
PROPOSAL: https://github.com/Expensify/App/issues/49752#issuecomment-2375615670
Tests

Login with any account.
Create a new WS.
Go to that workspace setting =>  More Features => Enable Accounting feature.
Go to Accounting, click NetSuite.
Enter NetSuite credentials.
Verify you can connect with NetSuite without any issue.

[x] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

Same as Tests.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/39f0d588-6a0d-4055-8b9b-9eba66a8a831

Android: mWeb Chrome
https://github.com/user-attachments/assets/0f3ed8dc-4853-4494-80bb-6869c7692913

iOS: Native

https://github.com/user-attachments/assets/9b057ba6-97bd-42eb-9eab-0f245d4795c1

iOS: mWeb Safari

https://github.com/user-attachments/assets/97a7dbde-18bd-4674-8e61-581eba62e5bd

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/0a0c7278-566b-4d41-a819-ab8f6b41e96b

MacOS: Desktop

https://github.com/user-attachments/assets/65cc2c20-9628-4f26-939e-cc1f3f681d1d

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Performance regression was introduced here:

https://github.com/Expensify/App/pull/50143

We are currently fine with that regression, as it will be fixed later on. The e2e system reports regressions for every new PR until a new release version has been created (this will be improved soon). So can be ignored!


Fix availability

Home Assistant shows entity availability based on HubSpace availability. When a device is unavailable in HubSpace, you cannot interact with it in Home Assistant.

This should fix an issue where a device shows as available when HubSpace cannot communicate with it. Testing instructions:

Goto HACS within HA
Click Hubspace-HomeAssistant
Click the triple dots on the top-left
Click Update Information
Click the triple dots on the top-left
Click Redownload
Click Show beta versions
Select v3.0.2
Click DOWNLOAD
Restart HA

Let me know if the issues persist after using this beta version


Prometheus 2.26.1

here is a list of bug fixes that could make it into a 2.26.1 release
#8748
#8723
#8746
#8737

when will it be released

Closing this as they should be in 2.27. Chris will decide the faith of the remaining one.


Don't use Expect header and components in meta section

Use a different custom HTTP header to define the version range the client wants to receive.
Specify a different HTTP status code for an error response.
Fixes https://github.com/ga4gh-discovery/ga4gh-discovery-search/issues/47

Now also fixes Meta section doesn't clearly define component versions #49


SEGFAULT when uv_udp_recv_stop or uv_read_stop in uv_alloc_cb

Version: 1.30.2
Platform: Linux host 4.4.0-157-generic #185-Ubuntu SMP Tue Jul 23 09:17:01 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

The code in the attached files (segfault_udp.c, segfault_tcp.c) causes a SEGFAULT inside libuv when it stops reading from a  uv_udp_t or uv_tcp_t by invoking uv_udp_recv_stop or uv_read_stop inside the uv_alloc_cb callback.
Also see: https://groups.google.com/d/topic/libuv/QWg9XLt-fuw/discussion

Yes, calling stop in the alloc_cb cannot work as the read_cb is set to NULL and later is being accessed. I would probably add an assertion in the code to check for the validity of the read_cb and a note in the documentation of the stop functions to warn users not to use them in the alloc_cb.

Or we could make it legal by not calling the read callback, right? I guess this is only applicable in case you try to allocate memory, fail and as a result don't want to read anymore...

Or we could make it legal by not calling the read callback, right?

Yeah, that makes more sense


[WIP] Refactoring of linux_pwm_out

Please use PX4 Discuss or Slack to align on pull requests if necessary. You can then open draft pull requests to get early feedback.
Describe problem solved by this pull request
Make more pwm related parameters on Linux based boards can be configured. New driver is called linux_pwm_output but linux_pwm_out is not removed.
Describe your solution
Take px4fmu as the reference and completely rewrite the driver.
Test data / coverage
Test passed on RPi with debug and pca9685 mode. The actual pwm pulse each channel outputed is examined  with gazebo_plane simulator in debug mode. Due to hardware limitation I cannot test for other hardware solutions.
Additional context
Currently it does not support parameters related to trim value to be configured due to some very strange problems. Other parameters can be configured and take effect immediately without rebooting required. This will cause heavy load when parameters changed but not very significant compared to the computing power from RPi #13635
Now the mixer file should be loaded by mixer command. (Some comments should be changed.)
This driver assume that there are 16 channels in no difference. Parameters like PWM_MAIN_XXXn are treated for the first 8 channels and others with AUX mark are treated for 9~16 channels. Discuss
It is able to be merged but also can be kept as WIP for further development. But I'm not able to make improvements to hardware solutions except for RPi with PCA9685.

Did you consider breaking out PCA9685 as a standalone (cross platform) mixer module? I never really liked linux_pwm_out. We should now be in a position to have everything broken out as a relatively simple standalone driver with all the mixer logic provided by lib/mixer_module (src/lib/mixer_module).
The only thing it would take to make PCA9685 cross platform is to use I2C like in other drivers, rather than opening /dev/i2c-x directly.
Example:
https://github.com/PX4/Firmware/blob/505e922b08cb64066b0ac4cd401489655713165f/src/drivers/lights/rgbled/rgbled.cpp#L63

Proposal:

Split out pca9685 into a new standalone output module that uses I2C and mixer_module
For what's left in linux_pwm_out (bbblue, navio, ocpoc) I'd like consider abstracting the actual PWM access into the same API as used on NuttX (up_pwm_servo_set, etc). Then we can simply use the fmu module everywhere (renamed to something like pwm_out). We can do this later.

Overall I think this would help clean up a lot of the mess (killing linux_pwm_out entirely) and allow for better code re-use and testing. I want to minimize these differences between platforms.

Proposal:
* Split out `pca9685` into a new standalone output module that uses I2C and mixer_module

* For what's left in linux_pwm_out (bbblue, navio, ocpoc) I'd like consider abstracting the actual PWM access into the same API as used on NuttX (`up_pwm_servo_set`, etc). Then we can simply use the `fmu` module everywhere (renamed to something like `pwm_out`). We can do this later.

Overall I think this would help clean up a lot of the mess (killing linux_pwm_out entirely) and allow for better code re-use and testing. I want to minimize these differences between platforms.

That's good. But these low level API is a little difficult to understand in my view. I still cannot understand how it works. I would like to create a new pr to get PCA9685 merged as a multi-platform supported driver but others in linux_pwm_out really annoying.

Additionally, I suggest that the parameters which are defined with "MAIN' and "AUX" should be abandoned. They are useless and confusing. I think a flat definition of actual pwm channels works better in most case.

And another question:
Should pwm parameters be update real time or reboot required?
px4fmu relies on-boot-configure done by pwm command and doesn't update most of them from params inside the loop.
If I implement a pwm driver, what should I firstly considered to be supported? Now I only know that I can properly make the driver support mixer files loaded from mixer command by supporting corresponding ioctls, and it is not necessary to support esc_calib and pwm commands which will lead to conflicted control result. Any other suggestion?


Allow user to draw a path with the mouse

Record the points, then fft them. See https://www.youtube.com/watch?v=n9nfTxp_APM for inspiration.

Write three classes, like in a game:

Class to control the whole app, load paths, fft, save images, etc.
Class for running and drawing the epicycles
Class for recording mouse coordinates and drawing a path
Switch between the states via keypress. If the user drew a path and switches states then immediately begin running the corresponding fft and epicycles. Also accept command line argumends to start the app in either state.

Note in the readme that the path to the text file is optional. If it is left out then the game should start directly in drawing mode.

Either take the points in the order they are provided or try to optimize the path on the press of a button.


Randomly choose from pre-defined list

I am wondering in C# AutoFixure, is there a way to randomly choose from the pre-defined list? for example, so when I use fixture.Create or fixture.CreateMany, it randomly selects an object from the pre-defined list. I did not find anything similar from documentation and searching stackoverflow so I am not sure it is even possible.
Documentation link

Closed via https://stackoverflow.com/questions/47761145/autofixure-randomly-choose-from-predefined-list


How to disable Fzf contrib autoloading

Hi @akinomyoga,
I use the dotfiles managing tool chezmoi, which I setup to install fzf and its bash completion files from the fzf upstream to:
.local/bin/fzf
.bashrc.d/80-fzf_completion.bash
.bashrc.d/80-fzf_key_bindings.bash

In my .bashrc I source all .bashrc.d/*.bash files, therefore also loading the fzf files.
As you can see, those are not standard locations, and ble.sh fails to find those and therefore it prints (kinda annoying) error messages.
Is there a way to disable autoloading the fzf integrations in ble.sh?
Or even better, is there a way to specify the those files as a bleopt?
Is there any benefit by letting ble.sh know where the fzf integrations files are? What are the benefits over loading them manually like I did?
Thank you in advance! :slightly_smiling_face:

@dylankb maybe you know something about this?
I added you since you helped to implement the FZF integration :slightly_smiling_face:

Is there a way to disable autoloading the fzf integrations in ble.sh?

No, or exactly speaking, disabling the integration will make the fzf completion block the entire shell session and the shell does not respond anymore. The integration is needed to make the fzf completion work with ble.sh. This is related to the assumption that the fzf completion makes. Since ble.sh extends the completion feature of the shell, the behavior is inevitably not the same as the original Bash. For this reason, some subtle assumptions that the fzf completion uses to hack Bash is not satisfied with ble.sh.

Or even better, is there a way to specify the those files as a bleopt?

That is one possible solution.

Is there any benefit by letting ble.sh know where the fzf integrations files are?

Originally, we intended that the fzf completion and key-bindings are loaded through the fzf integration and didn't assume the case where the user loads those settings manually. This is because the adjustments of the fzf settings are always needed. The fzf-initialize module is designed for this situation to automatically detect the locations of the fzf settings that the user tries to load.
However, there are still users who try to load the fzf settings manually. For such a case, the core-complete module of ble.sh tries to automatically fix the problem when it detects a manually loaded fzf-completion setting. This is now done by afterward calling the module designed for the first way (indirectly loading the fzf settings through the integration).
The problem would be that the module designed for the first case (indirect loading) is just re-used for the second (unexpected) case (manual loading). In your situation, you would like to load the setting manually, which falls in the second case where ble.sh didn't assume.

What are the benefits over loading them manually like I did?

Because ble.sh needs to modify the settings that the fzf completion and key-binding set up. The most natural way is to intercept the loading stage of those fzf settings.

To determine a solution, I need to know the detailed setup of chezmoi or your specific setup. Depending on the actual situation, possible solutions are as follows:

If you customize the settings that are defined in the default fzf completion or key-binding, you will probably need to write your own integration to make your fzf settings work with ble.sh. In that case, contrib/integration/fzf-{completion,key-binding}.bash will not be able to directly use but can be example implementations you can reference when you write your own integration.
If you just copy/move the fzf settings to the specific directly ~/.bashrc.d, isn't it possible to keep the location of those files in the default locations somewhere under ~/.local/share/fzf/... and instead put ble-import lines in ~/.bashrc.d/80-fzf*.bash? That might not work because I'm not familiar with the chezmoi framework, but it would be the best solution if it works. If it doesn't work, could you explain how chezmoi works and the reason that it is not possible to keep the standard locations of the original files and put symlinks or source <standard locations> at 80-fzf*.bash.
If those files are still kept somewhere inside ~/.local, I may add more "standard locations" to the list, though I'm not sure if it is actually the case. What is the result of the following command?

$ (cd ~; find .local | grep fzf)

The above solutions still try to load the fzf settings indirectly, but you still need to do the manual sourcing of the fzf settings, I might think of separating the fzf integration module into the ones for two cases, i.e., for the auto-loading case and for the case of manual loading + afterward modification.

I've created a user in a virtual machine with Ubuntu 20.04 LTS and installed chezmoi. I tried to find how chezmoi sets up fzf, but chezmoi doesn't seem to specify how fzf is installed. I guess the above setup of .local/bin/fzf, .bashrc.d/80-fzf_completion.bash, and .bashrc.d/80-fzf_key_bindings.bash is designed by you. Is my understanding correct? If there is a way to reproduce the provided setup using the chezmoi framework, could you describe it?

@stablestud Could you provide the result of the following command?
$ (cd ~; find .local | grep fzf)

Thanks @akinomyoga for the thorough explanation about the fzf integration.
I thought the ble.sh implementation replaces the default fzf scripts, thus my confusion,
but good to know, I will then but the fzf scripts into the default directory ~/.local/share/fzf/...
and make us of ble-import.
Can I specify ble-import also in .blerc?
And yes I manually setup chezmoi to put the fzf files into these destinations.
For reference, here is my install instruction for fzf which will be executed by chezmoi: https://github.com/stablestud/dotfiles/blob/master/.chezmoiexternals/fzf.toml.tmpl
And here's the requested output:
.local/share/blesh/contrib/fzf-key-bindings.bash
.local/share/blesh/contrib/fzf-git.bash
.local/share/blesh/contrib/fzf-initialize.bash
.local/share/blesh/contrib/integration/fzf-key-bindings.bash
.local/share/blesh/contrib/integration/fzf-git.bash
.local/share/blesh/contrib/integration/fzf-initialize.bash
.local/share/blesh/contrib/integration/fzf-completion.bash
.local/share/blesh/contrib/fzf-completion.bash
.local/share/chezmoi/private_dot_config/fish/conf.d/99-fzf.fish
.local/share/chezmoi/.chezmoiexternals/fzf.toml.tmpl
.local/man/man1/fzf.1
.local/man/man1/fzf-tmux.1
.local/bin/fzf-tmux
.local/bin/fzf

Looking at the integration scripts, I see that there is also one available for Zoxide.
Unfortunately the documentation for it is sparse and I wonder if there is any benefit of loading ble.sh zoxide integration?
Currently I load Zoxides completion in ~/.bashrc.d/80-zoxide.bash with eval "$(zoxide init --cmd=j bash)"
Should I also make use of ble.sh's zoxide integration?

Thank you for your reply. Yes, the latest update of your configuration https://github.com/stablestud/dotfiles/commit/eca2fda936cae3457e6885f6f7bdc490f955f0fc is what I expect.
For the zoxide integration, you do not have to use it explicitly. You can just do eval "$(zoxide init --cmd=j bash)". ble.sh automatically loads contrib/integration/zoxide when it detects the zoxide configuration. The difference between the fzf settings (specifically the fzf key-bindings) and the zoxide completion is that the former needs modification at the loading time, but the latter can be modified afterward.

Thank you! 😎
My issues are resolved 😄


Abstract team

When I was working on setting up the project for our team, I made a mistake which resulted in having this error on the screen:
You cannot access this site unless you are a member of the thoughtbot team

I was a little bit confused. After digging into the code, I realized that it is a hard-coded thing. :smile:
This PR makes the meaning of the team more abstract in order to avoid confusions. :wink:

Thanks!


Data Grid - Column Headers - Add tooltip on hover #809

Description
Adds tooltip to DataGrid header cell
Issues Resolved
Fixes #809
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] All tests pass

[ ] yarn lint
[ ] yarn test-unit

[ ] Update CHANGELOG.md
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@keskami For UI changes like this can you provide some screencasts or screenshots of the before and after behavior of the component? That makes it much quicker for reviewers to understand your intended changes.

ok! I'll make sure to do that from now on

Before

after


Only recompile plugin scripts to executables when needed

This is an optimization that skips the compilation step of a package plugin if a compiled version already exists, if none of the input files have changed, and if none of the compiler flags have changed.
Motivation:
Better performance by avoiding unnecessary work.
Modifications:

compute hash of the input conditions and store it next to the compiled executable
if the compiled executable exists and the hash is the same since the next time, skip compiling
add a field to the compilation result structure to reflect whether the compilation was cached
extend a unit test to verify that diagnostics (e.g. warnings) are still emitted

Result:
No functional change, but less time spent compiling plugins.
rdar://74663095
NOTE: This PR currently incorporates apple/swift-package-manager#3913 since it builds on that code, but this will be rebased once that is merged.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Azure SQL DB - Date datatype recognized as String

I have an Azure SQL Database (PaaS) based AAS model where tables were correctly imported initially, but for a while now source data type DATE are not recognized correctly in Tabular Editor (latest version 2.17.8455), and "Refresh Table metadata" continuously bringing it up as a mismatch to modify it to String.
SQL user has full access to db, I even tried explicitly cast the data type to DATE in the view but same result.

"Data source providers SQLOLEDB and SQLNCLI have been deprecated. Use MSOLEDBSQL instead." This advice from BPA rules solves the issue, but would appreciate if I can get a confirmation

Hi @jozsefbraun
Apologies for the late reply. Yes, there are several reasons why it is preferred to use MSOLEDBSQL. One of them, is that the "Refresh table metadata" feature is better able to map datatypes.


Potential overflow when decoding in RoaringBitmap::deserialize_from_impl()

What is the issue
There is an overflow in deserialize_from_impl() that can be reached if s + len  overflow a u16.
The overflow is reachable as both s and len are decoded from user input.
Noting in release mode this will wrapping overflow and not cause a panic. However, a panic would occur in debug mode.
What is the solution
Use checked math and propagate the error.

Closed by #271


Update zio, zio-test, zio-test-sbt to 2.1.0

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

from 1.0.18 to 2.1.0 ⚠
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #2901.


What category should waydroid project fall into?

waydro.id
https://github.com/waydroid/waydroid

@apiraino  it works on Wayland only 🙂

I'm dumb, it's written also in the docs :-)
https://waydro.id/#howto

I agree this looks like a really cool project, and will happily add it! Thanks for sharing.
But oh boy... what category indeed. Maybe a new one called "Emulation"?


Serbian translation for North Macedonia is incorrect

In the Serbian (sr) translations, MK (the ISO 3166 code for North Macedonia) is mapped to "Нова Каледонија". But "Нова Каледонија" appears to be the Serbian name for New Caledonia. I think (based on Wikipedia; I personally don't read Serbian) the correct translation should be something like "Северна Македонија".

I don't read Sebian either, but "Северна Македонија" looks correct, and this seems to be an issue with the I18Data gem that we use. I'll report it upstream.

Thanks!

Fixed in #705, I'll try to have a new release soon


Cursor slows down if typing animation is enabled

Issue summary
When there is a long text to echo and typing animation is enabled at any delay, the echoing slows down to a very low pace.
Expected behavior
The cursor should keep moving at same pace.
Actual behavior
the echoing slows down to a very low pace after a very specific time
Steps to reproduce
Browser and OS
Chrome(Version 111.0.5563.65 (Official Build) (64-bit)) and Windows 11 Home
Additional notes

Yes, This is a known issue, I'm closing because this is a duplicate of #820.


Typo in Blog Post on Auth

Hey! Not sure where to put this, but there is a typo in the Fresh blog post here. I'm new to Deno as of today! Good to be here ❤
https://deno.com/blog/setup-auth-with-fresh
In this segment on #add-login-and-logout-to-index
The code reads
// routes/index.tsx

export default function Home({ data }: PageProps<Data>) {
  return (

        You currently {data.isAllowed ? "are" : "are not"} logged in.

      {!data.isAllowed ? <Login /> : Logout}

  );
}

and that href on the Logout button should be Logout as the other 404's.
Freaking love this project!!

thanks for reporting the typo! we'll update it.


Move tutorial files out of repo

Many contributors have difficulty with git lfs. Accordingly, the tutorial files need to be removed from the main earthenterprise repo and will be hosted elsewhere. The goal is to get the size of the repo down small enough that we no longer have to rely on git-lfs.
AC:

Tutorial files are removed from the main repo
Write follow-on tickets to further reduce the size of the repo and remove git-lfs requirement

Added tutorial to opengee.org website, but need to remove data files from repo


Decoding a Json Encoded board fails

Here's a sample ghci session:
ghci> let g = unsafeNewGame [human "josh", human "nick"]
ghci> g
Game {, [josh rack: TJQEOEE score: 0id: 0] :| [[nick rack: NMNYSDN score: 0id: 1]], ______________________________________________
|3W|  |  |2L|  |  |  |3W|  |  |  |2L|  |  |3W|
|  |2W|  |  |  |3L|  |  |  |3L|  |  |  |2W|  |
|  |  |2W|  |  |  |2L|  |2L|  |  |  |2W|  |  |
|2L|  |  |2W|  |  |  |2L|  |  |  |2W|  |  |2L|
|  |  |  |  |2W|  |  |  |  |  |2W|  |  |  |  |
|  |3L|  |  |  |3L|  |  |  |3L|  |  |  |3L|  |
|  |  |2L|  |  |  |2L|  |2L|  |  |  |2L|  |  |
|3W|  |  |2L|  |  |  | *|  |  |  |2L|  |  |3W|
|  |  |2L|  |  |  |2L|  |2L|  |  |  |2L|  |  |
|  |3L|  |  |  |3L|  |  |  |3L|  |  |  |3L|  |
|  |  |  |  |2W|  |  |  |  |  |2W|  |  |  |  |
|2L|  |  |2W|  |  |  |2L|  |  |  |2W|  |  |2L|
|  |  |2W|  |  |  |2L|  |2L|  |  |  |2W|  |  |
|  |2W|  |  |  |3L|  |  |  |3L|  |  |  |2W|  |
|3W|  |  |2L|  |  |  |3W|  |  |  |2L|  |  |3W|
----------------------------------------------
, Bag {bagTiles = [O,N,B,I,G,I,E,A,E,H,R,O,S,L,_,W,S,R,I,F,G,I,D,E,V,D,E,Y,E,S,R,I,A,E,U,A,G,I,L,H,D,E,F,T,O,T,T,U,N,T,I,O,I,L,_,A,A,V,P,C,N,E,R,W,K,I,E,B,A,R,A,L,Z,O,O,A,R,U,M,O,A,U,T,X,P,C]}, nr turns:0, }
ghci> let Right g' = applyWord "TOE" Vertical (7,7) [] g
ghci> g'
Game {, [nick rack: NMNYSDN score: 0id: 1] :| [[josh rack: JQEEONB score: 6id: 0]], ______________________________________________
|3W|  |  |2L|  |  |  |3W|  |  |  |2L|  |  |3W|
|  |2W|  |  |  |3L|  |  |  |3L|  |  |  |2W|  |
|  |  |2W|  |  |  |2L|  |2L|  |  |  |2W|  |  |
|2L|  |  |2W|  |  |  |2L|  |  |  |2W|  |  |2L|
|  |  |  |  |2W|  |  |  |  |  |2W|  |  |  |  |
|  |3L|  |  |  |3L|  |  |  |3L|  |  |  |3L|  |
|  |  |2L|  |  |  |2L|  |2L|  |  |  |2L|  |  |
|3W|  |  |2L|  |  |  | T|  |  |  |2L|  |  |3W|
|  |  |2L|  |  |  |2L| O|2L|  |  |  |2L|  |  |
|  |3L|  |  |  |3L|  | E|  |3L|  |  |  |3L|  |
|  |  |  |  |2W|  |  |  |  |  |2W|  |  |  |  |
|2L|  |  |2W|  |  |  |2L|  |  |  |2W|  |  |2L|
|  |  |2W|  |  |  |2L|  |2L|  |  |  |2W|  |  |
|  |2W|  |  |  |3L|  |  |  |3L|  |  |  |2W|  |
|3W|  |  |2L|  |  |  |3W|  |  |  |2L|  |  |3W|
----------------------------------------------
, Bag {bagTiles = [I,G,I,E,A,E,H,R,O,S,L,_,W,S,R,I,F,G,I,D,E,V,D,E,Y,E,S,R,I,A,E,U,A,G,I,L,H,D,E,F,T,O,T,T,U,N,T,I,O,I,L,_,A,A,V,P,C,N,E,R,W,K,I,E,B,A,R,A,L,Z,O,O,A,R,U,M,O,A,U,T,X,P,C]}, nr turns:1, }
ghci> import Data.Aeson
ghci> encode $ gameBoard g'
"[[[7,7],\"T\"],[[7,8],\"O\"],[[7,9],\"E\"]]"
ghci> eitherDecode $ encode $ gameBoard g' :: Either String Board
Left "when expecting a record (:*:), encountered String instead"

And the relevant definitions:
From Board.hs
data Board = Board {
  contents :: (Array Point Square)
} deriving (Eq, Ord, Generic, Show)

instance ToJSON Board where
  toJSON (Board b) = toJSON . fmap g . filter f $ A.assocs b where
    f (_,s) = Maybe.isJust $ tile s
    g (p,s) = (p,tile s)

instance FromJSON Board where
  parseJSON = withArray "Board" $ \arr ->
    Board . (newBoard //) <$> mapM parseJSON (V.toList arr)

From Square.hs
data Square = Square {
  tile      :: Maybe Tile,
  bonus     :: Bonus,
  squarePos :: Point
} deriving (Eq, Ord, Generic, ToJSON, FromJSON)

It seems that the Board parser is expecting to parse its list of Squares using the derived FromJSON instance for Square, instead of reversing the process used to encode the squares in Board's ToJSON instance

closing this since we merged the fix in


Keep getting log messages despite log level 0

It's been a while since I check my Pi running Homebridge and I was updating my plugins today. On the Status page I'm getting continuous (multiple per second) log messages from the P1 plugin. I've set the Log Level of the Electricity accessory to 0 in the Eve app, but no change. The log does state
[31/03/2023, 14:23:06] [P1] Electricity: Log Level: changed to 0 (from 1)
Maybe something caused by the latest Apple updates?

No, this is Homebridge stuff, nothing to do with iOS, etc. versions.  What messages do you get after that "Log Level: changed to 0" message?

It looks like this:
[31/03/2023, 18:12:20] [P1] Electricity: Log Level: changed to 0 (from 1)
2023-03-31T16:12:21.029Z ciao:Responder Sending response via unicast to {"address":"<IP_ADDRESS>","port":5353,"interface":"eth0"} (took 6 ms): [PTR,PTR,PTR,PTR] answers and [TXT,SRV,A,AAAA,AAAA,NSEC,NSEC,TXT,SRV,A,AAAA,AAAA,NSEC,NSEC,TXT,SRV,A,AAAA,AAAA,NSEC,NSEC,TXT,SRV,A,AAAA,AAAA,NSEC,NSEC] additionals with size 1398B (UPS: 1440)
2023-03-31T16:12:21.030Z ciao:Responder Sending response via unicast to {"address":"<IP_ADDRESS>","port":5353,"interface":"eth0"} (took 7 ms): [PTR,PTR,PTR,PTR] answers and [TXT,SRV,A,AAAA,AAAA,NSEC,NSEC,TXT,SRV,A,AAAA,AAAA,NSEC,NSEC,TXT,SRV,A,AAAA,AAAA,NSEC,NSEC,TXT,SRV,A,AAAA,AAAA,NSEC,NSEC] additionals with size 1316B (UPS: 1440)
[31/03/2023, 18:12:21] [P1] Electricity Phase 1: Consumption: set to 1254 W (from 1247 W)
[31/03/2023, 18:12:21] [P1] Electricity Phase 1: Voltage: set to 227.9 V (from 228 V)
[31/03/2023, 18:12:21] [P1] Electricity Phase 2: Voltage: set to 228.8 V (from 229 V)
[31/03/2023, 18:12:21] [P1] Electricity Phase 3: Voltage: set to 228.5 V (from 228.6 V)
[31/03/2023, 18:12:21] [P1] Electricity Delivered Phase 3: Consumption: set to 70 W (from 78 W)
[31/03/2023, 18:12:22] [P1] Electricity Phase 1: Consumption: set to 1245 W (from 1254 W)
[31/03/2023, 18:12:22] [P1] Electricity Phase 1: Voltage: set to 228.1 V (from 227.9 V)
[31/03/2023, 18:12:22] [P1] Electricity Phase 2: Consumption: set to 78 W (from 79 W)
[31/03/2023, 18:12:22] [P1] Electricity Phase 2: Voltage: set to 229.1 V (from 228.8 V)
[31/03/2023, 18:12:22] [P1] Electricity Phase 3: Voltage: set to 228.7 V (from 228.5 V)
[31/03/2023, 18:12:22] [P1] Electricity Delivered Phase 3: Consumption: set to 79 W (from 70 W)

Thanks.  Looks like the accessory for the phases doesn’t sync the log level to the electricity accessory.

In v1.3.5.

Just installed but now P1 throws errors (so fast I can’t even copy & paste from the status screen in HB) and I need to disable the plugin for HomeBridge to work. I got the lines below from a screenshot I took:
[09/04/2023, 10:35:43] [P1] ISK5\2M550T-1012 v5.0
[09/04/2023,
10:35:431
[P11 Electricity: Configured Name: warning: 7 listeners
Hostname
homebridge
[09/04/2023,
10:35:43] [P1] Electricity: On: warning: 7 listeners
[09/04/2023, 10:35:43] (P1] Electricity: Log Level: warning: 7 listeners
IPv4 (eth0)
<IP_ADDRESS>
[09/04/2023, 10:35:43] (P1] Electricity History: Configured Name: warning:
7 listeners
[09/04/2023, 10:35:43] (P] Electricity History: History Request: warning: 7 listeners
IPv6 (eth0)
fabd:3f06:28d:4369:81c:9a77:c
[09/04/2023,
10:35:431
[P11 Electricity History: SetTime: warning: 7 listeners
[09/04/2023,
10:35:431 P11 warning: TypeError: delegate: not an AccessoryDelegate
Node.is Version v18.15.0
ElectricityDetails.inheritLogLevel
Lib/node modules /homebridge-pl/node modules /homebridge
-lib/lib/AccessoryDelegate.is:288:13)
User
pi
at new ElectricityDetails (/usr/local/lib/node modules /homebridge-pl/lib/PlAccessory.is:69:10 ) at Electricity.check (/usr/local/lib/node modules /homebridge-pl/lib/PlAccessory. is:29:24)
Storage Path /var/lib/homebridge
at new Electricity (/usr/local/lib/node modules /homebridge-pl/lib/PlAccessory.is:56:10 ) at PIPlatform.onData (/usr/local/lib/node modules /homebridge-pl/lib/PIPlatform. is: 181:26)
Config Path /var/lib/homebridge/config.son
at PIClient.<anonymous> (/usr/local/lib/node modules /homebridge-pl/lib/PIPlatform.is: 117:40)
Service Mode
Yes
at PIClient.emit (node:events: 513:28 ) at PIClient.emit (node: domain: 489: 12)
at PiClient.parseTelegram (/usr/local/lib/node_ modules /homebridge-pl/lib/PIClient.js:682:12)
ReadlineParser.
<anonymous> (/usr/local/lib/node modules /homebridge-pl/lib/PiClient. is:424:51)

Hm, looks like the inheritLogLevel() is called a bit too early, before the main Electricity accessory has initialised.

Could you try beta v1.3.6-0?  I don't have 3-phase electricity, so it's hard for me to test.

Just tried and the beta fixes the issue, and now the log level = 0 command stops the continuous logging as expected. So this is the one I think! Thanks a lot of the rapid fix during Easter, much appreciated.

Published v1.3.6, and removed v1.3.5 and the beta.


is it possible setting second unit of expiration date ??

Hi, I'm David.
It's very nice module of cache!
I searched on this title at google or issue pages.
first of all, I was setting maxCachePeriodInSecond = 10 because of test, then I want to remove data from my local disk. but after 10 second it still alive in my disk.
At the page of download image page
var cache = ImageCache(name: "myReviewCache")
cache.maxCachePeriodInSecond = 10

let resource = ImageResource(downloadURL: URL(string : imgUrl)!, cacheKey: imgUrl)
cell.reviewImage.kf.setImage(with: resource, options : [.targetCache(cache)])

After I'm going other page . and then access var cache = ImageCache(name: "myReviewCache").
let a = cache.isImageCached(forKey: "www.example.com/test.jpeg")
 print(a)

CacheCheckResult(cached: true, cacheType: Optional(Kingfisher.CacheType.disk))
So, I don't know is it right way to expiration date..

The maxCachePeriodInSecond does not mean the cache file could be removed just after the period. It is a reference duration for Kingfisher to determine whether a cached file could be removed or not. To actually remove the expired cache, you need to switch your app to background or call cleanExpiredDiskCache on ImageCache.

@onevcat Thanks'
hum,, in other words, just checking what the saved cache is removed or not?
the store is not removed, just check cache file for reference of doing other work??
is that??

I am not sure I could understand your comment.
In other words, maxCachePeriodInSecond does not play as a timer to count down for removing the cached files. It defines a reference date that Kingfisher could check with it when removing cache.

@onevcat Ok..
Thank you!
eventually, If I should remove cache, Only one to use cleanDiskCache function. :)
Ok, I got it thanks


Match, Compare, or Select? An Investigation of Large Language Models for Entity Matching

You may find our investigation helpful ;)
https://arxiv.org/abs/2405.16884
https://github.com/tshu-w/LLM4EM

Thank you @tshu-w for sharing your work! This is interesting result. Let @daiwaid and I take a closer look at your findings and get back to you.


Table icons are rendering off page

Note sure where this was introduced. The table icons seem to be rendering out of page.

Per @jeffpamer This was introduced in https://github.com/NASA-AMMOS/aerie-ui/commit/bb5dadb9a9234bedc01af8869a39524c33ec4636


Where can I get Cap4M?

Where can I get Cap4M?

You can refer to GLIP to see if they've released the data

Thank you! But I didn't see GLIP release Cap4M

Thank you! But I didn't see GLIP release Cap4M

Maybe you can email them for more details

Where can I get Cap4M?

Did you get Cap4M?

The author said that he had no access to Cap4M

perhaps the cap4M is a leaky dataset to the benchmarks ?

The Cap4M is a 4M image-text pairs collected from the web with boxes generated by GLIP-T(C) in [13], and CC (Conceptual Captions) + SBU (with 1M data).