#Overseerr
quaint cave
@boreal veldt @latent quiver
So Seerr now got released, and Felix put in effort to make the library work with Seerr
It originally started as supporting Jellyseerr, but that felt weird, as Jellyseerr isn't Overseerr
but now that it's Seerr we can
solid obsidian
Yes, Seerr 🫡
quaint cave
Yes!
quaint cave
@solid obsidian @latent quiver do you happen to have Overseerr running?
solid obsidian
No seerr, just couldn't resist the pun
twin sequoia
-# I seerr what you did theerr 😶
quaint cave
Because apparently there are issue comments and my test data doesn't seem to have them
and I am not sure why I added that
@boreal veldt I would love if you could double check https://github.com/joostlek/python-overseerr/pull/323/changes/a377dbf532f4f9b5a1b4191c55057177a34aa8e0
Is media_info missing because the movie hasn't been requested yet?
latent quiver
<@363996043450515458> <@263171959766908928> do you happen to have Overseerr runn...
I do have both running, figured we’d need it for a little while
I just did the seer migration last night from copying over data from a backup, was easy
quaint cave
Could you maybe share a response of a list of issues with comments?
(eventually I only need to have 1)
because Seerr just adds it as a comment, but without user data
and my model does ask for user data
but I have no overseerr fixture that has a comment on an issue, so I am not sure if I just made this up or not
boreal veldt
<@253225491601817600> I would love if you could double check <https://github.com...
will do
quaint cave
Okay I got the PR working now
So some fields are now not provided anymore by Seerr
Oh no, some of the fields added aren't present in Overseerr
boreal veldt
So some fields are now not provided anymore by Seerr
yeah, I think we should let them in there for a few months for backwards compatability and then deprecate and remove them at some point
quaint cave
Yea, I think that would mainly depend on the main migration path
as in, if they still support overseerr for a year, then I think we could as well
latent quiver
Here's the response when viewing all issues, no comments
When you click into an issue you get comments in the response
Induvidual Issue with comments
Individual
@quaint cave
latent quiver
as in, if they still support overseerr for a year, then I think we could as well
They issued their final release with the nudge to move to seerr in 1.35.0 but nothing should technically break for the forseeable future
quaint cave
Here's the response when viewing all issues, no comments
Interesting
quaint cave
They issued their final release with the nudge to move to seerr in 1.35.0 but no...
Do they have a security period?
Like I assume if there's a big security issue going that they'd do a patch
boreal veldt
Is media_info missing because the movie hasn't been requested yet?
@quaint cave no, it is always empty. Tested it with multiple movies, released and unreleased
quaint cave
<@80252278073724928> no, it is always empty. Tested it with multiple movies, rel...
No i mean requested
boreal veldt
ah "requested" (I read released), let me check
yeah, when it is requested the media_info is populated
boreal veldt
Is media_info missing because the movie hasn't been requested yet?
so, yes
quaint cave
yeah, when it is requested the media_info is populated
Check!
Let's also add such fixture to the library and HA
boreal veldt
@quaint cave did you check the issue with updating issues and the webhook or shall we address this in new PRs?
https://github.com/joostlek/python-overseerr/pull/323#issuecomment-3904713804
quaint cave
I did not check the issue yet no
In theory we can just create a PR to core that just bumps the dependency
and then we can look into the issue, and rename the thing
Okay I released 0.9.0
boreal veldt
@quaint cave can you send the link to the HA version bump PR? After it's merged I'd like to reopen and finish https://github.com/home-assistant/core/pull/155522
quaint cave
<@80252278073724928> can you send the link to the HA version bump PR? After it's...
I don't have the link at me right now
My first priority now though would be to change the integration to be just Seerr
As today is beta cut and I have a ton to merge still
quaint cave
quaint cave
Can someone help and maybe open a PR for the docs?
boreal veldt
I'll do that on the weekend
boreal veldt
made it from the wrong branch, will rebase tomorrow
boreal veldt
https://github.com/home-assistant/home-assistant.io/pull/43834#pullrequestreview-3871721343
Would it make sense to rename the core integration?
I don't know if it's that easy or if it would have side effect
quaint cave
https://github.com/home-assistant/home-assistant.io/pull/43834#pullrequestreview...
We can rename the name, not the domain
boreal veldt
Shall wen do that?
I can take care of that
What does this involve? Renaming everything but the domain?
quaint cave
I already opened a PR for that