Conversation
When the plugin list matched the MD5 (which it hasn't done for a while due to a server side issue with the MD5 not being correct!), it would always fail. The server side issue was corrected, which manifested this issue in the code. Also, the DEV list MD5 URL wasn't used when the DEV list was selected.
| if (downloadResult && serverMD5 != cHashBuffer.get()) | ||
| if (downloadResult && serverMD5 == cHashBuffer.get()) { | ||
| // Server hash matches local hash, so we're ok to continue | ||
| downloadSuccess = TRUE; |
There was a problem hiding this comment.
This is the actual fix. If the hash matched with the server, it would error later.
There was a problem hiding this comment.
And I already wanna suggest to add a checksum onto the complete list to avoid unnecesary downloads but it seems this was already there.
Could we also find out that the downloaded list is corrupted? Like seen in my post to #57, where it just contained the HTML error page, no xml?
|
Wow, just wanna comment on it, but you were too fast. Would have been:
How could the issue be explained for the standard list as mentioned in the answer of #57? That one I'm not facing. Could you also have a look at: Mem leak according to cppcheck. |
|
I've changed the server hash and cleared the caches, so it won't be an issue now. There's very aggressive caching on the prod instance, so it wouldn't have kicked in until all the edge caches have the updated hash which matched the contents. It was only when we updated the list to v1.4.5 that the server md5 issue was noticed and fixed, which triggered this issue (just slowly, because of the caching) |
|
Good catch CPPcheck :) I'll push it in a separate PR. |
|
It doesn't seem to be fixed. Just did a fresh install of Notepad++ and added Plugin Manager (shame you have to do it yourself nowadays), but Plugin Manager is not able to get the plugin list. |
When the plugin list matched the MD5 (which it hasn't done for a while due to a server side issue with the MD5 not being correct!), it would always fail.
The server side issue was corrected, which manifested this issue in the code.
Also, the DEV list MD5 URL wasn't used when the DEV list was selected.
This is the fix for #57