UI not visible?

Hello,
I have an issue where the bulk creation UI is not visible.

I installed inventree 0.15.5 via the installer. I also ran  sudo inventree run invoke update and then restart.
Should there be a section in /admin for the bulk plugin (because there is not)? Did I mis-understand anything?

Thanks!

Hi @johanneshk,
This seems like you're either running in debug mode (if so try disabling it and try again)
If it's still not solved, you may have not collected the static files. Could you please post a screenshot of the browsers devtools console and network tab?

To open the devtools press CTRL shift I.
Then select the console tab and make a screenshot of any error which is shown there.
Next navigate to the network tab and make a screenshot too.
search for a red file with bulk or panel in the name and if there is any, click on it and make a screenshot too.

Best
Lukas

It appears that indeed static files are not loaded properly...

I tried to find how to manually collect static files but couldn't find anything...
Running 'invoke update' doesn't appear to collect static files:
 sudo inventree run invoke update

Installing required python packages from 'src/backend/requirements.txt'
Requirement already satisfied: pip in ./env/lib/python3.9/site-packages (24.1.2)
Requirement already satisfied: setuptools in ./env/lib/python3.9/site-packages (69.5.1)
Collecting setuptools
  Downloading setuptools-71.0.4-py3-none-any.whl.metadata (6.5 kB)
Downloading setuptools-71.0.4-py3-none-any.whl (2.3 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 5.3 MB/s eta 0:00:00
Installing collected packages: setuptools
  Attempting uninstall: setuptools
    Found existing installation: setuptools 69.5.1
    Uninstalling setuptools-69.5.1:
      Successfully uninstalled setuptools-69.5.1
Successfully installed setuptools-71.0.4
Requirement already satisfied: asgiref==3.8.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 3)) (3.8.1)
Requirement already satisfied: async-timeout==4.0.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 9)) (4.0.3)
Requirement already satisfied: attrs==23.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 13)) (23.2.0)
Requirement already satisfied: babel==2.15.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 19)) (2.15.0)
Requirement already satisfied: bleach==6.1.0 in ./env/lib/python3.9/site-packages (from bleach[css]==6.1.0->-r src/backend/requirements.txt (line 23)) (6.1.0)
Requirement already satisfied: brotli==1.1.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 27)) (1.1.0)
Requirement already satisfied: certifi==2024.2.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 112)) (2024.2.2)
Requirement already satisfied: cffi==1.16.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 118)) (1.16.0)
Requirement already satisfied: charset-normalizer==3.3.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 174)) (3.3.2)
Requirement already satisfied: coreapi==2.3.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 266)) (2.3.3)
Requirement already satisfied: coreschema==0.0.4 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 269)) (0.0.4)
Requirement already satisfied: cryptography==42.0.7 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 273)) (42.0.7)
Requirement already satisfied: cssselect2==0.7.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 309)) (0.7.0)
Requirement already satisfied: defusedxml==0.7.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 313)) (0.7.1)
Requirement already satisfied: deprecated==1.2.14 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 319)) (1.2.14)
Requirement already satisfied: diff-match-patch==20230430 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 326)) (20230430)
Requirement already satisfied: dj-rest-auth==6.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 330)) (6.0.0)
Requirement already satisfied: django==4.2.14 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 332)) (4.2.14)
Requirement already satisfied: django-allauth==0.61.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 366)) (0.61.1)
Requirement already satisfied: django-allauth-2fa==0.11.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 369)) (0.11.1)
Requirement already satisfied: django-cleanup==8.1.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 372)) (8.1.0)
Requirement already satisfied: django-cors-headers==4.3.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 375)) (4.3.1)
Requirement already satisfied: django-crispy-forms==1.14.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 378)) (1.14.0)
Requirement already satisfied: django-dbbackup==4.1.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 381)) (4.1.0)
Requirement already satisfied: django-error-report-2==0.4.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 384)) (0.4.2)
Requirement already satisfied: django-filter==24.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 387)) (24.2)
Requirement already satisfied: django-flags==5.0.13 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 390)) (5.0.13)
Requirement already satisfied: django-formtools==2.5.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 393)) (2.5.1)
Requirement already satisfied: django-ical==1.9.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 396)) (1.9.2)
Requirement already satisfied: django-import-export==3.3.7 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 399)) (3.3.7)
Requirement already satisfied: django-js-asset==2.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 402)) (2.2.0)
Requirement already satisfied: django-maintenance-mode==0.21.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 406)) (0.21.1)
Requirement already satisfied: django-markdownify==0.9.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 409)) (0.9.3)
Requirement already satisfied: django-money==3.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 412)) (3.2.0)
Requirement already satisfied: django-mptt==0.16.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 415)) (0.16.0)
Requirement already satisfied: django-otp==1.5.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 418)) (1.5.0)
Requirement already satisfied: django-picklefield==3.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 422)) (3.2)
Requirement already satisfied: django-q-sentry==0.1.6 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 426)) (0.1.6)
Requirement already satisfied: django-q2==1.6.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 428)) (1.6.2)
Requirement already satisfied: django-recurrence==1.11.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 431)) (1.11.1)
Requirement already satisfied: django-redis==5.4.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 435)) (5.4.0)
Requirement already satisfied: django-sesame==3.2.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 438)) (3.2.2)
Requirement already satisfied: django-sql-utils==0.7.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 441)) (0.7.0)
Requirement already satisfied: django-sslserver==0.22 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 444)) (0.22)
Requirement already satisfied: django-stdimage==6.0.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 446)) (6.0.2)
Requirement already satisfied: django-taggit==5.0.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 449)) (5.0.1)
Requirement already satisfied: django-user-sessions==2.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 452)) (2.0.0)
Requirement already satisfied: django-weasyprint==2.3.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 455)) (2.3.0)
Requirement already satisfied: django-xforwardedfor-middleware==2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 458)) (2.0)
Requirement already satisfied: djangorestframework==3.14.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 460)) (3.14.0)
Requirement already satisfied: djangorestframework-simplejwt==5.3.1 in ./env/lib/python3.9/site-packages (from djangorestframework-simplejwt[crypto]==5.3.1->-r src/backend/requirements.txt (line 467)) (5.3.1)
Requirement already satisfied: drf-spectacular==0.27.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 470)) (0.27.2)
Requirement already satisfied: dulwich==0.22.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 473)) (0.22.1)
Requirement already satisfied: et-xmlfile==1.1.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 521)) (1.1.0)
Requirement already satisfied: feedparser==6.0.11 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 525)) (6.0.11)
Requirement already satisfied: fonttools==4.51.0 in ./env/lib/python3.9/site-packages (from fonttools[woff]==4.51.0->-r src/backend/requirements.txt (line 528)) (4.51.0)
Requirement already satisfied: googleapis-common-protos==1.63.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 572)) (1.63.0)
Requirement already satisfied: grpcio==1.63.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 578)) (1.63.0)
Requirement already satisfied: gunicorn==22.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 626)) (22.0.0)
Requirement already satisfied: html5lib==1.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 629)) (1.1)
Requirement already satisfied: icalendar==5.0.12 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 633)) (5.0.12)
Requirement already satisfied: idna==3.7 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 637)) (3.7)
Requirement already satisfied: importlib-metadata==7.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 641)) (7.0.0)
Requirement already satisfied: inflection==0.5.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 648)) (0.5.1)
Requirement already satisfied: itypes==1.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 652)) (1.2.0)
Requirement already satisfied: jinja2==3.1.4 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 656)) (3.1.4)
Requirement already satisfied: jsonschema==4.22.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 660)) (4.22.0)
Requirement already satisfied: jsonschema-specifications==2023.12.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 664)) (2023.12.1)
Requirement already satisfied: markdown==3.6 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 668)) (3.6)
Requirement already satisfied: markuppy==1.14 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 672)) (1.14)
Requirement already satisfied: markupsafe==2.1.5 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 675)) (2.1.5)
Requirement already satisfied: oauthlib==3.2.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 737)) (3.2.2)
Requirement already satisfied: odfpy==1.4.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 741)) (1.4.1)
Requirement already satisfied: openpyxl==3.1.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 744)) (3.1.2)
Requirement already satisfied: opentelemetry-api==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 748)) (1.24.0)
Requirement already satisfied: opentelemetry-exporter-otlp==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 760)) (1.24.0)
Requirement already satisfied: opentelemetry-exporter-otlp-proto-common==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 763)) (1.24.0)
Requirement already satisfied: opentelemetry-exporter-otlp-proto-grpc==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 769)) (1.24.0)
Requirement already satisfied: opentelemetry-exporter-otlp-proto-http==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 773)) (1.24.0)
Requirement already satisfied: opentelemetry-instrumentation==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 777)) (0.45b0)
Requirement already satisfied: opentelemetry-instrumentation-django==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 785)) (0.45b0)
Requirement already satisfied: opentelemetry-instrumentation-redis==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 788)) (0.45b0)
Requirement already satisfied: opentelemetry-instrumentation-requests==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 791)) (0.45b0)
Requirement already satisfied: opentelemetry-instrumentation-wsgi==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 794)) (0.45b0)
Requirement already satisfied: opentelemetry-proto==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 798)) (1.24.0)
Requirement already satisfied: opentelemetry-sdk==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 805)) (1.24.0)
Requirement already satisfied: opentelemetry-semantic-conventions==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 811)) (0.45b0)
Requirement already satisfied: opentelemetry-util-http==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 820)) (0.45b0)
Requirement already satisfied: packaging==24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 827)) (24.0)
Requirement already satisfied: pdf2image==1.17.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 831)) (1.17.0)
Requirement already satisfied: pillow==10.3.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 834)) (10.3.0)
Requirement already satisfied: pint==0.21 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 910)) (0.21)
Requirement already satisfied: pip-licenses==4.4.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 913)) (4.4.0)
Requirement already satisfied: prettytable==3.10.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 916)) (3.10.0)
Requirement already satisfied: protobuf==4.25.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 920)) (4.25.3)
Requirement already satisfied: py-moneyed==3.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 935)) (3.0)
Requirement already satisfied: pycparser==2.22 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 939)) (2.22)
Requirement already satisfied: pydyf==0.10.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 943)) (0.10.0)
Requirement already satisfied: pyjwt==2.8.0 in ./env/lib/python3.9/site-packages (from pyjwt[crypto]==2.8.0->-r src/backend/requirements.txt (line 947)) (2.8.0)
Requirement already satisfied: pyphen==0.15.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 953)) (0.15.0)
Requirement already satisfied: pypng==0.20220715.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 957)) (0.20220715.0)
Requirement already satisfied: python-barcode==0.15.1 in ./env/lib/python3.9/site-packages (from python-barcode[images]==0.15.1->-r src/backend/requirements.txt (line 961)) (0.15.1)
Requirement already satisfied: python-dateutil==2.9.0.post0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 964)) (2.9.0.post0)
Requirement already satisfied: python-dotenv==1.0.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 970)) (1.0.1)
Requirement already satisfied: python-fsutil==0.14.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 973)) (0.14.1)
Requirement already satisfied: python3-openid==3.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 977)) (3.2.0)
Requirement already satisfied: pytz==2024.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 981)) (2024.1)
Requirement already satisfied: pyyaml==6.0.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 988)) (6.0.1)
Requirement already satisfied: qrcode==7.4.2 in ./env/lib/python3.9/site-packages (from qrcode[pil]==7.4.2->-r src/backend/requirements.txt (line 1043)) (7.4.2)
Requirement already satisfied: rapidfuzz==3.9.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1047)) (3.9.0)
Requirement already satisfied: redis==5.0.4 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1138)) (5.0.4)
Requirement already satisfied: referencing==0.35.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1142)) (0.35.1)
Requirement already satisfied: regex==2024.4.28 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1148)) (2024.4.28)
Requirement already satisfied: requests==2.31.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1228)) (2.31.0)
Requirement already satisfied: requests-oauthlib==2.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1236)) (2.0.0)
Requirement already satisfied: rpds-py==0.18.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1240)) (0.18.1)
Requirement already satisfied: sentry-sdk==2.1.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1343)) (2.1.1)
Collecting setuptools==69.5.1 (from -r src/backend/requirements.txt (line 1347))
  Downloading setuptools-69.5.1-py3-none-any.whl (894 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 894.6/894.6 kB 6.2 MB/s eta 0:00:00
Requirement already satisfied: sgmllib3k==1.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1353)) (1.0.0)
Requirement already satisfied: six==1.16.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1356)) (1.16.0)
Requirement already satisfied: sqlparse==0.5.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1363)) (0.5.0)
Requirement already satisfied: tablib==3.5.0 in ./env/lib/python3.9/site-packages (from tablib[html,ods,xls,xlsx,yaml]==3.5.0->-r src/backend/requirements.txt (line 1369)) (3.5.0)
Requirement already satisfied: tinycss2==1.2.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1373)) (1.2.1)
Requirement already satisfied: typing-extensions==4.11.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1380)) (4.11.0)
Requirement already satisfied: uritemplate==4.1.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1389)) (4.1.1)
Requirement already satisfied: urllib3==2.2.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1395)) (2.2.1)
Requirement already satisfied: wcwidth==0.2.13 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1402)) (0.2.13)
Requirement already satisfied: weasyprint==61.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1406)) (61.2)
Requirement already satisfied: webencodings==0.5.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1410)) (0.5.1)
Requirement already satisfied: whitenoise==6.6.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1418)) (6.6.0)
Requirement already satisfied: wrapt==1.16.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1421)) (1.16.0)
Requirement already satisfied: xlrd==2.0.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1496)) (2.0.1)
Requirement already satisfied: xlwt==1.3.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1500)) (1.3.0)
Requirement already satisfied: zipp==3.18.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1504)) (3.18.1)
Requirement already satisfied: zopfli==0.2.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1508)) (0.2.3)
Installing collected packages: setuptools
  Attempting uninstall: setuptools
    Found existing installation: setuptools 71.0.4
    Uninstalling setuptools-71.0.4:
      Successfully uninstalled setuptools-71.0.4
Successfully installed setuptools-69.5.1
Installing plugin packages from '/etc/inventree/plugins.txt'
Requirement already satisfied: inventree-brother-plugin in ./env/lib/python3.9/site-packages (from -r /etc/inventree/plugins.txt (line 2)) (0.9.0)
Requirement already satisfied: inventree-bulk-plugin in ./env/lib/python3.9/site-packages (from -r /etc/inventree/plugins.txt (line 4)) (1.3.0)
Requirement already satisfied: brother-ql-inventree>=1.1 in ./env/lib/python3.9/site-packages (from inventree-brother-plugin->-r /etc/inventree/plugins.txt (line 2)) (1.2)
Requirement already satisfied: pydantic==2.* in ./env/lib/python3.9/site-packages (from inventree-bulk-plugin->-r /etc/inventree/plugins.txt (line 4)) (2.8.2)
Requirement already satisfied: Jinja2==3.* in ./env/lib/python3.9/site-packages (from inventree-bulk-plugin->-r /etc/inventree/plugins.txt (line 4)) (3.1.4)
Requirement already satisfied: MarkupSafe>=2.0 in ./env/lib/python3.9/site-packages (from Jinja2==3.*->inventree-bulk-plugin->-r /etc/inventree/plugins.txt (line 4)) (2.1.5)
Requirement already satisfied: annotated-types>=0.4.0 in ./env/lib/python3.9/site-packages (from pydantic==2.*->inventree-bulk-plugin->-r /etc/inventree/plugins.txt (line 4)) (0.7.0)
Requirement already satisfied: pydantic-core==2.20.1 in ./env/lib/python3.9/site-packages (from pydantic==2.*->inventree-bulk-plugin->-r /etc/inventree/plugins.txt (line 4)) (2.20.1)
Requirement already satisfied: typing-extensions>=4.6.1 in ./env/lib/python3.9/site-packages (from pydantic==2.*->inventree-bulk-plugin->-r /etc/inventree/plugins.txt (line 4)) (4.11.0)
Requirement already satisfied: click in ./env/lib/python3.9/site-packages (from brother-ql-inventree>=1.1->inventree-brother-plugin->-r /etc/inventree/plugins.txt (line 2)) (8.1.7)
Requirement already satisfied: packbits in ./env/lib/python3.9/site-packages (from brother-ql-inventree>=1.1->inventree-brother-plugin->-r /etc/inventree/plugins.txt (line 2)) (0.6)
Requirement already satisfied: pillow>=10.0.0 in ./env/lib/python3.9/site-packages (from brother-ql-inventree>=1.1->inventree-brother-plugin->-r /etc/inventree/plugins.txt (line 2)) (10.3.0)
Requirement already satisfied: pyusb in ./env/lib/python3.9/site-packages (from brother-ql-inventree>=1.1->inventree-brother-plugin->-r /etc/inventree/plugins.txt (line 2)) (1.2.1)
Requirement already satisfied: attrs in ./env/lib/python3.9/site-packages (from brother-ql-inventree>=1.1->inventree-brother-plugin->-r /etc/inventree/plugins.txt (line 2)) (23.2.0)
Backing up InvenTree database...
Python version 3.9.5 - /opt/inventree/env/bin/python3
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Backing Up Database: /opt/inventree/data/database.sqlite3
Backup size: 1.6 MiB
Writing file to default-inventree-2024-07-21-085453.dump.gz
Backing up InvenTree media files...
Python version 3.9.5 - /opt/inventree/env/bin/python3
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Backup size: 10.3 MiB
Writing file to inventree-2024-07-21-085457.tar.gz
Running InvenTree database migrations...
========================================
Python version 3.9.5 - /opt/inventree/env/bin/python3
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
No changes detected
Python version 3.9.5 - /opt/inventree/env/bin/python3
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Python version 3.9.5 - /opt/inventree/env/bin/python3
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Operations to perform:
  Synchronize unmigrated apps: allauth, allauth_2fa, corsheaders, crispy_forms, dbbackup, dj_rest_auth, django_cleanup, django_filters, django_ical, django_otp, djmoney, drf_spectacular, formtools, generic, import_export, maintenance_mode, markdownify, messages, mptt, registration, rest_framework, runserver_nostatic, staticfiles, web
  Apply all migrations: InvenTree, account, admin, auth, build, common, company, contenttypes, django_q, error_report, exchange, flags, label, machine, order, otp_static, otp_totp, part, plugin, report, socialaccount, stock, taggit, user_sessions, users
Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
Running migrations:
  No migrations to apply.
========================================
InvenTree database migrations completed!
Updating frontend...
Downloading frontend...
fatal: not a git repository (or any of the parent directories): .git
[INFO] Running in package environment, got commit "b13cd712dc87c6d67013a7cccc2795d1a60b959c" from VERSION file
Current frontend information for commit is not available - this is expected in some cases
Found workflow QC (run 13497-1)
Found artifact frontend-build with id<PHONE_NUMBER> (1.88MB).

GitHub doesn't allow artifact downloads from anonymous users. Either download the following file
via your signed in browser, or consider using a point release download via invoke frontend-download --tag <git-tag>

    Download: https://github.com/InvenTree/inventree/suites/26140571385/artifacts/1713798115 manually and
    continue by running: invoke frontend-download --file <path-to-downloaded-zip-file>
Python version 3.9.5 - /opt/inventree/env/bin/python3
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Rendered all files in /opt/inventree/src/backend/InvenTree/templates/js/translated
Collecting static files...
Python version 3.9.5 - /opt/inventree/env/bin/python3
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Python version 3.9.5 - /opt/inventree/env/bin/python3
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Python version 3.9.5 - /opt/inventree/env/bin/python3
File “/opt/inventree/src/backend/InvenTree/locale/th/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/zh/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/en/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/fa/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/fr/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/tr/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/sr/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/sv/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/it/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/zh_hant/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/es/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/es_MX/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/he/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/hi/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/hu/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/zh_Hans/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/bg/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/ko/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/no/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/pl/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/sl/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/lv/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/da/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/ja/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/el/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/fi/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/de/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/nl/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/sk/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/ru/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/pt/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/vi/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/pt_br/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/id/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/uk/LC_MESSAGES/django.po” is already compiled and up to date.
File “/opt/inventree/src/backend/InvenTree/locale/cs/LC_MESSAGES/django.po” is already compiled and up to date.
InvenTree translation coverage: 19%

Though now I see that updating the frontend failed, so I'll try to manually update that.

Yes, the problem is with static files. #7425 has broken how static files were collected. I'll be working on updating the plugin.

Are you sure, you're running v0.15.x? Then this seems like a different bug, as the mentioned PR is was not back ported into 0.15.x. Could you please check the following three things for me:

If the static folder on your disk contains a folder called inventree-bulk-plugin or plugins/inventree-bulk-plugin. If there is one of those, please post back which one and the contents of the folder.

If not, try running sudo inventree run invoke static, and check again.
If you successfully found the folders, please check if you can server the files via http://your-domain.com/static/inventree-bulk-plugin/dist/bulk-creation-panel.js or http://your-domain.com/static/plugins/inventree-bulk-plugin/inventree-bulk-plugin/dist/bulk-creation-panel.js

Have the same issue. After running invoke static, neither subdirectory shows up.

Have the same issue. After running invoke static, neither subdirectory shows up.

@eiaro How have you installed inventree? Using the installer? Docker? And which version (best would be to also provide the commit hash, you can find that in the ui with the about inventree modal)

@wolflu05 Installed Inventree by following the official Docker guide. I'm running 0.15.5 (stable).
Version Information:
InvenTree-Version: 0.15.5
Django Version: 4.2.14
Commit Hash: cc45357
Commit Date: 2024-07-12
Database: postgresql
Debug-Mode: False
Deployed using Docker: True
Platform: Linux-6.1.0-10-amd64-x86_64-with
Installer: DOC
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}, {'name': 'InvenTreeCurrencyExchange', 'slug': 'inventreecurrencyexchange', 'version': '1.0.0'}, {'name': 'InvenTreeLabel', 'slug': 'inventreelabel', 'version': '1.0.0'}, {'name': 'InvenTreeLabelMachine', 'slug': 'inventreelabelmachine', 'version': '1.0.0'}, {'name': 'InvenTreeLabelSheet', 'slug': 'inventreelabelsheet', 'version': '1.0.0'}, {'name': 'DigiKeyPlugin', 'slug': 'digikeyplugin', 'version': '1.0.0'}, {'name': 'LCSCPlugin', 'slug': 'lcscplugin', 'version': '1.0.0'}, {'name': 'MouserPlugin', 'slug': 'mouserplugin', 'version': '1.0.0'}, {'name': 'TMEPlugin', 'slug': 'tmeplugin', 'version': '1.0.0'}, {'name': 'Brother Labels', 'slug': 'brother', 'version': '0.9.0'}, {'name': 'IPNGenerator', 'slug': 'ipngen', 'version': '0.1'}, {'name': 'InvenTreeBulkPlugin', 'slug': 'inventree-bulk-plugin', 'version': '1.3.0'}]

Thanks for that information, that helps. There seems to be multiple issues at the inventree side with the latest version and plugins in my tests. But not sure about stable I need to do some deeper analysis in the next days.

I have checked with stable again. It's working fine for me there. Have you @eiaro  and @johanneshk  both checked, that you have enabled the app integration plugins?
In PUI:

Or CUI:

If not, activate it, stop the server and then run invoke update. The plugin should work just fine then.

@wolflu05 I'm so sorry, I indeed didn't have the switches above enabled :( . I honestly didn't understand this part in the documentation "Make sure you allow the use of the url integration and app integration" and then just didn't consider it further. I enabled the switch and invoked 'update' and now it works! If you think it's useful I can submit an update to the instruction, I think something like the following would have made it clear to me (as an absolute beginner with Inventree):
"Make sure to enable 'Enable URL integration' and 'Enable app integration' switches in Plugin Settings section"
Again, my bad and oversight, I didn't read the documentation with enough care. Thanks!

Glad that we got this sorted out. And thanks, that's also how I discovered that plugins using static files won't work correctly with the latest version before the latest version is officially released, so this can be fixed.

I think something like the following would have made it clear to me

Thats a very good suggestion, I'll change that in the documentation in a few days when I'll fix the issue with the latest version, as the install instructions are slightly simpler with 0.16 then (no need to manually invoke update, the static files should be collected and migrations should run automatically then).


Fixes unknown option for heartbeat rhythm; adds i18n to vitals section

Proposed Changes

Fixes #8406

@coronasafe/care-fe-code-reviewers @coronasafe/code-reviewers
Merge Checklist

[x] Add specs that demonstrate bug / test a new feature.
[x] Ensure that UI text is kept in I18n files.
[x] Prep screenshot or demo video for changelog entry, and attach it to issue.
[x] Request for Peer Reviews
[ ] Completion of QA

Tested working @nihal467

LGTM


Resolve syncing conflicts from repo_sync_working_branch to master

Pull request opened by Docs to resolve syncing conflicts from repo_sync_working_branch to master.

Resolved the merge conflict per https://github.com/MicrosoftDocs/visualstudio-docs-pr/pull/8433/files. We'll merge the PR.


Serverless reverse proxy implementation

Background
we need a basic reverse proxy for 0x and zerion
some sort of serverless infra should be utilized for this.
https://www.serverless.com/ has been offered as a good solution for simple lambda abstraction
Acceptance Criteria

implement basic reverse proxy for 0x / zerion, test all critical endpoints called by the shapeshift app
determine proper secret storage (can we use GH secrets) and access (how do we rotate keys)
CI/CD process for updates
ping @0xean for adding cnames / cloudfront
endpoints should restrict origin
rate limiting by ip would be nice to have, but could also be done in CF
write lambda in TS

https://chat.openai.com/share/df7d9ffc-dc50-4107-b198-338f9c2d9f31


Add a Benchmark Framework for Proxy Changes

I'm interested in adding benchmarking for the proxy before I make some memory management changes so that I can actually measure if they're making a significant change. So I'm going to do some research and write benchmarking tests

Still need to add a tls version

I think this can be closed, right? TLS is finished?

Yep, https://github.com/nccgroup/tracy/pull/40

There That I
On Thu, Jul 26, 2018, 8:59 PM Natnael Getahun<EMAIL_ADDRESS>wrote:

Closed #31 https://github.com/nccgroup/tracy/issues/31.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nccgroup/tracy/issues/31#event-1756447691, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACcVCpQZDXUcKW_iIBcF_qvvfGW93XHFks5uKpAWgaJpZM4VIVCc
.

E
y it t it u t
😉😗🛃🚹♿
I'd htd rrhudgggz
On Sun, Jul 29, 2018, 4:34 PM Michael Roberts<EMAIL_ADDRESS>wrote:

There That I
On Thu, Jul 26, 2018, 8:59 PM Natnael Getahun<EMAIL_ADDRESS>wrote:

Closed #31 https://github.com/nccgroup/tracy/issues/31.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nccgroup/tracy/issues/31#event-1756447691, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACcVCpQZDXUcKW_iIBcF_qvvfGW93XHFks5uKpAWgaJpZM4VIVCc
.


Stepper component

Integrate this plugin: https://kinark.github.io/Materialize-stepper/
Probably as a region template.

Don't want to rely on a plugin afterall


Difference between Caption and Section extraction in GROBID 0.7.0

Hello,
I have been evaluation GROBID for multiple semantic structures. And when it comes to Caption and Section Header extraction, I could not see unique tags for both in TEI XML. Instead, they are both appearing under the tag "Head."
Is there any other way I can extract Section Headers and Captions separately?
For example

Introduction
Despite the proliferation of clustering algorithms (Kmeans-based, spectral, density-based, statistical), hierarchical clustering (HC) algorithms still are one of the most commonly used variants. This is attributed to their parameterless nature and their simplicity of implementation. No cluster parameter is required because HC builds a nested hierarchy of the clusters formed, often visualized using dendrograms. Dendrograms can be 'cut' at any level to form the desired number of clusters.

Many HC algorithms run in Ω(N 2 ) time because all pairwise distances are computed. This limits their applicability to rather small datasets. Solutions exist that attempt to mitigate the large runtime by means of approximations, heuristic search, projections, etc. As we will discuss in depth in the Related Work Section, many of these algorithms come with several assumptions or traits that impose certain limitations: complex parameter choices, applicability for specific linkage functions

• Introduction of a single data property B for adaptive analysis to capture the computational difficulty of hierarchical clustering.

1.1 Overview Our clustering algorithms consist of two phases. The first phase is the same for all algorithms and partitions the data into sets of close points. The algorithm PerturbMultiPartition, described in Section 4, constructs sets of neighboring points by first perturbing the points given to deal with unfavorable point arrangements and then partitioning them using random projections onto randomly chosen lines. The distances between points on a projected line are scaled by the same factor for all points in expectation. So, close points in the high-dimensional space remain close on the random line and distant points remain distant.

The second phase uses the sets resulting from the partitioning to create clusters efficiently by computing distances only for pairs of points contained in the same set. Thus, instead of computing the entire distance matrix of size Ω(N 2 ) for N points, our algorithm generally requires much fewer distance computations. Specifically, the number of required distance computations depends on the density of data points as discussed and formalized in Section 5.

and

Table 2 :2<figDesc>The HCs (i.e. dendrograms) computed by the RP-SLC/ALC algorithms and traditional HC algorithms are almost identical. 100%</figDesc>
<row><cell>2000</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell>8000</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell cols="2">Single¡Linkage</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>Time (sec)</cell><cell cols="2">Clustering</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell cols="2">Average¢Linkage Clustering</cell><cell></cell></row><row><cell>1000</cell><cell></cell><cell></cell><cell>22x</cell><cell></cell><cell cols="2">4000</cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell>10x</cell><cell></cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>RP SLC</cell><cell></cell><cell></cell><cell></cell><cell cols="2">RP£ALC</cell><cell></cell></row><row><cell>0</cell><cell>10K</cell><cell>20K</cell><cell>30K</cell><cell>40K</cell><cell>50K</cell><cell>0</cell><cell>1K</cell><cell>2K</cell><cell>3K</cell><cell>4K</cell></row><row><cell></cell><cell></cell><cell cols="3">Number of Objects</cell><cell></cell><cell></cell><cell></cell><cell>Number of Objects</cell><cell></cell><cell></cell></row>

Hello @Apurv3377 !
This is actually an XML question :)
We usually use XPath to get structured content:

"//dev/head" for section header
"//figure/head" for figure header

In python, you can use lxml, which is very good (you will need to specificy the namespace http://www.tei-c.org/ns/1.0 as argument). There are good xml libraries in every languages.
With command line xmllint it's something like this:
xmllint --xpath "//*[local-name()='div']/*[local-name()='head']" file.xml

xmllint --xpath "//*[local-name()='figure']/*[local-name()='head']" file.xml

because xmllint does not support namespaces setting.
Hope this helps !


cksum/hashsum: Support for non-UTF-8 input in checksum files

Second part of splitting #6603.
This PR adds support for non-UTF-8 checksum file content for cksum and hashsum validation tools.
In practice, given a CHECKSUM file with the following content, non-UTF-8 characters can appear in 2 places:

in the filename
in a comment
All the other places are either algorithm name, which should be ASCII, or hexa/base64 digest, which should be ASCII as well.

$ cat CHECKSUM
SHA1 (filename-might-have-non-utf-8) = 058ab38dd3603703b3a7063cf95dc51a4286b6fe
# comment-might-have-non-utf-8

The most important step is to get rid of the call to BufRead::lines() to iterate on the lines of the CHECKSUM file, otherwise, it panics on non-UTF-8 characters.
This change makes heavy use of String/OsString/Vec<u8> conversion, which happen to not be equally treated on all platforms.

I closed the PR by mistake, wanted to mark it as ready :/

@cakebaker @BenWiederhake
PR is ready for review if one of you can take a look :)

@RenjiSann sorry, there are some conflicts :|

Ready for what should be a final review :)


Logically Impossible Seed - blue potion (MM) requires >99 rupees if shop shuffle (MM) is turned on

The full explanation of why I think I got a logically impossible seed (that I got around with bombchus) is rather long, so I'll explain in brief what I think probably went wrong in logic:
One route through the Beneath the Well (MM) section requires blue potions, but these aren't repeatedly obtainable if you don't have either progressive wallet (MM) AND have got shop shuffle enabled
Here's that full explanation:
Let's focus on the Goron mask, which we need to obtain to beat this seed. The logic expects you to be able to get to this check:
MM Beneath the Well Mirror Shield: Goron Mask (MM)
As a result of getting Goron mask you can do this check:
MM Goron Baby: Bomb Bag (OoT)
I think this bomb bag leads to this next check, but I can't tell for certain:
OOT MQ Fire Temple 1f Lava Room Goron Chest: Progressive Wallet (MM)
This progressive wallet leads to the second progressive wallet:
MM Blacksmith Gilded Sword: Progressive Wallet (MM)
So therefore it is logically impossible for the player to have more than 99 rupees before they obtain the Goron Mask.
Let's take a step back now and work out the possible conditions for getting to the Beneath The Well Mirror Shield check. We have two routes, the front route and the back route.
The back route requires that we have light arrows. Light arrows (MM) are in Ganon's Castle. This is unreachable, but for brevity I'll omit the details.
The front route requires we have a big poe to give to the gibdo. The two locations for a big poe in MM are:

Ikana Graveyard - dampe digging.
Beneath the well - west side poe room

1 is unobtainable because
MM Pirate Fortress Sewers Chest 1: Captain's Hat
Sewers requires Goron mask to hit a switch to enter.
2 is unobtainable because you need a blue potion. The scrub at Ikana charges 100 rupees, which is impossible when you only have 99 rupees. Alternatively, you can get a blue potion from the potion shop in the swamp for 60 rupees (and mask of scents), but not if you have shop shuffle (MM) enabled!

 HP: Keaton Mask
Termina Field:
MM Astral Observatory Moon Tear: Pocket Cucco
MM Termina Field Water Chest: 10 Arrows (OoT)
MM Termina Field Tall Grass Chest: Mask of Truth (MM)
MM Termina Field Tree Stump Chest: 20 Bombs (OoT)
MM Termina Field Kamaro Mask: Purple Rupee (MM)
MM Termina Field Tall Grass Grotto: 10 Bombchu (OoT)
MM Termina Field Pillar Grotto: 10 Bombchu (OoT)
MM Termina Field Peahat Grotto: OOT_STICK
MM Termina Field Dodongo Grotto: Bottle - Blue Fire
MM Termina Field Bio Baba Grotto: Blue Rupee (OoT)
MM Termina Field Scrub: Piece of Heart (OoT)
MM Termina Field Gossip Stones HP: Red Rupee (MM)
MM Termina Field Cow Front: Romani Milk
MM Termina Field Cow Back: Romani Milk
Road to Southern Swamp:
MM Road to Southern Swamp HP: Deku Shield
MM Road to Southern Swamp Grotto: 10 Arrows (OoT)
MM Swamp Archery Reward 1: Small Key (Spirit Temple)
MM Swamp Archery Reward 2: Bottle of Gold Dust
Southern Swamp:
MM Southern Swamp HP: Stone Mask
MM Southern Swamp Scrub Deed: Red Rupee (MM)
MM Southern Swamp Grotto: 5 Bombchu (MM)
MM Tourist Information Pictobox: Silver Rupee (MM)
MM Tourist Information Boat Cruise: Piece of Heart (MM)
MM Tourist Information Tingle Picture: Blue Rupee (OoT)
MM Woods of Mystery Grotto: Progressive Wallet (OoT)
MM Swamp Potion Shop Kotake: Piece of Heart (OoT)
MM Swamp Potion Shop Item 1: Skull Mask
MM Swamp Potion Shop Item 2: Blast Mask
MM Swamp Potion Shop Item 3: 1 Bombchu (MM)
MM Southern Swamp Song of Soaring: Piece of Heart (OoT)
Deku Palace:
MM Deku Palace HP: Fire Arrows (OoT)
MM Deku Palace Grotto Chest: 30 Arrows (MM)
MM Deku Palace Sonata of Awakening: Progressive Hookshot (OoT)
MM Deku Shrine Mask of Scents: Purple Rupee (MM)
Woodfall:
MM Woodfall Entrance Chest: Blue Rupee (MM)
MM Woodfall HP Chest: Green Potion (OoT)
MM Woodfall Near Owl Chest: Gold Rupee (OoT)
MM Woodfall Great Fairy: Recovery Heart (OoT)
Mountain Village:
MM Mountain Village Waterfall Chest: OOT_NUTS_5
MM Mountain Village Don Gero Mask: Postman's Hat
MM Mountain Village Frog Choir HP: Magic Bean (MM)
MM Mountain Village Tunnel Grotto: Recovery Heart (OoT)
MM Blacksmith Razor Blade: Piece of Heart (MM)
MM Blacksmith Gilded Sword: Progressive Wallet (MM)
MM Goron Graveyard Mask: Piece of Heart (MM)
Twin Islands:
MM Twin Islands Underwater Chest 1: Recovery Heart (OoT)
MM Twin Islands Underwater Chest 2: Silver Rupee (MM)
MM Twin Islands Frozen Grotto Chest: Empty Bottle (OoT)
MM Twin Islands Ramp Grotto Chest: Kokiri Sword (OoT)
MM Goron Elder: Zora Mask (MM)
MM Goron Race Reward: Piece of Heart (OoT)
Goron Village:
MM Goron Village HP: Magic Upgrade (OoT)
MM Goron Village Scrub Deed: Small Key (Forest Temple)
MM Goron Village Scrub Bomb Bag: Giant's Mask
MM Goron Powder Keg: 20 Bombchu (OoT)
MM Lone Peak Shrine Lens Chest: Heart Container (OoT)
MM Lone Peak Shrine Boulder Chest: Piece of Heart (MM)
MM Lone Peak Shrine Invisible Chest: Mirror Shield (MM)
MM Goron Baby: Bomb Bag (OoT)
MM Goron Shop Item 1: Piece of Heart (OoT)
MM Goron Shop Item 2: Small Key (Fire Temple)
MM Goron Shop Item 3: Purple Rupee (MM)
Road to Snowhead:
MM Path to Snowhead HP: Piece of Heart (MM)
MM Path to Snowhead Grotto: Circus Leader's Mask
Snowhead:
MM Snowhead Great Fairy: Red Rupee (MM)
Romani Ranch:
MM Romani Ranch Epona Song: Piece of Heart (OoT)
MM Romani Ranch Aliens: Silver Rupee (MM)
MM Romani Ranch Cremia Escort: Deku Stick Upgrade
MM Cucco Shack Bunny Mask: Heart Container (MM)
MM Doggy Racetrack Chest: Mirror Shield
MM Doggy Racetrack HP: Blue Rupee (OoT)
MM Romani Ranch Barn Cow Left: Romani Milk
MM Romani Ranch Barn Cow Right Front: Romani Milk
MM Romani Ranch Barn Cow Right Back: Romani Milk
Great Bay Coast:
MM Great Bay Coast Zora Mask: Light Arrows (OoT)
MM Great Bay Coast HP: Silver Rupee (MM)
MM Great Bay Coast Fisherman HP: Romani's Mask
MM Great Bay Coast Fisherman Grotto: Bottle of Chateau Romani
MM Great Bay Coast Cow Front: Romani Milk
MM Great Bay Coast Cow Back: Romani Milk
MM Laboratory Zora Song: Swamp Title Deed
MM Laboratory Fish HP: Small Key (Shadow Temple)
Pinnacle Rock:
MM Pinnacle Rock Chest 1: 5 Arrows (OoT)
MM Pinnacle Rock Chest 2: Empty Bottle (OoT)
MM Pinnacle Rock HP: Piece of Heart (OoT)
Zora Cape:
MM Zora Cape Underwater Chest: Heart Container (OoT)
MM Zora Cape Waterfall HP: Piece of Heart (MM)
MM Zora Cape Grotto: 30 Arrows (OoT)
MM Great Bay Great Fairy: Piece of Heart (OoT)
MM Zora Cape Ledge Chest 1: Piece of Heart (MM)
MM Zora Cape Ledge Chest 2: Red Potion (OoT)
MM Waterfall Rapids Beaver Race 1: Recovery Heart (OoT)
MM Waterfall Rapids Beaver Race 2: Blue Rupee (OoT)
Zora Hall:
MM Zora Hall Scrub HP: Progressive Goron Lullaby
MM Zora Hall Scrub Deed: Recovery Heart (OoT)
MM Zora Hall Evan HP: Bomb Bag (MM)
MM Zora Hall Scene Lights: Blue Rupee (OoT)
MM Zora Shop Item 1: Silver Rupee (MM)
MM Zora Shop Item 2: MM_BOMBS_10
MM Zora Shop Item 3: Blue Rupee (OoT)
Milk Road:
MM Gorman Track Garo Mask: 10 Bombchu (OoT)
Road to Ikana:
MM Road to Ikana Chest: Red Rupee (MM)
MM Road to Ikana Grotto: Recovery Heart (OoT)
MM Road to Ikana Stone Mask: Progressive Sword (MM)
Ikana Graveyard:
MM Ikana Graveyard Captain Mask: Blue Rupee (MM)
MM Ikana Graveyard Grotto: Goron Mask (OoT)
MM Beneath The Graveyard Chest: Boomerang
MM Beneath The Graveyard Song of Storms: Heart Container (OoT)
MM Beneath The Graveyard HP: 5 Bombs (OoT)
MM Beneath The Graveyard Dampe Chest: Couple's Mask
Ikana Canyon:
MM Ikana Valley Scrub Rupee: Silver Rupee (MM)
MM Ikana Valley Scrub HP: 30 Arrows (OoT)
MM Ikana Valley Grotto: Ice Arrows (OoT)
MM Ikana Great Fairy: 5 Bombs (OoT)
MM Music Box House Gibdo Mask: Sonata of Awakening
MM Ghost Hut HP: OOT_NUTS_5
Stone Tower:
MM Stone Tower Inverted Chest 1: Poe Spirit (OoT)
MM Stone Tower Inverted Chest 2: Small Key (Ganon's Castle)
MM Stone Tower Inverted Chest 3: Piece of Heart (OoT)
Woodfall Temple:
MM Woodfall Temple Entrance Chest: Stray Fairy (Woodfall Temple)
MM Woodfall Temple SF Entrance: Stray Fairy (Woodfall Temple)
MM Woodfall Temple SF Main Pot: Stray Fairy (Woodfall Temple)
MM Woodfall Temple SF Main Deku Baba: Stray Fairy (Woodfall Temple)
MM Woodfall Temple Water Chest: Stray Fairy (Woodfall Temple)
MM Woodfall Temple SF Water Room Beehive: Stray Fairy (Woodfall Temple)
MM Woodfall Temple Map: 10 Arrows (OoT)
MM Woodfall Temple SF Maze Skulltula: Stray Fairy (Woodfall Temple)
MM Woodfall Temple SF Maze Beehive: Stray Fairy (Woodfall Temple)
MM Woodfall Temple SF Maze Bubble: Stray Fairy (Woodfall Temple)
MM Woodfall Temple Compass: Piece of Heart (OoT)
MM Woodfall Temple Dark Chest: Boss Key (Woodfall Temple)
MM Woodfall Temple Center Chest: Compass (Woodfall Temple)
MM Woodfall Temple SF Main Bubble: Map (Woodfall Temple)
MM Woodfall Temple Bow: Stray Fairy (Woodfall Temple)
MM Woodfall Temple Boss Key Chest: Stray Fairy (Woodfall Temple)
MM Woodfall Temple SF Pre-Boss Bottom Right: Stray Fairy (Woodfall Temple)
MM Woodfall Temple SF Pre-Boss Left: Stray Fairy (Woodfall Temple)
MM Woodfall Temple SF Pre-Boss Top Right: Piece of Heart (OoT)
MM Woodfall Temple SF Pre-Boss Pillar: Stray Fairy (Woodfall Temple)
MM Woodfall Temple Boss Container: Stray Fairy (Woodfall Temple)
MM Woodfall Temple Boss: Goron's Ruby
Snowhead Temple:
MM Snowhead Temple Bridge Room: Stray Fairy (Snowhead Temple)
MM Snowhead Temple SF Bridge Under Platform: Stray Fairy (Snowhead Temple)
MM Snowhead Temple SF Bridge Pillar: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Map: Stray Fairy (Snowhead Temple)
MM Snowhead Temple SF Map Room: Progressive Sword (MM)
MM Snowhead Temple Map Alcove: Fish (OoT)
MM Snowhead Temple Central Room Alcove: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Pillars Room: Boss Key (Snowhead Temple)
MM Snowhead Temple Central Room Bottom: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Block Room: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Block Room Ledge: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Compass: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Compass Room Ledge: Compass (Snowhead Temple)
MM Snowhead Temple SF Compass Room Crate: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Icicle Room Alcove: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Icicle Room: Stray Fairy (Snowhead Temple)
MM Snowhead Temple SF Dual Switches: Red Rupee (MM)
MM Snowhead Temple Fire Arrow: Stray Fairy (Snowhead Temple)
MM Snowhead Temple SF Snow Room: Small Key (Stone Tower Temple)
MM Snowhead Temple SF Dinolfos 1: Map (Snowhead Temple)
MM Snowhead Temple SF Dinolfos 2: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Boss Key: Stray Fairy (Snowhead Temple)
MM Snowhead Temple Boss HC: 10 Arrows (OoT)
MM Snowhead Temple Boss: Odolwa's Remains
Great Bay Temple:
MM Great Bay Temple Entrance Chest: Map (Great Bay Temple)
MM Great Bay Temple SF Water Wheel Platform: Stray Fairy (Great Bay Temple)
MM Great Bay Temple SF Water Wheel Skulltula: Stray Fairy (Great Bay Temple)
MM Great Bay Temple SF Central Room Barrel: Stray Fairy (Great Bay Temple)
MM Great Bay Temple SF Central Room Underwater Pot: Heart Container (OoT)
MM Great Bay Temple Map: Boss Key (Great Bay Temple)
MM Great Bay Temple SF Map Room Pot: Stray Fairy (Great Bay Temple)
MM Great Bay Temple Baba Chest: Stray Fairy (Great Bay Temple)
MM Great Bay Temple Compass: Stray Fairy (Great Bay Temple)
MM Great Bay Temple Compass Room Underwater: Stray Fairy (Great Bay Temple)
MM Great Bay Temple SF Compass Room Pot: 5 Arrows (OoT)
MM Great Bay Temple Ice Arrow: Stray Fairy (Great Bay Temple)
MM Great Bay Temple Boss Key: Stray Fairy (Great Bay Temple)
MM Great Bay Temple Green Pipe 1 Chest: Purple Rupee (OoT)
MM Great Bay Temple Green Pipe 2 Lower Chest: Stray Fairy (Great Bay Temple)
MM Great Bay Temple Green Pipe 2 Upper Chest: Stray Fairy (Great Bay Temple)
MM Great Bay Temple Green Pipe 3 Chest: Stray Fairy (Great Bay Temple)
MM Great Bay Temple SF Green Pipe 3 Barrel: Stray Fairy (Great Bay Temple)
MM Great Bay Temple SF Pre-Boss Above Water: Stray Fairy (Great Bay Temple)
MM Great Bay Temple SF Pre-Boss Underwater: Stray Fairy (Great Bay Temple)
MM Great Bay Temple Boss HC: Compass (Great Bay Temple)
MM Great Bay Temple Boss: Water Medallion
Stone Tower Temple:
MM Stone Tower Temple Entrance Chest: Pendant of Memories
MM Stone Tower Temple Entrance Switch Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Under West Garden Ledge Chest: Piece of Heart (MM)
MM Stone Tower Temple Under West Garden Lava Chest: Green Rupee (OoT)
MM Stone Tower Temple Map: Progressive Strength
MM Stone Tower Temple Center Sun Block Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Center Across Water Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Compass: Small Key (Shadow Temple)
MM Stone Tower Temple Water Sun Switch Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Mirrors Room Center Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Mirrors Room Right Chest: Piece of Heart (OoT)
MM Stone Tower Temple Wind Room Ledge Chest: Compass (Stone Tower Temple)
MM Stone Tower Temple Wind Room Jail Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Light Arrow: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Before Water Bridge Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Water Bridge Chest: Small Key (Woodfall Temple)
MM Stone Tower Temple Inverted Entrance Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Inverted East Lower Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Inverted East Middle Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Inverted East Upper Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Inverted Wizrobe Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Inverted Under Wizrobe Chest: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Inverted Boss Key: Stray Fairy (Stone Tower Temple)
MM Stone Tower Temple Inverted Giant Mask: Boss Key (Stone Tower Temple)
MM Stone Tower Boss HC: Map (Stone Tower Temple)
MM Stone Tower Boss: Kokiri's Emerald
Pirates' Fortress Exterior:
MM Pirate Fortress Entrance Chest 1: Piece of Heart (OoT)
MM Pirate Fortress Entrance Chest 2: Blue Rupee (OoT)
MM Pirate Fortress Entrance Chest 3: 1 Bombchu (MM)
Pirates' Fortress Sewers:
MM Pirate Fortress Sewers Chest 1: Captain's Hat
MM Pirate Fortress Sewers Chest 2: Piece of Heart (MM)
MM Pirate Fortress Sewers Chest 3: 30 Arrows (OoT)
MM Pirate Fortress Sewers HP: Zelda's Lullaby
Pirates' Fortress Interior:
MM Pirate Fortress Interior Lower Chest: Progressive Scale
MM Pirate Fortress Interior Upper Chest: Red Rupee (MM)
MM Pirate Fortress Interior Hookshot: Don Gero's Mask
MM Pirate Fortress Interior Aquarium: Gold Rupee (MM)
MM Pirate Fortress Interior Silver Rupee Chest: Small Key (Fire Temple)
Ikana Castle:
MM Ancient Castle of Ikana HP: Progressive Strength
MM Ancient Castle of Ikana Song Emptiness: Progressive Wallet (OoT)
Beneath the Well:
MM Beneath the Well Keese Chest: Recovery Heart (OoT)
MM Beneath the Well Skulltulla Chest: Piece of Heart (MM)
MM Beneath the Well Cow: Romani Milk
MM Beneath the Well Mirror Shield: Goron Mask (MM)
Secret Shrine:
MM Secret Shrine HP Chest: Blue Rupee (OoT)
MM Secret Shrine Boss 1 Chest: Piece of Heart (MM)
MM Secret Shrine Boss 2 Chest: Recovery Heart (OoT)
MM Secret Shrine Boss 3 Chest: MM_ARROWS_10
MM Secret Shrine Boss 4 Chest: Piece of Heart (MM)
Swamp Spider House:
MM Swamp Spider House Mask of Truth: Blue Rupee (OoT)
Ocean Spider House:
MM Ocean Spider House Wallet: Chicken
MM Ocean Spider House Chest HP: Piece of Heart (MM)
The Moon:
MM Moon Fierce Deity Mask: Bolero of Fire
MM Moon Trial Deku HP: Piece of Heart (MM)
MM Moon Trial Goron HP: Deku Shield
MM Moon Trial Zora HP: Fairy Bow (OoT)
MM Moon Trial Link Chest 1: Red Rupee (MM)
MM Moon Trial Link Chest 2: 5 Bombs (OoT)
MM Moon Trial Link HP: Ice Trap (OoT)

Blue potion locks the left part of the Well, you won't need it to reach the mirror shield chest

To get through the right part of the well, you need beans, fish, big poe then milk. Everything but big poe is obtainable.
big poe is locked behind the left part of the well (which does require the blue potion) or Dampe digging. I think both of these are impossible:
Blue potion wasn't (repeatedly?) obtainable below 99 rupees because of shop scramble.
Dampe digging required captain's hat, which was only obtainable after getting Goron mask, which is at the end of the well.
(I've already beaten the seed, but it was because I used bombchus to obtain something instead of bombs)

The Big Poe is in the right path of well, absolutely not locked by Blue Potion. To reach Big Poe, you need in order:

5 Magic Beans (that you can buy at Bean salesmanman with Deku Mask)
10 Deku Nuts
10 Bombs (with first MM Bomb Bag being in Market shops)
This gives you access to Big Poe, and you can even kill it as you have Magic (also sphere 0), so you can shoot Deku Bubbles.

I'll attach a map of Beneath the Well so you can maybe figure out your error.

Yes, I withdraw the assertion that the seed was impossible.
Big poe is possible without blue potion as it's on the right side and uses obtainable items.


Update issue template

Less an "update" more a "rework"; use headers instead of bolded sections for category headers, a slight reorganization and rewording of the sections, and use checklists to try and get more useful information out of users.

That's because it has to, bot.


wrong calculation of total inverse mass

in function void ParticleContact::resolveInterpenetration(real duration) (pcontacts.cpp around line 100)
you calculate total inverse mass like this
// The movement of each object is based on their inverse mass, so
// total that.
real totalInverseMass = particle[0]->getInverseMass();
if (particle[1]) totalInverseMass += particle[1]->getInverseMass();
I think this is mathematically wrong since 1/mass1 + 1/mass2  is not the same as 1/(mass1+mass2) as I think you mean. Browsing through the code I saw the same calculation in a number of points.

This seems to be related to issue #13


Add more info about browser support and WebGL

Closes #1284 and #1285
Related to https://github.com/CartoDB/support/issues/1938
This adds more information about the requirements to run CARTO VL (WebGL version, required extension...). We can't really add more details on this, nor a specific list for mobile devices. Hope it helps to clarify the requirements.
Once available at Dev Center, we should update: SB 21520692

@elenatorro This is the little change to docs that we were talking about yesterday. It would be nice if it could be part of the 'patch' that includes the fix to the map example.

Hi @ztephm, we have just added a bit more of information to https://carto.com/developers/carto-vl/support/browser-support/ at Dev Center, so we can now update SB 21520692, would you please?


Clarification on which objects are multiprocess/fork safe?

This is likely a dumb/obvious question but is there any guideline on multiprocess/fork safety of various jax objects?
In particular I've noticed code hanging when I accidentally serialized a jax xla devicearray as opposed to a numpy ndarray via python's multiprocessing module.
I'd also be okay with a firm "please don't serialize jax objects and always convert to np ndarray".

In general no JAX objects are safe in the presence of fork(). fork() is fundamentally incompatible with threading, and JAX uses threading internally. If you want to fork() and do anything other than something like exec(), do the fork() before calling into JAX.
I think the current state is "most bets are off if you serialize JAX objects". That's not because we're opposed, but more because it's not something we test and so there are no guarantees. By contrast np.ndarray will certainly work. Does that answer the question?

Thanks for the clarification, that's inline with my expectation. Would be in reasonable to throw an exception upon calling serialization methods (eg. throw in setstate and getstate) for internal jax objects as opposed to having it be silent serialized?


Audio is distorted / stuttering in Firefox on Android

Version: 0.6.4
FF version: 121.1.0
Android version: 13
Device: Galaxy s20 FE 5G
Current behavior:
Audio is distorted and stuttering when playing demo sounds on demo site in FF on Android. Sounds like a Geiger counter.
Expected behavior:
Clean audio with no distortion or stuttering
Steps to reproduce:
Navigate to https://alemangui.github.io/pizzicato/ on FF for android, and play the demos
Other information:
Please see video recording of issue
https://github.com/alemangui/pizzicato/assets/8467401/ce7335b9-e365-427e-be8e-6fc70dfb880e

@alemangui Not sure if this project is still maintained or not, but doesn't look like theres been any activity in a few years. This is an amazing project but its a shame that the audio is so bad in Firefox.

I use FireFox Developer, with this library and have no problems, so I can only ask what audio interrace is in use (I have Zoom U44), which while a class-compliant USB Audio device, is actually a professional audio interface.

@nascent Theres no audio interface, its a mobile phone as you can see in the attached video?


Endpoint parameters not parsed

Hi,
I've found that parameters written at endpoint level are not parsed.
Here is an example
openapi-processor-mapping: v2

options:
  package-name: be.unamur.nuts.web.api
  javadoc: true

openapi: 3.0.2
info:
  title: nuts
  version: '1.0'
  contact: {}
  description: 'Test bug'
servers:
  - url: 'http://localhost:8080'
tags:
  - name: user
    description: Everything about users
paths:
  '/users/{userId}':
    parameters:
      - schema:
          type: integer
        name: userId
        in: path
        required: true
        description: Id of an existing user.
    get:
      summary: Get User Info by User ID
      tags:
        - user
      responses:
        '200':
          description: User Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/User'
              examples:
                Get User Alice Smith:
                  value:
                    id: 142
                    firstName: Alice
                    lastName: Smith
                    email<EMAIL_ADDRESS>                    dateOfBirth: '1997-10-31'
                    emailVerified: true
                    signUpDate: '2019-08-24'
        '404':
          description: User Not Found
      operationId: get-users-userId
      description: Retrieve the information of the user with the matching user ID.

components:
  schemas:
    User:
      title: User
      type: object
      description: ''
      x-examples:
        Alice Smith:
          id: 142
          firstName: Alice
          lastName: Smith
      properties:
        id:
          type: integer
          description: Unique identifier for the given user.
        firstName:
          type: string
          description: The firstname of the user
        lastName:
          type: string
          description: The lastname of the user
      required:
        - lastName
  examples: {}

The result is the following Interface:
public interface UserApi {
    @GetMapping(
        path = {"/users/{userId}"},
        produces = {"application/json"}
    )
    User getUsersUserId();
}

spring processor version: 1.0.0.M20
maven plugin version: 1.0.0.M2
The userId should be used by the function

interesting, this works with the swagger parser but fails with openapi4j.
Workaround maybe <parser>SWAGGER</parser>.
Thanks for reporting.

Thank you
I've tested your workaround with SWAGGER parser.
That works with the version 1.0.0.M20 but I must add another plugin dependency, unless it fails :
<dependency>
    <groupId>com.fasterxml.jackson.dataformat</groupId>
    <artifactId>jackson-dataformat-yaml</artifactId>
</dependency>

If I don't the plugin doesn't find the method com.fasterxml.jackson.dataformat.yaml.YAMLFactory.builder()
With the last spring processor version (2021.1), it doesn't work but that's probably not due to the SWAGGER parser.
The error is that the io/openapiprocessor/api/v1/OpenApiProcessor class is required but missing.

Uhhh :-(
that is probably an issue with the maven plugin. It think it needs an update to work with the 2021 version. That is already high on my todo list.

Cool :smiley: Thank you !

Hi,
published spring 2021.2 and maven-plugin 2021.1.


haskell.compiler.ghc928: init at 9.2.8

Description of changes

Add GHC-9.2.8: https://www.haskell.org/ghc/blog/20230526-ghc-9.2.8-released.html
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

https://gitlab.haskell.org/ghc/ghc/-/compare/ghc-9.2.7-release...ghc-9.2.8-release?from_project_id=1&straight=true

Locally I built haskell.compiler.ghc928 and haskell.packages.ghc928.lens, so there is at least a base-line amount of functionality.


Update iOS headers for React Native 0.40

Also add explicit React-Native version (^0.40) peer dependency to package.json

See https://github.com/facebook/react-native/releases/tag/v0.40.0 for more information on the breaking changes for iOS React Native header imports. Note that this will likely break compatibility with React Native <0.40, which certainly could be problematic for some users. It's up to the maintainer - if <0.40 support is more important, than a separate branch could be made for 0.40+; if keeping up-to-date with React Native's latest is more important, then a note could be added to the README to point <0.40 users to a specific commit/branch before introducing these 0.40 fixes. Publishing releases might also be helpful here, with clear notes on which React Native versions are supported for each release. Thoughts?

Thank you very much indeed for your pull request. Now the package has been updated.


Thanks @Bisstocuz for your contribution!


[Github] #4800 Add field for meta author and use it in frontend

1. Why is this change necessary?
See #4800
2. What does this change do, exactly?
Add a configuration field to set a meta author and use it in the frontend.
3. Describe each step to reproduce the issue or behaviour.
See #4800
4. Please link to the relevant issues (if any).
#4800
5. Checklist

[X] I have rebased my changes to remove merge conflicts
[ ] ~I have written tests and verified that they fail without my change~
[X] I have created a changelog file with all necessary information about my changes
[ ] ~I have written or adjusted the documentation according to my changes~
[ ] ~This change has comments for package types, values, functions, and non-obvious lines of code~
[X] I have read the contribution requirements and fulfill them.

Imported from Github. Please see: https://github.com/shopware/shopware/pull/4968

[public]

FixVersion Change: <IP_ADDRESS>

This issue will be / was solved in Shopware version <IP_ADDRESS>.
[created from NEXT-40034, comment 529651]


toml::de::from_slice crash

Hi!
Here's my code for toml::de::from_str:
extern crate toml;
#[macro_use]
extern crate serde_derive;

use std::{convert, fmt::Debug, fs, io::Read, path, env};

#[derive(Debug, Deserialize)]
struct Config {
    projects: Vec<ProjectConfig>,
}

#[derive(Debug, Deserialize)]
struct ProjectConfig {
    project_home: String,
    project_root: String,
    subroots: Option<Vec<SubrootConfig>>,
}

#[derive(Debug, Deserialize)]
struct SubrootConfig {
    path: String,
}

fn main() {
    // possible path:
    // "foo/bar"
    // "foo/bang"
    /*let subroots_only = r#"
        project_home = "bwah"
        project_root = "my_directory"
        [[subroots]]
        path = "bar"
        [[subroots]]
        path = "bang"
    "#;*/
    let projects = {
        let mut file_path: path::PathBuf = path::PathBuf::new();

        file_path.push(env::current_dir().unwrap().as_path());
        file_path.push("my_file.toml");
        let mut configuration_file: fs::File = fs::OpenOptions::new()
            .read(true)
            .open(file_path.as_path())
            .map_err(|error| panic!("Cannot read the configuration file: '{}'", error))
            .unwrap();
        let mut stringified_content: String = String::new();
        match configuration_file.read_to_string(&mut stringified_content) {
            Ok(bytes) => println!("{} bytes has been appended to buffer.", bytes),
            Err(error) => panic!(
                "
                The data in this stream is not valid UTF-8.\n
                See error: '{}'
                ",
                error
            ),
        }
        stringified_content
    };

    let config_content: Config = toml::from_str(projects.as_str())
        .map_err(|error| panic!("Something went wrong: {}", error))
        .unwrap();
}

Here's the toml file content:
[[projects]]
project_home = "my/home/"
project_root = "my_directory"
[[projects.subroots]]
path = "my/path/file"
[[projects.subroots]]
path = "my/path/file"
[[projects]]
project_home = "another/home/"
project_root = "another_directory"

Result:
246 bytes has been appended to buffer.
----------

Project home: 'my/home/'
Project root: 'my_directory'
Are there subroots?
yup!
Here are the path:
`my/path/file`
`my/path/file`
----------

Project home: 'another/home/'
Project root: 'another_directory'
Are there subroots?
No.
Done!

Works like a charm.
Here's my code for toml::de::from_slice:
extern crate toml;
#[macro_use]
extern crate serde_derive;

use std::{convert, fmt::Debug, fs, io::Read, path, env};

#[derive(Debug, Deserialize)]
struct Config {
    projects: Vec<ProjectConfig>,
}

#[derive(Debug, Deserialize)]
struct ProjectConfig {
    project_home: String,
    project_root: String,
    subroots: Option<Vec<SubrootConfig>>,
}

#[derive(Debug, Deserialize)]
struct SubrootConfig {
    path: String,
}

fn main() {
    // possible path:
    // "foo/bar"
    // "foo/bang"
    /*let subroots_only = r#"
        project_home = "bwah"
        project_root = "my_directory"
        [[subroots]]
        path = "bar"
        [[subroots]]
        path = "bang"
    "#;*/
    let projects = {
        let mut file_path: path::PathBuf = path::PathBuf::new();

        file_path.push(env::current_dir().unwrap().as_path());
        file_path.push("my_file.toml");
        let mut configuration_file: fs::File = fs::OpenOptions::new()
            .read(true)
            .open(file_path.as_path())
            .map_err(|error| panic!("Cannot read the configuration file: '{}'", error))
            .unwrap();
            let mut byte_buffer: Vec<u8> = vec![];
        match configuration_file.read(&mut byte_buffer) {
            Ok(bytes) => println!("{} bytes has been appended to buffer.", bytes),
            Err(error) => panic!(
                "
                The data in this stream is not valid UTF-8.\n
                See error: '{}'
                ",
                error
            ),
        }
        byte_buffer
    };

    let config_content: Config = toml::from_slice(&projects)
        .map_err(|error| panic!("Something went wrong: {}", error))
        .unwrap();
}

Same configuration file.
Result:
0 bytes has been appended to buffer.
thread 'main' panicked at 'Something went wrong: missing field `projects`', src\main.rs:188:26
note: Run with `RUST_BACKTRACE=1` for a backtrace.
error: process didn't exit successfully: `target\debug\struct_generator.exe` (exit code: 101)

I don't understand why I get this error message. Is it a bug?
Meta
$ cargo -V
cargo 1.26.0-nightly (008c36908 2018-04-13)
$ rustc -V
rustc 1.27.0-nightly (7360d6dd6 2018-04-15)

I think instead of configuration_file.read you'll want to use configuration_file.read_to_end, does that work for you?

That mistake... Yes, it does. Thank you!
    Finished dev [unoptimized + debuginfo] target(s) in 1.26 secs
     Running `target\debug\struct_generator.exe`
246 bytes has been appended to buffer.


mobile: Link the test servers with test_extensions

Occasionally I have seen test failures due to missing cluster factory implementation, such as
Didn't find a registered cluster factory implementation for name: 'envoy.cluster.static

This PR fixes the issue by linking the JNI test servers with @envoy_build_config//:test_extensions to force the factory registrations.
Risk Level: low (tests only)
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/assign @abeyad


RHEL 7.7 gdm login fails

Please describe the issue in as much detail as possible, including any errors and traces
Hello, RHEL 7.7, sudo & su work. gdm gui login fails. I notice that
/usr/bin/python3 /usr/lib64/security/howdy/compare.py "my username" stays with 100% CPU 4ever.
Camera is not activated.
No errors in /var/log. How can I troubleshoot?
Howdy version 2.4 (Can't find rpm for 2.5, when i copied 2.5 and overwrited 2.4 didn't work at all)

I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable): RHEL 7.7
Howdy version: howdy-2.4.0-2.el7.x86_64

ok found it, it was selinux


requireNativeComponent: "CameraView" was not found in the UIManager

Issue Description
Hi, I have the next error at try execute a example for read a QR code, someone can help me about this error please.
**Invariant Violation: requireNativeComponent: "CameraView" was not found in the UIManager.
This error is located at:
in CameraView (at CameraKitCamera.android.js:21)
in CameraKitCamera (at CameraKitCameraScreenBase.js:156)
in RCTView (at View.js:44)
in RCTView (at View.js:44)
in CameraScreenBase (at App.js:14)
in RCTView (at View.js:44)
in App (at withExpoRoot.js:22)
in RootErrorBoundary (at withExpoRoot.js:21)
in ExpoRootComponent (at renderApplication.js:34)
in RCTView (at View.js:44)
in RCTView (at View.js:44)
in AppContainer (at renderApplication.js:33)**
Steps to Reproduce / Code Snippets / Screenshots
I use Expo framework for execute de app on device Android

Environment

react : 16.5.0
react-native : https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz,
react-native-camera-kit: 8.0.0,
Platform(s) (iOS, Android, or both?): Android 5.0.1
Device info (Simulator/Device? OS version? Debug/Release?): expo : 32.0.0

For me it was fixed after removing the react-native-camera package

For me it was fixed after removing the react-native-camera package

in my case I don't have installed the react-native-camera package, someone have an any idea

@osloga did u got the solution ? If yes kindly share i am also having the same issue coming.

Hi, I am unable to make react-native-camera-kit work on android
& ios platforms when upgrading to react-native:0.60.1 & haven't installed react-native-camera.
What can be the possible solution?

I had the same problem, and I solved it by running the following console command:

react-native link react-native-camera-kit

I had the same problem, and I solved it by running the following console command:

react-native link react-native-camera-kit

This is also what i use. have you already fixed the issue?

1- react-native link react-native-camera-kit
then rebuild the project and issue will be resolved.


Markdown Preview: Add support for Mermaid diagrams

GitHub added mermaid support out of the box for Markdown:
https://github.com/mermaid-js/mermaid
https://mermaid-js.github.io/mermaid/#/
Adding this to the Markdown Preview will significantly ease the editing of embedded diagrams in VSCode for GitHub documentation.

graph TD
    A[VSCode] -->|Add Mermaid| B(Do diagrams)
    B --> C{Let me think}
    C -->|One| D[Markdown]
    C -->|Two| E[Mermaid]
    C -->|Three| F[Fun]

This VSCode extension already supports it for their own use: https://marketplace.visualstudio.com/items?itemName=dendron.dendron
https://wiki.dendron.so/notes/ba97866b-889f-4ac6-86e7-bb2d97f6e376/

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!


Clarify “Global” computation output

The computation output tables’ “Global” label wasn’t clear to Jess in our 2017-03-27 demo. She asked whether this was “meta analysis” or just an “average.” How can we clarify the output’s methods to users?

@JingMing623 @everner-ds Any thoughts on this? Should we ignore for the demo as we can explain output on a call?

For single-shot and multi-shot, the word 'global' indeed has different meanings.  for single-shot will be meta-analysis result (average), and for multi-shot, it is mega-analysis. It is kind of depending on which algorithm we are using.  If we want to change 'Global' to other words, probably need to link to different algorithm too.

We could temporarily add a tooltip to the “Global” headings to clarify its section’s meaning:

In the future we should provide a way for computation authors to explain their computations’ output in a sentence or two. Perhaps this can go in the computation’s root module.exports:
// computation.js

module.exports = {
  name: 'Multi-Shot Ridge Regression',
  version: '1.0.2',
  descriptions: {
    main: 'Iterative decentralized ridge regression.',
    output: 'Mega-analysis',
  },
};

This could also go in a package.json entry point.

Looks nice! Yes, I agree computation author should provide this information to coinstac

Closing this issue. We can revisit advanced description output in #12.


Actually allow to create new kafka lookups

The problem was that attempting to add a new Kafka-based lookup via API would return 202 ACCEPTED, but the lookups would not actually appear in subsequent queries.
A quick investigation showed that all the other (map and cachedNamespace)  LookupExtractorFactory.replaces() implementations return true for null, but for Kafka it returns false.
With this change, adding a new lookup works fine.

cc @drcrallen, if I am not mistaken.

Great catch @gvsmirnov, thanks for the PR! Would you mind filling out the druid CLA at http://druid.io/community/cla.html ?
After CLA is cleared I'm 👍

👍

Thank you for the quick response. CLA signed.
On Thu, 4 Aug 2016 at 7:19 pm, Nishant<EMAIL_ADDRESS>wrote:

👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/druid-io/druid/pull/3326#issuecomment-237604577, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABbJ2GmYmPArr3G8OV1EJo_NTBngPsYjks5qchD7gaJpZM4JclEw
.

Great thanks!


isfname+=32 breaks escaping for space in options

vim -u NUL -c"set isfname+=32 | filetype plugin on | e 1.pl"
causes following error
Error detected while processing C:\Program Files (x86)\Vim\vim74\ftplugin\perl.vim:
line   18:
E518: Unknown option: -f
Failing config string is
setlocal keywordprg=perldoc\ -f

On Wed, Oct 14, 2015 at 8:59 PM, andrey-starodubtsev <
<EMAIL_ADDRESS>wrote:
vim -u NUL -c"set isfname+=32 | filetype plugin on | e 1.pl"

causes following error
Error detected while processing C:\Program Files
(x86)\Vim\vim74\ftplugin\perl.vim:
line 18:
E518: Unknown option: -f
Failing config string is
setlocal keywordprg=perldoc\ -f

Apparently your perldoc executable is different than the maintainer's — or
mine.
When I run "man perldoc" in my bash shell (on openSUSE Linux) it tells me:
[...]
Examples:
       perldoc -f BuiltinFunction

[...]
OPTIONS
[...]
-f perlfunc
The -f option followed by the name of a perl built-in function
will extract the documentation of this function from perlfunc.
        Example:

              perldoc -f sprintf

[...]
You should report the problem to http://github.com/vim-perl/vim-perl/issues
(the bug reporting URL for that plugin), telling your problem to the
maintainer (i.e. the owners of that group) in as much detail as you can,
including as a minimum

which operating system you are on (including version and any service
packs)
which version of perl and of perldoc you are using (and from where you
downloaded them).
the details of the Vim error you described above.

Best regards,
Tony.

Hi andrey-starodubtsev!
On Mi, 14 Okt 2015, andrey-starodubtsev wrote:

vim -u NUL -c"set isfname+=32 | filetype plugin on | e 1.pl"
causes following error
Error detected while processing C:\Program Files (x86)\Vim\vim74\ftplugin\perl.vim:
line   18:
E518: Unknown option: -f
Failing config string is
setlocal keywordprg=perldoc\ -f

I can reproduce it:
diff --git a/src/option.c b/src/option.c
--- a/src/option.c
+++ b/src/option.c
@@ -4768,7 +4768,8 @@ do_set(arg, opt_flags)
#ifdef BACKSLASH_IN_FILENAME
&& !((flags & P_EXPAND)
&& vim_isfilec(arg[1])

                                          && (arg[1] != '\\'

                                          && ((arg[1] != '\\' &&

                                               arg[1] != ' ')
                                              || (s == newval
                                                  && arg[2] != '\\')))

#endif
Best,
Christian
Die Ziele der Menschen sind Reichtum an Materiellem.
Reichtum an Glück sollte das Ziel sein.
-- Benjamin Stramke

Has this issue been fixed?  I can't reproduce:
$ vim -u NONE -c"set isfname+=32 | filetype plugin on | e 1.pl"
no error

but maybe that's because it's specific to Windows?

seems to be fixed also on windows. Let's close it down.


Fix phpdoc warns

Fixed a few phpdoc warns on the API documentation and phpdoc blocks.

Coverage remained the same at 84.862% when pulling 3a487c2570af18d39845eaf0e752bfedeee21738 on feature/fix-phpdoc-warns into 8ec07b6fa35d4a7c8e13999312b1e47c52f3dabf on develop.

Coverage remained the same at 84.862% when pulling f619b2ac4e7b7cf0f43d90ab3dcfb711045aea95 on feature/fix-phpdoc-warns into 11245563f194be421b757d44fea30182678907d5 on develop.


Url patterns

Fixes some issues in the url patterns PR.

Changes mini-templating to use {name} instead of ${name}.
Merges url-pattern into a single json property.
Makes excluded files page respect url pattern.
Introduces common.js file to share between pages.

@paulwellnerbou I changed a few things from #76. Objections?

I went ahead and wrapped the stuff in common.js in its own namespace.


Add ability to hijack through proxy

Part of docker/docker#18373
ping @calavera @nathanleclaire

LGTM

LGTM


Display activity notifications

[ ] Add bell icon to link to a user's notifications on the dashboard
[ ] Explore idea of marking read
[ ] Add inside turbo_tag to facilitate display in dropdown in menu
[ ] Group MessageReceived notifications

@tillprochaska Some questions I have about the frontend in general and this PR include:

Font-size, the mockups seem to use much bigger text than we currently have set for h1, h2. Should we always respect these font-sizes to keep consistency in the project, or should I try to make it most similar to the design?

Spacing - same question. --spacing-unit-xl does not appear to be enough spacing at the top of the page. Should I be adding calc(1.5 x ...)or should we only be using pre-set variables/adding new ones.

Component-only views - I see we have a PageHeader component, which I originally used, but it has a gray background and padding that I don't want. I added my own HTML, but that meant adding a dashboard/index.css file and importing it. From looking at the code, I think you don't do this anywhere, but favor a component-only solution. So, should I refactor the PageHeader to accept a gray/white background, with/without padding, etc?

Font-size, the mockups seem to use much bigger text than we currently have set for h1, h2. Should we always respect these font-sizes to keep consistency in the project, or should I try to make it most similar to the design?

The screendesign/mockups aren’t meant to be implemented pixel perfect and they might not be 100% consistent/systematic in themselves. Use different sizing and spacing if necessary/where you see fit. In general, I’d always prefer consistency and a systematic.

Spacing - same question. --spacing-unit-xl does not appear to be enough spacing at the top of the page. Should I be adding calc(1.5 x ...)or should we only be using pre-set variables/adding new ones.

I tend to use multiples of the base spacing unit if the predefined are not enough. But you can also add --spacing-unit-xxl, --spacing-unit-xxs etc. if you’d prefer!

I added my own HTML, but that meant adding a dashboard/index.css file and importing it. From looking at the code, I think you don't do this anywhere, but favor a component-only solution.

Yes, I’d prefer scoping all styles to specific components, as in my experience, it helps reducing unintended side effects.

So, should I refactor the PageHeader to accept a gray/white background, with/without padding, etc?

The questions refers to this header, right?

I’d probably not try to adjust the PageHeader component to fit this case. Maybe you could just use the Flex utility component? Something like this might work, although I haven’t tested it:
<header>
  <%= c('flex', style: :spaceBetween) do %>
    <%= c('heading', tag: :h1) { 'Lorem Ipsum' } %>
    <%= c('button', …) %>
  <% end %>
</header>

@mattwr18 Enhancements that have been prioritized:

Change the link "Zur Frage" to "Zur Antwort" (or "Zu den Antworten" once the messages are grouped). We already support anchor links for individual messages, i.e. we’d only need to add the respective hash to the link, e.g. /requests/123#message-456.

There are two main problems: Editors are overwhelmed by the amount of notifications and they’d like to see at a glance whether another editor has already replied. As this is kind of a difficult problem. We’d like to implement grouping of notifications first, get more feedback, and see if how to solve the second problem from there.

Regarding grouping, I was thinking if adding a separate notification type for replies by editors and grouping only successive notifications of the same type might solve this issue. But I haven’t done any testing around it.
Letzte Aktivität

Contributor C and Contributor D have replied to Question A.

Editor B has replied to Contributor A and three others.

Contributor A and three others have replied to Question A.

Note how the first and the second notification are both about Question A and have the same type (new reply by contributor), but they aren’t grouped as a single item because something else happened in between. This might make it easier for people to understand the chronological order, and might give them enough insight to answer the question "Did someone else from my team already take care of these new messages."


jquery UI

Eliminate jquery ui??  We are using draggable... which is not mobile friendly and shake which does not really add value.  Need to implement mobile dragging I guess.

bump

We know ... I think this is the same as issue #20 ... closing this... we know!


Update ml_beginners.md

Fix a couple of small typos

This change is

CLA complete

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


no public type provider classes were found

I get this error with small script files on .NET Framework (not Core).
I use the FCS with my own WPF editor. As a standalone Editor App the type provider works fine. All good.
But when I host my F# Editor and FCS inside my CAD app (Rhinoceros3D)  I get this error message.
The same error is shown in by the FsChecker as well as by FSharp Interactive.
What is different in the hosted context that would trigger this error ?
I am using FCS 23.0.3
ExcelProvider.0.8.2\lib\ExcelProvider.dll' has assembly level attribute 'Microsoft.FSharp.Core.CompilerServices.TypeProviderAssemblyAttribute' but no public type provider classes were found

This issue seem to be related to Excel provider.
FSharp.Data Provider works fine in hosted context too.

raised here https://github.com/fsprojects/ExcelProvider/issues/54