I made a mistake in my config.yaml where I misspelled the name of my community and my posts were not being created in that community. There wasn't any indication that there was a problem with the community not existing or not being found, which made it hard to diagnose the issue. I think the change is probably updating the logging here to be a bit more descriptive, though I think there is likely also upstream work that could be done in LemmyBot to improve the error it returns.
Here is my error logging from the relevant timeframe:
user_already_exists
user_already_exists
FetchError: invalid json response body at https://lemmy.world/api/v3/post reason: Unexpected token 'J', "Json deser"... is not valid JSON
at /home/doug/workspace/Lemmy-Mega-Bot/node_modules/node-fetch/lib/index.js:273:32
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
type: 'invalid-json'
}
FetchError: invalid json response body at https://lemmy.world/api/v3/post reason: Unexpected token 'J', "Json deser"... is not valid JSON
at /home/doug/workspace/Lemmy-Mega-Bot/node_modules/node-fetch/lib/index.js:273:32
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
type: 'invalid-json'
}
user_already_exists
I made a mistake in my config.yaml where I misspelled the name of my community and my posts were not being created in that community. There wasn't any indication that there was a problem with the community not existing or not being found, which made it hard to diagnose the issue. I think the change is probably updating the logging here to be a bit more descriptive, though I think there is likely also upstream work that could be done in LemmyBot to improve the error it returns.
Here is my error logging from the relevant timeframe: