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

Editing stream rule value does not update consistently on web page #1490

SoMuchToGrok opened this Issue Jun 16, 2015 · 2 comments


None yet
4 participants

SoMuchToGrok commented Jun 16, 2015

Hey Team,

When I edit a stream rule value, and click save, the value itself does not [consistently] update on the web page, despite a "Success! Stream rule has been successfully updated" message. The value IS updated in MongoDB (refreshing the page causes the stream rule to show the correct data). Some sort of javascript bug?

I've been able to reproduce it a few times, but it's inconsistent. Using the latest version of Chrome. If you need anything else, let me know.



This comment has been minimized.


edmundoa commented Jun 16, 2015


This is a problem with MongoDB, which only ensures write atomicity on a single document. As stream rules and streams are different documents (and are stored in different collections), sometimes there are inconsistencies in the data we display after updating stream rules. Anyway, data is persisted and should be consistent after some time, e.g. after a page reload.

I am not sure if we can do much about this but I'll leave the ticket open for now to see if someone has any idea on how to fix this issue.

@kroepke kroepke added this to the 1.2.0 milestone Jun 18, 2015

@bernd bernd added the bug label Aug 11, 2015

@edmundoa edmundoa self-assigned this Sep 3, 2015


This comment has been minimized.


edmundoa commented Sep 3, 2015

Investigated this a bit further and turns out it's not related to MongoDB at all, but there is a bug in our Javascript code updating the stream rule that may trigger sometimes.

@edmundoa edmundoa closed this in c8f2a67 Sep 3, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment