Support of Gosund SP1 v23

Is your feature request related to a problem? Please describe:
When having a Gosund SP1 outlet being autodiscovered it shows up as two devices in HB (and in HomeKit as one device with two switches) - the one the right side is connected to the actual switch:

This happened log-wise:
[10/1/2021, 10:41:23 PM] [Tasmota] Adding new accessory: Waschmaschine ENERGY TotalStartTime
[10/1/2021, 10:41:23 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Total
[10/1/2021, 10:41:23 PM] [Tasmota] Creating service: Waschmaschine ENERGY Total sensor
[10/1/2021, 10:41:23 PM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Total Consumption': Characteristic not in required or optional characteristic section for service . Adding anyway.. See https://git.io/JtMGR for more info.
[10/1/2021, 10:41:23 PM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Configured Name': Characteristic not in required or optional characteristic section for service . Adding anyway.. See https://git.io/JtMGR for more info.
[10/1/2021, 10:41:23 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Yesterday
[10/1/2021, 10:41:23 PM] [Tasmota] Creating service: Waschmaschine ENERGY Yesterday sensor
[10/1/2021, 10:41:23 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_yesterday
[10/1/2021, 10:41:23 PM] [Tasmota] Marking accessory 'Waschmaschine ENERGY Total' to Online
[10/1/2021, 10:41:23 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Today
[10/1/2021, 10:41:23 PM] [Tasmota] Creating service: Waschmaschine ENERGY Today sensor
[10/1/2021, 10:41:23 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_today
[10/1/2021, 10:41:23 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Power
[10/1/2021, 10:41:23 PM] [Tasmota] Creating service: Waschmaschine ENERGY Power sensor
[10/1/2021, 10:41:23 PM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Current Consumption': Characteristic not in required or optional characteristic section for service . Adding anyway.. See https://git.io/JtMGR for more info.
[10/1/2021, 10:41:23 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY ApparentPower
[10/1/2021, 10:41:23 PM] [Tasmota] Creating service: Waschmaschine ENERGY ApparentPower sensor
[10/1/2021, 10:41:23 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_apparentpower
[10/1/2021, 10:41:23 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY ReactivePower
[10/1/2021, 10:41:23 PM] [Tasmota] Creating service: Waschmaschine ENERGY ReactivePower sensor
[10/1/2021, 10:41:23 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_reactivepower
[10/1/2021, 10:41:24 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Factor
[10/1/2021, 10:41:24 PM] [Tasmota] Creating service: Waschmaschine ENERGY Factor sensor
[10/1/2021, 10:41:24 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Voltage
[10/1/2021, 10:41:24 PM] [Tasmota] Creating service: Waschmaschine ENERGY Voltage sensor
[10/1/2021, 10:41:24 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Current
[10/1/2021, 10:41:24 PM] [Tasmota] Creating service: Waschmaschine ENERGY Current sensor
[10/1/2021, 10:41:24 PM] [Tasmota] Found existing accessory: Tasmota
[10/1/2021, 10:41:24 PM] [Tasmota] Creating service: Tasmota switch
[10/1/2021, 10:41:24 PM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Configured Name': Characteristic not in required or optional characteristic section for service . Adding anyway.. See https://git.io/JtMGR for more info.
[10/1/2021, 10:41:24 PM] [Tasmota] Found existing accessory: Waschmaschine status
[10/1/2021, 10:41:24 PM] [Tasmota] Creating service: Waschmaschine status sensor

Describe the solution you'd like:
Appear as one switch (which it is) and present details (voltage, current, consumption etc) to HomeKit if possible.
Describe alternatives you've considered:
I use homebridge-aedes as broker - means it starts along homebridge. Thus MQTT outlets register some time after aedes started up.
When using mqttthing and startPub configuration to ask for on/off status at HB start up the outlets have not yet registered at that point. I would have to create a so-called codec to react on the online messages from the outlets.
Additional context:

Currently Voltage, Current and consumption are not part of the Home App, and to view these values you need to use the Elgato Eve App.

Ok. But could you please make it appear as one switch?

Can you enable debug and share the 'Tasmota:platform Discovered' messages for the device ?  I'm wondering what is creating the second switch.

2021-10-06T16:00:12.041Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_TotalStartTime/config Waschmaschine ENERGY TotalStartTime {
  name: 'Waschmaschine ENERGY TotalStartTime',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_TotalStartTime',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: ' ',
  ic: 'mdi:progress-clock',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['TotalStartTime']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Adding new accessory: Waschmaschine ENERGY TotalStartTime
[10/6/2021, 6:00:12 PM] [Tasmota] Setting accessory information Waschmaschine ENERGY TotalStartTime
2021-10-06T16:00:12.055Z Tasmota:Service fakegatoService exists Waschmaschine ENERGY TotalStartTime
2021-10-06T16:00:12.056Z Tasmota:platform discovery devices - this.api.registerPlatformAccessories
2021-10-06T16:00:12.063Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_Total/config Waschmaschine ENERGY Total {
  name: 'Waschmaschine ENERGY Total',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_Total',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: 'kWh',
  dev_cla: 'power',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['Total']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Total
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine ENERGY Total sensor
[10/6/2021, 6:00:12 PM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Total Consumption': Characteristic not in required or optional characteristic section for service Switch. Adding anyway.. See https://git.io/JtMGR for more info.
2021-10-06T16:00:12.098Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_Yesterday/config Waschmaschine ENERGY Yesterday {
  name: 'Waschmaschine ENERGY Yesterday',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_Yesterday',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: 'kWh',
  dev_cla: 'power',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['Yesterday']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Yesterday
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine ENERGY Yesterday sensor
[10/6/2021, 6:00:12 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_yesterday
2021-10-06T16:00:12.102Z Tasmota:Service fakegatoService exists Waschmaschine ENERGY Yesterday
2021-10-06T16:00:12.102Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
2021-10-06T16:00:12.132Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_Today/config Waschmaschine ENERGY Today {
  name: 'Waschmaschine ENERGY Today',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_Today',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: 'kWh',
  dev_cla: 'power',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['Today']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Today
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine ENERGY Today sensor
[10/6/2021, 6:00:12 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_today
2021-10-06T16:00:12.135Z Tasmota:Service fakegatoService exists Waschmaschine ENERGY Today
2021-10-06T16:00:12.135Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
2021-10-06T16:00:12.138Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_Power/config Waschmaschine ENERGY Power {
  name: 'Waschmaschine ENERGY Power',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_Power',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: 'W',
  dev_cla: 'power',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['Power']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Power
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine ENERGY Power sensor
[10/6/2021, 6:00:12 PM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Current Consumption': Characteristic not in required or optional characteristic section for service Switch. Adding anyway.. See https://git.io/JtMGR for more info.
2021-10-06T16:00:12.141Z Tasmota:Service fakegatoService exists Waschmaschine ENERGY Power
[10/6/2021, 6:00:12 PM] [Tasmota] Creating statusUpdate listener for tele/maschine/SENSOR Waschmaschine ENERGY Power
2021-10-06T16:00:12.142Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
2021-10-06T16:00:12.145Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_ApparentPower/config Waschmaschine ENERGY ApparentPower {
  name: 'Waschmaschine ENERGY ApparentPower',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_ApparentPower',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: 'VA',
  dev_cla: 'power',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['ApparentPower']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY ApparentPower
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine ENERGY ApparentPower sensor
[10/6/2021, 6:00:12 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_apparentpower
2021-10-06T16:00:12.147Z Tasmota:Service fakegatoService exists Waschmaschine ENERGY ApparentPower
2021-10-06T16:00:12.147Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
2021-10-06T16:00:12.150Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_ReactivePower/config Waschmaschine ENERGY ReactivePower {
  name: 'Waschmaschine ENERGY ReactivePower',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_ReactivePower',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: 'VAr',
  dev_cla: 'power',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['ReactivePower']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY ReactivePower
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine ENERGY ReactivePower sensor
[10/6/2021, 6:00:12 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_reactivepower
2021-10-06T16:00:12.155Z Tasmota:Service fakegatoService exists Waschmaschine ENERGY ReactivePower
2021-10-06T16:00:12.155Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
2021-10-06T16:00:12.158Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_Factor/config Waschmaschine ENERGY Factor {
  name: 'Waschmaschine ENERGY Factor',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_Factor',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: 'Cos φ',
  ic: 'mdi:alpha-f-circle-outline',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['Factor']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Factor
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine ENERGY Factor sensor
[10/6/2021, 6:00:12 PM] [Tasmota] Setting accessory information Waschmaschine ENERGY Factor
2021-10-06T16:00:12.160Z Tasmota:Service fakegatoService exists Waschmaschine ENERGY Factor
2021-10-06T16:00:12.160Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
2021-10-06T16:00:12.163Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_Voltage/config Waschmaschine ENERGY Voltage {
  name: 'Waschmaschine ENERGY Voltage',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_Voltage',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: 'V',
  ic: 'mdi:alpha-v-circle-outline',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['Voltage']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Voltage
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine ENERGY Voltage sensor
[10/6/2021, 6:00:12 PM] [Tasmota] Setting accessory information Waschmaschine ENERGY Voltage
2021-10-06T16:00:12.166Z Tasmota:Service fakegatoService exists Waschmaschine ENERGY Voltage
2021-10-06T16:00:12.166Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
2021-10-06T16:00:12.169Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_ENERGY_Current/config Waschmaschine ENERGY Current {
  name: 'Waschmaschine ENERGY Current',
  stat_t: 'tele/maschine/SENSOR',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  uniq_id: '1C52D8_ENERGY_Current',
  dev: { ids: [ '1C52D8' ] },
  unit_of_meas: 'A',
  ic: 'mdi:alpha-a-circle-outline',
  frc_upd: true,
  val_tpl: "{{value_json['ENERGY']['Current']}}",
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine ENERGY Current
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine ENERGY Current sensor
[10/6/2021, 6:00:12 PM] [Tasmota] Setting accessory information Waschmaschine ENERGY Current
2021-10-06T16:00:12.171Z Tasmota:Service fakegatoService exists Waschmaschine ENERGY Current
2021-10-06T16:00:12.172Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
2021-10-06T16:00:12.177Z Tasmota:platform Discovered -> homeassistant/switch/1C52D8_RL_1/config Tasmota {
  name: 'Tasmota',
  stat_t: 'tele/maschine/STATE',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  cmd_t: 'cmnd/maschine/POWER',
  val_tpl: '{{value_json.POWER}}',
  pl_off: 'OFF',
  pl_on: 'ON',
  uniq_id: '1C52D8_RL_1',
  dev: { ids: [ '1C52D8' ] },
  tasmotaType: 'switch'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Tasmota
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Tasmota switch
2021-10-06T16:00:12.182Z Tasmota:Service fakegatoService exists Tasmota
[10/6/2021, 6:00:12 PM] [Tasmota] Creating statusUpdate listener for tele/maschine/STATE Tasmota
2021-10-06T16:00:12.186Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
[10/6/2021, 6:00:12 PM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Configured Name': Characteristic not in required or optional characteristic section for service Switch. Adding anyway.. See https://git.io/JtMGR for more info.
2021-10-06T16:00:12.204Z Tasmota:platform Discovered -> homeassistant/sensor/1C52D8_status/config Waschmaschine status {
  name: 'Waschmaschine status',
  stat_t: 'tele/maschine/HASS_STATE',
  avty_t: 'tele/maschine/LWT',
  pl_avail: 'Online',
  pl_not_avail: 'Offline',
  json_attr_t: 'tele/maschine/HASS_STATE',
  unit_of_meas: '%',
  val_tpl: "{{value_json['RSSI']}}",
  ic: 'mdi:information-outline',
  uniq_id: '1C52D8_status',
  dev: {
    ids: [ '1C52D8' ],
    name: 'Waschmaschine',
    mdl: 'Gosund SP1 v23',
    sw: '9.4.0(tasmota)',
    mf: 'Tasmota'
  },
  tasmotaType: 'sensor',
  pl_on: 'ON',
  pl_off: 'OFF'
}
[10/6/2021, 6:00:12 PM] [Tasmota] Found existing accessory: Waschmaschine status
[10/6/2021, 6:00:12 PM] [Tasmota] Creating service: Waschmaschine status sensor
[10/6/2021, 6:00:12 PM] [Tasmota] Setting accessory information Waschmaschine status
2021-10-06T16:00:12.207Z HAP-NodeJS:Accessory [Waschmaschine ENERGY TotalStartTime] Muting event notification for Name as ids aren't yet assigned!
2021-10-06T16:00:12.207Z HAP-NodeJS:Accessory [Waschmaschine ENERGY TotalStartTime] Muting event notification for Manufacturer as ids aren't yet assigned!
2021-10-06T16:00:12.208Z HAP-NodeJS:Accessory [Waschmaschine ENERGY TotalStartTime] Muting event notification for Model as ids aren't yet assigned!
2021-10-06T16:00:12.208Z HAP-NodeJS:Accessory [Waschmaschine ENERGY TotalStartTime] Muting event notification for Firmware Revision as ids aren't yet assigned!
2021-10-06T16:00:12.208Z HAP-NodeJS:Accessory [Waschmaschine ENERGY TotalStartTime] Muting event notification for Serial Number as ids aren't yet assigned!
2021-10-06T16:00:12.208Z Tasmota:Service fakegatoService exists Waschmaschine status
2021-10-06T16:00:12.209Z Tasmota:platform discoveryDevices - this.api.updatePlatformAccessories
2021-10-06T16:00:12.265Z Tasmota:mqtt emit tele/maschine/LWT Online
[10/6/2021, 6:00:12 PM] [Tasmota] Marking accessory 'Waschmaschine ENERGY Total' to Online
2021-10-06T16:00:12.266Z HAP-NodeJS:Accessory [Waschmaschine ENERGY TotalStartTime] Muting event notification for Total Consumption as ids aren't yet assigned!
[10/6/2021, 6:00:12 PM] [Tasmota] Marking accessory 'Waschmaschine ENERGY Total' to Online
2021-10-06T16:00:12.267Z HAP-NodeJS:Accessory [Waschmaschine ENERGY TotalStartTime] Muting event notification for Current Consumption as ids aren't yet assigned!
[10/6/2021, 6:00:12 PM] [Tasmota] Marking accessory 'Tasmota' to Online
2021-10-06T16:00:12.267Z HAP-NodeJS:Accessory [Waschmaschine ENERGY TotalStartTime] Muting event notification for On as ids aren't yet assigned!

I am having the exact same issue and got frustrated since I couldn't remove it.
I tried filtering it out with deny filters at "homeassistant/sensor/#".  But that did not have any effect. I would be very happy for a solution since it is always one more tap in the Home App before i can actually switch something.
Cheers :)

I had the same issue with a Shelly 1PM, I fixed it by fully removing the cached accessory via Homebridge UI - then when Homebridge was restarted, the Tasmota plugin rediscovered the device and set it up correctly with just one power switch.

Thanks for the hint! I will try it out! It needed to block the /homeassistant/sensor/# branch in order to work or will it work without the blocklist?

Shouldn't need to block anything

okay I can confirm that flushing the cached accessories did not solve the issue.
I even flushed the docker container an it's persistant volumes and that did not help.
here is the log that is adding the devices:
[11/26/2021, 2:15:24 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY TotalStartTime
[11/26/2021, 2:15:24 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY TotalStartTime sensor
[11/26/2021, 2:15:24 PM] [Tasmota] Warning: missing dev_cla Socket4-DP-PC ENERGY TotalStartTime
[11/26/2021, 2:15:24 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY Total
[11/26/2021, 2:15:24 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY Total sensor
[11/26/2021, 2:15:24 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY Yesterday
[11/26/2021, 2:15:24 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY Yesterday sensor
[11/26/2021, 2:15:24 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_yesterday
[11/26/2021, 2:15:24 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY Today
[11/26/2021, 2:15:24 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY Today sensor
[11/26/2021, 2:15:24 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_today
[11/26/2021, 2:15:24 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY Power
[11/26/2021, 2:15:24 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY Power sensor
[11/26/2021, 2:15:24 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY ApparentPower
[11/26/2021, 2:15:24 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY ApparentPower sensor
[11/26/2021, 2:15:24 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_apparentpower
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY ReactivePower
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY ReactivePower sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_reactivepower
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY Factor
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY Factor sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: missing dev_cla Socket4-DP-PC ENERGY Factor
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY Voltage
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY Voltage sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: missing dev_cla Socket4-DP-PC ENERGY Voltage
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket4-DP-PC ENERGY Current
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket4-DP-PC ENERGY Current sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: missing dev_cla Socket4-DP-PC ENERGY Current
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket4-DP-PC status
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket4-DP-PC status sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY TotalStartTime
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY TotalStartTime sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: missing dev_cla Socket2-Fernseher ENERGY TotalStartTime
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY Total
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY Total sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY Yesterday
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY Yesterday sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_yesterday
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY Today
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY Today sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_today
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY Power
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY Power sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY ApparentPower
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY ApparentPower sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_apparentpower
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY ReactivePower
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY ReactivePower sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_reactivepower
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY Factor
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY Factor sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: missing dev_cla Socket2-Fernseher ENERGY Factor
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY Voltage
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY Voltage sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: missing dev_cla Socket2-Fernseher ENERGY Voltage
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher ENERGY Current
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher ENERGY Current sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Warning: missing dev_cla Socket2-Fernseher ENERGY Current
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher status
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher status sensor
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket4-DP-PC
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket4-DP-PC switch
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher switch
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket4-DP-PC ENERGY Total' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket4-DP-PC ENERGY Total' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket4-DP-PC' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket2-Fernseher ENERGY Total' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket2-Fernseher ENERGY Total' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket2-Fernseher' to Online

okay I can confirm that flushing the cached accessories did not solve the issue. I even flushed the docker container an it's persistant volumes and that did not help

Are you sure, and the device disappeared from Home app? According to your log, it only tried to create two switches, one on two separate devices?
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket4-DP-PC
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket4-DP-PC switch
[11/26/2021, 2:15:25 PM] [Tasmota] Found existing accessory: Socket2-Fernseher
[11/26/2021, 2:15:25 PM] [Tasmota] Creating service: Socket2-Fernseher switch

What do you mean? It also finds all the sensor and adds them. This creates a switch device with two switches within it. This the energy Sensor as a switch does not make sense.
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket4-DP-PC ENERGY Total' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket4-DP-PC ENERGY Total' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket4-DP-PC' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket2-Fernseher ENERGY Total' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket2-Fernseher ENERGY Total' to Online
[11/26/2021, 2:15:25 PM] [Tasmota] Marking accessory 'Socket2-Fernseher' to Online

What do you mean? It also finds all the sensor and adds them.

The main lines are those which say "Creating service:" - these tell you what is being created in HomeKit based on what is being discovered. It's creating two "switches" (amongst other sensors), one on Socket4-DP-PC and one on Socket2-Fernseher.
Is one of these two switches incorrect?
Otherwise, if you have other switches in HomeKit, these are still cached accessories, since they aren't being created now.

All lines
"Creating service... ENERGY ..... sensor"

are wrong.
I have only 2 switches on the network and they are being recognized. But along them they get added as energy sensors.
The switches are fine, but the switches as energy sensors is wrong. Plus the energy sensors (which are the switches) get displayed as a switch. They are not showing any sensor data. Just taking up space in the app and doing nothing. I cannot manually delete those.

Same problem here, also Gosund.

All devices are shown twice, I think the plugin incorrectly adds the switch-sensors as another switch?
Here is my log, only the lines with the faulty device:
[1/19/2022, 7:04:00 PM] [Tasmota] Adding new accessory: Schlafzimmer ENERGY TotalStartTime
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: missing dev_cla Schlafzimmer ENERGY TotalStartTime
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: incomplete HASS Discovery message and device definition homeassistant/sensor/643F67_ENERGY_TotalStartTime/config Schlafzimmer ENERGY TotalStartTime
[1/19/2022, 7:04:00 PM] [Tasmota] Adding new accessory: Schlafzimmer ENERGY Total
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: Unhandled Tasmota sensor type energy
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: incomplete HASS Discovery message and device definition homeassistant/sensor/643F67_ENERGY_Total/config Schlafzimmer ENERGY Total
[1/19/2022, 7:04:00 PM] [Tasmota] Adding new accessory: Schlafzimmer ENERGY Yesterday
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: Unhandled Tasmota sensor type energy
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: incomplete HASS Discovery message and device definition homeassistant/sensor/643F67_ENERGY_Yesterday/config Schlafzimmer ENERGY Yesterday
[1/19/2022, 7:04:00 PM] [Tasmota] Adding new accessory: Schlafzimmer ENERGY Today
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: Unhandled Tasmota sensor type energy
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: incomplete HASS Discovery message and device definition homeassistant/sensor/643F67_ENERGY_Today/config Schlafzimmer ENERGY Today
[Schlafzimmer ENERGY Power@Schlafzimmer ENERGY Power@Current Consumption] Characteristic not in required or optional characteristic section for service . Adding anyway.
[1/19/2022, 7:04:00 PM] [Tasmota] Adding new accessory: Schlafzimmer ENERGY Power
[1/19/2022, 7:04:00 PM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Configured Name': Characteristic not in required or optional characteristic section for service . Adding anyway.. See https://git.io/JtMGR for more info.
[1/19/2022, 7:04:00 PM] [Tasmota] Found existing accessory: Schlafzimmer ENERGY ApparentPower
[1/19/2022, 7:04:00 PM] [Tasmota] Creating service: Schlafzimmer ENERGY ApparentPower sensor
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_apparentpower
[1/19/2022, 7:04:00 PM] [Tasmota] Found existing accessory: Schlafzimmer ENERGY ReactivePower
[1/19/2022, 7:04:00 PM] [Tasmota] Creating service: Schlafzimmer ENERGY ReactivePower sensor
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: Unhandled Tasmota power sensor type _energy_reactivepower
[1/19/2022, 7:04:00 PM] [Tasmota] Found existing accessory: Schlafzimmer ENERGY Factor
[1/19/2022, 7:04:00 PM] [Tasmota] Creating service: Schlafzimmer ENERGY Factor sensor
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: Unhandled Tasmota sensor type power_factor
[1/19/2022, 7:04:00 PM] [Tasmota] Found existing accessory: Schlafzimmer ENERGY Voltage
[1/19/2022, 7:04:00 PM] [Tasmota] Creating service: Schlafzimmer ENERGY Voltage sensor
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: Unhandled Tasmota sensor type voltage
[1/19/2022, 7:04:00 PM] [Tasmota] Found existing accessory: Schlafzimmer ENERGY Current
[1/19/2022, 7:04:00 PM] [Tasmota] Creating service: Schlafzimmer ENERGY Current sensor
[1/19/2022, 7:04:00 PM] [Tasmota] Warning: Unhandled Tasmota sensor type current
[1/19/2022, 7:04:00 PM] [Tasmota] Found existing accessory: Schlafzimmer status
[1/19/2022, 7:04:00 PM] [Tasmota] Creating service: Schlafzimmer status sensor
[1/19/2022, 7:04:00 PM] [Tasmota] Found existing accessory: Schlafzimmer
[1/19/2022, 7:04:00 PM] [Tasmota] Creating service: Schlafzimmer switch
[1/19/2022, 7:04:00 PM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Configured Name': Characteristic not in required or optional characteristic section for service . Adding anyway.. See https://git.io/JtMGR for more info.
[1/19/2022, 7:04:00 PM] [Tasmota] Marking accessory 'Schlafzimmer ENERGY Power' to Online
[1/19/2022, 7:04:00 PM] [Tasmota] Marking accessory 'Schlafzimmer' to Online

It adds several accessories for all the sensors, but only the ENERGE Power one seems to be wrong?
But nevertheless, none of the sensors are shown.
If there is something I can do to help pin this down, just let me know!


A user should be able to stop and restart a service using the CLI

Background & motivation
A user can stop and restart a service using the Starlark instructions.
Desired behaviour
A user should be able to stop and restart a service using the following CLI commands:
kurtosis service stop <enclave name> <service name>
kurtosis service start <enclave name> <service name>

How important is this to you?
Painful; the lack of this feature makes using Kurtosis frictionful.

Related to #673


Minor cleanups from working on sampling bugfix

Description
While working on #14355, I came across a bunch of typos, spacing inconsistencies, etc. I pulled those non-functional changes out into a separate PR.

This PR has:

[x] been self-reviewed.

Heya @kfaraz, thanks for your review! 🙇

As for the java code, your changes do improve readability but it is still better to leave these changes to the next person touching these files for functional improvements. If you are updating the behaviour of these classes in any of your other PRs, you can include these there.

Do you think the benefit of a slightly cleaner git history outweighs leaving non-functional cleanups like these up for another day? Personally, I feel any updates similar to this one benefit future developers more than a clean history, and we should encourage anyone to make similar updates. After all, what are the chances that the next person touching the codebase will catch the exact same thing?
However, I of course can easily revert any of the Java comments if you feel strongly about this.

Do you think the benefit of a slightly cleaner git history outweighs leaving non-functional cleanups like these up for another day?

Yeah, I am torn about it at times myself 🤷🏻 .

Personally, I feel any updates similar to this one benefit future developers more than a clean history,

I would have to disagree on the benefit to developers aspect as anyone reading a typo can immediately make out the correct alternative. Had we been rephrasing the javadocs to use better language or adding new info, it could have been beneficial.

we should encourage anyone to make similar updates. After all, what are the chances that the next person touching the codebase will catch the exact same thing?

I agree that we should encourage these improvements, however small. I personally do tend to include these with my own changes.
But I prefer a slightly different approach of going about them. I would rather contributors (and even reviewers) read the comments, javadocs, logs, exceptions in and around the code which is being touched in the PR at hand. This practice ensures that any outdated info is updated (which is often the case with comments and javadocs) and is bound to catch any formatting/typo issues too as an added benefit.
Let me know what you think.

Heya @kfaraz, thank you for your detailed thoughts. Alright, let me focus this PR on updating the Markdown doc only, and include some of the cleanups with #14355 (in case I touch that code).

@kfaraz Reverted the improvements in the non-markdown files.
(/cc @ektravel Do you mind taking a quick peek as well?)

@amaechler , sorry,  I had missed a couple of minor suggestions. Just added these.

Reading through this PR, I realized that the whole of kinesis ingestion doc can do with a bit of language and structure revamp (e.g. adding a separate column for default values).
But we can do that in a separate PR. @ektravel , would you be willing to take that up?
Merging these changes for now.

@kfaraz I will create a separate PR to revamp the kinesis ingestion doc.


bosh -d wl-bosh deploy cf-deployment.yml is failing

I am able to create and upload release using cf-262.yml
But when I run bosh -d wl-bosh deploy cf-deployment.yml, I am getting following warning and error.
11:55:13 | Deprecation: Ignoring cloud config. Manifest contains 'networks' section.
11:55:13 | Preparing deployment: Preparing deployment (00:00:00)
L Error: Job 'consul_agent' not found in Template table
11:55:13 | Error: Job 'consul_agent' not found in Template table
Started  Mon Jun 12 11:55:13 UTC 2017
Finished Mon Jun 12 11:55:13 UTC 2017
Duration 00:00:00
Task 68 error
Updating deployment:
Expected task '68' to succeed but was state is 'error'
Exit code 1

@dgadiraju It looks like you're using the new (golang) BOSH CLI, or the older (Ruby) one -- is that right? If so, can you try with the old CLI?

Hi @dgadiraju. I'm going to close the issue due to inactivity, but feel free to open it again if you need more help.


Feature Request/Idea: Custom colors for specific tags

Hey,
I know you want to keep this plugin simple but i am missing that one feature that i wanted at first and also it was the reason why i downloaded this plugin, and that's custom color for specific tags.
My case of usage: I want to make tag #recallable always yellow and all other tags to be colored like this plugin now does, via palette. This is just an example and i want this for multiple tags.
My suggested solution: If you don't want to mess with adding setting components inside setting tab, you could just add multiline textbox where each line will be tag and color separated by space, or other character that does not belong into tag and color.
#recallable #FFFF00
#uncompleted #FF0000
#completed #00FF00
...

I guess you get that idea.
Other Sub-Ideas:

Custom coloring sub-tags of parent specified tag color
Selecting Pre-Defined colors by obsidian (here is list of CSS vars)
Settings intuitive UI to make it better for casual users

Anyways thank you for this plugin! ❤ Hope my solution will be at least considered to add. This would make this plugin a 10x better!

Hi there!
Thank you for your very polite and clear suggestion!

you could just add multiline textbox where each line will be tag and color separated by space, or other character that does not belong into tag and color.

If you want to customize particular tag's color you don't need this plugin.
You can use CSS Snippets or probably just https://github.com/Zachatoo/obsidian-css-editor to edit snippets inside Obsidian. Here is a related discussion where you can get selectors for colorizing specific tags https://forum.obsidian.md/t/how-to-show-all-tags-in-color/40113
Thank you again and with you find right solution to improve your productivity ✨


[Question] Testing the module

Hello, InquirerPy uses prompt_toolkit in the background, which is a library where you are capable of mocking prompt answers. I know that there are some unit tests on that repo, but, is there a way to test and mock a result for InquirerPy prompt function ?
Thanks a lot!

Hi @felipemeriga ,
Depending on how far deep you wanna go with mocking, but if you are just looking to mock the prompt function (which I recommend, there's not really any benefit for you to mock deeper since it has already been tested by the unit test) it would be quite simple.
Module/somefunction.py
from InquirerPy.resolver import prompt

def get_name():
    return prompt({"type": "input", "message": "Name:"})

tests/test_somefunction.py
import unittest
from unittest.mock import call, patch

from Module.somefunction import get_name

class TestPrompt(unittest.TestCase):
    @patch("Module.somefunction.prompt")
    def test_get_name(self, mocked_prompt):
        mocked_prompt.return_value = "hello"
        result = get_name()
        self.assertEqual(result, "hello")

Might have typo but the idea is just directly mock the prompt function. There's no other consideration on the terminal environment, IO stuff or prompt_toolkit, because these stuff are called later in the prompt function and by mocking it, those will never run.
Lemme know if you need any further assistance (e.g. pytest).
Thanks,
Kevin


dtb image generated here is far too small and does not flash

With these build steps, I get a dtb image that is less then 15 kb
and it does not flash with fastboot:
(in the out/target/product/hikey960 folder)
14336 Sep 14 11:34 dt.img
in the device/linaro/hikey-kernel folder, the dtb images are much
bigger:
23076236 Sep 12 11:12 Image-dtb-4.9
these do flash with fastboot.

14336 is reasonable. Mine is 12288.
Image-dtb-4.9 includes both the kernel Image and the dtb, so it's much bigger.

Hi docularxu,
Is there some extra step that I am missing in order to be able to flash it to the device?
Thanks.

I figured it out. I copied them over to the device/linaro/hikey-kernel
folder in the aosp and let the aosp build them. Then I was able to flash them.


Can we add configuration of  r.Lumen.Reflections.DiffuseBoost ?

Hi Lyall,
Thank you for your fantastic Wukong mod! I’ve noticed some issues with lighting quality in darker scenes, especially in Chapter 1. It seems adjusting the r.Lumen.Reflections.DiffuseBoost setting could improve the lighting based on community suggestions.
I tried using Unreal Engine 5 Unlocker  (UUU5) to tweak this, but seems like it conflicts with your mod’s DLL. Since I’m not familiar with C++ or your toolchain, could you consider adding an option to adjust the r.Lumen.Reflections.DiffuseBoost setting directly within the mod? This would make it easier to fine-tune the lighting without third-party tools.
Thanks for your consideration!
Best regards,

r.Lumen.Reflections.DiffuseBoost is not a valid CVar in this version of Unreal Engine. I have dumped all available CVars here.


[FLINK-13458][table] ThreadLocalCache clashes for Blink planner

What is the purpose of the change
Fixes a class clash between planners.
Brief change log
Class moves to flink-table-common.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Thanks everyone. Merging...


Use DataTree from xarray

DataTree is already available in main and will be usable and importable from xarray directly starting with next xarray release. see https://docs.xarray.dev/en/latest/whats-new.html and https://github.com/pydata/xarray/issues/8807

We should also discuss how quickly do we want to make the switch. There have already been a couple changes of behaviour between DataTree in xarray-datatree package and DataTree in xarray itself so I'd probably change the dependency as soon as the next xarray release is out to make sure we don't end up with a painful transition later on when we'd like to start advertizing the library


Add README.md to pcr0tool

Here we have two commits:

One to improve UX a little bit: to do not require pcr0tool dump_registers before pcr0tool sum on a CBnT machine.
Another is README.md

@ChriMarMe , @rihter007 : It reset the approves (because I did a force push), could you re-stamp it, please? :)


[BUG] Detached Volume Stuck in Attached State During Node Eviction

Describe the bug
A detached volume is stuck in the attached state during node eviction, and the volume can't go back to the detached state
To Reproduce

Creating a three-node cluster
Creating a volume pvc-d743c883-692e-46d0-a3a5-9cb485c0eb90 with three replicas
Attaching the volume to one of the nodes and detaching it
Choosing one node (for example node2), disabling its Node Scheduling and enabling Eviction Requested
The volume will be kept attached with a stopped replica which resides on the evicted node

Replica pvc-d743c883-692e-46d0-a3a5-9cb485c0eb90-r-f763ee06 running on node-0
Replica pvc-d743c883-692e-46d0-a3a5-9cb485c0eb90-r-6de8993b running on node-1
Replica pvc-d743c883-692e-46d0-a3a5-9cb485c0eb90-r-21988b84 running on node-2
Replica pvc-d743c883-692e-46d0-a3a5-9cb485c0eb90-r-44369fec stopped on node-2

Expected behavior
Volume pvc-d743c883-692e-46d0-a3a5-9cb485c0eb90 should be back to detached state
Support bundle for troubleshooting
supportbundle_d1e587b6-6921-420c-8e0d-a068c6cf110a_2024-11-11T08-57-30Z.zip
Environment

Longhorn version: v1.4.3
Harvester: v1.2.1
Impacted volume (PV): pvc-d743c883-692e-46d0-a3a5-9cb485c0eb90

Workaround and Mitigation

Reducing volume's replica count to 2 before node eviction

@chriscchien Could you check if the issue is reproducible in v1.6.3 and v1.7.3? Thank you.

I can reproduce this issue in v1.7.2 and v1.6.3 by below steps

Dynamic provision a volume, wait volume healthy.
Scale down workload to 0 to detach the volume.
From UI, choose one replica node and disabling the Node Scheduling and enabling Eviction Requested immediately after step 2.
Volume kept attached.

in v1.6.3, 1 stopped replica and 3 running replicas observed like this ticket mentioned.
in v1.7.2, 3 replicas kept in running state, no extra stopped observed.

v1.7.2 - all replica running (evict ip-172-31-32-129)
> kl get nodes.longhorn.io
NAME               READY   ALLOWSCHEDULING   SCHEDULABLE   AGE
ip-172-31-37-57    True    true              True          3m53s
ip-172-31-40-145   True    true              True          3m53s
ip-172-31-32-129   True    false             True          3m52s
>
> kl get volume
NAME                                       DATA ENGINE   STATE      ROBUSTNESS   SCHEDULED   SIZE         NODE              AGE
pvc-94b6d534-ae8b-408b-8b9b-94f6b0e83b4d   v1            attached   healthy<PHONE_NUMBER>   ip-172-31-37-57   2m55s
>
> kl get replicas
NAME                                                  DATA ENGINE   STATE     NODE               DISK                                   INSTANCEMANAGER                                     IMAGE                               AGE
pvc-94b6d534-ae8b-408b-8b9b-94f6b0e83b4d-r-b087166e   v1            running   ip-172-31-40-145   1d488181-b38c-402c-8944-b75c2226319c   instance-manager-682be07898be605a482901d3854583f9   longhornio/longhorn-engine:v1.7.2   3m1s
pvc-94b6d534-ae8b-408b-8b9b-94f6b0e83b4d-r-80b9b644   v1            running   ip-172-31-37-57    edff8df0-e5f7-4799-b093-6eb24331b4ff   instance-manager-f7ab0aa2aa492fb64d6aa19031c57c1f   longhornio/longhorn-engine:v1.7.2   3m1s
pvc-94b6d534-ae8b-408b-8b9b-94f6b0e83b4d-r-b30a5343   v1            running   ip-172-31-32-129   f8a523fa-195c-41ff-bae6-83865f278af0   instance-manager-0e8c361d05c1cf0fa4a6373f22853e8c   longhornio/longhorn-engine:v1.7.2   84s

v1.6.3 - 3 replics running and 1 stopped replica (evict ip-172-31-37-57 )
> kl get nodes.longhorn.io
NAME               READY   ALLOWSCHEDULING   SCHEDULABLE   AGE
ip-172-31-37-57    True    false             True          3m35s
ip-172-31-32-129   True    true              True          3m32s
ip-172-31-40-145   True    true              True          3m34s
>
> kl get volume
NAME                                       DATA ENGINE   STATE      ROBUSTNESS   SCHEDULED   SIZE         NODE               AGE
pvc-a4c3e035-653e-4652-89e9-dd06c25baf62   v1            attached   healthy<PHONE_NUMBER>   ip-172-31-40-145   2m29s
>
> kl get replicas
NAME                                                  DATA ENGINE   STATE     NODE               DISK                                   INSTANCEMANAGER                                     IMAGE                               AGE
pvc-a4c3e035-653e-4652-89e9-dd06c25baf62-r-a9410bb4   v1            running   ip-172-31-40-145   1d488181-b38c-402c-8944-b75c2226319c   instance-manager-8c0e16cf9c459267bd4d71b9daa248e1   longhornio/longhorn-engine:v1.6.3   2m47s
pvc-a4c3e035-653e-4652-89e9-dd06c25baf62-r-fd413e43   v1            running   ip-172-31-32-129   f8a523fa-195c-41ff-bae6-83865f278af0   instance-manager-ffb1c3aff0267f3fb796535d793464f7   longhornio/longhorn-engine:v1.6.3   2m47s
pvc-a4c3e035-653e-4652-89e9-dd06c25baf62-r-dae675b5   v1            running   ip-172-31-37-57    edff8df0-e5f7-4799-b093-6eb24331b4ff   instance-manager-cb6bb2ff2d85ed7981d4a7f9aed44aa7   longhornio/longhorn-engine:v1.6.3   2m46s
pvc-a4c3e035-653e-4652-89e9-dd06c25baf62-r-2d2bb614   v1            stopped                                                                                2m4s

Reproduced on the current active Longhorn versions; did not check v1.4.3.
Cause:
The volume eviction controller updated the attachment ticket after the volume attachment controller had already detached the volume.
2024-11-14T07:08:22.467291107Z time="2024-11-14T07:08:22Z" level=info msg="Volume e2e-test-volume-123 is selected to detach from node ip-10-0-2-13" func="controller.(*VolumeAttachmentController).handleVolumeDetachment" file="volume_attachment_controller.go:555" controller=longhorn-volume-attachment longhornVolumeAttachment=e2e-test-volume-123 node=ip-10-0-2-13

2024-11-14T07:08:31.147398370Z time="2024-11-14T07:08:31Z" level=info msg="Volume e2e-test-volume-123 is selected to attach to node ip-10-0-2-13, ticket +&{volume-eviction-controller-e2e-test-volume-123 volume-eviction-controller ip-10-0-2-13 map[disableFrontend:any] 0}" func="controller.(*VolumeAttachmentController).handleVolumeAttachment" file="volume_attachment_controller.go:676" controller=longhorn-volume-attachment longhornVolumeAttachment=e2e-test-volume-123 node=ip-10-0-2-13

Workaround for v1.4.3: Enable the Replica Node Level Soft Anti-Affinity setting, and Longhorn will automatically detach the volume.

Workaround for v1.4.3: Enable the Replica Node Level Soft Anti-Affinity setting, and Longhorn will automatically detach the volume. /cc @WebberHuang1118

Hi @c3y1huang
Does one node require multiple disks to make this workaround work?  What if the three nodes only have one disk? Thanks.

Move this back to implementation as this has introduced a regression failure.
https://github.com/longhorn/longhorn/issues/9857

Move this back to Analysis and Design as this has introduced a regression failure. #9857

Proposed fix:
Precheck there are valid replica candidates before attaching the volume; otherwise, avoid volume attachment.

@c3y1huang The PR is merged. We can move it forward. Thank you.

Verified pass on longhorn master(https://github.com/longhorn/longhorn-manager/commit/bb0a41dba42cf7fe1bebdd3f2e15efec8eb896ff)
Following test steps, volume detached successfully.


Add g.berezin solution for day 5 with explanation

Hello, thanks for taking the time to write the solution! however I'd ask you to consider the schedule first - @stewSquared is meant to be doing today

@bishabosha @GrigoriiBerezin
I was just now sitting down to write this up.
Seeing as how this is already written, I don't mind handing it over.
Perhaps I'll do some review and provide suggested edits.

ok great, thank you both :)

@GrigoriiBerezin Do you have your original code published on GitHub?
I'm finding it a little tricky to get code from your write-up compiling (endFrom is missing, uses some methods from cats, it's not always clear when a def is a method and what class it's supposed to be part of).

Just a heads up, we have a requirement that the code be written with a clear def part1(input: String): Any and def part2(input: String): Any entry points (the result can be more specialised)

Hello, thanks for taking the time to write the solution! however I'd ask you to consider the schedule first - @stewSquared is meant to be doing today - hopefully we can agree together what should be done here
Edit: I should probably fix the website template so that people look first there

Sorry, didn't see that you have schedule for that

I've solved task using scala2, but I will reformat solution explanation to scala3 with your edits today, if you don't mind

Just a heads up, we have a requirement that the code be written with a clear def part1(input: String): Any and def part2(input: String): Any entry points (the result can be more specialised)
Also i believe the mapping is always sequential so mostly the resource "kind" is irrelevant (please correct me if some input had a non sequential chain)

In case of changing order of maps, should I left it as it is? User input may be different due to no limitation about it in task

I refactored a bit the code, it's still the same solution but reuses calculate from part 2 for both solutions. I also described the functionality of the code

Thanks again for refactoring!
I refactored a bit the code, it's still the same solution but I tried to make it use up fewer columns (avoiding scrolling), also it reuses calculate from part 2 for both solutions. I also described the functionality of the code more.

Thank you


Is there a way to use auth with proxy?

For example http://username:password@IP
It would be great if we can get this working

I used proxy-chain to solve this problem.

See my snippet in https://github.com/NikolaiT/se-scraper/issues/51#issuecomment-635876218 for an example


Benchmark suite

Add benchmarks measuring to make sure that the things we think are getting erased are actually getting erased in practice.

Relevant instructions at http://blog.johantibell.com/2012/04/cabal-bench.html and https://github.com/travis-ci/artifacts.


Add Getting Started section to README

README Update
Please add a getting started section to README so that folks know how to start with this project.

Added Getting started section to README file


Passing variable between Phases(access and response)

Unable to Pass variables between access and response phase.
Any suggestion on above please?

hi @sivasubramani300890
could you please elaborate on this?

Hi @jschmid1 , Thanks for your response.
Tried to pass some values between phases. Able to do through self.var


Added Interlingua translation

Since we have Esperanto, I've added the translation for Interlingua (another auxillary language)

@dustinkredmond Thank you, and you missed two the most important files:

https://github.com/chubin/wttr.in/blob/master/share/translations/de-help.txt
https://github.com/chubin/wttr.in/blob/master/share/translations/de.txt

@chubin Whoops, sorry about that, I've added another commit with "ia.txt" and "ia-help.txt"

@dustinkredmond Merged, deployed! Please test.
It looks great

@chubin Tested and I agree. All looks great!


Mysteriously breaks

Done in 2.34s.
fs.js:913
  return binding.readdir(pathModule._makeLong(path), options.encoding);
                 ^

Error: ENOENT: no such file or directory, scandir '/Users/per/Github/playground/node_modules'
    at Object.fs.readdirSync (fs.js:913:18)
    at getDirectories (/usr/local/lib/node_modules/yrn/bin.js:65:13)
    at restorePackagesAndSymlinks (/usr/local/lib/node_modules/yrn/bin.js:100:22)
    at ChildProcess.x (/usr/local/lib/node_modules/yrn/bin.js:48:5)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:194:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)

Couldn't pinpoint it so far.

Can't reproduce.


Weird bug in ListOption? [secret-distribute-generic]

Specifying memref.get_global in ops to distribute results in some strange behavior when looking at the opsToDistribute
        distributeOpts.opsToDistribute = {"affine.for", "affine.load",
                                          "affine.store", "memref.get_global"};
        pm.addPass(secret::createSecretDistributeGeneric(distributeOpts));

Results in byte garbage for memref.get_global, and that the generic isn't distribute through the op

16 bytes seems like the max


Using tab to change input elements does not trigger keyboard event

Shouldn't changing focus from one element to another using TAB change the input type to keyboard?
Steps to reproduce at demo page:

use mouse to click input Email address
use keyboard TAB key to change focus to input Password
input type stays as mouse 💣

If you keep using keyboard TAB key to change focus, it will change input type to mouse when button Submit is focused, which seems inconsistent

Hi @felipesabino,
This is intended behavior. Since everyone has to use a keyboard to interact with form elements, the script persists the last known input type while interacting with inputs, selects and textareas. I left buttons out since they are used outside of forms other interface interactions, like triggering a mobile menu.
In a previous iteration I had an optional flag that could be set to disable this behavior but I removed it in this version for simplicity. I could see a couple options to bring back that functionality:

Bring back a flag, I believe it was setting data-whatinput-formtyping on the body, that disables the behavior and allows the input type to switch when interacting with a form.
Update the data-whatintent attribute with the actual interaction type during form interactions since whatintent is more reactive to input changes (it detects for mousemove).

What do you think?

I came here to report that keyboard-after-mouse didn’t update but understand your reasoning. Nice work.
Would it be accurate to say that focussing initially with mouse should leave data-whatintent="mouse" and tabbing would update data-whatinput="keyboard"?
As for buttons, I would style them differently in or outside of forms if I needed to, and would simply opt for accurate representation in the plugin.

@ten1seven But what about updating data-whatinput to keyboard only if user pressed TAB key?

@DmitryGonchar it would switch to keyboard outside of the context of form elements but retain mouse (if that's what you had been using) since someone who switched to the keyboard to fill in a form might use the tab key to move to the next input.
I've been working on version 5.0 and it changes the logic of data-whatinput and data-whatintent. In this new version, data-whatinput no longer ignores form input keyboard use. It's the "hard-line", reporting exactly what's happening. data-whatintent continues to be more speculative, reporting mouse usage on mousemove and now has the "old" form input typing buffer. I'd love it if you, @jasonhibbs, and @felipesabino would take a look and let me know what you think since you all have been vocal about this feature!
https://github.com/ten1seven/what-input/tree/version-five

@ten1seven Sorry, I did not understand, where is the problem with this suggestion?

someone who switched to the keyboard to fill in a form might use the tab key to move to the next input.

Yes, and in this case (if I understand correctly) data-whatinput should become "keyboard", since right now user is using keyboard to navigate (keyboard became the current input method). But it does not right now.
Ok, will take a look

About v5. Looks good!
But I am not sure it will be applicable for case that we have. We want to show a special :focus style if user navigates around website with a keyboard (this is mostly for users with disabilities). In v5 if we set it in [data-whatinput="keyboard"] :focus { (as we do now) - it will be shown for non-disabled users when they type letters into the <input>. If we do this for [data-whatintent="keyboard"] :focus { then this effect will disappear as soon as user drags a mouse around - also a strange (from the user's point of view) behavior.
And a code style opinion - for me it was difficult to distinguish currentInput and currentIntent variables - I often confused them because they look very similar. This can become a source of bugs later  (for you or for other contributors). Some suggestions: renaming to currentIntention or currentInputIntent (maybe curInputIntent to make it shorter), or rename Intent to something else.

@DmitryGonchar this is the big conundrum that I have with this script:

Report switches in input immediately: this might cause confusion when, as you mention, someone using the keyboard moves the mouse.
Make assumptions about usage by not switching to "keyboard" when someone using a mouse starts typing in a form field (or uses common mouse modifier keys, like CTRL+click): assumptions are dangerous and can misrepresent someone's actual needs.

My attempt to address these conflicting usages was for data-whatinput to behave like bullet #1 and data-whatintent to behave like bullet #2. I'm curious what you think would be the ideal behavior? I'm still tweaking v5 and am happy to get more feedback!
Also, the current live demo page still relies on v4, so I'm hoping you downloaded a zip of v5 to test out the new behavior.

ah, ok, so it is free to change the behavior of data-whatintent.
I would change currentIntent condition to
// list of keys codes for which we change intent even for form inputs
var changeIntentMap = [
 9 // Tab
];
...
if( (... && formInputs.indexOf(activeElem.nodeName.toLowerCase()) === -1)
  || changeIntentMap.indexOf(eventKey) !== -1 ) {
  currentIntent  = value;

this will enable switching intent to keyboard on Tab for inputs
And also there need to be a config option to disable switching intent to mouse on mouse move. I am not sure why it is there, since most often moving mouse is not an input action.

Actually, based on the description of #1 ("Report switches in input immediately") you should change whatinput on mousemove , not whatintent. Then config option is not needed

@ten1seven Should I?

Yes, I think this is a good idea 👍

@ten1seven Sorry for the delay, done. Other files were generated by running gulp
Should I make similar fix and PR to master ?
Have you made up your mind about 2) - changing input instead of intent on mouse move (see this comment)?

Hi @DmitryGonchar, thanks! I'm out of the country on vacation all this week so I'll take a look when I get back on Monday.

@DmitryGonchar just rolled your changes into version 4: https://github.com/ten1seven/what-input/pull/64

This is rolled into v4 and v5. Going to close this issue.

I'm having trouble understanding why this changed was rolled only into "intent", given the earlier comment and that that intent currently does update for mouse-move events. I would much rather be able to have this behavior without having the mouse move behavior


Adding annotation functionality

Purpose
$title
Goals

Adding the annotation for the functions that need be inside the connector
Adding the icons for the connector

Approach
Annotation analysis task was introduced instead of function analysis task. Icon path need to be defined in the annotation field and if icons were identified connector will be created with the icons provided.
User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? no
Ran FindSecurityBugs plugin and verified report? no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples
The user defined function must follow the following syntax,
import ballerinax/ballerina ;

@ballerina:ConnectorInfo{
    name:"testConnector",
    iconPath:"./icons"
}
public function test(xml xmlA, xml xmlB, xml xmlC) returns xml {
    return xmlA+xmlB+xmlC
}

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

icon path must be now mentioned in the Ballerina.toml file as mentioned below, otherwise default icons will be used.
[path]
iconPath = path/to/icons


Add LightHouse to GitHub workflows

Is your feature request related to a problem? Please describe.
As of now, the FCC sites is not measured by any sort of site analyzing tools. But it is becoming increasingly important to keep an eye out on the UI/UX, a11y etc scores.
Google Webmasters announced on May 28, 2020 that they'll be starting to incorporate Core Web Vitals to the SEO and site ranking. Here's the link to the announcement. That's not all, Google devs announced on Web Dev Live(Web Dev Live is a Google dev conference of sorts in replacement of Google IO 2020 due to worldwide pandemic) that starting from next year they'll be adding more Performance Metrics like these and they recommend to use LightHouse to start optimizing from now on (Chick here to learn more).
Describe the solution you'd like
At such a time, it's crucial to give importance to a site's Core Web Vital scores and optimize them. There's no better way to do so than using LightHouse. LightHouse is a Google developed site analyzing tool that'll score a site for it's Performance, Accessibility, SEO etc criterias. LightHouse measures Core Web Vitals and shows the results.  LightHouse will also point out the problems in these sector and the steps to fix it.

Here's how the scores and optimizing tips looks like ->
https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1596356088677-85438.report.html
(Please note I've generated these scores using the workflow on #39353 with the production version of FCC site. The production build was created by running npm run build && npm run start)


c# - Chronic.Parser

Hello All,
I'm using C#, and building a LuisDialog.  Luis is passing me the builtin date & time entities, but I need them to be translated into real dates and times.
Looking at the example in the docs for the alarmbot, http://docs.botframework.com/sdkreference/csharp/dialogs.html#alarmBot
var parser = new Chronic.Parser();
Google tells me that Chronic is a ruby framework, at which point I regurgitated some of my tea.  (only joking)
I cant find this in the bot builder SDK, or in the Luis namespace - what am I missing?
Cheers for any help in advance,
Kind Regards,
Matt

Oh - is it nChronic? nChronic

Yes, its nChronic

Its 'chrono', so try using chrono.parseDate( xyz); .
i hope it works now. :+1:


GUACAMOLE-231: Document Guacamole protocol "mouse" instruction.

NOTE: Intended for staging/0.9.12-incubating. This is documentation for the "mouse" instruction implemented by apache/incubator-guacamole-server#76 and apache/incubator-guacamole-client#128, which are collectively fixes for a regression due to GUACAMOLE-117).


[Doc] Enhance the document's structure

Suggested the new structure of document as below:

What's the HwameiStor
Quick Start
2.1 Installations
2.2 Start a Stateful Application
2.2.1 Basic Operations
2.2.2 Advanced Operations
2.3 Advanced Features
2.3.1 Node Expansion
2.3.2 Disk Expansion
2.3.3 Upgrade
2.4 Uninstall
Architecture of HwameiStor
3.1 Overview
3.2 Components
3.3 Resources
3.4 APIs
Development Designs (Optional)
Applications
5.1 TiDB
5.2 MinIO
...
Terminologies
Community
FAQs

working on a doc pr.


Why the report associates "typescript:3.2.1" issues with "CVE-2021-1639" vulnerabilities?

In a recent dependency check, we found that the report reported a problem with 'typescript:3.2.1', but the "CVE-2021-1639" mentioned in the details was a "Visual Studio Code" vulnerability. And the vulnerability details do not describe that the problem is caused by the typescript version.
Why does dependency check correlate the two, is this a bug in dependency check? Or is there some other reason for this result?

Because Sonatype OSSINDEXs analysts have linked that CVE against the npm Typescript package. Follow the OSSINDEX hyperlink and login to Sonatype OSSINDEX to see if they have more info on the vulnerability-page on why they linked this issue to the npm typescript package

Looks like the root cause was in the typescript package and was fixed during development of 4.2 and only backported to the 3.1.x, 3.7.x, 3.9.x, 4.0.x and 4.1.x branches.


METRON-1233: Remove description of Global configuration from Enrichment doc

It confuses reader. Description of Global configuration is available ahead of the enrichment and listed here:
https://metron.apache.org/current-book/metron-platform/metron-common/index.html
Global config is used for validation of the fields.
Enrichment is used for fields enrichment and probably can also be used for validation of the fields (which is not covered in the doc).
From available doc I can see that they serve two different purposes.
So, I don't see any reason to mention global config in enrichment description. What's the benefit of knowing about global configuration when you want deep dive in enrichment?
Contributor Comments
[Please place any comments here.  A description of the problem/enhancement, how to reproduce the issue, your testing methodology, etc.]
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[ ] Have you included steps or a guide to how the change may be verified and tested manually?

[ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && build_utils/verify_licenses.sh

[ ] Have you written or updated unit tests and or integration tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

Thanks for the contribution @DimDroll. Can you take a look at https://github.com/apache/metron/pull/791 - does this help? There are some relevant global config options for enrichment.

Still needs conflict resolution, still needs relevancy check

@mmiklavc , I still don't see anything helpful specified about enrichment in here:
https://metron.apache.org/current-book/metron-platform/metron-common/index.html
I guess we can reference enrichment configuration in global configuration, but I still don't see sense of mentioning Global configuration in Enrichment section without anything relevant to enrichment in Global configuration.

bump.  Let's get a response on this @mmiklavc , @JonZeolla , @nickwallen

@DimDroll @ottobackwards - All of our topologies pull in the global config. One such more recent example is that we now provide an option for specifying batching details for enrichment:
enrichment.writer.batchSize
enrichment.writer.batchTimeout

The reason for this is that we don't have a global-only-per-topology type of configuration, with the exception parsers because of how they can be deployed independently. If you think there's some better clarification that could be made, I'm open to it. But I think the link between parsers, enrichment, indexing, and the global configs should be maintained as it is relevant.

@mmiklavc can you re-visit this and if it is not going to land close it?

@ottobackwards - considering the current state of enrichment and global config options, I think we should close this. Anything special we need to do to close someone else's PR? We've crossed the threshold for activity lapse, so maybe that's all.

@DimDroll we are going to close this at this time.  Please feel free to open a DISCUSS thread on the dev list to continue the discussion.


Insertion sort in PHP

💥 Proposal
Insertion sort in PHP
Have you read the Contributing Guidelines on Pull Requests?
YES

/assign


Updating gulp-sass and consequently node-sass that is running errors

In the newer version of nodejs the library of node-sass is no longer available, so I update the package with a newer version of gulp-sass, The android and ios implementation is also instantiated.

Thanks,
we have to take a look to the versions conflict thing, we'll try to review this ASAP

Hi,
thanks for your contribution, unfortunately, with this version we still get errors when we setup the environment since the beginning.

Closing this issue, please review https://tracker.moodle.org/browse/MOBILE-1796


ads: envoy is sending DiscoveryRequest without TypeUrl set

Hi, I am using envoy with ADS. Occasionally I see DiscoveryRequest.TypeUrl (https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/discovery.proto) being empty. I also see requests coming in with the TypeUrl correctly set to one of Listener, Cluster, RouteConfiguration, Secret.
The DiscoveryRequest is pertaining to response_nonce in such cases.
Is it expected for the TypeUrl in the DiscoveryRequest to be empty? In what cases can this happen? How should ADS respond to such a request?
envoy  version: 3504d40f752eb5c20bc2883053547717bcb92fd8/1.14.1/Clean/RELEASE/BoringSSL

Looks like the DiscoveryRequest when the TypeUrl is empty is pertaining to response_nonce:
{"level":"debug","component":"envoy/ads","time":"2020-04-30T21:15:24Z","file":"grpc.go:26","message":"TypeUrl: , request: response_nonce:\"15882813242656433

@zuercher would you know why this would happen? I haven't been able to find this in the docs.


Use Zalando PostgreSQL database conventions

fullstop. currently does not follow our database conventions (as all our STUPS microservices do), check e.g. https://github.com/zalando-stups/pierone/blob/master/resources/db/migration/V1__Basic_schema.sql

For simplicity with Spring Boot + Hibernate, we agreed on keeping the "standard" naming scheme.


trang not found in make process

On Mac OS I get
Entering /mounted/lmh/ext/LaTeXMLsTeX
Running Makefile.PL
Configuring /mounted/lmh/ext/LaTeXMLsTeX ... Can't exec "type": No such file or directory at Makefile.PL line 14.

Trang is not found which could lead to a make failure.
You can ignore this message if you do not intend to change the schema.
See README for more info!

make: trang: Command not found
make: *** [LaTeXML.rng] Error 127
Generating a Unix-style Makefile
Writing Makefile for LaTeXML::Plugin::sTeX
Writing MYMETA.yml and MYMETA.json

but trang is installed in /usr/local/bin/trang.

The message you got comes from type which does not exist in the Debian distribution that we are using for lmh_docker so I added which to the checking as well. which does exist in Debian.
I think what we should really is to provide trang inside the docker image by default (see https://github.com/KWARC/localmh_docker/pull/29) because this checking mechanism won't have the access to the resources outside the docker. (this is the nature of having a docker) Even if the checking works, it would still don't know if we have trang installed on the host system or not.
The checking here is mainly for the developers using the plugin outside the docker so that they are informed about the need of trang if they would like to customize the scheme, and the detection mechanism does work outside docker now (being tested on both Mac and Ubuntu)

seems to be a duplicate of #116


Update blaze-http to 0.15.2

Updates org.http4s:blaze-http from 0.15.1 to 0.15.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.15.1).
You might want to review and update them manually.
website/jvm/src/hugo/content/changelog.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s", artifactId = "blaze-http" } ]

labels: library-update, semver-patch, old-version-remains

Too late, my robotic friend.


Building on MacOS: imgui_impl_opengl3

When building on macOS (10.15.7), I am running into this error from make:
CMake Error at CMakeLists.txt:188 (add_executable):
  Cannot find source file:

    libs/imgui/examples/imgui_impl_opengl3.cpp

However, that file does reside in `libs/imgui/backends/'.
What is the solution? Should I change the CMakeLists.txt ?

The solution to this issue should be same as the solution to the #148 ( https://github.com/dfranx/SHADERed/issues/148#issuecomment-736542915 ), I think.

Yes, seems to work with the libs pulled via git.
Suggestion: put these 3 command lines in the README.md

Great! Glad it works!
They already are in the README.md:

Oh, well, I skipped the Linux section. Suggestions: set a textual "pointer" in the macOS section to the Linux section.


add clickable prop to allow the app to define a flipable card

exposes the prop clickable to card view to allow the app to configure a flipable card

Thank you!!


Readd JUnit XML Serialization

And also probably a setting for where to store it

Resolved by 438510b6cb732e293132f86f1426d2632844b870

Resolved by 438510b6cb732e293132f86f1426d2632844b870


Show "What is a wallet?" explonation in the guest book example

When initializing the wallet selector in the options object pass also the following option (object):
walletSelectorUI: {
  description: "Please select a wallet to connect to this dapp:",
  explanation: `Wallets are used to send, receive, and store digital assets. There are different types of wallets.
              They can be an extension added to your browser, a hardware device plugged into your computer,
              web-based, or as an app on your phone.`,
}

Repository: https://github.com/amirsaran3/guest-book-example
Live Demo: https://amirsaran3.github.io/guest-book-example/
With this the collapsible wallet explanation and a custom description will be shown like in the below pic:

Sent the necessary code to Amir and confirmed that he added it to the options object on initialization of the wallet selector, since I did not have access to push.
When we initialize the wallet selector now it will look like this, we just added the walletSelectorUI option:
const near = await NearWalletSelector({
  wallets: ["nearwallet", "senderwallet", "ledgerwallet"],
  networkId: "testnet",
  theme: "light",
  contract: {
    address: nearConfig.contractName,
    viewMethods: ["getMessages"],
    changeMethods: ["addMessage"],
  },
  walletSelectorUI: {
    description: "Please select a wallet to connect to this dapp:",
    explanation: `Wallets are used to send, receive, and store digital assets. There are different types of wallets.
                They can be an extension added to your browser, a hardware device plugged into your computer,
                web-based, or as an app on your phone.`,
  }
});

After next deploy the changes will take effect:
Repository: https://github.com/amirsaran3/guest-book-example
Live Demo: https://amirsaran3.github.io/guest-book-example/

Since we have setup the guest book example inside the wallet-selector repo latest changes are in dev branch, for detailed info refer to the PR #69


pedersen commitments inside EVM for scalability and privacy

Motivation
So inside the snark its really expensive to use sha256 or other binary hash functions. So we want to use pedersen commitments where ever we can. But this means that the EVM and SNARK do not speak the same language. EVM can do sha256 hashes but snarks can do pedersen.
Status Quo
At the moment we end up doing a bunch of sha256 operations inside the snark which ends up being majority of the complexity inside the snark. We can do pedersen commitments insde the EVM but the gas costs are prohibative (~10000 gas)
It would be cool to have pre-compile for pedersen commitments for altbn128 and bls12-381 Precompile https://github.com/barryWhiteHat/baby_jubjub
This would help a bunch with our with our scalability via snarks work as it would reduce the size of our snark circuits and let us add more signatures in their place :)
It would also help with our anonymity work as having to use sha256 in the snark circuit means that users must spend ~1 minute per proof and are just not able to do this on mobile. We can again use pedersen commitments in the snark but the EVM not supporing this opperation makes our smart contract need to become expensive. Or charge ppl 10,000 gas extra per deposit.

Here is some python code for eddsa and pedersen commitments
https://github.com/HarryR/ethsnarks/blob/master/ethsnarks/pedersen.py
https://github.com/HarryR/ethsnarks/blob/master/ethsnarks/eddsa.py

I believe this would be superseded by a precompile for general elliptic curve math (https://ethereum-magicians.org/t/ewasm-precompile-for-general-elliptic-curve-math/2581). right?

Agree, closing


Builds fail to compile with node > 3 on travis

Likely related to a combination of nvm and node-gyp, but it only seems to happen with bcrypt.
Here is an example repo that only depends on the latest bcrypt.
Here is the verbose travis build log

I just searched existing issues. Sorry about this.


Move bom dependencies to outer pom

Move guava, protobuf and test dependencies from bom/pom.xml to pom.xml
Also fix: bigquery imported truth twice

PTAL @garrettjonesgoogle @pongad

I think we should do point 3 of https://github.com/GoogleCloudPlatform/google-cloud-java/issues/2781#issuecomment-369372684 as well, but that can be in a separate PR.

@garrettjonesgoogle Do you want to take a look?


feat(auth): allow configuration from a .env file

This is similar to the Vue change but Angular doesn't directly support dotenv in the build process, so I created a simple Node script that generates a code file.
Side note: I just remembered I will need to add a CUSTOMIZE.md file like I did for the Vue project.

LGTM


[Feature Request] Support shoppify emails

Add support for shipping emails from Shopify.
They seem to look like they come from<EMAIL_ADDRESS>Subject lines:
Your <item> Order <order number> is Confirmed! 🎉
Order <order number> confirmed
A shipment from order <order number> is on the way
Shipping update for order <order number>
Note that Shoppify has a PoS and I have an email for a purchase made in-person with the subject
Receipt for order <order number>
Let me know if theres any more information needed

Shoppify isn't a shipper are they?
Do they not use UPS/USPS/FedEx/etc ?

@firstof9 I noticed that for some websites (like Shopify, ebay, etc) I am not receiving a dedicated DHL/DPD/whatever mail, only a custom mail from the seller. Is there any way to deal with that?

Shoppify isn't a shipper are they? Do they not use UPS/USPS/FedEx/etc ?
Neither is a seller on Amazon, shipping with USPS.
These are basically the same, the Shopify emails contain the tracking number and status updates

I am not receiving a dedicated DHL/DPD/whatever mail, only a custom mail from the seller. Is there any way to deal with that?

I know for shippers like DHL you sign up to get notices from them when something is en-route to your address, similar to UPS.

Neither is a seller on Amazon who ships with USPS.

While true, Amazon does have their own delivery drivers as well,  in the US at least.

While true, Amazon does have their own delivery drivers as well, in the US at least.

I'm not referring to Prime sales. Amazon sellers can also sell and ship from their home/business just like Shopify stores. The emails operate the same in this case.

Correct, in which case you'd get a tracking email from USPS/UPS/FedEx (if you enabled the notifications for your shipping address).


Fix incorrect help message

The cargo clean --target command does not have a default setting, but the command-line help text says it does.

@dwijnand Do you object to merging this as-is, and then following up later with more documentation about how cargo clean works?  It might also be an opportunity to survey the deficiencies of cargo clean and sketch out some fixes to make it work better.

Sure, I'm always down for incremental improvements and eagerly landing changes.
@bors r+

:pushpin: Commit 26232c310221aaea5243ae6fbce3c652d326ffeb has been approved by dwijnand

:hourglass: Testing commit 26232c310221aaea5243ae6fbce3c652d326ffeb with merge 6022bbb7c272f25e72e099d3d15d9ab8831993b1...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: dwijnand
Pushing 6022bbb7c272f25e72e099d3d15d9ab8831993b1 to master...


The accuracy of the final acquired pose of MeshLoc

Hello, dear author! This work is very wonderful.
I tried to experiment with the pose of some images in the 12scens_kitchen file.
I found that the final meshloc obtained quaternions are basically the same as the true value (but the first W appears negative， XYZ is similar).
However, the position difference is large.
I tried to use d2net and LOFTER, and the final result is similar, with a big position gap.
Here is my parameter configuration,

what is wrong ?
Here are the quaternions obtained from the rotation matrix of pose.txt of frame-000000-colar.jpg

You are comparing poses that cannot be directly compared.
MeshLoc returns the camera pose as R, t, such that a 3D point p_w in world coordinates is mapped to a point p_c in camera coordinates as p_c = R * p_w + t.
The pose files provided by the 12 Scenes dataset store the pose as R^T, c, where c = -R^T * t is the camera position in world coordinates.


chore: 准备发布npm包的信息

配置changesets
修改各个包的package.json，增加必要信息

Codecov Report
Base: 64.61% // Head: 64.61% // No change to project coverage :thumbsup:

Coverage data is based on head (219d7f8) compared to base (3f18866).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #424   +/-   ##
=======================================
  Coverage   64.61%   64.61%
=======================================
  Files         105      105
  Lines        2962     2962
  Branches      370      370
=======================================
  Hits         1914     1914
  Misses       1002     1002
  Partials       46       46

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


v1.4 backports 2019-01-31

#6864 -- Test: Report a kubernetes summary to a single file. (@eloycoto)
#6860 -- operator: Pace kube-dns pod restarts to every 5 minutes (@tgraf)
#6857 -- Fix misc daemon issues (@aanm)
#6856 -- fqdn: Fix repeat UUID insertion (@raybejjani)
#6845 -- Enable cilium-health in ipvlan mode (@brb)
#6840 -- Nightly fixes (@eloycoto)
#6748 -- cilium, ipvlan: avoid tail call in fast path (@borkmann)
#6672 -- Add DNS Proxy upstream time histogram metric (@eloycoto)

Backport was clean.
Once this PR is merged, you can update the PR labels via:
$ for pr in 6864 6860 6857 6856 6845 6840 6748 6672; do contrib/backporting/set-labels.py $pr done 1.4; done

This change is

test-me-please

test-missed-k8s

test-docs-please


DOCS-12791-http-properties-kt

Adding new HTTP service system properties into HTTP Connector docs

Merge the PR in Mule runtime monthly release approximately Jan 4th 2022

Closing as new verified sign commits PR https://github.com/mulesoft/docs-connectors/pull/1800


Failure to Automatically Read and Save to Existing Excalidraw Canvas File After Reload

When saving an Excalidraw canvas file and reloading the webpage, the app fails to automatically read from the previously saved file.
After reloading, users cannot save changes to the existing file. Instead, they must save to a new file or manually reopen the existing one to continue working

Hello @MuhammadBilalEllahi , could you provide a video if possible I tried your steps but everything worked for me as expected.

https://github.com/user-attachments/assets/3bb491f8-0dc8-4391-8d0b-3457d691d688

Thanks
I have identified where the issue is in code will try to fix it


problems while static resources to get response from apps behind zuul

hi,Im new to zuul,I have an app behind zuul and eureka,in that app I have some static resources like index.html,and included jquery etc.in that html I have some ajax requests like /app to get some info,without zuul and eureka，that works fine.I visit my index.html like this :http://myAddr/index.html，and send ajax request to /app. now I put that app behind zuul(name it as myApp),so I visit http://zuulAddr/myApp/index.html to visit that page,and some static resources I also have to add the prefix "/myaddr" to match the zuul routes.and ,the "/app" also have to add the prefix to work fine. is there some way to avoid these prefix adding work? my project have actually a lot of resources and requests.I added server.context-path，but is does not work.if I set the context-path to "myApp",the address became http://zuulAddr/myApp/myApp/index.html,that is really wired.maybe I　missed some important config?

i have the same question

I had same issue in the past I did add the route for each static resource.


Add auto-generate samples for Media and Reservations

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Optimize use of db queries

Remove any duplicate queries where possible.

This has been fixed and will go in release 2.3


[FX-4591] Migrate Button component

FX-4591
Description
In this PR, we migrate main Button component to MUI Base and TailwindCSS
How to test

Use Temploy and Production to compare components

Development checks

[ ] Add changeset according to guidelines (if needed)
[ ] Read CONTRIBUTING.md and Component API principles
[ ] Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[x] Annotate all props in component with documentation
[ ] Create examples for component
[ ] Ensure that deployed demo has expected results and good examples
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[ ] Self reviewed
[ ] Covered with tests (visual tests included)

Breaking change

N/A codemod is created and showcased in the changeset
[ ] test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

Okay, I'm going to fix unit tests and happo/cypress screenshots after migrating the last button

About already migrated button: The only difference I can see right now are corners:

@toptal-anvil ping reviewers


Feature Request - Allow specifying layout slots as array in custom card list settings to keep order

I'm writing some code that generates custom card lists files, based on XML files for Cockatrice custom sets. I'm writing this code in Swift. Since Dictionaries in swift do not have order, encoding the layouts to a JSON string gives me inconsistent results, since the object keys are encoded in order based on the internal Swift dictionary, which is different each time it is encoded.
{
  "layouts" : {
    "Mythic" : {
      "slots" : {
        "Common" : 10,
        "Land" : 1,
        "Mythic" : 1,
        "Uncommon" : 3
      },
      "weight" : 1
    },
    "Rare" : {
      "slots" : {
        "Uncommon" : 3,
        "Rare" : 1,
        "Common" : 10,
        "Land" : 1
      },
      "weight" : 7
    }
  },
  "withReplacement" : true
}

I'd like the slots to be in a specific order, however, when drafting on Draftmancer (ie Land, Rare, Uncommon, Common). If we could specify the slots the slots as an array like this, and have that be respected when drafting, that would be great!
Something like this is what I would want to have be valid:
{
  "layouts" : {
    "Mythic" : {
      "slots" : [
        {
          "slot": "Land",
          "quantity": 1
        },
        {
          "slot": "Mythic",
          "quantity": 1
        },
        {
          "slot": "Uncommon",
          "quantity": 3
        },
        {
          "slot": "Common",
          "quantity": 10
        }
      ],
      "weight" : 1
    },
    "Rare" : {
      "slots" : [
        {
          "slot": "Land",
          "quantity": 1
        },
        {
          "slot": "Rare",
          "quantity": 1
        },
        {
          "slot": "Uncommon",
          "quantity": 3
        },
        {
          "slot": "Common",
          "quantity": 10
        }
      ],
      "weight" : 7
    }
  },
  "withReplacement" : true
}

Implemented in a92a240
I went with name and count to be more consistent with the rest of the settings:
"layouts": {
  "Normal" : {
    "weight": 3,
    "slots": [
      { "name": "Rare",     "count": 1},
      { "name": "Uncommon", "count": 3},
      { "name": "Common",   "count": 10}
    ]
  },
  "Lucky": {
    "weight": 1,
    "slots": [
      { "name": "Rare"     , "count" : 2},
      { "name": "Uncommon" , "count" : 3},
      { "name": "Common"   , "count" : 9}
    ]
  }
}

Awesome, thank you!


Should the alias parameter in the Path method be removed?

Privileged issue

[ ] I'm @tiangolo or he asked me directly to create an issue here.

Issue Content
This is my MRE code:
from __future__ import annotations

from typing import Annotated

import uvicorn
from fastapi import FastAPI, Path

app = FastAPI()

@app.get('/{item_id}')
async def async_root(item_id: Annotated[int, Path(title = 'Item ID', alias = 'xid')]):
    return {'item_id': item_id}

if __name__ == '__main__':
    uvicorn.run(app, host = '<IP_ADDRESS>', port = 18081)

and I got the swagger docs:
http://<IP_ADDRESS>:18081/docs#/default/async_root__item_id__get

Question:

Why is the content of the title field not displayed in the documentation?

The generated curl request is incorrect; the placeholder {item_id} has not been replaced with the value 123 for xid
3. When I try to manually send a curl request to access it, I still get an error:
curl http://<IP_ADDRESS>:18081/123
{"detail":[{"type":"missing","loc":["path","xid"],"msg":"Field required","input":null}]}

When I remove the alias field from the Path method, it works normally：

@app.get('/{item_id}')
async def async_root(item_id: Annotated[int, Path(title = 'Item ID')]):
    return {'item_id': item_id}

 curl http://<IP_ADDRESS>:18081/123
{"item_id":123}

the alias field description:

My Environment:
Python 3.12.4
FastAPI 0.115.0
macOS M2 Max 14.6.1
PyCharm 2024.2.3 (Professional Edition)

@bowenerchen I think alias is useful for passing a Python reserved keyword or similar as a path parameter (as noted in the FastAPI docs). You must pass an alias to a path operation decorator like this
@app.get("/{xid}") # <- here
async def async_root(item_id: Annotated[int, Path(alias="xid")]):
    return {"item_id": item_id}

After that everything works.
> curl http://<IP_ADDRESS>:18018/123
{"item_id":123}

Sorry if I missed your point.