RuntimeError: Not compiled with METIS support

I would like to try pyg_autoscale. I have tried to install it on my mac M1 Max with MacOS 13.2.1. Here is the sequence of commands that I used:
conda create --name playground_pygas python=3.8
conda activate playground_pygas
pip3 install torch torchvision
pip install torch-scatter -f https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html
pip install torch-sparse -f https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html
pip install torch-geometric
pip install git+https://github.com/rusty1s/pyg_autoscale.git

According to https://pytorch.org/get-started/locally/ the command pip3 install torch torchvision install current stable (2.0.0) PyTorch. Other commands according to https://github.com/rusty1s/pyg_autoscale#readme.
All packages install successfully, but when I try one of the example scripts (for example https://github.com/rusty1s/pyg_autoscale/blob/master/examples/train_gcn.py I get the following error:
mputing METIS partitioning with 40 parts... Traceback (most recent call last):
  File "train_gcn.py", line 25, in <module>
    perm, ptr = metis(data.adj_t, num_parts=40, log=True)
  File "/Users/marco/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch_geometric_autoscale/metis.py", line 31, in metis
    cluster = partition_fn(rowptr, col, None, num_parts, recursive)
  File "/Users/marco/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/_ops.py", line 502, in __call__
    return self._op(*args, **kwargs or {})
RuntimeError: Not compiled with METIS support

What am I doing wrong? Any help is much appreciated.
Thank you!

Can you run
pip uninstall torch-sparse
pip install --verbose torch-sparse -f https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html

Just using --verbose in pip install did not make any difference with respect to above output, so I did -v -v -v (according to https://pip.pypa.io/en/stable/cli/pip/#cmdoption-v):
pip install -v -v -v torch-sparse -f https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html                                                                                (playground_pygas)
Using pip 23.0.1 from /Users/marco/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/pip (python 3.8)
Non-user install because site-packages writeable
Created temporary directory: /private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-build-tracker-rf5jw5bj
Initialized build tracking at /private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-build-tracker-rf5jw5bj
Created build tracker: /private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-build-tracker-rf5jw5bj
Entered build tracker: /private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-build-tracker-rf5jw5bj
Created temporary directory: /private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-install-8_jfygy5
Created temporary directory: /private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-ephem-wheel-cache-fexks8qo
Looking in links: https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html
2 location(s) to search for versions of torch-sparse:
* https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html
* https://pypi.org/simple/torch-sparse/
Fetching project page and analyzing links: https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html
Getting page https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html
Looking up "https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html" in the cache
Request header has "max_age" as 0, cache bypassed
Starting new HTTPS connection (1): pytorch-geometric.com:443
https://pytorch-geometric.com:443 "GET /whl/torch-2.0.0+cpu.html HTTP/1.1" 304 0
Fetched page https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html as text/html
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/pyg_lib-0.2.0%2Bpt20-cp310-cp310-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/pyg_lib-0.2.0%2Bpt20-cp311-cp311-macosx_10_15_universal2.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/pyg_lib-0.2.0%2Bpt20-cp38-cp38-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/pyg_lib-0.2.0%2Bpt20-cp39-cp39-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/pyg_lib-0.2.0%2Bpt20cpu-cp310-cp310-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/pyg_lib-0.2.0%2Bpt20cpu-cp311-cp311-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/pyg_lib-0.2.0%2Bpt20cpu-cp38-cp38-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/pyg_lib-0.2.0%2Bpt20cpu-cp39-cp39-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1%2Bpt20cpu-cp310-cp310-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1%2Bpt20cpu-cp310-cp310-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1%2Bpt20cpu-cp311-cp311-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1%2Bpt20cpu-cp311-cp311-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1%2Bpt20cpu-cp38-cp38-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1%2Bpt20cpu-cp38-cp38-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1%2Bpt20cpu-cp39-cp39-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1%2Bpt20cpu-cp39-cp39-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1-cp310-cp310-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1-cp311-cp311-macosx_10_9_universal2.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1-cp38-cp38-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_cluster-1.6.1-cp39-cp39-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1%2Bpt20cpu-cp310-cp310-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1%2Bpt20cpu-cp310-cp310-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1%2Bpt20cpu-cp311-cp311-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1%2Bpt20cpu-cp311-cp311-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1%2Bpt20cpu-cp38-cp38-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1%2Bpt20cpu-cp38-cp38-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1%2Bpt20cpu-cp39-cp39-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1%2Bpt20cpu-cp39-cp39-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1-cp310-cp310-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1-cp311-cp311-macosx_10_9_universal2.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1-cp38-cp38-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_scatter-2.1.1-cp39-cp39-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp310-cp310-linux_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17%2Bpt20cpu-cp310-cp310-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp310-cp310-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17%2Bpt20cpu-cp310-cp310-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp311-cp311-linux_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17%2Bpt20cpu-cp311-cp311-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp311-cp311-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17%2Bpt20cpu-cp311-cp311-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp38-cp38-linux_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17%2Bpt20cpu-cp38-cp38-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp38-cp38-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17%2Bpt20cpu-cp38-cp38-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp39-cp39-linux_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17%2Bpt20cpu-cp39-cp39-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp39-cp39-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17%2Bpt20cpu-cp39-cp39-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp310-cp310-macosx_10_15_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17-cp310-cp310-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp311-cp311-macosx_10_9_universal2) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17-cp311-cp311-macosx_10_9_universal2.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp38-cp38-macosx_10_15_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17-cp38-cp38-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: none of the wheel's tags (cp39-cp39-macosx_10_15_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_sparse-0.6.17-cp39-cp39-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2%2Bpt20cpu-cp310-cp310-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2%2Bpt20cpu-cp310-cp310-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2%2Bpt20cpu-cp311-cp311-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2%2Bpt20cpu-cp311-cp311-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2%2Bpt20cpu-cp38-cp38-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2%2Bpt20cpu-cp38-cp38-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2%2Bpt20cpu-cp39-cp39-linux_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2%2Bpt20cpu-cp39-cp39-win_amd64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2-cp310-cp310-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2-cp311-cp311-macosx_10_9_universal2.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2-cp38-cp38-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
  Skipping link: wrong project name (not torch-sparse): https://data.pyg.org/whl/torch-2.0.0%2Bcpu/torch_spline_conv-1.2.2-cp39-cp39-macosx_10_15_x86_64.whl (from https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html)
Fetching project page and analyzing links: https://pypi.org/simple/torch-sparse/
Getting page https://pypi.org/simple/torch-sparse/
Found index url https://pypi.org/simple
Looking up "https://pypi.org/simple/torch-sparse/" in the cache
Request header has "max_age" as 0, cache bypassed
Starting new HTTPS connection (1): pypi.org:443
https://pypi.org:443 "GET /simple/torch-sparse/ HTTP/1.1" 304 0
Fetched page https://pypi.org/simple/torch-sparse/ as application/vnd.pypi.simple.v1+json
  Found link https://files.pythonhosted.org/packages/21/a6/af5865f7bc2dc45ea789ebb35bdf5d84c05e140d7d2ec7e5823d24db176f/torch_sparse-0.1.0.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.1.0
  Found link https://files.pythonhosted.org/packages/02/4f/89bcb156022a3960c4db852915c64ea78b4e993e0f8d7a83e60e6819fc11/torch_sparse-0.2.0.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.2.0
  Found link https://files.pythonhosted.org/packages/8f/41/98db80cc9d9345c76445393661ce4dd3e08fc46fb17028e7706612063e4d/torch_sparse-0.2.1.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.2.1
  Found link https://files.pythonhosted.org/packages/73/5b/5b7b6c66148afaa5e2ed8a3e18e109361957d28e67032d92cb282d173f32/torch_sparse-0.2.2.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.2.2
  Found link https://files.pythonhosted.org/packages/43/2a/bb2ead5b33c6932937c6c74199ebecd72bd4b3ab224842a50366e5b2af4a/torch_sparse-0.2.3.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.2.3
  Found link https://files.pythonhosted.org/packages/73/72/e374662f6f47d9ac0e082a6d5c18d14e15c52863e89c6bc6957a0d2ed026/torch_sparse-0.2.4.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.2.4
  Found link https://files.pythonhosted.org/packages/b0/0a/2ff678e0d04e524dd2cf990a6202ced8c0ffe3fe6b08e02f25cc9fd27da0/torch_sparse-0.4.0.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.4.0
  Found link https://files.pythonhosted.org/packages/c7/3e/aa5449787910283d846a7c739899ccf8c53c914f8a7aee7bc500a32dc091/torch_sparse-0.4.1.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.4.1
  Found link https://files.pythonhosted.org/packages/7d/c5/1f73917168aa9816f41e0696f266fa07d0ebfe8d25c3e63a0f08440534b9/torch_sparse-0.4.2.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.4.2
  Found link https://files.pythonhosted.org/packages/08/4e/a268613fa6a92ffbc65b89e66fc8be5590801937185007f0f7bcb75ea21f/torch_sparse-0.4.3.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.4.3
  Found link https://files.pythonhosted.org/packages/0e/bf/6242893c898621e7e4756e1ad298e903df6dfae208aec1c32adf8cfd1f7f/torch_sparse-0.4.4.tar.gz (from https://pypi.org/simple/torch-sparse/), version: 0.4.4
  Found link https://files.pythonhosted.org/packages/92/80/7137d14dac46d515373d8b3eb47e2565ecfd646ba8658a6a6a1c24e49a2c/torch_sparse-0.5.1.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.5.1
  Found link https://files.pythonhosted.org/packages/11/17/03bd3a1f056d971e498bd1ad818bbde3dd5409c845ed2ce76186fec65dd2/torch_sparse-0.6.0.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.0
  Found link https://files.pythonhosted.org/packages/12/9e/66247cbc250e746d06de35c6eb226ec39f4cb4be46adf6ee27527915910b/torch_sparse-0.6.1.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.1
  Found link https://files.pythonhosted.org/packages/dc/65/ee198eae5c517cfc6d05473bf4ec8593830dc61446ffd65fdb7cd3b469ce/torch_sparse-0.6.3.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.3
  Found link https://files.pythonhosted.org/packages/92/d4/7261b5ee3ff529ac3652fda2ad9757c0fb3cde514014a9c26fe71bad38e9/torch_sparse-0.6.4.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.4
  Found link https://files.pythonhosted.org/packages/18/0d/a0ab465c6fd30318e8ce2c121424fb09573e46eb16231e6fedb6ddd953f5/torch_sparse-0.6.5.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.5
  Found link https://files.pythonhosted.org/packages/db/d1/968436c29959c321740ee95f781c961f12b2d23f0ecdbdaaf3ccf64ddc94/torch_sparse-0.6.6.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.6
  Found link https://files.pythonhosted.org/packages/ce/c0/f5ccc280629765cf1e97b601426cad6170d00603cf9836ba52f85d44ac27/torch_sparse-0.6.7.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.7
  Found link https://files.pythonhosted.org/packages/3c/dd/f34dce6512a3922948c3ac0cf50cceb2eeafeedd34a278d502eb77d07dc0/torch_sparse-0.6.8.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.8
  Found link https://files.pythonhosted.org/packages/9a/86/699eb78ea7ce259da7f9953858ec2a064e4e5f5e6bf7de53aa6c8bb8b9a8/torch_sparse-0.6.9.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.9
  Found link https://files.pythonhosted.org/packages/c7/49/c97315cd579a19d4e575ca06dd8f79f43c00c9c38658fbe91116cd7909dd/torch_sparse-0.6.10.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.10
  Found link https://files.pythonhosted.org/packages/5a/81/f66f60ef6ce915ca54a4fcd0c97ec8a1a802312c1774caf329a866ebbf31/torch_sparse-0.6.11.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.11
  Found link https://files.pythonhosted.org/packages/00/40/208c5b8ae34c89403d9da648c9689465880539d95a4ad570ac9d6f301b72/torch_sparse-0.6.12.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.6), version: 0.6.12
  Found link https://files.pythonhosted.org/packages/ee/44/b4a1d6d7fa67309781005c0e36723dd0bd745fc1a20c9330796055953b10/torch_sparse-0.6.13.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.7), version: 0.6.13
  Found link https://files.pythonhosted.org/packages/ed/f0/8d198555417336fac1b56c23b50699717cfc743f5d6bd5d1ece59695aa4c/torch_sparse-0.6.14.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.7), version: 0.6.14
  Found link https://files.pythonhosted.org/packages/6d/79/df42a4bf93191ff44d31ba58eb3ec98a02dfb7402fac34852f864c4b3999/torch_sparse-0.6.15.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.7), version: 0.6.15
  Found link https://files.pythonhosted.org/packages/88/e8/9e75676a3415d438fdb354b5ee0ffac777eb447fe4924224beef7529ea43/torch_sparse-0.6.16.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.7), version: 0.6.16
  Found link https://files.pythonhosted.org/packages/cb/ff/21d4674bdf232cd7a2bdbbbb04c35ba1cbdf444d4f3331f5d7eb6c5d4a8f/torch_sparse-0.6.17.tar.gz (from https://pypi.org/simple/torch-sparse/) (requires-python:>=3.7), version: 0.6.17
Skipping link: unsupported archive format: .html: https://pytorch-geometric.com/whl/torch-2.0.0+cpu.html
Skipping link: not a file: https://pypi.org/simple/torch-sparse/
Given no hashes to check 29 links for project 'torch-sparse': discarding no candidates
Using cached wheel link: file:///Users/marco/Library/Caches/pip/wheels/22/b4/54/ca8f8938b70218d75f3b96bb1c2126d16521fb5996191b4efe/torch_sparse-0.6.17-cp38-cp38-macosx_11_0_arm64.whl
Collecting torch-sparse
  Using cached torch_sparse-0.6.17-cp38-cp38-macosx_11_0_arm64.whl
  Added torch-sparse from file:///Users/marco/Library/Caches/pip/wheels/22/b4/54/ca8f8938b70218d75f3b96bb1c2126d16521fb5996191b4efe/torch_sparse-0.6.17-cp38-cp38-macosx_11_0_arm64.whl to build tracker '/private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-build-tracker-rf5jw5bj'
  Removed torch-sparse from file:///Users/marco/Library/Caches/pip/wheels/22/b4/54/ca8f8938b70218d75f3b96bb1c2126d16521fb5996191b4efe/torch_sparse-0.6.17-cp38-cp38-macosx_11_0_arm64.whl from build tracker '/private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-build-tracker-rf5jw5bj'
Requirement already satisfied: scipy in /Users/marco/miniconda3/envs/playground_pygas/lib/python3.8/site-packages (from torch-sparse) (1.10.1)
Requirement already satisfied: numpy<1.27.0,>=1.19.5 in /Users/marco/miniconda3/envs/playground_pygas/lib/python3.8/site-packages (from scipy->torch-sparse) (1.24.2)
Created temporary directory: /private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-unpack-u1wd33_7
Installing collected packages: torch-sparse

Successfully installed torch-sparse-0.6.17
Remote version of pip: 23.0.1
Local version of pip:  23.0.1
Was pip installed by pip? False
Removed build tracker: '/private/var/folders/x_/3z3xyvcs3tj071fqts801cg00000gn/T/pip-build-tracker-rf5jw5bj'

Oh, I somehow missed you are on macOS. In this case, the library will get built from source, and METIS needs to be installed beforehand in order to get picked up :(

Two questions:

You write "the library will get built from source, and METIS needs to be installed beforehand in order to get picked up": can you please tell me how to do that, or point me to a link with howto? Thank you.
Is is different if I install on RedHat?

You can find instructions here.

The problem is not related to macOS. I have re-installed a new conda environment on a RedHad server with CUDA, and I still have the same problem: installation steps:
conda create --name playground_pygas python=3.8
conda activate playground_pygas
pip3 install torch --index-url https://download.pytorch.org/whl/cu118
pip install torch-scatter -f https://pytorch-geometric.com/whl/torch-2.0.0+cu118.html
pip install torch-sparse -f https://pytorch-geometric.com/whl/torch-2.0.0+cu118.html
pip install torch-geometric
pip install git+https://github.com/rusty1s/pyg_autoscale.git

Looks like PyGAS is compiled without CUDA support. You may find look when installing via
FORCE_CUDA=1 pip install git+https://github.com/rusty1s/pyg_autoscale.git

FORCE_CUDA=1 pip install git+https://github.com/rusty1s/pyg_autoscale.git helped and I can successfully run train_gcn.py and train_gcn2.py, but when I run train_gin.py I get the following error:
Computing METIS partitioning with 10000 parts... Done! [9.03s]
Permuting data... Done! [6.65s]
/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/utils/data/dataloader.py:561: UserWarning: This DataLoader will create 6 worker processes in total. Our suggested max number of worker in current system is 2, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
  warnings.warn(_create_warning_msg(
Pre-processing subgraphs... Done! [0.30s]
/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch_geometric/deprecation.py:22: UserWarning: 'data.DataLoader' is deprecated, use 'loader.DataLoader' instead
  warnings.warn(out)
Traceback (most recent call last):
  File "train_gin.py", line 179, in <module>
    loss = train(model, train_loader, optimizer)
  File "train_gin.py", line 146, in train
    loss.backward()
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/_tensor.py", line 487, in backward
    torch.autograd.backward(
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/autograd/__init__.py", line 200, in backward
    Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.FloatTensor [29934, 128]], which is output 0 of ReluBackward0, is at version 1; expected version 0 instead. Hint: enable anomaly detection to find the operation that failed to compute its gradient, with torch.autograd.set_detect_anomaly(True).

I have tried to rerun using the hint, that is adding torch.autograd.set_detect_anomaly(True), and this is the result:
Computing METIS partitioning with 10000 parts... Done! [8.97s]
Permuting data... Done! [6.62s]
/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/utils/data/dataloader.py:561: UserWarning: This DataLoader will create 6 worker processes in total. Our suggested max number of worker in current system is 2, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
  warnings.warn(_create_warning_msg(
Pre-processing subgraphs... Done! [0.39s]
/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch_geometric/deprecation.py:22: UserWarning: 'data.DataLoader' is deprecated, use 'loader.DataLoader' instead
  warnings.warn(out)
/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/autograd/__init__.py:200: UserWarning: Error detected in ReluBackward0. Traceback of forward call that caused the error:
  File "train_gin.py", line 179, in <module>
    loss = train(model, train_loader, optimizer)
  File "train_gin.py", line 144, in train
    out, reg = model(batch.x, batch.adj_t, *args)
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch_geometric_autoscale/models/base.py", line 149, in __call__
    out = self.forward(x, adj_t, batch_size, n_id, offset, count, **kwargs)
  File "train_gin.py", line 102, in forward
    h = self.mlps[-1](h)
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/nn/modules/container.py", line 217, in forward
    input = module(input)
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/nn/modules/activation.py", line 103, in forward
    return F.relu(input, inplace=self.inplace)
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/nn/functional.py", line 1457, in relu
    result = torch.relu(input)
 (Triggered internally at ../torch/csrc/autograd/python_anomaly_mode.cpp:114.)
  Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
Traceback (most recent call last):
  File "train_gin.py", line 179, in <module>
    loss = train(model, train_loader, optimizer)
  File "train_gin.py", line 146, in train
    loss.backward()
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/_tensor.py", line 487, in backward
    torch.autograd.backward(
  File "/u/masbodio/miniconda3/envs/playground_pygas/lib/python3.8/site-packages/torch/autograd/__init__.py", line 200, in backward
    Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.FloatTensor [29934, 128]], which is output 0 of ReluBackward0, is at version 1; expected version 0 instead. Hint: the backtrace further above shows the operation that failed to compute its gradient. The variable in question was changed in there or anywhere later. Good luck!

Any idea, please?

Can you try to make this line an out-of-place function. This behavior might have changed due to different PyTorch versions:
h = h.clone()
h += x[:h.size(0)]

This does not solve the problem.

Can you change this line here to relu() instead of relu_()?


Fix Node::add_sibling parent check

Replace data.blocked > 0 by data.parent->data.blocked > 0 in order to check if the parent is busy.
implement https://github.com/godotengine/godot/pull/78834#discussion_r1246618876 and https://github.com/godotengine/godot/pull/78834#discussion_r1246625740

Thanks!

Cherry-picked for 4.1.1.


Read config filename from workflow rather than assuming the default location

The Builder module (builder_web.py) currently reads the configuration file for a workflow from the default config/config.yaml file. Instead, parse the workflow file for the configfile tag and source from there.

This issue is simplied by #89 as configurations are only loaded as needed, so the Snakefile can be loaded first, checked for config filenames and then used for config loading. Note that these filenames may need to propogate into the builder system, or be redetermined there.


The different params between large segment and

Hi, the code is very good! But I have some questions.
In you main.cpp, detector short segments use follow params
 // Gaussian kernel size
  int ksize = 5;
  // Sigma of the gaussian kernel
  float sigma = 1;
  // The threshold of pixel gradient magnitude.
  // Only those pixels whose gradient magnitude are larger than
  // this threshold will be taken as possible edge points.
  float gradientThreshold = 30;
  // If the pixel's gradient value is bigger than both of its neighbors by a
  // certain anchorThreshold, the pixel is marked to be an anchor.
  uint8_t anchorThreshold = 8;
  // Anchor testing can be performed at different scan intervals, i.e.,
  // every row/column, every second row/column
  unsigned int scanIntervals = 2;

  // Minimum line segment length
  int minLineLen = 15;
  // Threshold used to check if a list of edge points for a line segment
  double lineFitErrThreshold = 0.2;
  // Threshold used to check if a new pixel is part of an already fit line segment
  double pxToSegmentDistTh = 1.5;
  // Threshold used to validate the junction jump region. The first eigenvalue of the gradient
  // auto-correlation matrix should be at least junctionEigenvalsTh times bigger than the second eigenvalue
  double junctionEigenvalsTh = 10;
  // the difference between the perpendicular segment direction and the direction of the gradient
  // in the region to be validated must be less than junctionAngleTh radians
  double junctionAngleTh = 10 * (M_PI / 180.0);
  // The threshold over the validation criteria. For ELSED, it is the gradient angular error in pixels.
  double validationTh = 0.15;

  // Whether to validate or not the generated segments
  bool validate = true;
  // Whether to jump over junctions
  bool treatJunctions = true;
  // List of junction size that will be tested (in pixels)
  std::vector<int> listJunctionSizes = {5, 7, 9};

when you detect large segments. what is the params？

Hii, thanks a lot for your interest. All the parameters are the same except the listJunctionSizes by an empty list, this prevents the algorithm from trying to jump at gradient discontinuities and therefore, it detects only short segments:
https://github.com/iago-suarez/ELSED/blob/36b4547fa729fcf10c8764dba055d38e59aa25f1/src/main.cpp#L43-L45
If this answers your question, please close the issue.
Best,
Iago.


Add a license info link to the README file

As discussed in https://github.com/ForNeVeR/wpf-math/issues/110#issuecomment-361077280

Thanks for your review!


Installation of the add-on fails on devices with little memory

Hello,
I tried to install the add-on directly from the repository as described, but it always fail with this output on the logfile:
make  --no-print-directory -C python
swig -I../../../../pjlib/include -I../../../../pjlib-util/include -I../../../../pjmedia/include -I../../../../pjsip/include -I../../../../pjnath/include -c++  -w312  -python -o pjsua2_wrap.cpp ../pjsua2.i
python3 setup.py build
running build
running build_py
creating build
creating build/lib.linux-aarch64-3.9
copying pjsua2.py -> build/lib.linux-aarch64-3.9
running build_ext
building '_pjsua2' extension
creating build/temp.linux-aarch64-3.9
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -ffile-prefix-map=/build/python3.9-PN012d/python3.9-3.9.2=. -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -ffile-prefix-map=/build/python3.9-PN012d/python3.9-3.9.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.9 -c pjsua2_wrap.cpp -o build/temp.linux-aarch64-3.9/pjsua2_wrap.o -g -O2 -DPJ_AUTOCONF=1 -I/include -O2 -DPJ_IS_BIG_ENDIAN=0 -DPJ_IS_LITTLE_ENDIAN=1 -fPIC -DPJMEDIA_USE_OLD_FFMPEG=1 -DPJMEDIA_USE_OLD_FFMPEG=1 -I/pjproject/pjlib/include -I/pjproject/pjlib-util/include -I/pjproject/pjnath/include -I/pjproject/pjmedia/include -I/pjproject/pjsip/include
aarch64-linux-gnu-gcc: fatal error: Killed signal terminated program cc1plus
compilation terminated.
error: command '/usr/bin/aarch64-linux-gnu-gcc' failed with exit code 1
make[1]: *** [Makefile:37: _pjsua2.so] Error 1
make: *** [Makefile:29: python] Error 2
Removing intermediate container 7354840e65f3
Any ideas how to fix this?
I have a pretty new installation of Home Assistant OS x64 on a raspberry pi 3

Could be an Out Of Memory kill. What amount of memory does your Raspi 3 have?

Okay, I have an raspberry pi 3B, it should have 1GB RAM. Any ideas to get around this?

There is a way to pre-build the docker images and put them on docker hub, but I actually like that the build is done transparently on the device itself. If you want to do that yourself I can only point you in this direction:
https://developers.home-assistant.io/docs/add-ons/publishing/

I read the link you provided but I am not sure if I can manage to do this on my own. I read that it is possible to reduce the memory consumption of make with providing the -j switch to reduce the number of parallel processes. Can this be a possible solution?

I don't think that pjsip does any parallelization while compiling, so I don't think so.

Imposible to install on home assistant OS 2021.11.5.
Even freezes the system and not accessible , I had to power restart
Intel nuc 4gb ram, its a pity I would like to try this

I finally managed to install it as i moved from Pi3@1GB to Pi4@4GB

There are now pre-compiled images available which also speeds up installation a lot.


fix(components): autocomplete, tabIndex is not passed on input

Closes #2372
📝 Description
Autocomplete, tabIndex is not passed on input
⛳ Current behavior (updates)
inputProps don't get passed down to the input element.
🚀 New behavior
It is used to otherProps override slotsProps.inputProps. Now slotsProps.inputProps(user input) takes precedence over.
💣 Is this a breaking change (Yes/No):
No.
📝 Additional Information

Good catch! @kuri-sun could you please add the changeset?

@jrgarciadev Absolutely


Build is broken on master

Fetched most recent master, ran cargo build --release, fails with the following errors:
error[E0658]: use of unstable library feature 'map_first_last'
   --> /home/usr/.cargo/registry/src/github.com-1ecc6299db9ec823/redb-0.13.0/src/tree_store/page_store/cached_file.rs:257:50
    |
257 |                 if let Some((_, v)) = write_lock.pop_first() {
    |                                                  ^^^^^^^^^
    |
    = note: see issue #62924 <https://github.com/rust-lang/rust/issues/62924> for more information

error[E0658]: use of unstable library feature 'map_first_last'
   --> /home/usr/.cargo/registry/src/github.com-1ecc6299db9ec823/redb-0.13.0/src/tree_store/page_store/cached_file.rs:319:58
    |
319 |                     if let Some((offset, buffer)) = lock.pop_first() {
    |                                                          ^^^^^^^^^
    |
    = note: see issue #62924 <https://github.com/rust-lang/rust/issues/62924> for more information

Running:
rustc 1.65.0 (897e37553 2022-11-02)
rustc 1.65.0 (897e37553 2022-11-02)
On Ubuntu 22.04

We're on the newest stable rustc (rustc 1.67.0 (fc594f156 2023-01-24)) because of our bleeding edge database.
Just do rustup update

I think this fixes it. Please feel free to reopen if updating Rust doesn't work!

rustup update doesnt work, says:
info: no updatable toolchains installed
info: cleaning up downloads & tmp directories
even tho rustc --version shows me rustc 1.61.0
any advice ?

What is the output of rustup show?

Default host: armv7-unknown-linux-gnueabihf
rustup home:  /root/snap/rustup/common/rustup
no active toolchain

Maybe try rustup default stable to activate the stable toolchain. Otherwise reinstall or try looking at rustup help. I'm not at my computer at the moment so unfortunately can't look up the commands.

So I manage to install it but still cant find nothing with ord -v (ord --version) within the system even tho I had this:
Compiling ord v0.4.2 (/ssd/ordinals/ord)
Finished dev [unoptimized + debuginfo] target(s) in 22m 19s
I had to install it manually with cargo build since I had this error when I tried to execute ./install.sh
"install: error: Could not determine target from output of uname -m-uname -s, please use --target: armv7l-Linux"

When you compile with cargo build --release the executable is put in ./target/release/ord you can copy it out and put it anywhere your shell can find it. Or you use cargo install --path <PATH> to directly install somewhere in your $PATH

When you compile with cargo build --release the executable is put in ./target/release/ord you can copy it out and put it anywhere your shell can find it. Or you use cargo install --path <PATH> to directly install somewhere in your $PATH

Might be good to mention this in the build guide for folks compiling from git.


spa/npm with VS running as admin

Describe the bug
I am unable to start my Angular/SPA project which uses npm when Visual Studio 2019 is running as administrator. This is required to deploy my projects to IIS.
To Reproduce
Steps to reproduce the behavior:

Start VS2019 as Administrator
New ASP.NET Core Web Application project, choose Angular.
Debug project.
Error:

Now listening on: http://<IP_ADDRESS>:39986
Application started. Press Ctrl+C to shut down.
       Error: EPERM: operation not permitted, mkdir 'C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm'

Additional context

VS2019 Preview 3
NodeJS: 11.10.0
npm 6.8.0

Upgrade to 2.2.2. This is a known issue


Plan output location when backend is disabled

Hello,
I may have missed something but I can't find my plan anywhere.
I use
backendConfig:
    disable: true

because I don't want to use the provided Kubernetes backend, I want to use my own S3 backend (that is versioned and not limited to 1MB).
I looked at my Terraform object and could not find the plan.
I looked at the generated secret and I found dummy plan in place of my plan, found https://github.com/weaveworks/tf-controller/blob/79242b66cbe30c39bdd62c08fb34b720e2795f8d/runner/server.go#L425.
It looks the state backend is used for plans.
I my case having plans in Kubernetes is fine, but I need a way to distinguish state and plan backends.

We have a plan but do not support other backends yet. The backendConfig.disable: true is designed for Terraform Cloud integration.
There's a discussion on supporting other backends (https://github.com/weaveworks/tf-controller/issues/97) and there's a contributor who's working on it, but he's been busy until now so the PR hasn't landed yet.

Makes sense. Thank you for your time. Will wait for this feature.


Add a Quart view

Description
This PR adds a Quart view, as originally asked in this issue but never actually implemented.
Quart 0.19 being a major release now depending on Flask 3 and Werkzeug 3, I had to bump the Flask support and remove pytest-flask which is incompatible (but AFAIK not required by Strawberry).
Note that I did not commit poetry.lock to avoid causing too many conflicts. I can if you want me to.
Types of Changes

[ ] Core
[ ] Bugfix
[x] New feature
[ ] Enhancement/optimization
[x] Documentation

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release adds a Quart view.
Here's the tweet text:
🆕 Release (next) is out! Thanks to Pierre Chapuis for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release adds a Quart view.
Here's the tweet text:
🆕 Release (next) is out! Thanks to Pierre Chapuis for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)

Thanks for contributing to Strawberry! 🎉 You've been invited to join
the Strawberry GraphQL organisation 😊
You can also request a free sticker by filling this form: https://forms.gle/dmnfQUPoY5gZbVT67
And don't forget to join our discord server: https://strawberry.rocks/discord 🔥


jf git count-contributors required parameters information is incorrect

Describe the bug
In the help content for the JF CLI command jf git cc, the --scm-type command is listed as [Optional], but it is required when you run the command.
See below
> jf --version
jf version 2.65.0

> jf git cc --help

Name:
  jf git count-contributors - List all GIT providers' contributing developers.

Usage:
  jf git count-contributors [command options]

Options:
  --detailed-summary    [Default: false] Set to true to get a contributors detailed summary.
  --input-file          [Optional] Path to an input file in YAML format contains multiple git providers. With this option, all other scm flags will be ignored and only git servers mentioned in the file will be examined..
  --months              [Default: 1] Number of months to analyze.
  --owner               [Optional] The format of the owner key depends on the Git provider: On GitHub and GitLab, the owner is typically an individual or an organization, On Bitbucket, the owner can also be a project. In the case of a private instance on Bitbucket, the individual or organization name should be prefixed with '~'.
  --repo-name           [Optional] List of semicolon-separated(;) repositories names to analyze, If not provided all repositories related to the provided owner will be analyzed.
  --scm-api-url         [Optional] SCM API URL. For example: 'https://api.github.com'.
  --scm-type            [Optional] SCM type. Possible values are: gitlab, github and bitbucket.
  --token               [Optional] SCM API token. In the absence of a flag, tokens should be passed in the JF_GIT_TOKEN enviroment variable, or in the corresponding environment variables 'JFROG_CLI_GITLAB_TOKEN, JFROG_CLI_GITHUB_TOKEN or JFROG_CLI_BITBUCKET_TOKEN'.

> jf git cc --owner tomjfrog --months 12 --detailed-summary true
10:57:36 [🔵Info] Trace ID for JFrog Platform logs: 42bc1e3d7b541e98
10:57:36 [🚨Error] The --scm-type option is mandatory

Current behavior
--scm-type is noted as optional.
Reproduction steps
Run the command jf git cc without the --scm-type parameter and it will fail.
Expected behavior
The information in the help content to reference the parameter as required.
JFrog CLI-Security version
2.65
JFrog CLI version (if applicable)
2.65
Operating system type and version
macOS 14.6.1 23G93 x86_64
JFrog Xray version
N/A

Hi @tomjfrog, thank you for reporting this issue.
You can follow the fix here: https://github.com/jfrog/jfrog-cli-security/pull/170, It should be available soon
If you have any more questions or issues in this matter you can reopen this.
Thank you.


added ajax tests for 204 No Content

Description:
Related issue (if exists):

Coverage remained the same at 97.115% when pulling c6e243479ec6389ce513b20c22a2fb5a8e2cf93a on danmarshall:master into 80b817f41084440312954efa3bb0eef4947c8d8b on ReactiveX:master.

Hi @kwonoj I didn't realize this was going to make a 2nd PR :(

Yes, please update original PR to include this changes.
One question - isn't this test supposed to 'fail' with current master's codebase?

I suppose it would only fail if it simulates IE ?

Yes, I thought test case should mock response to check beahvior of json.parse.

I see. Well I am not sure how to handle this, as MockXMLHttpRequest behaves as Chrome / standards. Seems like there would need to be a MockXMLHttpRequest_IE ?

It's rough idea that I haven't tried yet, but I might give a chance of mocking via sinon.

So your original fix was handling IE which does not provide xhr.response or xhr.responseText. In this unit test, we tell the MockXMLHttpRequest to respond:
        'status': 204,
        'contentType': 'application/json',
        'responseText': expected
      });

To simulate the IE behavior, we would just not respondWith responseText, like this:
        'status': 204,
        'contentType': 'application/json'
      });

I don't know if I can call request.respondWith() twice within the same unit test, do you? Otherwise there will be two tests.

it is not prevented to use it multiple times, but as respondWith will update most recent mock response I'd go with separating test cases. You can see some of test cases are testing specific conditions like 'should try to create AXObject for XHR in old version of IE', assume could be applied for this case as well.


Removing double timeout clear from replset.js

This was accidentally introduced during the following refactor:
https://github.com/mongodb-js/mongodb-core/commit/cd44d70f57661ad63c6a65558ffcfa38d1e7d3a2#diff-dc27eebcc66ed957fe1f8d58c5387d0dL856

Thank you for contributing @tlhunter! Two things:

Can you alter your commit message to conform to our commit guidelines
Does this cause an error, or is it just an unnecessary call?


Issues with Network Processor demo

I'm trying to work through the 04_network_processor notebook on a PYNQ-Z1 board running the most recent version of the PYNQ image (v2.3).
I'm running into the some issues with the LinkManager cell. First, it appears that the commands cannot execute from within the notebook. When I sudo the commands individually in the terminal, I get the following error while loading the kernel module:
insmod: ERROR: could not insert module /usr/local/lib/python3.6/dist-packages/pynq_networking/kernel_module/pynqenet.ko: Invalid module format
and I see the following error in the output from dmesg:
pynqenet: disagrees about version of symbol module_layout
I believe these errors are due to a differing kernel version between what the PYNQ board is running (4.14) and what the module was compiled against (4.9). Would it be possible to get an upgraded module compiled against the 2.3, or upcoming 2.4 PYNQ image? (I'm working with @drichmond and he suggested as much)

Hi @yunqu,
@HelloKayT met with @stephenneuendorffer at FPGA. He says that we just need the kernel image rebuilt.
Would you be able to provide this?

@drichmond  Any steps to do this?

The process is briefly described here:
https://github.com/Xilinx/PYNQ-Networking/tree/master/pynq_networking/kernel_module

On Mar 4, 2019, at 10:34 AM, Yun Rock Qu<EMAIL_ADDRESS>wrote:
@drichmond https://github.com/drichmond Any steps to do this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Xilinx/PYNQ-Networking/issues/10#issuecomment-469365768, or mute the thread https://github.com/notifications/unsubscribe-auth/AGFUdJag1l_nP7bQhKele1PG-slvhQznks5vTWdTgaJpZM4bIKih.

This is assuming we had our old kernel building flow, while right now we are trying to do petalinux. I tried to do this before but I am not quite sure how to do it.

Could we rebuild the kernel object on a board with a PYNQ 2.4 image?
That seems like it would simplify the process

On Mar 4, 2019, at 10:42 AM, Yun Rock Qu<EMAIL_ADDRESS>wrote:
This is assuming we had our old kernel building flow, while right now we are trying to do petalinux. I tried to do this before but I am not quite sure how to do it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Xilinx/PYNQ-Networking/issues/10#issuecomment-469370227, or mute the thread https://github.com/notifications/unsubscribe-auth/AGFUdOHIfJBwVBzj8H587zoScTj5iYWyks5vTWkrgaJpZM4bIKih.

Though, I think we need the petalinux header files (which are not on the board)

On Mar 4, 2019, at 10:45 AM, Dustin Richmond<EMAIL_ADDRESS>wrote:
Could we rebuild the kernel object on a board with a PYNQ 2.4 image?
That seems like it would simplify the process

On Mar 4, 2019, at 10:42 AM, Yun Rock Qu<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
This is assuming we had our old kernel building flow, while right now we are trying to do petalinux. I tried to do this before but I am not quite sure how to do it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Xilinx/PYNQ-Networking/issues/10#issuecomment-469370227, or mute the thread https://github.com/notifications/unsubscribe-auth/AGFUdOHIfJBwVBzj8H587zoScTj5iYWyks5vTWkrgaJpZM4bIKih.

Let me try this. Will get back to you later.

Thanks Rock!

On Mar 4, 2019, at 11:17 AM, Yun Rock Qu<EMAIL_ADDRESS>wrote:
Let me try this. Will get back to you later.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Xilinx/PYNQ-Networking/issues/10#issuecomment-469384584, or mute the thread https://github.com/notifications/unsubscribe-auth/AGFUdD2rdchLEWkURQqQg-bCo65XiH7Nks5vTXFEgaJpZM4bIKih.

I think I have recompiled the ko file:
https://github.com/yunqu/PYNQ-Networking/tree/master
This branch has the compiled ko file, and the boot files. Not sure what else I need.
The kernel module does not seem to bring up br0 successfully.

Thanks Rock!
This seems to work. The kernel module installs on my board and I can see it with lsmod.
However, there are some unrelated (and other unknown issues).
For instance

The Python3.6 installation path has changed in PYNQ 2.3+. The library has hardcoded paths
The scapy library seems to be deprecated/renamed, and uses kamene instead (easy name switch)
The mosquitto library must be installed with apt

I can run the 01, 02, 04, and 05 notebooks. I can’t run the 03 notebook (cell 5 fails with ICMP errors).
I can send more detailed error messages if necessary.
Dustin

On Mar 4, 2019, at 1:51 PM, Yun Rock Qu<EMAIL_ADDRESS>wrote:
I think I have recompiled the ko file:
https://github.com/yunqu/PYNQ-Networking/tree/master https://github.com/yunqu/PYNQ-Networking/tree/master
This branch has the compiled ko file, and the boot files. Not sure what else I need.
The kernel module does not seem to bring up br0 successfully.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Xilinx/PYNQ-Networking/issues/10#issuecomment-469435936, or mute the thread https://github.com/notifications/unsubscribe-auth/AGFUdIqYGGRNvwXkA7ZND7LgLekb2q9vks5vTZVNgaJpZM4bIKih.

@drichmond Can you tell me what you did?
Feel free to pull request on my master branch so I can also replicate your progress.
You can open another thread if you think the error message is not related to this thread.

Yeah, I’ll open a new PR later today.

On Mar 5, 2019, at 9:11 AM, Yun Rock Qu<EMAIL_ADDRESS>wrote:
@drichmond https://github.com/drichmond Can you tell me what you did?
Feel free to pull request on my master branch so I can also replicate your progress.
You can open another thread if you think the error message is not related to this thread.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Xilinx/PYNQ-Networking/issues/10#issuecomment-469767130, or mute the thread https://github.com/notifications/unsubscribe-auth/AGFUdNZq32gOVLCr9F5r8le3T6uQT34mks5vTqUkgaJpZM4bIKih.


Internationalization Support

Is your feature request related to a problem? Please describe.
mkdocs-material already supports a wide range of languages, should be great if this package supports more language rather than manually modifying all the templates or sticking with hard-coded English :)
Describe the solution you'd like
Allowing user to feed a data file (such as JSON/YAML) should be feasible enough. Original text could be used as a polyfill to ensure backward compatibility.
Describe alternatives you've considered
Utilizing the gettext module is also a considerable alternative, but I doubt it will be a little bit harder for end users to tweak them.
Also, we can centralize the translation context in the repositories to provide support for other languages natively.

Agreed, we need internationalization. We can probably reuse the same approach as Material for MkDocs, with a Jinja macro containing a dict with keys and translated values. Each handler would have its own macro, since each handler has its own set of templates.

I tried to tweak the code and made a prototype, however I'm not sure where to place the language files, since multiple themes could utilize the same language file. In that case, how could we provide customizations?

Different themes could use different wording, so I believe we should have one language file per theme. WDYT?

That seems reasonable to me. I'll look into it again in the following few days :)

Looks nice to me! Is there something in particular bothering you in your prototype?

Looks nice to me! Is there something in particular bothering you in your prototype?

I'm quite uncertain about handling symbols and capitalization (e.g. description Description Description:), since they might vary much between languages 😕
I'm proposing that we use dotted keys to indicate variants (description.normal description.capitalized, etc.), although I'm not quite certain about their names 😅

I see. Yeah I had the same doubts but eventually concluded this:

having case-sensitive keys for all kinds of capitalization will be a PITA to translate for contributors
case-sensitiveness might not even be a thing in some languages
I believe string methods like upper, title and capitalize will do the right thing depending on the locale? at least better than what we could hardcode in translation files?

Hmmm...

There is no way to perform case conversions and character classifications according to the locale. For (Unicode) text strings these are done according to the character value only, while for byte strings, the conversions and classifications are done according to the ASCII value of the byte, and bytes whose high bit is set (i.e., non-ASCII bytes) are never converted or considered part of a character class such as letter or whitespace.

https://docs.python.org/3/library/locale.html#background-details-hints-tips-and-caveats
So we might have to actually add all kinds of capitalization into the translation files...

I'm proposing that we use dotted keys to indicate variants (description.normal description.capitalized, etc.), although I'm not quite certain about their names sweat_smile

This, or the keys themselves have the expected casing: description, DESCRIPTION, Description:, etc.

This, or the keys themselves have the expected casing: description, DESCRIPTION, Description:, etc.

Sounds quite interesting, in this way the maintenance burden of the templates could be reduced to minimum :)
Could also possibly benefit translators too (by checking the original file less times)

Yeah. It would be a bit cumbersome to translate so many similar keys, but it is not that hard either.

Just submitted mkdocstrings/python#77
However mkdocstrings itself may require a small patch here:
diff --git a/src/mkdocstrings/plugin.py b/src/mkdocstrings/plugin.py
index 5233cf4..cde45a4 100644
--- a/src/mkdocstrings/plugin.py
+++ b/src/mkdocstrings/plugin.py
@@ -201,6 +201,7 @@ class MkdocstringsPlugin(BasePlugin):

         extension_config = {
             "theme_name": theme_name,
+            "locale": str(config["theme"]["locale"]),
             "mdx": config["markdown_extensions"],
             "mdx_configs": config["mdx_configs"],
             "mkdocstrings": self.config,

Do all themes accept this locale option? It will not always be specified, so it should use config["theme"].get("locale", default_locale)) instead.

Do all themes accept this locale option? It will not always be specified, so it should maybe use config["theme"].get("locale", default_locale) instead.

I checked mkdocs' code, it's always provided:
https://github.com/mkdocs/mkdocs/blob/afb66c1bea3eb07a917803a25d5e536edd2b8084/mkdocs/theme.py#L34

Code
class Theme:
    """
    A Theme object.

    Keywords:

        name: The name of the theme as defined by its entrypoint.

        custom_dir: User defined directory for custom templates.

        static_templates: A list of templates to render as static pages.

    All other keywords are passed as-is and made available as a key/value mapping.

    """

    def __init__(self, name: str | None = None, **user_config) -> None:
        self.name = name
        self._vars = {'name': name, 'locale': 'en'}

        # MkDocs provided static templates are always included
        package_dir = os.path.abspath(os.path.dirname(__file__))
        mkdocs_templates = os.path.join(package_dir, 'templates')
        self.static_templates = set(os.listdir(mkdocs_templates))

        # Build self.dirs from various sources in order of precedence
        self.dirs = []

        if 'custom_dir' in user_config:
            self.dirs.append(user_config.pop('custom_dir'))

        if name:
            self._load_theme_config(name)

        # Include templates provided directly by MkDocs (outside any theme)
        self.dirs.append(mkdocs_templates)

        # Handle remaining user configs. Override theme configs (if set)
        self.static_templates.update(user_config.pop('static_templates', []))
        self._vars.update(user_config)

        # Validate locale and convert to Locale object
        self._vars['locale'] = localization.parse_locale(self._vars['locale'])

Yep, whatever works in all cases :slightly_smiling_face:

Sorry for the late update, however I thought I underestimated the pitfalls in i18n implementations across MkDocs :(
So, according to MkDocs Material - Changing the Language, they use a different approach to determine which language the site uses (using dashes (-) and the theme.language key rather than somewhat standard theme.locale)
I tried to use mkdocs.localization.parse_locale to unify the language codes, but it turned out to have some pitfalls.

Original Language Code
Result of Babel
MkDocs Polyfill

ku-IQ
error
ku_IQ

sh
error
sh

pt-BR
pt_BR
pt_BR

tl
fil_PH
tl

zh-Hant
zh_Hant
zh_Hant

zh-TW
zh_Hant_TW
zh_TW

zh
zh
zh

So I guess we should just copy mkdocs-material's approach and stuck with theme.language, forgetting theme.locale.

Is it possible to support multiple languages?
I used to use MkDocs-i18n to generate files for each language. But it won't work if import other site like
  - mkdocstrings:
      handlers:
        python:
          import:
            - https://docs.python.org/3/objects.inv

Is it possible to support multiple languages? I used to use MkDocs-i18n to generate files for each language.

IMO docstrings basically only come in one language, which is what mkdocstrings display. Maybe your request belongs to another issue to allow importing the same namespace with different aliases: e.g. distinguish between English and Chinese version of Python docs.

Is it possible to support multiple languages? I used to use MkDocs-i18n to generate files for each language.

IMO docstrings basically only come in one language, which is what mkdocstrings display. Maybe your request belongs to another issue to allow importing the same namespace with different aliases: e.g. distinguish between English and Chinese version of Python docs.

Yes, but there are other non-mkdocstrings-generated pages, like index page and some tutorial pages.


How To DEBUG in lua script

please tell me how to debug in lua script,thank you
my ide is IDEA

and also i want to know how to use DebugLib,
it's not work when i use "debug.traceback()"
is only print the following:
stack traceback:
[Java]: in ?
and i debug in project, see that calls is 0


如何查看已ac过的代码？

It's really recommended to create an issue by a template.
如何查看已ac过的代码？

So far it's not supported. Tracking issue: https://github.com/jdneo/vscode-leetcode/issues/69


Install fails silently on Raspberry Pi 4

When running $ goenv install 1.15.6 on an RPi4 (arm64) the program fails silently without installing anything.  Any clues? Thank you...

FYI running $ make on ~/.goenv yields the the following:
 ✓ prints go-build version when '--version' argument is given
 ✗ {before,after}_install hooks get triggered when '--force' argument and version argument is not already installed version and gets installed
   (from function `assert_equal' in file test/./test_assert_helpers.bash, line 33,
    from function `assert_output' in file test/./test_assert_helpers.bash, line 60,
    in test file test/goenv-install.bats, line 728)
     `assert_output <<-OUT' failed
   expected: (newline not part of expected output)
   before: TEST_DIR/root/versions/1.2.2
   Downloading 1.2.2.tar.gz...
   -> http://localhost:8090/1.2.2/1.2.2.tar.gz
   Installing Go Linux 64bit 1.2.2...
   Installed Go Linux 64bit 1.2.2 to TEST_DIR/root/versions/1.2.2

   after: 0
   REHASHED
   actual: (newline not actual output)
   before: TEST_DIR/root/versions/1.2.2
   after: 0
   REHASHED
 ✗ {before,after}_install hooks get triggered when '-f' argument and version argument is not already installed version and gets installed
   (from function `assert_equal' in file test/./test_assert_helpers.bash, line 33,
    from function `assert_output' in file test/./test_assert_helpers.bash, line 60,
    in test file test/goenv-install.bats, line 783)
     `assert_output <<-OUT' failed
   expected: (newline not part of expected output)
   before: TEST_DIR/root/versions/1.2.2
   Downloading 1.2.2.tar.gz...
   -> http://localhost:8090/1.2.2/1.2.2.tar.gz
   Installing Go Linux 64bit 1.2.2...
   Installed Go Linux 64bit 1.2.2 to TEST_DIR/root/versions/1.2.2

   after: 0
   REHASHED
   actual: (newline not actual output)
   before: TEST_DIR/root/versions/1.2.2
   after: 0
   REHASHED
 ✗ rehashes shims when '-f' argument and version argument is not already installed version and gets installed
   (from function `assert_equal' in file test/./test_assert_helpers.bash, line 33,
    from function `assert_output' in file test/./test_assert_helpers.bash, line 60,
    in test file test/goenv-install.bats, line 825)
     `assert_output <<-OUT' failed
   expected: (newline not part of expected output)
   Downloading 1.2.2.tar.gz...
   -> http://localhost:8090/1.2.2/1.2.2.tar.gz
   Installing Go Linux 64bit 1.2.2...
   Installed Go Linux 64bit 1.2.2 to TEST_DIR/root/versions/1.2.2
   actual: (newline not actual output)

 ✗ adds patch version '0' to definition when version argument is not already installed version and gets installed
   (from function `assert_equal' in file test/./test_assert_helpers.bash, line 33,
    from function `assert_output' in file test/./test_assert_helpers.bash, line 60,
    in test file test/goenv-install.bats, line 894)
     `assert_output <<-OUT' failed
   expected: (newline not part of expected output)
   Adding patch version 0 to 1.2
   Downloading 1.2.0.tar.gz...
   -> http://localhost:8090/1.2.0/1.2.0.tar.gz
   Installing Go Linux 64bit 1.2.0...
   Installed Go Linux 64bit 1.2.0 to TEST_DIR/root/versions/1.2.0
   actual: (newline not actual output)
   Adding patch version 0 to 1.2
 ✓ has usage instructions

Thnxs!

Found a temporary solution:
$ export GOPKG=go1.15.6.linux-arm64.tar.gz
$ wget https://golang.org/dl/$GOPKG
$ tar -C ~/.goenv/versions/1.15.6 -xvf $GOPKG
$ goenv global 1.15.6 && goenv rehash
$ rm $GOPKG

Same issue here; tried reinstalling, using Brew (vs cloning manually), checked and played around with my ~/.zshrc a lot, too. It's quite the pickle.
Thanks for the temporary fix @fungl164.

Same issue here; tried reinstalling, using Brew (vs cloning manually), checked and played around with my ~/.zshrc a lot, too. It's quite the pickle.
Thanks for the temporary fix @fungl164.

The same issue is happening with me in Macbook Air M1.

would it be useful to allow "build from source" for older versions?

dupe of #106


Add append builder for Bytes object

Description:

Related issue(s):
Fixes # https://github.com/hashgraph/pbj/issues/34
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Not sure the approach is quite right here. To start with can we add a two methods to Bytes:
public Bytes append(Bytes data) { ...}
public Bytes append(RandomAccessData data) { ...}

They return a new Bytes object that contains the bytes of this bytes object followed by all the bytes of the supplied object. The one that takes a Bytes object can have an efficient implementation that does zero copies of data by having an implementation of Bytes with two inner Bytes objects and direct referencing their data. Because Bytes is immutable it will work.

I see... I think we can keep the Builder class for now. It is doing copy and it has bunch of convenient methods and it is tested. I'm implementing the Bytes way with no copying. One thing is that you can append multiple Bytes objects to a Bytes objects. This is what I intend to support. Having a List of Bytes in the Bytes and modifying all the methods to deal with it. Not sure how this will make the reading of primitives (VarInt, etc, especially with unsafe buffers). I suspect that delegating to the appended Bytes might introduce some inefficiencies. But lets measure things.


Delete profile id during file share snapshot creation.

What this PR does / why we need it:
Delete profile id option during file share snapshot creation.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
#905

Please resolve the ci problem.


add podspec

podspec for this package, now that is was moved to react-native-community. This closes several pending issues.
this can be added to podfile like this:
  pod "RNGoogleSignin", :path => '../node_modules/react-native-google-signin'

  pod 'Yoga', :path => '../node_modules/react-native/ReactCommon/yoga/Yoga.podspec'
  pod 'React', path: '../node_modules/react-native', :subspecs => [
    'Core',
    'RCTActionSheet',
    'RCTAnimation',
    'RCTGeolocation',
    'RCTImage',
    'RCTLinkingIOS',
    'RCTNetwork',
    'RCTSettings',
    'RCTText',
    'RCTVibration',
    'RCTWebSocket',
  ]

closes https://github.com/react-native-community/react-native-google-signin/issues/53
similar prs:
https://github.com/react-native-community/react-native-google-signin/pull/331
https://github.com/react-native-community/react-native-google-signin/pull/284
https://github.com/react-native-community/react-native-google-signin/pull/255
https://github.com/react-native-community/react-native-google-signin/pull/183

Tested having this in my Podfile:
pod "RNGoogleSignin", :path => '../node_modules/react-native-google-signin'

pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga/yoga.podspec'
pod 'React', path: '../node_modules/react-native', :subspecs => [
  'Core',
  'CxxBridge',
  'DevSupport',
  'RCTBlob',
  'RCTActionSheet',
  'RCTAnimation',
  'RCTGeolocation',
  'RCTImage',
  'RCTLinkingIOS',
  'RCTNetwork',
  'RCTSettings',
  'RCTText',
  'RCTVibration',
  'RCTWebSocket',
]


Offer a dry run mode

@mkaszub I would put the dry run option into the configuration file. What do you think?

@mkaszub Any oppinions?

Chaostoolkit offeres dry run switch. Adding yet another switch could be not the best option.
Maybe chaostoolkit should check if driver offers dry run mode and if yes execute it and if not just behave as is.
Pobierz aplikację Outlook dla systemu Androidhttps://aka.ms/ghei36

From: Bugra Derre<EMAIL_ADDRESS>Sent: Tuesday, May 26, 2020 3:58:26 PM
To: proofdock/chaos-azure<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [proofdock/chaos-azure] Offer a dry run mode (#16)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/proofdock/chaos-azure/issues/16, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADHLC4CQO5G3OGGSHXUHAEDRTPDIFANCNFSM4NKKT6VA.

True. Completely forgot that switch


Looks like it's running on my cpu only

I'm getting great results, but it does not seem to be using my GPU at all.  I get the following error.  Any ideas how to fix this?   Thanks!
"C:\Users\importon\anaconda3\envs\mpi\lib\site-packages\onnxruntime\capi\onnxruntime_inference_collection.py:54: UserWarning: Specified provider 'CUDAExecutionProvider' is not in available provider names.Available providers: 'CPUExecutionProvider'
warnings.warn("

That is probably an issue with your setup.

What is your GPU? (It will only work if your GPU is from NVIDIA)
Make sure you have onnxruntime-gpu instead of onnxruntime
Make sure you have CUDA installed properly

Thanks for your help!
I have a Nvidia 1080ti
I tried uninstalling onyx runtime in order to force the onnxruntime-gpu to run, and I get the error below now.  It's weird because I can run other ML example code projects that require CUDA without issue.  It just seems to not be able to find the right path with onyx?
"File "C:\Users\importon\anaconda3\envs\mpi\lib\site-packages\onnxruntime\capi\onnxruntime_inference_collection.py", line 395, in _create_inference_session
sess.initialize_session(providers, provider_options, disabled_optimizers)
RuntimeError: D:\a_work\1\s\onnxruntime\python\onnxruntime_pybind_state.cc:562 onnxruntime::python::CreateExecutionProviderInstance CUDA_PATH is set but CUDA wasn't able to be loaded. Please install the correct version of CUDA and cuDNN as mentioned in the GPU requirements page (https://onnxruntime.ai/docs/reference/execution-providers/CUDA-ExecutionProvider.html#requirements), make sure they're in the PATH, and that your GPU is supported."


US lozalization issue on 1.18.2 (mod version 0.7.22)

Describe
Everything is missing their names and displays translation key instead of localized name in English (US)
I think the issue may be caused by uppercase spelling of US in name of en_US.json file (previous versions had it spelled lowercase).
Other languages including English (UK) work fine.
Steps to reproduce
Set the English (US) language
Multiplayer?
No
Version
1.18.2-0.7.21r (Latest 1.18)
Minecraft, Forge and maybe other related mods versions
Forge 40.2.0 Minecraft 1.18.2
Screenshots or Videos
No response
Crashlog/log
No response

Fixed in 0.7.23r


Create common compat library

Avoid files being compiled twice and reduce complexity of cmake build. However we still need to avoid different build flags being used inside those files (NO_ERR) in particular

I renamed the targets to OvergrowthLogging and OvergrowthCompat


Missing BufferedChecksum

Hi @NightOwl888 , just noticed the latest preview version marked the BufferedChecksum class internal with this commit https://github.com/apache/lucenenet/commit/6e8897762faf2ab8b9ef4bc485f47db314f12c4f
As we were using it in our code, just to understand, is this functionality something we should re-implement on our side, or will it eventually be exposed again by Lucene.Net?

The issue here is described in #255. The issue is that IChecksum was ported over from Java when .NET already has an abstraction for this purpose, namely, HashAlgorithm.
An attempt was made to make the conversion using Crc32.NET, an implementation of HashAlgorithm that implements CRC32. Some of the tests pass, but the CheckIndex functionality is no longer functional with this draft implementation.
Since this wasn't considered to be a primary interface and we didn't expect any users to utilize it, it has been made internal until a HashAlgorithm-derived implementation of CRC32 can be properly implemented and tested. Issue #255 is up for grabs if you would like to proceed with it to make a public implementation again.

Closing as duplicate of #255 (which was added to JIRA prior to this issue).


Update type-fest to ^4.10.2 to ensure compatibility with TypeScript 5.4

See the release notes: https://github.com/sindresorhus/type-fest/releases/tag/v4.10.2
And https://github.com/sindresorhus/type-fest/pull/807 that's mentioned within them
/ Sincerely co-maintainer of type-fest and user of umzug

Merged. Will aim to publish today.


Uncaught Intervention\Image\Exception\NotSupportedException: Driver (GD) could not be instantiated

GD Library and mbstring are already installed on our VPS Cpanel server but for some reason, I keep getting the following error.
PHP Fatal error:  Uncaught Intervention\Image\Exception\NotSupportedException: Driver (GD) could not be instantiated. in /intervention/image/src/Intervention/Image/ImageManager.php:113
GD Support: enabled
GD Version: bundled (2.1.0 compatible)
FreeType Support: enabled
FreeType Linkage: with freetype
FreeType Version: 2.4.11
GIF Read Support: enabled
GIF Create Support: enabled
JPEG Support: enabled
libJPEG Version: 6b
PNG Support: enabled
libPNG Version: 1.5.13
WBMP Support: enabled
XPM Support: enabled
libXpm Version: 30411
XBM Support: enabled
WebP Support: enabled

Got the same error. Extension is enabled

same error for me on Ubuntu 20.04

I suggest to try this with Intervention Image Version 3.


asm standalone billing tests

Motivation
New feature ASM Standalone billing tests
RFC: https://docs.google.com/document/d/12NBx-nD-IoQEMiCRnJXneq4Be7cbtSc6pJLOFUWTpNE/edit
Changes

A new scenario
A new feature
Some basic tests (we'd need a multi-service setup to test everything properly)

Workflow

⚠ Create your PR as draft ⚠
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
Framework is modified, or non obvious usage of it -> get a review from R&P team

:rocket: Once your PR is reviewed, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist

[ ] Relevant label (run-parametric-scenario, run-profiling-scenario...) are presents
[ ] If PR title starts with [<language>], double-check that only <language> is impacted by the change
[ ] No system-tests internal is modified. Otherwise, I have the approval from R&P team
[ ] CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
[ ] A docker base image is modified?

[ ] the relevant build-XXX-image label is present

[ ] A scenario is added (or removed)?

[ ] Get a review from R&P team

and rebasing the branch to fix failures (sorry)


[BUG] [VSCode Extension] Cannot trigger batch run with vscode extension side bar in some cases.

Describe the bug
Cannot trigger batch run with vscode extension side bar in some cases.
How To Reproduce the bug

Open a prompt flow project folder.
Close All opened windows

In Flows section in side bar, select any one of the flow, click 'Batch run', nothing will happen.

Environment Information

Windows 11
vscode extension 1.6.0

Fixed with extension version 1.7.0


[BUG] Sigma Null Filters Not Translated To Query Properly

What is the bug?
Null filters in Sigma rules are not translated properly to queries leading to False Positives and broken detections.
Example:
Pre-packaged rule Wmiprvse Spawning Process contains a null filter

By sigma syntax this should only hit on documents where the LogonId field exists (As in NOT null)
The query is translated to this by OpenSearch:
((winlog.event_data.ParentImage: *\\WmiPrvSe.exe) AND ((NOT (((winlog.event_data.LogonId: "0x3e7") OR (winlog.event_data.LogonId: "null")) OR ((winlog.user.name: *AUTHORI*) OR (winlog.user.name: *AUTORI*)) OR ((winlog.event_data.Image: *\\WmiPrvSE.exe) OR (winlog.event_data.Image: *\\WerFault.exe)))))) AND ((NOT winlog.event_data.LogonId: null))
This is not working as intended. The NOT winlog.event_data.LogonId: null section is actually looking for null as a string.  This query will return all documents that dont have winlog.event_data.LogonId equal to the string "null"
How can one reproduce the bug?
Steps to reproduce the behavior:

Create any Sigma rule that uses a null filter (or use the prepackaged rule noted above)
View its query and note the null filter is translated to NOT : null
Go to discover
Query for NOT <field>:null or simply: NOT winlog.event_data.LogonId:null
All documents where the specified field is not the string "null" are returned (Nearly all data)

What is the expected behavior?
The sigma to be properly translated to something along the lines of:
winlog.event_data.LogonId:* where this returns results where the field being queried exists in the data
What is your host/environment?

OS: 2.11 fresh install

Thanks,
Jay

Resolved by #722


broken links on build

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
When checking yarn start locally, everything works, I checked the links.
yarn build throws errors
Provided that docusaurus.config.js has onBrokenLinks: 'throw'
If you remove this value, then everything is fine, but the condition that this value would be.
Reproducible demo
https://github.com/kubevela/kubevela.io/pull/771
Steps to reproduce
update https://github.com/kubevela/kubevela.io/pull/771/files
https://github.com/kubevela/kubevela.io/runs/7039961689?check_suite_focus=true
Expected behavior
There should be no errors if the links are not broken
Actual behavior
https://github.com/kubevela/kubevela.io/runs/7039961689?check_suite_focus=true
Your environment

Public source code: https://github.com/kubevela/kubevela.io
Public site URL:https://kubevela.io/
Docusaurus version used: 2.0.0-alpha.75
Environment name and version (e.g. Chrome 89, Node.js 16.4): 102 16+ node
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Ubuntu

Hi! It's because in the latest version, we will not output slugs with duplicate last segment by default. See https://github.com/facebook/docusaurus/pull/5830. You can fix this by adding explicit slugs to those docs.


Tuto-secific branch (breaks functionality: NOT for master branch)

This PR is NOT for the master branch.
Indeed, it brings several internal checks to be done when the tools are executed, that are intended to assess whether they are correctly executed in the context of the tutorial demonstrations. This is to help prevent some unintended uses of the tools already observed by users when testing the tutorial commands on some setups.
The idea is, if possible, to create a new branch (typically named tuto') of off this pull request, and to use a dedicated git clone command as part for the tutorial document and slides. If this is not possible, please create this tuto' branch out of `master', and then I'll PR on the new branch afterwards.
Thanks!

Hi @xiaoweih,
Please note this PR should not be applied on master, and is intended for the creation of a new branch on this repository.
I'm afraid we urgently need to revert its changes.
(Sorry I don't have the right to create new branches, hence the attempt via a PR on master.)
Best,
Nicolas

And I created a “tutorial” branch. --- xiaowei
From: nberth @.>
Reply to: TrustAI/DeepConcolic @.>
Date: Monday, 15 March 2021 at 19:56
To: TrustAI/DeepConcolic @.>
Cc: Xiaowei Huang @.>, Mention @.***>
Subject: Re: [TrustAI/DeepConcolic] Tuto-secific branch (breaks functionality: NOT for master branch) (#62)
Hi @xiaoweihhttps://github.com/xiaoweih,
Please note this PR should not be applied on master, and is intended for the creation of a new branch on this repository.
I'm afraid we urgently need to revert its changes.
(Sorry I don't have the right to create new branches, hence the attempt via a PR on master.)
Best,
Nicolas
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/TrustAI/DeepConcolic/pull/62#issuecomment-799709282, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEEJMW244DSAWZ66JD2OXCLTDZQ45ANCNFSM4ZGY4CGQ.


Create/Modify overlay implementation

Reference: https://www.notion.so/Carnot-Simulation-Mechanism-c025dbab6b374c139004aae45831cf78

Solved.


CUDA tests: There is no RNG seeding in test_atomics.py

See: https://github.com/numba/numba/pull/6368#discussion_r505447275
The values tested will be random for each invocation of the tests, because there is no RNG seeding. The RNG should be seeded for each test, so that values are stable.

Closing as resolved in #6376.


event_source() not compatible with prototype readers?

Hi,
I see that that in the master all "Factories" disappeared. I admit I do not see the immediate improvement, but this is surely my limit.
Anyway, I understand that for reading events I must now use "event_source()" like
from ctapipe.io import event_source
source = event_source("/ctadata/franca/LST/LST-1.7.Run00000.0529.fits.fz", max_events=None)

but it seems to recognise only MC data:
ValueError: Cannot find compatible EventSource for
	url:/ctadata/franca/LST/LST-1.7.Run00000.0529.fits.fz
in available EventSources:
	['SimTelEventSource']

is this correct?

I think this has more with the creation of the plugin architecture than with the removal of factories.
The other eventsource are not imported by default.
Could you try adding this line to your file:
from ctapipe.io.lsteventsource import LSTEventSource

I will commit a fix for the moment, until the eventsource is in a plugin

See here: https://github.com/cta-observatory/ctapipe/pull/991

For more info:
The factories have changed - you now can use EventSource.from_url(filename) or you can use the event_source() helper function, if you don't need the Tool/config functionality.  I think now you have to install the non-MC event sources separately... I haven't tried that yet, but perhaps Dominik could help? He implemented that.  For now they must be installed with pip, since I haven't made conda packages
Basically there is still "Factory" functionality, but it's built-in to the base class, like other Python classes (similar to how astropy works as well), but the second change is that we don't bundle all the readers with ctapipe, since it was getting too hard to maintain and test
Because of this big API change, the next revision of ctapipe will be 0.7 (0.6.x still uses the old way)
I'm working now on releaseing 0.6.2 (it's turning out to be a bit complicated), but should be there soon

Thanks Max, adding the line it works
I related it to the Factories because before I was using the EventSourceFactory that I can not more do now.

See here: #991
Wonderful!

I am ready to put the reader in a plugin, but how does it works?
Dominik, could you please indicate me an example?
Thanks

Because of this big API change, the next revision of ctapipe will be 0.7 (0.6.x still uses the old way)
I'm working now on releaseing 0.6.2 (it's turning out to be a bit complicated), but should be there soon

Ok Karl, I see
Thanks

I can do this for all the event sources trying to keep the git history.

Basically we only need a python module that is called ctapipe_io_xxxx


Make scrolling other elements trigger lazy-loading

This PR fixes a problem I currently have. Simply, I have a div on my page which is overflow: auto.  The issue is that Layzr's handlers method only operates on window. This means that only scrolling the window itself will trigger lazy-loading, and scrolling any other element won't. I propose the addition of handlersFor which will add the scroll handler for the given node.
Note: I looked into detecting resizing of a div (though, it's not a problem I have). It seems that this is a popular solution, and very efficient. However, it would introduce a dependency for an edge case which is probably rare. Having said that, maybe we should expose requestFrame (perhaps under a different name) as a hook for adding other triggers?

@zaccharles I like the idea. I think for a cleaner implementation though, it might make sense to extend the current handler method. If it accepted an additional parameter, that was a selector or element node (which defaulted to the window object), it would keep the code DRY, and accomplish the same thing.
I'll look into this in the near future, when I get some time to potentially cut a release. I also want to do some testing, to make sure the existing in viewport calculation will work for elements that are inside scrolling containers, rather than a scrolling window.

I think that sounds like a better solution.
As for the in viewport calculation, I can tell you that it worked on my app, so at least there's some promise :) I also exposed requestFrame in my fork and found it quite useful to have access the that.
Anyway, I'll continue using my fork for now, happy to help if I can, though I think you're all over it :)

cheers man :beers: hopefully I'll get a chance to take a look this weekend - if not definitely next week. glad to hear that this is working in your fork, hopefully I wont have to rework anything.

Hello @callmecavs and @zaccharles
As I can see this branch has conflicts.
@zaccharles are you planning to resolve conflicts?
Or in another way I can create new pull request for the same feature with my code and tests. What do you think about it?

Happy for you to create a new PR @ilyaztsv :)

@zaccharles I create PR regarding to optional container with scroll.


Bug with Field Level Authorisation on Amplify API

Describe the bug
Amplify does not produce correct behaviour on field level authorisation, after finding help on discord, I found out that the behaviour of amplify add api is not deterministic and is affected by the order of adding congito user pool and API Key.
Amplify CLI Version
4.41.1
To Reproduce

amplify add api -> choosecognito user pool as default auth type -> choose API key as additional auth type.
In graphql.schema, add the following SDL

type Todo
  @model
  @auth(
    rules: [
      { allow: public, operations: [read] }
      { allow: groups, groups: ["admin"] }
    ]
  ) {
  id: ID!
  name: String!
  description: String
  secret: String @auth(rules: [{ allow: groups, groups: ["admin"] }])
}

Run amplify api gql-compile, and inspect the graphql.schema in build folder

type Todo @aws_api_key @aws_cognito_user_pools {
  id: ID!
  name: String!
  description: String
  secret: String
  createdAt: AWSDateTime!
  updatedAt: AWSDateTime!
}

Expected behavior
I expect the following SDL in type Todo, which I obtained correctly if I switch of order of default auth type to API key
type Todo @aws_cognito_user_pools @aws_api_key {
  id: ID!
  name: String!
  description: String
  createdAt: AWSDateTime!
  updatedAt: AWSDateTime!
  secret: String @aws_cognito_user_pools
}

OS: Mac
Node Version: 12.18.3

Hello @chrisyeung1121 the behavior you are looking for here is deny-by-default this is something we are tracking as a part of the @auth Enhancement RFC here: https://github.com/aws-amplify/amplify-cli/issues/1043
We are looking at adding these enhancements in the next version of the transformer here: https://github.com/aws-amplify/amplify-cli/issues/6217
Closing this issue in favor the of the @auth and GQL Transformer vNext RFC.


gulp.watch stops watching files

I am having a issue where gulp.watch successfully detects file changes, but only for a while. After a few file changes and saves to my index.html, it stops detecting file changes. There are no errors...it just silently stops detecting the file saves/changes.
from the gulpfile.js of fountain-webapp:

function watch(done) {
  gulp.watch([
    conf.path.src('index.html'),
    'bower.json'
  ], gulp.parallel('inject'));

one@development ~/github/drop $ gulp -v
[15:11:54] CLI version 1.2.2
[15:11:54] Local version 4.0.0-alpha.2

one@development ~/github/drop $ npm -g list generator-fountain-webapp
/home/one/.nvm/versions/node/v4.2.2/lib
└──<EMAIL_ADDRESS>
one@development ~/github $ node --version
v4.2.2
one@development ~/github $ npm --version
2.14.7

Your task most likely isn't signaling async completion. Support questions should be directed to StackOverflow.

Here is a bare bones version, I don't see a async issue. Please let me know if I am missing. gulp.watch will detect a change to index.html one time, after that it won't detect any changes:
gulp.task('serve', gulp.series('watch'));

function reloadBrowserSync(cb) {
  console.log('sssssssssssssssss');
  cb();
}

function watch(done) {
  gulp.watch(['/home/one/github/one-drop/src/index.html',
             '/home/one/github/one-drop/src/app/**/*.html'], reloadBrowserSync);
  done();
}

Here is what it looks like when it will detect the first change.... after that is silently detects no future file changes to index.html:
[18:07:19] Finished 'serve' after 17 ms
[18:07:31] Starting 'reloadBrowserSync'...
sssssssssssssssss
[18:07:31] Finished 'reloadBrowserSync' after 676 Î¼s


Fix mat4

Bring the SDK up to spec by replacing 4x3 matrices for instance transforms by 4x4 ones

Superseded by #52


Decompose substitute_node only when gate width matches definition.

Fixes #3440
When #3233 was implemented, a check was added to the unroller to ensure that, before using DAGCircuit.substitute_node,  the definition width matched that of the instruction being replaced, but this fix was not included in the Decompose pass. This PR add that check.
Summary
Details and comments

No changelog needed since #3233 hasn't been released yet.


fix: 403s on action-gh-release creating release

Per https://github.com/softprops/action-gh-release/issues/236 we add a permission to enable the action-gh-release to create a release object for the repo.

might fix https://github.com/jqlang/bazel_rules_jq/actions/runs/6738206173/job/18317311589 error:


Switching directions

This should be also specified in more detail

I don't think that this is super important for the prototype implementation. -> low prio


Bug - : the desired outcome image and actual solution is very different  you  need to review it. Thanks.

Complete the following REQUIRED checkboxes:

[x] I have thoroughly read and understand The Odin Project Contributing Guide
[x] The title of this issue follows the Bug - location of bug: brief description of bug format, e.g. Bug - Grid exercises: CSS not properly linked to HTML files

The following checkbox is OPTIONAL:

[x] I would like to be assigned this issue to work on it

1. Description of the Bug:

2. How To Reproduce:

3. Expected Behavior:

4. Desktop/Device:

Device:
OS:
Browser:
Version:

5. Additional Information:

Hey there, could you be more clear about which exercise has this issue? Thanks

This is probably relating to issue #259

Closing as it is a duplicate of the above linked issue


Can't compile osmini

When trying to build omini Make don't find 'out' folder
You should add mkdir at the start of build.

I've uploaded a new version (0.0.2) ! Normally the bug is fixed. If don't work, please try to create these folders: out/ and out/io/

So good !


How many FPS?

Hello! How many FPS/Hz can one achieve with this adapter?

The HDMI side of the adapter runs at 60Hz.
The Boson outputs either 30Hz/60Hz, and this is selectable at runtime on the device.

Thank you very much!


Support unordered column compare

Chunked changes from #122 :
Support ignoring column ordering when comparing dataframe and dataset
Minor refactoring

Please help with the review @SemyonSinchenko , @alfonsorr