The container image for 24.04 is different from that of 22.04 and 20.04. The 24.04 container includes a "ubuntu" user with a UID of 1000, where the previous containers shipped with only a "root" user. The "ubuntu" user does not have sudo turned on by default.
I also wrote a somewhat similar tool. I call it deep-ast. It's pretty flexible in what it can track. I used it when refactoring some code in urllib3, to see what Exceptions could get raised along a given code path.
Some 3d printers have automatic bed leveling. Which is a process where the printer will touch the print bed in many places with a probe. This allows the printer to detect peaks and valleys, which it can then compensate for. The website above allows you to visualize that data.
I wasn't judging the tools. I use several of them and with 0 complaints.
I'm judging the article for being incorrect about it's specific points and for focusing on a single tool while the alternatives also suffer from the exact same issues.
Did you look at the search results? I didn't see anything resembling the text in any of the search results. I don't think this lines comes from a famous literary source. Likely google just has logic to handle missing whitespace.
> On a previous team I had used Concourse CI to some extent, but I wasn’t really blown away by the experience. Travis and Circle were mentioned. I was a fool. I should have committed to seriously researching some of the contenders and making a more informed decision, but I lacked the willpower and the discernment.
The whole post can be summed up as he had very little CICD experience. Made lots of beginner mistakes, which is easy to do in Jenkins. Then decided to write a post where all his complaints about Jenkins are not only wrong but are the issues that plague all the other CICD tools.
> So instead of writing Bash directly, you’re writing Bash inside Groovy
> The trouble is: Groovy is a much, much worse language for executing commands than Bash. Bash is interpreted, has a REPL that is great for experimentation, does require a ton of imports, and has lightweight syntax. Groovy has none of these things.
Groovy has a language server, linters and a vscode IDE plugins. They are probably not as stable or full featured as the bash ones, but they are available and very few take advantage of them. Again, how is YAML+Bash better?
> The way that developers test their Groovy steps is by triggering a job on the remote Jenkins server to run them. The feedback loop is 2 orders of magnitude slower than it is for just executing Bash locally.
This is a rookie mistake. For about 60-75% of pipelines you can run them locally in a docker container on your local machine. You can even set up hot code reload so as you change your pipeline the Jenkins reloads it. You can also configure the job to kick off a build when it reloads the code. When Jenkins is configured correctly it has the fastest feedback loop of any CICD tool on the market. GitHub actions comes in a close second since it can also be run locally but you cant run a "clone" of what you run in production, like having the same secrets, so it gets second place. Beside Jenkins and GitHub actions, I dont know of any solutions for the other tools.
You can run a GitHub action on Jenkins. It's a very deep and complex system. It's like an iceberg and so many engineers dont leave the surface before deciding it sucks and one of the YAML CICD tools is better. Sure the YAML alternatives are EASY to get started with and to do basic stuff with. But they are Terrible at anything complex. While Jenkins is not easy to get started with, once mastered, you can build complex pipelines with ease.
I get that I'm a Jenkins fanboy. Most of the things I mentioned above, I either contribute to or I'm the author of. I know Jenkins has issues. I know it has hurt lots of people, I read the complaints online. But it's still the best out there. The best software in the world is not written in bash or yaml and the same is true of the best CICD pipelines in the world. It's a shame very few people get to see/use those pipelines.
I'm seeing issues with SSHing into new ec2 instances and getting those new instances to reach apt to fetch packages. I'm using packer. My last successful build was 4 hours ago. This is in us-west-2. AWS service health dashboard doesn't show anything for me.
EDIT: Health dashboard shows all services as green, not that the dashboard is down.
Edit: I had originally wanted to go with something more dramatic like "cython and pyyaml breaks the python ecosystem" but decided on something more realistic. I have never seen a issue get upvoted so fast. In 40mins it had 100+ upvotes. Thought the HN community would enjoy a shortcut to the problem and the work-around fix.
Yeah but ChatGPT can already write Terraform and Cloudformation really well. So this doesn't seem that special besides it's already baked into the pulumi eco system.
> XTS-210 is about the size of a basketball, weighs in at 19 kg (42 lb), and displaces 210 cc.
So you are talking about a 26HP lawn mower.
While the Camry might make more power at its normal size. It would not if you scaled it down to the size of a basketball. I'm guessing it would make 1-3HP at that size.
I got my simple docker files working with podman but my more advanced ones didn't. This was about 8 months ago. After running podman for about 2-3 weeks on my dev machine, I went back to docker.
This gave me issues with my vscode devcontainer setup. You can see my work around here https://github.com/DontShaveTheYak/cf2tf/pull/288/files