Appview stops getting my labels after ~1-3 hours after redeclaring labeler service

[simnaut]

Hello,
I am using this labeler server and it works very well for about 1-3 hours after I declare the labeler service, but then the AppView appears to stop picking up labels after that. I redeclare the labeler service, and then I get another 1-3 hours of real time labeling and then the labels aren't picked up anymore again.

From all my logs it looks like the label server is emitting new labels without errors, they just don't make it to the appview or this label scanner after that ~1-3 hour time period: https://blue.mackuba.eu/scanner/

I am having a hard time finding any relevant diagnostic info that indicates what the problem is. I feel like the appview would have diagnostic info but I don't have any access to that.

[simnaut]

A theory I had is that the queryLabels endpoint is working (I believe this is what the appview uses after the labeler service is declared to get all the labels), but not the subscribeLabels endpoint (perhaps what it switches to after the first websocket to queryLabels closes?)

[ThisIsMissEm]

You'd need to give more information about how you're deploying the labeler. Were you able to connect to your labeler via websocket and receive labels? The label scanner you linked to doesn't actually use the websocket endpoint on the labeler, so it's really able to tell you if the labeler is working correctly or not.

[simnaut]

Thanks. Yes I can connect and see labels via websocket. You can too if interested in taking a look: politicslabeler.dudesuh.com. It's deployed on a droplet with caddy as https reverse proxy. I've been using the label scanner to verify that emitted labels on posts are getting picked up by the appview or not

[ThisIsMissEm]

Does the websocket connection stay open for more than 3 hours or does it terminate? What do the logs on the labeler show?

[simnaut]

I haven't run my tester that long before. I just kicked it off now though and will let you know in a few hours. The labeler's logs show its just emitting labels without any interruptions.

[simnaut]

I ran the tester from my home network so its externally facing from the internet to this droplet that hosts the labeler. It has been going for 5 hours now. The appview has already stopped picking up the labels, but my tester is still showing an active stream of labels coming through.

test-subscribe.js

[simnaut]

Made a cron job to redeclare the labeler service every hour. So far looks like this this is keeping the appview engaged. I don't know what consequences (if any) there are to this approach but for now I'll take it. I wish I could have found what the issue is but I think I would need help from a bluesky appview admin or something.

[simnaut]

This approach lasted for about a week, and now redeclaring the service doesn't seem to get the appview engaged anymore. My labeler is basically dead now. I still don't know what the issue is.