Repository navigation
Known issues with DB4S and CI workflow #1688
Description
Activity
- pinned this issue
on Dec 28, 2018 - unpinned this issue
on Dec 28, 2018 @chrisjlocke I'm just wondering why did you unpinn this issue? Is it okay to pin it back again?
- pinned this issue
on Feb 11, 2019 It was probably unpinned because we worked around the Qt issue by changing to Qt 5.11.3 for our nightly builds, and the OpenSSL 1.1 thing also only affects people compiling it themselves too.
The Wifi problem potentially affects more people, so just now pinned it back. Good suggestion. 😄
Reacted by Karim ElDeebI see, thanks.
We should keep this one open and pinned to list the things that are out of our control and things we cannot really fix, but maybe provide a workaround till they are fixed by the affected library.
- changed the title
[-]Known issues with DB4S[/-][+]Known issues when compiling with DB4S[/+]on Feb 18, 2019 - changed the title
[-]Known issues when compiling with DB4S[/-][+]Known issues when compiling DB4S[/+]on Feb 18, 2019 Just removed the WiFi entry, as the fix is now in our most recent release (3.11.1). Also updated the title to mention "when compiling" as both of the remaining issues are developer only items (at this point). Naturally, this can be changed around later depending if/what/how/when/where (etc) new significant issues show up. 😄
Good point on removing the WiFi part since it is fixed now. 👍
I think we should split the first post into two sections; when using and the other when compiling DB4S.
I see that the dark mode/theme does not work as intended. Many issues are opened for that. On macOS and Windows 10, right?
Should this be noted here as well since this is a Qt thing we cannot do anything about, and so that we can close all new issues about it with a link to this issue?
Reacted by Justin CliftOh yeah, good approach. I'm about to get off the computer, so feel free to get that done if you want.
- changed the title
[-]Known issues when compiling DB4S[/-][+]Known issues with DB4S[/+]on Feb 21, 2019 Long time no see... sorry! Anyway I've tried to build the latest git with Qt 5.12.3..
Is this really solved or it's again just me testing it in the wrong way?Oh cool, looks like it might be solved now after all! 😄
- Shouldn't it be on one line, rather than wordwrapped on 3 lines? Guess thats an application option... does that work @gortiz?
7 remaining items
Yes, I think it was just a 'general place' for any issues that were show-stopppers...
Cool, closing this then and unpinning it. 😄
- unpinned this issue
on May 22, 2021 - pinned this issue
on Oct 14, 2022 @chrisjlocke Is there a reason pinned it again? 🤔
Reacted by Chris LockeYes, it was unpinned, but Justin wanted to add to it, and couldn't find it, so I pinned it again, and then he found it, then he edited it. The last part in it is current.
Reacted by Justin Clift@chrisjlocke oh, I got it. Thanks for response. 😄
and one more, how about you think reopen this issue?
@lucydodo Good idea. 😄
Hi @chrisjlocke, Do you mind if I edit the content of this issue a bit?
Our CI workflow sometimes fails. If the CI workflow fails for a particular commit or PR, I can leave a comment on the commit or PR to track and resolve the issue, but the downside is that if it works on a schedule, like a nightly build, there is no place to leave a comment and I have to create a new issue or discussion.
Of course, I can email @justinclift privately to track and resolve the issue when disconnected from our build server,
but otherwise I want to track it together here. 😄@lucydodo You don't need to ask, you're welcome to do it. 😄
Thank you, I was worried it might be rude to edit it arbitrarily. :)
- changed the title
[-]Known issues with DB4S[/-][+]Known issues with DB4S and CI workflow[/+]on Dec 27, 2023
This issue is for tracking all known issues with DB Browser for SQLite (DB4S) and our CI workflow.
It will show you what to expect when using and/or building DB4S. (Include
continuousandnightlybuild)It is meant to let you know that we are aware of these issues, but there are no fixes for them at the moment.
Either because the fix is out of our control (e.g. It is a problem with a library we use and
an issue with GitHub Actions restrictions or polices) or we haven't figured out a way (yet!) to fix them. 😃
Ideas, solutions, and PRs are always welcome.
DB4S (Application-level)
Error message:
The root CA certificate is not trusted for this purpose(macOS only)This is a known (minor) issue on macOS when trying to connect to DBHub.io via DB4S.
We're looking into it, and it's being tracked here: #2829
CI workflow
No known issues 🚀