Skip to content
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

Errors when upload using the newest CLI #3289

Open
colehank opened this issue Jan 17, 2025 · 5 comments · Fixed by #3291
Open

Errors when upload using the newest CLI #3289

colehank opened this issue Jan 17, 2025 · 5 comments · Fixed by #3291
Assignees
Labels

Comments

@colehank
Copy link

What went wrong?

in the newest openneuro version, when I upload my dataset by deno run -A jsr:@openneuro/cli upload --ignoreWarnings --dataset ds005810 NOD-MEG, I meet the errors as follows:

error: Uncaught (in worker "") SyntaxError: The requested module 'path-browserify' does not provide an export named 'join' at <anonymous> (file:///Users/zgh/Library/Caches/deno/npm/registry.npmjs.org/isomorphic-git/1.29.0/index.js:3:10)
error: Uncaught (in promise) null

Expected behavior

just let the cli work well

How to reproduce

Image

Desktop

  • OS: MacOs 15.2

Phone

  • Device:
  • OS:
  • Browser:
  • Version:

Additional information

No response

@colehank colehank added the bug label Jan 17, 2025
@nellh
Copy link
Contributor

nellh commented Jan 17, 2025

Hi, thank you for the bug report.

Can you try running this with the --reload argument to Deno like this deno run --reload -A ...? This will reload cached dependencies and may resolve this issue.

@colehank
Copy link
Author

Thanks for your reply!
I changed my code to deno run --reload -A jsr:@openneuro/cli upload --ignoreWarnings --dataset ds005810 NOD-MEG,
But this error still occurs. My deno version is 2.1.6
Image

@nellh
Copy link
Contributor

nellh commented Jan 17, 2025

A fix for this is included in @openneuro/cli release 4.30.1. Please reopen if you are still seeing this issue after updating with deno --reload once more.

@colehank
Copy link
Author

colehank commented Jan 18, 2025

Thank you for the quick update, but it seems that I am still encountering some issues. I checked and I am using version 4.30.1, but the problem persists. I’m wondering if there might be an issue with my local environment. And it looks like I don't have permission to reopen the issue

Image

@nellh
Copy link
Contributor

nellh commented Jan 25, 2025

@colehank A new release with 4.30.2 includes another fix for this, can you please test with the reload flag again and let me know if this has resolved your issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants