@hasen_95dx I think it have bug because main goal was to make feature work.
I have never thought about let agent find UI issues by only looking at the code. Maybe it just easy for it because it looked at tons of UI code and know what correct code look like
@func25 The “BUG:” message looks interesting. I often see panic with message “unexpected <something>…”. Do you have convention when to use that “BUG:” message?
@badlogicgames I had this issue with my home wifi too. The network at work worked fine. These are likely the causes, you can give it to gpt codex as a hint to debug the issue: https://t.co/vW0nL3KkZg.
In my case, tweaking some configuration here solved the issue:
@func25 Agree. And I think we should comment "returns ErrUserNotFound when ..." at func definition so caller know about it. It's not always easy to see what error values a function can return. E.g
func GetUser(ctx, id) (*User, error) {
_, err := doSth()
return getUser()
}
@zigo_101 People still adopting and transitioning to Go. For new services, many ppl consider using Go. I think it still growth steadily but there havent new public famous projects written in it.