-
Notifications
You must be signed in to change notification settings - Fork 178
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
Release 14.1.4-rc1 #649
Release 14.1.4-rc1 #649
Conversation
As this contains DB migrations I thought doing one rc without rolling out to everyone might not hurt :) |
Codecov Report
@@ Coverage Diff @@
## master #649 +/- ##
=========================================
Coverage 72.13% 72.13%
Complexity 680 680
=========================================
Files 58 58
Lines 2415 2415
=========================================
Hits 1742 1742
Misses 673 673 Continue to review full report at Codecov.
|
Could you add a composer and npm update? |
There is a new feed-io: https://github.com/alexdebril/feed-io/releases/tag/v4.5.4, which then also fixes #640 |
Yea will do that |
npm update was already included, no new updates |
Changed - Basic Media-RSS support (#599) - Database index improvements (#637) Fixed - Call to a member function getUrlHash() on null" when adding a feed (#640) - Don't install symfony/console via composer (#636) - Fix for for ONLY_FULL_GROUP_BY (see #406) (Issue #80) (#407) - Catch invalid feeds (#646) Signed-off-by: Benjamin Brahmer <info@b-brahmer.de>
Changelog and commit message adjusted |
I would appreciate some testing, in my test the DB migration took some time but still ok. Will test the release by personal use for some time. |
I'll also give the RC a test, to see if #607 is still there. It is not yet mentioned in the changelog, but with the bump of feed-io to version 4.5.4 it should be fixed, right? |
Yes it should |
What is the expected behaviour in terms of feeds, that have not been updated for a while? As far as I understood #607, the feeds have been fetched, but under a wrong assumption of the date of last modification, resulting in new items being ignored. As a side effect, the modification date in the database got updated. So I would expect only new items since the update of the news app to show up, because of this logic: news/lib/Fetcher/FeedFetcher.php Lines 85 to 89 in e7fee91
Is this assumption correct? And if so, would it be a good idea to reset the modification date in the database during migration, so the older (missing) feed items get imported, too? |
Changed
Fixed
Signed-off-by: Benjamin Brahmer info@b-brahmer.de