Inbound Note processing doesn't work properly on first server run #378

Closed
opened 2023-04-20 14:16:09 +00:00 by yanchan09 · 1 comment

After setting the server up for the first time and not restarting it afterwards, processing inbound Notes fails with the following stacktrace:

Error: the user is already exists
    at file:///opt/foundkey/src/packages/backend/built/services/create-system-user.js:25:19
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async EntityManager.transaction (/opt/foundkey/src/node_modules/typeorm/entity-manager/EntityManager.js:72:28)
    at async createSystemUser (file:///opt/foundkey/src/packages/backend/built/services/create-system-user.js:19:5)
    at async getInstanceActor (file:///opt/foundkey/src/packages/backend/built/services/instance-actor.js:11:25)
    at async Resolver.resolve (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/resolver.js:74:25)
    at async createNote (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/models/note.js:60:20)
    at async resolveNote (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/models/note.js:261:16)
    at async createNote (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/models/note.js:107:11)
    at async default (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/kernel/create/note.js:26:9)
After setting the server up for the first time *and not restarting it afterwards*, processing inbound Notes fails with the following stacktrace: ``` Error: the user is already exists at file:///opt/foundkey/src/packages/backend/built/services/create-system-user.js:25:19 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async EntityManager.transaction (/opt/foundkey/src/node_modules/typeorm/entity-manager/EntityManager.js:72:28) at async createSystemUser (file:///opt/foundkey/src/packages/backend/built/services/create-system-user.js:19:5) at async getInstanceActor (file:///opt/foundkey/src/packages/backend/built/services/instance-actor.js:11:25) at async Resolver.resolve (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/resolver.js:74:25) at async createNote (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/models/note.js:60:20) at async resolveNote (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/models/note.js:261:16) at async createNote (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/models/note.js:107:11) at async default (file:///opt/foundkey/src/packages/backend/built/remote/activitypub/kernel/create/note.js:26:9) ```
yanchan09 changed title from Inbound activity processing doesn't work properly on first server run to Inbound Note processing doesn't work properly on first server run 2023-04-20 14:24:16 +00:00
Johann150 added the
fix
label 2023-04-20 15:29:21 +00:00
Owner

Thank you for the bug report.

Thank you for the bug report.
Sign in to join this conversation.
No Label
feature
fix
upkeep
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: FoundKeyGang/FoundKey#378
No description provided.