text:
🐛 BUG: WINDOWS nebula can't find the key from .yaml path

What version of nebula are you using? (nebula -version)
1.9.4
What operating system are you using?
Windows amd
Describe the Bug
I can't make nebula recognize the cert I just create. I used nebula-cert with the tutorial to create cert and the administration cert too.
Just as a side note everything work on my linux on the first try and I even tried to import the certificate that I created on my linux but nothing work. I tried with elevated and normal command. I installed Windows OS 3 days ago.
I tried the different pathname :
"C:/nebula_asus/ca.crt"
'C:/nebula_asus/ca.crt'
'C:\nebula_asus\ca.crt'
"C:\nebula_asus\ca.crt"
I would appreciate any help
Logs from affected hosts
C:\nebula_asus>nebula.exe -config "C:/nebula_asus/config.yaml"
failed to load config: yaml: line 21: did not find expected key

Config files from affected hosts
# 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: C:/nebula_asus/ca.crt
    cert: C:/nebula_asus/host.crt
    key: C:/nebula_asus/host.key
    # blocklist is a list of certificate fingerprints that we will refuse to talk to
    #blocklist:
    #  - c99d4e650533b92061b09918e838a5a0a6aaee21eed1d12fd937682865936c72
    # disconnect_invalid is a toggle to force a client to be disconnected if the certificate is expired or invalid.
    #disconnect_invalid: true

  # 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 192.168.100.1 and has the real ip address of 100.64.22.11 and runs on port 4242:

  static_host_map:
    "192.168.165.1": ["100.64.22.11:4242"]

  # The static_map config stanza can be used to configure how the static_host_map behaves.
  #static_map:
    # cadence determines how frequently DNS is re-queried for updated IP addresses when a static_host_map entry contains
    # a DNS name.
    #cadence: 30s

    # network determines the type of IP addresses to ask the DNS server for. The default is "ip4" because nodes typically
    # do not know their public IPv4 address. Connecting to the Lighthouse via IPv4 allows the Lighthouse to detect the
    # public address. Other valid options are "ip6" and "ip" (returns both.)
    #network: ip4

    # lookup_timeout is the DNS query timeout.
    #lookup_timeout: 250ms

  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: 0.0.0.0
      #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:
      - "192.168.165.1"

    # 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" IPv4 rules are present, then you MUST set a rule for "0.0.0.0/0" as
    # the default. Similarly if both "allow" and "deny" IPv6 rules are present,
    # then you MUST set a rule for "::/0" as the default.
    #remote_allow_list:
      # Example to block IPs from this subnet from being used for remote IPs.
      #"172.16.0.0/12": false

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

    # EXPERIMENTAL: This option may change or disappear in the future.
    # Optionally allows the definition of remote_allow_list blocks
    # specific to an inside VPN IP CIDR.
    #remote_allow_ranges:
      # This rule would only allow only private IPs for this VPN range
      #"10.42.42.0/24":
        #"192.168.0.0/16": 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.
      #"10.0.0.0/8": true

    # advertise_addrs are routable addresses that will be included along with discovered addresses to report to the
    # lighthouse, the format is "ip:port". `port` can be `0`, in which case the actual listening port will be used in its
    # place, useful if `listen.port` is set to 0.
    # This option is mainly useful when there are static ip addresses the host can be reached at that nebula can not
    # typically discover on its own. Examples being port forwarding or multiple paths to the internet.
    #advertise_addrs:
      #- "1.1.1.1:4242"
      #- "1.2.3.4:0" # port will be replaced with the real listening port

    # EXPERIMENTAL: This option may change or disappear in the future.
    # This setting allows us to "guess" what the remote might be for a host
    # while we wait for the lighthouse response.
    #calculated_remotes:
      # For any Nebula IPs in 10.0.10.0/24, this will apply the mask and add
      # the calculated IP as an initial remote (while we wait for the response
      # from the lighthouse). Both CIDRs must have the same mask size.
      # For example, Nebula IP 10.0.10.123 will have a calculated remote of
      # 192.168.1.123
      #10.0.10.0/24:
        #- mask: 192.168.1.0/24
        #  port: 4242

  # 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: 0.0.0.0
    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
    # By default, Nebula replies to packets it has no tunnel for with a "recv_error" packet. This packet helps speed up reconnection
    # in the case that Nebula on either side did not shut down cleanly. This response can be abused as a way to discover if Nebula is running
    # on a host though. This option lets you configure if you want to send "recv_error" packets always, never, or only to private network remotes.
    # valid values: always, never, private
    # This setting is reloadable.
    #send_recv_error: always

  # 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.
  # This option is only supported on Linux.
  #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.
    #delay: 1s

    # set the delay before attempting punchy.respond. Default is 5 seconds. respond must be true to take effect.
    #respond_delay: 5s

  # 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: aes

  # Preferred ranges is used to define a hint about the local network ranges, which speeds up discovering the fastest
  # path to a network adjacent nebula node.
  # This setting is reloadable.
  #preferred_ranges: ["172.16.0.0/24"]

  # sshd can expose informational and administrative functions via ssh. This can expose informational and administrative
  # functions, and allows manual tweaking of various network settings when debugging or testing.
  #sshd:
    # Toggles the feature
    #enabled: true
    # Host and port to listen on, port 22 is not allowed for your safety
    #listen: 127.0.0.1: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
    # Authorized users and their public keys
    #authorized_users:
      #- user: steeeeve
        # keys can be an array of strings or single string
        #keys:
          #- "ssh public key string"
    # Trusted SSH CA public keys. These are the public keys of the CAs that are allowed to sign SSH keys for access.
    #trusted_cas:
      #- "ssh public key string"

  # EXPERIMENTAL: relay support for networks that can't establish direct connections.
  relay:
    # Relays are a list of Nebula IP's that peers can use to relay packets to me.
    # IPs in this list must have am_relay set to true in their configs, otherwise
    # they will reject relay requests.
    #relays:
      #- 192.168.100.1
      #- <other Nebula VPN IPs of hosts used as relays to access me>
    # Set am_relay to true to permit other hosts to list my IP in their relays config. Default false.
    am_relay: false
    # Set use_relays to false to prevent this instance from attempting to establish connections through relays.
    # default true
    use_relays: true

  # 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. If not set, a default will be chosen by the OS.
    # For macOS: if set, must be in the form `utun[0-9]+`.
    # For NetBSD: Required to be set, must be in the form `tun[0-9]+`
    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: 10.0.0.0/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
    # `mtu`: will default to tun mtu if this option is not specified
    # `metric`: will default to 0 if this option is not specified
    # `install`: will default to true, controls whether this route is installed in the systems routing table.
    # This setting is reloadable.
    unsafe_routes:
      #- route: 172.16.1.0/24
      #  via: 192.168.100.99
      #  mtu: 1300
      #  metric: 100
      #  install: true

    # On linux only, set to true to manage unsafe routes directly on the system route table with gateway routes instead of
    # in nebula configuration files. Default false, not reloadable.
    #use_system_route_table: false

  # TODO
  # Configure logging level
  logging:
    # panic, fatal, error, warning, info, or debug. Default is info and is reloadable.
    #NOTE: Debug mode can log remotely controlled/untrusted data which can quickly fill a disk in some
    # scenarios. Debug logging is also CPU intensive and will decrease performance overall.
    # Only enable debug logging while actively investigating an issue.
    level: debug
    # 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: 127.0.0.1:9999
    #interval: 10s

    #type: prometheus
    #listen: 127.0.0.1:8080
    #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 Manager 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

    # query_buffer is the size of the buffer channel for querying lighthouses
    #query_buffer: 64

    # 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:
    # Action to take when a packet is not allowed by the firewall rules.
    # Can be one of:
    #   `drop` (default): silently drop the packet.
    #   `reject`: send a reject reply.
    #     - For TCP, this will be a RST "Connection Reset" packet.
    #     - For other protocols, this will be an ICMP port unreachable packet.
    outbound_action: drop
    inbound_action: drop

    # Controls the default value for local_cidr. Default is true, will be deprecated after v1.9 and defaulted to false.
    # This setting only affects nebula hosts with subnets encoded in their certificate. A nebula host acting as an
    # unsafe router with `default_local_cidr_any: true` will expose their unsafe routes to every inbound rule regardless
    # of the actual destination for the packet. Setting this to false requires each inbound rule to contain a `local_cidr`
    # if the intention is to allow traffic to flow to an unsafe route.
    #default_local_cidr_any: false

    conntrack:
      tcp_timeout: 12m
      udp_timeout: 3m
      default_timeout: 10m

    # 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) AND (local 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 remote CIDR, `0.0.0.0/0` is any.
    #   local_cidr: a local CIDR, `0.0.0.0/0` is any. This could be used to filter destinations when using unsafe_routes.
    #      Default is `any` unless the certificate contains subnets and then the default is the ip issued in the certificate
    #      if `default_local_cidr_any` is false, otherwise its `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

      # Expose a subnet (unsafe route) to hosts with the group remote_client
      # This example assume you have a subnet of 192.168.100.1/24 or larger encoded in the certificate
      - port: 8080
        proto: tcp
        group: remote_client
        local_cidr: 192.168.100.1/24

Yaml is probably upset about the : character in your path. Try quoting the strings like this:
pki:
    # The CAs that are accepted by this node. Must contain one or more certificates created by 'nebula-cert ca'
    ca: "C:/nebula_asus/ca.crt"
    cert: "C:/nebula_asus/host.crt"
    key: "C:/nebula_asus/host.key"

Thanks for your quick answer ! unfortunatly I already tried the following :
"C:/nebula_asus/ca.crt"
'C:/nebula_asus/ca.crt'
'C:\nebula_asus\ca.crt'
"C:\nebula_asus\ca.crt"
(On the three line ca cert and key)
pki:
    # The CAs that are accepted by this node. Must contain one or more certificates created by 'nebula-cert ca'
    ca: "C:/nebula_asus/ca.crt"
    cert: "C:/nebula_asus/host.crt"
    key: "C:/nebula_asus/host.key"

Oh wow sorry, quite the reading comprehension failure on my part.
I think we were both misled by the word key in the error Nebula returned. Your problem has nothing to do the PKI block thankfully. The issues begin after it, on line 21.
The key static_host_map: is a top-level item, and needs to not be indented. It looks like all of your config has been jammed under the pki key.

Oh my god, I feel so dumb on this one... I curl directly the file on my linux so I didn't had any issue, and copy and paste on windows...
I miss the three hours I spent this afternoon 😵
Thank you so much, issue solved

repo: slackhq/nebula


text:
SSLWantReadError not available until python 2.7.9

SSLWantReadError, which is used in the most recent commit 42bfde00 is not available until python 2.7.9, released just over five months ago. Did you intend to limit slackclient's use to versions 2.7.9 and greater?
If so, it should be documented somewhere.

cc @zoni

Doh! My bad, sorry. #30 should take care of this.

Thanks @zoni I've merged your fix into my fork, python-slackclient doesn't seem to update very quickly

source: gharchive/issue

authors: llimllib zoni

repo: slackhq/python-slackclient

license: mit

license_type: permissive

license_source: bigquery


text:
Implement search kudos by username case-insensitive

This probably means comparing everything in lowercase
https://medium.com/open-graphql/implementing-search-in-graphql-11d5f71f179

repo: slashkudos/kudos-web

license_source: github-api


text:
fastdtw and dtw giving different answers.

timeseries1.xlsx
timeseries2.xlsx
i tried fastdtw and dtw on the two timeseries that I have uploaded.Both are giving different answers. Should it give the same answer or am I missing out something?

@harsh244 It's good practice to explain briefly why the issue is no longer relevant before closing it.

After reading the paper found out that it depends a lot on how we set the radius parameter so fasdtw may not always give us the best path as it is based on a lot of approximations ,the more we set the radius as the more closer the answer of our fasdtw to dtw ,at radius=(length of timeseries) ,fastdtw becomes dtw .

repo: slaypni/fastdtw


text:
{at:} animation synchronization does not work

Describe the bug
In a certain setup, the slide animation sync in code blocks does not work, they work sequentially instead
To Reproduce
# BTW I use jOOQ

```sql {1|2|3|all} {at:0}
SELECT AUTHOR_ID, COUNT(*)
FROM BOOK
GROUP BY AUTHOR_ID
```

```kotlin {1|2|3-4|all}  {at:0}
create.select(BOOK.AUTHOR_ID, count())
      .from(BOOK)
      .groupBy(BOOK.AUTHOR_ID)
      .fetch();
```

Desktop (please complete the following information):

OS: EndeavourOS Linux x86_64
Browser: Vivaldi	6.5.3206.53 (Stable channel) stable (64-bit
Slidev version: 0.46.1

Duplicates #1246

repo: slidevjs/slidev

license: MIT


text:
#14 Standardize gmelius endpoint

Pull request for the topic https://github.com/slingr-stack/gmelius-endpoint/issues/14 created by @agreggio-slingr
What does it do?
This ticket implements the use of slingr-helpgen, whereby it modifies existing functions, adds basic functions and step flows.
How to test it?
Make calls from the platform for example using the console using the information provided in the documentation.
Implementation notes
Create new version of the endpoint, it is not compatible with previous versions.
Implementation notes
Create a new tags changing the major version and deploy to the platform.

#approve

Version for implementation tag created: v2.2.1

source: gharchive/pull-request

repo: slingr-stack/gmelius-endpoint


text:
[e2e]: maven workflow_dispatch main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7780258402
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.maven.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.maven.workflow_dispatch.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Mon Feb  5 06:04:42 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7795401714
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.maven.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.maven.workflow_dispatch.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Tue Feb  6 06:04:43 UTC 2024

repo: slsa-framework/slsa-github-generator


text:
Your walking direction makes others bob their heads to it

Walk right, they look right. Walk left, they look left. I don't know why they do that but weird

Yep, the torso tilt property needs to be split to each mario, right now it is a single value.  I am working on a multiplayer rewrite and it will address this

Closing this issue because it is fixed in the new multiplayer version.

cool

license: WTFPL


text:
(Suggestion) Additional Settings For Custom Game

The following are some settings that could be added to make Custom Game more Customizable:
Health: Toggle
Glider/Karts: Toggle
Show Usernames In Game: Toggle
(Would hide all players usernames when toggled off for games of Hide and Seek)
Minimap: Toggle
(Would prevent players from using the minimap if toggled off for games of Hide and Seek)
Knockback: Selection
(Chose from Low, Medium, or High)
Ground-Pound Jump/Dive: Toggle
Gameshark Codes: Toggle
PvP Default: Toggle
(This changes the default PvP toggle, Making More Peaceful/Chaotic Custom Games, User can still toggle it on/off)
Custom Usernames: Toggle
(This would make using Custom Usernames instead of your Discord/Gmail unavailable/available)
Profanity Filter: Toggle
Join/Leave Chat Notification: Toggle
(Would send a message in chat if a user has Joined/Left)
Public Room: Toggle
(Maybe a Public room list could be added in the future, each user could only make one room each to prevent room spam, If Toggled off it would give you a link like normal)
Public Room Name: Text Box
(Requires Public Room Toggle to be active)
Public Room Password: Toggle + Text box
(Requires Public Room Toggle and Password Toggle to be active to use text box, Would show a lock next to the room and the room creator would give out a password to use to enter the room)
Other things that could be added to custom games:
Announcement Text box
(Would be under the chat box for only the room creator, would act like public game announcements from moderators)
Kicking
(If the room creator uses "/kick [user]", the user will be kicked and will be unable to join again for another 10 minutes and would not tell them to wait or show a timer in order prevent them from joining again, /ban could also be added)
Seeker
(If the room creator uses "/seek [user]" the user would become 1.5 times bigger, deal 8 damage on all hits, and become a bright red. They would also not be able to see usernames in game or use the minimap no matter what the username/minimap settings are set to.)

I agree. Developers will add features soon in this game.

Cool ideas!

Woah! Those are some really sweet ideas! Might take a ton of time for developing, but still, I would love to see all this in sm64js.com!

Nice ideas!

Custom games are depreciated for now.


text:
Publish to Maven Central

Hi,
is this project still active ?
Are you planning to publish your project to Maven central ?

Hi @eolivelli, I'm not actively developing this project. I believe it should be on Maven central already (please also see README.md for what to add to pom.xml). Let me know if it doesn't work and I'll take a look, for now I'll go ahead and close this issue.

@eolivelli, did you add the dependency as described in README.md? It is listed as:
<dependency>
    <groupId>net.smacke</groupId>
    <artifactId>jaydio</artifactId>
    <version>0.1</version>
</dependency>

As far as I know, adding this dependency to your pom.xml should be all you need to get the dependency from Maven central -- it works for me. Where specifically are you having trouble?

Sorry
The artifact is on Maven Central
https://mvnrepository.com/artifact/net.smacke/jaydio/0.1
Yesterday I was looking for the wrong groupId
Thank you for checking again.
You library will be useful in my project (https://github/diennea/herddb) in order to leverage O_DIRECT with JDK8.
Now with JDK10+ O_DIRECT is natively available in the JDK10 and it is working very well.

authors: eolivelli smacke

repo: smacke/jaydio


text:
MP Rest Client 1.2

fixes #43

Thanks Ken for switching to the released version!
I tried the tests locally and they pass. I also retried them a couple times on SemaphoreCI and they fail (always on time out on wiremock but not always the same amount of tests fails...)

I suspected it was something intermittent.
So I guess we can take a punt and merge and hope it works?

@kenfinnigan if you're okay with it we can do it ;)

If it's run locally without issue we can give it a shot.
Then investigate further if it fails again, maybe we need to increase a wiremock timeout

authors: kenfinnigan michalszynkiewicz

repo: smallrye/smallrye-rest-client


text:
Initialize steppath using a function instead of init

Description
This commit changes the initialization of the STEPPATH to an Init function instead of doing it at the start using Go's init function.
It also removes the mkdir of STEPPATH. If necessary, commands like "step ca bootstrap" or "step ca init" will create the directory.
step and step-ca should call step.Init() at the start and fail if an error is returned. We might need to change other tools too.
Commands that create files in the STEPPATH or in a step context should create the directory if it doesn't exist. Main commands like step ca bootstrap and step ca init already do that.

Does it make sense to add a helper for the mkdir operation, to be called after Init()?

I added that initially, but I removed it after not seeing an operation that writes files there that do not do MkdirAll. I can add it back, @hslatman what do you think?

Might be handy to add, just in case, for future use cases. It would make this Init and the fact that the dir(s) have to be created by the implementer a bit more discoverable/documented.
Given that you mention you didn't find a code path that didn't already do it, it's probably OK to merge this one and add the helper in a follow up.

authors: hslatman maraino

repo: smallstep/cli-utils


text:
Smallstep.step: v0.24.5-rc.11

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Automated with GoReleaser

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.goreleaserbot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant step-travis-ci

repo: smallstep/winget-pkgs


text:
QA: Trail Access/Display

[x] Display trail access only if there is an “atype=trailhead” entry in activities table associated with that POI
[x] Display only one trail system (dictated by trail_info_id)
[x] Display only one trail segment (dictated by trail_info_id) above the “with access to”
[x] Always display at least one segment (even if under 1 mile). Examples: Kickapoo Woods, Dan Ryan Woods
[ ] If a trailhead has an aname, use that in place of the auto naming

We were already always displaying at least one segment for entrance/poi detail panel. I've fixed it to now display the first segment no matter the length for trail subsystem detail panels too.

@versatilehuman  for the Trailhead naming, what do you mean by in place of auto naming?
Generally we are now using the nameid field where it exists to join with the names table to get names.

Display trail access only if there is an “atype=trailhead” entry in activities table associated with that POI

Added with Trailsyserver commit https://github.com/smartchicago/trailsyserver/commit/c9ecaa1341411a78e9df562b13d3574752e9600f

@versatilehuman I am still a little unclear on the expectations for trailhead naming.
For activities in general, the name is populated by:

names.name based on activities.nameid=names.nameid
If (1) produces nothing, fall back to activities.aname for name.

Trailheads are similarly done as:

names.name based on activities.nameid=names.nameid + " Trail Access"
If (1) produces nothing, fall back to activities.aname for name  + " Trail Access"

So is the idea to get rid of the " Trail Access" part and rely on names.name and activities.aname only?

I talked to Garret and he wants to keep the names.nameid first approach. So I need to go back and add new nameids for many of the new activities and update the name table (I had never seen the name table and clearly didn't understand the naming approach). Addressing it that way, I can add "Future Access" on the data side and make sure new activities are named correctly.

@shua123 We lost Trail Access in the panel.

Any lingering issues covered by #125

repo: smartchicago/trailsy


text:
SMRT-1209 Adding Travis CI file

co-authored-by: Richard Jones rajones@hntb.com

closing because of ci issues

repo: smartcitiesdata/divo


text:
remove unused dai variable

RewardToken is used for both staking and rewards.
Remove dai variable from staking.test.js.
All tests work.

Boom!

authors: PatrickAlphaC tonisives

repo: smartcontractkit/defi-minimal


text:
docs: fix nonexistent search param in list table

Fix the use of nonexistent "search" parameter in list table --> should have been "schema"

Closed due to merge conflict --> will be addressed/combined in a new PR

repo: smartmind-team/thanosql-sdk-python


text:
Typescript definitions

I use typescript when possible and I have written some basic definitions for this SDK. I would like to contribute them to this repository if possible. Feedback on the idea and then the definitions themselves would be awesome!

That sounds fantastic, @mnalsup! Will you put together a pull request? We'll work with you to get it into the SDK.

This functionality will be revisited should the SDK be moved over to TypeScript.

https://www.npmjs.com/package/@types/smartystreets-javascript-sdk

https://www.npmjs.com/package/@types/smartystreets-javascript-sdk

authors: cbuchert kkikta-bcg mnalsup newbish


text:
🛑 Stefanie-Braun.de is down

In 1bafc74, Stefanie-Braun.de (https://www.stefanie-braun.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Stefanie-Braun.de is back up in 906a6fa after 6 minutes.

repo: smb/mon-ip


text:
also works with GetText 0.13.x

Declare it to also work with GetText 0.13.x so that projects using it are not stuck with GetText 0.12

Coverage remained the same at 97.561% when pulling a0f0b01f51d6d3ec6d9f17f6cab57e1ae28ba437 on roques:patch-1 into e82f6a3db4416ac93f2f5d99ea251fce7b1a5c86 on smeevil:master.

Thank you :)

authors: coveralls roques smeevil


text:
Simplifying base directory

I think it's easier for first-time users to navigate the GitHub page when the base directory is smaller.
I'd suggest making a folder MetaMorpheus with all the code:
MetaMorpheus
--> Bootstrapper1
--> CMD
--> EngineLayer
--> GUI
--> MetaMorpeusSetup
--> TaskLayer
--> Test
--> .dockerignore
--> Dockerfile
--> MetaMorpheus.sln
--> smith_MM_certificate.pfx.enc
And then keep the stuff at the base level that needs to be at the base level:
.gitattributes
.gitignore
.travis.yml
LICENSE.txt
README.md
_config.yml
Would need to update AppVeyor, Docker, and Travis builds accordingly.

https://github.com/smith-chem-wisc/MetaMorpheus/pull/2060

repo: smith-chem-wisc/MetaMorpheus


text:
Add no-op behavior for initialize methods of logging system.

Issue #

https://github.com/awslabs/aws-sdk-swift/issues/903
Description of changes

Calling bootstrap method of swift-log's LoggingSystem more than once per program execution results in unexpected behavior (swift-log spec), most likely a crash.
To avoid this crash, no-op behavior is added to SDKLoggingSystem which wraps LoggingSystem. Whether the initialize methods have been already called or not is internally recorded to isInitialized variable. If yes, methods return with no-op done.
Scope

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This approach is not thread-safe because this may still result in multiple calls to bootstrap if it is simultaneously called from different threads.
Two possible approaches to thread-safe initialization:

Use NSRecursiveLock to enforce exclusive access to LoggingSystem and the isInitialized variable.  You can find a recursive lock example in our codebase here:
https://github.com/smithy-lang/smithy-swift/blob/f11e2e816b8b7e578872bde38b56578caa69fd90/Sources/ClientRuntime/Networking/Streaming/BufferedStream.swift#L71
Use a Swift actor to enforce exclusive access to initialization.  Look up Swift actors if you have not used them before.

The first approach is technically not async-safe since it blocks the calling thread, though the effect is minimal if the lock is released quickly. The second approach would require marking the initialize methods async which, depending on where they're called from, may be a breaking API change.
Look at either of these methods & let me know if you have further questions about how they work.

Super interesting! I just looked up these approaches and using actor seems like a good approach to me since it is part of Swift's concurrency features which we already utilize elsewhere (async/await).
Based on your latest commit seems like you agree @sichanyoo! From my limited understanding it looks like you want to declare the add and initialize with async to make it work with actor.

authors: dayaffe sichanyoo

repo: smithy-lang/smithy-swift


text:
No workee in Unity 2020.1.10f1

I see a lot of pink shader posts here.
Does anybody think the developer will correct?

@giantkiller Hello unfortunately this plugin no longer supported
If you want to convert the specific shader please let me know I can help you

Thank you. I could use help. My initial concern is that the GLSL variants have strayed far from what they were when you wrote this or HLSL has changed significantly also.
The https://www.shadertoy.com/view/WtSfWK
//-----------------------------------------------
// main = animate + render + color grade
//-----------------------------------------------
void mainImage( out vec4 fragColor, in vec2 fragCoord )
{
// init random seed
ivec2 q = ivec2(fragCoord);
and then the converter shows:
fixed4 frag(VertexOutput i) : SV_Target
{
	// init random seed
	fixed2 q = fixed2(i.uv, i.uv);

The compiler errors at this line fixed2(i.uv, i.uv); with incorrect number of arguments to numeric-type constructor
So I am not sure about line of code. My hunch is the converter got confused.
I know C. I am weak on writing structs but I understand them when I see them.
And I could not find an explanation of fixed2(i.uv, i.uv) with or why 2 parameters.
I see a lot of of ShaderToy shaders and I want to get to the point of grabbing them, running them through your converter then repairing them of the nuances. With a big 'if that is possible?'
Thank you for your previous response.

Thank you. I could use help. My initial concern is that the GLSL variants have strayed far from what they were when you wrote this or HLSL has changed significantly also.
The https://www.shadertoy.com/view/WtSfWK
//-----------------------------------------------
// main = animate + render + color grade
//-----------------------------------------------
void mainImage( out vec4 fragColor, in vec2 fragCoord )
{
// init random seed
ivec2 q = ivec2(fragCoord);
and then the converter shows:
fixed4 frag(VertexOutput i) : SV_Target
{
	// init random seed
	fixed2 q = fixed2(i.uv, i.uv);

The compiler errors at this line fixed2(i.uv, i.uv); with incorrect number of arguments to numeric-type constructor
So I am not sure about line of code. My hunch is the converter got confused.
I know C. I am weak on writing structs but I understand them when I see them.
And I could not find an explanation of fixed2(i.uv, i.uv) with or why 2 parameters.
I see a lot of of ShaderToy shaders and I want to get to the point of grabbing them, running them through your converter then repairing them of the nuances. With a big 'if that is possible?'
Thank you for your previous response.

authors: giantkiller smkplus

repo: smkplus/ShaderMan


text:
Summerize and compare all results

Is your feature request related to a problem? Please describe.
If you are running 5-10 models, it comes very difficult to read though all of them, especially if they are contradicting
Describe the solution you'd like
Chatall wrote a promt that gets leads to a ranking of the answers and a final conclusion. Something similar would be nice.
Additional context
I know scraping the response form the different UIs is difficult but i beleve its worth it. A project called smart gpt tied this approach and beat a bunch of benchmarks with it

#132 already touched on smartgpt but i think the chatall implementation still solves the 'no api keys' requirement

cool, would happily welcome a PR for that!

authors: PhillipRt swyxio

repo: smol-ai/GodMode


text:
[Draft] Left-over temp() files

Snakemake version
Bug appeared in the 7.x series.
The bugfix for temp files introduced in version 7.3 (and further fixed in 7.3.5) hasn't fixed all our issues.
Bug still present as of 7.8.2
Describe the bug
Note: this is a draft submission, our team needs to analyze the issue better in order to make a simpler proof-of-concept example. This current issue is based on some real-world run on large datasets, we need to first trim down to a usable minimal example.
Not all files tagged as temp() are cleaned-up. What we have observed while rummaging through logs and scratch directories:
It seems that in simple situation with one temp file passed between a producer rule and a consumer rule, everything works fine, and the file is deleted upon completion of the consumer rule (ie. when exactly 2 rules are involved):

rule A → temp() → rule  B

But we observe left-over temp files when:

multiple rules (>2) sharing the same files seem to throw it of:

rule A, rule B → temp() → rule C
(i.e.: two alternative rule could be generating a given file, selected through configuration)
rule A → temp() → rule B, rule C
(i.e.: multiple down-stream consumers of the temp file)

single rules (<2) ditto:

rule A → temp()
(this is used in the absence of proper handling of node-local temporary space by snakemake #1474)

Less certain if that hypothesis is the mechanism:

When a rule is affected, its other output could be affected, despite being straight forward.

rule A, rule B → temp() → rule C

n rules >2, affected

rule C → temp() → rule D

n rules = 2, but coming from affected rule C
i.e.: the whole "left-over temp file" issue is triggered at the level of a whole rule, as soon as any of its input or output aren't straight forward.

Also, I have no idea whether this is related the current issue or completely independent:

Currently snakemake reports a lower total number of jobs in the initial plan (e.g.: total 664) than in the progression counter (e.g.: finished with ( 664 of 1163 steps (57%) done)
This peculiar run was executed using the --until command-line option
Note though that none of the temporary files are used beyond that point, so they would have been all safe to be deleteted, but only the straightforward (rule A → temp() → rule  B) were.
Question: Is snakemake internally creating some "virtual jobs" to handle clean-up of more complex temp() files?
Also out pipeline runs on a HPC (using LSF as a job submission system), and uses groups to bundle multiple rules on a single job.

Logs
Note: as mentioned this comes from a large real-world use, we need to trim it down.
Job stats:
job                    count    min threads    max threads
-------------------  -------  -------------  -------------
dehuman                  166             16             16
dh_filter                166             16             16
dh_hostalign             166             16             16
dh_redo_alignreject      166              8              8
total                    664              8             16

Select jobs to execute...

…

4 of 1163 steps (0.3%) done

…

[Sun Jun 19 13:19:15 2022]
Finished job 2399.
[Sun Jun 19 13:19:15 2022]
Finished job 2398.
[Sun Jun 19 13:19:15 2022]
Finished job 2397.
[Sun Jun 19 13:19:15 2022]
Finished job 2396.
664 of 1163 steps (57%) done
Removing temporary output /cluster/scratch/bs-pangolin/pangolin/temp/samples/B8_10_2020_12_16_NA_NA/20201223_HWKGTDRXX/raw_uploads/filtered_1.fastq.gz.
Removing temporary output /cluster/scratch/bs-pangolin/pangolin/temp/samples/B8_10_2020_12_16_NA_NA/20201223_HWKGTDRXX/raw_uploads/filtered_2.fastq.gz.
Complete log: .snakemake/log/2022-06-19T125746.832133.snakemake.log

…/raw_uploads/filtered_2.fastq.gz. is a straightforward case (rule A → temp() → rule  B).
After running:
/cluster/scratch/bs-pangolin/pangolin/temp/samples/12_2020_11_5_A/20201215_JGDDY/alignments/reject_R2.fastq.gz
/cluster/scratch/bs-pangolin/pangolin/temp/samples/12_2020_11_5_A/20201215_JGDDY/alignments/host_aln.sam
/cluster/scratch/bs-pangolin/pangolin/temp/samples/12_2020_11_5_A/20201215_JGDDY/alignments/reject_R1.fastq.gz
/cluster/scratch/bs-pangolin/pangolin/temp/samples/12_2020_11_5_A/20201215_JGDDY/alignments/dehuman.filter
/cluster/scratch/bs-pangolin/pangolin/temp/samples/12_2020_11_5_A/20201215_JGDDY/alignments/dh_aln.sam
/cluster/scratch/bs-pangolin/pangolin/temp/samples/12_2020_11_5_A/20201215_JGDDY/raw_uploads/dehuman.sam
…

This remaining files have the other organizations mentioned above.
Minimal example

Will come soon...
Additional context
These issues have been affecting us while we're running V-pipe. In several point of the pipeline, such as the rules in charge of depleting human-mapping alignement-reject from the raw read, and recompress the raws as cram files, before uploading those on SRA.

@uweschmitt could you help with the minimal example?

@uweschmitt could you help with the minimal example?

Will have a look tomorrow.

rule all:
    input:
        "files/done.txt",

rule create_data:
    output:
        used_output = temporary("files/used_output"),
        unused_output = temporary("files/unused_output"),
    group: "a"
    shell:
        """
        echo rule a > {output.used_output}
        echo rule a > {output.unused_output}
        """

rule consume_data:
    input:
        froma = "files/used_output"
    group: "a"
    output:
        done=("files/done.txt")
    shell:
        """
        touch {output.done}
        """

Snakemake does not cleanup the files/unused_output file when run in cluster mode. The group assignments in the scrpt are required to trigger the bug:
$ snakemake --cluster "bsub" -j 1
...
$ ls files
done.txt  unused_output

We will delete this issue soon which is superseded by https://github.com/snakemake/snakemake/issues/1754

authors: DrYak uweschmitt

repo: snakemake/snakemake


text:
Improve Event Exchange on Event Sources

Introduction
Each EventSource has a data channel that data go through them. Currently, there is only one goroutine that distributes events between clients.
Problem
One goroutine might not be enough to distribute events if the rate of incoming events or number of subscribers on a specific topic increases.
Initial Solution
Goroutine Pool

Issue Resolved in #14

repo: snapp-incubator/qsse


text:
fix: enable alias voting and propose globally

Needed for https://github.com/snapshot-labs/sx-monorepo/pull/320
This PR will enable the already existing voting and proposal creation with alias globally, without checking for space settings

Sounds a bit dangerous because users don't have any option to delete their alias just in case if user login using a unknown device
Maybe before this could we add a way for users to delete their alias and have an expiry for alias? so that old alias won't be used to cast votes

Yes, ideally, we should have a section in user profile to list all alias, and ideally, have a way to customize which actions can be used with alias

waiting for #353

repo: snapshot-labs/snapshot-sequencer


text:
Add Chainstack Polygon node

All other nodes are failing, many spaces are affected

Moralis node is back online


text:
replace eth-ens-namehash with @ensdomains/eth-ens-namehash

@ensdomains/eth-ens-namehash is a fork of eth-ens-namehash maintained by the ENS org.
It makes this patch obsolete: https://github.com/snapshot-labs/snapshot/blob/develop/patches/idna-uts46-hx%2B2.3.1.patch

Awesome!

authors: mktcode samuveth

repo: snapshot-labs/snapshot


text:
fix: Update shutter URL

Summary
Same as https://github.com/snapshot-labs/sx-monorepo/commit/66e98942a0fbebdb2a63e15b884361d2124fd0e0

I think the url end by /

I think the url end with /

It looks to be working fine https://snapshot-git-update-shutter-url-snapshot.vercel.app/#/shutterdao0x36.eth/proposal/0x4bb5cf27998b7371d1c69f7d2d0e433d601bcb46e2a2cdd38108a743c432fa35 any reason for /?
Also it is without / on https://github.com/snapshot-labs/sx-monorepo/commit/66e98942a0fbebdb2a63e15b884361d2124fd0e0

It's returning a 301 code, which redirect to the url with /. Let's use the final url directly
curl -I https://blog.shutter.network/shielded-voting
HTTP/2 301
server: openresty
status: 301 Moved Permanently
location: /shielded-voting/
ghost-cache: MISS
cache-control: public, max-age=31536000
ghost-age: 0
via: 1.1 varnish, 1.1 varnish
accept-ranges: bytes
date: Fri, 02 Aug 2024 07:20:54 GMT
age: 8470
x-served-by: cache-ams21048-AMS, cache-nrt-rjtf7700059-NRT
x-cache: HIT, HIT
x-cache-hits: 1, 1
x-timer: S1722583255.521994,VS0,VE2
vary: Cookie
x-request-id: 253bef3c-f6de-4ca2-a2d9-8068ed20cf3b
ghost-fastly: true
alt-svc: clear
content-length: 0

Done done


text:
Allow to follow bluesky account from the web UI for websites

On web.brid.gy, when using indieauth, i can follow mastodon account from the account of my website, but i can't follow bluesky accounts.
This should be for both adding the bluesky account i want to follow, or going to another bluesky account profile and saying my account to be follow it (it should be the same endpoint).

Yes! This should definitely support Bluesky.

repo: snarfed/bridgy-fed


text:
Flickr add upload method

Flickr uploads uses a separate API from other requests
use requests.post for upload (urllib2 doesn't help with multi-part)
If no permission scopes are requested, use the authenticate
API instead of authorize (returns without prompting if previous authed)

cool!
should raise_for_failure maybe go into webutil.util.interpret_http_exception?
I'm also curious to hear the rationale for why upload is here instead of granary. i get that it's a different api, but still...?

also, XML, whee!

It does seem more consistent for the Flickr error code interpretation in raise_for_failure to be in interpret_http_exception instead; I'm not sure how to actually move it though. Would I raise a 400 error with the message and error code in the body of the error, and then in interpret, upgrade it to 401 based on the error body?
My thinking on flickr_auth.upload was that it's basically a special case of flickr_auth.call_api_method, and I like having the OAuth1 machinations handled all in this one module. Then the Granary implementation is all about logic and not about manipulating HTTP headers or whatever. That said, I don't feel strongly -- happy to move to Granary if you'd prefer it.

oauth 1! right. makes sense, sgtm.
and yeah, you're right, interpret_http_exception isn't such a great fit after all, since there's no exception here. it's fine as is.

authors: kylewm snarfed

repo: snarfed/oauth-dropins

license: unlicense


text:
folding scheme with lookup arguments (part 2)

This is the final part of issue #34
Here is a short summary of this PR:

rewrite the evaluation trait and evaluation methods for custom gates and lookup gates
put table expression vector {t_i} into advice columns
add log-derivative relational check in decider
integration tests of multiple round special soundness protocol for NIFS
multiple bug fixing for lookup integration

For final part of work with issue you can use gh syntax like:
Close #34
In that case with merging of PR - issue will be auto-close

For final part of work with issue you can use gh syntax like: Close #34 In that case with merging of PR - issue will be auto-close

I had added "close #34" in the last commit.

I think I'm ripe for adding struct to store indexes instead of tuple for three elements and enum instead of constants. It makes reading the code pretty hard right now. Also isolate taking elements from fixed,selector,other at the index level.
I'll try to do this quickly today (though more likely next weekday morning) and make a PR to this branch

authors: chaosma cyphersnake

repo: snarkify/sirius


text:
Support encrypted connection via phpredis

Fixes https://github.com/snc/SncRedisBundle/issues/562

Can you rebase your branch? I fixed the CI.

Could you also add some tests too please?

I has originally added a test, but then realized Travis only spins up a
basic Redis service, so I'm not sure how I'm able to test the tls
connection. Open to ideas..
I'll rebase when I'm back in the office later this morning.
Thank you!
On Thu, Mar 12, 2020, 3:19 AM Benoit GALATI notifications@github.com
wrote:

Could you also add some tests too please?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/snc/SncRedisBundle/pull/563#issuecomment-598110352,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMXTY2W2JD5Y4FFXF2BQ3RHCZM7ANCNFSM4LF7YLPA
.

I has originally added a test, but then realized Travis only spins up a basic Redis service, so I'm not sure how I'm able to test the tls connection. Open to ideas..

Yea you're right. I have no idea as I am not using this feature myself.

Yea you're right. I have no idea as I am not using this feature myself.

Yeah, with the ease of services like Elasticache (and enabling encryption with a simple option), it's now a hassle to stand up your own Redis instance with custom configs.
Hoping we can just merge this with the caveat that tls via phpredis is not fully tested.
Thanks for your help and maintenance of this very useful package!

Thanks @benburleson

authors: B-Galati benburleson

repo: snc/SncRedisBundle


text:
Send to all user from the app segment

Hi! This is a great and awesome simple package.. thank you!
I want to send notifications to all users from an app, using the app segmentation.. How can i do this?

Thank you!
I can not find instructions in the manual how to do it. It seems this can be done only through firebase console. If you find a description of how we can do it - show me the link and I'll add this feature to the package.
Right now you can sign all the necessary people on the any topic and send a message to him.

I did not found any way to do this too. I will work with topics, seems to be the best (unique) option through API.
Thank you.

authors: guissilveira sngrl

repo: sngrl/php-firebase-cloud-messaging


text:
Manual Installation

CocoaPods and Carthage are awesome tools and make our life really easier, but there are some devs who still don't know how to use them.
It would be cool to add the Manual installation guide in your README.md. You can take a look at my iOS Readme Template to see how you can do it.

I thought it wasn't necessary but you're right, some devs still don't know how to use them.
I will add a guide in the README. Thanks you

authors: klefevre lfarah

repo: snipsco/Postal


text:
Caching doesn't work

Using the recommended settings caching does not work, it seems like things are cached correctly but calling source .venv/bin/activate results in a file not found error
on:
  push:
    branches-ignore:
      - main
name: Tests
jobs:
  test-round-pull:
    name: ground Pull
    runs-on: ubuntu-latest
    defaults:
      run:
        shell: bash
        working-directory: ground-pull
    steps:
      - uses: actions/checkout@v2
      - name: Setup Python
        uses: actions/setup-python@v2
        with:
          python-version: "3.8"
      - uses: harmon758/postgresql-action@v1
        with:
          postgresql version: "11"
          postgresql db: test-db
          postgresql user: postgres
          postgresql password: local_password
      - name: Check Postgres running
        run: |
          sleep 2
      - name: Check running containers
        run: docker ps -a
      #----------------------------------------------
      #  -----  install & configure poetry  -----
      #----------------------------------------------
      - name: Install Poetry
        uses: snok/install-poetry@v1
        with:
          version: 1.1.10
          virtualenvs-create: true
          virtualenvs-in-project: true
          installer-parallel: true
      #----------------------------------------------
      #       load cached venv if cache exists
      #----------------------------------------------
      - name: Load cached venv
        id: cached-poetry-dependencies
        uses: actions/cache@v2
        with:
          path: .venv
          key: venv-${{ runner.os }}-${{ steps.setup-python.outputs.python-version }}-${{ hashFiles('**/poetry.lock') }}
      #----------------------------------------------
      # install dependencies if cache does not exist
      #----------------------------------------------
      - name: Install dependencies
        if: steps.cached-poetry-dependencies.outputs.cache-hit != 'true'
        run: poetry install --no-interaction --no-root
      #----------------------------------------------
      #              run test suite
      #----------------------------------------------
      - name: Run tests
        run: |
          source .venv/bin/activate
          poetry run make check-format
          poetry run make mypy
          poetry run make lint
          poetry run make test

Unfortunately not :(

Whats strange is running the following step, before source .venv/bin/activate works. But this just installs the dependencies again, which we're trying to avoid.
      #----------------------------------------------
      # install your root project, if required
      #----------------------------------------------
      - name: Install library
        run: poetry install --no-interaction

If you have the opportunity to create a demo project or some reproducible example that would help me a lot. Otherwise, maybe it would be helpful to sprinkle in a few ls statements to get a sense of where the venv is located relative to your working directory.

You should restore your cache before installing poetry

@sondrelg This still does not fix it!

on:
  push:
    branches-ignore:
      - main
name: Local Tests - Vital Background Pull
jobs:
  test-vital-background-pull:
    name: Local Tests - Vital Background Pull
    runs-on: ubuntu-latest
    defaults:
      run:
        shell: bash
        working-directory: vital-background-pull
    steps:
      - uses: actions/checkout@v2
      - name: Setup Python
        uses: actions/setup-python@v3
        with:
          python-version: 3.9
      - uses: harmon758/postgresql-action@v1
        with:
          postgresql version: "11"
          postgresql db: vital-test-db
          postgresql user: postgres
          postgresql password: local_password
      - name: Check running containers
        run: docker ps -a
      - name: Restore pip cache
        uses: actions/cache@v3
        with:
          path: $(python -m pip cache dir)
          key: ubuntu-latest-pip-3.9-${{ hashFiles('**/pyproject.toml') }}
          restore-keys: |
            ubuntu-latest-pip-3.9-
      #----------------------------------------------
      #  -----  install & configure poetry  -----
      #----------------------------------------------
      - name: Install Poetry
        uses: snok/install-poetry@v1
        with:
          version: 1.1.10
          virtualenvs-create: true
          virtualenvs-in-project: true
          installer-parallel: false
      - name: Restore poetry cache
        uses: actions/cache@v3
        with:
          path: $(poetry config cache-dir)
          key: ubuntu-latest-poetry-3.9-${{ hashFiles('**/pyproject.toml') }}
      - name: Restore virtualenv
        uses: actions/cache@v3
        id: cache-venv
        with:
          path: .venv
          key: ubuntu-latest-virtualenv-3.9-${{ hashFiles('**/pyproject.toml') }}
      #----------------------------------------------
      # install dependencies if cache does not exist
      #----------------------------------------------
      - name: Install dependencies
        if: steps.cache-venv.outputs.cache-hit != 'true'
        run: poetry install --no-interaction --no-root
      #----------------------------------------------
      #              run test suite
      #----------------------------------------------
      - name: Run tests
        run: |
          source .venv/bin/activate
          make check-format
          make mypy
          make lint
          make test

Can you use something like path: "$( poetry env list --full-path | grep Activated | cut -d' ' -f1 )"  for the cache? Maybe you need the full path of the venv if your runner cwd is different.

authors: maitham miigotu sondrelg

repo: snok/install-poetry


text:
SNOW-861532 Remove sp check for params in session.sql

Description
The change in Snowflake and the connector was checked in to reach full parity as far as integ/test_bind_variable.sql goes. We could remove this restriction from snowpark.
Testing
regression test with test_bind_variable.sql
Please answer these questions before submitting your pull requests. Thanks!

What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes SNOW-861532

Fill out the following pre-review checklist:

[ ] I am adding a new automated test(s) to verify correctness of my new code
[ ] I am adding new logging messages
[ ] I am adding a new telemetry message
[ ] I am adding new credentials
[ ] I am adding a new dependency

Please describe how your code solves the related issue.
The change in Snowflake and the connector was checked in to reach full parity as far as integ/test_bind_variable.sql goes. We could remove this restriction from snowpark.

Ran test against https://github.com/snowflakedb/snowflake/tree/shixuan_bind_test
Test run: https://ci-dev-133.int.snowflakecomputing.com/job/RT-Precommit/12858/
Build job: https://ci-dev-142.int.snowflakecomputing.com/job/PythonStoredProcBuildPrecommitTest/456/
Specifically, the bind variable integ test passed: https://ci-dev-133.int.snowflakecomputing.com/job/RT-PC-TestWorker/177427/testReport/(root)/t_python_sp_integ/snowpark_test_bind_variable_sql/

repo: snowflakedb/snowpark-python


text:
database is locked

Version is 1.0 (implementation "com.snowplowanalytics.snowplow.tracker:snowplow:1.0")
com.snowplowanalytics.snowplow.tracker.Tracker provideSnowplowTracker(SJApp application, Session session) {
	Emitter emitter = new Emitter.EmitterBuilder(SNOWPLOW_EMMITTER_ID, application).build();
	Subject subject = new Subject.SubjectBuilder().context(application).build();
  ...

}

Crashlytics:
Caused by android.database.sqlite.SQLiteDatabaseLockedException: database is locked (code 5 SQLITE_BUSY[5]): , while compiling: PRAGMA journal_mode
at android.database.sqlite.SQLiteConnection.nativePrepareStatement(SQLiteConnection.java)
at android.database.sqlite.SQLiteConnection.acquirePreparedStatement + 1229(SQLiteConnection.java:1229)
at android.database.sqlite.SQLiteConnection.executeForString + 842(SQLiteConnection.java:842)
at android.database.sqlite.SQLiteConnection.setJournalMode + 490(SQLiteConnection.java:490)
at android.database.sqlite.SQLiteConnection.setWalModeFromConfiguration + 460(SQLiteConnection.java:460)
at android.database.sqlite.SQLiteConnection.open + 296(SQLiteConnection.java:296)
at android.database.sqlite.SQLiteConnection.open + 215(SQLiteConnection.java:215)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked + 705(SQLiteConnectionPool.java:705)
at android.database.sqlite.SQLiteConnectionPool.open + 272(SQLiteConnectionPool.java:272)
at android.database.sqlite.SQLiteConnectionPool.open + 239(SQLiteConnectionPool.java:239)
at android.database.sqlite.SQLiteDatabase.openInner + 1292(SQLiteDatabase.java:1292)
at android.database.sqlite.SQLiteDatabase.open + 1247(SQLiteDatabase.java:1247)
at android.database.sqlite.SQLiteDatabase.openDatabase + 903(SQLiteDatabase.java:903)
at android.database.sqlite.SQLiteDatabase.openDatabase + 893(SQLiteDatabase.java:893)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked + 355(SQLiteOpenHelper.java:355)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase + 298(SQLiteOpenHelper.java:298)
at com.snowplowanalytics.snowplow.tracker.storage.EventStore.open + 83(EventStore.java:83)
at com.snowplowanalytics.snowplow.tracker.storage.EventStore.(SourceFile:6)
at com.snowplowanalytics.snowplow.tracker.Emitter.(SourceFile:19)
at com.snowplowanalytics.snowplow.tracker.Emitter.(SourceFile:1)
at com.snowplowanalytics.snowplow.tracker.Emitter$EmitterBuilder.build + 233(Emitter.java:233)
at ru.superjob.client.android.di.module.AnalyticsModule.provideSnowplowTracker + 54(AnalyticsModule.java:54)
at ru.superjob.client.android.di.module.AnalyticsModule_ProvideSnowplowTrackerFactory.provideSnowplowTracker + 36(AnalyticsModule_ProvideSnowplowTrackerFactory.java:36)
at ru.superjob.client.android.di.module.AnalyticsModule_ProvideSnowplowTrackerFactory.get + 26(AnalyticsModule_ProvideSnowplowTrackerFactory.java:26)
at ru.superjob.client.android.di.module.AnalyticsModule_ProvideSnowplowTrackerFactory.get + 10(AnalyticsModule_ProvideSnowplowTrackerFactory.java:10)
at dagger.internal.DoubleCheck.get + 47(DoubleCheck.java:47)
at ru.superjob.client.android.di.component.DaggerAppComponent.getSnowplowTracker + 673(DaggerAppComponent.java:673)
at ru.superjob.client.android.SJApp.initSnowPlow + 201(SJApp.java:201)
at ru.superjob.client.android.SJApp.init + 161(SJApp.java:161)
at ru.superjob.client.android.SJApp.onCreate + 94(SJApp.java:94)
at android.app.Instrumentation.callApplicationOnCreate + 1154(Instrumentation.java:1154)
at android.app.ActivityThread.handleBindApplication + 6153(ActivityThread.java:6153)
at android.app.ActivityThread.access$1200 + 235(ActivityThread.java:235)
at android.app.ActivityThread$H.handleMessage + 1768(ActivityThread.java:1768)
at android.os.Handler.dispatchMessage + 106(Handler.java:106)
at android.os.Looper.loop + 214(Looper.java:214)
at android.app.ActivityThread.main + 6981(ActivityThread.java:6981)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run + 493(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main + 1445(ZygoteInit.java:1445)

Closing because it has been with no activity for a long time.
Please, feel free to reopen or comment this issue, whether it's of your interest or you want to contribute on this.

authors: AlexBenny RuslanTroshkov

repo: snowplow/snowplow-android-tracker


text:
Fatal Exception: java.lang.ExceptionInInitializerError

Describe the bug
Fatal Exception: java.lang.ExceptionInInitializerError
To Reproduce
unable to reproduce in dev environment, facing issue in prod, reported in the firebase crashlog.
Expected behavior
should not throw an error
Screenshots
If applicable, add screenshots to help explain your problem.

Device informatoin (please complete the following information):

Device: Pixel 6
OS: Android 14
Version snowplow_tracker: ^0.7.1  (flutter)

Additional context
stacktrace.txt
Add any other context about the problem here.

@srongch Can you please share your emitter / initialisation snippet and configuration?

authors: miike srongch

repo: snowplow/snowplow-flutter-tracker


text:
Assemble the apps using Docker Compose

https://docs.docker.com/compose/

http://blog.dubizzle.com/boilerroom/2016/08/18/setting-development-environment-docker-compose/

repo: snowplow/snowplow-mini


text:
Support newer Expo/RN versions

Disclaimer: to be honest, I do not fully understand why it only works this way.
I am building an app with RN 0.68.2 and Expo 45. I wanted to install the Snowplow package but the builds for iOS fail with this error (besides for RCTBundleManager also for a few others):
Duplicate interface definition for class 'RCTBundleManager'

in file included from [...]/node_modules/@snowplow/react-native-tracker/ios/RNSnowplowTracker.m:21:
in file included from [...]/node_modules/@snowplow/react-native-tracker/ios/RNSnowplowTracker.h:28:

Based on what I learned from similar issues in other packages I have made the changes in this PR and tested them with my app.

https://github.com/expo/expo/issues/15649
https://github.com/expo/expo/issues/15622
https://github.com/segmentio/analytics-react-native/pull/434

If memory serves originally in this project we couldn't support expo at all, since they it support native modules at the time. It's been a while since I've been involved in this project but awsome to see that's changed - thanks for bringing that to our attention @Jeroen-G!

@colmsnowplow I don't want to diminish your enthousiasm, but Expo does not really support native modules 😅  We use the 'bare workflow' from expo, meaning that we 'ejected' from the Expo bubble and allowing the installation of native modules. Nevertheless, we still rely heavily on Expo packages.

Hi @Jeroen-G
Thanks for the PR. We'll get someone to take a deeper look at this and Expo support shortly, but in the meantime could you sign our CLA so we could merge this? It looks like our CLA bot has gone walkabouts!

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

I don't feel comfortable giving my personal details, therefore I will not sign the CLA. Feel free to do with the contribution what you like :)

Hi @Jeroen-G,
Thanks again for raising this issue and the PR!
I'm sorry to hear that our CLA makes you uncomfortable to contribute. We'll raise your concerns internally in order to see if we can handle the CLA differently. In any case, it can be a long process. We'll keep you updated about any decision about this PR and the CLA issue.

authors: AlexBenny Jeroen-G colmsnowplow paulboocock

repo: snowplow/snowplow-react-native-tracker


text:
Explore events with 192.168.* IP address

In a sufficiently large dataset using Clojure Collector 0.8.0+ (which has X-Forwarded-For parsing), 1 in 1000 events (0.11%) will have a private IP address.
One explanation for these internal IP addresses would be some form of client-side proxy introducing an X-Forwarded-For header into the outbound request. The X-Forwarded-For parsing in the Clojure Collector, and by extension probably the equivalent functionality in Scala Common Enrich (#1372), would then report the internal as the final IP address.
To investigate further depends on #1527.

Just done another analysis on a decent sized data set and found that 0.11% of events were recorded against IP's beginning with 192.168
SELECT
CASE WHEN user_ipaddress LIKE '192.168.%' THEN 'IP starts 192.168' ELSE 'Normal IP' END,
COUNT(*)
FROM atomic.events
GROUP BY 1
ORDER BY 1

Returns:
IP starts 192.168	5745723
Normal IP	5093314942

Migrated to https://github.com/snowplow/enrich/issues/185

authors: alexanderdean chuwy yalisassoon

repo: snowplow/snowplow


text:
Kafka exception on send are not caught correctly

KafkaProducer.send is asynchronous and I don't know if that will fail directly. It seems you need to provide a callback to catch exceptions:
https://kafka.apache.org/0100/javadoc/index.html?org/apache/kafka/clients/producer/KafkaProducer.html
(send method)
Fully non-blocking usage can make use of the Callback parameter to provide a callback that will be invoked when the request is complete.
 ProducerRecord<byte[],byte[]> record = new ProducerRecord<byte[],byte[]>("the-topic", key, value);
 producer.send(myRecord,
               new Callback() {
                   public void onCompletion(RecordMetadata metadata, Exception e) {
                       if(e != null)
                           e.printStackTrace();
                       System.out.println("The offset of the record we just sent is: " + metadata.offset());
                   }
               });

vs https://github.com/snowplow/snowplow/blob/e977c976151a36894ed7b83e9461c2fea7eec252/2-collectors/scala-stream-collector/src/main/scala/com.snowplowanalytics.snowplow.collectors/scalastream/sinks/KafkaSink.scala#L82

Good catch!

authors: alexanderdean simplesteph


text:
Scala Common Enrich: use tnuid to add a network_userid in adapters

Clojure Collector always adds nuid with cookie content to log, therefore it's advised to use tnuid to override network_userid via tracker - SCE overrides network_userid with tnuid value if it is present.
At the same time all adapters accept only nuid parameter, throwing an exception on tnuid. Example from Iglu Adapter:
        "level": "error",
        "message": "error: object instance has properties which are not allowed by the schema: [\"tnuid\"]\n    level: \"error\"\n    schema: {\"loadingURI\":\"#\",\"pointer\":\"\"}\n    instance: {\"pointer\":\"\"}\n    domain: \"validation\"\n    keyword: \"additionalProperties\"\n    unwanted: [\"tnuid\"]\n"

It happens because tnuid should be extracted from Iglu Adapter's payload, but instead it's part of self-describing JSON, which should not be a case.
In the end we have non-working tnuid in adapters+clj-collector.
Docs for webhooks also should be updated: 1, 2, etc. (and many webhook docs miissing fact that some properties can be customized, btw)

Agreed, the webhook adapters should respect tnuid...

Migrated to https://github.com/snowplow/enrich/issues/78

authors: alexanderdean chuwy


text:
Fix primary key secondary key table overwrites

there appears to be more raw logs and less aggregations written to DynamoDB table AggregateRecords.
I suspect that I changed the schema last week from "downsampled_bucket_time + createdAt_timestamp"  to the new  "downsampled_bucket_time + color" which would potentially result in less uniqueness at the table level.  maybe the keys are overwriting each other resulting in less aggregations written to AggregateRecords.

Hey @bigsnarfdude - I've done some further thinking on this. To recap, what we want is a composite key consisting of timebucket + event type. This is so that if you want to get metrics on e.g. "Blue", you can just do a scan of Blue records, for the timebuckets you care about.
You are correct - your current approach won't deliver the above. This is because you will accidentally overwrite your existing count with the new count.
The solution is not to change the secondary index to a whenwritten timestamp, because then we end up with multiple records for a given timebucket+eventtype, and we lose the secondary indexing on event type.
The solution instead is a simple one. We do a read on the existing timebucket+eventtype key, and add our new count to the existing count if found; if not found then we just write the new count.
Does that make sense? Here is the pseudo-code:
for each [timebucket, eventtype, count]:
  get old_count from dynamodb for timebucket+eventtype
  if old_count is null
    new_count = count
  else
    new_count = old_count + count
  end
end

Please confirm the above makes sense and you can make that change on Monday.

somehow my branch got merged to master. i can't recall if i did that but, I tried to revert master and failed. i don't know how to rebase. i could reset my local master three stops and branch off the master at:
commit de1a7e312fcd18dccbfeb91c5cb14bd2e45bba21
Author: Alex Dean alex@snowplowanalytics.com
Date:   Sat Jun 6 12:55:09 2015 +0100
Working on the build Spark

Delete your local copy, do a fresh checkout of master, branch from there...
On 7 Jun 2015 5:12 pm, "Vincent Ohprecio" notifications@github.com wrote:

somehow my branch got merged to master. i can't recall if i did that but,
I tried to revert master and failed. i don't know how to rebase. i could
reset my local master three stops and branch off the master at:
commit de1a7e3
https://github.com/snowplow/spark-streaming-example-project/commit/de1a7e312fcd18dccbfeb91c5cb14bd2e45bba21
Author: Alex Dean alex@snowplowanalytics.com
Date: Sat Jun 6 12:55:09 2015 +0100
Working on the build Spark
—
Reply to this email directly or view it on GitHub
https://github.com/snowplow/spark-streaming-example-project/issues/16#issuecomment-109767338
.

(I merged your branch to master and deleted it to prevent confusion!)
On 7 Jun 2015 5:13 pm, "Alex Dean" alex@snowplowanalytics.com wrote:

Delete your local copy, do a fresh checkout of master, branch from there...
On 7 Jun 2015 5:12 pm, "Vincent Ohprecio" notifications@github.com
wrote:

somehow my branch got merged to master. i can't recall if i did that but,
I tried to revert master and failed. i don't know how to rebase. i could
reset my local master three stops and branch off the master at:
commit de1a7e3
https://github.com/snowplow/spark-streaming-example-project/commit/de1a7e312fcd18dccbfeb91c5cb14bd2e45bba21
Author: Alex Dean alex@snowplowanalytics.com
Date: Sat Jun 6 12:55:09 2015 +0100
Working on the build Spark
—
Reply to this email directly or view it on GitHub
https://github.com/snowplow/spark-streaming-example-project/issues/16#issuecomment-109767338
.

ok

getOrCreate function built to resolve overwrites

authors: alexanderdean bigsnarfdude


text:
FileNotFoundError: [Errno 2] No such file or directory: '/root/.ynam_mintapi_cookies'

I'm not much well-versed in python so please forgive me in advance. I'm running macOS Monterey and tried getting the utility to work in Terminal and also trying to run in Docker. So I attempted to do a fresh install and run in Docker (building the image using the dockerfile in the ynam repo). When I go to run the container, I get this error...
2022-11-30 19:58:52 Traceback (most recent call last): 2022-11-30 19:58:52   File "/usr/local/lib/python3.8/dist-packages/ynam/main.py", line 21, in main 2022-11-30 19:58:52     mints = mapi.getXtns() 2022-11-30 19:58:52   File "/usr/local/lib/python3.8/dist-packages/ynam/api.py", line 84, in getXtns 2022-11-30 19:58:52     client.authorize(self.cookies(), self.key()) 2022-11-30 19:58:52   File "/usr/local/lib/python3.8/dist-packages/ynam/api.py", line 98, in cookies 2022-11-30 19:58:52     with open(self.cpath, 'r') as file: 2022-11-30 19:58:52 FileNotFoundError: [Errno 2] No such file or directory: '/root/.ynam_mintapi_cookies' 2022-11-30 19:58:52  2022-11-30 19:58:52 During handling of the above exception, another exception occurred: 2022-11-30 19:58:52  2022-11-30 19:58:52 Traceback (most recent call last): 2022-11-30 19:58:52   File "/usr/local/bin/ynam", line 8, in <module> 2022-11-30 19:58:52     sys.exit(main()) 2022-11-30 19:58:52   File "/usr/local/lib/python3.8/dist-packages/ynam/main.py", line 23, in main 2022-11-30 19:58:52     mapi.updateAuth() 2022-11-30 19:58:52   File "/usr/local/lib/python3.8/dist-packages/ynam/api.py", line 117, in updateAuth 2022-11-30 19:58:52     file.write(str(bowser._get_cookies())) 2022-11-30 19:58:52   File "/src/mintapi/mintapi/browser.py", line 214, in _get_cookies 2022-11-30 19:58:52     return self.driver.get_cookies() 2022-11-30 19:58:52 AttributeError: 'NoneType' object has no attribute 'get_cookies'
It does this whether I try to run manually in Terminal, or try to start the container in Docker
Also even after installing ynam with python3, I'm getting a command not found when trying to run the ynam function...I may have missed a number of steps.
Thanks!

Figured this out. Looks like the current versions doesn't gracefully handle if a cookie file doesn't exist, and the default path is at /root/.ynam_mint_api_cookies.
Doing touch .ynam_mint_api_cookies in a directory you mount into /root for the container seems to get past it.

ynam knows how to recover from a missing cookie file. When it can't login, it calls MintAPI.updateAuth(), which resets the cookie file, among other things. There might be a filesystem permissions issue that stops ynam from creating files, though, which could cause this error.
As @natescherer  mentioned, the default location is in the home directory of whatever user it's running as. If you need it to be elsewhere, the --cookies parameter is your friend

repo: snowskeleton/ynam


text:
help: is my EdgeTPU working properly

hey @snowzach,
this is actually not a bug but more a question - and I am really sorry for that - cause I am not pretty sure if my EdgeTPU is working properly.
I have doods2 running on a Beelink Mini S12 Pro, with Ubuntu Server 24.04 installed, inside docker (image is latest). I have installed the drivers accordingly and running lsusb on the host gives (as far as I can tell) the correct output:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 18d1:9302 Google Inc.

the docker-cmpose has the /dev/bus/usb mapped proper:
  doods2:
    container_name: dc_doods
    image: snowzach/doods2:latest
    labels:
      com.centurylinklabs.watchtower.enable: true
      traefik.enable: true
      traefik.http.routers.doods.middlewares: 'https_redirect@file'
      traefik.http.routers.doods.rule: 'Host(`doods.domain.net`)'
      traefik.http.routers.doods.entrypoints: 'web, web-secure'
      traefik.http.services.doods.loadbalancer.server.port: 8080
    devices:
      - /dev/bus/usb:/dev/bus/usb
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /srv/nfs/docker/doods2/config.yaml:/app/config.yaml
      - /srv/nfs/docker/doods2/models:/app/models
    environment:
      - CONFIG_FILE=/app/config.yaml
    restart: unless-stopped
    stop_grace_period: 30s

My doods 2 server is configured as follows - mind the edgetpu model and hwaccel true setting:
  detectors:
    - name: default
      type: tflite
      modelFile: /app/models/tf2_ssd_mobilenet_v1_fpn_640x640_coco17_ptq_edgetpu.tflite
      labelFile: /app/models/coco_labels_tf2_ssd_mobilenet_v1_fpn_640x640_coco17_ptq_edgetpu.txt
      hwAccel: True

when connection the bash in the docker and running lsusb - it shows the following which slightly confuses me:
Bus 002 Device 002: ID 18d1:9302
Bus 002 Device 001: ID 1d6b:0003 Linux 6.8.0-36-generic xhci-hcd xHCI Host Controller
Bus 001 Device 002: ID 8087:0026
Bus 001 Device 001: ID 1d6b:0002 Linux 6.8.0-36-generic xhci-hcd xHCI Host Controller

next thing is the logs when starting the server - which says for CPU:
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
2024-06-28 08:47:22,844 - doods.doods - INFO - Registered detector type:tflite name:default
2024-06-28 08:47:22,876 - uvicorn.error - INFO - Started server process [1]

when detecing an image the edgetpu modeel seems to be working - but I wonder if it is cpu-based detection or with the EdgeTPU: (sample with stock image)

{
  "id": "manual",
  "detections": [
    {
      "top": 0.013015419244766235,
      "left": 0.22488349676132202,
      "bottom": 0.995612382888794,
      "right": 0.7756258845329285,
      "label": "person",
      "confidence": 80.078125
    }
  ],
  "duration": 300
}

is there any chance to see if it using the tpu?
thanks for any help 🙏🏼

If you are using a model that has edgetpu in the filename, it's using the TPU. Generally it will fail if you arent. If you want to verify, unplug and try without it.. It shouldn't work.

perfect - thanks for the hint. 👍🏼

authors: kimpenhaus snowzach


text:
sqe2dos: plot residual

One way to understand the reliability of the DOS computed from SQE is to have a look at the residual I(E) and compare it to the original measured I(E). Add a script for that.

ARCS Vanadium data
Large residual. C_ms=0.5. it is too large.

Smaller residual. C_ms=0.2

repo: sns-chops/multiphonon


text:
[Snyk] Security upgrade ruby from 2.6.5 to 2.7.7

Snyk has created this PR to fix 2 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

openshift-configs/Dockerfile

We recommend upgrading to ruby:2.7.7, as this image has only 401 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Write SNYK-DEBIAN10-LIBWEBP-5893093
  852

Out-of-bounds Write SNYK-DEBIAN10-LIBWEBP-5893093
  852

Out-of-bounds Write SNYK-DEBIAN10-LIBWEBP-5893093
  852

Out-of-bounds Write SNYK-DEBIAN10-LIBWEBP-5893093
  852

CVE-2023-44487 SNYK-DEBIAN10-NGHTTP2-5953390
  561

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

:tada: Snyk checks have passed. No issues have been found so far.
:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)
:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)

repo: snyk-kevin/railsgoat


text:
[Snyk] Security upgrade tap from 11.1.5 to 18.0.0

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

package.json
package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230
  170

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

:tada: Snyk checks have passed. No issues have been found so far.
:white_check_mark: code/snyk check is complete. No issues have been found. (View Details)

repo: snyk-rfrazier/nodejs-goof


text:
🛑 Interseed (interseed.app) is down

In 0f0989f, Interseed (interseed.app) (https://interseed.app) was down:

HTTP code: 404
Response time: 126 ms

Resolved: Interseed (interseed.app) is back up in 1590960 after 17 minutes.

repo: so-more/proof-monitoring


text:
Command-line for shots detection and split in tensorflow or pytorch

I am impressed with this tool.
I want to ask the command line for
mp4 to shots splitting and
mp4 to shots detection
using the tool.
If you can help.

There is a cli tool.
See https://github.com/soCzech/TransNetV2/tree/master/inference#simple-usage.
Just install and use:
transnetv2_predict /path/to/video.mp4


text:
Installation using TCSH - conda info

     active environment : goodman_pipeline
    active env location : /home/briceno/linux/miniconda3/envs/goodman_pipeline
            shell level : 1
       user config file : /home/briceno/.condarc
 populated config files : /home/briceno/.condarc
          conda version : 4.5.11
    conda-build version : not installed
         python version : 3.7.0.final.0
       base environment : /home/briceno/linux/miniconda3  (writable)
           channel URLs : http://ssb.stsci.edu/astroconda/linux-64
                          http://ssb.stsci.edu/astroconda/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/linux-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/pro/linux-64
                          https://repo.anaconda.com/pkgs/pro/noarch
          package cache : /home/briceno/linux/miniconda3/pkgs
                          /home/briceno/.conda/pkgs
       envs directories : /home/briceno/linux/miniconda3/envs
                          /home/briceno/.conda/envs
               platform : linux-64
             user-agent : conda/4.5.11 requests/2.19.1 CPython/3.7.0 Linux/4.15.0-36-generic ubuntu/18.04 glibc/2.27
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

With pip installation this is not important now.

authors: cbaorion simontorres


text:
Type definitions

Hello! Could you please give us TypeScript definitions?

any updates on this?

No, sorry, no plan to work on this any time soon. Pull requests are welcome though.
You could also try simple alternative using hooks: https://github.com/oblador/react-native-animatable/issues/132#issuecomment-786870602

authors: nhbravo sobstel

license: Unlicense


text:
Rename internal to intrinsic

I believe it might be a more precise name and frees up internal as a
possible visibility modifier, if we ever need it.

Please note that this branch is currently sitting on the filename branch, so it would make sense to review the PR about filename first, and then I'll rebase this branch onto master.

repo: soc/dora


text:
Disc not loading on slim PSone console

Before opening this kind of issue, please ensure:

I am using a compatible console version.
I am using CD-R media, not CD-RW.
I bought the card from an eBay seller, so I would imagine they installed it correctly since it's working on another console.

TonyHax version 1.4.3
I bought the memory card from an eBay seller.
Tony Hawk's Pro Skater 2 (NTSC-U)
SCPH-9001 (works), and 2x SCPH-101 (not working).
The integrity check passes.
SCPH-9001: BIOS v4.1 12/16/97 A, 1st SCPH-101: BIOS v4.4 03/24/00 A, 2nd SCPH-101: BIOS v4.5 05/25/00 A
I have burnt the PS1 port of the 240p Test Suite using the image linked here:
https://github.com/filipalac/240pTestSuite-PS1/issues/12
Although it works perfectly on my fat PS1 (the SCPH-9001), it will not load on my two slim PSone consoles (SCPH-101). When attempting to load it on both slim consoles, I get the Disc error type D with either code 22 or code 12. What's even more annoying is I've managed to get it to work once without errors, but now it shows these errors every time I try to load it.

I've tried cleaning the disc drive lens.
I've also tried adjusting the laser potentiometer.
I've burnt the disc at the slowest possible speed that my drive allows (10x).

The disc I used is a CMC Magnetics Maxell CD-R. I would try other brands of CD-R, but this is all I have. I've also heard that Verbatim discs are now CMC made, so I don't think those would help.
If anyone has any advise on getting this to work on a Slim PSone, I'd appreciate it. I initially thought Sony implemented stricter checks to make sure the slim consoles couldn't read burnt CDs, but considering other Slim PSone users have managed to get TonyHax to read discs just fine, I am baffled at this.

According to https://github.com/grumpycoders/pcsx-redux/blob/0889ddf70e503751aff0b1a2873a07b88d68340b/src/mips/openbios/cdrom/helpers.c#L60, type D code 12 are thrown when a disc's sector cannot be read - ie it's probably the media's fault.

I pretty much forgot about this until you closed it. I was able to make a working copy of the disc (still using the same CMC Magnetics Maxell discs as before) by burning it again using an older CD burner - the 2005 vintage NEC DVD burner in my Windows XP computer. It turns out that the modern laptop form factor DVD burner in my Windows 7 computer wasn't cutting it in this case. I was told that laptop CD burners aren't 100% reliable for this situation, so I thought I'd try an older desktop form factor burner and sure enough, it works now. Now I can use 240p Test Suite on all of my PS1 consoles (fat and slim).

CMC magnetics is complete garbage. I agree with socram8888. You want Verbatim datalifeplus from Mitsubishi (probably).


text:
zlef ayn/EN 42928/upgrades

[ ] styleCheck passes
[ ] unit tests pass
[ ] integration tests pass
[ ] manual tests pass
[ ] API docs updated

This build looks good.

This build looks good.

This build looks good.

This build looks good.

authors: socrata-jenkins zachlefevre

repo: socrata-platform/spandex


text:
Missing genes in output after adding alignments to clustering.

Expected Behavior
All genes from the input file should be in the output.
Current Behavior
Without adding the alignment the behavior is as expected. But when alignment is included some genes go missing from the output file.
Steps to Reproduce (for bugs)
Please make sure to execute the reproduction steps with newly recreated and empty tmp folders.

mmseqs createdb $infile $DB/$n --dbtype 2
mmseqs cluster $DB/$n $C90/${n}_C90_cluster ${n}_tmp --min-seq-id 0.90 --cov-mode 1 -c 0.5 --cluster-mode 2 --cluster-reassign --threads 5
mmseqs align $DB/$n $DB/$n $C90/${n}_C90_cluster $C90/${n}_C90_align --alignment-mode 2 --threads 5
mmseqs createtsv $DB/$n $DB/$n $C90/${n}_C90_cluster ${odir}/${n}_C90_cluster.tsv --threads 5
mmseqs createtsv $DB/$n $DB/$n $C90/${n}_C90_align ${odir}/${n}_C90_cluster_align.tsv --threads 5

MMseqs Output (for bugs)
Please make sure to also post the complete output of MMseqs. You can use gist.github.com for large output.

wc -l 09d_mmseqs_cluster_tsv/*
344349 09d_mmseqs_cluster_tsv/Vibrio_cholerae_C90_cluster_align.tsv
358964 09d_mmseqs_cluster_tsv/Vibrio_cholerae_C90_cluster.tsv

Context
Providing context helps us come up with a solution and improve our documentation for the future.
I'm trying to use MMSeqs2 instead of CD-HIT but I need the alignment of each gene in a cluster to the representative gene.
Your Environment
Include as many relevant details about the environment you experienced the bug in.

Git commit used (The string after "MMseqs Version:" when you execute MMseqs without any parameters):
Which MMseqs version was used (Statically-compiled, self-compiled, Homebrew, etc.):
For self-compiled and Homebrew: Compiler and Cmake versions used and their invocation:
Server specifications (especially CPU support for AVX2/SSE and amount of system memory):
Operating system and version:

The alignments are probably falling below the default alignment threshold. Just give a large value to the -e parameter and it should not reject any alignments anymore.

Ok. That totally works. Thank you!!
I had to give it a super large value. Should I think about adjusting some clustering thresholds? Does this mean some of the sequences in that end up in various clusters aren't a great fit?

authors: milot-mirdita rotheconrad


text:
🛑 Subs EU is down

In 782b802, Subs EU (https://subscene.eu.org) was down:

HTTP code: 502
Response time: 515 ms

Resolved: Subs EU is back up in 322879c.

repo: softsub/uptime


text:
Fix setNativeProps type

Summary
Setting Object to the props type does not allow passing any object to the method. So in TypeScript when using the method for example with Path, you will get an error when passing the d:
this.pathComponent?.setNativeProps({ d })

Argument of type '{ d: string; }' is not assignable to parameter of type 'Object & { matrix?: ColumnMajorTransformMatrix | undefined; fill?: ColorValue | undefined; } & TransformProps'.
  Object literal may only specify known properties, and 'd' does not exist in type 'Object & { matrix?: ColumnMajorTransformMatrix | undefined; fill?: ColorValue | undefined; } & TransformProps'
.ts(2345)

Instead ob Object, you should use at least P so it allows the original props of the component you are using.
Test Plan
Only Type checking is modified, so it does not affect the functionality.
Compatibility
Not aplicable
Checklist

[ ] I have tested this on a device and a simulator
[ ] I added documentation in README.md
[x ] I updated the typed files (typescript)
[ ] I added a test for the API in the __tests__ folder

@fauri13 it seems that the job is failing. Could you take a look at it locally and resolve it?

@fauri13 it seems that the job is failing. Could you take a look at it locally and resolve it?

I've changed the other types as well, now it's compiling.

repo: software-mansion/react-native-svg