Fix: wrong calculation of nextUpdate when setting custom fetchInterval #1206
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AntsyLich
reviewed
Sep 9, 2024
| @@ -107,7 +107,7 @@ class FetchInterval( | |||
| interval.absoluteValue.takeIf { interval < 0 } | |||
| ?: increaseInterval(interval, timeSinceLatest, increaseWhenOver = 10), | |||
| ) | |||
| return latestDate.plusDays((cycle + 1) * interval.toLong()).toEpochSecond(dateTime.offset) * 1000 | |||
| return latestDate.plusDays((cycle + 1) * interval.absoluteValue.toLong()).toEpochSecond(dateTime.offset) * 1000 | |||
There was a problem hiding this comment.
Should just fix this inside calculateInterval
There was a problem hiding this comment.
calculateInterval is used to automatically calculate the interval based on chapter's release date, when SmartUpdate is set to 'default'.
The case here is when user set a custom SmartUpdate, interval is set to a negative value and used as is, without calling to calculateInterval.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
it was using the negative value of custom fetchInterval to calculate nextUpdate and causing a nextUpdate date in the past