rootvector2 opened a new pull request, #427:
URL: https://github.com/apache/commons-beanutils/pull/427

   `ArrayConverter.parseElements` sets up a `StreamTokenizer` but never 
disables its default comment character `/`, so a list element containing a 
slash comments out the rest of the input and the following elements are 
silently dropped: `a/b,c` parses to `["a"]` and a leading slash such as 
`/etc/passwd,/tmp/x` parses to an empty array. Every other non-allowed 
character splits and keeps both sides (see `testUnderscore_BEANUTILS_302`, 
where `first_value,second_value` yields four elements), so `/` is the outlier. 
`st.ordinaryChar('/')` makes it split like any other separator; adding `/` to 
`allowedChars` still keeps it inside a token. Found while auditing the 
delimited-list parser against the `_` behavior that test pins.
   
   - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
   - [ ] Read the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) if you use 
Artificial Intelligence (AI).
   - [ ] I used AI to create any part of, or all of, this pull request. Which 
AI tool was used to create this pull request, and to what extent did it 
contribute?
   - [x] Run a successful build using the default 
[Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command 
line by itself.
   - [x] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied. This may not always be possible, 
but it is a best practice.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body. Note that a maintainer may squash commits during the merge process.
   


-- 
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