We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It appears that there is a logic issue in the member.entity.js file, specifically at the following line: https://github.com/ibp-network/ibp-monitor/blob/59631c7ff3667f4413e14670f5df1e771b5a2476/domain/member.entity.js#L57C49
member.entity.js
The current code seems to incorrectly increment the member level by +1, which results in monitoring for instances that are not yet running.
What is the reasoning here for increment? Wouldn't it be making more sense to use members.json as source truth?
The text was updated successfully, but these errors were encountered:
@pandres95 was there any reasoning for this increment if I look to fix it now over the weekend?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
It appears that there is a logic issue in the
member.entity.js
file, specifically at the following line:https://github.com/ibp-network/ibp-monitor/blob/59631c7ff3667f4413e14670f5df1e771b5a2476/domain/member.entity.js#L57C49
The current code seems to incorrectly increment the member level by +1, which results in monitoring for instances that are not yet running.
What is the reasoning here for increment? Wouldn't it be making more sense to use members.json as source truth?
The text was updated successfully, but these errors were encountered: