 By default, stdout and stderr are not captured, and those attributes
[   43s]         will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture them.
[   43s]
[   43s]         If check is True and the exit code was non-zero, it raises a
[   43s]         CalledProcessError. The CalledProcessError object will have the return code
[   43s]         in the returncode attribute, and output & stderr attributes if those streams
[   43s]         were captured.
[   43s]
[   43s]         If timeout is given, and the process takes too long, a TimeoutExpired
[   43s]         exception will be raised.
[   43s]
[   43s]         There is an optional argument "input", allowing you to
[   43s]         pass bytes or a string to the subprocess's stdin.  If you use this argument
[   43s]         you may not also use the Popen constructor's "stdin" argument, as
[   43s]         it will be used internally.
[   43s]
[   43s]         By default, all communication is in bytes, and therefore any "input" should
[   43s]         be bytes, and the stdout and stderr will be bytes. If in text mode, any
[   43s]         "input" should be a string, and stdout and stderr will be strings decoded
[   43s]         according to locale encoding, or by "encoding" if set. Text mode is
[   43s]         triggered by setting any of text, encoding, errors or universal_newlines.
[   43s]
[   43s]         The other arguments are the same as for the Popen constructor.
[   43s]         """
[   43s]         if input is not None:
[   43s]             if kwargs.get('stdin') is not None:
[   43s]                 raise ValueError('stdin and input arguments may not both be used.')
[   43s]             kwargs['stdin'] = PIPE
[   43s]
[   43s]         if capture_output:
[   43s]             if kwargs.get('stdout') is not None or kwargs.get('stderr') is not None:
[   43s]                 raise ValueError('stdout and stderr arguments may not be used '
[   43s]                                  'with capture_output.')
[   43s]             kwargs['stdout'] = PIPE
[   43s]             kwargs['stderr'] = PIPE
[   43s]
[   43s]         with Popen(*popenargs, **kwargs) as process:
[   43s]             try:
[   43s]                 stdout, stderr = process.communicate(input, timeout=timeout)
[   43s]             except TimeoutExpired as exc:
[   43s]                 process.kill()
[   43s]                 if _mswindows:
[   43s]                     # Windows accumulates the output in a single blocking
[   43s]                     # read() call run on child threads, with the timeout
[   43s]                     # being done in a join() on those threads.  communicate()
[   43s]                     # _after_ kill() is required to collect that and add it
[   43s]                     # to the exception.
[   43s]                     exc.stdout, exc.stderr = process.communicate()
[   43s]                 else:
[   43s]                     # POSIX _communicate already populated the output so
[   43s]                     # far into the TimeoutExpired exception.
[   43s]                     process.wait()
[   43s]                 raise
[   43s]             except:  # Including KeyboardInterrupt, communicate handled that.
[   43s]                 process.kill()
[   43s]                 # We don't call process.wait() as .__exit__ does that for us.
[   43s]                 raise
[   43s]             retcode = process.poll()
[   43s]             if check and retcode:
[   43s] >               raise CalledProcessError(retcode, process.args,
[   43s]                                          output=stdout, stderr=stderr)
[   43s] E               subprocess.CalledProcessError: Command '[PosixPath('/tmp/mesonpy-test-venv-e6z5h263/bin/python'), '-c', 'import spam; print(spam.system("ls /tmp/pytest-of-abuild/pytest-17/test0/mesonpy-test-x0t_i2l1/spam-0.0.1-py3-none-any.whl"))']' returned non-zero exit status 1.
[   43s]
[   43s] /usr/lib64/python3.9/subprocess.py:528: CalledProcessError
[   43s] ----------------------------- Captured stdout call -----------------------------
[   43s] + meson setup --native-file=/home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-native-file.ini -Ddebug=false -Doptimization=2 --prefix=/usr /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/build
[   43s] Directory already configured.
[   43s]
[   43s] Just run your build command (e.g. ninja) and Meson will regenerate as necessary.
[   43s] If ninja fails, run "ninja reconfigure" or "meson --reconfigure"
[   43s] to force Meson to regenerate.
[   43s]
[   43s] If build failures persist, run "meson setup --wipe" to rebuild from scratch
[   43s] using the same options as passed when configuring the build.
[   43s] To change option values, run "meson configure" instead.
[   43s] + meson compile
[   43s] [0/1] Regenerating build files.
[   43s] Cleaning... 2 files.
[   43s] The Meson build system
[   43s] Version: 0.63.2
[   43s] Source dir: /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam
[   43s] Build dir: /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/build
[   43s] Build type: native build
[   43s] Project name: spam
[   43s] Project version: undefined
[   43s] C compiler for the host machine: cc (gcc 12.2.1 "cc (SUSE Linux) 12.2.1 20220830 [revision e927d1cf141f221c5a32574bde0913307e140984]")
[   43s] C linker for the host machine: cc ld.bfd <IP_ADDRESS>20810-1
[   43s] Host machine cpu family: x86_64
[   43s] Host machine cpu: x86_64
[   43s] Program python found: YES (/usr/bin/python3.9)
[   43s] Found pkg-config: /usr/bin/pkg-config (1.8.0)
[   43s] Build targets in project: 1
[   43s]
[   43s] spam undefined
[   43s]
[   43s]   User defined options
[   43s]     Native files: /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-native-file.ini
[   43s]     backend     : ninja
[   43s]     debug       : false
[   43s]     optimization: 2
[   43s]     prefix      : /usr
[   43s]
[   43s] Found ninja-1.11.1 at /usr/bin/ninja
[   43s] [1/2] Compiling C object _spam.cpython-39-x86_64-linux-gnu.so.p/src_spammodule.c.o
[   43s] [2/2] Linking target _spam.cpython-39-x86_64-linux-gnu.so
[   43s] + meson install --destdir /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-mhm9xzoo/install
[   43s] ninja: Entering directory `/home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/build'
[   43s] ninja: no work to do.
[   43s] Installing _spam.cpython-39-x86_64-linux-gnu.so to /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-mhm9xzoo/install/usr/lib64/python3.9/site-packages/spam
[   43s] Installing /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/src/__init__.py to /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-mhm9xzoo/install/usr/lib/python3.9/site-packages/spam
[   43s] WARNING Using heuristics to map files to wheel, this may result in incorrect locations
[   43s] WARNING File could not be mapped to an equivalent wheel directory: /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-mhm9xzoo/install/usr/lib64/python3.8/site-packages/spam/_spam.cpython-38-x86_64-linux-gnu.so (/usr/lib64/python3.8/site-packages/spam/_spam.cpython-38-x86_64-linux-gnu.so)
[   43s] Copying files to wheel...
[   43s] [0/0] spam/__init__.py
[   43s] ----------------------------- Captured stderr call -----------------------------
[   43s] Traceback (most recent call last):
[   43s]   File "<string>", line 1, in <module>
[   43s]   File "/tmp/mesonpy-test-venv-e6z5h263/lib64/python3.9/site-packages/spam/__init__.py", line 1, in <module>
[   43s]     from ._spam import system
[   43s] ModuleNotFoundError: No module named 'spam._spam'
[   43s] =========================== short test summary info ============================
[   43s] FAILED tests/docs/examples/test_spam.py::test_build_and_import - subprocess.C...
[   43s] =================== 1 failed, 51 passed, 1 xpassed in 18.95s ===================

Note the cp38 vs cp39 mismatch

Thanks for the report @bnavigator. Which Linux distro is this? Also, is it fixed when you use Meson 0.63.3 instead of 0.63.2? That should have fixed the File could not be mapped to an equivalent wheel directory thing by no longer writing absolute paths in intro-install_plan.json.

The build log is from the openSUSE Build Service for Tumbleweed.
Tumbleweed does not have meson 0.63.3 yet, but when I include it into the build project I get a new error in test_scipy_like (#170). Excluding that, the WARNING is gone, the error changes, but the test fails at an earlier stage. It still looks for the wrong cpython version:

[    5s] + pytest-3.8 --ignore=_build.python38 --ignore=_build.python39 --ignore=_build.python310 -v -vv -k 'not test_scipy_like'
[    5s] ============================= test session starts ==============================
[    5s] platform linux -- Python 3.8.14, pytest-7.1.2, pluggy-1.0.0 -- /usr/bin/python3.8
[    5s] cachedir: .pytest_cache
[    5s] rootdir: /home/abuild/rpmbuild/BUILD/meson_python-0.10.0, configfile: setup.cfg
[    5s] plugins: mock-3.6.1
[    5s] collecting ... collected 53 items / 1 deselected / 52 selected
...
[   22s] tests/docs/examples/test_spam.py::test_build_and_import PASSED           [100%]
[   22s]
[   22s] ================= 51 passed, 1 deselected, 1 xpassed in 17.39s =================
...
[   22s] + pytest-3.9 --ignore=_build.python38 --ignore=_build.python39 --ignore=_build.python310 -v -vv -k 'not test_scipy_like'
[   22s] ============================= test session starts ==============================
[   22s] platform linux -- Python 3.9.14, pytest-7.1.2, pluggy-1.0.0 -- /usr/bin/python3.9
[   22s] cachedir: .pytest_cache
[   22s] rootdir: /home/abuild/rpmbuild/BUILD/meson_python-0.10.0, configfile: setup.cfg
[   22s] plugins: mock-3.6.1
[   23s] collecting ... collected 53 items / 1 deselected / 52 selected
[   23s]
...
[   40s] tests/docs/examples/test_spam.py::test_build_and_import FAILED           [100%]
[   40s]
[   40s] =================================== FAILURES ===================================
[   40s] ____________________________ test_build_and_import _____________________________
[   40s]
[   40s] virtual_env = PosixPath('/tmp/mesonpy-test-venv-1u0kttug/bin/python')
[   40s] tmp_dir_session = PosixPath('/tmp/pytest-of-abuild/pytest-9/test0/mesonpy-test-9pyibyzf')
[   40s]
[   40s]     @pytest.mark.skipif(platform.system() != 'Linux', reason='Unsupported on this platform for now')
[   40s]     @pytest.mark.skipif(sys.version_info < (3, 8), reason='Example only supports >=3.8')
[   40s]     @pytest.mark.skipif(platform.python_implementation() == 'PyPy', reason='PyPy bug on creating the venv')
[   40s]     def test_build_and_import(virtual_env, tmp_dir_session):
[   40s]         """Test that the wheel for the spam example builds, installs, and imports."""
[   40s] >       wheel = build_project_wheel(
[   40s]             package=examples_dir / 'spam',
[   40s]             outdir=tmp_dir_session
[   40s]         )
[   40s]
[   40s] tests/docs/examples/test_spam.py:17:
[   40s] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
[   40s] tests/docs/examples/conftest.py:29: in build_project_wheel
[   40s]     return outdir / mesonpy.build_wheel(
[   40s] mesonpy/__init__.py:987: in build_wheel
[   40s]     return project.wheel(out).name
[   40s] mesonpy/__init__.py:935: in wheel
[   40s]     wheel = self._wheel_builder.build(self._build_dir)
[   40s] mesonpy/__init__.py:599: in build
[   40s]     self._install_path(whl, counter, origin, destination)
[   40s] mesonpy/__init__.py:571: in _install_path
[   40s]     wheel_file.write(origin, location)
[   40s] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
[   40s]
[   40s] self = <wheel.wheelfile.WheelFile [closed]>
[   40s] filename = '/home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/build/_spam.cpython-38-x86_64-linux-gnu.so'
[   40s] arcname = 'spam/_spam.cpython-38-x86_64-linux-gnu.so', compress_type = None
[   40s]
[   40s]     def write(self, filename, arcname=None, compress_type=None):
[   40s] >       with open(filename, 'rb') as f:
[   40s] E       FileNotFoundError: [Errno 2] No such file or directory: '/home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/build/_spam.cpython-38-x86_64-linux-gnu.so'
[   40s]
[   40s] /usr/lib/python3.9/site-packages/wheel/wheelfile.py:143: FileNotFoundError
[   40s] ----------------------------- Captured stdout call -----------------------------
[   40s] + meson setup --native-file=/home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-native-file.ini -Ddebug=false -Doptimization=2 --prefix=/usr /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/build
[   40s] Directory already configured.
[   40s]
[   40s] Just run your build command (e.g. ninja) and Meson will regenerate as necessary.
[   40s] If ninja fails, run "ninja reconfigure" or "meson --reconfigure"
[   40s] to force Meson to regenerate.
[   40s]
[   40s] If build failures persist, run "meson setup --wipe" to rebuild from scratch
[   40s] using the same options as passed when configuring the build.
[   40s] To change option values, run "meson configure" instead.
[   40s] + meson compile
[   40s] [0/1] Regenerating build files.
[   40s] Cleaning... 2 files.
[   40s] The Meson build system
[   40s] Version: 0.63.3
[   40s] Source dir: /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam
[   40s] Build dir: /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/build
[   40s] Build type: native build
[   40s] Project name: spam
[   40s] Project version: undefined
[   40s] C compiler for the host machine: cc (gcc 12.2.1 "cc (SUSE Linux) 12.2.1 20220830 [revision e927d1cf141f221c5a32574bde0913307e140984]")
[   40s] C linker for the host machine: cc ld.bfd <IP_ADDRESS>20810-1
[   40s] Host machine cpu family: x86_64
[   40s] Host machine cpu: x86_64
[   40s] Program python found: YES (/usr/bin/python3.9)
[   40s] Found pkg-config: /usr/bin/pkg-config (1.8.0)
[   40s] Build targets in project: 1
[   40s]
[   40s] spam undefined
[   40s]
[   40s]   User defined options
[   40s]     Native files: /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-native-file.ini
[   40s]     backend     : ninja
[   40s]     debug       : false
[   40s]     optimization: 2
[   40s]     prefix      : /usr
[   40s]
[   40s] Found ninja-1.11.1 at /usr/bin/ninja
[   40s] [1/2] Compiling C object _spam.cpython-39-x86_64-linux-gnu.so.p/src_spammodule.c.o
[   40s] [2/2] Linking target _spam.cpython-39-x86_64-linux-gnu.so
[   40s] + meson install --destdir /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-2dbz4_tm/install
[   40s] ninja: Entering directory `/home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/build'
[   40s] ninja: no work to do.
[   40s] Installing _spam.cpython-39-x86_64-linux-gnu.so to /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-2dbz4_tm/install/usr/lib64/python3.9/site-packages/spam
[   40s] Installing /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/src/__init__.py to /home/abuild/rpmbuild/BUILD/meson_python-0.10.0/docs/examples/spam/.mesonpy-2dbz4_tm/install/usr/lib/python3.9/site-packages/spam
[   40s] Copying files to wheel...
[   40s] [0/1] spam/_spam.cpython-38-x86_64-linux-gnu.so
[   40s] =========================== short test summary info ============================
[   40s] FAILED tests/docs/examples/test_spam.py::test_build_and_import - FileNotFound...
[   40s] ============ 1 failed, 50 passed, 1 deselected, 1 xpassed in 17.42s ============

Hum, interesting. I'll need to reproduce.

I have meson 0.64.0 on Gentoo here, and it fails with a different error:
E                   ValueError: Extension module 'spam/_spam.cpython-310-x86_64-linux-gnu.so' not compatible with Python interpreter. Filename suffix '.cpython-310-x86_64-linux-gnu.so' not in {'.abi3.so', '.so', '.cpython-311-x86_64-linux-gnu.so'}.

I can reproduce this by running nox.
Full log (300k): test.txt

There is an issue with the test setup indeed, I'll fix that. Although, it seems that Meson does not reconfigure the project if the native file provided points to executable at different locations. It's probably okay, but a bit surprising. @eli-schwartz Is it expected that if a project is build with a native file pointing to a different python executable the project is not reconfigured?

Meson explicitly exits successfully after printing an informational message, if you attempt to meson setup into an already configured build directory -- telling you that you don't need to do that, it's already configured.
If you're newly configuring against a different version of python, you should probably be using a different unique build directory and maybe for test purposes also be doing all work inside a context manager for a temporary directory.

using a different unique build directory and maybe for test purposes also be doing all work inside a context manager for a temporary directory.

We do that when packaging the rpm package. However the tests outside of tox don't seem to do that.

@bnavigator There is an issue with this specific test. I'm fixing it.

Thanks!


login-redirect.html missing

@asadsahi can you please help me
after login on redirect error occurred no route found with login-redirect.html

If this issue is still valid, please create a minimal reproduction and link here and I might have a look. Thanks


auth-mailchimp-sync with upgraded users for anonymous to a user with email

What feature would you like to see?
I use anonymous users to store unauthenticated user data in my RTDB so that when the user does sign in they keep all their data. I then use the link operation to upgrade anonymous user to one with email.
How would you use it?
On this upgrade i would like to sync the email with Mailchimp.

Hey @perryjsteward, thanks for the feature request. it is currently not possible to update Mailchimp if a user initially logs in as anonymous as described here.
I'd advise tracking this issue for further updates on backfilling  Mailchimp with users who aren't on the mailing list because, for instance, they initially signed up as anonymous.


Replace sqlite3 with better-sqlite3 library

I tried briefly and ran into some odd node-abi issues, which led to electron upgrades, which led to quasar upgrades.
If someone can attempt this, it would be good.

Should we just close this issue? Is this required anymore?


No Devices discovered.

Hi. I installed the adapter and startet an instance. Also I provided my login credentials.
For me it looks like the adapter starts. At least the bulp turns green. :)
However. I cant see any "devices" in "objects". For sure I am doing something wrong but what the **** is it?
Any help would be much appreciated.

Please See  #6

Please See  #6


Checkout cache files when locked by version control UE 5.2

A rebase of https://github.com/disguise-one/RenderStream-UE/pull/92

QA PASSED


2019_09_12 Cloned Source Fails to Build on openSUSE Linux

The whole console output MIGHT be available from
https://temporary.softf1.com/2019/bugs/2019_09_12_Agar_Fails_to_Compile_bugreport_t1.txt
but the first error seems to be
gcc -M  -march=native -D_AGAR_INTERNAL -D_DEFAULT_SOURCE -D_BSD_SOURCE -I/home/ts2/m_local/lib/Agar/kompil/libagar/include -D_XOPEN_SOURCE=600 -D_AGAR_CORE_INTERNAL -Ix86_64-unknown-linux-gnu byteswap.c class.c config.c core.c cpuinfo.c data_source.c db.c dir.c dso.c error.c event.c exec.c file.c getopt.c load_integral.c load_real.c load_string.c load_version.c object.c string.c tbl.c text.c time.c time_dummy.c timeout.c threads.c vasprintf.c vsnprintf.c user.c user_dummy.c user_getenv.c variable.c vec.c time_posix.c time_renderer.c time_gettimeofday.c net.c net_dummy.c net_bsd.c user_posix.c
In file included from /usr/include/sys/types.h:132:0,
                 from /usr/include/stdlib.h:314,
                 from /home/ts2/m_local/lib/Agar/kompil/libagar/include/agar/core/core.h:40,
                 from byteswap.c:7:
./time.h:4:3: error: #error "Must be included by object.h"
 # error "Must be included by object.h"
   ^~~~~
In file included from /usr/include/sys/select.h:43:0,

I do admit that I  am running relatively old openSUSE version, "openSUSE Leap"  version 42.3, but that should not be a problem for a GUI library that aims to be portable.

No luck. The new console output MIGHT be available from
https://temporary.softf1.com/2019/bugs/2019_09_14_Agar_Fails_to_Compile_bugreport_t1_compilation_attempt_01.txt
The first error line seems to be
gcc -march=native -ftree-vectorize  -D_AGAR_INTERNAL -D_DEFAULT_SOURCE -D_BSD_SOURCE  -I/home/ts2/m_local/lib/Agar/kompil/libagar/include -U_XOPEN_SOURCE -D_XOPEN_SOURCE=600        -I/usr/include -D_AGAR_CORE_INTERNAL  -fPIC -o string.o -c string.c
string.c:76:35: error: 'AG_STRING_BUFFERS_MAX' undeclared here (not in a function); did you mean 'AG_BUFFER_MAX'?
 static char *_Nullable agPrintBuf[AG_STRING_BUFFERS_MAX];
                                   ^~~~~~~~~~~~~~~~~~~~~
                                   AG_BUFFER_MAX
string.c:80:8: error: unknown type name 'AG_FmtStringExt'
 static AG_FmtStringExt *_Nullable agFmtExtensions = NULL;
        ^~~~~~~~~~~~~~~
string.c:111:9: error: unknown type name 'AG_FmtString'; did you mean 'AG_VecString'?
 PrintU8(AG_FmtString *_Nonnull fs, char *_Nonnull dst, AG_Size dstSize)
         ^~~~~~~~~~~~
         AG_VecString

Would it make sense if I tried to set up a
https://travis-ci.org/

for the Agar? As of 2019_09_14 I do not know, if they have openSUSE Linux option but I suspect that for a start almost any distro would do with the libagar.

Yes, that would be very helpful. I tried to get a recent OpenSUSE running under VirtualBox but it locked up during installation for some reason. I could not reproduce this in other distros.
AG_STRING_BUFFERS_MAX is in core/string.h:40, which is included by core/string.c. Those errors:
class.c:65:11: warning: incompatible implicit declaration of built-in function 'strrchr'
class.c:65:11: note: include '<string.h>' or provide a declaration of 'strrchr'
are very odd, because core/class.c does include <string.h> on line 33.
I wonder why is the compiler apparently confusing agar's core/string.h with the system string.h (as it did with <time.h> until I renamed agar's core/time.h to core/agtime.h)? The compiler seems to be behaving as if /home/ts2/m_local/lib/Agar/kompil/libagar/include/agar/core was added as a standard include (-I) path, which should never be the case.

Please re-open if this is still an issue with latest (SVN) sources.


Incompatible types issue with IBM Semeru Runtime

When compiling codes which use Sundrio to generate classes with IBM Semeru Runtime (previously known as AdoptOpenJDK 11 Openj9 JVM), sometimes only withNew*(byte[]) methods will be generated, while withNew*(String) methods are expected in the client code. This will trigger incompatible types compilation error similar to:
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/test/strimzi-kafka-operator/cluster-operator/src/test/java/io/strimzi/operator/cluster/model/CruiseControlTest.java:[541,47] incompatible types: java.lang.String cannot be converted to byte[]
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

On Temurin runtime (previously known as AdoptOpenJDK 11 Hotspot JVM) and OpenJDK11, withNew*(String) methods will be generated and this error would not occur during compilation.
It looks like the root cause might lie in here: https://github.com/sundrio/sundrio/blob/533e4b9b6ecc6ed2c9580c20162d296378e7a6f0/annotations/builder/src/main/java/io/sundr/builder/internal/utils/BuilderUtils.java#L312
The code just chooses the first constructor which has only one argument. Probably on IBM Semeru runtime the String(byte[]) constructor comes first.
Could anyone please look into this issue and help to fix it? Thanks!

Thanks for the detailed explanation, I will look into it asap.

Thanks @iocanel

@kun-lu20: While I wan't able to reproduce thte issue, the code could be simplified and be more deterministic.
I'll mere #292 and release shortly.

@iocanel Thank you so much!


Front Page links to top level

The aim is to have the front page that reflects the structure created for the pages relating to the product.
Currently, the front page displays the placeholders that were created initially but as work has moved on for the product knowledge base the links are no longer correct.

From the product team, we want to have a page that describes every part of the product, but we cannot update the front page as we do not control any part of the knowledge base outside of the directory "data-collection".
We would like the engineering team to update the front page to show the card for "Docs PRODUCT DOCUMENTATION":

How it works | /data-collection/huma-product/how-it-works
Modules | /data-collection/modules/
ePROS / Licensed Questionnaires | /data-collection/epros-licensed-questionnaires/
Features | /data-collection/features/

resolved


*: Remove embeddedDictionary and ExternalDictionary

What problem does this PR solve?
Issue Number: ref #5628
Problem Summary:
What is changed and how it works?
Check List
Tests

[x] Unit test
[x] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

Question: Is it safe to delete this files?

Question: Is it safe to delete this files?

@ywqzzy  I think it is safe. Those files are not used and local dictionary encoding will not be used in the near future.

/merge

/run-all-tests

/rebuild

/run-all-tests

/run-integration-tests

/run-unit-tests

/run-all-tests

/run-unit-tests

/run-unit-tests

/run-unit-tests


Don't clip when the clip path is empty (issue #12306)

/botio test

/botio test

Unfortunately there appears to be a number of regressions, see an incomplete list below:

issue13447-eq-page1
bug1669099-page1
There's also movement in what appears to be most, if not all, Type3-related tests

Unfortunately there appears to be a number of regressions, see an incomplete list below:
* issue13447-eq-page1

* bug1669099-page1

* There's also movement in what appears to be most, if not all, Type3-related tests

Likely related to https://github.com/mozilla/pdf.js/blob/379125c37ff58cfb86e3bbd2eca5760fb2fcb061/src/display/canvas.js#L2823
I changed it to this.ctx.clip() which should be better.

/botio test

Likely related to
https://github.com/mozilla/pdf.js/blob/379125c37ff58cfb86e3bbd2eca5760fb2fcb061/src/display/canvas.js#L2823
I changed it to this.ctx.clip() which should be better.

That really cannot explain all of the movement in Type3-tests though, since the code-path in question only matter for annotations...

/botio test

/botio makeref

/botio-windows makeref

I completely missed that there was a regressions in the tiling-pattern-large-steps-page1 test-case (look at its right edge).
@calixteman Can you please take a look into that, and fix it in a follow-up?

Yep, it's likely because of https://github.com/mozilla/pdf.js/blob/5bbed400f2e82422c5bd7cc507b2c14cc1dc16f1/src/display/pattern_helper.js#L622 (it's just a guess).


Why does local deployment still need to access github?

I deployed in my local VM and got below ERROR, Why need to access GitHub to check the latest version?
2023-12-22 15:33:11.682653 ERROR version/version.go:40 get github version fail: Get "https://api.github.com/repos/ccfos/nightingale/releases/latest": dial tcp <IP_ADDRESS>:443: i/o timeout
What would you like to be added:
Why is this needed:

To alert users of a new release, a notification will appear here if the version is lower than the new.

I think you'd better set a switch that can be turned off.


Scikit-sparse not (default) available for Ubuntu 22

https://pypi.org/project/scikit-sparse/ states that scikit-sparse has  python version requirement of < 3.10
Since the default version on Ubuntu 22 is 3.10 it makes it unavailable

It can easily be build for 3.10 my simply changing the requrements.txt to <= 3.10

Also note that pyproject.toml is missing requirements for 3.10, and it needs an unpinned numpy version for future Python versions. Consider removing the existing numpy pins and depending just on oldest-supported-numpy instead.


React element not rendered properly only on production builds

Describe the bug
I'm having an issue with a React library (that I created), for some reason it works properly on dev mode, but it doesn't on production builds.
I noticed the bug only happens with the default import (that seems to import the Common JS build), but it doesn't happen with any other build target (UMD and ESM)
Reproduction
To reproduce the bug it's enough to bootstrap a new app with npx init vite using the React template.
Install the library with npm install react-resize-aware.
Then, edit the src/App.jsx file to be:
import { useState } from 'react';
import logo from './logo.svg';
import './App.css';
import useResizeAware from 'react-resize-aware';

function App() {
  const [listener] = useResizeAware();

  return (
    <div>
      {listener}
      Test
    </div>
  );
}

export default App;

If you run the app on dev mode and you inspect the resulting DOM, an iframe will be visible.
If you build the app and run it with vite preview, the iframe is replaced by a <t /> element.
System Info
System:
    OS: macOS 12.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 386.64 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    Yarn: 1.22.15 - ~/.nvm/versions/node/v16.13.0/bin/yarn
    npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 96.0.4664.110
    Safari: 15.2
  npmPackages:
    @vitejs/plugin-react: ^1.0.7 => 1.1.3
    vite: ^2.7.2 => 2.7.3

Used Package Manager
npm
Logs
$ /private/tmp/vite/node_modules/.bin/vite build --debug
  vite:config bundled config file loaded in 42.54ms +0ms
  vite:config using resolved config: {
  vite:config   plugins: [
  vite:config     'alias',
  vite:config     'vite:react-babel',
  vite:config     'vite:react-refresh',
  vite:config     'vite:react-jsx',
  vite:config     'vite:modulepreload-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html-inline-script-proxy',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:watch-package-data',
  vite:config     'vite:build-html',
  vite:config     'commonjs',
  vite:config     'vite:data-uri',
  vite:config     'rollup-plugin-dynamic-import-variables',
  vite:config     'vite:asset-import-meta-url',
  vite:config     'vite:build-import-analysis',
  vite:config     'vite:esbuild-transpile',
  vite:config     'vite:reporter',
  vite:config     'vite:load-fallback'
  vite:config   ],
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     polyfillModulePreload: true,
  vite:config     outDir: '/private/tmp/vite/dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     cssTarget: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     sourcemap: false,
  vite:config     rollupOptions: { input: '/private/tmp/vite/index.html' },
  vite:config     minify: 'esbuild',
  vite:config     terserOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     reportCompressedSize: true,
  vite:config     chunkSizeWarningLimit: 500,
  vite:config     watch: null,
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] }
  vite:config   },
  vite:config   resolve: { dedupe: [ 'react', 'react-dom' ], alias: [ [Object], [Object] ] },
  vite:config   optimizeDeps: {
  vite:config     include: [ 'react/jsx-dev-runtime' ],
  vite:config     esbuildOptions: { keepNames: undefined, preserveSymlinks: undefined }
  vite:config   },
  vite:config   configFile: '/private/tmp/vite/vite.config.js',
  vite:config   configFileDependencies: [ 'vite.config.js' ],
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     build: {}
  vite:config   },
  vite:config   root: '/private/tmp/vite',
  vite:config   base: '/',
  vite:config   publicDir: '/private/tmp/vite/public',
  vite:config   cacheDir: '/private/tmp/vite/node_modules/.vite',
  vite:config   command: 'build',
  vite:config   mode: 'production',
  vite:config   isProduction: true,
  vite:config   server: { fs: { strict: true, allow: [Array], deny: [Array] } },
  vite:config   preview: {
  vite:config     port: undefined,
  vite:config     strictPort: undefined,
  vite:config     host: undefined,
  vite:config     https: undefined,
  vite:config     open: undefined,
  vite:config     proxy: undefined,
  vite:config     cors: undefined
  vite:config   },
  vite:config   env: { BASE_URL: '/', MODE: 'production', DEV: false, PROD: true },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     warnOnce: [Function: warnOnce],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen],
  vite:config     hasErrorLogged: [Function: hasErrorLogged]
  vite:config   },
  vite:config   packageCache: Map(0) { set: [Function (anonymous)] },
  vite:config   createResolver: [Function: createResolver]
  vite:config } +2ms
vite v2.7.3 building for production...
✓ 35 modules transformed.
dist/assets/favicon.17e50649.svg   1.49 KiB
dist/assets/logo.ecc203fb.svg      2.61 KiB
dist/index.html                    0.52 KiB
dist/assets/index.cfbfdb95.js      0.91 KiB / gzip: 0.52 KiB
dist/assets/index.cd9c0392.css     0.75 KiB / gzip: 0.48 KiB
dist/assets/vendor.2b1a1f45.js     130.18 KiB / gzip: 42.06 KiB
✨  Done in 0.84s.

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

i have test some cases , and found that u can add 'module' field in 'react-resize-aware' package.json, then whether dev or prod mode would be ok. like this:

the reason is: if u don't specified the 'module' field ,  whether in dev/prod mode, vite (esbuild/rollup) will resolve the 'react-resize-aware' package by the 'main' fileld, which is dist/index.js , and your package was pack by microbundle, in microbundle docs, the 'main' field is for CJS , and u should include the 'module' field according the docs https://github.com/developit/microbundle


Optimization - refactor to reuse javascript objects

There are a number of code segments in which a frequent event (pubsub msg, tick, etc) will instantiate new javascript object(s) such as a THREE Vector3 each time. Per AFRAME performance suggestions, these should reuse a object probably set as a property of the contextual object (e.g. user cam for A/V stream frustrum culling). The performance overhead of instantiation and garbage collection more likely overshadows any benefit of memory saved from dereferencing unused objects.

Scanning through as of 651d859, there does not seem to be any remaining cases of these in these.


Add and apply flake8 config

Correctly added and applied Flake8 config, according to guidelines given by GDS.

Spoken to  theTech Leads in the engineering team and the app should just use flake8 and not black.

As a note, when the project started, the direction received was to use Black (as per @pipwilson's direction). We then subsequently received indication to use Flake8. This PR applies Flake8, and so satisfies that remit. Removing Black will not really achieve anything given that the project was originally developed using it as a standard - ideally it would continue in the same direction to ensure consistency.


Feature/hsl api endpoint

Add hsl api endpoint to website to allow serverside fetching to prevent API key from being out in the open and allow dynamic fetching so the ttimetable can be rendered client side.

As this is not being used anywhere (yet), I think we probably don't want to merge this before we have the UI-functionality added as well. Can you do a separate PR for that that is built on top of this one?


finish first pass over docs

Codecov Report

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

@@           Coverage Diff           @@
##           master      #49   +/-   ##
=======================================
  Coverage   86.42%   86.42%
=======================================
  Files           3        3
  Lines         140      140
=======================================
  Hits          121      121
  Misses         19       19

Impacted Files
Coverage Δ

src/LiveServer.jl
25% <ø> (ø)
:arrow_up:

src/file_watching.jl
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 244c57f...521b7f0. Read the comment docs.


Installation instructions ask for sudo pip install

The installation instructions for mbed-CLI ask the user to install using pip, and suggests using sudo pip install mbed-cli on macOS and Linux. According to this stackoverflow answer, doing this is incorrect and can cause problems on recent versions of macOS.
Instead, the instructions should recommend installing with pip install mbed-cli --user. This might be a problem since it requires adding the install location to $PATH (in my case: ~/Library/Python/2.7/bin)

ARM Internal Ref: MBOTRIAGE-453


tl.store throws error when storing into tensor with extended dimension with interpreter

Describe the bug
When doing a tl.store into a tensor with repeated dimension (i.e. repeat(a, 'b l -> b l d', d=2) aka there is a dimension with stride 0), interpreter seems to throw an error even though the address being stored into doesn't involve the dimension with stride 0.
The following code works without interpreter but doesn't with interpreter.
import torch
import triton
import triton.language as tl
from einops import repeat
def example(x):
    b, l, d = x.shape
    grid = (b, l, d)
    with torch.cuda.device(x.device.index):
        _example_kernel[grid](
            x,
            x.stride(0),x.stride(1),x.stride(2)
        )
    return x

@triton.jit
def _example_kernel(
    X,
    stride_x_b, stride_x_l, stride_x_d
):
    pid_b = tl.program_id(0)
    pid_l = tl.program_id(1)
    pid_d = tl.program_id(2)

    x_ptr = X + pid_b * stride_x_b + pid_l * stride_x_l
    tl.store(x_ptr, 1)

if __name__ == "__main__":
    a = -torch.rand((2,2), device='cuda')
    a = repeat(a, 'b l -> b l d', d=2)
    print(a)

    a = example(a)
    print(a)

Running this script with TRITON_INTERPRET=1 returns an error
File "/home/xxx/miniconda3/envs/mamba/lib/python3.10/site-packages/triton/runtime/interpreter.py", line 1063, in _restore_args_dev
    arg_dev.data.copy_(arg_hst.to(arg_dev.device).data)
RuntimeError: unsupported operation: more than one element of the written-to tensor refers to a single memory location. Please clone() the tensor before performing the operation.RuntimeError: unsupported operation: more than one element of the written-to tensor refers to a single memory location. Please clone() the tensor before performing the operation.

Running with interpreter mode off seems to do fine.
I know that pytorch would do this if the whole tensor being stored into has repeated addresses. However, in the above case,  the dimension with stride 0 is not involved in the store and this error shouldn't happen? (Running without interpreter seems to do fine as well)
Environment details
Triton==3.0.0 GPU==RTX 2080Ti python==3.10 torch==2.3.0

The problem is with the repeat method, which invokes expand (I guess).
For now, you can use
    with torch.cuda.device(x.device.index):
        _example_kernel[grid](
            x.clone(),
            x.stride(0),x.stride(1),x.stride(2)
        )

I'd love to look into solving this one! It seems definitely manageable but I would greatly appreciate any guidance as a first time contributor :)

I think it might be related to the copy statement used by the interpreter to handle the tl.store statement. i.e.
File "/home/xxx/miniconda3/envs/mamba/lib/python3.10/site-packages/triton/runtime/interpreter.py", line 1063, in _restore_args_dev
    arg_dev.data.copy_(arg_hst.to(arg_dev.device).data)

Maybe it doesn't take in to account that the address in tl.store actually doesn't have repeated address.

It has nothing to do with tl.store.
Problems are on the CPU side related with how the interpreter manages memory

I think I found the issue and am working on a PR! i'm thinking of just changing this part of the triton code
# runtime/interpreter.py line 1069
def _restore_args_dev(self, args_dev, args_hst, kwargs, kwargs_hst):
        for arg_dev, arg_hst in zip(args_dev, args_hst):
            if hasattr(arg_dev, "data_ptr"):
                arg_dev.data.copy_(arg_hst.to(arg_dev.device).data)

to this
def _restore_args_dev(self, args_dev, args_hst, kwargs, kwargs_hst):
        for arg_dev, arg_hst in zip(args_dev, args_hst):
            if hasattr(arg_dev, "data_ptr"):
                if arg_dev.is_contiguous():
                    arg_dev = arg_dev.contiguous()
                    arg_dev.data.copy_(arg_hst.to(arg_dev.device).data)
                else:
                    arg_dev.data.copy_(arg_hst.to(arg_dev.device).data)

Would a PR like this be accepted?

def _restore_args_dev(self, args_dev, args_hst, kwargs, kwargs_hst):
        for arg_dev, arg_hst in zip(args_dev, args_hst):
            if hasattr(arg_dev, "data_ptr"):
                if not arg_dev.is_contiguous():
                    arg_dev = arg_dev.contiguous()
                arg_dev.data.copy_(arg_hst.to(arg_dev.device).data)

Probably not. It has side effects on the original arguments

Oh, I also think that arg_dev won't be the original arg_dev anymore (if you don't have other code), so the data do not get copied.

Hmm I'll look into a better solution then

I have a draft idea. Feel free to implement something if you'd like
First, this example can be problematic itself. grid = (b, l, d), but x's storage is (l, d).
Second, I think we should copy the storage of tensor but not the tensor itself. That being said, the .cpu() method in the current interpreter implementation can be improved.

@EmmettBicker assign it to you for now. I won't be touching this feature for now :)

More hints: copy the storage of tensors and reshape using as_strided might be enough.
We also want to add a few test cases to validate the method.

Thank you :)!
By copying the storage, do you mean manipulating arg_dev.data? Because I've been working on something like this because I can't find a way to do .copy_ on a tensor with a stride of 0 at all?
# first, instead of arg_hst = arg_dev.cpu(), do
original_size = arg_dev.size()
original_stride = arg_dev.stride()
arg_hst = arg_dev.cpu().as_strided(original_size , original_stride)

```py

# This still doesn't work, I think it's just impossible to do copy_ with a tensor w/ a 0 stride
# arg_dev.data.copy_(arg_hst.to(arg_dev.device).data))
# This works but seems dangerous
arg_dev.data = arg_hst.to(arg_dev.device).data

That's as close as I've gotten, what do you think about smth like that? I'm concerned about just using .data because I know it breaks some things in pytorch but I was wondering if it was at acceptable in this circumstance

I meant torch tensor storage. https://pytorch.org/docs/stable/storage.html#torch.UntypedStorage

Ok! I'll look into doing that and do some tests to validate my solution once I get something that doesn't raise an exception. Thank you for all your help, I really appreciate it :)

@wyc1997 Hi! This should now work on the next nightly build of triton :)


Question regarding computation of q(z| x, y) in code.

Hi @mazrk7 ,
Thanks a lot for the code, first of all. I had a question regarding your calculation of q(z|x,y) here: https://github.com/mazrk7/gmvae/blob/master/scripts/gmvae.py#L246
Here, you used the y sampled from qy.
In RuiShi's original code, he uses the ground-truth cluster labels to compute q(z|x, y), as can be seen on this and the next line: https://github.com/RuiShu/vae-clustering/blob/master/gmvae_k.py#L49
Is this your own modification to make the model unsupervised? It doesn't say so in the Readme, so I wanted to confirm it is not a typo or something.
Thanks in advance!

Ayush.

Hi @aayushARM,
Thanks for taking interest!
First of all, I believe both mine and RuiShi's original implementation are unsupervised.
The difference is that in RuiShi's code, he marginalises over all k class values for inference of q(z|x,y), following from Kingma's M2 model (see Section 3.1.2 in particular).
In my case, I use the Gumbel-Softmax distribution as a continuous relaxation of the discrete variable to directly allow backpropagation through y ~ q(y|x) (see Section 3.3 of the corresponding paper, which comments on this).
I believe I tested both approaches at some point and found the latter to be better performing. Hope that clarifies things and let me know if you have any other questions :)
Mark

Thanks for the response, @mazrk7 !
I understand the difference between his and your implementation better now. I also had another quick question regarding this:
I'm interested in using the GMVAE framework for anomaly detection, and for that, the only difference would be that after training,  instead of finding cluster label 'y' for each test image as you do, I need to find the likelihood of the sampled 'z' corresponding to the test image w.r.t all the clusters and then sum them up:

(here, p(z'|c') is the same as p(z|y) in your code)
The images producing LL lower than a threshold can then be regarded as anomalies. In your code, you have a Fully-connected layer that maps from y -> p(z|y), which gives an inferred {Mean, Std} of the prior distribution of the cluster from which the test image came. To find LL, I need such {Mean, Std} pairs for ALL the clusters. I'm wondering what's the right way to do that?

No problem!
Yes, the fully-connected layer y -> p(z|y) does only infer the parameters of the prior associated with a specific cluster (i.e. y=k). But then you could also iterate over each y value, as in https://github.com/mazrk7/gmvae/blob/master/scripts/gmvae.py#L152 when no mixture component indices are provided (clusters=None), so as to compute your p(z) log-likelihood. However, the prior distributions are not conditioned on the input images, so I think for your application you might want to iterate over all y values when sampling from the q(z|x,y) distribution and compute the log-likelihood for the q(z|x) mixture.
Does this help?

Hey,
Sorry for the late reply! I got stuck in some other unavoidable work.
And thanks for clarifying that I can iterate for all y over p(z|y) values to find p(z), I'll try this out.
Regarding your suggestion to "iterate over all y values when sampling from the q(z|x,y) distribution and compute the log-likelihood for the q(z|x) mixture", do you mean if y can take 10 different values, I sample 10 z values, and after that compute the LL of each z w.r.t to the corresponding q(z|x,y)? This will be like find LL of a sample w.r.t the distribution it was sampled from in the first place, which doesn't make sense. Maybe I'm missing something here?

Hey, no sorry I mean sample z once from q(z|x,y) and then use the logits or probabilities of the q(y|x) distribution to represent all y values. You can then just take the log sum of your log probabilities for the sampled z, scaled by the mixture probabilities, as in your earlier equation.
In case that's not clear, maybe have a look at how the TensorFlow Probability library does it: https://github.com/tensorflow/probability/blob/v0.11.1/tensorflow_probability/python/distributions/mixture_same_family.py#L346

Hi @aayushARM, is it alright if I close the issue?

Hey, yeah the issue is largely solved at this point. I'm closing it. Thanks for your help! :)


Wallet font is not BC Sans

Font currently appears to be Helvetica Neue or similar. Needs changing to BC Sans.

There seems to be a mix of BC Sans and a different font (not sure what it is). This is all over the app.

@knguyenBC @alexgmetcalf @amanji Yes, it'll be left over in places we have not refactored the UI extensively by eliminating a component that really doesn't add much. One of us will need to make a pass through the app and ax all the older components.

@jleach are we ballparking this ticket until a thorough pass through is done? This ticket is put in done but I doubled checked and it's still inconsistent in many areas.


[Enhancement] Add FE tablet schedule to information_schema

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Problem Summary(Required) ：

This PR adds FE tablet schedule information to information_schema, so as to debug tablet repair/balance problems more easily.
Note that this information is only available in FE leader, so MySQL client should connect to FE leader to query this table.
Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

run starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5

@Mergifyio backport branch-2.4


[Bug]: Binance Wallet (injected) broken as of 2.13.1

Current Behavior

Cannot add property isUnlocked, object is not extensible

Expected Behavior
Binance Wallet should connect and function.
Steps To Reproduce

Install latest (2.13.1) Binance Wallet extension: https://chrome.google.com/webstore/detail/binance-wallet/fhbohimaelbohpjbbldcngcnapndodjp and create account/address.
Go to https://reactdemo.blocknative.com/
Press Select a Wallet
Select Binance Smart Wallet
See error Cannot add property isUnlocked, object is not extensible

What package is effected by this issue?
@web3-onboard/injected
Is this a build or a runtime issue?
Runtime
Package Version
2.5.0
Node Version
16.16.0
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Anything else?
Works with previous versions of the extension: v2.13.0 and down.
Tested locally with
"@web3-onboard/core": "^2.5.0",
"@web3-onboard/injected-wallets": "^2.0.14",

Seems something changed in the extension that no longer allows writing to window.BinanceChain here:
https://github.com/blocknative/web3-onboard/blob/fb81fbb38c5629bde0fac681e86bfe382092bda4/packages/injected/src/wallets.ts#L71
Sanity Check

[X] If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a Minimal, Reproducible Example.

@ReflectiveChimp lookin into this now. Will update here on status changes

@ReflectiveChimp pr to fix this issue - #1174

@ReflectiveChimp A fix is merged into staging and available for testing with the 2.0.15-alpha.2 version of the injected package. A production release will happen in the next 24hrs

@Adamj1232 Thank you for quick turn around, can confirm the fix works.


Actions: Provide trigger to run actions on user management events

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[X] I have joined the ZITADEL chat

Describe your problem
I can't execute custom code to react to user lifecycle/management events in ZITADEL.
Triggers for actions are currently limited to few use cases. While we will make additional triggers available with https://github.com/zitadel/zitadel/issues/5101 , this issue exists to make sure that this use case is covered under the new implementation.
Describe your ideal solution
As a developer, I can execute custom code when a user has been created/updated/deleted, so I can provision the user information or react with custom code to these changes
Use cases from different discussions with users/discovery calls:

user created / updated provision via SCIM to other applications, described in https://github.com/zitadel/zitadel/issues/6601
user deleted delete user in other applications
password change update legacy system or send an email

Version
No response
Environment
ZITADEL Cloud
Additional Context
related to https://github.com/zitadel/zitadel/issues/5101

This would be great for moving the email sending capabilities out to a microservice to render/send it via sendgrid etc.

This is now possible with our new actions v2.
As first part we have implemented the possibility to run them on each request.
You can find the docs here: https://zitadel.com/docs/apis/actionsv2/introduction
@stebenz @adlerhurst  Can we close this issue, as it is possible with the new actions?

This is now possible with our new actions v2.
As first part we have implemented the possibility to run them on each request.
You can find the docs here: https://zitadel.com/docs/apis/actionsv2/introduction
@stebenz @adlerhurst  Can we close this issue, as it is possible with the new actions?

Current not, as soon as https://github.com/zitadel/zitadel/issues/7246 is closed we can close this one as well


"Contribute on Github" instead of "Bring me to Github"

Changed the description of the Github button to avoid misunderstandings.
#210

It's done.

Just quickly checked the Github casing, but now where all set. Thanks again!


apns_send_message -> push_notifications.apns.APNSServerError: BadDeviceToken

Version: 1.6.1
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/push_notifications/apns.py", line 113, in apns_send_message
    certfile=certfile, **kwargs
  File "/usr/lib/python3.6/site-packages/push_notifications/apns.py", line 94, in _apns_send
    **notification_kwargs
  File "/usr/lib/python3.6/site-packages/apns2/client.py", line 83, in send_notification
    raise exception_class_for_reason(result)
apns2.errors.BadDeviceToken

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/project/src/api/views.py", line 203, in send_push_notification
    push.send_message(msg)  # ToDo: i18n
  File "/usr/lib/python3.6/site-packages/push_notifications/models.py", line 167, in send_message
    **kwargs
  File "/usr/lib/python3.6/site-packages/push_notifications/apns.py", line 120, in apns_send_message
    raise APNSServerError(status=reason_for_exception_class(apns2_exception.__class__))
push_notifications.apns.APNSServerError: BadDeviceToken

Drop all APNS tokens via admin interface.


change title on README

I left reviews and line comments and created a new file for de the Readme

Webooos


[REEF-972] Maven clean command should remove lang/cs/bin folder

JIRA:
REEF-972
Pull request:
This closes #

We decided to move all .NET builds into MSBuild. Also, MSBuild triggers the maven build, not the other way around. The reason for that is that REEF.NET depends on REEF Java, but not the other way around.

Oh, I see. You mean I need to use msbuild /target:Clean to clean up the msbuild output.
Thank you. Now, I understand more. I will close this issue and Jira.


Ignore blocked pipelines for badge rendering

Fixes: https://github.com/woodpecker-ci/woodpecker/issues/2337
Use the existing pagination helper to find the last pipeline that has a status != blocked. While it works, I'm not sure if that's the best solution. If you have any other suggestion, please let me know.

Sure, sounds like a better idea 😅

Thanks for your review!


FreeCad @FreeCAD-0.19.1.a88db11

The current Version is @018
https://github.com/FreeCAD/FreeCAD/releases/tag/0.19.1

The current Version is 0.19.2 now, but still not
I modified bucket/freecad.json to below temporarily.
{
    "version": "0.19.2",
    "description": "General-purpose parametric 3D CAD modeler and a building information modeling software with finite-element-method support.",
    "homepage": "https://www.freecadweb.org",
    "license": "LGPL-2.0-or-later",
    "architecture": {
        "64bit": {
            "url": "https://github.com/FreeCAD/FreeCAD/releases/download/0.19.2/FreeCAD-<IP_ADDRESS>b5e18a-WIN-x64-installer1.exe#/dl.7z",
            "hash": "5ed4d2609f5010a8f18af40f29b127ab5e0923dd5aa4b022f8ce35bbcfb54f44"
        }
    },
    "pre_install": "Remove-Item \"$dir\\`$*\", \"$dir\\Uninstall*\" -Recurse -Force",
    "bin": "bin\\FreeCADCmd.exe",
    "shortcuts": [
        [
            "bin\\FreeCAD.exe",
            "FreeCAD"
        ]
    ],
    "checkver": {
        "github": "https://github.com/FreeCAD/FreeCAD",
        "regex": "releases/download/([\\d.]+)/FreeCAD-(?<build>[\\w.]+)-WIN"
    },
    "autoupdate": {
        "architecture": {
            "64bit": {
                "url": "https://github.com/FreeCAD/FreeCAD/releases/download/$version/FreeCAD-$matchBuild-WIN-x64-installer.exe#/dl.7z"
            }
        },
        "hash": {
            "url": "$url-SHA256.txt",
            "regex": "(?sm):\\s+([a-fA-F\\d\\s]+)CertUtil"
        }
    }
}


Allow overriding colour in Gauge components

Hey, I just made a Pull Request!
Fixes #7705. Adds a color prop to Gauge, LinearGauge and GaugeCard so the color of the gauge can be arbitrarily set. Obviously this behaviour is hard to screenshot, so it basically looks exactly like the existing ones except with whatever color you like whenever you like. Here's one in fetching magenta, anyway:

And LinearGauge:

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@benjdlambert I've modified this according to your suggestion, but since the only change to the components is the thing that's hard to test, there are no tests 😬 I've added stories for each of them though.

@Rugvip thanks - think that's everything.

actually I seem to have ruined the API reports by trying to rebuild them to reflect my changes. Having another go


Request: Provide more updated versions

It would be more preferable if there was a process to release updated versions of tools which are low maintenance* and comparatively easier to build, such as curl
(* As opposed to something like Python, where, as I understand, the process is more involved.)

There are three general types of builds in the repo, in increasing order of update efforts:

some have no minimal.diff, and these will be the easiest to update
some have a minimal.diff, the patches would need to updated when you update the version
some like python/gcc/emacs need a bit more checking when updating (actually python might become easier if we figure out an automatic script for handling the addition of packages)

What do you think is the best way to update each of the above?

For (1), I guess we could monitor the upstream packages for updates through GitHub actions and have the packages built automatically. Here, the updates should only be monitored for the top level packages that are shipped as binaries to users (e.g. monitoring updates to bash, as opposed to, say its depenency, ncurses) since users care more about them.
For (2), it may be better to upstream some of the changes if the maintainers are not opposed to their inclusion. (3) still requires manual checks for now.


Before sending SOULTION_COMPLETE message, Product Manager verifies the solution

TODO elaborate

We will be introducing the Code Review Agent and the QA Agent for this purpose. Hence, closing this issue.


Add support for partial path match in the skip option

This is a fix for issue #124. The skip option is extended to support partial path match. Currently it is possible to exclude the vendor folder with this pattern only:
gas -skip "*vendor*" ./..

I extended the fileList to support also partial paths like this:
gas -skip vendor ./..

Getting the skip / inclusions lists right has been a bit of a nightmare. This looks like a sensible change


how to add image instead of Tab #1,Tab #...

Hey @ElaneirzGard, that's a good idea. I didn't have much time to work on Pager lately but I'm looking for people to help me so we can add this functionality!

any update for this ?

any update for this ?


Feat : homepage design #688

Related Issue
Closes #688
Screenshots

Checklist

[x] My code adheres to the established style guidelines of the project.
[ ] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

@JasonDsouza212 please review

@mandliyarajendra11, the changes made are not satisfactory. Currently, someone else is working on them. However, if she fails to complete the task, we can discuss it further and make the necessary changes accordingly.


Implement local ssh daemon

Description

Implement local ssh daemon
Related Issue(s)

Related https://github.com/gitpod-io/gitpod/issues/16836
Analysis Path ^1

Event vscode_desktop_ssh, with property kind: local-ssh
With funnel: connecting -> ? local-ssh-failure -> connected (got_destination)

Error Reporting ^1
How to test

Should test with platform stable, insiders and os linux macOS Windows

Clone this repo and switch to PR's branch
Exec commands below to install extension locally

yarn
yarn local-test

Restart VSCode to make sure daemon is up-to-date (need 10 seconds to exit) [^2], commands below can help test [^3]
Start workspace in Gitpod and Open in VSCode
It should able to start without password required
Stop workspace, and use VSCode Desktop recent (ctrl + R) to access the stopped workspace
It should ask you if you want to restart it
Run command Gitpod: Export all Logs should include local ssh loggings

‼  Major Test Points ‼

[ ] Local SSH can be controlled by  feature flag https://app.configcat.com/08da1258-64fb-4a8e-8a1e-51de773884f6/08da1258-6541-4fc7-8b61-c8b47f82f3a0/08da1258-6512-4ec0-80a3-3f6aa301f853?settingId=75503
[ ] Throw error inside localssh (i.e. reject here) errors should reported to segment https://app.segment.com/gitpod/sources/ide_team_playground/debugger
[ ] Should send event to segment https://app.segment.com/gitpod/sources/ide_team_playground/debugger with kind = local-ssh

[^2]: We need 10 second to avoid daemon exists too quickly with only one window trying to reload
[^3]: watch daemon process watch -n 1 "ps aux | grep '[d]aemon.js'"  and tail daemon loggings tail -f $TMPDIR/gitpod-vscode-daemon.log | grep <pid>

Let's make sure that this PR does not break existing semantic, hide local SSH gateway behind feature flag and merge, try to contain changes. No need to look in analytics yet.


Error on following "Build with Bazel in Android Studio"

I have followed the tutorials of : https://google.github.io/mediapipe/getting_started/android.html
But i faced this error:
This bazel problem
.

.
.
.
When i sync bazel, i faced error :
ERROR: An error occurred during the fetch of repository 'local_execution_config_python':
Traceback (most recent call last):
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/py/python_configure.bzl", line 210, column 33, in _create_local_python_repository
python_lib = _get_python_lib(repository_ctx, python_bin)
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/py/python_configure.bzl", line 130, column 21, in _get_python_lib
result = execute(repository_ctx, [python_bin, "-c", cmd])
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/remote_config/common.bzl", line 217, column 13, in execute
fail(
Error in fail: Repository command failed
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.
ERROR: Error fetching repository: Traceback (most recent call last):
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/py/python_configure.bzl", line 210, column 33, in _create_local_python_repository
python_lib = _get_python_lib(repository_ctx, python_bin)
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/py/python_configure.bzl", line 130, column 21, in _get_python_lib
result = execute(repository_ctx, [python_bin, "-c", cmd])
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/remote_config/common.bzl", line 217, column 13, in execute
fail(
Error in fail: Repository command failed
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.
.
.
.
I tried to search, and found sollution. Sollution is to turn off "app execution aliases"

.
.
.
But, i faced another error:
ERROR: An error occurred during the fetch of repository 'local_execution_config_python':
Traceback (most recent call last):
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/py/python_configure.bzl", line 208, column 32, in _create_local_python_repository
python_bin = get_python_bin(repository_ctx)
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/remote_config/common.bzl", line 46, column 23, in get_python_bin
python_bin = which(repository_ctx, "python3")
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/remote_config/common.bzl", line 27, column 25, in which
result = execute(repository_ctx, ["C:\Windows\System32\where.exe", program_name])
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/remote_config/common.bzl", line 217, column 13, in execute
fail(
Error in fail: Repository command failed
INFO: Could not find files for the given pattern(s).
ERROR: Error fetching repository: Traceback (most recent call last):
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/py/python_configure.bzl", line 208, column 32, in _create_local_python_repository
python_bin = get_python_bin(repository_ctx)
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/remote_config/common.bzl", line 46, column 23, in get_python_bin
python_bin = which(repository_ctx, "python3")
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/remote_config/common.bzl", line 27, column 25, in which
result = execute(repository_ctx, ["C:\Windows\System32\where.exe", program_name])
File "C:/users/adarm/_bazel_adarm/ghnafdkl/external/org_tensorflow/third_party/remote_config/common.bzl", line 217, column 13, in execute
fail(
Error in fail: Repository command failed
INFO: Could not find files for the given pattern(s).
.
.
.
.
What should i do.?
I tried a variety of ways, but it made more and more errors.
.

Hi @adarmawan117 Which solution are you trying for ?

https://stackoverflow.com/a/65342590

By the way. I have succesfull running desktop hello world and hand tracking example.
But this android example (on android studio), i facef that error

By the way, i use windows

Hi @adarmawan117 , As we mentioned in https://google.github.io/mediapipe/getting_started/install#installing-on-windows, MediaPipe doesn't support building its Android apps on native Windows because of the limited bazel support for Android on native Windows. Please try WSL instead. You can find the instructions at https://google.github.io/mediapipe/getting_started/install#installing-on-windows-subsystem-for-linux-wsl.

From your above comment, closing this issue. Thanks !

FYI, using MediaPipe in Android Studio with Bazel is deprecated. Please see the new gradle approach in https://github.com/google/mediapipe/blob/master/docs/getting_started/android_solutions.md.


[CARBONDATA-2947] Adaptive encoding support for timestamp no dictionary and Refactor ColumnPageWrapper

Support adaptive encoding for Timestamp data type in case of no dictionary column

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/364/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8611/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/541/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/374/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/550/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8620/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/376/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8624/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/554/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/386/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/389/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8637/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/567/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/401/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/579/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8649/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/413/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8662/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/592/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8663/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/593/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/415/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/416/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8665/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/595/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8669/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/599/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/440/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8688/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/618/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/446/

LGTM

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/626/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8696/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/453/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/633/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8704/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8711/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/641/


Grant types support

Hi,
The examples do not cover all the grant types. Are all the types supported by this library as stated in the rfc ?
Regards

Additionally, the OAuth 2 specification documents purposefully leave the grants enumeration open ended to allow for implementors to add their own. Is there an example of how the grants accepted by Osin may be accepted or how an implementor can create their own grant type?


[AIRFLOW-2712] Pass annotations to KubernetesExecutorConfig

Make sure you have checked all steps below.
JIRA

[X] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[X ] Here are some details about my PR, including screenshots of any UI changes:
Adds an "annotation" field to the KubernetesExecutorConfig so annotations can be specified without hardcoding.

Tests

[X ] My PR adds the following unit tests OR does not need testing for this extremely good reason:
No Kubernetes testing suite exists, afaik. Happy to add them if there is a place for them.

Commits

[ X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ X] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[X ] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3576 into master will increase coverage by <.01%.
The diff coverage is 49.27%.

@@            Coverage Diff             @@
##           master    #3576      +/-   ##
==========================================
+ Coverage   76.83%   76.84%   +<.01%
==========================================
  Files         204      204
  Lines       15485    15485
==========================================
+ Hits        11898    11899       +1
+ Misses       3587     3586       -1

Impacted Files
Coverage Δ

airflow/example_dags/example_bash_operator.py
95% <ø> (ø)
:arrow_up:

airflow/utils/email.py
97.4% <ø> (ø)
:arrow_up:

airflow/jobs.py
83.01% <100%> (ø)
:arrow_up:

airflow/api/common/experimental/mark_tasks.py
68% <24.32%> (ø)
:arrow_up:

airflow/www/views.py
68.94% <45.83%> (ø)
:arrow_up:

airflow/www_rbac/views.py
71.57% <47.36%> (ø)
:arrow_up:

airflow/example_dags/example_python_operator.py
78.94% <50%> (ø)
:arrow_up:

airflow/models.py
88.72% <76.92%> (+0.04%)
:arrow_up:

... and 5 more

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 985a433...87d3e0d. Read the comment docs.

RE the bug: yep I didn't notice that. Thanks - I don't have a way to test gcp on my system so I can't guarantee this works (given we don't have any tests for it)
RE the copying: I don't think it's going to cause a bug, but I've copied it anyways to prevent against any evil bugs in the future.
RE the rebasing: Sorry for that, I stuffed up my previous rebase. I've force pushed and fixed it in this morning's commit.
I've spent all day trying to get testing working on my system. I'll get an update to this PR up tomorrow with tests included.

It seems to me the failed build here is not my fault - I haven't touched the tests that are failing; and some pass occasionally. Is there another concern here I'm not seeing @ashb ?

Code looks good now, will check on the tests - they are likely a transient failure. We get them frequently :( :(

Tests failures look nothing to do with this PR.


Does it work for Android?

hasn't been implemented yet. You're welcome to create a PR :)

@mvayngrib I've already implemented it for Android and even wanted to contribute, but noticed that license is GPL-3.0 in NPM. It is not suited for me.
BTW,
I can create a PR with some staff ready. Let me know if I should.
P.S.:
This repo has MIT license. Please select one of the licenses MIT or GPL-3 and set it everywhere NPM and GitHub.

hm, on npm i see MIT license: https://www.npmjs.com/package/react-native-aes

@bitsal absolutely, contributions are welcome!

@mvayngrib I'm sorry, I've fixed android code here https://github.com/tectiv3/react-native-aes. The same names misled me.

@bitsal ah cool, haven't seen that one. No problem :)


pre-compiled .img location?

Where can I find the image with ros2 precompiled on it? I see references to it on the installation page, but can't seem to find the file anywhere online. I've tried cross compiling, and am getting errors related to pyparsing's version for some reason.
Would appreciate some help here, thanks!

It can be found in the ROS2 section of the https://www.gctronic.com/doc/index.php?title=Pi-puck. This is the direct link do download the image.


Console error messages when using datepicker

I am using materialize 1.0.0 alpha v1 on chrome 63 beta (but this happens in firefox as well). When using the datepicker, I am getting this error in the console everytime I click on a date in the datepicker:
Uncaught TypeError: Cannot read property 'parentNode' of null     at HTMLBodyElement.callback (materialize.js:599)
Here is a JSFiddle showing this happening. It isn't really an issue, as everything still works, but it does get rather annoying when debugging.

Oops, just realised that this issue had already been posted and fixed in #5352, closing.


Refactor cddl specification

per mini-protocol CDDL spec
tx-submission2 CDDL spec
keep-alive CDDL spec
reimplement handshake spec: node-to-node & node-to-client
update technical repor:

fixed a missplaced section
include CDDL mini-protocol encoding specs
standardise message and state indentifiers
link to haddock documentation

bors merge


Comments Page User Roles - Rules

As a TM I should only be able to see all comments on an engagement that I am assigned to. If not assigned to I should only be able to see approved comments.
Link to Spreadsheet in Teams: Spreadsheet

Add checks to:
Comment details page
Comment listing page
Read Comments page

Hey team! Please add your planning poker estimate with Zenhub @djnunez-aot @tiagograf-AOT @VineetBala-AOT


TracIK Implementation for kinematics_interface

The ros2_control project has a kinematics_interface that is defined by four methods: calculate_jacobian, calculate_link_transform, convert_joint_deltas_to_cartesian_deltas, and convert_cartesian_deltas_to_joint_deltas. They also provide an implementation using KDL. Forking this KDL plugin, and modifying it to use TracIK instead, should be relatively straightforward! I may be able to help with this, if it is a desired feature.

Hi @jcarpinelli-bdai! Thanks for the ping. I've been reviewing some ros2_control PRs as time allows so this would be a nice personal exercise, sadly because of my day job I can't promise when I could land an implementation.
To be clear, it is a desired feature, and if you have an imminent need then please feel free to do the typing. Otherwise, I will get to it.. eventually! Just keep me posted 🙇


Removed slice_join_eps from pline boolean options

Just using pos_equal_eps for stitching slices together should work fine and avoids loss in floating point accuracy in cases where intersects are very close to one another (fixing debug assert case). The slice_join_eps was originally added in the C++ code to mask over problems of floating point accuracy in the intersects code.
Also when constructing the aabb_index from the slice start points no fuzzy epsilon is applied (they are added as points), epsilon is only applied during the querying. If it is applied both in creation and querying then the epsilon is effectively doubled, which is not desired.

This fixes case number 1 reported in https://github.com/jbuckmccready/cavalier_contours/issues/27.


DocData order ID uniqueness

As the README says:

Docdata is really keen on having unique merchant order ids

At least during testing it has happened to me several times that the ID is not unique.
For this we have DOCDATA_ORDER_ID_START in the sandbox app...
First question is: Will this also become a problem in production?
Second question is: How can we build unique IDs automatic? Without a offset?
The source order ID generates oscar in: oscar.apps.order.utils.OrderNumberGenerator it's just:
100000 + basket.id
Unfortunately, it looks like you can't just change/replace the OrderNumberGenerator in oscar, isn't it?
The sandbox changed the ID in Facade.get_create_payment_args()
If i see it right: The so called merchant order id is merchantOrderReference here:
https://github.com/django-oscar/django-oscar-docdata/blob/master/tests/testdata/xsd1-1_3.xsd#L2351
This string can be 255 characters long.
Wouldn't it be the easiest to do combine the current date with the basket.id ?

It won't become a problem in production unless you throw away your production database and start over. Order numbers should be unique in Oscar as well.
Note that I added the DOCDATA_ORDER_ID_START for testing purposes of  the sandbox and should not be used in production.

Unfortunately, it looks like you can't just change/replace the OrderNumberGenerator in oscar, isn't it?

Oscar is designed to be fully customizable, not only the models but also most  of the utility classes. There is an example for customizing the OrderNumberGenerator in oscar's docs: https://django-oscar.readthedocs.io/en/releases-1.6/topics/customisation.html#start-customising
This way you can generate the order numbers as you would like to.
The sandbox application customized the checkout app as described here

What's about to add a customizing the OrderNumberGenerator in the sandbox app and remove all of the DOCDATA_ORDER_ID_START stuff?
Just add a datetime string prefix to the order number. The goal: There are never the problem of conflicts while testing.
If that's what wanted, I'll make a pull request.

That would bring the burden of an extra application into the sandbox including extra maintenance and possible incompatibilities with (future) Oscar versions.
I'd like to keep the sandbox as minimal as possible. (In the future the checkout application could be removed as well).

I'd like to keep the sandbox as minimal as possible

You're absolutely right.
What's about #50 ?


to_triage: add jdescottes

Coverage decreased (-0.04%) to 26.251% when pulling fdeec9fafec492da7d48c1f90b10c8bc8827d35d on calixteman:nag_jdescottes into 3ca9d304673179b88d353427af7c7be478019f16 on mozilla:master.


Added support for X509 based authentication / session establishment

Most important part -- Addition of "NewX509Session" in session.go.
Diff here:
https://github.com/nuagenetworks/vspk-go/compare/master...FlorianOtel:master#diff-2b0fab1cea6874e1e0910bf2773794db
Then removing underlined prefixed variables (non-idiomatic in Go ;))

@FlorianOtel I will have to reject this PR as this is autogenerated, but i will incorporate your changes in that system (only relevant changes, cause i'm not going to switch to your imports, of course)

Closing this as mentioned before, the code change has will be accepted in nuagenetworks/monolithe


rox-filer: Use wrapGAppsHook

I also updated the derivation slightly to use pname + version.
Motivation for this change
Fixes ROX-Filer being unable to use SVG icons when the environment is not already being polluted by another wrapper.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 125042 at 3f8d0419 run on x86_64-linux 1

1 package built successfully:

rox-filer

4 suggestions:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/desktops/rox/rox-filer/default.nix:51:3:
   |
51 |   installPhase = ''
   |   ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/desktops/rox/rox-filer/default.nix:85:5:
   |
85 |     license = with licenses; [ gpl2 lgpl2 ];
   |     ^

warning: unclear-gpl
lgpl2 is a deprecated license, please check if project uses lgpl2Plus or lgpl2Only and change meta.license accordingly.
Near pkgs/desktops/rox/rox-filer/default.nix:85:5:
   |
85 |     license = with licenses; [ gpl2 lgpl2 ];
   |     ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/desktops/rox/rox-filer/default.nix:29:5:
   |
29 |     ./rox-filer-2.11-in-source-build.patch
   |     ^


Parameter are visible but internaly empty, and when restart, all the values are empty

Godot version:
beta 4
OS/device including version:
Win10 64bit
Issue description:
In visual script :
parameter of functions and properties are not created (the value is visible but internaly empty) even if values are visible when play values considered as empty.
and when save and restart godot and load the project again the values of all nodes are clearly empty.

Steps to reproduce:
create project >> add sprite >> add visual script >> add animation player >> create animation >> add func _physics_process >> add play animation node and enter animation name >> add position and lookat nodes and enter values >> play (it will consider parameter as empty) >> save project >> exit >> reopen godot >> load the project and check parameters (it will be empty)

We are a team working on this project for a CS class. Could we get assigned to this issue. Our uusernames are gsegovia2018,mattintriago,cniefit,amssat221

same on beta 5 release

beta 6 too

issue still present in "set" nodes with index (e.g. "set position.x" or "set modulate.g") in version RC3


Baseline Image is modified during test run

Describe the bug
Hi,
I upgraded from 3.1.7 to 3.2.3 and now when I run the tests (with pluginVisualRegressionUpdateImages: false) the baseline images (something-something#0.png) is also modified. not the content but metadata (last-modified).
This doesn't happen when I switch back to 3.1.7
To Reproduce
Steps to reproduce the behavior:
If this can't be reproduced by you, then let me know and i'll try adding a minimal reproducible repo for this.
Expected behavior
Baseline screenshots are not touched unless updateImages flag is set.
Please complete the following information:

OS and version: Windows 10
Browser and version: Chrome 107 (headless) | Electron 106 (headless)
Cypress version 10.11.0 | 11.2.0

Hey!
To avoid unexpected behaviour after migration, this plugin always regenerates baseline images whenever its' version has been changes (so, every time you upgrade it in your repository). After single regeneration right after version update everything should work as expected - create a new issue please if that's not the case for you.
And regarding your original issue - do you have any ideas how we could improve this situation?
I'm thinking about writing documentation of this feature, do you think it will be enough? What would your like to see in a description of this feature?
And ofc - PR for it is more than welcome 🙏

Hi Jakub, thank you very much for your response.
I can confirm, the baseline image changes happen only once after the dependency update.
Sure I think in the READMEs FAQ section if this behavior is mentioned then it would help people facing this issue. And I'm also curious why this is necessary. I naively would assume that the screenshot is taken by cy/browser and the options passed by the user therefor the baseline image wouldn't change if the plugin is upgraded.
(should i close this issue?)

For what it's worth, this surprised me and my colleague as well. We also assumed the baseline images would be kept as-is between upgrades.
Out of curiosity, has there been any unexpected behavior after upgrades before?
Personally, I would be fine with a situation where an upgrade of this plugin fails on CI for some or all snapshots. Deleting failing baselines is already part of our workflow for when visual changes are intended.
We have a few hundred baseline images in our test suite. Depending on the update frequency we could end up with a larger-than-necessary .git folder.
That said, we're also fine with keeping the behavior as-is. But maybe add an entry to the FAQ :smile:

I agree -- updating all images on a version change is unexpected, especially when it's just a version patch.

Thanks for your feedback. Yes, there were some issues in the past when we did changes to default image comparison configuration.
I think we can make this situation a bit better and provide separate versioning for when images need to be updated. I'll create a PR for the plugin soon

I've just created a PR regarding this behaviour, feel free to review it: https://github.com/FRSOURCE/cypress-plugin-visual-regression-diff/pull/221


Multiple Alphas

Currently, a single value of alpha is used in retention. However, a ViR should use different alphas for each head. This makes it such that some heads are more focused in the "local" / "more recent" tokens whereas some heads look "further back".
The formula for alpha is 1-2^(-5-arange(0, h)) for the h-th head in the original RetNet paper (there, alpha is called "gamma").

Solved in 6992b8c6c44194ab116cdf6e634325ad67ec6222


FIX: Add Crystal Felling Axe

Issue: The Crystal Felling Axe wasn't removing any notification overlay
Fix: Simply added the Crystal Felling Axe to the set of woodcutting animations

Thank you, I'll update the plugin with the runelite repo asap.


Two people are set up as drivers.

Is your feature request related to a problem? Please describe:
We have two drivers registered with the car. When the main driver is being used, everything works fine. However, whenever the second driver is logged into the car the terminal is filled with errors and HomeKit shows as now response.
Describe the solution you'd like:
Something that allows me to either hide these messages and still enable the few features that still work.
Describe alternatives you've considered:
No real alternatives as this is functionality that exists in the idConnect app. I.e. it hides data for "privacy purposes" whenever the guest driver is using the car.
Additional context:

none

This is the main message shown for all of the different items within homebridge
This plugin threw an error from the characteristic 'Brightness': Unhandled error thrown inside read handler for characteristic: Cannot read properties of undefined (reading 'batteryStatus'). See https://homebridge.io/w/JtMGR for more info.
many of the sensors still appear to be working in HomeKit

I will take a look and see how this can be done best.


Adding gitter.im for support questions

Hi,
I am currently using Broadway and while the behaviour is good documented by the test cases I am missing some support forum for the application. I am aware of DDD/CQRS and DDDinPHP groups on Google Groups but sometimes I have question especially for Broadway. So including a chat right here to GitHub sounds like a nice idea to solve this.
The Chat in question is https://gitter.im/

+1

There is the IRC channel which is mentioned in the readme

Feel free to join #qandidate on freenode with questions and remarks!

I personally don't feel much for yet another communication channel I need to pay attention to.

Its 2016 and you still hang out in IRC channels oO?


Remove deprecated IPN fields, use new fields

app/code/community/Bitpay/Core/controllers/IpnController.php (line 55-68)
Remove deprecated IPN fields (btcPaid,, btcPrice, rate).
Store/log new IPN field transactionCurrency

#147

Fixed in PR #147


Create skeleton projects

demo
blog
profile page
etc.

Like this one: https://github.com/PHPoole/PHPoole-demo.


cuissard

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c]

/trunk merge


[BUG] Cannot get Test Framework to ignore a volatile query parameter

I'm attempting to generate random(ish) block ids to address https://github.com/Azure/azure-sdk-for-net/issues/8162
When add add blockid to https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/storage/Azure.Storage.Common/tests/Shared/StorageRecordMatcher.cs#L42, it is ignored, and the test framework continues to check blockid in the test recordings.

We'd need a change in the Azure.Core Test Framework's RecordMatcher to get this working.


gnustep: update

Motivation for this change
Replaces #122045
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Seeing as the sogo test still passes and everything else still builds, I'll self-merge this in a week or so, if there is no objection.


Wheel name regex fails

https://github.com/novemberfiveco/s3pypi/blob/6ac00dd636b826fda08c58306b2adff21bd210cd/s3pypi/package.py#L54
While debugging publishing with s3pypi on my build server, I finally discovered the issue was this regex doesn't match the python setup.py output on my build server.
The output does contain creating build/bdist.linux-x86_64/wheel/PACKAGENAME-0.2.16.dist-info/WHEEL, but that is the end of the output.
The build server does successfully build an installable wheel. I'm not sure if this is an issue with output verbosity of running python setup.py  [ARGS] on the build server or something else, but the build server does have up to date setuptools and wheel packages installed, and this seems to be more of an issue of the regex search for the wheel name looking for a wheel name in inconsistent command output.

This regex has been removed in s3pypi 1.0.0.


PiecewiseChebyshev does not work as expected when breakpoints = None

Information

Qiskit Terra version: Master
Python version: 3.7.5
Operating system: Windows 10

What is the current behavior?
When using PiecewiseChebyshev  with breakpoints equal None, the resulting circuit contains one gate only.
Steps to reproduce the problem
f_x, degree, breakpoints, num_state_qubits = lambda x: np.sqrt(x), 2, None, 2
pw_approximation = PiecewiseChebyshev(f_x, degree, breakpoints, num_state_qubits)
print(pw_approximation.breakpoints)
print(pw_approximation.polynomials)

Result:
[0, 4]
[[3.141592653589793]]

What is the expected behavior?
Result should be:
[0, 4]
[[0.6901841202733885, 1.321746423545076, -0.12631246065433754]]

Suggested solutions
I think self.breakpoints should be used instead of self._breakpoints in polynomials property

@anedumla could you have a look? 🙂

I'll close this as this should've been fixed by #6210.


Tests pending.

LGTM and tested w/ c9s and looks good!