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

FEATURE REQUEST: [PLM]: Allow for multiple delete of Parent Channels #33

Closed
donchi40 opened this issue Feb 4, 2025 · 8 comments
Closed
Assignees
Labels
(L0) Complete Ready for release, pending deployment

Comments

@donchi40
Copy link

donchi40 commented Feb 4, 2025

I hope I describe this clearly.
Let's say that during the addition of new channels, I mistakenly created multiple parents.
Now, when viewing the Parents Stations tab, I see the multiple listings for multiple channels, for example, I have too many Court TV and BBC Comedy set as parents.
Currently, you click on Delete for each parent listing, which the system saves it, and then return to the full Parent listing.
Now I have to scroll down, and click delete on the next parent.
What I'm requesting, if it's possible, is to have maybe a check box next to each parent so I can select multiple listings at one time, before clicking the save/update button.

@donchi40 donchi40 changed the title Feature Request: Allow for multiple delete of Parent Channels FEATURE REQUEST: [PLM]: Allow for multiple delete of Parent Channels Feb 4, 2025
@babsonnexus babsonnexus self-assigned this Feb 4, 2025
@babsonnexus babsonnexus added the (L3) Enhancement - Accepted New feature or modification label Feb 4, 2025
@babsonnexus
Copy link
Owner

What I can do is add a selection to the 'Preferred Playlist' dropdown called Delete and then if you select that and save, it will remove all the parents that you've set that as.

@donchi40
Copy link
Author

donchi40 commented Feb 4, 2025

OK, looking forward to see that.

@babsonnexus
Copy link
Owner

This will be made available in the next release:


  • NEW: [PLM] Delete multiple parent stations at once.

Under Preferred Playlists, there is a new option for 'Delete':

image

You can then select this for multiple parents at once, resulting in all of them being deleted on save and their child stations being unassigned.

Should you try to create a new parent using the 'Delete' tag, it will be assigned 'None'.

@babsonnexus babsonnexus added (L0) Complete Ready for release, pending deployment and removed (L3) Enhancement - Accepted New feature or modification labels Feb 7, 2025
@donchi40
Copy link
Author

donchi40 commented Feb 7, 2025

Thank you... Looking forward to this change.

@babsonnexus
Copy link
Owner

@donchi40
Copy link
Author

donchi40 commented Feb 11, 2025

@babsonnexus
Unfortunately, I am giving up for now...
I had SLM/PLM opened before I started anything the the updates below, and it was working.

So to start, I downloaded/updated to the new version (just so you know, I'm using Podman, the Fedora/RedHat version of Docker) and spun it up.
The console wouldn't open. I get this:


This site can’t be reached The connection was reset.
Try: Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET


I looked at the logs is Dozzle, and I see the following error: Container has no logs yet

I then used both "podman logs -f streamlink1" and also opened the slm.log in the slm_files folder... and I see:

2025-02-10 15:41:59.765169: Beginning Initialization Process (see log for details)...
[DEBUG | 2025-02-10 15:41:59,766] - Starting new HTTPS connection (1): www.justwatch.com:443
2025-02-10 15:42:09.773196: ERROR: https://www.justwatch.com reports HTTPSConnectionPool(host='www.justwatch.com', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7fde81a59850>: Failed to resolve 'www.justwatch.com' ([Errno -3] Temporary failure in name resolution)"))
2025-02-10 15:42:09.773261: INFO: Retrying in 1 minute...
[DEBUG | 2025-02-10 15:43:09,774] - Starting new HTTPS connection (1): www.justwatch.com:443

And it just keeps repeating every minute...

I logged into the console and tried to ping or nslookup www.justwatch.com but couldn't find neither ping nor nslookup.
From the host server, I did a nslookup on www.justwatch.com to make sure I could see it and got the IP address.
I first added 8.8.8.8 to container's /etc/nslookup file but still no go on finding the site.
I then added the ip-address and hostname to the container's /etc/hosts file but still getting the same error.

Lastly, I deleted the image, the container and also the streamlink folders and then restarted as a fresh install.
Still having the same resolve issue.

So at this moment in time, I am giving up and will take a fresh look tomorrow.
Unless you have any suggestions?

Additional 1:
Just in case you ask, here is the compose.yaml file I'm using, please note, this was what I was using with the previous release and it worked:
slm1:
image: ghcr.io/babsonnexus/stream-link-manager-for-channels
container_name: streamlink1
ports:
- 5000:5000
volumes:
- ./streamlink/streamlink1/slm_files:/app/program_files
- ./streamlink/streamlink1/channels:/app/channels_folder
environment:
- TZ=Pacific/Honolulu
restart: unless-stopped

Additional 2:
I just looked at an old backup of the slm.log from last month, and this is what I should be seeing:

[DEBUG | 2025-01-31 08:13:38,008] - Starting new HTTPS connection (1): www.justwatch.com:443
[DEBUG | 2025-01-31 08:13:39,533] - https://www.justwatch.com:443 "GET / HTTP/1.1" 200 None

2025-01-31 08:13:39.711700: SUCCESS: https://www.justwatch.com is accessible. Continuing...
[DEBUG | 2025-01-31 08:13:39,718] - Starting new HTTPS connection (1): apis.justwatch.com:443
[DEBUG | 2025-01-31 08:13:40,125] - https://apis.justwatch.com:443 "POST /graphql HTTP/1.1" 200 None
[DEBUG | 2025-01-31 08:13:46,793] - Starting new HTTPS connection (1): raw.githubusercontent.com:443
[DEBUG | 2025-01-31 08:13:47,395] - https://raw.githubusercontent.com:443 "GET /babsonnexus/stream-link-manager-for-channels/refs/heads/main/slm.py HTTP/1.1" 200 66705

So... I am at a loss as I don't know what changed so that the container can no longer access the justwatch web site.

@donchi40
Copy link
Author

@babsonnexus
Thanks for the follow up...
However, I've got it resolved... after stepping away overnight and now looking at it again.
So today, I noticed several failures in my other containers... for example, my speedtest stopped running the tests due to some network failure and some of my other playlist containers weren't updating.
So, I rebooted the host server and then ran a manual container speedtest, and it worked.
I then regenerated the SLM container and I can now access the web page...
Now I just have to rebuild my playlists... but as I've picked up so many tips along the way, I'm finding it much easier now to create the lists I want.
Again, thanks for all the assists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
(L0) Complete Ready for release, pending deployment
Projects
None yet
Development

No branches or pull requests

2 participants