4 ms·

> (actually I just checked again, and the PR has been closed by stalebot). Can you provide the link?

Delgan 4mo ago
I, too, was curious to see it in practice. Here is the ticket opened by @retr0id: https://github.com/oven-sh/bun/issues/28030 https://github.com/oven-sh/bun/issues/28030 And here is the swarm of bots / LLMs / agents that open, review and bikeshed the PR before it's closed by the stalebot: https://github.com/oven-sh/bun/pull/28031 https://github.com/oven-sh/bun/pull/28031 It's hilarious. But also a little sad.
- Retr0id 4mo ago
  Yup, that's the one.
  - Phelinofist 4mo ago
    That's pure comedy
- skeledrew 4mo ago
  Why sad?
  - Retr0id 4mo ago
    It's a bizarre simulation of what would normally be a social interaction, and the (minor) effort I put in on my end just went into a black hole.
    - skeledrew 4mo ago
      I see. I'm kinda wondering, did something break in the process? Or was it missing a human to do the final check and merge?
- dgellow 4mo ago
  Ok, you didn’t lie, it’s extremely funny, the stalebot at the end is such a good punchline!
tomjakubowski 4mo ago
Here's a trivial docs issue I opened, where I had a similar experience: https://github.com/oven-sh/bun/issues/31233 https://github.com/oven-sh/bun/issues/31233 The difference is that the PRs to fix that problem were already open when I created the issue. I was unaware of them (I only searched for duplicate issues, not PRs addressing the problem). The robobun comment implies there are 5 open PRs addressing it, but I could only find two. They still haven't been merged, a month later. https://github.com/oven-sh/bun/pull/30677 https://github.com/oven-sh/bun/pull/30677 <-- later rolled up into: https://github.com/oven-sh/bun/pull/30747 https://github.com/oven-sh/bun/pull/30747
- anematode 4mo ago
  Utter dysfunction. I ripped out bun from my projects after the vibe Rust rewrite, but seems like the problem has existed much longer...

I, too, was curious to see it in practice. Here is the ticket opened by @retr0id: https://github.com/oven-sh/bun/issues/28030 https://github.com/oven-sh/bun/issues/28030 And here is the swarm of bots / LLMs / agents that open, review and bikeshed the PR before it's closed by the stalebot: https://github.com/oven-sh/bun/pull/28031 https://github.com/oven-sh/bun/pull/28031 It's hilarious. But also a little sad.

Retr0id 4mo ago
Yup, that's the one.
- Phelinofist 4mo ago
  That's pure comedy
skeledrew 4mo ago
Why sad?
- Retr0id 4mo ago
  It's a bizarre simulation of what would normally be a social interaction, and the (minor) effort I put in on my end just went into a black hole.
  - skeledrew 4mo ago
    I see. I'm kinda wondering, did something break in the process? Or was it missing a human to do the final check and merge?
dgellow 4mo ago
Ok, you didn’t lie, it’s extremely funny, the stalebot at the end is such a good punchline!

tomjakubowski 4mo ago

Here's a trivial docs issue I opened, where I had a similar experience: https://github.com/oven-sh/bun/issues/31233 https://github.com/oven-sh/bun/issues/31233 The difference is that the PRs to fix that problem were already open when I created the issue. I was unaware of them (I only searched for duplicate issues, not PRs addressing the problem). The robobun comment implies there are 5 open PRs addressing it, but I could only find two. They still haven't been merged, a month later. https://github.com/oven-sh/bun/pull/30677 https://github.com/oven-sh/bun/pull/30677 <-- later rolled up into: https://github.com/oven-sh/bun/pull/30747 https://github.com/oven-sh/bun/pull/30747

anematode 4mo ago
Utter dysfunction. I ripped out bun from my projects after the vibe Rust rewrite, but seems like the problem has existed much longer...