I'm having a strange issue with file permissions or so for a shadow-cljs build I'm doing of this project: https://gitlab.com/hyperfiddle/electric3-starter-app
The cljs-runtime JS files get built just fine, but the main.js bundle seems to be corrupted. It can not be opened by the web server, and I can also not cat it. It does have a size on the disk.
https://clojurians.slack.com/archives/C7Q9GSHFV/p1747778392576229 I've described here more detail.
I think* this is the command that builds it: https://gitlab.com/hyperfiddle/electric3-starter-app/-/blob/main/src-dev/dev.cljc?ref_type=heads#L24
shadow-cljs writes all files in pretty much the exact same way, so dunno why any particular file may fail on its end
could be the OS preventing the write because it detects something it thinks its malware or so
hmm, perhaps yes?
or it just gets too large? how large is the cljs-runtime folder?
but that makes no sense .. at most a couple mb should be fine
maybe disk is just full? 😛
15M resources/public/electric_starter_app/js/cljs-runtime
yeah thats nothing
300GB free
macos has all sorts of security nonsense. maybe you just clicked not allow somewhere 😛
hmm okay, I'll try to research in that direction.
odd that only main.js has this issue and the cljs-runtime files open just fine
I'm not touching this electric setup, too much going on I don't understand
Yeah it's a bit exotic, anyways thanks as always @thheller 🙏
config wise it looks fine except stuff like :build-hooks [(hyperfiddle.electric.shadow-cljs.hooks3/reload-clj)] where as always I don't understand why this is a hook 😛
but dunno why that would interfere with writing the module file
Hmm yes, well it could indeed be some kind of macos protection, but the commands my finest LLM's spit out wrt checking these assumptions all come back negative so I don't know!
just try it in a different folder I guess?
avoid any of the default macos dirs like Downloads Documents etc. they are all sort of special
I've also tried 3 different folders already 😅
but whereever you run it should probably just ask for permission, so dunno why it wouldn't
I gave claude sonnet a chance to come up with theories, interestingly... it found that grep can access the file:
Claude no longer helps me because it figures "works as intended" wrt licensing. Hahah.
Thanks for having a look anyway, I'll talk to the electric guys.