Summaries: add since date for template calls

@jgclark I wanted to generate daily progress reports since my birthday (when I made myself certain promises). Hahahaha. So I added a tiny bit of code to allow for the period to be a date from which to start.
<%- progressUpdate({period: '2022-02-15', heading: 'Post-Birthday Habits', showSparklines: true}) %>

Because my Lint/Prettier settings are different than yours, the changes appear more extreme than they are. You can always open the changed files and resave them so they have your formatting that you prefer.

@jgclark for Git-noob reasons, I seem to have also included some of my Task changes. you can ignore all the changes to files in dwertheimer.TaskAutomations that are in this commit. :)

@jgclark also added ability to ignore today using includeToday:false param


UnityStudio can't read/extract xml files?

Yo,
Perfare why UnityStudio can't detect xml files?
Example file:
https://th1-qjmu.static.kunlun.com/CDN_Resourse/Android/1100/GameSite/local/GameRes.unity3d
Can you help me?

I don't know what you want to do, I tested this file extract is fine

Try open GameRes.unity3d file in Unity Studio. If you open this file with Unity Assets Bundle Extractor I can saw theses files and extract raw.
https://image.prntscr.com/image/O7qnMn7oT_K1mmQq7JA9RQ.png
But unfortunately Unity Studio can't saw theses files for me extract.

File - Load file - select bundle file


Change character line length?

https://hilton.org.uk/blog/source-code-line-length#:~:text=GitHub is the de facto,in the GitHub diff view.

125 characters per line is the real de facto coding standard for maximum line length these days, because this is the maximum number of characters that you can see in the GitHub diff view. This used to be 119 characters, but the page layout changed.

https://github.com/SciML/SciMLStyle/issues/21
Following Julia's standard of 4 space tabs might make this reasonable (@ranocha). What do you think @YingboMa ?

Will JuliaFormatter reformat code when increasing the line length?

From my point of view, it's quite a bit of personal preference and depends also on the coding environment etc. The article you linked above basically gives us a reason for an upper bound of 125 characters. Personally, I prefer something something around 100 characters (with a bit of a soft limit).


I am getting http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused. error.

Hi, I follow the the instruction until the init step.  At that point I am getting:
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
Thanks for your help.
Context

Your Environment

Docker version docker version (e.g. Docker 17.0.05 ):
sudo docker version
Client:
Version:      1.8.3
API version:  1.20
Go version:   go1.4.3
Git commit:   f4bf5c7
Built:
OS/Arch:      linux/arm

Server:
Version:      1.8.3
API version:  1.20
Go version:   go1.4.3
Git commit:   f4bf5c7
Built:
OS/Arch:      linux/arm

What version of Kubernetes are you using? kubectl version:
sudo kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:08:12Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/arm"}
The connection to the server localhost:8080 was refused - did you specify the right host or port?

Operating System and version (e.g. Linux, Windows, MacOS):

Mac OS High Sierra

What ARM or Raspberry Pi board are you using?

Raspberry Pi 3 B+

Intro
Alexellis, thank you for your work. I appreciate you love for documentation and I admire you that you have documented all the steps.
I have the same issue but would like to provide additional/better formatted data.
Expected Behaviour
When configuring the master node,
sudo kubeadm init --token-ttl=0 should succeed.
I tried applying sed replacements described in
https://github.com/alexellis/k8s-on-raspbian/blob/master/GUIDE.md#initialize-your-master-node when the .yaml files are generated.
Current Behaviour
pi@k8s-master-1:~ $ sudo kubeadm init --token-ttl=0
[init] Using Kubernetes version: v1.14.0
[preflight] Running pre-flight checks
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Activating the kubelet service
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [k8s-master-1 localhost] and IPs [<IP_ADDRESS> <IP_ADDRESS> ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master-1 localhost] and IPs [<IP_ADDRESS> <IP_ADDRESS> ::1]
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8s-master-1 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [<IP_ADDRESS> <IP_ADDRESS>]
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.

Unfortunately, an error has occurred:
        timed out waiting for the condition
[...]
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster

It stays at this point. I use sudo kubeadm reset to reset the installation.
Possible Solution
I don't know. :smile:
Maybe I should somehow delay [kubelet-check]
[...]
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[...]

Steps to Reproduce (for bugs)

Follow https://github.com/alexellis/k8s-on-raspbian/blob/master/GUIDE.md#initialize-your-master-node
sudo kubeadm init --token-ttl=0
wait until [control-plane] Creating static Pod manifest for "kube-apiserver" then apply inline sed substitutions.

Context
systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
   Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/kubelet.service.d
           └─10-kubeadm.conf
   Active: activating (auto-restart) (Result: exit-code) since Mon 2019-04-08 16:31:21 BST; 6s ago
     Docs: https://kubernetes.io/docs/home/
  Process: 9304 ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS (code=exited, status=255)
 Main PID: 9304 (code=exited, status=255)
      CPU: 2.531s

Apr 08 16:31:21 k8s-master-1 systemd[1]: kubelet.service: Failed with result 'exit-code'.

journalctl -xeu kubelet
-- The start-up result is done.
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.393101   11134 server.go:417] Version: v1.14.0
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.396709   11134 plugins.go:103] No cloud provider specified.
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.397071   11134 server.go:754] Client rotation is on, will bootstrap in background
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.428405   11134 certificate_store.go:130] Loading cert/key pair from "/var/lib/kubelet/pki/kubelet-client-current.pem".
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: E0408 16:36:21.617689   11134 machine.go:288] failed to get cache information for node 0: open /sys/devices/system/cpu/cpu0/cache: no such file or directory
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.626248   11134 server.go:625] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.628372   11134 container_manager_linux.go:261] container manager verified user specified cgroup-root exists: []
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.628555   11134 container_manager_linux.go:266] Creating Container Manager object based on Node Config: {RuntimeCgroupsName: SystemCgroupsName: KubeletCgroupsName: ContainerRuntime:do
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.629821   11134 container_manager_linux.go:286] Creating device plugin manager: true
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.630064   11134 state_mem.go:36] [cpumanager] initializing new in-memory state store
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.630825   11134 state_mem.go:84] [cpumanager] updated default cpuset: ""
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.630943   11134 state_mem.go:92] [cpumanager] updated cpuset assignments: "map[]"
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.631681   11134 kubelet.go:279] Adding pod path: /etc/kubernetes/manifests
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.631894   11134 kubelet.go:304] Watching apiserver
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: E0408 16:36:21.656102   11134 reflector.go:126] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Node: Get https://<IP_ADDRESS>:6443/api/v1/nodes?fieldSelector=metadata.name%3Dk8s-
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: E0408 16:36:21.658924   11134 reflector.go:126] k8s.io/kubernetes/pkg/kubelet/kubelet.go:442: Failed to list *v1.Service: Get https://<IP_ADDRESS>:6443/api/v1/services?limit=500&resourceVersion=0:
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: E0408 16:36:21.659089   11134 reflector.go:126] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://<IP_ADDRESS>:6443/api/v1/pods?fieldSelector=spec.nodeName%
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.670977   11134 client.go:75] Connecting to docker on unix:///var/run/docker.sock
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.671142   11134 client.go:104] Start docker client with request timeout=2m0s
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: W0408 16:36:21.686627   11134 docker_service.go:561] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, falling back to "hairpin-veth"
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.686855   11134 docker_service.go:238] Hairpin mode set to "hairpin-veth"
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: W0408 16:36:21.688070   11134 cni.go:213] Unable to update cni config: No networks found in /etc/cni/net.d
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: W0408 16:36:21.721951   11134 cni.go:213] Unable to update cni config: No networks found in /etc/cni/net.d
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.722389   11134 docker_service.go:253] Docker cri networking managed by cni
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: W0408 16:36:21.722931   11134 cni.go:213] Unable to update cni config: No networks found in /etc/cni/net.d
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.843084   11134 docker_service.go:258] Docker Info: &{ID:O7JZ:NQVM:XFMI:GI7E:GG3W:65QB:PUSF:5CAZ:7QZR:CL3W:EQ23:DIEQ Containers:0 ContainersRunning:0 ContainersPaused:0 ContainersStop
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.843828   11134 docker_service.go:271] Setting cgroupDriver to cgroupfs
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.923486   11134 remote_runtime.go:62] parsed scheme: ""
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.923640   11134 remote_runtime.go:62] scheme "" not registered, fallback to default scheme
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.923880   11134 remote_image.go:50] parsed scheme: ""
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.923979   11134 remote_image.go:50] scheme "" not registered, fallback to default scheme
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.924959   11134 asm_arm.s:868] ccResolverWrapper: sending new addresses to cc: [{/var/run/dockershim.sock 0  <nil>}]
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.925155   11134 clientconn.go:796] ClientConn switching balancer to "pick_first"
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.925439   11134 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0x85623b0, CONNECTING
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.926529   11134 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0x85623b0, READY
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.926826   11134 asm_arm.s:868] ccResolverWrapper: sending new addresses to cc: [{/var/run/dockershim.sock 0  <nil>}]
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.926936   11134 clientconn.go:796] ClientConn switching balancer to "pick_first"
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.927166   11134 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0x8562b90, CONNECTING
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.928058   11134 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0x8562b90, READY
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.942645   11134 kuberuntime_manager.go:210] Container runtime docker initialized, version: 18.09.0, apiVersion: 1.39.0
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: E0408 16:36:21.950470   11134 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.CSIDriver: Get https://<IP_ADDRESS>:6443/apis/storage.k8s.io/v1beta1/csidrivers?l
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.952890   11134 server.go:1037] Started kubelet
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: E0408 16:36:21.953798   11134 kubelet.go:1282] Image garbage collection failed once. Stats initialization may not have completed yet: failed to get imageFs info: unable to find data in memory cache
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.955864   11134 server.go:141] Starting to listen on <IP_ADDRESS>:10250
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: E0408 16:36:21.957875   11134 event.go:200] Unable to write event: 'Post https://<IP_ADDRESS>:6443/api/v1/namespaces/default/events: dial tcp <IP_ADDRESS>:6443: connect: connection refused' (may
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.967077   11134 server.go:343] Adding debug handlers to kubelet server.
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.968478   11134 fs_resource_analyzer.go:64] Starting FS ResourceAnalyzer
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.969338   11134 status_manager.go:152] Starting to sync pod status with apiserver
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.969775   11134 kubelet.go:1806] Starting kubelet main sync loop.
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.970487   11134 kubelet.go:1823] skipping pod synchronization - [container runtime status check may not have completed yet., PLEG is not healthy: pleg has yet to be successful.]
Apr 08 16:36:21 k8s-master-1 kubelet[11134]: I0408 16:36:21.985920   11134 volume_manager.go:248] Starting Kubelet Volume Manager
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.007267   11134 controller.go:115] failed to ensure node lease exists, will retry in 200ms, error: Get https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1beta1/namespaces/kube-node
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.016133   11134 desired_state_of_world_populator.go:130] Desired state populator starts to run
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.027184   11134 kubelet.go:2170] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitial
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.028674   11134 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.RuntimeClass: Get https://<IP_ADDRESS>:6443/apis/node.k8s.io/v1beta1/runtimeclass
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.073113   11134 kubelet.go:1823] skipping pod synchronization - container runtime status check may not have completed yet.
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.088459   11134 kubelet.go:2244] node "k8s-master-1" not found
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.091127   11134 kubelet_node_status.go:283] Setting node annotation to enable volume controller attach/detach
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.134072   11134 kubelet_node_status.go:72] Attempting to register node k8s-master-1
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.137462   11134 kubelet_node_status.go:94] Unable to register node "k8s-master-1" with API server: Post https://<IP_ADDRESS>:6443/api/v1/nodes: dial tcp <IP_ADDRESS>:6443: connect:
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.144922   11134 clientconn.go:440] parsed scheme: "unix"
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.147586   11134 clientconn.go:440] scheme "unix" not registered, fallback to default scheme
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.148932   11134 asm_arm.s:868] ccResolverWrapper: sending new addresses to cc: [{unix:///run/containerd/containerd.sock 0  <nil>}]
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.149092   11134 clientconn.go:796] ClientConn switching balancer to "pick_first"
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.149437   11134 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0x8b39920, CONNECTING
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.150806   11134 balancer_conn_wrappers.go:131] pickfirstBalancer: HandleSubConnStateChange: 0x8b39920, READY
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: W0408 16:36:22.168894   11134 nvidia.go:66] Error reading "/sys/bus/pci/devices/": open /sys/bus/pci/devices/: no such file or directory
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.194171   11134 kubelet.go:2244] node "k8s-master-1" not found
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.211106   11134 controller.go:115] failed to ensure node lease exists, will retry in 400ms, error: Get https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1beta1/namespaces/kube-node
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.295595   11134 kubelet.go:1823] skipping pod synchronization - container runtime status check may not have completed yet.
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.298382   11134 kubelet.go:2244] node "k8s-master-1" not found
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.337945   11134 kubelet_node_status.go:283] Setting node annotation to enable volume controller attach/detach
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.354840   11134 kubelet_node_status.go:72] Attempting to register node k8s-master-1
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.357620   11134 kubelet_node_status.go:94] Unable to register node "k8s-master-1" with API server: Post https://<IP_ADDRESS>:6443/api/v1/nodes: dial tcp <IP_ADDRESS>:6443: connect:
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.403820   11134 kubelet.go:2244] node "k8s-master-1" not found
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.504277   11134 kubelet.go:2244] node "k8s-master-1" not found
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.604752   11134 kubelet.go:2244] node "k8s-master-1" not found
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.613838   11134 controller.go:115] failed to ensure node lease exists, will retry in 800ms, error: Get https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1beta1/namespaces/kube-node
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.641551   11134 kubelet_node_status.go:283] Setting node annotation to enable volume controller attach/detach
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.657770   11134 cpu_manager.go:155] [cpumanager] starting with none policy
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.657902   11134 cpu_manager.go:156] [cpumanager] reconciling every 10s
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: I0408 16:36:22.658083   11134 policy_none.go:42] [cpumanager] none policy: Start
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: E0408 16:36:22.659848   11134 reflector.go:126] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Node: Get https://<IP_ADDRESS>:6443/api/v1/nodes?fieldSelector=metadata.name%3Dk8s-
Apr 08 16:36:22 k8s-master-1 kubelet[11134]: F0408 16:36:22.662743   11134 kubelet.go:1359] Failed to start ContainerManager failed to initialize top level QOS containers: failed to update top level BestEffort QOS cgroup : failed to set suppo
Apr 08 16:36:22 k8s-master-1 systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Apr 08 16:36:22 k8s-master-1 systemd[1]: kubelet.service: Unit entered failed state.
Apr 08 16:36:22 k8s-master-1 systemd[1]: kubelet.service: Failed with result 'exit-code'.

RPi 2 B rev1.1

Experiencing the same issue as well Pi 3B

Running into the same problem on Ubuntu 16.04 with v1.15.0. Also, internet does not work after kubeadm init.

See my recommendation to use k3s in the main readme.
I'd encourage you to raise an issue with kubeadm in the meantime. https://github.com/kubernetes/kubeadm

I am experiencing the same issue with Ubuntu 18.04 and kubeadm v.1.15.3

Same problem Centos 7, kuber 1.16

I am experiencing the same issue with Ubuntu 18.04 and kubeadm v1.16.1:
kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp <IP_ADDRESS>:102

and the output gave me some advises:
This error is likely caused by:
    - The kubelet is not running
    - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
    - 'systemctl status kubelet'
    - 'journalctl -xeu kubelet'

after journalctl, I got the failed message:
kubelet[27956]: F1014 19:15:43.743985   27956 server.go:271] failed to run Kubelet: failed to create kubelet: misconfiguration: kubelet cgroup driver: "cgroupfs" is different from docker cgroup driver: "systemd"

Experimenting the same error

Experimenting the same error

Centos 7 the same

Please try k3s which is designed to accommodate and tested on RPi.
This repository is for Kubernetes on Raspbian, I would not expect CentOS and other distributions to work out of the box since they are not tested.
For technical support on kubeadm please join the Kubernetes Slack, PRs are welcome.
http://slack.kubernetes.io


k3s: package is missing a runtime dependency on libseccomp

Describe the bug
The k3s package is built incorrectly, such that automatic runtime dependency misses one of its runtime dependencies. (For anyone curious, this is on me. I wrote the initial package, and it's been subtly broken since the beginning).
To Reproduce
The easiest way to reproduce is to boot a system that's fairly recent (nixos-unstable currently is new enough), make sure you rna nix-collect-garbage, and observe the following error:
$ nix-shell -E "(import (builtins.fetchTarball "https://github.com/NixOS/nixpkgs/archive/718305392f0e66ac4693eaaf66e49fce8a3ae744.tar.gz") {}).pkgs.k3s"

[nix-shell:~]# k3s kubectl version
kubectl: error while loading shared libraries: libseccomp.so.2: cannot open shared object file: No such file or directory

Note that this error will not occur if the correct store path for that libseccomp happens to have been pulled in by another package, such as systemd. The above does reproduce when using the nixos channel version  nixos-21.03pre248308.5d0e2dedd55.
Expected behavior
The libseccomp dependency of k3s should be correctly captured in the usual nixpkgs runtime dependency way, and so this error shouldn't occur.
Additional context
So, why does this happen?
The root problem is pretty easy to understand once you spot it. One of the requirements of automatic runtime dependencies working is that all referenced libraries appear as plaintext strings within the output directory.
Unfortunately, k3s is packaged in a a weird way.  On the first run, it unpacks that tarball into a data directory, and then runs those binaries.
nixpkgs mostly re-uses the upstream packaging scripts for building the k3s cli binary: https://github.com/NixOS/nixpkgs/blob/a948654086898aa95541bcd2ab39325588dc3332/pkgs/applications/networking/cluster/k3s/default.nix#L199
Unfortunately, k3s's package-cli script gzips all of the binaries it packs in there, and gzipping them means automatic runtime dependencies no longer work.
https://github.com/rancher/k3s/blob/03f05f93370f636fd3c5162a06fee54e40f9dd91/scripts/package-cli#L38-L39
What do we do about this?
So, how do we fix this?
I've got a few options that I think will work:

Don't compress the "data" tarball so automatic runtime dependencies still finds it
This one's simple, but increases the size of the k3s binary. It might be the right fix if nothing else seems more compelling. I haven't checked the size difference yet.
Patch k3s to not use the gzipped data tarball, and instead make the data directory a nix store path.
I think the data directory is meant to be read-only, which actually makes this pretty attractive. It means more maintenance work and diverging from upstream a bit, which are the main downsides.
Patch k3s to not use any bindata stuff at all, just rely on a wrapper script + $PATH
This one has similar tradeoffs as 2, and in practice is probably pretty similar.
Make sure k3s dependencies are all statically compiled & remove the libseccomp dependency.
Right now, libseccomp seems to be the only dynamically linked dependency, so maybe we can just remove it and ignore this problem? I don't think this is actually viable since removing libseccomp may result in a real reduction in security and break some uses of the package.

I think my current plan is to see how much of a size difference 1 makes, and then spend some time digging into 2/3 to see how much work it actually is.
I am a little wary that 2&3 are diverging from upstream's packaging a bit more than 1, and ends up with an arguably different thing than k3s.
Notify maintainers
cc @euank
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.35, NixOS, 21.03pre248308.5d0e2dedd55 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.7`
 - channels(root): `"nixos-21.03pre248308.5d0e2dedd55"`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
- k3s
# a list of nixos modules affected by the problem
module:
- k3s

Option 1 also requires patches to the code since it assumes the contents of the bindata data.tar.gz are in fact gzipped, and errors out if they're not.

After thinking about this a little more, there's another pretty easy option. If we just put an uncompressed reference in a text file somewhere, that solves things. We already have the binary dependencies packaged into the big k3s binary separated into their own derivations, so leaving behind a reference to those store paths in a text file is both really easy, and solves this in a pretty nix-like way. I'll make a PR for that solution, because it seems both really easy, and like it fits the nix model pretty well!


Proper node configuration

Right now, Krustlet uses a bunch of hardcoded values for creating the Node object in Kubernetes (such as the IP address and hostname). We should follow similar patterns to normal kubelet for configuring these values, so part of this task will be investigating how kubelet does it in mainline Kubernetes.

I also went and dug through the Kubelet codebase. The initial node configuration is found here and you can basically override any of the IP and hostname values using a flag. The default node IP address comes from the system using the method found here: https://github.com/kubernetes/kubernetes/blob/61d36e4a43b831f960b190b81d371cb33b5f20d1/pkg/kubelet/nodestatus/setters.go#L189
I'll take this issue on and get an implementation in place


Use async/await

Use async and await to simplify tests with promises. I found that this made timing more consistent and allowed the elimination of uses of $nextTick in tests.

Informed by the vue-test-utils documentation:
https://vue-test-utils.vuejs.org/guides/testing-async-components.html
I found that I didn't need to use the flushPromises utility mentioned, but it could easily be introduced later if needed.


Add MIT License

Signed-off-by: Prakash<EMAIL_ADDRESS>Issue No.  https://github.com/naufaldi/time-tracking/issues/20

Hi @naufaldi Can you please review it and merge this PR.


Swift 3.0 compiler error

Version of protoc (protoc --version)
libprotoc 3.1.0
Version of ProtocolBuffers.framework
3.0.5
.proto file to reproduce

Description
I cloned the branch protobuf-swift-ProtoBuf3.0-Swift3.0 and run ./scripts/build.sh
but resulted in the error:
This file was generated by an older version of protoc which is incompatible with your Protocol Buffer headers. Please regenerate this file with a newer version of protoc.
I have update the libprotoc to latest version as shown above , could you offer me a solution or some ideas? Thanks you

You should use master branch.

But when I compiled the .proto files the .pb.swift files ends up in Swift 2 syntax , I want the version of Swift 3 , can you give me some suggestion?

You need reinstall protobuf-swift compiler. how you installed him erly, from homebrew?

Yes, I have red some issues related to  that and find out that install through homebrew is not worked since it have no version of Swift3 , so I have uninstall it and reinstall
The good news is I suddenly found that Xcode have not complained the syntax yet , may be  something wrong before but I did not figure out
Thanks for your patience


feat: CLIs should accept _ in digits passed to it

Component
Forge, Cast, Anvil
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (0ad127a 2024-07-25T00:18:26.746279000Z)
What command(s) is the bug in?
forge test -f http://<IP_ADDRESS>:8545 --isolate --fuzz-runs 4_294_967_290
Operating System
macOS (Apple Silicon)
Describe the bug
 forge test -f http://<IP_ADDRESS>:8545 --isolate --fuzz-runs 4_294_967_290

error: invalid value '4_294_967_290' for '--fuzz-runs <RUNS>': invalid digit found in string

$ forge test -f http://<IP_ADDRESS>:8545 --isolate --fuzz-runs<PHONE_NUMBER>

This works.
Underscore is allowed in foundry.toml, so it would make sense I would think that it would similarly be accepted as command line argument.

We would have to go out of our way to annotate every single integer command line option with a custom parser since the default one does not support this. I don't think this is worth the effort.


⚠ 한경주요지수-코스피200 has degraded performance

In 9d3d1d2, 한경주요지수-코스피200 (https://markets.hankyung.com/indices/kospi200) experienced degraded performance:

HTTP code: 200
Response time: 8678 ms

Resolved: 신규상장 performance has improved in 98dc6cb.


[Admin] (redirect) Fix invalid redirect for recently deprecated page.

Docs Build status updates of commit a207d8a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@davidchesnut here's the PR that fixes the redirect. Please review when you have time...thanks!


chore: Migrate third party images for fluent-bit and telemetry-self-monitor to Github Actions

Description
Changes proposed in this pull request:

Migrate fluent-bit mage build task from Prow Job to Github Actions
Migrate telemetry-self-monitor image build task from Prow Job to Github Actions

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

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


Timeout on rssh

Hi. When I use "ssh -D 5005 -J server hostname", then I start to use this port as a proxy, after a while rssh kills my session by timeout, is there any way to remove or change this? I start e.g. a network scan, some long running exploits and after a while rssh just kills me and everything hangs up.
This was a long time ago, in your old updates, then it stopped killing the session, if I use the port, it lived as long as the port is used, but now it's like before, it kills the session just by timeout, both linux and windows.

Hm. I was having an issue like this but assumed it was flakey networking.
I haven't made any changes to that aspect of rssh so not sure how its decided to change.
I'll do some regression testing.
You can disable timeouts entirely with - - timeout 0
However I think this problem might be different than just the timeout mechanism.

Got it. Yeah, I also thought it was a connection at first, but then some update made it stable, but now it's throwing out again.

Very annoying, I'll see if I can get a situation that replicates it. But otherwise I may temporarily just remove the timeout feature and see if that helps

Cool I can replicate it.
For my future reference, its not just jump (-J) hosting, its all connections.

Additional information. After the first disconnection it seems to become stable.

@chikamobina Are you using the clients in foreground mode? (--foreground) as it seems I can only get this behavior to happen in that mode?

Glad to hear the windows dll works, I honestly havent tested it since I made it.

@chikamobina can you try v2.1.1 and see if you get the same disconnects on your backgrounded clients?
I cant replicate backgrounded clients dying, I've identified the change that causes foreground clients to die (although not why it causes death)

Okay, I've removed the code that was causing this issue (at least the foreground crashing bit).  Am doing a release as this is quite not good in terms of bugginess.
Tell me if you get the weird disconnections still please.

@chikamobina can you try v2.1.1 and see if you get the same disconnects on your backgrounded clients?
I cant replicate backgrounded clients dying, I've identified the change that causes foreground clients to die (although not why it causes death)

I was just testing this on the last version

Okay, I've removed the code that was causing this issue (at least the foreground crashing bit). Am doing a release as this is quite not good in terms of bugginess.
Tell me if you get the weird disconnections still please.

I'll let you know when I test it, thank you.

As I have been using this myself without issue Im going to close this. Feel free to re-open it if you are still experiencing issues.

Okay, I have tested and this problem observed in my lab with the firewall only, in other places everything works fine, thank you.


Next event countdown timer

Maybe a nice little addition to the upcoming events section? Enhancement?

Perhaps I could be convinced by good design? :wink: this has made me wonder about adding "human readable" timestamps to the events though:

"Next Thursday at 7pm", "Tomorrow at 7pm", but I'm not sure how reliable that will be with this static build site thing-a-majig :wink:

It is a good job I am not easily offended today 😉... I will have a think / play with designs and come back to you on this point.

Next Thursday at 7pm", "Tomorrow at 7pm", but I'm not sure how reliable that will be with this static build site thing-a-majig
I don't think there are any issues as far as I know, Gatsby uses something similar for their yearly copyright tag but I will again check and come back to you.

I can not find a nice way of presenting the 'countdown timer' so I instead decided to take a stab at the "human readable" timestamps. PR here: https://github.com/NorfolkDev/norfolkdevelopers-website/pull/57
Lemme know if something is wrong and I will get it sorted!


Revert "Two more places to check whether attempting half_closed connecton logic is feasible"

This reverts commit 653927f9aab9a3cbe8f09521dd8c8154ccbc1614.
Erroneous fix caused KEEPALIVE to fail on HTTP/1.1 over HTTPS
Found by @zwoop, @mlibbey, @masaori335  and @maskit to have bad interactions with PR #4213.  In a separate PR I will add tests to catch regressions in client-side keep alive.

Cherry-picked to 8.0.x


fixed username url

Coverage decreased (-0.1%) to 75.768% when pulling a8a9e970a1b47d447c3e54f5c01e610d70e7031c on Tr0nYx:master into 56bd4a9a10de383a022512e2726d36a6c35596e6 on Alpha-Trader:master.


Defer loading of user info until when it's really necessary

Goal
UserInfo was being loaded form preferences way before we actually need it, which delays the execution of startup on the main thread.
Instead, we defer this to when it's consumed by putting it behind a provider which will be executed when it's first read. Access to the in-memory copy is synchronized, which shouldn't impact runtime very much.
This also fixes an existing race condition where concurrent modification could result in some values being lost, though it's probably not very likely.
Testing
Existing tests cover these workflows

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#539
#538
#537  👈
#536
#535
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite

Merge activity

Mar 11, 11:07 AM EDT: @bidetofevil started a stack merge that includes this pull request via Graphite.


Update README.md

Just fixing a broken link in the README

Didn't see a PR was already open for this https://github.com/philipwalton/flexbugs/pull/207


setOption("value", '') doesn't work

I have "reset code" button and my code looks like this:
$('#reset-code__btn').click(function () {     myCodeMirror.setOption("value", '');     console.log(myCodeMirror.getValue()) })
It works fine when i am trying to reset code for the first time, but then it isn't working. How to fix this?

So, i just replaced myCodeMirror.setOption("value", '') by myCodeMirror.setValue(''); and now it works


Wording

Hi,
Unless it's generally accepted at this point, I think we should consider rephrasing "from DI" in the following occurrences:

"Get an ILogger<TCategoryName> object from DI."
"To write logs in the Program class, get an ILogger instance from DI:"

My thought process is that DI can either be the pattern, or the MS.Ext.DI libs. Even in the case where the provided example code explicitly resolves an instance, it might be confusing.
What do you think?
Regards,
Adam

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

ID: 7184a308-a254-9350-a5cd-5bced1f369ae
Version Independent ID: 726e3bf1-f367-d733-8933-bccc04da0e16
Content: Logging in ASP.NET Core
Content Source: aspnetcore/fundamentals/logging/index.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

@Anarkin Thanks for the question.  I've never seen any indication that "from DI" in contexts like these has been misunderstood, and we use the phrase throughout our docs.  The acronym DI should only appear in an article after being introduced earlier in the same article as "dependency injection (DI)", with either a short explanation or a link to the DI article. Either way, "DI" should be understood as the DI system used by ASP.NET Core, and "from DI" as shorthand for "from the DI container".


CI: add coverage report

Current coverage is 47.66% (diff: 100%)

Merging #11 into master will decrease coverage by 1.23%

@@             master        #11   diff @@
==========================================
  Files            83         83
  Lines          2170       2075    -95
  Methods           0          0
  Messages          0          0
  Branches        144        143     -1
==========================================
- Hits           1061        989    -72
+ Misses         1055       1031    -24
- Partials         54         55     +1

Powered by Codecov. Last update 8429c72...80f347d


[BUG] NSTool incorrectly marks SaveDataOwnerId as FAIL

About
When verifying Program NCA or NPDM files, SaveDataOwnerId is incorrectly marked as FAIL.
Steps to reproduce

Locate a Program NCA or NPDM file that has SaveDataOwnerId values populated
Run NSTool in verify mode for that file nstool -y <file path>

Actual output
Pokemon Legends Arceus Program NCA:
[WARNING] ACI/FAC SaveDataOwnerId: FAIL (0x010003f003a34000 (1) not permitted)
[WARNING] ACI/FAC SaveDataOwnerId: FAIL (0x0100187003a36000 (1) not permitted)
[WARNING] ACI/FAC SaveDataOwnerId: FAIL (0x0100abf008968000 (1) not permitted)
[WARNING] ACI/FAC SaveDataOwnerId: FAIL (0x01008db008c2c000 (1) not permitted)
[WARNING] ACI/FAC SaveDataOwnerId: FAIL (0x0100000011d90000 (1) not permitted)
[WARNING] ACI/FAC SaveDataOwnerId: FAIL (0x010018e011d92000 (1) not permitted)
[NCA Header]
  Format Type:     NCA3
  Dist. Type:      Game Card
  Content Type:    Program
  Key Generation:  13
  Sig. Generation: 0
  Kaek Index:      Application (0)
  Size:            0x181024000
  ProgID:          0x01001f5010dfa000
  Content Index:   0
  SdkAddon Ver.:   11.4.6 (v184813056)

Expected output
Pokemon Legends Arceus Program NCA:
[NCA Header]
  Format Type:     NCA3
  Dist. Type:      Game Card
  Content Type:    Program
  Key Generation:  13
  Sig. Generation: 0
  Kaek Index:      Application (0)
  Size:            0x181024000
  ProgID:          0x01001f5010dfa000
  Content Index:   0
  SdkAddon Ver.:   11.4.6 (v184813056)

This appears to be because NSTool compares the SaveDataOwnerId values between ACI0 and ACID. Nintendo does not appear to populate ACID with SaveDataOwnerId values, so this check should be removed.

This issue has been fixed in development-tip (https://github.com/jakcron/nstool/commit/c7fe8bcd0fde494042870a18506de65fa0fbcbd5), and should be present in any release after 1.8.0


nx 11 is not supported anymore

hi, this commit broke compatibility with nx11 which we are extensively using in my company
Now I'm getting an error Project root not found for projectName(which is super confusing because it holds no context and I was sure it comes from nx itself)
So now we can not use new features that being added to this project, for example, this one
Can you please bring compatibility back?

Breaks on Nx v15.1.1 as well. Same issue.
Downgrading to<EMAIL_ADDRESS>fixed the issue.
I think it might be possible that the bug is actually in @nrwl/devkit and will be fixed in v15.7.0.
see: https://github.com/nrwl/nx/pull/14854
Only had a quick glance, so not 100% sure.

yes<EMAIL_ADDRESS>also helped me, but I really need that feature I added in a PR and which is released in later versions

Too many breaking changes in this devkit, it's not following semver like the rest of their packages. I discussed this last time and concluded that we should bump a major in @jscutlery/semver for each @nrwl/devkit minor...

@edbzn can you for now bring back compatibility with both devkits?

@cakeinpanic I do not have enough time to give today, unfortunately, and I won't be available for a couple of days, so if you raise a PR I'll merge and release but can't do it myself.


What should syndication links be?

When a BF user federates a post from their web site into the fediverse, should they include a u-syndication link for it? What should that link be?
Mastodon instance do generate their own post ids and URLs for these posts, eg https://indieweb.social/<EMAIL_ADDRESS>which show their own rendering if you're logged into that instance, but if you're not, they redirect you to the original post on the web site.
Any other ideas?

Lots of discussion: https://chat.indieweb.org/2022-11-19#t1668886259526500
Conclusion is basically the webaction, remote follow/interact UI where you type in your instance, like Mastodon had until v4. See #60

New conclusion, use your Bridgy Fed user page, eg https://fed.brid.gy/user/snarfed.org. Has a remote follow UI, and advertises BF's webmention endpoint, so it works for automatic webmention sending.


xDnsServerConditionalForwarder: Adds resource

Pull Request (PR) description
Adds an xDnsServerConditionalForwarder resource
This Pull Request (PR) fixes the following issues
N/A
Task list

[x] Added an entry under the Unreleased section of the change log in the README.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md.
[x] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[x] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #88 into dev will increase coverage by 1.24%.
The diff coverage is 82.05%.

@@            Coverage Diff             @@
##              dev      #88      +/-   ##
==========================================
+ Coverage   72.56%   73.81%   +1.24%
==========================================
  Files          10       11       +1
  Lines         514      592      +78
==========================================
+ Hits          373      437      +64
- Misses        141      155      +14

Impacted Files
Coverage Δ

...Forwarder/MSFT_xDnsServerConditionalForwarder.psm1
82.05% <82.05%> (ø)

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 4b84752...bda13f5. Read the comment docs.


Client as a service: Message Recieved Event

I have a client running as a service. It connects to the server. It subscribes to topics.  It just doesn't ever receive messages. The Client as a service is logging all activity to a couple of text files on the c: drive. I log that the service started, the client started, the client connects to the server, the client subscribes with the server, and finally, when messages are received by the client.
I have the test from GitHub as a base to test with. The server, when receiving messages logs to the console, so I see that messages are received.  I am using the client test to send messages, as well as subscribe to messages and log to the console.  I can see messages coming to the server, and then back to the client that sent them.
Them problem is the client as a service never logs that it has received a message. The service client has the same subscription as the console client, subscribed to "#".  The client is publishing to the client test default of "A/B/C" with the payload of "Hello World". Any idea of what is going wrong here? I may try to build my sql connector into the server, but I was trying to keep the server free and just dealing with the messaging.  Putting the logging into a client.  But the client running as a service never gets a message.

Disregard.  It is functioning.


Add shouldResetTimeout

Summary
Set shouldResetTimeout to true in axios-retry config
Explanation
Without this configuration option set to true, we get infinity loop because default timeout is set to 1ms, and that request always fails
Steps to reproduce

Listen on each price change through websocket
on each price change send get request to coinbase
kill your internet connection, restore it back after 5 seconds
you are now in infinity loop

Thank you very much for your contribution, @tcar121293! Your fixes got released with v3.0.2. 🚀


treewide/nixos: remove with lib; part 1

Description of changes
part of #208242
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@philiptaron would you consider this "size" of MR ok to review?
I am going to split up the individual services.
(I have already written a shitty script to generate these changes, with a total of 1243 changed files. I will review all files by hand before I submit them via PR.)

@Stunkymonkey: I think a few things 🙂

I really like one commit per module, named for the module. That helps on many fronts, but especially rebuild and regression hunting.
I like about ~150 max commits per PR. That's about my ability to review and say yes. In total, that would be about 8 or 9 PRs for the whole of the nixos/ directory. Totally manageable. Add me for all of it.
I really want to see the tool that you're using, "shitty" or not. That helps me build an intuition for what sort of defects or otherwise to look out for.
If there's a module with more than ~50 lines of changes in it, skip that for the bulk PRs.

Thank you for tackling this refactor!

@philiptaron my "shitty" script (simple replace):
shitty-patch.sh
#!/usr/bin/env bash

# Get the list of files containing "with lib;"
files=$(grep -rlFx "with lib;" /home/felix/code/system-installs/nixpkgs/nixos/)

options=(
    "any"
    "attrByPath"
    "attrNames"
    "attrValues"
    "boolToString"
    "cli."
    "concatLists"
    "concatMap"
    "concatStrings"
    "const"
    "elem"
    "escape"
    "filter"
    "flatten"
    "flip"
    "foldAttrs"
    "foldl"
    "foldr"
    "generators."
    "getBin"
    "getDev"
    "getExe"
    "hasAttr"
    "hasPrefix"
    "hasSuffix"
    "imap1"
    "isAttrs"
    "isBool"
    "isDerivation"
    "isInt"
    "isList"
    "isPath"
    "isString"
    "last"
    "length"
    "lessThan"
    "lists"
    "listToAttrs"
    "literalExpression"
    "literalMD"
    "maintainers."
    "makeBinPath"
    "makeLibraryPath"
    "mapAttrs"
    "maybeEnv"
    "mergeOneOption"
    "mkAliasOptionModuleMD"
    "mkBefore"
    "mkDefault"
    "mkEnableOption"
    "mkForce"
    "mkIf"
    "mkImageMediaOverride"
    "mkMerge"
    "mkOption"
    "mkOrder"
    "mkOverride"
    "mkPackageOption"
    "mkRemovedOptionModule"
    "mkRenamedOptionModule"
    "nameValuePair"
    "optional"
    "recursiveUpdate"
    "removePrefix"
    "replaceStrings"
    "setPrio"
    "singleton"
    "sort"
    "stringAfter"
    "stringLength"
    "stringToCharacters"
    "substring"
    "subtractLists"
    "teams."
    "toList"
    "toUpper"
    "types."
    "unique"
    "versionAtLeast"
    "versionOlder"
    "zipAttrs"
    # "all" too many other instances
    # "partition" too many other instances
)

# Function to escape special characters for sed
escape_sed_pattern() {
    echo "$1" | sed 's/[.[\*^$+()|]/\\&/g'
}

# Loop over each file
for file in $files; do
    # delete empty before
    sed -i '/with lib;/,$ b; /^$/d;' "$file"
    # delete empty after
    sed -i '/with lib;/{N;s/\n$//}' "$file"
    # delete match
    sed -i '/^\s*with lib;\s*$/d' "$file"

    for str in "${options[@]}"; do
        # Escape the string for use in sed
        escaped_str=$(escape_sed_pattern "$str")

        # Prepend "lib." to the current string
        lib_str="lib.$str"

        # Escape the lib_str for use in sed
        escaped_lib_str=$(escape_sed_pattern "$lib_str")

        # Use sed to replace occurrences in the temporary file
        sed -i '/inherit/!s/'"$escaped_str"'/'"$escaped_lib_str"'/g' "$file"
    done

    sed -i "s/with maintainers;/with lib.maintainers;/g" "$file"
    sed -i "s/with types;/with lib.types;/g" "$file"
    # revert wrong locations
    sed -i "s/mlib.any/many/g" "$file"
done

~150 max commits per PR

I guess you wanted to say about "lines of changes"?
I started with #336404

No, I'm saying 150 commits (150 files) 😁
I feel quite adept at reviewing patterns.

The tool sadly makes a few bugs -- see if you can evolve it a bit so it doesn't make this:
https://github.com/NixOS/nixpkgs/blob/c8503c7029fcbbac6a0f190b9580b6067e217c8b/nixos/modules/security/pam.nix#L1607-L1608

https://github.com/NixOS/nixpkgs/commit/3b7622d31b50e332a54955d2ef10621ce39ec0e9#diff-9bd6954b6c183d51a0dcbf1f540c61b89a2427e1d3ee7af1dccd98ca2c859279R118 This must've slipped. utils has no lib inside, and this broke my system rebuild.

How do we currently ensure that the rest of the changes are correct and not just because others haven't used them yet?

easiest way imo would be to fix the script and then rerun it before this PR to identify the breakages. the problem is the missing \b at the end which ends up matching substrings.

Okay I've started running it locally, but it seems to be quite slow, not sure when it'll finish.


Attempt to show moderator ID in ban/unban reasons

Is where a reason why Pidroid should show moderator IDs when a user is banned?

I'll probably want to change how it works to allow moderators to selectively have anonymity, either as a punishment menu option or a server-wide setting by administrators. Right now, it works very inconsistently.

oops

https://github.com/JustAnyones/Pidroid/pull/47#issuecomment-1932446520

https://github.com/JustAnyones/Pidroid/commit/b7b121a8e78e818cffcdf72491da68f5f5e19fc3#diff-f63986992d624ab6c2f5cdef5db6ccedf197331a824377b1caa198a0aaf4fcf1R74?


"Invalid URL" error. Script does not work

Done in PowerShell 7 on windows 10
Command used:
py main.py -room_id<PHONE_NUMBER>637265062 -mode manual
Output:

|_   () || || | | |  ()_ _____  | _ ___ __ ___ _ _ | |_ _ _
| | | | / / | |/ _ \ / / | || \ V / -) |   / -) / _ \ '/ ` / -) '|
|| ||_\ |_|_/_\ |||_/___| ||____/| _,___||
[] USERNAME: imkevinhart
[] ROOM_ID:<PHONE_NUMBER>637735062
[] URL M3U8
[] URL FLV
[*] RECORDING...
Invalid URL '': No scheme supplied. Perhaps you meant http://?

Try the new version.
When a user has never been live, it is not possible to get the room_id

From the tests I did, "imkevinhart" has never been live, so you have no way of knowing his room_id

def get_room_id(user:<PHONE_NUMBER>381814555) -> str:
tiktok_url = "https://www.tiktok.com/@{shopquangchau_thukid}/live"
try:
response = req.get(tiktok_url)
response.raise_for_status()
content = response.text
return re.search("room_id=(.*?)"/>", content).group(1)
Sorry i'm newbie, why it's Missing user/room id error?

Try the new version.
When a user has never been live, it is not possible to get the ro

the first time when I use it worked, but after I always got this error : HTTPConnectionPool(host='pull-flv-f16-tt02.fcdn.us.tiktokv.com', port=80): Max retries exceeded with url: /stage/stream-35709xxxxx74_or4/index.flv (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x00000268EEAF0D30>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed'))
What should got wrong.

I got the same error from everyone I tried, even when they were live. It worked the first time (used manual mode), then I used automatic mode on someone who was offline and noticed it didn't start working when they went online. Now it won't work at all in either mode.

I tried with vpns is not a blocking ip, i still have this issue, is something about https and http i think  I tried other code made with node js, and works perfect, every live.

I tried with vpns is not a blocking ip, i still have this issue, is something about https and http i think I tried other code made with node js, and works perfect, every live.

What's the other code?

Thank you Michele.

Any updates?

Fixed

How can I get work youtube-dl.exe on linux ? Thanks.

How can I get work youtube-dl.exe on linux ? Thanks.

got it, thanks.

How can I get work youtube-dl.exe on linux ? Thanks.

https://phoenixnap.com/kb/install-ffmpeg-ubuntu
Try this or search on google for other distrubution

I get this error when I try to use it:
'youtube-dl' is not recognized as an internal or external command,
operable program or batch file.

Windows or linux?

Windows

Well, when I running something like this I try run the terminal or powershell where youtube-dl.exe is. And then run it the live tiktok py.

The tiktok py and youtube-dl are both in the same directory if that's what you mean.

And obvsly you terminal is running in the folder path. Right? Because I tested right now and it works for me, pretty well.

Yes, I go to cd TikTok-Live-Recorder before I try using it. The default directory my terminal starts out in is the same one that youtube-dl and the tiktok py are both in.

I get this error when I try to use it:
'youtube-dl' is not recognized as an internal or external command,
operable program or batch file.

I have youtube-dl and it's added to my PATH.

Try:
pip install youtube-dl

I get this error when I try to use it:
'youtube-dl' is not recognized as an internal or external command,
operable program or batch file.

I have youtube-dl and it's added to my PATH.

Try: pip install youtube-dl

Thanks! This did help and it works now. I did notice that the automatic mode doesn't work.  If you run a command in automatic mode when someone is offline, it doesn't start working after they come on. It only says this as if they're still offline:
[*] [user] is offline
waiting 5 minutes before recheck


⚠ Bofrost.fr has degraded performance

In f61a9a4, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1183 ms

Resolved: Bofrost.fr performance has improved in ca08cf6 after 6 minutes.


~$(foo ...) should be ~$(%foo ...)

for consistency with other hint syntaxes etc.

I agree.
On Tue, Feb 23, 2016 at 11:26 AM, Anton Dyudin<EMAIL_ADDRESS>wrote:

for consistency with other hint syntaxes etc.
—
Reply to this email directly or view it on GitHub
https://github.com/urbit/arvo/issues/21.

PRed.
On Tue, Feb 23, 2016 at 11:32 AM, Curtis Yarvin<EMAIL_ADDRESS>wrote:

I agree.
On Tue, Feb 23, 2016 at 11:26 AM, Anton Dyudin<EMAIL_ADDRESS>wrote:

for consistency with other hint syntaxes etc.
—
Reply to this email directly or view it on GitHub
https://github.com/urbit/arvo/issues/21.

Forgot my "closes #21" in d690fa4


perf(twoslash): calculate playgroundURL on-demand

This would improve performance in usages like https://shikiji.netlify.app/packages/twoslash where the playgroundURL is never used, allowing saving bits to optionally not bundle lz-string

It's been a couple months (sorry); I know that https://www.npmjs.com/package/twoslash claims to succeed the package here. Would it make sense to use that package now instead?

It wasn't blocking anything so no worries - I am more curious about what's the plan of the maintenance work for packages in this repo? For example, that data module is still on ts 4:
https://github.com/microsoft/TypeScript-Website/blob/c2b124d3855b09b1682b420e93f585be5c66e671/packages/ata/package.json#L29 and haven't been published for a while now.
I would volunteer myself to do the minimal maintenance work (merging non-controversial PRs, widen version ranges, and fixing releases) for this project if needed (and if that's ok with Microsoft's policy) - Otherwise, let me know if if there is any other way I could help on this. I don't want to end up forking everything if there are better options to collaborate.
Thank you!

That being said, having to fix some stuff here recently, I think that we know concretely how to get things running again, so I think I could get some stuff fixed soon.

FYI the repo is now publishable again; sorry it took so long. I've taken the liberty to update your PRs and add changesets.
That being said, I think it may turn out to be a better move to deprecate @typescript/twoslash and start using twoslasher along with other updated deps.

Though, this PR does appear to make the site not build; quite possible this approach is incompatible with gatsby somehow due to this prop not being serializable.

Yeah, IMO deprecating is the right call here


Event rule prechange null when assigning asset

I have found that the Event Rule feature of Netbox always outputs "prechange" as null when it is triggered by the Inventory plugin.
This specifically happens when using the "Edit Assignment" button and either assigning or un-assigning an asset to a device.
Example (removed some of the extra data):
{
  "event": "updated",
  "timestamp": "2024-12-11T21:46:43.439904+00:00",
  "model": "device",
  "username": "admin",
  "request_id": "072d20b9-f291-49f0-b9f6-6dd407c96790",
  "inventory_item_count": 0
  "snapshots": {
    "prechange": null,
    "postchange": {
      "created": "2024-12-10T03:14:39.898Z",
      "last_updated": "2024-12-11T21:46:43.364Z"
      },
      "tags": []
    }
}

We have an integration with another service that syncs devices when the serial number is updated. This is difficult to do as we have no way of telling what the serial number was previously if people use the Edit Assignment button.
Not sure if this is intended or not.

seems to be fixed now, thanks! made my life much easier


fix(peerDeps): remove experimental svelte5 support from v3

to avoid peer dependency mismatch with svelte-hmr
Svelte5 users can upgrade to next major "@sveltejs/vite-plugin-svelte": "^4.0.0-next.6" in their devDependencies

closing in favor of #964


CI: Export pytest and coverage reports

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@feb74c9). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main       #45   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         5
  Lines           ?       355
  Branches        ?        78
========================================
  Hits            ?       355
  Misses          ?         0
  Partials        ?         0

Flag
Coverage Δ

pytest
100.00% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Delegate API endpoint expansion/upgrade

Would it be possible to provide additional parameters to be utilized for endpoints:
/getpublicaddresspaymentinformation
/getblocksfound
additional parameters for both endpoints:

Ascending vs descending based on boolean true/false/None
Limit of returned data in array  as integer

Thank You.
Animus

Hi @AnimusXCASH
I will try to add in the next release then

Hi @AnimusXCASH
I added the blocks found to the block_producer_block_heights to the delegate global API
http://delegates.xcash.foundation/getdelegatesinformation?parameter1=DELEGATE_NAME
still need to do the others

Hi @AnimusXCASH
I will add the request to the testnet, but I only will add the start number and total amount of items so applications can have pages of data.
The sorting by what field and by how should be application specific and coded in the front end application that uses the API.
examples
http://test/getpublicaddresspaymentinformation?public_address=XCA&start=100&amount=50 // get 100-150 (or up to max)

you can use all for amount if you want all of them
you have to use 1 for the start item, not 0
same for the other one but it does not have a public_address just start and end

Hi @AnimusXCASH I added the blocks found to the block_producer_block_heights to the delegate global API http://delegates.xcash.foundation/getdelegatesinformation?parameter1=DELEGATE_NAME
still need to do the others

Has this been integrated already or is it still on Testnet only?

Hi @AnimusXCASH
I Added it for sure to the shared delegates API, and I think the main website API
but after I added it we found later in June that we needed to remove the blocks from the main delegates due to an error that has not been fixed yet. So running that command might pull nothing now.
I can let you know when its been fixed, but you can get any shared delegates block by visiting their API and running that command (or the get payment details api)


JS TS server frequent crashing

Type: Bug
Just typing the code crashes the server on the M1 Mac
VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:32:21.587Z)
OS version: Darwin arm64 22.1.0
Modes:
Sandboxed: No
Remote OS version: Linux arm64 5.10.109-0-virt
Remote OS version: Linux arm64 5.10.109-0-virt

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
2, 2, 4

Memory (System)
16.00GB (0.19GB free)

Process Argv
. --crash-reporter-id ef1cab6e-7ae9-41ad-a673-66dc1f22f903

Screen Reader
no

VM
0%

Item
Value

Remote
Dev Container: Existing Dockerfile @ colima

OS
Linux arm64 5.10.109-0-virt

CPUs
unknown (2 x 0)

Memory (System)
1.93GB (0.03GB free)

VM
0%

Item
Value

Remote
Dev Container: Existing Dockerfile @ colima

OS
Linux arm64 5.10.109-0-virt

CPUs
unknown (2 x 0)

Memory (System)
1.93GB (0.03GB free)

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

macos-modern-theme
dav
2.3.18

remote-containers
ms-
0.266.1

remote-ssh
ms-
0.94.0

remote-ssh-edit
ms-
0.84.0

vscode-remote-extensionpack
ms-
0.23.0

remote-explorer
ms-
0.0.3

wordpress-toolbox
wor
1.3.15

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1cf:30587006
282f8724:30602487
iaj6b796:30613358
89544117:30613380
fim-prod:30623723

Please try collecting the TS Server log from the crashed instance:

Set "typescript.tsserver.log": "verbose"

Restart VS Code and reproduce the problem

Open the TypeScript section of the output panel

At the very top, find the first line that prints to path to the semantic error log file. It should look something like:
[Info  - 19:54:59.247] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20200213T104930/exthost55/vscode.typescript-language-features/tsserver-log-ZT2zau/tsserver.log

That file contains the typescript logs.

Look through that log file for the first error or stack trace you see. If you can share the log, I can also take a look to see if anything stands out

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

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


Add pre tag and remove all attributes from the main element to remove aria-hidden tagging

This should fix issue #422.

Verified in prod that this works :)

Awesomely our prerendered sharing page even renders in links text-mode browser now...so search engines should give us more love too


v5.0.0 is incompatible with ts-node

I'm hitting a similar issue to https://github.com/TypeStrong/ts-node/issues/155#issuecomment-570120923 with ava and ts-node while importing this in one of the functions I'm testing.
If there's no fix feel free to close this. I figured I couldn't hurt to open and at least others will now be able to find this.
  Uncaught exception in test/app/graphql/resolvers/query/display.ts

  Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /Users/xo/code/unraid/api/node_modules/path-type/index.js
  require() of ES modules is not supported.
  require() of /Users/xo/code/unraid/api/node_modules/path-type/index.js from /Users/xo/code/unraid/api/app/core/modules/info/get-all-devices.ts is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
  Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /Users/xo/code/unraid/api/node_modules/path-type/package.json.

  › Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from node_modules/path-type/package.json.
  › Object.<anonymous> (app/core/modules/info/get-all-devices.ts:4:4)

You have two options.
Option 1
To get it working:

Install node 14+
Then set the type field to 'module' value in your package.json.
Then go and update all your local imports throughout the sources from import ... from 'file' to import ... from 'file.js'
Yes, .js, even if it's a TypeScript file. Ludicrous? Sure, but better future always comes for a price.
Go into your tsconfig.json and set "module" to "ES2020" (or similar) and "moduleResolution" to "node".

Congratulations, now you're tsc is ready. At least it should now build the code and runs it. BUT.
Your ts-node is not going to support this shi...ft. Have a look at this thread: https://github.com/TypeStrong/ts-node/issues/1007 where people discuss how they suffer precisely with this new approach.
But roughly don't run ts-node something and don't do node --require ts-node/register something as well. Instead please do node --loader ts-node/esm something and contemplate messages like:
(node:1577583) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

Inconvenient? Maybe. But at least your know that you're on the bleeding edge of technologies and that you're making this world a better place, at least for Sindre Sorhus.
Option 2
Just don't use this. Or downgrade to the previous version, when the author didn't harm this world that much with his righteous attempts to make it "better".

Indeed, It has been months now. The world is not "better" and we're still losing hours of work time on this, without any satisfactory solution in the end. I respect and admire your work @sindresorhus , but this forced path to ESM is not cool.

https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c
And see the working config here: https://github.com/sindresorhus/is/blob/main/tsconfig.json


Define what clobber means

Some people are unclear. It should be defined or replaced with a better word throughout the spec

We could probably replace the word with replace.

Just ran into this in this part of the spec.
There, the text:

The server will clobber the following keys: creator, room_version.

... could be changed into:

The server will override the following keys: creator, room_version.

(Assuming that my understanding of the phrase is correct, and it means to say that the client-specified value will be ignored, and a server-determined value will always be used for those keys.)
I'm not sure whether this 'override' terminology will work elsewhere in the spec, or whether it needs to be clarified with clauses such as "if it is specified".
I do think that 'override' is a clearer term to use here than 'replace', as it explicitly denotes that the replacement is forcible in nature. It's also a term that is commonly understood in every-day language use; though less so than 'replace', but I'm not sure that that difference matters given the target audience.

I'm not entirely sure. overwrite is clearer than override to me, but replace sounds the simplest and clearest of the lot.
This is purely my opinion though.


[BUG] clvm instance connect gets stuck

Describe the bug
A clear and concise description of what the bug is.
when using 'clvm instance connect '
it gets stuck like in the following screenshot
It worked locally by reverting commit 5fa84e8192b66adedcd927492b1c1e496fc062ae, its most likely related
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Extra info:

OS: [e.g. Amazon Linux 2]
Affected Version

looks like other ssm related features are affected as well

@orkhanshirin please revert the changes accordingly.


Update Composer dependencies (2021-07-29-00-04)

Visual regression test passed!
View the visual regression test report


There was an unknown error when performing a doctor check.

After I installed minidcos on my most actual CentOS 7.5
(uname -a: Linux <server> 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux)
with the command for the Linux package:
sudo curl --fail -L https://github.com/dcos/dcos-e2e/releases/download/2<IP_ADDRESS>/minidcos -o /usr/local/bin/minidcos && sudo chmod +x /usr/local/bin/minidcos
I also changed the owner of the directory and the file with:
sudo chown myuser:myuser
... as I have to use sudo on my sytems to install packages.
After installation has been finished, I executed the command minidcos docker doctor -v
All checks went well until 13/13. This gave me the following error:
Note: Docker has approximately 31.5 GB of memory available. The amount of memory required depends on the workload. For example, creating large clusters or multiple clusters requires a lot of memory.
A four node cluster seems to work well on a machine with 9 GB of memory available to Docker.
12/13 checks complete:
2018-12-23 17:54:22 ERROR    dcos_e2e._common | docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
ERROR:dcos_e2e._common:docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
2018-12-23 17:54:22 ERROR    dcos_e2e._common | See 'docker run --help'.
ERROR:dcos_e2e._common:See 'docker run --help'.

Error: There was an unknown error when performing a doctor check.
The doctor function was "_check_can_mount_in_docker".
The error was: "Command '['docker', 'exec', '--user', 'root', '--interactive', '53adb21fa73f33c64b2d63ab63b28e97096a251f2c25d719cf4944b44d54979b', 'docker', 'run', '-v', '/foo', 'alpine']' returned non-zero exit status 125.".
12/13 checks complete: Exception ignored in: <bound method tqdm.__del__ of 12/13 checks complete: ▏        >
Traceback (most recent call last):
  File "site-packages/tqdm/_tqdm.py", line 931, in __del__
  File "site-packages/tqdm/_tqdm.py", line 1133, in close
  File "site-packages/tqdm/_tqdm.py", line 496, in _decr_instances
  File "site-packages/tqdm/_monitor.py", line 52, in exit
  File "threading.py", line 1053, in join

Actually the docker daemon is up and running:
$ sudo systemctl status docker
docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor prese                                                                                t: disabled)
   Active: active (running) since So 2018-12-23 17:32:45 CET; 18min ago
     Docs: https://docs.docker.com
 Main PID: 15404 (dockerd)
   CGroup: /system.slice/docker.service
           ├─15404 /usr/bin/dockerd -H unix://
           ├─15427 containerd --config /var/run/docker/containerd/containerd....
           ├─16403 containerd-shim -namespace moby -workdir /var/lib/docker/c...
           ├─24416 containerd-shim -namespace moby -workdir /var/lib/docker/c...
           ├─24515 containerd-shim -namespace moby -workdir /var/lib/docker/c...
           ├─25318 containerd-shim -namespace moby -workdir /var/lib/docker/c...
           ├─26123 containerd-shim -namespace moby -workdir /var/lib/docker/c...
           └─26898 runc --root /var/run/docker/runtime-runc/moby --log /run/d...

I tried the same with starting the docker daemon manually:
$ sudo dockerd
INFO[2018-12-23T19:16:39.403460151+01:00] parsed scheme: "unix"                         module=grpc
INFO[2018-12-23T19:16:39.404589503+01:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2018-12-23T19:16:39.404830250+01:00] parsed scheme: "unix"                         module=grpc
INFO[2018-12-23T19:16:39.404916296+01:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2018-12-23T19:16:39.405424749+01:00] ccResolverWrapper: sending new addresses to cc: [{unix:///run/containerd/containerd.sock 0  <nil>}]  module=grpc
INFO[2018-12-23T19:16:39.405605361+01:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2018-12-23T19:16:39.405818241+01:00] pickfirstBalancer: HandleSubConnStateChange: 0xc42076cad0, CONNECTING  module=grpc
INFO[2018-12-23T19:16:39.407404153+01:00] ccResolverWrapper: sending new addresses to cc: [{unix:///run/containerd/containerd.sock 0  <nil>}]  module=grpc
INFO[2018-12-23T19:16:39.410009554+01:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2018-12-23T19:16:39.410287038+01:00] pickfirstBalancer: HandleSubConnStateChange: 0xc420886190, CONNECTING  module=grpc
INFO[2018-12-23T19:16:39.408256998+01:00] pickfirstBalancer: HandleSubConnStateChange: 0xc42076cad0, READY  module=grpc
INFO[2018-12-23T19:16:39.411416250+01:00] pickfirstBalancer: HandleSubConnStateChange: 0xc420886190, READY  module=grpc
INFO[2018-12-23T19:16:39.462749589+01:00] [graphdriver] using prior storage driver: overlay2
INFO[2018-12-23T19:16:39.545900130+01:00] Graph migration to content-addressability took 0.00 seconds
INFO[2018-12-23T19:16:39.549423401+01:00] Loading containers: start.
INFO[2018-12-23T19:16:41.842242207+01:00] Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address
INFO[2018-12-23T19:16:42.713012048+01:00] Loading containers: done.
INFO[2018-12-23T19:16:42.831660976+01:00] Docker daemon                                 commit=4d60db4 graphdriver(s)=overlay2 version=18.09.0
INFO[2018-12-23T19:16:42.832064665+01:00] Daemon has completed initialization
INFO[2018-12-23T19:16:42.886521566+01:00] API listen on /var/run/docker.sock

Then I retried:
$ pwd
/usr/local/bin
[myuser@server bin]$ ./minidcos docker doctor

on "dockerd" terminal it said:
INFO[2018-12-23T19:17:47.437329516+01:00] Container 6faf2e38300319c5fe2c18ef8758d771ad496ac1930e96fbaa32870894bfadf0 failed to exit within 10 seconds of signal 15 - using the force
INFO[2018-12-23T19:17:47.899840140+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:18:00.165255179+01:00] Container 6171b37f290a7265cbae3e1cf388da5aa88269b5cd8bb58df867a05f5af8203f failed to exit within 10 seconds of signal 15 - using the force
INFO[2018-12-23T19:18:00.614194441+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:18:12.738779801+01:00] Container faccf28f1779cfb1bc814dd836b58c238e44228458d6f9a40d1c746734009c2f failed to exit within 10 seconds of signal 15 - using the force
INFO[2018-12-23T19:18:13.189271409+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:18:25.333069615+01:00] Container c85462287ccb5f9063ff351d26043cd8b9c6d7037583f7c2359bfb8c76b1742a failed to exit within 10 seconds of signal 15 - using the force
INFO[2018-12-23T19:18:25.782169752+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:18:38.035307969+01:00] Container 0831d004a297ef2377b6272b199bd98114db1ee157dd98c671d153b14c93b5e9 failed to exit within 10 seconds of signal 15 - using the force
INFO[2018-12-23T19:18:38.498353545+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:19:07.051312557+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:19:08.542774254+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:19:09.774780657+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:19:36.829187350+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:19:37.939741998+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2018-12-23T19:19:39.307944482+01:00] ignoring event                                module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"

and the output in the "minidcos" terminal still was:
Note: Docker has approximately 31.5 GB of memory available. The amount of memory required depends on the workload.  memory.
A four node cluster seems to work well on a machine with 9 GB of memory available to Docker.
12/13 checks complete:
2018-12-23 19:19:36 ERROR    dcos_e2e._common | docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
ERROR:dcos_e2e._common:docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
2018-12-23 19:19:36 ERROR    dcos_e2e._common | See 'docker run --help'.
ERROR:dcos_e2e._common:See 'docker run --help'.

Error: There was an unknown error when performing a doctor check.
The doctor function was "_check_can_mount_in_docker".
The error was: "Command '['docker', 'exec', '--user', 'root', '--interactive', '20425e8f106830d9b7b4157b434fe698af42ac67a9f7a6d95a704fb924a71fe5', 'docker', 'run', '-v', '/foo', 'alpine']' returned non-zero exit status 125.".
12/13 checks complete:  Exception ignored in: <bound method tqdm.__del__ of 12/13 checks complete: >
Traceback (most recent call last):
  File "site-packages/tqdm/_tqdm.py", line 931, in __del__
  File "site-packages/tqdm/_tqdm.py", line 1133, in close
  File "site-packages/tqdm/_tqdm.py", line 496, in _decr_instances
  File "site-packages/tqdm/_monitor.py", line 52, in exit
  File "threading.py", line 1053, in join

But a:
$ ls -l /var/run/docker.sock
srw-rw----. 1 root docker 0 23. Dez 19:16 /var/run/docker.sock

seems to proof, that the docker socket is available.
The current user is member of the usergroup "docker" I can execute any docker command without "sudo" upfront.
I tried the same commands while being root, but nothing changed.
P.S.:
$ docker version
Client:
 Version:           18.09.0
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        4d60db4
 Built:             Wed Nov  7 00:48:22 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.0
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       4d60db4
  Built:            Wed Nov  7 00:19:08 2018
  OS/Arch:          linux/amd64
  Experimental:     false

@Spirit328 @anuradhai4i  - Does docker ps work - I assume not but I assume sudo docker ps might! If you let me know, I can make progress with this.

I cannot get miniDC/OS release 2<IP_ADDRESS> to work on CentOS 7 in Docker. However, I can successfully create a cluster with release 2<IP_ADDRESS>, CentOS Linux release 7.6.1810, Docker version 18.09.6. However, I do need to specify the Docker version, and minidcos docker doctor still fails.
To create the cluster:
$ minidcos docker create --variant oss --agents 1 --cluster-id default --docker-version 17.12.1-ce dcos_generate_config.sh
$ minidcos docker wait --cluster-id default

Thanks all for your contributions to this thread.
It is interesting and it includes multiple issues:

Ugly traceback in an error message

Traceback (most recent call last):
  File "site-packages/tqdm/_tqdm.py", line 931, in __del__
  File "site-packages/tqdm/_tqdm.py", line 1133, in close
  File "site-packages/tqdm/_tqdm.py", line 496, in _decr_instances
  File "site-packages/tqdm/_monitor.py", line 52, in exit
  File "threading.py", line 1053, in join

This traceback should no longer be shown, since an update to tqdm a while back.

What the error means

2018-12-23 19:19:36 ERROR    dcos_e2e._common | docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
ERROR:dcos_e2e._common:docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
2018-12-23 19:19:36 ERROR    dcos_e2e._common | See 'docker run --help'.
ERROR:dcos_e2e._common:See 'docker run --help'.

While folks here have been inspecting their local Docker instances, the error refers to Docker on the minidcos nodes (Docker in Docker).

The requirement to specify --docker-version

In #1574 (released in 2<IP_ADDRESS>), I made the change "Changed the default version of Docker installed on minidcos docker clusters to 18.06.3-ce.".
This should mean that folks no longer have to specify --docker-version by default in the newest minidcos.

Next steps

What seems clear is that using Docker version 1.13.1 on nodes is problematic on some machines.
The main pain should be taken away with the update to make 18.06.3-ce the default version.
However, the doctor command will still fail.
Ideally we can narrow down exactly what the problem is, and make that clear in the doctor error.
An intermediate step might look for the given error and just move on with a warning, potentially one which links to this issue.


[Blazor] JS Interop - excessive ')' character

cc @guardrex

Internal previews

📄 File
🔗 Preview link

aspnetcore/blazor/javascript-interoperability/index.md
ASP.NET Core Blazor JavaScript interoperability (JS interop)

BTW @hakenr ... We have a CODEOWNERS file in place, so I should get added auto-magically ✨ as a reviewer to any Blazor doc PR ... in theory 😆. For other articles, you'd perhaps want to ping the author manually.
https://github.com/dotnet/AspNetCore.Docs/blob/main/.github/CODEOWNERS


mxbai-rerank-large-v1 starup error

System Info
infinity ver 0.0.32
python 3.10
Information

[ ] Docker
[X] The CLI directly via pip

Tasks

[ ] An officially supported command
[ ] My own modifications

Reproduction
infinity_emb --model-name-or-path /opt/works/AI/ollama/ollama/mxbai-rerank-large-v1 --host <IP_ADDRESS> --port 8090 --log-level debug
INFO     2024-05-14 11:42:24,850 datasets INFO: PyTorch version 2.2.1 available.             config.py:58
INFO:     Started server process [1184226]
INFO:     Waiting for application startup.
INFO     2024-05-14 11:42:25,632 infinity_emb INFO:                                    select_model.py:54
model=/opt/works/AI/ollama/ollama/mxbai-rerank-large-v1 selected, using
engine=torch and device=None
DEBUG    2024-05-14 11:42:25,633 infinity_emb DEBUG: model is a directory, opening     select_model.py:25
config.json
ERROR:    Traceback (most recent call last):
File "/home/fanai/.conda/envs/infinity/lib/python3.10/site-packages/starlette/routing.py", line 677, in lifespan
async with self.lifespan_context(app) as maybe_state:
File "/home/fanai/.conda/envs/infinity/lib/python3.10/contextlib.py", line 199, in aenter
return await anext(self.gen)
File "/home/fanai/.conda/envs/infinity/lib/python3.10/site-packages/infinity_emb/infinity_server.py", line 46, in lifespan
app.model = AsyncEmbeddingEngine.from_args(engine_args)  # type: ignore
File "/home/fanai/.conda/envs/infinity/lib/python3.10/site-packages/infinity_emb/engine.py", line 49, in from_args
engine = cls(**asdict(engine_args), _show_deprecation_warning=False)
File "/home/fanai/.conda/envs/infinity/lib/python3.10/site-packages/infinity_emb/engine.py", line 40, in init
self._model, self._min_inference_t, self._max_inference_t = select_model(
File "/home/fanai/.conda/envs/infinity/lib/python3.10/site-packages/infinity_emb/inference/select_model.py", line 62, in select_model
loaded_engine = unloaded_engine.value(engine_args=engine_args)
File "/home/fanai/.conda/envs/infinity/lib/python3.10/site-packages/infinity_emb/transformer/crossencoder/torch.py", line 38, in init
super().init(
File "/home/fanai/.conda/envs/infinity/lib/python3.10/site-packages/sentence_transformers/cross_encoder/CrossEncoder.py", line 81, in init
self.model = AutoModelForSequenceClassification.from_pretrained(
TypeError: transformers.models.auto.auto_factory._BaseAutoModelClass.from_pretrained() got multiple values for keyword argument 'trust_remote_code'
ERROR:    Application startup failed. Exiting.
Expected behavior
starup ok

Got it! Thats because of the sentence-transformer with breaking change in 2.6 vs 2.7. Fixed on latest master.

Should be fixed now with pip install infinity_emb[all]==0.0.33, the current sentence-transformers is pulled correctly.


[Feature Request] Option to use as launcher only once

Hello, thank you for developing such an amazing app!
I wanted to ask you if something would be possible.
I have created a Tasker profile to switch to Taskbar when a Bluetooth Keyboard and Mouse are connected, and to return to Nova when not.
However, I get stuck in a loop when enabling Taskbar, as it is asking me to select "Always use" to be able to continue, yet since I'm using AutoTools as the launcher activity, the task seems to stop working.
It would help me a lot if there was some way to disable the Always warning, or perhaps you would know of a better way to do this.
Anyway, thank you again for providing the option, I wish you a great afternoon and a nice day!

you can use cmd package set-home-activity "com.farmerbb.taskbar/.activity.HomeActivity" to set Taskbar as default launcher and cmd package set-home-activity "com.teslacoilsw.launcher/.NovaLauncher" to revert to Nova, commands need to be executed with root permissions

you can use cmd package set-home-activity "com.farmerbb.taskbar/.activity.HomeActivity" to set Taskbar as default launcher and cmd package set-home-activity "com.teslacoilsw.launcher/.NovaLauncher" to revert to Nova, commands need to be executed with root permissions