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

registry-mgr return ERROR null #111

Closed
tloubrieu-jpl opened this issue Nov 21, 2024 · 2 comments · Fixed by NASA-PDS/registry-common#114, NASA-PDS/validate#1080, NASA-PDS/harvest#220 or #118
Assignees
Labels

Comments

@tloubrieu-jpl
Copy link
Member

Checked for duplicates

No - I haven't checked

🐛 Describe the bug

From In Sook Moon, PPI:

Harvest worked yesterday, but somehow today I got the following message today.

[SUMMARY] Reading configuration from /opt/pds/registry/harvest-4.0.4/./conf/ppi/vex-aspera4-els-pad.xml
[SUMMARY] Output directory: /tmp/harvest/out
[ERROR] null

I tried with another data bundle.

Another issue with the registry

./bin/registry-manager set-archive-status -auth /home/sysop/.auth/registry-auth.txt -es file:///home/sysop/config/ppi_mcp_prod.x ml -lidvid urn:nasa:pds:vex-aspera4-els::1.0 -status archived

[ERROR] null

Could you please explain what the problem is?

🕵️ Expected behavior

I expected the tool to work and change the archive status

📜 To Reproduce

...

🖥 Environment Info

No response

📚 Version of Software Used

harvest v4.0.4

🩺 Test Data / Additional context

No response

🦄 Related requirements

🦄 #xyz

⚙️ Engineering Details

No response

🎉 Integration & Test

No response

@al-niessner
Copy link
Contributor

al-niessner commented Dec 3, 2024

Cannot duplicate. In the end, somebody somewhere is throwing an exception without a message. There are several handler that print the '[ERROR]' part of this followed by the ex.getMessage() which in this case is null.

I guess one option is to look for all System.out of '[ERROR]' and then replace it with a more robust check for null and if null then do a stacktrace instead. It would help us find the offending exception(s) and get meaningful and/or helpful messages in there.

@tloubrieu-jpl
Copy link
Member Author

For now, @al-niessner will add a stack trace instead of the null message. That will help to investigate that error in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment