newrelic / nr1-cloud-optimize

NR1 Cloud Optimize allows you to Identify right-sizing opportunities and potential savings of your AWS, GCP, and Azure instances across your cloud environment.
https://discuss.newrelic.com/t/cloud-optimizer-nerdpack/82936
Apache License 2.0
50 stars 37 forks source link

Unable to update the advanced config fields #41

Closed rjusselrelic closed 4 years ago

rjusselrelic commented 4 years ago

Unable to adjust the configuration fields

When trying to adjust these fields, the input is not received. The field does not change, and the console shows the following message: [Violation] 'input' handler took 243ms

Steps to Reproduce

Run the nerdpack, select the configuration menu option, and attempt to change a field value

Expected Behaviour

The fields would show the changed value and upon exit/save update the multiplier, inclusion period etc.

Screen Shot 2020-04-30 at 11 32 29 PM

Relevant Logs / Console output

[Violation] 'input' handler took 198ms
[Violation] 'input' handler took 194ms
[Violation] 'input' handler took 187ms
[Violation] 'input' handler took 195ms
[Violation] 'input' handler took 217ms
[Violation] 'input' handler took 186ms
[Violation] 'input' handler took 186ms
[Violation] 'input' handler took 184ms
[Violation] 'input' handler took 241ms
[Violation] 'input' handler took 221ms
[Violation] 'input' handler took 216ms
[Violation] 'input' handler took 253ms
[Violation] 'input' handler took 230ms
[Violation] 'input' handler took 244ms
[Violation] 'input' handler took 244ms
[Violation] 'input' handler took 260ms
[Violation] 'input' handler took 243ms
[Violation] 'input' handler took 248ms
[Violation] 'input' handler took 235ms
[Violation] 'input' handler took 234ms
[Violation] 'input' handler took 254ms
[Violation] 'input' handler took 238ms

Your Environment

Additional context

Kav91 commented 4 years ago

@rjusselrelic thanks for raising.

Just debugged the issue, it has broke on this PR https://github.com/newrelic/nr1-cloud-optimize/pull/40

cc @tangollama @devfreddy @danielgolden

devfreddy commented 4 years ago

:tada: This issue has been resolved in version 1.2.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: