In non-minimal changesets, I would miss information/documentation about individual logical changes that make up the changeset.
It’s usually possible to find this by navigating back to the PR which you can find referenced in the squash commit.
I guess this might be a larger problem for codebases not following a trunk-based approach, where PRs grows to very large sizes before going into the mainline branch.
Have the gooners gone too far and why is the answer yes?
Slap on a zero.
Also, minimum billing is in increments of 1 week
You know macOS ships with a terminal ootb, right? There’s a reason it’s a massively popular option for devs.
I mean, I’d probably do it server-side even if I were to have nefarious intent and want the data for myself anyway, since image processing client-side isn’t necessarily a good use of your users devices, really.
Plus, if I were to want the data in a client-side, I could upload it before doing the client-side stripping.
This comment doesn’t really hold up to scrutiny, my friend
That’s where their 5-7 year support window
This is one of the worse scams that Apple perpetrate with iOS admins iPadOS - yes, the devices get updates for as many years as specified. However, basically all apps available for iOS and iPadOS only support the two latest versions of the OS, meaning that once your device is out of support, it functionally becomes a brick after one year, as no apps will support it anymore.
Android has a worse record of keeping the OS up to date on devices, but app developers on Android routinely support 10 or more versions back of the OS, making this problem less severe.
I mean, assuming the republicans ever lose power, why should any of the conventions of the past be upheld? Why should not every single judge appointed by the republicans be removed from their positions?
Trump has shown you that the rules don’t matter when you are in power, fucking learn the lesson already
As I understand it, Google mostly ships new stuff that they let die because it’s one of the only ways to get a promotion at Google - to ship a product.
Once shipped, the newly promoted staff moves on to something else, and the business people take a look and see if the product actually makes any sense from a financial perspective, which is rarely the case.
You don’t need to be a peak tech literate person to have been able to accomplish this.
The level of neglect of security that was involved when creating that app should really be criminal. Door was left wide open for anyone to walk in a take a peek
SSL is not the tool you need in this case, although you should obviously already be running exclusively on encrypted traffic.
The problem here is one of access rights - you should not make files default-available for anyone that can figure out the file name to the particular file in the bucket. At the very least, you need to be using signed URLs with a reasonably short expiration, and default all other access to be blocked.
Are you under the impression that this will pay any artist anything?
It’s fine to take a pro-piracy stance, but pretending that you’re doing it out of concern for the artists is grade A-bullshit.
Hey, I’m not saying I don’t stand with the gooners, take that back
Union of concerned gooners rising up
Language models are unsuitable for math problems broadly speaking. We already have good technology solutions for that category of problems. Luckily, you can combine the two - prompt the model to write a program that solves your math problem, then execute it. You’re likely to see a lot more success using this approach.
uBlock Origin with the appropriate filter list will do it for you, like this one: https://github.com/DandelionSprout/adfilt/blob/master/LegitimateURLShortener.txt
I don’t think OpenAI maintains any data centers, they run all of their stuff on Azure.
Dude really is hilariously pathetic isn’t he
Millions of people suffer from the debilitating condition of being British, we need an awareness month
That kind of commit quality should only really be permissible on private projects, and as a reviewer, it’s arguably acceptable to reject PRs with this kind of history.
You should be writing your commits to the benefit of the code reviewer - structure them in a logical fashion to tell the story about the changes you want to get merged.
For non-trivial branches I usually soft reset to the point where all code is unstaged and uncommitted and then curate the commits to align with what the reviewer should be reading. It’s not uncommon for me to have several branches containing a single “wip”-commit which I amend onto while building up the full code for the branch.