144hz monitor support for smoothly experience

It would be nice to have support above 60hz. Now all apps in WSLG are very choppy on 144hz/240hz monitors.
Right now WSLG max Hz is 60
You can check the refreshrate here: https://www.testufo.com/refreshrate
WSLG:

Windows 10:

/mnt/wslg/weston.log
Date: 2021-04-29 MSK
[23:11:20.148] weston 9.0.0
               https://wayland.freedesktop.org
               Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
               Build: 9.0.0-256-gfd961f5c
[23:11:20.148] Command line: /usr/bin/weston --backend=rdp-backend.so --xwayland --shell=rdprail-shell.so --logger-scopes=log,rdp-backend,rdprail-shell --log=/mnt/wslg/weston.log
[23:11:20.148] OS: Linux, <IP_ADDRESS>-microsoft-standard-WSL2, #1 SMP Fri Apr 2 22:23:49 UTC 2021, x86_64
[23:11:20.148] Using config file '/home/wslg/.config/weston.ini'
[23:11:20.148] Output repaint window is 7 ms maximum.
[23:11:20.148] Loading module '/usr/lib/libweston-9/rdp-backend.so'
[23:11:20.151] using FreeRDP version 2.2.0
[23:11:20.151] RDP backend: WESTON_RDP_DEBUG_LEVEL: 3.
[23:11:20.151] RDP backend: Environment dump - start
[23:11:20.151]   WSL_DISTRO_NAME=
[23:11:20.151]   WSL2_SHARED_MEMORY_OB_DIRECTORY=WSL\5B227B4D-64E1-43D2-B427-65DAD579A444\wslg
[23:11:20.151]   PWD=/
[23:11:20.151]   NAME=DESKTOP-8IA18VK
[23:11:20.151]   WSL_FEATURE_FLAGS=7
[23:11:20.151]   SHLVL=1
[23:11:20.151]   WSL2_GUI_APPS_ENABLED=1
[23:11:20.151]   WSL2_DISTRO_NAME=Ubuntu
[23:11:20.151]   WSL2_VM_ID=5B227B4D-64E1-43D2-B427-65DAD579A444
[23:11:20.151]   _=/usr/bin/WSLGd
[23:11:20.151]   HOME=/home/wslg
[23:11:20.151]   USER=wslg
[23:11:20.151]   LOGNAME=wslg
[23:11:20.151]   SHELL=/bin/bash
[23:11:20.151]   PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
[23:11:20.151]   XDG_RUNTIME_DIR=/mnt/wslg/runtime-dir
[23:11:20.151]   WAYLAND_DISPLAY=wayland-0
[23:11:20.151]   DISPLAY=:0
[23:11:20.151]   XCURSOR_PATH=/usr/share/icons
[23:11:20.151]   XCURSOR_THEME=whiteglass
[23:11:20.151]   XCURSOR_SIZE=16
[23:11:20.151]   PULSE_AUDIO_RDP_SINK=/mnt/wslg/PulseAudioRDPSink
[23:11:20.151]   PULSE_AUDIO_RDP_SOURCE=/mnt/wslg/PulseAudioRDPSource
[23:11:20.151]   USE_VSOCK=3
[23:11:20.151]   WSL2_DEFAULT_APP_ICON=/usr/share/icons/wsl/linux.png
[23:11:20.151]   WSL2_DEFAULT_APP_OVERLAY_ICON=/usr/share/icons/wsl/linux.png
[23:11:20.151]   WESTON_DISABLE_ABSTRACT_FD=1
[23:11:20.151]   WSL2_SHARED_MEMORY_MOUNT_POINT=/mnt/shared_memory
[23:11:20.151]   WESTON_CONFIG_FILE=/home/wslg/.config/weston.ini
[23:11:20.151] RDP backend: Environment dump - end
[23:11:20.151] Using external fd for incoming connections: 3
[23:11:20.151] Default head is being added
[23:11:20.151] Registered plugin API 'weston_rdprail_api_v1' of size 48
[23:11:20.156] RDP backend: use_gfxredir = 1
[23:11:20.156] RDP backend: enable_hi_dpi_support = 1
[23:11:20.156] RDP backend: enable_fractional_hi_dpi_support = 0
[23:11:20.156] RDP backend: debug_desktop_scaling_factor = 0
[23:11:20.156] RDP backend: enable_distro_name_title = 1
[23:11:20.156] RDP backend: enable_copy_warning_title = 0
[23:11:20.156] Using VSOCK for incoming connections: 3
[23:11:20.156] Registered plugin API 'weston_rdp_output_api_v1' of size 16
[23:11:20.156] Head attaching: rdp-0, index:0, is_primary: 1
[23:11:20.156] get_config: attached head [0]: make:(null), mode:(null), name:rdp-0, (0x55997a712110)
[23:11:20.156] get_config: attached head [0]: x:0, y:0, width:0, height:0
[23:11:20.156] set_size: attached head [0]: make:weston, mode:rdp, name:rdp-0, (0x55997a712110)
[23:11:20.156] set_size: attached head [0]: x:0, y:0, width:0, height:0
[23:11:20.156] Output 'rdp-0' enabled with head(s) rdp-0
[23:11:20.156] Compositor capabilities:
               arbitrary surface rotation: yes
               screen capture uses y-flip: no
               presentation clock: CLOCK_MONOTONIC_RAW, id 4
               presentation clock resolution: 0.000000001 s
[23:11:20.156] Loading module '/usr/lib/weston/rdprail-shell.so'
[23:11:20.157] RDPRAIL-shell: WESTON_RDPRAIL_SHELL_DEBUG_LEVEL: 3.
[23:11:20.157] wet_shell_init: distro name Ubuntu (6)
[23:11:20.157] rdp_rail_shell_initialize_notify: shell: distro name: Ubuntu
[23:11:20.158] app_list_monitor_thread: running in system-distro with user-distro: Ubuntu
[23:11:20.158] app_list_monitor_thread: open(/proc/self/ns/mnt)
[23:11:20.158] Loading module '/usr/lib/libweston-9/xwayland.so'
[23:11:20.158] app_list_monitor_thread: open(/proc/2/ns/mnt)
[23:11:20.160] app_list_monitor_thread: inotify_add_watch(/usr/share/applications)
[23:11:20.160] Registered plugin API 'weston_xwayland_v1' of size 32
[23:11:20.163] Registered plugin API 'weston_xwayland_surface_v1' of size 48
[23:11:20.163] Not using abstract fd for Xwayland
[23:11:20.163] xserver listening on display :0
[23:11:20.165] app_list_monitor_thread: /usr/local/share/applications doesn't exist, skipping.
[23:11:20.165] app list folder[0]: /usr/share/applications
[23:11:20.166] desktop file: /usr/share/applications/snap-handle-link.desktop has NoDisplay specified
[23:11:20.166] app list entry failed to update: Key:snap-handle-link
[23:11:20.166] free_app_entry(): (null): /usr/share/applications/snap-handle-link.desktop
[23:11:20.167] desktop file: /usr/share/applications/byobu.desktop is terminal based app
[23:11:20.167] app list entry failed to update: Key:byobu
[23:11:20.167] free_app_entry(): (null): /usr/share/applications/byobu.desktop
[23:11:20.168] desktop file: /usr/share/applications/vim.desktop is terminal based app
[23:11:20.168] app list entry failed to update: Key:vim
[23:11:20.168] free_app_entry(): (null): /usr/share/applications/vim.desktop
[23:11:20.168] desktop file: /usr/share/applications/htop.desktop is terminal based app
[23:11:20.168] app list entry failed to update: Key:htop
[23:11:20.168] free_app_entry(): (null): /usr/share/applications/htop.desktop
[23:11:20.169] desktop file: /usr/share/applications/info.desktop is terminal based app
[23:11:20.169] app list entry failed to update: Key:info
[23:11:20.169] free_app_entry(): (null): /usr/share/applications/info.desktop
[23:11:20.170] desktop file: /usr/share/applications/python3.8.desktop has NoDisplay specified
[23:11:20.170] app list entry failed to update: Key:python3.8
[23:11:20.170] free_app_entry(): (null): /usr/share/applications/python3.8.desktop
[23:11:20.170] app list folder[1]: /usr/local/share/applications
[23:11:20.989] Client: ClientStatus:0x3f5
[23:11:20.989]      - TS_RAIL_CLIENTSTATUS_ALLOWLOCALMOVESIZE
[23:11:20.989]      - TS_RAIL_CLIENTSTATUS_ZORDER_SYNC
[23:11:20.989]      - TS_RAIL_CLIENTSTATUS_WINDOW_RESIZE_MARGIN_SUPPORTED
[23:11:20.989]      - TS_RAIL_CLIENTSTATUS_HIGH_DPI_ICONS_SUPPORTED
[23:11:20.989]      - TS_RAIL_CLIENTSTATUS_APPBAR_REMOTING_SUPPORTED
[23:11:20.989]      - TS_RAIL_CLIENTSTATUS_POWER_DISPLAY_REQUEST_SUPPORTED
[23:11:20.989]      - TS_RAIL_CLIENTSTATUS_GET_APPID_RESPONSE_EX_SUPPORTED
[23:11:20.989]      - TS_RAIL_CLIENTSTATUS_BIDIRECTIONAL_CLOAK_SUPPORTED
[23:11:20.989] Client HandShake buildNumber:21370
[23:11:21.042] Server AppList caps version:3
[23:11:21.062] Client: gfxredir_caps: length:28
[23:11:21.062] Client: gfxredir_caps[0]: signature:0x53504143
[23:11:21.062] Client: gfxredir_caps[0]: version:0x1
[23:11:21.062] Client: gfxredir_caps[0]: length:12
[23:11:21.062] Client: gfxredir_caps[1]: signature:0x53504143
[23:11:21.062] Client: gfxredir_caps[1]: version:0x2000
[23:11:21.062] Client: gfxredir_caps[1]: length:16
[23:11:21.062] Client: gfxredir_caps[1]: supportedFeatures:0x0
[23:11:21.062] Client: GrfxCaps count:0x8
[23:11:21.062] Client: GrfxCaps[0] version:0x80004 length:4 flags:0x0
[23:11:21.062]  Version : RDPGFX_CAPVERSION_8
[23:11:21.062] Client: GrfxCaps[1] version:0x80105 length:4 flags:0x0
[23:11:21.062]  Version : RDPGFX_CAPVERSION_81
[23:11:21.062] Client: gfxredir selected caps: version:0x2000
[23:11:21.062] Client: GrfxCaps[2] version:0xa0002 length:4 flags:0x0
[23:11:21.062]  Version : RDPGFX_CAPVERSION_10
[23:11:21.062] Client: GrfxCaps[3] version:0xa0200 length:4 flags:0x0
[23:11:21.062]  Version : RDPGFX_CAPVERSION_102
[23:11:21.062] Client: GrfxCaps[4] version:0xa0301 length:4 flags:0x0
[23:11:21.062]  Version : RDPGFX_CAPVERSION_103
[23:11:21.062] Client: GrfxCaps[5] version:0xa0400 length:4 flags:0x0
[23:11:21.062]  Version : RDPGFX_CAPVERSION_104
[23:11:21.062] Client: GrfxCaps[6] version:0xa0502 length:4 flags:0x0
[23:11:21.062]  Version : RDPGFX_CAPVERSION_105
[23:11:21.062] Client: GrfxCaps[7] version:0xa0600 length:4 flags:0x0
[23:11:21.062]  Version : RDPGFX_CAPVERSION_106
[23:11:21.072] Pulse Audio source listener socket on /mnt/wslg/PulseAudioRDPSource
[23:11:21.072] xf_peer_adjust_monitor_layout:
[23:11:21.072]   DesktopWidth:2560, DesktopHeight:1440
[23:11:21.072]   UseMultimon:0
[23:11:21.072]   ForceMultimon:0
[23:11:21.072]   MonitorCount:0
[23:11:21.072]   HasMonitorAttributes:0
[23:11:21.072]   HiDefRemoteApp:1
[23:11:21.072] disp_monitor_validate_and_compute_layout:---INPUT---
[23:11:21.072] AudioIn source_thread: Listening for audio in connection.
[23:11:21.072]  rdpMonitor[0]: x:0, y:0, width:2560, height:1440, is_primary:1
[23:11:21.072]  rdpMonitor[0]: physicalWidth:597, physicalHeight:336, orientation:0
[23:11:21.072]  rdpMonitor[0]: desktopScaleFactor:100, deviceScaleFactor:100
[23:11:21.072]  rdpMonitor[0]: scale:1, client scale :1.00
[23:11:21.072] Client desktop upper left coordinate (0,0)
[23:11:21.072] disp_monitor_validate_and_compute_layout:---OUTPUT---
[23:11:21.072]  rdpMonitor[0]: x:0, y:0, width:2560, height:1440, is_primary:1
[23:11:21.072]  rdpMonitor[0]: weston x:0, y:0, width:2560, height:1440
[23:11:21.072]  rdpMonitor[0]: physicalWidth:597, physicalHeight:336, orientation:0
[23:11:21.072]  rdpMonitor[0]: desktopScaleFactor:100, deviceScaleFactor:100
[23:11:21.073]  rdpMonitor[0]: scale:1, clientScale:1.00
[23:11:21.073] Head mode change:rdp-0 OLD width:0, height:0, scale:1, clientScale:1.000000
[23:11:21.073] Head mode change:rdp-0 NEW width:2560, height:1440, scale:1, clientScale:1.000000
[23:11:21.073] move head/output rdp-0 (0,0) -> (0,0)
[23:11:21.073] client origin (0,0) is (0,0) in Weston space
[23:11:21.073] client virtual desktop is (0,0) - (2560,1440)
[23:11:21.073] weston virtual desktop is (0,0) - (2560,1440)
[23:11:21.073] kbd_layout:0x409 kbd_type:0x4 kbd_subType:0x0 kbd_functionKeys:0xc
[23:11:21.073] convert_rdp_keyboard_to_xkb_rule_names: matching layout=us variant=(null)
[23:11:21.075] Client ExecOrder:0x00000008, Program:dummy-entry, WorkingDir:(null), RemoteApplicationArguments:(null)
[23:11:21.075] Client ExecOrder launching dummy-entry
[23:11:21.075] launching 'dummy-entry'
[23:11:21.076] Client: ClientSysparam: filterKeys
[23:11:21.076] Client: ClientSysparam: toggleKeys:62
[23:11:21.076] Client: ClientSysparam: stickyKeys:510
[23:11:21.076] Client: ClientSysparam: caretWidth:1
[23:11:21.076] Client: ClientSysparam: highContrast
[23:11:21.076] Client: ClientSysparam: taskbarPos:(left:0, top:1400, right:2560, bottom:1440)
[23:11:21.076] Client: ClientSysparam: mouseButtonSwap:0
[23:11:21.076] Client: ClientSysparam: keyboardPref:0
[23:11:21.076] Client: ClientSysparam: dragFullWindows:1
[23:11:21.076] Client: ClientSysparam: keyboardCues:0
[23:11:21.076] Client: ClientSysparam: workArea:(left:0, top:0, right:2560, bottom:1400)
[23:11:21.076] Client AppList caps version:3
[23:11:21.076] compositor: executing 'dummy-entry' failed: No such file or directory
[23:11:21.076] Client AppList client language id: en_US
[23:11:21.076] Detected a monitor change on head 'rdp-0', not bothering to do anything about it.
[23:11:21.076] app_list_monitor_thread: startRdpNotifyEvent is signalled. 0 - en_US
[23:11:21.076] Client: ClientSysparam: filterKeys
[23:11:21.076] Client: ClientSysparam: toggleKeys:62
[23:11:21.076] Client: ClientSysparam: stickyKeys:510
[23:11:21.076] Client: ClientSysparam: caretWidth:1
[23:11:21.076] Client: ClientSysparam: highContrast
[23:11:21.076] Client: ClientSysparam: taskbarPos:(left:0, top:1400, right:2560, bottom:1440)
[23:11:21.076] Client: ClientSysparam: mouseButtonSwap:0
[23:11:21.076] Client: ClientSysparam: keyboardPref:0
[23:11:21.076] Client: ClientSysparam: dragFullWindows:1
[23:11:21.076] Client: ClientSysparam: keyboardCues:0
[23:11:21.076] Client: ClientSysparam: workArea:(left:0, top:0, right:2560, bottom:1400)
[23:11:21.076] Client ExecOrder program terminated
[23:11:21.076] dummy-entry exited with status 255
[23:11:21.079] rdp_audio_server_activated: 1 audio formats supported.
[23:11:21.079]  [0] - Format(WAVE_FORMAT_PCM) - Bits(16), Channels(2), Frequency(44100)
[23:11:21.079] RDPAudio - Agreed on format 0.
[23:11:21.079] rdp_audio_server_activated: bytesPerFrame:4, latency:5
[23:11:21.079] Pulse Audio Sink listener socket on /mnt/wslg/PulseAudioRDPSink
[23:11:21.079] Audio sink thread: Listening for audio connection.
[23:11:21.079] Client: clipboard capabilities: cCapabilitiesSet:1
[23:11:21.079] Client: clipboard capabilities[0]: General
[23:11:21.079]     Version:2
[23:11:21.079]     GeneralFlags:0x10
[23:11:21.079]         CB_CAN_LOCK_CLIPDATA
[23:11:21.079] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:11:21.079] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:11:21.079] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:11:21.079] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:11:21.079] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:11:21.079] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:11:21.079] Client: clipboard_client_format_list (0x7f4684000d80) allocated
[23:11:21.079] Client: clipboard_client_format_list (0x7f4684000d80) mine_type:"text/html"
[23:11:21.079] Client: clipboard_client_format_list (0x7f4684000d80) mine_type:"text/plain;charset=utf-8"
[23:11:21.079] RDP clipboard_data_source_publish (0x7f4684000d80)
[23:11:21.079] RDP clipboard_data_source_send (0x7f4684000d80) fd:88, mime-type:"text/html"
[23:11:21.079] RDP clipboard_data_source_send (0x7f4684000d80) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:11:21.079] RDP clipboard_set_selection (base:0x7f4684000d80}
[23:11:21.082] Client: clipboard_client_format_data_response (0x7f4684000d80) flags:1, dataLen:1224
[23:11:21.082] RDP clipboard_data_source_write (0x7f4684000d80) write completed (1073 bytes)
[23:11:21.082] RDP clipboard_data_source_unref (0x7f4684000d80): refcount:1
[23:11:25.171] Audio sink thread: connection successful on socket (86).
[23:11:25.171] RDP Sink version (1 - 1)
[23:11:25.696] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:11:25.696] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:11:25.696] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:11:25.696] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:11:25.696] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:11:25.696] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:11:25.696] Client: clipboard_client_format_list (0x7f4684000e50) allocated
[23:11:25.696] Client: clipboard_client_format_list (0x7f4684000e50) mine_type:"text/html"
[23:11:25.696] Client: clipboard_client_format_list (0x7f4684000e50) mine_type:"text/plain;charset=utf-8"
[23:11:25.696] RDP clipboard_data_source_publish (0x7f4684000e50)
[23:11:25.696] RDP clipboard_data_source_cancel (0x7f4684000d80)
[23:11:25.696] RDP clipboard_data_source_send (0x7f4684000e50) fd:88, mime-type:"text/html"
[23:11:25.696] RDP clipboard_data_source_send (0x7f4684000e50) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:11:25.696] RDP clipboard_set_selection (base:0x7f4684000e50}
[23:11:25.696] RDP clipboard_data_source_unref (0x7f4684000d80): refcount:0
[23:11:25.699] Client: clipboard_client_format_data_response (0x7f4684000e50) flags:2, dataLen:0
[23:11:25.699] RDP clipboard_data_source_unref (0x7f4684000e50): refcount:1
[23:11:34.421] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:11:34.421] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:11:34.421] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:11:34.421] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:11:34.421] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:11:34.421] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:11:34.421] Client: clipboard_client_format_list (0x7f4684000f40) allocated
[23:11:34.421] Client: clipboard_client_format_list (0x7f4684000f40) mine_type:"text/html"
[23:11:34.421] Client: clipboard_client_format_list (0x7f4684000f40) mine_type:"text/plain;charset=utf-8"
[23:11:34.421] RDP clipboard_data_source_publish (0x7f4684000f40)
[23:11:34.421] RDP clipboard_data_source_cancel (0x7f4684000e50)
[23:11:34.421] RDP clipboard_data_source_send (0x7f4684000f40) fd:88, mime-type:"text/html"
[23:11:34.421] RDP clipboard_data_source_send (0x7f4684000f40) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:11:34.421] RDP clipboard_set_selection (base:0x7f4684000f40}
[23:11:34.421] RDP clipboard_data_source_unref (0x7f4684000e50): refcount:0
[23:11:34.422] Client: clipboard_client_format_data_response (0x7f4684000f40) flags:2, dataLen:0
[23:11:34.422] RDP clipboard_data_source_unref (0x7f4684000f40): refcount:1
[23:15:25.854] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:15:25.854] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:15:25.854] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:15:25.854] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:15:25.854] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:15:25.854] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:15:25.854] Client: clipboard_client_format_list (0x7f4684000e50) allocated
[23:15:25.854] Client: clipboard_client_format_list (0x7f4684000e50) mine_type:"text/html"
[23:15:25.854] Client: clipboard_client_format_list (0x7f4684000e50) mine_type:"text/plain;charset=utf-8"
[23:15:25.854] RDP clipboard_data_source_publish (0x7f4684000e50)
[23:15:25.854] RDP clipboard_data_source_cancel (0x7f4684000f40)
[23:15:25.854] RDP clipboard_data_source_send (0x7f4684000e50) fd:88, mime-type:"text/html"
[23:15:25.854] RDP clipboard_data_source_send (0x7f4684000e50) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:15:25.854] RDP clipboard_set_selection (base:0x7f4684000e50}
[23:15:25.854] RDP clipboard_data_source_unref (0x7f4684000f40): refcount:0
[23:15:25.858] Client: clipboard_client_format_data_response (0x7f4684000e50) flags:1, dataLen:1680
[23:15:25.858] RDP clipboard_data_source_write (0x7f4684000e50) write completed (1529 bytes)
[23:15:25.858] RDP clipboard_data_source_unref (0x7f4684000e50): refcount:1
[23:16:00.188] app_list_monitor_thread: file created/updated (microsoft-edge-dev.desktop)
[23:16:00.190] desktop file: /usr/share/applications/microsoft-edge-dev.desktop
[23:16:00.190]     Name[en_US]:Microsoft Edge (dev) (Ubuntu)
[23:16:00.190]     Exec:/usr/bin/microsoft-edge-dev
[23:16:00.190]     TryExec:(null)
[23:16:00.190]     WorkingDir:(null)
[23:16:00.190]     Icon name:microsoft-edge-dev
[23:16:00.190]     Icon file:(null)
[23:16:00.190] app list entry updated: Key:microsoft-edge-dev, Name:Microsoft Edge (dev) (Ubuntu)
[23:16:00.190] shell_blend_overlay_icon: app 128x128; overlay 128x128; scale 1.75x1.75
[23:16:00.190] rdp_rail_notify_app_list(): rdp_peer 0x55997a71ba80
[23:16:00.190]     inSync: 0
[23:16:00.190]     syncStart: 0
[23:16:00.190]     syncEnd: 0
[23:16:00.190]     newAppId: 1
[23:16:00.190]     deleteAppId: 0
[23:16:00.190]     deleteAppProvider: 0
[23:16:00.190]     appId: microsoft-edge-dev
[23:16:00.190]     appGroup: (null)
[23:16:00.190]     appExecPath: /usr/bin/microsoft-edge-dev
[23:16:00.190]     appWorkingDir: (null)
[23:16:00.190]     appDesc: Microsoft Edge (dev) (Ubuntu)
[23:16:00.190]     appIcon: 0x55997a717620
[23:16:00.190]     appProvider: (null)
[23:16:19.139] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:16:19.139] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:16:19.139] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:16:19.139] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:16:19.139] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:16:19.139] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:16:19.139] Client: clipboard_client_format_list (0x7f4684000b20) allocated
[23:16:19.139] Client: clipboard_client_format_list (0x7f4684000b20) mine_type:"text/html"
[23:16:19.139] Client: clipboard_client_format_list (0x7f4684000b20) mine_type:"text/plain;charset=utf-8"
[23:16:19.139] RDP clipboard_data_source_publish (0x7f4684000b20)
[23:16:19.139] RDP clipboard_data_source_cancel (0x7f4684000e50)
[23:16:19.139] RDP clipboard_data_source_send (0x7f4684000b20) fd:88, mime-type:"text/html"
[23:16:19.139] RDP clipboard_data_source_send (0x7f4684000b20) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:16:19.139] RDP clipboard_set_selection (base:0x7f4684000b20}
[23:16:19.139] RDP clipboard_data_source_unref (0x7f4684000e50): refcount:0
[23:16:19.141] Client: clipboard_client_format_data_response (0x7f4684000b20) flags:2, dataLen:0
[23:16:19.141] RDP clipboard_data_source_unref (0x7f4684000b20): refcount:1
[23:16:19.854] Spawned Xwayland server, pid 2709
[23:16:21.073] rdp_rail_idle_handler is called on peerCtx:0x55997a71ba80
[23:16:21.515] xfixes version: 5.0
[23:16:21.519] created wm, root 581
[23:16:21.519] xfixes selection notify event: owner 2097153
[23:16:21.519] our window, skipping
[23:16:22.129] shell_blend_overlay_icon: app 128x128; overlay 128x128; scale 1.75x1.75
[23:16:22.129] rdp_rail_set_window_icon: original icon width:128 height:128 format:537036936
[23:16:22.129] rdp_rail_set_window_icon: converted icon width:96 height:96 format:537036936
[23:16:22.242] rdp_rail_wake_handler is called on peerCtx:0x55997a71ba80
[23:16:22.243] shell_blend_overlay_icon: app 128x128; overlay 128x128; scale 1.75x1.75
[23:16:22.243] rdp_rail_set_window_icon: original icon width:128 height:128 format:537036936
[23:16:22.243] rdp_rail_set_window_icon: converted icon width:96 height:96 format:537036936
[23:16:22.243] Client: ClientGetAppidReq: pid:2630 appId:Microsoft-edge-dev
[23:16:22.267] !!!cursor role is added after creation - WindowId:0x1
[23:16:24.790] Client: LanguageImeInfo: ProfileType: 2 (TF_PROFILETYPE_KEYBOARDLAYOUT)
[23:16:24.790] Client: LanguageImeInfo: LanguageID: 0x409
[23:16:24.790] Client: LanguageImeInfo: LanguageProfileCLSID: GUID_NULL
[23:16:24.790] Client: LanguageImeInfo: ProfileGUID: GUID_NULL
[23:16:24.790] Client: LanguageImeInfo: KeyboardLayout: 0x409
[23:16:24.790] convert_rdp_keyboard_to_xkb_rule_names: matching layout=us variant=(null)
[23:16:56.330] Client: ClientGetAppidReq: WindowId:0x5 does not have appId, or not top level window.
[23:17:00.628] Client: ClientGetAppidReq: WindowId:0x6 does not have appId, or not top level window.
[23:18:38.654] xfixes selection notify event: owner 4194314
[23:18:38.656] RDP clipboard_data_source_cancel (0x7f4684000b20)
[23:18:38.656] RDP clipboard_set_selection (base:0x55997aa68d90}
[23:18:38.656] RDP clipboard_data_source_unref (0x7f4684000b20): refcount:0
[23:18:38.656] RDP clipboard_set_selection (base:0x55997aa68d90) available formats[0]: text/plain;charset=utf-8
[23:18:38.656] RDP clipboard_set_selection (base:0x55997aa68d90) supported formats[0]: 1: CF_TEXT
[23:18:38.656] wrote 46 (chunk size 46) of 46 bytes
[23:18:38.656] transfer complete
[23:18:38.674] Client: clipboard_client_format_list_response msgFlags:0x1
[23:18:38.685] Client: clipboard_client_format_data_request requestedFormatId:1 - CF_TEXT
[23:18:38.686] RDP clipboard_data_source_request (base:0x55997aa68d90) requested mime type:"text/plain;charset=utf-8"
[23:18:38.686] RDP clipboard_data_source_request (base:0x55997aa68d90) available formats: text/plain;charset=utf-8
[23:18:38.686] RDP clipboard_data_source_request (0x55997aae4a10) allocated
[23:18:38.686] wrote 46 (chunk size 46) of 46 bytes
[23:18:38.686] transfer complete
[23:18:38.686] RDP clipboard_data_source_read (0x55997aae4a10): read completed (46 bytes)
[23:18:38.686] Client: clipboard_client_send_format_data_response (0x55997aae4a10) format_index:0 text/plain;charset=utf-8 (47 bytes)
[23:18:38.686] RDP clipboard_data_source_unref (0x55997aae4a10): refcount:0
[23:18:42.097] Client: ClientGetAppidReq: WindowId:0x7 is not found.
[23:19:16.306] xfixes selection notify event: owner 4194314
[23:19:16.307] xfixes selection notify event: owner 4194314
[23:19:16.308] RDP clipboard_set_selection (base:0x55997aa7b180}
[23:19:16.308] RDP clipboard_set_selection (base:0x55997aa7b180) available formats[0]: text/plain;charset=utf-8
[23:19:16.308] RDP clipboard_set_selection (base:0x55997aa7b180) supported formats[0]: 1: CF_TEXT
[23:19:16.309] wrote 35 (chunk size 35) of 35 bytes
[23:19:16.309] transfer complete
[23:19:16.314] Client: clipboard_client_format_list_response msgFlags:0x1
[23:19:16.324] Client: clipboard_client_format_data_request requestedFormatId:1 - CF_TEXT
[23:19:16.325] RDP clipboard_data_source_request (base:0x55997aa7b180) requested mime type:"text/plain;charset=utf-8"
[23:19:16.325] RDP clipboard_data_source_request (base:0x55997aa7b180) available formats: text/plain;charset=utf-8
[23:19:16.325] RDP clipboard_data_source_request (0x55997aa90750) allocated
[23:19:16.325] wrote 35 (chunk size 35) of 35 bytes
[23:19:16.325] transfer complete
[23:19:16.325] RDP clipboard_data_source_read (0x55997aa90750): read completed (35 bytes)
[23:19:16.325] Client: clipboard_client_send_format_data_response (0x55997aa90750) format_index:0 text/plain;charset=utf-8 (36 bytes)
[23:19:16.325] RDP clipboard_data_source_unref (0x55997aa90750): refcount:0
[23:19:38.731] Client: clipboard_client_format_data_request requestedFormatId:1 - CF_TEXT
[23:19:38.731] RDP clipboard_data_source_request (base:0x55997aa7b180) requested mime type:"text/plain;charset=utf-8"
[23:19:38.731] RDP clipboard_data_source_request (base:0x55997aa7b180) available formats: text/plain;charset=utf-8
[23:19:38.731] RDP clipboard_data_source_request (0x55997aa90750) allocated
[23:19:38.731] wrote 35 (chunk size 35) of 35 bytes
[23:19:38.731] transfer complete
[23:19:38.731] RDP clipboard_data_source_read (0x55997aa90750): read completed (35 bytes)
[23:19:38.731] Client: clipboard_client_send_format_data_response (0x55997aa90750) format_index:0 text/plain;charset=utf-8 (36 bytes)
[23:19:38.731] RDP clipboard_data_source_unref (0x55997aa90750): refcount:0
[23:21:30.284] Client: clipboard_client_format_list clipboard format list: numFormats:3
[23:21:30.284] Client: clipboard_client_format_list clipboard formats[0]: formatId:49553, formatName:PNG
[23:21:30.284] Client: clipboard_client_format_list clipboard formats[1]: formatId:8, formatName:CF_DIB
[23:21:30.284] Client: clipboard_client_format_list clipboard formats[2]: formatId:17, formatName:CF_DIBV5
[23:21:30.284] Client: clipboard_client_format_list (0x7f4684000c90) allocated
[23:21:30.284] Client: clipboard_client_format_list (0x7f4684000c90) mine_type:"image/bmp"
[23:21:30.284] RDP clipboard_data_source_publish (0x7f4684000c90)
[23:21:30.284] RDP clipboard_data_source_send (0x7f4684000c90) fd:91, mime-type:"image/bmp"
[23:21:30.284] RDP clipboard_data_source_send (0x7f4684000c90) request index:1 formatId:8 CF_DIB
[23:21:30.284] RDP clipboard_set_selection (base:0x7f4684000c90}
[23:21:30.289] Client: clipboard_client_format_data_response (0x7f4684000c90) flags:2, dataLen:0
[23:21:30.289] RDP clipboard_data_source_unref (0x7f4684000c90): refcount:1
[23:21:30.301] Client: clipboard_client_format_list clipboard format list: numFormats:3
[23:21:30.301] Client: clipboard_client_format_list clipboard formats[0]: formatId:49553, formatName:PNG
[23:21:30.301] Client: clipboard_client_format_list clipboard formats[1]: formatId:8, formatName:CF_DIB
[23:21:30.301] Client: clipboard_client_format_list clipboard formats[2]: formatId:17, formatName:CF_DIBV5
[23:21:30.301] Client: clipboard_client_format_list (0x7f4684000df0) allocated
[23:21:30.301] Client: clipboard_client_format_list (0x7f4684000df0) mine_type:"image/bmp"
[23:21:30.301] RDP clipboard_data_source_publish (0x7f4684000df0)
[23:21:30.301] RDP clipboard_data_source_cancel (0x7f4684000c90)
[23:21:30.301] RDP clipboard_data_source_send (0x7f4684000df0) fd:91, mime-type:"image/bmp"
[23:21:30.301] RDP clipboard_data_source_send (0x7f4684000df0) request index:1 formatId:8 CF_DIB
[23:21:30.301] RDP clipboard_set_selection (base:0x7f4684000df0}
[23:21:30.301] RDP clipboard_data_source_unref (0x7f4684000c90): refcount:0
[23:21:30.303] Client: clipboard_client_format_data_response (0x7f4684000df0) flags:2, dataLen:0
[23:21:30.303] RDP clipboard_data_source_unref (0x7f4684000df0): refcount:1
[23:21:43.600] xfixes selection notify event: owner 2097153
[23:21:43.600] our window, skipping
[23:21:43.600] xfixes selection notify event: owner 2097153
[23:21:43.600] our window, skipping
[23:21:45.742] xfixes selection notify event: owner 4194314
[23:21:45.742] xfixes selection notify event: owner 4194314
[23:21:45.744] RDP clipboard_data_source_cancel (0x7f4684000df0)
[23:21:45.744] RDP clipboard_set_selection (base:0x55997aa69a50}
[23:21:45.744] RDP clipboard_data_source_unref (0x7f4684000df0): refcount:0
[23:21:45.744] RDP clipboard_set_selection (base:0x55997aa69a50) available formats[0]: text/plain;charset=utf-8
[23:21:45.744] RDP clipboard_set_selection (base:0x55997aa69a50) supported formats[0]: 1: CF_TEXT
[23:21:45.744] wrote 35 (chunk size 35) of 35 bytes
[23:21:45.744] transfer complete
[23:21:45.754] Client: clipboard_client_format_list_response msgFlags:0x1
[23:21:45.764] Client: clipboard_client_format_data_request requestedFormatId:1 - CF_TEXT
[23:21:45.764] RDP clipboard_data_source_request (base:0x55997aa69a50) requested mime type:"text/plain;charset=utf-8"
[23:21:45.764] RDP clipboard_data_source_request (base:0x55997aa69a50) available formats: text/plain;charset=utf-8
[23:21:45.764] RDP clipboard_data_source_request (0x55997aa90750) allocated
[23:21:45.765] wrote 35 (chunk size 35) of 35 bytes
[23:21:45.765] transfer complete
[23:21:45.765] RDP clipboard_data_source_read (0x55997aa90750): read completed (35 bytes)
[23:21:45.765] Client: clipboard_client_send_format_data_response (0x55997aa90750) format_index:0 text/plain;charset=utf-8 (36 bytes)
[23:21:45.765] RDP clipboard_data_source_unref (0x55997aa90750): refcount:0
[23:21:46.472] Client: clipboard_client_format_data_request requestedFormatId:1 - CF_TEXT
[23:21:46.472] RDP clipboard_data_source_request (base:0x55997aa69a50) requested mime type:"text/plain;charset=utf-8"
[23:21:46.472] RDP clipboard_data_source_request (base:0x55997aa69a50) available formats: text/plain;charset=utf-8
[23:21:46.472] RDP clipboard_data_source_request (0x55997aa90750) allocated
[23:21:46.472] wrote 35 (chunk size 35) of 35 bytes
[23:21:46.472] transfer complete
[23:21:46.472] RDP clipboard_data_source_read (0x55997aa90750): read completed (35 bytes)
[23:21:46.472] Client: clipboard_client_send_format_data_response (0x55997aa90750) format_index:0 text/plain;charset=utf-8 (36 bytes)
[23:21:46.472] RDP clipboard_data_source_unref (0x55997aa90750): refcount:0
[23:21:57.324] Client: clipboard_client_format_list clipboard format list: numFormats:3
[23:21:57.324] Client: clipboard_client_format_list clipboard formats[0]: formatId:49553, formatName:PNG
[23:21:57.324] Client: clipboard_client_format_list clipboard formats[1]: formatId:8, formatName:CF_DIB
[23:21:57.324] Client: clipboard_client_format_list clipboard formats[2]: formatId:17, formatName:CF_DIBV5
[23:21:57.324] Client: clipboard_client_format_list (0x7f4684000df0) allocated
[23:21:57.324] Client: clipboard_client_format_list (0x7f4684000df0) mine_type:"image/bmp"
[23:21:57.324] RDP clipboard_data_source_publish (0x7f4684000df0)
[23:21:57.324] RDP clipboard_data_source_send (0x7f4684000df0) fd:91, mime-type:"image/bmp"
[23:21:57.325] RDP clipboard_data_source_send (0x7f4684000df0) request index:1 formatId:8 CF_DIB
[23:21:57.325] RDP clipboard_set_selection (base:0x7f4684000df0}
[23:21:57.327] Client: clipboard_client_format_data_response (0x7f4684000df0) flags:2, dataLen:0
[23:21:57.327] RDP clipboard_data_source_unref (0x7f4684000df0): refcount:1
[23:21:57.346] Client: clipboard_client_format_list clipboard format list: numFormats:3
[23:21:57.346] Client: clipboard_client_format_list clipboard formats[0]: formatId:49553, formatName:PNG
[23:21:57.346] Client: clipboard_client_format_list clipboard formats[1]: formatId:8, formatName:CF_DIB
[23:21:57.346] Client: clipboard_client_format_list clipboard formats[2]: formatId:17, formatName:CF_DIBV5
[23:21:57.346] Client: clipboard_client_format_list (0x7f4684000f00) allocated
[23:21:57.346] Client: clipboard_client_format_list (0x7f4684000f00) mine_type:"image/bmp"
[23:21:57.346] RDP clipboard_data_source_publish (0x7f4684000f00)
[23:21:57.346] RDP clipboard_data_source_cancel (0x7f4684000df0)
[23:21:57.346] RDP clipboard_data_source_send (0x7f4684000f00) fd:91, mime-type:"image/bmp"
[23:21:57.346] RDP clipboard_data_source_send (0x7f4684000f00) request index:1 formatId:8 CF_DIB
[23:21:57.346] RDP clipboard_set_selection (base:0x7f4684000f00}
[23:21:57.346] RDP clipboard_data_source_unref (0x7f4684000df0): refcount:0
[23:21:57.451] Client: clipboard_client_format_data_response (0x7f4684000f00) flags:1, dataLen:4450500
[23:21:57.455] RDP clipboard_data_source_write (0x7f4684000f00) write completed (4450514 bytes)
[23:21:57.455] RDP clipboard_data_source_unref (0x7f4684000f00): refcount:1
[23:23:47.682] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:23:47.682] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:23:47.682] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:23:47.682] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:23:47.682] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:23:47.682] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:23:47.682] Client: clipboard_client_format_list (0x7f4684000c80) allocated
[23:23:47.682] Client: clipboard_client_format_list (0x7f4684000c80) mine_type:"text/html"
[23:23:47.682] Client: clipboard_client_format_list (0x7f4684000c80) mine_type:"text/plain;charset=utf-8"
[23:23:47.682] RDP clipboard_data_source_publish (0x7f4684000c80)
[23:23:47.682] RDP clipboard_data_source_cancel (0x7f4684000f00)
[23:23:47.682] RDP clipboard_data_source_send (0x7f4684000c80) fd:91, mime-type:"text/html"
[23:23:47.682] RDP clipboard_data_source_send (0x7f4684000c80) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:23:47.682] RDP clipboard_set_selection (base:0x7f4684000c80}
[23:23:47.682] RDP clipboard_data_source_unref (0x7f4684000f00): refcount:0
[23:23:47.684] Client: clipboard_client_format_data_response (0x7f4684000c80) flags:1, dataLen:928
[23:23:47.684] RDP clipboard_data_source_write (0x7f4684000c80) write completed (767 bytes)
[23:23:47.684] RDP clipboard_data_source_unref (0x7f4684000c80): refcount:1
[23:23:47.888] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:23:47.888] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:23:47.888] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:23:47.888] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:23:47.888] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:23:47.888] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:23:47.888] Client: clipboard_client_format_list (0x7f4684000e70) allocated
[23:23:47.888] Client: clipboard_client_format_list (0x7f4684000e70) mine_type:"text/html"
[23:23:47.888] Client: clipboard_client_format_list (0x7f4684000e70) mine_type:"text/plain;charset=utf-8"
[23:23:47.889] RDP clipboard_data_source_publish (0x7f4684000e70)
[23:23:47.889] RDP clipboard_data_source_cancel (0x7f4684000c80)
[23:23:47.889] RDP clipboard_data_source_send (0x7f4684000e70) fd:91, mime-type:"text/html"
[23:23:47.889] RDP clipboard_data_source_send (0x7f4684000e70) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:23:47.889] RDP clipboard_set_selection (base:0x7f4684000e70}
[23:23:47.889] RDP clipboard_data_source_unref (0x7f4684000c80): refcount:0
[23:23:47.889] Client: clipboard_client_format_data_response (0x7f4684000e70) flags:2, dataLen:0
[23:23:47.889] RDP clipboard_data_source_unref (0x7f4684000e70): refcount:1
[23:23:48.073] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:23:48.073] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:23:48.073] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:23:48.073] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:23:48.073] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:23:48.073] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:23:48.073] Client: clipboard_client_format_list (0x7f4684000f40) allocated
[23:23:48.073] Client: clipboard_client_format_list (0x7f4684000f40) mine_type:"text/html"
[23:23:48.073] Client: clipboard_client_format_list (0x7f4684000f40) mine_type:"text/plain;charset=utf-8"
[23:23:48.074] RDP clipboard_data_source_publish (0x7f4684000f40)
[23:23:48.074] RDP clipboard_data_source_cancel (0x7f4684000e70)
[23:23:48.074] RDP clipboard_data_source_send (0x7f4684000f40) fd:91, mime-type:"text/html"
[23:23:48.074] RDP clipboard_data_source_send (0x7f4684000f40) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:23:48.074] RDP clipboard_set_selection (base:0x7f4684000f40}
[23:23:48.074] RDP clipboard_data_source_unref (0x7f4684000e70): refcount:0
[23:23:48.075] Client: clipboard_client_format_data_response (0x7f4684000f40) flags:2, dataLen:0
[23:23:48.075] RDP clipboard_data_source_unref (0x7f4684000f40): refcount:1
[23:23:48.245] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:23:48.245] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:23:48.245] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:23:48.245] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:23:48.245] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:23:48.245] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:23:48.245] Client: clipboard_client_format_list (0x7f4684000e70) allocated
[23:23:48.245] Client: clipboard_client_format_list (0x7f4684000e70) mine_type:"text/html"
[23:23:48.245] Client: clipboard_client_format_list (0x7f4684000e70) mine_type:"text/plain;charset=utf-8"
[23:23:48.245] RDP clipboard_data_source_publish (0x7f4684000e70)
[23:23:48.245] RDP clipboard_data_source_cancel (0x7f4684000f40)
[23:23:48.246] RDP clipboard_data_source_send (0x7f4684000e70) fd:91, mime-type:"text/html"
[23:23:48.246] RDP clipboard_data_source_send (0x7f4684000e70) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:23:48.246] RDP clipboard_set_selection (base:0x7f4684000e70}
[23:23:48.246] RDP clipboard_data_source_unref (0x7f4684000f40): refcount:0
[23:23:48.248] Client: clipboard_client_format_data_response (0x7f4684000e70) flags:2, dataLen:0
[23:23:48.248] RDP clipboard_data_source_unref (0x7f4684000e70): refcount:1
[23:23:48.417] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:23:48.417] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:23:48.417] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:23:48.417] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:23:48.417] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:23:48.417] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:23:48.417] Client: clipboard_client_format_list (0x7f4684000f40) allocated
[23:23:48.417] Client: clipboard_client_format_list (0x7f4684000f40) mine_type:"text/html"
[23:23:48.417] Client: clipboard_client_format_list (0x7f4684000f40) mine_type:"text/plain;charset=utf-8"
[23:23:48.417] RDP clipboard_data_source_publish (0x7f4684000f40)
[23:23:48.417] RDP clipboard_data_source_cancel (0x7f4684000e70)
[23:23:48.417] RDP clipboard_data_source_send (0x7f4684000f40) fd:91, mime-type:"text/html"
[23:23:48.417] RDP clipboard_data_source_send (0x7f4684000f40) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:23:48.417] RDP clipboard_set_selection (base:0x7f4684000f40}
[23:23:48.417] RDP clipboard_data_source_unref (0x7f4684000e70): refcount:0
[23:23:48.418] Client: clipboard_client_format_data_response (0x7f4684000f40) flags:2, dataLen:0
[23:23:48.418] RDP clipboard_data_source_unref (0x7f4684000f40): refcount:1
[23:23:48.582] Client: clipboard_client_format_list clipboard format list: numFormats:5
[23:23:48.582] Client: clipboard_client_format_list clipboard formats[0]: formatId:49414, formatName:HTML Format
[23:23:48.583] Client: clipboard_client_format_list clipboard formats[1]: formatId:13, formatName:CF_UNICODETEXT
[23:23:48.583] Client: clipboard_client_format_list clipboard formats[2]: formatId:16, formatName:CF_LOCALE
[23:23:48.583] Client: clipboard_client_format_list clipboard formats[3]: formatId:1, formatName:CF_TEXT
[23:23:48.583] Client: clipboard_client_format_list clipboard formats[4]: formatId:7, formatName:CF_OEMTEX
[23:23:48.583] Client: clipboard_client_format_list (0x7f4684000e70) allocated
[23:23:48.583] Client: clipboard_client_format_list (0x7f4684000e70) mine_type:"text/html"
[23:23:48.583] Client: clipboard_client_format_list (0x7f4684000e70) mine_type:"text/plain;charset=utf-8"
[23:23:48.583] RDP clipboard_data_source_publish (0x7f4684000e70)
[23:23:48.583] RDP clipboard_data_source_cancel (0x7f4684000f40)
[23:23:48.583] RDP clipboard_data_source_send (0x7f4684000e70) fd:91, mime-type:"text/html"
[23:23:48.583] RDP clipboard_data_source_send (0x7f4684000e70) request index:3 formatId:49414 Client side Registered Clipboard Format
[23:23:48.583] RDP clipboard_set_selection (base:0x7f4684000e70}
[23:23:48.583] RDP clipboard_data_source_unref (0x7f4684000f40): refcount:0
[23:23:48.584] Client: clipboard_client_format_data_response (0x7f4684000e70) flags:1, dataLen:928
[23:23:48.584] RDP clipboard_data_source_write (0x7f4684000e70) write completed (767 bytes)
[23:23:48.584] RDP clipboard_data_source_unref (0x7f4684000e70): refcount:1
[23:23:49.429] xfixes selection notify event: owner 2097153
[23:23:49.429] our window, skipping
[23:23:49.429] xfixes selection notify event: owner 2097153
[23:23:49.429] our window, skipping
[23:23:49.429] xfixes selection notify event: owner 2097153
[23:23:49.429] our window, skipping
[23:23:49.429] xfixes selection notify event: owner 2097153
[23:23:49.429] our window, skipping
[23:23:49.429] xfixes selection notify event: owner 2097153
[23:23:49.429] our window, skipping
[23:23:49.429] xfixes selection notify event: owner 2097153
[23:23:49.429] our window, skipping
[23:23:49.429] xfixes selection notify event: owner 2097153
[23:23:49.429] our window, skipping
[23:23:49.429] xfixes selection notify event: owner 2097153
[23:23:49.429] our window, skipping
[23:23:50.053] Client: ClientGetAppidReq: WindowId:0x8 does not have appId, or not top level window.

Thanks for the feedback @Peredery . This is something we are aware of and are working on improving. We'll soon add a configuration option that will allow you to manually chose the rate at which the Weston compositor composes to match your screen, longer term this will be done automatically and align with your monitor refresh.

This is addressed in 1.0.22 which was released earlier today. To pick up the update, please execute the following from an elevated command prompt:
wsl --shutdown
wsl --update

Please see this article for details on how to change the default WSLg presentation rate.
https://github.com/microsoft/wslg/wiki/Controlling-WSLg-frame-rate


Migrate to statsite 'organisation'?

It seems the author simply doesn't have the time to keep track of all the issues and PR's (which makes sense, it's a lot of work+time), so maybe it's a good idea to have some sort of group or organisation with more people that can accept PR's?

Agreed, I think it'd make sense if more contributors could merge PRs and avoid maintaining long-lived forks

I hope @armon has a few minutes to spare to say something about this. If he is too busy (which does happen, work gets in the way quite often for me as well), we could always just decide to set up an "official" fork.

Happy to help with the project if it branches out into an org, and possibly work on moving our long-running fork into the main code base (https://github.com/lyft/statsite)

Let's see what others (or @armon) have to say for the next 2-3 days, even with 3 volunteers we would have enough people to get an org going.

Make sense, but which repo will be a base fork?

I imagine this repo would be the base fork as its the one most people are already running. I can take the multi-sink + built-in HTTP fork (+ critical bug fix to sampling) and merge it back in with all the changes in the upstream later (build system, event system, etc).

Using this repo would indeed be the best plan, most forks are based on this one and merge back in to this one. Changing that will make it harder for everyone to add their pending PR's.
I'm trying to figure out if I can break down my monster-PR as to make the merging for others easier, the alternative would be me merging first and everyone else merging on top of that.
I've taken the liberty of setting up an org named 'statsite', but it's @armon his call on weather that's okay. It's his name after all, and while I'm not really all that interested in legal aspects, I just don't want an unfriendly break.

Hey all! Funny I was just thinking in the shower about emailing contributors to give commit access. Unfortunately my days are dominated by management and I've neglected the project. I would be happy to move it to an organization.

@johnkeates Do you want me to just transfer this to that organization?

CC: @sleepybishop @melkor217 who have also made contributions.

I suppose it makes sense to transfer it, great minds think alike eh ;-)
I'll start off with adding us four, and you can transfer whenever you feel like it.

@johnkeates Transfered! Thanks so much, and many apologies for being slow to do this.

@armon thanks! and no worries about being busy, we all have jobs taking away our attention and time from stuff like this ;) I think this is a good move, with a bit of luck we'll get a proper community drive behind statsite and your project will go on and grow on it's own!
I'm closing this issue since it's "resolved", thanks for taking the time to make this happen in a neat fashion.


Xnero: Watch worktime.com

Xnero requests the watch of the watch_keyword worktime\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

worktime\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


chore: set amendment_status default to draft

Issue: https://github.com/bcgov/cas-cif/issues/1085

Work finished in another PR


Gives error in a fresh app

I tried on fresh apps but always give this error. When import on the top: unable to resolve module 'react-native-keyboard-aware-scrollview'
"dependencies": {
"react": "16.2.0",
"react-native": "0.53.3",
"react-native-keyboard-aware-scroll-view": "^0.4.4"
},

@potasium react-native-keyboard-aware-scrollview is not the same as react-native-keyboard-aware-scroll-view


Fix packed scene translation parser missing strings.

This is my attempt to fix the POT generator missing strings.

Made a special case for when the node type is empty, it will open the scene and get the type from there. It might even make sense to parse the whole instanced scene too, but it's possible to work around by just adding it to the files list.
(fixes #74194)
Removed the MenuButton and OptionButton case, as it's attempting to parse the old 3.x scene format.
Added a function that will tell if the property of the node should be included. It will now match the property name against all properties in the lookup list, which allows wildcard for popup/item_0/text property of the nodes with popup menus.
(fixes #88017)

I'm planning to add the lookup and exclude properties in the project settings, but i don't know how to do that yet.
This is my first time really working with c++ so i have no idea really what im doing.
It might be that the variable names im using are wrong.
I ported this code from a custom translation parser i made in gdscript.

as it's attempting to parse the old 3.x scene format.

What do you mean by this? This isn't a backwards compatible feature as far as I can tell

It might even make sense to parse the whole instanced scene too

I would recommend against that, since it could lead to parsing of unwanted strings. 😉
Overall, nice job!

BTW the same could happen with the inclusion of all *_text properties. It will include more strings from nodes inheriting AcceptDialog, but also user created nodes which might use this name ending for other purposes. I know there is some properties that end with _text that arent strings, but that's taken care of with the type check. I hope it doesn't cause problems.

Thanks! And congrats for your first merged Godot contribution :tada:


Cannot import redux-mock-store with v1.5.0

Hello,
I upgraded redux-mock-store from v1.4.0 to v1.5.0, and with the new version I get:
TypeError: redux_mock_store_1.default is not a function
No code change on my project except the upgrade to v1.5.0...
Sample use in my project:
import createMockStore from 'redux-mock-store';
import thunk from 'redux-thunk';
import ApiService from 'services/ApiService';

const middlewares = [thunk.withExtraArgument({ apiService: ApiService })];
const mockStore = createMockStore<any>(middlewares);

I'm on 1.5.1 and still experiencing the issue.
Has this been fixed in the meantime. I see that PR #135 was merged, but maybe not tagged yet?
Thanks!

This isn't working for me no matter the version, though it works on an older project. I wonder if a change in typescript/ts-node is incompatible?
Old project which works:
ts-node: 3.3.0, typescript: 2.5.2, redux-mock-store: 1.2.3
New project which fails:
ts-node: 5.0.1, typescript: 2.6.2, redux-mock-store: 1.5.1 (I also tried 1.4.0 since it worked for @abenchi but that fails too for me)

I also share the same problem as @DarthDerrr still getting the redux_mock_store_1.default error.
I've installed the redux-mock-store: 1.4.0, 1.5.1 but its all the same
typescript: 2.7.2,
redux-mock-store: 1.4.0,
@types/redux-mock-store: 0.0.13

@zone-live temporary workaround is to import it like so:
const configureMockStore = require('redux-mock-store');

I have no idea too :D
More info here https://github.com/arnaudbenard/redux-mock-store/issues/144#issuecomment-375298780

@marcucio It works as well, good one 👍

I had a similar problem (not exactly the same error message) when importing configureStore in Storybook stories after a React Native upgrade.
I could solve it by changing :
import configureStore from 'redux-mock-store'

to
import configureStore from 'redux-mock-store/dist/index-umd'

For what it's worth, I couldn't get either of the following to work
import * as configureStore from 'redux-mock-store';
import configureStore from "redux-mock-store";

redux-mock-store: 1.5.1
types/redux-mock-store: 0.0.13
typescript 2.8.3

This was fine:
const configureStore = require('redux-mock-store');

But for now I've reverted to 1.4.0 where this continues to work:
import configureStore from "redux-mock-store";

I have tried adding redux-mock-store v1.4 and v1.5.3 to try and fix the issue, but just by adding the imports or requires generates the error:

Test suite failed to run
Cannot find module 'redux' from 'index.js'
  at Resolver.resolveModule (node_modules/jest-cli/node_modules/jest-resolve/build/index.js:221:17)
  at Object.<anonymous> (../node_modules/redux-mock-store/lib/index.js:8:14)

Package.json:
"redux-mock-store": "^1.5.3"
Test file:
import configureStore from "redux-mock-store";
import thunk from "redux-thunk";

const middlewares = [thunk];
const mockStore = configureStore(middlewares);

I appreciate any suggestions.

@lucksp Can you create a basic example that reproduces this error? And share it on Github?

@newyork-anthonyng like with my whole webpack config, npm scripts, and everything?

@lucksp You don't have to upload your entire project; just enough so that I can run the tests and see the Cannot find module 'redux' from 'index.js' error that you are seeing.
It'll be easier for others to debug.

@lucksp Can you upload this to a Github repository? And make sure that you are able to run npm run test yourself and that it shows the expected error?
I downloaded the files from your gist, but the files aren't configured correctly. For example, I'd have to reconstruct your entire directory structure for imports like "../../src/redux/actions/ActionCreators/Chat". And files like ./__tests__/mocks/localStorageMock.js are missing.
I'll be more than happy to look at it after you do that.
PS. I also find that reproducing your project uncovers where the errors really are.

Of course the simplified repo with only package.json, babelrc, tests, and Action file work.  I'll try to dig some more and get back to ya.


Ergonomic and idiomatic improvements

This issue provides a number of suggestions to improve type safety and lead to more idiomatic Swift.
Use a read-only var property accessor
https://github.com/influxdata/influxdb-client-swift/blob/eabb2999f79af7745ab006f253ab2ede5db0585b/Sources/InfluxDBSwiftApis/InfluxDB2API.swift#L52-L54
to:
internal var urlSession { client.session }

Avoid specifying default access level
With few exceptions, internal is the default access level, and therefore does not need to be included. See https://docs.swift.org/swift-book/LanguageGuide/AccessControl.html#ID7 for more information.
Use lazy stored properties for the APIs
https://github.com/influxdata/influxdb-client-swift/blob/5dc1dce36fa5a41538c4ab4572f6d45d3729f50b/Sources/InfluxDBSwiftApis/InfluxDB2API.swift#L68-L70
to:
public lazy var authorizations: AuthorizationsAPI = { AuthorizationsAPI(influxDB2API: self) }()

This avoids creating redundant instances every time the "API" functions are accessed and provides a more fluent, idiomatic API.
NOTE: The definition of the lazy var must be moved out of the extension definition into the class
Use @discardableResult to avoid compiler warnings
https://github.com/influxdata/influxdb-client-swift/blob/e52b98f4f5bb912b545735c6d6437702c61a2688/Sources/InfluxDBSwift/Point.swift#L70
can be annotated with @discardableResult:
@discardableResult public func addTag(key: String?, value: String?) -> Point {

permitting the following:
https://github.com/influxdata/influxdb-client-swift/blob/e52b98f4f5bb912b545735c6d6437702c61a2688/Sources/InfluxDBSwift/Point.swift#L50
to be changed to:
point.addTag(key: tag.0, value: tag.1)

Use sum types for field values:
Accepting Any makes it difficult to determine what values are acceptable. Passing unsupported values will also result in runtime errors:
https://github.com/influxdata/influxdb-client-swift/blob/e52b98f4f5bb912b545735c6d6437702c61a2688/Sources/InfluxDBSwift/Point.swift#L83
Favour enum as a sum type. In addition, these cases match the data types used in Line Protocol and throughout the documentation:
public enum FieldValue {
    case integer(Int)
    case float(Double)
    case boolean(Bool)
    case string(String)
    case unsigned(UInt)
}

public func addField(key: String, value: FieldValue) {
    // ...
}

Rename WritePrecision to TimestampPrecision
This allows us to use the enumeration to describe a timestamp as a tuple (Int, TimestampPrecision) and also the desired output (line protocol) precision.
https://github.com/influxdata/influxdb-client-swift/blob/d9041018e8d4a547df10270217f1a82b6a59cf37/Sources/InfluxDBSwift/InfluxDBClient.swift#L223
Use sum types for timestamp values:
Accepting Any makes it difficult to determine what values are acceptable. Passing unsupported values will also result in runtime errors:
https://github.com/influxdata/influxdb-client-swift/blob/e52b98f4f5bb912b545735c6d6437702c61a2688/Sources/InfluxDBSwift/Point.swift#L96
Favour enum as a sum type, which explicitly states the allowed value types:
public enum TimestampValue {
    case interval(Int, TimestampPrecision)
    case date(Date)
}

public func time(time: TimestampValue) {

It also ensures when using an integer to describe a timestamp, it must carry a precision for the value.
Defer output timestamp precision to serialisation
The desired line protocol write precision should be deferred to the point of serialisation.
Remove:
https://github.com/influxdata/influxdb-client-swift/blob/e52b98f4f5bb912b545735c6d6437702c61a2688/Sources/InfluxDBSwift/Point.swift#L21
Update the toLineProtocol API:
https://github.com/influxdata/influxdb-client-swift/blob/e52b98f4f5bb912b545735c6d6437702c61a2688/Sources/InfluxDBSwift/Point.swift#L107
to include the output timestamp precision:
public func toLineProtocol(precision: TimestampPrecision = defaultWritePrecision, defaultTags: [String: String?]? = nil) throws -> String? {

Prefer implicit member expressions
See: https://docs.swift.org/swift-book/ReferenceManual/Expressions.html#ID394
This reduces the length of the expressions and is considered idiomatic:
https://github.com/influxdata/influxdb-client-swift/blob/e52b98f4f5bb912b545735c6d6437702c61a2688/Sources/InfluxDBSwift/Point.swift#L283
may be rewritten as:
case .s:

Implement CustomStringConvertable to provide description
Deriving from NSObject to provide description is not idiomatic. NSObject opts the class in to the Objective-C runtime, which may not be intentional.
Remove NSObject:
https://github.com/influxdata/influxdb-client-swift/blob/e52b98f4f5bb912b545735c6d6437702c61a2688/Sources/InfluxDBSwift/Point.swift#L11
and description override:
https://github.com/influxdata/influxdb-client-swift/blob/e52b98f4f5bb912b545735c6d6437702c61a2688/Sources/InfluxDBSwift/Point.swift#L119-L122
Add extension which implements CustomStringConvertable:
extension InfluxDBClient.Point: CustomStringConvertible {
    /// Line Protocol from Data Point.
    public var description: String {
        "Point: measurement:\(measurement), tags:\(tags), fields:\(fields), time:\(time ?? "nil")"
    }
}

Hi @stuartcarnie,
I am almost done but I have one question about: Use sum types for field values:.
The FieldValue defined as
public enum FieldValue {
    case integer(Int)
    case float(Double)
    case boolean(Bool)
    case string(String)
    case unsigned(UInt)
}

doesn't supports other types of Int such as Int8, Int16 and so on.
The Swift doesn't allow to use a Protocol for associated enum value. So we aren't able to use  UnsignedInteger as a associated enum type (case integer(UnsignedInteger)).
What do you think about add other cases for Int and UInt:
public enum FieldValue {
    case integer(Int)
    case integer8(Int8)
    case integer16(Int16)
    ...
}

or we could drop "direct" support for other types of Int?
Regards

@bednar I'd recommend you add convenience initialisers to handle conversion, and keep the list of enumerations strictly to the supported types:
extension FieldValue {
    init(value: Int8) {
        self = .integer(Int(value))
    }

    init(value: Int16) {
        self = .integer(Int(value))
    }
}

@stuartcarnie thanks it looks good 👍

@stuartcarnie

Defer output timestamp precision to serialisation

The precision on the Point is for planning supports of batching write. If the client will be use as a gateway then every point could have different precision.


Sample Update Tracking Issue - complete list

Last Updated: 4/18/21
Doesn't include migration topic samples.

 I've been trying to figure it out from the source code and debugger, and the Docs don't provide sufficient explanation:
    using (var entry = _cache.CreateEntry(CacheKeys.Parent))
    {
        // expire this entry if the dependant entry expires.
        entry.Value = DateTime.Now;
        entry.RegisterPostEvictionCallback(DependentEvictionCallback, this);

        _cache.Set(CacheKeys.Child,
            DateTime.Now,
            new CancellationChangeToken(cts.Token));
    }

How does the child token above communicate to the parent token to evict and what is the purpose of disposing of the parent token? Is this a hack where the parent eviction only occurs because the already marked as expired parent gets evicted when the child cancellation triggers a remove expired entries search? Second suggestion add to sample app a compilable version of this dependent cache entries construction because it makes more sense: https://github.com/aspnet/Caching/issues/48

I am struggling to figure out how to improve the performance of my shiny new Razor Pages/Page Model based app. I have some hefty partial page renders (sidebar icons based on heavy DB calls), which I want to cache (per-model).
I've tried using the  tag helper, but I can't get the example working as expected.
Is there any ETA for the 2.1 release (with the attached docs drop), or better yet - a way to preview the docs as they are being written by Luke?

Is there any ETA for the 2.1 release

The only ETA I'm aware of was given by Scott Hunter at the //Build conference when he said that they were aiming for sometime around the end of this month.

with the attached docs drop

The 2.1 docs are under continuous release now. They're rolling out almost daily. However, samples (this issue) will not be updated until 2.1 releases. We won't have 1.x, 2.0, and 2.1 samples ... only 1.x and 2.x (2.x will be 2.0 prior to 2.1 release; 2.x will become 2.1 after the 2.1 release). We don't want to break users using the latest stable release (2.0) until 2.1 actually hits the street.

@Tratcher The HTTPsys sample isn't happy ("Secure connection failed") with HTTPS Redirection Middleware and ...
.UseHttpSys(options =>
{
    // The following options are set to default values.
    options.Authentication.Schemes = AuthenticationSchemes.None;
    options.Authentication.AllowAnonymous = true;
    options.MaxConnections = null;
    options.MaxRequestBodySize = 30000000;
    options.UrlPrefixes.Add("https://localhost:5001");
});

Should I not use the middleware in this sample ... or how do I fix this?

HttpSys https is hard to set up, we didn't do anything to improve that for 2.1. You don't need to add the middleware for this sample, the middleware usage/config wouldn't be any different here.

Sounds good. Thx. I'll comment the line and add a quick note so that its existence is surfaced.

there shouldn't be any harm if the folder is updated to samples (plural) at the same time.

Let's not do that. It's fine to have a sample folder with multiple samples under it.

Let's not do that.

I'll need to revert some changes when I was preparing for 3.x (i.e., I was setting up a "2.x" folder for the work that will be coming for "3.x" in the future). Do you want me to go back and do that?

Do you want me to go back and do that?

No, don't revert. Just stop making the change from sample to samples in future work.

I sounds like this may be on the radar, but wanted to mention it anyway. The security\authorization\razor-pages-authorization.md page has a link to a non-existent sample, which looks to have been removed when introducing the 2.x sample in #6835).

Thanks for the heads-up.  Link fixed by phone PR #6978 :+1: ... Bad news ... Gulf Power now says that equipment was destroyed by the storm ... No power until tomorrow. :fearful:

bump. This is a huge issue.  How are we keeping all of the samples up to date with the releases?

@spboyer I'm going as fast as I can. 🏃🏃🏃🏃😅
I'm bogged down a bit by other high priority issues. I try to do these updates whenever I can.
This round of updates from 2.0 to 2.1 requires quite a few small changes. Inevitably, the topic requires concurrent changes, and then I find other problems that need to be fixed along the way. Often, it has been so long since the topic has had a major overhaul/update that it's worth going ahead and taking the time to enhance/update it [e.g., File Providers (#7708) and DI (#7412) topics in review now are in this bucket].
It's also been a longstanding problem that we haven't had the staffing to keep samples updated even prior to 2.1 RTM. I'm still to this day finding:

1.0 project.json-based samples in the repo! Yikes!
Topics with only a 1.x sample ... a 2.0 sample was never created.
Samples resting on MVC ... when as of 2.0, they're supposed to be RP-based.
Even samples resting entirely on console apps. Geebers McScreebers! :smile:

How are we keeping all of the samples up to date with the releases?

As laid out in the table, I recommended that we "call dibs" on them and work them through asap. We just want to make sure that two authors don't quietly pick up the same topic+sample and begin working it over. As you can see, I've sort of taken the lead on this issue. I'm getting about two done per week.
One good thing about my having taken so many is that we will achieve a very high level of consistency in the layout and feel of the samples. The downside is that with the other priorities distracting me from this issue it's taking longer than I would like to get them done.

@Rick-Anderson @scottaddie @tdykstra Poser, question, query ❓ ...
The new templates include a package for Razor support with MSBuild. This package isn't necessary for samples to run; however, it would be a nice-to-have and mirror-the-template philosophy to include it in sample apps ...
<PackageReference Include="Microsoft.AspNetCore.Razor.Design" Version="2.2.0" PrivateAssets="All" />

... sooooooooooooo .... do you want to include that?
I guess we're already leaning toward samples that take the in-proc prop ...
<AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>

... that's another one that isn't strictly required for sample apps to run. Under the mirror-the-template philosophy, Scott and I said†, 'Hell, yeah!'
†Well, I added the "hell" part. Scott just said "yeah" on that one. :smile:

This is the kind of "nice to have" that I wouldn't spend time on.

Ok, but I'll eventually need firmer guidance. If we're dropping the in-proc prop into the file just because it's in the template, then doesn't it follow that this one should go in? I'm cool either way ... just asking what we're doing.

@guardrex I've been removing the Microsoft.AspNetCore.Razor.Design package reference, since it's not needed to demonstrate concepts in my docs. It's not worth the time to go back and remove them, but something to consider moving forward.

Ok ... in-proc in and Razor.Design out. Sounds good to me. :+1:

@guardrex is this issue still current? If not, can you close? Also - apologies if i send a few pings your way from some open issues, i'm trying to do a survey of some of the long-standing open issues to address some of them this week. Reach out if i'm hitting you up too much from GitHub. :)

@bradygaster ... That depends. What normally happens on this issue is that at several points in the past, perhaps once a year, I actually canvas every sample app on the repo 😅 and update this issue. Then, we usually hit several of the ...... er ..... more disturbing cases lol ... like 2.x samples 🙈😄 lingering for popular topics.
It's best to ask @Rick-Anderson if he wants to proceed with this process. I don't mind performing another update of this issue in early 2022 if he/you would like to keep using this. This issue is the only overview of where everything stands with sample apps. I fear without it that we'd have no clear knowledge of what's going on. However, it may have outlived its usefulness. I yield to @Rick-Anderson and you to close if that seems best.

I'd love to do a survey like that with you. Have you seen the fantastic improvements to the Orleans samples' visibility Reuben made? I think something like that for SignalR and for the broader ASP.NET would be fantastic.

@guardrex  should we close?

I think so. I don't have time to tend to this further, and it isn't relevant for Blazor, as I've adopted a :x: NO SAMPLES!™ :x: (where possible) approach 😄. This tracking issue was helpful in the old days 👴 to update a bunch of samples release-to-release for topics that I worked on regularly.


[11.x]Replacing outdated mysqldump with mariadb-dump

 mysqldump causes a warning and will be removed in future releases so I simply replaced it with mariadb-dump

I looked into this when I added the MariaDB driver but decided against it because mariadb-dump doesn't work with Sail. I don't think it's possible to install both mysqldump and mariadb-dump in the Sail container, but we could create a symlink mariadb-dump -> mysqldump.

See above.

@staudenmeir good call on the symlink but I do feel that could lead to confusion as people would expect the actual mariadb-dump binary but are in reality using mysqldump.

@driesvints It's not ideal but the easiest workaround I can think of. The current situation isn't ideal for MariaDB users either: If you dump your schema with Sail (i.e. using MySQL's mysqldump), you could lose MariaDB-specific features. If there aren't any critical differences between mariadb-dump and mysqldump now, there will be in the future.
This PR needs to be applied at some point as MariaDB will remove its support for mysqldump.
AFAICS, the cleanest solution would be to add am option to customize the path to the dump binary. With this, Sail could use the binaries from the actual mysql/mariadb containers.

Can we even merge this in on a patch release? Won't existing apps using MariaDB be broken if it's suddenly the mariadb-dump that's being used instead of mysqldump?

Yeah, we should target Laravel 12. I don't think we can rule out issues like this completely.


Previous style is applied after reopening a map and applying a new style

Steps to Reproduce
Please break down here below all the needed steps to reproduce the issue

Create a map selecting ne_10m_railroads dataset
Style color layer based upon cartodb_id field from the UI
Back to the main menu
Open the map again
Change style using the CartoCSS panel:

#layer {
  line-width: 1.5;
  line-color: ramp([cartodb_id], (#00e6a4,#a7e369, #e6de00,#ed8d36,#e60042), jenks);
  line-opacity: 0.9;
}

Apply (clicking or typing CTRL+S)

Current Result

A previous CartoCSS appears in the panel and the style associated with it is applied.

#layer {
  line-width: 1.5;
  line-color: ramp([cartodb_id], (#00e6a4,#a7e369, #e6de00,#ed8d36,#e60042), jenks);
}

Surprisingly, moving with the arrow you can go back and then forward to the "last" CartoCSS and apply again.

Expected result

CartoCSS and style should be applied correctly.

Browser and version

Google Chrome v54.

.carto file

Untitled Map (on 2017-01-19 at 16.24.09).carto.zip

Thanks @ramiroaznar for your report, already fixed (not deployed yet) with https://github.com/CartoDB/cartodb/commit/6d8fecf6e9cbbd2cdf45fb0fdd8132e5fcdb12e3.

This is still happening. For instance, when changing a popup, it resets the style.

We are still on it @ramiroaznar, we haven't deployed anything yet (check status in the builder project board).

this is happening to me too.

Deploying to ded02 for acceptance. Build number 1153.

@ramiroaznar fancy passing acceptance?

Deployed in production.
@ramiroaznar 's life will be better from now on.


Bot is down

Sad day. Me sad. No regex bot. Why. Server issues? Can restart? Financial issues? Need someone to take over? Help is there. Please bring it back? Then me good again.

I don't know why I said it like that

It indeed went down overnight, but I brought it back about an hour ago

Indeed! Thank you so much!


Fixes titles and exception routing

Coverage remained the same at 83.953% when pulling c808c4f6a592a4ed37d1782bd58651d761c0ea4e on ankitkataria:hot-fixes/seo into dd1736a2edd990e43d27e2c71bdbd3d57b3f9081 on CircuitVerse:master.


MSBot Clone command fails

Tool
Name: MSBot
Version: 4.0.7
OS: Windows 10
Describe the bug
MSBot clone command fails with the following error:
ERROR: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.
To Reproduce
Steps to reproduce the behavior:

Use sample: 12.nlp-with-luis
Run the following command:
msbot clone services -f "c:\temp\nlp-with-luis\deploymentScripts\msbotClone" -n nlp-with-luis -l westus --subscriptionId xxxx --appId xxxx --appSecret xxxxx--luisAuthoringKey xxxx --verbose

The following services will be created by this operation:

Azure App Site Plan                     westus              S1                  nlp-with-luis
Azure AppInsights Service               West US 2           F0                  nlp-with-luis
Azure Blob Storage Service              westus              Standard_LRS        nlp-with-luis
Azure Bot Service Registration          Global                                  nlp-with-luis
Azure LUIS Cognitive Service            westus              S0                  nlp-with-luis
Azure WebApp Service (Bot)              westus                                  nlp-with-luis

Would you like to perform this operation? [y/n]y
Checking az botservice version
az -v
Fetching subscription account
az account show --subscription xxxxxxx
Creating resources in subscription: Bot Framework Team xxxxx
Creating Azure group [nlp-with-luis]
az group create -g nlp-with-luis -l westus
Using the provided ApplicationId and Secret rather than auto-provisioning
Creating Azure Bot Service [nlp-with-luis]
az bot create -g nlp-with-luis --name nlp-with-luis --kind webapp --location westus --insights-location "West US 2"  --version v4 --appid xxxxx -p "xxxxx"
az bot create -g nlp-with-luis --name nlp-with-luis --kind webapp --location westus --insights-location "West US 2"  --version v4 --appid xxxxx -p "xxxxx" exit code: 1
WARNING: The behavior of this command has been altered by the following extension: botservice
ERROR: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.
I also tried another variation of the clone command:
msbot clone services -f "c:\temp\nlp-with-luis\deploymentScripts\msbotClone" -n nlp-with-luis -l westus --luisAuthoringKey xxxxxxxxxxx --verbose
It failed with the following message:
[az bot] obtained msa app id and password. Provisioning bot now.
(Please be patient, this may take several minutes)
az bot create -g nlp-with-luis --name nlp-with-luis --kind webapp --location westus --insights-location "West US 2"  --version v4 exit code: 1
WARNING: The behavior of this command has been altered by the following extension: botservice
WARNING: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code xxxx to authenticate.
WARNING: obtained msa app id and password. Provisioning bot now.
ERROR: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.
Expected behavior
Services should be created.
Error messages should be helpful.
[bug]

@Kaiqb have you tried "West US" for location? Looking at az cli, we expect location args in the format of "Central US"

Disregard, sat through a repro with Vishwac. Will investigate

@Kaiqb I'm going to close this as it should be fixed with the latest bits; additionally, the warning:

az bot create -g nlp-with-luis --name nlp-with-luis --kind webapp --location westus --insights-location "West US 2" --version v4 exit code: 1
WARNING: The behavior of this command has been altered by the following extension: botservice

Should not be occurring as create is not modified by the latest extension.


[report-converter] Support sarif format

Fixes #1797.  Credit goes to him!
We've long wanted to support sarif
(https://sarifweb.azurewebsites.net/), and finally, this is the first real step towards it!
This patch can both parse and and export to sarif.

Turns out we have an entry in the main README for all outputs, need to fix that.


Hyphenation

Hi,
I saw you made some amazing improvements in the new version of TextJustify, including the hyphenation, congratulations.
Now I’m trying to implement this new version into my project but I’m facing an issue.
If I right understand, the new way to get texts hyphenatated is:
docView.getDocumentLayoutParams().setHyphenator(new Hyphenator(HyphenPattern.PT));
docView.getDocumentLayoutParams().setHyphenated(true);

This way, nothing happens, seems like LayoutParams.setHyphenator() method will always just return (without set).
So I made some changes in this method and have the hyphenator settled.
But now, I’m facing an Exception:
java.util.ConcurrentModificationException
at java.util.LinkedList$LinkIterator.next(LinkedList.java:124)
at com.bluejamesbond.text.DocumentLayout.measure(DocumentLayout.java:222)
at com.bluejamesbond.text.DocumentView.onMeasure(DocumentView.java:142) …
Let me know if you need more details. Thank you.

Thank you for the fix.
But now I'm getting the text justified but not hyphenated.
I may be missing a step, so, no rush, but can you provide me an example on how to use?
Thank you again.

Thank you for the fix.
But now I'm getting the text justified but not hyphenated.
I may be missing a step, so, no rush, but can you provide me an example on how to use?
Thank you again.

@muriloandrade It does hyphenate. I have put your exact code into the the sample demo which you can download at https://play.google.com/store/apps/details?id=com.bluejamesbond.text.sample
Just click on the "Hyphenated Test"

@muriloandrade It does hyphenate. I have put your exact code into the the sample demo which you can download at https://play.google.com/store/apps/details?id=com.bluejamesbond.text.sample
Just click on the "Hyphenated Test"


Remove support for PHP 8.0, remove unnecessary reflection method calls

Description
Just investigating upgrading to PHPUnit 10 here to find out that it's still blocked by the interop integration tests.
Considering that we'll be dropping 8.0 for PHPUnit 10 anyhow, this patch just chips off one job from that upgrade.

@froschdesign
I don't think it's necessarily worth releasing this, what do you think?

@gsteel
You have planned further changes, so it is possible to summarise this.

I'm releasing this as-is: any further improvements can safely land in 3.4.0 later.


Error: Access to the specified native messaging host is forbidden.

General information

Operating system + version: Arch Linux (Kernel version: 4.11.9-1)
Browser + version: Version 61.0.3163.91 (Official Build) (64-bit)
If installed an official release, put a release version: aur/browserpass 2.0.4-1 [installed]
If built from sources, put a commit id ($ git describe --always):
Browserpass extension version as reported by your browser: 2.0.4

Exact steps to reproduce the problem

Click on the lock icon in the browser

What should happen?
Show the list of accounts
What happened instead?
Error: Access to the specified native messaging host is forbidden.
Extra
This happened after upgrading from a 1.x version.

This is probably not it, but just in case, could you double-check that you don't accidentally have two browserpass chrome extensions installed? There should only be "browserpass-ce", with a blue icon.
The error message itself suggests that you have an issue with the native messaging host definition. How many entries does this command find, and please post the contents of each of them:
$ locate com.dannyvankooten.browserpass.json

No two installations and ID of the extension matches.
Here is the locate output (obfuscated is the username of the system):
/etc/chromium/native-messaging-hosts/com.dannyvankooten.browserpass.json
/etc/chromium/policies/managed/com.dannyvankooten.browserpass.json
/etc/opt/chrome/native-messaging-hosts/com.dannyvankooten.browserpass.json
/etc/opt/chrome/policies/managed/com.dannyvankooten.browserpass.json
/home/obfuscated/.config/google-chrome/NativeMessagingHosts/com.dannyvankooten.browserpass.json
/home/obfuscated/.config/google-chrome/policies/managed/com.dannyvankooten.browserpass.json
/usr/lib/mozilla/native-messaging-hosts/com.dannyvankooten.browserpass.json

I bet one of these files is a left-over from v1, which is incompatible with v2. Simple idea: just try to remove all of them and install aur/browserpass again. Except, the last file is for Firefox though, maybe keep it if you use Firefox, I don't think browserpass handles it.

That solved it. Thank you very much for the very fast help!

p.s. A big thank you for maintaining this project. I am a very happy and grateful user.

Happy to hear it! 🙂


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree


Design of checkboxes in monochrome mode - proposal

Current checkboxes in accessibility menu look like circles, that do not clearly reflect their state in monochrome mode. They are differentiated only by color, which is acceptable in color mode, but in monochrome they're a little confusing:

I propose to use some check marks to make them more clear. For example, I tested it by modifying the SVGs in HTML like this:
<svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path fill-rule="evenodd" clip-rule="evenodd" d="m 16.371092,6.6210937 c 0.513245,0.5203285 0.507123,1.3583198 -0.01367,1.8710938 L 9.8535158,14.896484 c -0.5147559,0.506589 -1.3407128,0.506589 -1.8554687,0 L 3.6425783,10.607422 C 3.1217848,10.094649 3.1156616,9.2566574 3.6289063,8.7363283 4.1416797,8.2155349 4.9796709,8.2094117 5.5,8.7226563 L 8.9257813,12.097656 14.5,6.6074219 c 0.519236,-0.5121001 1.35949,-0.5058647 1.871092,0.013672 z M 10,20 C 15.5228,20 20,15.5228 20,10 20,4.47715 15.5228,0 10,0 4.47715,0 0,4.47715 0,10 0,15.5228 4.47715,20 10,20 Z" fill="currentColor"></path></svg>
The result:

Hello, I'd like to work on this issue. Could you please assign it to me?

@stefanietam @tyler-yin Do you have some ideas around how to make this part of the UI clearer? Shall we go with the suggested solution?
I'm not 100% sure about SVG either in terms of how accessible they are inline. Would need more confirmation here.


Wrap timeline in flex container

Firstly, I'm new to this so apologies if I'm not doing this right!
Overview of PR
Just wrapping the timeline in a flex container in the same way that the header is wrapped in a flex container.
I think there are sometimes issues with the way the width of the viewport is calculated, which in some circumstances can make the timeline go onto two rows like the screenshot below. Resizing the screen forces a recalculation and it renders properly. You can also see this in the codesandbox examples if you slowly resize the preview pane to be smaller, the items jump down (to be in the same position as this screenshot) then they re-render to be in the right place.
Wrapping the sidebar and timeline in a flex container allows the siderbar to shrink, in the same way that the header sidebar shrinks, and always keeps the timeline on the same row

Hi, Thank you for this. I really appreciate your help. Could you please open an issue with the bug so we can connect this to the issue for future documentation.
This will be released in the next feature version that will go out this weekend

Thanks @Ilaiwi. Much appreciated

this will be solved when #391 gets merged. Thanks for reporting. Please refer to #476 for more details

this will be solved when #391 gets merged. Thanks for reporting. Please refer to #476 for more details


Username button

Added button to capture a name and send it to local storage. Added styling to the button.

RE 'welcome username!': Probably on build.html while building or when user is ready to checkout. Could be added to the home page after we hit MVP.


alias problem with callbacks

My tests were working fine on 0.1.2. Upgrade to 0.2.2 has compile issues when using aliases in callbacks.
The following test runs on 0.1.2, but gives the following compile error on 0.2.2:
==> example
Compiled lib/example.ex
Generated example.app
** (CompileError) nofile:7: One.__struct__/0 is undefined, cannot expand struct One
    (elixir) src/elixir_map.erl:44: :elixir_map.translate_struct/4
    (stdlib) lists.erl:1352: :lists.mapfoldl/3
    (stdlib) lists.erl:1353: :lists.mapfoldl/3

# lib/example.ex
defmodule Example do
end

defmodule Example.One do
  defstruct one: 1
  def get, do: inspect(__MODULE__)
end

# test/example_test.exs
defmodule ExampleTest do
  use Pavlov.Case, async: true
  alias Example.One

  before :each do
   {:ok, one: %One{one: 3}}
  end

  it "gets Example.One" do
    assert One.get == "Example.One"
  end

  describe "nested" do
  end
end

Ah, yes, I've also been seeing this in my projects since the upgrade. The way to get deep callbacks and lets was to simply store these functions and then redeclare them inside each child module created by describe or context. This works, but apparently Elixir doesn't "remember" the scope that the function was originally declared under, leading to the problem you're seeing with aliases. I've been trying to figure out a way to store and pass this context along, with no luck so far.
The workaround I found was to either stop using aliases altogether (and use the fully qualified module name) or to do import MyModule inside the callback or let expression.
I'll leave the issue open nonetheless, but maybe you can use the workarounds to get your tests passing in the meantime?
Thanks!


[address-resolver] ensure prev pointer stays valid on entry removal

This commit simplifies the model for iterating through a linked
list by using a prev pointer as the iterator variable. This helps
fix an issue with the prev pointer not staying  valid when entry
is removed from the list during iteration.

@jwhui @abtink side comment. Recently we have found a couple of P1/P2 bugs which OpenThread CI didn't find, but rather (most likely) yours and our longer stress tests. What do you think about addressing this problem on OT CI?
What I'm thinking about is to have tests that stress the network for a greater amount of time (generating running out of message buffers, cache entries and emulating some loss of the packets), so we can detect asserts/faults faster. Because of simulated time, I think, it should be viable to have such tests running on multiple simulated devices possibly for "hours".

@jwhui @abtink side comment. Recently we have found a couple of P1/P2 bugs which OpenThread CI didn't find, but rather (most likely) yours and our longer stress tests. What do you think about addressing this problem on OT CI?
What I'm thinking about is to have tests that stress the network for a greater amount of time (generating running out of message buffers, cache entries and emulating some loss of the packets), so we can detect asserts/faults faster. Because of simulated time, I think, it should be viable to have such tests running on multiple simulated devices possibly for "hours".

@LuDuda, I completely agree. In fact, we are working on an improved OpenThread Network Simulator (OTNS) that should allow for much faster simulation speedup by rewriting the simulation driver (see #4268 for the initial evidence of this). We are planning to open source OTNS very soon and use this as a basis for expanded testing scenarios, including stress tests.
/cc/ @simonlingoogle

@LuDuda I agree that more testing is always good, the key in my opinion is in addition to stress testing, to write more test-cases and covering more situations. At the end, we should be ready to take quick action and investigate issues as no test framework can truly cover all aspects and corner cases (this is nature of active development and product integration).
This issue itself was found by oss-fuzz testing which I believe is run everyday on master and sort of performs the stress testing that you are mentioning.
We did also add a a rather detailed test-case covering the behavior of the address query/cache along with the original #4599 from PR #4600 . This test went through a lot of the behaviors of address reolsver module and many corner-cases:

Verify query timeout and retry behavior:

Multiple address query to non-existing addresses and verify cache entries start in "query" state.
Verify that entries to time out and check that they enter "retry" state.
Check that in "retry" state, during retry delay interval no new address query sent for the same tragets
Verify that after retry delay passed, new address queries are sent correctly again.
Verify that on first time address query the entry cannot be evicted, but in second/next attempts it is allowed to be evicted.

Verify snoop behavior:

Verify snoop behavior and that snoop entries are added correctly on rx packet inspection
Verify that only MAX_SNOOPED_NON_EVICTABLE of snooped entries are non-evictable.
Verify that snoop entries are used and move to "cached" state on tx to same address.

Verify cache entry update:

Verify address cache entry update on successful address notification from  routers
Verify address cache entry update for request to a sleepy child (and that parent is the rloc) and last transaction in cache entry are updated correctly.
Verify cache entry moving to top of list on subsequent use

Verify behavior when cache table is full:

Verify that snoop optimization uses at most MAX_SNOOPED_NON_EVICTABLE entries and not overwrite other cached entries
Verify that snooped entries are converted to "cached" on use.
Verify that entries are moved to top of list on use.
Verify that on full table, oldest entry is evicted.

As you can see this already covers a lot of things. I did actually spent some time to figure out how come the test did not catch the issue being addressed by this PR (it happens to be rather unfortunate order of events which masked this). I am going to update the test to cover the situation being addressed here.

Thank you @abtink for the detailed response.
I'm sorry if I badly formulated my intention of the above comment. I just wanted to present some idea I had for a while, and even started to implement something, though the OTNS sounds great.
I agree that this feature is well verified :+1: In general truely in my opinion you do the best job in community with testing e.g. toranj or unit testing.   :)...
I agree and I think we'd need combination of different approaches: more targeted test-cases (to cover corner cases that may be hard to happen by fuzz/stress test), along with more stress/fuzz testing to cover situations we cannot think of. At the end, I am sure bugs may still slip through once in while... but we'd be ready for it... :)

Let's be ready! :smile:

What I'm thinking about is to have tests that stress the network for a greater amount of time (generating running out of message buffers, cache entries and emulating some loss of the packets), so we can detect asserts/faults faster. Because of simulated time, I think, it should be viable to have such tests running on multiple simulated devices possibly for "hours".

There has been some work on building stress tests for OpenThread. One outcome of the effort is OTNS, which is to be released soon, that can simulate large number of nodes efficiently.
The current stress tests covered some basic connectivity tests and commissioning tests, which have revealed a number of bugs in OT core. I think one difference between stress tests and functional tests (e.x. unittests, tranj) is that stress tests tries to make sure application level functionalities are achievable despite the harsh environment.
I think one way to integrate this into OT CI is to run comprehensive stress tests for each master branch commit so that we reveal issues as soon as possible.
@LuDuda @jwhui

@simonlingoogle, I would prefer to do as much testing as possible before we get into master branch. As @abtink mentioned, we already employ a number of techniques, including unit, functional, fuzzing, static analysis, etc.
I see stress testing as a form of functional testing. Stress tests may cover application scenarios, or something completely random (i.e. monte carlo). It would be great to add these additional test scenarios to our testing mix.


chore(deps): update electron to v3.0.4

Description:
This electron update includes a number of minor fixes and improvements.
Motivation and Context:
Keep dependencies up to date.
How Has This Been Tested?
Verify app builds and runs.
Types of changes:
Dependency update
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Tested ACK b9ebc9b


[POC] CSS Variables

DO NOT MERGE!
This PR demonstrate css vars implementation proposed in #27651

[x] turn theme into css vars
[x] support multiple themes
[x] fix ssr flash issue

Flash issue solved by running script in the body before the <Main> application

open https://deploy-preview-28639--material-ui.netlify.app/css-vars-flash/ and click switch theme (to other theme that is not light).
Hard reload will see the flash (I added setTimeout to make it obvious)
goto https://deploy-preview-28639--material-ui.netlify.app/css-vars-no-flash/ won't see flash (even the same setTimeout)

With css variables, the component does not rerender when theme change (only if the component use the same variable)

[ ] I have followed (at least) the PR section of the contributing guide.

The idea has been proved, so this PR can be closed.


X Axis Flip Still Needed?

Is it still true that ATI sensors don't use the right hand rule for their sensor axes?  I have a new Axia80 and it seems to be correct (i.e. it uses a right hand coord system).  The raw netft_data seems to match up with the +X and +Y labels on the sensor and the +Z data lines up with a right hand rule.  The flip on lines 244/247 of netft_utils seems to be unnecessary.
I did a quick scan of the ATI website and first two sensor drawings in their pdf (the nano17 and then the nano17e) both use a right hand rule as well, although I don't have any other sensors to test on.
I modified my local copy but it could be a good thing to either note or put in a config to disable.

I reached out to an applications engineer with ATI, she told me that all of their sensors follow the right hand rule. So I would think the flip is unnecessary.

@AndyZe
We've fallen into the same pitfall due to the x axis inversion, and are having to use our own fork of the repo which does not apply the inversion.
It'd make sense to fix the issue at the source by either removing the inversion (if all are right-handed) or by providing the option to the user (if there's a mix of left-handed and right-handed).
I'm happy to raise a PR, but would appreciate input on which idea is better suited as I'm not familiar with the range of force sensors ABI offers.


Edit and save a file that is not of the default NOTES_EXT

My NOTES_EXT variable is set to markdown, which is good, because that's what I take most of my notes in. However many of my  "notes" are .c or .py files filled with comments on however the code in the file works. Whenever I open one of these files, notes makes a new blank .md file and names it exactly the same as the file I was trying to open instead of just opening the file. So, for example, if I were trying to open file.c, notes will make a new file titled file.c.md. I want to be able to edit .md notes along with .c and .py. Thanks!

Hi @NumenHackerCracker good suggestion, thanks. I think this sounds like an easy & sensible fix: if the exact filename exists, notes open should use that rather than appending an extension.
Would you be interested in putting together a PR to fix that? I think the main place the extension is used is here: https://github.com/pimterry/notes/blob/428946ed32a29d5fdd100778aa185d548db6b2c2/notes#L173-L184 and it should be easy to add another test for this similar to: https://github.com/pimterry/notes/blob/428946ed32a29d5fdd100778aa185d548db6b2c2/test/test-open.bats#L84-L91

I've been doing some hacking on the script recently and I actually implemented this feature.
I think all I had to do was change get_full_note_path to just not add the file extension if $notes_dir/$notes_path is a file. If not, then test for the extension and add if not there.
Looking at the code you posted, I'm wondering about this:
if [ ! -f "$note_path" ]; then
    note_path="$notes_dir/$note_path"
fi

Is this there in case a user supplies an absolute path or something? it seems like the $nodes_dir should always be prepended, shouldn't it?

If you've got a fix for this issue in general, please do put in a PR, that'd be great.

Is this there in case a user supplies an absolute path or something?

Yes, I'm pretty sure that's why that's there. I don't remember the original reasoning for that (that line was last touched 5 years ago!) but it's a useful option to have, especially for composing notes with other CLI tools.


Fixed opts.destroy, added opts.size, and removed trailing line in files

Come on, dude. Accept this!
Is really simple to integrate.
Also, removed trailing line in files.

Apologies I hadn't seen this! New release coming soon