Proget docker linux upgrade from v5.3.8 to V5.3.9 issue

[nuno.guerreiro.rosa_9280]

After I attempt an upgrade from the docker Linux container from v5.3.8 to v5.3.9 I am getting the following exception when loading the web UI.
In the docker container logs both for the SQL Server and Proget instance, everything seems to be working fine.

Any idea what might be the issue?

I have just bumped the version and did a docker-compose up.

Message: An error occurred in the web application: Object reference not set to an instance of an object
Stack trace: at Inedo.ProGet.WebApplication.RuntimeLocalizationDictionary.GetCurrent () [0x00006] in <2602fa8c19cc4155be9186cda413e6a1>:0
at Inedo.ProGet.WebApplication.RuntimeLocalizationDictionary.get_Current () [0x00000] in <2602fa8c19cc4155be9186cda413e6a1>:0
at Inedo.ProGet.WebApplication.LocalizationHelpers.GetValue (System.String key) [0x00000] in <2602fa8c19cc4155be9186cda413e6a1>:0
at Inedo.ProGet.WebApplication.Localization+RootPage+FeedsTable.get_Feeds () [0x00000] in <2602fa8c19cc4155be9186cda413e6a1>:0
at Inedo.ProGet.WebApplication.Pages.RootPage.CreateBottomPanels (Inedo.ProGet.Data.DB+Context db) [0x00243] in <2602fa8c19cc4155be9186cda413e6a1>:0
at Inedo.ProGet.WebApplication.Pages.RootPage.CreateChildControlsAsync () [0x00138] in <2602fa8c19cc4155be9186cda413e6a1>:0
at Inedo.ProGet.WebApplication.Pages.ProGetSimplePageBase.InitializeAsync () [0x0006c] in <2602fa8c19cc4155be9186cda413e6a1>:0
at Inedo.Web.PageFree.SimplePageBase.ExecutePageLifeCycleAsync () [0x0007c] in <8a0468ee94a94ef1b2bba97871f29990>:0
at Inedo.Web.PageFree.SimplePageBase.ProcessRequestAsync (System.Web.HttpContext context) [0x00080] in <8a0468ee94a94ef1b2bba97871f29990>:0
at System.Web.TaskAsyncResult.Wait (System.IAsyncResult result) [0x00032] in <b4f0b153c02f4f0588d3f7549d75281b>:0
at System.Web.HttpTaskAsyncHandler.System.Web.IHttpAsyncHandler.EndProcessRequest (System.IAsyncResult result) [0x00000] in <b4f0b153c02f4f0588d3f7549d75281b>:0
at Inedo.Web.Handlers.AsyncHandlerWrapper.EndProcessRequest (System.IAsyncResult result) [0x00000] in <8a0468ee94a94ef1b2bba97871f29990>:0
at System.Web.HttpApplication.async_handler_complete_cb (System.IAsyncResult ar) [0x00015] in <b4f0b153c02f4f0588d3f7549d75281b>:0

[nuno.guerreiro.rosa_9280]

If I open any page like https://www.myinstance.com I get the exception.
If I open any other page like https://www.myinstance.com/feeds it works so it must be a problem with this v.5.3.9 version.

The exception above occurs in the home page but I saw other pages which also throws a similar exception like browsing package versions.
I have rolled back to v5.3.8.

[nuno.guerreiro.rosa_9280]

Any feedback in regards to this issue? It looks related to the new localization feature added on v5.3.9

[rhessinger]

Hi @nuno-guerreiro-rosa_9280,

This is the first time we have heard any issues with this. We also have not been able to recreate this issue internally. Is there anything unique in your ProGet setup?

Thanks,
Rich

[rhessinger]

Hi @nuno-guerreiro-rosa_9280,

We have finally been able to recreate this issue in our sandbox. We are currently looking into a fix, but we expect to have one in the next version of ProGet, 5.3.10. This looks to be an issue with the mono framework. We use mono runtime in our Docker images for ProGet. We are also going to be releasing a .Net Core based technical preview of ProGet Docker in version 5.3.10. This will be in addition to our standard mono based version. Our internal testing is going very well and it looks to have removed a lot of the gotchas that mono has.

Thanks,
Rich

[nuno.guerreiro.rosa_9280]

Thank you for the support. Looking forward for the fix.

[atripp]

@nuno-guerreiro-rosa_9280 just to let you know, as part of ProGet 5.3.10 release, we shipped the ProGetCore container image as well.

You can follow the normal steps in the Linux and Docker Installation Guide to install/upgrade, but just use progetcore for the container instead of proget.

Aside from support for the Lucene-based Maven feed indexing (in progress), it seems to be feature complete. And of course, if there are problems, you can switch back to proget:5.3.10 or downgrade as needed (no database schema changes).

For example, docker pull proget.inedo.com/productimages/inedo/progetcore:5.3.10

[nuno.guerreiro.rosa_9280]

@atripp I will try the progetcore when I manage to have some time but I can confirm the issue I reported was solved in proget v5.3.10. Thank you.