Comments (6)
FYI: I'm assigning a high priority to the next release coming next week.
Therefore, this improvement will be attempted after the release the next stable version.
from sqlitebrowser.
Ah, I understand perfectly. As you said, I will make that test it on a Runner image without Qt installed. :)
from sqlitebrowser.
Maybe some kind of automated "does the application start?" test after every build?
It'd need to be done in a separate container/vm/something than did the build though, to make sure having the development libraries installed on the same system doesn't give a misleading result.
Have seen that exact problem happen with Qt libraries, where testing on the build system itself can hide packaging problems.
from sqlitebrowser.
Can you elaborate a little more? :)
from sqlitebrowser.
Here's how I was originally thinking of doing it.
Run a GitHub-hosted runners with multiple OSes simultaneously as a matrix.
And run the following (pseudo-code) script:
run sqlitebrowser
if (exit_code == 0)
success
else
fail
from sqlitebrowser.
Yeah, that approach sounds like a decent idea. 😄
Can you elaborate a little more? :)
Yep. At least on macOS, if you compile an application with the Qt development pieces already installed then the various paths (eg PATH
, LD_LIBRARY_PATH
, (etc)) of the development libraries can give misleading results.
For example, when a person installs then runs DB4S on their standard macOS computer it'll try loading the Qt libraries from inside of the DB4S package installed under /Applications
.
If the DB4S package was accidentally made badly (ie bug during packaging), then the Qt libraries in the package might not actually be present, or might be present in the wrong sub directory (etc). When the user tries to launch it, an error will be generated and the user will commonly let us know there's a problem to investigate.
Now, if that same broken package is instead launched on a computer that has the Qt development libraries installed, then it wouldn't immediately fail if the Qt libraries are missing from the package. Instead, it'll use the Qt libraries from the Qt development install then launch as per normal.
So, it'd look like DB4S was working as intended and the package was all good. Except it's not.
So doing testing of the DB4S packages on the dev system they're built on isn't a foolproof test, and your approach of doing the tests in a matrix (ie new VM per OS test) is a good one that sounds like it'd avoid that problem.
Hopefully the above makes sense. Only mentioned it due to hitting this exact problem when originally creating some of the macOS packaging scripts. 😄
from sqlitebrowser.
Related Issues (20)
- [Bug]: SELECT sqlite_version() crashes the app HOT 7
- [Feature]: Right click option - Copy with regex
- [Bug]: Can't open rc2 on macOS 12.7.5 HOT 8
- [Bug]: DB4S crashes and the project file contents lost HOT 15
- [Bug]: Copying data to clipboard takes too long HOT 9
- [Bug]: Plot Selections Forgotten
- [Bug]: Recent Win32 nightly zips are corrupted HOT 4
- [Feature]: Suggestions/minor problems with current dark theme HOT 8
- [Feature]: Time Detection / Converter Plugin for SQLite db files.
- [Feature]: Chrome History - Page Transition Types HOT 3
- [Bug]: Plot legend crops text with high res display. 3840 x 2160 Windows 11 NVidea HOT 1
- macOS 15 Sequoia Compatibility Check HOT 1
- [Bug]: Force Read/Write with Save Database As HOT 4
- [Feature]: Open zipped databases OR add support for creating a zipped db HOT 1
- [Feature]: use relative path in project settings HOT 2
- [Feature]: Highlight line of selected cell in Browse Table view
- improving Bidi
- [Bug]: all agregation functions do not work on large tables (including group by and order by) without limiting row count in sub query HOT 1
- [Bug]: Tiny icons for UI elements in 3.13.0-rc1 on Windows HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sqlitebrowser.