-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Ameba: Fix Lint/UselessAssign #4795
Conversation
@@ -232,7 +232,7 @@ def fetch_channel(ucid, pull_all_videos : Bool) | |||
id: video_id, | |||
title: title, | |||
published: published, | |||
updated: Time.utc, | |||
updated: updated, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not too sure if this should be using the current time Time.utc
or the parsed updated time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's supposed to report the time when the channel content was fetched by the background job. That's especially useful for channels that don't post often, when the last update is for a very old video.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case should there be a new attribute that reports when the video was updated on YouTube's side? Or should we just remove the logic that parses the updated time?
invidious/src/invidious/channels/channels.cr
Lines 208 to 210 in fad0a4f
updated = Time.parse_rfc3339( | |
entry.xpath_node("default:updated", namespaces).not_nil!.content | |
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, my bad. All that time I though we were talking about InvidiousChannel.updated
while you want to change ChannelVideo.updated
.
My previous message applies to the former, and your fix in indeed welcome in the latter case :)
Thank you! |
No description provided.