ERROR: A script with same hash (...) already exists! (RESOLVED)
Running into some strange issues today...
I've run the same command hundreds of times, but all the sudden i'm getting back an error when trying to sync push my latest changes. 15mm ago i didn't get the error. It's possible i broke something, but again, i'm not sure how or if in fact it is on my side at all. Your advice and support to debug is greatly appreciated.
$> wmill script generate-metadata --yes
... OK
$> wmill sync push --yes
...
Applying changes to files ...
Creating script with a parent f/configs/status
Creating script with a parent f/lib/airtable
Creating script with a parent f/lib/common
Creating script with a parent f/lib/tally
Server failed. Bad Request: Bad request: A script with same hash (hence same path, description, summary, content) already exists!
error: Uncaught (in promise) ApiError: Bad Request
at catchErrorCodes (file:///Users/cward/Library/Caches/deno/npm/registry.npmjs.org/windmill-client/1.319.1/dist/core/request.js:224:15)
at file:///Users/cward/Library/Caches/deno/npm/registry.npmjs.org/windmill-client/1.319.1/dist/core/request.js:269:45
at Generator.next (<anonymous>)
at fulfilled (file:///Users/cward/Library/Caches/deno/npm/registry.npmjs.org/windmill-client/1.319.1/dist/core/request.js:5:58)
at eventLoopTick (ext:core/01_core.js:168:7)
3 Replies
funny enough, it was an older file which the project doesn't depend on anymore ... i removed it and problem solved. But still, strange that it popped up all the sudden. Anyway.... moving on. Thanks.
we have the same problem lately. solution is always to delete the file, even if it's still used. the next sync will recreate it
but it's not nice that it happens out of the blue because it breaks our CI/CD
apologies, I think I know the issue, it's because of the diff created by those now obsolete default false fields