Using wrong gcc (not winlibs) is not detected on Windows

Nuitka-Options: Used command line options: --onefile main.py
Nuitka: Starting Python compilation with Nuitka '2.1rc6' on Python '3.11' commercial grade 'not installed'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: gcc (gcc 13.2.0).
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [module.main.o] Error 3
scons: *** [module.charset_normalizer.api.o] Error 3
scons: *** [module.charset_normalizer.o] Error 3
scons: *** [module.certifi.core.o] Error 3
scons: *** [module.charset_normalizer.cd.o] Error 3
scons: *** [module.charset_normalizer.constant.o] Error 3
scons: *** [module.charset_normalizer.models.o] Error 3
scons: *** [module.charset_normalizer.utils.o] Error 3
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [module.charset_normalizer.version.o] Error 3
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [module.colorist.o] Error 3
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [module.colorist.constants.ansi.o] Error 3
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [module.charset_normalizer.legacy.o] Error 3
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [__helpers.o] Error 3
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [__constants.o] Error 3
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [__loader.o] Error 3
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [module.certifi.o] Error 3
FATAL: Failed unexpectedly in Scons C backend compilation.
Nuitka:WARNING:     Complex topic! More information can be found at
Nuitka:WARNING: https://nuitka.net/info/scons-backend-failure.html
Nuitka-Reports: Compilation crash report written to file 'nuitka-crash-report.xml'.

can you upgrade your nuitka version and try again?

I have the same error on 2.0.5 with mingw64 13.0.2.

On 2.0.6 on anaconda and minGW64 13.0.2 same:
`(base) c:\My_Documents\Work\alorAPI_setkaNG>python -m nuitka --onefile --mingw64 --lto=yes setkaNG311.py
Nuitka-Options: Used command line options: --onefile --mingw64 --lto=yes setkaNG311.py
Nuitka: Starting Python compilation with Nuitka '2.0.6' on Python '3.11' commercial grade 'not installed'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'pandas'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'numpy'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'matplotlib'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'mpl_toolkits'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'scipy'.
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:16')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:17')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:18')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:18')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:19')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:19')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:20')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:33')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:257')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: options-nanny: Using module 'numba' (version 0.59.0) with incomplete support due to untrue condition 'not use_numba and standalone': Numba is not yet fully working with
Nuitka-Plugins:WARNING: Nuitka standalone, try to use '--noinclude-numba-mode=nofollow', but it may fail.
Nuitka-Plugins:WARNING: options-nanny: Module has parameter: Numba JIT is disabled by default in standalone mode, make a choice explicit with '--module-parameter=numba-disable-jit=yes|no'
Nuitka-Plugins:anti-bloat: Not including 'PIL.ImageQt' automatically in order to avoid bloat, but this may cause: PIL will not be able to create Qt image objects.
Nuitka-Plugins:anti-bloat: Not including 'qtpy' automatically in order to avoid bloat, but this may cause: pandas will not be able to use Qt for clipboard interaction.
Nuitka-Plugins:anti-bloat: Not including 'PyQt5' automatically in order to avoid bloat, but this may cause: pandas will not be able to use Qt for clipboard interaction.
Nuitka-Plugins:matplotlib: Using configuration file or default backend 'QtAgg'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: gcc (gcc 13.2.0).
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [module.AlorPy.Config.o] Error<PHONE_NUMBER>
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [__helpers.o] Error<PHONE_NUMBER>
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [__loader.o] Error<PHONE_NUMBER>
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [module.AlorPy.o] Error<PHONE_NUMBER>
scons: *** [module.AlorPy.AlorPy.o] Error<PHONE_NUMBER>
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [__constants.o] Error<PHONE_NUMBER>
Nuitka-Reports: Compilation report written to file 'nuitka-crash-report.xml'.
Nuitka-Reports: Compilation crash report written to file 'nuitka-crash-report.xml'.`
nuitka-crash-report.zip

I have the same error on 2.0.6 with mingw64 13.2.0
It is also a Windows 11 computer. Computers of different brands use the same version and command to package the same code. If it fails, this error will appear. For example, I can package normally using a Lenovo computer, but this error will appear on HP computers.

Can anybody with google foo try to find out what std::filesystem::__cxx11::filesystem_error causes there are in gcc? I was suspecting disc space, it could also be low memory. Try also with --low-memory if you can and with gcc, if that changes something, maybe a out of memory situation happened. However, for multiple modules the same gcc error, is really bizarre. This being reproducible kills me. I am doing it myself on Windows 11, just not a fresh install.
Maybe Windows 11 has changed in a way that corrupts gcc?

Can anybody with google foo try to find out what std::filesystem::__cxx11::filesystem_error causes there are in gcc? I was suspecting disc space, it could also be low memory. Try also with --low-memory if you can and with gcc, if that changes something, maybe a out of memory situation happened. However, for multiple modules the same gcc error, is really bizarre. This being reproducible kills me. I am doing it myself on Windows 11, just not a fresh install.
Maybe Windows 11 has changed in a way that corrupts gcc?

On another Windows 11 system, I installed gcc and python and other environments in the same way. The code that needs to be packaged is exactly the same, and it can be packaged normally on that computer. Using --low-memory on this computer also fails to package, and the same error is reported, but the number of std::filesystem::__cxx11::filesystem_error errors has been reduced a lot. I will use MSVC to try packaging later.

Low memory will not compile C files in paralell which lowers the memory usage and makes the compilation slower, so I think we can rule that out.

Can you also try --disable-ccache with gcc, that's another shot.

I am updated fully except for KB5034848 with Windows 11, I will try and update, to see if that makes the issue affect me too. This version of gcc has been used with a lot of success for a lot of time, and this doesn't seem to be code dependent at all, kind of like a hello world issue there. From winlibs, the word "filesystem_error" is not in their issue tracker, and the only newer package that we can use updated the contained clang, that we don't really use all that much, certainly not when it crashes for you.
I have to use a Lenovo laptop and not see it, but do we think that HP broke something there? Is this something AV checking could cause?

Can you also try --disable-ccache with gcc, that's another shot.

After I added --disable-ccache, I downloaded the Dependency Walker tool according to the prompts. At this time, I was able to package the results. Thank you.

So, this could be ccache.exe that is having the issue, we download that one too. I wonder if it had cached those things and just put them up again.

So that's a ccache issue, apparently with no solution yet or what https://github.com/ccache/ccache/issues/1409

I am assuming that Anaconda has a bad ccache release, the one that should be used is the one from winlibs, and that one is this: "C:\Users\kayha\AppData\Local\Nuitka\Nuitka\Cache\downloads\gcc\x86_64\13.2.0-16.0.6-11.0.1-msvcrt-r1\mingw64\bin\ccache.exe" --version
ccache version 4.8.2
I am assuming you are getting 4.9.x used, and that one doesn't work, and it's coming from Anaconda, cannot trust outsiders to even deploy tools good enough to make a version output, maybe that's what it is. I am removing guessing of ccache paths for Win32, since we only accept the winlibs gcc anyway.

If you were to provide output of --show-scons with no disabling of ccache, we could tell if you are affected. Nuitka also downloads 4.6 if the ccache is not found in PATH which however it would have to be. For you to use 4.9 would mean that it's on PATH, probably due to Anaconda bin being there before we put the winlibs gcc, but for me it's first path element, so that would have to pickup ccache.exe from there.
So, the code I am removing for factory now, should just not have any effect, for as long as you are using the downloaded gcc, which it might be bad at enforcing maybe.

Can you also try --disable-ccache with gcc, that's another shot.
this helped me too, the exe file is generated and working
but there are errors "The system cannot find the path specified."
nuitka-crash-report is not generated

`Nuitka-Plugins:anti-bloat: Not including 'PIL.ImageQt' automatically in order to avoid bloat, but this may cause: PIL will not be able to create Qt image objects.
Nuitka-Plugins:anti-bloat: Not including 'qtpy' automatically in order to avoid bloat, but this may cause: pandas will not be able to use Qt for clipboard interaction.
Nuitka-Plugins:anti-bloat: Not including 'PyQt5' automatically in order to avoid bloat, but this may cause: pandas will not be able to use Qt for clipboard interaction.
Nuitka-Plugins:matplotlib: Using configuration file or default backend 'QtAgg'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: gcc (gcc 13.2.0).
Nuitka-Scons: Backend linking program with 2102 files (no progress information available for this stage).
Nuitka-Scons: Running 'gcc -o "C:\MY_DOC~1\Work\ALORAP~1\SETKAN~1.DIS\setkaNG311_20.exe" -flto=6 -fuse-linker-plugin -fpartial-inlining -freorder-functions -Wl,--exclude-all-symbols
Nuitka-Scons: -Wl,--out-implib,.\import.lib -municode -O3 -s -Wl,--enable-auto-import -static-libgcc -Wl,--stack,9863168<EMAIL_ADDRESS>-LC:\PROGRA~3\ANACON~1\libs -lm -lpython311' took
Nuitka-Scons: 4333.25 seconds
The system cannot find the path specified.
The system cannot find the path specified.
. . . . .
Nuitka-Plugins:data-files: Included data file 'botocore\cacert.pem' due to package data for 'botocore'.
Nuitka-Plugins:data-files: Included 1656 data files due to package data directory 'data' for 'botocore'.
Nuitka-Plugins:data-files: Included data file 'certifi\cacert.pem' due to package data for 'certifi'.
Nuitka-Plugins:matplotlib: Included 182 data files due to package data for 'matplotlib.
Nuitka-Plugins:matplotlib: Included data file 'matplotlib\mpl-data\matplotlibrc' due to updated matplotlib config file with backend to use.
Nuitka-Plugins:data-files: Included data file 'pandas\io\formats\templates\html.tpl' due to package data directory 'templates' for 'pandas.io.formats'.
Nuitka-Plugins:data-files: Included data file 'pandas\io\formats\templates\html_style.tpl' due to package data directory 'templates' for 'pandas.io.formats'.
Nuitka-Plugins:data-files: Included data file 'pandas\io\formats\templates\html_table.tpl' due to package data directory 'templates' for 'pandas.io.formats'.
Nuitka-Plugins:data-files: Included data file 'pandas\io\formats\templates\latex.tpl' due to package data directory 'templates' for 'pandas.io.formats'.
Nuitka-Plugins:data-files: Included data file 'pandas\io\formats\templates\latex_longtable.tpl' due to package data directory 'templates' for 'pandas.io.formats'.
Nuitka-Plugins:data-files: Included data file 'pandas\io\formats\templates\latex_table.tpl' due to package data directory 'templates' for 'pandas.io.formats'.
Nuitka-Plugins:data-files: Included data file 'pandas\io\formats\templates\string.tpl' due to package data directory 'templates' for 'pandas.io.formats'.
Nuitka-Plugins:data-files: Included 603 data files due to package data directory 'zoneinfo' for 'pytz'.
Nuitka-Plugins:data-files: Included data file 'scipy\stats_sobol_direction_numbers.npz' due to package data for 'scipy'.
Nuitka-Plugins:dll-files: Found 1 file DLLs from llvmlite.binding.ffi installation.
Nuitka-Postprocessing: Creating single file from dist folder, this may take a while.
Nuitka-Onefile: Running bootstrap binary compilation via Scons.
Nuitka-Scons: Onefile C compiler: gcc (gcc 13.2.0).
Nuitka-Scons: Onefile linking program with 1 files (no progress information available for this stage).
The system cannot find the path specified.
The system cannot find the path specified.
Nuitka-Onefile: Using compression for onefile payload.
Nuitka-Onefile: Onefile payload compression ratio (22.00%) size 659570937 to 145072804.
Nuitka-Onefile: Keeping onefile build directory 'setkaNG311_20.onefile-build'.
Nuitka: Keeping dist folder 'setkaNG311_20.dist' for inspection, no need to use it.
Nuitka: Keeping build directory 'setkaNG311_20.build'.
Nuitka: Successfully created 'setkaNG311_20.exe'.`

The missing is likely for make.exe and indicative of you not using the downloaded gcc, but a randomly different one. I saw a report like that before on Discord, where Nuitka is saying it would enforce it, but then doesn't actually enforce it. Unfortunately, because I am accepting low quality reports, nobody has provided the --version output that would reveal it.

Unfortunately, because I am accepting low quality reports, nobody has provided the --version output that would reveal it.

`winlibs personal build version gcc-13.2.0-llvm-17.0.6-mingw-w64msvcrt-11.0.1-r5
This is the winlibs Intel/AMD 64-bit standalone build of:

GCC 13.2.0
GDB 14.1
LLVM/Clang/LLD/LLDB 17.0.6
MinGW-w64 11.0.1 (linked with msvcrt)
GNU Binutils 2.42
GNU Make 4.4.1
PExports 0.47
dos2unix 7.5.2
Yasm 1.3.0
NASM 2.16.01
JWasm 2.12pre
ccache version 4.9
CMake 3.28.2
ninja 1.11.1.git.kitware.jobserver-1
Doxygen 1.10.0

Thread model: posix
Runtime library: MSVCRT
This build was compiled with GCC 13.2.0 and packaged on 2024-02-03.
Please check out http://winlibs.com/ for the latest personal build.`

Well, there is zero chance that a random gcc combination works. I deliberately update it only in the relatively rare circumstances that no new binutils, GCC, ccache apparently, or clang issues exist.
It would appear that your ccache.exe cannot do --version output even. If so, report that to winlibs, it will prevent Nuitka from updating winlibs.
What python -m nuitka --version would have output, is the path to the compiler and that would let me know, that it's essentially an unsupported gcc. I changed my stance from allowing newer versions over time, since LTO and Windows in general are so fragile, to the point, where this gcc of yours should be ignored in favor of a downloaded gcc, independent of versions.
I realize, I lost a bunch of time by accepting that the original poster didn't fill out the issue template. That would have immediately gotten me on track. Instead, I guessed it might be a disk full fluke based on the lack of information. I got to not waste my time on incomplete reports, and instead ask for better ones.
Here is my template text, that will allow me to find this one for deleting later on:

In the template, we have made it clear, that not filling out the issue template is not acceptable. I am closing this kind of report as invalid. The main reason is that we do not want to be left guessing. For you it's easy to erase the issue template and expect us to ask you questions only as necessary, but we cannot do that. We would much rather wait for you to create a new report, fill out the template, or wait for somebody with the necessary skill to do it.
In short: No issue template, no fun. Therefore we are  likely just deleting the issue, as it serves as a bad example and detraction for searches.  And even worse, it might keep good reporters from reporting as is this "already known."
The real bug is that if detected as a GCC that is not ours, we need to reject outside gcc findings on Windows.

If you were to provide output of --show-scons with no disabling of ccache, we could tell if you are affected. Nuitka also downloads 4.6 if the ccache is not found in PATH which however it would have to be. For you to use 4.9 would mean that it's on PATH, probably due to Anaconda bin being there before we put the winlibs gcc, but for me it's first path element, so that would have to pickup ccache.exe from there.
So, the code I am removing for factory now, should just not have any effect, for as long as you are using the downloaded gcc, which it might be bad at enforcing maybe.

`(base) c:\My_Documents\Work\alorAPI_setkaNG>python -m nuitka --onefile --mingw64 --lto=yes --show-scons setka_dyn_NG311.py
Nuitka-Options: Used command line options: --onefile --mingw64 --lto=yes --show-scons setka_dyn_NG311.py
Nuitka: Starting Python compilation with Nuitka '2.0.6' on Python '3.11' commercial grade 'not installed'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'pandas'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'numpy'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'matplotlib'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'mpl_toolkits'.
Nuitka-Plugins:delvewheel: Detected usage of 'delvewheel' version '1.5.2' in module 'scipy'.
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:16')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:17')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:18')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:18')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:19')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:19')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core._numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:20')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core.numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:33')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: anti-bloat: Undesirable import of 'numba' in 'pandas.core.numba.extensions' (at 'C:\ProgramData\anaconda3\Lib\site-packages\pandas\core_numba\extensions.py:257')
Nuitka-Plugins:WARNING: encountered. It may slow down compilation.
Nuitka-Plugins:WARNING:     Complex topic! More information can be found at https://nuitka.net/info/unwanted-module.html
Nuitka-Plugins:WARNING: options-nanny: Using module 'numba' (version 0.59.0) with incomplete support due to untrue condition 'not use_numba and standalone': Numba is not yet fully working with
Nuitka-Plugins:WARNING: Nuitka standalone, try to use '--noinclude-numba-mode=nofollow', but it may fail.
Nuitka-Plugins:WARNING: options-nanny: Module has parameter: Numba JIT is disabled by default in standalone mode, make a choice explicit with '--module-parameter=numba-disable-jit=yes|no'
Nuitka-Plugins:anti-bloat: Not including 'PIL.ImageQt' automatically in order to avoid bloat, but this may cause: PIL will not be able to create Qt image objects.
Nuitka-Plugins:anti-bloat: Not including 'qtpy' automatically in order to avoid bloat, but this may cause: pandas will not be able to use Qt for clipboard interaction.
Nuitka-Plugins:anti-bloat: Not including 'PyQt5' automatically in order to avoid bloat, but this may cause: pandas will not be able to use Qt for clipboard interaction.
Nuitka-Plugins:matplotlib: Using configuration file or default backend 'QtAgg'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Scons command: C:\ProgramData\anaconda3\python.exe -W ignore C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\bin\scons.py -f
Nuitka-Scons: C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\BACKEN~1.SCO --jobs 6 --warn=no-deprecated --no-site-dir --debug=stacktrace
Nuitka-Scons: result_name=C:\MY_DOC~1\Work\ALORAP~1\SETKA~1.DIS\setka_dyn_NG311 source_dir=. nuitka_python=false debug_mode=false debugger_mode=false python_debug=false module_mode=false
Nuitka-Scons: full_compat=false experimental= trace_mode=false file_reference_mode=runtime module_count=2822 result_exe=C:\MY_DOC~1\Work\ALORAP~1\SETKA~1.DIS\setka_dyn_NG311.exe
Nuitka-Scons: standalone_mode=true onefile_mode=true onefile_temp_mode=true frozen_modules=154 python_sysflag_no_site=true nuitka_src=C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build
Nuitka-Scons: python_version=3.11 python_prefix=C:\ProgramData\anaconda3 no_deployment= show_scons=true mingw_mode=true lto_mode=yes noelf_mode=true anaconda_python=true
Nuitka-Scons: cpp_defines=NUITKA_PLUGIN_MULTIPROCESSING_ENABLED=1 target_arch=x86_64
scons: Reading SConscript files ...
Nuitka-Scons: CC 'C:\MinGW\bin\gcc.exe' version check gives (13, 2, 0)
Nuitka-Scons: Initial CC: 'gcc'
Nuitka-Scons: Initial CCVERSION: (13, 2, 0)
Nuitka-Scons: Checking usability of binary 'C:\MinGW\bin\gcc.exe' from environment 'gcc'.
Scons: Compiler used C:\MinGW\bin\gcc.exe
Nuitka-Scons: Backend C compiler: gcc (gcc 13.2.0).
Nuitka-Scons: Using C11 mode: True
Nuitka-Scons: Using resource mode: 'win_resource' (default for Windows).
Nuitka-Scons: Told to run compilation on 6 CPUs.
Nuitka-Scons: Found ccache 'C:\MinGW\bin\ccache.exe' to cache C compilation result.
Nuitka-Scons: Providing real CC path 'C:\MinGW\bin\gcc.exe' via PATH extension.
Nuitka-Scons: Launching Scons target: ['C:\MY_DOC~1\Work\ALORAP~1\SETKA~1.DIS\setka_dyn_NG311.exe']
scons: done reading SConscript files.
scons: Building targets ...
"C:\MinGW\bin\ccache.exe" "C:\MinGW\bin\gcc.exe" -o constants.o -c -flto=6 -fuse-linker-plugin -fno-fat-lto-objects -std=c11 -fvisibility=hidden -fwrapv -pipe -fpartial-inlining -ftrack-macro-expansion=0 -Wno-deprecated-declarations -fno-var-tracking -Wno-misleading-indentation -fcompare-debug-second -O3 -D_WIN32_WINNT=0x0501 -D__NUITKA_NO_ASSERT -DMS_WIN64 -D_NUITKA_STANDALONE -D_NUITKA_ONEFILE_MODE -D_NUITKA_ONEFILE_TEMP_BOOL -D_NUITKA_CONSTANTS_FROM_RESOURCE -D_NUITKA_FROZEN=154 -D_NUITKA_EXE -D_NUITKA_PLUGIN_MULTIPROCESSING_ENABLED=1 -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\zlib -IC:\PROGRA~3\ANACON~1\include -I. -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\include -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\static_src -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\libbacktrace constants.c
"C:\MinGW\bin\ccache.exe" "C:\MinGW\bin\gcc.exe" -o helpers.o -c -flto=6 -fuse-linker-plugin -fno-fat-lto-objects -std=c11 -fvisibility=hidden -fwrapv -pipe -fpartial-inlining -ftrack-macro-expansion=0 -Wno-deprecated-declarations -fno-var-tracking -Wno-misleading-indentation -fcompare-debug-second -O3 -D_WIN32_WINNT=0x0501 -D__NUITKA_NO_ASSERT -DMS_WIN64 -D_NUITKA_STANDALONE -D_NUITKA_ONEFILE_MODE -D_NUITKA_ONEFILE_TEMP_BOOL -D_NUITKA_CONSTANTS_FROM_RESOURCE -D_NUITKA_FROZEN=154 -D_NUITKA_EXE -D_NUITKA_PLUGIN_MULTIPROCESSING_ENABLED=1 -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\zlib -IC:\PROGRA~3\ANACON~1\include -I. -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\include -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\static_src -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\libbacktrace helpers.c
"C:\MinGW\bin\ccache.exe" "C:\MinGW\bin\gcc.exe" -o loader.o -c -flto=6 -fuse-linker-plugin -fno-fat-lto-objects -std=c11 -fvisibility=hidden -fwrapv -pipe -fpartial-inlining -ftrack-macro-expansion=0 -Wno-deprecated-declarations -fno-var-tracking -Wno-misleading-indentation -fcompare-debug-second -O3 -D_WIN32_WINNT=0x0501 -D__NUITKA_NO_ASSERT -DMS_WIN64 -D_NUITKA_STANDALONE -D_NUITKA_ONEFILE_MODE -D_NUITKA_ONEFILE_TEMP_BOOL -D_NUITKA_CONSTANTS_FROM_RESOURCE -D_NUITKA_FROZEN=154 -D_NUITKA_EXE -D_NUITKA_PLUGIN_MULTIPROCESSING_ENABLED=1 -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\zlib -IC:\PROGRA~3\ANACON~1\include -I. -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\include -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\static_src -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\libbacktrace loader.c
"C:\MinGW\bin\ccache.exe" "C:\MinGW\bin\gcc.exe" -o module.AlorPy.AlorPy.o -c -flto=6 -fuse-linker-plugin -fno-fat-lto-objects -std=c11 -fvisibility=hidden -fwrapv -pipe -fpartial-inlining -ftrack-macro-expansion=0 -Wno-deprecated-declarations -fno-var-tracking -Wno-misleading-indentation -fcompare-debug-second -O3 -D_WIN32_WINNT=0x0501 -D__NUITKA_NO_ASSERT -DMS_WIN64 -D_NUITKA_STANDALONE -D_NUITKA_ONEFILE_MODE -D_NUITKA_ONEFILE_TEMP_BOOL -D_NUITKA_CONSTANTS_FROM_RESOURCE -D_NUITKA_FROZEN=154 -D_NUITKA_EXE -D_NUITKA_PLUGIN_MULTIPROCESSING_ENABLED=1 -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\zlib -IC:\PROGRA~3\ANACON~1\include -I. -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\include -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\static_src -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\libbacktrace module.AlorPy.AlorPy.c
"C:\MinGW\bin\ccache.exe" "C:\MinGW\bin\gcc.exe" -o module.AlorPy.Config.o -c -flto=6 -fuse-linker-plugin -fno-fat-lto-objects -std=c11 -fvisibility=hidden -fwrapv -pipe -fpartial-inlining -ftrack-macro-expansion=0 -Wno-deprecated-declarations -fno-var-tracking -Wno-misleading-indentation -fcompare-debug-second -O3 -D_WIN32_WINNT=0x0501 -D__NUITKA_NO_ASSERT -DMS_WIN64 -D_NUITKA_STANDALONE -D_NUITKA_ONEFILE_MODE -D_NUITKA_ONEFILE_TEMP_BOOL -D_NUITKA_CONSTANTS_FROM_RESOURCE -D_NUITKA_FROZEN=154 -D_NUITKA_EXE -D_NUITKA_PLUGIN_MULTIPROCESSING_ENABLED=1 -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\zlib -IC:\PROGRA~3\ANACON~1\include -I. -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\include -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\static_src -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\libbacktrace module.AlorPy.Config.c
"C:\MinGW\bin\ccache.exe" "C:\MinGW\bin\gcc.exe" -o module.AlorPy.o -c -flto=6 -fuse-linker-plugin -fno-fat-lto-objects -std=c11 -fvisibility=hidden -fwrapv -pipe -fpartial-inlining -ftrack-macro-expansion=0 -Wno-deprecated-declarations -fno-var-tracking -Wno-misleading-indentation -fcompare-debug-second -O3 -D_WIN32_WINNT=0x0501 -D__NUITKA_NO_ASSERT -DMS_WIN64 -D_NUITKA_STANDALONE -D_NUITKA_ONEFILE_MODE -D_NUITKA_ONEFILE_TEMP_BOOL -D_NUITKA_CONSTANTS_FROM_RESOURCE -D_NUITKA_FROZEN=154 -D_NUITKA_EXE -D_NUITKA_PLUGIN_MULTIPROCESSING_ENABLED=1 -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\zlib -IC:\PROGRA~3\ANACON~1\include -I. -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\include -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\static_src -IC:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\inline_copy\libbacktrace module.AlorPy.c
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [module.AlorPy.Config.o] Error 3
scons: internal stack trace:
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Job.py", line 262, in run
task.execute()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Script\Main.py", line 193, in execute
SCons.Taskmaster.OutOfDateTask.execute(self)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Taskmaster.py", line 235, in execute
self.targets[0].build()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Node_init_.py", line 755, in build
self.get_executor()(self, **kw)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 384, in call
return _do_execute_map[self.do_execute](self, target, kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 120, in execute_action_list
raise status    # TODO pylint E0702: raising int not allowed
^^^^^^^^^^^^
scons: *** [module.AlorPy.o] Error 3
scons: internal stack trace:
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Job.py", line 262, in run
task.execute()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Script\Main.py", line 193, in execute
SCons.Taskmaster.OutOfDateTask.execute(self)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Taskmaster.py", line 235, in execute
self.targets[0].build()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Node_init.py", line 755, in build
self.get_executor()(self, **kw)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 384, in call
return _do_execute_map[self._do_execute](self, target, kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 120, in execute_action_list
raise status    # TODO pylint E0702: raising int not allowed
^^^^^^^^^^^^
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: *** [__helpers.o] Error 3
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
scons: internal stack trace:
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Job.py", line 262, in run
task.execute()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Script\Main.py", line 193, in execute
SCons.Taskmaster.OutOfDateTask.execute(self)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Taskmaster.py", line 235, in execute
self.targets[0].build()
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Node_init_.py", line 755, in build
self.get_executor()(self, **kw)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 384, in call
return _do_execute_map[self.do_execute](self, target, kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 120, in execute_action_list
raise status    # TODO pylint E0702: raising int not allowed
^^^^^^^^^^^^
scons: *** [module.AlorPy.AlorPy.o] Error 3
scons: internal stack trace:
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Job.py", line 262, in run
task.execute()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Script\Main.py", line 193, in execute
SCons.Taskmaster.OutOfDateTask.execute(self)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Taskmaster.py", line 235, in execute
self.targets[0].build()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Node_init.py", line 755, in build
self.get_executor()(self, **kw)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 384, in call
return _do_execute_map[self._do_execute](self, target, kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 120, in execute_action_list
raise status    # TODO pylint E0702: raising int not allowed
^^^^^^^^^^^^
scons: *** [_constants.o] Error 3
scons: internal stack trace:
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Job.py", line 262, in run
task.execute()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Script\Main.py", line 193, in execute
SCons.Taskmaster.OutOfDateTask.execute(self)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Taskmaster.py", line 235, in execute
self.targets[0].build()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Node_init.py", line 755, in build
self.get_executor()(self, **kw)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 384, in call
return _do_execute_map[self._do_execute](self, target, kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 120, in execute_action_list
raise status    # TODO pylint E0702: raising int not allowed
^^^^^^^^^^^^
scons: *** [_loader.o] Error 3
scons: internal stack trace:
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Job.py", line 262, in run
task.execute()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Script\Main.py", line 193, in execute
SCons.Taskmaster.OutOfDateTask.execute(self)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Taskmaster.py", line 235, in execute
self.targets[0].build()
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Node_init.py", line 755, in build
self.get_executor()(self, **kw)
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 384, in call
return _do_execute_map[self._do_execute](self, target, kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\PROGRA~3\ANACON~1\Lib\SITE-P~1\nuitka\build\INLINE~1\lib\scons-4.3.0\SCons\Executor.py", line 120, in execute_action_list
raise status    # TODO pylint E0702: raising int not allowed
^^^^^^^^^^^^
scons: building terminated because of errors.
Nuitka-Reports: Compilation report written to file 'nuitka-crash-report.xml'.
Nuitka-Reports: Compilation crash report written to file 'nuitka-crash-report.xml'.`
nuitka-crash-report.zip

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
Feedback if this is working is very welcome, just please do not share plans of doing it, but rather confirmations or denials of it working.

It would appear that your ccache.exe cannot do --version output even. If so, report that to winlibs, it will prevent Nuitka from updating winlibs.

Yes:
`ccache --version
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what():  filesystem error: Cannot convert character sequence: Illegal byte sequence`

What python -m nuitka --version would have output, is the path to the compiler and that would let me know, that it's essentially an unsupported gcc. I changed my stance from allowing newer versions over time, since LTO and Windows in general are so fragile, to the point, where this gcc of yours should be ignored in favor of a downloaded gcc, independent of versions.

(base) c:\My_Documents\Work\alorAPI_setkaNG>python -m nuitka --version 2.0.6 Commercial: None Python: 3.11.7 | packaged by Anaconda, Inc. | (main, Dec 15 2023, 18:05:47) [MSC v.1916 64 bit (AMD64)] Flavor: Anaconda Python Executable: C:\ProgramData\anaconda3\python.exe OS: Windows Arch: x86_64 WindowsRelease: 10 Version C compiler: C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.39.33519\bin\Hostx64\x64\cl.exe (cl 14.3).

The factory and soon 2.1 release will no longer accept random Windows gcc's just because the version is new enough and enforce the use of the downloaded version. It can be changed by making a PR with the URL change, and if tests pass.
Having make, having working ccache, having working LTO, having working binutils with no regressions on windows, having all needed workarounds for false messages, all that is so unlikely to exist outside of properly validated versions, we are wasting time and users time, by letting them even attempt things that they do not understand.

The version output reacts to --mingw if you do not provide it, MSVC will be output. The compiler related flags must be given there too.

The version output reacts to --mingw if you do not provide it, MSVC will be output. The compiler related flags must be given there too.

(base) c:\My_Documents\Work\alorAPI_setkaNG>python -m nuitka --version --mingw 2.0.6 Commercial: None Python: 3.11.7 | packaged by Anaconda, Inc. | (main, Dec 15 2023, 18:05:47) [MSC v.1916 64 bit (AMD64)] Flavor: Anaconda Python Executable: C:\ProgramData\anaconda3\python.exe OS: Windows Arch: x86_64 WindowsRelease: 10 Version C compiler: C:\MinGW\bin\gcc.exe (gcc 13.2.0).

Yeah, you are all affected by the belief that you need to install it yourself, and that new enough versions will work, which is just not the case. Thanks for confirming this. I believe the user manual is unclear about this. We are rewriting the statements there to be more clear regarding this.

This is now on develop.


fix: Map ORM errors to internalServerError

Description
Mapping the ORM errors to internalServerError to not expose sensible information about the database

Codecov Report

Merging #1227 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1227      +/-   ##
==========================================
+ Coverage   89.38%   89.39%   +<.01%
==========================================
  Files          38       38
  Lines        2232     2234       +2
==========================================
+ Hits         1995     1997       +2
  Misses        237      237

Flag
Coverage Δ

#Kitura
89.39% <100%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

Sources/Kitura/CodableRouter.swift
78.67% <100%> (+0.2%)
:arrow_up:

Continue to review full report at Codecov.

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

Tests passed, but github not picking them up...okay to merge?


How to install cufflinks v0.17.0 via conda?

Hello y'all!
I wasn't able to install cufflinks v0.17.0 via conda. The only two distributions I found are below:

https://anaconda.org/conda-forge/cufflinks-py
https://anaconda.org/conda-forge/python-cufflinks

Can someone shine a little 💡 on this matter?
Thanks!

@cshaley @dhirschfeld mind consolidating into 1

@timkpaine, achieved goal via pip install workaround on conda environment.yml as of below.
name: example-env
channels:
  - anaconda-fusion
  - defaults
  - conda-forge
dependencies:
  - python>=3.7.5
  - pandas>=0.25.2
  - plotly>=4.0.0
  - plotly-orca>=1.2.1
  - pip:
    - cufflinks>=0.17.0

python-cufflinks=0.17.0 is now available from conda-forge


Crash on open manga

Steps to reproduce
The manga opened the second time so I have no idea
Expected behavior
not crash
Actual behavior
what happened was I opened a new maid dragon chapter, and a wall of text popped up
Crash logs
neko_crash_logs (6).txt
Neko version
2.12.6
Android version
13 sdk 33
Device
samsung galaxy tab s7+
Other details
I don't know if this is the full log or not, the page that popped up had a crash dump button, but I can't find that specific log and this seems really short given it was a scrollable page for the other one. if you know were the log is I can try to find it to give you a better thing to work off of.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to the newest version Latest.
[X] I have filled out all of the requested information in this form.

There is nothing in the file, as you mentioned if you can get to happen again take a screenshot the crash screen


Are alias table entry and rule statistics counters written to disk or kept only in RAM?

Don't see anything in manual about the alias counters.
https://docs.opnsense.org/manual/aliases.html
Manual mentions the firewall rule statistics counters but not if written to disk.
https://docs.opnsense.org/manual/firewall.html
Interest is in minimizing USB flash drive write cycles.
22.7.10_2
VGA image install

traffic counters only in memory, see https://www.freebsd.org/cgi/man.cgi?pf.conf(5)


[1.x] Make reproducibility toggleable for ConsistentAnalysisFormat

c.c. https://github.com/sbt/sbt/issues/7790
This PR makes ConsistentAnalysisFormat toggle-able via new flag reproducible to preserve timestamp information needed for Zinc to conduct certain invalidation decisions. Users who uses reproducible build tool can choose to set reproducible flag on (at the expense of less accurate invalidation), and most users who don't use reproducible build tool can set reproducible off for more accurate invalidation.
Build tools using Zinc may need to surface the flag to users, and are encouraged to set reproducible = false as default option.

Reopening the PR, following discussion in https://github.com/sbt/zinc/pull/1496#issuecomment-2480978181
@ephemerist


firebase_ml_vision 0.9.3+8 not able to detect barcode

barcodeDetector.detectInImage(visionImage)  is not able to parse below image and get the qrcode details
using: firebase_ml_vision 0.9.3+8

you can repreduce it with attached image

Hi @kw2019ltd
Please use the example  and make sue you've proper done the setup
can you please provide your flutter doctor -v and flutter run --verbose while scanning?
Thank you

yes i tried it, the issue with this QR it has no border so barcodeDetector.detectInImage(visionImage)
not able to detect the barcode.
you can save the image and try it you will face same issue.
[√] Flutter (Channel stable, v1.17.0, on Microsoft Windows [Version 10.0.18363.778], locale en-IL)
• Flutter version 1.17.0 at C:\Tools\flutter
• Framework revision e6b34c2b5c (6 days ago), 2020-05-02 11:39:18 -0700
• Engine revision 540786dd51
• Dart version 2.8.1
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at C:\Users\kotai\AppData\Local\Android\sdk
• Platform android-29, build-tools 29.0.2
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
X Android license status unknown.
Try re-installing or updating your Android SDK Manager.
See https://developer.android.com/studio/#downloads or visit visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions.
[√] Android Studio (version 3.6)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 45.1.1
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
[!] IntelliJ IDEA Ultimate Edition (version 2019.3)
• IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2019.3.1
X Flutter plugin not installed; this adds Flutter specific functionality.
X Dart plugin not installed; this adds Dart specific functionality.
• For information about installing plugins, see
https://flutter.dev/intellij-setup/#installing-the-plugins

Hi @kw2019ltd
I tried to to reproduce this issue using official. example and it has no issue

Please clone this repo and add your firebase configuration

flutter doctor -v
[✓] Flutter (Channel dev, 1.18.0-13.0.pre, on Mac OS X 10.15.4 19E287, locale
    en-GB)
    • Flutter version 1.18.0-13.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 8fbfe1cfbf (35 hours ago), 2020-05-06 17:36:01 -0700
    • Engine revision d6aa099de7
    • Dart version 2.9.0 (build 2.9.0-5.0.dev 4da5b40fb6)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.45.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.10.1

[✓] Connected device (4 available)
    • SM M305F   • 32003c30dc19668f • android-arm64  • Android 10 (API 29)
    • macOS      • macOS            • darwin-x64     • Mac OS X 10.15.4 19E287
    • Web Server • web-server       • web-javascript • Flutter Tools
    • Chrome     • chrome           • web-javascript • Google Chrome
      81.0.4044.138

• No issues found!

Hi @kw2019ltd
I tried to to reproduce this issue using official. example and it has no issue

Please clone this repo and add your firebase configuration

flutter doctor -v
[✓] Flutter (Channel dev, 1.18.0-13.0.pre, on Mac OS X 10.15.4 19E287, locale
    en-GB)
    • Flutter version 1.18.0-13.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 8fbfe1cfbf (35 hours ago), 2020-05-06 17:36:01 -0700
    • Engine revision d6aa099de7
    • Dart version 2.9.0 (build 2.9.0-5.0.dev 4da5b40fb6)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.45.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.10.1

[✓] Connected device (4 available)
    • SM M305F   • 32003c30dc19668f • android-arm64  • Android 10 (API 29)
    • macOS      • macOS            • darwin-x64     • Mac OS X 10.15.4 19E287
    • Web Server • web-server       • web-javascript • Flutter Tools
    • Chrome     • chrome           • web-javascript • Google Chrome
      81.0.4044.138

• No issues found!

Hi in order to reproduce the issue you need to load the image using image
picker and you will face the issue.
Attached image pls load it using image picker and call barcode detector you
will get no result.
On Fri, May 8, 2020, 17:58 Taha Tesser<EMAIL_ADDRESS>wrote:

Hi @kw2019ltd https://github.com/kw2019ltd
I tried to to reproduce this issue using official. example
https://pub.dev/packages/firebase_ml_vision and it has no issue
[image: flutter_03]
https://user-images.githubusercontent.com/48603081/81418470-5b260280-916a-11ea-8423-28b025fb9629.png
Please clone this repo https://github.com/FirebaseExtended/flutterfire
and add your firebase configuration
flutter doctor -v
[✓] Flutter (Channel dev, 1.18.0-13.0.pre, on Mac OS X 10.15.4 19E287, locale
en-GB)

• Flutter version 1.18.0-13.0.pre at /Users/tahatesser/Code/flutter_dev

• Framework revision 8fbfe1cfbf (35 hours ago), 2020-05-06 17:36:01 -0700

• Engine revision d6aa099de7

• Dart version 2.9.0 (build 2.9.0-5.0.dev 4da5b40fb6)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at /Users/tahatesser/Code/SDK

• Platform android-29, build-tools 29.0.3

• ANDROID_HOME = /Users/tahatesser/Code/SDK

• Java binary at: /Applications/Android

  Studio.app/Contents/jre/jdk/Contents/Home/bin/java

• Java version OpenJDK Runtime Environment (build

  1.8.0_212-release-1586-b4-5784211)

• All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer

• Xcode 11.4.1, Build version 11E503a

• CocoaPods version 1.9.1

[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
• Android Studio at /Applications/Android Studio.app/Contents

• Flutter plugin version 45.1.1

• Dart plugin version 192.7761

• Java version OpenJDK Runtime Environment (build

  1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.45.0)
• VS Code at /Applications/Visual Studio Code.app/Contents

• Flutter extension version 3.10.1

[✓] Connected device (4 available)
• SM M305F   • 32003c30dc19668f • android-arm64  • Android 10 (API 29)

• macOS      • macOS            • darwin-x64     • Mac OS X 10.15.4 19E287

• Web Server • web-server       • web-javascript • Flutter Tools

• Chrome     • chrome           • web-javascript • Google Chrome

  81.0.4044.138

• No issues found!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FirebaseExtended/flutterfire/issues/2506#issuecomment-625856361,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALJEI6TOCNKBW3PEJEWJPGLRQQMX7ANCNFSM4M2PFWMQ
.

salam any any update of this issue?

Hi @kw2019ltd
To better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem, official example works fine
Thank you

hi as i said you need to download the image i sent as is, dont take screen shot and try to scan it.
the issue that image has no border.
in order to repreduce the issue do the following:
1 - downalod the image as is
2- try to scan it using image picker and then call
barcodeDetector.detectInImage(visionImage)
expected: barCode return
actual: empty result
minimal code:
final _barcodeDetector = FirebaseVision.instance.barcodeDetector();
Future _getImage() async {
try {
var image = await ImagePicker.pickImage(
source: ImageSource.gallery,
);
  if (image != null) {
    var barCodes =
        await getBarcodeFromFile(image, _barcodeDetector);
    var barcodeDto = await _parseBarCode(barCodes, 'scan_image');
    await _showCodeWidget(barcodeDto);
  }
} catch (e, s) {

}

}
Future<List> getBarcodeFromFile(
File imageFile, BarcodeDetector barcodeDetector) async {
final visionImage = FirebaseVisionImage.fromFile(imageFile);
if (visionImage != null) {
return await barcodeDetector.detectInImage(visionImage);
}
return null;
}

Hi @viplavrawal
Using official example
Pick your qr code and then please select barcode scanner from the menu

Here using you qr code, can see green highlight that detected qr code

flutter doctor -v
[✓] Flutter (Channel dev, 1.19.0-1.0.pre, on Mac OS X 10.15.4 19E287, locale
    en-GB)
    • Flutter version 1.19.0-1.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 456d80b9dd (10 days ago), 2020-05-11 11:45:03 -0400
    • Engine revision d96f962ca2
    • Dart version 2.9.0 (build 2.9.0-7.0.dev 092ed38a87)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.8052
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.45.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.10.2

[✓] Connected device (7 available)
    • SM M305F                  • 32003c30dc19668f                     •
      android-arm64  • Android 10 (API 29)
    • Android SDK built for x86 • emulator-5554                        •
      android-x86    • Android 10 (API 29) (emulator)
    • Taha’s iPhone             • 00008020-001059882212002E            • ios
      • iOS 13.5
    • iPhone 11                 • F067D2F5-5386-4EBE-8600-326B40C64462 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-13-5 (simulator)
    • macOS                     • macOS                                •
      darwin-x64     • Mac OS X 10.15.4 19E287
    • Web Server                • web-server                           •
      web-javascript • Flutter Tools
    • Chrome                    • chrome                               •
      web-javascript • Google Chrome 81.0.4044.138

• No issues found!

Thank you

hi i tried the same for me its not working on my device one plus 8T
attached screen shot where it was not able to detect QR code

record where it was not able to detect qrcode

also i added print to check if barcode detect it was not

I/native  ( 9172): barcode_detector_client.cc:238 Not using NNAPI
I/flutter ( 9172): 0
pls check the issue.


fix demo, make it runnable in flink 1.15.3

Proposed changes
Problem summary
make the demo DatabaseFullSync work on Flink 1.15.3
Checklist(Required)

[ n] Does it affect the original behavior
[ y] Has unit tests been added
[ n] Has document been added or modified
[ n] Does it need to update dependencies
[ y] Is this PR support rollback (If NO, please explain WHY)

Further comments
original demo does not really work, I fix :

mvn package the fat jar which could directly upload to a clean Flink
bug of SYNC_TBLS

Thank you for your contribution, this is just a code sample reference, not a packaged executable jar.
Synchronize the entire mysql database, adding a more convenient tool, using the side output stream instead of filter, you can refer to here.


Feature: Add isDryRun() to Java API

Which version and edition of Flyway are you using?
6.0.0
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Java API
Which database are you using (type & version)?
MariaDB 10.2.6
Which operating system are you using?
macOS Mojave 10.14.6/CentOS 7
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
Standard Java migration (implement BaseJavaMigration.migrate()
What did you expect to see?
Feature Request - an API to check if currently in a dry-run state.
What did you see instead?
Current workaround is context.getConfiguration().getDryRunOutput() != null

IWhich class would you like the method added to?

We probably wouldn't add this to the Configuration interface because that is meant to reflect the options in the config files (and dryRun isn't one of them), so I'm going to close this because the workaround seems reasonable.


ratify crashing due to unknown flag

What happened in your environment?
when install ratify following the startup
helm install ratify \
    ./charts/ratify --atomic \
    --namespace gatekeeper-system \
    --set-file notaryCert=./test/testdata/notary.crt \
    --set featureFlags.RATIFY_CERT_ROTATION=true

the ratify pod will be crashing, with error log Error: unknown flag: --cache-enabled
I think it might be commit not included in v1.0.0-rc.6 but chart published is too latest.
What did you expect to happen?
No response
What version of Kubernetes are you running?
1.26
What version of Ratify are you running?
v1.0.0-rc.6
Anything else you would like to add?
No response
Are you willing to submit PRs to contribute to this bug fix?

[ ] Yes, I am willing to implement it.

i used incorrect chart repo sorry for confusing


New suggestion request for: f . uncurry (zipWith g) $ (a, b)

This looks like a good one to have in general:
module Z where
lhs f g a b = f . uncurry (zipWith g) $ (a, b)
rhs f g a b = f $ zipWith g a b

even GHC think they are the same on -O2:
$ ghc -O2 Z.hs -ddump-simpl
[1 of 1] Compiling Z                ( Z.hs, Z.o )

==================== Tidy Core ====================
<omitted>
rhs [InlPrag=NOUSERINLINE[2]]
  :: forall c t a b. ([c] -> t) -> (a -> b -> c) -> [a] -> [b] -> t
<omitted>
rhs = lhs
<omitted>

Agreed! I think the hint should be uncurry f (a, b) ==> f a b.  PR most welcome!

Yeah I didn't attempt to simplify it as I assumed such a simple rule must have existed, turn out it's not:
$ cat >Z.hs
module Z where f g x y = uncurry g (x,y)
$ hlint Z.hs
No hints

I'll take a look, feel free to assign me on this.

Sure, assigned to you :)
If the simple one works, it automatically gets generalised in a bunch of interesting ways, so if you write the simple one, it will catch the more complex example you initially wrote.


Misleading error message if component template is missing

Just encountered this issue when I called the component helper like this {{component name="my-component" template="special"}}.
The error message I got was Component my-component not found. and so I triple checked the component name because I thought it had a typo in it when in reality it was just the wrong template parameter, which I should've prefixed with the full component name.
First it would be great if you'd actually get an error which points to a missing template instead of a missing component to prevent confusion and second it's also a bit inconvenient that you have to write the component name again, couldn't this be simplified? Especially for consistency since you don't have to write the full component name in modifiers and decorators either when creating components or even setting them via data.

Thanks for your feedback.
I've added a more meaningfull error message:
Component "..." with template file "..." not found in folder "...".
This will be in the next release.
But for the second part:
You have been warned. ;-)

I can't find anything inconvenient and the component helper works in a very simple and logical way.
You have to provide the full name without the extension for data and template files. Nobody demands that the name of the component must be included in the file name. It's just the default.
We shouldn't add some magic.


Tree shaking and partial imports.

Is this something that can be done here?
I figured something like
import('lodash', 'map').then(map => ...)

Just curious if this has been thought of.

You meant import(… instead of Import(… right?

@Mouvedia was on a phone, but I fixed that.

I don't really understand this issue. What bug are your reporting with the current proposal? Are you trying to create another proposal? If so this isn't the place for it.

@domenic I am merely asking if there is something synonymous with
import { map } from 'lodash'

In this proposal.

You can do import('lodash').then(ld => ld.map).

@domenic I am aware of that. Was just curious since obviously that doesn't support tree shaking.

From what I understand, tree-shaking is a nonstandard way of using modules supported by some ahead-of-time tooling that turns those modules into non-modules. It's not really something that informs the design of the language, but instead is something for those creating such tools to work through on their own.

@DylanPiercey to be precise here, if you have a tool that can do tree shaking on something like:
import * as foo from "foo";
foo.x('do something');

Assuming that foo exports a lot more than just x, then it is very likely that the same tool can work the same way with import("foo").


Class Library

I have moved the source into a class library so that I could include the source code into an existing project of mine. Would you be interested if I created a pull request for you?
It would mean you have to create a test app that includes the class library but I would like to help structure that if your interested.

Closing this as it is about the same as #5.


Option to package with supplied Dockerfile

This option would come in handy when one needs to have a custom image (usually built on top of lambci/lambda ones) for requirements packaging.
The use case I came across was when I needed to run my serverless Python function that uses pymssql in Python 3.6 environment. Unfortunately, the project currently does not provide a pre-built wheel for Python 3.6 in Linux environment -  see https://github.com/pymssql/pymssql/issues/473
So my workaround for this is to build pymssql with the environment variable export PYMSSQL_BUILD_WITH_BUNDLED_FREETDS=1, included in a Dockerfile as such:
FROM lambci/lambda:build-python3.6

ENV PYMSSQL_BUILD_WITH_BUNDLED_FREETDS 1

Built the image, and pushed to Docker Hub, specified in custom.pythonRequirements.dockerImage option supported by this plugin. Everything works great.
However, this solution would be more portable and flexible for when the use case prohibits the use of Docker Hub, for whatever reasons. If there's an option to allow dockerImage to be sourced from a Dockerfile directly, basically adding one step to first build the image using supplied Dockerfile, tag it with serverless service name and stage and runtime for matching convention with currently supplied set of lambci/lambda images, and then just follow the existing steps to package pip requirements.

Oooh, that's a good idea, having to maintain your own image is a nuisance and this would help a ton. I think I'd  want to add a dockerfile option which is mutually exclusive with the dockerImage option.


Enable ints up to 8 bytes

Update the Data __int__ to enable up to 8 bytes
Fixes: #2243

@Shulyaka could you check please?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

Thanks Julian!


CLI: Offline sync of large files prints lots of terminal noise

I am running my code on a remote cluster that does not have internet access while executing the code. Hence, I have to scp the files to my local system and then sync them. The issue with this is that whenever I try to sync large files(>400MB), a huge string of the metrics logged in at each time step gets printed out on the terminal. Would it be possible to suppress that?
My wandb version 0.10.11

Can you share a screen shot or terminal output of what you're seeing?  Is this happening when you run wandb sync or when you are scp'ing the data?

The above screenshot is just a small part of the whole thing which is printed. Actually, similar chunks are printed for other metrics as well(validation losses, etc.). This happens when I run wandb sync

Are there any other error messages surrounding these?

No, it just keeps on printing these lines for a long time.

Any updates on this?

Hi there, could you please share some code/files we could try to reproduce this issue? We'd like to get you a fix but I haven't been able to get this to happen on my own projects.

Can I email the log folder drive link to reproduce the error?

Sure, send them to<EMAIL_ADDRESS>

@vanpelt I have sent a drive link to the log files to<EMAIL_ADDRESS>

Thanks, I've received and the ticket will be prioritized in the backlog.

@vanpelt Are there any updates on this?

@nsidn98 we have a branch that should fix this.  You can install it locally by running the following:
pip install --upgrade git+git://github.com/wandb/client.git@fr_sync_fix#egg=wandb
This should go out in the next official release early next week, thanks for your patience on this one.

Thanks a lot for looking into this and fixing it!


Error creating incident

Install went well with version 2.
Testing the app, Create Incident
Error: 
An error has occurred, please try to create your incident again
It looked like the incident team was starting to be created, then it disappeared.
On second try it worked, but this time I didn't add Guest Users or CLoud Storage Location

Hi @tcrobbins4 ,
Thanks for reaching out to us.
It could be an intermittent issue in your first try, but it should ideally work even if you add Guest users and cloud storage location. Can you please try to add those fields as well and create another incident in browser version of teams? If you face any errors again, please share me the console logs and network trace for further troubleshooting on this issue. Thanks!

Ok.  Stand by.  Heading on vacation for a few days.


Create a doc site for the k8s builder

There are currently some docs in the form of a readme and markdown files in the docs folder, however it would be great to have a more user friendly doc site
For example the Hyperledger Besu project uses the MKDOCS_MATERIAL material docs insider:

https://github.com/hyperledger/besu-docs/blob/d63f1467fa4acc4e807bb34fa34a03d560930b64/mkdocs-insider.yml
https://github.com/hyperledger/besu-docs/pull/1113
https://squidfunk.github.io/mkdocs-material/

If you're here for hacktoberfest and have any questions, get in touch on our fabric-hacktoberfest Discord channel!

See October 2023 TOC meeting for a Documentation Task Force Update
Also, the new documentation should cover private images #96, and multi-arch Docker images #97.

Include the following doc suggestion from @y12studio in #98

Warning: There are instances where the chaincode pod may continue to run even after its associated peer has disconnected. To conserve Kubernetes CPU and memory resources, it's advisable to remove these lingering pods. They can be identified and removed by their label: fabric-builder-k8s-peerid=peerID. For example, you can use the following command to locate these pods:
kubectl get pod -A -l app.kubernetes.io/created-by=fabric-builder-k8s,fabric-builder-k8s-peerid=peerID

Make sure documentation covers everything required for running chaincode in a different namespace. @davidfdr reported that the fabric-builder-rolebinding namespace needs to match.

Done! https://labs.hyperledger.org/fabric-builder-k8s/


[META] Encourage contributions with the Easy Pick label

Implementing an Easy Pick label would help to increase contributions to Bower.
See http://seld.be/notes/encouraging-contributions-with-the-easy-pick-label

Good idea. this would be very useful to me right now.

It would be great for people just starting with node like me. That way we can start contributing with less effort.

Hey! For now please register on http://goo.gl/forms/P1ndzCNoiG
We need some time to organize everything :)

We should keep this open so it stays on the radar that will allow people to see @sheerun answer with the link to register.
@bower/bower-volunteers - please share the register link with others that might be interested in contributing.

@sheerun @colinodell - I noticed that React has a label for good first bug that they tell those who want to start contributing to pick out. How about a label close to this?

I understand the desire to have potential contributors register, but I worry that it may exclude or alienate people like myself who don't have the time or desire to commit to becoming a regular contributor.
An Easy Pick label serves a similar purpose to @pertrai1's suggestion, in that it highlights fairly simple tasks and issues that almost anyone can pick up with minimal experience or guidance.  I believe that adding this label would help encourage contributions from people who:

Have never contributed to Bower before
Are looking to make a one-time contribution
Are looking to make small, infrequent contributions

A similar idea is up-for-grabs: http://up-for-grabs.net/  This is also geared to encouraging contributions, but may include tasks which are too difficult for newcomers.
So while I do feel that registration would be great for organizing frequent contributors, I still feel there needs to be something to target newcomers and occasional contributors as well, which is why I feel strongly about the Easy Pick concept.
Just my $0.02 :)

@colinodell Totally agree. For the longest time I was a roamer :-) so to speak around GitHub not knowing how to even start contributing. If Bower had a way to get people involved by labelling how to easily get started would be a good first step.

We currently have level:beginner|intermediate|advanced

@faceleg No doubt those will work. Just liked the idea when I saw it about the First Bug label that is easy to spot for someone.

Let's stick it with the level tags for the moment

@ceoaliongroo +1

If there is not already, some mention of the level tags might be helpful in the contributing docs

@faceleg @sheerun I have added the Labels to the Wiki: https://github.com/bower/bower/wiki/Contributor-Guidelines

Great :) I can change labels at any time.


Introduction to MVC

The task is to prepare concise and easy introduction to MVC architectural pattern in any form - find yt video, short article, prepare quick tutorial.
Result of this task will be presented to the rest of the team.

 Introduction to MVC

https://github.com/spectre-team/spectre/wiki/MVC.png
https://github.com/spectre-team/spectre/wiki/MVC.docx


JavaScript JSDoc function completion not working for previews

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.86.0 (https://github.com/microsoft/vscode/commit/3ddf196d27d71d2f5539db607b1a10adb3d0800c)
OS Version: Windows 11 Home x64, version 23H2 (build 22631.3007)

Steps to Reproduce:

Enable the following settings: editor.suggest.preview and javascript.suggest.completeFunctionCalls
Create a JavaScript file and write a simple function with JSDoc, for example:

/**
 * @param {number} a First number
 * @param {number} b Second number
 * @returns {number} Sum of a and b
 */
 function add(a, b) { return a + b; }

Start writing a call to add. The editor should show a preview like this: add(a, b), but instead it only suggests the name add, even though previews and function call completion are enabled.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.85.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Seems to work fine for me:

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


background

It's just the best theme ever, but there's one problem. When Monokai Pro and Filter Spectrum are selected, the code background becomes white instead of the theme colour. This happens in Webstorm, in PyCharm and Intellij everything is fine. Please solve this problem!

Fixed this by going to Settings->Editor->Color Scheme->General; From the scheme drop down at the top choose Monokai Pro Filter Spectrum.
Don't know if this will stay across updates.


do you care if I publish this package to ros?

this package (including the re-writes I made in #2) could be really useful for others and I think publishing it for others to download as binaries for easy installation and setup.
is it OK with you if I publish it to ROS and maintain it?

also, I might try and rewrite it for ROS2 if thats ok as well

Everything sounds good! I just merged your pull request - feel free to publish the package to ROS and let me know if you need anything else!

@vvasilo sounds great! Would you rather me publish it from my forked repo? If you make me a collaborator on your repo here I can release it from this one.
It might be better since this is the original repo rather than a forked version.

I just added you!


Timeout for base llms

Description: Adding timeout as an option to the BaseLLM class.

@alessarcross Hi , could you, please, resolve the merging issues? After that ping me and I push this PR for the review. Thanks!

Closing because the PR wouldn't line up with the current directory structure of the library (would need to be in /libs/langchain/langchain instead of /langchain). Feel free to reopen against the current head if it's still relevant!


destroy process group in end_training

What does this PR do ?
With the latest version of torch, when we use multi-gpu, torch will trigger a warning asking us to call destoy_process_group(). This PR fixes this by adding that in end_training method. Note that this function needs to be called on all process.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Agreed, I'll make a push to Marc's branch since he's OOO. We're missing a if is_main_process: flag here :)

All of the trackers come loaded with @on_main_process decorators already for their functions (if needed/applicable) so this is fine how it is/the right method: https://github.com/huggingface/accelerate/blob/main/src/accelerate/tracking.py#L571-L576


Docker topology probe fails if /proc directory doesn't contain a pid for each container

When skydive is run from within a container, the docker topology problem does not create the containers.
I ran skydive allinone from within a Docker container on Mac with --volume /var/run/docker.sock:/var/run/docker.sock so that the Mac's Docker environment could be seen.
Although the Docker topology probe starts it silently fails because topology/probes/docker.go calls netns.GetFromPid(info.State.Pid) which returns an error if /proc//ns/net doesn't exist (and it won't; containers' view of /proc does not include everything the host sees.)
The first problem is the return without logging if GetFromPid() fails.  If we just log and continue if GetFromPid() fails, and also continue instead of returning when syscall.Stat() in topology/probes/netns.go:Register() fails, then the Docker problem works when skydive is run within a container.

The described bug also happens on Ubuntu WSL connecting to the windows docker desktop.


Conflicts with ardalis clean architecture template

After installing the template, I can not create a project using the template because it uses the same identifier (clean-arch) as another template from Ardalis. Consider giving it a differenet ID

Right, didn't notice the name conflict.
You can create the template via the package id:
dotnet new Amantinband.CleanArchitecture -o CleanArchitecture


HTTP Tap - Streamed trace segments output  does not contain headers added by Envoy

Title:  HTTP Tap - Segmented trace output  does not contain headers added by Envoy
Description:
Using the Tap feature the fully buffered trace and the streamed trace segments output formats differ with regard to the headers added by Envoy. The streamed  trace segments output does not contain the headers added at virtual host, global route and route level while the buffered trace output contains all those. My expectation would be that tap output contains the same HTTP headers for both output format.
Using  Envoy  version: "44f8c365a1f1798f0af776f6aa64279dc68f5666/1.12.1/Clean/RELEASE/BoringSSL"
Config:
The corresponding HTTP config:
- name: envoy.http_connection_manager
        config:
          codec_type: AUTO
          stat_prefix: ingress_http
          route_config:
            name: remote_api
            virtual_hosts:
            - name: apiq
              domains:
              - "*"
              request_headers_to_add:
              - header:
                  key: "x-req-hdr-add-vh-level"
                  value: "req-vh"
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: someserver
                request_headers_to_add:
                  - header:
                      key: "x-req-hdr-add-rt-level"
                      value: "req-rt"
            request_headers_to_add:
              - header:
                  key: "x-req-hdr-add-global-rt-level"
                  value: "req-global-rt"
          http_filters:
          - name: envoy.lua
            config:
              inline_code:  |
                  function envoy_on_request(request_handle)
                    request_handle:headers():add("x-req-hdr-add-lua", "req-lua")
                  end
          - name: envoy.filters.http.tap
            config:
              common_config:
                admin_config:
                  config_id: test_config_id
           - name: envoy.router

Tap config used for fully buffered trace output:
config_id: test_config_id
tap_config:
  match_config:
    any_match: true
  output_config:
    sinks:
      - streaming_admin: {}`

Tap config used for streamed trace segments output:
config_id: test_config_id
tap_config:
  match_config:
    any_match: true
  output_config:
    streaming: true
    sinks:
      - streaming_admin: {}`

Output:
Fully buffered trace output.
{
 "http_buffered_trace": {
  "request": {
   "headers": [
    {
     "key": ":authority",
     "value": "<IP_ADDRESS>:10000"
    },
    {
     "key": ":path",
     "value": "/delay"
    },
    {
     "key": ":method",
     "value": "GET"
    },
    {
     "key": ":scheme",
     "value": "http"
    },
    {
     "key": "user-agent",
     "value": "curl/7.58.0"
    },
    {
     "key": "accept",
     "value": "*/*"
    },
    {
     "key": "x-forwarded-proto",
     "value": "http"
    },
    {
     "key": "x-request-id",
     "value": "462b17b5-7222-4a69-b608-cab90a591698"
    },
    {
     "key": "x-req-hdr-add-lua",
     "value": "req-lua"
    },
    {
     "key": "x-envoy-expected-rq-timeout-ms",
     "value": "15000"
    },
    {
     "key": "x-req-hdr-add-rt-level",
     "value": "req-rt"
    },
    {
     "key": "x-req-hdr-add-vh-level",
     "value": "req-vh"
    },
    {
     "key": "x-req-hdr-add-global-rt-level",
     "value": "req-global-rt"
    }
   ],
   "trailers": []
  },

Streamed trace segments  output:
{
 "http_streamed_trace_segment": {
  "trace_id": "15955110079683032660",
  "request_headers": {
   "headers": [
    {
     "key": ":authority",
     "value": "<IP_ADDRESS>:10000"
    },
    {
     "key": ":path",
     "value": "/delay"
    },
    {
     "key": ":method",
     "value": "GET"
    },
    {
     "key": "user-agent",
     "value": "curl/7.58.0"
    },
    {
     "key": "accept",
     "value": "*/*"
    },
    {
     "key": "x-forwarded-proto",
     "value": "http"
    },
    {
     "key": "x-request-id",
     "value": "e0f0d2c0-e20e-4ad9-8799-e3ed98dbf59a"
    },
    {
     "key": "x-req-hdr-add-lua",
     "value": "req-lua"
    }
   ]
  }
 }
}

Per email thread, the issue here is that the headers are added after the tap filter streams its view of the headers. This is going to be difficult to fix but it's worth looking into this to see if we can do better here.

I can imagine having something akin to an upstream HTTP filter chain, making it possible to configure a set of HTTP filters that are passed the entirety of the upstream request/response. That way you could include a tap filter that sees not only the final request headers without buffering, but is also able to output individual retry attempts etc.
A general filter mechanism would also open up for extensions that modify upstream requests based on stuff like retry state (ie modify a request after N attempts), though I'm not sure if  this is something anyone actually cares about.

I can imagine having something akin to an upstream HTTP filter chain, making it possible to configure a set of HTTP filters that are passed the entirety of the upstream request/response. That way you could include a tap filter that sees not only the final request headers without buffering, but is also able to output individual retry attempts etc.

Yeah, this would work.
More simply we could also just add a callback that an HTTP filter could register for like onHeadersContinued(...) or something like that, so a filter could actually get notified when everything has made it through the chain. But yeah I think the upstream filter chain is probably the better real solution.


Add the K framework language

Hi!
K is a language for defining programming languages as well as type systems and other formal analysis tools. It was first initiated by Grigore Rosu and is currently developed by the FSL group at the University of Illinois at Urbana-Champaign and the FMSE group at Alexandru Ioan Cuza University in Iasi, Romania. You can visit the K Framework website for a more in-depth explanation.
Both the developers and users of K have been using GitHub to host K code for a while though GitHub linguist cannot identify it correctly. As the common usage is now exceeding a certain threshold, we thought we should do something about this.
As requested in CONTRIBUTING.md here is the search showing the common usage of the K Framework.
Some problems
This is the first time I am contributing to linguist so I would appreciate some help by the maintainers. The first issue is that running ./script/set-language-ids --update did not work for me, resulting in the error:
/Users/ayberkt/.rvm/rubies/ruby-2.4.0/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler/setup (LoadError)
        from /Users/ayberkt/.rvm/rubies/ruby-2.4.0/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from ./script/set-language-ids:3:in `<main>'

I am not at all experienced with neither Ruby nor RVM so I could not figure out what's going wrong. If this script is just to update the language ids in languages.yml, I would appreciate if one of the maintainers could run it for me—if they don't mind doing so; I believe this will be the easiest solution.
Also if I recall correctly, running script/add-grammar resulted in some warnings/errors though it seemed to correctly do what it was supposed to do. I would appreciate as well if someone could check whether it worked correctly.
Other than these, all steps listed in CONTRIBUTING.md have been completed.
Looking forward to seeing K Framework on GitHub linguist!
/cc: @msaxena2 @lucaspena

Any chance we can get an update on this?
/cc: @msaxena2 @lucaspena

I shared this same concern in #3638 and I'm not sure how we've addressed this in the past. @larsbrinkhoff, @Alhadis, @pchaigno do you guys know?

In the past, we've postponed these kind of pull request (.dat file extension for instance) until we have a not-a-language option.

I'm tempted to go the route of using a heuristic which falls back to "Text". This approach can be used for #3638 too.

So we wouldn't use the Bayesian classifier for .k files? Unless there's a simple way to identify K files, I'm afraid a heuristic could only catch common cases. Would that be good enough?

In the past, we've postponed these kind of pull request (.dat file extension for instance) until we have a not-a-language option.

Aaaah, yes. I remember seeing discussions about that now you point it out.

So we wouldn't use the Bayesian classifier for .k files? Unless there's a simple way to identify K files, I'm afraid a heuristic could only catch common cases. Would that be good enough?

Hmmm, good point. Probably not. It might work in this case, but thinking about it, it'll probably lead to bad behaviour in the long run.

We should really add a default choice. Unfortunately, I'm not even sure the current classifier is a good fit for that... Can we compute a confidence for its results?

Thanks for the help @lildude! Here is a summary of what I did to address the issues you have mentioned.

I took a look at the issue with the grammars.yml file and it turns out that script/add-grammar had not been properly run but still made some changes so it was in a stuck state. I removed all the changes it made and ran it again with my bundle problems fixed so it went better this time, but it still ran into the following error.
➜ ./script/add-grammar https://github.com/traiansf/language-k
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
OK vendor/grammars/language-k (source.k-framework)
script/list-grammars:81:in `block in to_markdown': undefined method `chomp' for nil:NilClass (NoMethodError)
	from script/list-grammars:65:in `each'
	from script/list-grammars:65:in `to_markdown'
	from script/list-grammars:96:in `update_readme'
	from script/list-grammars:102:in `<main>'

I see that a6df945c93b1771dbec4980ce97ba5284da71c39 has updated the grammars.yml, so this might be fine, but as I don't know all the tasks it is supposed to accomplish I can't be sure if this is enough. What should I do about this?

I have now updated vendor/README.md.

I just opened up an issue at traiansf/language-k about the permissive license issue.

The examples are currently under the UIUC/NCSA license. If you could whitelist this we would prefer that but if that's not possible, we can release these sample programs under one of the whitelisted licenses (in another repo maybe).

I removed most of the sample programs and left only the smaller ones. If this is too few now, I can add some of them back.

Please let me know if there is anything else I can do to help.

The examples are currently under the UIUC/NCSA license. If you could whitelist this we would prefer that but if that's not possible, we can release these sample programs under one of the whitelisted licenses (in another repo maybe).

Paging our resident law-guy, @mlinksva.
Is this an acceptable license? Can we whitelist it?

@Alhadis yes NCSA is acceptable and can be whitelisted.

Thanks! =) Submitted a PR to whitelist it: #3714
@ayberkt Once #3714 is merged, you might need to do a fresh pull from upstream.

Thanks @mlinksva @Alhadis!

@ayberkt are you still pursuing this?

@axic no and I don't even remember why it wasn't concluded when I was pursuing it.

I know this is a really really old PR that will need a bit of work to get it ready for merging (it's probably easier to close it and open a new one), but I thought I'd point out that we now have a mechanism for adding the .k extension thanks to the new method of handling "generic" extensions implemented in https://github.com/github/linguist/pull/4936
In short, it involves:

adding the .k extension to the list at https://github.com/github/linguist/blob/3d39c1c1a0d34c1af890ecfd18cf9ed595c68132/lib/linguist/strategy/extension.rb#L6
adding a heuristic to clearly differentiate and identify .k "K Framework" files
adding a test to confirm the clarification
adding a sample

I know this is a really really old PR that will need a bit of work to get it ready for merging (it's probably easier to close it and open a new one)

Thanks @lildude. I don't remember why this PR was never concluded. Did I forget to do something? In any case, I think someone from FSL would be interested in pursuing this further.
cc: @grosu @xc93 @msaxena2.

I don't remember why this PR was never concluded. Did I forget to do something?

No. It was because .k is too generic and matches far too many files from many different languages which couldn't all be identified so the PR was blocked. We didn't have a solution for such generic cases then, but we do now 😄

Closing as stale. If someone wants to pick this up and implement support for the .k extension in future, my comment at https://github.com/github/linguist/pull/3689#issuecomment-704791687 will help you do that.