Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Unable to unsubscribe to remote communities stuck in the Subscribe Pending state #1315

Open
4 tasks done
IanNorris opened this issue Jun 15, 2023 · 9 comments
Open
4 tasks done
Labels
area: ux bug Something isn't working extra: critical It's really, really important

Comments

@IanNorris
Copy link

IanNorris commented Jun 15, 2023

Requirements

  • Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support
  • Did you check to see if this issue already exists?
  • Is this only a single bug? Do not put multiple bugs in one issue.
  • Is this a server side (not related to the UI) issue? Use the Lemmy back end repo.

Summary

If you subscribe to a community you no longer want to subscribe to, if the subscription is stuck in a pending state (Subscribe Pending) then there is no way to unsubscribe from it. Clicking the link in the UI does nothing.

This probably happens at the moment if some instances are backed up. I have multiple in this state, for example memes@lemmy.ml without any way to unsubscribe.

Steps to Reproduce

  1. Subscribe to a community on a congested instance (eg memes@lemmy.ml)
  2. Go to the Communities list and click to show your Subscribed list.
  3. Observe the Subscription Pending state
  4. Notice there is no way to cancel the pending subscription even though the content appears in the feed

Technical Details

N/A

Version

0.17.4, 0.18.0

Lemmy Instance URL

Lemmy.world

@IanNorris IanNorris added the bug Something isn't working label Jun 15, 2023
@alectrocute
Copy link
Contributor

@SleeplessOne1917 This is fixed in >= 0.18, yeah?

@SleeplessOne1917
Copy link
Member

@alectrocute I'm not entirely sure. If you want to verify, you can test on voyager.lemmy.ml, which is currently running 0.18.

@IanNorris
Copy link
Author

Would I be right in thinking voyager is unfederated? From what I can tell it can't see other instances. I think the issue may have been made visible by lemmy.world being unfederated from beehaw and lemmy.ml which were the instances stuck in the Subscribe Pending state for me.

@SleeplessOne1917
Copy link
Member

@IanNorris voyager is not federated.

@IanNorris
Copy link
Author

Unfortunately I can confirm that 0.18.0 doesn't fix the issue.

@alectrocute alectrocute added the extra: critical It's really, really important label Jun 25, 2023
@Gestrid
Copy link

Gestrid commented Jun 26, 2023

Can confirm. My instance, lemmy.ca, is on 0.18.0, and it's still happening. Notably, it's only happening to communities that I sub to on lemmy.ml, though the other instances I sub to probably aren't nearly as busy as that one.

@zacharee
Copy link

lemmy.ml works for me from sh.itjust.works, but lemmy.world and zerobytes.monster are stuck in the pending state. Posts in the communities I'm trying to subscribe to don't federate to my instance, either, so I don't think it's just an issue with the response to the request.

@IanNorris
Copy link
Author

lemmy.ml works for me from sh.itjust.works, but lemmy.world and zerobytes.monster are stuck in the pending state. Posts in the communities I'm trying to subscribe to don't federate to my instance, either, so I don't think it's just an issue with the response to the request.

I believe that these instances may have been unfederated by the network - this is what originally caused this issue for me as my account was on lemmy.world.

@zacharee
Copy link

I checked and none seem to have blocked each other. sh.itjust.works has only blocked burggit.moe and lemmygrad.ml. lemmy.world doesn't have sh.itjust.works on its blocklist, and zerobytes.monster has sh.itjust.works on its allowlist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ux bug Something isn't working extra: critical It's really, really important
Projects
None yet
Development

No branches or pull requests

6 participants