spring-projects / spring-projects/spring-framework
Determine why transferTo tests fail for Undertow
Open
Nobody has claimed this yet.
in: web
type: task
- Dominant language
- Java
- Stars
- 60.2k
- Forks
- 38.8k
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 27
Description
With the introduction of the DefaultMultipartParser, two tests started failing when running against Undertow:
org.springframework.web.reactive.function.MultipartIntegrationTests#transferToandorg.springframework.web.reactive.result.method.annotation.MultipartIntegrationTests#transferTo.
As temporary workaround the tests were disabled for 5.3 M1, but this needs to be resolved by M2.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the two named MultipartIntegrationTests#transferTo cases and the DefaultMultipartParser change that preceded the failures. Run both tests against Undertow, inspect the temporary disabled-test workaround, and compare the parser behavior with the expected transferTo handling. Done means both tests pass on Undertow without being disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100