Question/Bug: roomdb: the item (<pubkey>) is already on the list

[geoah]

Hey there,

I've been trying to play around with ssb and rooms and I'm still trying to wrap my head around some stuff so I'm not really sure if what I'm seeing is an feature or a bug.

I deployed a new go-ssb-room server from e3cea25e25c9173f6a9c878ed71f81454556dbf0 using the docker-compose provided and put an nginx with let's encrypt infront of it.

I added my user and used the password method to log in the admin dashboard. So far so good.

I couldn't figure out how to invite myself, and a previous issue (https://github.com/ssb-ngi-pointer/go-ssb-room/issues/280#issuecomment-991613213) mentioned just creating an invite and using it. I tried on both ios and android (0.2112.3) and in both cases, clicking on the link opens the app, I see the request reaches the server (just logs handling json body), but nothing else happens. No error messages on the app or server.

Trying to debug this further, I added some additional logging, and the issue seems to be that the consume method fails around here: https://github.com/ssb-ngi-pointer/go-ssb-room/blob/e3cea25e25c9173f6a9c878ed71f81454556dbf0/web/handlers/invites.go#L254-L262

The error seems to be the following:

transaction failed, rolling back: roomdb: the item (@<mypubkey>.ed25519) is already on the list

I've also tried to invite a friend as well, at first they seemed to manage to register, but manyverse did nothing (same version on android). After that, they are getting the same error.

---

Question: Is the constraint that a user can only consume an invite once a bug, a feature, or user error?

---

ps. Thank you for your hard work at this, both manyverse and rooms sound amazing! :D

[Count042]

I'm also experiencing this issue. I'm using my own custom docker-compose w/ caddy as a reverse proxy.

[rmdes]

I think the origin of this is that roomdb cannot be found/not writeable in the current dockerfiles. I have double checked and roomdb is writable but it seems it cannot be found, it's like the code expect it to be in a place it is not, since the .env clearly define the REPO, I'm still trying to get this working !

[staltz]

@HendrikPetertje Could you help these folks with Docker?

[decentral1se]

Hey, some thoughts to push this along...

I deployed a new go-ssb-room server from https://github.com/ssb-ngi-pointer/go-ssb-room/commit/e3cea25e25c9173f6a9c878ed71f81454556dbf0 using the docker-compose provided and put an nginx with let's encrypt infront of it.

Have you tried updating to the latest release / HEAD? We're running with traefik as proxy and not seeing these issues.

Question: Is the constraint that a user can only consume an invite once a bug, a feature, or user error?

As I understand it, invites are issued on a per-user basis. One invite, one user. There was a bug with rejecting users from being invited who had already been invited but that was hopefully fixed with https://github.com/ssb-ngi-pointer/go-ssb-room/commit/49aaff968f5d097323da228b2b12c03de90a2de4.