MQTT Climater activation ignored

Describe the bug
I have configured my Tesla Model Y manually via MQTT/Teslamate as this gives me the possibility to add support for climater, which is currently not supported by the Teslamate template.
Unfortunately when the climate is activated, evcc does not activate the load point. Of course I have verified that the climate status is correctly published via the correct MQTT topic.
Also, evcc vehicle correctly reflects the status as Climate Active: true.
Other similar issues have pointed to some 'polling' values not being correct, which could solve those issues. However, I would believe that in the case of using MQTT 'polling' should not be the source of the issue, or is it?
Output of evcc vehicle while the car was connected and the climate was on:
[main  ] INFO 2024/03/07 07:18:52 evcc 0.124.6
[main  ] INFO 2024/03/07 07:18:52 using config file: /etc/evcc.yaml
[db    ] INFO 2024/03/07 07:18:52 using sqlite database: /root/.evcc/evcc.db
[mqtt  ] INFO 2024/03/07 07:18:52 connecting evcc-1018362524 at tcp://homeassistant:1883
[mqtt  ] DEBUG 2024/03/07 07:18:53 tcp://homeassistant:1883 connected
Soc:            98%
Capacity:       60.0kWh
Charge status:  A
Range:          403km
Climate active: true
OnIdentified:   Mode:pv
Features:       [CoarseCurrent]

Regarding the attached log output, the activation of the pre-heating was published via MQTT at 07:07:21 and the car was disconnected from the charger at 07:11:21.
Steps to reproduce

Configure climater via MQTT.
Activate climate while the EV is connected to the LP and charging is already finished.
See that the LP will not be enabled.

Configuration details
# open evcc at http://evcc.local:7070
network:
  schema: http
    #  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

mqtt:
  broker: homeassistant:1883
  topic: evcc
  user: evcc
  password: #####

log: debug
levels:
  cache: error

# unique installation id
plant: #####

interval: 10s # control cycle interval

sponsortoken: #####

vehicles:
- name: ev1
  type: custom
  title: Model Y
  capacity: 60
  features: ["coarsecurrent"]
  onIdentify:
    mode: pv
      #    minSoc: 10
      #    targetSoc: 80
  soc:
    source: mqtt
    topic: teslamate/cars/1/battery_level
    timeout: 720h # 30d
  range:
    source: mqtt
    topic: teslamate/cars/1/rated_battery_range_km
    timeout: 720h # 30d
  status:
    source: combined
    plugged:
      source: mqtt
      topic: teslamate/cars/1/plugged_in
      timeout: 720h # 30d
    charging:
      source: mqtt
      topic: teslamate/cars/1/charger_actual_current
      timeout: 720h # 30d
  climater:
    source: mqtt
    topic: teslamate/cars/1/is_climate_on
    timeout: 720h # 30d

meters:
  - name: grid
    type: custom
    power:
      source: mqtt
      topic: homeassistant/sensor/eg_og_power_consumption
      timeout: 1200m
      scale: 1

site:
  title: Home
  meters:
    grid: grid

chargers:
  - name: goe_garage
    type: template
    template: go-e-v3
    host: <IP_ADDRESS>

loadpoints:
  - title: Garage
    charger: goe_garage
    vehicle: ev1
    minCurrent: 6
    maxCurrent: 16
    mode: off

tariffs:
  currency: EUR
  grid:
    type: tibber
    token: "#####"
    homeid: "#####"

Log details
evcc-1  | [main  ] INFO 2024/03/05 07:26:00 evcc 0.124.6
evcc-1  | [main  ] INFO 2024/03/05 07:26:00 using config file: /etc/evcc.yaml
evcc-1  | [main  ] INFO 2024/03/05 07:26:00 starting ui and api at :7070
evcc-1  | [db    ] INFO 2024/03/05 07:26:00 using sqlite database: /root/.evcc/evcc.db
evcc-1  | [mqtt  ] INFO 2024/03/05 07:26:00 connecting evcc-1287483002 at tcp://homeassistant:1883
evcc-1  | [mqtt  ] DEBUG 2024/03/05 07:26:01 tcp://homeassistant:1883 connected
evcc-1  | [lp-1  ] WARN 2024/03/05 07:26:01 deprecated: minCurrent setting is ignored, please remove
evcc-1  | [lp-1  ] WARN 2024/03/05 07:26:01 deprecated: maxcurrent setting is ignored, please remove
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 charge total import: 170.365kWh
evcc-1  | [site  ] INFO 2024/03/05 07:26:01 site config:
evcc-1  | [site  ] INFO 2024/03/05 07:26:01   meters:      grid ✓ pv ✗ battery ✗
evcc-1  | [site  ] INFO 2024/03/05 07:26:01     grid:      power ✓ energy ✗ currents ✗
evcc-1  | [site  ] INFO 2024/03/05 07:26:01   vehicles:
evcc-1  | [site  ] INFO 2024/03/05 07:26:01     vehicle 1: range ✓ finish ✗ status ✓ climate ✓ wakeup ✗
evcc-1  | [lp-1  ] INFO 2024/03/05 07:26:01 loadpoint 1:
evcc-1  | [lp-1  ] INFO 2024/03/05 07:26:01   mode:        off
evcc-1  | [lp-1  ] INFO 2024/03/05 07:26:01   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
evcc-1  | [lp-1  ] INFO 2024/03/05 07:26:01   meters:      charge ✓
evcc-1  | [lp-1  ] INFO 2024/03/05 07:26:01     charge:    power ✓ energy ✓ currents ✓
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 phase timer inactive
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 pv timer inactive
evcc-1  | [lp-1  ] INFO 2024/03/05 07:26:01 vehicle updated: unknown -> Model Y
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 set charge mode: pv
evcc-1  | [site  ] WARN 2024/03/05 07:26:01 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:01 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:01 grid meter: 1325W
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:01 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:01 site power: 1325W
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 charge total import: 170.365kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 charger status: A
evcc-1  | [lp-1  ] INFO 2024/03/05 07:26:01 car disconnected
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 set charge mode: off
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 set charge mode: pv
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 set session soc limit: 0
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 set session energy limit: 0
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:01 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:01 grid meter: 1325W
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:01 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:01 site power: 1325W
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 charge total import: 170.365kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:01 charger status: A
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:11 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:11 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:11 grid meter: 1319W
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:11 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:11 site power: 1319W
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:11 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:11 charge total import: 170.365kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/05 07:26:11 charger status: A
evcc-1  | [site  ] DEBUG 2024/03/05 07:26:21 ----

[...]

evcc-1  | [site  ] DEBUG 2024/03/07 07:07:11 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:11 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:11 grid meter: 1678W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:11 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:11 site power: 1678W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:11 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:11 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:11 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:11 pv charge current: 0A = 0A + -7.3A (1678W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:21 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:21 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:21 grid meter: 1676W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:21 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:21 site power: 1676W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:21 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:21 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:21 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:21 pv charge current: 0A = 0A + -7.29A (1676W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:31 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:31 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:31 grid meter: 1678W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:31 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:31 site power: 1678W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:31 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:31 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:31 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:31 pv charge current: 0A = 0A + -7.3A (1678W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:41 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:41 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:41 grid meter: 1674W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:41 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:41 site power: 1674W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:41 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:41 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:41 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:41 pv charge current: 0A = 0A + -7.28A (1674W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:51 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:51 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:51 grid meter: 1673W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:51 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:07:51 site power: 1673W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:51 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:51 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:51 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:07:51 pv charge current: 0A = 0A + -7.27A (1673W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:01 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:01 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:01 grid meter: 1674W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:01 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:01 site power: 1674W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:01 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:01 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:01 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:01 pv charge current: 0A = 0A + -7.28A (1674W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:11 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:11 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:11 grid meter: 1671W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:11 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:11 site power: 1671W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:11 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:11 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:11 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:11 pv charge current: 0A = 0A + -7.27A (1671W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:21 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:21 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:21 grid meter: 1674W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:21 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:21 site power: 1674W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:21 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:21 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:21 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:21 pv charge current: 0A = 0A + -7.28A (1674W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:31 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:31 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:31 grid meter: 1675W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:31 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:31 site power: 1675W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:31 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:31 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:31 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:31 pv charge current: 0A = 0A + -7.28A (1675W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:41 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:41 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:41 grid meter: 1676W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:41 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:41 site power: 1676W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:41 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:41 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:41 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:41 pv charge current: 0A = 0A + -7.29A (1676W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:51 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:51 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:51 grid meter: 1670W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:51 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:08:51 site power: 1670W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:51 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:51 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:51 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:08:51 pv charge current: 0A = 0A + -7.26A (1670W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:01 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:01 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:01 grid meter: 1670W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:01 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:01 site power: 1670W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:01 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:01 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:01 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:01 pv charge current: 0A = 0A + -7.26A (1670W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:11 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:11 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:11 grid meter: 1670W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:11 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:11 site power: 1670W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:11 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:11 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:11 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:11 pv charge current: 0A = 0A + -7.26A (1670W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:21 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:21 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:21 grid meter: 1669W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:21 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:21 site power: 1669W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:21 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:21 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:21 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:21 pv charge current: 0A = 0A + -7.26A (1669W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:31 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:31 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:31 grid meter: 1738W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:31 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:31 site power: 1738W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:31 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:31 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:31 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:31 pv charge current: 0A = 0A + -7.56A (1738W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:41 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:41 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:41 grid meter: 1725W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:41 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:41 site power: 1725W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:41 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:41 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:41 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:41 pv charge current: 0A = 0A + -7.5A (1725W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:51 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:51 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:51 grid meter: 1722W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:51 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:09:51 site power: 1722W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:51 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:51 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:51 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:09:51 pv charge current: 0A = 0A + -7.49A (1722W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:01 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:01 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:01 grid meter: 1729W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:01 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:01 site power: 1729W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:01 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:01 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:01 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:01 pv charge current: 0A = 0A + -7.52A (1729W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:11 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:11 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:11 grid meter: 1731W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:11 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:11 site power: 1731W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:11 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:11 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:11 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:11 pv charge current: 0A = 0A + -7.53A (1731W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:21 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:21 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:21 grid meter: 1729W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:21 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:21 site power: 1729W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:21 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:21 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:21 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:21 pv charge current: 0A = 0A + -7.52A (1729W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:31 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:31 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:31 grid meter: 1729W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:31 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:31 site power: 1729W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:31 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:31 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:31 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:31 pv charge current: 0A = 0A + -7.52A (1729W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:41 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:41 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:41 grid meter: 1727W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:41 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:41 site power: 1727W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:41 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:41 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:41 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:41 pv charge current: 0A = 0A + -7.51A (1727W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:51 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:51 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:51 grid meter: 1731W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:51 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:10:51 site power: 1731W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:51 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:51 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:51 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:10:51 pv charge current: 0A = 0A + -7.53A (1731W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:01 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:01 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:01 grid meter: 1729W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:01 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:01 site power: 1729W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:01 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:01 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:01 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:01 pv charge current: 0A = 0A + -7.52A (1729W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:11 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:11 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:11 grid meter: 1733W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:11 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:11 site power: 1733W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:11 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:11 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:11 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:11 pv charge current: 0A = 0A + -7.53A (1733W @ 1p)
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:21 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:21 grid meter: 1729W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:21 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:21 site power: 1729W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 charger status: A
evcc-1  | [lp-1  ] INFO 2024/03/07 07:11:21 car disconnected
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 set charge mode: off
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 set charge mode: pv
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 set session soc limit: 0
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 set session energy limit: 0
evcc-1  | [lp-1  ] WARN 2024/03/07 07:11:21 charger out of sync: expected disabled, got enabled
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 charger disable
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 wake-up timer: stop
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:21 ----
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:21 grid meter: 1728W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:21 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:21 site power: 1728W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 07:11:21 charger status: A
evcc-1  | [site  ] DEBUG 2024/03/07 07:11:31 ----

What type of operating system are you running?
Linux
Version
0.124.6

Bitte evcc trace log wo climater active sichtbar ist.

Bitte evcc trace log wo climater active sichtbar ist im Kontext nicht erfolgter Freigabe.

Siehe gewünschte Trace Log. Man sieht klar, dass das MQTT Topic empfangen wird. Eine Aktion folgt darauf nicht.
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:18 ----
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:18 GET http://<IP_ADDRESS>/api/status?filter=alw,car,eto,nrg,wh,trx,cards
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:18 {"alw":false,"eto":219126,"car":3,"wh":0,"trx":null,"nrg":[234.9799957,233.1199951,234.9799957,2.480000019,0,0,0,0,0,0,0,0,0,0,0,0],"cards":[{"name":"n/a","energy":0,"cardId":true},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false}]}
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:18 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:18 grid meter: 1196W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:18 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:18 site power: 1196W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:18 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:18 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:18 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:18 limitSoc reached: 75.0% > 70%
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:19 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:19 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:20 recv homeassistant/sensor/eg_og_power_consumption: '1197'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:21 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:21 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:22 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:22 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:22 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:23 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:23 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:23 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:24 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:24 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:24 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:25 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:26 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:26 recv homeassistant/sensor/eg_og_power_consumption: '1196'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:26 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:26 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:27 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:27 recv homeassistant/sensor/eg_og_power_consumption: '1196'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:27 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:28 recv teslamate/cars/1/plugged_in: 'true'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:28 recv teslamate/cars/1/is_climate_on: 'true'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:28 recv teslamate/cars/1/rated_battery_range_km: '307.01'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:28 recv homeassistant/sensor/eg_og_power_consumption: '1197'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:28 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:28 ----
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:28 GET http://<IP_ADDRESS>/api/status?filter=alw,car,eto,nrg,wh,trx,cards
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:28 {"alw":false,"eto":219126,"car":3,"wh":0,"trx":null,"nrg":[234.6699982,233.1199951,234.9799957,2.480000019,0,0,0,0,0,0,0,0,0,0,0,0],"cards":[{"name":"n/a","energy":0,"cardId":true},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false}]}
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:28 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:28 grid meter: 1194W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:28 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:28 site power: 1194W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:28 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:28 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:28 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:28 limitSoc reached: 75.0% > 70%
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:28 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:29 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:29 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:30 recv homeassistant/sensor/eg_og_power_consumption: '1196'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:30 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:31 recv homeassistant/sensor/eg_og_power_consumption: '1196'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:31 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:32 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:32 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:32 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:33 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:33 recv homeassistant/sensor/eg_og_power_consumption: '1196'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:33 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:34 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:35 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:35 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:35 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:36 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:36 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:36 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:36 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:37 recv homeassistant/sensor/eg_og_power_consumption: '1196'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:37 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:38 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:38 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:38 ----
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:38 GET http://<IP_ADDRESS>/api/status?filter=alw,car,eto,nrg,wh,trx,cards
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:38 {"alw":false,"eto":219126,"car":3,"wh":0,"trx":null,"nrg":[234.9799957,232.8099976,234.9799957,2.480000019,0,0,0,0,0,0,0,0,0,0,0,0],"cards":[{"name":"n/a","energy":0,"cardId":true},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false}]}
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:38 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:38 grid meter: 1194W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:38 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:38 site power: 1194W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:38 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:38 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:38 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:38 limitSoc reached: 75.0% > 70%
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:38 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:39 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:39 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:39 recv homeassistant/sensor/eg_og_power_consumption: '1196'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:39 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:40 recv homeassistant/sensor/eg_og_power_consumption: '1197'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:40 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:41 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:41 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:42 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:42 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:44 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:44 recv homeassistant/sensor/eg_og_power_consumption: '1196'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:45 recv homeassistant/sensor/eg_og_power_consumption: '1197'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:45 recv homeassistant/sensor/eg_og_power_consumption: '1195'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:45 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:46 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:47 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:47 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:47 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:48 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:48 ----
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:48 GET http://<IP_ADDRESS>/api/status?filter=alw,car,eto,nrg,wh,trx,cards
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:48 {"alw":false,"eto":219126,"car":3,"wh":0,"trx":null,"nrg":[234.9799957,232.8099976,234.9799957,2.480000019,0,0,0,0,0,0,0,0,0,0,0,0],"cards":[{"name":"n/a","energy":0,"cardId":true},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false}]}
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:48 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:48 grid meter: 1193W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:48 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:48 site power: 1193W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:48 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:48 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:48 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:48 limitSoc reached: 75.0% > 70%
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:48 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:49 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:50 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:50 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:51 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:52 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:52 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:52 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:53 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:53 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:54 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:55 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:56 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:56 recv homeassistant/sensor/eg_og_power_consumption: '1191'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:57 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:58 recv homeassistant/sensor/eg_og_power_consumption: '1191'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:58 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:58 ----
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:58 GET http://<IP_ADDRESS>/api/status?filter=alw,car,eto,nrg,wh,trx,cards
evcc-1  | [go-e  ] TRACE 2024/03/07 17:48:58 {"alw":false,"eto":219126,"car":3,"wh":0,"trx":null,"nrg":[234.9799957,233.1199951,234.9799957,2.480000019,0,0,0,0,0,0,0,0,0,0,0,0],"cards":[{"name":"n/a","energy":0,"cardId":true},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false},{"name":"n/a","energy":0,"cardId":false}]}
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:58 charge power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:58 grid meter: 1192W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:58 pv power: 0W
evcc-1  | [site  ] DEBUG 2024/03/07 17:48:58 site power: 1192W
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:58 charge currents: [0 0 0]A
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:58 charge total import: 219.126kWh
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:58 charger status: B
evcc-1  | [lp-1  ] DEBUG 2024/03/07 17:48:58 limitSoc reached: 75.0% > 70%
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:58 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:59 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:59 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:59 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:00 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:00 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:00 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:01 recv homeassistant/sensor/eg_og_power_consumption: '1191'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:01 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:01 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:02 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:02 recv homeassistant/sensor/eg_og_power_consumption: '1191'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:02 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:03 recv homeassistant/sensor/eg_og_power_consumption: '1194'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:03 recv homeassistant/sensor/eg_og_power_consumption: '1193'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:03 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:04 recv homeassistant/sensor/eg_og_power_consumption: '1191'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:05 recv homeassistant/sensor/eg_og_power_consumption: '1190'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:05 recv homeassistant/sensor/eg_og_power_consumption: '1191'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:06 recv homeassistant/sensor/eg_og_power_consumption: '1190'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:06 recv homeassistant/sensor/eg_og_power_consumption: '1191'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:07 recv homeassistant/sensor/eg_og_power_consumption: '1189'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:07 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:07 recv homeassistant/sensor/eg_og_power_consumption: '1191'
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:49:07 recv homeassistant/sensor/eg_og_power_consumption: '1192'
evcc-1  | [site  ] DEBUG 2024/03/07 17:49:08 ----

@andig May I ask why the issue was closed immediately after opening it and even it remains closed after I have posted the requested log?

Closed since incomplete.

@andig What exactly is incomplete here? You have asked for a trace log, and I have provided it in my answer 3 days ago. What else do you need?

Trace log shows no climater afaikt. This fits with climater not even implemented in Teslamate template. Happy to take a PR for adding it.

@andig May I ask you to read the bug report carefully instead of discarding it over and over again? The first sentence of the bug report reads:

I have configured my Tesla Model Y manually via MQTT/Teslamate as this gives me the possibility to add support for climater, which is currently not supported by the Teslamate template.

This means, I have of course configured EVCC to receive the relevant MQTT topic, which can also be verified in my configuration file, that I have attached.
Also, the provided trace log clearly shows that the topic is correctly received.
evcc-1  | [mqtt  ] TRACE 2024/03/07 17:48:28 recv teslamate/cars/1/is_climate_on: 'true'
Unfortunately there is no further reaction to this receiving of the topic. This is the whole point of filing the bug.
When looking at the code that I believe to be relevant to this, it seems that it is necessary to change the soc polling mode to connected in order for climater to work at all. Maybe you can confirm this. Especially when no polling is needed at all (for example in case MQTT is used), this is especially unintuitive and should at least get mentioned in the respective documentation.

When looking at the code that I believe to be relevant to this, it seems that it is necessary to change the soc polling mode to connected in order for climater to work at all.

See vehicleClimatePollAllowed


support outer dependencies collect

nowaday, loader can use .dependecy fn to add outer dependencies, while this kind of deps changed,
it's parent module will be compiled
re #8

Codecov Report

Merging #11 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev      #11   +/-   ##
=======================================
  Coverage   95.16%   95.16%
=======================================
  Files          62       62
  Lines         972      972
  Branches      259      259
=======================================
  Hits          925      925
  Misses         41       41
  Partials        6        6

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 0b0f5fd...7d3e966. Read the comment docs.


incorrect initialize model

I'm submitting a Regression

Current behavior:
Im trying use this sample for objecr detection(https://github.com/microsoft/Windows-Machine-Learning/tree/master/Samples/Tutorial Samples/YOLOv4ObjectDetection), but when  i inintializing your model(yolov4.onnx),appear this error in Evaluate frame func:
System.NullReferenceException: "Object reference not set to an instance of an object."
_binding was null.

this error manifested after initializing model. i think model wasn't correct initialized
Expected behavior

Minimal reproduction of the problem with instructions

Environment
Onnx version:

Windows Build Number:19041
App min and target version:19041
OS Version (Server, IoT Core, Desktop, etc): Desktop W10
Thanks in advance

I have the same problem too, any solutions?

This issue should now be resolved as the sample has been changed to use the Microsoft.AI.MachineLearning NuGet package.


Feature Request: OS Families

I've done some work over on comtrya that uses this library and I was looking at how comtrya utilizes os_info and thought about how other programs may use os_info. Getting specific information is great, but in some cases, mostly in Linux, having the specific distro may be a little bit too much information for what is needed. As an example, Comtrya looks at all of the OS type to then decide what action to take. For some actions that may become unruly. So I am thinking, what if we add another parameter for a Generic "family." So you still get all of the detailed information but a generic label also. So for instance, all Linux distros would have a "Linux" family label. So a program that calls on information from os_info and doesnt care what distro it is can just compare against the family. It just needs to know it is linux, the calling code doesn't care if it is Gentoo or Debian or Fedora. An example would be comtrya with adding the ability for user management. Linux distros add users in pretty much the same fashion, but comtrya would have to have code for all possible variants of Type. I am also wondering if this would also allow code being ran on linux systems that don't have a specific Type definition in os_info to already be useful for calling code. In the case of a rust tool that handles user management, it could just compare against the family not against each individual type.

Thank you for the suggestion, I think that makes sense. I will try to look into that, but feel free to submit a pull request if you like and/or want to speedup the process.


[WIP] US 2018 sprint accessibility

This begins work on the page navigation part of https://github.com/wagtail/wagtail/issues/4199#issuecomment-358640129
It wraps the main content of the admin in a main button, and changes a footer id in the nav menu to a more semantic menu-footer. This will allow future work on making footer tags more accessible. (I started working on this, so hopefully it's coming soon!)
Many thanks to @marteki for helping!

This is now replaced by #5290.


addNode method added.

addNode method added to treeview in order to add a new node under an already exists node. Now adding node under another node would be easy and painless

@lxsameer ,
I really need this method as I need to dynamically add nodes under parents(through ajax).
Is there any possibility to add multiple  nodes under a parent node ?
Also, can you please give me an example of how can I use your addNode method ?
Thanks in advance

This is really needed. That or some sort of url callback option like jstree does:
$('#tree').jstree({
'core' : {
  'data' : {
    'url' : function (node) {
      return node.id === '#' ?
        'ajax_roots.json' :
        'ajax_children.json';
    },
    'data' : function (node) {
      return { 'id' : node.id };
    }
  }
});

There isn't an easy way to dynamically expand nodes via ajax otherwise. Currently I use a backbone view to generate the tree and I keep track of childnodes in a hash within the view, then I re-render the tree with all children on an expand event :/

Why you did not inspect the project first? It was already added in 22172d83be84469828499037172ec46a20a2632f

Apparently I have not had enough coffee this morning. It looks like the develop branch has both the addNodes() method and a dataUrl option for ajax. Nice to know. Though kinda confusing...I expected to see that on master.


Shrink unsafe blocks

is there any benefit to this reorganisation other than "the unsafe blocks are smaller"? as in is it inadvisable to return from inside an unsafe block for any reason?


Change moduleService to implement NamedService

What this PR does:
The moduleService has a name, and it's trivial to implement ServiceName method.
I came across this while trying to add debug information about running services in mimir
Which issue(s) this PR fixes:
Fixes #
Checklist

[ ] Tests updated
[ ] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

Module service is a wrapper around another service. name field is name of the module. If anything, module service wrapper should expose name of wrapped service, instead of the module name.

thanks for the review. I pushed a commit to try delegating ServiceName to wrapped Service, ptal

If moduleSerice implements Service with its own implementation (albeit some of it delegated), wouldn't it also make sense to expose a best-effort name? I am thinking of ServiceName() as existing to primarily aid debugging and make services human-readable. Isn't more information better in this case or will it be confusing to clients?

If moduleSerice implements Service with its own implementation (albeit some of it delegated), wouldn't it also make sense to expose a best-effort name? I am thinking of ServiceName() as existing to primarily aid debugging and make services human-readable. Isn't more information better in this case or will it be confusing to clients?

In general "service" here is an object with observable state and a lifecycle. Not all services have or need a name.
To your question, if we moduleService wrapper a name, I think something like "service for module " would be more appropriate (or "service for module : ") than just a module name.

I pushed a commit that changes it to module service <name> and module service <name> for <originalServiceName>. This is becoming slightly more verbose than I hoped for initially, but I don't have better suggestions.


Add methods to pass arguments to CMake

Thanks! I wonder if actually these should be called cmake_build_args as they're only passed to the build step? (along with docs explaining that)

I am okay with whatever you think the API should look like.
My worry with this renaming would be that it might be confusing because there is also build_arg.
Note that the example I gave with -C is run in CMake's generation step.
Most flags CMake accepts are run in the generation step(even things like --trace).
Or I might be confusing what you mean by build step?

Ah yeah we invoke cmake twice here, but this is only applying to the build step? In that sense would this not solve your use case of passing -C to the generation step?
I'd be fine adding two suites of methods, one for the build step and one for the generation step. We should just be clear what arguments are going where.

If I run "-C" using build_arg, I get an error.
From what I know, -- [flags] are passed to the native build tool, not to CMake's generation step and that's why passing -C to build_arg doesn't work.

These just go before --, right?

Yes.
You can see the -- separator here: https://github.com/alexcrichton/cmake-rs/pull/29/files#diff-b4aea3e418ccdb71239b96952d9cddb6R493

Hm ok so to take a step back I'm proposing two new methods:

cmake_config_arg
cmake_build_arg

The former appends arguments to the configuration cmake command, where the latter appends arguments to the build command (but before -- where after which other build arguments come into play)
Does that make sense?


ISPN-7496 Ignore Leavers when processing StateTransfer

https://issues.jboss.org/browse/ISPN-7496

I decided to split obtaining transactions (with SYNCHRONOUS option) and listeners (with SYNCHRONOUS_IGNORE_LEAVERS) to be sure that I won't do any harm.
I also tried to write a test but it seems pointless since in case of failure, listeners just emit a warning and move on.

@wburns could you have a look?

@danberindei seems fine to me.

all tests ok locally, but the core testsuite looks slower. pushing...

integrated! thanks @slaskawi


[issue] Autoloot

Version: 1.0.0.rc3
Mods: CBA, TFAR, ACE(no-medical)
Environment: SP
.rpt attatched? YES
have you edited the missionfile?: No
Issue:

Autoloot succesfully, then more fight and more bodies around: the same AI will tell "nothing to loot", the other AI, on the contrary, started looting succesfully
Surrender box aren't checked: to allow it: replace

https://github.com/A3Antistasi/Antistasi-WotP/blob/38660b293ff26cfefbc2e0110950ba72560eb459/A3-Antistasi/AI/autoLoot.sqf#L18
with
_objetos = nearestObjects [_unit, ["WeaponHolderSimulated", "GroundWeaponHolder", "WeaponHolder","IND_Box_Base"], 50];

Can be done easily, will do.
In the case of vests or backpacks, I can order the AI to take them no matter what, just in case they have something useful....


Adding description to package.json

Not sure if leaving it out was intentional, but it doesn't display nicely in npm:

@ianwalter : Thanks for the PR 🙌

:tada: This PR is included in version 1.16.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


is batch-size set to 1 during training?

Hello, is batch-size set to 1 during training?

No https://github.com/aimagelab/VATr/blob/6ef5a91b541c92b448191a7f424e29db6e117e3d/train.py#L31C28-L31C28


Fix regression from #91

PR #91 did not add client argument to all function calls to get_all_external_repos, which causes issue like
  File "/snap/openstack/x24/lib/python3.10/site-packages/sunbeam/jobs/plugin.py", line 228, in
enabled_plugins
    repos.extend(cls.get_all_external_repos())
TypeError: PluginManager.get_all_external_repos() missing 1 required positional argument: 'client'

This PR addresses the regression.

/canonical/self-hosted-runners/run-workflows 9a4b12cbbd9aa2dfbe3b5458849f3ef5c3ecb2a7


Reactions are executed after onPatches listener returns

Related to #96, I'm wondering whether there is any argument against executing reactions inside the onPatches listener, i.e. when an action inside an onPatches listener triggers a reaction the reaction would be executed right after the action call and before the listener returns. The onPatches listener seems to be wrapped as an action
https://github.com/xaviergonz/mobx-keystone/blob/44a1cf2fb7d322ce09ea50eb47457074ca1a0177/packages/lib/src/patch/emitPatch.ts#L59-L61
but even when I remove this part, reactions are still executed after the listener returns, so something else must be causing this behavior and I can't seem to find it.
This is a test case meant to be included in test/patch/patch.test.ts for the behavior I'd like to have:
test("reaction is executed inside onPatches listener", () => {
  let reactionCalls = 0

  @model("test/reactionOnPatchesListener/M")
  class M extends Model({ a: prop<number>(10), b: prop<number>(20) }) {
    onInit() {
      autoDispose(
        reaction(
          () => this.b,
          () => {
            reactionCalls++
          }
        )
      )
    }
  }

  const m = new M({})

  autoDispose(
    onPatches(m, () => {
      expect(reactionCalls).toBe(0)

      runUnprotected(() => {
        m.b = 21
      })

      expect(reactionCalls).toBe(1)
    })
  )

  runUnprotected(() => {
    m.a = 11
  })
})

This is the behavior I would have expected, but in the context of #96 I discovered that a reaction is executed after the onPatches listener returns.

https://github.com/xaviergonz/mobx-keystone/pull/114 is a good solution to this problem, so I'll close this issue.


Question : Library production workflow

Despite my efforts, I couldn't find any documentation / solution about the "good way" to  make a bundle for librairies projects, and I'm stuck at this point.
My main problem is that when we make a bundle via the SystemJS Builder, there is no such thing as "index / main" file which permit to make exports in the bundle file.
For example :

bundle a core folder via its index.js file into a core.js file which directly make the same exports as in index.js, permitting to do a import { foo } from 'project/core' instead of import { foo } from 'project/core/index'
do exactly the same thing, but with only one bundle file (for all the project) at the end

Here is the related issue on my project : noelmace/angularjs-decorators#2 (which reference the pull requests and demos).

(my bad, the previous referenced issue has no relation to this one)

This is what static bundles (sfx builds) are for (or even Webpack or Rollup, it's irrelevent what tool is used for module compaction), but it has to be done carefully based on which internals and externals should apply.

Thank you very much for the fast answer.
So, if I have :
app/

foo.js
export default let Foo = 42;

And use :
 jspm bundle-sfx app/module/index.js myModule.js
I'll get a myModule.js file, and I can import the definitions on index with
` import { Foo } from 'myModule/

Thank you very much for the fast answer. SystemJS and JSPM are a bit new to me, but they are really great.
So, if I have :
app/
    moduleA/
        index.js
        foo.js

core/index.js
export Foo from './foo.js';

foo.js
export default let Foo = 42;

And use :
 jspm bundle-sfx app/* myProject.js
I'll get a myProject.js file, and, after a JSPM install, I can import foo with :
 import { Foo } from 'myProject/moduleA'
without any "bundles" parameter in the systemjs config file ?
Or maybe I'm wrong on the folder structure ... if so, could you tell me what you recommend ?
I'm also not understanding why we need a micro-loader implementation if at the end, we are sure to use our library as a JSPM dependency, so with SystemJS.

You'd need to rather distribute your library as separate files for these types of requires. SFX bundles just turn many modules into one as a compaction, losing the references to the external modules. Bundles themselves are not a distribution format.


Unable to quit the build script like before

Short description of the problem:
Unable to quit a running build script by pressing q.  No longer see the list of commands to quit, restart etc. (See Screenshot:1). Surprisingly changing the scripts in package.json as below in Steps to reproduce allows to quit.
What behaviour are you expecting?
I expect a way to quit the build scripts. Currently I have to close command prompt and start all over again and then need to browse to project directory again. This is painful.
Steps to reproduce:

Create a blank starter template and do ionic serve in command prompt.
Press q and try to quit the build as such it will not quit the build script.
Change scripts in package.json like below it should allow you to quit but it doesn't show usual logs with the default scripts.

From
"scripts": {
    "ionic:build": "ionic-app-scripts build",
    "ionic:serve": "ionic-app-scripts serve"
  }

To
"scripts": {
    "build": "ionic-app-scripts build",
    "serve": "ionic-app-scripts serve"
  }

Screenshot:1

Which @ionic/app-scripts version are you using?
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.2
Ionic CLI Version: 2.1.8
Ionic App Lib Version: 2.1.4
Ionic App Scripts Version: 0.0.44
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 7
Node Version: v6.9.1
Xcode version: Not installed

I posted a similar issue on Slack yesterday and found that if you press <ctrl-c> instead of pressing q, it will close all of the node.exe processes (as expected).
Not a solution, but a workaround in the interim...

Ctrl-c will cancel the script. I don't think anything more is needed really.

I liked the old way of doing it with the Q to Quit, R to Reload, etc. it was easy to understand and work with

Thanks you all for the temporary fix. Would be good if they can add quit command to debug tools which from memory is currently available on ctrl+shift+8.

For now I don't think we have any plans to add this functionality. Ctrl-c and Command-c is very common for this sort of thing. We'll reopen if anything changes here.
Thanks,
Dan

Thank @danbucholtz  Ctrl+C works and is good enough for me as of now

This is not completely fixed. I can ctrl+c ti quit immediately after ionic-serve, but as soon as I change a file and another build is started, I can no longer ctrl+c to quit.
Ionic info:
Ionic Framework Version: 2.0.0-rc.3
Ionic CLI Version: 2.1.12
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.45
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 7
Node Version: v6.9.1
Xcode version: Not installed

@Barryrowe,
You should be able to do a command-c at any time. Please try again and let me know if that's not the case.
Thanks,
Dan

I forgot to report back. This looks like sit was an issue with a bad npm install. I am on 0.0.45 and haven't had issues lately.


Which end is Start and Finish? (Graphic ambiguity)

Please replace the starting end with a garden water spigot or valve.  I always have to test which color the water comes from because I'll often start from the wrong side.

Well, it always starts from the right. But if you like you can design a nice new icon that fits well into the overall design and I will replace it..


Tell Travis CI how to install before running tests

This just makes it nicer to navigate the Travis CI interface.

Sweet thx.


⚠ Feeby.pl has degraded performance

In b0e9823, Feeby.pl (https://feeby.pl) experienced degraded performance:

HTTP code: 403
Response time: 8776 ms

Resolved: Feeby.pl performance has improved in 68f24ca.


Ability to add project to archive

Hi,
my team has a new project nearly every two week, so we have many-many project and projects list in main screen is big, so is there any such functionality in the plans for the future?
I think that it is better to sort projects since the last build and hide archived project from main projects list (but show it in right side if project has new commit, for gitlab hooks).
I will try implement this feature, so write your suggestions.

I like the idea.
I think it is good to have the option to sort on last date (but not to replace the sort on name)
And an option to archive the project so it is hidden from the main page. (It need to have a filter or separated page with archived projects to set it back)

:+1:


Connection issue

Dear ,
I hope this email finds you well. I am writing to you regarding an issue I encountered while using the FirebaseESP8266 library, which seems to conflict with the WiFiClientSecure library, preventing the client from establishing a connection with the desired host.
Description of the issue:
When attempting to connect to a host using WiFiClientSecure, the connection fails, and I am unable to establish a connection to the intended host.
This issue arises after including both the FirebaseESP8266 and WiFiClientSecure libraries in my program.
I have verified that the issue is not related to the network or the host since I was able to establish a successful connection when not using the FirebaseESP8266 library.
Steps to reproduce the issue:
Include the WiFiClientSecure and FirebaseESP8266 libraries in the program.
Set up the WiFiClientSecure connection and attempt to connect to a host.
Result: The connection fails, and I am unable to establish a connection to the host.
I have tried some solutions, such as updating both the FirebaseESP8266 and WiFiClientSecure libraries to the latest version, but the issue still persists.
I am in urgent need of your assistance to resolve this matter. I kindly request you to review and provide a solution or bug fix for this issue.
Thank you for your time and effort in developing the FirebaseESP8266 library. I look forward to your prompt response.

There is nothing related to the library.
The important when you are working with WiFiClientSecure (using BearSSL SSL library engine) is memory consumption.
You should debug your code for WiFi, SSL and OOM via Arduino IDE debug options, and check your device free heap as WiFiClientSecure object requires maximum 16k memory by default.
You can set the amount of reserve memory for in and out buffers of WiFiClientSecure's BearSSL engine from 512 bytes to 16384 bytes by calling setBufferSizes (search google for how to do this).
Your SSL client will be unable to connect to server in case of memory allocation failure as your device free heap is not enough which causes TLS handshake failure.
Please make sure you read and set the heap amount of your device correctly from this doc.
This library also creates the WiFiClientSecure instant inside the FirebaseData object to work with Firebase server.

You will see the library implemented this BearSSL memory reserved options for internal WiFiClientSecure used in the FirebaseData object here.

I tried setting the heap amount of your device as your doc gave but it
seems to run. My board Wemos d1r2(EPS8266) hangs and restarts by itself. It
can't solve the problem I'm having
I
Vào Th 2, 29 thg 5, 2023 vào lúc 15:34 Suwatchai K. <
@.***> đã viết:

You will see the library implemented this BearSSL memory reserved options
for internal WiFiClientSecure used in the FirebaseData object here
https://github.com/mobizt/Firebase-ESP8266/blob/95613ddab1c39aaf246bfddf302c953dd24cbdd7/examples/File/Flash/Flash.ino#L121
.
—
Reply to this email directly, view it on GitHub
https://github.com/mobizt/Firebase-ESP8266/issues/367#issuecomment-1566761727,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV7YCDH4HDRHBWWNOLDZPGDXIRNR7ANCNFSM6AAAAAAYSO4OSM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Problem: logrotate configuration is not optional

hare_setup utility by default tries to install logrotate configuration which
requires provisioner cli to be installed. It is possible that on some dev setups
provisioner is not installed, in which case hare_setup throws an error that may
mislead user to assume that hare_setup command itself failed.
Also it is not required logrotate to be configured in context of every command
execution.
Solution:
Provide an explicit option to hare_setup utility to configure hare logrotate
values.

If I am not wrong then hare_setup will still throw an error if provisioner is not installed.
Can we check if provisioner is installed and then attempt logrotate functionality in hare_setup.

@SwapnilGaonkar7 No, the idea is different.
If the user does want to configure logrotate, then (s)he will add the corresponding flag when invoking hare_setup. If the user doesn't want it (or it is obvious that provisioner CLI is not available), the argument will not be passed. So it is up to user to decide.
Your approach has another drawback. Consider the user does want to configure logrotate, then hare_setup will check if provisioner CLI is available and only then configure log rotate. So if provisioner CLI is not available, the end user will even not know that something went wrong.

@SwapnilGaonkar7 No, the idea is different.
If the user does want to configure logrotate, then (s)he will add the corresponding flag when invoking hare_setup. If the user doesn't want it (or it is obvious that provisioner CLI is not available), the argument will not be passed. So it is up to user to decide.
Your approach has another drawback. Consider the user does want to configure logrotate, then hare_setup will check if provisioner CLI is available and only then configure log rotate. So if provisioner CLI is not available, the end user will even not know that something went wrong.

But we are still calling log rotate in post_install section. So we will get error message if provisioner is not installed

@SwapnilGaonkar7 ,

But we are still calling log rotate in post_install section. So we will get error message if provisioner is not installed
We have included logrotate flag in setup.yaml because setup.yaml is supposed to used by the provisioner. Other users, mainly dev and QA will invoke hare_setup utility directly. If mini provisioner is invoked in Provisioner's context then it is expected that provisioner cli is present.
We want to configure logrotate in production environment, thus we have included logrotate flag in setup.yaml.


solved #685, made the explore button functional

Redirected the explore more button on hero section of home page to top products of the season section. The changes made are responsive with respect to the screen size as well without disturbing the functionality of the code .
https://github.com/user-attachments/assets/3a29279e-8f1d-4934-b94a-f54bf22e387a
@Tejashri-Taral
please merge before 10 am today (deadline for hacktoberfest) and add the labels
Thank you

@Tejashri-Taral
please merge before the hacktoberfest deadline .
I hope the changes made are working as per your expectations
Thanks

@Tejashri-Taral
it would be really helpful please look into it the deadline is reaching

Can you add some4 awesome product age in explore more?


Re-running article extraction benchmark

In last benchmark https://github.com/scrapinghub/article-extraction-benchmark#open-source-libraries Trafilatura scored well, but not best. This was with version 0.5.1. I am wondering if you can re-run the benchmark with latest version.

Re-run then myself, trafilatura, goose3 and news-please were updated to latest version.
 Nice results indeed, especially considering the first two are not freely available IMO.
I notified the makers of the benchmark of the idea to test it with newer versions.


Listener does not return response for DELETE /db

with 1.3.0-30
http DELETE http://localhost:5984/testdb

No response

Expected (CouchDB and Mac OSX behavior):
{"ok":true}

This is a regression. This works with 1.2.1

@sethrosetter
Does LiteServ return HTTP Header?

http -v DELETE http://<IP_ADDRESS>:8081/testdb

DELETE /testdb HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Length: 0
Host: <IP_ADDRESS>:8081
User-Agent: HTTPie/0.9.3

HTTP/1.1 200 Ok
connection: keep-alive
date: Fri, 15 Jul 2016 16:59:13 GMT
keep-alive: timeout=30, max=100
mime-version: 1.0
server: D. Rogatkin's TJWS with Android support (aka Acme.Serve)/Version 1.105, $Revision: 1.267 $,Couchbase Lite 1.3.0-30
transfer-encoding: chunked

I tested with curl against LiteServ. Response body is returned.
hideki@hidekis:~$ curl -X "DELETE" http://<IP_ADDRESS>:5984/db
{"ok":true}hideki@hidekis:~$


Require some value in search boxes

Do we want to require the user to enter some value in the search box for both package and vulnerability searches?  Package search currently allows an empty search; vulnerability search requires some value but even "j" or "2" works.  (For the time being, the new UI will require that the user enter some -- any -- value in those search boxes or else encounter a popup warning.)

I think we should not allow empty searches anywhere: both on the UI and in the API; that's the common behaviour for any search engine I know of.
We should likely also restrict the search to two characters minimum. Searching for less does not make much sense IMHO. I can understand that Google allows to search for something like a or b... but that's not for us.
IMHO also a popup is not the best UX: rather with no search, nothing should happen when you click on search or press enter. Just nothing until you enter something to search.
And if you enter too few characters a simple warning message below the search box would be a better hint IMHO NB: this could be a refinement added later as this is not critical)

I've updated the package and vulnerability searches to do nothing when the search box is empty -- using jQuery, and stripping leading/trailing spaces as well (which also takes care of a user who enters only 1+ spaces).
Will tackle the minimum-character requirement after I've taken care of some higher-priority items.  I could do this with jQuery and a client-side alert dialog, but that display differs from the div-based display I've implemented for 0 hits (these are server-based and appear outlined in red plus red text just below the relevant search box).

AJAX might be ideal to avoid reloading the page for a server-side message, which reloads the page and loses the current scroll position, or would that be introducing excessive complexity . . . ?
A syntactically-incorrect purl search is evaluated server-side but currently treats that input as a package name search (via a try/except) and thus returns a 0-hit message.  I'd like to advise the user when the purl is malformed but that seems challenging when we're using 1 search box for purl as well as package name searches (now implemented).

See also new issue opened by @pombredanne -- https://github.com/nexB/vulnerablecode/issues/871


Exceptions encountered when running Razor Components application

I encountered these errors while trying to debug a Razor Components applications (the benchmarks UI by @sebastienros). The first exception was an ArgumentOutOfRangeException while trying to build the render tree. It looks like it was swallowed.
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: chunkLength
   at System.Text.StringBuilder.ToString()
   at Microsoft.AspNetCore.Blazor.RenderTree.RenderTreeBuilder.AddContent(Int32 sequence, Object textContent)
   at Benchmarks.UI.App.Pages.Index.BuildRenderTree(RenderTreeBuilder builder) in C:\dev\git\Benchmarks\src\Benchmarks.UI.App\Pages\Index.cshtml:line 251
   at Microsoft.AspNetCore.Blazor.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Blazor.Rendering.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
   at Microsoft.AspNetCore.Blazor.Rendering.Renderer.ProcessRenderQueue()
   at Microsoft.AspNetCore.Blazor.Rendering.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Blazor.Server.Circuits.CircuitSynchronizationContext.ExecuteSynchronously(TaskCompletionSource`1 completion, SendOrPostCallback d, Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Blazor.Server.Circuits.CircuitSynchronizationContext.ExecuteBackground(WorkItem item)
Exception thrown: 'MessagePack.Internal.MessagePackDynamicObjectResolverException' in MessagePack.dll
Exception thrown: 'System.TypeInitializationException' in MessagePack.dll
Exception thrown: 'System.TypeInitializationException' in MessagePack.dll
Exception thrown: 'System.TypeInitializationException' in MessagePack.dll
Exception thrown: 'System.TypeInitializationException' in Microsoft.AspNetCore.SignalR.Protocols.MessagePack.dll
Exception thrown: 'MessagePack.Internal.MessagePackDynamicObjectResolverException' in MessagePack.dll
Exception thrown: 'System.NullReferenceException' in Microsoft.AspNetCore.Blazor.dll
Exception thrown: 'System.NullReferenceException' in System.Private.CoreLib.dll
Microsoft.AspNetCore.Blazor.Server.BlazorHub:Warning: Unhandled Server-Side exception

This second exception ended up crashing the process (likely an async void somewhere 😉 )
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.AspNetCore.Blazor.RenderTree.RenderTreeDiffBuilder.UpdateRetainedChildComponent(DiffContext& diffContext, Int32 oldComponentIndex, Int32 newComponentIndex)
   at Microsoft.AspNetCore.Blazor.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
   at Microsoft.AspNetCore.Blazor.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
   at Microsoft.AspNetCore.Blazor.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
   at Microsoft.AspNetCore.Blazor.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
   at Microsoft.AspNetCore.Blazor.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
   at Microsoft.AspNetCore.Blazor.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
   at Microsoft.AspNetCore.Blazor.RenderTree.RenderTreeDiffBuilder.ComputeDiff(Renderer renderer, RenderBatchBuilder batchBuilder, Int32 componentId, ArrayRange`1 oldTree, ArrayRange`1 newTree)
   at Microsoft.AspNetCore.Blazor.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Blazor.Rendering.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
   at Microsoft.AspNetCore.Blazor.Rendering.Renderer.ProcessRenderQueue()
   at Microsoft.AspNetCore.Blazor.Rendering.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Blazor.Server.Circuits.CircuitSynchronizationContext.ExecuteSynchronously(TaskCompletionSource`1 completion, SendOrPostCallback d, Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Blazor.Server.Circuits.CircuitSynchronizationContext.ExecuteBackground(WorkItem item)
Exception thrown: 'System.TypeInitializationException' in Microsoft.AspNetCore.SignalR.Protocols.MessagePack.dll
Exception thrown: 'MessagePack.Internal.MessagePackDynamicObjectResolverException' in MessagePack.dll
Exception thrown: 'System.NullReferenceException' in Microsoft.AspNetCore.Blazor.dll
Exception thrown: 'System.NullReferenceException' in System.Private.CoreLib.dll
Exception thrown: 'System.NullReferenceException' in System.Private.CoreLib.dll
Exception thrown: 'System.NullReferenceException' in Microsoft.AspNetCore.Blazor.dll
An unhandled exception of type 'System.NullReferenceException' occurred in System.Private.CoreLib.dll
Object reference not set to an instance of an object.

cc @SteveSandersonMS @rynowak @javiercn

Do you have repro steps?

Nope, couldn't narrow it down. The application is here https://github.com/aspnet/Benchmarks/tree/master/src/Benchmarks.UI.Server. I might try to update to a newer version of razor components to see if that helps.

Ah, it was 0.7.0. There was a bad thread safety bug with rendering reported by a lot of people. It manifested in various ways, because it allowed corruption of some internal data structures.
We eliminated the bad asynchrony in 0.8.0 (or Preview 2 for Razor Components) and it went away as expected.
If you still experience it with > 0.7.0, please let us know!

@SteveSandersonMS I'll try moving the app to razor components.


feat: failOnConsole should print the log right away

Feature description
failOnConsole() by default will capture all errors, and output them at the end of the test.
However, that has undesirable consequences:

If you are debugging the test, seeing the console errors right away is very helpful.

If the test is going to time out, the developer won't see the console message until after the timeout. By logging the error right away, you see what might have caused the test to timeout, without having to wait for the timeout.

Even though failOnConsole() tries to capture the stack trace and output it when logging the message again at the end, that still does not preserve the stack trace of async actions (i.e .catch(console.error)) (see https://stackoverflow.com/q/59726106/8584605 for more details).
At the same time, browser DevTools have features for piecing together async stack traces - but this "piecing together" seems to only happen when you let the console error through naturally - accessing the new Error() stack trace does not include this. So having the console error logged right away is very helpful.

For the above reasons, I propose that failOnConsole should print the message right away.

Given the following comment in the failOnConsole's code, I think this change will still be fine - you let the console messages though, but then throw an error at the end saying that unexpected console messages got printed during the test execution.
https://github.com/thomasbrodusch/vitest-fail-on-console/blob/d6b7b3bcb5758862d7f5470d308b16339eef3e2e/src/index.ts#L89
The error message at the end of the test doesn't need to include the console messages again. But if for some reason that I am not aware of that is necessary, then having the console message printed twice is still less bad than the current behavior (see the reasons listed above).
Workaround
I am using the silenceMessage option to "hack" failOnConsole into the correct behavior:
  const originalConsole = { ...console };
  failOnConsole({
    silenceMessage(message, methodName) {
      originalConsole[methodName](message);
      return false;
    },
  });

Hi @maxpatiiuk thanks for raising an issue!
In my opinion, this is more like an improvement request rather than a critical issue.
That said, you can totally make a  new PR proposal ;)


Change sorting order

At the moment apps are always sorted alphabetically, so I'd suggest some other method(s) that are more dynamic and, therefore, less biased. Perhaps a mix of popular and recently updated to mix things up.

How?
We don't have any information about what is popular or what has been updated.

Yeah, I understand. But it is possible. For popularity, you could count clicks. For recently updated, well, that's more complicated still and I can only think of scraping :/
But I'm only suggesting because it would really improve the overall experience :)

Counting clicks across users would require a server and that is not really within the scope of this project.


Sequence to sequence training and predicting (Decoder Encoder)

I have 2 questions:

I discussed about sequence to sequence learning where the length of input and output are different in problem #2403 and I concluded that I have to use encoder and decoder architecture. I have a fundamental question, what is the reason that keras doesn't support this case and encoder and decoder is needed.  Is it a fundamental problem of recurrent neural networks (if it is, can anyone explain this to me?), or is it the Keras problem that doesn't support this case?

2.When I have the following model:
      model = Sequential()
      hidden_neurons = 50
      model.add(LSTM(hidden_neurons,
             batch_input_shape=(batch_size, n_prev, 1),
             forget_bias_init='one',
             return_sequences=True,
             stateful=True))
     model.add(LSTM(hidden_neurons,
             batch_input_shape=(batch_size, n_prev, 1),
             forget_bias_init='one',
             return_sequences=False,
             stateful=True))

    model.add(Dense(n_nxt))
    model.compile(loss='mse', optimizer='rmsprop')

consider batch_size =1, then which of the following statement is true:
A. All n_prev inputs are fed to all  hidden_neurons in the first LSTM layer?
B. At each time only one of in_prev inputs are fed  to the first LSTM layer and it will propagate to all other hidden_neurons in this layer?

batch_input_shape=(batch_size, timesteps, feature_dim)

@mininaNik  Question about your code:
the first LSTM has an output dimension of hidden_neurons, why do you (or why are you allowed to) define the second LSTM input dimension to be 1?

@mininaNik I guess batch_input_shape for the second LSTM is ignored, as answered for Q2 in #3038


[submodule-sync] bot-submodule-sync-branch-22.06 to branch-22.06 [skip ci] [bot]

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
 If failed, it will remain open until test pass or manually fix.


Inquiry about pre-trained checkpoint

Hi, thanks for the great work. May I ask if we can have access to the pre-trained checkpoint of RVT-base on eTram? By the way, it seems that the RVT model only supports the h5 format, but I can only find raw dvs format from the download link. Do you have any plans to upload the h5 format dataset in the future? I'm looking forward to your reply.

Hi @harryma123 thank you for reaching out and for your interest in eTraM. Regarding your question, we've made the RVT-base checkpoint available along with the data in .h5 format. You can now access both resources conveniently. If you encounter any further issues or have additional questions, please don't hesitate to ask.

Hi @aayush-v , thanks for your prompt response. I tested the ckpt and found that it only supports ('pedestrian', 'car', 'bicycle'). However, in your paper, the eTram dataset contains 8 different classes. So, I would like to know if you have an 8-class ckpt available.
By the way, if I want to generate my own customized dataset, does the class ID matter for training? If I hard code it to zero, would it still make sense?

Hi @harryma123, our baselines are established on the three major traffic participant categories - Pedestrians, Vehicles (car, bus, truck, tram), and Micro-mobility (bicycle, bike, wheelchair) and the checkpoint corresponding to that experiment has been made available. In addition to these annotations, we also provide the annotations of 8 different classes as mentioned in the paper.
As for your second question, the class ID does matter since training is done for an object detection task. If you hard code all class IDs to zero your model will essentially learn to localize the presence of an object, and not actually classify them.

Hi @aayush-v , I'm sorry if I haven't described it clearly. I actually meant the track ID, not the class ID. Does it make a difference for model training? Additionally, I would like to know if you have a pretrained checkpoint for YOLOv8 available.

The tracking IDs do not matter for the object detection algorithms used. They completely depend on Class IDs, so it would not make a difference if you hard coded them to zero.
As of now, we do not have any immediate plans for a YOLOv8 pretrained checkpoint, nevertheless you can utilize the code in our repository to train the model.


Implement tide_disco::error::Error for builder::Error

Trait bound needed to construct surf_disco::Client<builder::Error>.

 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.Quentin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


ci: support 3.13

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.37%. Comparing base (4c3f6c7) to head (135bc77).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #462   +/-   ##
=======================================
  Coverage   85.37%   85.37%
=======================================
  Files          19       19
  Lines        2120     2120
=======================================
  Hits         1810     1810
  Misses        310      310

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


Zooniverse metadata upload

Is your feature request related to a problem? Please describe.
When uploading to zooniverse, the only metadata uploaded with the subjects is the date of extraction.
We encountered situations where subjects were uploaded to zooniverse but childproject did not confirm those uploads. In those conditions, we don't have anything linking the zooniverse subject to the chunks in the csv generated by child-project (as it was not updated with subject ID for those)
Describe the solution you'd like
Add some useful metadata to the uploads, index of the dataset and mp3 filename should suffice

#429


fix: typo on Debug property because are unexported

Affected Components

[ ] New Features
[ ] Bug Fixing
[ ] Types
[ ] Tests
[x] Docs
[ ] Other

Notes for the Reviewer
This PR includes fixes for the following issues:

https://github.com/checkly/checkly-go-sdk/issues/35#issue-993705710

Hi @kenriortega, we just shipped a fix for this showing how to set up the debug property. Anyway, thank you very much :)


DU tests consistently fail locally on Manjaro machine

Most du tests fail locally on my Linux machine due to incorrect directory sizes.
---- test_du::test_du_basics_subdir stdout ----
current_directory_resolved:
run: /home/gilad/repos/coreutils/target/debug/coreutils du subdir/deeper
thread 'test_du::test_du_basics_subdir' panicked at 'assertion failed: `(left == right)`
  left: `"4\tsubdir/deeper\n"`,
 right: `"8\tsubdir/deeper\n"`', /home/gilad/repos/coreutils/tests/by-util/test_du.rs:55:9

---- test_du::test_du_d_flag stdout ----
current_directory_resolved:
run: /home/gilad/repos/coreutils/target/debug/coreutils du -d 1
thread 'test_du::test_du_d_flag' panicked at 'assertion failed: `(left == right)`
  left: `"16\t./subdir\n20\t./\n"`,
 right: `"28\t./subdir\n36\t./\n"`', /home/gilad/repos/coreutils/tests/by-util/test_du.rs:159:9

---- test_du::test_du_hard_link stdout ----
current_directory_resolved:
run: /home/gilad/repos/coreutils/target/debug/coreutils ln subdir/links/subwords.txt subdir/links/sublink.txt
run: /home/gilad/repos/coreutils/target/debug/coreutils du subdir/links
thread 'test_du::test_du_hard_link' panicked at 'assertion failed: `(left == right)`
  left: `"12\tsubdir/links\n"`,
 right: `"16\tsubdir/links\n"`', /home/gilad/repos/coreutils/tests/by-util/test_du.rs:131:9

---- test_du::test_du_soft_link stdout ----
current_directory_resolved:
run: /home/gilad/repos/coreutils/target/debug/coreutils ln -s subdir/links/subwords.txt subdir/links/sublink.txt
run: /home/gilad/repos/coreutils/target/debug/coreutils du subdir/links
thread 'test_du::test_du_soft_link' panicked at 'assertion failed: `(left == right)`
  left: `"12\tsubdir/links\n"`,
 right: `"16\tsubdir/links\n"`', /home/gilad/repos/coreutils/tests/by-util/test_du.rs:99:9

Note that GNU du report the same sizes as uutils, so it seems like the values hardcoded in the test suite are not true for all linux installs.
Not sure what affects these sizes. I'm using Manjaro Linux with kernel 5.10 and ext4.
Not sure how to fix the test. Ideally we could just equate to actual GNU du output, but I'm not sure we can assume it exists on the machine running the tests.
Maybe not worth fixing.

IIRC the directory size is 4KiB for most if not all Linux installations I've ever touched.
I wonder what machines in GitHub Actions have different values for Linux.

These tests also fail on my linux box (5.11.11-200.fc33.x86_64).

Not sure how to fix the test. Ideally we could just equate to actual GNU du output, but I'm not sure we can assume it exists on the machine running the tests.

I also think dynamically taking reference values from the local du, provided that du is available, is a better option than hard coded reference values only. (If du is not available, falling back to the hard coded values would be my choice.)


clean up unused code

remove code for

ad blocker stuff
app stuff
consent (windowshade) stuff
javascript-based opt out stuff

resolved in 1.4.2


oracle  metric save Update b_obvisitor.py

Codecov Report

Merging #530 (cc7ffd4) into master (83d5e59) will decrease coverage by 0.32%.
The diff coverage is 82.60%.

@@            Coverage Diff             @@
##           master     #530      +/-   ##
==========================================
- Coverage   95.44%   95.12%   -0.32%
==========================================
  Files         131      131
  Lines        4718     4741      +23
==========================================
+ Hits         4503     4510       +7
- Misses        215      231      +16

Flag
Coverage Δ

unittests
95.12% <82.60%> (-0.32%)
:arrow_down:

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

Files
Coverage Δ

domainlab/algos/observers/b_obvisitor.py
85.84% <94.44%> (+1.63%)
:arrow_up:

domainlab/algos/msels/c_msel_oracle.py
91.42% <40.00%> (-8.58%)
:arrow_down:

... and 4 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more