Eduardo Salinas

Maybe consider using https://boringssl.googlesource.com/boringssl

https://github.com/VowpalWabbit/vowpal_wabbit/blob/c9cb804a74c94df4a00756c78f6e204526fcb7a9/vowpalwabbit/core/src/parser.cc#L311

Yes, it is not entirely clear. It is referring to the dirs on that same location as that text file in the repository, which makes it extra confusing on that...

We also have these autogen docs: https://vowpalwabbit.org/docs/ https://vowpalwabbit.org/docs/vowpal_wabbit/python/latest/

This could be achievable with the following bits: - Avoiding the std:cout https://github.com/VowpalWabbit/vowpal_wabbit/blob/4ccc76046256d3c8e7bd46900139c9d472a28967/vowpalwabbit/gd.cc#L305 - instantiating vw with enable_logging=True https://github.com/VowpalWabbit/vowpal_wabbit/blob/4ccc76046256d3c8e7bd46900139c9d472a28967/python/tests/test_cb.py#L41 - and then calling `output = vw.get_log()`

arm support is being tracked here https://github.com/VowpalWabbit/vowpal_wabbit/issues/2284

This is blocking this fix https://github.com/VowpalWabbit/vowpal_wabbit/pull/4023

> Just wanted to ask your opinion on doing things like that. The goal is to write tests that are asserting specific invariants vs checking stdout that we have now...

similar to flatbuffer automated tests https://github.com/VowpalWabbit/vowpal_wabbit/blob/2d394ce7bdb02cc3f5bb08c0031565e0e4ea48dc/test/run_tests.py#L19

This might be relevant for https://github.com/VowpalWabbit/vowpal_wabbit/pull/3144