landreev
landreev
Here's a real life example of a problem this will solve: We had a support request (RT 321319) where a remote admin was asking about hardening their installation, specifically about...
This looks good. Once you make a PR I can review and/or QA it quickly.
(As is the custom with your PRs, it is merged, but it's left up to you to delete the branch, or not)
@poikilotherm Hi, Harvard just gave us all an extra mini-vacation, but I'm back at work. I made this draft PR last week that finally gets rid of the old custom...
Yay! 🎉 I was about to ask myself if there was going to be RC2... I'm ok either way - up to you. Thank you again!
As for the first 2 formats under 1., we really don't support them (at least for now), so we should probably hide them from the pulldown and/or not allow people...
As for > 2. Harvesting as a server using a v5.11 client, same formats fail but json reports a different error: unable to find valid certification path to requested target...
@poikilotherm > sounds like this reveals some internal network problems?! If there is anything I can do, please reach out (here/Matrix/Slack/Issue in XOAI/...) I don't think it's network problems. It...
> I wasn't saying that but since you asked I have now tested json using v5.11 as both client (demo) and server (prod) and get the same license error. OK,...
So, about those dataverse_json import errors: The `Invalid license: CC0` error was there because some of the prod. datasets in the set you were testing did not get re-exported after...