diff options
| author | Jacob Lalonde <jalalonde@fb.com> | 2025-05-19 15:19:55 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-05-19 15:19:55 -0700 |
| commit | f27cfeae6a544775803a50b3ed4c87e9193889a2 (patch) | |
| tree | 313284f539b79f18bd7e956c442cc1f04b8640b8 /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp | |
| parent | 2dd6a8c35a79710273bb98da8729ec6dea251998 (diff) | |
| download | llvm-f27cfeae6a544775803a50b3ed4c87e9193889a2.zip llvm-f27cfeae6a544775803a50b3ed4c87e9193889a2.tar.gz llvm-f27cfeae6a544775803a50b3ed4c87e9193889a2.tar.bz2 | |
[LLDB][Progress-On-Dap] Have indeterminate progress actually send events. (#140162)
Recently, I got a report how a user 'hung', and come to find out it's
actually because DAP is checking percentage, and on non-deterministic
events, we will effectively never send a progress event to DAP. Here we
short circuit and don't view percentages for DAP messages and solely
depend on the DAP 250ms throttle, which is probably still too
aggressive, but better than no updates.
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions