[Bug]: Can't access control-planes with proxied DNS entries from cloudflare

Description
When using cloudflare proxied DNS records, you cannot talk to K8S API, even when additional_tls_san is set correctly.
This makes it impossible to configure firewall such that only connections coming from cloudflare are allowed.
Steps to reproduce:

created a cluster with "cp.production.example.org" as additional_tls_san in kube.tf
created proxied dns entry in cloudflare that points to control-plane nodes
try to interact with k8s API  (e.g. kubectl get nodes) -> connection does not work / freeze

Kube.tf file
locals {
  # You have the choice of setting your Hetzner API token here or define the TF_VAR_hcloud_token env
  # within your shell, such as: export TF_VAR_hcloud_token=xxxxxxxxxxx
  # If you choose to define it in the shell, this can be left as is.

  # Your Hetzner token can be found in your Project > Security > API Token (Read & Write is required).
  hcloud_token = "xxxxxxxxxxx"
}

module "kube-hetzner" {
  providers = {
    hcloud = hcloud
  }
  hcloud_token = var.hcloud_token != "" ? var.hcloud_token : local.hcloud_token

  # Then fill or edit the below values. Only the first values starting with a * are obligatory; the rest can remain with their default values, or you
  # could adapt them to your needs.

  # * For local dev, path to the git repo
  # source = "../../kube-hetzner/"
  # If you want to use the latest master branch
  # source = "github.com/kube-hetzner/terraform-hcloud-kube-hetzner"
  # For normal use, this is the path to the terraform registry
  source = "kube-hetzner/kube-hetzner/hcloud"

  # You can optionally specify a version number
  # version = "1.2.0"

  # Note that some values, notably "location" and "public_key" have no effect after initializing the cluster.
  # This is to keep Terraform from re-provisioning all nodes at once, which would lose data. If you want to update
  # those, you should instead change the value here and manually re-provision each node. Grep for "lifecycle".

  # Customize the SSH port (by default 22)
  ssh_port = 21259

  # * Your ssh public key !! replace with actual ssh key
  ssh_public_key = ""
  # * Your private key must be "ssh_private_key = null" when you want to use ssh-agent for a Yubikey-like device authentication or an SSH key-pair with a passphrase.
  # For more details on SSH see https://github.com/kube-hetzner/kube-hetzner/blob/master/docs/ssh.md
  ssh_private_key = null
  # You can add additional SSH public Keys to grant other team members root access to your cluster nodes.
  # ssh_additional_public_keys = []

  # You can also add additional SSH public Keys which are saved in the hetzner cloud by a label.
  # See https://docs.hetzner.cloud/#label-selector
  # ssh_hcloud_key_label = "role=admin" !! create admin ssh key and save to vaultwarden

  # If you use SSH agent and have issues with SSH connecting to your nodes, you can increase the number of auth tries (default is 2)
  ssh_max_auth_tries = 4 # increased due to multiple loaded ssh keys in agent

  # If you want to use an ssh key that is already registered within hetzner cloud, you can pass its id.
  # If no id is passed, a new ssh key will be registered within hetzner cloud.
  # It is important that exactly this key is passed via `ssh_public_key` & `ssh_private_key` variables.
  # hcloud_ssh_key_id = ""

  # These can be customized, or left with the default values
  # * For Hetzner locations see https://docs.hetzner.com/general/others/data-centers-and-connection/
  network_region = "eu-central" # change to `us-east` if location is ash

  # If you want to create the private network before calling this module,
  # you can do so and pass its id here. For example if you want to use a proxy
  # which only listens on your private network. Advanced use case.
  #
  # NOTE1: make sure to adapt network_ipv4_cidr, cluster_ipv4_cidr, and service_ipv4_cidr accordingly.
  #        If your network is created with <IP_ADDRESS>/8, and you use subnet <IP_ADDRESS>/9 for your
  #        non-k3s business, then adapting `network_ipv4_cidr = "<IP_ADDRESS>/9"` should be all you need.
  #
  # NOTE2: square brackets! This must be a list of length 1.
  #
  # existing_network_id = [hcloud_network.your_network.id]

  # If you must change the network CIDR you can do so below, but it is highly advised against.
  # network_ipv4_cidr = "<IP_ADDRESS>/8"

  # Using the default configuration you can only create a maximum of 42 agent-nodepools.
  # This is due to the creation of a subnet for each nodepool with CIDRs being in the shape of 10.[nodepool-index].0.0/16 which collides with k3s' cluster and service IP ranges (defaults below).
  # Furthermore the maximum number of nodepools (controlplane and agent) is 50, due to a hard limit of 50 subnets per network, see https://docs.hetzner.com/cloud/networks/faq/.
  # So to be able to create a maximum of 50 nodepools in total, the values below have to be changed to something outside that range, e.g. `<IP_ADDRESS>/16` and `<IP_ADDRESS>/16` for cluster and service respectively.

  # If you must change the cluster CIDR you can do so below, but it is highly advised against.
  # Never change this value after you already initialized a cluster. Complete cluster redeploy needed!
  # The cluster CIDR must be a part of the network CIDR!
  # cluster_ipv4_cidr = "<IP_ADDRESS>/16"

  # If you must change the service CIDR you can do so below, but it is highly advised against.
  # Never change this value after you already initialized a cluster. Complete cluster redeploy needed!
  # The service CIDR must be a part of the network CIDR!
  # service_ipv4_cidr = "<IP_ADDRESS>/16"

  # If you must change the service IPv4 address of core-dns you can do so below, but it is highly advisd against.
  # Never change this value after you already initialized a cluster. Complete cluster redeploy needed!
  # The service IPv4 address must be part of the service CIDR!
  # cluster_dns_ipv4 = "<IP_ADDRESS>"

  # For the control planes, at least three nodes are the minimum for HA. Otherwise, you need to turn off the automatic upgrades (see README).
  # **It must always be an ODD number, never even!** Search the internet for "split-brain problem with etcd" or see https://rancher.com/docs/k3s/latest/en/installation/ha-embedded/
  # For instance, one is ok (non-HA), two is not ok, and three is ok (becomes HA). It does not matter if they are in the same nodepool or not! So they can be in different locations and of various types.

  # Of course, you can choose any number of nodepools you want, with the location you want. The only constraint on the location is that you need to stay in the same network region, Europe, or the US.
  # For the server type, the minimum instance supported is cpx11 (just a few cents more than cx11) but the cax11 is even cheaper and more powerful (arm64); see https://www.hetzner.com/cloud.

  # IMPORTANT: Before you create your cluster, you can do anything you want with the nodepools, but you need at least one of each, control plane and agent.
  # Once the cluster is up and running, you can change nodepool count and even set it to 0 (in the case of the first control-plane nodepool, the minimum is 1).
  # You can also rename it (if the count is 0), but do not remove a nodepool from the list.

  # You can safely add or remove nodepools at the end of each list. That is due to how subnets and IPs get allocated (FILO).
  # The maximum number of nodepools you can create combined for both lists is 50 (see above).
  # Also, before decreasing the count of any nodepools to 0, it's essential to drain and cordon the nodes in question. Otherwise, it will leave your cluster in a bad state.

  # Before initializing the cluster, you can change all parameters and add or remove any nodepools. You need at least one nodepool of each kind, control plane, and agent.
  # ⚠ The nodepool names are entirely arbitrary, but all lowercase, no special characters or underscore (dashes are allowed), and they must be unique.

  # If you want to have a single node cluster, have one control plane nodepools with a count of 1, and one agent nodepool with a count of 0.

  # Please note that changing labels and taints after the first run will have no effect. If needed, you can do that through Kubernetes directly.

  # Multi-architecture clusters are OK for most use cases, as container underlying images tend to be multi-architecture too.

  # * Example below:

  control_plane_nodepools = [
    {
      name        = "control-plane-fsn1",
      server_type = "cax21",
      location    = "fsn1",
      labels      = [],
      taints      = [],
      count       = 3
      # swap_size   = "2G" # remember to add the suffix, examples: 512M, 1G
      # zram_size   = "2G" # remember to add the suffix, examples: 512M, 1G
      # kubelet_args = ["kube-reserved=cpu=250m,memory=1500Mi,ephemeral-storage=1Gi", "system-reserved=cpu=250m,memory=300Mi"]

      # Fine-grained control over placement groups (nodes in the same group are spread over different physical servers, 10 nodes per placement group max):
      # placement_group = "default"

      # Enable automatic backups via Hetzner (default: false)
      # backups = true
    },
    # {
    #   name        = "control-plane-nbg1",
    #   server_type = "cpx11",
    #   location    = "nbg1",
    #   labels      = [],
    #   taints      = [],
    #   count       = 1

    #   # Fine-grained control over placement groups (nodes in the same group are spread over different physical servers, 10 nodes per placement group max):
    #   # placement_group = "default"

    #   # Enable automatic backups via Hetzner (default: false)
    #   # backups = true
    # },
    # {
    #   name        = "control-plane-hel1",
    #   server_type = "cpx11",
    #   location    = "hel1",
    #   labels      = [],
    #   taints      = [],
    #   count       = 1

    #   # Fine-grained control over placement groups (nodes in the same group are spread over different physical servers, 10 nodes per placement group max):
    #   # placement_group = "default"

    #   # Enable automatic backups via Hetzner (default: false)
    #   # backups = true
    # }
  ]

  agent_nodepools = [
    {
      name        = "system",
      server_type = "cax21",
      location    = "fsn1",
      labels = [
        "nodepool=system"
      ],
      taints = [],
      count  = 3
      # swap_size   = "2G" # remember to add the suffix, examples: 512M, 1G
      # zram_size   = "2G" # remember to add the suffix, examples: 512M, 1G
      # kubelet_args = ["kube-reserved=cpu=50m,memory=300Mi,ephemeral-storage=1Gi", "system-reserved=cpu=250m,memory=300Mi"]

      # Fine-grained control over placement groups (nodes in the same group are spread over different physical servers, 10 nodes per placement group max):
      # placement_group = "default"

      # Enable automatic backups via Hetzner (default: false)
      # backups = true
    }
  ]
  # Add custom control plane configuration options here.
  # E.g to enable monitoring for etcd, proxy etc:
  # control_planes_custom_config = {
  #   etcd-expose-metrics         = true,
  #   kube-controller-manager-arg = "bind-address=<IP_ADDRESS>",
  #   kube-proxy-arg              = "metrics-bind-address=<IP_ADDRESS>",
  #   kube-scheduler-arg          = "bind-address=<IP_ADDRESS>",
  # }

  # You can enable encrypted wireguard for the CNI by setting this to "true". Default is "false".
  # FYI, Hetzner says "Traffic between cloud servers inside a Network is private and isolated, but not automatically encrypted."
  # Source: https://docs.hetzner.com/cloud/networks/faq/#is-traffic-inside-hetzner-cloud-networks-encrypted
  # It works with all CNIs that we support.
  # Just note, that if Cilium with cilium_values, the responsibility of enabling of disabling Wireguard falls on you.
  # enable_wireguard = true

  # * LB location and type, the latter will depend on how much load you want it to handle, see https://www.hetzner.com/cloud/load-balancer
  load_balancer_type     = "lb11"
  load_balancer_location = "fsn1"

  # Disable IPv6 for the load balancer, the default is false.
  load_balancer_disable_ipv6 = true

  # Disables the public network of the load balancer. (default: false).
  # load_balancer_disable_public_network = true

  # Specifies the algorithm type of the load balancer. (default: round_robin).
  # load_balancer_algorithm_type = "least_connections"

  # Specifies the interval at which a health check is performed. Minimum is 3s (default: 15s).
  # load_balancer_health_check_interval = "5s"

  # Specifies the timeout of a single health check. Must not be greater than the health check interval. Minimum is 1s (default: 10s).
  # load_balancer_health_check_timeout = "3s"

  # Specifies the number of times a health check is retried before a target is marked as unhealthy. (default: 3)
  # load_balancer_health_check_retries = 3

  ### The following values are entirely optional (and can be removed from this if unused)

  # You can refine a base domain name to be use in this form of nodename.base_domain for setting the reserve dns inside Hetzner
  # base_domain = "mycluster.example.com"

  # Cluster Autoscaler
  # Providing at least one map for the array enables the cluster autoscaler feature, default is disabled
  # By default we set a compatible version with the default initial_k3s_channel, to set another one,
  # have a look at the tag value in https://github.com/kubernetes/autoscaler/blob/master/charts/cluster-autoscaler/values.yaml
  # ⚠ Based on how the autoscaler works with this project, you can only choose either x86 instances or ARM server types for ALL autoscaler nodepools.
  # If you are curious, it's ok to have a multi-architecture cluster, as most underlying container images are multi-architecture too.
  #
  # ⚠ Setting labels and taints will only work on cluster-autoscaler images versions released after > 20 October 2023. Or images built from master after that date.
  #
  # * Example below:
  autoscaler_nodepools = [
    {
      name        = "autoscaled-agents"
      server_type = "cax21"
      location    = "fsn1"
      min_nodes   = 0
      max_nodes   = 5
      labels = {
        "node.kubernetes.io/role" : "peak-workloads"
      }
      taints = [{
        key : "node.kubernetes.io/role"
        value : "peak-workloads"
        effect : "NoExecute"
      }]
    }
  ]

  # ⚠ Deprecated, will be removed after a new Cluster Autoscaler version has been released which support the new way of setting labels and taints. See above.
  # Add extra labels on nodes started by the Cluster Autoscaler
  # This argument is not used if autoscaler_nodepools is not set, because the Cluster Autoscaler is installed only if autoscaler_nodepools is set
  # autoscaler_labels = [
  #   "node.kubernetes.io/role=peak-workloads"
  # ]

  # Add extra taints on nodes started by the Cluster Autoscaler
  # This argument is not used if autoscaler_nodepools is not set, because the Cluster Autoscaler is installed only if autoscaler_nodepools is set
  # autoscaler_taints = [
  #   "node.kubernetes.io/role=specific-workloads:NoExecute"
  # ]

  # Configuration of the Cluster Autoscaler binary
  #
  # These arguments and variables are not used if autoscaler_nodepools is not set, because the Cluster Autoscaler is installed only if autoscaler_nodepools is set.
  #
  # Image and version of Kubernetes Cluster Autoscaler for Hetzner Cloud:
  #   - cluster_autoscaler_image: Image of Kubernetes Cluster Autoscaler for Hetzner Cloud to be used.
  #   - cluster_autoscaler_version: Version of Kubernetes Cluster Autoscaler for Hetzner Cloud. Should be aligned with Kubernetes version.
  #
  # Logging related arguments are managed using separate variables:
  #   - cluster_autoscaler_log_level: Controls the verbosity of logs (--v), the value is from 0 to 5, default is 4, for max debug info set it to 5.
  #   - cluster_autoscaler_log_to_stderr: Determines whether to log to stderr (--logtostderr).
  #   - cluster_autoscaler_stderr_threshold: Sets the threshold for logs that go to stderr (--stderrthreshold).
  #
  # Example:
  #
  # cluster_autoscaler_image = "registry.k8s.io/autoscaling/cluster-autoscaler"
  # cluster_autoscaler_version = "v1.27.3"
  # cluster_autoscaler_log_level = 4
  # cluster_autoscaler_log_to_stderr = true
  # cluster_autoscaler_stderr_threshold = "INFO"

  # Additional Cluster Autoscaler binary configuration
  #
  # cluster_autoscaler_extra_args can be used for additional arguments. The default is an empty array.
  #
  # Please note that following arguments are managed by terraform-hcloud-kube-hetzner or the variables above and should not be set manually:
  #   - --v=${var.cluster_autoscaler_log_level}
  #   - --logtostderr=${var.cluster_autoscaler_log_to_stderr}
  #   - --stderrthreshold=${var.cluster_autoscaler_stderr_threshold}
  #   - --cloud-provider=hetzner
  #   - --nodes ...
  #
  # See the Cluster Autoscaler FAQ for the full list of arguments: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-the-parameters-to-ca
  #
  # Example:
  #
  # cluster_autoscaler_extra_args = [
  #   "--ignore-daemonsets-utilization=true",
  #   "--enforce-node-group-min-size=true",
  # ]

  # Enable etcd snapshot backups to S3 storage.
  # Just provide a map with the needed settings (according to your S3 storage provider) and backups to S3 will
  # be enabled (with the default settings for etcd snapshots).
  # Cloudflare's R2 offers 10GB, 10 million reads and 1 million writes per month for free.
  # For proper context, have a look at https://docs.k3s.io/datastore/backup-restore.
  # etcd_s3_backup = { !! needs to be configured - ask kai for payment methods
  #   etcd-s3-endpoint        = "xxxx.r2.cloudflarestorage.com"
  #   etcd-s3-access-key      = "<access-key>"
  #   etcd-s3-secret-key      = "<secret-key>"
  #   etcd-s3-bucket          = "k3s-etcd-snapshots"
  # }

  # To enable Hetzner Storage Box support, you can enable csi-driver-smb, default is "false".
  # enable_csi_driver_smb = true

  # To enable iscid without setting enable_longhorn = true, set enable_iscsid = true. You will need this if
  # you install your own version of longhorn outside of this module.
  # Default is false. If enable_longhorn=true, this variable is ignored and iscsid is enabled anyway.
  # enable_iscsid = true

  # To use local storage on the nodes, you can enable Longhorn, default is "false".
  # See a full recap on how to configure agent nodepools for longhorn here https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/discussions/373#discussioncomment-3983159
  # Also see Longhorn best practices here https://gist.github.com/ifeulner/d311b2868f6c00e649f33a72166c2e5b
  # enable_longhorn = true

  # By default, longhorn is pulled from https://charts.longhorn.io.
  # If you need a version of longhorn which assures compatibility with rancher you can set this variable to https://charts.rancher.io.
  # longhorn_repository = "https://charts.rancher.io"

  # The namespace for longhorn deployment, default is "longhorn-system".
  # longhorn_namespace = "longhorn-system"

  # The file system type for Longhorn, if enabled (ext4 is the default, otherwise you can choose xfs).
  # longhorn_fstype = "xfs"

  # how many replica volumes should longhorn create (default is 3).
  # longhorn_replica_count = 1

  # When you enable Longhorn, you can go with the default settings and just modify the above two variables OR you can add a longhorn_values variable
  # with all needed helm values, see towards the end of the file in the advanced section.
  # If that file is present, the system will use it during the deploy, if not it will use the default values with the two variable above that can be customized.
  # After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.

  # Also, you can choose to use a Hetzner volume with Longhorn. By default, it will use the nodes own storage space, but if you add an attribute of
  # longhorn_volume_size (⚠ not a variable, just a possible agent nodepool attribute) with a value between 10 and 10000 GB to your agent nodepool definition, it will create and use the volume in question.
  # See the agent nodepool section for an example of how to do that.

  # To disable Hetzner CSI storage, you can set the following to "true", default is "false".
  # disable_hetzner_csi = true

  # If you want to use a specific Hetzner CCM and CSI version, set them below; otherwise, leave them as-is for the latest versions.
  # hetzner_ccm_version = ""
  # hetzner_csi_version = ""

  # If you want to specify the Kured version, set it below - otherwise it'll use the latest version available.
  # kured_version = ""

  # If you want to enable the Nginx ingress controller (https://kubernetes.github.io/ingress-nginx/) instead of Traefik, you can set this to "nginx". Default is "traefik".
  # By the default we load optimal Traefik and Nginx ingress controller config for Hetzner, however you may need to tweak it to your needs, so to do,
  # we allow you to add a traefik_values and nginx_values, see towards the end of this file in the advanced section.
  # After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.
  # If you want to disable both controllers set this to "none"
  ingress_controller = "none" # we manage traefik ourselves via argocd
  # Namespace in which to deploy the ingress controllers. Defaults to the ingress_controller variable, eg (nginx, traefik)
  # ingress_target_namespace = ""

  # You can change the number of replicas for selected ingress controller here. The default 0 means autoselecting based on number of agent nodes (1 node = 1 replica, 2 nodes = 2 replicas, 3+ nodes = 3 replicas)
  # ingress_replica_count = 1

  # Use the klipperLB (similar to metalLB), instead of the default Hetzner one, that has an advantage of dropping the cost of the setup.
  # Automatically "true" in the case of single node cluster (as it does not make sense to use the Hetzner LB in that situation).
  # It can work with any ingress controller that you choose to deploy.
  # Please note that because the klipperLB points to all nodes, we automatically allow scheduling on the control plane when it is active.
  # enable_klipper_metal_lb = "true"

  # If you want to configure additional arguments for traefik, enter them here as a list and in the form of traefik CLI arguments; see https://doc.traefik.io/traefik/reference/static-configuration/cli/
  # They are the options that go into the additionalArguments section of the Traefik helm values file.
  # We already add "providers.kubernetesingress.ingressendpoint.publishedservice" by default so that Traefik works automatically with services such as External-DNS and ArgoCD.
  # Example:
  # traefik_additional_options = ["--log.level=DEBUG", "--tracing=true"]

  # By default traefik image tag is an empty string which uses latest image tag.
  # The default is "".
  # traefik_image_tag = "v3.0.0-beta5"

  # By default traefik is configured to redirect http traffic to https, you can set this to "false" to disable the redirection.
  # The default is true.
  # traefik_redirect_to_https = false

  # Enable or disable Horizontal Pod Autoscaler for traefik.
  # The default is true.
  # traefik_autoscaling = false

  # Enable or disable pod disruption budget for traefik. Values are maxUnavailable: 33% and minAvailable: 1.
  # The default is true.
  # traefik_pod_disruption_budget = false

  # Enable or disable default resource requests and limits for traefik. Values requested are 100m & 50Mi and limits 300m & 150Mi.
  # The default is true.
  # traefik_resource_limits = false

  # If you want to configure additional ports for traefik, enter them here as a list of objects with name, port, and exposedPort properties.
  # Example:
  # traefik_additional_ports = [{name = "example", port = 1234, exposedPort = 1234}]

  # If you want to configure additional trusted IPs for traefik, enter them here as a list of IPs (strings).
  # Example for Cloudflare:
  # traefik_additional_trusted_ips = [
  #   "<IP_ADDRESS>/20",
  #   "<IP_ADDRESS>/22",
  #   "<IP_ADDRESS>/22",
  #   "<IP_ADDRESS>/22",
  #   "<IP_ADDRESS>/18",
  #   "<IP_ADDRESS>/18",
  #   "<IP_ADDRESS>/20",
  #   "<IP_ADDRESS>/20",
  #   "<IP_ADDRESS>/22",
  #   "<IP_ADDRESS>/17",
  #   "<IP_ADDRESS>/15",
  #   "<IP_ADDRESS>/13",
  #   "<IP_ADDRESS>/14",
  #   "<IP_ADDRESS>/13",
  #   "<IP_ADDRESS>/22",
  #   "2400:cb00::/32",
  #   "2606:4700::/32",
  #   "2803:f800::/32",
  #   "2405:b500::/32",
  #   "2405:8100::/32",
  #   "2a06:98c0::/29",
  #   "2c0f:f248::/32"
  # ]

  # If you want to disable the metric server set this to "false". Default is "true".
  # enable_metrics_server = false

  # If you want to enable the k3s built-in local-storage controller set this to "true". Default is "false".
  # enable_local_storage = true

  # If you want to allow non-control-plane workloads to run on the control-plane nodes, set this to "true". The default is "false".
  # True by default for single node clusters, and when enable_klipper_metal_lb is true. In those cases, the value below will be ignored.
  # allow_scheduling_on_control_plane = true

  # If you want to disable the automatic upgrade of k3s, you can set below to "false".
  # Ideally, keep it on, to always have the latest Kubernetes version, but lock the initial_k3s_channel to a kube major version,
  # of your choice, like v1.25 or v1.26. That way you get the best of both worlds without the breaking changes risk.
  # For production use, always use an HA setup with at least 3 control-plane nodes and 2 agents, and keep this on for maximum security.

  # The default is "true" (in HA setup i.e. at least 3 control plane nodes & 2 agents, just keep it enabled since it works flawlessly).
  automatically_upgrade_k3s = false

  # The default is "true" (in HA setup it works wonderfully well, with automatic roll-back to the previous snapshot in case of an issue).
  # IMPORTANT! For non-HA clusters i.e. when the number of control-plane nodes is < 3, you have to turn it off.
  # automatically_upgrade_os = false

  # If you need more control over kured and the reboot behaviour, you can pass additional options to kured.
  # For example limiting reboots to certain timeframes. For all options see: https://kured.dev/docs/configuration/
  # By default, the kured lock does not expire and is only released once a node successfully reboots. You can add the option
  # "lock-ttl" : "30m", if you have a single node which sometimes gets stuck. Note however, that in that case, kured continuous
  # draining the next node because the lock was released. You may end up with all nodes drained and your cluster completely down.
  # The default options are: `--reboot-command=/usr/bin/systemctl reboot --pre-reboot-node-labels=kured=rebooting --post-reboot-node-labels=kured=done --period=5m`
  # Defaults can be overridden by using the same key.
  kured_options = { # update only saturday night so we have still sunday to fix everything in case things go wrong
    "reboot-days" : "sa",
    "start-time" : "1am",
    "end-time" : "5am",
    "time-zone" : "Local",
    "lock-ttl" : "30m",
  }

  # Allows you to specify either stable, latest, testing or supported minor versions.
  # see https://rancher.com/docs/k3s/latest/en/upgrades/basic/ and https://update.k3s.io/v1-release/channels
  # ⚠ If you are going to use Rancher addons for instance, it's always a good idea to fix the kube version to latest - 0.01,
  # ⚠ Rancher currently only supports v1.25 and earlier versions: https://github.com/rancher/rancher/issues/41113
  # The default is "v1.29".
  # initial_k3s_channel = "stable"

  # The cluster name, by default "k3s"
  cluster_name = "production"

  # Whether to use the cluster name in the node name, in the form of {cluster_name}-{nodepool_name}, the default is "true".
  # use_cluster_name_in_node_name = false

  # Extra k3s registries. This is useful if you have private registries and you want to pull images without additional secrets.
  # Or if you want to proxy registries for various reasons like rate-limiting.
  # It will create the registries.yaml file, more info here https://docs.k3s.io/installation/private-registry.
  # Note that you do not need to get this right from the first time, you can update it when you want during the life of your cluster.
  # The default is blank.
  /* k3s_registries = <<-EOT
    mirrors:
      hub.my_registry.com:
        endpoint:
          - "hub.my_registry.com"
    configs:
      hub.my_registry.com:
        auth:
          username: username
          password: password
  EOT */

  # Additional environment variables for the host OS on which k3s runs. See for example https://docs.k3s.io/advanced#configuring-an-http-proxy .
  # additional_k3s_environment = {
  #   "CONTAINERD_HTTP_PROXY" : "http://your.proxy:port",
  #   "CONTAINERD_HTTPS_PROXY" : "http://your.proxy:port",
  #   "NO_PROXY" : "<IP_ADDRESS>/8,<IP_ADDRESS>/8,",
  # }

  # Additional commands to execute on the host OS before the k3s install, for example fetching and installing certs.
  # preinstall_exec = [
  #   "curl https://somewhere.over.the.rainbow/ca.crt > /root/ca.crt",
  #   "trust anchor --store /root/ca.crt",
  # ]

  # Additional flags to pass to the k3s server command (the control plane).
  # k3s_exec_server_args = "--kube-apiserver-arg enable-admission-plugins=PodTolerationRestriction,PodNodeSelector"

  # Additional flags to pass to the k3s agent command (every agents nodes, including autoscaler nodepools).
  # k3s_exec_agent_args = "--kubelet-arg kube-reserved=cpu=100m,memory=200Mi,ephemeral-storage=1Gi"

  # The vars below here passes it to the k3s config.yaml. This way it persist across reboots
  # k3s_global_kubelet_args = ["kube-reserved=cpu=100m,ephemeral-storage=1Gi", "system-reserved=cpu=memory=200Mi", "image-gc-high-threshold=50", "image-gc-low-threshold=40"]
  # k3s_control_plane_kubelet_args = []
  # k3s_agent_kubelet_args = []

  # If you want to allow all outbound traffic you can set this to "false". Default is "true".
  # restrict_outbound_traffic = false

  # Allow access to the Kube API from the specified networks. The default is ["<IP_ADDRESS>/0", "::/0"].
  # Allowed values: null (disable Kube API rule entirely) or a list of allowed networks with CIDR notation.
  # For maximum security, it's best to disable it completely by setting it to null. However, in that case, to get access to the kube api,
  # you would have to connect to any control plane node via SSH, as you can run kubectl from within these.
  # Please be advised that this setting has no effect on the load balancer when the use_control_plane_lb variable is set to true. This is
  # because firewall rules cannot be applied to load balancers yet.
  # firewall_kube_api_source = null

  # Allow SSH access from the specified networks. Default: ["<IP_ADDRESS>/0", "::/0"]
  # Allowed values: null (disable SSH rule entirely) or a list of allowed networks with CIDR notation.
  # Ideally you would set your IP there. And if it changes after cluster deploy, you can always update this variable and apply again.
  # firewall_ssh_source = ["<IP_ADDRESS>/32"]

  # Adding extra firewall rules, like opening a port
  # More info on the format here https://registry.terraform.io/providers/hetznercloud/hcloud/latest/docs/resources/firewall
  extra_firewall_rules = [
    {
      description     = "For Redis"
      direction       = "in"
      protocol        = "tcp"
      port            = "6379"
      source_ips      = ["<IP_ADDRESS>/0", "::/0"]
      destination_ips = [] # Won't be used for this rule
    },
    {
      description     = "To Allow ArgoCD access to resources via SSH"
      direction       = "out"
      protocol        = "tcp"
      port            = "22"
      source_ips      = [] # Won't be used for this rule
      destination_ips = ["<IP_ADDRESS>/0", "::/0"]
    },
    {
      description     = "For Denkcluster access"
      direction       = "out"
      protocol        = "tcp"
      port            = "6443"
      source_ips      = [] # Won't be used for this rule
      destination_ips = ["<IP_ADDRESS>/0", "::/0"]
    }
  ]

  # If you want to configure a different CNI for k3s, use this flag
  # possible values: flannel (Default), calico, and cilium
  # As for Cilium, we allow infinite configurations via helm values, please check the CNI section of the readme over at https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/#cni.
  # Also, see the cilium_values at towards the end of this file, in the advanced section.
  # ⚠ Depending on your setup, sometimes you need your control-planes to have more than
  # 2GB of RAM if you are going to use Cilium, otherwise the pods will not start.
  # cni_plugin = "cilium"

  # You can choose the version of Cilium that you want. By default we keep the version up to date and configure Cilium with compatible settings according to the version.
  # cilium_version = "v1.14.0"

  # Set native-routing mode ("native") or tunneling mode ("tunnel"). Default: tunnel
  # cilium_routing_mode = "native"

  # Used when Cilium is configured in native routing mode. The CNI assumes that the underlying network stack will forward packets to this destination without the need to apply SNAT. Default: value of "cluster_ipv4_cidr"
  # cilium_ipv4_native_routing_cidr = "<IP_ADDRESS>/8"

  # Enables egress gateway to redirect and SNAT the traffic that leaves the cluster. Default: false
  # cilium_egress_gateway_enabled = true

  # You can choose the version of Calico that you want. By default, the latest is used.
  # More info on available versions can be found at https://github.com/projectcalico/calico/releases
  # Please note that if you are getting 403s from Github, it's also useful to set the version manually. However there is rarely a need for that!
  # calico_version = "v3.27.2"

  # If you want to disable the k3s kube-proxy, use this flag. The default is "false".
  # Ensure that your CNI is capable of handling all the functionalities typically covered by kube-proxy.
  # disable_kube_proxy = true

  # If you want to disable the k3s default network policy controller, use this flag!
  # Both Calico and Ciliun cni_plugin values override this value to true automatically, the default is "false".
  # disable_network_policy = true

  # If you want to disable the automatic use of placement group "spread". See https://docs.hetzner.com/cloud/placement-groups/overview/
  # We advise to not touch that setting, unless you have a specific purpose.
  # The default is "false", meaning it's enabled by default.
  # placement_group_disable = true

  # By default, we allow ICMP ping in to the nodes, to check for liveness for instance. If you do not want to allow that, you can. Just set this flag to true (false by default).
  # block_icmp_ping_in = true

  # You can enable cert-manager (installed by Helm behind the scenes) with the following flag, the default is "true".
  enable_cert_manager = false # installed by us via ArgoCD

  # IP Addresses to use for the DNS Servers, the defaults are the ones provided by Hetzner https://docs.hetzner.com/dns-console/dns/general/recursive-name-servers/.
  # The number of different DNS servers is limited to 3 by Kubernetes itself.
  # It's always a good idea to have at least 1 IPv4 and 1 IPv6 DNS server for robustness.
  dns_servers = [
    "<IP_ADDRESS>",
    "<IP_ADDRESS>",
    "2606:4700:4700::1111",
  ]

  # When this is enabled, rather than the first node, all external traffic will be routed via a control-plane loadbalancer, allowing for high availability.
  # The default is false.
  # use_control_plane_lb = true

  # When the above use_control_plane_lb is enabled, you can change the lb type for it, the default is "lb11".
  # control_plane_lb_type = "lb21"

  # When the above use_control_plane_lb is enabled, you can change to disable the public interface for control plane load balancer, the default is true.
  # control_plane_lb_enable_public_interface = false

  # Let's say you are not using the control plane LB solution above, and still want to have one hostname point to all your control-plane nodes.
  # You could create multiple A records of to let's say cp.cluster.my.org pointing to all of your control-plane nodes ips.
  # In which case, you need to define that hostname in the k3s TLS-SANs config to allow connection through it. It can be hostnames or IP addresses.
  additional_tls_sans = ["cp.production.example.org"] # !! change this to

  # lb_hostname Configuration:
  #
  # Purpose:
  # The lb_hostname setting optimizes communication between services within the Kubernetes cluster
  # when they use domain names instead of direct service names. By associating a domain name directly
  # with the Hetzner Load Balancer, this setting can help reduce potential communication delays.
  #
  # Scenario:
  # If Service B communicates with Service A using a domain (e.g., `a.mycluster.domain.com`) that points
  # to an external Load Balancer, there can be a slowdown in communication.
  #
  # Guidance:
  # - If your internal services use domain names pointing to an external LB, set lb_hostname to a domain
  #   like `mycluster.domain.com`.
  # - Create an A record pointing `mycluster.domain.com` to your LB's IP.
  # - Create a CNAME record for `a.mycluster.domain.com` (or xyz.com) pointing to `mycluster.domain.com`.
  #
  # Technical Note:
  # This setting sets the `load-balancer.hetzner.cloud/hostname` in the Hetzner LB definition, suitable for
  # both Nginx and Traefik ingress controllers.
  #
  # Recommendation:
  # This setting is optional. If services communicate using direct service names, you can leave this unset.
  # For inter-namespace communication, use `.service_name` as per Kubernetes norms.
  #
  # Example:
  lb_hostname = "production.example.org" # !! change this to

  # You can enable Rancher (installed by Helm behind the scenes) with the following flag, the default is "false".
  # ⚠ Rancher currently only supports Kubernetes v1.25 and earlier, you will need to set initial_k3s_channel to a supported version: https://github.com/rancher/rancher/issues/41113
  # When Rancher is enabled, it automatically installs cert-manager too, and it uses rancher's own self-signed certificates.
  # See for options https://rancher.com/docs/rancher/v2.0-v2.4/en/installation/resources/advanced/helm2/helm-rancher/#choose-your-ssl-configuration
  # The easiest thing is to leave everything as is (using the default rancher self-signed certificate) and put Cloudflare in front of it.
  # As for the number of replicas, by default it is set to the number of control plane nodes.
  # You can customized all of the above by adding a rancher_values variable see at the end of this file in the advanced section.
  # After the cluster is deployed, you can always use HelmChartConfig definition to tweak the configuration.
  # IMPORTANT: Rancher's install is quite memory intensive, you will require at least 4GB if RAM, meaning cx21 server type (for your control plane).
  # ALSO, in order for Rancher to successfully deploy, you have to set the "rancher_hostname".
  # enable_rancher = true

  # If using Rancher you can set the Rancher hostname, it must be unique hostname even if you do not use it.
  # If not pointing the DNS, you can just port-forward locally via kubectl to get access to the dashboard.
  # If you already set the lb_hostname above and are using a Hetzner LB, you do not need to set this one, as it will be used by default.
  # But if you set this one explicitly, it will have preference over the lb_hostname in rancher settings.
  # rancher_hostname = "rancher.xyz.dev"

  # When Rancher is deployed, by default is uses the "latest" channel. But this can be customized.
  # The allowed values are "stable" or "latest".
  # rancher_install_channel = "stable"

  # Finally, you can specify a bootstrap-password for your rancher instance. Minimum 48 characters long!
  # If you leave empty, one will be generated for you.
  # (Can be used by another rancher2 provider to continue setup of rancher outside this module.)
  # rancher_bootstrap_password = ""

  # Separate from the above Rancher config (only use one or the other). You can import this cluster directly on an
  # an already active Rancher install. By clicking "import cluster" choosing "generic", giving it a name and pasting
  # the cluster registration url below. However, you can also ignore that and apply the url via kubectl as instructed
  # by Rancher in the wizard, and that would register your cluster too.
  # More information about the registration can be found here https://rancher.com/docs/rancher/v2.6/en/cluster-provisioning/registered-clusters/
  # rancher_registration_manifest_url = "https://rancher.xyz.dev/v3/import/xxxxxxxxxxxxxxxxxxYYYYYYYYYYYYYYYYYYYzzzzzzzzzzzzzzzzzzzzz.yaml"

  # Extra commands to be executed after the `kubectl apply -k` (useful for post-install actions, e.g. wait for CRD, apply additional manifests, etc.).
  # extra_kustomize_deployment_commands=""

  # Extra values that will be passed to the `extra-manifests/kustomization.yaml.tpl` if its present.
  # extra_kustomize_parameters={}

  # See an working example for just a manifest.yaml, a HelmChart and a HelmChartConfig examples/kustomization_user_deploy/README.md

  # It is best practice to turn this off, but for backwards compatibility it is set to "true" by default.
  # See https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/issues/349
  # When "false". The kubeconfig file can instead be created by executing: "terraform output --raw kubeconfig > cluster_kubeconfig.yaml"
  # Always be careful to not commit this file!
  create_kubeconfig = false

  # Don't create the kustomize backup. This can be helpful for automation.
  # create_kustomization = false

  # Export the values.yaml files used for the deployment of traefik, longhorn, cert-manager, etc.
  # This can be helpful to use them for later deployments like with ArgoCD.
  # The default is false.
  # export_values = true

  # MicroOS snapshot IDs to be used. Per default empty, the most recent image created using createkh will be used.
  # We recommend the default, but if you want to use specific IDs you can.
  # You can fetch the ids with the hcloud cli by running the "hcloud image list --selector 'microos-snapshot=yes'" command.
  # microos_x86_snapshot_id = "1234567"
  # microos_arm_snapshot_id = "1234567"

  ### ADVANCED - Custom helm values for packages above (search _values if you want to located where those are mentioned upper in this file)
  # ⚠ Inside the _values variable below are examples, up to you to find out the best helm values possible, we do not provide support for customized helm values.
  # Please understand that the indentation is very important, inside the EOTs, as those are proper yaml helm values.
  # We advise you to use the default values, and only change them if you know what you are doing!

  # Cilium, all Cilium helm values can be found at https://github.com/cilium/cilium/blob/master/install/kubernetes/cilium/values.yaml
  # Be careful when maintaining your own cilium_values, as the choice of available settings depends on the Cilium version used. See also the cilium_version setting to fix a specific version.
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   cilium_values = <<EOT
ipam:
  mode: kubernetes
k8s:
  requireIPv4PodCIDR: true
kubeProxyReplacement: true
routingMode: native
ipv4NativeRoutingCIDR: "<IP_ADDRESS>/8"
endpointRoutes:
  enabled: true
loadBalancer:
  acceleration: native
bpf:
  masquerade: true
encryption:
  enabled: true
  type: wireguard
MTU: 1450
  EOT */

  # Cert manager, all cert-manager helm values can be found at https://github.com/cert-manager/cert-manager/blob/master/deploy/charts/cert-manager/values.yaml
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   cert_manager_values = <<EOT
installCRDs: true
replicaCount: 3
webhook:
  replicaCount: 3
cainjector:
  replicaCount: 3
  EOT */

  # csi-driver-smb, all csi-driver-smb helm values can be found at https://github.com/kubernetes-csi/csi-driver-smb/blob/master/charts/latest/csi-driver-smb/values.yaml
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   csi_driver_smb_values = <<EOT
controller:
  name: csi-smb-controller
  replicas: 1
  runOnMaster: false
  runOnControlPlane: false
  resources:
    csiProvisioner:
      limits:
        memory: 300Mi
      requests:
        cpu: 10m
        memory: 20Mi
    livenessProbe:
      limits:
        memory: 100Mi
      requests:
        cpu: 10m
        memory: 20Mi
    smb:
      limits:
        memory: 200Mi
      requests:
        cpu: 10m
        memory: 20Mi
  EOT */

  # Longhorn, all Longhorn helm values can be found at https://github.com/longhorn/longhorn/blob/master/chart/values.yaml
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   longhorn_values = <<EOT
defaultSettings:
  defaultDataPath: /var/longhorn
persistence:
  defaultFsType: ext4
  defaultClassReplicaCount: 3
  defaultClass: true
  EOT */

  # If you want to use a specific Traefik helm chart version, set it below; otherwise, leave them as-is for the latest versions.
  # traefik_version = ""

  # Traefik, all Traefik helm values can be found at https://github.com/traefik/traefik-helm-chart/blob/master/traefik/values.yaml
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   traefik_values = <<EOT
deployment:
  replicas: 1
globalArguments: []
service:
  enabled: true
  type: LoadBalancer
  annotations:
    "load-balancer.hetzner.cloud/name": "k3s"
    "load-balancer.hetzner.cloud/use-private-ip": "true"
    "load-balancer.hetzner.cloud/disable-private-ingress": "true"
    "load-balancer.hetzner.cloud/location": "nbg1"
    "load-balancer.hetzner.cloud/type": "lb11"
    "load-balancer.hetzner.cloud/uses-proxyprotocol": "true"

ports:
  web:
    redirectTo:
      port: websecure

    proxyProtocol:
      trustedIPs:
        - <IP_ADDRESS>/32
        - <IP_ADDRESS>/8
    forwardedHeaders:
      trustedIPs:
        - <IP_ADDRESS>/32
        - <IP_ADDRESS>/8
  websecure:
    proxyProtocol:
      trustedIPs:
        - <IP_ADDRESS>/32
        - <IP_ADDRESS>/8
    forwardedHeaders:
      trustedIPs:
        - <IP_ADDRESS>/32
        - <IP_ADDRESS>/8
  EOT */

  # If you want to use a specific Nginx helm chart version, set it below; otherwise, leave them as-is for the latest versions.
  # nginx_version = ""

  # Nginx, all Nginx helm values can be found at https://github.com/kubernetes/ingress-nginx/blob/main/charts/ingress-nginx/values.yaml
  # You can also have a look at https://kubernetes.github.io/ingress-nginx/, to understand how it works, and all the options at your disposal.
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   nginx_values = <<EOT
controller:
  watchIngressWithoutClass: "true"
  kind: "DaemonSet"
  config:
    "use-forwarded-headers": "true"
    "compute-full-forwarded-for": "true"
    "use-proxy-protocol": "true"
  service:
    annotations:
      "load-balancer.hetzner.cloud/name": "k3s"
      "load-balancer.hetzner.cloud/use-private-ip": "true"
      "load-balancer.hetzner.cloud/disable-private-ingress": "true"
      "load-balancer.hetzner.cloud/location": "nbg1"
      "load-balancer.hetzner.cloud/type": "lb11"
      "load-balancer.hetzner.cloud/uses-proxyprotocol": "true"
  EOT */

  # Rancher, all Rancher helm values can be found at https://rancher.com/docs/rancher/v2.5/en/installation/install-rancher-on-k8s/chart-options/
  # The following is an example, please note that the current indentation inside the EOT is important.
  /*   rancher_values = <<EOT
ingress:
  tls:
    source: "rancher"
hostname: "rancher.example.com"
replicas: 1
bootstrapPassword: "supermario"
  EOT */

}

provider "hcloud" {
  token = var.hcloud_token != "" ? var.hcloud_token : local.hcloud_token
}

terraform {
  required_version = ">= 1.5.0"
  required_providers {
    hcloud = {
      source  = "hetznercloud/hcloud"
      version = ">= 1.43.0"
    }
  }
}

output "kubeconfig" {
  value     = module.kube-hetzner.kubeconfig
  sensitive = true
}

variable "hcloud_token" {
  sensitive = true
  default   = ""
}

Screenshots
No response
Platform
Linux

@maaft Are you sure it wasn't the dns that needed time to propagate?

@maaft If you click the orange cloud to disable proxying, does it work?
Also dig +a your-domain.com to know which ip it's returning without proxy. I fear that it could be the private ip. See #1280. If so, PR welcome, it should be one line, and will merge fast.

@mysticaltech I should've mentioned that as soon as I disable "proxy" mode at cloudflare, the connection works flawlessly. Thing is, I'd really like to use proxied DNS.
Without proxy, it returns the correct IPs.
Hm, probably proxied DNS entries use their own SSL certificate and that is what confuses kubectl since it doesn't match public key in kubeconfig?

@maaft Hmm, maybe check cloudflare's ssl settings, choose source to clouflare to not enforce ssl, because it's already encrypted. It will only enforce from your machine to cloudflare. Try that!

Moving this to a discussion because it's probably not a bug on our side. But will continue to assist the best I can.


investigate training slowdown

noticed a definite slowdown in training with >50k steps. Investigate. Probably requires #28

Big rewrite has resolved this (somehow...)


[GSSoC'23] Styling Footer Section ✔

Fixes Issue - 134

Closes #134

Changes proposed

Adding anchors tags.
Adding hovering effects.
Added responsive for the small devices too.
Added respective links.

Screenshots

@sahil-sagwekar2652 please review this pr


Request from Bayero University,Kano-Nigeria

Request for Bayero University, Kano -Nigeria.
The official website of the university is : https://www.buk.edu.ng/
The university offers three IT-related programs: Software Engineering, Computer Science, and Information Technology : https://csit.buk.edu.ng/?q=node/8
The University also offers Computer Engineering at the faculty of engineering: : https://eng.buk.edu.ng/?q=node/6
Attached is proof of email formats use by all the university. everyone in the university irrespective of staff or students use<EMAIL_ADDRESS>

@shmuhammad2004 Pull request merged. Thank you!


ProcTHOR + Objaverse

Hi authors, thanks for the awesome work! I noticed that in Objaverse paper you mentioned there are 10K homes generated with ProcTHOR populated with objects from OBJAVERSE-LVIS. I wonder if the scripts of integrating ProcTHOR and Objaverse can be provided? Or is it possible to provide the scene json/unity file?

Hi, please check our Holodeck project which can use Objaverse assets in AI2-THOR.


fix: react-shadcn-ui-pages-router remove bundled css and tailwind plugins

Change Summary
Removes the videojs css global imports from being directly bundled in the JS, as well as removing tailwind default plugins.
For the videojs css: Using next.js pages router, integrators were getting an error.
For the tailwind default plugins: Integrators were getting an error if their repo didn't use those, and they're not strictly required by the package.
Also see https://github.com/stephancill/opencast/pull/17/files#diff-dc91be4f00064ec7b4edd44ad2a0d214ae80430b14b0ce4372eb6449e92d9732
Merge Checklist

[x] PR has a changeset
[x] PR includes documentation if necessary
[x] PR updates the rich-embed examples if necessary
[ ] includes a parallel PR for Mod-starter and the gateway if necessary

This was blocking someone trying to integrate, so I bypassed the typical procedure @stephancill since it's the middle of the night for you. Still should have a retroactive review and merge any fixes as updates


Context Menu on Paths

Could you please let me know that we can use the context menu on paths?
It is working on 'map', but not ok with 'paths'. I used angular-leaflet-directive. Thanks

Yes I have used it with paths. I'm not an angular user but can't see why it would affect the use of the plugin for paths. There's a basic angular example that I included in the examples directory but that does not add menu items to any map layers. You could try creating a simple test case that doesn't use angular and if you're still seeing the problem there I can look into it for you.


Fix build?

Running cargo install rand-bytes fails like so:
$ cargo install rand-bytes
    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading rand-bytes v0.1.0
  Installing rand-bytes v0.1.0
error: failed to compile `rand-bytes v0.1.0`, intermediate artifacts can be found at `/var/folders/ff/nw88cbjx2ms_jrhxmlmm_r_c0000gn/T/cargo-install0jqqsg`

Caused by:
  no matching version `^0.7.5` found for package `ring`
location searched: registry `https://github.com/rust-lang/crates.io-index`
versions found: 0.13.2, 0.13.1, 0.13.0, ...
required by package `rand-bytes v0.1.0`

I've bumped the dependencies and released v0.2.0: https://crates.io/crates/rand-bytes/0.2.0
Can you try again please?


Remove ResizeObservation from Resize Observer sidebar

This is not part of the actual API; it's a suggested implementation detail.

Fixed in https://github.com/mdn/kumascript/pull/1223


Proposal to change class list generation in components

What do you guys think about using something like this for generating classname lists in components?
I think it's cleaner as it's more declarative and gets rid of mutation and repeatable code.
If you think it's a good idea I'd be happy to implement it in the rest of the components.

Hi @jonathanp !!
Yes, I like the proposal and we are probably moving to it soon. @nathanmarks is already using it in the cards branch I think. When it get merged we can start working on it. This afternoon I'm going to try your PR and probably merge.
Can you update it with the latest changes from master?
Thanks! :)

Np, it's updated now.
Aha, I didn't see @nathanmarks' PR before I created mine. We're using different packages for creating the class name string though, classnames vs classnames-minimal :)

@jonathanp I need classnames as I use classnames/bind. Can we stick with the proper repo instead of your fork?

@nathanmarks: with ES6's computed property names syntax you really don't need the bind function though. You can write it with classnames-minimal easily like this...
import classNames from 'classnames-minimal';
import styles from './style.css';

const classes = classNames({
  [styles.root]: true,
  [styles.disabled]: this.props.disabled,
  [styles.highlighted]: this.props.highlighted
});

console.log(classes); // => contains the class names generated by CSS modules and filtered by our predicates

Sure, you can use the classname package in the same way but if you only need a small subset of the API I think the 5 LOC version should be preferred over the 173 LOC one.

@jonathanp
Nice tip about the computed property names. I just took another look though and there's a couple of other nice features from classnames missing, including the ability to pass in any number of arguments which is a commonly used feature.
Most people are used to using the API of https://github.com/JedWatson/classnames and you can still do what you want to do with it. 173 LOC is really not a big deal...

@jonathanp
Big issue I just encountered while testing it -- this restricts what users can pass into the components via the className attribute. I just tried swapping this into my own app on a couple of components and had issues with passing through the className which may not be an object.

@nathanmarks: That shouldn't be a problem. Since this.props.className is a string the class name passed down as a prop will be included in the generated string because of this line.
I don't see any situation where this API won't be sufficient if you have access to ES2015 syntax.

@jonathanp If you are intent on pushing this new implementation, can you at least add the ability to pass in N arguments?
This isn't about your API not working, it's about familiarity with an existing API from the go-to for this functionality in terms of 3rd party packages (500k NPM downloads in the last month).

@nathanmarks If you could provide a valid reason for extending the API I would be happy to consider it, but I've been trying to demonstrate with my code examples that there really isn't any reason why this is needed. That's the whole point of the classname-minimal package, to be a more slim version of classname.
@javivelasco what's your take on this?

@jonathanp It's not a big deal, I prefer to stick to a familiar API -- and I think we tend to have different styles of using the original package. Here's a snippet from my code:
const {
  accent,
  children,
  className,
  icon,
  primary,
  image,
  ...otherProps
} = this.props;

const classes = classNames('avatar', { accent, primary }, className);

// My use explained
// classNames(class, { optional classes }, user classes)

I just find it easier to identify what's what at a glance. As far as I know though I could be misusing it!

@jonathanp I think both options have pros and cons -- i'm not that fussed and it's not my decision anyways :)

I like both approaches but I would go for the most used implementation since it would be easier for contributors to add new code and debug errors. @jonathanp I understand your implementation and why did you did it, but I'd like to stick to the most used option. Having a bigger set of features is not a big deal in this scenario IMHO even though they're not all used.
Let's move the current implementation and see how it looks like, we are always free to change again :)

I understand, np :) I've updated the PR to use the classnames package!

Merged!
FYI, as soon as @nathanmarks finishes the PR for the new Card component we are going to migrate all className definitions to use classnames package in a new branch. @jonathanp feel free to give feedback about the final approach we're gonna take!
Thanks! :)


Fixes for writing xml

Issue #6:
Switched from writing XML manually for nodes/edges to creating them with appropiate methods. This will fix problems associated with special characters (<>'"&).
Not tested on subgraphs
Fixed bug for edge attributes as well (issue #2)

@sveinp Thaks for this PR. We should make such changes in source files and generate the browserified cytoscape-graphml.js file by running 'gulp build' command. Please would you help me to reproduce the initial problem? How did you find out the not properly encoded characters? How did you encounter the problem? (Were you not able to use the generated xml in somewhere and you are able to use it after your changes?)

I just had a graph that contained some of these characters in the node labels.
Here is a jsfiddle example:
http://jsfiddle.net/nw63onzk/13/
At least in chrome, the Export XML will not work due to the illegal XML (if you change/remove the node with the < in the name, it will work).

@sveinp thaks. Now I am able to see the initial problem. I merged this PR (I merged your commit then I moved the changes to src files and run 'gulp build' comment).


Edit title of a gui

Hi, how can I edit the title of a gui on update? (I want insert current page into title)

there is no such feature currently.

It will be added in future?

i don't think so because the repository is quite death


#161469242 Create Categories

What does this PR do?
Creates product categories
Relevant Pivotal Tracker stories?
#161469242

Pull Request Test Coverage Report for Build 39

19 of 54 (35.19%)  changed or added relevant lines in 4 files are covered.
13 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-16.3%) to 45.93%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/api/v2/views/user_views.py
0
1
0.0%

app/api/v2/views/category_views.py
10
19
52.63%

app/api/v2/models/category_model.py
6
31
19.35%

Files with Coverage Reduction
New Missed Lines
%

app/init.py
2
89.47%

app/api/v2/models/user_model.py
4
51.61%

app/api/v2/views/user_views.py
7
64.52%

Totals

Change from base Build 37:
-16.3%

Covered Lines:
79

Relevant Lines:
172

💛  - Coveralls


beta 20 compatibility

I think this change is not really needed, the tilde allows higher beta versions.
https://getcomposer.org/doc/articles/versions.md#tilde-version-range-

Sorry @MakeilaLundy, I did not know about
https://github.com/craftcms/cms/wiki/Beta-20--Update-Guide


audioFromTensor or audioFromBlob or audioFromArrayBuffer

Area Select
react-native-pytorch-core (core package)
Description
Please, add up functionality for converting audio tensor to audio or saving audio tensor to file just like there is an implementation with images

I have found experimental.audioFromBytes
in experimental namespace but keep getting  [Error: Expect jsi::Number or jsi::Array, but another type is given]

managed to work around the issue it seems, audio resampling would be also a nice thing to have, definitely


Port setting ignored / not applied

LDAP URL was parsed, but port setting not stored.
For ldaps:// connections, the port was then not applied because ldap_connect ignores the port parameter if a URL is used in the hostname.

Thanks for spotting! It'l take some time (hours, not days) until this change is passed on to the wordpress-repo though

No problem, I'm using it directly from git at the moment.


Cleanup cli.rs

Some commits that cleans up the code in cli.rs:

Remove an unneeded move of the config data in the config subcommand
Remove unneeded clone of the default_session in the kill subcommand
Only load the config once in handle_sub_commands

Also fixed a misspelled comment.

LGTM


catch statement has an issue in verify-machine-requirements.js

Prerequisites

[] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Steps to Reproduce

run script/bootstrap

Expected behavior:
run script

Actual behavior:
shows errors

atom version 1.56.0

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀


created_at is also modified when we edit the blog (demo)

I noticed the created_at field being updated to have the same value as updated_at when I edited a record (the default demo application that we have after following the install instructions).

this was resolved in https://github.com/drujensen/kemalyst-model/pull/4


Adding the VQAMED problem

These are the configuration files and problem class for VQAMED data.

This pull request introduces 1 alert when merging d3a708d55d7f4d72abca87b704268a83f1955550 into d8243c87622e66f66a5ad64d7281dc8e5c96a510 - view on LGTM.com
new alerts:

1 for Except block handles 'BaseException'

Comment posted by LGTM.com


Crash while moving iteams

Description
The software crashes when I try to move items
Steps To Reproduce
1- select several items
2- mve them to another folder or to a software
3-Files crash and close
Steps to fix

fix crash when moving several items

Files Version
2.3.12
Windows Version
Windows 10 Pro Version	21H2 Installed on	25/08/2022 OS build	19044.2251 Experience	Windows Feature Experience Pack 120.2212.4180.0
Relevant Assets/Logs
debug_fulltrust.log
2022-11-19 17:45:59.8002|WARN|HandleShellRecentItemsMessage|
	System.ComponentModel.Win32Exception (15): The system cannot find the drive specified.
   at Vanara.PInvoke.Shell32.ShellUtil.GetShellItemForPath(String path)
   at Vanara.Windows.Shell.ShellItem..ctor(String path)
   at Vanara.Windows.Shell.ShellLink.get_Target()
   at Files.FullTrust.MessageHandlers.RecentItemsHandler.<>c__DisplayClass11_0.<HandleShellRecentItemsMessage>b__0()

Is this still an issue in the preview version? https://files.community/download/preview

It is on all versions


Adding exception handling code to tf.Dimension methods

This PR adds exception handling code to some of the tf.Dimension methods.

Thanks, @dynamicwebpaige for the review.

Commented on a similar PR https://github.com/tensorflow/tensorflow/pull/27962, please see the comments there.


Go 1.5 on OSX fails to build unable to locate sysctl

go tool dist: FAILED: sysctl machdep.cpu.extfeatures: exec: "sysctl": executable file not found in $PATH
builder for ‘/nix/store/jqgqfv3i61c5pi2f2vxar41k80fajmad-go-1.5.drv’ failed with exit code 1
error: build of ‘/nix/store/jqgqfv3i61c5pi2f2vxar41k80fajmad-go-1.5.drv’ failed

Log: https://gist.github.com/miah/67765a0452c09921c1b7
sysctl is of course included with osx, and located in /usr/sbin.

To maybe save whoever fixes this some time:
It worked for me after changing the install phase in ~/.nix-defexpr/channels/nixpkgs/pkgs/development/compilers/go/1.5.nix.
I first added /usr/sbin to the path and ran into another bug.
That's why I also changed all.bash to make.bash. That's in no way a proper fix, but I didn't see another way; the bug is apparently related to CGO and Go issue 11994.
I just didn't see where I can best add the official workaround (-ldflags=-s) during the tests - probably somewhere in https://github.com/golang/go/blob/master/src/cmd/dist/test.go#L589.
Here's the relevant part of the file after changes:
    export PATH="$GOBIN:$PATH:/usr/sbin"
    cd ./src
    echo Building
    ./make.bash

I guess it's not the proper way, but I restored the original version of 1.5.nix afterwards.
Using nix-build -A on a fresh clone of nixpks just unleashed a bunch of compilation issues starting with stuff in zlib I didn't want to deal with, so I fumbled through this the way I did.

probably long fixed. @zimbatm

I don't have a mac anymore. Let's close this and see if it gets re-opened.


Add link to run on MyBinder.org to run jupyter notebook for Free.

Hi Peter, thanks for putting this on GitHub, please find attached a
Patch that add :

a requirements.txt (that only add numpy so far)
and a link to launch on MyBinder.org.

MyBinder.org is a service that we (the Jupyter team) run for free, (no
login required, no Personal Information collected), that turn any GitHub
repository with Jupyter Notebooks into an ephemeral docker image which
is launched on Google Cloud Engine for a couple of hours. Images are
built on the fly if repository have changes, so it may take a few
minutes to launch after merged pull-request, or pushes.Otherwise it
should be quasi instantaneous, so the link added to the Readme should
alway be up to date (all of that is of course conditional to our servers
having enough capacity and we know you can be quite popular... So sorry
if you encounter delays)! MyBinder needs the requirement.txt to figure
out what to install (when running Python, because it can run R,
Julia...) so I added numpy, which seem necessary for some notebooks !
To anyone reading, the images are ephemeral so once you leave the tab,
your changes are gone and there is not way to save it ! Download
notebooks on your computer if you have significant modifications !
 I hope
adding Binder to them would encourage people to play with it.
It's completely ok if you wish not to add the badge, it just requires
readers to past info manually on https://mybinder.org/, or use the
chrome or firefox extensions.
Thanks !
--
Matthias

I was looking for a good solution to run the notebooks; thanks for suggesint MyBinder and setting this up!


Suggestion: Use Floodgate Universally linked account instead of having to sign in... every single time

I use a Nintendo Switch but I'm already linked so this saves a lot of time of having to dig out my phone open the link type the code log in and then go back to the switch, Also hard on my phone and ipad. thanks :)

GeyserConnect could check if the Bedrock account is linked to a Java account, but the Global Api (which contains the global linking system), doesn't store user credentials (which would be a massive security risk), which puts that out if the question
The global linking system was designed as an extension of floodgate. i.e, bypass the authentication of the server, not store credentials for authentication

Yeah, this is something we don't plan on implementing, as we don't want to store credentials or authentication tokens remotely. Geyser standalone exists as an alternative where you can input your own code, or you can compile your own GeyserConnect and include your credentials in there.
Thanks anyway.


502 Bad Gateway during Exposure Check

Technical details

Device name: Google Pixel 6
Android version: 12
App version: 2.14.1

Describe the bug
When I want to check for positive encouters I get during download the Error Message: Cause 4000: Something went wrong. Your Internet Connection may have been lost. Please ensure that you are connected to the Internet.
I already restarted the device, tried it again via WiFi and Mobile Data, and the error still continues. The device itself has an internet connection without problems.
Via click on details I get this error:
Ursache:de.rki.coronawarnapp.exception.http.BadGatewayException: Error during web request: code=502 message=Bad Gateway body=<title>502 Bad Gateway</title>
502 Bad Gateway

nginx'	at de.rki.coronawarnapp.http.HttpErrorParser.intercept(HttpErrorParser.kt:14)	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:14)	at de.rki.coronawarnapp.http.interceptor.RetryInterceptor.intercept(RetryInterceptor.kt:3)	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:14)	at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.kt:4)	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:14)	at de.rki.coronawarnapp.http.interceptor.WebSecurityVerificationInterceptor.intercept(WebSecurityVerificationInterceptor.kt:3)	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:14)	at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:25)	at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:12)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)	at java.lang.Thread.run(Thread.java:920)
Expected behaviour
Encouter Check
Additional context

Also reported in https://github.com/corona-warn-app/cwa-server/issues/1614

Got the same problem on a Samsung S10+.

@Alexispap This issue affects all users as it's server side. Thanks anyways for confirmation

@Lionfox2 @Alexispap @Ein-Tim Thanks for reporting, should work again now.

Corona-Warn-App Open Source Team


Upgrade semver from 6.3.0 to 6.3.1

Hi there,
I just checked out this repository to learn more about the overall architecture of heroicons, especially since I need to build my own iconset (mainly for React). While installing the dependencies I saw that semver needs to be updated to 6.3.1 due to a high severity vulnerability.
Here's the link to the vulnerability: https://security.snyk.io/package/npm/semver/6.3.0
I ran npm audit fix to fix this problem :)

Thanks — not actually a vulnerability to be concerned about to be clear because none of the relevant code is ever shipped to users but always good to keep these warnings quiet.


Added site-feature-break-counter

We all know, we really need this. :bomb: :bomb:

:+1:

If this breaks anything in production, people will kill me :skull: :smile:


Unneccessary readline dependency?

This seems to be a built-in module in python.
What's more, pip install readline fails on arm64 linux.

This will be solved and cleaned up when #107 lands.

I removed the dependency of readline, and the the installation worked: https://github.com/mmabrouk/chatgpt-wrapper/issues/158


test travis' new fast builds feature

Fixes bug 1118887 for olympia

These tests are substantially faster.  Would you talk more about what the "fast builds feature" is and what you're doing to enable it?

Yeah the tests are much faster using this new architecture. It's based on docker images, and has two advantages: it uses 2 cores (instead of 1.5 for the current architecture, from what I can understand), and is much much faster to start (when the machines are loaded, you could wait for several minutes for your build to start... with the new architecture, it should start in less than 10 seconds).
It also seems that this new architecture is running on faster machines, as the total build time is much shorter.
The only limitation I can see for now is that you can't use sudo, so you can't install anything globally, nor use apt. This means you can't install/compile m2crypto for example, so you need to have a precompiled wheel.
To use this new 'fast architecture' you simply need to add sudo: false to your .travis.yml file

Well, my mistake, I merged before your answer. If you feel this is missing something or should be reverted, please let me know :/


csi.server.opensds go into the zombie state

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
I perform fault testing for OpenSDS with Kubernetes and Ceph.One of test cases is simulating the Ceph slow disk impact on OpenSDS and Kubernetes CSI when the StatefulSet start up.The test result shows that the csi.server.opensds process in CSI nodeplugin container  go into the zombie state.This will cause the entire Kubernetes node to be unavailable
What you expected to happen:
The Pod creating failed,but doesn't influence Kubernetes.
How to reproduce it (as minimally and precisely as possible):

First use fio to consume disk performance:

fio -filename=/home/ceph/var/lib/osd/ceph-1032/test -direct=1 -iodepth 32  -rw=write -ioengine=libaio -bs=4M -size=80G  -runtime=120  -name=mytest

Create StorageClass for OpenSDS and create a StatefulSet with 10 Pods.A pod stucks in ContainerCreating state when it's creating：

fio-test-ss-5                        1/1       Running             0          11m       <IP_ADDRESS>      <IP_ADDRESS>    <none>
fio-test-ss-6                        1/1       Running             0          11m       <IP_ADDRESS>      <IP_ADDRESS>    <none>
fio-test-ss-7                        1/1       Running             0          10m       <IP_ADDRESS>      <IP_ADDRESS>    <none>
fio-test-ss-8                        0/1       ContainerCreating   0          9m        <none>           <IP_ADDRESS>    <none>

Check Ceph and OpenSDS,the volumes are created,but check the corresponding Kubernetes node and the CSI nodeplugin logs:

I1123 06:45:51.633227       1 logs.go:40] 2018/11/23 06:45:51 helper.go:89: Command: blkid /dev/rbd1
I1123 06:45:51.636349       1 logs.go:40] 2018/11/23 06:45:51 helper.go:250: failed to GetFSType: exit status 2
I1123 06:45:51.636370       1 logs.go:40] 2018/11/23 06:45:51 helper.go:89: Command: mkfs -t ext4 -F /dev/rbd1
I1123 06:45:51.639745       1 logs.go:40] 2018/11/23 06:45:51 helper.go:278: failed to Format: exit status

Because Ceph IO stuck, /dev/rbd1 mkfs failed.And csi.server.opensds go into the zombie state.
I check the rbd status,the rbd map process die.
root@k8s-node2:~# ps aux| grep server
root     124127  0.0  0.0      0     0 ?        Zsl  14:06   0:00 [csi.server.open] <defunct>

Environment:

Hotpot(release/branch) version:v0.2.0
OS (e.g. from /etc/os-release):Debian 8
Kernel (e.g. uname -a):3.16.0-6-amd64

I will close this issue, please reopen it if there are still some problems.


bug: plugin specs using the same base repo are not loaded properly

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.10.0 Release Build
Operating system/version
NixOS unstable
Describe the bug
Since version 11.0.0 lazy does no longer work with specs using the same underlying directory/repo. See the repro for an example. The issue was introduced with the major version 11, version 10 still worked in its final minor versioning.
Steps To Reproduce

run nvim -u repro.lua repro.lua as I provide it, and observe that only one of the mini.nvim modules is loaded in :Lazy
switch the comment from line 12 to line 13 to use the version 10
rm -r ./.repro
repeat step 1, it's working now

Expected Behavior
Both specs should load correctly, even if they're based on the same plugin directory.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
	vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
	-- vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
	vim.fn.system({ "git", "clone", "--branch=v11.0.0", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
	-- vim.fn.system({ "git", "clone", "--branch=v10.24.3", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
	"folke/tokyonight.nvim",
	-- add any other plugins here
	{
		"echasnovski/mini.nvim",
		main = "mini.statusline",
		name = "mini.statusline",
		opts = {},
	},
	{
		"echasnovski/mini.nvim",
		main = "mini.tabline",
		name = "mini.tabline",
		opts = {},
	},
}
require("lazy").setup(plugins, {
	root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

duplicate of https://github.com/folke/lazy.nvim/issues/1610
tldr: it was an unintended bug which got fixed

Dup #1610

Sorry to bother you, search didn't turn that one up 🙃


JAX-RS endpoints no longer being hit with 3.0.3 or 3.0.4

Trying the latest versions of renarde security (3.0.3 or 3.0.4) with Quarkus 3.4.1 causes my endpoints to no longer be hit.
I have a /login endpoint which works fine with previous versions, but trying them with the latest versions causes them to either silenty fail or not be hit at all (hard to tell since there are no errors).
Using this request for both versions and changing nothing else in the code.
curl -v -c support_cookiefile --data<EMAIL_ADDRESS>http://localhost:8080/login
CURL OUTPUT
3.0.2
*   Trying <IP_ADDRESS>:8080...
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> POST /login HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/8.1.2
> Accept: */*
> Content-Length: 41
> Content-Type: application/x-www-form-urlencoded
>
< HTTP/1.1 303 See Other
< Location: http://localhost:8080/
* Added cookie QuarkusUser="eyJjdHkiOiJKV1QiLCJhbGciOiJSU0EtT0FFUCIsImVuYyI6IkEyNTZHQ00ifQ.fUeT_LmPODjBm4vQibv2s2TygiLWLX9NRIL0sFx7Pe2VPtavXAup8C2KZuJ5lhy_71rMBCvEnUX3Rojw26wcaFndreEn_3QQv_XW2lS2PkFpHILqd65BE_mpU6qNX37VyYYp52nKovOrdx5tyooDLukRiKLeBQ4Kmc8yttcknsl4tCAPT9ltVUzDkARfnwH_rc5jbumI4UlURGpPJLs7dH1IgcVw5yMtFoHHdiMKC0Jjsq6c7fCTCSaZ3MVlXfejw3TwHjZvs2lV6wYE8DPpGKTKYF9v_M0-4Vq1DaQVhlf5jui0d7LDkODZbOskoYOvmqOJnDLLr16p_USgyDJUVQ._G6AsoEFOEaSU2ht.mgCfkCfxYo9BYmaHqBZjuD8e7C6kFjkzK2-WAIPXjOjgzXutd05c4OU7_DqvyWAj8-DeTVrtAjWSxoB0HAfyGHeDbVewxOj3dQ-7a1mFNIByLPK-2OiRcnbs6dwpATBPt_yfBlLSIZhxw1AkHL9hB6orrDDUsm3o0Dp3vVuuVSJPgcPKMLkr8Sk2tgeyQB8M2ueKYYd4FVoqce4bhP2bQgKgb0eG6RAksHRI_2Zx4_m4xKugYEb8uxNvSPAGDR_bFL0qE9CMyl9mTwBRk1RJcZfuWq6PZLwL8_Gb7jJ5ghVviq45ZydCyzUWP2TQGwh9VKLNCRgTCvu908m1kDXqqAPiIHYwmZNlU8Dltifef1wDQMF5TkKYi8QSbTxxP2nVC0fNJFwWhXDXaAlANEbf_yeWYyU6xBZrhGjNuaiPfmWhi0DS0x6SLLrzFKfTxSE72jLGUsjizfwun281ciY3bfGdMqXMumJvz-SLQnow8J0ZMStPMLZP-jMnuGgiSfGwzLjla9WJR8KT8vp9BHh9O24zbsEZ24PuTjuWmkTUYb3SScUyegbz0sqOjd4dFyNTkkN62NrI-WhSB2UaxA06UJHS4NNVIgfUC8dpSN2wrKA98kpR8-5oigNXQcCTk_WKwdJ7rEXErngtdEszoInZ-BqT6o7ku0F00j5AikUGJjLOEQ8X2xAzleRa1XSqojfEldx2ZN--DqAAxlqZJ9mUYhJwZmcCok7U02Y5QqDFqxLxges3t1aep2ObViEhLadqBuLYcDnFP4RhZ85IvCRhqqyEHCyumGNDv1o.1Fz016ChznUmU5yerw1NOg" for domain localhost, path /, expire 0
< Set-Cookie: QuarkusUser=eyJjdHkiOiJKV1QiLCJhbGciOiJSU0EtT0FFUCIsImVuYyI6IkEyNTZHQ00ifQ.fUeT_LmPODjBm4vQibv2s2TygiLWLX9NRIL0sFx7Pe2VPtavXAup8C2KZuJ5lhy_71rMBCvEnUX3Rojw26wcaFndreEn_3QQv_XW2lS2PkFpHILqd65BE_mpU6qNX37VyYYp52nKovOrdx5tyooDLukRiKLeBQ4Kmc8yttcknsl4tCAPT9ltVUzDkARfnwH_rc5jbumI4UlURGpPJLs7dH1IgcVw5yMtFoHHdiMKC0Jjsq6c7fCTCSaZ3MVlXfejw3TwHjZvs2lV6wYE8DPpGKTKYF9v_M0-4Vq1DaQVhlf5jui0d7LDkODZbOskoYOvmqOJnDLLr16p_USgyDJUVQ._G6AsoEFOEaSU2ht.mgCfkCfxYo9BYmaHqBZjuD8e7C6kFjkzK2-WAIPXjOjgzXutd05c4OU7_DqvyWAj8-DeTVrtAjWSxoB0HAfyGHeDbVewxOj3dQ-7a1mFNIByLPK-2OiRcnbs6dwpATBPt_yfBlLSIZhxw1AkHL9hB6orrDDUsm3o0Dp3vVuuVSJPgcPKMLkr8Sk2tgeyQB8M2ueKYYd4FVoqce4bhP2bQgKgb0eG6RAksHRI_2Zx4_m4xKugYEb8uxNvSPAGDR_bFL0qE9CMyl9mTwBRk1RJcZfuWq6PZLwL8_Gb7jJ5ghVviq45ZydCyzUWP2TQGwh9VKLNCRgTCvu908m1kDXqqAPiIHYwmZNlU8Dltifef1wDQMF5TkKYi8QSbTxxP2nVC0fNJFwWhXDXaAlANEbf_yeWYyU6xBZrhGjNuaiPfmWhi0DS0x6SLLrzFKfTxSE72jLGUsjizfwun281ciY3bfGdMqXMumJvz-SLQnow8J0ZMStPMLZP-jMnuGgiSfGwzLjla9WJR8KT8vp9BHh9O24zbsEZ24PuTjuWmkTUYb3SScUyegbz0sqOjd4dFyNTkkN62NrI-WhSB2UaxA06UJHS4NNVIgfUC8dpSN2wrKA98kpR8-5oigNXQcCTk_WKwdJ7rEXErngtdEszoInZ-BqT6o7ku0F00j5AikUGJjLOEQ8X2xAzleRa1XSqojfEldx2ZN--DqAAxlqZJ9mUYhJwZmcCok7U02Y5QqDFqxLxges3t1aep2ObViEhLadqBuLYcDnFP4RhZ85IvCRhqqyEHCyumGNDv1o.1Fz016ChznUmU5yerw1NOg;Version=1;Path=/;HttpOnly;SameSite=LAX
< content-length: 0
* Added cookie _renarde_crsf="3fDvp1ZeCiO/SwUJqWKMdA==" for domain localhost, path /, expire 0
< set-cookie: _renarde_crsf=3fDvp1ZeCiO/SwUJqWKMdA==; Path=/
* Added cookie _renarde_flash="e30=" for domain localhost, path /, expire 0
< set-cookie: _renarde_flash=e30=; Path=/; HTTPOnly; SameSite=Lax
<
* Connection #0 to host localhost left intact

3.0.4

*   Trying <IP_ADDRESS>:8080...
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> POST /login HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/8.1.2
> Accept: */*
> Content-Length: 41
> Content-Type: application/x-www-form-urlencoded
>
< HTTP/1.1 400 Bad Request
< content-length: 0
* Added cookie _renarde_flash="e30=" for domain localhost, path /, expire 0
< set-cookie: _renarde_flash=e30=; Path=/; HTTPOnly; SameSite=Lax
<
* Connection #0 to host localhost left intact

You're doing a POST without a CSRF token, that's why it doesn't work. I agree there should be an error message, though. If you're using {#form ...} you will get a CSRF token. If not, you need to obtain it before-hand with a GET request, which you can do with:
public Application extends Controller {
 @Inject
 CsrfTokenParameterProvider csrf;

 public String csrf(){
  return csrf.getToken();
 }
}

All of this works OOTB if using {#form} and Qute templates, or even in JUnit tests, using renarde-test.
What is the context in which you're calling this POST /login? Client Java library, or AJAX, or curl, or else?

I was calling it from the curl command line and in the previous versions it would automatically work as I showed in the output above.
When using the latest version that automatic redirection no longer works.

Well, it's not that it doesn't work, it's that it requires a CSRF token. All POST methods with a form body now require it. That has always been the goal, but issues prevented it from working properly.
Can you obtain a token before making your curl call?
Note that if you actually login from your browser, this will work out of the box.

This application is a legacy application that was written in Scala/Play 2.x. It used the built in authentication mechanism in Play security.
I converted the application to use Renarde and Renarde Security with JDBC authentication since they were storing their user information and passwords in the database.

With this, you mean? https://quarkus.io/guides/security-jdbc

Well, unfortunately no, they are doing their own lookups in a few tables to get the id and then find the password (hash) in another table and then use BCrypt to compare the incoming passwords with the one stored in the database.
Then if found, they return the User object, otherwise throw error.
Ideally, I would've used what you mentioned but the code I'm working with is many years old and not well laid out so I couldn't touch a lot.
Even better, I would use Keycloak and OIDC but that is a big upgrade for them and no time at the moment.

OK, so are you using this? https://docs.quarkiverse.io/quarkus-renarde/dev/security.html#custom_authentication_with_jwt

For scripts, there are two alternatives, IMO:

you can generate a JWT token on the script's end, given that you have access to the server's private key, there's probably CLI tools for that
you could use basic auth instead of relying on the login+obtaining the JWT cookie

I tried to find how to enable basic auth in Renarde and it appears I must do something to support it. Would it make your clients easier or are you more interested in option 1?


list gridscale among tested providers

I just tested our (gridscale) object storage with goofys and it works just fine.

sure. Sorry, I somehow did not pay attention to that. ;)

Sorry for the late response. I condensed the ceph listings since they should all work the same way. At some point it may not make sense to keep adding ceph providers but we will cross that bridge when we get there.


Compiling to x86_64-unknown-linux-gnu with alsa using libudev dependency

My compilation fails:
called `Result::unwrap()` on an `Err` value: "`PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=\"1\" PKG_CONFIG_ALLOW_SYSTEM_LIBS=\"1\" \"pkg-config\" \"--libs\" \"--cflags\" \"libudev\"` did not exit successfully: exit status: 1\nerror: could not find system library 'libudev' required by the 'libudev-sys' crate\n\n--- stderr\nPackage libudev was not found in the pkg-config search path.\nPerhaps you should add the directory containing `libudev.pc'\nto the PKG_CONFIG_PATH environment variable\nNo package 'libudev' found\n"

even though I added this to my Cross.toml:
[target.x86_64-unknown-linux-gnu]
pre-build = [
    "dpkg --add-architecture $CROSS_DEB_ARCH",
    "apt-get update && apt-get install --assume-yes pkg-config:$CROSS_DEB_ARCH libssl-dev:$CROSS_DEB_ARCH ca-certificates:$CROSS_DEB_ARCH libasound2-dev:$CROSS_DEB_ARCH libpulse-dev:$CROSS_DEB_ARCH libdbus-1-dev:$CROSS_DEB_ARCH portaudio19-dev:$CROSS_DEB_ARCH libudev-dev:$CROSS_DEB_ARCH"
]

My run command is cross build --release --target x86_64-unknown-linux-gnu.
I searched online and it looks like I might be missing from complicated linker env variables?

I'm not able to replicate this, neither with v0.2.5 or using main. Can you post the entire build log
here's my try at reproducing it
cargo init
cargo add libudev-sys

# Cross.toml
[target.x86_64-unknown-linux-gnu]
pre-build = [
    "dpkg --add-architecture $CROSS_DEB_ARCH",
    """apt-get update && apt-get install --assume-yes \
        pkg-config:$CROSS_DEB_ARCH \
        libssl-dev:$CROSS_DEB_ARCH \
        ca-certificates:$CROSS_DEB_ARCH \
        libasound2-dev:$CROSS_DEB_ARCH \
        libpulse-dev:$CROSS_DEB_ARCH \
        libdbus-1-dev:$CROSS_DEB_ARCH \
        portaudio19-dev:$CROSS_DEB_ARCH \
        libudev-dev:$CROSS_DEB_ARCH \
    """
]

❯ cross build --release --target x86_64-unknown-linux-gnu
   Compiling pkg-config v0.3.29
   Compiling libc v0.2.153
   Compiling libudev-sys v0.1.4
   Compiling libudev-test v0.1.0 (/project)
    Finished release [optimized] target(s) in 44.24s

Hm i'm not too sure why but the error I get now is related to alsa:
error: failed to run custom build command for `alsa-sys v0.3.1`

Caused by:
  process didn't exit successfully: `/target/release/build/alsa-sys-6d9c1bff4963f07a/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=ALSA_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=ALSA_STATIC
  cargo:rerun-if-env-changed=ALSA_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr
  thread 'main' panicked at /Users/cbournhonesque/dev/rust/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alsa-sys-0.3.1/build.rs:13:18:
  `PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" PKG_CONFIG_ALLOW_SYSTEM_LIBS="1" "pkg-config" "--libs" "--cflags" "alsa"` did not exit successfully: exit status: 1
  error: could not find system library 'alsa' required by the 'alsa-sys' crate

  --- stderr
  Package alsa was not found in the pkg-config search path.
  Perhaps you should add the directory containing `alsa.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'alsa' found


Hide certain fields from the Django admin interface

Describe the problem
I'm using the Django Admin to expose some of the values used by Constance. However, there are a few sensible ones that I would prefer to keep completely hidden from the user interface (not even shown using a password field)
Is this possible?

No

class PostCodesAdmin(admin.ModelAdmin):
exclude = ('pcname',)  #This exclude function will do which u want!
list_display = ('id', 'gisid', 'title', )


Refactor proxy code - implement interface

Short
Reorder/-write net-managers proxy code in order for it to be more flexible with outlook on IPv6 implementation extension.
Proposal
Currently the code is very limited to IPv4 packets, working with raw go types (net.IPv4). Casting the packets to custom types which implement an interface will make the code easier to modify and extend in the long run.
Ratio
Makes code cleaner and easier to extend with functionality
Impact
net-manager
Status
Needs testing
Checklist

[x] Discussed
[ ] Documented
[x] Implemented
[ ] Tested

Will be included in #153


Create simon game

Create a Simon game project

Hello @manjunani @zheeno @akbar-alam, please assign me this issue.

HI @evasharma12 , The issue has been assigned on your name kindly go ahead with the changes


Question: Does OpenDAL supports internal endpoints for alicloud oss?

https://www.alibabacloud.com/help/en/object-storage-service/latest/oss-internal-endpoints-and-vip-ranges

Oh find it. https://github.com/apache/incubator-opendal/blob/61fbd696d963b96130ff8ab4aabb3ab51111d0b7/core/src/services/oss/backend.rs#L112


Skin mods seem to simply not work?

At first, I simply replaced the images, xmls, and such in the assets folder, and then the game crashed when I tried any song. I then, tried using the 3.2 hotpatch, and the game crashed again. I then tried using the mod folder and tried the images folder. The game read the icons just fine, but I couldn't see if the actual pngs and xmls were because the game still kept crashing. Do I need custom json files for each skin and need to put them into the character folder?

There might be an issue with your xml/png files, this post isn't very informative