-
Notifications
You must be signed in to change notification settings - Fork 14
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
Testing #101
Conversation
[autopatch] Autopatch to migrate to new permission system
[autopatch] Missing ynh_abort_if_errors in change_url scripts
* Tighten permissions * Check for existence of cache file before chmoding it
Quash the last package_check warning
CI gives us this warning: > ! Using official helper ynh_permission_update implies requiring at least version 3.7.0, but manifest only requires 3.5
!testme |
Upgrade from master fails in my case:
|
@YunoHost-Apps/apps-group you probably know that better than me : I believe the CI test upgrade from latest version, but which precise version ? Latest master ? CI says |
So to what commit that "f75d58cb" is referring to ? Does that works also with a very recently merged commit ? |
in fact, it's |
But if I understand well the summary, it's using this very old commit from 2017 f75d58c, isn't it ? Note: I'm trying to figure out that to know if I discovered a particular issue in my wallabag instance, or a more general bug during the upgrade. |
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.
(Super quick review, LGTM but not super familiar with the app)
I tested again, I have this strange bug again… Can someone else try to upgrade and see if it works correctly ? |
@lapineige I just tried a fresh install (I did not add any article though) and then an upgrade from testing and it looked OK to me: https://paste.yunohost.org/raw/loposuqubo. |
Then that's an issue with my instance… great 😅 |
I did not test on my production instance though, I don't want to lose anything. Does the upgrade fail gracefully on your instance (ie. you don't lose anything and 2.3.8 is still working after the upgrade failure)? |
Yes it does. If you can try it, maybe you can import a few/all articles from your production instance, and try to upgrade ? I wonder how I could solve my bug… I don't understand it 😅 |
OK, I got some errors too on production: https://paste.yunohost.org/raw/vugedeceko |
Also see wallabag/wallabag#4826 |
We are not lucky, that we waited for 2.4.1 to include those fixes, and that we still have the issue 😅 |
! Using official helper ynh_legacy_permissions_delete_all implies requiring at least version 4.1, but manifest only requires 3.7.0 ! Using official helper ynh_legacy_permissions_exists implies requiring at least version 4.1, but manifest only requires 3.7.0
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.
Quick review, LGTM
!testme |
I think we need to wait for a feedback from wallabag/wallabag#5233 The issue I encountered doesn't seem to be specific to my instance, and the CI can't test that. |
OK then, I let you move forward on this :) |
Co-authored-by: Yunohost-Bot <>
Co-authored-by: Yunohost-Bot <>
Wait, did we merged this while you issue mentioned above is not fixed ? I hope that won't break anything… |
Ugh indeed, didn't read that carefully ... At least the backup process before upgrade should still work If you or anybody can confirm the issue, we can revert the merge I guess.. |
Both @nicofrand and I did encounter that issue. The backup is here indeed, but I prefer that people whiling to test come here to test that PR/testing branch than the risk to break a lot of instances and rely on the backup system & stuff like that. 2 people encountering the error is a small sample, I'm not sure it's a frequent issue, but this app is used by many people and I'd prefer to stay a bit conservative, just in case. It's not that difficult to install this branch if someone really need the new version. @alexAubin do you know if a revert can have any (bad) impact on current servers that did upgrade already ? |
Alrighty, I guess reverting should be okay since it was only merged hours ago ... I created a revert-of-the-revert here that we can merge once the upstream issue is resolved : #106 |
At first I was a bit lost, but ok now I understand, #106 is like merging this PR again when we think it is ready. |
Problem
Solution
PR Status