nerfstuidio not found

I have installed the neurad-studio as required. However, when I try to train the model, it gives me:
python nerfstudio/scripts/train.py neurad pandaset-data --data /mnt/ssd/xxx/data/pandaset/
Traceback (most recent call last):
File "/mnt/ssd/xxx/neurad-studio/nerfstudio/scripts/train.py", line 69, in
from nerfstudio.configs.method_configs import AnnotatedBaseConfigUnion
File "/mnt/ssd/xxx/neurad-studio/nerfstudio/configs/method_configs.py", line 28, in
from nerfstudio.cameras.camera_optimizers import CameraOptimizerConfig, ScaledCameraOptimizerConfig
File "/mnt/ssd/xxx/neurad-studio/nerfstudio/cameras/camera_optimizers.py", line 32, in
from nerfstudio.cameras.cameras import Cameras
File "/mnt/ssd/xxx/neurad-studio/nerfstudio/cameras/cameras.py", line 31, in
import nerfstudio.utils.math
File "/mnt/ssd/xxx/neurad-studio/nerfstudio/utils/math.py", line 27, in
from nerfstudio.data.scene_box import OrientedBox
ModuleNotFoundError: No module named 'nerfstudio.data.scene_box'
Am I missing some steps during the setup? I am running at the root folder of /mnt/ssd/xxx/neurad-studio.
Any help is appreciated. Thanks in advance.

Maybe you have missed the installation of the neurad-package iself ?
Install neurad: After cloning the repo make sure you install it:
git clone https://github.com/georghess/neurad-studio.git
cd neurad-studio
pip install --upgrade pip setuptools
pip install -e .

Make sure you verify the installation steps from the README.md:

Create conda environement: https://github.com/georghess/neurad-studio?tab=readme-ov-file#create-environment
Install dependencies: https://github.com/georghess/neurad-studio?tab=readme-ov-file#dependencies
Install neurad: https://github.com/georghess/neurad-studio?tab=readme-ov-file#installing-neurad

Very interestingly, I found that I cannot properly install it using python 3.8. I switched to python 3.10 and everything installed properly. But for py3.10 the .toml didn't work properly, maybe its my conda problem. Thx anyways.


Is test_general_signal timing sensitive?

I am building and running tests of sh on nixpkgs on a high load machine and was wondering if it is possible that the following test failure is caused by a timing issue:
Sourcing python-remove-tests-dir-hook
Sourcing python-catch-conflicts-hook.sh
Sourcing python-remove-bin-bytecode-hook.sh
Sourcing pip-build-hook
Using pipBuildPhase
Using pipShellHook
Sourcing pip-install-hook
Using pipInstallPhase
Sourcing python-imports-check-hook.sh
Using pythonImportsCheckPhase
Sourcing python-namespaces-hook
Sourcing python-catch-conflicts-hook.sh
Sourcing pytest-check-hook
Using pytestCheckPhase
unpacking sources
unpacking source archive /nix/store/v6hbjcc5ay3694bg19zjbhrn00f7k2rj-source
source root is source
setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/tox.ini
patching sources
configuring
no configure script, doing nothing
building
Executing pipBuildPhase
Creating a wheel...
WARNING: The directory '/homeless-shelter/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Processing /build/source
  Running command Preparing metadata (pyproject.toml)
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: sh
  Running command Building wheel for sh (pyproject.toml)
  Building wheel for sh (pyproject.toml) ... done
  Created wheel for sh: filename=sh-2.0.2-py3-none-any.whl size=38306 sha256=a8999ec9f4a529fcdabf23c8f1c1c3601214e1321ea6e315e1e5de16518f3b68
  Stored in directory: /build/pip-ephem-wheel-cache-dqfr9hiu/wheels/79/4b/9b/fc24941d75fdb959a71ee80195b2c89d6ae9389f9f0f80fb22
Successfully built sh
Finished creating a wheel...
Finished executing pipBuildPhase
installing
Executing pipInstallPhase
/build/source/dist /build/source
Processing ./sh-2.0.2-py3-none-any.whl
Installing collected packages: sh
Successfully installed sh-2.0.2
/build/source
Finished executing pipInstallPhase
pythonOutputDistPhase
Executing pythonOutputDistPhase
Finished executing pythonOutputDistPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/dfqsl7x199hx8icr0q08fhkc9gwm4vb6-python3.10-sh-2.0.2
checking for references to /build/ in /nix/store/dfqsl7x199hx8icr0q08fhkc9gwm4vb6-python3.10-sh-2.0.2...
patching script interpreter paths in /nix/store/dfqsl7x199hx8icr0q08fhkc9gwm4vb6-python3.10-sh-2.0.2
stripping (with command strip and flags -S -p) in  /nix/store/dfqsl7x199hx8icr0q08fhkc9gwm4vb6-python3.10-sh-2.0.2/lib
shrinking RPATHs of ELF executables and libraries in /nix/store/zv50w2zg49nimk3mcpa9hs6bxdmcn867-python3.10-sh-2.0.2-dist
checking for references to /build/ in /nix/store/zv50w2zg49nimk3mcpa9hs6bxdmcn867-python3.10-sh-2.0.2-dist...
patching script interpreter paths in /nix/store/zv50w2zg49nimk3mcpa9hs6bxdmcn867-python3.10-sh-2.0.2-dist
Executing pythonRemoveTestsDir
Finished executing pythonRemoveTestsDir
running install tests
no Makefile or custom installCheckPhase, doing nothing
pythonCatchConflictsPhase
pythonRemoveBinBytecodePhase
pythonImportsCheckPhase
Executing pythonImportsCheckPhase
pytestCheckPhase
Executing pytestCheckPhase
============================= test session starts ==============================
platform linux -- Python 3.10.11, pytest-7.2.1, pluggy-1.0.0
rootdir: /build/source
collected 178 items / 4 deselected / 174 selected

tests/test.py ...F...................................................... [ 33%]
................................................s....................... [ 74%]
............................................                             [100%]

=================================== FAILURES ===================================
_____________________ FunctionalTests.test_general_signal ______________________

self = <tests.test.FunctionalTests testMethod=test_general_signal>

        def test_general_signal(self):
            from signal import SIGINT

            py = create_tmp_test(
                """
    import sys
    import os
    import time
    import signal

    i = 0
    def sig_handler(sig, frame):
        global i
        i = 42

    signal.signal(signal.SIGINT, sig_handler)

    for _ in range(6):
        print(i)
        i += 1
        sys.stdout.flush()
        time.sleep(1)
    """
            )

            stdout = []

            def agg(line, stdin, process):
                line = line.strip()
                stdout.append(line)
                if line == "3":
                    process.signal(SIGINT)
                    return True

            p = python(py.name, _out=agg, _tee=True)
            p.wait()

            self.assertEqual(p.process.exit_code, 0)
>           self.assertEqual(str(p), "0\n1\n2\n3\n42\n43\n")
E           AssertionError: '0\n1\n2\n3\n43\n44\n' != '0\n1\n2\n3\n42\n43\n'
E             0
E             1
E             2
E             3
E           + 42
E             43
E           - 44

tests/test.py:1672: AssertionError
=============================== warnings summary ===============================
tests/test.py::FunctionalTests::test_unchecked_pipeline_failure
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread background thread for pid 290

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2656, in background_thread
      handle_exit_code(exit_code)
    File "/build/source/sh.py", line 2347, in fn
      return self.command.handle_command_exit_code(exit_code)
    File "/build/source/sh.py", line 838, in handle_command_exit_code
      raise exc
  sh.ErrorReturnCode_2:

    RAN: /nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/bin/python3.10 /build/tmpp6a_vkid

    STDOUT:

    STDERR:

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

tests/test.py::FunctionalTests::test_exit_code_with_hasattr
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread background thread for pid 452

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2656, in background_thread
      handle_exit_code(exit_code)
    File "/build/source/sh.py", line 2347, in fn
      return self.command.handle_command_exit_code(exit_code)
    File "/build/source/sh.py", line 838, in handle_command_exit_code
      raise exc
  sh.ErrorReturnCode_3:

    RAN: /nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/bin/python3.10 /build/tmpvaqcl0bf

    STDOUT:

    STDERR:

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

tests/test.py::FunctionalTests::test_signal_exception
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread background thread for pid 581

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2656, in background_thread
      handle_exit_code(exit_code)
    File "/build/source/sh.py", line 2347, in fn
      return self.command.handle_command_exit_code(exit_code)
    File "/build/source/sh.py", line 838, in handle_command_exit_code
      raise exc
  sh.SignalException_SIGTERM:

    RAN: /nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/bin/python3.10 /build/tmp17rt4bv1

    STDOUT:

    STDERR:

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

tests/test.py::FunctionalTests::test_stdout_callback_kill
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread background thread for pid 661

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2656, in background_thread
      handle_exit_code(exit_code)
    File "/build/source/sh.py", line 2347, in fn
      return self.command.handle_command_exit_code(exit_code)
    File "/build/source/sh.py", line 838, in handle_command_exit_code
      raise exc
  sh.SignalException_SIGKILL:

    RAN: /nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/bin/python3.10 -u /build/tmpeit9x7_h

    STDOUT:

    STDERR:

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

tests/test.py::FunctionalTests::test_stdout_callback_terminate
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread background thread for pid 701

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2656, in background_thread
      handle_exit_code(exit_code)
    File "/build/source/sh.py", line 2347, in fn
      return self.command.handle_command_exit_code(exit_code)
    File "/build/source/sh.py", line 838, in handle_command_exit_code
      raise exc
  sh.SignalException_SIGTERM:

    RAN: /nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/bin/python3.10 -u /build/tmp_s9j1itv

    STDOUT:

    STDERR:

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

tests/test.py::FunctionalTests::test_fg_alternative
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread STDIN thread for pid 716

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2606, in input_thread
      done = stdin.write()
    File "/build/source/sh.py", line 2919, in write
      chunk = self.get_chunk()
    File "/build/source/sh.py", line 2860, in fn
      chunk = stdin.read(bufsize)
    File "/nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/capture.py", line 192, in read
      raise OSError(
  OSError: pytest: reading from stdin while output is captured!  Consider using `-s`.

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

tests/test.py::FunctionalTests::test_signal_group
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread background thread for pid 731

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2656, in background_thread
      handle_exit_code(exit_code)
    File "/build/source/sh.py", line 2347, in fn
      return self.command.handle_command_exit_code(exit_code)
    File "/build/source/sh.py", line 838, in handle_command_exit_code
      raise exc
  sh.SignalException_SIGKILL:

    RAN: /nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/bin/python3.10 /build/tmpbfannjvz

    STDOUT:
  735
  731

    STDERR:

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

tests/test.py::FunctionalTests::test_unchecked_producer_failure
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread background thread for pid 757

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2656, in background_thread
      handle_exit_code(exit_code)
    File "/build/source/sh.py", line 2347, in fn
      return self.command.handle_command_exit_code(exit_code)
    File "/build/source/sh.py", line 838, in handle_command_exit_code
      raise exc
  sh.ErrorReturnCode_2:

    RAN: /nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/bin/python3.10 /build/tmpssifhe90

    STDOUT:

    STDERR:

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

tests/test.py::FunctionalTests::test_tty_tee
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread background thread for pid 740

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2656, in background_thread
      handle_exit_code(exit_code)
    File "/build/source/sh.py", line 2347, in fn
      return self.command.handle_command_exit_code(exit_code)
    File "/build/source/sh.py", line 838, in handle_command_exit_code
      raise exc
  sh.SignalException_SIGKILL:

    RAN: /nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/bin/python3.10 /build/tmpbfannjvz

    STDOUT:
  744
  740

    STDERR:

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

tests/test.py::FunctionalTests::test_done_cb_exc
  /nix/store/agawdr80hxrmhm2gcqvzs6z4s06qabby-python3.10-pytest-7.2.1/lib/python3.10/site-packages/_pytest/threadexception.py:73: PytestUnhandledThreadExceptionWarning: Exception in thread background thread for pid 772

  Traceback (most recent call last):
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
      self.run()
    File "/nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/lib/python3.10/threading.py", line 953, in run
      self._target(*self._args, **self._kwargs)
    File "/build/source/sh.py", line 1654, in wrap
      fn(*rgs, **kwargs)
    File "/build/source/sh.py", line 2656, in background_thread
      handle_exit_code(exit_code)
    File "/build/source/sh.py", line 2347, in fn
      return self.command.handle_command_exit_code(exit_code)
    File "/build/source/sh.py", line 838, in handle_command_exit_code
      raise exc
  sh.ErrorReturnCode_1:

    RAN: /nix/store/fhzv25qmq4jsfwddq2dslf4mcqpkk15w-python3-3.10.11/bin/python3.10 /build/tmpv6u2nrxi

    STDOUT:

    STDERR:

    warnings.warn(pytest.PytestUnhandledThreadExceptionWarning(msg))

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================
FAILED tests/test.py::FunctionalTests::test_general_signal - AssertionError: '0\n1\n2\n3\n43\n44\n' != '0\n1\n2\n3\n42\n43\n'
= 1 failed, 172 passed, 1 skipped, 4 deselected, 10 warnings in 81.04s (0:01:21) =
/nix/store/4np3l3m41jjv0ig04v3f0gbilj6j38k0-stdenv-linux/setup: line 1596: pop_var_context: head of shell_variables not a function context

There are a few tests that have timing issues inherent to process launching/flushing/exiting. Not sure if that one is, but it's possible.

Also ran into this in CI. Unfortunately the project is internal, but I got the exact same test result diff.


Port unitary synthesis to rust

What should we add?
For level 3 compilation now, the unitary synthesis as part of the 2q block optimization becomes a large bottleneck since we've moved layout and routing mostly to multithreaded rust code. To look at further speeding this up we should look at whether we can accelerate the numeric component of:
https://github.com/Qiskit/qiskit-terra/blob/main/qiskit/quantum_info/synthesis/two_qubit_decompose.py
and
https://github.com/Qiskit/qiskit-terra/blob/main/qiskit/quantum_info/synthesis/one_qubit_decompose.py
by moving it to rust.  For things that are already in vectorized numpy functions the performance gains may not be that big. The other constraint is that linear algebra functions that depend on blas we'll probably still want to call to numpy (likely via python since the numpy c api doesn't expose a lot of the linalg functions which leverage blas) since we don't want the complexity of linking the rust binary against blas at build time.
I'm not actually sure how much it'll speed things up since I expect a large chunk of time is spent building circuits and manipulating them. Moving the numeric portion of the modules to rust won't really change because the circuit side is in python space and rust can't really accelerate those portion of the modules. This effort is not necessarily going to turn out to be worth it, but we can't really know until we give it a try.

One thought I did have is that we could do some of the work in parallel if we allow the synthesis function to take a list of unitaries as an input we can process them in parallel and then just loop over the results to build the circuits. Even if the evaluation doesn't get much faster by moving to rust doing multiple things in parallel can still provide a good speedup.

The internals have quite a bit of intermediate numpy array creation and numerical operations. There is likely gains to be had by removing those. Not sure how big that is in the grand scheme of things though

Many of the vectorized numpy functions involve small vectors and matrices, with linear dimensions like 2 or 4. Often the python overhead for numpy calls dominates for these calculations.

It's worth pointing out since I originally opened this issue I was able to find some benefit to using Rust for the circuit construction too in the 1q decomposer in: https://github.com/Qiskit/qiskit-terra/pull/9578 and https://github.com/Qiskit/qiskit-terra/pull/9583 so we probably could follow a similar pattern if porting the 2q decomposer too.

The importance of this has risen a bit, after #8779 was fixed by https://github.com/Qiskit/qiskit/pull/10365 and #10467 we're not definitely bottlenecked on the performance of UnitarySynthesis when using optimization level 3 (along with commutative analysis performance).


Missing source download for <IP_ADDRESS> on download.arongodb.com

https://download.arangodb.com/Source/ArangoDB-<IP_ADDRESS>.tar.gz

3.7 is not released yet as you also found out. Closing.


New CSS style blocks top half of the page

Your new CSS has made your service unusable. The top 1-3 paragraphs of the page are no longer visible, depending on screen size.
This is a very simple CSS fix, but when I submitted a bug report, I was told it was my fault by employees that appear to be trying to cover their own asses.
It is not my fault. It is a very simple CSS problem that you've introduced in your new styles. The page needs to expand downwards as the menu up top expands. Somewhere, someone inexperienced in CSS has made an alteration to your framework so that this no longer works.
I've removed my documentation from your site.  It's obvious what has happened to anyone that has spent 20 minutes working on a website, and it's not my Markdown or YAML, which have nothing to do with CSS.

@earth-tone, I'm going to use this time to remind you of the Read the Docs code of conduct.

Please choose your words more carefully and be respectful. Read the Docs is a free service with some full time people and some volunteers but insulting folks is not going to get them to help you with your problem.
Members of Read the Docs tried to help you and you disagreed with what they said (I believe they are correct FWIW). When you disagreed, you specifically said "are you retarded?". This is unacceptable. Specifically this violates the part of our code of conduct around "be considerate", "be respectful" and "be careful of the words you choose".
If this behavior continues, we will take further action.

I'm going to close this issue. If you'd like help, please feel free to open a new issue where you treat Read the Docs contributors and employees with respect.


using last broker version 5.0.3

using last broker version 5.0.3
adding postgre persistence for connector A
using new last connector version 8.0.2
adding UI (user interface) for connectors with las DataspaceConnectorUI version
modified postman colection to take into account how to register a broker into connector
unregister broker in connector FAIL for connector (version 7.1.0 and 8.0.2) and broker (version 5.0.0 and 5.0.3)

Thank you for your pull request @aramirezarsys!
I have mentioned your proposal with the IDSA Technical Steering Committee and in the meeting all your pull request points were discussed:

MetadataBroker update to version 5.0.3 was approved.
Dataspace Connector update to version 8.0.2 was approved.
Adding PostgreSQL database persistence for connectors was approved.
Adding User Interface has been established as a functionality that does not affect the execution of the Testsuite or the execution of test cases. For this reason, it has not been accepted to be implemented at the IDS-testbed repository.
It will be further discussed the update at the postman collection regarding internal Broker registration at the connector.
The issue unregister to Metadatabroker has been notified to the developers of the component.

I have used your pull request to generate a new one with the changes approved by IDSA technical steering committee.
You can find it here #103.

Thanks for the input.
All the approved points are collected at Component update (DSC and MDB) to new versions pull request.
Please review this pull request #103 and provide feedback there.


Add [wip] work for item filter params

Move param parsing to controller
Add param parsing of comma-delimited and ranged parameter values
Incomplete support for filtering by item date and volume
Merge test/utils.test.js into test/util.test.js

https://jira.nypl.org/browse/SCC-3104

going to post another PR for these changes


Add meetups 71 and 72

Can you also remove the starting double h from GitHubLink at UI/UX meetup ? I just noticed that :-)

Can you also remove the starting double h from GitHubLink at UI/UX meetup ? I just noticed that :-)

We should create a new ticket for this, but for the lest time I can do it! 😄


Fix x64_mingw_24. Typo in PR #5170

@homu r+

:pushpin: Commit 9837143 has been approved by segiddins

:hourglass: Testing commit 9837143 with merge 6e0dcf4...

:sunny: Test successful - status


Issue with ShadowErrors, VS2017 and Status Bar

I'm getting Error that VS2017 must be installed, while I do have VS2017 and VS2019. Not sure why it's not detecting it.
This is the command line:
BuildGraph -target="Make Installed Build Win64" -script="D:\Epic Games\UE_Source\UnrealEngine\Engine\Build\InstalledEngineBuild.xml" -set:WithDDC=false -set:SignExecutables=false -set:EmbedSrcSrvInfo=false -set:GameConfigurations=Development;Shipping -set:WithFullDebugInfo=false -set:HostPlatformEditorOnly=false -set:AnalyticsTypeOverride= -set:WithWin64=true -set:WithWin32=true -set:WithMac=false -set:WithAndroid=false -set:WithIOS=false -set:WithTVOS=false -set:WithLinux=false -set:WithLumin=false -set:WithLinuxAArch64=false -set:CompileDatasmithPlugins=false -set:VS2019=false -set:WithServer=false -set:WithClient=false -set:WithHoloLens=false
I'm getting these errors :

SharedPCH.Core.ShadowErrors.cpp
SharedPCH.CoreUObject.ShadowErrors.cpp
SharedPCH.CoreUObject.RTTI.ShadowErrors.cpp
SharedPCH.UnrealEd.NoOptimized.RTTI.ShadowErrors.NoUndef.cpp
SharedPCH.Core.ShadowErrors.NoUndef.cpp
SharedPCH.UnrealEd.NoOptimized.ShadowErrors.cpp
SharedPCH.Engine.NoOptimized.ShadowErrors.cpp
SharedPCH.Slate.ShadowErrors.cpp
SharedPCH.UnrealEd.RTTI.ShadowErrors.cpp
SharedPCH.UnrealEd.ShadowErrors.cpp
SharedPCH.Engine.ShadowErrors.cpp
Something with ShadowErrors, any idea why?

fyi, I'm trying to build Chaos, so I edited the BuildEnvironment = TargetBuildEnvironment.Shared; to BuildEnvironment = TargetBuildEnvironment.Unique; and added bCompileChaos = true; and bUseChaos = true; to the UE4Editor.Target.cs. (That's since that's what unreal documentation required.), is this causing the ShadowErrors errors?
...also I'm not sure what's going on at the status bar, probably need to give it some space or open a new window.

...and the last thing, regarding your documentation ("How to use").
"Copy the built binary to the UE4 source folder prepared above."
after I built it, I copy the release folder in the bin folder and pasted it in the unreal source code directory, where GenerateProjectFiles.bat exists, am I doing it right?

@Bernardrouhi
1: UE4 uses 2017 compiler by default so you will need to enable 2019 compiler option to use 2019 compiler.
2: Those errors you mentioned are not errors actually. The program just detects them as errors because of some regex expression.
3: I wasn't aware of the text overlapping. Thanks for pointing it out. I will fix it in next update.

@ryanjon2040
Okay, I tried building it again with VS2019, now I'm getting this
AutomationException: Attempt to add file to temp storage manifest that does not exist (D:\Epic Games\UE_Source\UnrealEngine\cpp.hint)

Any idea what cpp.hint is?
...also Is there anyways to build it faster? (3 hours+)

@Bernardrouhi
That is a strange error. Never seen it before. I would advice posting it on the forums. cpp.hint is a hint file.
The build time depends on the PC itself. Faster CPU + SSD should build faster.

@ryanjon2040
Thanks for the reply, alright, I'll post that on their forum.

@Bernardrouhi I'll close this issue for now since its not related to this application.

Apparently, it's a bug in 4.25.4, and it's fixed in version 4.26 here is the snapshot of the git repo.

I remove line 520 and compile it again, and it did compile successfully. (thought to share that here)

Thank you so much for letting me know. I only tried on 4.25.3.


outdated lodash - improving performance

There is a newer version of lodash (3.3.1) which  improved performance 20-40% overall  by better utilizing the JIT in JavaScript engines, using internal helper functions that avoid optimization disqualifications & increase the likelihood of function inlining.
lodash 3.0.0 is 40%  (1.40x) faster than lodash 2.4.1.
In v3 also introduced were lazily evaluated chaining for massive performance wins in certain scenarios.
Any change to update to the latest release?

+1.

Closing in favor of #1410


Better visibility of behavior for users that don't have a public email

The plugin will only use a user's name and email from GitHub if they are public, as previously described. In the case that [notification] always_notify_updater is true, users with a public email in their GitHub profile will receive notifications, whereas users without a public email in their GitHub profile will not unless they have explicitly set their email address in their Preferences. For the jQuery Trac sites we'd like to make the behavior more consistent, or at least more explicit. Therefore, I've considered the following and would like to get some feedback on whether you think one or both is a good idea:

Add a notice on login for a user that doesn't have a public email address in their GitHub profile. The notice would be something like: You will not receive email notifications unless you set your email address in preferences [x] (with preferences being a link to /prefs and [x] being a dismiss button). The notice could persist on every page until the name and email are set, or until the notice is explicitly dismissed (AccountManagerPlugin has similar behavior for verification of emailed registration tokens).
Allow users with a private name and email in their GitHub profile to explicitly opt-in to having their name and email set in Trac preference data (is it even possible?).

You can ask for the user:email scope to get access to the private email.
However I'm not sure GitHub's UI lets you decline that scope and still proceed with the login.
What about making that a configuration option of the plugin?

What about making that a configuration option of the plugin?

Yeah, I think a configuration option is a good idea.
I'll investigate this coming weekend and propose one or more pull-requests.

The configuration options to request the user:email scope is now merged with #105. Do you want to keep this open to track implementing the notification behavior you outlined above?

However I'm not sure GitHub's UI lets you decline that scope and still proceed with the login.

It looks like GitHub does not let you decline the scope and proceed with the login. I tested 2.3dev after making my email address private and with [github] request_email set to True:

Do you want to keep this open to track implementing the notification behavior you outlined above?

As for the other idea, of adding a notice, it might be more appropriate to add the behavior to Trac. I'll discuss with the team that requested the behavior and reply back here.

See also Trac #12165. Sounds like [github] request_email will be good enough for the jQuery UI site. Thanks for implementing!


Core Version & Element Modules - unable to inject module style urls

Check that this is really a bug

[X] I confirm

Reproduction link
https://stackblitz.com/edit/swiper-element-module-styles?file=app.vue,components%2FBaseImageSlider.vue
Bug description
I am using Swiper element (web component) version as described here: https://swiperjs.com/element
I would like to use Core module + modules to only add the modules i really use. For performance reasons.
So i tried to follow the instructions here: https://swiperjs.com/element
Regarding the docs these module style url injects should be possible:
injectStylesUrls: [
      'swiper/element/css/a11y',
      'swiper/element/css/keyboard',
      'swiper/element/css/navigation',
      'swiper/element/css/mousewheel',
    ],

But it does not work. No matter which export urls i try. it does not get applied.
Expected Behavior
Style url inject of the module styles should work
Actual Behavior
Not working. No styles applied
Swiper version
11.1.1
Platform/Target and Browser Versions
macOS Google Chrome Version 123.0.6312.107 (Offizieller Build) (arm64)
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

You need correct paths for styles

@nolimits4web first of all, thanks for creating the wonderful library.
In a project, we're trying to migrate from Swiper React to Elements, and I second @awacode21 comments, the documentation does not provide enough clarity on what to do. My code is almost exactly as documented here but this part of the documentation is a bit vague:

we also need to add modules styles globally and also inject modules styles to the shadow DOM

Does "add modules styles globally" mean import "swiper/element/css/pagination" in the context of a React app?
Does "inject modules styles to the shadow DOM" mean injectStylesUrls: ["swiper/element/css/pagination"]?
If not, how can we inject the existing styles provided by the package (i.e. stylesheets that already exist like node_modules/swiper/modules/pagination-element.min.css)?

Thanks for the response.


How to create "Codable Types" table

I craete a model calss like this:
class SRModel: NSObject,Codable {
    var uid:Int64 = 0
    var name:String?
}

but I can't crate table

You still have to create the table manually:
https://github.com/stephencelis/SQLite.swift/blob/master/Documentation/Index.md#creating-a-table


allow folders with suffix ".swift" in a package's root folder

I created a swift library with the unfortunate name "progress.swift". To support cocoa pods i added an Xcode project in a subfolder named "Progress.swift".
As a result i got the following error message: Your source structure is not supported due to invalid sources layout: .../Packages/Progress.swift-0.1.4. There should be no source files under: .../Packages/Progress.swift-0.1.4. when trying to build it.
This pull request should fix the issue.

It would be better if a test could be added for this.

I added a new fixture & test to verify it.
Might be to much overhead for such a simple fix.

LGTM! 👌


feat(glossary): add ability to clone glossary term(name and documentation) from term profile menu

Add ability to clone Glossary Term by using "Clone" button in term's profile menu. After cloning, user is redirected to new entity's profile page.
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@chriscollins3456 This PR can be closed, cause we changed origin. We can continue discussion in https://github.com/datahub-project/datahub/pull/9445. I also implemented made suggested changes. Thanks!


ENHANCEMENT: Add caching to InheritedPermissions

Do not merge
Until https://github.com/silverstripe/silverstripe-framework/pull/7673 is merged!
Adds backend caching to InheritedPermissions, e.g. canEditMultiple().
Resolves https://github.com/silverstripe/silverstripe-framework/issues/7442

4 branch, please

Rebased on 4 now that the prior PR is merged.
@unclecheese I've added a separate commit with what I think is PROBABLY an improvement. Feel free to comment if you want to have a say. :)

Can be merged on green:  But don't forget https://github.com/silverstripe/silverstripe-assets/pull/102 and https://github.com/silverstripe/silverstripe-cms/pull/2045 if you merge this.

Fixed linting issues.


Oracle JDK 8 does not work

The documentation is easy to mis-read for the java requirements. The link to Java takes you to Azul JDK (Open JDK) but the link just says Java JDK 8. I interpreted that to mean that Oracle Java JDK 8 was ok also. When using the Oracle JDK mvn deploy will throw the following cryptic error :
The server encountered an unknown failure: : sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target -> [Help 1]
Using Open JDK 8 or Azul JDK 8 works fine. I suggest updating the doc to clarify this point.
thx

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

ID: e656bde5-b5d8-8d80-b7b3-ab430e57613e
Version Independent ID: 329eb12f-7302-4ecf-c1bf-a50ba3f34bdf
Content: Create your first function in Azure with Java and Maven
Content Source: articles/azure-functions/functions-create-first-java-maven.md
Service: functions
Product: unspecified
GitHub Login: @rloutlaw
Microsoft Alias: routlaw, glenga

@jkirubakaran Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Tried with Oracle JDK and the error does not occur anymore.

It sounds like this issue is no longer reproducible. Please reopen this issue if you can still repo it. #please-close


fix: made to work with node 14+

Updated to also work with node 16. Please note that this MR will drop support for Node versions below 14. Additionally, it might be a good idea to migrate to node-addon-api eventually. Node 12 and 14 are currently in maintenance mode and maintenance for 12 will end in April next year (https://nodejs.org/en/about/releases/)

Supersedes https://github.com/sqlanywhere/node-sqlanywhere/pull/39

Updated to also work with node 16. Please note that this MR will drop support for Node versions below 14. Additionally, it might be a good idea to migrate to node-addon-api eventually. Node 12 and 14 are currently in maintenance mode and maintenance for 12 will end in April next year (https://nodejs.org/en/about/releases/)

Hi Peter,
Thanks for the work.  Am I to understand that this change will break node 10, node 12, node 14 ?
I discussed with my team and we don't want to merge changes to master that affect our compatibility matrix.  We want to wait a longer time after a node version is EOL before making incompatible changes.
In the meantime I am glad that you are sharing this work.
Kind regards,
Dan

Hi @DanCummins-SAP! I have tested this on node 14 and 16 and this has this is known to work. It might also build perfectly fine on node 12 and 10, but I don't know since I have not tested. Node 10 support has ended already (it is not even on the compatibility-matrix anymore) and node 12 support will end in april of 2022.
I mean I understand that you don't want to break the compatibility-matrix, but currently most of the supported node versions (14, 16 and 17) are not supported by this library (see https://nodejs.org/en/about/releases/).
If you were to release this as a major version bump, users still have an option (they can use the old major version) and, more importantly, are still able to use your databases with the more actual versions of nodejs.

Hi, I had really successful dev times with the 39 pull request. But recently decided to try upgrade node and install the 43 pull request. It looks like npm is having hard time finding the git repo. I run "npm install sqlanywhere/node-sqlanywhere#pull/43/head" and the error I'm getting is "npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno ENOENT
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t<EMAIL_ADDRESS>npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent"
Please help out.

@fanjian5i5i It looks like npm is having a hard time finding the git binary. I would look into my npm config if I were you. Doesn't seem to have anything to do with the PR.

@fanjian5i5i It looks like your npm installation is having a hard time finding the git binary. I would look into my npm config if I were you. Doesn't seem to have anything to do with the PR.

Thanks so much for your response. I updated node to 16 and npm to 8 and it did find the git repo and install the pull request

Are there any plans to merge this PR or update this repo to work on the current versions of NodeJS? Node 14 has been EOL since March 2023 and Node 16 was marked as EOL an few months ago in September 2023.
As far as I can tell this PR works for Node 16, 18, and 20, though I did not test thoroughly.
For a full list of EOL dates please see: https://github.com/nodejs/Release#end-of-life-releases


Add typing information to tests

Codecov Report

Merging #186 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #186   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          18     18
  Lines         831    831
  Branches      115    115
=====================================
  Hits          831    831

Flag
Coverage Δ

#unittests
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


feat: fix flipping between Paused and Running

Problem:
VM status flipping between Paused and Running when host accidentally restarts.
Solution:
Check whether VM is stuck in PasuedIOError when the related Volume is healthy.
Related Issue:
https://github.com/harvester/harvester/issues/4633
Test plan:

Create a 3-node harvester cluster.
Provision a 3-node RKE2 cluster on the harvester and wait for it's ready.
Choose one node to stop kubelet.
a. Find the pid of kubelet process by ps -aux | grep kubelet.
b. Freeze the kubelet process by kill -STOP <kubelet-pid>.
After the node is unavailable. Run shutdown now -r.
After the node is running again, the VM can't be ready.

This PR can work on both v1.2.0 and v1.2.1-rc1. It's ready. Wait for missing elemental image fix (registry.opensuse.org/isv/rancher/elemental/stable/teal53/15.4/rancher/elemental-builder-image/5.3:0.3.1).

@FrankYang0529 Thanks for the great work of this PR. But I'm not a fan of doing the workaround within the controller.
Instead, we should pursue the proper fix either in Longhorn or kubelet.
The flipping state is caused by an I/O error. If we restart the VM silently, it might hide the problem and no one will notice it.
Also by doing this, it might make it even harder to debug because the virt-launcher pod is gone and states change. We had some support experience and found keeping the crime scene is always what we prefer most.
I'd suggest we add the workaround steps and let the user do it.


fix: iterate over receipts in order in BundleStateWithReceipts

This fixes a bug where the receipts root and logs bloom in BundleStateWithReceipts::receipts_root_slow and BundleStateWithReceipts::block_logs_bloom would be non-deterministic due to arbitrary ordering when iterating over a HashMap. Introduced a receipts_ordered method, which should be used for every method that interacts with the receipts map directly and requires ordered receips.

closing in favor of #4558


HangUp is an Async API

@LoadLibrary : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Closing per email


Allow persistent/sticky login so that users do not have to reauthenticate multiple times per day

Describe the solution you'd like
Credentials should not need to be entered every 10 minutes when I open AppCenter in a fresh tab. There is close to no persistence of credentials as nearly every time I use AppCenter (or HockeyApp), I need to reauthenticate. Azure Devops, Office 365, Azure MS Portal, etc. all remember who I am on my work machine.
Describe alternatives you've considered
None. I have no choice but to go through the authorization flow multiple times per day.
Additional context
Add an option here to "Stay signed in?"

Hi @ericcjobes -- Thanks for reaching out. I haven't noticed this being a wide-spread issue so there may be something particular about your machine or browser causing this. I suggest you start a chat with a member of our support team through the in-app chat experience in the lower-right of https://appcenter.ms. I'll leave the issue open for now to see if this gets any more votes to signal similar experience from others and whether your discussion with support yields a resolution.


Feature: move dashboard button to landing

Issue: https://github.com/LaurierHawkHacks/Landing/issues/120
Two things:

Import the most impressive button component I have seen
Update the existing button to button component that @juancwu created.

@juancwu any reason you setup this in tailwind.config if you don't use it?
'tbrand-mouse-down': '#1D7882',
'tbrand-highlight': '#00CEDB',

Btw...it's not passing the automated check for some reason. Might need help on this one >:D
Warning: CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
Error: Path does not exist: eslint-results.sarif
ConfigurationError: Path does not exist: eslint-results.sarif
    at run (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:65:15)
    at async runWrapper (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:76:[9](https://github.com/LaurierHawkHacks/Landing/actions/runs/8127235652/job/22211846750?pr=122#step:5:10))

@juancwu any reason you setup this in tailwind.config if you don't use it?
'tbrand-mouse-down': '#1D7882',
'tbrand-highlight': '#00CEDB',

Did not make a whole lot sense when the colours are not widely shared so I just put in the arbitrary colours in the component. Left the styles cuz I forgot to remove them lol.

Btw...it's not passing the automated check for some reason. Might need help on this one >:D
Warning: CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
Error: Path does not exist: eslint-results.sarif
ConfigurationError: Path does not exist: eslint-results.sarif
    at run (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:65:15)
    at async runWrapper (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:76:[9](https://github.com/LaurierHawkHacks/Landing/actions/runs/8127235652/job/22211846750?pr=122#step:5:10))

I think its good to learn some DevOps @teoh4770 :eyes:

@juancwu any reason you setup this in tailwind.config if you don't use it?
'tbrand-mouse-down': '#1D7882',
'tbrand-highlight': '#00CEDB',

Did not make a whole lot sense when the colours are not widely shared so I just put in the arbitrary colours in the component. Left the styles cuz I forgot to remove them lol.

Solid reason lmao.

Btw...it's not passing the automated check for some reason. Might need help on this one >:D
Warning: CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
Error: Path does not exist: eslint-results.sarif
ConfigurationError: Path does not exist: eslint-results.sarif
    at run (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:65:15)
    at async runWrapper (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:76:[9](https://github.com/LaurierHawkHacks/Landing/actions/runs/8127235652/job/22211846750?pr=122#step:5:10))

I think its good to learn some DevOps @teoh4770 👀

Can't avoid devop 😭

Btw...it's not passing the automated check for some reason. Might need help on this one >:D
Warning: CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
Error: Path does not exist: eslint-results.sarif
ConfigurationError: Path does not exist: eslint-results.sarif
    at run (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:65:15)
    at async runWrapper (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:76:[9](https://github.com/LaurierHawkHacks/Landing/actions/runs/8127235652/job/22211846750?pr=122#step:5:10))

I think its good to learn some DevOps @teoh4770 👀

Can't avoid DevOps 😭

Next time you can just run pnpm run lint to check for issues when its the eslint action.
I have updated the PR with the changes needed.

Btw...it's not passing the automated check for some reason. Might need help on this one >:D
Warning: CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
Error: Path does not exist: eslint-results.sarif
ConfigurationError: Path does not exist: eslint-results.sarif
    at run (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:65:15)
    at async runWrapper (/home/runner/work/_actions/github/codeql-action/v2/lib/upload-sarif-action.js:76:[9](https://github.com/LaurierHawkHacks/Landing/actions/runs/8127235652/job/22211846750?pr=122#step:5:10))

I think its good to learn some DevOps @teoh4770 👀

Can't avoid DevOps 😭

Next time you can just run pnpm run lint to check for issues when its the eslint action.
I have updated the PR with the changes needed.

Noted

Merge so that new branches can use the button component.


[Coverity CID :203488]Memory - corruptions in /subsys/net/lib/lwm2m/ipso_push_button.c

Static code scan issues seen in File: /subsys/net/lib/lwm2m/ipso_push_button.c
Category: Memory - corruptions
Function: button_create
Component: Networking
CID: 203488
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

False positive.


DBT configs search from prefix

Based on the discussion on https://github.com/open-metadata/OpenMetadata/pull/4462#pullrequestreview-951528821
Do not search all the buckets (this will not work with some more constrained security requirements).
We should allow a prefix to be passed there too and search from that key.

cc @OnkarVO7

let's see if we can fix it for 0.10.1

Yes I'll take a look

Thanks for the update @OnkarVO7. As part of this, we will also add the bucket name to not have any permission issues when listing all buckets.


docs: add detailed explanation about default events

Description
It seems better to add more detailed information about default events emitted by baseapp. (Especially information about the event structure.)
This PR is trying to add such information to the document created by #1081.
Checklist:

[x] I followed the contributing guidelines and code of conduct.
[ ] I have added a relevant changelog to CHANGELOG.md
[ ] I have added tests to cover my changes.
[ ] I have updated the documentation accordingly.
[ ] I have updated API documentation client/docs/swagger-ui/swagger.yaml

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.ryuichi.sakai seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@zemyblue, PTAL

@zemyblue Rebased.


Metrics

Added metrics for transformers and opened the transformer model up to the whole dataset, earning us a accuracy of 80.7%

I've pushed my updated code to this branch and I believe it shows up in this PR including the updated graphs. This added code in train.rnn calculates and stores the accuracy, training loss, and validation loss for each epoch. After training, it plots two graphs: one for accuracy vs epochs and another for training and validation loss vs epochs. Unfortunately we cannot include them in the report but we could consider adding them to the readme and referencing that in the report. (thankfully there doesn't seem to be any merge conflicts here)


line output format: wrong (relative) filename

Running vale --output line /some/path/README.md in /some/path will display:

/README.md:22:45:vale.Hedging:Consider removing 'probably'

The leading slash is wrong here.
It looks like it is made relative to the current working directory, but then not sliced correctly: running it from /some will use /path/README.md (where is should be path/README.md for the correct relative path).
The default output format ("CLI") and "JSON" are using the full path however always.
vale version 0.9.0

I just stumpled upon this bug myself. A quick workaround (for my workflow at least) is to pipe the output of vale through sed and just prepend the missing path elements.

I've changed "line" to default to returning full paths (as "CLI" and "JSON" also do). The old behavior has moved to a flag, --relative, which still needs to be fixed.


OETL randomly stucks

OrientDB 2.1.12, Windows 7 64b, JAVA 1.8
I have simple table accounts with 7 columns. I want to import this table to orientdb. I've created a script for oetl and if I run this script without parallel access, all will work.
But if I try to turn the paralelization on, it will often stuck randomly:
OrientDB etl v.2.1.12 (build 2.1.x@rb2f496fd6baa3b845b8f442c0ade5505249336cb; 2016-03-01 08:10:48+00
00) www.orientdb.com
BEGIN ETL PROCESSOR
[file] INFO Reading from file accounts_500k.csv with encoding UTF-8
Started parallel execution with 7 threads

extracted 3 504 rows (0 rows/sec) - 3 504 rows -> loaded 1 vertices (0 vertices/sec) Total time: 1
015ms [0 warnings, 0 errors]
extracted 8 696 rows (5 120 rows/sec) - 8 696 rows -> loaded 5 188 vertices (5 115 vertices/sec) T
otal time: 2029ms [0 warnings, 0 errors]
extracted 11 753 rows (2 970 rows/sec) - 11 753 rows -> loaded 8 245 vertices (2 970 vertices/sec)
Total time: 3058ms [0 warnings, 0 errors]
extracted 11 753 rows (0 rows/sec) - 11 753 rows -> loaded 8 245 vertices (0 vertices/sec) Total t
ime: 4064ms [0 warnings, 0 errors]
extracted 11 753 rows (0 rows/sec) - 11 753 rows -> loaded 8 245 vertices (0 vertices/sec) Total t
ime: 5078ms [0 warnings, 0 errors]
extracted 11 753 rows (0 rows/sec) - 11 753 rows -> loaded 8 245 vertices (0 vertices/sec) Total t
ime: 6092ms [0 warnings, 0 errors]
extracted 11 753 rows (0 rows/sec) - 11 753 rows -> loaded 8 245 vertices (0 vertices/sec) Total t
ime: 7106ms [0 warnings, 0 errors]
extracted 11 753 rows (0 rows/sec) - 11 753 rows -> loaded 8 245 vertices (0 vertices/sec) Total t
ime: 8120ms [0 warnings, 0 errors]
extracted 11 753 rows (0 rows/sec) - 11 753 rows -> loaded 8 245 vertices (0 vertices/sec) Total t
ime: 9134ms [0 warnings, 0 errors]

we have done some code improvement to avoid this kind od deadlock. Will be in 2.1.13

Thanks for quick reply, but I tried it 5 times and it crashed two times :(
And one new NPE is here. I'm ready to fully cooperate with you, if you are interested, just send me a message.
d:\Prace\orientDB\orientdb-community-2.1.13\bin>oetl.bat account.json
OrientDB etl v.2.1.13 (build 2.1.x@r9bc1a54a4a62c4de555fc5360357f446f8d2bc84; 2016-03-14 17:00:05+00
00) www.orientdb.com
BEGIN ETL PROCESSOR
[file] INFO Reading from file accounts_500k.csv with encoding UTF-8
Started parallel execution with 7 threads
Exception in thread "OrientDB ETL pipeline-0" java.lang.NullPointerException
at com.orientechnologies.orient.etl.transformer.OVertexTransformer.begin(OVertexTransformer.
java:53)
at com.orientechnologies.orient.etl.OETLPipeline.begin(OETLPipeline.java:70)
at com.orientechnologies.orient.etl.OETLProcessor$2.run(OETLProcessor.java:349)
at java.lang.Thread.run(Thread.java:745)

extracted 3 502 rows (0 rows/sec) - 3 502 rows -> loaded 0 vertices (0 vertices/sec) Total time: 1
003ms [0 warnings, 0 errors]
extracted 8 799 rows (5 223 rows/sec) - 8 799 rows -> loaded 5 293 vertices (5 219 vertices/sec) T
otal time: 2017ms [0 warnings, 0 errors]
extracted 22 400 rows (13 413 rows/sec) - 22 400 rows -> loaded 18 907 vertices (13 426 vertices/s
ec) Total time: 3031ms [0 warnings, 0 errors]
extracted 38 995 rows (16 365 rows/sec) - 38 995 rows -> loaded 35 489 vertices (16 353 vertices/s
ec) Total time: 4045ms [0 warnings, 0 errors]
extracted 59 135 rows (19 861 rows/sec) - 59 135 rows -> loaded 55 628 vertices (19 860 vertices/s
ec) Total time: 5059ms [0 warnings, 0 errors]
extracted 84 117 rows (24 637 rows/sec) - 84 117 rows -> loaded 80 610 vertices (24 637 vertices/s
ec) Total time: 6073ms [0 warnings, 0 errors]
extracted 134 301 rows (49 491 rows/sec) - 134 301 rows -> loaded 130 795 vertices (49 492 vertice
s/sec) Total time: 7087ms [0 warnings, 0 errors]
extracted 135 601 rows (1 293 rows/sec) - 135 601 rows -> loaded 132 094 vertices (1 292 vertices/
sec) Total time: 8092ms [0 warnings, 0 errors]
extracted 135 601 rows (0 rows/sec) - 135 601 rows -> loaded 132 094 vertices (0 vertices/sec) Tot
al time: 9106ms [0 warnings, 0 errors]
extracted 135 601 rows (0 rows/sec) - 135 601 rows -> loaded 132 094 vertices (0 vertices/sec) Tot
al time: 10120ms [0 warnings, 0 errors]
extracted 135 601 rows (0 rows/sec) - 135 601 rows -> loaded 132 094 vertices (0 vertices/sec) Tot
al time: 11134ms [0 warnings, 0 errors]
extracted 135 601 rows (0 rows/sec) - 135 601 rows -> loaded 132 094 vertices (0 vertices/sec) Tot
al time: 12148ms [0 warnings, 0 errors]
extracted 135 601 rows (0 rows/sec) - 135 601 rows -> loaded 132 094 vertices (0 vertices/sec) Tot
al time: 13162ms [0 warnings, 0 errors]
extracted 135 601 rows (0 rows/sec) - 135 601 rows -> loaded 132 094 vertices (0 vertices/sec) Tot
al time: 14176ms [0 warnings, 0 errors]

The best would be to have the configuration json and a data sample.

Just for the record - config and sample was sent directly to Rob due to privacy reasons :)

Hi, solution to this problem is more complex than expected. My suggestion is to run with parallel set at false. It takes a little bit longer, but on my tests it never locks.

Thanks, I did it this way, but if you have 150M rows, it's a very long procedure :( So I will wait for this fix.

Hello robfrank,
When can we expect this to be fixed?
Regards,
Sajeev

I managed to solve this problem on develop branch. At the moment I can't backport on 2.2.x, too much differences.


Possible Memory Leak: SocketIO + RedisStore

(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace:
    at RedisClient.<anonymous> (events.js:126:17)
    at RedisClient.subscribe (/var/nodejs/lib/node_modules/socket.io/lib/stores/redis.js:116:18)
    at RedisClient.emit (events.js:81:20)
    at RedisClient.return_reply (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/index.js:450:22)
    at HiredisReplyParser.<anonymous> (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/index.js:81:14)
    at HiredisReplyParser.emit (events.js:64:17)
    at HiredisReplyParser.execute (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/lib/parser/hiredis.js:35:22)
    at RedisClient.on_data (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/index.js:358:27)
    at Socket.<anonymous> (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/index.js:93:14)
    at Socket.emit (events.js:64:17)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace:
    at Redis.<anonymous> (events.js:126:17)
    at RedisClient.subscribe (/var/nodejs/lib/node_modules/socket.io/lib/stores/redis.js:118:14)
    at RedisClient.emit (events.js:81:20)
    at RedisClient.return_reply (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/index.js:450:22)
    at HiredisReplyParser.<anonymous> (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/index.js:81:14)
    at HiredisReplyParser.emit (events.js:64:17)
    at HiredisReplyParser.execute (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/lib/parser/hiredis.js:35:22)
    at RedisClient.on_data (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/index.js:358:27)
    at Socket.<anonymous> (/var/nodejs/lib/node_modules/socket.io/node_modules/redis/index.js:93:14)
    at Socket.emit (events.js:64:17)

This error seemed to have started when i switched from MemoryStore to RedisStore, Seems to happen periodontally,  This may not be a memory leak but none the less should be fixed.
NPM Stats:
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>
Redis server version 2.2.12 (00000000:0)

That doesn't include these changes. Use:
"socket.io" : "https://github.com/dshaw/socket.io/tarball/dev%2Fredis"
instead if
"socket.io" : "0.8.4"
in you package.json.
You might also want to delete and reinstall your node_modules folder, since they both identify as the same version. I'm not sure who wins in that case.

OK, I pulled the latest from your dev/redis branch, however that message still shows when a connection is made. It occurs on line 133 of stores/redis.js. It is because the listeners are being applied to the this.sub object as opposed to the actual redis container: https://gist.github.com/1270830
I tried removing the call to setMaxListeners that you added and then I got one of those messages on line 135 when a listener is attached to the Store object. So it appears that there are actually two instances of this problem occurring. I wonder if the setMaxListeners should be called on the pub and cmd objects to defend against future instances of this happening.

Updated dev/redis with this.sub.maxListeners(0).

Great, works for me. Do you think that the max listeners should be set on pub and cmd as well or are those used differently?

Yay, I'll get this in. sub has all the listeners. pub and cmd mostly trigger events. I don't want to remove this notification anywhere that it's not absolutely necessary to do so.

Cool. I guess leaving it to the default (pub / cmd) is best until necessary to do so. That way it will be well known if it pushes the limit which is a probably a good thing to be known.


Updates for 1.1 release

@richlander @dleeapho
After walking through these, I definitely think all the samples need to do a better job at enumerating clear steps to configure an environment which can be used to build and run the samples.  Getting a configuration that has a compatible cli and correct shared framework installed is going to be frustrating for many.  I see this as something that can be done with a follow-up PR.

Good points! Will do.
Thanks for this PR!


[Quest/Malawi Core] Add a summary page for paginated questionnaires

Name of feature to enhance
Paginated questionnaires
Description of feature
Is a questionnaire that spans multiple pages
Describe the enhancement
At the end of the pages, there should be a summary page. This feature is part of the recent android fhir sdk update. The PR for this feature can be found here.
Note: If the questionnaire only has a single page then the summary page is not needed.

Relates to #1188


Update BigQuery insert_id

Per the BigQuery team:

The insert ID in tabledata.insertAll should not be a hash of the row's contents. We should support customers intentionally including multiple rows in the same value.

This PR changes the value used for insert_id to Object#object_id from an MD5 hash. Object#object_id is guaranteed to be unique on active objects.

@jjolma Can you review this change?

I think this approach can result in incorrect de-duplication since 1) object_ids can be recycled as objects are garbage collected, and 2) two clients streaming into the same table happen to have object_id collisions.  In either case, the first row would get inserted correctly, but the second one would not.
This is very unlikely, admittedly, but would it be a simple change to use a random ID, e.g. UUID4, instead?

@jjolma I don't think this can happen. If you look at the link in the PR description, it says:

The same number will be returned on all calls to object_id for a given object, and no two active objects will share an id.

It is possible for the same object_id to be recycled, but not within the scope of the tabledata.insertAll RPC call, since all data objects are active during the RPC invocation.

The de-duplication window spans all RPCs within the de-duplication window.

Okay, I have updated the PR to use a UUID for insert_id. PTAL.

LGTM


docs/install_linux.md

Hi @kkash18, I am going to close this issue like I have closed the previous issues that you have opened. We welcome issues, comments, and pull requests in this repository, but please refrain from opening issues or other communications that are not relevant to this repository or its purpose.


Tslint

Added tslint.json with the discussed rules/options, and linted the typescript files in the project. Also updated some of the tests to reflect changes to the components (checkbox and radio buttons)

Coverage remained the same at 100.0% when pulling 5f45e683465334d3d46c01ce7061dcf09daafd9d on tslint into 55b8f9674da3cbb94c98663b80a4cf78a0780774 on master.

Coverage remained the same at 100.0% when pulling 910f3846810f9eec67ba4589c2a6dbbeec799334 on tslint into 55b8f9674da3cbb94c98663b80a4cf78a0780774 on master.

Coverage remained the same at 100.0% when pulling 1b8685ee40242e82221ec84d938a152a88c289f6 on tslint into 55b8f9674da3cbb94c98663b80a4cf78a0780774 on master.

Coverage remained the same at 100.0% when pulling fc7abaff706d5e22c7be8f95b4ff14e50c1b6729 on tslint into 55b8f9674da3cbb94c98663b80a4cf78a0780774 on master.

Coverage remained the same at 100.0% when pulling ea4a30becf63ef4c904d34392c8ab11503f2df8e on tslint into 55b8f9674da3cbb94c98663b80a4cf78a0780774 on master.


acpi-tables: switch to using libgpiod when DISTRO_FEATURES has acpi

Signed-off-by: Ferry Toth<EMAIL_ADDRESS>

When acpi is enabled pinmux's are controlled by loading acpi tables. However, Edison Arduino requires TRI_STATE_ALL be toggled, which is normally handled by MRAA. Echoing to the pin number doesn't seem to work reliably, so change to gpiolib. This code is incorporated into initramfs, so acpi tables are loaded and TRI_STATE_ALL toggled as early as possible without loading acpi.cpio to memory from U-Boot.
This can be tested by enabling acpi or building pyro64_acpi and testing i2c. Without this patch the following will not work:
modprobe -i i2c-dev
i2cdetect -r 1
#WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1 using read byte commands.
I will probe address range 0x03-0x77.
Continue?

Inspection is good enough. This code has only effect with acpi enabled and works (the code in the repo doesn't).
I'm on Kubuntu 18.04 BTW, despite the build warning this works fine.

Thanks, merged.


mattermost refactoring

Description
Changes proposed in this pull request:

Upgraded to v8
fixed infinite error loop issue

Testing

Related issue(s)
Fixes https://github.com/kubeshop/botkube/issues/1143

@dependabot help


Update surface-hub-site-readiness-guide.md

line 134 Fixed  video link MD formatting

@levinec Would you be able to merge this PR that addresses a minor Markdown link fix? Thank you.


How to add custom color scheme internally, to prepare for PR #217

I have my file that defines the colors for my color scheme, but I'm not sure how to make it so Galaxyline recognizes it as a built-in color scheme, so I can submit it as a PR.

Hey, please take a look at the themes.md file in the docs directory in the repository


[Bug]:  Writing more than 20MB to HDFS results in silent data corruption.

What happened?
I've been trying to use hadoopfilesystem.HadoopFileSystem to write TFX artefacts to HDFS.  When the file I try to write is smaller than 20MB everything is fine. But when it is larger than 20MB (python's BufferedWriter default buffer size), the written file is corrupted without any error being detected.
I believe it is because HdfsUploader uses the HDFScli (and through it, the WebHDFS API) as if one could stream write a file after opening it, as is usually the case for filesystems, but it doesn't seem to be the case for WebHDFS/HDFScli: the file must be written all at once with exactly one PUT query.

When the whole file is smaller than the buffer of BufferedWriter, it gets written all at once when closing the BufferedWriter and everything works.
When the file is larger than the buffer, several write calls are made to the hdfs.InsecureClient on the same file handle and all hell breaks loose.

If I am right, this should be rather difficult to fix since beam's writing API necessitates being able to stream to a file, and WebHDFS doesn't seem to allow it.
Issue Priority
Priority: 1
Issue Component
Component: io-py-hadoop

Obvious workarounds:

(for TFX) making your artefacts smaller by using more tasks/parallelism
making the BufferedWriter's buffer larger if your workers have enough memory (hadoopfilesystem.py line 253)

Additional notes: I have reproduced this bug without using TFX at all, only with a python 3.7 container, beam 2.39, and writing text in a big file as in:
fs = apache_beam.io.hadoopfilesystem.HadoopFileSystem(apache_beam.options.pipeline_options.PipelineOptions.from_dictionary({"hdfs_host": "hadoop-hadoop-hdfs-nn.hdfs", "hdfs_port":"50070", "hdfs_user":"root"})) writer = fs.create("hdfs://myfile.txt") for i in range(4000000):     writer.write(bytes(str(i) + "\n", 'utf-8')) writer.close()

Last remark: Although I am not exactly sure why, the bug doesn't manifest when writing the big file all at once. Likely in that case it bypasses the BufferedWriter entirely.

.take-issue


VSLangProj15817.2.32505.113

Type: Missing
Summary:
VSLangProj15817.2.32505.113
Details:
Declaring OTHER for proprietary license
Resolution:
https://www.nuget.org/packages/VSLangProj158/17.2.32505.113/License
Affected definitions:

VSLangProj158 17.2.32505.113

Closing. My curation is not showing up under Files changed.


Please add support for RedisTimeSeries :)

Could you please add support for RedisTimeSeries
https://oss.redislabs.com/redistimeseries/
thanks!

ioredis works with arbitrary commands with Redis#call(commandName: string, ...args: any[]): Promise<any>, so RedisTimeSeries is already supported:
const redis = new Redis()
redis.call('TS.ADD', 'temperature:3:11',<PHONE_NUMBER>, 30)


Refactor code on users, status, utils

Refactor code summary

add app prefix on some functions
optimize import
apply some coding style suggested my the linter
render -> render_index
hard coded 404, 500 -> Http404, PermissionDenied

+1 besides comments
@bruce3557 please check

+1
please merge if it is okay

Going to merge.


upgrade jruby to <IP_ADDRESS> as it fixed some assertions bugs

When investigating issue https://github.com/asciidoctor/asciidoctor-intellij-plugin/issues/337 I found that the latest ruby version fixes some assertions, see https://github.com/jruby/jruby/pull/5693.
As the test suite of AsciidoctorJ runs without errors on this new JRuby release, I suggest an update of JRuby with this PR.

Thanks!


Using with NeoVim - Support?

I've installed the plugin using vim-plug in NeoVim. There plugin doesn't appear to have started opening a sample file and running the ig command gives the following error:
Error detected while processing function 57_IndentGuidesToggle..indent_guides#toggle..indent_gui
des#enable..indent_guides#init_script_vars..indent_guides#capture_highlight:
line    2:
E411: highlight group not found: Normal
Is there an issue with my setup?

Fixed adding the following to my vim file:
colorscheme default

Was going to suggest that :)
In GUI mode, the colors for the indent guides are all derived from the Normal highlight group.


fix: downgrade ArgoCD frontend plugin

Description
downgrade roadiehq/backstage-plugin-argo-cd back to 2.4.1 to avoid regression.
For more info, see the original PR https://github.com/janus-idp/backstage-showcase/pull/947
Which issue(s) does this PR fix
PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

does this require a yarn.lock regen?

it should, I've added it

/override "SonarCloud Code Analysis"
complains about code not in this PR

e2e tests are failing to start for some reason.
I've tested the change manually and with this downgrade bot, ArgoCD cards are showing correctly. Before the downgrade the "ArgoCD History" card was not loading up.

/cherry-pick 1.1.x


Update instruction data to compatible with Anchor

See https://github.com/hyperledger/solang/pull/1105

Did you run yarn fmt and yarn lint?

Yes, those should be checked in CI now


g-link doesn't work when navigating from template in production

Description
When I freshly navigate (by refreshing or pasting the url) to a template path (e.g. /blog/:id where project contains /src/templates/BlogPost.vue and gridsome.config.js is configured to templates: { BlogPost: '/blog/:id' }), the template loads, but clicking on g-links doesn't work. Note: this problem only occurs when the project has been built for production.
Steps to reproduce
Clone this repository:
https://github.com/AMFTech512/austinfay-gridsometest
run npm install
run gridsome build
go into the dist directory and start a simple http server. I used http-server available from npm.
Navigate to http://localhost:8080/blog/7276d4ef759b5f50407ed8829c5ac817
Click on any link on the page.
Expected result
The app should navigate to a different page.
Actual result
Though the route in the url bar changes, the rendered HTML on the page doesn't change. The original blog post template remains the thing that is rendered.

Hi,
it seems there is a problem with your g-link definition inside the templates/BlogPost.vue.
Also the :key definition wasn't correct.
I have changed it locally to this one:
<template>
    <Layout>

Blog Posts

                <g-link :to="blogPost.node.path">{{ blogPost.node.title }}</g-link>

    </Layout>
</template>

<static-query>
query{
  posts: allBlogPost{
    edges{
      node{
        id
        path
        title
        description
        content
      }
    }
  }
}
</static-query>

To test the gridsome build result, I use this ( just add it to the scripts inside the `package.json? ) - I was able to click any link.
"prod": "python3 -m http.server --directory dist/"

Hey @AMFTech512
Can you reproduce the error with a different host like vercel or netlify?

Hi again, @noxify,
Sure. Here's the link:
https://xenodochial-gates-fac98e.netlify.app/
I also updated the code in the repository that I sent you before.
Thanks for taking the time to look at this!

Hey @AMFTech512 ,
I'm sorry but I can't reproduce your described problem.
My Env:

Google Chrome Version 83.0.4103.61
macOS Catalina 10.15.5

STRs:

Open the netlify url in a new tab
opened dev tools and ensured that "Network > Disable cache" is disabled
Refreshed the website
clicked every link
4.1. from each blog post entry i clicked also the "About" and the "Home" link

I have repeated all steps in porn mode, but the result was the same.
Since the OS should not be the problem - Which browser are you using?
Regards,
marcus

Hi again, @noxify,
I've tried on 3 browsers:

Google Chrome Version 83.0.4103.61
Microsoft Edge Version 83.0.478.44
Firefox Version 77.0

I'm running Windows 10 Version 1909 Build 18363.836 (but I agree that OS shouldn't matter).
So you don't experience the same behavior? Here's a short video of what I see:
https://drive.google.com/file/d/1HrVwPqm7AcQXc7m6tsDwpJFSd6gbdt5J/view?usp=sharing
Sorry, I really hope I'm not wasting your time.
Austin

Hi @AMFTech512
You’re not wasting my time :) we are here to help 😊
I will check it tomorrow - maybe I have missed something 🤷🏾♂
Thanks for the video :)

Hi @AMFTech512
with your video, I was able to reproduce the issue.
It seems that this issue occurs only if on "BlogPost" pages.
I refreshed the page also on "Blog" and "About", but here the page changed as expected.

I did some research on the existing gh issues, I have found multiple issues for this case, but #337 seems to be the same issue.
The problem is, that you have a p tag inside a p tag.

Changing the parent p to a div, it should solve the issue ( original solution: https://github.com/gridsome/gridsome/issues/337#issuecomment-478281759 )

Hey @noxify, you're right!
I know that you shouldn't have nested p tags, but I also think it's strange that having them causes this behavior in the app. Switching that tag to a div definitely solved the problem.
I can't believe that I didn't find post #337 before... I guess I didn't search hard enough. I was convinced there was a bug in Gridsome.
Thanks for all of your help!
Austin


m.youtube.com not appearing

I set up the proxy on my site schlarman.org/web/ I am mainly doing my browsing from a mobile device and when I enter YouTube.com it redirects to m.youtube.com and it just shows a blank page.

I attempted to create a plugin as suggested https://github.com/Athlon1600/php-proxy-app/issues/37 but it can't seem to get it to work.

What is not working? The plugin itself? Is it enabled?
https://github.com/Athlon1600/php-proxy-app/blob/master/config.php
It has to be added here:
$config['plugins'] = array(

I followed what you said and made sure to have it enabled from the config.php file. the code that is in the plugin looks like this:
use Proxy\Plugin\AbstractPlugin;
use Proxy\Event\ProxyEvent;

class YoutubeMobilePlugin extends AbstractPlugin {

	public function onBeforeRequest(ProxyEvent $event){
		$event['request']->headers->set('user-agent', 'Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25');
	}

	public function onHeadersReceived(ProxyEvent $event){
		// fired right after response headers have been fully received - last chance to modify before sending it back to the user
	}

	public function onCurlWrite(ProxyEvent $event){
		// fired as the data is being written piece by piece
	}

	public function onCompleted(ProxyEvent $event){
		// fired after the full response=headers+body has been read - will only be called on "non-streaming" responses
	}
}

It still doesn't seem to want to work, I even uploaded the version with the plugin to part of my website ( be.schlarman.org ) and it doesn't seem to work. I am trying to get it to work on a screen the size of an Ipad or smaller.

I gave up on the main issue and then replaced
$event['request']->headers->set('user-agent', 'Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25');
With
$event['request']->headers->set('user-agent', 'Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0');
I sacrifice any sort of phone user, but I plan on only using tablets as the smallest device on the site.


Feature request: Modify R3F Euler rotations in degrees, not radians

Using radians to keyframe Euler rotations feels less natural to me, coming from software like Blender where these edits are done in degrees. For example, keyframing to Y=90º is easier than Y=1.5707963. We could change the @theatre/r3f bindings to work with Euler rotations (e.g. THREE.Euler) in degrees, instead. This could potentially just be a UI change, where the keyframe data is still serialized and stored in radians. Would a PR for this change be welcome? Thanks!

Hey @donmccurdy, this makes sense! The PR is definitely welcome! So to summarize, we take input in degrees and store and sterilize in radians, right?
Ultimately the goal is that while we should always serialize to a canonical unit (in this case radians), we could support data entry and display in different units, like degrees for rotation, km for translation, or F for temperature, if someone makes a custom prop for that sometime. :D

So to summarize, we take input in degrees and store and sterilize in radians, right?

If there's some reason it's better to store degrees (I don't know of any) I'd be open to that approach too. But yes — "input and display in degrees, store in radians" sounds great.
This isn't my use case at the moment, but I could easily imagine needing a similar solution for interpolating color, e.g. input and display in sRGB, store and interpolate in Linear-sRGB or ACEScg.

Glad you mentioned this, I already made an internal design doc for the future architecture of props, the current one is only there to serve the most immediate needs. Basically I see 3 different individually configurable aspects to props:

how values are input
how things are interpolated
how values are stored and output

For example in the case of colors, you might want to input it in HLS, interpolate in LAB, and have the output be in sRGB, so even the interpolation could have its own bespoke space to happen in.
None of this is set in stone, just something we are thinking about.

Considering this would be a bandaid until we overhaul the deeper architecture a little, which is a bit down the road, it best be arranged at extension level for now. I'd hide it behind a configuration option that defaults to radians to take care of backwards compatibility, should be enough imo.

Just to share another possible 'difference' in handling rotations vs. vectors here – I'm finding it much more natural to keyframe rotations using the ZYX order rather than XYZ. For example, camera.rotation.set(x, y, z, 'ZXY').


aswanth

Any updates @aswanthpp

Are there any updates here or should we close the PR and label it as spam?

spam


[Feature Request] Support unmarshaling of $.Inner yaml/json/toml string within shortcodes

Within shortcodes, there does not seem to be a way to unmarshal data passed in via $.Inner.
I am aware that data files located in the data directory of the project root are automatically unmarshaled and accessible as a data structure.  However, I would like to keep my data (e.g. code samples) embedded within the markdown text itself, rather than placing the code samples in a different directory.
The current hugo code-toggle example follows the pattern where it processes data from $.Inner.  However the remarshal function that it uses transforms data from string (e.g. yaml) -> data-structure -> string (e.g. json).  I need an unmarshal function that transforms data from string -> data-structure, at which point the data-structure is accessible.
Example Markdown
{{<my-shortcode>}}
osx:   brew install docker
win10: choco.exe install docker
{{</my-shortcode>}}

Example Shortcode: my-shortcode.html
{{ $myDict := unmarshal $.Inner }}
or
{{ $myDict := $.Inner | unmarshal "yaml" }}

<div>{{ $myDict.osx }}<div>

If there's an existing method of unmarshaling and accessing $.Inner as a data struture, please provide guidance.  If there isn't, and if proposal is reasonable, I'm happy to implement the PR.

Closing in favor of #5428


[cloud_firestore] Firestore plugin should be more helpful in reporting the cause of failed transactions.

Working with Firestore plugin 0.6.3 and just realized a bug on my side after spending too much time looking the wrong places. Firestore plugin should be more helpful in reporting the cause of errors. Specifically in CloudFirestorePlugin.java where the returned exception from the error override does not give much useful information even though it could have:
// Start operations on Dart side.
channel.invokeMethod(
  "DoTransaction",
  arguments,
  new Result() {
    @Override
    public void success(Object doTransactionResult) {
      transactionTCS.setResult((Map<String, Object>) doTransactionResult);
    }

    @Override
    public void error(
      String errorCode, String errorMessage, Object errorDetails) {
      // result.error(errorCode, errorMessage, errorDetails);
      transactionTCS.setException(new Exception("Do transaction failed."));
    }

    @Override
    public void notImplemented() {
      // result.error("DoTransaction not implemented", null, null);
      transactionTCS.setException(
      new Exception("DoTransaction not implemented"));
    }
});

[✓] Flutter (Channel dev, v0.3.5, on Mac OS X 10.12.6 16G1314, locale en-DK)
[✓] Android toolchain - develop for Android devices (Android SDK 26.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.2)
[✓] Android Studio (version 3.1)
[✓] IntelliJ IDEA Community Edition (version 2017.2.6)
[✓] Connected devices (1 available)

@mortenboye
The issue at https://github.com/flutter/flutter/issues/17024 has been closed and moved here. Future collaboration on this issue will be done here.

We'll consolidate and track this on #1223 - thanks!