Problem when installing yolox

I see this AssertionError when installing yolox when calling the pip install -v -e . step.
I previously used python3.9, where I had the same issue. I hoped that downgrading to Python3.8 would solve it, but it didn't. I downgraded from setuptools69.1.1 to setuptools-62.6.0.
What else could I try to make it work?
`
(.venv) (base) ubuntu@ip-10-150-129-58:~/yolox_keypoint_segment$ python -m pip install -v -e .
Using pip 24.0 from /home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/pip (python 3.8)
Obtaining file:///home/ubuntu/yolox_keypoint_segment
Running command python setup.py egg_info
running egg_info
creating /tmp/pip-pip-egg-info-rvow2iur/yolox.egg-info
writing /tmp/pip-pip-egg-info-rvow2iur/yolox.egg-info/PKG-INFO
writing dependency_links to /tmp/pip-pip-egg-info-rvow2iur/yolox.egg-info/dependency_links.txt
writing requirements to /tmp/pip-pip-egg-info-rvow2iur/yolox.egg-info/requires.txt
writing top-level names to /tmp/pip-pip-egg-info-rvow2iur/yolox.egg-info/top_level.txt
writing manifest file '/tmp/pip-pip-egg-info-rvow2iur/yolox.egg-info/SOURCES.txt'
package init file 'exps/default/init.py' not found (or not a regular file)
reading manifest file '/tmp/pip-pip-egg-info-rvow2iur/yolox.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file '/tmp/pip-pip-egg-info-rvow2iur/yolox.egg-info/SOURCES.txt'
Preparing metadata (setup.py) ... done
Requirement already satisfied: numpy in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (1.24.4)
Requirement already satisfied: torch>=1.7 in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (2.2.1)
Requirement already satisfied: opencv_python in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (<IP_ADDRESS>)
Requirement already satisfied: loguru in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (0.7.2)
Requirement already satisfied: scikit-image in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (0.21.0)
Requirement already satisfied: tqdm in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (4.66.2)
Requirement already satisfied: torchvision in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (0.17.1)
Requirement already satisfied: Pillow in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (10.2.0)
Requirement already satisfied: thop in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (0.1.1.post2209072238)
Requirement already satisfied: ninja in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (<IP_ADDRESS>)
Requirement already satisfied: tabulate in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (0.9.0)
Requirement already satisfied: tensorboard in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (2.14.0)
Requirement already satisfied: pycocotools>=2.0.2 in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (2.0.7)
Requirement already satisfied: onnx==1.8.1 in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (1.8.1)
Requirement already satisfied: onnxruntime==1.8.0 in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (1.8.0)
Requirement already satisfied: onnx-simplifier==0.3.5 in ./.venv/lib/python3.8/site-packages (from yolox==0.3.0) (0.3.5)
Requirement already satisfied: protobuf in ./.venv/lib/python3.8/site-packages (from onnx==1.8.1->yolox==0.3.0) (4.25.3)
Requirement already satisfied: six in ./.venv/lib/python3.8/site-packages (from onnx==1.8.1->yolox==0.3.0) (1.16.0)
Requirement already satisfied: typing-extensions>=<IP_ADDRESS> in ./.venv/lib/python3.8/site-packages (from onnx==1.8.1->yolox==0.3.0) (4.10.0)
Requirement already satisfied: onnxoptimizer>=0.2.5 in ./.venv/lib/python3.8/site-packages (from onnx-simplifier==0.3.5->yolox==0.3.0) (0.3.13)
Requirement already satisfied: flatbuffers in ./.venv/lib/python3.8/site-packages (from onnxruntime==1.8.0->yolox==0.3.0) (23.5.26)
Requirement already satisfied: matplotlib>=2.1.0 in ./.venv/lib/python3.8/site-packages (from pycocotools>=2.0.2->yolox==0.3.0) (3.7.5)
Requirement already satisfied: filelock in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (3.13.1)
Requirement already satisfied: sympy in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (1.12)
Requirement already satisfied: networkx in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (3.1)
Requirement already satisfied: jinja2 in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (3.1.3)
Requirement already satisfied: fsspec in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (2024.2.0)
Requirement already satisfied: nvidia-cuda-nvrtc-cu12==12.1.105 in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (12.1.105)
Requirement already satisfied: nvidia-cuda-runtime-cu12==12.1.105 in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (12.1.105)
Requirement already satisfied: nvidia-cuda-cupti-cu12==12.1.105 in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (12.1.105)
Requirement already satisfied: nvidia-cudnn-cu12==<IP_ADDRESS> in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cublas-cu12==<IP_ADDRESS> in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cufft-cu12==<IP_ADDRESS> in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-curand-cu12==<IP_ADDRESS> in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusolver-cu12==<IP_ADDRESS> in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusparse-cu12==<IP_ADDRESS> in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-nccl-cu12==2.19.3 in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (2.19.3)
Requirement already satisfied: nvidia-nvtx-cu12==12.1.105 in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (12.1.105)
Requirement already satisfied: triton==2.2.0 in ./.venv/lib/python3.8/site-packages (from torch>=1.7->yolox==0.3.0) (2.2.0)
Requirement already satisfied: nvidia-nvjitlink-cu12 in ./.venv/lib/python3.8/site-packages (from nvidia-cusolver-cu12==<IP_ADDRESS>->torch>=1.7->yolox==0.3.0) (12.3.101)
Requirement already satisfied: scipy>=1.8 in ./.venv/lib/python3.8/site-packages (from scikit-image->yolox==0.3.0) (1.10.1)
Requirement already satisfied: imageio>=2.27 in ./.venv/lib/python3.8/site-packages (from scikit-image->yolox==0.3.0) (2.34.0)
Requirement already satisfied: tifffile>=2022.8.12 in ./.venv/lib/python3.8/site-packages (from scikit-image->yolox==0.3.0) (2023.7.10)
Requirement already satisfied: PyWavelets>=1.1.1 in ./.venv/lib/python3.8/site-packages (from scikit-image->yolox==0.3.0) (1.4.1)
Requirement already satisfied: packaging>=21 in ./.venv/lib/python3.8/site-packages (from scikit-image->yolox==0.3.0) (23.2)
Requirement already satisfied: lazy_loader>=0.2 in ./.venv/lib/python3.8/site-packages (from scikit-image->yolox==0.3.0) (0.3)
Requirement already satisfied: absl-py>=0.4 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (2.1.0)
Requirement already satisfied: grpcio>=1.48.2 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (1.62.0)
Requirement already satisfied: google-auth<3,>=1.6.3 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (2.28.1)
Requirement already satisfied: google-auth-oauthlib<1.1,>=0.5 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (1.0.0)
Requirement already satisfied: markdown>=2.6.8 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (3.5.2)
Requirement already satisfied: requests<3,>=2.21.0 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (2.31.0)
Requirement already satisfied: setuptools>=41.0.0 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (62.6.0)
Requirement already satisfied: tensorboard-data-server<0.8.0,>=0.7.0 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (0.7.2)
Requirement already satisfied: werkzeug>=1.0.1 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (3.0.1)
Requirement already satisfied: wheel>=0.26 in ./.venv/lib/python3.8/site-packages (from tensorboard->yolox==0.3.0) (0.42.0)
Requirement already satisfied: cachetools<6.0,>=2.0.0 in ./.venv/lib/python3.8/site-packages (from google-auth<3,>=1.6.3->tensorboard->yolox==0.3.0) (5.3.3)
Requirement already satisfied: pyasn1-modules>=0.2.1 in ./.venv/lib/python3.8/site-packages (from google-auth<3,>=1.6.3->tensorboard->yolox==0.3.0) (0.3.0)
Requirement already satisfied: rsa<5,>=3.1.4 in ./.venv/lib/python3.8/site-packages (from google-auth<3,>=1.6.3->tensorboard->yolox==0.3.0) (4.9)
Requirement already satisfied: requests-oauthlib>=0.7.0 in ./.venv/lib/python3.8/site-packages (from google-auth-oauthlib<1.1,>=0.5->tensorboard->yolox==0.3.0) (1.3.1)
Requirement already satisfied: importlib-metadata>=4.4 in ./.venv/lib/python3.8/site-packages (from markdown>=2.6.8->tensorboard->yolox==0.3.0) (7.0.1)
Requirement already satisfied: contourpy>=1.0.1 in ./.venv/lib/python3.8/site-packages (from matplotlib>=2.1.0->pycocotools>=2.0.2->yolox==0.3.0) (1.1.1)
Requirement already satisfied: cycler>=0.10 in ./.venv/lib/python3.8/site-packages (from matplotlib>=2.1.0->pycocotools>=2.0.2->yolox==0.3.0) (0.12.1)
Requirement already satisfied: fonttools>=4.22.0 in ./.venv/lib/python3.8/site-packages (from matplotlib>=2.1.0->pycocotools>=2.0.2->yolox==0.3.0) (4.49.0)
Requirement already satisfied: kiwisolver>=1.0.1 in ./.venv/lib/python3.8/site-packages (from matplotlib>=2.1.0->pycocotools>=2.0.2->yolox==0.3.0) (1.4.5)
Requirement already satisfied: pyparsing>=2.3.1 in ./.venv/lib/python3.8/site-packages (from matplotlib>=2.1.0->pycocotools>=2.0.2->yolox==0.3.0) (3.1.1)
Requirement already satisfied: python-dateutil>=2.7 in ./.venv/lib/python3.8/site-packages (from matplotlib>=2.1.0->pycocotools>=2.0.2->yolox==0.3.0) (2.9.0.post0)
Requirement already satisfied: importlib-resources>=3.2.0 in ./.venv/lib/python3.8/site-packages (from matplotlib>=2.1.0->pycocotools>=2.0.2->yolox==0.3.0) (6.1.2)
Requirement already satisfied: charset-normalizer<4,>=2 in ./.venv/lib/python3.8/site-packages (from requests<3,>=2.21.0->tensorboard->yolox==0.3.0) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in ./.venv/lib/python3.8/site-packages (from requests<3,>=2.21.0->tensorboard->yolox==0.3.0) (3.6)
Requirement already satisfied: urllib3<3,>=1.21.1 in ./.venv/lib/python3.8/site-packages (from requests<3,>=2.21.0->tensorboard->yolox==0.3.0) (2.2.1)
Requirement already satisfied: certifi>=2017.4.17 in ./.venv/lib/python3.8/site-packages (from requests<3,>=2.21.0->tensorboard->yolox==0.3.0) (2024.2.2)
Requirement already satisfied: MarkupSafe>=2.1.1 in ./.venv/lib/python3.8/site-packages (from werkzeug>=1.0.1->tensorboard->yolox==0.3.0) (2.1.5)
Requirement already satisfied: mpmath>=0.19 in ./.venv/lib/python3.8/site-packages (from sympy->torch>=1.7->yolox==0.3.0) (1.3.0)
Requirement already satisfied: zipp>=0.5 in ./.venv/lib/python3.8/site-packages (from importlib-metadata>=4.4->markdown>=2.6.8->tensorboard->yolox==0.3.0) (3.17.0)
Requirement already satisfied: pyasn1<0.6.0,>=0.4.6 in ./.venv/lib/python3.8/site-packages (from pyasn1-modules>=0.2.1->google-auth<3,>=1.6.3->tensorboard->yolox==0.3.0) (0.5.1)
Requirement already satisfied: oauthlib>=3.0.0 in ./.venv/lib/python3.8/site-packages (from requests-oauthlib>=0.7.0->google-auth-oauthlib<1.1,>=0.5->tensorboard->yolox==0.3.0) (3.2.2)
Installing collected packages: yolox
Running setup.py develop for yolox
Running command python setup.py develop
running develop
running egg_info
writing yolox.egg-info/PKG-INFO
writing dependency_links to yolox.egg-info/dependency_links.txt
writing requirements to yolox.egg-info/requires.txt
writing top-level names to yolox.egg-info/top_level.txt
/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
package init file 'exps/default/init.py' not found (or not a regular file)
reading manifest file 'yolox.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'yolox.egg-info/SOURCES.txt'
running build_ext
building 'yolox.layers.fast_cocoeval' extension
Emitting ninja build file /home/ubuntu/yolox_keypoint_segment/build/temp.linux-x86_64-cpython-38/build.ninja...
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "/home/ubuntu/yolox_keypoint_segment/setup.py", line 64, in
setuptools.setup(
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/init.py", line 87, in setup
return distutils.core.setup(**attrs)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 177, in setup
return run_commands(dist)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 193, in run_commands
dist.run_commands()
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 968, in run_commands
self.run_command(cmd)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/dist.py", line 1229, in run_command
super().run_command(command)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 987, in run_command
cmd_obj.run()
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/command/develop.py", line 34, in run
self.install_for_development()
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/command/develop.py", line 114, in install_for_development
self.run_command('build_ext')
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/cmd.py", line 317, in run_command
self.distribution.run_command(command)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/dist.py", line 1229, in run_command
super().run_command(command)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 987, in run_command
cmd_obj.run()
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 79, in run
_build_ext.run(self)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 871, in build_extensions
build_ext.build_extensions(self)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/command/build_ext.py", line 459, in build_extensions
self._build_extensions_serial()
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/command/build_ext.py", line 485, in _build_extensions_serial
self.build_extension(ext)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 202, in build_extension
_build_ext.build_extension(self, ext)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/Cython/Distutils/build_ext.py", line 135, in build_extension
super(build_ext, self).build_extension(ext)
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/setuptools/_distutils/command/build_ext.py", line 540, in build_extension
objects = self.compiler.compile(
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 684, in unix_wrap_ninja_compile
_write_ninja_file_and_compile_objects(
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 1760, in _write_ninja_file_and_compile_objects
_write_ninja_file(
File "/home/ubuntu/yolox_keypoint_segment/.venv/lib/python3.8/site-packages/torch/utils/cpp_extension.py", line 2292, in _write_ninja_file
assert len(sources) > 0
AssertionError
error: subprocess-exited-with-error
× python setup.py develop did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
full command: /home/ubuntu/yolox_keypoint_segment/.venv/bin/python -c '
exec(compile('"'"''"'"''"'"'
# This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
#
# - It imports setuptools before invoking setup.py, to enable projects that directly
#   import from `distutils.core` to work with newer packaging standards.
# - It provides a clear error message when setuptools is not installed.
# - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
#   setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
#     manifest_maker: standard file '"'"'-c'"'"' not found".
# - It generates a shim setup.py, for handling setup.cfg-only projects.
import os, sys, tokenize

try:
    import setuptools
except ImportError as error:
    print(
        "ERROR: Can not execute `setup.py` since setuptools is not available in "
        "the build environment.",
        file=sys.stderr,
    )
    sys.exit(1)

__file__ = %r
sys.argv[0] = __file__

if os.path.exists(__file__):
    filename = __file__
    with tokenize.open(__file__) as f:
        setup_py_code = f.read()
else:
    filename = "<auto-generated setuptools caller>"
    setup_py_code = "from setuptools import setup; setup()"

exec(compile(setup_py_code, filename, "exec"))
'"'"''"'"''"'"' % ('"'"'/home/ubuntu/yolox_keypoint_segment/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' develop --no-deps
cwd: /home/ubuntu/yolox_keypoint_segment/

error: subprocess-exited-with-error
× python setup.py develop did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
`

copy dir yolox/layers/cocoeval from https://github.com/Megvii-BaseDetection/YOLOX/tree/main/yolox/layers


fix fix broker load progress due to retry

Proposed changes
Currently, when retrying a broker load, it will use a different load_id with the same job_id.
The total_scan_nums in progress is accumulated by job_id.
This will cause the total_scan_nums progress to be multiple of the actual scan nums.


two-way conversion :  sac <--> asdf

Some of our tools work on sac files, others work on ASDF files, so I'd like to be able to convert forward and backward without any loss of metadata.
pyasdf/scripts/sac2asdf.py does not preserve stats.sac dictionaries, so I wrote a new version that does:  https://github.com/rmodrak/asdf_converters/blob/master/asdf_converters/sac2asdf.py
this new script constructs a dictionary {(original_sac_filename: trace.stats.sac) for trace in stream}, dumps it into a dill virtual file that is then saved as an ASDF auxiliary data file.
What remains is to devise a mapping between original_sac_filenames <--> ASDF waveforms.  I see no easy way of doing this using the existing ASDF API.  ASDFDataSet.get_waveforms comes close, but I think there ought to be a simpler way.
Am I missing something?  Any advice would be greatly appreciated.

I'm not necessarily too fond on such a tool but I can see how this would be hugely useful in practice especially when transitioning workflows to ASDF. So if its okay with you I might even replace the existing pyasdf/scripts/sac2asdf.py with your script and its inverse once it finalized.

this new script constructs a dictionary {(original_sac_filename: trace.stats.sac) for trace in stream}, dumps it into a dill virtual file that is then saved as an ASDF auxiliary data file.

Maybe consider dumping a JSON string to the auxiliary data? Then there at least is some chance to also read it with a non-Python tool.

What remains is to devise a mapping between original_sac_filenames <--> ASDF waveforms. I see no easy way of doing this using the existing ASDF API. ASDFDataSet.get_waveforms comes close, but I think there ought to be a simpler way.

You could use the waveform labels to store the filenames: http://seismicdata.github.io/pyasdf/of_tags_and_labels.html
Another option would be to store the HDF5 path for each waveform in the dumped dictionary.

I share your mixed feelings, but as you were saying, it may be a practical
necessity until more applications natively support ASDF.
Good suggestions, let me respond further after I've looked into them a bit
more.
On Thu, Nov 23, 2017 at 12:09 AM, Lion Krischer<EMAIL_ADDRESS>wrote:

I'm not necessarily too fond on such a tool but I can see how this would
be hugely useful in practice especially when transitioning workflows to
ASDF. So if its okay with you I might even replace the existing
pyasdf/scripts/sac2asdf.py with your script and its inverse once it
finalized.
this new script constructs a dictionary {(original_sac_filename:
trace.stats.sac) for trace in stream}, dumps it into a dill virtual file
that is then saved as an ASDF auxiliary data file.
Maybe consider dumping a JSON string to the auxiliary data? Then there at
least is some chance to also read it with a non-Python tool.
What remains is to devise a mapping between original_sac_filenames <-->
ASDF waveforms. I see no easy way of doing this using the existing ASDF
API. ASDFDataSet.get_waveforms comes close, but I think there ought to be a
simpler way.
You could use the waveform labels to store the filenames:
http://seismicdata.github.io/pyasdf/of_tags_and_labels.html
Another option would be to store the HDF5 path for each waveform in the
dumped dictionary.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SeismicData/pyasdf/issues/41#issuecomment-346563120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AERpSnpu0c6E2NTnJRaEtne77pEbx3Y9ks5s5TY5gaJpZM4QoUF4
.


Remove dependency on https://api.mapbox.com/mapbox-gl-js/plugins/mapbox-gl-rtl-text/v0.2.3/mapbox-gl-rtl-text.js

Update: Upstream Issue unter https://github.com/visgl/react-map-gl/issues/2310

Right now, we fetch data from the Mapbox domain which we do not want to do due to our privacy policy.
Goal
Remove this domain / remove the plugin / or have the data locally.
Next steps

Test if we can overwrite with local file. Or     mapboxgl.setRTLTextPlugin('https://cdn.maptiler.com/mapbox-gl-js/plugins/mapbox-gl-rtl-text/v0.1.2/mapbox-gl-rtl-text.js'); because we already connect to maptiler. (Source)
Create issue with ReactMapGL to inline the file. Or is this Maplibre?

Research

What it looks like ATM
Docs https://maplibre.org/maplibre-gl-js/docs/examples/mapbox-gl-rtl-text/
Docs https://maplibre.org/maplibre-gl-js/docs/API/classes/default/#setrtltextplugin
https://documentation.maptiler.com/hc/en-us/articles/4410638577297-How-to-use-MapLibre
Searching for mapbox-gl-rtl-text in our node_modules revealsmaplibre-gl/dist/maplibre-gl-dev.js:
  26951      else if (processStyledBidirectionalText) {
  26952:         // Need version of mapbox-gl-rtl-text with style support for combining RTL text
  26953          // with formatting

  34070  var devDependencies = {
  34071: 	"@mapbox/mapbox-gl-rtl-text": "^0.2.3",
  34072  	"@mapbox/mvt-fixtures": "^3.10.0",

  57238  /**
  57239:  * Sets the map's [RTL text plugin](https://www.mapbox.com/mapbox-gl-js/plugins/#mapbox-gl-rtl-text).
  57240   * Necessary for supporting the Arabic and Hebrew languages, which are written right-to-left.

  57247   * ```ts
  57248:  * maplibregl.setRTLTextPlugin('https://unpkg.com/@mapbox/mapbox-gl-rtl-text@0.2.3/mapbox-gl-rtl-text.js');
  57249   * ```
  57250:  * @see [Add support for right-to-left scripts](https://maplibre.org/maplibre-gl-js/docs/examples/mapbox-gl-rtl-text/)
  57251   */

andreact-map-gl/dist/exports-maplibre.cjs:
  870    const {
  871:     RTLTextPlugin = "https://api.mapbox.com/mapbox-gl-js/plugins/mapbox-gl-rtl-text/v0.2.3/mapbox-gl-rtl-text.js"
  872    } = props;

andreact-map-gl/src/utils/set-globals.ts:
  38    const {
  39:     RTLTextPlugin = 'https://api.mapbox.com/mapbox-gl-js/plugins/mapbox-gl-rtl-text/v0.2.3/mapbox-gl-rtl-text.js'
  40    } = props;

Fixed by using the latest version of ReatMapGL and ac2c4177378aebc94420d49e1a38a54bf63a724d


#CCR-955 improved tooltip

Proposed Changes
Please use the Jira Key followed by the changes

CCR-955

improved tooltip for files item

Checklist

[ ] I have added or updated unit tests
[ ] I have added or updated integration tests (if appropriate)
[ ] I have added or updated documentation / readme (if appropriate)
[ ] I have verified that my changes have not introduced new lint errors
[x] I have added a GitHub labels to the PR for either patch, minor, or major

Testing Instructions

point 4 in this comment https://virtru.atlassian.net/browse/CCR-955?focusedCommentId=133556

What problem is this solving?

point 4 in this comment https://virtru.atlassian.net/browse/CCR-955?focusedCommentId=133556

We should not add things to this repo that are only for one product. That looks like it should be solved by the application. The application should make sure to give the Tooltip component the correct props.

What problem is this solving?

point 4 in this comment https://virtru.atlassian.net/browse/CCR-955?focusedCommentId=133556

We should not add things to this repo that are only for one product. That looks like it should be solved by the application. The application should make sure to give the Tooltip component the correct props.

This issue can be in any product if we will pass not an only string. In the tooltip, we can use any tags

What problem is this solving?

point 4 in this comment https://virtru.atlassian.net/browse/CCR-955?focusedCommentId=133556

We should not add things to this repo that are only for one product. That looks like it should be solved by the application. The application should make sure to give the Tooltip component the correct props.

This issue can be in any product if we will pass not an only string. In the tooltip, we can use any tags

React components should not expect to display HTML. They should expect to display JSX. Using HTML inside of React components is an anti-pattern, and as a reusable library Virtuoso should be very opinionated about this.


someone know how to support Optional Content

case 'UseOC':
// Not implemented, since we don't support Optional Content Groups yet.

Closing since this is basically a duplicate of #269. It's a large feature to implement and doesn't seem to be used very often, so it's not on our priority list.


Generic error message

This looks like a great tool and I’d love to use it. Unfortunately, I’ve only been able to get this rather generic error message:
==========
Error creating merge request: exit status 128
==========

It appears to be coming from this section of code, but I’m not clear which one specifically or what the error is.
I am using a self-hosted GitLab instance, but I don’t think that’s causing the issue.
I’m not at all familiar with Go; is there any way to add a more specific error message for each of those conditions to try and track down the root cause?

Thanks for the feedback @macbookandrew . Whilst I'm unsure as to why you are getting an error, I have just pushed a change that should print out the error message when there is an error, which hopefully helps us find out what is going wrong.
I use this utility on two separate self-hosted Gitlab instances, so that is not the issue. I suspect it may be some permission issues on the Gitlab repository itself with regards to who can push a merge request, but I'm not sure.
Please try again (I've updated the docker images) and let me know if this now returns a more useful error? Thanks.

Thanks a lot! That gave me this. We have disabled Git access over HTTP because we require 2FA. I’ll add a step to convert URL structure to work around this.
remote: Git access over HTTP is not allowed
fatal: unable to access 'https://path-to-my-project/': The requested URL returned error: 403

Looks like the image needs SSH in order for that to work:
error: cannot run ssh: No such file or directory

Thanks for the updated merge request! I've just rebuild & pushed the docker images with the openssh-client installed - please test and let me know if this solves your issue?

Getting closer. Now it’s using root as the git username instead of git:
$ gitlabci-composer-update-mr <name> <email> <branch>
Pulling latest changes from <branch>
Warning: Permanently added the RSA host key for IP address <IP address> to the list of known hosts.
root@my-gitlab-server: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
==========
Error switching branch: exit status 1
==========

Looking at your codebase, I see some other code that may not be compatible with our SSH-only server. I may end up having to fork and rework it for SSH.

Ahh yes, that makes perfect sense (good find!). Much of that I inherited (rewrote into Go) based on the original PHP module, so I'm sure that logic can be reworked/improved. Those git environment variables are based on CI_REPOSITORY_URL environment setting passed through from the CI process, however I don't know if that can be easily converted into an SSH-type URL.
If I was to add a "debug line" to that function to print out your CI_REPOSITORY_URL and you could tell me what it says (you should of course substitute your actual data with fake) then that would be a great starting point for me. Please tell me which image you're using and I'll update it for the test.

We’ve run into this on other pipelines and have this set up to convert the URL structure:
$ SSH_GIT_URL=$(echo "$CI_REPOSITORY_URL" | sed 's/git.my-gitlab-server\//git.my-gitlab-server:/' | cut -d "@" -f 2)
$ git remote set-url origin $SSH_GIT_URL
$ git remote get-url origin # verify URL
git.my-gitlab-server:demo/test-project.git
$ gitlabci-composer-update-mr <name> <email> <branch>

So far so good, and we also have the SSH key added in with a before_script step. But apparently the current user in the container is root, not git, so the git checkout command fails due to invalid username.

I see, however I don't know the format of CI_REPOSITORY_URL is when HTTP(S) access is specifically disabled. If that format is different to the standard HTTP(s) syntax then we can set up git differently in that case. I would however assume that a gitlab-ci-token is supplied one way or another (maybe via the CI_JOB_TOKEN variable?).
One thing that confuses me a little is a previous comment you made that you "have disabled Git access over HTTP because we require 2FA". We have 2FA as well and allow HTTPS (the "gitlab-ci-token" bypasses 2FA, like an "app password" in Google etc). I don't see why HTTPS is disabled because of 2FA? Regardless though, it would be nice to not have to use HTTP(S), but I'm unsure what I can do to fix that from my end. as I don't have a similar environment here to test with.

Yes, there is a gitlab-ci-token supplied; here’s the CI_REPOSITORY_URL format:
<EMAIL_ADDRESS>
Our GitLab administrator has disabled HTTP(S) access as described here and is enforcing 2FA for all user accounts. I think 2FA breaks git clone|pull|push https://my-gitlab-server but I could be wrong. l’ll see if they can enable HTTPS for git operations and see if that helps.

Glad to hear it is working! Don't worry about the PR, I have reverted your change and am building new images now.


Attributes in gts fetch

Hi guys. I am having trouble getting the attributes in a gts object. When I get the gts the information does not come.
I do the following:
1 - I insert the gts:
Post: http://<IP_ADDRESS>:8080/api/v0/update
gts body:
1 / 10.0: 10.0 / 0 test {asid = 51ce2135-ece5-419e-97ee-00570b894c14, arid = de52aec5-9744-4254-a960-4beec783760d, dvid = 7e5d6d42-4106-4691-9e0c-2b080fdeb13d = cdd = dsd = cdd = cdd = cdd = cdd = cdd = cdd = cdd = cdd = cddd Measurement, alid =, assd = 18568cf4-107a-4925-89a8-99b63f2fe511} {rcdt =<PHONE_NUMBER>385, _id = ec0db0c4-48ce-473f-b860-0021434d16f9, evdt =<PHONE_NUMBER>385} 789
2 - Getting the gts.
Get: http://<IP_ADDRESS>:8080/api/v0/fetch?now=now&timespan=-5&selector=~.*{}&format=fulltext&showattr=true&dedup=t&sortmeta=false
Response:
1/9.999999990686774:9.999999990686774/0 prueba{asid=51ce2135-ece5-419e-97ee-00570b894c14,arid=de52aec5-9744-4254-a960-4beec783760d,dvid=7e5d6d42-4106-4691-9e0c-2b080fdeb13d,csid=,.app=noentiendo,evty=Measurement,alid=,assd=18568cf4-107a-4925-89a8-99b63f2fe511}{} 789
1/9.999999990686774:9.999999990686774/0 test{asid=51ce2135-ece5-419e-97ee-00570b894c14,arid=de52aec5-9744-4254-a960-4beec783760d,dvid=7e5d6d42-4106-4691-9e0c-2b080fdeb13d,csid=,.app=noentiendo,evty=Measurement,alid=,assd=18568cf4-107a-4925-89a8-99b63f2fe511}{} 789
The attributes section is blank
Could you please help me, I need to search for attribute values
Thank you very much

Hi, add ingress.parse.attributes = true in your configuration (or uncomment it).

Thank you very much for the answer, I have several configuration files, could you tell me where this property is located?

It worked!!! Add to files
10-egress.conf
10-ingress.conf
In the path: opt / warp10 / etc / conf.d
Thank you very much


Consider the confusion around == vs ===

Many JS users have been taught to avoid == due to type coercion and instead favor ===.
Sometimes even strict lint rules could prevent usage of ==.
Examples
// Source code
console.log(a == b)

// Possible Bugs
console.log(1 == '1')          // true
console.log(1n == '1')         // true
console.log(BigInt(1) == '1')  // true
console.log(null == undefined) // true

// Fixed with triple equals
console.log(1 === '1')          // false
console.log(1n === '1')         // false
console.log(BigInt(1) === '1')  // false
console.log(null === undefined) // false

This proposal mentions that the opposite is true for the Decimal type because === is no overridable. So it sounds like Decimal(x) === Decimal(y) will never be true 🤔
The part I want to point out that is deceiving is this:
console.log(BigInt(1) === BigInt(1))     // true
console.log(Decimal(1) === Decimal(1))   // false

Possible solutions:

Allow overriding ===
Disallow overriding ==
???

Note that === invariance is pretty important for {Weak?}{Map,Set} keys.
I'd personally be a fan of restricting operator overloading to value types and make == non-overloadable (hence making ===/== the same for value types).
e.g. Maybe something like?:

const Complex = ValueType('Complex', {
  // If the returned value from create is the same then the same
  // value returned when constructing one
  create: (re, im) => #{ re, im },
  operators: {
    '+'(a, b) { return Complex(a.re + b.re, a.re + b.im) },
  },
});

Complex(3, 4) === Complex(3, 4); // true

Without this though there will also be Weak References which allows constructing a WeakValueMap. With a WeakValueMap one can cache objects such that Complex(3, 4) === Complex(3, 4) works.

=== gets at a strict version of equality, so I'd like to stick to strong invariants there by not making it programmatically overridable. Instead, "value types", which would generalize the records and tuples proposal, would support deep structural equality, so if a type wants to make two things ===, it can just make them actually the same value (without having to hold onto one of them for identity).
Does this mean we shouldn't support overloading ==? This seems debatable to me. If we think that we really really shouldn't give == any useful semantics, that makes me regret the BigInt semantic decision where it allows comparison across numeric types for mathematical equality (whereas === will return false across types).

BigInt is a primitive, so it having useful semantics for == makes sense to me. When comparing two objects, however, I'd expect == and === to always be the same (as I think they currently are?)

I wonder if we could get a bit deeper into how overloading == relates to other operators in terms of expectations. Right now, you can rely on the invariant that +always returns a primitive, just as strongly as you can count on == comparing Objects by their identities.
How do these invariants compare in terms of what programmers depend on and we need to preserve?
Does the with operators from declaration mitigate any surprising effects, given that behavior remains the same without the declaration (except that usage of operators will cause exceptions to be thrown)?


api change to .notA

resolving this for anyone else that uses the new beta release of Xcode8

Thank you for sending this PR.
We have landing swift3 support in master branch, which includes this change.
Feel free to give it a go.
🍻


Support sub-byte types for LLMs

This issue is meant to house the list of tasks/issues pertaining to enabling sub-byte types for large language models (LLMs). It spans different layers in the whole IREE stack, which are organized into different task lists. The immediate goal is to enable end-to-end solution to quantized matmul, examples in #12859; the ultimate goal is to enable end-to-end LLaMA/Alpaca/etc. inference.
For sub-byte types, right now the focus is on power of two bit widths (i4 and i2). We may need to extend to i3 in the future; but that would likely mean its own tracking issues.
## Flow/Stream tasks
- [ ] https://github.com/openxla/iree/pull/13344

## SPIR-V CodeGen Tasks
- [ ] https://github.com/openxla/iree/issues/13552
- [ ] https://github.com/openxla/iree/pull/13603
- [ ] https://github.com/openxla/iree/issues/13601
- [ ] Enable end-to-end `i4` matmul (tracking issue pending)

## LLVM CPU CodeGen Tasks
- [ ] https://github.com/llvm/llvm-project/issues/62662
- [ ] Push through the dequant operation in isolation (tracking issue pending)
- [ ] Enable end-to-end `i4` matmul (tracking issue pending)

## VM tasks
- [ ] [vm] Make sure proper FlatBuffer serialization for sub-byte types (tracking issue pending)
- [ ] Expose sub-byte types to IREE ABI for data exchange with users (tracking issue pending)
- [ ] Enable sub-byte data read/write in IREE tools (tracking issue pending)

## Model tasks
- [ ] Generate full end-to-end i4 LLaMA/Alpaca model (tracking issue pending)

@yzhang93 fyi

Hi @qedawkins , are you going to work on this task 🙂 ? Originally I was planning to pick this up next week (but will probably spend 20% of my time). If it's urgent and you are going to work on it then I'll skip this task. Otherwise feel free to assign any tasks to me that still need a person to work on.

Hi @qedawkins , are you going to work on this task slightly_smiling_face ? Originally I was planning to pick this up next week (but will only spend 20% of my time).
If it's urgent and you are going to work on it then I'll skip this task. Otherwise feel free to assign any standalone tasks to me that still need some people to work on.

Hi @pzread, it would be awesome if you want to help out here. There are a few items on the list and we have someone slated for Move SPIRV small bitwidth load/store emulation to memref, but there will certainly be tasks up for grabs and I can let you know (haven't really figured out all of the required work yet/work distribution necessary here).
The dequantization task is a subtask of #12859 which is more of an end goal than an individual item (also not all of which is specific to sub-byte element types). I don't think anyone is working on Add support for power of 2 sub-byte aligned types to IREE tooling yet though

I've updated the tile and the tasklist to make it more clear.

@hanhanW @yzhang93 Here is the current reference IR (and tracking issue): https://github.com/openxla/iree/issues/12859#issuecomment-1546067940

Thanks for the pointer!
@yzhang93 This is still aligned with our discussion, except the configuration of typeConverter. We'll return int4 for int4 input, not int8 for int4 input. In this context, the types match, so we don't have to create cast ops. Let me know if you run into any issues, I'm happy to look into the code and IRs. I can also help with generating the input IR for the pass from the reference IR.

Thanks for the pointer!
@yzhang93 This is still aligned with our discussion, except the configuration of typeConverter. We'll return int4 for int4 input, not int8 for int4 input. In this context, the types match, so we don't have to create cast ops. Let me know if you run into any issues, I'm happy to look into the code and IRs. I can also help with generating the input IR for the pass from the reference IR.

I'm quite confused by what you said return int4 for int4 input for typeConverter. Then is the memref data linearization and shift logic still holds for this case? If possible can we have a VC sometime tomorrow? I can show you what I have right now.

Okay, SG. I'm available tomorrow, please send me an invitation. Or we can sync on Monday.

Regarding the "Enable end-to-end i4 matmul (tracking issue pending)" entries above for LLVM CPU, I have filed this issue with my brain-dump on the topic: https://github.com/openxla/iree/issues/14195 - consider linking it from the above tasks overview ?

Don't we have most of this all supported ? Should we close and open a new one for future tasks ?

Yeah, let's call this done and re-open with the roadmap of types you were showing this morning.


Rewrite testEql using Typeable to make it impossible to forget cases

Description
Everything is Typeable so we can use that to reduce some clutter.
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[x] New tests are added if needed and existing tests are updated
[x] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[x] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[x] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

@lehins and @TimSheard it would be good to get this reviewed and merged.

@lehins could you please run the checks? I think this is the final version of the PR.

@lehins done

@lehins something appears to be broken in CI.

@MaximilianAlgehed Looks like some issue with Github since yesterday. Traballs don't get downloaded fully or corrupted. This happens on multiple repos that we have.
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive

@MaximilianAlgehed Looks like Github has finally back to normal operation since yesterday. Just in case I implemented a fallback workaround too in #3713
Do you mind rebasing again on master again? We've had a few PRs merged yesterday.

@lehins still broken?

@lehins still broken?

@MaximilianAlgehed Why do say it is broken? CI hasn't finished yet. (Only "Required" ones are important)

Right... So the one thats called ci is irrelevant to CI?

Right... So the one thats called ci is irrelevant to CI?

It is relevant, but it just doesn't work for forked repos, I think. In any case it is not terribly reliable, but it is useful, since it runs CI in nix, where GithubActions is build with regular cabal setup without nix.

Perfect, thanks for clearing that up. I won't care about that one in the
future when working from our fork.
Den tors 7 sep. 2023 12:41Alexey Kuleshevich @.***>
skrev:

Right... So the one thats called ci is irrelevant to CI?
It is relevant, but it just doesn't work for forked repos, I think. In any
case it is not terribly reliable, but it is useful, since it runs CI in
nix, where GithubActions is build with regular cabal setup without nix.
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/cardano-ledger/pull/3697#issuecomment-1709923441,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBPPQN4JAPPOSFDWLVURDDXZGQETANCNFSM6AAAAAA4HJFO4I
.
You are receiving this because you were mentioned.Message ID:
@.***>


Fix benchmark run build

Fixes a regression introduced by #9134
Pull Request Description
Make sure that sbt is invoked only if there are some tasks to run. If not, sbt all is invoked, which fails, as all is not a command.
Important Notes
The first Engine Benchmarks job failure is in https://github.com/enso-org/enso/actions/runs/8073012762/job/22055882533#step:8:923
Benchmark Standard Libraries are failing since the same time, and on the same error, for example at https://github.com/enso-org/enso/actions/runs/8073051776/job/22056002795
Checklist

[ ] Make sure that (dry-run) benchmarks are fine

Dry-run engine benchmarks scheduled at https://github.com/enso-org/enso/actions/runs/8094436748


Failed to open file test/struct_unsigned_char_ptr_to_struct_constant_description_ptr_key_value_pair_ptr_binary_search.l2 for read

[HOSTCC=gcc]
$ make kernel
...
Failed to open file test/struct_unsigned_char_ptr_to_struct_constant_description_ptr_key_value_pair_ptr_binary_search.l2 for read.
On line 1 in file test/struct_unsigned_char_ptr_to_struct_constant_description_ptr_key_value_pair_ptr_binary_search.l2
recc: linker.c:590: process_assembly: Assertion `0 && "OFFSET not declared.."' failed.
kernel/Makefile:5: recipe for target 'kernel/kernel.l1' failed
make: *** [kernel/kernel.l1] Aborted (core dumped)

Ah yes, I was a bit sloppy when I released last.  The build process is complicated which I need to work on, but if you do
'make' it should build that dependency that is missing, then it will try to run the unit tests, but unless you've set up the testing API on your machine, it will error out when it starts chrome (but you can ignore that because you got the dependency built that you need).
Then, to build the kernel image without trying to run it in the browser (which requires the API), you can just do
make kernel/kernel.l1
Then you can do
make run-c-emulator
or
make run-java-emulator
or
make run-python-emulator
and it should just work.  You can exit the kernel with the 'q' key.
If you get build errors, it might be because you have a different version of gcc or clang, so it is safe to delete all the compiler flags from the root makefile.
I'll fix this dependency error and change around the make file soon.
Leme know if you need help.

Still it isn't working.
I think if you clone the project from github into a new directory, you will be able to replicate the build error.

I just tried out doing
git clone https://github.com/RobertElderSoftware/recc.git && make test/filesystem.l1 && make kernel/kernel.l1
and that should work to build the kernel.  Then I did
make run-python-emulator
and I can get it to run (it is quite slow at the moment).
make run-c-emulator
will run it a bit faster (but I just noticed that clang complains with some of the strict warning flags).  If you delete the clang flags from the makefile it runs without a hitch.
I'll update the makefile to make it more user friendly.

I seems to be a gcc-related problem. With clang, make kernel/kernel.l1 and run-c-emulator works, albeit with slightly reduced CLANG_FLAGS.

What kind of problem/error messages to you get?

I just pushed an update to make the makefile a bit more clear, fixed a few warnings, and fixed the build for the kernel image.  Here were my steps:
Tested on Ubuntu 4 with gcc 3.3.4
Grab and unzip
wget http://recc.robertelder.org/recc.tar.gz && gunzip recc.tar.gz && tar -xvf recc.tar
Old versions of gcc don't understand newer warnings flags
cat Makefile | sed 's/GCC_FLAGS=.*/GCC_FLAGS=/g' > newmake && mv newmake Makefile
Build kernel
make bootstrap-datatypes && make kernel/kernel.l1
Run Kernel
make run-c-emulator
Tested on Ubuntu 14:
gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4
git clone https://github.com/RobertElderSoftware/recc.git && cd recc && make bootstrap-datatypes && make kernel/kernel.l1
make run-c-emulator
I'll consider it resolved for now, but if something is still broken, feel free to re-open an issue.


create CLI

$ cienv --format [json|export]

$ cienv --formant export
export BRANCH=xxx
...

$ eval "$(cienv -f export)"

$ cienv
{
  "branch": "xxx"
}

@suzuki-shunsuke, did this meet your expectations? I've used ci-env instead of cienv to avoid conflicts with the existing folder named 'cienv'.

Thank you for your contribution!
But sorry, this issue is very old (over four years ago) and I don't remember why this issue is still open.
I have already developed a similar tool.
https://github.com/suzuki-shunsuke/ci-info
ci-info was released about a month after this issue was created.

This issue was created at Sep 10, 2020
https://github.com/suzuki-shunsuke/ci-info/releases/tag/v0.1.0-0 (Oct 25, 2020)

I close this issue because I have already developed a similar tool ci-info.
I'm sorry about that.

https://github.com/suzuki-shunsuke/go-ci-env/pull/154#issuecomment-2409617328


PREFIX

i make a prefix with meta but dosn work

btw i have essentials chat plugin

This section of the wiki might help.

You need vault.

ok thanks


[feature] adopt comment-api

🧩 Feature
adopt comment api
Description
https://code.visualstudio.com/updates/v1_35#_comments-api
https://github.com/microsoft/vscode-extension-samples/tree/main/comment-sample
 A clear and concise description of the feature

look nice and it also looks like a selection of multiple lines can be made. For our review purposes marking "reviewed" areas is important

I very much like that. We also stumbled upon this API in the last couple of days. It looks very nice and is used by other plugins as well (Atlassian plugin for instance).
I see two topics to be tackled, though, before starting any implementation:

How to integrate all the information that can currently be entered in the webview into this inline view? (name, description, category, priority)
How should the data model look like when multiple comments are added?

Ich think this will be a quite heavy breaking change. As far as I have seen, there is no possibility to provide a custom layout within this comment box.
Another Idea could be to have this in addition for making fast comments, which can be edited in the current editor afterwards and assigned to categories etc.
Multiple comments could be handled in the current data structure by es special escape sequence. But maybe it would be the best to refactor everything including the data model and provide a completely new version / plugin


Bugfix search in ClassLoader for some framework like dev mode in Play

See : https://github.com/playframework/playframework/issues/6207

merged - thanks


Feat/motion library

@pkhrag plz review and merge

change the default pid values to what we calculated last night. Is the arduino node working from the current launch file? If not either fix it ir remove it for now.

pid values are being set in launch file. I couldn't find any way for dynamic_reconfig to take values from launch file and set it in it's gui. Arduino node is not working from the launch file but let it be there for now, we will fix it later


updated package.json to point to react v18

update for #329

It looks like this build failed because we need to run npm install on this branch to get package-lock in sync.

Closed in favor of #327


Update dependency

What
Updated required version for dependency.
How to review
LGTM.
Who can review
Anyone.

Need a bit more context as to why you're doing a hotfix and not following the normal development cycle


Fix normalizeChannel()

Any time the constraints of normalizeChannel() are violated it returns
undefined, which is rarely what we want.
 This should lower the prevelance of #undefined in
user-facing applications.
See-also: https://github.com/ssb-js/ssb-ref/pull/33

Sweet!


Can't run project on Apple M1 Machines when Flowbius dependency is added to a kotlin library module

Summary
Gradle Sync fails on Machines with Apple M1 Chipset when Flowbius dependency is added to the kotlin library module of my project. The project runs fine on Intel machines though.
Dependency
implementation 'com.trello.flowbius:flowbius:0.1.0'
Description
I'm trying to add flowbius to a kotlin library module of my project and I get the following error when I try to run the project on M1 machines:
Execution failed for task ':core:compileKotlin'.
> Error while evaluating property 'filteredArgumentsMap' of task ':core:compileKotlin'
   > Could not resolve all files for configuration ':core:compileClasspath'.
      > Could not resolve com.trello.flowbius:flowbius:0.1.0.
        Required by:
            project :core
         > No matching variant of com.trello.flowbius:flowbius:0.1.0 was found. The consumer was configured to find an API of a library compatible with Java 11, preferably in the form of class files, preferably optimized for standard JVMs, and its dependencies declared externally, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm' but:
             - Variant 'apiElements' capability com.trello.flowbius:flowbius:0.1.0 declares an API of a library, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm':
                 - Incompatible because this component declares a component compatible with Java 17 and the consumer needed a component compatible with Java 11
                 - Other compatible attribute:
                     - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
             - Variant 'runtimeElements' capability com.trello.flowbius:flowbius:0.1.0 declares a runtime of a library, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm':
                 - Incompatible because this component declares a component compatible with Java 17 and the consumer needed a component compatible with Java 11
                 - Other compatible attribute:
                     - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)

This issue does not occur on Mac with Intel Chip. It is however resolved for M1 Chip Machine as well if I change my module's targetCompatibility to JavaVersion.VERSION_17 or when I change this module to to an android library.
Project Configuration
Gradle file of module in which I'm trying to add Flowbius:
plugins {
    id 'org.jetbrains.kotlin.jvm'
}

dependencies {
    api "com.spotify.mobius:mobius-core:1.5.9"
    implementation 'com.trello.flowbius:flowbius:0.1.0'

    testImplementation "com.spotify.mobius:mobius-test:1.5.9"
    testImplementation "org.junit.jupiter:junit-jupiter-engine:5.8.2"
    testImplementation "org.junit.jupiter:junit-jupiter-params:5.8.2"
    testImplementation "com.google.truth:truth:1.1.3"
}

java {
    sourceCompatibility = JavaVersion.VERSION_11
    targetCompatibility = JavaVersion.VERSION_11
}

test {
    useJUnitPlatform()
}

Project's Root Gradle
plugins {
    id 'com.android.application' version '7.2.2' apply false
    id 'com.android.library' version '7.2.2' apply false
    id 'org.jetbrains.kotlin.android' version '1.7.10' apply false
    id 'org.jetbrains.kotlin.jvm' version '1.7.10' apply false
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

Environment
Laptop:
M1 Pro chip MBP with Mac OS Monterey 12.6.
Android Studio:
Android Studio Dolphin | 2021.3.1
java --version:
openjdk 11.0.15 2022-04-19 LTS
OpenJDK Runtime Environment Zulu11.56+19-CA (build 11.0.15+10-LTS)
OpenJDK 64-Bit Server VM Zulu11.56+19-CA (build 11.0.15+10-LTS, mixed mode)

Thanks, I believe we just didn't specific source compatibility in the previous build. We will release a 0.1.1 soon and we will include that.


Navbar dropdown not aligning.

Honestly don't know what the issue is.

Issue found - Working on fix now.


Scanning screen does not come back after targetLost-event

The scanning screen provides clear gui-feedback to the user that scanning is going on. As such, it is very helpful. However, once a target-match has been found, it won't come back.
Is there any way of making it show up again after a targetLost-event?

@HeimMatthias Actually, I couldn't decide which one should be the default behaviour when I implemented that. Should the scanning screen only be shown the first time or not.
Will it be very annoying if the scanning screen show up every time when the tracking is lost like momentarily for a second or so?
Love to hear some feedback.

I think the most practical for users of the library would be to have a function with which to enable the scanning screen again.
I can see that it would be annoying if the screen came back every time the target is lost for a second, but the default behaviour will be different from project to project (and maybe even from target to target).
For example, in my sample project, I have targets that trigger a video to play - if I loose the target , for a fraction of a second, I clearly don't want the additional overhead for the scanning screen to to come back before the video continues. On the other hand, I also use targets that simply trigger a slide-in frame with additional links, and in this case I don't mind if the scanning screen comes back immediately; as the user may simply use the scanner to go to the next target to load a different information screen.
So, while it would be good to have a boolean loading option to change the default behaviour of the screen coming back or not, in my case it would be most useful to be able to do something like this programatically:
exampleTarget.addEventListener("targetLost", event => {
      setTimeout(function() {
          if (!arSystem.targetIsBeingTrackedAtTheMoment()) arSystem.showScanningScreen();
      }, 2000);
    });

(sorry, the function names are woefully inadequate, but I think you get the idea).

Hi, wondering if anyone's got a solution/workaround to this?

this.el.addEventListener('targetLost', () => {             setTimeout(() => {               return document.querySelector('a-scene').systems['mindar-image-system'].ui.showScanning()             }, 1000)  })
work for me

this.el.addEventListener('targetLost', () => { setTimeout(() => { return document.querySelector('a-scene').systems['mindar-image-system'].ui.showScanning() }, 1000) })
funciona para mi

I was just looking for this, the code looks very good, but it is not clear to me where to write it

@underlabmx check out the events-handling demo see how/where to reference an 'exampleTarget' and catch when lost.
ie something like :
const exampleTarget = document.querySelector('#example-target')
// detect target lost
exampleTarget.addEventListener("targetLost", event => {
	// console.log("target lost")
	setTimeout(() => { return document.querySelector('a-scene').systems['mindar-image-system'].ui.showScanning() }, 1000)
})


PhaBox2 Conda Installation Error (+Solution)

Dear JiaYu,
I wanted to report a small channel priority issue for conda installation of PhaBox2 that I've managed to fix. I would recommend updating your Wiki!
This installation works:
conda create -n phabox2 phabox=2.1.5 -c conda-forge -c bioconda -y

This installation gives an error:
conda create -n phabox2 phabox=2.1.5 -c bioconda -c conda-forge -y

The -c conda-forge repository needs to be set at top priority and -c bioconda as second priority. This wouldn't raise an error if  conda config --set channel_priority flexible is set, but for me I always have my configuration on conda config --set channel_priority strict to make sure all environments are reproducible.
Final Solution, run:
conda config --add channels bioconda
conda config --add channels conda-forge
conda config --set channel_priority strict
conda create -n phabox2 phabox=2.1.5 -c conda-forge -c bioconda -y

Hope this helps! I wanted to post it here incase someone runs into a similar issue.
Best,
Erfan

I see. Good to know.
I will revise the WIKI accordingly. Thanks.
Best,
Jiayu


Feat: Adding a navbar on top

Describe the feature
We can add a navbar consisting of home, about us, contact us and support elements
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

kindly consider assigning it to me.

Duplicate issue


default() vs new() for struct update syntax

C-CTOR suggest to use Struct::new(). I saw also the use of Default::default(), like in https://tomaka.github.io/glium/glium/draw_parameters/struct.DrawParameters.html. Maybe a point could be added about when to use which.

I somewhere seen a recommendation to prefer Default over empty new() method. Following it I removed new() for crypto-hashes crates and only left for cases when some additional arguments must be passed for hash initialization.
But now I am considering to add new() to Digest trait implemented as fn new() -> Self { Self::default() }. For example it simply does not look right to call Sha256::default() instead of Sha256::new(). Yes, it will be somewhat redundant, but stylistically more appealing.
But anyway it will be indeed nice to have some rules regarding default() vs new().

We will follow up on this as part of #38.


Add 'Not tested v3' labels to untested legacy bonus guides + introducing labels in 'Bonus Section'  index page

What
This PR adds a yellow 'Status: Not tested v3' label to all the untested legacy bonus guides.
It also add a 'Labels' section to the 'Bonus Section' index page that introduces the reader to the meaning of these labels.
For now, two categories of labels exist: Difficulty (Easy/green, Intermediate/yellow, Hard/red) and v3-tested status (tested/green or not tested/yellow). More labels could be added later on if judged useful.
Why
To warn readers that a bonus guide might not work on a RaspiBolt v3 and might require some slight or heavy adaptions to make it work.
How
Added the yellow status label to all untested legacy guides.
Added a Label section to the bonus section.
Scope

[ ] significant change to core configuration
[ ] independent bonus guide
[x] simple bug fix

Test & maintenance
Check that the label syntax is correct as they are not displayed in the Github preview.
Animated GIF (optional)

I like adding the untested lables. They're not quite aligned perfectly, because that only works if there's regular text just above the labels, but that's a minor concern. I think that can be fixed when updating each individual bonus guide.
I would restructure the Bonus Section a bit, however:
* The introductory text with the warning is no longer necessary with the explicit "Status' lables.

* The ToC is pushed to the bottom and is not visible enough. I think we should move it above the labels section.

* How about breaking from the regular syntax and making the ToC a proper H2 section?

I also rephrased the text for brefity. And how about using the simpler "Medium" instead of "Intermediate"?
See my proposed changes to the Bonus Section page here. I can also push these changes directly. Whatever you prefer.
Stadicus@d510dd9
See here for a preview: https://stadicus.github.io/raspibolt-dev/bonus/

Great suggestions, LGTM! feel free to push the changes directly from your branch.
(there is one small typo "All bonus guides are rated with lables": lables should be labels)

Not sure if I'm doing something wrong, but I can't push to your branch. Did you enable the "allow changes from maintainers" (or similar) checkbox when creating the pr?
$ git push vajra vajra/bonus-labels
Total 0 (delta 0), reused 0 (delta 0)
To github.com:VajraOfIndra/RaspiBolt.git
 ! [remote rejected] vajra/bonus-labels -> vajra/bonus-labels (permission denied)

Maybe its easier if you just copy/paste the changes for now?

Yeap, the 'Allow edit by maintainers' is ticked.. not sure why it doesn't work.
Ok, will do the changes manually, np.

I incorporated your changes to the Bonus section index page, PTAL

One little nit, otherwise LGTM

Super, I added the separator, I'll merge now.


[Release Checklist] 2.6.0-RC1

[ ] OpenShift Pipeline
[ ] Konvoy Pipeline
[ ] Native K8s Pipeline
Upgrade Pipelines [spc/cstor/jiva]

[ ]  1.0 to 2.6.0-RC1
[ ]  1.1 to 2.6.0-RC1
[ ]  1.2 to 2.6.0-RC1
[ ]  1.3 to 2.6.0-RC1
[ ]  1.4 to 2.6.0-RC1
[ ]  1.5 to 2.6.0-RC1
[ ]  1.6 to 2.6.0-RC1
[ ]  1.7 to 2.6.0-RC1
[ ]  1.8 to 2.6.0-RC1
[ ]  1.9 to 2.6.0-RC1
[ ] 1.10.0 to 2.6.0-RC1
[ ] 1.11.0 to 2.6.0-RC1
[ ] 1.12.0 to 2.6.0-RC1
[ ] 2.0.0 to 2.6.0-RC1
[ ] 2.1.0 to 2.6.0-RC1
[ ] 2.2.0 to 2.6.0-RC1
[ ] 2.3.0 to 2.6.0-RC1
[ ] 2.4.0 to 2.6.0-RC1
[ ] 2.5.0 to 2.6.0-RC1

cspc/cstor csi volume upgrade

[ ] 1.10.0 to 2.6.0-RC1
[ ] 1.11.0 to 2.6.0-RC1
[ ] 1.12.0 to 2.6.0-RC1
[ ] 2.0.0 to 2.6.0-RC1
[ ] 2.1.0 to 2.6.0-RC1
[ ] 2.2.0 to 2.6.0-RC1
[ ] 2.3.0 to 2.6.0-RC1
[ ] 2.4.0 to 2.6.0-RC1
[ ] 2.5.0 to 2.6.0-RC1

ZFS Upgrade Pipelines

[ ]  0.4.1 to 1.4.0-RC1
[ ]  0.5 to 1.4.0-RC1
[ ]  0.6.1 to 1.4.0-RC1
[ ] 0.7.0 to 1.4.0-RC1
[ ] 0.8.0 to 1.4.0-RC1
[ ] 0.9.2 to 1.4.0-RC1
[ ] 1.0.0 to 1.4.0-RC1
[ ] 1.0.1 to 1.4.0-RC1
[ ] 1.1.0 to 1.4.0-RC1
[ ] 1.2.1 to 1.4.0-RC1
[ ] 1.3.0 to 1.4.0-RC1

Migration spc pool to cspc and cstor volume to cstor csi volume

[ ] 1.12.0 to 2.6.0-RC1
[ ] 2.0.0 to 2.6.0-RC1
[ ] 2.1.0 to 2.6.0-RC1
[ ] 2.2.0 to 2.6.0-RC1
[ ] 2.3.0 to 2.6.0-RC1
[ ] 2.4.0 to 2.6.0-RC1
[ ] 2.5.0 to 2.6.0-RC1

Images are now available
openebs/node-disk-exporter:1.2.0-RC1
openebs/node-disk-operator:1.2.0-RC1
openebs/node-disk-manager:1.2.0-RC1

openebs/zfs-driver:1.4.0-RC1

openebs/migrate:2.6.0-RC1
openebs/linux-utils:2.6.0-RC1
openebs/upgrade:2.6.0-RC1
openebs/cstor-webhook:2.6.0-RC1
openebs/cstor-pool-manager:2.6.0-RC1
openebs/cstor-volume-manager:2.6.0-RC1
openebs/cspc-operator:2.6.0-RC1
openebs/cvc-operator:2.6.0-RC1
openebs/cstor-csi-driver:2.6.0-RC1

openebs/provisioner-localpv:2.6.0-RC1
openebs/velero-plugin:2.6.0-RC1
openebs/snapshot-provisioner:2.6.0-RC1
openebs/snapshot-controller:2.6.0-RC1
openebs/openebs-k8s-provisioner:2.6.0-RC1
openebs/admission-server:2.6.0-RC1
openebs/m-upgrade:2.6.0-RC1
openebs/m-exporter:2.6.0-RC1
openebs/cstor-volume-mgmt:2.6.0-RC1
openebs/cstor-pool-mgmt:2.6.0-RC1
openebs/m-apiserver:2.6.0-RC1
openebs/jiva:2.6.0-RC1
openebs/cstor-istgt:2.6.0-RC1
openebs/cstor-pool:2.6.0-RC1

PR for 2.6.0-RC1 changes https://github.com/openebs/charts/pull/191
PR for 2.6.0-RC1 helm chart https://github.com/openebs/charts/pull/192


Some great feature requests.

I have a few feature ideas that have existed in bots previously, they are as follows:
1.) Multi-threading and parallel processing to run multiple accounts simultaneously.
2.) Auto account creation by getting random names and details from a site like https://namefake.com/ where only captcha needs to be solved manually or it can be solved automatically with the help of services like:
1.) http://www.imagetyperz.com/
2.) https://deathbycaptcha.com/
3.) https://2captcha.com/
and saving these details into a text file for later use.
3.) Auto-redeem rewards with URL or name for different countries along with phone verification using a service with available API such as:
1.) https://frenziedsms.com/
2.) https://otpzone.com/
3.) https://www.textverified.com/
If you could implement this, it would make the bot completely automated which would save a lot of time.

Well, the idea about multiple accounts running simultaneously would be great. I was wondering what you mean by the auto account creation?
Its only able to run 5 at a time because of ip bans. But what I think would be a great idea would be to add rotating proxies along with an account creator. That would make the possibility of 100's of accounts available. As long as the bot could run fast enough, it could have as many accounts as you wanted!
This would be an amazing update and I would be totally down to help.

for captcha solving there is a extension nopecha they give peer ip if it is not a vpn 100 captcha free  every 24h

Hello @TatsP,
Thank you for your suggestions. We have considered implementing some of them in the past, such as the auto-account creator and parallel programming/multi-threaded running, but we were hesitant because of the increased risks. Ultimately, the decision was based on safety and resources.

Safety:

Multi-Threading:
We considered it more valuable to design an automation bot that could relatively safely accumulate reward points using 5 accounts per instance, rather than an automation bot that accumulates points using an unknown number of accounts in a single instance. This could potentially lead to a large number of reward accounts being shadow-locked or suspended, with dead or unusable reward points.
Account Creation:
After speaking with reward support on multiple occasions about locked, suspended, or troubleshooting reward accounts, we were given possible reasons for account moderation, such as providing fake information.

Resources:

Multi-Threading: As the name suggests, multi-threading requires significantly more computer resources than running each account one at a time.
Account Creation: There are no concerns or issues related to resources in this category.

While we have designed this repository with these two factors in mind, I am open to possibly implementing these features as optional for users who want to enable the more risky features that sacrifice safety and resources at their own risk. Similar to the AUTOMATE_PUNCHCARD environment variable, there will be a higher risk of ban/suspension/account moderation in exchange for increased earning potential.
Additionally, we would love to do more features for our international users. The only issue with that is the lack of foreign developers to work on the repository. Currently, the only contributors to this repository are based in the United States, which does not require phone verification for every reward redemption.
Therefore, we are unable to provide that feature at the moment because our accounts are based in the United States and we are unable to implement, debug, or test an automated phone verification system. We will be unable to implement that feature until a foreign, non-USA developer is able to do so.
Additionally, @NolanMastro, we have heard mixed responses from the support team and information online regarding the number of allowed accounts per IP. We may be increasing the number of allowed accounts from 5 to 6 very soon.

I am not a developer but i can change some things and test them in Germany
Alsow how your bot work with 5 profiles all at one's or one after one?
Prem Patel @.***> schrieb am Do., 8. Dez. 2022, 17:15:

Hello @TatsP https://github.com/TatsP,
Thank you for your suggestions. We have considered implementing some of
them in the past, such as the auto-account creator and parallel
programming/multi-threaded running, but we were hesitant because of the
increased risks. Ultimately, the decision was based on safety and resources.

Safety:

Multi-Threading:
We considered it more valuable to design an automation bot that could
relatively safely accumulate reward points using 5 accounts per instance,
rather than an automation bot that accumulates points using an unknown
number of accounts in a single instance. This could potentially lead to a
large number of reward accounts being shadow-locked or suspended, with dead
or unusable reward points.
Account Creation:
After speaking with reward support on multiple occasions about locked,
suspended, or troubleshooting reward accounts, we were given possible
reasons for account moderation, such as providing fake information.

Resources:

Multi-Threading: As the name suggests, multi-threading requires
significantly more computer resources than running each account one at a
time.
Account Creation: There are no concerns or issues related to
resources in this category.

While we have designed this repository with these two factors in mind, I
am open to possibly implementing these features as optional for users who
want to enable the more risky features that sacrifice safety and resources
at their own risk. Similar to the AUTOMATE_PUNCHCARD environment variable,
there will be a higher risk of ban/suspension/account moderation in
exchange for increased earning potential.
Additionally, we would love to do more features for our international
users. The only issue with that is the lack of foreign developers to work
on the repository. Currently, the only contributors to this repository are
based in the United States, which does not require phone verification for
every reward redemption.
Therefore, we are unable to provide that feature at the moment because our
accounts are based in the United States and we are unable to implement,
debug, or test an automated phone verification system. We will be unable to
implement that feature until a foreign, non-USA developer is able to do so.
Additionally, @NolanMastro https://github.com/NolanMastro, we have
heard mixed responses from the support team and information online
regarding the number of allowed accounts per IP. We may be increasing the
number of allowed accounts from 5 to 6 very soon.
—
Reply to this email directly, view it on GitHub
https://github.com/Prem-ium/BingRewards/issues/31#issuecomment-1342966107,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGC2LQS6ANCVB4T2NM64ODLWMICRVANCNFSM6AAAAAASRZWXEQ
.
You are receiving this because you commented.Message ID:
@.***>

I would be willing to test new features from another country as well as I would want to suggest a few more features:
1.) Solve Quiz and Polls correctly and always giving the correct answer as it would result in higher points due to right answers, this has already been implemented in other bots such as this bot https://github.com/MehdiRtal/MicrosoftRewardsBot
2.) Implementation of feature to automatically complete daily videos as well as the daily available web browser pages, this will result in additional 100-150 points per account, more information regarding this will be found in the below mentioned Reddit threads.
https://reddit.com/r/MicrosoftRewards/comments/vscyfu/us_found_new_daily_points/
https://reddit.com/r/MicrosoftRewards/comments/wn1and/msn_fitness_hyper_optimization_i_aint_got_time_to/

@TatsP
Nice suggestion
Which one is your Fav bot?

@TatsP
I agree that the videos would be really nice, but if your not running this on some sort of external device or server your missing out.
With just a bit of tweaking I got this to run my 5 accounts on a rasberry pi 2, everything works great and all accounts max out on their points every day. 100% automatic also, all I have to do is wait for the gift cards to come rolling in.


Python 3: Package structure and relative imports

I've been looking at Stash's package structure a bit (for the universal branch). I noticed that many modules use implicit relative imports (e. g. stash.py imports system.shcommon, which actually imports stash.system.shcommon) which do not work under Python 3. This is not a big issue, most of these can be replaced with real relative imports (e. g. from .system import shcommon).
The second issue (not directly related to the first one) is that the repo root is the stash package folder, i. e. site-package/stash is the repo root. This means that you have to clone the repo into site-packages/stash, or some imports (for example in launch_stash.py will fail). So it's not possible to have two versions of Stash installed without changing the package name and adjusting imports.
A solution to this would be to move all Stash module files (like stash.py and system) into a stash subfolder, while leaving non-module files in the repo root (like launch_stash.py). This would make installing multiple versions or switching between branches much easier. The launch_stash.py would be in the same folder as the stash package, so when it imports stash it automatically uses the version next to it instead of the one from site-packages.
For normal users nothing would change - if there is no stash package in the same folder as launch_stash.py, it looks through the other module locations, including site-packages. getstash.py would only need some minor modifications to copy the stash folder into site-packages and not the entire repo.

Yes the relative imports need to be fixed. Thanks.
However, having multiple stash installations is actually something I try to avoid. I agree it is useful for development purpose. But for most users, this possibility is more likely to cause confusions, e.g. one may wonder why selfupdate does not work as it is probably updating another version which is not the currently running one.

Yes, that's understandable, users shouldn't install multiple stash instances by accident. However I don't think this change would affect stash installations in site-packages - as long as we change getstash.py to understand the new structure, selfupdate would work the same as before for normal users.
The difference is that with the old structure, when you clone the repo by hand into a different folder, the launch_stash.py in the repo would still use the stash installation in site-packages, and not the one in the cloned repo. With the new structure, launch_stash.py would prefer importing stash from the current directory, and fall back to site-packages if there is no valid stash package next to the launch_stash.py.


Apparent bug on IE11

Hello.
Apparently there is a bug when rendering svgs on IE11. Anyone else can report this?
From my tests I found out that in the defineProperty loop IE11 seems to reject the viewport property.
It appears to be the only property it rejects raising an error. The screenshot below show a hack that just skips that property and then everything works fine including all my preact components and stuff.

I couldn't reproduce this on MS Edge or on any other modern browsers, I didn't test on IE versions prior to 11 though.
The screenshot below shows the IE11 throwing the error in my code:

For now I'm using my hack since it does affect my use case. I don't know exactly if viewport is needed here for other people or how else we should tackle this.

Hi @mkautzmann - great bug report, thank you for the helpful screen captures and context.  One additional detail that would help me diagnose would be the value of el.nodeName at the time of the exception.  If the issue ocurrs on svg nodes themselves, then it's a more difficult fix. If it's being triggered on any other type of element, I can simply add a conditional similar to yours.
Cheers!

el.nodeName is svg at the exception. I'm rendering other elements with preact in the page but IE blocks the rendering on all elements because of this preact-svg bug. It must be something hardcoded in IE that doesn't accept viewport property definition on svg.

@mkautzmann Since most browsers are not affected by this, I think the best solution would be to wrap the property assignment in a try/catch.  It won't be the best for performance, but it will mean viewport can still be adjusted dynamically in 99% of browsers.

@developit Looks fine. I can do that and submit a PR if you find that OK. It may stay around as long as IE11 is relevant. Edge does not have the issue.

That would be awesome, I'll merge and release right away if you have the time.

Fix released in 1.3.0


Support new host logs

Since the build failed (well it is stuck, thanks TravisCI), I've tested it locally. Builds & runs like a charm.


Epic 552 : Decentralize data model

[ ] Make all IDs to be universal

requirement: have the ability to merge databases from different ANET instances

[ ] Add a revision field, possibly a hash of the content

requirement: have drafts/proposals of each data element

[ ] ID + revision should be unique
[ ] design a way to designate which revisions have been approved, through an approval chain similar to reports
[ ] design a way to resolve which revision to use, possibly the most recently approved revision

Requirements

Design an unversal method for handling Entities (Reports, People, Places, Organizations, Positions, etc)
An entity should have a life cycle beyond the data store of its creation. For example, it should be easily moved from one store to another without the need for complex manipulations
Two datastores, with or without a common ancestor should be able to be merged, provided with a conflict resolution strategy, without the need for complex manipulations
A datastore should support non destructive edits

Proposed Approach
Vocabulary

entity - an abstract data structure identified by a uuid
version - a version of an entity is an immutable object instance with the uuid of the entity, a timestamp, a state (draft/published) a SHA-1 hash of the object content, and entity subtype-specific attributes. It is identified by uuid + hash

** published version** - a version that has been approved and can be viewed by the public.
** draft version** - a version that has not yet been approved and is typically only visible to its author and the approving chain

datastore - a collection of entity versions. It can be typically resolved to a consistent graph of the latest versions prior to a point in time - or the current time for the most up to date state.

Data structures
Example of a Person entity
{
    "http://anet.org/entity/uuid": "63ee47c7-b56f-4847-9f91-bd7416d5ee63",
    "http://anet.org/entity/timeStamp": " ",
    "http://anet.org/entity/hash": "64AA9268A1949A76343085A4D6494B5AD5EBE6BE",
    "http://anet.org/entity/state": "published",

    "http://anet.org/person/name": "SMITH, John",
    "http://anet.org/country": "Suburbia",
    "http://anet.org/telephone": "123 3454"
}

Example of a Position entity
{
    "http://anet.org/entity/uuid": "7f778bc2-1f2c-4bf2-95a9-160f1b3fd8ba",
    "http://anet.org/entity/timeStamp": " ",
    "http://anet.org/entity/hash": "64AA9268A1949A76343085A4D6494B5AD5EBE6BE",
    "http://anet.org/entity/state": "published",

    "http://anet.org/position/name": "Director",
    "http://anet.org/position/personRef": "63ee47c7-b56f-4847-9f91-bd7416d5ee63"
}

Possible datastructure technologies

https://json-ld.org/

Semantic behavior

a uuid is generated when a new entity is created
in each datastore, uuid+hash is unique
in each datastore, only one version can exist per published report
old/stale draft versions could either be garbage collected and/or compressed
cached graph of the published entities. An in-memory partial or full cache could be maintained on the client and/or server side (likely partial/lazy on client).

given a point in time, the cache could provide a traversable graph consisting of the most recent published versions prior to that point
given a uuid, the cache could provide the list of versions of that UUID


protoc-gen-swift cannot load SwiftProtobuf library when using SwiftProtobufPlugin in release mode

The plugin works without issue when the build scheme is set to debug mode, but when doing a release build, protoc cannot find SwiftProtobuf when loading protoc-gen-swift:
dyld[57698]: Library not loaded: @rpath/SwiftProtobuf.framework/Versions/A/SwiftProtobuf

The log shows that in debug mode, protoc-gen-swift is compiled with
cd /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/SourcePackages/checkouts/swift-protobuf
    /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -Xlinker -reproducible -target arm64-apple-macos10.13 -isysroot /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk -O0 -w -L/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/EagerLinkingTBDs/Debug -L/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Debug -L/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib -F/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/EagerLinkingTBDs/Debug -F/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Debug/PackageFrameworks -F/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Debug/PackageFrameworks -F/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Debug -F/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks -iframework /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks -filelist /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/SwiftProtobuf.build/Debug/protoc-gen-swift.build/Objects-normal/arm64/protoc-gen-swift.LinkFileList -Xlinker -rpath -Xlinker /usr/lib/swift -Xlinker -rpath -Xlinker /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Debug/PackageFrameworks -Xlinker -object_path_lto -Xlinker /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/SwiftProtobuf.build/Debug/protoc-gen-swift.build/Objects-normal/arm64/protoc-gen-swift_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -fobjc-link-runtime -L/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx -L/usr/lib/swift -Xlinker -add_ast_path -Xlinker /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/SwiftProtobuf.build/Debug/protoc-gen-swift.build/Objects-normal/arm64/protoc_gen_swift.swiftmodule -Wl,-no_warn_duplicate_libraries -Wl,-no_warn_duplicate_libraries -framework SwiftProtobuf -framework SwiftProtobufPluginLibrary -Xlinker -dependency_info -Xlinker /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/SwiftProtobuf.build/Debug/protoc-gen-swift.build/Objects-normal/arm64/protoc-gen-swift_dependency_info.dat -o /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Debug/protoc-gen-swift

But in release mode, it misses the rpath argument:
/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -Xlinker -reproducible -target arm64-apple-macos10.13 -isysroot /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk -Os -w -L/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/EagerLinkingTBDs/Release -L/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Release -L/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib -F/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/EagerLinkingTBDs/Release -F/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Release/PackageFrameworks -F/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Release/PackageFrameworks -F/Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Products/Release -F/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks -iframework /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks -filelist /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/SwiftProtobuf.build/Release/protoc-gen-swift.build/Objects-normal/arm64/protoc-gen-swift.LinkFileList -Xlinker -rpath -Xlinker /usr/lib/swift -Xlinker -object_path_lto -Xlinker /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/SwiftProtobuf.build/Release/protoc-gen-swift.build/Objects-normal/arm64/protoc-gen-swift_lto.o -Xlinker -debug_variant -fobjc-link-runtime -fprofile-instr-generate -L/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx -L/usr/lib/swift -Xlinker -add_ast_path -Xlinker /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/SwiftProtobuf.build/Release/protoc-gen-swift.build/Objects-normal/arm64/protoc_gen_swift.swiftmodule -Wl,-no_warn_duplicate_libraries -Wl,-no_warn_duplicate_libraries -framework SwiftProtobuf -framework SwiftProtobufPluginLibrary -Xlinker -dependency_info -Xlinker /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/SwiftProtobuf.build/Release/protoc-gen-swift.build/Objects-normal/arm64/protoc-gen-swift_dependency_info.dat -o /Users/test/Library/Developer/Xcode/DerivedData/PaperPilot-cyqhgfgkjjzzwchgmxwnwngxtkbw/Build/Intermediates.noindex/SwiftProtobuf.build/Release/protoc-gen-swift.build/Objects-normal/arm64/Binary/protoc-gen-swift

I can reproduce this on Xcode 15.0 and 15.1 beta, with swift-protobuf 1.25.1.

Since we haven't gotten any other reports, I'm guessing this is something unique to your set up?  Can you provide more detailed information about you builds?  Given the snippets you included, it doesn't sound like you are using SwiftPM to build the plugin?  What are the exact steps you are using?  Then someone might have some ideas.

I'm just using the spm-plugin in Xcode following the instructions outlined in Sources/protoc-gen-swift/Docs.docc/spm-plugin.md.

This sounds like an SPM/Xcode problem. Would you mind filing a feedback using the feedback assistant and share the feedback number with me. I don't think there is anything that SwiftProtobuf can do here.

I'm a collaborator with MikeWalrus. I have submitted the feedback FB13402398.

It looks like you are building SwiftProtobuf into an a framework. I assume this is where this problem comes from. Make sure to attach a reproducer Xcode project to your feedback.

I'm running into the very same problem, it doesn't seem to be that unique.

Closing this since it seems the issues here are with Xcode's SwiftPM support and nothing we can do on this project.

For me this disappeared after reducing the dependencies inside the project to a minimum, i.e. avoiding to depend on Protobuf (or GRPC) multiple times

I can confirm that this issue still exists and my solution for it still works (came here as I had the issue on another project)


Add no-autoplay rule

Pull Request purpose
[ ] Documentation update
[ ] Bug fix
[X] New rule
[ ] Updates an existing rule
[ ] Add something to the core
[ ] Other, please explain:
Checklist
[ ] Update CHANGELOG.md
[ ] Update task status in release plan (README)
[ ] Docs added (/docs/rules/<rule_name>)
[ ] Docs ready to be added to website (ec0lint.com)

Overview of changes
Would you like to add anything more?

Changes look good, please do:

delete Fuzz Test from pipeline definition
(minor update) change log message 'youtube' -> 'YouTube'
confirm with Kasia the log message


Movie Set graphics Removed

tmm_logs3.zip
tmm_logs2.zip

Version: 2.9.1
Build: 2016-12-12 17:48
OS: Windows 7 6.1
JDK: 1.8.0_60 x86 Oracle Corporation
What is the actual behaviour?
Program removes graphics MovieSet
Description

I set the path to the movies,
loading information,
I write graphic movieset and add description (example: Ace Ventura Collection),
I change the name of the collection (example: Ace Ventura Kolekcja),
Finished.
Then changed the name of the folder with movies or I move them and I set a new path to the movies in the program,
I scan path movie,
and they are removed graphics movieset (movieset-fanart.jpg, movieset-poster.jpg) (deleted from the disk completely),
movieset-logo.png, movieset-banner.jpg, movieset-clearart.png replace files logo.png, clearart.png (change the extension to .jpg)
does not show ID movieset - in view Movie sets

there was a problem with keeping movieset-logo and movie logo separated (worked only for poster and fanart).
Should work in the next version (or nightly build tomorrow if you want to test it)

Hello
far nothing has changed. did not work

do you run the nightly build?
because we did not have any release since mid december

Yes - last version
version=2.9.2-SNAPSHOT
build=nightly
date=2017-01-12 00:02

could you please update to the latest build?
the movieset-* files should disappear from the list and should not being renamed with the movie
also a new update datasources should not bring these files back to the movie in the list (but should stay on the disk)

Hi
It looks like it works when it comes to movieset-banner, clearlogo, logo etc. :)
But deletes from disk movieset-poster and movieset-fanart. as I described earlier.

now I see your point.
The movieset-* artwork get deleted, when the movie gets disconnected from the movie set inside tmm (cleanup).
We won't keep movieset artwork inside the movie folder if the movie is not in a movieset.
When you move your movies around, you somehow break the connection to the movie set and this is the case tmm triggers the cleanup

I think just the opposite
Now all files are deleted movieset- *
Movies are still in collections, sometimes need to move folders to another location, and reload the Tiny Media Manger - and that's when files are removed movieset- * (!!! so I do not want !!!)
I want to make movies still have a graphics movieset. I do not change the information in the movies - only I move them to another location.
sorry for poor English, it can cause confusion
renamed movieset-* OK :)

your workflow works here for me..
do you delete the movie from tmm prior to moving? (this would break the connection!)

No, I no delete movies from TMM.
Deleting path of movies (Collections) of TMM, I move folder to another location (or changing the name of the root folder).
I set a new path for these movies in TMM and update data sources - and HERE removes graphics movieset- * , and removes TMDBset id in the view Movie Sets
I do not change in the .nfo - movies, and I still want to have in the collection
Maybe I did not write that - movieset artwork in the store each movie folders
P.S.
The first part of the query is OK - rename movieset graphics :)
so we leave - it works.
I'm sorry - I help myself translator :)
tmm_logs.zip

okay, if i get you right, you remove the datasource from the settings, movie the movies to another location, add this location to the movie datasources and update after that?
removing a datasource also removes all movies inside it from tmm -> breaking movie set connection..
btw: movie sets (and their set tmdb id) should never be dropped from tmm unless you delete the movieset

Ok

"[remove the datasource from the settings, move the movies to another location, add this location to the movie datasources and update after that?]" YES
"[removing a datasource also removes all movies inside it from tmm -> breaking movie set connection.]" YES
"[movie sets (and their set tmdb id) should never be dropped from tmm unless you delete the movieset]"
I not removed movie sets,
remove datasource does not delete graphics movieset- * and TMDb id,
removes graphics movieset- * and TMDb id makes Update datasource

Sample folder structure:
Folder root.txt
I hope that clearly written :)

I've changed the cleanup logic that it is only triggered, when you manually remove the movie from the movie set;
If you remove the movie from tmm (DEL button or remove a data source) then there is no more cleanup!
the newest nightly should work as you desire

Great, PERFECT.  :1st_place_medal:
Thanks a lot


Needs Update for 9.93 JSS

Due to changes in the 9.93 JSS, the tool is unable to get the JSS Summary. This cases an index out of bounds exception and crashes the tool.

Fixed in commit 05062787a4d8e1b96b0da69b36f36984d87bdf91.


Add C++ model generation support

Reason/Context
Now that Modelina supports C++ model generation, we need to add support for it in the CLI.
To do this:

Add the language (cplusplus) to the list of languages: https://github.com/asyncapi/cli/blob/c2b5cb38ce9fb544139a6fab2da6a5639d018e29/src/commands/generate/models.ts#L9
Add a new switch entry as we have for JavaScript: https://github.com/asyncapi/cli/blob/c2b5cb38ce9fb544139a6fab2da6a5639d018e29/src/commands/generate/models.ts#L209
Add a new test case for the new language: https://github.com/asyncapi/cli/blob/c2b5cb38ce9fb544139a6fab2da6a5639d018e29/test/commands/generate/models.test.ts#L73
Add a required namespace option

Can i pick it up ? @jonaslagoni

Please do @kaushik-rishi 🙂

/gfi ts

@jonaslagoni linked pr #575