Project dependencies

Working on the Client Side Processing we realized that using openeo-processes-dask and openeo-pg-parser-networkx drags in many dependencies as @soxofaan noted here:
https://github.com/Open-EO/openeo-python-client/pull/338#issuecomment-1418936710
Could we check if all of them are really used? datacube for instance is not used directly but still listed as requirement.

Ok here is the list of all the current dependencies, I see that datacube is anyway required by odc-algo:
openeo-processes-dask==2023.1.2
  - dask [required: >=2022.11.1, installed: 2022.12.0]
    - click [required: >=7.0, installed: 8.1.3]
      - colorama [required: Any, installed: 0.4.6]
    - cloudpickle [required: >=1.1.1, installed: 2.2.0]
    - fsspec [required: >=0.6.0, installed: 2022.11.0]
    - packaging [required: >=20.0, installed: 21.3]
      - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
    - partd [required: >=0.3.10, installed: 1.3.0]
      - locket [required: Any, installed: 1.0.0]
      - toolz [required: Any, installed: 0.12.0]
    - pyyaml [required: >=5.3.1, installed: 6.0]
    - toolz [required: >=0.8.2, installed: 0.12.0]
  - dask-geopandas [required: >=0.2.0,<1, installed: 0.2.0]
    - dask [required: >=2021.06.0, installed: 2022.12.0]
      - click [required: >=7.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - cloudpickle [required: >=1.1.1, installed: 2.2.0]
      - fsspec [required: >=0.6.0, installed: 2022.11.0]
      - packaging [required: >=20.0, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - partd [required: >=0.3.10, installed: 1.3.0]
        - locket [required: Any, installed: 1.0.0]
        - toolz [required: Any, installed: 0.12.0]
      - pyyaml [required: >=5.3.1, installed: 6.0]
      - toolz [required: >=0.8.2, installed: 0.12.0]
    - distributed [required: >=2021.06.0, installed: 2022.12.0]
      - click [required: >=7.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - cloudpickle [required: >=1.5.0, installed: 2.2.0]
      - dask [required: ==2022.12.0, installed: 2022.12.0]
        - click [required: >=7.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
        - cloudpickle [required: >=1.1.1, installed: 2.2.0]
        - fsspec [required: >=0.6.0, installed: 2022.11.0]
        - packaging [required: >=20.0, installed: 21.3]
          - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
        - partd [required: >=0.3.10, installed: 1.3.0]
          - locket [required: Any, installed: 1.0.0]
          - toolz [required: Any, installed: 0.12.0]
        - pyyaml [required: >=5.3.1, installed: 6.0]
        - toolz [required: >=0.8.2, installed: 0.12.0]
      - jinja2 [required: Any, installed: 3.1.2]
        - MarkupSafe [required: >=2.0, installed: 2.1.1]
      - locket [required: >=1.0.0, installed: 1.0.0]
      - msgpack [required: >=0.6.0, installed: 1.0.4]
      - packaging [required: >=20.0, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - psutil [required: >=5.0, installed: 5.9.4]
      - pyyaml [required: Any, installed: 6.0]
      - sortedcontainers [required: !=2.0.1,!=2.0.0, installed: 2.4.0]
      - tblib [required: >=1.6.0, installed: 1.7.0]
      - toolz [required: >=0.10.0, installed: 0.12.0]
      - tornado [required: >=6.0.3, installed: 6.2]
      - urllib3 [required: Any, installed: 1.26.13]
      - zict [required: >=0.1.3, installed: 2.2.0]
        - heapdict [required: Any, installed: 1.0.1]
    - geopandas [required: >=0.10, installed: 0.12.1]
      - fiona [required: >=1.8, installed: 1.8.22]
        - attrs [required: >=17, installed: 22.1.0]
        - certifi [required: Any, installed: 2022.12.7]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
        - click-plugins [required: >=1.0, installed: 1.1.1]
          - click [required: >=4.0, installed: 8.1.3]
            - colorama [required: Any, installed: 0.4.6]
        - cligj [required: >=0.5, installed: 0.7.2]
          - click [required: >=4.0, installed: 8.1.3]
            - colorama [required: Any, installed: 0.4.6]
        - munch [required: Any, installed: 2.5.0]
          - six [required: Any, installed: 1.16.0]
        - setuptools [required: Any, installed: 65.5.1]
        - six [required: >=1.7, installed: 1.16.0]
      - packaging [required: Any, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - pandas [required: >=1.0.0, installed: 1.5.2]
        - numpy [required: >=1.20.3, installed: 1.24.1]
        - python-dateutil [required: >=2.8.1, installed: 2.8.2]
          - six [required: >=1.5, installed: 1.16.0]
        - pytz [required: >=2020.1, installed: 2022.6]
      - pyproj [required: >=2.6.1.post1, installed: 3.4.0]
        - certifi [required: Any, installed: 2022.12.7]
      - shapely [required: >=1.7, installed: 1.8.4]
    - packaging [required: Any, installed: 21.3]
      - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
    - pygeos [required: Any, installed: 0.13]
      - numpy [required: >=1.13, installed: 1.24.1]
  - datacube [required: >=1.8.4,<2.0.0, installed: 1.8.9]
    - affine [required: Any, installed: 2.3.1]
    - cachetools [required: Any, installed: 5.2.0]
    - click [required: >=5.0, installed: 8.1.3]
      - colorama [required: Any, installed: 0.4.6]
    - cloudpickle [required: >=0.4, installed: 2.2.0]
    - dask [required: Any, installed: 2022.12.0]
      - click [required: >=7.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - cloudpickle [required: >=1.1.1, installed: 2.2.0]
      - fsspec [required: >=0.6.0, installed: 2022.11.0]
      - packaging [required: >=20.0, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - partd [required: >=0.3.10, installed: 1.3.0]
        - locket [required: Any, installed: 1.0.0]
        - toolz [required: Any, installed: 0.12.0]
      - pyyaml [required: >=5.3.1, installed: 6.0]
      - toolz [required: >=0.8.2, installed: 0.12.0]
    - distributed [required: Any, installed: 2022.12.0]
      - click [required: >=7.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - cloudpickle [required: >=1.5.0, installed: 2.2.0]
      - dask [required: ==2022.12.0, installed: 2022.12.0]
        - click [required: >=7.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
        - cloudpickle [required: >=1.1.1, installed: 2.2.0]
        - fsspec [required: >=0.6.0, installed: 2022.11.0]
        - packaging [required: >=20.0, installed: 21.3]
          - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
        - partd [required: >=0.3.10, installed: 1.3.0]
          - locket [required: Any, installed: 1.0.0]
          - toolz [required: Any, installed: 0.12.0]
        - pyyaml [required: >=5.3.1, installed: 6.0]
        - toolz [required: >=0.8.2, installed: 0.12.0]
      - jinja2 [required: Any, installed: 3.1.2]
        - MarkupSafe [required: >=2.0, installed: 2.1.1]
      - locket [required: >=1.0.0, installed: 1.0.0]
      - msgpack [required: >=0.6.0, installed: 1.0.4]
      - packaging [required: >=20.0, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - psutil [required: >=5.0, installed: 5.9.4]
      - pyyaml [required: Any, installed: 6.0]
      - sortedcontainers [required: !=2.0.1,!=2.0.0, installed: 2.4.0]
      - tblib [required: >=1.6.0, installed: 1.7.0]
      - toolz [required: >=0.10.0, installed: 0.12.0]
      - tornado [required: >=6.0.3, installed: 6.2]
      - urllib3 [required: Any, installed: 1.26.13]
      - zict [required: >=0.1.3, installed: 2.2.0]
        - heapdict [required: Any, installed: 1.0.1]
    - GeoAlchemy2 [required: Any, installed: 0.12.5]
      - packaging [required: Any, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - SQLAlchemy [required: >=1.4, installed: 1.4.44]
        - greenlet [required: !=0.4.17, installed: 2.0.1]
    - jsonschema [required: Any, installed: 4.17.3]
      - attrs [required: >=17.4.0, installed: 22.1.0]
      - pyrsistent [required: >=0.14.0,!=0.17.2,!=0.17.1,!=0.17.0, installed: 0.19.2]
    - lark [required: Any, installed: 1.1.5]
    - netcdf4 [required: Any, installed: 1.6.2]
      - cftime [required: Any, installed: 1.6.2]
        - numpy [required: >1.13.3, installed: 1.24.1]
      - numpy [required: >=1.9, installed: 1.24.1]
    - numpy [required: Any, installed: 1.24.1]
    - pandas [required: Any, installed: 1.5.2]
      - numpy [required: >=1.20.3, installed: 1.24.1]
      - python-dateutil [required: >=2.8.1, installed: 2.8.2]
        - six [required: >=1.5, installed: 1.16.0]
      - pytz [required: >=2020.1, installed: 2022.6]
    - psycopg2 [required: Any, installed: 2.9.5]
    - pyproj [required: >=2.5, installed: 3.4.0]
      - certifi [required: Any, installed: 2022.12.7]
    - python-dateutil [required: Any, installed: 2.8.2]
      - six [required: >=1.5, installed: 1.16.0]
    - pyyaml [required: Any, installed: 6.0]
    - rasterio [required: >=1.3.2, installed: 1.3.4]
      - affine [required: Any, installed: 2.3.1]
      - attrs [required: Any, installed: 22.1.0]
      - certifi [required: Any, installed: 2022.12.7]
      - click [required: >=4.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - click-plugins [required: Any, installed: 1.1.1]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
      - cligj [required: >=0.5, installed: 0.7.2]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
      - numpy [required: >=1.18, installed: 1.24.1]
      - setuptools [required: Any, installed: 65.5.1]
      - snuggs [required: >=1.4.1, installed: 1.4.7]
        - numpy [required: Any, installed: 1.24.1]
        - pyparsing [required: >=2.1.6, installed: 3.0.9]
    - shapely [required: >=1.6.4, installed: 1.8.4]
    - sqlalchemy [required: Any, installed: 1.4.44]
      - greenlet [required: !=0.4.17, installed: 2.0.1]
    - toolz [required: Any, installed: 0.12.0]
    - xarray [required: >=0.9,!=2022.6.0, installed: 2022.12.0]
      - numpy [required: >=1.20, installed: 1.24.1]
      - packaging [required: >=21.3, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - pandas [required: >=1.3, installed: 1.5.2]
        - numpy [required: >=1.20.3, installed: 1.24.1]
        - python-dateutil [required: >=2.8.1, installed: 2.8.2]
          - six [required: >=1.5, installed: 1.16.0]
        - pytz [required: >=2020.1, installed: 2022.6]
  - geopandas [required: >=0.11.1,<1, installed: 0.12.1]
    - fiona [required: >=1.8, installed: 1.8.22]
      - attrs [required: >=17, installed: 22.1.0]
      - certifi [required: Any, installed: 2022.12.7]
      - click [required: >=4.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - click-plugins [required: >=1.0, installed: 1.1.1]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
      - cligj [required: >=0.5, installed: 0.7.2]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
      - munch [required: Any, installed: 2.5.0]
        - six [required: Any, installed: 1.16.0]
      - setuptools [required: Any, installed: 65.5.1]
      - six [required: >=1.7, installed: 1.16.0]
    - packaging [required: Any, installed: 21.3]
      - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
    - pandas [required: >=1.0.0, installed: 1.5.2]
      - numpy [required: >=1.20.3, installed: 1.24.1]
      - python-dateutil [required: >=2.8.1, installed: 2.8.2]
        - six [required: >=1.5, installed: 1.16.0]
      - pytz [required: >=2020.1, installed: 2022.6]
    - pyproj [required: >=2.6.1.post1, installed: 3.4.0]
      - certifi [required: Any, installed: 2022.12.7]
    - shapely [required: >=1.7, installed: 1.8.4]
  - odc-algo [required: >=0.2.3,<1, installed: 0.2.3]
    - affine [required: Any, installed: 2.3.1]
    - dask [required: Any, installed: 2022.12.0]
      - click [required: >=7.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - cloudpickle [required: >=1.1.1, installed: 2.2.0]
      - fsspec [required: >=0.6.0, installed: 2022.11.0]
      - packaging [required: >=20.0, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - partd [required: >=0.3.10, installed: 1.3.0]
        - locket [required: Any, installed: 1.0.0]
        - toolz [required: Any, installed: 0.12.0]
      - pyyaml [required: >=5.3.1, installed: 6.0]
      - toolz [required: >=0.8.2, installed: 0.12.0]
    - dask-image [required: Any, installed: 2022.9.0]
      - dask [required: >=0.16.1, installed: 2022.12.0]
        - click [required: >=7.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
        - cloudpickle [required: >=1.1.1, installed: 2.2.0]
        - fsspec [required: >=0.6.0, installed: 2022.11.0]
        - packaging [required: >=20.0, installed: 21.3]
          - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
        - partd [required: >=0.3.10, installed: 1.3.0]
          - locket [required: Any, installed: 1.0.0]
          - toolz [required: Any, installed: 0.12.0]
        - pyyaml [required: >=5.3.1, installed: 6.0]
        - toolz [required: >=0.8.2, installed: 0.12.0]
      - numpy [required: >=1.11.3, installed: 1.24.1]
      - pims [required: >=0.4.1, installed: 0.6.1]
        - imageio [required: Any, installed: 2.22.4]
          - numpy [required: Any, installed: 1.24.1]
          - pillow [required: >=8.3.2, installed: 9.2.0]
        - numpy [required: >=1.19, installed: 1.24.1]
        - slicerator [required: >=0.9.8, installed: 1.1.0]
      - scipy [required: >=0.19.1, installed: 1.9.3]
        - numpy [required: >=1.18.5,<1.26.0, installed: 1.24.1]
    - datacube [required: >=1.8.5, installed: 1.8.9]
      - affine [required: Any, installed: 2.3.1]
      - cachetools [required: Any, installed: 5.2.0]
      - click [required: >=5.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - cloudpickle [required: >=0.4, installed: 2.2.0]
      - dask [required: Any, installed: 2022.12.0]
        - click [required: >=7.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
        - cloudpickle [required: >=1.1.1, installed: 2.2.0]
        - fsspec [required: >=0.6.0, installed: 2022.11.0]
        - packaging [required: >=20.0, installed: 21.3]
          - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
        - partd [required: >=0.3.10, installed: 1.3.0]
          - locket [required: Any, installed: 1.0.0]
          - toolz [required: Any, installed: 0.12.0]
        - pyyaml [required: >=5.3.1, installed: 6.0]
        - toolz [required: >=0.8.2, installed: 0.12.0]
      - distributed [required: Any, installed: 2022.12.0]
        - click [required: >=7.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
        - cloudpickle [required: >=1.5.0, installed: 2.2.0]
        - dask [required: ==2022.12.0, installed: 2022.12.0]
          - click [required: >=7.0, installed: 8.1.3]
            - colorama [required: Any, installed: 0.4.6]
          - cloudpickle [required: >=1.1.1, installed: 2.2.0]
          - fsspec [required: >=0.6.0, installed: 2022.11.0]
          - packaging [required: >=20.0, installed: 21.3]
            - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
          - partd [required: >=0.3.10, installed: 1.3.0]
            - locket [required: Any, installed: 1.0.0]
            - toolz [required: Any, installed: 0.12.0]
          - pyyaml [required: >=5.3.1, installed: 6.0]
          - toolz [required: >=0.8.2, installed: 0.12.0]
        - jinja2 [required: Any, installed: 3.1.2]
          - MarkupSafe [required: >=2.0, installed: 2.1.1]
        - locket [required: >=1.0.0, installed: 1.0.0]
        - msgpack [required: >=0.6.0, installed: 1.0.4]
        - packaging [required: >=20.0, installed: 21.3]
          - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
        - psutil [required: >=5.0, installed: 5.9.4]
        - pyyaml [required: Any, installed: 6.0]
        - sortedcontainers [required: !=2.0.1,!=2.0.0, installed: 2.4.0]
        - tblib [required: >=1.6.0, installed: 1.7.0]
        - toolz [required: >=0.10.0, installed: 0.12.0]
        - tornado [required: >=6.0.3, installed: 6.2]
        - urllib3 [required: Any, installed: 1.26.13]
        - zict [required: >=0.1.3, installed: 2.2.0]
          - heapdict [required: Any, installed: 1.0.1]
      - GeoAlchemy2 [required: Any, installed: 0.12.5]
        - packaging [required: Any, installed: 21.3]
          - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
        - SQLAlchemy [required: >=1.4, installed: 1.4.44]
          - greenlet [required: !=0.4.17, installed: 2.0.1]
      - jsonschema [required: Any, installed: 4.17.3]
        - attrs [required: >=17.4.0, installed: 22.1.0]
        - pyrsistent [required: >=0.14.0,!=0.17.2,!=0.17.1,!=0.17.0, installed: 0.19.2]
      - lark [required: Any, installed: 1.1.5]
      - netcdf4 [required: Any, installed: 1.6.2]
        - cftime [required: Any, installed: 1.6.2]
          - numpy [required: >1.13.3, installed: 1.24.1]
        - numpy [required: >=1.9, installed: 1.24.1]
      - numpy [required: Any, installed: 1.24.1]
      - pandas [required: Any, installed: 1.5.2]
        - numpy [required: >=1.20.3, installed: 1.24.1]
        - python-dateutil [required: >=2.8.1, installed: 2.8.2]
          - six [required: >=1.5, installed: 1.16.0]
        - pytz [required: >=2020.1, installed: 2022.6]
      - psycopg2 [required: Any, installed: 2.9.5]
      - pyproj [required: >=2.5, installed: 3.4.0]
        - certifi [required: Any, installed: 2022.12.7]
      - python-dateutil [required: Any, installed: 2.8.2]
        - six [required: >=1.5, installed: 1.16.0]
      - pyyaml [required: Any, installed: 6.0]
      - rasterio [required: >=1.3.2, installed: 1.3.4]
        - affine [required: Any, installed: 2.3.1]
        - attrs [required: Any, installed: 22.1.0]
        - certifi [required: Any, installed: 2022.12.7]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
        - click-plugins [required: Any, installed: 1.1.1]
          - click [required: >=4.0, installed: 8.1.3]
            - colorama [required: Any, installed: 0.4.6]
        - cligj [required: >=0.5, installed: 0.7.2]
          - click [required: >=4.0, installed: 8.1.3]
            - colorama [required: Any, installed: 0.4.6]
        - numpy [required: >=1.18, installed: 1.24.1]
        - setuptools [required: Any, installed: 65.5.1]
        - snuggs [required: >=1.4.1, installed: 1.4.7]
          - numpy [required: Any, installed: 1.24.1]
          - pyparsing [required: >=2.1.6, installed: 3.0.9]
      - shapely [required: >=1.6.4, installed: 1.8.4]
      - sqlalchemy [required: Any, installed: 1.4.44]
        - greenlet [required: !=0.4.17, installed: 2.0.1]
      - toolz [required: Any, installed: 0.12.0]
      - xarray [required: >=0.9,!=2022.6.0, installed: 2022.12.0]
        - numpy [required: >=1.20, installed: 1.24.1]
        - packaging [required: >=21.3, installed: 21.3]
          - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
        - pandas [required: >=1.3, installed: 1.5.2]
          - numpy [required: >=1.20.3, installed: 1.24.1]
          - python-dateutil [required: >=2.8.1, installed: 2.8.2]
            - six [required: >=1.5, installed: 1.16.0]
          - pytz [required: >=2020.1, installed: 2022.6]
    - distributed [required: Any, installed: 2022.12.0]
      - click [required: >=7.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - cloudpickle [required: >=1.5.0, installed: 2.2.0]
      - dask [required: ==2022.12.0, installed: 2022.12.0]
        - click [required: >=7.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
        - cloudpickle [required: >=1.1.1, installed: 2.2.0]
        - fsspec [required: >=0.6.0, installed: 2022.11.0]
        - packaging [required: >=20.0, installed: 21.3]
          - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
        - partd [required: >=0.3.10, installed: 1.3.0]
          - locket [required: Any, installed: 1.0.0]
          - toolz [required: Any, installed: 0.12.0]
        - pyyaml [required: >=5.3.1, installed: 6.0]
        - toolz [required: >=0.8.2, installed: 0.12.0]
      - jinja2 [required: Any, installed: 3.1.2]
        - MarkupSafe [required: >=2.0, installed: 2.1.1]
      - locket [required: >=1.0.0, installed: 1.0.0]
      - msgpack [required: >=0.6.0, installed: 1.0.4]
      - packaging [required: >=20.0, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - psutil [required: >=5.0, installed: 5.9.4]
      - pyyaml [required: Any, installed: 6.0]
      - sortedcontainers [required: !=2.0.1,!=2.0.0, installed: 2.4.0]
      - tblib [required: >=1.6.0, installed: 1.7.0]
      - toolz [required: >=0.10.0, installed: 0.12.0]
      - tornado [required: >=6.0.3, installed: 6.2]
      - urllib3 [required: Any, installed: 1.26.13]
      - zict [required: >=0.1.3, installed: 2.2.0]
        - heapdict [required: Any, installed: 1.0.1]
    - numexpr [required: Any, installed: 2.8.4]
      - numpy [required: >=1.13.3, installed: 1.24.1]
    - numpy [required: Any, installed: 1.24.1]
    - rasterio [required: >=1.3.2, installed: 1.3.4]
      - affine [required: Any, installed: 2.3.1]
      - attrs [required: Any, installed: 22.1.0]
      - certifi [required: Any, installed: 2022.12.7]
      - click [required: >=4.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - click-plugins [required: Any, installed: 1.1.1]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
      - cligj [required: >=0.5, installed: 0.7.2]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
      - numpy [required: >=1.18, installed: 1.24.1]
      - setuptools [required: Any, installed: 65.5.1]
      - snuggs [required: >=1.4.1, installed: 1.4.7]
        - numpy [required: Any, installed: 1.24.1]
        - pyparsing [required: >=2.1.6, installed: 3.0.9]
    - scikit-image [required: Any, installed: 0.19.3]
      - imageio [required: >=2.4.1, installed: 2.22.4]
        - numpy [required: Any, installed: 1.24.1]
        - pillow [required: >=8.3.2, installed: 9.2.0]
      - networkx [required: >=2.2, installed: 2.8.8]
      - numpy [required: >=1.17.0, installed: 1.24.1]
      - packaging [required: >=20.0, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - pillow [required: >=6.1.0,!=8.3.0,!=7.1.1,!=7.1.0, installed: 9.2.0]
      - PyWavelets [required: >=1.1.1, installed: 1.4.1]
        - numpy [required: >=1.17.3, installed: 1.24.1]
      - scipy [required: >=1.4.1, installed: 1.9.3]
        - numpy [required: >=1.18.5,<1.26.0, installed: 1.24.1]
      - tifffile [required: >=2019.7.26, installed: 2022.10.10]
        - numpy [required: >=1.19.2, installed: 1.24.1]
    - toolz [required: Any, installed: 0.12.0]
    - xarray [required: Any, installed: 2022.12.0]
      - numpy [required: >=1.20, installed: 1.24.1]
      - packaging [required: >=21.3, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - pandas [required: >=1.3, installed: 1.5.2]
        - numpy [required: >=1.20.3, installed: 1.24.1]
        - python-dateutil [required: >=2.8.1, installed: 2.8.2]
          - six [required: >=1.5, installed: 1.16.0]
        - pytz [required: >=2020.1, installed: 2022.6]
  - odc-geo [required: >=0.3.2,<0.4.0, installed: 0.3.3]
    - affine [required: Any, installed: 2.3.1]
    - cachetools [required: Any, installed: 5.2.0]
    - numpy [required: Any, installed: 1.24.1]
    - pyproj [required: >=3.0.0, installed: 3.4.0]
      - certifi [required: Any, installed: 2022.12.7]
    - shapely [required: Any, installed: 1.8.4]
  - openeo-pg-parser-networkx [required: >=2023.1.2, installed: 2023.1.2]
    - geojson-pydantic [required: >=0.5.0,<0.6.0, installed: 0.5.0]
      - pydantic [required: Any, installed: 1.10.2]
        - typing-extensions [required: >=4.1.0, installed: 4.4.0]
    - networkx [required: >=2.8.6,<3.0.0, installed: 2.8.8]
    - numpy [required: >=1.24.1,<2.0.0, installed: 1.24.1]
    - pendulum [required: >=2.1.2,<3.0.0, installed: 2.1.2]
      - python-dateutil [required: >=2.6,<3.0, installed: 2.8.2]
        - six [required: >=1.5, installed: 1.16.0]
      - pytzdata [required: >=2020.1, installed: 2020.1]
    - pydantic [required: >=1.9.1,<2.0.0, installed: 1.10.2]
      - typing-extensions [required: >=4.1.0, installed: 4.4.0]
    - pyproj [required: >=3.4.0,<4.0.0, installed: 3.4.0]
      - certifi [required: Any, installed: 2022.12.7]
    - shapely [required: >=1.8, installed: 1.8.4]
  - rasterio [required: >=1.3.4,<2.0.0, installed: 1.3.4]
    - affine [required: Any, installed: 2.3.1]
    - attrs [required: Any, installed: 22.1.0]
    - certifi [required: Any, installed: 2022.12.7]
    - click [required: >=4.0, installed: 8.1.3]
      - colorama [required: Any, installed: 0.4.6]
    - click-plugins [required: Any, installed: 1.1.1]
      - click [required: >=4.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
    - cligj [required: >=0.5, installed: 0.7.2]
      - click [required: >=4.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
    - numpy [required: >=1.18, installed: 1.24.1]
    - setuptools [required: Any, installed: 65.5.1]
    - snuggs [required: >=1.4.1, installed: 1.4.7]
      - numpy [required: Any, installed: 1.24.1]
      - pyparsing [required: >=2.1.6, installed: 3.0.9]
  - rioxarray [required: >=0.12.0,<1, installed: 0.13.1]
    - packaging [required: Any, installed: 21.3]
      - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
    - pyproj [required: >=2.2, installed: 3.4.0]
      - certifi [required: Any, installed: 2022.12.7]
    - rasterio [required: >=1.1.1, installed: 1.3.4]
      - affine [required: Any, installed: 2.3.1]
      - attrs [required: Any, installed: 22.1.0]
      - certifi [required: Any, installed: 2022.12.7]
      - click [required: >=4.0, installed: 8.1.3]
        - colorama [required: Any, installed: 0.4.6]
      - click-plugins [required: Any, installed: 1.1.1]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
      - cligj [required: >=0.5, installed: 0.7.2]
        - click [required: >=4.0, installed: 8.1.3]
          - colorama [required: Any, installed: 0.4.6]
      - numpy [required: >=1.18, installed: 1.24.1]
      - setuptools [required: Any, installed: 65.5.1]
      - snuggs [required: >=1.4.1, installed: 1.4.7]
        - numpy [required: Any, installed: 1.24.1]
        - pyparsing [required: >=2.1.6, installed: 3.0.9]
    - xarray [required: >=0.17, installed: 2022.12.0]
      - numpy [required: >=1.20, installed: 1.24.1]
      - packaging [required: >=21.3, installed: 21.3]
        - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
      - pandas [required: >=1.3, installed: 1.5.2]
        - numpy [required: >=1.20.3, installed: 1.24.1]
        - python-dateutil [required: >=2.8.1, installed: 2.8.2]
          - six [required: >=1.5, installed: 1.16.0]
        - pytz [required: >=2020.1, installed: 2022.6]
  - xarray [required: >=2022.11.0, installed: 2022.12.0]
    - numpy [required: >=1.20, installed: 1.24.1]
    - packaging [required: >=21.3, installed: 21.3]
      - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9]
    - pandas [required: >=1.3, installed: 1.5.2]
      - numpy [required: >=1.20.3, installed: 1.24.1]
      - python-dateutil [required: >=2.8.1, installed: 2.8.2]
        - six [required: >=1.5, installed: 1.16.0]
      - pytz [required: >=2020.1, installed: 2022.6]
  - xgboost [required: >=1.5.1,<2.0.0, installed: 1.7.1]
    - numpy [required: Any, installed: 1.24.1]
    - scipy [required: Any, installed: 1.9.3]
      - numpy [required: >=1.18.5,<1.26.0, installed: 1.24.1]

Hey - sorry for the late reply on this, I was on sick leave last week!
IMHO odc-algo is the worst offender here. It's not a stable/well-defined library in the first place and it pulls in 1) datacube + all its sql stuff we don't use here and 2) scikit-image, which we don't use at all.
We literally only need it for its xr_reproject method, so finding an alternative to this would probably be the biggest "bang for your buck" in terms of effort vs. reduced dependency set.
There's already an open issue for porting that functionality into odc-geo, could be a good contribution over there: https://github.com/opendatacube/odc-geo/issues/26

As discussed today, we'll put resample_spatial into the experimental folder and expose a new build variant [experimental] that we'll use internally. A vanilla installation of this repo should then not include these unnecessary dependencies from odc-algo!

Thanks Lukas. Little note: it's resample_cube_spatial, resample_spatial is currently not yet implemented here.

@clausmichele just released 2023.3.0, this has the discussed build variants and doesn't pull in matplotlib from the parser anymore! 👍


Allow choice of credential store at runtime.

(Requested by @soywod)
The current usage pattern for this crate is that the developer chooses the credential store to use (for each platform) at compile time, and the users of the developer's application have no choice in the matter. Because it's not possible, currently, to build this crate with all possible credential stores on all platforms, there is no way for a developer to let his application users choose their desired credential store at runtime.
Perhaps, in the next major version of keyring, this could change?

I'm not sure this requires any enhancement. The only two credential stores you can't use at the same time are the synchronous and asynchronous versions of the secret service, and those are the same credential store, so there would be no functional difference in choosing one or the other.  In all other cases, you can build in all the credential stores and then choose between them at runtime by using set_default_credential_builder. @soywod, can you say more about what flexibility you are trying to get?

so there would be no functional difference in choosing one or the other.

This may be partially wrong. So far the dbus crate exposes a blocking API (std) and a nonblock API (tokio). The zbus crate exposes by default an async API (async-io), another async API behind a cargo feature (tokio) and a blocking API. But you cannot use the blocking API only, so it comes with futures-* dependencies. Both do not manage the same way: one needs a third party lib (libdbus), the other spawns an async execute (although looks like you can disable it).
My point is: some people may need the blocking D-Bus API, some the Z-Bus tokio API, some both. If you expose everything, people can compose the way they want. This idea brings us to the last point (and joins your questions): as a lib you don't want to rewrite from scratch every implementations you have for std, tokio, async-std etc. Code needs to be put in common.

To summarize: ideally, a reusable and composable lib should:

Have cumulative cargo features and not exclusive ones
Expose components both at compile time (cargo features) and runtime
Not care about I/O and runtime, no need to deal with duplicate async/non async traits
Propose default I/O connectors, and make sure lib consumers can develop their own connector if needed

The Sans I/O pattern looks the most promising to me, and seem to fit all the cases. I partially contibuted to a Sans I/O project called imap-next, and it works great. The new keyring prototype I experiment with looks promising also. The only drawback I found is that it makes the code a bit more complicated to understand, it's kind of an unusual way to code. I really invite you to read more about the pattern and real world examples I shared to make your own opinion.

so there would be no functional difference in choosing one or the other.

This may be partially wrong. So far the dbus crate exposes a blocking API (std) and a nonblock API (tokio).

This is not a functional difference. Whether an interface is sync or async is a "non-functional" distinction: it does not affect the specified input/output behavior of the interface, only the form of the computation that produces those outputs from those inputs. This stack overflow answer gives a nice, concise definition of functional vs. non-functional requirements.
Putting this another way: there is no way for a user of an application which uses keyring to know whether, under the covers, that application's developer is using a sync or async credential store. Only the developer knows this.
It sounds like what you really want is a crate that exposes both synchronous and asynchronous interfaces. I don't see the point in this, for two reasons:

Abstract credential store behavior is, for all intents and purposes, synchronous. Without a deep understanding of how a credential store works, it's incredibly dangerous to make multiple calls into that store at the same time.  Calls to credential stores should always be serialized by the programmer, not the store.
While it's abstractly clear how to wrap an asynchronous interface around a synchronous one (allocate a separate thread for all uses of the synchronous interface, and have the async interface queue all accesses on that thread and wait for their completion), the details of how to do this effectively will vary tremendously based on the system architecture of the consumer and so it should be done by the consumer not by the crate being consumed.

You have mentioned how much more complex the architecture is when you try to attract whether you are using an async or sync component underneath the API surface. In my experience, it also tends to be inefficient, because the generalized architecture can't be optimized based on the client architecture.
The only reason I have even left zbus support in keyring at all is for backwards compatibility. I don't know of any systems that use dbus that don't have a dbus library, so there's really no reason not to use dbus-secret-service in any new application you are building. Can you give me a real-world use case you have that requires zbus?
Very interested in your thoughts here.


Chrome extension

How to add its chrome extension?

Sorry, BetterDiscord is not available as a chrome extension. It can only be installed to the desktop app.

Will there be any in future?

No.


Alexa Event -> On Device Activity  not working since today

Since today  "on device activity"  is no longer working. When I ask Alexa something, no event / message is generated anymore.
If I use the "Volume change" function of the "Alexa event"-node, an event/message is generated. Is this a known problem or is there any advice on how I can solve the problem?
Update: with updated alexa-remote2 version 7.0.4  it's working again

I can confirm i see the same.
was ok till today working like a charm.
no updates done and stopped working.
tried fresh/refresh auth no change
there was ha and node red update so did them as was broken anyway and no change.
node red node-red-contrib-amazon-echo had update so i did this and no change
just letting you know what i done, will wait for devs to look as i know you always do your best. thanks in advance

Just came here to report it has stopped working for me as well

same to me...nothing changed > reinstall, refresh without effect.

+1 from Italy since 2 days ago

@bbindreiter It seems you need to update alexa-remote2 dependency to version 7.0.4
I manually installed it and it fixed the problem for me.

It seems you need to update alexa-remote2 dependency to version 7.0.4 I manually installed it and it fixed the problem for me.
I updated it via: "npm i alexa-remote2" but without any effect - are there any additioan actions that you recommend to do (you did)?

@bbindreiter It seems you need to update alexa-remote2 dependency to version 7.0.4 I manually installed it and it fixed the problem for me. Amazon making changes again I guess, keep up the good work ;-)

Thanks, will try it today

As I've told @smcgann99 in the NodeRED forum, this also didn't make any difference for me

For some reason, running the install command didn't update the alexa-remote2 package
When I went to check - mine was still on a version 6
I decided to try removing it using npm remove alexa-remote2 and it said it uninstalled 4 packages
I then re-ran npm install alexa-remote2 and it installed 4 packages and my version is now 7.0.4
And now it works again :slight_smile:

Unfortunately  I removed  (npm remove alexa-remote2) and installed  (npm install alexa-remote2) with no effect by now

btw how can I check the alexa_remote2 version, as it does'nt apperar in "manage palette" menu?

@brunialti

version check: "npm list"
make sure that the npm uninstall/intall is run in the right folder: ".node-red" > example: /home/pi/.node-red

working again now!

"how can I check the alexa_remote2 version"
go into your .node-red/node_modules/alexa-remote2 folder
then open up package.json in a text editor and it says its version near the top
{
  "name": "alexa-remote2",
  "version": "7.0.4",
  "description": "Remote Control for amazon echo devices",
....

Can confirm, it does work for me with 5.0.49 and alexa-remote2 7.0.3. Will publish a new version anyway. Anyway, stop relying on that function, it is not sustainable.
{
  "data": {
    "timestamp":<PHONE_NUMBER>160,
    "device": {
      "deviceName": "Echo Office",
      "deviceEntityId": null
    },
    "voiceHistoryRecordItems": [
      {
        "timestamp":<PHONE_NUMBER>147,
        "transcriptText": "alexa what's the time",

      },
      {
        "timestamp":<PHONE_NUMBER>162,
        "transcriptText": "The time is 9:40 AM.",

      ]
    }
  ]
},
"conversionDetails": {
  "CUSTOMER_TRANSCRIPT": [
    {
      "timestamp":<PHONE_NUMBER>147,
      "transcriptText": "alexa what's the time",

    }
  ],
  "ALEXA_RESPONSE": [
    {
      "timestamp":<PHONE_NUMBER>162,
      "transcriptText": "The time is 9:40 AM.",

    }
  ]
},
"name": "Echo Office",
"description": {
  "summary": "what's the time"
},
"alexaResponse": "The time is 9:40 AM.",
}

Please try 5.0.50, it uses the latest alexa-remote2 (7.0.4). Thanks!

thanks @bbindreiter ive just checked and the update is not available yet on the pallete but ill check again later.
Thanks again for you update,
FYI, i do not solely rely on this function, but when it works its grate so its very helpful. when it doesn't we have app button, wall button and longer voice commands to work with.
we are just lazy and like to say short commands like Alexa light or Alexa tv and it knows where we are to turn on the correct device. This solution that sometimes has issue is better than any other solution that I know.

The new release solves my problem.

Unfortunately I still can't get my flow working even with 7.0.4.

I have alexa-remote2 7.0.4 and alexa-cookie 5.0.2 installed (confirmed by checking package.json files).

An Alexa Event node, configured to report Device Activity, indicates "listening" (see screenshot below).

A Debug node is connected to the Alexa Event node (plus other nodes that form the flow).

I have spoken requests to several Echo devices but no device activity events are ever reported by the Debug node (or received by the other nodes).

I have restarted Node-Red and re-initialized the cookie several times the problem persists. I would appreciate suggestions for what I should check/try next.

I hoped this update would solve the Device activity node but it's no dice on my end. (UK) would this be region specific since some ppl confirm this working for them?

I hoped this update would solve the Device activity node but it's no dice on my end. (UK) would this be region specific since some ppl confirm this working for them?

I'm in the uk and worked fine for me since update as above. Just commenting to advise I'm uk too

I wonder how our configurations are different. I just reinstalled the node
and rebooted the pi then tried it again. Unfortunately without luck on my
end.
I'm VERY keen to get this functionality back.
On Tue, 23 Apr 2024, 19:11 sicampbell82, @.***> wrote:

I hoped this update would solve the Device activity node but it's no dice
on my end. (UK) would this be region specific since some ppl confirm this
working for them?
I'm in the uk and worked fine for me since update as above. Just
commenting to advise I'm uk too
—
Reply to this email directly, view it on GitHub
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2073074374,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL265H6Y2662GEJPGHHDY62P4XAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZTGA3TIMZXGQ
.
You are receiving this because you commented.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2073074374
@github.com>

Not sure but as listed about in comment
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2059875301
these are my changes when debugging that did not work and then i updated node-red-contrib-alexa-remote2-applestrudel to 5.0.50 and restarted then it all just worked again

I had some time to spin up new NR instance - (3.1.9 and 5.0.50 version od the node) basic innit node and on device activity  - nothing when I speak to all my echos. I can direct smart devices from NR

Not that it will probably fix your issue but don't use the Initialise node anymore
Set the Auto Init parameter to On instead
And remember to set your deployment option to Modified Nodes in case you haven't done that

What colour is your on device node status. O don't really like it being
gray. Feels like it should be another colour.
On Sat, 27 Apr 2024, 07:53 Simon Walters, @.***> wrote:

Not that it will probably fix your issue but don't use the Initialise node
anymore
Set the Auto Init parameter to On instead
And remember to set your deployment option to Modified Nodes in case you
haven't done that
—
Reply to this email directly, view it on GitHub
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2080391274,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL236XAAIZ76MDGPDUADY7NDP3AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGM4TCMRXGQ
.
You are receiving this because you commented.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2080391274
@github.com>

Its grey when listening - turns to green when something detected

turns green when something detected

How I wish it would do that again but, in my case, it hasn't in a long time.
Given that no one has indicated there's anything wrong with the configuration I posted above, it's all the more perplexing.

Many people have many issues with this node -in the past - it's not been working for me but 90% of others have been happy.
Its not a node to rely on as it's all reverse-engineered and Amazon can (and do) change things around whenever they want to
One day we'll find out that it depends wether you bought one of your Echos on a Tuesday or not :)

Duh.
Alexa account configuration has a on/off toggle for device activity. I
completely missed this. I'm not sure in what circumstances I'd like this to
be off as I can simply not use the node... But toggling it fixed the issue
for me and I have my device activities back again
😍😍😍
On Sat, 27 Apr 2024, 13:54 Simon Walters, @.***> wrote:

Many people have many issues with this node -in the past - it's not been
working for me but 90% of others have been happy.
Its not a node to rely on as it's all reverse-engineered and Amazon can
(and do) change things around whenever they want to
One day we'll find out that it depends whether you bought one of your
Echos on a Tuesday or not :)
—
Reply to this email directly, view it on GitHub
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2080590759,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL26IUP23TY2ZMOPDMOTY7ONY5AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGU4TANZVHE
.
You are receiving this because you commented.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2080590759
@github.com>

It's off per default to ease traffic on Amazon servers. They have asked us, actually Apollon77, to add this.

toggling it fixed the issue for me

I tried switching that setting from On to Off (deploy) and back to On (deploy) but the Alexa Event node still fails to report events.

If I add an Alexa Routine node, its Devices list displays all my Echo devices, so alexa-remote2 is communicating with Amazon's servers (it retrieved all device names including one I added recently). However, the Alexa Event node doesn't report any events that occur on those devices.
I noticed that the Alexa Event node's description says:

Listens to Push events. Events must be enabled for this account.

Regarding "Events must be enabled for this account", is it referring to the node's account configuration, specifically the Event field must be set to On? Or is that a setting in my Amazon account? Because I don't recall ever having to enable anything in my Amazon account.
Grasping at straws ...

Alexa account configuration has a on/off toggle for device activity.

Is this a different option somewhere that's not the Events and Auto Query Activities toggle in the account node? You don't mention them by name so wondering if I may have missed it as well. Thanx Michael

This is in the configuration node for the Alex's remote. It's easy to miss
if you used it before and you assume that you know the options by heart.
Open it up and you will see the toggle just below other settings
On Sat, 25 May 2024, 23:26 Michael Murphy, @.***> wrote:

Alexa account configuration has a on/off toggle for device activity.
Is this a different option somewhere that's not the Events and Auto Query
Activities toggle in the account node? You don't mention them by name so
wondering if I may have missed it as well. Thanx Michael
—
Reply to this email directly, view it on GitHub
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131567959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL2ZYWWPQ56OYUYNFXYLZEEFZRAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3DOOJVHE
.
You are receiving this because you commented.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2131567959
@github.com>

Sorry, I’m Just not getting it. If I go to the right side-bar and open the configuration node for the Alexa remote account I get the same options…
@.***
Michael Murphy
Ocean Blue Properties
Coosa Island Storage
Bullets Mini Storage
107 Coosa Island Rd
Cropwell, AL 35054
205-600-4463
From: NotEnoughTech @.>
Sent: Saturday, May 25, 2024 5:32 PM
To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.>
Cc: Michael Murphy @.>; Comment @.>
Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
This is in the configuration node for the Alex's remote. It's easy to miss
if you used it before and you assume that you know the options by heart.
Open it up and you will see the toggle just below other settings
On Sat, 25 May 2024, 23:26 Michael Murphy<EMAIL_ADDRESS>wrote:

Alexa account configuration has a on/off toggle for device activity.
Is this a different option somewhere that's not the Events and Auto Query
Activities toggle in the account node? You don't mention them by name so
wondering if I may have missed it as well. Thanx Michael
—
Reply to this email directly, view it on GitHub
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131567959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL2ZYWWPQ56OYUYNFXYLZEEFZRAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3DOOJVHE
.
You are receiving this because you commented.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2131567959
@github.com>

—
Reply to this email directly, view it on GitHubhttps://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131577567, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZDP7UL6MPZRQK63TROZTDZEEGPJAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3TONJWG4.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

I'm getting a screenshot got you one sec
On Sun, 26 May 2024, 05:25 Michael Murphy, @.***> wrote:

Sorry, I’m Just not getting it. If I go to the right side-bar and open the
configuration node for the Alexa remote account I get the same options…
@.***
Michael Murphy
Ocean Blue Properties
Coosa Island Storage
Bullets Mini Storage
107 Coosa Island Rd
Cropwell, AL 35054
205-600-4463
From: NotEnoughTech @.>
Sent: Saturday, May 25, 2024 5:32 PM
To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.>
Cc: Michael Murphy @.>; Comment @.>
Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel]
Alexa Event -> On Device Activity not working since today (Issue #188)
This is in the configuration node for the Alex's remote. It's easy to miss
if you used it before and you assume that you know the options by heart.
Open it up and you will see the toggle just below other settings
On Sat, 25 May 2024, 23:26 Michael Murphy<EMAIL_ADDRESS>wrote:

Alexa account configuration has a on/off toggle for device activity.
Is this a different option somewhere that's not the Events and Auto
Query
Activities toggle in the account node? You don't mention them by name so
wondering if I may have missed it as well. Thanx Michael
—
Reply to this email directly, view it on GitHub
<
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131567959>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AKDRL2ZYWWPQ56OYUYNFXYLZEEFZRAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3DOOJVHE>

.
You are receiving this because you commented.Message ID:

<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2131567959

@github.com>

—
Reply to this email directly, view it on GitHub<
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131577567>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AAZDP7UL6MPZRQK63TROZTDZEEGPJAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3TONJWG4>.
You are receiving this because you commented.Message ID:
<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHub
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132059564,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL253YXOEBVR7ETFYADLZEFP3JAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGA2TSNJWGQ
.
You are receiving this because you commented.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2132059564
@github.com>

Step 1

this should be on - then reboot

I must have something else going on because I have had auto query on for a while (toggled on/off) rebooted etc.. Still no events. All the other nodes are working as expected. I have an Astro project that I’m working on. Trying 2 use node-red to control it. Its been interesting so far…Have you worked with it yet? I have another alexa issue with that has me stumped. Zero support for it so far…
2024-05-26_03-21-04.pnghttps://1drv.ms/i/s!ApYuqualHfEeo58l20dSYkELZy_sJw?e=QCf2qV
Michael
From: NotEnoughTech @.>
Sent: Sunday, May 26, 2024 12:17 AM
To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.>
Cc: Michael Murphy @.>; Comment @.>
Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
image.png (view on web)https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/assets/42407403/41c82eb7-f46a-4b08-9bc0-6f08cdba6b7b
Step 1
image.png (view on web)https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/assets/42407403/1919c99c-7945-4810-ad82-a799c31f0d4b
this should be on - then reboot
—
Reply to this email directly, view it on GitHubhttps://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132070087, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZDP7QQS3JREGZ3EOVPZFLZEFV6BAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGA3TAMBYG4.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

I haven't heard of Astro.
About the issue, are you able to try on a clean instance to see if there is something else affecting your installation?

I went as far as removing AlexaRemote2 and then re-installing still nothing. Nothing in the logs give me a clue of why I’m not receiving events. It’s got me stumped.
Astro
https://a.co/d/ahjbaRR
Michael
From: NotEnoughTech @.>
Sent: Sunday, May 26, 2024 3:50 AM
To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.>
Cc: Michael Murphy @.>; Comment @.>
Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
I haven't heard of Astro.
About the issue, are you able to try on a clean instance to see if there is something else affecting your installation?
—
Reply to this email directly, view it on GitHubhttps://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132140406, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZDP7RR23PK2VGA6ZCILNDZEGO45AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGE2DANBQGY.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

Oh this is Astra, I remember this.
I think the common consensus was, that having Amazon Echo with a camera on
was bad enough, we don't need one that roams haha
my test server has just this:
[image: image.png]
Works fine.
did you use npm to remove AR2? A new instance will take moments to confirm.
I assume you can log in and operate other Alexa functions?
    Mat Zolnierczyk

Maker, Robotics Engineer
Owner | NotEnoughTech
@.***
notenoughtech.com
Teesside, North Yorkshire, UK
[image: facebook] https://www.facebook.com/NotEnoughTECH/
[image: twitter] https://twitter.com/NotEnoughTECH
[image: linkedin] https://www.linkedin.com/in/mat-zolnierczyk/
[image: instagram] https://www.instagram.com/notenoughtech/
On Sun, May 26, 2024 at 6:16 PM Michael Murphy @.***>
wrote:

I went as far as removing AlexaRemote2 and then re-installing still
nothing. Nothing in the logs give me a clue of why I’m not receiving
events. It’s got me stumped.
Astro
https://a.co/d/ahjbaRR
Michael
From: NotEnoughTech @.>
Sent: Sunday, May 26, 2024 3:50 AM
To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.>
Cc: Michael Murphy @.>; Comment @.>
Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel]
Alexa Event -> On Device Activity not working since today (Issue #188)
I haven't heard of Astro.
About the issue, are you able to try on a clean instance to see if there
is something else affecting your installation?
—
Reply to this email directly, view it on GitHub<
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132140406>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AAZDP7RR23PK2VGA6ZCILNDZEGO45AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGE2DANBQGY>.
You are receiving this because you commented.Message ID:
<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHub
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132290499,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL27QXAOUVRTHPOHPP6TZEIKILAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGI4TANBZHE
.
You are receiving this because you commented.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2132290499
@github.com>

I have had auto query on for a while (toggled on/off) rebooted etc.. Still no events. All the other nodes are working as expected.

You are not alone. I also have Auto Query set to On and it still fails to receive events. Other nodes work properly, just not Device Activity. It used to work but hasn't for a long time. Its fragility has convinced me to abandon alexa-remote2 and explore other solutions.

Yeah I have about given up also. Have spent many hours trying to get this to work..  Looking @ Voice Monkey - Supercharge Your Alexa Routineshttps://voicemonkey.io/
Michael
From: tdejneka @.>
Sent: Sunday, May 26, 2024 1:34 PM
To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.>
Cc: Michael Murphy @.>; Comment @.>
Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
I have had auto query on for a while (toggled on/off) rebooted etc.. Still no events. All the other nodes are working as expected.
You are not alone. I also have Auto Query set to On and it still fails to receive events. Other nodes work properly, just not Device Activity. It used to work but hasn't for a long time. Its fragility has convinced me to abandon alexa-remote2 and explore other solutions.
—
Reply to this email directly, view it on GitHubhttps://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132327281, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZDP7TQ6HP2XJE4J5GXMNDZEITIFAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGMZDOMRYGE.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

So it seems it's time to accept this is dead and move on?
What other options there are for people with Alexas that are pretty much useless now?

I'm not sure what could stop others but once I enabled that toggle things
were working for me.
Would be good to pull resources together and figure out what else is making
this behave badly
Mat Zolnierczyk
Maker, Robotics Engineer
Owner | NotEnoughTech
@.***
notenoughtech.com
Teesside, North Yorkshire, UK
[image: facebook] https://www.facebook.com/NotEnoughTECH/
[image: twitter] https://twitter.com/NotEnoughTECH
[image: linkedin] https://www.linkedin.com/in/mat-zolnierczyk/
[image: instagram] https://www.instagram.com/notenoughtech/
On Tue, Jun 4, 2024 at 4:07 PM jonferreira @.***> wrote:

So it seems it's time to accept this is dead and move on?
What other options there are for people with Alexas that are pretty much
useless now?
—
Reply to this email directly, view it on GitHub
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2147776779,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL26L3UDB3VYKK7W7SZLZFXJ47AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXG43TMNZXHE
.
You are receiving this because you commented.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2147776779
@github.com>

pull resources together and figure out what else is making this behave badly

I'm running the latest version of alexa-remote2 (5.0.50) on Node-Red (17.0.12 as a Home Assistant Add-on). The Device Activity node indicates "listening" but no event is ever received. All other nodes work (such as turning on a light or TTS) only the device Activity node remains forever silent. It worked for a few years then, about half a year ago, it stopped and none of the subsequent versions of alexa-remote2 have resuscitated it.
It's configured like this:

I noticed this recently as well. One of my installs is still working, but the other install is no longer receiving events as of today. All other aspects (that I use) are still working fine, such as changing volume and looking at lists, but the on device event is broken for me.

After a long time Device Events are finally working again for me. I have updated from 5.0.49 to 5.0.50, set "Auto Query Activities" from unset to "On" and restarted Node Red. Thanks to @notenoughtech, I wasn't aware of that setting.

I'm pleased to hear it's working for you.
Happy days
On Mon, 1 Jul 2024, 10:48 Chris380, @.***> wrote:

After a long time Device Events are finally working again for me. I have
updated from 5.0.49 to 5.0.50, set "Auto Query Activities" from unset to
"On" and restarted Node Red. Thanks to @notenoughtech
https://github.com/notenoughtech, I wasn't aware of that setting.
—
Reply to this email directly, view it on GitHub
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2199707745,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL23OFT5VKFMDOAJKQT3ZKEQWPAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJZG4YDONZUGU
.
You are receiving this because you were mentioned.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2199707745
@github.com>

updated from 5.0.49 to 5.0.50, set "Auto Query Activities" from unset to "On" and restarted Node Red.

FWIW, in the screenshot I posted last month, I'm using the same version with the same settings and it fails to detect events.
Nobody has come forward to explain why those settings work for some users but not others. I assume that's because no one has sufficient understanding of how this actually works under the hood. Or whoever does understand it doesn't have the time to explain it. Either way, it leaves me with a non-functional Alexa Event Node and no clear way to fix it.
If you see anything different in that screenshot compared to your settings, please let me know. Thank you.

I am in the UK so slightly different settings and mine partially responds. IE 1 in 5 times I get a response...

For some reason I do get quite frequent connect/disconnects. Did you set up something to see if the same happens to you?

I do get quite frequent connect/disconnects

In my case, it connects and remains connected. I can use it to send commands, play TTS, etc.
What doesn't work is the Alexa Event node's ability to detect/report events. Speaking to Alexa used to be reported as an event but that's no longer working for me.

I'm running the latest version (18.0.4) of Home Assistant's Node-Red Addon.  It includes:
Node-RED version: v4.0.2
Node.js  version: v18.20.3

The Alexa Event node fails to detect/report events.

Hi,
i`m having problems too with the alexa event node.
If i init the data, it´s working about one to five events.  i´m getting a debug output and all is working great. till the next command nothing happens. No event is firing until ich restart NordeRed an init all new. then the same as above happens.
I´m on proxmox with a VM.
HAOS on newest Version (OS 12.4 and Core 2024.7.4).
NodeRed v4.0.2
node-red-contrib-alexa-remote2-applestrudel 5.0.50
if more informations needed just say.

I have noticed this has stopped working as well even with 5.0.50. Anyone else noticed the same?

So far the usual fixes of initializing, fresh authentication, and redeploying flows have had no effect. When I tried doing fresh authentication, it seems Amazon now has a captcha, so maybe they change something again and it broke this?

It just started working again randomly without me changing anything, so likely some Amazon shenanigans.

Hi, i`m having problems too with the alexa event node. If i init the data, it´s working about one to five events. i´m getting a debug output and all is working great. till the next command nothing happens. No event is firing until ich restart NordeRed an init all new. then the same as above happens. I´m on proxmox with a VM. HAOS on newest Version (OS 12.4 and Core 2024.7.4). NodeRed v4.0.2 node-red-contrib-alexa-remote2-applestrudel 5.0.50
if more informations needed just say.

Hi Simon,
could you tell me how you manage to install node-red-contrib-alexa-remote2-applestrudel 5.0.50?
I'm still 0n version 5.0.25 and no way to install th updated one.
By the way, did the event node issu get solved or still not working?
Thanks


Improving 'WARN' log with unavailable receiver URL endpoints.

When publishing data to endpoints via the "DataEndpointGroup" class following warn log can be observed and the unavailable receiver endpoints are will not be printed. As an improvement shall we add the relevant unavailable endpoints to the logs.

WARN {org.wso2.carbon.databridge.agent.endpoint.DataEndpointGroup} - No receiver is reachable at reconnection, will try to reconnect every 30 sec {org.wso2.carbon.databridge.agent.endpoint.DataEndpointGroup}

Closing since fixed in the master branch.


feat(icon): Add about.me icon

Description
This is a icon about https://about.me

Icon idea is from https://about.me/favicon.ico
It only shows "me" as tab icon in firefox.

Compatibility
It seems fine with compatibility.

Caveats
important: after merging, update document, please.
I should also add this icon to update the document, but i did not add it.
Because I found that document use the following css file,  if I add icon to document, it would break document.
<EMAIL_ADDRESS>

sorry for again and again force push....  only to change commit message to fit commitlint.
I have changed commit message for several times, but it still cannot pass commitlint test....
But it seems work fine in my local environment.
This is my first time to use commitlint, I cannot figure out how to solve it.

Don’t worry @candywater, this is actually an issue with our CI, not your PR. We’re investigating the issue in #415.

As much as I would like this icon, I don't have authorization to merge any new icons.
References:
#410 (comment)
#310 (comment)
So we will need to wait for the creator in this one.
I will make a new PR to all README.md regarding this.
I do apologize for the delay.

Thanks for your mention!
I have read #310 , too.
I understood the situation, maybe NES-icons.css is a good idea.
and here are the images


Feature: User generated interest

Type of feature
🍕 Feature
Current behavior
This would need planning, but a user should be able to search or suggest interests. The challenge will be associating it to one of the existing topics 900k topics on GitHub.

Suggested solution

Let's get the top 100 topics on GitHub per our data.
Allow suggestions either via the GitHub Discussions or Zendesk.
Add new topics based on demand.

Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

Blocked due to API updates need.

Closing as not planned, custom topics can still be added through the URL manually, and we'll add additional ones as needed


Static linking + code cleaning + Visual Studio solution

I've added flags for static linking we discussed... You said that library works on Linux when you compiled it yourself, maybe this flags helped too :)
Also I've changed linker flags for Windows with the same purpose, namely I've replaced /MD with /MT and /MDd with /MTd. As I've said, this helped to fix library on my friend's machine.
Please note, that you should change this flags for GodotNativeTools/godot-cpp too when compiling.
Another small change: I've removed fetching of custom lobby member data "ready" from the function getLobbyMembersData(). This code was copy-pasted by me from the Valve example application SpaceWar and it is really not needed, Anyway, getLobbyMembersData() returns you steamIDLobbyMember, therefore you can later call GetLobbyMemberData().
The last feature here is the ready Visual Studio solution directory! Now all you need to do to compile GodotSteam on Windows is:

Create some folder, for example, GDNative
Checkout https://github.com/GodotNativeTools/godot-cpp to GDNative folder
Build godot-cpp (requires SCons, can be tricky on Windows)
Please note, that you should manually change /MD to /MT and /MDd to /MTd in godot-cpp's SConstruct file to enable static linking of the Visual C runtime or you can not be able to compile GodotSteam!
Checkout GodotSteam
Copy public and redistributable_bin folders from Steam SDK to GodotSteam\include\sdk
Open solution file GodotSteam\VisualC\GodotSteam.sln in Visual Studio (I used Visual Studio Community 2015, I believe that later versions like 2017 and 2019 can convert this solution file to their format)
Select your desired configuration and build! Both debug and release versions & 32 and 64-bit architectures are supported, just make sure that you've compiled the corresponding version of godot-cpp.

Looks fantastic!  Yeah, I am gonna redo the how-to and bring the branch up-to-date with the module now that I got it working again.  Thanks for all your work!


♻ Rules Search should indicate "archived" rules

cc @adamcogan
Hi team,
Pain
When searching for a rule, the results will show archived rules together with live rules.
E.g. https://ssw.com.au/rules/search/?keyword=screenshot

Figure: The hovered rule in red is archived
What could be improved?
"Archived" rules are OK to appear in results, as long as we indicate that to users...
Option A (recommended): Hide archived rules by default and include a checkbox "Include archived" if the user is looking for them

Add a label (stamp) next to the result.
... same as we have on the category view (e.g. https://ssw.com.au/rules/rules-to-better-communication)

Option B: Add a label (stamp) next to the result only
Option C: Have a second results area just for archived rules
Screenshots

Figure: Checkbox used on categories to show archived rules

Figure: Label used to indicate archived rules in a category view
Thanks!

✅ @jeoffreyfischer completed this via - https://github.com/SSWConsulting/SSW.Rules/pull/1198


JohnMaxwellAcademy.com

Checklist

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dl version 2020.03.24
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Single video: https://www.johnmaxwellacademy.com/products/15-laws-of-growth/categories/741206/posts/2418867
Playlist: https://www.johnmaxwellacademy.com/products/15-laws-of-growth

Description

You need an account, and it's free to get one, at least for the next 7 days. all they need is for you to create a username and password. I created an account with a fake email address and it works with a fake email address. (You don't need to click the link in the email to watch the videos on the browser)

It appears you require an account to view the content. It's probable youtubedl was blocked in the process of attempting to download the videos for that reason.

It appears you require an account to view the content. It's probable youtubedl was blocked in the process of attempting to download the videos for that reason.


no viewbox makes this impossible to scale to fit parent

before:

after

LGTM, would it make sense to have both width/height and viewbox?

@Josh-Cena  I'm not a master of svg, but when i set viewbox and leave width/height, it looks (just as) broken as the before picture

Too awful that we use GitHub pages for the website so there's no way for me to preview the effect before merging. I'm going to merge this, and if it doesn't work out (e.g. doesn't allow customizing sizes), I'll let you know so we can figure out how to properly address it. Thanks!

Too awful that we use GitHub pages for the website so there's no way for me to preview the effect before merging. I'm going to merge this, and if it doesn't work out (e.g. doesn't allow customizing sizes), I'll let you know so we can figure out how to properly address it. Thanks!

Hey @andreigec FYI your change didn't work out https://yanivam.github.io/react-svg-worldmap/examples/sizing
Sorry I was too lazy to test this locally first. Would you mind testing this yourself and see how to better fix this? You can install this locally and run yarn start in the website folder to preview the effect.

@Josh-Cena  not sure when you say it doesnt work out - the resizing here is what i expect?

@Josh-Cena  not sure when you say it doesnt work out - the resizing here is what i expect?

Previously, every map should be a different size determined by the hardcoded width; now, if you change the tabs, all the maps have largest size that fits the container.

Previously, every map should be a different size determined by the hardcoded width; now, if you change the tabs, all the maps have largest size that fits the container.

Ok the issue is actually that the "responsive" sizing mode is using the window width/height:
https://github.com/yanivam/react-svg-worldmap/blob/main/lib/src/utils.ts#L29
This wont work if the svg occupies a div that is not the full width of the screen - like with my example where it is roughly half the screen.

Ok the issue is actually that the "responsive" sizing mode is using the window width/height:
https://github.com/yanivam/react-svg-worldmap/blob/main/lib/src/utils.ts#L29
This wont work if the svg occupies a div that is not the full width of the screen - like with my example where it is roughly half the screen.

Ah, so we should use the bounding container's width instead. Would you send another PR to revert this change and see how we could retrieve the parent container's width? In the worst case we can just apply viewbox to responsive maps.

Ah, so we should use the bounding container's width instead. Would you send another PR to revert this change and see how we could retrieve the parent container's width? In the worst case we can just apply viewbox to responsive maps.


Bluetooth: Mesh: Permit model walk from any model

Fixes bug where applications that disable model extensions end up in an
infinite loop, and adds support for walking model subtrees, as opposed
to forcing root to be unextended.
Signed-off-by: Trond Einar Snekvik<EMAIL_ADDRESS>

Works fine...


Charts[Template] Consolidate sidecar templates

:tada: This issue has been resolved in version 0.21.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add Haiku as officially supported operating system

 Issue by AdrianArroyoCalle
Thursday Jul 03, 2014 at 11:12 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/15368
This issue was labelled with: I-enhancement in the Rust repository

Haiku is a open source operating system based on BeOS that runs pretty fast in a POSIX environment plus BeAPI. It's licensed under the MIT license and it isn't Linux, Hurd, Solaris or something like that. At the moment Haiku has LLVM, Clang, GCC4, Python, Perl, GNU make, curl and git. Other languages also have support for Haiku like FreePascal. So it will be great if Rust runs natively on Haiku.

I think we probably don't want a tracking issue per-platform that would be nice to support one day, and our policy right now is that we're more than willing to accept patches to port to new OSes but we will likely not actively pursue it ourselves. As a result I'm going to close this.

Too bad... I've been looking into rust, but not being interested in cross-platform support is a game killer.

We are interested in cross-platform support. This issue was closed because we're not keeping track of it through issues. PRs to support Haiku would be welcome.
On Sep 24, 2016, 23:27 -0400, Alexander von Gluck IV<EMAIL_ADDRESS>wrote:

Too bad... I've been looking into rust, but not being interested in cross-platform support is a game killer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/rust-lang/rfcs/issues/799#issuecomment-249400396), or mute the thread (https://github.com/notifications/unsubscribe-auth/AABsittCF3nkXW2HdDqr_1XEEgi7ssw6ks5qteoygaJpZM4DaTS_).


📃: ANALOG CLOCK

:red_circle: Title : ANALOG CLOCK
:red_circle: Aim : To add Analog clock
:red_circle: Tech Stack Used : HTML,CSS,JS
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : MANKALA VAISHNAVI
What is your participant role? (Mention the Open Source Program name. Eg. GSSOC, SSOC, JWOC, etc.)GSSOC

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@VaishnaviMankala19 go ahead.


(Swift) Support raw strings

Resolves #2819
Changes
Add support for raw strings with up to three leading/trailing hashes. In theory, raw strings can have any number of hashes, as long as they’re balanced, but more than one is rarely used.
Checklist

[x] Added markup tests, or they don't apply here because...
[x] Updated the changelog at CHANGES.md
[x] Added myself to AUTHORS.txt, under Contributors

That same # symbol can now be used inside strings, to mark special characters. For example, if you want to use string interpolation, you should now use #(variableName) rather than just (variableName), like this:

I wonder if we should highlight such things?

When you use # with a string it affects the way Swift understands special characters in the string: \ no longer acts as an escape character, so \n literally means a backslash then an “n” rather than a line break

So it sounds like the contains needs to be changed for raw strings to not include escapes...

I'm afraid this is about as much as I can contribute in the short term, so I'm hoping you can take that up.
I even had to install NPM specifically for this, which should tell you how familiar I am with JS codebases 😅

But even if you don't, I'm hoping this small fix can at least make it in. At the moment, raw strings are highlighted wrong. This would at least highlight them as a string, even if it's not perfect.
I also don't see any difference with normal Swift strings. They also highlight as one big hljs-string, even when they contain escapes or interpolated values.  For example:
"1.\tACE\t976\n2.\tBOB\t952\n3.\tCU2\t897"

becomes:
"1.\tACE\t976\n2.\tBOB\t952\n3.\tCU2\t897"

and
"Hi \(player), your score is: \(score)."

becomes:
"Hi \(player), your score is: \(score)."

I also don't see any difference with normal Swift strings.

It's not visual.  Right now an extra escape would throw everything off:
#" \"#

This sting never ends because \" is an escape sequence... so your rule will never find the "# terminating sequence it's looking for, etc...

And you found a bug, subst should indeed be highlighted:

I'm afraid this is about as much as I can contribute in the short term, so I'm hoping you can take that up.

If not I, someone else.  Thanks for the effort! :)

Thanks for having Swift support in the first place 😅

Closing this for now until someone has time to circle back to it and complete it fully.  The issue remains open of course (with link to this PR).


Xonsh as default command shell

Hi! Very interesting distro!
I think xonsh shell should be the default shell :)
Thanks for your work!
For community
⬇  Please click the 👍 reaction instead of leaving a +1 or 👍  comment

It could be, but the whole point of the project is to have it python-based. Otherwise, we would have used busybox's default shell, ash, or bash, or something. That's why you can't exit the python interpreter on boot. It IS the shell.

hi @SorrowEater! Yep indeed, but:
from xonsh.main import main
main()

Why you can't run this? )

Wow... I just followed the link you put for xonsh... Yeah, it's doable, and it's cool. I think @joshiemoore feels that if we're making a PythonOS, we should use it's interpreter, which is why we don't use ash, but maybe we could integrate it with snakewm? Like a terminal? That way we're still staying true to Python, but we still have a way to, you know, do linux stuff.

Like, I'm trying to say it's not impossible, but then it's just imbedded Linux with a Python window manager.

We're trying to move away from Linux and make a PYTHON os. I think.

All you need to be pure python is to have core utils that implemented on python (cd, vim, ls, ifconfig, etc). I suppose xonsh is pretty agile and extensible to do what you want.

well... I guess we are imbedded linux... But what I'm trying to say is, someone either tried very hard to make the >>> prompt the default, or someone messed up majorly. If it's the first one, I don't feel comfortable just tearing it down and making it just regular linux. If it's the second one, then xonsh can be seen as a viable alternative. I'll look into it. Maybe I'll give an option between xonsh and the >>> prompt in the release page. That way, people can get a smaller image if needed, but if they want linux utils, then they can also have an option for it. I don't know about the main repo tho...

Okay, I'm back with knowledge of what ash is. Ash is the embedded linux version of the >>> shell. Basically, ash is the default shell, and it pipes to the actual >>> prompt. It was specifically chosen for this project, and for it to be replaced will either require someone willing to do it and make a pull request, or some of the collaborators to agree, that yes, xonsh is better than ash.

Good! It's a good thing to put here the link to the code that could be the start point to research and development.

JFYI. I've made a short try to run xonsh portable binary file (it's proof of concept and non production ready) on busybox in the docker and have a success:
docker run --rm -it busybox

wget https://github.com/anki-code/xonsh-portable-binary/releases/download/0.9.27-7168b26/xonsh
chmod +x xonsh
./xonsh

ls
# bin dev etc
import json
json.loads('{"hello":"busy"}')
# {'hello': 'busy'}

Okay, I'm back with knowledge of what ash is. Ash is the embedded linux version of the >>> shell. Basically, ash is the default shell, and it pipes to the actual >>> prompt. It was specifically chosen for this project, and for it to be replaced will either require someone willing to do it, that person makeing a pull request, and some of the collaborators agreeing, that yes, xonsh is better suited for this project than ash.

Its NOT choosed. Its default shell in busybox.

Okay, I'm back with knowledge of what ash is. Ash is the embedded linux version of the >>> shell. Basically, ash is the default shell, and it pipes to the actual >>> prompt. It was specifically chosen for this project, and for it to be replaced will either require someone willing to do it, that person makeing a pull request, and some of the collaborators agreeing, that yes, xonsh is better suited for this project than ash.

Its NOT choosed. Its default shell in busybox.

Interesting. Well, when I get around to it, I might decide to implement xonsh in my fork, and thanks for the information, I guess...

Okay, I'm back with knowledge of what ash is. Ash is the embedded linux version of the >>> shell. Basically, ash is the default shell, and it pipes to the actual >>> prompt. It was specifically chosen for this project, and for it to be replaced will either require someone willing to do it, that person makeing a pull request, and some of the collaborators agreeing, that yes, xonsh is better suited for this project than ash.

Its NOT choosed. Its default shell in busybox.

Interesting. Well, when I get around to it, I might decide to implement xonsh in my fork, and thanks for the information, I guess...

I try to make a version of snakeware with xonsh

Update! @anki-code, xonsh works on my fork, but it falls back to bash(or maybe sh, I forgot, it's been a while). This is a dependencies issue, thankfully, so it will be resolved soon. Thanks for the suggestion!

Hi @joshiemoore! Why this issue was closed?


Fixed invalid reference to DFSR_PMU constant from CortexM

Regression introduced into v0.26.0.
Reported by @Hoohaha in #865

/morph test


Allow private container registries

Allow private container registries in K8s, Code Engine and knative backends #505
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@erezh16 you had some concerns?

@JosepSampe hold it a bit to merge... @Cohen-J-Omer will test how it works, We have hollidays now, so it will be only in few days from now

I do. A previous discovery by @Cohen-J-Omer suggested that when working with the code engine backend and docker hub, meta-data is not generated by invoking the expected code from the main Lithops code, but rather through some obscure path in the code engine backend itself. This violates the current design of Lithops. This is also what failed for @Cohen-J-Omer during his experiments with a private repository - he couldn't get the meta-data to generate. Because of the design issue, I would hold off this patch until it is code-reviewed and we make sure mata-data is generated again in the right way - outside and independently of the compute back-end.

@Cohen-J-Omer can you please post a comment here with the short report that you prepared that summarizes your observations?

@JosepSampe @gilv @erezh16
After pulling version 234.dev1 and uploading a runtime based on it to icr.io, I've tried running a simple map job (that works when running a runtime image stored in a public docker hub repository), but it fails to extract Python preinstalled modules in function _generate_runtime_meta() of code_engine.py.
This is the exact same issue I've encountered last time I was entrusted with figuring out issue #505.
My best guess is that it has something to do with access authorization, which is supposed to be taken care of by adding  registry access point to your code_engine project and inserting its name in the following field of the job definition:
imagePullSecrets:
- name: 'registry-access'
but alas, it doesn't seem to solve the issue.
Perhaps it needs to be converted to base-64 representation, as frequently done with Kubernetes' secret data?
Attached herein is my last report on the issue:
intermediate assignment report.pdf

@gilv Seems there was an error when setting the container image name, when the image name contains the container registry. Now it is fixed and private repos in IBM CR work properly.

@Cohen-J-Omer see latest commit from Josep..does it resolve the issue?

@gilv
Got the same error.
My course of action:
Pulled new commits> built new runtime image> tagged it to be able to push it to icr.io> pushed it>updated config file> ran lithops clean> ran compute_handler.clean()> tried to run a simple test> got the "Unable to extract Python preinstalled modules" Exception.

@Cohen-J-Omer How did you configure docker_user, docker_password and docker_server vars in config?

Hey @JosepSampe, sorry for the delay, was a bit preoccupied:
The fields you mentioned don't exist in the template config file, rather the following fields:
#docker:
#host: <HOST_IP>
#ssh_user: <SSH_USER>
#ssh_password: <SSH_PASSWORD>
I've created my icr.io registry using an account connected to my w3id, therefore:

ssh_user is<EMAIL_ADDRESS>ssh_password is: the password of my w3id.
host is: https://us.icr.io

I'm using code_engine and cos.
My config file is configured by following "Option 2 (KUBECONFIG file)" in code_engine.md and works well against docker hub repositories.

@Cohen-J-Omer Instructions to make it working are in this PR. You must set these variables in the "code_engine" section (not docker section). The variables are:

@gilv @erezh16 @JosepSampe
Erez and I investigated a bit on the subject of the meta-data mentioned above and reached the following:
 Observations:

Compute backends takes a reference to internal storage, unlike before.

Code_engine backend utilizes the reference to storage to achieve the following:

Creates and persists the mata-data (with extension .meta) to storage by calling  self.capi.create_namespaced_custom_object() - code_engine.py line 539.
Code_engine polls the meta_data until it is found in storage - code_engine.py line 552.
Code_engine returns meta_data from storage.
Lithops invoker persists the final meta_data (with extension .meta.json) in storage.
We verified the above by code analysis and debugging.

 Conculsions:

.meta object is temporary. the real meta data is .meta.json, so lithops design isn't broken.

Does the code_engine backend has to use storage to create the meta_data?

@JosepSampe I've read the newly committed code_engine.md, but the renamed fields you mentioned seem to address users who opted to apply configuration via "Option 1 (IBM IAM):" alone.

@Cohen-J-Omer does it works now when you setup keys as @JosepSampe suggested?

@gilv
Great job @JosepSampe, but as a user, who read your newly committed code_engine.md file, how am i supposed to know that if I'm using a private repository, i'll to support my decision by:

Adding this specific combination of fields (mentioned in your last comment) to the config template?
For example without your comment i would have chosen container_registry field instead of docker_server.
Initialize docker_user to iamapikey?
Initialize docker_password to ?

I've created a new config file and this time configured the code_engine part according to option1 in config/compute/code_engine.md.
My code_engine section in my config file:
code_engine:
    namespace : name-space achieved by following option1 in code_engine.md.
    region  : us-south
    docker_server: us.icr.io
    docker_user: iamapikey
    docker_password: my api key
    runtime: us.icr.io/omer-test/lithops-ce-pr657-v385

@Cohen-J-Omer Can you post debug logs?

As far as I can tell, logs aren't created in the usual logs folder before runtime meta is generated so I've simply copied the output in debug mode and pasted it here:
logs.txt

@Cohen-J-Omer Seems there was a problem in the clean() method that prevented to delete the already deployed runtimes. Now it is fixed. To make sure everything is cleaned, first delete all your job definitions using the IBM Dashboard. Then try this PR again.


Don't write an empty k3s service on disk

just use the one that was created by the k3s installer script
Fixes: https://github.com/kairos-io/kairos/issues/2125

We built an image with this for fedora and it works.

We built an image with this for fedora and it works.

did you tried with a master/agent or just single-node? https://github.com/kairos-io/provider-kairos/pull/519#discussion_r1447550521 would probably get unnoticed until you try specifically to customize how you start k3s or k3s-agent

@mudler validated it and it's working correctly on alpine too. This is because the installer from k3s creates a unit file which ends with:
if [ -f /etc/environment ]; then . /etc/environment; fi
if [ -f /etc/rancher/k3s/k3s-agent.env ]; then . /etc/rancher/k3s/k3s-agent.env; fi

and we write to /etc/rancher/k3s/k3s-agent.env the following:
K3S_TOKEN="..."
K3S_URL="https://<IP_ADDRESS>:6443"
command_args="agent --with-node-id >>/var/log/k3s-agent.log 2>&1"


Add option to NestingDepth to ignore parent reference suffixes

As you may know, since SASS 3.3.0
("The parent selector, &, can be used with an identifier suffix..." http://sass-lang.com/documentation/file.SASS_CHANGELOG.html#smaller_improvements_2)
we can use the ampersand character (&) to build compound selectors.
This is quite usefull if you use BEM principles for writing your classnames selectors.
Take a look at this SASS/SCSS example:
.block {
&--state {
color: blue;
}
}
That will compile to the following CSS:
.block--state {
color: blue;
}
When I run CSS Lint on my SCSS source code, it considers that I'm using nesting while in reality I'm not.
It could look like nesting but in fact, I'm just concatenating several string into a single classname.
Do you consider this as an issue ?

Hey @entipe, thanks for raising this issue.
I agree that in this particular case the resulting code generated is not actually nested, but I believe the intent of the NestingDepth linter is also to help keep your SCSS code "flat". Thus even though introducing nesting doesn't really add another level of actual nesting, it's still desirable from a readability perspective to keep the amount of syntactical nesting in your SCSS code limited. The deeper your selectors are written the harder they can be to read.
Having said that, I would be open to a pull request adding an option to ignore these sorts of selectors. It would have to handle edge cases like &--state, .some-nested-class { ... } (which you would hopefully never write but nonetheless scss-lint would need to handle them).

+1 to this feature.
Though, I'm sad to report, I have written a selector like &--state, .js-added-class-on-parent & { ... }. Not exactly the selector you mentioned, but pretty close.

+1
This should also apply to &:hover, &:active, &:focus and other pseudo classes.

+1

+1

Implemented in #490.