-
Notifications
You must be signed in to change notification settings - Fork 334
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
self.tags error in regenerator is wrong #1612
Comments
andyxning
pushed a commit
to andyxning/shinken
that referenced
this issue
May 7, 2015
andyxning
pushed a commit
to andyxning/shinken
that referenced
this issue
May 7, 2015
andyxning
pushed a commit
to andyxning/shinken
that referenced
this issue
May 7, 2015
Open
I think i can give a method to fix this bug. see PR #1616. However, with memory leak in WebUI, i have no idea and i think we should continue to work on it. :) |
was merged if I'm not wrong, I fix here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
it seems that the root reason is that the regenerator module has something wrong. Currently, i can tell that when we reload configuration, then the
self.tags
inRegenerator
is wrong. It does not have anything to clean all previous tags count instead just adding.this will cause all the tags count number increase every time we reload the configuration.
This will also make WebUI to present some error info.
and some related issues #1597
The text was updated successfully, but these errors were encountered: