apache / apache/maven-resolver
Catching Throwable in non-framework code in PutTaskRequestContent
- Dominant language
- Java
- Stars
- 152
- Forks
- 160
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 49
Description
**Affected version:** HEAD
**File:** `maven-resolver-transport-jetty/src/main/java/org/eclipse/aether/transport/jetty/PutTaskRequestContent.java:246, 298`
```java
} catch (Throwable t) {
lockedSetTerminal(Content.Chunk.from(t, true));
}
```
Catches `OutOfMemoryError`, `StackOverflowError`, `InternalError`, etc. These should propagate. Wrapping them as terminal chunks converts fatal JVM errors into regular failure conditions, making them invisible to diagnostics.
Originally reported in #1944.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in maven-resolver-transport-jetty/src/main/java/org/eclipse/aether/transport/jetty/PutTaskRequestContent.java at lines 246 and 298, and read the surrounding terminal-error handling. Verify the behavior for fatal JVM errors, then run the relevant transport tests; done means those errors propagate instead of being converted into terminal chunks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100