-
Notifications
You must be signed in to change notification settings - Fork 3
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
products/{identifier}
missing properties object in application/json response
#155
Comments
Testing with old version? When I test on PR NASA-PDS/registry-api#82 I get (hopefully I got cut-n-paste correct):
|
@al-niessner copy that. I will wait to see if @tloubrieu-jpl @ramesh-maddegoda or @tdddblog can test and confirm this? |
If it is, we can just add it to addressed in issues in the PR. |
@jordanpadams and @al-niessner, in the docker compose related work, I am directly pulling the following image of the Registry API.
I get the following output with that. May be nasapds/registry-api-service image does not have the latest version. http://localhost:8080/products/urn%3Anasa%3Apds%3Ainsight_rad%3A%3A2.1
|
@ramesh-maddegoda so that docker image is from what is actually in DockerHub? If so, then I think that is an older version than the current main branch. |
@jordanpadams , that is correct. The docker compose is expected to pull from our DockerHub images (when the image is not available locally), to simply the deployment, without having to build locally. |
@ramesh-maddegoda copy. could you try running the testing use case we are talking about here using one of the other docker compose use cases, where we want to deploy everything but deploy the API built from source. I think this is currently called something like |
@jordanpadams and @al-niessner, I tried to build the the
Therefore, I tried to use the jar file available at registry-api v0.5.0-SNAPSHOT. This is the latest jar file available at https://github.com/NASA-PDS/registry-api/releases . Note: I am using the test data downloaded from the following URL.
But with above
|
thanks @ramesh-maddegoda so looks like this may have been fixed per NASA-PDS/registry-api#82. will update that PR comment to make sure it is tested. |
@ramesh-maddegoda I was able to build. I need to check what local setting might impact you or me. |
The build failure worries me. If the main branch fails like that, then how can we trust the latest built JAR file? I do docker builds of this stuff all the time, and |
@tloubrieu-jpl @ramesh-maddegoda @jordanpadams
I believe that error is because nobody has run maven in NASA-PDS/registry-api to install the artifacts in the maven repo sonatype.org. They did get renamed in one of my various branches. |
@al-niessner @ramesh-maddegoda @tloubrieu-jpl I just removed my local maven repo and did a fresh @ramesh-maddegoda what version of Java and Maven are you running? Maybe it was just some funky thing with sonatype when you ran it yesterday? |
Java version:
Maven version:
|
Hi @ramesh-maddegoda , that worked for me as well with a fresh local maven repository (~/.m2).
|
Hi @tloubrieu-jpl, I think, then it can be a specific issue on my laptop. I got both JDK and maven from Homebrew. Will troubleshoot that. To check the specific issue on this ticket, is it possible to push the latest docker image of registry-api to Dockerhub? |
🐛 Describe the bug
missing properties object in application/json response (maybe others?)
📜 To Reproduce
When querying
products/
endpoint, I get:But with
products/urn:nasa:pds:orex.ovirs::10.0
(missing properties):🕵️ Expected behavior
properties
block should be included inproducts/{identifier}
response as well.🦄 Related requirements
⚙️ Engineering Details
We should definitely test the other endpoints to make sure this is working correctly as well.
The text was updated successfully, but these errors were encountered: