Closed cmazakas closed 3 months ago
Antora version: an automated preview of the documentation is available at https://96.http-proto.prtest.cppalliance.org/site/index.html
GCOVR code coverage report https://96.http-proto.prtest.cppalliance.org/gcovr/index.html
LCOV code coverage report https://96.http-proto.prtest.cppalliance.org/genhtml/index.html
Coverage Diff https://96.http-proto.prtest.cppalliance.org/gcovr/coverage_diff.txt
Antora version: an automated preview of the documentation is available at https://96.http-proto.prtest.cppalliance.org/site/index.html
GCOVR code coverage report https://96.http-proto.prtest.cppalliance.org/gcovr/index.html
LCOV code coverage report https://96.http-proto.prtest.cppalliance.org/genhtml/index.html
Coverage Diff https://96.http-proto.prtest.cppalliance.org/gcovr/coverage_diff.txt
@ashtum please review
Antora version: an automated preview of the documentation is available at https://96.http-proto.prtest.cppalliance.org/site/index.html
Antora version: an automated preview of the documentation is available at https://96.http-proto.prtest.cppalliance.org/site/index.html
if its ready, merge it
Fixing the
flat_buffer
has caused a latent implementation bug to surface in the parser tests. Namely:This test will pass when it should fail with the above
in_place_overflow
error. This is caused by an underflow on unsigned integers, which results in a wrap-around andn0
winds up being the unsigned equivalent of-33
which is actually quite large in unsigned.The code most likely meant
fb_.max_size()
when it did this check and we've updated it to include an assertion for the purposes of saftey.