Skip to content
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

fix: Restore access to existing wireless graphs #6593

Merged
merged 1 commit into from
May 5, 2017

Conversation

murrant
Copy link
Member

@murrant murrant commented May 5, 2017

DO NOT DELETE THIS TEXT

Please note

Please read this information carefully. You can run ./scripts/pre-commit.php to check your code before submitting.

Testers

If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926

@mention-bot
Copy link

Thank you for submitting a PR @murrant! We have found the following @arjitc, @paulgear and @clinta based on the history of these files to review this PR.

@LibreNMS-CI
Copy link

Auto-Deploy finished, Test PR at http://6593.ci.librenms.org or https://6593.ci.librenms.org

@scrutinizer-notifier
Copy link

The inspection completed: No new issues

@laf
Copy link
Member

laf commented May 5, 2017

Is their a point in adding this back if we no longer poll for data?

@murrant
Copy link
Member Author

murrant commented May 5, 2017

So users can see their old graphs still. We didn't remove the graphs and I didn't intend too.

At a later time we would remove both the graphs and this.

@laf laf merged commit 50d31ad into librenms:master May 5, 2017
@murrant murrant deleted the restore-graphs-wireless branch May 5, 2017 19:38
@lock
Copy link

lock bot commented May 18, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

@lock lock bot locked as resolved and limited conversation to collaborators May 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants