can't convert macro action to keycode

Information

ratbagd version: 0.17
Distribution:  Debian Linux Bookworm (running as VirtualBox, Logitech G500 shared from Host)
Kernel version: Linux 6.1.0-18-amd64 x86_64 GNU/Linux

Device info (if applicable):
$ ratbagctl Logitech G500 info
singing-gundi - Logitech G500
             Model: usb:046d:c068:0
 Number of Buttons: 13
    Number of Leds: 0
Number of Profiles: 1
Profile 0: (active)
  Name: Profile 1
  Report Rate: 500Hz
  Resolutions:
    0: 400x400dpi
    1: 800x800dpi (active)
    2: 2000x2000dpi
    3: <disabled>
    4: <disabled>
  Button: 0 is mapped to 'button 1'
  Button: 1 is mapped to 'button 2'
  Button: 2 is mapped to 'button 3'
  Button: 3 is mapped to 'button 8'
  Button: 4 is mapped to macro '↕X ↕G ↕A'
  Button: 5 is mapped to 'button 6'
  Button: 6 is mapped to 'wheel-left'
  Button: 7 is mapped to 'wheel-right'
  Button: 8 is mapped to 'resolution-up'
  Button: 9 is mapped to 'resolution-down'
  Button: 10 is mapped to UNKNOWN
  Button: 11 is mapped to UNKNOWN
  Button: 12 is mapped to UNKNOWN

Describe the bug
Unable to set Macros (commiting in Piper will return error, ratbagctl aswell)
To Reproduce
Steps to reproduce the behavior:
ratbagctl -vvv "Logitech G500" profile 0 button 4 action set macro KEY_X KEY_G KEY_A
resulting in output of ratbagd:
ratbag error: hidpp10: can't convert macro action to keycode in button 4
ratbag error: hidpp10: failed to update buttons (-22)
ratbagd error: error committing device (-1000)
but listing shows populated Macro
ratbagctl "Logitech G500" info
Button: 4 is mapped to macro '↕X ↕G ↕A'
Logs
Please start the daemon with verbosity and reproduce the issue.
ratbag debug: New device: Logitech G500
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: device assigned driver hidpp10
ratbag debug: hidraw info: bus 0x03 vendor 0x46d product 0xffffc068
ratbag debug: Logitech G500 is device '/dev/hidraw1'.
ratbag debug: Parsing HID report descriptor
ratbag debug: Parsing HID report descriptor
ratbag debug: hidraw info: bus 0x03 vendor 0x46d product 0xffffc068
ratbag debug: Logitech G500 is device '/dev/hidraw2'.
ratbag debug: Parsing HID report descriptor
ratbag debug: Parsing HID report descriptor
ratbag debug: - HID report ID 01
ratbag debug: - HID report ID 03
ratbag debug: - HID report ID 10
ratbag debug: - HID report ID 11
ratbag raw: Fetching individual features (0x1)
ratbag raw: hidpp10 tx:  10 | 00 | 81 | 01 | 00 00 00
ratbag raw: hidpp write:  10 00 81 01 00 00 00
ratbag raw: hidpp read:   10 00 81 01 00 00 00
ratbag raw: hidpp10 rx:  10 | 00 | 81 | 01 | 00 00 00
ratbag raw: Fetching HID++ notifications (00)
ratbag raw: hidpp10 tx:  10 | 00 | 81 | 00 | 00 00 00
ratbag raw: hidpp write:  10 00 81 00 00 00 00
ratbag raw: hidpp read:   10 00 8f 81 00 02 00
ratbag raw:     HID++ error from the device (0): ERR_INVALID_ADDRESS (02)
ratbag raw: hidpp10 rx:  10 | 00 | 8f | 81 | 00 02 00
ratbag raw: Fetching current resolution (0x63)
ratbag raw: hidpp10 tx:  10 | 00 | 83 | 63 | 00 00 00
ratbag raw: hidpp write:  10 00 83 63 00 00 00
ratbag raw: hidpp read:   11 00 83 63 22 00 22 00 80 01 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | 63 | 22 00 22 00 80 01 00 00 00 00 00 00 00 00 00 00
ratbag raw: Fetching LED status (0x51)
ratbag raw: hidpp10 tx:  10 | 00 | 81 | 51 | 00 00 00
ratbag raw: hidpp write:  10 00 81 51 00 00 00
ratbag raw: hidpp read:   10 00 81 51 22 12 00
ratbag raw: hidpp10 rx:  10 | 00 | 81 | 51 | 22 12 00
ratbag raw: Fetching USB refresh rate (0x64)
ratbag raw: hidpp10 tx:  10 | 00 | 81 | 64 | 00 00 00
ratbag raw: hidpp write:  10 00 81 64 00 00 00
ratbag raw: hidpp read:   10 00 81 64 02 00 00
ratbag raw: hidpp10 rx:  10 | 00 | 81 | 64 | 02 00 00
ratbag raw: Fetching optical sensor settings (0x61)
ratbag raw: hidpp10 tx:  10 | 00 | 81 | 61 | 00 00 00
ratbag raw: hidpp write:  10 00 81 61 00 00 00
ratbag raw: hidpp read:   10 00 81 61 4c 10 10
ratbag raw: hidpp10 rx:  10 | 00 | 81 | 61 | 4c 10 10
ratbag raw: Fetching current profile (0xf)
ratbag raw: hidpp10 tx:  10 | 00 | 81 | 0f | 00 00 00
ratbag raw: hidpp write:  10 00 81 0f 00 00 00
ratbag raw: hidpp read:   10 00 81 0f 00 00 00
ratbag raw: hidpp10 rx:  10 | 00 | 81 | 0f | 00 00 00
ratbag raw: Fetching the profiles' directory
ratbag raw: Reading memory page 1, offset 0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 00 00
ratbag raw: hidpp write:  10 00 83 a2 01 00 00
ratbag raw: hidpp read:   11 00 83 a2 02 00 01 ff ff ff 00 11 22 11 00 2a 00 2a 22 12
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 02 00 01 ff ff ff 00 11 22 11 00 2a 00 2a 22 12
ratbag raw: Reading memory page 1, offset 0x10
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 08 00
ratbag raw: hidpp write:  10 00 83 a2 01 08 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x20
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 10 00
ratbag raw: hidpp write:  10 00 83 a2 01 10 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x30
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 18 00
ratbag raw: hidpp write:  10 00 83 a2 01 18 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x40
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 20 00
ratbag raw: hidpp write:  10 00 83 a2 01 20 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x50
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 28 00
ratbag raw: hidpp write:  10 00 83 a2 01 28 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x60
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 30 00
ratbag raw: hidpp write:  10 00 83 a2 01 30 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x70
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 38 00
ratbag raw: hidpp write:  10 00 83 a2 01 38 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x80
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 40 00
ratbag raw: hidpp write:  10 00 83 a2 01 40 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x90
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 48 00
ratbag raw: hidpp write:  10 00 83 a2 01 48 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0xa0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 50 00
ratbag raw: hidpp write:  10 00 83 a2 01 50 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0xb0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 58 00
ratbag raw: hidpp write:  10 00 83 a2 01 58 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0xc0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 60 00
ratbag raw: hidpp write:  10 00 83 a2 01 60 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0xd0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 68 00
ratbag raw: hidpp write:  10 00 83 a2 01 68 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0xe0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 70 00
ratbag raw: hidpp write:  10 00 83 a2 01 70 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0xf0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 78 00
ratbag raw: hidpp write:  10 00 83 a2 01 78 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x100
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 80 00
ratbag raw: hidpp write:  10 00 83 a2 01 80 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x110
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 88 00
ratbag raw: hidpp write:  10 00 83 a2 01 88 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x120
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 90 00
ratbag raw: hidpp write:  10 00 83 a2 01 90 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x130
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 98 00
ratbag raw: hidpp write:  10 00 83 a2 01 98 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x140
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 a0 00
ratbag raw: hidpp write:  10 00 83 a2 01 a0 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x150
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 a8 00
ratbag raw: hidpp write:  10 00 83 a2 01 a8 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x160
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 b0 00
ratbag raw: hidpp write:  10 00 83 a2 01 b0 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x170
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 b8 00
ratbag raw: hidpp write:  10 00 83 a2 01 b8 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x180
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 c0 00
ratbag raw: hidpp write:  10 00 83 a2 01 c0 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x190
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 c8 00
ratbag raw: hidpp write:  10 00 83 a2 01 c8 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x1a0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 d0 00
ratbag raw: hidpp write:  10 00 83 a2 01 d0 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x1b0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 d8 00
ratbag raw: hidpp write:  10 00 83 a2 01 d8 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x1c0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 e0 00
ratbag raw: hidpp write:  10 00 83 a2 01 e0 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x1d0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 e8 00
ratbag raw: hidpp write:  10 00 83 a2 01 e8 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x1e0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 f0 00
ratbag raw: hidpp write:  10 00 83 a2 01 f0 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ratbag raw: Reading memory page 1, offset 0x1f0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 01 f8 00
ratbag raw: hidpp write:  10 00 83 a2 01 f8 00
ratbag raw: hidpp read:   11 00 83 a2 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 24 9f
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff ff ff ff ff ff ff ff ff ff ff ff ff ff 24 9f
ratbag raw: Fetching profile 0
ratbag raw: Reading memory page 2, offset 0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 00 00
ratbag raw: hidpp write:  10 00 83 a2 02 00 00
ratbag raw: hidpp read:   11 00 83 a2 ff 00 00 80 00 11 00 11 22 11 00 22 00 22 22 12
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | ff 00 00 80 00 11 00 11 22 11 00 22 00 22 22 12
ratbag raw: Reading memory page 2, offset 0x10
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 08 00
ratbag raw: hidpp write:  10 00 83 a2 02 08 00
ratbag raw: hidpp read:   11 00 83 a2 00 55 00 55 22 22 00 00 00 00 12 22 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 55 00 55 22 22 00 00 00 00 12 22 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x20
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 10 00
ratbag raw: hidpp write:  10 00 83 a2 02 10 00
ratbag raw: hidpp read:   11 00 83 a2 12 21 01 81 10 10 02 81 01 00 81 02 00 81 04 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 12 21 01 81 10 10 02 81 01 00 81 02 00 81 04 00
ratbag raw: Reading memory page 2, offset 0x30
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 18 00
ratbag raw: hidpp write:  10 00 83 a2 02 18 00
ratbag raw: hidpp read:   11 00 83 a2 81 80 00 82 00 1b 81 20 00 83 01 00 83 02 00 83
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 81 80 00 82 00 1b 81 20 00 83 01 00 83 02 00 83
ratbag raw: Reading memory page 2, offset 0x40
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 20 00
ratbag raw: hidpp write:  10 00 83 a2 02 20 00
ratbag raw: hidpp read:   11 00 83 a2 04 00 83 08 00 ff ff 00 ff ff 00 ff ff 00 4c 47
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 04 00 83 08 00 ff ff 00 ff ff 00 ff ff 00 4c 47
ratbag raw: Reading memory page 2, offset 0x50
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 28 00
ratbag raw: hidpp write:  10 00 83 a2 02 28 00
ratbag raw: hidpp read:   11 00 83 a2 53 30 32 50 00 72 00 6f 00 66 00 69 00 6c 00 65
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 53 30 32 50 00 72 00 6f 00 66 00 69 00 6c 00 65
ratbag raw: Reading memory page 2, offset 0x60
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 30 00
ratbag raw: hidpp write:  10 00 83 a2 02 30 00
ratbag raw: hidpp read:   11 00 83 a2 00 20 00 31 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 20 00 31 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x70
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 38 00
ratbag raw: hidpp write:  10 00 83 a2 02 38 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x80
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 40 00
ratbag raw: hidpp write:  10 00 83 a2 02 40 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x90
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 48 00
ratbag raw: hidpp write:  10 00 83 a2 02 48 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0xa0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 50 00
ratbag raw: hidpp write:  10 00 83 a2 02 50 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0xb0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 58 00
ratbag raw: hidpp write:  10 00 83 a2 02 58 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0xc0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 60 00
ratbag raw: hidpp write:  10 00 83 a2 02 60 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0xd0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 68 00
ratbag raw: hidpp write:  10 00 83 a2 02 68 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0xe0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 70 00
ratbag raw: hidpp write:  10 00 83 a2 02 70 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0xf0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 78 00
ratbag raw: hidpp write:  10 00 83 a2 02 78 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x100
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 80 00
ratbag raw: hidpp write:  10 00 83 a2 02 80 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x110
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 88 00
ratbag raw: hidpp write:  10 00 83 a2 02 88 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x120
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 90 00
ratbag raw: hidpp write:  10 00 83 a2 02 90 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x130
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 98 00
ratbag raw: hidpp write:  10 00 83 a2 02 98 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x140
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 a0 00
ratbag raw: hidpp write:  10 00 83 a2 02 a0 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x150
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 a8 00
ratbag raw: hidpp write:  10 00 83 a2 02 a8 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x160
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 b0 00
ratbag raw: hidpp write:  10 00 83 a2 02 b0 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x170
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 b8 00
ratbag raw: hidpp write:  10 00 83 a2 02 b8 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x180
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 c0 00
ratbag raw: hidpp write:  10 00 83 a2 02 c0 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x190
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 c8 00
ratbag raw: hidpp write:  10 00 83 a2 02 c8 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x1a0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 d0 00
ratbag raw: hidpp write:  10 00 83 a2 02 d0 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x1b0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 d8 00
ratbag raw: hidpp write:  10 00 83 a2 02 d8 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x1c0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 e0 00
ratbag raw: hidpp write:  10 00 83 a2 02 e0 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x1d0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 e8 00
ratbag raw: hidpp write:  10 00 83 a2 02 e8 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x1e0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 f0 00
ratbag raw: hidpp write:  10 00 83 a2 02 f0 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag raw: Reading memory page 2, offset 0x1f0
ratbag raw: hidpp10 tx:  10 | 00 | 83 | a2 | 02 f8 00
ratbag raw: hidpp write:  10 00 83 a2 02 f8 00
ratbag raw: hidpp read:   11 00 83 a2 00 00 00 00 00 00 00 ff ff ff ff ff ff ff 33 0a
ratbag raw: hidpp10 rx:  11 | 00 | 83 | a2 | 00 00 00 00 00 00 00 ff ff ff ff ff ff ff 33 0a
ratbag raw: profile 0 is named 'Profile 1'
ratbag raw: *** macro starts at (0xff, 0x00fe) ***
ratbag raw: hidpp10: failed to read macro
ratbag raw: *** macro starts at (0xff, 0x00fe) ***
ratbag raw: hidpp10: failed to read macro
ratbag raw: *** macro starts at (0xff, 0x00fe) ***
ratbag raw: hidpp10: failed to read macro
ratbag raw: +++++++++++++++++++ Profile data: +++++++++++++++++
ratbag raw:  ff 00 00 80 00 11 00 11
ratbag raw:  22 11 00 22 00 22 22 12
ratbag raw:  00 55 00 55 22 22 00 00
ratbag raw:  00 00 12 22 00 00 00 00
ratbag raw:  12 21 01 81 10 10 02 81
ratbag raw:  01 00 81 02 00 81 04 00
ratbag raw:  81 80 00 82 00 1b 81 20
ratbag raw:  00 83 01 00 83 02 00 83
ratbag raw:  04 00 83 08 00 ff ff 00
ratbag raw:  ff ff 00 ff ff 00
ratbag raw: +++++++++++++++++++ Profile data end +++++++++++++++++
ratbag raw: Profile 0:
ratbag raw:   DPI mode: 400x400 dpi
ratbag raw:   LED status: 1:on 2:on 3:off 4:off
ratbag raw:   DPI mode: 800x800 dpi
ratbag raw:   LED status: 1:on 2:on 3:on 4:off
ratbag raw:   DPI mode: 2000x2000 dpi
ratbag raw:   LED status: 1:on 2:on 3:on 4:on
ratbag raw:   DPI mode: 0x0 dpi
ratbag raw:   LED status: 1:on 2:off 3:on 4:on
ratbag raw:   DPI mode: 0x0 dpi
ratbag raw:   LED status: 1:on 2:off 3:off 4:on
ratbag raw:   Angle correction: 1
ratbag raw:   Default DPI mode: 129
ratbag raw:   Refresh rate: 500
ratbag raw:   Button 0: button 1
ratbag raw:   Button 1: button 2
ratbag raw:   Button 2: button 3
ratbag raw:   Button 3: button 8
ratbag raw:   Button 4: key 27 modifier 0
ratbag raw:   Button 5: button 6
ratbag raw:   Button 6: special 1
ratbag raw:   Button 7: special 2
ratbag raw:   Button 8: special 4
ratbag raw:   Button 9: special 8
ratbag raw: Fetching current profile (0xf)
ratbag raw: hidpp10 tx:  10 | 00 | 81 | 0f | 00 00 00
ratbag raw: hidpp write:  10 00 81 0f 00 00 00
ratbag raw: hidpp read:   10 00 81 0f 00 00 00
ratbag raw: hidpp10 rx:  10 | 00 | 81 | 0f | 00 00 00
ratbag raw: Fetching current resolution (0x63)
ratbag raw: hidpp10 tx:  10 | 00 | 83 | 63 | 00 00 00
ratbag raw: hidpp write:  10 00 83 63 00 00 00
ratbag raw: hidpp read:   11 00 83 63 22 00 22 00 80 01 00 ff ff ff ff ff ff ff 33 0a
ratbag raw: hidpp10 rx:  11 | 00 | 83 | 63 | 22 00 22 00 80 01 00 ff ff ff ff ff ff ff 33 0a
ratbag debug: driver match found: Logitech HID++1.0
hidraw1: "Logitech G500", 1 profiles
ratbag debug: New device: Logitech G500
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: device assigned driver hidpp10
ratbag debug: hidraw info: bus 0x03 vendor 0x46d product 0xffffc068
ratbag debug: Logitech G500 is device '/dev/hidraw1'.
ratbag debug: Parsing HID report descriptor
ratbag debug: Parsing HID report descriptor
DBus server ready
ratbag error: hidpp10: can't convert macro action to keycode in button 4
ratbag error: hidpp10: failed to update buttons (-22)
ratbagd error: error committing device (-1000)
ratbag error: hidpp10: can't convert macro action to keycode in button 4
ratbag error: hidpp10: failed to update buttons (-22)
ratbagd error: error committing device (-1000)
First make sure it isn't running already.
$ ratbagd --verbose=raw
OUTPUT HERE

Additional context
Add any other context about the problem here.

Reproducable on real hardware (Lenovo T480s with debian bookworm) aswell

I'm getting a similar issue on Fedora 40

Well, (for me) it's totally useless then...


Issue with Xcode 13 beta 3

UIApplication.shared.windows.first?.rootViewController?.present(controller, animated: false)
        DispatchQueue.main.asyncAfter(deadline: .now()+0.1) {

'shared' is unavailable in application extensions for iOS: Use view controller based solutions where appropriate instead.

Manager.swift

Fixed with PR #7 waiting to Merge


Codeium Chat panel broken on startup

Does the activitylog.xml mention anything about LanguageServer.InitializeAsync()?
I got it fixed in #25 (LanguageServer.cs#L54), it was because the chat window was opened upon startup and it was getting the DTE too soon.


update repository links per my username change

There seems to be an issue locally resulting in coveralls.io errors:
Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}

This happens either when publishing or running yarn run test, although it appears that CI is able to run it. Initially I thought this was references to sprjr still in the code and remotes - but even after correcting that the issue persists.
This branch does not fix that yet, so is WIP while I try to figure it out.

I do see failures in Travis CI now though, which is good because I cycled the repo token in coveralls.io so I'd be upset if it worked TBH: https://travis-ci.org/github/stevey-p/react-localize/jobs/697836997#L279


The director's origin instance does not return proper headers

When running an object copy command and when the error returned is Attempt #1: Pelican director did not include mandatory X-Pelican-Namespace header in response the debug log does not include any headers

Closing this issue. The problem was that auto-discovery for the OSDF pointed to an old director (one still written in flask!). All new instances of the director should have this hammered out.


Send coverage results to codecov

@StephenTaylor-Kx someone with an admin access should activate Codecov integration for this repository and then we can update the URLs.  Meanwhile, please see   abalkin/pyq#1.

Moved to #45.


Log Out Macro

The only thing I feel this is missing is a logout macro, would be great to see it included in a future release as an optional bind

I've looked into this and I recommend just using http://lutbot.com/#/ if you want a logout macro. Nothing I implement will be as good as that for logging out, and I don't want to include cports.exe in my repository just to mimic that performance.


Reproduce experiments

Reproduce all experiments on SIM, IHDP and NEWS datasets
Run experiments with: https://github.com/NSAPH-Projects/tresnet-pm-mortality/blob/dev/scripts/benchmarks.sh
Pay attention to changes in dropout (increased to 0.2) and how it affects the results

Solved in #34


A transaction with a large amount of asset is failed

We need to change the logic of the "add all" button on the send screen
If the amount of the asset in the wallet = 3-4 * max_int 64, then the "add all" button takes all the coins, but the transaction fails with the "Key keeper malfunctionedr"
Note:  In CLI we maximum supported amount<PHONE_NUMBER>37 BEAMs 9551615 GROTH.

By romanov: limit amount per transaction

By romanov: limit amount per transaction

In UI we historically have 100M limit per transaction. So 'add all' now is 'add max' and max value is 100M even if the wallet has more assets.

In UI we historically have 100M limit per transaction. So 'add all' now is 'add max' and max value is 100M even if the wallet has more assets.

checked

checked


Move non-secret configurations from vault to this repo

Instead of storing a whole packit-service.yaml and fedora.toml in the vault, we store in the vault (in extra-vars.yml) only the private values.
The packit-service.yaml.j2 and fedora.toml.j2 templates are stored in secrets/<service>/<deployment> and processed during deployment.
Fixes #368

[ ] Where do we use secrets/template/ ? Document it or remove it.

Where do we use secrets/template/ ? Document it or remove it.

IIRC it is used in packit-service (openshift) tests with deploying or Zuul in here

IIRC it is used in packit-service (openshift) tests with deploying or Zuul in here

I can see that packit-service/files/deployment.yaml runs make generate-local-secrets in a cloned deployment repo, but that calls the generate-secrets role which has it's own templates.
Ditto playbooks/generate-local-secrets.yml in this repo.


[web, wasm] When wasm fails to load, print chrome details + option to update element

Right now if a demo is loaded in non-chrome and/or without the right flags nothing helpful happens

[ ] include that things are currently tested in Chrome v111 w/ which flags
[ ] Have some (pluggable) way so folks can show the error in html. Maybe look for a well defined function or something that could be overridden

CC @eyebrowsoffire @joshualitt

I think we should just close this. The bootstrapping code is going to just fall back to JS if needed, so there is no need for an error message.


Chunks are not sent to the player if no biome information is passed into the Column

When creating a new column to send to the client, if you use the constructor public Column(int x, int z, Chunk chunks[]) instead of public Column(int x, int z, Chunk chunks[], byte biomeData[]), then when the first constructor chains to the second, and passes a null argument, and the chunk is not created, and thus not sent to the client.
This could be solved by changing either:
    public Column(int x, int z, Chunk chunks[]) {         this(x, z, chunks, null);     }
to
    public Column(int x, int z, Chunk chunks[]) {         this(x, z, chunks, new byte[256]);     }
or changing:
public Column(int x, int z, Chunk chunks[], byte biomeData[]) {
    if(chunks.length != 16) {
        throw new IllegalArgumentException("Chunk array length must be 16.");
    }

    if(biomeData != null && biomeData.length != 256) {
        throw new IllegalArgumentException("Biome data array length must be 256.");
    }

    this.skylight = false;
    boolean noSkylight = false;
    for(int index = 0; index < chunks.length; index++) {
        if(chunks[index] != null) {
            if(chunks[index].getSkyLight() == null) {
                noSkylight = true;
            } else {
                this.skylight = true;
            }
        }
    }

    if(noSkylight && this.skylight) {
        throw new IllegalArgumentException("Either all chunks must have skylight values or none must have them.");
    }

    this.x = x;
    this.z = z;
    this.chunks = chunks;
    this.biomeData = biomeData;
}

to
public Column(int x, int z, Chunk chunks[], byte biomeData[]) {
    if(chunks.length != 16) {
        throw new IllegalArgumentException("Chunk array length must be 16.");
    }

    if(biomeData != null && biomeData.length != 256) {
        throw new IllegalArgumentException("Biome data array length must be 256.");
    }

    this.skylight = false;
    boolean noSkylight = false;
    for(int index = 0; index < chunks.length; index++) {
        if(chunks[index] != null) {
            if(chunks[index].getSkyLight() == null) {
                noSkylight = true;
            } else {
                this.skylight = true;
            }
        }
    }

    if(noSkylight && this.skylight) {
        throw new IllegalArgumentException("Either all chunks must have skylight values or none must have them.");
    }

    this.x = x;
    this.z = z;
    this.chunks = chunks;
    this.biomeData = Objects.nonNull(biomeData) ? biomeData : new byte[256];
}

This is intended behavior; see http://wiki.vg/Protocol#Chunk_Data

@Steveice10 But if that's the intended behavior, why is there a constructor for it?

@109C With biome data, it is considered to be supplying a full column. Without, it's supplying parts of a column, as noted in the protocol information.


The changes to enalbe VirtIO with sriov special qemu patches

Signed-off-by: HeYue<EMAIL_ADDRESS>

@feijiang1 @YadongQi @YuanjunHuang please help to review this patch.
This patch modify the virtio and virtio2d parameters to boot well with 27 qemu sriov special patches.
Has verified on ADL RVP, the sriov virtio gvt-d could boot well.
Verified on TGL NUC, the gvt-d, virtio boot well.


Cherry pick Windows7 powershell <2 fixes for 2.0.1 release

Codecov Report

Merging #855 into 2.0.x will decrease coverage by 0.16%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##            2.0.x     #855      +/-   ##
==========================================
- Coverage   96.49%   96.32%   -0.17%
==========================================
  Files          35       35
  Lines        3191     3375     +184
  Branches      268      482     +214
==========================================
+ Hits         3079     3251     +172
- Misses        112      114       +2
- Partials        0       10      +10

Impacted Files
Coverage Δ

browser/model/cygwin.js
100% <100%> (ø)
:arrow_up:

browser/services/platform.js
99.52% <100%> (+0.58%)
:arrow_up:

browser/model/devstudio.js
88.17% <0%> (-1.83%)
:arrow_down:

browser/model/helpers/downloader.js
96.94% <0%> (-1.52%)
:arrow_down:

browser/model/jbosseap.js
98.8% <0%> (-1.2%)
:arrow_down:

browser/pages/about/controller.js
21.05% <0%> (-1.17%)
:arrow_down:

browser/directives/componentPanel.js
14.28% <0%> (-1.1%)
:arrow_down:

browser/pages/confirm/controller.js
89.71% <0%> (-0.93%)
:arrow_down:

browser/services/data.js
97.03% <0%> (-0.92%)
:arrow_down:

browser/model/jbossfuse.js
99.21% <0%> (-0.79%)
:arrow_down:

... and 23 more

Continue to review full report at Codecov.

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


cannot find package "github.com/ethereum/go-ethereum/crypto/sha3

hello, i get this error when running make deps :
"
cannot find package "github.com/ethereum/go-ethereum/crypto/sha3" in any of:
/usr/lib/go-1.10/src/github.com/ethereum/go-ethereum/crypto/sha3 (from $GOROOT)
/root/go/src/github.com/ethereum/go-ethereum/crypto/sha3 (from $GOPATH)
Makefile:204: recipe for target 'deps' failed
make[1]: *** [deps] Error 1
make[1]: Leaving directory '/src/github.com/loomnetwork/loomchain'
Makefile:102: recipe for target 'deps' failed
make: *** [deps] Error 2 "
i followed all the steps gived on https://loomx.io/developers/en/relentless.html#build-the-relentless-smart-contract.
Any idea of how to solve it?
maybe see here can help to fix the makefile : https://github.com/ethereum/go-ethereum/issues/19320
thanks in advance

I think you misconfigured your GOPATH (step 2 an 3 in https://loomx.io/developers/en/relentless.html#getting-started)

I think you misconfigured your GOPATH (step 2 an 3 in https://loomx.io/developers/en/relentless.html#getting-started)

Thank you VM, but i exactly followed all the steps on 2 different server. And same error. Wich version of go do you recommend to use please?

It work for me now. Resolved the issue by reinstalling go with the command "sudo snap install go"

@edenweb1 thx. I will close the issue then


Add dependency graph image to docs

The image is now hosted at https://ibm.github.io/FHIR/images/fhir-dependency-graph.png

Now we just need to decide where to reference it from :-)
README?
FHIRServerUserGuide?
ModelGuide?

Now we just need to decide where to reference it from :-)
README?
FHIRServerUserGuide?
ModelGuide?

right... If I know where, I can raise the PR


Fix source directory of copy command

The copy command copies the whole template folder to the new directory. We need to copy only the content of the folder.

@ziyaddin this command is along with condition
"If your locale is missing..." (Line 29) meaning that the folder has not been created yet.
thanks for carefully checking this document. :+1:

Oh I see.


How to get status progress of tasks (clone, deploy vm from template...)

Hello,
I use vcenter 6.7
I deploy, clone vm from template ... by API  ( ... rest/com/vmware/vcenter/ovf/library-item/id:<...>?~action=deploy)
It run well, and create vm done after some minute
But how can I get status of this task (percent complete, success , failed ...) with sdk, api
Thank you!

Hi,
Please take a look at https://vmware.github.io/vsphere-automation-sdk-python/vsphere/6.7.1/com.vmware.cis.html#module-com.vmware.cis.task_client

Hi @anusha94 ,
If possible can you please share any sample or example to list, show info or show status of tasks for a VM using the above module.
Thanks,
Pushkar

Hi @pushkargr
I checked and it seems that we can get the task progress/status only for those operations that return a task object containing the task_id.
For your use case, you can checkout this sample
The deploy method returns a DeploymentResult object and you can check if the operation succeeded or not.
You can checkout other content-library related samples here
Thanks!

Oh I just realized that deploy vm was related to @dungla2011
@pushkargr
Like I mentioned task progress can be tracked only for those operations that return a task object. You can refer to the documentation to know the return types of different APIs

Thanks @anusha94, Is there any other way to list the currently running tasks on a VM with status apart from this SDK then?

Depends on what operations you are looking for. If they are older features like adding nic, serial ports, etc., you can consider using pyvmomi (SOAP based APIs)
The vSphere Automation SDK is for REST APIs (available from VC 6.5+)
See some of the usage of task in pyvmomi in this clone sample and tasks utility

Hi @pushkargr ,
So the UI uses SOAP APIs, in particular java bindings.
For Java, you can check out vSphere Management SDK
For python, refer pyvmomi

Closing this issue as the Automation SDK currently supports tasks progress for a limited set of operations. Other SDK references are mentioned in the above comment.


Front-end supplemental license

Tips

Thanks very much for contributing to Apache DolphinScheduler.
Please review https://dolphinscheduler.apache.org/en-us/community/index.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds checkstyle plugin.)
Brief change log
(for example:)

Add maven-checkstyle-plugin to root pom.xml

Verify this pull request
(Please pick either of the following options)
This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added dolphinscheduler-dao tests for end-to-end.
Added CronUtilsTest to verify the change.
Manually verified the change by testing locally.

Codecov Report

Merging #1548 into dev will decrease coverage by 0.01%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             dev   #1548      +/-   ##
========================================
- Coverage   7.79%   7.77%   -0.02%
========================================
  Files        272     272
  Lines      13641   13641
  Branches    2166    2166
========================================
- Hits        1063    1061       -2
- Misses     12506   12508       +2
  Partials      72      72

Impacted Files
Coverage Δ

...ache/dolphinscheduler/common/enums/ZKNodeType.java
0% <0%> (-100%)
:arrow_down:

Continue to review full report at Codecov.

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


Skip previously cracked IP

I still got many duplicates output from honeypot would be great if cbrutekrag could skip the same cracked IP

Hi @maulvi, sorry for the late response
You can simply skip the targets that have been identified as a honeypot, so you can avoid false positives, etc.
It is convenient for you?
You can discard any non-bruteforceable targets activating the "scan phase" using -s argument

Hi @maulvi, sorry for the late response
You can simply skip the targets that have been identified as a honeypot, so you can avoid false positives, etc.
It is convenient for you?
You can discard any non-bruteforceable targets activating the "scan phase" using -s argument

-s argument is not effective against sonicwall SSH firewall because it looks like legit openssh act like honeypot accept any password but has secondary login in ssh terminal, resulting many IP duplicates.
example
https://i.imgur.com/nEv6WTv.png

Hi @maulvi . Thanks for your feedback
Let me investigate this scenario

May I ask if this issue has been resolved?


Map controls not functioning in Chrome 40 on Windows 8

I'm unable to zoom in or out, as well as expand/collapse the layer switcher menu and select different layers. This seems to be an issue with click events not being handled.
To reproduce:

Go to http://dev.openlayers.org/examples/zoom.html in Chrome on Windows 8
Attempt to zoom in or out using the controls
Instead of zooming, the hash #zoomIn or #zoomOut appears in the address bar

Hi, I had the same issue. It's not working in Chrome, only on computers with touch screen. You should disable touch screen in Chrome and zooming will be working. You can do it like in this example:
http://ccm.net/faq/40811-google-chrome-how-to-disable-touch-input


feat: GitHub Actions

GitHub Actions

Signed-off-by: Andrii Soluk<EMAIL_ADDRESS>

Codecov Report

Merging #298 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #298   +/-   ##
=======================================
  Coverage   88.75%   88.75%
=======================================
  Files          39       39
  Lines        1975     1975
=======================================
  Hits         1753     1753
  Misses        122      122
  Partials      100      100

Continue to review full report at Codecov.

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


[WIP]deploy loki via template in launch.sh

@vprashar2929  PTAL.
By the ways, Loki pod can not be started due to resource limitation on my OCP cluster. I will have another try on the large cluster.

@vprashar2929 PTAL. By the ways, Loki pod can not be started due to resource limitation on my OCP cluster. I will have another try on the large cluster.

@anpingli Quick question is it mandatory to deploy Loki stack with resources provided in observatorium-logs-template.yaml I know they are big numbers but can't we reduce them to lower side. For eg. observatorium-metrics-template.yaml contains huge numbers but for deploying the components on testing OCP cluster we change those resources to minimum required and define them in observatorium-metrics.test.env. Can we do the same with Loki?


Fix ExplicitApi in core-data

Idea Description
Please add public if it is used in other classes, if not, please add private for all classes, property, and functions.

Reference images and links
https://kotlinlang.org/docs/whatsnew14.html#explicit-api-mode-for-library-authors

🙋

Thanks! Assigned!


share and shareReplay possibly shouldn't reset on completion?

Use case:
Cache all of the values from a slow source
IObservable source := Observable get5ValuesFromSlowSource().shareReplay(5);

source.subscribe(...) // gets the 5 values

// Some time later (after the above has finished)

source.subscribe(...) // re-gets the 5 values from the slowSource - should get them from the shareReplay cache instead

This is becoming more and more annoying


updated README_ja.md to japanese lessons #642

Missing translations now added!

Closed #641
Closed #642


ERROR: Service 'natlas-server' failed to build:

While setting up the docker image using docker-compose.yaml file (in centOS 7), i am getting the following error.
Building natlas-server
Step 1/31 : FROM node:12-stretch as webpack
ERROR: Service 'natlas-server' failed to build: Error parsing reference: "node:12-stretch as webpack" is not a valid repository/tag: invalid reference format

#Docker version
docker -v
Docker version 1.13.1, build 64e9980/1.13.1

issue solved by updating the docker.
Thanks


Multi-user support for basic channel

Closing this because the parachain -> ethereum part of this was done in #637 and I'm working on the opposite direction now


Smithsonian subproviders check reports all unit codes as outdated

Description

The Smithsonian provider DAG validates its list of subproviders (or unit codes) before attempting to pull data. Sometimes, it reports that all known unit codes are outdated and must be deleted. It seems like the Smithsonian API might be flaky. We should detect this and retry.
Reproduction

Run the Smithsonian provider script locally a few times, until you see the error.

You can also look at the last few runs in production.
Resolution

[ ] 🙋 I would be interested in resolving this bug.

It seems like the Smithsonian API might be flaky

I don't have any known contacts there, but it might be nice to find someone we could reach out to there about this as well.
I see the general<EMAIL_ADDRESS>email address exists, not sure if there's a better point of contact.

So far I've actually been unable to reproduce this locally 🤔


Checkpointing simple from_generator dataset iterator gives "PyFunc is stateful" error.

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
Yes
Source
binary
Tensorflow Version
2.12.0
Custom Code
Yes
OS Platform and Distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Trying to build a simple checkpointable dataset. As a first step trying to mimic the behavior of `tf.data.Dataset.range` so that it can be made more complex. Building the iteration logic via a generator results in `PyFunc is stateful` error.

Standalone code to reproduce the issue
def count():
  i = 0
  while i < 10:
    yield i
    i += 1

ds = tf.data.Dataset.from_generator(
    count, output_signature=tf.TensorSpec(shape=(), dtype=np.int32))

ckpt = tf.train.Checkpoint(iterator=it)
manager = tf.train.CheckpointManager(ckpt, '~/tf-ckpt', max_to_keep=2)
manager.save()

Relevant log output
_NotOkStatusException: FailedPreconditionError: {{function_node __wrapped__SerializeIterator_device_/job:localhost/replica:0/task:0/device:CPU:0}} PyFunc is stateful. [Op:SerializeIterator]

I was able to reproduce the issue in TF 2.11 and TF Nightly 2.12.0-dev20230123. Please find the gist here. Thank you.

from_generator datasets are not checkpointable due to their dependency on a Python runtime. That being said, it would be good to improve the error message to something clearer.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


[Event Request] Codeunit 22 Item Jnl.-Post Line - OnAfterInsertCapValueEntry

Hi, would it be possible to get an event OnAfterInsertCapValueEntry in codeunit 22 Item Jnl.-Post Line, procedure InsertCapValueEntry, like this :

?
Thanks

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


DatePicker: Add FixDay, FixMonth, FixYear

Description
Closes #2722

Allows overriding of the OnMonthSelected and OnYearClicked handlers
Introduces FixYear, FixMonth and FixDay Parameters, allowing for variations such as YearMonth, MonthDay, YearDay -Pickers
Hides Menu-Buttons to navigate to Year/Month/Day when the corresponding param is set

How Has This Been Tested?
Added  new tests for datepicker for possible scenarios of this feature.
Covered: Month-Day, Year-Month, Year-Day, Only Year, Only  Month, Only Day Pickers
Types of changes

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Code Style: I believe I used the right style ... in razor files the auto format did some weird formatting, so I formatted my changes manually

Thanks for PR, do you have gif or video to show the new features?

Code looks fine.
@elite-conveyancing would you look at it one more time please?

Hi @JonBunator, thanks for the review. Could you help me with that revert ... what exactly do I need to do? I did a fresh rebase against dev now.

Thanks a lot!

@steveoandrey
This is wrong i think, the fixed year, fixed year + day, fixed year + month version does not display the year in the top.

Hi @Garderoben
In my head it is actually by design but I understand your point, I ll create a new pr which changes it back
I will make the year button readonly if the year is fix and so on.
Perhaps I should add additional params in the sense of HideYearInHeader?


Refactor Registry <-> Target interface, introduce Provider

This PR implements the first pass of #1325. It is a draft to support discussion on #1325.
Breaking change: probe_rs::config::Registry must now be instantiated instead of calling bare functions inside probe_rs::config. Registry::default() is sufficient unless you wish to add_target_from_yaml(). This change affects all users, and much of this PR is plumbing &Registry around the various utilities.
probe_rs::provider is a new pub(crate) module, defining the Provider/Family/Variant traits described in my proposal. probe_rs::provider::{Generic,Builtin,File} are three Providers extracted from Registry and Target. These details are internal to probe-rs.
This PR affects autodetection, dropping probe_rs::config::ChipInfo and adding Provider::autodetect_arm(&self, &ArmChipInfo, &mut Memory). This change will enable specialized autodetection routines in future PRs yet retains the functionality of the current implementation.

@willglynn Thank you for tackling this beast :).  I would like to request that I be allowed to review this PR, for the sake of testing the integrity of probe-rs-debugger before you merge. I don't mind if stuff breaks, but I'd love the opportunity to adapt and ensure continuity of the offerings.
Also, if you have not already seen it, please have a look at #1212 ... I think it is related and it would be nice if we can factor in a future where the target can be configured to take into account variants in chips, boards (external memories) and probes.

Sure!
This approach could support #1212 by adding flash size as a field on a shared VariantConfig, or perhaps to a specialized (dyn) ProviderSpecificConfig: Serialize+Deserialize+Any. Registry could retain the config and pass a reference to Provider::families(), Family::variant(), and/or Provider::autodetect_arm() whenever it calls down. This would allow the Variants to customize their memory map and flash algorithms as appropriate when constructing a Target.

@noppej I got this branch to a spot where I think it did everything? If this is something probe-rs wants to merge then I can work on rebasing it again.

@Yatekii Can you give us a 👍 or 👎?
@willglynn Thank you for being willing to help. The PR was marked at "Draft", which is probably why it was overlooked in review. Apologies if that causes you extra rebase work.


Minor change

Line 63 refers to "batched based operation" while I think it should be "batch based operation"

@svchandramohan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; merging now. Thanks.


⚠ Jenkins Plugins Artifactory has degraded performance

In 6c0d39a, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1385 ms

Resolved: Jenkins Plugins Artifactory performance has improved in b1b5d1f after 50 minutes.


feat: Few more interesting queries to track

Description
Just adding few more interesting queries to track in load test
How Has This Been Tested?
Tested the queries manually in OCP console and as part of similar config file
Checklist:

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/test max-concurrency-basic

/retest

/retest

/test max-concurrency-basic

/retest-required

/lgtm

/test max-concurrency-basic

/test max-concurrency-basic

/hold

/lgtm

/unhold

/hold

/unhold


Also a POST example.

I need to return a mocked response based on an json object passed in the body of a POST. Can this be done?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4df5cb3a-5bb7-c6c0-dbef-9cf9b51ea264
Version Independent ID: 68e97872-e73c-83a4-6856-3705a705e23c
Content: Mock API responses with the Azure portal
Content Source: articles/api-management/mock-api-responses.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

@nezoic Thanks for the question! We will review and get back to you!

@nezoic The mock-response policy works for all operations. You would have to create an operation for the HTTP method that you need and use the policy as required.

@nezoic Just following up here... Hope my previous comment clears things up.

@nezoic Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Lets-Plot: geom_contourf() instead of geom_contour()

In section Common Plots / Contour Plot you could replace the code for Lets-Plot with
contour_data = {'x': X.flatten(), 'y': Y.flatten(), 'z': Z.flatten()}
(
    ggplot(contour_data)
    + geom_contourf(aes(x='x', y='y', z='z', fill='..level..'))
    + scale_fill_viridis(option="plasma")
    + ggtitle("Maths equations don't currently work")
)

This allows to build a nicer looking plot:

It's already been replaced in PR #43, if you prefer that way of updating code.

closed in #43


PDO::FETCH_GROUP fetch mode is not working at all

Laravel Version: 5.5.34
PHP Version: 7.1

Description:
Pay attention to the select() method of Illuminate\Database\Connection.php:
Laravel 5.5
    public function select($query, $bindings = [], $useReadPdo = true)
    {
        return $this->run($query, $bindings, function ($query, $bindings) use ($useReadPdo) {
            if ($this->pretending()) {
                return [];
            }

            // For select statements, we'll simply execute the query and return an array
            // of the database result set. Each element in the array will be a single
            // row from the database table, and will either be an array or objects.
            $statement = $this->prepared($this->getPdoForSelect($useReadPdo)
                              ->prepare($query));

            $this->bindValues($statement, $this->prepareBindings($bindings));

            $statement->execute();

            return $statement->fetchAll();
        });
    }

Laravel 5.2
    public function select($query, $bindings = [], $useReadPdo = true)
    {
        return $this->run($query, $bindings, function ($me, $query, $bindings) use ($useReadPdo) {
            if ($me->pretending()) {
                return [];
            }
            // For select statements, we'll simply execute the query and return an array
            // of the database result set. Each element in the array will be a single
            // row from the database table, and will either be an array or objects.
            $statement = $this->getPdoForSelect($useReadPdo)->prepare($query);
            $statement->execute($me->prepareBindings($bindings));
            $fetchMode = $me->getFetchMode();
            $fetchArgument = $me->getFetchArgument();
            $fetchConstructorArgument = $me->getFetchConstructorArgument();
            if ($fetchMode === PDO::FETCH_CLASS && ! isset($fetchArgument)) {
                $fetchArgument = 'StdClass';
                $fetchConstructorArgument = null;
            }
            return isset($fetchArgument)
                ? $statement->fetchAll($fetchMode, $fetchArgument, $fetchConstructorArgument)
                : $statement->fetchAll($fetchMode);
        });
    }

... and this part of code from official 5.4 upgrade, thaty forced us to set fetch mode through some Event thing:
Event::listen(StatementPrepared::class, function ($event) {
    $event->statement->setFetchMode(...);
});

We can see, that after upgrade $fetchMode parameter is now should be set directly to PDOStatement object, instead of passing as fetchAll() argument. Actually, there is absolutely no difference, if you use primitive fetch modes like FETCH_ASSOC, FETCH_OBJ. But it does not work at all, when you use fetch modes, targeted for multiple results, like FETCH_GROUP.
Unfortunately this is not well documented in php docs but you can check detailed examples of that problem in this stackoverflow thread:
https://stackoverflow.com/questions/20620886/pdostatement-getting-different-results-between-fetchallmode-and-setfetch
TLDR of author investigation, crawling native php C code

The list of constants, supported by setFetchMode (PDOStatement method) does not include the PDO::FETCH_GROUP

It was working for sure before upgrade, but not working with this type of constants after.
Steps To Reproduce:
$fetchMode = PDO::FETCH_GROUP | PDO::FETCH_ASSOC;
\Event::listen(StatementPrepared::class, function ($event) use ($fetchMode) {
        $event->statement->setFetchMode($fetchMode);
});

app('db')->table('fruits')->insert([['name' => 'apple', 'color' => 'green'], ['name' => 'pear', 'color' => 'yellow']]);

$result = app('db')->table('fruits')->get();

dd($result);

Expected result (results are grouped by the first column value - as it must be using FETCH_GROUP):
Illuminate\Support\Collection {
  #items: array:2 [
    "apple" => array:1 [
      0 => array:1 [
        "color" => "green"
      ]
    ]
    "pear" => array:1 [
      0 => array:1 [
        "color" => "yellow"
      ]
    ]
  ]
}

Actual result (results are not grouped - only FETCH_ASSOC mode applied):
Illuminate\Support\Collection {
  #items: array:2 [
    0 => array:2 [
      "name" => "apple"
      "color" => "green"
    ]
    1 => array:2 [
      "name" => "pear"
      "color" => "yellow"
    ]
  ]
}

Do you have an idea for a fix?

I'm currently thinking on that, however with this setFetchMode() callback it's hard to do smth elegant ) Anything that passes $fetchMode not into statement but as fetchAll() argument makes the whole idea of the code below useless. Actually almost reverting back to previous version...
Event::listen(StatementPrepared::class, function ($event) {
    $event->statement->setFetchMode(...);
});

My understanding from the whole change back then was to basically discourage alternative fetch modes.
Together with Eloquent apparently they caused all kind of (support) issues.
But on the way the flexibility was sacrificed for regular queries.

I don't think it's meant to work with this mode tbh. If you want this to be supported again it's best to open up an issue in https://github.com/laravel/ideas to get some support first.

Theres another option I find to by pass it
Add env DB_FETCHMODE=FETCH_ASSOC
In config/database add for connections.mysql
'fetch_mode' => env('DB_FETCHMODE', 'FETCH_ASSOC'),
In illuminate/datbase/connection.php replace prepared function with
protected function prepared (PDOStatement $statement){ $config = $this->config; $statement->setFetchMode($config['fetch_mode'] == "FETCH_OBJ" ? 5 : ($config['fetch_mode'] == "FETCH_NUM" ? 3 : 2)); $this->event(new Events\StatementPrepared( $this, $statement )); return $statement; }
This make default FETCH_ASSOC for your application
Then if you want to change it like before,
add config(['database.connections.mysql.fetch_mode' => 'FETCH_OBJ']);
a replacement of DB::setFetchMode(PDO::FETCH_ASSOC);


property support

I can see the usefulness of this, but I'm not sure I want to change from matching the original Kefir.Bus API, and I'm not a big fan of having a function that returns different types of values (stream or property) depending on its parameters. None of Kefir's own functions do that either to my knowledge.
It's easy enough to write a function wrapping kefir-bus to make a property-bus like this, which I'd rather have applications interested in doing this do.


Added "-format" for gedcomq

The "-format" option allows gedcomq to output in two new formats; "pretty-json" and "csv".

This change is

Codecov Report

Merging #178 into master will increase coverage by 0.4%.
The diff coverage is 50%.

@@            Coverage Diff            @@
##           master     #178     +/-   ##
=========================================
+ Coverage   49.16%   49.57%   +0.4%
=========================================
  Files         158      160      +2
  Lines        4593     4662     +69
=========================================
+ Hits         2258     2311     +53
- Misses       2294     2306     +12
- Partials       41       45      +4

Impacted Files
Coverage Δ

gedcomdiff/main.go
0% <0%> (ø)
:arrow_up:

simple_node.go
78.12% <0%> (-3.85%)
:arrow_down:

util/cli.go
0% <0%> (ø)

q/formatter.go
74.64% <74.64%> (ø)

Continue to review full report at Codecov.

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


chore(deps): update renovate/renovate docker tag to v35.144.2

This PR contains the following updates:

Package
Update
Change

renovate/renovate
minor
35.143.0 -> 35.144.2

Release Notes

renovatebot/renovate
v35.144.2
Compare Source
Build System

deps: update dependency glob to v10.3.1 (#23031) (888d953)

v35.144.1
Compare Source
Documentation

partial rewrite developer docs (#23015) (a7f6514)
remove obsolete WIP message for bazel-module manager (#23024) (4ae9fff)

Miscellaneous Chores

containerbase: log details when no releases found (#23008) (f017f05)
deps: update dependency graphql to v16.7.0 (#23026) (1ae6e98)
deps: update dependency graphql to v16.7.1 (#23027) (a83634a)

Code Refactoring

exec: More coverage fixes (#23021) (756a1c9)
Fix exec utils coverage (#23018) (36ff13a)
http: Fix coverage (#23004) (ce41717)
override return type of JSON.parse (#23011) (2d77984)

Build System

deps: update dependency glob to v10.3.0 (#23030) (98dc2f2)

v35.144.0
Compare Source
Features

Clone objects via wrapper (#22970) (53263bb)

v35.143.1
Compare Source
Bug Fixes

Sanitize utils coverage (#22995) (4eb11d1)
Url utils coverage (#22994) (89c9691)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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


Add -Encoding ASCII to Out-File command

If you wanted to make a pull request for that new command line param for save to file, I will review it. If not, I should be able to add that pretty easy. I think I originally had it that way and then changed it to be more consistent with the Bash version.
I will add the -Encoding ASCII switch to the Out-File. I wasn't aware of the dbcs issue.
Originally posted by @steppsr in https://github.com/steppsr/getxchtxPS/issues/7#issuecomment-1105422575

v0.2.0


offer more verifiable installation methods

First of all, to make sure this doesn't come off too ungrateful: thanks for the awesome project! :innocent:
Given the current prevalence of supply-chain attacks it would be great if we could have some more verifiable (e.g. reproducible) installation methods than piping arbitrary shellscripts.
Having community binaries that can be reproduced from code means there are considerably more audit possibilities, which makes it harder for any eventual mallicious tampering to go unnoticed.
I don't quite understand the reasoning behind not supporting go install, but even if that is out of the question, providing any way to reproduce the downloadable binaries would be a net win, even if we have to jump through some hoops to reproduce them.
This improved verifiability would also trickle down to other installation methods like the container images.
I understand there may be some specifics regarding enterprise builds which the community doesn't have access to, but I'd be willing to lend some time to implement this, if the maintainers agree with the premise :innocent:

Hey! Note, binaries can also be downloaded from our website:

For example: https://release.ariga.io/atlas/atlas-darwin-amd64-v0.24.0

Closing, as there is no action to take here, but feel free to join our Discord and continue the discussion there.


Don't use android:allowBackup="true" in the library AndroidManifest

Hello,
Is android:allowBackup="true" of any use in your library?
Otherwise I would say as filipmaelbrancke on:
https://github.com/medyo/android-about-page/issues/6
Thanks !

Hi,
I'm having the same question with @Arkillon as well, to be honest i had a really bad experience when it's set is true before (uninstalled and app remembered previous settings, it was nightmare..), so i was wondering if it can be set as false intead @Tourenathan-G5organisation
if it's not possible, is there a way around for my app not 'backed up'?


Filter syntax is wrong

The syntax in section "Filtering Data on the Page" is described as
&filter='<field>'-IS-'<value>'[-AND-'<field>'-IS-'<value>']
but it is in reality
&filter='<field>' IS '<value>'[ AND '<field>' IS '<value>']
There is no mentioned that '-' are space in reality. Using -AND- and -IS- is not working...

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 33f33556-5071-49c4-f035-b731c1b27274
Version Independent ID: 73b81c02-b93b-2e86-18b8-91c66234f590
Content: Opening a Page in the Microsoft Dynamics NAV Web Client by Using a URL - Dynamics NAV
Content Source: dynamics-nav/Opening-a-Page-in-the-Microsoft-Dynamics-NAV-Web-Client-by-Using-a-URL.md
Product: dynamics-nav-2018
GitHub Login: @jswymer

Thanks for the feedback! The article has been fixed and an update will be published soon.


Inserting wrong password shows error [Object object] instead of something more informative

@AlbertoCasasOrtiz I am now getting this. Could we return a more informative error? Thanks

@AlbertoCasasOrtiz we also get a weird error when the username does not exist. Thanks.

@AlbertoCasasOrtiz I am still have the error above when inserting the wrong password or a non existing username


No such file or directory page_client-reference-manifest.js with Route Groups

I just migrated from app/central/... to app/(central)/... to share a layout but remove the url grouping, as explained in the nextjs docs here: https://nextjs.org/docs/app/building-your-application/routing/route-groups
But this breaks my SST deploy / OpenNext build. My dir layout is:
tree -L 2 app/
app/
├── (central)
│   ├── collection
│   ├── discovery
│   ├── layout.tsx
│   ├── manifesto
│   ├── page.tsx
│   ├── settings
│   └── symposium
├── _constants
│   └── server.ts
├── api
│   └── auth
├── dev
│   └── page.tsx
├── favicon.ico
├── fonts
│   ├── GeistMonoVF.woff
│   └── GeistVF.woff
├── global-error.tsx
├── globals.css
├── layout.tsx
├── lib
│   └── routes.ts
├── onboarding
│   ├── assignment1
│   ├── assignment2
│   ├── assignment3
│   ├── assignment4
│   ├── loading.tsx
│   └── welcome
└── page.tsx

The error message:
npx open-next build
Next.js version : 14.2.13
OpenNext v3.2.1

┌─────────────────────────────────┐
│ OpenNext — Building Next.js app │
└─────────────────────────────────┘

yarn run v1.22.19
$ next build
  ▲ Next.js 14.2.13
  - Environments: .env.local
  - Experiments (use with caution):
    · webpackBuildWorker
    · instrumentationHook

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ✓ Collecting page data
 ✓ Generating static pages (18/18)
   Finalizing page optimization  .   Collecting build traces
 ✓ Collecting build traces
 ⚠ Failed to copy traced files for /home/mover/lekondo-cotton/.next/server/app/(central)/page.js [Error: ENOENT: no such file or directory, copyfile '/home/mover/lekondo-cotton/.next/server/app/(central)/page_client-reference-manifest.js' -> '/home/mover/lekondo-cotton/.next/standalone/.next/server/app/(central)/page_client-reference-manifest.js'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'copyfile',
  path: '/home/mover/lekondo-cotton/.next/server/app/(central)/page_client-reference-manifest.js',
  dest: '/home/mover/lekondo-cotton/.next/standalone/.next/server/app/(central)/page_client-reference-manifest.js'
}
 ✓ Finalizing page optimization

Route (app)                                        Size     First Load JS
┌ ƒ /                                              3.58 kB         249 kB
├ ○ /_not-found                                    1.03 kB         184 kB
├ ƒ /api/auth/[auth0]                              0 B                0 B
├ ƒ /api/auth/dev/dangerouslyGetAPIToken           0 B                0 B
├ ƒ /collection                                    1.15 kB         189 kB
├ ƒ /collection/[collectionId]                     8.8 kB          271 kB
├ ƒ /collection/[collectionId]/item/[itemId]       3.33 kB         228 kB
├ ƒ /collection/[collectionId]/item/[itemId]/edit  413 B           225 kB
├ ○ /dev                                           1.48 kB         189 kB
├ ƒ /discovery                                     322 B           183 kB
├ ƒ /manifesto                                     323 B           183 kB
├ ○ /onboarding/assignment1                        2.56 kB         221 kB
├ ○ /onboarding/assignment2                        2.7 kB          236 kB
├ ○ /onboarding/assignment3                        2.45 kB         263 kB
├ ○ /onboarding/assignment4                        3.53 kB         229 kB
├ ○ /onboarding/welcome                            673 B           191 kB
├ ƒ /settings                                      322 B           183 kB
├ ƒ /settings/privacy                              1.57 kB         197 kB
├ ƒ /settings/profile                              1.66 kB         213 kB
└ ƒ /symposium/[tag]                               5.95 kB         224 kB
+ First Load JS shared by all                      183 kB
  ├ chunks/52774a7f-acd6185c7912d037.js            36.1 kB
  ├ chunks/5347-99e5327102b28534.js                90.4 kB
  ├ chunks/fd9d1056-7ab42e1942c648c4.js            53.8 kB
  └ other shared chunks (total)                    2.53 kB

ƒ Middleware                                       160 kB

○  (Static)   prerendered as static content
ƒ  (Dynamic)  server-rendered on demand

Done in 79.31s.

┌──────────────────────────────┐
│ OpenNext — Generating bundle │
└──────────────────────────────┘

Bundling middleware function...
Bundling static assets...
Bundling cache assets...
Building server function: default...
node:fs:2969
  handleErrorFromBinding(ctx);
  ^

Error: ENOENT: no such file or directory, copyfile '/home/mover/lekondo-cotton/.next/standalone/.next/server/app/(central)/page_client-reference-manifest.js' -> '/home/mover/lekondo-cotton/.open-next/server-functions/default/.next/server/app/(central)/page_client-reference-manifest.js'
    at copyFileSync (node:fs:2969:3)
    at file:///home/mover/lekondo-cotton/node_modules/@opennextjs/aws/dist/build/copyTracedFiles.js:144:13
    at Map.forEach (<anonymous>)
    at copyTracedFiles (file:///home/mover/lekondo-cotton/node_modules/@opennextjs/aws/dist/build/copyTracedFiles.js:115:17)
    at generateBundle (file:///home/mover/lekondo-cotton/node_modules/@opennextjs/aws/dist/build/createServerBundle.js:108:11)
    at createServerBundle (file:///home/mover/lekondo-cotton/node_modules/@opennextjs/aws/dist/build/createServerBundle.js:69:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async build (file:///home/mover/lekondo-cotton/node_modules/@opennextjs/aws/dist/build.js:46:5)
    at async file:///home/mover/lekondo-cotton/node_modules/@opennextjs/aws/dist/index.js:9:1 {
  errno: -2,
  syscall: 'copyfile',
  code: 'ENOENT',
  path: '/home/mover/lekondo-cotton/.next/standalone/.next/server/app/(central)/page_client-reference-manifest.js',
  dest: '/home/mover/lekondo-cotton/.open-next/server-functions/default/.next/server/app/(central)/page_client-reference-manifest.js'
}

Node.js v18.18.0

next.config.mjs:
import { withSentryConfig } from '@sentry/nextjs';

/** @type {import('next').NextConfig} */
const nextConfig = {
  images: {
    remotePatterns: [
      {
        protocol: 'https',
        hostname: '**',
      },
      {
        protocol: 'http',
        hostname: '**',
      },
    ],
  },
};

// eslint-disable-next-line import/no-default-export
export default withSentryConfig(nextConfig, {
 // Sentry stuff
});

sst.config.ts:
// eslint-disable-next-line @typescript-eslint/triple-slash-reference
/// <reference path="./.sst/platform/config.d.ts" />
export default $config({
  app(input) {
    return {
      name: 'lekondo-cotton',
      removal: input?.stage === 'prod' ? 'retain' : 'remove',
      home: 'aws',
      region: 'us-east-1',
      providers: {
        cloudflare: {
          version: '5.41.0',
          apiToken: process.env.CLOUDFLARE_API_TOKEN,
        },
      },
    };
  },
  async run() {
    new sst.aws.Nextjs('Lekondo', {
      domain: {
        name: process.env.DOMAIN,
        dns: sst.cloudflare.dns({
          zone: '123',
          override: true,
        }),
      },
      openNextVersion: '3.2.1',
      environment: {
        NEXT_PUBLIC_API_URL: process.env.NEXT_PUBLIC_API_URL ?? '',
        BASE_URL: process.env.BASE_URL ?? '',
        AUTH0_SECRET: process.env.AUTH0_SECRET ?? '',
        AUTH0_BASE_URL: process.env.AUTH0_BASE_URL ?? '',
        AUTH0_ISSUER_BASE_URL: process.env.AUTH0_ISSUER_BASE_URL ?? '',
        AUTH0_CLIENT_ID: process.env.AUTH0_CLIENT_ID ?? '',
        AUTH0_CLIENT_SECRET: process.env.AUTH0_CLIENT_SECRET ?? '',
        AUTH0_AUDIENCE: process.env.AUTH0_AUDIENCE ?? '',
      },
    });
  },
});

Failed to copy traced files for /home/mover/lekondo-cotton/.next/server/app/(central)/page.js [Error: ENOENT: no such file or directory, copyfile '/home/mover/lekondo-cotton/.next/server/app/(central)/page_client-reference-manifest.js' -> '/home/mover/lekondo-cotton/.next/standalone/.next/server/app/(central)/page_client-reference-manifest.js']

This error indicates that something went wrong with next build itself, and since that's used by OpenNext to compute the server functions it explains the fail. You could try removing the .next folder

When you move folders/filers around in next, you usually need to do a clean wipe of .next. There are some weird reference caching that can cause build issues.

@conico974 @khuezy next build goes off with out a hitch. I have cleared .next, .sst, etc. This also fails in my Github actions (that dont have a cache). But these are local logs currently.
 y build
Found '/home/mover/lekondo-cotton/.nvmrc' with version <18.18.0>
Now using node v18.18.0 (npm v9.8.1)
yarn run v1.22.19
$ next build
  ▲ Next.js 14.2.13
  - Environments: .env.local
  - Experiments (use with caution):
    · instrumentationHook

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ✓ Collecting page data
 ✓ Generating static pages (18/18)
   Finalizing page optimization  .   Collecting build trace
 ✓ Collecting build traces
 ✓ Finalizing page optimization

Route (app)                                        Size     First Load JS
┌ ƒ /                                              3.58 kB         249 kB
├ ○ /_not-found                                    1.03 kB         184 kB
├ ƒ /api/auth/[auth0]                              0 B                0 B
├ ƒ /api/auth/dev/dangerouslyGetAPIToken           0 B                0 B
├ ƒ /collection                                    1.15 kB         189 kB
├ ƒ /collection/[collectionId]                     8.8 kB          271 kB
├ ƒ /collection/[collectionId]/item/[itemId]       3.33 kB         228 kB
├ ƒ /collection/[collectionId]/item/[itemId]/edit  413 B           225 kB
├ ○ /dev                                           1.48 kB         189 kB
├ ƒ /discovery                                     322 B           183 kB
├ ƒ /manifesto                                     323 B           183 kB
├ ○ /onboarding/assignment1                        2.56 kB         221 kB
├ ○ /onboarding/assignment2                        2.7 kB          236 kB
├ ○ /onboarding/assignment3                        2.45 kB         263 kB
├ ○ /onboarding/assignment4                        3.53 kB         229 kB
├ ○ /onboarding/welcome                            673 B           191 kB
├ ƒ /settings                                      322 B           183 kB
├ ƒ /settings/privacy                              1.57 kB         197 kB
├ ƒ /settings/profile                              1.66 kB         213 kB
└ ƒ /symposium/[tag]                               5.95 kB         224 kB
+ First Load JS shared by all                      183 kB
  ├ chunks/52774a7f-acd6185c7912d037.js            36.1 kB
  ├ chunks/5347-99e5327102b28534.js                90.4 kB
  ├ chunks/fd9d1056-7ab42e1942c648c4.js            53.8 kB
  └ other shared chunks (total)                    2.54 kB

ƒ Middleware                                       160 kB

○  (Static)   prerendered as static content
ƒ  (Dynamic)  server-rendered on demand

Done in 75.21s.

You're not running next build with ouput standalone, which is what OpenNext do and need.
This part is failing, the error i showed you is not originating from OpenNext, but from Next itself

Is this standalone output? I don't have next globally installed or anything:
./node_modules/.bin/next build
  ▲ Next.js 14.2.13
  - Environments: .env.local
  - Experiments (use with caution):
    · instrumentationHook

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ✓ Collecting page data
 ✓ Generating static pages (18/18)
   Finalizing page optimization  .   Collecting build trace
 ✓ Collecting build traces
 ✓ Finalizing page optimization

Route (app)                                        Size     First Load JS
┌ ƒ /                                              3.58 kB         249 kB
├ ○ /_not-found                                    1.03 kB         184 kB
├ ƒ /api/auth/[auth0]                              0 B                0 B
├ ƒ /api/auth/dev/dangerouslyGetAPIToken           0 B                0 B
├ ƒ /collection                                    1.15 kB         189 kB
├ ƒ /collection/[collectionId]                     8.8 kB          271 kB
├ ƒ /collection/[collectionId]/item/[itemId]       3.33 kB         228 kB
├ ƒ /collection/[collectionId]/item/[itemId]/edit  413 B           225 kB
├ ○ /dev                                           1.48 kB         189 kB
├ ƒ /discovery                                     322 B           183 kB
├ ƒ /manifesto                                     323 B           183 kB
├ ○ /onboarding/assignment1                        2.56 kB         221 kB
├ ○ /onboarding/assignment2                        2.7 kB          236 kB
├ ○ /onboarding/assignment3                        2.45 kB         263 kB
├ ○ /onboarding/assignment4                        3.53 kB         229 kB
├ ○ /onboarding/welcome                            673 B           191 kB
├ ƒ /settings                                      322 B           183 kB
├ ƒ /settings/privacy                              1.57 kB         197 kB
├ ƒ /settings/profile                              1.66 kB         213 kB
└ ƒ /symposium/[tag]                               5.95 kB         224 kB
+ First Load JS shared by all                      183 kB
  ├ chunks/52774a7f-acd6185c7912d037.js            36.1 kB
  ├ chunks/5347-99e5327102b28534.js                90.4 kB
  ├ chunks/fd9d1056-7ab42e1942c648c4.js            53.8 kB
  └ other shared chunks (total)                    2.53 kB

ƒ Middleware                                       160 kB

○  (Static)   prerendered as static content
ƒ  (Dynamic)  server-rendered on demand

Looks to me like the error originates from the OpenNext — Generating bundle, after the build is successful. Is there a way for me to run this step via next directly?

The first error which is the exact same btw is originating from next build

To run in standalone https://nextjs.org/docs/app/api-reference/next-config-js/output#automatically-copying-traced-files

Nice, same error in standalone mode. I'll open an issue with Next directly, thanks!

Can you try upgrading your next version? I'm using groups too and haven't had issues building/copying groups.


Is a issues？

When ues  [customField becomeFirstResponder] then textfield is covered by the keyboard(iphone 5s). I hope  customField can be first responder when it show, and how? ths.

Hi @noname004. Thanks for using FCAlertView! Can you please paste the code you're using to generate the custom Field and showing it? Thanks!


Refactor and rename sandboxing implementation

The sandboxing code inside the client which is responsible for running the contracts of pallet-contracts needs a refactor. Currently, the different execution engines for contracts are crammed into sc-executor-common. Neither should different execution engines be in the same crate nor should runtime execution and sandbox execution be intertwined in this way. For that reason we want to refactor that code in order to have proper abstractions that allows us to move the sandboxing code to its own set of crates.
Rename
After a discussion with @pepyakin (see comments below) we agreed that we should also move away from the term "sandboxing" for this whole thing. One proposal what I also back is to use the terminology "Wasm Virtualization".
TODO

[x] #10563
[ ] Create a trait to abstract over sandboxing execution engines ("backends").
[ ] Use dynamic dispatch with that trait to make engine selection possible at runtime (command line argument).
[ ] Move sandboxing code into its own crate client/wasm-virt with one additional crate per execution engine (sc-wasm-virt-wasmi, sc-wasm-virt-wasmer). This should also move all wasm virtualization related traits that needs to be implement by the runtime executor to the new location.

Another open question is whether we need to expand the API to allow for chunked execution so that code merkelization can be implemented. However, current thinking is that we can and should get away without execution engine support. I think it is reasonable to go forward with a non chunked version risking that we might need to maintain two APIs. Otherwise this is blocked by #9431.

I think, by carefully designing the API we can future-proof it to support potential chunked execution similar to what we have done for wasmi during our experiment.

Maybe. It adds complexity, though. For example, we would need some kind of feature discovery then because not all execution engines will support this right off the bat. As a matter of fact none will support it as we only put it in for future proofing. Just creating a new version of the API when the need arises is better in my opinion. Future proofing APIs is worth nothing when users will depend on the implementation.

Excerpt from our discussion about changing the terminology from sandoxing to a term based on virtualization, e.g. wasm virtualization API, hypervisor API, or whatever.

Specifically, I think it is just too general and does not represent what it actually does. What is usually understood by sandbox? Well, it's when some code is put into an environment where it cannot reach to anything except things that was explicitly designated to be used by that sandboxed code.
If we agree on that definition, then the "runtime" is exactly that. The thing that executes "runtime" (which would be called runtime by normal people) can be also called a sandbox.
However, virtualization is really more appropriate term here I feel. This is because it fits really an analogy. Virtualization is where you have some medium that provides virtualization facilities, some hypervisor/supervisor that virtualizes or multiplexes the underlying hardware, emulating other and providing services, and the guest which consumes those services, who uses the hardware through the hypervisor, and ultimately is controlled by the hypervisor

Updated the top post with new information after a discussion I had with @0x7CFE, today.

Refined the top posting again after the picture got a bit clearer on how the final refactoring should look like.

I narrowed down the scope if this issue and created a a proper task list.

What exactly do you *need it for?

run a piece of wasm in runtime

You can still do that: Use sp_sandbox::embedded_executor. It doesn't rely on this interface but includes a wasmi into the runtime.

No one is working on this anymore.

Since we decided to go with wasmi for now and we don't really have the resources to work on that we will close it.


Make sure the client id is not a blank string

Otherwise it becomes a different request to API, GET /oauth/clients/ which returns a list of clients to Identity.
Ready for review @heroku/api

:+1:

@mikehale Thanks!


Missing Weapons

I cant see STG44 or any other guns?

STG44, Torque 35, Spear and Static-HV have been added in #95!


add an AUTOMATED bool flag to help us know what repos need new ci/cd

considering https://www.docker.com/blog/changes-to-docker-hub-autobuilds/, I wanted to see just how many repos I have to redo

I just used what is in the API, zero opinion. If you want to change it to
merge, go for it :)
On Wed, 9 Jun 2021, 6:16 pm Silvin Lubecki, @.***>
wrote:

@.**** commented on this pull request.
In internal/commands/repo/list.go
https://github.com/docker/hub-tool/pull/179#discussion_r648074803:

@@ -62,6 +62,10 @@ var (
s := fmt.Sprintf("%v", r.IsPrivate)
return s, len(s)
}},

{"AUTOMATED", func(r hub.Repository) (string, int) {

nit: What about "AUTOBUILD" ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/hub-tool/pull/179#pullrequestreview-679348448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAG6TFH26L3G5QM6XOTJLDTR4PPDANCNFSM46K7UJFQ
.


@grammy/conversations v1.1.1 session parse error

Reprocude:
import { Bot, session } from "grammy"
import { conversations, createConversation } from '@grammyjs/conversations'
const token = 'XXXXXXXXXXXXXXXXXXXXXXX'
const bot = new Bot(token)
function initial() {
return { }
}
bot.use(session({ initial }))
bot.use(conversations())
let c = async function (conversation, ctx) {
await ctx.reply("Some message");
const { message } = await conversation.waitFrom(ctx.from)
console.log(message)
}
bot.use(createConversation(c))
bot.on('message', ctx => {
ctx.conversation.enter('c')
})
bot.start()
After any message to bot i've got:
/data/____/node_modules/@grammyjs/conversations/out/conversation.js:357
if (session.conversation[id].length === 0) {
^
TypeError: Cannot read properties of undefined (reading 'length')
at ctx.conversation.enter (/data/____/node_modules/@grammyjs/conversations/out/conversation.js:357:46)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
OS: Ubuntu 22.04 LTS
NodeJS: 19.7.0
Grammy: 1.15.2
@grammy/conversations v1.0.3 - have not that issue.

Yep... forgot await, sorry.
False issue. Close please.

You're not the first one to forget this. I'll think about how to detect and prevent such mistakes library-side. Glad it's fixed!


Installation: Tell user to create package.json file if does not exist

When you follow just the README.md content in an empty folder, this happens:
C:\Users\Jan\Documents\throwaway\prismaReadme
λ npm install @prisma/client

><EMAIL_ADDRESS>postinstall C:\Users\Jan\Documents\node_modules\@prisma\client
> node scripts/postinstall.js

warning In order to use "@prisma/client", please install @prisma/cli. You can install it with "npm add -D @prisma/cli".
npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\Jan\Documents\package.json'
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\Jan\Documents\package.json'
npm WARN Documents No description
npm WARN Documents No repository field.
npm WARN Documents No README data
npm WARN Documents No license field.

+<EMAIL_ADDRESS>added 1 package and audited 1 package in 7.734s
found 0 vulnerabilities

C:\Users\Jan\Documents\throwaway\prismaReadme
λ ls

Running the command from the warning has the same effect:
C:\Users\Jan\Documents\throwaway\prismaReadme
λ npm add -D @prisma/cli

><EMAIL_ADDRESS>preinstall C:\Users\Jan\Documents\node_modules\@prisma\cli
> node preinstall/index.js

><EMAIL_ADDRESS>install C:\Users\Jan\Documents\node_modules\@prisma\cli
> node download-build/index.js

npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\Jan\Documents\package.json'
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\Jan\Documents\package.json'
npm WARN Documents No description
npm WARN Documents No repository field.
npm WARN Documents No README data
npm WARN Documents No license field.

+<EMAIL_ADDRESS>added 1 package from 1 contributor and audited 2 packages in 28.605s
found 0 vulnerabilities

C:\Users\Jan\Documents\throwaway\prismaReadme
λ ls

Only after you create a package.json you actually can install the CLI and later Client:
C:\Users\Jan\Documents\throwaway\prismaReadme
λ npm init -y
Wrote to C:\Users\Jan\Documents\throwaway\prismaReadme\package.json:

{
  "name": "prismaReadme",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

C:\Users\Jan\Documents\throwaway\prismaReadme<EMAIL_ADDRESS>λ npm add -D @prisma/cli

><EMAIL_ADDRESS>preinstall C:\Users\Jan\Documents\throwaway\prismaReadme\node_modules\@prisma\cli
> node preinstall/index.js

><EMAIL_ADDRESS>install C:\Users\Jan\Documents\throwaway\prismaReadme\node_modules\@prisma\cli
> node download-build/index.js

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 1 package from 1 contributor and audited 1 package in 24.448s
found 0 vulnerabilities

C:\Users\Jan\Documents\throwaway\prismaReadme<EMAIL_ADDRESS>λ ls
node_modules/  package.json  package-lock.json

Similar to the warning in @prisma/client that it needs the CLI, we could output a message that the installation of the CLI requires an existing package.json file. It could look like this:
warning In order to install "@prisma/cli", please create a package.json file. You can create it with "npm init -y".

I get the same warnings you did but my directory was not empty after npm install @prisma/client. Output of ls is
node_modules            package-lock.json

Likewise after running npm add -D @prisma/cli, inside node_modules/@prisma are both cli and client folders.
  ~/Desktop/throw 
   npm add -D @prisma/cli
><EMAIL_ADDRESS>preinstall /Users/fawyna/Desktop/throw/node_modules/@prisma/cli
> node preinstall/index.js

><EMAIL_ADDRESS>install /Users/fawyna/Desktop/throw/node_modules/@prisma/cli
> node download-build/index.js

npm WARN saveError ENOENT: no such file or directory, open '/Users/fawyna/Desktop/throw/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/Users/fawyna/Desktop/throw/package.json'
npm WARN throw No description
npm WARN throw No repository field.
npm WARN throw No README data
npm WARN throw No license field.

+<EMAIL_ADDRESS>added 1 package from 1 contributor and audited 2 packages in 7.487s
found 0 vulnerabilities

  ~/Desktop/throw 
   ls
node_modules            package-lock.json

I tried on both Mac OSX (Node v12.13.0) and Windows (v10.15.2) with the same results. Its probably good practice to have a package.json file anyway, so perhaps there should still be a warning?

Hi! I'm one of the program coordinators of a nonprofit program called CodeDay Init, and we partner with colleges to help CS students make their first open-source contribution.
We'll claim this issue for now and a group of students will be on it soon with mentorship! If this issue is no longer relevant, please let me know.

hey @itsmingjie ! Glad to have you here and happy to help students contribute. This issue may no longer be relevant, let me have a look and let you know soon.

Sorry, the "good first issue" should have definitely been removed with the answer from @abuuzayr because it is now unclear a) what the state is and b) what could be done to improve it. Might just be closed in the end.