James Lamb

@shiyu1994 the `valgrind` test is now failing for what looks like a real reason, not a timeout. ```text ==4762== 352 bytes in 1 blocks are possibly lost in loss record...

oh wow @shiyu1994 you are right! Very nice attention to detail!! This looks like EXACTLY that same issue, even the same stack trace. I guess the test is failing because...

🎉 glad `valgrind` is passing now! whenever @guolinke is able to review and approve this, let's merge it.

I wanted to check that this fixed the warning from #5400, but unfortunately the build logs are already gone from Azure. So I was going to merge `master` into this...

sure, fine with me

I like your approach @jmoralez ! I'd support special handling of verbosity in `ParameterAlias::KeyAliasTransform()` to ensure that all log messages can be controlled by `verbose`.

While working on #5169, I ran into this issue and have been doing some investigation. I think I've identified a fully reproducible example (using a container) and a strategy for...

Ok, so! I've been able to collect my thoughts on this. ### Reproducible Example Given the following Dockerfile, pinned to the `ubuntu:latest` (Ubuntu 22.04) image as of two weeks aago....

@david-cortes more details on "letting the linker do the job" and "using the linker from python's configured compiler" (like a link to an example or relevant documentation) would be greatly...

Thanks for that information. I'm not familiar with that pattern for Python projects, will look around for some examples and documentation on it. As discussed in #5061 , I think...