[all-commits] [llvm/llvm-project] a1b14d: [lldb] Remove progress report coalescing (#130329)

[Jonas Devlieghere via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: a1b14dbc4740fe49dfb2af44907a195597474556
      https://github.com/llvm/llvm-project/commit/a1b14dbc4740fe49dfb2af44907a195597474556
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2025-03-08 (Sat, 08 Mar 2025)

  Changed paths:
    M lldb/include/lldb/Core/Progress.h
    R lldb/include/lldb/Host/Alarm.h
    M lldb/include/lldb/lldb-enumerations.h
    M lldb/source/API/SystemInitializerFull.cpp
    M lldb/source/Core/Debugger.cpp
    M lldb/source/Core/Progress.cpp
    M lldb/source/Host/CMakeLists.txt
    R lldb/source/Host/common/Alarm.cpp
    M lldb/test/API/python_api/sbprogress/TestSBProgress.py
    M lldb/unittests/Callback/TestBreakpointSetCallback.cpp
    M lldb/unittests/Core/ProgressReportTest.cpp
    R lldb/unittests/Host/AlarmTest.cpp
    M lldb/unittests/Host/CMakeLists.txt

  Log Message:
  -----------
  [lldb] Remove progress report coalescing (#130329)

Remove support for coalescing progress reports in LLDB. This
functionality was motivated by Xcode, which wanted to listen for less
frequent, aggregated progress events at the cost of losing some detail.
See the original RFC [1] for more details. Since then, they've
reevaluated this trade-off and opted to listen for the regular, full
fidelity progress events and do any post processing on their end.

rdar://146425487



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications