unable to compile

I am trying to install winloop and fail:
winloop from sources <IP_ADDRESS>
python 3.10
pip 23.2
conda
cython               3.0.0
Win 10.
When calling python setup.py build_ext --inplace I get error (trace below).
same error when installing by pip install winloop. just it gets einloop 0.0.6/
(py10) C:\petals\winloop>python setup.py build_ext --inplace
Compiling winloop\loop.pyx because it changed.
[1/1] Cythonizing winloop\loop.pyx
warning: winloop\includes/consts.pxi:1:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:3:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:4:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:5:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:7:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:8:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:10:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:13:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:16:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:21:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:24:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:25:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:1:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:3:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:4:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:5:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:7:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:8:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:10:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:13:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:16:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:21:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:24:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:25:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\handles/stream.pyx:3:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\handles/process.pyx:364:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\handles/process.pyx:365:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\handles/process.pyx:366:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\handles/process.pyx:367:0: The 'DEF' statement is deprecated and will be removed in a future Cython version. Consider using global variables, constants, and in-place literals instead. See https://github.com/cython/cython/issues/4310
warning: winloop\handles/udp.pyx:351:8: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead.   This may cause incorrect vtables to be generated.
warning: winloop\handles/basetransport.pxd:54:25: Previous declaration is here
warning: winloop\handles/stream.pyx:284:9: Compatible but non-identical C method '_is_reading' not redeclared in definition part of extension type 'UVStream'.  This may cause incorrect vtables to be generated.
warning: winloop\handles/basetransport.pxd:54:25: Previous declaration is here
warning: winloop\handles/udp.pyx:135:9: Compatible but non-identical C method '_is_reading' not redeclared in definition part of extension type 'UDPTransport'.  This may cause incorrect vtables to be generated.
warning: winloop\handles/basetransport.pxd:54:25: Previous declaration is here
Error compiling Cython file:
...
# === overloads ===
cdef _new_socket(self)
cdef size_t _get_write_buffer_size(self) noexcept

cdef bint _is_reading(self)
                     ^

winloop\handles/basetransport.pxd:54:25: C method '_is_reading' is declared but not defined
Traceback (most recent call last):
File "C:\petals\winloop\setup.py", line 91, in
do_installation()
File "C:\petals\winloop\setup.py", line 57, in do_installation
ext_modules=cythonize(ext),
File "c:\conda\envs\py10\lib\site-packages\Cython\Build\Dependencies.py", line 1134, in cythonize
cythonize_one(*args)
File "c:\conda\envs\py10\lib\site-packages\Cython\Build\Dependencies.py", line 1301, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: winloop\loop.pyx

On Tue, Jul 25, 2023 at 4:13 PM Poedator @.***> wrote:

I am trying to install winloop and fail:
winloop from sources <IP_ADDRESS>
python 3.10
pip 23.2
conda
cython 3.0.0
Win 10.
When calling python setup.py build_ext --inplace I get error (trace
below).
same error when installing by pip install winloop. just it gets einloop
0.0.6/
(py10) C:\petals\winloop>python setup.py build_ext --inplace
Compiling winloop\loop.pyx because it changed.
[1/1] Cythonizing winloop\loop.pyx
warning: winloop\includes/consts.pxi:1:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:3:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:4:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:5:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:7:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:8:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:10:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:13:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:16:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:21:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:24:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:25:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:1:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:3:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:4:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:5:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:7:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:8:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:10:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:13:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:16:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:21:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:24:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\includes/consts.pxi:25:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\handles/stream.pyx:3:0: The 'DEF' statement is deprecated
and will be removed in a future Cython version. Consider using global
variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\handles/process.pyx:364:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\handles/process.pyx:365:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\handles/process.pyx:366:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\handles/process.pyx:367:0: The 'DEF' statement is
deprecated and will be removed in a future Cython version. Consider using
global variables, constants, and in-place literals instead. See
cython/cython#4310 https://github.com/cython/cython/issues/4310
warning: winloop\handles/udp.pyx:351:8: The 'IF' statement is deprecated
and will be removed in a future Cython version. Consider using runtime
conditions or C macros instead.  This may cause incorrect vtables to be
generated.
warning: winloop\handles/basetransport.pxd:54:25: Previous declaration is
here
warning: winloop\handles/stream.pyx:284:9: Compatible but non-identical C
method '_is_reading' not redeclared in definition part of extension type
'UVStream'. This may cause incorrect vtables to be generated.
warning: winloop\handles/basetransport.pxd:54:25: Previous declaration is
here
warning: winloop\handles/udp.pyx:135:9: Compatible but non-identical C
method '_is_reading' not redeclared in definition part of extension type
'UDPTransport'. This may cause incorrect vtables to be generated.
warning: winloop\handles/basetransport.pxd:54:25: Previous declaration is
here
Error compiling Cython file:
...
=== overloads ===
cdef _new_socket(self)
cdef size_t _get_write_buffer_size(self) noexcept
cdef bint _is_reading(self)
^

winloop\handles/basetransport.pxd:54:25: C method '_is_reading' is
declared but not defined
Traceback (most recent call last):
File "C:\petals\winloop\setup.py", line 91, in
do_installation()
File "C:\petals\winloop\setup.py", line 57, in do_installation
ext_modules=cythonize(ext),
File "c:\conda\envs\py10\lib\site-packages\Cython\Build\Dependencies.py",
line 1134, in cythonize
cythonize_one(*args)
File "c:\conda\envs\py10\lib\site-packages\Cython\Build\Dependencies.py",
line 1301, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: winloop\loop.pyx
—

It seems that Cython has changed the way they did things since 3.0 is now
out. I will look into fixing this all when I have the time to and I’ll let
you know my findings. In the meantime it would be a good idea to create a
workflow that can check for compiler errors. Thank you for finding this for
me.

Reply to this email directly, view it on GitHub
https://github.com/Vizonex/Winloop/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3K7GGXJEZXT3DXSXB2BXYLXSAZIXANCNFSM6AAAAAA2XUTOCI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@poedator I may have made a temporary fix and that's to drop the _is_reading() noexcept Keyword on it which may have been the reason for your problem. Let me update the library with these changes I'm looking for some more fixes to uploading all the Wheels to pypi first then I'll actually update this library afterwards but until then those DEF Keywords look to be like a new threat/problem in the future so I'll contact the uvloop devs about this change as well to see what both of our libraries can implement to fix the compiler warnings.

@poedator
https://github.com/Vizonex/Winloop/commit/273dd899b5ec8d5355ed3cf142739a760d1176d7
See if cloning and compiling the main branch fixes your issue, I'll handle dropping the DEF Keywords soon as I can, seems to be deprecated by the main Cython Devs due to changes from Pyrex https://github.com/cython/cython/issues/4310

@poedator I found the real problem and I fixed it now let me change a few things. turns out we need to keep some of the noexcept keywords but I'll just have to upload my files to github so I don't have to make a bunch of mini pull-requests...

@poedator see: https://github.com/Vizonex/Winloop/commit/a1394ead53ef0117fbd8a20d33f5ddcf9bbd4dae

@poedator I'll mark this as Completed when you can tell me that your end compiled the library correctly.

Hi, @Vizonex!
Thank you for your quick response and fixes.
I pulled https://github.com/Vizonex/Winloop/commit/a1394ead53ef0117fbd8a20d33f5ddcf9bbd4dae and was able to compile and install it. Had to update to Visual Studio-2022, for 2019 was missing 'io.h'.
Check out the compilation output and test results here:
https://gist.github.com/poedator/14a1c2c0fd0e784b5a3227a7f63e7a54

there were warnings from compiler - you may want to act on them.
I ran the test code from this repo front page test result was Ran 2 tests in 2.173s. Not sure it this was good or not - ehere to check the Asyncio Event Loop Policy?

On Tue, Aug 1, 2023 at 12:06 PM Poedator @.***> wrote:

Hi, @Vizonex https://github.com/Vizonex!
Thank you for your quick response and fixes.
I pulled a1394ea
https://github.com/Vizonex/Winloop/commit/a1394ead53ef0117fbd8a20d33f5ddcf9bbd4dae
and was able to compile and install it. Had to update to Visual
Studio-2022, for 2019 was missing 'io.h'.
Check out the compilation output and test results here:
https://gist.github.com/poedator/14a1c2c0fd0e784b5a3227a7f63e7a54

there were warnings from compiler - you may want to act on them.
I ran the test code from this repo front page test result was Ran 2
tests in 2.173s. Not sure it this was good or not - ehere to check the
Asyncio Event Loop Policy?

—
Reply to this email directly, view it on GitHub
https://github.com/Vizonex/Winloop/issues/4#issuecomment-1660753275, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3K7GGTXKEB4GWSRC2AEIG3XTEZPPANCNFSM6AAAAAA2XUTOCI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you I’ll be sure to add the missing io.h I compiled it myself
without it on python version 3.9.15 but I’ll be sure to add it in for other
builds as well, I’ll close this issue shortly.

I noticed that after installation frou sources the winloop module does not appear in pip list output. It also makes my VS Code complain. Yet it is importable in python. Not a blocker, but you may want to take a look.


Fix SITL segfault in camera trigger

In SITL the only supported camera interface mode is via mavlink. If the interface was not set to mavlink (and by default it was not set to that) then no camera interface was created and a null pointer was invoked.
This PR does the following:

For posix build set the default trigger mode to mavlink.
Exit cleanly if a camera interface was not created.

@bkueng I addressed your comment, please have a look.


[libspatialite] build failure

Operating system
Linux
Compiler
GCC 13.1
Steps to reproduce the behavior
`./vcpkg install libspatialite:x64-linux-dynamic`

Failure logs
root@79dfb50ce157:~/vcpkg# ./vcpkg install libspatialite:x64-linux-dynamic
Computing installation plan...
The following packages will be built and installed:
    libspatialite[core,freexl,geocallbacks]:x64-linux-dynamic -> 5.0.1#12
Detecting compiler hash for triplet x64-linux-dynamic...
Restored 0 package(s) from /vcpkg_binary_cache in 4.83 us. Use --debug to see more details.
Restored 0 package(s) from /root/.cache/vcpkg/archives in 3.1 us. Use --debug to see more details.
Installing 1/1 libspatialite:x64-linux-dynamic...
Building libspatialite[core,freexl,geocallbacks]:x64-linux-dynamic...
warning: -- Using community triplet x64-linux-dynamic. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: /root/vcpkg/triplets/community/x64-linux-dynamic.cmake
-- Using cached libspatialite-5.0.1.tar.gz.
-- Extracting source /root/vcpkg/downloads/libspatialite-5.0.1.tar.gz
-- Applying patch fix-makefiles.patch
-- Applying patch fix-linux-configure.patch
-- Applying patch gaiaconfig-msvc.patch
-- Applying patch fix-mingw.patch
-- Using source at /root/vcpkg/buildtrees/libspatialite/src/atialite-5-bc39e08d26.clean
-- Getting CMake variables for x64-linux-dynamic-dbg
-- Getting CMake variables for x64-linux-dynamic-rel
-- Generating configure for x64-linux-dynamic
-- Finished generating configure for x64-linux-dynamic
-- Configuring x64-linux-dynamic-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: /usr/bin/bash -c "V=1 ./../src/atialite-5-bc39e08d26.clean/configure  \"--enable-freexl\" \"--disable-gcp\" \"--enable-geocallbacks\" \"--disable-rttopo\" \"--disable-examples\" \"--disable-minizip\" \"--disable-silent-rules\" \"--verbose\" \"--enable-shared\" \"--disable-static\" \"LIBS=-L/root/vcpkg/installed/x64-linux-dynamic/debug/lib/pkgconfig/../../lib -lgeos_c -lxml2 -lproj -lsqlite3 -lz -lfreexl -lm $LIBS\" \"--prefix=/root/vcpkg/installed/x64-linux-dynamic/debug\" \"--bindir=\\${prefix}/../tools/libspatialite/debug/bin\" \"--sbindir=\\${prefix}/../tools/libspatialite/debug/sbin\" \"--libdir=\\${prefix}/lib\" \"--includedir=\\${prefix}/../include\" \"--datarootdir=\\${prefix}/share/libspatialite\""
    Working Directory: /root/vcpkg/buildtrees/libspatialite/x64-linux-dynamic-dbg
    Error code: 77
    See logs for more information:
      /root/vcpkg/buildtrees/libspatialite/config-x64-linux-dynamic-dbg-config.log
      /root/vcpkg/buildtrees/libspatialite/config-x64-linux-dynamic-dbg-out.log
      /root/vcpkg/buildtrees/libspatialite/config-x64-linux-dynamic-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:833 (vcpkg_execute_required_process)
  ports/libspatialite/portfile.cmake:180 (vcpkg_configure_make)
  scripts/ports.cmake:147 (include)

error: building libspatialite:x64-linux-dynamic failed with: BUILD_FAILED
Elapsed time to handle libspatialite:x64-linux-dynamic: 7.4 s
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+libspatialite
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?title=[libspatialite]+Build+error&body=Copy+issue+body+from+%2Froot%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

config-x64-linux-dynamic-dbg-config.log
config-x64-linux-dynamic-dbg-err.log
config-x64-linux-dynamic-dbg-out.log
Additional context
This was run in a gcc:13.1-based docker container. The port compiles successfully when I set CC and CXX to point to gcc-12, but with GCC 13 it fails at the configuration stage due to an inability to find libgeos_c.so.1 (which does exist). Defining LD_LIBRARY_PATH to include to the vcpkg lib and debug/lib directories fixes the error.

This issue hasn’t been updated in 3 month, if it is still an issue, please reopen this issue.


Eventing TLS: prioritize destination CA certs over resolved addressable CA certs

This condition is prioritizing addr over dest
https://github.com/knative/pkg/blob/559de7ee8c6788ec4561b170181556f6fa0a36af/resolver/addressable_resolver.go#L257-L259
we should set addr.CACerts to whatever dest.CACerts has set if dest.CACerts is set/non empty regardless of the value of addr.CACerts
Additional Info

The fix should be backported to release-1.11 branch

/good-first-issue

/assign


Auto updates on a regular basis

As a User of this dataset, I want to have it auto-updated on regular basis, e.g. weekly, so that I can use it in my projects that will be always up-to-date.

This ticket has been resolved through: https://github.com/datopian/carbondoomsday/issues/2.

I have a fork that uses GitHub Actions to automatically run the script on the 1st of each month.
The fork also includes other changes such as bypassing make
Should I open a PR or keep the feature downstream?

@jtpotato that would be amazing and very welcome! We are happy to lose make!


SourceLocation as a relative path

▶ odo create java --binary target/spring-boot-rest-http-1.5.17-5-SNAPSHOT.jar
 ✓  Checking component
 ✓  Checking component version
Please use `odo push` command to create the component with source deployed

▶ cat .odo/config.yaml
kind: LocalConfig
apiversion: odo.openshift.io/v1alpha1
ComponentSettings:
  Type: java
  SourceLocation: /Users/tkral/tmp/odo-examples/spring-boot-http-booster/target/spring-boot-rest-http-1.5.17-5-SNAPSHOT.jar
  SourceType: binary
  Application: spring-boot-hekh
  Project: default
  Name: java-olhp

▶ odo create java
 ✓  Checking component
 ✓  Checking component version
Please use `odo push` command to create the component with source deployed

▶ cat .odo/config.yaml
kind: LocalConfig
apiversion: odo.openshift.io/v1alpha1
ComponentSettings:
  Type: java
  SourceLocation: /Users/tkral/tmp/odo-examples/spring-boot-http-booster
  SourceType: local
  Application: spring-boot-fqkv
  Project: default
  Name: java-yaiq

SourceLocation in a config needs to be saved as a relative path to the context directory.
In the above example SourceLocation  should be target/spring-boot-rest-http-1.5.17-5-SNAPSHOT.jar for the binary component and  ./ or .  for the local component.
We can't put the whole path there because it prenets sharing the config

/priority hight
/state ready

@girishramnani this needs to addressed before beta release

Do you want me to take this?

Do you want me to take this?

that would be great

/assign girishramnani

@girishramnani this might be related to something that @cdrage  is doing in his PR https://github.com/openshift/odo/pull/1446

Yeah, seems so
On Wed, 3 Apr 2019, 20:32 Tomas Kral<EMAIL_ADDRESS>wrote:

@girishramnani https://github.com/girishramnani this might be related
to something that @cdrage https://github.com/cdrage is doing in his PR
#1446 https://github.com/openshift/odo/pull/1446
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/odo/issues/1552#issuecomment-479528277, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGP5tINypWafp-sgw5q7xX8wQiu1ZLKSks5vdMKHgaJpZM4cYV_8
.

any progress here?

I commented here: https://github.com/openshift/odo/issues/1429 as both of these issues are relevant.
I am currently investigating this (got distracted by doc changes I've been pinged on), at the moment, it looks like I'll have to add another FromSlash somewhere in the code.

For issue #1429: I am currently investigating this (got distracted by doc changes I've been pinged on), at the moment, it looks like I'll have to add another FromSlash somewhere in the code.

I think  that it should be ToSlash not From ;-)

Been distracted by issue #1429 as I'm trying to fix the Windows ignore bug.
Question, with regards to storing the actual filepath, should we be storing it as per whatever OS is being used, or ALWAYS forward slash?

Been distracted by issue #1429 as I'm trying to fix the Windows ignore bug.

When you fix this issue, the #1429 will get resolved.

Question, with regards to storing the actual filepath, should we be storing it as per whatever OS is being used, or ALWAYS forward slash?

always forward slash!
It needs to be stored in forward slash format. Before the path is stored, it needs to be properly converted to relative path, and piped through ToSlash. This will ensure that it is always stored in a unified way (with forwarding slashes). When it is read it will be piped through FromSlash to ensure that it is converted to current OS format


Retarget to .NET Standard.

[x] Fusee.Base.Common
[x] Fusee.Base.Core
[ ] Fusee.Base.Imp.Android
[x] Fusee.Base.Imp.Desktop
[ ] Fusee.Base.Imp.Web
[x] Fusee.Engine.Common
[x] Fusee.Engine.Core
[ ] Fusee.Engine.Imp.Font.Desktop
[ ] Fusee.Engine.Imp.Graphics.Android
[x] Fusee.Engine.Imp.Graphics.Desktop
[ ] Fusee.Engine.Imp.Graphics.Web
[ ] Fusee.Engine.Imp.Input.Desktop
[ ] Fusee.Engine.Imp.Input.Web
[ ] Fusee.Engine.Imp.Network.Desktop
[ ] Fusee.Engine.Imp.Network.Web
[ ] Fusee.Engine.Imp.Physics.Desktop
[ ] Fusee.Engine.Imp.Sound.Desktop
[ ] Fusee.Engine.Imp.Sound.Web
[ ] Fusee.Engine.Imp.Video.Desktop
[ ] Fusee.Engine.Imp.Video.Web
[ ] Fusee.Engine.Player.Android
[ ] Fusee.Engine.Player.Core
[ ] Fusee.Engine.Player.Desktop
[ ] Fusee.Engine.Player.Web
[x] Fusee.Jometri
[x] Fusee.Math.Core
[x] Fusee.Serialization
[x] Fusee.Xene
[x] Fusee.Xirkit
[ ] fuseeCmdLine

.NET Core 2.1 is released as a LTS version. Support for .NET Core 2.0 ends October 1, 2018.

Develop is netstandard2.0 except for the Xamarin projects. Xamarin does not yet support the new project structure.


Added link to 1.0 docs

Took me 5 mins to figure this out..

Hmm, can't get the profile up and running with my silex 1.0 project. Are v1 projects still supported?

Thank you @tiemevanveen.

No problem. And my question, I suppose v1 are still supported right?

Hmm, can't get the profile up and running with my silex 1.0 project. Are v1 projects still supported?


Too many build targets

Maybe should make one(or few) main target platform ?
Too many precompiler directives = too hard for implement new feature and improvements and also code readability in future.
Or separate old target compatibility version in own repository ?
What do you think about it ?
P.S. For example async/await, spans, read-only struct, and many other feature, too hard implement now.

There isnt too many precompiler directives. Only for netcore and unity specific bugs. Also async/await doesnt make sense in this library because all operations already async

Ok it's really not need for main library methods for now.


VPNKIT.EXE keeps connections open

Problematic version: Docker Community Edition <IP_ADDRESS>-win78 2018-11-19 and newer, including latest edge versions.
Latest non-problematic version: Docker Community Edition 18.06.1-ce-win73 2018-08-29
Tested on Windows 10 Pro, latest stable build 18362 and Windows Server latest stable build
Problem description: our software uses netcore container and downloads data using http from enduser device. In cycle every 5 seconds. So every 5 seconds there is an open connection between software and end-user device. This device has 8 free ports on port 80. After a time all 8 are exhausted.
So i check open connections, using netstat, and 'Netstat -ano' shows 8 ESTABLISHED connections between software and end-user device. After a bit research, all are linked to vpnkit.exe.
When I start everything from scratch there are 0 ESTABLISHED connections (of course sometimes I can catch one, but that opening and closing connections is really fast, so it always shows nothing, after start). But after some time 1 connection is still open-ESTABLISHED. After a time, another one, and this keeps going on and on, untill there are 8 ESTABLISHED connections, because that is maximum, that that end-user device allows.
Docker for Linux has no problems.
When running this software as a standard windows service beside docker, everything runs flawlessly.
So I still use that latest 18.06 version and testing all latest edge versions, with no luck for now.

Closing as wildly outdated but more importantly this is the wrong repository to report this issue on.
Please open an issue in https://github.com/moby/moby


fixes #93 stop endless loop when node parent is null

added checking if node is null in the while condition

I'm always wary of merging this type of fixes. Adding safe checks around the code is just a patch, where the real problem is hiding somewhere else. The engine should never reach the HTML tag while scanning parents.
I'll keep this pull open as a reminder and explore the real issue over the weekend.

I completely agree with you about this being a patch more than a fix for the real bug, but not merging it means you leave the library with a bug that cause endless loop.
Don't you think it's a priority to release a fix for this as a minor update and keep the bigger unknown bug as a todo for when you or anyone else have time?


Added youtube videos to front page

Updated patch [1] from Tuomas with a couple of changes for discussion:
Co-Authored-By: Tuomas Kuosmanen<EMAIL_ADDRESS>[1] https://github.com/submariner-io/submariner-website/pull/150

@tigert I'm merging your patch with some additions on top ^


[FEATURE]: CSM reporting metrics for PV/PVC for PowerStore

As a K8s admin, I want to view the pvc / pv metrics reporting back to kubelet via the CSI driver.
In addition, I want to verify that the volume is still provisioned properly on the array (exists and is exported to the node) and that it is still accessible and correctly mounted at the indicated volume path.

All features updates completed hence closing this Issue.


Temporal Random Walks

Reviewer Checklist

[ ] Code has no errors
[ ] Unit tests are appropriate
[ ] Demo notebook runs
[ ] Code is well commented

@kjun9 Temporal Random Walks is ready for review. Thanks.

wow! Thanks @kjun9 for the prompt review! The suggestions for the code fixes seem right. I will make the changes and let you know. I guess i'll get to these fixes next sprint(year?!).

The code seems to match the paper more closely now, but I haven't reviewed the notebook at all. Does the notebook give better results?

I also haven't run the notebook at all, since it requires using a 20gb dataset in its current form. I'd prefer to just remove it for now and work on a fresh demo with another dataset?

I also haven't run the notebook at all, since it requires using a 20gb dataset in its current form. I'd prefer to just remove it for now and work on a fresh demo with another dataset?

Sounds reasonable, although just for convenience of retrieval (i.e. minimise how much git magic we have to do to dig it out), maybe you could open a separate draft PR that contains only that notebook?

I've opened https://github.com/stellargraph/stellargraph/pull/773 to keep track of the old notebook

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@099d764). Click here to learn what that means.
The diff coverage is 92.68%.

@@            Coverage Diff             @@
##             develop     #552   +/-   ##
==========================================
  Coverage           ?   83.05%
==========================================
  Files              ?       43
  Lines              ?     5122
  Branches           ?        0
==========================================
  Hits               ?     4254
  Misses             ?      868
  Partials           ?        0

Impacted Files
Coverage Δ

stellargraph/core/graph.py
91.3% <100%> (ø)

stellargraph/core/graph_networkx.py
88.14% <100%> (ø)

stellargraph/data/explorer.py
95.01% <81.25%> (ø)

Continue to review full report at Codecov.

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

This was closed accidentally, see: https://github.com/stellargraph/stellargraph/issues/786.

New PR: https://github.com/stellargraph/stellargraph/pull/787


FederatedStore-FederatedAccess: Why are Read Write Predicates Strings and not AccessPredicate objects?

FederatedStore-FederatedAccess: Why are Read Write Predicates Strings and not AccessPredicate objects?
This requires deserialisation on every usage of FederatedAccess on graphs, This seems wasteful.

The Read/Write Access predicates are stored as strings because the parent object be serialisable (so that they may be stored in a Disk Cache). It's the same story for Named Operations / Named Views

I'm not understanding, I might be missing something fundamental here is the JSON serialiser not being used in this example?

To answer your first question, no. For the JCS cache, they currently they use Java serialisation. Maybe that's something we could (and probably should) change.

And for the FederatedAccessDetail question, maybe but the FederatedAccess object is already fulfilling that role

As I understand it. We are in agreement that FederatedStoreCache can be modified to handle the manipulation of unserialisable AccessPredicate into cached strings and then retrieved back into AccessPredicate objects.
This will clean up the code and be "logically" a more performant FederatedAccess object (real world difference will likely be minimal).
It is likely that NamedOperations and NamedViews should follow the same changes. This is likely should be achieved by a default caching mechanism (similar to FederatedStoreCache) which serialises as default using JSONserialiser or uk.gov.gchq.gaffer.serialisation.implementation.*. A lot of effort has been made across gaffer development to use these serialisers, only to find issues with the JavaSerialiser via JCSCache.

After discussion, this item won't be handled as part of the alpha-3 fedstore merging, but will be reviewed as part of alpha-5 and a decision taken then as to whether to handle it there or after the later NamedOperation changes

We may not in the end include any NamedOperation changes in 2.0. The question here is whether this item is worth doing and, if it is, whether it has to be included in the 2.0 release or can be be left to the post-2.0 backlog

Due to test FederatedStoreCacheBackwardCompatibilityTest requiring backwards compatibility of the Cache I can't do smarter changes with the cache as required.

Have since decided the only break and migration required is the cache gets deleted and Graphs are re-added.
the underlying data is of graphs will still persist.

repost: Requiring Further Discussion.
It is likely that NamedOperations and NamedViews should follow the same changes. This likely should be achieved by a default caching mechanism (similar to FederatedStoreCache) which serialises as default using JSONserialiser or uk.gov.gchq.gaffer.serialisation.implementation.*. A lot of effort has been made across gaffer development to use these serialisers, only to find issues with the JavaSerialiser via JCSCache.

Closed by https://github.com/gchq/Gaffer/pull/2862


Support for Xamarin Forms css syntax

Description
With the introduction of Xamarin Forms 3.0 css is now supported. While most of the css is generally valid css, there is a selector that is not typically supported for web applications. Having the ability to generate the css from Sass would be hugely beneficial but currently the Sass compiler generates an exception. I need a way that I can support compiling sass that uses the derived types syntax:

Selector
Example
Description

^base
^contentpage
Selects all elements with ContentPage as base class, including ContentPage itself. Case irrelevant. This selector isn't present in the CSS specification, and only applies to XF.

Sample
As an example I might want to make all buttons have a transparent background whether I'm using the base Button class or some custom Button class.
^button {
  background-color: transparent;
}

This might require a change to the Sass language. You would need to request that to the sass/sass repo.
I don't think it would be accepted though since it wouldn't match the CSS selector allowed characters https://stackoverflow.com/a/4132824/455535

@nschonni I thought each language is handled separately now, and I'm not trying to be so presumptuous as to say that all of Sass should be required to change. Since this is for Xamarin Forms developers, they're already working in .NET so making the change for the .NET library makes the most sense here. Ultimately all I need is some way to tell the Sass compiler to accept the special syntax with a preceding ^

This is a wrapper for libsass, and libsass won't add features that aren't in the Sass language. You could see if you can figure out a way to monkey patch it here though


How to stream any url?

Hello,
could you explain to me how to stream any url?
Please?
Even if it's not with this library, and it's natively in flutter.
For example, stream this
https://api.betterapi.net/youchat?inputs=hola&stream=True&key=site
Thanks!

Hi, if I am getting this right, you want to stream responses of a specific API that supports Server-Sent Events (SSE), and it is not related to the library, right?
if yes then I will love to help you with this and write a short tutorial about it, however, this is still not the right place for it, so it would be better if you reach me by mail at<EMAIL_ADDRESS>or by asking on Stackverflow then tagging me on it (my profile).
I will close this curerntly.

Yes,
Thanks
I will contact you :)

Question done :)
https://stackoverflow.com/questions/76502116/how-to-stream-responses-of-a-specific-api-that-supports-server-sent-events-sse
thanks
El dom, 18 jun 2023 a las 19:00, Anas FIKHI @.***>)
escribió:

Hi, if I am getting this right, you want to stream responses of a specific
API that supports Server-Sent Events (SSE), and it is not related to the
library, right?
if yes then I will love to help you with this and write a short tutorial
about it, however, this is still not the right place for it, so it would be
better if you reach me by mail at @.*** or by asking on
Stackverflow then tagging me on it (my profile
https://stackoverflow.com/users/18670641/gwhyyy).
I will close this curerntly.
—
Reply to this email directly, view it on GitHub
https://github.com/anasfik/openai/issues/60#issuecomment-1596207738, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A2FNLKITPAUXL5KGV4SYE4TXL4X33ANCNFSM6AAAAAAY4R7Q5A
.
You are receiving this because you authored the thread.Message ID:
@.***>


[Bug]: Mime-type not working on upload

File Name
generativeai/files.py
What happened?
Mime-type assignment is not working properly
Gemini stopped working due to the file upload in the python sdk being broken.
this is how i use the file upload
def upload_to_gemini(path, mime_type=None):
    """Uploads the given file to Gemini."""
    file = genai.upload_file(path, mime_type=mime_type)
    print(f"[UPLOAD] File uploaded as: {file.uri}")
    return file

when i upload a file like so
audio_file = upload_to_gemini(temp_path, "audio/wav")
it uploads correctly but the mime type is not set
AUDIO FILE: genai.File({
'name': 'files/30txz5yr4lnt',
'display_name': 'tmp8nqzekug.wav',
'mime_type': '',
'sha256_hash': '',
'size_bytes': '0',
'state': 'ACTIVE',
'create_time': '2024-11-11T23:28:05.021763Z',
'expiration_time': '2024-11-13T23:28:05.001887117Z',
'update_time': '2024-11-11T23:28:05.021763Z'})
as you can see the mime type is not set
resulting in this issue:
400 Unable to submit request because it has an empty mimeType parameter in fileData. Add a value to the parameter and try again. Learn more: https://cloud.google.com/vertex-ai/generative-ai/docs/model-reference/gemini
This has happened on my local machine as well as google cloud run functions.
Relevant log output
TRACEBACK: Traceback (most recent call last):
  File "/Users/User/OWL/main.py", line 668, in analyze_single_call
    response = chat.send_message([
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/generativeai/generative_models.py", line 578, in send_message
    response = self.model.generate_content(
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/generativeai/generative_models.py", line 331, in generate_content
    response = self._client.generate_content(
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/ai/generativelanguage_v1beta/services/generative_service/client.py", line 830, in generate_content
    response = rpc(
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/api_core/gapic_v1/method.py", line 131, in __call__
    return wrapped_func(*args, **kwargs)
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/api_core/retry/retry_unary.py", line 293, in retry_wrapped_func
    return retry_target(
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/api_core/retry/retry_unary.py", line 153, in retry_target
    _retry_error_helper(
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/api_core/retry/retry_base.py", line 212, in _retry_error_helper
    raise final_exc from source_exc
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/api_core/retry/retry_unary.py", line 144, in retry_target
    result = target()
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/api_core/timeout.py", line 120, in func_with_timeout
    return func(*args, **kwargs)
  File "/Users/User/OWL/venv/lib/python3.10/site-packages/google/api_core/grpc_helpers.py", line 78, in error_remapped_callable
    raise exceptions.from_grpc_error(exc) from exc
google.api_core.exceptions.InvalidArgument: 400 Unable to submit request because it has an empty mimeType parameter in fileData. Add a value to the parameter and try again. Learn more: https://cloud.google.com/vertex-ai/generative-ai/docs/model-reference/gemini

Code of Conduct

[X] I agree to follow this project's Code of Conduct

related to https://github.com/google-gemini/generative-ai-python/issues/628

Doesn't seem that this issue is related to this repository. It's related to the Gemini API, not Gemini API in Vertex AI. Refer to #628 for the fix.


Weather website using HTML, CSS and Javascript

Describe the project
The weather website is a simple web application that allows users to check the current weather conditions of a particular location.
Issue Type:

[ ] Bug Report
[ ] Feature Request
[ ] Documentation
[X] New Project

Additional context
I want to work on this. Please assign this issue to me. @TusharKesarwani
Screenshots

I have done this project before, I want to work in this project. Please assign this project to me.

Please assign me this issue


Add vxlan role and ip params to hypervisor inventory

If vxlan is selected as a network type in the network config setup then a Tunnel Interface IP field must be populated for hypervisors.

Addressed by pull request #105


Search view: I ofter hit the dismiss button by accident

I often click on the search result view's dismiss button by accident. That forces me to search again.

it's hard to see as it is so close to the text
and only shows up on hover
it is at a different location every line
it has the same color as the text

Other views have it at the end. I suggest to put it there.

Another issue created here, https://github.com/microsoft/vscode/issues/103398. Looks like there is a setting to align the buttons right, but not always show.

Yeah you want "search.actionsPosition": "right". Actually this is the second time this has come up in 24 hours hours. I'll try changing the default in October.


Update API Endpoints dealing with Game model (List and Detail Views)

Pull Request https://github.com/uchicago-cs/chigame/pull/153 changed the Game model to be more fleshed out, taking inspiration from BoardGameGeeks. Due to the changes in the model, we changed our API Endpoint Views dealing with the Game model, so that the model attributes are returned correctly. There are additions to the model, as well as changes to the existing attributes of the Game model.
Specifically, the GameSerializer now has the line fields = "__all__", which implies that we want to return all the fields in the model, when serializing and deserializing a Game. This is also dynamic, as we don't have to add fields/rename fields manually, when the Game class changes, as the serializer will just return all the fields in the model.

This PR has been closed, but its content has been duplicated in PR #289


chore(*): change controller name suffix from 'Ctrl' to 'Controller'

Related discussion: https://github.com/angular/angularjs.org/pull/163#discussion_r27342489

looks good to me

@caitp, should I merge this then ?

@gkalpak yes

Hm...it seems like I don't have access to push to angular/angularjs.org :confused:


SLES_TEST_SUDOERS_VERIFICATION_SUCCESS is included in SLES15?

The same test kept failing in SLES 15. Is it available in SLES 15 or not? If SLES 15 no longer has it, we should remove this string inclusion in the ps1 file.

}
elseif ($global:detectedDistro -imatch "SLES") {
$matchstrings = @("_TEST_SUDOERS_VERIFICATION_SUCCESS","_TEST_GRUB_VERIFICATION_SUCCESS", "_TEST_REPOSITORIES_AVAILABLE")
# to avoid extra blank space

Is it the same with #338?

Is it the same with #338?

I am checking with PM

During the information exchange, all of SLES images do not have this parameter. I think we should omit in our test script.

Added a bug to SUSE. We do not know if this is a planned change or not. https://bugzilla.suse.com/show_bug.cgi?id=1150407

Remove this check for sles in PR #665


[0.15.1] - sheet_to_json no longer correctly converts dates to JS dates

We upgraded to 0.15.1 to get the minified version of xlsx into our build, but immediately tests started failing. When parsing an excel file to JSON, XLSX used to return the date string "01/01/18", but now returns the corresponding Excel date number 43101.
Eventually we determined that XLSX.utils.sheet_to_json was parsing dates as their excel date value.  01/01/18 is now parsed as 43101, which, when converted to a date, it is assumed as unix time of 43101, so 43,101 seconds after Midnight, January 1, 1970.
We have had to revert back to 0.13.5 to get our thousands of tests passing again.

You can use new Date(1000*60*60*24*(43101-25569)). I don't know where 25569 from. but this works

@spradlin-dev yes the raw default flipped in 0.15.0
@g6ling JS 0 date is the unix epoch (January 1 1970) but Excel's 0 date is January 1 1900 (hence the need to subtract the 70 years).  The other confounding factor is 1900 leap year bug which affects February 29 1900 (Excel thinks it exists but JS does not)


adding code to take care of multiple entity names with special charac…

…ters

Thanks ! @azurebrd
Sounds good to wait for @valearna to check out the code.

Thanks @valearna


[DO NOT MERGE] Make announcements section live

Trello: https://trello.com/c/ekjW492n
What's changed and why?
We're ready to make the announcements section, so we need to remove the "Unreleased feature" feature flag.
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

Hi @leenagupte,
Only thing I found are that unreleased feature permissions are still being used in this test but once that is gone then should be all good to approve.

Thank you! Fixing now.


How to automatically connect and pop up the signature box when switching accounts

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
0.12.8
wagmi Version
0.12.10
Current Behavior
No response
Expected Behavior
No response
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
How to automatically connect and pop up the signature box when switching accounts

`

{hasMounted && }
<Component {...pageProps} />

    </WagmiConfig>`

solved


⚠ 한경주요지수-코스피200 has degraded performance

In 1e5f348, 한경주요지수-코스피200 (https://markets.hankyung.com/indices/kospi200) experienced degraded performance:

HTTP code: 200
Response time: 5654 ms

Resolved: 신규상장 performance has improved in 30739cd.


Overhead per key

Hi! We currently anticipate a 5% storage overhead per key in the KV store. We were planning to confirm this estimate by running some tests to get an empirical approximation but thought to ask first in case an estimate has already been measured. This will help us make decisions related to sharding and instance sizing. Thank you!

Hi! what's the stats of your key/values? I assume we're looking at the in-RAM storage overhead (rather than the persistent blob storage). how big are the keys&values at 50 percentile, 90 percentile, and total number of keys, etc?
For the in-RAM storage there is some fixed overhead to store metadata so the percentage changes depending on the k/v sizes. Right now it's a 64-bit integer for the timestamp (https://github.com/privacysandbox/fledge-key-value-service/blob/release-0.13/components/data_server/cache/key_value_cache.h#L93) and some internal overhead required by the data structures like unique_ptr, the hash map and probably overhead incurred by TEE. This may change as we may optimize the storage implementation in the future.
However, with that said, so far our finding suggests that TEE implementation by the cloud could be more impactful to the sharding and instance sizing decision than per-key implementation overhead. For example on AWS there is certain limitation on what can be used from a machine for TEE. (https://github.com/aws/aws-nitro-enclaves-cli/issues/263)
We don't have an analysis ready to share but there is work in progress to test our sharding capabilities. And with the big caveat above I recommend that you test out with the empirical approach. If you share the data stats with us we might also be able to take a look along with our own testing.

Apologies for the lack of response, was conferring with my team about this. We will share this info in a private shared doc with our contact


Interactive cli

If everything goes well, this PR should close #23. 🤞
The output still might have an issue (similar to #26), but it's orthogonal (from my perspective) to this PR, and we can fix it separately.

It looks like I fixed everything. 🙂
Here is how it works now (with the Color.js test suite):
https://github.com/LeaVerou/htest/assets/9166277/65e22a78-2369-4e9a-b943-8c74e894f5bd

Amazing. You should put this video on the homepage!

Will do in a separate PR. :)


Only create changed buffer if it already exists

Objective

DynamicUniformBuffer tries to create a buffer as soon as the changed flag is set to true. This doesn't work correctly when the buffer wasn't already created. This currently creates a crash because it's trying to create a buffer of size 0 if the flag is set but there's no buffer yet.

Solution

Don't create a changed buffer until there's data that needs to be written to a buffer.

Testing

run cargo run --example scene_viewer and see that it doesn't crash anymore

Is the size check missing anywhere else? This is a pattern we’ve used across many of these GPU buffer wrappers.

Is the size check missing anywhere else? This is a pattern we’ve used across many of these GPU buffer wrappers.

It's missing for at least DynamicStorageBuffer, and possibly RawBufferVec from a quick scan.

There is an associated issue for this: https://github.com/bevyengine/bevy/issues/13235

Yeah, I can add it everywhere else. I was focused on the DynamicUniformBuffer because it's the one currently causing crashes on main in some examples.


Add more reviews to initial data set

To better demonstrate editorial communities, we would like to have more reviews associated to various preprints.
There are some constraints on which preprints and reviews we can use (Biorxiv preprints and Zenodo DOI-based reviews).
/cc @hdrury1

a list of registered DOIs for eLife reviews. The DOIs in square brackets are the corresponding bioRxiv articles.

10.5281/zenodo.3820276 [10.1101/642017]
10.5281/zenodo.3820283 [10.1101/615682]
10.5281/zenodo.3820289 [10.1101/629618]
10.5281/zenodo.3820295 [10.1101/600445]
10.5281/zenodo.3820302 [10.1101/252593]
10.5281/zenodo.3820314 [10.1101/497495]
10.5281/zenodo.3821160 [10.1101/856153]
10.5281/zenodo.3821167 [10.1101/871517]
10.5281/zenodo.3821171 [10.1101/610014]
10.5281/zenodo.3821367 [10.1101/822718]

When @hdrury1 added these reviews, I shared that we were only fetching the Description field from the Zenodo DOIs, so everything ended up in there rather than just a summary. In theory, the additional content would live only in the attached file. There's an interesting discussion to be had here.
At the moment, we'll put in these DOIs and they will look as wonky as the current Zenodo reviews we were using.

The [10 eLife reviews(http://prc-staging.libero.pub/editorial-communities/b560187e-f2fb-4ff9-a861-a204f3fc0fb0) are available, but we have a placeholder for a different editorial community. Close and split that different editorial community into another ticket, whenever that data becomes available?


[fix] mobile sns_redirect_path

Coverage decreased (-9.3%) to 74.818% when pulling b5a151015385fdec104ce9eb6a78d6357df128cf on ShinjiTanimoto:mobile into 8ecb0ee3d6fade85488c98be27c8e4932648a316 on shirasagi:master.


NIOCore: add explicit type cast for Windows compatibility

Windows does not have a socklen_t type, instead using CInt for the
value.  This adds an explicit type cast to repair the build on Windows.

@swift-nio-bot test this please


Add custom "update" event or run "update" on init.

I load images via ajax and on success the plugin is inited. But events if images are above threshold, they are not loaded untill i scroll. I think, it would be a good idea to run update event on init.

You can  do $(window).trigger("scroll") or something similar in ajax callback.

i did it. but it does not work. it only works when i set $(window).trigger("scroll") in timeout. but it is not the best way, i think. anyway, $(window).trigger("scroll") looks like a hack.


ld-elf.so.1: /usr/local/lib/libtesseract.so.5: Undefined symbol "__kmpc_global_thread_num"

I need help finding the source of the following problem:
When I compile the gosseract sample ...
`package main
import (
"fmt"
"github.com/otiai10/gosseract/v2"
)
func main() {
client := gosseract.NewClient()
defer client.Close()
client.SetImage("path/to/image.png")
text, _ := client.Text()
fmt.Println(text)
// Hello, World!
}`
... on FreeBSD 12.3 with ...
tesseract 5.0.0  leptonica-1.76.0   libgif 5.2.1 : libjpeg 8d (libjpeg-turbo 2.1.2) : libpng 1.6.37+apng : libtiff 4.3.0 : zlib 1.2.11 : libwebp 1.2.1  Found OpenMP 201511  Found libarchive 3.5.2 zlib/1.2.11 liblzma/5.2.5 bz2lib/1.0.8 liblz4/1.9.3 libzstd/1.5.0  Found libcurl/7.80.0 OpenSSL/1.1.1l zlib/1.2.11 libssh2/1.10.0 nghttp2/1.46.0
... and start the programm i get the following error:
ld-elf.so.1: /usr/local/lib/libtesseract.so.5: Undefined symbol "__kmpc_global_thread_num"
Possibly somebody can point me in the right direction what to do to fix this?
I already opened an issue in gosseract but nobody answered. I'm not sure if this is something depending on the gosseract part or is it because the libtesseract has a problem?

Maybe a missing -openmp compiler or linker option? This is not a Tesseract issue.

Please use the Tesseract user forum for questions.

This is a tesseract issue. And it is still actual

The missing symbol __kmpc_global_thread_num is not part of the Tesseract code (that's why I said it is not a Tesseract issue). It might be related to OpenMP, so either try to build Tesseract without OpenMP support (I'd suggest that) or try to find the library which provides that symbol and add it to the linker command line.

Only for the record: When installing tesseract from freebsd repo it doesn't work. We have to manually recompile tesseract to get it working like it did all the time up to now from repo. Hmm ... interessing point. Thanks!


Explore tag-based-discovery alternatives

Tell us about your request
Users have given strong positive feedback on the tag selection mechanism for security groups and subnets, but we should  explore better default discovery values for securitygroups/subnets.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Right now, the kubernetes.io/cluster/$name tag is somewhat standardized across kubernetes controllers for aws, but the semantics are slightly different. For example, in EKS, the security groups with this tag are owned by the service itself, but the subnets are not. Additionally, the loadbalancer controller only allows a single security group with this tag, which karpenter doesn't enforce.
There might be some more elegant/effective way to do this. This issue is a reminder to keep thinking about it.
Are you currently working around this issue?
It's working fine at the mo.
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

https://github.com/aws/karpenter/issues/1017


Studdenly stopped working. No video

just worked for me a few days ago. I was testing it on my localhost. Always used https.Then today i restarted my pc and suddenly it stopped working.
this is what i see in chrome's console.
Error: Cannot access video stream (NotFoundError).
at new i (instascan.min.js:9)
at Function. (instascan.min.js:9)
at n (instascan.min.js:4)
at Generator._invoke (instascan.min.js:4)
at Generator.e.(anonymous function) [as throw] (https://rawgit.com/schmich/instascan-builds/master/instascan.min.js:4:23151)
at n (instascan.min.js:4)
at r (instascan.min.js:4)
at instascan.min.js:4
(anonymous) @ app.js:25
I tried signing my own ssl certificate, still doesn't work. i tried on firefox, same issue.
Also, when i open with Android Chrome app the front camera works, but as soon as a select the back facing camera the video stops working on both front and back facing cameras. What happened, how can i fix this?
Also i've noticed that the live demo stopped working as well.
As i thurther experiment i tried opening with my Android Chrome app the live Demo, so the video now works, but doesn't scan.
I tried my localhost with Android Chrome app, the camera works, but it doesn't scan as great as it did a few days ago. It doesn't always scan now.

Could you resolve with anything? cause i am having the same issue now. it was just working fine last year


DM-39291: Pin photutils to 1.7.

spectractor used a deprecated keyword in the photutils API that is now gone.  pin photutils until this can be fixed.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


New Atlantis The Well Local Map

I noticed the local map for the well wasn't working at all, since I update my mods daily I assumed it was something I had changed recently. I updated SCP yesterday and started a new game this morning, the map was not working as soon as I entered the well. After bisecting all of my mods I have narrowed it down to SCP, with the mod installed the local map will not show at all. When it's uninstalled it works perfectly

Game Version
1.11.36
Language
English (EN)
New Game
Yes
Reproduction Steps
Enter The Well in New Atlantis (SCP Installed), attempt to open local map opens planet view and hotkey to switch to local map does not work

Confirmed.
The cell header for The Well [000F4ED4] was modified to inherit gravity from the planet (Unknown 17 flag). Bethesda added new data to the cell headers for the local maps and although this data was forwarded in v0.1.4 of SFCP, it appears it doesn't work properly. We will need to remove [000F4ED4] from SFCP until the CK is released.
Fix: Remove [000F4ED4] from SFCP.


Show color blindness pallettes

I have at least two coworkers with forms of color blindness and when screen sharing, my color selection can be difficult for them. I put my RootLoops theme into this simulator and it is not great. If the effort is reasonable, adding a way to preview these simulations in RootLoops would be a helpful feature.

Love the idea! I've been thinking about adding more accessibility features right into the generator, including testing for color blindness and low contrast.
I'd love to make it easy for people who generate a color palette to do the right thing and offer some guidance. When there's low contrast, the best action is probably to ask the user to adjust the sugar ingredient and maybe articifial colors until the contrast improves.
When it comes to several forms of color blindness, the best action is probably going to be a bit more involved. We could offer the user to pick a different set of hues according to certain kinds of color blindness. Right now, we simply pick 6 hues by splitting the color wheel into 6 equidistant angles and call it a day. Tweaking that for different kinds of color perception issues could be what it takes to generate schemes with better accessibility.
Sorry, wall of text - I'm mostly jotting down thoughts for my future self. Again, love the idea, and it's absolutely something I'm going to research :)


Added Alchemy and Infura v3 nodes

Added two more nodes in order to alleviate failing queries to blockchain or when submitting txs due to rate limits.

Added USDC to coin_volatility.json


feat(toast): add inline notification styles and set  to false by default

modify toast component to have inline notification styles and closeable property set to false by default

The other way I was thinking is to export separately an
‘InlineNotification’ that returns a ‘Toast’ with correctly set up defaults.
On Fri, Nov 30, 2018 at 8:43 AM Gergely Nemeth<EMAIL_ADDRESS>wrote:

@gergelyke commented on this pull request.
In docs/migrations/00574.md
https://github.com/uber-web/baseui/pull/574#discussion_r237925053:

@@ -0,0 +1,9 @@
+## Toast

+#### Changed the default closeable value from true to false. Also changed the default notification presentation type to 'inline' that results in default styles change. To render a notification as a toast the default props needs to be overwritten.
+
+```diff
+-  Message
++  import {TYPE} from 'baseui/toast'
++  Message
can we do this in a non-breaking manner, by using defaults for the
original behaviour?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/uber-web/baseui/pull/574#pullrequestreview-180350649,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB1Nj4ugM70d4-hOG-zy_8FFA3MLcHe3ks5u0WBFgaJpZM4Y7hD_
.

Probably that would be better, as folks won't have to set any prop, just use a drop-in component


runtime: use std::max_align_t over max_align_t (NFC)

MSVC does not provide a full C99 environment.  Use the C++ equivalent
spelling for the value.  This allows the build to succeed on Windows.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test and merge

@compnerd Looks like this broke Ubuntu 14.04 bot - https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4486/

Weird, std::max_align_t is part of C++11, it should be present.  I guess we could do a workaround for linux with a comment, but, this seems wrong.

@compnerd I think you need to #include <cstddef> instead of including the C header #include "stddef.h".

Maybe https://github.com/apple/swift/pull/17101 is going to fix it?

Looks like my changes didn't help but it's good to have them anyway...

There's a stddef.h in include/swift/Runtime/Portability.h too. Is that (transitively) included?

Maybe, I've opened https://github.com/apple/swift/pull/17126 to deal with that as well...

I'm still trying to build in a VM :-(

https://github.com/apple/swift/pull/17126 does not appear to have fixed this, so I've opened https://github.com/apple/swift/pull/17139 to revert the original change until this can be sorted out.

I didn't expect building against 14.04 to be so challenging.  Unfortunately, this change is needed to build for Windows, so both states are less than ideal.  I think that the solution here is to special case the 14.04 build to use max_align_t.  I think that the C++ standard library here is broken on 14.04 as I don't believe that they have a definition of std::max_align_t, which is mandated by C++11.

I'm happy to hold off on merging the revert if you can land something relatively quickly that resolves the issue, but we shouldn't let this keep the CI red for much longer.

@rudkx, @xedin I think that #17140 should repair the 14.04 build.


Use public Git repository for 'yval' dependency

Thanks a lot, I need to find more time to synchronize these :)


History API response too big for integrations

At Kubecon, loading the history on socks shop took forever, repsonse sizes of >1MB.
For most timelines, the [{Stamp, Message},...] is enough.

Or, could trim to some time-span/number of messages, and paginate.

Or, could trim to some time-span/number of messages, and paginate.

The Cortex UI use case is to show the flux history under the timeline chart.
There are some technical limitations:

the graph can only be rendered once (updates look bad), which means the history should be available already and should not be queried at the same time
loading the history took >30sec, limited by bandwidth

For that reason I think a "simple" history would be great idea. The date-based pagination would be a cherry on top.

simple=1 has no effect. Should be simple=true.


Implement parrot data and variants

SpongeAPI | SpongeCommon
This pull request implements parrot data and parrot variants, as well as adding a cute little test plugin.
For now I default to red in places as that is the parrot in vanilla with the 0 meta, so it made sense, but I'm open to changing this.
Cheers 🐦
(Here's me using the test plugin to make a ton of red parrots)

Should be good to go if people want to review. Entity constants/catalog changes can be PR'd after, especially after some related catalog changes get in.

I have expanded this PR to implement more of the parrot methods as well as the tame entity event and sitting data as well. Parrots should be good to go :) just need to do some final testing with the new additions

I forgot my license at home officer, please let me off the hook this time.

Okay I've tested these changes and they seem to work well to me.


IR sensor as remote shutter

Hey Toxa! Apologies in advance, this is my first stab at GBDK. I've been chasing the dream of a remote shutter for GB Camera for a while -- I like to take GB Cameras to events and do a kind of a selfie booth. In the past I modded a DMG with a physical shutter jacking into the A button, and then much later put an IR sensor in a DMG using a microcontroller to simulate button presses. But it dawned on me that now we can build it right into the software if you have a GBC!
This actually works(!!!), the one issue being that the IR sensor is inconveniently pointed up. However, I found some 9mm prisms on aliexpress for a few bucks and when they arrive I think it will be a trivial and possibly reversible modification for anyone who wants the selfie-remote experience.
Rather than actually detecting the pattern of any IR remote, here I'm just recognizing any rapid flashing as a remote -- I can disguise my laziness here with the fact that we really want to recognize all manner of remotes indiscriminately.
Feel free to close this PR and take it in your own direction (or not), but thank you for making Photo! open source so I can at least have this feature that's been a dream for years! :)

this slows down the display refresh rate and also not work at daylight on street. so, i suggest:

add setting (off by default), that enables this feature; see: https://github.com/untoxa/gb-photo/commit/06943916feb78d129b3811f76197e96263364d60
make ir_sense_start()/ir_sense_stop() inline, move them into the header
SENSE_DUR should be a define, SDCC can't eliminate the use of the real variable here
yes, you can't use CPU speed switching, not only because of the visual glitches, but also because of the GB Camera hardware

Thanks! I'll implement these :)

i don't see why IR should not be used with repeat or timer mode, when you make selfie using remote and want to hide your hand before camera make the picture.

that also corresponds with the behavior of the link-cable shutter device

also, will be nice to have a game boy rom that sends the IR commands, that may be separate rom or improvement to the "remote": https://github.com/untoxa/gb-photo/blob/master/remote/src/main.c

This is a really interesting idea!
I see your points about making this operate just like it would from the link cable remote... give me a day and I'll move it back into the settings and clean up!

Okay, back to being a setting - and we're not treating IR shutter special in any way, it can be combined with any trigger mode and is subject to save confirmation if you turn that on.
Added IR to the remote, and tried to allow hot-plug of the link cable, refreshing the screen graphic to reflect this status, and only blasting IR when the link cable is disconnected -- so IR or link cable is used depending on which is available.
Only IR shutter is implemented now but we could definitely implement a full control scheme. But shutter covers 90% of the use cases I think.
It might be a good idea to add an .enabled function pointer to the menu structs so one could conditionally show / not show menu items such as IR, CGB palette, SGB border while continuing to keep the menu data const; the height would have to be recalculated based on number of enabled items. Instead of this I've just made IR display a - when not available. This could be a disabled checkbox in the icon font, but I think maybe hiding it would be better overall.
Happy to implement any other feedback here, want to get it right.

uint16_t guard is useless because there is no flow control. 0x80 bit will stay fixed amount of time, no matter if there is a connected device or not.

about dynamic menus. i don't think it is worth implementing the dynamically allocated menus, will be much simpler and with the same efficiency implement "graying" of the menu items. how that may be implemented:

implement graying in the VWF rendering. probably, using a global variable for speed, not function parameter(s). rendering is not too fast to make it even slower, we should be careful.
implement a menu item status callback: takes menu id as a parameter and returns bool. null pointer means "enabled".
implement navigation, that skips the grayed menu items, rollback when it is not possible to move forward and menu is not looped.
that seem very doable, but that must be separate PR of course.

uint16_t guard is useless because there is no flow control. 0x80 bit will stay fixed amount of time, no matter if there is a connected device or not.

HEhe yeah, I realized that eventually after some testing. Missed that in cleanup!

probably you forgot to push the updated PNG.

I didn't change the PNG, but I guess you mean it would be cool if the background indicated that the IR is active somehow... I can try to do that? I'm not an artist but I can try :)
Good ideas on the disabled menus :) I thought maybe "greyed out" wouldn't be clear enough with 2 bit color but inverse is a great idea.
OK, so what should I do here? I'll clean up the guard... let me know what you had in mind for the "updated PNG"?

ah, it flashes the "game boy screen". i thought it does nothing, because images are identical, they are not at that point.

That's right! idea was to have the DMG screen on in the graphic when the link cable is connected and off when it's not.


Create Portfolio_Project.html

Portfolio is created using HTML.


fix: GetTransactionNoWalletResponse.transaction: allow null and expor…

call GetTransactionNoWallet with includeTransaction=false result transaction is null.
I want to export the interface when creating data.

@d-yokoi What is the convention for exporting interfaces? a lot of these smaller interfaces are only split up for readability (nested interfaces are ugly) so exporting everything seems like it would increase confusion (exported interfaces are important, non-exported are not etc.)
I leave the decision up to you.
re: transaction null LGTM ACK

Decided to just export everything from index

tests passed locally. merging

In my experience, it's good to export all interfaces which are visible to users.
However, only types exported at the index file should be under official support so we can change others without announcement.

thank you merge it.


initial state discriminator

State discriminator for two states in the IQ plane

@TheoLaudatQM I added the tests and finished readme, please review again and see if you have any comments

Looking at the test I am wondering if it would not be useful to add a function that rotates the IQ blobs according to the angle calculated with two_state_discriminator, like Ig_rotated, Qg_rotated, Ie_rotated, Qe_rotated = rotate_iq_blobs(Ig, Qg, Ie, Qe), when we will implement it in other scripts, what do you think?

Do you see any use for that?
The idea is to put that angle into the configuration file, and then use the rotated integration weights. This means that the data would already come out rotated...

That is true, I do not know if there is a use-case for which someone would want to run this calibration in a more complex sequence where they would need to rotate the blobs on the fly... If you don't think it is relevant then you can forget it :)

@qguyk Any comments before I merge?


Accessing the Permutohedral Layer  to define a Net through Python Code

I am designing my Caffe Net through python . Just like Importing any other Caffe Layers , is there any way we can import the Permutohedral layer in Python Code  .
Thank you !!

Yes, you can use pycaffe to specify any layer in caffe, including 'permutohedral' layer. We used this layer for propagating information across video frames. You can find an example net specification with permutohedral layers here: https://github.com/varunjampani/video_prop_networks/blob/master/seg_propagation/create_online_net.py


tests: showcase verdict output for drops and alerts in tests - v5

Previous PR: https://github.com/OISF/suricata-verify/pull/1310
Changes from previous PR:

add test for UDP reject with verdict
rebase
adjust verdict output to reflect requested changes in Suricata PR

Ticket
Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/5464

Merged in #1315, thanks!


[Feature templates] Device model validation

Pull Request summary:
Functionality to protect users from creating and attaching templates that are not valid for provided devices.
Description of changes:
In order to validate device models available for template, endpoint "/dataservice/template/feature/types" is used to fetch all of the template types and associated device models. Then, by forcing user to provide list of device models when preparing the template, the same list is compared with available device models for desired template.
Checklist:

[x] Make sure to run pre-commit before commiting changes
[x] Make sure all checks have passed
[x] PR description is clear and comprehensive
[x] Mentioned the issue that this PR solves (if applicable)
[x] Make sure you test the changes

Results:

When providing proper devices, validation pass without notifying user
If user provides device model in list of device models that is not supported for the template, DeviceModelError is raised, and debug message is added to log with information which devices are supported.

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/189


Add GitHub link and remove users route

@tstirrat some minor updates to the dummy app. Could you review and merge?

Let's add the view source link to to global header so it's always visible. and maybe something like the github fork things in the left corner here: https://firefeed.io/

@tstirrat updated. Could you take a look?

This also needs a rebase and squash


Screen outpout laggy (Input via mouse works fine)

[Y ] I have read the FAQ.
[ Y] I have searched in existing issues.

Environment

OS:Windows
scrcpy version: scrcpy-win64-v2.1.1
installation method:Windows release
device model: Samsung note 9
Android version: 10

When running the screen on pc gets really laggy and runs at around 1 fps, the input on the phone gets almost no delay.
Screen is a little broken (Gets buggy sometimes, so i cant use it really) so i checked #1285 and #2884 and tried recording through
adb shell screenrecord /sdcard/file.mp4
adb pull /sdcard/file.mp4
The pulled video is fine.
Also tried solutions listed in #3064 and doesnt seem to affect.
Any help?
scrcpy-win64-v2.1.1\scr... file pushed, 0 skipped. 46.7 MB/s (56995 bytes in 0.001s)
[server] INFO: Device: [samsung] samsung SM-N9600 (Android 10)
[server] WARN: Audio disabled: it is not supported before Android 11
INFO: Renderer: direct3d
WARN: Demuxer 'audio': stream explicitly disabled by the device
INFO: Texture: 512x960

Screen is a little broken

Try scrcpy --turn-screen-off.

The pulled video is fine.

And with scrcpy --record=file.mp4?

It ran perfectly with scrcpy --record=file.mp4

Perfectly smooth run, tried again with no record on and it lags again.

Wait, you mean that the content in the window in real time is smoother with scrcpy --turn-screen-off --record=file.mp4 than scrcpy --turn-screen-off? That can't be true (i.e. that's a coincidence), the recorder is only a client-side additional component :open_mouth:
Add --print-fps to both commands and compare what happens.

You were right, apparently it ran smoothly the first time with the recorder and kinda laggy the second time with screen off but the events werent connected because it runs smoothly with both of those now.
It actually runs smoothly when i run it without those now too!
Not quite sure of the reasons but its working perfectly now! thank you so much.
On another note after i managed to run the app it wont accept mouse input apparently, as it wont transfer to an event in the app and it works fine outside it... Is there a touch event input? So when i click it generates a touch event instead of an actual mouse click on the phone? Just asking im not really sure how the mouse translates to the actual phone but i read some other issues and thats the picture that im getting.

[Update]
Ok so i have done a few more tests and i have identified that the issue is with the specific cellphone (Note 9) in the specific app (MH Now)
Tried with another phone (Note 11 with input via usb depuration enabled) and it worked perfectly, samsung doesnt have this config so i dont know how i could make it work for the note 9


UnmarshallerError if specifying format with type: [foo, 'null']

I'm still working on minimal reproducer to prove this out so apologies for the lack of a one in advance.
I've got a schema like this:
openapi: '3.1.0'
# ...
components:
  schemas:
    PatchList:
      type: object
      properties:
        # ...
        pull_url:
          title: Pull URL
          type:
            - string
            - 'null'
          format: uri
          maxLength: 255
        # ...

If my server returns a response with pull_url set to null, then the call to openapi_core.validation.response.validators.ResponseValidator.validate fails with the following traceback:
Traceback (most recent call last):
  File "/dev/patchwork/patchwork/tests/api/test_relation.py", line 267, in test_remove_one_patch_from_relation_good
    resp = self.client.patch(
  File "/dev/patchwork/patchwork/tests/api/utils.py", line 241, in patch
    validator.validate_data(
  File "/dev/patchwork/patchwork/tests/api/validator.py", line 141, in validate_data
    result.raise_for_errors()
  File "/dev/openapi-core/openapi_core/validation/datatypes.py", line 12, in raise_for_errors
    raise error
  File "/dev/openapi-core/openapi_core/validation/response/validators.py", line 245, in validate
    data = self._get_data(response, operation_response)
  File "/dev/openapi-core/openapi_core/validation/response/validators.py", line 88, in _get_data
    data = self._unmarshal(schema, casted)
  File "/dev/openapi-core/openapi_core/validation/validators.py", line 76, in _unmarshal
    return unmarshaller(value)
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 91, in __call__
    return self.unmarshal(value)
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 434, in unmarshal
    return unmarshaller.unmarshal(value)
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 316, in unmarshal
    properties = self.format(value)
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 325, in format
    return self._unmarshal_properties(formatted, schema_only=schema_only)
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 354, in _unmarshal_properties
    all_of_properties = self._clone(all_of_schema).format(
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 325, in format
    return self._unmarshal_properties(formatted, schema_only=schema_only)
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 373, in _unmarshal_properties
    properties[prop_name] = self.unmarshallers_factory.create(
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 91, in __call__
    return self.unmarshal(value)
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 433, in unmarshal
    unmarshaller = self._get_best_unmarshaller(value)
  File "/dev/openapi-core/openapi_core/unmarshalling/schemas/unmarshallers.py", line 430, in _get_best_unmarshaller
    raise UnmarshallerError("Unmarshaller not found for type(s)")
openapi_core.unmarshalling.schemas.exceptions.UnmarshallerError: Unmarshaller not found for type(s)

If I comment out format, things work as expected. I suspect it's attempting to apply a formatter for the null values. As far as I can tell, this should work though. I'm not aware of any other mechanism to achieve this.

This post suggests I could use oneOf to do this, but it seems we're not able to do so here:
openapi: '3.1.0'
# ...
components:
  schemas:
    PatchList:
      type: object
      properties:
        # ...
        pull_url:
          title: Pull URL
          oneOf:
            - type: 'null'
            - type: string
              format: uri
              maxLength: 255
        # ...

This yields the exact same exception.

Things do, however, work if I specify type twice:
openapi: '3.1.0'
# ...
components:
  schemas:
    PatchList:
      type: object
      properties:
        # ...
        pull_url:
          title: Pull URL
          type:
            - type: 'null'
            - type: string
          oneOf:
            - type: 'null'
            - type: string
              format: uri
              maxLength: 255
        # ...

Hi @stephenfin
thanks for reporting the issue.
The first example doesn't work because uri is string type format only so if you define multiple types it will fail with others (in this case null). This works as expected.
The second example here is null is not considered as valid if type is not defined in main schema. Here we have the issue.
The third one is just a workaround for the second example issue which (as you noticed) shouldn't be necessary.

@p1c2u Thanks for confirming that the latter two examples are what we'd expect: the OpenAPI spec is seriously lacking when it comes to discussions on nullable attributes :disappointed: Is there anything I can do to help? I did try to address this but it seems there have been significant changes in the 0.17 beta and my test suite has yet to be adapted for this so I was kind of flying blind.

For what it's worth, the first example is rather common too, even if it's technically correct. For example, the OpenAPI 3.1 spec for GitHub's own API contains things like this:
---
openapi: 3.1.0
# ...
paths:
  # ...
  "/authorizations":
    # ...
    post:
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                scopes:
                  description: A list of scopes that this authorization is in.
                  type:
                  - array
                  - 'null'
                  items:
                    type: string
                  examples:
                  - public_repo
                  - user
                # ...

In this case, items only applies for type: array, not type: null, so this doesn't seem valid either. It's common though. Given the spec is silent on this matter, I wonder if this is something we want to choose to accept also?

Hmm, I actually think JSONSchema allows the first example (henceforth option A). From the spec:

7.6.1. Assertions and Instance Primitive Types
Most assertions only constrain values within a certain primitive type. When the type of the instance is not of the type targeted by the keyword, the instance is considered to conform to the assertion.
For example, the "maxLength" keyword from the companion validation vocabulary [json-schema-validation]: will only restrict certain strings (that are too long) from being valid. If the instance is a number, boolean, null, array, or object, then it is valid against this assertion. This behavior allows keywords to be used more easily with instances that can be of multiple primitive types. The companion validation vocabulary also includes a "type" keyword which can independently restrict the instance to one or more primitive types. This allows for a concise expression of use cases such as a function that might return either a string of a certain length or a null value:
{
    "type": ["string", "null"],
    "maxLength": 255
}

If "maxLength" also restricted the instance type to be a string, then this would be substantially more cumbersome to express because the example as written would not actually allow null values. Each keyword is evaluated separately unless explicitly specified otherwise, so if "maxLength" restricted the instance to strings, then including "null" in "type" would not have any useful effect.

@stephenfin 0.17 should be mostly compatible except validation errors. Can you tell which changes do you have in mind?
First option is definitely correct the problem is current implementation of format validators and unmarshallers which don't allow to handle multiple types with format correctly. I started the refactor of this part.

@stephenfin 0.17 should be mostly compatible except validation errors. Can you tell which changes do you have in mind?

I'm using the Django validators and seeing the following exceptions when installing the pre-release (pip install --pre --upgrade openapi-core):
Traceback (most recent call last):
  File "/usr/lib64/python3.8/unittest/case.py", line 60, in testPartExecutor
    yield
  File "/usr/lib64/python3.8/unittest/case.py", line 676, in run
    self._callTestMethod(testMethod)
  File "/usr/lib64/python3.8/unittest/case.py", line 633, in _callTestMethod
    method()
  File "/dev/patchwork/patchwork/tests/api/utils.py", line 104, in wrapper
    func(self, *args, **kwargs)
  File "/dev/patchwork/patchwork/tests/api/test_comment.py", line 189, in test_update_authorized
    resp = self._test_update(person=person)
  File "/dev/patchwork/patchwork/tests/api/test_comment.py", line 171, in _test_update
    return self.client.patch(
  File "/dev/patchwork/patchwork/tests/api/utils.py", line 84, in client_wrapper
    resp = orig_func(path, data, *orig_args, **orig_kwargs)
  File "/dev/patchwork/patchwork/tests/api/utils.py", line 241, in patch
    validator.validate_data(
  File "/dev/patchwork/patchwork/tests/api/validator.py", line 128, in validate_data
    validator = RequestValidator(schema_unmarshallers_factory)
  File "/dev/patchwork/.tox/py38-django41/lib/python3.8/site-packages/openapi_core/validation/request/validators.py", line 86, in __init__
    super().__init__(
  File "/dev/patchwork/.tox/py38-django41/lib/python3.8/site-packages/openapi_core/validation/validators.py", line 66, in __init__
    raise NotImplementedError(
NotImplementedError: schema_unmarshallers_factory is not assigned

I suspect I just need to update how I'm creating my validators. No big deal.

First option is definitely correct the problem is current implementation of format validators and unmarshallers which don't allow to handle multiple types with format correctly. I started the refactor of this part.

Excellent. Happy to test this when it's available! 🙋

Oh I see you use low level integration. You must pass spec at first argument to RequestValidator/ResponseValidator but probably I will make it backward compatible in the future pre-rereleases.


⚠ Shadow Does Streams has degraded performance

In dfd66a0, Shadow Does Streams (https://stream.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 5448 ms

Resolved: Shadow Does Streams performance has improved in 514843f after 7 minutes.