https://github.com/evcc-io/evcc/issues/new?assignees=&labels=&projects=&template=bug_report.yaml

Describe the bug
After updating evcc to a newer version than 0.122.1 the addon start failes always.
I am a sponsor, so I decided to raise this issues after several months to get the benefits as sponsor ;-)
Hardware: Raspi 4
Steps to reproduce

install newer version than evcc 0.122.1
automatic restart of the addon
often not always after several restarts I was able to assign the evcc admin password

evcc does not start with full screen info:

...
Configuration details
network:
  # schema is the HTTP schema
  # setting to `https` does not enable https, it only changes the way URLs are generated
  schema: http
  # host is the hostname or IP address
  # if the host name contains a `.local` suffix, the name will be announced on MDNS
  # docker: MDNS announcements don't work. host must be set to the docker host's name.
  host: homeassistant.local
  # host: evcc.local
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 30s # control cycle interval - < 30 sec könnte System zum Schwingen bringen

# database configuration for persisting charge sessions and settings
# database:
#   type: sqlite
#   dsn: <path-to-db-file>

# sponsor token enables optional features (request at https://sponsor.evcc.io)
sponsortoken: <...>
# telemetry enables aggregated statistics
#
# Telemetry allows collecting usage data (grid and green energy, charge power).
# Data is aggregated, no individual charging sessions are tracked. The collected,
# anonymous data can be retrieved using https://api.evcc.io.
#
# See https://github.com/evcc-io/evcc/pull/4343 or details.
#
# For time being, this is only available to sponsors, hence data is associated with
# the sponsor token's identity.
#
# telemetry: true
# used for sharing data
plant: <...>

# log settings
log: info
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  cache: error
  db: error

# modbus proxy for allowing external programs to reuse the evcc modbus connection
# each entry will start a proxy instance at the given port speaking Modbus TCP and
# relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP)
modbusproxy:
  #  - port: 5200
  #    uri: solar-edge:502
  #    # rtu: true
  #    # readonly: true

# meter definitions
# name can be freely chosen and is used as reference when assigning meters to site and loadpoints
# for documentation see https://docs.evcc.io/docs/devices/meters
meters:
  - name: my_rct_grid
    type: template
    template: rct-power
    usage: grid
    host: xxx.xxx.xxx.xx
  - name: my_rct_pv
    type: template
    template: rct-power
    usage: pv
    host: xxx.xxx.xxx.xx
  - name: my_rct_battery
    type: template
    template: rct-power
    usage: battery
    host: xxx.xxx.xxx.xx
    capacity: 8.64
  # - name: my_fritz_pv1 # Bluetti
  #  type: template
  #  template: fritzdect
  #  usage: pv
    #uri: https://fritz.box # Optional
  #  user: <...>
  #  password: <...>
  #  ain: <...>
  # raw config for leading ain: "0..": refer to https://github.com/evcc-io/evcc/issues/6399#issuecomment-1442459448
  - name: my_fritz_pv2 # Sued1
    type: template
    template: fritzdect
    usage: pv
    #uri: https://fritz.box # Optional
    user: <...>
    password: <...>
    ain: <...>
  - name: my_fritz_pv3 # Nachfuehrung
    type: template
    template: fritzdect
    usage: pv
    #uri: https://fritz.box # Optional
    user: homeassistant
    password: greenHouse#2023
    ain:<PHONE_NUMBER>05
#  - name: my_fritz_pv4
#    type: template
#    template: fritzdect
#    usage: pv
#    #uri: https://fritz.box # Optional
#    user: homeassistant
#    password: greenHouse#2023
#    ain:<PHONE_NUMBER>56
  - name: my_deye_biohort
    type: custom
    power: # power (W)
      source: mqtt # plugin type
      topic: sensor/inverters/deye_biohort_total_ac_output_power_active
      timeout: 360s
  - name: my_deye_sud_3
    type: custom
    power: # power (W)
      source: mqtt # plugin type
      topic: sensor/inverters/deye_sud_3_total_ac_output_power_active
      timeout: 360s
  - name: my_bluetti_battery
    type: custom
    power: # power (W)
      source: mqtt # plugin type
      # topic: bluetti/state/AC200M-2236008116154/dc_output_power
      # nachfolgender Wert scheint noch nicht übernommen zu werden
      topic: sensor/ac200max/ac200m_dc_output_power_2
      timeout: 360s # don't accept values older than timeout
      # scale: 0.001 # floating point factor applied to result, e.g. for Wh to kWh conversion
      scale: 0.9 # negativ "charging"; positiv "discharging" - 90% efficiency after inverter
    soc: # optional battery soc (%)
      source: mqtt # plugin type
      # topic: bluetti/state/AC200M-2236008116154/total_battery_percent
      # nachfolgender Wert scheint noch nicht übernommen zu werden
      topic: sensor/ac200max/ac200m_total_battery_percent_2
      timeout: 360s # don't accept values older than timeout
    # currents: # optional currents (A)
    #  - source: # L1 plugin type
    #  - source: # L2 plugin type
    #  - source: # L3 plugin type
    capacity: 3.7
# charger definitions
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for documentation see https://docs.evcc.io/docs/devices/chargers
chargers:
  - name: my_charger
    type: template
    template: go-e-v3
    host: xxx.xxx.xxx.xx

# vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for documentation see https://docs.evcc.io/docs/devices/vehicles
vehicles:
  - name: IONIQ_5
    type: template
    template: hyundai
    title: "IONIQ 5" # Wird in der Benutzeroberfläche angezeigt # Optional
    user: <....>
    password: <...>
    #vin: # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind # Optional
    capacity: 72 # Akkukapazität in kWh # Optional
    phases: 3
    minCurrent: 6
    maxCurrent: 16
    identifiers:
      - "Michael Ioniq 5" # RFID token ID
      - "Christin Ioniq 5" # RFID token ID
    language: en # 'de' für Deutsch und 'en' für Englisch # Optional
  - name: FIAT_500e
    type: template
    template: offline
    title: "FIAT 500e" # Wird in der Benutzeroberfläche angezeigt # Optional
    capacity: 24 # Akkukapazität in kWh # Optional
    phases: 1
    minCurrent: 8
    maxCurrent: 16
    identifiers:
      - "Michael 500e" # RFID token ID
      - "Christin 500e" # RFID token ID
  - name: FIAT_500e_La_Prima
    type: template
    template: offline
    title: "FIAT 500e La Prima" # Wird in der Benutzeroberfläche angezeigt # Optional
    capacity: 42 # Akkukapazität in kWh # Optional
    phases: 3
    minCurrent: 6
    maxCurrent: 16
    identifiers:
      - "Peppino" # RFID token ID
  - name: Greenhouse_Gast
    type: template
    template: offline
    title: "Greenhouse Gast" # Wird in der Benutzeroberfläche angezeigt # Optional
    # capacity: 24 # Akkukapazität in kWh # Optional
    phases: 1
    minCurrent: 8
    maxCurrent: 16
    identifiers:
      - "Gast" # RFID token ID
    # site describes the EVU connection, PV and home battery
site:
  title: Greenhouse # display name for UI
  meters:
    grid: my_rct_grid # grid meter
    pv: # list of pv inverters/ meters
      - my_rct_pv
      # - my_fritz_pv1
      - my_fritz_pv2
      - my_fritz_pv3
      #- my_fritz_pv4
      - my_deye_biohort
      - my_deye_sud_3
      #- my_deye_inverters
    battery: # list of battery meters
      - my_rct_battery
      - my_bluetti_battery
    #aux:
  residualPower: 400 # standard house consumption
#  prioritySoc: 60 # obsolete - give home battery priority up to this soc (empty to disable)
#  bufferSoc: 95 # obsolete - ignore home battery discharge above soc (empty to disable)

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Abstellplatz # display name for UI
    charger: my_charger # charger
    # meter: # charge meter
    mode: pv # set default charge mode, use "off" to disable by default if charger is publicly available
    vehicle: FIAT_500e # set default vehicle (disables vehicle detection)
    #resetOnDisconnect: true # set defaults when vehicle disconnects
    phases: 0 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
#    minCurrent: 6 # minimum charge current (default 6A) - deprecated
#    maxCurrent: 16 # maximum charge current (default 16A) - deprecated

    # remaining settings are experts-only and best left at default values
    # priority: # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
    soc:
      # polling defines usage of the vehicle APIs
      # Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery
      # or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.
      poll:
        # poll mode defines under which condition the vehicle API is called:
        #   charging: update vehicle ONLY when charging (this is the recommended default)
        #   connected: update vehicle when connected (not only charging), interval defines how often
        #   always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
        mode: charging
        # poll interval defines how often the vehicle API may be polled if NOT charging
        interval: 60m
      estimate: true # set false to disable interpolating between api updates (not recommended)
    enable: # pv mode enable behavior
      delay: 1m # threshold must be exceeded for this long
      threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
    disable: # pv mode disable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)
    guardDuration: 5m # switch charger contactor not more often than this (default 5m)

# tariffs are the fixed or variable tariffs
# cheap (tibber/awattar) can be used to define a tariff rate considered cheap enough for charging
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type: fixed
    price: 0.5027 # EUR/kWh
    zones:
      - days: Mo-Fr
        hours: 2-5
        price: 0.5027 # EUR/kWh
      - days: Sa,So
        price: 0.5027 # EUR/kWh

    # # or variable via tibber
    # type: tibber
    # cheap: 0.2 # EUR/kWh
    # token: "476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4" # access token
    # homeid: "cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c" # optional if multiple homes associated to account

    # # or variable via awattar
    # type: awattar
    # cheap: 0.2 # EUR/kWh
    # region: de # optional, choose at for Austria
  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.10 # EUR/kWh
  planner:
    # planner tariff can be used for target charging if not grid tariff is specified
    # GrünStromIndex (Germany only) or ElectricityMaps provide CO2 intensity forecast

    # type: grünstromindex
    # zip: <zip>

    # type: electricitymaps
    # uri: <uri>
    # token: <token>
    # zone: DE

# mqtt message broker
mqtt:
  broker: localhost:1883
  topic: evcc # root topic for publishing, set empty to disable
  user: mqttuser
  password: greenHouse

# influx database
influx:
  # url: http://localhost:8086
  # database: evcc
  # user:
  # password:

# eebus credentials
eebus:
  # uri: # :4712
  # interfaces: # limit eebus to specific network interfaces
  # - en0
  # certificate: # local signed certificate, required, can be generated via `evcc eebus-cert`
  #   public: # public key
  #   private: # private key

# push messages
messaging:
  events:
    start: # charge start event
      title: Charge started
      msg: Started charging in "${mode}" mode
    stop: # charge stop event
      title: Charge finished
      msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
    connect: # vehicle connect event
      title: Car connected
      msg: "Car connected at ${pvPower:%.1fk}kW PV"
    disconnect: # vehicle connected event
      title: Car disconnected
      msg: Car disconnected after ${connectedDuration}
    soc: # vehicle soc update event
      title: Soc updated
      msg: Battery charged to ${vehicleSoc:%.0f}%
    guest: # vehicle could not be identified
      title: Unknown vehicle
      msg: Unknown vehicle, guest connected?
    error: # errors (deduplicated)
      title: "Error: {{ .error }}"
    warn: # warnings (deduplicated)
      title: "Warning: {{ .warn }}"
  services:
  # - type: pushover
  #   app: # app id
  #   recipients:
  #   - # list of recipient ids
  # - type: telegram
  #   token: # bot id
  #   chats:
  #   - # list of chat ids
  # - type: email
  #   uri: smtp://<user>:<password>@<host>:<port>/?fromAddress=<from>&toAddresses=<to>
  # - type: ntfy
  #   uri: https://<host>/<topics>
  #   priority: <priority>
  #   tags: <tags>

Log details
[site  ] INFO 2024/08/26 19:37:42 site config:
[site  ] INFO 2024/08/26 19:37:42   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2024/08/26 19:37:42     grid:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/08/26 19:37:42     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/08/26 19:37:42     pv 2:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/08/26 19:37:42     pv 3:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/08/26 19:37:42     pv 4:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/08/26 19:37:42     pv 5:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/08/26 19:37:42     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2024/08/26 19:37:42     battery 2: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2024/08/26 19:37:42   vehicles:
[site  ] INFO 2024/08/26 19:37:42     vehicle 1: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2024/08/26 19:37:42     vehicle 2: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2024/08/26 19:37:42     vehicle 3: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2024/08/26 19:37:42     vehicle 4: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[lp-1  ] INFO 2024/08/26 19:37:42 loadpoint 1:
[lp-1  ] INFO 2024/08/26 19:37:42   mode:        pv
[lp-1  ] INFO 2024/08/26 19:37:42   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2024/08/26 19:37:42   meters:      charge ✓
[lp-1  ] INFO 2024/08/26 19:37:42     charge:    power ✓ energy ✓ currents ✓
[lp-1  ] DEBUG 2024/08/26 19:37:42 phase timer inactive
[lp-1  ] DEBUG 2024/08/26 19:37:42 pv timer inactive
[lp-1  ] INFO 2024/08/26 19:37:42 vehicle updated: unknown -> FIAT 500e
[site  ] DEBUG 2024/08/26 19:37:42 ----
[lp-1  ] DEBUG 2024/08/26 19:37:42 charge power: 0W
[lp-1  ] DEBUG 2024/08/26 19:37:42 charge currents: [0 0 0]A
[main  ] INFO 2024/08/26 19:37:42 new version available: 0.130.4
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2024/08/26 19:40:40 evcc 0.130.3
[main  ] INFO 2024/08/26 19:40:40 using config file: /config/evcc.yaml
[mqtt  ] INFO 2024/08/26 19:40:41 connecting evcc-2070517360 at tcp://localhost:1883
[main  ] INFO 2024/08/26 19:40:41 listening at :7070
[lp-1  ] DEBUG 2024/08/26 19:40:42 charge total import: 4521.571kWh
[site  ] WARN 2024/08/26 19:40:44 vehicle 'FIAT 500e' does not support automatic detection
[site  ] WARN 2024/08/26 19:40:44 vehicle 'FIAT 500e La Prima' does not support automatic detection
[site  ] WARN 2024/08/26 19:40:44 vehicle 'Greenhouse Gast' does not support automatic detection
[site  ] INFO 2024/08/26 19:40:44 site config:
[site  ] INFO 2024/08/26 19:40:44   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2024/08/26 19:40:44     grid:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/08/26 19:40:44     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/08/26 19:40:44     pv 2:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/08/26 19:40:44     pv 3:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/08/26 19:40:44     pv 4:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/08/26 19:40:44     pv 5:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/08/26 19:40:44     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2024/08/26 19:40:44     battery 2: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2024/08/26 19:40:44   vehicles:
[site  ] INFO 2024/08/26 19:40:44     vehicle 1: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2024/08/26 19:40:44     vehicle 2: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2024/08/26 19:40:44     vehicle 3: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2024/08/26 19:40:44     vehicle 4: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[lp-1  ] INFO 2024/08/26 19:40:44 loadpoint 1:
[lp-1  ] INFO 2024/08/26 19:40:44   mode:        pv
[lp-1  ] INFO 2024/08/26 19:40:44   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2024/08/26 19:40:44   meters:      charge ✓
[lp-1  ] INFO 2024/08/26 19:40:44     charge:    power ✓ energy ✓ currents ✓
[lp-1  ] DEBUG 2024/08/26 19:40:44 phase timer inactive
[lp-1  ] DEBUG 2024/08/26 19:40:44 pv timer inactive
[lp-1  ] INFO 2024/08/26 19:40:44 vehicle updated: unknown -> FIAT 500e
[main  ] INFO 2024/08/26 19:40:44 new version available: 0.130.4
[site  ] DEBUG 2024/08/26 19:40:44 ----
[lp-1  ] DEBUG 2024/08/26 19:40:44 charge power: 0W
[lp-1  ] DEBUG 2024/08/26 19:40:44 charge currents: [0 0 0]A
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2024/08/26 19:43:42 evcc 0.130.3
[main  ] INFO 2024/08/26 19:43:42 using config file: /config/evcc.yaml
[mqtt  ] INFO 2024/08/26 19:43:43 connecting evcc-1642149322 at tcp://localhost:1883
[main  ] INFO 2024/08/26 19:43:43 listening at :7070
[lp-1  ] DEBUG 2024/08/26 19:43:45 charge total import: 4521.571kWh
[site  ] WARN 2024/08/26 19:43:46 vehicle 'FIAT 500e' does not support automatic detection
[site  ] WARN 2024/08/26 19:43:46 vehicle 'FIAT 500e La Prima' does not support automatic detection
[site  ] WARN 2024/08/26 19:43:46 vehicle 'Greenhouse Gast' does not support automatic detection
[site  ] INFO 2024/08/26 19:43:46 site config:
[site  ] INFO 2024/08/26 19:43:46   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2024/08/26 19:43:46     grid:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/08/26 19:43:46     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/08/26 19:43:46     pv 2:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/08/26 19:43:46     pv 3:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/08/26 19:43:46     pv 4:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/08/26 19:43:46     pv 5:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/08/26 19:43:46     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2024/08/26 19:43:46     battery 2: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2024/08/26 19:43:46   vehicles:
[site  ] INFO 2024/08/26 19:43:46     vehicle 1: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2024/08/26 19:43:46     vehicle 2: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2024/08/26 19:43:46     vehicle 3: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[site  ] INFO 2024/08/26 19:43:46     vehicle 4: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[lp-1  ] INFO 2024/08/26 19:43:46 loadpoint 1:
[lp-1  ] INFO 2024/08/26 19:43:46   mode:        pv
[lp-1  ] INFO 2024/08/26 19:43:46   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2024/08/26 19:43:46   meters:      charge ✓
[lp-1  ] INFO 2024/08/26 19:43:46     charge:    power ✓ energy ✓ currents ✓
[lp-1  ] DEBUG 2024/08/26 19:43:46 phase timer inactive
[lp-1  ] DEBUG 2024/08/26 19:43:46 pv timer inactive
[lp-1  ] INFO 2024/08/26 19:43:46 vehicle updated: unknown -> FIAT 500e
[site  ] DEBUG 2024/08/26 19:43:46 ----
[lp-1  ] DEBUG 2024/08/26 19:43:46 charge power: 0W
[lp-1  ] DEBUG 2024/08/26 19:43:46 charge currents: [0 0 0]A
[main  ] INFO 2024/08/26 19:43:46 new version available: 0.130.5

What type of operating system are you running?
HomeAssistant Add-on
Version
0.130.3

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

@frog60 can you please fix the title?

Not quite sure what the issue is here.
Does evcc perma-restart? Log looks like this. Or is this a UI issue. Screenshots look strange.

Not quite sure what the issue is here. Does evcc perma-restart? Log looks like this. Or is this a UI issue. Screenshots look strange.

Right the UI looks strange. Sometimes it seems so that UI looks fine, but it restarts again.

Maybe it is just waiting for some external meter values via MQTT?
Will need better log.
Maybe just try evcc meter and see if it finishes output with no error whithin a few seconds.

"Evcc Meter" using ssh on cmd line?

We don‘t support the HA addon.


Alias is currently overwrote with no warning

Currently when reusing an alias it will overwrite the old contract id. Should we add a --force flag to allow this but fail otherwise?

The original implementation had --force, but Leigh suggested that we always replaced the contract id. Is there any real case where you wouldn't want to persist the latest contract id?

My feedback was that --force is confusing because it doesn't communicate the scope of what is being forced. An option like --force should be focused on the primary action being performed by a command which in this case is deploying the contract, and not related to an ancillary action being performed like saving an alias. Why: It's natural to see options related to their primary option. For example, if we add --force, this command looks like it forces deployment but is actually invalid:
$ stellar contract deploy --wasm ... --force

If we want aliases to not overwrite by default, then I think the path that results in a clearer API is:

Disallow overriding and add no options for overwriting
Add a rm command for removing the alias

I expect that someone interacting with a pubnet network is probably keeping a record of their contract addresses concretely somewhere that isn't just in these aliases given that it is a production use case, and that these aliases are more useful during development, in which case overwriting feels fine. We overwrite elsewhere.
We could output a log line, or a stderr output saying the alias is being ovewritten and what the old value was and new value, so if someone accidentally ovewrites they can fix it.


Simulst clean reimpl

Nearly ready at this point, just training and evaluating from scratch to verify correctness.

ASR and SimulST training work, now, after compatibility checks. Just have to double check eval after SimulST training finishes.

Reduced set eval completed and looked fine at a glance.


Fix Kevm tests broken by function matching instead of unification

See https://office.runtimeverification.com/jenkins/job/haskell-backend/job/master/219/

Most likely this fails because of #810 or #789, both of which timed out in out build system.

https://github.com/kframework/kore/pull/834 contains a test for this issue. Basically, we are trying to match f(A|->B M, A) against f(1|->1 2|->2, 2) and we are matching A|->B with 1|->1 and A with 2 which fails for the obvious reason.
We have two possible fixes:

Change matching to work in multiple steps (i.e. allow postponing matches). This can still fail, but it should work for most (all?) practical cases.
Revert to using unification.

What won't work:
1.

I am also inclined toward (1). We tried to get unification (2) working for function evaluation for a long time. It's not evident to me that we know how to make progress with (2). On the other hand, it seems like we have a good idea what is needed to make matching (1) work, so that seems less risky.
As far as grading the difficulty of matching candidates, I don't think we need to do anything fancy. If we only care about returning a single result from matching—which is what we want for function and simplification rules, at least—then I think we can grade every match candidate this way:

zero solutions: match fails
one solution: match succeeds, add the substitution to the solution
unknown number of solutions: defer this candidate

This misses a few matching solutions, such as when two candidates each have several possible solutions, but they only agree on one solution. However, I don't think we need to worry about that because I don't think anyone expects to be able to write rules like that.

Fixed by: #835


TimeoutException after extended clustered get/put test

I’m running a single-client 90/10 get/put test with a 16gb L2 cache and no L1 cache with 128 test threads.  After approx. 60-90 minutes we start getting TimeoutExceptions on the client, after which the client hangs – attempts to manually restart the client are unsuccessful.  The client and server are both using min/max 2gb heaps.

@kcleereman Raised pr https://github.com/ehcache/ehcache3/pull/1682 with the fix for this issue.


[Checkout UI React] Shipping methods are re-selected when adding or removing cart lines

Please list the package(s) involved in the issue, and include the version you are using
"@shopify/ui-extensions": "^2024.7.0"
"@shopify/ui-extensions-react": "^2024.7.0"
Describe the bug
Adding or removing cart lines in checkout causes a re-selection of the default Shipping method when used in a store with Checkout and Customer Accounts Extensibility preview.
Our Checkout UI Extension renders whenever a specific Shipping Method is selected during checkout. When that shipping method is selected, we render a ChoiceList that allows them to select a tip amount. We use applyCartLinesChange to add, remove, or update the tip amount depending on this choice.
The bug occurs when adding or removing a product as a cart line, it causes the default Shipping method to become re-selected. This does not occur when updating an existing cart line items quantities, only when adding or removing.
Steps to reproduce the behavior:

Create a development store with Checkout and Customer Accounts Extensibility preview
Ensure the store has a Shipping zone configured with a rate's price set to Free
Add another rate that's more expensive
Place the extension in the Checkout Editor or use the CLI to navigate to the extension preview
When the more expensive Shipping method is selected, render a component that will add products, or remove products from the cart
The default Shipping method will be re-selected upon a cartLine having been added or removed

Expected behavior
I expect that the chosen Shipping method will remain selected, despite the changes to the customer's cart lines.
Screenshots

Above is an example of a cartLine that we're adding. When these are added or removed, the bug occurs.

Above is an example of the Shipping methods. When selecting the bottom option, and then adding or removing a cart line item, the first option "Standard" becomes re-selected.
Additional context
This issue occurs when using a development store with the Checkout and Customer Accounts Extensibility preview, which is recommended by Shopify when developing Checkout UI Extensions for Shopify Plus stores.
In this preview store, placing the extension via the Checkout Editor results in this re-selection behavior. It also occurs when using the CLI to open the developer console, and navigating directly to the checkout extension. Both methods of activating the extension have this bug.
Interestingly, when experimenting with a development store that does not have the preview enabled, we are able to get the desired behavior if we navigate to the checkout extension via the CLI's developer console. No re-selection of Shipping methods occurs, which is our desired behavior. Unfortunately we want to test in a production environment where the CLI will not be available, and so have to use the Checkout Editor to place our extension, which is not possible without a Checkout and Customer Accounts Extensibility preview, so we want to find a fix.

@jamesvidler , This looks related to some things you were looking at with improving negotiations?


Simplify build by converting to go mod

use go mod to manage dependency
remove govendor
simplify bool expression as suggested by gopls

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


⚠ Turnos 24x7 has degraded performance

In 1a96746, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 809 ms

Resolved: Turnos 24x7 performance has improved in 2f35793.


Show chance to succeed when forming the dice pool

This PR adds a new feature to the Dice Prompt; it approximates the probability of succeeding the check given what's on the pool. This uses the Monte Carlo method to determine the probability instead of creating all the permutations since that is not feasible as the dice pool grows. Right now I'm uncertain if there's a better method given how the Genesys dice behave so give me some time to brush up on my knowledge; it's been too long since I took a statistics class. In the meantime this solution is more than acceptable.
This feature is enabled/tweaked per user since it has a direct impact on Foundry's performance. It's also possible to turn it of completely (this is the default). The Monte Carlo method works by simulating a bunch of rolls and analyzing the result, so the number the users input in the config corresponds to the amount of rolls performed.

The higher the number, the better the approximation. At 500, the performance isn't impacted that much (for my desktop specs) and the results are good. Compare the calculated approximation and the real probability in the images below:

I think this is a good WIP, but in order to improve performance and also get a more precise result, I would recommend taking a look at this repo and its webpage. It calculates the probabilities of various outcomes rather than approximating them by simulating a large number of rolls.

I think this is a good WIP, but in order to improve performance and also get a more precise result, I would recommend taking a look at this repo and its webpage. It calculates the probabilities of various outcomes rather than approximating them by simulating a large number of rolls.

That repo is a great find and it also collaborates what a friend of mine that studied stats told me. Basically I need the distribution of each dice and somehow combine them when a pool is built.
However, I really need to understand the math behind it before I even dare do an implementation. And I'm unwilling to simply do a port of the code in that repo for the same reason. But thanks again, this is a good reference for the future.


Use VS 2019 to build. Targeting VS 2015 - 2019

Several changes in this PR 😒 ...

Building with VS 2019
All changes related to Conan branding: icons, license,...
CI uses 2019 to build (and automatically uploads to VS marketplace)

...

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


GValue traits for Variant are implemented wrongly

See https://github.com/sdroege/gobject-subclass/pull/10#discussion_r198022635
Currently we use the glib_wrapper! macro, which will consider it a boxed type. It is however a fundamental type now and needs to have g_value_set_variant and g_value_get_variant used. See Note: GLib 2.24 did include a boxed type with this name. It was replaced with this fundamental type in 2.26. in the docs of G_TYPE_VARIANT

Solved since a year or so


permanent mac_bindig cause traffic blackhole

Hello!
I want to report a bug in patch for MAC_binding functionality, seems that it just adding but not updating or deleting MAC_Bindig rows.
https://github.com/ovn-org/ovn/commit/a2b88dc5136507e727e4bcdc4bf6fde559f519a9
In my setup I have logical router with DNAT rules.
Whenever I create or delete logical routers or DNAT rules on them with same IPs, I can see that MAC_Binding rows are not updated or deleted in SBDB.
Let me show some example of relationships between Port_Binding and Mac_Binding, which I expect to be properly served by OVN controller pinctrl module. But its not :(

DNAT rule added
Port_Binding

_uuid               : 7c16e012-5acc-498e-b656-79a19f5bb4d1
chassis             : 1f4aa70f-804a-4e98-b8ba-22db389be1e2
datapath            : 09b37624-d7d2-4a21-8758-3809ae319f62
encap               : []
external_ids        : {"neutron:cidrs"="<IP_ADDRESS>/24", "neutron:device_id"="9788b99d-351c-4741-92d3-2ee27ecd1e3f", "neutron:device_owner"="network:router_gateway", "neutron:network_name"=neutron-a0f9f5fd-e94b-44d9-a4b3-66082dd9dd5a, "neutron:port_name"="", "neutron:project_id"="", "neutron:revision_number"="1", "neutron:security_group_ids"="", "neutron:subnet_pool_addr_scope4"="", "neutron:subnet_pool_addr_scope6"=""}
gateway_chassis     : []
ha_chassis_group    : []
logical_port        : "ad363382-c4e1-42f1-a103-85a0decf8b73"
mac                 : [router]
nat_addresses       : ["fa:16:3e:a1:d9:1e <IP_ADDRESS>"] <<<< This field updated!!!
options             : {l3gateway-chassis=az14-network-2, peer=lrp-ad363382-c4e1-42f1-a103-85a0decf8b73, shadow-port="true"}
parent_port         : []
requested_chassis   : []
tag                 : []
tunnel_key          : 6
type                : l3gateway
up                  : true
virtual_parent      : []

MAC_binding
_uuid               : b05316bd-4293-44c1-890c-ca2ca869241d  <<<< This row OVN must create if not exist!
datapath            : 06cb9489-07d5-4328-8543-aab635b1d8d1
ip                  : "<IP_ADDRESS>"
logical_port        : lrp-8c60913e-1e3f-44fe-ba6e-49ecf6ced01e
mac                 : "fa:16:3e:a1:d9:1e"   <<<< This field OVN must update with new mac if row already exist!

DNAT rule deleted
Port_Binding

_uuid               : 7c16e012-5acc-498e-b656-79a19f5bb4d1
chassis             : 1f4aa70f-804a-4e98-b8ba-22db389be1e2
datapath            : 09b37624-d7d2-4a21-8758-3809ae319f62
encap               : []
external_ids        : {"neutron:cidrs"="<IP_ADDRESS>/24", "neutron:device_id"="9788b99d-351c-4741-92d3-2ee27ecd1e3f", "neutron:device_owner"="network:router_gateway", "neutron:network_name"=neutron-a0f9f5fd-e94b-44d9-a4b3-66082dd9dd5a, "neutron:port_name"="", "neutron:project_id"="", "neutron:revision_number"="1", "neutron:security_group_ids"="", "neutron:subnet_pool_addr_scope4"="", "neutron:subnet_pool_addr_scope6"=""}
gateway_chassis     : []
ha_chassis_group    : []
logical_port        : "ad363382-c4e1-42f1-a103-85a0decf8b73"
mac                 : [router]
nat_addresses       : [] <<<< This field cleared!!!
options             : {l3gateway-chassis=az14-network-2, peer=lrp-ad363382-c4e1-42f1-a103-85a0decf8b73, shadow-port="true"}
parent_port         : []
requested_chassis   : []
tag                 : []
tunnel_key          : 6
type                : l3gateway
up                  : true
virtual_parent      : []

MAC_binding
_uuid               : b05316bd-4293-44c1-890c-ca2ca869241d  <<<< This row OVN must destroy!
datapath            : 06cb9489-07d5-4328-8543-aab635b1d8d1
ip                  : "<IP_ADDRESS>"
logical_port        : lrp-8c60913e-1e3f-44fe-ba6e-49ecf6ced01e
mac                 : "fa:16:3e:a1:d9:1e"

Logical router added
Port_Binding

_uuid               : 4fba6716-0eb1-4cb2-ac57-66184939e623  <<<< This row created!
chassis             : 1f4aa70f-804a-4e98-b8ba-22db389be1e2
datapath            : 890aef9d-0dd6-48e5-935b-d07951143c37
encap               : []
external_ids        : {"neutron:network_name"=neutron-a0f9f5fd-e94b-44d9-a4b3-66082dd9dd5a, "neutron:revision_number"="1", "neutron:router_name"="9788b99d-351c-4741-92d3-2ee27ecd1e3f", "neutron:subnet_ids"="8525a5ff-7e20-40f1-a768-b82b30378ac2"}
gateway_chassis     : []
ha_chassis_group    : []
logical_port        : lrp-ad363382-c4e1-42f1-a103-85a0decf8b73
mac                 : ["fa:16:3e:a1:d9:1e <IP_ADDRESS>/24"]
nat_addresses       : []
options             : {chassis-redirect-port=cr-lrp-ad363382-c4e1-42f1-a103-85a0decf8b73, l3gateway-chassis=az14-network-2, peer="ad363382-c4e1-42f1-a103-85a0decf8b73"}
parent_port         : []
requested_chassis   : []
tag                 : []
tunnel_key          : 1
type                : l3gateway
up                  : true
virtual_parent      : []

MAC_binding
_uuid               : f3435a82-05f8-4c08-8689-6ebbc4f6c7b4  <<<< This row OVN must create if not exist!
datapath            : 06cb9489-07d5-4328-8543-aab635b1d8d1
ip                  : "<IP_ADDRESS>"
logical_port        : lrp-8c60913e-1e3f-44fe-ba6e-49ecf6ced01e
mac                 : "fa:16:3e:a1:d9:1e"  <<<< This filed OVN must update with new mac if row already exist!

Logical router deleted
Port_Binding

_uuid               : 4fba6716-0eb1-4cb2-ac57-66184939e623  <<<< This row deleted!
chassis             : 1f4aa70f-804a-4e98-b8ba-22db389be1e2
datapath            : 890aef9d-0dd6-48e5-935b-d07951143c37
encap               : []
external_ids        : {"neutron:network_name"=neutron-a0f9f5fd-e94b-44d9-a4b3-66082dd9dd5a, "neutron:revision_number"="1", "neutron:router_name"="9788b99d-351c-4741-92d3-2ee27ecd1e3f", "neutron:subnet_ids"="8525a5ff-7e20-40f1-a768-b82b30378ac2"}
gateway_chassis     : []
ha_chassis_group    : []
logical_port        : lrp-ad363382-c4e1-42f1-a103-85a0decf8b73
mac                 : ["fa:16:3e:a1:d9:1e <IP_ADDRESS>/24"]
nat_addresses       : []
options             : {chassis-redirect-port=cr-lrp-ad363382-c4e1-42f1-a103-85a0decf8b73, l3gateway-chassis=az14-network-2, peer="ad363382-c4e1-42f1-a103-85a0decf8b73"}
parent_port         : []
requested_chassis   : []
tag                 : []
tunnel_key          : 1
type                : l3gateway
up                  : true
virtual_parent      : []

MAC_binding
_uuid               : f3435a82-05f8-4c08-8689-6ebbc4f6c7b4  <<<< This row OVN must destroy!
datapath            : 06cb9489-07d5-4328-8543-aab635b1d8d1
ip                  : "<IP_ADDRESS>"
logical_port        : lrp-8c60913e-1e3f-44fe-ba6e-49ecf6ced01e
mac                 : "fa:16:3e:a1:d9:1e"

So in the above examples I tried to create/delete logical routers with same external IP address twice, and traffic, when router created second time to its external IP, blackholed.
The same picture I can see when, some DNAT rules were added to first router then router deleted and then DNAT rules repeated on second router with same IPs - traffic blackholed again.
My setup:

OVN 22.03.3
OVS 2.17.7

Hi @ardenisov!  Thanks for your report!
CC: @almusil
It's however something we can't easily fix in the general case because mac bindings (ARP cache) are for IPs that may also be outside of OVN.
Partially related to this we added support for mac binding aging in 22.09:
https://github.com/ovn-org/ovn/commit/1a947dd3073
Quoting from the original bug report that triggered that change:
In OpenStack, we have been doing some tricks in the past to workaround
the limitation of MAC_Binding entries not expiring.

Some of those tricks involve not monitoring the MAC_Binding table at all
to avoid OOM killers [0] or delete the entries upon association/disassociation
of a Floating IP [1].

Ideally, old (or better, unused) entries should be deleted helping reduce the
size of the database but also avoiding issues when reusing IP addresses.

Would it be an option for you to upgrade to a version that has it and enable the feature?
Thanks,
Dumitru

seems that it just adding but not updating or deleting MAC_Bindig rows.

It does, please have a look at the ovn.at delete Mac bindings test. It works - no issues
Please have a look at the related issue also Issue-251
The only case that we fail to reproduce at the moment is snat/dnat adding/removal

Hi, what is the OVN version that you are testing the aging with? Also could you please show the relevant datapath bindings (3998ece8-bb0c-4070-948b-3127f49aca9b and 3998ece8-bb0c-4070-948b-3127f49aca9b) if they actually correspond to those two routers?

Hello, @almusil ! Sorry, I miss your request.
My setup was restored with different ids and issue reproduced:
I use 24.03 OVN version.
New setup is:
r1
_uuid               : c7698e88-019d-48dd-a6e8-97978f404624
copp                : []
enabled             : true
external_ids        : {}
load_balancer       : []
load_balancer_group : []
name                : neutron-ad7c01e9-b3c9-429b-9744-4cb0a24556b3
nat                 : [a13b62df-13af-40a5-aac6-82f410db70e6, da15b3c2-9f9c-48ef-ab7d-27e92e820a5e]
options             : {always_learn_from_arp_request="false", chassis=pd32-nsrv-006, dynamic_neigh_routers="true", mac_binding_age_threshold="5"}
policies            : []
ports               : [055e2390-891f-4c49-80ab-1d8466fc0735, a7f2a1a5-1e91-4cbe-b7ec-7cd48be0cae6, da099f13-2d94-4402-bc2d-c3a995f792c7]
static_routes       : [d72144e3-eeeb-4d14-ab2f-09e67a52886c]

r2:
_uuid               : c476e2ef-5cad-474c-8595-5ae6751ce3f8
copp                : []
enabled             : true
external_ids        : {}
load_balancer       : []
load_balancer_group : []
name                : neutron-63e4812c-8518-4076-9b52-554b2ed5d6eb
nat                 : [a2bc1bd4-c1ee-4402-9679-b4e2aefa3049, c2a28c7d-fd6a-41d9-b8d9-b9d39c0aa0ef]
options             : {always_learn_from_arp_request="false", chassis=pd32-nsrv-005, dynamic_neigh_routers="true", mac_binding_age_threshold="5"}
policies            : []
ports               : [2c548c50-735c-4b69-a58f-d05131074e73, 2f08362a-7822-4f7a-ac1f-c23104b80c5d]
static_routes       : [70140877-605b-4cf6-a23e-c2a7707fcea0, e1ed760c-3bec-4117-9f89-22f416e6ebd8]

p1:
_uuid               : 055e2390-891f-4c49-80ab-1d8466fc0735
enabled             : []
external_ids        : {}
gateway_chassis     : []
ha_chassis_group    : []
ipv6_prefix         : []
ipv6_ra_configs     : {}
mac                 : "fa:16:3e:ac:43:76"
name                : lrp-7c33c1cc-d60d-42ff-87a0-2a2f12364ab5
networks            : ["<IP_ADDRESS>/24"]
options             : {}
peer                : []
status              : {}

p2:
_uuid               : 2c548c50-735c-4b69-a58f-d05131074e73
enabled             : []
external_ids        : {}
gateway_chassis     : [ba621169-c551-4da2-a429-ed0057259eb0, c8365b35-1ba1-40b1-a90a-2b2d1ba2693d]
ha_chassis_group    : []
ipv6_prefix         : []
ipv6_ra_configs     : {}
mac                 : "fa:16:3e:f3:cf:0b"
name                : lrp-8bd496d6-acaa-416e-9042-54920959e72f
networks            : ["<IP_ADDRESS>/24"]
options             : {}
peer                : []
status              : {}

mac1:
_uuid               : 727a07a9-f83b-4087-bac1-b4186af9ddf7
datapath            : 497d0260-2754-4672-abf0-256bfd02cd17
ip                  : "<IP_ADDRESS>"
logical_port        : lrp-7c33c1cc-d60d-42ff-87a0-2a2f12364ab5
mac                 : "fa:16:3e:f3:cf:0b"
timestamp           :<PHONE_NUMBER>158

dp1:
_uuid               : 497d0260-2754-4672-abf0-256bfd02cd17
external_ids        : {always_learn_from_arp_request="false", logical-router="c7698e88-019d-48dd-a6e8-97978f404624", mac_binding_age_threshold="5"}
load_balancers      : []
tunnel_key          : 26

mac2:
_uuid               : 1f335763-aa6c-41aa-ae3e-59067257bb5f
datapath            : c36656c4-c46c-46e1-8d7c-9ff0d3dc1220
ip                  : "<IP_ADDRESS>"
logical_port        : lrp-8bd496d6-acaa-416e-9042-54920959e72f
mac                 : "fa:16:3e:ac:43:76"
timestamp           :<PHONE_NUMBER>192

dp2:
_uuid               : c36656c4-c46c-46e1-8d7c-9ff0d3dc1220
external_ids        : {always_learn_from_arp_request="false", logical-router="c476e2ef-5cad-474c-8595-5ae6751ce3f8", mac_binding_age_threshold="5"}
load_balancers      : []
tunnel_key          : 108

As you can see, mac_binding_age_threshold=5, but related mac_bindings alive as related router live without any traffic between them and timestamps don't updated.
I'll save this config for further investigation.


FIX: correct labels processing

Description

Motivation and Context

How Has This Been Tested?

That was hot-fixed at SMI.

Would like to experiment with the usability a little more before merging. Trying to get this working locally against a spoofed IOC....

Codecov Report

Merging #1037 into master will increase coverage by 0.01%.
The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master    #1037      +/-   ##
==========================================
+ Coverage   89.45%   89.46%   +0.01%
==========================================
  Files          50       50
  Lines        8371     8371
==========================================
+ Hits         7488     7489       +1
+ Misses        883      882       -1

Impacted Files
Coverage Δ

bluesky/magics.py
84.61% <87.5%> (+0.51%)
:arrow_up:

Continue to review full report at Codecov.

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

OK, I think this is a decent second pass. If this behavior seems sensible to you all, let's merge it and get a bug-fix release out. Future iterations may follow as we try to use it more in the wild.
Example configuration:
from ophyd import EpicsMotor, Device, Signal, Component
mtr = EpicsMotor('', name='mtr', labels={'motors'})
from bluesky.magics import BlueskyMagics
get_ipython().register_magics(BlueskyMagics)

class Thing(Device):
    a = Component(EpicsMotor, '')
    b = Component(EpicsMotor, '')

class ThingHaver(Device):
    tA = Component(Thing)
    tB = Component(Thing, labels={'favorites'})

th = ThingHaver(name='th', labels={'motors', 'things'})
s = Signal(name='s', labels={'motors', 'favorites', 'stuff'})

Output:
In [2]: %wa
motors
  Positioner                     Value       Low Limit   High Limit  Offset
  mtr                            0           0           0           0
  th_tA_a                        0           0           0           0
  th_tA_b                        0           0           0           0
  th_tB_a                        0           0           0           0
  th_tB_b                        0           0           0           0

  Local variable name                    Ophyd name (to be recorded as metadata)
  mtr                                    mtr
  th                                     th
  s                                      s

things
  Positioner                     Value       Low Limit   High Limit  Offset
  th_tA_a                        0           0           0           0
  th_tA_b                        0           0           0           0
  th_tB_a                        0           0           0           0
  th_tB_b                        0           0           0           0

  Local variable name                    Ophyd name (to be recorded as metadata)
  th                                     th

favorites
  Positioner                     Value       Low Limit   High Limit  Offset
  th_tB_a                        0           0           0           0
  th_tB_b                        0           0           0           0

  Local variable name                    Ophyd name (to be recorded as metadata)
  th.tB                                  th_tB
  s                                      s

stuff
  Local variable name                    Ophyd name (to be recorded as metadata)
  s                                      s

I like the updates.

Closes #828 only 9 months late. Sorry for the long wait on that, @afluerasu and @ambarb.

Self-merged with @tacaswell and @mrakitin's blessing via Slack. Moving on to tag a micro release....


fixed the icon lmao

sorry for formatting btw

Dude, I don't want to be rude, but please refrain from autoformatting the whole index with your different code-style...
Besides why do you want to add spaces in strings like rel="stylesheet " or here width="32 " height="32 "?
I've added a favicon-pregenerated preset in https://github.com/ranimepiracy/index/commit/53f8d8699c230fceafc9b49a67b033d39d323c6b and as I see no real changes or benefits I'll close this PR. But feel free to contribute any other worthwhile changes 👍

Dude, I don't want to be rude, but please refrain from autoformatting the whole index with your different code-style...
Besides why do you want to add spaces in strings like rel="stylesheet " or here width="32 " height="32 "?
I've added a favicon-pregenerated preset in https://github.com/ranimepiracy/index/commit/53f8d8699c230fceafc9b49a67b033d39d323c6b and as I see no real changes or benefits I'll close this PR. But feel free to contribute any other worthwhile changes 👍

Dude, I don't want to be rude, but please refrain from autoformatting the whole index with your different code-style...
Besides why do you want to add spaces in strings like rel="stylesheet " or here width="32 " height="32 "?

Yeah sorry about that, I realize that makes it hard to use pull requests, If I continue to add PRs I'll disable my autoformatting

Dude, I don't want to be rude, but please refrain from autoformatting the whole index with your different code-style...
Besides why do you want to add spaces in strings like rel="stylesheet " or here width="32 " height="32 "?

Yeah sorry about that, I realize that makes it hard to use pull requests, If I continue to add PRs I'll disable my autoformatting

You should definetly use autoformatting, but you can adjust the project-setting in vs.
Doing formatting by hand is really not the way to go...

You should definetly use autoformatting, but you can adjust the project-setting in vs.
Doing formatting by hand is really not the way to go...


Feature: add features to safe apps

This PR:

Implements https://github.com/safe-global/safe-config-service/issues/755 by creating a new table for safe app features with a many to many relationship

I have read the CLA Document and I hereby sign the CLA

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

25 of 25 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 99.778%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
900

Relevant Lines:
902

💛  - Coveralls


Fails in strict mode

Module build failed: SyntaxError: <path> 'with' in strict mode
lodash's template uses with.
Is there any workaround? I'm surprised that I'm the only one with this issue.
{
    test: /\.ejs/,
    loader: 'ejs-loader',
    include: path.join(sourceDir, '_assets', 'javascripts', 'templates')
}

Using import 'template_name.ejs' to include it.

I'm not using this module ATM so can't verify it. Can you create a repo where this is reproducible? Or even better, submit a fix in a PR. Thanks!

This happens for me as well. It occurs when you don't specify a variable in your query.

this happens with me as well. I am using ejs-loader for jest testing tranformation

This is a fundamental issue with lodash's template compiler. Lodash does not plan to resolve the issue, as seen on https://github.com/lodash/lodash/issues/3709#issuecomment-375898111. If you wish to use ES6 strict mode with ejs-loader, you can pass the new exportAsESM option into the loader. This will work fine as long as variable is provided in the options


jestrunner.codeLensSelector doesn't work

Hi!
I've modified this setting:
"jestrunner.codeLensSelector": "**/*-{test,acceptance-test}.{js,jsx,ts,tsx}"
But I can't see "run jest option" in explore/context:

It looks like default value can't be overwritten

unsure why it is not working for you.
here is the source code:
https://github.com/firsttris/vscode-jest-runner/blob/24bb70702e47943d855bee8724286bab9f9317da/src/extension.ts#L65
this is the provided default value:
https://github.com/firsttris/vscode-jest-runner/blob/master/package.json#L96
which is working otherwise it would not work at all wouldnt it?

Perhaps related is what I have been observing:
If I use this in my test code:
import testJSON from '../../../test/config.json';
... the 'Run | Debug' codelenses appear in my code.
If I include this import assertion however, which is supported in Node v18:
import testJSON from '../../../test/config.json' assert { type: 'json' };
...the codelenses disappear.
@andyindahouse Is there anything in your actual test which not widely supported yet?
@firsttris I'd like to keep using import assertions, is there something in the configuration of the extension which will allow for this?
Thanks.

@aligg73 probably the babel parser for jest used by the extension (provided by jest-editor-support) is not supporting this feature yet and crashing as a result.

Jest-editor-support has unit tests for various features / plugins. you can check if this feature is already included.

which is working otherwise it would not work at all wouldnt it?

The default value is working "**/*.{test,spec}.{js,jsx,ts,tsx}"

Perhaps related is what I have been observing:
If I use this in my test code: import testJSON from '../../../test/config.json';  ... the 'Run | Debug' codelenses appear in my code. If I include this import assertion however, which is supported in Node v18:
import testJSON from '../../../test/config.json' assert { type: 'json' };  ...the codelenses disappear. @andyindahouse Is there anything in your actual test which not widely supported yet?
@firsttris I'd like to keep using import assertions, is there something in the configuration of the extension which will allow for this?
Thanks.

Nope, there aren't anything unusual. It's a normal test in TS.
Furthermore if I change the name of my test to fit in the default glob format, It works fine.
@firsttris Have you ever tried to change the default case? Does it works for you? 🤔

you can run the extension in development mode (see readme.md)
check if it crashes inside this try-catch
https://github.com/firsttris/vscode-jest-runner/blob/master/src/JestRunnerCodeLensProvider.ts#L58

+1 overriding the default glob pattern doesn't work


chore: bump Go version to 1.16

1.16 ensures that we retain compatibility with Podman.

@snprajwal We usually use the name of the file or directory that is changed as a prefix to the commit subject line.
https://github.com/checkpoint-restore/criu/blob/criu-dev/CONTRIBUTING.md#describe-your-changes
This makes it easier to understand the changes in every commit when reviewing the history with git log --oneline.
Would it be possible to use go.mod: bump Go version to 1.16 instead?


Bracket Pair Colorization - Match active scope ruler and underline color to the brackets color

Hi,
I love the new feature! But I miss the option to have the indent guide ruler of the current scope/closure colorized the same color as the closing brackets. Also, it would be great to have underlined with the same color the closure opening line (such as a method or if condition header).
This styling option is available in the former Bracket Pair Colorizer extension and I would love to see integrated into the new feature in VS Code. It looked like this:

Thanks!

Your first request appears to be on the way - see PR #133509
/assign @hediet

Duplicate of #131001.


$ is not recognized as a valid escape

-define(prx,"login: |Password: |\\\$ |> ").

from https://github.com/lumen/otp/blob/ca83f680aab717fe65634247d16f18a8cbfc6d8d/lib/common_test/src/unix_telnet.erl#L29
Pygment also thinks it is a bad escape, but the problem is that erlc will accept it, so we need to match that.

Superseded by #617


Feature Request: !attic <COURSE_CODE>

returns all the files found in the course's uqattic drive folder

Could !attic alone just link the root directory of the drive?

sure it could, but where's the fun in that? ;)

oh I see, you're saying for an empty option-- that's a good idea :^)

I actually did this in #217, but needs to be ported to python in #259. Will close for now as that issue will track completion.


Fix byte[] and HttpData conversion

Motivation:
The following annotated service method will fail because
ByteArrayResponseConverterFunction currently does not convert byte[]
or HttpData with the content type other than
application/octet-stream or application/binary.
Modifications:

Convert byte[] or HttpData even if the content type is neither
application/octet-stream nor application/binary.
Also fix the case where byte[] or HttpData is not converted when a
service method produces text content.

Result:

Fixes #1999

For @tobias-


Not able to Pay all Withdrawal requests

I run centos 6, all working good, I even integrated a dice game.
My probleme in admin panel, I'm not able to make All payments. I see good balance of Asmoney, that's mean connection good! Here error I get :
Notice: Undefined index: settings in /var/www/html/faucet/includes/function.php on line 79
Notice: Use of undefined constant FILE - assumed 'FILE' in /var/www/html/faucet/maincore.php on line 73
I'm using Namecheap as domain with Masked redirect.
If you help I share the dice here as a pull request :)

changed :
define(FILE,basename(basename($_SERVER['SCRIPT_FILENAME']),'.php'));  for :
define('FILE',basename(basename($_SERVER['SCRIPT_FILENAME']),'.php'));  fixed the :
Notice: Use of undefined constant FILE - assumed 'FILE' in /var/www/html/faucet/maincore.php on line 73

Was API limitation.


update registration logic to support import command w/signoff

Description
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

https://github.com/meshery/meshery/pull/11354

Please fix lint checks.


Adding parent_tree_number,tested_parent_tree_cont_pct to database and geographic data columns

Although the parent_tree_id is stored on seedlot_parent_tree, seedlot_parent_tree_gen_qlty, smp_mix, smp_mix_gen_qlty, and seedlot_parent_tree_smp_mix tables, the value showed on screens that the user will work is the parent_tree_number, and those values are not stored anywhere on the database. The column should be created on seedlot_parent_tree and smp_mix tables. IMPORTANT: After migrating the parent tree table management feature to the new SPAR application and consequently the paret_tree table, columns should be dropped from those two tables, and data should be fetched from parent_tree table using joins.
The tested parent tree contribution percentage is related to each Genetic Worth trait and should be stored on seedlot_genetic_worth table. Currently, it is stored on seedlot table.
Also, adding the columns related to geographic data defined on:
https://apps.nrs.gov.bc.ca/int/confluence/display/FSADT2/Defining+Seedlot+Geographic+data

Just need to check with Sabina if we are keeping the latitude and longitude code, as they are always equal to 'N' and 'W'.


Add nexus variables to the gradle task environment

Currently the gradle task do not set the nexus variable to the environment.
We need to add these variables, so enable gradle builds to pull 3rd party dependencies from nexus.

Probably not related but see also #327

Duplicated by #373 and now fixed.


Optimise/refine case-*/word/space icons

Optimisations from #1023. Also related to #1041.
Plus following #1191, as mentioned in https://github.com/lucide-icons/lucide/pull/1191#issuecomment-1531675386 …

I think it hurts overall legibility.

Agreed that 2px radius might, but not so sure 1px harms legibility… What do you think @karsa-mistmere?

case-upper is a real fun one when thrown into the optimizer.
https://lucide-site-git-feat-added-edit-page-jguddas.vercel.app/edit/lucide-icons/lucide/case-upper?PHN2ZwogIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIKICB3aWR0aD0iMjQiCiAgaGVpZ2h0PSIyNCIKICB2aWV3Qm94PSIwIDAgMjQgMjQiCiAgZmlsbD0ibm9uZSIKICBzdHJva2U9ImN1cnJlbnRDb2xvciIKICBzdHJva2Utd2lkdGg9IjIiCiAgc3Ryb2tlLWxpbmVjYXA9InJvdW5kIgogIHN0cm9rZS1saW5lam9pbj0icm91bmQiCj4KICA8bGluZSB4MT0iNCIgeTE9IjEzIiB4Mj0iMTAiIHkyPSIxMyIgLz4KICA8cG9seWxpbmUgcG9pbnRzPSIzLDE1IDcsNyAxMSwxNSIgLz4KICA8cGF0aCBkPSJNMTUgN2g0YzEuMSAwIDIgLjkgMiAycy0uOSAyLTIgMmgtNFY3eiIgLz4KICA8cGF0aCBkPSJNMTUgMTFoNC41YzEuMSAwIDIgLjkgMiAycy0uOSAyLTIgMkgxNXYtNHoiIC8+Cjwvc3ZnPg==

I'm, ok with this change!


Prevent infinite loop in PipelineExtensions.PeekAsyncAwaited() (#1827)

#1827

Make sure you file an issue on pipes in corefxlab

@davidfowl https://github.com/dotnet/corefxlab/issues/1540

@davidfowl Can you take another look? I realized I should have done the same change to the "non-awaited"  method too.


boards: arduino_101: remove mention of boot stub

The stub is used for testing only and is not compatible anymore with the
usage documented here.
Fixed #9772
Signed-off-by: Anas Nashif<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #9807   +/-   ##
=======================================
  Coverage   52.24%   52.24%
=======================================
  Files         212      212
  Lines       25951    25951
  Branches     5593     5593
=======================================
  Hits        13557    13557
  Misses      10159    10159
  Partials     2235     2235

Continue to review full report at Codecov.

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


use of debounce-promise with React. (TypeError: Object(...) is not a function)

In the first attempt to use the debounce-promise with a React component, I'm encountering the following error that can be seen in the screenshot below, also follows the code used, what am I missing?

import React, { Component } from 'react';
import { connect } from 'react-redux';
import { fetchUser } from './actions';
import { debounce } from 'debounce-promise';

    class App extends Component {
	constructor(props) {
		super(props);

const _searchAsyncDebounced = debounce(async text => props.fetchUser(text), 500);

		this.handleTextChange = async event => {
			const imageUrl = await _searchAsyncDebounced(event.target.value);
			this.setState({ imageUrl });
		};
	}

	render() {
		let image = '';
		if (this.state.imageUrl) image = ;
		return (

Github Search:

				<input placeholder="Username" onChange={this.searchUser} />

{image}

		);
	}
}

const mapStateToProps = state => ({
	image: state.user.avatar_url,
});

const mapDispatchToProps = {
	fetchUser,
};

export default connect(
	mapStateToProps,
	mapDispatchToProps
)(App);

Looks like a named vs default import issue and is unrelated to React.
Try
import debounce from 'debounce-promise'


SDK Does Not Respect Configured Timeout

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug
In the case of ServiceUnavailable (503) error when querying database, the SDK doesn't respect the configured timeout. Timeout is configured during client initialization using CosmosClientOptions.RequestTimeout property.
CosmosClientOptions cosmosClientOptions = new CosmosClientOptions()             {                 RequestTimeout = 500             };
To Reproduce
Expected behavior
SDK should terminate the call and return control to the caller once request time exceeds the configured timeout.
Actual behavior
SDK doesn't terminate the call and blocks the caller for much more time than what it is configured during client initialization.
Environment summary
SDK Version: cosmos-netstandard-sdk/3.23.1
OS Version Windows/10.0.17763
Additional context
cosmosDbClientLogs.txt

@aavasthy Can you take a look at the attached diagnostics and reply to this question?

@Jasen-Quadras
"RequestTimeout" determines the maximum response time from the server for a single request. It is specified as 500ms in clientOptions. ClientOptions also has "OpenTCPConnectionTimeout" that determines the maximum amount of time a client will wait to establish a new TCP connection to the server. This is 5 seconds by default if not specified otherwise. From the diagnostic log that is shared above, "ChannelAcquisitionStarted" event failed that means the TCP connection was not even established. So it was the 5 seconds "OpenTCPConnectionTimeout" that threw the timeout error and not "RequestTimeout".

@aavasthy, that means in 5 seconds the caller should have received an exception. But that did not happen. As you can see in the log, the request was blocked for at least 35 seconds (It may have been more than this).

@aavasthy, that means in 5 seconds the caller should have received an exception. But that did not happen. As you can see in the log, the request was blocked for at least 35 seconds (It may have been more than this).

@Jasen-Quadras when you say at least 35s(2100 ms) are you mentioning the total "duration in milliseconds":34491.8583 that we see in the summary diagnostics?

@aavasthy, yes.

The total "duration in milliseconds":34491.8583 that we see in the summary diagnostics includes the processing time of other requests that didn't encounter the timeout error.

Closing as the questions have been answered, thanks @aavasthy.


qtdeclarative: fix for gcc6

Signed-off-by: Yi Qingliang<EMAIL_ADDRESS>

Please, read the README file. Patches are not accepted through GitHub.


Minimal changes to get pmxbot up and running again

Minimal changes to get pmxbot up and running again. Our main use case is webhooks as we've lost observability on applications as a result. This is now working as well as the common integrations (e.g. thanks and motivate)
Key changes:

Changed the dependency to be the new name: slack_sdk
Updated to use the v2 of the RTMClient
self.slack.server is no longer a thing in the new client, so changed to use self.slacker for retrieving info on users/channels (or as they're referred to as now: conversations)
Now using the web client for posting messages to slack. For this we need the channel ID rather than the channel name, so there is logic implemented to resolve this where necessary.
Kept it simple by spawning a thread to run the scheduler rather than an asyncio loop as suggested by jaraco here: https://github.com/pmxbot/pmxbot/issues/85#issuecomment-489086969

Talking to PmxBot directly:

Webhooks and scheduled messages:

Responding in threads, tagging users and channels:

Help docs:

Some other random commands:

Tests were failing. Fixed in 6f8fa0b.

@jaraco Thanks for the review and contributions, I particularly like your implementation for handling paginated data from slack!
I believe I've addressed all of your comments, please take another look when you have capacity.
I'd like to do some final testing tomorrow, so if you review and approve before then, don't merge just yet!

@jaraco Thanks for the review and contributions, I particularly like your implementation for handling paginated data from slack!
I believe I've addressed all of your comments, please take another look when you have capacity.
I'd like to do some final testing tomorrow, so if you review and approve before then, don't merge just yet!

... All looks good to me!

Excellent work and great collaboration. Thanks!


NeonHelper.ExecuteCapture(): support custom output encodings

We ran into a situation the other day where we realized that the wsl.exe command line tool was actually outputting 16-bit Unicode characters.  Although that situation is a bit odd (who writes command line tools that does that?), being able to control how the process output streams is interpreted might be generally useful.
We're going to add an optional outputEncoding parameter to the exec methods to give developers a way to control how the standard output and error text returned by the subprocess is interpreted.

DONE


pull request for e2e test at 11/16/2016 00:56:11

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

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


Branch 202673820

Very very confusing merge. GRPC build targets got duplicated because of internal change,  protobuf pip version was accidently downgraded internally, and many conflicts caused by internal formatting tool

Might have messed some of the merge up. Double checking

looks like windows bazel build is broken by cl/202664219

@case540 Can you explain a bit more what this is? A 150 commit PR this close to 1.9 being tagged is wild. I'm not arguing about the need, it's just these large PRs often break the ppc64le build and we have to sift through a lot of code to find out why. A bit more transparency would be great!

@jayfurmanek I dont think this is in 1.9 branch so it being committed close to 1.9 being tagged shouldn't matter. This is just part of the process of pushing internally made commits to public tensorflow.

Ah, right. I was looking at so many 1.9 commits lately, I see this is to master now. (sorry!)
If this must come in one big PR, having a description of what it is would be nice.

@jayfurmanek thanks for your note. This PR was part of our old process to push internal changes out to github daily. We have recently moved to a new workflow where each internal change gets pushed to GitHub right away, and hopefully it is more clear than big PR like this one!

Oh ok, that's great to hear! These big PRs can be painful to sift through, so the new method is most welcome. Thanks!


Add ASE to Build Image

Is this pull request associated with an issue(s)?
No
Description
Title.

🚀 [bumpr] Bumped! New version:v0.3.60 Changes:v0.3.59...v0.3.60


Problem while compiling with Carthage

Steps to reproduce
in Cartfile add this > github "AliSoftware/Reusable"
$ carthage update

Carthage console:
*** Downloading Reusable.framework binary at "4.0.5"
***  Skipped installing Reusable.framework binary due to the error:
	"Incompatible Swift version - framework was built with 4.2 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>) and the local version is 4.2.1 (swiftlang-1000.11.42 clang-1<IP_ADDRESS>)."

check it plz

Closing for lack of activity, and because the OP was likely using an outdated version of Carthage.


Eyelink pupil size requires calibration

Eyelinks use an internal unit for their pupil size measurement, which is fine if we want relative units, but does not translate into absolute units (which is commonly used, especially to compare across systems). To do so, labs will need to run a calibration: printing a black circle of known absolute size, holding it at head distance away from the Eyelink, and conducting a measurement. This should be relatively brief (and labs may have already done so for other experiments), but we will need to collate the data for the pupillometry spinoff.
Source: https://www.sr-research.com/support/thread-154.html (walled behind account creation; relevant section in screenshot below)

Having looked into this a bit more, and after discussions with colleagues who have used or use Eyelink-systems, it seems that there is no straightforward fix to this. There is a long and a short answer. The short answer is that studying pupil dilation changes is likely not possible with these systems if remote tracking mode was used. Even relative changes in pupil size are difficult to interpret if participants changed their position to the eye tracker from baseline to test.


The data in the [Bug Report] window affects the data

Element UI version
1.4.2
OS/Browsers version
win 7 版本  chrome 58.0.3029.110 (64-bit)
Vue version
2.4.2
Reproduction Link
https://jsfiddle.net/pj71jkyw/523/
Steps to reproduce
1 、点击编辑按钮，打开编辑弹窗；
2、选择天数，金额会随之变化；
3、不点击确定按钮，点击其它地方或者点击关闭叉号，金额发生了变化；
1, click the Edit button, open the edit window;
2, select the number of days, the amount will change;
3, do not click the OK button, click on other places or click to close the fork, the original amount has changed;
What is Expected?
弹窗里的数据无论怎么编辑，再未点确定保存前，都不影响原数据。
The data in the window no matter how to edit, and then no point to determine the preservation before, does not affect the original data.
What is actually happening?
只要弹窗里的数据发生变化，原数据也会变化
As long as the data in the window changes, the original data will change

引用的是同一个对象，自然会同步。

怎么样才能达到预期的效果？


Allow for null baseline_sha

Needed for https://github.com/iterative/dvclive/pull/646 to work without a baseline revision (since this would be a pain to provide in a no-git scenario).
@daavoo I will likely need your help to make similar changes on the Studio side to accept requests with missing baseline_sha.

Codecov Report
Patch and project coverage have no change.

Comparison is base (c85eda7) 100.00% compared to head (cd8507f) 100.00%.
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #72   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines          154       154
  Branches         6         6
=========================================
  Hits           154       154

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Can we use just a 40-character placeholder string like "z" * 40?

The schema checks for a valid sha here:
https://github.com/iterative/dvc-studio-client/blob/535c3aa5ec1742f693466089418b656b4601d1f1/src/dvc_studio_client/schema.py#L9

@dberenbaum is it still relevant?

It depends on how we decide to go with issues like https://github.com/iterative/dvclive/issues/638 and https://github.com/iterative/dvclive/issues/237. If we decide to clone the repo on every node where dvclive runs, then this won't be needed, but if we decided to allow for some "no-git" scenarios, I think it might be needed. I can convert to draft until we decide.


Update askpass

Hey!
Interesting project! Thought I'd start by refactoring small files.

Thank you. i have merged your pull request into the development branch. i'll keep the master branch synchronized with the last released version. Once we are ready to release then i merge into the master branch all changes from development branch.


Color isn't copied

When you click to copy the color, the color isn't being copied to clipboard.
Browser: Chrome 56.0.2924.87

Hey, can you open devtools and check if there is anything odd in the console when copying a color?

same results in my console. chrome

Hmm, I'll look into it @FernandoBoza @TheExeLab


adding location scaffolding

@craig-clayton, made the location.hjs and made some minor changes to item.hjs.
Review and merge so we can get locations done :)

Looks good - merge!


E2E: go release main config-ldflags-noassets slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v17.0.13
Run: https://github.com/slsa-framework/example-package/actions/runs/6600995576
Workflow name: .github/workflows/e2e.go.release.main.config-ldflags-noassets.slsa3.yml
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.release.main.config-ldflags-noassets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.release.main.config-ldflags-noassets.slsa3.yml
Trigger: release
Branch: v17.0.13
Date: Sun Oct 22 01:56:47 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v17.0.13
Run: https://github.com/slsa-framework/example-package/actions/runs/6607687702
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.release.main.config-ldflags-noassets.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.release.main.config-ldflags-noassets.slsa3.yml
Trigger: release
Branch: v17.0.13
Date: Mon Oct 23 01:54:30 UTC 2023
Tests are passing now. Closing this issue.


Only showing one Aim-map stat graph

Hello,
Very nice program even if it is not properly working for me, it only shows one of my played aim maps as a graph. I also get an module error from "seaborn", so it could even be my fault.
Error if nor my fault:
seaborn\algorithms.py:86: RankWarning: Polyfit may be poorly conditioned
boot_dist.append(f(*sample, **func_kwargs))

That's a normal warning from seaborn when using polynomial plots.
Do you have data for all the maps you have played in the stats folder?


[javascript] Remove Buffer usage

Motivation
Buffer is Node only and gets converted to a string anyway so user should be responsible to convert based on their platform
Solution
Remove Buffer

The problem is that this breaks API unfortunately. :(
Is there a real problem with having it be there?

Buffer is a Node only thing, not standard JavaScript so it won't be acceptable in all runtimes.
@tasn would you prefer I close all my PRs and open them against the standard-webhooks library instead? That's much more new and I could do a 2.0 version there with breaking changes that won't effect as many people. In general though the Svix library has node only things which affects people like me who want to use it in other environments like Cloudflare workers, we have to use polyfills

Why not have the user be responsible for turning the Buffer into a string? That way it works for every platform. That's the core of the issue, Buffer is a Node API, not a JavaScript one

Yeah, for sure. The problem is breaking API though. :|


Add @wlynch as a pipelines maintainer

Changes
Billy has been a long time contributor to pipelines. He has contributed a number of security related features, served on the vulnerability management team, and has been a prolific reviewer for a number of large features such as trusted resources, larger results, SPIRE support etc.
Reviews: https://github.com/search?q=-author%3Awlynch+repo%3Atektoncd%2Fpipeline+reviewed-by%3Awlynch+type%3Apr&type=pullrequests
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[ ] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/kind misc

/assign @tektoncd/core-maintainers

/kind misc

/approve

/lgtm


New version: BandedMatrices v1.6.0

Registering package: BandedMatrices
Repository: https://github.com/JuliaLinearAlgebra/BandedMatrices.jl
Created by: @jishnub
Version: v1.6.0
Commit: 5ee8d5abebf6274b20d102688ec64fbd9c686c88
Reviewed by: @jishnub
Reference: https://github.com/JuliaLinearAlgebra/BandedMatrices.jl/commit/5ee8d5abebf6274b20d102688ec64fbd9c686c88#commitcomment-138270179
Description: A Julia package for representing banded matrices

[noblock]
Looks like there is a merge conflict.
@jishnub Can you re-trigger Registrator? This will fix the merge conflict.


Angular 6 Production on local IIS, Manual Url/Refresh Page is not working

The project is built successfully, deployed on local-IIS. The routes are working fine when navigate through index.html but when i refresh the page, it shows Http Error 404.0 - Not Found.
Following is the detail of versions, running on my system.
Versions
Angular CLI: 6.0.8
Node: 8.11.2
OS: win32 x64
Angular: 5.2.9
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
Package                           Version
@angular-devkit/architect             0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core                    0.6.8
@angular-devkit/schematics         0.6.8
@angular/cli                                  6.0.8
@ngtools/webpack                       6.0.8
@schematics/angular                    0.6.8
@schematics/update                     0.6.8
rxjs                                                 5.5.8
typescript                                      2.5.3
webpack                                        4.8.3

@sajjadkhadim, repo link, please.

after adding web.config, showing HTTP Error 500.19 - Internal Server Error

<system.webServer>

</system.webServer>

@sajjadkhadim, it is a not angular bug.

system.webServer should be wrapped by configuration node.

@derkachdeveloper thanks for your reply, i have tried with  tag, but still showing error

@sajjadkhadim, do you can share repo? i to try.

@derkachdeveloper now my web.cofig file is below

@derkachdeveloper, project is confidential, can not share repo.

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

@clydin  Above issue is resolved by configuration of URL Rewrite.
I have followed instruction given below
https://stackoverflow.com/questions/12614072/how-do-i-configure-iis-for-url-rewriting-an-angularjs-application-in-html5-mode/26152011#26152011
I have installed urlrewrite.exe and then deployed in C:\inetpub\wwwroot\GTSS, 'GTSS' is project directory.

Hello everyone,
in few weeks ago, I was really stuck because of this 404 error, so after trying more than one solution, and all of those solutions were returning sometimes 404 or 500 errors, I decided to redirect the any wrong request to index.html in case of error.
so I googled for it and I found this solution :
web.config :
<?xml version="1.0" encoding="UTF-8"?>

<configuration>
  <system.web>
    <compilation targetFramework="4.0" />

    <customErrors mode="On" redirectMode="ResponseRewrite">
      <error statusCode="404" redirect="/index.html" />
    </customErrors>
  </system.web>

  <system.webServer>
    <httpErrors errorMode="Custom">
      <remove statusCode="404"/>
      <error statusCode="404" path="/index.html" responseMode="ExecuteURL"/>
    </httpErrors>
  </system.webServer>
</configuration>

the good part of this solution, all my route are working as they should, and I can refresh and write the url manually without any error.

This helped me with the routing issue
https://blog.angularindepth.com/deploy-an-angular-application-to-iis-60a0897742e7

<system.webServer>

</system.webServer>


Edit the x and y of the frames.

The lefts sprite are too much at left and the down sprite is too much down, and I don't remember how to change it.

If you are using kade engine, build a test version with -debug at the end of it. The command in powershell should look like lime test [your operating system] -debug when it is done compiling launch the game go into a song and make player 1 your character, so if you go into bopeebo make dad your character via the charting menu and leave the charting menu and press 6 and it should open a offsets menu w and s, change through animations, use the arrows to change the offsets of the animation you're currently on.

If you are using kade engine, build a test version with -debug at the end of it. The command in powershell should look like lime test [your operating system] -debug when it is done compiling launch the game go into a song and make player 1 your character, so if you go into bopeebo make dad your character via the charting menu and leave the charting menu and press 6 and it should open a offsets menu w and s, change through animations, use the arrows to change the offsets of the animation you're currently on.

pressin 8*


minifab for k8s does not meet client.authentication.k8s.io ( k8s credential and authentication extension )

some cloud k8s, like AWS ESK, requires credential and authentication extension to operate k8s as described below URLs.

https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html  describes EKS requires client.authentication.k8s.io
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html  describes setting up  AWS credential into ${HOME}/.aws

current minifab container doesn't have feature to load and involve these extension, so minifab failed to setup HLF on AWS EKS.
but with small modification as followings, minifab can setup HLF on AWS EKS.
# extra options to set minifab container
export MINIFAB_OPTS='-v /home/my/.aws:/root/.aws -v /somewhere/aws-iam-authenticator:/usr/local/bin/aws-iam-authenticator'
# start minifab
minifab netup ...

diff --git a/minifab b/minifab
--- a/minifab
+++ b/minifab
   docker run --rm --name minifab -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd)/vars:/home/vars \
-  -v $(pwd)/spec.yaml:/home/spec.yaml -e "ADDRS=$ADDRS" hyperledgerlabs/minifab:latest /home/main.sh "$@"
+  -v $(pwd)/spec.yaml:/home/spec.yaml -e "ADDRS=$ADDRS" ${MINIFAB_OPTS} hyperledgerlabs/minifab:latest /home/main.sh "$@"

@litong01 I'm not sure what name is better for above environment variable, MINIFAB_OPT is ok? or any suggestion?

You can actually create a correct kubeconfig file which contains access token, then everything will work fine. I've tested against eks which worked fine.
Use aws eks get-token to get access token then use kibectl config set-credentials to get the access token inside the kube config file. Use that kube config like any other ones. Things will work great.
Please close this issue.

@litong01 I tested the way you suggested with 'eksctl create cluster' command. and found your suggestion requires manual editing kubeconfig.
just after 'eksctl create cluster' command execution, kubeconfig file assumes to use aws or aws-iam-authenticator as described in the above URL.
after get-token and set-credentials, kubeconfig snippet became as bellow.
at this moment, kubectl failed because of   'aws command not found'.
To succeeded it, I need to delete 'execute' section from kubeconfig by manual.
on the other hand, my above method needs no modification.
I found both methods can operate AWS EKS, but my method is more easier than yours.
I'd like to confirm you have no plan to merge  my above method?
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: ...
users:
- name: arn:aws:eks:REGION:ID:cluster/CLUSTERNAME
    exec: # still remains this section and need to delete  for using embeded token.
      apiVersion: client.authentication.k8s.io/v1alpha1
      command: aws
      args: ...
    token: value which got by aws eks get-token

That adds aws specific to minifabric. I do not think it is a good idea.

I never modified my kube config file manually. All used either aws eks or kubectl command.

Getting the kube config file has been always different from cloud to cloud, for example, you may have used gcloud, now aws eks, using them to get the right kube config file can always be automated before you run minifabric. You really should not need to add cloud specific steps in minifabric to make it working against eks.

first I understood your concern.
Could you show me more about
how you set token into kubeconfig and disable aws(-iam-authenticator) command without manual editing?
When I tested, I needed manual editing so, I started working the above patch.
By the way,
even the above my method, minifabric is not involved AWS proprietary feature.
as you see in the above, my patch to minifabric just adds 'MINIFAB_OPT' as extra free parameter.
then, user can set any files to mount from runtime shell, not only for eks, gcloud, other cloud proprietary command and credentials.

@itaru2622 Use the following script to get your token inside kubeconfig file without manual editing it. Make sure that you have jq available in your system to parse the access token return from get-token command which is aws specific.
CONTEXT=$(kubectl config current-context)

TOKEN=$(aws eks get-token --cluster-name xxxx | jq -r '.status.token')

kubectl config set-credentials $CONTEXT --token=$TOKEN

@litong01 I will close this issue.
I tested with latest kubectl (ver 1.21.1) and found that your script work fine, it needs not manual editing.


For 3D Networks?

Hello!
I want to check my 3D CNN model's GPU using with torchstat, but it seems not support inputs with more than 3D...
assertionerror occured..
any solutions to solve this problem? or can you recommend some effective tools to check GPU usage? thx..

try another package "thop"


Bump language and mod enums

Add ScoreV2 mod enum
Add various new language enums

@khazhyk

What are you basing this on? This doesn't seem to match https://github.com/ppy/osu-api/wiki

Didn't seem to find this documented anywhere at osu! side so based via here:
For example: https://osu.ppy.sh/beatmapsets?l=2
l=2 argument, 2 according to wiki is english lang, 5 is instrumental and so on.

Also added new genres according to this:

Click on whatever genre/language in this GUI to see it's API num via search query


Interface control document (mechanical) + BOM

This has been started here, which is statically rendered from a plantuml file, but needs to have an associated Bill of Materials (BOM), preferably in a tabulated form with (at least) a list of part numbers and quantities.

Tagging @Burhan-Q's Off the shelf parts documentation for facilitating discussion on part numbers.

patrick recommends 6 columns for a table for BOM

make a template page for website while deciding what the BOM will be

use this photo for autopopulating in the meantime ^ (bom for electronics subassembly taken 7/18

Hardware parts list that BOM pulls from: https://docs.google.com/spreadsheets/d/1nCw9LUN7ygv8B8hno6poN-m15rsixNSolVTXhXynrfw/edit#gid=0

I would recommend having BOM's split up by assembly and not by mechanical/electrical(issue #8 )

goal: get content up in a simple table
look at the picture in this comment chain for the accurate quantities and parts used in the builds we've been doing since 7/18. in order to save time copy the part pictures/names/etc from the hardware parts list copied in this comment thread (double check tabs at the bottom).


Bootstrap 5

Hi,
It is possible to customize class name to use it with bootstrap 5 (invalid-feedback instead of field-validation-error
https://getbootstrap.com/docs/5.2/forms/validation/#server-side
Regards

It's not possible yet, but that seems like a useful feature.

For information, CSS class to customize are:
HtmlHelper.cs
    public class HtmlHelper : IHtmlHelper, IViewContextAware
    {
        /// <summary>
        /// CSS class name for input validation.
        /// </summary>
        public static readonly string ValidationInputCssClassName = "input-validation-error";

        /// <summary>
        /// CSS class name for valid input validation.
        /// </summary>
        public static readonly string ValidationInputValidCssClassName = "input-validation-valid";

        /// <summary>
        /// CSS class name for field validation error.
        /// </summary>
        public static readonly string ValidationMessageCssClassName = "field-validation-error";

        /// <summary>
        /// CSS class name for valid field validation.
        /// </summary>
        public static readonly string ValidationMessageValidCssClassName = "field-validation-valid";

        /// <summary>
        /// CSS class name for validation summary errors.
        /// </summary>
        public static readonly string ValidationSummaryCssClassName = "validation-summary-errors";

        /// <summary>
        /// CSS class name for valid validation summary.
        /// </summary>
        public static readonly string ValidationSummaryValidCssClassName = "validation-summary-valid";

@haacked Is there anything stopping this from being merged? It's a feature that would be desperately useful to allow easy integration with other UI libraries such as https://tabler.io/ which has its own opinionated view on what the error/valid classes should be.

@SKeeneCode Just merged it. It should be on NPM soon.


fix missing title prefix on the cards component page

Why:
Closes: N/A

I noticed the Card Components documentation page is missing a title prefix, so I added __nextra_dynamic_opts.title: 'Card Components' to the static props to ensure the page has a proper title.
What's being changed (if available, include any code snippets, screenshots, or gifs):

Before

After

Check off the following:

[x] I have reviewed my changes in staging, available via the View
deployment link in this PR's timeline (this link will be available after
opening the PR).

For content changes, you will also see an automatically generated comment
with links directly to pages you've modified. The comment won't appear if
your PR only edits files in the data directory.

[ ] For content changes, I have completed the
self-review checklist.

🙏 thanks


[now dev] Use canary builders for the canary version

Use canary builders for the canary version

Codecov Report

Merging #2753 into canary will increase coverage by 0.12%.
The diff coverage is 25%.

@@            Coverage Diff             @@
##           canary    #2753      +/-   ##
==========================================
+ Coverage   13.76%   13.88%   +0.12%
==========================================
  Files         262      262
  Lines       10599    10557      -42
  Branches     1366     1365       -1
==========================================
+ Hits         1459     1466       +7
+ Misses       8991     8942      -49
  Partials      149      149

Impacted Files
Coverage Δ

src/util/dev/server.ts
62.42% <25%> (+1.38%)
:arrow_up:

src/util/get-files.ts
91.01% <0%> (+0.9%)
:arrow_up:

src/util/dev/builder.ts
73.11% <0%> (+1.01%)
:arrow_up:

src/util/output/create-output.ts
40.9% <0%> (+3.4%)
:arrow_up:

src/util/dev/yarn-installer.ts
84.74% <0%> (+3.79%)
:arrow_up:

src/util/dev/router.ts
83.33% <0%> (+4.76%)
:arrow_up:

src/util/projects/get-project-by-id-or-name.ts
25% <0%> (+5%)
:arrow_up:

src/util/dev/builder-cache.ts
74.86% <0%> (+5.01%)
:arrow_up:

src/util/prefer-v2-deployment.ts
61.36% <0%> (+5.11%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

You think it's possible to add an integration test?


Add example using a reflex to best practices doc

Done in https://github.com/timonus/OpenerManifest/commit/065f047faf1d1b7172b7d376906f41f8286a3e7c


Duration: Double length is output and played

Reproduction steps

Playing a m4a file

Double length of the original file is shown and played.

Expected outcome
Maybe the file content length is loaded wrong.

Actually happening
eg. the file has a length of 2 minutes. 4 minutes are shown in the total duration and will be played. After the 2 minutes it is muted.
Your setup
Which version of MediaManager are you using?
iOS, latest build. I use the MediaSample.Core example.

Playing an mp3 audio file works like a charm. m4a not a described above.


New bathymetry

New bathymetry for TP2

@AchrefAO I think you should only update the topography version "03", not "02".
Unless you have a specific reason to change version "02".

Absolutely, I have added the version 3 and replaced the files regional.depth.ab and regional.grid.ab

@AchrefAO I think you should only update the topography version "03", not "02".
Unless you have a specific reason to change version "02".

Absolutely, I have added the version 3 and replaced the files regional.depth.ab and regional.grid.ab

But I still see the vesion 02 topography changed under "Files changed" on the pull request.

@AchrefAO I think you should only update the topography version "03", not "02".
Unless you have a specific reason to change version "02".

Absolutely, I have added the version 3 and replaced the files regional.depth.ab and regional.grid.ab

But I still see the vesion 02 topography changed under "Files changed" on the pull request.

@lilleannette  Can you refuse it and I'll submit again


Release 2.12.3 (for SGE)

Backports PR ( https://github.com/nanshe-org/docker_nanshe_workflow/pull/84 ) for SGE.
Releases the 2.12.3 version of the workflow.

Running into issue ( https://github.com/nanshe-org/docker_nanshe_workflow/issues/86 ) here as well. Moving ahead without resolution for now as previously noted. Should add this passed when testing it locally.