black screen instead of login to session on Ubuntu 22.04 LTS

#2258 was closed but the problem persist after an Ubuntu LTS 22.04 upgrade.
The error messages are only shown in the log file and the user is confronted with a black screen

@matt335672  thank your for looking into this. I am having a hard time hunting down the reason(s) why remote desktop sharing doesn't work out of the box on my ubuntu 22.04 LTS boxes.
I have also filed https://bugs.launchpad.net/ubuntu/+bug/1995201  and there seem to be quite a few parts involved and the documentation seems to be lacking necessary parts.
The first part i don't understand is whether i have to install xrdp in the first place. The machine that does offer remote desktop sharing via rdp and works doesn't have xrdp installed at all.
For another machine installing xrdp will make connections possible but than the desktop doesn't appear properly.
I get error messages in
/var/log/syslog
/var/log/xrdp.log
/var/log/xrdp-sesman.log
examples from /var/log/syslog
Oct 31 12:42:13 capri xrdp[32057]: [INFO ] connection problem, giving up
Oct 31 12:42:13 capri xrdp[32057]: [INFO ] some problem
Oct 31 12:42:13 capri xrdp[32057]: [ERROR] SSL_write: I/O error
Oct 31 12:42:13 capri xrdp[32057]: [ERROR] xrdp_sec_send_fastpath: xrdp_fastpath_send failed
Oct 31 12:42:13 capri xrdp[32057]: [ERROR] xrdp_rdp_send_fastpath: xrdp_sec_send_fastpath failed
Oct 31 12:42:13 capri xrdp[32057]: [ERROR] xrdp_orders_send: xrdp_rdp_send_fastpath failed
Oct 31 12:42:13 capri xrdp[32057]: [ERROR] xrdp_sec_send_fastpath: xrdp_fastpath_send failed
Oct 31 12:42:13 capri xrdp[32057]: [ERROR] xrdp_rdp_send_fastpath: xrdp_sec_send_fastpath failed
Oct 31 12:42:13 capri xrdp[32057]: [ERROR] xrdp_orders_send: xrdp_rdp_send_fastpath failed
Oct 31 12:42:13 capri xrdp[32057]: [ERROR] xrdp_iso_send: trans_write_copy_s failed

examples from xrdp.log
[20221030-11:40:41] [ERROR] xrdp_wm_log_msg: error loading libvnc.so specified in xrdp.ini, please add a valid entry like lib=libxrdp-vnc.so or similar

examples from xrdp-sesman.log
[20221030-11:19:41] [WARN ] Timed out waiting for X server on display 10 to startup
[20221030-11:19:41] [ERROR] There is no X server active on display 10
[20221030-11:19:41] [ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection
[20221030-11:19:41] [WARN ] Window manager (pid 13340, display 10) exited quickly (0 secs). This could indicate a window manager config problem
....
[20221031-12:38:54] [INFO ] Session started successfully for user ... on display 10
[20221031-12:38:54] [INFO ] Starting the xrdp channel server for display 10
[20221031-12:38:54] [INFO ] Session in progress on display 10, waiting until the window manager (pid 32578) exits to end the session
[20221031-12:38:54] [WARN ] Timed out waiting for X server on display 10 to startup
[20221031-12:38:54] [ERROR] There is no X server active on display 10
[20221031-12:38:54] [ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection
[20221031-12:38:54] [WARN ] Window manager (pid 32578, display 10) exited quickly (0 secs). This could indicate a window manager config problem
[20221031-12:38:54] [INFO ] Calling auth_stop_session and auth_end from pid 32577
[20221031-12:38:54] [INFO ] Terminating X server (pid 32579) on display 10
[20221031-12:38:54] [INFO ] Terminating the xrdp channel server (pid 32583) on display 10
[20221031-12:38:54] [INFO ] X server on display 10 (pid 32579) returned exit code 1 and signal number 0
[20221031-12:38:54] [INFO ] xrdp channel server for display 10 (pid 32583) exit code 0 and signal number 0

For 22.04, if you just want to share the desktop of the logged-in user, use gnome-remote-desktop provided by GNOME 42. This is a simple way to share the desktop of a logged-in user over RDP. It uses the same TCP port as xrdp, so is incompatible with it.
If you want to user xrdp to get the session management we'll need to look at those errors.
The best place to start is xrdp-sesman. We'll need a complete log from where the connection attempt is received for the user.

It depends entirely on your use-case(s).
If you just want your users to connect to existing desktops, use GRD - it's what it's for.
If you want more of a terminal server arrangement where your users only have remote desktops, use xrdp.
In between these two, things are more murky. Bear in mind that on systemd-based distros any user can only have one graphical desktop active on a system at once. You can't log a system in on the graphical console and then start an xrdp session on the same box with the same user. Similarly, if a user is logged in over xrdp, you can't log the same user in on the graphical console. This is a systemd limitation. See https://github.com/systemd/systemd/issues/24932 for technical information on this.

@Zheka17 :-

what do you get for dpkg -l \*xrdp\*?
what's in /home/zheka/.xorgxrdp.10.log?

||/ Name           Version      Architecture Description
+++-==============-============-============-===============================================
ii  xorgxrdp       1:0.2.18-1   amd64        Remote Desktop Protocol (RDP) modules for X.org
ii  xrdp           0.9.19-1+b2  amd64        Remote Desktop Protocol (RDP) server

[   170.895]
X.Org X Server <IP_ADDRESS>
X Protocol Version 11, Revision 0
[   170.895] Current Operating System: Linux eadeb 6.0.11-x64v3-xanmod1 0~20221202.bfbe1c1 SMP PREEMPT_DYNAMIC Fri Dec 2 23:03:53 UTC 2 x86_64
[   170.895] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.0.11-x64v3-xanmod1 root=UUID=0308af2f-0ebe-4830-9f80-db773d45972c ro noplymouth video=SVIDEO-1:d mitigations=off transparent_hugepage=always quiet
[   170.895] xorg-server 2:21.1.4-3 (https://www.debian.org/support)
[   170.895] Current version of pixman: 0.42.2
[   170.895]    Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   170.895] Markers: (--) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   170.895] (++) Log file: ".xorgxrdp.10.log", Time: Mon Dec  5 14:36:22 2022
[   170.895] (++) Using config file: "/etc/X11/xrdp/xorg.conf"
[   170.895] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   170.895] () Option "defaultserverlayout" "X11 Server"
[   170.895] () ServerLayout "X11 Server"
[   170.895] () |-->Screen "Screen (xrdpdev)" (0)
[   170.895] () |   |-->Monitor "Monitor"
[   170.895] () |   |-->Device "Video Card (xrdpdev)"
[   170.895] () |-->Input Device "xrdpMouse"
[   170.895] () |-->Input Device "xrdpKeyboard"
[   170.895] () Option "DontVTSwitch" "on"
[   170.895] () Option "AutoAddDevices" "off"
[   170.895] () Not automatically adding devices
[   170.895] (==) Automatically enabling devices
[   170.895] (==) Automatically adding GPU devices
[   170.895] (==) Automatically binding GPU devices
[   170.895] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   170.895] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   170.895]    Entry deleted from font path.
[   170.895] (==) 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
[   170.895] (==) ModulePath set to "/usr/lib/xorg/modules"
[   170.895] (II) Loader magic: 0x55e05f298f00
[   170.895] (II) Module ABI versions:
[   170.895]    X.Org ANSI C Emulation: 0.4
[   170.895]    X.Org Video Driver: 25.2
[   170.895]    X.Org XInput driver : 24.4
[   170.895]    X.Org Server Extension : 10.0
[   170.896] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
[   170.896] (II) xfree86: Adding drm device (/dev/dri/card0)
[   170.896] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[   170.896] (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted
[   170.897] (--) PCI:*(0@0:2:0) 8086:4680:1043:8694 rev 12, Mem @ 0x6002000000/16777216, 0x4000000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
[   170.897] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[   170.897] (II) LoadModule: "dbe"
[   170.897] (II) Module "dbe" already built-in
[   170.897] (II) LoadModule: "ddc"
[   170.897] (II) Module "ddc" already built-in
[   170.897] (II) LoadModule: "extmod"
[   170.897] (II) Module "extmod" already built-in
[   170.897] (II) LoadModule: "glx"
[   170.897] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   170.897] (II) Module glx: vendor="X.Org Foundation"
[   170.897]    compiled for <IP_ADDRESS>, module version = 1.0.0
[   170.897]    ABI class: X.Org Server Extension, version 10.0
[   170.897] (II) LoadModule: "int10"
[   170.897] (II) Loading /usr/lib/xorg/modules/libint10.so
[   170.897] (II) Module int10: vendor="X.Org Foundation"
[   170.897]    compiled for <IP_ADDRESS>, module version = 1.0.0
[   170.897]    ABI class: X.Org Video Driver, version 25.2
[   170.897] (II) LoadModule: "record"
[   170.897] (II) Module "record" already built-in
[   170.897] (II) LoadModule: "vbe"
[   170.897] (II) Loading /usr/lib/xorg/modules/libint10.so
[   170.897] (II) Module int10: vendor="X.Org Foundation"
[   170.897]    compiled for <IP_ADDRESS>, module version = 1.0.0
[   170.897]    ABI class: X.Org Video Driver, version 25.2
[   170.897] (II) LoadModule: "glamoregl"
[   170.897] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[   170.898] (II) Module glamoregl: vendor="X.Org Foundation"
[   170.898]    compiled for <IP_ADDRESS>, module version = 1.0.1
[   170.898]    ABI class: X.Org ANSI C Emulation, version 0.4
[   170.898] (II) LoadModule: "xorgxrdp"
[   170.898] (II) Loading /usr/lib/xorg/modules/libxorgxrdp.so
[   170.899] (II) Module XORGXRDP: vendor="X.Org Foundation"
[   170.899]    compiled for <IP_ADDRESS>, module version = 0.2.18
[   170.899]    ABI class: X.Org Video Driver, version 25.2
[   170.899] xorgxrdpSetup:
[   170.899] (II) LoadModule: "fb"
[   170.899] (II) Module "fb" already built-in
[   170.899] (II) LoadModule: "xrdpdev"
[   170.899] (II) Loading /usr/lib/xorg/modules/drivers/xrdpdev_drv.so
[   170.899] (II) Module XRDPDEV: vendor="X.Org Foundation"
[   170.899]    compiled for <IP_ADDRESS>, module version = 0.2.18
[   170.899]    ABI class: X.Org Video Driver, version 25.2
[   170.899] xrdpdevSetup:
[   170.899] (II) LoadModule: "xrdpmouse"
[   170.899] (II) Loading /usr/lib/xorg/modules/input/xrdpmouse_drv.so
[   170.899] (II) Module XRDPMOUSE: vendor="X.Org Foundation"
[   170.899]    compiled for <IP_ADDRESS>, module version = 0.2.18
[   170.899]    Module class: X.Org XInput Driver
[   170.899]    ABI class: X.Org XInput driver, version 24.4
[   170.899] rdpmousePlug:
[   170.899] (II) LoadModule: "xrdpkeyb"
[   170.899] (II) Loading /usr/lib/xorg/modules/input/xrdpkeyb_drv.so
[   170.899] (II) Module XRDPKEYB: vendor="X.Org Foundation"
[   170.899]    compiled for <IP_ADDRESS>, module version = 0.2.18
[   170.899]    Module class: X.Org XInput Driver
[   170.899]    ABI class: X.Org XInput driver, version 24.4
[   170.899] rdpkeybPlug:
[   170.899] rdpIdentify:
[   170.899] (II) XRDPDEV: driver for xrdp: XRDPDEV
[   170.899] rdpDriverFunc: op 10
[   170.899] (WW) Falling back to old probe method for XRDPDEV
[   170.899] rdpProbe:
[   170.899] (II) Loading sub module "fb"
[   170.899] (II) LoadModule: "fb"
[   170.899] (II) Module "fb" already built-in
[   170.899] rdpProbe: found DRMDevice xorg.conf value [/dev/dri/renderD128]
[   170.899] rdpProbe: found DRI3 xorg.conf value [1]
[   170.899] (II) XRDPDEV(0): using default device
[   170.899] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   170.899] rdpPreInit:
[   170.899] rdpPreInit: /dev/dri/renderD128 open failed
[   170.899] () XRDPDEV(0): Depth 24, (--) framebuffer bpp 32
[   170.899] (==) XRDPDEV(0): RGB weight 888
[   170.899] (==) XRDPDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[   170.899] (==) XRDPDEV(0): Default visual is TrueColor
[   170.899] (==) XRDPDEV(0): DPI set to (96, 96)
[   170.899] (II) XRDPDEV(0):   mode "640x480" ok
[   170.899] (II) XRDPDEV(0):   mode "800x600" ok
[   170.899] (II) XRDPDEV(0): Virtual size is 800x600 (pitch 800)
[   170.899] (**) XRDPDEV(0):  Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[   170.899] (II) XRDPDEV(0): Modeline "800x600"x0.0   36.00  800<PHONE_NUMBER>  600 601 603 625 +hsync +vsync (35.2 kHz d)
[   170.899] rdpScreenInit: virtualX 800 virtualY 600 rgbBits 8 depth 24
[   170.899] rdpScreenInit: pfbMemory bytes 1920000
[   170.899] rdpScreenInit: pfbMemory 0x7f859b51e010
[   170.899] rdpSimdInit: assigning yuv functions
[   170.899] rdpSimdInit: cpuid ax 1 cx 0 return ax 0x00090672 bx 0x10800800 cx 0x7ffafbff dx 0xbfebfbff
[   170.899] rdpSimdInit: sse2 amd64 yuv functions assigned
[   170.899] (==) XRDPDEV(0): Backing store enabled
[   170.899] rdpClientConInit: disconnect idle session after [0] sec
[   170.899] rdpClientConInit: kill disconnected [0] timeout [0] sec
[   170.899] rdpXvInit: depth 24
[   170.899] rdpScreenInit: out
[   170.899] (II) Initializing extension Generic Event Extension
[   170.899] (II) Initializing extension SHAPE
[   170.899] (II) Initializing extension MIT-SHM
[   170.899] (II) Initializing extension XInputExtension
[   170.899] (II) Initializing extension XTEST
[   170.899] (II) Initializing extension BIG-REQUESTS
[   170.899] (II) Initializing extension SYNC
[   170.899] (II) Initializing extension XKEYBOARD
[   170.899] (II) Initializing extension XC-MISC
[   170.899] (II) Initializing extension SECURITY
[   170.900] (II) Initializing extension XFIXES
[   170.900] (II) Initializing extension RENDER
[   170.900] (II) Initializing extension RANDR
[   170.900] (II) Initializing extension COMPOSITE
[   170.900] (II) Initializing extension DAMAGE
[   170.900] (II) Initializing extension MIT-SCREEN-SAVER
[   170.900] (II) Initializing extension DOUBLE-BUFFER
[   170.900] (II) Initializing extension RECORD
[   170.900] (II) Initializing extension DPMS
[   170.900] (II) Initializing extension Present
[   170.900] (II) Initializing extension DRI3
[   170.900] (II) Initializing extension X-Resource
[   170.900] (II) Initializing extension XVideo
[   170.900] (II) Initializing extension XVideo-MotionCompensation
[   170.900] (II) Initializing extension SELinux
[   170.900] (II) SELinux: Disabled on system
[   170.900] (II) Initializing extension GLX
[   170.900] (II) AIGLX: Screen 0 is not DRI2 capable
[   170.909] (EE)
[   170.909] (EE) Backtrace:
[   170.910] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55e05f20cc59]
[   170.910] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f859c25af90]
[   170.910] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   170.910] (EE) 2: /lib64/ld-linux-x86-64.so.2 (?+0x0) [0x7f859cb3c029]
[   170.910] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (_dl_catch_exception+0x7a) [0x7f859c36de9a]
[   170.910] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (_dl_catch_error+0x2f) [0x7f859c36df4f]
[   170.910] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (dlerror+0x297) [0x7f859c2a3dc7]
[   170.910] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (dlclose+0x36) [0x7f859c2a3b26]
[   170.911] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (nouveau_drm_screen_create+0x1d50f4) [0x7f859a4e7f44]
[   170.911] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (nouveau_drm_screen_create+0x1d4340) [0x7f859a4e7190]
[   170.911] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   170.911] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (?+0x0) [0x7f8599aaa179]
[   170.911] (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x60ae16) [0x7f859a0b5156]
[   170.911] (EE) 11: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x60ad84) [0x7f859a0b50c4]
[   170.911] (EE) 12: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x6f4) [0x7f8599aaaa34]
[   170.911] (EE) 13: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0xa175) [0x7f8599ab44b5]
[   170.911] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   170.911] (EE) 14: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7f859bc18d77]
[   170.911] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   170.911] (EE) 15: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7f859bc17b7f]
[   170.911] (EE) 16: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) [0x55e05f09ea24]
[   170.911] (EE) 17: /usr/lib/xorg/Xorg (dri3_send_open_reply+0x10af) [0x55e05f1caa9f]
[   170.911] (EE) 18: /usr/lib/xorg/Xorg (InitExtensions+0x89) [0x55e05f10a2a9]
[   170.911] (EE) 19: /usr/lib/xorg/Xorg (InitFonts+0x1e8) [0x55e05f09d4e8]
[   170.911] (EE) 20: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) [0x7f859c24618a]
[   170.911] (EE) 21: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x85) [0x7f859c246245]
[   170.911] (EE) 22: /usr/lib/xorg/Xorg (_start+0x21) [0x55e05f086b61]
[   170.911] (EE)
[   170.911] (EE) Segmentation fault at address 0x337
[   170.912] (EE)
Fatal server error:
[   170.912] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   170.912] (EE)
[   170.912] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[   170.912] (EE) Please also check the log file at ".xorgxrdp.10.log" for additional information.
[   170.912] (EE)
[   170.912] rdpLeaveVT:
[   170.912] (EE) Server terminated with error (1). Closing log file.

Can you try using one of these:

https://gist.github.com/Nexarian/82cb4d48f07e9b9005123c21c8dc08e5#file-xrdp-intel-setup-sh
https://gist.github.com/Nexarian/0eb26a3284b21b55b6e1e8653ed88ec9#file-xrdp-nvidia-setup-sh

Reboot, and let me know if the session loads? With MSTSC, I've had good results with both of these on a from-scratch Ubuntu 22.04.1 installation.

that's the output of:   dmesg | grep drm

[    0.809548] ACPI: bus type drm_connector registered
[    1.193980] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[    1.195111] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
[    1.197564] i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_70.1.1.bin version 70.1
[    1.197567] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9
[    1.211721] i915 0000:00:02.0: [drm] HuC authenticated
[    1.211724] i915 0000:00:02.0: [drm] GuC submission disabled
[    1.211726] i915 0000:00:02.0: [drm] GuC SLPC disabled
[    1.212405] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
[    1.212850] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[    1.214228] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[    1.214299] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[    1.610591] systemd[1]: Starting Load Kernel Module drm...
[    1.613927] systemd[1]<EMAIL_ADDRESS>Deactivated successfully.
[    1.613959] systemd[1]: Finished Load Kernel Module drm.

( I am wary of trying Nexarian's solution... yet)

@Zheka17 What makes you wary of it? While the branches are prototypes, you could easily change the code in the installation scripts to suit your needs (and build devel instead). The two most important things in there are the Xorg configuration as well as adding your username to the proper groups.

This just got resolved with Debian's update/bug fix to mesa drivers.

On 3 of my 4 computers i was able to solve the problem in a very awkward way of debugging an try and error. The 4th machine still gives strange error messages that some driver problem exists. It will take until January before i can report more on this because i am away from that machine for 4 weeks. It's a pity the ticket is closed as of now because there is quite a bit of background information available by now. Here is the message  i get on the non working machine:
Oct 31 13:54:03 pax gnome-shell[1942]: Failed to create virtual monitor with size 1920x1080: Backend doesn't support creating virtual monitors

@WolfgangFahl - feel free to post any information you have.
I don't recognise the message above I'm afraid. It looks like it's come from a logged in session, and as I understand the problem, you are not able to log in. Have I misunderstood something?

It just looks if i can't login. There have been lot's of reasons why the screen stays black since i investigated the details. No reason to close this issue. The problem is a live and kicking under certain circumstances.

Post xrdp-sesman.log for a login attempt and we'll look at it.
Suggest you:-

systemctl stop xrdp-sesman
sudo rm /var/log/xrdp-sesman.log
systemctl start xrdp-sesman

The try to log in and post the entire resulting log.

Dear @matt335672,
I'm having a similar issue as described by the OP. Here is the full xrdp-sesman.log after running the steps above:
[20230627-11:46:58] [INFO ] starting xrdp-sesman with pid 771001
[20230627-11:47:29] [INFO ] Socket 8: AF_INET6 connection received from ::1 port 39104
[20230627-11:47:29] [INFO ] Terminal Server Users group is disabled, allowing authentication
[20230627-11:47:29] [INFO ] ++ created session (access granted): username csantos, ip ::ffff:<IP_ADDRESS>:63555 - socket: 12
[20230627-11:47:29] [INFO ] starting Xorg session...
[20230627-11:47:29] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20230627-11:47:29] [INFO ] Starting session: session_pid 853182, display :11.0, width 1400, height 1050, bpp 24, client ip ::ffff:<IP_ADDRESS>:63555 - socket: 12, user name csantos
[20230627-11:47:29] [INFO ] [session start] (display 11): calling auth_start_session from pid 853182
[20230627-11:47:29] [ERROR] sesman_data_in: scp_process_msg failed
[20230627-11:47:29] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
[20230627-11:47:29] [INFO ] Starting X server on display 11: /usr/lib/xorg/Xorg :11 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20230627-11:47:29] [INFO ] Found X server running at /tmp/.X11-unix/X11
[20230627-11:47:29] [INFO ] Found X server running at /tmp/.X11-unix/X11
[20230627-11:47:29] [INFO ] Found X server running at /tmp/.X11-unix/X11
[20230627-11:47:29] [INFO ] Session started successfully for user csantos on display 11
[20230627-11:47:29] [INFO ] Starting the xrdp channel server for display 11
[20230627-11:47:29] [INFO ] Starting the default window manager on display 11: /etc/xrdp/startwm.sh
[20230627-11:47:29] [INFO ] Session in progress on display 11, waiting until the window manager (pid 853194) exits to end the session

I'm on Ubuntu 22.04.2, running xrdp 0.9.17-2ubuntu2 and xorgxrdp 1:0.2.17-1build1, with a CUDA enabled proprietary driver, CUDA/CUDA Toolkit installed. Nexarian's suggestion seems promising, but I'd like to avoid installing all the additional packages if possible.

I wonder why the ticket is closed - there is still no systematic solution that will avoid the problem and make sure a login is possible or a proper error message appears.

Thanks for the tips @matt335672 . Could you elaborate on option (1)? The information under ~/.xorgxrdp.x.log wasn't clear enough for me, and I do not know what files to edit to achieve this configuration. I assumed it should be the file /etc/X11/xrdp/xorg.conf, but again there was no mention of "gpu", "hardware" or "acceleration" in this file, so I'm a bit lost here.
I also tried option (2), but even after compiling xrdp and xorgxrdp with --enable-glamor, the original issue persisted. The logs did look different though:
[  7904.898]
X.Org X Server <IP_ADDRESS>
X Protocol Version 11, Revision 0
[  7904.898] Current Operating System: Linux bigfoot 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64
[  7904.898] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=ce10ac21-772e-4ea7-941e-33515c6d422b ro quiet splash vt.handoff=7
[  7904.898] xorg-server 2:21.1.4-2ubuntu1.7~22.04.1 (For technical support please see http://www.ubuntu.com/support)
[  7904.898] Current version of pixman: 0.40.0
[  7904.898] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  7904.898] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  7904.898] (++) Log file: ".xorgxrdp.11.log", Time: Fri Jul  7 20:58:03 2023
[  7904.898] (++) Using config file: "/etc/X11/xrdp/xorg.conf"
[  7904.898] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  7904.898] (**) Option "defaultserverlayout" "X11 Server"
[  7904.898] (**) ServerLayout "X11 Server"
[  7904.898] (**) |-->Screen "Screen (xrdpdev)" (0)
[  7904.898] (**) |   |-->Monitor "Monitor"
[  7904.898] (**) |   |-->Device "Video Card (xrdpdev)"
[  7904.898] (**) |-->Input Device "xrdpMouse"
[  7904.898] (**) |-->Input Device "xrdpKeyboard"
[  7904.898] (**) Option "DontVTSwitch" "on"
[  7904.898] (**) Option "AutoAddDevices" "off"
[  7904.898] (**) Not automatically adding devices
[  7904.898] (==) Automatically enabling devices
[  7904.898] (==) Automatically adding GPU devices
[  7904.898] (==) Automatically binding GPU devices
[  7904.898] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  7904.898] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  7904.898] 	Entry deleted from font path.
[  7904.898] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[  7904.898] 	Entry deleted from font path.
[  7904.898] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[  7904.898] 	Entry deleted from font path.
[  7904.898] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[  7904.898] 	Entry deleted from font path.
[  7904.898] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[  7904.898] 	Entry deleted from font path.
[  7904.898] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	built-ins
[  7904.898] (==) ModulePath set to "/usr/lib/xorg/modules"
[  7904.898] (II) Loader magic: 0x5601fec44020
[  7904.898] (II) Module ABI versions:
[  7904.898] 	X.Org ANSI C Emulation: 0.4
[  7904.898] 	X.Org Video Driver: 25.2
[  7904.898] 	X.Org XInput driver : 24.4
[  7904.898] 	X.Org Server Extension : 10.0
[  7904.899] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c3
[  7904.899] (II) xfree86: Adding drm device (/dev/dri/card1)
[  7904.899] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card1
[  7904.899] (EE) systemd-logind: failed to take device /dev/dri/card1: Operation not permitted
[  7904.899] (II) xfree86: Adding drm device (/dev/dri/card0)
[  7904.899] (II) Platform probe for /sys/devices/pci0000:00/0000:00:08.1/0000:18:00.0/drm/card0
[  7904.899] (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted
[  7904.902] (--) PCI:*(1@0:0:0) 10de:2684:10de:167c rev 161, Mem @ 0xfb000000/16777216, 0xf000000000/34359738368, 0xf800000000/33554432, I/O @ 0x0000f000/128, BIOS @ 0x????????/524288
[  7904.902] (--) PCI: (24@0:0:0) 1002:164e:1462:7d67 rev 193, Mem @ 0xf810000000/268435456, 0xf820000000/2097152, 0xfcd00000/524288, I/O @ 0x0000e000/256
[  7904.902] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[  7904.902] (II) LoadModule: "dbe"
[  7904.902] (II) Module "dbe" already built-in
[  7904.902] (II) LoadModule: "ddc"
[  7904.902] (II) Module "ddc" already built-in
[  7904.902] (II) LoadModule: "extmod"
[  7904.902] (II) Module "extmod" already built-in
[  7904.902] (II) LoadModule: "glx"
[  7904.902] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  7904.902] (II) Module glx: vendor="X.Org Foundation"
[  7904.902] 	compiled for <IP_ADDRESS>, module version = 1.0.0
[  7904.902] 	ABI class: X.Org Server Extension, version 10.0
[  7904.902] (II) LoadModule: "int10"
[  7904.902] (II) Loading /usr/lib/xorg/modules/libint10.so
[  7904.902] (II) Module int10: vendor="X.Org Foundation"
[  7904.902] 	compiled for <IP_ADDRESS>, module version = 1.0.0
[  7904.902] 	ABI class: X.Org Video Driver, version 25.2
[  7904.902] (II) LoadModule: "record"
[  7904.902] (II) Module "record" already built-in
[  7904.902] (II) LoadModule: "vbe"
[  7904.902] (II) Loading /usr/lib/xorg/modules/libint10.so
[  7904.902] (II) Module int10: vendor="X.Org Foundation"
[  7904.902] 	compiled for <IP_ADDRESS>, module version = 1.0.0
[  7904.902] 	ABI class: X.Org Video Driver, version 25.2
[  7904.902] (II) LoadModule: "xorgxrdp"
[  7904.903] (II) Loading /usr/lib/xorg/modules/libxorgxrdp.so
[  7904.903] (II) Module XORGXRDP: vendor="X.Org Foundation"
[  7904.903] 	compiled for <IP_ADDRESS>, module version = 0.9.19
[  7904.903] 	ABI class: X.Org Video Driver, version 25.2
[  7904.903] xorgxrdpSetup:
[  7904.903] (II) LoadModule: "fb"
[  7904.903] (II) Module "fb" already built-in
[  7904.903] (II) LoadModule: "xrdpdev"
[  7904.903] (II) Loading /usr/lib/xorg/modules/drivers/xrdpdev_drv.so
[  7904.904] (II) Module XRDPDEV: vendor="X.Org Foundation"
[  7904.904] 	compiled for <IP_ADDRESS>, module version = 0.9.19
[  7904.904] 	ABI class: X.Org Video Driver, version 25.2
[  7904.904] xrdpdevSetup:
[  7904.904] (II) LoadModule: "xrdpmouse"
[  7904.904] (II) Loading /usr/lib/xorg/modules/input/xrdpmouse_drv.so
[  7904.904] (II) Module XRDPMOUSE: vendor="X.Org Foundation"
[  7904.904] 	compiled for <IP_ADDRESS>, module version = 0.9.19
[  7904.904] 	Module class: X.Org XInput Driver
[  7904.904] 	ABI class: X.Org XInput driver, version 24.4
[  7904.904] rdpmousePlug:
[  7904.904] (II) LoadModule: "xrdpkeyb"
[  7904.904] (II) Loading /usr/lib/xorg/modules/input/xrdpkeyb_drv.so
[  7904.904] (II) Module XRDPKEYB: vendor="X.Org Foundation"
[  7904.904] 	compiled for <IP_ADDRESS>, module version = 0.9.19
[  7904.904] 	Module class: X.Org XInput Driver
[  7904.904] 	ABI class: X.Org XInput driver, version 24.4
[  7904.904] rdpkeybPlug:
[  7904.904] rdpIdentify:
[  7904.904] (II) XRDPDEV: driver for xrdp: XRDPDEV
[  7904.904] rdpDriverFunc: op 10
[  7904.904] (WW) Falling back to old probe method for XRDPDEV
[  7904.904] rdpProbe:
[  7904.904] (II) Loading sub module "fb"
[  7904.904] (II) LoadModule: "fb"
[  7904.904] (II) Module "fb" already built-in
[  7904.904] rdpProbe: found DRMDevice xorg.conf value [/dev/dri/renderD128]
[  7904.904] rdpProbe: found DRI3 xorg.conf value [1]
[  7904.904] (II) XRDPDEV(0): using default device
[  7904.904] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  7904.904] rdpPreInit:
[  7904.904] rdpPreInit: /dev/dri/renderD128 open failed
[  7904.904] (**) XRDPDEV(0): Depth 24, (--) framebuffer bpp 32
[  7904.904] (==) XRDPDEV(0): RGB weight 888
[  7904.904] (==) XRDPDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[  7904.904] (==) XRDPDEV(0): Default visual is TrueColor
[  7904.904] (==) XRDPDEV(0): DPI set to (96, 96)
[  7904.904] (II) XRDPDEV(0): 	mode "640x480" ok
[  7904.904] (II) XRDPDEV(0): 	mode "800x600" ok
[  7904.904] (II) XRDPDEV(0): Virtual size is 800x600 (pitch 800)
[  7904.904] (**) XRDPDEV(0):  Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[  7904.904] (II) XRDPDEV(0): Modeline "800x600"x0.0   36.00  800<PHONE_NUMBER>  600 601 603 625 +hsync +vsync (35.2 kHz d)
[  7904.904] rdpScreenInit: virtualX 800 virtualY 600 rgbBits 8 depth 24
[  7904.904] rdpScreenInit: pfbMemory bytes 1920000
[  7904.904] rdpScreenInit: pfbMemory 0x7f99232cb010
[  7904.904] rdpSimdInit: assigning yuv functions
[  7904.904] rdpSimdInit: cpuid ax 1 cx 0 return ax 0x00a60f12 bx 0x0b200800 cx 0x7ef8320b dx 0x178bfbff
[  7904.904] rdpSimdInit: sse2 amd64 yuv functions assigned
[  7904.904] (==) XRDPDEV(0): Backing store enabled
[  7904.904] rdpClientConInit: disconnect idle session after [0] sec
[  7904.904] rdpClientConInit: kill disconnected [0] timeout [0] sec
[  7904.904] rdpClientConInit: do_touchpad_scroll_hack [0]
[  7904.904] rdpXvInit: depth 24
[  7904.904] rdpScreenInit: out
[  7904.904] (II) Initializing extension Generic Event Extension
[  7904.904] (II) Initializing extension SHAPE
[  7904.904] (II) Initializing extension MIT-SHM
[  7904.904] (II) Initializing extension XInputExtension
[  7904.904] (II) Initializing extension XTEST
[  7904.904] (II) Initializing extension BIG-REQUESTS
[  7904.904] (II) Initializing extension SYNC
[  7904.904] (II) Initializing extension XKEYBOARD
[  7904.904] (II) Initializing extension XC-MISC
[  7904.904] (II) Initializing extension SECURITY
[  7904.904] (II) Initializing extension XFIXES
[  7904.904] (II) Initializing extension RENDER
[  7904.904] (II) Initializing extension RANDR
[  7904.904] (II) Initializing extension COMPOSITE
[  7904.905] (II) Initializing extension DAMAGE
[  7904.905] (II) Initializing extension MIT-SCREEN-SAVER
[  7904.905] (II) Initializing extension DOUBLE-BUFFER
[  7904.905] (II) Initializing extension RECORD
[  7904.905] (II) Initializing extension DPMS
[  7904.905] (II) Initializing extension Present
[  7904.905] (II) Initializing extension DRI3
[  7904.905] (II) Initializing extension X-Resource
[  7904.905] (II) Initializing extension XVideo
[  7904.905] (II) Initializing extension XVideo-MotionCompensation
[  7904.905] (II) Initializing extension SELinux
[  7904.905] (II) SELinux: Disabled on system
[  7904.905] (II) Initializing extension GLX
[  7904.905] (II) AIGLX: Screen 0 is not DRI2 capable
[  7904.917] (II) IGLX: Loaded and initialized swrast
[  7904.917] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  7904.917] (II) Initializing extension XFree86-VidModeExtension
[  7904.918] (II) Initializing extension XFree86-DGA
[  7904.918] (II) Initializing extension XFree86-DRI
[  7904.918] (II) Initializing extension DRI2
[  7904.918] rdpCreateScreenResources:
[  7904.926] (II) Using input driver 'XRDPMOUSE' for 'xrdpMouse'
[  7904.926] (**) Option "CorePointer"
[  7904.926] (**) xrdpMouse: always reports core events
[  7904.926] rdpmousePreInit: drv 0x5601ff29a9a0 info 0x5601ff594980, flags 0x0
[  7904.926] (II) XINPUT: Adding extended input device "xrdpMouse" (type: Mouse, id 6)
[  7904.926] rdpmouseControl: what 0
[  7904.926] rdpmouseDeviceInit:
[  7904.926] rdpmouseCtrl:
[  7904.926] rdpRegisterInputCallback: type 1 proc 0x7f992448e430
[  7904.926] (**) xrdpMouse: (accel) keeping acceleration scheme 1
[  7904.926] (**) xrdpMouse: (accel) acceleration profile 0
[  7904.926] (**) xrdpMouse: (accel) acceleration factor: 2.000
[  7904.926] (**) xrdpMouse: (accel) acceleration threshold: 4
[  7904.926] rdpmouseControl: what 1
[  7904.926] rdpmouseDeviceOn:
[  7904.926] (II) Using input driver 'XRDPKEYB' for 'xrdpKeyboard'
[  7904.926] (**) Option "CoreKeyboard"
[  7904.926] (**) xrdpKeyboard: always reports core events
[  7904.926] rdpkeybPreInit: drv 0x5601ff29bf00 info 0x5601ff597b60, flags 0x0
[  7904.926] (II) XINPUT: Adding extended input device "xrdpKeyboard" (type: Keyboard, id 7)
[  7904.926] rdpkeybControl: what 0
[  7904.926] rdpkeybDeviceInit:
[  7904.931] rdpkeybChangeKeyboardControl:
[  7904.931] rdpkeybChangeKeyboardControl: autoRepeat on
[  7904.931] rdpRegisterInputCallback: type 0 proc 0x7f992390cb30
[  7904.931] rdpkeybControl: what 1
[  7904.931] rdpkeybDeviceOn:
[  7904.931] rdpkeybChangeKeyboardControl:
[  7904.931] rdpkeybChangeKeyboardControl: autoRepeat on
[  7904.935] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[  7904.935] (II) AutoAddDevices is off - not adding device.
[  7904.936] (II) config/udev: Adding input device Video Bus (/dev/input/event2)
[  7904.936] (II) AutoAddDevices is off - not adding device.
[  7904.936] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[  7904.936] (II) AutoAddDevices is off - not adding device.
[  7904.936] (II) config/udev: Adding drm device (/dev/dri/card1)
[  7904.936] (II) xfree86: Adding drm device (/dev/dri/card1)
[  7904.936] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card1
[  7904.936] (EE) systemd-logind: failed to take device /dev/dri/card1: Operation not permitted
[  7904.936] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event6)
[  7904.936] (II) AutoAddDevices is off - not adding device.
[  7904.936] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event7)
[  7904.936] (II) AutoAddDevices is off - not adding device.
[  7904.936] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event4)
[  7904.936] (II) AutoAddDevices is off - not adding device.
[  7904.936] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event5)
[  7904.936] (II) AutoAddDevices is off - not adding device.
[  7904.937] (II) config/udev: Adding input device MSI MYSTIC LIGHT  (/dev/input/event3)
[  7904.937] (II) AutoAddDevices is off - not adding device.
[  7904.937] (II) config/udev: Adding drm device (/dev/dri/card0)
[  7904.937] (II) xfree86: Adding drm device (/dev/dri/card0)
[  7904.937] (II) Platform probe for /sys/devices/pci0000:00/0000:00:08.1/0000:18:00.0/drm/card0
[  7904.937] (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted
[  7904.937] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=3 (/dev/input/event8)
[  7904.937] (II) AutoAddDevices is off - not adding device.
[  7904.937] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=7 (/dev/input/event9)
[  7904.937] (II) AutoAddDevices is off - not adding device.
[  7904.937] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=8 (/dev/input/event10)
[  7904.937] (II) AutoAddDevices is off - not adding device.
[  7904.937] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=9 (/dev/input/event11)
[  7904.937] (II) AutoAddDevices is off - not adding device.
[  7904.939] rdpDeferredRandR:
[  7904.939] rdpResizeSession: width 1024 height 768
[  7904.939]   calling RRScreenSizeSet
[  7904.939] rdpRRScreenSetSize: width 1024 height 768 mmWidth 271 mmHeight 203
[  7904.939] rdpRRGetInfo:
[  7904.939]   screen resized to 1024x768
[  7904.940]   RRScreenSizeSet ok 1
[  7904.940] rdpResizeSession: width 1440 height 900
[  7904.940]   calling RRScreenSizeSet
[  7904.940] rdpRRScreenSetSize: width 1440 height 900 mmWidth 381 mmHeight 238
[  7904.940] rdpRRGetInfo:
[  7904.940]   screen resized to 1440x900
[  7904.941]   RRScreenSizeSet ok 1
[  7904.993] rdpClientConGotConnection:
[  7904.993] rdpClientConGotConnection: g_sck_accept ok new_sck 9
[  7904.993] rdpClientConGetConnection: idle_disconnect_timeout set to non-positive value, idle timer turned off
[  7904.993] rdpAddClientConToDev: adding first clientCon 0x5601ff5c2b50
[  7904.993] rdpClientConProcessMsgVersion: version 0 0 0 1
[  7904.993] rdpClientConProcessScreenSizeMsg: set width 1440 height 900 bpp 15
[  7904.993] rdpClientConAllocateSharedMemory: shmemid 9 shmemptr 0x7f9917494000 bytes 2592000
[  7904.993] rdpClientConProcessMsgClientInput: invalidate x 0 y 0 cx 1440 cy 900
[  7904.993] KbdSync: toggling num lock
[  7904.994] rdpkeybChangeKeyboardControl:
[  7904.994] rdpkeybChangeKeyboardControl: autoRepeat on
[  7905.031] rdpInDeferredRepeatCallback:
[  7905.031] rdpkeybChangeKeyboardControl:
[  7905.031] rdpkeybChangeKeyboardControl: autoRepeat off
[  7905.031] rdpInDeferredRepeatCallback:
[  7905.031] rdpkeybChangeKeyboardControl:
[  7905.031] rdpkeybChangeKeyboardControl: autoRepeat off
[  7905.094] rdpInDeferredRepeatCallback:
[  7905.094] rdpkeybChangeKeyboardControl:
[  7905.094] rdpkeybChangeKeyboardControl: autoRepeat off
[  7905.194] rdpClientConProcessMsgClientInfo:
[  7905.194]   got client info bytes 7072
[  7905.194]   jpeg support 0
[  7905.194]   offscreen support 1
[  7905.194]   offscreen size 5242880
[  7905.194]   offscreen entries 100
[  7905.194]   client can not do offscreen to offscreen blits
[  7905.194]   client can do new(color) cursor
[  7905.194]   client can not do multimon
[  7905.194] rdpRRSetRdpOutputs: numCrtcs 0 numOutputs 0 monitorCount 0
[  7905.194] rdpRRSetRdpOutputs: add output 0 left 0 top 0 width 1440 height 900
[  7905.194] rdpLoadLayout: keylayout 0x00020409 variant  display 11
[  7905.194] rdpkeybChangeKeyboardControl:
[  7905.194] rdpkeybChangeKeyboardControl: autoRepeat on
[  7905.194] rdpkeybChangeKeyboardControl:
[  7905.194] rdpkeybChangeKeyboardControl: autoRepeat on
[  7905.294] rdpInDeferredRepeatCallback:
[  7905.294] rdpkeybChangeKeyboardControl:
[  7905.294] rdpkeybChangeKeyboardControl: autoRepeat off
[  7905.294] rdpInDeferredRepeatCallback:
[  7905.294] rdpkeybChangeKeyboardControl:
[  7905.294] rdpkeybChangeKeyboardControl: autoRepeat off
[  7980.026] KbdSync: toggling num lock
[  7980.026] rdpkeybChangeKeyboardControl:
[  7980.026] rdpkeybChangeKeyboardControl: autoRepeat off
[  7980.026] rdpkeybChangeKeyboardControl:
[  7980.026] rdpkeybChangeKeyboardControl: autoRepeat off
[  7982.141] rdpClientConRecv: g_sck_recv failed(returned 0)
[  7982.141] rdpClientConRecvMsg: error
[  7982.141] rdpClientConCheck: rdpClientConGotData failed
[  7982.141] rdpClientConDisconnect:
[  7982.141] rdpRemoveClientConFromDev: removing clientCon 0x5601ff5c2b50

Any idea what could be behind this?

Update: In the end, I've decided to go with @Nexarian's approach (nvidia support) and it solved my issue (though I had to edit the installation script to prevent removal of my already installed cuda packages). Also I wonder why dbus-user-session is uninstalled by @Nexarian's script, given that snap dependent applications (firefox) stopped working and I suspect it could be related to this removal (according to this thread).
One thing to note: My first connection attempt failed with the same error message as in https://github.com/neutrinolabs/xrdp/issues/2063. Looking at /var/log/xrdp.log, I saw the error xrdp_mm_egfx_send_planar_bitmap: xrdp_egfx_send_frame_end error, which I felt could be related to my video settings on my RDP client. So I changed my video mode from 15 bits to 32 bits and everything worked fine.

Please try this:
sudo nano /etc/xrdp/startwm.sh
And then add this line at the end of the file:
export $(dbus-launch)
between:
fi
and
test -x /etc/X11/Xsession && exec /etc/X11/Xsession
so it should should look something like this:
fi

export $(dbus-launch)

test -x /etc/X11/Xsession && exec /etc/X11/Xsession

save the file (CTRL+X Y ENTER)
reload daemon: sudo systemctl daemon-reload
restart xrdp server: sudo systemctl restart xrdp.service
Try connecting now, it should work (tested on Debian).
If it's still blackscreen, restart machine.
If it's still blackscreen, logout from DE on your ssh machine, and try connecting again (xrdp by default doesn't like allowing the same user into an RDP session, that is what those modified lines are for in the startwm.sh I mentioned)
Hope it helps :)

Please try this: sudo nano /etc/xrdp/startwm.sh

Works on Ubuntu 24.04.1 with Intel graphics.

Is there a solution in the meantime or only a work around? Since the ticke status has been "closed" all the time i have no idea what to expect from 22.x or 24.x releases. I still have a hard time getting remote connections working with these environments and i would not consider this as an "out of the box" feature yet if there are no positive reports.

22.x and 24.x are Ubuntu releases. If you expect something to Ubuntu, report it to Ubuntu Team.


On close Min to system tray option

What feature or improvement do you think would benefit Files?
Faster load time number 1
Requirements
win11
Files Version
win11
Windows Version
win11
Comments
No response

Merging with #11279.


update site

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rawlingsj
If they are not already assigned, you can assign the PR to them by writing /assign @rawlingsj in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

:star: PR built and available in a preview environment cb-kubecd-office-hours-1-pr-1 here

/test this

:star: PR built and available in a preview environment cb-kubecd-office-hours-1-pr-1 here


Replace some .src expansion with macros

This replaces the simple instances of .src expansion (where the whole file is expanded to a float and double version) with macros. Essentially: @type@_xyz becomes CAT(TYPE, _xyz), where TYPE must be defined where the template file is included. CAT is defined in templating.h
The main advantage is greatly improved compiler diagnostics (and debugging with GDB), because the compiler actually knows where the problematic lines came from.
My other work (fast dwtn, swt) is based on top of this, because it is much easier to work with the C parts.

This all looks good to me.  I appreciate the work you have been putting into improving the usability of the C code.

AppVeyor passed.

Looks good to me too. The extra lines needed in setup.py are a small price to pay for the gains you get here.

Looks good and other PRs depend on this, so let's just get it in. Thanks @kwohlfahrt


Add owners files

@filanov @eranco74 does this look good for a start or should I add more people?

No prow yet, so I'm merging manually.


⚠ Bofrost.at has degraded performance

In 388facd, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1587 ms

Resolved: Bofrost.at performance has improved in aada9d6.


fix assorted typos (CONTRIBUTING, README, diffie-hellman, perfect-numbers, robot-simulator)

Looks good :+1:


Unable to setup vms,when starting it using virtctl the pod is running and than going in terminating phase

kubectl logs virt-launcher-testvm-d8s75 is giving
**{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-04-24T23:36:20.237487Z"}
{"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-04-24T23:36:20.237558Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu+unix:///session?socket=/var/run/libvirt/virtqemud-sock","pos":"libvirt.go:519","timestamp":"2023-04-24T23:36:20.238618Z"}
{"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:527","timestamp":"2023-04-24T23:36:20.238934Z"}
{"component":"virt-launcher","level":"error","msg":"failed to start virtqemud","pos":"libvirt_helper.go:250","reason":"fork/exec /usr/sbin/virtqemud: errno 0","timestamp":"2023-04-24T23:36:20.239471Z"}
panic: fork/exec /usr/sbin/virtqemud: errno 0
goroutine 19 [running]:
kubevirt.io/kubevirt/pkg/virt-launcher/virtwrap/util.LibvirtWrapper.StartVirtquemud.func1()
pkg/virt-launcher/virtwrap/util/libvirt_helper.go:251 +0x4ce
created by kubevirt.io/kubevirt/pkg/virt-launcher/virtwrap/util.LibvirtWrapper.StartVirtquemud
pkg/virt-launcher/virtwrap/util/libvirt_helper.go:218 +0x65
{"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 12 with status 512","pos":"virt-launcher-monitor.go:120","timestamp":"2023-04-24T23:36:20.244316Z"}
{"component":"virt-launcher-monitor","level":"error","msg":"dirty virt-launcher shutdown: exit-code 2","pos":"virt-launcher-monitor.go:138","timestamp":"2023-04-24T23:36:20.244506Z"}**
I have checked the libvrt daemon,its running perfectly fine,also restarted it multiple times but still no luck.Also triend uninstalling and re-installing kubevirt but issue is still not solved

As per official doc for setup on minikube it is supposed to have 7 pods running in kubevirt namespace but its showing only 6,replica set,daemon set and deployments are all running fine

Looks similar to https://github.com/kubevirt/kubevirt/issues/9511. Try running minikube with containerd: minikube start --container-runtime=containerd

Tanks @vasiliy-ul  minikube start --container-runtime=containerd worked for me


[KYUUBI #825] Introduce jcommander framework to kyuubi project

Why are the changes needed?
Fixes #825
For more details, please go to #775
Hi @yaooqinn @pan3793,
Here's the patch base on JCommander in scala, please point out if the scala grammar is not used correctly.
The following usage is generated from JCommander, I think it seems a bit long for users, we can discuss it here.
By the way, we can use the format of bookkeeper-ctl‘s usage.
Thanks.
Usage: kyuubi-ctl <server|engine> <create|get|delete|list> [options]
[ ENGINE ]
get
  -s, --host       Hostname or IP address of a service.
  -u, --user       The user name this engine belong to.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -p, --port       Listening port of a service.
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -h, --help
delete
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -p, --port       Listening port of a service.
  -s, --host       Hostname or IP address of a service.
  -u, --user       The user name this engine belong to.
  -h, --help
list
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -p, --port       Listening port of a service.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -u, --user       The user name this engine belong to.
  -s, --host       Hostname or IP address of a service.
  -h, --help

[ SERVER ]
create
  -s, --host       Hostname or IP address of a service.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -p, --port       Listening port of a service.
  -h, --help
get
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -h, --help
delete
  -s, --host       Hostname or IP address of a service.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -p, --port       Listening port of a service.
  -h, --help
list
  -p, --port       Listening port of a service.
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -s, --host       Hostname or IP address of a service.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -h, --help

BooKKeeper CTL Usage
1. Totoal Usage
[bookkeeper-all-4.13.0]$ bin/bkctl
bkctl interacts and operates Apache BookKeeper clusters

Usage:  bkctl [flags] [command group] [commands]

    cookie              Commands on operating cookies

Infrastructure commands :

    autorecovery        Command on some specific operation.
    bookie              Commands on operating a single bookie
    bookieid            Commands operating on bookie ids
    bookies             Commands on operating a cluster of bookies
    cluster             Commands on administrating bookkeeper clusters

2. When choose one command
[bookkeeper-all-4.13.0]$ bin/bkctl bookie
Commands on operating a single bookie

Usage:  bkctl bookie [command] [command options]

Commands:

    converttodbstorage                              Convert bookie indexes from
                                                    InterleavedStorage to DbLedgerStorage format
    converttointerleavedstorage                     Convert bookie indexes from
                                                    DbLedgerStorage to InterleavedStorage
                                                    format
    endpointinfo                                    Get all end point
                                                    information about a given bookie.
    flip-bookie-id                                  Update bookie id in ledgers
                                                    (this may take a long time).
    format                                          Format the current server

How was this patch tested?

[X] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

After second thought and have a discussion with @turboFei (author of this the first version of kyuubi-ctl),  I change my vote to kyuubi-ctl <create|get|delete|list> <server|engine> options. It's because

some tools use cmd action object, i.e. kubectl, some tools chose cmd subcmd subcmd, both are widely used.
one of the fact is that kyuubi-ctl list service and kyuubi-ctl list engine are almost the same things except for the znode root path, and we can reuse lots code if chose the pattern cmd action object

I am planning that we have a command like kyuubi-ctl [create|get|delete|list] config or kyuubi-ctl config [create|get|delete|list]. with this, which way is right to go? @turboFei @timothy65535 @pan3793

@yaooqinn would you please add some details or demos on config? in my view, the chosen will be based on the code reused rate.

create, apply a config to a running server(maybe)or a configuration file
list, get and validate all configurations in the configuration file(can be configured with -f -type (spark|kyuubi))
get, get a single config's config entry with doc, version, key, value, etc
delete, unapply a config to a running server(maybe) or a configuration file

or something.

kyuubi-ctl config [create|get|delete|list] makes more sense to me, and I suggest change create to set, delete to remove for object config, in other words, we can use independent action words for different objects.

Codecov Report

Merging #826 (90b8ccf) into master (bf0042c) will decrease coverage by 1.56%.
The diff coverage is 30.00%.

:exclamation: Current head 90b8ccf differs from pull request most recent head 9737563. Consider uploading reports for the commit 9737563 to get more accurate results

@@             Coverage Diff              @@
##             master     #826      +/-   ##
============================================
- Coverage     78.60%   77.04%   -1.57%
  Complexity       10       10
============================================
  Files           135      149      +14
  Lines          5123     5293     +170
  Branches        642      646       +4
============================================
+ Hits           4027     4078      +51
- Misses          745      859     +114
- Partials        351      356       +5

Impacted Files
Coverage Δ

...he/kyuubi/ctl/commands/common/UnixStyleUsage.scala
0.00% <0.00%> (ø)

.../kyuubi/ctl/commands/config/SetConfigCommand.scala
0.00% <0.00%> (ø)

...uubi/ctl/commands/server/CreateServerCommand.scala
0.00% <0.00%> (ø)

...uubi/ctl/commands/server/DeleteServerCommand.scala
0.00% <0.00%> (ø)

.../kyuubi/ctl/commands/server/GetServerCommand.scala
0.00% <0.00%> (ø)

...kyuubi/ctl/commands/server/ListServerCommand.scala
0.00% <0.00%> (ø)

...uubi/ctl/commands/engine/DeleteEngineCommand.scala
18.18% <18.18%> (ø)

...kyuubi/ctl/commands/engine/ListEngineCommand.scala
18.18% <18.18%> (ø)

...yuubi/ctl/commands/server/ServerCommandGroup.scala
22.22% <22.22%> (ø)

...yuubi/ctl/commands/config/ConfigCommandGroup.scala
33.33% <33.33%> (ø)

... and 18 more

Continue to review full report at Codecov.

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

Hi @yaooqinn @pan3793, review again when you are free , thanks.
cmd examples

input --help

Usage: kyuubi-ctl <server|engine|config> [actions] [options]

  engine  Commands on operating engine
  server  Commands on operating server
  config  Commands on operating config

input server --help

Usage: kyuubi-ctl server [actions] [options]
create
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help
get
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help
delete
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help
list
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help

input server get --help

get
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using
                     zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help

Easy to add new more service / command

Add new command which extends Command
Add the new command to service command group
If add new service type, need to update Kyuubi
ok

cc @turboFei PTAL

Hi @yaooqinn @pan3793 @turboFei, review again when you are free , thanks.
cmd examples

input --help

Usage: kyuubi-ctl <server|engine|config> [actions] [options]

  engine  Commands on operating engine
  server  Commands on operating server
  config  Commands on operating config

input server --help

Usage: kyuubi-ctl server [actions] [options]
create
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help
get
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help
delete
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help
list
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help

input server get --help

get
  -zk, --zk-quorum The connection string for the zookeeper ensemble, using
                     zk quorum manually.
  -n, --namespace  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host       Hostname or IP address of a service.
  -p, --port       Listening port of a service.
  -h, --help

Easy to add new more service / command

Add new command which extends Command
Add the new command to service command group
If add new service type, need to update Kyuubi
ok

the behavior changes a lot for each command, the acceptable args change from cmd to cmd

The usage in master branch
Usage: kyuubi-ctl [create|get|delete|list] [options]

  -zk, --zk-quorum <value>
                           The connection string for the zookeeper ensemble, using zk quorum manually.
  -n, --namespace <value>  The namespace, using kyuubi-defaults/conf if absent.
  -s, --host <value>       Hostname or IP address of a service.
  -p, --port <value>       Listening port of a service.
  -v, --version <value>    Using the compiled KYUUBI_VERSION default, change it if the active service is running in another.
  -b, --verbose            Print additional debug output.

Command: create [server]

Command: create server
        Expose Kyuubi server instance to another domain.

Command: get [server|engine] [options]
        Get the service/engine node info, host and port needed.
Command: get server
        Get Kyuubi server info of domain
Command: get engine
        Get Kyuubi engine info belong to a user.
  -u, --user <value>       The user name this engine belong to.

Command: delete [server|engine] [options]
        Delete the specified service/engine node, host and port needed.
Command: delete server
        Delete the specified service node for a domain
Command: delete engine
        Delete the specified engine node for user.
  -u, --user <value>       The user name this engine belong to.

Command: list [server|engine] [options]
        List all the service/engine nodes for a particular domain.
Command: list server
        List all the service nodes for a particular domain
Command: list engine
        List all the engine nodes for a user
  -u, --user <value>       The user name this engine belong to.

  -h, --help               Show help message and exit.

Each different command uses its own command parameters to be more extensible.

Hi @pan3793 @yaooqinn thanks for the suggestion, patch is updated accordingly, can you please take another look. BTW, sorry for the delay, there are a lot of things to deal with in the past week.

maybe we can do it group by group

maybe we can do it group by group

First step is introduce framework to kyuubi project, we can discuss the design of the command frammework.
Next plan:

[ ] Implement engine part
[ ] Implement service part


test fails to find standard lib import

gb test is failing to find the net/http/httptest subdirectory
// src/foo/foo_test.go
package main

import (
	"net/http/httptest"
	"testing"
)

func TestFoo(t *testing.T) {
	_ = httptest.NewRequest("", "https://example.com", nil)
}

$ gb test -a
foo_test.go:9: undefined: httptest.NewRequest
FATAL command "test" failed: exit status 2

I'm not able to reproduce this issue, see #681 for a test that confirms this.

Hmm, looks like httptest may not have existed in 1.6 and earlier. Let me check.

Yup, httptest.NewRequest was added in Go 1.7.
If you have upgraded your Go installation you must rebuild gb. Sorry about this limitation, it's not an easy one to overcome.

@davecheney Thanks for the lightning fast followup and resolution!

No worries.
On Tue, Dec 13, 2016 at 4:14 PM, bndw<EMAIL_ADDRESS>wrote:

@davecheney https://github.com/davecheney Thanks for the lightning fast
followup and resolution!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/constabulary/gb/issues/680#issuecomment-266644995,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAcAzWT2urLfA75_2-B12qBB7_SOjiSks5rHim5gaJpZM4LLRKZ
.


Adding the Open in Cloud Shell button + tutorial in Cloud Shell

The Open in Cloud Shell button lets users clone the repository into their Cloud Shell (https://cloud.google.com/shell/) instance, so they can try the samples without having to install the SDK.
The Quickstart tutorial is a tutorial based in Cloud Shell, similar to this, which guides users through the same steps as the Quickstart.

This is awesome.


false positive: no matching method found

Running report_package on a package with this code
module M
function children end
function traverse(root)
    children(root)
end
end

...I get
═════ 1 possible error found ═════
┌ @ ... M.children(root)
│ no matching method found `children(::Any)`: M.children(root::Any)

However, if I add an implementation of children for any type, I don't get any error.
module M
function children end
function traverse(root)
    children(root)
end
children(::Int) = 2
end

Since there's no way to define interfaces in julia, I would say that declaring the function children should be enough for JET for not to complain about the "children" function
thanks!

This is expected. JET should report error when the interface is missing the required implementation.

Because you're using the default unsound analysis mode. You can use report_package(...; mode=:sound) to use the sound mode, although it usually results in lots of false positives reports.

Hi,
thanks for your quick answer, but I get the same error with :sound
julia> report_package("SCEngine";mode=:sound)
[toplevel-info] virtualized the context of Main (took 0.02 sec)
[toplevel-info] entered into /home/dani/source/repos/sc-engine/src/SCEngine.jl
[ Info: Loading module SCEngine
[toplevel-info]  exited from /home/dani/source/repos/sc-engine/src/SCEngine.jl (took 2.527 sec)
[toplevel-info] analyzing from top-level definitions (2/2)
[toplevel-info] analyzed 2 top-level definitions (took 1.907 sec)
═════ 334 possible errors found ═════
┌ @ M.children(root)
│ no matching method found `children(::Any)`: M.children(root::Any)

I guess that the error message means you are missing any children implementation.

To summarize:

when there aren't any implementation: both :basic and :sound mode should report an error
when there is some implementation available but the interface signature isn't fully covered: only the :sound mode should report an error


[ Bug ] Level Up pop-up don't work in Custom Games with Tournament Code

Describe the bug
The Level Up Pop-up don't always work in Custom Games with Tournament codes
To Reproduce
Steps to reproduce the behavior:

Create a custom game with a Tournament Code
Spectate the game
Wait until a champion get his level X (6 in this example)
Sometimes nothing is shown, somethimes the same level up play again and again until I desactivate it in localhost:3003

Expected behavior
When a champion get to X level, play the pop-up once.
Screenshots
https://clips.twitch.tv/CarelessSmilingSalmonRedCoat-DEs6ftIjqU9tZP1-
System:

OS: Windows 10
Node: 16.7
Prod Tool Version: 1.8.0
Observer Tool Version: 6.7.4
Streaming Software & Version: OBS Studio
Browser: Opera GX

The Item pop-up seems to work properly tho... So I don't know what is the specific issue here.

Are you sure this problem is exclusive to games with a tournament code, and doesn't just happen in general?
It might be related to the account name change, the ingame API which provides this info is a bit broken at the moment...

Hmmm weird. In a replay game I downloaded, it was working fine. I'll test again with another replay tomorrow to see ifI can replicate it or not.

At the moment riot has some issues with adapting to there own changes for the ingame API, we will try to implement so fixes for that regardless.
for more information, check out this issue  https://github.com/RiotGames/developer-relations/issues/857

This is what I thought. Thanks for the rapid follow up. As long as it don't break farsight or the observer tool, I can just disable level up and items if needed for now and work with everything else.

It should not affect farsight as far as we can tell so just deactivating level ups and items, everything should work fine

After some testing and investigation, we found out that, in this case, the riot API was not the problem.
Instead, the tool tried to save player - levels multiple times which caused this issue. This was fixed with the new patch to the in-game module.


Compiler fails with a Bad Sad error when resource method has return instead of returns

Description:
Compiler fails with a Bad Sad error when resource method has return instead of returns. Ideally, we need to show a proper error and fail without causing a Bad Sad error.
Steps to reproduce:
Compiler the following code
import ballerina/http;
service echo_service on new http:Listener(8090) {
    resource function test1(http:Caller caller, http:Request req) return error? {
        var result = caller->respond("Hello World!");
        if (result is error) {
        }
    }
}

Ballerina Internal Log - ballerina-internal.log
Affected Versions:
Ballerina Swan Lake Preview 4
OS, DB, other environment details and versions:
Ubuntu 20

Fixed in current master/alph2.


[OAP-1610][remote-shuffle][SDle]Upgrade mockserver-netty version to 5…

….11.0 to pass Snyk scannning
What changes were proposed in this pull request?
Upgrade mockserver-netty version from 5.6.0 to 5.11.0 in order to pass Snyk scanning of SDLe task.
How was this patch tested?
Pass UT and Snyk vulnerability scanning.

@carsonwang Will the version upgrade on mockserver-netty & mockserver-client-java to 5.11.0 bring more impact on remote-shuffle? if not, we  need upgrade it to pass Snyk vulnerability scanning, for version 5.6.0 is detected with vulnerabilities.

LGTM


fix: allow specifying websocket port

A Replit user reached out with pain getting a Reflex app set up on Replit. After some digging, this change seems to make the pain vanish
As a short explanation of why:

all Replit projects are Docker containers
we have reverse proxies set up to route traffic to repls given some URL, eg https://f3ea4bab-7ba5-4eb2-9ad4-9ec4f3702158-00-1squ4svnaus5u.infra-staging.replit.dev/
we may also do port mapping to make the experience as pleasant as possible, eg 3000->80 for http ports
because this is happening over the internet, we do also support auto tls promotion, which means that content being served from a project running in dev mode (eg reflex dev) will probably be accessed via https://
all of this results in the next server being served over :443, but the web socket still being provided via wss on :8080

this change allows the next server's client to connect to the wss websocket on :8080 as expected

all of this results in the next server being served over :443, but the web socket still being provided via wss on :8080

i'm unsure about this line; is replit terminating TLS for the websocket separately and mapping 8080 external -> 8000 internal?

is replit terminating TLS for the websocket separately and mapping 8080 external -> 8000 internal?

In our case, we were doing
config = rx.Config(
    ...
    backend_port=8080,
    api_url=f"wss://{replit_dev_domain}:8080"
)

which is where 8080 is coming from. We're doing wss://...:8080 external -> ws://...:8080 internal. It should be equivalent to 8000 external being mapped to 8000 internal, iiuc.

Interesting. If the api_url is being set explicitly to something that is not one of the SAME_DOMAIN_HOSTNAMES then i would have expected the line changed in the patch to not even be executed. This endpoint rewriting logic should only be occuring if the api_url is localhost.
// These hostnames indicate that the backend and frontend are reachable via the same domain.
const SAME_DOMAIN_HOSTNAMES = ["localhost", "<IP_ADDRESS>", "::", "0:0:0:0:0:0:0:0"];

I may be mistaken then. @cdmistman, were you still using the port override, or did we back out the configuration change and just 8080 -> 8000?

ah sorry, it seems there's been some work since this project was vanilla!
give me a sec, i'm gonna revalidate this patch from a fresh reflex project...

ah ok yes - @blast-hardcheese when we were walking through this a few mins ago we didn't get the same problem, but the patch from this PR isn't sufficient to fix the problems here, there's still another part missing
@masenf if you'd like to TAL, you can fork this Repl to a Replit account and click the run button, you'll see the websocket error pop up once everything's running https://replit.com/@coltonatreplit/CriminalEnchantingEfficiency

So, my full reproducing case is:

reflex init, choose the sidebar template
✍ Modify rxconfig.py to add backend_port=8080, to work around the aforementioned port binding bug
✍ Configure the VM to have 443 -> 3000 and 8080 -> 8080
❌ Observe that the UI is loadable at https://${uuid}.replit.dev/ and I see attempts to connect to wss://${uuid}.replit.dev/ as well (note missing port), the protocol switch is not handled by the UI server, and the Cannot connect to server: timeout popup (first screenshot below) is shown.
✍ Modify .web/utils/state.js to introduce @cdmistman 's change
✅ Loading the same URL as before, https://${uuid}.replit.dev/, observe that wss://... now includes port :8080 (screenshot two)

@blast-hardcheese got it, thanks for the explanation.
It sounds like you're wanting to take advantage of the automatic hostname rewriting without also assuming the wss port will be the standard https port 443.
Am I correct in my previous observation that setting api_url="https://actual-hostname.repl.it:8080" in the rxconfig.py does work around this issue without the patch being proposed here?
I'm hesitant to accept the patch as-is because it would be a behavioral regression that would break common load balancer setups that we've been recommending over the past 6 months or so. But I do want to find a solution that minimizes the amount of configuration we expect end users to do and understand.
I'm currently leaning to a solution wherein (when connecting to the frontend over https)

the api_url is set to https://localhost:8080

do not strip off the port
assume you want to connect to wss://{frontend}:8080

the api_url is set to http://localhost:8080 (the default)

strip off the port
assume you want to connect to wss://{frontend}

In this configuration, you would still have to set api_url yourself, but you could set it to a generic value and take advantage of the hostname rewriting.

I have confirmed that the following in rxconfig.py does work:
import reflex as rx
import os

replit_dev_domain = os.getenv("REPLIT_DEV_DOMAIN")

config = rx.Config(
    app_name="reflex_test",
    backend_port=8080,
    api_url=f"https://{replit_dev_domain}:8080"
)

For context, what is the underlying rationale for dropping the port? You mention common load-balancer setups, are you referring to production environments multiplexing both servers on the same port, either via path matching or protocol matching?
One solution we discussed internally was to expose a websocket proxy from the frontend repo to the backend, possibly printing a helpful WARN: Using a development websocket proxy! For improved performance, see [docs link](...).
The downside would be that you'd have a larger surface area to maintain, and it may obscure the error if the user doesn't notice that they're using the dev proxy in production, but maybe this is mitigated by misconfigurations just being slow instead of correlating with downtime for the user.

You mention common load-balancer setups, are you referring to production environments multiplexing both servers on the same port, either via path matching or protocol matching?

Yeah exactly. We recommend setting up either caddy or nginx to terminate TLS and have the webserver proxy the requests to the correct port. I would say it's less common to have TLS for the websocket terminated separately on an uncommon port.

expose a websocket proxy from the frontend repo to the backend

I've played around with this a bit in the last couple of week, but the other direction: hitting the backend on / actually proxies to the frontend (or a static export of the same). It seems to work pretty well, but is currently still PoC and the performance is less than stellar.

Another option for this specific usage is to special case the REPLIT_DEV_DOMAIN like we do for github codespaces: https://github.com/reflex-dev/reflex/blob/6420fb12526bed1d76e94fdfc1c6fdabbb2c3638/reflex/config.py#L319-L329
Then we could get it working out of the box and even workaround the port 8000 / 8080 issue for users automatically.

I've played around with this a bit in the last couple of week, but the other direction: hitting the backend on / actually proxies to the frontend (or a static export of the same). It seems to work pretty well, but is currently still PoC and the performance is less than stellar.

Yeah, I'd imagine that the frontend would involve sending quite a bit more content than would otherwise be transferred over the websocket port, but definitely quite a bit easier to maintain.

Another option for this specific usage is to special case the REPLIT_DEV_DOMAIN like we do for github codespaces:

That seems like a good idea. Good news is the fix for :8000 is going out shortly, so that shouldn't be an issue. I'll open a PR to add support for REPLIT_DEV_DOMAIN for the time being, and wherever you decide to land on the 8000-over-3000 or 3000-over-8000 should be fine.
Thank you!

I'll open a PR to add support for REPLIT_DEV_DOMAIN for the time being

Aweomse! that should be a much less controversial change. Thanks for helping unpack this issue.
I've playing around with reflex on repl.it and it's quite nice to work with and feels faster than codespaces. I definitely could see myself using this for sharing repros and helping users debug their code.

glad to hear you like it! also glad to hear a better solution was agreed upon. thank you @masenf for working with us on this problem!

I have confirmed that the following in rxconfig.py does work:

Turns out I had forgotten to revert the manual changes to state.js. When I did so, the bug reappeared, so I am convinced that the change laid out in this PR is actually the correct one. To avoid impinging on your efforts to help folks productionize reflex, I gated it behind a suffix check, hostname.endsWith('replit.dev'), which is spiritually equivalent to the previously agreed upon workaround similar to what was done for codespaces.
Happy to remove that check once the non-prod-one-port solution has been found. Thank you!


test-branch/execute-job/quoted-authorization/f5789259-82d9-471d-9d98-2f740dc644f4

PR for testing c6a75dca1d8c9e40be8a993572c0126bcdc33047

/canonical/self-hosted-runners/run-workflows c6a75dca1d8c9e40be8a993572c0126bcdc33047


Protected domains

If the domain is protected, like on stage domains with a basic auth, it does need additional server config, to make it work.
One way could be a static url prefix which can be opened on the server by default, or just something /.well-known/synco-token

good point :) I'll try to add to the wizard that it asks for the user and password in this case.

Hi there, my script hero!
Any progress on this?

Hey @jonnitto ,
The workaround for URLs behind HTTP basic authentication is to specify the URL with:
<EMAIL_ADDRESS>- we have recently tested this and it works. As soon as I find some time I also want to include this in synco; but it is hard to estimate currently.
All the best,
Sebastian


Apple store reject UIWebView

Dear Developer,
We identified one or more issues with a recent delivery for your app, "AppName" AppVersion. Please correct the following issues, then upload again.ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability.

How to resolve these issue ? i am facing these since 1 month.


EPEERINVALID Error on npm (2) install

It seems like React 15 is being loaded, but it's the wrong version (too high) for a couple of other components. This breaks npm install rsg-alt for npm 2.
npm ERR! node v4.2.1
npm ERR! npm  v2.14.12
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>

Are you trying to use react 15 with rsg, or is it somehow trying to use react 15 when you install rsg?
I haven't tried anything with 15 yet, but I'm open to a PR if you want to look into it.

This was a completely blank folder that I installed in, so it looks like React 15.0.1 is being installed, but your dependencies require 0.14.0 to be satisfied/run properly.
I'm planning on looking into this, using this project with React 15 and having it support functional components. If everything goes well you can expect some PRs.

Feel free. If you do, we'll release it under a new major version. I'll give you publish and push rights once the prs come in

React being depended on with the version "^0.14.3" seems to be the issue. This picks the latest major version, which is 15.x.x and has breaking changes from 0.14.x.

Thanks, will update

I'm getting some funky issues (using npm 3.8):

complained I'm using the wrong version of babel-plugin-react-transform, which is meant for Babel 5. Checked the issues for the project and I'm indeed using the right version (even tried fixing to 2.0.2). I did a direct install using the current branch hash, but get another odd error
tried fixing all versions used in the main package.json
tried using ~ before all versions as well

Kind of stumped and out of time, did fixing the versions work for you?

It works if React is installed already. I started trying to upgrade React and the libraries that give deprecation warnings, but the task seems too big for me right now.

np, I'll have time again to look at it this weekend, sorry about that


Fizz Buzz

Directions
Write a program that console logs the nubers from 1 to n. But for multiples of three print "fizz" instead of the number and for the multiples of five print "buzz". For numbers which are multiples of both three and five print "fizzbuzz" .Make use of functions and methods where necessory
You can code this with any language of you choice!
Examples
fizzBuzz(5);
1
2
fizz
4
buzz

Please i can't seem to assign myself to this issue

Done Blanco

please can I also be assign

please assign me


Topic/222 make table responsiveness optional

BREAKING CHANGE: Table responsive behavior is now optional.

Make table responsiveness optional.
Update and simplify demo.

Please review @gregdeane @cjhowald @dami-gg

I pushed a commit to solve a minor issue here:
If the column name is big, then in responsive mode the label overlaps the contents, see screenshot below (second card, second row):
Before Fix:

After Fix:

(Added overflow hidden and text-overflow as ellipsis)

Thanks @sambhav-gore

👍

👍


Can't boot with opencore

Describe the bug
upgrade from installed system. HaCMini.pkg file successfully installed. But can’t boot, output is A bootable device has not been detected .Copy files to a usb disk, same situation.
Expected behavior
A clear and concise description of what you expected to happen.
Environment:

Running OSX version: 10.14.6
Target drive OSX version:
HaC Mini installer version: 2.0

Additional context
Add any other context about the problem here.
Logs
Please attach /var/log/install.log

secure boot is off.

I just noticed that I can boot from OC when I pull out the windows disk.
Windows Disk only, Windows boots.
Mac Disk only, MacOS boots via OpenCore. (No issues by the way.)
Both disks, Windows boots.
If I select the MacOS partition in the BIOS, Windows boots anyway.
Only way to get into MacOs with both disks installed is booting from Clover USB.
Is that OC, not showing the boot menu and defaulting to windows?
Should the OC picker come up or is it configured to default to a specific boot entry?

Follow the instructions at the end of https://osy.gitbook.io/hac-mini-guide/installation-guide/installation titled "Installing other OS"

Follow the instructions at the end of https://osy.gitbook.io/hac-mini-guide/installation-guide/installation titled "Installing other OS"

Yeah I tried that. (Crossposted in 2.0 Beta-Test thread).

Powershell as admin.

@slimx is the original issue resolved? If not, please try the new workarounds in https://osy.gitbook.io/hac-mini-guide/post-installation/support

Closing due to inactivity. You can request this to be reopened if the issue still persists with v2.2 installer.


KubernetesManifest@0: Add support for TrafficSplit annotations

Required Information
Type: Feature
Enter Task Name: KuberentesManifest@0
Environment

Server - Azure Pipelines
Agent - Hosted and Private

Issue Description
When the canary deployment strategy is chosen along with SMI traffic handling, KubernetesManifest@0 generates a TrafficSplit and the manifest for that is pretty hard-coded with only weights and service names.
At least with Istio, this will only work for services accessed from within the cluster. To get this working with ingress traffic, the Istio VirtualService needs to have a gateway attached.
The Istio SMI adapter has support for setting this through annotations but there's no way to add annotations to the generated TrafficSplit.
It would be cool to be able to add annotations to the TrafficSplit to support cases like this. It could be a key/value list parameter to the task and just copied into the TrafficSplit when it's generated. If none are present, you get the same thing you get now.

It appears the GitHub Actions counterpart is interested in a PR for this. It's a little harder, I think, to work in here, but it's still a feature we'd be interested in. Would a PR be accepted for it?


feat(accessibility): ✨ add aria-label to input field

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

Project coverage is 0.00%. Comparing base (8daf69a) to head (68faee8).
Report is 27 commits behind head on main.

:exclamation: Current head 68faee8 differs from pull request most recent head 11b3501. Consider uploading reports for the commit 11b3501 to get more accurate results

Files
Patch %
Lines

src/main.rs
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main     #56   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          1       1
  Lines          8      16    +8
=====================================
- Misses         8      16    +8

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


RancherD Doc Changes

Summary:

Reviewed RancherD docs on staging branch and have a few important edits that should be made
Details:

Many of these are suggestions and open for discussion, but 2 and 4 are required.

https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/#node-requirements

If we link node requirements, we should probably specifically mention Docker is NOT necessary to have on the Linux Host. It currently looks like it is required when we link that page.

https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/#1-set-up-the-config-yaml in "If you do not specify a pre-shared secret, RancherD will generate one and place it at /var/lib/rancher/rancherd/server/node-token."

this should be  /var/lib/rancher/rke2/server/node-token

https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/#2-launch-the-first-server-node

In step 1 here, should we specify available environment variables? The relevant one to me is: INSTALL_RANCHERD_VERSION
So an example curl command would be like: curl -sfL https://get.rancher.io | INSTALL_RANCHERD_VERSION=v2.5.4-rc6 sh -

https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/rancherd-configuration/#customizing-the-rancherd-helm-chart In "Put this manifest on your host in /var/lib/rancher/rancherd/server/manifests before running RancherD."

should be /var/lib/rancher/rke2/server/manifests

https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/#4-verify-that-rancher-is-installed-on-the-kubernetes-cluster
Should we mention that there will be many things installed? If watching pods, you'll see:

helm-operation pods in cattle-system namespace
a rancher pod and rancher-webhook pod in cattle-system namespace
a fleet-agent, fleet-controller, and gitjob pod in fleet-system namespace
a rancher-operator pod in rancher-operator-system namespace

https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/#fixed-registration-address

We should mention that the Rancher UI is served on port 8443 by default, as opposed to 443 which is what happens in standard rancher installs, so LBs or whatever is used should be setup appropriately. For example, in my testing, I setup a single LB in AWS and 4 Target Groups using TCP to 6443, 9345, 8080, and 8443. In the LB I forwarded like: 6443 -> 6443, 9345 -> 9345, 80 -> 8080, 443 -> 8443. NOTE that we do mention these ports in https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/rancherd-configuration/#customizing-the-rancherd-helm-chart
but I think it would be helpful in this section as well for clarity.
This can be as simple as adding it to https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/#fixed-registration-address at the end with the other ports.

Would it be useful to mention that installing this way is using rancher generated certs, and if they want to use a different cert method, follow the configuration guide here? https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/rancherd-configuration/#certificates-for-the-rancher-server

I'd imagine this should be mentioned in https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/#1-set-up-the-config-yaml
We can link to the certificates.
Maybe this section can be called "Setup configurations" and link to certificates, have this information about config.yaml, and also link to the values.yaml configurations at https://staging.rancher.com/docs/rancher/v2.x/en/installation/install-rancher-on-linux/rancherd-configuration/#customizing-the-rancherd-helm-chart

Also, can we mention at the beginning of Part I that "this is using rancher generated certs, and if you want to bring your own self-signed or valid certs, to follow instructions in configuration reference on each node before running steps" -- I'm not sure what the best wording would be, but something that alerts the user of the certs used by default and what they would need to do BEFORE running install if they wanted to use a different option. cc @jiaqiluo

closing because https://github.com/rancher/docs/pull/2947 was merged


[e2e]: nodejs tag main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.262
Run: https://github.com/slsa-framework/example-package/actions/runs/8354503684
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.262
Date: Wed Mar 20 06:08:45 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.263
Run: https://github.com/slsa-framework/example-package/actions/runs/8365067980
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.263
Date: Wed Mar 20 20:17:17 UTC 2024
Tests are passing now. Closing this issue.


JDynmapGriefprevention russian translation

Hey Dmitry, didn't find any other way to contect you.
Can I use your russian translation of Messages_ru.properties for JDynmapGriefprevention to add it to my Spigot page of the plugin for others to download (https://www.spigotmc.org/resources/jdynmapgriefprevention.818/)?
Best regards, jahan.

Hi Jahan,
Sure. Please have a look at 0437d146da021e3af47809dc3e8571051428e7ac and 8704ccf2bdcd61e8b5ea307c201b899f371cf817
Let me know if you need anything else)
Thanks!


fix: add report tests [ZEN-537]

[x] Ready for review
[x] Linked to Jira ticket - ZEN-537

What does this PR do?
Adds missing report tests from #170

Do we by any chance document the test org setup procedure somewhere in case we need to recreate it? I assume you had to enable the FF for it to work?

@strassl-snyk I'm not certain if we have it documented, but I didn't turn on the FF because I mocked the return values of the tests that were sending the 400 as the results weren't needed from deeproxy in that case. Also, I'm not sure if it makes sense to have tests in code-client that depend on FFs, I think that should be something done in deeproxy/registry, what do you think?
About the account used in the tests, I'm fairly certain that it is in 1Password, at the least the SNYK_API_KEY used in the CircleCI env variable matches it for app.dev.snyk.io (just double checked it)

Fair enough, I think we are fine with mocked return values for now. No need to add a tailored e2e test setup in every single service and we should have tests that ensure API stability in code-orchestrator.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add Transaction, Unwind, Authentication support & CollectAs update

I've been using the pre-release version now for a while and aside from the CollectAs change, it's worked as expected.
In terms of this merge, it's a big merge, not helped by the initial switch over to MyGet and my updates required to get it to compile there.
Project structure wise, the Test project has been renamed (and moved to coincide) to Neo4jClient.Tests - this allows MyGet to automagically run the Unit Tests without needing to maintain a script file - but (as a consequence) any pull request based on the previous structure - will be slightly more complex to merge, but I am (as they say) on the case.
Ideally I'd quite like to squash some of the merges down, but
a) I'm not sure how to do this - mainly as I'm a 'keep history' type person  and
b) I'm also willing to accept a bit of a messy source control to get this in.
I'd like thoughts on the SourceControl side of things - generally I would remove the middle checkins where I was getting MyGet to work.
Obviously big props to @arturosevilla for the initial work I think this will be enough of a step to reset the release counter to 1.1.0

@cskardon props to yourself as well!
Messy checkins don't really matter IMHO. If a regression bug is found later, would squashing the commits make it harder to pinpoint when performing a bisect?
And squashing is just making more work for you?

https://www.nuget.org/packages/Neo4jClient/<IP_ADDRESS>
For better or worse - it is done, go live the dream :)

cool!


Newsletter 13: A little section about rspirv-reflect

As mentioned in #232, I wrote a small section on rspirv-reflect.

Thanks for the feedback @17cupsofcoffee, does conform to the guidelines better?

@Jasper-Bekkers As I don't have write permission to this PR, I made a meta PR with required style tweaks: https://github.com/Traverse-Research/rust-gamedev.github.io/pull/1
Could you also resolve the merge conflicts, please?

Merged manually (https://github.com/rust-gamedev/rust-gamedev.github.io/commit/a68fb5f7ff655eb5b97911cc688c827001af9740) as I don't have write permission to the PR's branch.


Use bold blue color for path decoration

File paths in result is too obscure with some colorschemes in iTerm2.  It is because the color “Bold Green”(color code 010) has a special use for those colorschemes.
This PR use “Bold Blue”(color code 012) for that. Here are samples, above is master, below is my forked version.

color
palette
sample

iTerm2 (default)

Solarized

base16-default

Duotones Dark

I think it is better that the colors in decorator.go can be specified by .ptconfig.toml. But this patch is tentatively enough to this use.

Nice examples, thanks @delphinus35.

I think it is better that the colors in decorator.go can be specified by .ptconfig.toml.

I think so.
I will implement --color-line-number, --color-match and --color-path options and release new version in next week.
Please wait :+1:

related issue: https://github.com/monochromegane/the_platinum_searcher/issues/117

Hi @delphinus35 .
I have released v2.1.0 now that contains color-line-number, color-path and color-match options.
You can specify the options like the following:
$ pt --color-path="1;34" PATTERN

and you can add the same option in .ptconfig.toml :smile:
see also: https://github.com/monochromegane/the_platinum_searcher/pull/130
Thanks.

Awesome! I confirmed --color-** options and desirable results. :+1:


desmachymatous, exospherical

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 5
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[d,e]

/trunk merge


Paragraphs and inline image

I've installed this plugin and like it a lot. However, I found out that the Markdown parser is always adding a paragraph for each line.
Problem 1
Lorem Ipsum dolor …

![foobar](foo/bar.jpeg)

… sit amet

will result in this HTML:

Lorem Ipsum dolor …

… sit amet

This plugin then converts it to a figure with caption. However, a figure (block element) is not allowed within a paragraph (invalid HTML).
Problem 2
Additionally, it will break the content if the image is inline.
Lorem Ipsum dolor ![foobar](foo/bar.jpeg) … sit amet

will result in

Lorem Ipsum dolor  sit amet

Converting the inline image in this case is wrong, because it would become a block element due to
 (apart from problem 1).
Solution
I have changed the plugin to only handle image tags that are inside empty paragraphs, and then also remove the paragraph. I hope my assumption about the markdown parser is correct, but as the plugin is for Gitbook I guess we can assume always the same parser…

Hi Andreas,
Thank you very much for your changes! They are now merged and the plugin released as 0.2.0.
Best regards,
Tomas

Thanks! :+1:


nimble: Add pre-enable and post-stop callbacks

@dhrishi do you think it might help somehow in the context of #467 ?

Hi @rymanluk Sorry for missing this. Can you please let me know how these callbacks will help wrt stop/deinit ports? That PR cleans up the host and port specific things in a generic way.

@sjanc @andrzej-kaczmarek I think we could still have it


Small issue

https://github.com/Mintplex-Labs/anything-llm/blob/f499f1ba59f2e9f8be5e44c89a951e859382e005/frontend/src/pages/GeneralSettings/LLMPreference/index.jsx#L11
needs to be lowercased

resolved by 195d3cfcc33fc5c03cc2c8451e302c38383558d7