Cannot recall programs or temperature

I am on version 8 now
And if i try to recall a program it doesn't start.
Also if i try to recall a temperature it won't start.
This is what i use
`

alias: 'Airco huiskamer aan'
trigger:
platform: state
entity_id: input_boolean.airco_huiskamer_koelen
to: 'on'
action:

service: hon.start_program
data:
program: Koelen beneden
target:
entity_id: climate.huiskamer
`

or this
`

alias: 'Airco huiskamer koelen'
trigger:
platform: state
entity_id: input_boolean.airco_huiskamer_koelen
to: 'on'
action:

service: hon.climate_set_echo_mode
data:
echo_mode: off
target:
entity_id: climate.huiskamer
service: climate.set_hvac_mode
data:
hvac_mode: Cool
target:
entity_id: climate.huiskamer
delay:
seconds: 2
service: climate.set_temperature
data:
temperature: 24
target:
entity_id: climate.huiskamer
service: input_boolean.turn_off
entity_id: input_boolean.verwarming
service: climate.turn_on
target:
entity_id: climate.huiskamer

`

Hi, these hon services aren't supported, you have to use the swtich.turn_off service.

Tnx! I used the other hon application before.
Now I use yours. How does the silent mode works? Also as switch?

Yes 🙂
You can see all supported switches in settings > Device & Services > Haier hOn

Thank you, found it. If I put silent mode it automatically switches back and didn’t work

Can you show me your device data

i have problems with the integration.
First it worked, but now it doesn't startup.
I also tried new version but doesn't startup again

Do you get any error message?

integration cannot be loaded and other time configuration failed

Can you check the messages in Settings -> System -> Logs ?

This is the problem, maybe you edited something manual or an update was interrupted 🤔
If you use hacs, delete the hon dir (/config/custom_components/hon/) and install it again with hacs.

i tried to delete it.
after that i installed new integrations.
but i cannot add it, because its not in the list
so strange!

oh i didnt deleted the dir, i try again

again not successful.
Error setting up entry<EMAIL_ADDRESS>for hon
22:35:27 – (FOUT) Haier hOn (aangepaste integratie) - bericht kwam voor het eerst om 22:34:14 en verschijnt 3 keer
hOn Authentication Error 1 401 - https://account2.hon-smarthome.com/setup/secur/RemoteAccessAuthorizationPage.apexp?source=CAAAAYjAxA2kMDAwMDAwMDAwMDAwMDAwAAAA9JF6rxdV5eVrEo1riAzJy-6d-qh8o_-JemKiYj50XhW7UJoTbZj24PmFOxd4ZKODLWjj56If6qP0DRP-1nMkCtB_dQFUKZoeCkptMjyzgY_B_Y7EnadJkBIL1todXrpTR1AjXpt8bqTU-Yh1vNxFrfW4N9hMIP91rlvYmoie8sRR-xfNiXIx9gr3d-UwZtZlhg2tXNG21wxtT2bk-iEjcxTHN1RnoY7o0Hubd6XceL_DOp_F8ozRLGcv5MenMVQzhh2z-aES4f_eARZV0GhIPjUjYF96mYAHQf2lyxMbhHazSg_HY3l_TaYKTgUiRKrNgDXmiv3pC0uSv44Rj41SHr83scEXbidnga4135t5386u2ZSyrOTel7sEjQhs6_iQ9ies84N-gi6eGTumPMIMk7t4tVJGAa0plJNCvTSwaH_dwDnXvbHI96jqxobETjExIWVAQzTYb9HJfQQ4rAFNCTjlHOP6lm9DMK4-MTuY4GWouc0T-MSELcNtQYBsTuh-H7wfxv3F1u24abVSwJ-Y_px90o_z9UgKuT-lb0koLyQeZY0ea5rFAir4C0u8fbfOSyNn-1f3QaOV2rMC1X1TpGcFoLslBrym9kEO7AaOP5DpRGBH-kivOM3wu4QLAfyDyS6HHKTGNxWy9zPTnd_Rjrfhvzt4G4J2UC6rwB27BpJcILxt_rL43wSsPTmZo4sevXnj68WVpor_afuuzmuej2hsLTOrpunoHnx3JeTuU&display=touch 2 302 - https://account2.hon-smarthome.com/s/login?display=touch&ec=302&inst=68&startURL=/setup/secur/RemoteAccessAuthorizationPage.apexp?source%3DCAAAAYjAxA2kMDAwMDAwMDAwMDAwMDAwAAAA9JF6rxdV5eVrEo1riAzJy-6d-qh8o-JemKiYj50XhW7UJoTbZj24PmFOxd4ZKODLWjj56If6qP0DRP-1nMkCtB_dQFUKZoeCkptMjyzgY_B_Y7EnadJkBIL1todXrpTR1AjXpt8bqTU-Yh1vNxFrfW4N9hMIP91rlvYmoie8sRR-xfNiXIx9gr3d-UwZtZlhg2tXNG21wxtT2bk-iEjcxTHN1RnoY7o0Hubd6XceL_DOp_F8ozRLGcv5MenMVQzhh2z-aES4f_eARZV0GhIPjUjYF96mYAHQf2lyxMbhHazSg_HY3l_TaYKTgUiRKrNgDXmiv3pC0uSv44Rj41SHr83scEXbidnga4135t5386u2ZSyrOTel7sEjQhs6_iQ9ies84N-gi6eGTumPMIMk7t4tVJGAa0plJNCvTSwaH_dwDnXvbHI96jqxobETjExIWVAQzTYb9HJfQQ4rAFNCTjlHOP6lm9DMK4-MTuY4GWouc0T-MSELcNtQYBsTuh-H7wfxv3F1u24abVSwJ-Y_px90o_z9UgKuT-lb0koLyQeZY0ea5rFAir4C0u8fbfOSyNn-1f3QaOV2rMC1X1TpGcFoLslBrym9kEO7AaOP5DpRGBH-kivOM3wu4QLAfyDyS6HHKTGNxWy9zPTnd_Rjrfhvzt4G4J2UC6rwB27BpJcILxt_rL43wSsPTmZo4sevXnj68WVpor_afuuzmuej2hsLTOrpunoHnx3JeTuU%26display%3Dtouch 3 301 - https://account2.hon-smarthome.com/s/login/?display=touch&ec=302&inst=68&startURL=/setup/secur/RemoteAccessAuthorizationPage.apexp?source%3DCAAAAYjAxA2kMDAwMDAwMDAwMDAwMDAwAAAA9JF6rxdV5eVrEo1riAzJy-6d-qh8o-JemKiYj50XhW7UJoTbZj24PmFOxd4ZKODLWjj56If6qP0DRP-1nMkCtB_dQFUKZoeCkptMjyzgY_B_Y7EnadJkBIL1todXrpTR1AjXpt8bqTU-Yh1vNxFrfW4N9hMIP91rlvYmoie8sRR-xfNiXIx9gr3d-UwZtZlhg2tXNG21wxtT2bk-iEjcxTHN1RnoY7o0Hubd6XceL_DOp_F8ozRLGcv5MenMVQzhh2z-aES4f_eARZV0GhIPjUjYF96mYAHQf2lyxMbhHazSg_HY3l_TaYKTgUiRKrNgDXmiv3pC0uSv44Rj41SHr83scEXbidnga4135t5386u2ZSyrOTel7sEjQhs6_iQ9ies84N-gi6eGTumPMIMk7t4tVJGAa0plJNCvTSwaH_dwDnXvbHI96jqxobETjExIWVAQzTYb9HJfQQ4rAFNCTjlHOP6lm9DMK4-MTuY4GWouc0T-MSELcNtQYBsTuh-H7wfxv3F1u24abVSwJ-Y_px90o_z9UgKuT-lb0koLyQeZY0ea5rFAir4C0u8fbfOSyNn-1f3QaOV2rMC1X1TpGcFoLslBrym9kEO7AaOP5DpRGBH-kivOM3wu4QLAfyDyS6HHKTGNxWy9zPTnd_Rjrfhvzt4G4J2UC6rwB27BpJcILxt_rL43wSsPTmZo4sevXnj68WVpor_afuuzmuej2hsLTOrpunoHnx3JeTuU%26display%3Dtouch 4 200 - https://account2.hon-smarthome.com/s/login/?language=en_US&display=touch&ec=302&inst=68&startURL=%2Fsetup%2Fsecur%2FRemoteAccessAuthorizationPage.apexp%3Fsource%3DCAAAAYjAxA2kMDAwMDAwMDAwMDAwMDAwAAAA9JF6rxdV5eVrEo1riAzJy-6d-qh8o-JemKiYj50XhW7UJoTbZj24PmFOxd4ZKODLWjj56If6qP0DRP-_1nMkCtB_dQFUKZoeCkptMjyzgY_B_Y7EnadJkBIL1todXrpTR1AjXpt8bqTU-Yh1vNxFrfW4N9hMIP91rlvYmoie8sRR-xfNiXIx9gr3d-UwZtZlhg2tXNG21wxtT2bk-iEjcxTHN1RnoY7o0Hubd6XceL_DOp_F8ozRLGcv5MenMVQzhh2z-aES4f_eARZV0GhIPjUjYF96mYAHQf2lyxMbhHazSg_HY3l_TaYKTgUiRKrNgDXmiv3pC0uSv44Rj41SHr83scEXbidnga4135t5386u2ZSyrOTel7sEjQhs6_iQ9ies84N-gi6eGTumPMIMk7t4tVJGAa0plJNCvTSwaH_dwDnXvbHI96jqxobETjExIWVAQzTYb9HJfQQ4rAFNCTjlHOP6lm9DMK4-MTuY4GWouc0T-MSELcNtQYBsTuh-H7wfxv3F1u24abVSwJ-Y_px90o_z9UgKuT-lb0koLyQeZY0ea5rFAir4C0u8fbfOSyNn-1f3QaOV2rMC1X1TpGcFoLslBrym9kEO7AaOP5DpRGBH-kivOM3wu4QLAfyDyS6HHKTGNxWy9zPTnd_Rjrfhvzt4G4J2UC6rwB27BpJcILxt_rL43wSsPTmZo4sevXnj68WVpor_afuuzmuej2hsLTOrpunoHnx3JeTuU%26display%3Dtouch&System=IoT_Mobile_App&RegistrationSubChannel=hOn 5 200 - https://account2.hon-smarthome.com/s/sfsites/aura?r=3&other.LightningLoginCustom.login=1 ERROR - 200 - https://account2.hon-smarthome.com/s/sfsites/aura?r=3&other.LightningLoginCustom.login=1 =============== Response =============== {"actions":[{"id":"79;a","state":"SUCCESS","returnValue":"Your login attempt has failed. Make sure the username and password are correct.","error":[]}],"context":{"mode":"PROD","app":"siteforce:loginApp2","contextPath":"/s/sfsites","pathPrefix":"","fwuid":"c1R3MUZhNldLUm1BS0plaUgwaDhnQWI4T1Q3UVpoR0gtemxDX3B4aTM3bVEyNDQuMjAuMS0yLjQxLjQ","mlr":1,"loaded":{"APPLICATION@markup://siteforce:loginApp2":"Izv9eREiUIuimW-V5PtbgQ"},"globalValueProviders":[{"type":"$Global","values":{"eswConfigDeveloperName":{"writable":true,"defaultValue":""},"isVoiceOver":{"writable":true,"defaultValue":false},"setupAppContextId":{"writable":true,"defaultValue":""},"density":{"writable":true,"defaultValue":""},"srcdoc":{"writable":false,"defaultValue":false},"appContextId":{"writable":true,"defaultValue":""},"dynamicTypeSize":{"writable":true,"defaultValue":""}}}],"enableAccessChecks":true,"apce":1,"dns":"c","lairn":[],"laerc":[],"lav":"58","mna":{"lightning":"interop"},"lff":{"ENABLE_MIXED_SHADOW_MODE":false,"ENABLE_LIGHT_GET_ROOT_NODE_PATCH":true,"DISABLE_LIGHT_DOM_UNSCOPED_CSS":false},"arse":1,"acaf":1,"services":["markup://lightning:configProvider","markup://force:salesforceScopedModuleResolver","markup://force:ldsEngineCreator","markup://instrumentation:locatorService"]},"perfSummary":{"version":"core","request":28,"actions":{"79;a":{"total":25,"db":2}},"actionsTotal":25,"overhead":0}} ========================================
22:35:27 – (FOUT) Haier hOn (aangepaste integratie) - bericht kwam voor het eerst om 22:34:14 en verschijnt 3 keer

So, the error message is "Your login attempt has failed. Make sure the username and password are correct". Can you double check that your login is correct? 🤔

i tried 4 times......

finally, i changed the password in the hon app. after this the integration is working.
now i can check the device settings

device info entity not available??

Example configuration.yaml entry
command_line:

binary_sensor:
command: "cat /proc/sys/net/ipv4/ip_forward"

data:
  additional_data:
  appliance:
    SK_Secondary: AC#selfClean#2022-01-04
    applianceId: xx-xx-xx-xx-xx-xx#2021-08-07T12:09:08Z
    applianceModelId: 340
    applianceStatus: 1
    applianceTypeId: 11
    applianceTypeName: AC
    attributes:
      acuVersion: 06.26.00
      chipset: 1
      dictionaryId: 180
      eppParserSet: 1
      fwLabel: iotfw_epp
      lang: it-IT
      uiVersion: 06.26.00
    brand: haier
    code: AAANW1E0000
    connectivity: wifi|ble
    eepromId: 41
    eepromName: no_eeprom
    enrollmentDate: 2021-08-07T12:09:08.452Z
    fwVersion: 5.12.0
    id: 340
    lastSelfClean: 2023-05-01T07:38:16.091Z
    lastSelfPurify: 2022-07-14T17:21:18.756Z
    lastUpdate: 2022-10-01T07:28:36Z
    macAddress: xx-xx-xx-xx-xx-xx
    modelName: AS35TADHRA-2
    nickName: Huiskamer
    purchaseDate: 2021-08-06T22:00:00.000Z
    sections:
      chatbot: True
      double_pairing_hidden: True
      epp_enabled: False
    series: tundra
    topics:
      publish:
      subscribe:
        - $aws/events/presence/disconnected/xx-xx-xx-xx-xx-xx
        - $aws/events/presence/connected/xx-xx-xx-xx-xx-xx
        - haier/things/xx-xx-xx-xx-xx-xx/event/appliancestatus/update
        - haier/things/xx-xx-xx-xx-xx-xx/event/discovery/update
    unitConfiguration: 1to1
  attributes:
    activity:
    commandHistory:
      command:
        ancillaryParameters:
        applianceOptions:
        applianceType: AC
        attributes:
          0: P
          1: R
          10: C
          11: .
          12: I
          13: O
          14: T
          15: _
          16: C
          17: O
          18: O
          19: L
          2: O
          3: G
          4: R
          5: A
          6: M
          7: S
          8: .
          9: A
          channel: BeMobile
          origin: scheduling
        commandName: stopProgram
        device:
          appVersion: 1.10.0
          mobileOs: android
          osVersion: 28
        macAddress: xx-xx-xx-xx-xx-xx
        parameters:
          10degreeHeatingStatus: 0
          ch2oCleaningStatus: 0
          cleaningTimeStatus: 0
          echoStatus: 0
          electricHeatingStatus: 0
          energySavePeriod: 15
          energySavingStatus: 0
          filterChangeStatusCloud: 0
          freshAirStatus: 0
          halfDegreeSettingStatus: 0
          healthMode: 0
          heatAccumulationStatus: 0
          humanSensingStatus: 0
          humidificationStatus: 0
          humiditySel: 30
          intelligenceStatus: 0
          lightStatus: 0
          lockStatus: 0
          machMode: 1
          muteStatus: 0
          onOffStatus: 0
          operationName: grSetDAC
          pm2p5CleaningStatus: 0
          pmvStatus: 0
          rapidMode: 0
          screenDisplayStatus: 0
          selfCleaning56Status: 0
          selfCleaningStatus: 0
          silentSleepStatus: 0
          specialMode: 0
          tempSel: 24.00
          tempUnit: 0
          voiceSignStatus: 0
          voiceStatus: 0
          windDirectionHorizontal: 0
          windDirectionVertical: 5
          windSensingStatus: 0
          windSpeed: 5
        programName: PROGRAMS.AC.IOT_COOL
        timestamp: 2023-06-14T21:01:22.360Z
        transactionId: xx-xx-xx-xx-xx-xx_2023-06-14T21:01:22.360Z
      timestampAccepted: 2023-06-14T21:01:39.8Z
      timestampExecuted: 2023-06-14T21:01:40.7Z
    lastConnEvent:
      category: CONNECTED
      instantTime: 2023-05-16T05:08:23Z
      macAddress: xx-xx-xx-xx-xx-xx
      timestampEvent:<PHONE_NUMBER>797
    parameters:
      10degreeHeatingStatus: 0
      acType: 0
      airQuality: 0
      ch2oCleaningStatus: 0
      ch2oValueIndoor: 0
      co2ValueIndoor: 0
      compressorCurrent: 51.10
      compressorFrequency: 0
      compressorStatus: 0
      debugEnabled: 0
      defrostStatus: 0
      echoStatus: 0
      electricHeatingStatus: 0
      electricHeatingStatusIndoor: 0
      energySavePeriod: 15
      energySavingStatus: 0
      errAckFlag: 0
      errors: 00
      expansionValveOpenDegree: 88
      fanStatusIndoor: 0
      fanStatusOutdoor: 2
      filterChangeStatusLocal: 0
      fourWayValveStatus: 2
      freshAirStatus: 0
      halfDegreeSettingStatus: 0
      healthMode: 0
      highTransRate: 1
      humanSensingStatus: 0
      humidificationStatus: 0
      humidityIndoor: 0
      humiditySel: 30
      intelligenceStatus: 0
      lightStatus: 0
      lockStatus: 0
      machMode: 1
      machineModeHK: 0
      muteStatus: 0
      onOffStatus: 0
      operationName:
      operationSource: 3
      pm2p5CleaningStatus: 0
      pm2p5LevelIndoor: 0
      pm2p5ValueIndoor: 0
      pm2p5ValueOutdoor: 0
      pmvStatus: 0
      power: 0
      rapidMode: 0
      screenDisplayStatus: 0
      selfCleaningStatus: 0
      sensingResult: 0
      silentSleepStatus: 0
      specialMode: 0
      statusSyncRate: 1440
      stdTransRate: 3600
      tempAirOutdoor: 20
      tempCoilerIndoor: 22.00
      tempCoilerOutdoor: -64
      tempDefrostOutdoor: 18
      tempInAirOutdoor: -64
      tempIndoor: 24.50
      tempOutdoor: 24.00
      tempSel: 24.00
      tempUnit: 0
      totalElectricityUsed: 0
      totalWorkTime: 0
      transMode: 0
      vocValueIndoor: 0
      windDirectionHorizontal: 0
      windDirectionVertical: 5
      windSpeed: 5
    resultCode: 0
  settings:
    ancillaryParameters:
      programRules: {'selfCleaningStatus': {'$installationType': {'1toN': {'typology': 'fixed', 'fixedValue': '0'}}}, 'selfCleaning56Status': {'$installationType': {'1to1': {'typology': 'fixed', 'fixedValue': '0'}, '1to2': {'typology': 'fixed', 'fixedValue': '0'}, '1toN': {'typology': 'fixed', 'fixedValue': '0'}}}}
    custom:
      category: setParameters
    parameters:
      10degreeHeatingStatus: 0
      ch2oCleaningStatus: 0
      cleaningTimeStatus: 0
      echoStatus: 0
      electricHeatingStatus: 0
      energySavePeriod: 15
      energySavingStatus: 0
      filterChangeStatusCloud: 0
      freshAirStatus: 0
      halfDegreeSettingStatus: 0
      healthMode: 0
      heatAccumulationStatus: 0
      humanSensingStatus: 0
      humidificationStatus: 0
      humiditySel: 30
      intelligenceStatus: 0
      lightStatus: 0
      lockStatus: 0
      machMode: 0
      muteStatus: 0
      onOffStatus: 1
      operationName: grSetDAC
      pm2p5CleaningStatus: 0
      pmvStatus: 0
      rapidMode: 0
      screenDisplayStatus: 1
      selfCleaning56Status: 0
      selfCleaningStatus: 0
      silentSleepStatus: 0
      specialMode: 0
      tempSel: 22
      tempUnit: 0
      voiceSignStatus: 0
      voiceStatus: 0
      windDirectionHorizontal: 0
      windDirectionVertical: 5
      windSensingStatus: 0
      windSpeed: 5
  startProgram:
    ancillaryParameters:
      programRules: {'selfCleaningStatus': {'$installationType': {'1toN': {'typology': 'fixed', 'fixedValue': '0'}}}, 'selfCleaning56Status': {'$installationType': {'1to1': {'typology': 'fixed', 'fixedValue': '0'}, '1to2': {'typology': 'fixed', 'fixedValue': '0'}, '1toN': {'typology': 'fixed', 'fixedValue': '0'}}}}
      remoteActionable: 1
      remoteVisible: 0
    custom:
      program: iot_simple_start
    parameters:
      10degreeHeatingStatus: 0
      ch2oCleaningStatus: 0
      cleaningTimeStatus: 0
      echoStatus: 0
      electricHeatingStatus: 0
      energySavePeriod: 15
      energySavingStatus: 0
      filterChangeStatusCloud: 0
      freshAirStatus: 0
      halfDegreeSettingStatus: 0
      healthMode: 0
      heatAccumulationStatus: 0
      humanSensingStatus: 0
      humidificationStatus: 0
      humiditySel: 30
      intelligenceStatus: 0
      lightStatus: 0
      lockStatus: 0
      machMode: 1
      muteStatus: 0
      onOffStatus: 1
      operationName: grSetDAC
      pm2p5CleaningStatus: 0
      pmvStatus: 0
      rapidMode: 0
      screenDisplayStatus: 1
      selfCleaning56Status: 0
      selfCleaningStatus: 0
      silentSleepStatus: 0
      specialMode: 0
      tempSel: 25
      tempUnit: 0
      voiceSignStatus: 0
      voiceStatus: 0
      windDirectionHorizontal: 0
      windDirectionVertical: 5
      windSensingStatus: 0
      windSpeed: 5
  statistics:
    mostUsedPrograms:
      - count: 1073
        prCode: None
        programName: PROGRAMS.AC.HOME_ASSISTANT
      - count: 102
        prCode: None
        programName: PROGRAMS.AC.IOT_COOL
      - count: 60
        prCode: None
        programName: PROGRAMS.AC.IOT_AUTO
      - count: 44
        prCode: None
        programName: PROGRAMS.AC.IOT_HEAT
      - count: 17
        prCode: None
        programName: PROGRAMS.AC.IOT_DRY
    mostUsedRecipes:
    programsCounter: 0
  stopProgram:
    parameters:
      10degreeHeatingStatus: 0
      ch2oCleaningStatus: 0
      cleaningTimeStatus: 0
      echoStatus: 0
      electricHeatingStatus: 0
      energySavePeriod: 15
      energySavingStatus: 0
      filterChangeStatusCloud: 0
      freshAirStatus: 0
      halfDegreeSettingStatus: 0
      healthMode: 0
      heatAccumulationStatus: 0
      humanSensingStatus: 0
      humidificationStatus: 0
      humiditySel: 30
      intelligenceStatus: 0
      lightStatus: 0
      lockStatus: 0
      machMode: 0
      muteStatus: 0
      onOffStatus: 0
      operationName: grSetDAC
      pm2p5CleaningStatus: 0
      pmvStatus: 0
      rapidMode: 0
      screenDisplayStatus: 1
      selfCleaning56Status: 0
      selfCleaningStatus: 0
      silentSleepStatus: 0
      specialMode: 0
      tempSel: 22
      tempUnit: 0
      voiceSignStatus: 0
      voiceStatus: 0
      windDirectionHorizontal: 0
      windDirectionVertical: 5
      windSensingStatus: 0
      windSpeed: 5
commands:
  settings:
    10degreeHeatingStatus:
      max: 1
      min: 0
      step: 1
    category:
      - setConfig
      - setParameters
    echoStatus:
      max: 1
      min: 0
      step: 1
    machMode:
      - 0
      - 1
      - 2
      - 4
      - 6
    muteStatus:
      max: 1
      min: 0
      step: 1
    rapidMode:
      max: 1
      min: 0
      step: 1
    screenDisplayStatus:
      max: 1
      min: 0
      step: 1
    selfCleaningStatus:
      max: 1
      min: 0
      step: 1
    silentSleepStatus:
      max: 1
      min: 0
      step: 1
    tempSel:
      max: 30
      min: 16
      step: 1
    windDirectionVertical:
      - 2
      - 4
      - 5
      - 6
      - 7
      - 8
    windSpeed:
      - 1
      - 2
      - 3
      - 5
  startProgram:
    10degreeHeatingStatus:
      max: 1
      min: 0
      step: 1
    echoStatus:
      max: 1
      min: 0
      step: 1
    ecoMode:
      max: 1
      min: 0
      step: 1
    machMode:
      - 0
      - 1
      - 2
      - 4
      - 6
    muteStatus:
      max: 1
      min: 0
      step: 1
    program:
      - Koelen beneden
      - Warmte beneden
      - iot_10_heating
      - iot_auto
      - iot_cool
      - iot_dry
      - iot_fan
      - iot_heat
      - iot_self_clean
      - iot_simple_start
    programFamily:
      - maintenance
      - health
      - maintenance_health
    rapidMode:
      max: 1
      min: 0
      step: 1
    remoteActionable:
      max: 1
      min: 0
      step: 1
    remoteVisible:
      max: 1
      min: 0
      step: 1
    screenDisplayStatus:
      max: 1
      min: 0
      step: 1
    selfCleaningStatus:
      max: 1
      min: 0
      step: 1
    silentSleepStatus:
      max: 1
      min: 0
      step: 1
    tempSel:
      max: 30
      min: 16
      step: 1
    windDirectionVertical:
      - 2
      - 4
      - 5
      - 6
      - 7
      - 8
    windSpeed:
      - 1
      - 2
      - 3
      - 5
  stopProgram:
    10degreeHeatingStatus:
      max: 1
      min: 0
      step: 1
    echoStatus:
      max: 1
      min: 0
      step: 1
    machMode:
      - 0
      - 1
      - 2
      - 4
      - 6
    muteStatus:
      max: 1
      min: 0
      step: 1
    rapidMode:
      max: 1
      min: 0
      step: 1
    screenDisplayStatus:
      max: 1
      min: 0
      step: 1
    selfCleaningStatus:
      max: 1
      min: 0
      step: 1
    silentSleepStatus:
      max: 1
      min: 0
      step: 1
    tempSel:
      max: 30
      min: 16
      step: 1
    windDirectionVertical:
      - 2
      - 4
      - 5
      - 6
      - 7
      - 8
    windSpeed:
      - 1
      - 2
      - 3
      - 5
rules:
  startProgram:
    ecoMode:
      1:
        machMode:
          1:
            tempSel: 26
            windDirectionVertical: 3
            windSpeed: 1
          4:
            tempSel: 20
            windDirectionVertical: 3
            windSpeed: 1
pyhOnVersion: 0.13.0

finally, i changed the password in the hon app. after this the integration is working. now i can check the device settings

Do you have special characters in your password? Would be interesting, maybe we have another bug there :thinking:

I don't see anything special for your device, mute and echo should work... do you get an error message in the logs?

finally, i changed the password in the hon app. after this the integration is working. now i can check the device settings

Do you have special characters in your password? Would be interesting, maybe we have another bug there 🤔

only thing is an @ and ! In password

I don't see anything special for your device, mute and echo should work... do you get an error message in the logs?

Did you see anything?
Also check out if it works since this change.

Updated to beta 8
Now there are some strange texts under buttons.
And cannot change temp after I turned them on

What does that mean? Can you provide a screenshot?

This is what happens.

finally, i changed the password in the hon app. after this the integration is working. now i can check the device settings

Do you have special characters in your password? Would be interesting, maybe we have another bug there 🤔

Hello. In my experience, the hOn password expired in 365 days. Yesterday was the second time that I need to login in hOn app and change it for a new password in last 2 years.
Maybe a suggestion with the integration is a way to change the login credentials. The only solution I found is delete the integration and reinstalling. Worked fine for my.
Thanks

This is what happens.

The programs can now be set as preset with the climate entity. I don't know this custom card and can't say if it's possible to hide these presets :thinking:

finally, i changed the password in the hon app. after this the integration is working. now i can check the device settings

Do you have special characters in your password? Would be interesting, maybe we have another bug there thinking

Hello. In my experience, the hOn password expired in 365 days. Yesterday was the second time that I need to login in hOn app and change it for a new password in last 2 years. Maybe a suggestion with the integration is a way to change the login credentials. The only solution I found is delete the integration and reinstalling. Worked fine for my.
Thanks

That's a good hint, thanks! I will add the possibility to reconfigure the integration and will check if it's possible to display a warning in this case.


Segmentation fault (core dumped)

Describe the bug
After the last update, Ferdi does not open by itself at the beginning session; then, I try to open it by the terminal and I got that bug:
❯ ferdi
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
[1]    2135 segmentation fault (core dumped)  ferdi

After trying it three times, Ferdi finally opens.
To Reproduce
Steps to reproduce the behavior:

Begin session in Manjaro Linux
Wait.
As Ferdi didn't open, open by yourself clicking in the button.
See how Ferdi tries to open but it closes itself immediately.
Go to the terminal an try to open Ferdi.
Get the error.
Try to open it some times more.
Finally, it will open.

I updated it by yay, I installed it by yay too.
Thanks.
Expected behavior

Screenshots

Desktop:

OS: [e.g. macOS, Windows 10 etc.]
Ferdi Version [e.g. 5.4.3]

Server Used: [e.g. https://api.getferdi.com]

Debug information: https://debug.getferdi.com/...
Additional context

I also similar error - core dump, when trying to login to Franz account

After several times, Ferdi stopped crashing and now I can use it

Related: #667
Try installing the binary package ferdi-bin, from AUR.

The binary package worked for me for a few hours, but after I rebooted it stopped working again

Installing the ferdi package (not the binary but the 5.5.0-2 package) from the AUR seems to have fixed it for now, let's see if it is consistent

It isn't, after a reboot it started crashing again

@obvionaoe

The binary package worked for me for a few hours, but after I rebooted it stopped working again

Strange, for me the binary is still stable. Rebooted a couple timies to be sure. I think you were on a slightly higher Manjaro kernel, but other that that idk:

Output of inxi -Sx
System:    Host: dell-laptop Kernel: 5.4.35-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.3.0
           Desktop: KDE Plasma 5.18.4 Distro: Manjaro Linux

Mine here:
System:    Host: joselito-asus-rog Kernel: 5.4.35-1-MANJARO x86_64 bits: 64 compiler: gcc
           v: 9.3.0 Desktop: Deepin 15.10.1 Distro: Manjaro Linux

Same experience here, different kernel and DE:
Host: ChanceBox Kernel: 5.5.18-3-MANJARO x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: KDE Plasma 5.18.4
           Distro: Manjaro Linux

If I remember, I'll try it later with an older kernel and see what happens.

Disabling systray seems to get ferdi not to segfault.
Going to .config/Ferdi/config/settings.json, then changing enableSystemTray to false made Ferdi open at least.

So, it seems like the problem is with the SystemTray.

These electron issues look like they might be related to this: https://github.com/electron/electron/issues/22137, https://github.com/electron/electron/issues/22215

I get the same issue:
$ inxi -Sx
System:    Host: laurin-pc Kernel: 5.6.11-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: KDE Plasma 5.18.5
           Distro: Manjaro Linux
$ ferdi
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
[1]    5198 segmentation fault (core dumped)  ferdi

and, like others, it works when disabling systray

For me, the ferdi 5.5.0-4 and ferdi-git AUR packages exit with segmentation fault, but the ferdi-bin 5.5.0-1 package (based on the Fedora RPM) works fine. So maybe the culprit is the electron 8.2.5-2 from Arch vs whatever Electron version is currently used for building the RPM.

Would it be sensible to revert the upgrade from Electron 8.1.1 to 8.2.3 done via https://github.com/getferdi/ferdi/pull/625?

@kytwb I don't think that's the correct course of action, because using an older version of Electron potentially introduces security vulnerabilities. Even then, the AUR packages are building Ferdi with the Electron installed on the system, which would likely be the latest version.
Probably it's better to work around the issue until it's fixed in upstream Electron. I gather from the Zulip commit that that the crash is caused by creating a Tray icon without setting its context menu immediately, although as of now I understand neither the Zulip or the Ferdi codebases well enough to grok why that's the case.

This can probably be closed, right?

My system now runs Electron v9.1.0 and I reinstalled the AUR ferdi (5.5.0-7), I have not experienced any crashes/segfaults.

I rebuilted ferdi modifying the AUR PKGBUILD to go back to native electron (9.1.0) and it seems the segfault problem is indeed solved.
Unrelated but as a piece of information, you might want to save some time and apply the patch by @schinfo for the stuck loading screen bug that still affects electron9, no noticeable problems after that.

I am having this issue on NixOS.


Code action & diagnostic jump

Describe the bug
When there is only one error/warning message with a codeaction, invoking :Lspsaga diagnostic_jump will cause this bug.
https://user-images.githubusercontent.com/94868861/213698004-c14d6dd7-1f9b-4c3d-8a0b-454644785ad6.mp4
Steps to reproduce
$ nvim main.c
declare a variable
use this variable, but make a typo so that clangd provides a code action for it.
make sure there is only one error/warning in the file.
Expected behavior
Don't spawn multiple code action messages
Neovim version (nvim -v)
0.8.2 stable
lspsaga commit
last commit
Terminal name/version
powershell

sorry I can't reproduce i tried in nvim 0.8.2  and nvim 0.9 both works fine. please try use a min config to reproduce.

Oh I see.  My mistake


No hostname resolve timeout

Since there is no SimplePing instance is cached, any ping call starts with hostname resolving. In a very bad networks (I've tested on Network Link Conditioner with 30% packet loss) there might be pretty big lag between the function call an actual ip address resolved by SimplePing.
Right now I had to workaround it with my own timeout, but it would be much better, if PlainPing could do this kind a stuff, since it declares a timeout ability.
Also, it would be much more effective to cache a resolved ip address (with some cache-control policies, of course), or, at least, return it into a completion, so a caller could use it to perform second ping slightly faster.

Since there is no SimplePing instance is cached, any ping call starts with hostname resolving. In a very bad networks (I've tested on Network Link Conditioner with 30% packet loss) there might be pretty big lag between the function call an actual ip address resolved by SimplePing.
Right now I had to workaround it with my own timeout, but it would be much better, if PlainPing could do this kind a stuff, since it declares a timeout ability.
Also, it would be much more effective to cache a resolved ip address (with some cache-control policies, of course), or, at least, return it into a completion, so a caller could use it to perform second ping slightly faster.

Hi, Sega
Could you share how u fix the bid-lag problem?
I appreciate it!

I made my timeout like this:
var timeout: (() -> Void)? = {
    debugPrint("own timeout")
}
DispatchQueue.main.asyncAfter(deadline: .now.advanced(by: .seconds(1))) {
    timeout?()
}
PlainPing.ping(address, withTimeout: 0.95) { (estimatedTime, err, resolvedIp) in
    timeout = nil
    debugPrint(estimatedTime, err, resolvedIp)
}


Lace wallet stuck on loading with rotating circle. DevTools - Console : Failed to initialize wallet

I added a couple of wallets to Lace using the 24 word daedalus pass phrases.
For a couple of days they were visible without issue. Now since a couple of days I do not see the wallets anymore, and lace is stuck on loading.
Looking at the logs I see in the Chrome Devtools, Consols:
[BackgroundMessenger(wallet-api-lace)] connected
background.js:106 Failed to initialize wallet manager InvalidArgumentError: Invalid argument 'walletId': Wallet 701cfeb92d12211da38052a7a4b42a3f not found
at WalletManager.activate (background.js:122:246587)
Any ideas or suggestions?

Contact the Support page to resolve your request.
Note: You can also initiate a chat with the live agent on the chat button to get more information about your request via Live Chat
@wouterpattje

@wouterpattje Thanks for posting the issue.
Your query would be best dealt with by the support team.
Please see the link below to our dedicated support line:
Support : Help Center
Note: Click on the live chat icon at the bottom corner of the page to start a conversation

reinstalled the extension, reentered the passphrase, now all works again, Seems to have broken during update from 1.14 to 1.15.


[cli] allow specify OT executable when adding nodes

This PR allows users to specify a different OT executable when adding nodes instead of the default executable configured by -ot-cli <executable>.

@simonlingoogle , please help resolve conflict.

@simonlingoogle , please help resolve conflict.

resolved


Customizing the primary color

The various components use a hard-coded blue color, it would be nice to make this customizable.
Describe the solution you'd like
Defining a primary color variable and using this instead of blue would allow the primary color to be overridden on a per-project basis. Its default values can still be set to blue to make this change transparent to the user.
Describe alternatives you've considered
Manually overriding the generated CSS is out of the question, what I'm doing right now is setting blue to my desired color but this prevents from using blue elsewhere in the code.
Additional context
This is similar to what DaisyUI does.

Hey @lewebsimple,
This is something that we've been exploring the past few weeks, but we're still not 100% decided on this aspect.
The advantage is quite obvious, that per project base it is much easier to change the primary/secondary/tertiary colors, however, it will mean that we'll have to introduce a class that is not available with a default Tailwind configuration.
We will do this change if this request will have enough traction and demand.


add galera_package_parameter, so we can ensure version on galera package

Hello,
at least on my platform (Ubuntu and Percona), MySQL and Galera packages have different versioning :
[root@machine ~  ]# apt-cache policy percona-xtradb-cluster-common-5.6
percona-xtradb-cluster-common-5.6:
  Installed: 5.6.36-26.20-1.xenial
  Candidate: 5.6.37-26.21-3.xenial
  Version table:
     5.6.37-26.21-3.xenial 500
        500 http://apt/stable xenial/percona amd64 Packages
 *** 5.6.36-26.20-1.xenial 100
        100 /var/lib/dpkg/status
[root@machine ~  ]# apt-cache policy percona-xtradb-cluster-galera-3.x
percona-xtradb-cluster-galera-3.x:
  Installed: 3.20-4.xenial
  Candidate: 3.21-3.xenial
  Version table:
     3.21-3.xenial 500
        500 http://apt/stable xenial/percona amd64 Packages
 *** 3.20-4.xenial 100
        100 /var/lib/dpkg/status

It should be useful so one can do version lock even on galera package.
Does this work make sense and can be merged?
Thanks

@arteal Thanks for your contribution! As to wether this makes sense or not: I'm not certain yet. Since it does not break anything and is useful for you, I've merged it...


following the IEEE printf specification

previously, the case of %i wasn't working because options:NSRegularExpressionSearch was missing for the second part of the expression.
there are actually more integer specifiers than just d and i, there are also o, u, x and c and their uppercase counterparts.
(.*) was too greedy as it would capture float specifiers, so if the format was %f dogecoins it would have a match. This is solved by excluding the float specifiers f, e, g, a and their uppercase counterparts.

More info in my Stack Overflow answer: https://stackoverflow.com/questions/52332747/what-are-the-supported-swift-string-format-specifiers

Looks great! 👍


Add unit tests for usePodContainers

Closes: https://issues.redhat.com/browse/RHOAIENG-4051
Description

Adds unit tests for usePodContainers.ts

How Has This Been Tested?

Run npm run test
Test Impact

Request review criteria:

Self checklist (all need to be checked):

[X] The developer has manually tested the changes and verified that the changes work
[X] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

Alternatively, when it comes to wrapping functions, you could have also mocked out usePod and asserted it was called with the expected values and then assert that the result of usePodContainers is dependent on the result of usePod.

/lgtm
/approve


Change ILockedFrameBuffer.Dpi to Vector.

ILockedFrameBuffer.Dpi was a Size but it would make more sense as a Vector because Size * Vector produces a Size whereas a Size * Size would produce a Size3D if that type existed.
Fixes #997.

That breaks binary compatibility for no particular reason. It will complicate the development of out-of-main-source-tree interop packages, since they won't be compatible with nuget release and nightly builds at the same time. Can we leave that interface alone until we are ready to release 0.6?
Other than that looks good.

Yeah, sure - I guess we need to work out how to handle patch versus minor version branching. I usually would use master as the unstable/API-breakage branch and a 0.5 branch for patch releases, but it sounds like you're wanting to continue working on the MonoMac backend from CI builds, is that right? In that case, we can either a) leave this as PR until we're ready to release, or b) merge this to a 0.6 branch now, and merge from master to 0.6 periodically/before release.


add X-Mobile-Advertising-Id header

Add mobile advertising id header.

@hafizh Thanks for suggesting. We have to talk in our next API Guild meeting  about this suggestion. Can you give more argumentation here, why and what you need this for?

This is a header Apps pass for all requests, that also all underlying dependencies accept and pass to nakadi events, tracking or recommentation services. So, @bocytko suggested we add it here, so we don't have to align on the correct naming, with every team expecting it and standardize this.

@hafizh Can you join our guild meeting to elaborate on this topic? I send you an invite.

@bocytko can you say something to this issue? Otherwise we will close this issue.

@ruiaraujo can you help here with the description of the header (maybe you have it already in the FSA or skipper)?
@tkrop are you refusing to accept this header altogether or are your just unsatisfied with the description?

@bocytko We do not refuse generally. But, because we discourage the use of proprietary headers except for one well defined use case described in our Properietary Headers Section, we expect the requirements around it to be explained. Currently, we can not decide from the PR whether this X-Advertising-ID is matching our use case for a Proprietary Header or whether it should be modeled as query/path or body parameter.
It would help if @ruiaraujo, @hafizh,  or you can join our next API guild meeting to explain the usage pattern and give more context.

@tkrop How can we get an invite?
@bocytko We are not handling it yet but we will.

@ruiaraujo done.

@hafizh @ruiaraujo As you remember, we discussed this PR in Guild meeting on 06.11. We felt that clearer definition of use cases, format, semantics and client / server obligations is needed to standardize the "x-Advertising-id' in the Guidelines.
Some more concrete questions:

How does the  "x-Advertising-id" is related to the (privacy regulation compliant) IDFA (Apple IDentifier For mobile Advertising) for iOS and the GAID (Google mobile Advertising IDentifier) for Android?
Is it simply a placeholder for either the IDFA or GAID depending on the mobile app platform? If yes, and make it clear in the definition (incl. references to format definition etc.)
It is supposed to be only provided by customer facing mobile apps communicating with online services, is it? If yes, we should call it "x-Mobile-Advertising-id'.
Is it really a pass through parameter that should be supported by all mobile called backend services including its called services (either via APIs or events)?

Will you provide a PR update that provides a clearer definition and explicit statements around the questions above? Otherwise we should close the PR. Thank you!

@tfrauenstein Thank you for taking your time on this. The main take away from the Guild meeting for me was to find out if this header/id is something that also applies for web. If so to come up and align on a more generic naming and semantics. However, this turned out to be challenging since a lot of teams needs to be involved in this. Also looking into it more we didn't see it as applicable for web.
To answer your questions:

How does the "x-Advertising-id" is related to the (privacy regulation compliant) IDFA (Apple IDentifier For mobile Advertising) for iOS and the GAID (Google mobile Advertising IDentifier) for Android?
Is it simply a placeholder for either the IDFA or GAID depending on the mobile app platform? If yes, and make it clear in the definition (incl. references to format definition etc.)

Yes, it is a placeholder for IDFA for iOS and GAID for Android. Will update description.

It is supposed to be only provided by customer facing mobile apps communicating with online services, is it? If yes, we should call it "x-Mobile-Advertising-id'.

That sounds reasonable. Will update.

Is it really a pass through parameter that should be supported by all mobile called backend services including its called services (either via APIs or events)?

In a way, yes! But in general it is an optional parameter. The apps can always send it when available. Weather the backend supports it or not depends on their use cases. If they provide such features that are linked to this parameter or not.
I will try to articulate this into the description as well.

:+1:

:+1:

@hafizh thx -- basically looks fine, however I proposed concrete editorial update

👍

:+1:


CSRF token validation fails in Gii

What steps will reproduce the problem?

upgrade Yii2 to v2.0.12
delete cookies
Try to create a new controller, model etc. in Gii
Fill in form and click 'Preview'

What is the expected result?
Preview page should appear
What do you get instead?
Bad Request (# 400)
Unable to verify your data submission
Additional info
As a temporary workaround, you can disable CSRF validation in config:
$config = [
    'components' => [
        'request' => [
            // ...
            'enableCsrfValidation' => false
            // ...
    ]
    // ...
];

Also, if you downgrade to 2.0.11, then use Gii (e.g. click 'Preview'), then upgrade to 2.0.12, you can continue using Gii until you delete the cookies.

Q
A

Yii version
2.0.12

PHP version
5.6.30

Operating system
Linux (CentOS 7)

Please try with code from master branch.

@samdark Yes, it works with code from master. Thanks!


Color Picker opens on Shift+C

I have color picker set to open on Win + Shift + C and it comes up as I'm typing when I type Shift + C.
It happens on 2 separate installs on my home and work PC.

Fixed with #6044 and will be inside 0.21


Link to heading in glossary

We have some rather extensive glossary entries, so we would like to link to a page such as:
/glossary/contest#computerspieler

Now of course I can link to this: [Wettkampfsystem>Computerspieler](/glossary/contest#computerspieler)
but I think :t[Wettkampfsystem>Computerspieler]{#contest#computerspieler} would be more elegant.
Or maybe we are misusing the glossary and the content should actually be on an own page linked from the glossary entry,
let me know what you thnk :)

I personally though of the glossary as a list of definitions, so shorter texts. But I see your use-case.
I think the term directive should be extended to:
:t[A Term]{#term anchor="heading2"}

hm, that seems like unnecessary new syntax. Why not remove the hashtag from the glossary term and simply do it like this?
 :t[A Term]{term#heading2}

Because I decided to extend markdown with directives: https://github.com/remarkjs/remark-directive
:t is short for term. But maybe :g would be better.

I have implemented it in 7e95234c0b859314e0fd38521e238088e5e7ba1c and documented it here: https://hyperbook.openpatch.org/elements/glossary


IE11 image not loading

Hi,
I use below code and image is not loading on IE11.
<img src="images/blank.gif" data-srcset="images/work/qe-sm.jpg 500w, images/work/qe.jpg 1024w" class="lazyload" alt="qe" />

It's work if I use data-src and image loading perfectly fine. But I want to use two different version image for mobile and desktop.
Thanks in advance for help.

You might need to use a polyfill or add a data-src as fallback. Read here: https://github.com/aFarkas/lazysizes/blob/gh-pages/README.md#about-responsive-image-support-picture-andor-srcset

Thank you so much.
I use "plugins/respimg/ls.respimg.min.js" and it's working.
I like also idea about use fallback "data-src" it's work great.


Swap useSyncExternalStore shim behavior and update React deps

This PR:

Updates all React-related dependencies to React 18 final
Updates React Testing Library
Swaps the shim behavior so that the primary entry point now uses the useSyncExternalStore shim behavior as the default
Changes the old "/compat" entry point so that it is now "/next" and imports uSES directly from React without using the shim
Updates the Jest test setup to test all three scenarios (main entry + React 18, main entry + React 17, next entry + React 18)
Adds TS 4.6 to the TS test matrix

Just did a quick bundle size comparison of React-Redux 7.2.8, 8.0-beta.3 (with no uSES shim), and a build from this branch (with uSES shim).  The setup is a Vite app with React 18 and RTK 1.8.1, and a store with a basic counter slice and <Counter> component.
As best as I can tell from source-map-explorer, the vendor chunk sizes (including all of React, ReactDOM, RTK, and Immer) are:

7.2.8: 167.33K
8.0-b3: 167.21K
8.0-b4: 167.99K

In other words:

8.0-b3 is 120b smaller than 7.x, minified
8.0-b4 is 600b larger than 7.x, minified

But, that 600 bytes gets us compat with React 16.8/17, and makes it possible for people to easily upgrade to React-Redux v8 even if they aren't using React 18 yet.  It also ensures compat with React Native, which won't support React 18 until the "New Architecture" is fully released:
https://reactnative.dev/blog/2022/03/30/version-068#opting-in-to-the-new-architecture
So, that slight increase in bundle size is well worth it.
Also, users who are on React 18 can alias the "/next" entry point and drop the shim from their bundle.


Fixes the azure account pane location

https://github.com/microsoft/azuredatastudio/issues/11172

Coverage remained the same at 36.02% when pulling 5fddfbc254330bbcb2d2185f853df5d1e9c1cfaa on amir/fix/11172 into 0043a7f93ba500bc59c042e1476f1e7927efb1da on main.


Relax interface for bpError in the Prometheus middlewares

Right now we expect the user to have the same definition of baseplate.thrift than we do but nothing enforces it. In the case of the Prometheus middleware this leads to us not recognizing an error as being a Baseplate.Error and therefore not adding the labels for the error code.
This PR introduces a relaxed interface only to be used by the prometheus middleware to ensure that they will identity a Baseplate.Error as such regardless of past or future changes to the baseplate.thrift file.

flaky test ? It passes locally and appears unrelated to the change here

flaky test ? It passes locally and appears unrelated to the change here

looks so. https://github.com/reddit/baseplate.go/pull/487

Could you please also change IDLExceptionSuppressor and BaseplateErrorFilter to use baseplateErrorCode instead of baseplateError.

I don't have merge permission in here so I'll need one of you to merge it for me if that's ok


Present only with real time update

The current state of present only is low, does not have real time update.
Added real time update, added disabled on slider for css styling on demand

Sorry but I don't understand what it is. Could you provided an example.
Moreover, you have changed the indentation so all the file is modified.Could you please modify your PR to only show what you have changed?

Closing as no update for more than a month.


Hello. What is it?

The following assertion was thrown building FutureBuilder(dirty, state: _FutureBuilderState#a9c6c):
setState() or markNeedsBuild() called during build.
This GetBuilder widget cannot be marked as needing to build because the framework is already in the process of building widgets.  A widget can be marked as needing to be built during the build phase only if one of its ancestors is currently building. This exception is allowed because the framework builds parent widgets before children, which means a dirty descendant will always be built. Otherwise, the framework might not visit this widget during this build phase.
The widget on which setState() or markNeedsBuild() was called was: GetBuilder
state: _GetBuilderState#ce1fc
The widget which was currently being built when the offending call was made was: FutureBuilder
dirty
state: _FutureBuilderState#a9c6c
The relevant error-causing widget was:
FutureBuilder file:///Users/alexander/AndroidStudioProjects/migrant_app/lib/chat/chat_room.dart:95:22
When the exception was thrown, this was the stack:
#0      Element.markNeedsBuild. (package:flutter/src/widgets/framework.dart:4318:11)
#1      Element.markNeedsBuild (package:flutter/src/widgets/framework.dart:4333:6)
#2      State.setState (package:flutter/src/widgets/framework.dart:1289:15)
#3      GetStateUpdaterMixin.getUpdate (package:get/get_state_manager/src/simple/get_state.dart:22:18)
#4      ListNotifier.refresh (package:get/get_state_manager/src/simple/list_notifier.dart:22:14)
...
════════════════════════════════════════════════════════════════════════════════════════════════════
════════ Exception caught by rendering library ═════════════════════════════════════════════════════
A RenderFlex overflowed by 99650 pixels on the right.
The relevant error-causing widget was:
AppBar file:///Users/alexander/AndroidStudioProjects/migrant_app/lib/chat/chat_room.dart:73:15
════════════════════════════════════════════════════════════════════════════════════════════════════
[GETX] GOING TO ROUTE /ProfileCommon
I/flutter (12712): null
════════ Exception caught by widgets library ═══════════════════════════════════════════════════════
The following assertion was thrown building FutureBuilder(dirty, state: _FutureBuilderState#6dce6):
setState() or markNeedsBuild() called during build.
This GetBuilder widget cannot be marked as needing to build because the framework is already in the process of building widgets.  A widget can be marked as needing to be built during the build phase only if one of its ancestors is currently building. This exception is allowed because the framework builds parent widgets before children, which means a dirty descendant will always be built. Otherwise, the framework might not visit this widget during this build phase.
The widget on which setState() or markNeedsBuild() was called was: GetBuilder
state: _GetBuilderState#ce1fc
The widget which was currently being built when the offending call was made was: FutureBuilder
dirty
state: _FutureBuilderState#6dce6
The relevant error-causing widget was:
FutureBuilder file:///Users/alexander/AndroidStudioProjects/migrant_app/lib/common_profile/profile_user_widget_common.dart:40:12
When the exception was thrown, this was the stack:
#0      Element.markNeedsBuild. (package:flutter/src/widgets/framework.dart:4318:11)
#1      Element.markNeedsBuild (package:flutter/src/widgets/framework.dart:4333:6)
#2      State.setState (package:flutter/src/widgets/framework.dart:1289:15)
#3      GetStateUpdaterMixin.getUpdate (package:get/get_state_manager/src/simple/get_state.dart:22:18)
#4      ListNotifier.refresh (package:get/get_state_manager/src/simple/list_notifier.dart:22:14)
...

It means that you are calling the build method before it is completed.
This only occurs if you perform things that are considered bad practices, such as logic within the build method.
Builder methods must be pure, you must not call functions or perform setters from it.
This is not related to Getx, besides being a question, something that is not allowed in this space, therefore, I am closing this.


jestPuppeteer.debug() broken if stdin is not a TTY

On my windows system w/ cygwin and conemu, jestPuppeteer.debug() results in this error:
TypeError: stdin.setRawMode is not a function
  at resolve (node_modules/jest-environment-puppeteer/lib/PuppeteerEnvironment.js:98:19)
  at Object.debug (node_modules/jest-environment-puppeteer/lib/PuppeteerEnvironment.js:84:16)

This appears to be related:
https://github.com/nodejs/node-v0.x-archive/issues/8204

I'm seeing a similar issue, @DavidJRobertson did you ever find a workaround? I'm on macOS 10.14.3 running node 8.9.4.

Due to the fact that this fails, I've been using other methods to debug like setting headless: false and calling jest.setTimeout which work ok for debugging but cause tests to fail that normally pass when it is running headless. I'm assume changing the headless option shouldn't cause the non-deterministic results but maybe I'm wrong.
@neoziro before I file separate issues, are those things to be expected? Does jestPuppeteer.debug() account for a lot of edge cases? If that's the case, I'll probably wait for this to be resolved before filing anything else.
Thanks for this package btw, aside from some minor debugging hiccups jest and jest-puppeteer have been pretty easy (and enjoyable) to figure out and start using.

Ok here's some updates...
I don't get the error in the OP if headless or devtools (or both) are set:
jest-puppeteer.config.js
module.exports = {
    launch: {
        headless: false,
        devtools: true
    }
}

Using the approach from this comment was also the only thing that made jestPuppeteer.debug() work for me. Obviously #106 is somewhat related to this one.
Still seeing some other weirdness but maybe this issue can be closed by documenting the need for headless: false or devtools: true.

Edited the above comment, it seems both or at least devtools, is required.

The documentation mentions how to extend PuppeteerEnvironment.
Adding tty to the environment resolved this issue for me:
const PuppeteerEnvironment = require('jest-environment-puppeteer')
const tty = require('tty'); // added this

class CustomEnvironment extends PuppeteerEnvironment {
  async setup() {
    await super.setup()
  }

  async teardown() {
    await super.teardown();
  }
}

module.exports = CustomEnvironment

Stale, feel free to open a new issue if you have this problem.


SBOL2 and SBOL3 should both be supported  Namely, we should be able to see the HTML formatted definitions for terms in SBOL2 and SBOL3 via the SBOL Ontology

https://sbols.org/v2#ComponentDefinition - takes you to definition
https://sbols.org/v3#Component - takes you to RDF rather than definition
Need help from @goksel


No openai?

Can this be run without openai by using localai?

Yes. We have basic support, but needs a few local lines of code changed (Model IDs).
There's a PR coming up now for more.

See https://github.com/enricoros/big-agi/pull/112 .

So I built and tested it but it still wants the openai api key. Also the local model doesn't appear in the drop down.

Watch this branch: https://github.com/enricoros/big-agi/compare/main...feaure-model-sources
there are huge changes coming, with regard to supporting multiple models. It's a big overhaul.


bugfix: WebsiteRedirectLocation header response

Reopened old PR #1208, now with bert-e.

Hello giacomoguiulfo,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get
information on this process.
Status report is not available.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

2 peers

Integration data created
I have created the integration data for the additional destination branches.

this pull request will merge bugfix/S3C-1396-website-redirect-header-response into
development/6.4
w/7.4/bugfix/S3C-1396-website-redirect-header-response will be merged into development/7.4 (pull request #1364)
w/8.0/bugfix/S3C-1396-website-redirect-header-response will be merged into development/8.0 (pull request #1365)

Follow integration pull requests if you would like to be notified of
build statuses by email.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

2 peers

@bert-e wait

@giacomoguiulfo  I changed the base to development/6.4 as it's a bugfix that's relevant to an older branch. Can you rebase your branch?

Oops, targeted 6.4 instead of 8.0. Closing this.

Oh, GitHub allows retargeting. Too late 😔

@rahulreddy Just saw this comment. My bad, I closed this PR thinking it had a bad target, and I didn't know Github allowed retargeting. Reopened in #1366 targeting development/6.4 with everything properly rebased.


Added guzzle support

Moved adapter configuration to AdapterCompilerPass to avoid exceptions if buzz or guzzle dependencies are not present.

Cool, thanks :)

Could you be so kind to create a new tag?

https://github.com/henrikbjorn/HBStampieBundle/releases/tag/1.0.0 here you go :)

@stof good catch, thanks. i'll push a PR next week.


Feedback on reqwest dependency

Hey HVM authors. Awesome project. We've been porting it to Cosmopolitan Libc so it can run as an Actually Portable Executable.
I'm writing to bring to your attention that the only difficulties we encountered were due to a dependency on the "reqwest" library, which depends on non-portable i/o interfaces and schleps in 60 dependencies. We were able to successfully work around this on our end (see our fork in https://github.com/ahgamut/HVM/tree/cosmopolitan) so we require no action on your part, but I'd suggest that the dependency be reconsidered regardless, since it's only needed by this project on a single line that performs a simple HTTP GET request. Perhaps something more standard and leaner?
Thanks for the great work!
cc: @ahgamut

Hey HVM authors. Awesome project. We've been porting it to Cosmopolitan Libc so it can run as an Actually Portable Executable.
I'm writing to bring to your attention that the only difficulties we encountered were due to a dependency on the "reqwest" library, which depends on non-portable i/o interfaces and schleps in 60 dependencies. We were able to successfully work around this on our end (see our fork in ahgamut/HVM@cosmopolitan) so we require no action on your part, but I'd suggest that the dependency be reconsidered regardless, since it's only needed by this project on a single line that performs a simple HTTP GET request. Perhaps something more standard and leaner?
Thanks for the great work!
cc: @ahgamut

nice, any other comments etc? I am actually using redbean for a new service, so interested in the potential applications!

Regardless of the portability issues, I recommend merging in the patch from https://github.com/ahgamut/HVM/tree/cosmopolitan, since it makes cargo build about 3x faster on my machine.
Benchmarks
I ran these 3 times each, interleaved, to reduce random error.
HVM master
work@ub:~/beta/HVM$ time (cargo clean && cargo build 2>/dev/null)

real	1m13,181s
user	3m40,239s
sys	0m17,160s
work@ub:~/beta/HVM$ time (cargo clean && cargo build 2>/dev/null)

real	1m18,195s
user	3m47,138s
sys	0m17,900s
work@ub:~/beta/HVM$ time (cargo clean && cargo build 2>/dev/null)

real	1m25,026s
user	3m45,692s
sys	0m18,458s
work@ub:~/beta/HVM$ git rev-parse HEAD
71dd90684fe7d7acf21828428795b4689a639b34

Patch at https://github.com/ahgamut/HVM/tree/cosmopolitan
work@ub:~/beta/tmp/HVM$ time (cargo clean && cargo build 2>/dev/null)

real	0m38,791s
user	1m57,686s
sys	0m8,490s
work@ub:~/beta/tmp/HVM$ time (cargo clean && cargo build 2>/dev/null)

real	0m45,095s
user	1m56,095s
sys	0m8,656s
work@ub:~/beta/tmp/HVM$ time (cargo clean && cargo build 2>/dev/null)

real	0m43,731s
user	1m58,950s
sys	0m8,588s
work@ub:~/beta/tmp/HVM$ git rev-parse HEAD
f25cb04f27616163fe6a1be8acfc8e4fa521b754

I'll have a look, but I'm in the middle of a big refactor and polish right now

The changes are here. I'll have a look on @lawcho's suggestion soon.


Fix the step by step title sizing and spacing on mobile when it appears as a footer

Changes

changes margin bottom on step by step nav related from $gutter * 1.5 to $gutter-half for both desktop and mobile
adds font size bold-24 for mobile views

What
On mobile when the step by step nav appears as a footer the sizing of the step by step title is too small and there's a lot of whitespace between the title and the steps beneath.
We should bump up the size of the title and close up the space a little. Check-in with Kate if you need guidance on sizing and spacing.
Why
One of our goals this quarter is to optimise the user-facing step by step pattern.
Ticket: https://trello.com/c/zlQ0Go3P/700-fix-the-step-by-step-title-sizing-and-spacing-on-mobile-when-it-appears-as-a-footer
Remember to update the CHANGELOG if your change needs to be listed in the next version of the gem.

Component guide for this PR:
https://govuk-publishing-compon-pr-413.herokuapp.com/component-guide/step_by_step_nav_related

Waiting on kate to confirm the font size changes


fix(avm): fixes AVM full tests and decrease timeout to 35 minutes

Fixes failure in: https://github.com/AztecProtocol/aztec-packages/actions/runs/9885438673
Timeout decrease for the AVM full tests action to 35 minutes.

All AVM tests in full proving mode are passing: https://github.com/AztecProtocol/aztec-packages/actions/runs/9887473673

Benchmark results
Metrics with a significant change:

proof_construction_time_sha256_100_ms (16): 6,490 (+20%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,709 (-1%)
1,537 (-1%)
701 (-1%)
749 (-1%)
772 (-1%)

proof_construction_time_sha256_30_ms
11,712 (-1%)
3,134 (-2%)
1,399 (-1%)
1,439 (-1%)
1,467

proof_construction_time_sha256_100_ms
43,684 (-1%)
11,781
:warning: 6,490 (+20%)
5,404
5,343

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
59.0 (+2%)
87.0

proof_construction_time_poseidon_hash_30_ms
1,513 (-1%)
415 (-1%)
200
229 (+3%)
268

proof_construction_time_poseidon_hash_100_ms
5,614 (-1%)
1,515 (-1%)
675
735 (+1%)
741 (-1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
708
708
708

l1_rollup_calldata_gas
6,600
6,592
6,600

l1_rollup_execution_gas
583,062
583,205
583,364

l2_block_processing_time_in_ms
757 (-1%)
1,412
2,706

l2_block_building_time_in_ms
13,173
26,082
50,970

l2_block_rollup_simulation_time_in_ms
13,173
26,081
50,970

l2_block_public_tx_process_time_in_ms
11,023 (-1%)
23,726
48,608

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
7,039
9,839

node_database_size_in_bytes
12,464,208
16,142,416

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

GasToken:_increase_public_balance
98.4 (-1%)
13,790

GasToken:set_portal
11.5 (-5%)
3,339

Token:constructor
127 (+4%)
23,692

FPC:constructor
92.0 (-1%)
13,592

GasToken:mint_public
81.9
10,158

Token:mint_public
59.9 (-5%)
19,034

Token:assert_minter_and_mint
109 (+5%)
12,925

AuthRegistry:set_authorized
43.7 (-3%)
7,812

FPC:prepare_fee
105 (-6%)
15,062

Token:transfer_public
32.2 (-14%)
31,218

FPC:pay_refund
135 (+2%)
25,260

Benchmarking:increment_balance
1,351
15,267

Token:_increase_public_balance
15.9 (+7%)
15,006

FPC:pay_refund_with_shielded_rebate
183 (+2%)
26,347

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.155

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4
16.8
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.603
0.516
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.3
75.8 (-1%)
131 (-1%)
244 (-1%)
468 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.494
0.466
0.449 (-1%)
0.442 (-1%)
0.437 (-1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
60.0
111 (-1%)
182 (-1%)
351 (-1%)
691 (-1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.507
0.498 (-1%)
0.482 (-1%)
0.475 (-1%)
0.475 (-1%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
72.9
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
133
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.518
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
76,837
667,838

Transaction size based on fee payment method
| Metric |  |
| - |  |


Foundation: add SPI for XCTest

Foundation does not re-expose CoreFoundation interfaces on Windows.
This is desirable on Linux as well, however, in the interest of not
breaking existing applications, we have not yet done this.  For now
interfaces required are only available on Windows.

CC: @millenomi

@swift-ci please test

@swift-ci please test and merge


EXPERIMENTAL: Poll apiserver for new pods from executor

Probably we should use a ListWatch instead of polling. But in general the idea of getting rid of the deep call into the kubelet to get the pod status works. kube-dns and kube-ui come up and their status is updated (by kubelet's status manager).

/cc @jdef

The result of this PR is the following:

the executor remains the source of pod config updates, standing in for the apiserver
the executor stops querying the in-process kubelet for pod status; queries apiserver instead
the kubelet continues to publish pod status updates to apiserver

One consequence is that pod status must fully round-trip from the slave/node to the apiserver and then back again in order for the executor to observe an updated pod status. Somewhat concerned about the scalability of this, but perhaps those concerns are founded on the premise that apiserver and etcd currently don't scale -- they eventually will.
Another is that this implementation has the executor polling the apiserver for each monitored pod. This will not scale. I recommend looking at https://github.com/kubernetes/kubernetes/tree/master/pkg/controller/framework for inspiration (look at the k8s replication controller and/or daemon controller for inspiration). It would be lovely to have a single goroutine processing events for pod/task status changes, at the executor level.

Yeah, as commented in the PR description, we don't want polling of course. There are ListWatches for that. This is only a proof of concept for the information flow.

The other missing change is to replace the channel config source by a http config source between executor and Kubelet. Then both components can be split.
Another idea would be to investigate the Kubelet http endpoint. Maybe we get the pod status from there locally.

Be careful with http config source - we don't want the kubelet thinking
that these are static pods, we want it to update the apiserver as it
currently does
On Tue, Sep 8, 2015 at 5:11 PM, Dr. Stefan Schimanski <
<EMAIL_ADDRESS>wrote:

The other missing change is to replace the channel config source by a http
config source between executor and Kubelet. Then both components can be
split.
Another idea would be to investigate the Kubelet http endpoint. Maybe we
get the pod status from there locally.
—
Reply to this email directly or view it on GitHub
https://github.com/mesosphere/kubernetes/pull/44#issuecomment-138700821.

Sure. But I think that's a special case for the file source.
I want to try a small in-process web server to see whether this plan makes sense.

The other thing to worry about w/ the http source is the poll lag time; the
podtask only has so long to start before the we give up on it. given that
the executor and the kubelet are on the same machine I'm less worried about
network rtt time feeding into the lag, but the poller itself will likely
have some sort of lag built in. I don't think that the http source has a
streaming interface (though I could be wrong, haven't looked in a whie).
On Tue, Sep 8, 2015 at 5:19 PM, Dr. Stefan Schimanski <
<EMAIL_ADDRESS>wrote:

Sure. But I think that's a special case for the file source.
I want to try a small in-process web server to see whether this plan makes
sense.
—
Reply to this email directly or view it on GitHub
https://github.com/mesosphere/kubernetes/pull/44#issuecomment-138705274.


Remove test dependency on Microsoft.Extensions.Buffers.Testing.Sources

This source code use to live in common. This puts a copy of the source code here instead of pulling it via package reference.
cref https://github.com/aspnet/Common/pull/386

Closing in favor of this: https://github.com/aspnet/KestrelHttpServer/pull/2717/commits/128eefdef3825e1a2b8313f76b235c465b10b682, which means the .Sources package will still be produced, but it comes from kestrel instead of common.


Small object write performance very slow

Environment info
POK baremetal cluster(c83f1-infa)
NooBaa Version:
INFO[0000] CLI version: 5.9.0
INFO[0000] noobaa-image: noobaa/noobaa-core:master-20220112
INFO[0000] operator-image: noobaa/noobaa-operator:master-20220112
INFO[0000] noobaa-db-image: centos/postgresql-12-centos7
INFO[0000] Namespace: noobaa
OC version
Client Version: 4.9.0
Server Version: 4.9.0
Kubernetes Version: v1.22.0-rc.0+894a78b
Actual behavior

Writes with small objects(64KB, 4MB) limited to max of 120 writes/sec.

Expected behavior

Write performance should be much higher with small objects where the bandwidth is not an issue.

Steps to reproduce

Run cosbench with small object writes with multiple workers.

More information - Screenshots / Logs / Other output
must-gather.tar.gz

@nimrod-becker please add this issue to https://ibm.ent.box.com/notes/806750308079

Hi @davidbw246,
I saw this message in the endpoint logs:
2022-01-24 13:56:57.560361 [PID-14/TID-21] [L0] FS::FSWorker::Execute: WARNING Rename _old_path=/nsfs/fs1/cb6/.noobaa-nsfs_61b11a909954d0002a5d14fd/uploads/4a0c95ec-30ad-4161-8fa6-150f800e851e _new_path=/nsfs/fs1/cb6/586_64KB  took too long: 881.188 ms
When you try to measure the time of renaming a small file directly on your file system, do you see these times too? seems like the file system action itself took a long time (when I’m saying renaming I refer to moving a small file between directories)
besides that, I see many many Postgres error messages which might also slow down NooBaa,
I saw also some RPC timeouts which probably were caused because of the Postgres issues.

I did some tests on an endpoint where I time moving 64KB files between directories that back my buckets in /nsfs/fs1.
The time to move a file was consistently 4ms whether I did 1 or 2 moves simultaneously.
The 4ms per move is about half of the average time to do a 64KB put(8ms) using cosbench.
8ms for a put is ok, the problem is when you do 2 puts simultaneously they average 16ms. The system should be able to do 2 puts in 8ms.
example of command I ran on the endpoint:
time for i in {1..1000}; do mv cb1/tmp64KB cb2; mv cb2/tmp64KB cb1; done

Can we verify if the 16ms average is on the endpoint side or the FS side?
similar to what you did with the mv, can we run  it and time it from within the pod on the PVC bound to it?

It seems we would need to change the way we work with small files. We have an item on the roadmap to integrate with the SpectrumScale lib to increase performance for multipart uplaods. Might be beneficial to see if this also can be done for small objects, but we would need the info on what API to invoke

Hi @davidbw246 , Since action is on IBM development, we should still keep it open and ensure there is PR created to fix it. Directly closing it might result in we loosing the track.
@nimrod-becker , what do you think ? Can we track it at your end somehow as well.

Reopening due to the request from @akmithal  above.

As a roadmap item with the other items we have, not as a bug I think @akmithal

Was there a PR created to fix this as @akmithal recommended above?

There was no PR created, this is an item for future versions and it needs to be prioritized. @akmithal @davidbw246 please add to the list of items for next versions and close this issue

Has this been added to the list of items for next versions? Where would I find that list?

@nimrod-becker , what is the estimate on this availability

Marc's PR is already, in .
Its also dependent on the availability of libgpfs on the FS.
In any case, I am aware of performance testing being run

@nimrod-becker @guymguym can we close this one?

@guymguym @nimrod-becker
Do we want to keep this issue open for POSIX? Are we satisfied with suggesting libgpfs as our only solution?

@romayalon an optimization for posix would be to try using link() instead of rename() when the target file is missing, and if there is a race then fallback to rename. That should allow also reducing the rename overhead from most of the posix calls that do not involve replacing an existing target object. But this issue is quite old by now, so I would open a new issue to track further optimization options and close this one.

Per the last comment, I opened a new github issue - https://github.com/noobaa/noobaa-core/issues/8178 for further object operations optimizations, closing this one.


ui-router 1.0.0-rc1 onEnter hook fired multiple times

I'm migrating my app to ui-router 1.0.0 and I have this issue with nested states, when onEnter $transitions hook fires as many times, as many parents the state has (i.e. how deep it is nested), regardless of whether I filter states in my hook or not. Is this expected or a bug?
$stateProvider
  .state("root", {
    url: "/"
  })
  .state("root.child", {
    url: "/child"
  })
  .state("root.child.child", {
    url: "/child",
      data: {
      foo: "bar"
    }
  });

$transitions.onEnter(
  {to: state => state.data && state.data.foo === "bar"},
  transition =>
    console.log(`on enter triggered`, transition.from(),   transition.to())
);

$state.go("root.child.child");

In this example the hook is fired 3 times.
Here's the fiddle.

This is expected based on how you coded your hook.  The onEnter hook is a state based.  The pseudocode for processing onEnter is as follows:
Transition starting: {
  for each entering state: {
    If criteria matches {
      invoke hook for state
    }
  }
}

When initially going to root.child.child there are three states being entered: root, root.child, root.child.child.
Your criteria is { to: state => state.data && state.data.foo === "bar" } which matches for each of the three states being entered.  This is because although three states are being entered, there is only one "to state", which is root.child.child.  That state's data has the foo: 'bar' data, so it matches.
You should change your criteria to use entering instead of to.
{ entering: state => state.data && state.data.foo === 'bar' }

Here's an updated fiddle: https://jsfiddle.net/2m63pvqb/1/
Some other approaches that might work:
  .state("root.child.child", {
    url: "/child",
      data: {
      foo: "bar"
    },
   onEnter: ($transition$, $state$) => do sommething specific when entering root.child.child
  });

Some other approaches that might work:
   $transitions.onStart({ entering: state => state.data && state.data.foo === 'bar' }, trans =>
      do something ONCE if any states being entered have data.foo === 'bar'


Add verbose option and callback option

Some preparatory work for https://github.com/brainglobe/cellfinder-napari/issues/38. This:

Adds a verbose=True argument to cellfinder_core.main.main() which can be used to optionally turn off output to the terminal
[TODO] Adds a callback argument to cellfinder_core.main.main() that can be used to supply a custom callback function that will be called each time a layer is processed. This will allow us to use a custom callback function in cellfinder-napari to drive a progress bar in the GUI.

Going to work on this a bit more on my branch, will re-open when ready


More emphasis on const gotchas?

const x = { 'hello': 'world' };
x['hello'] = 'alien';
console.log(x['hello']); // prints 'alien'
x = { }                  // fails silently.
console.log(x['hello']); // still prints 'alien'

This (correctly) prints 'alien' but may not be apparent to many people. I think this should be at least noted in the example.

// fails silently.

that won't be true of a conforming implementation. it'll throw an error affirmatively.


Virtual Titles appear at end of line, rather than next to link

I'm cross-referencing from the upstream repo since this one claims to be actively-maintained.
https://github.com/ihsanturk/neuron.vim/issues/14
There appears to have been updates on the virtual title API (see last comment in above-linked issue)

The API has changed but the behaviour has not. You can now set the virtual text with extmarks but it's still rendered at the end of the line, and if you have multiple extmarks in a line it only shows the virtual text of one of them (forgot whether it's the first or last one).
https://github.com/neovim/neovim/pull/9496 is about having virtual text within lines, but it's only a barebones POC and it's been a while since it saw any real progress.

I like them at the end. Wouldn't it feel weird to have them in the middle of the line? Would that cause characters in that line to skip the virtual text automatically or what?

With conceal the cursor will still move through the actual characters in the buffer even if they are hidden. I'd expect this to behave similarly (hence it being called anticonceal in the PR), so the cursor would jump over this virtual text.
I would strongly prefer the title to be shown next to the link it belongs to rather than at the end of the line. I feel this would be much clearer especially with multiple links in a single line. It shouldn't be hard to make this configurable so those that prefer to keep it at the end can do so though.

I'm also in favor of putting the virtual title right next to the link. consider these two cases where titles are used "conversationally"
I am in favor of [ae28ce2] because they [fb23213d] and [1290cfe]. [Adjacent Links] [Look Good] [Make Lines Readable]

versus

I am in favor of [ae28ce2][Adjacent Links] because they [fb23213d][Look Better] and [1290cfe][Make Lines Readable].

Maybe it's just me, but I tend to write my link titles so that they both convey meaning on their own while also adding semantic value to the sentences in which they appear.
Bonus points if it's user-configurable!

Ok, but this is still unsupported on neovim, right? So for now all we can do is wait.

So I think one when this https://github.com/srid/neuron/issues/373 gets in we could have links such as [your title of choice](a34b2fc4.md) which we could create a shortcut to insert and then optionally conceal could only show the title. The downside of this is that the title will be hardcoded in so might be out of sync with the actual title if you have updated it.

While adding conceal for that sounds like a useful feature it's a separate one from this one; that title won't be virtual but actually present in the text, with the downsides you mention.
Adding an option/mapping to insert links with the title included might be useful. It would probably be good to support both versions, especially since the second one is just a regular markdown link and will thus work in places where wikilinks might not (I know some people prefer to keep all their links like that for this reason).

I'm also in favor of having the titles done inline, especially since I don't plan on migrating all my link types to the newly proposed format. I would imagine concealing as MaienM mentioned would work for this no matter the format. There is a simple example of it being done here https://gist.github.com/huytd/668fc018b019fbc49fa1c09101363397


[BUG] Deleted wallet balance is included in Wallet Management "LNBits Balance"

Describe the bug
Problem: If / When deleted wallets have balance it is calculated to balance on Manage Server page on Wallets Management also after deletion. Issue ruins usability of LNBits Balance and Reserve calculation %.
To Reproduce
Steps to reproduce the behavior:

Go to super admin page and note LNBits Balance and Reserve%
Go to any wallet with balance
Delete the wallet
Go to super admin page and notice the LNBits Balance is not change and Reserve  % has not increased

Expected behavior
LNBits balance should decrease of amount of deleted wallet had.

LNbits version: 0.11.1
Database sqlite

Additional context
Even if user would empty before delete, issue remains cause wallet may have millisats, which are impossible for user to drain.
Seems also "Node Balance" does not included balance from disconnected channels (FundingSource LNDRest).
Yvette confirmed at https://t.me/lnbits/80187 issue deleted wallet balance.
Suggestions to fix

Tell how one can set one wallet balance on database to zero, cause updating is not trivial as this:
How you set balance of wallet to zero, cause database.balances rows are views?

on database.sqlite3
sqlite> UPDATE balances SET balance = 0 WHERE wallet = '37cf3944dc8649e.....';
Error: cannot modify balances because it is a view

Implemnt "Un-topup" functionality, where Server Super Admin can discard extra balance for eg "Burner Wallet" (wallet that has exessive balance for some reason).

Implement change where wallet deletion also zeroes deleted wallet balance, from balances table, including millisats.

Why this is needed?
Cause currently LNBits admin has no idea how much of total balance of users wallets is. Calculation now days counts deleted wallets balance too. ie it counts balances of wallets that no one can access ie it counts wrong.

This is a "feature not a bug" but I agree it should change. When a wallet is deleted, the "lnbits balance" should be deducted by however much that wallet contained. I looked into the code and it involves adding a deduction transaction as part of the deletion process. It would also be nice to "clean up" any previously deleted wallets from the balance. A use-case is when the LN node operator wants to swap-out sats with an onchain payment but deduct the sata from an lnbits wallet, the only way to keep the lnbits wallet balanced is to transfer it to a special "swap-out" wallet. It would be nice to also have the opposite of the "top off" button and allow the admin to subtract sats from a wallet for such an admin case.

This is a "feature not a bug" but I agree it should change. When a wallet is deleted, the "lnbits balance" should be deducted by however much that wallet contained.

You should explain why you think it should change. Otherwise your comment does not say anything new.

This is a "feature not a bug" but I agree it should change. When a wallet is deleted, the "lnbits balance" should be deducted by however much that wallet contained.

You should explain why you think it should change. Otherwise your comment does not say anything new.

Ok. I think it should change.

yes, i also think that should change, eventually the watchdog feature aalso should utilize this and turn off payments if lnbits balance exceeds the node balance

Change cause superuser of LNbits cannot know actual balance needed to cover user funds if non-accessible wallets are calculated to balance now.
Should you consider also solution option that wallet with any (Even millisats) can not be deleted? During delecion process move funds to another wallet would be mandatory. This way there would be no deleted wallet with balance. But anyhow solution to fix currently broken balances should be offered to superusers

From: Pavol Rusnak @.>
Sent: Sunday, March 24, 2024 11:22:12 PM
To: lnbits/lnbits @.>
Cc: Tomi Lind @.>; Author @.>
Subject: Re: [lnbits/lnbits] [BUG] Deleted wallet balance is included in Wallet Management "LNBits Balance" (Issue #2224)
This is a "feature not a bug" but I agree it should change. When a wallet is deleted, the "lnbits balance" should be deducted by however much that wallet contained.
You should explain why you think it should change. Otherwise your comment does not say anything new.
—
Reply to this email directly, view it on GitHubhttps://github.com/lnbits/lnbits/issues/2224#issuecomment-2016947066, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABXJ6Z7M7I2VQPBIOUCTUZLYZ47YJAVCNFSM6AAAAABCQFFY3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWHE2DOMBWGY.
You are receiving this because you authored the thread.Message ID: @.***>

For audits a burn of sats needs to be reported within the txs of the wallet

Change cause superuser of LNbits cannot know actual balance needed to cover user funds if non-accessible wallets are calculated to balance now.
Should you consider also solution option that wallet with any (Even millisats) can not be deleted? During delecion process move funds to another wallet would be mandatory. This way there would be no deleted wallet with balance. But anyhow solution to fix currently broken balances should be offered to superusers

From: Pavol Rusnak @.>
Sent: Sunday, March 24, 2024 11:22:12 PM
To: lnbits/lnbits @.>
Cc: Tomi Lind @.>; Author @.>
Subject: Re: [lnbits/lnbits] [BUG] Deleted wallet balance is included in Wallet Management "LNBits Balance" (Issue #2224)
This is a "feature not a bug" but I agree it should change. When a wallet is deleted, the "lnbits balance" should be deducted by however much that wallet contained.
You should explain why you think it should change. Otherwise your comment does not say anything new.
—
Reply to this email directly, view it on GitHubhttps://github.com/lnbits/lnbits/issues/2224#issuecomment-2016947066, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABXJ6Z7M7I2VQPBIOUCTUZLYZ47YJAVCNFSM6AAAAABCQFFY3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWHE2DOMBWGY.
You are receiving this because you authored the thread.Message ID: @.***>

If you are required to move sats to another wallet, then lnbits becomes a roach motel if its attached to a lightning node that wants to perform onchain payments or to cover channel fees. Lnbits needs the ability to both add sats to a wallet, and to remove sats from a wallet as an administrative function. If a wallet is deleted and it contains sats, that should be deducted from the lnbits balance and be considered a donation to the lightning node.

When will this pr be included in a release?

The fix is included in this PR by @dni
https://github.com/lnbits/lnbits/pull/2490
A new release will be available this week.

Works perfectly!


Bonds: Reference Pricing Curves

Please add two additional curves to the Price graph for a bond so that investors may view the standard curve alongside the actual Optimistic and Pessimistic curves.

displaying two curves on the price history chart on the bonds interface?

Is there any api call's ready for optimistic & pessimistic chart?
Or do I need to implement this with placeholder?

@elite0226
The Optimistic- and Pessimistic Curves are actually just 2 other bonds' price histories that are displayed on the same chart - to be provided.
The Standard Curve is the formula for the predicted bond prices - to be provided.


Some new ansi issues...

At least on my system (shsbbs.net) with ssh (login bbs password shsbbs).  I didn't check telnet.  The message/files groups/areas selector is off a bit and in ice edit, when wrapping, there is some weirdness.  I don't know how to be more precise, check it out on my system to see it.  Both of those problems didn't appear in netrunner or ftelnet.  I need to learn how to do video screen captures...

Seem to be fixed in one of my changes in the ansi backend.
I made an emergency release :)
https://github.com/mkrueger/icy_term/releases/tag/0.6.5
I wanted to test some days the refactorings I did but my unit test coverage is good so at least some things are working :).
Nice that anyone uses IEMSI. Reopen if you still have issues with the selector.


successMessage, errorMessage, and progressMessage do not accept a function that returns an object.

Documentation states that successMessage, errorMessage, and progressMessage are able to take a function that returns an message configuration object. However, from the code below, the return of the function clearly expects a string:
return n = a[e + "Message"], o.isFunction(n) ? n.call(g, e, t) : n

If the function, in this case n, returns an object, it is later on written into 'message' during success and error states.

I'm not entirely sure that is true. If you look at the non-uglified Coffeescript, it's a little clearer that code above invokes the function type + 'Message' where type is {'success', 'error', 'progress'}' if it's a function, otherwise just return the value of type + 'Message'`. Trying to read uglified code can be misleading since its all mangled up. If you do happen to run into an real example where the above does not work, feel free to open a new issue with the examples and we'll be happy to help debug the issue.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2815

Questions ?
Please refer to the Backport tool documentation


Signup warm-up screen and illustration

What

Signup warm-up screen and illustration

I think this one was implemented by @monsieurtanuki, isn't it?


Refactor linter provider

I just found another small issue. If the linting process succeeds without error, there is an error logged to the console: SyntaxError: Unexpected end of input
The error is raised by JSON.parse after you pass it an empty array. If you pass an array of Uint8Arrays (like in the case the compiler found errors) it works fine. That's a bit surprising to me. Is this documented behaviour?
To fix this, I restructured the code a bit.

Awesome! Thank you.

Wanna join the organization? I'm really thankful for the contributions you've done.

Glad I could help and thank for your work. Also thank you for your offer. Currently my resources are a bit limited and I'm generally not sure if crystal and I have a future together :) I still try to find out if it fits my needs. If it's ok for you, I'd like to keep the current workflow. At least for now.

Works for me. :D


print reason why parent task was cancelled

Description
Print reason why parent task was cancelled
Related Issues
Resolves #11830

Check List

[ ] Functionality includes testing.
[ ] API changes companion pull request created, if applicable.
[ ] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dblock  I have check the banReason can't be null.
startBan will be called in TaskCancellationService.cancelTaskAndDescendants, it will be called in two place:

BanParentRequestHandler.messageReceived(): in here, reason in BanParentTaskRequest can't be null.
TaskManager.cancelTaskAndDescendants(), it also can't be null.

Even if banReason is null, it will not throw NullPointerException.

Looks good, let's add a line to CHANGELOG?

https://build.ci.opensearch.org/blue/organizations/jenkins/gradle-check/detail/gradle-check/42016/pipeline


⚠ All Access Electrical has degraded performance

In 4b16363, All Access Electrical (https://allaccesselectrical.com.au) experienced degraded performance:

HTTP code: 200
Response time: 9986 ms

Resolved: All Access Electrical performance has improved in 556dd3a.


if  use this one ,how to deal with .md blog

from doc, i clearly understand how to use for .astro files,but it was confused for me about .md

@wanghaisheng this library does not support markdown in the /pages directory.
I encourage you to separate your markdown content from your astro pages that have the styling and logic.
Instead, for markdown, I recommend using Astro with its Content Collections:

https://docs.astro.build/en/guides/content-collections/#organizing-with-subdirectories
https://docs.astro.build/en/recipes/i18n/#use-collections-for-translated-content

Here’s an example project structure:
.
└── astro-project/
    └── src/
        ├── pages/
        │   └── blog/
        │       ├── index.astro
        │       └── [id].astro
        └── content/
            └── blog/
                ├── en/
                │   ├── post-1.md
                │   └── post-2.md
                ├── es/
                │   ├── post-1.md
                │   └── post-2.md
                └── fr/
                    ├── post-1.md
                    └── post-2.md

That way, all your posts are organized with all your languages, and you have a single blog page to list posts and individual page for each post.
Then, you can use your locale from this library along with getCollection and getEntry, and render the contents in your Astro files.
So all your locales will use the same astro template, even with a default locale.
Let me know if you have any questions!  I will update the README with this information too.

@wanghaisheng updated the docs!  Hope that helps—let me know if you have any questions

I  finally get that
i am use content/*.md  now
let me try

Then, you can use your locale from this library along with getCollection and getEntry, and render the contents in your Astro files.

can you show a example for this

I am traveling tomorrow, but I can build in example with Content Collections in a few days

Here is an example using the blog template from astro with this library
astro-i18n-blog.zip
Not everything is translated, but it gives an example with Content Collections.  Please upgrade your astro-i18n-aut for more utility functions

@wanghaisheng I think I will update the example with helper functions like getLocaleCollection later


Support for v3.0?

Getting the following:
warn - As of Tailwind CSS v2.2, `lightBlue` has been renamed to `sky`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `warmGray` has been renamed to `stone`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `trueGray` has been renamed to `neutral`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `coolGray` has been renamed to `gray`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `blueGray` has been renamed to `slate`.
warn - Update your configuration file to silence this warning.
wait  - compiling...
error - ./node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[3].oneOf[8].use[1]!./node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[3].oneOf[8].use[2]!./styles/globals.css
RangeError: Maximum call stack size exceeded
    at Array.map (<anonymous>)
wait  - compiling /_error (client and server)...
wait  - compiling...
error - ./node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[3].oneOf[8].use[1]!./node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[3].oneOf[8].use[2]!./styles/globals.css
RangeError: Maximum call stack size exceeded
    at Array.map (<anonymous>)

I hope to use this for my projects some day, thanks for starting this

@robertstojs Thanks for opening this issue! I am currently working to resolve another issue that may be contributing to the error you're seeing, here: https://github.com/tailwindlabs/tailwindcss-intellisense/issues/544
Once that's resolved, I'll also push a change for the color name warnings, so this should be fully compatible soon!
** In the meantime, you should be able to use version 1.1.0 which should resolve that error if it's related to using the tailwind-lerp-colors plugin (but not the warnings yet).

@robertstojs Closing this issue as resolved. If you encounter any further issues, please reach out. I'd love to help make this work for you! 😃


Export SetSelectedColumns Outside of Package

Many applications need to set the filtering columns at a later stage (not at the creation of the reader). Hence exposing this method would be useful.

@akrennmair Please review


[igraph] update to 0.10.7

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory. Nothing to delete
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks for the update!


KIE Sandbox won't accept extended services URLs with pathnames (i.e. http://localhost/extended-services) via env var

If the KIE_SANDBOX_EXTENDED_SERVICES_URL env var is set to a URL with pathnames, such as http://localhost/extended-services/ the path is removed from the final URL string.
Check here: https://github.com/kiegroup/kie-tools/blob/main/packages/online-editor/src/extendedServices/ExtendedServicesContextProvider.tsx#L69
Suggested fix: If envUrl.pathname is different than /, concatenate it to the final envHost.