Inject node issue - interval settings missing when interval selected

Hi dear,
a strange behavior happens to me with inject node on a particular machine.
For example, when I try to set interval, no relevant boxes appear to chose times

while I'm expecting something like this

Cattura2

Same behavior with other options ("Interval between times" and "at a specific time")

I'm using node red 1.0.3 on Raspbian/Buster

I've checked for inject.js integrity (I've compared it with another one from another machine where it is working) and I've not encountered any problem.

Does anybody have a suggestion?

2nd time I have seen this lately

Can you look in browsers console log for clues & show us if you spot the problem?

Thank you so much for the quick reply.
I'm sorry for duplicating the topic...I didn't see the other one before.
Anyway, if I can try to hold on here, I can confirm the issue in the console of the browser as per the following picture

I think there could be something broken (but I don't know what) because when I tried to update node red nothing happened. So restarted everything, made an update, upgrade, npm rebuild of .nore-red folder and then I was able to update to 1.0.6 revision.

Now I have

and the same problem

On the same problem installation as you first reported or a different node-red installation?

Same problem (missing boxes for the interval settings) on the updated node-red installation.

Can you try clearing the cache in the browser and try again? Might need to force a couple of full refreshes too. Ctrl-F5 for me (Firefox), but might be different for you.

Just so I fully understand, you now have 2 node-red installs that display this anomaly?

No, I have several (may be dozen) installations where everything is fine.
Only in one of these, where I've just updated from 1.0.3 to 1.0.6, I have this strange behavior

Cache totally cleaned. Nothing different. Actually I really don't know what to check more.
The strange is also that inject node push a message every 1 second when interval is selected.

Can you try it in a different browser (or on a different client machine)?

I currently use chrome. I 've tried with 3 different browsers (chrome, avast browser, edge ...firefox is not able to open node red board for flows). Nothing.
To add more, on 2 different tab of the same chrome session, I run simultaneously 2 node red on different machines (192.168.1.13 and 192.168.1.193). While on the first there is no problem on the second I have the issue.

I wonder if there is a contrib node that is polluting the editor in someway that breaks this. It's the only thing I can think of.

@marcos can you share a list of any contrib nodes you've added to this instance?

Do you mean something like this ?
@clysema/node-red-contrib-ui-week-schedule
0.1.4
node-red
1.0.6
node-red-contrib-bigcsv
1.2.0
node-red-contrib-bigtimer
2.3.1
node-red-contrib-boolean-logic
0.0.3
node-red-contrib-calc
1.0.1
node-red-contrib-calendar-trigger
0.9.1
node-red-contrib-config
1.1.2
node-red-contrib-counter
0.1.5
node-red-contrib-dashboard-sum-bars
0.0.1
node-red-contrib-date-converter
0.0.3
node-red-contrib-deglitch
1.0.2
node-red-contrib-fast-csv
0.4.0
node-red-contrib-filter
0.1.3
node-red-contrib-frequency-meter
0.0.1
node-red-contrib-gpsd
1.0.2
node-red-contrib-ibm-watson-iot
0.2.8
node-red-contrib-jsonpath
0.1.1
node-red-contrib-light-scheduler
0.0.15
node-red-contrib-modbus
5.10.1
node-red-contrib-mytimeout
3.2.0
node-red-contrib-owntracks
0.0.2
node-red-contrib-persist
1.0.3
node-red-contrib-pid
1.1.6
node-red-contrib-play-audio
2.5.0
node-red-contrib-revpi-nodes
1.0.6
node-red-contrib-schedex
1.10.2
node-red-contrib-simple-weekly-scheduler
0.0.14
node-red-contrib-timed-counter
0.0.4
node-red-contrib-timerswitch
1.2.4
node-red-contrib-ttn
2.0.5
node-red-contrib-ui-led
0.3.1
node-red-contrib-web-worldmap
2.3.10
node-red-contrib-webhookrelay
0.3.0
node-red-dashboard
2.22.0
node-red-node-email
1.7.8
node-red-node-geofence
0.1.2
node-red-node-openweathermap
0.2.2
node-red-node-pi-gpio
1.0.9
node-red-node-pi-gpiod
0.0.13
node-red-node-ping
0.2.0
node-red-node-random
0.1.4
node-red-node-rbe
0.2.8
node-red-node-serialport
0.10.2
node-red-node-smooth
0.1.2
node-red-node-tail
0.1.1
node-red-node-ui-list
0.2.5
node-red-node-ui-table

And how does that list compare to the instances where you don't see the issue? Can we narrow it down at all?

The other is long too and has so many different nodes. I'll try to remove what isn't needed in the flow and I'll let you know. Thanks

Look for nodes on the failing list but not on the other one.

And it isn't just about what nodes you have in your flows - it's what you have installed that is relevant.

Fixed. I'm not yet able to say what node was causing the issue but I've proceeded in this way:
because there were 4 flows, I deleted the 3 flows I use for tests on this machine. The issue was still there. So I went to remove all unused nodes. Meanwhile, I was checking if the inject node came back to normality. Finally, only after a rpi reboot, inject node was come back to work properly. Now, I need to recover deleted test flows to proceed with my development so I'll pay more attention to inject node, and hopefully, I'll let you know which is the node that causes the issue as soon as it will manifest again.
Thank you so much.

Marcus, it would at least help us track it down if you could dump that list once more now that it's working.

We will at least see which 4 you uninstalled.

I was assuming you uninstalled till I reread this bit - did you actually uninstall or just delete nodes in your flow?

Hi Steve,
I completely uninstalled nodes. Any way, going forward with my activities, at the moment I can't restrict the issue to specific node

Hopefully by today COB I'll be able to write more.

I'm here again. I completely recovered my 4 flows with all relevant nodes (I've installed all them again). Then I've done some check; restarted node-red, rebooted rpi... every thing is fine. Inject node works properly.
At this point I can suppone that something was wrong in those nodes which hadn't an instance in the flow...even if this sound a bit strange.

Those node were the following:
node-red-contrib-bigcsv
1.2.0
node-red-contrib-bigtimer
2.3.1
node-red-contrib-boolean-logic
0.0.3
node-red-contrib-calendar-trigger
0.9.1
node-red-contrib-counter
0.1.5
node-red-contrib-deglitch
1.0.2
node-red-contrib-fast-csv
0.4.0
node-red-contrib-filter
0.1.3
node-red-contrib-frequency-meter
0.0.1
node-red-contrib-gpsd
1.0.2
node-red-contrib-ibm-watson-iot
0.2.8
node-red-contrib-jsonpath
0.1.1
node-red-contrib-modbus
5.10.1
node-red-contrib-pid
1.1.6
node-red-contrib-play-audio
2.5.0
node-red-contrib-revpi-nodes
1.0.6
node-red-contrib-timerswitch
1.2.4
node-red-contrib-ttn
2.0.5
node-red-node-serialport
0.10.2
node-red-node-smooth
0.1.2

In case of news I'll let you all know.