Lighthouse does not have a static_host_map entry

I am trying to setup nebula for my home. I have a VM on oracle cloud that should act as the light house. I believe I have configured it all correctly but I am still getting the error
INFO[0000] Firewall rule added                           firewallRule="map[caName: caSha: direction:outgoing endPort:0 groups:[] host:any ip: proto:0 startPort:0]"
INFO[0000] Firewall rule added                           firewallRule="map[caName: caSha: direction:incoming endPort:0 groups:[] host:any ip: proto:1 startPort:0]"
INFO[0000] Firewall rule added                           firewallRule="map[caName: caSha: direction:incoming endPort:443 groups:[laptop home] host: ip: proto:6 startPort:443]"
INFO[0000] Firewall started                              firewallHash=876eda8b2903dec4d256217a3b832246533ae8c94ce26a173645b36db278ce0f
INFO[0000] Main HostMap created                          network=<IP_ADDRESS>/24 preferredRanges="[]"
INFO[0000] UDP hole punching enabled
ERRO[0000] Lighthouse unreachable                        error="Lighthouse <IP_ADDRESS> does not have a static_host_map entry"
INFO[0000] Prometheus stats listening on <IP_ADDRESS>:8099 at /metrics
INFO[0000] Nebula interface is active                    build=1.3.0 interface=nebula1 network=<IP_ADDRESS>/24 udpAddr="<IP_ADDRESS>:4242"

Config for my lighthouse
# This is the nebula example configuration file. You must edit, at a minimum, the static_host_map, lighthouse, and firewall sections
# Some options in this file are HUPable, including the pki section. (A HUP will reload credentials from disk without affecting existing tunnels)

# PKI defines the location of credentials for this node. Each of these can also be inlined by using the yaml ": |" syntax.
pki:
  # The CAs that are accepted by this node. Must contain one or more certificates created by 'nebula-cert ca'
  ca: /etc/nebula/ca.crt
  cert: /etc/nebula/oracle-vm.crt
  key: /etc/nebula/oracle-vm.key
  #blocklist is a list of certificate fingerprints that we will refuse to talk to
  #blocklist:
  #  - c99d4e650533b92061b09918e838a5a0a6aaee21eed1d12fd937682865936c72

# The static host map defines a set of hosts with fixed IP addresses on the internet (or any network).
# A host can have multiple fixed IP addresses defined here, and nebula will try each when establishing a tunnel.
# The syntax is:
#   "{nebula ip}": ["{routable ip/dns name}:{routable port}"]
# Example, if your lighthouse has the nebula IP of <IP_ADDRESS> and has the real ip address of <IP_ADDRESS> and runs on port 4242:
static_host_map:
  "<IP_ADDRESS>": ["pubip:4242"]

lighthouse:
  # am_lighthouse is used to enable lighthouse functionality for a node. This should ONLY be true on nodes
  # you have configured to be lighthouses in your network
  am_lighthouse: true
  # serve_dns optionally starts a dns listener that responds to various queries and can even be
  # delegated to for resolution
  #serve_dns: false
  #dns:
    # The DNS host defines the IP to bind the dns listener to. This also allows binding to the nebula node IP.
    #host: <IP_ADDRESS>
    #port: 53
  # interval is the number of seconds between updates from this node to a lighthouse.
  # during updates, a node sends information about its current IP addresses to each node.
  interval: 60
  # hosts is a list of lighthouse hosts this node should report to and query from
  # IMPORTANT: THIS SHOULD BE EMPTY ON LIGHTHOUSE NODES
  # IMPORTANT2: THIS SHOULD BE LIGHTHOUSES' NEBULA IPs, NOT LIGHTHOUSES' REAL ROUTABLE IPs
  #hosts: {}
  #  - "<IP_ADDRESS>"

  # remote_allow_list allows you to control ip ranges that this node will
  # consider when handshaking to another node. By default, any remote IPs are
  # allowed. You can provide CIDRs here with `true` to allow and `false` to
  # deny. The most specific CIDR rule applies to each remote. If all rules are
  # "allow", the default will be "deny", and vice-versa. If both "allow" and
  # "deny" rules are present, then you MUST set a rule for "<IP_ADDRESS>/0" as the
  # default.
  remote_allow_list:
    # Example to block IPs from this subnet from being used for remote IPs.
    "<IP_ADDRESS>/24": true

    # A more complicated example, allow public IPs but only private IPs from a specific subnet
    #"<IP_ADDRESS>/0": true
    #"<IP_ADDRESS>/8": false
    #"<IP_ADDRESS>/24": true

  # local_allow_list allows you to filter which local IP addresses we advertise
  # to the lighthouses. This uses the same logic as `remote_allow_list`, but
  # additionally, you can specify an `interfaces` map of regular expressions
  # to match against interface names. The regexp must match the entire name.
  # All interface rules must be either true or false (and the default will be
  # the inverse). CIDR rules are matched after interface name rules.
  # Default is all local IP addresses.
  #local_allow_list:
    # Example to block tun0 and all docker interfaces.
    #interfaces:
      #tun0: false
      #'docker.*': false
    # Example to only advertise this subnet to the lighthouse.
    #"<IP_ADDRESS>/8": true

# Port Nebula will be listening on. The default here is 4242. For a lighthouse node, the port should be defined,
# however using port 0 will dynamically assign a port and is recommended for roaming nodes.
listen:
  # To listen on both any ipv4 and ipv6 use "[::]"
  host: <IP_ADDRESS>
  port: 4242
  # Sets the max number of packets to pull from the kernel for each syscall (under systems that support recvmmsg)
  # default is 64, does not support reload
  #batch: 64
  # Configure socket buffers for the udp side (outside), leave unset to use the system defaults. Values will be doubled by the kernel
  # Default is net.core.rmem_default and net.core.wmem_default (/proc/sys/net/core/rmem_default and /proc/sys/net/core/rmem_default)
  # Maximum is limited by memory in the system, SO_RCVBUFFORCE and SO_SNDBUFFORCE is used to avoid having to raise the system wide
  # max, net.core.rmem_max and net.core.wmem_max
  #read_buffer: 10485760
  #write_buffer: 10485760

# EXPERIMENTAL: This option is currently only supported on linux and may
# change in future minor releases.
#
# Routines is the number of thread pairs to run that consume from the tun and UDP queues.
# Currently, this defaults to 1 which means we have 1 tun queue reader and 1
# UDP queue reader. Setting this above one will set IFF_MULTI_QUEUE on the tun
# device and SO_REUSEPORT on the UDP socket to allow multiple queues.
#routines: 1

punchy:
  # Continues to punch inbound/outbound at a regular interval to avoid expiration of firewall nat mappings
  punch: true

  # respond means that a node you are trying to reach will connect back out to you if your hole punching fails
  # this is extremely useful if one node is behind a difficult nat, such as a symmetric NAT
  # Default is false
  respond: true

  # delays a punch response for misbehaving NATs, default is 1 second, respond must be true to take effect
  #delay: 1s

# Cipher allows you to choose between the available ciphers for your network. Options are chachapoly or aes
# IMPORTANT: this value must be identical on ALL NODES/LIGHTHOUSES. We do not/will not support use of different ciphers simultaneously!
#cipher: chachapoly

# Local range is used to define a hint about the local network range, which speeds up discovering the fastest
# path to a network adjacent nebula node.
#local_range: "<IP_ADDRESS>/24"

# sshd can expose informational and administrative functions via ssh this is a
#sshd:
  # Toggles the feature
  #enabled: true
  # Host and port to listen on, port 22 is not allowed for your safety
  #listen: <IP_ADDRESS>:2222
  # A file containing the ssh host private key to use
  # A decent way to generate one: ssh-keygen -t ed25519 -f ssh_host_ed25519_key -N "" < /dev/null
  #host_key: ./ssh_host_ed25519_key
  # A file containing a list of authorized public keys
  #authorized_users:
    #- user: steeeeve
      # keys can be an array of strings or single string
      #keys:
        #- "ssh public key string"

# Configure the private interface. Note: addr is baked into the nebula certificate
tun:
  # When tun is disabled, a lighthouse can be started without a local tun interface (and therefore without root)
  disabled: false
  # Name of the device
  dev: nebula1
  # Toggles forwarding of local broadcast packets, the address of which depends on the ip/mask encoded in pki.cert
  drop_local_broadcast: false
  # Toggles forwarding of multicast packets
  drop_multicast: false
  # Sets the transmit queue length, if you notice lots of transmit drops on the tun it may help to raise this number. Default is 500
  tx_queue: 500
  # Default MTU for every packet, safe setting is (and the default) 1300 for internet based traffic
  mtu: 1300
  # Route based MTU overrides, you have known vpn ip paths that can support larger MTUs you can increase/decrease them here
  routes:
    #- mtu: 8800
    #  route: <IP_ADDRESS>/16
  # Unsafe routes allows you to route traffic over nebula to non-nebula nodes
  # Unsafe routes should be avoided unless you have hosts/services that cannot run nebula
  # NOTE: The nebula certificate of the "via" node *MUST* have the "route" defined as a subnet in its certificate
  unsafe_routes:
    #- route: <IP_ADDRESS>/24
    #  via: <IP_ADDRESS>
    #  mtu: 1300 #mtu will default to tun mtu if this option is not sepcified

# TODO
# Configure logging level
logging:
  # panic, fatal, error, warning, info, or debug. Default is info
  level: info
  # json or text formats currently available. Default is text
  format: text
  # Disable timestamp logging. useful when output is redirected to logging system that already adds timestamps. Default is false
  #disable_timestamp: true
  # timestamp format is specified in Go time format, see:
  #     https://golang.org/pkg/time/#pkg-constants
  # default when `format: json`: "2006-01-02T15:04:05Z07:00" (RFC3339)
  # default when `format: text`:
  #     when TTY attached: seconds since beginning of execution
  #     otherwise: "2006-01-02T15:04:05Z07:00" (RFC3339)
  # As an example, to log as RFC3339 with millisecond precision, set to:
  #timestamp_format: "2006-01-02T15:04:05.000Z07:00"

stats:
  #type: graphite
  #prefix: nebula
  #protocol: tcp
  #host: <IP_ADDRESS>:9999
  #interval: 10s

  type: prometheus
  listen: <IP_ADDRESS>:8099
  path: /metrics
  namespace: prometheusns
  subsystem: nebula
  interval: 10s

  # enables counter metrics for meta packets
  #   e.g.: `messages.tx.handshake`
  # NOTE: `message.{tx,rx}.recv_error` is always emitted
  #message_metrics: false

  # enables detailed counter metrics for lighthouse packets
  #   e.g.: `lighthouse.rx.HostQuery`
  #lighthouse_metrics: false

# Handshake Manger Settings
#handshakes:
  # Handshakes are sent to all known addresses at each interval with a linear backoff,
  # Wait try_interval after the 1st attempt, 2 * try_interval after the 2nd, etc, until the handshake is older than timeout
  # A 100ms interval with the default 10 retries will give a handshake 5.5 seconds to resolve before timing out
  #try_interval: 100ms
  #retries: 20
  # trigger_buffer is the size of the buffer channel for quickly sending handshakes
  # after receiving the response for lighthouse queries
  #trigger_buffer: 64

# Nebula security group configuration
firewall:
  conntrack:
    tcp_timeout: 12m
    udp_timeout: 3m
    default_timeout: 10m
    max_connections: 100000

  # The firewall is default deny. There is no way to write a deny rule.
  # Rules are comprised of a protocol, port, and one or more of host, group, or CIDR
  # Logical evaluation is roughly: port AND proto AND (ca_sha OR ca_name) AND (host OR group OR groups OR cidr)
  # - port: Takes `0` or `any` as any, a single number `80`, a range `200-901`, or `fragment` to match second and further fragments of fragmented packets (since there is no port available).
  #   code: same as port but makes more sense when talking about ICMP, TODO: this is not currently implemented in a way that works, use `any`
  #   proto: `any`, `tcp`, `udp`, or `icmp`
  #   host: `any` or a literal hostname, ie `test-host`
  #   group: `any` or a literal group name, ie `default-group`
  #   groups: Same as group but accepts a list of values. Multiple values are AND'd together and a certificate would have to contain all groups to pass
  #   cidr: a CIDR, `<IP_ADDRESS>/0` is any.
  #   ca_name: An issuing CA name
  #   ca_sha: An issuing CA shasum

  outbound:
    # Allow all outbound traffic from this node
    - port: any
      proto: any
      host: any

  inbound:
    # Allow icmp between any nebula hosts
    - port: any
      proto: icmp
      host: any

    # Allow tcp/443 from any host with BOTH laptop and home group
    - port: 443
      proto: tcp
      groups:
        - laptop
        - home

Config for my client
# This is the nebula example configuration file. You must edit, at a minimum, the static_host_map, lighthouse, and firewall sections
# Some options in this file are HUPable, including the pki section. (A HUP will reload credentials from disk without affecting existing tunnels)

# PKI defines the location of credentials for this node. Each of these can also be inlined by using the yaml ": |" syntax.
pki:
  # The CAs that are accepted by this node. Must contain one or more certificates created by 'nebula-cert ca'
  ca: /etc/nebula/ca.crt
  cert: /etc/nebula/raspi.crt
  key: /etc/nebula/raspi.key
  #blocklist is a list of certificate fingerprints that we will refuse to talk to
  #blocklist:
  #  - c99d4e650533b92061b09918e838a5a0a6aaee21eed1d12fd937682865936c72

# The static host map defines a set of hosts with fixed IP addresses on the internet (or any network).
# A host can have multiple fixed IP addresses defined here, and nebula will try each when establishing a tunnel.
# The syntax is:
#   "{nebula ip}": ["{routable ip/dns name}:{routable port}"]
# Example, if your lighthouse has the nebula IP of <IP_ADDRESS> and has the real ip address of <IP_ADDRESS> and runs on port 4242:
static_host_map:
  "<IP_ADDRESS>": ["pubip:4242"]

lighthouse:
  # am_lighthouse is used to enable lighthouse functionality for a node. This should ONLY be true on nodes
  # you have configured to be lighthouses in your network
  am_lighthouse: false
  # serve_dns optionally starts a dns listener that responds to various queries and can even be
  # delegated to for resolution
  #serve_dns: false
  #dns:
    # The DNS host defines the IP to bind the dns listener to. This also allows binding to the nebula node IP.
    #host: <IP_ADDRESS>
    #port: 53
  # interval is the number of seconds between updates from this node to a lighthouse.
  # during updates, a node sends information about its current IP addresses to each node.
  interval: 60
  # hosts is a list of lighthouse hosts this node should report to and query from
  # IMPORTANT: THIS SHOULD BE EMPTY ON LIGHTHOUSE NODES
  # IMPORTANT2: THIS SHOULD BE LIGHTHOUSES' NEBULA IPs, NOT LIGHTHOUSES' REAL ROUTABLE IPs
  hosts:
    - "<IP_ADDRESS>"

  # remote_allow_list allows you to control ip ranges that this node will
  # consider when handshaking to another node. By default, any remote IPs are
  # allowed. You can provide CIDRs here with `true` to allow and `false` to
  # deny. The most specific CIDR rule applies to each remote. If all rules are
  # "allow", the default will be "deny", and vice-versa. If both "allow" and
  # "deny" rules are present, then you MUST set a rule for "<IP_ADDRESS>/0" as the
  # default.
  remote_allow_list:
    # Example to block IPs from this subnet from being used for remote IPs.
    "<IP_ADDRESS>/24": true

    # A more complicated example, allow public IPs but only private IPs from a specific subnet
    #"<IP_ADDRESS>/0": true
    #"<IP_ADDRESS>/8": false
    #"<IP_ADDRESS>/24": true

  # local_allow_list allows you to filter which local IP addresses we advertise
  # to the lighthouses. This uses the same logic as `remote_allow_list`, but
  # additionally, you can specify an `interfaces` map of regular expressions
  # to match against interface names. The regexp must match the entire name.
  # All interface rules must be either true or false (and the default will be
  # the inverse). CIDR rules are matched after interface name rules.
  # Default is all local IP addresses.
  #local_allow_list:
    # Example to block tun0 and all docker interfaces.
    #interfaces:
      #tun0: false
      #'docker.*': false
    # Example to only advertise this subnet to the lighthouse.
    #"<IP_ADDRESS>/8": true

# Port Nebula will be listening on. The default here is 4242. For a lighthouse node, the port should be defined,
# however using port 0 will dynamically assign a port and is recommended for roaming nodes.
listen:
  # To listen on both any ipv4 and ipv6 use "[::]"
  host: <IP_ADDRESS>
  port: 4242
  # Sets the max number of packets to pull from the kernel for each syscall (under systems that support recvmmsg)
  # default is 64, does not support reload
  #batch: 64
  # Configure socket buffers for the udp side (outside), leave unset to use the system defaults. Values will be doubled by the kernel
  # Default is net.core.rmem_default and net.core.wmem_default (/proc/sys/net/core/rmem_default and /proc/sys/net/core/rmem_default)
  # Maximum is limited by memory in the system, SO_RCVBUFFORCE and SO_SNDBUFFORCE is used to avoid having to raise the system wide
  # max, net.core.rmem_max and net.core.wmem_max
  #read_buffer: 10485760
  #write_buffer: 10485760

# EXPERIMENTAL: This option is currently only supported on linux and may
# change in future minor releases.
#
# Routines is the number of thread pairs to run that consume from the tun and UDP queues.
# Currently, this defaults to 1 which means we have 1 tun queue reader and 1
# UDP queue reader. Setting this above one will set IFF_MULTI_QUEUE on the tun
# device and SO_REUSEPORT on the UDP socket to allow multiple queues.
#routines: 1

punchy:
  # Continues to punch inbound/outbound at a regular interval to avoid expiration of firewall nat mappings
  punch: true

  # respond means that a node you are trying to reach will connect back out to you if your hole punching fails
  # this is extremely useful if one node is behind a difficult nat, such as a symmetric NAT
  # Default is false
  respond: true

  # delays a punch response for misbehaving NATs, default is 1 second, respond must be true to take effect
  #delay: 1s

# Cipher allows you to choose between the available ciphers for your network. Options are chachapoly or aes
# IMPORTANT: this value must be identical on ALL NODES/LIGHTHOUSES. We do not/will not support use of different ciphers simultaneously!
#cipher: chachapoly

# Local range is used to define a hint about the local network range, which speeds up discovering the fastest
# path to a network adjacent nebula node.
#local_range: "<IP_ADDRESS>/24"

# sshd can expose informational and administrative functions via ssh this is a
#sshd:
  # Toggles the feature
  #enabled: true
  # Host and port to listen on, port 22 is not allowed for your safety
  #listen: <IP_ADDRESS>:2222
  # A file containing the ssh host private key to use
  # A decent way to generate one: ssh-keygen -t ed25519 -f ssh_host_ed25519_key -N "" < /dev/null
  #host_key: ./ssh_host_ed25519_key
  # A file containing a list of authorized public keys
  #authorized_users:
    #- user: steeeeve
      # keys can be an array of strings or single string
      #keys:
        #- "ssh public key string"

# Configure the private interface. Note: addr is baked into the nebula certificate
tun:
  # When tun is disabled, a lighthouse can be started without a local tun interface (and therefore without root)
  disabled: false
  # Name of the device
  dev: nebula1
  # Toggles forwarding of local broadcast packets, the address of which depends on the ip/mask encoded in pki.cert
  drop_local_broadcast: false
  # Toggles forwarding of multicast packets
  drop_multicast: false
  # Sets the transmit queue length, if you notice lots of transmit drops on the tun it may help to raise this number. Default is 500
  tx_queue: 500
  # Default MTU for every packet, safe setting is (and the default) 1300 for internet based traffic
  mtu: 1300
  # Route based MTU overrides, you have known vpn ip paths that can support larger MTUs you can increase/decrease them here
  routes:
    #- mtu: 8800
    #  route: <IP_ADDRESS>/16
  # Unsafe routes allows you to route traffic over nebula to non-nebula nodes
  # Unsafe routes should be avoided unless you have hosts/services that cannot run nebula
  # NOTE: The nebula certificate of the "via" node *MUST* have the "route" defined as a subnet in its certificate
  unsafe_routes:
    #- route: <IP_ADDRESS>/24
    #  via: <IP_ADDRESS>
    #  mtu: 1300 #mtu will default to tun mtu if this option is not sepcified

# TODO
# Configure logging level
logging:
  # panic, fatal, error, warning, info, or debug. Default is info
  level: info
  # json or text formats currently available. Default is text
  format: text
  # Disable timestamp logging. useful when output is redirected to logging system that already adds timestamps. Default is false
  #disable_timestamp: true
  # timestamp format is specified in Go time format, see:
  #     https://golang.org/pkg/time/#pkg-constants
  # default when `format: json`: "2006-01-02T15:04:05Z07:00" (RFC3339)
  # default when `format: text`:
  #     when TTY attached: seconds since beginning of execution
  #     otherwise: "2006-01-02T15:04:05Z07:00" (RFC3339)
  # As an example, to log as RFC3339 with millisecond precision, set to:
  #timestamp_format: "2006-01-02T15:04:05.000Z07:00"

stats:
  #type: graphite
  #prefix: nebula
  #protocol: tcp
  #host: <IP_ADDRESS>:9999
  #interval: 10s

  type: prometheus
  listen: <IP_ADDRESS>:8099
  path: /metrics
  namespace: prometheusns
  subsystem: nebula
  interval: 10s

  # enables counter metrics for meta packets
  #   e.g.: `messages.tx.handshake`
  # NOTE: `message.{tx,rx}.recv_error` is always emitted
  #message_metrics: false

  # enables detailed counter metrics for lighthouse packets
  #   e.g.: `lighthouse.rx.HostQuery`
  #lighthouse_metrics: false

# Handshake Manger Settings
#handshakes:
  # Handshakes are sent to all known addresses at each interval with a linear backoff,
  # Wait try_interval after the 1st attempt, 2 * try_interval after the 2nd, etc, until the handshake is older than timeout
  # A 100ms interval with the default 10 retries will give a handshake 5.5 seconds to resolve before timing out
  #try_interval: 100ms
  #retries: 20
  # trigger_buffer is the size of the buffer channel for quickly sending handshakes
  # after receiving the response for lighthouse queries
  #trigger_buffer: 64

# Nebula security group configuration
firewall:
  conntrack:
    tcp_timeout: 12m
    udp_timeout: 3m
    default_timeout: 10m
    max_connections: 100000

  # The firewall is default deny. There is no way to write a deny rule.
  # Rules are comprised of a protocol, port, and one or more of host, group, or CIDR
  # Logical evaluation is roughly: port AND proto AND (ca_sha OR ca_name) AND (host OR group OR groups OR cidr)
  # - port: Takes `0` or `any` as any, a single number `80`, a range `200-901`, or `fragment` to match second and further fragments of fragmented packets (since there is no port available).
  #   code: same as port but makes more sense when talking about ICMP, TODO: this is not currently implemented in a way that works, use `any`
  #   proto: `any`, `tcp`, `udp`, or `icmp`
  #   host: `any` or a literal hostname, ie `test-host`
  #   group: `any` or a literal group name, ie `default-group`
  #   groups: Same as group but accepts a list of values. Multiple values are AND'd together and a certificate would have to contain all groups to pass
  #   cidr: a CIDR, `<IP_ADDRESS>/0` is any.
  #   ca_name: An issuing CA name
  #   ca_sha: An issuing CA shasum

  outbound:
    # Allow all outbound traffic from this node
    - port: any
      proto: any
      host: any

  inbound:
    # Allow icmp between any nebula hosts
    - port: any
      proto: icmp
      host: any

    # Allow tcp/443 from any host with BOTH laptop and home group
    - port: 443
      proto: tcp
      groups:
        - laptop
        - home

I have also allowed traffic on port 4242 on OCI console

Are you running a release or a build from master?

Are you running a release or a build from master?

I am running version 1.3.0 from release

Config looks fine, can you share the certificate dump for CA, node and lighthouse?
nebula-cert print -path somecert.crt

Sure
CA
NebulaCertificate {
	Details {
		Name: //redacted personal domain
		Ips: []
		Subnets: []
		Groups: []
		Not before: 2021-05-01 08:55:10 +0000 UTC
		Not After: 2022-05-01 08:55:10 +0000 UTC
		Is CA: true
		Issuer:
		Public key: 854c3fae22b1a2a24a957a3b09531e51349a7f3ad15b5ec71d2e1736189db81e
	}
	Fingerprint: d35b677482e51ece13de611c76e9d99134c9c87771b8b20e9bf51b4c6896d30c
	Signature: eac7f3358e6a8c637476e9613d32425fc0324bfa802d8b739862d6db0bb44225130d372cb58597b7b329c7963daa32694f2df8191007edfe24a3a1519628e60f
}

lighthouse
NebulaCertificate {
	Details {
		Name: oracle-vm
		Ips: [
			<IP_ADDRESS>/24
		]
		Subnets: []
		Groups: []
		Not before: 2021-05-01 08:55:14 +0000 UTC
		Not After: 2022-05-01 08:55:09 +0000 UTC
		Is CA: false
		Issuer: d35b677482e51ece13de611c76e9d99134c9c87771b8b20e9bf51b4c6896d30c
		Public key: 838f3ec1bd7f29548c376a0250ef57711443bc7fe1079141e054ef3f7c1e860b
	}
	Fingerprint: 745d89e4463c92373c122b77177bb5e83e1e65e8d80d39359b2e71dbf5240d35
	Signature: af1fa6e21b1669dc1c32cbe37422e19d6863e2df3738b7681b1ebecdf1e4118f79653252050aeef69692fcb8df7635ad49adf09570be99f2d188dbfc64614307
}

node
NebulaCertificate {
	Details {
		Name: raspi
		Ips: [
			<IP_ADDRESS>/24
		]
		Subnets: []
		Groups: []
		Not before: 2021-05-01 14:25:41 +0530 IST
		Not After: 2022-05-01 14:25:09 +0530 IST
		Is CA: false
		Issuer: d35b677482e51ece13de611c76e9d99134c9c87771b8b20e9bf51b4c6896d30c
		Public key: ccc1b34463de63f188bbd71f0340d48b82c827b17540e6a61dc6357a1e00422e
	}
	Fingerprint: 359bd78f1987d255190e75b268f8416c69a014a281131c889d6516847e79cd79
	Signature: cb51583ffbbbdd8d203c65a5cf6e7c95efcb441dca91cb1636add6c3ec4ca10737b3e32d87d4d40303287d883a166d58c66b330872da77cf437f81fb37b48b09
}

I would suggest cleaning up the comments from the config files so things are much easier to look at.
Anyways, I just noticed you had some entries in the remote_allow_list key. Take note of the comment in that specific section:

If all rules are "allow", the default will be "deny"

This basically denies pubIp from being allowed as a remote ip.

Yes! The remote_allow_list was the culprit in my case!
Thank you for helping


TeX commands visible in HTML output

Description
It looks like some of LaTeX formatting commands made it into the visible text:
\pdfcolInitStack
tcb@breakable

Archived output: https://web.archive.org/web/20240621062246/https://arxiv.org/html/2406.14550v1
(Optional:) Please add any files, screenshots, or other information here.
No response
(Required) What is this issue most closely related to? Select one.
Other
Internal issue ID
0d2c53f8-500c-44ce-840b-acba655ad517
Paper URL
https://arxiv.org/html/2406.14550v1
Browser
Chrome/<IP_ADDRESS>
Device Type
Desktop

I've just seen the error box at the top of the page saying these are known issues. My mistake.


Decommission eris.nixos.org

We want to retire this machine, and are replacing it with pluto.nixos.org.
Its services need to be migrated before that can happen:

[x] netboot
[x] rfc39
[x] prometheus
[x] grafana
[x] victoriametrics (nixos-metrics)

The earliest possible cancellation date is 28 February 2024. Renewal is likely monthly.

Configs deleted and contract cancelled.


Validate the latest cert-manager in Rancher server helm chart to latest

Currently we recommend to install cert-manager 1.7.1 (https://docs.ranchermanager.rancher.io/pages-for-subheaders/install-upgrade-on-a-kubernetes-cluster#4-install-cert-manager). cert-manager 1.7.1 is EOL; requesting eng validation for cert-manager in Rancher to see if it can be updated to 1.10.x (or higher). This will require an update to docs as well. See https://cert-manager.io/docs/installation/supported-releases/ for currently supported releases.
See also https://github.com/rancher/rancher/issues/36693 as a reference to the previous validation testing done on 1.7.1.
SURE-5786

Just to add a comment to this, with Rancher being validated to k8s 1.24 but cert manager 1.7.x only to 1.23. This effectively means that Rancher is only deploy-able to k8s 1.23 with cert-manager.
Rancher Support Matrix: https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-0/
Up to k8s 1.24
Upgrade Docs Recommending 1.7: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/upgrade-cert-manager
Cert Manager K8s support: https://cert-manager.io/docs/installation/supported-releases/
Where 1.7 is only supported up to 1.23

same issue here. would like to know to which version to upgrade.

same issue here. would like to know to which version to upgrade.

Not the official word here, but we pushed to 1.8 and tested reissuing, which worked for LetsEncrypt. We did not test renewal that may or may not be effected by lack of rotationPolicy in the Rancher/LetsEncrypt generated certs. Not sure about how the validity check works for letsencrypt, it may not yet be tied to rotationPolicy.
1.7.3 also worked charmingly on k3s 1.24 but again we have not tested renewal.

Still an issue.

Didn't see this earlier, we are completing via: https://github.com/rancher/rancher/issues/40880


ci: add release-notes step

:tada: This PR is included in version 0.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


HTML ID change: button-download-discovery-iso button ID is prefixed

To make it always unique.

Cc @cdvultur


[add-resource] New Plugin Studioeditor

Hi there.
Please take a look at the Studioeditor plugin for GRAV, a complex one...
I would like to add the Studioeditor plugin to the Grav Repository.
Here are the project details: Studioeditor
Thx.
u

This looks like an interseting plugin. However as it currently has an issue with Flex Objects, and Flex is a required plugin for admin, I cannot approve it.
The reaon is that people will enevitably come to the admin plugin and raise issues that the admin is broken.  You need to find a way to resolve your issue so that it works without any manual modification to Grav and the standard required plugins.
NOTE: if it has an issue with some other non-standard plugin, I would let it slide, but as it stands is evectively saying it's not compatible with a base Grav install unless you do these manual steps.  And you would only find that information if you went to your repo and read the README.

No problem at all, probably it's not even Studioeditor, smartypants shows a blueprint errror that may be the cause. Good job. Will keep you updated here about my findings. One question: Seems that you are the only person doing quality management, Grav needs a dedicated community manager and a team offering the quality checks... I exposed the problem, I'm quite sure you wouldn't even detected the problem without my hint...

Community help appreciated, as stated by @rhukster, the plugin is worth the effort and the community will benefit. Anybody out there?

Whoever wants to be invited as a colloaborator, even as an owner of the plugin, hands up. I'm getting far too old and I'm doing clean up now... Studioeditor is more than 6 years old... and I'm not really working with computers anymore.... I'm doing a last effort to publish things to the wild I've done over the years...

@rhukster: in fact, this plugin (or something similar) should be part of Admin... Would help to open up Grav for many people that feel insecure offering GRAV as a solution to companies, etc. I'll invite you too.

Problem is a flex-objects issue already open: Blueprints that extend default cause a memory overflow.

I've tested this error creating a new plugin to see if I can reproduce the error, answer is yes.

Ok, found a fix. Probably it's documented somewhere, to extend default blueprint via a plugin the extending blueprint shouldn't be named default.yaml, in my case renaming it to studioeditor.yaml the problems gone away, or you can use default.yaml in your plugin but in needs to be full-fledged. There may be other solutions but that's what I've figured out, all related to Types.php for Page in my case in the system core of GRAV.

I will publish v1.1.4 later which includes the fix the media resizer support as well

v1.1.4 published. Including fixes for the issues formerly mentioned in README. Please check again.

Cool plugin!
Definitely must be in Grav repo!

Published right now v1.1.7 as there was still a mention to problems with Flex Objects in the README file.

v1.1.8 released. Can we get this reviewed again?

v1.1.9 released with additional language sets, fixes for notices, an updated Markdown guide within the editor, etc. Would be nice to get some feedback these days. Thanks.

Traveling at the mo. Will check in this as soon as I have better access.

Finally found what's causing blueprint inheritance errors. Will update the issue for Flex Objects. v1.2.0 will include the inheritence fix which allows that inheritance change won't break from system over admin/flex/plugins to themes...

Summarized: You cannot approve before I publish v1.2.0 :-)

v1.2.0 released, includes improved bugfix for blueprint inheritance.

You've arrived? :-)

Will look again today.

Testing again in a fresh install with Admin, and it's got problems.. No Editor in view and translations missing?

Also, you probably should use the onAdminListContentEditors() event to have the contet editor show up in the list of editors the user can pick from (rather than forcing it as the default):
example from nextgen editor:
    public function onAdminListContentEditors($event)
    {
        $options = $event['options'];
        $options['nextgen-editor'] = 'NextGen Content Editor (WYSIWYM Editor)';
        $event['options']  = $options;
        return $event;
    }

here's some more logic from the onPluginsInitialize() method of the nextgen editor plugin:
            if (method_exists($user, 'getContentEditor')) {
                // Preferred 1.7+ FlexUsers approach
                $markdown_editor = $user->getContentEditor();
            } else {
                // Grav 1.6 compatibility
                $markdown_editor = $user->content_editor ?? 'default';
            }

            if (($this->configs['default_for_all'] && $markdown_editor === 'default') || $markdown_editor === 'nextgen-editor') {
                // Enable the main event we are interested in
                $this->enable([
                    'onAdminTwigTemplatePaths' => ['onAdminTwigTemplatePathsDefaultEditor', -10],
                ]);
            }
            ...

This basically allows the plugin to override the forms/fields/markdown/markdown.html.twig file to use your own (by adding it to twig template path before admin plugin) only when the user has the editor selected OR if you have enabled for all in the plugin configuration.

If you save, editor shows perfectly. That's not even strange as the plugin does not extend the new blueprint but I can add this behavior. Simply save as with any new page, that's it and you'll see the editor. Thx for your recommendations, will check/implement recommendations in 2.0 on which I started to work.
Right now the default blueprint approach is perfectly valid and at least for this version if I don't want to rewrite the whole plugin will be maintained as I would also need to overwrite the media uploader to make it work in conjunction with the editor, that's perfectly possible and transparent with the extending approach via blueprints. Will provide v1.2.1 which will include editor support for new files.

v1.2.1 released, includes fix for the editor display problem for newly created pages.
Please test again.

Same problem for me in 1.2.1

Now it’s me travelling 🤪Enviat des de el meu móvil...El 24 abr. 2024, a les 13:06, Andy Miller @.***> va escriure:
Same problem for me in 1.2.1
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

@rhukster, the solution is pure js as the editor did not initialize given that there's no upload field available for new pages before they've been saved for the first time. This said, you may have to clear the cache of your browser and of the GRAV instance for this reason.


point links on OWW to GitHub (for targets files and scripts)

Point links on OWW to GitHub (for targets files and scripts)

Done.


Fix golint issues

@Ghostbaby @soulseen @wangcanfengxs @bitsf @heww @chlins
Please help to fix the golint issue related to the code you're owning.
Check golint report: https://github.com/goharbor/harbor-operator/pull/440/checks?check_run_id=1863335336

not include goerr113 tracked by #465


By defensive with command and reader access due to issues with MySQL provider

Issue #10147

MySQL provider sometimes has null Parameters collection
MySQL provider sometimes throws when asking for records affected

Fix is to be defensive in our code and we will file issues on MySQL provider

/cc @Eilon

Good to go for the patch, but let's still take a closer look at why exactly this is happening.

Universe rel/2.0.3 has been updated. https://github.com/aspnet/Universe/commit/8c63660b15545d6c27eed521ae4d414e170da64b


Multiple ping got mixed on Windows 7

When I paralleled ping different ip on a windows 7 host, I found stats.PacketRecv got mixed, and some unreachable ip get a full PacketRecv

This should be fixed in the latest version of the go-ping library.
If you update and still see the issue, please open a new issue and provide steps for reproducing.


Telemetry Data from Icebreaker App

Does anyone have a dashboard or queries created for Icebreaker that will show how many active user's there are and how many pairs were created? Is there a way to see who was left out of the pairs if there is an odd number of users? Wanted to see if there was any guidance on how to do this.

Hi @teiselt96 ,
Thanks for highlighting the issue. For now it will be considered as enhancement and will plan it for future releases.

Hi @teiselt96 ,
We have already considered this as a backlog item. We will take this feature and implement it in the upcoming sprints.


Validation: enable additional type bool

Booleans are a common type one might want to have as metadata.
One has to keep in mind and test, that python implements booleans as numbers (https://stackoverflow.com/questions/37888620/comparing-boolean-and-int-using-isinstance)
print isinstance(True, (float, int))
True

So the function which checks the type should make sure, that onyo differentiates between these.
And, possibly more important, it should differentiate between False as a boolean and a string, to keep this information consistent along assets.

When implemented, the PR should also update the README to explain that the new type is available.


Function and System.Collections.ArrayList must Out-null

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Hello Powershell Teams,
I have a bug when I use System.Collections.ArrayList in a function. I must use out-null when I add a element to list
I write this function
function simplefunction
{
$collection = New-Object System.Collections.ArrayList
$collection.add("Toto")
return $collection
}
-> the result about simplefunction is
0
Toto
I must use out-null
function simplefunction
{
$collection = New-Object System.Collections.ArrayList
$collection.add("Toto")|out-null
return $collection
}
-> the result is now OK when I use this function
Toto
Kind Regards
Thierry
Expected behavior
Toto

Actual behavior
0
Toto

Error details
I must used out-null after add function in System.Collections.ArrayList object

Environment data
Microsoft Powershell 7.1.3

Visuals
No response

The output is part of the .NET behavior. PowerShell just echoes the return from the Add method.
https://github.com/microsoft/referencesource/blob/master/mscorlib/system/collections/arraylist.cs
        // Adds the given object to the end of this list. The size of the list is
        // increased by one. If required, the capacity of the list is doubled
        // before adding the new element.
        //
        public virtual int Add(Object value) {
            Contract.Ensures(Contract.Result<int>() >= 0);
            if (_size == _items.Length) EnsureCapacity(_size + 1);
            _items[_size] = value;
            _version++;
            return _size++;   // <----- This is where the element number in PowerShell comes from.
        }

The more efficient method of blocking the output is to use "$null =". It doesn't impact the Add(), prevents console output, and is faster than pipelining to Out-Null.
function simplefunction
{
   $collection = New-Object System.Collections.ArrayList
   $null = $collection.add("Toto")
   return $collection
}

You can also use a generic list which has a void Add method
$list = [System.Collections.Generic.List[Object]]::new()
$list.Add("foo")

The other benefit of a generic list is that you can explicitly set the type of the entries. The example above is set to allow Object which is essentially anything but say you wanted a list of strings then do [System.Collections.Generic.List[String]]::new().

Thank you for yours messages. I do that


war file has some problem

I put the war file to the directory og tomcat/webapps, but when i input the url http://localhost:8080/exhibitor-war-exhibitor-war-1.0 with chrome.Then i got a http 404 error,it says that the /exhibitor/v1/ui/index.html not found.why?

With Tomcat, if the WAR file is not named ROOT.war, then you have to prepend the war file name I believe.

The redirect is because of the default redirect in web.xml is taking "/" to redirect to "/exhibitor/v1/ui/index.html"
The two files in question are below:
https://github.com/Netflix/exhibitor/blob/master/exhibitor-standalone/src/main/resources/WEB-INF/web.xml
https://github.com/Netflix/exhibitor/blob/master/exhibitor-standalone/src/main/java/com/netflix/exhibitor/servlet/ExhibitorServletFilter.java
Either update it to your liking, or name the war file as ROOT.war. Or as a workaround, give the complete path to the html file that loads Exhibitor:
In your example above, the filename(root context) appears to be "exhibitor-war-exhibitor-war-1.0", so the direct url will be:
http://<IP_ADDRESS>:8080/exhibitor-war-exhibitor-war-1.0/exhibitor/v1/ui/index.html

Thanks!


Create iiitvadodara.ac.in

Official website: https://iiitvadodara.ac.in/
Programs: https://iiitvadodara.ac.in/academics_under_graduate.php
The hosted domain, and the domain that I'm requesting are the same

@SteakFisher lib/domains/in/ac/iiitvadodara: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@SteakFisher First stage of verification passed, official domain for Indian Institute Of Information Technology, Vadodara is iiitvadodara.ac.in as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@SteakFisher Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


Adjust Assemble to do one pass using JS files for playground

If we move to JS files for components can probably get back to one pass and allow more complicated examples in the playground.
Based on discussion with @chrisprice

Fixed (in a manner of speaking) by 2bf4206de72876ee4b4044f2ae88f691c54400eb


Don't barf if requirement has no url attribute

Without this, I was getting (with pip 6.1.0.dev0):
[marca@marca-mac2 profilesvc]$ cat reqs2.txt
ipython
pygments
pyramid

[marca@marca-mac2 profilesvc]$ caniusepython3 --requirements reqs2.txt
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/2.7/bin/caniusepython3", line 9, in <module>
    load_entry_point('caniusepython3==3.0.0', 'console_scripts', 'caniusepython3')()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/caniusepython3/__main__.py", line 159, in main
    check(projects_from_cli(args))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/caniusepython3/__main__.py", line 86, in projects_from_cli
    projects.extend(projects_from_requirements(parsed.requirements))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/caniusepython3/__main__.py", line 46, in projects_from_requirements
    elif req.url and req.url.startswith('file:'):
AttributeError: 'InstallRequirement' object has no attribute 'url'

I believe this is because pip changed the name of the attribute from url to link (see https://github.com/pypa/pip/pull/2280).
Cc: @xavfernandez

@brettcannon: Both good points, although when I looked at changing it, I thought that we could do even better by extracting 2 functions:
def req_has_file_link(req):
    url = getattr(req, 'url', None)
    if url and is_file_link(url):
        return True
    link = getattr(req, 'link', None)
    if link and is_file_link(link):
        return True

def is_file_link(link):
    if link.url.lower().startswith('file:'):
        return True
    if getattr(link, 'scheme', None) == 'file':
        return True

Without those, the if statement gets a bit unwieldy and I am not a fan of multi-line if statements.

Oops. Fixing...

OK, fixed. Travis CI passing.

Hopefully, third time is a charm...

$ tox
...
  py26: commands succeeded
  py27: commands succeeded
  py32: commands succeeded
  py33: commands succeeded
  py34: commands succeeded
  pypy: commands succeeded
  congratulations :)
>>> elapsed time 23m47s

One minor change and I will merge the PR!

Done.
You've been totally cool and polite with all the changes you've requested!

Thanks!


pkg_dependencies installed late

Looking at: picoCTF-2018-problems-af/packaged-problems/forensics/meta-material, this tries to install libimage-exiftool-perl using the following in problem.json:
"pkg_dependencies" : ["libimage-exiftool-perl"]
Unfortunately, this dependency isn't installed until later, so if you do:
sudo shell_manager package .
sudo dpkg -i picoctf-truly-an-artist-p1-0-0.deb
dpkg fails, because libimage-exiftool-perl isn't installed yet.
sudo apt-get install -f
will fix this, but it would be nice to have this happen more automatically.

After some discussion within the tech team, it seems the root cause of this problem is the use of dpkg -i, which was not designed to handle dependencies. Since we have upgraded the platform OS to Ubuntu 16.04, the newer apt install command in it can conveniently take a deb filename and it should take care of the dependencies:
https://unix.stackexchange.com/questions/159094/how-to-install-a-deb-file-by-dpkg-i-or-by-apt
So perhaps the solution to this issue is to change the commands to:
sudo shell_manager package .
sudo apt install picoctf-truly-an-artist-p1-0-0.deb

Do you think that would work?

Yes, I think that would be fine. As a future enhancement, it would be nice to have a shell_manager package_and_deploy, because I never really want to just package.

Updated title to reflect remaining enhancement task


Cow occasionally checks out the wrong branches

Occasionally cow checkout the wrong branch of some module for no apparent reason. When I did the 4.7.0-rc1 release I got the wrong branch of framework and admin. All the other modules were using the correct branches.
Until we figure out what is going on we can use this simple bash script to figure what branch is module is on.
#!/usr/bin/env bash
# Run this script from vendor/silverstripe
for f in *; do
    if [ -d "$f" ]; then
        BRANCH=`(cd $f; git rev-parse --abbrev-ref HEAD)`
        printf "%-20s   %s\n" $f $BRANCH
    fi
done

This hasn't been a problem for the last however many releases - seems to be fixed


Deploy Errors

I followed the Gatsby guide for deploying to gh-pages, but it did not work.

I get many errors about files not being found even though they are there in the final directory named "public".

Looks like it is not using the prex path even when I enter a prefixPath in the config.

please sir, is there anyone who can think of to be done?

nevermind,
The real issue was that "pathPrefix" needed to be at the top level of gatsby-config.js, not nested within siteMetadata. This is probably just an inconsistency with new versions of gatsby, and I should probably let the maintainer of gatsby starter hero blog know that his template is not correct syntax anymore...

oh, this is gatsby starter hero blog...


console warning in iOS

After placing a pager in Nativescript 5.2 angular application, in iOS, I got:
CONSOLE WARN file:///app/tns_modules/nativescript-pager/pager.js:435:56: Class "UICollectionDelegateImpl" already implements the "UIScrollViewDelegate" protocol.

I got the same message, and the app crashes. I'm using NS 5.2

It should be working on the latest

@triniwiz along with that error, when I turned pages, they sometimes got stuck in the middle. Will the fix solve this as well?

@racknoris a gif would be nice to see the behavior


Add Web API and handle responder identity

Hi, this is a first go at using the Slack Web API to allow for responders to define identities (custom name and emoji/thumbnails) they will use when sending messages. There are some limits based on spotty (buggy) areas of the Slack API but for most things it works well. Additionally, for emotes, since the RTC doesn't support message formatting, I've switched out the use of it for the Web API.
There is an accompanying changeset to the base Hedwig package as well.

Hi @rjanja,
All of these changes seem like they would be better suited else where. The adapter for Slack is designed to send messages over the WebSocket connection, not over HTTP.
You could move the HTTP functionality into its own package and use it from within your responders, instead of sending the message via the Hedwig.Responder.{send,reply,emote} functions.
I would be interested in a PR that brings in the WebAPI module similar to how you have in this PR. If that sounds like something you would be interested in that would be awesome!
If you do decide to send a PR for that, please do not replace :hackney with HTTPoison.
Thank you!

Hi @scrogson, thanks for the feedback and for all your work on the hedwig projects.
The WebSocket (RTM) API lacks message formatting support which makes it less useful and interesting to us. That said, there may be merit to having the Web API fully supported by a separate adapter instead of intermingling both APIs as I have done.
Are you suggesting that the Web API might fit within this adapter but be called directly from individual responders? I've tried to keep everything separate and independent thus far, but I do see a need to access the Web API directly instead of injecting message properties to trigger those calls (for things like adding reactions to messages or working with message attachments).
I'm happy to contribute back to this project, and I'm hoping our goals of easily integrating more advanced Slack features into bots will fit within the aims of your project. I'm open to suggestions and as much feedback as you care to provide; this has so far been an excellent learning experience.
I did struggle with the decision to replace :hackney. It wasn't a necessity but a preference, so that's not a big deal to leave as-is.
One thing that wasn't present in this PR but I can see value in is documenting the shortcomings of the APIs (both Web and RTM). Some things, like the emote (me_message) not working as intended are not obvious until after doing a bit of research. I'm also happy to help with this effort.


wlfreerdp shows distorted, unusable screen

Describe the bug
I am attempting to connect to an Windows 10 machine over RDP, on Wayland. When I use wlfreerdp with basic options (hostname and user/pass parameters), the result is unusable (see screenshot below). I've tried setting scaling options, explicit resolution, etc, with no results.
I am running wlfreerdp from a GNOME 3.36 session with fractional scaling enabled.
When I run xfreerdp, I do not experience this issue. However, xfreerdp is sub-optimal, due to distortion issues with xwayland when fractional scaling is enabled.
When I run in remmina, I do not experience this particular issue (although I do run into an issue where its scaling gets funky when a full-screen remmina window loses focus).
I've experienced this issue with either or two monitors connected.
To Reproduce
Steps to reproduce the behavior:

Use wlfreerdp with minimal configuration
Observe result

Expected behavior
RDP session opens as expected.
Actual behavior
RDP session is distorted and unusable.
Screenshots

Application details

Version of FreeRDP: 2.0.0-rc4
Command line used: wlfreerdp /v:<host> /u:<user> /d:<domain>
output of /buildconfig
OS version connecting to: Windows 10
If available the log output from a run with /log-level:trace

Desktop (please complete the following information):

OS: Arch Linux

This appears to be an issue when fractional scaling is enabled in Wayland (i.e. gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']").
When I turned that setting off (with GNOME 200% scaling still enabled), the RDP window opened as expected, initially. It died shortly after with the following output:
[18:43:25:987] [123412:123412] [INFO][com.freerdp.gdi] - Local framebuffer format  PIXEL_FORMAT_BGRA32
[18:43:25:987] [123412:123412] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGR24
[18:43:31:850] [123412:123422] [ERROR][com.freerdp.channels.cliprdr.client] - context->custom not set!
[18:43:31:850] [123412:123422] [ERROR][com.freerdp.channels.cliprdr.client] - cliprdr_process_general_capability failed with error 1359!
[18:43:31:850] [123412:123422] [ERROR][com.freerdp.channels.cliprdr.client] - cliprdr_process_clip_caps failed with error 1359!
[18:43:31:850] [123412:123422] [ERROR][com.freerdp.channels.cliprdr.client] - cliprdr_order_recv failed with error 1359!
[18:43:31:851] [123412:123412] [ERROR][com.freerdp.core] - cliprdr_virtual_channel_client_thread reported an error. Error was 1359
[18:43:31:851] [123412:123412] [ERROR][com.freerdp.core] - checkChannelErrorEvent() failed - 0
Failed to check FreeRDP file descriptor

Not sure if this is related, or if I should open a separate issue for this.

Looks like we have something to handle with our wayland impl to be informed of fractional scaling.

The second issue appears to be unrelated then? Should I open an issue for it as well?

@JacobHenner for the clipboard & wayland stuff better update to master ;)


Site title line height is incorrect

Currently the line height is "1rem." Line height should not use a unit, and the correct line height is 1.142 (sorry it's not a nice round number @Jura but this matches the specs in Figma).
Current implementation looks like this:

@mrelevo , please verify

Verified in dev

verified in storybook and Drupal


Changes ScheduleRunnerPlugin RunMode::Loop to run on fixed interval

Calculates the execution time of the 'scheduler.run' and subtracts it from the wait time to make loop run at a more fixed interval.
If execution time is greater than wait time do not wait.

A PR enforcing formatting just got though, you don't need to change anything (PR #234 just need to be merged before yours), sorry about that


Restored the embedded reduction factor to bruteforce.

This change was present on the GitLab branch but missed out during the transition to GitHub.
This change is intentionally as close as possible to the patch on GitLab.
Fixes #1045

Trying to find EMBEDDED_REDUCTION_FACTOR  in gitlab to compare. Was it on a particular branch? Only seeing search hits in the conversions tests

@kpet I've created the helper functions and used them in locations that this change requires.

I've pushed a change that simply renames the get* functions to set* instead.

I've pushed a change that simply renames the get* functions to set* instead.


Issue with JSON

Hi,
The dashboard is very useful and all the functions used to work. However, now there is an error that says that there are extra characters at the end of JSON input:

Any idea how it can be fixed?

what specifically is this report?

Hi,
I created the same report as yours (based on your great pbix file). Currently in both reports I see the same error.
So it is getting users entitlements (so users vs.  license type, etc)  from DevOps using query and following source address:
= Json.Document(Web.Contents("https://vsaex.dev.azure.com/" & Organization  & "/_apis/userentitlements?api-version=4.1-preview.1"))
What is interesting, I entered this address in the web browser, copied JSON to the file, opened the JSON file in PowerBI and there were no issues then loading data to PowerBi.
Maybe there is something wrong with the authorization?
Jacek

However, this error appears just after uploading your file and without changing anything (like for example Organization parameter):

I can't recall such error in the past. The dashboard was working very well many months.

@JackPlacek I'm closing the issue after our talk. Thanks for your feedback.
Resolution: create PAT and connect report using our user and PAT.


Readonly workspaces should show errors on edits other than types

Mentioned this in another comment, but readonly workspaces should show errors on deletions and cut/paste at the least, and ideally all edit commands (transpose, insert line above, join lines, etc.)

#52573

No. This is just how read only editors behave. We do not throw errors to the users face, but instead choose to disable those actions instead.
Closing as will not fix.
If there is a particular action that you feel shuold throw an error, please file an issue to me with that exact action in mind - thanks!


Kuch ni

Type: Feature Request
Bs Bhai Video call add krdena
VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T06:00:27.244Z)
OS version: Darwin arm64 22.3.0
Modes:

/duplicate of #194382

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Introduce internal FerretDB ID for documents

What should be done?
To ensure that updates and deletes by that internal ID are exact. It should not be visible to the user.
Where?
TBD
Definition of Done
TBD

all handlers updated;
unit tests added/updated;
integration/compatibility tests added/updated;
spot refactorings done;
user documentation updated or an issue to create documentation created;
something else?

Will this ID be stored in the DB? If so, is this something sqlite backend is aware of but not exposed to handler?


update

remove redundant dependency

merge dis

merge dis x2

Wow, I have not checked this in a long time.
I merged it, thanks for the update.

hi, plz check the config.admin, i already put the SteamID64 and still the error continues..
Stack: ReferenceError: admin is not defined
at SteamUser. (C:\Users\TioDavi\Desktop\tf2-autoprice-bot-master\daemon_shop.js:664:35)
at emitTwo (events.js:126:13)
at SteamUser.emit (events.js:214:7)
at SteamUser._emitIdEvent (C:\Users\TioDavi\node_modules\steam-user\components\utility.js:29:12)
at SteamUser._handlers.(anonymous function) (C:\Users\TioDavi\node_modules\steam-user\components\chat.js:281:9)
at SteamUser._handleMessage (C:\Users\TioDavi\node_modules\steam-user\components\messages.js:249:30)
at emitThree (events.js:136:13)
at CMClient.emit (events.js:217:7)
at CMClient._netMsgReceived (C:\Users\TioDavi\node_modules\steam-client\lib\cm_client.js:323:8)
at CMClient.handlers.(anonymous function) (C:\Users\TioDavi\node_modules\steam-client\lib\cm_client.js:603:8)
EXIT


add gRPC support

I have not tested the implementation yet because I am not at home at the moment, but I wanted you to be able to have a first look at it.
For logging, gRPC has two options as far as I know: zap and logrus. I have been working with logrus for the past few weeks and decided in favour for that. If you want it changed, please let me know.
Also, I do not distinguish between rest and grpc in server mode, I only try to additionally listen to the grpc port and log if that fails, but still continue listening on the http port. Maybe it is better to have a separate grpc mode? (still, it is server mode, so...)
Last but not least, I'm afraid I have a different formatter configured, so additional stuff may have changed (i.e. I noticed changes in imports). If you want me to revert those changes, let me know.
Greetings, Ann-Katrin
PS: Information on setting up the grpc environment in go: https://grpc.io/docs/quickstart/go/
Running go generate grpc_server/gen.go will update the protobuf code after changing the proto file

Looks good! Thanks for your work and I hope your home automation goes well!
Cheers,
// Erik


Online score storage

It'd be nice to have an online score storage. After the player finishes the game, he could have a choose whether to store his high score in either offline or online score storage (it should be fully optional I think).
I think that the score should be encrypted or hashed with hash of the current game level pack (and maybe game code itself), so we can check it on server. It will not be completely safe, but at least it wouldn't be deadly simple to hack and send fraud score to our server.
I think it would be nice and consistent to hack a server with common lisp, but if we want a more familiar environment, we can make something with Clojure.
The server could have a web interface and/or a client could show a top score list somewhere. I would like to discuss these details and factor that to a distinct tasks (and maybe even another project). The client-server API of course should be deadly simple.
Note that we also have some plans to implement multiplayer in future: #37.

Nice idea! But as discussed on the stream, this is not high priority right now.
Also, I think it's possible to implement the server side on Emacs Lisp. :) So we should consider this language as an option along with Clojure and CL.

Hm, and how could it be executed then? Emacs on server? Nice :)

@ForNeVeR http://www.gnu.org/software/emacs/manual/html_node/elisp/Batch-Mode.html

Please note that aside the main functionality (e.g. score storage) there are some additional features I mentioned (such as a web interface) that may be extremely difficult to implement with such a... strange platform for web servers.
And if elisp solution will require some additional software such as nginx or lighttpd or some CGI gateway - that'll create a big problem for portability. And personally I wouldn't afford such hardly portable solution.

http://nicferrier.github.io/elnode/

Elnode is a non-blocking IO webserver written entirely in EmacsLisp. It’s like an EmacsLisp version of node.js.

Hmm, okay then. It seems like a reasonable idea now.

Not questioning this issue anymore. Hence removing the question label. :)


Fonts & Images 404 Error with themes fixed

Fonts & Images 404 Error with themes fixed

Hello @Dfmarulanda. Thanks for the pull request. Can you give us a little more information about your environment? I'd like to get to understand better why these directory paths aren't working for you.

@Dfmarulanda any update on this? If not we'll close it soon

Closing since there isn't any responses to the questions.


feature: update cpu arch apis

这个 PR 实现什么功能/修复什么问题:
feature: update cpu arch apis

是否需要 backport 到之前的 release 分支:
None
/area region glance
/cc @swordqiu @zexi

Codecov Report

Merging #8828 (80463f8) into master (a3f1f77) will increase coverage by 11.91%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #8828       +/-   ##
===========================================
+ Coverage    5.92%   17.84%   +11.91%
===========================================
  Files         818       88      -730
  Lines      127432     8848   -118584
===========================================
- Hits         7553     1579     -5974
+ Misses     119201     7096   -112105
+ Partials      678      173      -505

Flag
Coverage Δ

aFlag
17.84% <ø> (+11.91%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/compute/models/baremetalagents.go

pkg/cloudcommon/db/adminsharablevirtual.go

pkg/mcclient/options/dnsrecords.go

pkg/mcclient/options/k8s/base.go

pkg/keystone/models/serviceresource.go

pkg/compute/models/loadbalancercertificates.go

pkg/hostman/system_service/host_deployer.go

pkg/mcclient/options/loadbalanceracls.go

pkg/cloudcommon/cronman/cronman.go

pkg/compute/regiondrivers/aliyun.go

... and 714 more

Continue to review full report at Codecov.

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

/lgtm
/approve


[Communication - Calling] Cloud recording state is not accurate for participants who join a call with recording already active

Package Name: @azure/communication-calling
Package Version: 1.22.3
Operating system: Windows
browser

name/version: Chrome 122.0.6261.95

Describe the bug
Participants are not able to retrieve accurate cloud recording state if they join a call after a cloud recording has already been started.
To Reproduce
Use the add-1-on-1-voice-calling sample, and do the bare minimum to add "manage call recording on the client" and "add a participant to a call" functionality.
Steps to reproduce the behavior:

Establish a 1:1 call
Get the recording feature API object and inspect isRecordingActive property. Property is false, as expected.
Determine the Server Call ID and start a cloud recording using call automation.
Inspect isRecordingActive property. Property is true, as expected.
Add a new participant to the call.
For the new participant, get the recording feature API object and inspect isRecordingActive property.

Expected behavior
isRecordingActive property is true.
Actual behavior
isRecordingActive property is false. The recording feature API object does not contain accurate recording state.
Additional context
This is actually reproducible for any participant, depending on when the recording feature API object is retrieved from the call instance.
My expectation here is: regardless of when the recording feature API object is retrieved from the call instance, it will be up to date with the current cloud recording state for the call.

Any updates on this issue?
It is very concerning since the new participants will not know if the call is being recorded or not and therefore, will not be properly notified. This is a requirement for ethical software development and possibly by law (https://learn.microsoft.com/en-us/azure/communication-services/concepts/voice-video-calling/call-recording#regulatory-and-privacy-concerns).

@lsbrettjewell  I am unable to repro this issue, recording state is for the call not per participant, what does the Step 6 means in the participant  context?

Let me see if I can clarify. I am still reproducing this in 1.24.1.
First, how can we determine the recording state on the client side? According to the documentation:
// get the recording features' API object from the call instance
const callRecordingApi = call.feature(Features.Recording);
// inspect the isRecordingActive property of callRecordingApi
const isRecordingActive = callRecordingApi.isRecordingActive;

Reproduction steps:

Join a call where a cloud recording is already active.
Get the recording features' API object and inspect the isRecordingActive property.

Expected behavior:
isRecordingActive property is true
Actual behavior:
isRecordingActive property is false!

Thanks @lsbrettjewell, I understand the scenario now.

Hi @lsbrettjewell,
We have resolved this issue. Please use any packages published on 5/30/2024 (1.26.1-beta.1, 1.25.3-beta.1, 1.24.3-beta.1, 1.25.1 and 1.24.4). Can we close this issue?


[ZEPPELIN-3448] Bump up version of org.scala-lang:scala-library

What is this PR for?
This is to upgrade the package org.scala-lang:scala-library to 2.11.12
What type of PR is it?
[Improvement]
What is the Jira issue?

ZEPPELIN-3448

Questions:

Does the licenses files need an update? N?A
Is there breaking changes for older versions? N?A
Does this needs documentation? N?A

I'll close this for now.