paperless-ng: pikepdf import error

The addon is not working. Installed without any changes it gives an pikepdf import error when you try to upload files. See link at the end which describes the same error.
Also the links to paperless-ng in about actually point to qbittorrent.
Also tried to use another OCR language but doesn't seem to support it. Tried nld and dut.
https://issueexplorer.com/issue/linuxserver/docker-paperless-ng/8

Hello, thanks I pushed a new version that adds the code you linked to that updates pikepdf. Let me know how it goes!
Thanks for reporting the link also I've changed it

Nice! Didn't expect it to be picked up this quick 😉
I tested but unfortunately it doesn't work yet. I first tested after upgrading with uploading a document. I got the same error. To be sure I deleted the addon, deleted all data/config files and installed the addon again. Again with uploading a file I got the same error. If case it matters, I'm using the 64-bit version of Home Assistant on a RPi4B. I see that it pulled and used the following docker image: linuxserver/paperless-ng:arm64v8-latest
I checked the addon log and I think pikopdf is not actually being installed/updated. Here is a fragment from the addon log:
Setting up python3.8-dev (3.8.10-0ubuntu1~20.04.2) ...
Setting up g++ (4:9.3.0-1ubuntu2) ...
update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode
update-alternatives: warning: skip creation of /usr/share/man/man1/c++.1.gz because associated file /usr/share/man/man1/g++.1.gz (of link group c++) doesn't exist
Setting up build-essential (12.8ubuntu1.1) ...
Setting up libalgorithm-diff-xs-perl (0.04-6) ...
Setting up libalgorithm-merge-perl (0.08-3) ...
Setting up python3-dev (3.8.2-0ubuntu2) ...
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
/sbin/ldconfig.real: /usr/local/lib/libjbig2enc.so.0 is not a symbolic link

/var/run/s6/etc/cont-init.d/91-pikepdf.sh: line 9: pip: command not found
... success!
[cont-init.d] 91-pikepdf.sh: exited 0.
[cont-init.d] 92-local_mounts.sh: executing...
[cont-init.d] 92-local_mounts.sh: exited 0.
[cont-init.d] 92-smb_mounts.sh: executing...
[cont-init.d] 92-smb_mounts.sh: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services

And the error as displayed within paperless-ng under failed tasks in the admin page:
pikepdf's extension library failed to import : Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/pikepdf/__init__.py", line 13, in <module>
from . import _qpdf
ImportError: /usr/local/lib/python3.8/dist-packages/pikepdf/_qpdf.cpython-38-aarch64-linux-gnu.so: undefined symbol: _ZN20QPDFPageObjectHelper16placeFormXObjectE16QPDFObjectHandleRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS0_9RectangleEbbb

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/django_q/cluster.py", line 432, in worker
res = f(*task["args"], **task["kwargs"])
File "/app/paperless/src/documents/tasks.py", line 74, in consume_file
document = Consumer().try_consume_file(
File "/app/paperless/src/documents/consumer.py", line 248, in try_consume_file
document_parser.parse(self.path, mime_type, self.filename)
File "/app/paperless/src/paperless_tesseract/parsers.py", line 230, in parse
import ocrmypdf
File "/usr/local/lib/python3.8/dist-packages/ocrmypdf/__init__.py", line 10, in <module>
from ocrmypdf import helpers, hocrtransform, leptonica, pdfa, pdfinfo
File "/usr/local/lib/python3.8/dist-packages/ocrmypdf/helpers.py", line 22, in <module>
import pikepdf
File "/usr/local/lib/python3.8/dist-packages/pikepdf/__init__.py", line 16, in <module>
raise ImportError(_msg) from _e
ImportError: pikepdf's extension library failed to import

Thanks for the very detailed troubleshooting info. I'm not with my system right now so can't test straight away! I see the key error in the new script is "pip: command not found", I'll add pip and push a new version :) probably tomorrow I'll check a bit more if it works :)

I've also cleaned the pikepdf install script so only errors are verbose. Hopefully it will be clearer to read. I don't have access to my computer for the moment but pikepdf seems to update.

Nice! I upgraded and tested. It works now! I did see some errors in the addon log however and seem to occur each time you start the addon. The full log is below. I can't determine if anything should be fixed or not.
Suggestion to extend documentation
One small suggestion is to add the TZ addon option. It's not stated. Apparently I can set this to Europe/Amsterdam so that it uses the correct timezone for me ;)
OCR multi language support
I tested some more and apparently only english OCR is included in the package. If I try to change eng to nld in the paperless-ng config file I get the below error while starting the addon;
SystemCheckError: System check identified some issues:
ERRORS:
?: The selected ocr language nld is not installed. Paperless cannot OCR your documents without it. Please fix PAPERLESS_OCR_LANGUAGE.

I tried searching on how to add additional OCR languages and found as below. Can you do anything with this and add (configurable) multilanguage support?

linuxserver seems to have an addon docker that can be used. It would mean adding two variables to the environment to configure; https://github.com/linuxserver/docker-mods/tree/papermerge-multilangocr
paperless-ng seems to use OCRmyPDF. If following the link it mentions additional languages can be installed. Maybe this is an option; https://paperless-ng.readthedocs.io/en/latest/configuration.html#ocr-settings
The OCR language packs are also mentioned in the bare metal install notes; https://paperless-ng.readthedocs.io/en/latest/setup.html#bare-metal-route

Where to find the folders
Sorry for all the questions. Last one ;) The documentation states that paperless-ng users 3 folders. I looked but cannot find them anywhere in the home assistant shares or on the file system. Do you know where things are stored now? https://paperless-ng.readthedocs.io/en/latest/setup.html#bare-metal-route
Output of full addon log still containing some errors
You are running the latest version of this add-on.
 System: Home Assistant OS 7.0  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.12.3
 Home Assistant Supervisor: 2021.12.2
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
 https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing...
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 10-adduser: executing...
-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/
Brought to you by linuxserver.io
-------------------------------------
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    0
User gid:    0
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 50-config: executing...
Operations to perform:
  Apply all migrations: admin, auth, authtoken, contenttypes, django_q, documents, paperless_mail, sessions
Running migrations:
  No migrations to apply.
[cont-init.d] 50-config: exited 0.
[cont-init.d] 70-aliases: executing...
[cont-init.d] 70-aliases: exited 0.
[cont-init.d] 90-config_yaml.sh: executing...
Using config file found in /config/addons_config/paperless_ng/config.yaml
Config file is a valid yaml
[00:04:56] INFO: Starting the app with the variables in in /config/addons_config/paperless_ng/config.yaml
PAPERLESS_OCR_LANGUAGE=eng
PAPERLESS_OCR_MODE=skip
[cont-init.d] 90-config_yaml.sh: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 91-pikepdf.sh: executing...
Installing pikepdf...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/aarch64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/aarch64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7, <> line 76.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
... success!
[cont-init.d] 91-pikepdf.sh: exited 0.
[cont-init.d] 92-local_mounts.sh: executing...
[cont-init.d] 92-local_mounts.sh: exited 0.
[cont-init.d] 92-smb_mounts.sh: executing...
[cont-init.d] 92-smb_mounts.sh: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
Waiting for redis to become available...
Waiting for redis to become available...
[services.d] done.
Waiting for redis to become available...
1667:C 22 Dec 2021 00:10:08.733 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1667:C 22 Dec 2021 00:10:08.733 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=1667, just started
1667:C 22 Dec 2021 00:10:08.733 # Configuration loaded
1667:M 22 Dec 2021 00:10:08.766 * Running mode=standalone, port=6379.
1667:M 22 Dec 2021 00:10:08.766 # Server initialized
1667:M 22 Dec 2021 00:10:08.767 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1667:M 22 Dec 2021 00:10:08.768 * Ready to accept connections
[2021-12-21 23:10:20 +0000] [1669] [INFO] Starting gunicorn 20.1.0
[2021-12-21 23:10:20 +0000] [1669] [INFO] Listening at: http://<IP_ADDRESS>:8000 (1669)
[2021-12-21 23:10:20 +0000] [1669] [INFO] Using worker: paperless.workers.ConfigurableWorker
[2021-12-21 23:10:20 +0000] [1669] [INFO] Server is ready. Spawning workers
[2021-12-21 23:10:24,143] [INFO] [paperless.management.consumer] Using inotify to watch directory for changes: /data/consume
23:10:24 [Q] INFO Q Cluster blossom-mirror-steak-vegan starting.
23:10:24 [Q] INFO Process-1:1 ready for work at 1723
23:10:24 [Q] INFO Process-1:2 ready for work at 1724
23:10:24 [Q] INFO Process-1:3 monitoring at 1725
23:10:24 [Q] INFO Process-1 guarding cluster blossom-mirror-steak-vegan
23:10:24 [Q] INFO Process-1:4 pushing tasks at 1726
23:10:24 [Q] INFO Q Cluster blossom-mirror-steak-vegan running.
23:10:54 [Q] INFO Enqueued 1
23:10:54 [Q] INFO Process-1 created a task from schedule [Check all e-mail accounts]
23:10:54 [Q] INFO Process-1:1 processing [november-nitrogen-harry-bakerloo]
23:10:54 [Q] INFO Process-1:1 stopped doing work
23:10:54 [Q] INFO Processed [november-nitrogen-harry-bakerloo]
23:10:54 [Q] INFO recycled worker Process-1:1
23:10:54 [Q] INFO Process-1:5 ready for work at 1729
23:12:52 [Q] INFO Enqueued 1
23:12:52 [Q] INFO Process-1:2 processing [Clean Tenso stoomuitlaat verstopt.pdf]
[2021-12-21 23:12:52,953] [INFO] [paperless.consumer] Consuming Clean Tenso stoomuitlaat verstopt.pdf
[2021-12-21 23:13:36,420] [WARNING] [ocrmypdf._validation] The output file size is 1.49× larger than the input file.
Possible reasons for this include:
The argument --deskew was issued, causing transcoding.
PDF/A conversion was enabled. (Try `--output-type pdf`.)
[2021-12-21 23:13:51,492] [INFO] [paperless.consumer] Document 2000-12-15 Clean Tenso stoomuitlaat verstopt consumption finished
23:13:51 [Q] INFO Process-1:2 stopped doing work
23:13:51 [Q] INFO Processed [Clean Tenso stoomuitlaat verstopt.pdf]
23:13:51 [Q] INFO recycled worker Process-1:2
23:13:51 [Q] INFO Process-1:6 ready for work at 1814

Thanks for the detailed informations!

[] 1. Logs errors
Indeed this is just because it installs apps in a headless mode, without supervision. I've pushed the apps install to the dockerfile, it will remove the errors.
[] 2. Tz
Thanks, I'll add that!
[] 3. Multi ocr
I think it is natively taken into account using the env variables that can be defined in the config.yaml file (see addon options) based on the list here : https://paperless-ng.readthedocs.io/en/latest/configuration.html. Based on what you wrote, I think setting the value is not enough to have it installed. I'll check the linuxserver code, or I'll use my own developed for nextcloud
[] 4. Folders : I'll complete the post Tomorrow

Language installation confirmed working with fra (post above updated)

I checked but the env variable is actually PAPERLESS_OCR_LANGUAGE and not PAPERLESS_OCR_LANGUAGES (plural) 😉 If you remove the S at the end you'll find you'll experience the same errors. I also tried with only nld in there. Same error. But with only eng it doesn't give any errors.
dpkg-preconfigure: unable to re-open stdin:
... success!
[cont-init.d] 91-pikepdf.sh: exited 0.
[cont-init.d] 92-local_mounts.sh: executing...
[cont-init.d] 92-local_mounts.sh: exited 0.
[cont-init.d] 92-smb_mounts.sh: executing...
[cont-init.d] 92-smb_mounts.sh: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Waiting for redis to become available...
Waiting for redis to become available...
Waiting for redis to become available...
1682:C 22 Dec 2021 15:30:11.349 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1682:C 22 Dec 2021 15:30:11.350 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=1682, just started
1682:C 22 Dec 2021 15:30:11.350 # Configuration loaded
1682:M 22 Dec 2021 15:30:11.373 * Running mode=standalone, port=6379.
1682:M 22 Dec 2021 15:30:11.373 # Server initialized
1682:M 22 Dec 2021 15:30:11.373 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1682:M 22 Dec 2021 15:30:11.375 * Ready to accept connections
[2021-12-22 14:30:23 +0000] [1681] [INFO] Starting gunicorn 20.1.0
[2021-12-22 14:30:23 +0000] [1681] [INFO] Listening at: http://<IP_ADDRESS>:8000 (1681)
[2021-12-22 14:30:23 +0000] [1681] [INFO] Using worker: paperless.workers.ConfigurableWorker
[2021-12-22 14:30:23 +0000] [1681] [INFO] Server is ready. Spawning workers
SystemCheckError: System check identified some issues:
ERRORS:
?: The selected ocr language eng,nld is not installed. Paperless cannot OCR your documents without it. Please fix PAPERLESS_OCR_LANGUAGE.
SystemCheckError: System check identified some issues:

Hi, my instructions were unclear : actually there is 2 steps now :

Language installation : donc through an addo' option. I've added a new addon option named OCRLANG in which you need to put "eng,nld"
Language selection : the PAPERLESS_OCR_LANGUAGE env variable in config.yaml

Setting both these options should allow installing and using nld! For the moment I've tested with fra and it worked

Hi, my instructions were unclear : actually there is 2 steps now :

Language installation : donc through an addon option. I've added a new addon option named OCRLANG in which you need to put "eng,nld" (since addon version 1.5.0-5)
Language selection : the PAPERLESS_OCR_LANGUAGE env variable in config.yaml, using + separated trigrams (you have a comma). From the documentation :

PAPERLESS_OCR_LANGUAGE
This can be a combination of multiple languages such as deu+eng, in which case tesseract will use whatever language matches best. Keep in mind that tesseract uses much more cpu time with multiple languages enabled.

Setting both these options should allow installing and using nld! For the moment I've tested with fra and it worked

Ah ok. I did both and started after upgrading but there seems to be an error with pikopdf now. See below. To be sure I deleted and reinstalled the addon also but still the same.
[23:06:41] INFO: Starting the app with the variables in in /config/addons_config/paperless_ng/config.yaml
PAPERLESS_OCR_LANGUAGE=eng+nld
PAPERLESS_OCR_MODE=skip
[cont-init.d] 90-config_yaml.sh: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 91-pikepdf.sh: executing...
Installing pikepdf...
Usage:
  pip install [options] <requirement specifier> [package-index-options] ...
  pip install [options] -r <requirements file> [package-index-options] ...
  pip install [options] [-e] <vcs project url> ...
  pip install [options] [-e] <local project path> ...
  pip install [options] <archive url/path> ...
no such option: -y

Argh a typo... I've pushed a new version that solves that... The key issue is that I have an rpi3b so really low ram I can't really test the builds before pushing to github :) or it would be in a big week.

No problem. I really appreciate your quick responses. I don't mind waiting until you can look at it with your own system. I tested again after upgrading but it still doesn't work. Since you mentioned it works with eng,fra I tried that and also that doesn't seem to work for me.
I set the addon options as you said with eng,fra as OCRLANG:

And here is the addon log where you see I have eng+fra set in the config. But it seems it cannot find FRA. For ENG I see it being installed but no mention of that for FRA either.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-aaa_dockerfile_backup.sh: executing...
[cont-init.d] 00-aaa_dockerfile_backup.sh: exited 0.
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
 Add-on: Paperless NG
 scan, index and archive all your physical documents
-----------------------------------------------------------
 Add-on version: 1.5.0-6
 You are running the latest version of this add-on.
 System: Home Assistant OS 7.0  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.12.4
 Home Assistant Supervisor: 2021.12.2
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
 https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing...
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 10-adduser: executing...
-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/
Brought to you by linuxserver.io
-------------------------------------
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    0
User gid:    0
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 50-config: executing...
Operations to perform:
  Apply all migrations: admin, auth, authtoken, contenttypes, django_q, documents, paperless_mail, sessions
Running migrations:
  No migrations to apply.
[cont-init.d] 50-config: exited 0.
[cont-init.d] 70-aliases: executing...
[cont-init.d] 70-aliases: exited 0.
[cont-init.d] 90-config_yaml.sh: executing...
Using config file found in /config/addons_config/paperless_ng/config.yaml
Config file is a valid yaml
[13:06:47] INFO: Starting the app with the variables in in /config/addons_config/paperless_ng/config.yaml
PAPERLESS_OCR_LANGUAGE=eng+fra
PAPERLESS_OCR_MODE=skip
[cont-init.d] 90-config_yaml.sh: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 91-pikepdf.sh: executing...
Installing pikepdf...
... success!
[cont-init.d] 91-pikepdf.sh: exited 0.
[cont-init.d] 92-local_mounts.sh: executing...
[cont-init.d] 92-local_mounts.sh: exited 0.
[cont-init.d] 92-smb_mounts.sh: executing...
[cont-init.d] 92-smb_mounts.sh: exited 0.
[cont-init.d] 93-multiocr.sh: executing...
OCRLANG variable is set, processing the language packages
installing tesseract-ocr-eng
Reading package lists...
Building dependency tree...
Reading state information...
tesseract-ocr-eng is already the newest version (1:4.00~git30-7274cfa-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
/var/run/s6/etc/cont-init.d/93-multiocr.sh: line 14: cd: /usr/share/tessdata: No such file or directory
[cont-init.d] 93-multiocr.sh: exited 1.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Waiting for redis to become available...
Waiting for redis to become available...
Waiting for redis to become available...
1169:C 23 Dec 2021 13:11:24.314 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1169:C 23 Dec 2021 13:11:24.314 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=1169, just started
1169:C 23 Dec 2021 13:11:24.314 # Configuration loaded
1169:M 23 Dec 2021 13:11:24.338 * Running mode=standalone, port=6379.
1169:M 23 Dec 2021 13:11:24.338 # Server initialized
1169:M 23 Dec 2021 13:11:24.338 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1169:M 23 Dec 2021 13:11:24.339 * Ready to accept connections
[2021-12-23 12:11:36 +0000] [1171] [INFO] Starting gunicorn 20.1.0
[2021-12-23 12:11:36 +0000] [1171] [INFO] Listening at: http://<IP_ADDRESS>:8000 (1171)
[2021-12-23 12:11:36 +0000] [1171] [INFO] Using worker: paperless.workers.ConfigurableWorker
[2021-12-23 12:11:36 +0000] [1171] [INFO] Server is ready. Spawning workers
SystemCheckError: System check identified some issues:
ERRORS:
?: The selected ocr language fra is not installed. Paperless cannot OCR your documents without it. Please fix PAPERLESS_OCR_LANGUAGE.
SystemCheckError: System check identified some issues:
ERRORS:
?: The selected ocr language fra is not installed. Paperless cannot OCR your documents without it. Please fix PAPERLESS_OCR_LANGUAGE.
Waiting for redis to become available...
Waiting for redis to become available...
SystemCheckError: System check identified some issues:
ERRORS:
?: The selected ocr language fra is not installed. Paperless cannot OCR your documents without it. Please fix PAPERLESS_OCR_LANGUAGE.
SystemCheckError: System check identified some issues:
ERRORS:
?: The selected ocr language fra is not installed. Paperless cannot OCR your documents without it. Please fix PAPERLESS_OCR_LANGUAGE.
Waiting for redis to become available...
Waiting for redis to become available...

Another typo corrected, I've tried with eng,fra as addon option and it seemed to work, there is not anymore the error message ;) I'll check a bit more in 2 days

Hi, had you have time to test it? I've just installed and tested it both fra & import seem to work

sorry, due to the holidays I didn't get to it. I've tested and it works! I also tried your papermerge addon and that one also works. still comparing solutions. I can now test which one works best. Do you by any chance also take addon requests? I came across docspell which also seems a good competitor. Somebody even made the config for use with portainer; https://github.com/olaxe/docspell/tree/main/home-assistant
While testing the addons I am still wondering where files actually go. I see mentions in the logs that folders are created but besides the paperless-ng config file I don't see anything else created for paperless-ng nor papermerge in the usual folders; /config, /addons, /share.

Hi, unless I'm mistaken, folders can be modified from the user interface. The data dir, in which files are uploaded, should be in : PAPERLESS_DATA_DIR=/config/addons_config/paperless_ng
I'm not too keen to add new addons if their function overlaps with existing ones. Especially, this one has only an image for arm64 and amd64, it's image has not been updated for 9m on dockerhub. And seeing that the owner went through the trouble of creating a docker compose for HA, I would think it would be easier for him to make an addon directly. Although indeed it does look good :) honestly I'm just using onedrive, it is just so convenient... Or nextcloud to have ocr, mobile apps and a full environnement.

Initial issue solved

Thanks I'll test out where files go and such while comparing them all. And you are totally right! I managed to install and configure it so I can compare it with paperless_ng and papermerge. And thanks for mentioning nextcloud! I didn't even know it existed. I'm definitely going to check it out for comparison! Looking through all your addons now and it's like a swiss army package 😁😉 !!! Very handy addons which covers functionality I still want to explore. If there are any issues, should I create a new issue for each independent addon or what is your preference? I'll be trying out a lot of them 🥳

Thanks for the feedback! It's better to create individual issues in github, mentioning each time the addon and full addon log ;) and sometime restarting the addon can help in case the first run creates some needed files
Have fun!


Please revert to displaying code by default when navigating to deno.land URLs

I loved being able to click on a link and look directly at code.
But with the new update, there is a structured docs type page, with examples how to import.
E.g. for my own modules<EMAIL_ADDRESS>One of the awesome things about deno is that errors give URLs you can click on and directly see the code in question. The developer process is phenomenal.
The new structured view I can see as helpful to some people, but it would be great to be opt-in, or maybe a side bar, but having the code itself front and center on clicking a link is IMO ideal for most of the time most people visit (obv I am biased and have zero data to back this up, just a hunch).
Right now, I have to click an extra button to get to the code. It sounds like not much, but when developing, debugging, understanding, it's an annoying extra click over and over.
BTW this is a great set of tools, and I am a huge fan, if "fan" is the right word. Keep up the awesomeness!!!!

Thanks for the feedback.
The reasoning behind the change is that scanning 1000 line of code for information isn't very useful, especially when trying to use a 3rd party module.  Having a documentation first view makes things easier for people to understand when trying to consume 3rd party code.  Not everyone has a compiler in their head, and even if they had one, reading code isn't the most effective way to figure out how to deal with it.
We make sure that when you are clicking on a stack trace, you get to the specific line, for example [https://deno.land/x/cloudseed@v0.0.20/graphql/generate.ts:37:12][https://deno.land/x/cloudseed@v0.0.20/graphql/generate.ts:37:12].  Outside of that, intelligent editors which leverage the Deno language service have the ability to go to source on third party modules and have them available in the editor, which is a much better way to view source code.
Also there is a lot of precedent for "documentation first" views of code.  Both GoLang and docs.rs provide a documentation first view of the code.
If you need a richer source view, then deno.land/x is never going to meet your needs and it would be a lot better to browse the code in the source control website that publishes it. GitHub is designed for viewing code.  deno.land/x was designed to provide information about 3rd party modules that can be consumed by Deno.  The documentation view fits that better.
We realise a lot of 3rd party packages aren't taking advantage of the rich documentation, partly because there hasn't been anything there to see.  We will add a section to the manual on how to best ensure your JSDoc works well.  In the specific example you provided, in generate.ts, if you were to add the @module tag to the JSDoc block, you would get a lot better documentation for that module on the site:
/**
 * VERY OPINIONATED SCRIPT, NOT DESIGNED FOR GENERAL USE OUTSIDE OF CLOUDSEED GRAPHQL TYPES GENERATION
 * Runs npm @graphql-codegen to generate graphql bindings from
 * a running graphql server with the default settings:
 * - src/graphql/queries.graphql (contain all your queries)
 * - src/graphql/generated/types (generated)
 * This is used in multiple repositories, so capture in a deno script
 *
 * @module
 */

We know that it will take a while for module authors to adjust, but defaulting to a source view will sadly, not politely force people to improve their documentation.

Got it. Thank you for the write up on the reasoning, it makes a lot of sense.
And thanks for the documentation tip, will start adding to my code!

The new module landing page has landed, which has distinct links for a doc view and a source view, so https://deno.land/x/cloudseed gives a whole package overview.
We still think having a documentation first view is a better default than a source view. If you do switch over to the source view it does stay in that view, but we do think the default of a direct link being a documentation view is better for more users in more cases, even though there will be a period of adjustment.
So I think for this specific feedback, there isn't anything actionable, so I am going to close, but feel free to provide further feedback as we evolve this space.


Use stronger RSA keys for peer ids

This bumps the key size for our peer ids to 2048 bits and adds new pre-generated testing ids.

:+1:


Unexpected error: smartdnsblock failed

Test procedure

Install Windows 11 in a virtual machine
Install vc_redist.x64.exe
Install Outline Manager
Configure Ubuntu 20.04 server with Docker preinstalled
Paste API URL into Outline Manager
Install Outline Client
Add server access key to client
Attempt to connect from client to server

Expected result
Client connects to server
Actual result
Unexpected error.
Sorry, an unexpected error occurred.
Wireshark shows TCP exchange with server, followed by 1 UDP packet from client to server, followed by 1 UDP packet back from server to client.
Windows Event Viewer, Windows Logs > Application, shows:
Failed to handle connection: System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
at System.IO.Pipes.PipeStream.BeginWriteCore(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback callback, Object state)
at System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at OutlineService.OutlineService.WriteResponse(ServiceResponse response)
at OutlineService.OutlineService.HandleConnection(IAsyncResult result)
preceded by:
request failed: could not start smartdnsblock: smartdnsblock failed (stdout: , (stderr: )
Workaround
Install Shadowsocks on server:
wget https://raw.githubusercontent.com/teddysun/shadowsocks_install/master/shadowsocks-libev-debian.sh
chmod +x shadowsocks-libev-debian.sh
./shadowsocks-libev-debian.sh
Install Shadowsocks on client from https://github.com/shadowsocks/shadowsocks-windows/releases
Result of Workaround
Shadowsocks works fine.

As per https://github.com/Jigsaw-Code/outline-client/issues/782 it is vc_redist.x86.exe that must be installed to fix the problem, even on a 64-bit machine.


Improvements to line labeling

[ ] Position a label at the best position on the line
[x] Multiple bounding boxes for a single label
[ ] line can be labeled multiple times
[ ] Shields for highways are positioned reasonably; can have multiple

Current problem areas:
Labels should be positioned on the actual geometry, not a straight line: Chuo Expressway @ #17/35.66661/139.55926

When a label is repeated, it should not be too close to the next segment of the same feature:
Some places in Denver have way too few road labels: (straight unlabeled roads)


Update configuration.md

The description of MaxSendMessageSize and MaxReceiveMessageSize do not accurately describe whether the it's a client to server request or a server to client response

These settings are for server configuration. They control the server side.
The new descriptions in the PR aren't accurate.


Add shadow DOM example

Added an example that uses shadow DOM.
Used the Mozilla example: https://github.com/mdn/web-components-examples/tree/master/simple-template

Keen to have the shadowDOM example. Please do the review and merge this pull-reqeust someone.

Bump :)

@tourdedave this one would be really nice to have. Your site is a great collection of examples for Selenium samples and ShadowDOM would certainly be a great addition.

Sorry for the delay in getting this merged. Thanks! 💯


Black glTF models

I believe there have been reports of glTF models showing up black in Cesium on the forum (if you know of any please comment here).  There is a reported issue in Three.js on some hardware, https://github.com/mrdoob/three.js/issues/8381.  If this is the generated shaders, we will either fix the shaders or workaround them in JavaScript.
This could affect all of our lighting code, not just glTF models.

https://groups.google.com/d/msg/cesium-dev/nlWiGXaaDz4/m1sVlxajCAAJ
https://groups.google.com/d/msg/cesium-dev/FFKF3N77FmQ/Edpa3y3IBAAJ

Also seen here: https://groups.google.com/forum/?hl=en#!topic/cesium-dev/q7U3dSjFDRk
sail_boat.gltf.txt

I'll take a look at that one since it went through the obj converter.

I have updated the the Google Groups forum topic with the original OBJ file as well, as well as other details.

Thanks I'll check it out!

Apparently the OBJ file was corrupt, in my case.  Sean Lilley had a look and said the following:

It looks like the website exports a somewhat broken obj file. The faces reference normals that don't seem to exist and the obj doesn't load correctly in any programs I've tried. I was able to clean up the obj a bit and export it correctly, but I would bring this issue up with tinkercad.

Also reported here: https://groups.google.com/forum/?hl=en#!topic/cesium-dev/WNkjQNihsfY

Brought up on the forum: https://groups.google.com/forum/#!topic/cesium-dev/k4zWR2R7shY

The dark/black models should be all gone from the May release of Cesium 1.45.

Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/d/msg/cesium-dev/nlWiGXaaDz4/m1sVlxajCAAJ
https://groups.google.com/d/msg/cesium-dev/FFKF3N77FmQ/Edpa3y3IBAAJ
https://groups.google.com/forum/?hl=en#!topic/cesium-dev/q7U3dSjFDRk
https://groups.google.com/forum/?hl=en#!topic/cesium-dev/WNkjQNihsfY
https://groups.google.com/forum/#!topic/cesium-dev/k4zWR2R7shY
If this issue affects any of these threads, please post a comment like the following:

The issue at https://github.com/AnalyticalGraphicsInc/cesium/issues/3737 has just been closed and may resolve your issue. Look for the change in the next stable release of Cesium or get it now in the master branch on GitHub https://github.com/AnalyticalGraphicsInc/cesium.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:


Uniswap universal router support

Found this on reddit today: https://github.com/Elnaril/uniswap-universal-router-decoder
I've seen the universal router mentioned in a couple issues and it seems like the way to go.
Would be cool to get this working with the library somehow.

Hey! Just had a quick look into uniswap-python (nice lib, btw ! :) ). If it supports web3.py v6 (saw some pre-v6 toChecksumAddress) and with a bit of work, it should be possible to integrate my lib into it. 👍

cool 👍


Minimum EV SOC not working

I'm  currently running v1.8.0.
I have set Minimum EV SoC to 25%, but when I plug in my car and the SoC is less than 25% it does not start to charge the car.
The Charging sensor keeps begin "Off". The SoC from the car was 15%.
Added screenshots also.

What you described is the current implementation. Minimum EV SoC is used together with Apply price limit to charge the car to the Minimum EV SoC even if the price is higher than the price limit. Note that this charging still is done at the lowest price, and not directly when connecting the car to the charger.
To start charging directly when connected to the charger has been requested in #168.

What is then the difference between Minimum SoC and target SoC?
One would assume that minimum SoC means: Charge to this SoC as soon as the charger is connected whereas
Target SoC is: Charge to this SoC no later than Charge complete time, but at the cheapest possible time.
With the current way, it would charge to Minimum SoC within the Completed time hence as I understand Minimum SoC equals at least Target SoC, unless you set Target SoC lower than Minimum SoC (why would you ever do so)

It appears to be not working as you described. I'm having similar issue as the OP: Minimum SoC doesn't make the car charge when it's plugged in with a SoC lower than the set minimum, no matter the other settings.

Sorry if my description wasn't clear. What you observe is the intended behaviour of the current implementation, i.e. Minimum SoC doesn't make the car charge when it's plugged in with a SoC lower than the set minimum.
To start charging immediately when connected to the charger, if SOC is lower than some value, has been requested in #168.
Since this is a dublicate, I will close this issue.


change PostgreSQL driver to pg8000 only

psycopg2 packaging and building requires more dependencies but it got more recent updates compared to pg8000.
pg8000 is written in pure python, let's try to use only pg8000, if there will be too much performance degradation or not stable enough we can switch back to psycopg2.
What do you think?

I think we first need to measure the performance (probably with the new schema in 6.0) in order to be able to do a good decision.


Theme

NCAR brand standards
We want a consistent top navbar across repositories, a footer that is pinned below the left navbar (doesn't float up if too little content), it to look good on multiple screen sizes and light/dark mode, to make a gallery extension that can be used for each category landing page.

Closing for now in favor of creating more specific issues when appropriate


feat: add isDirty store and setInitialValues helper

Closes #83
Missing

[ ] Documentation for setInitialValues
[ ] Documentation for isDirty
[ ] Documentation for getField (from previous merge)

Codecov Report

Merging #85 (5de8ae5) into main (5d7b58d) will decrease coverage by 0.20%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main      #85      +/-   ##
==========================================
- Coverage   99.33%   99.13%   -0.21%
==========================================
  Files          39       39
  Lines         904      924      +20
  Branches      284      286       +2
==========================================
+ Hits          898      916      +18
- Misses          5        7       +2
  Partials        1        1

Impacted Files
Coverage Δ

packages/solid/src/create-form.ts
100.00% <ø> (ø)

packages/solid/src/stores.ts
98.11% <71.42%> (-1.89%)
:arrow_down:

packages/felte/src/stores.ts
100.00% <100.00%> (ø)

packages/validator-superstruct/src/index.ts
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


npm install error

after getting this error during npm install of example:
'babel' is not recognized as an internal or external command,

I installed babel using
npm install -g babel

but installation fails again with the following error:
d:\git\relay\isomorphic-relay-router>npm install
npm WARN peerDependencies The peer dependency react-router included from isomorphic-relay-router will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from react-router will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
\
><EMAIL_ADDRESS>postinstall d:\git\relay\isomorphic-relay-router\node_modules\react-router
> node ./npm-scripts/postinstall.js

-
><EMAIL_ADDRESS>postinstall d:\git\relay\isomorphic-relay-router\node_modules\history
> node ./npm-scripts/postinstall.js

-
><EMAIL_ADDRESS>postinstall d:\git\relay\isomorphic-relay-router\node_modules\react-router-relay\node_modules\history
> node -e "require('fs').stat('lib', function (e, s) { process.exit(e || !s.isDirectory() ? 1 : 0) })" || npm run build

><EMAIL_ADDRESS>prepublish d:\git\relay\isomorphic-relay-router
> npm run build

><EMAIL_ADDRESS>build d:\git\relay\isomorphic-relay-router
> babel --stage 1 src --out-dir lib

The CLI has been moved into the package `babel-cli`.

$ npm install -g babel-cli

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\\opt\\nodejs\\nodejs-v0.12.4-x64\\\\node.exe" "D:\\opt\\nodejs\\nodejs-v0.12.4-x64\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
npm ERR! node v0.12.4
npm ERR! npm  v2.10.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: `babel --stage 1 src --out-dir lib`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'babel --stage 1 src --out-dir lib'.
npm ERR! This is most likely a problem with the isomorphic-relay-router package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel --stage 1 src --out-dir lib
npm ERR! You can get their info via:
npm ERR!     npm owner ls isomorphic-relay-router
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     d:\git\relay\isomorphic-relay-router\npm-debug.log

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\\opt\\nodejs\\nodejs-v0.12.4-x64\\\\node.exe" "D:\\opt\\nodejs\\nodejs-v0.12.4-x64\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v0.12.4
npm ERR! npm  v2.10.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: `npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'npm run build'.
npm ERR! This is most likely a problem with the isomorphic-relay-router package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build
npm ERR! You can get their info via:
npm ERR!     npm owner ls isomorphic-relay-router
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     d:\git\relay\isomorphic-relay-router\npm-debug.log

d:\git\relay\isomorphic-relay-router>

Currently only babel v5 is supported:
npm install -g babel@5

Added information regarding supported bebel version to README of the example.


master is broken

looks like master is not green since Jan 5 after two commits by @mck1117

https://github.com/dron0gus/wideband/commit/2318bd1e01328d1e752bdb59344bb1f8bbec9a0b

dron0gus@2318bd1

pr?

https://github.com/mck1117/wideband/pull/180


server settings

Core Section

[X] I have searched for this issue on this repository

Stage Selection
None
MOD Selection
None
QUEST Selection
None
RECIPES / EVENTS Selection
None
Summary
Love the pack. I want to play with friends. What is the level-type?

Love the pack. I want to play with friends. What is the level-type?

it should be skyblockbuilder:skyblock (except changes of Skyblock Builder)

is it skyblockbuilder:custom_skyblock?


[WIP] user_events: Update user popover-avatar.

When a user changes its avatar image, the
popover-avatar is being updated as well.
Fixes: #14290

GIFs or Screenshots:

@clarammdantas did this end up working?  My guess is it won't, because the problem is the browser caching the URL we'll later use if one opens the popover later?

@timabbott it didn't work. When I tested the first time it worked, so I made this PR, but then I tested again and it didn't sync, so I consider it could be a cache problem or  . I read the discussion on zulip chat, gonna try to solve it tomorrow.

@timabbott @showell I used the version on user.avatar_url to pass together with avatar/user_id/medium because every time the avatar image is updated, the user.avatar_url is updated as well on the frontend, so the version will be the most recent one. It's working fine :)

@timabbott and @showell This PR is ready for review.
I tried to use the browser URL API as Tim suggested. Before we were using only the relative URL so it was only avatar/user_id/medium but the URL() constructor needs a base_url, so that's why I added it. I don't think it will be any trouble since I'm passing the base_url from window.location.href.

@clarammdantas can you rebase this onto upstream/master?
Also, this is failing tests; you can see from the "Details" link above that test-js-with-node is failing.

This would be an API change requiring an API_FEATURE_LEVEL change.  I tried pushing a commit to this branch for that, but @clarammdantas it looks like you've disabled maintainers pushing to your PRs?

hmm that's odd, I don't remember doing that. I'm going to check and reconfigure.

Merged as 7e9024a39cae63164a6cec34012c16cb74469a87, after (1) adding the feature level update and (2) fixing out-of-order field sorting.  Thanks @clarammdantas!


Adding WIP as an alternative work in progress label

Since we introduced "WIP" rather than "Work in progress" for astropy-helpers.

Actually we could just rename WIP to Work in progress (renaming labels is easy)

oh, sure either way. I wasn't sure why you've named it WIP.

Coverage remained the same at 67.455% when pulling c654cb0ddc2b6a069566a2efd4b4a44c40afeecb on bsipocz:wip_ignores_II into 067d8346302f392bf5c439fd80cd57d69811b72a on astropy:master.

I've renamed it. The original reason I called it WIP instead was 'jet lag' :)


Try to clean up Config table to add the +_ from jamie

Description

Making a mess of everything, clearly not helping much

This will be handle by a new UI/UX of the component.


Zafira patchset inserting test runners is corrupted

Description
Zafira patchset inserting additional test runners fails in latest release (4.1.80)
Steps to reproduce

Install clean Zafira 4.1.79 from scratch
Try to update to 4.1.80

Actual behavior
Startup fails because of db constraint violation:
Caused by: liquibase.exception.DatabaseException: ERROR: duplicate key value violates unique constraint "integration_types_name_unique"
  Detail: Key (name)=(SELENIUM) already exists.
  Where: SQL statement "INSERT INTO integration_types(name, display_name, icon_url, integration_group_id) VALUES ('SELENIUM', 'Selenium', '', integration_group_id_var) RETURNING id"
PL/pgSQL function inline_code_block line 25 at SQL statement [Failed SQL: (0) UPDATE integration_groups SET display_name = 'Test Environment Provider' WHERE name = 'TEST_AUTOMATION_TOOL';

Expected behavior (if known)
Update goes smooth
Environment
API (back-end) version: 4.1.80 (check steps!)
Additional context
This happens because we updated default test runner and then tried to re-insert Selenium regardless of the fact that it was already there.
Proposed fix: wrap every integration we insert into if else checking if it's already inserted (pseudocode: IF integration_types contains ''selenium" THEN do_nothing ELSE insert selenium). Do that for all integrations we insert just in case.

done #1879


[FEAT] [Enhancement]  [Anchor BE Python] Enable Search Functionality for Existing Search Bar on Dashboard/Settings Page

Description
The dashboard/settings page already includes a search bar. This involves implementing the backend functionality to make this search bar operational, allowing users to search elements effectively.
Purpose
To ensure the existing search bar is fully functional and integrates with the backend to provide accurate and relevant search results.
Requirements

Search Query Handling:

Implement backend logic to process search queries submitted through the search bar.
Ensure that search queries are correctly parsed and handled by the backend.

Search Logic:

Develop and integrate algorithms to search through the relevant datasets (e.g., settings, dashboard elements).

Search Results:

Return relevant search results based on user queries.
Ensure results are sorted and displayed in a user-friendly manner.

Performance Considerations:

Optimize search queries to handle large datasets efficiently.
Implement pagination or lazy loading if necessary to manage large result sets.

Error Handling:

Implement error handling for invalid search queries or no results found scenarios.
Provide appropriate feedback to users when no results are available.

Expected Outcome

The existing search bar on the dashboard/settings page becomes functional, allowing users to search and filter settings or elements effectively.
Search results are relevant, well-organized, and performance is optimized.

Acceptance Criteria

The search bar processes user queries and returns relevant results.
Search results are accurate and displayed clearly.
Proper error handling and user feedback are in place.

live link

Please can this be assigned to me?

Someone is on it.
On Sat, 24 Aug 2024 at 15:22, OLUWANIFEMI @.***> wrote:

Please can this be assigned to me?
—
Reply to this email directly, view it on GitHub
https://github.com/hngprojects/hng_boilerplate_nestjs/issues/1007#issuecomment-2308411820,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2A464J3Z7GBXR4X3KKQ6JDZTCJKFAVCNFSM6AAAAABNBSSLTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGQYTCOBSGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


[BUG] lots of exceptions when parsing list of installed applications, making list very short

Please confirm these before moving forward

[X] I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
[X] I have tested that this issue has not been fixed in the latest (beta or stable) release.
[X] I have checked the FAQ section for solutions
[X] This issue is about a bug (if it is not, please use the correct template)

Describe your issue
The list of installed packages is very short & doesn't contain applications installed earlier today. As an example, I installed Tabby & Alacritty with WingetUI today. Gave both of them a good try. Decided to stay with Alacritty. Had to reboot for unrelated reasons. After the reboot neither application appears in the list of installed applications, even though they're both still installed.
Refreshing the list doesn't help.
Additionally the debug log contains a massive amount of exceptions relating to parsing package names/descriptions.
Steps to reproduce the issue
Look at the list of installed packages & the debug log. For the nothing has to be done in order to reproduce it.
WingetUI Log
Debug log file
Package Managers Logs
Package manager log file
Screenshots and videos

I can see what your issue is. I will try to fix it as soon as I can

Much appreciated!


Question.

Is this compatible with Windows 11, and CUDA 11.8?

Ditto, when using the pdf_library.yaml template after activating and installing all deps, the splitter seems to find no files in any of the doc_path's provided. Not sure if this is a windows thing, as the docs seem to only reference linux.

nvm, was a bug in the code: https://github.com/snexus/llm-search/issues/50

CUDA 11.8 shouldn't be a problem. Also fixed the compatibility with Python 3.11. Please open a new ticket if you encounter a specific problem.


entropy: stm32: Move clock configuration to device tree

Similarly to #53258, update entropy driver to get clock configuration from device tree.
Noticeable changes:

STM32L4 are now using MSI or HSI48 instead of PLLSAI as RNG CLK
A runtime check is implemented to check RNG clock config correctness

Based on #53258

Rebased after https://github.com/zephyrproject-rtos/zephyr/pull/53258 was merged

@desowin I had to rebase. Would you mind having a quick new look ?

@erwango hello
This PR currently breaks my project. I'm using rng on stm32l4 for mbedtls purpose.
How my dts should be modified following your PR ? Can you give an example ?
Note: I'm using nucleo_l4a6 board with the following overlay actually:
&rng {
	status = "okay";
};

Thanks for the clarification,
Joel

Auto-reply, hope this can help somebody else reading this PR, I have added:
&clk_hsi48 {
	/* HSI48 required for RNG */
	status = "okay";
};

This activate the HSI clock that is used for RNG peripheral.


Dropped outdated arcfour cipher

OpenSSL 7.6 removed support for arcfour. rsync which uses ssh is trying
to establish connection with use of arcfour. For newer installations it
is ending with an error to establish connection.
Removed hardcoded arcfour cipher from code.

This change is

Identified the issue with outdated arcfour cipher. https://github.com/pytest-dev/pytest-cloud/issues/11

Coverage remained the same at 58.264% when pulling dbb5032e4c71a1f99d81f197641d240d12d7b457 on dasm:remove_arcfour into 1c7c619a02e1cc5c7038c9d286b673f4e363d147 on pytest-dev:master.

@dasm what is your pypi username, will add you as a maintainer so that you can make reseases yourself

@bubenkoff my pypi is the same (just created :P). Added myself to AUTHORS too.

@dasm please don't forget to make and push git tags when making the releases

and of course, the version has to be changed

OK. Will change version and push tags. Thanks @bubenkoff

@bubenkoff I tried to publish new tag on repository, but it's giving me: failed to push some refs
I believe I don't have permissions to do so. For PyPI, Manage button is greyed out too.
Am I missing something?

what's the git command you're running?
as for pypi, you don't have to manage it via the web interface, just do:
 python setup.py sdist upload

from the project folder

I successfully uploaded new version to pypi with CLI. I also pushed new tag. Forgot to create tag with git tag 4.0.0 master at first place. Doh.
Thank you @bubenkoff


Fix code error in routing.md

Handlers should be chained, so semicolons are removed.

Fix #369

Fully fixed in #370


[build-config] move to monorepo root

🏠 Internal
With more packages coming, this PR

moves the build-config to the monorepo root package.json so that package creators don't have to deal with the boilerplate. This will help keep things consistent across packages, too. Note that currently this build config does not support webpack or TS, but we can easily add support for that with @beemo. I tested locally with another test package and everything seems to work okay.

adds a pre-commit hook to run prettier on any staged files ✨

adds a test:watch script to support jest --watch mode. this isn't easy out of the box with beemo because jest runs in a subprocess so output is not piped to the command line, but the script provides a workaround

@kristw @xtinec

This looks good except that jest coverage is being reported as unknown in the build. It works fine locally, so unsure what exactly is wrong.

Looks like it has been reporting unknown for a couple PRs, will fix in another PR as I think it's (another) build config issue.

the jest coverage is fixed 🎉 talk about a worm hole ...

notes from this
jest

jest stopped reporting coverage (only on Travis) because we were defining jest.config.js coveragePathIgnorePatterns in the form ['node_modules/', 'build/', ...].
Travis builds are executed in a /build/ directory on their machines so, and the ignore pattern match uses the full directory location<EMAIL_ADDRESS>pre-pends <roodDir>/ before each of these, e.g., ['<rootDir>/node_modules/', '<rootDir>/build/', ...] to prevent this.

workspaces

Beemo supports workspaces out of the box, i.e., support for monorepos
this PR defined a workspaces entry the root package.json which is used  by both Beemo and yarn
for the build, yarn workspaces actually do a lot of what lerna helps us do (technically don't even need lerna with workspaces), and hoists all package dependencies to the root, and sym-links inter-package dependencies (which lerna bootstrap would do)


db.startsWith is not a function

Um yah, this happens when I run the leaderboard command. Um is this because of the version of quick.db?

Yea, this function got removed in the more recent versions of Quick.db. I believe the version this is using in 6.2.0

Hey! As chxlls said, db.startsWith is outdated. It was replaced with db.has.


Path is not loading in Linux

Tried with stockfish 14,15,16 but I am getting this error
File "/app/app.py", line 105, in init_engine_stockfish     stockfish = Stockfish(path = engine_path)                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/stockfish/models.py", line 57, in __init__     self._stockfish_major_version: int = int(                                          ^^^^ ValueError: invalid literal for int() with base 10: 'Could' (base) ruvinjagoda@Ruvins-MacBook-Air server-docker %

I get the same issue.

@RuvinT It seems you can fix it by editing line 57 in /usr/local/lib/python3.11/site-packages/stockfish/models.py to just comment out the line with #.
No adverse effects seem to have occured.

@RuvinT You could also merge the fix in #124.


Updated splash screen logo to work better with the dark theme

A new build of 63c58c93220d2201b95493ade65893763dae5355 has completed succesfully!
Binaries available at https://build.nav.community/binaries/updated-splash-logo


[WIP] PR: Bookmarks GUI

Description of Changes

[x] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

This is the current status of the bookmarks GUI integration.

Still to be done (short term):

[ ] Refactor the signalling system for bookmarks
- [ ] Write a bookmark manager
- [ ] Remove bookmarks using the pane
- [ ] Remove unused code
[ ] Enable/disable panel from preferences
[ ] Add keyboard shortcuts

Still to be done (maybe now, maybe later):

[ ] Add Bookmarks sub menu to Search(?)-menu with bookmarks in file(?)
[x] Reintroduce column-based bookmarks (adding from panel will give beginning of line or first non-space character or cursor position(?)) but limit to one per line.

Still to be done (most likely not now):

[ ] Fuzzy filtering in Bookmarks pane
[ ] Remove all bookmarks in file (right-click menu on line number/tab?)
[ ] Reassign slots/line numbers from pane

Issue(s) Resolved

Fixes #910
Fixes #9021
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: Oscar Gustafsson/@oscargus

Hello @oscargus! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/bookmarks/plugin.py:

Line 42:80: E501 line too long (81 > 79 characters)
Line 49:5: E303 too many blank lines (2)
Line 50:5: E301 expected 1 blank line, found 0
Line 76:80: E501 line too long (90 > 79 characters)
Line 77:80: E501 line too long (80 > 79 characters)
Line 91:34: W292 no newline at end of file

In the file spyder/plugins/bookmarks/widgets/bookmarksgui.py:

Line 159:80: E501 line too long (81 > 79 characters)
Line 167:13: E128 continuation line under-indented for visual indent
Line 176:17: E731 do not assign a lambda expression, use a def
Line 176:80: E501 line too long (92 > 79 characters)
Line 179:17: E731 do not assign a lambda expression, use a def
Line 179:80: E501 line too long (82 > 79 characters)
Line 183:21: E128 continuation line under-indented for visual indent
Line 185:29: E231 missing whitespace after ','
Line 193:1: E303 too many blank lines (3)
Line 218:80: E501 line too long (82 > 79 characters)
Line 244:1: E303 too many blank lines (3)
Line 247:1: E302 expected 2 blank lines, found 3

In the file spyder/utils/icon_manager.py:

Line 286:80: E501 line too long (115 > 79 characters)
Line 287:80: E501 line too long (219 > 79 characters)

I think that the side bar in the editor is already too large, I don't think we should be making it even larger.
Could the bookmarks be combined with the debug section with a control-click to set the bookmark(shift-click currently does conditional break points)? Your current bookmark icon would overlap nicely behind the debug circle
Currently the debug sections doesn't have a separate context menu. We could add one offering breakpoint insertion and removal and bookmark insertion and removal. In the future we could add conditional breakpoints there.

I think that the side bar in the editor is already too large, I don't think we should be making it even larger.

I agree with @bcolsen. We really need to avoid adding a new panel just for this.

It can probably be merged, yes. Is it possible to stack icons while drawing or should one create combined ones?

Is it possible to stack icons while drawing

Yes it is possible

We stack the # TODO's over the errors in the info panel so it should work.

Should I also try to add markers to the right-hand side "band"? Personally, I do not see the need. Although it may be good to see where the bookmarks are, I doubt that one will use that to jump to them. Being able to add them graphically is primarily a convenience thing.

Should I also try to add markers to the right-hand side "band"?

I think would be handy to see at a glace if you have created a bookmark in a file. The only reason not to would be whether we have any colors left that could be used for bookmarks(we might not).

Closing this as the enforced design with showing at most one of bookmarks/todos/warnings doesn't work for me and do not want to spend more time on it then.

Closing this as the enforced design with showing at most one of bookmarks/todos/warnings doesn't work for me and do not want to spend more time on it then.

I said we should, not we must implement things using a single panel. So I don't see the need for you to close this and PR #9836 because we can still keep discussing the user interface for this.
Why do you think it's better to add multiple panes for these plugins?

As I wrote my concern in the other thread, I believe we cannot really keep adding base plugins and panels to Spyder just "for the sake of it" we really need to think things more thoroughly so that the UI we offer is not too crowded or too confusing for users.

Closing this as the enforced design with showing at most one of bookmarks/todos/warnings doesn't work for me and do not want to spend more time on it then.

Sorry to hear this @oscargus.
We have other options, like mixing not with an exclusive combobox but using checkboxes, so that the user can display several things at the same time, or just some.
I think the bigger concept here is that we have some type of annotation (be it a bookmark, a warning are error, a code tip etc) and we want to provide a single interface to access to these annotations/messages etc. This is where a single plugin idea makes sense, as conceptually they are one and the same, messages for the user with a give position and meaning per file.

As I wrote my concern in the other thread, I believe we cannot really keep adding base plugins and panels to Spyder just "for the sake of it" we really need to think things more thoroughly so that the UI we offer is not too crowded or too confusing for users.

I agree. We've added a lot of complexity in terms of new features to Spyder 4 but I think as a user you don't feel that reflected in the user interface, and that's a good thing.
Therefore adding 3 new panels is something we need to consider very carefully.

We have other options, like mixing not with an exclusive combobox but using checkboxes, so that the user can display several things at the same time, or just some.

Or another option could be using tabs.

I think the bigger concept here is that we have some type of annotation (be it a bookmark, a warning are error, a code tip etc) and we want to provide a single interface to access to these annotations/messages etc.

This is a good point, I haven't seen things like that.

Or another option could be using tabs.

I think @oscargus mentioned he wanted to have a look simultaneously at different things (todos, and warnings for example) so that is why I suggest the having a single view that could mix everything.

The main reason I started using spyder over pycharm although I am at a university and can obtain the professional version for free, is that it has simple user interface, ideal for use in scientific computing which is the main purpose spyder built for. Other students love it as well.

Thanks @Khalilsqu for your input! Glad to know our user interface and user experience design choices is what drives people to Spyder!
As you probably have seen, we put a lot of effort on them.

The thing is that there is no need to show all the plugins, only the activated ones will allocate a tab. However, with the suggestion you put forward (I didn't really see much room for discussion at that time, maybe a language thing, as I'm a non-native English speaker, but for me should is the same as must, I would have used could) limits the possibility to show information concurrently. Information that I would like to see concurrently. By having them as separate plugins, I can undock them, independent of where they are positioned.
Hence, for me it is better to develop the todo and warning panes as external plugins. In that way, anyone who wants to see the information concurrently can do so.
As I wrote in another thread: one can discuss where to put the various plugins. In the code now, all "additional" plugins always ends up in the same position. This is not ideal as it in the Spyder default layout gives up to 11 (plus any external plugins) in the same "screen area"(? not sure what to call it). This may indeed be a problem, if all are shown at the same time. Ideally, the user should be able to position plugins in any screen area, and create its own layouts, but that is clearly a rather big effort.
For me, when I write code, I would prefer to see the bookmarks, TODOs, warnings, (ideally some GitHub information, like loading an issue), the code of course, and possibly the find in files and help.
While running/debugging: console, breakpoints, variables, and editor.
I understand that keeping things simple is important, but also to make things flexible. These are not contradictory. One can have a simple default setting and the ability to add additional features. (Not sure that there should only be one way to do one thing either.)
There is also a fundamental difference between todos/warnings and bookmarks which in my opinion makes them unsuitable to merge into a single interface. Todos/warnings are file-based, while bookmarks are for all files. One could imagine putting todos/warnings in the same interface for sure, it is simple to align the columns. One main reason for not merging todos/warnings was that I couldn't really figure out a single name, even worse an icon, for it (I also started with one of them just to see how it could be done). Merging those into one should be rather straightforward, and one can imagine using checkboxes/menu options to select what to show (one can discuss if these should effect the corresponding settings in preferences or just be session-based).
Also, it can be worth noting that I didn't delete the branch, so anyone wanting to take it up can do so. I just didn't want to put the effort in to get an interface that did not bring me any benefit.
(On another note, ideally, bookmarks should be session/project-based somehow.)

By having them as separate plugins, I can undock them, independent of where they are positioned.

What if this "Extra info" plugin has the possibility to show each tab in a separate window? That's doable and it would cover your use case as well as our design decision.

As I wrote in another thread: one can discuss where to put the various plugins. In the code now, all "additional" plugins always ends up in the same position

I don't understand what you mean by this. Could you provide a screenshot?


Group opposite boolean task options together

Fixes #24704

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

I've triggered the following builds for you:

BuildDistributions build

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


GIL tests are flaky

The following tests fail randomly, for example in https://travis-ci.org/PyO3/pyo3/jobs/501186502:

gil::test::test_owned
gil::test::test_owned_nested
gil::test::test_pyobject_drop

The reason seems to be that they all take references of the empty Python tuple and make assertions for the expected reference count. This can fail if the tests are executed in parallel.

To add a bit more context why this happens: Empty tuples are singletons, i.e. you get the same object every time you ask for an empty (s. https://github.com/python/cpython/blob/234531b4462b20d668762bd78406fd2ebab129c9/Objects/tupleobject.c#L89-L91). This means that those parallel running test all change the reference count of that object, leading to those test failures. A solution would be using a unique object for each test.

This is a similar root cause to #204. See #205 for how this problem was fixed for the GC tests.

How about using cargo test -- --test-threads=1?

That would open is up to other thread safety bugs. We've already found locking bugs in datetime  because the tests are run in parallel. I think the right solution is to make the test suite thread safe.


refactor(upgrade-job): remove duplicate code

Requires #324
This change refactors the helm upgrade dry-run code, and removes a duplicate 'helm upgrade' command runner.

Thanks to @tiagolobocastro for helping with the 'return an async closure' strategy.

@niladrih  Request you to please fill in the PR template. It might take 5 minutes of yours , but is helpful in opensoure world. Your pr says remove duplicate code . What is the code which is removed ?

bors try

bors merge


Adding Contributor section in readme  ( Automatically )

I will like to add a feature this will update contributor list in read me automatically !! Will start to work on this issue as soon as i get assigend !!

Assigned :)


Unused list item

Unused list item after Constants under Identifiers :heart_eyes:

@googlebot I signed it!

this should be fixed now with commit fd8c54856d66df2e2643e048344ae04d2cfdde9a


fails to run

fails to run/launch on a OnePlus One with CM12.1.

Need more info.

Maybe you should show the error file in logcat ....


feature: enable per pod remote APIServer support

Description
This pr includes two new annotations that can be added to pods to override the general APIServer configurations.
In particular:

liqo.io/api-server-support=remote is used to make the offloaded pod contact the remote API server with the mounted service account (the original pod value by default)
liqo.io/api-server-support=disabled will disable the APIServer support in the same way the general flag disables it for all the pods
liqo.io/remote-service-account-name=<remote SA name> specifies the ServiceAccount name for the remote cluster. Note that this needs to be created in the remote cluster with the related permissions; at the moment, liqo is not replicating and reflecting this kind of resource.

Fixes #1832
How Has This Been Tested?

[x] locally
[x] with existing tests

/test

Thank you so much for this feature.

/test

/test

/test

/merge


HBASE-25848: Add flexibility to backup replication in case replication filter throws an exception

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  6s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 39s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed

+1 :green_heart:
javac
1m  1s
the patch passed

+1 :green_heart:
shadedjars
8m 12s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
the patch passed

_ Other Tests _

-1 :x:
unit
148m 20s
hbase-server in the patch failed.

178m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3283

JIRA Issue
HBASE-25848

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f388f6c31017 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 5b9940907e

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/1/testReport/

Max. process+thread count
3748 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@apurtell @gjacoby126 Changed the interface audience.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  3s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 59s
master passed

+1 :green_heart:
compile
1m 17s
master passed

+1 :green_heart:
shadedjars
9m 29s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 49s
master passed

-0 :warning:
patch
10m 32s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 10s
the patch passed

+1 :green_heart:
compile
1m 32s
the patch passed

+1 :green_heart:
javac
1m 32s
the patch passed

+1 :green_heart:
shadedjars
10m  4s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 47s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
206m 33s
hbase-server in the patch passed.

243m 46s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3283

JIRA Issue
HBASE-25848

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d46df40ca52d 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 5b9940907e

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/1/testReport/

Max. process+thread count
2538 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  8s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 45s
the patch passed

+1 :green_heart:
compile
1m 17s
the patch passed

+1 :green_heart:
javac
1m 17s
the patch passed

+1 :green_heart:
shadedjars
8m 53s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
205m 59s
hbase-server in the patch passed.

245m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3283

JIRA Issue
HBASE-25848

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e75079421737 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / fe47557f4c

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/2/testReport/

Max. process+thread count
2765 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 25s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 26s
the patch passed

+1 :green_heart:
compile
1m 26s
the patch passed

+1 :green_heart:
javac
1m 26s
the patch passed

+1 :green_heart:
shadedjars
9m 40s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 48s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
214m 14s
hbase-server in the patch passed.

253m  6s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3283

JIRA Issue
HBASE-25848

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 8130cb95ea72 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7c24ed4f45

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/4/testReport/

Max. process+thread count
2815 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3283/4/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Docs/subhamkrai/#545

@subhamkrai it's a bit deceiving, but the fix that is needed here is to either update published: false to published: true or to remove the "performance" entry in the toc.yml until the performance page has been written.

Okay I'm on it.


 Add Simple nonrepairable test suite

Pull Request Key Information
Reason for change
Adding E2E test suite separately
What was changed
New test suite added
Intended Purpose
Provide a non-repairable only simple test suite for E2E testing
Level of version change required
N/A
Testing Completed
Manually looked over the E2E test suite output results.
Additional Information
Other test suites will be added in separately

V4-simple_nonrepairable_emissions_cdd0f1f25e180ed8bbc5e7b2ceefb11f07faedc5.log


Rename points of interest

Motivation

The term "points of interest" (POIs) is not recognized as locations on the map.
Proposed Solution

Change the wording, e.g.

English: "Locations on map"
German: "Orte auf Karte"

Hey, @timoludwig I would like to work on this.

Can you please guide in which file I need to rename?

Hey, @timoludwig I would like to work on this.

Nice, we really appreciate it!

Can you please guide in which file I need to rename?

The string "Points of Interest" with "Locations on map" in following files:

src/cms/templates/_base.html
src/cms/templates/pois/poi_list.html
src/cms/templates/pois/poi_list_archived.html

The string "POI" with "Locations on map" (only in strings, not in class names) in the following files:

src/cms/views/pois/poi_view.py
src/cms/views/pois/poi_actions.py
src/cms/views/pois/poi_list_view.py

Please keep an eye on lower/upper case.
After that, execute ./dev-tools/translate.sh to re-create the language file src/cms/locale/de/LC_MESSAGES/django.po.
Then, insert the German translation "Orte auf Karte" in the related msgstr sections of the language file.
Feel free to ask any questions, if you feel uncomfortable with the German translations, you can also only change the English strings and we will add the rest. Thanks in advance!

@timoludwig I made all the changes but I could not run the ./dev-tools/install.sh command hence the ./dev-tools/translate.sh.
I am using windows (cmd prompt) could you please guide me which software I need to download so that I can run ./dev-tools/translate.sh command.
Thanks for your guidance.

I was able to install our CMS on Windows using the Windows Subsystem for Linux. See our documentation for more information.
If you think this is too much work for this task, you can just push your changes and I will adjust the translations.

@timoludwig Okay for now I have created a pull request. I guess I need to shift to linux soon.
Thanks for helping me.

Cool, we'd really appreciate it if you wanted to contribute to our project in the future!

Hi, @timoludwig I tried creating a PR for some other issue for the same repo but when I click Pull Request I see both my new commit and my previous commit(this one). I am new to open source can you tell me what should I do?

The reason for this is that I combined your two commits from your develop branch into one commit before merging into our develop branch. Since git doesn't know that these commits are equivalent, it thinks that your two commits are still missing from our develop branch and wants to merge them if you open a new PR.
My suggestion is to work with local feature branches even on your own fork. So every time you work on a new issue, create a new branch and keep your develop branch exactly in sync with ours.
To fix the current state, you have two options:

Delete and re-initialize your fork again or
Remove your two commits from your develop branch and force-push:

git reset --hard HEAD~2
git push origin HEAD --force

After that, you should create a new upstream remote and then you can sync your fork every time our develop branch gets updated.

@timoludwig Thanks a lot. In future if I make a separate branch to work then do I need to merge it or I can just push that feature branch and create a PR

@timoludwig Do I need to merge it or I can just push that feature branch and create a PR

Please open your PR directly from your feature branch without merging it in your fork. Select Integreat/cms-django/develop as base and e.g. Yashs911/cms-django/feature/xyz as head.


Fix misaligned bus icon on Projects page

Asana Ticket: 🐞 Bug | System icons misaligned on Project index
In 0f80d0a a number of classnames that started with c- were renamed to start with m-, but we missed this one spot.
Fixed appearance:

Note that since the bus icon now has the correct margins, it can sometimes wrap onto a second line when it didn't before:

This seems okay to me but, backing up a bit, it seems odd that only buses are represented by an icon here, where other transit modes are spelled out in text. The rest of the page (including the filter buttons at the top and the project list at the bottom) consistently uses icons for all transit modes. Maybe @ingridpierre can shed light on this decision.

I'm not sure why a coverage change is being reported here — the line that supposedly lost coverage is in a Phoenix controller somewhere and doesn't relate to this change. Maybe it's a side effect of the tests being run against a live environment?

Coverage seems to have passed. We typically only concern ourselves with the DIFF tab: https://codecov.io/gh/mbta/dotcom/compare/f4f4da36123925cf1855a15bfdc2a67388048bae...4fe68eb8ffa8d9720326b33995ce4c6e4d62c814/diff

@digitalcora I totally understand the concern here, but it's intentional. There's actually a further perceived discrepancy I hear from other folks, which is that subway lines are described by their line and CR lines only get the mode "pill" shape.
This has to do with how our wayfinding standards IRL work, and also with space concerns. The bus icon is what is intended as often the related or affected buses on projects are too numerous to list. Wayfinding standards are really clearly documented by that team so the Designers tend to follow those when talking about the styling of route info, since they're established outside the department and closely reflect what customers see when they're not looking at their devices.
TL;DR: why we use an icon rather than a pill that says "Bus" or something:
Here's an image of the wayfinding standards to show what this looks like out in the world. Subway line pills, followed by commuter rail mode pill, and bus icon to indicate bus connections.

Thank you @ingridpierre 🙌


Glide clear cache

Is there way to clear cached images? I display big images and after few minutes of work cache can be over than 100mb. I've tried to look at source code and it seems glide used just to download images to file, correct me if I wrong.

It seems Glide don't allow to remove cached images, I'll try Fresco


No more upload_allowed

This is unused and largely polluting the argument list of too many functions.

will merge this one later, after some of the other changes are better tested

@jackrobison please review

Can you rebase on master?


Document Gradle configuration with creating reports

I believe you should document, for example on https://spotbugs.readthedocs.io/en/latest/gradle.html#configure-gradle-plugin, a default setup that creates any Reports at all. I wasn't able to find anything official, and the Gradle plugin just does nothing on its own. It would be great if it also hinted the correct configuration in log when we run build without reports configured.
With fragments from issues like https://github.com/spotbugs/spotbugs-gradle-plugin/issues/1084, some old solutions (or old migration / tasks.withType from pdf), I was able to come up with the following correct configuration for build.gradle.kts:
tasks.withType<com.github.spotbugs.snom.SpotBugsTask> {
    reports {
        reports.create("xml") {
            required = true
            outputLocation =  layout.buildDirectory.file("reports/spotbugs/spotbugs.xml")
        }
        reports.create("html") {
            required = true
            outputLocation =  layout.buildDirectory.file("reports/spotbugs/spotbugs.html")
        }
    }
}

considering that reportsDir = layout.buildDirectory.dir("spotbugs") does nothing, and there is pretty much nothing documented about this parameter.
One more thing, I see that SpotBugsExtension.kt has some Javadocs, but I can't see any of it when viewing these (decompiled) parameters in IntelliJ IDEA, so I'm not sure, but are the sources correctly distributed on Gradle?

Gradle 8.9, id("com.github.spotbugs") version "6.0.20"

Okay, my bad, it seems there was already a documentation in Readme under Configure the SpotBugsTask section, which is linked from the document I linked. It contains code that works with Kotlin:
// require Gradle 8.2+
tasks.spotbugsMain {
    reports.create("html") {
        required = true
        outputLocation = file("$buildDir/reports/spotbugs.html")
        setStylesheet("fancy-hist.xsl")
    }
}

I remember that the reports weren't being generated unless I specified explicit outputLocation, but now it works all the time. I wonder what was wrong with my setup; the documentation includes outputLocation anyway, so it's fine.
My setup with tasks.withType<com.github.spotbugs.snom.SpotBugsTask> also has the mistake of using the same outputLocation for both main and test, so the file would get overwritten.
When it comes to IDE not displaying Javadocs, it behaves the same as se.solrike.sonarlint sonarlint-gradle-plugin. I wonder what causes it.
I'm closing the issue as it's pretty much resolved.


Data loader apply_func breaks when there is a float64 and device is MPS

Bug description
The apply_func does not take into account that MPS devices cannot utilize float64 dtypes. This ultimately breaks a script when by chance a conversion happens automatically and the apply_func sends a float64 to mps.
How to reproduce the bug
Send a json dictionary with a long float number and watch it convert automatically to float64 and crash on a training/testing/validation step.

Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0): Latest
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 1.10): Latest
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration: MPS macbook pro.
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
I tried to make a crappy patch in the apply_func.py file which circunnavigates the issue. Probably whwatever parses it into tensors should be changed to have the default be 32 maybe instead of 64. Here is the fix:
def batch_to(data: Any) -> Any:
        kwargs = {}
        # Don't issue non-blocking transfers to CPU
        # Same with MPS due to a race condition bug: https://github.com/pytorch/pytorch/issues/83015
        if isinstance(data, Tensor) and isinstance(device, torch.device) and device.type not in _BLOCKING_DEVICE_TYPES:
            kwargs["non_blocking"] = True
        if data.type() == "torch.DoubleTensor" and "mps" in str(device):
            data = data.type(torch.float32)
        data_output = data.to(device, **kwargs)
        if data_output is not None:
            return data_output
        # user wrongly implemented the `_TransferableDataType` and forgot to return `self`.
        return data

cc @justusschock

Hi @pedrocolon93
Thanks for reporting this. Could you modify this script  to demonstrate the problem and post it here?

Probably whwatever parses it into tensors should be changed

Could you include the error message in your report, so we know which functions got called?

Probably whwatever parses it into tensors should be changed

@awaelchli this would be the dataloaders collate function.
@pedrocolon93 the collate function is something we don't control. It lives inside the torch dataloaders and has to be customized by the user. We only move it to device later on. And I do think that we should not make these changes but habe the error as is as the other way might introduce undesired behavior regarding numerical stability. The proper solution would be to already return float32 tensors on your dataset.


[Snyk] Upgrade next from 13.5.5 to 13.5.6

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade next from 13.5.5 to 13.5.6.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 10 versions ahead of your current version.
The recommended version was released 21 days ago, on 2023-10-18.

Release notes

Package name: next

13.5.6 - 2023-10-18

13.5.6-canary.8 - 2023-10-19

13.5.6-canary.7 - 2023-10-18

13.5.6-canary.6 - 2023-10-18Core Changes

fix typos: #56870
Update React from 09fbee89d to a41957507: #56970
Reland "feat(turbopack): support basic next/dynamic": #56934
Add @ mui/icons-material to the default optimizePackageImports list: #56801

Credits
Huge thanks to @ xiaolou86, @ ztanner, @ sokra, and @ shuding for helping!

13.5.6-canary.5 - 2023-10-17No content.

13.5.6-canary.4 - 2023-10-17Core Changes

Adding  component to @ next/third-parties: #56106
Replace Promise.withResolvers polyfill with DetachedPromise: #56954
chore(next/image)!: mark onLoadingComplete as deprecated in favor of onLoad: #56944
chore: lower Node.js version requirement: #56943

Misc Changes

chore: reduce fs-extra usage in scripts/: #56917
chore(test): set COREPACK_ENABLE_STRICT: 0 for create-next-app tests: #56955

Credits
Huge thanks to @ janicklas-ralph, @ wyattjoh, @ SukkaW, @ styfle, and @ balazsorban44 for helping!

13.5.6-canary.3 - 2023-10-17Core Changes

feat: set status code to 500 if unexpected error occurs before streaming in app router: #56236
cache: add unstable_noStore API: #56930

Credits
Huge thanks to @ dpnolte and @ feedthejim for helping!

13.5.6-canary.2 - 2023-10-17Core Changes

feat(env): upgrade dotenv: #38481
Update Babel dependencies: #51962
perf: fix tracing for routes: #56924
build: Update swc_core to v0.86.1: #56770

Credits
Huge thanks to @ JuanM04, @ Andarist, @ feedthejim, and @ kdy1 for helping!

13.5.6-canary.1 - 2023-10-16Core Changes

Update React from d900fadbf to 09fbee89d. Removes server context and experimental prefix for server action APIs: #56809

Documentation Changes

Update 05-mdx.mdx . Fix key of the prop: #56883

Credits
Huge thanks to @ WhoAmIRUS and @ gnoff for helping!

13.5.6-canary.0 - 2023-10-16Core Changes

perf: fix server trace file logic : #56898
feat: drop Node.js 16: #56896

Misc Changes

improve next-image-proxy test: #56893
chore(test): test remote image from proxy: #56895
ensure kodiak is re-added to apps list after code-freeze action: #56907

Credits
Huge thanks to @ ztanner, @ styfle, @ feedthejim, and @ balazsorban44 for helping!

13.5.5 - 2023-10-16 Read more

    from next GitHub release notes

Commit messages

Package name: next

9051bc4 v13.5.6
a9e796e update version script
70f93bf update ci config
7db2ce3 Upgrade edge-runtime/cookies (#57021)
40965eb Patch React with fix for write-after-close for ReadableStream (#57011)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


I recieved a request to have a section on removing Application Insights

It would be useful to have a section here on how to remove Application Insights from your project.

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

ID: d0fe1dde-e648-523a-88f5-94811293729d
Version Independent ID: 053b0d57-ab96-b235-cbe3-59f0c9e65bcb
Content: Monitor your ASP.NET Web App  with Azure Application Insights
Content Source: articles/azure-monitor/learn/quick-monitor-portal.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@SergeyKanzhelev Thank you!  I know that there has been interest in seeing this documented.  I will assign this to the document author so they can update our documentation accordingly.

Thanks @SergeyKanzhelev I created an internal work item to track this and will take care of this during this month's sprint.

This issue has been addressed.

#please-close


[issue][controller] - not set error stask on event or on status

Put error stack on event or status seems a good idea to track issue in easy way. But it can break kube-apiserver when the tack trace is big ...
So, the first choice is to truncate message or juste remove it ...

Not send event onError to avoid to create on loop lot of same event. Instead, just create it on condition