It appears that some instances have not resolved the unsubscribes properly, and I’m seeing errors like the below:

2025-10-07T12:20:11.488023Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: CommunityHasNoFollowers: CommunityHasNoFollowers
   0: lemmy_apub::activities::community::announce::receive
             at crates/apub/src/activities/community/announce.rs:161
   1: lemmy_server::root_span_builder::HTTP request
           with http.method=POST http.scheme="http" http.host=lemmy.domain.ext http.target=/inbox otel.kind="server" request_id=02568c66-9ed6-4eb0-b533-77b19rcdef56 http.status_code=400 otel.status_code="OK"
             at src/root_span_builder.rs:16

Is there a way to determine which communities are throwing this error, and force the unsubscribe?

  • fmstrat@lemmy.nowsci.comOPEnglish
    1·
    11 days ago

    This was with the default logging:

    RUST_LOG=warn,extism=info,lemmy_server=debug,lemmy_api=debug,lemmy_api_common=debug,lemmy_api_crud=debug,lemmy_apub=debug,lemmy_db_schema=debug,lemmy_db_views=debug,lemmy_routes=debug,lemmy_utils=debug,lemmy_websocket=debug

    Any idea which one I should set to trace?