Guillaume Hetier
Guillaume Hetier
Address issues found in the release pipeline: - release triggers - build triggers - Pipeline starting on the wrong commit when two tags are created in close succession - package...
More sanitizers need to be onboarded in the GitHub CI by default and run regularly. List of sanitizers: - clang sanitizers - TSAN - See other sanitizers used by internal...
The platform layer currently contains: - basic, essential helpers like `CxPlatAlloc` - higher level abstraction like datapaths, storage This is problematic when writing unit tests for the core layer since...
We need clear, visible notification when the internal release pipeline fails at any state, balancing spurious noise and efficient warning. Sending emails to the team on packaging / publishing failure...
MsQuic multi-receive option allows the app to request that multiple receive notification can happen without waiting for previous notifications to complete a receive first. See `SetStreamMultiReceiveEnabled` to enable it. The...
- Ensure that BinSkim and APIScan are running in ADO build/release pipeline - Ensure the pipeline does fail when a violation is reported - If both the above are already...
Nuget packages from the UWP build should be published to the feed Microsoft.Native.Quic.MsQuic.UWP.OpenSSL
Test failure in [Interop (Release, linux, ubuntu-24.04, x64, quictls, -Test)](https://github.com/microsoft/msquic/actions/runs/18617835070/job/53085067121?pr=5529#logs) It looks like a memory corruption in the epoll datapath. See https://github.com/microsoft/msquic/issues/5529#issuecomment-3422795153_
The PATH_CHALLENGE failure is dealt with in `QuicLossDetectionRetransmitFrames`, when detecting that no packet containing a PATH_CHALLENGE has been acknowledged for longer than a validation timeout. When this is the case,...