DM claims no updates available, file system says otherwise

[snomos]

According to DM, Inari Sámi is at latest nightly build:

But according to zsh, that is not the case (cf second last line):

-rw-r--r--  1 root  wheel   5276913 Oct  8  2021 /Library/Services/fo.bundle/Contents/Resources/fo.zhfst
-rw-r--r--  1 root  wheel   3165554 Nov  8 16:13 /Library/Services/kl.bundle/Contents/Resources/kl.zhfst
-rw-r--r--  1 root  wheel    104212 Jan 29 15:51 /Library/Services/lut.bundle/Contents/Resources/lut.zhfst
-rw-r--r--  1 root  wheel   3757014 Feb 21  2023 /Library/Services/mhr.bundle/Contents/Resources/mhr.zhfst
-rw-r--r--  1 root  wheel    695254 May  3  2023 /Library/Services/mns.bundle/Contents/Resources/mns.zhfst
-rw-r--r--  1 root  wheel    928493 Aug 31  2023 /Library/Services/mrj.bundle/Contents/Resources/mrj.zhfst
-rw-r--r--  1 root  wheel   1499132 Sep 21  2022 /Library/Services/nno.bundle/Contents/Resources/nn-Runr.zhfst
-rw-r--r--  1 root  wheel   1515258 Sep 21  2022 /Library/Services/nno.bundle/Contents/Resources/nn.zhfst
-rw-r--r--  1 root  wheel   1390961 Jun  1  2023 /Library/Services/olo.bundle/Contents/Resources/olo.zhfst
-rw-r--r--  1 root  wheel  18941111 Jun  6  2023 /Library/Services/se.bundle/Contents/Resources/se.zhfst
-rw-r--r--  1 root  wheel   4737921 Sep 25  2023 /Library/Services/sma.bundle/Contents/Resources/sma.zhfst
-rw-r--r--  1 root  wheel  16927782 Jun  1  2023 /Library/Services/smj.bundle/Contents/Resources/smj.zhfst
-rw-r--r--  1 root  wheel  16336078 Jun  1  2023 /Library/Services/smj.bundle/Contents/Resources/smj_NO.zhfst
-rw-r--r--  1 root  wheel  16286721 Jun  1  2023 /Library/Services/smj.bundle/Contents/Resources/smj_SE.zhfst
-rw-r--r--  1 root  wheel   9990111 Jun  6  2023 /Library/Services/smn.bundle/Contents/Resources/smn.zhfst
-rw-r--r--  1 root  wheel  23269745 Sep 26  2023 /Library/Services/sms.bundle/Contents/Resources/sms.zhfst

In fact, all installed .zhfst files are from last year or older (except one from January this year), while DM claims they are all update to within the last couple of days for most of them.

So something seems seriously wrong with the automatic update system. I reinstalled DM to the latest version available in the stable branch (at divvun.no).

[snomos]

I also tried the newest nightly build of DM, with. the result that it could not contact the Páhkat repository, even after several restarts of DM.

[dylanhand]

I also tried the newest nightly build of DM, with. the result that it could not contact the Páhkat repository, even after several restarts of DM.

I've seen this issue as well. It seems intermittent and often happens after initially working upon first launch.

In case it's helpful while I'm investigating, I've found that reinstalling Divvun Manager is a reliable way of getting it to load.

[snomos]

I tried reinstalling, and it didn't help. The issue is not that it doesn't get contact with the repo server (that happens as well, but that is, as you say, intermittent, and can be solved after restarts or reinstallation), but that it is lying: it claims the newest version is installed, but the file system and actual behaviour of e.g. spellers tells a different story (the true story).

Lying is one thing, but failing to actually update is the major issue here (and lying is just a symptom of the other problem).

[dylanhand]

I tried reinstalling, and it didn't help. The issue is not that it doesn't get contact with the repo server (that happens as well, but that is, as you say, intermittent, and can be solved after restarts or reinstallation), but that it is lying: it claims the newest version is installed, but the file system and actual behaviour of e.g. spellers tells a different story (the true story).

Lying is one thing, but failing to actually update is the major issue here (and lying is just a symptom of the other problem).

Sorry I wasn't more clear. In my experience, reinstalling usually fixes the issue where DM hangs and does not load the list of packages.

It does not fix its lying that there are no updates when in fact there are.

[dylanhand]

@snomos have you found a reliable way to reproduce the bug where it does not connect/the UI does not refresh?

I've been messing with the app for a while now and haven't been able to reproduce the issue.

[snomos]

Unfortunately no. I have had reports from others earlier, but with a working system myself, and the whole issue is very strange.

What I can offer now is a Mac (my Mac) that has this issue, and a person willing to spend time in debugging this (me). So chances are a bit better to find the issue, although it won't be easy.

[snomos]

Could it be related to stale caches or something? Where is the pahkat cache on macOS?

[dylanhand]

Ok 😄

Any information you can provide will be helpful. I've seen this issue before but of course now that I'm trying to debug it, it refuses to present itself.

Not yet sure where the caches are kept. I've spent some time today going through the code to see how the pieces fit together but it's not crystal clear.

[dylanhand]

@snomos is this not a duplicate of #32?

What it sounds like is happening, is that the latest stable version of the package is installed, so DM is not offering to overwrite it with the nightly version.

It sounds, based on #32, that the way this is expected to work is that if a package is installed via the stable channel, switching to the nightly channel will not indicate an update is available, but instead should show that the latest version on the stable channel is installed. Is that right? Can you confirm which way you initially installed the package (stable/beta/nightly)?

Put another way, if I'm interpreting #32 correctly, my understanding is that the result you're seeing is correct in that it does not offer to update to the nightly version (assuming package was not initially installed via nightly channel), but it is incorrect in that it doesn't indicate you're running the latest stable version.

[snomos]

A very good point, and indeed you are probably right.

At the same time, it illustrates the problem:

Can you confirm which way you initially installed the package (stable/beta/nightly)?

No, I can't reliably, because there is no way I can tell which channel was used to install a given speller. Also the easter egg with version info does not give any clue as to whether the speller was built using nightly, beta or stable.

BUT given the 1.1.1 git tag and its date, it looks likely that my Faroese speller (which I tested right now for the purpose of this bug) was installed using the stable branch. So it looks like you are correct.

And yes, DM should only update installed packages using the same channel as when it was first installed: nightly installs are updated through the nighty channel, beta installs using the beta channel, and stable ditto.

That is, we need to fix #32 ASAP, to end this confusion. For both Windows and Mac.

[dylanhand]

Ok thanks for clarifying. I'll begin looking into #32.

[dylanhand]

Upon further inspection, there actually was a bug with this issue's description that affected nightly packages.

The bug prevented a nightly with the same version, but a more recent timestamp, to be installed.

This is fixed in the latest nightly version.