[BUG] ImportError: cannot import name 'cached_download' from 'huggingface_hub'

Model
None
Describe the bug
Just Extracted the zip file and did run the win_config.
Problem was on win_start.bat Showed import error
Installation Progress on win_config
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: done

## Package Plan ##

  environment location: C:\Ai\Larma-cleaner\lama-cleaner\installer

  added / updated specs:
    - cudatoolkit=11.7

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    boltons-24.0.0             |     pyhd8ed1ab_0         291 KB  conda-forge
    ca-certificates-2024.8.30  |       h56e8100_0         155 KB  conda-forge
    certifi-2024.8.30          |     pyhd8ed1ab_0         160 KB  conda-forge
    conda-23.7.4               |  py310h5588dad_0        1011 KB  conda-forge
    cudatoolkit-11.7.0         |      ha6f8bbd_10       965.6 MB  conda-forge
    jsonpatch-1.33             |     pyhd8ed1ab_0          17 KB  conda-forge
    jsonpointer-3.0.0          |  py310h5588dad_1          40 KB  conda-forge
    packaging-24.1             |     pyhd8ed1ab_0          49 KB  conda-forge
    pluggy-1.5.0               |     pyhd8ed1ab_0          23 KB  conda-forge
    ruamel.yaml-0.17.21        |  py310he2412df_1         171 KB  conda-forge
    ruamel.yaml.clib-0.2.6     |  py310he2412df_1         112 KB  conda-forge
    ------------------------------------------------------------
                                           Total:       967.6 MB

The following NEW packages will be INSTALLED:

  boltons            conda-forge/noarch::boltons-24.0.0-pyhd8ed1ab_0 None
  cudatoolkit        conda-forge/win-64::cudatoolkit-11.7.0-ha6f8bbd_10 None
  jsonpatch          conda-forge/noarch::jsonpatch-1.33-pyhd8ed1ab_0 None
  jsonpointer        conda-forge/win-64::jsonpointer-3.0.0-py310h5588dad_1 None
  packaging          conda-forge/noarch::packaging-24.1-pyhd8ed1ab_0 None
  pluggy             conda-forge/noarch::pluggy-1.5.0-pyhd8ed1ab_0 None
  ruamel.yaml        conda-forge/win-64::ruamel.yaml-0.17.21-py310he2412df_1 None
  ruamel.yaml.clib   conda-forge/win-64::ruamel.yaml.clib-0.2.6-py310he2412df_1 None

The following packages will be UPDATED:

  ca-certificates                      2022.9.24-h5b45459_0 --> 2024.8.30-h56e8100_0 None
  certifi                            2022.9.24-pyhd8ed1ab_0 --> 2024.8.30-pyhd8ed1ab_0 None
  conda                              22.9.0-py310h5588dad_1 --> 23.7.4-py310h5588dad_0 None

Downloading and Extracting Packages
conda-23.7.4         | 1011 KB   | ############################################################################ | 100%
cudatoolkit-11.7.0   | 965.6 MB  | ############################################################################ | 100%
certifi-2024.8.30    | 160 KB    | ############################################################################ | 100%
ca-certificates-2024 | 155 KB    | ############################################################################ | 100%
boltons-24.0.0       | 291 KB    | ############################################################################ | 100%
jsonpointer-3.0.0    | 40 KB     | ############################################################################ | 100%
ruamel.yaml.clib-0.2 | 112 KB    | ############################################################################ | 100%
ruamel.yaml-0.17.21  | 171 KB    | ############################################################################ | 100%
jsonpatch-1.33       | 17 KB     | ############################################################################ | 100%
pluggy-1.5.0         | 23 KB     | ############################################################################ | 100%
packaging-24.1       | 49 KB     | ############################################################################ | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: | "By downloading and using the CUDA Toolkit conda packages, you accept the terms and conditions of the CUDA End User License Agreement (EULA): https://docs.nvidia.com/cuda/eula/index.html"

done
Retrieving notices: ...working... done
Looking in indexes: https://pypi.org/simple, https://download.pytorch.org/whl/cu117
Collecting torch==1.13.1+cu117
  Using cached https://download.pytorch.org/whl/cu117/torch-1.13.1%2Bcu117-cp310-cp310-win_amd64.whl (2255.4 MB)
Collecting torchvision==0.14.1+cu117
  Using cached https://download.pytorch.org/whl/cu117/torchvision-0.14.1%2Bcu117-cp310-cp310-win_amd64.whl (4.8 MB)
Requirement already satisfied: typing-extensions in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from torch==1.13.1+cu117) (4.3.0)
Collecting numpy
  Using cached numpy-2.1.3-cp310-cp310-win_amd64.whl (12.9 MB)
Collecting pillow!=8.3.*,>=5.3.0
  Using cached pillow-11.0.0-cp310-cp310-win_amd64.whl (2.6 MB)
Requirement already satisfied: requests in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from torchvision==0.14.1+cu117) (2.28.1)
Requirement already satisfied: charset-normalizer<3,>=2 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->torchvision==0.14.1+cu117) (2.0.4)
Requirement already satisfied: idna<4,>=2.5 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->torchvision==0.14.1+cu117) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->torchvision==0.14.1+cu117) (1.26.12)
Requirement already satisfied: certifi>=2017.4.17 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->torchvision==0.14.1+cu117) (2024.8.30)
Installing collected packages: torch, pillow, numpy, torchvision
Successfully installed numpy-2.1.3 pillow-11.0.0 torch-1.13.1+cu117 torchvision-0.14.1+cu117
Collecting xformers==0.0.16
  Using cached xformers-0.0.16-cp310-cp310-win_amd64.whl (40.0 MB)
Requirement already satisfied: numpy in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from xformers==0.0.16) (2.1.3)
Requirement already satisfied: torch==1.13.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from xformers==0.0.16) (1.13.1+cu117)
Collecting pyre-extensions==0.0.23
  Using cached pyre_extensions-0.0.23-py3-none-any.whl (11 kB)
Collecting typing-inspect
  Using cached typing_inspect-0.9.0-py3-none-any.whl (8.8 kB)
Requirement already satisfied: typing-extensions in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from pyre-extensions==0.0.23->xformers==0.0.16) (4.3.0)
Collecting mypy-extensions>=0.3.0
  Using cached mypy_extensions-1.0.0-py3-none-any.whl (4.7 kB)
Installing collected packages: mypy-extensions, typing-inspect, pyre-extensions, xformers
Successfully installed mypy-extensions-1.0.0 pyre-extensions-0.0.23 typing-inspect-0.9.0 xformers-0.0.16
Collecting lama-cleaner
  Using cached lama_cleaner-1.2.5-py3-none-any.whl (6.8 MB)
Collecting piexif==1.1.3
  Using cached piexif-1.1.3-py2.py3-none-any.whl (20 kB)
Collecting flask==2.2.3
  Using cached Flask-2.2.3-py3-none-any.whl (101 kB)
Collecting simple-websocket
  Using cached simple_websocket-1.1.0-py3-none-any.whl (13 kB)
Collecting omegaconf
  Using cached omegaconf-2.3.0-py3-none-any.whl (79 kB)
Collecting safetensors
  Using cached safetensors-0.4.5-cp310-none-win_amd64.whl (285 kB)
Collecting loguru
  Using cached loguru-0.7.2-py3-none-any.whl (62 kB)
Requirement already satisfied: torch>=1.9.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (1.13.1+cu117)
Collecting werkzeug==2.2.2
  Using cached Werkzeug-2.2.2-py3-none-any.whl (232 kB)
Collecting transformers==4.27.4
  Using cached transformers-4.27.4-py3-none-any.whl (6.8 MB)
Collecting gradio
  Using cached gradio-5.4.0-py3-none-any.whl (56.7 MB)
Collecting yacs
  Using cached yacs-0.1.8-py3-none-any.whl (14 kB)
Collecting controlnet-aux==0.0.3
  Using cached controlnet_aux-0.0.3-py3-none-any.whl (122 kB)
Collecting opencv-python
  Using cached opencv_python-<IP_ADDRESS>-cp37-abi3-win_amd64.whl (38.8 MB)
Collecting diffusers==0.16.1
  Using cached diffusers-0.16.1-py3-none-any.whl (934 kB)
Collecting pydantic
  Using cached pydantic-2.9.2-py3-none-any.whl (434 kB)
Collecting flaskwebgui==0.3.5
  Using cached flaskwebgui-0.3.5-py3-none-any.whl (7.9 kB)
Collecting flask-cors
  Using cached Flask_Cors-5.0.0-py2.py3-none-any.whl (14 kB)
Requirement already satisfied: rich in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from lama-cleaner) (12.5.1)
Collecting flask-socketio
  Using cached Flask_SocketIO-5.4.1-py3-none-any.whl (18 kB)
Collecting scipy
  Using cached scipy-1.14.1-cp310-cp310-win_amd64.whl (44.8 MB)
Collecting einops
  Using cached einops-0.8.0-py3-none-any.whl (43 kB)
Collecting filelock
  Using cached filelock-3.16.1-py3-none-any.whl (16 kB)
Collecting importlib-metadata
  Using cached importlib_metadata-8.5.0-py3-none-any.whl (26 kB)
Requirement already satisfied: numpy in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (2.1.3)
Collecting scikit-image
  Using cached scikit_image-0.24.0-cp310-cp310-win_amd64.whl (12.9 MB)
Collecting timm
  Using cached timm-1.0.11-py3-none-any.whl (2.3 MB)
Requirement already satisfied: torchvision in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (0.14.1+cu117)
Requirement already satisfied: Pillow in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from controlnet-aux==0.0.3->lama-cleaner) (11.0.0)
Collecting huggingface-hub
  Using cached huggingface_hub-0.26.2-py3-none-any.whl (447 kB)
Collecting regex!=2019.12.17
  Using cached regex-2024.9.11-cp310-cp310-win_amd64.whl (274 kB)
Requirement already satisfied: requests in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from diffusers==0.16.1->lama-cleaner) (2.28.1)
Collecting click>=8.0
  Using cached click-8.1.7-py3-none-any.whl (97 kB)
Collecting Jinja2>=3.0
  Using cached jinja2-3.1.4-py3-none-any.whl (133 kB)
Collecting itsdangerous>=2.0
  Using cached itsdangerous-2.2.0-py3-none-any.whl (16 kB)
Collecting whichcraft
  Using cached whichcraft-0.6.1-py2.py3-none-any.whl (5.2 kB)
Requirement already satisfied: packaging>=20.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from transformers==4.27.4->lama-cleaner) (24.1)
Requirement already satisfied: tqdm>=4.27 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from transformers==4.27.4->lama-cleaner) (4.64.1)
Collecting pyyaml>=5.1
  Using cached PyYAML-6.0.2-cp310-cp310-win_amd64.whl (161 kB)
Collecting tokenizers!=0.11.3,<0.14,>=0.11.1
  Using cached tokenizers-0.13.3-cp310-cp310-win_amd64.whl (3.5 MB)
Collecting MarkupSafe>=2.1.1
  Using cached MarkupSafe-3.0.2-cp310-cp310-win_amd64.whl (15 kB)
Requirement already satisfied: typing-extensions in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from torch>=1.9.0->lama-cleaner) (4.3.0)
Collecting python-socketio>=5.0.2
  Using cached python_socketio-5.11.4-py3-none-any.whl (76 kB)
Collecting tomlkit==0.12.0
  Using cached tomlkit-0.12.0-py3-none-any.whl (37 kB)
Collecting semantic-version~=2.0
  Using cached semantic_version-2.10.0-py2.py3-none-any.whl (15 kB)
Collecting aiofiles<24.0,>=22.0
  Using cached aiofiles-23.2.1-py3-none-any.whl (15 kB)
Collecting ffmpy
  Using cached ffmpy-0.4.0-py3-none-any.whl (5.8 kB)
Collecting python-multipart==0.0.12
  Using cached python_multipart-0.0.12-py3-none-any.whl (23 kB)
Collecting gradio-client==1.4.2
  Using cached gradio_client-1.4.2-py3-none-any.whl (319 kB)
Collecting typer<1.0,>=0.12
  Using cached typer-0.12.5-py3-none-any.whl (47 kB)
Collecting MarkupSafe>=2.1.1
  Using cached MarkupSafe-2.1.5-cp310-cp310-win_amd64.whl (17 kB)
Collecting fastapi<1.0,>=0.115.2
  Using cached fastapi-0.115.4-py3-none-any.whl (94 kB)
Collecting pandas<3.0,>=1.0
  Using cached pandas-2.2.3-cp310-cp310-win_amd64.whl (11.6 MB)
Collecting anyio<5.0,>=3.0
  Using cached anyio-4.6.2.post1-py3-none-any.whl (90 kB)
Collecting orjson~=3.0
  Using cached orjson-3.10.11-cp310-none-win_amd64.whl (136 kB)
Collecting pydub
  Using cached pydub-0.25.1-py2.py3-none-any.whl (32 kB)
Collecting ruff>=0.2.2
  Using cached ruff-0.7.2-py3-none-win_amd64.whl (9.4 MB)
Collecting uvicorn>=0.14.0
  Using cached uvicorn-0.32.0-py3-none-any.whl (63 kB)
Collecting httpx>=0.24.1
  Using cached httpx-0.27.2-py3-none-any.whl (76 kB)
Collecting safehttpx<1.0,>=0.1.1
  Using cached safehttpx-0.1.1-py3-none-any.whl (8.4 kB)
Collecting starlette<1.0,>=0.40.0
  Using cached starlette-0.41.2-py3-none-any.whl (73 kB)
Collecting fsspec
  Using cached fsspec-2024.10.0-py3-none-any.whl (179 kB)
Collecting websockets<13.0,>=10.0
  Using cached websockets-12.0-cp310-cp310-win_amd64.whl (124 kB)
Collecting pydantic-core==2.23.4
  Using cached pydantic_core-2.23.4-cp310-none-win_amd64.whl (1.9 MB)
Collecting annotated-types>=0.6.0
  Using cached annotated_types-0.7.0-py3-none-any.whl (13 kB)
Collecting typing-extensions
  Using cached typing_extensions-4.12.2-py3-none-any.whl (37 kB)
Collecting win32-setctime>=1.0.0
  Using cached win32_setctime-1.1.0-py3-none-any.whl (3.6 kB)
Requirement already satisfied: colorama>=0.3.4 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from loguru->lama-cleaner) (0.4.5)
Collecting antlr4-python3-runtime==4.9.*
  Using cached antlr4_python3_runtime-4.9.3-py3-none-any.whl
Requirement already satisfied: commonmark<0.10.0,>=0.9.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from rich->lama-cleaner) (0.9.1)
Requirement already satisfied: pygments<3.0.0,>=2.6.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from rich->lama-cleaner) (2.11.2)
Collecting wsproto
  Using cached wsproto-1.2.0-py3-none-any.whl (24 kB)
Collecting exceptiongroup>=1.0.2
  Using cached exceptiongroup-1.2.2-py3-none-any.whl (16 kB)
Requirement already satisfied: idna>=2.8 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from anyio<5.0,>=3.0->gradio->lama-cleaner) (3.4)
Collecting sniffio>=1.1
  Using cached sniffio-1.3.1-py3-none-any.whl (10 kB)
Requirement already satisfied: certifi in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from httpx>=0.24.1->gradio->lama-cleaner) (2024.8.30)
Collecting httpcore==1.*
  Using cached httpcore-1.0.6-py3-none-any.whl (78 kB)
Collecting h11<0.15,>=0.13
  Using cached h11-0.14.0-py3-none-any.whl (58 kB)
Collecting pytz>=2020.1
  Using cached pytz-2024.2-py2.py3-none-any.whl (508 kB)
Collecting python-dateutil>=2.8.2
  Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl (229 kB)
Collecting tzdata>=2022.7
  Using cached tzdata-2024.2-py2.py3-none-any.whl (346 kB)
Collecting bidict>=0.21.0
  Using cached bidict-0.23.1-py3-none-any.whl (32 kB)
Collecting python-engineio>=4.8.0
  Using cached python_engineio-4.10.1-py3-none-any.whl (57 kB)
Collecting shellingham>=1.3.0
  Using cached shellingham-1.5.4-py2.py3-none-any.whl (9.8 kB)
Collecting zipp>=3.20
  Using cached zipp-3.20.2-py3-none-any.whl (9.2 kB)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (1.26.12)
Requirement already satisfied: charset-normalizer<3,>=2 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->diffusers==0.16.1->lama-cleaner) (2.0.4)
Collecting networkx>=2.8
  Using cached networkx-3.4.2-py3-none-any.whl (1.7 MB)
Collecting tifffile>=2022.8.12
  Using cached tifffile-2024.9.20-py3-none-any.whl (228 kB)
Collecting lazy-loader>=0.4
  Using cached lazy_loader-0.4-py3-none-any.whl (12 kB)
Collecting imageio>=2.33
  Using cached imageio-2.36.0-py3-none-any.whl (315 kB)
Collecting six>=1.5
  Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Installing collected packages: whichcraft, tokenizers, pytz, pydub, antlr4-python3-runtime, zipp, win32-setctime, websockets, tzdata, typing-extensions, tomlkit, tifffile, sniffio, six, shellingham, semantic-version, scipy, safetensors, ruff, regex, pyyaml, python-multipart, piexif, orjson, opencv-python, networkx, MarkupSafe, lazy-loader, itsdangerous, imageio, h11, fsspec, flaskwebgui, filelock, ffmpy, exceptiongroup, einops, click, bidict, annotated-types, aiofiles, yacs, wsproto, werkzeug, uvicorn, typer, scikit-image, python-dateutil, pydantic-core, omegaconf, loguru, Jinja2, importlib-metadata, huggingface-hub, httpcore, anyio, transformers, starlette, simple-websocket, pydantic, pandas, httpx, flask, diffusers, timm, safehttpx, python-engineio, gradio-client, flask-cors, fastapi, python-socketio, gradio, controlnet-aux, flask-socketio, lama-cleaner
  Attempting uninstall: typing-extensions
    Found existing installation: typing_extensions 4.3.0
    Uninstalling typing_extensions-4.3.0:
      Successfully uninstalled typing_extensions-4.3.0
Successfully installed Jinja2-3.1.4 MarkupSafe-2.1.5 aiofiles-23.2.1 annotated-types-0.7.0 antlr4-python3-runtime-4.9.3 anyio-4.6.2.post1 bidict-0.23.1 click-8.1.7 controlnet-aux-0.0.3 diffusers-0.16.1 einops-0.8.0 exceptiongroup-1.2.2 fastapi-0.115.4 ffmpy-0.4.0 filelock-3.16.1 flask-2.2.3 flask-cors-5.0.0 flask-socketio-5.4.1 flaskwebgui-0.3.5 fsspec-2024.10.0 gradio-5.4.0 gradio-client-1.4.2 h11-0.14.0 httpcore-1.0.6 httpx-0.27.2 huggingface-hub-0.26.2 imageio-2.36.0 importlib-metadata-8.5.0 itsdangerous-2.2.0 lama-cleaner-1.2.5 lazy-loader-0.4 loguru-0.7.2 networkx-3.4.2 omegaconf-2.3.0 opencv-python-<IP_ADDRESS> orjson-3.10.11 pandas-2.2.3 piexif-1.1.3 pydantic-2.9.2 pydantic-core-2.23.4 pydub-0.25.1 python-dateutil-2.9.0.post0 python-engineio-4.10.1 python-multipart-0.0.12 python-socketio-5.11.4 pytz-2024.2 pyyaml-6.0.2 regex-2024.9.11 ruff-0.7.2 safehttpx-0.1.1 safetensors-0.4.5 scikit-image-0.24.0 scipy-1.14.1 semantic-version-2.10.0 shellingham-1.5.4 simple-websocket-1.1.0 six-1.16.0 sniffio-1.3.1 starlette-0.41.2 tifffile-2024.9.20 timm-1.0.11 tokenizers-0.13.3 tomlkit-0.12.0 transformers-4.27.4 typer-0.12.5 typing-extensions-4.12.2 tzdata-2024.2 uvicorn-0.32.0 websockets-12.0 werkzeug-2.2.2 whichcraft-0.6.1 win32-setctime-1.1.0 wsproto-1.2.0 yacs-0.1.8 zipp-3.20.2
- Platform: Windows-10-10.0.26100-SP0
- Python version: 3.10.6
- torch: 1.13.1+cu117
- torchvision: 0.14.1+cu117
- Pillow: 11.0.0
- diffusers: 0.16.1
- transformers: 4.27.4
- opencv-python: <IP_ADDRESS>
- xformers: 0.0.16
- accelerate: N/A
- lama-cleaner: 1.2.5
- rembg: N/A
- realesrgan: N/A
- gfpgan: N/A

Collecting rembg
  Using cached rembg-2.0.59-py3-none-any.whl (39 kB)
Requirement already satisfied: tqdm in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from rembg) (4.64.1)
Requirement already satisfied: pillow in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from rembg) (11.0.0)
Requirement already satisfied: scipy in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from rembg) (1.14.1)
Requirement already satisfied: scikit-image in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from rembg) (0.24.0)
Collecting opencv-python-headless
  Using cached opencv_python_headless-<IP_ADDRESS>-cp37-abi3-win_amd64.whl (38.8 MB)
Collecting onnxruntime
  Using cached onnxruntime-1.20.0-cp310-cp310-win_amd64.whl (11.3 MB)
Collecting pooch
  Using cached pooch-1.8.2-py3-none-any.whl (64 kB)
Collecting pymatting
  Using cached PyMatting-1.1.12-py3-none-any.whl (52 kB)
Collecting jsonschema
  Using cached jsonschema-4.23.0-py3-none-any.whl (88 kB)
Requirement already satisfied: numpy in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from rembg) (2.1.3)
Collecting attrs>=22.2.0
  Using cached attrs-24.2.0-py3-none-any.whl (63 kB)
Collecting jsonschema-specifications>=2023.03.6
  Using cached jsonschema_specifications-2024.10.1-py3-none-any.whl (18 kB)
Collecting rpds-py>=0.7.1
  Using cached rpds_py-0.20.1-cp310-none-win_amd64.whl (218 kB)
Collecting referencing>=0.28.4
  Using cached referencing-0.35.1-py3-none-any.whl (26 kB)
Collecting protobuf
  Using cached protobuf-5.28.3-cp310-abi3-win_amd64.whl (431 kB)
Collecting flatbuffers
  Using cached flatbuffers-24.3.25-py2.py3-none-any.whl (26 kB)
Collecting sympy
  Using cached sympy-1.13.3-py3-none-any.whl (6.2 MB)
Collecting coloredlogs
  Using cached coloredlogs-15.0.1-py2.py3-none-any.whl (46 kB)
Requirement already satisfied: packaging in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from onnxruntime->rembg) (24.1)
Collecting platformdirs>=2.5.0
  Using cached platformdirs-4.3.6-py3-none-any.whl (18 kB)
Requirement already satisfied: requests>=2.19.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from pooch->rembg) (2.28.1)
Collecting numba!=0.49.0
  Using cached numba-0.60.0-cp310-cp310-win_amd64.whl (2.7 MB)
Requirement already satisfied: tifffile>=2022.8.12 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->rembg) (2024.9.20)
Requirement already satisfied: lazy-loader>=0.4 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->rembg) (0.4)
Requirement already satisfied: networkx>=2.8 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->rembg) (3.4.2)
Requirement already satisfied: imageio>=2.33 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->rembg) (2.36.0)
Requirement already satisfied: colorama in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tqdm->rembg) (0.4.5)
Collecting llvmlite<0.44,>=0.43.0dev0
  Using cached llvmlite-0.43.0-cp310-cp310-win_amd64.whl (28.1 MB)
Collecting numpy
  Using cached numpy-2.0.2-cp310-cp310-win_amd64.whl (15.9 MB)
Requirement already satisfied: certifi>=2017.4.17 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests>=2.19.0->pooch->rembg) (2024.8.30)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests>=2.19.0->pooch->rembg) (1.26.12)
Requirement already satisfied: charset-normalizer<3,>=2 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests>=2.19.0->pooch->rembg) (2.0.4)
Requirement already satisfied: idna<4,>=2.5 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests>=2.19.0->pooch->rembg) (3.4)
Collecting humanfriendly>=9.1
  Using cached humanfriendly-10.0-py2.py3-none-any.whl (86 kB)
Collecting mpmath<1.4,>=1.1.0
  Using cached mpmath-1.3.0-py3-none-any.whl (536 kB)
Collecting pyreadline3
  Using cached pyreadline3-3.5.4-py3-none-any.whl (83 kB)
Installing collected packages: mpmath, flatbuffers, sympy, rpds-py, pyreadline3, protobuf, platformdirs, numpy, llvmlite, attrs, referencing, pooch, opencv-python-headless, numba, humanfriendly, pymatting, jsonschema-specifications, coloredlogs, onnxruntime, jsonschema, rembg
  Attempting uninstall: numpy
    Found existing installation: numpy 2.1.3
    Uninstalling numpy-2.1.3:
      Successfully uninstalled numpy-2.1.3
Successfully installed attrs-24.2.0 coloredlogs-15.0.1 flatbuffers-24.3.25 humanfriendly-10.0 jsonschema-4.23.0 jsonschema-specifications-2024.10.1 llvmlite-0.43.0 mpmath-1.3.0 numba-0.60.0 numpy-2.0.2 onnxruntime-1.20.0 opencv-python-headless-<IP_ADDRESS> platformdirs-4.3.6 pooch-1.8.2 protobuf-5.28.3 pymatting-1.1.12 pyreadline3-3.5.4 referencing-0.35.1 rembg-2.0.59 rpds-py-0.20.1 sympy-1.13.3
Collecting realesrgan
  Using cached realesrgan-0.3.0-py3-none-any.whl (26 kB)
Requirement already satisfied: numpy in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from realesrgan) (2.0.2)
Collecting facexlib>=0.2.5
  Using cached facexlib-0.3.0-py3-none-any.whl (59 kB)
Requirement already satisfied: Pillow in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from realesrgan) (11.0.0)
Requirement already satisfied: opencv-python in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from realesrgan) (<IP_ADDRESS>)
Requirement already satisfied: torch>=1.7 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from realesrgan) (1.13.1+cu117)
Collecting gfpgan>=1.3.5
  Using cached gfpgan-1.3.8-py3-none-any.whl (52 kB)
Collecting basicsr>=1.4.2
  Using cached basicsr-1.4.2-py3-none-any.whl
Requirement already satisfied: tqdm in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from realesrgan) (4.64.1)
Requirement already satisfied: torchvision in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from realesrgan) (0.14.1+cu117)
Collecting yapf
  Using cached yapf-0.40.2-py3-none-any.whl (254 kB)
Requirement already satisfied: requests in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (2.28.1)
Requirement already satisfied: pyyaml in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (6.0.2)
Collecting addict
  Using cached addict-2.4.0-py3-none-any.whl (3.8 kB)
Collecting tb-nightly
  Using cached tb_nightly-2.19.0a20241104-py3-none-any.whl (5.5 MB)
Collecting lmdb
  Using cached lmdb-1.5.1-cp310-cp310-win_amd64.whl (100 kB)
Requirement already satisfied: scipy in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (1.14.1)
Requirement already satisfied: scikit-image in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (0.24.0)
Requirement already satisfied: future in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->realesrgan) (0.18.2)
Collecting filterpy
  Using cached filterpy-1.4.5-py3-none-any.whl
Requirement already satisfied: numba in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from facexlib>=0.2.5->realesrgan) (0.60.0)
Requirement already satisfied: typing-extensions in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from torch>=1.7->realesrgan) (4.12.2)
Requirement already satisfied: colorama in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tqdm->realesrgan) (0.4.5)
Collecting matplotlib
  Using cached matplotlib-3.9.2-cp310-cp310-win_amd64.whl (7.8 MB)
Requirement already satisfied: llvmlite<0.44,>=0.43.0dev0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from numba->facexlib>=0.2.5->realesrgan) (0.43.0)
Requirement already satisfied: certifi>=2017.4.17 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->realesrgan) (2024.8.30)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->realesrgan) (1.26.12)
Requirement already satisfied: charset-normalizer<3,>=2 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->realesrgan) (2.0.4)
Requirement already satisfied: idna<4,>=2.5 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->realesrgan) (3.4)
Requirement already satisfied: tifffile>=2022.8.12 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (2024.9.20)
Requirement already satisfied: packaging>=21 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (24.1)
Requirement already satisfied: networkx>=2.8 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (3.4.2)
Requirement already satisfied: lazy-loader>=0.4 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (0.4)
Requirement already satisfied: imageio>=2.33 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->realesrgan) (2.36.0)
Requirement already satisfied: werkzeug>=1.0.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (2.2.2)
Collecting absl-py>=0.4
  Using cached absl_py-2.1.0-py3-none-any.whl (133 kB)
Collecting markdown>=2.6.8
  Using cached Markdown-3.7-py3-none-any.whl (106 kB)
Requirement already satisfied: six>1.9 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (1.16.0)
Requirement already satisfied: setuptools>=41.0.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (65.4.0)
Requirement already satisfied: protobuf!=4.24.0,>=3.19.6 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->basicsr>=1.4.2->realesrgan) (5.28.3)
Collecting grpcio>=1.48.2
  Using cached grpcio-1.67.1-cp310-cp310-win_amd64.whl (4.4 MB)
Collecting tensorboard-data-server<0.8.0,>=0.7.0
  Using cached tensorboard_data_server-0.7.2-py3-none-any.whl (2.4 kB)
Requirement already satisfied: platformdirs>=3.5.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from yapf->basicsr>=1.4.2->realesrgan) (4.3.6)
Collecting tomli>=2.0.1
  Using cached tomli-2.0.2-py3-none-any.whl (13 kB)
Requirement already satisfied: importlib-metadata>=6.6.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from yapf->basicsr>=1.4.2->realesrgan) (8.5.0)
Requirement already satisfied: zipp>=3.20 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from importlib-metadata>=6.6.0->yapf->basicsr>=1.4.2->realesrgan) (3.20.2)
Requirement already satisfied: MarkupSafe>=2.1.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from werkzeug>=1.0.1->tb-nightly->basicsr>=1.4.2->realesrgan) (2.1.5)
Collecting fonttools>=4.22.0
  Using cached fonttools-4.54.1-cp310-cp310-win_amd64.whl (2.2 MB)
Collecting kiwisolver>=1.3.1
  Using cached kiwisolver-1.4.7-cp310-cp310-win_amd64.whl (55 kB)
Collecting cycler>=0.10
  Using cached cycler-0.12.1-py3-none-any.whl (8.3 kB)
Collecting contourpy>=1.0.1
  Using cached contourpy-1.3.0-cp310-cp310-win_amd64.whl (216 kB)
Requirement already satisfied: python-dateutil>=2.7 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->realesrgan) (2.9.0.post0)
Collecting pyparsing>=2.3.1
  Using cached pyparsing-3.2.0-py3-none-any.whl (106 kB)
Installing collected packages: lmdb, addict, tomli, tensorboard-data-server, pyparsing, markdown, kiwisolver, grpcio, fonttools, cycler, contourpy, absl-py, yapf, tb-nightly, matplotlib, filterpy, basicsr, facexlib, gfpgan, realesrgan
Successfully installed absl-py-2.1.0 addict-2.4.0 basicsr-1.4.2 contourpy-1.3.0 cycler-0.12.1 facexlib-0.3.0 filterpy-1.4.5 fonttools-4.54.1 gfpgan-1.3.8 grpcio-1.67.1 kiwisolver-1.4.7 lmdb-1.5.1 markdown-3.7 matplotlib-3.9.2 pyparsing-3.2.0 realesrgan-0.3.0 tb-nightly-2.19.0a20241104 tensorboard-data-server-0.7.2 tomli-2.0.2 yapf-0.40.2
Requirement already satisfied: gfpgan in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (1.3.8)
Requirement already satisfied: yapf in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (0.40.2)
Requirement already satisfied: opencv-python in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (<IP_ADDRESS>)
Requirement already satisfied: basicsr>=1.4.2 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (1.4.2)
Requirement already satisfied: pyyaml in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (6.0.2)
Requirement already satisfied: tb-nightly in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (2.19.0a20241104)
Requirement already satisfied: numpy in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (2.0.2)
Requirement already satisfied: tqdm in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (4.64.1)
Requirement already satisfied: torchvision in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (0.14.1+cu117)
Requirement already satisfied: facexlib>=0.2.5 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (0.3.0)
Requirement already satisfied: scipy in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (1.14.1)
Requirement already satisfied: torch>=1.7 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (1.13.1+cu117)
Requirement already satisfied: lmdb in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from gfpgan) (1.5.1)
Requirement already satisfied: scikit-image in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (0.24.0)
Requirement already satisfied: Pillow in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (11.0.0)
Requirement already satisfied: requests in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (2.28.1)
Requirement already satisfied: addict in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (2.4.0)
Requirement already satisfied: future in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from basicsr>=1.4.2->gfpgan) (0.18.2)
Requirement already satisfied: numba in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from facexlib>=0.2.5->gfpgan) (0.60.0)
Requirement already satisfied: filterpy in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from facexlib>=0.2.5->gfpgan) (1.4.5)
Requirement already satisfied: typing-extensions in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from torch>=1.7->gfpgan) (4.12.2)
Requirement already satisfied: tensorboard-data-server<0.8.0,>=0.7.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (0.7.2)
Requirement already satisfied: grpcio>=1.48.2 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (1.67.1)
Requirement already satisfied: absl-py>=0.4 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (2.1.0)
Requirement already satisfied: packaging in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (24.1)
Requirement already satisfied: werkzeug>=1.0.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (2.2.2)
Requirement already satisfied: protobuf!=4.24.0,>=3.19.6 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (5.28.3)
Requirement already satisfied: setuptools>=41.0.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (65.4.0)
Requirement already satisfied: six>1.9 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (1.16.0)
Requirement already satisfied: markdown>=2.6.8 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tb-nightly->gfpgan) (3.7)
Requirement already satisfied: colorama in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from tqdm->gfpgan) (0.4.5)
Requirement already satisfied: platformdirs>=3.5.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from yapf->gfpgan) (4.3.6)
Requirement already satisfied: importlib-metadata>=6.6.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from yapf->gfpgan) (8.5.0)
Requirement already satisfied: tomli>=2.0.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from yapf->gfpgan) (2.0.2)
Requirement already satisfied: zipp>=3.20 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from importlib-metadata>=6.6.0->yapf->gfpgan) (3.20.2)
Requirement already satisfied: MarkupSafe>=2.1.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from werkzeug>=1.0.1->tb-nightly->gfpgan) (2.1.5)
Requirement already satisfied: matplotlib in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from filterpy->facexlib>=0.2.5->gfpgan) (3.9.2)
Requirement already satisfied: llvmlite<0.44,>=0.43.0dev0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from numba->facexlib>=0.2.5->gfpgan) (0.43.0)
Requirement already satisfied: charset-normalizer<3,>=2 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->gfpgan) (2.0.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->gfpgan) (1.26.12)
Requirement already satisfied: certifi>=2017.4.17 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->gfpgan) (2024.8.30)
Requirement already satisfied: idna<4,>=2.5 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from requests->basicsr>=1.4.2->gfpgan) (3.4)
Requirement already satisfied: tifffile>=2022.8.12 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->gfpgan) (2024.9.20)
Requirement already satisfied: networkx>=2.8 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->gfpgan) (3.4.2)
Requirement already satisfied: imageio>=2.33 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->gfpgan) (2.36.0)
Requirement already satisfied: lazy-loader>=0.4 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from scikit-image->basicsr>=1.4.2->gfpgan) (0.4)
Requirement already satisfied: fonttools>=4.22.0 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (4.54.1)
Requirement already satisfied: kiwisolver>=1.3.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (1.4.7)
Requirement already satisfied: python-dateutil>=2.7 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (2.9.0.post0)
Requirement already satisfied: contourpy>=1.0.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (1.3.0)
Requirement already satisfied: pyparsing>=2.3.1 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (3.2.0)
Requirement already satisfied: cycler>=0.10 in c:\ai\larma-cleaner\lama-cleaner\installer\lib\site-packages (from matplotlib->filterpy->facexlib>=0.2.5->gfpgan) (0.12.1)
- Platform: Windows-10-10.0.26100-SP0
- Python version: 3.10.6
- torch: 1.13.1+cu117
- torchvision: 0.14.1+cu117
- Pillow: 11.0.0
- diffusers: 0.16.1
- transformers: 4.27.4
- opencv-python: <IP_ADDRESS>
- xformers: 0.0.16
- accelerate: N/A
- lama-cleaner: 1.2.5
- rembg: 2.0.59
- realesrgan: 0.3.0
- gfpgan: 1.3.8

2024-11-04 15:15:41.328 | INFO     | lama_cleaner.parse_args:parse_args:185 - Launching installer web config page
INFO: Could not find files for the given pattern(s).
* Running on local URL:  http://<IP_ADDRESS>:7861

To create a public link, set `share=True` in `launch()`.
host='<IP_ADDRESS>' port=8080 model='lama' sd_local_model_path='' sd_controlnet=False sd_controlnet_method='control_v11p_sd15_canny' device='cuda' gui=False no_gui_auto_close=False no_half=False cpu_offload=False disable_nsfw=False sd_cpu_textencoder=False enable_xformers=False local_files_only=False model_dir='C:\\Users\\Admin\\.cache' input='' output_dir='' enable_interactive_seg=False interactive_seg_model='vit_l' interactive_seg_device='cpu' enable_remove_bg=False enable_anime_seg=False enable_realesrgan=False realesrgan_device='cpu' realesrgan_model='realesr-general-x4v3' realesrgan_no_half=False enable_gfpgan=False gfpgan_device='cpu' enable_restoreformer=False restoreformer_device='cpu' enable_gif=False
2024-11-04 15:15:46.924 | INFO     | lama_cleaner.web_config:save_config:54 - [15:15:46] Successful save config to: C:\Ai\Larma-cleaner\lama-cleaner\installer_config.json

Screenshots
When i run the win_start.bat the error happened

System Info
Software version used

iopaint: no idea
pytorch: 1.13.1
CUDA: 11.7
Window 11
Python 3.10.6

Please download the IOPaint.zip file, this error should have been fixed.

Please download the `IOPaint.zip` file, this error should have been fixed.

I've purchased one click installer long time ago and they don't have ioPaint included in the zip.
been using it on my laptop is fine. But when i transported to my Desktop this error showed up

Please download the `IOPaint.zip` file, this error should have been fixed.

i've purchased one-click installer long time ago. luckly i found the reciept to get the iopaint.zip so the problem is now resolved


Add E-mail to social media list

Description
LinkFree will mostly be used for professional contact so I think that adding Emails (Gmail, Outlook, etc...) is required.
Changes
1- Added Email (in PrimeReact the icon is pi-envelope and the color is #5F6368)
2- Added my profile for tests
Screenshots

Related issues
#437

Thanks for the contribution. Unfortunately We are switching the icon library soon. So we might not need this.

@krishguptadev lets get this merged for now, it will add value straight away


Test change - DO NOT MERGE

What does this PR do?:
Summarize the changes. Are any stacks or samples added or updated?
Which issue(s) this PR fixes:
Link to github issue(s)
PR acceptance criteria:

[ ] Contributing guide
Have you read the devfile registry contributing guide and followed its instructions?
[ ] Test automation
Does this repository's tests pass with your changes?
[ ] Documentation
Does any documentation need to be updated with your changes?
[ ] Check Tools Provider
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:

/retest

/retest

@johnmcollier should we close this one?


Update GW_LISTEN

GW_LISTEN is <IP_ADDRESS>:1680 in the official Helium documentation, but GW_LISTEN is <IP_ADDRESS>:1680 in Dockerfile, refer to the link: https://docs.helium.com/solana/migration/maker-hotspot-software/#quick-reference-summary

You can already override this in the settings.toml...https://github.com/helium/gateway-rs/blob/d862bc9962866e575d7c6dd731d65cf849a586ed/config/settings.toml#L15

So why does it need an env variable in the dockerfile at all?

It technically doesn't, but changing it at this point will likely be a breaking change for some makers.

So why does it need an env variable in the dockerfile at all?

It technically doesn't, but changing it at this point will likely be a breaking change for some makers.

I'm going to close this as won't fix for now

Okay, thank you for your reply.


[Bugfix] Check if resource group exist when alter mv properties, and …

Add some UT.

[FE PR Coverage Check]
:heart_eyes: pass : 3 / 3 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/alter/AlterJobMgr.java
3
3
100.00%
[]


Multi tag values using or

Coverage decreased (-0.3%) to 93.9% when pulling 8f994b0a77652824f4bde2e988330897c8c1ad1b on multi_tag_values_using_or into b411a51d13be28441b1579c9e8e7a8307366d1ba on master.

Coverage decreased (-0.3%) to 93.9% when pulling 8f994b0a77652824f4bde2e988330897c8c1ad1b on multi_tag_values_using_or into b411a51d13be28441b1579c9e8e7a8307366d1ba on master.


Server defaults

https://issues.jboss.org/browse/ISPN-7442
https://issues.jboss.org/browse/ISPN-7444
https://issues.jboss.org/browse/ISPN-7445
https://issues.jboss.org/browse/ISPN-7446
Some important changes to ensure that we ship leaner server configurations with optimal values.
Here is an example of what the final configuration looks like:
https://gist.github.com/tristantarrant/78505d3b85f432b402b7a5733ecb274e/revisions

@ryanemerson @wburns added ISPN-7446

Done @pruivo

looks good. waiting for CI results :+1:

No related test failures in the previous run: http://ci.infinispan.org/viewLog.html?buildId=49477&tab=buildResultsDiv&buildTypeId=bt9


Missing a step somewhere - Gmail Workspace Account Authentication

I have tried on Windows, Ubuntu and via python and I still get the same errors and I am sure I am just missing something really simple. I am not getting any prompts to authorize the oAuth either via cli or on the app.
In the logs I am getting the following but trying to track it down is not giving me any leads.
Doing SMTP to Google using the port 2465 that is in the config file. I am using my workspace account which is of my own domain but it is going through Google of course.
Here are the log entries:
<-- b'530-5.7.0 Authentication Required. For more information, go to\r\n'
<-- b'530-5.7.0 Authentication Required. For more information, go to\r\n'
<-- b'530-5.7.0 https://support.google.com/mail/?p=WantAuthError kd3-20020a05622a268300b0042e09c6b82dsm2181889qtb.24 - gsmtp\r\n'
Doing some searching is not coming up with anything. I do have the project in my workspace for the API and have the client_id and client_secret
I don't have an @gmail entry in my config file but something like the example below. I've also tried the advance google entry as well and no joy.
[myuser@mydomain]
Hopefully it is something simple that i am missing.
Thanks.

Are you using a service account or a normal Gmail setup? If you're struggling to get set up it's always worth starting with the simplest method and getting that working first.

Thanks for getting back to me. I am using just the standard gmail setup using my workspace account. No service account. I created the project in google and even did web and desktop app ones and copied the ids over but no joy.
For the config entry under the account entry I have tried using my email address and also just the @domain part for the info in the brackets.
Does the entry need to be @gmail.com? My domain of course isn't a @gmail.com.
I've tried using telnet to do a test to the smtp server and all the commands but the proxy just doesn't try to authenticate. I could try using another of my normal @gmail.com accounts but I do think it would still give me the same results. Nothing in my firewall is blocking the attempts to google or anything along those lines.

What SMTP login method are you using? (If you can tell me the actual commands you're using via telnet, even better)


update to work with tutorials

Description
Updated to work with moveit2 Humble tutorial 'pick and place with moveit task constructor'
Checklist

[ ] Required by CI: Code is auto formatted using clang-format
[ ] While waiting for someone to review your request, please consider reviewing another open pull request to support the maintainers

I don't understand what this is doing and this PR seems to be inactive. Please open a new PR and explain your changes in the description


#124 Upgrading lombok and maven-failsafe to become OpenJDK-10+ compatible

How to test

Execute integration test suite:

$> mvn clean verify -DskipIntegrationTests=false

Execute UnitTest and compile the package

$> mvn clean package

Additional notes
Details of the machine used to launch the above steps:
uname -a
Linux ggarrido-laptop 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$> java --version
openjdk 11.0.6 2020-01-14
OpenJDK Runtime Environment (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1)
OpenJDK 64-Bit Server VM (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1, mixed mode, sharing)

$> mvn --version
Apache Maven 3.6.0
Maven home: /usr/share/maven
Java version: 11.0.6, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-76-generic", arch: "amd64", family: "unix"

Thanks!


PWA feature - problem with Google Oauth authentication (and probably other similar systems)

Current Behavior
I am not 100% certain that the below description is completely correct, but I am fairly sure it is close.
I use Cloudflare ZeroTrust with Google Oauth authentication to access the editor at nodered.mydomain.com, and nodered.mydomain.com/dashboard to access the dashboard from Android.
Before the PWA capability, if re-authentication was required, reloading the dashboard page (by swiping down in Android) attempted to reload the dashboard and I was redirected to the Google login screen by Cloudflare so I could login and then the dashboard loaded.
Now, with the PWA version, if the authentication has expired then it appears that I just get a blank screen and there does not seem to be a way of forcing a reload so I am stuck.
To recover the situation I have to browse to the node-red root url (not the dashboard) and then I get the login screen before the editor opens. Then if I go back to the dashboard application it opens ok.  Currently there is no way of adding a shortcut to the dashboard to the home screen in Android, other than via a PWA application.
This has been discussed in PR #708 and in forum post Add PWA Functionality by cgjgh · Pull Request #708 · FlowFuse/node-red-dashboard · GitHub where @TotallyInformation suggested:

It sounds like the client code needs to have something that picks up a 401 response code from a client request and triggers a standard redirect to an endpoint defined in the D2 config.

Expected Behavior
No response
Steps To Reproduce
No response
Environment

Dashboard version: 1.8.1
Node-RED version: 4.0.0-Beta.2
Node.js version:
npm version:
Platform/OS: Server on Ubuntu or Pi OS
Browser: Chrome and Brave on Android phone

Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate

I have done some further tests and I am now sure that my initial analysis was correct. I have amended the description accordingly.
At the very least it would be helpful if there were a setting to disable the PWA feature so that a normal shortcut can be used to open the dashboard url.

@colin,
I am not a PWA expert, but I 'think' it is not as easy like that.  For example I have asked @cgjgh
if he could make my web-push node PWA compliant (see here, since D2 has now become a PWA app.  So turning it off (if possible) would have a lot of impact.

There must be a recognised solution to this problem, it is not specific to node-red to require re-authentication like this.

@colinl I use Authentik, a self-hosted auth provider with Google OAUTH as a social login option in front of NodeRed. In Chrome on Windows I tried to replicate this issue by removing session cookies from Dashboard in an attempt to emulate session expiration. It did indeed act in the manner you described: blank screen on Dashboard (reloading dashboard didn't work), but navigating to NodeRed editor redirected to OAUTH login as it should. After logging in, Dashboard worked again.
Dev console in Chrome showed the following error when Dashboard blank screen appeared:
Access to fetch at 'https://example_authentik_oauth_server.com' (redirected from 'https://example_nodered_instance.com/dashboard/_setup') from origin 'https://example_nodered_instance.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Wondering if your dev console shows the same when your session expires or if it's unrelated. Side note: I've set my session expiration in Authentik to 4 weeks which is probably why I never noticed this.

I had not tried it on the PC (I normally access via the local network on the PC).  I have now done so, using Edge, and when I get the blank screen I see in the developer tools
auth error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
The CORS error makes some sense, but what this error means I have no idea.
In Brave it works ok, but I note that Brave does not have the Install App option.

@cgjgh would it be difficult to provide a setting in settings.js (for example) that disabled this feature, reverting to the previous Add to Home Screen option?  Unless someone has a fix for the fundamental problem.

To be able to disable PWA dynamically after Vite build, from my tests all that would be necessary is to encase line 32 of main.mjs in a condition like so:
if (enablePWA) {
// register service worker
    registerSW({ immediate: true })
}

Also browser cache needs to be cleared and PWA removed.
Then you could make enablePWA configurable in D2 ui-base. Not quite sure how to at the moment. @joepavitt could you give some quick pointers on this? Reconnection notification config option could also be added.

Getting reports that this is also an issue with FlowFuse authentication too

Have people getting the CORS issue configured CORS for Node-RED? If not, the defaults would likely block you. That's what CORS does after all. It is by design.
Re the not JSON issue, that will be because some server is delivering HTML on the error.

Have people getting the CORS issue configured CORS for Node-RED? If not, the defaults would likely block you. That's what CORS does after all. It is by design.

Not sure, I've not had a chance to reproduce/investigate entirely, but white/blank pages at the point of authentication, and needing to revert back to FlowFuse platform in order to re-activate the Dashboard is the current report. Which aligns with what @colinl was seeing in the PWA behaviour with his OAuth

Have people getting the CORS issue configured CORS for Node-RED?

I cannot find how to do that. Can you elucidate please?

Hi
Just tries this yesterday and was having issues with login after added the app to home screen.
In my case, I have the Node-Red sites behind nginx, just add to add a couple of directives to the configuration
server {
  listen ***.***.com:**** ssl http2;
  server_name ***.***.com:****;

  # See https://ssl-config.mozilla.org/#server=nginx&version=1.18.0&config=intermediate&openssl=1.1.1k&hsts=false&ocsp=false&guideline=5.6see https://ssl-config.mozilla.org/#server=nginx&version=1.18.0&config=intermediate&openssl=1.1.1k&hsts=false&ocsp=false&guideline=5.6
  ssl_session_timeout 1d;
  ssl_session_cache shared:MozSSL:10m; # about 40000 sessions
  ssl_session_tickets off;
  ssl_protocols TLSv1.2 TLSv1.3;
  ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
  ssl_prefer_server_ciphers off;

  ssl_certificate /etc/letsencrypt/live/***/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/***/privkey.pem;

  location / {
    # CORS Related, not sure if everything is necessary
    if ($request_method = 'OPTIONS') {
        add_header 'Access-Control-Allow-Origin' '*';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
        #
        # Custom headers and headers various browsers *should* be OK with but aren't
        #
        add_header 'Access-Control-Allow-Headers' 'DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range';
        #
        # Tell client that this pre-flight info is valid for 20 days
        #
        add_header 'Access-Control-Max-Age' 1728000;
        add_header 'Content-Type' 'text/plain; charset=utf-8';
        add_header 'Content-Length' 0;
        return 204;
     }
     if ($request_method = 'POST') {
        add_header 'Access-Control-Allow-Origin' '*' always;
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS' always;
        add_header 'Access-Control-Allow-Headers' 'DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range' always;
        add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range' always;
     }
     if ($request_method = 'GET') {
        add_header 'Access-Control-Allow-Origin' '*' always;
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS' always;
        add_header 'Access-Control-Allow-Headers' 'DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range' always;
        add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range' always;
     }
    # End of CORS
    proxy_pass http://<IP_ADDRESS>:***;
    proxy_http_version 1.1;

    proxy_buffering off;
    proxy_request_buffering off;
    proxy_redirect off;

    proxy_set_header Host $http_host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    proxy_connect_timeout 3m;
    proxy_send_timeout 3m;
    proxy_read_timeout 3m;

    client_max_body_size 0; # Stream request body to backend
  }
}

It seems to have solved the issue, at least if using Basic Authentication it seems to be working now.

The above will only work with servers you're in control of though...
Here's a solution that seems to work with my auth setup: (@colinl wondering if you can try and replicate this)
In line 74 of main.mjs set dashboard setup fetch request to no-cors:
// GET our SocketIO Config from Node-RED & any other bits plugins have added to the _setup endpoint`
fetch('_setup', { mode: 'no-cors' })`

Then in the catch statement of the fetch request on line 177:
 console.log('auth error:', err)
 console.log('redirecting to:', window.location.origin + '/dashboard')
 window.location.replace(window.location.origin + '/dashboard')

This will redirect to dashboard root on error which will then be redirected to auth.
My theory on why the blank screen error occurs is the setup request to NodeRed fails when session has expired. In PWA app this results in dashboard never loading while also not providing a way to reload or navigate away which would presumably fix the problem. Since PWA loads the webpage from cache, it (maybe) doesn't know that session has expired, and only the setup request fails.
To be clear the above is only a proof of concept, ultimately you would probably make a CORS preflight request and catch the error there before making the setup request which would remain CORS enabled.

@colinl wondering if you can try and replicate this

I will give it a go.  Will have to wait for the situation to arise before knowing whether it sorts it, which may take a few days.

The changes made to the nginx conf, didn't work. The behaviour becomes even more erratic.
After adding the APP to the home screen, sometimes it stops working after one hours, other times after more than one day. And when it stops working in the shortcut in home screen even in the browser doesn't open. The surest way to recover is either to delete the browsing data, or to purposely entering a wrong URL (ex: /dash instead of /dashboard).
Now that i have updated more instances to V1.8.x or greater, is even happening on the PC browser (although very rarely) but in this case the workaround is simpler... CTRL + F5.

When you say it stops working, exactly what is the symptom that you see?

I am afraid the change doesn't work for me, at least on the laptop.  The google auth has expired and now it is stuck in a loop continuously redirecting to /dashboard.

It starts doing on the PC browser the same as in android, when using the PWA App (Added to Home-screen) showing a blank screen.
In the network manager, the request for _setup was coming as "unauthorized"/"error".
In the meanwhile i have removed all the extra settings in the nginx.conf and it seems to have returned to normal.
For now, going to forget the PWA option, add to screen or install App (although only one or twice the popup to install app has shown in android) until this get fixed.
Did not attempt to perform the changes suggested by cgjgh, I am only mentioning the nginx.conf changes that I had suggested previously.

On Android, the google auth having expired, with the suggested mods, I just get the blank screen again.  I don't know whether it is also permanently redirecting or not.

You're not alone in seeing that @arturv2000 - it does appear PWA stuff has completely broken any Dashboard 2.0 behind an authentication layer - it's very high up on my list of investigate this in more detail

I am unable to reproduce any blank screens with my setup which is behind Authentik auth provider as I mentioned. I should mention however that my D2 build is using an updated version of Vite-PWA and Vue as is currently being used in Vite-PWA project scaffolding. I didn't want to make another PR with these changes as PWA future seemed uncertain.
If anyone would like to test the exact version I'm using here it is: https://github.com/cgjgh/node-red-dashboard/tree/PWA-Update

@cgjgh Just tried to replace the dashboard by the version you have, and continue to have the same problem.
With my setup (using Windows with Edge or Chrome for browser) and the Node-Red in a Linux server using nginx as reverse proxy.
The way I am at the moment to reproduce this is:

Let's assume we are accessing the dashboard normally
Close all the browser windows (in case of google chrome also close/exit  from the chrome icon in the system tray)
Open again the browser
Access the dashboard, it will stay a blank page until I force a refresh Shift + F5 or Ctrl + F5. In android is necessary to clear the "Cookies and site Data"

If I don't exit the browser (complete exit, close all instances of the process), it seems to kept working for a long time (at least up to 8 hours).

Just a small update
With this new version, and adding indication in nginx to disable cache
# kill cache
add_header Last-Modified $date_gmt;
add_header Cache-Control 'no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0';
if_modified_since off;
expires off;
etag off;

And opening the page and going to developer tools and force disable cache and making a few Ctrl+F5, then untick the disable cache. On PC (Windows - Edge and Chrome) seems to be working, when stating a browser session from a new browser process it always request the login and it load the page. Sometimes even appear a small popup windows indicating a new version available with the option to reload. Have seen this in other websites, seems to be a way to handle browser cache.
On Android, it is more tricky, it enters in a "loading loop" as Colin described before. The login popup shows again if we put a wrong address, like dashb, and after that going to dashboard. But if close the window (and remove chrome from the android background apps), it happens again when reopening the browser and entering the URL. Even if I clear the browser cache after successful login, after closing / removing from background it happens again.

New version pop up is a feature of the PWA, prompt to update. I enabled it to allow for better transparency when new versions available instead of automatically updating. It should only appear on every new Vite build.
Another pop up you should be getting after a couple seconds is App is offline ready which signifies that service worker has completed precaching of files.
Can you navigate to the line where error occurs in the image?
Also, can you tell me the steps I can take to recreate your setup in Docker for example?

@cgjgh Ok, demo took way less time than anticipated.
Was able to "touch" the server. I started by deleting the node_module folder inside node-red user folder, and also deleted node_modules where I had cloned you git repo. Also restored the nginx conf to the default one required for Node-Red site.
After installing everything and building the app, and uninstall original dashboard and install the new compiled one, on Windows (Browser Edge) is not showing any problems, it loads correctly the page and if I exit the browser and try to open again it works (after reopening the browser it requests again the authentication.
Regarding android, it enters the white page and loading loop.
In the meanwhile, via stackoverflow i think i found the solution for android.
But it seems to only work if i make npm run build:dev.
In the file main.msj in the `catch('err)' where was this line:
window.location.replace(window.location.origin + '/dashboard')

replaced by:
 window.location.href = window.location.origin + window.location.pathname + window.location.search + (window.location.search ? '&' : '?') + 'reloadTime=' + Date.now().toString() + window.location.hash;

And now in android (chrome browser) is working, if build:dev. if build normal, it returns to the white page and loading, and the url after a while is something likehttps://xxxxxxx.com:1111/dashboard/?&reloatTime=121212121212&reloadTime=121212121212......
And also find out why the install app wasn't showing. I am modifying the icons and site.webmanifest for my own icons, and the site.webmanifest didn't have the name, short_name and start_url defined.

@arturv2000 What happens if you make an endpoint in nodered with http in node and make the response a 302 redirect to your dashboard?
Example:
[{"id":"b4c8d8f441022d6d","type":"http in","z":"3d14fb98ea740a0b","name":"Auth Endpoint","url":"/auth","method":"get","upload":false,"swaggerDoc":"","x":310,"y":760,"wires":[["e80bf2a236fbfcf1"]]},{"id":"e80bf2a236fbfcf1","type":"http response","z":"3d14fb98ea740a0b","name":"Redirect to /dashboard","statusCode":"302","headers":{"Location":"http://localhost:1880/dashboard"},"x":550,"y":760,"wires":[]}]

Change location in response node to dashboard url.

Then in the catch block set the window.location.replace URL to that endpoint.

 When I am almost finishing it someone disturbs me and when I look again to the PC assume that is completed.
Regarding the last UPDATE, the last code example works in Android (chrome) and with build in RELEASE mode.
Apparently that forces the browser to receive a query parameter, and if the parameter is not know/cache forces the browser to make a request that should answer with error by the server that redirects to the original page.

My apologies for the oversight and thank you for your continued work on the issue.🙂
So, if I were to provide a brief summary, would I be correct in saying that the code from my branch PWA Update works as is on PC Windows, but on Android still requires the anti-caching URL:
window.location.replace(window.location.origin + '/dashboard' + '?' + 'reloadTime=' + Date.now().toString() + Math.random());

Can I update the branch then to include this fix and/or submit a PR to address the blank screen issue?

In my current use case, yes it seems to be working.
The use case is:

Node-Red Dashboard using the cgjgh PWA-Update branch with the modification indicated bellow
Node-Red is being served by nginx as reverse proxy, nginx supposedly with default configuration required for Node-Red (I think I copied from the forum somewhere)
SSL enabled

NOTE: As indicated before, if trying to use this branch is recommended to clear browser cache for the test domain before attempting. Not sure if necessary since initially wasn't really working.
Have the PWA app installed on android phone (Android 13) and tablet (Android 14) since yesterday evening and they are still opening without issues. The same for Edge and Chrome browser on Windows, and on Linux (raspberryPi) Firefox and Chromium.
Not sure about IOS no way of testing at the moment.
The changes I made to your code where the following:
    .catch((err) => {
        console.log('auth error:', err)
        console.log('redirecting to:', window.location.origin + '/dashboard')
        //window.location.replace(window.location.origin + '/dashboard') //Original, seems to have no issues with Edge and Chrome on Windows, doesn't work on Android (Not tested on Linux browser)
        //window.location.href = window.location.origin + window.location.pathname + window.location.search + (window.location.search ? '&' : '?') + 'reloadTime=' + Date.now().toString() + window.location.hash; // Also works on Edge + Chrome on windows, doesn't work on android

        window.location.replace(window.location.origin + '/dashboard' + '?' + 'reloadTime=' + Date.now().toString() + Math.random()); //Seems to work on Edge and Chrome on Windows Chromium and Firefox on Linux, and also on Chrome Android (an also as PWA App)
    })

Only changed the .catch((err) handler and replaced the redirect.
Never tried even on Windows without any redirect.

@arturv2000 Ok, I’ll update the branch with your changes. Thank you again for the work you’ve done.

I have installed this version of node-red-dashboard in two more instances (have three total with this version) and they all seem to be working correctly either in PC or Android.
One question regarding the PWA's.
I have several instances of Node-Red running in the same server, each one is a specific TCP Port (1880, 1881, 1882, etc...).
Is It possible to install one PWA for each instance in the smartphone?
At the moment it seems that is not possible, since if I install the PWA for instance in port 1880 when accessing site on port 1881 it doesn't give the option to install the PWA, only to open the previous installed PWA.
For what I could understand in order to do this there have two options, one register the service worker differently for each app (scope), or using different subdomains for each app (sub1.mysite.com:1881/dashboard and sub2.mysite.com:1882/dashboard)
Is my understanding correct?
Thank You

@arturv2000 Different subdomains for each node red instance works. I currently have nodered.mydomain.com/dashboard and nodered2.mydomain.com/dashboard installed as PWA.
I would have imagined that mydomain.com:1880/dashboard and mydomain.com:1881/dashboard should work too but haven’t tested.

@colinl @arturv2000 seems to have had success with his deployment of D2 with the above-mentioned branch. Would you be willing to conduct an additional test using this branch to increase confidence that it functions correctly with various deployment scenarios?
If not, I'll just go ahead and ask @joepavitt to make a PR.
https://github.com/cgjgh/node-red-dashboard/tree/PWA-Update

Yes. I have been tied up for a few days. Hopefully will try it today.

Can you confirm please that to pick up your modified code I can
git clone https://github.com/cgjgh/node-red-dashboard
Then in the cloned directory
git checkout PWA-Update
I did that then npm install, npm run build, then uninstall the flowfuse dashboard and install from that folder, then restart node-red.  I ask because, having done that, odd things are happening.

@colinl Yes that is what I did in for my tests.
On Android and on the PC, I also cleared the browser cache/data/cookies for the server domain and uninstall the PWA APP, Otherwise it seems that sometimes I was getting the old version instead of the new one.

Thanks.  In fact I also had caching problems, I had to login to my cloudflare account and clear the cache there, as it was not picking up a new version of a contributed ui node that I am developing. I have opened a question about that on the forum. https://discourse.nodered.org/t/is-there-an-issue-with-cache-headers-for-umd-js-file-in-contributed-d2-ui-nodes/88123

@colinl Saw your post too late. Know you need a while to check if blank screen is fixed, but did you get it running?

Yes, it is all running. Will see what happens when the token expires.

If not, I'll just go ahead and ask @joepavitt to make a PR.

You'll need to create the PR yourself please as the origin of the code change is your branch/repo. I can then review accordingly. There has been a lot of traffic here, would be great to see a summary on the PR of the. changes and why they were required.

It is looking good. On both Android and Edge browser, google expired and it asked me to login as it should.
Great work, thanks.
I do still occasionally get the permanent connection failed message, but that is a different issue.

@colinl That’s great to hear.
@joepavitt Excuse my imprecise wording. I was trying to convey that given the issues with PWA, I wanted to get your approval for initiating the PR which will potentially further integrate PWA into D2. As of now PWA issues seem to be mostly resolved. Do you then approve going further with the PR?

Do you then approve going further with the PR?

If any incoming PR can fix the issue users are facing, then I'm all for it.

Just want to mention this here: https://eu1.hubs.ly/H09ddSP0
We're hiring for a full-time developer to work on Dashboard 2.0 if anyone in this thread is interested


Move files from azure repo

Docs Build status updates of commit bc83cd5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azure-fluid-preview-pr/breadcrumb/toc.yml
:white_check_mark:Succeeded

azure-fluid-preview-pr/fluid/fluid-authorization.md
:white_check_mark:Succeeded
View

azure-fluid-preview-pr/fluid/fluid-jwtoken.md
:white_check_mark:Succeeded
View

azure-fluid-preview-pr/fluid/fluid-quickstart.md
:white_check_mark:Succeeded
View

azure-fluid-preview-pr/fluid/index.yml
:white_check_mark:Succeeded
View

azure-fluid-preview-pr/fluid/overview.md
:white_check_mark:Succeeded
View

azure-fluid-preview-pr/fluid/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[WIP] Raft uses a unique protocol for each execution request

Closing until prerequisites for this are met.


feat: Add variable for service endpoints for infra subnet

Adds a variable + local for service endpoints for the infra subnet

Allows enabling things such as Microsoft Keyvault access to the subnet easily. Currently, otherwise, the solution might entail something such as a Bash script that does so manually via Azure CLI after this module has been ran.

Removed the specific validation to match requested change in #245


Add Alpakka Kafka

Alpakka Kafka https://github.com/akka/alpakka-kafka/ (aka akka-stream-kafka) could be included it builds for both 2.12.8 and 2.13.0 (by excluding a few tests that need an embedded Kafka broker).
Lagom depends on Alpakka Kafka (relevant for #846)

let's tackle this!

let's discuss the gory details on the new PR, #969


Parachute in multiplayer doesn't spawn

My friend and I tested this mod today on our unit's dedicated server. We tested this on a C130J from the mod RHSUSAF. All the interaction appeared, but during the jump the parachute never spawned.

Was everyone running the mod?


Short figure caption for outline

Description
Allow adding an optional short caption to be displayed in the outline
Use Case
When adding a caption to a figure, the text might be quite long, in particular, when the figure contains a table or (multiple) images that require explanation. The entire caption text is automatically added to the outline, which may look really messy, depending on the text length.
In the caption package of LaTeX, one can add an argument <list entry> (kind of a short caption), that shows up in the outline instead of the <heading> (i.e. the actual caption), if given: \caption[⟨list entry⟩]{⟨heading⟩}. If no <list entry> is given, the <heading> is shown in the outline (as is happening now in typst) and if it is given, but left empty ( \caption[]{⟨heading⟩}) , no entry will be made in the outline.

I propose changing the heading.outlined type from boolean to string/none. This modification will enable the Table of Contents (ToC) to display a specified string if it is not set to none.

But then, if it is none is it not showing or is it using the long caption?

See also: https://github.com/typst/typst/pull/1892#issuecomment-1729119959

Here's an idea for a workaround while this isn't implemented yet:
#let outlined-figure(
	contents,
	label-name,
	placement: auto,
	caption: none,
	outline-caption: none,
) = [
	#if outline-caption != none [
		#show figure: it => it.counter.update(v => v - 1)
		#figure(contents, caption: outline-caption)
	]
	#figure(
		contents,
		placement: placement,
		caption: caption,
		outlined: outline-caption == none,
	) #label(label-name)
]

Seems to work and produce the desired result (as far as I can tell).

This works for me. Thank you!!

Here is another solution that is maybe a little bit less cursed:
#let in-outline = state("in-outline", false)
#show outline: it => {
  in-outline.update(true)
  it
  in-outline.update(false)
}

#let flex-caption(long, short) = locate(loc =>
  if in-outline.at(loc) { short } else { long }
)

Which can then be used like this:
#outline(title: [Figures], target: figure)

#figure(
  rect(),
  caption: flex-caption(
    [This is my long caption text in the document.],
    [This is short],
  )
)

Here is another solution that is maybe a little bit less cursed:
#let in-outline = state("in-outline", false)
#show outline: it => {
  in-outline.update(true)
  it
  in-outline.update(false)
}

#let flex-caption(long, short) = locate(loc =>
  if in-outline.at(loc) { short } else { long }
)

Which can then be used like this:
#outline(title: [Figures], target: figure)

#figure(
  rect(),
  caption: flex-caption(
    [This is my long caption text in the document.],
    [This is short],
  )
)

Working nicely 😄 . Also works for headings:
#heading(level:1, flex-caption(
  [ a ver long title a ver long title a ver long title  ],
  [my short one])
)

Thank you so much!!

Here is another solution that is maybe a little bit less cursed:
#let in-outline = state("in-outline", false)
#show outline: it => {
  in-outline.update(true)
  it
  in-outline.update(false)
}

#let flex-caption(long, short) = locate(loc =>
  if in-outline.at(loc) { short } else { long }
)

Which can then be used like this:
#outline(title: [Figures], target: figure)

#figure(
  rect(),
  caption: flex-caption(
    [This is my long caption text in the document.],
    [This is short],
  )
)

For future reference - this can (obviously) also be used to omit citations inside figure outlines.
#outline(title: [Figures], target: figure)

#figure(
  rect(),
  caption: flex-caption(
    [Some figure showing x @somesource], //Display caption including citation
    [Some figure showing  x], //Caption without citation used in the outline
  )
)

Hi all — I'm new to Typst, so if I should check out some more documentation on my own, please don't hesitate to tell me "just read [XYZ]"!
But I was curious if the new "context" introduced in 0.11.0 will be able to improve the current workaround? I tend to think it can, but I am not entirely sure how. Any advice?

But I was curious if the new "context" introduced in 0.11.0 will be able to improve the current workaround?

Yes, it would now look like this:
#let flex-caption(long, short) = context if in-outline.get() { short } else { long }


Target class [files] does not exist

After replacing Illuminate\Filesystem\FilesystemServiceProvider::class in providers list. I'm getting below error.
In Container.php line 811:

  Target class [files] does not exist.

It used to work on Laravel 5.8 version. But, after upgrading to Laravel 7.x it is throwing the error.
I've done little research on the error, and as per this issue https://github.com/laravel/framework/issues/35120 the service provider is not really registering the file system.
By going through the core file system https://github.com/laravel/framework/blob/7.x/src/Illuminate/Filesystem/FilesystemServiceProvider.php I found the below statement is missing in FlysystemOtherServiceProvider.
$this->app->singleton('files', function () {
            return new Filesystem;
});

Interesting. I wonder what they changed that made it stop working. I'll see about adding that.

Based on the code I'm looking at, this should still work as expected... The FlysystemServiceProvider extends Illuminate\Filesystem\FilesystemServiceProvider, making it register all its own services except the replacement FlysystemManager...

Yes, it should have worked. I don't know some reason, it looked like the application was not at all recognising the service provider. If I replace with default provider, it works.
Not sure it is only happening in my application or not. I'll check it with a bare L8 application when I get time.
For time being I've extended default file file system in my application. As I'm only using the http additional driver.


Command Line Script does not work on windows Python 3.2

C:\Users\Alex\test>markdown_py test.txt
Traceback (most recent call last):
File "C:\Users\Alex\python32\Scripts\markdown_py", line 34, in
run()
File "C:\Users\Alex\python32\lib\site-packages\markdown_main_.py", line 81,
in run
markdown.markdownFromFile(**options)
File "C:\Users\Alex\python32\lib\site-packages\markdown_init_.py", line 426
, in markdownFromFile
kwargs.get('encoding', None))
File "C:\Users\Alex\python32\lib\site-packages\markdown_init_.py", line 364
, in convertFile
output_file.write(html)
File "C:\Users\Alex\python32\lib\codecs.py", line 356, in write
self.stream.write(data)
TypeError: must be str, not bytes

Well, it works fine on Windows Python 3.2 as a python library (we are a lib first & script second). However, yes, it appears that there is a bug in the command line wrapper script. I've changed the title to better reflect the problem. Thanks for the report.


Adding Jekyll tutorial

Fixing Issue #3622
Description
This pull request adds a comprehensive Jekyll tutorial to the documentation. The tutorial covers the basics of setting up a Jekyll site, creating posts and pages, using templates and layouts, and customizing the site with themes and plugins. It also includes examples and step-by-step instructions to help beginners understand and build their own Jekyll sites.
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Security enhancement
[ ] Other (specify): _______________

Checklist

[x] I have performed a self-review of my code.
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have followed the code style guidelines of this project.
[x] I have checked for any existing open issues that my pull request may address.
[x] I have ensured that my changes do not break any existing functionality.
[x] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
[x] I have read the resources for guidance listed below.
[x] I have followed security best practices in my code changes.

Additional Context
This Jekyll tutorial includes:

Setting up a Jekyll development environment.
Creating and managing posts and pages.
Using and customizing templates and layouts.
Applying themes and integrating plugins for added functionality.
Step-by-step instructions and examples for beginners to get started with Jekyll.

Resources for Guidance
Please read the following resources before submitting your contribution:

[x] Code Harbor Hub Community Features
[x] Markdown Guide

@Ajay-Dhangar sir, kindly review and please let me know if any changes required.


result

It is hard to tell from just one image. Maybe you can tell me the hyperparameters you used in training and how many epochs the model was trained on. Furthermore, there might be a natural variance in the weights during training, so be sure you are testing the best model according to the validation data.

The parameters have not changed, I changed the batch_size to 2, epoch to 200, and you give 4 and 100.

Why did I start training from epoch=96 after loading the pre-trained model to start training? Thank you

Why did I start training from epoch=96 after loading the pre-trained model to start training? Thank you

This happens when you use a checkpoint, epoch=96 is most likely the epoch where the pre-trained model got the best weights.


Feature: Unsafe sign by hash

Fix error code conflicts
Impl unsafe sign by hash

Test Data:
e005000035058000002c800000c3800000000000000000000000abfcd07e44a6bfc18efb18062c8e588c34f187e3d2b286d4411781acdf6692eb

PTAL @fbsobreira


Parameterized stored procedures wrong argument number

System information:

Operating system (distribution) and version
Win10/1909
DBeaver version
5.3.4, 7.0.0, 7.0.1
Additional extensions

Connection specification:

Database name and version : PostgreSQL-12.2.1
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)?

Describe the problem you're observing:
I met two issues wihen running stored procedure from the Project window>Functions tree. They have a wrong argument number, anonymous parameters (?,?) being added.
Another issue (might be a request) is about RETURNS TABLE result. See example below.
Steps to reproduce, if exist:
create table tbl (a text, b int, c int);
insert into tbl values ('one', 1, 10);

create function get_tbl (param text)
    returns table(a text, b int, c int) as $$
    begin
        return query
        select t.a, t.b, t.c from tbl t where t.a = param;
    end
$$ language plpgsql;

-- (1)
select get_tbl('one');
get_tbl   |
----------|
(one,1,10)|
-- (2)
select * from get_tbl('one');   -- or select * from get_tbl(:param);
a     |b     |c     |
------|------|------|
one   |     1|    10|

In Functions in tree > Execute Stored Procedure, I get extra params in SQL Editor:
SELECT public.get_tbl(:param,?,?,?);

Where do the "?" come from ?
How to get result as in query (2), SELECT * from public.get_tbl(:param); and get proper grid display as a record, even without opening the query the SQL Editor if optional?
Thanks!
Include any warning/errors/backtraces from the logs
NA

thanks for the bug report

Fixed

verified


SNMP v1 fixes for NoSuchName

When using retry_no_such=True for an easysnmp session, this ensures that the response is correclty aligned with the input variable list.

Thanks for all your efforts on this @nnathan, let's merge it!


New command to view contract storage state

Sometimes, it is useful to inspect raw contract storage state even though near-sdk-rs uses borsh to serialize keys and values.
near CLI JS has near view-state <account-id> [OPTIONAL_STORAGE_KEY_PREFIX] command, and I initially planned (#128) to implement it in a separate "dev" extension, but now I feel this raw viewing mode belongs here.
near contract view-storage <contract-account-id> all network-config testnet now
near contract view-storage <contract-account-id> keys-start-with-string "S" network-config testnet now
near contract view-storage <contract-account-id> keys-start-with-bytes-as-base64 "Uw==" network-config testnet now

I also take this, please leave it to me. Thanks.


Add support for loading cubemaps from DDS files

Hello there, I don't have a test for this on zig-gamedev, but we're using this code for Image-Based Lighting for Tides of Revival and it seems to work fine :)

Thanks!
I like this pattern for settings like this:
    pub fn createAndUploadTex2dFromDdsFile(
        gctx: *GraphicsContext,
        relpath: []const u8,
        args: struct {
            is_cubemap: bool = false,
        },
   )

This gives us ability to provide a default value and also is easier for the user to read on the call site.
createAndUploadTex2dFromDdsFile(..., .{ .is_cubemap = true });

We use this pattern for createAndUploadTex2dFromFile() function.

Oh nice, I like it too. Changing it now :)


Maybe add the ability to run lua scripts on the menu?

What feature do you want to get added on the base engine?
I wouldn't actually know since I don't work with haxe but I'd imagine that this shouldn't be too difficult to do (assuming it hasn't been already implemented and I'm not just a stupid idiot) but I feel like being able to run lua scripts on the menu so you can add neat menu stuff without using source code would be cool
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

they will add a stage editor, but 6K+ or winning icons are a no for them

I don't have plans for that at the moment.


IE8 tile loading bug

Can you look at leaflet (master branch) in IE8? Tiles sometimes freeze and stop loading after several drags and zooms. It looks like:

Windows XP, Service Pack 3, IE8

I can reproduce this with latest master on IE8/Win7 (virtual machine from MS in Virtual Box) with the /debug/map/map.html example.
An interesting question is if Leaflet still aims to support IE8, which starts to get really old, and it seems some libraries are dropping support for it.
I'll try to have a look, but given the state of IE8 debugger, I can't promise anything :)

Yeah, Leaflet still has to support IE8 since A LOT of government/enterprise apps depend on this. Thanks for looking into this.

Follow up: I ran the test specs on IE8, and there are quite a few errors. Some of them appear in GridLayer, which I guess might be the issue we're seeing here.

So far, I've found out that the tiles load, but for some reason the leaflet-tile-loaded class is never applied to the element. I'll try to find some more time to dig into why.
As a side note, this issue can be debugged in IE11 if you set the debugger's document mode to IE8, which makes things a lot easier.

I think I've managed to pinpoint the bug, here is a possible solution: #3346

@RLRR thanks a lot! Merged.


can we just load any .ply file in the viewer

let's say if i just want to visualize the results can i load it direclty in the viewer the .ply file and also if there is other way to load it with other supported files

I'd also be interested in this - is it currently possible to load a .ply file from any of the above viewers into NeRFStudio?


Improve testing workflow

Describe testing workflow in readme or similar
Add unit tests where sensible
Create test bots/scripts that test every feature

So far I have added a few regression tests to ensure bugs I got during development don't show again


main.py: error: unrecognized arguments: --queries-offline 20

I was trying to run GettingStarted.ipynb in v0.5/classification_and_detection directory, but when running the cell at step 4:
!./run_local.sh onnxruntime mobilenet cpu --accuracy
I get the following error message: main.py: error: unrecognized arguments: --queries-offline 20
I have defined the directories as follows in step 3:
os.environ['MODEL_DIR'] = 'mobilenet_v1_1.0_224.onnx'
os.environ['DATA_DIR'] = os.path.join(root, "fake_imagenet")

I have downloaded the models and run the create fake imagenet script as well.
Is there anything that I have missed when running this notebook?

Also I have found that removing os.environ['EXTRA_OPS'] ="--queries-offline 20 --time 10 --max-latency 0.2" gives the following error message:
INFO:main:Namespace(accuracy=True, backend='onnxruntime', cache=0, config='../mlperf.conf', count=None, data_format=None, dataset='imagenet_mobilenet', dataset_list=None, dataset_path='/home/work/salt/mlperf/inference/v0.5/classification_and_detection/fake_imagenet', find_peak_performance=False, inputs=None, max_batchsize=32, max_latency=None, model='mobilenet_v1_1.0_224.onnx/mobilenet_v1_1.0_224.onnx', model_name='mobilenet', output='/home/work/salt/mlperf/inference/v0.5/classification_and_detection/output/onnxruntime-cpu/mobilenet', outputs=['MobilenetV1/Predictions/Reshape_1:0'], profile='mobilenet-onnxruntime', qps=None, samples_per_query=None, scenario='SingleStream', threads=11, time=None)
INFO:imagenet:loaded 8 images, cache=0, took=0.0sec
Traceback (most recent call last):
  File "python/main.py", line 537, in <module>
    main()
  File "python/main.py", line 430, in main
    model = backend.load(args.model, inputs=args.inputs, outputs=args.outputs)
  File "/home/work/salt/mlperf/inference/v0.5/classification_and_detection/python/backend_onnxruntime.py", line 33, in load
    self.sess = rt.InferenceSession(model_path, opt)
  File "/home/work/.local/lib/python3.6/site-packages/onnxruntime/capi/session.py", line 25, in __init__
    self._load_model(providers)
  File "/home/work/.local/lib/python3.6/site-packages/onnxruntime/capi/session.py", line 32, in _load_model
    self._path_or_bytes, True)
RuntimeError: /onnxruntime_src/onnxruntime/core/session/inference_session.cc:220 onnxruntime::InferenceSession::InferenceSession(const onnxruntime::SessionOptions&, const string&, onnxruntime::logging::LoggingManager*) status.IsOK() was false. Given model could not be parsed while creating inference session. Error message: system error number 20
Stacktrace:

Hm, I ran this many times but not recently. Are there more messages from onnx runtime ?
This is the model from zenodo and onnxruntime-1.1 ?

Yes, the model if from zenodo, onnxruntime is version 1.1.1

Could this be an error related to onnxruntime?

I've also found that removing --queries-offline makes it work, albeit resulting in an accuracy of 62.5%

--queries-offline is no longer an valid argument (guess we forgot to update the tutorial. we'll update it for v0.7).
The accuracy is not really meaningful since the tutorial uses a fake dataset with just a couple of images.

ok, thank you!


Attribute error

Traceback (most recent call last):
File "e:/uwu/wifi.py", line 4, in
command_output = subprocess.run(["netsh", "wlan", "show", "profiles"], capture_output = True).stdout.decode()
File "C:\Users\33138052\AppData\Local\Programs\Python\Python38\lib\site-packages\run_init_.py", line 145, in new
process = cls.create_process(command, stdin, cwd=cwd, env=env, shell=shell)
File "C:\Users\33138052\AppData\Local\Programs\Python\Python38\lib\site-packages\run_init_.py", line 121, in create_process
shlex.split(command),
File "C:\Users\33138052\AppData\Local\Programs\Python\Python38\lib\shlex.py", line 310, in split
return list(lex)
File "C:\Users\33138052\AppData\Local\Programs\Python\Python38\lib\shlex.py", line 300, in next
token = self.get_token()
File "C:\Users\33138052\AppData\Local\Programs\Python\Python38\lib\shlex.py", line 109, in get_token
raw = self.read_token()
File "C:\Users\33138052\AppData\Local\Programs\Python\Python38\lib\shlex.py", line 140, in read_token
nextchar = self.instream.read(1)
AttributeError: 'list' object has no attribute 'read'
Any fixes?

Well normally List methods (if i'm not wrong) don't have the read Attribute so there's the error if you use a debugger or something similar you will probably get more information. Then tell us.


Unwrap booleans.

I added a negative test for Duration, since typesafe/config does
not automatically unwrap durations.

See here for comparison with typesafe/config https://scastie.scala-lang.org/olafurpg/TUua5O3DRAunCu3jS4y1oQ

cool thanks


Traefik unable to create logs folder in docker swarm

What version of Traefik are you using (traefik version)?
1.1.2
What is your environment & configuration (arguments, toml...)?
We are running traefik as docker service in swarm mode.
What did you do?

Traefik should create the log folder '/app/logs/'  if not present.
What did you see instead?
Traefik throws following error at stdout and then redirects the logs to stdout
time="2017-03-02T04:13:55Z" level=error msg="Error opening fileopen \"/app/logs/access.log\": no such file or directory"
time="2017-03-02T04:13:55Z" level=error msg="Error opening fileopen \"/app/logs/traefik.log\": no such file or directory"
time="2017-03-02T04:13:55Z" level=info msg="Traefik version v1.1.2 built on 2016-12-15_10:21:15AM"
time="2017-03-02T04:13:55Z" level=error msg="Error opening fileopen \"/app/logs/access.log\": no such file or directory"

Same here

Fixed by #1507


Revise brake current logic.

Now we dump ALL brake current in the resistor, and if it saturates we throw a fault. This is a bit inflexible.
New design:

"Max regen current" config variable: the brake current above this level is sent to the brake resistor. This allows for controlled regen current into battries.
Make a "regen current fault level" config variable: If the brake resistor is saturated, and the regen current that still flows into the supply exceeds this level, generate a fault. This fault would superseed the current brake saturation fault.

If both of the above variables are 0.0, then the behaviour is identical to the current behaviour, so there is no loss of generality.

I don't see a real reason to use the "fault level" value.  If the regen is maxed out, AND we hit our brake saturation, then we can't do anything more and should throw a fault immediately


Add embed widget

revert of a revert so I can put it in a branch.

I'm not sure what this is doing. "Buy Tickets" just takes me to EB just like a regular link.

PR for the wrong branch, this is broken.


Signal strength CSS

I'd like to be able to change the color of my wifi indicator based on the signal strength, there seems to be no way to do that, it seems like you could just make the selector
#network.wifi.-10
for everything below 10 and
#network.wifi.+10 for everything above ten, for example.
or give a range

You can use format-icons.
per https://github.com/Alexays/Waybar/wiki/Module:-Network,
format-icons:
typeof: array/object
Based on the current signal strength, the corresponding icon gets selected.
The order is low to high. Or by the state if it is an object.

You can pass in the styling here along with the icon. I don't think you can specify the thresholds for each level, but this seems adequate.

Unfortunately that dos not allow me to pass opacity, only colors as far as I'm aware, although that does help, thanks

You can pass an alpha property if you want to set the opacity

I can't seem to get what you suggested working
"󰤟"
to
"󰤟"
and
"󰤟"
all seem to do the same thing, making the icon completely invisible, can you please give me an example? sorry!

Try using % between 1-100 for the value of alpha so for instance,
"󰤟"

That works! thank you so much, is there anywhere I can find a list of these span properties, i'm having trouble finding the waybar ones listed anywhere, i think it would be good to document this, unless i'm missing it in the documentation somewhere