Yeah, that's the type of thing I was wondering about. Some weird chemical type thing or something that does damage over time. I haven't been worrying about it too much, but figured I should probably at least check before I knock too many canned meals back.
And yeah, this is metal cans I'm talking about.
For the microplastics, I guess I'm not too concerned with this if I can't avoid them anyway.
I forgot to mention that I also eat a sandwich or something with the canned food meal. Like peanut butter and jelly or something. And about the salt content, I rinse both the beans and vegetables off before I mix them. I'm pretty sure there's little to no salt left at that point, because I don't taste any.
They do have a robust testing process, but their main focus at the CentOS Stream stage is more about preparing for the stable RHEL build than it is about adding a ton of new features and bug fixes. Testing takes time so it would be physically impossible for them to test everything if they didn't have a limit on the type of contributions they accept. For bug fixes, their limit is that the bug has to be critical. For bugs lesser than that, the correct place to contribute those fixes is in Fedora.
That has been adequately explained in the merge request at this point, if you click in that link at the top of this thread amd read through it to get the latest info. The Red Hat devs have also made no indication that they're not welcome to contributors. Anyone who's saying that is blowing this merge request issue out of proportion.
I'm getting downvoted because I'm not conceding that the miscommunication was a legitimate excuse for that blowup. And I'm going to continue to not concede that. I found this whole situation to be embarrassing, and I think instead of getting mad at the miscommunication, you should all be getting mad at the moron who took that screenshot and whipped up the mob frenzy to swarm that merge request, because ultimately Red Hat was 100% justified in not accepting that merge request, and it made you all look like morons.
It's fine to get mad on social media, but if you're contributing to GitLab or someplace else, then you need to slow your roll. There's always a process involved when contributing to a project, and you have to learn that process in order to contribute effectively. You can't blow up and whip up a social media frenzy at the slightest inconvenience.
Edit: Sorry, @angrymouse@lemmy.world. I should also add that I'm not mad at you personally or anything, or calling you a moron. I'm more talking about the collective response to this situation. And I'm pretty bad at words, so I feel like I accidentally made it too angry.
I'm getting downvoted on my comment about not making a comment on CentOS, so now I feel obligated to reply to this.
I don't know, dude. I don't really care about the miscommunication. I was just focusing solely on the merits of the merge request's code changes.
For the miscommunication, it seems like a two way street to me. That was GitLab, so the Red Hat dev was probably operating under the assumption that people there already understood everything about their testing process. But obviously that's not the case, so Red Hat should create better boilerplate responses for these scenarios. But on the other side of the coin, whoever took this screenshot and posted it to reddit or wherever did so prematurely, imo. They should've asked around a bit to make sure it was a legitimate thing to blow up about before they sent a lynch mob to the merge request.
CentOS Stream is the staging ground for RHEL. It isn't a bleeding edge distro that can accept any merge request willy-nilly. For the reason why, reread my original comment about the nature of enterprise support.
Fedora is the distro that is more bleeding edge in the RHEL realm. This merge request was more suited for Fedora, and the fix was successfully applied to Fedora. So, I fail to see any irrational actions from Red Hat here.
I'm making no comment on CentOS being absorbed and repurposed by Red Hat. I'm just saying it makes sense why Red Hat would rather have this fix in Fedora than CentOS Stream.
CentOS Stream is midstream of RHEL and Fedora. That sounds like it's like a cert type of environment for RHEL. The same logic would apply there. You don't want to be introducing a bunch of new changes to code once it's in the cert environment unless they're critical.
I haven't been really keeping up with this RHEL drama, so I'm probably going to regret making this comment. But about this bug merge request in particular, you have to remember that RHEL's main target audience is paying enterprise customers. It's the "E" right there in RHEL. So stability is a high priority for their developers, since if they accidentally introduce a bug to their code, then they'll have a lot of unhappy paying customers.
The next comment that was cropped out of that screenshot basically explains exactly that. While the Red Hat developers probably appreciate the bug fix, the reality is that the bug was listed as non-critical, and the Red Hat teams didn't have the capacity to adequately regression test and QA the merge request. But the patch was successfully merged into Fedora, so it will eventually end up in RHEL through that path, which is exactly what the Fedora path is for.
The blowup about this particulat bug doesn't seem justified to me. Red Hat obviously can't fix and regression test every single bug that's listed in their bug tracker. So why arbitrarily focus on this one medium priority bug? if it were listed as a critical bug, then yes, the blowup would be justified.
I'm still working my way up to listening to symphonies. I've mainly been listening to sonatas, concertos, and things like quartets and stuff. But of the few symphonies I've listened to so far, that's one thing I noticed. They reminded me a lot of all the movie soundtracks I've heard throughout my life.
It sounds stupid since soundtracks are commonly played by a full orchestra, so what else what they sound like. But I just never made that connection before that they're basically modern day classical music haha.
That's a good idea though, thanks! I'll mix in some soundtracks to my classical music exploration.
My lifestyle is unhealthy and would most definitely benefit from therapy. But that disclaimer aside, I have a few things I find happiness from. Listening to music is a big one. Over the past year or two I've transitioned to listening to mostly classical music, so I have a whole new world to explore in that genre. I'm currently listening to a lot of Shostakovich. Another big source of happiness is continuing to learn about programming. That's kind of like a ritual that I've maintained since my school days. And one of my guilty pleasures recently is those stupid reaction YouTube channels. Not the obnoxious ones where they're all like "WoaaaAAaa!!1" or whatever. But just regular people watching comedic and music things.
I know about two forms of meditation: mindfulness meditation and transcendental meditation. They're both pretty much exactly the same, except in mindfulness meditation, you focus on your breath traveling through the tips of your nostrils, and in transcendental meditation, you focus on a sound/word/phrase in your head.
This guy explains transcendental meditation really well. If you want to try mindfulness meditation, then just change his instructions to focus on your breath instead of a sound, and keep the rest of the instructions exactly as they are: https://youtu.be/nBCsFuoFRp8
One thing to note is that there's transcendental meditation, and then there's Transcendental Meditation™. They're the same exact thing, except with with transcendental meditation, you pick whatever sound you want, but with Transcendental Meditation™, you pay $1600 to have some dude sprinkle a bunch of essential oils or some shit on you and pick your sound for you. Plus, who knows what kind of recurring hidden fee nonsense you're signing up for, so I suggest avoiding Transcendental Meditation™.
Yes, it's a safe bet that it's just my current job. I was a lot happier at a previous job with a government contractor that was very low stress. I'm going to start applying for new dev jobs.
I'll most likely stay in the dev field because it's the path of least resistance for me, and because the job security most definitely shields me from a lot of new stressors I'm probably not even aware of. But I still wonder sometimes what it would be like to have a job outside like that one guy who said he became a wildlife ranger. Or to have a job where you solve physical problems with your hands, instead of abstract problems with your brain.
Cool, thanks for the update! Coincidentally, Liftoff put gestures with no option to turn them off in their latest release, so I've been a little unsatisfied about that. I'll try Thunder again.
The play store release is a huge deal too. Ngl that I probably wouldn't have used Thunder if I had to manually update it from github for each new release.
yarn @ yarn @sopuli.xyz Posts 7Comments 78Joined 2 yr. ago
Thanks for the alternatives ideas. I should try to mix up my "cooking" game a little, just to get a little more variety in my diet.