Yes, the qemu solution seems simpler and more future-proof than the custom Unifi repository.
Also, my guess would be that few people running Wekan on hardware old enough not to have AVX will have a massively large user base on their installation; most are probably small-time hobbyists like myself, so any negligible slowdowns being exacerbated by scale won’t be much of an issue.
I can already guess the answer to this is ”no, because of how snap works”, but would it be possible for Wekan (installed as a snap) to use mongodb tools already installed on the host system? The reason I’m asking is that I’m running Unifi’s network application on the same non-AVX-capable host, and the installation script for it has added a mongodb repository patched to work without AVX, so that’s already covered.
A tooltip is used to render explanations for terminology when site content is viewed directly in a browser. But feed readers traditionally don’t support styles, and so the content is broken up by the <span class='terminology-tooltip'> elements’ content being shown mid-sentence. For instance, this paragraph in the 2024.10 release post
<p>We also introduce some small YAML automation syntax changes. If you are still a sucker for writing your automations
in <span class='terminology'>YAML<span class='terminology-tooltip'>YAML is a human-readable data serialization
language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration,
for example in the <code>configuration.yaml</code> or <code>automations.yaml</code>
files.<a class='terminology-link' href='/docs/configuration/yaml/'> [Learn more]</a></span></span> (like me), I’m sure
you’ll love these little tweaks that make it all feel more natural.</p>is shown in my feed reader (Tiny Tiny RSS) as:
I’m not sure if this is a recent technical change, or just the first instance of these spans being used, or if I just haven’t been reading the posts that thoroughly, but the 2024.10 release post was the first I noticed this.
I’m on amd64 too, and yep, it’s working just fine after switching to 2024.7/candidate. Excellent, thank you!
Yeah, still not working for me either. Restarting HA snap just results in the same traceback getting logged as before.
Settings > Devices & services > HACS shows it’s up to date (or at least at that same version, 1.34.0). I can’t find a ”Configuration” or ”HACS update” view under the HACS service, only the one with related Service info, Automations and so on (possibly because HACS is ”Not loaded”, which is the issue).
I don’t know if the host system has any bearing on this, but mine is running Ubuntu 20.04, and I’ll happily provide any other info if needed.
Here’s the full traceback I have, unfiltered. It refers to pydantic, and it looks like something people have worked around by forcing pydantic to version 1.10.16. I barely speak any Python at all though, so I wouldn’t know what other implications this has, if any, but I hope it’s at least a clue.
As a workaround, adding --no-warnings seems to suppress this output.
Yup, I can also confirm that v1.67.0-beta.7775.8cb7f28f8.fix-7673-dir-wrapping fixes this!
Ah, apparently ”Show content warnings” on the app is the opposite of what’s ”Always expand posts marked with content warnings” in the web UI. I was confused because the former refers to the warning, whereas the latter refers to the content. There may be minor usability issue there, but I’ll leave it out of this one.
Sorry for the noise. To make up for it, #290 looks like a duplicate of this one and thus could possibly also be closed.
I have ”Always expand posts marked with content warnings” on in my settings, but CW-marked posts in the Android app still show as unexpanded.
I’m fairly sure this used to work until recently, and #87 being closed as ”completed” back in October would imply I wasn’t just imagining it.