You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I started auto update prompted by notepad++, initially it showed a very huge value for percentage completion.
In my case, I was updating from 7.5.1 to 7.5.4.
Snapshot attached.
It seems to be a divide by zero sort of issue.
There must be a minor change that needs to check for the new installer size and use it when more than 0 or something similar. or possibly at the time of % calculation the installer size was not initialized(?).
Steps to Reproduce the Issue
Update from 7.5.1 to 7.5.4. This may possibly also apply for any update or from any version to 7.5.4.
Expected Behavior
The installer percentage should start from 0%.
Actual Behavior
Initial installation percentage was 9223372036854775808%.
Debug Information
Notepad++ v7.5.4 (64-bit)
Build time : Jan 1 2018 - 01:50:29
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 10 (64-bit)
Plugins : DSpellCheck.dll mimeTools.dll NppConverter.dll
The text was updated successfully, but these errors were encountered:
Description of the Issue
When I started auto update prompted by notepad++, initially it showed a very huge value for percentage completion.
In my case, I was updating from 7.5.1 to 7.5.4.
Snapshot attached.
It seems to be a divide by zero sort of issue.
There must be a minor change that needs to check for the new installer size and use it when more than 0 or something similar. or possibly at the time of % calculation the installer size was not initialized(?).
Steps to Reproduce the Issue
Expected Behavior
Actual Behavior
Debug Information
Notepad++ v7.5.4 (64-bit)
Build time : Jan 1 2018 - 01:50:29
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 10 (64-bit)
Plugins : DSpellCheck.dll mimeTools.dll NppConverter.dll
The text was updated successfully, but these errors were encountered: