[ https://issues.apache.org/jira/browse/KUDU-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745369#comment-17745369 ]
ASF subversion and git services commented on KUDU-3402: ------------------------------------------------------- Commit 83dd4b0163fd9d315b316315b7acc22f6dc4c3a7 in kudu's branch refs/heads/branch-1.17.x from Zoltan Martonka [ https://gitbox.apache.org/repos/asf?p=kudu.git;h=83dd4b016 ] KUDU-3402 Update trace-viewer with newest catapult changes. Kudu trace viewer was originally forked from the about_tracing with minimal changes. I have done the following steps: 1. Merge master from github.com/catapult-project/catapult into the kudu branch in github.com/cloudera/catapult. 2. Override the kudu_tracing with about_tracing (git hash: c23fd238e1e9704fb4386): $ cd tracing/tracing/ui/extras $ cp about_tracing/* kudu_tracing/ $ cd kudu_tracing/ $ cp about_tracing.html kudu_tracing.html $ rm about_tracing.html $ sed -i 's/about_tracing/kudu_tracing/g' * 3. Redo the few changes that was needed for Kudu and restore the old filter format: https://github.com/cloudera/catapult/commit/003d1462c43c196462f2f317f4d89116c7ca7421 Change-Id: I931de59a2cad944bfb945b3e1bee3e9c96b5b34b Reviewed-on: http://gerrit.cloudera.org:8080/20188 Reviewed-by: Marton Greber <greber...@gmail.com> Tested-by: Kudu Jenkins Reviewed-by: Alexey Serbin <ale...@apache.org> (cherry picked from commit d9fc68f62bf160249f578d2a7e052a732fa5cc1f) Reviewed-on: http://gerrit.cloudera.org:8080/20230 Reviewed-by: Yingchun Lai <laiyingc...@apache.org> Tested-by: Alexey Serbin <ale...@apache.org> > Make tracing.html work on newer browsers > ---------------------------------------- > > Key: KUDU-3402 > URL: https://issues.apache.org/jira/browse/KUDU-3402 > Project: Kudu > Issue Type: Improvement > Reporter: Marton Greber > Assignee: Zoltan Martonka > Priority: Minor > > After starting up Kudu, navigate to one of the Master or Tablet Server > /tracing.html endpoint to see the tracing web UI. By using a recent version > of Chrome, one gets a blank screen. Pulling up the logs, one can see the root > cause: document.registerElement: > {code:java} > Uncaught TypeError: document.registerElement is not a function > at tracing.js:31:88 > at tracing.js:31:448 {code} > By checking the [MDN Web > Docs|https://developer.mozilla.org/en-US/docs/Web/API/Document/registerElement], > it can be seen, that this feature has been deprecated. In Chrome it was > removed in version 80. -- This message was sent by Atlassian Jira (v8.20.10#820010)