Subversion Repositories SmartDukaan

/*

 * Unpack selenium-remote-driver from the fat jar at startup.

 *

 * Selenium reads its JS "atoms" as classpath RESOURCES on essentially every WebDriver

 * command -- W3CHttpCommandCodec.amendParameters -> executeAtom -> Resources.toString.

 * Inside a Spring Boot fat jar that is a NESTED-jar read served by

 * org.springframework.boot.loader.jar.ZipInflaterInputStream, and on this loader

 * (Spring Boot 2.0.2, 2018) that read is the failure surface behind three separate

 * inflater corruptions seen on prod -- "invalid stored block lengths", "invalid distance

 * too far back", "invalid code lengths set" -- on a jar whose outer AND nested archives

 * both pass `unzip -t`. Intact bytes plus three different inflater errors is a reader

 * fault, not a file fault.

 *

 * requiresUnpack extracts the jar to a real file at launch, so the atom read becomes an

 * ordinary filesystem read and leaves the nested reader out of the hot path entirely.

 * This is the durable half of the 2026-09-21/22 activation outage (17,508 then 27,768

 * failures/day against a ~30-50 baseline); the other half is in

 * Oppo/RealmeImeiActivationService, which no longer spends the day's imei pool when the

 * whole chunk fails.

 *

 * NOTE this is also why a restart is an unreliable cure: it was restarted at 13:16 on

 * 09-22 and still failed for three hours, then a 16:36 restart came up clean, on the

 * SAME jar. Do not treat "restart fixed it" as a diagnosis.

 */

bootJar {

    requiresUnpack '**/selenium-remote-driver*.jar'

}