-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node.flashreload() Not Working #3251
Comments
There was changes introduced. Do you use Gitter? If yes, please check it. If not: |
Ok... this works but what about all the other functions related to old method like...... node.flashindex() etc. for k, v in pairs(node.LFS) do print(k,v) end |
I had the impression that we wanted to deprecate this which should add a deprecation warning, printed on usage. So this should work as it used to. |
It should work for backwards compatibility, I don't mind having a deprecation warning in the documentation, but when did we agree that any deprecated function should print a warning on usage. This can change the behaviour of a legacy app. Before we adopt this as a policy, I feel that we should debate and vote on this. |
I would prefer to have the "Do all deprecated uses print a usage warning as a separate policy issue. Gregor, feel free to open this if you want the discussion. |
We have been doing this for years through a dedicated function in
We first add add a call to |
I know that, but there is a difference between a facility that may be used when appropriate and one that is mandatory. An LFS app might do 10s or even 100s of index lookups per sec. Adding this deprecation note could cause major timing problems and even timeout to a working app. The old none-object forms of timer and file were similarly deprecated. Adding a mandatory deprecation note to these would be similar insanity. |
@TerryE Terry, true that flashindex may be called quite often, but flashreload usually will not be called that often. So I see this issue as valid. |
OK, I will add the deprecation warning to flashreload on the next set of updates. |
The problem is not only the deprecation warning, but that you seem to have removed the flashreload command entirely. |
@HHHartmann, not sure how this happened. It's a 1-liner to put back. |
Ok. I can do it, just didn't want to cause merge trouble for you |
|
@marcelstoer I know when it happened. That was a big change: 75 files changed with 1,644 additions and 776 deletions. The new line |
@HHHartmann Gregor, on reflection, I will add this to #3272 because I also want to add #3145 at the same time. We need this for on ESP LFS maintenance. |
Gregor wanted to have this fixed before the next master drop. I support that. |
Done. See 41c5f8f |
The good thing about PRs is that we sometimes spot issues before they land 😜 |
Marcel, OK. Thanks for pointing this out, but fixing it would have just been as quick. I've now corrected this, d88c14b, and I will do a two stage PR / merge in future. |
To fix nodemcu#3251.
The text was updated successfully, but these errors were encountered: