[Bug]: sqlcipher.dll is broken in nightly installer

[darklie]

[Bug]: sqlcipher.dll is broken in nightly installer

[lucydodo]

@darklie I have pushed the patch to the upstream.
I have confirmed that is works in my environment*. The CI is now live, allowing you to test it yourself once finish the CI process,
If you have the time,we could appreciate it if you could test it. Here's the link for download continuous build:
https://github.com/sqlitebrowser/sqlitebrowser/releases/tag/continuous

Thank you again for bringing this important issue to our attention for our next release. :)

*: Windows 11 Pro Version 23H2 (OS Build: 22631.3155)

[lucydodo]

Thank you for reporting the issue. Upon checking the logs, it appears that the SQLCipher library build is not functioning correctly. As I am currently unavailable due to personal schedule, I will investigate the matter further tomorrow.

https://github.com/sqlitebrowser/sqlitebrowser/actions/runs/8180582970/job/22368898623#step:7:813

[lucydodo]

@justinclift Additionally, we're currently relying on GitHub Actions to build for our next release,
so I add the 'release blocker' label for the same reason.

[lucydodo]

I've identified the cause and fixed it (at least on my local VM). However, this workaround has been problematic when used in GitHub Actions in the past, so I'll be testing it internally before pushing it upstream.

@justinclift The thing is, I need access to our runner for internal testing and it doesn't seem to be working,
Can you check it out if you have a moment? :)

[lucydodo]

Thank you for your confirmation, I can connect runner now.
Let's run some test and try to resolve the issue.

[darklie]

Thank you for @lucydodo and @justinclift !
I tested it this ( https://github.com/sqlitebrowser/sqlitebrowser/releases/tag/continuous ) build and it moves fine.
I appreciate your help.

[justinclift]

Oh, that's interesting. Thanks for letting us know @darklie. 😄

@lucydodo Sounds like this will be of interest to you. 😄

[justinclift]

Cool, thanks for taking a look @lucydodo. 😄

[justinclift]

I need access to our runner for internal testing and it doesn't seem to be working,

@lucydodo Looking into it now.

[justinclift]

@lucydodo Both the M1 macOS VM and the Windows VM should be accessible now. The macOS one looked ok when I checked, however the Windows one had a problem with autossh.

Looks like autossh hit a problem at some point while it was running (router reboot maybe?), and after it couldn't re-connect 5 times it just stopped re-trying.

To hopefully fix that for the future, I've just added Restart=always to the autossh systemd unit file. In theory that should mean it never gives up trying to re-connect.

[justinclift]

Awesome. 😄