alexandrump/amarr
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Use patched jamule 1.0.3-thax1 (fixes intermittent 'Invalid opcode' errors)

Browse Source 
jamule's AmuleConnection created a new BufferedInputStream on every
request over the same persistent socket. Recreating the wrapper
discards whatever it read ahead into its own buffer past the current
packet boundary -- those bytes are gone from the raw stream, never
reaching the parser, corrupting framing for the next packet on that
connection. This showed up as intermittent
'jamule.exception.ServerException: Invalid opcode (wrong protocol
version?)' failures, unpredictably dropping some Torznab searches.

Patched jamule keeps one BufferedInputStream per connection (recreated
only alongside the socket on reconnect), published locally as
com.vexdev:jamule:1.0.3-thax1.
This commit is contained in:
alexandrump
2026-09-08 01:34:42 +02:00
parent 6907657520
commit 0811776273
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
settings.gradle.kts
+1 -1
View File
@@ -30,7 +30,7 @@ dependencyResolutionManagement {
library("ktor-client-cio", "io.ktor", "ktor-client-cio").versionRef("ktor")
library("ktor-client-logging", "io.ktor", "ktor-client-logging").versionRef("ktor")
library("ktor-client-mock", "io.ktor", "ktor-client-mock").versionRef("ktor")
library("jamule", "com.vexdev", "jamule").version("1.0.3")
library("jamule", "com.vexdev", "jamule").version("1.0.3-thax1")
library("guava", "com.google.guava", "guava").version("32.1.3-jre")
library("kotest-runner-junit5", "io.kotest", "kotest-runner-junit5").versionRef("kotest")
library("kotest-assertions-core", "io.kotest", "kotest-assertions-core").versionRef("kotest")