search

drizzle-mizzle / Character-Engine-Discord

(not yet very) Ultimate LLMs aggregator right in your Discord server
https://discord.gg/JtVzgJ8Znh
GNU General Public License v3.0
105 stars 47 forks source link

Bot stopped working after the latest commit #3

Closed luxlia closed 1 year ago

luxlia commented 1 year ago

The latest commit (0485132) and the commit before it (cb0f147) broke the bot. It throws the following error when I use the slash command:

:warning: Failed to execute command: An error occurred while saving the entity changes. See the inner exception for details.

rolling back to commit b97f46a resolves the issue, and the bot works again.

drizzle-mizzle commented 1 year ago

Yeah, I make changes almost everyday, so sometimes things break, but usually being fixed in next 24 hours. And this issue could be actually helpful if you would specify the exact command caused the problem...

darkxuin commented 1 year ago

I had the same error when trying to spawn a c.AI character. Rolling back fixed it. /spawn cai-character

drizzle-mizzle commented 1 year ago

If there occurs any unhandled exception, it's being displayed in the console. Just saying "it doesn't work" won't help to solve anything, provide the full error stack trace.

darkxuin commented 1 year ago

This isn't going to help so, i'm sorry. When the error happened there was nothing displayed in the console. I attempted to recreate the error by updating to the current version but, it's working fine now. I can only speculate it had something to do with running the first time.

luxlia commented 1 year ago

When the error happened there was nothing displayed in the console

I had a similar thing happen – no logs showed up when the error occurred. I also tried to recreate the issue by going back to that specific commit, then checked the docker compose logs for errors (I'm using Docker), but there's nothing. I even tried to manually run the entrypoint.sh inside the container, but still, no error was displayed. Anyway, the latest commit seems to be working fine now, so I guess the problem's sorted. Gonna close it.

drizzle-mizzle commented 1 year ago

Most likely, it's somehow related to the fact that I have changed database struct a little, made some fields nullable, but they remained non-null in you database. I'll try to mark sensitive changes like this in description in the future.

drizzle-mizzle commented 1 year ago

Yeah, I only noticed that I have not included the migration in the commit where this change occurred, only in one of the following