Multiple lines of "fatal: not a git repository (or any of the parent directories): .git" during update

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
Probably not a bug per se, since everything is working alright - but maybe something to take a look into:
During docker-compose run inventree-server invoke update I always get multiple lines of the error message
fatal: not a git repository (or any of the parent directories): .git
Can I debug this further to understand where to look for fixing this?
Steps to Reproduce
Run  docker-compose run inventree-server invoke update in a docker production installation.
Expected behaviour
No fatal errors unless something is actually wrong ;-)
Deployment Method

[X] Docker
[ ] Bare metal

Version Information
Version Information:
InvenTree-Version: 0.11.0 dev
Django Version: 3.2.18
Commit Hash: e9a1b57
Commit Date: 2023-02-28
Database: postgresql
Debug-Mode: False
Deployed using Docker: True
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}, {'name': 'IPNAutoGenerator', 'slug': 'ipnautogenerator', 'version': None}, {'name': 'Brother Labels', 'slug': 'brother', 'version': '0.6.0'}]
Relevant log output
docker-compose run inventree-server invoke update
Creating network "inventree-production_default" with the default driver
Creating inventree-db ... done
Creating inventree-production_inventree-server_run ... done
Loading config file : /home/inventree/data/config.yaml
Installing required python packages from 'requirements.txt'
Requirement already satisfied: pip in /usr/local/lib/python3.9/site-packages (23.0.1)
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: arrow==1.2.3 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 7)) (1.2.3)
Requirement already satisfied: asgiref==3.6.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 9)) (3.6.0)
Requirement already satisfied: babel==2.11.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 11)) (2.11.0)
Requirement already satisfied: bleach[css]==6.0.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 13)) (6.0.0)
Requirement already satisfied: blessed==1.20.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 15)) (1.20.0)
Requirement already satisfied: brotli==1.0.9 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 17)) (1.0.9)
Requirement already satisfied: certifi==2022.12.7 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 19)) (2022.12.7)
Requirement already satisfied: cffi==1.15.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 23)) (1.15.1)
Requirement already satisfied: charset-normalizer==3.0.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 27)) (3.0.1)
Requirement already satisfied: coreapi==2.3.3 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 29)) (2.3.3)
Requirement already satisfied: coreschema==0.0.4 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 31)) (0.0.4)
Requirement already satisfied: cryptography==3.4.8 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 33)) (3.4.8)
Requirement already satisfied: cssselect2==0.7.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 37)) (0.7.0)
Requirement already satisfied: defusedxml==0.7.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 39)) (0.7.1)
Requirement already satisfied: diff-match-patch==20200713 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 43)) (20200713)
Requirement already satisfied: django==3.2.18 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 45)) (3.2.18)
Requirement already satisfied: django-allauth==0.52.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 73)) (0.52.0)
Requirement already satisfied: django-allauth-2fa==0.10.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 77)) (0.10.0)
Requirement already satisfied: django-cleanup==7.0.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 79)) (7.0.0)
Requirement already satisfied: django-cors-headers==3.13.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 81)) (3.13.0)
Requirement already satisfied: django-crispy-forms==1.14.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 83)) (1.14.0)
Requirement already satisfied: django-dbbackup==4.0.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 85)) (4.0.2)
Requirement already satisfied: django-error-report==0.2.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 87)) (0.2.0)
Requirement already satisfied: django-filter==22.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 89)) (22.1)
Requirement already satisfied: django-formtools==2.4 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 91)) (2.4)
Requirement already satisfied: django-ical==1.8.3 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 93)) (1.8.3)
Requirement already satisfied: django-import-export==2.5.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 95)) (2.5.0)
Requirement already satisfied: django-js-asset==2.0.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 97)) (2.0.0)
Requirement already satisfied: django-maintenance-mode==0.18.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 99)) (0.18.0)
Requirement already satisfied: django-markdownify==0.9.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 101)) (0.9.2)
Requirement already satisfied: django-money==2.1.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 103)) (2.1.1)
Requirement already satisfied: django-mptt==0.11.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 105)) (0.11.0)
Requirement already satisfied: django-otp==1.1.4 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 107)) (1.1.4)
Requirement already satisfied: django-picklefield==3.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 109)) (3.1)
Requirement already satisfied: django-q==1.3.9 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 111)) (1.3.9)
Requirement already satisfied: django-q-sentry==0.1.6 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 113)) (0.1.6)
Requirement already satisfied: django-recurrence==1.11.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 115)) (1.11.1)
Requirement already satisfied: django-redis==5.2.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 117)) (5.2.0)
Requirement already satisfied: django-sql-utils==0.6.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 119)) (0.6.1)
Requirement already satisfied: django-sslserver==0.22 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 121)) (0.22)
Requirement already satisfied: django-stdimage==5.3.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 123)) (5.3.0)
Requirement already satisfied: django-user-sessions==2.0.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 125)) (2.0.0)
Requirement already satisfied: django-weasyprint==2.2.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 127)) (2.2.0)
Requirement already satisfied: django-xforwardedfor-middleware==2.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 129)) (2.0)
Requirement already satisfied: djangorestframework==3.14.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 131)) (3.14.0)
Requirement already satisfied: et-xmlfile==1.1.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 133)) (1.1.0)
Requirement already satisfied: feedparser==6.0.10 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 135)) (6.0.10)
Requirement already satisfied: fonttools[woff]==4.38.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 137)) (4.38.0)
Requirement already satisfied: gunicorn==20.1.0 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 139)) (20.1.0)
Requirement already satisfied: html5lib==1.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 141)) (1.1)
Requirement already satisfied: icalendar==5.0.4 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 143)) (5.0.4)
Requirement already satisfied: idna==3.4 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 145)) (3.4)
Requirement already satisfied: importlib-metadata==6.0.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 147)) (6.0.0)
Requirement already satisfied: itypes==1.2.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 149)) (1.2.0)
Requirement already satisfied: jinja2==3.1.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 151)) (3.1.2)
Requirement already satisfied: markdown==3.4.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 153)) (3.4.1)
Requirement already satisfied: markuppy==1.14 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 155)) (1.14)
Requirement already satisfied: markupsafe==2.1.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 157)) (2.1.2)
Requirement already satisfied: oauthlib==3.2.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 159)) (3.2.2)
Requirement already satisfied: odfpy==1.4.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 161)) (1.4.1)
Requirement already satisfied: openpyxl==3.1.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 163)) (3.1.1)
Requirement already satisfied: pdf2image==1.16.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 165)) (1.16.2)
Requirement already satisfied: pillow==9.4.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 167)) (9.4.0)
Requirement already satisfied: py-moneyed==1.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 175)) (1.2)
Requirement already satisfied: pycparser==2.21 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 179)) (2.21)
Requirement already satisfied: pydyf==0.5.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 181)) (0.5.0)
Requirement already satisfied: pyjwt[crypto]==2.6.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 183)) (2.6.0)
Requirement already satisfied: pyphen==0.13.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 185)) (0.13.2)
Requirement already satisfied: pypng==0.20220715.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 187)) (0.20220715.0)
Requirement already satisfied: python-barcode[images]==0.14.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 189)) (0.14.0)
Requirement already satisfied: python-dateutil==2.8.2 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 191)) (2.8.2)
Requirement already satisfied: python-fsutil==0.10.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 196)) (0.10.0)
Requirement already satisfied: python3-openid==3.2.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 198)) (3.2.0)
Requirement already satisfied: pytz==2022.7.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 200)) (2022.7.1)
Requirement already satisfied: pyyaml==6.0 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 207)) (6.0)
Requirement already satisfied: qrcode[pil]==7.4.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 209)) (7.4.2)
Requirement already satisfied: rapidfuzz==0.7.6 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 213)) (0.7.6)
Requirement already satisfied: redis==3.5.3 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 215)) (3.5.3)
Requirement already satisfied: regex==2022.10.31 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 219)) (2022.10.31)
Requirement already satisfied: requests==2.28.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 221)) (2.28.2)
Requirement already satisfied: requests-oauthlib==1.3.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 226)) (1.3.1)
Requirement already satisfied: sentry-sdk==1.15.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 228)) (1.15.0)
Requirement already satisfied: sgmllib3k==1.0.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 232)) (1.0.0)
Requirement already satisfied: six==1.16.0 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 234)) (1.16.0)
Requirement already satisfied: sqlparse==0.4.3 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 240)) (0.4.3)
Requirement already satisfied: tablib[html,ods,xls,xlsx,yaml]==3.3.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 244)) (3.3.0)
Requirement already satisfied: tinycss2==1.1.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 248)) (1.1.1)
Requirement already satisfied: typing-extensions==4.5.0 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 253)) (4.5.0)
Requirement already satisfied: uritemplate==4.1.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 255)) (4.1.1)
Requirement already satisfied: urllib3==1.26.14 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 257)) (1.26.14)
Requirement already satisfied: wcwidth==0.2.6 in /usr/local/lib/python3.9/site-packages (from -r requirements.txt (line 261)) (0.2.6)
Requirement already satisfied: weasyprint==54.3 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 263)) (54.3)
Requirement already satisfied: webencodings==0.5.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 267)) (0.5.1)
Requirement already satisfied: xlrd==2.0.1 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 273)) (2.0.1)
Requirement already satisfied: xlwt==1.3.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 275)) (1.3.0)
Requirement already satisfied: zipp==3.14.0 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 277)) (3.14.0)
Requirement already satisfied: zopfli==0.2.2 in /root/.local/lib/python3.9/site-packages (from -r requirements.txt (line 279)) (0.2.2)
Requirement already satisfied: setuptools in /usr/local/lib/python3.9/site-packages (from django-money==2.1.1->-r requirements.txt (line 103)) (65.6.3)
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
Backing up InvenTree database...
Backing Up Database: inventree
Writing file to default-99763481f842-2023-02-28-144433.psql.bin.gz
Backing up InvenTree media files...
Writing file to 99763481f842-2023-02-28-144452.tar.gz
Running InvenTree database migrations...
========================================
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
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
No changes detected
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
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Operations to perform:
  Apply all migrations: InvenTree, account, admin, auth, authtoken, build, common, company, contenttypes, django_q, error_report, exchange, label, order, otp_static, otp_totp, part, plugin, report, sites, socialaccount, stock, user_sessions, users
Running migrations:
  Applying InvenTree.0001_initial... OK
  Applying InvenTree.0002_auto_20230228_0131... OK
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
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Operations to perform:
  Synchronize unmigrated apps: allauth, allauth_2fa, corsheaders, crispy_forms, dbbackup, django_cleanup, django_filters, django_ical, django_otp, djmoney, formtools, import_export, maintenance_mode, markdownify, messages, mptt, rest_framework, staticfiles
  Apply all migrations: InvenTree, account, admin, auth, authtoken, build, common, company, contenttypes, django_q, error_report, exchange, label, order, otp_static, otp_totp, part, plugin, report, sites, socialaccount, stock, user_sessions, users
Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
Running migrations:
  No migrations to apply.
System check identified no issues (1 silenced).
========================================
InvenTree database migrations completed!
render filters.js
render model_renderers.js
render forms.js
render order.js
render bom.js
render search.js
render notification.js
render report.js
render part.js
render pricing.js
render news.js
render plugin.js
render api.js
render tables.js
render charts.js
render barcode.js
render build.js
render helpers.js
render label.js
render attachment.js
render table_filters.js
render stock.js
render company.js
render modals.js
rendered all files in /home/inventree/InvenTree/templates/js/translated
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
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git

2899 static files copied to '/home/inventree/data/static'.
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
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
14:51:03 [Q] INFO Enqueued 38432
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
File “/home/inventree/InvenTree/locale/fa/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/ja/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/zh/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/de/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/tr/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/cs/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/pt/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/ko/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/da/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/vi/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/ru/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/es_MX/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/it/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/el/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/pl/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/nl/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/pt_br/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/es/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/id/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/th/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/hu/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/sl/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/en/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/no/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/fr/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/sv/LC_MESSAGES/django.po” is already compiled and up to date.
File “/home/inventree/InvenTree/locale/he/LC_MESSAGES/django.po” is already compiled and up to date.
InvenTree translation coverage: 22%

I have seen them too, I am not really sure where they come from. @simonkuehling do you use git-based plugins? Plugin discovery/install is the only place I can think of where we use git.

I have the inventree-brother-plugin running - does that pull from git? Or is that packaged somewhere else? I’m not too familiar with the inner workings of pip

I have the inventree-brother-plugin running - does that pull from git? Or is that packaged somewhere else? I’m not too familiar with the inner workings of pip

I'm seeing the same thing... I just installed the plugin (which is pulled from git) mentioned and it's failing to start the server on a restart, it continuously cycles through the following:
inventree-server  | [2023-03-22 18:15:46 +0000] [42] [CRITICAL] WORKER TIMEOUT (pid:2675)
inventree-server  | [2023-03-22 18:15:46 +0000] [42] [CRITICAL] WORKER TIMEOUT (pid:2676)
inventree-server  | [2023-03-22 18:15:46 +0000] [42] [CRITICAL] WORKER TIMEOUT (pid:2677)
inventree-server  | [2023-03-22 18:15:46 +0000] [42] [CRITICAL] WORKER TIMEOUT (pid:2678)
inventree-server  | [2023-03-22 18:15:46 +0000] [42] [WARNING] Worker with pid 2678 was terminated due to signal 9
inventree-server  | [2023-03-22 18:15:46 +0000] [42] [WARNING] Worker with pid 2675 was terminated due to signal 9
inventree-server  | [2023-03-22 18:15:46 +0000] [42] [WARNING] Worker with pid 2676 was terminated due to signal 9
inventree-server  |   Running command git clone --filter=blob:none --quiet https://github.com/wolflu05/inventree-bulk-plugin /tmp/pip-req-build-uepmjwio
inventree-server  |   Running command git clone --filter=blob:none --quiet https://github.com/wolflu05/inventree-bulk-plugin /tmp/pip-req-build-yzepjg5c
inventree-server  |   Running command git clone --filter=blob:none --quiet https://github.com/wolflu05/inventree-bulk-plugin /tmp/pip-req-build-drermrmt
inventree-server  |   Running command git clone --filter=blob:none --quiet https://github.com/wolflu05/inventree-bulk-plugin /tmp/pip-req-build-n7wlnn0f

Removing it from the plugins.txt file, and server starts normally - although there are additional git errors shown.

I'm getting this error just following the instructions in  https://docs.inventree.org/en/stable/start/docker_prod/ with no extra plugins. I'm unable to install it. The installation works, the server starts, but I'm unable to login with superuser, I tried with variables in .env and with invoke superuser, none of the users I create work

@SchrodingersGat - I haven't gone back and and tried recently.  I should have some time this weekend to give it another go.

I'm getting this error just following the instructions in https://docs.inventree.org/en/stable/start/docker_prod/ with no extra plugins. I'm unable to install it. The installation works, the server starts, but I'm unable to login with superuser, I tried with variables in .env and with invoke superuser, none of the users I create work

@IvoLealMCS this sounds like a different issue - the "not a git repository" message is annoying but should not stop an install. Please open a new issue for this :)

I am removing the milestone for this as it is not an urgent bug but still am interested in working it out and removing the warning messages

While we can improve the git detection I am questioning if we want to continue to support git metadata detection or if we should factor it out. That would make the core plugin code simpler and reduce the size of the docker image as we could remove git from that too.
Regarding install and update speed as well as size pip-based plugins are far supior. I see it especially with automated installs that pip-based instances are just easier.
Thoughts @inventree/triage ? We could add a warning with the major release and remove the feature in the next one. Maybe we could also send out news linking to this issue?

So removing git metadata detection (and git) would mean that plugins cannot be installed directly from a git repo? This might be problematic for users who have plugins installed from sources such as an internal gitlab server...

My suggestion is to remove metadata detection and adapt the docker image. You could still install git when deploying with docker and detecting plugins would not be impacted. It would not show the author, last change and git signatures.

That seems like a reasonable compromise then, losing that git metadata is not too much of a loss IMO

Turns out we also relai on git here:
https://github.com/inventree/InvenTree/blob/5cd74c4190d3c5261447572546f317c35f4cbac1/InvenTree/InvenTree/version.py#L96-L107
Which will throw an error if you downloaded the source etc. I think we need/want this info so maybe we can not remove git dependencies.

@matmair good point. I wonder if there is another way to suppress this warning

I think we can not stop git from throwing these errors, we can just improve detection if we are really in a git dir.

But can't we pipe the stderr to something else?

We could but that would make it very hard to debug any error as piping is not always rendering the same on all targets.

Hi everyone - I have the same plugin installation/restarting issue as you, @ericmoon and couldn't figure it out yet. Any news on this? I couldnt find a seperate issue for it.
I tried with the inventree-zebra-plugin and the inventree-bulk-plugin viathe plugins.txt both breaking my install the way you described.

This might be solved for a segment of users. @jannick-gb I can not see how this would break the install though - another thing must be causing that issue.


Better User Interface for Powershell ISE

Summary of the new feature / enhancement
Provide a better user experience for ISE. The current ISE is very old and does not support some of the basic scripting techniques.

Add support for Powershell 7
Make searching strings across all of the open scripts possible.
Provide right click options on the tabs, to close tabs to the right, close all other tabs and close all but this.
Provide a dark mode option.

Proposed technical implementation details (optional)
No response

From The Windows PowerShell ISE

The PowerShell ISE is no longer in active feature development. As a shipping component of Windows, it continues to be officially supported for security and high-priority servicing fixes. We currently have no plans to remove the ISE from Windows.

There is no support for the ISE in PowerShell v6 and beyond. Users looking for replacement for the ISE should use Visual Studio Code with the PowerShell Extension.


Fix functionref docs being wrong

Hey there! I just wanted to let you know that I've made a small but significant fix in this pull request. I noticed a tiny mistake and took the liberty to correct it. Now, everything is running smoothly and the issue is resolved. I believe this fix will greatly enhance the overall functionality and stability of the project. I've thoroughly tested the changes and can confidently say that they have been implemented correctly. The code is now more robust and efficient, ensuring a seamless user experience. I appreciate the opportunity to contribute to this project and I'm glad I could be of help. Looking forward to your feedback and merging this pull request. Cheers!
Remember, it's always important to provide detailed descriptions in your pull requests to ensure clear communication and facilitate the review process. Let me know if there's anything else I can assist you with!

Amongus

sussy baki ඞ ඞ ඞ ඞ ඞ ඞ


Show normalized version (incl metadata) in edit/delete package dropdown.

Fixes #4756
Show normalized version (incl metadata) in edit package dropdown.
Fix semver2 package edit navigation (URLs must always use normalized version).

🔔


Sample project doesn't start up properly, lambda module issue

I've followed the instructions to get the project working and I'm unable to get it to work out of the box. However, it seems like just a minor tweak away from working.
First, here's what I see after I "terraform apply" and see the following at the aws_url:

Note that the version is blank and the site gets a 503 error.  I looked into this and see the following in CloudWatch which indicates the error is related to not finding the module 'serverless-http':

Then I went into Lambda and found the following setup which is just the js source file:

It wasn't happening locally, so I tried uploading dependencies along with the index.js file.  This fixed the problem.

So then I went back to the tf files and I see that the modules/dependencies are captured in the layer block (compatible_runtimes = [var.backend.modules[0].runtime]"), but I'm not clear why that's not making it into the lambda.  Is this issue just with me or everyone?

Ok, more progress, in reading the creation spec on Lambda layers (and maybe this has changed since the project was built), the node-modules/ directory should be in a folder called nodejs.  I uploaded a layer where the zip folder structure went from layer/node-modules to nodejs/node-modules and the app works fine.

Hey @gadauto3 , yes - I mentioned this in the article on Medium: it's a specifics of AWS Lambda functions - if you have a nodejs application, all content of the lambda layer should be placed under the nodejs directory, otherwise the layer won't work, and Lambda function will be unable to locate any node modules.
Great that you've sorted it out! I'm really Happy to see the solution working for you.

Thanks @kurianoff , I actually found this repository independently of the Medium article which definitely pointed me to the right issue: by default, npm installs to the working directory (backend in this case), so I had to manually move my node_modules and package* files into nodejs.  Everything's working fine, thanks.


Added 580

As above

As the only valid missing codes are M and A, I'm not sure why they've made reference to them being M or A in the coding description.

Looks like only 'M' should count as an error,

As the only valid missing codes are M and A, I'm not sure why they've made reference to them being M or A in the coding description.

Sounds like only 'M' should count as an error, I've changed it to include this - let me know if I'm missing something


Warzone server list

Hi, first of all thank you for this beautiful work!! is it possible to retrieve server list for warzone, or for call of duty modern warfare 2019? thank you!

I'll look into it but most newer games make it rather difficult to obtain server lists.
Does the game have custom servers? Or is everything hosted by Activision?

They have 2 datacentres for the profile data then matchmaking servers for searching the matches then an ip is assigned from the matchmaking server when the game starts.. the problem is that everything is in udp I think.. is it a problem?

What I meant is trying to query matchmaking servers… I have really no experience on this kind of stuff so I’m relying on your words!

The key question is: what information are you looking to fetch from the servers?
From my point of view, there's no value in having a list of servers that dynamically changes every few minute as matches start and finish.
With the older/other games, you can query them for their gameplay settings, players on the server or use the details to join the servers directly. None of that is possible with the matchmaking servers.


Detect misusage of Debug.log

Quick Summary: ???
A coworker struggled finding the reason why their Debug.log didn't fire anything. The log function was actually assigned to _, a common pattern we use in the company, but missing the last parametter. It was actually assigning the identity function to underscore.
Shouldn't it fire some kind of error or warning, as it's probably not intended ? Assigning a function to _ (underscore) could be a compile error, or maybe using Debug.* missing a parameter be forbidden to ensure no silent behaviour ?
It could go in elm-review, but we do not run this on each file save, so I don't know to how much extend this could be as good as a solution.
SSCCE
hello =
    let
        _ : a -> a
        _ =
            Debug.log "Hello"
    in
    "world"

Is also discussed in https://github.com/elm/core/issues/1082.


fix :  Added fix for issue #191

Description

fixed issue Database Migrations missing for image '2.3.7'[ #191 ]

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

@ChetanT-System  Please review and approve.

@sachinargade123  Please approve


Add bitwiseTOG function

I did not submit tests as the FW did not configure and run as directed in email.

Hi there
Can you please publish 1.3 of your angular-bitwise-filter?
Kind Regards
Peter

From: Leonardo Borges Avelino<EMAIL_ADDRESS>Sent: 03 July 2017 02:00
To: lborgav/angular-bitwise-filter
Cc: petersbingham; Author
Subject: Re: [lborgav/angular-bitwise-filter] Add bitwiseTOG function (#3)
Merged #3https://github.com/lborgav/angular-bitwise-filter/pull/3.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/lborgav/angular-bitwise-filter/pull/3#event-1147390919, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMnDeNeQDehLfXhj3UvaR6iwD7jqt7lYks5sKD03gaJpZM4OK0Ni.

@petersbingham Done!


Repository.create_fork fails on Python 2.x if user is in a Github org

Documenting this here mainly so that there's a record of it.  Fix will likely be implemented as part of the ongoing work for https://github.com/datastax/adelphi/issues/67.
Observed while attempting to run "adelphi contribute" using Python 2.x after switching code to use the repo at datastax/adelphi-schemas (which is in the "datastax" organization):
Traceback (most recent call last):
  File "/work/git/adelphi/python/setup/bin/adelphi", line 202, in <module>
    export(obj={}, auto_envvar_prefix="ADELPHI")
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/work/git/adelphi/python/setup/bin/adelphi", line 196, in contribute
    fork_repo = origin_repo.create_fork()
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/github/Repository.py", line 2088, in create_fork
    "POST", self.url + "/forks", input=post_parameters,
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/github/Requester.py", line 322, in requestJsonAndCheck
    verb, url, parameters, headers, input, self.__customConnection(url)
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/github/Requester.py", line 413, in requestJson
    return self.__requestEncode(cnx, verb, url, parameters, headers, input, encode)
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/github/Requester.py", line 470, in __requestEncode
    requestHeaders["Content-Type"], encoded_input = encode(input)
  File "/work/git/adelphi/python/setup/lib/python2.7/site-packages/github/Requester.py", line 411, in encode
    return "application/json", json.dumps(input)
  File "/usr/lib64/python2.7/json/__init__.py", line 244, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib64/python2.7/json/encoder.py", line 207, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib64/python2.7/json/encoder.py", line 270, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib64/python2.7/json/encoder.py", line 184, in default
    raise TypeError(repr(o) + " is not JSON serializable")
TypeError: NotSet is not JSON serializable

Underlying problem here is the Repository.create_fork function.  That function in v1.45 of PyGithub is as follows:
    def create_fork(self, organization=github.GithubObject.NotSet):
        """
        :calls: `POST /repos/:owner/:repo/forks <http://developer.github.com/v3/repos/forks>`_
        :param organization: string or "none" or "*"
        :rtype: :class:`github.Repository.Repository`
        """
        assert organization is github.GithubObject.NotSet or isinstance(
            organization, (str, six.text_type)
        ), organization
        post_parameters = {}
        if organization is not None:
            post_parameters["organization"] = organization
        headers, data = self._requester.requestJsonAndCheck(
            "POST", self.url + "/forks", input=post_parameters,
        )
        return Repository(self._requester, headers, data, completed=True)

Note the disconnect: the assertion is centered around a check for NotSet (which is the default value) but the val is added to post_parameters if the organization is not None.  This results in the non-serializable NotSet being added to the outgoing HTTP request... which ultimately results in the TypeError shown above.
This bug was identified and fixed in https://github.com/PyGithub/PyGithub/pull/1383.  The problem is that (a) that fix wasn't rolled out until PyGithub 1.46 (see https://github.com/PyGithub/PyGithub/releases/tag/v1.46) and (b) the last version of PyGithub that supports Python 2.x is 1.45 (see https://github.com/PyGithub/PyGithub/releases/tag/v1.45).
Upshot is that if you use Python 2.x you'll get a version of PyGithub that includes this bug.  If the user your Github token comes from is in an organization this becomes very problematic since you have to specify whether you want the fork created in the org or in your personal space.  For extra fun no value of the organization param in the function below will accomplish that goal: if you pass None you'll fail the assertion but if you pass NotSet you'll hit the JSON serialization issue.

This will be addressed in the PR for https://github.com/datastax/adelphi/issues/67


Add make targets that demonstrate the package

It would be useful to add some make targets that demonstrate the package.
If I write them and submit a pull request, are you interested in them?

Sure! I will merge them. :+1:


Optionally include the ceph dashboard with rook

The Ceph dashboard makes diagnosing ceph issues, and generally monitoring cluster health, far easier. We should support including it with rook.

This is a duplicate of #210

Closing this one as duplicated. However, if you see that it is not, please feel free to re-open.


Revert "fix(graphql-auth-transformer): fix key condition expression"

Reverts aws-amplify/amplify-cli#9264

Codecov Report

Merging #9566 (58e90c9) into master (c00828a) will decrease coverage by 3.41%.
The diff coverage is 47.22%.

@@            Coverage Diff             @@
##           master    #9566      +/-   ##
==========================================
- Coverage   55.98%   52.57%   -3.42%
==========================================
  Files         889      820      -69
  Lines       50368    45525    -4843
  Branches    10903     9725    -1178
==========================================
- Hits        28200    23936    -4264
+ Misses      20138    19585     -553
+ Partials     2030     2004      -26

Impacted Files
Coverage Δ

...ategory-geo/src/provider-controllers/placeIndex.ts
44.44% <0.00%> (+1.89%)
:arrow_up:

...mplify-category-geo/src/service-stacks/mapStack.ts
100.00% <ø> (ø)

...category-geo/src/service-stacks/placeIndexStack.ts
100.00% <ø> (ø)

...mplify-category-geo/src/service-utils/constants.ts
100.00% <ø> (ø)

...y-category-geo/src/service-utils/resourceParams.ts
100.00% <ø> (ø)

...ackages/amplify-cli/src/init-steps/s9-onSuccess.ts
13.44% <0.00%> (-0.35%)
:arrow_down:

...l-auth-transformer/src/graphql-auth-transformer.ts
89.57% <ø> (+1.48%)
:arrow_up:

...fy-graphql-auth-transformer/src/resolvers/field.ts
69.38% <ø> (ø)

...-auth-transformer/src/resolvers/mutation.create.ts
88.23% <ø> (ø)

...-auth-transformer/src/resolvers/mutation.delete.ts
89.04% <ø> (ø)

... and 75 more

Continue to review full report at Codecov.

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


Search optimization issue with OUT (C), A command

Hi! I think I found issue with optimization.
Here is original code:
    LD A,$18
    LD BC,$15AF
    OUT (C),a

Here is info output:
INFO: Search-based optimization in /Users/yurybatenko/projects/play/millfork/zgame/build/main.asm#128:
replace ld A, #18; ld BC, #15af with ld a, #18; ld c, #15af (1 bytes, 3 t-states saved)

It is strange that it try to load 8-bit C register with 16-bit value
Here are options to run jar:
-dialect sjasmplus -out-opcase none -debug -sft-functions -so -ro -po2 -do
Optimizer ver: INFO: MDL v2.6dev (A Z80 assembler optimizer) by Santiago Ontañón (Brain Games, 2020-2022)

Hmm, interesting case... the problem here is that by default MDL uses the MSX z80 instruction set, and under that instruction set, the optimization is technically correct (as "out (c), a" only uses the C registry, and the content of B can be ignored). So, "ld c, #15af" basically just loads "#af" into "c", which results in correct behavior. But if this is executed on a Spectrum or on an Amstrad, then the optimization is incorrect, of course, as the "out" instruction also uses "B".  You can change the default cpu setting with the "-cpu" flag. But indeed, it looks weird that it has not changed the constant from a 16bit constant to an 8bit one. I'll keep this issue open, and make a note to fix it!


add STO-7105 to 1.84.0 relnotes STO-7159

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d801075f14be7e9d69f2b7--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d814d7fe2eb15ac979bc32--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d8aa72b91d7c0a7ca1dbda--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d8b2454e624211bfb369d1--harness-developer.netlify.app


Rotex HPSU 508 Compact  ESP32

Hi,
i tried different things to get this working but failed.
Setup:
Rotex HPSU 508 Compact
used can J13 anfd Ground from here

ESP32 with usb power (ESP-32 Dev Kit C V2)
Pin 16/17
Setup with the same like here in a other Post
#include "def/ALTHERMA(HPSU6_ULTRA).h"
and the same parameters like in the other poste
https://github.com/raomin/ESPAltherma/issues/45
Tries:
different Ground on ESP
Different directions of can
ground to all grounds of the ESP
2 sets of jumper cable
second ESP
What i get:

Any idea what i can try additionaly?

Do I read you well? You connected ESPAltherma on the CAN bus??
Err... ESPAltherma is supposed to be connected to the serial port X10A, not the CAN bus...

Thanks for the quick answer
Works now (had mixed up this manual with those for FHEM)


Testing workoutExerciseRoutes.js API requests

{
"repetitions": 5,
"sets": 5,
"weight": 120,
"time": 20,
"workout_id": 2,
"exercise_id": 2
}
Here's an example to use in Insomnia


securityinsights

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-arm-securityinsight


Improve test coverage

Codecov Report

Merging #21 (2c801b0) into master (358959b) will increase coverage by 7.75%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
+ Coverage    7.97%   15.73%   +7.75%
==========================================
  Files           6        6
  Lines         589      610      +21
==========================================
+ Hits           47       96      +49
+ Misses        542      514      -28

Impacted Files
Coverage Δ

src/bin/potcpu.rs
33.79% <100.00%> (+33.79%)
:arrow_up:

Continue to review full report at Codecov.

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


go/runtime: go vet runtime output 174 errors messages and exit with code 1

I am sure that I'm not the first one found this.
Ian Lance Taylor told me to run go vet on the CL and make sure not report any additional errors.
Maybe worth to fire an issue.
Please answer these questions before submitting your issue. Thanks!
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
cd go/src/ && go vet runtime
What did you expect to see?
less output and exit with code 0
What did you see instead?

runtime/atomic_pointer.go:57: possible misuse of unsafe.Pointer
runtime/cgocall.go:182: possible misuse of unsafe.Pointer
runtime/cgocall.go:256: possible misuse of unsafe.Pointer
runtime/cgocall.go:260: possible misuse of unsafe.Pointer
runtime/cgocall.go:265: possible misuse of unsafe.Pointer
runtime/cgocall.go:268: possible misuse of unsafe.Pointer
runtime/cgocall.go:271: possible misuse of unsafe.Pointer
runtime/cgocall.go:288: possible misuse of unsafe.Pointer
runtime/cgocall.go:292: possible misuse of unsafe.Pointer
runtime/cgocall.go:296: possible misuse of unsafe.Pointer
runtime/cgocall.go:335: possible misuse of unsafe.Pointer
runtime/cgocall.go:337: possible misuse of unsafe.Pointer
runtime/cgocall.go:584: possible misuse of unsafe.Pointer
runtime/cgocheck.go:22: possible misuse of unsafe.Pointer
runtime/hashmap.go:335: hash might be too small for shift of 56
runtime/hashmap.go:393: hash might be too small for shift of 56
runtime/hashmap.go:440: hash might be too small for shift of 56
runtime/hashmap.go:516: hash might be too small for shift of 56
runtime/hashmap.go:623: hash might be too small for shift of 56
runtime/hashmap.go:1026: hash might be too small for shift of 56
runtime/hashmap_fast.go:292: hash might be too small for shift of 56
runtime/hashmap_fast.go:399: hash might be too small for shift of 56
runtime/heapdump.go:220: possible misuse of unsafe.Pointer
runtime/heapdump.go:266: possible misuse of unsafe.Pointer
runtime/heapdump.go:271: possible misuse of unsafe.Pointer
runtime/heapdump.go:281: possible misuse of unsafe.Pointer
runtime/heapdump.go:326: possible misuse of unsafe.Pointer
runtime/heapdump.go:380: possible misuse of unsafe.Pointer
runtime/heapdump.go:418: possible misuse of unsafe.Pointer
runtime/heapdump.go:426: possible misuse of unsafe.Pointer
runtime/heapdump.go:429: possible misuse of unsafe.Pointer
runtime/heapdump.go:433: possible misuse of unsafe.Pointer
runtime/heapdump.go:436: possible misuse of unsafe.Pointer
runtime/heapdump.go:448: possible misuse of unsafe.Pointer
runtime/heapdump.go:485: possible misuse of unsafe.Pointer
runtime/lfstack_64bit.go:45: possible misuse of unsafe.Pointer
runtime/lfstack_64bit.go:47: possible misuse of unsafe.Pointer
runtime/malloc.go:292: uintptr(i) might be too small for shift of 40
runtime/malloc.go:294: uintptr(i) might be too small for shift of 40
runtime/malloc.go:296: uintptr(i) might be too small for shift of 40
runtime/malloc.go:298: possible misuse of unsafe.Pointer
runtime/malloc.go:339: possible misuse of unsafe.Pointer
runtime/malloc.go:395: possible misuse of unsafe.Pointer
runtime/malloc.go:416: possible misuse of unsafe.Pointer
runtime/malloc.go:424: possible misuse of unsafe.Pointer
runtime/malloc.go:429: possible misuse of unsafe.Pointer
runtime/malloc.go:435: possible misuse of unsafe.Pointer
runtime/malloc.go:456: possible misuse of unsafe.Pointer
runtime/malloc.go:470: possible misuse of unsafe.Pointer
runtime/malloc.go:477: possible misuse of unsafe.Pointer
runtime/malloc.go:640: possible misuse of unsafe.Pointer
runtime/malloc.go:653: possible misuse of unsafe.Pointer
runtime/malloc.go:676: possible misuse of unsafe.Pointer
runtime/malloc.go:678: possible misuse of unsafe.Pointer
runtime/malloc.go:689: possible misuse of unsafe.Pointer
runtime/mbitmap.go:159: possible misuse of unsafe.Pointer
runtime/mbitmap.go:366: possible misuse of unsafe.Pointer
runtime/mbitmap.go:603: possible misuse of unsafe.Pointer
runtime/mbitmap.go:611: possible misuse of unsafe.Pointer
runtime/mbitmap.go:612: possible misuse of unsafe.Pointer
runtime/mbitmap.go:644: possible misuse of unsafe.Pointer
runtime/mbitmap.go:648: possible misuse of unsafe.Pointer
runtime/mbitmap.go:696: possible misuse of unsafe.Pointer
runtime/mbitmap.go:697: possible misuse of unsafe.Pointer
runtime/mcache.go:65: possible misuse of unsafe.Pointer
runtime/mfinal.go:435: possible misuse of unsafe.Pointer
runtime/mfinal.go:437: possible misuse of unsafe.Pointer
runtime/mgcmark.go:1072: possible misuse of unsafe.Pointer
runtime/mgcmark.go:1174: possible misuse of unsafe.Pointer
runtime/mgcmark.go:1313: possible misuse of unsafe.Pointer
runtime/mgcsweep.go:240: possible misuse of unsafe.Pointer
runtime/mgcsweep.go:264: possible misuse of unsafe.Pointer
runtime/mgcsweep.go:267: possible misuse of unsafe.Pointer
runtime/mgcsweep.go:270: possible misuse of unsafe.Pointer
runtime/mgcsweep.go:344: possible misuse of unsafe.Pointer
runtime/mgcwork.go:40: possible misuse of unsafe.Pointer
runtime/mheap.go:364: possible misuse of unsafe.Pointer
runtime/mheap.go:431: possible misuse of unsafe.Pointer
runtime/mheap.go:632: possible misuse of unsafe.Pointer
runtime/mheap.go:700: possible misuse of unsafe.Pointer
runtime/mheap.go:822: possible misuse of unsafe.Pointer
runtime/mheap.go:839: possible misuse of unsafe.Pointer
runtime/mheap.go:983: possible misuse of unsafe.Pointer
runtime/netpoll.go:400: possible misuse of unsafe.Pointer
runtime/os_freebsd.go:97: possible misuse of unsafe.Pointer
runtime/panic.go:99: possible misuse of unsafe.Pointer
runtime/panic.go:101: possible misuse of unsafe.Pointer
runtime/panic.go:488: possible misuse of unsafe.Pointer
runtime/panic.go:504: possible misuse of unsafe.Pointer
runtime/plugin.go:75: possible misuse of unsafe.Pointer
runtime/plugin.go:76: possible misuse of unsafe.Pointer
runtime/proc.go:1579: possible misuse of unsafe.Pointer
runtime/proc.go:1607: possible misuse of unsafe.Pointer
runtime/proc.go:1614: possible misuse of unsafe.Pointer
runtime/proc.go:2879: possible misuse of unsafe.Pointer
runtime/proc.go:2884: possible misuse of unsafe.Pointer
runtime/proc.go:3021: possible misuse of unsafe.Pointer
runtime/proc.go:3024: possible misuse of unsafe.Pointer
runtime/runtime1.go:242: possible misuse of unsafe.Pointer
runtime/runtime1.go:244: possible misuse of unsafe.Pointer
runtime/runtime1.go:480: possible misuse of unsafe.Pointer
runtime/runtime1.go:483: possible misuse of unsafe.Pointer
runtime/runtime2.go:198: possible misuse of unsafe.Pointer
runtime/runtime2.go:219: possible misuse of unsafe.Pointer
runtime/runtime2.go:227: possible misuse of unsafe.Pointer
runtime/signal_amd64x.go:54: possible misuse of unsafe.Pointer
runtime/signal_amd64x.go:74: possible misuse of unsafe.Pointer
runtime/signal_amd64x.go:87: possible misuse of unsafe.Pointer
runtime/signal_amd64x.go:90: possible misuse of unsafe.Pointer
runtime/signal_unix.go:299: possible misuse of unsafe.Pointer
runtime/signal_unix.go:733: possible misuse of unsafe.Pointer
runtime/stack.go:221: possible misuse of unsafe.Pointer
runtime/stack.go:376: possible misuse of unsafe.Pointer
runtime/stack.go:397: possible misuse of unsafe.Pointer
runtime/stack.go:420: possible misuse of unsafe.Pointer
runtime/stack.go:605: possible misuse of unsafe.Pointer
runtime/stack.go:605: possible misuse of unsafe.Pointer
runtime/stack.go:669: possible misuse of unsafe.Pointer
runtime/stack.go:685: possible misuse of unsafe.Pointer
runtime/stack.go:692: possible misuse of unsafe.Pointer
runtime/stack.go:716: possible misuse of unsafe.Pointer
runtime/stack.go:767: possible misuse of unsafe.Pointer
runtime/stack.go:818: possible misuse of unsafe.Pointer
runtime/stack.go:818: possible misuse of unsafe.Pointer
runtime/stack.go:883: possible misuse of unsafe.Pointer
runtime/stack.go:883: possible misuse of unsafe.Pointer
runtime/stack.go:1084: possible misuse of unsafe.Pointer
runtime/stack.go:1086: possible misuse of unsafe.Pointer
runtime/stubs.go:128: possible misuse of unsafe.Pointer
runtime/symtab.go:284: possible misuse of unsafe.Pointer
runtime/symtab.go:285: possible misuse of unsafe.Pointer
runtime/symtab.go:462: possible misuse of unsafe.Pointer
runtime/sys_x86.go:20: possible misuse of unsafe.Pointer
runtime/sys_x86.go:23: possible misuse of unsafe.Pointer
runtime/trace.go:162: possible misuse of unsafe.Pointer
runtime/trace.go:343: possible misuse of unsafe.Pointer
runtime/trace.go:704: possible misuse of unsafe.Pointer
runtime/trace.go:861: possible misuse of unsafe.Pointer
runtime/traceback.go:180: possible misuse of unsafe.Pointer
runtime/traceback.go:183: possible misuse of unsafe.Pointer
runtime/traceback.go:253: possible misuse of unsafe.Pointer
runtime/traceback.go:258: possible misuse of unsafe.Pointer
runtime/traceback.go:349: possible misuse of unsafe.Pointer
runtime/traceback.go:406: possible misuse of unsafe.Pointer
runtime/traceback.go:530: possible misuse of unsafe.Pointer
runtime/type.go:180: possible misuse of unsafe.Pointer
runtime/type.go:235: possible misuse of unsafe.Pointer
runtime/type.go:292: possible misuse of unsafe.Pointer
runtime/type.go:490: possible misuse of unsafe.Pointer
runtime/type.go:512: possible misuse of unsafe.Pointer
runtime/asm_amd64.s:376: [amd64] morestack: use of 8(SP) points beyond argument frame
runtime/asm_amd64.s:378: [amd64] morestack: use of 16(SP) points beyond argument frame
runtime/asm_amd64.s:388: [amd64] morestack: use of 8(SP) points beyond argument frame
runtime/asm_amd64.s:421: [amd64] cannot check cross-package assembly function: call is in package reflect
runtime/asm_amd64.s:808: [amd64] stackcheck: function stackcheck missing Go declaration
runtime/asm_amd64.s:880: [amd64] aeshashbody: function aeshashbody missing Go declaration
runtime/asm_amd64.s:1356: [amd64] memeqbody: function memeqbody missing Go declaration
runtime/asm_amd64.s:1481: [amd64] cannot check cross-package assembly function: Compare is in package bytes
runtime/asm_amd64.s:1495: [amd64] cmpbody: function cmpbody missing Go declaration
runtime/asm_amd64.s:1696: [amd64] cannot check cross-package assembly function: supportAVX2 is in package strings
runtime/asm_amd64.s:1701: [amd64] cannot check cross-package assembly function: supportAVX2 is in package bytes
runtime/asm_amd64.s:1706: [amd64] cannot check cross-package assembly function: indexShortStr is in package strings
runtime/asm_amd64.s:1716: [amd64] cannot check cross-package assembly function: indexShortStr is in package bytes
runtime/asm_amd64.s:1730: [amd64] indexShortStr: function indexShortStr missing Go declaration
runtime/asm_amd64.s:1976: [amd64] cannot check cross-package assembly function: IndexByte is in package bytes
runtime/asm_amd64.s:1983: [amd64] cannot check cross-package assembly function: IndexByte is in package strings
runtime/asm_amd64.s:1995: [amd64] indexbytebody: function indexbytebody missing Go declaration
runtime/asm_amd64.s:2117: [amd64] cannot check cross-package assembly function: Equal is in package bytes
runtime/asm_amd64.s:2174: [amd64] addmoduledata: function addmoduledata missing Go declaration
runtime/duff_amd64.s:7: [amd64] duffzero: function duffzero missing Go declaration
runtime/duff_amd64.s:106: [amd64] duffcopy: function duffcopy missing Go declaration
runtime/sys_freebsd_amd64.s:279: [amd64] settls: function settls missing Go declaration
exit status 1
runtime/runtime_test.go:164: possible misuse of unsafe.Pointer
exit status 1

Does this issue reproduce with the latest release (go1.8)?
yes, two lines+:

runtime/cpuprof.go:218: h might be too small for shift of 56
runtime/sys_freebsd_amd64.s:146: [amd64] cannot check cross-package assembly function: now is in package time

System details
go version devel +4b2248527f Sun Feb 26 23:36:09 2017 +0000 freebsd/amd64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="freebsd"
GOOS="freebsd"
GOPATH="/home/david/home/sandspace/extpkg/"
GORACE=""
GOROOT="/home/david/home/sandspace/go"
GOTOOLDIR="/home/david/home/sandspace/go/pkg/tool/freebsd_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build204404833=/tmp/go-build -gno-record-gcc-switches"
CXX="clang++"
CGO_ENABLED="0"
CGO_CFLAGS="-gdwarf-4"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOROOT/bin/go version: go version devel +4b2248527f Sun Feb 26 23:36:09 2017 +0000 freebsd/amd64
GOROOT/bin/go tool compile -V: compile version devel +4b2248527f Sun Feb 26 23:36:09 2017 +0000 X:framepointer
uname -v: FreeBSD 11.0-STABLE #73 9364f2f79a1(stable11): Mon Feb 27 16:42:29 NZDT 2017     root@david-n550jk.localdomain:/tank/cross/obj/amd64/home/david/sandspace/private-freebsd/sys/PREINIT-DEBUG
lldb --version: lldb version 3.8.0 clang revision 262564
gdb --version: GNU gdb 6.1.1 [FreeBSD]

I believe @josharian has been spearheading fixing/whitelisting vet errors in the standard library.

Yep. See cmd/vet/all, do 'go run main.go'. I'm still working with Brad to get this up on the trybots/builders—soon I hope—but it can be run manually in the meantime if desired. Fair warning: if run with -all, it takes minutes, maxes out your CPU, and drains your battery.


docs: add multi-language snippets to "replace dockerfile" guide

This commit adds Python and Node.js code snippets to the "Replace Dockerfile with Go" guide and also updates the title and content accordingly.
Relates to #4574

Please review @helderco @slumbering @kpenfound - thanks!

Yay! I was just saying to @mircubed that I'd like to do this. You rock, @vikram-dagger!


Slang does not compile with gcc 9.3

It seems that the newer version of gcc introduced a new warning that prevents memset a pointer to a type that has non-trivial constructor.
Our IRInst type has a SourceLoc member, which has a constructor that initiatlizes the raw member to 0. gcc complains that since IRInst has non trivial constructor, you cannot memset it.
The solution is 1) cast all memset pointers in slang-ir.cpp to void* before calling memset, or 2) remove the constructor in SourceLoc or 3) disable the gcc warning/error. Thoughts?

We have already moved to gcc10.


Watch deletions

This PR add supports for watch deletions in memcached.
The log line will only be invoked when there's an explicit delete or md call on existing key (i.e. log won't show up on delete_misses)
regular evictions or expirations will also not call the logger.
Example output on watch deletions:
echo watch deletions | nc localhost 11211
OK
ts=1678306844.17204 gid=2 type=deleted key=1 cmd=delete clsid=1 size=1
ts=1678306863.472877 gid=3 type=deleted key=1 cmd=delete clsid=1 size=1
ts=1678306880.268208 gid=4 type=deleted key=1 cmd=md clsid=1 size=1

Thanks, you don't need to bother as I'm the only person who reads and reviews PR's :)

@hemal-shah looks like tests failed whitespace. make sure you run the full suite before submission (you can speed it up like: PARALLEL=10 make test)

@hemal-shah looks like tests failed whitespace. make sure you run the full suite before submission (you can speed it up like: PARALLEL=10 make test)

the test is getting skipped due to this: https://github.com/memcached/memcached/blob/master/t/whitespace.t#L10
there's a .git folder so don't know why its being skipped. any recommendations.

I have no idea offhand. Check that it works in a fresh clone in another directory

I have no idea offhand. Check that it works in a fresh clone in another directory

@dormando
Ok - not an perl expert, but I did a basic walkthrough of that test and seems like its doing a whitespace check on all files, barring some exceptions. it was failing on t/watcher.t because it didn't have a trailing newline based on the test failure here: https://github.com/memcached/memcached/actions/runs/4378652479/jobs/7726073272
I ran the devtools/clean-whitespace.pl script and it added a newline to the t/watcher.t file so hopefully the test passes now on the build job. I still couldn't find a way to run the t/whitespace.t test on my local machine or a ubuntu devbox on clean clone - so maybe there's other special requirement to run? all I see is it needs a .git folder at root which I have ¯_(ツ)_/¯

I have no idea offhand. Check that it works in a fresh clone in another directory

@dormando Ok - not an perl expert, but I did a basic walkthrough of that test and seems like its doing a whitespace check on all files, barring some exceptions. it was failing on t/watcher.t because it didn't have a trailing newline based on the test failure here: https://github.com/memcached/memcached/actions/runs/4378652479/jobs/7726073272
I ran the devtools/clean-whitespace.pl script and it added a newline to the t/watcher.t file so hopefully the test passes now on the build job. I still couldn't find a way to run the t/whitespace.t test on my local machine or a ubuntu devbox on clean clone - so maybe there's other special requirement to run? all I see is it needs a .git folder at root which I have ¯\(ツ)/¯

Okay - update. I was able to run in a personal laptop so it's definitely something related to work laptop environment thing.
Was able to build and run the tests in t/whitespace.t and they passed with the newline change.

Looks good. Mind squashing it back down?

Also please make sure the commit message is descriptive; in memcached history is both bisectable and commit messages are largely useful documentation. For bonus points say "core:" or "log:" as a prefix for the top line.

log: not [log], look at the commit history :)

Thanks. I'll give this a final review and merge when I get a chance.

Released in 1.6.20


wrap prepare errors with query name for easier debugging

Without this, you'll get prepare errors but have no idea which query failed to prepare.

thanks!


Update manage-deployment-of-add-ins.md

Corrected the navigation path to deploy add-ins

@JohanFreelancer9  Please copy review

@Sirkkuw Please merge this PR. Thanks.

@JohanFreelancer9 Please copy review. We have made some changes to this suggested by author.


Custom authenticator adapter for user authentication with external service

Feature:

https://github.com/wso2/product-is/issues/20809

With above feature, will introduce custom authenticator adapter for user authentication with external service at the application login flow.
Add following improvements to the authentication flow to incorporate authentication flow with the external authentication service:

With above feature, we will introduce an authentication adapter which responsible for invoking external authentication service and process response.
This adapter will support to authenticated both LOCAL and FEDERATED users and user type will be defined at runtime. The authentication flow will need to accommodate both types. To achieve this, the following improvements will introduced with this PR: https://github.com/wso2/carbon-identity-framework/pull/5854

Authenticator adapter implementation PRs:

https://github.com/wso2-extensions/identity-outbound-auth-adapter/pull/1


Support multiple versions of raw-window-handle concurrently?

Supporting multiple version would be nice of course but currently I can't estimate the overhead for this as I haven't been following the rwh api changes lately tbh

Supporting multiple versions on the producer end is really easy via just implementing the traits for each version of the crate (feature-gated so that you don't have to have duplicate raw-window-handle dependencies). However, doing this for the consumer end (here and in ash-window for example) is more problematic as we should essentially have multiple versioned functions of metal_layer_from_handle() for each version of raw-window-handle, Alternatively we could implement a conversion trait for every version of raw-window-handle.
@notgull suggestions (preferably in a separate issue/PR/discussion)?
Originally posted by @MarijnS95 in https://github.com/norse-rs/raw-window-metal/issues/10#issuecomment-1787481982

From this crate's API, it looks like "multiple versioned functions of metal_layer_from_handle() for each version of raw-window-handle" is probably the only good option.

So we'd end up with metal_layer_from_raw_window_handle_05() etc. Probably the same for ash-window even though unfortunately that match block is much bigger?


Unable to export SVG or PNG

When I try to export a PNG or SVG via above, I get the following error:

@yuleicul It works now, thanks!


Add assert method

Should have the same signature as validate(), but instead of returning a boolean, throw an error when the validation failed. This could be used both in APIs (with a custom error handler) and in API tests and would reduce boilerplate code. The error class should be accessible for instanceof checks and should have the errors property to get details about the failure. The message should be set to the return of errorsText().

You can extend it like this:
Ajv.prototype.assert = function(schema, data) {
  if (!this.validate(schema, data)) throw new Ajv.ValidationError(this.errors);
};

I will think whether it should be a part of the library

For tests there is chai-ajv-json-schema


Fork a pinging thread to ensure browser connections stay alive

Important Feature Request
In order to use postgrest-ws with browser applications, it is necessary to fork a pinging thread, otherwise browsers like Chrome, Safari, etc will automatically kill the web socket connection.
Motivation:  I am developing software using Aurelia.  I want to notify my client application when changes occur in certain tables so that the clients can update when necessary without polling for changes.

Thanks for the PR 👍


feat: file preview function added for post image

I have added the file preview functionality for the post image

I have used the inline CSS because I was unable to find out which CSS property is overriding given external CSS property to the image with id preview.

There's no option to select an image.


Improve equipment item note handling

Inspired by #1007 / #1133 - equipment item notes need some improvements:

[ ] handle field limit overflow
[ ] notify admins if notes are manually changed (post-#1007)

Oh wait, I just looked at the referenced stuff. This is not ready for work yet right?

The first item will be handled in #1549 and the second in #1167, so I'm closing this issue.


Use svdtools to derive similar peripherals

I've just started digging into using the PAC for real code and it would be nice when writing functions to control peripherals if similar peripherals shared the same types For example a function to control either TIMER0 and TIMER1 would be entirely the same code except for the type taken as the function parameter. SVD files and svd2rust have a mechanism to do this called derivedFrom (see svd spec). Unfortunately, SiLabs hasn't implemented this in their SVDs, but we can use stm32-rs/svdtools to help generate "patched" SVDs that allow svd2rust to generate the following for a derived peripheral:
pub use self::timer0 as timer1;

I'll take a look at it!

Since basic svdtools integration has been added to the gen-tools and you have authored the first batch of patches for the EFM32TG11B120, I guess that issue can be closed.


[newrelic-logging] Add sha256sum ConfigMap annotation to fluent-bit DaemonSet

It allows the pods to be recreated if a change happens on the fluent-bit ConfigMap.
We've followed same approach that other charts like https://github.com/newrelic/nri-kubernetes/blob/main/charts/newrelic-infrastructure/templates/controlplane/daemonset.yaml#L31-L32
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [mychartname])

Already implemented https://github.com/newrelic/helm-charts/pull/906


Fix open zeppelin proxy detection

Description
This PR adds support for detecting OpenZeppelin proxies by uncommenting and implementing the OpenZeppelin implementation slot detection logic in the detectProxyTarget function.
Changes made:

Uncommented the OPEN_ZEPPELIN_IMPLEMENTATION_SLOT constant.
Added a new detectUsingOpenZeppelinSlot function to check for OpenZeppelin proxies.
Included the new detection method in the primary detection methods array.

Additional Information

[x] I have read the contributing docs (if this is your first contribution)
[x] This is not a duplicate of any existing pull request

Related Issues
Fixes #154
Your ENS/address: portdev.eth

@Pabl0cks thanks for the feedback!
I have just checked the main branch and this problem exists there too.
Merging in https://github.com/BuidlGuidl/abi.ninja/tree/feat/getsourcecode fixes that problem as well as improving the overall app.
Here is a deployment link for that branch if you'd like to test:
https://abi-ninja-v2-git-feat-getsourcecode-buidlguidldao.vercel.app/
My suggestion here would be, since the problem exists on prod deployment as well, is either:
-> merge this, i open a new pr for getsourcecode, merge that
-> I close this and make getsourcecode + this as one new pr
How do those options sound? Happy to hear any ideas!

I don't remember the exact reason why we commented it out (might be related to when we separated the logic)
But when we merge getsourcecode PR we will remove these all!


Update the gossiper finished announcement and use this in the block proposer

The gossiper currently emits a FinishedGossiping announcement when it has completed gossiping about a given item.  In the case of Deploys, this announcement was to be used by the block proposer as an indication that the given Deploy was now suitable for inclusion in a proposed block.
The block proposer needs a delay between learning of a Deploy and proposing it, since any peers receiving the proposed block would potentially flood the proposer with requests to provide them with the Deploy.  The natural choice for such a delay is to use the announcement from the gossiper, as it indicates the Deploy has likely been gossiped far enough to avoid a flood of requests.
However, it was found that the gossiper's announcement is unsuitable since it doesn't take into account the Deploy not yet having been received.  Since Deploys themselves aren't gossiped, but only their IDs, we saw an edge case being hit whereby a node would have finished gossiping about a given deploy before it had actually received and stored the Deploy.  The block proposer requires the Deploy to be in local storage to propose it.
Hence either:

the gossiper announcement should be updated to only happen once the complete item has been received and stored, and gossiping has completed
the block proposer needs to only consider a Deploy suitable once the gossiper announcement has been made and the deploy acceptor has made a AcceptedNewDeploy announcement for that Deploy.

To do: Track in L1 Daily.

The event is forwarded to the transaction buffer here:
https://github.com/casper-network/casper-node/blob/d14054d73872414e8ee4a4b16551b210f620a83e/node/src/reactor/main_reactor.rs#L853
and it is handled by the transaction buffer here:
https://github.com/casper-network/casper-node/blob/db822516fc681ece6611afdbb7d4c1c2301abb53/node/src/components/transaction_buffer.rs#L789


What does "none select for random" mean (options page)?

Um, I really don't understand what this phrase is supposed to mean. 🤔 Or is this a common English term I don't understand as a foreigner? 😅 I mean: This phrase appears even though I've selected multiple search engines in the options page...
I need this info in order to translate it into German 🤪

This is supposed to mean, "if no search engine is selected by the user, the extension will randomly choose a search engine to redirect to". So, if none of the search engines are picked by user (shown in the image), the search engine that will be redirected to will be random.

I'm very sorry for making it very confusing. I should probably change it in English as well. Sorry, I do see why this could be a confusion.
Thank you for the call out!!　😄

Ah, that makes sense. Thanks for the clarification. But why then does it appear even if I did select some search engines? 🤔 Or is the string not supposed to disappear at all? I'm standing on the cable right now, as we Germans say 😅

Oh yeah! It’s supposed to be showing all the time. I think I should change this as it is very confusing. I’ll use the same string so don’t worry about re-translating. Thank you!

I will close this as I changed it to "none for random", which hopefully is easier to understand. Thank you for pointing this out!


No usable version of libssl was found

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/hello-world-tutorial/create
Operating System: linux
I used the following command:
dotnet new webApp -o myWebApp --no-https
I got the following error:
No usable version of libssl was found
Aborted
I'm using Void Linux and I have the following ssl/tls packages installed:
libressl-3.0.2_2
libressl-devel-3.0.2_2
libssl47-3.0.2_2
libtls19-3.0.2_2
Thanks!

I tried the following command and it seems to be working now:
ln -s /usr/lib/libssl.so.47.0.6 /usr/lib/libssl.so.1.0.0
I'm not sure if this will result in any problems later.  Thanks for any help.

There's some more information at https://github.com/dotnet/runtime/issues/24869

I'm glad you found a solution. Please refer to the dependencies to ensure you've got all the required prerequisites.

FWIW, the dependencies link in the comment above does not actually list what the native dependencies for running dotnet on linux actually are.

I was trying to install PowerShell and had the same issue (_ No usable version of libssl was found_).
I installed a package named libssl47 (available on Void Linux's official repository) and pwsh works fine now.

For futture me and anyone else searching this and ending up here.
Likely only an issue with your system not providing openssl-1 which dotnet 5.x expects.
Please note that you can always manually install these dependencies. In specific openssl-1.1.1-c can be installed using the following set of commands on most linux systems:
wget https://www.openssl.org/source/openssl-1.1.1c.tar.gz
tar -xzvf openssl-1.1.1c.tar.gz
cd openssl-1.1.1c
./config
make
sudo make install (it puts it into /usr/local/lib so it doesn't mess with the rest of your system)

Messing with LD_LIBRARY_PATH is usually considered bad practice so please read up on how to do this on your linux in a better way!
Having said that, here is how to map this temporary via LD_LIBRARY_PATH:
LD_LIBRARY_PATH="/usr/local/lib" dotnet
# or
export export LD_LIBRARY_PATH="/usr/local/lib"

Does somebody have a solution where I don't need to install an old openssl? I have libssl.so.3
CLR_OPENSSL_VERSION_OVERRIDE=3
export CLR_OPENSSL_VERSION_OVERRIDE
or
ln -s /usr/lib/libssl.so.3  /usr/lib/libssl.so.1.0.0
have the same effect
Cannot get required symbol ERR_put_error from libssl

I would settle for updating the LD path for dotnet. LD_LIBRARY_PATH
doesn't seem to have an effect

Does anybody have a solution where I don't need to install an old openssl?

If this is .NET Core 3.1, then no. There's no solution. .NET Core 3.1 just doesn't support OpenSSL 3.x, so you really do need to have an older version of OpenSSL (either 1.0 or 1.1) for it to work.
On the other hand, .NET Core 3.1 goes EOL next month. The newer supported releases - 6.0 and 7.0 - both support OpenSSL 3.0. Maybe you can think about moving to one of those supported releases 1 month early?

ln -s /usr/lib/libssl.so.3 /usr/lib/libssl.so.1.0.0

Please don't do this. This file says "hey, over here! I am OpenSSL 1.0! use me!" .NET is fairly smart and errors out nicely. Another program may trust that claim and accidentally do something really bad.

Would https://github.com/dotnet/runtime/pull/80380 solve this issue?

Tried all the solutions above, still doesn't work

Here's what worked for me on Ubuntu. Download "libssl1.0.0_1.0.2n-1ubuntu5_amd64.deb" from here.
To install run: sudo dpkg -i libssl1.0.0_1.0.2n-1ubuntu5_amd64.deb

On Fedora 32+ you can install compat-openssl10 and everything should be fine😉

For futture me and anyone else searching this and ending up here.
Likely only an issue with your system not providing openssl-1 which dotnet 5.x expects.
Please note that you can always manually install these dependencies. In specific openssl-1.1.1-c can be installed using the following set of commands on most linux systems:
wget https://www.openssl.org/source/openssl-1.1.1c.tar.gz
tar -xzvf openssl-1.1.1c.tar.gz
cd openssl-1.1.1c
./config
make
sudo make install (it puts it into /usr/local/lib so it doesn't mess with the rest of your system)

Messing with LD_LIBRARY_PATH is usually considered bad practice so please read up on how to do this on your linux in a better way! Having said that, here is how to map this temporary via LD_LIBRARY_PATH:
LD_LIBRARY_PATH="/usr/local/lib" dotnet
# or
export export LD_LIBRARY_PATH="/usr/local/lib"

This answer is great, however when I tried running
openssl version

I got this error
openssl: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
To resolve this, we need to ensure that the system knows where to find the new libraries. Here are the steps to do so:

Verify that the libraries are installed in /usr/local/lib:
ls -l /usr/local/lib | grep libssl

You should see libssl.so.1.1 and related libraries listed.

Create a configuration file for the dynamic linker:

Create a new file in the /etc/ld.so.conf.d/ directory:
sudo nano /etc/ld.so.conf.d/openssl-1.1.1c.conf

Add the following line to this file:
/usr/local/lib

Save and exit the editor (Ctrl+X, then Y, then Enter).

Update the dynamic linker run-time bindings:
sudo ldconfig

Verify that the library path is updated:

Run the following command to check if ldconfig has picked up the new libraries:ldconfig -p | grep libssl

You should see entries for /usr/local/lib/libssl.so.1.1 and similar libraries.

Retry the OpenSSL version command:
openssl version

Set the LD_LIBRARY_PATH environment variable (if necessary):

Temporarily set LD_LIBRARY_PATH to include /usr/local/lib:
export LD_LIBRARY_PATH=/usr/local/lib

Add this to your ~/.bashrc or ~/.profile for persistent changes:
echo 'export LD_LIBRARY_PATH=/usr/local/lib' >> ~/.bashrc
source ~/.bashrc

Verify the OpenSSL version again and try building your .NET application:
openssl version
dotnet build

By following these steps, the system should recognize the newly installed OpenSSL libraries, allowing you to run openssl and dotnet commands without errors.


Use the action when clicking "Yes"

Hi, would that be possible to actually use the action (send the reaction card in the chat) when clicking on the "Yes" when asked if the reaction was used ? There is already a button of the reaction coming with the question, but unless I'm missing something we can't interact with it to actually use the reaction and send the chat card. If that could be done by clicking Yes" it would spare the time to search the reaction in the sheet to send the chat card, and let the player target before clicking "Yes" to automate the effect of the reaction if there are any.

I think I will try to automate this process, but with targeting it be more hardly
Maybe for start it would be "Yes (Choose target)", if need to target or  "Yes" not

Idk how it works behind the scene, but for example with Action support, if I target my ally when he triggers a reactive strike and then click "Yes", if clicking Yes only send the reaction chat card, wouldn't that count as if I clicked on it in my sheet and do the Action support automation as well, using the token I already targeted before clicking Yes as the target ?

Example
https://github.com/reyzor1991/foundry-vtt-pf2e-reaction/assets/6688366/d61c712b-c76e-437e-bd61-5e4c64603b82

In this case, need to update actions, and Button "Yes (Choose target)" it's only visual I can't target ally or smth else

so if I understand it right :
the (choose target) part on the button does nothing, it's just a reminder for the user to choose a target before clicking on it ?
and even if the user already has a target he needs to refresh it before clicking ?
either way it's already awesome

Yes, it's just a reminder
Not need to refresh, but need to target at correct actor because effect would be applied to target

Fix issue
Could you create video for 2 issue?
https://github.com/reyzor1991/foundry-vtt-pf2e-reaction/assets/6688366/74af71ba-71c8-4da4-b06d-e89093e3a197

all works fine, thank for your hard work


[BUG] Issue with 2.11.4

I abuse fastfetch I admit that. This bug might be hard to reproduce as result and it happens when fastfetch is used in combination with fastfetch. (there is no typo in that sentence lol).
Context of what I mean by using fastfetch with fastfetch
This is how it looks now after updating to version 2.11.4

And it gets fixed by going back to version 2.11.3:

Here is my config:
{
  "$schema": "https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json",
  "logo": {
    "color": {
      "1": "36",
      "2": "36"
    },
    "padding": {
      "left": 1,
      "right": 2,
      "top": 1
    }
  },
  "display": {
    "separator": " ",
    "color": {
      "keys": "36"
    }
  },
  "modules": [
    "separator",
    {
     "key": "Weather",
     "type": "command",
     "text": "cat $XDG_CACHE_HOME/fastfetch/weatherinfo"
    },
    {
     "key": "Date & Time",
     "type": "command",
     "text": "( fastfetch -s datetime --pipe; fastfetch -s uptime --pipe ) | sed 's/Date & Time //g; s/Uptime/- Up:/g' | tr '\n' ' '",
    },
    "separator",
    {
     "key": "System",
     "type": "command",
     "text": "( fastfetch -s os --pipe; fastfetch -s kernel --pipe ) | sed 's/Kernel/- Kernel/g; s/OS //g' | tr '\n' ' '",
    },
    {
     "key": "Packages",
     "type": "command",
     "text": "( fastfetch -s packages --pipe; echo \"-\"; am -f --less && echo \"(AppMan)\" ) | sed 's/Packages //g' | tr '\n' ' '",
    },
    {
     "key": "WM & Theme",
     "type": "command",
     "text": "( fastfetch -s wm --pipe; fastfetch -s theme --pipe ) | sed 's/WM //g; s/Theme/-/g' | tr '\n' ' '"
    },
    {
      "key": "Icon & Font",
      "type": "command",
      "text": "( fastfetch -s icons --pipe; fastfetch -s font --pipe ) | sed 's/Icons //g; s/Font/-/g' | tr '\n' ' '"
    },
    {
      "key": "Terminal & Font",
      "type": "command",
      "text": "( fastfetch -s terminal --pipe; fastfetch -s terminalfont --pipe ) | sed 's/Terminal //g; s/Font/-/g' | tr '\n' ' '"
    },
    {
     "key": "Interactive Shell",
     "type": "shell",
    },
    "cpu",
    "memory",
    {
      "key": "Swap",
      "type": "command",
      "text": "zramctl --raw | awk 'NR==2{print $5\"iB (\"$4\"iB / \"$3 \"iB) - ZRAM (\"$2\")\"}' | sed 's/\\([GMK]\\)iB/ \\1iB/g; s/BiB/ B/g'"
    },
    {
      "key": "GPU",
      "type": "command",
      "text": "cat $XDG_CACHE_HOME/fastfetch/gpuinfo"
    },
    {
      "key": "Vulkan",
      "type": "command",
      "text": "cat $XDG_CACHE_HOME/fastfetch/vulkaninfo"
    },
    {
      "type": "display",
      "compactType": "original-with-refresh-rate"
    },
    "disk",
    "physicaldisk",
    {
     "key": "Physical Disk Total IO",
     "type": "diskio",
     "detectTotal": true
    },
    "break",
    "colors"
  ]
}

The issue caused because one of my fastfetch scripts broke with the update, and now it prints the arch logo when running:

However even after disabling my scripts that pipe the output of fastfetch and removing the cached files, my fastfetch is still broken. Likely because the logo still gets printed on some of my "command" keys in the config.
I am using the released binaries from the repo (amd64.tar.gz) on archlinux.

I noticed that version 2.11.5 just released, it still has the same issue.


Tab Key doesn't work on emmet in Brackets and Sublime Text 3

Hello,

Hello,
I have a problem with emmet, when i want to expand abbreviation with tab key, emmet doesn't work. I obtein an usual space of tab key. I don't know what is wrong. I tried to uninstall the extention and reinstall, it doesn't work. That's doing in brackets and in Sublime Text it makes a weird stuf. Can someone help me please ?
Sincerly

Same problem here. TAB key stopped expanding. Could really use some help

same

Same

It's rerun now !
Le mer. 17 oct. 2018 à 08:35, hatemfrere<EMAIL_ADDRESS>a
écrit :

Same
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/emmetio/brackets-emmet/issues/128#issuecomment-430507122,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkgDVwJoGdUy3PQ5LNHqvTQREzgBR-Z6ks5uls_IgaJpZM4TPZaf
.

same here


[draco] Update to 1.4.3

Describe the pull request

What does your PR fix?
Updates draco to 1.4.3

Which triplets are supported/not supported? Have you updated the CI baseline?
As before, Yes

Does your PR follow the maintainer guide?

Yes

@chausner ,Could you please take a look:
https://dev.azure.com/vcpkg/public/_build/results?buildId=62287&view=artifacts&pathAsName=false&type=publishedArtifacts

@chausner ,Could you please take a look: https://dev.azure.com/vcpkg/public/_build/results?buildId=62287&view=artifacts&pathAsName=false&type=publishedArtifacts

Should be fixed now.


Updating 201 monitoring

Fixes:

https://github.com/aws-samples/aws-workshop-for-kubernetes/issues/407
https://github.com/aws-samples/aws-workshop-for-kubernetes/issues/491

Also bumps ksm for more metrics and Prom-operator.
Description of changes:
Clarify the README.md for Cloud9 users. The user need to modify the proxy command to see the Grafana and Prometheus dashboards.
Also fixes the RBAC issue for the prometheus deployment.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@CharlyF Will you create a PR for upstream? I'd like to include this contribution.

Will do @buzzsurfr , I noticed a few issues with the service meshes part as well, I'm trying to figure out what's going on.
I was not able to get the linkerd to work (I’m not too familiar with it but digging).
But the Istio step has issues as well, I was able to pinpoint the source to (I believe): https://github.com/istio/istio/issues/5327.


`dynamic atexit destructor for 'threadPool'

I'm getting a weird exception / crash at end of runtime.
This console program produces it:
#include <RStein.AsyncCpp/Tasks/TaskCompletionSource.h>

int main()
{
		RStein::AsyncCpp::Tasks::TaskCompletionSource<__int64> _tCS;
}

I had never heard of atexit() before this, and it was quite confusing. Should I ignore this crashing? Is there a work-around?
Here is the call stack for the above:
>	[Inline Frame] FolderOpenerTestConsole.exe!std::thread::{dtor}() Line 95	C++
 	[Inline Frame] FolderOpenerTestConsole.exe!std::destroy_at(std::thread * const) Line 325	C++
 	[Inline Frame] FolderOpenerTestConsole.exe!std::_Default_allocator_traits<std::allocator<std::thread>>::destroy(std::allocator<std::thread> &) Line 721	C++
 	[Inline Frame] FolderOpenerTestConsole.exe!std::_Destroy_range(std::thread * _First, std::thread * const) Line 950	C++
 	[Inline Frame] FolderOpenerTestConsole.exe!std::vector<std::thread,std::allocator<std::thread>>::_Destroy(std::thread * _First, std::thread * _Last) Line 1680	C++
 	[Inline Frame] FolderOpenerTestConsole.exe!std::vector<std::thread,std::allocator<std::thread>>::_Tidy() Line 1764	C++
 	FolderOpenerTestConsole.exe!std::vector<std::thread,std::allocator<std::thread>>::~vector<std::thread,std::allocator<std::thread>>() Line 712	C++
 	[Inline Frame] FolderOpenerTestConsole.exe!RStein::AsyncCpp::Schedulers::SimpleThreadPool::{dtor}() Line 35	C++
 	FolderOpenerTestConsole.exe!`RStein::AsyncCpp::Schedulers::Scheduler::initDefaultScheduler'::`2'::`dynamic atexit destructor for 'threadPool''()	C++
 	ucrtbase.dll!00007ffb4f4cbea0()	Unknown
 	ucrtbase.dll!00007ffb4f4cbdb7()	Unknown
 	ucrtbase.dll!00007ffb4f4cbd6d()	Unknown
 	ucrtbase.dll!00007ffb4f4ca17a()	Unknown
 	ucrtbase.dll!00007ffb4f4ca10f()	Unknown
 	ucrtbase.dll!00007ffb4f4ca0af()	Unknown
 	FolderOpenerTestConsole.exe!__scrt_common_main_seh() Line 295	C++
 	kernel32.dll!00007ffb4f5e54e0()	Unknown
 	ntdll.dll!00007ffb5174485b()	Unknown

Hi @lawabider ,
what version of the library do you use?
Current master branch, VS 2010, Relase/Debug X64 configuration.
My console application.
#include "../RStein.AsyncCpp/Tasks/TaskCompletionSource.h"
int main()
{
		RStein::AsyncCpp::Tasks::TaskCompletionSource<__int64> _tCS;
}

Result.

Related issue.
https://github.com/renestein/Rstein.AsyncCpp/issues/27

Thanks; I've downloaded the code again and it's working now.


Reset error delay on successful requests

When we encounter an error in the HttpPageBufferClient we have a backoff and we retry after the backoff. We need to reset this error backoff on successful requests to avoid latencies in requests.

looks good

Merged.


Access Violatin reading location

Line: 84 PE.C
	uint32_t* IDT_entry = (uint32_t*)rva2phys(pe, pe->NTHeaders->OptionalHeader.DataDirectory[IMAGE_DIRECTORY_ENTRY_IMPORT].VirtualAddress);

I got this error:
Exception: Exception 0xc0000005 encountered at address 0x4a294c: Access violation reading location 0xcccccd4c

I gonna check why don't work and but i think are problems with getting the PE file into Memory bytes

I make a mistake when put the exe path, but still with out work

I made tests on Windows 11 and not work y got an error on GhostWriter.C Function GWPrepareThread i will check in others OS if works

Yeah, sorry, this repo has been unmaintained for years, I don't even have a Windows system to test it on right now.
Do keep in mind that you can only inject a 32-bit process into another 32-bit process, I never got around to adding 64 bit support.


Scheduled Down Monitors

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature
🔖 Feature description
I have several platforms and servers that are not online 24/7/365 due to costs for that service and only run during hours of operation (8:00 AM to 5:00 PM). Of course, this tool is to notify in an outage but it would be nice to have scheduled monitoring so I don't get alarms at 10:00 PM constantly but having all the nice monitoring when needed.
✔ Solution
Add a setting in each monitor to setup scheduled monitoring during the creation of the new monitor and after the monitor has been created. Checkbox to enable and time range to monitor during.
❓ Alternatives
No response
📝 Additional Context
No response

This is a duplicate of #191
Someone opened a pull request https://github.com/louislam/uptime-kuma/pull/1213 which adds adds a maintenance planning system.

@koen20 Oh... I did not look back that far. I guess this can be closed out and I'll add input to that request.


Fix ccaName for reminders being not being set properly

Fix bugs introduced in earlier commit (Jivesh's editc commit)

Codecov Report

Merging #233 (6c97347) into master (041ec33) will decrease coverage by 0.26%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #233      +/-   ##
============================================
- Coverage     45.21%   44.94%   -0.27%
- Complexity      501      503       +2
============================================
  Files           121      121
  Lines          2530     2554      +24
  Branches        312      316       +4
============================================
+ Hits           1144     1148       +4
- Misses         1324     1343      +19
- Partials         62       63       +1

Impacted Files
Coverage Δ

...ss/logic/commands/reminder/ReminderAddCommand.java
0.00% <ø> (ø)

src/main/java/seedu/address/model/AddressBook.java
70.00% <ø> (+2.25%)
:arrow_up:

...ess/logic/commands/person/PersonDeleteCommand.java
65.00% <0.00%> (-10.00%)
:arrow_down:

...eminder/ReminderNameContainsKeywordsPredicate.java
33.33% <0.00%> (-9.53%)
:arrow_down:

...in/java/seedu/address/logic/parser/ParserUtil.java
35.71% <0.00%> (-0.65%)
:arrow_down:

...in/java/seedu/address/commons/util/StringUtil.java
94.73% <0.00%> (ø)

...eedu/address/model/reminder/ReminderStartDate.java
0.00% <0.00%> (ø)

...u/address/logic/commands/cca/CcaColourCommand.java
0.00% <0.00%> (ø)

... and 3 more

Continue to review full report at Codecov.

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