Endless loop when calling cover.control in ESPHome or stopping the desk manually

To move the desk with millimeter precision, I created a service, since moving the cover with float values doesn't seem to work with Home Assistant directly.
api:
  password: XXX
  services:
    - service: move_to_position
      variables:
        position: float
      then:
        - cover.control:
            id: idasen_desk
            position: !lambda 'return position/100;'

Often when moving the desk only a small amount it moves to the target position and then keeps trying to move the desk in an endless loop. The same happens when the desk is already at the target position and also if the desk is stopped manually with the old "dumb" control switch while moving.
I think the easiest solution here would be to break the loop if the speed is 0 twice in a row.
Log:
[10:28:02][D][cover:072]: 'AZ Desk Nico' - Setting
[10:28:02][D][cover:080]:   Position: 22%
[10:28:02][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.3 - speed 0.0
[10:28:02][D][idasen_desk_controller:289]: Cover control - START - position 0.2 - target 14.6 - current 14.3
[10:28:02][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.3 - speed 0.0
[10:28:02][D][idasen_desk_controller:274]: Update Desk - Move from 14.3 to 14.6
[10:28:02][D][cover:152]: 'AZ Desk Nico' - Publishing:
[10:28:02][D][cover:155]:   Position: 22%
[10:28:02][D][cover:168]:   Current Operation: OPENING
[10:28:03][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.3 - speed 0.0
[10:28:03][D][idasen_desk_controller:274]: Update Desk - Move from 14.3 to 14.6
[10:28:03][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.3 - speed 12.0
[10:28:03][D][binary_sensor:036]: 'AZ Desk Nico Moving': Sending state ON
[10:28:03][D][idasen_desk_controller:274]: Update Desk - Move from 14.3 to 14.6
[10:28:03][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.6 - speed 0.0
[10:28:03][D][sensor:092]: 'AZ Desk Nico Height': Sending state 76.60000 cm with 1 decimals of accuracy
[10:28:03][D][binary_sensor:036]: 'AZ Desk Nico Moving': Sending state OFF
[10:28:03][D][idasen_desk_controller:274]: Update Desk - Move from 14.6 to 14.6
[10:28:03][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.6 - speed 0.0
[10:28:03][D][idasen_desk_controller:274]: Update Desk - Move from 14.6 to 14.6
[10:28:03][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.6 - speed 0.0
[10:28:03][D][idasen_desk_controller:274]: Update Desk - Move from 14.6 to 14.6
[10:28:04][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.6 - speed 0.0
[10:28:04][D][idasen_desk_controller:274]: Update Desk - Move from 14.6 to 14.6
[10:28:04][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.6 - speed 0.0
[10:28:04][D][idasen_desk_controller:274]: Update Desk - Move from 14.6 to 14.6
[10:28:04][D][idasen_desk_controller:199]: Desk bluetooth data: height 14.6 - speed 0.0
[10:28:04][D][idasen_desk_controller:274]: Update Desk - Move from 14.6 to 14.6
........

Is the new version based on ESPHome BLE Client fixes your issue ?

In the new version, the height sensor never updates and because of that, the script is stuck in an endless loop, too (but the desk stops at the right position if I set a target).
This is the log while and after moving to position:
[20:47:58][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82
[20:47:58][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82
[20:47:58][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82
[20:47:59][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82
[20:47:59][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82
[20:47:59][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82
[20:47:59][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82
[20:47:59][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82
[20:48:00][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82
[20:48:00][D][idasen_desk_controller:194]: Update Desk - Move from 22 to 82

When adding an update_interval, the loop stops, but I don't know if it's the best solution to spam the bluetooth connection with update requests 24/7.

Do you see this error in your logs esp_ble_gattc_register_for_notify failed ?

No, I can't find this  error. I can only see multiple Unhandled type: advType: 0x12
Here's the complete log on verbose level:

Complete Log
[22:20:52][I][app:105]: ESPHome version 1.19.1 compiled on Jun 19 2021, 22:19:45
[22:20:52][C][template.binary_sensor:018]: Template Binary Sensor 'AZ Desk Nico Connection'
[22:20:52][C][template.binary_sensor:018]: Template Binary Sensor 'AZ Desk Nico Moving'
[22:20:52][C][logger:189]: Logger:
[22:20:52][C][logger:190]:   Level: VERBOSE
[22:20:52][C][logger:191]:   Log Baud Rate: 115200
[22:20:52][C][logger:192]:   Hardware UART: UART0
[22:20:52][C][esp32_ble_tracker:606]: BLE Tracker:
[22:20:52][C][esp32_ble_tracker:607]:   Scan Duration: 300 s
[22:20:52][C][esp32_ble_tracker:608]:   Scan Interval: 320.0 ms
[22:20:52][C][esp32_ble_tracker:609]:   Scan Window: 30.0 ms
[22:20:52][C][esp32_ble_tracker:610]:   Scan Type: ACTIVE
[22:20:52][C][ble_client:033]: BLE Client:
[22:20:52][C][ble_client:034]:   Address: XX:XX:XX:XX:XX:XX
[22:20:52][C][ble_sensor:019]: BLE Sensor 'AZ Desk Nico Height'
[22:20:52][C][ble_sensor:019]:   State Class: ''
[22:20:52][C][ble_sensor:019]:   Unit of Measurement: 'cm'
[22:20:52][C][ble_sensor:019]:   Accuracy Decimals: 1
[22:20:52][C][ble_sensor:019]:   Icon: 'mdi:arrow-up-down'
[22:20:52][C][ble_sensor:020]:   MAC address        : XX:XX:XX:XX:XX:XX
[22:20:52][C][ble_sensor:021]:   Service UUID       : 99FA0020338A10-248A-4900-9C02-15F78A
[22:20:52][C][ble_sensor:022]:   Characteristic UUID: 99FA0021338A10-248A-4900-9C02-15F78A
[22:20:52][C][ble_sensor:023]:   Descriptor UUID    :<PHONE_NUMBER>0000-0000-0000-0000-000000
[22:20:52][C][ble_sensor:024]:   Notifications      : YES
[22:20:52][C][ble_sensor:025]:   Update Interval: 4294967.5s
[22:20:52][C][ble_sensor:019]: BLE Sensor 'AZ Desk Nico Speed'
[22:20:52][C][ble_sensor:019]:   State Class: ''
[22:20:52][C][ble_sensor:019]:   Unit of Measurement: 'cm/min'
[22:20:52][C][ble_sensor:019]:   Accuracy Decimals: 0
[22:20:52][C][ble_sensor:019]:   Icon: 'mdi:speedometer'
[22:20:52][C][ble_sensor:020]:   MAC address        : XX:XX:XX:XX:XX:XX
[22:20:52][C][ble_sensor:021]:   Service UUID       : 99FA0020338A10-248A-4900-9C02-15F78A
[22:20:52][C][ble_sensor:022]:   Characteristic UUID: 99FA0021338A10-248A-4900-9C02-15F78A
[22:20:52][C][ble_sensor:023]:   Descriptor UUID    :<PHONE_NUMBER>0000-0000-0000-0000-000000
[22:20:52][C][ble_sensor:024]:   Notifications      : YES
[22:20:52][C][ble_sensor:025]:   Update Interval: 4294967.5s
[22:20:52][C][ethernet:068]: Ethernet:
[22:20:52][C][ethernet:222]:   IP Address: 192.168.XXX.XXX
[22:20:52][C][ethernet:223]:   Hostname: 'az_desk_nico'
[22:20:52][C][ethernet:224]:   Subnet: <IP_ADDRESS>
[22:20:52][C][ethernet:225]:   Gateway: <IP_ADDRESS>
[22:20:52][C][ethernet:236]:   DNS1: <IP_ADDRESS>
[22:20:52][C][ethernet:237]:   DNS2: <IP_ADDRESS>
[22:20:52][C][ethernet:240]:   MAC Address: XX:XX:XX:XX:XX:XX
[22:20:52][C][ethernet:241]:   Is Full Duplex: YES
[22:20:52][C][ethernet:242]:   Link Up: YES
[22:20:52][C][ethernet:243]:   Link Speed: 100
[22:20:52][C][ethernet:070]:   Power Pin: GPIO16 (Mode: OUTPUT)
[22:20:52][C][ethernet:071]:   MDC Pin: 23
[22:20:52][C][ethernet:072]:   MDIO Pin: 18
[22:20:52][C][ethernet:073]:   Type: LAN8720
[22:20:53][C][ota:029]: Over-The-Air Updates:
[22:20:53][C][ota:030]:   Address: az_desk_nico.local:3232
[22:20:53][C][ota:032]:   Using Password.
[22:20:53][C][api:095]: API Server:
[22:20:53][C][api:096]:   Address: az_desk_nico.local:6053
[22:20:53][C][idasen_desk_controller:024]: Idasen Desk Controller:
[22:20:53][C][idasen_desk_controller:025]:   MAC address        : XX:XX:XX:XX:XX:XX
[22:20:53][C][idasen_desk_controller:026]:   Desk 'AZ Desk Nico'
[22:20:53][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:20:54][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:20:54][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:20:55][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:00][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:00][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:01][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:06][D][esp32_ble_tracker:620]: Found device XX:XX:XX:XX:XX:XX RSSI=-99
[22:21:06][D][esp32_ble_tracker:641]:   Address Type: PUBLIC
[22:21:06][D][esp32_ble_tracker:643]:   Name: 'XXXX_XXXXXXX'
[22:21:07][D][cover:072]: 'AZ Desk Nico' - Setting
[22:21:07][D][cover:080]:   Position: 22%
[22:21:07][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:07][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:07][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:07][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:08][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:08][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:08][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:08][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:08][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:08][D][esp32_ble_tracker:620]: Found device XX:XX:XX:XX:XX:XX RSSI=-103
[22:21:08][D][esp32_ble_tracker:641]:   Address Type: RANDOM
[22:21:08][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:09][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:09][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:09][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:09][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:09][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:09][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:10][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:10][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:10][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:10][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:10][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:10][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:11][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:11][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:11][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:11][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:11][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:12][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:12][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:12][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:12][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:12][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:13][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:13][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:13][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:13][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:13][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:14][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:14][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:14][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:14][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:14][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:14][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:15][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:15][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:15][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:15][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:15][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:15][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:15][V][esp32_ble_tracker:591]: Unhandled type: advType: 0x12
[22:21:16][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:16][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:16][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:16][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:16][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:17][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:17][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:17][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:17][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:17][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:18][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:18][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:18][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:18][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:18][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:19][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:19][D][esp32_ble_tracker:620]: Found device XX:XX:XX:XX:XX:XX RSSI=-96
[22:21:19][D][esp32_ble_tracker:641]:   Address Type: PUBLIC
[22:21:19][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:19][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:19][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:19][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:20][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:20][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:20][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:20][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:20][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:21][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:21][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:21][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:21][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:21][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:22][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:22][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:22][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:22][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:22][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[22:21:23][D][idasen_desk_controller:194]: Update Desk - Move from 82 to 22
[...]

Still seems to be an issue in v2.0.1

@noxhirsch is the v2.0.1 fixes some of your problems ?
@spyfly could you share logs after your device just booted ?

@spyfly could you share logs after your device just booted ?
It seems like the issue has been resolved. Desk Height now properly updates both when changing it manually or via HA.

@noxhirsch Have you try the latest release with the option only_up_down_command set to true ?
https://github.com/j5lien/esphome-idasen-desk-controller#not-moving-using-cover-component

@j5lien I just tried that out. Unfortunately, it only made it worse. The height is not updated here either and the desk moves several centimeters past the target.
I think the simplest fallback solution would be to have the cover component periodically trigger a sensor update while the desk is in motion.

It supposed to be the case. When the bluetooth notification can't be setup, it supposed to retrieve the height when the desk moves.
On your log, what notification state can you see ?
[C][idasen_desk_controller:027]:   Notifications      :

Notifications seem to be enabled:
[15:20:59][C][idasen_desk_controller:026]:   Notifications      : enable
Maybe the notification format is slightly different in some countries, so it can not get parsed? @spyfly seems to have the same problem and is also from Germany.

Clicking on the preset of the linak-desk-card sent the controller to the endless loop of "speed 0.0" and I could not interve from the physical controls either. However downloading and compiling a custom version with @noxhirsch's fix was the solution that can be found here: https://github.com/j5lien/esphome-idasen-desk-controller/pull/18 I downloaded his repository and referenced the component using this page as a guide: https://esphome.io/components/external_components.html#external-components-local . I believe I'm in the same situation as @angadsingh that I cannot use the ble_client version.

thanks @hoborm. i had to do the same. 1.2.0 with @noxhirsch's patch is perfect - except no ble notifications so when moving desk manually HA doesn't know its height.

@hoborm & @angadsingh My workaround with the ble_client is to set the update_interval for the sensor to 5s (or faster if you want to "annoy" the desk more ;) ). That way, the manual controls are only "locked" for a few seconds - and additionally you always have the most up to date height, even if you move the desk manually.

thanks @noxhirsch however the ble_client version doesn't even connect to the desk for some of us: https://github.com/j5lien/esphome-idasen-desk-controller/issues/29

I merged @noxhirsch's patch on the v1.2.0 and created the v1.2.1 with it.

@hoborm & @angadsingh My workaround with the ble_client is to set the update_interval for the height sensor to 5s (or faster if you want to "annoy" the desk more ;) ). That way, the manual controls are only "locked" for a few seconds - and additionally you always have the most up to date height, even if you move the desk manually.

Two years later... I had to upgrade my HA Core to HAOS to have it all integrated in 1 RPi instead of scattered throughout my Docker containers. One of the things was upgrading the ESP instance to 7.0 and using the latest controller.
It got stuck updating the height, but with this update_interval it's all smooth as before! Many thanks :)


Logging config could not sync collect because could not detect logging app deploy

Use the wrong context when checking the application deployment

Version: master 2.2 (2/11/19)
Confirmed fix.


move some design docs to rfcs

We have written many design docs internally, and we need to public them to let users know TiKV deeply.

[ ] Raft merge
[x] Batch split #6
[x] ReadPool optimization
[ ] Remove region meta from etcd
[ ] Distributed GC
[ ] Batch message
[ ] Coprocessor chunk
[ ] Raft Local reader
[ ] Region heartbeat optimization
[ ] Follower/Leader read
[ ] Scheduling based on priority
[ ] API check for compatibility rolling update
[ ] Titan - a new engine for RocksDB
[ ] Titan GC
[ ] Joint consensus
[ ] lightning
[ ] PD simulator
[x] PD schedule limit
[ ] Threaded Raftstore
[ ] Failpoint
[ ] Region Consistency check

Please label all PRs for this with the "Migrated RFC" tag so our team can know that it has already been accepted/implemented.

cc @siddontang I'd like to see the design document of -

Joint consensus
Raft Local reader
Follower/Leader read

If any google docs or internal docs can be shared here, I'm glad to port them into English design document for archiving.


Can't send kaspa out of kaspa-ng

Describe the bug
For some reason it say's I have insufficient funds even when I put in significantly less that what I have in the wallet
To Reproduce
Steps to reproduce the behavior:
All I did was input a destination address and go to input the amount I roughly have (so fees can be removed from the remainder of the dust leftover) and it says insufficient funds and won't let me send it.
Expected behavior
Being able to send the funds
Screenshots

Desktop (please complete the following information):

OS: windows 11 home vs. 10.0.22631 build 22631
Kaspad version: kaspa NG v0.2.5-eac0efa + Rusty Kaspa v0.14.1

Additional context
Add any other context about the problem here.

oh additional context. yes the wallet is fully synced.

apparently It works on the remote kaspa node. but not on the integrated daemon

Nevermind it's throwing an error trying to decrypt the wallet

I was initially using the wrong bip39 phrase realized my error fixed it and it still won't decrypt the wallet

I apologize for so many replies I'm just stubborn and still trying things. apparently I still had the bip39 phrase wrong fixed it and it worked on the remote node but I still couldn't get it to allow me to press the send button to get to the point of being able to input the password and bip39 phrase to decrypt the wallet for the transaction on the integrated daemon

This is not a kaspa-ng repository.  Please use https://github.com/aspectron/kaspa-ng/issues to file kaspa-ng related issues.
The "insufficient balance" issue has been fixed at https://kaspa-ng.org and the update for the desktop version is available here:
https://github.com/aspectron/kaspa-ng/releases/tag/v0.2.6-pre-rc1
Decryption problems occur due to incorrect passphrases during creation or subsequent attempts to access the wallet.  If the bip39 passphrase is incorrect, nothing can be done to recover the wallet.  If the wallet passphrase is incorrect, one can use the mnemonic to recover the wallet.


Update FAQ section on saved state.

Fixes issue #585.

+1 from me, but I'd like someone in the Maine Coons to confirm given my comment above.

Tweaked the wording, so back to you to have another look. I also fixed a couple of trivial formatting things on the way past.


VSCode Notebooks: Cells are not being exported due to CRLF and CR line endings

Cells marked #export with CR and CRLF line endings are not being exported. In the example json notebook below only the LF_exports function will be properly exported (Windows 10, Python 3.8). Ran into this with VSCode on Windows which will use CRLF in the Notebook Editor unless Files: Eol is set to \n in File->Preferences->Settings.
{  "cells": [   {    "cell_type": "code",    "execution_count": null,    "metadata": {},    "outputs": [],    "source": [     "# default_exp core"    ]   },   {    "cell_type": "markdown",    "metadata": {},    "source": [     "# module name here\n",     "\n",     "> API details."    ]   },   {    "cell_type": "code",    "execution_count": null,    "metadata": {},    "outputs": [],    "source": [     "#hide\n",     "from nbdev.showdoc import *"    ]   },   {    "cell_type": "code",    "execution_count": 1,    "metadata": {},    "outputs": [],    "source": [     "#export\n",     "def LF_exports(arg):\n",     "    return"    ]   },   {    "cell_type": "code",    "execution_count": 2,    "metadata": {},    "outputs": [],    "source": [     "#export\r",     "def CR_does_not_export(arg):\r",     "    return"    ]   },   {    "cell_type": "code",    "execution_count": null,    "metadata": {},    "outputs": [],    "source": [     "#export\r\n",     "def CRLF_does_not_export(arg):\r\n",     "    return"    ]   }  ],  "metadata": {   "kernelspec": {    "display_name": "Python 3",    "language": "python",    "name": "python3"   },   "language_info": {}  },  "nbformat": 4,  "nbformat_minor": 2 }

This issue is being re-opened because of #432 we cannot just strip all CRLF/CR's from notebooks we have to be more thoughtful as that seems to break other things such as LaTeX.
References: https://github.com/fastai/nbdev/issues/422 and https://github.com/fastai/nbdev/issues/427

Any update on this? Seems to still be happening with 1.1.14

Should be fixed in v2


feature request: ignore specific lines instead of entire file

I would like to mark a line as to be ignored by yamlfmt. Similar to the use of # noqa and similar ignore syntaxes.
I'm using yamlfmt to format CircleCI config files, which references variables as << foo.bar >>  and this should not be reformatted. But when limiting line length to N, yamlfmt will try to break it down in smaller lines.

Hi @Barabazs thanks for the feature request. This is a pretty reasonable request, however it would be really hard to implement given the current architecture of yamlfmt.
Since it (along with some other requested features) likely requires writing a custom yaml parser, it is probably too big of an undertaking for me to try and address it soon. I would like to be able to make it happen some day though. Sorry :disappointed:

Hi @braydonk thank you for  the prompt response. I totally understand and respect your position.
I never programmed in Go, otherwise I might give it a try with some guidance.

Yeah I understand. Even though imo Go is quite an easy language to pick up, this task would probably be quite challenging.
If anything changes and I'm able to spend more than just spare time on this project, then this would likely be the first major thing I take on. So never say never!


python312Packages.tencentcloud-sdk-python: 3.0.1266 -> 3.0.1267

Diff: https://github.com/TencentCloud/tencentcloud-sdk-python/compare/refs/tags/3.0.1266...3.0.1267
Changelog: https://github.com/TencentCloud/tencentcloud-sdk-python/blob/3.0.1267/CHANGELOG.md

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 357551

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.tencentcloud-sdk-python
python311Packages.tencentcloud-sdk-python.dist
python312Packages.tencentcloud-sdk-python
python312Packages.tencentcloud-sdk-python.dist


The composite video is huge.

720P, 30fps, 30 minutes of video is about 1G, is there any way to make the synthesized video smaller?

Lower the bitrate!

Closing this issue, let me know if you need anything else.


Display encrypted files in green (#74)

This is to address issue #74 .  In keeping with the apparent goal of this project, this PR does the minimal thing to address the issue.  Looking at this reveals a lot of housekeeping work though.

In the years since Winfile was maintained, a lot more file attributes have been added.  Winfile has been masking in file system attributes with its own internal bits, meaning that it can't represent many of the new file system changes from the last decade without putting its own bits somewhere else.
There's a documented bug where it assumes that GetFileAttributes returning a value including 0x8000 isn't a directory (in WFIsDir.)  I don't know the origin of that constant, but today it's FILE_ATTRIBUTE_INTEGRITY_STREAM and it can be on a directory (like compression or encryption) to indicate newly created files should have CRC validation (on ReFS.)
This change does not attempt to update the multi-file properties UI to allow encryption state to be changed.  Like compression, this cannot be changed via SetFileAttributes and requires a separate call to EncryptFile/DecryptFile for this task.  If the goal is to also support legacy (pre-2000), this implies a LoadLibrary/GetProcAddress dance.
The existing code already pointed out that the colors are hard-coded, which seems bad in light of other work to provide theming, or that the background color or regular file color is arbitrary.

Nice work.  I would like to see two small additions:

add an "E" at the end of the global szAttr and change PutAttributes() to use it.
add a field to the dialog MULTIPLEATTRIBSDLG to show the Encrypted attribute, but leave the field disabled to indicate it can't be changed.

Quick question: I know that File Explorer can highlight compressed files in blue. Does Winfile do this? If not, we might need to add that eventually.
Also, we would probably need an option to enable or disable color highlighting as File Explorer does.

Actually it is WinFile that shows compressed files as blue; explorer does not show any color (at least on my system) for compressed or encrypted files. Explorer does show a different icon for those types of files.

Explorer displayed compressed files in blue for a long time; the icon is a recent thing (Win8?)  Since compression arrived in NT 3.51, I'd go ahead and guess winfile had it first.
As far as the rest, I guess I'm struggling with what the scope of a good PR is.  This project is fairly new (in the team sense) so there's still some things to figure out about how to work effectively together.  I made this PR intentionally minimal because I thought that was the request (from "what makes a good PR": "Can we keep PR focused on one type and one issue at a time?")  But given the comments from three people, there's no dispute that there are a lot of related enhancements to make - the question is, do you want me to submit all related changes in a single PR?  (Think carefully/be careful what you wish for.)  I don't disagree that encryption support would be much better with multi select properties UI, displayed attributes, a persistent option to disable color, or color selection, etc.
Also, I spent a fair amount of time tracking down what happened in WFIsDir.  DOS file attributes query (mov ax, 4300, int 21h) returns 16 bits of attributes or 16 bits of error, in different registers.  16 bit WinFile had an extensible model for network redirectors, which might support long file names but couldn't express them through the DOS interface, so winfile could optionally call a DLL that also returned 2 16 bit values.  Internally though, it encoded this into one 16 bit value with the high order bit indicating whether the remaining 15 bits were errors or attributes; this was feasible because neither error nor attribute numbers could go to 16 bits.  When moving to 32 bit land, all of this code was removed, the call to the helper was replaced with GetFileAttributes (which handles long file names implicitly), and the comment was added asking why the flag check is there.  Point is, the flag check is now wrong and I'm certain is superfluous/historical.

Are you then specifically saying that @NazmusLabs request for coloring to be optional not be part of this?

Note the latest commit only updates the English dialog template (I don't know the translations for anything else.)  Is there a better way to flag that translation updates are needed?  I did verify that the code functions if the dialog template isn't updated - it'll hit errors trying to update things internally but none of it is visible to the user.

@malxau just add the additional line in every currently available translation, then the translators would translate it.

+1 to @peterooch's comment above.  One more minor item: INVALID_FILE_ATTRIBUTES == ((DWORD)-1).
I'll merge as soon as you have a chance to fix those two things.


build: merge dev to stage

:tada: This PR is included in version 0.24.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


DOC: add preview of AmpForm-DPD model deserialization

Added a page for Lc to pKpi that illustrates https://github.com/ComPWA/ampform-dpd/pull/132 (preview).

[!WARNING]
The model validation does not work yet, for now the page just illustrates the symbolic rendering of the deserialized model. Keep an eye on https://github.com/ComPWA/ampform-dpd/issues/133 for upcoming fixes.

@mmikhasenko the page has been converted from a Jupyter notebook with MyST syntax and is not yet optimal for Quarto. On the road today, hope to get back to that later today. The PR should be merged before tomorrow afternoon.

Looks great, @redeboer.
I could not spot any problems right away: maybe it matches once the nan is solved.

Combination of s (GeV^2), and masses (GeV) does not look right, if the order of the argument changes (production vs decay of resonance)

p^{2L} is missing.

my form-factor includes z^{2l} in the numerator, that is why there is no p^{2l+1} in julia code. Just 2p/sqrt{s}

I'm doubting btw between merging this PR for now to get at least the preview up or addressing the issues first. Don't think I can handle that quickly because it might require a new prerelease of AmpForm-DPD.

Combination of s (GeV^2), and masses (GeV) does not look right, if the order of the argument changes (production vs decay of resonance)

Good point, though more of a design problem + latex rendering problem? You would just have to square the mass. But yeah if there is some argument swapping going on programmatically this is tricky...

@mmikhasenko seeing that CI takes some time, I would prefer to merge this one (and #45?) asap. Remaining issues will be addressed through https://github.com/ComPWA/ampform-dpd/issues/133 and a follow-up PR here.


PHOENIX-5608 upgrading CATALOG table fails when setting phoenix.conne…

…ction.autoCommit=true

Looks good.
Can you attach patch to the Jira and hit "Submit Patch".

Merged to master. @ChinmaySKulkarni @lhofhansl - do you want me to push this to 4.x-HBase-1.x now as well, or wait until 4.15 RC3 is already cut and up?

@gjacoby126 please push to the 4.x branches as well, thanks.


[BUG] Problems encountered when deploying on Ubuntu 2004 and Debian 10 operating systems according to official documentation

OpenIM Server Version
3.8.1
Operating System and CPU Architecture
Linux (AMD)
Deployment Method
Docker Deployment
Bug Description and Steps to Reproduce
Problems encountered when deploying on Ubuntu 2004 and Debian 10 operating systems according to official documentation
https://docs.openim.io/zh-Hans/guides/gettingStarted/dockerCompose
MINIO_EXTERNAL_ADDRESS="http://external_ip:10005"
GRAFANA_URL="http://external_ip:13000/"
external_ip If it has been modified to a public IP address.

After deployment, it is not possible to log in to the backend or register users to log in to the OpenIM system
Screenshots Link
No response

log

openim-server-logs.txt
openim-chat-logs.txt


Cannot find module,node

Is this a request for help?:
YES
Is this an ISSUE or FEATURE REQUEST? (choose one):
Issue
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.9.6
every time when deploying this images getting this error`
module.js:540
throw err;
^
Error: Cannot find module '/app/index.js'
at Function.Module._resolveFilename (module.js:538:15)
at Function.Module._load (module.js:468:25)
at Function.Module.runMain (module.js:684:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3;
but code works on pc,I hadn't get error for other deployments they was done this way
dockerfile`
FROM node:8.9
ENV port 3000
WORKDIR /app
COPY package.json /app
RUN npm install
COPY . /app
CMD ["sh", "-c", "node index.js --port=${port}"]
output of RUN ls -la after COPY ./app
Step 7/8 : RUN ls -la
---> Running in 9e24667abd49
total 76
drwxr-xr-x  9 root root  4096 Jun 21 07:14 .
drwxr-xr-x 57 root root  4096 Jun 21 07:14 ..
-rw-rw-r--  1 root root    30 May 31 09:00 .dockerignore
-rw-rw-r--  1 root root   151 Jun 21 07:14 Dockerfile
-rw-rw-r--  1 root root   556 Jun 20 15:16 api.yaml
drwxrwxr-x  2 root root  4096 May 23 09:03 controllers
-rw-rw-r--  1 root root   446 Jun 20 15:18 index.js
drwxrwxr-x  3 root root  4096 May 15 11:27 insert
drwxrwxr-x  3 root root  4096 May 15 11:27 modules
drwxr-xr-x 69 root root  4096 Jun 20 15:07 node_modules
-rw-r--r--  1 root root 20404 Jun 20 15:07 package-lock.json
-rw-rw-r--  1 root root   328 May 31 09:02 package.json
drwxrwxr-x  2 root root  4096 May 15 11:27 services
drwxrwxr-x  2 root root  4096 Jun 14 14:56 settings
drwxrwxr-x  2 root root  4096 May 23 09:35 utilities

just forget this!!I've tagged the same container as new version,pushed and its works!


Display some information in Hex format

Enhancement:
Currently, the DCL uses decimal values for all numeric fields but it'd be good to visualize in Hex format, at least: VID, PID & Device_Type .
In order to avoid misinterpretation from actual value from DCL, it could be shown in parenthesis on the right, ie:
VID                          PID
12288 (0x3000)     4096 (0x1000)

This was implemented in 1.0.6


#6 Split test execution between net472, netcore2.0 and netcore3.1 for…

… easier analysis
see https://github.com/Brunni/DotNetAsyncScheduler/issues/6

Closes #6


Discuss delegated testing strategies

This is a very general discussion. Its intent is to possibly hash out a solution for wider testing environment than what would normally be possible.
Our problem is as follows:

PSI/J is meant to be used to talk to a wide variety of cluster scheduler setups. Many of these are unique in various ways, despite using the same core software. In order to increase the likelihood that PSI/J functions correctly on such a wide variety of systems, proper testing is necessary on each potential target machine. However, we, as developers, have access to a rather limited subset of all potential setups. This difference between the machines we should test on and the machines we can test on forms a gap that we should address.

So we must delegate the testing to either a system that has access to many machines or to users that have such access. We'd like to explore the possibility of doing the latter.
In principle, potential users, should they decide to use PSI/J, would be motivated to ensure that releases are compatible with their environment. If we provide a sufficiently simple mechanism for users to run tests and contribute the results back to us, we may be able to bridge the gap above in the sense that a system would emerge that would effectively act as if automated tests were run on a much wider variety of systems than what we have access to. The important part to note is that we do not need access to all said systems; we only need the results from tests that are run by users who do.

I think we are past planning on this and have a working implementation.


root logger configuration in supervisor.py breaks logging settings for parent modules

The way logging is configured in supervisor.py breaks logging settings when balena-sdk is imported into another module. Please consult this page on how logging should be configured in a library
https://docs.python.org/3/howto/logging.html#configuring-logging-for-a-library
https://github.com/balena-io/balena-sdk-python/blob/682a14f0db75fed8f5ca869821ffa45aeacd1b39/balena/models/supervisor.py#L11

hey @kwmlodozeniec, this has been fixed in the latest release (v9.0.0). Can you please update the sdk and try again?

Hey @nghiant2710 just tried latest SDK and issue is no longer there. Thanks for a quick resolution!


Decide how to distribute targets file in NuGet

MagicChunks.targets file is currently in lib folder. We should consider if this makes sense and what the best way is to distribute the targets file.

I would suggest moving the MagicChunks.targets into a dedicated package MagicChunks.MSBuild.nupkg and place it into the build/<net-version> folder there. That way, for current msbuild based projects, referencing the MagicChunks.MSBuild.nupkg will automatically import the MagicChunks.targets into the build.
Reference: docs.microsoft.com

I would suggest moving the MagicChunks.targets into a dedicated package MagicChunks.MSBuild.nupkg and place it into the build/<net-version> folder there. That way, for current msbuild based projects, referencing the MagicChunks.MSBuild.nupkg will automatically import the MagicChunks.targets into the build.
Reference: docs.microsoft.com


Hosting the application online

Describe the solution you'd like
Hosting the application online for everyone to use.
Currently working on Heroku.
Describe alternatives you've considered
None so far.

Got it running right now at https://osc-hub.herokuapp.com/.
Test it out and let me know of changes.
Currently pushed changes by making db.sqlite3 public by removing it from gitignore, then pushing changes to Heroku using CLI.
Fix: Creating a private repo and saving creds and DB and using this to deploy it to the cloud.

Alright, so currently facing an IntegrityError while logging in.
This however does not seem to be the case for my account, weird since I hadn't set up anything using my Email ID.
Attached below is the screenshot of the error.

This issue has been fixed to my knowledge, with the latest commit 9b89ae36a0d3ce6e3a18b76aaf7a37fe55e0efe3.

Fixed at 9b89ae36a0d3ce6e3a18b76aaf7a37fe55e0efe3.
Hosting completed using Heroku.

Ignore the above message. Connected DB to PostgreSQL and enabled CI with GitHub. Pushes made to the master branch will automatically be deployed on Heroku. 😄 💯

@all-contributors please add @SVijayB for infrastructure.


Improve logging and monitoring of the cwl-to-es

With this change, the cwl-to-es lambda function will log a single line per execution, with the result of that execution.
It will log in JSON format so it's easier to parse via a log metric filter.
I've also created a log metric filter to monitor the amount of errors thrown by the lambda function.
As per https://github.com/skyscrapers/engineering/issues/211

@duboisph yep, it's running in our staging account

@venturel the idea is to export it to prometheus and create an alert for it


Enrique

Branch conflicts. Merging using PR #17 instead

Branch conflicts. Merging using PR https://github.com/ronuma/legends/pull/17 instead


feat: add changes to mobile ui

closes #23
I modified the folder structure, removed extra code, made the ui clean and also added base components so everyone can start using those components and design stays consistent throughout the app instead of using custom stylings on reused components.

you can use this design as a guide to build a base app.
https://github.com/keep-starknet-strange/joyboy/discussions/48


[HOLD for payment 2024-06-20] [$250] Distance rates - Default distance rate is Disabled instead of Enabled after creating new WS

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.77-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Go to Account settings > Workspaces
Create a new workspace
Go to More features
Enable Distance rates
Go to Distance rates
Might need to go offline and repeat Step 3 to 6 if the actual result is not seen.

Expected Result:
The default distance rate will appear Enabled in the list (should exhibit the same behavior with tax rates when enabling Taxes feature)
Actual Result:
The default distance rate appears Disabled initially, then it changes to Enabled after a while
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/86724e4d-f356-449f-87e0-41b3029e02ee
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0190b7357307a90634
Upwork Job ID:<PHONE_NUMBER>558452736
Last Price Increase: 2024-05-30
Automatic offers:

Krishna2323 | Contributor | 102575239

Issue OwnerCurrent Issue Owner: @puneetlath

@puneetlath  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to  #wave-collect - Release 1

@trjExpensify or @mountiny mind confirming the expected behavior here?

Yeah I think it should be enabled when the feature is turned on, this will probs be optimistic data fix

Yeah I think it should be enabled when the feature is turned on, this will probs be optimistic data fix

Yep, agreed. Enabled by default. 👍

Thanks for the proposals everyone.
I think we can just go with the first proposal from @Krishna2323 as it specifies the correct root cause and the fix.
@Nodebrute The incorrect optimistic value for distance rate is a legit point, but I think that's a nice to have addition instead of the actual issue on hand. I think we can handle it in the PR.
@cretadn22 I'd much rather specify the enablement explicitly rather than relying on default interpretation.
🎀 👀 🎀 C+ reviewed

I've paid @Krishna2323.
@allroundexperts bump on the checklist for you.

Checklist

https://github.com/Expensify/App/pull/23600
https://github.com/Expensify/App/pull/23600/files#r1650201035
N/A
A regression test would be helpful. The steps given in the OP look good to me!

$250 approved for @allroundexperts


Add optional SCM info.

Closes #1288

Looks like tests passed but mima checker failed due to new field in Info case class.
What should I do to resolve?

Added mima filter and all mima error gone.
Only webasite job faillure, which seems I could not handle 🤔
https://travis-ci.org/coursier/coursier/jobs/563406500#L965

Merging, thanks @exoego!

@exoego I've noticed that scm is None when developerConnection is missing in the POM. But not setting developerConnection seems to be common:
    <scm>
        <url>https://github.com/typelevel/cats-effect</url>
        <connection>git@github.com:typelevel/cats-effect.git</connection>
    </scm>

I will submit a PR to coursier

Thanks! It seems that according to the XSD all elements in <scm> are optional.

Opened a PR in https://github.com/coursier/coursier/pull/1331


Update Letters “the-kid-within”

Automatically generated by Netlify CMS

👷 Deploy Preview for effortless-brioche-210b80 processing.

Name
Link

🔨 Latest commit
cdc14bb68b3298246f137ddef6442f03d7dc101f

🔍 Latest deploy log
https://app.netlify.com/sites/effortless-brioche-210b80/deploys/63ee7d52c913de00089f2dae


Add current export state DB API to cataloger

Add DB cataloger API to manage current export state.  This takes an actual transaction, to allow adding tasks within that same transaction.  Otherwise racing occurs when 2 exports are triggered concurrently.

Thanks!  Fixed and will pull once tests pass.


Ignore experimental reasons if the post is manually reported

See https://chat.stackexchange.com/transcript/message/45508505#45508505 and https://chat.stackoverflow.com/transcript/message/43164457#43164457
This is a workaround by detecting if the why text starts with Post manually, which should always be the case if the post is manually scanned/reported.

Coverage remained the same at 65.098% when pulling ad671aa860f60abadbce65c296448494df5cbef0 on iBug:ignore-exp into 5703dc6a631ab869f4316fcc08680f988a2e1891 on Charcoal-SE:master.

Tested in SOBotics, it's working.


[Perf] High Allocator SocketOutput.Write

Drill down on Issue #288
Measurements post PR #287
Item 2 on highest allocators in plaintext test

Microsoft.AspNet.Server.Kestrel.Http.SocketOutput.Write
Allocations (2003 requests)

Bytes (2003 requests)

Have PR for this coming

Hopefully resolved by https://github.com/aspnet/KestrelHttpServer/pull/309 will report back

Closed, resolved by #315 per @benaadams

@lodejard still open; is resolved by #363 instead now :)

Resolved by #363 Resuse writes, initalize queues


liveshare.languages.allowGuestCommandControl can be written by a guest to a workspace settings.json to enable control, circumventing the host enabling it

Describe what happened:
What was your system configuration?
Live Share Extension Version: 1.0.5883
Version: 1.82.2 (user setup)
Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
Date: 2023-09-14T05:55:25.390Z
Electron: 25.8.1
ElectronBuildId: 23779380
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Steps to Reproduce / Scenario:

Join a live share session as a guest
Create or open the workspace's .vscode/settings.json
Add "liveshare.languages.allowGuestCommandControl": true
Save the file
You can now run Quick Fixes as the guest user

Please attach logs to this issue:
You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
Screenshots
If applicable, add screenshots to help explain your problem.

Good afternoon!
My team recently ran into this as well but we added a .vsls.json file in our workspace to prevent folks from seeing or editing the .vscode/settings.json file per this.
Below is the contents of that file:
{
  "$schema": "http://json.schemastore.org/vsls",
  "gitignore": "exclude",
  "excludeFiles": [".gitignore", ".vscode/settings.json", "!node_modules"],
  "hideFiles": [".gitignore"]
}

I can't prove why it happens, but the .vsls.json file is not visible within a liveshare session if you are not the host. I'm not sure if that file is hidden automatically by the extension for that very reason.


Netflix Landing Page Clone

🛠 Issue #1411

Closes #1411
Description
Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] New Project

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

Create fresh PR


Need different vcf atomizer output modes

Need different modes for outputting data in different orientations from the vcf atomizer:
Variant centric:
One row per unique variant. Multi-sample vcfs would have multiple sample objects under the FORMAT object.
{
    "CHROM" : "chr1",
    "POS" : "1",
    "REF" : "G",
    "ALT" : "A",
    "INFO" : {
        "ANN" : [
            {
                "effect": "one"
            },
            {
                "effect": "two"
            },
        ]
    },
    "FORMAT" : {
        "SAM1": {
            "AF": 0.2
        },
        "SAM2": {
            "AF": 0.1
        }
    }
}

Sample variant centric (current):
One row per each variant for each sample. We expand the FORMAT object into multiple rows (while duplicating all other information).
{
    # all other values the same
    "FORMAT" : {
        "AF": 0.2 # AF for SAM1
    },
    "sample":"SAM1"
}
{
    # all other values the same
    "FORMAT" : {
        "AF": 0.1 # AF for SAM2
    },
    "sample":"SAM2"
}

Annotation centric (previously):
One row per each annotation per each variant for each sample. We expand further expand the ANN object into multiple rows (while duplicating all other information).
{
    # all other values the same
    "INFO" : {
        "ANN" : {
            "effect": "one" # first ANN annotation for SAM1
        }
    },
    "FORMAT" : {
        "AF": 0.2
    },
    "sample":"SAM1"
}
{
    # all other values the same
    "INFO" : {
        "ANN" : {
            "effect": "two" # second ANN annotation for SAM1
        }
    },
    "FORMAT" : {
        "AF": 0.2
    },
    "sample":"SAM1"
}
{
    # all other values the same
    "INFO" : {
        "ANN" : {
            "effect": "one" # first ANN annotation for SAM2
        }
    },
    "FORMAT" : {
        "AF": 0.1
    },
    "sample":"SAM2"
}
{
    # all other values the same
    "INFO" : {
        "ANN" : {
            "effect": "two" # second ANN annotation for SAM2
        }
    },
    "FORMAT" : {
        "AF": 0.1
    },
    "sample":"SAM2"
}

closed as of atomizer_rework branch merge


IOS: CBCentralManager implementation of RestoreIdentifier is missing

Hi,
on IOS - we are missing the Implementation of RestoreIdentifier
            _centralManager = new CBCentralManager(this, DispatchQueue.CurrentQueue, new **CBCentralInitOptions
            {
                ShowPowerAlert = true,
                RestoreIdentifier = "myapp.indentifier"
            });**

Also WillRestoreState is required to make background modes behave correctly on IOS.
The class that contains CBCentralManager will need to inherit from CBCentralManagerDelegate for this to work

Hi @mariusbloemhof,
I'm the friendly issue checker.
It seems like (100.00 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message.
But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!

Hi, any feedback about this enhancement?

Hi @smstuebe, I think this is straightforward to implement and is a pretty important feature (for us at least). I'm happy to help if this is not on the radar soon.

@pravincar I believe that we need to reimplement creating CBCentralManager in BleImplementation.cs. I am not sure if this is enough according to apple documentation here you need implement constructor which have DispatchQueue null and delegete set to self. @xabre @smstuebe With some advices I would be happy to implement it.

@xabre @smstuebe I found out that this is implemented and merged on branch 2.0.0 here. Would it be possible to release it?

Release with v2.0.1


quick setup from flannel to weavenet not working

There are some flannel networking configurations that are not cleared up, during quick provisioning, such as:
#ip addr
10: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN
    link/ether 7a:75:cb:c2:21:66 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/32 scope global flannel.1
       valid_lft forever preferred_lft forever
    inet6 fe80::7875:cbff:fec2:2166/64 scope link
       valid_lft forever preferred_lft forever

when moving from calico to flannel we receive this error:
kubectl logs --namespace kube-system kube-flannel-ds-amd64-2d6fz Could not find valid interface matching enp0s8: error looking up interface enp0s8: route ip+net: no such network interface


DocHandle.doc(): don't yield tick

I've never really been clear why we needed this await pause(), but at some point I removed it and broke blutack and so we put it back.
It shouldn't ever really hurt anything to have an async function yield one tick, but you also shouldn't really need it. Currently tests pass with and without it.
If this still breaks blutack, let's get to the bottom of why; and if we can't find a better solution, try to document it and get it under test.

I think if blutack breaks from this it's blutack's fault and we should fix it there :)

For what it's worth, I have removed the pause in my local version and nothing has broken here yet!

Well, it seems fine and I've merged it. If blutack is sad, we'll figure out why.


About the compute_speed.py

Hi, ycszen:
About the compute_speed.py, I have a question.
I think the torch.cuda.synchronize() should be used after each model forward ranther than once.
So I think the right testing speed is:
    torch.cuda.synchronize()
    torch.cuda.synchronize()
    t_start = time.time()
    for _ in range(iteration):
        model(input)
        torch.cuda.synchronize()
    torch.cuda.synchronize()
    elapsed_time = time.time() - t_start

Is it right?

@ycszen

Yes. You are right.
I have updated the code as follows:
    torch.cuda.synchronize()
    time_spent = []
    for _ in range(iteration):
        t_start = time.time()
        with torch.no_grad():
            model(input)
        torch.cuda.synchronize()
        time_spent.append(time.time() - t_start)
    torch.cuda.synchronize()
    elapsed_time = np.sum(time_spent)


Enable slack channel

Enable slack as channel. Test some features on slack.

Slack enabled.

Updated code with changes mentioned here


Rename setup.cfg to .flake8 for more obviousness.

As suggested by @pp-mo in issue #2941. This is purely a naming convention change, and has no practical effect. Especially since we're not yet running flake8 via stickler yet.

Could not review pull request. It may be too large, or contain no reviewable changes.

I also hereby accept the CLA and will mail you a signed copy when I next unbury my printer cabinet.
Hmm. May have to add the printer to the 'take to Cambridge' list.

mail you a signed copy when I next unbury my printer cabinet.

Emailing an electronically signed version would be faster... :postbox: :cry:

Well, assuming 'typing my name' is a sufficient electronic signature, that's done. I don't currently have an active PGP key or S/MIME delegation to sign it with, so...

Not sure about this as other tools, like pytest, would also read from this file. So it's one file for all tools vs many (possibly hidden) files for every single tool.

one file for all tools vs many (possibly hidden) files for every single tool.

Well yes, but only tools that are explicitly needed or supported by the project.  How many could there be?

And it only works for those tools that "agree to share" this magic single filename : where is that consensus ?
So, what is the scope of that thing supposed to be ?
I'd be happy with this if it were covered by a PEP,
but I don't find that ...
According to my crude web searches, the original intent of setup.cfg is configuration for installation,
in fact = default options for commands in setup.py (thus a distutils concept).
On the other side of the argument I find this : http://renesd.blogspot.co.uk/2017/02/setupcfg-solution-to-python-config-file.html

Ok, there are clearly some good arguments both ways here.
Looking at that blog post by @illume, there's a few tools to look at. My quick google-fu didn't find any more obvious ones, so I'll treat that list as canonical without further data. I don't see this project using mypy any time soon, nor replacing unittests with pytest. So... from where I'm standing the only other tool we'd be likely to consider using is coverage.py. If anyone wants to suggest we deploy that, sure - but in the mean time if flake8 is the only thing using the file - the .flake8 name does seem to be more obvious.
TL;DR - I'm with Patrick on this one, till we use more tools that share the config.

There is a valid point that we only have one tool to configure, and therefore one specific configuration file seems appropriate. However, we could be a little forward thinking here and not make extra work for ourselves...
We currently use nose for testing, which is deprecated; it is likely that we will follow cartopy's lead and switch to pytest at some point. When we do that we could add another configuration file, or we could continue to use setup.cfg (by the way, pytest is not deprecating/removing the use of setup.cfg, they are deprecating/removing the section title [pytest] within setup.cfg in favour of [tool:pytest]).
It seems to me that whilst changing the name of this file now is perfectly fine, it is quite likely we'll want to change it back again quite soon.

@pp-mo What do you think? If it's likely we're going to be using more tools, the argument for using a standard file does make sense. On the other hand, if that second tool isn't exactly round the corner, then the clarity of the different filename also makes sense for the meantime.

What do you think?

Personally I still prefer this approach, but given all the opinion against I wouldn't be happy merging it, so status quo wins.


Edited summary

Added the description for this class.

Docs Build status updates of commit 459986c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint-server/xml/Microsoft.SharePoint/SPAudit.xml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


RESET alters parameters during animation tree transition

Godot version
4.1.1-stable
System information
Windows 10
Issue description
I have a simple animation tree that goes from a fade in (alpha modulation) on a tooltip to a bounce animation (y position translation). My reset track sets the alpha to zero. When the animation tree automatically transitions from the end of the "enter" animation to the "bounce" animation, it is resetting the Tooltip:modulate:alpha property based on the reset track.
It was my understanding that the reset track is played after saving your project, or loading the scene.. is it supposed to be played between animations? Perhaps I've misunderstood, but given that it uses the reset value for the modulate:alpha property even if I set it explicitly in the bounce animation, something is amiss.
I also get these errors in the editor about using call_deferred:

Steps to reproduce
Extract the attached reproduction project. Open animation_tree_bug.tscn. Click on "AnimationTree". Go to the AnimationTree editor, play "Enter" animation. It should then transition to the "Bounce" animation, and the alpha should immediately revert back to zero.
Minimal reproduction project
animation_tree_bug.zip

At least the errors which might have caused this seem to be fixed in 4.2 dev5 and master at fe5b1c8d49313d63fbe91cb7cdf463e10fb86afa. Can you try the latest dev5 and see if it fixes the issue for you?

I actually cannot consistently reproduce the errors I screenshotted (if that's what you're referring to), it seemed to happen when I was constructing the reproduction scene itself, modifying the reset track. Just built master to take a look myself, and can confirm the issue with the reset animation overriding the modulate parameter is present in both 4.2.dev5 and master.

Looks related to code added in this commit: https://github.com/godotengine/godot/commit/17ce879a15dac1d79f5c9a093b0cc54b8e8ff02e#diff-47d98bbc16960ace8510b2cfa795da0e87601cc3f22a6f2e5155cfe01c750952.
Each track's value from the track cache is initialized per _process_graph call. The bezier value for tooltip:modulate is taken from the init_value stored in the cache that was generated at the start of the tree's playback. Init_value is never changed again since the cache remains the same. Given the second animation does not contain that modulation track to perform bezier interpolation, that initial cache value ends up being the applied value for the track.
Could there be some way to skip the track value initialization under certain conditions, or to ensure that we are not applying value updates to tracks that have not changed?

Made a band-aid fix, not sure of the best approach, so I'm not creating a PR until someone familiar with the animation tree can set eyes on it. I am not fond of adding a state variable to the track cache, but I am also not fond of iterating over animation states to ensure we only initialize the tracks used. https://github.com/forager-pixel/godot/commit/59763a6dbe9cb0c043476a4bbb42ffdd3440a2d2

I'm seeing at least one issue with this fix.. if you have xfade then suddenly it exposes a major issue with how the blend values are calculated. When blending to a value, if the "from" animation doesn't contain a value for that track, you then are only calculating the value from whatever fraction of the blend factor the "to" animation has - leading to erroneous values.
Perhaps philosophically there was an intent here for people to keep track of all animated values per animation state they create, but it puts burden on them to create more verbose animations than may be necessary, so I'm not too sold on that idea. In my mind why not keep states simple where possible, and allow the engine to transition using the actual previous values?

I'm not very familiar with the animation system. @TokageItLab might be able to say if this is intentional behavior or a bug and if your linked fix makes sense.

Appreciate the responses @bitsawer @TokageItLab.
Does this mean that xfade will also be a useless property in non-deterministic blending? If I gather what you're saying it sounds like it will always set the blend factor to 1 when tracks dont match up. But, I dont fully understand why at least in a simple xfade case we cannot infer the initial value from the current value at the end of the "from" animation. I may be missing all the edge cases here, since animations nest in not so obvious ways sometimes.

No crossfade with missing tracks in NonDeterministic blending is performed. It stops working the moment it reaches 0.
This is because, as explained above, it has no default value, and if you use some value as the default value, the result with and without crossfade will be very different, and it will look like a complete bug.


Add example for occlusion and transmission effects, add ability to set number of transmission rays

Closes #2
Adds option to set number of transmission rays.
Adds example for occlusion and transmission effects.

Oh you got it to work, I tried it a week ago without success.
Thanks for the PR ^^


ARROW-8158: [C++] Upgrade to LLVM 9

LLVM 7 and 8 are still supported.
Debian GNU/Linux stretch based
images (ci/docker/linux-apt-jni.dockerfile and
dev/tasks/linux-packages/apache-arrow/apt/debian-stretch/Dockerfile)
still use LLVM 8 because LLVM 9 packages for strech at apt.llvm.org
are broken. (LLVM 10 packages aren't broken.)
CentOS 8 packages still use LLVM 8 because there are no packages for
LLVM 9 on CentOS 8.
manylinux1 still use LLVM 8 because g++ 4.8.2 is old to build LLVM 9
or later.

@github-actions crossbow submit -g nightly

@github-actions crossbow submit -g nightly

@github-actions crossbow submit -g nightly

According to this discussion, could you please update the LLVM part of LICENSE.txt?
cc @wesm

According to this discussion, could you please update the LLVM part of LICENSE.txt?

Thanks for notifying this. I've updated.
The new LICENSE.txt mentions bundled software:
https://github.com/apache/arrow/pull/7280/commits/4a8464512c9b60a7f1aea6e699184438f51969c0#diff-61e0bdf7e1b43c5c93d9488b22e04170R1298-R1308
==============================================================================
Software from third parties included in the LLVM Project:
==============================================================================
The LLVM Project contains third party software which is under different license
terms. All such code will be identified clearly using at least one of two
mechanisms:
1) It will be in a separate directory tree with its own `LICENSE.txt` or
   `LICENSE` file at the top containing the specific license and restrictions
   which apply to that software, or
2) It will contain specific license and restriction terms at the top of every
   file.

I've checked bundled software in LLVM 9. There are 2 software:

llvm/test/YAMLParser/LICENSE.txt
llvm/utils/unittest/googlemock/LICENSE.txt

Both of them are for testing. So I didn't put additional license information to our LICENSE.txt.

Umm, the gandiva-decimal-test test is sometimes  stuck on CI:

e.g.: AMD Debian 10 C++: https://github.com/apache/arrow/pull/7280/checks?check_run_id=718284495
e.g.: AMD Fedora 31 C++: https://github.com/apache/arrow/pull/7280/checks?check_run_id=718284516

But I couldn't reproduce this on my local environment...
Could  @praveenbingo, @pravindra or someone help me?

I think this PR has a mis-assigned JIRA number

Oh, sorry. I've fixed Jira ID.


Providing a version on crates.io?

Hi all,
This is a really interesting library, that is sure to be useful in many of our projects. Thanks for all of your efforts here (and I'm a huge fan of your work, @vigna)!  However, if we'd like to build an application or tool relying on sux-rs and put it on crates.io, we are currently kind of hosed, as there is no version there. There was one ~6 months ago, but it was yanked. I realize that things are still under active development here and improving quickly, but do you think it would be possible to periodically checkpoint those and release them on crates.io?
Thanks!
Rob

That should happen very soon. The version on crates.io is just a placeholder. It's just that I don't want to put out APIs and then change them radically.
It's a bit complicated to get that right because Rust was designed without thinking of data structures with implicit representations, and it really gets ugly when you try to use the standard traits. E.g., Index is entirely useless in a succinct or compressed data structure.
Indeed, if you have comments on the traits you see know that would be invaluable input.

In particular, what we're trying to get right is:

IndexedDict, for an indexed dictionary (successor, predecessor, etc.)
BitFieldSlice, for arrays of elements of fixed bit width
Rank / Select
How should we pass inputs that usually comes from buffered files into stuff like VFuncBuilder. Our current idea is to have a Lender returning a Result<T>, so that errors from the underlying I/O can be managed easily, and also one can reuse a buffer for efficiency. This leads however to some complications with type inference and adapters, and the impossibility of using the Iterator/Lender API (you can't use ? with that), so we're trying to understand the best way to use the Rust type system to make things easy for everyone.

Just pinging @theJasonFan here, in case he has specific input to provide on these traits.

One possible solution to this may be to publish things as multiple creates with a smaller scope, so that you don't have to commit to a version for everything.
That also has the benefit of reducing dependencies/bloat for users. For example rust-bio does not do this partitioning, and its dependencies are anecdotally always the main thing slowing down my compilation, even if I don't actually use those parts of rust-bio.


refine parse_outputs in ExecuteNbCode.

重构ExecuteNbCode中输出解析部分代码。实现同时输出代码片段中的正常打印内容和异常内容，示例如下：
executor = ExecuteNbCode()
code = """
import pandas as pd
df = pd.DataFrame({'ID': [1,2,3], 'NAME': ['a', 'b', 'c']})
print(df.columns)  # 需要正常输出的内容
print(df['DUMMPY_ID'])  # 会发生异常的代码
"""
output, is_success = await executor.run(code)
assert not is_success                 # -> True
assert "Index(['ID', 'NAME'], dtype='object')" in output  # -> True
assert "Executed code failed," in output  # -> True
assert "KeyError: 'DUMMPY_ID'" in output # -> True
print(output)
#  Index(['ID', 'NAME'], dtype='object')    # 这是需要正常输出的内容，剩下的是需要输出的异常信息
#, Executed code failed, please reflect the cause of bug and then debug. Truncated to show only last 2000 characters
#-----------------------------------------------------------------
# KeyError                                  Traceback (most recent call last)
# File ~/opt/anaconda3/envs/metagpt/lib/python3.9/site-packages/pandas/core/indexes/base.py:3653, in
# Index.get_loc(self, key)
# 3652 try:
# -> 3653     return self._engine.get_loc(casted_key)
# 3654 except KeyError as err:
# ....

Codecov Report
Attention: Patch coverage is 87.50000% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 81.21%. Comparing base (803359a) to head (bcde517).
Report is 1 commits behind head on code_interpreter.

Files
Patch %
Lines

metagpt/actions/mi/execute_nb_code.py
87.50%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                Coverage Diff                @@
##           code_interpreter     #980   +/-   ##
=================================================
  Coverage             81.20%   81.21%
=================================================
  Files                   226      226
  Lines                 12483    12488    +5
=================================================
+ Hits                  10137    10142    +5
  Misses                 2346     2346

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

LGTM


Pattern matching of union and nullable types

It is a common thing to have to deal with all the possible types of a union type (especially, object or null). In some languages, like Haskell or Rust, there are pattern matching constructs to allow compile-time checking of all the cases. AFAIK, the only way to deal with these union types in CC at the moment is to do casting. The problem with this is that it is tedious and prone to error. If you cast incorrectly, the compiler isn't going to catch that.
Here's a idea of how you could design pattern matching in closure:
switch (goog.type(foo)) {
    case 'Foo':
        // do something with `foo` known to be a Foo object
        break;
    case 'null':
        // do something with `foo` known to be null
        break;
}

This could be implemented like:
if (foo instanceof Foo) {
    // ...
} else if (foo === null) {
    // ...
}

Where goog.type (or some other method) would just be a virtual thing which the compiler recognizes as a cue to do this pattern matching.
Ideally you would also be able to do it outside of a switch with something like
if (goog.typeIs(foo, 'Foo')) {
}

which allows you to do a sort of cast but without having to invent another variable.
Is there any support for this already? I think it would be a really useful feature that would find a lot of bugs and prevent having to do casting all over the place.

The compiler type specializes these unions, casting is not the only option. You can IF-test a union type to get to the members of the union.
http://closure-compiler-debugger.appspot.com/#input0%3D%252F**%2520%2540constructor%2520*%252F%250Afunction%2520Foo()%2520%257B%250A%2520%2520this.prop%2520%253D%2520123%253B%250A%257D%250A%250Afunction%2520f(%252F**%2520%253FFoo%2520*%252F%2520x)%2520%257B%250A%2520%2520if%2520(x%2520%253D%253D%253D%2520null)%2520%257B%250A%2520%2520%2520%2520return%253B%250A%2520%2520%257D%2520else%2520%257B%250A%2520%2520%2520%2520var%2520%252F**%2520!Foo%2520*%252F%2520y%2520%253D%2520x%253B%250A%2520%2520%2520%2520return%2520y.prop%253B%250A%2520%2520%257D%250A%257D%26input1%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3D1%26CHECK_SYMBOLS%3D1%26CHECK_TYPES%3D1%26MISSING_PROPERTIES%3D1%26PRESERVE_TYPE_ANNOTATIONS%3D1%26PRETTY_PRINT%3D1

Oh, nice. Is there a way to also check the the type when it's two non-null types, especially if one only exists in a typedef?
/** @typedef {number} */
var int;

/** @param {int|string} foo */
function bar (foo) {
    if (foo is int) {
    } else { // foo is string
}

if (typeof foo === "number") {
...
} else {
...
}
You can't do typeof for custom type names. Instanceof checks inside IFs also tighten the type.

Thanks, using instanceof well help. It would still be nice to be able to do custom types as well; otherwise, they're sort of third-class citizens to the compiler.

This isn't really a compiler issue. typeof is a built-in operator, and it produces a specific set of strings. If you write (typeof foo === "mytype") it will never evaluate to true.

typeof is a built-in operator, and it produces a specific set of strings. If you write (typeof foo === "mytype") it will never evaluate to true.

I understand that. What I meant was that it would be nice if Closure had the (extra) capability to utilize the virtual types in some way. Not with typeof, but some other Closure-recognized thing, like goog.getType or something like that. In any case, using instanceof is a lot better than what I was doing before, so thank you.


 I fixed it. Sorry.

It works direct but as docker container it's gives the error
Regards,
Kumaravel
9029930068
On 31-Oct-2016 7:22 PM, "Alexei Ledenev"<EMAIL_ADDRESS>wrote:

Closed #27 https://github.com/gaia-adm/pumba/issues/27.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gaia-adm/pumba/issues/27#event-841920942, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGHqjrXBI-uz39fRvcQFCPlq9BvYTwCdks5q5fKpgaJpZM4Kk-gi
.


[RELAY][REFACTOR] Mix mode context analysis

https://discuss.tvm.apache.org/t/vm-an-error-from-context-analysis-pass/7818
This PR uses the MixModeVisitor to leverage its non-recursive visitor and memoization. We bumped the visit limit to allow high order functions to be visited multiple times which enables pytorch lstm tests. More powerful unification needs to be added for these functions.
In addition, the use_gpu decorator is added to many more unit tests.

cc @mbrookhart @masahi @icemelon9 @jroesch

I need this fix for a new PyTorch frontend test I'm working on, so merging now. Thanks @zhiics @mbrookhart @leandron


🚧(feature) Rework plots and metrics user experience (V0)

Purpose
Enhance dashboard compactness and UX.
Proposal
To do :

[X] Utilize human-readable names in place of video UUIDs for mock data.
[X] Present metrics in a more compact and inline format.
[X] Update plot when user selects a metric.
[X] Improve layout to render on small screens.

https://github.com/openfun/warren/assets/45729124/ca295a17-ef99-4382-ac46-28c56ce312a4
These changes are inspired by Google Analytics features here.
To be improved:

[ ] Accessibility.
[ ] Visual information on the current selected metric.
[ ] Metrics Tabs responsiveness.
[ ] Plot styling + construction.

This looks nice :) On a first viewing of the tool, I had the following remarks (not sure how much latitude you have to change those):

It would be nice to have a color reference somewhere, to be able to distinguish lessons (in the labels, or maybe with a tooltip when hovering over a curve ?)
The curve morph when you change variables feels like a rescaling, and might be a bit confusing (the initial curve being drawn display is nice)
Maybe It could be useful to have a variable scale with a minimum value a bit lower than 100 for classes with a low number of students / viewers

Recent updates:
https://github.com/openfun/warren/assets/45729124/94c2c8cd-a09c-4d7f-9228-1fde2a2cb306


Use bundleForClass instead of mainBundle

Getting the resource paths for adjacency_graphs.json and frequency_lists.json returns nil when zxcvbn-ios is in a framework. Replacing [NSBundle mainBundle] with [NSBundle bundleForClass:[self class]] solves this problem and works for zxcvbn-ios when is in the main application or in a framework.
This problem can easily be seen by adding zxcvbn-ios to a project via CocoaPods with the use_frameworks! option in the Podfile.

Closing PR in favour of https://github.com/dropbox/zxcvbn-ios/pull/16


[layer_internal] refactoring read, save

implement read, save function in layer_node
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: hyeonseok lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1289. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

Please consider rebasing.

:octocat: cibot: @lhs8928, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1289-202106161412340.94231796264648-1902389464bf8a0725b068a0049dad60e069cfab/.

:octocat: cibot: @lhs8928, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1289-202106161451110.41966509819031-5ed9c29d8722d6b00dc4c8476bc218c8313ee561/.

Please consider rebasing.

Resolve conflict

:octocat: cibot: @lhs8928, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1289-202106161712040.94964003562927-8f02a565ba0e7bdc68596bdfdf3e97cbc815c807/.

:octocat: cibot: @lhs8928, nntrainer/layers/layer_node.cpp includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @lhs8928, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1289-202106161847240.016993045806885-7ab126374757b5f533cc31d4e1f6e66cae82524d/.


Organize existing files and folders

Look into NY/HK/UK/Boston/Tokyo/ folders and see the different features of the web clients

updated the files, reviewed all files and folders. Added a logiks folder


Make env public and update docs

fix for #90

The failed travis build looks like a fluke to me, so I merged anyways...


Support multiple subnets per AZ allows us to add more NAT GW

*How to categorize this issue?
/area TODO
/kind enhancement
What would you like to be added:
We are currently evaluating a new architecture for our platform. Currently we are using multiple subnets per availability zone (AZ) to scale the NAT Gateway (NAT GW) on AWS and Azure. For GCP, we are scaling by using multiple public IPs within a single NAT.
However, Gardener currently only supports creating a single subnet per AZ, which limits us to a maximum of one NAT Gateway per AZ. This constraint could become a bottleneck for our scaling requirements.
It would be great if Gardener could support the creation of multiple subnets per AZ, allowing us to scale the NAT Gateway on AWS and Azure effectively, and continue to use multiple public IPs within a single NAT on GCP.
Why is this needed:
Scalability improvement

/assign


Ticket26937: check for free disk space

I also don't know why two specific log messages were picked as places to catch an exception when we think that maybe we ran out of disk space.

In concrete cases where i run out of space, they happened there.

Couldn't this happen every time we log?

Yes

Shouldn't we therefore catch this exception at every log message? (Please do not write code to do that)

Maybe, but we would need to change all logs, so probably we do not want that.
What about just leaving the logs in this PR?

Fixed the issues you pointed out when calculating the space


Update amiupdater.cfg.yml

Overview
Brief description of what this PR does, and why it is needed (use case)?
-- Added RHEL 8.5 HA image
Testing/Steps taken to ensure quality
How did you validate the changes in this PR?
Notes
Optional. Caveats, Alternatives, Other relevant information.
Testing Instructions
How to test this PR Start after checking out this branch (bulleted)

Include test case, and expected output

/do-e2e-tests


Upgrade styled-system to v4

This PR upgrades styled-system to v4 which should save us 7kB in our bundle size 😎
The biggest change is that the styles export was removed, so I had to do a little refactoring of our constants file.
The get helper also got refactored to return the last argument as a fallback, which I thought it did before, but I need to do some testing to make sure that doesn't bork our expected behavior with pulling theme values

@shawnbot I mean... I think it was doing what it was supposed to do - I was providing an invalid theme references and it was returning an empty string because the get function couldn't find it. If we don't have tests around our get function we should


When I turn on camera it turned on and showing view 90 degrees rotated.

This issue happened when I updated my library with latest main brach
these are the steps I followed
it is happening in iOS App
Joined a meeting
camera settings are 16:9

joined a meeting
tuned on the camera
camera opened by it is rotated 90 right without rotating the phone.

Please look into it.
https://github.com/livekit/client-sdk-swift/assets/130336875/f0e24e67-bbc7-4835-9866-4e3ddf1560e8
Uploading Screen Recording 2023-09-14 at 2.28.16 PM.mov…

Please look into it.

Hello, I fixed this one. There will be a new release.

When is the next release?
when can we expect that?

@hiroshihorie can you please suggest which older version we can use as of now?

@hiroshihorie & @cloudwebrtc This issue is still not resolved.
114.5735.06

We swapped the WebRTC binary, can you "Reset Package Caches" and try again

@hiroshihorie still not working for me!

Can you try v1.1.1, please open if still have problems .


Refactor out EventMachine dependencies.

Even though Celluloid and EventMachine are mutually exclusive, when Reel is installed, EventMachine comes along, because whether used or not, websocket-driver and other faye-* gems bring in an EventMachine dependency. This has affected actioncable also, through faye-* dependencies, and it is being addressed in this thread: rails/actioncable#16
In our next release bringing in HTTP/2 ( #198 ) we need to also refactor out dependencies which bring in EventMachine, whether it be used or not, and provide complete Celluloid::IO support for websockets, by refactoring the faye-* gems in parallel with this next release.
This will be achieved one of two ways:

Working with @jcoglan to remove EventMachine in a version of his gems.
Fork and refactor the faye-* gems as Celluloid::WebSocket which would also solve our need to bring celluloid-websocket-client back up to speed with the faye-* gems.

/cc: @tarcieri, @dhh, @jcoglan, @kenichi, @jasonayre

faye-websocket depends on EM but websocket-driver does not. The intention was always for websocket-driver to allow easy WebSocket integration into other I/O stacks.

websocket-driver is also quite easy to integrate into a celluloid-io loop: https://gist.github.com/Asmod4n/241c84ef31df921b31e9/c15bd4e3be2efd261f325d18eec126f1e9649b62

Thanks @jcoglan, that makes sense and explains what I've been seeing. EM is only listed as a development dependency for websocket-driver I now see. And agreed, @Asmod4n. I've seen and worked on several implementations like that. Thinking out loud...
Maybe we ought to extract all websocket code from Reel, and create reel-websocket both for client and server uses, fleshing out WebSocket::Driver in pure Celluloid::IO rather than focusing on the Rack approach being primary... of hijacking.
We can support hijacking in the reel-rack handler, but reel-websocketought to be a pure ruby, pure I/O base for that. Thenreel-websocketcan be used byReelitself andAngelo... half as a standardized "Celluloid WebSocket" and half as aWebSocket::Driver` abstraction layer.

@digitalextremist Yep, EM is only used to run the example in the websocket-driver repo, it's not a runtime dep.


core.js: check for iOS/mobile compatibility.

Done. It relies on 'navigator.userAgent' and is currently not in use. It's even unclear how reliable this is and it's fairly impossible to cover with unit tests. It would probably be a better solution to check for features where necessary.


Unhandled JS Exception: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

error message:
2016-08-05 16:16:19.394 [error][tid:com.facebook.react.JavaScript] Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.
2016-08-05 16:16:19.398 [fatal][tid:com.facebook.react.RCTExceptionsManagerQueue] Unhandled JS Exception: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.
xcode:7.2  osx:10.11.5
1.https://facebook.github.io/react-native/docs/native-modules-ios.html
2.Objective-c code
#import "CalendarManager.h"
#import "RCTConvert.h"

@interface CalendarManager()

@property (nonatomic, copy) RCTResponseSenderBlock            mBlock;

@end

@implementation CalendarManager

- (dispatch_queue_t)methodQueue
{
    return dispatch_get_main_queue();
}

RCT_EXPORT_MODULE();

RCT_EXPORT_METHOD(addEvent:(NSString *)title)
{
    self.mBlock(@[[NSNull null], @[@1, @2, @3]]);
}

RCT_EXPORT_METHOD(findEvents:(RCTResponseSenderBlock)callBack)
{
    self.mBlock = callBack;
}

@end

3.package.json
{
  "name": "MarkLite",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start"
  },
  "dependencies": {
    "react": "15.0.2",
    "react-native": "0.26.1"
  }
}

4.index.ios.js
'use strict';

import {
  AppRegistry,
  NativeModules
} from 'react-native'

var CalendarManager = NativeModules.CalendarManager;
CalendarManager.findEvents((error, events)=>{
  console.log('findEvents callback :'+events);
});

CalendarManager.addEvent('this is a test');

module.export = CalendarManager;
AppRegistry.registerComponent('CalendarManager', () => CalendarManager);

use the RCTRootView
    NSURL *jsCodeLocation = [NSURL
                             URLWithString:@"http://localhost:8081/index.ios.bundle?platform=ios&dev=true"];
    RCTRootView *rootView =
    [[RCTRootView alloc] initWithBundleURL : jsCodeLocation
                         moduleName        : @"CalendarManager"
                         initialProperties : nil
                          launchOptions    : nil];
    UIViewController *vc = [[UIViewController alloc] init];
    vc.view = rootView;
    [self.navigationController pushViewController:vc animated:YES];

@facebook-github-bot stack-overflow

Hey @phil-007 and thanks for posting this! @damusnet tells me this issue looks like a question that would be best asked on StackOverflow. StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only. Will close this as this is really a question that should be asked on SO.


Simulator should return warrior metadata

When I load simulators, the warrior doesn't return the metadata in the parse results from what I can see :(

Did you specify metadata using the comments? e.g.
;name imp
;author traditional

And do you mean the parse result before it hits the simulator or the loaded warrior after it has been through the initialise function?

I got the metadata from the warriors in the warriors folder. The metadata comes back from the parser in tokens but not in the warrior post init

Yeah, not sure if I ever bothered hooking that up but shouldn't be a problem.

So is the problem that the meta data is returned from the parser in the IParseResult but that it is not within the IState after the simulator has been initialised?
The code certainly seems to be there to do this (see WarriorLoader.ts line 43).
I don't understand your description because you say that the metadata is in the result from the parser but not in parseResults - but the parse results are produced by the parser...?

Sorry what I mean is that it's returned in the IParseResult within the tokens, but not within the metaData object, not the metaData object anywhere else.
So if I parse this:
;redcode
;name Dwarf
;author A. K. Dewdney
;assert CORESIZE % 5 == 0

	DAT		-1
start	ADD	#5,	-1
	MOV	#0,	@-2
	JMP	-2

	END	start

I get this:

Where warrior is the tokens run through the serialiser

Ah, ok interesting.  I'll take a look!

Should be resolved by #73

Close 'em off sucker!


Add support for outputting json to a file

This solves the problem of console messages, such as
Fetching package information from...
appearing in the json, that breaks json parsing tools.
I'd be happy to do it in another fashion if that's required.

I see some tests are failing, I'll look into that.

Thanks @jhf for your PR.
If I understand correctly you are currently running elm-analyse --format=json, but the output of the process is not correct JSON. For the simplicity of the tool I would suggest to suppress the messages that corrupt the JSON output if the flag is set. This is already done for other messages ('file loading' and such).
Having to write to a file brings complexity with it, such as access, intermediate folders which have to be created, and in this case additional configuration in the process.
Would it suffice for you if the human readable messages are suppressed?

Thanks @jhf for your PR.

You are welcome.

If I understand correctly you are currently running elm-analyse --format=json, but the output of the process is not correct JSON. For the simplicity of the tool I would suggest to suppress the messages that corrupt the JSON output if the flag is set. This is already done for other messages ('file loading' and such).

Ok.

Having to write to a file brings complexity with it, such as access, intermediate folders which have to be created, and in this case additional configuration in the process.

Yes, good point.

Would it suffice for you if the human readable messages are suppressed?
Certainly, are you taking a stab at removing Fetching package information from... or do you wan't an updated PR?

If you can update the PR, that would be really cool. I do not have much time on my hands at this moment for this project :(.


OSCPoint close powerpoint command from Companion error

Hi Nick,
When I send the close PPT command from Companion, regardless off the mode I set it (save file, abort or discard), PPT does not respond. I am running Companion v3.4.0 and OSCPoint v<IP_ADDRESS>.
Here is the log.
Close command error.txt

A quick search shows this on Stack Overflow: https://stackoverflow.com/a/39412792
Is this file open in the preview pane in Explorer, as well as in PowerPoint itself? If you've got the preview pane open in Explorer, it'd be worth closing it and seeing if the issue still occurs.
https://stackoverflow.com/a/39412792

Thanks for the response.
I have rebooted the machine a few times now, and after the 4th reboot, the command works. I am not sure why, but it's working now. Thanks

Thanks for the update!


[docs] Add alt text on images (related to #4036)

This pull request mentions #4028 and modifies the following files only:

[x] docs/Features.rst
[x] docs/GPU-Performance.rst
[x] docs/GPU-Windows.rst
[ ] docs/Parallel-Learning-Guide.rst
[ ] docs/Parameters-Tuning.rst
[ ] docs/gcc-Tips.rst
[ ] docs/index.rst

I apologize for the inconvenience, but could you please merge in the latest changes from master? We recently merged some fixes for failing continuous integration jobs (#4032)

Sure

Sure! Thanks for the suggestions, will do it.

@akshitadixit it looks like this branch has some conflicts with recent changes on master. I'd be happy to fix them if you'd like (they aren't related to your code). Can I push to your branch?

@akshitadixit it looks like this branch has some conflicts with recent changes on master. I'd be happy to fix them if you'd like (they aren't related to your code). Can I push to your branch?

Sure, please do!

Oh definitely! Will finish it off.

Very nice and detailed descriptions!
Please check some typos and add dots at the end for the consistency with descriptions in other files.

Done the needful.

Looks good to me! @StrikerRUS I didn't want to overstep and dismiss your blocking review, so you'll have to approve before this can be merged.


Graph API v15.0

Dear All,
I have recently received recurring emails from Facebook stating that I need to update my applications that currently access the API v15.0.
Our project currently uses:
"react-native-fbsdk-next": "^11.1.0"
"react-native": "0.73.9"
Is this solved by updating the SDK version?
Thanks!

So you are getting emails saying you need to update
Updates are available here
I'm not sure what the question is? (that is, it seems obvious?)
Update.


Toy benchmark for testing

Toy Benchmark
Select a small subset from the VNNCOMP benchmark that can be used for testing and prototyping. Keep it (very) small so we can keep it inside the repository without adding too much bloat in size

https://github.com/ChristopherBrix/vnncomp2022_benchmarks/tree/main


Fixed throw exception if new version has a different media type

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Fixed tickets
fixes #1889

Related issues/PRs
https://github.com/sulu-io/sulu-standard/pull/646

License
MIT

Documentation PR
none

What's in this PR?
This PR adding validation of the media type for new versions.

@wachterjohannes This PR has also conflicts keeping the tests from being executed.

@danrot fixed


[web]: Stripe on boarding process in Flutter

The developer has integrated the initial payment function of stripe connect, however is unable to onboard with the login and log out function in the stripe account.  Stripe referred us to Flutter for support to enable this function to be integrated into the app.
Would really appreciate any support available to enable the development to continue.
Many thanks.

Hi @BeeAnytime
It seems you are asking for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Update CHANGELOG.md and version.rb for v2.7.2

Update CHANGELOG.md and version.rb for v2.7.2.

CI passed -> merging.