Nossie wrote: ↑Mon 14 Oct 2024 11:12 pm
Hi Hans,
I've done a little digging and asking around a few docker people and ...
Running the app in a container vs a vm/server isn't much difference. If you have the issue I'd bet it's happening if you used a vm as well.
Remember that there is nobody else who has this issue (others are running Windows or Linux). Not sure of anybody running this in vm.
Nossie wrote: ↑Mon 14 Oct 2024 11:12 pm
It's something code wise that's causing an issue, it sounds more like a weird race condition that's happening
A race condition... see
the wiki.
If true, could be related to the next point.
Nossie wrote: ↑Mon 14 Oct 2024 11:12 pm
Main.cs line 343 may be line above it that's the issue
See screenshot:
Schermafbeelding 2024-10-15 082259.png
Nossie wrote: ↑Mon 14 Oct 2024 11:12 pm
To be honest, race conditions are above me Hans but do you mind telling me what's above line 343?
What is happening in line 343 is that it creates the main thread to run the different modules as asynchronous tasks. A
relatively simple explanation of asynchronous programming is given here.
It could be some timing issue related to the usage of async but because it used to work on your system and the only thing which has been added is the SQLite libraries (which reside in the runtimes) the problem must be related to those. And that leads me to the remark that the diary module is NOT (currently) run async. It may in future.
Afaiac, these remarks are guesses and I do not see a reason why any of the remarks should be valid without additional proof.
I'll think about proving a timing point.
Anybody with a suggestion is invited to propose something!
You do not have the required permissions to view the files attached to this post.