-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Deactivated packages listed on website #97
Comments
hey @Diaoul, I'm not very familiar with the back-end system. What are the next steps to integrating these PRs into the production system? |
I think we need to create a new release. I have GitHub actions to push the relevant docker images. Then on the server a few docker-compose commands should do the trick. |
Hey @Diaoul, I'm not very familiar with releases but I've tried to create a draft (https://github.com/SynoCommunity/spkrepo/releases/tag/untagged-d15132cea06383933b7b). Let me know what you think. It asks for binaries to attach but with the build workflow not working do I just attach the zip file for the codebase? |
Exciting! It looks like there needs to be a version number change somewhere else... the logs seem to be showing an upload attempt of the old version number:
|
Here. My bad I did not check as the tag was present. |
Done, it's building again |
I'll run the update on the server later tonight. |
Upgraded the server. Can you check it is working as you expect? |
I may have to give some time for the caches to update to confirm. Right now I suspect the back-end is a bit busy because I'm getting a mix of "Error 503 first byte timeout" and "Internal Server Error". EDIT: There were also a few other commits since the last release which I don't see PRs for so I hope these aren't causing issues now that the new release is out (which should include these): |
|
@publicarray, can you comment on these commits? Based on the error above, one of these may be causing an error on the server. |
I've pushed a wip branch that I had locally that fixes an issue with the latest flask-security-too, maybe it's worth getting it some love. Currently some tests are failing but I think that's fixable. |
Looks like the fs_uniquifirr column needs to be added to the database |
Weird, I think I reverted the deployment and stuck to the old release instead 🤔 |
That would explain why my python updates still showed up while not yet activated... |
@hgy59, thanks for the perspective. If the download, install and test workflow was for admins then there should be a way for admins to do so via the admin portal (maybe on the build page they could be hyperlinked). If on the other hand, this was supposed to be viewable by the public then I don't see the point of having an activate function at all. |
Inactive packages are not visible in the package center of DSM. |
Really? So when we had this issue (SynoCommunity/spksrc#5798 (comment)) we could have just disabled it rather than deleting it? |
There are still use cases that require the old behaviour. |
In the website URL
https://synocommunity.com/package/[package]
there is listed some packages which are listed even though they are deactivated in the admin interface. Looking at SickBeard we see the following:Admin status:
Website status:
We should not list versions that are not active. Moreover we should not list packages if none of their versions are active.
EDIT: Looking at the code, apparently the second issue was something known as missing:
spkrepo/spkrepo/views/frontend.py
Lines 98 to 99 in 76951e0
The text was updated successfully, but these errors were encountered: