A blue screen occurs when a remote connection is made using windows11

### xrdp version

0.9.21

### Detailed xrdp version, build options

xrdp <IP_ADDRESS>
  A Remote Desktop Protocol Server.
  Copyright (C) 2004-2020 Jay Sorg, Neutrino Labs, and all contributors.
  See https://github.com/neutrinolabs/xrdp for more information.

  Configure options:
      --enable-ipv6
      --enable-jpeg
      --enable-fuse
      --enable-rfxcodec
      --enable-opus
      --enable-painter
      --enable-vsock
      --build=aarch64-linux-gnu
      --prefix=/usr
      --includedir=${prefix}/include
      --mandir=${prefix}/share/man
      --infodir=${prefix}/share/info
      --sysconfdir=/etc
      --localstatedir=/var
      --disable-silent-rules
      --libdir=${prefix}/lib/aarch64-linux-gnu
      --libexecdir=${prefix}/lib/aarch64-linux-gnu
      --disable-maintainer-mode
      --disable-dependency-tracking
      --with-socketdir=/run/xrdp/sockdir
      build_alias=aarch64-linux-gnu
      CFLAGS=-g -O2 -ffile-prefix-map=/build/xrdp-xCPoG3/xrdp-<IP_ADDRESS>=. -fstack-protector-strong -Wformat -Werror=format-security
      LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed
      CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2
      PKG_CONFIG_PATH=/build/xrdp-xCPoG3/xrdp-<IP_ADDRESS>/pkgconfig

  Compiled with OpenSSL 3.0.11 19 Sep 2023

Operating system & version
debian 12
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
No response
What desktop environment do you use?
No response
Environment xrdp running on
No response
What's your client?
No response
Area(s) with issue?
No response
Steps to reproduce
When using the Raspberry PI zero2w, I installed the bookworm system of debian12 for it, and then tried to connect remotely with win11. After entering the user name and password correctly, the desktop screen still wouldn't display properly, and there was a blue screen and then an error, like the following.

The following information is obtained by viewing related logs.
[20240623-18:01:04] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<IP_ADDRESS> port 20852
[20240623-18:01:04] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20240623-18:01:04] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20240623-18:01:04] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20240623-18:01:04] [WARN ] Cannot accept TLS connections because certificate or private key file is not readable. certificate file: [/etc/xrdp/cert.pem], private key file: [/etc/xrdp/key.pem]
[20240623-18:01:04] [INFO ] Security protocol: configured [RDP], requested [SSL|HYBRID|HYBRID_EX|RDP], selected [RDP]
[20240623-18:01:04] [ERROR] libxrdp_force_read: header read error
[20240623-18:01:04] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20240623-18:01:04] [ERROR] [MCS Connection Sequence] receive connection request failed
[20240623-18:01:04] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20240623-18:01:04] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20240623-18:01:04] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20240623-18:01:04] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20240623-18:01:04] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20240623-18:01:46] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<IP_ADDRESS> port 1699
[20240623-18:01:46] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20240623-18:01:46] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20240623-18:01:46] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20240623-18:01:46] [WARN ] Cannot accept TLS connections because certificate or private key file is not readable. certificate file: [/etc/xrdp/cert.pem], private key file: [/etc/xrdp/key.pem]
[20240623-18:01:46] [INFO ] Security protocol: configured [RDP], requested [RDP], selected [RDP]
[20240623-18:01:46] [INFO ] Connected client computer name: LC
[20240623-18:01:46] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20240623-18:01:46] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20240623-18:01:46] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000804]
[20240623-18:01:46] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [us] options []
[20240623-18:01:46] [INFO ] Non-TLS connection established from ::ffff:<IP_ADDRESS> port 1699: with security level : high
[20240623-18:01:47] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20240623-18:01:47] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 5242880 MB cache entries 100
[20240623-18:01:47] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20240623-18:01:47] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20240623-18:01:47] [WARN ] Cannot find keymap file /etc/xrdp/km-00000804.ini
[20240623-18:01:47] [WARN ] Cannot find keymap file /etc/xrdp/km-00000804.ini
[20240623-18:01:47] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[20240623-18:01:47] [WARN ] local keymap file for 0x00000804 found and doesn't match built in keymap, using local keymap file
[20240623-18:01:53] [INFO ] connecting to sesman on <IP_ADDRESS>:3350
[20240623-18:01:53] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20240623-18:01:53] [INFO ] sesman connect ok
[20240623-18:01:53] [INFO ] sending login info to session manager. Please wait...
[20240623-18:01:53] [INFO ] xrdp_wm_log_msg: login successful for user LC on display 10
[20240623-18:01:53] [INFO ] login successful for user LC on display 10
[20240623-18:01:53] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20240623-18:01:53] [INFO ] started connecting
[20240623-18:01:53] [INFO ] lib_mod_connect: connecting via UNIX socket
[20240623-18:05:23] [INFO ] connection problem, giving up
[20240623-18:05:23] [INFO ] some problem
[20240623-18:05:23] [ERROR] xrdp_wm_log_msg: Error connecting to user session
[20240623-18:05:23] [INFO ] Error connecting to user session

Seeing the above error message, I think it should be the permission problem, but after using the command
sudo adduser xrdp ssl-cert

the previous problem still occurs. I have tried many methods but none of them work
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Anything else?
No response

I would also like to add that this problem occurs when using win11 remote connections, but using VNC-related applications can log in normally

Just came here from your discussion at #3139. I'll close that one and point it here.
Are you trying to use the same user as on the console?
Set up a separate user for xrdp - see the FAQ entry

Just came here from your discussion at #3139. I'll close that one and point it here.
Are you trying to use the same user as on the console?
Set up a separate user for xrdp - see the FAQ entry

Following your advice, I re-established a user
sudo adduser username

However, when I logged in with a new user, I still got the same error as before. On this basis, I turned off VNC functionality and restarted xrdp but the problem did not seem to be resolved
xrdp.log
[20240625-17:21:33] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<IP_ADDRESS> port 13152
[20240625-17:21:33] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20240625-17:21:33] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20240625-17:21:33] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20240625-17:21:33] [WARN ] Cannot accept TLS connections because certificate or private key file is not readable. certificate file: [/etc/xrdp/cert.pem], private key file: [/etc/xrdp/key.pem]
[20240625-17:21:33] [INFO ] Security protocol: configured [RDP], requested [SSL|HYBRID|HYBRID_EX|RDP], selected [RDP]
[20240625-17:21:33] [ERROR] libxrdp_force_read: header read error
[20240625-17:21:33] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20240625-17:21:33] [ERROR] [MCS Connection Sequence] receive connection request failed
[20240625-17:21:33] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20240625-17:21:33] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<IP_ADDRESS> port 13153
[20240625-17:21:33] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20240625-17:21:33] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20240625-17:21:33] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20240625-17:21:33] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20240625-17:21:33] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20240625-17:21:33] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20240625-17:21:33] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20240625-17:21:33] [WARN ] Cannot accept TLS connections because certificate or private key file is not readable. certificate file: [/etc/xrdp/cert.pem], private key file: [/etc/xrdp/key.pem]
[20240625-17:21:33] [INFO ] Security protocol: configured [RDP], requested [RDP], selected [RDP]
[20240625-17:21:33] [INFO ] Connected client computer name: LC
[20240625-17:21:33] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20240625-17:21:33] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20240625-17:21:33] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000804]
[20240625-17:21:33] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [us] options []
[20240625-17:21:33] [INFO ] Non-TLS connection established from ::ffff:<IP_ADDRESS> port 13153: with security level : high
[20240625-17:21:33] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20240625-17:21:33] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 5242880 MB cache entries 100
[20240625-17:21:33] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20240625-17:21:33] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20240625-17:21:33] [WARN ] Cannot find keymap file /etc/xrdp/km-00000804.ini
[20240625-17:21:33] [WARN ] Cannot find keymap file /etc/xrdp/km-00000804.ini
[20240625-17:21:33] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[20240625-17:21:33] [WARN ] local keymap file for 0x00000804 found and doesn't match built in keymap, using local keymap file
[20240625-17:22:01] [INFO ] connecting to sesman on <IP_ADDRESS>:3350
[20240625-17:22:01] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20240625-17:22:01] [INFO ] sesman connect ok
[20240625-17:22:01] [INFO ] sending login info to session manager. Please wait...
[20240625-17:22:01] [INFO ] xrdp_wm_log_msg: login successful for user LC01 on display 10
[20240625-17:22:01] [INFO ] login successful for user LC01 on display 10
[20240625-17:22:01] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20240625-17:22:01] [INFO ] started connecting
[20240625-17:22:01] [INFO ] lib_mod_connect: connecting via UNIX socket
[20240625-17:25:31] [INFO ] connection problem, giving up
[20240625-17:25:31] [INFO ] some problem
[20240625-17:25:31] [ERROR] xrdp_wm_log_msg: Error connecting to user session
[20240625-17:25:31] [INFO ] Error connecting to user session

xrdp-sesman.log
[20240625-17:22:01] [INFO ] Socket 12: AF_INET6 connection received from ::1 port 36434
[20240625-17:22:01] [INFO ] Terminal Server Users group is disabled, allowing authentication
[20240625-17:22:01] [INFO ] ++ created session (access granted): username LC01, ip ::ffff:<IP_ADDRESS>:13153 - socket: 12
[20240625-17:22:01] [INFO ] starting Xorg session...
[20240625-17:22:01] [INFO ] Starting session: session_pid 1435, display :10.0, width 1920, height 1080, bpp 24, client ip ::ffff:<IP_ADDRESS>:13153 - socket: 12, user name LC01
[20240625-17:22:01] [INFO ] [session start] (display 10): calling auth_start_session from pid 1435
[20240625-17:22:01] [ERROR] sesman_data_in: scp_process_msg failed
[20240625-17:22:01] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
[20240625-17:22:02] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20240625-17:22:12] [WARN ] Timed out waiting for X server on display 10 to startup
[20240625-17:22:12] [INFO ] Session started successfully for user LC01 on display 10
[20240625-17:22:12] [INFO ] Starting the xrdp channel server for display 10
[20240625-17:22:12] [INFO ] Session in progress on display 10, waiting until the window manager (pid 1469) exits to end the session
[20240625-17:22:12] [WARN ] Timed out waiting for X server on display 10 to startup
[20240625-17:22:12] [ERROR] There is no X server active on display 10
[20240625-17:22:12] [ERROR] A fatal error has occurred attempting to start the window manager on display 10, aborting connection
[20240625-17:22:12] [WARN ] Window manager (pid 1469, display 10) exited quickly (0 secs). This could indicate a window manager config problem
[20240625-17:22:12] [INFO ] Calling auth_stop_session and auth_end from pid 1435
[20240625-17:22:12] [INFO ] Terminating X server (pid 1470) on display 10
[20240625-17:22:12] [INFO ] Terminating the xrdp channel server (pid 1492) on display 10
[20240625-17:22:12] [INFO ] X server on display 10 (pid 1470) returned exit code 1 and signal number 0
[20240625-17:22:12] [INFO ] xrdp channel server for display 10 (pid 1492) exit code 0 and signal number 0
[20240625-17:22:12] [INFO ] cleanup_sockets:
[20240625-17:22:12] [INFO ] Process 1435 has exited
[20240625-17:22:12] [INFO ] ++ terminated session:  username LC01, display :10.0, session_pid 1435, ip ::ffff:<IP_ADDRESS>:13153 - socket: 12

I just found that my wins11 user name and the Raspberry PI user name are the same, so I changed a new computer to test, the blue screen still appears, the error content is as follows
[20240625-18:01:02] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<IP_ADDRESS> port 51693
[20240625-18:01:02] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20240625-18:01:02] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20240625-18:01:02] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20240625-18:01:02] [WARN ] Cannot accept TLS connections because certificate or private key file is not readable. certificate file: [/etc/xrdp/cert.pem], private key file: [/etc/xrdp/key.pem]
[20240625-18:01:02] [INFO ] Security protocol: configured [RDP], requested [SSL|HYBRID|HYBRID_EX|RDP], selected [RDP]
[20240625-18:01:02] [ERROR] libxrdp_force_read: header read error
[20240625-18:01:02] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20240625-18:01:02] [ERROR] [MCS Connection Sequence] receive connection request failed
[20240625-18:01:02] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20240625-18:01:02] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20240625-18:01:02] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20240625-18:01:02] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20240625-18:01:02] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20240625-18:01:03] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:<IP_ADDRESS> port 51694
[20240625-18:01:03] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20240625-18:01:03] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20240625-18:01:03] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20240625-18:01:03] [WARN ] Cannot accept TLS connections because certificate or private key file is not readable. certificate file: [/etc/xrdp/cert.pem], private key file: [/etc/xrdp/key.pem]
[20240625-18:01:03] [INFO ] Security protocol: configured [RDP], requested [RDP], selected [RDP]
[20240625-18:01:03] [INFO ] Connected client computer name: REND_LC
[20240625-18:01:03] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20240625-18:01:03] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20240625-18:01:03] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000804]
[20240625-18:01:03] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [us] options []
[20240625-18:01:03] [INFO ] Non-TLS connection established from ::ffff:<IP_ADDRESS> port 51694: with security level : high
[20240625-18:01:03] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20240625-18:01:03] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 10485760 MB cache entries 100
[20240625-18:01:03] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20240625-18:01:03] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20240625-18:01:03] [WARN ] Cannot find keymap file /etc/xrdp/km-00000804.ini
[20240625-18:01:03] [WARN ] Cannot find keymap file /etc/xrdp/km-00000804.ini
[20240625-18:01:03] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[20240625-18:01:03] [WARN ] local keymap file for 0x00000804 found and doesn't match built in keymap, using local keymap file
[20240625-18:01:12] [INFO ] connecting to sesman on <IP_ADDRESS>:3350
[20240625-18:01:13] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20240625-18:01:13] [INFO ] sesman connect ok
[20240625-18:01:13] [INFO ] sending login info to session manager. Please wait...
[20240625-18:01:13] [INFO ] xrdp_wm_log_msg: login successful for user LC01 on display 10
[20240625-18:01:13] [INFO ] login successful for user LC01 on display 10
[20240625-18:01:13] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20240625-18:01:13] [INFO ] started connecting
[20240625-18:01:13] [INFO ] lib_mod_connect: connecting via UNIX socket
[20240625-18:04:43] [INFO ] connection problem, giving up
[20240625-18:04:43] [INFO ] some problem
[20240625-18:04:43] [ERROR] xrdp_wm_log_msg: Error connecting to user session
[20240625-18:04:43] [INFO ] Error connecting to user session
[20240625-18:06:38] [INFO ] Received termination signal, stopping the server accept new connections thread
[20240625-18:06:38] [INFO ] address [<IP_ADDRESS>] port [3389] mode 1
[20240625-18:06:38] [INFO ] listening to port 3389 on <IP_ADDRESS>
[20240625-18:06:38] [INFO ] xrdp_listen_pp done
[20240625-18:06:40] [INFO ] starting xrdp with pid 1977
[20240625-18:06:40] [INFO ] address [<IP_ADDRESS>] port [3389] mode 1
[20240625-18:06:40] [INFO ] listening to port 3389 on <IP_ADDRESS>
[20240625-18:06:40] [INFO ] xrdp_listen_pp done

Hi, BTW, you should see the following guide in Detailed xrdp version, build options section of the bug report form. I

Paste the result between ~~~.  Please DO NOT remove ~~~!

It means doing like this. The area inside the green square is "between ~~~".

Thanks for the updated logs.
There appears to be a problem starting the X server. From the sesman log:-
[20240625-17:22:02] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20240625-17:22:12] [WARN ] Timed out waiting for X server on display 10 to startup

Can you try logging in to the machine over ssh and running these commands manually:-
rm -f ~/.xorgxrdp.*.log
/usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log

The command may produce an error, or it may run the X server. If there's an error, please post it. If the X server runs, can you CTRL-C out of it and post the contents of ~/.xorgxrdp.10.log?

@matt335672 Ok, so let me try again. Before doing this, I looked at the answers to the previous questions and tried to reinstall the system with debian 11, and it seems that xrdp works fine.

That's interesting！

Great you've got something working, but if you've re-installed the system we can't debug your original problem.
Are you going to try again with Debian 12?

No problem, I re-installed debian12 using the previous method, the problem still exists
[20240628-18:29:19] [INFO ] starting xrdp-sesman with pid 14516
[20240628-18:31:07] [INFO ] Socket 12: AF_INET6 connection received from ::1 port 42048
[20240628-18:31:07] [INFO ] Terminal Server Users group is disabled, allowing authentication
[20240628-18:31:07] [INFO ] ++ created session (access granted): username lc2024, ip ::ffff:<IP_ADDRESS>:52144 - socket: 12
[20240628-18:31:07] [INFO ] starting Xorg session...
[20240628-18:31:07] [INFO ] Starting session: session_pid 14572, display :10.0, width 1920, height 1080, bpp 24, client ip ::ffff:<IP_ADDRESS>:52144 - socket: 12, user name lc2024
[20240628-18:31:07] [INFO ] [session start] (display 10): calling auth_start_session from pid 14572
[20240628-18:31:07] [ERROR] sesman_data_in: scp_process_msg failed
[20240628-18:31:07] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
[20240628-18:31:07] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20240628-18:31:08] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20240628-18:31:08] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20240628-18:31:08] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20240628-18:31:08] [INFO ] Session started successfully for user lc2024 on display 10
[20240628-18:31:08] [INFO ] Starting the xrdp channel server for display 10
[20240628-18:31:08] [INFO ] Starting the default window manager on display 10: /etc/xrdp/startwm.sh
[20240628-18:31:08] [INFO ] Session in progress on display 10, waiting until the window manager (pid 14573) exits to end the session
[20240628-18:31:09] [WARN ] Window manager (pid 14573, display 10) exited with non-zero exit code 1 and signal 0. This could indicate a window manager config problem
[20240628-18:31:09] [WARN ] Window manager (pid 14573, display 10) exited quickly (1 secs). This could indicate a window manager config problem
[20240628-18:31:09] [INFO ] Calling auth_stop_session and auth_end from pid 14572
[20240628-18:31:09] [INFO ] Terminating X server (pid 14574) on display 10
[20240628-18:31:09] [INFO ] Terminating the xrdp channel server (pid 14577) on display 10
[20240628-18:31:09] [INFO ] X server on display 10 (pid 14574) returned exit code 1 and signal number 0
[20240628-18:31:09] [INFO ] xrdp channel server for display 10 (pid 14577) exit code 0 and signal number 0
[20240628-18:31:09] [INFO ] cleanup_sockets:
[20240628-18:31:09] [INFO ] Process 14572 has exited
[20240628-18:31:09] [INFO ] ++ terminated session:  username lc2024, display :10.0, session_pid 14572, ip ::ffff:<IP_ADDRESS>:52144 - socket: 12

Then, I used the command you provided
rm -f ~/.xorgxrdp.*.log
/usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log

The following results are displayed
X.Org X Server <IP_ADDRESS>
X Protocol Version 11, Revision 0
Current Operating System: Linux raspberrypi 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64
Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=B8:27:EB:89:17:46 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  console=ttyS0,115200 console=tty1 root=PARTUUID=1da6ffa5-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=CN
xorg-server 2:21.1.7-3+rpt2+deb12u7 (https://www.debian.org/support)
Current version of pixman: 0.42.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: ".xorgxrdp.10.log", Time: Fri Jun 28 18:43:34 2024
(++) Using config file: "/etc/X11/xrdp/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xorgxrdpSetup:
xrdpdevSetup:
rdpmousePlug:
rdpkeybPlug:
rdpIdentify:
rdpDriverFunc: op 10
rdpProbe:
rdpProbe: found DRMDevice xorg.conf value [/dev/dri/renderD128]
rdpProbe: found DRI3 xorg.conf value [1]
(EE)
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE) Please also check the log file at ".xorgxrdp.10.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.

Following the prompts, I tried to open.xorgxrdp.10.log，Like the following.
cat ~/.xorgxrdp.10.log

[  1998.289]
X.Org X Server <IP_ADDRESS>
X Protocol Version 11, Revision 0
[  1998.290] Current Operating System: Linux raspberrypi 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64
[  1998.290] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=B8:27:EB:89:17:46 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  console=ttyS0,115200 console=tty1 root=PARTUUID=1da6ffa5-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=CN
[  1998.290] xorg-server 2:21.1.7-3+rpt2+deb12u7 (https://www.debian.org/support)
[  1998.290] Current version of pixman: 0.42.2
[  1998.290]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[  1998.290] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1998.291] (++) Log file: ".xorgxrdp.10.log", Time: Fri Jun 28 18:43:34 2024
[  1998.292] (++) Using config file: "/etc/X11/xrdp/xorg.conf"
[  1998.292] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  1998.292] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1998.293] (**) Option "defaultserverlayout" "X11 Server"
[  1998.293] (**) ServerLayout "X11 Server"
[  1998.293] (**) |-->Screen "Screen (xrdpdev)" (0)
[  1998.293] (**) |   |-->Monitor "Monitor"
[  1998.295] (**) |   |-->Device "Video Card (xrdpdev)"
[  1998.295] (**) |   |-->GPUDevice "kms"
[  1998.295] (**) |-->Input Device "xrdpMouse"
[  1998.295] (**) |-->Input Device "xrdpKeyboard"
[  1998.295] (**) Option "DontVTSwitch" "on"
[  1998.295] (**) Option "AutoAddDevices" "off"
[  1998.295] (**) Not automatically adding devices
[  1998.295] (==) Automatically enabling devices
[  1998.295] (==) Automatically adding GPU devices
[  1998.295] (==) Automatically binding GPU devices
[  1998.295] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  1998.295] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  1998.296]    Entry deleted from font path.
[  1998.296] (==) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/75dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        /usr/share/fonts/X11/75dpi,
        built-ins
[  1998.296] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1998.296] (II) Loader magic: 0x556a0c0ef0
[  1998.296] (II) Module ABI versions:
[  1998.296]    X.Org ANSI C Emulation: 0.4
[  1998.296]    X.Org Video Driver: 25.2
[  1998.296]    X.Org XInput driver : 24.4
[  1998.296]    X.Org Server Extension : 10.0
[  1998.301] (--) using VT number 2

[  1998.301] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[  1998.306] (II) xfree86: Adding drm device (/dev/dri/card0)
[  1998.306] (II) Platform probe for /sys/devices/platform/soc/soc:gpu/drm/card0
[  1998.307] (**) OutputClass "vc4" setting /dev/dri/card0 as PrimaryGPU
[  1998.307] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[  1998.307] (II) LoadModule: "dbe"
[  1998.308] (II) Module "dbe" already built-in
[  1998.308] (II) LoadModule: "ddc"
[  1998.308] (II) Module "ddc" already built-in
[  1998.308] (II) LoadModule: "extmod"
[  1998.308] (II) Module "extmod" already built-in
[  1998.308] (II) LoadModule: "glx"
[  1998.308] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1998.315] (II) Module glx: vendor="X.Org Foundation"
[  1998.315]    compiled for <IP_ADDRESS>, module version = 1.0.0
[  1998.315]    ABI class: X.Org Server Extension, version 10.0
[  1998.315] (II) LoadModule: "int10"
[  1998.315] (II) Loading /usr/lib/xorg/modules/libint10.so
[  1998.316] (II) Module int10: vendor="X.Org Foundation"
[  1998.316]    compiled for <IP_ADDRESS>, module version = 1.0.0
[  1998.316]    ABI class: X.Org Video Driver, version 25.2
[  1998.316] (II) LoadModule: "record"
[  1998.316] (II) Module "record" already built-in
[  1998.316] (II) LoadModule: "vbe"
[  1998.316] (II) Loading /usr/lib/xorg/modules/libint10.so
[  1998.316] (II) Module int10: vendor="X.Org Foundation"
[  1998.316]    compiled for <IP_ADDRESS>, module version = 1.0.0
[  1998.316]    ABI class: X.Org Video Driver, version 25.2
[  1998.316] (II) LoadModule: "glamoregl"
[  1998.317] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[  1998.338] (II) Module glamoregl: vendor="X.Org Foundation"
[  1998.338]    compiled for <IP_ADDRESS>, module version = 1.0.1
[  1998.338]    ABI class: X.Org ANSI C Emulation, version 0.4
[  1998.338] (II) LoadModule: "xorgxrdp"
[  1998.338] (II) Loading /usr/lib/xorg/modules/libxorgxrdp.so
[  1998.339] (II) Module XORGXRDP: vendor="X.Org Foundation"
[  1998.339]    compiled for <IP_ADDRESS>, module version = 0.9.19
[  1998.339]    ABI class: X.Org Video Driver, version 25.2
[  1998.339] xorgxrdpSetup:
[  1998.339] (II) LoadModule: "fb"
[  1998.339] (II) Module "fb" already built-in
[  1998.339] (II) LoadModule: "xrdpdev"
[  1998.340] (II) Loading /usr/lib/xorg/modules/drivers/xrdpdev_drv.so
[  1998.341] (II) Module XRDPDEV: vendor="X.Org Foundation"
[  1998.341]    compiled for <IP_ADDRESS>, module version = 0.9.19
[  1998.341]    ABI class: X.Org Video Driver, version 25.2
[  1998.341] xrdpdevSetup:
[  1998.341] (II) LoadModule: "modesetting"
[  1998.342] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1998.342] (II) Module modesetting: vendor="X.Org Foundation"
[  1998.342]    compiled for <IP_ADDRESS>, module version = 1.21.1
[  1998.342]    Module class: X.Org Video Driver
[  1998.342]    ABI class: X.Org Video Driver, version 25.2
[  1998.342] (II) LoadModule: "xrdpmouse"
[  1998.343] (II) Loading /usr/lib/xorg/modules/input/xrdpmouse_drv.so
[  1998.343] (II) Module XRDPMOUSE: vendor="X.Org Foundation"
[  1998.343]    compiled for <IP_ADDRESS>, module version = 0.9.19
[  1998.343]    Module class: X.Org XInput Driver
[  1998.343]    ABI class: X.Org XInput driver, version 24.4
[  1998.343] rdpmousePlug:
[  1998.343] (II) LoadModule: "xrdpkeyb"
[  1998.344] (II) Loading /usr/lib/xorg/modules/input/xrdpkeyb_drv.so
[  1998.344] (II) Module XRDPKEYB: vendor="X.Org Foundation"
[  1998.344]    compiled for <IP_ADDRESS>, module version = 0.9.19
[  1998.344]    Module class: X.Org XInput Driver
[  1998.344]    ABI class: X.Org XInput driver, version 24.4
[  1998.345] rdpkeybPlug:
[  1998.345] rdpIdentify:
[  1998.345] (II) XRDPDEV: driver for xrdp: XRDPDEV
[  1998.345] rdpDriverFunc: op 10
[  1998.345] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  1998.739] (WW) Falling back to old probe method for XRDPDEV
[  1998.740] rdpProbe:
[  1998.740] (II) Loading sub module "fb"
[  1998.740] (II) LoadModule: "fb"
[  1998.740] (II) Module "fb" already built-in
[  1998.740] rdpProbe: found DRMDevice xorg.conf value [/dev/dri/renderD128]
[  1998.741] rdpProbe: found DRI3 xorg.conf value [1]
[  1998.741] (II) XRDPDEV(0): using default device
[  1998.741] (II) modeset(G0): using drv /dev/dri/card0
[  1998.741] (EE)
Fatal server error:
[  1998.741] (EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
[  1998.741] (EE)
[  1998.742] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[  1998.742] (EE) Please also check the log file at ".xorgxrdp.10.log" for additional information.
[  1998.742] (EE)
[  1998.743] (EE) Server terminated with error (1). Closing log file.
root@raspberrypi:~# ^C
root@raspberrypi:~# cat ~/.xorgxrdp.10.log
[  1998.289]
X.Org X Server <IP_ADDRESS>
X Protocol Version 11, Revision 0
[  1998.290] Current Operating System: Linux raspberrypi 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64
[  1998.290] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=B8:27:EB:89:17:46 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  console=ttyS0,115200 console=tty1 root=PARTUUID=1da6ffa5-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles cfg80211.ieee80211_regdom=CN
[  1998.290] xorg-server 2:21.1.7-3+rpt2+deb12u7 (https://www.debian.org/support)
[  1998.290] Current version of pixman: 0.42.2
[  1998.290]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[  1998.290] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1998.291] (++) Log file: ".xorgxrdp.10.log", Time: Fri Jun 28 18:43:34 2024
[  1998.292] (++) Using config file: "/etc/X11/xrdp/xorg.conf"
[  1998.292] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  1998.292] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1998.293] (**) Option "defaultserverlayout" "X11 Server"
[  1998.293] (**) ServerLayout "X11 Server"
[  1998.293] (**) |-->Screen "Screen (xrdpdev)" (0)
[  1998.293] (**) |   |-->Monitor "Monitor"
[  1998.295] (**) |   |-->Device "Video Card (xrdpdev)"
[  1998.295] (**) |   |-->GPUDevice "kms"
[  1998.295] (**) |-->Input Device "xrdpMouse"
[  1998.295] (**) |-->Input Device "xrdpKeyboard"
[  1998.295] (**) Option "DontVTSwitch" "on"
[  1998.295] (**) Option "AutoAddDevices" "off"
[  1998.295] (**) Not automatically adding devices
[  1998.295] (==) Automatically enabling devices
[  1998.295] (==) Automatically adding GPU devices
[  1998.295] (==) Automatically binding GPU devices
[  1998.295] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  1998.295] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  1998.296]    Entry deleted from font path.
[  1998.296] (==) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/75dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        /usr/share/fonts/X11/75dpi,
        built-ins
[  1998.296] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1998.296] (II) Loader magic: 0x556a0c0ef0
[  1998.296] (II) Module ABI versions:
[  1998.296]    X.Org ANSI C Emulation: 0.4
[  1998.296]    X.Org Video Driver: 25.2
[  1998.296]    X.Org XInput driver : 24.4
[  1998.296]    X.Org Server Extension : 10.0
[  1998.301] (--) using VT number 2

[  1998.301] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[  1998.306] (II) xfree86: Adding drm device (/dev/dri/card0)
[  1998.306] (II) Platform probe for /sys/devices/platform/soc/soc:gpu/drm/card0
[  1998.307] (**) OutputClass "vc4" setting /dev/dri/card0 as PrimaryGPU
[  1998.307] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[  1998.307] (II) LoadModule: "dbe"
[  1998.308] (II) Module "dbe" already built-in
[  1998.308] (II) LoadModule: "ddc"
[  1998.308] (II) Module "ddc" already built-in
[  1998.308] (II) LoadModule: "extmod"
[  1998.308] (II) Module "extmod" already built-in
[  1998.308] (II) LoadModule: "glx"
[  1998.308] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1998.315] (II) Module glx: vendor="X.Org Foundation"
[  1998.315]    compiled for <IP_ADDRESS>, module version = 1.0.0
[  1998.315]    ABI class: X.Org Server Extension, version 10.0
[  1998.315] (II) LoadModule: "int10"
[  1998.315] (II) Loading /usr/lib/xorg/modules/libint10.so
[  1998.316] (II) Module int10: vendor="X.Org Foundation"
[  1998.316]    compiled for <IP_ADDRESS>, module version = 1.0.0
[  1998.316]    ABI class: X.Org Video Driver, version 25.2
[  1998.316] (II) LoadModule: "record"
[  1998.316] (II) Module "record" already built-in
[  1998.316] (II) LoadModule: "vbe"
[  1998.316] (II) Loading /usr/lib/xorg/modules/libint10.so
[  1998.316] (II) Module int10: vendor="X.Org Foundation"
[  1998.316]    compiled for <IP_ADDRESS>, module version = 1.0.0
[  1998.316]    ABI class: X.Org Video Driver, version 25.2
[  1998.316] (II) LoadModule: "glamoregl"
[  1998.317] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[  1998.338] (II) Module glamoregl: vendor="X.Org Foundation"
[  1998.338]    compiled for <IP_ADDRESS>, module version = 1.0.1
[  1998.338]    ABI class: X.Org ANSI C Emulation, version 0.4
[  1998.338] (II) LoadModule: "xorgxrdp"
[  1998.338] (II) Loading /usr/lib/xorg/modules/libxorgxrdp.so
[  1998.339] (II) Module XORGXRDP: vendor="X.Org Foundation"
[  1998.339]    compiled for <IP_ADDRESS>, module version = 0.9.19
[  1998.339]    ABI class: X.Org Video Driver, version 25.2
[  1998.339] xorgxrdpSetup:
[  1998.339] (II) LoadModule: "fb"
[  1998.339] (II) Module "fb" already built-in
[  1998.339] (II) LoadModule: "xrdpdev"
[  1998.340] (II) Loading /usr/lib/xorg/modules/drivers/xrdpdev_drv.so
[  1998.341] (II) Module XRDPDEV: vendor="X.Org Foundation"
[  1998.341]    compiled for <IP_ADDRESS>, module version = 0.9.19
[  1998.341]    ABI class: X.Org Video Driver, version 25.2
[  1998.341] xrdpdevSetup:
[  1998.341] (II) LoadModule: "modesetting"
[  1998.342] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1998.342] (II) Module modesetting: vendor="X.Org Foundation"
[  1998.342]    compiled for <IP_ADDRESS>, module version = 1.21.1
[  1998.342]    Module class: X.Org Video Driver
[  1998.342]    ABI class: X.Org Video Driver, version 25.2
[  1998.342] (II) LoadModule: "xrdpmouse"
[  1998.343] (II) Loading /usr/lib/xorg/modules/input/xrdpmouse_drv.so
[  1998.343] (II) Module XRDPMOUSE: vendor="X.Org Foundation"
[  1998.343]    compiled for <IP_ADDRESS>, module version = 0.9.19
[  1998.343]    Module class: X.Org XInput Driver
[  1998.343]    ABI class: X.Org XInput driver, version 24.4
[  1998.343] rdpmousePlug:
[  1998.343] (II) LoadModule: "xrdpkeyb"
[  1998.344] (II) Loading /usr/lib/xorg/modules/input/xrdpkeyb_drv.so
[  1998.344] (II) Module XRDPKEYB: vendor="X.Org Foundation"
[  1998.344]    compiled for <IP_ADDRESS>, module version = 0.9.19
[  1998.344]    Module class: X.Org XInput Driver
[  1998.344]    ABI class: X.Org XInput driver, version 24.4
[  1998.345] rdpkeybPlug:
[  1998.345] rdpIdentify:
[  1998.345] (II) XRDPDEV: driver for xrdp: XRDPDEV
[  1998.345] rdpDriverFunc: op 10
[  1998.345] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  1998.739] (WW) Falling back to old probe method for XRDPDEV
[  1998.740] rdpProbe:
[  1998.740] (II) Loading sub module "fb"
[  1998.740] (II) LoadModule: "fb"
[  1998.740] (II) Module "fb" already built-in
[  1998.740] rdpProbe: found DRMDevice xorg.conf value [/dev/dri/renderD128]
[  1998.741] rdpProbe: found DRI3 xorg.conf value [1]
[  1998.741] (II) XRDPDEV(0): using default device
[  1998.741] (II) modeset(G0): using drv /dev/dri/card0
[  1998.741] (EE)
Fatal server error:
[  1998.741] (EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
[  1998.741] (EE)
[  1998.742] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[  1998.742] (EE) Please also check the log file at ".xorgxrdp.10.log" for additional information.
[  1998.742] (EE)
[  1998.743] (EE) Server terminated with error (1). Closing log file.

This looks to me like you're pulling in hardware devices when you don't need to. It was fixed in neutrinolabs/xorgxrdp#241 which isn't in your Debian 12 build yet.
Edit /etc/X11/xrdp/xorg.conf and make the following changes:-

After the line Option "AutoAddDevices" "off" add a new line containing Option "AutoAddGPU" "off"
After the line Device "Video Card (xrdpdev)", add a new line containing GPUDevice ""

These are the same changes in commit neutrinolabs/xorgxrdp@b7002eee91b104dee8d9b9479e306419eaff5b8d, if you'd rather work from that.
Give that a go and report back

2. GPUDevice ""

On Arch Linux it is not working.

I'm closing this as the OP hasn't responded in 3 weeks.
@D3vil0p3r - you've already raised your own issue in #3176. We can deal with yours separately.

After lot of research I came to this thread and found the solution to my problems, I'm so grateful!!! I can confirm that https://github.com/neutrinolabs/xrdp/issues/3140#issuecomment-2199593196 fixed this exact issue on Raspios Debian 12 (bookworm)

Thanks @eberzosa
I've added this section to the FAQ as I think this really qualifies as an FAQ by now.

This looks to me like you're pulling in hardware devices when you don't need to. It was fixed in neutrinolabs/xorgxrdp#241 which isn't in your Debian 12 build yet.
Edit /etc/X11/xrdp/xorg.conf and make the following changes:-

After the line Option "AutoAddDevices" "off" add a new line containing Option "AutoAddGPU" "off"
After the line Device "Video Card (xrdpdev)", add a new line containing GPUDevice ""

These are the same changes in commit neutrinolabs/xorgxrdp@b7002ee, if you'd rather work from that.
Give that a go and report back

That's works for me. Zorin OS/Ubuntu

This looks to me like you're pulling in hardware devices when you don't need to. It was fixed in neutrinolabs/xorgxrdp#241 which isn't in your Debian 12 build yet.
Edit /etc/X11/xrdp/xorg.conf and make the following changes:-

After the line Option "AutoAddDevices" "off" add a new line containing Option "AutoAddGPU" "off"
After the line Device "Video Card (xrdpdev)", add a new line containing GPUDevice ""

These are the same changes in commit neutrinolabs/xorgxrdp@b7002ee, if you'd rather work from that.
Give that a go and report back

That's works for me. Zorin OS/Ubuntu

Thank you! I've spent hours working on this issue, tried a ton of old "fixes" reimaged my pi etc. and nothing worked until this. I've got xrdp working on the windows app on macOS 15.2 with no problems now.


Add client action

This PR adds github action checks for the following:

Generated client
Generated manifests
Generated code.

This should help ensure that our artifacts are always up to date.

I'll work on consolidating into one action.

Consolidated.

/lgtm
We could also add a verification step that check go mod tidy induces no diff.

/lgtm
/approve


Capture phase implemented for displayObject's events.

Hi @jgranick!
I implemented a capture phase for all events which are fired from/through display objects, not only for ADDED_TO_STAGE and REMOVED_FROM_STAGE. Finally, the openfl events work exactly the same as flash events through all event phases.
Please check the pull request and let me know if there are any issues.
I could provide flash and openfl test example if you like to test it.
Best,
Nenad

Merged! Thank you for all the testing and work that went into this :+1:


improve social icons , navbar and bugs fix

Issues Identification
Closes: #565
Description
Summary
Applied styling on social media Icons and changed social media icons with a hover effect , fixed all the CSS bugs and improve the navbar
Details
Improvements:

Optimized social media icons: Enhanced the social media icons and its animation on the Testimonial , about, community_suport, contact, course, course_details, courses, contributor, privacy, terms, feedback, index, and projects pages to improve user experience.

Revamped Social media icons Design: Redesigned the Social media icons with modern CSS styling to enhance visual appeal.

Update StyleSheet: update CSS file to enhance styling and functionality, ensuring better code organization and maintainability.

How Has This Been Tested?
The program was tested locally on a machine using the Chrome browser. To verify the changes, the website was loaded after the modifications were made. This involved manually inspecting the visual elements and functionally testing various user interactions to ensure the changes were implemented correctly.
Types of Changes
Please check the boxes that apply

[X] Bugfix (non-breaking change that fixes an issue)
[X] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Please check the boxes that apply

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] My changes do not break the current system and pass all existing test cases
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes

Screenshots
Before
https://github.com/user-attachments/assets/46309ea0-0d6c-49f1-97cf-8fe853c318c8
After
After fixing the Navbar

After improving social media Icons
https://github.com/user-attachments/assets/4977edf7-8c15-4b8e-bd66-3b42315b4e9a
Additional Information
@vivekvardhan2810 please merge this before someone edit the codebase.

@vivekvardhan2810 please tell everyone to stop using inline styling because inline styling is overtaking on vanilla CSS files.

Okay, i will tell @VidhanThakur09 anyways thanks for pointing out.

Welcome


how to solve this error

file:///E:/bookcars/api/server.js:18
const DB_SSL = process.env.BC_DB_SSL.toLowerCase() === 'true'
^
TypeError: Cannot read properties of undefined (reading 'toLowerCase')
at file:///E:/bookcars/api/server.js:18:38
at ModuleJob.run (node:internal/modules/esm/module_job:194:25)
Node.js v18.16.1
[nodemon] app crashed - waiting for file changes before starting...

First, check out the prerequisites.
Then, you need to create api/.env file with the following content:
NODE_ENV=development
BC_PORT=4002
BC_HTTPS=false
BC_PRIVATE_KEY=/etc/ssl/bookcars.com.key
BC_CERTIFICATE=/etc/ssl/bookcars.com.crt
BC_DB_HOST=<IP_ADDRESS>
BC_DB_PORT=27017
BC_DB_SSL=false
BC_DB_SSL_KEY=/etc/ssl/bookcars.com.key
BC_DB_SSL_CERT=/etc/ssl/bookcars.com.crt
BC_DB_SSL_CA=/etc/ssl/bookcars.com.ca.pem
BC_DB_DEBUG=false
BC_DB_APP_NAME=bookcars
BC_DB_AUTH_SOURCE=admin
BC_DB_USERNAME=admin
BC_DB_PASSWORD=PASSWORD
BC_DB_NAME=bookcars
BC_JWT_SECRET=JWT_SECRET
BC_JWT_EXPIRE_AT=86400
BC_TOKEN_EXPIRE_AT=86400
BC_SMTP_HOST=in-v3.mailjet.com
BC_SMTP_PORT=587
BC_SMTP_USER=USER
BC_SMTP_PASS=PASSWORD
<EMAIL_ADDRESS><EMAIL_ADDRESS>BC_CDN_USERS=/var/www/cdn/bookcars/users
BC_CDN_TEMP_USERS=/var/www/cdn/bookcars/temp/users
BC_CDN_CARS=/var/www/cdn/bookcars/cars
BC_CDN_TEMP_CARS=/var/www/cdn/bookcars/temp/cars
BC_DEFAULT_LANGUAGE=en
BC_BACKEND_HOST=http://localhost:3001/
BC_FRONTEND_HOST=http://localhost:3002/
BC_MINIMUM_AGE=21
BC_EXPO_ACCESS_TOKEN=EXPO_ACCESS_TOKEN

Set the following options:
BC_DB_PASSWORD=PASSWORD
BC_JWT_SECRET=JWT_SECRET
BC_SMTP_HOST=in-v3.mailjet.com
BC_SMTP_PORT=587
BC_SMTP_USER=USER
BC_SMTP_PASS=PASSWORD
<EMAIL_ADDRESS><EMAIL_ADDRESS>
Replace PASSWORD with a strong password of your choice and JWT_SECRET with a secret token. Finally, set the SMTP options. SMTP options are necessary for sign up.
If you are on Windows, you need to install IIS and update these settings as well:
BC_CDN_USERS=/var/www/cdn/bookcars/users
BC_CDN_TEMP_USERS=/var/www/cdn/bookcars/temp/users
BC_CDN_CARS=/var/www/cdn/bookcars/cars
BC_CDN_TEMP_CARS=/var/www/cdn/bookcars/temp/cars

Check out step 6 on this documentation.
If you want to enable push notifications in the mobile app, follow these instructions and set the following option:
BC_EXPO_ACCESS_TOKEN=EXPO_ACCESS_TOKEN

Run the api:
cd ./api
npm install
npm run dev

For the backend and the frontend, you need to create .env file as well. You can find the instructions here.

I am trying to run the android app should I do the same and thank u so much
for replying
On Sun, 20 Aug, 2023, 8:13 pm Akram El Assas, @.***>
wrote:

First, check out the prerequisites
https://github.com/aelassas/bookcars/wiki/Run-from-Source#prerequisites.
Then, you need to create api/.env file with the following content:
NODE_ENV=development
BC_PORT=4002
BC_HTTPS=false
BC_PRIVATE_KEY=/etc/ssl/bookcars.com.key
BC_CERTIFICATE=/etc/ssl/bookcars.com.crt
BC_DB_HOST=<IP_ADDRESS>
BC_DB_PORT=27017
BC_DB_SSL=false
BC_DB_SSL_KEY=/etc/ssl/bookcars.com.key
BC_DB_SSL_CERT=/etc/ssl/bookcars.com.crt
BC_DB_SSL_CA=/etc/ssl/bookcars.com.ca.pem
BC_DB_DEBUG=false
BC_DB_APP_NAME=bookcars
BC_DB_AUTH_SOURCE=admin
BC_DB_USERNAME=admin
BC_DB_PASSWORD=PASSWORD
BC_DB_NAME=bookcars
BC_JWT_SECRET=JWT_SECRET
BC_JWT_EXPIRE_AT=86400
BC_TOKEN_EXPIRE_AT=86400
BC_SMTP_HOST=in-v3.mailjet.com
BC_SMTP_PORT=587
BC_SMTP_USER=USER
BC_SMTP_PASS=PASSWORD
@.***
@.***
BC_CDN_USERS=/var/www/cdn/bookcars/users
BC_CDN_TEMP_USERS=/var/www/cdn/bookcars/temp/users
BC_CDN_CARS=/var/www/cdn/bookcars/cars
BC_CDN_TEMP_CARS=/var/www/cdn/bookcars/temp/cars
BC_DEFAULT_LANGUAGE=en
BC_BACKEND_HOST=http://localhost:3001/
BC_FRONTEND_HOST=http://localhost:3002/
BC_MINIMUM_AGE=21
BC_EXPO_ACCESS_TOKEN=EXPO_ACCESS_TOKEN http://localhost:3001/BC_FRONTEND_HOST=http://localhost:3002/BC_MINIMUM_AGE=21BC_EXPO_ACCESS_TOKEN=EXPO_ACCESS_TOKEN
Set the following options:
BC_DB_PASSWORD=PASSWORD
BC_JWT_SECRET=JWT_SECRET
BC_SMTP_HOST=in-v3.mailjet.com
BC_SMTP_PORT=587
BC_SMTP_USER=USER
BC_SMTP_PASS=PASSWORD
@.***
@.***
Replace PASSWORD with a strong password of your choice and JWT_SECRET
with a secret token. Finally, set the SMTP options. SMTP options are
necessary for sign up.
If you are on Windows, you need to install IIS and update these settings
as well:
BC_CDN_USERS=/var/www/cdn/bookcars/users
BC_CDN_TEMP_USERS=/var/www/cdn/bookcars/temp/users
BC_CDN_CARS=/var/www/cdn/bookcars/cars
BC_CDN_TEMP_CARS=/var/www/cdn/bookcars/temp/cars
Check out step 6 on this documentation
https://github.com/aelassas/bookcars/wiki/Run-from-Source.
If you want to enable push notifications in the mobile app, follow these
instructions
https://github.com/aelassas/bookcars/wiki/Build-Mobile-App#configuration
and set the following option:
BC_EXPO_ACCESS_TOKEN=EXPO_ACCESS_TOKEN
Run the api:
cd ./api
npm install
npm run dev
For the backend and the frontend, you need to create .env file as well.
You can find the instructions here
https://github.com/aelassas/bookcars/wiki/Run-from-Source.
—
Reply to this email directly, view it on GitHub
https://github.com/aelassas/bookcars/issues/42#issuecomment-1685302462,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5VNXUKLNS2V2HAU2DMIMKTXWIPAZANCNFSM6AAAAAA3XKFC5A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

You can find the instructions on how to run the mobile app here.


Raise an error for duplicate lexical variable names (fixes #487)

This implements the static errors reported in #487, specified here:

It is a Syntax Error if the LexicallyDeclaredNames of StatementList contains any duplicate entries.

It is a Syntax Error if any element of the LexicallyDeclaredNames of StatementList also occurs in the VarDeclaredNames of StatementList.

In other words, if a let/const variable is declared in the same scope as another variable with the same name, a parsing error should be thrown. This is implemented with the following steps:

When entering a function scope, create an empty set of var-declared names
When entering a block scope, create a new empty set of lexically-declared names. Additionally, push the current set of var-declared names, and work with a new empty set.
When exiting a block scope, merge the set of var-declared names from the block with the set of var-declared names from the parent scope.
When parsing a binding pattern (e.g. a variable declaration or function parameters), check if the bound identifier clashes with any lexically-declared names (if the bound identifier is non-lexical), or any variable names at all (if the bound identifier is lexical). If so, raise a parsing error. Otherwise, add it to the current lexically-declared name set or var-declared name set as appropriate.

The merging behavior for var-declared names in the third bullet-point is necessary due to how var scoping works. For example, this should be a syntax error:
{
  var foo = 1;
}

let foo = 1;

But this should not be a syntax error:
{
  var foo = 1;
  {
    let foo = 1;
  }
}

This is my first contribution to Acorn, so please review thoroughly.

Thanks for working on this! It looks good, on the whole, but I added a few comments.

Thanks for the feedback. I changed the Sets to objects -- I'll look at the parseFunctionBody code tomorrow to see if I can find a good solution to address your other comments.

I updated the PR to check for parameter/variable clashes in the same checkLVal call as the check for parameter/parameter clashes.

This example currently fails:
let x = 1
function foo(x) {}

Because the parser won't let us use x as parameter when it exists in the outer scope.
Another problem occurs here:
for (let i = 1;;) {}
for (let i = 2;;) {}

It doesn't seem to treat the initializers for a for loop as being part of the loop's scope, so these will be considered to clash in the outer scope.
An even weirder failure is this one:
class Foo {
  method(name) {}
  method2() { let name }
}

For some reason the first method's parameter is considered to clash with the second method's local variable.
These are from running the parser on Acorn's src/*.js. If you could run a few real-world ES6 codebases through it as a test, that might turn up other issues.

Also, could you move the tests into tests-harmony.js? That's where we put ES6-related tests (though the naming of those files could be clearer).
And thanks for your work on this!

@marijnh The last 7 tests in this PR are actually valid JS code and should throw.

@zubuzon Yes, that's understood. They are also specified to succeed, aren't they?

@marijnh Yes. They should parse normally, but two of them should throw in strict mode.  Regarding this PR. The best approach is to have it's own scope tracker to handle this if you want to catch all TC39 early-errors.
And also have a look at <IP_ADDRESS>.1 ParseModule   and 15.1.19 ParseScript and study what you can read there about early errors..

I think I fixed all the issues that have been brought up. I also ran the ESLint unit tests with this version of Acorn -- 8 errors occurred, but all of them appear to be correct behavior.
There's one last thing to address, relating to variables in catch clauses. This will depend on whether we implement Annex B semantics.
From 13.5.1:

It is a Syntax Error if any element of the BoundNames of CatchParameter also occurs in the VarDeclaredNames of Block.

However, B.3.5 overrides this clause with

It is a Syntax Error if any element of the BoundNames of CatchParameter also occurs in the VarDeclaredNames of Block unless CatchParameter is CatchParameter : BindingIdentifier and that element is only bound by a VariableStatement, the VariableDeclarationList of a for statement, the ForBinding of a for-in statement, or the BindingIdentifier of a for-in statement.

In other words, the following examples are valid if we implement the Annex B semantics, and invalid if we don't implement the Annex B semantics:
try {} catch (foo) { var foo = 1; }
try {} catch (foo) { for (var foo = 1;;); }
try {} catch (foo) { for (var foo in bar); }
try {} catch (foo) { for (var [foo] in bar); }

The following examples are invalid regardless of whether we implement Annex B semantics:
try {} catch ([foo]) { var foo = 1; }
try {} catch ({ foo }) { var foo = 1; }
try {} catch (foo) { let foo = 1; }
try {} catch (foo) { for (var foo of bar); }
try {} catch ({ a: foo, b: foo }) {}

The following examples are valid regardless of whether we implement Annex B semantics:
try {} catch (foo) {} let foo = 1;

This one still fails, which I think isn't accurate (browsers accept it):
'use strict'
function foo() {
  let foo
}

@not-an-aardvark Isn't this two valid JS if you implement Annex B semantics?  You mention they should fail.
try {} catch ([foo]) { var foo = 1; }
try {} catch ({ foo }) { var foo = 1; }

@zubuzon

@not-an-aardvark Isn't this two valid JS if you implement Annex B semantics? You mention they should fail.

try {} catch ([foo]) { var foo = 1; }
try {} catch ({ foo }) { var foo = 1; }

No, because CatchParameter is not CatchParameter : BindingIdentifier in those examples -- instead it's CatchParameter : ArrayAssignmentPattern and CatchParameter : ObjectAssignmentPattern.

Looks good now! I ran it on a few sizeable ES6 codebases and didn't get any more spurious errors. I've merged it as 53dfd4b.

Thanks!
Sorry, I should have clarified that I was waiting for an answer to the Annex B question to fix the try syntax before this PR was merged. The syntax check is currently incorrect in this case:
try {} catch (foo) {} let foo = 1;

This is valid syntax regardless of whether Annex B is implemented, but Acorn currently reports an error for it. Essentially, Acorn currently treats catch parameters like this:
try {} catch (foo) { /* ... */ }

// is treated like

try {} catch (_) { var foo; }

This is not quite compliant with either the standard syntax or the Annex B version. If you let me know which version to implement, I can make another PR to handle these in a standard way. Alternatively, we can remove duplicate-checking for catch parameters and leave that as a separate issue, since they seem to be independent from duplicate-checking for variables.
If there isn't much ecosystem impact from using the standard, non-Annex-B semantics, I personally think that would be the simplest option.

Oh, sorry, I assumed that was already implemented. I don't have a strong preference about whether Annex B is implemented -- I agree that it probably won't have a big impact.

Ok, I'll implement the non-Annex-B semantics and make a new PR.


Write docs for functions in Mailer using macro

Hi!
I found #939 and decide to check if I could make my first contribution, at least writing docs, so here here it is!
With this PR I write basic documentation for the functions inside the __using__ defmacro:

deliver/2
deliver!/2
deliver_many/2

I know that sometimes functions inside macro are not documented, however, I think it may be useful when the user generates the documentation for its project or even if the user has an editor that shows this docs (at least in my VSCode with ElixirLS in an test project doesn't shows the docs, but I imagine there is some way).
I can't say it fix #939, because I think the issue it is a bit in the wrong direction because deliver!/2 won't be never in Swoosh documentation because it is implemented outside the __using__.
Well, hope this little contribution may be useful!

I can't say it fix #939, because I think the issue it is a bit in the wrong direction because deliver!/2 won't be never in Swoosh documentation because it is implemented outside the __using__.

Yeah as far as I'm concerned this part is a wont fix.

Thanks. close #939


Update extensions versions

Updated extension versions of ServiceBus, EventGrid, and EventHubs.
Issue describing the changes in this PR
resolves #863
Pull request checklist

[x] My changes do not require documentation changes

[ ] Otherwise: Documentation issue linked to PR

[ ] My changes should not be added to the release notes for the next release

[x] Otherwise: I've added my notes to release_notes.md

[ ] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[x] I have added all required tests (Unit tests, E2E tests)

Additional information
Additional PR information

/check-enforcer evaluate

Microsoft.Azure.Functions.Worker.Extensions.ServiceBus version 5.4.0 is now available in nuget gallery.

Microsoft.Azure.Functions.Worker.Extensions.EventHubs 5.1.0 is now available in nuget gallery.


feat(rainbowkit): :arrow_up: upgrade dependencies

Some random guy who shall not be named wanted to update the dependencies.
he fucked around, now he's finding out. intense music
Join him on his journey to madness MUAHAHAHA
sound of fire and screaming

this is abandoned. We've switched to NextJS.


Just build go 1.22.6 from our dockerfile (copied from oficial dockerfile)

Upgrading go/libs to see if it helps with https://github.com/river-build/river/issues/640

👍


Study the interactions with Auth0

I don't think I can do this unless the API us up and running

This is too much for this project


[SPARK-45137][CONNECT] Support map/array parameters in parameterized sql()

What changes were proposed in this pull request?
In the PR, I propose to extend the proto protocol, and add two more fields to SqlCommand: arguments and pos_arguments. This should allow to construct arrays/maps/structs by the map(), array(), struct(), map_from_arrays() and map_from_entries(), and pass them to sql() as arguments.
Why are the changes needed?
To fix the issue demonstrated by the example:
spark.sql("select element_at(?, 1)", Array(array(lit(1)))).collect()
java.lang.UnsupportedOperationException: literal unresolved_function {
[info]   function_name: "array"
[info]   arguments {
[info]     literal {
[info]       integer: 1
[info]     }
[info]   }
[info] }
[info]  not supported (yet).

Note: The PR https://github.com/apache/spark/pull/42752 supported constructors, and this PR extends the feature on Scala connect client.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
By new checks:
$ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *.ClientE2ETestSuite"

Was this patch authored or co-authored using generative AI tooling?
No.

Merging to master. Thank you, @HyukjinKwon and @cloud-fan for review.


Example invalid

What does the example in this article have to do with Get-SPEnterpriseSearchMetadataCrawledProperty?
[Enter feedback here]

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

ID: 60645b5d-fac6-4f02-1cd8-c76ceda53cdb
Version Independent ID: acea67c9-6ea9-a577-510b-694f7d2e6f87
Content: Get-SPEnterpriseSearchMetadataCrawledProperty (sharepoint-server)
Content Source: sharepoint/sharepoint-server-ps/sharepoint-server/Get-SPEnterpriseSearchMetadataCrawledProperty.md
Product: sharepoint-server-itpro
GitHub Login: @Techwriter40
Microsoft Alias: pamgreen

Hello @SharePointBlackBelt how are you?
Just to confirm, do you refer to this example?
$ssa = Get-SPEnterpriseSearchServiceApplication
$cat = Get-SPEnterpriseSearchMetadataCategory -SearchApplication $ssa -Identity People
Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Category $cat -Limit 1
I tested it and it does what the description says, please kindly let me know if I understood you correctly,
Thanks

Yes, you are right. I should have phrased this better... the problem is that it does not show what the crawled property mapping is, and the article doesn't mention how to get the mapping.
For example, running something like:
$ssa = Get-SPEnterpriseSearchServiceApplication
Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Category $cat -Name ows_Proposal_x0020_Section
Returns:
Name               : ows_Proposal_x0020_Section
CategoryName       : SharePoint
Propset            : 00130329-0000-0130-c000-000000131346
IsMappedToContents : True
VariantType        : 0
showing it's mapped, but mapped to what? Maybe the article could be improved with additional examples.

Hello @SharePointBlackBelt Vincent,

the problem is that it does not show what the crawled property mapping is, and the article doesn't mention how to get the mapping

I understand what you were looking for now, thanks.
Is this method, of the resulting CrawledProperty object, the mapping you are looking for?
https://docs.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/ms562672(v=office.14)

Oh yeah, that works. Thank you. Maybe this example, or one similar could be added to the article.
$crawledprop = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $ssa -Category $cat -Name ows_Proposal_x0020_Section
$crawledprop.GetMappedManagedProperties()
Name                 PID      ManagedType  EnabledForScoping  EqualityMatchOnly

ProposalSection      1012     Text         False              False

@SharePointBlackBelt
Glad to hear Vincent.
Yes will propose to add an example in line with the first example.
Thank you


Fix for attempt counter

The attempt counter is now being persisted as part of the job data, but is not being retrieved correctly from the job. The end result is that the number of attempts is always zero.

On which version of Laravel did you test your fixes?

5.2.39

Okay. Already in 5.2 release. Thanks!


chore Fix JAVA_OPTS in start_be.sh

Proposed changes
Issue Number: close #19263
Problem summary
We should set -XX:-MaxFDLimit on macOS if we enable java support for BE otherwise BE may fail to start up.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.76 seconds
stream load tsv:          424 seconds loaded<PHONE_NUMBER>9 Bytes, about 168 MB/s
stream load json:         24 seconds loaded<PHONE_NUMBER> Bytes, about 93 MB/s
stream load orc:          60 seconds loaded<PHONE_NUMBER> Bytes, about 17 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230504095845_clickbench_pr_138141.html

run buildall

run p0

run buildall


Devices with webcams should allow to stream their video to Device Cloudlet UI

If managed device has webcam, we should allow to use webcam->websocket route from @gautric blog post. That should allow us to stream real time video from the devices using the device management UI.

an low level implementation here
http://gautric.github.io/blog/2015/10/23/rhiot-camel-webcam-websocket-macbookpro.html

What need to enable device to report their webcam capabilities. LWM2M client would be great for that. That would allow us to ask each device if it provides webcam or not.
Then, we should provide some way to tell the device to turn on the streaming to the Rhiot Cloud.
So I would like to have the video [on|of] button near the devices equiped with webcams on device management UI. Default to off.


Google Cloud Translation API integration

I needed to translate my website to a new language, which was not supported by Deepl. Free Google API was constantly giving timeouts, so I implemented Google Cloud API plugin, which worked great and by the way, it's also free up to a certain usage threshold.

Hi thanks for the PR! Really appreciate it. May you please write an additional paragraph in the readme for the price? You wrote Free: "Yes*". But what does that asterisk mean?

hi @ben182, their pricing scheme is not totally clear for me.
They charge per character. I translated around 1000 messages and I paid for it 0,44€.
you can find the pricing details:
https://cloud.google.com/translate/pricing
I updated the readme and I replaced Free: "Yes*" with "No".


Usage stats issue

On the Usage stats page, there seems to be an issue with the generation of the filtered data. After selecting desired options (user & a date range), clicking Go produces no results. The buttons (Go, Download) don't seem to lead to any action. I've tried on multiple browsers (Safari - I'm on a mac), Firefox, and Chrome with the same result.
I'm simply trying to pull a list of our current users (which I used to do with the API that I currently miss dearly).

Hi @cmalinowski3,
Can you please try again? There is a security setting that was missing from your account that allows this information to be run. I just added it for your account.
Also, as an FYI. The Admin Features -> Users menu will give you a complete list of your institution's users which you may also find useful.

@cmalinowski3 - I just want to add that we will soon provide complete reports of users and plans from the dashboard "Download" buttons. This is a high priority enhancement post MVP, it just requires some more work on the Roadmap code. We will also provide a report of plans created per template. Let us know if there's anything else you'd like to have on the Usage dashboard.

Such quick turnaround! Thanks for the responses.
@briri I just tried and successfully ran the report. Thank you so much. I had seen the option for the users list under Admin Features, but I wanted to be able to extract a list of emails in an easy way. I thought I might have that in the download of the data for the usage statistics, but I see now that isn't the case. It sounds like the upcoming reports that @stephaniesimms mentions will get me there though.

@stephaniesimms I would also add that we find it useful to be able to know when an individual user created their account. Sometimes we see a surge of account creations from admins in a specific department, for example. That helps us to target certain outreach.
I know in the Users list, we can sort by Last Activity, which is useful, but that account creation date also has value.

thanks for this feedback @cmalinowski3 - i created an issue in the main roadmap code repository to add the Created date column back to the Users table. we will address this in the coming weeks.
https://github.com/DMPRoadmap/roadmap/issues/1248


Fix topics decoding to work with zero values

Because +cat doesn't care to left-shift if you append a zero value.
Previously:
> (decode-topics:rpc:ethereum ~[0x0 0x1] ~[%uint %uint])
[0 1]
> (decode-topics:rpc:ethereum ~[0x1 0x0] ~[%uint %uint])
[0 1]

Now:
> (decode-topics:rpc:ethereum ~[0x0 0x1] ~[%uint %uint])
[0 1]
> (decode-topics:rpc:ethereum ~[0x1 0x0] ~[%uint %uint])
[1 0]

I think ++can is the canonical way to assemble fixed-width blocks?
On Wednesday, 6 March 2019, Philip Monk<EMAIL_ADDRESS>wrote:

@philipcmonk approved this pull request.
Indeed, don't use (cat a b c) if you want (add b (lsh a 1 c))!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/1098#pullrequestreview-211566654, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhrzaSvw_Lvn9DtWZauGpQWaT4DaTks5vUHDOgaJpZM4bhNup
.

Ah, yes, ++can is better.

Or actually ++rep, if they're all just lsh 1?
I'm also somewhat confused what the surrounding code is doing: is render-hex-bytes literally just uncurried x-co:co? In that case, it's taking a list of @uxI(uint256), printing them as a tape of hex characters, converting that into a cord of hex characters, and then parsing back from hex into a tuple of the exact same numbers??

Yeah it looks like every single call to decode-topics accepts ~[%uint], ~[%uint %uint], or ~[%uint %address] where %address is an alias for %uint. While I'm all for future compatibility, I feel like in this case it would be reasonable to remove the function in question entirely and replace it with a series of length checks: ?>  ?=([who=@ wer=address ~] topics.log) and similar.
(I'm also not sure why azimuth-events is a core instead of a (map @uxI term) which you could apply to event.log once and then idiomatically ?-. Or well, not literally term, %- :~ my result so that you can actually catch typoed(as currently) or unhandled(but known) event types)

…why is the compiler allowing lone terms in a $% o.o https://github.com/urbit/arvo/blob/master/sys/zuse.hoon#L7608-L7617
(I think the rune you technically want here is $?, possibly with a $@ split to $% tho tbh giving the commented static/dynamic precedence makes sense)

I completely forgot about rep. Serious tunnel-vision going on here.
Thanks for the feedback @ohAitch! I have touched up the logic here to not do superfluous @t <--> (list @) conversions.
Found an issue in the encoding logic while I was trying to test my changes there. We probably want more thorough tests for encoding, and tests at all for decoding. Official test data (which the current tests are sourced from) don't reach further than simple cases. Currently have a Q out to Ethereum core devs for recommended test data, but if that comes up blank, I might just pull in these.
Tests aside, this PR is ready for re-review.


Add code of conduct md

I know it's a basic issue, but i want to start from somewhere, i am new to the platform and want to contribute. If needed please assign this issue to me under gssoc.
A Code of Conduct is essential for open-source projects because it sets clear expectations for behavior, ensuring a respectful and inclusive environment. It helps prevent harassment and discrimination, making the community welcoming and safe for everyone. By outlining consequences for unacceptable behavior, it maintains a positive and collaborative atmosphere, which is crucial for the project's success and sustainability.

@jaibhedia please assign this issue to me if needed


add optional syntax to wx_shape validation

Changes
This allows wx_shape validation to work with optional ASDF properties.
If a property is optional the name must be put in brackets like (optional_prop) in the wx_shape section of the schema (see asdf documentation)
Related Issues
Closes # (add issue numbers)
Checks

[x] updated CHANGELOG.md
[x] updated tests
[x] updated doc/
[x] update example/tutorial notebooks

Hello @CagtayFabry! Thanks for updating this PR.

In the file weldx/asdf/validators.py:

Line 5:1: F401 'pandas as pd' imported but unused


Headings should not be rendered isolated at the bottom of a page.

To reproduce:
Link
I searched for a solution before, but now I this very cool snippet!
https://stackoverflow.com/questions/9238868/how-do-i-avoid-a-page-break-immediately-after-a-heading/53742871#53742871
h1, h2 {
    page-break-inside: avoid;
}
h1::after, h2::after  {
    content: "";
    display: block;
    height: 100px;
    margin-bottom: -100px;
}

We should just add the other hX tags.
Here can it be tested with the css, here without

Ooh, this is an incredibly clever fix! I had resigned myself to the idea that page-break-after: avoid didn't work. I've included your fix in the commit referenced above, works like a charm :-)


Metric changes resulting from changing the training mode

Hello and thank you for your work! I would like to ask if when training the mask transformer, I set the conditional mode to uncond and changed the mask ratio from random to fixed 20%

, which results in a large fid (around 17), do you know what this is asking?

The fixed mask ratio would cause inconsistency between training and inference.


Allow Unordered ICA Channels

Summary
Currently, ICA only allows ordered channels. This causes the channel to close if a timeout occurs, forcing the user to reopen it.
Problem Definition
ICA only allows ordered channels because if ordering is not enforced, then the relayer could try malicious attacks by reordering/censoring some of the ica-controller's transactions. However, this requirement can be dropped because the ica-controller can choose not to send any new transactions until it receives an acknowledgement or a timeout packet.
From talking to multiple builders, my impression is that external ica-controller implementations would rather prefer to keep track of the tx sequence themselves.
This issue needs discussion because it is similar to https://github.com/cosmos/ibc-go/issues/1663. But this loosens the channel requirement even further and doesn't require a new connection.
Proposal

Remove the channel type = ordered checks from both host and controller.
If channel is ordered, keep logic the same, otherwise:
Modify golang controller and host to keep track of the sequence number of the tx's.
Restrict host to execute txs which increment the sequence number by 1.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

This would be very helpful for our use-case as well. We are using ICA round the clock with low timeout values for the transactions (because we want them to pass in a narrow time range, or not pass). If there is any event that causes this timeout then we're suddenly stuck with a closed channel that has to be re-opened.

Great to hear you are using ICA! Could you tell us a bit more about your precise use case if you are happy for it to be public? We had heard that ordered channels for ICA was a pain point for a few users but when we looked in more detail at the number of channel closures happening is actually really small. For example on Stride, the number of ICA timeouts has been 40/ 35,261 which is 0.11% of transactions since genesis and for Quicksilver it was 68 of 312,565 ICA txs since Jan. so approx 0.02% therefore the change would be a relatively small improvement it seems but would like to hear more about your own experience

approx 0.02% therefore the change would be a relatively small improvement it seems

I think this may be due to survivorship bias. I know most relayers don't want to run ICAs because it's too error prone and complex. Devs have a much harder time building applications because ICA relay channels are harder to come by. You should speak to some of the devs from the recent Dora hackathon within the Neutron track at Cosmoverse. The challenge required devs to use ICA and most people gave up because it was too difficult.

Quicksilver it was 68 of 312,565 ICA txs since Jan. so approx 0.02% therefore the change would be a relatively small improvement

'Small improvement' in percentage of overall terms, but the wasted hours of finding, fixing and working around channel closures has been an expensive past time :)
'Big improvement' in DevX.

Apologies; it was not my intention to suggest so :) great to see the spec is merged, I’m looking forward to it!


chore add a config to contorl if sync on close

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add xo from template
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

Codecov Report

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

@@           Coverage Diff           @@
##           master     #441   +/-   ##
=======================================
  Coverage   73.94%   73.94%
=======================================
  Files           2        2
  Lines         476      476
=======================================
  Hits          352      352
  Misses        124      124

Continue to review full report at Codecov.

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

Coverage remained the same at 71.626% when pulling 043dba806338cfdb8782de3611b31ed82e22639b on template-sync-1 into 8e82d85d5430c0c9ca6c2c543bd83fb483288c66 on master.

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


FDK Contexts

Per our group discussion about FDK's, just want to define what we put in our Context objects in the FDK's .

ctx.CallID() string
ctx.ContentType() string
ctx.Config() map[string]string - app + route configs merged
ctx.Get(string) - returns arbitrary object - this is where things like HTTP headers map would go, eg: ctx.Get("headers") => map[string][]string

ctx.Get() has confusing functionality since it's not clear whether it returns things from the config or the headers (or both), comments won't really fix that. if we return from both that seems fine, ctx.Get("headers") => map[string][]string seems hairy, because a user could make a config key that is "headers".
ctx.Config() and ctx.Headers() seems sane, with ctx.Get(string) pulling from either one potentially, but the precedence is tricky.

It returns from neither, ctx.Get("headers") returns the headers map. ctx.Get("whatever") would return something else, perhaps from another transport. A config key that is called headers would not conflict because config is already in ctx.Config(). If it were in Get(), it would be used like so: ctx.Get("config")[string]

I agree with Reed. We'd better go with the separate method for each type of protocol-specific mandatory fields. So, context.Headers() style is more preferable.
I know that headers, app/route config are the things we don't like to change. But can we somehow distinguish app config and route config inside function's runtime?
One more field to add to the list of things @treeder described:

context.Format()
context.App()
context.Route()
context.ContentLength() (in http we have exact header to use, but we don't have that in JSON

My 2 cents / pennies / eurocents...
I agree with Reed and Denis, a get(string) is too vaguely defined, and also not very idiomatic in more type-safe or opinionated languages where I would actually expect at least a get(some kind of enum) or even a genercized get<T>() where T is a type parameter denoting what we want to get. However, I disagree that we should expose different methods for each transport protocol and thus expose the protocols and require the developer to know which one was used (or get all of them until they get a non-null result).
In fact, I would even venture the idea that we should not specify too much the actual methods to get the data (which could and look different in every language), but we should specify what data is available and what it means. In other words, in this situation we can't yet specify "what the FDK should look like" because we still haven't really specified "what is the data that Fn can provide to the function".
My personal opinion is that the data is clearly differentiated based on who provides it, but the how it is provided doesn't matter too much to the function developer: it could be http / kafka / whatever is used to call the function. So it seems to me that a function developer would essentially care about four types of data to handle in their function:

Entirely contract-based Fn-specific values (call id, format, etc - provided by the Fn infrastructure)
Key/Value pairs from configuration (provided by the function developer / maintainer / operator)
Accessory Key/Value pairs from user input (provided by the caller via http headers or in the event)
A body of raw user input content (provided by the caller via http body or in the event)

Content type and length are a bit of a special case because we need to know them to interpret the body, so I'm not sure where exactly they would fit (I would consider them first-class Fn-specific stuff but that's just my gut feeling); still, it seems to me that everything else falls into one of those four categories.
It follows then that the "specification" I would suggest is that a "context representation" (again, it could be different in every language as long as it is still referred to as "the context") should have:

Individual accessors to get Fn-specific stuff (e.g. a ctx.callID() method - just an example in one language, not a spec)
A single accessor to access the key/value pairs in the config (for example as a method returning a read-only reference to a map, dict, or whatever the language allows)
A single accessor to access the key/value pairs in the user input (for example as a method returning a read-only reference to a map, dict, or whatever the language allows)
A single accessor to the raw body stream (or maybe we can omit this and say that the body stream will always be in the "input" parameter to the handler)

Incidentally, if we separate the data by who provides it, we then give the function developer all the information to decide things like precedence of user input vs config. We don't want to dictate that decision in our framework, because each developer might have their own rules based on business logic (e.g. to handle configurable defaults).

Responding to @denismakogon 's comment:

Format: is that useful to the function writer?  What would they do with that information?
App/Route: +1
ContentLength: if they did need it, they could just check the length on the input. If we support a streaming input option, I guess that would be more useful, but the common case won't be streaming (ie: most likely came in JSON format).

Responding to @hhexo 's comment:
Regarding the input we provide to the function, it's somewhat defined already and pretty much covers all 4 of your suggestions (docs could be a lot better, but I think it's sort of influx due to this. Both default and http format include 1 and 2 in the environment, 3 is in the environment for default format and in the http headers for http format. 4 is through STDIN.
You might want to get in on this conversation about the JSON input as we're trying to define it: https://github.com/fnproject/fn/pull/463 (and I'm thinking the JSON format should relate to the discussion we're having here).
Regarding the "context specification":
I think your 1, 2 and 4 are already covered and based on yours and others input, there appears to be some agreement on those. 4 is the separate input parameter though, not part of the context. 3 is the one we're mostly discussing here.

A single accessor to access the key/value pairs in the user input (for example as a method returning a read-only reference to a map, dict, or whatever the language allows)

Are you suggesting something like ctx.Arguments()? That returns some sort of map based on whatever the input is, defined by transport? That's not a bad idea, makes sense. But what is an argument in an HTTP request?  All the headers?  The query params?  Some parts of the path?  If we take all of those and put them into the same map, would it be confusing?  I think query parameters are an obvious one, you'd almost always want those (currently accessible via request_url). Parts of a path would be useful/required, especially if dynamic, but we haven't solved for that yet. I would venture a guess that the main header people would want to get access to is Authorization (we already provide content-type), and maybe that becomes top-level accessor (as discussed in meeting). Also, a lot (vast majority?) of user input will be JSON which will be a primary source of arguments to a function.
I think there's something there, but maybe we should flesh it out along with some real world examples.

@treeder so, having content length as part of format would let FDKs (at least Python, maybe others) provide body (from JSON object) as streaming object so there would be no need to keep fully in memory rather than providing streamable objects (similar to what @jan-g did for HTTP format, we provide input as content length stream reader).

So, here's one question. Where should protocol-specific attributes be stored?
For HTTP protocol we have following fields:

HTTP method
request URL
query parameters
HTTP proto version

Simple solution would be to put them inside context.protocol object. @treeder @rdallman @zootalures @hhexo thoughts?

I was indeed suggesting something like ctx.Arguments(). We would then need to define a contract for how protocol-specific differences are handled when collating the data.
@treeder has a very good point about the different types of key/value pairs in an http request... we have headers, query params, and other stuff (@denismakogon mentioned url, method and version), all can be possibly represented as key/value. Arguably it's http's fault for being a bit disorganized with its input - but it's true that http features solve different problems than the ones we have. :)
To have our cake and eat it, we could have two different APIs: we have an abstraction ("the context") as the default or recommended / documented way of working, and if you want to go low-level you use a different API and get the raw protocol data structures.
If the APIs are different, then we don't have to compromise, so we can say that the "context" is only our abstraction and we entirely dictate what goes in it (as long as we document the contract) regardless of protocol. InputEvent in the Java FDK is already quite close to this idea (minus the fact it exposes the headers).

Okay, I'm good with context.Arguments() as key-value. Just wanted to make things clear. It looks like JSON protocol has nothing like HTTP, no version, no query parameters, etc. So that just might be empty, anyway, let's stick with the following API (bare minimum) for context object:
CallID() // Fn call ID
AppName() // Fn app name
Route() // Fn app route path
Config() // Fn app and/or route key-value config
Headers() // Call request headers
Arguments() // for protocol-specific attributes

Questions:

Should we include context.RequestURL() as well? For hot JSON/HTTP it always dynamic and developers might want to access/use it.

Should we include context.RequestURL() as well? For hot JSON/HTTP it always dynamic and developers might want to access/use it.

it's possible we have non-http input in the future, so it may be best to leave this tucked away in the headers for the time being.

I do remember that we at least talked about that, agree, that still possible. But I don't remember that we talked about having non-http function triggering. I mean, we'd still have http requests used for triggering function, no?

not necessarily I don't think. for example, we could consume a kafka topic directly and generate 'functions' from that (i.e. the topic name is the "route" to use, with each message a payload [of some possible format])

Okay, if the call will go in a different path, then agree, request URL should stay somewhere behind the scene and be available through HTTP headers.

I don't think we all agree on headers either, I don't think it should be a top level method. The following so far are for sure, the rest we should stick in an arbitrary map until we figure out where (or if) we want them top level.
CallID() // Fn call ID
ContentType() // eg: application/json
AppName() // Fn app name
Route() // Fn app route path
Config() // Fn app and/or route key-value config
SomeFunctionToGetOtherArbitraryValuesOutOfAMap() // eg: Get("headers"), OpenEvents has an "attributes" map for extras like this btw.

The reason that last function should be a map is to keep it flexible so we can put whatever we want into it until we decide whether something should get bumped up to the top. It could container "headers", "request_url", "query_parameters", "hostname", "container_id", etc. And we can safely move forward covering everything we need without locking ourselves into something.

Okay, so, OpenEvents appears pretty often, can't we implement JSON protocol according to OpenEvents spec? This looks more and more reasonable at this point. Of course, that would be OpenEvents-compatible JSON protocol, because we have more terms and resources than OpenEvents spec or we name things differently. Thoughts? @rdallman @treeder


Need documentation for Installing SQL Server 2019 Express from the Command Prompt

__Could you provide corresponding documentation for Installing SQL Server 2019 Express from the Command Prompt?
On the SQL Server Downloads page, the SQL Server 2019 Express edition setup (SQL2019-SSEI-Expr.exe) is downloaded from https://go.microsoft.com/fwlink/?linkid=866658.
The interactive setup of SQL2019-SSEI-Expr.exe works fine, but there is no documentation for using SQL2019-SSEI-Expr.exe as a silent install. I'm specifically trying to include it in a WiX bootstrapper package, for which there are also no examples of bootstrapping the SQL 2019 Express setup.
Any documentation and/or examples of Installing SQL Server 2019 Express from the Command Prompt or WiX would be greatly appreciated.
Thanks,
Dean.
[Enter feedback here]

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

ID: 4ff01c71-f3bf-2c3a-5e90-b11952aee4f8
Version Independent ID: 99ebd80b-9465-6929-c84f-187525ee3284
Content: SQL Server installation - Command Prompt parameters - SQL Server
Content Source: docs/database-engine/install-windows/install-sql-server-from-the-command-prompt.md
Product: sql
Technology: install
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@deanwiles -- Dean, thank you for your feedback.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@MashaMSFT -- Masha, please look into this issue.

Thanks, William.
I have been scouring through those resources for the past few weeks without much luck. There are mostly examples of using earlier versions of SQL Server setup (e.g. 2012) which do not behave the same and which invoke SQLEXPR_x86_ENU.exe directly instead of the new SQL2019-SSEI-Expr.exe setup wrapper.
I can manually download the 2019 version of SQLEXPR_x86_ENU.exe (or use Fiddler to deduce the current Microsoft download URL for SQLEXPR_x86_ENU.exe), but that also lacks current command line documentation or examples of bootstrapping from WiX.

@deanwiles
First, we apologize for the delayed response.
Thank you for your feedback! We will investigate and get back to you with the relevant info.

@deanwiles
Have you come across this page - https://www.brycematheson.io/how-to-perform-a-silent-install-of-sql-server-or-sql-express/?

@deanwiles
I had some time to go through the article and try the command with the file name you provided for SQL Server 2019 Express - SQL2019-SSEI-Expr.exe.
And in the code block when I replace "setup.exe" with the filename SQL2019-SSEI-Expr.exe, it does a quiet install.
C:\SQLMedia\SQLServer2019> setup.exe /Q /IACCEPTSQLSERVERLICENSETERMS /ACTION="install" /PID="AAAAA-BBBBB-CCCCC-DDDDD-EEEEE" /FEATURES=SQL,AS,IS,Tools
/INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="MyDomain\MyAccount"
/SQLSVCPASSWORD="" /SQLSYSADMINACCOUNTS="MyDomain\MyAccount "
/AGTSVCACCOUNT="MyDomain\MyAccount" /AGTSVCPASSWORD=""
/ASSVCACCOUNT="MyDomain\MyAccount" /ASSVCPASSWORD=""
/ISSVCAccount="MyDomain\MyAccount" /ISSVCPASSWORD=""
/ASSYSADMINACCOUNTS="MyDomain\MyAccount"
Result i get:

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion, and we will reopen the issue. To see what the community is wanting, please visit the SQL Server User Feedback site.

Thanks. I finally got SQL Express 2019 to Bootstrap silently from WiX and documented my findings here.


Where i can find the FW File ?

bfus    9.0.19

?

https://github.com/roleoroleo/yi-hack-Allwinner-v2/releases/tag/0.1.2

as this has been resolved, could you please close this issue?
thanks,
p

Thank you


Going to another not spa page then hitting back button returns JSON response

Version
2.7.0
Reproduction link
https://github.com/jericopulvera/test-app
Steps to reproduce

I searched something from my search bar then router.push('search', query)

Search returns a result

Then I go to a login page that is not an SPA.

I click back button from the browser.

I get a JSON response instead of vue-router page.

What is expected?
return vue router page.
What is actually happening?
returning a json response.

that's a pretty big repo! are you able to provide a minimal case?

If you see the JSON response, then that'S coming from your server, so vue-router (running on the client) has nothting to do with it.
I assume you are using vue-router in history mode? You must configure your server accordingly to this:
https://router.vuejs.org/en/essentials/history-mode.html


fix(cors) properly validate flat strings

Closes #3832.
This pull request changes the behavior of the CORS plugin as follows:

Forces a full string validation to avoid the issue in #3832
When a both valid and matched domain is processed, returns an Access-Control-Allow-Origin header value that equals the string sent by the client in the original Origin value
Validates that the scheme, host and port also match the Origin value as per RFC6454 Section 5

These changes seem reasonable to me, but happy to hear feedback.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I have added a commit to this PR. Should be good to go now, but waiting for any additional review just in case. Will be merged for 1.0rc4.