kpumuk opened a new pull request, #3700:
URL: https://github.com/apache/thrift/pull/3700

   <!-- Explain the changes in the pull request below: -->
     
   Ruby fuzz targets currently suppress integer-conversion errors by matching 
Ruby exception text. That hides native protocol-decoding problems and is 
sensitive to message formatting changes between Ruby versions.
   
   This change removes the conversion-error allowlist so the harness ignores 
only malformed-protocol and truncated-input exceptions. Native and pure Ruby 
struct decoding now accept Compact Protocol container counts across the full 
unsigned 32-bit range and report larger counts as 
`ProtocolException::SIZE_LIMIT`.
   
   The native implementation keeps ordinary container-size validation on a C 
Fixnum fast path. Focused Binary, accelerated Binary, and Compact 
container-read benchmarks remained unchanged from master.
   
   <!-- We recommend you review the checklist/tips before submitting a pull 
request. -->
   
   - [x] Did you create an [Apache 
Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) ticket?  
([THRIFT-6136](https://issues.apache.org/jira/browse/THRIFT-6136))
   - [x] If a ticket exists: Does your pull request title follow the pattern 
"THRIFT-NNNN: describe my issue"?
   - [x] Did you squash your changes to a single commit?  (not required, but 
preferred)
   - [x] Did you do your best to avoid breaking changes?  If one was needed, 
did you label the Jira ticket with "Breaking-Change"?
   - [ ] If your change does not involve any code, include `[skip ci]` anywhere 
in the commit message to free up build resources.
   
   <!--
     The Contributing Guide at:
     https://github.com/apache/thrift/blob/master/CONTRIBUTING.md
     has more details and tips for committing properly.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to