Why, when I search for a community my instance is not yet aware of, does it sometimes not bring back any posts in that community? This community is in example of that.
Most new additions will redline the CPU but then come back with a populated page for the community. Sometimes that doesn’t happen and no amount of purging and retrying will cause it to.
I’m currently unable to subscribe to anything on Beehaw. I just get subscription pending and there is no content sent my way. Statistically they’re also more likely to encounter no. 1 above. Can I fix this?
Your instance won’t start fetching any posts from a community, until someone from your instance subscribes to it. Then it will fetch the last 25 posts (I think) and then all future posts.
I don’t think that’s true. Searching for a community typically brings back a fully populated page. None of the posts have comments or up/down votes, but they’re all there.
I’d say in maybe 20% of cases though it comes back empty.
Here is the official documentation: https://join-lemmy.org/docs/administration/federation_getting_started.html#fetching-communities
If you search for a community first time, 20 posts are fetched initially. Only if a least one user on your instance subscribes to the remote community, will the community send updates to your instance.
The point is I’m not getting 20 posts. I get nothing. I can subscribe and then get posts from that point forward as I’d expect.
You can try and fetch an earlier post manually and see if that works.
Yeah, sadly not working on communities that exhibit this issue. This one (!lemmy_admin) is one. I have two posts showing on my instance, this one and another that seems to have been updated recently.
If I search for https://lemmy.ml/post/6417868 using my instances search I get no results found. The error in the logs is
2023-11-10T10:20:48.585813Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: couldnt_find_object: data did not match any variant of untagged enum SearchableKinds 0: lemmy_apub::fetcher::search::search_query_to_object_id at crates/apub/src/fetcher/search.rs:19 1: lemmy_apub::api::resolve_object::resolve_object with data=Query(ResolveObject { q: "https://lemmy.ml/post/6417868", auth: Some(Sensitive) }) at crates/apub/src/api/resolve_object.rs:19 2: lemmy_server::root_span_builder::HTTP request with http.method=GET http.scheme="http" http.host=doomscroll.n8e.dev http.target=/api/v3/resolve_object otel.kind="server" request_id=4ef4bf5c-228f-4268-b798-3561a79d9a2f http.status_code=400 otel.status_code="OK" at src/root_span_builder.rs:16 LemmyError { message: Some("couldnt_find_object"), inner: data did not match any variant of untagged enum SearchableKinds, context: SpanTrace [{ target: "lemmy_apub::fetcher::search", name: "search_query_to_object_id", file: "crates/apub/src/fetcher/search.rs", line: 19 }, { target: "lemmy_apub::api::resolve_object", name: "resolve_object", fields: "\u{1b}[3mdata\u{1b}[0m\u{1b}[2m=\u{1b}[0mQuery(ResolveObject { q: \"https://lemmy.ml/post/6417868\", auth: Some(Sensitive) })", file: "crates/apub/src/api/resolve_object.rs", line: 19 }, { target: "lemmy_server::root_span_builder", name: "HTTP request", fields: "\u{1b}[3mhttp.method\u{1b}[0m\u{1b}[2m=\u{1b}[0mGET \u{1b}[3mhttp.scheme\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"http\" \u{1b}[3mhttp.host\u{1b}[0m\u{1b}[2m=\u{1b}[0mdoomscroll.n8e.dev \u{1b}[3mhttp.target\u{1b}[0m\u{1b}[2m=\u{1b}[0m/api/v3/resolve_object \u{1b}[3motel.kind\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"server\" \u{1b}[3mrequest_id\u{1b}[0m\u{1b}[2m=\u{1b}[0m4ef4bf5c-228f-4268-b798-3561a79d9a2f \u{1b}[3mhttp.status_code\u{1b}[0m\u{1b}[2m=\u{1b}[0m400 \u{1b}[3motel.status_code\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"OK\"", file: "src/root_span_builder.rs", line: 16 }] }
but I don’t know if that’s helpful.
The pending subscription is a known thing. If you retract the subscription and then redo it, it should be good. If not, wait a bit and retry. You may have to reload the page so see the button change to “Subscribed”.
Not sure about the other though. In my experience, purging and refetching a community will always fix it… :/
I’ll pass this post to the admin Matrix chat (which you should join), since it’s important to have this kind of info publicly and readily available as well.
Yeah. I looks like the beehaw thing has resolved itself. I don’t know why it was just them but I have been able to subscibe since yesterday. I’m guessing that this is an issue with the source instance rather than the requesting instance - maybe it’s not sending out an accept activity like it should.
I’m still seeing the lack of content in newly searched communities though. https://sh.itjust.works/c/plugins for instance just refuses to come back with anything.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !plugins@sh.itjust.works