-
Notifications
You must be signed in to change notification settings - Fork 51
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
Update for MP6 #494
Update for MP6 #494
Conversation
Remove Open Tracing Add Telemetry
Remove Open Tracing Add Telemetry
@Emily-Jiang |
Depending on which version of MP health you are talking about. It was only deprecated later. It was fine in the earlier version of MP Health. I suggest you to fix the test error first not to change other things. |
@luiseufrasio did you figure out what was the test failures and propose a update on the PR to unblock this? |
@Emily-Jiang the tests seems to be NOT running: https://github.com/eclipse/microprofile-starter/pull/494/checks |
The conflict needs to be solved before the tests can be executed. @majidmostafavi can you please resolve the conflicts and then the CI jobs can be launched? |
src/main/java/org/eclipse/microprofile/starter/rest/APIEndpointV7.java
Outdated
Show resolved
Hide resolved
@@ -0,0 +1,4 @@ | |||
{"configs":{" | |||
MP33":{"supportedServers":[" | |||
]},"MP32":{"supportedServers":[ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure this file. Do you need to just mention MP60?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rdebusscher we are stuck on this failure. Can you please shed some lights on this? Your help is very much appreciated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Emily-Jiang What is the issue exactly? From the failed test run, it just seems a problem with some assertions on text values.
Not much time to go in detail for the moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found the error in the surefire-reports and changed the code to print the URL call which fails: Download failed. URI: http://127.0.0.1:9090/api/project?supportedServer=LIBERTY&selectedSpecs=CONFIG&selectedSpecs=FAULT_TOLERANCE&selectedSpecs=HEALTH_CHECKS&selectedSpecs=METRICS&selectedSpecs=OPEN_TRACING&selectedSpecs=OPEN_API&artifactId=liberty&buildTool=MAVEN expected:<200> but was:<400>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried the URL locally running on liberty:
So after I called:
http://127.0.0.1:9080/mp-starter/api/project?supportedServer=LIBERTY&selectedSpecs=CONFIG&selectedSpecs=FAULT_TOLERANCE&selectedSpecs=HEALTH_CHECKS&selectedSpecs=METRICS&selectedSpecs=OPEN_TRACING&selectedSpecs=OPEN_API&artifactId=liberty&buildTool=MAVEN
I received back:
{
"error": "One or more selectedSpecs is not available for the given mpVersion",
"code": "ERROR003"
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure the version combination.
What about the error for APITest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Error in the API test is due to the addition of the Telemetry option. Please update the test to the new expected values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which file needs to be updated? @rdebusscher
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on the log of the test
https://github.com/eclipse/microprofile-starter/pull/494/checks#step:7:17864
This is the failure
supportMatrix(org.eclipse.microprofile.starter.APITest) Time elapsed: 0.319 sec <<< FAILURE!
java.lang.AssertionError: Response of /7/supportMatrix
And from the test method APITest#supportMatrix
public void supportMatrix() throws FileNotFoundException {
test(v7Matrix, "/7/supportMatrix");
we see that the contents of this file os compared to the response
v7Matrix = new File(getClass().getClassLoader().getResource("json_examples/v7/supportMatrix.json.segments").getFile());
Why is there a v7 of the Api created when it is identical to v6? |
v7 has Telemetry added though. |
The version of the API has nothing to do with the config op the MP versions and the options. It is about the available endpoints, their parameters and responses. So
Even the API versions 2 and higher, all return this result which includes Telemetry. So there is no need at all to have a new API version. |
before MP50 and MP60 use Health
before MP50 and MP60 use Health
I thought the earlier version of MP (1.x-5.x) should NOT return Telemetry @rdebusscher |
Earlier versions of MP will not return Telemetry. As I already said, MP Version and API version of the Starter app are 2 independent things. |
Should the earlier API version such as 2.x return Telemetry at all? |
In my opinion, yes. Those that make an integration with the API should not use latest version since that can have breaking changes at any time. Only a certain API version is stable. |
Thanks @rdebusscher ! @majidmostafavi you don't need to create a new version of the API. |
|
||
import javax.ws.rs.Path; | ||
|
||
@Path("/7") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on my understanding from @rdebusscher , there is no need to do this change.
@Emily-Jiang @cesarhernandezgt I found the way to fix the issues from the API MicroProfile Starter but I can't add commits on this PR, it seems someone needs to give me some permission:
|
@breakponchito it was the branch from @majidmostafavi . I think you can checkout his branch and then do a new PR.
|
yes I already create a new PR here: #499 @Emily-Jiang Could you help me with this? |
Add Telemetry
update for MP6