I had a request from DANS management to start checking out the separated node frontend for Dataverse. Is there an alpha/dev release version/tag we should check out, or is this too soon?
(Too soon is a perfectly valid answer - we're eager, but quality takes time : ) )
It's not too soon but please check out this fix you need to bump the version of Solr: https://github.com/IQSS/dataverse-frontend/pull/176
I have this on the agenda to talk about in 15 minutes: https://ct.gdcc.io :big_smile:
It works for me now but I should confirm with @Ellen K that it's working for her now. She's the one who noticed the problem.
Excellent, I'm joining, though I'm in public and won't be able to speak so much. I can type though.
Have you had a chance to try it? I'm curious if you bump into https://github.com/IQSS/dataverse-frontend/issues/178 or not.
Just about to start on that as last item on Friday : )
Hit some problems with getting packages:
npm ERR! 403 403 Forbidden - GET https://npm.pkg.github.com/download/@IQSS/dataverse-client-javascript/2.0.0-pr80.378cc1e/2361fc91f5e8618751025871e860062307b1adf4 - Permission permission_denied: The token provided does not match expected scopes.
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.
I've created a fine grained token for testing purposes, all permissions.
Sorry, sorry, I forgot https://github.com/IQSS/dataverse-frontend/issues/152 is still open. read:packages should be enough. If you'd like to make a PR to update the README, please be my guest!
Much obliged, I'll try instructions there : )
Yeap, got past it. It's running, going to figure out how to get to certain pages now : )
Oh! You have /spa for example?
To see how to pass a DOI to the spa, I recommend watching https://github.com/IQSS/dataverse-frontend#demo-videos
Yeap, that works too. I'm going to read the code, check what pages/routes are available. Looks great already though : )
Cool, so you were able to create a dataset in the old UI and see it in the new UI?
Yeap, absolutely.
Fantastic. What image tag did you use? This:
./run-env.sh <dataverse_image_tag>
Currently running off alpha, but I used npm start to get things working locally. I ran the backend in a different shell.
Oh, ok, so you didn't use that run-env script.
Nope, just ran em separated. I can run them together if you'd like, I'm sure.
Would you mind trying that script? It's documented in the README. I'm trying to reproduce https://github.com/IQSS/dataverse-frontend/issues/179
No problem, lemme kill the other stack real quick.
Thanks! Oh and please make sure to pull from develop to pick up https://github.com/IQSS/dataverse-frontend/pull/176
I'm on develop, no worries.
Great. I only mention it because it was only merged 45 minutes ago. :big_smile:
INFO - Setting up Dataverse on image tag alpha...
INFO - Removing current environment if exists...
INFO - Running docker containers...
[+] Running 1/1
โ dev_dataverse Error 0.9s
Error response from daemon: manifest unknown
Suspect I'm seeing some login problems with ghcr.io; I've used the same token with package permissions separetely and I'm logged in via CLI with that one.
Ah, this is an image thing. The alpha image is on Docker Hub but not GHCR. We plan to document what to pass as an image better in https://github.com/IQSS/dataverse-frontend/issues/177
Can you please try this tag?
./run-env.sh 9692-files-api-extension-display-data
That's the one I just tested with in https://github.com/IQSS/dataverse-frontend/issues/179 where I put some output. (Works on my machine.)
Yeap, that one pulls and it's starting up.
Cool, it theory any recent tag from https://github.com/orgs/gdcc/packages/container/package/dataverse should work.
The idea is the frontend devs typically won't want alpha. They'll want unmerged code that adds a new API or whatever.
Yeap, she runs. I can access the spa page as well on port 8000
Mac has become successfully airborne at this point though
Nice! Ha! Would you be able to leave a note at https://github.com/IQSS/dataverse-frontend/issues/179 ?
Secretly hoping it'll melt and I can get something better : o )
ha
you're on linux, right?
Will do
I'm not unfortunately. I'm on Mac.
I would love to be on Linux. I miss it.
Gotcha, well so am I and Ellen. So it's a good test. :big_smile:
I sometimes miss Linux. :stuck_out_tongue_wink:
Reading the issue; not sure how to access dataverse though. I'm just getting the payara page. Checking the logging.
Gonna restart container real quick.
Oh, it needs time.
I think the timeout is 5 minutes.
So please give configbaker a few minutes to do its thing.
Nah, no worries there; it errored out on my end, likely because my CPU was at 95% and it timed out.
yikes
Yeah, seeing the Payara page is normal for the first minute at least, before the war file deploys and configbaker configures everything.
Running a cleanup, then retrying.
awesome, much appreciated
Creating a dataverse works fine.
Great. Please do leave a comment in that issue, if you don't mind.
Oliver suspects a race condition. Ellen's laptop is quite fast.
Already did. If it's a race condition, I had the opposite. Getting container up took too long that configbaker had a timeout.
Wow, so 5 minutes wasn't enough. :grimacing:
Please feel free to bump up that value in a PR if you like.
Ha, your comment is great. Thanks!
Nah, that's a laptop problem. If anything - I have a perfect reason to ask for something better now.
This topic can be resolved, btw; I have something to showcase : )
Thomas van Erven has marked this topic as resolved.
Much obliged for your help!
Sure! Thanks for all the testing!
Note that sometimes this high CPU load comes from GC calls. Might be neat to Monitor them. Or just try again with some more RAM for DV. 2GB is definitively a close call in some scenarios
(Gc calls originating from JVM trying to free some memory on the heap before finally failing)
Last updated: Oct 30 2025 at 05:14 UTC