cljs-dev

dnolen 2023-04-06T14:08:16.624209Z

@borkdude https://github.com/clojure/clojurescript/pull/203

🙌 1
dnolen 2023-04-10T12:29:12.865139Z

trying it again

dnolen 2023-04-10T12:55:24.468149Z

applied

borkdude 2023-04-10T14:36:04.592279Z

thanks!

borkdude 2023-04-07T11:46:58.773459Z

FWIW the tests run fine locally

clojure -M:compiler.test:compiler.test.run
Ran 213 tests containing 920 assertions.
0 failures, 0 errors.

dnolen 2023-04-07T13:30:04.673189Z

very odd

borkdude 2023-04-07T18:33:06.002389Z

I think it's just a network hiccup, given:

npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

borkdude 2023-04-07T18:33:20.531109Z

Maybe re-trigger it a few more times?

borkdude 2023-04-11T12:37:58.211619Z

@dnolen When is CLJS due for another release? Some people will run into the above issue with vanilla CLJS (but not with shadow-cljs): https://github.com/metosin/malli/pull/888#issuecomment-1503249983

borkdude 2023-04-06T15:09:10.384179Z

Seems one CI step had a network hiccup

dnolen 2023-04-06T17:50:43.167779Z

hrm wasn’t fixed by re-running, I wonder if something is up w/ a dep