elischleifer

We happen to build the perfect solution to avoiding GitHubs Merge Queue - ours :)

It’s also massively more performant

https://trunk.io/merge-queue

Of all the things Amazon brings to the marketplace - global surveillance is not one I would advertise on the superbowl.

"The less polished and coherent something is, the more value I assign to it." - maybe a bit of an overstatement ;)

100% - targeted advertising lives and breathes on data - this is par for the course

This headline could be written about every major social network on our planet. Tracking pixels are not something TikTok invented.

Detection of copy-pasta is interesting - what it's calling out is not a deficiency in LLM's to code but in agentic rules in place that should just remind the agent to refactor into a common function when appropriate.

We already are performing our own unintentional form of geo-engineering with our relentless pumping of CO2 into the air. That said, not sure blocking the sun is our best plan right now for avoiding the worst of climate change. Instead of trying to have our cake and eat it too, we need to accelerate our focus on reducing carbon output, decarbonize electricity and transportation, and invest in massive amounts of energy production to the point where energy is so cheap we can use it to pull carbon from the air.

fair point. I think I've just been burned too many times by dependabot looking to update single ts packages with single line changes. it's default configuration is overly aggresive

Working at Microsoft back in the early 00s I spent a lot of unfriendly hours with windbg. On one particular project we hunted for a terrible crash for months until it was uncovered that we were compiling against the single thread CRT when using threads extensively...whoops

Just another reason not to use dependabot - it's default configuration appears to be created to burn money on GH Actions / Azure.

The security breaches be damned - the UI was terrible / constantly prompted me to store credit card info in LastPass and I was just not interested...but couldn't get it to stop this. deleted and moved to Dashlane.

better and better visuals....still looking for a killer app.

This is amazing. Not interested in growing vampire teeth - but the ability to regrow teeth when lost - or get a new set of chompers without coffee stains sounds super cool :)

Another tool that tackles GitHub Action debugging head on: https://www.ci-debugger.io/

Wrap your GH Actions in a debugger breakpoint and connect into the live broken GH Action to inspect the machine, re-run commands etc..

At it's heart - realtime debugging for GitHub actions.

Fisherman's Wharf is the most not-San Francisco part of SF. You know if there is a Hard Rock Cafe that you are not really where the locals dine.

Time to short the makers of Goo Gone?

Devil's advocate...how much do we really care about these different distros at this point. The world lives out of the browser. As long as I have chrome and VS Code I'm pretty good to go.

Founder here. Debugging CI pipelines is a pain and it often feels like a slow, unproductive printf() debugging process. All of us who have gone through the tedious cycle of run->fail->log->fix->run->fail-> can attest to the massive waste of time it creates.

To change this, we built Trunk's CI Debugger. We initially built this for Trunk because we found that CI jobs were not stable and took multiple hours to track down the root cause of failure. The debugger gave our team a way to add conditional breakpoints, receive alerts on and debug our CI like you do your code.

You can see how this works for GitHub Action in our repo: https://github.com/trunk-io/breakpoint, but it works with any CI system you use - Jenkins, GitHub Actions, Buildkite, Circle CI.

To get started, check out our CI Debugger in the link above. We learned a ton building this tool, and I would love to hear your feedback and answer any questions you might have. Here's to making the debugging process in CI systems as seamless as it should be.

Feels like after the log4j situation - the naming convention of XforJ would be a bad omen.

Stay safe east coast. I remember a couple years ago when the sun was just gone from San Francisco.

No surprise here. This business has crazy high costs and the marginal value is just not there. Subscription businesses in consumer are brutal.

Great question. The magic is in the dynamic nature of the breakpoint triggering. If you want to SSH into a CI machine you need to know ahead of time that you want to investigate that machine and pause execution while it's going.

With the debugger, you set conditional rules like - 'if this fails - then trigger debugger and hold machine' - instead of trying to catch lightning in a bottle - it waits for you.

More details and sign-up here https://ci-debugger.io

Is someone in danger and you need the answer to this question? blink twice if you're in trouble.

Unregulated currency markets are a danger to a well functioning economy. We know that without regulation abuse will occur, it always does. It's about time that crypto, whatever magical value you want to ascribe to it, is regulated like other financial instrucments.

It's not just about the visuals - its about how the data can be sliced and diced. How your pull requests behave is a very different phenomenon than from how your main branch is behaving. You need to be able to tease this apart easily.

I would say that broadly the ergonomics of the product are where it is most differentiated. Datadog's solution - feels very much like a datadog product - in that it's a giant dump of data you have to craft to tell a story. Not all pipelines are the same, their execution patterns are different and expectations for Pass/Fail/Cancel differ as well.

shockingly it doesn't