[BACKLOG-20951] - changing text of Stop menu item

@pentaho/ackbar message changes.  probably don't need wingman

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'ui' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'ui' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  ui/src/main/java/org/pentaho/di/ui/spoon/trans/TransGraph.java
  ui/src/main/resources/org/pentaho/di/ui/spoon/messages/messages_en_US.properties

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.trans.steps.salesforceupdate.SalesforceUpdateMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupsert.SalesforceUpsertMeta

Instruction Change: -0.1% :small_red_triangle_down:


feat: add metrics

Stacked PRs:

#403
->#402
#401
#400
#399
#398

feat: add metrics

closing in favor of https://github.com/GoogleCloudPlatform/java-docs-samples/pull/9691


CMake Warning

Describe the bug
  The DOWNLOAD_EXTRACT_TIMESTAMP option was not given and policy CMP0135 is
  not set.  The policy's OLD behavior will be used.  When using a URL
  download, the timestamps of extracted files should preferably be that of
  the time of extraction, otherwise code that depends on the extracted
  contents might not be rebuilt if the URL changes.  The OLD behavior
  preserves the timestamps from the archive instead, but this is usually not
  what you want.  Update your project to the NEW behavior or specify the
  DOWNLOAD_EXTRACT_TIMESTAMP option with a value of true to avoid this
  robustness issue.

Steps to reproduce

First I make a PR
Then the CI runs
And then look at the logs for Build Source Tests

Expected behavior
No CMake warnings

Related article(s):
https://cmake.org/cmake/help/latest/policy/CMP0135.html


Add Roadmap

Creates a ROADMAP file for upcoming Milestones and links to it from the project README.

:snowman:

:shipit:


Roborock S6: State "roborock.0.Devices.XXX.cleaningInfo.Y" has no existing object

Describe the bug
Hab gerade meinen zweiten Roborock (S6) in die Roborock-App umgezogen und bekomme nun regelmäßig (bei jedem Update) eine Wagenladung voll Warnings im Log nach dem Schema "State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.0" has no existing object, this might lead to an error in future versions".  Das betroffene Device ist nur "5hMBOgcFv6CIHdkwW59ObV" (S6). Beim anderen bisher vorhandenen Device "BzoCkI61lkZZ4dPedPre6" (S7) sind keine Warnings vorhanden und dort werden auch die korrekten Werte bestückt.
Screenshots & Logfiles
Log:
2023-02-05 17:51:49.017 - info: host.raspberrypi-gang instance system.adapter.roborock.0 started with pid 606
2023-02-05 17:51:50.804 - debug: roborock.0 (606) Redis Objects: Use Redis connection: <IP_ADDRESS>:9001
2023-02-05 17:51:50.874 - debug: roborock.0 (606) Objects client ready ... initialize now
2023-02-05 17:51:50.877 - debug: roborock.0 (606) Objects create System PubSub Client
2023-02-05 17:51:50.878 - debug: roborock.0 (606) Objects create User PubSub Client
2023-02-05 17:51:51.013 - debug: roborock.0 (606) Objects client initialize lua scripts
2023-02-05 17:51:51.023 - debug: roborock.0 (606) Objects connected to redis: <IP_ADDRESS>:9001
2023-02-05 17:51:51.027 - silly: roborock.0 (606) redis psubscribe cfg.o.system.user.*
2023-02-05 17:51:51.081 - silly: roborock.0 (606) redis psubscribe cfg.o.enum.*
2023-02-05 17:51:51.088 - silly: roborock.0 (606) objectDB connected
2023-02-05 17:51:51.092 - debug: roborock.0 (606) Redis States: Use Redis connection: <IP_ADDRESS>:6379
2023-02-05 17:51:51.101 - debug: roborock.0 (606) States create System PubSub Client
2023-02-05 17:51:51.103 - debug: roborock.0 (606) States create User PubSub Client
2023-02-05 17:51:51.116 - debug: roborock.0 (606) States connected to redis: <IP_ADDRESS>:6379
2023-02-05 17:51:51.117 - silly: roborock.0 (606) statesDB connected
2023-02-05 17:51:51.385 - info: roborock.0 (606) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock#453edf077b2b824092869fbc1d98407d7c535df3) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
2023-02-05 17:51:51.537 - silly: roborock.0 (606) States system redis pmessage io.system.adapter.roborock.0.logLevel/io.system.adapter.roborock.0.logLevel:{"val":"silly","ack":true,"ts":1675615911440,"q":0,"from":"system.adapter.roborock.0","lc":1675615911440}
2023-02-05 17:51:51.665 - debug: roborock.0 (606) RoomIDs debug: {"10467471":"Wohnzimmer","10467473":"Zimmer Domi","10467476":"Küche","10467477":"Schlafzimmer","10467479":"Bad","10467481":"Balkon","10467484":"Gang","10609107":"Nebenzimmer"}
2023-02-05 17:51:51.755 - info: roborock.0 (606) MQTT initialized
2023-02-05 17:51:51.808 - debug: roborock.0 (606) Products: object
2023-02-05 17:51:51.809 - debug: roborock.0 (606) Products: object
2023-02-05 17:51:51.810 - debug: roborock.0 (606) Robot key: roborock.vacuum.s6
2023-02-05 17:51:52.217 - debug: roborock.0 (606) Latest data requested
2023-02-05 17:51:52.218 - debug: roborock.0 (606) getParameter: get_status
2023-02-05 17:51:52.224 - debug: roborock.0 (606) getParameter: get_water_box_custom_mode
2023-02-05 17:51:52.225 - debug: roborock.0 (606) getParameter: get_consumable
2023-02-05 17:51:52.227 - debug: roborock.0 (606) getParameter: get_network_info
2023-02-05 17:51:52.230 - debug: roborock.0 (606) getParameter: get_carpet_mode
2023-02-05 17:51:52.231 - debug: roborock.0 (606) getParameter: get_carpet_clean_mode
2023-02-05 17:51:52.233 - debug: roborock.0 (606) getParameter: get_fw_features
2023-02-05 17:51:52.233 - debug: roborock.0 (606) Firmware features request
2023-02-05 17:51:52.234 - debug: roborock.0 (606) getParameter: get_multi_maps_list
2023-02-05 17:51:52.236 - debug: roborock.0 (606) getParameter: get_room_mapping
2023-02-05 17:51:52.237 - debug: roborock.0 (606) get_room_mapping
2023-02-05 17:51:52.239 - debug: roborock.0 (606) Products: object
2023-02-05 17:51:52.239 - debug: roborock.0 (606) Products: object
2023-02-05 17:51:52.240 - debug: roborock.0 (606) Robot key: roborock.vacuum.a15
2023-02-05 17:51:52.589 - debug: roborock.0 (606) dps debug: {"id":10,"result":[[16,"10467484"],[17,"10467471"],[18,"10467479"],[19,"10467477"],[22,"10609107"],[23,"10467481"],[24,"10467476"]]}
2023-02-05 17:51:52.595 - debug: roborock.0 (606) get_room_mapping: [[16,"10467484"],[17,"10467471"],[18,"10467479"],[19,"10467477"],[22,"10609107"],[23,"10467481"],[24,"10467476"]]
2023-02-05 17:51:52.598 - debug: roborock.0 (606) dps debug: {"id":1,"result":[{"msg_ver":2,"msg_seq":293,"state":8,"battery":100,"clean_time":3218,"clean_area":49750000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":104,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"mop_forbidden_enable":0,"debug_mode":0}]}
2023-02-05 17:51:52.599 - debug: roborock.0 (606) get_status: {"msg_ver":2,"msg_seq":293,"state":8,"battery":100,"clean_time":3218,"clean_area":49750000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":104,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"mop_forbidden_enable":0,"debug_mode":0}
2023-02-05 17:51:52.616 - debug: roborock.0 (606) dps debug: {"id":8,"result":[111,112,113,114,115,116,117,118,119,120,122,123,124,125]}
2023-02-05 17:51:52.618 - debug: roborock.0 (606) dps debug: {"id":2,"result":"unknown_method"}
2023-02-05 17:51:52.621 - debug: roborock.0 (606) dps debug: {"id":5,"result":[1082836,16630107500,417,[1675416611,1675157412,1674811813,1674552612,1674207012,1673947812,1673602213,1673343012,1672997413,1672738213,1672392612,1672133412,1671787813,1671528612,1671183013,1670923813,1670578212,1670319013,1669973412,1669714213]]}
2023-02-05 17:51:52.636 - debug: roborock.0 (606) dps debug: {"id":4,"result":{"ssid":"1.FCGlucke_Rep","ip":"<IP_ADDRESS>","mac":"64:90:c1:10:fd:96","bssid":"70:4f:57:52:df:4b","rssi":-57}}
2023-02-05 17:51:52.638 - debug: roborock.0 (606) dps debug: {"id":9,"result":[{"max_multi_map":1,"max_bak_map":0,"multi_map_count":1,"map_info":[{"mapFlag":0,"add_time":1675531719,"length":10,"name":"Hauptkarte","bak_maps":[]}]}]}
2023-02-05 17:51:52.640 - debug: roborock.0 (606) dps debug: {"id":3,"result":[{"main_brush_work_time":1083754,"side_brush_work_time":381931,"filter_work_time":108742,"filter_element_work_time":2,"sensor_dirty_time":0}]}
2023-02-05 17:51:52.643 - debug: roborock.0 (606) dps debug: {"id":7,"result":"unknown_method"}
2023-02-05 17:51:52.645 - debug: roborock.0 (606) dps debug: {"id":6,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}]}
2023-02-05 17:51:52.670 - info: roborock.0 (606) State value to set for "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.deviceStatus.water_box_custom_mode" has to be type "number" but received type "string"
2023-02-05 17:51:52.671 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.672 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.672 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.733 - debug: roborock.0 (606) dps debug: {"id":14,"result":[[1674552612,1674555773,3161,49920000,0,1,3,1,52]]}
2023-02-05 17:51:52.734 - debug: roborock.0 (606) Cleaning record: [1674552612,1674555773,3161,49920000,0,1,3,1,52]
2023-02-05 17:51:52.737 - debug: roborock.0 (606) dps debug: {"id":18,"result":[[1673343012,1673346835,3823,49267500,0,1,3,1,52]]}
2023-02-05 17:51:52.738 - debug: roborock.0 (606) dps debug: {"id":11,"result":[[1675416611,1675419829,3218,49750000,0,1,3,1,52]]}
2023-02-05 17:51:52.739 - debug: roborock.0 (606) Cleaning record: [1673343012,1673346835,3823,49267500,0,1,3,1,52]
2023-02-05 17:51:52.740 - debug: roborock.0 (606) Cleaning record: [1675416611,1675419829,3218,49750000,0,1,3,1,52]
2023-02-05 17:51:52.753 - debug: roborock.0 (606) dps debug: {"id":12,"result":[[1675157412,1675160804,3392,49675000,0,1,3,1,52]]}
2023-02-05 17:51:52.754 - debug: roborock.0 (606) Cleaning record: [1675157412,1675160804,3392,49675000,0,1,3,1,52]
2023-02-05 17:51:52.756 - debug: roborock.0 (606) dps debug: {"id":13,"result":[[1674811813,1674815459,3646,49845000,0,1,3,1,52]]}
2023-02-05 17:51:52.757 - debug: roborock.0 (606) Cleaning record: [1674811813,1674815459,3646,49845000,0,1,3,1,52]
2023-02-05 17:51:52.759 - debug: roborock.0 (606) dps debug: {"id":16,"result":[[1673947812,1673951552,3740,49795000,0,1,3,1,52]]}
2023-02-05 17:51:52.759 - debug: roborock.0 (606) Cleaning record: [1673947812,1673951552,3740,49795000,0,1,3,1,52]
2023-02-05 17:51:52.761 - debug: roborock.0 (606) dps debug: {"id":15,"result":[[1674207012,1674209712,2700,46510000,0,1,3,1,52]]}
2023-02-05 17:51:52.762 - debug: roborock.0 (606) Cleaning record: [1674207012,1674209712,2700,46510000,0,1,3,1,52]
2023-02-05 17:51:52.764 - debug: roborock.0 (606) dps debug: {"id":17,"result":[[1673602213,1673605818,3605,49705000,0,1,3,1,52]]}
2023-02-05 17:51:52.765 - debug: roborock.0 (606) Cleaning record: [1673602213,1673605818,3605,49705000,0,1,3,1,52]
2023-02-05 17:51:52.779 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.3.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.783 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.3.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.784 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.3.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.788 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.3.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.789 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.3.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.790 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.3.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.791 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.3.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.791 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.3.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.792 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.3.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.793 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.7.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.795 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.7.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.796 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.7.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.796 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.7.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.797 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.7.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.798 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.7.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.799 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.7.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.800 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.7.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.801 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.7.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.802 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.0.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.802 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.0.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.803 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.0.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.826 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.0.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.827 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.0.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.828 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.0.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.839 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.0.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.840 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.0.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.841 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.0.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.842 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.1.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.847 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.1.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.848 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.1.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.849 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.1.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.850 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.1.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.851 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.1.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.854 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.1.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.855 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.1.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.856 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.1.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.857 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.2.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.858 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.2.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.859 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.2.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.860 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.2.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.861 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.2.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.862 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.2.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.863 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.2.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.864 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.2.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.865 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.2.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.866 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.5.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.870 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.5.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.872 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.5.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.873 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.5.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.874 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.5.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.874 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.5.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.875 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.5.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.876 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.5.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.877 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.5.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.878 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.4.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.879 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.4.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.880 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.4.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.881 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.4.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.882 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.4.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.883 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.4.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.884 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.4.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.885 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.4.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.886 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.4.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.887 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.6.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.932 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.6.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.933 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.6.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.934 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.6.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.935 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.6.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.936 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.6.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.941 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.6.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.942 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.6.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:52.943 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.6.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:53.223 - debug: roborock.0 (606) Latest data requested
2023-02-05 17:51:53.223 - debug: roborock.0 (606) getParameter: get_status
2023-02-05 17:51:53.224 - debug: roborock.0 (606) getParameter: get_water_box_custom_mode
2023-02-05 17:51:53.226 - debug: roborock.0 (606) getParameter: get_consumable
2023-02-05 17:51:53.226 - debug: roborock.0 (606) getParameter: get_network_info
2023-02-05 17:51:53.227 - debug: roborock.0 (606) getParameter: get_carpet_mode
2023-02-05 17:51:53.228 - debug: roborock.0 (606) getParameter: get_carpet_clean_mode
2023-02-05 17:51:53.230 - debug: roborock.0 (606) getParameter: get_fw_features
2023-02-05 17:51:53.230 - debug: roborock.0 (606) Firmware features request
2023-02-05 17:51:53.231 - debug: roborock.0 (606) getParameter: get_multi_maps_list
2023-02-05 17:51:53.231 - debug: roborock.0 (606) getParameter: get_room_mapping
2023-02-05 17:51:53.232 - debug: roborock.0 (606) get_room_mapping
2023-02-05 17:51:53.297 - debug: roborock.0 (606) dps debug: {"id":40,"result":[[16,"10467476"],[17,"10467479"],[18,"10467477"],[19,"10467481"],[20,"10467473"],[22,"10467471"],[23,"10467484"]]}
2023-02-05 17:51:53.298 - debug: roborock.0 (606) get_room_mapping: [[16,"10467476"],[17,"10467479"],[18,"10467477"],[19,"10467481"],[20,"10467473"],[22,"10467471"],[23,"10467484"]]
2023-02-05 17:51:53.300 - debug: roborock.0 (606) dps debug: {"id":36,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}]}
2023-02-05 17:51:53.301 - debug: roborock.0 (606) dps debug: {"id":32,"result":[203]}
2023-02-05 17:51:53.303 - debug: roborock.0 (606) dps debug: {"id":38,"result":[111,112,113,114,115,116,117,118,119,120,122,123,124,125]}
2023-02-05 17:51:53.304 - debug: roborock.0 (606) dps debug: {"id":31,"result":[{"msg_ver":2,"msg_seq":282,"state":8,"battery":100,"clean_time":11,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"fan_power":102,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":203,"water_box_carriage_status":0,"mop_forbidden_enable":0,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":0,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"dock_error_status":0,"unsave_map_reason":4,"unsave_map_flag":0}]}
2023-02-05 17:51:53.305 - debug: roborock.0 (606) get_status: {"msg_ver":2,"msg_seq":282,"state":8,"battery":100,"clean_time":11,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"fan_power":102,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":203,"water_box_carriage_status":0,"mop_forbidden_enable":0,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":0,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"dock_error_status":0,"unsave_map_reason":4,"unsave_map_flag":0}
2023-02-05 17:51:53.321 - debug: roborock.0 (606) dps debug: {"id":39,"result":[{"max_multi_map":1,"max_bak_map":1,"multi_map_count":1,"map_info":[{"mapFlag":0,"add_time":1675423621,"length":10,"name":"Hauptkarte","bak_maps":[{"mapFlag":4,"add_time":1675423621}]}]}]}
2023-02-05 17:51:53.323 - debug: roborock.0 (606) dps debug: {"id":37,"result":[{"carpet_clean_mode":1}]}
2023-02-05 17:51:53.325 - debug: roborock.0 (606) dps debug: {"id":33,"result":[{"main_brush_work_time":875038,"side_brush_work_time":11144,"filter_work_time":324864,"filter_element_work_time":0,"sensor_dirty_time":70053,"dust_collection_work_times":0}]}
2023-02-05 17:51:53.331 - debug: roborock.0 (606) dps debug: {"id":34,"result":{"ssid":"1.FCGlucke","ip":"<IP_ADDRESS>","mac":"b0:4a:39:04:69:e9","bssid":"44:4e:6d:69:b7:f1","rssi":-68}}
2023-02-05 17:51:53.363 - debug: roborock.0 (606) dps debug: {"id":35,"result":{"clean_time":874941,"clean_area":13618002500,"clean_count":342,"dust_collection_count":0,"records":[1675451592,1675420802,1675248002,1675075202,1674996181,1674816001,1674725138,1674725117,1674725026,1674643201,1674470400,1674211201,1674038400,1673865601,1673606401,1673433600,1673260802,1673001600,1672828801,1672656000]}}
2023-02-05 17:51:53.436 - debug: roborock.0 (606) dps debug: {"id":42,"result":[{"begin":1675420802,"end":1675423566,"duration":2764,"area":45560000,"error":0,"complete":1,"start_type":3,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.437 - debug: roborock.0 (606) Cleaning record: {"begin":1675420802,"end":1675423566,"duration":2764,"area":45560000,"error":0,"complete":1,"start_type":3,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.441 - debug: roborock.0 (606) dps debug: {"id":43,"result":[{"begin":1675248002,"end":1675250804,"duration":2802,"area":45317500,"error":0,"complete":1,"start_type":3,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.441 - debug: roborock.0 (606) Cleaning record: {"begin":1675248002,"end":1675250804,"duration":2802,"area":45317500,"error":0,"complete":1,"start_type":3,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.447 - debug: roborock.0 (606) dps debug: {"id":46,"result":[{"begin":1674816001,"end":1674818840,"duration":2839,"area":45667500,"error":0,"complete":1,"start_type":3,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.448 - debug: roborock.0 (606) Cleaning record: {"begin":1674816001,"end":1674818840,"duration":2839,"area":45667500,"error":0,"complete":1,"start_type":3,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.450 - debug: roborock.0 (606) dps debug: {"id":41,"result":[{"begin":1675451592,"end":1675451603,"duration":11,"area":0,"error":0,"complete":0,"start_type":2,"clean_type":3,"finish_reason":60,"dust_collection_status":0}]}
2023-02-05 17:51:53.451 - debug: roborock.0 (606) dps debug: {"id":52,"result":[{"begin":1674211201,"end":1674214020,"duration":2819,"area":45745000,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.452 - debug: roborock.0 (606) Cleaning record: {"begin":1675451592,"end":1675451603,"duration":11,"area":0,"error":0,"complete":0,"start_type":2,"clean_type":3,"finish_reason":60,"dust_collection_status":0}
2023-02-05 17:51:53.453 - debug: roborock.0 (606) Cleaning record: {"begin":1674211201,"end":1674214020,"duration":2819,"area":45745000,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.455 - debug: roborock.0 (606) dps debug: {"id":48,"result":[{"begin":1674725117,"end":1674725124,"duration":2,"area":0,"error":0,"complete":0,"start_type":2,"clean_type":1,"finish_reason":43,"dust_collection_status":0}]}
2023-02-05 17:51:53.456 - debug: roborock.0 (606) Cleaning record: {"begin":1674725117,"end":1674725124,"duration":2,"area":0,"error":0,"complete":0,"start_type":2,"clean_type":1,"finish_reason":43,"dust_collection_status":0}
2023-02-05 17:51:53.460 - debug: roborock.0 (606) dps debug: {"id":44,"result":[{"begin":1675075202,"end":1675077928,"duration":2726,"area":45695000,"error":0,"complete":1,"start_type":3,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.460 - debug: roborock.0 (606) Cleaning record: {"begin":1675075202,"end":1675077928,"duration":2726,"area":45695000,"error":0,"complete":1,"start_type":3,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.478 - debug: roborock.0 (606) dps debug: {"id":50,"result":[{"begin":1674643201,"end":1674646187,"duration":2986,"area":45902500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.479 - debug: roborock.0 (606) Cleaning record: {"begin":1674643201,"end":1674646187,"duration":2986,"area":45902500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.481 - debug: roborock.0 (606) dps debug: {"id":58,"result":[{"begin":1673001600,"end":1673001754,"duration":147,"area":3327500,"error":0,"complete":0,"start_type":2,"clean_type":3,"finish_reason":60,"dust_collection_status":0}]}
2023-02-05 17:51:53.482 - debug: roborock.0 (606) Cleaning record: {"begin":1673001600,"end":1673001754,"duration":147,"area":3327500,"error":0,"complete":0,"start_type":2,"clean_type":3,"finish_reason":60,"dust_collection_status":0}
2023-02-05 17:51:53.484 - debug: roborock.0 (606) dps debug: {"id":45,"result":[{"begin":1674996181,"end":1674996183,"duration":2,"area":0,"error":0,"complete":0,"start_type":2,"clean_type":1,"finish_reason":43,"dust_collection_status":0}]}
2023-02-05 17:51:53.485 - debug: roborock.0 (606) Cleaning record: {"begin":1674996181,"end":1674996183,"duration":2,"area":0,"error":0,"complete":0,"start_type":2,"clean_type":1,"finish_reason":43,"dust_collection_status":0}
2023-02-05 17:51:53.487 - debug: roborock.0 (606) dps debug: {"id":49,"result":[{"begin":1674725026,"end":1674725079,"duration":41,"area":920000,"error":0,"complete":0,"start_type":2,"clean_type":3,"finish_reason":43,"dust_collection_status":0}]}
2023-02-05 17:51:53.488 - debug: roborock.0 (606) Cleaning record: {"begin":1674725026,"end":1674725079,"duration":41,"area":920000,"error":0,"complete":0,"start_type":2,"clean_type":3,"finish_reason":43,"dust_collection_status":0}
2023-02-05 17:51:53.513 - debug: roborock.0 (606) dps debug: {"id":51,"result":[{"begin":1674470400,"end":1674473247,"duration":2847,"area":45627500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.514 - debug: roborock.0 (606) Cleaning record: {"begin":1674470400,"end":1674473247,"duration":2847,"area":45627500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.515 - debug: roborock.0 (606) dps debug: {"id":60,"result":[{"begin":1672656000,"end":1672658889,"duration":2888,"area":45622500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.516 - debug: roborock.0 (606) Cleaning record: {"begin":1672656000,"end":1672658889,"duration":2888,"area":45622500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.518 - debug: roborock.0 (606) dps debug: {"id":54,"result":[{"begin":1673865601,"end":1673868654,"duration":3053,"area":45852500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.518 - debug: roborock.0 (606) Cleaning record: {"begin":1673865601,"end":1673868654,"duration":3053,"area":45852500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.520 - debug: roborock.0 (606) dps debug: {"id":47,"result":[{"begin":1674725138,"end":1674730242,"duration":5104,"area":46190000,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.521 - debug: roborock.0 (606) Cleaning record: {"begin":1674725138,"end":1674730242,"duration":5104,"area":46190000,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.522 - debug: roborock.0 (606) dps debug: {"id":57,"result":[{"begin":1673260802,"end":1673263712,"duration":2910,"area":45922500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.523 - debug: roborock.0 (606) Cleaning record: {"begin":1673260802,"end":1673263712,"duration":2910,"area":45922500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.525 - debug: roborock.0 (606) dps debug: {"id":56,"result":[{"begin":1673433600,"end":1673436525,"duration":2925,"area":45552500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.525 - debug: roborock.0 (606) Cleaning record: {"begin":1673433600,"end":1673436525,"duration":2925,"area":45552500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.527 - debug: roborock.0 (606) dps debug: {"id":59,"result":[{"begin":1672828801,"end":1672831852,"duration":3051,"area":45580000,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.528 - debug: roborock.0 (606) Cleaning record: {"begin":1672828801,"end":1672831852,"duration":3051,"area":45580000,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.529 - debug: roborock.0 (606) dps debug: {"id":55,"result":[{"begin":1673606401,"end":1673609286,"duration":2885,"area":45722500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.530 - debug: roborock.0 (606) Cleaning record: {"begin":1673606401,"end":1673609286,"duration":2885,"area":45722500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:53.532 - debug: roborock.0 (606) dps debug: {"id":53,"result":[{"begin":1674038400,"end":1674041195,"duration":2795,"area":45662500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}]}
2023-02-05 17:51:53.533 - debug: roborock.0 (606) Cleaning record: {"begin":1674038400,"end":1674041195,"duration":2795,"area":45662500,"error":0,"complete":1,"start_type":2,"clean_type":3,"finish_reason":56,"dust_collection_status":0}
2023-02-05 17:51:55.655 - debug: roborock.0 (606) dps debug: {"id":19,"result":[[1672997413,1673001003,3590,49637500,0,1,3,1,52]]}
2023-02-05 17:51:55.655 - debug: roborock.0 (606) Cleaning record: [1672997413,1673001003,3590,49637500,0,1,3,1,52]
2023-02-05 17:51:55.660 - debug: roborock.0 (606) dps debug: {"id":23,"result":[[1671787813,1671790923,3110,49825000,0,1,3,1,52]]}
2023-02-05 17:51:55.661 - debug: roborock.0 (606) dps debug: {"id":29,"result":[[1669973412,1669976671,3259,46082500,0,1,3,1,52]]}
2023-02-05 17:51:55.662 - debug: roborock.0 (606) Cleaning record: [1671787813,1671790923,3110,49825000,0,1,3,1,52]
2023-02-05 17:51:55.663 - debug: roborock.0 (606) Cleaning record: [1669973412,1669976671,3259,46082500,0,1,3,1,52]
2023-02-05 17:51:55.665 - debug: roborock.0 (606) dps debug: {"id":21,"result":[[1672392612,1672395976,3364,49215000,0,1,3,1,52]]}
2023-02-05 17:51:55.665 - debug: roborock.0 (606) Cleaning record: [1672392612,1672395976,3364,49215000,0,1,3,1,52]
2023-02-05 17:51:55.667 - debug: roborock.0 (606) dps debug: {"id":24,"result":[[1671528612,1671532019,3407,50010000,0,1,3,1,52]]}
2023-02-05 17:51:55.668 - debug: roborock.0 (606) Cleaning record: [1671528612,1671532019,3407,50010000,0,1,3,1,52]
2023-02-05 17:51:55.670 - debug: roborock.0 (606) dps debug: {"id":26,"result":[[1670923813,1670927298,3485,49352500,0,1,3,1,52]]}
2023-02-05 17:51:55.672 - debug: roborock.0 (606) dps debug: {"id":20,"result":[[1672738213,1672740996,2783,46985000,0,1,3,1,52]]}
2023-02-05 17:51:55.672 - debug: roborock.0 (606) Cleaning record: [1670923813,1670927298,3485,49352500,0,1,3,1,52]
2023-02-05 17:51:55.673 - debug: roborock.0 (606) Cleaning record: [1672738213,1672740996,2783,46985000,0,1,3,1,52]
2023-02-05 17:51:55.676 - debug: roborock.0 (606) dps debug: {"id":25,"result":[[1671183013,1671186581,3568,49410000,0,1,3,1,52]]}
2023-02-05 17:51:55.677 - debug: roborock.0 (606) Cleaning record: [1671183013,1671186581,3568,49410000,0,1,3,1,52]
2023-02-05 17:51:55.679 - debug: roborock.0 (606) dps debug: {"id":27,"result":[[1670578212,1670581482,3270,49282500,0,1,3,1,52]]}
2023-02-05 17:51:55.680 - debug: roborock.0 (606) dps debug: {"id":28,"result":[[1670319013,1670322818,3805,49747500,0,1,3,1,52]]}
2023-02-05 17:51:55.681 - debug: roborock.0 (606) Cleaning record: [1670578212,1670581482,3270,49282500,0,1,3,1,52]
2023-02-05 17:51:55.681 - debug: roborock.0 (606) Cleaning record: [1670319013,1670322818,3805,49747500,0,1,3,1,52]
2023-02-05 17:51:55.683 - debug: roborock.0 (606) dps debug: {"id":30,"result":[[1669714213,1669717794,3581,49802500,0,1,3,1,52]]}
2023-02-05 17:51:55.683 - debug: roborock.0 (606) Cleaning record: [1669714213,1669717794,3581,49802500,0,1,3,1,52]
2023-02-05 17:51:55.685 - debug: roborock.0 (606) dps debug: {"id":22,"result":[[1672133412,1672136620,3208,49212500,0,1,3,1,52]]}
2023-02-05 17:51:55.685 - debug: roborock.0 (606) Cleaning record: [1672133412,1672136620,3208,49212500,0,1,3,1,52]
2023-02-05 17:51:55.695 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.8.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:55.697 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.8.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:55.698 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.8.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:55.699 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.8.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:55.700 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.8.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:55.701 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.8.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:55.702 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.8.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:55.703 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.8.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:55.704 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.8.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.540 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.12.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.602 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.12.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.603 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.12.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.604 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.12.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.605 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.12.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.606 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.12.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.607 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.12.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.608 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.12.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.608 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.12.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.609 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.18.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.610 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.18.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.611 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.18.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.611 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.18.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.612 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.18.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.613 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.18.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.614 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.18.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.615 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.18.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.616 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.18.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.617 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.10.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.618 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.10.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.619 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.10.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.619 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.10.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.627 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.10.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.628 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.10.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.628 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.10.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.629 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.10.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.632 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.10.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.633 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.13.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.634 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.13.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.634 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.13.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.635 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.13.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.636 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.13.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.637 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.13.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.638 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.13.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.639 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.13.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.639 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.13.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.640 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.15.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.642 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.15.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.643 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.15.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.644 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.15.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.646 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.15.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.647 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.15.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.648 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.15.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.649 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.15.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.649 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.15.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.650 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.9.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.651 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.9.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.652 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.9.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.652 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.9.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.653 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.9.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.654 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.9.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.655 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.9.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.655 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.9.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.658 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.9.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.660 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.14.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.661 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.14.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.662 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.14.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.663 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.14.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.664 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.14.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.665 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.14.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.666 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.14.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.666 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.14.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.667 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.14.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.668 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.16.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.669 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.16.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.669 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.16.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.670 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.16.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.671 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.16.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.671 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.16.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.672 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.16.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.673 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.16.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.674 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.16.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.674 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.17.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.675 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.17.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.676 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.17.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.677 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.17.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.677 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.17.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.678 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.17.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.679 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.17.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.680 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.17.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.681 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.17.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.681 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.19.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.682 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.19.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.683 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.19.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.683 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.19.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.684 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.19.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.685 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.19.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.685 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.19.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.686 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.19.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.687 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.19.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.688 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.11.0" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.688 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.11.1" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.689 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.11.2" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.690 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.11.3" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.690 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.11.4" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.691 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.11.5" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.692 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.11.6" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.693 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.11.7" has no existing object, this might lead to an error in future versions
2023-02-05 17:51:56.693 - warn: roborock.0 (606) State "roborock.0.Devices.5hMBOgcFv6CIHdkwW59ObV.cleaningInfo.Records.11.8" has no existing object, this might lead to an error in future versions
2023-02-05 17:52:10.088 - info: host.raspberrypi-gang "system.adapter.roborock.0" disabled
2023-02-05 17:52:10.089 - info: host.raspberrypi-gang stopInstance system.adapter.roborock.0 (force=false, process=true)
2023-02-05 17:52:10.093 - silly: roborock.0 (606) States system redis pmessage io.system.adapter.roborock.0.sigKill/io.system.adapter.roborock.0.sigKill:{"val":-1,"ack":false,"ts":1675615930091,"q":0,"from":"system.host.raspberrypi-gang","lc":1675615930091}
2023-02-05 17:52:10.098 - info: host.raspberrypi-gang stopInstance system.adapter.roborock.0 send kill signal
2023-02-05 17:52:10.094 - info: roborock.0 (606) Got terminate signal TERMINATE_YOURSELF
2023-02-05 17:52:10.095 - info: roborock.0 (606) terminating
2023-02-05 17:52:10.097 - info: roborock.0 (606) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-02-05 17:52:10.808 - info: host.raspberrypi-gang instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

Folgende Objekte werden angelegt, aber nicht mit Werten bestückt:

OK. Den Fehler kenne ich bereits. Ich dachte, dass der nur beim S5 und alter Auftritt. Dann muss ich das für den s6 ebenfalls machen. Das geht schnell und kann ich heute Abend machen.

https://github.com/copystring/ioBroker.roborock/tree/s4_to_s6_uses_old_standard
Damit läuft hoffentlich alles. Die Roborock S4 bis S6 nutzen anscheinend einen anderen Standard.

Ach ok, dann ist ja alles wie erwartet. Danke fürs wie immer schnelle Beheben 👍

Gern. Fixed via https://github.com/copystring/ioBroker.roborock/pull/64


Use CodeMirror Kotlin

Looks like CodeMirror already had a Kotlin mode ready to go, it was just hidden under some MIME types. This gets rid of the unnecessary kotlin.js custom mode, and allows for the addition of more languages that need MIME types (Java, C#, C++, Scala, etc.).

What if we just configure MIME modes like:
{
  "name": "Kotlin",
  "mime": "text/x-kotlin"
}

and them import as require(language.module || language.mime)?

Actually, now I see what is happening. MIME types don't need to be imported. @briandennis how do we want to distinguish types like this?

I think the easiest way to do this might be to have MIME and module since you can have the case where a MIME's corresponding mode may not already be imported by another language.
We should also probably rename module field to mode to avoid confusion.
{
  name: "Kotlin",
  mode: "clike",
  mime: "text/x-kotlin"
}

Logic for requireing modes: keep a set of modes that have already been required, don't require it again if it's already been added
Logic for setting language in CodeMirror component: If language has a mime, pass that. Otherwise, pass the mode.

How will we deal with the auto detected language being kotlin when the mode is clike?

Alright here's a summary of the changes I've made:

Use mode instead of module
If mime is defined, use that instead of mode
Only require modes once
For auto detection of languages, add a short property if the mime makes the language different from the mode. The short property will be used if no language could be found searching the modes.


Use of unresolved identifier 'linkingObjects'

I tried adding Realm v1.0 to my Swift projects when I came across this.
Goals
Add Realm v1.0 to my Swift project.
Expected Results
Successful add Realm to the Swift project.
Actual Results
Got this build error.

Use of unresolved identifier 'linkingObjects'

Steps to Reproduce

Create brand new Swift project.
Set the Deployment Target to iOS 8.
Initialize CocoaPods for the project. Below is my Podfile.

platform :ios, '8.0'

target 'RealmTestDrive' do
  use_frameworks!

  pod 'RealmSwift', '~> 1.0'

end

Run pod install. I have CocoaPods v1.0.1 installed on my Mac.
Build the project after successful CocoaPods installation.

Code Sample
This is the model class where the error is present. I've attached a demo Xcode project below.
import Foundation
import RealmSwift

class Service: Object {

    dynamic var id: Int = 0
    dynamic var title: String = ""
    dynamic var desc: String = ""
    dynamic var price: Float = 0
    dynamic var windowStyle: WindowStyle?

    var parts: [Part] {
        return linkingObjects(Part.self, forProperty: "services") // This is the error line
    }

    override static func primaryKey() -> String? {
        return "id"
    }

    override var description: String {
        return title
    }
}

https://www.dropbox.com/s/c85bkhc446780tz/RealmTestDrive.zip?dl=0
Version of Realm and Tooling
ProductName:	Mac OS X
ProductVersion:	10.11.5
BuildVersion:	15F34

/Applications/Xcode.app/Contents/Developer
Xcode 7.3
Build version 7D175

/usr/local/bin/pod
1.0.1
Realm (1.0.0)
RealmSwift (1.0.0)
RealmSwift (~> 1.0)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin15)

/usr/local/bin/carthage
0.16.2
(not in use here)

/usr/bin/git
git version 2.6.4 (Apple Git-63)

I tried deleting Derived Data folder, cleaning and building, the whole nine yards several times. I even uninstalled all versions of CocoaPods I had in my machine plus deleted the ~/.cocoapods directory and reinstalled CocoaPods anew. Tried this many times too. But nothing worked.

Read the 1.0 release notes. linkingObjects has changed in 1.0
https://realm.io/docs/swift/latest/#inverse-relationships
Replace:
var parts: [Part] {
return linkingObjects(Part.self, forProperty: "services")
}
with:
let parts = LinkingObjects(fromType: Part.self, property: "services")

I am going to hop in here.
I too have updated to Realm 1.0.1 and changed the lines where i had to with the new code (see post above by @jamikado).
Unfortunately I now get an empty list where I got some result with the Realm version I used before.
Nothing else was changed. Is this known?

@ilendemli glad you worked it out, and sorry for the confusion. Realm models should be defined exactly as the documentation describes: https://realm.io/docs/swift/latest/#models
We hope to see further improvements to Swift's reflection mechanism that would allow us to be more flexible with how users define models. If you agree, please file a radar or a Swift bug and we'll be happy to dupe or 👍.
I'll be closing this issue since it seems everyone who's chimed in has since been able to adapt their models to conform to the necessary syntax.


Finding default settings.json doesn't work for my work laptop

I've tried putting Comi/settings.json in:

normal user docs
admin user docs
OneDrive docs

Specifying the path still doesn't work actually

#12 would help debug this

fixed in commit fe6bab1


Program always fails due to hang

Before I run the afl-fuzz I am able to run my target executable with drrun.exe. But no matter what I do with the timeout passed to afl-fuzz.exe, the test case always results in a hang.  Any suggestions to check out?

 Problems like this can be caused by an incorrect target offset. A hang in winafl means that the target didn't respond correctly which can happen because of a timeout but can also happen for other reasons (I realize error messages might be misleading in those cases).

Hi Ivan, thanks for the suggestions!  I actually got it working because I was using the offset in the file for the WinMain function, and not the actual offset from the image module base.  Now that I have the correct nargs and target_offset it is working great!

@msftsecurityteam  I think I am facing the same problem .. how can I get the actual offset from the image module base??  I am trying to fuzz the main function .. I opened IDA Pro and the address of the function something similar to .text:00000000004014F0 then I used the offset to be 0x14F0 but I still getting time outs ..


fix(CompiledRouter): support URI templates with a trailing slash

Summary of Changes
Previously, the default CompiledRouter was erroneously stripping trailing slashes from URI templates.
This has been fixed so that it is now possible to add two different routes for a path with and without a trailing forward slash.
Related Issues
Closes #1544
Open Questions
I'm a bit divided what to do with add_route() in case RequestOptions.strip_url_path_trailing_slash is set to True, and the provided template ends with a trailing slash?

Do nothing special, effectively adding a non-functional route that is never hit (this may be a breaking change is someone had such a route).
Raise a ValueError asking to only add routes without a trailing slash (this may be a breaking change is someone had such a route).
Strip the trailing slash from the template before submitting it to the router's add_route().
Strip the trailing slash from the template before submitting it to the router's add_route(), and emit a deprecation warning.
Something else?

I have now proceeded with the first option, documenting this as a breaking change, and sprinkling some warnings throughout the docs. Thanks @CaselIT for input!

Regarding the question, the problem I see is that we cannot assume that an user has set the options before adding the routes. Also the options may be dynamically updated.
Taking this into consideration, I don't think a warning should be raised, we should just document, maybe with a warning, the behaviour of the router wrt that request option.

Ah, good point wrt the configuration order @CaselIT !
RequestOptions.strip_url_path_trailing_slash is by default False, so if the user hasn't set that to True yet, we obviously cannot do anything about it. But if the user has already overridden to True, I am inclined to emit a warning though, that might be helpful in debugging... :thinking:

The documentation looks good 👍

@kgriffs good point; I have now added a dedicated test to better exercise this scenario.


cargo build and cargo install -f write Cargo.lock differently

Given the following repo: https://github.com/oconnor0/build-your-own-editor/tree/24586c991a7faa513723595164df544e7c81ae73
When I run cargo build from the root, the Cargo.lock is written out one way.
When I run cargo install -f from the root, the Cargo.lock is written in a different way.
They are consistent - so that if I run cargo build, git will show no changed. If I then run cargo install -f, I see changes in Cargo.lock. Running cargo build again shows no changes.
There are only two Cargo.toml in the repository:
At the root:
[package]
name = "build-your-own-editor"
version = "0.0.1"
authors = ["Matthew O'Connor<EMAIL_ADDRESS>
[dependencies]
textbox = { path = "textbox" }

[workspace]
members = [".", "textbox"]

[replace]
"winapi:0.2.8" = { git = "https://github.com/oconnor0/winapi-rs.git", rev = "textbox" }
"wio:0.1.2" = { git = "https://github.com/oconnor0/wio-rs.git", rev = "textbox" }

Inside the textbox directory:
[package]
name = "textbox"
version = "0.0.1"
authors = ["Matthew O'Connor<EMAIL_ADDRESS>workspace = ".."

[dependencies]
bitflags = "*"
bit-set = "*"
num-traits = "*"

[target.'cfg(windows)'.dependencies]
winapi = "0.2.8"
wio = "0.1.2"
kernel32-sys = "*"

[target.'cfg(unix)'.dependencies]
termbox-sys = "*"

Interesting! Could you gist the diff between the two lock files?

https://gist.github.com/oconnor0/c64d3a95fb5784fb2f485e46fec01df1

Thanks! Confirms my suspicions and fixed in https://github.com/rust-lang/cargo/pull/3146


[BUG] make letsencrypt expects certbot, while not installed

Describe the bug
make letsencrypt is expecting an venv in /opt/certbot/bin/ and certbot installed, while neither might not be present.
Devcontainer has steps to setup venv and install certbot; these should be part of base make scripts as well so that CD can utilize them as well.
Steps to reproduce

run make letsencrypt on blank WSL/Linux machine

@deniscep  is this to check for the prerequisites as we do with terraform and docker, or to actually install it? If to install then we should do all prerequisites?

Add as prereq to docs.


What is OMCI_CUSTOM_RDP?

Previously, I have a DFP-34X-2C2 using software version V1.0-220304.  I configure the GPON to access to Maxis or Unifi with these minimum configuration:
flash set GPON_PLOAM_FORMAT 1
flash set GPON_PLOAM_PASSWD <hex code>
flash set OMCI_TM_OPT 0

I purchase another DFP-34X-2C2 recently using software version V1.0-220414 but perform the above setting doesn't allow me to get thru PPPoE authentication.  The GPON do show O5 state.
After compare and try all OMCI value of both GPON device one by one, the new GPON works with the additional OMCI_CUSTOM_RDP setting:
flash set GPON_PLOAM_FORMAT 1
flash set GPON_PLOAM_PASSWD <hex code>
flash set OMCI_TM_OPT 0
flash set OMCI_CUSTOM_RDP 4

I couldn't find any information about OMCI_CUSTOM_RDP.  Do you know what is this for?

The firmware startup scripts refer to it as "custom route" ( I do not know in this context what it means)
and the default on firmware 220414 is 4...

Yes. Both stick show same OltVendorId.  Any clue?

I also use 220414

# flash get OMCI_CUSTOM_RDP
OMCI_CUSTOM_RDP=4

and OLT is 0x414c434c = Nokia
if I factory reset, OMCI_CUSTOM_RDP still same value 4
every OLT has different effect, mine need HW_HWVER then can be use, if I use Nokia HW_HWER, I need put other OMCI info to work...
So, I need to know what your OLT id is, Huawei or ZTE or Ericsson or something else...

I thought OLT is device of ISP?  I have no control of it.

I thought OLT is device of ISP? I have no control of it.

well ..yes the olt is at the fiber operator side.. @Anime4000 has the same ISPs as you, but because reasons ISPs are not homogenous, the have OLTs configured diffferently or running different brands, This is in most cases due to inertia (if it aint broke dont fix it) or they have special requirements etc.. this usually translates into a shit show and larger long term mainteniance costs  ..the world aint perfect out there..

I perform reset to factory on my new GPON and notice the value OMCI_CUSTOM_RDP is 4.
I think the vendor ship a GPON with dirty configuration.

@ccy
I see, it seem good to backup the key and factory reset after receiving the Stick.
yet, we still wondering with RDP parameters...
I feel OMCI_CUSTOM_RDP is like how many virtual LAN port? maybe not...
no information on this...

OMCI_CUSTOM_BDP controls which bdp_xxx.so/.ko plugins get loaded
OMCI_CUSTOM_RDP controls which rdp_xxx.so/.ko plugins get loaded
OMCI_CUSTOM_MCAST controls which mc_xxx.so/.ko plugins get loaded
OMCI_CUSTOM_ME controls which me_xxx.so/.ko plugins get loaded
each of these "plugins" makes a small tweak to some internal function/"feature", and getting the values of these flags right might be important
additionally, the DEVICE_TYPE value controls a lot too, 0 = bridge, 1 = router, 2 = hybrid, and unless it is set to bridge, a lot of things are skipped (like making pon0 iface and adding it to bridge), its not just for reporting to OLT

I'm maintaining a list of all the available features (described as function names inside the modules) here:
https://gist.github.com/rajkosto/79034a1f7b3de3f40edf50ffbd8396b0


[Improvement]: Improve error message when there is a mismatch in worker send and recevie pairing

Description
$subject.
function foo() {
    boolean foo = true;

    worker w1 {
        20 -> w2;
    }

    worker w2 {
    }

}

This above code gives,
ERROR [test_parser.bal:(21:15,23:6)] worker send/receive interactions are invalid; worker(s) cannot move onwards from the state: '[20 -> w2, FINISHED, FINISHED]'

We need to give a meaningful error message.

Fixed in #41999


Rethink edit attributes vs edit geometry mode

#108 introduced two different modes, edit attributes (for stuff in the sidebar) and edit geometry (for the geospatial representation). The motivation was that the form was going to soon outgrow the sidebar and become a modal.
I'd like to revisit that design choice, after the UX session with Kelin. I think one "Edit" mode (or "select" or some other name) is fine. Clicking or selecting an object would activate the appropriate controls on the map, but ALSO open up the form in the sidebar. If our forms ever outgrow the sidebar, we simply add a prominent button there to pop-out into a full modal and cover part/all of the map. If a user is trying to fill out this larger form for many objects, we can even have some kind of "sticky" behavior about showing that bigger modal by default or not.
Thoughts?

I don't fully understand the suggestion but my thinking is that, given that the attribute editing form will grow, it makes sense to keep geometry editing and attribute editing functionality separate.

Try a quick prototype at https://acteng.github.io/atip/merge_edit/scheme.html?authority=Adur (give it a few mins to deploy, and keep in mind there are lots of bugs left in this -- it's just a quick example)
https://github.com/acteng/atip/assets/1664407/eea6ece2-ad51-4985-a29f-f17b2e06ad37
Even in the current approach with a separate "Edit attributes", we're only using the sidebar. The idea with the new approach is that we'd add a new button to show a full-screen form:

I've seen a few people get confused by the two separate edit modes, and when using ATIP myself, it's a bit frustrating to switch back and forth.

Amazing progress Dustin! I'm in strategy mode but will aim to test soon.

Thanks Stuart! You've got me thinking about a few other old ideas for simplifying the UX flow... One note -- we don't have the ability (or any intended use case for this) to select multiple features at a time today.
Thinking through the UX again... this idea of a list and a focus view really sounds solid:
List view

The left sidebar lists all features and has the file management / scheme-wide forms (possibly as a modal, if they grow to include more)
The map shows all features
Clicking one feature either from the sidebar or map switches into the focus view
The current toolbox on the right changes to just have options for "New point / route / freehand polygon / snapped polygon". Or if we settle on a better taxonomy for what we want people to map, maybe more semantic categories (crossing, school street, junction improvement, side road treatment, etc) that launch the appropriate geometric tool.

Focus view on one existing feature at a time:

The left sidebar is just the form for that one feature, with nothing else shown
When first creating a new feature, maybe this form is disabled until the user has drawn enough geometry
The right toolbox changes to only show map controls for the current geometry type. This will free up some visual room to be much more explicit about switching between freehand and snapped mode for route-drawing, for example.
Other features in the map can be drawn faded out, and won't be selectable at all
Prominent "Save", "Undo / revert", "Delete" buttons to change states back to the list view

I'm not entirely sure where something like the split route tool belongs. Probably as a possible mode when focusing on one existing route.
Any thoughts on this design? It'll be a substantial code change, and I'd prefer to not invest much in it without confidence this is nice. Would low-fi mockups be useful first? @robinlovelace-ate, any opinions on this big re-design?

Sounds good to me! Looking at the current ATIP Sketch tool (which this relates to more than browse tool):
Authority landing page

In edit mode, this will be better with New point / route / polygon (will be UX win if they can be merged, e.g. by making Shift -> freehand mode like the route tool which is working really nice now) on the right but no huge change right?

In list mode:

Agreed, there's TMI in the left panel which overflows. +1 to showing only one feature. Hope that's helpful..

Please try out https://acteng.github.io/atip/focus_mode_mvp/scheme.html?authority=Adur. This is a quick demo of some of these ideas -- the sidebar and toolbox both change when you're editing or drawing something. This is a rough sketch of this idea, but any thoughts on it? Is this worth pursuing?

Tried it. Really like it, way better on small screens and allows more focus on job at hand. Didn't detect any downside.

Edit modes merged a while ago


 There's not much deep static analysis determining whether something later on gets called internally/privately.
It does seems like fat arrows in local/private functions should be valid as it returns the class/object rather than this, so maybe the rule should have been sussed out better.
That said, I suppose you should just turn this off in your case, or directly call it as URL::. If I'm interpreting this issue wrong feel free to point that out. Otherwise I'm not sure what else can be done to fix this.


app update fails with exit status 100 on fedora 40

i've made sure that

[x] there is no existing issue about the same topic
[x] read the prerequisites

here is the showcase video
https://github.com/user-attachments/assets/ca5a1a89-4265-4531-bac4-a7163f9708c6

Thanks for bringing this up. According to the dnf man page:
exit code will be 100 when there are updates available and a list of the updates will be printed, 0 if not and 1 if an error occurs.

So I guess what I need to do is to not throw an error if dnf check-update returns 100. Will get this fixed on the next release.

v0.20 should have fixed this.


chore(governance): add Lambda Powertools for .NET in issue templates

Issue number: #2195
Summary
Changes
The Powertools for .NET link is missing from the template issues so I added this.
User experience

Please share what the user experience looks like before and after this change

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[x] Meet tenets criteria
[x] I have performed a self-review of this change
[ ] Changes have been tested
[ ] Changes are documented
[x] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

thanks a lot @leandrodamascena for the attention to detail <3


Startup issue - Clickhouse DB Connection

Hey,
I tried to spin up the docker environment and im having the following error which I cannot resolve. It seems that the plausible_events_db container is not reachable.
Loading plausible..
Starting dependencies..
Starting repos..
create Plausible.Repo database if it doesn't exist
create Plausible.ClickhouseRepo database if it doesn't exist
13:47:45.948 [error] Clickhousex.Protocol (#PID<0.244.0>) failed to connect: ** (ErlangError) Erlang error: :econnrefused
13:47:45.948 [error] Clickhousex.Protocol (#PID<0.245.0>) failed to connect: ** (ErlangError) Erlang error: :econnrefused
13:47:45.962 [error] GenServer #PID<0.265.0> terminating
** (UndefinedFunctionError) function :econnrefused.exception/1 is undefined (module :econnrefused is not available)
    :econnrefused.exception([])
    (db_connection 2.2.2) lib/db_connection/connection.ex:87: DBConnection.Connection.connect/2
    (connection 1.0.4) lib/connection.ex:622: Connection.enter_connect/5
    (stdlib 3.12.1) proc_lib.erl:249: :proc_lib.init_p_do_apply/3
Last message: nil

[... repeat former block * 4]

** (MatchError) no match of right hand side value: {:error, "killed"}
    (plausible 0.0.1) lib/plausible_release.ex:56: anonymous fn/2 in Plausible.Release.createdb/0
    (elixir 1.10.3) lib/enum.ex:2111: Enum."-reduce/3-lists^foldl/2-0-"/3
    (plausible 0.0.1) lib/plausible_release.ex:55: Plausible.Release.createdb/0
    (stdlib 3.12.1) erl_eval.erl:680: :erl_eval.do_apply/6
    (elixir 1.10.3) lib/code.ex:341: Code.eval_string_with_error_handling/3

In the beginning the server couldn't even bind to the requested IPv6 address. So I instructed it to bind on IPv4 in two ways like this in clickhouse-config.xml
<yandex>
    ...
    <listen_host><IP_ADDRESS></listen_host> // <listen_host><IP_ADDRESS></listen_host>
    ...
</yandex>

Due to the sparse log of where it tried to connect I set the upstream manually like this in plausible-conf.env. Still no luck.
CLICKHOUSE_DATABASE_URL=http://plausible_events_db:8123/plausible_events_db

I got it working by setting it to:
<listen_host><IP_ADDRESS></listen_host>

See PR https://github.com/plausible/hosting/pull/21

Totally confused now. I checked out everything in a new folder. Only applied the patch you mentioned and it works. Probably a docker error down the testing line. The configuration is working. Thanks for confirming.


feat: support stream route plugin

Type of change:

[ ] Bugfix
[x] New feature provided
[ ] Improve performance
[ ] Backport patches

What this PR does / why we need it:
Resolved #744

Codecov Report

Merging #918 (0debbb9) into master (75098d1) will increase coverage by 0.12%.
The diff coverage is 27.77%.

@@            Coverage Diff             @@
##           master     #918      +/-   ##
==========================================
+ Coverage   31.90%   32.03%   +0.12%
==========================================
  Files          72       72
  Lines        7899     7917      +18
==========================================
+ Hits         2520     2536      +16
  Misses       5103     5103
- Partials      276      278       +2

Impacted Files
Coverage Δ

pkg/kube/translation/apisix_route.go
24.45% <27.77%> (+2.01%)
:arrow_up:

Continue to review full report at Codecov.

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

You can add this feature to ApisixRoute v2, thanks

Sorry I've been a little busy lately, I'll improve this PR in this week.

@Belyenochi thanks!

Sorry I've been a little busy lately, I'll improve this PR in this week.

@Belyenochi friendly reminder :smile_cat:

Thanks for your contribution, as #1056 is more complete and has been merged, I will close this PR.
Looking forward to your continued activity


Open /dev/urandom before chroot

This is necessary on systems that don't have getrandom, such as BSDs and
Linux pre 3.17.

Closed in favor of #291
Justin points out that this will not work with installs that use the system mbedTLS


Refactor of the neural sparse search tutorial

Description
Recently we get the feedback that it's hard to find using neural sparse search with raw sparse vectors in existing documentations. Besides, the neural sparse search tutorial is not well structured compared with neural search tutorial.
This PR refact the neural sparse search tutorial. Mainly for these points:

Using seperate sections neural sparse search with built-in pipelines and with raw sparse vectors
Add a seperate sub section about Set up an ML sparse encoding model. It takes a ref from https://opensearch.org/docs/latest/search-plugins/neural-search-tutorial/#step-1-set-up-an-ml-language-model, but with more contents about 2 working mode in neural sparse, and a table to show the model combinations we offer in OpenSearch (we'll release v2 models soon, and present the combinations in a table will be more clear)
Refact the sections/subsections structure to give a more clear view

Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
Version
2.15, 2.16
Frontend features
If you're submitting documentation for an OpenSearch Dashboards feature, add a video that shows how a user will interact with the UI step by step. A voiceover is optional.
Checklist

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

This PR is ready for review, thanks!


Mod Dont Load

https://pastebin.com/jE9zHnnN
From ym Latest log because no crashlog

Should be fixed in 1.0.1 (1.18.2)/1.1.1 (1.19.2), give curseforge about an hour to approve the updates

still doesn't load on  1.1.1

i see the mod on the modlist and the keybind but no button and the keybind action doesn't trigger anything

@genesy Anything in your latest.log?

Also both of you: what game version? (1.18.2 or 1.19.2)

Can't give latest.log rn but I'm on 1.19.2

alright, looking into it more. I did code this in like 4 hours with minimal testing...

Wait do you have a crafting table in your inventory

You need that for the button/keybind (for balance, its QOL not a magic step skipper, although maybe I should make that configurable)

Oh i only had crafting table from crafting on a stick maybe. I'll try it again later.

Yeah there is a tag for if you really need that (inventory_crafter:crafting_tables) but I advise just a regular vanilla table item.

Keeping this open because I want to hear from @SugarDaddii, does any update 1.x.1 or above work for you now?

Iam at work right now … can test it again in the afternoon 😁

Its working yes

iam on version 1.1.2 latest

Alright, closing the issue. If your problem occurs even with a vanilla crafting table @genesy open a new issue as I believe it is likely unrelated.


Nx 16 breaks the module-federation schematic

Since version 16 nx switched their package scope from @nrwl to @nx
https://github.com/nrwl/nx/pull/16069
This breaks the module-federation schematic:
 nx g @angular-architects/module-federation:init --type=dynamic-host
 ...
TypeError: Cannot read properties of undefined (reading 'split')
    at new Range (C:\...\module-federation-poc\node_modules\semver\classes\range.js:32:8)
    at Object.minVersion (C:\...\module-federation-poc\node_modules\semver\ranges\min-version.js:6:11)
    at infereNxBuilderNames (C:\...\module-federation-poc\node_modules\@angular-architects\module-federation\src\schematics\mf\schematic.js:130:31)
    at C:\...\module-federation-poc\node_modules\@angular-architects\module-federation\src\schematics\mf\schematic.js:211:36
    at Generator.next (<anonymous>)
    at fulfilled (C:\...\module-federation-poc\node_modules\tslib\tslib.js:164:62)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

 >  NX   Cannot read properties of undefined (reading 'split')

This is in a freshly setup angular nx workspace.
nx version: 16.0.0
angular version: 15.2.0
@angular-architects/module-federation version: 15.0.3

Thanks. Meanwhile, we have version 16 that works with Angular 16 and Nx 16.0 + Nx 16.1. Last time I checked, there was an issue with Nx 16.2 preventing it to work.

Works again with NX 16.2.2


added binary search for c++

Here I made a file for binary search in C++

What a great code :smile: !
Thank you for contributing! :rocket:
Looks like your branch has conflicts with the master, please resolve them, and make sure that your code is original. :smile:


chore: Reduce dependency upgrade frequency to weekly

I feel like we don't need to have our dependencies upgrading daily, especially as our release candency approx. monthly 😄

AWS CodeBuild CI Report

CodeBuild project: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: 8623b5088e1209ea623285cd0e828e32afc624c7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository