Skip to content

Conversation

@Leemoonsoo
Copy link
Member

This PR fixes problem described in
https://issues.apache.org/jira/browse/ZEPPELIN-331

By excluding the webbrowser who created the angular object update event from broadcast target.

  • exclude from broadcast
  • add unittest

@Leemoonsoo Leemoonsoo changed the title Don't update back the browser where updated the angular object ZEPPELIN-331 Don't update back the browser where updated the angular object Oct 13, 2015
@corneadoug
Copy link
Contributor

Do you know how to reproduce that issue?

@Leemoonsoo
Copy link
Member Author

You can easily reproduce when there are big network latency between your browser and zeppelin server.

@Leemoonsoo Leemoonsoo force-pushed the ZEPPELIN-331 branch 2 times, most recently from 114eecf to ad8657d Compare October 18, 2015 10:19
@Leemoonsoo
Copy link
Member Author

Ready to merge

@Leemoonsoo
Copy link
Member Author

Merge if there're no more discussions

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'd better change the level of this log to debug. I saw the issue to change it with this kind of logs

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for finding this one. update pushed.

@Leemoonsoo Leemoonsoo force-pushed the ZEPPELIN-331 branch 3 times, most recently from b99186d to cd45a7f Compare November 14, 2015 11:39
@asfgit asfgit closed this in 0fde27f Nov 15, 2015
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