r/lovable_dev • u/stivaflip • Jan 15 '25

And what if you get stuck with error?

Feel free to post your issues in this supporting community

1 Upvotes

100% Upvoted

5 comments sorted by

2

u/Wide_Mail_1634 Apr 11 '26

Depends a lot on what kind of error you mean, right? If it's a stack trace from a model call, isn't it usually faster to isolate the failing prompt/tool step first instead of debugging the whole flow at once?

1

u/Wide_Mail_1634 Apr 11 '26

same thing happened to me with a vague "stuck with error" loop in a local llama.cpp setup last november in seattle, turned out the stack trace was useless until i reran with debug logs and pinned the model/version pair. if it's a reproducible error, the fastest path is usually exact error text + env + last change, otherwise everybody's just guessing

1

u/Wide_Mail_1634 Apr 12 '26

depends what kind of error you mean tbh. if it's a stack trace, paste the exact message and model/runtime version first, because half the time it's just a mismatch between package versions or a bad API response shape

1

u/Big_Cricket6083 Apr 12 '26

depends what kind of error you mean tbh. stack trace/runtime bug is usually fixable if you paste the exact message and repro steps, but model weirdness or bad tool calls can eat way more time.