"Failed to create MMAL component vc.camera_info: Function not implemented" on Yocto image

There is a chance that something wrong with the Yocto image itself, but it looks very weird that raspistill (IIRC it also uses libmmal under the hood) works and picamera doesn't. Do you have any idea @waveform80? Thanks!

Raspberry Pi 2 Model B;
Raspberry Pi Camera v2.1;
rpi-test-image Yocto image + one additional package python-pip;
Camera is enabled and 256Mb is allocated for GPU (start_x=1 gpu_mem=256 in config.txt);
Kernel version is Linux raspberrypi2 4.4.23 #1 SMP Tue Oct 4 14:55:18 UTC 2016 armv7l armv7l armv7l GNU/Linux;
And output from ldconfig:

root@raspberrypi2:~# ldconfig -p | grep libmmal
    libmmal_vc_client.so (libc6) => /usr/lib/libmmal_vc_client.so
    libmmal_util.so (libc6) => /usr/lib/libmmal_util.so
    libmmal_core.so (libc6) => /usr/lib/libmmal_core.so
    libmmal_components.so (libc6) => /usr/lib/libmmal_components.so
    libmmal.so (libc6) => /usr/lib/libmmal.so

Everything works fine with raspistill - no problems whatsoever. But the following code is failing (Python 2.7, picamera 1.12 installed via pip install picamera[array]):
import picamera
camera = picamer.PiCamera()

Here is a verbose python output:
Python 2.7.11 (default, Sep 29 2016, 19:22:22)
[GCC 5.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
import picamera # directory /usr/lib/python2.7/site-packages/picamera
# /usr/lib/python2.7/site-packages/picamera/__init__.pyc matches /usr/lib/python2.7/site-packages/picamera/__init__.py
import picamera # precompiled from /usr/lib/python2.7/site-packages/picamera/__init__.pyc
# /usr/lib/python2.7/__future__.pyc matches /usr/lib/python2.7/__future__.py
import __future__ # precompiled from /usr/lib/python2.7/__future__.pyc
# /usr/lib/python2.7/site-packages/picamera/exc.pyc matches /usr/lib/python2.7/site-packages/picamera/exc.py
import picamera.exc # precompiled from /usr/lib/python2.7/site-packages/picamera/exc.pyc
# /usr/lib/python2.7/site-packages/picamera/mmal.pyc matches /usr/lib/python2.7/site-packages/picamera/mmal.py
import picamera.mmal # precompiled from /usr/lib/python2.7/site-packages/picamera/mmal.pyc
import ctypes # directory /usr/lib/python2.7/ctypes
# /usr/lib/python2.7/ctypes/__init__.pyc matches /usr/lib/python2.7/ctypes/__init__.py
import ctypes # precompiled from /usr/lib/python2.7/ctypes/__init__.pyc
dlopen("/usr/lib/python2.7/lib-dynload/_ctypes.so", 2);
import _ctypes # dynamically loaded from /usr/lib/python2.7/lib-dynload/_ctypes.so
# /usr/lib/python2.7/struct.pyc matches /usr/lib/python2.7/struct.py
import struct # precompiled from /usr/lib/python2.7/struct.pyc
dlopen("/usr/lib/python2.7/lib-dynload/_struct.so", 2);
import _struct # dynamically loaded from /usr/lib/python2.7/lib-dynload/_struct.so
# /usr/lib/python2.7/ctypes/_endian.pyc matches /usr/lib/python2.7/ctypes/_endian.py
import ctypes._endian # precompiled from /usr/lib/python2.7/ctypes/_endian.pyc
# /usr/lib/python2.7/site-packages/picamera/camera.pyc matches /usr/lib/python2.7/site-packages/picamera/camera.py
import picamera.camera # precompiled from /usr/lib/python2.7/site-packages/picamera/camera.pyc
dlopen("/usr/lib/python2.7/lib-dynload/datetime.so", 2);
import datetime # dynamically loaded from /usr/lib/python2.7/lib-dynload/datetime.so
# /usr/lib/python2.7/mimetypes.pyc matches /usr/lib/python2.7/mimetypes.py
import mimetypes # precompiled from /usr/lib/python2.7/mimetypes.pyc
# /usr/lib/python2.7/urllib.pyc matches /usr/lib/python2.7/urllib.py
import urllib # precompiled from /usr/lib/python2.7/urllib.pyc
# /usr/lib/python2.7/string.pyc matches /usr/lib/python2.7/string.py
import string # precompiled from /usr/lib/python2.7/string.pyc
dlopen("/usr/lib/python2.7/lib-dynload/strop.so", 2);
import strop # dynamically loaded from /usr/lib/python2.7/lib-dynload/strop.so
# /usr/lib/python2.7/socket.pyc matches /usr/lib/python2.7/socket.py
import socket # precompiled from /usr/lib/python2.7/socket.pyc
dlopen("/usr/lib/python2.7/lib-dynload/_socket.so", 2);
import _socket # dynamically loaded from /usr/lib/python2.7/lib-dynload/_socket.so
# /usr/lib/python2.7/functools.pyc matches /usr/lib/python2.7/functools.py
import functools # precompiled from /usr/lib/python2.7/functools.pyc
dlopen("/usr/lib/python2.7/lib-dynload/_functools.so", 2);
import _functools # dynamically loaded from /usr/lib/python2.7/lib-dynload/_functools.so
dlopen("/usr/lib/python2.7/lib-dynload/_ssl.so", 2);
import _ssl # dynamically loaded from /usr/lib/python2.7/lib-dynload/_ssl.so
dlopen("/usr/lib/python2.7/lib-dynload/cStringIO.so", 2);
import cStringIO # dynamically loaded from /usr/lib/python2.7/lib-dynload/cStringIO.so
dlopen("/usr/lib/python2.7/lib-dynload/time.so", 2);
import time # dynamically loaded from /usr/lib/python2.7/lib-dynload/time.so
# /usr/lib/python2.7/base64.pyc matches /usr/lib/python2.7/base64.py
import base64 # precompiled from /usr/lib/python2.7/base64.pyc
dlopen("/usr/lib/python2.7/lib-dynload/binascii.so", 2);
import binascii # dynamically loaded from /usr/lib/python2.7/lib-dynload/binascii.so
# /usr/lib/python2.7/urlparse.pyc matches /usr/lib/python2.7/urlparse.py
import urlparse # precompiled from /usr/lib/python2.7/urlparse.pyc
# /usr/lib/python2.7/collections.pyc matches /usr/lib/python2.7/collections.py
import collections # precompiled from /usr/lib/python2.7/collections.pyc
dlopen("/usr/lib/python2.7/lib-dynload/_collections.so", 2);
import _collections # dynamically loaded from /usr/lib/python2.7/lib-dynload/_collections.so
dlopen("/usr/lib/python2.7/lib-dynload/operator.so", 2);
import operator # dynamically loaded from /usr/lib/python2.7/lib-dynload/operator.so
# /usr/lib/python2.7/keyword.pyc matches /usr/lib/python2.7/keyword.py
import keyword # precompiled from /usr/lib/python2.7/keyword.pyc
# /usr/lib/python2.7/heapq.pyc matches /usr/lib/python2.7/heapq.py
import heapq # precompiled from /usr/lib/python2.7/heapq.pyc
dlopen("/usr/lib/python2.7/lib-dynload/itertools.so", 2);
import itertools # dynamically loaded from /usr/lib/python2.7/lib-dynload/itertools.so
dlopen("/usr/lib/python2.7/lib-dynload/_heapq.so", 2);
import _heapq # dynamically loaded from /usr/lib/python2.7/lib-dynload/_heapq.so
import thread # builtin
# /usr/lib/python2.7/ssl.pyc matches /usr/lib/python2.7/ssl.py
import ssl # precompiled from /usr/lib/python2.7/ssl.pyc
# /usr/lib/python2.7/textwrap.pyc matches /usr/lib/python2.7/textwrap.py
import textwrap # precompiled from /usr/lib/python2.7/textwrap.pyc
# /usr/lib/python2.7/contextlib.pyc matches /usr/lib/python2.7/contextlib.py
import contextlib # precompiled from /usr/lib/python2.7/contextlib.pyc
# /usr/lib/python2.7/threading.pyc matches /usr/lib/python2.7/threading.py
import threading # precompiled from /usr/lib/python2.7/threading.pyc
# /usr/lib/python2.7/fractions.pyc matches /usr/lib/python2.7/fractions.py
import fractions # precompiled from /usr/lib/python2.7/fractions.pyc
# /usr/lib/python2.7/decimal.pyc matches /usr/lib/python2.7/decimal.py
import decimal # precompiled from /usr/lib/python2.7/decimal.pyc
dlopen("/usr/lib/python2.7/lib-dynload/math.so", 2);
import math # dynamically loaded from /usr/lib/python2.7/lib-dynload/math.so
# /usr/lib/python2.7/numbers.pyc matches /usr/lib/python2.7/numbers.py
import numbers # precompiled from /usr/lib/python2.7/numbers.pyc
# /usr/lib/python2.7/locale.pyc matches /usr/lib/python2.7/locale.py
import locale # precompiled from /usr/lib/python2.7/locale.pyc
# /usr/lib/python2.7/site-packages/picamera/bcm_host.pyc matches /usr/lib/python2.7/site-packages/picamera/bcm_host.py
import picamera.bcm_host # precompiled from /usr/lib/python2.7/site-packages/picamera/bcm_host.pyc
# /usr/lib/python2.7/site-packages/picamera/mmalobj.pyc matches /usr/lib/python2.7/site-packages/picamera/mmalobj.py
import picamera.mmalobj # precompiled from /usr/lib/python2.7/site-packages/picamera/mmalobj.pyc
# /usr/lib/python2.7/weakref.pyc matches /usr/lib/python2.7/weakref.py
import weakref # precompiled from /usr/lib/python2.7/weakref.pyc
# /usr/lib/python2.7/site-packages/picamera/encoders.pyc matches /usr/lib/python2.7/site-packages/picamera/encoders.py
import picamera.encoders # precompiled from /usr/lib/python2.7/site-packages/picamera/encoders.pyc
# /usr/lib/python2.7/io.pyc matches /usr/lib/python2.7/io.py
import io # precompiled from /usr/lib/python2.7/io.pyc
dlopen("/usr/lib/python2.7/lib-dynload/_io.so", 2);
import _io # dynamically loaded from /usr/lib/python2.7/lib-dynload/_io.so
# /usr/lib/python2.7/site-packages/picamera/frames.pyc matches /usr/lib/python2.7/site-packages/picamera/frames.py
import picamera.frames # precompiled from /usr/lib/python2.7/site-packages/picamera/frames.pyc
# /usr/lib/python2.7/site-packages/picamera/streams.pyc matches /usr/lib/python2.7/site-packages/picamera/streams.py
import picamera.streams # precompiled from /usr/lib/python2.7/site-packages/picamera/streams.pyc
# /usr/lib/python2.7/site-packages/picamera/renderers.pyc matches /usr/lib/python2.7/site-packages/picamera/renderers.py
import picamera.renderers # precompiled from /usr/lib/python2.7/site-packages/picamera/renderers.pyc
# /usr/lib/python2.7/site-packages/picamera/color.pyc matches /usr/lib/python2.7/site-packages/picamera/color.py
import picamera.color # precompiled from /usr/lib/python2.7/site-packages/picamera/color.pyc
# /usr/lib/python2.7/colorsys.pyc matches /usr/lib/python2.7/colorsys.py
import colorsys # precompiled from /usr/lib/python2.7/colorsys.pyc
import RPi # directory /usr/lib/python2.7/site-packages/RPi
# /usr/lib/python2.7/site-packages/RPi/__init__.pyc matches /usr/lib/python2.7/site-packages/RPi/__init__.py
import RPi # precompiled from /usr/lib/python2.7/site-packages/RPi/__init__.pyc
dlopen("/usr/lib/python2.7/site-packages/RPi/GPIO.so", 2);
import RPi.GPIO # dynamically loaded from /usr/lib/python2.7/site-packages/RPi/GPIO.so
mmal: mmal_component_create_core: could not find component 'vc.camera_info'
Traceback (most recent call last):
  File "test.py", line 2, in <module>
    camera = picamera.PiCamera()
  File "/usr/lib/python2.7/site-packages/picamera/camera.py", line 367, in __init__
    with mo.MMALCameraInfo() as camera_info:
  File "/usr/lib/python2.7/site-packages/picamera/mmalobj.py", line 1412, in __init__
    super(MMALCameraInfo, self).__init__()
  File "/usr/lib/python2.7/site-packages/picamera/mmalobj.py", line 446, in __init__
    prefix="Failed to create MMAL component %s" % self.component_type)
  File "/usr/lib/python2.7/site-packages/picamera/exc.py", line 157, in mmal_check
    raise PiCameraMMALError(status, prefix)
picamera.exc.PiCameraMMALError: Failed to create MMAL component vc.camera_info: Function not implemented
....

Sounds like https://github.com/raspberrypi/userland/issues/178
Have you been rebuilding userland with modified build parameters (ie  '--no-as-needed')?

Hey @6by9, thanks for the hint. Currently I use master branch of meta-raspberry and there is --no-as-needed [1] in the userland recipe. With this both raspistill and raspivid work fine, but not picamera python lib. Out of curiosity I was trying to remove --no-as-needed and obviously nothing worked after that :) Or I should try to modify it in some other way?
Also wondering if it's somehow related to the fact that picamera is not included into yocto image from the start and I install it via pip install picamera[array] later on.
[1] https://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/recipes-graphics/userland/userland_git.bb#n41

I'm afraid this is all rather beyond my knowledge (I've never dealt with the --as-needed switch or gcc's __attribute__ mechanism), so I doubt I'll be able to shed any light on this. The only thing I would mention is that ctypes in Python (which picamera uses to access libmmal) will be loading the library with dlopen whereas I'd assume raspistill / raspivid will be dynamically linked. I've no idea if/how that could make any difference though.
The manner of picamera's installation shouldn't make any difference; the deb on Raspbian is effectively the result of running pip install, and it certainly won't change the manner in which it accesses libmmal.

It seems that picamera uses libmmal.so while raspivid and raspistill links against libmmal_{core,util,vc_client}.so directly. On Alpine Linux I added the -DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-as-needed' to cmake (as in the Yocto package) and raspivid/raspistill worked fine but picamera gave exactly the same "Function not implemented" errors (as libmmal still wasn't properly linked to the relevant libs), so I compiled using LDFLAGS="-Wl,--no-as-needed" instead (as in the Void Linux package) and it worked correctly.
ldd /opt/vc/lib/libmmal.so (using -DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-as-needed'):
	ldd (0xb6ec1000)
	libmmal_core.so => /opt/vc/lib/libmmal_core.so (0xb6e8f000)
	libmmal_util.so => /opt/vc/lib/libmmal_util.so (0xb6e71000)
	libvcos.so => /opt/vc/lib/libvcos.so (0xb6e58000)
	libc.musl-armhf.so.1 => ldd (0xb6ec1000)

ldd /opt/vc/lib/libmmal.so (using LDFLAGS="-Wl,--no-as-needed"):
	ldd (0xb6eb6000)
	libmmal_vc_client.so => /opt/vc/lib/libmmal_vc_client.so (0xb6e87000)
	libmmal_components.so => /opt/vc/lib/libmmal_components.so (0xb6e6c000)
	libvchiq_arm.so => /opt/vc/lib/libvchiq_arm.so (0xb6e56000)
	libvcsm.so => /opt/vc/lib/libvcsm.so (0xb6e40000)
	libmmal_core.so => /opt/vc/lib/libmmal_core.so (0xb6e22000)
	libmmal_util.so => /opt/vc/lib/libmmal_util.so (0xb6e04000)
	libcontainers.so => /opt/vc/lib/libcontainers.so (0xb6de1000)
	libvcos.so => /opt/vc/lib/libvcos.so (0xb6dc8000)
	libc.musl-armhf.so.1 => ldd (0xb6eb6000)

It certainly isn't a bug in picamera, so it seems the only workaround that could be done here would be to use the libmmal_*.so directly as raspivid/raspistill does (idk if that's feasible/possible though).

NOTE: applying https://github.com/raspberrypi/userland/pull/459 locally still gave me the same results as using -DCMAKE_EXE_LINKER_FLAGS i.e. no libs linked to libmmal.so, so maybe this is relevant to you @6by9  :)

The linker flags are needed when compiling picamera, not libmmal.
https://github.com/raspberrypi/userland/pull/459 only changes the dependencies of the standard apps, not the libraries.
libmmal does NOT depend on  libmmal_vc_client. If you wish to use the VPU components then your application needs to link against it, and to NOT over optimise and end up removing the constructor.
https://github.com/raspberrypi/userland/issues/178 / https://github.com/raspberrypi/userland/issues/303#issuecomment-204394592

That's ... odd; picamera isn't compiled (in any meaningful sense). It's just dynamically loading what it needs from the C libs identified in picamera/mmal.py. I'm not entirely familiar with the guts of CPython's ctypes module but I'd guess ultimately it's just calling dlopen and dlsym to grab what it needs from libmmal and libbcm_host. I'm afraid I can't shed much more light on this!

I am also facing a similar error while building userland.
I am using the attached python code for livestreaming.
All working fine till this morning, until I built userland for cec-client.
Later I am facing this issue everytime. Could someone share me the libmmal_vc_client.so with vc.camera_info included.
Error:
pimate@pimate-eswar:~$ python /home/pimate/ESWAR/LIVE/live.py
mmal: mmal_component_create_core: could not find component 'vc.camera_info'
Traceback (most recent call last):
File "/home/pimate/ESWAR/LIVE/live.py", line 8, in
camera = PiCamera()
File "/usr/local/lib/python3.6/dist-packages/picamera/camera.py", line 367, in init
with mo.MMALCameraInfo() as camera_info:
File "/usr/local/lib/python3.6/dist-packages/picamera/mmalobj.py", line 2346, in init
super(MMALCameraInfo, self).init()
File "/usr/local/lib/python3.6/dist-packages/picamera/mmalobj.py", line 633, in init
prefix="Failed to create MMAL component %s" % self.component_type)
File "/usr/local/lib/python3.6/dist-packages/picamera/exc.py", line 184, in mmal_check
raise PiCameraMMALError(status, prefix)
picamera.exc.PiCameraMMALError: Failed to create MMAL component b'vc.camera_info': Function not implemented
pimate@pimate-eswar:~$
live.txt

I am also facing a similar error while building userland.
I am using the attached python code for livestreaming.
All working fine till this morning, until I built userland for cec-client.
Later I am facing this issue everytime. Could someone share me the libmmal_vc_client.so with vc.camera_info included.
Error:
python /home/pimate/ESWAR/LIVE/live.py
mmal: mmal_component_create_core: could not find component 'vc.camera_info'
Traceback (most recent call last):
File "/home/pimate/ESWAR/LIVE/live.py", line 8, in
camera = PiCamera()
File "/usr/local/lib/python3.6/dist-packages/picamera/camera.py", line 367, in init
with mo.MMALCameraInfo() as camera_info:
File "/usr/local/lib/python3.6/dist-packages/picamera/mmalobj.py", line 2346, in init
super(MMALCameraInfo, self).init()
File "/usr/local/lib/python3.6/dist-packages/picamera/mmalobj.py", line 633, in init
prefix="Failed to create MMAL component %s" % self.component_type)
File "/usr/local/lib/python3.6/dist-packages/picamera/exc.py", line 184, in mmal_check
raise PiCameraMMALError(status, prefix)
picamera.exc.PiCameraMMALError: Failed to create MMAL component b'vc.camera_info': Function not implemented
live.txt

Where do i have to put the following to avoid this error?
SET( CMAKE_EXE_LINKER_FLAGS "-Wl,--no-as-needed" )

I tried the following and the issue is resolved.

sudo rm -rf /opt/vc
sudo apt-get update
sudo apt-get install --reinstall libraspberrypi0 libraspberrypi-dev libraspberrypi-doc libraspberrypi-bin

I'm also experiencing this issue with a self-compiled version of the raspberry userland repo on the latest Ubuntu Server image for the Raspberry Pi 4. I've added SET( CMAKE_EXE_LINKER_FLAGS "-Wl,--no-as-needed" ) to the CMakeLists.txt of that repo and ran the buildme script. However, picamera says:
mmal: mmal_component_create_core: could not find component 'vc.camera_info'
Traceback (most recent call last):
  File "picam.py", line 171, in <module>
    main()
  File "picam.py", line 143, in main
    with picamera.PiCamera(
  File "/usr/local/lib/python3.8/dist-packages/picamera/camera.py", line 367, in __init__
    with mo.MMALCameraInfo() as camera_info:
  File "/usr/local/lib/python3.8/dist-packages/picamera/mmalobj.py", line 2346, in __init__
    super(MMALCameraInfo, self).__init__()
  File "/usr/local/lib/python3.8/dist-packages/picamera/mmalobj.py", line 631, in __init__
    mmal_check(
  File "/usr/local/lib/python3.8/dist-packages/picamera/exc.py", line 184, in mmal_check
    raise PiCameraMMALError(status, prefix)
picamera.exc.PiCameraMMALError: Failed to create MMAL component b'vc.camera_info': Function not implemented

Does anyone have another hint here? Thanks!

Not a very good fix, but copying libmmal.so from a working version of Raspbian (/opt/vc/lib/libmmal.so) to /usr/lib/arm-linux-gnueabihf/libmmal.so on Ubuntu Mate 20.04 worked for me.


Nimrod/starknet resources refactor

This change is

Codecov Report
Attention: Patch coverage is 73.40426% with 50 lines in your changes are missing coverage. Please review.

Project coverage is 73.27%. Comparing base (0446693) to head (c6e8066).
Report is 1 commits behind head on main.

Files
Patch %
Lines

crates/native_blockifier/src/py_block_executor.rs
0.00%
22 Missing :warning:

...ve_blockifier/src/py_transaction_execution_info.rs
0.00%
11 Missing :warning:

crates/native_blockifier/src/py_validator.rs
0.00%
7 Missing :warning:

crates/blockifier/src/transaction/objects.rs
91.07%
0 Missing and 5 partials :warning:

crates/blockifier/src/fee/actual_cost.rs
94.73%
0 Missing and 3 partials :warning:

crates/blockifier/src/fee/fee_utils.rs
92.30%
0 Missing and 1 partial :warning:

crates/blockifier/src/fee/gas_usage.rs
80.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1655      +/-   ##
==========================================
- Coverage   73.67%   73.27%   -0.41%
==========================================
  Files          59       59
  Lines        8622     8642      +20
  Branches     8622     8642      +20
==========================================
- Hits         6352     6332      -20
- Misses       1786     1827      +41
+ Partials      484      483       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Feature request: Add clearTimeout-like functionality to timeout* operators

In some use cases it would be helpful if the timeout* operators would accept an observable that had the possibility to clear the timeout. So when the observable that the timeout is subscribed to emits something and the "clearing" observable emits true in the timespan till the timeout is reached, the timeout is cleared.
One use case would be a spinner that is shown after a certain amount of time for long running actions but should not be shown for short actions.

I think you can achieve that with switch.

Alright I figured it out. Thanks for the suggestion!


[Feature Request] Ability to change on/off sounds in the config file.

And thanks for making this software - MS teams doesn't have push to talk.
It would also be nice to have documentation on building the application so we can change it ourselves. To other people, on windows go to:
C:\Program Files\AutoHotkey\Compiler
Then run:
.\Ahk2Exe.exe /in [path to the git repo]MicMute.ahk
A .exe will be generated at the git repo path.

Hey, I'm actually working on this right now because I recently replaced discord's sounds with original sounds that I made, so I'm also adding the ability to use custom sounds just in case they're horrible 😄
also as to build the application just run
Ahk2Exe.exe /in "path\to\MicMute.ahk" /out "path\to\MicMute.exe"

Hey, I'm actually working on this right now because I recently replaced discord's sounds with original sounds that I made, so I'm also adding the ability to use custom sounds just in case they're horrible 😄
also as to build the application just run
Ahk2Exe.exe /in "path\to\MicMute.ahk" /out "path\to\MicMute.exe"

🎉 Check the latest release 🎉

🎉 Check the latest release 🎉


fix: wrong full page class name in Loading

Proposed Changes

Rename fullPageIconClass to fullPageClass in Loading component documentation
Change fullPageClass description

The docs is auto-generated running docs script and It reads props from component https://github.com/oruga-ui/oruga/blob/develop/packages/oruga/src/components/loading/Loading.vue
Please add the missing prop fullPageClass and run docs build. The markdown will be updated.

I have been rename fullPageIconClass to fullPageClass in loading/Inspector.vue. This PR is ready now.

Ok but you are missing to add fullPageClass prop to Loading.vue component (oruga and oruga-next) as I told you.

Thanks 👍


Emulator Loading 100% but no run

Hello i just want to embed the emulator into my website
this is my index page:
`
// the javascript:
var resizeOwnEmulator = function(width, height)
{
var emulator = $('#emulator');
emulator.css('width', width);
emulator.css('height', height);
}
$(function()
{
    function embed()
    {
        var emulator = $('#emulator');
        if(emulator)
        {
            var flashvars = {
                system : 'nes',
                url : "/roms/Metroid.nes"};
            var params = {};
            var attributes = {};

            params.allowscriptaccess = 'sameDomain';
            params.allowFullScreen = 'true';
            params.allowFullScreenInteractive = 'true';

            swfobject.embedSWF('bin/Nesbox.swf', 'emulator', '640', '480', '11.2.0', 'flash/expressInstall.swf', flashvars, params, attributes);
        }
    }

    embed();
});

`
But it is not working.
The Emulator is displayed, but he just says Loading game 100%
But it doesnt matter where the rom is. If I say url:"asjdfkajs;dlkfja;lsdkjf;lkasjdf"
then he says Loading game 100%
If i let flashvars empty like this:
var flashvars = {};
The Emulator displays to and i can click on it and choose a rom and can play!
But of course i want to choose a rom in the code.
My Directories on the server is
index.php
Nesbox.as3proj
src
roms
-Metroid.nes
lib
flash
-expressInstall.swf
bin
-Nesbox.swf
-nes.swf
So Pls guys can someone help me out?

hi, pls give me url and I'll try to investigate.

Thx for trying to help me. But i solved the problem my self.
It was just a tiny mistake here:
url : "/roms/Metroid.nes"
it hast to be:
url : "roms/Metroid.nes"
without the slash, because it is a relative path.
The Problem in here is that there isn't a failure message or something like that.
It just says game loaded 100%. That's really confusing.
:D

384/5000
Hi good day.
I would need your help.
I'm testing with blogger and google sites nesbox, I load well the emulator 100%. But it stays frozen on that screen. Never load the rom.
I leave the link so that they can see it all.
Http://retrojuegosonline.blogspot.com/2017/01/play-indiana-jones-and-last-crusade.html
I await your prompt response and thank you beforehand.
" CODE "

To play this game, please, download the latest Flash player!

try to rename "Super_Metroid" to "Super_Metroid.smc" in the zip file

muchas gracias por su respues. Pero sigue sin funcionar mismo error.
quedo asi ahora:
var flashvars =                  {                     system : 'snes',                     url : 'https://sites.google.com/site/retrojuegosonline/roms/super_metroid.smc'                 };                 var params = {};                 var attributes = {};

seem the problem is in domains, you are using two domains retrojuegosonline.blogspot.com and sites.google.com to host emulator and roms
I think sites.google doesn't allow to download rom for blogspot
So, try to host all the files on same domain.

perfect. I'm going to try some other host. Do you have any free to recommend me?

try github pages :)
https://pages.github.com/

ty

I do not understand how to use github to host a website. Do you know any other free? Thank you

I finally learned how to use github and manage to make the emulator work perfectly.
I thank him with all my heart. You are a genius

I am rpeveri by the way.
Now my question is how much space and bandwidth supports free github


Added retries for getting refreshable token

Changes

Title
Tests

[x] make test passing
[x] make fmt applied
[ ] relevant integration tests applied

Codecov Report
Patch coverage: 81.81% and project coverage change: -0.03 :warning:

Comparison is base (e8225d5) 18.92% compared to head (0e4f319) 18.89%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #500      +/-   ##
==========================================
- Coverage   18.92%   18.89%   -0.03%
==========================================
  Files          82       83       +1
  Lines        8988     9011      +23
==========================================
+ Hits         1701     1703       +2
- Misses       7139     7160      +21
  Partials      148      148

Impacted Files
Coverage Δ

config/oauth_visitors.go
48.14% <81.81%> (+21.83%)
:arrow_up:

... and 8 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Improved documentation of Signal.foldp

@mietek asked what happened to this commit. It's indeed a bit mysterious. @evancz had merged the PR with that commit (see https://github.com/elm-lang/core/pull/149), but somehow it went missing from the repository's history.
So I've repeated the change in this PR here, and hope it can be quickly merged.

@evancz, here's another instance of how the deficiency of the current docs in this respect is hurting: latest thread on the mailing list. That person shouldn't have to ask on the mailing list

Where does the initial signalled value get lost?

Instead, the documentation of foldp should have told them. That's what the note added here does. Also, you had already approved the note and its wording when you merged pull request https://github.com/elm-lang/core/pull/149 almost a year ago.

@jvoigtlaender, I must note that the note added here does not explain why the initial value of the signal is ignored. I still don’t understand this.

I also don’t understand how to use foldp' to work around this problem.  Here’s what I did instead, in order to continue using StartApp.
type Model = ...

initialModel : Model
initialModel = ...

type Action = Idle | ...

init : (Model, Effects Action)
init =
    (initialModel, Effects.task (Task.succeed Idle))

update : Action -> Model -> (Model, Effects Action)
update action model =
    case action of
      Idle ->
        (model, none)
      ...

@mietek, yes, the documentation with my added note only says what the behavior of foldp is, not why it is that way. I don't think the documentation of a function should say why it is not another function? For example, when reading the documentation of List.filter, do you expect a justification for the fact that the function keeps, rather than drops, the elements that satisfy the given predicate? The other version (dropping rather than keeping) would also have been an option. But the choice was made to implement the version that keeps. The documentation should state what is the case, and it does. The same should apply to the documentation of foldp, I think.
Separately from the issue of documentation, I wouldn't know what to say (here or elsewhere) about "why" foldp is as it is. Just as for filter, it was a choice. To either include in core the version that we now know as foldp, or the version we now know as foldp'. Evan made that choice, and it has been like this since then.
About how to use foldp' to work around this problem: Does this help? It's not in the context of start-app, but that's simply because in start-app the foldp is hidden from the programmer, so it cannot be replaced by foldp'. If you want a solution in the context of start-app, you need to wait for the start-app package to be revised, or use a fork of it. See https://github.com/evancz/start-app/pull/37.

@jvoigtlaender, the documentation describes foldp as “Create a past-dependent signal”, and yet the result does not depend on the incoming signal’s initial value, which is most certainly in the past. To my mind, the description is borderline incoherent, and the behaviour is an unpleasant surprise.
The List.filter analogy is unsatisfactory. Given that filter means “keeping” in other languages, I would expect any new language that chooses filter to mean “dropping” to justify the choice in the documentation. Additionally, “keeping” and “dropping” are the only two unsurprising behaviours for filter.   would not expect filter to keep all the elements of a list that satisfy a given predicate, except the first.

Okay, maybe the filter analogy was a stretch. Still, I'm not exactly sure what you want to be added to the documentation of foldp in addition to what I already add here. You say:

To my mind, the description is borderline incoherent, and the behaviour is an unpleasant surprise.

With my added text, the behavior would not anymore be a surprise. It might still be unpleasant behavior, but that means you are calling for the function to be replaced by a different one, not for a change to the documentation. Also "Create a past-dependent signal" plus "but the initial value is not used" explains exactly what the function does, so I don't know what is wrong about that in combination.
And as for providing justification in the documentation, I have already remarked that I'm not the person to give that justification. And I doubt Evan wants to give it. So none of this should stop this pull request from being merged. It strictly improves the current documentation, and I don't see a further strict improvement being proposed.

I guess what I'm trying to say is that there are separate issues coming up in the above discussion:

foldp behaves somewhat strangely
the current documentation of foldp doesn't mention that strangeness
the current documentation of foldp doesn't justify that strangeness

All I can do is address 2. here. If 1. and/or 3. should be addressed, that should be brought up on the mailing list or in separate issues in this repository.
If there is some way to address 2. better than I have in the commit above, I'm all ears.

To take some pull request pressure off this repository, I am now going to merge some PRs that are "just" about documentation and that seem uncontroversial. I am starting with this one, which I consider uncontroversial (in as far as its stated goal, namely addressing point 2. from the previous comment), because it was already once merged in by Evan (see link above).
Any other points, specifically 1. and 3. from the previous comment, could be the topic of separate issues/PRs.


Support @Option with ListProperty

Expected Behavior
It is possible to annotation a JavaBean property of type List<String> with @Option and supply it with values from the command-line. We should have feature parity for properties of type ListProperty<String> etc.
Current Behavior (optional)
Currently an error is thrown if @Option is used on ListProperty<String>:
Caused by: org.gradle.cli.CommandLineArgumentException: Command-line option '--serial' does not take an argument.
	at app//org.gradle.cli.CommandLineParser$KnownOptionParserState.onArgument(CommandLineParser.java:423)
	at app//org.gradle.cli.CommandLineParser.parse(CommandLineParser.java:93)
	at app//org.gradle.execution.commandline.CommandLineTaskConfigurer.configureTasksNow(CommandLineTaskConfigurer.java:67)
	... 123 more

Context
When migrating eager multi-valued properties from List<T> to lazy ListProperty<T> types we need to keep @Option working for them.

Duplicate of https://github.com/gradle/gradle/issues/10517.


ActiveField: add rangeInput(), colorInput() and switch mode to checkbox()

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues

@simialbi sure, but after maintainers allow changes in PR

@WinterSilence simialbi is a mainteiner for this repo, please follow his request.

@simialbi done

@WinterSilence Thx for the tests. I miss a switch input test. Could you please add one too?

@simialbi done

Thank you


NOMERGE: ci tests

wip
What
Checklist

[ ] I have read and agree to Contributor Guide and the Code of Conduct
[ ] I've included a screenshot or gif (if applicable)
[ ] I have tested demo.rerun.io (if applicable)

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

Reverting #3460 does what we'd expect:


Create MD detailing the base model used

We used one basic model when generating models for tests. We should details it's specifics somewhere.

I'm currently working on a way to present the geometry details in a md file.  This is a sample of one I have on a gist:
https://gist.github.com/kcoley/7c90f1d663e787de41e34220f461aedf#file-trianglenoindices-md
I realize as we do different test, the geometry information may change.  This poses these questions:

Would we need a unique geometry md file for each generated asset?
Should some information be omitted? (color/ tangents, etc.)
Should the presentation of this data be changed to be clearer?

In terms of consistency, it seems the positions, normals and tangents should not change for the initial set of tests we have created.  The texture coords and colors can potentially vary depending on the test.

We are currently using an image generated by @PatrickRyanMS

Where is image displayed?

Sorrry, was trigger happy.  We don't have this image yet.


Additional compile options...

-3, --30k
Make the memory restricted to 30,000 bytes, (and wrap when reaching the limits).
-w, --unwrapped, --un-wrapped
Make the memory pointer not allowed to underflow/overflow.
-c, --cell-unwrap, --cell-un-wrap
Make cells not allowed to underflow/overflow.
-u, --un-restricted
Un-restrict bytes from being a byte. Allow them to go as far as Lua will let them.
-b [8|16|32|64|unlimited], --bits=[8|16|32|64|unlimited]
Change the byte size (default is 8 bits).
-B [x], --bytes=[x]
Custom amount of memory [x] (number of bytes) allowed.
-s, --signed
Make numbers signed!
-n, --no-negative, --no-negative-memory, --non-negative-memory-location
Disallows memory access to the left of the initial 0th cell.
-i [c], --ignore=[c]
Ignore til end of line from [c] (a custom character).
-e [c], --end=[c]
Specify character which will end the program if encountered.

Also I'll get to these later.


[Windows] Removed nodes will try to add itself back after restart

rancher/rancher:v2.3.0-alpha3
Steps:

Create a Windows cluster
Add Windows node
Remove the node in Rancher UI
Restart the Windows node

Results:
The removed node will try to add itself back.

Expected:
It should not try to add itself back

reproduced the issue on v2.3.0-alpha3
Steps:

Create a Windows cluster
Add Windows node
Remove the node in Rancher UI
Restart the Windows node

Results:
The removed node will try to add itself back.
And gets added successfully.

verified on rancher:master-head and works fine.
Steps:

Create a Windows cluster
Add Windows node
Remove the node in Rancher UI
Restart the Windows node

Results:
The removed node will not add itself back.


ajy-UID2-1443-Accordion-component

Add accordion component from radix.
https://github.com/IABTechLab/uid2-self-serve-portal/assets/137864392/c50bd65f-8ae7-4e9a-8929-cd0f56c525bd

After talking with Jingyi, it probably makes more sense to use the Collapsible component rather than the accordion.


Dynamic properties?

I like the addition of properties for classes (and, more generally, this library). Is there any way to dynamically add them to my userdata?
I thought perhaps having a table as an exposed member (don't know if that is possible) that I can dynamically add properties to would be a way to do it, but it appears properties only work with usertype. Some sort of example of what I want to do:
struct DynamicObject
{
    void update_dynamic_props()
    {
        for(auto& prop : props)
        {
            dynamic_props[prop] = sol::property([&]() { return prop.second; }, [&](const std::string& new_val) { prop.second = new_val; });
        }
    }

    sol::table dynamic_props;
    std::unordered_map<std::string, std::string> props;
};

void property_test()
{
    state lua;
    lua.new_usertype<DynamicObject>("DynamicObject",
      							     "dynamic_props", &DynamicObject::dynamic_props
							     );

Properties aren't supported as something that can be generally set on anything just yet. Having the ability for tables would probably be good.
I'll put this on the TODO list. But I'm also in the last 2 weeks of school.

Just a note: I haven't forgot about this feature, but I'm trying to figure out what else to do besides "properties work with not-userdata now". What is the observable effect for the code you wrote?

While we're talking about additions to sol::property, will sol::this_state be acceptable to be present in the arguments of methods passed to sol::property? As in,
class Test {
public:
  int a;

  int getA(sol::this_state L) { return a; }

  void setA(sol::this_state L, int n) { a = n; }
};

// ..
L.new_usertype<Test>("Test",
                       "a", sol::property(&Test::getA, &Test::setA));

I have no idea if that would work. I'm almost gonna say "No", since we specifically provide either 1 argument or 0 to the function. I'll be sure to tag that on as something to do after this week (PAAAPEEERS AND GRAAADES Ihateschool).

Yup, it doesn't work right now. With some slightly sneaky use of meta methods it should be usable but it's a bit ugly ;)

What I really wanted is to bind dynamic properties directly to instances of userdata that are owned by the C++ side. However I figured that being able to add them to a table that is a member would be a useful compromise, assuming dynamic properties directly on the instance might not be doable.

What is a dynamic property? Something where you can rig up a userdata to have aribitrary keys that you don't set with a metatable / new_usertype? You do that by using the __index metamethod and the __newindex metamethod (__index = getter, __newindex = setter). E.g.:
struct dynamic {
     sol::object lookup_get ( const char* accessor ) {
            // look up data based on c-string accessor, get out the parameter
            // e.g.: thing[accessor]
     }

     sol::object lookup_set ( const char* accessor, sol::stack_object value ) {
            // set something based on accessor, using the value if you like
            // e.g.: thing[accessor] = value
     }
};

lua.new_usertype<dynamic>( "dynamic",
     sol::meta_function::index, &dynamic::lookup_get,
     sol::meta_function::new_index, &dynamic::lookup_set,
);

Try that. If that answers what you want, I think I'll close this issue then, because these methamethods are essentially what this functionality is for.

If you want it on a table, create a new metatable on that table and also set the index / __newindex values on it as well. You can access the metatable (and set it if you see its nil) from sol by doing auto x = mytable[sol::metatable_key]; if (!x) { /* no metatable: set it */ x = lua.create_table_with(); }

I'm gonna assume that overriding __index and __newindex gives you the power you want. Good luck!

I know this is old, but I think having a tutorial section with these examples would be useful.

Sorry this isn't working for me:

struct PropertySet
{
	sol::object get_property_lua(const char* name, sol::this_state s)
	{
		MY_INFO("PropertySet::get_property %s", name);
		auto& var = props[name];
		return sol::make_object(s, var);
	}

	void set_property_lua(const char* name, sol::stack_object object)
	{
		MY_INFO("PropertySet::set_property %s", name);
		props[name] = object.as<std::string>();
	}

	std::unordered_map<std::string, std::string> props;
};

struct DynamicObject
{
	PropertySet& get_dynamic_props()
	{
		return dynamic_props;
	}

	PropertySet dynamic_props;
};

void property_test()
{
	using namespace sol;

	state lua;
	lua.new_usertype<PropertySet>("PropertySet"
								  , meta_function::new_index, &PropertySet::set_property_lua
								  , meta_function::index, &PropertySet::get_property_lua
								  );
	lua.new_usertype<DynamicObject>("DynamicObject"
									,"props", sol::property(&DynamicObject::get_dynamic_props)
									);
	lua.set_function("print", [](std::string str) {
		MY_INFO("lua print: %s", str.c_str());
	});

	lua.script(R"__(
obj = DynamicObject:new()
obj.props.name = 'test name'
print('name = ' .. obj.props.name)
)__");
}

I get exception "[string "..."]:3: sol: attempt to index (set) nil value "test name" on userdata (bad (misspelled?) key name or does not exist)".
It was working (when I was taking and returning std::strings instead of sol::objects) before I updated to latest (so I could have the make_object function to take and return arbitrary types), but now this.

My bad there. I pushed the fix. Code should work as advertised.

Actually it's my fault, I don't know why I'm trying to work against your latest changes instead of last release. I rolled back to last release and it works fine now!

@Nava2 Examples are in the docs now and referenced in there as well. Thanks for the suggestion and thanks for this issue! I appreciate you guys reporting and working with me here.


Update Bundle Plugin (and ActiveMQ Client) to latest version for forward compatibility

I updated these dependencies before troubleshooting an issue with this component failing to initialize properly on 10.6. The dependency changes already seem to have it working with 10.6 again. I believe it was the Bundle Plugin that made the difference.
The JAR failed to build at all when using version 5.15.4 of the ActiveMQ client, until the Bundle Plugin was updated as well. It did build using version 5.15.3 of the ActiveMQ Client, but still failed at run time. It was lucky that I tried updating the Bundle Plugin instead of just sticking with 5.15.3, or I would still be scratching my head.
Note, this is still compiled against GeoEvent SDK 10.4.1, and the transport itself still reports as version 10.3.0. Thus it should be compatible with version 10.4.1 and above of GeoEvent Server, and should not break previously configured inputs that look for component version 10.3.0.

Could we see about getting this merged? The Esri:master version does not work on 10.6, and also lacks recent bug fixes and improvements in the ActiveMQ client library.
(BTW note, some of the changes listed above in the pull request were already merged with a previous pull request. Not sure why they showed up again, but probably because changes were made directly in master.  However, once this pull request is closed off, if there are any further changes required I will make them in branches to keep it tidier.)

@hanoch Please check it now. I believe it is ready to pull.

Done.


doc: fix broken link for Installation Guides

Summary of changes:
Fixes: broken link for Installation Guides

test-me-please

@halfcrazy Thank you very much for your PR!

@halfcrazy Looks great! Thanks for contributing !


Make antlr and antlr4 invisible for customer projects.

They will now only be visible in the test classpath for customer projects. I think it's better to use 'application' to control the test classpath of user projects, rather than introducing yet another test dependency that users must relate to.
antlr4-runtime was very straight forward, but antlr-runtime caused quite a bit of head scratching before I got it right.

We should ask ourselves if we will be able to maintain this, if we have to exclude 10, 20 or 50 dependencies. I don't have the full picture yet, but I think we'll end up somewhere between 15-30.


how to skip debug output to console ?

How can I avoid filling up the console with this job?
schedule         INFO     Running job Every 0.3 seconds do check_door_status() (last run: 2021-01-11 17:11:47, next run: 2021-01-11 17:11:47)
schedule         INFO     Running job Every 0.3 seconds do check_door_status() (last run: 2021-01-11 17:11:47, next run: 2021-01-11 17:11:47)
schedule         INFO     Running job Every 0.3 seconds do check_door_status() (last run: 2021-01-11 17:11:47, next run: 2021-01-11 17:11:48)

Set the logging level of the schedule logger to ERROR to disable the INFO logs from the scheduler:
schedule_logger = logging.getLogger('schedule')
schedule_logger.setLevel(level=logging.ERROR)

Let me know if this helps!

Set the logging level of the schedule logger to ERROR to disable the INFO logs from the scheduler:
schedule_logger = logging.getLogger('schedule')
schedule_logger.setLevel(level=logging.ERROR)

Let me know if this helps!

ok, I found
import logging
logging.getLogger('schedule').propagate = False

It would be nice if one could filer by level per schedule (set level per schedule, or filter by tag)

ok, I found
import logging
logging.getLogger('schedule').propagate = False

It would be nice if one could filer by level per schedule (set level per schedule, or filter by tag)

@SijmenHuizenga It does help, you beat me to answer my own question. Thanks,
A per-schedule or per-task option would still be nice.

@SijmenHuizenga It does help, you beat me to answer my own question. Thanks,
A per-schedule or per-task option would still be nice.

Our solutions were like seconds apart, that's quite a special thing ;)
The easiest way to achieve per-task or per-schedule logging is to disable the built-in logging and add your own logging lines to the jobs themselves. Take a look at this annotation logging example for maybe some inspiration ;)

Our solutions were like seconds apart, that's quite a special thing ;)
The easiest way to achieve per-task or per-schedule logging is to disable the built-in logging and add your own logging lines to the jobs themselves. Take a look at this annotation logging example for maybe some inspiration ;)


Is there any C# documentation so I could understand how to use the  google-cloud-dotnet? Thank you

https://cloud.google.com/dotnet
Hope this helps in getting you started.

And if you are particularly interested in how to use the client libraries in this repo, take a look at https://cloud.google.com/dotnet/docs/reference/help/getting-started and all the other topics that appear on the left hand side index under Client Library Help. Although samples there might be written for specific libraries the concepts explained apply to most libraries on this repo.


Pivot control does not work with appsdk 1.3-experimental1

Describe the bug
After upgrading to 1.3-experimental1 using a Pivot control results in a crash with WinRT originate error - 0x80004002 and then XAML parsing failed.
Steps to reproduce the bug

Add a Pivot to an app using appsdk 1.3-experimental1

Expected behavior
Should work as in 1.2
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.3 Experimental 1: 1.3.230202101-experimental1
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

True. But even after I revert the nuget package to 1.2.230118

@lhak is it persisting by running x86 configuration ?

Experiencing the same issue after trying out 1.3 experimental 1. Any views, controls or pages that contain a Pivot control will fail with a XAML parsing exception.

Thanks for finding and filing, this is an issue we'll be relnoting for an upcoming preview release and targeting to fix for 1.3 stable.

:tada:Microsoft.WindowsAppSDK v1.3.0 has been released which fixes this issue.

Release Notes
Nuget


Admin Captain Teammate view

Context
As a captain I can see each teammate of the team.
Expected Behavior
When I connect to the admin interface I must be able to see the a teammate in my team.
Acceptance Criteria
The teammate must look like as the figma model.

I made the following changes to the Yaki_backend_admin:

Modified the SQL query in **teamMateRepository** for the **findAllByTeam** methodI to retrieve the **lastName**, **firstName**, and **email** of a **teamMate**.
Modified the **findAllByTeam** method in **teamMateService**
Modified the JUnit unit test for the **findAllByTeam** method


Helper functions and examples for the SplitMap control in pyleaflet

Not sure if this is already implemented and I am just not aware of it.
I am always envious of our ENVI (haha) users who have the ability to lock multiple views/layers together to follow the cursor around. The closest thing that I can think of in the Python world is the SplitMap control that lets you compare two different layers side-by-side.
See https://ipyleaflet.readthedocs.io/en/latest/controls/split_map_control.html

Definitely not implemented by us yet as far as I know; the leafmap package does have an implementation: https://leafmap.org/notebooks/49_split_control/
(It's a pretty cool package actually, would be great to integrate it a bit more in our repo!)

The leafmap package is not currently available in the sandbox, is it? Looks cool though.

No, it's not - I've only read about it, not used it yet.

Just my luck, I may have hit a bug https://github.com/jupyter-widgets/ipyleaflet/issues/453


⚠ jaswdr.dev has degraded performance

In 49573fb, jaswdr.dev (https://jaswdr.dev/) experienced degraded performance:

HTTP code: 200
Response time: 675 ms

Resolved: jaswdr.dev performance has improved in 030c968.


Release 2.6 - egeria-base helm chart syntax error

$ helm install egeria egeria-base                                                                         [10:51:16]
Error: cannot load values.yaml: error converting YAML to JSON: yaml: line 86: could not find expected ':'

Caused by a bad edit from a search/replace when the presentation server UI was modified.

Additionally the docker-compose environment fails :

Checking OMAG Server Platform availability...
    Core Platform is active
        Checking OMAG Server cocoMDS2
           ... cocoMDS2 is configured
           ... cocoMDS2 is down - needs to be started
                Starting server cocoMDS2 ...
                   ...cocoMDS2 failed to start
                       error message is: OMAG-ADMIN-500-001 Method activateWithSuppliedConfig for OMAG server cocoMDS2 returned an unexpected exception of org.odpi.openmetadata.repositoryservices.ffdc.exception.OMRSConfigErrorException with message OMRS-CONNECTOR-400-004 The connection null passed to the EnterpriseOMRSRepositoryConnector is invalid.

The most relevant exceptions include
dev_1           | Caused by: OCFCheckedExceptionBase{reportedHTTPCode=400, reportingClassName='org.odpi.openmetadata.adapters.repositoryservices.graphrepository.repositoryconnector.GraphOMRSGraphFactory', reportingActionDescription='open', reportedErrorMessage='OMRS-GRAPH-REPOSITORY-400-021 It is not possible to open the graph database in the open method of org.odpi.openmetadata.adapters.repositoryservices.graphrepository.repositoryconnector.GraphOMRSGraphFactory class for repository cocoMDSx', reportedErrorMessageId='OMRS-GRAPH-REPOSITORY-400-021', reportedErrorMessageParameters=[open, org.odpi.openmetadata.adapters.repositoryservices.graphrepository.repositoryconnector.GraphOMRSGraphFactory, cocoMDSx], reportedSystemAction='The system was unable to open the graph repository graph database', reportedUserAction='Please check that the graph database exists and is not in use by another process.', reportedCaughtException=org.janusgraph.core.JanusGraphException: Could not execute operation due to backend exception, reportedCaughtExceptionClassName='org.janusgraph.core.JanusGraphException', relatedProperties=null}

dev_1           | 	Caused by: com.sleepycat.je.DiskLimitException: (JE 18.3.12) Disk usage is not within je.maxDisk or je.freeDisk limits and write operations are prohibited: maxDiskLimit=0 freeDiskLimit=5,368,709,120 adjustedMaxDiskLimit=0 maxDiskOverage=0 freeDiskShortage=1,285,390,336 diskFreeSpace=4,083,318,784 availableLogSize=-1,285,390,336 totalLogSize=1,427 activeLogSize=1,427 reservedLogSize=0 protectedLogSize=0 protectedLogSizeMap={}
dev_1           | 		at com.sleepycat.je.dbi.EnvironmentImpl.checkDiskLimitViolation(EnvironmentImpl.java:2733)

ie no storage can be written in compose.
This is likely caused by the configuration changes to support persistent storage in the k8s chart during 2.6 development

^^ Reading the message above carefully, the cause is that my local test environment is out of disk space ie:
freeDiskLimit=5,368,709,120
freeDiskShortage=1,285,390,336
diskFreeSpace=4,083,318,784

With persistence enabled each volume is pre-allocated.
Unlike the helm charts we have limited flexibility in the egeria configuration - so for example we can't easily switch
persistence off (which would be fine as the notebooks themselves default now to having it off)
I think the best course of action here is to change the default allocation to 0.5G per volume & to add a note to the docker-compose README.
Longer term it probably makes sense to consolidate in just working with k8s and not developing the docker compose chart further.

The default storage driver on docker-compose is 'local'. There are no options at the volume level for defining size.
Driver specific options can be set, and there is some info at https://docs.docker.com/engine/reference/commandline/volume_create/#driver-specific-options
However whilst storage size limits are possible on linux/macos, they are not supported on windows....
This is demonstrating some of the challenges with using compose.
Commenting out the support for storage with comments (so it offers an example) is probably the most pragmatic at this point since docker-compose is better suited to simpler use/smaller footprint environments, and a requirement for 20-30GB of storage is arguably unreasonable.

fixed


Create CI for cevmos

Given the complexity of properly setting up a cevmos deployment for testing while developing or reviewing PRs, we need a CI pipeline that performs continous integration against the changes and tests the whole stack end to end to prevent regressions or wasting time fighting with local setups.
Steps required for CI:

Check out evmos branch and compile target ethermint+optimint branch
Spin up mock network and run tests
Deploy a network with cevmos that uses a real DALC (celestia-node)
Test network upgrades against existing state for non-consensus breaking PRs

Besides an external CI, it would also be useful to have docker-compose scripts that can easily be run locally for at least some of these steps while developing.
(Edited by @jbowen93 )
A non conclusive list of sub tasks for this:

[ ] #18
[ ] #19
[x] #20

This is almost done
PR https://github.com/jbowen93/evmos/pull/8 does this for the evmos repo (though currently only on the jbowen93 fork)
PR https://github.com/celestiaorg/ethermint/pull/33 does this for the ethermint repo
Issue https://github.com/celestiaorg/optimint/issues/339 tracks work to do this for the optimint repo which should be almost the same as the ethermint work.


Custom SearchParameter for local search to support offline use case

Is your feature request related to a problem? Please describe.
The current search implementation in the FHIR engine is based on the FHIR specification where it is specified that the default search strategy for token search as string is an exact match. We have a requirement to perform partial match to reduce the search space while displaying results on the UI.
Describe the solution you'd like
Support SearchParameter for custom search strategies .
Describe alternatives you've considered
We have a working version with online search, but this is needed for the offline use case.
cc: @jingtang10 @fredhersch

partial search of a token (e.g. use contains, basically treating a token as a string) <-- highest priority
extension search <-- second priority
normal search <-- there's nothing that's needed

Token Text Search:
The fhir query supports search by modifiers like :missing, :exact, :text, :in, :below, :above, :not, :[type], :identifier,:above, :below etc for different parameters (Token, String, Reference, URI). For token specifically these are
ALL -> :missing; e.g. gender:missing=true
TOKEN -> :text, :in, :below, :above and :not-in
Current requirement seems like asking for a support of :text modifier. Which means searching text field of CodeableConcept or display field of Coding. Please note that this does not do partial search on code field. Here is the doc for token modifiers in details http://hl7.org/fhir/R4/search.html#token.
Example -> Condition?code:text=headache
Possible Solution:

The current code should support modifiers (Enum) into query depending on SearchParam type. It would be similar to operation into current code.
Once added as filter it would validated for applicability for given param, and then when generating query (getQuery) it would add corresponding literal to query LIKE '%SEARCH%' (when :text modifier is present).

Extension search:
FHIR by default does not support extension search.
To allow search by extension there is need to

Add a custom search param on server as well http://hl7.org/fhir/R4/searchparameter.html. See example http://hl7.org/fhir/R4/searchparameter-example-extension.json.html.
Once this done we need to think about how to let mobile app know about the custom search Param i.e. Sync Search Params?
And then Add support for a handling custom search param i.e. process the type and add query literal from synced Search Param.
Handle the query content from expression or xpath of Custom Search Param

@jingtang10 @f-odhiambo

There is another ticket which aims working on Full text search i.e.e FTS (android FTS-3/4). The FTS is powerful but specific to android with a specific set of features. The language/syntax and virtual table structure is also its own.
As mentioned in comment above the FHIR search is very powerful and has specific rules for each param type. Moreover hapi itself has implemented the search using Lucene the use of Lucene on android SDK can help with query syntax conformance with HAPI query syntax with all features available without any customization/deviation/complexity easily.
Some aspects to evaluate are performance (Lucene claims to be faster), complexity (FTS has shorter learning curve), scalability (HAPI uses Lucence hence accommodating syntax and features is easier), size (Lucene claims to be compact but uses Files, FTS uses sqlite) etc.
I am doing a small POC on Lucene and then we can benchmark and decide the workable approach.
@jingtang10 @f-odhiambo @shoaibmushtaq25

An example use case is Partial search with id. Eg:
fhirEngine
        .search<Encounter>(
          Search(ResourceType.Encounter).apply {
            filter(service-type, { this.value = of("Patient Check In") })
          }
        )
        .isEmpty()

The SearchParameter that we are using in the HAPI FHIR server is
{
    "resourceType": "SearchParameter",
    "id":"786344c7-644e-4665-80fa-86290c9bb71a",
    "title": "Service Type Text",
    "status": "active",
    "code": "service-type",
    "base": [
      "Encounter"
    ],
    "type": "string",
    "expression": "Encounter.serviceType.text",
    "xpathUsage": "normal"
}


Update to SDL2 2.0.9

Would it be possible to update this to SDL2 2.0.9? The latest version has so many new features and improvements compared to this version.
I could look into it if I was shown how to test wraps locally so I can be sure I'm committing something that works. I have had trouble making my own wraps because I could not figure out a way to test it properly.

Just submit a pull request. That's really the best way now.
There is also mesonwrap review tool from https://github.com/mesonbuild/wrapweb, but it works the best with submitted pull requests.

I see some assistance is needed how can I help?

Hi, thank you for looking into this. I just wanted to indicate that a pull request is welcome: https://mesonbuild.com/Adding-new-projects-to-wrapdb.html#add-a-new-wrap
I can review and merge it.

Should I cover the missing version between the current sdl2 wrap and the latest version of sdl2 or just do the latest?

I don't think there is much of a point. People tend to use the latest version and they can submit the older one if they need to.

Will get to work as soon as possible.

Quick question. How do I reliably get a sha256 value for the archive? Asking because I would not like to get this wrong.


Bug when creating a {New Event} from a Monster activation

In a custom monster, if you click "Activations" and click {New Event} it will create Event0

If you then click the -> to open it and change the name:

When you click back (or open the monster from components) it gives you this error:

Events and spawns all work fine this way, just custom monsters that don't seem to link to the new name.

This bug is more board than this.  Any horror/evade/activation events that are renamed will not update correctly.

Check out the prerelease here, let me know if you find any bugs:
https://github.com/NPBruce/valkyrie/releases/tag/prerelease%2F1.5%2Fv1.5.0a


added a function to not validate names that start with a "." or "_"

Closes: #1
Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

i have signed the CLA


Bump datastore-v1-proto-client dependency to match libraries-bom

There are some conflicts when using Datastore client along with Beam imported.
I think it is important to get this in on Beam 2.49.0 to avoid dependency conflicts out there.
https://mvnrepository.com/artifact/com.google.cloud/libraries-bom/26.17.0 uses https://mvnrepository.com/artifact/com.google.cloud/google-cloud-datastore-bom/2.15.0, but somehow the BOM doesn't mandate the version for the proto dep here, so upgrading manually for now.

R: @Abacn

JavaPreCommit known flink test fakes; SQL tests Timeout waiting to lock Build cache infra flakes. Most likely unrelated. Triggering again

Run Java PreCommit

Run Python_Transforms PreCommit

Run SQL_Java17 PreCommit


Select Bug

I noticed this in docs, as well as locally.
Visually it looks like the Select is working, but the native select element's value is being reset, or set to an empty string.
Only on the second time of clicking the option will it get set properly.

Fixed on v2.1.6


PTM info output

#253 #237
Please let me know when you want to check the code. Thank you.

Sure, tomorrow morning! Make sure that CI are passing


preLaunchTask not working when using require("dap").continue()

Hi, I have the following in my launch.json
"name": "Remote GDB",
"type":"cppdbg",
"request": "launch",
"preLaunchTask": "gdb_server",

and this is part of a task in task.json
"taskName": "gdb_server",
"label": "Run remote gdb server",
"type": "shell",
"command": "launch_ssh_gdb_server.sh"

but when I launch the require("dap").continue() do not start the gdb_server task
Is there any reason why this config should not work?

https://github.com/microsoft/vscode/commit/18ca3040b1b42391501a080aef5766b2124aee7e
taskName is deprecated. Use the "label" field instead in the preLaunchTask

Sorry but still no luck. Changed to
"name": "Remote GDB",
"type":"cppdbg",
"request": "launch",
"preLaunchTask": "Run remote gdb server",

and removed the label field from tasks.json but I still don't see any task running in Overseer pane

Apologies, I've been off the grid for a bit. The launch.json file looks correct, but in your tasks.json you should keep the label field, and remove the taskName. You'll know it's correct if you do :OverseerRun and "Run remote gdb server" shows up in the list of available tasks

Did exactly what you said but the preLaunchTask doesn't spawn when running nvim-dap configuration. I can see the "Run remote gdb server" item in OverseerRun list and it works if I select it, but it doesn't start automatically when I run "Remote GDB" configuration. When I call require("dap").continue(), the nvim-dap menu shows up, I select "Remote GDB" but Overseer doesn't run the preLaunchTask. How can I help you to address the problem?

I just added a bit more logging here 2784f668c4eb2b77a002f3a4408d2a6600965662
Set the log level to TRACE and see what the output is when you run require("dap").continue() and select "Remote GDB".
overseer.setup({
  log = {
    {
      type = "file",
      filename = "overseer.log",
      level = vim.log.levels.TRACE,
    },
  },
})

By default the log file should be under .cache/nvim/overseer.log. You should see a line that indicates that it's starting the preLaunchTask. If you don't, then that indicates something going wrong with the hook.

Hi, I've tried to log to a file like you suggested, but the file is empty when if I start nvim-dap with require("dap").continue(). The logging works because I can see the logs if I start overseer task manually. It seems the preLaunchTask is not called when starting nvim-dap debug session

Are you trying to do any sort of lazy-loading for overseer? Have you called overseer.setup() before the call to require("dap").continue()?

Ok, you was right, I changed the order of the plugins and now the task starts correctly. Anyway, I have another problem now. The task starts but the debug sessions doesn't. The task stays in the "RUNNING" state because it is a gdb server that listen on a port. Does overseer waits for the task to go in "SUCCESS" state before starting the debug session?

Ah, the good news is that this works the same way as it does in VS Code. The bad news is that it's annoying in VS Code.
Basically, if you want to run a task in the background while you're debugging, the task has to be defined as isBackground and it needs to have a problem matcher with a background property that defines when the task is "sort of complete". You can read more about this stack overflow or the discussion on this vscode issue.

The launch json looks correct, but you need to keep the "label" in
tasks.json. "taskName" was deprecated to be replaced by "label".
On Thu, Aug 18, 2022, 12:09 AM redirect11 @.***> wrote:

Sorry but still no luck. Changed to
"name": "Remote GDB","type":"cppdbg","request": "launch","preLaunchTask": "Run remote gdb server",
and removed the label field from tasks.json but I still don't see any task
running in Overseer pane
—
Reply to this email directly, view it on GitHub
https://github.com/stevearc/overseer.nvim/issues/17#issuecomment-1219076243,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD3XJ42GEAXBYQFW2VG5FLVZXHTJANCNFSM56YNIKGQ
.
You are receiving this because you commented.Message ID:
@.***>


Error in production

I managed to run peatio in development and it works great but when I run it in production I get this:
"An unhandled lowlevel error occurred. The application logs may have details."
Application log is empty

Hello @hamid1989
We don't support passenger. Run app in docker and you will get output. Or you can update config/environments/shared/logger.rb to suit your needs.

I didn't used passenger, I deployed it with docker and using localhost:3000, when I run rails server with RAILS_ENV=production I get this and no logs can be found.
I'm going to create new layout for peatio and I'm learning it's code so I can know what changes can cause app working problems.


Failing to upgrade due to conflict

Describe the bug
On a large cluster, the delay of leader election and conflicts when updating CRDs blocked Longhorn upgrading
To Reproduce
Steps to reproduce the behavior:

create a large cluster of many nodes (about 30 nodes)
Install Longhorn v1.0.0
Upgrade Longhorn to v1.0.1
There is a long delay on the upgrading process

Additional context
more detail about the logs and discussions are at https://github.com/longhorn/longhorn/issues/1379#issuecomment-665804479

It's probably blocked instead of being very slow.

Need to backport to v1.0.2

After the fix, it takes ~16 mins for 30-node cluster. Still ~ 30s per node. It seems like  the delay of leader election still persists.

After the fix, it takes ~15 mins for 30-node cluster. Still ~ 30s per node. It seems like  the delay of leader election still persists.

It seems that each manager will loop in retry until it becomes the leader

@shuo-wu
Manager enters the retry loop. Then goes into upgrade(). Then goes into leaderelection.RunorDie(). It is sleeping inside leaderelection.RunorDie(), wakes up every 2 seconds try to vote to become leader. When it becomes leader, it does the upgrade. If it gets into an error while upgrading it will back out to the retry loop, sleep 3 seconds and try upgrade() again.
So, manager will sleep/wakeup in leaderelection.RunorDie() until it become leader.
I am guessing that the bug inside leaderelection.RunorDie() prevents the manager to give up the leadership even when it successfully finish upgrading . So, it is forced to give up its leadership after 20s LeaseDuration. https://github.com/longhorn/longhorn-manager/blob/0ad9564e091ad3ce87989e8b022fe72241f637f5/upgrade/upgrade.go#L98
How do you think?

I just double check the arg LeaseDuration and here is the explanation:

LeaseDuration is the duration that non-leader candidates will wait to force acquire leadership. This is measured against time of last observed ack.

I am not sure what force acquire leadership is, and if this is the culprit of the 30s delay.
2. We may need to verify how the error is triggered. Then I can find a correct way to release the lock in advance.

@shuo-wu Phan was referring to https://github.com/longhorn/longhorn/issues/1379

@PhanLe1010 Could you please add manual test cases
https://github.com/longhorn/longhorn-tests/tree/master/docs/content/manual
We maintain our manual test cases here

@khushboo-rancher
Does it mean that I will have to create a PR into the longhorn-tests repo?

@PhanLe1010 Yes, like this one - https://github.com/longhorn/longhorn-tests/pull/383

Thanks @khushboo-rancher. Added

Verified on longhorn-master - 08-05-2020
Validation - Passed
Tested with 32 nodes multiple times, Installation and upgrade from v1.0.0 to master worked fine.


Fix #3284 to get kafka.bootstrap.servers from DevServicesLauncherConf…

…igResultBuildItem

@jamesnetherton I think this fix could be conflict with https://github.com/apache/camel-quarkus/commit/f96c117e3179621726af06dc23dcefe6efd4e103 in quarkus-main.
So please take care of merging quarkus-main to main. Thanks !

I'm afraid that we can not produce DevServicesConfigResultBuildItem since there is a dependency cycle.  So I think we should abondond these two commits in quarkus-main https://github.com/apache/camel-quarkus/commit/f96c117e3179621726af06dc23dcefe6efd4e103 and https://github.com/apache/camel-quarkus/commit/dc5be32f7ad77890e7bd006bb098b83f956d3639


 The filter contains two operational modes, one where velocity is estimated, another where the velocity is set as a constant parameter
Verification
Unit test included
Documentation
rst documentation included
Future work
none

ignoring the random unit test error in the linux build since it's a known issue


WIP: fix accidently quadratic behavior

we've recmoputed item map every time previously :man_facepalming: :man_facepalming: :man_facepalming:

bors r+

Found the problem with GC: this bit depends (in salsa's sense) on raw syntax trees, and so is constantly changing.


Spevacus: Watch techinspiration.net

Spevacus requests the watch of the watch_keyword techinspiration\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

techinspiration\.net has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Daniil in Charcoal HQ


Click pointing doesn't rotate you correctly

When I was trying it was going the opposite way so I assume it's some worldrotation shenanigans.

Fixed in https://github.com/space-wizards/space-station-14/commit/16c31ade0f0dbd1c7991fbd2fef172e0d34e3bd5


Propose a file sharing / auth mechanism for CloudFlare R2

Cloudflare R2 promises no egress fees on data (worldwide) - would be good to think of a way that controlled datasets could be shared.
There is some sort of 'lambda' that runs on each request - and can enforce custom auth - but would have to work out how to do passports/visas processing?

I mean can we literally make an access key/credentials (however CloudFlare does it) - and just do Object store presigned URLs in the first instance?


Fix multilingual VALUES and equals signs in values

Fixes two issues: multilingual VALUES parsing into too many dimensions (e.g. VALUES[de]=blabla) and a record value with an equals sign breaking parsing (e.g. VALUES="my=value"

Thank you!

@wyozi do you have an example of PX files which was failing to you? I'd like to add a test

@ferblape this one should have both cases


Add Bitcoin Support

Thank you! Added a few comments with fixes I'd appreciate before a final review. This also needs tests. If you can write them, awesome. If not, I can do that.

If you can get to the fixes by this weekend, awesome. If not, I'll take care of Bitcoin support

Appreciate the help @ascension—I'll take it from here. Just whipped up stripe-as-promised so the majority of the code here will disappear anyway.


Validation Errors Display

After defining the rules in the Repository/{Model Name}/{Model Name}.php, the page just seems to refresh and not display the error or session information. The layout is including the /partials/message.blade.php and /partial/error.blade.php
Any ideas?

Check the routes and see if the routes are loading the web middleware twice, I just recently pulled the web middleware from the builders etc.

I can verify this. All working now. Thanks.


[vcpkg] install using_parser_urdf target

install using_parser_urdf target
It fix for linux and mac. need to fix for windows as well.

@talregev it is helpful for mantainers if you provide a link of the previous discussions on this. In a nutshell, when sdformat is compiled as a static library (BUILD_SHARED_LIBS=OFF) the privatly linked target using_parser_urdf needs to be exported, otherwise there is an installation error.
@talregev can you provide the erro you get on Windows with this PR? Otherwise it is difficult for other people to provide help if they do not even know the error you are having.

@traversaro @azeey
Link to the discussion:
https://github.com/microsoft/vcpkg/pull/31280#issuecomment-1546619308

logs of vcpkg with the error
sdformat13.zip
urdfdom already install from vcpkg.
C:\src\vcpkg>type C:\src\vcpkg\buildtrees\sdformat13\config-x64-windows-out.log
[1/2] "C:/src/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" -E chdir ".." "C:/src/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" "C:/src/vcpkg/buildtrees/sdformat13/src/t13_13.5.0-6e97358adf.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=C:/src/vcpkg/packages/sdformat13_x64-windows" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DRUBY=C:/src/vcpkg/downloads/tools/ruby/rubyinstaller-2.7.4-1-x86/bin/ruby.exe" "-DBUILD_TESTING=OFF" "-DSKIP_PYBIND11=ON" "-DUSE_INTERNAL_URDF=OFF" "-DCMAKE_DISABLE_FIND_PACKAGE_Doxygen=ON" "-DCMAKE_REQUIRE_FIND_PACKAGE_GzURDFDOM=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_Python3=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/src/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/src/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/src/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/src/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
FAILED: ../CMakeCache.txt
"C:/src/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" -E chdir ".." "C:/src/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" "C:/src/vcpkg/buildtrees/sdformat13/src/t13_13.5.0-6e97358adf.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=C:/src/vcpkg/packages/sdformat13_x64-windows" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DRUBY=C:/src/vcpkg/downloads/tools/ruby/rubyinstaller-2.7.4-1-x86/bin/ruby.exe" "-DBUILD_TESTING=OFF" "-DSKIP_PYBIND11=ON" "-DUSE_INTERNAL_URDF=OFF" "-DCMAKE_DISABLE_FIND_PACKAGE_Doxygen=ON" "-DCMAKE_REQUIRE_FIND_PACKAGE_GzURDFDOM=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_Python3=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/src/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/src/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/src/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/src/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
-- The C compiler identification is MSVC 19.35.32216.1
-- The CXX compiler identification is MSVC 19.35.32216.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- sdformat13 version 13.5.0
-- Operating system is Windows
-- Attempting manual search for tinyxml2
-- Found TINYXML2: TRUE
-- Looking for TINYXML2 - found

-- Looking for urdfdom - not found

-- Looking for urdfdom - not found

-- Could NOT find PY_psutil (missing: PY_PSUTIL)
-- Found ruby executable: C:/src/vcpkg/downloads/tools/ruby/rubyinstaller-2.7.4-1-x86/bin/ruby.exe
-- Looking for gz-math7 -- found version 7.0.2
-- Searching for dependencies of gz-math7
-- Looking for gz-utils2 -- found version 2.0.0
-- Searching for dependencies of gz-utils2
-- Looking for gz-math7 - found

-- Looking for gz-utils2 -- found version 2.0.0
-- Searching for dependencies of gz-utils2
-- Searching for <gz-utils2> component [cli]
-- Looking for gz-utils2-cli -- found version 2.0.0
-- Searching for dependencies of gz-utils2-cli
-- Looking for gz-utils2 - found

-- Searching for Python - not found.
CMake Warning at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:69 (message):
   CONFIGURATION WARNINGS:
   -- Python psutil package not found. Memory leak tests will be skipped
   -- Python is missing: Python interfaces are disabled.
Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

CMake Error at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:73 (message):
  -- BUILD ERRORS: These must be resolved before compiling.
Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

CMake Error at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:75 (message):
  --    Couldn't find the urdfdom >= 1.0 system installation
Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

CMake Error at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:77 (message):
  -- END BUILD ERRORS

Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

CMake Error at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:82 (message):
  Errors encountered in build.  Please see BUILD ERRORS above.
Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

-- Configuring incomplete, errors occurred!
[2/2] "C:/src/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" -E chdir "../../x64-windows-dbg" "C:/src/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" "C:/src/vcpkg/buildtrees/sdformat13/src/t13_13.5.0-6e97358adf.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/src/vcpkg/packages/sdformat13_x64-windows/debug" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DRUBY=C:/src/vcpkg/downloads/tools/ruby/rubyinstaller-2.7.4-1-x86/bin/ruby.exe" "-DBUILD_TESTING=OFF" "-DSKIP_PYBIND11=ON" "-DUSE_INTERNAL_URDF=OFF" "-DCMAKE_DISABLE_FIND_PACKAGE_Doxygen=ON" "-DCMAKE_REQUIRE_FIND_PACKAGE_GzURDFDOM=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_Python3=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/src/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/src/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/src/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/src/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
FAILED: ../../x64-windows-dbg/CMakeCache.txt
"C:/src/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" -E chdir "../../x64-windows-dbg" "C:/src/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" "C:/src/vcpkg/buildtrees/sdformat13/src/t13_13.5.0-6e97358adf.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/src/vcpkg/packages/sdformat13_x64-windows/debug" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DRUBY=C:/src/vcpkg/downloads/tools/ruby/rubyinstaller-2.7.4-1-x86/bin/ruby.exe" "-DBUILD_TESTING=OFF" "-DSKIP_PYBIND11=ON" "-DUSE_INTERNAL_URDF=OFF" "-DCMAKE_DISABLE_FIND_PACKAGE_Doxygen=ON" "-DCMAKE_REQUIRE_FIND_PACKAGE_GzURDFDOM=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_Python3=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/src/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/src/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/src/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/src/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
-- The C compiler identification is MSVC 19.35.32216.1
-- The CXX compiler identification is MSVC 19.35.32216.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- sdformat13 version 13.5.0
-- Operating system is Windows
-- Attempting manual search for tinyxml2
-- Found TINYXML2: TRUE
-- Looking for TINYXML2 - found

-- Looking for urdfdom - not found

-- Looking for urdfdom - not found

-- Could NOT find PY_psutil (missing: PY_PSUTIL)
-- Found ruby executable: C:/src/vcpkg/downloads/tools/ruby/rubyinstaller-2.7.4-1-x86/bin/ruby.exe
-- Looking for gz-math7 -- found version 7.0.2
-- Searching for dependencies of gz-math7
-- Looking for gz-utils2 -- found version 2.0.0
-- Searching for dependencies of gz-utils2
-- Looking for gz-math7 - found

-- Looking for gz-utils2 -- found version 2.0.0
-- Searching for dependencies of gz-utils2
-- Searching for <gz-utils2> component [cli]
-- Looking for gz-utils2-cli -- found version 2.0.0
-- Searching for dependencies of gz-utils2-cli
-- Looking for gz-utils2 - found

-- Searching for Python - not found.
CMake Warning at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:69 (message):
   CONFIGURATION WARNINGS:
   -- Python psutil package not found. Memory leak tests will be skipped
   -- Python is missing: Python interfaces are disabled.
Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

CMake Error at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:73 (message):
  -- BUILD ERRORS: These must be resolved before compiling.
Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

CMake Error at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:75 (message):
  --    Couldn't find the urdfdom >= 1.0 system installation
Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

CMake Error at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:77 (message):
  -- END BUILD ERRORS

Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

CMake Error at C:/src/vcpkg/installed/x64-windows/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:82 (message):
  Errors encountered in build.  Please see BUILD ERRORS above.
Call Stack (most recent call first):
  CMakeLists.txt:157 (gz_configure_build)

-- Configuring incomplete, errors occurred!
ninja: build stopped: subcommand failed.

Given the error:
  --    Couldn't find the urdfdom >= 1.0 system installation

what is failing is the call gz_find_package(GzURDFDOM VERSION 1.0 QUIET) in https://github.com/gazebosim/sdformat/blob/e55378e6d03ca6b38ed8d7017f0c29dc4947cb30/CMakeLists.txt#L59 , nothing directly related to the sdformat13::using_parser_urdf target. Perhaps a possible debug step is to remove the QUIET from gz_find_package(GzURDFDOM VERSION 1.0) to get a more informative error message?

I will remove the quiet and give you the logs again.

I will remove the quiet and put the logs again here.
I run it without the quite. the same output. Putting here the logs:
sdformat13.zip

I found workaround.
If i change it to gz_find_package(GzURDFDOM) without version, it compile. Is it acceptable solution?

@traversaro @azeey I found workaround. If i change it to gz_find_package(GzURDFDOM) without version, it compile. Is it acceptable solution?

This is a gentle remind about my comment.
I already see in the vcpkg PR that this modification (remove the version of urdfdom) is help and compile in all os (windows, linux osx).
I guess this is come that vcpkg didn't install correctly the urdfdom (it also have a problem to install it static only in windows).
Are you willing to help to fix that urdfdom in vcpkg? Is my workaround is acceptable solution?
I will happy to hear your comments and thoughts.

I'm not too familiar with vcpkg, but if we want static builds, shouldn't using_parser_urdf be built as a static library as well? It's not clear to me why it needs to be installed.

I'm not too familiar with vcpkg, but if we want static builds, shouldn't using_parser_urdf be built as a static library as well? It's not clear to me why it needs to be installed.

@traversaro Can you explain the problem?

@azeey @scpeters
This PR is ready for review. this changes is working on linux, mac and windows.
Can you review it?

I'm not too familiar with vcpkg, but if we want static builds, shouldn't using_parser_urdf be built as a static library as well? It's not clear to me why it needs to be installed.

@azeey You can read @traversaro comment here:
https://github.com/microsoft/vcpkg/pull/31280#issuecomment-1546619308

I'm not too familiar with vcpkg, but if we want static builds, shouldn't using_parser_urdf be built as a static library as well? It's not clear to me why it needs to be installed.

@traversaro Can you explain the problem?

So, the problem is that if you have two libraries in CMake, i.e. :

libA : a library of type INTERFACE
libB:  a library of type SHARED or STATIC, depending on BUILD_SHARED_LIBS

and you have in the code:
target_link_libraries(libB PRIVATE libA)

if libB is SHARED, there is no need to install libA, while if libB is static, you need to install also libA.

I'm not too familiar with vcpkg, but if we want static builds, shouldn't using_parser_urdf be built as a static library as well? It's not clear to me why it needs to be installed.

@traversaro Can you explain the problem?

So, the problem is that if you have two libraries in CMake, i.e. :

libA : a library of type INTERFACE
libB:  a library of type SHARED or STATIC, depending on BUILD_SHARED_LIBS

and you have in the code:
target_link_libraries(libB PRIVATE libA)

if libB is SHARED, there is no need to install libA, while if libB is static, you need to install also libA.

Thank you for explain that in detail!

https://github.com/gazebosim/sdformat/pull/1343 fixes static builds and passes CI, so I'll close this in favor of that.

@azeey Please close this issue only after the fix will merge. Thank you.


add Dispatch event to subgraph; map to a Message entity that records the cross-chain message

Description
Fixes #1753
Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[ ] Refactoring
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires changes in customer code

High-level change(s) description - from the user's perspective

Dispatch event now emits destinationDomain.

Subgraph now records Message for cross-chain use by listening to targeted Connector contracts.

We can consult the Message record in our polling loop for calling proveAndProcess (i.e. track which Messages need to be proven/delivered to which domains).

NOTE: Still need to add deployments/startBlock to the config for active deployments! Also, still need to redeploy the subgraph for staging!

Closing this out as I believe this got replaced by other subg event logic


Version of web demo

Does anyone know the version of zxing web demo is using?
I just realized the web demo has better recognization ablity than my local ZxingReader?
I am currently using python binding with version 2.0.0.
Thanks in advance.

The web reader demo is a little newer than 2.1.0 but in terms of detection rate it is equivalent to 2.1.0. See the release notes for info about improvements of 2.1. over 2.0.

Can you confirm that the 2.1 version of the python module behaves the same as the web-version? If so, please close this issue, if not, please send me a sample image that shows the different behavior of the two.

Can you confirm that the 2.1 version of the python module behaves the same as the web-version? If so, please close this issue, if not, please send me a sample image that shows the different behavior of the two.

I am not sure yet. Will test it next week.
I just upgraded my Python module from 2.0.0 to 2.1.0.
Sure, I am closing this issue. Thanks!


[docs] Remove outdated showcase

It seems like Code Typing Tutor does not exist anymore.

[x] I have followed (at least) the PR section of the contributing guide.

@LorenzHenk Thank you


Fixing readme to reflect reality.

Hey @antonbabenko.. Your Readme is a bit out of sync. Cheers, M.

Thanks, Marteen!
Better late than never, right? :)


Mull has become extremely memory hungry

It looks like the issue we had in the past.
I am running #582, #583 on some simple C++ project and the stats are as follows:
Running original tests (threads: 8): 71/71. Finished in 3157ms.
Searching mutants across functions (threads: 8): 5923/5923. Finished in 69ms.
Applying filter: no debug info (threads: 8): 42737/42737. Finished in 13ms.
Applying filter: file path (threads: 8): 36099/36099. Finished in 384ms.
Applying filter: junk (threads: 8): 28140/28140. Finished in 93285ms.
Preparing mutations (threads: 1): 1/1. Finished in 227280ms.
Applying mutations (threads: 1): 468/468. Finished in 33ms.
Compiling original code (threads: 8): 49/49. Finished in 131511ms.
Running mutants (threads: 8): 158/468

At the time I interrupted this execution, the macOS Activities Monitor was showing 30 GB RAM memory consumption by Mull.

Fixed by #595


git stash on pull?

Now that the git repo is exposed by a RW bind mount, people can edit stuff (when they are not aware it's a git repo). Just breaks pulling because of uncommitted local changes.
We can, before each pull

git stash
git checkout

prefer stashing so at least you might look at that stuff and it's probably not megabytes, of course we treat these local git repos as ephemeral, so in the end you'll loose them anyway, but it may allow for quick local changes and testing.

closed via f82ef8e


Return types of apply methods

For now, IO.apply and ZIO.apply returns Task.
Wouldn't it be better to return UIO here, so it can be used with whatever E I want?

I think having a Task here is a safe default, as this makes the failure recoverable if in doubt.
@jdegoes I would think that it is preferable to use the explicit effect or effectTotal respectively here, is that right?

Is it an option to add ZIO.pure which doesn't use call-by-name argument? Now it's not very clear how to create pure instances of ZIO[Any, Nothing, A] (except using UIO.apply).

I think ZIO.succeed is the canonical solution to this. With ZIO.succeedLazy as the lazy variant

@mschuwalow OK, makes sense. Thanks, I'm closing the issue.


Additions and modifications

Added new translations and made minor modifications to existing ones where the translation didn't make sense in the context required.

It seems I've started my translations on a branch that fails the build, but I checked what fails and it has nothing to do with my commits. Could you merge these two commits or should I re-do my changes on a clean fork?

Thanks for your translations, @SuperPranx! Your pull request doesn't have any error. The build sometimes fails (and I don't understand why).

You don't need to do a clean fork. You can sync your repo to origin by commands in cmd/bash/whatever:
git checkout master
git fetch upstream
git merge upstream/master
git push
in your git workdir to get changes from codecombat/codecombat repo, merge it to your master branch and push it to your remote github repo.