Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Just stuck in a loop trying to create a supabase user and now the prompt is disabled and I can go no further. #4989

Open
1 task done
miPwn opened this issue Jan 4, 2025 · 1 comment

Comments

@miPwn
Copy link

miPwn commented Jan 4, 2025

Describe the bug

I've had a few sessions like this where it just burns away millions of credits creating bugs and then trying to fix them or completely failing at fixing them after ten or more attempts. There doesn't seem to be any value in this AI post the initial creation of code. It seems useless at modifications or further enhancements without destroying the codebase or cluttering it with failed experiments.

Link to the Bolt URL that caused the error

https://bolt.new/~/sb1-f6bo3k3j

Validations

  • Please make your project public or accessible by URL. This will allow anyone trying to help you to easily reproduce the issue and provide assistance.

Steps to reproduce

I can't actually do anything as the prompt is disabled.

Expected behavior

It should be able to create a user and fix the issues it creates itself without constantly looping over failed attempts.

Screen Recording / Screenshot

No response

Platform

Browser name = Chrome
Full version = 131.0.0.0
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 75358551,
  "usedJSHeapSize": 66162279,
  "jsHeapSizeLimit": 4294705152
}
Username = miPwn
Chat ID = 67a7ec021b1d

Additional context

No response

@miPwn
Copy link
Author

miPwn commented Jan 4, 2025

Another thing that is really annoying (and dangerous) is it's over proactiveness and assumptions, adding unrequested features or making opinionated changes to functionality for nor reason while trying to address something else that is unrelated. On several occasions it has felt like errors were being introduced for the sole purpose of creating long fix cycles to generate more revenue. While these errors were often easier to fix manually, I do not trust it any more and have downgraded my subscription because of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant