Skip to content

[SPARK-11824] [WEBUI] WebUI does not render descriptions with 'bad' HTML, throws console error #10159

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

Closed
wants to merge 1 commit into from

Conversation

srowen
Copy link
Member

@srowen srowen commented Dec 5, 2015

Don't warn when description isn't valid HTML since it may properly be like "SELECT ... where foo <= 1"

The tests for this code indicate that it's normal to handle strings like this that don't contain HTML as a string rather than markup. Hence logging every such instance as a warning is too noisy since it's not a problem. this is an issue for stages whose name contain SQL like the above

CC @tdas as author of this bit of code

@SparkQA
Copy link

SparkQA commented Dec 5, 2015

Test build #47228 has finished for PR 10159 at commit 85c24f2.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@srowen
Copy link
Member Author

srowen commented Dec 8, 2015

Just removing the warning seems pretty harmless, and I am fairly confident it's the right thing to do given the JIRA. I'm going to merge later today.

@vanzin
Copy link
Contributor

vanzin commented Dec 8, 2015

So, I'm a little confused; is the text rendered correctly or not? If it is, then that part was not a bug, right (and doesn't need to be mentioned in the pr title)?

@srowen
Copy link
Member Author

srowen commented Dec 8, 2015

@vanzin yeah the title seems wrong. The description is rendered unescaped in this case and is fine. The problem is the big warning-level stack trace in the console every time this happens.

asfgit pushed a commit that referenced this pull request Dec 9, 2015
…ML, throws console error

Don't warn when description isn't valid HTML since it may properly be like "SELECT ... where foo <= 1"

The tests for this code indicate that it's normal to handle strings like this that don't contain HTML as a string rather than markup. Hence logging every such instance as a warning is too noisy since it's not a problem. this is an issue for stages whose name contain SQL like the above

CC tdas as author of this bit of code

Author: Sean Owen <[email protected]>

Closes #10159 from srowen/SPARK-11824.

(cherry picked from commit 1eb7c22)
Signed-off-by: Sean Owen <[email protected]>
@srowen
Copy link
Member Author

srowen commented Dec 9, 2015

Merged to master/1.6 to quiet the noise on the console

@asfgit asfgit closed this in 1eb7c22 Dec 9, 2015
@srowen srowen deleted the SPARK-11824 branch December 9, 2015 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants