Learn more about these different git repos.
Other Git URLs
commandline operations (git push xx, pagure-admin list-group) result in SQLAlchemy warnings cluttering the screen.
git push xx
pagure-admin list-group
$ git push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 8 threads Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 324 bytes | 64.00 KiB/s, done. Total 3 (delta 0), reused 0 (delta 0) remote: /usr/lib64/python3.8/site-packages/sqlalchemy/orm/relationships.py:1864: SAWarning: Setting backref / back_populates on relationship User.co_projects_admins to refer to viewonly relationship Project.admins will be deprecated in SQLAlchemy 1.4, and will be disallowed in a future release. viewonly relationships should not be mutated (this warning may be suppressed after 10 occurrences) remote: util.warn_limited( ... repeats several tims...
$ pagure-admin list-groups Using configuration file `/etc/pagure/pagure.cfg` /usr/lib64/python3.8/site-packages/sqlalchemy/orm/relationships.py:1864: SAWarning: Setting backref / back_populates on relationship User.co_projects_admins to refer to viewonly relationship Project.admins will be deprecated in SQLAlchemy 1.4, and will be disallowed in a future release. viewonly relationships should not be mutated (this warning may be suppressed after 10 occurrences) util.warn_limited( ...repeats several times... List of groups on this Pagure instance: Group: 1 - name xxxxxx
Is there a way to silence these? Also when Pagure runs into a 'Internal Server Error (500)', is there a log file where we can see what was being attempted that caused error? I ran into this error a few times.
Information for package pagure: ------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : pagure Version : 5.9.1-1.1 Arch : noarch Vendor : openSUSE Installed Size : 16.6 MiB Installed : Yes Status : up-to-date Source package : pagure-5.9.1-1.1.src Summary : A git-centered forge Description :
The SQLAlchemy warnings have been fixed in git already.
Also when Pagure runs into a 'Internal Server Error (500)', is there a log file where we can see what was being attempted that caused error? I ran into this error a few times.
Apache's log file? Or the workers' logs? It depends where the error occurs
Found back the commit: https://pagure.io/pagure/c/5c556b8f050597489aa416fe6d159677da6e81f7?branch=master
The SQLAlchemy warnings have been fixed in git already. Found back the commit: https://pagure.io/pagure/c/5c556b8f050597489aa416fe6d159677da6e81f7?branch=master
So I guess I'll just have to wait till openSUSE updates the package.
The SQLAlchemy warnings have been fixed in git already. Also when Pagure runs into a 'Internal Server Error (500)', is there a log file where we can see what was being attempted that caused error? I ran into this error a few times. Apache's log file? Or the workers' logs? It depends where the error occurs
Looked at apache2 logs, they look normal. Where can I find the workers' log?
@yogmk journalctl -u pagure_worker (for the main worker)
journalctl -u pagure_worker
The SQLAlchemy warnings have been fixed in git already. Found back the commit: https://pagure.io/pagure/c/5c556b8f050597489aa416fe6d159677da6e81f7?branch=master So I guess I'll just have to wait till openSUSE updates the package. The SQLAlchemy warnings have been fixed in git already. Also when Pagure runs into a 'Internal Server Error (500)', is there a log file where we can see what was being attempted that caused error? I ran into this error a few times. Apache's log file? Or the workers' logs? It depends where the error occurs Looked at apache2 logs, they look normal. Where can I find the workers' log?
I was wrong about apache log being normal. The one with error had been archieved (.xz) so missed it. It & journal has similar errors. I'll close this issue and open a new one.
Metadata Update from @yogmk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.