No worries, and there's no need to apologize. We simply have a different perspective; no harm was done, and you have nothing to apologize for.I totally agree. It's good to hear other opinions
I apologize for any inconvenience!
No worries, and there's no need to apologize. We simply have a different perspective; no harm was done, and you have nothing to apologize for.I totally agree. It's good to hear other opinions
I apologize for any inconvenience!
Yes, those new screenshots are absolutely much better. Now, I assume that all 3 were taken *after* the problem had already occurred. Perhaps you can provide the output of the shell script now, while the problem still exists, and before you try to recreate it. There might still be some clues there.I just split my scroll screenshot into 3 proper screenshots in the original post. If you or any other user would ever need it.
Exactly!Now, I assume that all 3 were taken *after* the problem had already occurred.
Unfortunately, I reconfigured the script an hour ago. I'll do the job at my earliest free time.There might still be some clues there.
I tried to reproduce the problem but didn't succeed after a few tries. I'll try to figure it out as soon as possible.while the problem still exists, and before you try to recreate it. There might still be some clues there.
Whenever you get SQLite3 errors, please provide the separate SQLite log file along with the syslog messages that you've already provided. This separate debug log file includes more details.I tried to reproduce the problem but didn't succeed after a few tries. I'll try to figure it out as soon as possible.
Anyhow, I've got hundreds of SQLite error lines during one of my trials. I'll send you a DM with the error log from spdMerlin and the two debug outputs from the shell script you provided. I believe the logged errors are very related to the loss of configuration and data, and maybe I'll lose them in a couple of hours of automatic speed tests, because of all the errors that have happened.
/opt/share/tmp/
After many hours of troubleshooting, code understanding, fixing, testing, and then doing my very first code commit in GitHub.
Finally, I submitted my very first pull request to the develop branch of spdMerlin script to address the bug of losing the "excluded" mark on interfaces when their status switch between up and down, with a minor improvement to relevant code.
Next, I'll start troubleshooting the data loss issue.. after a good break!
You’re making changes in a project you don’t have write access to. Submitting a change will write it to a new branch in your fork tarek-yag/spdMerlin, so you can send a pull request.
@ExtremeFiretop Thank you for informing me about this.
As this is my very first time making a contribution in GitHub, would you please just tell me where should I start editing the file and in which repo exactly to submit the pull request correctly?
The change right now is in a fork I had to create within my account, as I got told that I have no write access to the repository, so I'm a bit lost, a mini good hint would get me right on track.
Thanks a lot for the big help! I just submitted it successfully!Sure; it can be a bit intimating when you get started.
Let me literally do a "explain it like I'm 5" version and bare with me if I explain something you already knew or have done.
Noted. I expected this by myself when I re-prepared my pull request to be my official first!If you make your changes in your master branch and try to open a pull request against our master branch, it will automatically be denied by our workflow as we don't allow changes from outsiders to go straight to production.
Thanks a lot for the big help! I just submitted it successfully!
I figured out that I was missing the very last step only
User Interfaces get misleading sometimes when you're not very familiar with the environment, I had everything ready earlier even the subject and description of the pull request, I just missed the exact page where to submit the pull request after I left it the first time.
There are too many ways to go through!
Noted. I expected this by myself when I re-prepared my pull request to be my official first!
Well, this is a nice software developing methodology. Good luck everyone on board!
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!