Yicong-Huang opened a new issue, #5991:
URL: https://github.com/apache/texera/issues/5991
### What happened?
When a prior version's dist zip is left in `target/universal/` (e.g.
`config-service-1.2.0-incubating.zip` sitting next to a fresh
`config-service-1.3.0-incubating-SNAPSHOT.zip`), `bin/local-dev.sh auto` / `up`
silently skips every JVM service:
```
⚠ config-service: config-service/target/universal/config-service-*.zip not
produced — skipping
...
✓ auto bounce done: 0 rebuilt, 6 bounced
```
Stamps don't refresh, dirty indicator never clears, and services that were
running get stopped without being restarted (unzip pass kills them, then never
produces a launcher).
### How to reproduce?
1. `./bin/local-dev.sh up` once on a release branch (writes
`<svc>-1.2.0-incubating.zip` under each `target/universal/`).
2. Switch to main, `./bin/local-dev.sh auto`. sbt produces
`<svc>-1.3.0-incubating-SNAPSHOT.zip`; the old zip stays.
3. Every JVM service reports `<glob> not produced — skipping`.
### Root cause
Both unzip call sites use `unzip -oq ${zip_glob}` with the glob unquoted
(bin/local-dev.sh:1718, :2126). With two matching zips, the shell expands to
two filenames; unzip interprets the 2nd as a member to extract from the 1st
archive (`unzip [file.zip] [members...]`), finds no such member, returns 11.
```
$ unzip -oq config-service/target/universal/config-service-*.zip
caution: filename not matched: ...-1.3.0-incubating-SNAPSHOT.zip
$ echo $?
11
```
Fix: pick the newest matching zip (`ls -t <glob> | head -1`) and feed unzip
a single file.
### Version/Branch
main (1.3.0-incubating-SNAPSHOT), commit 0e0ec11ba.
--
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]
