Open
Conversation
wistefan
added
the
patch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Greetings @wistefan
It has been detected in one of the environments that the get entities request return a 500 error. Logs indicate the following message regarding validFor field in productSpecification API
{"timestamp":"1768918627586","level":"WARN","thread":"default-nioEventLoopGroup-1-9","logger":"org.fiware.tmforum.common.repository.TmForumRepository","message":"Was not able to list entities.","raw-message":"Was not able to list entities.","exception":"io.github.wistefan.mapping.MappingException: Was not able to invoke method setValidFor.\n\tat io.github.wistefan.mapping.EntityVOMapper.invokeWithExceptionHandling(EntityVOMapper.java:459)After debugging it locally it seemed like a serialization problem so I push this in order to fix this
Best regards