The weights could possibly be adjusted, but I doubt it's a priority for @thiggins . Personally I never even noticed there was a Trending widget on the forums until mentionned here.
Trends are probably global, which means none of the newer threads are getting enough views and new replies to get higher on the list.
The forums did get quieter these past few weeks.
I was only able to reproduce the RTC reset with Asuswrt-Merlin, I couldn't reproduce it when running the stock firmware after trying for about 3-4 days, which indicates the issue was only with the GPL version that Asuswrt-Merlin was using.
My provider seems to be doing server updates and breaking stuff along the way. A few days ago they made a change that removed the PHP handler I was using, I had to switch to a different PHP handler.
Ran some tests with them, the most major stability issues seem specific to the GPL version that I am using. I also tried to gather user feedback on the forums, apparently all those people who claimed their RT-BE92U was totally unusable have disappeared, the feedback received from current users...
Recent 3006 releases completely changed the way wireless networks are stored in nvram. If your script was designed for 3004 or early 3006, then that script will no longer work.
(Did Github.com get attacked/compromised? I randomly get github.com blocked by my antivirus this afternoon, claiming a malicious website.)
Asus recently did extensive changes to the dnsmasq code, so it's possible that some of my customizations were lost in the GPL merge.
The whole function will mount a partition, so I can see restarting httpd after mounting the volume to ensure that httpd is aware of the system level change.
That code was added in GPL 3006_102_34369.
Without knowing the intention behind it it's hard to tell if it's legitimate or not. The fact...
If Asus decided to put an httpd restart there it might be for a reason, so I'm not really keen on changing that behaviour.
Nothing in that log even mentions dnsmasq, only httpd gets restarted.
That DEBUG_RCTEST constant has been present since at least 2017 according to git blame (the initial GPL merge when the repo was started), so at this point I'd rather not touch it. This enables the "rc" applet, which may potentially be used by other components of the firmware.
That code block...
The real question is why Asus is setting DEBUG_RCTEST in the Makefile, which I would expect should only be enabled for test purposes. I just checked the GPL code itself and it's there.
I also see this (unrelated) typo next to a DEBUG_RCTEST section I just reviewed:
#ifdef HND_ROTUER
Well...
Check the system log. The most likely reason I can think of would be your router runs out of memory while doing the scan, causing service crashes. In the past running a fs check on a large disk has always been a problem due to the amount of RAM required for it.