Telegram GitHub Commits - обновления репозиториев

telegramdesktop/tdesktop/nightly • 6d51231 • 2 files, +23/-15 Switched nightly Windows CI with optimized binaries without arm64. #tdesktop

telegramdesktop/tdesktop/nightly • 651f9ba • 3 files, +23/-23 Switched nightly Windows CI with optimized binaries without arm64. #tdesktop

UnigramDev/Unigram/develop • 8ab18d3 • 2 files, +90/-30 Keep the originating description when an unhandled error is a bare E_FAIL (#3340) * Keep the originating description when an unhandled error is a bare E_FAIL A large share of unhandled errors reach OnUnhandledExceptionDetected as an E_FAIL with no message and a stack that only shows Propagate() rethrowing it. GetStowedException already tries to recover the real context, but it returns null unless every step succeeds, so those reports carry nothing. Read the description out of IRestrictedErrorInfo before giving up, and return what was recovered even when the stowed frames are unavailable. The call was already written out in a comment and left unused on the assumption that the propagated managed exception would carry the details - which is exactly what fails here. WatchDog no longer overwrites the recovered string with the empty one from the propagated exception. * Read the rest of the stowed exception record GetStowedException2 required ExceptionForm 1 and returned null otherwise, so three fields the record always carries went unused: - ResultCode, the HRESULT the error was stowed with, before propagation flattened it to E_FAIL. This is the field that actually distinguishes one failure from another. - ThreadId, the thread it originated on, which is not necessarily the one whose stack ends up in the report. - ErrorText, which form 2 carries instead of a stack, and which was discarded along with the whole record. It also returned null when no frame resolved a module base, dropping the above and the nested record with them. Now a FatalError is returned either way. Co-Authored-By: Claude Opus 5 (1M context) #unigram