search

sublinks / sublinks-federation

Federation service for Sublinks
MIT License
11 stars 4 forks source link

Error when starting the docker dev server about a duplicate key on the actors_pkey #103

Closed lazyguru closed 3 months ago

lazyguru commented 3 months ago

When the federation service runs, it is throwing errors:

federation-1  | 2024/06/09 04:59:06 /src/internal/db/db.go:42 ERROR: duplicate key value violates unique constraint "actors_pkey" (SQLSTATE 23505)
federation-1  | [3.252ms] [rows:0] INSERT INTO "federation"."actors" ("actor_type","id","username","name","bio","matrix_user_id","public_key","private_key") VALUES ('Person','','','joy','','','-----BEGIN PUBLIC KEY-----
federation-1  | MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAm7FRCUhXDJbN9v42AiaW2NI9intfCdi6
federation-1  | pKCQE8JlYvUhpGg/gL2sdJIHxGnK9gS9h/hhENb95tFbvL2cSf7nRQ1URag/r/MeUZzQuVKFSiNt
api-1         | 2024-06-09T04:59:06.192Z DEBUG 1 --- [io-8080-exec-10] s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped to com.sublinks.sublinksapi.api.lemmy.v3.user.controllers.UserController#show(GetPersonDetails)
federation-1  | Ts7p9u+jp9dEXViv+K57blZhFaeWAWSqFBcpESMsaUDtJypdE4WXZf5oZp8v9BUGKWWs0Sozyk2e
federation-1  | CI4+gL6hAsH3NASHdZdeAdTXjy6m2bvx60iZ93aVNZqxwz0s3w1Pyo8vdbuRErhUc3/RhAdDh0Yb
federation-1  | n7b3Rf3vh3TRZ5Hckk3L9JB3axIBgIlcsJkadwfrKWnZXLNhi4FUIqmAPSrZH5/k3rTHbNFp/nK9
federation-1  | Q75gVwIDAQAB
federation-1  | -----END PUBLIC KEY-----
federation-1  | ','-----BEGIN PRIVATE KEY-----
federation-1  | MIIEvAIBADANBgkqhkiG9w0BAQEFAASCBKYwggSiAgEAAoIBAQCbsVEJSFcMls32/jYCJpbY0j2K
federation-1  | e18J2LqkoJATwmVi9SGkaD+Avax0kgfEacr2BL2H+GEQ1v3m0Vu8vZxJ/udFDVRFqD+v8x5RnNC5
federation-1  | UoVKI21Ozun276On10RdWK/4rntuVmEVp5YBZKoUFykRIyxpQO0nKl0ThZdl/mhmny/0FQYpZazR
federation-1  | KjPKTZ4Ijj6AvqECwfc0BId1l14B1NePLqbZu/HrSJn3dpU1mrHDPSzfDU/Kjy91u5ESuFRzf9GE

NOTE: This was found by @chasingtheflow while working on https://github.com/sublinks/sublinks-frontend/pull/166

lazyguru commented 3 months ago

I found the bug. It's on the federation side. We were expecting the "username" field to be "display_name" (I think it was being set as this on the API side at one point, but we had explicitly said it should be "username" in the actors.schema.json file, so.... bug on our side)

lazyguru commented 3 months ago

@chasingtheflow FYI