[Bug] non-positive interval for NewTicker about snmpcollector

[sbengo]

I'm afraid that there is some problem with the -1 support, as the FilterFreq feature has been refactored and set it up as a Ticker.

Thanks for the information, we will try to fix this ASAP!

Thanks,
Regards!

[gmwiku]

Previous version runs smoothly.

[sbengo]

Hi @gmwiku , thanks for submitting this.

We will review this ASAP, just a question in order to have an idea of what can be happening:

• Can provide seme SNMPDevice CFG?
• Do you have some device with -1 as UpdateFilterFrequency?

Thanks,
Regards!

[gmwiku]

• Can provide seme SNMPDevice CFG?

Unfortunatelly I'm not allowed to share this information.

• Do you have some device with -1 as UpdateFilterFrequency?

Yes, 1 of 283 devices has such setting, I can try to change it and test if it helps. :)

[gmwiku]

I'm afraid that there is some problem with the -1 support, as the FilterFreq feature has been refactored and set it up as a Ticker.

After update FilterFreq to some positive value the problem disappeared. Thanks a lot for your tip.

BTW I'm not sure if it is related to JS libraries or to the browser, but under Chrome for Linux (Wersja 96.0.4664.45 (Oficjalna wersja) (64-bitowa)) "Device status" page doesn't contain any items, only the headers of the table and there are some errors in browser console:

vendor.c4bdd793bac7a4707054.bundle.js:1 ERROR TypeError: Cannot read properties of undefined (reading 'toString')
    at main.fd1107faf03ac8424150.bundle.js:1
    at Array.forEach (<anonymous>)
    at main.fd1107faf03ac8424150.bundle.js:1
    at Array.forEach (<anonymous>)
    at l.changeFilter (main.fd1107faf03ac8424150.bundle.js:1)
    at l.onChangeTable (main.fd1107faf03ac8424150.bundle.js:1)
    at e._next (main.fd1107faf03ac8424150.bundle.js:1)
    at e.__tryOrUnsub (vendor.c4bdd793bac7a4707054.bundle.js:1)
    at e.next (vendor.c4bdd793bac7a4707054.bundle.js:1)
    at e._next (vendor.c4bdd793bac7a4707054.bundle.js:1)

In another browser there is no problem. :)

[sbengo]

I think it can be the first time that the dev status is loaded and it is not connected yet. I think that we missed some checks (dev properties) in order to ensure that all data is available to be shown.

Thanks for submitting this, I will try to repro and will open a new issue, I will remain this one to the -1 support.

Thanks,
Regards!

[gmwiku]

Problem with JS library and/or browser is not valid any more ... probably some library has been cached, now Device status page is displayed properly. snmpcollector also works stable. So the only valid issue in this thread is UpdateFilterFrequency equal to -1 - according to displayed popup tip -1 value is still allowed and recomended in the case we don't want filter updates.