Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically adding ccs based on suspected regression changelists:

Use uint64_t for varint. by quiche-dev@google.com - https://quiche.googlesource.com/quiche/+/15fb5630803634b1988b77d876212fad71f7a2c3

Avoid truncation error on 32 bit platforms. by bnc@google.com - https://quiche.googlesource.com/quiche/+/94696df580816fb56eac22e4a3ba0558e7e30f15

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Bence and Victory, can any of you take a look? There are not many changes in the regression range. 

ClusterFuzz has detected this issue as fixed in range 623697:623714.

Detailed report: https://clusterfuzz.com/testcase?key=6030938634715136

Fuzzer: libFuzzer_net_hpack_decoder_fuzzer
Fuzz target binary: net_hpack_decoder_fuzzer
Job Type: x86_libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  state_ == State::COMPLETE in hpack_decoder_string_buffer.cc
  http2::HpackDecoderStringBuffer::str
  http2::ExtractHpackString
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan_debug&range=619404:619407
Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan_debug&range=623697:623714

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6030938634715136

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6030938634715136 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.