royitaqi
12fa4b17dc
[lldb] Make sure that a Progress "completed" update is always reported at destruction ( #102097 )
...
Make all `Progress` destructions to cause `progressEnd` events,
regardless of the value of `m_completed` before the destruction.
Currently, a `Progress` instance with `m_completed != 0 && m_complete !=
m_total` will cause a `progressUpdate` event (not `progressEnd`) at
destruction and. This contradicts with the classdoc: "a progress completed
update is reported even if the user doesn't explicitly cause one to be sent."
2024-08-07 07:58:34 -07:00
..
2024-05-08 15:07:14 -07:00
2024-05-30 10:38:21 -07:00
2024-05-30 10:38:21 -07:00
2024-05-31 01:29:00 +02:00
2023-08-15 16:03:28 -07:00
2024-02-22 21:48:49 -08:00
2023-09-01 21:32:24 -07:00
2024-05-20 15:51:42 -07:00
2024-05-03 09:25:38 -07:00
2024-04-18 15:35:56 -07:00
2024-03-11 10:21:07 -07:00
2024-07-01 10:45:56 +01:00
2024-06-20 10:32:06 -07:00
2024-07-17 10:05:55 -07:00
2023-08-09 17:17:18 -07:00
2024-07-09 13:35:34 -07:00
2023-09-13 22:27:05 -07:00
2024-03-21 08:40:08 -07:00
2024-05-31 14:04:40 -07:00
2024-08-01 17:43:25 -07:00
2024-02-08 12:39:04 -08:00
2024-08-05 10:17:25 -07:00
2024-08-07 07:58:34 -07:00
2023-12-16 14:39:37 -08:00
2023-11-09 13:35:35 -08:00
2024-07-11 12:58:24 -07:00
2023-07-09 14:09:21 +01:00
2024-03-21 08:40:08 -07:00
2024-04-24 12:13:18 -07:00
2023-09-22 13:33:07 -04:00
2023-10-17 15:40:51 -07:00
2024-06-20 10:32:06 -07:00
2024-03-08 16:03:04 -08:00
2024-03-08 16:03:04 -08:00
2024-06-07 08:39:10 +02:00
2024-06-07 08:39:10 +02:00
2024-06-07 08:39:10 +02:00
2024-06-07 08:39:10 +02:00
2024-03-08 16:03:04 -08:00
2024-03-08 16:03:04 -08:00
2024-06-07 08:39:10 +02:00
2024-03-08 16:03:04 -08:00
2024-06-05 10:57:46 -07:00
2024-06-07 08:39:10 +02:00