Like many things in the US, there's no centralized authority that mandates this sort of thing. Some states have laws around this some don't. For those that don't, some counties or cities might have laws around this. Belgium of course has a stronger central government, small land area, and a small population, so I'm not surprised that something like that would be done country-wide.
The shelter in my city chips every animal before anyone can adopt them. It's honestly bonkers to me why anyone who has a pet wouldn't chip them. It's cheap (especially when considering the cost of a regular vet visit), and can save you from lots of heartbreak later on.
Coloradan with all chipped pets for decades. Not sure where you're coming from. Our friend was reunited with a cat with a chip that was lost for a 6 months. Shitting on the US is great for karma these days
Did your state chip your pet or was it a private company? I think they are saying that there are no centralized authorities and you depend on private companies
That is upsetting for what could almost certainly be run from a SQLite database on a garbage-tier host. Presumably 99.9% of all animals are registered one time and never again queried. Could be near zero operational burden, but of course, capitalism.
Yeah, I moved to the US and I also thought it was weird. Same with vaccination stuff for dogs. You need to carry paperwork if you want to cross the Canada border. It's a throwback to the last century I guess.
> You can't. They can execute arbitrary code. They can download another bash file via Curl and execute that.
Presumably you'd check the code of the action before you include it (and then don't use an action with non-pinned versions). This way you know the action won't execute arbitrary code for this version and won't get any other code because of version pinning.
The docker action you linked is ironic in this regard since every other version in the code seems to be pinned except the one you linked to.
Because PRs with AI need to be reviewed with a lot more scrutiny, simply because AI is good at generating code that looks good, but isn't necessarily correct.
So now you're looking at a PR that at face value looks good, but doesn't reflect the author's skill and understanding of the subject.
Meaning now you shift more work to the owners of the codebase, as they have to go through those verifications steps.
If a person writes 100 lines of code there’s a (valid) assumption that someone thinks this 100 lines of code is worth writing. With AI it takes no effort to write 10,000 loc. Asking someone else to figure out if that code is worth merging just offloads the effort to someone else who didn’t ask for it.
It makes sense, because humans and AI write code different. Because humans aren't AI. The types of mistakes AI writes into code would never be done by a human.
Everything that a maintainer would need to prove to themselves to merge it can be codified in a pipeline.
Or some kind of protocol for building those things in the MR so that any new behavior explicitly demonstrates the new states and transitions.
This is hard if the new MR introduces a completely different paradigm outside the mental model of the reviewer and maintainer. Might be better off completely forking the project and running it in parallel aka taking on the maintainer duties if they feel so inclined to completely change things
In Texas where BCBS is based, the city asked them to re-instate in-office policies, as all those people drive a large amount of tax income in the city.
There is a difference in creating a food that tastes good vs creating a food that tastes good, but instantly wants you to eat the whole bag.
reply