inventree-worker restarting

Deployment Method

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

Describe the problem*
I am a Chinese user and I have to use proxy to pull docker images and required packages. After I start docker compose, container "inventree-worker" status always show "Restarting (1) 2 seconds ago"
Steps to Reproduce

Docker was installed automaticlly by 1Panel. Docker Compose version v2.29.2   Docker Engine Version: 27.2.1   containerd Version: 1.7.22  docker-init Version: 0.19.0
Add my proxy url in /etc/systemd/system/docker.service.d/http-proxy.conf, Download Required Files and Add proxy url in docker-compose.yml
 inventree-serve:
……
        environment:
            - HTTP_PROXY=<IP_ADDRESS>:10809
            - HTTPS_PROXY=<IP_ADDRESS>:10809
            - NO_PROXY=localhost,<IP_ADDRESS>,.localdomain
……
docker pull inventree/inventree:0.16.1
docker compose up -d
Then I can see my inventree login page in http://inventree.localhost/
docker ps -a IMAGE  inventree/inventree:stable   STATUS  Restarting (1) 53 seconds ago   NAMES   inventree-worker
docker logs 9d9acfa3fb66
Loading config file : /home/inventree/data/config.yaml
No idea what 'int.worker' is!

Relevant log output
user@debian:~/inventree$ docker compose run --rm inventree-server invoke update
[+] Creating 0/1
 ⠙ Network inventree_default  Creating                                                                                0.2s
[+] Creating 2/1 orphan containers ([inventree-inventree-server-run-c28d162d2a8d]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans fla
 ✔ Network inventree_default  Created                                                                                0.2s
 ✔ Container inventree-db     Created                                                                                0.0s
[+] Running 1/1
 ✔ Container inventree-db  Started                                                                                0.3s
Creating directory /home/inventree/data/static
Creating directory /home/inventree/data/media
Creating directory /home/inventree/data/backup
Copying config file from /home/inventree/src/backend/InvenTree/config_template.yml to /home/inventree/data/config.yaml
Installing required python packages from 'src/backend/requirements.txt'
Requirement already satisfied: pip in /usr/local/lib/python3.11/site-packages (24.0)
Collecting pip
  Downloading pip-24.2-py3-none-any.whl.metadata (3.6 kB)
Requirement already satisfied: setuptools in /root/.local/lib/python3.11/site-packages (72.1.0)
Collecting setuptools
  Downloading setuptools-75.1.0-py3-none-any.whl.metadata (6.9 kB)
Downloading pip-24.2-py3-none-any.whl (1.8 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.8/1.8 MB 4.0 MB/s eta 0:00:00
Downloading setuptools-75.1.0-py3-none-any.whl (1.2 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 15.1 MB/s eta 0:00:00
Installing collected packages: setuptools, pip
  Attempting uninstall: setuptools
    Found existing installation: setuptools 72.1.0
    Uninstalling setuptools-72.1.0:
      Successfully uninstalled setuptools-72.1.0
  Attempting uninstall: pip
    Found existing installation: pip 24.0
    Uninstalling pip-24.0:
      Successfully uninstalled pip-24.0
Successfully installed pip-24.2 setuptools-75.1.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: asgiref==3.8.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 3)) (3.8.1)
Requirement already satisfied: async-timeout==4.0.3 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 9)) (4.0.3)
Requirement already satisfied: attrs==23.2.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 13)) (23.2.0)
Requirement already satisfied: babel==2.15.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 19)) (2.15.0)
Requirement already satisfied: bleach==6.1.0 in /root/.local/lib/python3.11/site-packages (from bleach[css]==6.1.0->-r src/backend/requirements.txt (line 23)) (6.1.0)
Requirement already satisfied: brotli==1.1.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 27)) (1.1.0)
Requirement already satisfied: certifi==2024.7.4 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 112)) (2024.7.4)
Requirement already satisfied: cffi==1.16.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 118)) (1.16.0)
Requirement already satisfied: charset-normalizer==3.3.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 174)) (3.3.2)
Requirement already satisfied: coreapi==2.3.3 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 266)) (2.3.3)
Requirement already satisfied: coreschema==0.0.4 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 270)) (0.0.4)
Requirement already satisfied: cryptography==42.0.8 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 274)) (42.0.8)
Requirement already satisfied: cssselect2==0.7.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 310)) (0.7.0)
Requirement already satisfied: defusedxml==0.7.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 314)) (0.7.1)
Requirement already satisfied: deprecated==1.2.14 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 320)) (1.2.14)
Requirement already satisfied: diff-match-patch==20230430 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 327)) (20230430)
Requirement already satisfied: dj-rest-auth==6.0.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 331)) (6.0.0)
Requirement already satisfied: django==4.2.15 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 334)) (4.2.15)
Requirement already satisfied: django-allauth==0.63.3 in /root/.local/lib/python3.11/site-packages (from django-allauth[openid,saml]==0.63.3->-r src/backend/requirements.txt (line 369)) (0.63.3)
Requirement already satisfied: django-allauth-2fa==0.11.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 374)) (0.11.1)
Requirement already satisfied: django-cleanup==8.1.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 378)) (8.1.0)
Requirement already satisfied: django-cors-headers==4.4.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 382)) (4.4.0)
Requirement already satisfied: django-crispy-forms==1.14.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 386)) (1.14.0)
Requirement already satisfied: django-dbbackup==4.1.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 390)) (4.1.0)
Requirement already satisfied: django-error-report-2==0.4.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 394)) (0.4.2)
Requirement already satisfied: django-filter==24.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 398)) (24.2)
Requirement already satisfied: django-flags==5.0.13 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 402)) (5.0.13)
Requirement already satisfied: django-formtools==2.5.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 406)) (2.5.1)
Requirement already satisfied: django-ical==1.9.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 410)) (1.9.2)
Requirement already satisfied: django-import-export==3.3.9 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 414)) (3.3.9)
Requirement already satisfied: django-js-asset==2.2.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 418)) (2.2.0)
Requirement already satisfied: django-maintenance-mode==0.21.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 422)) (0.21.1)
Requirement already satisfied: django-markdownify==0.9.5 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 426)) (0.9.5)
Requirement already satisfied: django-money==3.2.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 430)) (3.2.0)
Requirement already satisfied: django-mptt==0.16.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 434)) (0.16.0)
Requirement already satisfied: django-otp==1.5.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 438)) (1.5.0)
Requirement already satisfied: django-picklefield==3.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 442)) (3.2)
Requirement already satisfied: django-q-sentry==0.1.6 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 446)) (0.1.6)
Requirement already satisfied: django-q2==1.6.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 449)) (1.6.2)
Requirement already satisfied: django-recurrence==1.11.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 453)) (1.11.1)
Requirement already satisfied: django-redis==5.4.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 457)) (5.4.0)
Requirement already satisfied: django-sesame==3.2.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 461)) (3.2.2)
Requirement already satisfied: django-sql-utils==0.7.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 465)) (0.7.0)
Requirement already satisfied: django-sslserver==0.22 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 469)) (0.22)
Requirement already satisfied: django-stdimage==6.0.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 472)) (6.0.2)
Requirement already satisfied: django-taggit==5.0.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 476)) (5.0.1)
Requirement already satisfied: django-user-sessions==2.0.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 480)) (2.0.0)
Requirement already satisfied: django-weasyprint==2.3.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 484)) (2.3.0)
Requirement already satisfied: django-xforwardedfor-middleware==2.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 488)) (2.0)
Requirement already satisfied: djangorestframework==3.14.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 491)) (3.14.0)
Requirement already satisfied: djangorestframework-simplejwt==5.3.1 in /root/.local/lib/python3.11/site-packages (from djangorestframework-simplejwt[crypto]==5.3.1->-r src/backend/requirements.txt (line 499)) (5.3.1)
Requirement already satisfied: drf-spectacular==0.27.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 503)) (0.27.2)
Requirement already satisfied: dulwich==0.22.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 507)) (0.22.1)
Requirement already satisfied: et-xmlfile==1.1.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 556)) (1.1.0)
Requirement already satisfied: feedparser==6.0.11 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 560)) (6.0.11)
Requirement already satisfied: fonttools==4.53.0 in /root/.local/lib/python3.11/site-packages (from fonttools[woff]==4.53.0->-r src/backend/requirements.txt (line 564)) (4.53.0)
Requirement already satisfied: googleapis-common-protos==1.63.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 608)) (1.63.2)
Requirement already satisfied: grpcio==1.64.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 614)) (1.64.1)
Requirement already satisfied: gunicorn==22.0.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 664)) (22.0.0)
Requirement already satisfied: html5lib==1.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 668)) (1.1)
Requirement already satisfied: icalendar==5.0.13 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 672)) (5.0.13)
Requirement already satisfied: idna==3.7 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 676)) (3.7)
Requirement already satisfied: importlib-metadata==7.1.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 680)) (7.1.0)
Requirement already satisfied: inflection==0.5.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 687)) (0.5.1)
Requirement already satisfied: isodate==0.6.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 691)) (0.6.1)
Requirement already satisfied: itypes==1.2.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 695)) (1.2.0)
Requirement already satisfied: jinja2==3.1.4 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 699)) (3.1.4)
Requirement already satisfied: jsonschema==4.22.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 703)) (4.22.0)
Requirement already satisfied: jsonschema-specifications==2023.12.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 707)) (2023.12.1)
Requirement already satisfied: lxml==5.2.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 711)) (5.2.2)
Requirement already satisfied: markdown==3.6 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 857)) (3.6)
Requirement already satisfied: markuppy==1.14 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 861)) (1.14)
Requirement already satisfied: markupsafe==2.1.5 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 864)) (2.1.5)
Requirement already satisfied: odfpy==1.4.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 926)) (1.4.1)
Requirement already satisfied: openpyxl==3.1.4 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 929)) (3.1.4)
Requirement already satisfied: opentelemetry-api==1.25.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 933)) (1.25.0)
Requirement already satisfied: opentelemetry-exporter-otlp==1.25.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 947)) (1.25.0)
Requirement already satisfied: opentelemetry-exporter-otlp-proto-common==1.25.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 951)) (1.25.0)
Requirement already satisfied: opentelemetry-exporter-otlp-proto-grpc==1.25.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 957)) (1.25.0)
Requirement already satisfied: opentelemetry-exporter-otlp-proto-http==1.25.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 961)) (1.25.0)
Requirement already satisfied: opentelemetry-instrumentation==0.46b0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 965)) (0.46b0)
Requirement already satisfied: opentelemetry-instrumentation-django==0.46b0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 973)) (0.46b0)
Requirement already satisfied: opentelemetry-instrumentation-redis==0.46b0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 977)) (0.46b0)
Requirement already satisfied: opentelemetry-instrumentation-requests==0.46b0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 981)) (0.46b0)
Requirement already satisfied: opentelemetry-instrumentation-wsgi==0.46b0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 985)) (0.46b0)
Requirement already satisfied: opentelemetry-proto==1.25.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 989)) (1.25.0)
Requirement already satisfied: opentelemetry-sdk==1.25.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 996)) (1.25.0)
Requirement already satisfied: opentelemetry-semantic-conventions==0.46b0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1003)) (0.46b0)
Requirement already satisfied: opentelemetry-util-http==0.46b0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1012)) (0.46b0)
Requirement already satisfied: packaging==24.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1019)) (24.1)
Requirement already satisfied: pdf2image==1.17.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1023)) (1.17.0)
Requirement already satisfied: pillow==10.3.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1027)) (10.3.0)
Requirement already satisfied: pint==0.21 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1104)) (0.21)
Requirement already satisfied: pip-licenses==4.4.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1108)) (4.4.0)
Requirement already satisfied: prettytable==3.10.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1112)) (3.10.0)
Requirement already satisfied: protobuf==4.25.3 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1116)) (4.25.3)
Requirement already satisfied: py-moneyed==3.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1131)) (3.0)
Requirement already satisfied: pycparser==2.22 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1135)) (2.22)
Requirement already satisfied: pydyf==0.10.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1139)) (0.10.0)
Requirement already satisfied: pyjwt==2.8.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1143)) (2.8.0)
Requirement already satisfied: pyphen==0.15.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1147)) (0.15.0)
Requirement already satisfied: pypng==0.20220715.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1151)) (0.20220715.0)
Requirement already satisfied: python-barcode==0.15.1 in /root/.local/lib/python3.11/site-packages (from python-barcode[images]==0.15.1->-r src/backend/requirements.txt (line 1155)) (0.15.1)
Requirement already satisfied: python-dateutil==2.9.0.post0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1159)) (2.9.0.post0)
Requirement already satisfied: python-dotenv==1.0.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1165)) (1.0.1)
Requirement already satisfied: python-fsutil==0.14.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1169)) (0.14.1)
Requirement already satisfied: python3-openid==3.2.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1173)) (3.2.0)
Requirement already satisfied: python3-saml==1.16.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1177)) (1.16.0)
Requirement already satisfied: pytz==2024.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1182)) (2024.1)
Requirement already satisfied: pyyaml==6.0.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1189)) (6.0.1)
Requirement already satisfied: qrcode==7.4.2 in /root/.local/lib/python3.11/site-packages (from qrcode[pil]==7.4.2->-r src/backend/requirements.txt (line 1245)) (7.4.2)
Requirement already satisfied: rapidfuzz==3.9.3 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1251)) (3.9.3)
Requirement already satisfied: redis==5.0.7 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1346)) (5.0.7)
Requirement already satisfied: referencing==0.35.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1350)) (0.35.1)
Requirement already satisfied: regex==2024.4.28 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1356)) (2024.4.28)
Requirement already satisfied: requests==2.32.3 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1437)) (2.32.3)
Requirement already satisfied: rpds-py==0.18.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1443)) (0.18.1)
Requirement already satisfied: sentry-sdk==2.8.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1546)) (2.8.0)
Collecting setuptools==72.1.0 (from -r src/backend/requirements.txt (line 1552))
  Downloading setuptools-72.1.0-py3-none-any.whl (2.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 8.4 MB/s eta 0:00:00
Requirement already satisfied: sgmllib3k==1.0.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1559)) (1.0.0)
Requirement already satisfied: six==1.16.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1562)) (1.16.0)
Requirement already satisfied: sqlparse==0.5.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1570)) (0.5.0)
Requirement already satisfied: tablib==3.5.0 in /root/.local/lib/python3.11/site-packages (from tablib[html,ods,xls,xlsx,yaml]==3.5.0->-r src/backend/requirements.txt (line 1576)) (3.5.0)
Requirement already satisfied: tinycss2==1.2.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1582)) (1.2.1)
Requirement already satisfied: typing-extensions==4.12.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1589)) (4.12.2)
Requirement already satisfied: uritemplate==4.1.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1598)) (4.1.1)
Requirement already satisfied: urllib3==2.2.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1604)) (2.2.2)
Requirement already satisfied: wcwidth==0.2.13 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1611)) (0.2.13)
Requirement already satisfied: weasyprint==61.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1615)) (61.2)
Requirement already satisfied: webencodings==0.5.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1621)) (0.5.1)
Requirement already satisfied: whitenoise==6.7.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1629)) (6.7.0)
Requirement already satisfied: wrapt==1.16.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1633)) (1.16.0)
Requirement already satisfied: xlrd==2.0.1 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1708)) (2.0.1)
Requirement already satisfied: xlwt==1.3.0 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1712)) (1.3.0)
Requirement already satisfied: xmlsec==1.3.14 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1716)) (1.3.14)
Requirement already satisfied: zipp==3.19.2 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1776)) (3.19.2)
Requirement already satisfied: zopfli==0.2.3 in /root/.local/lib/python3.11/site-packages (from -r src/backend/requirements.txt (line 1780)) (0.2.3)
Installing collected packages: setuptools
  Attempting uninstall: setuptools
    Found existing installation: setuptools 75.1.0
    Uninstalling setuptools-75.1.0:
      Successfully uninstalled setuptools-75.1.0
Successfully installed setuptools-72.1.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
Plugin configuration file does not exist - creating default file
Installing plugin packages from '/home/inventree/data/plugins.txt'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Failed to set maintenance mode state
Backing up InvenTree database...
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Backing Up Database: inventree
 pg_dump --dbname=postgresql://pguser:pgpassword@inventree-db:5432/inventree --format=custom
Backup size: 447.0 B
Writing file to default-ddb89a695a3a-2024-09-18-122050.psql.bin.gz
Backing up InvenTree media files...
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Backup size: 80.0 B
Writing file to ddb89a695a3a-2024-09-18-122053.tar.gz
Running InvenTree database migrations...
========================================
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Failed to set maintenance mode state
No changes detected
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Failed to set maintenance mode state
Operations to perform:
  Apply all migrations: InvenTree, account, admin, auth, build, common, company, contenttypes, django_q, error_report, exchange, flags, importer, machine, order, otp_static, otp_totp, part, plugin, report, socialaccount, stock, taggit, user_sessions, users
Running migrations:
  Applying InvenTree.0001_initial... OK
......
  Applying report.0026_auto_20240422_1301...
Legacy label table label_stockitemlabel not found - skipping migration

Legacy label table label_stocklocationlabel not found - skipping migration

Legacy label table label_partlabel not found - skipping migration

Legacy label table label_buildlinelabel not found - skipping migration
 OK
  Applying report.0027_alter_labeltemplate_model_type_and_more... OK
......
  Applying user_sessions.0003_auto_20161205_1516... OK
  Applying users.0011_auto_20240523_1640...
Cleared all user sessions to deal with GHSA-2crp-q9pc-457j
 OK
  Applying users.0012_alter_ruleset_can_view... OK
Failed to set maintenance mode state
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Operations to perform:
  Synchronize unmigrated apps: allauth, allauth_2fa, corsheaders, crispy_forms, dbbackup, dj_rest_auth, django_cleanup, django_filters, django_ical, django_otp, djmoney, drf_spectacular, formtools, generic, import_export, maintenance_mode, markdownify, messages, mptt, registration, rest_framework, runserver_nostatic, staticfiles, web
  Apply all migrations: InvenTree, account, admin, auth, build, common, company, contenttypes, django_q, error_report, exchange, flags, importer, machine, order, otp_static, otp_totp, part, plugin, report, socialaccount, stock, taggit, user_sessions, users
Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
Running migrations:
  No migrations to apply.
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/django/db/models/base.py:366: RuntimeWarning: Model 'company.company' was already registered. Reloading models is not advised as it can lead to inconsistencies, most notably with related models.
  new_class._meta.apps.register_model(new_class._meta.app_label, new_class)
/root/.local/lib/python3.11/site-packages/django/db/models/base.py:366: RuntimeWarning: Model 'company.contact' was already registered. Reloading models is not advised as it can lead to inconsistencies, most notably with related models.
  new_class._meta.apps.register_model(new_class._meta.app_label, new_class)
/root/.local/lib/python3.11/site-packages/django/db/models/base.py:366: RuntimeWarning: Model 'company.address' was already registered. Reloading models is not advised as it can lead to inconsistencies, most notably with related models.
  new_class._meta.apps.register_model(new_class._meta.app_label, new_class)
/root/.local/lib/python3.11/site-packages/django/db/models/base.py:366: RuntimeWarning: Model 'company.manufacturerpart' was already registered. Reloading models is not advised as it can lead to inconsistencies, most notably with related models.
  new_class._meta.apps.register_model(new_class._meta.app_label, new_class)
/root/.local/lib/python3.11/site-packages/django/db/models/base.py:366: RuntimeWarning: Model 'company.manufacturerpartparameter' was already registered. Reloading models is not advised as it can lead to inconsistencies, most notably with related models.
  new_class._meta.apps.register_model(new_class._meta.app_label, new_class)
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Not all required settings for adding a user on startup are present:
INVENTREE_ADMIN_USER, INVENTREE_ADMIN_EMAIL, INVENTREE_ADMIN_PASSWORD
========================================
InvenTree database migrations completed!
Skipping frontend update!
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Rendered all files in /home/inventree/src/backend/InvenTree/templates/js/translated
Collecting static files...
Python version 3.11.9 - /usr/local/bin/python3
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Python version 3.11.9 - /usr/local/bin/python3
/root/.local/lib/python3.11/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Not all required settings for adding a user on startup are present:
INVENTREE_ADMIN_USER, INVENTREE_ADMIN_EMAIL, INVENTREE_ADMIN_PASSWORD
Python version 3.11.9 - /usr/local/bin/python3
File “/home/inventree/src/backend/InvenTree/locale/ja/LC_MESSAGES/django.po” is already compiled and up to date.
......
File “/home/inventree/src/backend/InvenTree/locale/ru/LC_MESSAGES/django.po” is already compiled and up to date.
InvenTree translation coverage: 19%

In your docker compose file, change int.worker to worker


Image placement holder for broken images in the playlist items

It will be really nice to have an image place holder (or an onerror event to hook to for images not loaded) for items in the playlist where the poster images are dead or broken.

fixed. @1.0.11-alpha.1


[AUTOPATCHER] Patches CVE-2022-0729 for vim

        Patches CVE-2022-0729 for vim.
        This patch and PR was automatically generated and needs human verification before merging.

did upgrade vim to patch in another PR


How can i show thumbnail preview when forwarding the Video using timeline bar in react native?

I'm working on a project and It needs the exact same implementation as a youtube iframe video component for common mp4 videos. I want to ask if that is this possible to create a forward preview along with a progress bar using the react-native-video Library.
I'm using Below Environment:
React Native: "0.70.3"
React = "18.1.0"
I've not seen such a type of implementation using this Library. If there is any way to do such type of work, Please share otherwise I'll request to community to Please add such type of feature to this library.
I've attached a Sample Of the Required Feature. You can check.
Thanks In advance.

Unfortunately this feature is not yet available.

I did it the following way.

I get the storyboard from remote and their metadata*!
I chop the storyboard, based on the metadata using @react-native-community/image-editor'
After this when the user is seeking to x second, just simple display the closest image to x.

I did something like this:
`
useEffect(() => {
(async () => {
try {
const resp = await fetch(storyboardURL);
const storyboard = (await resp.json()) as Storyboard;
      if (storyboard && _isMounted.current && Array.isArray(storyboard.tiles)) {
        const croppedImages: Array<PreviewImage> = [];

        storyboard.tiles.forEach(async (story) => {
          ImageEditor.cropImage(storyboard.url, {
            offset: { x: story.x, y: story.y },
            size: { width: storyboard.tile_width, height: storyboard.tile_height },
            displaySize: { width: 150, height: 75 }
          }).then((url) => croppedImages.push({ url, start: story.start }));
        });

        setImages(croppedImages);
      }
    } catch (error) {}
  })();

}, []);
`
const getClosestPreviewURL = (images: PreviewImage[], val: number): string => {     return images.reduce((prev, curr) => (Math.abs(curr?.start - val) < Math.abs(prev?.start - val) ? curr : prev), {         start: 0,         url: ""     })?.url }
*resources: https://docs.mux.com/guides/video/create-timeline-hover-previews#add-timeline-hover-previews-to-your-player
Of course this is not the best solution, but unfortunately react-native-video does not support WebVTT

Thanks, @vargajacint.
I'll try this way if possible.

@freeboub I think you can close this


Added pure

I find myself writing this function alot, perhaps its worth including?

I'd rename it to singleton to be parallel with Dict and Set. I'll add this to the meta issue about core changes.

The process for adding stuff to core is described here, so we'll go through and think about all these things in a big batch.

Ok. Fair enough.

https://github.com/circuithub/elm-list-extra/pull/15 merged

Can you share an example of when you use it? What kind of code calls for this?

basically I use it in composition chains, for example
https://github.com/Fresheyeball/elm-students/blob/a5ed3ddf557f9a14a2a5f06f0f3d6c171e38ccb2/src/Test.elm#L180
pure : a -> List a
pure x = [x]

test : List H.Html
test = let
  details =
    pure << H.details [ A.style [ ("overflow", "hidden") ] ]
         << (::) (H.summary [] [ H.text "Tests" ])
         << pure << display << quickCheck << suite "Students"
  in details
    [ checkupdate
    , checkMetrics ]

I ask because that's how I'd use it as well, but I was wondering if this is ever nicer code than just naming things. Your example would become:
test : List H.Html
test = let
  toDetails checks =
    H.details
      [ A.style [ ("overflow", "hidden") ] ]
      [ H.summary [] [ H.text "Tests" ]
      , display (quickCheck (suite "Students" checks))
      ]
  in
    [ toDetails
        [ checkUpdate
        , checkMetrics
        ]
    ]

I personally think that is better code. Do you have any other examples?

I think you could make a similar criticism of other code using pure, and its fair enough. That said I also find pure useful in development workflow even if I remove it later (which usually happens).

Okay, thanks for sharing the example, that was very helpful!

Cheers!

If I may chime in: There are uses of pure/List.singleton in start-app here and here that are not as easily replaced as exercised for the above example. It seems these are conceptually different uses than the ones you discussed above.

While I'm still in favor of List.singleton, it can be easily replaced in start-app:
        inputs =
            Signal.mergeMany (messages.signal :: List.map (Signal.map singleton) config.inputs)

vs
        inputs =
            Signal.mergeMany (messages.signal :: List.map (Signal.map (\x -> [x])) config.inputs)

Sure. :smile:
Actually, when I wrote that code I defined it as singleton, because I was hoping that at some point List.singleton would be moved from http://package.elm-lang.org/packages/circuithub/elm-list-extra to core, at which time I would come back to this code and use that function.

So what I was trying to get at above was that that in these lines we really want singleton to be a function explicitly passed to another function, not inlining it like in the other examples above.

Agreed :+1:


Fix typos in MigrationCreator file

This PR is to fix typos in MigrationCreator file.

I'll take a look

Any feedback, please? @taylorotwell

Probably because multi-line comments in Laravel are written in a way that each line is a specific number of characters shorter than the preceding line. He'll want to make the corrections in a way that maintains this style.


Flaky test turned CI bot red

vm-kernel-nnbd-linux-release-x64 bot turned red at https://ci.chromium.org/p/dart/builders/ci.sandbox/vm-kernel-nnbd-linux-release-x64/3109 due to
There are new unapproved failures on this build
There are unapproved failures
(dartk-weak-asserts-linux-release-x64):
    service/async_star_step_out_test/service_1   (Pass -> Timeout, expected Pass) at a0ed69

Deflaking log says the test passed 5 times:
Test configuration:
    dartk-weak-asserts-linux-release-x64(architecture: x64, compiler: dartk, mode: release, runtime: vm, system: linux, nnbd: weak, builder-tag: vm_nnbd, enable-asserts)
Suites tested: benchmark_smoke, corelib, ffi, language, lib, samples, service, standalone, utils, vm
Total: 1 tests
 * 0 tests will be skipped (0 skipped by design)
 * 0 tests are expected to be flaky but not crash
 * 0 tests are expected to flaky crash
 * 1 tests are expected to pass
 * 0 tests are expected to fail that we won't fix
 * 0 tests are expected to fail that we should fix
 * 0 tests are expected to crash that we should fix
 * 0 tests are allowed to timeout
 * 0 could not be categorized or are in multiple categories

--- Total time: 01:10 ---
0:00:16.345720 - vm - dartk-vm release_x64/service/async_star_step_out_test/service_1
0:00:13.630006 - vm - dartk-vm release_x64/service/async_star_step_out_test/service_1
0:00:13.583862 - vm - dartk-vm release_x64/service/async_star_step_out_test/service_1
0:00:13.578357 - vm - dartk-vm release_x64/service/async_star_step_out_test/service_1
0:00:13.112040 - vm - dartk-vm release_x64/service/async_star_step_out_test/service_1

=== All 5 tests passed ===
INFO: Core dump archiving is activated
INFO: No unexpected crashes recorded

@whesse @athomas Why that particular one-time failure turned bot red? Are we not filtering flaky test failures anymore?

Another case happened on https://ci.chromium.org/p/dart/builders/ci.sandbox/app-kernel-linux-release-x64/10130 build, where the bot turned red due to failure standalone_2/io/regress_flutter_57125_test   (Pass -> Timeout, expected Pass), while it passed 5 times during deflaking.

I suspect this may have to do with my rewrite of the logic that marks a flaky record as active: false when it is forgiven, and sets it to active: true when flakiness is seen again.  The test with the problem does have an inactive flaky record, and it is not being set to active again, and the timeout seen from the original run (not the deflaking runs) is not being stored in the flaky record.


Cope with the possibility of overloaded "pointee" members

This can happen if we end up introducing separate ABI vs. always-emit-into-client versions.

@swift-ci please smoke test

@swift-ci please smoke test


/api/admin/login not working with --username and/or --password options

Empire Version
Most recent
OS Information (Linux flavor, Python version)
Ubuntu
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
When you start the server with "./empire --username test --password test --headless" you could then get the token with:
"curl --insecure -i -H "Content-Type: application/json" https://<IP_ADDRESS>:1337/api/admin/login -X POST -d '{"username":"test", "password":"test"}'". Right now, it does not work.
The error comes from the fact that in the flask part, in the part:
@app.route('/api/admin/login', methods=['POST'])
def server_login():
the "username" variable is an array and "return ' '.join(username)" and doing the curl request returns:
HTTP/1.0 200 OK
Content-Type: text/html; charset=utf-8
Content-Length: 7
Server: Werkzeug/0.11.9
Date: Fri, 23 Sep 2016 22:25:27 GMT
t e s t%
Solution:
The simplest solution is to do the following (the modification in bold):
@app.route('/api/admin/login', methods=['POST'])
def server_login():
"""
Takes a supplied username and password and returns the current API token
if authentication is accepted.
"""
    if not request.json or not 'username' in request.json or not 'password' in request.json:
        abort(400)

    suppliedUsername = request.json['username']
    suppliedPassword = request.json['password']

    # try to prevent some basic bruting
    time.sleep(2)

    if suppliedUsername == **''.join(username)** and suppliedPassword == **''.join(password)**:
        return jsonify({'token': apiToken})
    else:
        return make_response('', 401)

This is a duplicate of #329

Going to go ahead and close this one due to duplicates.


Drop DB deletion from test-esx

Details from this issue
https://github.com/vmware/docker-volume-vsphere/issues/865
Our original plan was as follows:
introduce schema version in the DB
force DB deletion on test to hide "no versioned" -> "versioned" schema update
For further schema changes, support version to version in-place upgrade
so, the auth_db deletion was a temporary measure. It should not be needed anymore, we just need to make sure we do not have really stale DBs around
Actions:
we should drop the DB delete from test set (@liping)
if you still have od DB, remove it manyully per error message
This PR is used to track the first action which drop the DB delete from test set
Going forward,  for further schema changes, we will support version to version in-place upgrade.
If incase user has any ancient DB(no version), he/she need to remove it manually.

Fixed #865


sitemap.xml and robot

hi,
i am new  to this where we can ut sitemap.xml and robot files .
regrds
gmchaturvedi

That is a very good question, How did I missed it.. :D
Well anything in src/public/ folder is available via /public/ But I know its not appropriate to add robots.txt & sitemap.xml with prefix like /public/robot.txt or /public/sitemap.xml
Its a bug and would be solved.
@gmchaturvedi1 Are there any other files that needs to be directly accessible via root of url?
i.e. /robot.txt  or /abc.xyz ?

Are there any other files that needs to be directly accessible via root of url?

favicon.ico, the sw.js if you don’t already have those in mind

@dav-is favicon is already handled

@gmchaturvedi1 With latest push on master branch if you add sitemap.xml/robot.txt to src/public folder it should be accessible via /robot.txt or /sitemap.xml.


Unable to Run floogen Command with Example Configuration

I am unable to run the floogen command as described in the README. I installed Bender and added a few print and debugging statements to link.py to understand the issue. However, I am encountering the following errors when I run the command. I used the example provided in the README as my configuration file.

Any guidance on how to resolve this issue would be greatly appreciated. Thank you for your help.

The issue was resolved by updating the protocol names in the Example configuration file to adhere to the naming conventions expected by the code. By ensuring that the protocol name is axi, the tool could correctly process the configuration and generate the desired NoC architecture. If you encounter similar issues, please ensure your protocol names in the configuration file follow the required naming conventions.


Accounts with legacy CAN associated broken after oracle update.

After the oracle update, accounts that either 1.supplied CAN, 2.borrowed CAN or 3.enabled CAN as collateral becomes unusable.
These are legacy positions that have not been completely removed from Venus and still affects accounts that interacted with CAN.
It affects not only the ui such as https://app.venus.io/ and https://venus.finance/app. But also direct contract interaction.

From issue report #44, it seems that the problem is not limited to accounts that has CAN associated with it.

it is cause the chainlink Oracle does not have price for CAN, and without having price the liquidity calculation in venus is broken for those users who have CAN enabled as collateral, the other user issue you mention has also CAN enabled.
I reported this bug directly to Venus Team 3 days ago so hopefully they are "working" on it.

it is cause the chainlink Oracle does not have price for CAN, and without having price the liquidity calculation in venus is broken for those users who have CAN enabled as collateral, the other user issue you mention has also CAN enabled.
I reported this bug directly to Venus Team 3 days ago so hopefully they are "working" on it.

I didn't see any CAN supplied or borrowed and thought it's independent of CAN. So it seems it's CAN related after all.

https://bscscan.com/address/0xfd36e2c2a6789db23113685031d7f16329158384#readProxyContract
on this contract you can check the address which market has enabled as collateral getAssetsIn function

you can see he have the Venus CAN market address in the list which means he had it enabled in the past and thats causing the error

Has the project been abandoned?

In order to solve this issue, should set price for CAN in chainlink as 0.00001 under value $0.01 cent due to the market already added unable to remove or update current priceOracle to handle except for unsupported asset

Will chainlink add CAN just to fulfil venus oracle needs? Can the oracle be reverted back to BAND till the issue is fixed? What's going to happen to all the funds that are currently stuck due to this?

Will chainlink add CAN just to fulfil venus oracle needs? Can the oracle be reverted back to BAND till the issue is fixed? What's going to happen to all the funds that are currently stuck due to this?

they dont need chainlink for that, the venus oracle that was deployed by venus which reads from chainlink, has a function to set a fixed DirectPrice for a certain asset which can solve this issue without bothering chainlink at all.

Closing as stale. If your issue has not been resolved, please leave a comment


Fix type inference

Right now, the type inference goes through but it doesn't actually change the NIR graph. This PR fixes that.

For me the inference changed the graph already without your modifications. Did you observe the nodes not changing in a specific instance?
The dataclasses are mutable unless set to frozen. That is why it is not necessary to actively write the nodes back into the graph.

yep I just wrote tests to check that this works, but the problem was something else. I will update the PR in a moment - sorry about the confusion


React step 1

Changelog
First for the project! yay

Hi, the component  and  no work, then I lift up "repositories" to , also I hardcode to add "|" between "Carbon Tutorial" and "Repositories" inside the . it looks weird :)


[DOCS] Better formatting of text in the Events documentation.

Description
Information in the Events documentation page is not formatted properly which may cause difficulty for the user to understand.
This small fix will bring more clarity in documentation.
Screenshots
For Example can be written in the second line for better visibility

Extra line spacing and a ";" can be seen

Additional information
No response

Removing the blank line and ; would be a good improvement.

I am new to open source and I would like to contribute. Please assign me.

Removing the blank line and ; would be a good improvement.
@MAYANKpandey14 do you want this assigned to you

Thank you, However I think this can become someone's first pull request.

I am new to open source and I would like to contribute. Please assign me.

@tusharkumar19701 I will assign this to you

@SaraJaoude Thanks for assigning me this issue.

what to do after cloning it in my terminal......unable to open the file

sorry I just don't know how to do it....I am unassigning myself

sorry I just don't know how to do it....I am unassigning myself

I'll assist you, @tusharkumar19701 🥳

what to do after cloning it in my terminal......unable to open the file

It will be saved as a Folder with the Name LinkFree . Open it and go to pages/docs/how-to-guides/events.mdx LinkFree -> pages -> docs -> how-to-guides -> events.mdx This events.mdx file is what you have to edit to debug the issue .
Ask freely @tusharkumar19701 if you get stuck in future . No need to get demotivated and quit, it is a part of the process, there is always something you are absolute beginner in.

So True 🥳

Hi, I ✋ would like to work on that issue, if that would be ok please assign me the issue. I can do that changes.

sorry I just don't know how to do it....I am unassigning myself

@tusharkumar19701 We appreciate that if you do not feel ready to work on an issue that you mention this - we want our contributors to feel comfortable.  Don't forget that when you are ready to contribute again you can check out the list of unassigned 'good first issues' which I have added here.
Also, as others have said here please do reach out and ask questions in the EddieHub Discord! Whilst maintainers prefer that conversation regarding an issue is done publicly on the issue's comments so they can help, Discord is a great way to bounce ideas and get the community's feedback.

Hi, I ✋ would like to work on that issue, if that would be ok please assign me the issue. I can do that changes.

@jaskarandji I have assigned this to you.

Thanks all of you for showing your support. I would definitely try to contact community members if I have any issues. I was just frustrated at that moment. After spending hours I was clueless, so that's why I unassigned myself. Next time I won't be quitting, I will definitely try to ask my doubts and clear them. Sorry for causing disturbance.

I have set the formatting of text and I want to ask that I created a separate branch for edit to debug the issue. My branch is now ready to go. Should I merge it with the main branch or should I do this 👇 ?

@jaskarandji please do as you mention in the screenshot (create Pull Request from your fork repo's branch Text-Format to the EddieHub LinkFree main branch).
This will then appear on our list of Pull Requests and will be reviewed by a maintainer in due course.

merged


Document the ingressClassName field

Preview: https://deploy-preview-1196--cert-manager-website.netlify.app/docs/configuration/acme/http01/#ingressclassname

Implementation PR: https://github.com/cert-manager/cert-manager/pull/5849

I addressed you comments. PTAL @wallrj


Style, end each list item with a period

In bulleted and numbered lists, end each list item with a period if:
Any item forms a complete sentence when combined with the list introduction that precedes the colon.
Style Guide: Lists Punctuation

@javierruizjimenez : Thanks for your contribution! The author, @eross-msft, has been notified to review your proposed change.


fix text in portuguese

Fix text in portuguese.

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[ x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[ x] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

Congrats @gloriaabreualves on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


State of the art radio reverse engineering disclosure

Hi,
This pull request adds documentation on the physical layers of the io-homecontrol protocol and a basic patch for GNURadio allowing to decode frames using an RTL-SDR (on the basis of 010101b's work). It is a WIP, reach me if you want details on how these have been found and how you can catch the train. We were 3 to catch up on 010101b's work but I did not credit the 2 others as I don't know if they want to.

@Aldohrs Thanks for your input! I have a huge pile of information i found. QEMU is a big help with this ARM stuff. It also seems that the rtl_433 implementation is wrong. Never thought about using gnuradio…
We should bundle our efforts and i will get in contact with you


fix: typos in documentation for multiple files

Added typo corrections to documentation for the following files
shapeshift-web/blob/develop/docs/asset-generation.md
typo in the text:
set is as an environment variable" should be "set it as an environment variable" (use "it" instead of "is").
 The phrase "handful" is the correct form.

Corrected.
shapeshift-web/blob/develop/docs/styles.md
"can not" should be "cannot" (it's generally preferred to write "cannot" as a single word).
Corrected.
shapeshift-web/edit/develop/src/assets/translations/ru/main.json
Typos have been identified and corrected.
Goal
Correct grammatical errors and improve readability of the documentation.

Thanks for the Russian translation suggestions @mdqst!
As we use a third-party platform to do the translation work (Gitlocalize), could you please revert this commit and I will submit them to our Russian translator for review during the next biweekly translation sync. Thanks in advance!

Ready for review as per https://discord.com/channels/554694662431178782/1001570348380200980/1304223232945029221

Thanks for the merge!
@mdqst I was able to reach our Russian translator for a quick review, but as suggested above, if you have more changes/suggestions for any language feel free to reach to me on Discord.


SearchBox Component with Auto Completion

A reusable search box with the ability to autocomplete a user's input would be an excellent component.
Besides the autocompletion, the component should allow the developer to specify its size or behave in a more responsive manner.
Some other interesting features would be basic input validation, a helper text property, a built-in submit button, and other types of styling customizations.

@IM-Deane Can you kindly assign this to me?

Sorry, but I'm unable to complete this at the given time. Would definitely love to contribute to this project sometime in the future. Thank you.


Token lifetimes with confidential client refresh tokens - VOLUNTARY PASSWORD RESET behavior

[Enter feedback here]
I can see that this sentence has been deleted now
https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes
Token lifetimes with confidential client refresh tokens
Confidential clients are applications that can securely store a client password (secret). They can prove that requests are coming from the secured client application and not from a malicious actor. For example, a web app is a confidential client because it can store a client secret on the web server. It is not exposed. Because these flows are more secure, the default lifetimes of refresh tokens issued to these flows is until-revoked, cannot be changed by using policy, and will not be revoked on voluntary password resets.
So what is the expected behavior in case of a VOLUNTARY password reset?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 02ff3d62-dc0e-ad0c-f5ae-418337cf31e4
Version Independent ID: d50952b5-6b98-c40d-d3a3-f9cbec58dd28
Content: Configurable token lifetimes - Microsoft identity platform
Content Source: articles/active-directory/develop/active-directory-configurable-token-lifetimes.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@AlexCesarini Thanks for the feedback. We will engage the content development team for further investigation, they will verify and perform necessary changes in the document as needed.

@AlexCesarini Yes, that text was removed since you can no longer configure the lifetimes of refresh tokens.  Looks like a refresh token for a confidential client will stay alive when the password is changed by a user.  See the revocation section in the access token article.  Hope that helps.

Sure
I suggest to cross reference this article in this section to add more clarity
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Ryan Wike @.>
Sent: Wednesday, May 19, 2021 12:22:45 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Lexo @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Token lifetimes with confidential client refresh tokens - VOLUNTARY PASSWORD RESET behavior (#75401)
@AlexCesarinihttps://github.com/AlexCesarini Yes, that text was removed since you can no longer configure the lifetimes of refresh tokens. Looks like a refresh token for a confidential client will stay alive when the password is changed by a user. See the revocationhttps://docs.microsoft.com/en-us/azure/active-directory/develop/access-tokens#revocation section in the access token article. Hope that helps.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/75401#issuecomment-843607134, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIXQ74RITERIKNB7QRBWV5DTOLSDLANCNFSM45AEFWNQ.

Yes, that's a good idea.  I'll do that.  Thanks for the input.

Just updated the article, changes will go live soon.  #please-close


[WIP] rhash: fix static build

Motivation for this change
Trying to get pkgsStatic.cmake to work. Probably not totally necessary for actual builds, since nativeBuildInputs = [ cmake ]; seems to pull in the non-static version. But thought it would just be a good exercise to see if I could get it to build.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

cc @Ericson2314 , my current issue is ar: command not found, looks like pkgsStatic.stdenv.cc.bintools.bintools exports commands that have the targetPrefix on each of them.
$ ls $(nix-build -A pkgsStatic.stdenv.cc.bintools.bintools)/bin
x86_64-unknown-linux-musl-addr2line  x86_64-unknown-linux-musl-c++filt  x86_64-unknown-linux-musl-gprof   x86_64-unknown-linux-musl-ld.gold  x86_64-unknown-linux-musl-objdump  x86_64-unknown-linux-musl-size
x86_64-unknown-linux-musl-ar         x86_64-unknown-linux-musl-dwp      x86_64-unknown-linux-musl-ld      x86_64-unknown-linux-musl-nm       x86_64-unknown-linux-musl-ranlib   x86_64-unknown-linux-musl-strings
x86_64-unknown-linux-musl-as         x86_64-unknown-linux-musl-elfedit  x86_64-unknown-linux-musl-ld.bfd  x86_64-unknown-linux-musl-objcopy  x86_64-unknown-linux-musl-readelf  x86_64-unknown-linux-musl-strip

Closing since #126621 has been merged

was just about to close :)


[e2e]: generic push main upload-tag-name slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7705276596
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Trigger: push
Branch: main
Date: Tue Jan 30 02:12:56 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7720199710
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Trigger: push
Branch: main
Date: Wed Jan 31 02:13:30 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7735232722
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.main.upload-tag-name.slsa3.yml
Trigger: push
Branch: main
Date: Thu Feb  1 02:16:24 UTC 2024
Tests are passing now. Closing this issue.


Allow sass usage from npm package.

Hi,
I want to use the sass version of milligram when installing it with npm. This requires the src directory to be included though. This will add the src directory to the published npm package.

Hi @jvanveen. You can see more about this issue here #79. Let me know if you have any doubts.
For now I will close the PR. Thanks for the contribution!

hi,
i added a comment in the issue. thanks for the quick response!


space: Fix clobbering presence data

Before this commit, space.updateProfileData would call presence.update with just the updated profile data, removing the previous and current locations that might be set in the presence data.
This commit fixes the issue by introducing an updateSelf function which allows callers to mutate the member retrieved from getSelf and trigger a presence update which maintains unrelated fields within the resulting presence data.

Superseded by changes in https://github.com/ably-labs/spaces/pull/101.


Bug report  com.netflix.loadbalancer.AbstractServerPredicate

public Optional<Server> chooseRoundRobinAfterFiltering(List<Server> servers, Object loadBalancerKey){
    List<Server> eligible = getEligibleServers(servers, loadBalancerKey);
    if (eligible.size() == 0) {
        return Optional.absent();
    }
    return Optional.of(eligible.get(nextIndex.getAndIncrement() % eligible.size()));
}

when nextIndex beyond the range of integers,  the method will throw a ArrayIndexOutOfBoundsException. eligible.get(-1).

Hi @wangfuguo
I think what you said makes sense, we can use math.abs ((nextIndex.getAndIncrement()) to avoid this situation.
But the AbstractServerPredicate  class is in the Netflix/ribbon project, is it better to submit this issues to Netflix/ribbon ?

Hi@holy12345
Thanks. The new version of Netflix/ribbon has solved the problem.

Hi@holy12345
Thanks. The new version of Netflix/ribbon has solved the problem.

Hi @holy12345
Thanks. The new version of Netflix/ribbon has solved the problem.


Socint 329 withdrawal refusal

change Refusal DTO to include note and eraseData, and remove dateTime
accept new refusal reason WITHDRAWAL_REFUSAL
some changes to tidy up interaction / subinteraction validation

JIRA LINK: https://collaborate2.ons.gov.uk/jira/browse/SOCINT-329

A couple of sore thumbs stick out in this - and not necessarily as a direct result of this work itself, but from accumulative debt that nonetheless, should perhaps be addressed here.

I see that the caseapi code has a model enum type RefusalType, and that is being reused elsewhere ie here. Not a good place for such an enum - as event publisher only uses String,  the common framework domain package would be a more logical home for RefusalType.
The saveCaseInteraction(...) takes the interaction type and subtypes, and does not validate that they are compatible. Perhaps when the interaction code was first written we thought it would only be necessary to validate the pair when the UI asked for an interaction to be saved, but I see no reason for the saveCaseInteraction(...) called for implicit interactionst as well as explicit UI interaction requests to instead include that validation.
point 2 comes up because strictly, according to the definition of the Refusal interaction type, subtypes are not allowed, even though we have subtypes for refusal defined in the sub type
The interactiontype should specify that the subtypes are valid.
The subtype naming was such that related subtypes were clearly identifiable by their prefix. This leads to slighly smelly code where to use the subtype enum we have to prefix the required with "REFUSAL_". Perhaps we should align the REFUSAL_ subtype names with the actual RefusalType names for clarity and maintenance.

Changes made, as requested.


Withdrawals from bsc to stellar are not being processed

From the master logs:
INFO [06-26|14:00:23.123] Remembering withdraw event for txHash=2c322f…c3a5a1 height=8635075 network=stellar
INFO [06-26|14:19:11.190] Remembering withdraw event for txHash=b67d12…cd4f45 height=8635451 network=stellar

No further logs found for the processing of these withdrawals

going to try to reproduce on testnet once https://github.com/threefoldfoundation/tft/issues/111 is done

Restarted  of the master, after a while it bstarted processing the withdrawals but could not reach the cosigner. Restarted the cosigner and they went through. Closing for now, hope the little bit of extra logging might make us a bit wiser.


"run test" code action does not raise the result of the test.

It would be useful to raise the output of the of test result either in the diagnostics panel, or simply a "bulb" icon (success / fail) with a hover showing the log from the test.
Gopls version: 0.8.3
ST4 version: 4126
lsp-gopls version: 1.0.5
reproduction steps:

open a go project that has tests
use the "code_action" called "run tests"
observe that there is no (obvious) output from the test run

You can sort-of get a quick summary in the status bar, if you're quick enough.
Or you can see the full RPC trace in the LSP log panel, which is not particularly easy to read.

I think that I can intercept this request and then output the content into a Test Panel

WIP:  https://github.com/sublimelsp/LSP-gopls/tree/f/test_log_panel
https://user-images.githubusercontent.com/32599364/171789125-23e6f386-0826-4a06-8b7f-62f78ad489c4.mp4

Open PR: https://github.com/sublimelsp/LSP-gopls/pull/21

Implemented in v1.0.6


Adds failing test using rename with Django model

PR of failing test to demonstrate issue #236 "Cannot use rename with DjangoModelFactory"

The CI trace is different from my local machine and isn't highlighting the actual issue. I was getting:
(factory_boy)James-MacBook-Pro-Personal:factory_boy James$ make DJANGO=1.8 test
python -W default setup.py test
/Users/James/.virtualenvs/factory_boy/lib/python3.4/imp.py:32: PendingDeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
  PendingDeprecationWarning)
running test
running egg_info
writing top-level names to factory_boy.egg-info/top_level.txt
writing factory_boy.egg-info/PKG-INFO
writing dependency_links to factory_boy.egg-info/dependency_links.txt
reading manifest file 'factory_boy.egg-info/SOURCES.txt'
/Users/James/.virtualenvs/factory_boy/lib/python3.4/site-packages/setuptools/command/sdist.py:183: DeprecationWarning: 'U' mode is deprecated
  manifest = open(self.manifest, 'rbU')
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'docs/_build'
writing manifest file 'factory_boy.egg-info/SOURCES.txt'
running build_ext
Traceback (most recent call last):
  File "setup.py", line 72, in <module>
    test_loader=test_loader,
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/Users/James/.virtualenvs/factory_boy/lib/python3.4/site-packages/setuptools/command/test.py", line 142, in run
    self.with_project_on_sys_path(self.run_tests)
  File "/Users/James/.virtualenvs/factory_boy/lib/python3.4/site-packages/setuptools/command/test.py", line 122, in with_project_on_sys_path
    func()
  File "/Users/James/.virtualenvs/factory_boy/lib/python3.4/site-packages/setuptools/command/test.py", line 163, in run_tests
    testRunner=self._resolve_as_ep(self.test_runner),
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/unittest/main.py", line 92, in __init__
    self.parseArgs(argv)
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/unittest/main.py", line 139, in parseArgs
    self.createTests()
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/unittest/main.py", line 146, in createTests
    self.module)
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/unittest/loader.py", line 146, in loadTestsFromNames
    suites = [self.loadTestsFromName(name, module) for name in names]
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/unittest/loader.py", line 146, in <listcomp>
    suites = [self.loadTestsFromName(name, module) for name in names]
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/unittest/loader.py", line 105, in loadTestsFromName
    module = __import__('.'.join(parts_copy))
  File "/Users/James/Documents/Work/Open Source/jamesbeith/factory_boy/tests/__init__.py", line 7, in <module>
    from .test_django import *
  File "/Users/James/Documents/Work/Open Source/jamesbeith/factory_boy/tests/test_django.py", line 102, in <module>
    class StandardFactoryWithRenamedField(factory.django.DjangoModelFactory):
  File "/Users/James/Documents/Work/Open Source/jamesbeith/factory_boy/factory/base.py", line 123, in __new__
    base_factory=base_factory,
  File "/Users/James/Documents/Work/Open Source/jamesbeith/factory_boy/factory/base.py", line 208, in contribute_to_class
    self._fill_from_meta(meta=meta, base_meta=base_meta)
  File "/Users/James/Documents/Work/Open Source/jamesbeith/factory_boy/factory/base.py", line 200, in _fill_from_meta
    % (self.factory, ','.join(sorted(meta_attrs.keys()))))
TypeError: 'class Meta' for <class 'tests.test_django.StandardFactoryWithRenamedField'> got unknown attribute(s) rename
make: *** [test] Error 1

This should be fixed in 2.6.0; feel free to reopen it if it's still broken :)


Pull Mesh Branch w/o commit history into mesh_integration

Decided we didn't want to bring commit history from ImmersiveDroneInterface, not even squashed histories. (Also there are residual files that we don't want)
Starting fresh with file by file copy.

Completed with commit 93839e


HOTT-930: Spec to catch when the CDS import failed

Failure was caused by missing load of entities by entity mapper. Check to ensure the list of MAPPERS is not empty.
Jira link
HOTT-930
What?
I have added/removed/altered:

[x] Added a spec to ensure the CDS importer has some entities to map

Why?
I am doing this because:

When the zeitwerk autoloader was enabled it broke autoloading of the entity mappers. This was not picked up because the specs mocked the list of entity mappers to use.
So I've added a spec to ensure when the list isn't mocked, it is still not empty.

Merging this PR since the same change on a broken branch was approved - see #203


Greyhound service not responding

I have install a Docker container for a Greyhound service on a server.  Time to time the service going down without any relevant details through docker logs.  The info request never respond (/resource/270_merge_3857/info) and Greyhound docker container need to be restarted to get back on track.  Where should I look to have more info on this problem. Is it a Docker, Greyhound or Entwine index config problem?

My first guess would be Greyhound.  What sort of logs do you see before the failure?
Does the server launch with logs that look like this?
Sun Sep 18 2016 16:11:59 GMT+0000 (UTC) LOG Using
Sun Sep 18 2016 16:11:59 GMT+0000 (UTC) LOG 	Chunk cache size: 64
Sun Sep 18 2016 16:11:59 GMT+0000 (UTC) LOG 	Libuv threadpool size: 5
Sun Sep 18 2016 16:11:59 GMT+0000 (UTC) LOG Read paths: [ /* */ ]
Sun Sep 18 2016 16:12:00 GMT+0000 (UTC) LOG HTTP server running on port 80

Any logging after that once you attempt to load the resource?  Also, is this data public?  If so I could try to reproduce locally.

Not public data but I'll ask to customer and send you a link if needed.  When I start Greyhound container, my log is:
Mon Sep 19 2016 18:35:46 GMT+0000 (UTC) LOG Using default config
Mon Sep 19 2016 18:35:47 GMT+0000 (UTC) LOG Using
Mon Sep 19 2016 18:35:47 GMT+0000 (UTC) LOG 	Chunk cache size: 32
Mon Sep 19 2016 18:35:47 GMT+0000 (UTC) LOG 	Libuv threadpool size: 5
Mon Sep 19 2016 18:35:47 GMT+0000 (UTC) LOG Read paths: [ '/opt/data' ]
Mon Sep 19 2016 18:35:47 GMT+0000 (UTC) LOG HTTP server running on port 80

here's log before failure
GET /resource/RDP_RMI/read?depthBegin=11&depthEnd=12&bounds=[273867.5,5045122.5,25,278745,5050000,4902.5]&schema=[{%22name%22:%22X%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Y%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Z%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Intensity%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Classification%22,%22size%22:1,%22type%22:%22unsigned%22},{%22name%22:%22Red%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Green%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Blue%22,%22size%22:2,%22type%22:%22unsigned%22}]&scale=1&offset=[288500,5050000,25]&compress=true - - ms - -
GET /resource/RDP_RMI/read?depthBegin=10&depthEnd=11&bounds=[268990,5040245,-9730,278745,5050000,25]&schema=[{%22name%22:%22X%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Y%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Z%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Intensity%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Classification%22,%22size%22:1,%22type%22:%22unsigned%22},{%22name%22:%22Red%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Green%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Blue%22,%22size%22:2,%22type%22:%22unsigned%22}]&scale=1&offset=[288500,5050000,25]&compress=true - - ms - -
GET /resource/RDP_RMI/read?depthBegin=11&depthEnd=12&bounds=[273867.5,5045122.5,25,278745,5050000,4902.5]&schema=[{%22name%22:%22X%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Y%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Z%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Intensity%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Classification%22,%22size%22:1,%22type%22:%22unsigned%22},{%22name%22:%22Red%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Green%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Blue%22,%22size%22:2,%22type%22:%22unsigned%22}]&scale=1&offset=[288500,5050000,25]&compress=true - - ms - -
GET /resource/RDP_RMI/read?depthBegin=10&depthEnd=11&bounds=[268990,5040245,-9730,278745,5050000,25]&schema=[{%22name%22:%22X%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Y%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Z%22,%22size%22:4,%22type%22:%22signed%22},{%22name%22:%22Intensity%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Classification%22,%22size%22:1,%22type%22:%22unsigned%22},{%22name%22:%22Red%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Green%22,%22size%22:2,%22type%22:%22unsigned%22},{%22name%22:%22Blue%22,%22size%22:2,%22type%22:%22unsigned%22}]&scale=1&offset=[288500,5050000,25]&compress=true - - ms - -
GET /resource/RDP_RMI/info - - ms - -

Hi Connor,
I have some news on this issue.  The RDP_RMI resource was transfert on server for publishing with an rsync command before while an other process was running a entwine build command (on the same laptop).   So the entwine index was corrupted or uncompleted and Greyhound crash on a reading query.  I'm not sure if customer was trying to read resource while he was copying entwine index on server (can be another failure cause)

Thanks for the update.  Were you able to reach the resource successfully with Greyhound after the full entwine index was loaded?
Of course, either way, crashing is not the appropriate response from Greyhound.  I may make a separate issue to more robustly handle some error cases within Greyhound to ensure appropriate responses for cases like this.  Hopefully you are able to continue with your workflow in the meantime.

Yes after restarting Greyhound container, we were able to open it in the viewer.
Here's the log of an other failure this morning.

Thanks for the data - I've got it built locally and have been browsing around.  So far I've been unable to replicate the issue in Potree.  From those logs, my guess is that your Greyhound container may be running low on memory, causing the requests to hang.  The - - in the log indicates that the request never receives a response, but did not crash or cause an explicit error.
Have you checked the output of free -g within your container while that error is occurring?  Do you have some information on the instance on which Greyhound is running?  How much memory is available?  Have you enabled any swap space?
One quick thing to try might be lowering Greyhound's chunk cache size.  You can do this by creating a configuration file that looks like this and changing the chunkCacheSize to 24 (for example).  Then:
# Assume your config file is located at ~/greyhound-config.js
docker run -it -v `pwd`:/opt/home connormanning/greyhound "bash -c \"cp /opt/home/greyhound-config.json /var/greyhound/config.json && greyhound dockerstart && greyhound log\""

Hi
after a greyhound container update, I try to set chunkCacheSize to 24 (greyhound crash ).  I create a config file (/var/greyhound/config.json) but when I restart container, change is not apply. If I connect to greyhound container and I try greyhound -c /var/greyhound/config.json or greyhound dockerstart I have this loop error:
Error: listen EADDRINUSE :::8080
    at Object.exports._errnoException (util.js:907:11)
    at exports._exceptionWithHostPort (util.js:930:20)
    at Server._listen2 (net.js:1250:14)
    at listen (net.js:1286:10)
    at Server.listen (net.js:1382:5)
    at HttpHandler.start (/usr/lib/node_modules/greyhound-server/src/interfaces/http/index.js:61:36)
    at /usr/lib/node_modules/greyhound-server/src/app.js:70:21
    at nextTickCallbackWith0Args (node.js:420:9)
    at process._tickCallback (node.js:349:13)
    at Function.Module.runMain (module.js:443:11)
    at startup (node.js:139:18)
    at node.js:974:3
Relaunching greyhound
Mon Oct 17 2016 03:12:54 GMT+0000 (UTC) LOG Using default config
Mon Oct 17 2016 03:12:54 GMT+0000 (UTC) LOG Using
Mon Oct 17 2016 03:12:54 GMT+0000 (UTC) LOG 	Chunk cache size: 32
Mon Oct 17 2016 03:12:54 GMT+0000 (UTC) LOG 	Libuv threadpool size: 5
Mon Oct 17 2016 03:12:54 GMT+0000 (UTC) LOG Read paths: [ '/opt/data', '~/greyhound', 'http://greyhound.io' ]
Mon Oct 17 2016 03:12:54 GMT+0000 (UTC) LOG HTTP server running on port 8080
events.js:141
      throw er; // Unhandled 'error' event
...
...

How can I restart container with custom config file?

Personally I'd just restart the container completely pointing at your new configuration.  If you want to use the same container, in f09de45 I've added a name to the monitoring task (re-pull docker to get it), so you can kill greyhound with something like kill -9 $(pidof greyhound-monitor).
By the way, launching with a custom config is now simpler than my previous comment, just use -c with no copying necessary and no more dockerstart command:
docker run -it -v ~:/opt/home connormanning/greyhound greyhound -c /opt/home/greyhound-config.json

I try it with the new -c option. It seems to work but  Chunk cache size: undefined in log. How can I know if greyhound really use my custom chunksize or it's a bug?
root@demo-preview5:/opt/data/greyhound# docker run -d -v /opt/data/greyhound:/opt/data --name "greyhound" -p 8080:8080 --restart unless-stopped connormanning/greyhound  greyhound -c /opt/data/greyhound.config.json
root@demo-preview5:/opt/data/greyhound# docker logs greyhound
Tue Oct 18 2016 13:45:29 GMT+0000 (UTC) LOG Using config at /opt/data/greyhound.config.json
Tue Oct 18 2016 13:45:29 GMT+0000 (UTC) LOG Using
Tue Oct 18 2016 13:45:29 GMT+0000 (UTC) LOG 	Chunk cache size: undefined
Tue Oct 18 2016 13:45:29 GMT+0000 (UTC) LOG 	Libuv threadpool size: 5
Tue Oct 18 2016 13:45:29 GMT+0000 (UTC) LOG Read paths: [ '/opt/data', '~/greyhound', 'http://greyhound.io' ]
Tue Oct 18 2016 13:45:29 GMT+0000 (UTC) LOG HTTP server running on port 8080
root@demo-preview5:/opt/data/greyhound# cat greyhound.config.json
{
    "queryLimits": { "chunksPerQuery": 16, "chunkCacheSize": 24 },
    "paths": ["/opt/data", "~/greyhound", "http://greyhound.io"],
    "resourceTimeoutMinutes": 30,
    "http": {
        "port": 8080,
        "enableStaticServe": true,
        "headers": {
            "Cache-Control":                  "public, max-age=300",
            "Access-Control-Allow-Origin":    "*",
            "Access-Control-Allow-Methods":   "GET,PUT,POST,DELETE"
        }
    }
}

Ah, sorry about that.  In this wave of simplifications I've been doing I tweaked that configuration format, but I haven't yet pushed the new documentation.  It should work if you remove the queryLimits key, and make it look like this:
{
    "chunksPerQuery": 16,
    "chunkCacheSize": 24,
    "paths": ...
}

Updated docs will be out soon.


How can I deploy a single-card MLC-LLM model? I want the model inference to run only on one card, not distributed.

📚 Documentation
Suggestion

Bug

Link to the buggy documentation/tutorial:
Description of the bug:

By default mlc llm deployment should be single card


Add option to report error if there are extraneous keys in operation or app arguments

This is of limited utility, as it only checks the top-level map, not any nested ones.


Lint for usage of plain text instead of using i18n

Having a lint that detects usage of plain text in .haml files would help enforce usage of i18n across all views.
For example, I imagine these would be linted:
Hello World

.div Hello World
.div
  Hello World

and these not:
= t('hello')

.div= t('hello')
.div
  = t('hello')

If that's a thing that's welcome and in the realm of possibility, I'd be happy to contribute this lint.

Open to a well-tested pull request with the linter disabled by default!

@phansch There are a few ways to do this and even more ways to improve it depending on your codebase, there is a WIP linter for GitLab at https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/11457 if you wanted to check it out.
It can be as simple as reporting every visit_plain visit.

@phansch I made a simple linter that lints most cases like:
.div Hello World
.div
  Hello World
.div= "Hello World"
.div
  = "Hello World"
.div= "Hello #{user},"
.div
  = "Hello #{user},"
.div= "Hello t('user'),"
.div
  = "Hello t('user'),"
.div Hello t('user'),
.div
  Hello t('user'),
-# etc...

And ignores the cases that you mention like:
.div= t('hello')
.div
  = t('hello')
.div= hello
.div= t('hello')
.div
  t('hello')

-# etc...

The class is available in a gist I made. The biggest problem are things that are not distinguishable from class names. For example:
.div{ class: 'some classes ' }
.div{ data: { confirm: 'Are you sure?' } }

Neither is linted, but the second should. Nevertheless, it's very useful :+1:


Started Python Work

I started on some Python code in my fork. Nothing fascinating, though. I set up a stub for a possible helper class with functions for parsing output from a git subprocess, input from the command line (the gum stage, gum switch, etc commands), and output from gum to the user. I'm not sure what we would use the input parsing function for unless we make it a wrapper for the optparse utilities in Python. Anyways, I thought I'd post a start.

Mitch. You are awesome.
I have a few other folks who are working on bash and alias versions of the same code. This weekend I am going to test them all and see which ones: stay out of the way of regular git and are the most cross platform.
By early next week we will know if this needs to be python based or bash based. Thank you again for your contribution.

How about having this repo as a "meta" project, only containing the concept/design and links to implementations? That would be huge creativity booster.

All for it. I will post any links to implementations while I am working on one myself.

I just released some git aliases in bash script. I want to see how far we can get in bash before going to python.
It could be soon.


Referral program needed in Easycloudbooks also.

Referral program needed in Easycloudbooks also. like Expcon.

Requirement - By @vinpahilwani

Referral Page in User Section
List of Companies which Requested with Referral Code
1st Credit (500 Rs) after Company Created
10% as Discount of Payment made by Company for 1 year Period from Company Createdate

Email Template Required for Sharing.
Post it Here

Email Template
Hi
I am excited to share I’ve created created my Online Practice on Easycloudbooks- A practice management software that helps you save time by automating recurring administrative tasks. You can create practice with following link ——— and get credit of Rs. 1000 as reward credit.
Thank you
(User Name)

Subject Line: @username has invited you to Easycloudbooks- Practice Management Softaware.

Please Provide this things

new page
https://user.easycloudbooks.com/referral


Update _config.yml

Update website

Delete contact page

Try to remove the background and update the index page

messed up the game page, restore

Remove the backgrounds, see how it goes


chore(main): release 1.2.6

:robot: I have created a release beep boop
1.2.6 (2023-09-02)
Bug Fixes

Plot Settings (d15d3dc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/chiba-ai-med/Landscaper/releases/tag/v1.2.6 :sunflower:


require error with async

Hey Samuel! I'm very excited about db gem and the new drivers you've been working on. I'd love to try it out with an SQL builder gem that I recently started working on, unfortunately I've hit this problem:
[1] pry(main)> require "db/postgres/connection"
LoadError: cannot load such file -- async/pool/resource
from /Users/solnic/.gem/ruby/2.7.2/gems/db-postgres-0.2.3/lib/db/postgres/connection.rb:23:in `require'
[2] pry(main)> require "async"
=> true
[3] pry(main)> require "async"
=> false
[4] pry(main)> require "db/postgres/connection"
LoadError: cannot load such file -- async/pool/resource
from /Users/solnic/.gem/ruby/2.7.2/gems/db-postgres-0.2.3/lib/db/postgres/connection.rb:23:in `require'

Is this expected? Thanks!

Can you please try v0.2.4 which includes the missing dependency.

@ioquatix it worked, thank you!

Great.


prismfees plugin method

calculate what the fees will be to pay a prism ahead of time.
This could be a nice data point for some UI's

In my opinion, this is out-of-scope for prisms. In lightning network, the sender pays fees to complete a payment. So there's nothing for us to worry about when RECEIVING a payment to a Prism--only when we payout to a receiver share. Since we are dealing with payment flows, we should simply account for the fees incurred as we go along. We should assume that core lightning is making intelligent decisions to minimize fees at the time of payment.

The fees to pay each prism member should be paid by the user paying the prism, not the prism node. And the sender would only have an idea of the fee to pay to the prism, but what if there are 100 prism members? Assuming fees comparable, that would be a 100x fee from what they thought they were paying.
In my opinion, if the prism node is going be accounting for fees, then the sender should know what fees will be incurred.

I definitely think that's out of scope. The user on a remote lightning node who pays to a Prism offer incurs the fees to pay to the Prism. From their perspective, they are paying a single lightning node. The BOLT12 Offer may or may not represent a Prism.
The design i prefer is one in which we are batching payments; it's not like every incoming payment to a Prism results in a payout for every member of that prism. Outlays are accrued until a payout threshold is reached and a payout occurs. Currently, fees from those payouts are paid by the Prism Owner by default, but we could instead account for payout fees in each prism member outlay value. In other words, payout fees are being deducted from future payouts for prism members resulting in Prisms members paying for fees for their payouts.
Furthermore, those prism members may have different outlay values and payout thresholds, values which may change over time. So I think providing an estimate would be difficult.


getaddrinfo when trying to use open-uri

Background:
I'm building Rails app(rails 3.0.7 / ruby 1.9.2) and in model I need to receive data from external websites. Example code:
require 'open-uri'
class Website < ActiveRecord::Base
  def read
    data = open(self.url)
    [...]
  end
end

When I call this code pow is returning error:
SocketError (getaddrinfo: nodename nor servname provided, or not known)

When I try this using "rails c" (tested with webrick and thin) everything is working fine... Pow version=0.2.2

This is an annoying bug that wasted hours of my time, follow the instructions to kill the errant pow process here
http://pow.cx/manual.html#section_2.5 to fix it.
Somehow, I had killed the pow process but an associated node.js process (I think) with a child ruby process that was serving up my app, stuck around with the bad DNS cache, so I kept getting the error. When I killed the node process, my app came right up.


"Add Existing" functionality no longer exists in current azure Portal interface

Looks like the documentation needs to be updated as their is no longer any way to add an existing disk to a VM

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d78385db-23e4-0471-6d03-262ac6c73407
Version Independent ID: d2ebdfb2-5f43-8bdc-fdb4-01948a275681
Content: Attach or detach a data disk to a virtual machine in Azure DevTest Labs
Content Source: articles/lab-services/devtest-lab-attach-detach-data-disk.md
Service: lab-services
Product: unspecified
GitHub Login: @spelluru
Microsoft Alias: spelluru

@ravensorb Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@ravensorb - Thanks for the feedback. I have tried the following steps and they worked fine for me.

Select Attach a new disk. Followed the steps to create a disk and attach it to the VM.
Detached the disk
Select Attach an existing disk. Followed the steps to attach an existing disk that was created in step 1.

Do you not see the Attach existing toolbar item? Or Do you see it but it's disabled? Could you provide details? Could you also let me know the type of the VM you are using? I am trying with Standard D8s v3 (8 cores, 32 GB memory).
Thanks

#please-close

@ravensorb We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

According to this document, Attach Existing should be there but I couldn't find it anywhere in the new portal,

also Detach is also missing or am I missing something?


Calculate project velocity

Describe the task
Currently the project and team member fte that we are showing is actually the velocity. So we need to replace that with velocity.
Also the fte of the team member in a project should be calculated based on the overall fte
i.e billable hours in project / (days till now * 8)
Expected behavior
SHow velocity and FTE
References
NA

This is deployed and working fine. Closing it now.


Problem with MariaDB 10.2

Hi,
I installed xmondrian under tomcat8 and tested it on our data with MySQL 5.7.22 - all works correctly.
Now I'm trying to switch it to the new database where the data will be migrated soon, and it does not work anymore. It seems that something is going wrong in getLevelMemberCount function, in mondrian.sql log I get the following logs:
2018-06-08 19:37:47,988 DEBUG [mondrian.sql] 3: SqlMemberSource.getLevelMemberCount: executing sql [
select
    count(*) as `c0`
from
    (select distinct
    `llx_olap_view_propal`.`date_valid_day` as `c0`,
    `llx_olap_view_propal`.`date_valid_month` as `c1`,
    `llx_olap_view_propal`.`date_valid_quarter` as `c2`,
    `llx_olap_view_propal`.`date_valid_year` as `c3`
from
    `llx_olap_view_propal` as `llx_olap_view_propal`) as `init`]

...for MySQL (working one)
and
2018-06-08 19:39:37,126 DEBUG [mondrian.sql] 3: SqlMemberSource.getLevelMemberCount: executing sql [
select
    count(DISTINCT `llx_olap_view_propal`.`date_valid_day``llx_olap_view_propal`.`date_valid_month``llx_olap_view_propal`.`date_valid_quarter``llx_olap_view_propal`.`date_valid_year`) as `c0`
from
    `llx_olap_view_propal` as `llx_olap_view_propal`]
2018-06-08 19:39:37,129 DEBUG [mondrian.sql] 3: , exec+fetch 3 ms, 0 rows
2018-06-08 19:39:37,129 DEBUG [mondrian.sql] 3: , failed (java.sql.SQLSyntaxErrorException: (conn=6863) You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '.`date_valid_quarter``llx_olap_view_propal`.`date_valid_year`) as `c0`)

...for MariaDB - error.
So in two cases, the SQL query is not the same, evidently the second query is incorrect.
I would try to fix it myself, but I cannot build mondrian, downloaded from https://github.com/pentaho/mondrian.
Can you share the build instructions, please?

I am investigating mondrian too, and had building experience of mondrian recently. I am not java developer, but i can share my experience. What your current building workflow and which errors you get?

I solved the problem, rebuilding mondrian 3.14 jar from sources jar, downloaded from Sourceforge.
The bug was in mondrian.rolap.SqlMemberSource.makeLevelMemberCountSql, around line 270
for (String colDef : columnList) {
                    if (i > 0) {
                        sb.append(", ");
                    }
                    sb.append(
                        sqlQuery.getDialect()
                            .generateCountExpression(colDef));
                    i++;    // ****************** this increment was lost
                }