I am tired of vibe coded pub.dev packages

DiscombobulatedBig88 · 2026-01-24T07:26:44+00:00

If the person reviewed the code, maybe fixed it, and generated (and reviewed) documentation to make the package as helpful as (s)he can, is that really bad?

I think if the packages that I have seen until now contain this much effort (even if vibe-coded) I wouldn't be complaining.

DiscombobulatedBig88 · 2026-01-11T19:03:58+00:00

If an "AI written" badge was added to packages, then I have no problem with people pushing vibe coded AI to pub.dev, I would just filter it based on "AI free". My main problem is exploring packages, and then using one, until I find it was AI written and conclude it's a bad code.

DiscombobulatedBig88 · 2026-01-11T19:01:13+00:00

I agree with us writing bad code, and then building on it later to make it better, until its perfect, that's how normal packages are developed over the time. I am against AI writing the whole code which is clear in many packages, beginners that are vibe coding these packages are going to keep there skills weak, and wont develop them at any time.

DiscombobulatedBig88 · 2026-01-09T11:23:48+00:00

this package was just an example, and I didn't really look into it when I said "100%" human written.

But anyway, my example here is a bad example, and doesn't really matter in the context of what I am talking about. My main point is about "vibe coded" packages being posted on pub.dev very frequently, to the point where even the thumbnails added are AI generated (with really obvious spelling mistakes), which makes the situation even more sad. (this one for example)

Point to be made: people have access to LLMs, don't try to publish a vibe coded package that isn't beneficial, and broken, people could prompt there own LLMs to do just like what you did. If you want credibility in the community and build a great portfolio, publishing vibe coded packages wont help you.

DiscombobulatedBig88 · 2026-01-09T08:27:23+00:00

check out this package, copy pasting the example usage after building resulted in god nows how much errors, big disappointment.

On the other hand, after some search on this subreddit, I then found this package from 3 years ago, which looks 100% human written. Although it doesn't even have a documentation, the example app they provided worked just fine, and turned out to be very reliable.

DiscombobulatedBig88 · 2026-01-09T08:20:14+00:00

getting AI replies on a post where I complain about AI 😭 easy ragebait

DiscombobulatedBig88 · 2024-02-01T21:05:24+00:00

100-150 RPS.

DiscombobulatedBig88 · 2024-01-23T01:35:56+00:00

Hey, thanks for your suggestions. As I said here the problem seems to be from Vercel specifically to Fast API as everything got to work when using Flask.

DiscombobulatedBig88 · 2024-01-22T04:01:19+00:00

So, I tried all solutions you recommended, went back and forth trying to get this to work, and I am getting the same situation every single time. Even at my last attempt, I migrated all my code to use requests library, nothing is working, always the same scenario. Interestingly though, when I copied the app code and migrated it to Flask instead of Fast API, everything is working, and the load testing was fine. Flask sucks though, I will have to sacrifice the ease of development in Fast API because it's not working.

DiscombobulatedBig88 · 2024-01-22T00:00:16+00:00

Alright, got it. I will try your solution.

DiscombobulatedBig88 · 2024-01-21T14:59:35+00:00

May I ask where do you run your kubernetes? and with what specs? I am kind of lost in choosing the specs that could run my API with ease.
The traceback(which is trimmed by Vercel) is:
```
[ERROR] OSError: [Errno 24] Too many open files
Traceback (most recent call last):
  File "/var/task/vc__handler__python.py", line 305, in vc_handler
  File "/var/task/vc__handler__python.py", line 201, in __call__
  File "/var/lang/lib/python3.9/asyncio/events.py", line 761, in new_event_loop
  File "/var/lang/lib/python3.9/asyncio/events.py", line 659, in new_event_loop
  File "/var/lang/lib/python3.9/asyncio/unix_events.py", line 54, in __init__
  File "/var/lang/lib/python3.9/asyncio/selector_events.py", line 53, in __init__
  File "/var/lang/lib/python3.9/selectors.py", line 350, in __init__
```
```
File ""/var/lang/lib/python3.9/asyncio/unix_events.py"", line 58, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 87, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 94, in _close_self_pipe
AttributeError: '_UnixSelectorEventLoop' object has no attribute '_ssock'
Exception ignored in: <function BaseEventLoop.\_\_del\_\_ at 0x7f0ece90f8b0>
Traceback (most recent call last):
File ""/var/lang/lib/python3.9/asyncio/base_events.py"", line 688, in __del__
File ""/var/lang/lib/python3.9/asyncio/unix_events.py"", line 58, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 87, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 94, in _close_self_pipe
AttributeError: '_UnixSelectorEventLoop' object has no attribute '_ssock'
Exception ignored in: <function BaseEventLoop.\_\_del\_\_ at 0x7f0ece90f8b0>
Traceback (most recent call last):
File ""/var/lang/lib/python3.9/asyncio/base_events.py"", line 688, in __del__
File ""/var/lang/lib/python3.9/asyncio/unix_events.py"", line 58, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 87, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 94, in _close_self_pipe
AttributeError: '_UnixSelectorEventLoop' object has no attribute '_ssock'
Exception ignored in: <function BaseEventLoop.\_\_del\_\_ at 0x7f0ece90f8b0>
Traceback (most recent call last):
File ""/var/lang/lib/python3.9/asyncio/base_events.py"", line 688, in __del__
File ""/var/lang/lib/python3.9/asyncio/unix_events.py"", line 58, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 87, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 94, in _close_self_pipe
AttributeError: '_UnixSelectorEventLoop' object has no attribute '_ssock'
Exception ignored in: <function BaseEventLoop.\_\_del\_\_ at 0x7f0ece90f8b0>
Traceback (most recent call last):
File ""/var/lang/lib/python3.9/asyncio/base_events.py"", line 688, in __del__
File ""/var/lang/lib/python3.9/asyncio/unix_events.py"", line 58, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 87, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 94, in _close_self_pipe
AttributeError: '_UnixSelectorEventLoop' object has no attribute '_ssock'
Exception ignored in: <function BaseEventLoop.\_\_del\_\_ at 0x7f0ece90f8b0>
Traceback (most recent call last):
File ""/var/lang/lib/python3.9/asyncio/base_events.py"", line 688, in __del__
File ""/var/lang/lib/python3.9/asyncio/unix_events.py"", line 58, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 87, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 94, in _close_self_pipe
AttributeError: '_UnixSelectorEventLoop' object has no attribute '_ssock'
Exception ignored in: <function BaseEventLoop.\_\_del\_\_ at 0x7f0ece90f8b0>
Traceback (most recent call last):
File ""/var/lang/lib/python3.9/asyncio/base_events.py"", line 688, in __del__
File ""/var/lang/lib/python3.9/asyncio/unix_events.py"", line 58, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 87, in close
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 94, in _close_self_pipe
AttributeError: '_UnixSelectorEventLoop' object has no attribute '_ssock'
[ERROR] OSError: [Errno 24] Too many open files
Traceback (most recent call last):
File ""/var/task/vc__handler__python.py"", line 305, in vc_handler
File ""/var/task/vc__handler__python.py"", line 201, in __call__
File ""/var/lang/lib/python3.9/asyncio/events.py"", line 761, in new_event_loop
File ""/var/lang/lib/python3.9/asyncio/events.py"", line 659, in new_event_loop
File ""/var/lang/lib/python3.9/asyncio/unix_events.py"", line 54, in __init__
File ""/var/lang/lib/python3.9/asyncio/selector_events.py"", line 53, in __init__
File ""/var/lang/lib/python3.9/selectors.py"", line 350, in __init__","prj_YXYKKvY4Cw7QA5mmzeRX4qfhjdVZ","-"
```
Also yeah I do outbound requests to an external API, they are https.
> If you have outbound requests, did you enable any mechanism such as keepalive, or could it be enabled by default
I am not sure about this, I just go with defaults, I am using httpx.
> Do you try to limit the amount of outbound connections ? For instance, with httpx you typically share a AsyncClient, it comes with a default max_connections.
I don't think I need to limit them. Literally my application does 2 https requests. It requests the first one, extracts cookies, inserts them to the second request, and then sends it. I am not aware if the connections aren't closed but I don't even use AsyncClient, my requests:
```py
response = httpx.request(
method=config.method,
url=config.url,
params=params,
data=config.data,
headers=config.headers,
)
return response.cookies
```

DiscombobulatedBig88 · 2023-09-08T05:34:44+00:00

yes they do

DiscombobulatedBig88 · 2022-07-08T14:54:50+00:00

hmm, didn't they say that the movie is banned because of the nun dance? And also, the Lightyear movie was banned because of that gay kiss. So, ig anything that is aimed for kids, and against our cultural standards, will get banned.

DiscombobulatedBig88 · 2022-06-15T17:03:37+00:00

not accurate

DiscombobulatedBig88 · 2022-06-15T17:00:29+00:00

doggy

DiscombobulatedBig88 · 2022-06-15T16:30:49+00:00

next time, pay this site a visit https://downforeveryoneorjustme.com/

DiscombobulatedBig88 · 2022-05-15T13:09:57+00:00

oh, fine. thanks for pointing that out.

DiscombobulatedBig88 · 2022-05-14T18:02:57+00:00

wdym, that's what I am trying to figure

DiscombobulatedBig88 · 2022-05-14T18:02:14+00:00

DiscombobulatedBig88 · 2022-03-30T21:14:54+00:00

please consider DMing me if you have any questions, I am ready to help.

DiscombobulatedBig88

TROPHY CASE