Failed to start with 0.131

Describe the bug
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2024/10/23 14:15:54 evcc 0.131.0
[main  ] INFO 2024/10/23 14:15:54 using config file: /config/evcc.yaml
[main  ] FATAL 2024/10/23 14:16:11 cannot create meter 'carport_pv_slave': cannot create meter type 'template': cannot create meter type 'custom': currents: [0] sunspec model not found: [{103 0 AphA}]
[main  ] FATAL 2024/10/23 14:16:11 will attempt restart in: 15m0s
Steps to reproduce

INstall update.

...
Configuration details
meters:
  - name: solaredge_grid
    type: template
    template: solaredge-inverter
    usage: grid
    modbus: tcpip
    id: 1
    host: <IP_ADDRESS> # Hostname
    port: 526
    # host: <IP_ADDRESS> # Hostname
    # port: 5206
    timeout: 3s

  - name: house_battery_master
    type: template
    template: solaredge-hybrid
    usage: battery
    modbus: tcpip
    id: 1
    host: <IP_ADDRESS> # Hostname
    port: 526
    # host: <IP_ADDRESS> # Hostname
    # port: 5206
    timeout: 3s

  - name: house_pv_master
    type: template
    template: solaredge-hybrid
    usage: pv
    modbus: tcpip
    id: 1
    host: <IP_ADDRESS> # Hostname
    port: 526
    # host: <IP_ADDRESS> # Hostname
    # port: 5206
    timeout: 3s

  - name: house_pv_slave
    type: template
    template: solaredge-hybrid
    usage: pv
    modbus: tcpip
    id: 3
    host: <IP_ADDRESS> # Hostname
    port: 527
    # host: <IP_ADDRESS> # Hostname
    # port: 5207
    timeout: 3s

  - name: pool_pv_slave
    type: template
    template: solaredge-inverter
    usage: pv
    modbus: tcpip
    id: 4
    host: <IP_ADDRESS> # Hostname
    port: 525
    # host: <IP_ADDRESS> # Hostname
    # port: 5205
    timeout: 3s

  - name: carport_pv_slave
    type: template
    template: solaredge-inverter
    usage: pv
    modbus: tcpip
    id: 5
    host: <IP_ADDRESS> # Hostname
    port: 528
    # host: <IP_ADDRESS> # Hostname
    # port: 5208
    timeout: 3s

#  - name: gate_pv
#    type: custom
#    power:
#      source: mqtt
#      topic: inverter/Gate/ch0/P_AC
#      timeout: 120s

# charger definitions
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for documentation see https://docs.evcc.io/docs/devices/chargers
chargers:
  - name: keba_p30_hh
    type: template
    template: keba-modbus
    modbus: tcpip
    host: <IP_ADDRESS>
    port: 529
    # host: <IP_ADDRESS>
    # port: 5209
    # serial: 24248092
    # rfid: 047E6272E96E80

  - name: pool_pump
    type: template
    template: shelly
    host: <IP_ADDRESS>
    standbypower: 1
    icon: waterheater
    integrateddevice: true

  - name: pool_heating
    type: template
    template: shelly
    host: <IP_ADDRESS>
    standbypower: 1
    icon: waterheater
    integrateddevice: true
    heating: true

    # vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for documentation see https://docs.evcc.io/docs/devices/vehicles
vehicles:
  - name: buzz
    type: template
    template: vw
    title: ID.BUZZ
    capacity: 77 # kWh
    phases: 0
    user<EMAIL_ADDRESS>    password: Nud3lD!ck?
    vin: WV2ZZZEB0PH009869
    icon: bus
    mode: pv
    identifiers:
      - 047E6272E96E80
      - 047E6272E96E8000

  - name: up
    type: template
    template: vw
    title: e.up!
    capacity: 32 # kWh
    phases: 0
    user<EMAIL_ADDRESS>    password: Nud3lD!ck?
    vin: WVWZZZAAZMD900317
    icon: car
    mode: pv
    identifiers:
      - 047728A27A7480
      - 047728a27a748000

  - type: template
    template: offline
    title: Pool - Pump
    icon: waterheater
    phases: 1
    mode: off
    name: pool_pump

  - name: pool_heating
    title: Pool - Heatimg
    type: custom
    icon: waterheater
    phases: 1
    soc:
      source: mqtt
      topic: heiligenhaus/pool/temperatur

# site describes the EVU connection, PV and home battery
site:
  title: Görscheider Weg # display name for UI
  meters:
    grid: solaredge_grid # grid meter
    battery:
      - house_battery_master
    pv:
      - house_pv_master
      - house_pv_slave
      - carport_pv_slave
      - pool_pv_slave
    # - gate_pv # list of pv inverters/ meters
    # aux:
    #   - aux # list of auxiliary meters for adjusting grid operating point
  residualPower: 200 # additional household usage margin
  prioritySoc: # give home battery priority up to this soc (empty to disable)
  bufferSoc: # ignore home battery discharge above soc (empty to disable)
  maxGridSupplyWhileBatteryCharging: # ignore battery charging if AC consumption is above this value
  smartCostLimit: # set cost limit for automatic charging in PV mode

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Garage # display name for UI
    charger: keba_p30_hh # charger
    mode: "pv" # set default charge mode, use "off" to disable by default if charger is publicly available
    # vehicles:
    #   - up
    #   - buzz
    phases: 0 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)

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

  - title: Pool - Pump # display name for UI
    charger: pool_pump # charger
    vehicle: pool_pump
    # meter: grid # charge meter
    mode: "off" # set default charge mode, use "off" to disable by default if charger is publicly available
    # phases: 1 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    # minCurrent: 1 # minimum charge current (default 6A)
    # maxCurrent: 1 # maximum charge current (default 16A)
    enable:
      threshold: -1000
      delay: 1m
    disable: # pv mode disable behavior
      threshold: 0 # maximum import power (W)
      delay: 1m # threshold must be exceeded for this long

    priority: 120 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
    guardDuration: 1m # switch charger contactor not more often than this (default 5m)

  - title: Pool - Heating # display name for UI
    charger: pool_heating # charger
    vehicle: pool_heating
    # meter: grid # charge meter
    mode: "off" # set default charge mode, use "off" to disable by default if charger is publicly available
    # phases: 1 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    # minCurrent: 1 # minimum charge current (default 6A)
    # maxCurrent: 1 # maximum charge current (default 16A)
    enable:
      threshold: -2800
      delay: 5m
    disable: # pv mode disable behavior
      threshold: 0 # maximum import power (W)
      delay: 5m # threshold must be exceeded for this long

    priority: 110 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
    guardDuration: 10m # switch charger contactor not more often than this (default 5m)
    soc:
      estimate: false
      poll:
        mode: always
        interval: 5m

Log details
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2024/10/23 14:15:54 evcc 0.131.0
[main  ] INFO 2024/10/23 14:15:54 using config file: /config/evcc.yaml
[main  ] FATAL 2024/10/23 14:16:11 cannot create meter 'carport_pv_slave': cannot create meter type 'template': cannot create meter type 'custom': currents: [0] sunspec model not found: [{103 0 AphA}]
[main  ] FATAL 2024/10/23 14:16:11 will attempt restart in: 15m0s

What type of operating system are you running?
HomeAssistant Add-on
Nightly build

[X] I have verified that the issue is reproducible with the latest nightly build

Version
0.131

Could you please show
evcc sunspec

For your SolarEdge?

I had also issues that it evcc was not booting but no logs due to the HA addon which only offers a short log and said it was waiting which then was repeated every 2 minutes or so.
I decided to stop and went back to 1.30.13 due to the issue.

Sorry, took me a while to learn how to come into the docker container :)
/app # evcc sunspec <IP_ADDRESS>:528 -i 5
[main  ] INFO 2024/10/23 14:53:52 evcc 0.130.13
--------- Model 1 common ---------
Mn         SolarEdge     string
Md   SE4000H-RW000BEN    string
Opt                      string
Vr           0004.002    string
SN           75032C20    string
DA               5.00    uint16
Pad            0x0065    pad
--------- Model 101 inverter ---------
A                    0.47    uint16
AphA                 0.47    uint16
AphB                  n/a    uint16
AphC                  n/a    uint16
A_SF                   -2    sunssf
PPVphAB            236.70    uint16
PPVphBC               n/a    uint16
PPVphCA               n/a    uint16
PhVphA             236.70    uint16
PhVphB                n/a    uint16
PhVphC                n/a    uint16
V_SF                   -1    sunssf
W                   68.15    int16
W_SF                   -2    sunssf
Hz                  49.98    uint16
Hz_SF                  -3    sunssf
VA                 112.45    int16
VA_SF                  -2    sunssf
VAr                 89.45    int16
VAr_SF                 -2    sunssf
PF                  60.60    int16
PF_SF                  -2    sunssf
WH             3039209.00    acc32
WH_SF                   0    sunssf
DCA                  0.19    uint16
DCA_SF                 -5    sunssf
DCV                369.70    uint16
DCV_SF                 -1    sunssf
DCW                 69.19    int16
DCW_SF                 -2    sunssf
TmpCab                n/a    int16
TmpSnk              31.97    int16
TmpTrns               n/a    int16
TmpOt                 n/a    int16
Tmp_SF                 -2    sunssf
St                      4    enum16
StVnd                   0    enum16
Evt1                  n/a    bitfield32
Evt2                  n/a    bitfield32
EvtVnd1        0x00000000    bitfield32
EvtVnd2               n/a    bitfield32
EvtVnd3               n/a    bitfield32
EvtVnd4        0x00000000    bitfield32

I have tried it again under HA Addon
and I got this log
"Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2024/10/23 15:07:38 evcc 0.131.0
[main  ] INFO 2024/10/23 15:07:38 using config file: /config/evcc.yaml
[mqtt  ] INFO 2024/10/23 15:07:39 connecting evcc-2126174612 at tcp://<IP_ADDRESS>:1883
[mqtt  ] DEBUG 2024/10/23 15:07:39 tcp://<IP_ADDRESS>:1883 connected
[main  ] INFO 2024/10/23 15:07:39 listening at :7070
[Garage-1] DEBUG 2024/10/23 15:07:39 waiting for chargepoint: 5m0s
[ocpp  ] DEBUG 2024/10/23 15:08:37 charge point connected: Garage
[ocpp  ] TRACE 2024/10/23 15:08:37 enqueued CALL [1093396971, ChangeAvailability] for Garage
[ocpp  ] TRACE 2024/10/23 15:08:37 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:08:37 sent JSON message to Garage: [2,"1093396971","ChangeAvailability",{"connectorId":0,"type":"Operative"}]
[ocpp  ] TRACE 2024/10/23 15:08:37 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:09:07 timeout for client Garage, canceling message
[ocpp  ] TRACE 2024/10/23 15:09:07 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:09:07 request<PHONE_NUMBER> for Garage timed out
[ocpp  ] TRACE 2024/10/23 15:09:07 Garage ready to transmit again
[Garage-1] DEBUG 2024/10/23 15:09:07 failed configuring availability: timeout
[ocpp  ] TRACE 2024/10/23 15:09:07 enqueued CALL [1613254401, GetConfiguration] for Garage
[ocpp  ] TRACE 2024/10/23 15:09:07 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:09:07 sent JSON message to Garage: [2,"1613254401","GetConfiguration",{}]
[ocpp  ] TRACE 2024/10/23 15:09:07 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:09:37 timeout for client Garage, canceling message
[ocpp  ] TRACE 2024/10/23 15:09:37 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:09:37 request<PHONE_NUMBER> for Garage timed out
[ocpp  ] TRACE 2024/10/23 15:09:37 Garage ready to transmit again
[main  ] FATAL 2024/10/23 15:09:37 cannot create charger 'wallbox4': cannot create charger type 'template': cannot create charger type 'ocpp': timeout
[main  ] FATAL 2024/10/23 15:09:37 will attempt restart in: 15m0s
...
[ocpp  ] TRACE 2024/10/23 15:12:00 received JSON message from Garage: [2,"1623527199","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:11:59Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "226.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "234.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "233.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:12:00 handling incoming CALL [1623527199, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:00 sent CALL RESULT [1623527199] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:00 sent JSON message to Garage: [3,"1623527199",{}]
[ocpp  ] TRACE 2024/10/23 15:12:10 enqueued CALL [2379615324, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:10 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:12:10 sent JSON message to Garage: [2,"2379615324","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:12:10 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:12:10 received JSON message from Garage: [3,"2379615324",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:12:10 handling incoming CALL RESULT [2379615324] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:10 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:12:10 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:12:10 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:12:10 received JSON message from Garage: [2,"115155578","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:12:09Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "226.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "234.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "233.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:12:10 handling incoming CALL [115155578, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:10 sent CALL RESULT [115155578] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:10 sent JSON message to Garage: [3,"115155578",{}]
[ocpp  ] TRACE 2024/10/23 15:12:20 enqueued CALL [684530518, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:20 dispatched request 684530518 for Garage
[ocpp  ] TRACE 2024/10/23 15:12:20 sent JSON message to Garage: [2,"684530518","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:12:20 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:12:20 received JSON message from Garage: [3,"684530518",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:12:20 handling incoming CALL RESULT [684530518] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:20 completed request 684530518 for Garage
[ocpp  ] TRACE 2024/10/23 15:12:20 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:12:20 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:12:20 received JSON message from Garage: [2,"973552722","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:12:19Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "226.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "234.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:12:20 handling incoming CALL [973552722, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:20 sent CALL RESULT [973552722] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:20 sent JSON message to Garage: [3,"973552722",{}]
[ocpp  ] TRACE 2024/10/23 15:12:30 enqueued CALL [218595078, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:30 dispatched request 218595078 for Garage
[ocpp  ] TRACE 2024/10/23 15:12:30 sent JSON message to Garage: [2,"218595078","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:12:30 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:12:30 received JSON message from Garage: [3,"218595078",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:12:30 handling incoming CALL RESULT [218595078] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:30 completed request 218595078 for Garage
[ocpp  ] TRACE 2024/10/23 15:12:30 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:12:30 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:12:30 received JSON message from Garage: [2,"843871112","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:12:29Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "226.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "234.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:12:30 handling incoming CALL [843871112, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:30 sent CALL RESULT [843871112] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:30 sent JSON message to Garage: [3,"843871112",{}]
[ocpp  ] TRACE 2024/10/23 15:12:40 enqueued CALL [562132803, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:40 dispatched request 562132803 for Garage
[ocpp  ] TRACE 2024/10/23 15:12:40 sent JSON message to Garage: [2,"562132803","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:12:40 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:12:40 received JSON message from Garage: [3,"562132803",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:12:40 handling incoming CALL RESULT [562132803] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:40 completed request 562132803 for Garage
[ocpp  ] TRACE 2024/10/23 15:12:40 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:12:40 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:12:40 received JSON message from Garage: [2,"2011950819","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:12:39Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "226.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "233.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:12:40 handling incoming CALL [2011950819, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:40 sent CALL RESULT [2011950819] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:40 sent JSON message to Garage: [3,"2011950819",{}]
[ocpp  ] TRACE 2024/10/23 15:12:50 received JSON message from Garage: [2,"1016908597","Heartbeat",{}]
[ocpp  ] TRACE 2024/10/23 15:12:50 handling incoming CALL [1016908597, Heartbeat] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 sent CALL RESULT [1016908597] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 sent JSON message to Garage: [3,"1016908597",{"currentTime":"2024-10-23T13:12:50Z"}]
[ocpp  ] TRACE 2024/10/23 15:12:50 enqueued CALL [776020957, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 dispatched request 776020957 for Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 sent JSON message to Garage: [2,"776020957","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:12:50 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 received JSON message from Garage: [3,"776020957",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:12:50 handling incoming CALL RESULT [776020957] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 completed request 776020957 for Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:12:50 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 received JSON message from Garage: [2,"219543390","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:12:50Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "226.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "233.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:12:50 handling incoming CALL [219543390, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 sent CALL RESULT [219543390] for Garage
[ocpp  ] TRACE 2024/10/23 15:12:50 sent JSON message to Garage: [3,"219543390",{}]
[ocpp  ] TRACE 2024/10/23 15:13:00 enqueued CALL [2845786369, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:13:00 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:13:00 sent JSON message to Garage: [2,"2845786369","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:13:00 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:13:11 received JSON message from Garage: [3,"2845786369",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:13:11 handling incoming CALL RESULT [2845786369] from Garage
[ocpp  ] TRACE 2024/10/23 15:13:11 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:13:11 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:13:11 dispatched request 750523241 for Garage
[ocpp  ] TRACE 2024/10/23 15:13:11 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:13:11 sent JSON message to Garage: [2,"750523241","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:13:11 enqueued CALL [750523241, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:13:11 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:13:11 received JSON message from Garage: [3,"750523241",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:13:11 handling incoming CALL RESULT [750523241] from Garage
[ocpp  ] TRACE 2024/10/23 15:13:11 completed request 750523241 for Garage
[ocpp  ] TRACE 2024/10/23 15:13:11 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:13:11 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:13:12 enqueued CALL [1667679634, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:13:12 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:13:12 sent JSON message to Garage: [2,"1667679634","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:13:12 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:13:12 received JSON message from Garage: [3,"1667679634",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:13:12 handling incoming CALL RESULT [1667679634] from Garage
[ocpp  ] TRACE 2024/10/23 15:13:12 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:13:12 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:13:12 timeout canceled for Garage"
But it looks like that it successfully reached my inverter and stopped that from charging the battery cause the AC charging is no longer running. I had tried that home storage charging based on price < 29 cent but it did not work. So i went to my inverter and set up a schedule to charge now from AC but this has been stopped now.
Here you can see the red area which is energy from the grid used to charge the battery with 3 kW max and AC power from the grid if there is no surplus.
Then there was break cause by the installation and start of evcc 1.31.0 and then i was reable to restart the AC charging via Growatt Cloud.

and now it has turned red again within 5 minutes
[ocpp  ] TRACE 2024/10/23 15:23:51 handling incoming CALL [6283719, StatusNotification] from Garage
[ocpp  ] TRACE 2024/10/23 15:23:51 sent CALL RESULT [6283719] for Garage
[ocpp  ] TRACE 2024/10/23 15:23:51 sent JSON message to Garage: [3,"6283719",{}]
[main  ] FATAL 2024/10/23 15:23:51 cannot create charger 'wallbox4': cannot create charger type 'template': cannot create charger type 'ocpp': sponsorship required, see https://github.com/evcc-io/evcc#sponsorship
[main  ] FATAL 2024/10/23 15:23:51 will attempt restart in: 15m0s
[ocpp  ] TRACE 2024/10/23 15:23:56 enqueued CALL [1913146757, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:23:56 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:23:56 sent JSON message to Garage: [2,"1913146757","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:23:56 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:23:56 received JSON message from Garage: [3,"1913146757",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:23:56 handling incoming CALL RESULT [1913146757] from Garage
[ocpp  ] TRACE 2024/10/23 15:23:56 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:23:56 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:23:56 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:23:56 received JSON message from Garage: [2,"750216102","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:23:56Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "227.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "234.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:23:56 handling incoming CALL [750216102, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:23:56 sent CALL RESULT [750216102] for Garage
[ocpp  ] TRACE 2024/10/23 15:23:56 sent JSON message to Garage: [3,"750216102",{}]
[ocpp  ] TRACE 2024/10/23 15:24:06 enqueued CALL [3703372465, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:06 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:24:06 sent JSON message to Garage: [2,"3703372465","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:24:06 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:24:06 received JSON message from Garage: [3,"3703372465",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:24:06 handling incoming CALL RESULT [3703372465] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:06 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:24:06 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:24:06 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:24:06 received JSON message from Garage: [2,"1472806988","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:24:06Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "227.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "233.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:24:06 handling incoming CALL [1472806988, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:06 sent CALL RESULT [1472806988] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:06 sent JSON message to Garage: [3,"1472806988",{}]
[ocpp  ] TRACE 2024/10/23 15:24:16 enqueued CALL [521495271, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:16 dispatched request 521495271 for Garage
[ocpp  ] TRACE 2024/10/23 15:24:16 sent JSON message to Garage: [2,"521495271","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:24:16 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:24:16 received JSON message from Garage: [3,"521495271",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:24:16 handling incoming CALL RESULT [521495271] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:16 completed request 521495271 for Garage
[ocpp  ] TRACE 2024/10/23 15:24:16 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:24:16 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:24:16 received JSON message from Garage: [2,"408520902","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:24:16Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "227.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "233.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:24:16 handling incoming CALL [408520902, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:16 sent CALL RESULT [408520902] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:16 sent JSON message to Garage: [3,"408520902",{}]
[ocpp  ] TRACE 2024/10/23 15:24:26 enqueued CALL [3805868050, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:26 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:24:26 sent JSON message to Garage: [2,"3805868050","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:24:26 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:24:26 received JSON message from Garage: [3,"3805868050",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:24:26 handling incoming CALL RESULT [3805868050] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:26 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:24:26 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:24:26 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:24:26 received JSON message from Garage: [2,"1441635954","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:24:26Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "227.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "233.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:24:26 handling incoming CALL [1441635954, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:26 sent CALL RESULT [1441635954] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:26 sent JSON message to Garage: [3,"1441635954",{}]
[ocpp  ] TRACE 2024/10/23 15:24:36 enqueued CALL [2787394014, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:36 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:24:36 sent JSON message to Garage: [2,"2787394014","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:24:36 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:24:36 received JSON message from Garage: [3,"2787394014",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:24:36 handling incoming CALL RESULT [2787394014] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:36 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:24:36 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:24:36 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:24:36 received JSON message from Garage: [2,"1162703637","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:24:36Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "227.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "234.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:24:36 handling incoming CALL [1162703637, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:36 sent CALL RESULT [1162703637] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:36 sent JSON message to Garage: [3,"1162703637",{}]
[ocpp  ] TRACE 2024/10/23 15:24:46 enqueued CALL [603218994, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:46 dispatched request 603218994 for Garage
[ocpp  ] TRACE 2024/10/23 15:24:46 sent JSON message to Garage: [2,"603218994","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:24:46 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:24:46 received JSON message from Garage: [3,"603218994",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:24:46 handling incoming CALL RESULT [603218994] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:46 completed request 603218994 for Garage
[ocpp  ] TRACE 2024/10/23 15:24:46 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:24:46 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:24:46 received JSON message from Garage: [2,"929003620","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:24:46Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "227.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "233.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:24:46 handling incoming CALL [929003620, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:46 sent CALL RESULT [929003620] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:46 sent JSON message to Garage: [3,"929003620",{}]
[ocpp  ] TRACE 2024/10/23 15:24:51 received JSON message from Garage: [2,"351625415","Heartbeat",{}]
[ocpp  ] TRACE 2024/10/23 15:24:51 handling incoming CALL [351625415, Heartbeat] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:51 sent CALL RESULT [351625415] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:51 sent JSON message to Garage: [3,"351625415",{"currentTime":"2024-10-23T13:24:51Z"}]
[ocpp  ] TRACE 2024/10/23 15:24:56 enqueued CALL [1505669717, TriggerMessage] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:56 dispatched request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:24:56 sent JSON message to Garage: [2,"1505669717","TriggerMessage",{"requestedMessage":"MeterValues","connectorId":1}]
[ocpp  ] TRACE 2024/10/23 15:24:56 started timeout timer for Garage
[ocpp  ] TRACE 2024/10/23 15:24:56 received JSON message from Garage: [3,"1505669717",{"status": "Accepted"}]
[ocpp  ] TRACE 2024/10/23 15:24:56 handling incoming CALL RESULT [1505669717] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:56 completed request<PHONE_NUMBER> for Garage
[ocpp  ] TRACE 2024/10/23 15:24:56 Garage ready to transmit again
[ocpp  ] TRACE 2024/10/23 15:24:56 timeout canceled for Garage
[ocpp  ] TRACE 2024/10/23 15:24:56 received JSON message from Garage: [2,"965163551","MeterValues",{"meterValue": [{"timestamp": "2024-10-23T13:24:56Z","sampledValue": [{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Energy.Active.Import.Register","unit": "Wh","value": "702201.2"},{"format": "Raw","location": "Outlet","context": "Trigger","measurand": "Power.Active.Import","unit": "W","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3","measurand": "Current.Import","unit": "A","value": "0.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L1-N","measurand": "Voltage","unit": "V","value": "227.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L2-N","measurand": "Voltage","unit": "V","value": "234.0"},{"format": "Raw","location": "Outlet","context": "Trigger","phase": "L3-N","measurand": "Voltage","unit": "V","value": "232.0"} ]} ],"connectorId": 1}]
[ocpp  ] TRACE 2024/10/23 15:24:56 handling incoming CALL [965163551, MeterValues] from Garage
[ocpp  ] TRACE 2024/10/23 15:24:56 sent CALL RESULT [965163551] for Garage
[ocpp  ] TRACE 2024/10/23 15:24:56 sent JSON message to Garage: [3,"965163551",{}]

@typxxi can you please immediately stop spamming this issue?

/cc @ivoks this is caused by https://github.com/evcc-io/evcc/pull/16675 not taking 1p inverters into account.

Ich konnte damit mich problemlos einloggen….

@softservicegit unbedingt Passwort ändern!!! In Zukunft am Besten
evcc discuss

benutzen.

/cc @ivoks this is caused by #16675 not taking 1p inverters into account.

Indeed. Hm, sorry for the trouble @softservicegit. I'll see if I can come up with a better approach.


Fixed #26067 -- Allowed ordering with StringAgg and ArrayAgg.

Added OrderableAgg base class for aggregates that allow for ordering input before aggregation,
such as Postgres' string_agg() and array_agg().
An 'ordering' element is added to the 'extra' parameter. It is parsed and resolved in
OrderableAggs 'resolve_expression'.
The actual 'ORDER BY' clause is formed in OrderableAggs 'as_sql' to ensure this parameter contains
well-formed SQL.
Add ordering to StringAgg and ArrayAgg
By inheriting from the novel OrderableAgg, these aggregations now allow ordering inputs prior to
aggregation.

buildbot, add to whitelist.

I'd like to see some tests where the ordering parameter isn't explicitly ordered. Something like:
values = AggregateTestModel.objects.aggregate(
    stringagg=StringAgg('char_field', delimiter=';', ordering=F('char_field'))
)

# and
values = AggregateTestModel.objects.aggregate(
    stringagg=StringAgg('char_field', delimiter=';', ordering='char_field')
)

I'm fairly sure this will fail. If you want ordering to be consistent with the order_by queryset method then you'll need to call asc() if you're not already working with an OrderBy expression. See django.db.models.sql.compiler.get_order_by().
You're also missing support for sorting by multiple fields. Is that allowed with orderable aggregates? Rather than accepting a single expression you may need to accept a list of them.
What are your thoughts on supporting string based fields with prepended ordering? Like:
values = AggregateTestModel.objects.aggregate(
    stringagg=StringAgg('char_field', delimiter=';', ordering='-char_field')
)

I don't have a strong opinion on this but it's worth discussing as some may care about the inconsistency (I don't for this use case).
Looks mostly good to me though, nice work.

Add a mention in the 1.11 release notes.

Closing due to inactivity. Please send a new PR if you return to it.

Thanks for the constructive feedback.
A new PR which addresses all these comments can be found here: https://github.com/django/django/pull/7604


Products in Carousel Collection are not fetching with the real name as in the Shopify Collections.

See this is the name of carousel items as mention in the vercel integration guide. And I was trying to fetch the products with "hidden-homepage-carousel" as mentioned in the repository. But this error was occuring "No collection found for hidden-homepage-carousel".
So in order to find the solution, I click on the view button as shown below:

This was navigating to this url:

Which means that the collection was creating with the name of "frontpage" instead of  "hidden-homepage-carousel". Then I fetch the products with "frontpage" and it worked.
So can anyone tell why this is happening? @wentsul @leerob

Probably the url slug is created when u first create the collection. After it's created and renames it does not update.

Same happening to me..
this is what works const products = await getCollectionProducts({ collection: 'frontpage' });

^ Thank you for sharing back that solution @rolandin!


The new WSA (Android 12.1) does not work anymore with the kernel file for the SU access

The old kernek file is not compatible wth android 12.1. While adb shell su access works, launcing any app results in the entire WSA crahsing

There's a separate github for the kernel, maybe you should open the issue there instead:
https://github.com/WSA-Community/WSA-Linux-Kernel


Revert "[SPARK-33861][SQL] Simplify conditional in predicate"

This reverts commit 32d4a2b and 3aa4e11.

Merged to master, branch-3.3 and branch-3.2

Thank you for reverting, @wangyum .

Sorry, but I missed that this is an ancient patch. To @wangyum , we need a new JIRA when we revert already released patches.

OK. https://issues.apache.org/jira/browse/SPARK-40493

Thank you, @wangyum .


task app notification fade

the task notifications should fade away after a few minutes. i think i'd also like to hide the buttons until the notification is mouse over or touched.

 tasks


Can not query historical data older then 2021-06-16 from object storage

Thanos, Prometheus and Golang version used:
thanos                      0.23.1
prometheus                   2.31.1
Object Storage Provider:
NetApp StorageGRID
What happened:
We have data there back from  2020-12-08, data looks fine, no visible issues, all blocks are consistent, no interruption, no overlapping. When we do a query, by some magic it returns only data from 2021-06-16 until now. Even it is in the middle of the block
| 01FN3PQAF98TWEVDA0P36CSCY5 | 10-06-2021 00:00:00 | 24-06-2021 00:00:00 | 335h59m59.995s | -95h59m59.995s  | 1,245,662  | 2,077,706,618   | 18,501,647    | 5          | false       | monitor=production,pod=dz1                               | 5m0s       | compactor      |
| 01FNHRV9N9C9GD6VKBFKHKW6N3 | 10-06-2021 00:00:00 | 24-06-2021 00:00:00 | 335h59m59.995s | -               | 1,245,662  | 173,837,766     | 2,086,962     | 5          | false       | monitor=production,pod=dz1                               | 1h0m0s     | compactor      |

debug log in both querier and store components does not show any reasons why it happens
We  run store and  querier on the same machine
 /usr/bin/thanos store --data-dir /var/lib/thanos/store --objstore.config-file /etc/prometheus/s3notk8s.yml --http-address <IP_ADDRESS>:10909 --grpc-address <IP_ADDRESS>:10901 --index-cache-size=20480MB --chunk-pool-size=81920MB --consistency-delay=12h --log.level=debug

/usr/bin/thanos query --http-address <IP_ADDRESS>:9090 --grpc-address <IP_ADDRESS>:19191 --store.sd-files=/etc/prometheus/stores.yml  --log.level=debug

What you expected to happen:
We would like to have a possibility to query all data from object storage or get a reason why  it is not  displaying.
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:
Dec 08 09:13:05 thanos thanos[29661]: level=debug ts=2021-12-08T09:13:05.101231898Z caller=proxy.go:681 msg="Store Addr: thanos.datastore.com:10903 LabelSets: {monitor=\"production\", pod=\"dz1\"}Mint:<PHONE_NUMBER>574 Maxt:<PHONE_NUMBER>000 queried"

Dec 08 09:13:06 thanos thanos[29661]: level=debug ts=2021-12-08T09:13:06.68366015Z caller=proxy.go:281 component=proxy request="min_time:1623760560000 max_time:1623847260000 matchers:<name:\"group\" value:\"misclxchosts\" > matchers:<name:\"instance\" value:\"lxchost2d9.env.dz1.com:9100\" > matchers:<name:\"job\" value:\"node\" > matchers:<name:\"monitor\" value:\"production\" > matchers:<name:\"node\" value:\"lxchost2d9.env.dz1.com\" > matchers:<name:\"pod\" value:\"dz1\" > matchers:<name:\"__name__\" value:\"up\" > max_resolution_window:300000 aggregates:COUNT aggregates:SUM partial_response_disabled:true " msg="Series: started fanout streams" status="Store Addr: thanos.datastore.com:10903 LabelSets: {monitor=\"production\", pod=\"dz1\"}Mint:<PHONE_NUMBER>574 Maxt:<PHONE_NUMBER>000 queried"

Dec 08 09:13:06 thanos thanos[30405]: level=debug ts=2021-12-08T09:13:06.698734975Z caller=bucket.go:1087 msg="stats query processed" stats="&{blocksQueried:1 postingsTouched:5 postingsTouchedSizeSum:21004 postingsToFetch:0 postingsFetched:0 postingsFetchedSizeSum:0 postingsFetchCount:0 postingsFetchDurationSum:0 cachedPostingsCompressions:0 cachedPostingsCompressionErrors:0 cachedPostingsOriginalSizeSum:0 cachedPostingsCompressedSizeSum:0 cachedPostingsCompressionTimeSum:0 cachedPostingsDecompressions:5 cachedPostingsDecompressionErrors:0 cachedPostingsDecompressionTimeSum:436478 seriesTouched:1 seriesTouchedSizeSum:209 seriesFetched:0 seriesFetchedSizeSum:0 seriesFetchCount:0 seriesFetchDurationSum:0 chunksTouched:2 chunksTouchedSizeSum:532 chunksFetched:2 chunksFetchedSizeSum:16273 chunksFetchCount:1 chunksFetchDurationSum:5511961 getAllDuration:13949624 mergedSeriesCount:1 mergedChunksCount:2 mergeDuration:44314}" err=null

Environment:

OS (e.g. from /etc/os-release):
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
Kernel (e.g. uname -a):
5.4.0-80-generic

Could you perhaps check in the Query Component UI of what stores it has? Mainly the focus would be on the relevant label sets and their announced time frames.

Yes, of course. I expect to have this data at least as deep as 10-06-2021 (because of blocks start time ) from NetApp StorageGrid obj storage, it is kind of s3 obj storage. I can not find any changes in the time frame where metrics stop being viewed  (16-06-2021) i.e. between  10-06-2021 - 24-06-2021. In thanos Query Component UI labels of obj store looks like
Endpoint: thanos.datastore.one.com:10903

Announced LabelSets :
...
"monitor="production" pod="dz1"
"monitor="production" pod="dz1" replica="prometheus1
"monitor="production" pod="dz1" replica="prometheus2"
...

Min Time
2020-10-01 00:00:00
Max Time
2021-12-20 04:00:00 | 3.746s ago

Last Successful Health Check
3.746s ago

The /etc/prometheus/s3.yml which is used as a config for obj store access, does not have any fancy options from what I can see
type: S3
config:
  bucket: "ocsysinfra-prometheus-metrics"
  endpoint: "s3.datastore.com"
  region: "SOME"
  access_key: "SOME"
  insecure: false
  signature_version2:  false
  secret_key: "SOME"
  put_user_metadata: {}
  http_config:
    idle_conn_timeout: "10m"
    response_header_timeout: "15m"
    insecure_skip_verify: true
  trace:
    enable: false
  part_size: 134217728

Not sure what settings more I can provide with.
Also if the config is broken/wrong  would it be  possible to see it in log messages when log level is set to debug?

Well, you could checkout the https://thanos.io/tip/components/tools.md/ - web for example.
Also it could be a config thing, as a StoreAPI could announce a certain date for which it will (not can) return data. Especially when chaining components, perhaps this was an issue. Please do check it out with the thanos tool, perhaps it gives more info :)

Hmmm… but i can read all blocks with thanos tool inspect… What exactly I
can expect from thanos tool web, is it not the same I posted above on image
attached?
man. 20. dec. 2021 kl. 21.17 skrev Wiard van Rij @.***>:

Well, you could checkout the https://thanos.io/tip/components/tools.md/ -
web for example.
Also it could be a config thing, as a StoreAPI could announce a certain
date for which it will (not can) return data. Especially when
chaining components, perhaps this was an issue. Please do check it out with
the thanos tool, perhaps it gives more info :)
—
Reply to this email directly, view it on GitHub
https://github.com/thanos-io/thanos/issues/4930#issuecomment-998239976,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJERUHY4Q2FXMQOBSAB3DVDUR6FOXANCNFSM5JTMDPAA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
 Ignore mine :)

So, this is what I did, I downloaded some block 01FN3PQAF98TWEVDA0P36CSCY5 from obj storage to my local disk into data folder, then run
./promtool  tsdb dump
Shows me nothing. Then I tried
./promtool  tsdb list BLOCK ULID                  MIN TIME       MAX TIME       DURATION        NUM SAMPLES  NUM CHUNKS   NUM SERIES   SIZE 01FN3PQAF98TWEVDA0P36CSCY5<PHONE_NUMBER>005<PHONE_NUMBER>000  335h59m59.995s<PHONE_NUMBER>   18501647     1245662<PHONE_NUMBER>
Looks good! And
 ./promtool  tsdb  analyze data  01FN3PQAF98TWEVDA0P36CSCY5
Block ID: 01FN3PQAF98TWEVDA0P36CSCY5
Duration: 335h59m59.995s
Series: 1245662
Label names: 169
Postings (unique label pairs): 8301
Postings entries (total label pairs): 9325193
...

I can see all label features there like cardinality etc.  This is a bit closer but still no idea why I can not request metrics older then 16-06-2021... And why  ./promtool  tsdb dump output  nothing... Is there any way to make it more verbose?

Hi @bobykus31 I am facing the same problem. Did you find out what was causing the issue?

No,
I dropped data since it was a year old.
ср, 13 лип. 2022 р. о 10:27 Vipul Jindal @.***> пише:

Hi @bobykus31 https://github.com/bobykus31 I am facing the same
problem. Did you find out what was causing the issue?
—
Reply to this email directly, view it on GitHub
https://github.com/thanos-io/thanos/issues/4930#issuecomment-1182924710,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJERUH3KYIXR3IANHB5WFZ3VTZ4XPANCNFSM5JTMDPAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Ihor Piddubnyak,
RHCE<PHONE_NUMBER>39408

Hi @vipul0805 @bobykus31, today we find out the reason  why.  Prometheus will create database in the  start command execute dir,  if you start your prometheus at different dir, prometheus will create a new database in the different dir.  --storage.tsdb.path can resolve this problem.  Hope useful!


signed apk crashes immediately

I have created signed apk it gets created without any error also installed without error but when i open, it crashes...
android studio -3.0.1
java - 1.8.0_60
package.json
  "name": "forapk",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "react": "16.3.1",
    "react-native": "0.55.4"
  },
  "devDependencies": {
    "babel-jest": "22.4.4",
    "babel-preset-react-native": "4.0.0",
    "jest": "22.4.4",
    "react-test-renderer": "16.3.1"
  },
  "jest": {
    "preset": "react-native"
  }
}

build.gradle

apply plugin: "com.android.application"

import com.android.build.OutputFile
project.ext.react = [
    entryFile: "index.js"
]

apply from: "../../node_modules/react-native/react.gradle"

def enableSeparateBuildPerCPUArchitecture = false

def enableProguardInReleaseBuilds = false

android {
    compileSdkVersion 26
    defaultConfig {
        applicationId "com.forapk"
        minSdkVersion 16
        targetSdkVersion 22
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86"
        }
    }
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a": 1, "x86": 2]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
    buildToolsVersion '26.0.2'
}

dependencies {
    compile fileTree(include: ['*.jar'], dir: 'libs')
    compile 'com.android.support:appcompat-v7:26.0.1'
    compile 'com.facebook.react:react-native:+'
    // From node_modules
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

step -1 Create Key-Store value from Build -> generate Signed APK...
step- 2 place that keystore.jks file under android/app directory
step -3 Edit the file ~/.gradle/gradle.properties or android/gradle.properties and add the following (replace
***** with the correct keystore password, alias and key password)
          MYAPP_RELEASE_STORE_FILE= keystore.jks
          MYAPP_RELEASE_KEY_ALIAS=myKeyAlias
          MYAPP_RELEASE_STORE_PASSWORD=123456
          MYAPP_RELEASE_KEY_PASSWORD=123456

step-4 Edit the file android/app/build.gradle in your project folder and add the signing config,
----
android {
    ---
    defaultConfig { ... }
    signingConfigs {
        release {
            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
                storeFile file(MYAPP_RELEASE_STORE_FILE)
                storePassword MYAPP_RELEASE_STORE_PASSWORD
                keyAlias MYAPP_RELEASE_KEY_ALIAS
                keyPassword MYAPP_RELEASE_KEY_PASSWORD
            }
        }
    }
    buildTypes {
        release {
            -----
            signingConfig signingConfigs.release
        }
    }
}
---

step -5 goto terminal  1) cd android 2) ./gradlew assembleRelease

hi, I am also facing the same issue. Does anybody has a solution?

Same issue for me , i did everything same as mentioned but app is crashing on launch ,

+1

i am facing this issue when i generate apk with meteor as backend but when i generate apk without meteor and removing all traces of meteor from react native it worked

I did this after some unexpected flow.  I created unsigned apk from react and then convert it to signed apk from my old ionic project ,use that keystore and all thing then it worked , Such an unexpected flow ,

Same, anyone found a working solution ?

Answering my own question. For me It turned out that I had to high gradle version.
Once i reverted/dwongraded to :
buld.gradle:
   from    classpath 'com.android.tools.build:gradle:3.2.0'
    to        classpath 'com.android.tools.build:gradle:3.1.4'

gradle-wrapper.properties
from distributionUrl=https\://services.gradle.org/distributions/gradle-4.6-all.zip
to     distributionUrl=https\://services.gradle.org/distributions/gradle-4.4-all.zip

all works for me again.
Hope it helps.

will try this

Same issue for me, i am trying on a huawei device.
When in debugging mode, the app works fine.
I generated the release apk.
First i tried without signing it, it failed at installing the app and output "App Not Installed"
Using jdk keytool, i followed the docs step by step, generated the signed version and installed it.
it was installed this time, but when opening, it shows blank page for 1 second and then closes without crashing.
Weird

Same issue here, release build of my app crashes on start after upgrading to com.android.tools.build:gradle:3.2.0 and gradle 4.6. Debug build works fine.

Following link worked for me https://github.com/adamivancza/react-navigation/commit/db8be7cc0b4ac738242ce82bcc2d1f3254a028c0  . Try this.


Help parsing refactor

Refactors help logic to separate rendering from gathering data.
Also fixes a bug where bubbling up the help_print would fail if the help_flags differ across the app stack.

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

:exclamation: No coverage uploaded for pull request base (develop-v2@cc780f0). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##             develop-v2      #57   +/-   ##
=============================================
  Coverage              ?   93.17%
=============================================
  Files                 ?       15
  Lines                 ?     1510
  Branches              ?      382
=============================================
  Hits                  ?     1407
  Misses                ?       56
  Partials              ?       47

Flag
Coverage Δ

unittests
93.17% <0.00%> (?)

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

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


Add Identity with JWT Tokens

TODO List to complete 4.5.1

[ ] Login Endpoint
[ ] ChangePassword Endpoint
[ ] Internal API for Managing Roles and Claims

Optional

[ ] Generate, Store, and Handle Refresh tokens
[ ] Logout Endpoint


Add priority selection strategy for transcription projects

Transcription projects will want to flow in order from a starting point to a finishing point, e.g. page 1, 2, 3....End. We need to add the functionality to build the selection queue in order from the priority field here.
Also the Tate transcription project we'll also need to support grouped and prioritized as individual volumes will be a subject set.

cc @VVH

For reference, we need to implement grouped and prioritized here.

Wellcome is going to need this too. The health reports are volumes that can be grouped by London borough or year.

Just noting we'll need this for beta launch for tate project by the 10th August.


How to import types or records from imported interfaces?

a.wit
package foo:a

interface foo {
   record bar {
      baz: string
   }
}

b.wit
Does not work with componentize.
package foo:b

world b {
   use foo:a/foo.{bar}

   export test: func() -> bar
}

Does not work with componentize.
package foo:b

world b {
   import foo:a/foo.{bar}

   export test: func() -> bar
}

Would work with componentize but then the type will not be recognized in wit
package foo:b

world b {
   import foo:a/foo

   export test: func() -> bar
}

On the js side I'd like to use it as
import { bar } from "foo:a/foo"

If bar was a func then I can use it as above.
I couldn't yet find a way to import types from interfaces.
Basically the ideal form for me would be,
package foo:b

world b {
   use foo:a/foo.{bar}

   export test: func() -> bar
}

which works with no issues when writing the component in Rust with wit-bindgen.
I'd be grateful if you could point me to the right direction. 🙏

Thanks for posting, agreed we should support these cases, marking as a bug, and I'll aim to pick it up soon.

I've landed the fix for this in https://github.com/bytecodealliance/componentize-js/commit/5e68ce33f2fe5f6056ce00a20757fee6159acdff, going out in the next release later today or tomorrow. But if there's anything I've missed please do post back. Thanks for the issue!

Great to hear!
I'll give it a try in the upcoming days.
Thank, you.


getting-started tells you to go follow the tutorial too early

Unclear at “The code for your app is in my_app/lib/main.dart. To learn more about how to build apps with Flutter, please see the tutorial.” Which path I should take.  Should I go to the tutorial now?
I suspect we should save this until after iOS or Android setup.  Perhaps we should hide iOS or Android (or both) under some sort of disclosure view to make the getting-started feel less long?

Will be addressed by https://docs.google.com/document/d/1wL_7BvpExxyvLqtf5am3_iMQThWBZ0Ak1uPVFiI3KN8/edit?usp=sharing

Fixed in flutter/website#178, based on doc shared by<EMAIL_ADDRESS>

Marking as closed.


Erroneously fingerprinting file references

We discovered an issue where strings matching app.js within js content would be fingerprinted, even though they weren't referring to the actual app.js generated by ember cli. Case in point:
Our code makes a request to look for a public file on GitHub. In one of our js files is a string containing a URL like this:
https://api.github.com/repos/{{repo stuff etc}}/contents/app.json?ref=master
After the broccoli build the string is transformed into this:
https://api.github.com/repos/{{repo stuff etc}}/contents/app-{{big-ol-fingerprint}}.json?ref=master
It appears as though it is finding it because it matches app.js, even though that is a subset of the actual string.

This is a pretty difficult problem to solve due to the nature of the regex used to fingerprint and replace all the asset paths.
Could you try using the ignore option? Are there other paths in that file that need to be re-written? You can see the ignore option here: https://github.com/rickharrison/broccoli-asset-rewrite

We tried using the ignore option, but that tells it not to fingerprint app.js at all. We do want it fingerprinted, we just don't want it to alter URLs of other files. I realize this is an extremely difficult thing to address as there is no reliable terminator for asset paths.

Are you sure you used ignore and not exclude ?

You are correct. We used exclude when we tried it earlier. From the docs (and code) in ember-cli, it looks like ignore isn't passed down through ember-cli's fingerprint options. Is there another way we can set it?

Can you try setting ignore and see if it works? I haven't worked with ember-cli in quite some time so I'm not that familiar with the current state of their build process.

ignore didn't work because it is not passed through by this library to broccoli-asset-rewrite.  I'm not sure that it would have helped us if it were passed through, though.  In the end we renamed our app.js build generated by ember-cli to something else so that broccoli-asset-rev wouldn't try to fingerprint instances of app.js in our code.

Thanks for that catch. I will try and get an update out to fix that issue soon.

This is fixed in 2.0.6. Please let me know if everything works for you.


🎉🎊🍾 [New Feature] (code + test) Add new module runner for handling anything about command line running.

Target

Add new module runner for handling anything about command line running.

Modify Code Scope

Source Code

module runner

Testing Code

Integration Test

test module runner
test module run_cmd

Effecting Scope

Add new module for handling PyMock-API command line running.

Description

Major Changes:

Add new module for handling command line running and providing an entry point of PyMock-API command line.
Add integration test for the new module.

Others:

Adjust the decorator implementation of testing with configuration file.
Adjust the pre-process of tests of module server.__init__.

Even through the test coverage decreases. (0.18%) but the level could be accepted (<<<= 3%) so ignore the checks are fail.


Low resolution on PV stream

Hello everyone,
I am trying out this library and found that the PV camera images are only 760x428 pixels. Is there a reason for this? The camera should have much higher resolution, so I do not understand why it does not save this. I am recording long throw, eye tracking, and PV.
Additionally, the PV stream gets saved in raw format, which takes up a lot of space. I want to record +- 15 minute videos, which currently would result in approximately 35GB of data (and probably a crashing app). Is it possible to adjust the code to save directly in .png, which would save around a factor 5 in file size?
Thanks in advance for your answers.

PV camera can work in the following profiles: https://learn.microsoft.com/en-us/windows/mixed-reality/develop/advanced-concepts/locatable-camera-overview.
StreamRecorder by default uses a profile that captures images in 760x428 resolution. You can change this setting a different value of kImageWidth (VideoFrameProcessor.cpp, 23rd line): https://github.com/microsoft/HoloLens2ForCV/blob/main/Samples/StreamRecorder/StreamRecorderApp/VideoFrameProcessor.cpp


No error, no output

Hi,
As of today's test, with the sample on npm.js.com the code is running without error, but no PDFs are generated.
Thanks,

Hi @Atheryl,
I just checked it, it is working fine. Can you please let me know if you are following the documentation?
Thank you

It was entirely my fault. I had a await that wasn't working apparently and the function was exiting before the PDF were written. Apologies.


S finder bar not properly removed on S7

On S7 and probably S6 and Note5 as well, although the sfinder itself in qs panel is gone, there's still some space left between the clock/date and qs icons.
Maybe it's because the marginTop value in layout/qs_panel_sfinder.xml is hardcoded, not referenced from dimens.xml.
Could you adjust the layout for these old devices please?

Thanks for the tip, I'll try to see if that works to fix it.

That marginTop would probably be realted to the SFinder itself, because of the layout it's stored in.

@mmihov05 That makes sense, but I don't quite see other possibilities compared with S8's SystemUI. Hope @ohayoubaka finds a fix soon ;)

Yeah me too I have this "issue" on my S7 too


subchannel socket events lost (causing 5sec latency) and only picked up by the timer-based backup poller.

When a client attempts to connect to a server while the server is down it causes an issue further down on that channel such that sub-channel socket event handling (when the server becomes available later) are not handled properly through the gRPC polling logic.  The events are then only picked-up by the timer based backup poller. The default polling period for the backup poller is set to 5000ms which leads to socket events being handled with an average of 5000ms latency. This in turn causes TLS handshake on the remote end to timeout early without completion. Effectively preventing the client from ever successfully completing the TLS handshake.
The same issue has been referenced by others online:
https://groups.google.com/g/grpc-io/c/_gdhX9aP7GE/m/E0tRoUPcDwAJ
https://groups.google.com/g/grpc-io/c/O231FCK4TVk
What version of gRPC and what language are you using?
This has been consistently seen on v1.39, v1.41.1 and v1.43.2
What operating system (Linux, Windows,...) and version?
Ubuntu 20.04
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc 9.3.0
What did you do?

use ChannelInterface::GetState(true) on the client channel to trigger the connection state machine before the server is available to accept connections.
Start the server and let is accept connections
Observe that the connection establishment state machine attempts to connect but the client->server interactions are internally delayed within the client-side logic to the period of 5sec each time. This is the result of the socket events only being picked up by the backup poller (that runs  once every 5sec)

What did you expect to see?
I expect to see subchannel socket events handled through the normal pollers logic (leading to minimal latency) rather than being only picked-up by the backup poller.
What did you see instead?
socket events are handled by the timer based backup poller
Anything else we should know about your project / environment?

Hi Mark,
In our application we use asynchronous APIs on this channel and therefore have a dedicated thread waiting for events through calling CompletionQueue::Next() at all times. I think this issue is still a bug, please reopen.

On Feb 14, 2022, at 8:51 AM, Mark D. Roth @.***> wrote:
This is expected behavior in our current polling model, which we're in the process of moving away from. The current model expects applications to explicitly dedicate threads to polling by calling CompletionQueue::Next() in at least one thread at all times. However, we know that this doesn't really make sense in applications using the C++ synchronous API, where the application will not otherwise be using completion queues. The backup poller was added as an interim solution to avoid completely missing polling events without severely affecting performance of applications that do properly dedicate polling threads (typically those using the C++ CQ-based async API), but we know it's not perfect. In particular, it is still possible (although much less likely) that the next RPC sent on the channel after a disconnect will still fail if the backup poller has not yet had a chance to process the disconnect from the server, although that problem should be further ameliorated by the introduction of transparent retry support (I just merged #28548 https://github.com/grpc/grpc/pull/28548 moments ago with that change).
For the long-term solution, we are working to migrate from the current polling model to a new model where all of the polling logic is handled by a pluggable EventEngine implementation, which provides its own polling thread(s), so that the application does not need to do so. See grpc/proposal#245 https://github.com/grpc/proposal/pull/245 for details.
—
Reply to this email directly, view it on GitHub https://github.com/grpc/grpc/issues/28866#issuecomment-1039315199, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXFC7BPR4N3IFEJRJDRDK63U3EXHXANCNFSM5OF5EXPA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

In the reproduction steps you indicated, you are not doing anything to tie the channel's fds into the CQs that you are polling.  You can do that by either (a) starting a call on the channel that is tied to one of the CQs you are polling or (b) calling channel->NotifyOnStateChange() to add an event on the CQ to notify you when the channel's state changes.

Adding NotifyOnStateChange() as you described below in option (b) seems to solve the problem however it brings with out the other issues as discussed in issue 21948 https://github.com/grpc/grpc/issues/21948 and 3064 https://github.com/grpc/grpc/issues/3064.

On Feb 14, 2022, at 12:05 PM, Mark D. Roth @.***> wrote:
In the reproduction steps you indicated, you are not doing anything to tie the channel's fds into the CQs that you are polling. You can do that by either (a) starting a call on the channel that is tied to one of the CQs you are polling or (b) calling channel->NotifyOnStateChange() to add an event on the CQ to notify you when the channel's state changes.
—
Reply to this email directly, view it on GitHub https://github.com/grpc/grpc/issues/28866#issuecomment-1039502524, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXFC7BPUF72AS36Y2J4KUB3U3FOCPANCNFSM5OF5EXPA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.


Update login ui

I can update the login ui and make it modern and better...

somewhat like this...
make sure to add the labels....
thanks...

hey @NK-Works any update ?

@ANSHIKA-26 working on it... will ask for a pull req it within 30 min to an hour max...


Exceptions when using cycli with no authorization required

Hi,
I initially filed an issue with py2neo:
https://github.com/technige/py2neo/issues/621
and technige said the issue looks to actually be within cycli.  As stated, I was using Neo4j 3.1.1 and have the latest version of cycli off of pypi.
I have not updated Neo4j to 3.2 as there was some issue with updating the data in my database, haven't gotten around to seeing if they've fixed that yet. I forget the details, I got some vague sense that Neo4j had some issues around authorization at the time. But I haven't needed to revisit that project yet.

Yeah I have unfortunately not tested cycli with Neo4j 3.1.1! I imagine I'll just have to update py2neo or something. I will take a look soon.


feat: add results.json and ResultPage.js

Please feel free to let me know if there is anything to change!! ^^!!

Please change the code in English~. This is very good!

Okay! I will edit it in English! Thank you for letting me know~

I modified it to English. Please check it out!

I modified it to English. Please check it out!

I got it. :)


[PowerToys Run] Remember results order after updating

Description of the new feature / enhancement
PowerToys is my primary way to open applications, and I have been using it for years now.
I really enjoy the latest update to it, and I think the visual looks much better.
I use the option Results order tuning because there are only a handful of applications I open, I like to press one key and like that my desired application is top most (after PT Run has learned).
Unfortunately, after every update the learned results are reset, and PT Run takes some time to learn again. Is there a way to back up the results order somehow?
Scenario when this would be used?
 Since PT Run, has learned that behavior of mine.
However, after updating even a patch version of the PT, my ordered results are gone, Now on pressing S I get Steam.
Supporting information
No response

/dup #29621


Code style checking: checkpatch and clang-format clash on BPF files

On bpf source files our checkpatch and clang-format tool clash on some trivial style violations:

clang-format will format the open brace on type declaration on next lines, example:

  enum msg_cgroup_ops {
  ...

  to

  enum msg_cgroup_ops
  {

While checkpatch will report:

  Error: ERROR:OPEN_BRACE: open brace '{' following enum go on the same line
  #41: FILE: bpf/lib/msg_types.h:36:
  +enum msg_cgroup_ops
  +{

I tend to prefer checkpatch style, but clang people may know better... so no preference , since we want the clang-format part of the build and it auto fixes files, maybe we relax checkpatch?

Seems related to b31cb1c262b071b777ad406aacf060876039b087

This seems that is already addressed by https://github.com/cilium/tetragon/commit/b31cb1c262b071b777ad406aacf060876039b087, closing.


Stamen not available as a valid provider

Perhaps I'm doing something wrong, but I have not been able to get a Stamen map to work as shown throughout the docs.
Stamen does not appear as a listed option when I run contextily.providers.
I did some digging into xyzservices and, from what I can tell, the Stamen maps are now listed under the Stadia provider. However, calling Stadia.StamenToner (for example) results in blank tiles showing an error has occurred.

I found an explanation here:  https://github.com/leaflet-extras/leaflet-providers?tab=readme-ov-file#stamen-design
It's probably a good idea to make this known in the documentation and update examples that show code which will no longer work.

Thanks for the heads up. We have actually already fixed all of this a while ago and removed Stamen from docs but I just now realised, that our docs are not rendering currently so the changes never made it to the documentation website. Will fix that.


Fixed the GitHub banner link

Unfortunately, plain src="banner.jpg" link leads to the https://github.com/jumpsuit/jumpsuit/blob/master/banner.png GitHub preview page, which is an HTML page, not a raw image.
This should fix the Readme rendering.

Thanks @kirushik!


Not working with next/babel preset

Bug Report
Looks like there is some kind of configs collision with next/babel (Next.js preset) preset. When it's enabled, Whoops, we crashed error is shown.
To Reproduce
mkdir next-docz-test
cd next-docz-test
yarn init -y
yarn add -E<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>echo '{"presets": ["next/babel"]}' > .babelrc
echo '---\nname: Index\nroute: \/\norder: 1\n---\n# Hello' > index.mdx
yarn docz dev
open http://localhost:3000

Stacktrace
Element type is invalid: expected a string (for built-in components)
or a class/function (for composite components) but got: undefined.
You likely forgot to export your component from the file it's defined in,
or you might have mixed up default and named imports.
Check the render method of Component.

in Component (created by n)
in n (created by t)
in div (created by Container)
in Container
in div (created by Wrapper)
in Wrapper
in div (created by Wrapper)
in Wrapper (created by Main)
in Main
in ThemeConfig (created by Page)
in Page (created by t)
in t
in t
in p (created by DocPreview)
in DocPreview
in c
in ThemeProvider
in ThemeConfig (created by Theme)
in Theme (created by DoczTheme)
in DefaultWrapper (created by DoczTheme)
in t (created by t)
in t (created by DoczTheme)
in ErrorBoundary (created by DoczTheme)
in DoczTheme (at root.jsx:30)
in Root (created by HotExportedRoot)
in AppContainer (created by HotExportedRoot)
in HotExportedRoot (at index.jsx:16)

Enviroment

Docz: 0.7.1
Next: 6.1.1
React 16.4.1
OS: OSX 10.13.4
Node / npm / yarn: 8.9.4 / 5.6.0 / 1.6.0

Same Problem trying to implement docz with Nextjs - same versions

I found a solution based on #20.
For this case using next.js I created a empty babel.json file, docz assume as babel default configuration and insert babel-preset-react-app.
babel.json:
{
  "presets": [],
  "plugins": []
}

That works for me @RafalFilipek

I'm using "docz": "^0.10.3"and the same problem was solved using the @jhta babel.json empty file.
I think this bug still going on.

Actually, i've just finished some further tests. I was using several babel 6 packages. I know that exists a plugin to enable docz run in babel 6 but i wasn't using it and that's why i was getting this error.
So, the case is:
If you're using Babel 6 and didn't configured the plugins correctly, you may fix your project just creating this babel.json file.
I'm my case i've just updated my packages project to babel 7 and removed this file and everything it's running smooth.
I think that everyone with these errors is related with babel 6 without correct configuration.


[BI-695]  ISSUE: Multiple clicks on Save results in equally multiple entities created for Programs and Locations

NewDataForm has been updated to automatically disable the "Save" button once it's been clicked to prevent double clicking.  The button will also show a loading indicator, to indicate that something is happening.
I also refactored the structure of the "views" folder a little bit to group views together based on their function.
Lastly, I added a "config" node in package.json and moved custom variables used for building and startup as I was having issues getting bi-web to start up.  This has no external affect on running any of the npm scripts for bi-web.

Realized that I missed handling edits after Nick had done a review.  Most recent commit accounts for both new data forms and edit forms.    Each parent component was updated to now have an instance of DataFormEventBusHandler, and the parent is responsible for signaling when the save activity is complete.

Realized that I missed handling edits after Nick had done a review.  Most recent commit accounts for both new data forms and edit forms.    Each parent component was updated to now have an instance of DataFormEventBusHandler, and the parent is responsible for signaling when the save activity is complete.


Add DynamicJson type

Adds an initial implementation, unit tests and perf tests.
The implementation is known to be terrible but I'd like to get something out and start getting feedback.

I'll address issues in a follow up PR.


Fix can not cancel from rotate encryption keys dialog

Fixes #6123
Simple fix - the close method is wired into the cancel button - it has logic to call the buttonDone function - but in the case of the cancel button, the argument that gets passed to the close method is the click event object - the close method then tries to treat that as the buttonDone function.
Updated to check that buttonDone is a function before it is used.
To test:

Provision an RKE2 cluster
Go to the cluster management list and from the action menu for the cluster, choose 'Rotate Encryption Keys'
Verify that pressing the Cancel button in the dialog now closes it

@aalves08 that other case is fine - that's just calling buttonDone directly - it takes a Boolean.


💡[FEATURE]: Enhance Nifty Arima model.

New Features that I want to Add in "Nifty /Arima/modell.ipynb":

Model Evaluation Metrics: Calculate and printMAE, MSE, and RMSE.
Forecast Future Values: Add functionality to forecast future values beyond the test dataset.
Improve Visualizations: Enhance the plot to include titles and combined all relevant plots into a single visualization for better comparison.

Hi @Akshat111111 , I have raised this issue. Please assign it to me.


dcterms:language recommended vocab, update needed

dcterms:language is currently recommended to use RFC 4646 as controlled vocabulary. RFC 4646 has been deprecated, 5646 being the current one.
Recommendation should be updated to point to RFC 5646.
RFC 4646: https://tools.ietf.org/html/rfc4646
RFC 5646: https://tools.ietf.org/html/rfc5646

This seems sensible. As far as I can tell, from a superficial reading, this
will not make any difference to the majority of users.
Regards
Quentin
Dr. Quentin Groom
(Botany and Information Technology)
Botanic Garden Meise
Domein van Bouchout
B-1860 Meise
Belgium
ORCID: 0000-0002-0596-5376 http://orcid.org/0000-0002-0596-5376
Landline; +32 (0) 226 009 20 ext. 364
FAX:      +32 (0) 226 009 45
E-mail<EMAIL_ADDRESS>Skype name: qgroom
Website:    www.botanicgarden.be
On 28 February 2017 at 00:40, Paula Zermoglio<EMAIL_ADDRESS>wrote:

dcterms:language http://rs.tdwg.org/dwc/terms/index.htm#dcterms:language
is currently recommended to use RFC 4646 as controlled vocabulary. RFC 4646
has been deprecated, 5646 being the current one.
Recommendation should be updated to point to RFC 5646.
RFC 4646: https://tools.ietf.org/html/rfc4646
RFC 5646: https://tools.ietf.org/html/rfc5646
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tdwg/dwc/issues/136, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFRj0F6YhJrsCE3B5k6_kd5EFUgEYUzqks5rg1DAgaJpZM4MNuVA
.

Makes sense!

Amended in 70d7a9f95a322d88bc66088f375f06e54613aab7.


[bugfix] make caching io closable

Why I'm doing:
Prevent resource leak in caching io
What I'm doing:
Adding closable method
Fixes #issue
https://github.com/StarRocks/starrocks/issues/47930
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

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

Is this error log centralized in the fe.log?


Non-functional vs nonfunctional (inconsistent across examples)

which one should it be? this is not consistent across examples and within examples.

Personally I prefer "nonfunctional" (lacking the hyphen).

I don't have a strong preference either way.  We should really wait for @smiths to weigh in though.

I don't have a strong opinion, but I would prefer non-functional requirements.  Based on a quick google search, it seems to be the more commonly employed form.  I like the idea that this term will now be consistent within and between documents!  I also assume that if we change our minds at a later point, switching to nonfunctional will be a trivial change.

ok, changed to "non-functional" this can be re-opened if we need to change back to nonfunctional.


AZCopy High Memory Usage - Uploading 2TB

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.27.2
Regression From
No response
Architecture
i86
Storage Explorer Build Number
20230123.2
Platform
Windows
OS Version
Windows 10 Build 19045
Bug Description
azcopy_windows_amd64.exe currently using 5.8GB of memory whilst uploading 2TB of data from a USB drive. It appears to use as much as possible and has been doing so for the last 12 hours. Mem usage currently at 95%.
Uploading data to a blob container.
Steps to Reproduce

Launch Storage Explorer
Upload Folder to Blob using Archive tier from USB 3.0 drive. Large amount of files as well as data, totalling 2TB.

Actual Experience
Program is running OK and uploading but anything else you want to do on the system is obviously very slow, ideally requires a dedicated system at the moment to upload.
Expected Experience
AzCopy should not be reserving that amount of memory especially as the external disk transfer speed is likely limited to no more than 50Mbps
Additional Context
No response

@unknowndpi , as you have seen, AzCopy is very good at using system resources. If you'd like to tone it down, there's a variety of settings in Storage Explorer you can use to do this.
Go to settings (gear on the left) > Transfers > AzCopy. Here you will find all of the AzCopy settings. Probably the easiest one to use is the Network Concurrency settings. Try changing it to adjust dynamically. Beyond that, you can play with any of the other settings to specifically reduce AzCopy's performance as you desire.

Transfers > Buffer Size would likely have been the option. Closing off as should have RTFM. Thanks.


Shader Error

Use the git version playcanvas.
Project:https://playcanvas.com/editor/scene/1530394

Thanks for raising this one @weilichuang!
Recent change broke this https://github.com/playcanvas/engine/pull/4636/files#diff-0b850a404fa1dc3f4ed648bac2c701107284d10aee6ef6c2b6dd1f144d7ba409R14
(as well as the diffuseDetail chunk).


BUG: Editor-options are not taking into consideration

Hello,
thank you for providing this widget.
It seems like the options-dict passed to the constructor of JSONEditorWidget are not passed on to the JavaScript file. Instead the editor-options are hardcoded in line 10 of json_widget.js.
Best regards

Hi @fmfeit , I'll take a look at improving this when I get a chance. Unfortunately I can't give you a timeline as I'm busy with other projects right now. That said, if you can make the change and submit a Pull Request I'll happily review and merge as appropriate.
Thanks for your feedback!

fixed in 8a9a66ac383386ec145717428e935662d061bace

Released 0.0.8


Bad Autocompletion on resource names after . or /

Bicep version
v0.4.1124
Describe the bug
When typing a resource name in auto completion, auto complete seems to forget everything you've typed so far if you get to a . or a /, which leads to some surprising completion results.
To Reproduce

Now type /w.  I'd now expect Microsoft.OperationalInsights/workspace to be the top result.  Instead you end up with completely unrelated results.  It seems as if auto completion is ignoring everything before the / and just searching on w

I have noticed this as well. If the text is inside of a string, it does not seem to happen.


Fix valueFrom bug in EnvVars

The code was setup to write any EnvVar provided in the Terraform Spec to the Runner SetEnv function, so if you set valueFrom it would still look for value and set that which would result in an empty string being set.
Tests added to verify that valueFrom is working with a Secret and a ConfigMap valueFrom setting.
Fixes #278

Thanks @chanwit I've made changes to handle the errors you pointed out.

LGTM thank you @Nalum


Implementation of features in WPS 2.0.0

 Issue by jachym
Wednesday Jun 18, 2014 at 20:25 GMT
Originally opened as https://github.com/PyWPS/pywps-4/issues/22

More advanced process control: PAUSE, RESUME, CANCEL

It would be better if this is split into several issues within the same milestone. From what we have learned so far is PAUSE and RESUME will not be easy to achieve with the Multiprocessing library.

agree with splitting