render

Describe the bug
render error on last stable build
To Reproduce
Steps to reproduce the behavior:

.\wfreerdp.exe /v:<IP_ADDRESS> /u:test1 /p:1 /w:1024 /h:768 /smart-sizing /gdi:hw
change window size

Expected behavior
Normal interface display
Screenshots

Application details

FreeRDP version (xfreerdp /version)
2022-07-08
https://ci.freerdp.com/job/freerdp-nightly-windows/lastStableBuild/
Command line used
.\wfreerdp.exe /v:<IP_ADDRESS> /u:test1 /p:1 /w:1024 /h:768 /smart-sizing /gdi:hw
Output of xfreerdp /buildconfig
OS version connecting to (server side)
win10
If available the log output from a run with /log-level:trace 2>&1 | tee log.txt
If you built it yourself add some notes which tag/commit/branch you have used, also your cmake parameters and
compiler can help

Environment (please complete the following information):

OS: Windows
Version/Distribution: win10 10.0.19044
Architecture: x64

Additional context
20220221 version is work, 20220708 version is not work.

@godtang can you please specify what commit version 20220221 is and what build configuration was used for both versions (call wfreerdp from the command line using the /version and /buildconfig switch).

@godtang can you please specify what commit version 20220221 is and what build configuration was used for both versions (call wfreerdp from the command line using the /version and /buildconfig switch).

I don't think it helps
[15:00:15:445] [43424:00007f94] [DEBUG][com.freerdp.client.common.cmdline] - windows: -2003/1 posix: -1000/0 compat: 1/0
[15:00:24:198] [50944:000078d8] [DEBUG][com.freerdp.client.common.cmdline] - windows: -2004/1 posix: -1000/0 compat: 1/0

@godtang use wfreerdp /version > output.txt (same for /buildconfig) to have the output written to the specified file.

@godtang I just noticed you are using powershell - please run the commands from a windows command prompt (cmd.exe).

Could you try running the working version with the option /gfx:rfx added to the command line and see if the rendering issue is also happening there?
The newer version was built without GFX/H264 support included so the older version might just hide this issue because it is using a different codec in the GFX pipeline.

with wfreerdp.20220221.exe /v:<IP_ADDRESS> /u:vagrant /p:vagrant /w:1024 /h:768 /smart-sizing /gdi:hw, it's work
with wfreerdp.20220221.exe /v:<IP_ADDRESS> /u:vagrant /p:vagrant /w:1024 /h:768 /smart-sizing /gdi:sw, the rendering issue is hanppend
with wfreerdp.20220221.exe /v:<IP_ADDRESS> /u:vagrant /p:vagrant /w:1024 /h:768 /smart-sizing /gdi:hw  /gfx:rfx, the rendering issue is hanppend

@godtang thanks for the feedback so far - I'll try to have a look at this asap

@mfleisz Is there a solution to this issue? I used the latest code for stable-2.0 and still have this problem

@godtang just wanted to take a look but your 20220221 version (commit 50fddfaf5) doesn't seem to link to a valid commit in the FreeRDP repository. Also can you try one more thing: can you compile that version (the 20220221) with the option WITH_MEDIA_FOUNDATION=OFF and check if the issue also happens with that version.

I have the same issue with wfreerdp on windows 10 after resizing the client window with smart sizing enabled:
wfreerdp.exe /v:<IP_ADDRESS> /u:mcsw /p:pass /w:1280 /h:800 /smart-sizing /cert-ignore
https://user-images.githubusercontent.com/4453789/186045397-c0922142-9ead-44dc-976c-77a32695c50d.mp4

build config
This is 3.0.0-dev Build configuration: BUILD_TESTING=OFF HAVE_AIO_H= HAVE_EXECINFO_H= HAVE_FCNTL_H=1 HAVE_GETLOGIN_R= HAVE_GETPWUID_R= HAVE_INTTYPES_H=1 HAVE_STDBOOL_H=1 HAVE_STDINT_H=1 HAVE_STRNDUP= HAVE_SYSLOG_H= HAVE_SYS_EVENTFD_H= HAVE_SYS_FILIO_H= HAVE_SYS_SELECT_H= HAVE_SYS_SOCKIO_H= HAVE_SYS_TIMERFD_H= HAVE_TM_GMTOFF= HAVE_UNISTD_H= HAVE_UNWIND_H= WITH_ADD_PLUGIN_TO_RPATH=OFF WITH_CAIRO=OFF WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_EVENTS=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_DSP_FFMPEG=OFF WITH_DSP_FFMPEG_AVAILABLE=0 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=OFF WITH_FREERDP_DEPRECATED=OFF WITH_GFX_H264=OFF WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_MEDIA_FOUNDATION=OFF WITH_NATIVE_SSPI=ON WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSSL=ON WITH_PROFILER=OFF WITH_PROGRESS_BAR=ON WITH_SAMPLE=OFF WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_EMULATE=OFF WITH_SMARTCARD_INSPECT=OFF WITH_SMARTCARD_PCSC=ON WITH_SOXR=OFF WITH_SPNEGO=OFF WITH_SSE2=ON WITH_SWSCALE=OFF WITH_THIRD_PARTY=OFF WITH_VAAPI=OFF WITH_VAAPI_AVAILABLE=0 WITH_VERBOSE_WINPR_ASSERT=ON WITH_VIDEO_FFMPEG=OFF WITH_VIDEO_FFMPEG_AVAILABLE=0 WITH_WIN8=OFF WITH_WINDOWS_CERT_STORE=ON WITH_WINMM=ON WITH_WINPR_DEPRECATED=OFF WITH_WINPR_TOOLS=ON WITH_WIN_CONSOLE=OFF WITH_ZLIB=OFF`

I tried with /gdi:hw parameter but wfreerdp crashes just after it connects:
wfreerdp.exe /v:<IP_ADDRESS> /u:mcsw /p:pass /w:1280 /h:800 /smart-sizing /cert-ignore /gdi:hw

log
[17:41:37:124] [33652:000078cc] [INFO][com.freerdp.client.windows] - Detected stdin=-1 -> gui mode
[17:41:37:127] [33652:000078cc] [DEBUG][com.freerdp.client.common.cmdline] - windows: 0/1 posix: -1000/0
[17:41:37:127] [33652:000078cc] [DEBUG][com.freerdp.client.common] - This is 3.0.0-dev Build configuration: BUILD_TESTING=OFF HAVE_AIO_H= HAVE_EXECINFO_H= HAVE_FCNTL_H=1 HAVE_GETLOGIN_R= HAVE_GETPWUID_R= HAVE_INTTYPES_H=1 HAVE_STDBOOL_H=1 HAVE_STDINT_H=1 HAVE_STRNDUP= HAVE_SYSLOG_H= HAVE_SYS_EVENTFD_H= HAVE_SYS_FILIO_H= HAVE_SYS_SELECT_H= HAVE_SYS_SOCKIO_H= HAVE_SYS_TIMERFD_H= HAVE_TM_GMTOFF= HAVE_UNISTD_H= HAVE_UNWIND_H= WITH_ADD_PLUGIN_TO_RPATH=OFF WITH_CAIRO=OFF WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_EVENTS=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_DSP_FFMPEG=OFF WITH_DSP_FFMPEG_AVAILABLE=0 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=OFF WITH_FREERDP_DEPRECATED=OFF WITH_GFX_H264=OFF WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_MEDIA_FOUNDATION=OFF WITH_NATIVE_SSPI=ON WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSSL=ON WITH_PROFILER=OFF WITH_PROGRESS_BAR=ON WITH_SAMPLE=OFF WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_EMULATE=OFF WITH_SMARTCARD_INSPECT=OFF WITH_SMARTCARD_PCSC=ON WITH_SOXR=OFF WITH_SPNEGO=OFF WITH_SSE2=ON WITH_SWSCALE=OFF WITH_THIRD_PARTY=OFF WITH_VAAPI=OFF WITH_VAAPI_AVAILABLE=0 WITH_VERBOSE_WINPR_ASSERT=ON WITH_VIDEO_FFMPEG=OFF WITH_VIDEO_FFMPEG_AVAILABLE=0 WITH_WIN8=OFF WITH_WINDOWS_CERT_STORE=ON WITH_WINMM=ON WITH_WINPR_DEPRECATED=OFF WITH_WINPR_TOOLS=ON WITH_WIN_CONSOLE=OFF WITH_ZLIB=OFF
Build type:          Release
CFLAGS:              /DWIN32 /D_WINDOWS  /Gd /W3
Compiler:            MSVC, 19.0.24234.1
Target architecture: x64
[17:41:37:127] [33652:00006f40] [DEBUG][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state
[17:41:37:127] [33652:00006f40] [DEBUG][com.freerdp.locale.keyboard] - Platform keyboard detection failed, trying autodetection
[17:41:37:127] [33652:00006f40] [DEBUG][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[17:41:37:127] [33652:00006f40] [DEBUG][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[17:41:37:127] [33652:00006f40] [DEBUG][com.freerdp.channels.cliprdr.client] - VirtualChannelEntryEx
[17:41:37:127] [33652:00006f40] [DEBUG][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[17:41:37:127] [33652:00006f40] [DEBUG][com.freerdp.channels.drdynvc.client] - VirtualChannelEntryEx
[17:41:37:127] [33652:00006f40] [DEBUG][com.freerdp.client.common.cmdline] - loading channelEx drdynvc
[17:41:37:129] [33652:00006f40] [DEBUG][com.freerdp.primitives] - primitives benchmark result:
[17:41:37:291] [33652:00006f40] [DEBUG][com.freerdp.primitives] -  * generic= 28
[17:41:37:444] [33652:00006f40] [DEBUG][com.freerdp.primitives] -  * optimized= 91
[17:41:37:444] [33652:00006f40] [DEBUG][com.freerdp.primitives] - primitives autodetect, using optimized
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_INITIAL --> CONNECTION_STATE_NEGO
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state
[17:41:37:446] [33652:00006f40] [DEBUG][com.freerdp.core] - freerdp_tcp_default_connect:freerdp_set_last_error_ex resetting error state
[17:41:37:447] [33652:00006f40] [DEBUG][com.freerdp.core] - connecting to peer <IP_ADDRESS>
[17:41:37:447] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3
[17:41:37:449] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - RDP_NEG_RSP::flags = { [0x01] |EXTENDED_CLIENT_DATA_SUPPORTED }
[17:41:37:449] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - selected_protocol: 2
[17:41:37:449] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_FINAL
[17:41:37:449] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - Negotiated NLA security
[17:41:37:449] [33652:00006f40] [DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_HYBRID
[17:41:37:451] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - -- NLA_STATE_INITIAL	--> NLA_STATE_INITIAL
[17:41:37:452] [33652:00006f40] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExW
[17:41:37:453] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - nla_client_init 1001 : packageName=Negotiate ; cbMaxToken=48256
[17:41:37:454] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -  InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
[17:41:37:454] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - ----->> sending...
[17:41:37:454] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> protocol version 6
[17:41:37:454] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> auth info
[17:41:37:454] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> client nonce
[17:41:37:454] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - [93 bytes]
[17:41:37:454] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - -- NLA_STATE_INITIAL	--> NLA_STATE_NEGO_TOKEN
[17:41:37:454] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_NEGO --> CONNECTION_STATE_NLA
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - <<----- receiving...
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    <<----- protocol version 2
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    <<----- nego token
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -  InitializeSecurityContext status SEC_E_OK [0x00000000]
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - ----->> sending...
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> protocol version 6
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> auth info
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> public key auth
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> client nonce
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - [855 bytes]
[17:41:37:563] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - -- NLA_STATE_NEGO_TOKEN	--> NLA_STATE_PUB_KEY_AUTH
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - <<----- receiving...
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    <<----- protocol version 2
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    <<----- public key info
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - ----->> sending...
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> protocol version 6
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> public key auth
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] -    ----->> client nonce
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - [104 bytes]
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - -- NLA_STATE_PUB_KEY_AUTH	--> NLA_STATE_AUTH_INFO
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.nla] - -- NLA_STATE_AUTH_INFO	--> NLA_STATE_FINAL
[17:41:37:675] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_NLA --> CONNECTION_STATE_MCS_CONNECT
[17:41:37:787] [33652:00006f40] [DEBUG][com.freerdp.core.gcc] - Server rdp encryption method: NONE
[17:41:37:787] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_MCS_CONNECT --> CONNECTION_STATE_MCS_ATTACH_USER
[17:41:37:897] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_MCS_ATTACH_USER --> CONNECTION_STATE_MCS_CHANNEL_JOIN
[17:41:38:560] [33652:00006f40] [DEBUG][com.freerdp.core.info] - Client Info Packet Flags = INFO_MOUSE|INFO_DISABLECTRLALTDEL|INFO_UNICODE|INFO_MAXIMIZESHELL|INFO_LOGONNOTIFY|INFO_COMPRESSION|INFO_ENABLEWINDOWSKEY|INFO_FORCE_ENCRYPTED_CS_PDU|INFO_LOGONERRORS|INFO_MOUSE_HAS_WHEEL|INFO_NOAUDIOPLAYBACK
[17:41:38:560] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_MCS_CHANNEL_JOIN --> CONNECTION_STATE_LICENSING
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_LICENSING --> CONNECTION_STATE_CAPABILITIES_EXCHANGE
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_CAPABILITIES_EXCHANGE --> CONNECTION_STATE_FINALIZATION
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - [CONNECTION_STATE_FINALIZATION] reset finalize_sc_pdus
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - rdp_send_data_pdu: sending data (type=0x1f size=37 channelId=1008)
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - rdp_send_data_pdu: sending data (type=0x14 size=41 channelId=1008)
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - rdp_send_data_pdu: sending data (type=0x14 size=41 channelId=1008)
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.activation] - Persistent Key List: TotalKeyCount: 0 MaxKeyFrag: 2042
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.activation] - persistentKeyList count: 0
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.activation] - numEntriesCache: 0: 0 1: 0 2: 0 3: 0 4: 0
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.activation] - totalEntriesCache: 0: 0 1: 0 2: 0 3: 0 4: 0
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - rdp_send_data_pdu: sending data (type=0x2b size=57 channelId=1008)
[17:41:38:671] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - rdp_send_data_pdu: sending data (type=0x27 size=41 channelId=1008)
[17:41:38:779] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - recv Synchronize Data PDU (0x1F), length: 22
[17:41:38:779] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - [CONNECTION_STATE_FINALIZATION] received flag FINALIZE_SC_SYNCHRONIZE_PDU| [0x0001]
[17:41:38:779] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - recv Control Data PDU (0x14), length: 26
[17:41:38:779] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - [CONNECTION_STATE_FINALIZATION] received flag FINALIZE_SC_CONTROL_COOPERATE_PDU| [0x0002]
[17:41:38:779] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - recv Control Data PDU (0x14), length: 26
[17:41:38:779] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - [CONNECTION_STATE_FINALIZATION] received flag FINALIZE_SC_CONTROL_GRANTED_PDU| [0x0004]
[17:41:38:779] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - recv Font Map Data PDU (0x28), length: 26
[17:41:38:779] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - [CONNECTION_STATE_FINALIZATION] received flag FINALIZE_SC_FONT_MAP_PDU| [0x0008]
[17:41:38:779] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_FINALIZATION --> CONNECTION_STATE_ACTIVE
[17:41:38:779] [33652:00006f40] [INFO][com.freerdp.gdi] - Local framebuffer format  PIXEL_FORMAT_BGRX32
[17:41:38:779] [33652:00006f40] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32
[17:41:38:796] [33652:00006f40] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd
[17:41:38:796] [33652:00006f40] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel ainput
[17:41:38:796] [33652:00006f40] [DEBUG][com.freerdp.channels.drdynvc.client] - register_plugin: num_plugins 1
[17:41:38:796] [33652:00006f40] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx
[17:41:38:796] [33652:00006f40] [DEBUG][com.freerdp.channels.drdynvc.client] - register_plugin: num_plugins 2
[17:41:38:796] [33652:00006f40] [TRACE][com.freerdp.channels.ainput.client] - ...
[17:41:38:796] [33652:00006f40] [DEBUG][com.freerdp.channels.drdynvc.client] - create_listener: 1.FreeRDP::Advanced::Input.
[17:41:38:796] [33652:00006f40] [TRACE][com.freerdp.channels.rdpgfx.client] - ...
[17:41:38:796] [33652:00006f40] [DEBUG][com.freerdp.channels.drdynvc.client] - create_listener: 2.Microsoft::Windows::RDS::Graphics.
[17:41:38:797] [33652:00004d7c] [DEBUG][com.freerdp.utils.scard] - [rdpdr-channel] receive [RDPDR_CTYP_CORE | PAKID_CORE_SERVER_ANNOUNCE] [0x000c0001] -> 12
[17:41:38:797] [33652:00006f40] [DEBUG][com.freerdp.core.update] - Primary Drawing Order [0x0a] OpaqueRect
[17:41:38:797] [33652:00004d7c] [TRACE][com.freerdp.utils.scard] - 0000 72 44 6e 49 01 00 0c 00 02 00 00 00             rDnI........
[17:41:38:797] [33652:00004d7c] [TRACE][com.freerdp.utils.scard] - [length=12]
[17:41:38:797] [33652:00006f40] [DEBUG][com.freerdp.core.update] - Primary Drawing Order [0x0a] OpaqueRect
[17:41:38:797] [33652:00004d7c] [DEBUG][com.freerdp.utils.scard] - [rdpdr-channel] sending [RDPDR_CTYP_CORE | PAKID_CORE_CLIENTID_CONFIRM] [0x000c0001] -> 12
[17:41:38:797] [33652:00004d7c] [TRACE][com.freerdp.utils.scard] - 0000 72 44 43 43 01 00 0c 00 02 00 00 00             rDCC........
[17:41:38:797] [33652:00004d7c] [TRACE][com.freerdp.utils.scard] - [length=12]
[17:41:38:797] [33652:00004d7c] [DEBUG][com.freerdp.utils.scard] - [rdpdr-channel] sending [RDPDR_CTYP_CORE | PAKID_CORE_CLIENT_NAME] [0x00000001] -> 48
[17:41:38:797] [33652:00004d7c] [TRACE][com.freerdp.utils.scard] - 0000 72 44 4e 43 01 00 00 00 00 00 00 00 20 00 00 00 rDNC........ ...
[17:41:38:797] [33652:00004d7c] [TRACE][com.freerdp.utils.scard] - [length=48]
[17:41:38:797] [33652:00006f40] [ERROR][com.freerdp.core.update] - order flags 0d failed
[17:41:38:797] [33652:00006f40] [ERROR][com.freerdp.core.fastpath] - Fastpath update Orders [0] failed, status 0
[17:41:38:797] [33652:00006f40] [ERROR][com.freerdp.core.fastpath] - fastpath_recv_update() - -1
[17:41:38:797] [33652:00006f40] [ERROR][com.freerdp.core.fastpath] - fastpath_recv_update_data() fail
[17:41:38:801] [33652:00006f40] [INFO][com.freerdp.client.windows] - Window is shown!
[17:41:38:801] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_ACTIVE - rdp_recv_pdu() - -3
[17:41:38:801] [33652:00006f40] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -3
[17:41:38:801] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - transport_check_fds() - -1
[17:41:38:801] [33652:00006f40] [DEBUG][com.freerdp.core] - rdp_check_fds() - -1
[17:41:38:801] [33652:00006f40] [ERROR][com.freerdp.core] - freerdp_check_fds() failed - 0
[17:41:38:801] [33652:00006f40] [INFO][com.freerdp.client.common] - Network disconnect!
[17:41:38:801] [33652:00006f40] [ERROR][com.freerdp.client.windows] - Failed to check FreeRDP file descriptor
[17:41:38:801] [33652:00006f40] [DEBUG][com.freerdp.core.rdp] - [CONNECTION_STATE_ACTIVE] reset finalize_sc_pdus
[17:41:38:801] [33652:00006f40] [DEBUG][com.freerdp.core.connection] - rdp_client_transition_to_state CONNECTION_STATE_ACTIVE --> CONNECTION_STATE_INITIAL
[17:41:38:802] [33652:00006f40] [TRACE][com.freerdp.channels.ainput.client] - ...
[17:41:38:802] [33652:00006f40] [TRACE][com.freerdp.channels.rdpgfx.client] - ...
[17:41:38:803] [33652:00006f40] [DEBUG][com.freerdp.client.windows] - Main thread exited with 0
[17:41:38:805] [33652:000078cc] [ERROR][com.freerdp.core] - freerdp_abort_connect_context:freerdp_set_last_error_ex ERRCONNECT_CONNECT_CANCELLED [0x0002000B]
[17:41:38:805] [33652:00006fd4] [DEBUG][com.freerdp.client.windows] - Keyboard thread exited.

I tried compiling with swscale and ffmpeg but it still has the same glitch and also still crashes in the same way with /gdi:hw

build config
This is 3.0.0-dev Build configuration: BUILD_TESTING=OFF HAVE_AIO_H= HAVE_EXECINFO_H= HAVE_FCNTL_H=1 HAVE_GETLOGIN_R= HAVE_GETPWUID_R= HAVE_INTTYPES_H=1 HAVE_STDBOOL_H=1 HAVE_STDINT_H=1 HAVE_STRNDUP= HAVE_SYSLOG_H= HAVE_SYS_EVENTFD_H= HAVE_SYS_FILIO_H= HAVE_SYS_SELECT_H= HAVE_SYS_SOCKIO_H= HAVE_SYS_TIMERFD_H= HAVE_TM_GMTOFF= HAVE_UNISTD_H= HAVE_UNWIND_H= WITH_ADD_PLUGIN_TO_RPATH=OFF WITH_CAIRO=OFF WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_EVENTS=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_DSP_FFMPEG=OFF WITH_DSP_FFMPEG_AVAILABLE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=ON WITH_FREERDP_DEPRECATED=OFF WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_MEDIA_FOUNDATION=OFF WITH_NATIVE_SSPI=ON WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSSL=ON WITH_PROFILER=OFF WITH_PROGRESS_BAR=ON WITH_SAMPLE=OFF WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_EMULATE=OFF WITH_SMARTCARD_INSPECT=OFF WITH_SMARTCARD_PCSC=ON WITH_SOXR=OFF WITH_SPNEGO=OFF WITH_SSE2=ON WITH_SWSCALE=ON WITH_THIRD_PARTY=OFF WITH_VAAPI=OFF WITH_VAAPI_AVAILABLE=1 WITH_VERBOSE_WINPR_ASSERT=ON WITH_VIDEO_FFMPEG=ON WITH_VIDEO_FFMPEG_AVAILABLE=1 WITH_WIN8=OFF WITH_WINDOWS_CERT_STORE=ON WITH_WINMM=ON WITH_WINPR_DEPRECATED=OFF WITH_WINPR_TOOLS=ON WITH_WIN_CONSOLE=OFF WITH_ZLIB=OFF
Build type:          Release
CFLAGS:              /DWIN32 /D_WINDOWS  /Gd /W3
Compiler:            MSVC, 19.0.24234.1
Target architecture: x64

Also interestingly, I notice some other things:
The video I posted in my previous comment shows the graphical glitching when using smart size and the window is sized to be larger than original size.
If the window is sized to be smaller than original size than different graphical glitching occurs. Also, I notice that when resizing the window, the glitching is temporarily fixed:
https://user-images.githubusercontent.com/4453789/186797368-529eee61-c35b-4f30-a9cd-2a74bc31aa9a.mp4
So, I had thought that maybe if I could figure out what code is executing during the resizing process, then I could also have this code run while using the client normally and it would fix the glitching? I have been fiddling with the code but have not completely fixed it.
The closest I have come is adding
GetWindowRect(wfc->hwnd, &windowRect);
InvalidateRect(wfc->hwnd, &windowRect, TRUE);

to
case WM_PAINT: in freerdp\client\Windows\wf_event.c
This appears to almost fix the problem when the window is sized larger than original, however there is still a strange region on the top-right that does not appear to update correctly:
https://user-images.githubusercontent.com/4453789/186798162-4a86aa46-1b99-41cc-b0e7-9e2559879d24.mp4
And the same glitching still happens when the window is sized smaller than original.
If someone with more knowledge and experience with this code has any suggestions as to what other code to look at that might fix this problem, it could be helpful.

I believe I have fixed this.
https://github.com/FreeRDP/FreeRDP/pull/8153

swscale or cairo are required for full smart-sizing functionality, you don´t have that in your buildconfig...


Implement a validation tool to ensure that an LSIF conforms to the spec

Things handled:

vertex before edge emitting
shape of edge and vertex
cardinality of edges
type of outV and inV of edges
sharding

This has happened and ships.


[WIP] Implement ActorSingleton for DistributedActor

Resolves https://github.com/apple/swift-distributed-actors/issues/824
⚠ WIP - haven't updated tests yet ⚠

Okey I think I have some work to be done here to make it nicer to implement! I'll follow up as soon as I'm out of compiler land <3

I'll check this out and see how to improve use of actor context and metadata now 👍

Make this PR mergeable to prepare for https://github.com/apple/swift-distributed-actors/pull/1001


GUI component throws error

Describe the bug
The Security component of the GUI fails to run. It cannot run SecureTea.py
To Reproduce
Steps to reproduce the behavior:

Run server app
Run gui app
Open gui at localhost:4200
Scroll down to Security
Run it without filling any entry

Expected behavior
SecureTea should run with log monitor and other standalone features
Why this may have happened according to you
The args generated for SecureTea are not proper
Anything else you were doing before this happened?
No
Screenshots

This image shows the error thrown
Desktop (please complete the following information):

Operating System:Ubuntu
OS version: 16.04
Browser Firefox
Version 74.0

Tackled with https://github.com/OWASP/SecureTea-Project/pull/256


Dev->UAT update Pak Andi

Coverage decreased (-0.003%) to 34.59% when pulling 0fc5961e3972fe790f54038745abdc9393f1fcff on dev into 9c8d4adfae1df3485fb4a076a56538ae881d3057 on uat.


Can not re-subscribe after stream failure

Trying to handle stream-failed event by re-subscribing to the same stream passed by the event with no luck. The SDP is sent but no response from the server is received and there is no error on the server side.
It's while the same approach works well for publisher, that is when a publish stream fails I can re-publish by handling stream-failed event.
PS: I use NetLimiter in order to drop or limit a connection(stream).

I have the very same  problem.
I noticed that in case of stream-failed the property failed of the stream is set to 'true'
That value is then checked on signaling messages received, both from the server and other peers (not p2p and p2p), not processing the signaling message in case the stream has the failed property set to true.
Here the two part of Room.js where all happen.
// if !p2p
that.socket.on('signaling_message_erizo', function (arg) {
   var stream;
   if (arg.peerId) {
       stream = that.remoteStreams[arg.peerId];
   } else {
       stream = that.localStreams[arg.streamId];
   }

   if (stream && !stream.failed) {
       stream.pc.processSignalingMessage(arg.mess);
   }
});

// if p2p "You can see that the message is processed anyway"
that.socket.on('signaling_message_peer', function (arg) {

   var stream = that.localStreams[arg.streamId];

   if (stream && !stream.failed) {
       stream.pc[arg.peerSocket].processSignalingMessage(arg.msg);
   } else {
       stream = that.remoteStreams[arg.streamId];

       if (!stream.pc) {
           createRemotePc(stream, arg.peerSocket);
       }
       stream.pc.processSignalingMessage(arg.msg);
   }
});

The first workaround I find is to manually delete the failed property from the stream on stream-failed. This bypass that check and allow a stream to be published again.
The problem is that the stream-failed event could be fired both for a publisher and for a subscriber.
In the Subscriber stream-failed case I don't think it is correct or useful to allow a user to re-subscribe the same failed stream (since isn't on the server anymore).
In the Publisher stream-failed case I think instead that allow the user to republish his local stream is the correct thing to do.
I created a pull request with a possible fix. You can check it here
Let me know.
Simone

Republishing a stream that has previously failed is a very sensitive issue. There are several checks implied in both client and server side. So we have to handle it carefully. My opinion is that we would have to analyze every possible scenario and try to search a robust solution.
Right now the client API is though to avoid the publication of a failed stream, so the solution is to create a new stream and publish it instead of the first one.
However, I still see an issue in the current implementation. To improve the behavior, the check should be done when publishing the stream, not when processing signaling messages from erizo. Thus, when you try to publish a stream with stream.failed = true, the API responds with an error message explaining that you have to create a new stream and publish it.
What do you think? Could you propose a PR implementing this?

Hello @aalonsog,

Right now the client API is though to avoid the publication of a failed stream, so the solution is to create a new stream and publish it instead of the first one.

You mean make a new getUserMedia()? It isn't a waste of time and resources? Event if a stream fails remotely, its local version is still valid. Am I wrong?
As far as I know, if a stream is marked as local it means that is a stream owned by the user that receive the message. Furthermore, I noticed that the stream-failed routine it unpublish the stream from licode, it resets its peerconnection, it sets the failed property to true and then it fires the stream-failed. So the handling process is very similar to a normal unpublish with the difference that is originated by something else going wrong (e.g. ICE CANDIDATE NEGOTIATION FAIL or similar).
This led me to implement the pull request I just posted, because in the end the state of the room after a stream-failed is the same of after a stream unpublish.

However, I still see an issue in the current implementation. To improve the behavior, the check should be done when publishing the stream, not when processing signaling messages from erizo. Thus, when you try to publish a stream with stream.failed = true, the API responds with an error message explaining that you have to create a new stream and publish it.

Also this is true. This is the reason why I had to check erizoJS code to understand whats happening.
I think I can implement the check you said, but then I have to review my client side code to handle a stream-failed by recreating a new local stream which, in my opinion, is not necessary.
What do you think?
Simone

Hi @simonemazzoni,
I agree with you, perhaps creating again the stream (and having to ask to user to accept media access) is not the best solution.
You are also right that setting the failed property to the stream is followed by unpublishing it. Taking this into account I think the best solution is to set failed property to false again when the stream has been successfully unpublished (when the unpublish callback is called). Assuming that when the stream has been unpublished it is in the same status as initially and it is ready to be published again. I prefer this because we avoid possible future checks of failed property.

Good, LGTM!
I'll make some tests with this logic and I'll make a new PR.

Of course, this is complementary with avoiding to publish a stream that has stream.failed = true

Yes, of course! I'll also implement the stream.failed check on publish to avoid the publish of failed streams.

Hi @aalonsog, I implemented the solution we discussed here, but I noticed few things on the client side logic that I would like to discuss with you.
I noticed that, from publisher point of view, when a stream-failed event is raised, is then followed by a stream-removed one, because the stream-failed routine it unpublish the stream that has failed.
This looks good to me, because if the stream doesn't work anymore, is right to remove it from licode and to signal it to the subscribers.
Assuming this, the thing I don't understand, is the needs to send a 'stream-failed' event!
Wouldn't be easier and cleaner to send only the stream-removed event, eventually setting the stream.failed property to true?
I'm saying this because from a publisher point of view, it causes confusion, because if he receives a stream-failed event on a published stream, he can't republish the same stream until he received the associate stream-removed event from that stream. So what's the point of listening the stream-failedevent? (This is the case of a stream-failed of a successfully published stream)
Furthermore, I noticed that in case of stream-failed during the publish routine, it's never fired the stream-added event to subscribers, but then is fired a stream-removed, so subscribers receive stream-removed events of streams never added.
I guess there is something mishandled in the logic.
Could you confirm that?
Please, tell me if I wasn't clear enough. It isn't an easy case to explain :)

Let me clear the subject. There are two possible scenarios:

When the stream between publisher and the server fails.
When the stream between subscriber and the server fails.

In the first scenario it's obvious that the publisher needs to publish again, either by re-getting the user media or by re-publishing the same stream (if available).
The second scenario, which is more common and happens frequently for clients with poor Internet connection, of course it is the responsibility of the server to drop the failed stream and re-send it for the subscriber because the source stream from the publisher is still alive.

@mkhahani I agree, for the first scenario.

The second scenario, which is more common and happens frequently for clients with poor Internet connection, of course it is the responsibility of the server to drop the failed stream and re-send it for the subscriber because the source stream from the publisher is still alive.

For the second scenario I think that the only thing that the server can do is to signal the subscriber that the stream has failed, so that the subscriber can retry a new subscribe since the stream of the publisher is still alive.

@aalonsog I updated my PR .
I implemented the error callback on both publish and subscribe if the stream has the failed property.
I also implemented the deletion of the stream.failed property on successful unpublish callback, to allow a user to try to republish its local stream as we discussed.


[Feature Request] Add support for LRCLIB as a source for synced lyrics

Hello,
It would be cool to see this project integrating LRCLIB as a source for time synced lyrics.
Thanks

thanks. will look into this. currently busy with work stuff


Lexsort output is incorrect

The output of cupy.lexsort is incorrect. I can't see any pattern as to what is wrong with the output.
Code to reproduce
import cupy
import numpy

# numpy output is correct:
a = (numpy.random.random((10,2)) * 10).astype(int)  # random ints between 0 and 9
print(a[numpy.lexsort(a.T[::-1])])                  # sorted by first column, not last

# cupy output is unsorted:
b = cupy.array(a)
print(b[cupy.lexsort(b.T[::-1])])

The same thing happens for floats, so that's not the reason.
Conditions
(output of python -c 'import cupy; cupy.show_config()'):
CuPy Version          : 7.1.1
CUDA Root             : /opt/cuda
CUDA Build Version    : 10020
CUDA Driver Version   : 10020
CUDA Runtime Version  : 10020
cuBLAS Version        : 10202
cuFFT Version         : 10102
cuRAND Version        : 10102
cuSOLVER Version      : (10, 3, 0)
cuSPARSE Version      : 10301
NVRTC Version         : (10, 2)
cuDNN Build Version   : 7605
cuDNN Version         : 7605
NCCL Build Version    : 2507
NCCL Runtime Version  : 2507

Thanks for the report, I can reproduce the result.

Not sure if this is relevant, but lexsort would fail these two tests:
diff --git a/tests/cupy_tests/sorting_tests/test_sort.py b/tests/cupy_tests/sorting_tests/test_sort.py
index b00856866..5b0c67d58 100644
--- a/tests/cupy_tests/sorting_tests/test_sort.py
+++ b/tests/cupy_tests/sorting_tests/test_sort.py
@@ -202,6 +202,20 @@ class TestLexsort(unittest.TestCase):
         with self.assertRaises(TypeError):
             return cupy.lexsort(a)

+    @testing.for_dtypes('fdFD')
+    @testing.numpy_cupy_allclose()
+    def test_nan2(self, xp, dtype):
+        a = testing.shaped_random((2, 10), xp, dtype)
+        a[0, 2] = a[1, 6] = xp.nan
+        return xp.lexsort(a)
+
+    @testing.for_dtypes('fdFD')
+    @testing.numpy_cupy_allclose()
+    def test_nan3(self, xp, dtype):
+        a = testing.shaped_random((2, 10), xp, dtype)
+        a[1, 2] = a[1, 6] = xp.nan
+        return xp.lexsort(a)
+

 @testing.parameterize(*testing.product({
     'external': [False, True],

lexsort with a[0, 2] = a[0, 6] = xp.nan is correct, though.


Add XML template literal parsing

Description:
Refer: https://ballerina.io/spec/lang/2020R1/#xml-template-expr

Duplicate of https://github.com/ballerina-platform/ballerina-lang/issues/23044


Issue?

Just after import I get this Error:
ERROR in ./~/vue-star-rating/src/star-rating.vue Module parse failed: .../node_modules/vue-star-rating/src/star-rating.vue Unexpected token (1:0) You may need an appropriate loader to handle this file type. | <template> |     <div> |         <div @mouseleave="resetRating" id="stars">
...imported in a project with a lot of other dependencies, all installed with npm, all included in package.json (using webpack and Vue 2.1.8 )
Can't see any error, do you have a hint?

When using npm, you are transpiling the .vue files themselves, so you will need to make sure you have vue-loader and babel-loader in your project (because the component is written in ES6). I tried this out with webpack-simple and it compiles correctly. I don't really use webpack day to day, but I think you will need to make sure you have the following in your webpack config:
  module: {
    rules: [
      {
        test: /\.vue$/,
        loader: 'vue-loader',
      },
      {
        test: /\.js$/,
        loader: 'babel-loader',
        exclude: /node_modules/
      },
    ]
  }

You can see the config I worked with at:  https://github.com/vuejs-templates/webpack-simple/blob/master/template/webpack.config.js#L11
To get babel to work, you need to include  babel-core and babel-preset-es2015
Then create a .babelrc file in the root of your project and add the following:
{
  "presets": [
    ["es2015"]
  ]
}

Hmm,
babel-loader / -transpiler and vue-loader are already included and running - my whole project is written in ES6 and everything else is working fine...
So I think I need to invest some time in webpack and debug what's really happening.
Anyway, thanks for your reply!

Okay, I found my mistake - I excluded vue-loader for the node_modules -directory...
Thanks for your help!

Excellent! thanks for following up with your solution. I will close this issue now.


Send eventdata using batches

Here's an example from the article https://devblogs.microsoft.com/azure-sdk/announcing-the-stable-release-of-the-python-event-hubs-client-library-using-pure-python-amqp-stack/#create-the-client-and-send-an-event:
from azure.eventhub import EventHubProducerClient, EventData

connection_str = '<< CONNECTION STRING FOR THE EVENT HUBS NAMESPACE >>'
eventhub_name = '<< NAME OF THE EVENT HUB >>'
client = EventHubProducerClient.from_connection_string(connection_str, eventhub_name=eventhub_name)

event_data_batch = client.create_batch()
can_add = True
while can_add:
    try:
        event_data_batch.add(EventData('Message inside EventBatchData'))
    except ValueError:
        can_add = False  # EventDataBatch object reaches max_size.

with client:
    client.send_batch(event_data_batch)

Quick change to test sending data in batches: make --text a multiple option.

@eventdata.command(name="send")
@click.option(
    "--text",
    required=True,
    multiple=True,
)
@click.pass_context
def send(ctx: click.Context, text: str):
    """Send a single event data to Azure Event Hubs"""

    client = EventHubProducerClient.from_connection_string(
        ctx.obj['connection_string'],
        eventhub_name=ctx.obj['name'],
    )

    event_data_batch = client.create_batch()

    for _text in text:
        try:
            event_data_batch.add(EventData(_text))
        except ValueError as e:
            print("Event data batch is full ({} messages).".format(len(event_data_batch)))
            raise e

    print(f"Sending event data to {ctx.obj['name']}")
    with client:
        client.send_batch(event_data_batch)

Should I also pick text from stdin?

Using https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/eventhub/azure-eventhub/samples/sync_samples/send_stream.py as a reference to make sending more flexible.

Drafting UX for getting input from --text option or stdin:
$ cat multiline.txt
line 1
line 2
line 3

$ cat multiline.txt | eh eventdata send
adding text: line 1
adding text: line 2
adding text: line 3


Hoooope for RTS5250 support

As a RTS5250 user,I really want to get my device useful in macOS.Hope for it.

See FAQ - Device Support.


Example of box staying the same size regardless of zoom like original Marker

The google.maps.marker stays the same size regardless of how zoomed in or out the map is.
How can the same effect be archived?
Add a box or gltf can become invisible if the users is zoomed to far our or in.

I made a hack that works by using the bounds of the map, and then calculating a initial size of the bounds with a start scale and then animating it based on that. Super rough, but it archives it. I first thought of using the zoom level, but since it is a number between 18 and 5, and I don't know if it is linear, I was not sure about that solution.

vs normal google maps js-three

https://codesandbox.io/s/unruffled-yalow-7c7dk?file=/src/index.ts

zoom level, but since it is a number between 18 and 5,

Should be able to use zoom to scale the object as the map changes. The zoom should follow a pattern similar to the following:
20 : 1128.497220
19 : 2256.994440
18 : 4513.988880
17 : 9027.977761
16 : 18055.955520
15 : 36111.911040
14 : 72223.822090
13 :<PHONE_NUMBER>00
12 :<PHONE_NUMBER>00
11 :<PHONE_NUMBER>00
10 : 1155581.153000
9  : 2311162.307000
8  : 4622324.614000
7  : 9244649.227000
6  : 18489298.450000
5  : 36978596.910000
4  : 73957193.820000
3  : 147914387.600000
2  : 295828775.300000
1  : 591657550.500000

@jpoehnelt Thank you, did not know that, that is better 😄


Contradictory unit for expiresIn value

Description
In the documentation / README for this section:

expiresIn: expressed in seconds or a string describing a time span zeit/ms.

Eg: 60, "2 days", "10h", "7d". A numeric value is interpreted as a seconds count. If you use a string be sure you provide the time units (days, hours, etc), otherwise milliseconds unit is used by default ("120" is equal to "120ms").

Consider expiration as 60, which is a pure numeric value. First it says "A numeric value is interpreted as a 'seconds' count." but later in the section it says "(if not string) otherwise 'milliseconds' unit is used by default ("120" is equal to "120ms")"
So is it 60 seconds or milliseconds?
Reproduction
Refer to the above section and find the same in the documentation / README
Environment

Version of this library used: 8.5.1
Version of the platform or framework used, if applicable: NA
Other relevant versions (language, server software, OS, browser): Irrelevant
Other modules/plugins/libraries that might be involved: None

60 in number => 60 seconds
"60" in string => 60 miliseconds

Thanks for feedback, for others, you might consider "60s" to remove any doubt if it is seconds or milliseconds

Thank you @0x0a0d and @tdewin!


Fixed the test suite

Some modules weren't being required by the spec_helper, spec_steps.rb
didn't seem to be using valid syntax, and the require calls were missing
for various test dependencies.

RSpec knows to load the requires from rails_helper.rb. Are you unable to run the test suite with bundle exec rspec on master? It should work using the vagrant or docker setups if there's something wonky with your local environment.

Yeah, it wasn't running on my dev box.
Must be an outdated gem somewhere, I'll try upgrading.
On Mar 8, 2017 4:36 PM, "Gannon McGibbon"<EMAIL_ADDRESS>wrote:

RSpec knows to load the requires from rails_helper.rb. Are you unable to
run the test suite with bundle exec rspec on master? It should work using
the vagrant or docker setups if there's something wonky with your local
environment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/winnipegrb/just_chew/pull/15#issuecomment-285192508,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACGmZvtceUZ7yhah_E1QXt0jVsJ9s-29ks5rjy1VgaJpZM4MXX6q
.

Found the issue, for whatever reason the rails_helper file wasn't being required automatically. The spec_helper file was though.


Validate the master_account setting

Can you elaborate this one?

Currently, the setting of the master_account (which takes an account ID) is not being validated - you can potentially put a string that is not even an ID, or an ID that does not exist. It should be validated properly at some point.


differencies in output when using heap between GCC_ARM and ARM builds

used configuration:
// Physical block device
HeapBlockDevice bd(1024*512, 512);
// File system declaration
LittleFileSystem fs("fs");

compiled by GCC_ARM

Mounting the filesystem... lfs error:469: Corrupted dir pair at 0 1
lfs error:2202: Invalid superblock at 536873884 536874136
Fail :(
No filesystem found, formatting... OK
Opening "/fs/numbers.txt"... Fail :(
No file found, creating a new file... OK
Writing numbers (10/10)... OK
Seeking file... OK
Incrementing numbers (10/10)... OK
Closing "/fs/numbers.txt"... OK
Opening the root directory... OK
root directory:
.
..
numbers.txt
Closing the root directory... OK
Opening "/fs/numbers.txt"... OK
numbers:
1
2
3
4
5
6
7
8
9
10
Closing "/fs/numbers.txt"... OK
Unmounting... OK
Mbed OS filesystem example done!

compiled by ARM

Mounting the filesystem... lfs error:469: Corrupted dir pair at 0 1
lfs error:2202: Invalid superblock at 1 536880404
Fail :(
No filesystem found, formatting... OK
Opening "/fs/numbers.txt"... Fail :(
No file found, creating a new file... OK
Writing numbers (10/10)... OK
Seeking file... OK
Incrementing numbers (10/10)... OK
Closing "/fs/numbers.txt"... OK
Opening the root directory... OK
root directory:
.
..
numbers.txt
Closing the root directory... OK
Opening "/fs/numbers.txt"... OK
numbers:
1
1
2
3
4
5
6
7
8
9
Closing "/fs/numbers.txt"... OK
Unmounting... OK
Mbed OS filesystem example done!

Hmm, this is precisely the issue that was fixed in https://github.com/ARMmbed/mbed-os-example-filesystem/pull/34
What hash of the example are you using?

git log -n 1 mbed-os-5.8.0-oob
commit c76e4f121387fcff7cac233fbb0137c6e0bc6ba4 (HEAD -> mbed-os-5.8.0-oob, tag: mbed-os-5.8.0-rc2, origin/mbed-os-5.8.0-oob)

The fix here:
29a91bf
is only on master it looks like, it needs to be cherry picked to the release branch.
@geky

ARM Internal Ref: MBOTRIAGE-511

Is this issue still relevant? can be closed?

Yes can be closed


Promtool doesn't work with PrometheusRules for prometheus-operator

Currently the promtool only works with raw rule definition yaml. Would be nice (and simple to implement) ability to use promtool on PrometheusRule definitions for the prometheus-operator
related issue
Proposal
Allows usage of standard promtool test rules with kubernetes PrometheusRules
Current workaround I am using a small simple wrapper (note yq I am using is from brew not pip)
cat $1 | yq r - spec > temprule
echo "rule_files:\n  - temprule\n\n" | cat - $1.promtest > temptest
promtool test rules temptest
rm temprule
rm temptest

I don't think it's the role of promtool to handle formats not defined by Prometheus itself, this is something that'd better live in the operator.

agreed

I agree formats not defined for prometheus directly should not be handled here (ie the entire PrometheusRule), but what I was suggesting was for the promtool unittest field we provide the option of specifying a field directive
ie
rule_files:
  - rule.yaml:spec

This would allow a rule to exist in any yaml and still be tested with the standard promtool.

I think it'd be better if it was either possible that "rule_files" come from stdin or you just use something like faq to extract the .spec content and write it to where the unit test file expects.

Agreed, allowing reading from stdin would be nice to not require a temporary FS storage location.

Does using /dev/stdin not work?

You're right, it should probably work.

Yes, that works, great. Will close this then, as it can be written in a single command-line using an external tool which is better suited for supporting various non-Prometheus-native formats than promtool itself.


Is 24H2 supported?

Since 24H2 officially release, I'd like to know if it's supported before updating

It likely isn't since there hasn't been an update for a while and 24H2 seems to require some changes, see Win11 24H2 · Issue #26 · Slion/VirtualDesktop.

Yeah, works fine on 24H2.


add support for scala 2.12 where possible

Has a bunch of changes into the build to get it to work and replace spray.http.Uri with Uri from https://github.com/lemonlabsuk/scala-uri
(spray sub project doesn't get 2.12 version)

Nice, scala-uri looks a bit more pleasant to use as well.

Coverage decreased (-0.1%) to 50.933% when pulling d4f302e482eecc5ef9f6ec1aaed390cfa1aef3f5 on Doikor:feature/2.12 into 214c8af79388ed525c53ff05b4f871e7e5c1b8ba on qvantel:master.


Deprection warnings due to use of positional arguments in Container classes

Using the dev branch of HDMF I'm seeing the following deprecation warnings for most Container classes defined here (e.g,. the
EventsTypesTable and ActionsTTypesTable).

I'm not sure if this is an issue in the extension or whether the autogeneration of Container classes in HDMF needs to be updated to use positional arguments.

This may not be an error in the extension code itself. It looks like those classes are autogenerated, so it may be that those arguments are somehow passed a positional arguments to the constructor of the parent class. This warning was added in https://github.com/hdmf-dev/hdmf/pull/730 It may be that the class generator in HDMF need to be updated. @rly any idea.

So this is due to the docval in DynamicTable having a warning for args in the init. I'm looking for where args are used.

@mavaylon1 and I discussed this today. It relates to the use of call_docval_func. I raised this issue in HDMF https://github.com/hdmf-dev/hdmf/issues/748


Filtering removes image

I am finding that when you start to filter the results, it removes the chosen image.

When removing the filter, the image is displayed as expected.

Thank you @rsiddle for this, .. it's a known issue with Chosen, check #19
There's a pending PR from @iamcal to fix this, harvesthq/chosen#2373 (reference)
Once this is fixed in Chosen, will update the extension,


Labels rendering

Hello, i have one question about rendering labels of roads, areas and etc.
I using tegola as tile server and react-map-gl as lib for react application to render it. Assume that I have to attach "glyphs" field and layer with the type equals symbol to the style.json for frontend part of application to display fonts.
I can't understand how i can display my own labels, when i used raster maps render it was very simple (just need to change column`s field or tag to display it ).  In your's tutorial you use openbox styles to display labels. So, how i can render my own data, it's possible with my current stack?

Not sure if this answers your question, @Linolium, but I've had to work out a local fontstack recently myself. I ended up using genfontgl, specifying an output location of glyphs in my server root, then used "glyphs": "/glyphs/{fontstack}/{range}.pbf in my mapbox json style. node-fontik might also be applicable in this context but I got to genfontgl first.
Hope that helps.

@Linolium it will probably be helpful to look at some of the style sheets in the tegola-web-demo repo. here is an example of using a tag to put a label on a line for transport_lines and an example of a symbol layer can be found here.

@erictheise @ARolek Thx a lot, i will try something with it soon. I will leave a response about result.

I configured glyphs on client, it works perfectly but i am using mapbox servers to take glyphs and sprites.
I tried to write my own server for that(kotlin + springboot) but got some problems with protobuf protocol. Where can i take glyphs and sprites servers to deploy it on my VM?

@Linolium have you considered using github pages to host the glyphs and sprites? That's what the tegola demo is doing.

@ARolek glyphs requests currently don't working in demo, all requests have 404 status. I wonder, it's necessary to get glyphs as requests with content type application/x-protobuf or i can get them in different way.

@Linolium everything shows as a 200 on this end (screen shot attached)

@ARolek maybe it's private? Because i get errors

And when i follow this link i get

@ARolek argh, i understood, it's because of adblock in chrome, when i turned it off everything worked

@Linolium I wonder why adblocker is blocking GH pages...

@ARolek i dunno, finnaly i did it, everything work fine

I just wrote simple spring-boot application for provide glyphs, fonts and construct routes, thx you a lot for help.


mentalCommandActiveAction issue

The API is not working as expected..
We are trying to set the commands to be used by using the below request..
{"jsonrpc":"2.0","method":"mentalCommandActiveAction","params":{"cortexToken":"XXXX","status":"set","session":"20863a01-5e61-4e33-8304-7ac6287f3497","actions":["lift"],"profile":"XXX"},"id":411114}
REsponse:
{"id":411114,"jsonrpc":"2.0","result":{"actions":["lift"],"message":"Set MentalCommand active actions successfully"}}
But subsequent get calls provide multiple "commands" like "neutral, list, push".... whereas we were expecting "lift" only...

@Akshathhm , which param you set in the request get mentalCommandActiveAction ?
"session" or "profile"
https://emotiv.gitbook.io/cortex-api/advanced-bci#profile-name-or-session-id
if you set param "profile" and you don't save this profile before. command "lift" just save to memory .

and you are working on Cortex v2 or v1. if on v1, I recommend you change to use v2 with more feature and bug fixing.
if on v2 please create ticket on this repo
https://github.com/Emotiv/cortex-v2-example

We are using cortext v2..
We tried to set the mentalCommandActiveAction using session.. So, do we need to updateSession after that?
or saving the profile is sufficient?
Subsequent get calls provide multiple commands like "neutral" ,"push", "lift".. which is not correct

we tried to call saveProfile - but its saying "profilename already exist"...
So here is what we want

Call mentalCommandActiveAction API to set the commands
Try subscribe to the steams  and expect only the activated command

did you try with new profile and work from your project ?

We got it work by doing following steps
Load the profile
Call mentalCommandActiveAction API
save the profile


(KHO-156) Feature/student works backend

Checklist

[ ] I have performed a self-review of my code
[ ] I have reached out to another developer to review my code
[ ] New and existing unit tests pass locally with my changes
[ ] All Lint and CI checks are passing

I'm ready to approve once the last 2 changes are made 👍


feat(RingTheory/Idempotents): Lifting complete orthogonal idempotents along nil extensions

Looks good to me, but didn't look at proofs at all. I hope we can get this in soon, feel free to ping me if there's no movement and I'll hit merge!

bors merge


slurm: <IP_ADDRESS> -> <IP_ADDRESS>

Things done
https://github.com/SchedMD/slurm/blob/slurm-20.02/RELEASE_NOTES
https://github.com/SchedMD/slurm/blob/slurm-20.02/NEWS
@bhipple marking the PR WIP as it breaks pyslurm at the moment.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test slurm

I don't have a computer setup at the moment to test the new slurm, but the diff LGTM.  I've opened an issue upstream with pyslurm to try to get an idea of how long / when they plan on upgrading:
https://github.com/PySlurm/pyslurm/issues/172
Ideally, we'd wait for pyslurm to cut a release, which would also give us some time to wait for any bugfix releases of slurm itself to shake out.  If pyslurm expects to take a while absorbing the upgrade, then perhaps we could create multiple versions of the slurm package?

@bhipple thanks for opening the issue. We can wait for feedback from pyslurm. NixOS 20.03 will run on 19.05 anyway. There is no hurry to upgrade on master.

It has been a while. Should we move on with the update?

It looks like there's an open PR for pyslurm with some activity a few weeks ago:
https://github.com/PySlurm/pyslurm/pull/175
I gave a prod to see if it can move forward; would be nice not to break pyslurm if we can avoid it.

@bhipple it would be great if we could get Slurm 20.02 in before the 20.09 branch-off. In case pyslurm does not make a new release in the next weeks, would you be comfortable with with just using the the commits from the pyslurm PR as patches?

That sounds reasonable.  I'd also be OK marking pyslurm as broken for the meanwhile until upstream supports it.  Not ideal, but users who still want it can pin/patch in overlays.

Re-based to latest master. Ready to merge.


Make port of Musicbot Fix

Hey Guys,
got a Firewall blocking Output of UDP/TCP
Is there a way to make the Port of the Musicbot fix?
Now its random, and i dont want to open all ports of my Rapsberrypi
Greetz

Discord API traffic is handled over port 443, which is the port which the traffic leaves your computer as well as the port where it arrives at Discord's servers. When you reach out to the server, the server replies with a port to communicate that traffic on. This port is chosen randomly from a range from about 1400+ (I don't remember the exact number off the top of my head).
However
In order for your computer to handle the port assignment (say the Discord API server says it wants you to use 25565), then outbound traffic must be allowed out of 25565 on your machine. Egress filtering is strongly encouraged, especially for Enterprise environments, but said egress filtering is handled at the edge firewall level, not at the workstation. You can block outbound ports on a workstation, but it's best handled as a blacklist (closing specific ports) instead of a whitelist. If you whitelist, you will run into all kinds of access issues.
TL;DR
Don't do egress filtering at the device level. Allow all (*) outbound traffic and apply egress filtering at the edge router if that is a requirement.


Fail safe tests with missing credentials

We use the same approach found in the Luis Recognizer Middleware tests for all the tests that need specifics keys (environment variables):

Validate the required environment variables with an EnvironmentVariablesDefined() method.
If any variable is not defined, terminate the test as a valid test.

This pull-request fixes #429

@cleemullins, we changed Debug.WriteLine for Assert.Inconclusive


Allow marking Qualys WAS security weaknesses as findings.

This is a compromise between #3348 and #3150. Some users may want to include the "Security Weakness" findings from Qualys as findings, while others may want to make them informational. (Note that the minimum finding level is left at Low. That was not changed from #3348, but may be a subject of contention between users.)
This PR improves the logic for determining this and adds a QUALYS_WEAKNESS_IS_VULN boolean toggle to settings to allow you to opt-in to having "Security Weakness" have a severity.

Can you also add a DD_QUALYS_WEAKNESS_IS_VULN? Or maybe even make the name more explicit to indicate it affects the web parser, but not the infra parser?

I have fixed the naming and added an environment variable.

@cody-m-tibco please review.

@iwalton3 could you resolve the conflicts please?

thanks @iwalton3
@madchap @damiencarol @Maffooch still happy to merge this?

We should have a unit test that shows the parser modification.
As it modifies how the parser works, could you add a unit test that shows the weakness as finding when we activate this option?

I added a unit test for this.


Cluster Update Failure When Adding a New Slurm Queue

Required Info:

AWS ParallelCluster version [e.g. 3.1.1]:3.1.4
Full cluster configuration without any credentials or personal data.

Region: us-east-1

Image:
  Os: alinux2

HeadNode:
  InstanceType: m5.xlarge
  Networking:
    SubnetId: subnet-0aa9d3bd709f86d50
    SecurityGroups:
    - sg-045290f659c3be158
  Ssh:
    KeyName: pcluster
  LocalStorage:
    RootVolume:
      Size: 600
      VolumeType: gp3
  Iam:
    AdditionalIamPolicies:
    - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore

Scheduling:
  Scheduler: slurm
  SlurmSettings:
    Dns:
      DisableManagedDns: true
      UseEc2Hostnames: true
  SlurmQueues:
  - Name: oar
    ComputeResources:
    - Name: m5xlarge
      InstanceType: m5.xlarge
      MinCount: 2
      MaxCount: 10
    Networking:
      SubnetIds:
      - subnet-0aa9d3bd709f86d50
      SecurityGroups:
      - sg-045290f659c3be158
    Iam:
      AdditionalIamPolicies:
      - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
  SlurmQueues:
  - Name: oarm6id24xlarge
    ComputeSettings:
      LocalStorage:
        RootVolume:
          Size: 500
    ComputeResources:
    - Name: m6id24xlarge
      InstanceType: m6id.24xlarge
      MinCount: 0
      MaxCount: 2
    Networking:
      SubnetIds:
      - subnet-0aa9d3bd709f86d50
      SecurityGroups:
      - sg-045290f659c3be158
    Iam:
      AdditionalIamPolicies:
      - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore

SharedStorage:
- MountDir: /share
  Name: efs-covid
  StorageType: Efs
  EfsSettings:
    FileSystemId: fs-7fce8efd

#AdditionalPackages:
#  IntelSoftware:
#    IntelHpcPlatform: true

DirectoryService:
  DomainName: dc=ncisdev,dc=noaa
  DomainAddr: ldap://<IP_ADDRESS>,ldap://<IP_ADDRESS>
  PasswordSecretArn: arn:aws:secretsmanager:us-east-1:716453263077:secret:MicrosoftAD.Admin.Password-gDGZv6
  DomainReadOnlyUser: cn=adjoin,ou=service,ou=NCISDEV,dc=ncisdev,dc=noaa
  AdditionalSssdConfigs:
    ldap_auth_disable_tls_never_use_in_production: True

Tags:
  - Key: noaa:environment
    Value: dev
  - Key: noaa:fismaid
    Value: noaa5006
  - Key: noaa:lineoffice
    Value: nesdis
  - Key: noaa:programoffice
    Value: 40-00
  - Key: noaa:taskerorderid
    Value: 13051420fneea0147
  - Key: noaa:application
    Value: OAR WRF-Chem

Cluster name: oar-pcluster

Output of pcluster describe-cluster command.

{
  "creationTime": "2022-06-30T19:35:47.455Z",
  "headNode": {
    "launchTime": "2022-06-30T19:38:44.000Z",
    "instanceId": "i-00c4711259d394ae3",
    "instanceType": "m5.xlarge",
    "state": "running",
    "privateIpAddress": "<IP_ADDRESS>"
  },
  "version": "3.1.4",
  "clusterConfiguration": {
    "url": "https://parallelcluster-e2ca1557272da85b-v1-do-not-delete.s3.amazonaws.com/parallelcluster/3.1.4/clusters/oar-pcluster-wtisscfpi6pepclv/configs/cluster-config.yaml?versionId=ZkTmb6RC_GHCxLLymscOGWLSeh0womE4&AWSAccessKeyId=AKIA2NT7RG3SULLIW55M&Signature=EPFIQnc8YB%2BsP3CunBz3WBPvLfY%3D&Expires=1661212485"
  },
  "tags": [
    {
      "value": "13051420fneea0147",
      "key": "noaa:taskerorderid"
    },
    {
      "value": "3.1.4",
      "key": "parallelcluster:version"
    },
    {
      "value": "noaa5006",
      "key": "noaa:fismaid"
    },
    {
      "value": "dev",
      "key": "noaa:environment"
    },
    {
      "value": "OAR WRF-Chem",
      "key": "noaa:application"
    },
    {
      "value": "nesdis",
      "key": "noaa:lineoffice"
    },
    {
      "value": "40-00",
      "key": "noaa:programoffice"
    }
  ],
  "cloudFormationStackStatus": "UPDATE_ROLLBACK_COMPLETE",
  "clusterName": "oar-pcluster",
  "computeFleetStatus": "RUNNING",
  "cloudformationStackArn": "arn:aws:cloudformation:us-east-1:716453263077:stack/oar-pcluster/d7077910-f8ab-11ec-aa98-0e38e0433449",
  "lastUpdatedTime": "2022-08-22T22:34:59.022Z",
  "region": "us-east-1",
  "clusterStatus": "UPDATE_FAILED"
}

[Optional] Arn of the cluster CloudFormation main stack:

Bug description and how to reproduce:
When trying to use to update the already existing cluster with the configuration above I get an error.
Interface: [eni-0966644c5bb6b0347] in use. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidNetworkInterface.InUse; Request ID: 557b2408-e32b-4d37-adfd-a0332a8c0ce9; Proxy: null)
The only thing that is changing from the original configuration is the addition of the Slurm queue oarm6id24xlarge.
If you are reporting issues about scaling or job failure:
We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.
For issues with Slurm scheduler, please attach the following logs:

From Head node: /var/log/parallelcluster/clustermgtd, /var/log/parallelcluster/clusterstatusmgtd (if version >= 3.2.0), /var/log/parallelcluster/slurm_resume.log, /var/log/parallelcluster/slurm_suspend.log, /var/log/parallelcluster/slurm_fleet_status_manager.log (if version >= 3.2.0) and/var/log/slurmctld.log.
From Compute node:  /var/log/parallelcluster/computemgtd.log and /var/log/slurmd.log.

If you are reporting issues about cluster creation failure or node failure:
If the cluster fails creation, please re-execute create-cluster action using --rollback-on-failure false option.
We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.
Please be sure to attach the following logs:

From Head node: /var/log/cloud-init.log, /var/log/cfn-init.log and /var/log/chef-client.log
From Compute node:  /var/log/cloud-init-output.log.

Additional context:
Any other context about the problem. E.g.:

CLI logs: ~/.parallelcluster/pcluster-cli.log
Custom bootstrap scripts, if any
Screenshots, if useful.

Hello @joehellmersNOAA,
Based on the Slurm Configuration you've provided, the Scheduling Section seems to have 2 SlurmQueues sections. The ParallelCluster Configuration format requires the Scheduling section to have a single SlurmQueues section under which a list of queues can be provided. (Scheduling-v3)
Kindly try updating the cluster after removing the second SlurmQueues section and moving oarm6id24xlarge queue to the first one.
This should have been caught by some validation. Could you confirm that you did not suppress validation when running the update? If not, then some validation checks may be needed.

Thanks for the catch.
No I did not suppress validations.

I made the following Scheduling section, and got the same error:
Scheduling:
  Scheduler: slurm
  SlurmSettings:
    Dns:
      DisableManagedDns: true
      UseEc2Hostnames: true
  SlurmQueues:
  - Name: oarm6id24xlarge
    ComputeSettings:
      LocalStorage:
        RootVolume:
          Size: 500
    ComputeResources:
    - Name: m6id24xlarge
      InstanceType: m6id.24xlarge
      MinCount: 0
      MaxCount: 2
    Networking:
      SubnetIds:
      - subnet-0aa9d3bd709f86d50
      SecurityGroups:
      - sg-045290f659c3be158
    Iam:
      AdditionalIamPolicies:
      - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
  - Name: oar
    ComputeResources:
    - Name: m5xlarge
      InstanceType: m5.xlarge
      MinCount: 2
      MaxCount: 10
    Networking:
      SubnetIds:
      - subnet-0aa9d3bd709f86d50
      SecurityGroups:
      - sg-045290f659c3be158
    Iam:
      AdditionalIamPolicies:
      - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore

Hello @joehellmersNOAA,
I'm not yet able to reproduce the issue with the above configuration.
The Network Interface referenced in the error seems to be attached to the HeadNode.
Normally the HeadNode attributes (such as the network interface) should not be updated when making updates to the compute nodes/queue
Could you kindly share the ChangeSet printed in the terminal when you attempt running the cluster update?
Also, can you confirm that no manual changes were made to the HeadNode Launch Template (AWSConsole>EC2>Launch templates>HeadNodeLaunchTemplate_*)? Thanks.

BTW, why does the new queue need to be the first one in the list?

The new queue does not need to the first one in the list.
I believe you added it as the first one following my comment "Kindly try updating the cluster after removing the second SlurmQueues section and moving oarm6id24xlarge queue to the first one."? In this regard I was referring to the first SlurmQueues section.

Yes, I can confirm that the LaunchTemplate was not manually configured.
The ChangeSet is
{
  "cluster": {
    "clusterName": "oar-pcluster",
    "cloudformationStackStatus": "UPDATE_IN_PROGRESS",
    "cloudformationStackArn": "arn:aws:cloudformation:us-east-1:716453263077:stack/oar-pcluster/d7077910-f8ab-11ec-aa98-0e38e0433449",
    "region": "us-east-1",
    "version": "3.1.4",
    "clusterStatus": "UPDATE_IN_PROGRESS"
  },
  "validationMessages": [
    {
      "level": "WARNING",
      "type": "DomainAddrValidator",
      "message": "The use of the ldaps protocol is strongly encouraged for security reasons."
    }
  ],
  "changeSet": [
    {
      "parameter": "HeadNode.LocalStorage",
      "requestedValue": {
        "RootVolume": {
          "Size": 600,
          "VolumeType": "gp3"
        }
      },
      "currentValue": "-"
    },
    {
      "parameter": "Scheduling.SlurmQueues",
      "requestedValue": {
        "Name": "oarm6id24xlarge",
        "ComputeSettings": {
          "LocalStorage": {
            "RootVolume": {
              "Size": 500
            }
          }
        },
        "ComputeResources": [
          {
            "Name": "m6id24xlarge",
            "InstanceType": "m6id.24xlarge",
            "MinCount": 0,
            "MaxCount": 2
          }
        ],
        "Networking": {
          "SubnetIds": [
            "subnet-0aa9d3bd709f86d50"
          ],
          "SecurityGroups": [
            "sg-045290f659c3be158"
          ]
        },
        "Iam": {
          "AdditionalIamPolicies": [
            {
              "Policy": "arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore"
            }
          ]
        }
      }
    }
  ]
}

Thanks for sending the logs.
Based on the ChangeSet, the LocalStorage properties of the HeadNode were updated:
      "parameter": "HeadNode.LocalStorage",
      "requestedValue": {
        "RootVolume": {
          "Size": 600,
          "VolumeType": "gp3"
        }
      },
      "currentValue": "-"

At this moment, ParallelCluster does not support updates to the HeadNode of an existing cluster.
In this case, CloudFormation tried to replace the existing HeadNode instance but it had the NetworkInterface (eni-0966644c5bb6b0347) being used hence the error:
Interface: [eni-0966644c5bb6b0347] in use. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidNetworkInterface.InUse; Request ID: 557b2408-e32b-4d37-adfd-a0332a8c0ce9; Proxy: null)

Was the HeadNode's LocalStorage property defined in the earlier versions of the cluster configuration?

Yes, I had manually updated the storage on the HeadNode.  I modified the configuration file to not include that specification, but it is still getting the same message.  Attached are the chanageset and log file for the latest attempt.
changeset2.log
pcluster-cli2.log

I'm afraid this is happening because when CloudFormation performs an UPDATE rollback it does not remove newer template versions but only resets the default version. Because of this all new updates will be recognized as having a change in the head node LT. Can you try to remove all versions except for version 1 for the head node Launch Template (lt-0e1bdf08d1d3e53a4) either through console or AWS CLI?

That did the trick.  Is this considered a bug?

Hi @joehellmersNOAA , thanks for reporting the issue.
Yes, the update of removing root volume should be blocked by our validation logic. We are tracking this issue and tracking the fix internally.
I am going to close this issue soon if you don't have other questions.
Thank you!


Increase default request timeout

Some CI tests in https://github.com/qiboteam/qibo-cloud-backends are failing due to timeout 10.
This issue seems to disappear by increasing timeout to e.g. 20s.
@marcorossi5, do you see some negative side effect for this increase?

Its ok to increase the timeout. It should have no effect.

Thanks @marcorossi5.


Fix "below" virtual text not working with 'rightleft'

Problem:  "below" virtual text doesn't work with 'rightleft'.
Solution: Use column from right border with 'rightleft'.

wow, kudos for adding a right-left test!


Get tests running in CI

To do

[x] Set PYTHONPATH in CI. Done here.
[x] Generate settings.py file (or arrange to use .env, and arrange for .env to be there).
[x]  Ensure that broker is running in CI.

Implemented by @jessicamillar here.


Sorting with custom field component?

Hello, firstly I would like to say thanks for this beautiful table, it has already saved me a lot of time).
Sorting toggle works perfect without custom component, and I think my main problem is how to trigger the table to change sorting field manually.
Also inside my custom component I can't get how to detect by which field table is sorted now.
Thanks

@halws Vuetable cannot really predict how it should sort column with custom component. But if you could explain your use case, it might have more idea on how this should be implemented.
If you would like to manipulate the sorting manually, you could use sort-order prop to manipulate how the sort should be done.

@ratiw Thanx for reply, my use case is next:
There is a table, which has custom fields component in its header. In each field, there should be two sortable cells.

Do you think possible solution could be use of event Bus?

@halws This is not possible for Vuetable since the @click event was bound in the <component> tag outside of the Field Component.

@ratiw Ok, now i get it). Anyway thank you.

For me the solution was to use sort-order prop with required sorting params.
Firstly, I created custom field components, which i registered locally.
Inside them, on click pass( sync) desired sort params throw vuex to the main table component. Then reload table with new sort params.
vuex
state: {
	sortOrder: { field: "id", sortField: "id", direction: "desc" }
	},
getters: {
	ortOrder(state) {
		return [state.sortOrder];
	}
},
mutations: {
	SET_SORT_FIELD: (state, sort) => (state.sortOrder = sort),
}

table component
computed: {
	sortOrder() {
		return this.$store.getters.sortOrder;
		}
	},
watch: {
	sortOrder() {
		this.$set(this.moreParams, "table", this.table);
		his.reloadTable();
	}
},
 methods: {
	  reloadTable() {
		this.$nextTick(function() {
			// this is required because vuetable uses tableFields internally, not fields
			this.vuetable.normalizeFields();
			this.vuetable.reload();
		});
	},
}

custom field component
<span
    class="fields__span sortable"
    @click="sort"> sort me</span>

methods: {
	sort() {
		this.$store.commit("SET_SORT_FIELD", {
		field: created_at,
		sortField: created_at,
		direction: this.sortOrder.direction === "desc" ? "asc" : "desc"
	  });
	}
}

@halws I like that you can come up with a creative solution that could solve your problem. Thanks for sharing the solution. :)

You may also use the orderBy method of vuetable
methods: {
        sort() {
            this.vuetable.orderBy(this.rowField);
        }
    }


[0.3/mtl] update metal-rs and wrap RP switch into an ARP

Sibling of #2972 for hal-0.3 with a version bump

bors r=aleksijuvani

Added a changelog entry
bors r=aleksijuvani

Fixes the minimized/hidden issues mentioned in https://github.com/gfx-rs/gfx/issues/2659 & https://github.com/gfx-rs/wgpu/issues/78

Bors retry

On Aug 22, 2019, at 16:58, bors[bot]<EMAIL_ADDRESS>wrote:
Build failed
continuous-integration/travis-ci/push
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Bors retry
One of the bots don't have x11 available?

On Aug 22, 2019, at 18:04, bors[bot]<EMAIL_ADDRESS>wrote:
Build failed
continuous-integration/travis-ci/push
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@grovesNL CI is unreliable atm. If you can force merge it, please do.

On Aug 22, 2019, at 18:41, bors[bot]<EMAIL_ADDRESS>wrote:
Build failed
continuous-integration/travis-ci/push
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Done!


Update The Swift Programming Language for SE-0386 (2 of 5)

Location
https://docs.swift.org/swift-book/documentation/the-swift-programming-language/accesscontrol#Access-Levels
Description
Update The Swift Programming Language to match the language changes implemented by SE-0386.  Five subsections in the document were identified as being impacted by the implementation of SE-0386.  This is the second impacted subsection.
Correction
Replace the first paragraph with:
Swift provides six different access levels for entities within your code. These access levels are relative to the source file in which an entity is defined, to the module that source file belongs to and to the package that the module belongs to.
Add the following as the second bullet in the subsequent list:
•	Package access enables entities to be used within any source file from their defining package, but not in any source file outside of that package. You typically use internal access when defining an app’s or a framework’s internal structure that spans multiple modules.
Append the following to the end of the next bullet:  contained within a single module

Thanks for this detailed write-up!  No need to track each change separately — I'm copying this content all into the first issue.
As a note, in the future, you're welcome to open a PR to implement these changes in source, instead of describing them in an issue.  It might actually be faster for you.  But either approach is appreciated.

Tracking all of this work under https://github.com/apple/swift-book/issues/215  (Adding the link here to make a back-reference show up on that bug.)


RE7 Demo Crashing

Hey, I'm having an issue with RE7 Demo. I extracted the files for the RE7 mod into the demo folder and when I launch the game, the game does not appear in the headset and the game crashes before the first disclaimer screen is about to disappear.
Here's my crash data:
crash_data.zip

Use the re7_tdb49.zip release when playing the demo.


Automated Greeting Workflow

I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet(using Github Bots) users who create new issues or pull requests in this repository.  The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."
Please assign this issue to me

Please assign me this issue under GSSoC'24.

Task done.


circt: 1.81.1 -> 1.83.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for circt is: Circuit IR compilers and tools
meta.homepage for circt is: https://circt.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.82.0 with grep in /nix/store/hd2zrawyw7awg1pgdd6mv65k0ykvr57k-circt-1.82.0
found 1.82.0 in filename of file in /nix/store/hd2zrawyw7awg1pgdd6mv65k0ykvr57k-circt-1.82.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

circt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hd2zrawyw7awg1pgdd6mv65k0ykvr57k-circt-1.82.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A circt https://github.com/r-ryantm/nixpkgs/archive/ea9a4d91fee9793ae133658dc668edd23da6f7b4.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ea9a4d91fee9793ae133658dc668edd23da6f7b4#circt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hd2zrawyw7awg1pgdd6mv65k0ykvr57k-circt-1.82.0
ls -la /nix/store/hd2zrawyw7awg1pgdd6mv65k0ykvr57k-circt-1.82.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

circt
circt.dev
circt.lib

Maintainer pings
cc @SharzyL @pineapplehunter for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for circt is: Circuit IR compilers and tools
meta.homepage for circt is: https://circt.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.83.0 with grep in /nix/store/50l24l2592rcwfcjm095xbf616q6cx14-circt-1.83.0
found 1.83.0 in filename of file in /nix/store/50l24l2592rcwfcjm095xbf616q6cx14-circt-1.83.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

circt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/50l24l2592rcwfcjm095xbf616q6cx14-circt-1.83.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A circt https://github.com/r-ryantm/nixpkgs/archive/e7f9526d960a65e528f41adaf9ad47fbf11208ea.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e7f9526d960a65e528f41adaf9ad47fbf11208ea#circt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/50l24l2592rcwfcjm095xbf616q6cx14-circt-1.83.0
ls -la /nix/store/50l24l2592rcwfcjm095xbf616q6cx14-circt-1.83.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

circt
circt.dev
circt.lib

Maintainer pings
cc @SharzyL @pineapplehunter for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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


1726508755056-base.js

1726508755056-base.txt

explain the issue

the bot works but stops playing music halfway through


fSelect dropdown is hidden under. I have tried changing z-index but still the same result

Old issue but for those that come across this one check this out:
https://stackoverflow.com/questions/20851452/z-index-is-canceled-by-setting-transformrotate
..for me I was animating the appearance of a sidebar containing the selects. Each select slid in which used transform/translate. This then created a new stacking context which cancelled out the z-index causing the fselects to appear under any other content.


Hi，can u shelves  this plugin on obsidian？

Sorry, I am not using Obsidian and am not familiar with it either. Closing.


solved issue #18

solved issue #18 .i have made the navigation buttons functionable.

i have solve the issue #18 . please review the pr and merge accordingly.

resolve it s


Report code coverage

Generate coverage reports for tests and androidTests

Current coverage is 50.55% (diff: 100%)

No coverage report found for master at 9d95459.

Powered by Codecov. Last update 9d95459...caf3373


Couldn't find any host available to create volume

Using general defaults for the values and updating my connection strings in the values.yml I am receiving this error:
Failed to create Volume: rpc error: code = Internal desc = Failed to get available location, err: DSM Api error. Error code:105
GRPC error: rpc error: code = Internal desc = Couldn't find any host available to create Volume

Any idea whats happening here? I saw a previous issue where updating the parameters to the StorageClass was the solution but it doesn't seem to have the same resolution for me.
https://github.com/christian-schlichtherle/synology-csi-chart/issues/1
Thanks for any help!

This error message usually means that your connection parameters are wrong. Please check your network, host name, username, PPW and so on.

@christian-schlichtherle ty for your prompt reply.
Problem was with the path I had defined in the StorageClass, as well as the user didn't have the appropriate rights for the connection. My admin can connect but my other user cannot. Still looking into which permission determines that


CEL implementation for DRCluster

The changes here are incorrect. Opened another PR: https://github.com/RamenDR/ramen/pull/1219


How to port it to new device?

I have exact partition layout for Moto Z Play. How can I make it work for it?

I have exact partition layout for Moto Z Play. How can I make it work for it?

Without the flash programmer you don't.

It's a proof of concept study. I think they explained how they did it for the said devices in the study itself.
Anyone wishing to follow will have to dig around for themselves. This includes having low level knowledge like ARM assembly language (version needed for your device) and understanding of how to extract the necessary information from the firehose files in order to be able to port the device into this template. i.e. 3 files
constants.h,
patcher.c &
shook_target.h
for your device.


Bump versions

WHAT
Bump dependency versions.
WHY
Media3 beta02 released and kotlin 1.7.0, required for Wear Compose 1.2.0 (when released)
HOW
Checklist :clipboard:

[x] Add explicit visibility modifier and explicit return types for public declarations
[x] Run spotless check
[x] Run tests
[x] Update metalava's signature text files

@shumelchyk hopefully not controversial, landing.


@swc/css exports CSS parser API

Describe the feature
@swc/css is a Node.js binding for SWC CSS features. It privides only APIs for minification.
If it provides a parser API, it would be good for Node.js tools that want to use the CSS parser.
Babel plugin or link to the feature description
N/A
Additional context
I'm personally considering the possibility of migrating the CSS parser used by Prettier from postcss to SWC.

Sending AST through N-API can be very slow, even slower than calling JS code.
SWC CSS parser supports CSS only, while Prettier can be used in Sass/SCSS/Less. What about those CSS preprocessors?


probes: replace ProbeManager with features API in cilium/ebpf

The first commit vendors the github.com/cilium/ebpf/features package.
With the second commit we replace most of the feature probes done with the current ProbeManager system with the features API in cilium/ebpf.
Fixes: #20062

/test

The first commit replaces a deprecated function in cilium/ebpf, which is needed so that updating cilium/ebpf to 9.1 won't break. We might want to cherry pick that one and split it of into a separate PR.

I think this part of the PR description no longer applies since #20584 was merged.

The second commit updates the cilium/ebpf dependency to a newer commit, so the third commit can use some of the newer Helper built-ins which were just recently added. Commit should be removed from PR once we actually release cilium/ebpf 9.1 and do a proper dependency upgrade.

Likewise, #20453 updated cilium/ebpf.

With the 3rd commit we replace most of the feature probes done with the current ProbeManager system with the features API in cilium/ebpf.

Converted this to draft, small update:
The 5.4 and 4.19 jobs seem to have failed with unable to initialize Kube proxy replacement options. Here are 2 zips for posterity:
94fee933_K8sPolicyTestExtended_Validate_toEntities_KubeAPIServer_Allows_connection_to_KubeAPIServer.zip
44b3b553_K8sDatapathConfig_Host_firewall_With_VXLAN.zip
The good news is the agent crashes early on in the startup process, and seems to occur fairly regularly, so doesn't seem so difficult to reproduce for now.
These failures highlight a shortcoming with the probing approach as proposed in this PR: we only check for features.Have...() == nil, which ignores any unexpected errors during probing (insufficient memory, permissions, ..). As part of this PR, we'll add a helper that logs a Fatal() if a probe result is not either nil or ErrNotSupported.
This way, we can start to uncover the root cause of these probe failures, as we're also seeing them on master from time to time (using bpftool).

/test

/test-1.22-5.4

/test-1.22-5.4

/test-1.22-5.4

/test-1.22-5.4
/test-1.24-net-next

/test-1.22-5.4

/test-1.22-5.4

/test-1.22-5.4

Marking this ready for review again.
The probe failures (EPERM) we were seeing should be resolved by the first commit, changing when we set the rlimit in the agent. I have been holding off on running the full test suite again before getting another round of reviews, but the 1.22-5.4 test did pass.
Open for discussion is probably to fatal on probes with inconclusive (neither nil or  ErrNotSupported) outcomes, but I do agree with Timo that keeping the fatal here could help discovering other issues and discover their root cause as inconclusive results are not expected to happen.

/test

/test-1.16-4.9

/test-1.24-net-next

/test-runtime

/test-1.16-4.9

This hit https://github.com/cilium/cilium/issues/20288 in https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-kernel-4.9/2411/testReport/Suite-k8s-1/16/K8sHubbleTest_Hubble_Observe_Test_L3_L4_Flow/, zip attached.
30cc83bc_K8sHubbleTest_Hubble_Observe_Test_L3-L4_Flow.zip

/test-1.16-4.9

Giving this some more time until 4.9.326 CI images are built, containing a backport of the bpf accounting fix to reduce the flakiness of the 4.9 tests.

/test

/test-1.16-4.9


please invite me to Eddie Hub community

Name
ISHA
Discord Username (if applicable)
Isha#0690
Additional Context
I learned about Eddie from twitter heard and read about some of his great projects. By joining this community  i can explore and learn more about open source project and do my contribution in it. Looking forward to be a part of this community...

thank you  for accepting my issue


CSS Font Loading

http://dev.w3.org/csswg/css-font-loading/
Interesting stuff, including SetClass.

Discussed in NYC; @domenic looking into it.

Discussed in SF; @torgo to follow up with @domenic and Kenji B.

I finally went back and looked through the old concerns about this. (Had to dig through my old email account in fact.) They have all since been taken care of.

Thanks, Domenic – any further info you ca point us to on that (just for closure)?

The original concern (from Ryan Sleevi) was about the initialization process for FontFace objects being underspecified and buggy in a few areas. These concerns were addressed over time in the following commits:

https://github.com/w3c/csswg-drafts/commit/88134a76d2b039f2ca99942e7e76ec83fb33392a
https://github.com/w3c/csswg-drafts/commit/b9923152182a54ccaf16330149049631af30912e
https://github.com/w3c/csswg-drafts/commit/069a1bb6aa6bda56596989c9c805e9f6e0f5ea51
https://github.com/w3c/csswg-drafts/commit/425954e5a71e19ef8de9504c869c0df71e54589e
https://github.com/w3c/csswg-drafts/commit/ba0a889ba69fe9c29de20a15eb975b67769e9151
https://github.com/w3c/csswg-drafts/commit/408a81a942e7e5aa18f461a50ed2495a3f62ced0
https://github.com/w3c/csswg-drafts/commit/9bbfc20b4a4b5e3698e1d713b1ee46b2d31c7cd1

You rock.

Alternately: I do.


BrainBot Halloween pfp

Going to pass on this mainly because a release has already been made for the Halloween name and I'd rather not make another Halloween release. Thanks anyways!


Workbench Modify html page error

Html page errors exist on Workbench Modify page.

What os/browser/tomcat/rdf4j versions are you using? What steps can I take to reproduce this?

@jamesrdf I use win 10/Microsoft edge/Tomcat 8 (I'll check it later) /RDF4J 2.2.2.
Nothing special has been done. The 'query' page is ok. But the 'update' page is like in the image.

Related to #373 ?


FIX: Ability to send email via crontab inside docker container

Loguru might help with email notifications, if the fix doesn't work: https://github.com/Delgan/loguru#exhaustive-notifier


cherry-pick(probe): initialize labels before probe start

cherry-pick #663

Codecov Report

Merging #664 (5ba7144) into v1.8.x (7c64d44) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           v1.8.x     #664      +/-   ##
==========================================
+ Coverage   45.10%   45.16%   +0.06%
==========================================
  Files          79       79
  Lines        3971     3970       -1
==========================================
+ Hits         1791     1793       +2
+ Misses       2009     2007       -2
+ Partials      171      170       -1

Impacted Files
Coverage Δ

cmd/ndm_daemonset/probe/customtagprobe.go
23.33% <ø> (-4.80%)
:arrow_down:

cmd/ndm_daemonset/controller/probe.go
100.00% <100.00%> (ø)

cmd/ndm_daemonset/probe/addhandler.go
70.91% <0.00%> (+0.98%)
:arrow_up:

Continue to review full report at Codecov.

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


Remove deprecated interceptor field from listener and service configuration

Description:
$subject
Subtask of https://github.com/ballerina-platform/ballerina-standard-library/issues/4300

Before merging the PR, we need to get these PRs merged.
https://github.com/ballerina-platform/ballerina-standard-library/issues/4570