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

Latency analysis parameters are not passed in explicitly but via Preference settings #1250

Closed
reteprelief opened this issue May 18, 2018 · 0 comments
Assignees
Milestone

Comments

@reteprelief
Copy link
Contributor

@reteprelief reteprelief commented May 18, 2018

Currently latency analysis takes four boolean settings as parameters. They are currently set via preferences. They are also set from ALISA via a hack in Values.

We should have latency analysis takes them as parameters. In the case of the latency analysis handler the parameters should be taken from the preferences, while from ALISA and other automated invocations they are passed in directly.

@reteprelief reteprelief added this to the 2.3.4 milestone May 18, 2018
@reteprelief reteprelief self-assigned this May 18, 2018
@ghost ghost added the in progress label May 18, 2018
@ghost ghost added review and removed in progress labels May 20, 2018
@ghost ghost removed the review label May 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.