Linux (Flatpak) support

Hey is anything here that isn’t working on Linux?
Would be great if you could compile an Flatpak for Linux.

Linux is not supported yet. But I have plan to add Linux support.

I hope it can be packaged in Flatpak/.deb/Appimage/Snap.

I second this, if you do add linux support, I think the best way to do it would be to target Flatpak. It would basically be available on all Distributions, including Valve's Steamdeck.

I second this, if you do add linux support, I think the best way to do it would be to target Flatpak. It would basically be available on all Distributions, including Valve's Steamdeck.

Flatpak should be enough.
Shouldn’t make it too complicated.
Flatpak is supported on all Systems and it works the best!

I'm interested to work on this issue. I have no experience in writing console emulator but AFAIK what I need to do is just fixing Windows-specific API that used by Kyty. Actually I already started on this task with the first step is to enabled CI build on Linux with #29. Here is my plan:

Add GitHub Actions to build for Windows only.
Add GitHub Actions to build for Linux. This build will not going to work yet but it is required for fixing code to run on Linux.
I will slowly fixing each error from Linux build.

With this plan @InoriRus can focus on the emulator part without worrying on the Linux-specific part.

Some progress today with my spare time:
[~/Workspace/personal/kyty/build:0]$ make
[  0%] Building CXX object lib/Scripts/CMakeFiles/scripts_obj.dir/src/BuildTools.cpp.o
[  0%] Building CXX object lib/Scripts/CMakeFiles/scripts_obj.dir/src/Scripts.cpp.o
[  0%] Building CXX object lib/Scripts/CMakeFiles/scripts_obj.dir/src/ScriptsFileLib.cpp.o
[  0%] Building CXX object lib/Scripts/CMakeFiles/scripts_obj.dir/src/ScriptsLoader.cpp.o
[  0%] Built target scripts_obj
[  1%] Building C object 3rdparty/sdl2/CMakeFiles/sdl2_obj.dir/src/SDL.c.o
In file included from /home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sdl2/include/SDL_log.h:40,
                 from /home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sdl2/src/./SDL_internal.h:125,
                 from /home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sdl2/src/SDL.c:21:
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sdl2/include/SDL_stdinc.h:533:49: error: unknown type name ‘wchar_t’
  533 | extern DECLSPEC size_t SDLCALL SDL_wcslen(const wchar_t *wstr);
      |                                                 ^~~~~~~

Already did some fixes to the build configurations but it look like there are a lot of work just for the build configurations.

The progress for today is looking good:
[~/Workspace/personal/kyty:0]$ cmake --build build
[  0%] Building CXX object lib/Scripts/CMakeFiles/scripts_obj.dir/src/BuildTools.cpp.o
[  1%] Building CXX object lib/Scripts/CMakeFiles/scripts_obj.dir/src/Scripts.cpp.o
[  1%] Building CXX object lib/Scripts/CMakeFiles/scripts_obj.dir/src/ScriptsFileLib.cpp.o
[  1%] Building CXX object lib/Scripts/CMakeFiles/scripts_obj.dir/src/ScriptsLoader.cpp.o
[  1%] Built target scripts_obj
[  1%] Building C object 3rdparty/rijndael/CMakeFiles/rijndael_obj.dir/source/rijndael-alg-fst.c.o
[  1%] Built target rijndael_obj
[  2%] Linking C static library librijndael.a
[  2%] Built target rijndael
[  2%] Building C object 3rdparty/lzma/CMakeFiles/lzma_obj.dir/C/LzFind.c.o
[  3%] Building C object 3rdparty/lzma/CMakeFiles/lzma_obj.dir/C/LzmaDec.c.o
[  3%] Building C object 3rdparty/lzma/CMakeFiles/lzma_obj.dir/C/LzmaEnc.c.o
[  3%] Built target lzma_obj
[  3%] Linking C static library liblzma.a
[  3%] Built target lzma
[  3%] Building C object 3rdparty/sqlite/CMakeFiles/sqlite_obj.dir/src/altered_sqlite3secure.c.o
In file included from /home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/altered_sqlite3secure.c:63:
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sqlite3.c: In function ‘sqlite3SelectNew’:
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sqlite3.c:125321:10: warning: function may return address of local variable [-Wreturn-local-addr]
125321 |   return pNew;
       |          ^~~~
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sqlite3.c:125281:10: note: declared here
125281 |   Select standin;
       |          ^~~~~~~
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sqlite3.c:125281:10: note: declared here
In file included from /home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/altered_sqlite3secure.c:69:
In function ‘sha1_update’,
    inlined from ‘sha1_final’ at /home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c:272:3:
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c:244:7: warning: ‘sha1_transform’ reading 64 bytes from a region of size 1 [-Wstringop-overread]
  244 |       sha1_transform(context, data + i);
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c:244:7: note: referencing argument 2 of type ‘const uint8_t[64]’ {aka ‘const unsigned char[64]’}
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c: In function ‘sha1_final’:
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c:144:6: note: in a call to function ‘sha1_transform’
  144 | void sha1_transform(sha1_ctx *context, const uint8_t buffer[64])
      |      ^~~~~~~~~~~~~~
In function ‘sha1_update’,
    inlined from ‘sha1_final’ at /home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c:275:5:
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c:244:7: warning: ‘sha1_transform’ reading 64 bytes from a region of size 1 [-Wstringop-overread]
  244 |       sha1_transform(context, data + i);
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c:244:7: note: referencing argument 2 of type ‘const uint8_t[64]’ {aka ‘const unsigned char[64]’}
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c: In function ‘sha1_final’:
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/sqlite/src/sha1.c:144:6: note: in a call to function ‘sha1_transform’
  144 | void sha1_transform(sha1_ctx *context, const uint8_t buffer[64])
      |      ^~~~~~~~~~~~~~
[  3%] Built target sqlite_obj
[  3%] Linking C static library libsqlite.a
[  3%] Built target sqlite
[  3%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/common/debug.c.o
[  3%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/common/entropy_common.c.o
[  4%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/common/error_private.c.o
[  4%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/common/fse_decompress.c.o
[  4%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/common/pool.c.o
[  4%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/common/threading.c.o
[  5%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/common/xxhash.c.o
[  5%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/common/zstd_common.c.o
[  5%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/fse_compress.c.o
[  5%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/hist.c.o
[  6%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/huf_compress.c.o
[  6%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/zstd_compress.c.o
[  6%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/zstd_compress_literals.c.o
[  6%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/zstd_compress_sequences.c.o
[  7%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/zstd_double_fast.c.o
[  7%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/zstd_fast.c.o
[  7%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/zstd_lazy.c.o
[  7%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/zstd_ldm.c.o
[  8%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/zstd_opt.c.o
[  8%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/compress/zstdmt_compress.c.o
[  8%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/decompress/huf_decompress.c.o
[  8%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/decompress/zstd_ddict.c.o
[  9%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/decompress/zstd_decompress.c.o
[  9%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/decompress/zstd_decompress_block.c.o
[  9%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/deprecated/zbuff_common.c.o
[  9%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/deprecated/zbuff_compress.c.o
[ 10%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/deprecated/zbuff_decompress.c.o
[ 10%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/dictBuilder/cover.c.o
[ 10%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/dictBuilder/divsufsort.c.o
[ 10%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/dictBuilder/fastcover.c.o
[ 11%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/dictBuilder/zdict.c.o
[ 11%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/legacy/zstd_v01.c.o
[ 11%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/legacy/zstd_v02.c.o
[ 11%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/legacy/zstd_v03.c.o
[ 12%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/legacy/zstd_v04.c.o
[ 12%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/legacy/zstd_v05.c.o
[ 12%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/legacy/zstd_v06.c.o
[ 13%] Building C object 3rdparty/zstd/CMakeFiles/zstd_obj.dir/lib/legacy/zstd_v07.c.o
[ 13%] Built target zstd_obj
[ 13%] Linking C static library libzstd.a
[ 13%] Built target zstd
[ 14%] Building CXX object lib/Sys/CMakeFiles/sys_obj.dir/src/SysLinuxDbg.cpp.o
[ 14%] Building CXX object lib/Sys/CMakeFiles/sys_obj.dir/src/SysLinuxFileIO.cpp.o
[ 14%] Building CXX object lib/Sys/CMakeFiles/sys_obj.dir/src/SysWindowsDbg.cpp.o
[ 14%] Building CXX object lib/Sys/CMakeFiles/sys_obj.dir/src/SysWindowsFileIO.cpp.o
[ 14%] Built target sys_obj
[ 14%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/CharUcd.cpp.o
[ 15%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/Compression.cpp.o
[ 15%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/Core.cpp.o
[ 15%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/Database.cpp.o
[ 15%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/DateTime.cpp.o
[ 16%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/DbgAssert.cpp.o
[ 16%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/Debug.cpp.o
[ 16%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/File.cpp.o
[ 16%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/Hashmap.cpp.o
[ 17%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/JsonReader.cpp.o
[ 17%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/Language.cpp.o
[ 17%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/MSpace.cpp.o
[ 17%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/MemoryAlloc.cpp.o
[ 18%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/SDLSubsystem.cpp.o
[ 18%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/String.cpp.o
[ 18%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/Subsystems.cpp.o
[ 18%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/Threads.cpp.o
[ 19%] Building CXX object lib/Core/CMakeFiles/core_obj.dir/src/Timer.cpp.o
[ 19%] Built target core_obj
[ 19%] Building CXX object lib/Math/CMakeFiles/math_obj.dir/src/CryptoAES.cpp.o
[ 20%] Building CXX object lib/Math/CMakeFiles/math_obj.dir/src/CryptoHash.cpp.o
[ 20%] Building CXX object lib/Math/CMakeFiles/math_obj.dir/src/Math.cpp.o
[ 20%] Building CXX object lib/Math/CMakeFiles/math_obj.dir/src/Rand.cpp.o
[ 20%] Building CXX object lib/Math/CMakeFiles/math_obj.dir/src/VectorAndMatrix.cpp.o
[ 20%] Built target math_obj
[ 20%] Linking CXX static library libsys.a
[ 20%] Built target sys
[ 20%] Linking CXX static library libmath.a
[ 20%] Built target math
[ 20%] Linking CXX static library libcore.a
[ 20%] Built target core
[ 20%] Linking CXX static library libscripts.a
[ 20%] Built target scripts
[ 20%] Generate KytyGitVersion.h
[ 20%] Built target KytyGitVersion
[ 20%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/deps/clog/src/clog.c.o
[ 20%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/api.c.o
[ 21%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/cache.c.o
[ 21%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/init.c.o
[ 21%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/cache/descriptor.c.o
[ 21%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/cache/deterministic.c.o
[ 22%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/cache/init.c.o
[ 22%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/info.c.o
[ 22%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/init.c.o
[ 22%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/isa.c.o
[ 23%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/name.c.o
[ 23%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/topology.c.o
[ 23%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/uarch.c.o
[ 23%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/vendor.c.o
[ 24%] Building C object 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/windows/init.c.o
/home/ultimaweapon/Workspace/personal/kyty/source/3rdparty/cpuinfo/src/x86/windows/init.c:11:10: fatal error: windows.h: No such file or directory
   11 | #include <windows.h>
      |          ^~~~~~~~~~~
compilation terminated.
make[2]: *** [3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/build.make:272: 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/src/x86/windows/init.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:479: 3rdparty/cpuinfo/CMakeFiles/cpuinfo_obj.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
[~/Workspace/personal/kyty:2]$

Just using SDL2 from vcpkg by integrated vcpkg as a Git submodule to solve yesterday error. Not sure if @InoriRus okay with this.

Just got a hit from Vulkan SDK problem. VCPKG did not included the source for this and it is required to do a manual install.

Better to make an appimage instead of flatpak.

Also i will try compiling on linux

Got it to compile on Ubuntu using #38

But I had to comment out basically all of fc script in https://github.com/InoriRus/Kyty/blob/1fdaa18f390398fa347d8f57984111332cc25036/source/CMakeLists.txt#L157 else I'd get stuck here
Scanning dependencies of target fc_script
[ 97%] Building CXX object CMakeFiles/fc_script.dir/3rdparty/gtest/src/gtest-all.cc.o
[ 97%] Building CXX object CMakeFiles/fc_script.dir/KytyScripts.cpp.o
make[2]: *** No rule to make target 'vulkan-1-NOTFOUND', needed by 'fc_script'.  Stop.
make[1]: *** [CMakeFiles/Makefile2:471: CMakeFiles/fc_script.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

Couldn't figure it out.

fc_script is a main emulator binary.

Better to make an appimage instead of flatpak.

I get why you would prefer an appimage however flatpaks are the only option on certain devices like the Valve Steam Deck since they don't allow appimages due to distro restrictions. so it's better to have both cause no doubt people would want to try and run it on them.

Better to make an appimage instead of flatpak.

Better to make an appimage instead of flatpak.

We get why you would prefer an appimage however flatpaks are the only option on certain devices like the Valve Steam Deck since they don't allow appimages due to distro restrictions. so it's better to have both cause no doubt people would want to try and run it on them.

Better to make an appimage instead of flatpak.

We get why you would prefer an appimage however flatpaks are the only option on certain devices like the Valve Steam Deck since they don't allow appimages due to distro restrictions. So it's better to have both cause no doubt people would want to try and run it on them.

Better to make an appimage instead of flatpak.

We get why you would prefer an appimage however flatpaks are the only option on certain devices like the Valve Steam Deck since they don't allow appimages due to distro restrictions. So it's better to have both cause no doubt people would want to try and run it on them.

Due to the power of the Steam Deck, its highly unlikely to run this on it.

Better to make an appimage instead of flatpak.

We get why you would prefer an appimage however flatpaks are the only option on certain devices like the Valve Steam Deck since they don't allow appimages due to distro restrictions. So it's better to have both cause no doubt people would want to try and run it on them.

Appimages work fine on the steam deck, but I think both would be preferable

Better to make an appimage instead of flatpak.

We get why you would prefer an appimage however flatpaks are the only option on certain devices like the Valve Steam Deck since they don't allow appimages due to distro restrictions. So it's better to have both cause no doubt people would want to try and run it on them.

Appimages work fine on the steam deck, but I think both would be preferable

Actually, no, AppImages do not work fine on the Steam Deck due to its restrictions, so flatpaks would be preferable.

Better to make an appimage instead of flatpak.

We get why you would prefer an appimage however flatpaks are the only option on certain devices like the Valve Steam Deck since they don't allow appimages due to distro restrictions. So it's better to have both cause no doubt people would want to try and run it on them.

Appimages work fine on the steam deck, but I think both would be preferable

Actually, no, AppImages do not work fine on the Steam Deck due to its restrictions, so flatpaks would be preferable.

Actually, yes, I have ran appimages on my steamdeck many times. You just set the executable bit and run it in dolphin, or add it as a non steam game and run it from gaming mode.

Better to make an appimage instead of flatpak.

We get why you would prefer an appimage however flatpaks are the only option on certain devices like the Valve Steam Deck since they don't allow appimages due to distro restrictions. So it's better to have both cause no doubt people would want to try and run it on them.

Appimages work fine on the steam deck, but I think both would be preferable

Actually, no, AppImages do not work fine on the Steam Deck due to its restrictions, so flatpaks would be preferable.

Actually, yes, I have ran appimages on my steamdeck many times. You just set the executable bit and run it in dolphin, or add it as a non steam game and run it from gaming mode.

Again, there are AppImage restrictions on Steam Deck, yes you may be able to start the AppImage but there are compatibility issues (restrictions), this is exactly why flatpaks are preferable.

Better to make an appimage instead of flatpak.

We get why you would prefer an appimage however flatpaks are the only option on certain devices like the Valve Steam Deck since they don't allow appimages due to distro restrictions. So it's better to have both cause no doubt people would want to try and run it on them.

Appimages work fine on the steam deck, but I think both would be preferable

Actually, no, AppImages do not work fine on the Steam Deck due to its restrictions, so flatpaks would be preferable.

Actually, yes, I have ran appimages on my steamdeck many times. You just set the executable bit and run it in dolphin, or add it as a non steam game and run it from gaming mode.

Again, there are AppImage restrictions on Steam Deck, yes you may be able to start the AppImage but there are compatibility issues (restrictions), this is exactly why flatpaks are preferable.

What restrictions are there that would affect an emulator?

What restrictions are there that would affect an emulator?

External dependencies can't be installed due to the os file system being read only if they are missing and some need super user privileges to run. Those are the issues we've ran into so far.

What restrictions are there that would affect an emulator?

External dependencies can't be installed due to the os file system being read only if they are missing and some need super user privileges to run. Those are the issues we've ran into so far.

Why not just include the dependencies in the appimage?

What restrictions are there that would affect an emulator?

External dependencies can't be installed due to the os file system being read only if they are missing and some need super user privileges to run. Those are the issues we've ran into so far.

Why not just include the dependencies in the appimage?

The steam deck has 64, 256, or 512 GB of space.
Please let’s be generous in space-consuming whether you have a steam deck or not.
Unnecessary space consumption is not the ideal solution to go!

Got it to compile on Ubuntu using #38
 But I had to comment out basically all of fc script in
https://github.com/InoriRus/Kyty/blob/1fdaa18f390398fa347d8f57984111332cc25036/source/CMakeLists.txt#L157
else I'd get stuck here
Scanning dependencies of target fc_script
[ 97%] Building CXX object CMakeFiles/fc_script.dir/3rdparty/gtest/src/gtest-all.cc.o
[ 97%] Building CXX object CMakeFiles/fc_script.dir/KytyScripts.cpp.o
make[2]: *** No rule to make target 'vulkan-1-NOTFOUND', needed by 'fc_script'.  Stop.
make[1]: *** [CMakeFiles/Makefile2:471: CMakeFiles/fc_script.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

Couldn't figure it out.

Please be aware that XDG is marked as a Legacy in the current Ubuntu version and will soon be deprecated.
It would be in all interest to ditch the XDG support completely

What restrictions are there that would affect an emulator?

External dependencies can't be installed due to the os file system being read only if they are missing and some need super user privileges to run. Those are the issues we've ran into so far.

Why not just include the dependencies in the appimage?

Wouldn't be a good idea due to Steam Deck's storage size, also when the dependencies have updates, you would have to rebuild the AppImage with those updates which would be unnecessary.


Migrate to new Azure Search SDK

Consider migrating to Azure.Search.Documents for improved performance and easier authentication.

Done in https://github.com/NuGet/NuGet.Jobs/pull/1034


Don't add -arch explictly to stdlib compile flags on Darwin

Rely instead on setting the OSX_ARCHITECTURES property (#38415)
Address rdar://96087734

@swift-ci please build toolchain

The windows breakage appears to be a missing dependency edge in a circular dependency between swiftAST and swiftBasic. libswiftAST.a contains the InFlightDiagnostic::flush definition, but isn't linked back into libswiftBasic.a, which uses it. Well that's gross.

We will probably need https://github.com/apple/swift/pull/61001 to make the windows build work.
Someone should probably pull the diagnostic bits into swiftBasic and break this link cycle, but later.

@swift-ci please test

@swift-ci please build toolchain

From a quick search in CMakeLists.txt/*.cmake files I don't see any other place in which we manually append -arch parameters.


Develop unit tests for disk space monitoring script

User Story

#6

good day sir please sir can you please explain what specifically what is to be done

After the ticket #12 is done, you need to test it. The test is done using a notebook file, as shown earlier

ok sir so am write a python script to test it sir

sir that test is not going sir. i have tried implementing the information found in the notebook into #12 code sir but it does not work in the notebook sir and nobody is able to help me

Push then your code @bryandino673 and create a pull request so that I can tell you where there's a problem

sir i have push and given the link to you sir but no fit back sir . i mean sir if there is no reply i will not know if what i did is correct sir


[AppService] az webapp: Rename container related parameters and add parameters --container-image-name and --container-registry-url into commands az webapp create and az webapp deployment slot create to deprecate --deployment-container-image-name

Related command
az webapp create, az webapp deployment slot create, az webapp config container set
Description
Remove docker prefix and rename container webapp related parameters
--docker-registry-server-url
--docker-custom-image-name
--docker-registry-server-user
--docker-registry-server-password
to
--container-registry-url
--container-image-name
--container-registry-user
--container-registry-password
and adding parameters --container-image-name and container-registry-url into az webapp create and az webapp deployment slot create to deprecate parameter --deployment-container-image-name. However, we will keep --deployment-container-image-name and allow customer to still use it for now.
Testing Guide

Ran commands az webapp create, az webapp deployment slot create, az webapp config container set and check if those changes break them
Ran appservice tests locally

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

AppService

@jvano

/azp run

since there are muliple changes in this PR, it would be good to separately list all of the changes in the History Notes section above

since there are muliple changes in this PR, it would be good to separately list all of the changes in the History Notes section above

@yanzhudd thanks for your comment, I updated History Note and put separate records of my changes there. Please check it out, thanks

Let me check with you if there is any breaking change in this PR?

please rerun some related tests in live mode to check if it meets your expectation

Please note that Azure CLI team is not responsible for code style and specification, but not business logic. It is better to get approval from service team for business logic as well.

Let me check with you if there is any breaking change in this PR?

I believe there is no breaking change in this PR, we don't remove those old parameters when we added support on new parameters, so customer should still be able to do what they want to do in the old way.

Hi @mstxsun,
it seems that there are multiple deprecated parameters in this PR, and we are about to having a breaking change window next sprint. Let me check with you if you plan to remove these deprecated parameter in the breaking change window. If so or you plan to make any other breaking changes, please let us know. Thanks!


Understanding the concept of session in JSP

Proposed title of the article
Understanding the concept of  session in JSP
Proposed article introduction
A session is an object with a unique session ID that is connected with each user, and the user's data is based on the account they have established. In a session, many types of data may be set; these data, which are specific to each site user, assist the user and the website owner in various ways.
In this article, we will discuss the concept of sessions in JSP, the session implicit object, Session methods in JSP, and how it is implemented.
Key takeaways
Introduction.
The session implicit object .
HttpSession interface methods.
Session methods in JSP.
HttpSession Example.
Article quality
I checked over some of Section Engineering's published writings and realized that the JSP sessions has yet to be covered and in most websites,this concept is just mentioned but not explained in detail, in this article I will explain the JSP sessions in detail.
References

Hi @Nicholas-Obare
In as much as the topic isn't covered on section, I have found several articles in sites like Geeks for Geeks and W3 schools that have covered this topic. We cannot move forward with this article but you are more than welcome to explore other topics of interest.


Convert String to JSON?

This might be a silly question. But is there a way to get a json object from string instead of a file by this library?

Yes, it is possible and code is ready but it waits for merge: https://github.com/nottyo/robotframework-jsonlibrary/pull/13


Build on Ubuntu not displaying WebView component

Hi @frang75 !  I built and ran the sample, WebHello, on Ubuntu but couldn't get the webView component to display in the app.  The app runs/builds fine, no errors logged to console but the actual webView component will not render.  I can't yet debug on Ubuntu but I will soon and try to isolate what the problem is but I wanted to bring it to your attention.
I am using/running/customizing the WebView component on MacOS which works great.  As you know, I had the ARM build for Windows giving me some headaches so I haven't tested yet Windows build for WebView but I'll spin up an X64 VM soon and build the Windows webView sample there and test as my next step.
Thanks and lmk what I'm missing in my setup to get WV working on Ubuntu/Linux.  I sent some discord messages that might shed some light on the issue possibly.

Hi @d33p-dev
In Linux/Ubuntu is necessary to install the webview-gtk development libraries.
https://nappgui.com/en/gui/webview.html#h1.3

LOL so RTFM..........................  THANKS!!!!!!!


bad connection or unexpected message

I just try select from goroutines inside opened transaction and got ths error:
pgdriver: Next: unexpected message '\x00'
Then I use pgx driver i got error:
driver: bad connection

@jpascal were you able to resolve this issue? We're seeing the same thing

@54M5M17H you can try to replace pgdriver with pgx and see if the problems goes away https://bun.uptrace.dev/postgres/#pgx


PM3D-Calibration missing data MD-CASH&WEEDS-2023

Description
For MD-CASH&WEEDS-2023 1 timing is missing from the soybean data and 2 timings are missing from the corn data.
Task Category

Data Shepherding

Type of User

Calibrator

User Code

MD-Mirsky

Stakeholder Point of Contact

@marialauracangiano

Data Shepherd

@zackgrzywacz

@zackgrzywacz You said that you completed these data, right?

@marialauracangiano oops I missed this one. I'm 95% sure we missed those timings due to our late planting last year, but I will double check


Crash on GATT sync (from crashlytics)

Try to push sync and then switch from graph view and (maybe) change sensor

in 1.5.20

QA passed


TypeError: Cannot read property 'Bucket' of undefined - but object is correct

Hi - I am not having success due to an error: "TypeError: Cannot read property 'Bucket' of undefined"
Below is my execution of the transfer utility
const sendToS3WithTransferUtil = (video, box, user) => {
  const config = {
    region: configs.AWS.region,
    access_key: configs.AWS.accessKeyId,
    secret_key: configs.AWS.secretAccessKey,
  };
  const movName = movieName(video);

  return transferUtility.setupWithBasic(config).then((ready) => {
    const options = {
      file: video.uri,
      bucket: configs.AWS.bucketInput,
      key: `uploads/${box.doc.ref.id}/${user.doc.ref.id}/${movName}`,
    };
    console.log(ready, 'transferUtility ready for s3; upload options -> ', options);

    return transferUtility.upload(options);
  });
};

i can verify config going into the method reads as i expect and promise returns true.
i can verify options going into the method reads as i expect

{bucket:'my.bucket.name',file:'longpathtofile',key:'path/to/file/in/bucket.mp4'}

have i done this incorrectly?

i am an idiot...it's working as expected

How did you do it? I have got the same error.


mlp_sizes seem wrong in qlinear_benchmark.py

https://github.com/spcl/QuaRot/blob/main/benchmarks/qlinear_benchmark.py#L53
when benchmark down_proj, the input and output channel should swap their position in mlp_sizes config, i.e. [28672, 8192] for llama-70B
after correct this, the latency of hadamard transform becomes noticeable for llama-70B down_proj.

@yyfcc17
Thank you so much for your issue.
The issue is that the CUDA kernel for Hadamard transform (this repo: https://github.com/Dao-AILab/fast-hadamard-transform) applies fast transformation on power-of-two matrices. However, one needs to add another matrix multiplication on top of it (see details here).
However, for a given matrix dimension n (which is not power-of-two), one can solve the performance issue by hardcoding the Hadamard transformations in CUDA. Dao's repo has a nice code generator for this and you can get reasonable speedups for an specific matrix size.

thanks for your answer, but i don't know how the K  in https://github.com/spcl/QuaRot/blob/main/fake_quant/hadamard_utils.py#L7
is choosen.
specifically, for 28672, it will hit n  % 28 == 0 in your  code. do you mean this can be slower than other K setting? so which value should be used to accelerate? 224? (28672 = 224 * 128)

i see, thanks for your reply.


act: 0.2.55 -> 0.2.56

Description of changes
https://github.com/nektos/act/releases/tag/v0.2.56
https://github.com/nektos/act/compare/v0.2.55...v0.2.56

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 275088 run on x86_64-linux 1

1 package built:

act


Stateless session handling?

I have been trying to set up a Google OpenID Client login to my small webapp, but we are running multiple instances of the same application.
Are there any suggestions how am I supposed to do session handling in this case? I was thinking about storing the whole session in a cookie, so nothing is stored on server side, but I don't know how should I approach this.
Have anyone had some experiences similar to this?

@htamas it would be better to discuss this directly in pac4j-user: http://www.pac4j.org/mailing-lists.html
Your question is not really related to the dropwizard integration of pac4j (and I personally I'm not sure I can help ^^).
Thanks!


Timeouts cause the number of subtests to be wrong.

https://website-webstatus-dev.corp.goog/features/preserves-pitch?q=baseline_date%3A2023-01-01..2023-12-31
Going to WPT.fyi, we see the number of subtests for safari to be low

https://wpt.fyi/results/?label=master&label=stable&aligned&q=feature%3Apreserves-pitch!is%3Atentative
We need to ignore them like we ignore crashes

This reported feature's score was hidden. The reason can be found in this PR https://github.com/GoogleChrome/webstatus.dev/pull/301/files


OptionException message contains duplicate missing required options.

Please remove the duplicate option names from the "Missing required option(s)" message that OptionException produces when a required option has synonyms.
Example:
OptionException message contains three required options (one for each name):
Missing required option(s) [f/csv-file-name/ff, f/csv-file-name/ff, f/csv-file-name/ff].

Usage: java -jar fatca.jar com.opessoftware.fatca.App [options]

Option (* = required)                    Description
---------------------                    -----------
-?, -h, --help                           Display usage information.
* -f, --csv-file-name, --ff <PATH_NAME>  Path name of input CSV file.

Expected behaviour is that OptionException message should contain only one required option that lists all names:
Missing required option(s) [f/csv-file-name/ff].

Whoops! Sorry for this oversight. Will correct.

I've corrected this on both the 4.x and master branches.

Thank you!  Quick turnaround time!  (So do I get my name in the list of contributors? ;-))


Setting a bool value to True in ZWave config sets it to False in OZW

Home Assistant release with the issue:
Home Assistant
0.100.2
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Linux
Integration:
https://www.home-assistant.io/integrations/zwave/
Description of problem:
So I was trying to configure the Aeotec Smart Switch 6 to report only on wattage changes. At first I thought the device was faulty, or that the documentation is false. BUT... many hours of debugging revaled that changing the 90: Enables/disables parameter 91/92 to True doesn't change it to true:
2019-10-23 20:46:06.038 Info, Node014, Value::Set - COMMAND_CLASS_CONFIGURATION - Enables/disables parameter 91/92 - 90 - 1 - False
2019-10-23 20:46:06.225 Info, Node014, Received Configuration report: Parameter=90, Value=0

Only when I manually called the service like this:
Service: zwave.set_config_parameter
Service Data: {"node_id": 14, "parameter": 90, "value": "True", "size":1 }

was I able to set it to really True:
2019-10-23 20:55:07.530 Info, Node014, Value::Set - COMMAND_CLASS_CONFIGURATION - Enables/disables parameter 91/92 - 90 - 1 - True
2019-10-23 20:55:07.719 Info, Node014, Received Configuration report: Parameter=90, Value=1

and now the switch really works as expected.
I'm assuming this is bug somewhere where the True value gets converted to 1 or something.
(maybe somehwere here: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/zwave/init.py#L658, or this is already getting the wrong value from the frontend)
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Traceback (if applicable):
Additional information:

If the manual service call works OK then it's more likely a frontend issue; moving to the frontend repository


Scoped Service

With idea about some node that running a service but it only serve for a specific scope: some nodes inside a netmask (same with ip-v4 netmask)

I implemented this with same idea of Service broadcast, which will broadcast to service dests which match broadcast level:

same group
same zone2
same zone1
global


Minor typo in creation of "init.py"

Line 34: Initially, the documentation instructed the user to create a new file named "init.py".  This is referenced as "init.py" in the remainder of the document. This edit is to reflect that.

@Eo300 : Thanks for your contribution! The author, @kraigb, has been notified to review your proposed change.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/python/learn-flask-visual-studio-step-02-create-app.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

#sign-off

@gewarren For you now.

I'll merge this now, but for the future, after you sign off it will get picked up at least once/day for merge by the PRMerger human review team.

Thanks, I forgot about that and expected it to be picked up right away.


Segfault with large messages

Hello,
So, up front this is my first rust project and it's very likely I'm screwing something up. I'm getting segfaults from inside msqueue when I have a large message. Messages sized 0x1000 don't kill it, 0x10000 do.
Code, adapted from a larger project:
extern crate crossbeam;

use std::sync::Arc;
use std::thread;
use crossbeam::sync::MsQueue;

struct B {
    data : [u8; 0x10000]
}

fn new_b() -> B {
    B { data :  [0; 0x10000] }
}

impl B {
    pub fn rx(
        &mut self,
        rx : Arc<MsQueue<B>>)
    {
        loop {
            let _ = rx.pop();
        }
    }
}

fn main() {
    let b_queue : Arc<MsQueue<B>> = Arc::new(MsQueue::new());

    {
        let mut c = new_b();
        let b_queue = b_queue.clone();

        thread::spawn(move || {
            c.rx(b_queue);
        });
    }

    loop {

    }
}

$ rust-gdb -q ../target/debug/msq-crash
Reading symbols from ../target/debug/msq-crash...done.
(gdb) r
Starting program: /home/joe/rust/msqueue-crash/target/debug/msq-crash
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff6fff700 (LWP 38768)]

Thread 2 "msq-crash" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff6fff700 (LWP 38768)]
0x000055555556007f in crossbeam::sync::ms_queue::MsQueue<msq_crash::B>::pop<msq_crash::B> (self=<error reading variable: Cannot access memory at address 0x7ffff6dce4e0>)
    at /home/joe/.cargo/registry/src/github.com-1ecc6299db9ec823/crossbeam-0.2.10/src/sync/ms_queue.rs:241
241	    pub fn pop(&self) -> T {
(gdb) bt
#0  0x000055555556007f in crossbeam::sync::ms_queue::MsQueue<msq_crash::B>::pop<msq_crash::B> (self=<error reading variable: Cannot access memory at address 0x7ffff6dce4e0>)
    at /home/joe/.cargo/registry/src/github.com-1ecc6299db9ec823/crossbeam-0.2.10/src/sync/ms_queue.rs:241
#1  0x00005555555635d0 in msq_crash::B::rx (self=0x7ffff6e9e8e8, rx=Arc<crossbeam::sync::ms_queue::MsQueue<msq_crash::B>> = {...}) at /home/joe/rust/msqueue-crash/src/main.rs:21
#2  0x0000555555563d28 in msq_crash::main::{{closure}} () at /home/joe/rust/msqueue-crash/src/main.rs:35
#3  0x000055555556311b in std::panic::{{impl}}::call_once<(),closure> (self=<error reading variable: value of type `std::panic::AssertUnwindSafe<closure>' requires 65544 bytes, which is more than max-value-size>,
    _args=()) at /build/rustc-1.14.0+dfsg1/src/libstd/panic.rs:295
#4  0x000055555555c6c9 in std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure>,()> (data=0x7ffff6f5ebc8 "\000") at /build/rustc-1.14.0+dfsg1/src/libstd/panicking.rs:356
#5  0x000055555557badb in panic_unwind::__rust_maybe_catch_panic () at /build/rustc-1.14.0+dfsg1/src/libpanic_unwind/lib.rs:97
#6  0x000055555555c2fa in std::panicking::try<(),std::panic::AssertUnwindSafe<closure>> (
    f=<error reading variable: value of type `std::panic::AssertUnwindSafe<closure>' requires 65544 bytes, which is more than max-value-size>) at /build/rustc-1.14.0+dfsg1/src/libstd/panicking.rs:332
#7  0x000055555555b5a5 in std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure>,()> (
    f=<error reading variable: value of type `std::panic::AssertUnwindSafe<closure>' requires 65544 bytes, which is more than max-value-size>) at /build/rustc-1.14.0+dfsg1/src/libstd/panic.rs:351
#8  0x000055555556398d in std::thread::{{impl}}::spawn::{{closure}}<closure,()> () at /build/rustc-1.14.0+dfsg1/src/libstd/thread/mod.rs:287
#9  0x000055555555fbda in alloc::boxed::{{impl}}::call_box<(),closure> (self=0x7ffff7044c40, args=()) at /build/rustc-1.14.0+dfsg1/src/liballoc/boxed.rs:595
#10 0x00005555555721b5 in alloc::boxed::{{impl}}::call_once<(),()> () at /build/rustc-1.14.0+dfsg1/src/liballoc/boxed.rs:605
#11 std::sys_common::thread::start_thread () at /build/rustc-1.14.0+dfsg1/src/libstd/sys_common/thread.rs:21
#12 std::sys::imp::thread::{{impl}}::new::thread_start () at /build/rustc-1.14.0+dfsg1/src/libstd/sys/unix/thread.rs:84
#13 0x00007ffff79c0464 in start_thread (arg=0x7ffff6fff700) at pthread_create.c:333
#14 0x00007ffff74ec9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

This crash does not occur when I build with '--release'. I'm guessing this is related to this?
Am happy to provide any other info I can. Tested on both macOS 10.12 and debian running linux 4.8.

Are anyone able to reproduce this?

Seems like this is probably a case of blowing the stack?


Octane: Unable to create work items

Attempting to create a work item in ALM Octane results in the following errors:
Caused by: java.lang.Exception: Error accessing remote system https://myoctane: Server Error, response contents:
{
"servlet":"RestMqm",
"message":"Request failed.",
"url":"/api/shared_spaces/1001/workspaces/1003/phases",
"status":"500"
}

And:
Caused by: java.lang.Exception: Error accessing remote system https://myoctane: Conflict, response contents:
{"total_count":0,"data":[],"exceeds_total_count":false,"errors":[{"error_code":"platform.general_error","correlation_id":"zqwno2l6l95nmhw8vgxpmr28p","description":"Action upon entity of type [defect] has failed. Error: BusinessRule related entity DefectEntityToken must have a valid phase","description_translated":"Action upon entity of type [defect] has failed. Error: BusinessRule related entity DefectEntityToken must have a valid phase","properties":{},"business_error":false}]}
	... 27 more

Fixed by 37459afd548dd13ebac37a71b3f8e4bb8b17bfd2


Update README.md

Remove the known issue, because it is already fixed.
Update the retention settings for cortex since it has been changed in the release 1.9.0
Update the links of values.yaml file to point to the configuration line directly

/lgtm


Update tests to work with refactor

This will update some of the tests in order to fit the new structure created by the refactor :rocket:

There are some extra commits here, I will merge manually

Merged!


Failed to send from federation

Tried sending 5 sats from a federation to Phoenix
https://twitter.com/Stromens/status/1783211311092097076?t=Ihy_yGL3CxDWn5t8gHvQTg&s=19
mutiny-logs.txt

Okay, this looks to be an amountless invoice issue. Fedimint sends to amountless don't work, will make sure we disable that flow for it.


Ensure correctness of OLAP telemetry for multi-extractor Classifiers

Describe the solution you'd like

Double check whether flowcontrolv1.Classifier message is being populated properly in the CheckResponse for multi-label Rego rules in populateFlowLabels
Should appendNewClassifier move inside the for loop on variables so that individual LabelKeys may be tracked.
Can an error be attributed to a particular LabelKey? If not, should change the Classifiers spec and the resulting OLAP telemetry.

Additional context

The purpose of flowcontrolv1.Classifier is to piece together the Classifiers (PolicyName, ClassifierIndex, LabelKey) that matched and errors. This info is made available as attributes in OLAP telemetry.

Related: #534

After discussion with @DariaKunoichi – some more things to polish regarding classifier error-handling:

Categorize errors into different kinds and perhaps treat them slightly differently
a. context-timeout – we should just early return, without any attempt to log, etc. Perhaps bump some stats counter?
b. errors caused by "invalid input" (eg. tried to extract a header, which is missing)
c. errors caused by problem with rego itself (not sure if we can differentiate it with b)
d. "internal errors" like https://github.com/fluxninja/aperture/blob/8228d34912ddafcd9b3725dae814485a9189b271/pkg/policies/dataplane/resources/classifier/classifier.go#L109 – they signify a breakage of some internal invariants and is not caused neither by policy or traffic, users should report an issue.
Right now we treat all them the same way "Log and add to checkresponse", which is not ideal.

Double check if multi-extractor classifier can handle "partial map" – eg. some extractors succeeded but some failed. If it's not possible, it's kinda sad, as error in one extractor could basically "disable" other extractor.


CI

I want CI on this project to avoid building everything on my computer.
AC:

CI exists
CI publishes the output artifacts.

latest tag available here: https://hub.docker.com/r/glavoie84/flo-x5-mqtt/tags
ci workflow: https://github.com/glavoie/flo-x5-mqtt/actions/workflows/build-docker-image.yml


[ENH] enable default for predict in probabilistic regressors if only interval predictions are possible

This adds a default for predict if only interval/quantile predictions are possible, but not full distribution predictions.

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.08% :warning:

Comparison is base (0d8bd68) 70.91% compared to head (77f2104) 70.84%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #65      +/-   ##
==========================================
- Coverage   70.91%   70.84%   -0.08%
==========================================
  Files          93       93
  Lines        4962     4963       +1
  Branches      900      805      -95
==========================================
- Hits         3519     3516       -3
- Misses       1205     1211       +6
+ Partials      238      236       -2

Files Changed
Coverage Δ

skpro/regression/base/_base.py
65.40% <100.00%> (+1.07%)
:arrow_up:

... and 4 files with indirect coverage changes

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


Check an object exists in a response path

Hi,
I'm sure I'm just not understanding something but my test is failing and I don't know how to get the steps to check for the response value in the right way:
stepContext:
  scenario: create user success
  step:     response body path environments should be production: true nonProduction: true
testOutput:
  success:  false
  expected: production: true nonProduction: true
  actual:
    production:    true
    nonProduction: true
  response:
    statusCode: 201
    headers:
      x-powered-by:   Express
      content-type:   application/json; charset=utf-8
      content-length: 87
      etag:           W/"57-NZwST3eL7b5VW6/DN41FOw"
      date:           Fri, 30 Sep 2016 01:11:14 GMT
      connection:     close
    body:       {"email":"test.user@email.com","environments":{"production":true,"nonProduction":true}}

@bialesdaniel - you haven't mentioned the actual step you have but if you are using jsonpath (which I think you are), then do
response body path $.environments.production should be true

@seymen The step I'm trying to run is response body path environments should be production: "true" nonProduction: "true"
I'm not sure what you mean by using jsonpath. The response body I am getting is json.
I tried the response body path $.environments.production should be true but it didn't seem to work. The test still failed.

@bialesdaniel - try this:
Then response body path $.environments.production should be true
And response body path $.environments.nonProduction should be true

yah I tried that and it didn't work

How is it any different than this:https://github.com/apickli/apickli/blob/master/source/test/features/httpbin.feature#L27

My issue is resolved. I wrote my own method for the multipart/form-data post but I wasn't correctly integrating it with the rest of the apickli code. I will try to add the multipart/form-data post code when I can and do a pull request

@bialesdaniel can you share your custom step for multipart form data?


Request: Cursor should not blink while typing and deleting words

It's bothering me a little that the cursor blinks while typing or deleting, this is not how regular cursors behave.
And as an extra request, could you also expose an onDelete function which is invoked for every deleted key (similar to onType)? I would be using this to implement my own custom cursor (I'd like to change the blinking timing, but I don't think it's worth exposing more cursor configs in this library's API)

@adarah
Now you can achieve that by using hook with the new version v5.
import { useTypewriter, Cursor } from 'react-simple-typewriter'

const TypewriterComponent = () => {
  const [text, flags] = useTypewriter({
    /* your config */
  });

  const { isDelay } = flags;

  return(

      {text}
      <Cursor cursorBlinking={isDelay} />

  );
};

as for your request, I've add a new callbacks too:

onType
onDelay
onDelete


Chrome on iOS animation problem

I know that some similar issues have bean posted, but I still don't understand that if there is a solution for this. A video is worth more than a 1000 words, so here it is:
https://drive.google.com/drive/folders/1TKiq6zxBWyFB40awDTLYbLae66JEW0kK
On the left: iPhone 5S - iOS 12.4 - Chrome 76.3809.123
On the right: iPhone 7 - iOS 12.4 - Chrome 76.3809.123
I'm testing a react based web app with animate.css (3.7.2). But as you can see, the iPhone 5S handles animation with ease but the iPhone 7 is very sloppy (like no animations at all).
Both iPhone has a Reduce motion setting OFF. In Safari, both phones are working great.
Is there anything I can do about it? I saw a @media (print), (prefers-reduced-motion: reduce) css option somewhere in a post, how can I use that? Where should I put it? Will that solve the issue?
Thank you in advance!

Anybody? Am I the only one having these issues?

Please see https://github.com/daneden/animate.css/blob/master/README.md#accessibility


Bump self_cell version

See https://github.com/Voultapher/self_cell/issues/49
(If you want, I can also bump the other crates, but as this is important, I’m making a separate PR)

v0.16.1 published

Welcome. Are you using it now?

yes, i use it for osm4routing, that in turn is used for https://github.com/osrd-project/osrd


Added new directory for EEG Emotion Analysis project

EEG Emotion Analysis Project Contribution
This pull request introduces the eeg_emotion_analysis_project, a comprehensive project focused on the analysis of emotions using EEG (Electroencephalography) data.
The project includes a dataset of EEG signals labeled with corresponding emotional states such as happiness, sadness, anger, and fear.
The project provides an in-depth analysis of the EEG data using various features including:

Time domain features (mean, standard deviation, peak-to-peak amplitude, root mean square)
Frequency domain features (power spectral density, mean frequency, dominant frequency)
Time-frequency domain features (Hjorth parameters, wavelet transform, short-time Fourier transform)
Spatial domain features (Laplacian of the EEG signal, coherence between different electrodes)

This contribution aims to enhance the repository's resources for EEG emotion detection research, providing a valuable tool for training and evaluating machine learning algorithms for emotion recognition.
Please review and let me know if any changes are required.

Hi @Ahmad10Raza didn't get the contribution that you have made. As this repository requires machine learning projects along with the datasets, only dataset sharing will not work for contributions.


Toolbar: Add tests for menu in overflow menu

Feature Request
Problem description
Currently it is not clear whether we support ToolbarMenu being part of Toolbar overflow menu.
Proposed solution
Make sure that ToolbarMenu can be in an overflow menu, by adding tests. Or state that we do not support this.

fixed


Notification to stay online on mobile (or on receive screen)

Pop-up should appear when user just gets on SEND/RECEIVE screen.
Send screen https://zpl.io/brv8yQr
Receive screen https://zpl.io/V1ONkBQ

@sasha-abramovich
I think we do not need this popup on the send screen.
Ok?

We don't need the popup for sure, but we can write it on the send and receive screens. What do you think @DenisDemyanko?

@sasha-abramovich
Yes. we need to provide some informative text on the screens.
@alexandrashelenkova  Please change the design?

@sasha-abramovich @DenisDemyanko @dariatarakanova
I think popup would still work better here. If it would be only text on receive screen, then user might not even notice that, alert would get more attention.

Let's do popup for now. Later when we will have a new design we can made some changes

We don't need the popup for sure, but we can write a note on the send and receive screens. What do you think @DenisDemyanko?

we do not need a pop-up window on the send screen, because the sender does not have to be always online for a successful transaction

in the new design of send and receive we have the proper message for the user to stay online as a part of entering amount and comment. it looks like this task is obsolete. sorry for the mess.

invalid


TypeError in v0.6-rc1

reported by @rcorces
In python 3, we get an error : TypeError: unorderable types: sttr() > int()
from looper.py line 353: if submit_settings.setdefault("cores", 1) > 1:
argument seems to be getting passed as a string.
fixing it like so works:
if int(submit_settings.setdefault("cores", 1)) > 1:
                    cmd += " -P " + submit_settings["cores"]
                try:
                    if int(submit_settings["mem"]) > 1:
                        cmd += " -M " + submit_settings["mem"]

Yes thanks @rcorces @nsheff this has been addressed in the rc2


BMC package added as a wrapper to some redfish APIs and serial console.

The BMC package allows both redfish access via the gofish library and the system's ssh-tunneled serial console.
In order to avoid explicit Connect/Disconnect (or Login/Logout) methods for redfish, every method (e.g. SystemManufacturer) internally connects before accessing redfish and disconnects right before returning. That way the session (and the timeout) is automatically created for that access only, minimizing the risk of leaving it open.
Every method for redfish access needs a system index. Usually, there's a 1:1 relationship between BMC:Server but it might not be always the case, so I believe it's a good idea to allow the user to explicitly set the index, even when most of the test cases will use "0" for it.
The SSH timeout is only used for opening the ssh tunnel that is needed for the bmc ssh'd cli to call the command that opens the serial console, although it might be used in the future for direct ssh'd cli access to the bmc.
The method OpenSerialConsole accepts a custom cli command to be sent to the bmc's ssh'd cli. If no command is provided, it will try to use the right one based on the first system's manufacturer as a best effort.

@greyerof Please add usage example to https://github.com/openshift-kni/eco-goinfra/tree/main/usage
and add README information about your package before https://github.com/openshift-kni/eco-goinfra#eco-goinfra---how-to-contribute section.

@kononovn I still have to upload a separate PR for ssh (+tunneled serialconsole access) sessions to the bmc. Can I include the whole BMC's README update there, please?


Deployment to Vercel Broken

Clicking the button and using the standard Vercel prompting results in:
This Serverless Function has crashed.

Your connection is working correctly.

Vercel is working correctly.

500: INTERNAL_SERVER_ERROR
Code: FUNCTION_INVOCATION_FAILED
ID: pdx1::zf5z4-1685748399799-42778bd3fd88

It doesn't work, same like mine #5. The author just wouldn't admit.


There is no limit to the container's free, and I still see the memory size of the host, so I feel I need to increase the LXCFS to implement it

After running debug, this is still the case, there is no limit, see the container resource visibility is still the host
bash-5.0# free -m
              total        used        free      shared  buff/cache   available
Mem:           7820        4423         712           0        2685        3053
Swap:             0           0           0
bash-5.0# exit
exit
[root@master ~]# free -m
              total        used        free      shared  buff/cache   available
Mem:           7820        4012        1006          45        2802        3347
Swap:             0           0           0

Remember that there is a project called LXCFS that can achieve the visibility of resources, you can see the visibility of container resources, the author here can be optimized, I don't know if I am right, I hope to get correction

This resolves and shows the actual size of the resource size limit between the container host and the container
https://github.com/lxc/lxcfs


Documentation and Code do not work.

The very first example in the quickstart does not work> Error: CSO246 The type or namespace name 'CommunicationManagementClient' could not be found (are you missing a using directive or an assembly reference?)
Hence, nothing else in that block of code works.
I am very certain that none of this code has actually been tested in the last couple years. There are multiple issues throughout the entire quickstart code.

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

ID: e2d3d6a4-64b0-4a37-f387-696f88865a54
Version Independent ID: e02b6c38-47ab-59f7-358f-c0f225837e54
Content: Quickstart - Create and manage resources in Azure Communication Services - An Azure Communication Services quickstart
Content Source: articles/communication-services/quickstarts/create-communication-resource.md
Service: azure-communication-services
Sub-service: arm
GitHub Login: @tophpalmer
Microsoft Alias: chpalm

@laultman
Thanks for your feedback! We will investigate and update as appropriate.

I've been working with this documentation for about a week to create a simple quickstart app that works. I am a 40 year professional coder in primarily Microsoft, so I am not someone who is just passing by.
This documentation is very convoluted. You do not state in simple direct words in the quickstat examples what the purpose of the example is. You do not provide a working test case the the intended purpose. The reader must comb the documentation carefully to eek-out the tid-bits of information.
I expect, not given instruction otherwise, that a quickstart should fully illustrate a topic and actually operate as an application.
After many hours invested and actually reaching a very simple success - the "echo test 8:echo123", I believe that I am qualified to state the say that this documentation along with the accompanying examples are simple code use cases with no intent to demonstrate a complete working example.
I would term it this way as a note to the reader at the top of each page:
This code and along with samples are not intended to be a complete and working application. They are an examples of a single functional topics that must be used with other code by you to create an application.
In the fundamentals your discussion is about the internal workings of Teams and is not a fundamentals in using Teams. I appreciate the how it works, but I was expecting how to employ it. I did not get that.

@laultman We have assigned your feedback to the doc author for further review. Thank you for your patience on this matter.

After two weeks of digging in the code and documentation. If this simple statement from this link has been put into a tip message for the Teams User 1:1 Voice and Video VoIP calling samples. I would have saved days of work. Especially since the page is about Windows UWP, one would assume that it works in ANY UWP app. That is not the case!

MSAL is a multi-framework library. Confidential Client flows are not available on mobile platforms (UWP, Xamarin.iOS, and Xamarin.Android) since there is no secure way of deploying a secret there.

It probably does work somewhere - but not in UWP!


Support ValueTuple<...>

In 1.0.0-beta, typeof((short, uint)).GetFormattedName() == "ValueTuple<short, uint>". It would be nicer (more idiomatic C#) if this were to return "(short, uint)" (and similarly for ValueTuples of any arity).

Thanks for reporting this! I think you're right. And turning off this transform should be possible via an additional, dedicated formatting option. The idea is that calling the two methods without any specific options should always return in the most compact, idiomatic representation.
I'll look into this over the weekend.


ReferenceError: date is not defined

Describe the bug
Steps to reproduce:
yarn create vite (use vue)
yarn add v-calendar@next
Follow instructions to install and use v-Calendar (https://vcalendar.io/installation.html)
yarn && yarn build && yarn preview
Console:
ReferenceError: date is not defined

I tried to use Vue 3 DatePicker (https://vue3datepicker.com/) as well as FlatPickr (https://github.com/ankurk91/vue-flatpickr-component) with same error with both.
Yarn dev works flawlessy. It's only once you build that the probem occurs.
Any ideas?
Reproduction
System Info
System:
    OS: macOS 12.3
    CPU: (10) arm64 Apple M1 Max
    Memory: 7.18 GB / 64.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.0 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.3.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 99.0.4844.83
    Firefox: 98.0.1
    Safari: 15.4
  npmPackages:
    @vitejs/plugin-vue: ^2.2.0 => 2.2.4
    vite: ^2.8.0 => 2.8.6

Used Package Manager
yarn
Logs
No response
Validations

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

I'm not able to reproduce the bug on:
https://stackblitz.com/edit/vitejs-vite-dmayam
https://vitejs-vite-dmayam--4173.local.webcontainer.io/
But I can do it everytime on my local and on a netlify website:
https://staging.loftsdulacdessables.com/
Simply use the date picker on the home page and check the console log.

I'm not able to reproduce the bug on:
https://stackblitz.com/edit/vitejs-vite-dmayam
https://vitejs-vite-dmayam--4173.local.webcontainer.io/
But I can do it everytime on my local machine and on a netlify website (No longer online)
Simply use the date picker on the home page and check the console log.


feat: support agoric BLD

Adds Agoric BLD for mainnet0, a cosmos-like IBC-enabled chain

🔥 thanks!

@arirubinstein Thanks for the addition!  If you come across any lcd endpoint with agoric data going back beyond 7/6/2022, please do let me know now or in the future.
Released on the website today.


Language toggle for doc sections

This implements the idea in #886 to make the original documentation string of the docs more easily accessible from within the translated docs. It allows for users to toggle each doc section between their selected language, and the original English version. While some prior art has enabled the original-translation-toggle per sentence, it's very hard to do so for the electron docs, because of how the documentation and its translations are structured.
All feedback is, of course, welcome, but critiques on the ux would be especially helpful.

Note: this PR is dependent on https://github.com/electron/electron-i18n/pull/222, so PR deployment is not possible right now.
For example: https://electron-website-pr-1053.herokuapp.com/docs/tutorial/updates?lang=zh-CN

Yay it's working with the latest electron-i18n release!  🎉🍻🍾

🎉


Intersection of a linestring passing through a polygon produces a multilinestring

Expected behavior and actual behavior.
Intersection of a linestring passing through a polygon should produce a single linestring. But it returns a multilinestring with the two linestrings that are outside the polygon instead of the single linestring that's inside the polygon.
Steps to reproduce the problem.
import matplotlib.pyplot as plt
from shapely import from_wkt

line = "LINESTRING<PHONE_NUMBER>941702 6090140.560580588,<PHONE_NUMBER>770195 6090151.846915013)"
polygon = "POLYGON ((922820.7212855534 6090150.592104633,<PHONE_NUMBER>20424 6090150.291979982,<PHONE_NUMBER>950204 6090150.053230791,<PHONE_NUMBER>99041 6090149.283807769,<PHONE_NUMBER>790132 6090148.692722978,<PHONE_NUMBER>2764 6090147.929088174,<PHONE_NUMBER>979327 6090147.525506645,<PHONE_NUMBER>417138 6090147.828043146,<PHONE_NUMBER>891327 6090148.240307301,<PHONE_NUMBER>549626 6090148.650642028,<PHONE_NUMBER>088496 6090149.534616105,<PHONE_NUMBER>784336 6090150.065289824,<PHONE_NUMBER>855535 6090150.592104633,<PHONE_NUMBER>855534 6090150.592104633))"

l = from_wkt(line)
p = from_wkt(polygon)

x, y = p.exterior.coords.xy
plt.plot(x, y)
x, y = l.coords.xy
plt.plot(x, y)
plt.show()

x,y= l.intersection(p).geoms[0].coords.xy
plt.plot(x, y)
x,y= l.intersection(p).geoms[1].coords.xy
plt.plot(x, y)
x, y = p.exterior.coords.xy
plt.plot(x, y, color="black")
plt.show()

Operating system
Ubuntu 22.04.1 LTS
Shapely version and provenance
2.0.1 installed from PyPI using pip

IMHO, in this case a simple check like
p.convex_hull.contains(l.intersection(p))

should be True instead of False.

Your polygon is not valid (has a self-intersection that isn't visible in the plot); that may produce unexpected behavior:
import shapely
>>> shapely.is_valid(p)
False
>>> shapely.is_valid_reason(p)
'Self-intersection[922820.721285554 6090150.59210463]'

Unfortunately making the polygon valid produces a geometry collection, from which you need to extract the polygon part(s), which then produce the expected output:
>>> shapely.make_valid(p)
<GEOMETRYCOLLECTION (POLYGON ((922822.28 6090150.292, 922823.128 6090150.053...>
>>> parts = shapely.get_parts(shapely.make_valid(p))
>>> parts
array([<POLYGON ((922822.28 6090150.292, 922823.128 6090150.053, 922823.966 6090149...>,
       <LINESTRING (922820.721 6090150.592, 922820.721 6090150.592)>],
      dtype=object)
>>> p2 = parts[shapely.get_type_id(parts)==3][0] # not robust; for example only taking first polygon
>>> shapely.intersection(p2, l)
<LINESTRING (922822.014 6090147.706, 922822.733 6090150.165)>

You can also use buffer(0) (a similar trick with a somewhat different underlying algorithm) to get a single valid polygon:
>>> shapely.buffer(p, 0)
<POLYGON ((922820.721 6090150.592, 922822.28 6090150.292, 922823.128 6090150...>

I see thanks for the help!


Syntax for exporting extensions

What if we can clean up the syntax for exporting extensions...
By making the interface simpler for doing this work we can remove some overhead from the programmers brain from having to remember placing the extension in the data segment.
Also from unnecessary typing.
Something like the following:
#include <phpcpp.h>

Php::Value multiply(Php::Parameters &params)
{
	return params[0] * params[1];
}

START_EXPORT_OF_EXTENSION("mathPlugin","1.0");

extension.add("multiply", multiply);

SUBMIT();

Which can be done by simply augmenting the library header with the following macros:
/**
 * Macro used to add improved syntax for initializing extension exportation
 * to the php engine
 */
#define START_EXPORT_OF_EXTENSION(name, version)            \
extern "C"                                                  \
{                                                           \
	PHPCPP_EXPORT void *get_module()                        \
	{                                                       \
		static Php::Extension extension{name, version};     \

/**
 * Macro used to add improved syntax for finalizing the exportation
 */
#define SUBMIT()                                            \
		return extension;                                   \
	}                                                       \
}

This is a big no-go.
I don't like the C++ preprocessor and macro's. One of the design goals of the PHP-CPP library was to get rid of all the macro's that the Zend API uses, and only use straightforward real C++ code that every C++ programmer understands. If we start using macro's, we lose exactly that.
Bjarne Stroustrup also dislikes the preprocessor: http://www.stroustrup.com/bs_faq2.html#macro


Same problem

Hi,
I'd really like to use your plugin, but I got the same problem as the other users... the process stops after "validating the credit card information".
Could you please bugfix?
Thanks in advance!

I debugged the plugin and found out that we are just using the wrong values.
See stripe testing docs credit card test numbers:
https://stripe.com/docs/testing

the same problem
i have checked up some card numbers from the link above. No changes. Still validating the credit card information and next nothing.


create a line sorting script

Sorts the lines in a file alphabetically. For example, the following file:
c
ab
aa
b
a

would turn into:
a
aa
ab
b
c

Hi, I would like to take up this issue. Could it be assigned to me?


[Bug]: Empty blocks if not all validators validate parachains

Bug Summary
Error occurs when number of parachain validators is less than number of all validators
Bug Description
It is observed that when KAGOME participates in parachains consensus in Kusama it creates blocks with no parachain inherents (Candidate backed/included).
The reason is that KAGOME implements Grid and cluster topologies, that distribute manifests only among parachain validators.
It is not clear how Polkadot-SDK validators create blocks with parachain inherents under the same circumstances
Steps to Reproduce
0001-parachains-pvf.toml.zip

unpack
run zombienet-macos-arm64 spawn -p native 0001-parachains-pvf.toml
observe that KAGOME validator's blocks do not have parachain inherents

Effects of the Bug
Slow down in parachains block finalization as their manifests cannot be included in time
Expected Behavior
No response
System Information
Polkadot-SDK 1.13
KAGOME – latest master
Additional Context
No response

implemented in #2180


"exchange full" message from CNI plugin

Seen on Kubernetes Slack:
Mar 12 19:19:54 ip-172-20-47-210 kubelet[2526]: E0312 19:19:54.253474    2526 kuberuntime_manager.go:636]
createPodSandbox for pod "foo(a1c7d76a-261c-11e8-80e1-0a918743583e)" failed:
rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "foo" network:
unable to set master of vethwepl3c8c481: exchange full

Speculating that maybe there were too many connections on the bridge - default limit is 1024.

Indeed, the kernel returns EXFULL (="exchange full") err when creating a bridge port if the limit of ports has been reached: https://github.com/torvalds/linux/blob/v4.16/net/bridge/br_if.c#L342
However, it seems that the limit is hard.

I'm seeing this issue on K8s 1.8.7 and Weave 2.2.1.
The problem node i 172-20-109-25, all commands are run against it.
  k exec -it weave-net-tc49l -n kube-system -c weave -- ./weave --local status ipam
  5a:66:61:f2:00:41(ip-172-20-109-25.ec2.internal)   458752 IPs (21.9% of total) (48 active)
  ea:50:6e:7d:06:83(ip-172-20-45-221.ec2.internal)   262144 IPs (12.5% of total)
  92:6a:33:fd:10:c9(ip-172-20-125-219.ec2.internal)   196560 IPs (09.4% of total)
  2a:1b:26:03:49:5c(ip-172-20-43-135.ec2.internal)   262144 IPs (12.5% of total)
  e2:1d:6e:98:b8:45(ip-172-20-76-252.ec2.internal)   131072 IPs (06.2% of total)
  d2:fa:90:d6:da:e3(ip-172-20-38-112.ec2.internal)   131072 IPs (06.2% of total)
  5a:db:89:6f:7f:a7(ip-172-20-105-71.ec2.internal)   131072 IPs (06.2% of total)
  aa:36:ba:ab:9f:33(ip-172-20-37-62.ec2.internal)   262144 IPs (12.5% of total)
  e2:5a:50:54:bb:2a(ip-172-20-74-197.ec2.internal)   131120 IPs (06.3% of total)
  12:75:51:5b:42:3f(ip-172-20-73-220.ec2.internal)   131072 IPs (06.2% of total)

  $ sudo docker ps | wc -l && ip a | grep veth | wc -l
  59
  1023

From kubelet on 172-20-109-25: May 14 13:28:58 ip-172-20-109-25 kubelet[891]: E0514 13:28:58.615230     891 cni.go:301] Error adding network: attaching veth "vethwepl6576d79" to "weave": exchange full
$ ls /sys/devices/virtual/net/weave/brif/ | wc -l
1022


Look into why new structures from Reveal are not showing up

Ensure that new points from Reveal via Nifi are received and processed correctly.
The data comes in this format:
{
    "id": "71e2d011-a498-46d6-8986-cd15e5cf1d6f",
    "parent_id": "3537",
    "status": "Pending Review",
    "geometry": "{\"type\":\"Point\",\"coordinates\":[32.6446266608928,-14.1567959784487]}",
    "server_version":<PHONE_NUMBER>599,
    "task_id": "d0fd193d-bf88-4cdd-abbe-8683da12031b",
    "task_spray_operator": "demomti",
    "task_status": "Ready",
    "task_business_status": "Not Visited",
    "task_execution_start_date": "",
    "task_execution_end_date": "",
    "task_server_version":<PHONE_NUMBER>347
}

I'm going to close this issue.
Some final notes:

Nifi uses the "task server version" field from OpenSRP tasks to determine if a task has been updated or not
Nifi periodically queries OpenSRP for updated tasks, and syncs them if found
Nifi periodically sends synced tasks to mSpray

There were some problems with the above, which have since been solved (or so we hope):

The reveal app was not setting a new task server version when the spray status (aka task business status) field on a task changed.  Nifi was thus unable to know that a task status had been updated.  This was fixed
The reveal Nifi deployment was unstable and couldn't reliable sync everything all the time.  This has hopefully been fixed now


Permisson denied error even in root mode

I'm root user in termux but I can't execute fluxion.sh with this error:
127|on5xelte:/data/data/com.termux/files/home/hacktronian/Fluxion # ./fluxion.sh /system/bin/sh: ./fluxion.sh: can't execute: Permission denied

Fluxion does not work on android.


SunEditor: Dialog and positioning fixes

As discussed on Discord when adding an image the position is off because of..
/* Ensure the editor can receive input in dialog */
body .sun-editor .se-wrapper .se-wrapper-inner {
  position:relative;
  z-index: 9999;
}

Submitted fix but re-opening so it can be tested by others.

final fix:
.sun-editor .se-wrapper {
   z-index: 9999 !important;
}


Update README.rst

Add link to license

Coverage remained the same at 91.525% when pulling d59bba3c995689584b4baf7e862f20ec4455bc5c on alanyee:master into 7aba41ea14cd6d6c9b13abf8549bce9ceecd0e15 on yahoo:master.


Fix Flaky-test: MessagePublishBufferThrottleTest

Fixed: https://github.com/apache/pulsar/issues/9368
Looks like a common seen async issue.

@codelipenghui, PTAL, seems you are the original author of the test.

@codelipenghui, PTAL, seems you are the original author of the test.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


Explore using Google's Container Service & Docker Registry

per this article

closing this issue since it's really just a duplicate of issue #20


feat: add new newsletter view

This PR introduces asyncapi.com/newsletter page to make it easy to link to a location where people can subscribe to Newsletter.
We had this page in the past but it was lost during change from Hugo to Next.js
Related issue(s)
See also #33`. The `See also #33` option will not automatically close the issue after the PR merge. -->

Ok for me, but I think we should change the design of this page because we are using the same colors for newsletter as is on the home page. @mcturco Could you check https://deploy-preview-644--asyncapi-website.netlify.app/newsletter and suggest changes, or should we leave it as it is?

Hmm yeah I agree with @magicmatatjahu here. I know the idea was to be a quick solution, but it looks a little bit too "copy and paste" for me, especially because there are no other sections on this new page to break up the dark background.
Instead, I would suggest that we remove the dark background (keep it white), change the Heading & Paragraph components to use their default textColor and then just make sure that the height of the section is at least 90vh so that it doesn't show white space below the footer on taller screens.

event though #designismypassion this time I will agree with you 😆

but it looks a little bit too "copy and paste" for me

who said it wasn't 🤣
I literally had to google what vh is and what you want me to do 😄
Let me know what you think. When I did some tests on my different screens, vh (viewport hight 😉 ) is better set to 80 rather than 90
tbh, I can also remove the footer entirely, I think we can agree that on such a specific view, we do not need it 😄

@derberg I fixed for you the footer 😘  https://deploy-preview-644--asyncapi-website.netlify.app/newsletter

@derberg Ok I see that documentation pages are broken, I will check this.

@magicmatatjahu sometimes you are so kind ❤
@mcturco how does it look like now?

you're welcome :) but still some views don't work, for example sticky navbar only works up to a certain height. I need to fix some global styles to make everything work as it should, give me some time.

@mcturco how does it look like now?

Yesss looks way better, thank you for making those changes!
Also side note - and we don't have to address this in this PR: Do all the forms on the website do this after submit? (See screenshot below) I think it would be better if we kept the submission notification on the same screen without redirecting to a netlify page. I could submit a separate issue for this

@mcturco definitely need to be discussed on separate issue, not sure if it can be changed, Netlify Forms are used for it

/rtm

@KhudaDad414 something ain't right, have a look at https://github.com/asyncapi/website/pull/644#issuecomment-1088862267. It was for sure up to date, and ready to merge

@derberg yeah this was happening to me a lot yesterday and was wondering why that was happening

@derberg  on it. please keep this branch https://github.com/derberg/website-asyncapi/tree/add-newslinkpage for now so I can do some testing :)


Content block intro needs a type token change

The problem
Previously we requested the intro paragraph section of content block to be changed from expressive-heading-03 to expressive-paragraph-01. This was needed because the line-height for heading-03 was too tight when first built.
However, the IDL and Carbon team have now decided to update line heights across type sets so that all line-heights will be divisible by 4. As a result, heading-03 will not have such tight line-height and will be a better overall type scale for this layout.

The solution
Please replace the expressive-paragraph-01 type token with expressive-heading-03 across all content blocks that use it.
Additional information

See this issue #1600 for the old request.
Lila has reviewed and approved this revert change.

@RobertaJHahn This change will apply to patterns for both Learn and Solutions. I will not log another issue from the design QA of those patterns (content block - segmented and leadspace-block) because it is documented here.


Strongly-typed resources

While investigating whether I could replace my own resource wrappers with wil I noticed that there aren't any specific strongly-typed wrappers. Although many wrappers are indeed incompatible due to different underlying policy template instantiations, stuff like process, thread, token or timer queue handles are all interchangeable. Is this something that was deliberately decided against or is seen as adding no value?

I can't speak for anyone else, but I suspect the answer is that it wouldn't add much value. The types are mostly used for storage, so beyond initialization, the type isn't very important, nor would it give you any safety since the underlying type is the same in all cases.
The obvious asterisk is testing for validity (IIRC some pseudo handles use -1, unfortunately), but that's a problem at declaration, not usage, so a well named typedef would be just as helpful as a distinct type.

I agree with @dunhor. Even if you had separate types unique_process_handle and unique_thread_handle, there would be no way of preventing you from using the wrong handle:
wil::unique_process_handle process{ ... };
SuspendThread(process.get()); // no way to prevent this

If it makes you feel better, you could write
using unique_process_handle = unique_handle;
using unique_thread_handle = unique_handle;

but be honest with yourself and understand that you are not getting any type safety.

We also prefer strongly typed resources, so decided to go further and wrap low-level unique_handle wrappers again into domain classes, like:
namespace windows {
class Thread {
   // Establish and check `unique_handle` invariant via factory method, so `Thread` always has correct handle.

  Thread(Thread &&) ...

  DWORD Suspend() const noexcept {
      return SuspendThread(handle_.get());
  }

private:
    Thread() ...
    unique_handle handle_;
}
}

Pros are:

Static type safety with all the goodies: impossible to use incompatible handle in a wrong place, better IntelliSense support due to known scope, easier to guess semantic (consider Process child vs unique_handle child_process), better static analysis support with custom rules on domain classes usage and more.
If we make methods virtual, mocking and testing becomes much more easier (certainly, with some runtime cost).
Easy to find and extend APIs, as each OS resource represented via single wrapper in a known place.
Don't need to wait till WIL adds new shiny wrapper or extension, hence WIL still is thin and lightweight :).

Cons are:

Need to write wrapper for every single method consumers are going to use. If unique_handle is exposed, static type safety is effectively lost.
Adding new method leads to recompilation of header dependents graph.

I'm going to close this as won't-fix. Feel free to send a PR for wrappers on top of unique_thread or unique_key that provide resource-specific behavior. Consider putting those in a different header other than the lower-level resource.h so they can be optionally included.