Warning "Ignoring unknown key in TOML for plugin" is shown when starting containerd 2.0 with version 2 config

Description
When starting containerd with a config file version 2, I see several unknown fields error:
WARN[2024-11-06T15:52:27.449046033+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=disable_cgroup plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449066423+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=disable_tcp_service plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449078957+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=enable_tls_streaming plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449089784+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=max_concurrent_downloads plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449099888+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=sandbox_image plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449110705+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=stats_collect_period plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449121844+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=stream_idle_timeout plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449131400+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=stream_server_address plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449141472+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=stream_server_port plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449152087+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=systemd_cgroup plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449162564+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd disable_snapshot_annotations" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449173025+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd discard_unpacked_layers" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449184163+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd no_pivot" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449194667+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd snapshotter" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449204685+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd default_runtime" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449215420+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd runtimes runc runtime_engine" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449226788+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd runtimes runc runtime_root" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449237446+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd untrusted_workload_runtime" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449248379+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=image_decryption plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449258337+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=registry plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449269320+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="registry mirrors" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449280204+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="registry mirrors docker.io" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449289981+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=x509_key_pair_streaming plugin=io.containerd.cri.v1.runtime

@AkihiroSuda asked me to report this, as even version 1 should be migrated.
Steps to reproduce the issue

Copy the containerd config I posted here and name it test.toml
Copy it to the root of the containerd repo
On the containerd repo, run: make && sudo make install && sudo bin/containerd --config test.toml
You will see the messages I pasted as containerd boots, no need to do anything else

Describe the results you received and expected
I expected the whole config was migrated fine. Although I'm not 100% sure this means it is not, it seems it isn't. If it is, then probably we should improve the error messages in some way
What version of containerd are you using?
2.0.0
Any other relevant information
Here is the full output when starting containerd with that config, in case it helps:
INFO[2024-11-06T15:52:27.432336139+01:00] starting containerd                           revision=207ad711eabd375a01713109a8a197d197ff6542 version=v2.0.0-rc.6-74-g207ad711e
WARN[2024-11-06T15:52:27.444636618+01:00] Configuration migrated from version 2, use `containerd config migrate` to avoid migration  t="14.462µs"
INFO[2024-11-06T15:52:27.444684960+01:00] loading plugin                                id=io.containerd.image-verifier.v1.bindir type=io.containerd.image-verifier.v1
INFO[2024-11-06T15:52:27.444714631+01:00] loading plugin                                id=io.containerd.internal.v1.opt type=io.containerd.internal.v1
INFO[2024-11-06T15:52:27.444761202+01:00] loading plugin                                id=io.containerd.warning.v1.deprecations type=io.containerd.warning.v1
INFO[2024-11-06T15:52:27.444780916+01:00] loading plugin                                id=io.containerd.content.v1.content type=io.containerd.content.v1
INFO[2024-11-06T15:52:27.445068473+01:00] loading plugin                                id=io.containerd.snapshotter.v1.blockfile type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445110906+01:00] skip loading plugin                           error="no scratch file generator: skip plugin" id=io.containerd.snapshotter.v1.blockfile type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445125826+01:00] loading plugin                                id=io.containerd.snapshotter.v1.btrfs type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445383328+01:00] skip loading plugin                           error="path /var/lib/containerd-rata/io.containerd.snapshotter.v1.btrfs (ext4) must be a btrfs filesystem to be used with the btrfs snapshotter: skip plugin" id=io.containerd.snapshotter.v1.btrfs type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445406911+01:00] loading plugin                                id=io.containerd.snapshotter.v1.devmapper type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445449267+01:00] skip loading plugin                           error="devmapper not configured: skip plugin" id=io.containerd.snapshotter.v1.devmapper type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445465596+01:00] loading plugin                                id=io.containerd.snapshotter.v1.native type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445501429+01:00] loading plugin                                id=io.containerd.snapshotter.v1.overlayfs type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445637690+01:00] loading plugin                                id=io.containerd.snapshotter.v1.zfs type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445672898+01:00] skip loading plugin                           error="lstat /var/lib/containerd-rata/io.containerd.snapshotter.v1.zfs: no such file or directory: skip plugin" id=io.containerd.snapshotter.v1.zfs type=io.containerd.snapshotter.v1
INFO[2024-11-06T15:52:27.445690004+01:00] loading plugin                                id=io.containerd.event.v1.exchange type=io.containerd.event.v1
INFO[2024-11-06T15:52:27.445737497+01:00] loading plugin                                id=io.containerd.monitor.task.v1.cgroups type=io.containerd.monitor.task.v1
INFO[2024-11-06T15:52:27.446016308+01:00] loading plugin                                id=io.containerd.metadata.v1.bolt type=io.containerd.metadata.v1
INFO[2024-11-06T15:52:27.446057655+01:00] metadata content store policy set             policy=shared
INFO[2024-11-06T15:52:27.448094651+01:00] loading plugin                                id=io.containerd.gc.v1.scheduler type=io.containerd.gc.v1
INFO[2024-11-06T15:52:27.448202400+01:00] loading plugin                                id=io.containerd.differ.v1.walking type=io.containerd.differ.v1
INFO[2024-11-06T15:52:27.448219600+01:00] loading plugin                                id=io.containerd.lease.v1.manager type=io.containerd.lease.v1
INFO[2024-11-06T15:52:27.448233450+01:00] loading plugin                                id=io.containerd.service.v1.containers-service type=io.containerd.service.v1
INFO[2024-11-06T15:52:27.448246197+01:00] loading plugin                                id=io.containerd.service.v1.content-service type=io.containerd.service.v1
INFO[2024-11-06T15:52:27.448269507+01:00] loading plugin                                id=io.containerd.service.v1.diff-service type=io.containerd.service.v1
INFO[2024-11-06T15:52:27.448304046+01:00] loading plugin                                id=io.containerd.service.v1.images-service type=io.containerd.service.v1
INFO[2024-11-06T15:52:27.448328735+01:00] loading plugin                                id=io.containerd.service.v1.introspection-service type=io.containerd.service.v1
INFO[2024-11-06T15:52:27.448340574+01:00] loading plugin                                id=io.containerd.service.v1.namespaces-service type=io.containerd.service.v1
INFO[2024-11-06T15:52:27.448362802+01:00] loading plugin                                id=io.containerd.service.v1.snapshots-service type=io.containerd.service.v1
INFO[2024-11-06T15:52:27.448372855+01:00] loading plugin                                id=io.containerd.shim.v1.manager type=io.containerd.shim.v1
INFO[2024-11-06T15:52:27.448386140+01:00] loading plugin                                id=io.containerd.runtime.v2.task type=io.containerd.runtime.v2
INFO[2024-11-06T15:52:27.448446718+01:00] loading plugin                                id=io.containerd.service.v1.tasks-service type=io.containerd.service.v1
INFO[2024-11-06T15:52:27.448463076+01:00] loading plugin                                id=io.containerd.grpc.v1.containers type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.448475087+01:00] loading plugin                                id=io.containerd.grpc.v1.content type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.448486106+01:00] loading plugin                                id=io.containerd.grpc.v1.diff type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.448496186+01:00] loading plugin                                id=io.containerd.grpc.v1.events type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.448508545+01:00] loading plugin                                id=io.containerd.grpc.v1.images type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.448519955+01:00] loading plugin                                id=io.containerd.grpc.v1.introspection type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.448533112+01:00] loading plugin                                id=io.containerd.grpc.v1.leases type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.448545231+01:00] loading plugin                                id=io.containerd.grpc.v1.namespaces type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.448557656+01:00] loading plugin                                id=io.containerd.sandbox.store.v1.local type=io.containerd.sandbox.store.v1
INFO[2024-11-06T15:52:27.448568449+01:00] loading plugin                                id=io.containerd.cri.v1.images type=io.containerd.cri.v1
WARN[2024-11-06T15:52:27.448645307+01:00] `mirrors` is deprecated, please use `config_path` instead
INFO[2024-11-06T15:52:27.448701638+01:00] Get image filesystem path "/var/lib/containerd-rata/io.containerd.snapshotter.v1.overlayfs" for snapshotter "overlayfs"
INFO[2024-11-06T15:52:27.448712689+01:00] Start snapshots syncer
INFO[2024-11-06T15:52:27.448731828+01:00] loading plugin                                id=io.containerd.cri.v1.runtime type=io.containerd.cri.v1
WARN[2024-11-06T15:52:27.449046033+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=disable_cgroup plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449066423+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=disable_tcp_service plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449078957+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=enable_tls_streaming plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449089784+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=max_concurrent_downloads plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449099888+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=sandbox_image plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449110705+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=stats_collect_period plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449121844+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=stream_idle_timeout plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449131400+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=stream_server_address plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449141472+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=stream_server_port plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449152087+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=systemd_cgroup plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449162564+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd disable_snapshot_annotations" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449173025+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd discard_unpacked_layers" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449184163+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd no_pivot" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449194667+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd snapshotter" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449204685+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd default_runtime" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449215420+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd runtimes runc runtime_engine" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449226788+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd runtimes runc runtime_root" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449237446+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd untrusted_workload_runtime" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449248379+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=image_decryption plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449258337+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=registry plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449269320+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="registry mirrors" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449280204+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="registry mirrors docker.io" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-06T15:52:27.449289981+01:00] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=x509_key_pair_streaming plugin=io.containerd.cri.v1.runtime
INFO[2024-11-06T15:52:27.449513151+01:00] starting cri plugin                           config="{\"containerd\":{\"defaultRuntimeName\":\"runc\",\"runtimes\":{\"runc\":{\"runtimeType\":\"io.containerd.runc.v2\",\"runtimePath\":\"\",\"PodAnnotations\":null,\"ContainerAnnotations\":null,\"options\":{\"BinaryName\":\"\",\"CriuImagePath\":\"\",\"CriuWorkPath\":\"\",\"IoGid\":0,\"IoUid\":0,\"NoNewKeyring\":false,\"Root\":\"\",\"ShimCgroup\":\"\"},\"privileged_without_host_devices\":false,\"privileged_without_host_devices_all_devices_allowed\":false,\"baseRuntimeSpec\":\"\",\"cniConfDir\":\"\",\"cniMaxConfNum\":0,\"snapshotter\":\"\",\"sandboxer\":\"podsandbox\",\"io_type\":\"\"}},\"ignoreBlockIONotEnabledErrors\":false,\"ignoreRdtNotEnabledErrors\":false},\"cni\":{\"binDir\":\"/opt/cni/bin\",\"confDir\":\"/etc/cni/net.d\",\"maxConfNum\":1,\"setupSerially\":false,\"confTemplate\":\"\",\"ipPref\":\"\",\"useInternalLoopback\":false},\"enableSelinux\":false,\"selinuxCategoryRange\":1024,\"maxContainerLogSize\":16384,\"disableApparmor\":false,\"restrictOOMScoreAdj\":false,\"disableProcMount\":false,\"unsetSeccompProfile\":\"\",\"tolerateMissingHugetlbController\":true,\"disableHugetlbController\":true,\"device_ownership_from_security_context\":false,\"ignoreImageDefinedVolumes\":false,\"netnsMountsUnderStateDir\":false,\"enableUnprivilegedPorts\":true,\"enableUnprivilegedICMP\":true,\"enableCDI\":true,\"cdiSpecDirs\":[\"/etc/cdi\",\"/var/run/cdi\"],\"drainExecSyncIOTimeout\":\"0s\",\"ignoreDeprecationWarnings\":null,\"containerdRootDir\":\"/var/lib/containerd-rata\",\"containerdEndpoint\":\"/run/containerd-rata/containerd.sock\",\"rootDir\":\"/var/lib/containerd-rata/io.containerd.grpc.v1.cri\",\"stateDir\":\"/run/containerd-rata/io.containerd.grpc.v1.cri\"}"
INFO[2024-11-06T15:52:27.449564715+01:00] loading plugin                                id=io.containerd.podsandbox.controller.v1.podsandbox type=io.containerd.podsandbox.controller.v1
INFO[2024-11-06T15:52:27.449628638+01:00] loading plugin                                id=io.containerd.sandbox.controller.v1.shim type=io.containerd.sandbox.controller.v1
INFO[2024-11-06T15:52:27.449673321+01:00] loading plugin                                id=io.containerd.grpc.v1.sandbox-controllers type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.449698109+01:00] loading plugin                                id=io.containerd.grpc.v1.sandboxes type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.449710850+01:00] loading plugin                                id=io.containerd.grpc.v1.snapshots type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.449721616+01:00] loading plugin                                id=io.containerd.streaming.v1.manager type=io.containerd.streaming.v1
INFO[2024-11-06T15:52:27.449734803+01:00] loading plugin                                id=io.containerd.grpc.v1.streaming type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.449747700+01:00] loading plugin                                id=io.containerd.grpc.v1.tasks type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.450275216+01:00] loading plugin                                id=io.containerd.transfer.v1.local type=io.containerd.transfer.v1
INFO[2024-11-06T15:52:27.450553057+01:00] loading plugin                                id=io.containerd.grpc.v1.transfer type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.450601122+01:00] loading plugin                                id=io.containerd.grpc.v1.version type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.450629340+01:00] loading plugin                                id=io.containerd.monitor.container.v1.restart type=io.containerd.monitor.container.v1
INFO[2024-11-06T15:52:27.450851656+01:00] loading plugin                                id=io.containerd.tracing.processor.v1.otlp type=io.containerd.tracing.processor.v1
INFO[2024-11-06T15:52:27.450916020+01:00] skip loading plugin                           error="skip plugin: tracing endpoint not configured" id=io.containerd.tracing.processor.v1.otlp type=io.containerd.tracing.processor.v1
INFO[2024-11-06T15:52:27.450944637+01:00] loading plugin                                id=io.containerd.internal.v1.tracing type=io.containerd.internal.v1
INFO[2024-11-06T15:52:27.451060741+01:00] skip loading plugin                           error="skip plugin: tracing endpoint not configured" id=io.containerd.internal.v1.tracing type=io.containerd.internal.v1
INFO[2024-11-06T15:52:27.451099882+01:00] loading plugin                                id=io.containerd.ttrpc.v1.otelttrpc type=io.containerd.ttrpc.v1
INFO[2024-11-06T15:52:27.451218648+01:00] loading plugin                                id=io.containerd.grpc.v1.healthcheck type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.451486930+01:00] loading plugin                                id=io.containerd.nri.v1.nri type=io.containerd.nri.v1
INFO[2024-11-06T15:52:27.451721185+01:00] runtime interface created
INFO[2024-11-06T15:52:27.452398434+01:00] created NRI interface
INFO[2024-11-06T15:52:27.452448020+01:00] loading plugin                                id=io.containerd.grpc.v1.cri type=io.containerd.grpc.v1
INFO[2024-11-06T15:52:27.452498843+01:00] Connect containerd service
INFO[2024-11-06T15:52:27.452541404+01:00] using experimental NRI integration - disable nri plugin to prevent this
INFO[2024-11-06T15:52:27.463816836+01:00] Start subscribing containerd event
INFO[2024-11-06T15:52:27.463902619+01:00] serving...                                    address=/run/containerd-rata/containerd.sock.ttrpc
INFO[2024-11-06T15:52:27.463956373+01:00] Start recovering state
INFO[2024-11-06T15:52:27.463965203+01:00] serving...                                    address=/run/containerd-rata/containerd.sock
INFO[2024-11-06T15:52:27.588657238+01:00] Start event monitor
INFO[2024-11-06T15:52:27.588699117+01:00] Start cni network conf syncer for default
INFO[2024-11-06T15:52:27.588706748+01:00] Start streaming server
INFO[2024-11-06T15:52:27.588721606+01:00] Registered namespace "k8s.io" with NRI
INFO[2024-11-06T15:52:27.588729124+01:00] runtime interface starting up...
INFO[2024-11-06T15:52:27.588734430+01:00] starting plugins...
INFO[2024-11-06T15:52:27.588745166+01:00] Synchronizing NRI (plugin) with current runtime state
INFO[2024-11-06T15:52:27.588960640+01:00] containerd successfully booted in 0.157354s

Show configuration if it is related to CRI plugin.
It is not related to the CRI plugin, but I'm just using this to paste my config.
version = 2
root = "/var/lib/containerd"
state = "/run/containerd"
plugin_dir = ""
disabled_plugins = []
required_plugins = []
oom_score = 0

[grpc]
  address = "/run/containerd/containerd.sock"
  tcp_address = ""
  tcp_tls_cert = ""
  tcp_tls_key = ""
  uid = 0
  gid = 0
  max_recv_message_size = 16777216
  max_send_message_size = 16777216

[ttrpc]
  address = ""
  uid = 0
  gid = 0

[debug]
  address = ""
  uid = 0
  gid = 0
  level = ""

[metrics]
  address = ""
  grpc_histogram = false

[cgroup]
  path = ""

[timeouts]
  "io.containerd.timeout.shim.cleanup" = "5s"
  "io.containerd.timeout.shim.load" = "5s"
  "io.containerd.timeout.shim.shutdown" = "3s"
  "io.containerd.timeout.task.state" = "2s"

[plugins]
  [plugins."io.containerd.gc.v1.scheduler"]
    pause_threshold = 0.02
    deletion_threshold = 0
    mutation_threshold = 100
    schedule_delay = "0s"
    startup_delay = "100ms"
  [plugins."io.containerd.grpc.v1.cri"]
    disable_tcp_service = true
    stream_server_address = "<IP_ADDRESS>"
    stream_server_port = "0"
    stream_idle_timeout = "4h0m0s"
    enable_selinux = false
    selinux_category_range = 1024
    sandbox_image = "k8s.gcr.io/pause:3.2"
    stats_collect_period = 10
    systemd_cgroup = false
    enable_tls_streaming = false
    max_container_log_line_size = 16384
    disable_cgroup = false
    disable_apparmor = false
    # XXX: rata. Added to test: https://github.com/containerd/containerd/pull/8779
    #enable_unprivileged_icmp = true
    restrict_oom_score_adj = false
    max_concurrent_downloads = 3
    disable_proc_mount = false
    unset_seccomp_profile = ""
    tolerate_missing_hugetlb_controller = true
    disable_hugetlb_controller = true
    ignore_image_defined_volumes = false
    [plugins."io.containerd.grpc.v1.cri".containerd]
      snapshotter = "overlayfs"
      default_runtime_name = "runc"
      no_pivot = false
      disable_snapshot_annotations = true
      discard_unpacked_layers = false
      [plugins."io.containerd.grpc.v1.cri".containerd.default_runtime]
        runtime_type = ""
        runtime_engine = ""
        runtime_root = ""
        privileged_without_host_devices = false
        base_runtime_spec = ""
      [plugins."io.containerd.grpc.v1.cri".containerd.untrusted_workload_runtime]
        runtime_type = ""
        runtime_engine = ""
        runtime_root = ""
        privileged_without_host_devices = false
        base_runtime_spec = ""
      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]
        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
          runtime_type = "io.containerd.runc.v2"
          runtime_engine = ""
          runtime_root = ""
          privileged_without_host_devices = false
          base_runtime_spec = ""
          [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
    [plugins."io.containerd.grpc.v1.cri".cni]
      bin_dir = "/opt/cni/bin"
      conf_dir = "/etc/cni/net.d"
      max_conf_num = 1
      conf_template = ""
    [plugins."io.containerd.grpc.v1.cri".registry]
      [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
        [plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"]
          endpoint = ["https://registry-1.docker.io"]
    [plugins."io.containerd.grpc.v1.cri".image_decryption]
      key_model = ""
    [plugins."io.containerd.grpc.v1.cri".x509_key_pair_streaming]
      tls_cert_file = ""
      tls_key_file = ""
  #[plugins."io.containerd.internal.v1.opt"]
  #  path = "/opt/containerd"
  [plugins."io.containerd.internal.v1.tracing"]
    sampling_ratio = 1.0
    service_name = "containerd"
  [plugins."io.containerd.internal.v1.restart"]
    interval = "10s"
  [plugins."io.containerd.metadata.v1.bolt"]
    content_sharing_policy = "shared"
  [plugins."io.containerd.monitor.v1.cgroups"]
    no_prometheus = false
  [plugins."io.containerd.runtime.v1.linux"]
    shim = "containerd-shim"
    runtime = "runc"
    runtime_root = ""
    no_shim = false
    shim_debug = false
  [plugins."io.containerd.runtime.v2.task"]
    platforms = ["linux/amd64"]
  [plugins."io.containerd.service.v1.diff-service"]
    default = ["walking"]
  [plugins."io.containerd.snapshotter.v1.btrfs"]
    root_path = ""
  [plugins."io.containerd.snapshotter.v1.devmapper"]
    root_path = ""
    pool_name = ""
    base_image_size = ""
    async_remove = false
  [plugins."io.containerd.snapshotter.v1.native"]
    root_path = ""
  [plugins."io.containerd.snapshotter.v1.overlayfs"]
    root_path = ""
    # XXX: rata. Added to test this func. Ignored in kernels > 5.19.
    slow_chown = true
  [plugins."io.containerd.tracing.processor.v1.otlp"]
    endpoint = ""
    insecure = false
    protocol = ""

I expected the whole config was migrated fine. Although I'm not 100% sure this means it is not, it seems it isn't. If it is, then probably we should improve the error messages in some way

I believe it's migrated. This error message can be improved. IIRC this error doesn't acctually mean Ignoring unknown key , instead it should mean "toml file missing a field defined in the given config struct" (since the toml is v2 while the config struct is v3).
https://github.com/containerd/containerd/blob/ebda6bc8730bc3ed763eb5d06501174ef2ebd1ee/cmd/containerd/server/config/config.go#L272-L278
The config migration is done in 2 places:

The main config (non plugins): when containerd reads the config file

(no plugin migration since plugins are defined as map[string]interface{}. So the actual plugin config is still v2 now.
https://github.com/containerd/containerd/blob/ebda6bc8730bc3ed763eb5d06501174ef2ebd1ee/cmd/containerd/server/config/config.go#L316-L319

Plugin migrations

When the containerd server starts, it loads plugins and runs the migration for every plugin, if the plugin defines a migration function
https://github.com/containerd/containerd/blob/ebda6bc8730bc3ed763eb5d06501174ef2ebd1ee/cmd/containerd/server/server.go#L251-L259

I took another look. The warnings all come from io.containerd.cri.v1.runtime

I expected the whole config was migrated fine. Although I'm not 100% sure this means it is not, it seems it isn't. If it is, then probably we should improve the error messages in some way

The whole config is migrated fine. The warning comes from some old toml keys that should've been deleted during the migration.
The reason is in io.containerd.cri.v1.runtime's config migration, it reads the whole original V2 CRI config and migrates it to V3 config. However, it didn't remove the fields that were deleted or moved to other service configs (like cri image service). And those old fields caused warnings.

read v2 cri config, migrate in place
https://github.com/containerd/containerd/blob/0be529a7c127baa7ac52935e43d8368db5c082ad/plugins/cri/runtime/plugin.go#L58-L64

only do minimum migration, didn't delete removed keys.
https://github.com/containerd/containerd/blob/0be529a7c127baa7ac52935e43d8368db5c082ad/plugins/cri/runtime/plugin.go#L211-L216

Same issue.
I used containerd v2.0.0 and copied the default version 2 config.toml from here.
and updated the last line to:
config_path = "/etc/containerd/certs.d"
I got the same warning message:
level=warning msg="Ignoring unknown key in TOML for plugin" error="strict mode: fields in the document are missing in the target struct" key=registry plugin=io.containerd.cri.v1.runtime

@yyu233

I got the same warning message:
level=warning msg="Ignoring unknown key in TOML for plugin" error="strict mode: fields in the document are missing in the target
struct" key=registry plugin=io.containerd.cri.v1.runtime

This is the same issue, I'm making a fix https://github.com/containerd/containerd/pull/10980.

nerdctl failed to pull from a mirror registry:

This config_path is only recognized by containerd cri, so nerdctl (or ctr) is not aware of that config. To make nerdctl work, you need to config nerdctl's hosts_dir: https://github.com/containerd/nerdctl/blob/main/docs/config.md#example

@rata I tried to fix this in https://github.com/containerd/containerd/pull/10980. With that change, only fields that cannot be migrated will be WARNed.
$ sudo ./bin/containerd --config ../test.toml
INFO[2024-11-25T03:09:18.766488174Z] loading plugin                                id=io.containerd.cri.v1.images type=io.containerd.cri.v1
WARN[2024-11-25T03:09:18.766626528Z] `mirrors` is deprecated, please use `config_path` instead
INFO[2024-11-25T03:09:18.766715440Z] Get image filesystem path "/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs" for snapshotter "overlayfs"
INFO[2024-11-25T03:09:18.766819393Z] Start snapshots syncer
INFO[2024-11-25T03:09:18.766951347Z] loading plugin                                id=io.containerd.cri.v1.runtime type=io.containerd.cri.v1
WARN[2024-11-25T03:09:18.767179117Z] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=disable_cgroup plugin=io.containerd.cri.v1.runtime
WARN[2024-11-25T03:09:18.767207334Z] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key=systemd_cgroup plugin=io.containerd.cri.v1.runtime
WARN[2024-11-25T03:09:18.767218790Z] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd no_pivot" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-25T03:09:18.767233154Z] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd default_runtime" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-25T03:09:18.767249632Z] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd runtimes runc runtime_engine" plugin=io.containerd.cri.v1.runtime
WARN[2024-11-25T03:09:18.767268965Z] Ignoring unknown key in TOML for plugin       error="strict mode: fields in the document are missing in the target struct" key="containerd untrusted_workload_runtime" plugin=io.containerd.cri.v1.runtime


PLT-6453 Migrate installed_incoming_webhooks.jsx to be pure and use Redux

Summary
Fixes the issue of no teamId as part of incoming webhook API
Pull Request Link
https://github.com/mattermost/mattermost-webapp/pull/60
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Has redux changes (please link)

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).


Start Menu Icon and System tray Disappear in Segmented mode

Describe the bug
When I activate the segmented mode, the start menu icon and system tray completely disappear
To Reproduce
Activate segmented mode
Screenshots

Desktop (please complete the following information):

OS: Windows 10 64-bit
Version 21H1

Additional context
I'm using the rainmeter skin, though I did try it with the standalone configurator and got the same result

Yeah I've tried that

So this is the end huh?  My tray with the clock, and date stuff disappears.  Sometimes it's just invisible, right clicking seems to do what it always does, sometimes it's seems to be all the way gone. Sometimes it will stay up for hours. Odd.  I've no idea how to reproduce the...bug?  awesome program though.

same bug


Cannot get transparent window.

App.vue

in index.js I have set transparent and frameless window.
I still get no transparency? It's my mistake or how is that working?
Help is awesome.

@azurinko
Setting frame: false and transparent: true should be all you need. One thing to know is that if your dev tools are attached to the window transparency will be disabled. Detaching the dev tools to a separate window will fix that.

I wish I could solve it into transperent... also main app.vue wich contains router is body totally transparent...
Offtopic: I wanna make some totally working thing about window frame(so I can have my github nonempty and commit something useful.), I already solved that title bar's title is automatically changed on document.title change, but I cannot find anything on events like minimalization maximalization normalization etc... of a window... I can perform those actions to them, but it's not sufficient, if I call event on a button it doesn't get called if it's maximalized other way.

The BrowserWindow API provides all the events you could possibly need, including those for minimizing and maximizing. https://electron.atom.io/docs/api/browser-window/
Once you get ahold of the current browser window, you can listen to any event since the api extends an EventEmitter.
Get access to current window and listen for maximize (renderer process)
import electron from 'electron'

// https://electron.atom.io/docs/api/browser-window/#browserwindowgetfocusedwindow
const mainWindow = electron.remote.BrowserWindow.getFocusedWindow()

// https://electron.atom.io/docs/api/browser-window/#event-maximize
mainWindow.on('maximize', e => {
  // do something
})

Going to close since this is not a direct issue with electron-vue.

I have same problem,I tried
'mainWindow.webContents.closeDevTools();' and 'mainWindow.webContents.openDevTools({mode:"detach"});',
set css => 'html, body{ background:  rgba(0,0,0,0)}'，still no transparent.
when i set css => 'html, body{ background:  rgba(0,0,0,0.1)}' , got transparent,but this is not totally transparent, i don't know why...

I solved this problem. I use iview and it set body #fff .....

After declaring transparency in the BrowserWindow API, add the following code to your vue component to remove the background:
<style> html, body{   background-color: transparent!important;   border-color: transparent!important; } </style>


Windows Bazel build broken?

Hi there, there seem to be 2 bugs in grpc/python_configure.bzl:

Quoting: The line
 cmd = '%s - %s' % (python_bin, print_lib)

doesn't handle spaces in paths, which are typical on Windows.
You can fix this by putting quotes around the command:
 cmd = '"%s" - %s' % (python_bin, print_lib)

However, it's better to avoid having to quote and escape strings in the first place, as follows:
 result = repository_ctx.execute(
     [_get_bash_bin(repository_ctx), "-c", '"$@"', '-', python_bin, "-", print_lib])

In the line
 python_import_lib_name = _get_python_import_lib_name, bin_path_key(
         repository_ctx, python_bin)

bin_path_key appears to be a string, which is not callable. Moreover, the argument order seems incorrect. I think the intended code was probably the following:
 python_import_lib_name = _get_python_import_lib_name(repository_ctx,
         python_bin, bin_path_key)

Fix for this: https://github.com/grpc/grpc/pull/20774

Thanks, that addresses the bin_key_path issue. The quoting issues also need to be fixed.
I just discovered a new quoting problem and added it to the initial post.

@mehrdadn PRs welcomed. :)

@gnossen I would, but unfortunately it comes with a fair bit more baggage than I'd like to carry for now.

Hi, has the quoting issue been fixed?


Minor update - missing '--name'

Minor update - missing '--name'

@egullbrandsson : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

Good catch. Thanks! #sign-off


Improve styling of update snackbar / toast / notification

UI Request -
Part of the way the platform works is that everything loaded is also cached so that the site will for the most part work offline or on low-bandwidth connections (and be overall more bandwidth friendly/efficient). When a user visits the site it first loads from the cache, and then in the background checks for updates which, if available will display the next time the user visits the site
The downside to this design pattern is that the user will only ever see the most up-to-date content after a page refresh. Therefore I've added a small prompt/notification to let the user know that new content is available. Assuming we want to keep this design pattern (strongly recommended from me as I think it is in line with our low-environmental-impact ethos... why download the same web page every time you visit it right?), then we could also make this notification look/feel a bit better.
You can get a feel for the default options available for the snackbar here:
https://material-ui.com/demos/snackbars/
@mattia-io could you communicate this to the design team?

This is the current default snackbar, I suggest we keep a similar format (message, reload button, close button).

Cool. Let me clear things.
Is this only happening only if new content is published while the user is on the page?
Let me try to example it out to see if I get it right.
I am user Y and I load the page with 3 documentations. I close the page and get on with my life. Two weeks later I go back to the site, which in the meanwhile has 5 documentations. As I load the cached version, by default, I will only see 3 documentations. Leave the site again. Come back in a day, no new documentations have been uploaded, this time I see 5 documentations.
Is that it? Did I get the functioning right?

No, it only happens when the developers push a new build which somehow changes the way information is displayed. For example a user loads the docs page, browses a bit, gets on with life, comes back, browses some more (no change), gets back on with life again, devs decide the title should actually be larger so changes code, commits new version, person returns and will see message to say new version of platform available.
There are essentially three different caching mechanisms, one for the data (which will always just update whilst on the page, no reload necessary), one for assets like images which we may or may not want to keep cached (harder to track changes if somebody uploads a new file with same url, but I think actually this wouldn’t happen as the file uploader provides a unique one each time), and one for core javascript/html files which will require refresh on change. Note we could not have any notification, but that would mean changes to the website aren’t shown until the user happens to next visit for themselves. There’s additional intermediate options which we will likely also use so that, for example if the user hasn’t visited the site in a week it will automatically just fetch the latest version and not bother trying to load a cached (and hence no message).
The reason you want to cache the core javascript/html is because otherwise it’s quite a waste of bandwidth, always loading the exact same files for the same content (but still pretty common practice for dynamic sites).

Current implementation is done. Closing.


Standardizing parser/constructor names

The contributing guidelines on safe constructors state:

Prefer fromString to parse.

But in header definitions we consistently use parse. Should we follow the guidelines or should we change them?

I've also noticed an ambiguity with the unsafe prefix - does unsafeParse on an invalid input throw an exception or return an invalid value? HttpCodec uses parseOrThrow - I like the clarity but I also like having the prominent unsafe prefix. How about using unsafeParseOrThrow or unsafeParseUnvalidated to indicate the unhappy-path behaviour?


Update composer version

Please,
update the require restriction for package composer/composer, it is in 1.1.2 version yet.

Hi @lainosantos, thanks for raising this issue. Recently, @nickveenhof contributed an update, so composer is current on 1.4.3.
Cheers!


I can't upload files

I can't upload files
files = ['out.csv', 'vix.csv']
pc.uploadfile(files)
this is the message it gives me
ValueError: Required parameter ``data, files`` is missing.
what does this refer to? Until yesterday I could upload files without problem

You have to do:
pc.uploadfile(files=files)
or
pc.uploadfile(files=['out.csv', 'vix.csv'])

Thanks @Rounak40 for answering this.


Change WorldClockAndroid / WorldClockIos samples to accept a CoroutineScope

Creating their own scope is clumsy.
https://github.com/cashapp/zipline/pull/692/files#r951659083

Closed by https://github.com/cashapp/zipline/pull/698


Use failure instead of std::error::Error

Migrate all errors in this crate to using failure: instead of implementing std::error::Error we should just implement failure::Fail instead

https://crates.io/crates/failure
https://crates.io/crates/failure_derive

failure is now deprecated, I’d recommend to close this issue and continue using the perfectly fine std::error::Error instead.

Yep, this was done in 5deb6af53b1e08e07345946a177311b64c475c22

Thanks!


No data

Data seems not to be properly parsed.

Stromgedacht API was returning inconsistent results, and in the meantime they have fixed it.


Weeks range selection (from same day of week, ex sat to sat)

I need to restrict the date range selection from a saturday to a future saturday (in other words the range can be only 7, 14, 21... days from the first picked saturday).
I've tried to enable only saturdays using the enable e disable options with a custom function call, but the problem is that the no range can be selected because all days in the middle from the two selectable saturdays are disabled.
There is an way/option to allow disabled dates inside the range (excluding start and end date that of course must be enabled) ?

Any solution?


Successfully deleted SWA still appears in the Resources view

V2 forward compatibility testing
After deleting a SWA and receiving a Delete Static Web App... succeeded Activity Log the SWA still appears in the tree view. Once you refresh, the SWA disappears as expected.

I checked Virtual Machines and this issue reproduces there too. I think I can fix this easily by adding some compat shim stuff in RGs

Fixed by https://github.com/microsoft/vscode-azureresourcegroups/pull/529


Add system test

system.add() recall during entity.addComp()
system.remove() recall during component.destroy()
system.remove() recall during entity.destroy()

update cocos-creator/engine-3d#54


App crashes when I try to open a Video

When I try to open a video from the gallery overview the app crashes.
This happenes since I updated from version 1.9.3 to 1.9.5. Also with the latest update (1.9.6) I can't open videos. Even version 1.9.3. doesn't work anymore.
I am now on Android 14 but even on 13 it didn't work.
I uploaded the system information and logs in a txt file to my cloud. Because it's to long to paste it here...
Here you can find the logs: https://cloud.famstrauss.org/s/W4rppHQsbtaY9DD
Thanks for your help!

Would this apply to you?

#722

Thank you very much. Enabling the toggle "disable_hardened_malloc" worked perfectly!


Instructions for BS4 and ng-cli

Instructions on how to set up ng2-bootstrap for Bootstrap 4 based on an angular-cli generated project.  This should hopefully remove the confusion a few people have over certain components not working when using Bootstrap 4.

Codecov Report

Merging #1714 into development will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development    #1714   +/-   ##
============================================
  Coverage        85.44%   85.44%
============================================
  Files               85       85
  Lines             2295     2295
  Branches           300      300
============================================
  Hits              1961     1961
  Misses             235      235
  Partials            99       99

Continue to review full report at Codecov.

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

Looks great, add a links to landing and readme.md files so it can be found
Huge work, thank you!

What do you mean by adding links to landing?  Can see where to add links in the .md files but cannot find a landing file.

It am generating landing from MD files

Added links to the new instructions to readme.md and getting-started.md

Awesome, thank you!


feat: add primer version checker

This script created for check if we are lagging behind the version Primer what published to npm. If it's true we need to manually update styles 😥. All Primer styles files after this merged should be live in ./public/styles/primer folder.
For more information read this note: https://hackmd.io/zZiYBmJuRsqTyDdrwluqbQ
/cc @electron/wg-website

@HashimotoYT Can you clarify on this point?

Why not bump it by add @primer/css?
Looks now Primer uses a single package instead of small packages, we can simply add @primer/css and take a needed style. But it still looks very risky, mostly if we have an error when updating @primer/css, we unable to fix it by updating styles locally. For now, I think we need manually port styles to repository instead of using npm version (but I'm open for discussion 💬).

Do we have a history of Primer breaking in such a way that would require us to completely replace one of its .scss files? If not, I'm strongly in favor of just installing @primer/css via npm and using it directly. The more of these check-and-update scripts we have (see also the generate-octicons script), the more complex the project becomes and the likely it is that we'll forget to check and update something.
(Also, even if we use @primer/css from npm, we can always copy over styles into the public folder if we really need to.)


i18n of IDE plugins - help, project-related and deploy

help plugin
projectConfigurator
projectWizard
deploy

deploy - currently internationalized
project configurator : has no impact with UI


fixing routes and 404 page

404 page will be addressed on a different PR
Fix route was merged via PR #166


calculate Cblock parallel per event

gains from parallelization are not sufficient to add code complexity. With bigger Buckets maybe this would help more, but we have not tested these yet.


Failed to open the source

Brief description of your issue

Calling any winget command results in an error message.
(base) ~> winget list
Failed to open the source; try the 'source reset' command if the problem persists.
An unexpected error occurred while executing the command:
0x8a15000f : Data required by the source is missing

Steps to reproduce
Entering any command like winget list or winget search.

Expected behavior
The command should execute without an error message

Actual behavior

(base) ~> winget list
Failed to open the source; try the 'source reset' command if the problem persists.
An unexpected error occurred while executing the command:
0x8a15000f : Data required by the source is missing

Environment
[winget --info]
Windows Package Manager version: 0.4.11391 Preview
Windows: Windows.Desktop version v10.0.19042.985
Package: Microsoft.DesktopAppInstaller version v1.11.11391.0

Any other software?

The same bug;
When run 'winget list'，return '0x8a15000f : Data required by the source is missing'

I had the same problem after updating to windows 11, the following from an Admin command prompt solved the problem:
winget source reset winget
winget source add --name winget --arg https://winget.azureedge.net/cache --type Microsoft.PreIndexed.Package

Now winget install from non-admin prompt works fine again.

@n-gao
We've published the v1.1 release candidate and updated our troubleshooting guide.
Can you confirm if this is still happening?

It is still happening


Dynamic modules

With this change the main runtime doesn't know anything about the Lua API or the set of modules and instead loads things dynamically using conventions similar to Lua.

The runtime is now able to find and load modules when they're required instead of loading a hardcoded list at startup.
Modules destroy themselves using the new luax_atexit to avoid a hardcoded destroy-list.
Rename module entry points to be of the form luaopen_lovr_<module>.
Separate common api helper functions into individual headers.
Move lovr.c stuff into main.c since it's rather small now.

Smart people have informed me that this approach won't work on iOS or consoles.


Samples

I'm the lead developer of delphimvcframework, and I'd like to add swagger support to the APIs offered by the controllers. Could you add some samples about this project so that we can evaluate It?
Thank you

Hello Danielle,
I'm happy with your interesting in SwagDoc library.
I'm on vacation to 26 march.
After my priority is to create documentation and samples for SwagDoc.
The SwagDoc creates swagger.json file  to be copied together with the Swagger files web page.
The Swagger files can to be in www.swagger.io website.
Do you know swagger documentation version 2.0? This is very important you to know or to learn.
Sorry for my vacation. I can't to help you more fast.
Marcelo Jaloto

*Download Swagger Interface files
https://swagger.io/docs/swagger-tools/#download-33
*Documentation Swagger version 2.0
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md

Hello Danielle,
I'm happy with your interesting in SwagDoc library.
I'm on vacation to 26 march.
After my priority is to create documentation and samples for SwagDoc.
The SwagDoc creates swagger.json file to be copied together with the
Swagger files web page.
Visit about Swagger in the  website address www.swagger.io
*Download Swagger Interface files
https://swagger.io/docs/swagger-tools/#download-33
*Documentation Swagger version 2.0
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md
Do you know swagger documentation version 2.0? This is very important you
to know or to learn.
Sorry for my vacation. I can't to help you more fast.
Marcelo Jaloto
Em qua, 21 de mar de 2018 21:46, Daniele Teti<EMAIL_ADDRESS>escreveu:

I'm the lead developer of delphimvcframework, and I'd like to add swagger
support to the APIs offered by the controllers. Could you add some samples
about this project so that we can evaluate It?
Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/marcelojaloto/SwagDoc/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/ATHpqCH9EQMj7uw_ZvDCoTOSPsPaugZAks5tgrw_gaJpZM4S1yqt
.

@danieleteti
look at the news, new samples and update in readme.
Do you need more samples?

@danieleteti,
a new full sample is available!
Download here!

Thank you @marcelojaloto
We'll try to integrate it before the upcoming ITDevCon9.
Thank you for the notification.

@danieleteti,
it's a great pleasure to have SwagDoc embedded in your framework, and even more to have an ITDevCon9 mentioned spec.
I'm going to present SwagDoc on October 23 at the Embarcadero Conference 2018 here in Brazil.
When you can, please keep me informed of the progress of your integration between Delphi MVC Framework and SwagDoc.
Thank you!


[Question]: Team workspace

Hello, I have noticed that the functionality of the team workspace is currently not implemented. There is a button, but it does not respond when clicked. Will your team consider implementing this feature in the future?

Of course, but this would not be open sourced.

如何向团队添加其他人，我想把知识库共享给其他团队成员，目前是不是没有这个功能

如何向团队添加其他人，我想把知识库共享给其他团队成员，目前是不是没有这个功能

Look like so.

如何向团队添加其他人，我想把知识库共享给其他团队成员，目前是不是没有这个功能

Look like so.

@wangtao19871205

如何向团队添加其他人，我想把知识库共享给其他团队成员，目前是不是没有这个功能

Look like so.

set your kdb permission to team and
insert into user_tenant (id,create_time,create_date,update_time,update_date,user_id,tenant_id,`role`,invited_by,status)
values (replace(uuid(),"-",""),unix_timestamp() * 1000,now(),unix_timestamp() * 1000,now(),'your_team_member_id','your_tenant_id','owner','your_id','1')

then your team member could see your kdb. but doesn't work for dialog

Of course, but this would not be open sourced.

@KevinHuSh When do you expect to be ready? I really want to be your first paying customer.


k3s failed to start, see journalctl -u k3s

[Fixed] k3s failed to start, see journalctl -u k3s, that error happens sometimes on first_control_plane when the eth1 network interface is not present. This bug is rare enough, and we believe it comes from Hetzner, randomly.
If it happens, destroy, and re-apply terraform.

We have opened an issue for it here https://github.com/hetznercloud/terraform-provider-hcloud/issues/512

This was fixed, just pull the latest and greatest and redeploy.


New Feuture - change alert messege and buttons text

Hi this not an issue,
I just wondering if you can give the ability to pass a message,btnTextSuccess,btnTextDenied params to change the texts.
Other than that the package is awsome thanks :)

Hi i'll see what I can do but it may take sometime

Hi i'll see what I can do but it may take sometime

No problem thanks

No problem thanks

I have committed the changes for new feature. Will be closing this issue

I have committed the changes for new feature. Will be closing this issue


For isNotificationOnly bots how do we get the serviceURL?

All the docs I've read (such as here indicate that a bots serviceURL is only discovered by receiving previous conversation messages

The serviceUrl property within the user's message indicates that the bot should send its response to the endpoint https://smba.trafficmanager.net/apis; this will be the base URI for any subsequent requests that the bot issues in the context of this conversation. If your bot will need to send a proactive message to the user, be sure to save the value of serviceUrl

If we want to make a proactive bot that only sends out notifications how do we discover the serviceUrl?

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

ID: 7f3dfdc7-7136-2d85-be50-647a4a2eae13
Version Independent ID: 58f44a51-ae08-3297-b409-76e393adaf43
Content: Notification only bots - Teams
Content Source: msteams-platform/concepts/bots/bots-notification-only.md
Product: msteams
GitHub Login: @o365devx
Microsoft Alias: o365devx

Please have a look at Conversation Update event which is triggered when your Bot is installed.
Please note that this event is triggered only once for personal scope.


Create outreach plan and coordinate timing

[ ] press release
[ ] press release distributed to (??)
[ ] twitter campaign (tweets drafted, timed, and coordinated)
[ ] reddit https://www.reddit.com/r/dataisbeautiful/
[ ] Others?

I am working w/ Com on the press release, but they are expecting a delay of 2-3 days. I am pushing to expedite the timing so we can release w/ the paper tomorrow am.
Working on drafting tweets as well, see #131
Haven't started drafting reddit post, but expect those to go out maybe on Thursday?
Should we create a timeline for all of these events and who is on point?


Create Business Configuration Maintenance Object

Tutorials: https://developers.sap.com/tutorials/abap-environment-business-configuration-object.html
Step 5 Create Business Configuration Maintenance Object --> Substep 7
Intstructions state to delete code in methods LHC_ZI_ERRORCODE###→VALIDATERECORDCHANGES and LHC_ZI_ERRORCODE###TEXT→VALIDATERECORDCHANGES

However, the code "generated" in the previous step does not contain methods with those names in the two local classes but shows  methods VALIDATETRANSPORTREQUEST instead.

Could there be something I missed in the tutorial causing this, or is there a mismatch between the instructions and what got generated?
Thanks and Cheers
Bärbel

Hi @BaerbelW ,
we will check this and will update this tutorial, if needed.
Best regards,
Merve

Hi @BaerbelW,
thank you. The name of the generated methods changed in one of the recent releases.
The correct method name is VALIDATETRANSPORTREQUEST.
Fixed by #22996
Regards,
Patrick


Next lxd stable release

Hi!
When can we expect non-thinpool lvm support introduced in https://github.com/lxc/lxd/issues/3160 in stable packages?

Probably next week. Most people get LXD through the Ubuntu archive or PPAs, those for us are generated based on what hit the current Ubuntu development release.
With Ubuntu 17.04 having been released last week, the next development release isn't open yet, so there's nowhere for us to upload a new LXD right now which is why I've been postponing the release of 2.13.


Ability to set default Client ID for Server

Describe the feature request
The API of injecting messages from the server is not really consistent with itself:
When creating a new InjectedMqttApplicationMessage(MqttApplicationMessage applicationMessage) the ClientID does not have to be set. However, for being able to actually inject this message, SenderClientId must not be null.
In Version 3, when publishing from the Server, the ClientID was always null.
Which project is your feature request related to?

Server

Describe the solution you'd like
For me, the ideal solution would be to be able to assign a ClientID-like string to the server, that is used by default when injecting messages. This could then be overridden by the SenderClientIdproperty of the InjectedMqtttApplicationMessage.
Describe alternatives you've considered

Allow publishing messages with ClientID == null (Behaviour of library V3)
Require a non-null SenderClientId when creating an InjectedMqttApplicationMessage.

Additional context
Thinking about it, this might actually be a bug, after solving issue #1470

I agree that it is better to enforce a client id for any injected application message. I will not yet change this to avoid breaking changes.
Since version 4 the client id is mandatory due to several new features so there is no way back 😄

Not when it comes to compiling but from business logic perspective. I recommend that you create an extension method in your project which always uses the same client ID internally. Another option is to encapsulate the server and provide your own (customized) API.


Search-mailbox is deprecated

Refer - https://docs.microsoft.com/en-us/powershell/module/exchange/search-mailbox?view=exchange-ps
Guidance should include how to use the compliance search cmdlets now.

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

ID: daae9c8b-a9c6-01a7-1072-faaab97793bf
Version Independent ID: 08cb659e-3295-e2df-4d9b-e0f426e238e7
Content: Phishing investigation
Content Source: compass/incident-response-playbook-phishing.md
Product: m365-security
Technology: m365d
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

Thanks for your dedication to our documentation. This issue appears to be fixed. #please-close


Multiple images are created and test fails

On some of my compose view when running the test with roborazzi.test.record=true multiple images are created(more than 100) and the test fails with
Compose did not get idle after X attempts in 60 SECONDS. Please check your measure/layout lambdas, they may be causing an infinite composition loop. Or set Espresso's master idling policy if you require a longer timeout. The following Idle Conditions failed .
androidx.test.espresso.AppNotIdleException: Compose did not get idle after 5 attempts in 60 SECONDS. Please check your measure/layout lambdas, they may be causing an infinite composition loop. Or set Espresso's master idling policy if you require a longer timeout. The following Idle Conditions failed .

My test looks like this:
@GraphicsMode(GraphicsMode.Mode.NATIVE)
@RunWith(RobolectricTestRunner::class)
@Config(application = KoinTestApp::class, qualifiers = RobolectricDeviceQualifiers.Pixel5)
class ScreenshotTest {
    @get:Rule
    val composeRule = createComposeRule()
    @Test
    fun launchComposable() {
        composeRule.setContent {
            captureRoboImage{
                MyComposePreview()
            }
        }
    }
}

The issue also happens when running it with roborazzi.test.compare=true
I was able to find what was causing this type of issue in my preview and here is the simplified preview:
@OptIn(ExperimentalMaterial3Api::class)
@Composable
fun MyComposePreview() {
    val interactionSource = remember { MutableInteractionSource() }
    BasicTextField(
        value = "value",
        onValueChange = {},
        decorationBox = { innerTextField ->
            OutlinedTextFieldDefaults.DecorationBox(
                value = "value.text",
                innerTextField = innerTextField,
                singleLine = true,
                enabled = true,
                interactionSource = interactionSource,
                visualTransformation = VisualTransformation.None,
                container = {
                    OutlinedTextFieldDefaults.ContainerBox(
                        true, false, interactionSource,
                        colors = OutlinedTextFieldDefaults.colors(),
                    )
                }
            )
        }
    )
}

Thanks. The reason why the images are created multiple times is that you are using both composeRule.setContent{} and captureRoboImage{}.
composeRule.setContent{}'s lambda is executed multiple times due to recompose.
So you need to use either way to use composeRule.setContent{} and composeRule.captureRoboImage() or captureRoboImage{}
NG
  @get:Rule
  val composeRule = createComposeRule()
  @Test
  fun launchComposable() {
    composeRule.setContent {
      captureRoboImage{
        MyComposePreview()
      }
    }
  }

OK
  @get:Rule
  val composeRule = createComposeRule()
  @Test
  fun launchComposable() {
    composeRule.setContent {
        MyComposePreview()
    }
    composeRule.captureRoboImage()
  }

OK
  @Test
  fun launchComposable() {
    captureRoboImage {
        MyComposePreview()
    }
  }

If you have any questions, feel free to ask me.


Add docker files to gitignore

Update gitignore to have Docker related files if users choose to go through the Docker setup.

Codecov Report

Merging #6507 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6507   +/-   ##
=======================================
  Coverage   73.32%   73.32%
=======================================
  Files          67       67
  Lines        9604     9604
=======================================
  Hits         7042     7042
  Misses       2562     2562

Continue to review full report at Codecov.

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

Codecov Report

Merging #6507 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6507   +/-   ##
=======================================
  Coverage   73.32%   73.32%
=======================================
  Files          67       67
  Lines        9604     9604
=======================================
  Hits         7042     7042
  Misses       2562     2562

Continue to review full report at Codecov.

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


Error 404 fetching pbiviz.json with custom webpack config.

Since powerbi-webpack-plugin version 3.2.0 the pbiviz.json file is no longer a webpack asset. Thing is, that it's documented anywhere and and I cant figure out from the commits what to change, so I try to open it here, because reverting to version 3.1.2 did nothing.
There is some change in the pbiviz command that prevents it from getting transferred to the backend assets folder.

Could you please provide us with your source code? So we'll be able to reproduce the issue.
You can send it to our email -<EMAIL_ADDRESS>


Column types assumed as int if first value is a whole number

If I have a column consisting of values [1.000, 2.5, 3.562, ...] then the column is interpreted as integer instead of float. A (bad) workaround is to increment the first value in the column by a negligible amount (e.g. 0.00000001).

closing, the solution is really to use a schema


React step 4

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

Hi @kellychurchill
This pull request is for step 4, not for step 5.

@krekalidis - the preview link is labeled step 5 because it is the expected outcome at the start of step 5.
Your preview does not match because the third word  in each title phrase is not correctly formatted - see the instructions here: https://www.carbondesignsystem.com/tutorial/react-step-4#type

@kellychurchill - I made the appropriate changes.

👍 Looks good - 🎉 You are one step closer to completion of the Carbon React tutorial and earning the digital credential.


mass.range specified but readImzML/readMSIData returns MSI data with full range of m/z

some of code are as follows:
`library(Cardinal)
options(scipen = 999)
min_mz <- 800
max_mz <- 3000
desired_resolution <- 0.01083
folder_path <- "E:\mass_spectrum_data\CRC-PXD019662-20240607\TMA5B-alltumours-nonormalization.imzML"
msi <- readImzML(path, memory = FALSE, verbose = TRUE, mass.range = c(min_mz, max_mz))
plot(msi)
print(msi)`

Is the dataset in "continuous" imzML format?
If so, that is currently the intended behavior.
The mass.range argument is only used when reading "processed" imzML so the mass range does not need to be calculated from the data.

yes, it is a "continuous" imzML. Thank u for your attention！


Deep-Linking Tabs prevent back button in IE from working correctly.

I'm using the tabs plugin in a site and was testing it with Internet Explorer when I noticed that the deep-linking tabs were "breaking" the back button in the browser (creating an infinite loop as described in the pull request I mention below).
I did some Googling and found #6118. I saw that it had been accepted and updated to the latest version of Foundation to test the fix. It worked in Chrome (and I'm assuming other non-IE browsers but did not do tests to verify), but not Internet Explorer.
I re-visited the code and simplified it (getting rid of recording the entry point because it seems that the tabs work fine without having to record the entry point). I did some final testing in IE (as well as Chrome to represent the cooler browsers) and found that it worked fine.
(I also fixed some formatting at the top of the tabs plugin)

Nice one!


Keep docker image labels around after conversion

It would appear that annotations are the equivalent to Docker labels: i.e. immutable image metadata. Is that the case, and if so, can we support keeping image labels around as annotations after conversion? Or as labels?

docker2aci is already adding those annotation while converting (perhaps it should be better documented):
  "annotations": [
    {
      "name": "created",
      "value": "2016-09-23T18:08:51Z"
    },
    {
      "name": "appc.io/docker/registryurl",
      "value": "registry-1.docker.io"
    },
    {
      "name": "appc.io/docker/repository",
      "value": "library/debian"
    },
    {
      "name": "appc.io/docker/imageid",
      "value": "37c816ae4431cabacbd1cf9ef8b50f9945ebc47a9aaa26a315612edc52b12c32"
    },
    {
      "name": "appc.io/docker/parentimageid",
      "value": "d0c4f1eb7dc8f4dae2b45fe5c0cf4cfc70e5be85d933f5f5f4deb59f134fb520"
    },
    {
      "name": "appc.io/docker/cmd",
      "value": "[\"/bin/bash\"]"
    },
    {
      "name": "appc.io/docker/tag",
      "value": "latest"
    }
  ]

I think those annotations so far cover metadata that we found was needed by other tools. Do they cover your usecase too or do you need something else additionally?

@lucab he's referring specifically to keeping docker labels around, which
we should probably add.
Luca Bruno<EMAIL_ADDRESS>schrieb am Mi., 19. Okt. 2016, 11:52:

docker2aci is already adding those annotation while converting (perhaps it
should be better documented):
"annotations": [
{
"name": "created",
"value": "2016-09-23T18:08:51Z"
},
{
"name": "appc.io/docker/registryurl",
"value": "registry-1.docker.io"
},
{
"name": "appc.io/docker/repository",
"value": "library/debian"
},
{
"name": "appc.io/docker/imageid",
"value": "37c816ae4431cabacbd1cf9ef8b50f9945ebc47a9aaa26a315612edc52b12c32"
},
{
"name": "appc.io/docker/parentimageid",
"value": "d0c4f1eb7dc8f4dae2b45fe5c0cf4cfc70e5be85d933f5f5f4deb59f134fb520"
},
{
"name": "appc.io/docker/cmd",
"value": "["/bin/bash"]"
},
{
"name": "appc.io/docker/tag",
"value": "latest"
}
]
I think those annotations so far cover metadata that we found was needed
by other tools. Do they cover your usecase too or do you need something
else additionally?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/appc/docker2aci/issues/208#issuecomment-254767031,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACewN39GKtu7HcpOS6uVJIltYEwT0lrgks5q1eh5gaJpZM4KaXfq
.

Ref: https://docs.docker.com/engine/reference/builder/#label
https://docs.docker.com/engine/userguide/labels-custom-metadata/

I did indeed mean that very thing. We use the LABEL directive in our docker files to encode build-time information into the image. Then when the image is signed, so is that static metadata. This is pretty important to our ability to track what is deployed: who built it, when did they build it, what git rev was used to build it, etc.

Makes sense. I think we can just create appc.io/docker/labels annotations
and store them in there.
Greg Poirier<EMAIL_ADDRESS>schrieb am Mi., 19. Okt. 2016,
18:48:

I did indeed mean that very thing. We use the LABEL directive in our
docker files to encode build-time information into the image. Then when the
image is signed, so is that static metadata. This is pretty important to
our ability to track what is deployed: who built it, when did they build
it, what git rev was used to build it, etc.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/appc/docker2aci/issues/208#issuecomment-254872016,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACewNyj_52PyoeOV81hiOQkYA9dKy6Sbks5q1knAgaJpZM4KaXfq
.

We have tooling around the label-schema.org stuff. Would it be horribly inappropriate to keep the current label namespace?

Do you mean copy the labels to annotations?
Greg Poirier<EMAIL_ADDRESS>schrieb am Mi., 19. Okt. 2016,
19:11:

We have tooling around the label-schema.org stuff. Would it be horribly
inappropriate to keep the current label namespace?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/appc/docker2aci/issues/208#issuecomment-254878559,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACewN_1TzkD3f5qR0u8ckD4OxhnNjDv5ks5q1k9PgaJpZM4KaXfq
.

Yes, if annotations are the equivalent of docker labels. What is the difference between an appc annotation vs appc label?

appc labels are more like selectors, used for discovery. So there should be
a small set of well known labels used as "query parameters" when trying to
locate an image (analogous to tags, but immutable).
Annotations can be arbitrary and hence are pretty much equivalent to docker
labels.
Greg Poirier<EMAIL_ADDRESS>schrieb am Do., 20. Okt. 2016,
00:28:

Yes, if annotations are the equivalent of docker labels. What is the
difference between an appc annotation vs appc label?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/appc/docker2aci/issues/208#issuecomment-254959522,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACewNxSeRWZlGIV-0YukvsZ3dgF9GbSJks5q1pmLgaJpZM4KaXfq
.

Assuming that appc annotations == docker labes.
We right now use:
FROM #{docker_image}
LABEL org.label-schema.schema-version="1.0"
LABEL org.label-schema.name="#{job_name}"
LABEL org.label-schema.build-date="#{Time.now.to_datetime.rfc3339}"
LABEL org.label-schema.vcs-ref="#{git_rev}"
LABEL org.label-schema.os-release="#{os_release(docker_image)}"
LABEL org.label-schema.vendor="Stripe"

Pardon the Ruby, but every image we create gets these labels.
From the exported image, we take all of the labels from the config file referenced in manifest.json and make those annotations in the resulting appc manifest without modifying the label identifiers (use the label-schema.org naming scheme instead of the /-delimited namespacing that coreos uses).

https://github.com/appc/docker2aci/pull/209

Closed by #223.


Add additional optional param for blocks

Checklist

[ ] Issue(s) linked

There is no issue yet.  This should add the option to post Blocks JSON to Slack;
Sample;
  step "transform" "buckets" {
    value = jsondecode(<<EOT
  [
      {
          "type": "section",
          "text": {
              "type": "mrkdwn",
              "text": "Pick an item from the dropdown list"
          },
          "accessory": {
              "action_id": "select_bucket",
              "type": "static_select",
              "placeholder": {
                  "type": "plain_text",
                  "text": "Select a bucket...."
              },
              "options": [
                  %{ for idx, name in step.pipeline.buckets.output.buckets[*].Name }
                  {
                    "text" : {
                      "type" : "plain_text",
                      "text" : "${name}"
                    },
                    "value" : "${name}"
                  } %{ if idx < length(step.pipeline.buckets.output.buckets[*].Name) - 1 },%{ endif }
                  %{ endfor }
              ]
          }
      }
  ]
  EOT
    )
  }

  step "pipeline" "post_message" {
    pipeline = slack.pipeline.post_message
    args = {
      channel = "test"
      blocks = jsonencode(step.transform.buckets.value)
    }
  }

Thanks @johnlayton for the enhancement 👍 !!
Following the above sample, could you please add a sample output/screenshot of how the block appears on slack?


Remove deprecated instruction

From the @testing-library docs: The module @testing-library/react/cleanup-after-each has been deprecated and no longer does anything (it is not needed). You no longer need to import this module and can safely remove any import or configuration which imports this module.
Previous console warning:

Just saw that there's an identical PR to achieve this, so closing this one :P
https://github.com/facebook/create-react-app/pull/7620


[Enhancement] Add pipe_failed_task_threshold config

Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.7 out of 8 committers have signed the CLA.:white_check_mark: ABingHuang:white_check_mark: LiShuMing:white_check_mark: before-Sunrise:white_check_mark: GavinMar:white_check_mark: packy92:white_check_mark: dirtysalt:white_check_mark: rickif:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


Datasets used to train model

Hey,
Is their any chance we can get the dataset videos you used to train the model?
Thanks

I really support this idea. Open access to the dataset would be very helpful.
I also am wondering, what are the tools used for labelling? What is the process? There is some mention of labeling being labor-intensive, and I myself would like to try labeling.
Willing assist in additional data prep, here.


WIP: Upgrade | Wagtail 6.0 and Node 20

This upgrades Wagtail from 5.2 to 6.0, and also Node from 18 to 20.
Another PR will follow to upgrade Wagtail from 6.0 to 6.1 and Node.js from 20 to 22.

closes #501
closes #500
closes #512
closes #513

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


what should Cache put operations do if the body errors out after resolving promise?

The spec text now says in Batch Cache Operations:

The cache commit is allowed as long as the response's headers are available.

So the body would stream to disk in the background after promise resolved.
What should Cache do if there is a network error while writing the body?  Just truncate the body?  Remove the entry?

I'd like to clarify this before we attempt to implement partial response commit in gecko.

We only know this if we check Content-Length, no? Which is known to not be reliable, though maybe HTTP/2 changes this a bit?

We know in the implementation in some cases because we get an error code from the network library.  Or it could be because another internal error, like worker thread shutdown, truncated the stream.
But if the connection is terminated with a RST, then no, we cannot distinguish these errors.

So the current design seems somewhat problematic for developers. You think you successfully added an entry, but then it errors later on and there's no way to find out. Should a cache keep an error log of sorts?

One idea is to resolve put/add/addAll with another object that exposes a promise representing the completion of the body.  That would at least give code a chance of detecting this.

So the body would stream to disk in the background after promise resolved.

The body would stream to disk in the background even after promise is returned. But the promise returned from addAll()/put() will resolve/reject only when the end-of-file is pushed to response's body or the response get a termination reason.
If the response gets a termination reason, the cache rolls back. That happens in addAll() step <IP_ADDRESS>.2 and put() step 14.2.

@jungkees thats how it used to work, but I thought we changed it.  I thought this note in BatchCacheOperations meant the UA could resolve the add/addAll/put promise before the body was complete:

The cache commit is allowed as long as the response's headers are available.

Or are you saying we commit to Cache, so other cache.Match() calls will find the partial response, but we still don't resolve the add/addAll/put promise when we commit to the Cache?  That sounds confusing from an API perspective to me...

Or are you saying we commit to Cache, so other cache.Match() calls will find the partial response, but we still don't resolve the add/addAll/put promise when we commit to the Cache?

Yes, that was the decision. Here's the summary of the behavior from the discussion: https://github.com/slightlyoff/ServiceWorker/issues/573.

Closing. History: https://github.com/slightlyoff/ServiceWorker/issues/362#issuecomment-119092324.


failed imports

In some cases the recent reimport (#10) failed.
It seems the problem is caused by goobi not providing uniform files for some unknown reason.
If images get referenced like that, the import fails:
<mets:div ID="PHYS_0020" ORDER="20" ORDERLABEL="19" TYPE="page">
    <mets:fptr FILEID="FILE_0020_PRESENTATION"/>
    <mets:fptr FILEID="FILE_0020_DEFAULT"/>
</mets:div>

Here it works.
<mets:div ID="PHYS_0004" ORDER="4" ORDERLABEL=" - " TYPE="page">
    <mets:fptr FILEID="FILE_0004"/>
    <mets:fptr FILEID="FILE_0004_PRESENTATION"/>
    <mets:fptr FILEID="FILE_0004_DEFAULT"/>
</mets:div>

Reason is the missing standard file-ptr in the mets. I probably could fix this, by just adding them to the file, since the corresponding files seem to exist. In some cases the files are even containing both kinds of links, faulty and working ones.
Ich however will rather try to republish them in goobi.

On second thought: maybe fixing the mets on the fly isn't a bad idea if it works, since it isn't easy to decide, if an import worked without opening the document in the collection, due to the fact, that mets can be partially corrupted.

[ ] identify faulty imports
[ ] fix them

Set A:
B-VG saubere Varaiante
Set B:
Protokoll 7. Laenderkonferenz
Protokoll 6. Laenderkonferenz
Protokoll 4. Laenderkonferenz
Protokoll 3. Laenderkonferenz
Protokoll der 4. Sitzung des Subkomitees des Verfassungsausschusses vom 22. Juli 1920
Protokoll 2. Laenderkonferenz 4. und 5. Jänner 1919 (partial)
Protokoll 1. Laenderkonferenz 23. November 1918 (partial)
It's possible that there are more partially failed imports, but this is enough to test, if I can fix this in the fly by adding the links to the mets file.

I republished theses images to the viewer in goobi as sugested, and reimported them, but this didn't solve the issue.

Since one of the documents allready imported and transcribed was not cropped but the default upload (one image even with turned 180 degrees): @csae8092 are we supposed to use the defaults or the cropped ones for transcribing?

Ideally those Images which will be archived in arche

this is the case, howerver some images are not cropped in goobi

it seems as if all issues are caused by goobi-workflows & need to be further investigated there

Set A:
B-VG saubere Varaiante
Set B:
Protokoll 7. Laenderkonferenz: bv_doc_id__61
Protokoll 6. Laenderkonferenz: bv_doc_id__60
Protokoll 4. Laenderkonferenz: bv_doc_id__59
Protokoll 3. Laenderkonferenz: bv_doc_id__58
Protokoll der 4. Sitzung des Subkomitees des Verfassungsausschusses vom 22. Juli 1920: bv_doc_id__39
Protokoll 2. Laenderkonferenz 4. und 5. Jänner 1919 (partial): bv_doc_id__57
Protokoll 1. Laenderkonferenz 23. November 1918 (partial): bv_doc_id__56

Still need to solve some of them, only way to do this is in goobi, since the processes there where messed up or failed due to the rather fragile systems. I will fix myself as long Jörg is on vacation, but on the long run, this should be handled by someone else.


caja-with-extensions doesn't install .desktop files into $XDG_DATA_DIRS

Describe the bug
caja-with-extensions doesn't install .desktop files into $XDG_DATA_DIRS
In particular, after installing caja-with-extensions, other applications aren't able to run it when they need to show folder content to the user.
caja package does install .desktop files, and doesn't have this problem.
Steps To Reproduce
Steps to reproduce the behavior:

$ nix-shell -p mate.caja-with-extensions
$ find `echo $XDG_DATA_DIRS|tr ":" " "` -name 'caja*.desktop'

no caja*.desktop entries found
Expected behavior
multiple caja*.desktop records should be found, like with caja package
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.18.0, NixOS, 22.05 (Quokka), 22.05.379.08950a6e29c`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.8.1`
 - channels(root): `"nixos-22.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Is there any workaround to fix this?
I've been struggling with this problem for a whole day, but I still can't figure out the solution.

@aquinary I've installed mate.caja and mate.caja-extensions instead, although it seems that not all extensions are working.

@aquinary I've installed mate.caja and mate.caja-extensions instead, although it seems that not all extensions are working.

I just changed the package a caja-extensions:
postInstall = ''
     mkdir -p $out/share/applications

    for file in `find $caja/share/ -type f -name "*"`
    do
      pathToFile=$(echo $file | awk -F "/" 'OFS = "/" {$2=$3=$4=""; print substr($0, 5)}')
      pathToDir=$(echo $pathToFile | awk -F "/" 'OFS = "/" {$NF=""; print $0}')

      mkdir -p $out/$pathToDir

      cat $caja/$pathToFile > $out/$pathToFile
      sed -i "s|$caja|$out|gi" "$out/$pathToFile"
    done
  '';

By default /usr/share/applications/caja.desktop contains a link to caja (without extensions). The script above goes through all the files and changes all occurrences from caja to caja-extensions. And it works great
And if I put mate.caja and mate.caja-extensions together, then only regular caja works, without extensions


Revert writing ostree/encapsulated ref

This partially reverts 30dee81c22ad5cb90e77198d3ddbcc25d388afb5
We do keep the code which ignores the presence of the file during
import, as an aid to future compatibility.
We can't do this by default for quite a while until support
for reading/ignoring the file has been out in the wild for e.g.
at least a month or two.

See https://github.com/coreos/rpm-ostree/pull/3957#issuecomment-1224381546

Perhaps we should make it opt-in...something like a new --format-version 1.1 flag and API?


copy, sync, move considerations.

When doing a daily automated transfer of files, I currently perform a rclone copy action in a bash script that also looks for 2 days old files, and clean them up manually (find -mtime). My concern is that rclone move could create data loss if e.g. interrupted by system reboot, process killed by any reason, network connection loss, attempting to move incomplete files in the middle of being copied, or anything similar unforeseen interruptions.
A copy action will simply retry the same files on the next time the script runs regardless, so I consider it safer by default. Is there a chance move action could loose files entirely in the above scenario? Am I wrong in my thinking, or is copy safer to use?
If not, then move is obviously simpler than copy+cleanup. I'd just like an official comment on this.

Move will only delete the source after the copy has completed successfully.
Move will retry things in the same way as copy, so if some files fail to move, then they will be moved on the next run.

Is there a chance move action could loose files entirely in the above scenario?

Move is designed not to lose files so (barring bugs) it should do what you want.

Thank you for the quick response.


How to manage the menu?!

So I've installed Shell and I have absolute no idea how to manage the menu. It changed it, but I have no way to manage it. It doesn't say anywhere in the readme nor in the application how to do this... yet it's the primary advertised feature. If it is detailed somewhere consider making it more prominent.

hold shift and right click on taskbar, Shell menu will appear at the top with the submenus, from here you can open directory where the shell configuration files is saved.
shell.nss is where shell config is set, and inside imports*.nss is the config of menu items, you can open those file with any text editor, i recommend the notepad++, and set the document language to C, to make the nss file more readable.
after editing any nss, you'll need to update changes, hold ctrl and press right click on desktop area or taskbar to it will force shell nss files to reload, or you can restart explorer.
please refer to this page to start editing your menu.
Note: you can easily "brick" the shell menu if you do some typos on the nss files, and the default Windows menu will appear. To resolve just correct the syntax or undo the changes and restart explorer.


Confused on how to use this

Hello LIVECell creators, I'm trying to use your LIVECell code for a set of images of cells. By looking through your code, it seems you take images and compress them into Excel data, then a model runs through the Excel file data. I'm confused how my images should be converted to Excel data. Is that also done through your code, or is there a process I need to complete to convert my images?
Also, I'm assuming the pre-processing code should be ran before the main code, but should the pre-processing code be ran in the same script as the main script, or should they be ran in separate scripts?
If I could get a run-down of the process of using .tif images to the final product of using the model to predict what types of cells are present, that would be greatly appreciated.
Thank you for any advice.

Hi @ridsmd, it is not clear to me what you are trying to achieve. Can you please explain what your inputs are and what outputs you are aiming to reach using the LIVECell code?


DHCP6 Before RA. Additions and ammendments

Replaced posix_kill() in kill_dhcp6client_process() with mwexec("kill -9 $pid"), this is because the posix_kill call was not reliably killing the dhcp6c process, kill -9 works every time.
Changes to the rtsold script creation. The script lines starting dhcp6c should not have be written to the script when dhcpwithoutra is true.
Style corrections, I spend more time doing these than changing code!

Needs conflicts to be resolved. Recieved has been replaced by Recieved by PR #3094

Closing in favor of #3102


Input Image

Hi Guys,
I want to use a JPG image as input, can you opensource the code that exchange the image into PKL?
Thank you

Hi @wenyihan4396 ,
Thanks for your interest!
The inference code can be found here
https://huggingface.co/spaces/CVPR/MonoScene/tree/main
Specifically, this file:
https://huggingface.co/spaces/CVPR/MonoScene/blob/main/app.py
Note that you need to modify the camera parameters in this function:
https://huggingface.co/spaces/CVPR/MonoScene/blob/main/helpers.py#L128
BR,
Anh-Quan

Hi Anh,
Thank you so much😊!
Best regards,
Yihan Wen
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: Cao Anh @.>
发送时间: 2022年8月19日 15:43
收件人: @.>
抄送: @.>; @.>
主题: Re: [cv-rits/MonoScene] Input Image (Issue #22)
Hi @wenyihan4396https://github.com/wenyihan4396 ,
Thanks for your interest!
The inference code can be found here
https://huggingface.co/spaces/CVPR/MonoScene/tree/main
Specifically, this file:
https://huggingface.co/spaces/CVPR/MonoScene/blob/main/app.py
Note that you need to modify the camera parameters in this function:
https://huggingface.co/spaces/CVPR/MonoScene/blob/main/helpers.py#L128
BR,
Anh-Quan
—
Reply to this email directly, view it on GitHubhttps://github.com/cv-rits/MonoScene/issues/22#issuecomment-1220356893, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARBAJK6C4JQ6AVD22YFZXQ3VZ43KFANCNFSM567BJBPA.
You are receiving this because you were mentioned.Message ID: @.***>


adjust routing plugin

when the routing tool is activated, it also

closes the context menu
removes existing highlight features

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.001%) to 99.544%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
11574

Relevant Lines:
11577

💛  - Coveralls


Dataproc Push job Id in xcom

This PR fix

Push dataproc Job Id instead of success message in xcom
Remove kwargs param from DataProcSubmitTrigger
Delete cluster task should always run in example

Closes: #400

@pankajastro change num_instances to 1 for worker_config as well please

If the worker node is 1 then getting this error
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/google/api_core/grpc_helpers.py", line 57, in error_remapped_callable
    return callable_(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/grpc/_channel.py", line 946, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/usr/local/lib/python3.9/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
    raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.INVALID_ARGUMENT
	details = "Worker configuration must contain two or more workers: '1'"

Can you please add to the description why do we need to push job_id to XCOM? Is it needed somewhere? In general, in my opinion, I feel we should add what and why in the PR description. Reference: https://cbea.ms/git-commit/#why-not-how

Since the sync version does the same so I am also doing here  I have added reference in #400

I have removed a couple of tasks in order to optimize the DAG here cfd7f12b50940f01f4dea9f67485292063d80156 .

PR title needs improvement. Summarize what you are doing here. If you are optimizing the example DAG, mention it as "Optimize example DAG for async google cloud operators".

I have improved a little bit and add added all the points that this PR addresses in the description.


android call notification not display when app is on quite mode.

Currently, I have used the other app and anyone having call me in calling app. So, that time i have received the simple call notification but not display "react-native-full-screen-notifiation-incoming-call" notification not received only on kill mode.

@bipin-sakariya Can you provide more information? library version, android version, device info,.. Did u open android studio to read log ?

Still not getting call notification on quite mode in latest version.

you can provide file androidmanifest

Ohh @linhvovan29546  thanks. I have update Androidmanifest file activity parameter and now call notification also display on quite mode.

@linhvovan29546 I have issue face on android call notification is not display when my app is on terminate state.

check your Mainactivity

I have already added in main activity.

I don't have any ideas for it, can you check log on Android Studio, not VS code

@linhvovan29546 I have getting call notification on android version 11 but in android version 12 it is not working.

my device use android version 12. I still see it showing the notification