The problem, I believe, is that stable diffusion presently only supports Python 3.10, but Arch ships 3.12, and some of the dependencies aren't compatible with the newer version. Here's what I did to get it working on Arch + AMD 7800XT GPU.
python3.10 -m venv venv
(in stable diffusion root directory)This should be enough for the dependencies to install correctly. To get GPU acceleration to work, I also had to add this environment variable: HSA_OVERRIDE_GFX_VERSION=11.0.0
(Not sure if this is needed or if the value is same for 7900 XTX)
That makes it clearer, thank you. But is this new technology? I always assumed it was the norm. It's possible I'm misremembering, but when I visited Japan over 20 years ago, every house had an AC that could both heat and cool (a necessity since the houses were basically uninsulated and could get quite chilly in the winter.)
I might be a bit confused, but aren't all air conditioners heat pumps? What other mechanism is there?
This was my experience as well as a developer trying to package an application as an appimage. Creating an appimage that works on your machine is easy. Creating one that actually works on other distros can be damn near impossible unless everything is statically linked and self contained in the first place. In contrast, flatpak's developer experience is much easier and if it runs, you can be pretty sure it runs elsewhere as well.
Tämä tuntuu jotenkin kuin olisi suoraan jostain vanhasta scifi satiirista. Eletään maailmassa jossa työnteko vie alati kasvavan osan ajasta. Ihmiset eristetään toisistaan ja sanotaan, että he ovat rationaalisia yksilöitä jotka tekevät vain itsenäisiä päätöksiä. Kanssakäyminen korvataan transaktionaalisilla palveluilla ja muodollisilla rajapinnoilla. Sitten ihmetellään miksi ihmiset ovat yksinäisiä ja ratkaisuksi tarjotaan chattibottia jolle voi puhua ongelmistaan!
If I recall, Enlightenment used to have a rather focal fan base at one time. The DE was a lot prettier than most of its contemporaries, and was relatively lightweight despite having animated effects and everything. I always thought EFL was one of the hidden gems of the Linux ecosystem that was left in GTKs and Qts shadow, but after reading the article (back when it was first published) I realized there was probably a good reason it never got popular. I thought the story was embellished, as thedailywtf articles typically are, with the "SPANK! SPANK! SPANK! Naughty programmer!" stuff, so I downloaded EFL source code and checked. OMG, it was a real error message. (Though I believe it has since been removed.)
The company in question using EFL was (probably) Samsung, who apparently still uses it as the native graphical toolkit for Tizen.
Fyysisten tuotteiden väärennökset vaativat niin paljon henkilöstöä ja infraa, että ne varmasti on monialaisen järjestäytyneen rikollisuuden käsissä. Mutta en usko tuon yleistyvän digitaaliseen piratismiin, jossa sivustojen pyörittäjät ovat yleensä olleet opiskelijoita tai muita tietotekniikkaharrastajia.
Juuri näin. Kun P2P verkot syntyivät, digitaalisesta massajakelusta tuli niin helppoa ja halpaa, että sitä pystyi tekemään vahingossa.
That is a good point to emphasize. A downside of a CLA is that it adds a bit of bureaucracy and may deter some contributors. If the primary concern is whether a GPL licensed app is publishable on an App Store, an alternative is to add an app store exception clause to the license. (The GPL allows optional extra clauses to make the license more permissive.) Though this means that while your code can be incorporated to other GPL licensed applications, you can't take code from other GPL projects that don't have the same exception.
As others have already said, the prohibition of using the code in commercial applications would make the license not open source/free software (as defined by the Free Software Foundation and Open Source Initiative.)
These are some of the most commonly used licenses:
If you want to use a true FLOSS license and your goal is to discourage people from selling it, I'd say the GPL is your best bet. Legit vendors who don't want to give out their source code won't touch GPL code. The non-legit ones won't care no matter what license you choose. Also, iOS App Store terms are not compatible with the GPL so they can't release their stuff there, but you can as long as you hold full copyright to your application.
When I first set up my IKEA remotes, they would sometimes bind to a random other light in the room. This happened when I used the IKEA method of pushing the reset button and holding the remote up to the target light. Not sure if it was caused by touchlink having a lot bigger range than it should have or if it has something to do with how the devices create zigbee groups. For me, this problem stopped happening once I switched to using zigbee2mqtt's own group and binding controls rather than try to pair the remote using the IKEA hub method.
So, check the remote's binding section in zigbee2mqtt console. Perhaps there other device is listed there, or you can try unbinding the default bind group to see if it does anything.
(I just checked, one of my remotes that is presently out of battery is bound to the default bind group according to z2m, even though it shouldn't be. Could be a bug with the IKEA remote where it resets back to a default binding and the plug happens to be listening on the same ID as well.)
@pavunkissa
@sopuli.xyz