Go ahead and try and mow that after its flopped over. Mower is going to choke with how much grass you are putting into it. You may need to weed wack it down and rake or blow it out before you can mow.
There's a fine line between large modifications to existing infrastructure and "new stuff". You need a handyman you can trust in order to know the difference.
It also depends on your insurance situation. If I'm doing renovations, my house insurance company will not honour my insurance if the work is being done by a contractor without knowing the insurance status of the contractor.
One thing to consider is whether there is a reasonably-priced "emergency contractor" service to which you can subscribe. Enercare in Toronto offers plumbing protection for $21/mo and electrical protection for $16/mo. Service calls — 24 hour service calls — are included and covered in the plan, and labour for fixing the problem is included. We've had multiple cases where we've needed to call a plumber out to look at issues and it would have cost ~$200 to get them in the door and more than $400 by time the work was done. We've also used them for discounted plumbing work (15% off labour and most parts) in the past when we didn't have a different contractor for something we needed done.
They also designed with cheap shells that felt loose before a year was out, and offered exactly zero water and dust protection so if your device got wet, it was considered out of warranty.
That's at most 1/10th the cost of the average Samsung phone.
That's cheap. If you think that a safe first-party replacement battery will sell for less than the 79€ that the whole replacement effort takes, then you're fooling yourself.
I strongly suspect that there's also not good language for blocking against third-party batteries (and the phone manufacturers would have good reason to do so because it might result in overheating or worse with really bad third-party batteries).
you are right. thats cursor-agent (the CLI), not the Cursor IDE. CodeBurn only parses the IDE's state.vscdb right now. cursor agent keeps transcripts under ~/.cursor/projects/*/agent-transcripts/ which we dont read yet.
MacPorts has some level of support for PowerPC, but anything that isn't in the most recent ~3-4 releases is likely to be cut off from any number of packages at useful versions. (There's substantial work down to support Rust on much older versions of macOS, but there's also versions above which Rust has cut off older macOS versions.)
I believe that there's a recommended stream for when you need older versions support, but it's definitely a secondary target from what I've been reading on the MLs.
I accept LLM contributions to most of my projects, but have (only slightly less) strict rules around it. (My biggest rule is that you must acknowledge the DCO with an appropriate sign-off. If you don't, or if I believe you don't actually have the right to sign off the DCO, I will reject your change.) I will also never accept LLM-generated security reports on any of my projects.
I contribute to chezmoi, which has a strict no-LLM contribution (of any kind) policy. There've been a couple of recent user bans because they used LLM‡ and their contributions — in tickets, no less — included code instructions that could not have possibly worked.
Those of us who have those rules do so out of knowledge and self-respect, not out of gatekeeping or ignorance. We want people to contribute. We don't want garbage.
I think that there needs to be something in the repo itself (`.llm-permissions`?) which all agents look at and follow. Something like:
# .llm-permissions
Pull-Requests: No
Issues: No
Security: Yes
Translation Assistance: Yes
Code Completion: Yes
On those repos where I know there's no LLM permissions, I add `.no-llm` because I've instructed Kiro to look for that file before doing anything that could change the code. It works about 95% of the time.
The one thing that I will never add or accept on my repos is AI code review. This is my code. I have to stand behind it and understand it.
‡ I disagree with those bans for practical reasons because the zero-tolerance stance wasn't visible everywhere to new contributors. I would personally have given these contributors one warning (closed and locked the issue and invited them to open a new issue without the LLM slop; second failure results in permanent ban). But I also understand where the developer of chezmoi is coming from.
This will not be a fun retrospective (the status updates are brutal and clear) -- and I've only been using Coveralls for open source projects for years.
There is a chance — depending on how stubborn the cloud infrastructure provider is (and both Google and AWS can be very stubborn because they don't like admitting that they just might possibly be wrong; I have no experience with Azure but imagine its the same) — that Coveralls will be unable to recover from this because rebuilding the infrastructure from zero on a different provider is going to be hard even if there is 100% IaC and even if there's a solid database backup outside of that provider that's accessible.
I hope they can, because they're a reasonable service and provide a lot of value to open source projects for coverage measurement.
That said, I have seen a number of reliable paths to getting extremely slow responses and eventually 500s from the coveralls servers while trying to look at the coverage details. It has felt like there's been a slow decline in Coveralls server quality because of that. (I've never really reported any of these because (a) I hoped that they were seeing these in their logs, metrics, or notifications and (b) I'm not a paying customer and it's easy for me to `open cover/excoveralls.html` or the equivalent.)
(I have tried the major alternative, codecov.io, in the past, but it's been a long time and I find it disappointing that they appear not to keep their example repos / documentation up to date.)
Most lawns in North America are Kentucky Blue or ryegrass which are what produce the eyesore.
But lawns in general are a pestilence.
reply