dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
localuser:dau being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: WARNING: standard input reopened
gpgconf: WARNING: standard input reopened
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=dau
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dau
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting LOGNAME=dau
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/var/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dau
/home/dau/.xsession: Zeile 1: gnome-panel: Kommando nicht gefunden.
Xsession: X session started for dau at Do 28. Jul 22:05:16 CEST 2022
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
localuser:dau being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: WARNING: standard input reopened
gpgconf: WARNING: standard input reopened
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=dau
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dau
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting LOGNAME=dau
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/var/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dau
/home/dau/.xsession: Zeile 1: gnome-panel: Kommando nicht gefunden.
Xsession: X session started for dau at Do 28. Jul 22:13:52 CEST 2022
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting DISPLAY=:10.0
localuser:dau being added to access control list
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: WARNING: standard input reopened
gpgconf: WARNING: standard input reopened
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting USER=dau
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dau
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-qP4wqeLqWJ,guid=831fc6273b07fdf1a312959762e2ee00
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting LOGNAME=dau
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/var/run/xrdp/sockdir
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dau
/home/dau/.xsession: Zeile 1: gnome-panel: Kommando nicht gefunden.

** (process:4521): WARNING **: 22:13:52.738: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=GNOME environment variable: Could not connect: Connection refused
Xsession: X session started for dau at Do 28. Jul 22:26:07 CEST 2022
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
localuser:dau being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: WARNING: standard input reopened
gpgconf: WARNING: standard input reopened
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=dau
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dau
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting LOGNAME=dau
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/var/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dau
/home/dau/.xsession: Zeile 1: gnome-panel: Kommando nicht gefunden.
Xsession: X session started for dau at Do 28. Jul 22:28:44 CEST 2022
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
localuser:dau being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: WARNING: standard input reopened
gpgconf: WARNING: standard input reopened
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=dau
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dau
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting LOGNAME=dau
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/var/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dau
/home/dau/.xsession: Zeile 1: gnome-panel: Kommando nicht gefunden.
Xsession: X session started for dau at Do 28. Jul 22:32:40 CEST 2022
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
localuser:dau being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: WARNING: standard input reopened
gpgconf: WARNING: standard input reopened
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=dau
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dau
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting LOGNAME=dau
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/var/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dau
/home/dau/.xsession: Zeile 1: gnome-panel: Kommando nicht gefunden.
Xsession: X session started for dau at Do 28. Jul 22:35:42 CEST 2022
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
localuser:dau being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: WARNING: standard input reopened
gpgconf: WARNING: standard input reopened
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=dau
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dau
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting LOGNAME=dau
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/var/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dau
/home/dau/.xsession: Zeile 1: gnome-panel: Kommando nicht gefunden.
Xsession: X session started for dau at Do 28. Jul 22:48:36 CEST 2022
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
localuser:dau being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: WARNING: standard input reopened
gpgconf: WARNING: standard input reopened
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=dau
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dau
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting LOGNAME=dau
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/var/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dau
/home/dau/.xsession: 1: /home/dau/.xsession: gnome-panel: not found
Xsession: X session started for dau at Do 28. Jul 22:51:12 CEST 2022
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
localuser:dau being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: WARNING: standard input reopened
gpgconf: WARNING: standard input reopened
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=dau
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dau
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting LOGNAME=dau
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/var/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/dau
/home/dau/.xsession: 1: /home/dau/.xsession: gnome-panel: not found

sudo journalctl -S -6m prints (I did 6m, otherwise you would only see "Closed socket 19 (AF_UNIX)" over and over again):
-- Logs begin at Thu 2022-07-28 20:29:31 CEST, end at Fri 2022-07-29 12:18:50 CEST. --
Jul 29 12:13:00 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] xrdp_wm_log_msg: connecting to sesman ip <IP_ADDRESS> port 3350
Jul 29 12:13:00 p-nwc01 xrdp-sesman[8407]: (8407)(140549696341504)[INFO ] A connection received from ::1 port 43860
Jul 29 12:13:00 p-nwc01 xrdp[19839]: (19839)(139723563611968)[INFO ] xrdp_wm_log_msg: sesman connect ok
Jul 29 12:13:00 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
Jul 29 12:13:00 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] return value from xrdp_mm_connect 0
Jul 29 12:13:00 p-nwc01 xrdp-sesman[8407]: (8407)(140549696341504)[INFO ] ++ created session (access granted): username dau, ip ::ffff:<IP_ADDRESS>:65438 - socket: 12
Jul 29 12:13:00 p-nwc01 xrdp-sesman[8407]: (8407)(140549696341504)[INFO ] starting Xorg session...
Jul 29 12:13:00 p-nwc01 xrdp-sesman[8407]: (8407)(140549696341504)[DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
Jul 29 12:13:00 p-nwc01 xrdp-sesman[8407]: (8407)(140549696341504)[DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
Jul 29 12:13:00 p-nwc01 xrdp-sesman[8407]: (8407)(140549696341504)[DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
Jul 29 12:13:00 p-nwc01 xrdp[19839]: (19839)(139723563611968)[INFO ] xrdp_wm_log_msg: login successful for display 10
Jul 29 12:13:00 p-nwc01 xrdp-sesman[8407]: (8407)(140549696341504)[DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
Jul 29 12:13:00 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[INFO ] calling auth_start_session from pid 21727
Jul 29 12:13:00 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] xrdp_wm_log_msg: started connecting
Jul 29 12:13:00 p-nwc01 xrdp-sesman[21727]: pam_unix(xrdp-sesman:session): session opened for user dau by (uid=0)
Jul 29 12:13:00 p-nwc01 systemd-logind[704]: New session c18 of user dau.
Jul 29 12:13:00 p-nwc01 systemd[1]: Started Session c18 of user dau.
Jul 29 12:13:00 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
Jul 29 12:13:00 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
Jul 29 12:13:00 p-nwc01 xrdp-sesman[21729]: (21729)(140549696341504)[INFO ] /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
Jul 29 12:13:01 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[CORE ] waiting for window manager (pid 21728) to exit
Jul 29 12:13:01 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[CORE ] window manager (pid 21728) did exit, cleaning up session
Jul 29 12:13:01 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[INFO ] calling auth_stop_session and auth_end from pid 21727
Jul 29 12:13:01 p-nwc01 xrdp-sesman[21727]: pam_unix(xrdp-sesman:session): session closed for user dau
Jul 29 12:13:01 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[DEBUG] cleanup_sockets:
Jul 29 12:13:01 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[DEBUG] cleanup_sockets: deleting /var/run/xrdp/sockdir/xrdp_chansrv_socket_10
Jul 29 12:13:01 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[DEBUG] cleanup_sockets: deleting /var/run/xrdp/sockdir/xrdpapi_10
Jul 29 12:13:01 p-nwc01 xrdp-sesman[21727]: (21727)(140549696341504)[DEBUG] cleanup_sockets: failed to delete /var/run/xrdp/sockdir/xrdpapi_10
Jul 29 12:13:01 p-nwc01 xrdp-sesman[8407]: (8407)(140549696341504)[INFO ] ++ terminated session:  username dau, display :10.0, session_pid 21727, ip ::ffff:<IP_ADDRESS>:65438 - socket: 12
Jul 29 12:13:01 p-nwc01 systemd-logind[704]: Session c18 logged out. Waiting for processes to exit.
Jul 29 12:13:01 p-nwc01 gnome-session[21775]: Unable to init server: Could not connect: Connection refused
Jul 29 12:13:01 p-nwc01 gnome-session-f[21783]: Cannot open display:
Jul 29 12:13:04 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:07 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:11 p-nwc01 systemd[1]: session-c18.scope: Succeeded.
Jul 29 12:13:11 p-nwc01 systemd-logind[704]: Removed session c18.
Jul 29 12:13:11 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:14 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:18 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:21 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:25 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:28 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:32 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:35 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:39 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:42 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:46 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:49 p-nwc01 sudo[21784]:      dau : TTY=pts/0 ; PWD=/home/dau ; USER=root ; COMMAND=/usr/bin/journalctl -S -3m
Jul 29 12:13:49 p-nwc01 sudo[21784]: pam_unix(sudo:session): session opened for user root by dau(uid=0)
Jul 29 12:13:49 p-nwc01 sudo[21784]: pam_unix(sudo:session): session closed for user root
Jul 29 12:13:49 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:53 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:13:56 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:00 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:03 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:07 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:09 p-nwc01 sudo[21795]:      dau : TTY=pts/0 ; PWD=/home/dau ; USER=root ; COMMAND=/usr/bin/journalctl -S -3m
Jul 29 12:14:09 p-nwc01 sudo[21795]: pam_unix(sudo:session): session opened for user root by dau(uid=0)
Jul 29 12:14:10 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:14 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:17 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:21 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:24 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:28 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:31 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:35 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:38 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:42 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:45 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:49 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:52 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:56 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:14:59 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:03 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:07 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:10 p-nwc01 sudo[21795]: pam_unix(sudo:session): session closed for user root
Jul 29 12:15:10 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:14 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:17 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:21 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:21 p-nwc01 sudo[21810]:      dau : TTY=pts/0 ; PWD=/home/dau ; USER=root ; COMMAND=/usr/bin/journalctl -S -3m
Jul 29 12:15:21 p-nwc01 sudo[21810]: pam_unix(sudo:session): session opened for user root by dau(uid=0)
Jul 29 12:15:24 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:28 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:31 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:35 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:38 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:42 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:45 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:49 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:52 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:56 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:15:59 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:03 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:06 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:10 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:13 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:17 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:20 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:24 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:27 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:30 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] xrdp_wm_log_msg: connection problem, giving up
Jul 29 12:16:30 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 19 (AF_UNIX)
Jul 29 12:16:30 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] xrdp_wm_log_msg: some problem
Jul 29 12:16:30 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] xrdp_mm_module_cleanup
Jul 29 12:16:30 p-nwc01 xrdp[19839]: (19839)(139723563611968)[DEBUG] Closed socket 18 (AF_INET6 ::1 port 43860)
Jul 29 12:17:01 p-nwc01 CRON[21829]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 29 12:17:01 p-nwc01 CRON[21830]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 29 12:17:01 p-nwc01 CRON[21829]: pam_unix(cron:session): session closed for user root
Jul 29 12:17:06 p-nwc01 sudo[21810]: pam_unix(sudo:session): session closed for user root
Jul 29 12:17:07 p-nwc01 sudo[21832]:      dau : TTY=pts/0 ; PWD=/home/dau ; USER=root ; COMMAND=/usr/bin/journalctl -S -3m
Jul 29 12:17:07 p-nwc01 sudo[21832]: pam_unix(sudo:session): session opened for user root by dau(uid=0)
Jul 29 12:17:07 p-nwc01 sudo[21832]: pam_unix(sudo:session): session closed for user root
Jul 29 12:17:26 p-nwc01 dbus-daemon[19898]: [session uid=1000 pid=19898] Activating service name='org.freedesktop.thumbnails.Cache1' requested by ':1.50' (uid=1000 pid=20297 comm="/usr/lib/tracker/tracker-miner-fs ")
Jul 29 12:17:26 p-nwc01 org.freedesktop.thumbnails.Cache1[19898]: Registered thumbailer gnome-thumbnail-font --size %s %u %o
Jul 29 12:17:26 p-nwc01 org.freedesktop.thumbnails.Cache1[19898]: Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Jul 29 12:17:26 p-nwc01 org.freedesktop.thumbnails.Cache1[19898]: Registered thumbailer atril-thumbnailer -s %s %u %o
Jul 29 12:17:26 p-nwc01 org.freedesktop.thumbnails.Cache1[19898]: Registered thumbailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Jul 29 12:17:26 p-nwc01 org.freedesktop.thumbnails.Cache1[19898]: Registered thumbailer /usr/bin/totem-video-thumbnailer -s %s %u %o
Jul 29 12:17:26 p-nwc01 org.freedesktop.thumbnails.Cache1[19898]: Registered thumbailer evince-thumbnailer -s %s %u %o
Jul 29 12:17:26 p-nwc01 org.freedesktop.thumbnails.Cache1[19898]: Registered thumbailer gsf-office-thumbnailer -i %i -o %o -s %s
Jul 29 12:17:26 p-nwc01 dbus-daemon[19898]: [session uid=1000 pid=19898] Successfully activated service 'org.freedesktop.thumbnails.Cache1'
Jul 29 12:17:29 p-nwc01 sudo[21852]:      dau : TTY=pts/0 ; PWD=/home/dau ; USER=root ; COMMAND=/usr/bin/journalctl -S -3m
Jul 29 12:17:29 p-nwc01 sudo[21852]: pam_unix(sudo:session): session opened for user root by dau(uid=0)
Jul 29 12:17:29 p-nwc01 sudo[21852]: pam_unix(sudo:session): session closed for user root
Jul 29 12:17:29 p-nwc01 dbus-daemon[19898]: [session uid=1000 pid=19898] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.50' (uid=1000 pid=20297 comm="/usr/lib/tracker/tracker-miner-fs ")
Jul 29 12:17:29 p-nwc01 systemd[18168]: Starting Tracker metadata extractor...
Jul 29 12:17:29 p-nwc01 dbus-daemon[19898]: [session uid=1000 pid=19898] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Jul 29 12:17:29 p-nwc01 systemd[18168]: Started Tracker metadata extractor.
Jul 29 12:17:40 p-nwc01 systemd[18168]: tracker-extract.service: Succeeded.
Jul 29 12:18:07 p-nwc01 gsd-color[20199]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output
Jul 29 12:18:50 p-nwc01 dbus-daemon[19898]: [session uid=1000 pid=19898] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.50' (uid=1000 pid=20297 comm="/usr/lib/tracker/tracker-miner-fs ")
Jul 29 12:18:50 p-nwc01 systemd[18168]: Starting Tracker metadata extractor...
Jul 29 12:18:50 p-nwc01 sudo[21893]:      dau : TTY=pts/0 ; PWD=/home/dau ; USER=root ; COMMAND=/usr/bin/journalctl -S -6m
Jul 29 12:18:50 p-nwc01 sudo[21893]: pam_unix(sudo:session): session opened for user root by dau(uid=0)

In the "journalctl" log I saw earlier that the firewall was blocking Port 3478 when xrdp tried connecting. What is that port needed for? I thought rdp only needed 3389? Anyways, I disabeled the firewall alltogether, and the same error still comes up.
Again, thanks for you help!
bitcubik

This seems relevant:-
/home/dau/.xsession: 1: /home/dau/.xsession: gnome-panel: not found

Check you've got GNOME installed correctly. https://wiki.debian.org/Gnome suggests apt-get install task-gnome-desktop.
Also, remove ~/.xsession entirely.

PS : I've no idea what needs port 3478. I don't think that's anything to do with xrdp.

Gnome is correctly installed and on the newest version.
Removing ~/.xsession did indeed do the trick. As soon as I removed the file and restarted the xrdp service, the session closed immidiatly upon login. I think that was caused by the user being logged in in a non-remote session, as soon as I logged out and tried again, the remote session finally opened correctly.
After that, I readded the "unset DBUS_SESSION_BUS_ADDRESS, unset XDG_RUNTIME_DIR, . $HOME/.profile" lines to startwm.sh, which also seemed to solve the problem with the remote session not working if the user was logged in non-remotely.
Reenableing the firewall and therefore blocking 3478 again did, just as you said, change nothing and it still worked.
Thank you very much for your help!
bitcubik


dialect/sql/schema: add MigrateOption 'WithForeighKeysDisable' (#748)

Hi there, i add a new migrate option to control whether or not create foreigh key in ddl.
Hope this can be helpful.

Hey @day-dreams, any updates regarding this PR?

sorry to update late. @a8m please review latest commit.

@a8m would you please merge this pr ?

@a8m would you please merge this pr ?

Hey @day-dreams, I'm currently on a vacation until Tuesday. I'll continue the review and merge it when I come back.
Thanks for your contribution.

I would like to see this pull can be merged soon...

Thanks for your contribution and sorry for the delay @day-dreams
PR merged manually (I needed to solve some Git conflicts)

A pretty cool PR AWESOME !

A pretty cool PR AWESOME !


Add WS subscription command for MQTT

Description:
Create an MQTT endpoint to allow the frontend to subscribe to MQTT topics and get it forwarded to the frontend over the websocket API.
This will power an MQTT dev panel upgrade.
To be done:

[x] tests
[x] When we shut down Home Assistant, by the time the websocket API is handling unsubscribes of any active subscriptions, the MQTT server is already disconnected, raising the following exception:

2019-03-05 15:09:40 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/Users/paulus/dev/hass/home-assistant/homeassistant/components/mqtt/__init__.py", line 730, in _async_unsubscribe
    _raise_on_error(result)
  File "/Users/paulus/dev/hass/home-assistant/homeassistant/components/mqtt/__init__.py", line 825, in _raise_on_error
    'Error talking to MQTT: {}'.format(mqtt.error_string(result_code)))
homeassistant.exceptions.HomeAssistantError: Error talking to MQTT: The client is not currently connected.

Frontend will require a new HAWS version which includes https://github.com/home-assistant/home-assistant-js-websocket/pull/85
CC @emontnemery
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

I think it looks good. It would be useful to also be able to see all exchanged MQTT messages, not just those manually subscribed to in frontend.


Dinfra application, updated payment destination.

This PR simply updates DINFRA payment to FIAT.
Unfortunately Swedish banking sector is not very crypto friendly.

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

@dsm-w3f is this PR what you need ?


GEODE-6533: Update LICENSE and NOTICE files for changed dependencies

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

MIT
animal-sniffer-annotations-1.17.jar - MIT - https://mvnrepository.com/artifact/org.codehaus.mojo/animal-sniffer-annotations
checker-qual-2.5.2.jar - MIT - https://mvnrepository.com/artifact/org.checkerframework/checker-qual
Apache 2.0
error_prone_annotations-2.2.0.jar - Apache 2.0 - https://mvnrepository.com/artifact/com.google.errorprone/error_prone_annotations
failureaccess-1.0.jar - Apache 2.0 - https://mvnrepository.com/artifact/com.google.guava/failureaccess
j2objc-annotations-1.1.jar - Apache 2.0 - https://mvnrepository.com/artifact/com.google.j2objc/j2objc-annotations
jsr305-3.0.2.jar - Apache 2.0 - https://mvnrepository.com/artifact/com.google.code.findbugs/jsr305
listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar - Apache 2.0 - https://mvnrepository.com/artifact/com.google.guava/listenablefuture/9999.0-empty-to-avoid-conflict-with-guava
commons-math3-3.2.jar - Apache 2.0 - https://mvnrepository.com/artifact/org.apache.commons/commons-math3
geo-0.7.1.jar - Apache 2.0 - https://mvnrepository.com/artifact/com.github.davidmoten/geo
grumpy-core-0.2.2.jar - Apache 2.0 - https://mvnrepository.com/artifact/com.github.davidmoten/grumpy-core
CDDL
istack-commons-runtime-2.2.jar - CDDL 1.1 -  https://projects.eclipse.org/projects/ee4j.jaxb
javax.activation-1.2.0.jar - CDDL 1.1 - https://mvnrepository.com/artifact/javax.activation, https://eclipse-ee4j.github.io/jaf/
javax.activation-api-1.2.0.jar - CDD 1.1 - https://mvnrepository.com/artifact/javax.activation, https://eclipse-ee4j.github.io/jaf/

@dickcav Thanks for catching the LICENSE file update. Looks like we need to update top-level file if we include any dependency into src distribution otherwise we update geode-assembly/src/main/dist/LICENSE file.
I have corrected the LICENSE changes and moved those into assembly LICENSE file.
Also, I have reverted NOTICE file changes as I still have more work to do, so will create a new PR.

@metatype This PR has been updated with only LICENSE changes and changes to NOTICES will follow.

@sboorlagadda here's my take on the changes to LICENSE:
diff --git a/LICENSE b/LICENSE
index a243c40007..0dc431d441 100644
--- a/LICENSE
+++ b/LICENSE
@@ -257,8 +257,6 @@ The MIT License (http://opensource.org/licenses/mit-license.html)

 Apache Geode bundles the following files under the MIT license:

-  - ClassGraph v4.0.6 (https://github.com/classgraph/classgraph), Copyright (c)
-    2015 Luke Hutchison
   - HTML5 Shiv vpre3.5 (https://github.com/aFarkas/html5shiv), Copyright
     (c) 2014 Alexander Farkas (aFarkas)
   - JavaScript InfoVis Toolkit v2.0.1 (http://philogb.github.io/jit/),
diff --git a/geode-assembly/src/main/dist/LICENSE b/geode-assembly/src/main/dist/LICENSE
index 94a70e636f..fa7db6036e 100644
--- a/geode-assembly/src/main/dist/LICENSE
+++ b/geode-assembly/src/main/dist/LICENSE
@@ -221,6 +221,10 @@ Apache Geode bundles the following files under the BSD 3-Clause License:
     Copyright (c) 2002-2007 Marc Prud'hommeaux.
   - Antlr v2.7.7 (http://www.antlr.org), Copyright (c) 2012 Terrence Parr
     and Sam Harwell
+  - Checker Qual 2.5.2 (https://checkerframework.org), Copyright (c)
+    2004-present by the Checker Framework developers
+  - ClassGraph v4.0.6 (https://github.com/classgraph/classgraph), Copyright (c)
+    2015 Luke Hutchison
   - JLine v2.12 (http://jline.sourceforge.net), Copyright (c) 2002-2006,
     Marc Prud'hommeaux<EMAIL_ADDRESS>   - jQuery Sparklines v2.0 (http://omnipotent.net/jquery.sparkline/),
@@ -270,13 +274,15 @@ The CDDL (https://glassfish.java.net/public/CDDLv1.0.html)
 Apache Geode bundles the following file under the Common Development and
 Distribution License:

-  - javax.activation v1.1.1
     (http://java.sun.com/javase/technologies/desktop/javabeans/jaf/index.jsp),
-  - javax.mail v1.4.7 (http://www.oracle.com/)
-  - javax.resource v 1.7 (https://glassfish.java.net/)
+  - jaxb-istack-commons v2.2 (https://javaee.github.io/jaxb-istack-commons/)
+  - javax.activation v1.2.0
+    (https://www.oracle.com/technetwork/java/javase/jaf-135115.html)
+  - javax.mail v1.6.2 (http://www.oracle.com/)
+  - javax.resource v 1.7.1 (https://glassfish.java.net/)
   - javax.servlet v3.1.0 (https://glassfish.java.net/)
-  - javax.transaction v1.2 (https://glassfish.java.net/)
-  - javax.xml.bind v2.2.11
+  - javax.transaction v1.3 (https://glassfish.java.net/)
+  - jaxb v2.3.1 (https://javaee.github.io/jaxb-v2/)

 1. Definitions.
   1.1. Contributor means each individual or entity that creates or
@@ -602,6 +608,9 @@ The MIT License (http://opensource.org/licenses/mit-license.html)

 Apache Geode bundles the following files under the MIT license:

+  - Animal Sniffer Annotations v1.17
+    (https://www.mojohaus.org/animal-sniffer/source-repository.html)
+    Copyright (c) 2009 codehaus.org
   - JavaScript InfoVis Toolkit v2.0.1 (http://philogb.github.io/jit/),
     Copyright (c) 2011 Sencha Inc.
   - JOpt Simple (http://pholser.github.io/jopt-simple/), Copyright (c)

@metatype Thanks for the feedback.
I see that jaxb-istack-commons has CDDL 1.1 (https://javaee.github.io/jaxb-istack-commons/LICENSE). So do we need to include it as 1.1 rather than 1.0?

I also reviewed the jars for NOTICE(s) and pushed changes.

@metatype Thanks for the feedback.
I see that jaxb-istack-commons has CDDL 1.1 (https://javaee.github.io/jaxb-istack-commons/LICENSE). So do we need to include it as 1.1 rather than 1.0?

yea makes sense

@metatype Thanks. I have updated CDDL to 1.1
Also Checker Framework seems to be GPL but I see that you considered it as BSD. Also GPL is category x and not allowed.
https://github.com/typetools/checker-framework/blob/master/LICENSE.txt

@metatype Thanks. I have updated CDDL to 1.1
Also Checker Framework seems to be GPL but I see that you considered it as BSD. Also GPL is category x and not allowed.
https://github.com/typetools/checker-framework/blob/master/LICENSE.txt

Whoops, I meant to add checker-qual under the MIT section.  If you look at their license statement [1], the qual/* and related files are under the more permissive MIT license.  You can also follow the discussion of this in the guava community [2].
[1] https://github.com/typetools/checker-framework/blob/master/LICENSE.txt
[2] https://groups.google.com/forum/#!topic/guava-discuss/wUmhhOP2Kpo

@metatype I did fix the license for checker-qual. Do you want to take a final look at the changes and give a 👍 ?

LGTM


Have to tag every song of my playlist even if I have already tagged it manually

Expected Behavior
When playing again the same video, should recognize it and scrobble it again.
Current Behavior
I'm playing a huge playlist of korean song (so the automatic recognition is a mess). I tagged them every time a new one was played but realized even the ones I've already tagged are not recognized after.
Possible Solution

Save previously scrobbled songs based on song ID.
Being able to favourite songs / playlists and save them based on ID to automatically scrobble them.

Steps to Reproduce (for bugs)

Listen to this playlist : https://www.youtube.com/watch?v=LR0pKtiaBJ0&index=5&list=PL7-lpefz7vzkCDL3-xRH5emCIg5XDJLQM
Play a song, tag it manually.
Change to another one.
Play again the first one. It's not detected despited having been tagged.

Context
I don't want to spend my day tagging same songs again and again.
Steps for resolving the issue
Environment

Version used: 1.61.0
Browser Name and version: Chrome Version 56.0.2924.87 (64-bit)

Duplicate of #291

No, it's not a duplicate of #291, but such feature is already implemented and will be available in the next release.


Unuseable

Everytime i attempt to login in a message is displayed reading "Error: read ECONNRESET"
Or "Error: socket hangup" and i am unable to login making the app unusable for me
PLEASE HELP

I'm having the same issue


create a recommender

baseline

[ ] weighted mean of measures

future thoughts to be captured in an advanced recommender later:

[ ] Node features
[ ] Edge features by tweet engagement (if available, might need to sample) (hint: entities in tweets?)

get_liking_users
get_liked_tweets
get_retweeters

[ ] :Consideration: Tweet content paired with ideal prompts in the embedding space
[ ] :Consideration: Outliers | Downweight certain recommendations?
[ ] GNNs to merge them altogether in a link prediction exercise?


Datagrid Single Row Action no longer works when ResizeSensor is used by other elements

Describe the bug
I've been using the ResizeSensor which is a part of css-element-queries library to detect the changes in dimension of any HTML element. I don't have any problems with it prior to Clarity version 2.2.0 but when I updated my dependencies to the latest Clarity version, the data grid component's single row action, which I think is now using the new smart popover, it's not popping up.
Resize sensor is disabled:

Resize sensor is enabled and applied to the toolbar element:

How to reproduce
Sample code that uses the ResizeSensor (I created a directive for this):
<div (elementResized)="onResize($event)">
    <button class="btn">Button 1</button>
    <button class="btn">Button 1</button>
</div>

<clr-datagrid>
    ...datagrid definition here
</clr-datagrid>

Use this StackBlitz link to see the issue:  https://stackblitz.com/edit/clarity-light-theme-v2-yrfkcg

Click on the Toggle Resize Sensor button to enable/disable the resize sensor.
Click on the single action row button.

Expected behavior
The datagrid single row action should show up when clicked. If you have an alternative that I can use for detecting the size changes in an element, then I think I get rid of the ResizeSensor library.
Versions
App

Angular: [e.g. 6] 8
Node: [e.g. 8.10.0] 10 or 11
Clarity: [e.g. 0.12.5] 2.2.0

Device:

Type: [e.g. MacBook] Dell XPS 13
OS: [e.g. iOS] Windows 10
Browser [e.g. chrome, safari] Chrome, Edge Chromium, Edge, Firefox, IE11
Version [e.g. 22] Latest

Additional notes
Column filters and column hide/show toggle seem fine. I think only the single action row button is not working.

Hi There,
I did a bit of investigation on this. One thing I noticed is that I can only replicate the issue as described wen using the stackblitz code editor and preview pane in the same tab. The popover works as expected when Toggle Resize Sensor is on in the full app view: https://clarity-light-theme-v2-yrfkcg.stackblitz.io/
Is this the case for you as well?

First, what are you using this ResizeSensor for exactly? I'm not sure why you are using it but since this is a third party service it is unclear to me if this is an issue on our end or theirs.

@gnomeontherun It doesn't work in the full app view for me either. When the button is green, that means ResizeSensor is being used. I made a toggle button so I can see the difference when using and not using the ResizeSensor.
I built a custom toolbar component similar to Microsoft's Office UI Fabric CommandBar component and Blueprint's Overflow list component. The component can contain several buttons/toolbar items. If the width of the toolbar is enough to display all the buttons then it'll display all of them. But, if the width is smaller than the total width of all the buttons, those buttons that aren't visible are added to the overflow button.
The reason why I used this library is because I used it to listen to the changes in the dimension of an element. With that, I can recalculate the width of the toolbar and the total width of all its buttons. Then when I got the right calculated widths, I can now decide whether I should make the buttons visible in the toolbar or hide it in the overflow button.
To summarize, my goal is to listen to the changes in the HTML element's dimensions. I can't use the html resize event since it fires only when resizing the browser window.

Here's what it looks like in real-world app:
When the width of the page is wider:

When the width is tight:

@gnomeontherun I've done some research and came up with an alternative solution. I totally got rid of the ResizeSensor library and used Google Dev's ResizeObserver instead. Tested it, used some polyfills for other browsers, and now I've got the single action row working again! Anyway, thanks for looking into this issue and I can now close this.

Awesome. fwiw - I think ResizeObserver is part of the WebAPI and not exclusive to Chrome/google https://drafts.csswg.org/resize-observer-1/ and https://developer.mozilla.org/en-US/docs/Web/API/ResizeObserver.


OCPBUGS-37295: Sessions flapping when a service is added, backporting

Backporting the fix and the tests

/label backport-risk-assessed

/label cherry-pick-approved

/jira refresh

/retest

/lgtm


updated bugged dependency

Updated file-saver dependency from 2.0.1 to 2.0.2
there is a known bug in version 2.0.1 that leads to npm trying to install the github branch. This causes an error in many environments.
This fixes that.

the test timed out... i think this is a problem with the tests themselves...

Closing because #2804 removes the file-saver dependency.


Refactor build script

Moved the logic into a function so the module can be imported and used elsewhere.
Factored out the configurable constants to the top of the file. I also reworded the descriptions for these to use a more extractable style. We can probably remove a bunch of the comments in the code since they explain what/how and not why, but for now they're fine to leave in.
It now calculates the best number of columns to make the resulting grid a square.
Added a final pass if the user has optipng installed to reduce the amount of space the image takes up.
Ran black and pylint over it to fix up any issues and use a consistent style.
Added a shebang and gave it execute privileges so it can just be run directs.
Added missing newline from end of file to make POSIX compliant.
Fixed a file descriptor leak by using a with context block when opening the image files.
Sort the geets by name to stabilize the order.

I also added gaps and margin to the grid to improve the look but that's less refactor and more feature so it's a separate commit in this PR.

Keller hitting the AI code with a 2x4.


Missing required module 'CAudioKitEX' in Previews

macOS Version(s) Used to Build
macOS 14.4.1 Sonomna
Xcode Version(s)
Xcode 15.2
Description
The Controls demo doesn't show properly when holding an iPhone in portrait mode, see image below. The knobs are too small and the keyboard has grotesque dimensions. It looks fine in landscape and on iPad.
In order to fix it within ControlsView.swift I tried adding following code. Neither version works but that gives stranges error that I can't fix. Tried it on several recipies: ControlsView, TableRecipeView, ...
struct ControlsView_Previews: PreviewProvider {
    static var previews: some View {
        ControlsView()
    }
}

#Preview {
    ControlsView()
}

<unknown>:0: error: missing required module 'CAudioKitEX'

Steps to reproduce

Fork CookBook
Compile and deploy on iPhone
Start app, navigate to "Additional Packages > Controls"
Hold iPhone upside (portrait)
Knobs are too small, Keyboard dimensions are grotesque
Try to fix it with Xcode preview
Absurd errors in Xcode that won't go away

tl;dr
Swift Previews are not working in the Cookbook. Throws error missing required module 'CAudioKitEX' even though AudioKitEX appears to be included. Nothing is broken at the moment, but the error shows up when you add a preview:
#Preview {
    ControlsView()
}

Yeah, I'm seeing this issue too and not sure how to fix it. That may be why Swift Previews were removed at some point from the Cookbook. The Cookbook adds packages to CookbookCommon rather than to the project. I can see where AudioKitEX is added so I'm not sure why previews can't find it as it compiles. Maybe @aure will know something.

I'll close this for now, but feel free to reopen if anyone wants to take a stab at fixing it. The structure of packages in the Cookbook prevents the use of Previews.


implement claim tasks functionality

Logged in users can now help out with open tasks by clicking on the 'HELP OUT' button in a task from the homepage task list. Upon confirming to help, a fetch POST request is sent to the EditTaskServlet that checks that this is in fact a 'helpout' edit action, then checks that the user is indeed logged in and that the task hasn't been already claimed by another user. If none of these errors occur, the task's status is changed to 'IN PROGRESS' and the helper's userId is updated in the task's 'helper' property.
Resolves #22 , fixes #47

LGTM for the java code. Want to ask @peap to look at the JS since I don't have much experience with front-end code?

Thanks and will do!


Black screen when certain characters are on screen

When using the wrapper and certain characters appear the screen goes black and nothing responds until refreshing
Characters that will cause this problem:

🚀
🎵
and more because I have not been able to find a cause for all of them

It seems to work fine for me.

Can you run discord from the command line and see if it gives you any errors when it happens?

I get no command line output when running discord and the screen goes black

Do you have symbola installed?

yes I can see them fine when using discord in firefox or chrome, but not in the wrapper

Can't seem to reproduce this either. What distro are you using?

I'm on Arch

So am I

Hi. Some of the community members have been able to solve this issue before we got to it. What I believe you're missing is freetype-font. They've come to the conclusion that freetype2-infinality or freetype2-ubuntu should solve your issue.
Both should be on the AUR. Try installing one of those and see if it fixes the issue.

that did indeed fix the issue for me

just correcting. it's not a font, it's rendering library.

Is there any other way to fix this? Infinality causes eye strain for me.

Try installing the ubuntu one. It looks better imo as well, that's why I installed it initially and why I never had this problem.


Transfer event not returned in getEvents

evm: v0.2.0
node: v11.14.0
There is a Transfer event defined on this contract but not return by the getEvents method of EVM
https://etherscan.io/address/0x5d00d312e171be5342067c09bae883f9bcb2003b#code
event Transfer(address indexed _from, address indexed _to, uint256 indexed _tokenId)
Reproduce:
const code = await web3.eth.getCode('0x5d00d312e171be5342067c09bae883f9bcb2003b');
const evm = new EVM(code);
const events = evm.getEvents();
console.log(events);

Expected:
[ 'Transfer(address,address,uint256)', 'Approval(address,address,uint256)', 'ApprovalForAll(address,address,bool)' ]

Actual:
[ 'Approval(address,address,uint256)', 'ApprovalForAll(address,address,bool)' ]

I've found that this is due to the contract initially being deployed with Remix's optimizations. I have been able to replicate the erroneous byte code output in other examples. The event signature seems the be appended to near the end of the bytecode.

Another contract with this issue is the Decentraland MANA contract at 0x0f5d2fb29fb7d3cfee444a200298f468908cc942. After some more research, this looks like a bug in solidity. Where the contract bytecode should end (JUMP-STOP, followed by the swarm hash), it actually followed by the Transfer event signature and then the swarm hash.
The last bytes are as follows, where ddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef after the JUMP-STOP is the Transfer(address,address,uint256) event.
50505600ddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3efa165627a7a72305820f462e7242c33877d5d2f087a81cc0a589147f1cf578ce7fc53451e7ce4fb376f0029
...
POP
POP
JUMP
STOP
'dd'(Unknown Opcode)
CALLCODE
MSTORE
'ad'(Unknown Opcode)
'1b'(Unknown Opcode)
'e2'(Unknown Opcode)
'c8'(Unknown Opcode)
SWAP12
PUSH10 0xc2b068fc378daa952ba7
CALL
PUSH4 0xc4a11628
CREATE2
GAS
'4d'(Unknown Opcode)
CREATE2
'23'(Unknown Opcode)
'b3'(Unknown Opcode)
'ef'(Unknown Opcode)

Of course, this is also not recognized by @j4ys0n's new getABI function contributed in #2

It seems that the culprit starts with the CODECOPY function https://github.com/MrLuit/evm/blob/2f64a4c48b2b6c16974e0d0410904df907282d68/src/opcodes/codecopy.ts#L19-L29
where this.code[##:##] is not parsed in the LOG function
https://github.com/MrLuit/evm/blob/2f64a4c48b2b6c16974e0d0410904df907282d68/src/opcodes/log.ts#L57
I've added another "hack-fix" for this in my local dev...
        let eventTopic = topics[0].toString(16);

        // A hack?
        if(eventTopic && eventTopic.startsWith('this.code')) {
          const regex = /this\.code\[(?<start>[0-9a-f]+):\((?<offset>[0-9a-f]+)\+(?<size>[0-9a-f]+)\)\]/;

          let { start, offset, size } = eventTopic.match(regex).groups;
          start = parseInt(start, 16);
          offset = parseInt(offset, 16);
          size = parseInt(size, 16);

          eventTopic = state.code.slice(start, offset + size).toString('hex');
        }


stl container as function parameter segmentation fault

declare as below:
string GET(string path, map<string, string> headers);

bind as:
        sol::constructors<sol::types<>> con;
        sol::usertype<Net::HttpClient> _httpclient(con,
                                                       "GET", &Net::HttpClient::GET,
                                                       "setHost", &Net::HttpClient::setHost,
                                                       "setProxy", &Net::HttpClient::setProxy);
        L->set_usertype("HttpClient", _httpclient);

lua script content:
   client = HttpClient.new()
   client:setHost("www.example.com")
   client:setProxy("http://<IP_ADDRESS>:8888")
   local h = {}
   h['Test-Header'] = 'Test-Header'
   local res = client:GET("tttttt", h)

Should be fixed with the latest release:
https://github.com/ThePhD/sol2/releases/tag/v2.11.4

👍 Thanks very much.


Remove migrate seed after composer update

Is this in prep for working on #210?

I just noticed last time we deployed into prod, it did a update command, running seeder in prod, which is not what we want.

I just noticed last time we deployed into prod, it did a update command...
@zach2825 actually pointed me to how this was happening: https://github.com/hackgvl/hackgreenville-com/blob/develop/scripts/handle-deploy-update.sh

composer update isn't running on deploy anyway, only in dev when you update your local packages.

I'm not 100% how - but the deploy output shows database seeders running.

It's this line in the deploy script


Add Windows version and SCCM version that rules were introduced

For each WDEG ASR rule, it would be useful to list which version of Windows 10, Windows Server, and SCCM CB the rule was introduced.
As an example for the "Block persistence through WMI event subscription" rule there could be something like below.

This rule was introduced in:

Windows 10: 1903
Windows Server: 1903, LTSC vNext
SCCM CB: 1902

Could also flatten it too:

This rule was introduced in Windows 10 1903, Windows Server 1903, Windows Server LTSC vNext, SCCM CB 1902

Below are my notes for each rule, but I'm not sure if it is totally accurate. I wasn't sure about some of the versions (denoted with ???):

Block executable content from email client and webmail - Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
Block Office applications from creating child processes - Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
Block Office applications from creating executable content - Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
Block Office applications from injecting code into other processes - Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
Block JavaScript or VBScript from launching downloaded executable content - Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
Block execution of potentially obfuscated scripts - Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
Block Win32 API calls from Office macro - Windows 10 1709, Windows Server 1809, Windows Server 2019, SCCM CB 1710
Block executable files from running unless they meet a prevalence, age, or trusted list criteria - Windows 10 1803, Windows Server 1809, Windows Server 2019, SCCM CB 1802???
Use advanced protection against ransomware - Windows 10 1803, Windows Server 1809, Windows Server 2019, SCCM CB 1802
Block credential stealing from the Windows local security authority subsystem (lsass.exe) - Windows 10 1803, Windows Server 1809, Windows Server 2019, SCCM CB 1802
Block process creations originating from PSExec and WMI commands - Windows 10 1803, Windows Server 1809, Windows Server 2019, SCCM CB 1802???
Block untrusted and unsigned processes that run from USB - Windows 10 1803, Windows Server 1809, Windows Server 2019, SCCM CB 1802
Block Office communication applications from creating child processes - Windows 10 1809, Windows Server 1809, Windows Server 2019, SCCM CB 1810???
Block Adobe Reader from creating child processes - Windows 10 1809, Windows Server 1809, Windows Server 2019, SCCM CB 1810???
Block persistence through WMI event subscription - Windows 10 1903???, Windows Server 1903???, Windows Server LTSC vNext, SCCM CB 1902???

My sources for SCCM versions are:

https://docs.microsoft.com/en-us/sccm/protect/deploy-use/create-deploy-exploit-guard-policy
https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1710#protect-devices
https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1802#protect-devices

My sources for Windows Server and Windows Server LTSC are:

https://docs.microsoft.com/en-us/windows-server/get-started-19/whats-new-19#security
https://docs.microsoft.com/en-us/windows-server/get-started/whats-new-in-windows-server-1809#additional-features

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

ID: f9de2e9a-c4c1-3763-6160-9427556291f1
Version Independent ID: 74160e2f-0f99-a37f-7123-81a31a6fab61
Content: Use attack surface reduction rules to prevent malware infection
Content Source: windows/security/threat-protection/windows-defender-exploit-guard/attack-surface-reduction-exploit-guard.md
Product: w10
Technology: windows
GitHub Login: @andreabichsel
Microsoft Alias: v-anbic

@officedocsbot assign @e0i

@iadgovuser1
The issue has been noted and the document will be revised in the light of your feedback.
Thank you.

@e0i this issue is solved by the PR #4430, please review and merge !

@iadgovuser1 : Please have a look at the commit and recent changes to the Github source page:
Rich text diff view:
https://github.com/MicrosoftDocs/windows-itpro-docs/commit/99331095c18b04e588b1942e30be337bdf6d8dfd?short_path=9467fe2#diff-9467fe25b71e6c0368355a30ce380a89
Github page:
windows/security/threat-protection/windows-defender-exploit-guard/attack-surface-reduction-exploit-guard.md

@illfated I can double check these tomorrow in my SCCM 1902 instance to try and answer some of these questions below. Here are my comments:
Block process creations originating from PSExec and WMI commands
SCCM name: Not applicable.
Is that correct? Makes sense if that's true because it isn't compatible with SCCM. Might want to remove "SCCM CB 1802" then.
Block Office communication application from creating child processes
SCCM name: Not yet available.
Is that correct? Seems like it should be there. Might want to remove "SCCM CB 1810" then.
Block Adobe Reader from creating child processes
SCCM name: Not applicable
Is that correct? Seems like it should be there. Might want to remove "SCCM CB 1810" then.
Block persistence through WMI event subscription
SCCM name: Not yet available
This might actually be true since it is so new. This one is missing "This rule was introduced in:" phrasing. It should be in Windows 10 1903.

@iadgovuser1
With the help of your feedback, the issue has been reviewed and an update to the documentation has been published.
Link to PR: https://github.com/MicrosoftDocs/windows-itpro-docs/pull/4430
Thanks for your feedback.

Thank you for those comments and your suggestions for what else needs to be remediated.
I am confident that this can be resolved too, as soon as any of the other contributors will add it to their work list.
I would have take the time myself, but I have got too many distractions going on in my life at the moment.

@illfated So it turns out that those 4 rules are not in SCCM CB 1902. I'd remove all mentions of SCCM CB for those rules in their "introduced in" lines. Outside of that, I wonder why the Adobe Reader one is listed as "Not applicable" instead of "Not yet available". It makes sense that "Block process creations originating from PSExec and WMI commands" is Not Applicable because it will break SCCM. I don't think that would be true for the Adobe Reader rule. That's the only other thing that might need to be changed other than what I mentioned already.

@iadgovuser1
We are closing the issue since the original subject of the issue has been addressed via pull request #4430
Thank you for taking the time to provide feedback and engaging in discussion to improve the documentation. Much appreciated.

@officedocsbot close

@e0i
I will likely open another issue to capture additional changes that may need to be made based on my previous comment.

Good choice. It will be easier to manage 1 pull request / page change per issue ticket.


I put the wrong memo tag how to recover my con back

Hello, I transferred 836.65 xlm from a exchange to other but I put the wrong memo tag.
My withdrawal address- GAHK7EEG2WWHVKDNT4CEQFZGKF2LGDSW2IVM4S5DP42RBW3K6BTODB4A
Memo-1022568865 (but I put<PHONE_NUMBER>bi )
Transection id- 63d483f11f4c2bdbc3f9970b5add21436133fc438a01bb1c9727ed cfd937db2f
Screen shot attached
Please help me😢🙏

You need to contact Binance support team and provide a link to your transaction. They can process your deposit manually.
https://www.binance.com/en/support/faq/115003798632-Summary-of-Incorrect-Deposit


automate setting syntax

syntax highlight
download https://highlightjs.org/download/
add highlight.pack.js to assets/javascript/
add what you like to assets/css
and add this code to application.js
$(document).on('ready', function() {
hljs.initHighlightingOnLoad();
});

done!!!!!!!!!!!! foooooooooooooooooo!!!!!!!!!


Debug apps build in winobjc_internal are failing to launch

Repro:
Install any of the win32 or arm debug apps built from winobjc_internal.
Source code:
// If this assertion fails, a bad pointer has been passed in.  It may be
// totally bogus, or it may have been allocated from another heap.  The
// pointer must have been allocated from the CRT heap.
_ASSERTE(_CrtIsValidHeapPointer(block));
Callstack:
00 ucrtbased!free_dbg_nolock
01 ucrtbased!_free_dbg
02 ucrtbased!free
03 CoreFoundation!__CFStringAppendFormatCore

This Release CoreFoundation -> Debug App and that is correctly triggering the free to use the Debug crt. The allocation however must still be on the release CRT. I will need to track down what exactly I missed. Perhaps a weird other function or a call was proxied through a dll that doesn't have the CRT replacement in it (libobjc2? does it hand out memory for new classes?)

ucrtbase!_realloc_base+0x30
CoreFoundation!__CFDataGrow+0xf8
CoreFoundation!CFDataSetLength+0xbe
Is at least one. Probably most of the _base symbols need redirected as well.

libobjc2 does not use a redirected heap, correct. That's part of why it's one of those things we ship in two versions :(

@DHowett-MSFT was just guessing. Looking more I just missed things.


OpenAPI3 generates allOf for properties with references to another schema and a doc

Playground
Is this necessary? I could see it being necessary for a some $ref semantics, but I don't see this being used in the wild, so I suspect tools will be fine without the allOf

I think the Spectral linter will complain if the $ref is not wrapped in allOf.
https://meta.stoplight.io/docs/spectral/4dec24461f3af-open-api-rules#no-ref-siblings


Hacker Typer

Much less responsive than in Scratch.
http://scratch.mit.edu/projects/72232520/
http://phosphorus.github.io/#72232520
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36

When did Scratch add the 'any' option to the key pressed blocks? It is not working because phosphorus has not implemented it yet.

That was really quick!!! :-) I hadn't noticed the "any" key, Thats for pointing this out. What is now weird to me then it is that it sometimes works... :-?

It only works for me when I press the 'a' key, which is the first letter of 'any'

:-)

Now fixed, please close.


Filled missing help for --destination-path

This checklist is used to make sure that common guidelines for a pull request are followed.

View a preview at https://prompt.ws/r/Azure/azure-cli/5706
This is an experimental preview for @microsoft users.


Rebalance Instances Over-limit

Raspiblitz 1.7.1
lightning-jet v 1.3.0 (installed under bos user)
Observed more rebalance instances than the limit set in the config.json.

Config.json contains: "maxInstances": 10,
Counted (18) node /home/bos/lightning-jet/jet rebalance ... processes in htop
jet monitor displays 14 rebalances in progress

Does the number of instances in jet monitor match ps -ef | grep 'jet rebalance' | grep -v grep?

Unfortunately, no.  Currently at 6 in ps vs 4 in jet monitor.
I reduced maxInstances to 5 for now and cleared it out a couple of times with manual kills.  Seems to creep up over time as if some rebalance processes are stuck in the background?

Reproduced on my prod node.  I had a lot more jet rebalance processes running based on htop than what showed up in jet monitor.   Potential fix in https://github.com/itsneski/lightning-jet/commit/3691b9d81b00966535c5fca799c298790fd12c32, testing in progress.

the issue manifested on my node, had 60 rebalance instances with the max of 15 configured. jet makes a db record for each rebalance instance it launches. it then relies on those records to determine the cur rebalance count.
sometimes db writes fail (e.g. db is locked), but rebalance still proceeds. hence actual rebalance count can be greater than the count of records on the db (which is capped by the configured max).


Fix downloadToFolder Function argument

Fix custom notification content example downloadToFolder argument type error
Fix no notification example downloadToFolder argument type error

Good catch! Thanks for this :+1:

Good catch! Thanks for this 👍

Thank you for merging!


new:usr: Swarm Eve + Benchmark

i suggest to put .idea in .gitignore and remove the .idea dir in the repo


Add mipmapping support in the OpenGL rendering

MIP maps (also known as mipmaps), are bitmaps grouped together and associated with a texture to increase runtime rendering quality and performance. Each bitmap image in the MIP map is a version of the main bitmap image, but at a reduced level of detail from the main image. (taken from the Actionscript developer guide)
This PR generates Mipmaps from a texture, plus sets a specific lod bias specified in the SamplerState

Hello, I have merged this PR and it appears that the rendering is working properly; I would like to ask, if I change all the renderings to MIPNEAREST, will it all take effect? How can I check if it is functioning properly?

Does it have a significant improvement in rendering performance? Will the memory decrease?

Why wasn't this even merged yet? It's important for rendering performance

I think there may be other issues, such as' generateMipmap 'being constantly called, which could cause GPU memory leaks.

Oh yeah

Hello, I have merged this PR and it appears that the rendering is working properly; I would like to ask, if I change all the renderings to MIPNEAREST, will it all take effect? How can I check if it is functioning properly?

I use this guide to see the differences between the mipmapping options

I think there may be other issues, such as' generateMipmap 'being constantly called, which could cause GPU memory leaks.

https://stackoverflow.com/questions/73908487/why-i-have-to-generate-mipmap-every-frame

I think there may be other issues, such as' generateMipmap 'being constantly called, which could cause GPU memory leaks.

https://stackoverflow.com/questions/73908487/why-i-have-to-generate-mipmap-every-frame

I see, that's great!

Cool! That means this definitely needs to be merges.


shouldThrowOnError does not apply to functions.invoke()

Bug report
Describe the bug
When shouldThrowOnError is set on supabaseClient, errors raised from functions.invoke() do not throw.
Additional context
@supabase/functions uses the standard fetch API, which does not throw on HTTP status codes other than 2xx; in addition the wrapper does not return the HTTP status code in the response object which is always in the form { data, error }.
For instance, if the Edge Function was written to reject some unauthorized request by returning a 403 Forbidden response, it is impossible to catch this condition.
In other words, supabaseClient always returns { data, error: null }, even when the HTTP status code indicates an error (unless of course if fetch itself threw in the first place).
This forces the user to provide an additional 'httpError' key in the 'data' object, which feels convoluted and obliges to check errors at two different levels (in error and in data.httpError).
Proposed improvement
Modify the code of @supabase/functions:
1- Detect http status codes other than 2xx, and populate the error property in that case together with the status code, instead of populating the data property
2- Add an option to the invoke() function parameters to pass a shouldThrowOnError boolean flag. If set, throw rather than returning the { data, error } object
I can submit a PR if the above makes sense.

This really surprised me as it seems I have to manually watch for the error prop and rethrow the error to act like a promise. Would love to have this incorporated and would be down to try and make a PR as well

FYI - In the meantime I've made my own function for invoking supabase functions so that this behaves as expected:
export const callSupabaseFunction = async (
  functionName: string,
  params: any
) => {
  const { data, error } = await supabase.functions.invoke(functionName, {
    body: JSON.stringify({
      params,
    }),
  });

  if (error) {
    throw new Error(error.message);
  }

  return data;
};

export const cancelReservation = (reservation_id: string) =>
  callSupabaseFunction("cancel-reservation", {
    reservation_id,
  });

I believe this behavior should be built in as well. Having to inspect the response every single time introduces many areas for errors.


Can this be used just to generate an .env file?

Curious if this supports any sort of output option.
I'd like to use this for development work, but forcing it as the entry point isn't tenable.
Ideally it could process the input file into an output file (which I would then use as a .env file for my python projects, for example)

I'm going to fork this repo, upgrade it with go modules support, and see if I can add support for dumping to file. I will open a PR, if successful.

@eedwards-sk we have just did the module support in a recent PR #34 (@alexions) so the barrier of entry on this enhancement should be one step closer if you have time to follow up.

@eedwards-sk there is a way how to this even without changing the ssm-env tool. Probably this way is not as good as having native support, but it works.
$ cat .env # env variables to be decoded
export HELLO=ssm://super-secret
export=WORLD=dev-environment

$ export $(cat .env | xargs) && ssm-env env > .env_decoded

$ cat .env_decoded
... extra vars ...
HELLO=pass123
WORLD=dev-environment
... extra vars ...

You will get the environment you want but in the decoded state.
In case if you want to limit the env vars, you can easily filter them with grep:
$ export $(cat .env | xargs) && ssm-env env | grep '^HELLO|^USER=' > .env_decoded

$ cat .env_decoded
HELLO=pass123
USER=alexions

I hope this helps!


teleport: Downgrade Go to 1.22 until upstream supports 1.23

Fixes #348922.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 348925 --checkout commit

x86_64-linux

:white_check_mark: 6 packages built:

teleport (teleport_16)
teleport.client (teleport_16.client)
teleport_14
teleport_14.client
teleport_15
teleport_15.client

@winterqt Why is that better, and/or where is that documented?

Why is that better

Less changes to files.

and/or where is that documented?

It's not, I don't think :/ it's just the status quo.

Less changes to files.

A +3 -1 delta in one file vs. a +2 -2 delta in another file is not a significant difference, and certainly not an improvement.

it's just the status quo.

That is not representative of the status quo. I count 43 uses of buildGo122Module and buildGo123Module in individual packages, compared to 20 overrides using buildGo122Module and buildGo123Module in all-packages.nix.
Moreover, leaving the change in teleport/generic.nix is more likely to remind the maintainers that they can revert it once upstream supports 1.23.
So if those are the best arguments one way or the other, I’m going to leave it like this.

I also prefer it to be in the package itself, as with pkgs/by-name, it will likely be in the package.nix more often than all-packages.nix. However, this doesn't apply to this specific package, as I'm not sure pkgs/by-name has a pattern for a package with multiple diff versions yet.
That said, I'm not especially attached to that and am happy with whatever the consensus is.

I would like to point out that overriding buildGoModule in all-packages.nix is the documented way of doing things and not just the status quo.
Even so in pkgs/by-name.
See https://github.com/NixOS/nixpkgs/blob/f67841950fe8e33ae6597cc2dac1bc179c3c2627/pkgs/by-name/README.md#changing-implicit-attribute-defaults.
Please move your override accordingly.

Okay, moved.

@emilylange ah, thanks for that clarification :)

When can this be merged? @winterqt still has requested changes, but it seems that they have been resolved; perhaps I am missing something.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4729

Fixed merge conflict with https://github.com/NixOS/nixpkgs/commit/50e65a512bbaa93add03e4bb9f5188a028f50670.


datetimepicker({'setOptions', {highlightedDates: [] } }) is not updated - calendar view is not updated when "highlightedDates" is set  to different value.

Hello.
Please see the stackoverflow.com question/issue:
xdan/datetimepicker - datetimepicker({'setOptions', {highlightedDates: [] } }) is not updated - calendar view is not updated.
There is plunker code snippet: https://plnkr.co/edit/4HkCp5?p=preview

Found solution...
So problem is that when new value of highlightedDays is empty array, then the "highlightedDays" value is not updated. So you need always some dummy value to update previous value.
This is like a hack, but works. I am passing dummy date from 1970`th, so no one cares about it...


Removed header with  no content that was missed on first validation pass

Docs Build status updates of commit 265e686:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: CannotMergeCommit] Cannot merge commit 265e68675147b3b8f7c9338b91a551825a9d1a84 in branch MissingHeadingContentBM1 of repository https://github.com/TheMythoclast/office-developer-exchange-docs into branch main (commit 999ac0ffbd576308f3c7d03f95e6d273942b04d2). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Crew component giving error message

Every component bellow 1.0 version is not running correctly

Hi @Aerdor1998
Could you explain the problem in more detail?

I dont know!!!!Error in login password Invite my iPhoneEm 23 de jul. de 2024, à(s) 17:40, Carlos Coelho @.***> escreveu:
Hi @Aerdor1998
Could you explain the problem in more detail?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

for me its like this

@juboyy
This is related to LLM, something seems not right there.

@AdrianoDBA
Could you share a screenshot of the problem?

@Aerdor1998
Thank you for your contribution! This issue will be closed. If you have any questions or encounter another problem, please open a new issue and we will be ready to assist you.

I'm facing a issue at Crew Sequential Component, when trying to build a simple multi-agent assistant workflow


Plagiarism

We recently noticed your paper which seemed like an interesting method to detect contamination in language models. However, it seems like it copies the entire experimental setup of our paper, "Evading Data Contamination is (too) Easy" (https://arxiv.org/abs/2402.02823), without any reference to our work as inspiration for this setup. Further, your implementation (i.e., this repository) copies large portions of our implementation without proper attribution. In more detail:

Implementation: This implementation shows blatant and obvious signs of plagiarism. In particular, our entire GitHub repo (https://github.com/eth-sri/malicious-contamination) was copied into this one, except that both the License and the README of our repo were removed. Even the results from our paper are still visible in the notebook you copied! This is not only scientific misconduct and plagiarism but also a copyright violation.

Experimental setup: Your experimental setup matches ours to a large degree without this being credited in any way:

Table 1:

The use of OpenOrca as background data
The use of exactly 25000 samples in your training data
The use of both one and five repeats of the contaminated training data
The use of a rephrased dataset to train on. By looking at your github repo, I can see that the dataset is generated using the exact same code as our rephrased dataset.
The use of the exact same code for the finetuning of your models on the contaminated datasets.
The use of language that is very, very similar to some of our wording. For instance:
Ours: "This leads to an effective contamination of 2% or 10% of the total training set."
Yours: "This results in an effective contamination of 2% or 10% of the entire training set."

Table 2:

The use of a model trained on the uncontaminated portion of the OpenOrca dataset as the uncontaminated model.
The 50%-50% split between contaminated and uncontaminated samples.
We note that you do cite us here, saying that you follow our work in evaluation metrics (based on the paragraph title). However, we do use a different evaluation metric (namely, TPR@5%FPR)

Please fix both your github repo by including the correct licenses and prominent attribution of our work and your paper to acknowledge our work and compare it in detail. Otherwise, we will have to take further steps, such as issuing a takedown notice for your GitHub repo.

Hi, we are sure we did not intend to plagiarize your paper. From our understanding, your paper is to point out the phenomenon of evasive data contamination but our paper focuses on how to detect it. We follow your experiment setup just in the preliminary experiment of in-distribution datasets, but we run more evaluation on OOD datasets like MATH, which we believe is different from your dataset scope. The finetune data settings are following your settings, we are sorry that we didn't mention that in the section 2, but we did cite your paper in the latter section. We admit this is our fault for missing reference, but it is not an intentional plagiarism. We will cite your paper in section 2 to emphasize your work's contribution in the next version of our papr.
For the code, we did use your code to run the preliminary experiment, while we edit some parts of your code so that we can run evaluation on OOD datasets. Besides, we argue that the code for the main method of our paper which is utilizing LLM's internal state for data contamination detection, is not from your repo but implemented by ourselves. We are sorry that we forgot to reference your github repo in our README.  We will mention that our implementation is based on your github, the credit is yours.
Overall, we are sorry that we miss some references for your paper and code, we are not intend to plagiarize your work. If you have any other questions, please let us know.

Hey @JasperDekoninck, in my opinion the main issue here is a lack of reference and acknowledgement, while "Plagiarism" refers to stating other's novel work as their own. As my colleague @ShangQingTu has added acknowledgement to your previous work, would you mind changing the name of your issue?

Thank you for your reply. However, your current explanation is not sufficient. Specifically, the following remains unaddressed:
How does the conclusion in section 2 differ from our paper? Specifically, “Observation 1. ID performance can be easily inflated by contamination” is the exact same observation we report in Table 1 of our paper. This is done using the exact same training data and method. While your paper does present results on other benchmarks (such as GSM-Hard and OOD datasets), you need to discuss more thoroughly why this is different from our setting and what the added benefit is. Right now, you do not discuss this at all, and it seems like you’re claiming the entire experiment is original, and that Observation 1 has not been observed before in the exact same setting with the exact same hyperparameters. This, in our opinion, is scientific misconduct. Given this experiment, we do believe the main issue is plagiarism and not simply a missing reference.
As we mentioned before, we saw that you cited us in section 4 of your paper. However, the citation is not only insufficient but also makes an incorrect claim about our work (that we are using the same evaluation metric as you, which isn’t the case).
Can you please discuss more thoroughly in your paper where your experimental setup in Section 2 came from, and how your conclusions differ from ours? We would also like to see this correction as soon as possible, rather than simply in the next version of your paper.

Thank your for your kindly request. We will modify our arxiv paper and resubmit it to arxiv on September 23, 2024.
We plan to conduct these changes (in bold):
Experimental Setup.
\textbf{Experimental Setup.} Following the experiment settings and hyperparameters from EAL~\cite{dekoninck2024evading}, we fine-tune two representative LLMs, Llama2~\cite{touvron2023llama} and Phi2~\cite{javaheripi2023phi2}, on the instruction dataset OpenOrca~\cite{openorca}, which has no overlap with GSM8K's in-distribution data....
Observation 1
\textbf{Observation 1. ID performance can be easily inflated by contamination.}  As depicted in Table \ref{tab1_benhcmark_alignment_tax}, we find that similar to exact contamination, in-distribution contamination can also greatly improve the performance of LLMs on in-distribution tasks.
At a 2% contamination level, both exact and in-distribution contaminated models achieve about 10% absolute performance gain on ID benchmarks.
Moreover, at a 10% contamination level, the ID gain can be even larger (more than 20%).  This observation is consistent with the findings in EAL~\cite{dekoninck2024evading}, while we further explore whether data contamination can improve models' performance on OOD datasets.
Section 4
\textbf{Models.} Following prior works~\cite{dekoninck2024evading}, we simulate contaminated and uncontaminated models by fine-tuning LLaMA2-7B~\cite{touvron2023llama} to get three different versions: LLaMA2-7B trained on OpenOrca (\textit{uncontaminated}), OpenOrca+GSM-i (\textit{contaminated}) and OpenOrca+GSM-i-Syn (\textit{contaminated}).
\textbf{Implementation Details.}
We will delete: "Following prior works~\cite{dekoninck2024evading}"
Thank you again for your time. If you have any other questions, please let us know.

Thank you for your response. However, we believe that the extent of the copying from our paper necessitates a more thorough intervention. Specifically, in the introduction and abstract, there is no mention that prior work has already shown that “even training on data similar to benchmark data inflates performance on in-distribution tasks without improving overall capacity” and "training on data similar to benchmark data can lead to severe performance overestimation". In-distribution contamination is exactly what we demonstrated in our paper and should therefore be appropriately attributed both in the intro and the abstract, particularly given that the performance overestimation you measure occurs in the same experimental setup as ours. Similarly, the statement "we design an OOD test for a set of fine-tuned LLMs simulating different levels of in-distribution"  should clarify that you again use the same experimental setup as us but additionally evaluate on different, “OOD”, datasets.
Moreover, the second part of your first contribution, "... it causes the model’s capability to be overestimated on ID benchmarks," is essentially the same contribution as ours. The only difference is that you frame it in comparison to OOD benchmarks, while we discuss overestimation in a broader sense. This is a nuanced distinction that warrants at least some discussion as to why it can be a major contribution.
We also noticed that in Section 5, you use the terms "sample-level contamination detection" and "benchmark-level contamination detection". Coincidentally, we defined these exact terms in Section 2 of our paper as the two main forms of contamination. These terms are also a key dimension along which we evaluate methods in Section 4 of our paper. It seems only appropriate to add a reference to where these terms were originally coined.
Overall, the paper appears to be heavily inspired by our work: you use the same code, the same experiment in Section 2, some similarities between your experiment in Section 4 and ours, and the same terminology to differentiate between contamination detection methods. It also seems that your new technique was developed as a way to address the attack we presented in our paper. The issue raised by one of your authors in our GitHub repository further supports this, as indicated by the comment (“First and foremost, I want to express my appreciation for the outstanding work your team has done. Your data rewriting method is very effective,” March 23), where the author explicitly states their intent to reproduce our experiments, making it clear that you were aware of our work. This inspiration should be clearly stated and attributed not only on GitHub but also in your paper.
In summary, while we do not dispute that your paper makes novel contributions (primarily DICE), we ask that you clearly distinguish these from the findings of our work. In particular, we ask that you clearly acknowledge that our work has already shown the increase in (ID) performance after contamination and the differentiation between sample- and benchmark-level contamination.

Hi, thanks for your response, we will further add more references for your work.
We plan to conduct these changes (in bold):
Abstract
The advancement of large language models (LLMs) relies on evaluation using public benchmarks, but data contamination can lead to overestimated performance. Previous researches focus on detecting contamination by determining whether the model has seen the exact same data during training.
Recently, EAL~\cite{dekoninck2024evading} has already shown that even training on data similar to benchmark data inflates performance, namely \emph{In-distribution contamination}. In this work, we argue that in-distribution contamination can lead to the performance drop on OOD benchmarks.
To effectively detect in-distribution contamination, we propose DICE, a novel method that leverages the internal states of LLMs to locate-then-detect the contamination.
...
Introduction
Recently, EAL~\cite{dekoninck2024evading} has already shown that training on data that bears similarity to the benchmark data can lead to severe performance overestimation, namely \emph{In-distribution contamination}. Since pre-training data is massive and hard to distinguish based on their distributions, we narrow our scope to the supervised fine-tuning (SFT) phase.
We aim to answer the following research questions:
(1) Does in-distribution contamination contribute to a model's overall math reasoning ability?
(2) If not, how can we detect it to prevent overestimating the model's capabilities due to contamination?
To investigate whether in-distribution contamination can really improve LLM's math reasoning ability, we design an OOD test for a set of fine-tuned LLMs simulating different levels of in-distribution contamination on GSM8K following prior work's experiment setup~\cite{dekoninck2024evading}.
...
We examine the impact of in-distribution contamination on LLMs' performance on both ID and OOD tasks, revealing that it can lead to the model's performance drop on OOD benchmarks.
Section 5
\section{Related Work}
Prior work~\cite{dekoninck2024evading} has divided the current data contamination detection methods into two categories, benchmark-level contamination detection and sample-level contamination detection.
....
Besides, we will add in the github README that our work is inspired by yours. Thank you again for your time. If you have any other questions, please let us know.

Thank you for your reply! That seems good to us