-
Notifications
You must be signed in to change notification settings - Fork 0
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
Error message running app #2
Comments
Hi @kerim. When you run this command
Having the file ending in |
find: .nbb/.cache/b34aecd91133fb66d9a99efeb9e3073b9e151750/nbb-deps/logseq: No such file or directory |
I ran the clone command after the last update. I don't remember the version number. Since it isn't loaded via brew I'm not sure how to check the version? In the announcement you said it was Release 0.4.0. |
Hmm. What does
Nice. It's a recent version so no need |
"no matches found: .nbb/.cache/*/nbb-deps/logseq" |
Sorry but I forgot to document you also need to have clojure installed. With that installed, could you give |
OK, installed, but still getting errors:
It finds nbb now:
But this is still not working:
|
Ah. That's the culprit. |
Doesn't seem to help. Still getting errors.
|
Since you're still seeing `node_modules/bb-cli` in that stacktrace, you
haven't uninstalled bb-cli. I don't know how you installed it but I'm
guessing with npm or brew. You'll need to uninstall it, start a new shell
and then try `bb --config ...` to confirm you have the right `bb` provided
by babashka
…On Tue, 18 Apr 2023 at 20:50, P. Kerim Friedman ***@***.***> wrote:
Doesn't seem to help. Still getting errors.
rm -rf .nbb/ && node graph_validator.mjs
Downloading dependencies...
Extracting dependencies...
Done.
***@***.***/nbb-logseq/lib/nbb_core.js:2238
Zr,new $APP.E(null,new $APP.E(null,$APP.xl,new $APP.E(null,z,null,1,null),2,null),new $APP.E(null,Xr,new $APP.E(null,new $APP.E(null,$APP.xl,new $APP.E(null,F,null,1,null),2,null),null,1,null),2,null),3,null),4,null),5,null),6,null)):null}finally{$APP.gq()}}).then(function(){var S=$APP.y(a);return Ju.g?Ju.g(S,b):Ju.call(null,S,b)}):Promise.reject(Error(["Could not find namespace: ",$APP.p.h(r)].join("")))}return Promise.resolve($APP.U.h(b))};
^
Error: Could not find namespace: logseq.graph-parser.cli
at Ju ***@***.***/nbb-logseq/lib/nbb_core.js:2238:350)
at ***@***.***/nbb-logseq/lib/nbb_core.js:647:207
at async file:///Users/{home}/graph-validator/graph_validator.mjs:9:18
Node.js v19.9.0
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXFVC52CCLY3FE3HA4W3SBLXB4ZGVANCNFSM6AAAAAAW25RKRI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'm obviously not unstalling it right, but I'm not sure what to do? I ran |
I followed the instructions on this page to install it, but they don't have uninstall instructions: https://www.npmjs.com/package/bb-cli |
I tried npm uninstall as well, but still getting the same error... |
Figured it out! Seems I had used the -global flag in those instructions, so to remove it I needed to use:
I then needed to uninstall and re-install Babashka with brew. Now things are working. Thanks for your patience! |
No worries. Glad you are able to run it!
…On Tue, 18 Apr 2023 at 21:28, P. Kerim Friedman ***@***.***> wrote:
Closed #2 <#2> as
completed.
—
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXFVC54BWU7KL2VRUZO4R7LXB45VXANCNFSM6AAAAAAW25RKRI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'm having error messages I don't understand when I try to run the app using "logseq-graph-validator" from within the graph folder, or running "rm -rf .nbb/ && node graph_validator.mjs" from within the app folder. (I was suggested to do the latter by @cldwalker.) Here is what I am seeing. Info about my setup below.
M1 MacBook Pro (always updated to latest version of MacOS)
borkdude/brew/babashka: stable 1.3.176
yarn: stable 1.22.19 (bottled)
node: stable 19.8.1 (bottled), HEAD
The text was updated successfully, but these errors were encountered: