0 Followers
0 Following
1 Posts

I’ve actually had pretty good success with ChatGPT when I go in expecting it to hallucinate a significant chunk of what it spits back at me. I like to think of it as a way to help process my own ideas. If I ask questions with at least a base understanding of the topic, I can then take whatever garbage it gives me and go off and find real solutions. The key is to not trust it whole cloth to give you the right answer, but to give you some nuggets that set you on the right path.

I think I’ve basically turned ChatGPT into my rubber duck.

Suddenly getting a server error on my instance

https://lemmy.world/post/10562215

Suddenly getting a server error on my instance - Lemmy.World

I don’t know when it started, I usually check my instance through the Voyager app and it never showed a problem, but I’m suddenly getting “server error” and 502 bad gateway errors on my instance on desktop. I haven’t made any major changes (read, any at all) since I last confirmed it worked on desktop. Checking the logs I don’t see any obvious proxy issues but I am getting weird connection issues in lemmy-ui: TypeError: fetch failed lemmy-lemmy-ui-1 | at Object.fetch (node:internal/deps/undici/undici:11730:11) lemmy-lemmy-ui-1 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { lemmy-lemmy-ui-1 | cause: ConnectTimeoutError: Connect Timeout Error lemmy-lemmy-ui-1 | at onConnectTimeout (node:internal/deps/undici/undici:6869:28) lemmy-lemmy-ui-1 | at node:internal/deps/undici/undici:6825:50 lemmy-lemmy-ui-1 | at Immediate._onImmediate (node:internal/deps/undici/undici:6857:13) lemmy-lemmy-ui-1 | at process.processImmediate (node:internal/timers:478:21) { lemmy-lemmy-ui-1 | code: 'UND_ERR_CONNECT_TIMEOUT' lemmy-lemmy-ui-1 | } lemmy-lemmy-ui-1 | } Where on earth can I even begin to address this?

Meaning I just wait a bit and retry later?

Upgraded to 0.18.5, which now gives me this error:

lemmy-lemmy-ui-1 | API error: FetchError: request to http://lemmy:8536/api/v3/site?auth=AUTH_KEY failed, reason: connect ECONNREFUSED IP_ADDRESS:8536
I created a gist with my compose file: gist.github.com/…/26a875576d3bbcf11923d7715ac15e6…. It should be stripped of all private info. I tried changing the version from 0.17.3 to 0.18.0 and the server returns a gateway error after restarting.
graphics

GitHub Gist: instantly share code, notes, and snippets.

Gist

Need some guidance with upgrading

https://lemmy.world/post/9861977

Need some guidance with upgrading - Lemmy.World

Hi! I’m hoping for some guidance upgrading my instance. I’m still running on v0.17.3 because I ran into some issues upgrading to 0.18 and didn’t have time to really figure it out. Now that the current release is v0.19, I have people on my instance asking to upgrade and I don’t blame them. Can I simply point Docker compose at the latest release, or do I have to do incremental upgrades? What do I need to look out for with v0.18? Documentation seems to be pretty slim for whatever breaking changes happened during that release cycle and how to deal with them. Any help is appreciated!

About freaking time. I have it as an option but I hate using it. I’ve been looking for alternatives for a while now because I just expect to lose a couple hundred bucks in “processing” for every project I work on.
Couldn’t happen to a nicer group of people.
They’re about 8 years behind the curve though. Just like a client who recently told me they were thinking of getting into NFTs to make some money.
It’s a bold strategy, Cotton. Let’s see if it pays off for them.