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
Parse URL if bad URI #70947
Parse URL if bad URI #70947
Conversation
Is there a good way to test this change?? I'm looking at this page, https://github.com/elastic/elasticsearch/blob/master/TESTING.asciidoc, but I'm not really a java guy so IDK what the generic test command is. |
This is what i get when I run
|
5b0286c
to
0a4c01c
Compare
Pinging @elastic/es-core-features (Team:Core/Features) |
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.
@legoguy1000, what are you trying to achieve with this change? Since URLs are a subset of URIs, I wouldn't expect there to be a case where a string was an invalid URI but a valid URL.
The URI type fails when parsing a url with non URL encoded values like spaces in the path. The URL type does not. |
What happens if you use the included gradle wrapper via |
|
Like I said I'm not a Java guy so IDK if i've even installed all the dev dependences that i need |
It looks like you're using JDK16 which does not appear to work well with our build system, yet. Try switching to JDK15 and doing a |
@elasticmachine ok to test |
@legoguy1000, if you're having trouble with the Java build framework on this one, I can pick it up since I now understand what the issue is. Let me know what you prefer. |
I haven't had a chance to do much with it lately. Feel free to push whatever changes you think are needed. I would like to know what i'm missing or what I should change/do for next time. |
Cool, I'll get a fix in for this before the next patch release. If you want to open a thread about getting your local build working in our forums (https://discuss.elastic.co/), tag me ( |
The resolution for this issue was merged in #71559. |
gradle check
?