Closed jsmassa closed 1 year ago
Unfortunately kaocha's node test runner fails for this project with an error after all tests have been executed. Until the problem has been fixed I am using the olical cljs test runner here, which also requires only a setup in the deps.edn and no further config or runner files.
We can also try simply updating the karma packages. Vulnerabilities still shown on my system might be just a local problem.
Does not work right now because of #96
The problem is fixed now with support for salt as in the clojure version still missing as stated in this comment.
Just uncomment the cljstest from main and it should be working
You can either merge now or wait for my cljs fix in the next days.
A couple more days won't make much of a difference I guess.
This now implements the corresponding salt concatenation in ClojureScript, but I am certain that the cljs tests are not properly executed. Can you check that you can really execute the tests and then we need to figure out why the cljstest here passed earlier while the unit test correctly failed in https://circleci.com/gh/replikativ/konserve/788 ? On my machine I get macro import compile errors (which also might be my setup) and cannot run the tests or start a REPL atm.
Is there still a problem? Like on the server, all of the tests are passing on my system.
I get a few warnings, but cleanups of this repo will be the goal of PR #88.
Fixed the lz4 warning though as this is a seems to be a difference in cljs
What about the line here? Isn't that supposed to be the unsupported compressor as well in case of an exception in the clojure code?
AES is now fixed in cljs and has the same cold storage format as in Clojure (i.e. you can read the same store from Clojure and ClojureScript), thanks to the help of @pkpkpk :tada: . A problem was that the cljs compliance test was not run asynchronously and I think this is why it just passed before it failed.
What about the line here? Isn't that supposed to be the unsupported compressor as well in case of an exception in the clojure code?
@jsmassa I think this try-catch can be removed (it is redundant), it accidentally slipped in there while I was getting the native build to work.
We are already using kaocha for our clojure tests, so it simplifies things if we are moving to kaocha for clojurescript as well.
Fixes #89.