-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Babashka support #21
Comments
The |
Was trying to use it in bb today, and I don't think it works anymore? This is what I see:
I have a longer stack trace from trying to use it in a script
|
@filipesilva We could add this var here: https://github.com/babashka/babashka/blob/master/src/babashka/impl/clojure/instant.clj I'll check and see if there's other stuff I'll run into |
I checked and this var is in So it might just be a matter of upgrading fipp. |
Can confirm that forcing a recent version of fipp works:
Updating the dep in hashp actually means updating it in https://github.com/greglook/puget though, so I expect this to be a bit more involved. |
Actually it's enough to just update Puget version. It uses a fipp dep that includes your fix. |
Fix weavejester#21 (comment) This does not fix weavejester#21 proper though, it just allows it to run in Babashka.
I'm currently working on better reader tag support in babashka. In the next release tags in
data_readers.clj(c)
will be automatically picked up, whereas before you had to set them manually by manipulating*data-readers*
.I tested that new feature using this library: https://twitter.com/borkdude/status/1621594481605615618
The output for babashka in this lib currently isn't great yet (it prints an implementation namespace of bb), but I think we could make it just output the namespace and line info:
Requesting a stacktrace at the point of execution isn't well supported in SCI / bb yet (this may come in the future, but that's going to take a while), but there's other ways of getting the above simplified output.
If there's any interest, I can look into improving this output.
The text was updated successfully, but these errors were encountered: