<!-- This is an auto-generated comment: summarize by coderabbit.ai -->
<!-- This is an auto-generated comment: review in progress by coderabbit.ai -->
> [!NOTE]
> Currently processing new changes ...
std::upper_bound assumes the range is sorted, right? What would happen if the log events aren't in ascending timestamp order? It's technically not impossible and we have seen log files where that's...
```suggestion
* Finds the log event, L, where if we assume:
*
* - the collection of log events is sorted in ascending timestamp order;
* - and we insert a marker log event, ...
std::upper_bound assumes the range is sorted, right? What would happen if the log events aren't in ascending timestamp order? It's technically not impossible and we have seen log files where that's...
How about `find_nearest_log_event_by_timestamp`? Similar to Marco's original suggestion. Any ambiguity about the name should be resolved by the docstring.
_:warning: Potential issue_
**Fix the URL format in FetchContent_Declare.**
The URL format is incorrect. The variable name should be properly enclosed in curly braces, and the path separator shou...
> > [@kirkrodrigues](https://github.com/kirkrodrigues) / [@davemarco](https://github.com/davemarco)
> > Any objection if we [`npm unpublish`](https://docs.npmjs.com/cli/v9/commands/npm-unpublish) 0...