realies
realies
It's possible to specify an offset which is referred to as cursor. For example: ``` (async () => { const recentInbox = await ig.direct.getInbox(); let nextCursor = recentInbox.oldest_cursor; while (nextCursor)...
what os are you trying this on?
Is the [latest update](https://hub.docker.com/layers/realies/soulseek/latest/images/sha256-c2fe902a77027e0d1e1581e4ed668add0401cdd72033482a1bebce7ac788993b?context=explore) from https://github.com/realies/soulseek-docker/commit/f299da8985c12a410e2acae76808d6ff487cbb3d fixing this? I can't recreate the issue on Ubuntu 24.04 with Docker 26.1.0.
@c-hri-s, are you sure this is latest? It should be writing to `/proc/self/fd/1` instead of `/dev/stdout` now.
Does it fail the same way if you run the container with PUID=0 and PGID=0, @dr3nch?
Running everything inside the container as root (PUID/PGID 0) is suboptimal for security. It would also change the ownership of all files mounted to root. I don't have access to...
@R4di04kt1v3, works fine on 24.04 over here. Just tested on a different VPS: ``` $ docker run --rm -p 6080:6080 realies/soulseek:latest Unable to find image 'realies/soulseek:latest' locally latest: Pulling from...
OK, not sure why I assumed the default PUID/PGID are 1000, this is how it fails: ``` $ docker run --name soulseek -e PUID=1000 -e PGID=1000 -p 6080:6080 soulseek:latest Traceback...
Thanks for the feedback. An update is in the works, in the meantime running as PUID=0 and PGID=0 should get it going.
Can you check if the latest build runs fine without PUID=0 and PGID=0? There's also a support me button on my profile page now :)