502 Bad Gateway after ubuntu 20 upgrade Inventree 0.15.1

Deployment Method

[X] Installer
[ ] Docker Development
[ ] Docker Production
[ ] Bare metal Development
[ ] Bare metal Production
[ ] Digital Ocean image
[ ] Other (please provide a link Steps to Reproduce

Describe the problem*
after runnig sudo apt update && sudo apt upgrade and rebooting my Ubuntu 20 machin i am no longer able to connect to inventree. not remote nor local.
i get :

Please instruct me how to fix this.
Steps to Reproduce
sudo apt update && sudo apt upgrade reboot
Relevant log output
No response

You need to check the startup logs of inventree (wherever they may be in your particular case). Error 502 means that nginx wasn't able to connect to the inventree backend, which may in turn mean that it's not even starting.

@shapirus thank you for the hint. But i am just a user of the system. Could you give me a few more hints on what or where i should look.
I found in /opt/inventree/log a setup_xxx.log file from yesterday but i could not find startup logs.
I have checked the status for ngunx but that seems to be running.
Any hints pls i really need inventree to be up and running again.
Br Martijn

This is all specific to your particular setup.  There are many possible ways to start the inventree processes and save (or not save) their logs.
It's best is to ask the person who configured it, or consult the manual/guide which was used to set it up.

I can partly understand but as mentioned im a user and yes i installed inventree myself on a bare ubuntu system.
Its been working well for me so far.
I did nit make any changes would not even know how to. I just followed the baremetal installer instructions.
That said I assume there are default locations where inventree stores this log.
You also refer to a manual where should i be able to find this?
Alternatively there will also be a config somewhere that instructs Inventree how to act where to store its data where to save its logs etc.
Can you guide me there?  Im based in the Netherlands if that helps.
Br martijn

Question,
i'm still not able to get Inventree up. and was googliong on nginx error debugging etc. and found:https://www.linuxbabe.com/linux-server/how-to-fix-common-nginx-errors
they mention: sudo systemctl status php7.4-fpm which is not running on my machine:
sudo systemctl status php7.4-fpm
Unit php7.4-fpm.service could not be found.

But than i'm not sure if its required or not for inventree.
meanwhile i have also tried reinstalling Inventree ( sudo wget -qO install.sh https://get.inventree.org && bash install.sh )
but also that did not resolve my issue.
any hints help is very much apreciated.
br martijn

I found in /opt/inventree/log a setup_xxx.log file from yesterday but i could not find startup logs.

Can you share the logs here? Where there any error messages present in those logs?

Hi Oliver,
thanks :-)
these are the latest files:
-rw-r--r--  1 inventree inventree     0 mei  1 00:00 setup_2024-04-29_17_59_17.log
-rw-r--r--  1 inventree inventree 74886 mei  1 00:00 setup_2024-04-29_17_59_17.log.1
-rw-r--r--  1 root      root          0 mei 18 00:00 setup_2024-05-16_19_05_43.log
-rw-r--r--  1 root      root      51660 mei 18 00:00 setup_2024-05-16_19_05_43.log.1
 cat /opt/inventree/log/setup_2024-05-16_19_05_43.log
 cat /opt/inventree/log/setup_2024-05-16_19_05_43.log.1

and the content of setup_2024-05-16_19_05_43.log.1
# Setting base environment variables
# Using existing config file: /etc/inventree/config.yaml
ERROR: Could not open requirements file: [Errno 2] No such file or directory: '/opt/inventree/.github/requirements.txt'
# Collected environment variables:
#    INVENTREE_MEDIA_ROOT=/opt/inventree/data/media
#    INVENTREE_STATIC_ROOT=/opt/inventree/data/static
#    INVENTREE_BACKUP_DIR=/opt/inventree/data/backup
#    INVENTREE_PLUGINS_ENABLED=true
#    INVENTREE_PLUGIN_FILE=/etc/inventree/plugins.txt
#    INVENTREE_SECRET_KEY_FILE=/etc/inventree/secret_key.txt
#    INVENTREE_DB_ENGINE=sqlite3
#    INVENTREE_DB_NAME=/opt/inventree/data/database.sqlite3
#    INVENTREE_DB_USER=sampleuser
#    INVENTREE_DB_HOST=samplehost
#    INVENTREE_DB_PORT=123456
# Getting the IP address of the server via web service
IP address is xx.xx.xxx.xxx
# Setting up python environment
Requirement already satisfied: invoke in ./env/lib/python3.10/site-packages (2.1.3)
Requirement already satisfied: wheel in ./env/lib/python3.10/site-packages (0.40.0)
# Stopping nginx
# Setting up nginx to /etc/nginx/sites-enabled/inventree.conf
# Starting nginx
# (Re)creating init scripts
Nothing to do.
Nothing to do.
# Enabling InvenTree on boot
# Admin data already exists - skipping
# Stopping InvenTree
# Updating InvenTree
Requirement already satisfied: wheel in ./env/lib/python3.10/site-packages (0.40.0)
# inv update| Installing required python packages from 'src/backend/requirements.txt'
# inv update| Requirement already satisfied: pip in ./env/lib/python3.10/site-packages (24.0)
# inv update| Requirement already satisfied: setuptools in ./env/lib/python3.10/site-packages (69.2.0)
# inv update| Collecting setuptools
# inv update|   Downloading setuptools-69.5.1-py3-none-any.whl.metadata (6.2 kB)
# inv update| Downloading setuptools-69.5.1-py3-none-any.whl (894 kB)
# inv update|    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 894.6/894.6 kB 9.0 MB/s eta 0:00:00
# inv update| Installing collected packages: setuptools
# inv update|   Attempting uninstall: setuptools
# inv update|     Found existing installation: setuptools 69.2.0
# inv update|     Uninstalling setuptools-69.2.0:
# inv update|       Successfully uninstalled setuptools-69.2.0
# inv update| Successfully installed setuptools-69.5.1
# inv update| Collecting asgiref==3.8.1 (from -r src/backend/requirements.txt (line 3))
# inv update|   Downloading asgiref-3.8.1-py3-none-any.whl (23 kB)
# inv update| Requirement already satisfied: async-timeout==4.0.3 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 9)) (4.0.3)
# inv update| Requirement already satisfied: attrs==23.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 13)) (23.2.0)
# inv update| Collecting babel==2.15.0 (from -r src/backend/requirements.txt (line 19))
# inv update|   Downloading Babel-2.15.0-py3-none-any.whl (9.6 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 9.6/9.6 MB 15.7 MB/s eta 0:00:00
# inv update| Requirement already satisfied: bleach==6.1.0 in ./env/lib/python3.10/site-packages (from bleach[css]==6.1.0->-r src/backend/requirements.txt (line 23)) (6.1.0)
# inv update| Requirement already satisfied: brotli==1.1.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 27)) (1.1.0)
# inv update| Requirement already satisfied: certifi==2024.2.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 112)) (2024.2.2)
# inv update| Requirement already satisfied: cffi==1.16.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 118)) (1.16.0)
# inv update| Requirement already satisfied: charset-normalizer==3.3.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 174)) (3.3.2)
# inv update| Requirement already satisfied: coreapi==2.3.3 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 266)) (2.3.3)
# inv update| Requirement already satisfied: coreschema==0.0.4 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 269)) (0.0.4)
# inv update| Collecting cryptography==42.0.7 (from -r src/backend/requirements.txt (line 273))
# inv update|   Downloading cryptography-42.0.7-cp39-abi3-manylinux_2_28_x86_64.whl (3.8 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.8/3.8 MB 19.9 MB/s eta 0:00:00
# inv update| Requirement already satisfied: cssselect2==0.7.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 309)) (0.7.0)
# inv update| Requirement already satisfied: defusedxml==0.7.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 313)) (0.7.1)
# inv update| Requirement already satisfied: deprecated==1.2.14 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 319)) (1.2.14)
# inv update| Requirement already satisfied: diff-match-patch==20230430 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 326)) (20230430)
# inv update| Collecting dj-rest-auth==6.0.0 (from -r src/backend/requirements.txt (line 330))
# inv update|   Downloading dj-rest-auth-6.0.0.tar.gz (220 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 220.0/220.0 kB 17.9 MB/s eta 0:00:00
# inv update|   Preparing metadata (setup.py): started
# inv update|   Preparing metadata (setup.py): finished with status 'done'
# inv update| Collecting django==4.2.12 (from -r src/backend/requirements.txt (line 332))
# inv update|   Downloading Django-4.2.12-py3-none-any.whl (8.0 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 8.0/8.0 MB 19.0 MB/s eta 0:00:00
# inv update| Collecting django-allauth==0.61.1 (from -r src/backend/requirements.txt (line 366))
# inv update|   Downloading django-allauth-0.61.1.tar.gz (951 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 951.5/951.5 kB 20.8 MB/s eta 0:00:00
# inv update|   Installing build dependencies: started
# inv update|   Installing build dependencies: finished with status 'done'
# inv update|   Getting requirements to build wheel: started
# inv update|   Getting requirements to build wheel: finished with status 'done'
# inv update|   Installing backend dependencies: started
# inv update|   Installing backend dependencies: finished with status 'done'
# inv update|   Preparing metadata (pyproject.toml): started
# inv update|   Preparing metadata (pyproject.toml): finished with status 'done'
# inv update| Requirement already satisfied: django-allauth-2fa==0.11.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 369)) (0.11.1)
# inv update| Requirement already satisfied: django-cleanup==8.1.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 372)) (8.1.0)
# inv update| Requirement already satisfied: django-cors-headers==4.3.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 375)) (4.3.1)
# inv update| Requirement already satisfied: django-crispy-forms==1.14.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 378)) (1.14.0)
# inv update| Requirement already satisfied: django-dbbackup==4.1.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 381)) (4.1.0)
# inv update| Requirement already satisfied: django-error-report-2==0.4.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 384)) (0.4.2)
# inv update| Collecting django-filter==24.2 (from -r src/backend/requirements.txt (line 387))
# inv update|   Downloading django_filter-24.2-py3-none-any.whl (94 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 94.5/94.5 kB 14.6 MB/s eta 0:00:00
# inv update| Requirement already satisfied: django-flags==5.0.13 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 390)) (5.0.13)
# inv update| Requirement already satisfied: django-formtools==2.5.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 393)) (2.5.1)
# inv update| Requirement already satisfied: django-ical==1.9.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 396)) (1.9.2)
# inv update| Requirement already satisfied: django-import-export==3.3.7 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 399)) (3.3.7)
# inv update| Requirement already satisfied: django-js-asset==2.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 402)) (2.2.0)
# inv update| Requirement already satisfied: django-maintenance-mode==0.21.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 406)) (0.21.1)
# inv update| Requirement already satisfied: django-markdownify==0.9.3 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 409)) (0.9.3)
# inv update| Requirement already satisfied: django-money==3.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 412)) (3.2.0)
# inv update| Requirement already satisfied: django-mptt==0.16.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 415)) (0.16.0)
# inv update| Collecting django-otp==1.5.0 (from -r src/backend/requirements.txt (line 418))
# inv update|   Downloading django_otp-1.5.0-py3-none-any.whl (80 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 81.0/81.0 kB 4.5 MB/s eta 0:00:00
# inv update| Collecting django-picklefield==3.2 (from -r src/backend/requirements.txt (line 422))
# inv update|   Downloading django_picklefield-3.2-py3-none-any.whl (9.5 kB)
# inv update| Requirement already satisfied: django-q-sentry==0.1.6 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 426)) (0.1.6)
# inv update| Collecting django-q2==1.6.2 (from -r src/backend/requirements.txt (line 428))
# inv update|   Downloading django_q2-1.6.2-py3-none-any.whl (101 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 101.2/101.2 kB 16.3 MB/s eta 0:00:00
# inv update| Requirement already satisfied: django-recurrence==1.11.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 431)) (1.11.1)
# inv update| Requirement already satisfied: django-redis==5.4.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 435)) (5.4.0)
# inv update| Requirement already satisfied: django-sesame==3.2.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 438)) (3.2.2)
# inv update| Requirement already satisfied: django-sql-utils==0.7.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 441)) (0.7.0)
# inv update| Requirement already satisfied: django-sslserver==0.22 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 444)) (0.22)
# inv update| Requirement already satisfied: django-stdimage==6.0.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 446)) (6.0.2)
# inv update| Requirement already satisfied: django-taggit==5.0.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 449)) (5.0.1)
# inv update| Requirement already satisfied: django-user-sessions==2.0.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 452)) (2.0.0)
# inv update| Collecting django-weasyprint==2.3.0 (from -r src/backend/requirements.txt (line 455))
# inv update|   Downloading django_weasyprint-2.3.0-py3-none-any.whl (10 kB)
# inv update| Requirement already satisfied: django-xforwardedfor-middleware==2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 458)) (2.0)
# inv update| Requirement already satisfied: djangorestframework==3.14.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 460)) (3.14.0)
# inv update| Requirement already satisfied: djangorestframework-simplejwt==5.3.1 in ./env/lib/python3.10/site-packages (from djangorestframework-simplejwt[crypto]==5.3.1->-r src/backend/requirements.txt (line 467)) (5.3.1)
# inv update| Collecting drf-spectacular==0.27.2 (from -r src/backend/requirements.txt (line 470))
# inv update|   Downloading drf_spectacular-0.27.2-py3-none-any.whl (102 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 102.9/102.9 kB 12.4 MB/s eta 0:00:00
# inv update| Collecting dulwich==0.22.1 (from -r src/backend/requirements.txt (line 473))
# inv update|   Downloading dulwich-0.22.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (979 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 979.1/979.1 kB 16.4 MB/s eta 0:00:00
# inv update| Requirement already satisfied: et-xmlfile==1.1.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 521)) (1.1.0)
# inv update| Requirement already satisfied: feedparser==6.0.11 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 525)) (6.0.11)
# inv update| Collecting fonttools==4.51.0 (from fonttools[woff]==4.51.0->-r src/backend/requirements.txt (line 528))
# inv update|   Downloading fonttools-4.51.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (4.6 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.6/4.6 MB 16.5 MB/s eta 0:00:00
# inv update| Collecting googleapis-common-protos==1.63.0 (from -r src/backend/requirements.txt (line 572))
# inv update|   Downloading googleapis_common_protos-1.63.0-py2.py3-none-any.whl (229 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 229.1/229.1 kB 11.8 MB/s eta 0:00:00
# inv update| Collecting grpcio==1.63.0 (from -r src/backend/requirements.txt (line 578))
# inv update|   Downloading grpcio-1.63.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.6 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.6/5.6 MB 16.7 MB/s eta 0:00:00
# inv update| Collecting gunicorn==22.0.0 (from -r src/backend/requirements.txt (line 626))
# inv update|   Downloading gunicorn-22.0.0-py3-none-any.whl (84 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 84.4/84.4 kB 17.9 MB/s eta 0:00:00
# inv update| Requirement already satisfied: html5lib==1.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 629)) (1.1)
# inv update| Collecting icalendar==5.0.12 (from -r src/backend/requirements.txt (line 633))
# inv update|   Downloading icalendar-5.0.12-py3-none-any.whl (116 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 116.3/116.3 kB 11.7 MB/s eta 0:00:00
# inv update| Collecting idna==3.7 (from -r src/backend/requirements.txt (line 637))
# inv update|   Downloading idna-3.7-py3-none-any.whl (66 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 66.8/66.8 kB 17.1 MB/s eta 0:00:00
# inv update| Collecting importlib-metadata==7.0.0 (from -r src/backend/requirements.txt (line 641))
# inv update|   Downloading importlib_metadata-7.0.0-py3-none-any.whl (23 kB)
# inv update| Requirement already satisfied: inflection==0.5.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 648)) (0.5.1)
# inv update| Requirement already satisfied: itypes==1.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 652)) (1.2.0)
# inv update| Collecting jinja2==3.1.4 (from -r src/backend/requirements.txt (line 656))
# inv update|   Downloading jinja2-3.1.4-py3-none-any.whl (133 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 133.3/133.3 kB 8.5 MB/s eta 0:00:00
# inv update| Collecting jsonschema==4.22.0 (from -r src/backend/requirements.txt (line 660))
# inv update|   Downloading jsonschema-4.22.0-py3-none-any.whl (88 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 88.3/88.3 kB 15.5 MB/s eta 0:00:00
# inv update| Requirement already satisfied: jsonschema-specifications==2023.12.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 664)) (2023.12.1)
# inv update| Collecting markdown==3.6 (from -r src/backend/requirements.txt (line 668))
# inv update|   Downloading Markdown-3.6-py3-none-any.whl (105 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 105.4/105.4 kB 14.2 MB/s eta 0:00:00
# inv update| Requirement already satisfied: markuppy==1.14 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 672)) (1.14)
# inv update| Requirement already satisfied: markupsafe==2.1.5 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 675)) (2.1.5)
# inv update| Requirement already satisfied: oauthlib==3.2.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 737)) (3.2.2)
# inv update| Requirement already satisfied: odfpy==1.4.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 741)) (1.4.1)
# inv update| Requirement already satisfied: openpyxl==3.1.2 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 744)) (3.1.2)
# inv update| Collecting opentelemetry-api==1.24.0 (from -r src/backend/requirements.txt (line 748))
# inv update|   Downloading opentelemetry_api-1.24.0-py3-none-any.whl (60 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.1/60.1 kB 12.1 MB/s eta 0:00:00
# inv update| Collecting opentelemetry-exporter-otlp==1.24.0 (from -r src/backend/requirements.txt (line 760))
# inv update|   Downloading opentelemetry_exporter_otlp-1.24.0-py3-none-any.whl (7.0 kB)
# inv update| Collecting opentelemetry-exporter-otlp-proto-common==1.24.0 (from -r src/backend/requirements.txt (line 763))
# inv update|   Downloading opentelemetry_exporter_otlp_proto_common-1.24.0-py3-none-any.whl (17 kB)
# inv update| Collecting opentelemetry-exporter-otlp-proto-grpc==1.24.0 (from -r src/backend/requirements.txt (line 769))
# inv update|   Downloading opentelemetry_exporter_otlp_proto_grpc-1.24.0-py3-none-any.whl (18 kB)
# inv update| Collecting opentelemetry-exporter-otlp-proto-http==1.24.0 (from -r src/backend/requirements.txt (line 773))
# inv update|   Downloading opentelemetry_exporter_otlp_proto_http-1.24.0-py3-none-any.whl (16 kB)
# inv update| Collecting opentelemetry-instrumentation==0.45b0 (from -r src/backend/requirements.txt (line 777))
# inv update|   Downloading opentelemetry_instrumentation-0.45b0-py3-none-any.whl (28 kB)
# inv update| Collecting opentelemetry-instrumentation-django==0.45b0 (from -r src/backend/requirements.txt (line 785))
# inv update|   Downloading opentelemetry_instrumentation_django-0.45b0-py3-none-any.whl (18 kB)
# inv update| Collecting opentelemetry-instrumentation-redis==0.45b0 (from -r src/backend/requirements.txt (line 788))
# inv update|   Downloading opentelemetry_instrumentation_redis-0.45b0-py3-none-any.whl (11 kB)
# inv update| Collecting opentelemetry-instrumentation-requests==0.45b0 (from -r src/backend/requirements.txt (line 791))
# inv update|   Downloading opentelemetry_instrumentation_requests-0.45b0-py3-none-any.whl (12 kB)
# inv update| Collecting opentelemetry-instrumentation-wsgi==0.45b0 (from -r src/backend/requirements.txt (line 794))
# inv update|   Downloading opentelemetry_instrumentation_wsgi-0.45b0-py3-none-any.whl (13 kB)
# inv update| Collecting opentelemetry-proto==1.24.0 (from -r src/backend/requirements.txt (line 798))
# inv update|   Downloading opentelemetry_proto-1.24.0-py3-none-any.whl (50 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 50.8/50.8 kB 9.3 MB/s eta 0:00:00
# inv update| Collecting opentelemetry-sdk==1.24.0 (from -r src/backend/requirements.txt (line 805))
# inv update|   Downloading opentelemetry_sdk-1.24.0-py3-none-any.whl (106 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 106.1/106.1 kB 18.8 MB/s eta 0:00:00
# inv update| Collecting opentelemetry-semantic-conventions==0.45b0 (from -r src/backend/requirements.txt (line 811))
# inv update|   Downloading opentelemetry_semantic_conventions-0.45b0-py3-none-any.whl (36 kB)
# inv update| Collecting opentelemetry-util-http==0.45b0 (from -r src/backend/requirements.txt (line 820))
# inv update|   Downloading opentelemetry_util_http-0.45b0-py3-none-any.whl (6.9 kB)
# inv update| Collecting packaging==24.0 (from -r src/backend/requirements.txt (line 827))
# inv update|   Downloading packaging-24.0-py3-none-any.whl (53 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 53.5/53.5 kB 29.8 MB/s eta 0:00:00
# inv update| Requirement already satisfied: pdf2image==1.17.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 831)) (1.17.0)
# inv update| Collecting pillow==10.3.0 (from -r src/backend/requirements.txt (line 834))
# inv update|   Downloading pillow-10.3.0-cp310-cp310-manylinux_2_28_x86_64.whl (4.5 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.5/4.5 MB 8.6 MB/s eta 0:00:00
# inv update| Requirement already satisfied: pint==0.21 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 910)) (0.21)
# inv update| Collecting pip-licenses==4.4.0 (from -r src/backend/requirements.txt (line 913))
# inv update|   Downloading pip_licenses-4.4.0-py3-none-any.whl (20 kB)
# inv update| Collecting prettytable==3.10.0 (from -r src/backend/requirements.txt (line 916))
# inv update|   Downloading prettytable-3.10.0-py3-none-any.whl (28 kB)
# inv update| Collecting protobuf==4.25.3 (from -r src/backend/requirements.txt (line 920))
# inv update|   Downloading protobuf-4.25.3-cp37-abi3-manylinux2014_x86_64.whl (294 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 294.6/294.6 kB 7.2 MB/s eta 0:00:00
# inv update| Requirement already satisfied: py-moneyed==3.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 935)) (3.0)
# inv update| Collecting pycparser==2.22 (from -r src/backend/requirements.txt (line 939))
# inv update|   Downloading pycparser-2.22-py3-none-any.whl (117 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 117.6/117.6 kB 9.7 MB/s eta 0:00:00
# inv update| Collecting pydyf==0.10.0 (from -r src/backend/requirements.txt (line 943))
# inv update|   Downloading pydyf-0.10.0-py3-none-any.whl (8.1 kB)
# inv update| Requirement already satisfied: pyjwt==2.8.0 in ./env/lib/python3.10/site-packages (from pyjwt[crypto]==2.8.0->-r src/backend/requirements.txt (line 947)) (2.8.0)
# inv update| Collecting pyphen==0.15.0 (from -r src/backend/requirements.txt (line 953))
# inv update|   Downloading pyphen-0.15.0-py3-none-any.whl (2.1 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 11.5 MB/s eta 0:00:00
# inv update| Requirement already satisfied: pypng==0.20220715.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 957)) (0.20220715.0)
# inv update| Requirement already satisfied: python-barcode==0.15.1 in ./env/lib/python3.10/site-packages (from python-barcode[images]==0.15.1->-r src/backend/requirements.txt (line 961)) (0.15.1)
# inv update| Collecting python-dateutil==2.9.0.post0 (from -r src/backend/requirements.txt (line 964))
# inv update|   Downloading python_dateutil-2.9.0.post0-py2.py3-none-any.whl (229 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 229.9/229.9 kB 12.8 MB/s eta 0:00:00
# inv update| Requirement already satisfied: python-dotenv==1.0.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 970)) (1.0.1)
# inv update| Collecting python-fsutil==0.14.1 (from -r src/backend/requirements.txt (line 973))
# inv update|   Downloading python_fsutil-0.14.1-py3-none-any.whl (16 kB)
# inv update| Requirement already satisfied: python3-openid==3.2.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 977)) (3.2.0)
# inv update| Requirement already satisfied: pytz==2024.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 981)) (2024.1)
# inv update| Requirement already satisfied: pyyaml==6.0.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 988)) (6.0.1)
# inv update| Requirement already satisfied: qrcode==7.4.2 in ./env/lib/python3.10/site-packages (from qrcode[pil]==7.4.2->-r src/backend/requirements.txt (line 1043)) (7.4.2)
# inv update| Collecting rapidfuzz==3.9.0 (from -r src/backend/requirements.txt (line 1047))
# inv update|   Downloading rapidfuzz-3.9.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.4 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.4/3.4 MB 11.5 MB/s eta 0:00:00
# inv update| Collecting redis==5.0.4 (from -r src/backend/requirements.txt (line 1138))
# inv update|   Downloading redis-5.0.4-py3-none-any.whl (251 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 252.0/252.0 kB 9.9 MB/s eta 0:00:00
# inv update| Collecting referencing==0.35.1 (from -r src/backend/requirements.txt (line 1142))
# inv update|   Downloading referencing-0.35.1-py3-none-any.whl (26 kB)
# inv update| Collecting regex==2024.4.28 (from -r src/backend/requirements.txt (line 1148))
# inv update|   Downloading regex-2024.4.28-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (774 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 774.1/774.1 kB 11.3 MB/s eta 0:00:00
# inv update| Requirement already satisfied: requests==2.31.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1228)) (2.31.0)
# inv update| Collecting requests-oauthlib==2.0.0 (from -r src/backend/requirements.txt (line 1236))
# inv update|   Downloading requests_oauthlib-2.0.0-py2.py3-none-any.whl (24 kB)
# inv update| Collecting rpds-py==0.18.1 (from -r src/backend/requirements.txt (line 1240))
# inv update|   Downloading rpds_py-0.18.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.1 MB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 12.0 MB/s eta 0:00:00
# inv update| Collecting sentry-sdk==2.1.1 (from -r src/backend/requirements.txt (line 1343))
# inv update|   Downloading sentry_sdk-2.1.1-py2.py3-none-any.whl (277 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 277.3/277.3 kB 7.4 MB/s eta 0:00:00
# inv update| Requirement already satisfied: setuptools==69.5.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1347)) (69.5.1)
# inv update| Requirement already satisfied: sgmllib3k==1.0.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1353)) (1.0.0)
# inv update| Requirement already satisfied: six==1.16.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1356)) (1.16.0)
# inv update| Collecting sqlparse==0.5.0 (from -r src/backend/requirements.txt (line 1363))
# inv update|   Downloading sqlparse-0.5.0-py3-none-any.whl (43 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 44.0/44.0 kB 20.0 MB/s eta 0:00:00
# inv update| Requirement already satisfied: tablib==3.5.0 in ./env/lib/python3.10/site-packages (from tablib[html,ods,xls,xlsx,yaml]==3.5.0->-r src/backend/requirements.txt (line 1369)) (3.5.0)
# inv update| Requirement already satisfied: tinycss2==1.2.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirementsWARNING: The candidate selected for download or install is a yanked version: 'django' candidate (version 4.2.12 at https://files.pythonhosted.org/packages/13/b3/4462fc6d771763a273590ecd6e535f284e057f5b8cc1dd41fca774b1072c/Django-4.2.12-py3-none-any.whl (from https://pypi.org/simple/django/) (requires-python:>=3.8))
Reason for being yanked: Release files have Windows end-of-line characters and are missing executable bits.
.txt (line 1373)) (1.2.1)
# inv update| Collecting typing-extensions==4.11.0 (from -r src/backend/requirements.txt (line 1380))
# inv update|   Downloading typing_extensions-4.11.0-py3-none-any.whl (34 kB)
# inv update| Requirement already satisfied: uritemplate==4.1.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1389)) (4.1.1)
# inv update| Collecting urllib3==2.2.1 (from -r src/backend/requirements.txt (line 1395))
# inv update|   Downloading urllib3-2.2.1-py3-none-any.whl (121 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 121.1/121.1 kB 8.3 MB/s eta 0:00:00
# inv update| Collecting wcwidth==0.2.13 (from -r src/backend/requirements.txt (line 1402))
# inv update|   Downloading wcwidth-0.2.13-py2.py3-none-any.whl (34 kB)
# inv update| Collecting weasyprint==61.2 (from -r src/backend/requirements.txt (line 1406))
# inv update|   Downloading weasyprint-61.2-py3-none-any.whl (271 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 271.5/271.5 kB 14.5 MB/s eta 0:00:00
# inv update| Requirement already satisfied: webencodings==0.5.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1410)) (0.5.1)
# inv update| Collecting whitenoise==6.6.0 (from -r src/backend/requirements.txt (line 1418))
# inv update|   Downloading whitenoise-6.6.0-py3-none-any.whl (19 kB)
# inv update| Requirement already satisfied: wrapt==1.16.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1421)) (1.16.0)
# inv update| Requirement already satisfied: xlrd==2.0.1 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1496)) (2.0.1)
# inv update| Requirement already satisfied: xlwt==1.3.0 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1500)) (1.3.0)
# inv update| Collecting zipp==3.18.1 (from -r src/backend/requirements.txt (line 1504))
# inv update|   Downloading zipp-3.18.1-py3-none-any.whl (8.2 kB)
# inv update| Requirement already satisfied: zopfli==0.2.3 in ./env/lib/python3.10/site-packages (from -r src/backend/requirements.txt (line 1508)) (0.2.3)
# inv update| Building wheels for collected packages: dj-rest-auth, django-allauth
# inv update|   Building wheel for dj-rest-auth (setup.py): started
# inv update|   Building wheel for dj-rest-auth (setup.py): finished with status 'done'
# inv update|   Created wheel for dj-rest-auth: filename=dj_rest_auth-6.0.0-py2.py3-none-any.whl size=250774 sha256=68e1e23e44a84a23a92406d211066c8ffaad0260e68732da81dc8041c4720132
# inv update|   Stored in directory: /tmp/pip-ephem-wheel-cache-2uv1gs4f/wheels/52/57/bc/bf75e7a58965bd0cc7a862d657204e049bbd63567d8ca2bc75
# inv update|   Building wheel for django-allauth (pyproject.toml): started
# inv update|   Building wheel for django-allauth (pyproject.toml): finished with status 'done'
# inv update|   Created wheel for django-allauth: filename=django_allauth-0.61.1-py3-none-any.whl size=1259785 sha256=524dc8e0033146fa8468e8fcb30b8c3975f89e6a1ac66fab74e0e71d5d709a8c
# inv update|   Stored in directory: /tmp/pip-ephem-wheel-cache-2uv1gs4f/wheels/b8/8e/55/e239a6c337430c7d00d97240cd7ad7bda03959ad6b02916ca4
# inv update| Successfully built dj-rest-auth django-allauth
# inv update| Installing collected packages: wcwidth, python-fsutil, zipp, whitenoise, urllib3, typing-extensions, sqlparse, rpds-py, regex, redis, rapidfuzz, python-dateutil, pyphen, pydyf, pycparser, protobuf, prettytable, pillow, packaging, opentelemetry-util-http, opentelemetry-semantic-conventions, markdown, jinja2, idna, grpcio, fonttools, babel, sentry-sdk, referencing, pip-licenses, opentelemetry-proto, importlib-metadata, icalendar, gunicorn, googleapis-common-protos, dulwich, asgiref, weasyprint, requests-oauthlib, opentelemetry-exporter-otlp-proto-common, opentelemetry-api, django, cryptography, opentelemetry-sdk, opentelemetry-instrumentation, jsonschema, django-weasyprint, django-picklefield, django-otp, django-filter, opentelemetry-instrumentation-wsgi, opentelemetry-instrumentation-requests, opentelemetry-instrumentation-redis, opentelemetry-exporter-otlp-proto-http, opentelemetry-exporter-otlp-proto-grpc, drf-spectacular, django-q2, django-allauth, dj-rest-auth, opentelemetry-instrumentation-django, opentelemetry-exporter-otlp
# inv update|   Attempting uninstall: wcwidth
# inv update|     Found existing installation: wcwidth 0.2.6
# inv update|     Uninstalling wcwidth-0.2.6:
# inv update|       Successfully uninstalled wcwidth-0.2.6
# inv update|   Attempting uninstall: python-fsutil
# inv update|     Found existing installation: python-fsutil 0.13.1
# inv update|     Uninstalling python-fsutil-0.13.1:
# inv update|       Successfully uninstalled python-fsutil-0.13.1
# inv update|   Attempting uninstall: zipp
# inv update|     Found existing installation: zipp 3.17.0
# inv update|     Uninstalling zipp-3.17.0:
# inv update|       Successfully uninstalled zipp-3.17.0
# inv update|   Attempting uninstall: urllib3
# inv update|     Found existing installation: urllib3 2.2.0
# inv update|     Uninstalling urllib3-2.2.0:
# inv update|       Successfully uninstalled urllib3-2.2.0
# inv update|   Attempting uninstall: typing-extensions
# inv update|     Found existing installation: typing_extensions 4.9.0
# inv update|     Uninstalling typing_extensions-4.9.0:
# inv update|       Successfully uninstalled typing_extensions-4.9.0
# inv update|   Attempting uninstall: sqlparse
# inv update|     Found existing installation: sqlparse 0.4.4
# inv update|     Uninstalling sqlparse-0.4.4:
# inv update|       Successfully uninstalled sqlparse-0.4.4
# inv update|   Attempting uninstall: rpds-py
# inv update|     Found existing installation: rpds-py 0.17.1
# inv update|     Uninstalling rpds-py-0.17.1:
# inv update|       Successfully uninstalled rpds-py-0.17.1
# inv update|   Attempting uninstall: regex
# inv update|     Found existing installation: regex 2023.12.25
# inv update|     Uninstalling regex-2023.12.25:
# inv update|       Successfully uninstalled regex-2023.12.25
# inv update|   Attempting uninstall: redis
# inv update|     Found existing installation: redis 5.0.1
# inv update|     Uninstalling redis-5.0.1:
# inv update|       Successfully uninstalled redis-5.0.1
# inv update|   Attempting uninstall: rapidfuzz
# inv update|     Found existing installation: rapidfuzz 3.6.1
# inv update|     Uninstalling rapidfuzz-3.6.1:
# inv update|       Successfully uninstalled rapidfuzz-3.6.1
# inv update|   Attempting uninstall: python-dateutil
# inv update|     Found existing installation: python-dateutil 2.8.2
# inv update|     Uninstalling python-dateutil-2.8.2:
# inv update|       Successfully uninstalled python-dateutil-2.8.2
# inv update|   Attempting uninstall: pyphen
# inv update|     Found existing installation: pyphen 0.14.0
# inv update|     Uninstalling pyphen-0.14.0:
# inv update|       Successfully uninstalled pyphen-0.14.0
# inv update|   Attempting uninstall: pydyf
# inv update|     Found existing installation: pydyf 0.8.0
# inv update|     Uninstalling pydyf-0.8.0:
# inv update|       Successfully uninstalled pydyf-0.8.0
# inv update|   Attempting uninstall: pycparser
# inv update|     Found existing installation: pycparser 2.21
# inv update|     Uninstalling pycparser-2.21:
# inv update|       Successfully uninstalled pycparser-2.21
# inv update|   Attempting uninstall: protobuf
# inv update|     Found existing installation: protobuf 4.25.2
# inv update|     Uninstalling protobuf-4.25.2:
# inv update|       Successfully uninstalled protobuf-4.25.2
# inv update|   Attempting uninstall: pillow
# inv update|     Found existing installation: pillow 10.2.0
# inv update|     Uninstalling pillow-10.2.0:
# inv update|       Successfully uninstalled pillow-10.2.0
# inv update|   Attempting uninstall: packaging
# inv update|     Found existing installation: packaging 23.2
# inv update|     Uninstalling packaging-23.2:
# inv update|       Successfully uninstalled packaging-23.2
# inv update|   Attempting uninstall: opentelemetry-util-http
# inv update|     Found existing installation: opentelemetry-util-http 0.43b0
# inv update|     Uninstalling opentelemetry-util-http-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-util-http-0.43b0
# inv update|   Attempting uninstall: opentelemetry-semantic-conventions
# inv update|     Found existing installation: opentelemetry-semantic-conventions 0.43b0
# inv update|     Uninstalling opentelemetry-semantic-conventions-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-semantic-conventions-0.43b0
# inv update|   Attempting uninstall: markdown
# inv update|     Found existing installation: Markdown 3.5.2
# inv update|     Uninstalling Markdown-3.5.2:
# inv update|       Successfully uninstalled Markdown-3.5.2
# inv update|   Attempting uninstall: jinja2
# inv update|     Found existing installation: Jinja2 3.1.3
# inv update|     Uninstalling Jinja2-3.1.3:
# inv update|       Successfully uninstalled Jinja2-3.1.3
# inv update|   Attempting uninstall: idna
# inv update|     Found existing installation: idna 3.6
# inv update|     Uninstalling idna-3.6:
# inv update|       Successfully uninstalled idna-3.6
# inv update|   Attempting uninstall: grpcio
# inv update|     Found existing installation: grpcio 1.54.2
# inv update|     Uninstalling grpcio-1.54.2:
# inv update|       Successfully uninstalled grpcio-1.54.2
# inv update|   Attempting uninstall: fonttools
# inv update|     Found existing installation: fonttools 4.47.2
# inv update|     Uninstalling fonttools-4.47.2:
# inv update|       Successfully uninstalled fonttools-4.47.2
# inv update|   Attempting uninstall: babel
# inv update|     Found existing installation: Babel 2.14.0
# inv update|     Uninstalling Babel-2.14.0:
# inv update|       Successfully uninstalled Babel-2.14.0
# inv update|   Attempting uninstall: sentry-sdk
# inv update|     Found existing installation: sentry-sdk 1.40.0
# inv update|     Uninstalling sentry-sdk-1.40.0:
# inv update|       Successfully uninstalled sentry-sdk-1.40.0
# inv update|   Attempting uninstall: referencing
# inv update|     Found existing installation: referencing 0.33.0
# inv update|     Uninstalling referencing-0.33.0:
# inv update|       Successfully uninstalled referencing-0.33.0
# inv update|   Attempting uninstall: opentelemetry-proto
# inv update|     Found existing installation: opentelemetry-proto 1.22.0
# inv update|     Uninstalling opentelemetry-proto-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-proto-1.22.0
# inv update|   Attempting uninstall: importlib-metadata
# inv update|     Found existing installation: importlib-metadata 6.11.0
# inv update|     Uninstalling importlib-metadata-6.11.0:
# inv update|       Successfully uninstalled importlib-metadata-6.11.0
# inv update|   Attempting uninstall: icalendar
# inv update|     Found existing installation: icalendar 5.0.11
# inv update|     Uninstalling icalendar-5.0.11:
# inv update|       Successfully uninstalled icalendar-5.0.11
# inv update|   Attempting uninstall: gunicorn
# inv update|     Found existing installation: gunicorn 21.2.0
# inv update|     Uninstalling gunicorn-21.2.0:
# inv update|       Successfully uninstalled gunicorn-21.2.0
# inv update|   Attempting uninstall: googleapis-common-protos
# inv update|     Found existing installation: googleapis-common-protos 1.62.0
# inv update|     Uninstalling googleapis-common-protos-1.62.0:
# inv update|       Successfully uninstalled googleapis-common-protos-1.62.0
# inv update|   Attempting uninstall: dulwich
# inv update|     Found existing installation: dulwich 0.21.7
# inv update|     Uninstalling dulwich-0.21.7:
# inv update|       Successfully uninstalled dulwich-0.21.7
# inv update|   Attempting uninstall: asgiref
# inv update|     Found existing installation: asgiref 3.7.2
# inv update|     Uninstalling asgiref-3.7.2:
# inv update|       Successfully uninstalled asgiref-3.7.2
# inv update|   Attempting uninstall: weasyprint
# inv update|     Found existing installation: weasyprint 60.2
# inv update|     Uninstalling weasyprint-60.2:
# inv update|       Successfully uninstalled weasyprint-60.2
# inv update|   Attempting uninstall: requests-oauthlib
# inv update|     Found existing installation: requests-oauthlib 1.3.1
# inv update|     Uninstalling requests-oauthlib-1.3.1:
# inv update|       Successfully uninstalled requests-oauthlib-1.3.1
# inv update|   Attempting uninstall: opentelemetry-exporter-otlp-proto-common
# inv update|     Found existing installation: opentelemetry-exporter-otlp-proto-common 1.22.0
# inv update|     Uninstalling opentelemetry-exporter-otlp-proto-common-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-exporter-otlp-proto-common-1.22.0
# inv update|   Attempting uninstall: opentelemetry-api
# inv update|     Found existing installation: opentelemetry-api 1.22.0
# inv update|     Uninstalling opentelemetry-api-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-api-1.22.0
# inv update|   Attempting uninstall: django
# inv update|     Found existing installation: Django 4.2.11
# inv update|     Uninstalling Django-4.2.11:
# inv update|       Successfully uninstalled Django-4.2.11
# inv update|   Attempting uninstall: cryptography
# inv update|     Found existing installation: cryptography 42.0.4
# inv update|     Uninstalling cryptography-42.0.4:
# inv update|       Successfully uninstalled cryptography-42.0.4
# inv update|   Attempting uninstall: opentelemetry-sdk
# inv update|     Found existing installation: opentelemetry-sdk 1.22.0
# inv update|     Uninstalling opentelemetry-sdk-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-sdk-1.22.0
# inv update|   Attempting uninstall: opentelemetry-instrumentation
# inv update|     Found existing installation: opentelemetry-instrumentation 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-instrumentation-0.43b0
# inv update|   Attempting uninstall: jsonschema
# inv update|     Found existing installation: jsonschema 4.21.1
# inv update|     Uninstalling jsonschema-4.21.1:
# inv update|       Successfully uninstalled jsonschema-4.21.1
# inv update|   Attempting uninstall: django-weasyprint
# inv update|     Found existing installation: django-weasyprint 2.2.2
# inv update|     Uninstalling django-weasyprint-2.2.2:
# inv update|       Successfully uninstalled django-weasyprint-2.2.2
# inv update|   Attempting uninstall: django-picklefield
# inv update|     Found existing installation: django-picklefield 3.1
# inv update|     Uninstalling django-picklefield-3.1:
# inv update|       Successfully uninstalled django-picklefield-3.1
# inv update|   Attempting uninstall: django-otp
# inv update|     Found existing installation: django-otp 1.3.0
# inv update|     Uninstalling django-otp-1.3.0:
# inv update|       Successfully uninstalled django-otp-1.3.0
# inv update|   Attempting uninstall: django-filter
# inv update|     Found existing installation: django-filter 23.5
# inv update|     Uninstalling django-filter-23.5:
# inv update|       Successfully uninstalled django-filter-23.5
# inv update|   Attempting uninstall: opentelemetry-instrumentation-wsgi
# inv update|     Found existing installation: opentelemetry-instrumentation-wsgi 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-wsgi-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-instrumentation-wsgi-0.43b0
# inv update|   Attempting uninstall: opentelemetry-instrumentation-requests
# inv update|     Found existing installation: opentelemetry-instrumentation-requests 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-requests-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-instrumentation-requests-0.43b0
# inv update|   Attempting uninstall: opentelemetry-instrumentation-redis
# inv update|     Found existing installation: opentelemetry-instrumentation-redis 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-redis-0.43b0:
# inv update|       Successfully uniERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
django-q 1.3.9 requires redis<4.0.0,>=3.5.3, but you have redis 5.0.4 which is incompatible.
2024-05-16 19:06:34,389 ERROR No CSRF_TRUSTED_ORIGINS specified. Please provide a list of trusted origins, or specify INVENTREE_SITE_URL
nstalled opentelemetry-instrumentation-redis-0.43b0
# inv update|   Attempting uninstall: opentelemetry-exporter-otlp-proto-http
# inv update|     Found existing installation: opentelemetry-exporter-otlp-proto-http 1.22.0
# inv update|     Uninstalling opentelemetry-exporter-otlp-proto-http-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-exporter-otlp-proto-http-1.22.0
# inv update|   Attempting uninstall: opentelemetry-exporter-otlp-proto-grpc
# inv update|     Found existing installation: opentelemetry-exporter-otlp-proto-grpc 1.22.0
# inv update|     Uninstalling opentelemetry-exporter-otlp-proto-grpc-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-exporter-otlp-proto-grpc-1.22.0
# inv update|   Attempting uninstall: drf-spectacular
# inv update|     Found existing installation: drf-spectacular 0.27.1
# inv update|     Uninstalling drf-spectacular-0.27.1:
# inv update|       Successfully uninstalled drf-spectacular-0.27.1
# inv update|   Attempting uninstall: django-q2
# inv update|     Found existing installation: django-q2 1.6.1
# inv update|     Uninstalling django-q2-1.6.1:
# inv update|       Successfully uninstalled django-q2-1.6.1
# inv update|   Attempting uninstall: django-allauth
# inv update|     Found existing installation: django-allauth 0.60.1
# inv update|     Uninstalling django-allauth-0.60.1:
# inv update|       Successfully uninstalled django-allauth-0.60.1
# inv update|   Attempting uninstall: dj-rest-auth
# inv update|     Found existing installation: dj-rest-auth 5.0.2
# inv update|     Uninstalling dj-rest-auth-5.0.2:
# inv update|       Successfully uninstalled dj-rest-auth-5.0.2
# inv update|   Attempting uninstall: opentelemetry-instrumentation-django
# inv update|     Found existing installation: opentelemetry-instrumentation-django 0.43b0
# inv update|     Uninstalling opentelemetry-instrumentation-django-0.43b0:
# inv update|       Successfully uninstalled opentelemetry-instrumentation-django-0.43b0
# inv update|   Attempting uninstall: opentelemetry-exporter-otlp
# inv update|     Found existing installation: opentelemetry-exporter-otlp 1.22.0
# inv update|     Uninstalling opentelemetry-exporter-otlp-1.22.0:
# inv update|       Successfully uninstalled opentelemetry-exporter-otlp-1.22.0
# inv update| Successfully installed asgiref-3.8.1 babel-2.15.0 cryptography-42.0.7 dj-rest-auth-6.0.0 django-4.2.12 django-allauth-0.61.1 django-filter-24.2 django-otp-1.5.0 django-picklefield-3.2 django-q2-1.6.2 django-weasyprint-2.3.0 drf-spectacular-0.27.2 dulwich-0.22.1 fonttools-4.51.0 googleapis-common-protos-1.63.0 grpcio-1.63.0 gunicorn-22.0.0 icalendar-5.0.12 idna-3.7 importlib-metadata-7.0.0 jinja2-3.1.4 jsonschema-4.22.0 markdown-3.6 opentelemetry-api-1.24.0 opentelemetry-exporter-otlp-1.24.0 opentelemetry-exporter-otlp-proto-common-1.24.0 opentelemetry-exporter-otlp-proto-grpc-1.24.0 opentelemetry-exporter-otlp-proto-http-1.24.0 opentelemetry-instrumentation-0.45b0 opentelemetry-instrumentation-django-0.45b0 opentelemetry-instrumentation-redis-0.45b0 opentelemetry-instrumentation-requests-0.45b0 opentelemetry-instrumentation-wsgi-0.45b0 opentelemetry-proto-1.24.0 opentelemetry-sdk-1.24.0 opentelemetry-semantic-conventions-0.45b0 opentelemetry-util-http-0.45b0 packaging-24.0 pillow-10.3.0 pip-licenses-4.4.0 prettytable-3.10.0 protobuf-4.25.3 pycparser-2.22 pydyf-0.10.0 pyphen-0.15.0 python-dateutil-2.9.0.post0 python-fsutil-0.14.1 rapidfuzz-3.9.0 redis-5.0.4 referencing-0.35.1 regex-2024.4.28 requests-oauthlib-2.0.0 rpds-py-0.18.1 sentry-sdk-2.1.1 sqlparse-0.5.0 typing-extensions-4.11.0 urllib3-2.2.1 wcwidth-0.2.13 weasyprint-61.2 whitenoise-6.6.0 zipp-3.18.1
# inv update| Installing plugin packages from '/etc/inventree/plugins.txt'
# inv update| Backing up InvenTree database...
# inv update| Python version 3.10.12 - /opt/inventree/env/bin/python3
# Set permissions for data dir and media: /opt/inventree/data
# Starting InvenTree
####################################################################################
This InvenTree install uses nginx, the settings for the webserver can be found in
/etc/nginx/sites-enabled/inventree.conf
Try opening InvenTree with either
http://localhost/ or http://xx.xx.xx.xx/

Admin user data:
   Email:
   Username:
   Password:
####################################################################################

Pls let me know if you require more.
Br Martijn

@matmair the error message at the start of the log looks suspicious to me:

ERROR: Could not open requirements file: [Errno 2] No such file or directory: '/opt/inventree/.github/requirements.txt'

Is this potentially a mangled path in the installer since we split the source code into the new directories?

have the same issue with a fresh install on a vm, within the logs i only found user warnings. not that he couldnt find the requirements.txt.

have the same issue with a fresh install on a vm, within the logs i only found user warnings. not that he couldnt find the requirements.txt.

Just fixed my error. in the config there is a line for INVENTREE_SITE_URL:

uncomment that, that was my problem it couldnt find a base url.

@mabroens can you see if setting the INVENTREE_SITE_URL param in your config file addresses the issue?

Hi Oliver,
I had seen the post and will try but can you be more specific to what config file.
/opt/inventree/conf.yaml?? Or another one

@asscherhofstede can you please specify exactly which config file you adjusted?

/etc/inventree/config.yaml

I just tried but my config.yml does not have that line.
config.yaml.txt

I just tried but my config.yml does not have that line. config.yaml.txt

okay im reproducing the error, i just got a clean ubuntu 20.04 install and had the same issue. I've downloaded with sudo apt-get install inventree.
everything seems to work fine every systemctl inventree seems to be working even the log doesnt have any error except userwarnings. but still getting 502 bad gateway.
if found two config.yaml files.
/opt/inventree/src/backend/InvenTree/config.yaml
/etc/inventree/config.yaml

and both files are same, on line 88 you'll see # site_url: 'http://localhost:8000'
uncomment line 88 on config file /etc/inventree/config.yaml
let me know if it works @mabroens

just tried that but without success. still bad gateway

sure. i had already copied it 5 above but this is the cat:
cat /etc/inventree/config.yaml

# Secret key for backend
# Use the environment variable INVENTREE_SECRET_KEY_FILE
secret_key_file: '/etc/inventree/secret_key.txt'

# Database backend selection - Configure backend database settings
# Documentation: https://inventree.readthedocs.io/en/latest/start/config/

# Note: Database configuration options can also be specified from environmental variables,
#       with the prefix INVENTREE_DB_
#       e.g INVENTREE_DB_NAME / INVENTREE_DB_USER / INVENTREE_DB_PASSWORD
database:
  # Uncomment (and edit) one of the database configurations below,
  # or specify database options using environment variables

  # Refer to the django documentation for full list of options

  # --- Available options: ---
  # ENGINE: Database engine. Selection from:
  #         - mysql
  #         - postgresql
  #         - sqlite3
  # NAME: Database name
  # USER: Database username (if required)
  # PASSWORD: Database password (if required)
  # HOST: Database host address (if required)
  # PORT: Database host port (if required)

  # --- Database settings ---
  ENGINE: sqlite3
  NAME: '/opt/inventree/data/database.sqlite3'
  USER: sampleuser
  PASSWORD: samplepassword
  HOST: samplehost
  PORT: 123456

  # --- Example Configuration - MySQL ---
  #ENGINE: mysql
  #NAME: inventree
  #USER: inventree
  #PASSWORD: inventree_password
  #HOST: 'localhost'
  #PORT: '3306'

  # --- Example Configuration - Postgresql ---
  #ENGINE: postgresql
  #NAME: inventree
  #USER: inventree
  #PASSWORD: inventree_password
  #HOST: 'localhost'
  #PORT: '5432'

  # --- Example Configuration - sqlite3 ---
  # ENGINE: sqlite3
  # NAME: '/home/inventree/database.sqlite3'

# Set debug to False to run in production mode
# Use the environment variable INVENTREE_DEBUG
debug: False

# Configure the system logging level
# Use environment variable INVENTREE_LOG_LEVEL
# Options: DEBUG / INFO / WARNING / ERROR / CRITICAL
log_level: WARNING

# Select default system language (default is 'en-us')
# Use the environment variable INVENTREE_LANGUAGE
language: en-us

# System time-zone (default is UTC)
# Reference: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
timezone: UTC

# Base currency code (or use env var INVENTREE_BASE_CURRENCY)
base_currency: USD

# Add new user on first startup
#admin_user: admin
#admin_email<EMAIL_ADDRESS>#admin_password: inventree

# List of currencies supported by default. Add other currencies here to allow use in InvenTree
currencies:
  - AUD
  - CAD
  - CNY
  - EUR
  - GBP
  - JPY
  - NZD
  - USD

# Email backend configuration
# Ref: https://docs.djangoproject.com/en/dev/topics/email/
# Alternatively, these options can all be set using environment variables,
# with the INVENTREE_EMAIL_ prefix:
# e.g. INVENTREE_EMAIL_HOST / INVENTREE_EMAIL_PORT / INVENTREE_EMAIL_USERNAME
# Refer to the InvenTree documentation for more information

email:
  # backend: 'django.core.mail.backends.smtp.EmailBackend'
  host: ''
  port: 25
  username: ''
  password: ''
  sender: ''
  tls: False
  ssl: False

# Set sentry_enabled to True to report errors back to the maintainers
# Set sentry,dsn to your custom DSN if you want to use your own instance for error reporting
sentry_enabled: False
#sentry_sample_rate: 0.1
#sentry_dsn<EMAIL_ADDRESS>
# Set this variable to True to enable InvenTree Plugins
# Alternatively, use the environment variable INVENTREE_PLUGINS_ENABLED
plugins_enabled: true
plugin_file: '/etc/inventree/plugins.txt'
#plugin_dir: '/path/to/plugins/'

# Allowed hosts (see ALLOWED_HOSTS in Django settings documentation)
# A list of strings representing the host/domain names that this Django site can serve.
# Default behaviour is to allow all hosts (THIS IS NOT SECURE!)
allowed_hosts:
  - '*'

# Cross Origin Resource Sharing (CORS) settings (see https://github.com/ottoyiu/django-cors-headers)
# Following parameters are
cors:
  # CORS_ORIGIN_ALLOW_ALL - If True, the whitelist will not be used and all origins will be accepted.
  allow_all: True

  # CORS_ORIGIN_WHITELIST - A list of origins that are authorized to make cross-site HTTP requests. Defaults to []
  # whitelist:
  # - https://example.com
  # - https://sub.example.com

# MEDIA_ROOT is the local filesystem location for storing uploaded files
media_root: '/opt/inventree/data/media'

# STATIC_ROOT is the local filesystem location for storing static files
static_root: '/opt/inventree/data/static'

### Backup configuration options ###
# INVENTREE_BACKUP_DIR is the local filesystem location for storing backups
backup_storage: django.core.files.storage.FileSystemStorage
backup_dir: '/opt/inventree/data/backup'
#backup_options:

# Background worker options
background:
  workers: 4
  timeout: 90
  max_attempts: 5

# Optional URL schemes to allow in URL fields
# By default, only the following schemes are allowed: ['http', 'https', 'ftp', 'ftps']
# Uncomment the lines below to allow extra schemes
#extra_url_schemes:
#  - mailto
#  - git
#  - ssh

# Login configuration
login_confirm_days: 3
login_attempts: 5
login_default_protocol: http

# Remote / proxy login
# These settings can introduce security problems if configured incorrectly. Please read
# https://docs.djangoproject.com/en/4.0/howto/auth-remote-user/ for more details
# The header name should be prefixed by `HTTP`. Please read the docs for more details
# https://docs.djangoproject.com/en/stable/ref/request-response/#django.http.HttpRequest.META
remote_login_enabled: False
remote_login_header: HTTP_REMOTE_USER

# Logout redirect configuration
# This setting may be required if using remote / proxy login to redirect requests
# during the logout process (default is 'index'). Please read the docs for more details
# https://docs.djangoproject.com/en/stable/ref/settings/#logout-redirect-url
#logout_redirect_url: 'index'

# Permit custom authentication backends
#authentication_backends:
#  - 'django.contrib.auth.backends.ModelBackend'

#  Custom middleware, sometimes needed alongside an authentication backend change.
#middleware:
#  - 'django.middleware.security.SecurityMiddleware'
#  - 'django.contrib.sessions.middleware.SessionMiddleware'
#  - 'django.middleware.locale.LocaleMiddleware'
#  - 'django.middleware.common.CommonMiddleware'
#  - 'django.middleware.csrf.CsrfViewMiddleware'
#  - 'corsheaders.middleware.CorsMiddleware'
#  - 'django.contrib.auth.middleware.AuthenticationMiddleware'
#  - 'django.contrib.messages.middleware.MessageMiddleware'
#  - 'django.middleware.clickjacking.XFrameOptionsMiddleware'
#  - 'InvenTree.middleware.AuthRequiredMiddleware'

# Add SSO login-backends (see examples below)
# social_backends:
#  - 'allauth.socialaccount.providers.google'
#  - 'allauth.socialaccount.providers.github'
#  - 'allauth.socialaccount.providers.keycloak'

# Add specific settings for social account providers (if required)
# social_providers:
#   keycloak:
#     KEYCLOAK_URL: 'https://keycloak.custom/auth'
#     KEYCLOAK_REALM: 'master'

# Customization options
# Add custom messages to the login page or main interface navbar or exchange the logo
# Use environment variable INVENTREE_CUSTOMIZE or INVENTREE_CUSTOM_LOGO
# customize:
#   login_message: InvenTree demo instance - <a href='https://inventree.readthedocs.io/en/latest/demo/'> Click here for login details</a>
#   navbar_message: <h6>InvenTree demo mode <a href='https://inventree.readthedocs.io/en/latest/demo/'><span class='fas fa-info-circle'></span></a></h6>
#   logo: logo.png
#   splash: splash_screen.jpg
#   hide_admin_link: true
#   hide_password_reset: true

@mabroens thanks for the config file! sorry i didnt notice the previous ones.
first i would set debug to True if you are trying to figure out the error.
And the second is, i just looked trough the config file of the previous version and there is the same line.
try the blank config file from this link:
https://github.com/inventree/InvenTree/blob/master/src/backend/InvenTree/config_template.yaml
and uncomment line 88.

yes i had already done that. see a few up. .
copied it uncommented the line 88 and than open web browser to Inventree . but still bad gateway. or should i first do another step sorry.
Br Martijn

Yes but thats the template from within your program i mean from the github.
And if debug is true try every sysmtctl even ngix.
If there us any log otherwise i would suggest clean install. Because im not sure if the auto update was any good.

ah that i missed :-) copied it to the system and systemctl restart inventree but still the same error.
you mention "otherwise i would suggest clean install."  is that sudo apt-get install inventree and woud that overwrite my exsisting installation?
would that clear/kill/??? my database or do you have any instructions on how to secure my current dB?
my preference would be to do a clean install ie remove all except for my dB

ah that i missed :-) copied it to the system and systemctl restart inventree but still the same error.
you mention "otherwise i would suggest clean install." is that sudo apt-get install inventree and woud that overwrite my exsisting installation? would that clear/kill/??? my database or do you have any instructions on how to secure my current dB?
my preference would be to do a clean install ie remove all except for my dB

I wanna try before that on last thing.
Im using inventree restart instead of systemctl. Not sure if thats any difference.
And try if you would like:
Inventree config:get VAR=INVENTREE_SITE_URL
Im curious if its gets the config settings.
Im not sure how to handle that, maybe its as easy as using the old db. @SchrodingersGat
I think it realy depends on wich version u had before this.

root@ASM100:/home/spectrum# inventree config:get VAR=INVENTREE_SITE_URL
root@ASM100:/home/spectrum#

Oh and tried this: Im using inventree restart instead of systemctl. Not sure if thats any difference. as well but that makes no diff

an otherthing i tried, for what its worth.:
root@ASM100:~# inventree logs --tail
==> /var/log/inventree/setup_2023-04-07_09_01_45.log <==

==> /var/log/inventree/setup_2023-04-25_15_30_41.log <==

==> /var/log/inventree/setup_2023-05-25_21_00_40.log <==

==> /var/log/inventree/setup_2023-07-02_20_27_31.log <==

==> /var/log/inventree/setup_2023-07-03_09_09_36.log <==

==> /var/log/inventree/setup_2023-07-09_11_13_05.log <==

==> /var/log/inventree/setup_2023-07-18_12_13_47.log <==

==> /var/log/inventree/setup_2023-08-27_10_32_12.log <==

==> /var/log/inventree/setup_2024-04-29_17_59_17.log <==

==> /var/log/inventree/setup_2024-05-16_19_05_43.log <==
mei 22 16:16:17 ASM100 systemd[1]: inventree-worker-1.service: Scheduled restart job, restart counter is at 5.
mei 22 16:16:17 ASM100 systemd[1]: inventree-web-1.service: Scheduled restart job, restart counter is at 5.
mei 22 16:16:17 ASM100 systemd[1]: Stopped inventree-web-1.service.
mei 22 16:16:17 ASM100 systemd[1]: inventree-web-1.service: Start request repeated too quickly.
mei 22 16:16:17 ASM100 systemd[1]: inventree-web-1.service: Failed with result 'exit-code'.
mei 22 16:16:17 ASM100 systemd[1]: Failed to start inventree-web-1.service.
mei 22 16:16:17 ASM100 systemd[1]: Stopped inventree-worker-1.service.
mei 22 16:16:17 ASM100 systemd[1]: inventree-worker-1.service: Start request repeated too quickly.
mei 22 16:16:17 ASM100 systemd[1]: inventree-worker-1.service: Failed with result 'exit-code'.
mei 22 16:16:17 ASM100 systemd[1]: Failed to start inventree-worker-1.service.
^C

@mabroens to confirm did you set the site_url in your config file? Or via the INVENTREE_SITE_URL environment variable?
Strange that you are not getting any logs from systemctl.. Can you show the output of:
journalctl -u inventree-web-1.service

@mabroens ok, so looks like the web server is actually functioning at least.
Next we should look at the nginx logs. Grab the name of the nginx process with:
systemctl list-units --type=service --state=running

(let's say it's nginx.service)
Then run:
systemctl status nginx.service

root@ASM100:~# systemctl list-units --type=service --state=running
UNIT                          LOAD   ACTIVE SUB     DESCRIPTION
accounts-daemon.service       loaded active running Accounts Service
acpid.service                 loaded active running ACPI event daemon
avahi-daemon.service          loaded active running Avahi mDNS/DNS-SD Stack
bluetooth.service             loaded active running Bluetooth service
colord.service                loaded active running Manage, Install and Generate Color Profiles
cron.service                  loaded active running Regular background program processing daemon
cups-browsed.service          loaded active running Make remote CUPS printers available locally
cups.service                  loaded active running CUPS Scheduler
dbus.service                  loaded active running D-Bus System Message Bus
gdm.service                   loaded active running GNOME Display Manager
inventree-web.service         loaded active running inventree-web.service
inventree-worker.service      loaded active running inventree-worker.service
inventree.service             loaded active running inventree.service
irqbalance.service            loaded active running irqbalance daemon
kerneloops.service            loaded active running Tool to automatically collect and submit kernel crash signatures
ModemManager.service          loaded active running Modem Manager
NetworkManager.service        loaded active running Network Manager
nginx.service                 loaded active running A high performance web server and a reverse proxy server
packagekit.service            loaded active running PackageKit Daemon
polkit.service                loaded active running Authorization Manager
power-profiles-daemon.service loaded active running Power Profiles daemon
rsyslog.service               loaded active running System Logging Service
rtkit-daemon.service          loaded active running RealtimeKit Scheduling Policy Service
snapd.service                 loaded active running Snap Daemon
ssh.service                   loaded active running OpenBSD Secure Shell server
switcheroo-control.service    loaded active running Switcheroo Control Proxy service
systemd-journald.service      loaded active running Journal Service
systemd-logind.service        loaded active running User Login Management
systemd-oomd.service          loaded active running Userspace Out-Of-Memory (OOM) Killer
systemd-resolved.service      loaded active running Network Name Resolution
systemd-timesyncd.service     loaded active running Network Time Synchronization
systemd-udevd.service         loaded active running Rule-based Manager for Device Events and Files
teamviewerd.service           loaded active running TeamViewer remote control daemon
thermald.service              loaded active running Thermal Daemon Service
udisks2.service               loaded active running Disk Manager
unattended-upgrades.service   loaded active running Unattended Upgrades Shutdown
upower.service                loaded active running Daemon for power management
<EMAIL_ADDRESS>           loaded active running User Manager for UID 1000
<EMAIL_ADDRESS>            loaded active running User Manager for UID 129
wpa_supplicant.service        loaded active running WPA supplicant
LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.

-- Boot 4cdb840733a44a46b3bf77d9a5660e6a --
apr 07 11:21:43 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 07 11:21:43 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.

-- Boot fb9d67b5870b41f7b800ef5ea7d4de02 --
apr 11 11:22:47 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 11 11:22:47 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 14 15:13:56 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 14 15:13:56 ASM100 systemd[1]: nginx.service: Succeeded.
apr 14 15:13:56 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.
-- Boot a0f841430eed4f11925545a38f85e711 --
apr 14 15:15:45 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 14 15:15:45 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.

-- Boot 023cc5bbe89f4dcfa8f617e748688391 --
apr 16 12:36:23 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 16 12:36:24 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 16 17:50:24 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 16 17:50:24 ASM100 systemd[1]: nginx.service: Succeeded.
apr 16 17:50:24 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.

-- Boot ae64959fb3e04579a2e6fdeb919f0cbb --
apr 21 07:52:27 ASM100 systemd[1]: Starting A high performance web server and a reverse proxy server...
apr 21 07:52:27 ASM100 systemd[1]: Started A high performance web server and a reverse proxy server.
apr 24 11:20:35 ASM100 systemd[1]: Stopping A high performance web server and a reverse proxy server...
apr 24 11:20:35 ASM100 systemd[1]: nginx.service: Succeeded.
apr 24 11:20:35 ASM100 systemd[1]: Stopped A high performance web server and a reverse proxy server.

Thanx guys for the support

next step now is to relocate my db and other relevant files to an external machine like dropbox or NAS.
and then remove Inventree from the machine and reisntall ubuntu and inventree again to have a clean machine.
Br Martijn

Ref: https://github.com/inventree/InvenTree/discussions/7336

@mabroens ok thank you for prodiving that extra information. We can use that to work out our fix for the installer.
(@matmair )

@mabroens thanks for adding in that additional detail, I'll make a note of it.

Seems like the original issue was resolved - can we close this @mabroens?

yes we can thank you


Correctly remove the buildin rails adapter

Followup #19. cc @dixpac
defined? for a string literal is always truthy, same as for symbols.
defined?(ActiveJob::QueueAdapters::SneakersAdapter) would work as an alternative.
module ActiveJob
  module QueueAdapters
    # Adapter removed from rails
  end
end

module ActiveJob
  module QueueAdapters
    remove_const(:SneakersAdapter) if defined?("::#{name}::SneakersAdapter")
  end
end

test.rb:10:in 'remove_const': constant ActiveJob::QueueAdapters::SneakersAdapter not defined (NameError)

@Earlopain I assume we really need to produce a new patch release? I can do that today.

Ah no, I don't think so. The adapter is still present in rails 8.0 so it is not urgent for a number of months yet. It isn't even deprecated yet (if they go with that route).

@Earlopain ah, OK. Thank you for the explanation. We certainly will ship a new patch release in the next few months.


Handles invalid header on versioned update

Description
When the versioning policy is set to "versioned-update", we require that the most recent version of the resource is provided in the request's if-match header on an update. The specified version must be in ETag format.
Previously, a 500 would be returned if the version was invalid or in an incorrect format. This PR instead returns a 400 Bad Request.
Related issues
Addresses AB#87737.
Testing
Updated the manual test flow to include this case.
A lot of the versioning policy test setup was done in #2457. An automated test for this scenario will be added once that PR merges and this branch can be rebased with those changes.
FHIR Team Checklist

✅ Update the title of the PR to be succinct and less than 50 characters
✅ Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
✅ Tag the PR with the type of update: Bug, Dependencies, Enhancement, or New-Feature
✅ Tag the PR with Azure API for FHIR if this will release to the Azure API for FHIR managed service (CosmosDB or common code related to service)
✅ Tag the PR with Azure Healthcare APIs if this will release to the Azure Healthcare APIs managed service (Sql server or common code related to service)
✅ CI is green before merge
Review squash-merge requirements

Semver Change (docs)
None (bug fix)

The PATCH operation seems to be not possible with the policy version-update. The operation returns  the following error: 400 - A valid if-match header is required for resource type 'Organization'

@EXPEkesheth, FYI
@sghino would you mind making an issue for this problem? We don't tend to monitor old PRs.


refactor: better monitor layout

This PR refactors the previous monitor layout configuration extending it with support for workspaces and keybinds to move between them. This means that custom WM-dependent solutions are no longer needed.

#24  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @zakuciael and the rest of your teammates on  Graphite

Merge activity

May 1, 3:07 PM EDT: @zakuciael merged this pull request with Graphite.


Modify the socket.io for the latest version of the package.json, The program cannot work properly

You should also change the client version to the v2.0.3, such as <script src="//cdn.bootcss.com/socket.io/2.0.3/socket.io.js"></script>.

@yangkean thx :)


A way to unscale data

Hi,
I'm using the TimeSeriesKMeans on some data I got, and it gives much better results after scaling it with TimeSeriesScalerMeanVariance. However, I'd like to plot the centroids in the original data representation. Is there an easy way to unscale them?
Thanks, this is a very nice library!

Hi @jaumebp
This method scales the time series independently.
Hence, there is not a single mean / variance vector for the whole dataset that could be used to "unscale" the centroids, I'm afraid.
And if the goal is visualization, I would suggest not trying to unscale anything when the clustering has been based on scaled data, since the resulting visualization could be misleading.
Hope this helps,
Romain


Advanced Search Does Not Return Any Results When Search for Reports with a Draft Status

Super users are responsible for policing draft reports for their organization.  However, using "Advanced search" to find reports with a "draft" status does not return any results.  As of this moment there are 524 reports with a draft status and the advisorOrganizationId is not NULL and the authorId is not NULL.
A super user would use the following search actions to find reports for his/her organization:

Select "Advanced search"
Select the "Reports" button
Add the "Organization" filter
Select an organization that has one or more draft reports
Select the "State" filter
Select the "Draft" value for the "State" filter
Click the blue "Search" button

The leadership would use the following search actions to find all reports with a draft status:

Select "Advanced search"
Select the "Reports" button
Select the "State" filter
Select the "Draft" value for the "State" filter
Click the blue "Search" button

Reference item 121

@dspCarlson , currently I can search for reports with draft state, but that returns only my draft reports. That kind of makes sense, as reports are only visible to me as long as they are in draft state.

Are we saying that they should also be visible to the super users of my org? I can see a point for that.
We could make admins be able to see everyone's draft reports, regardless of the org. Would that address the second use case?

@VassilIordanov Reports left in a draft/rejected status need to be identified and then approved or deleted.  Maybe search filters are not the means to identify and manage draft/rejected reports.
As of 20 August 2018, there are 1,014 reports with a draft or rejected status where the engagement date is more than one week ago.

A user can only search for their own draft reports, but not the draft reports of another person or organization.
This ticket should be closed.


axios_1.default is not a function?

Hi, I'm getting the following error when calling this:
const test = await GOOGLE_IMG_SCRAP({
    search: "cats",
});
console.log(test);

The error is:
Uncaught (in promise) TypeError: axios_1.default is not a function
    scrapGoogleImagesScriptsTag parseGoogleImages.ts:17
    __awaiter bundle.js:3372
    __awaiter bundle.js:3354
    scrapGoogleImagesScriptsTag bundle.js:3395
    parseGoogleImages parseGoogleImages.ts:65
    __awaiter bundle.js:3372
    __awaiter bundle.js:3354
    parseGoogleImages bundle.js:3429
    GOOGLE_IMG_SCRAP index.ts:71
    __awaiter bundle.js:3530
    __awaiter bundle.js:3512
    GOOGLE_IMG_SCRAP bundle.js:3592
    handleSubmit hooks.js:29
    React 23
    js index.js:6
    factory react refresh:6
    Webpack 3

I'm new to using React and npm, so it's possible this is due to a very obvious error on my part, but I'm curious if you have any ideas what I might be doing wrong.

I don't know what exactly is this error but if you are using it directly in react it will not work because react is a frontend framework you will need to set up a backend to use this package with expressjs for example. Are you using it directly in react ?

Oh okay I see, I don't have a backend framework, so that's probably the issue. Thanks for the info!

Haha no problem you can make one very fast with expressjs (only 20 lines of codes)


question in connect to vnc

when I try to connect android with VNC in port tcp/5900, I just connect to the mac itself, not the android in docker, why?

@jaassoon how are you running Docker in MacOS?
Probably in dedicated VM?

now I even cant see the devices.
docker ps
CONTAINER ID        IMAGE                          COMMAND             CREATED             STATUS              PORTS                                                                                NAMES 278f63e28d8b        tracer0tong/android-emulator   "/entrypoint.sh"    19 hours ago        Up About an hour    <IP_ADDRESS>:32777->22/tcp, <IP_ADDRESS>:32776->5037/tcp, <IP_ADDRESS>:32775->5554/tcp, <IP_ADDRESS>:32774->5555/tcp, <IP_ADDRESS>:32773->5900/tcp   android
adb connect <IP_ADDRESS>:32776
connected to <IP_ADDRESS>:32776
adb devices
List of devices attached
nothing to show

Could you make netstat -an | grep 32773 in shell? This is a port there are VNC should be attached. And also for 32777 (this is container ssh).

netstat -an | grep 32773
tcp6       0      0  ::1.32773              *.*                    LISTEN tcp4       0      0  *.32773                *.*                    LISTEN
netstat -an | grep 32777
tcp6       0      0  ::1.32777              *.*                    LISTEN tcp4       0      0  *.32777                *.*                    LISTEN

ok,It can connect to vnc. but
adb devices
still show nothing

And it sounds like I cant do anything with mouse click

I use chrome VNC plugin

Two problems here: 1) VNC in Android QEMU is not fully functional. So, it doesn't support mouse clicks and many other features. One option, which was discussed in previous issues to use Monkey Runner to send commands and capture screenshots. 2) About ADB probably you have not connected to correct port. Should be 32774


Visualize ocean floor geo data in Superset (with Trino, from S3)

Working on this: https://github.com/stackabletech/marispace-x/issues/71
Data uploaded here: https://repo.stackable.tech/repository/misc/marispace/multibeam_data_point_density_example.parquet
The coordinates use this reference frame: https://epsg.io/32632

The PR also makes a change in the superset-trino-s3 Stack which is also used by the Taxi demo. The change raises the row limit in superset, so larger queries can be made. This is necessary for this demo, to get a complete picture of the ocean floor.

It was straightforward to adapt the taxi data demo, but now I can't find a good Chart type to plot the data.
The data would best be plotted with a surface plot, but Superset doesn't offer this.
Maybe a view of the data can be created with already regular buckets and then the heatmap type can be used.

This is the visualization I have now. I got the asset working too.
Now I will just clean up some file naming.

before merging, 046a0e5c6589644c790bbeba74406c8d18a1e4ff needs to be replaced with main in the file references.

I have now attempted for multiple hours to get the data visualized in the deck.gl Heatmap plot type, but I can't get the coordinate conversion right.
What I did: use calculated columns in Superset to calculate lat/lon coordinates

lat = footprint_y /<PHONE_NUMBER>76
lon = footprint_x /<PHONE_NUMBER>76 + 6

This is based on the fixed distance that 1 degree does for lat, and then the 6 degree offset for the EPSG:32632 reference frame in eastern direction. But the location I get is still off:

(The big circle is where we get, the smaller one where we should be).
You can use this tool to calculate the actual coordinates that you should get.
I have asked north.io for more help on concrete conversion numbers to use, but they couldn't readily provide any.


Add --text-spacing-icon variable

What's this for

Wrong name, sorry, that variable already exists.
The text-spacing-icon variable would be like the text-enabled/disabled-icon but for the spacing that's next to e.g. the Note Recording Option


spurious update-in-place changes when re-running a plan for an IDENTICAL airbyte_connection resource

Expected Behaviour
When re-running a terraform plan/apply on a airbyte_connection resource whose definition HAS NOT CHANGED the expected outcome is that NO CHANGE IS DETECTED
Actual Behaviour
The provider detects that a SPURIOUS "update in place" is required when, in fact, there is ABSOLUTELY NO NEED for this.
airbytehq/airbyte provider version = 0.6.0

I've closed this because there was a change in the cron spec that I didn't notice that was forcing the update. Once this was corrected the spurious updates to the streams did not occur.


descendants should allow to enforce a limit on the search

Problem to solve
Currently, Flame's API descendants method will look at the entire subtree. Sometimes, usually for testing purposes, one might require to limit the search to a specific depth (depth limited search).
Proposal
One solution could be adding an optional named parameter to the method:
Iterable<Component> descendants({bool includeSelf = false, int? limit}) sync* {

(cc: @st-pasha , @Dan-Crane , @spydon)

I don't think this is something that should be handled in the method, since you get an Iterable back it is easy for the user to handle it on their side.
You can use this method for example.

Very overkill in the method above, just realized you can do descendants.take(4) instead.

Ah, right, it is the depth you want to limit, not the amount of results (was confused by the limit name).
I still think this is a parameter that is too implementation specific to include on decendants (if we don't get plenty of people asking for it of course). Or do you have a common usecase example that you could share?

Definitely, the parameter limit requires renaming. Indeed I'm talking about the depth limit. I'm not sure if there's already a fancy way of achieving this with existing API's, perhaps @st-pasha might have some insight.
I think it can suit well within descendants since it's basically like saying "return me all my sons and grandsons, but not my grand-grand-sons or further".
Regarding examples, I haven't got any specific ones that might help here.
Let's see what others think about this issue.

There isn't a way to filter the current descendants() to a specific depth.
On the other hand, we probably shouldn't be implementing features for which there is no conceivable use case, because that's just more effort to document, to test, and to maintain.

Personally, I haven't ended up with a giant tree of components. But there might be a game that does require this performance optimisation.
I agree that for the time being, we can avoid implementing it. If someone is willing to implement, document and test I wouldn’t be against it. Since it's a nice performance optimisation that could be handy at some point.

Sounds good to me @spydon !


metasploit: 6.1.25 -> 6.1.27

Motivation for this change
Update to latest upstream release 6.1.27
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 157448 run on x86_64-linux 1

1 package built:

msf (metasploit)


Move bitcoin-io write tests to tests/

If #3128 merges then the unit tests created with the write_test macro in hashes/src/impls.rs could be moved to hashes/tests/ because:

They are somewhere between regression tests and "prove functionality exists" tests
They only use the public API

#3128 now includes this.


Update zio, zio-test, zio-test-sbt to 2.0.0-RC5

Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

from 2.0.0-RC1 to 2.0.0-RC5.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #185.


[YUNIKORN-2799] Solve dockerfile warning which emerged while building

What is this PR for?
1 warning found:

RedundantTargetPlatform: Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior (line 17)
Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior
More info: https://docs.docker.com/go/dockerfile/rule/redundant-target-platform/
Dockerfile:17

  15 |     # See the License for the specific language governing permissions and
  16 |     # limitations under the License.
  17 | >>> FROM --platform=$TARGETPLATFORM scratch
  18 |     COPY --chown=0:0 LICENSE NOTICE third-party-licenses.md yunikorn-scheduler /
  19 |     USER 4444:4444

from docker version 27.1.1
suggested change: remove --platform=$TARGETPLATFORM in dockerfile
ref: https://docs.docker.com/reference/build-checks/redundant-target-platform/#examples
change:

shim: RedundantTargetPlatform
web:

RedundantTargetPlatform: Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior (line 32)
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 36)
FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 20)
InvalidDefaultArgInFrom: Default value for ARG node:${NODE_VERSION}-alpine results in empty or invalid base image name (line 20)

What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2799
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 38.77%. Comparing base (aa67a85) to head (ccdff6d).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #201   +/-   ##
=======================================
  Coverage   38.77%   38.77%
=======================================
  Files           2        2
  Lines          49       49
=======================================
  Hits           19       19
  Misses         27       27
  Partials        3        3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Adding integration test for Hadoop pre-process job

Adding integration test for Hadoop pre-process job

Codecov Report

Merging #4577 into master will decrease coverage by 0.13%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #4577      +/-   ##
============================================
- Coverage     64.42%   64.28%   -0.14%
  Complexity       32       32
============================================
  Files          1072     1072
  Lines         55638    55637       -1
  Branches       8112     8112
============================================
- Hits          35842    35765      -77
- Misses        17142    17208      +66
- Partials       2654     2664      +10

Impacted Files
Coverage Δ
Complexity Δ

...gment/name/NormalizedDateSegmentNameGenerator.java
93.33% <100%> (+6.37%)
0 <0> (ø)
:arrow_down:

...altime/ServerSegmentCompletionProtocolHandler.java
35.11% <0%> (-15.27%)
0% <0%> (ø)

...g/apache/pinot/common/response/ServerInstance.java
78.26% <0%> (-15.22%)
0% <0%> (ø)

...esthandler/ConnectionPoolBrokerRequestHandler.java
76.39% <0%> (-11.81%)
0% <0%> (ø)

...ore/query/scheduler/resources/ResourceManager.java
85.71% <0%> (-10.72%)
0% <0%> (ø)

...pache/pinot/core/util/SortedRangeIntersection.java
83.82% <0%> (-7.36%)
0% <0%> (ø)

...e/pinot/common/utils/FileUploadDownloadClient.java
71.68% <0%> (-6.63%)
0% <0%> (ø)

...e/impl/dictionary/LongOnHeapMutableDictionary.java
82.6% <0%> (-6.53%)
0% <0%> (ø)

...ot/common/protocols/SegmentCompletionProtocol.java
87.86% <0%> (-5.21%)
0% <0%> (ø)

.../org/apache/pinot/transport/netty/NettyServer.java
80.8% <0%> (-3.04%)
0% <0%> (ø)

... and 25 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a1c5af7...a8ab052. Read the comment docs.


Document "implementation-detail" trait

Which does exactly as it implies, and is used all over in Rakudo. Check some usage here
Suggestions
Research what it actually does, and come up with useful examples that reveal real use cases.

The implementation-detail trait is currently supported on subroutines and methods.  It basically sets a flag which can be introspected.  This flag is currently checked by introspection methods such as .keys on PseudoStashes and .^methods on classes.
Example: the CORE contains a subroutine &DYNAMIC that currently takes care of finding dynamic variables that haven't been found in the stack yet.
If you look for it directly, you will find it:
say CORE::<&DYNAMIC>.raku
# sub DYNAMIC (\name) { #`(Sub+{is-implementation-detail}|140341166976832) ... }

However, if you inspect CORE:: with .keys, it won't show:
dd CORE::.keys.grep( *.name eq "&DYNAMIC" )
# ().Seq

That's because it's marked as an implementation detail.


error MSB4025: The project file could not be loaded

Hi everyone,
I have an Issue when i run deploy-gocore.bat.
error MSB4025: The project file could not be loaded. Data at the root level is invalid. Line 1, position 1.
I am very thankful for all the help.
Best regards!

What is the value of %GOPATH% on your command line? For example, mine is C:\Users\ritchie\go
Also, I would run this batch file from a command line in the same folder that is located.
Thanks!
Ritchie

A compiled version is now available for testing: https://github.com/GridProtectionAlliance/go2cs/releases/


Operation is not reversible

I got his error:
File "/usr/local/lib/python3.5/site-packages/django/db/migrations/executor.py", line 218, in unapply_migration
    state = migration.unapply(state, schema_editor)
  File "/usr/local/lib/python3.5/site-packages/django/db/migrations/migration.py", line 146, in unapply
    raise IrreversibleError("Operation %s in %s is not reversible" % (operation, self))
django.db.migrations.exceptions.IrreversibleError: Operation <RunPython <function move_Point at 0x7feb316df730>> in my_app.0008_move_message_point_to_device_location is not reversible

this move_point method is a personal migration method that move data.
May i need to make a reverse method of it ?

Ok i understant that we must define a reverse operation for this custom migration method added with runPython: https://docs.djangoproject.com/en/1.10/ref/migration-operations/#runpython
But... new question 😄  : how test this reverse code added ?
Can we apply a reverse migration in your test (for example before = "0002.." after = "0001...." ) ?
Is this really usefull ? As this reverse migration is never used with data ?

Personally I usually define a no-op / null (looks like Django now has a built in RunSQL.noop) for data migrations. Seems like it should be supported if it isn't too crazy though! 👍

The migration needs to be reversible to be testable, because the test-case needs to be able to get to the state before it. It does this by migrating to that point, which requires it to migrate your migration backwards. If you don't care about the reverse operation, you can do:
migrations.RunPython(fix_all_my_data, migrations.RunPython.noop)

The before and after options just need to be things that it can migrate to. So "before" just means "state to be at before we call run_migration()" and "after" just means "state to be at after we call run_migration()". There is (I think) no requirement that before is before after.
I would claim that it is useful to be able to test your reverse migrations. We might never want to run a reverse, but it may be the case that if a deployment goes wrong you will need to roll-back your database, and migrating my be preferable to loading a backup.
There is the possibility here of a problem where you specifically want a migration to be non-reversible, but you still want to test it running forwards. If that is relevant here, then ideas welcomed.

Yes, i am ok with you @plumdog .
Good things : i put in place tet for my migration and so realize that i need to develop reverse migration (you give me a good use case of the purpose of them) and so i need to develop test for them to 😄 .  All is ok .
But it's true that i did not realize before making my test that reverse migration need to be developed..... so finally it's a good thing to test the code !


ETP functionality in WITSML Explorer

Stub
Moved from WE-18

an alternative is waiting for Witsml 2.1 with ETP 1.2


Customize NotFound

Current behavior
Ecto handles 404 for me and even if I try to get the data it assigns only message, but there is not way to understand which model is missing and make a custom message basing on this.
So in my ErrorView or catching mechanism I could get only
%{kind: :error, layout: false, reason: %Ecto.NoResultsError{message: "expected at least one result but got none in query: ... "}}

Expected behavior
Ecto.NoResultsMessage and others contain module name/schema.
%{kind: :error, layout: false, reason: %Ecto.NoResultsError{schema: MyApp.User, message: "expected at least one result but got none in query: ... "}}

Hi! If you feel like you need to customize for certain schemas, then the best is to use one() and pattern match on the result. We don't have a schema per se, since we are working with queries, and it may have multiple schemas or be query dependent.

@josevalim Does it make sense to put queryable into Ecto.NoResultsError to be able distinguish which Schema was queried? I think it makes sense to check what was the schema and handle pattern query.from instead of multiple places with case do statement


Simplification, fix bug in ProgressBar, improve comments and naming

Hey @pierredup, I very much like your feature, though I believe original implementation was too complicated. It took me a lot more time than necessary to understand how it works. There was too much stuff I wanted to comment on your pull request, so I just got my hands dirty and did the changes myself. I hope you don't mind. Would be nice if you and me can work on this together. I often hang out on symfony slack channel, so just shoot me a message.
ref: https://github.com/symfony/symfony/pull/24363

Happy to get rid of the OutputSectionReference class. 👍

Thanks @ostrolucky!