My use case, today: I want to quickly explore some JSON data on the command line.

The nREPL story is good, the console REPL is similarly basic as Clojure. Maybe one day we should have something better

So I should just run bb --nrepl-server and then cider-connect? 🙂

Yes

👍

You can also cider jack in with bb

Perhaps it checks the existence of a bb.edn file

Do you use cider inspector? The connected REPL looks fine except I'm getting "Inspector error" for the results I'm trying to inspect.

Hmm that’s one thing that is Cider specific and not yet in bb. You can use portal with bb though, that’s a one liner on the command line and then you can browse your data too

You could make a bash alias if it’s too long to remember. I can look up the invocation when I’m at the kbd

@U06BE1L6T Something like this:

echo '[1 2 3]' | bb -Sdeps '{:deps {djblue/portal {:mvn/version "0.34.2"}}}' -e "(require '[portal.api :as p]) (def p (p/open)) (add-tap #'p/submit) (tap> *input*) @(promise)"

https://twitter.com/borkdude/status/1597505695800516609

I see, thanks!

Seems super handy! But (on 1.0.166) I just get:

----- Error --------------------------------------------------------------------
Type:     java.lang.Exception
Message:  Could not find namespace: portal.api.
Location: <expr>:1:1

----- Context ------------------------------------------------------------------
1: (require '[portal.api :as p]) (def p (p/open)) 
   ^--- Could not find namespace: portal.api.
2:         (add-tap #'p/submit) (tap> *input*) @(promise)

----- Stack trace --------------------------------------------------------------
user - <expr>:1:1

let me try to erase that dep so I start from scratch...

borkdude@m1 ~/dev/joyride (master) $ rm -rf ~/.m2/repository/djblue
borkdude@m1 ~/dev/joyride (master) $ cat deps.edn |
  bb -Sdeps '{:deps {djblue/portal {:mvn/version "0.34.2"}}}' \
  -e "(require '[portal.api :as p]) (def p (p/open))
        (add-tap #'p/submit) (tap> *input*) @(promise)"
Downloading: djblue/portal/0.34.2/portal-0.34.2.pom from clojars
Downloading: djblue/portal/0.34.2/portal-0.34.2.jar from clojars

Thanks! Still some environmental difference?! :thinking_face:

$ rm -rf ~/.m2/repository/djblue
$ cat deps.edn |
  bb -Sdeps '{:deps {djblue/portal {:mvn/version "0.34.2"}}}' \
  -e "(require '[portal.api :as p]) (def p (p/open))
        (add-tap #'p/submit) (tap> *input*) @(promise)"
----- Error --------------------------------------------------------------------
Type:     java.lang.Exception
Message:  Could not find namespace: portal.api.
Location: <expr>:1:1

----- Context ------------------------------------------------------------------
1: (require '[portal.api :as p]) (def p (p/open))
   ^--- Could not find namespace: portal.api.
2:         (add-tap #'p/submit) (tap> *input*) @(promise)

----- Stack trace --------------------------------------------------------------
user - <expr>:1:1

what os is this?

Ubuntu

I will create a reminder for myself to figure this out on ubuntu. Not sure why this happens

Thank you! Have a good day!

you can also try: (babashka.deps/add-deps '{:deps {...}})

inside the -e expression to see if that helps

it could be a caching thing. can you also try: rm -rf ~/.clojure/.cpcache ?

Yes, I thought of add-deps too. It wil probably also work. But I was just wondering why the code of your tweet wouldn't work right away. Removing that cache doesn't help unfortunately.

I have no clue why it doesn't work :(

Thanks anyway! Nothing urgent or that I can't work around.

On WSL2 + ubuntu it "just works" for me, so I'm afraid I can't repro it. If you can repro it at some point, let me know.

Does it help if you add this dep?

org.babashka/spec.alpha {:git/url ""
                         :git/sha "1a841c4cc1d4f6dab7505a98ed2d532dd9d56b78"}

(last attempt)

Yes! That works!

aha!

maybe bb should include that lib by default

Totally beyond my understanding why, but I'm sure you know exactly what's going on. 🙂

I did see a warning about clojure.spec, but it didn't affect the behavior of portal for me

Oh, oops, I'm sorry. I was now running it from file with the -cp option (and clj -Spath ...) still in it (which already worked before). Removing that, it still does not work. So this is to let you know that spec.alpha was not the issue after all. Thanks anyway! I will switch my attention to more urgent stuff now...

ok, then I also don't know. laterzzz :)

Ouch, found that I had a, long forgotten, explicit BABASHKA_CLASSPATH set in my .bashrc. Without that, the original snippet works fine (obviously). Sorry for wasting your time.

aaah ok :)

no problem

let's continue in a thread

could this be the reason?

oh the other site doesn't load for me either

perhaps it's best to test with plain html on disk to rule out any networking stuff

I'll be afk now 💤 but I'll check back in tomorrow

Ah, that’s smart. I’ll test by slurping instead of curling. Thank you, have a good night!

A small update: Had the same issue with the files on disk.

(spit "working.html" (:body (curl/get "")))
(spit "broken.html" (:body (curl/get "")))
(convert-to (slurp "broken.html") :hickory) ;=> "\n"
(convert-to (slurp "working.html") :hickory) ;=> big ol' hickory map 

Ah, I think I figured it out! There was a /newline at the end of the broken.html file (and in that url). It seems like this was causing convert-to to act unexpectedly. You can see the behaviour with some other urls, too. will not convert to hickory, will. If I change the fn to:

(-> url 
    curl/get :body 
    clojure.string/trim-newline 
    (convert-to :hickory))

Not sure if this is a bug or I need to adjust my understanding of the fn.

Judging from the note in <https://github.com/retrogradeorbit/bootleg#data-conversion>, this appears to be sort of a "lossy" conversion. It seems like the HTML gets 'closed', and then the newline starts the next 'form'. This can be demonstrated by converting to a hickory-seq:

(utils/convert-to "<p>1</p>\n" :hickory)
;; => "\n"

(utils/convert-to "<p>1</p>\n" :hickory-seq)
;; => ({:type :element, :attrs nil, :tag :p, :content ["1"]} "\n")

Ah, i had not seen that note. Thanks for pointing it out! This makes more sense, and the example in the doc is clear.