Error on windows when I try to make

Hi, when I try to build on windows, I am getting the following error below. I have make 4.3 installed. Any guidance about how to resolve would be appreciated.
C:\picosat_elixir>make
process_begin: CreateProcess(NULL, pwd, ...) failed.
Makefile:1: pipe: No error
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:11: pipe: No error
make: *** No rule to make target '/c_src/picosat.c', needed by '/priv/picosat.o'.  Stop.

Full debug log:
C:\picosat_elixir>make -d
GNU Make 4.3
Built for Windows32
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
Reading makefile 'Makefile'...
CreateProcess(NULL,pwd,...)
process_begin: CreateProcess(NULL, pwd, ...) failed.
Makefile:1: pipe: No error
CreateProcess(NULL,uname -s,...)
process_begin: CreateProcess(NULL, uname -s, ...) failed.
Makefile:11: pipe: No error
Updating makefiles....
 Considering target file 'Makefile'.
  Looking for an implicit rule for 'Makefile'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.o'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.c'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.cc'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.C'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.cpp'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.p'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.f'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.F'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.m'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.r'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.s'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.S'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.mod'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.sh'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile,v'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'RCS/Makefile,v'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'RCS/Makefile'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 's.Makefile'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'SCCS/s.Makefile'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.o'.
  Looking for a rule with intermediate file 'Makefile.o'.
   Avoiding implicit rule recursion.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.c'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.cc'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.C'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.cpp'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.p'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.f'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.F'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.m'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.r'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.s'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.S'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.mod'.
   Trying pattern rule with stem 'Makefile.o'.
   Trying implicit prerequisite 'Makefile.o,v'.
   Trying pattern rule with stem 'Makefile.o'.
   Trying implicit prerequisite 'RCS/Makefile.o,v'.
   Trying pattern rule with stem 'Makefile.o'.
   Trying implicit prerequisite 'RCS/Makefile.o'.
   Trying pattern rule with stem 'Makefile.o'.
   Trying implicit prerequisite 's.Makefile.o'.
   Trying pattern rule with stem 'Makefile.o'.
   Trying implicit prerequisite 'SCCS/s.Makefile.o'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.c'.
   Looking for a rule with intermediate file 'Makefile.c'.
    Avoiding implicit rule recursion.
    Avoiding implicit rule recursion.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.y'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.l'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.w'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.w'.
    Trying pattern rule with stem 'Makefile.c'.
    Trying implicit prerequisite 'Makefile.c,v'.
    Trying pattern rule with stem 'Makefile.c'.
    Trying implicit prerequisite 'RCS/Makefile.c,v'.
    Trying pattern rule with stem 'Makefile.c'.
    Trying implicit prerequisite 'RCS/Makefile.c'.
    Trying pattern rule with stem 'Makefile.c'.
    Trying implicit prerequisite 's.Makefile.c'.
    Trying pattern rule with stem 'Makefile.c'.
    Trying implicit prerequisite 'SCCS/s.Makefile.c'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.y'.
    Looking for a rule with intermediate file 'Makefile.y'.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Trying pattern rule with stem 'Makefile.y'.
     Trying implicit prerequisite 'Makefile.y,v'.
     Trying pattern rule with stem 'Makefile.y'.
     Trying implicit prerequisite 'RCS/Makefile.y,v'.
     Trying pattern rule with stem 'Makefile.y'.
     Trying implicit prerequisite 'RCS/Makefile.y'.
     Trying pattern rule with stem 'Makefile.y'.
     Trying implicit prerequisite 's.Makefile.y'.
     Trying pattern rule with stem 'Makefile.y'.
     Trying implicit prerequisite 'SCCS/s.Makefile.y'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.l'.
    Looking for a rule with intermediate file 'Makefile.l'.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Trying pattern rule with stem 'Makefile.l'.
     Trying implicit prerequisite 'Makefile.l,v'.
     Trying pattern rule with stem 'Makefile.l'.
     Trying implicit prerequisite 'RCS/Makefile.l,v'.
     Trying pattern rule with stem 'Makefile.l'.
     Trying implicit prerequisite 'RCS/Makefile.l'.
     Trying pattern rule with stem 'Makefile.l'.
     Trying implicit prerequisite 's.Makefile.l'.
     Trying pattern rule with stem 'Makefile.l'.
     Trying implicit prerequisite 'SCCS/s.Makefile.l'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.w'.
    Looking for a rule with intermediate file 'Makefile.w'.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Trying pattern rule with stem 'Makefile.w'.
     Trying implicit prerequisite 'Makefile.w,v'.
     Trying pattern rule with stem 'Makefile.w'.
     Trying implicit prerequisite 'RCS/Makefile.w,v'.
     Trying pattern rule with stem 'Makefile.w'.
     Trying implicit prerequisite 'RCS/Makefile.w'.
     Trying pattern rule with stem 'Makefile.w'.
     Trying implicit prerequisite 's.Makefile.w'.
     Trying pattern rule with stem 'Makefile.w'.
     Trying implicit prerequisite 'SCCS/s.Makefile.w'.
    Trying pattern rule with stem 'Makefile'.
    Rejecting impossible implicit prerequisite 'Makefile.w'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.cc'.
   Looking for a rule with intermediate file 'Makefile.cc'.
    Avoiding implicit rule recursion.
    Avoiding implicit rule recursion.
    Trying pattern rule with stem 'Makefile.cc'.
    Trying implicit prerequisite 'Makefile.cc,v'.
    Trying pattern rule with stem 'Makefile.cc'.
    Trying implicit prerequisite 'RCS/Makefile.cc,v'.
    Trying pattern rule with stem 'Makefile.cc'.
    Trying implicit prerequisite 'RCS/Makefile.cc'.
    Trying pattern rule with stem 'Makefile.cc'.
    Trying implicit prerequisite 's.Makefile.cc'.
    Trying pattern rule with stem 'Makefile.cc'.
    Trying implicit prerequisite 'SCCS/s.Makefile.cc'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.C'.
   Looking for a rule with intermediate file 'Makefile.C'.
    Avoiding implicit rule recursion.
    Avoiding implicit rule recursion.
    Trying pattern rule with stem 'Makefile.C'.
    Trying implicit prerequisite 'Makefile.C,v'.
    Trying pattern rule with stem 'Makefile.C'.
    Trying implicit prerequisite 'RCS/Makefile.C,v'.
    Trying pattern rule with stem 'Makefile.C'.
    Trying implicit prerequisite 'RCS/Makefile.C'.
    Trying pattern rule with stem 'Makefile.C'.
    Trying implicit prerequisite 's.Makefile.C'.
    Trying pattern rule with stem 'Makefile.C'.
    Trying implicit prerequisite 'SCCS/s.Makefile.C'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.cpp'.
   Looking for a rule with intermediate file 'Makefile.cpp'.
    Avoiding implicit rule recursion.
    Avoiding implicit rule recursion.
    Trying pattern rule with stem 'Makefile.cpp'.
    Trying implicit prerequisite 'Makefile.cpp,v'.
    Trying pattern rule with stem 'Makefile.cpp'.
    Trying implicit prerequisite 'RCS/Makefile.cpp,v'.
    Trying pattern rule with stem 'Makefile.cpp'.
    Trying implicit prerequisite 'RCS/Makefile.cpp'.
    Trying pattern rule with stem 'Makefile.cpp'.
    Trying implicit prerequisite 's.Makefile.cpp'.
    Trying pattern rule with stem 'Makefile.cpp'.
    Trying implicit prerequisite 'SCCS/s.Makefile.cpp'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.p'.
   Looking for a rule with intermediate file 'Makefile.p'.
    Avoiding implicit rule recursion.
    Avoiding implicit rule recursion.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.web'.
    Trying pattern rule with stem 'Makefile.p'.
    Trying implicit prerequisite 'Makefile.p,v'.
    Trying pattern rule with stem 'Makefile.p'.
    Trying implicit prerequisite 'RCS/Makefile.p,v'.
    Trying pattern rule with stem 'Makefile.p'.
    Trying implicit prerequisite 'RCS/Makefile.p'.
    Trying pattern rule with stem 'Makefile.p'.
    Trying implicit prerequisite 's.Makefile.p'.
    Trying pattern rule with stem 'Makefile.p'.
    Trying implicit prerequisite 'SCCS/s.Makefile.p'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.web'.
    Looking for a rule with intermediate file 'Makefile.web'.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Trying pattern rule with stem 'Makefile.web'.
     Trying implicit prerequisite 'Makefile.web,v'.
     Trying pattern rule with stem 'Makefile.web'.
     Trying implicit prerequisite 'RCS/Makefile.web,v'.
     Trying pattern rule with stem 'Makefile.web'.
     Trying implicit prerequisite 'RCS/Makefile.web'.
     Trying pattern rule with stem 'Makefile.web'.
     Trying implicit prerequisite 's.Makefile.web'.
     Trying pattern rule with stem 'Makefile.web'.
     Trying implicit prerequisite 'SCCS/s.Makefile.web'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.f'.
   Looking for a rule with intermediate file 'Makefile.f'.
    Avoiding implicit rule recursion.
    Avoiding implicit rule recursion.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.F'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.r'.
    Trying pattern rule with stem 'Makefile.f'.
    Trying implicit prerequisite 'Makefile.f,v'.
    Trying pattern rule with stem 'Makefile.f'.
    Trying implicit prerequisite 'RCS/Makefile.f,v'.
    Trying pattern rule with stem 'Makefile.f'.
    Trying implicit prerequisite 'RCS/Makefile.f'.
    Trying pattern rule with stem 'Makefile.f'.
    Trying implicit prerequisite 's.Makefile.f'.
    Trying pattern rule with stem 'Makefile.f'.
    Trying implicit prerequisite 'SCCS/s.Makefile.f'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.F'.
    Looking for a rule with intermediate file 'Makefile.F'.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Trying pattern rule with stem 'Makefile.F'.
     Trying implicit prerequisite 'Makefile.F,v'.
     Trying pattern rule with stem 'Makefile.F'.
     Trying implicit prerequisite 'RCS/Makefile.F,v'.
     Trying pattern rule with stem 'Makefile.F'.
     Trying implicit prerequisite 'RCS/Makefile.F'.
     Trying pattern rule with stem 'Makefile.F'.
     Trying implicit prerequisite 's.Makefile.F'.
     Trying pattern rule with stem 'Makefile.F'.
     Trying implicit prerequisite 'SCCS/s.Makefile.F'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.r'.
    Looking for a rule with intermediate file 'Makefile.r'.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Trying pattern rule with stem 'Makefile'.
     Rejecting impossible implicit prerequisite 'Makefile.l'.
     Trying pattern rule with stem 'Makefile.r'.
     Trying implicit prerequisite 'Makefile.r,v'.
     Trying pattern rule with stem 'Makefile.r'.
     Trying implicit prerequisite 'RCS/Makefile.r,v'.
     Trying pattern rule with stem 'Makefile.r'.
     Trying implicit prerequisite 'RCS/Makefile.r'.
     Trying pattern rule with stem 'Makefile.r'.
     Trying implicit prerequisite 's.Makefile.r'.
     Trying pattern rule with stem 'Makefile.r'.
     Trying implicit prerequisite 'SCCS/s.Makefile.r'.
   Trying pattern rule with stem 'Makefile'.
   Rejecting impossible implicit prerequisite 'Makefile.F'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.m'.
   Looking for a rule with intermediate file 'Makefile.m'.
    Avoiding implicit rule recursion.
    Avoiding implicit rule recursion.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.ym'.
    Trying pattern rule with stem 'Makefile.m'.
    Trying implicit prerequisite 'Makefile.m,v'.
    Trying pattern rule with stem 'Makefile.m'.
    Trying implicit prerequisite 'RCS/Makefile.m,v'.
    Trying pattern rule with stem 'Makefile.m'.
    Trying implicit prerequisite 'RCS/Makefile.m'.
    Trying pattern rule with stem 'Makefile.m'.
    Trying implicit prerequisite 's.Makefile.m'.
    Trying pattern rule with stem 'Makefile.m'.
    Trying implicit prerequisite 'SCCS/s.Makefile.m'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.ym'.
    Looking for a rule with intermediate file 'Makefile.ym'.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Trying pattern rule with stem 'Makefile.ym'.
     Trying implicit prerequisite 'Makefile.ym,v'.
     Trying pattern rule with stem 'Makefile.ym'.
     Trying implicit prerequisite 'RCS/Makefile.ym,v'.
     Trying pattern rule with stem 'Makefile.ym'.
     Trying implicit prerequisite 'RCS/Makefile.ym'.
     Trying pattern rule with stem 'Makefile.ym'.
     Trying implicit prerequisite 's.Makefile.ym'.
     Trying pattern rule with stem 'Makefile.ym'.
     Trying implicit prerequisite 'SCCS/s.Makefile.ym'.
   Trying pattern rule with stem 'Makefile'.
   Rejecting impossible implicit prerequisite 'Makefile.r'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.s'.
   Looking for a rule with intermediate file 'Makefile.s'.
    Avoiding implicit rule recursion.
    Avoiding implicit rule recursion.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.S'.
    Trying pattern rule with stem 'Makefile.s'.
    Trying implicit prerequisite 'Makefile.s,v'.
    Trying pattern rule with stem 'Makefile.s'.
    Trying implicit prerequisite 'RCS/Makefile.s,v'.
    Trying pattern rule with stem 'Makefile.s'.
    Trying implicit prerequisite 'RCS/Makefile.s'.
    Trying pattern rule with stem 'Makefile.s'.
    Trying implicit prerequisite 's.Makefile.s'.
    Trying pattern rule with stem 'Makefile.s'.
    Trying implicit prerequisite 'SCCS/s.Makefile.s'.
    Trying pattern rule with stem 'Makefile'.
    Trying implicit prerequisite 'Makefile.S'.
    Looking for a rule with intermediate file 'Makefile.S'.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Avoiding implicit rule recursion.
     Trying pattern rule with stem 'Makefile.S'.
     Trying implicit prerequisite 'Makefile.S,v'.
     Trying pattern rule with stem 'Makefile.S'.
     Trying implicit prerequisite 'RCS/Makefile.S,v'.
     Trying pattern rule with stem 'Makefile.S'.
     Trying implicit prerequisite 'RCS/Makefile.S'.
     Trying pattern rule with stem 'Makefile.S'.
     Trying implicit prerequisite 's.Makefile.S'.
     Trying pattern rule with stem 'Makefile.S'.
     Trying implicit prerequisite 'SCCS/s.Makefile.S'.
   Trying pattern rule with stem 'Makefile'.
   Rejecting impossible implicit prerequisite 'Makefile.S'.
   Trying pattern rule with stem 'Makefile'.
   Trying implicit prerequisite 'Makefile.mod'.
   Looking for a rule with intermediate file 'Makefile.mod'.
    Avoiding implicit rule recursion.
    Avoiding implicit rule recursion.
    Trying pattern rule with stem 'Makefile.mod'.
    Trying implicit prerequisite 'Makefile.mod,v'.
    Trying pattern rule with stem 'Makefile.mod'.
    Trying implicit prerequisite 'RCS/Makefile.mod,v'.
    Trying pattern rule with stem 'Makefile.mod'.
    Trying implicit prerequisite 'RCS/Makefile.mod'.
    Trying pattern rule with stem 'Makefile.mod'.
    Trying implicit prerequisite 's.Makefile.mod'.
    Trying pattern rule with stem 'Makefile.mod'.
    Trying implicit prerequisite 'SCCS/s.Makefile.mod'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.c'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.cc'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.C'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.cpp'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.p'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.f'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.F'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.m'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.r'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.s'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.S'.
  Trying pattern rule with stem 'Makefile'.
  Rejecting impossible implicit prerequisite 'Makefile.mod'.
  Trying pattern rule with stem 'Makefile'.
  Trying implicit prerequisite 'Makefile.sh'.
  Looking for a rule with intermediate file 'Makefile.sh'.
   Avoiding implicit rule recursion.
   Trying pattern rule with stem 'Makefile.sh'.
   Trying implicit prerequisite 'Makefile.sh,v'.
   Trying pattern rule with stem 'Makefile.sh'.
   Trying implicit prerequisite 'RCS/Makefile.sh,v'.
   Trying pattern rule with stem 'Makefile.sh'.
   Trying implicit prerequisite 'RCS/Makefile.sh'.
   Trying pattern rule with stem 'Makefile.sh'.
   Trying implicit prerequisite 's.Makefile.sh'.
   Trying pattern rule with stem 'Makefile.sh'.
   Trying implicit prerequisite 'SCCS/s.Makefile.sh'.
  No implicit rule found for 'Makefile'.
  Finished prerequisites of target file 'Makefile'.
 No need to remake target 'Makefile'.
Updating goal targets....
Considering target file 'all'.
 File 'all' does not exist.
  Considering target file '/priv/lib/picosat_elixir/priv/picosat_nif.so'.
   File '/priv/lib/picosat_elixir/priv/picosat_nif.so' does not exist.
    Considering target file '/priv/picosat.o'.
     File '/priv/picosat.o' does not exist.
      Considering target file '/c_src/picosat.c'.
       File '/c_src/picosat.c' does not exist.
       Looking for an implicit rule for '/c_src/picosat.c'.
       Trying pattern rule with stem 'picosat'.
       Trying implicit prerequisite '/c_src/picosat.y'.
       Trying pattern rule with stem 'picosat'.
       Trying implicit prerequisite '/c_src/picosat.l'.
       Trying pattern rule with stem 'picosat'.
       Trying implicit prerequisite '/c_src/picosat.w'.
       Trying pattern rule with stem 'picosat'.
       Trying implicit prerequisite '/c_src/picosat.w'.
       Trying pattern rule with stem 'picosat.c'.
       Trying implicit prerequisite '/c_src/picosat.c,v'.
       Trying pattern rule with stem 'picosat.c'.
       Trying implicit prerequisite '/c_src/RCS/picosat.c,v'.
       Trying pattern rule with stem 'picosat.c'.
       Trying implicit prerequisite '/c_src/RCS/picosat.c'.
       Trying pattern rule with stem 'picosat.c'.
       Trying implicit prerequisite '/c_src/s.picosat.c'.
       Trying pattern rule with stem 'picosat.c'.
       Trying implicit prerequisite '/c_src/SCCS/s.picosat.c'.
       Trying pattern rule with stem 'picosat'.
       Trying implicit prerequisite '/c_src/picosat.y'.
       Looking for a rule with intermediate file '/c_src/picosat.y'.
        Avoiding implicit rule recursion.
        Trying pattern rule with stem 'picosat.y'.
        Trying implicit prerequisite '/c_src/picosat.y,v'.
        Trying pattern rule with stem 'picosat.y'.
        Trying implicit prerequisite '/c_src/RCS/picosat.y,v'.
        Trying pattern rule with stem 'picosat.y'.
        Trying implicit prerequisite '/c_src/RCS/picosat.y'.
        Trying pattern rule with stem 'picosat.y'.
        Trying implicit prerequisite '/c_src/s.picosat.y'.
        Trying pattern rule with stem 'picosat.y'.
        Trying implicit prerequisite '/c_src/SCCS/s.picosat.y'.
       Trying pattern rule with stem 'picosat'.
       Trying implicit prerequisite '/c_src/picosat.l'.
       Looking for a rule with intermediate file '/c_src/picosat.l'.
        Avoiding implicit rule recursion.
        Trying pattern rule with stem 'picosat.l'.
        Trying implicit prerequisite '/c_src/picosat.l,v'.
        Trying pattern rule with stem 'picosat.l'.
        Trying implicit prerequisite '/c_src/RCS/picosat.l,v'.
        Trying pattern rule with stem 'picosat.l'.
        Trying implicit prerequisite '/c_src/RCS/picosat.l'.
        Trying pattern rule with stem 'picosat.l'.
        Trying implicit prerequisite '/c_src/s.picosat.l'.
        Trying pattern rule with stem 'picosat.l'.
        Trying implicit prerequisite '/c_src/SCCS/s.picosat.l'.
       Trying pattern rule with stem 'picosat'.
       Trying implicit prerequisite '/c_src/picosat.w'.
       Looking for a rule with intermediate file '/c_src/picosat.w'.
        Avoiding implicit rule recursion.
        Trying pattern rule with stem 'picosat.w'.
        Trying implicit prerequisite '/c_src/picosat.w,v'.
        Trying pattern rule with stem 'picosat.w'.
        Trying implicit prerequisite '/c_src/RCS/picosat.w,v'.
        Trying pattern rule with stem 'picosat.w'.
        Trying implicit prerequisite '/c_src/RCS/picosat.w'.
        Trying pattern rule with stem 'picosat.w'.
        Trying implicit prerequisite '/c_src/s.picosat.w'.
        Trying pattern rule with stem 'picosat.w'.
        Trying implicit prerequisite '/c_src/SCCS/s.picosat.w'.
       Trying pattern rule with stem 'picosat'.
       Rejecting impossible implicit prerequisite '/c_src/picosat.w'.
       No implicit rule found for '/c_src/picosat.c'.
       Finished prerequisites of target file '/c_src/picosat.c'.
      Must remake target '/c_src/picosat.c'.
make: *** No rule to make target '/c_src/picosat.c', needed by '/priv/picosat.o'.  Stop.

Update: Compiling inside dev command prompt for vs 2019 successfully compiles the project, but I still get the following warning and error. Is this expected?
warning: :picosat_nif.solve/1 is undefined (module :picosat_nif is not available or is yet to be defined)
  lib/solver/picosat.ex:14: Picosat.Solver.solve/1

Generated picosat_elixir app

17:19:36.623 [warning] The on_load function for module picosat_nif returned:
{{:badmatch,
  {:error,
   {:load_failed,
    'Failed to load NIF library c:/dev/hub/_build/dev/lib/picosat_elixir/priv/picosat_nif: \'Unspecified error\''}}},
 [
   {:picosat_nif, :init, 0, [file: 'src/picosat_nif.erl', line: 9]},
   {:code_server, :"-handle_on_load/5-fun-0-", 1,
    [file: 'code_server.erl', line: 1317]}
 ]}

It looks like initially it was trying to build with the Makefile, rather than Makefile.win. Running in the VS2019 command prompt presumably uses the latter which is why it succeeds. It looks like the expected output is missing though, or there is something wrong with it. Do you have a picosat_nif.dll file in priv? It should be created by the build if it succeeds. If it is there, you might want to try deleting it and rebuilding again, in case something went wrong with the build the first time.

Thanks! Ill see if that helps. In the meantime will close this as it is working using the vs cmd prompt.

I wanted to go through the Livebooks at A Gentle Primer to Ash on Windows. After installing Microsoft Visual Studio Community, which installed the vcvarsall.bat script and the updating my PATH for the nmake utility, I still got a compile error.
Not sure why but the compiler wasn't able to find stdlib.h and signal.h.
PS C:\Users\USER> & "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64
**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.7.4
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
PS C:\Users\USER> iex.bat
Erlang/OTP 26 [erts-14.1] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit:ns]

Interactive Elixir (1.15.6) - press Ctrl+C to exit (type h() ENTER for help)
iex(1)> Mix.install [:picosat_elixir]
==> picosat_elixir

Microsoft (R) Program Maintenance Utility Version 14.37.32824.0
Copyright (C) Microsoft Corporation.  All rights reserved.

        if NOT EXIST "c:/Users/USER/AppData/Local/mix/Cache/installs/elixir-1.15.6-erts-14.1/6894cf6c1d948e5cf085b1b42da01329/_build/dev/lib/picosat_elixir" mkdir "c:/Users/USER/AppData/Local/mix/Cache/installs/elixir-1.15.6-erts-14.1/6894cf6c1d948e5cf085b1b42da01329/_build/dev/lib/picosat_elixir"
        if NOT EXIST "c:/Users/USER/AppData/Local/mix/Cache/installs/elixir-1.15.6-erts-14.1/6894cf6c1d948e5cf085b1b42da01329/_build/dev/lib/picosat_elixir\priv" mkdir "c:/Users/USER/AppData/Local/mix/Cache/installs/elixir-1.15.6-erts-14.1/6894cf6c1d948e5cf085b1b42da01329/_build/dev/lib/picosat_elixir\priv"
        cl /DNGETRUSAGE=1 /Ob2 /Wall /I"c_src" /I"c:/Users/USER/scoop/apps/erlang/26.1.1/erts-14.1/include"  /LD /MD /Fec:/Users/USER/AppData/Local/mix/Cache/installs/elixir-1.15.6-erts-14.1/6894cf6c1d948e5cf085b1b42da01329/_build/dev/lib/picosat_elixir\priv\picosat_nif.dll c_src\*.c
Microsoft (R) C/C++ Optimizing Compiler Version 19.37.32824 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

picosat.c
c_src\picosat.c(23): fatal error C1083: Cannot open include file: 'stdlib.h': No such file or directory
picosat_nif.c
c_src\picosat_nif.c(1): fatal error C1083: Cannot open include file: 'signal.h': No such file or directory
Generating Code...
NMAKE : fatal error U1077: 'cl /DNGETRUSAGE=1 /Ob2 /Wall /I"c_src" /I"c:/Users/USER/scoop/apps/erlang/26.1.1/erts-14.1/include"  /LD /MD /Fec:/Users/USER/AppData/Local/mix/Cache/installs/elixir-1.15.6-erts-14.1/6894cf6c1d948e5cf085b1b42da01329/_build/dev/lib/picosat_elixir\priv\picosat_nif.dll c_src\*.c' : return code '0x2'
Stop.
could not compile dependency :picosat_elixir, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile picosat_elixir --force", update it with "mix deps.update picosat_elixir" or clean it with "mix deps.clean picosat_elixir"
** (Mix.Error) Could not compile with "nmake" (exit status: 2).
One option is to install a recent version of
[Visual C++ Build Tools](https://visualstudio.microsoft.com/visual-cpp-build-tools/)
either manually or using [Chocolatey](https://chocolatey.org/) -
`choco install VisualCppBuildTools`.

After installing Visual C++ Build Tools, look in the "Program Files (x86)"
directory and search for "Microsoft Visual Studio". Note down the full path
of the folder with the highest version number. Open the "run" command and
type in the following command (make sure that the path and version number
are correct):

    cmd /K "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64

This should open up a command prompt with the necessary environment variables
set, and from which you will be able to run the "mix compile", "mix deps.compile",
and "mix test" commands.

Another option is to install the Linux compatiblity tools from [MSYS2](https://www.msys2.org/).

After installation start the msys64 bit terminal from the start menu and install the
C/C++ compiler toolchain. E.g.:

  pacman -S --noconfirm pacman-mirrors pkg-config
  pacman -S --noconfirm --needed base-devel autoconf automake make libtool git \
    mingw-w64-x86_64-toolchain mingw-w64-x86_64-openssl mingw-w64-x86_64-libtool

This will give you a compilation suite nearly compatible with Unix' standard tools.

    (mix 1.15.6) lib/mix.ex:577: Mix.raise/2
    (elixir_make 0.7.7) lib/elixir_make/compiler.ex:53: ElixirMake.Compiler.compile/1
    (mix 1.15.6) lib/mix/task.ex:447: anonymous fn/3 in Mix.Task.run_task/5
    (mix 1.15.6) lib/mix/tasks/compile.all.ex:124: Mix.Tasks.Compile.All.run_compiler/2
    (mix 1.15.6) lib/mix/tasks/compile.all.ex:104: Mix.Tasks.Compile.All.compile/4
    (mix 1.15.6) lib/mix/tasks/compile.all.ex:93: Mix.Tasks.Compile.All.with_logger_app/2
    (mix 1.15.6) lib/mix/tasks/compile.all.ex:56: Mix.Tasks.Compile.All.run/1
    (mix 1.15.6) lib/mix/task.ex:447: anonymous fn/3 in Mix.Task.run_task/5

A bit more context:
I am on Windows. Installed Elixir via scoop
I also installed the C/C++ compiler toolchain via MSYS2, and then tried to run Mix.install [:picosat_elixir], still no luck.
I am able to install it via the Developer Powershell for VS similar to @nadavhames, but I was wondering if there's any way to do that without installing a lot of things.
It might be that for me, I won't be able to install any Elixir/Erlang package that has a NIF, but I'd still like to leave a comment here for anyone else that faces a similar issue.

@Animesh-Ghosh This is what I did to compile picosat_elixir on Windows.
set path=C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\SDK\ScopeCppSDK\VC\bin;%path%
set lib=C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\SDK\ScopeCppSDK\SDK\lib;C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\SDK\ScopeCppSDK\VC\lib
set include=C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\SDK\ScopeCppSDK\SDK\include\ucrt;C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\SDK\ScopeCppSDK\VC\include


Simplify tags

Just noticed while skimming that this file seemed drastically over-complicated.
As the keys are all consts, this should mean that the net change for all this is that these take one slice pointer more space per instance.  And binary size is slightly smaller due to fewer types / a smaller type->interface lookup table.
Separately, now that it's simpler, some of the variations are more noticeable.
It may be worth standardizing further, e.g.:

sanitizing everything (except perhaps the kafka partition)
get rid of the "unknown" constructors?  I can see them having some use, but it seems kinda random what has it and what doesn't.

Coverage decreased (-0.1%) to 61.594% when pulling 6a27b4d544c33539889d4dcf7e0d7e2749796c25 on tags into 88e1b650eb75787d281093478a53147c5483bc48 on master.

Coverage decreased (-0.1%) to 61.594% when pulling 6a27b4d544c33539889d4dcf7e0d7e2749796c25 on tags into 88e1b650eb75787d281093478a53147c5483bc48 on master.


System error, Python version mismatch and triton==2.0.0 installation

To get started with demo, 3.10 is installed, but when installing the required libraries, the following bug appears:
ERROR: Ignored the following versions that require a different python version: 1.6.2 Requires-Python >=3.7,<3.10; 1.6.3 Requires-Python >=3.7,<3.10; 1.7.0 Requires-Python >=3.7,<3.10; 1.7.1 Requires-Python >=3.7,<3.10
ERROR: Could not find a version that satisfies the requirement triton==2.0.0 (from versions: none)
ERROR: No matching distribution found for triton==2.0.0

Make sure to include the repository hosting Triton 2.0.0 in your package manager's sources. If it hasn't been added yet, the version you're seeking might not be accessible to your package manager.


sql_database source with pyarrow backend does not support json typed columns from MySQL

dlt version
0.5.1
Source name
sql_database
Describe the problem
Upon running a pipeline with a MySQL sql_table source and pyarrow backend, the extraction process fails on source tables with json typed columns. Stack trace:
Traceback (most recent call last):
  File "/path/to/project/sql_database/helpers.py", line 142, in _load_rows
    yield row_tuples_to_arrow(
  File "/path/to/project/sql_database/arrow_helpers.py", line 140, in row_tuples_to_arrow
    return pa.Table.from_pydict(columnar_known_types, schema=arrow_schema)
  File "pyarrow/table.pxi", line 1920, in pyarrow.lib._Tabular.from_pydict
  File "pyarrow/table.pxi", line 6153, in pyarrow.lib._from_pydict
  File "pyarrow/array.pxi", line 398, in pyarrow.lib.asarray
  File "pyarrow/array.pxi", line 358, in pyarrow.lib.array
  File "pyarrow/array.pxi", line 85, in pyarrow.lib._ndarray_to_array
  File "pyarrow/error.pxi", line 92, in pyarrow.lib.check_status
pyarrow.lib.ArrowTypeError: Expected bytes, got a 'dict' object

Source: sql_database
Source db: MySQL version 8.0.32
Destination: Snowflake

Expected behavior
No response
Steps to reproduce

Create a sql_table source with a pyarrow backend:

    table_source = sql_table(
        credentials=mysql_engine,
        table=table_name_with_json_columns,
        backend="pyarrow",
    )

Run pipeline:

    pipeline_run_result = pipeline.run(
        table_source, write_disposition="replace"
    )

How you are using the source?
I'm considering using this source in my work, but bug is preventing this.
Operating system
Linux
Runtime environment
Docker, Docker Compose
Python version
3.10.12
dlt destination
Snowflake
Additional information
No response

This has been fixed by https://github.com/dlt-hub/verified-sources/pull/541


CoverageError when trying coffee-coverage-loader.js

node v4.2.6
when

./node_modules/.bin/mocha -R spec --compilers coffee:coffee-script/register --require ./coffee-coverage-loader

I get

(node) child_process: options.customFds option is deprecated. Use options.stdio instead.
/home/kfm/code/ds3g/readin/node_modules/coffee-coverage/lib/coffeeCoverage.js:279
throw new CoverageError("Could not parse " + fileName + ": " + err.stack);
^
CoverageError: Could not parse /home/kfm/code/ds3g/readin/node_modules/halbert/node_modules/browserify/node_modules/browser-resolve/test/fixtures-coffee/foo.coffee: SyntaxError: unexpected //
at Object.exports._runInstrumentor (/home/kfm/code/ds3g/readin/node_modules/coffee-coverage/lib/coffeeCoverage.js:279:13)
at CoverageInstrumentor.exports.CoverageInstrumentor.CoverageInstrumentor.instrumentCoffee (/home/kfm/code/ds3g/readin/node_modules/coffee-coverage/lib/coffeeCoverage.js:237:24)
at CoverageInstrumentor.exports.CoverageInstrumentor.CoverageInstrumentor.instrumentFile (/home/kfm/code/ds3g/readin/node_modules/coffee-coverage/lib/coffeeCoverage.js:219:21)
at CoverageInstrumentor.exports.CoverageInstrumentor.CoverageInstrumentor.instrumentDirectory (/home/kfm/code/ds3g/readin/node_modules/coffee-coverage/lib/coffeeCoverage.js:196:27)
at CoverageInstrumentor.exports.CoverageInstrumentor.CoverageInstrumentor.instrumentDirectory (/home/kfm/code/ds3g/readin/node_modules/coffee-coverage/lib/coffeeCoverage.js:182:23)

coffee-coverage-loader.js is copy-paste from sample...

FIX;
changed exclude into
  exclude: ['**/test', '**/node_modules', '**/.git'],

Hmm... Sounds like we broke something when we added glob support in 1.0.0.

Ok, this is weird though, because I just tried upgrading to latest coffee-coverage in amqp-connnection-manager, and it runs fine, even though it's using the defaults.  Even if I npm install halbert, so I have this exact same file locally...
Do you have an example project that reproduces this?  Also, when you're running mocha, you're running it a ./node_modules/.bin/mocha?  Not trying to run it from another folder?
Thanks!

yes,
My halberd ver tag is ^0.1.0 if it helps.
Im fine as long as I use this file

var COV_DIR = 'coverage';
var COV_DEST = 'coverage-coffee.json';
var path = require('path');
var coffeeCoverage = require('coffee-coverage');
var projectRoot = __dirname;
var coverageVar = coffeeCoverage.findIstanbulVariable();
// Only write a coverage report if we're not running inside of Istanbul.
/* jshint ignore:start /
var writeOnExit = (coverageVar == null) ? (projectRoot + '/' + COV_DIR + '/' + COV_DEST) : null;
/ jshint ignore:end */
// console.warn ("coverageVar:", coverageVar);
// console.warn ("writeOnExit:", writeOnExit);
// console.warn ("pRoot:", projectRoot);
coffeeCoverage.register({
instrumentor: 'istanbul',
basePath: projectRoot,
exclude: ['test', 'node_modules', '.git', 'features', '_*' ,'coverage'],
coverageVar: coverageVar,
writeOnExit: writeOnExit,
initAll: true
});


[Discussion] Virtualization Inception Issues

Regarding the IPI baremetal install on virtualized hosts, I'm using a virtualized RHEL8 system as the provisioner host. The provisioning VM does get deployed but never gets an IP address for some odd reason. I'm following Craig Robertson's guide: Guide to Installing OpenShift 4.10 IPI on Bare Metal
Did you manage to get this setup working to some degree (or at least have the provisioner VM get IPs on the baremetal and provisioning network interfaces)?

Hi @fahadysf. Yes, the described setup did work for me quite well back then. If you're following my setup, then I'd guess you did not get the veth pair working and the DHCP does not propagate to the brridge called "baremetal"


Script error

/timer: insufficient parameters (line 4362, main.nbs),

Appears sometimes, randomly .

This seems related to Netsplits, I will try to find the underlying issue. Thanks for the report.

latest version 7.46 has this error.


IRGen: Use clang's codegen for protocol decls

There are certain protocol method decls types that swift does not import today.
@protocol Incomplete
- (id)getObjectFromVarArgs:(id)first, ...;
@end

Furthermore, the old method also emitted duplicate entries for protocols methods when Swift synthesized methods for diagnosics.
We won't import this method into Swift. So if we emit protocol metadata from swift delcs we would generate incomplete records.
rdar://60888524

@swift-ci test source compat

@swift-ci test source compatibility release


Compat: avoid PHP notices when using PHP 8.2

Proposed changes:
This PR should just avoid a PHP notice when using PHP 8.2:
PHP Deprecated:  Creation of dynamic property Activitypub\Transformer\Post::$attachments is deprecated in /var/www/html/wp-content/plugins/activitypub/includes/transformer/class-post.php on line 249

Other information:

[ ] Have you written new tests for your changes, if applicable?

Testing instructions:
Not much to test here; if you have a local installation of WordPress using PHP 8.2, you should no longer see the deprecation notice when trying to access a post in an ActivityPub request.

Good catch! But I would prefer to simply remove $this->attachments = $images; in the get_attachment function. This seems to be a Copy&Paste issue that comes from the old Post-Model. In the actual case, there seems to be no need to have it as a Object-Attribute.

I'm not at all familiar with the codebase; do you mean I should get rid of it entirely?
diff --git a/includes/transformer/class-post.php b/includes/transformer/class-post.php
index 6f1fed3..e9453dc 100644
--- a/includes/transformer/class-post.php
+++ b/includes/transformer/class-post.php
@@ -28,13 +28,6 @@ class Post {
 	 */
 	protected $wp_post;

-	/**
-	 * Attachment images, used in the content.
-	 *
-	 * @var array
-	 */
-	protected $attachments = array();
-
 	/**
 	 * The Allowed Tags, used in the content.
 	 *
@@ -253,8 +246,6 @@ class Post {
 			}
 		}

-		$this->attachments = $images;
-
 		return $images;
 	}

Yes, not needed anymore.

👍 Done.


common Paint: Add name getter/setter API

Adds an API that can set/get string type name to tvgPaint.
This can be used when the user needs to traverse the scene tree or find a specific instance.
+) The SVG's "id" attribute is set to name when SVG is loaded.

This is a simple solution for https://github.com/Samsung/thorvg/issues/1276.
I think the size(cost) of tvgPaint can up unnecessarily. and it can not be used universally except in special cases.
What do you think?

Rebased PR

@hermet Do you have any comments for updates? At the time this patch was written, it wasn't a necessary thing. There were comments related to hashing, but I can't pay attention to them for a long time. (If hashing, it can be used more widly, but for now, I think it is over-spec. It can be sufficiently improved in the future.)
Or someone can take this task.

@JSUYA I agree with @kariem2k's opinion; ThorVG could save memory in general cases if it has a name with a single reference id. Thus, the usage would be something like this
bool paint->identify(string);   //Internally encode the string to a hash ID and compare its value.

Yet my question is whether tvg::Paint needs to return the name as a string or not. If so, how can it be done without any cost. On consideration.

Yet my question is whether tvg::Paint needs to return the name as a string or not. If so, how can it be done without any cost. On consideration.

It is not necessary to return it as a string. We can use if(Accessor::hashToString(paint->id()) == "ID") .

Accessor::hashToString

If ThorVG should support value recovery, then I guess hashing wouldn't be beneficial.

@JSUYA Please have a look at this. I'm not sure about this feature for SVG since there have been no practical requirements so far. It will just make things difficult for the SVG loader without any purpose.
https://github.com/thorvg/thorvg/pull/2334/commits/a0b1e502c25b01daba7b9e0876dc1e5b0c23782c
https://github.com/thorvg/thorvg/pull/2334/commits/380b6d596ee17fd68c047949ccac7ccd4bb1c852

@JSUYA Please have a look at this. I'm not sure about this feature for SVG since there have been no practical requirements so far. It will just make things difficult for the SVG loader without any purpose.
a0b1e50 380b6d5

Oh I've been waiting for your opinion since i think this discussion is not conclusive. I checked the contents of the hermet/type branch.
In my memory, this issue was requested by someone. https://github.com/thorvg/thorvg/issues/1276 But I don't remember
I agree that it is not a necessary feature now.
I'm closing this PR. If a feature related to this(string type return) is needed, it can be discussed again in a new place other than this PR.


[plugin] Add php.ini in the PHP plugin

Summary
Adds an editable php.ini to the PHP plugin. This is useful when developers need to configure their PHP instance, and by creating it in devbox.d we let developers customize it for each of their PHP projects. This addresses #1035 and the issue reported by @jrseliga
How was it tested?

On a clean PHP project, run devbox add php@latest and verify that the php.ini file is created in devbox.d
Also check the updated example in this PR

Thanks @Lagoja! Looks good to me, the php.ini file is published and it seems the settings defined within take precedent.

@Lagoja does php pick up the php.ini automatically? I thought it had to be in a special dir.

You can use the $PHPRC environment variable (which I added to the plugin) to tell PHP where to look for the php.ini file. It's the second location that PHP will look, after the SAPI module specific location:
https://www.php.net/manual/en/configuration.file.php
It seems to work on testing -- I can use it to set the xdebug mode, or to bump the memory limit for Django

missed that, awesome!

Going to tweak the examples to be backwards compatible, and then I'll merge


docker env vs docker build

Hi, I'm trying to solve problem with private pypi cloud and continues integration
My idea is:
custom:
  pythonRequirements:
    dockerizePip: true
    dockerFile: ./Dockerfile
    dockerEnv:
      - PIP_USERNAME
      - PIP_PASSWORD

But seems like I messed up docker env variables and docker build arguments.
Here is my dockerfile:
FROM lambci/lambda:build-python3.7

ARG PYPI_USERNAME
ARG PYPI_PASSWORD

RUN pip install --upgrade pip && \
    echo "machine your.private.pypi.cloud" >> ~/.netrc && \
    echo "  login $(echo $PYPI_USERNAME)" >> ~/.netrc && \
    echo "  password $(echo $PYPI_PASSWORD)" >> ~/.netrc && \
    chmod 600 ~/.netrc

May be someone can help me with this? Is there a possibility to pass build_args to custom docker?

Ow, I totally forgot about entrypoint command in docker. Changing my docker file to works perfectly.
FROM lambci/lambda:build-python3.7

ENTRYPOINT pip install --upgrade pip && \
    echo "machine your.private.pypi.cloud" >> ~/.netrc && \
    echo "  login $(echo $PYPI_USERNAME)" >> ~/.netrc && \
    echo "  password $(echo $PYPI_PASSWORD)" >> ~/.netrc && \
    chmod 600 ~/.netrc


IIS url rewrite with custom provider routing to Asp.Net core applications hosted by AspNetCoreModule

Hi,
I am facing following scenario:

Business case: routing customer aliases specified in URL to correct application version, e.g.:

/customer1/request -> /1.0.0/request
/customer2/request -> /1.0.5/request
/customer3/request -> /1.0.0/request

I am hosting multiple Asp.Net Core applications side by side via AspNetCoreModule on IIS (it uses pool 'No Managed Code')

Each application represents the same product on different version

I need to be able to route requests to specific application based on entry url
I cannot expose rewrited url back to the client (otherwise I could use redirect instead of rewrite, but it is not my case)
Routing is done via custom url rewrite provider, because it resolves rules based on settings in database

I cannot make it work, because:

IIS URL rewrite must run in the same App Pool as the target application

That means 'No Managed Code'

I need to use custom url rewrite provider, but it can only run on pool with managed code

How am I supposed to route requests to multiple Asp.Net Core applications on IIS?
Is there any way to achieve this?

@Matasx Move this over to IISIntegration repo issues: https://github.com/aspnet/IISIntegration/issues

Moved to https://github.com/aspnet/IISIntegration/issues/309


community stats page, switch column headers

Martin Kollmar "Community curation statistics: In the table "New curators per year" the column headers (or the column content) needs to be switched."
(some sort of selective blindness on my part, I have looked at these tables loads!)

Oh dear.  I've never noticed that either.
Fixed now.


Added awesome login form-25

@PuneethKshetty
PR merged now
Thanks for you contribution, PR counted for hacktoberfest.
Don't forget to star the repo
I would like to offer some swags from Loginradius ,to avail those please fill this form https://docs.google.com/forms/d/e/1FAIpQLSfnwWUWlRRwZpgmOX7X8lGMKotLbVe1JXCjPFSahLxLWugwig/viewform


Error in cupy's advanced indexing when an empty list is given

When an empty list is given as a selection object to numpy's advanced indexing, no item is selected for that axis.
>>> numpy.zeros((4,3,2))[[]]
array([], shape=(0, 3, 2), dtype=float64)

However, cupy's advanced indexing raises an error.
>>> cupy.zeros((4,3,2))[[]]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "cupy/core/core.pyx", line 1142, in cupy.core.core.ndarray.__getitem__ (cupy/core/core.cpp:23915)
    raise IndexError(
IndexError: arrays used as indices must be of integer or boolean type. (actual: <class 'numpy.float64'>)

Related to this bug, I found more.

[[]]  (double nested list)
numpy.array([], dtype=numpy.bool)   (a boolean array of size 0)

#2369 solved this issue, so I think we can close it.

Confirmed that it's fixed now. Thank you for reporting!


low information about load Identity table's  navigation from other custom models

[Enter feedback here]
there is no information about load navigation from non-identity tables that connect to identity tables ;

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

ID: d9869895-9ba2-5027-46cd-89d1d995cba4
Version Independent ID: 8750939b-6ae5-3b9a-6c32-5e84b7fea22c
Content: Identity model customization in ASP.NET Core
Content Source: aspnetcore/security/authentication/customize-identity-model.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @ajcvickers
Microsoft Alias: avickers

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog manageable. If you believe there is a concern which hasn't been addressed, please file a new issue.


Add support for block buttons based on specific screen widths, eg. btn-xs-block

This is an easy feature that anyone can implement with a little extra css, but I think it is a extremely common case that I think it would be necessary and useful for it to be built into Bootstrap.

I created #30376 for v5, but v4 can also achieve that. demo

This was addressed in v5 Alpha 3 with #31995

This was addressed in v5 Alpha 3 with #31995


The possibility of MPI implementation of StrobeAlign

Hello Kristoffer,
I saw an interesting reimplementation of BWA-MEM Using MPI (Message Passing Interface) here: https://github.com/bioinfo-pf-curie/mpiBWA
It seems a multi-node solution is becoming more appealing these days because most research groups have access to institution-hold HPC systems with thousands of computing nodes. The master process in MPI can just split reads into pieces and assign them to other processes on each node and collect (wait) results after all are done. I tested the mpiBWA with 10 node or something, a 25G Metagenome can be mapped to 500M genome in several minutes with exactly the same results with single node bwa mem. I think a mpiStrobeAlign will be insanely fast using 10 or so computer nodes.
Thanks,
Jianshu

It’s been a while since this issue has been opened, and while this is an interesting idea, realistically, I don’t see us implementing this anytime soon. So I would like to suggest to close this issue in order to keep the issue tracker a bit more tidy. We can add a tag so that we can still find it when anyone looks for something to work on.
While I’m here, I want to mention that maybe the need for an MPI version of strobealign may be reduced by just waiting for bigger nodes: We’ve recently switched our cluster from 20-core nodes to 128-core nodes. Since strobealign already scales up nicely to 128 cores, we get a sixfold speed improvement without having to do anything in the code. Strobealign is also already faster than BWA, so being restricted to a single node is just not such a big limitation IMO.


Added partition key support to spring data single partition queries

Added partition key support to spring data single partition queries

/azp run java - cosmos - tests


Token created don't have dynamic_last4 filled properly

When you create a card token with ApplePayStubs the dynamic_last4 property ends up null while the last4 property is filled but it should be the other way around.

This should be fixed now @remistr ! (and 👋)


update packages

This PR updates the packages to the latest compatible versions. Will need to coordinate this with the Tanssi package updates (https://github.com/papermoonio/tanssi-mkdocs/pull/11) and Opslayer.
With the latest version of material-mkdocs, a bunch of bug fixes around the navigation.instant feature were fixed, so now we can add it in. I haven't come across any issues with it. This feature makes it more of a single page application where the site doesn't reload every time you click on a new page. Makes the experience a bit smoother for users.

@albertov19 I fixed two things, so this needs to be reviewed again, please! It fixes:

the sticky header so it actually sticks! 😆  the build, node operators, etc. menu at the top should stay there as you scroll down the page. this was messed up when I applied the last fix for the safari issue
the double footer issue has been resolved. for some reason the footer was rendered from two different places, so this forces it to render from the same place on the home page and all of the index and content pages, which is in the container block

@albertov19  can you please review/approve this again? There were merge conflicts! Sorry, third time is the charm?


Fix arc controller connect

Missed this during the recent refactoring in the code - need to pass in the password for the initial connection.
Also updating extension description based on PM feedback

Coverage decreased (-0.002%) to 40.524% when pulling 5daee933a9637fca6b30bf4b0a34bc2490c898c6 on chgagnon/fixArcControllerConnect into bf278c39bda5bd5db644f624d96c2327a38b8335 on main.


Support names in references

For @elixir-lang/ecto-adapters,

[x] MySQL
[x] PostgreSQL
[ ] MSSQL
[ ] SQLite
[x] MongoDB

Here is the relevant commit: https://github.com/elixir-lang/ecto/commit/34bc420c09588172d430c5bb39867f956362b6eb. Just duplicate the changes and unit tests added to PostgreSQL/MySQL.
Here is the test: https://github.com/elixir-lang/ecto/commit/34bc420c09588172d430c5bb39867f956362b6eb#diff-56abcdb75cb6afa2275af793d936932fR463
This is the one of 2 changes before Ecto v1.0! I am waiting for feedback.

With Mongo there's no references at all, so there's nothing to do.

@michalmuskala so if I try to create a child model that links to a parent model that does not exist... it would just work?

Yes. The links in Mongo are at application level - there are no facilities for that in the database.

SQLite: https://github.com/jazzyb/sqlite_ecto/commit/3ea9113fb80b33011548f588729c5b01a5381daa

MSSQL: livehelpnow/tds_ecto@f60939cf655465d23b7ca2bf7caa26b9f1498e72


Flush alias

Hi,
This adds res.flushCompression() as an alias for res.flush()
This supports use such as:
// Not going to write again for a while.  If compression middleware is
// installed let's tell it to flush what we've got through to the client.
if (res.flushCompression) {
    res.flushCompression();
}

Currently the res object has a flush method regardless of whether compression middleware is installed.  The built-in flush method issues a noisy deprecation warning.  This patch provides an alias for the flush method to allow detection of the compression middleware's flush.
This addresses https://github.com/expressjs/compression/issues/72.
Thanks,
Bo

This would help me as well - any feedback on this @dougwilson?

This would be nice. Any chance of a quick review, @dougwilson?

In parallel, we can probably think of a good way to indicate if the response is getting compressed in a unique way that is obvious and doesn't conflict too much (darn Node.js taking  res.flush()  ;) ).


Default spaces for windows not specified in rules.

Hey ! Thanks for the awesome tiling manager. As I am relatively new to this software, I have a couple of questions.

Is there are way to set windows not specified by rules to got to a default space ?
Also, can I set rule such that "if more windows of the type open go to a new space" (assign multiple spaces in the rule) ?

So using the rules system you can only specify a single space for the default regardless of any other state.
You can utilize the signals (application_launched and window_created specifically) to write whatever logic you want, using the query system to retrieve information about the state, and then move the window to the desired space.

Thanks for the fast reply, I got the answer to my second question.
But for my first, let me explain it in more detail - Lets say I have written rules such that application A, B, C go to spaces 4, 5, 6. Now I want all applications, other than A, B, C to open in say, space 2 (i.e the default space for remaining apps).

But for my first, let me explain it in more detail - Lets say I have written rules such that application A, B, C go to spaces 4, 5, 6. Now I want all applications, other than A, B, C to open in say, space 2 (i.e the default space for remaining apps). I need help regarding making such a rule.

This is not possible in the latest released version, but you should be able to do it if you run from the master branch or wait for the next release, now that #173 has been implemented.

In version 2.4.0, something like the following should resolve your first question:
yabai -m rule --add app="^Finder$" space=3
yabai -m rule --add app="^Safari$" space=4
yabai -m rule --add app!="^(Finder|Safari)$" space=2


Update the readme to clarifies to the users

We need to add into the readme:

That the image built from the projects merged here is registry.redhat.io/redhat/community-operator-index:v<tag>
Clarifies that this repository is used to create the image and this image is used to distribute solutions on OCP/OKD by default
Clarifies that the solutions merged here ought to work in the OKD and OCP
Clarifies that OCP catalog is created by default using multi-sources and link the doc: https://docs.openshift.com/container-platform/4.6/operators/understanding/olm-rh-catalogs.html#olm-rh-catalogs_olm-rh-catalogs

for now, it is here https://redhat-openshift-ecosystem.github.io/community-operators-prod/operator-release-process/#operator-is-published

Hi @J0zi,
the above info is essential for users and IMO that would need to be in the readme.
also, see that the link provided does not cover all.


Move Enzyme.jl into extension

Enzyme.jl is quite a heavy dependency (and comes with its own compatibility constraints), but it is not essential for factor rotations, as it is only used by ComponentLoss criteria family.
This PR does the following:

introduces internal autodiff_gradient!() method that is agnostic of a particular autodiff backend
adds FactorRotations.set_autodiff_backend() global config method (defaults to Enzyme)
makes Enzyme.jl a weak dependency, moves autodiff_gradient!(::AutodiffBackend{:Enzyme}, ...) implementation to EnzymeExt

So the only user-visible change after this PR would be to execute using Enzyme if autodiff is required.
It also opens the possibility to have alternative backends for autodiff in the future.

Very nice change, I like it!
Just one thought: What do you think about using https://github.com/gdalle/DifferentiationInterface.jl directly? It's a smaller dependency compared to Enzyme and should give us a plug and play solution for all supported AutoDiff backends.

Just one thought: What do you think about using https://github.com/gdalle/DifferentiationInterface.jl directly?

I must admit I forgot there are packages for providing common autodiff interface, when I wrote this PR. Thank you for reminding!
I don't like reinventing the wheel, and it would have been nice to use this package.
Now, when I check the DifferentiationInterface.jl deps, it looks a little bit too much given that in most use cases FactorRotations.jl does not need autodiff:
it depends on ADTypes.jl (which depends on EnzymeCore.jl), SparseMatrixColorings.jl, and FillArrays.jl (which depends on PDMats.jl, which depends on SuiteSparse.jl).
The issue that motivated this PR was that in my project I use both Turing.jl and FactorRotations.jl, so I run into some obscure version conflicts, which also affected unrelated packages.
Given that autodiff is an actively developing ecosystem, I expect it would still be a potential issue if we plug in DifferentiationInterface.jl.
My suggestion is to keep this PR as is, and reconsider the support for DiffInterface.jl/ADTypes.jl if the need for more extensive autodiff support arises.
We just need to make sure that the current model (basically, set_autodiff_backend(backend) and autodiff_gradient!(::AutodiffBackend, ...) methods) would support it without breaking the compatibility -- and I think it would handle it.

Just one thought: What do you think about using https://github.com/gdalle/DifferentiationInterface.jl directly?

I must admit I forgot there are packages for providing common autodiff interface, when I wrote this PR. Thank you for reminding! I don't like reinventing the wheel, and it would have been nice to use this package. Now, when I check the DifferentiationInterface.jl deps, it looks a little bit too much given that in most use cases FactorRotations.jl does not need autodiff: it depends on ADTypes.jl (which depends on EnzymeCore.jl), SparseMatrixColorings.jl, and FillArrays.jl (which depends on PDMats.jl, which depends on SuiteSparse.jl).
The issue that motivated this PR was that in my project I use both Turing.jl and FactorRotations.jl, so I run into some obscure version conflicts, which also affected unrelated packages. Given that autodiff is an actively developing ecosystem, I expect it would still be a potential issue if we plug in DifferentiationInterface.jl.
My suggestion is to keep this PR as is, and reconsider the support for DiffInterface.jl/ADTypes.jl if the need for more extensive autodiff support arises. We just need to make sure that the current model (basically, set_autodiff_backend(backend) and autodiff_gradient!(::AutodiffBackend, ...) methods) would support it without breaking the compatibility -- and I think it would handle it.

That's a fair assessment. I've added some minor change requests, otherwise this is good to go.
Thanks for the effort!


Fix css workflow

Task/Issue URL: https://app.asana.com/0/488551667048375/1206418414402174/f
Description
Fixes the css workflow
Steps to test this PR

[ ] Workflow doesn't fail

develop

#4112   👈

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @marcosholgado and the rest of your teammates on  Graphite


Question: How would one deploy a Server build?

If I just run the .exe that was build, the server only listens to ports from the local machine (<IP_ADDRESS>:8084).
How can I run the server so that it listens to external requests (<IP_ADDRESS>:8084)?
For that matter: What if I want to deploy the HTML5 version? Is that easier?

Update:
I got the HTML5 version deployed.
For this I added another dotnet target in ClassicDSDHTML5/build.fsx
Target.create "Deploy" (fun _ ->
    runDotNet ("serve -d dist -p "+localPort+" -o -a <IP_ADDRESS>") projectFolder
)

Then one can deploy while listening to external calls via

dotnet fake build --target deploy

One can create a similar shortcut to the run.cmd. Simply copy the file, rename it and change the content to this command.


Can't sign transactions with RPC

I need to sign a transaction from python using RPC interface. It requires a signature of an account. So I do:
requests.post("http://localhost:8889/v1/wallet/sign_transaction", json=json.loads(data)).text
Where data looks like this(found this json params on github because RPC wiki seems to be outdated):
{     "signatures": [""],     "compression": "none",     "context_free_data": [],     "transaction": {     "region": 0,     "ref_block_num": "%s",     "ref_block_prefix": "%s",     "expiration": "%s",     "max_net_usage_words": 0,     "max_kcpu_usage": 0,     "delay_sec": 0,     "context_free_actions": [],     "actions": [{     "account": "user",     "name": "summ",     "authorization": [{     "actor": "tester",     "permission": "active"     }],     "data": "05000000000000000600000000000000"     }]     }     }
Block params comes from http://localhost:8888/v1/chain/get_info"
Output of this command is 403 HTTP error. I also tried to unlock my wallet with
s = '{"default":"PW5KFWYKqvt63d4iNvedfDEPVZL227D3RQ1zpVFzuUwhMAJmRAYyX"}' requests.post("http://localhost:8889/v1/wallet/unlock", json=json.loads(s))
Same 403 error. What do I wrong?

hi, the issue has been corrected ? could you help to tell how to fix that ?


Support usage archive to copy files from a container

@bradbeck @mattnworb

I think this functionality is already in master: https://github.com/spotify/docker-client/blame/master/src/main/java/com/spotify/docker/client/DefaultDockerClient.java#L775


How to update keybase on Ubuntu?

Have an version 2.13.0-20190104191034+69b3ee25b7 of keybase on Ubuntu but I don't find any option within the app to update it.
When I try to run /usr/bin/keybase update check I get Error finding updater path: Updater isn't supported on unix. Google didn't help much too... Please help.

Can you run
apt-get update
apt-get upgrade keybase

?

yes, it worked. Thanks

@pedro-roberto Great. Latest version should be 4.7.


failed tests after WCP chages

After merging pull request #15 "WCP check fix", some tests fail when I run python3 -m unittest. Here is the output:
FAIL: test_complex_WCP_no_violation_check1 (test.TestABAPlus)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jeff/work/2016-ABAPlus/test.py", line 320, in test_complex_WCP_no_violation_check1
    self.assertTrue(abap.check_WCP())
AssertionError: False is not true

======================================================================
FAIL: test_complex_WCP_no_violation_check2 (test.TestABAPlus)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jeff/work/2016-ABAPlus/test.py", line 365, in test_complex_WCP_no_violation_check2
    self.assertTrue(abap.check_WCP())
AssertionError: False is not true

======================================================================
FAIL: test_cycle_WCP_no_violation_check (test.TestABAPlus)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jeff/work/2016-ABAPlus/test.py", line 279, in test_cycle_WCP_no_violation_check
    self.assertTrue(abap.check_WCP())
AssertionError: False is not true

======================================================================
FAIL: test_simple_WCP_no_violation_check1 (test.TestABAPlus)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jeff/work/2016-ABAPlus/test.py", line 151, in test_simple_WCP_no_violation_check1
    self.assertTrue(abap.check_WCP())
AssertionError: False is not true

======================================================================
FAIL: test_simple_WCP_no_violation_check2 (test.TestABAPlus)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jeff/work/2016-ABAPlus/test.py", line 164, in test_simple_WCP_no_violation_check2
    self.assertTrue(abap.check_WCP())
AssertionError: False is not true

======================================================================
FAIL: test_simple_WCP_no_violation_check3 (test.TestABAPlus)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jeff/work/2016-ABAPlus/test.py", line 178, in test_simple_WCP_no_violation_check3
    self.assertTrue(abap.check_WCP())
AssertionError: False is not true

Since the tests are based on a stricter definition of WCP and Kristijonas made the WCP check more "lax",  they are no longer correct. . Kristijonas or I can add tests for the new WCP check when possible.

Do you think that you or @kcyras will update the tests soon? If not, then I can submit a pull request to disable the tests until you update them.

Re tests: I will do new ones, but really later, in a couple of weeks at the earliest, I imagine. So you could disable the old ones until I provide new ones.
 So pending now.

The WCP code is fixed and the tests now pass.


“I need to know which Python version is required for this project. I have tested with Python 3.11 and 3.10, but neither worked. Is there a specific version that I should use?”

“I need to know which Python version is required for this project. I have tested with Python 3.11 and 3.10, but neither worked. Is there a specific version that I should use?”

（venv）jibenqing@JideMac-mini-2独立%python <EMAIL_ADDRESS>#如果失败，您的Python可能无法配置为Tk^^^^^^^^^^^^^^^^^ModuleNotFoundError：没有名为“_tkinter”的模块（venv）jibenqing@JideMac-mini-2独立%
3.11.11

错误：忽略以下需要不同python版本的版本：1.21.2需要-Python >=3.7,<3.11; 1.21.3需要-Python >=3.7,<3.11; 1.21.4需要-Python >=3.7,<3.11; 1.21.5需要-Python >=3.7,<3.11; 1.21.6需要-Python >=3.7,<3.11; 1.26.0需要-Python <3.13,>=3.9; 1.26.1需要-Python <3.13,>=3.9错误：找不到满足火炬要求的版本（来自版本：无）错误：未找到火炬的匹配分布
3.13

ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11; 1.26.0 Requires-Python <3.13,>=3.9; 1.26.1 Requires-Python <3.13,>=3.9
ERROR: Could not find a version that satisfies the requirement torch (from versions: none)
ERROR: No matching distribution found for torch
3.13

(venv) mac@Mac-mini-2 standalone %    python standalone.py
Traceback (most recent call last):
File "/Users/jibenqing/gemini-multimodal-playground/standalone/standalone.py", line 3, in
from config_gui import ConfigGUI
File "/Users/jibenqing/gemini-multimodal-playground/standalone/config_gui.py", line 3, in
import tkinter as tk
File<EMAIL_ADDRESS>line 38, in
import _tkinter # If this fails your Python may not be configured for Tk
^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named '_tkinter'

if you are using a mac please install through terminal
brew install<EMAIL_ADDRESS>Change 3.11 with version you want

I had the same problem. Mac M1. I am using Python 3.12 after a few attempts with other python versions and it works.

Just clarified in the readme. Thanks both @PBenavides @cheesecake100201


python310Packages.tritonclient: init at 2.35.0

Description of changes
open ai triton client
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.tritonclient
python310Packages.tritonclient.dist
python311Packages.tritonclient
python311Packages.tritonclient.dist


Figure out tutorial-writing workflow

We'll understand this better once we get on the stack club cluster (see the computing model in #7), but the Plan (#6) should include notes on how to contribute to the Stack Club tutorial notebooks. This might take some thought: we want to enable people to develop quickly (in the club sessions, for example), but we also want to make it easy to capture what has been made after the fact. Maybe encouraging work in personal forks of this repo is safest, to reduce conflicts in the middle of a session? Let's come back to this later, in time to give good advice to anyone wanting to work on Stack Club notebooks during the Commissioning Team Bootcamp (at the end of May).

The Hello Word notebook describes how to contribute to the Stack Club notebooks: need to check that it and our other docs cover forking/branching, issuing projects etc.


Fix stack for windows

Related https://github.com/input-output-hk/ouroboros-network/issues/1082
Continuation of https://github.com/input-output-hk/ouroboros-network/pull/1774, which makes use of https://github.com/input-output-hk/cardano-prelude/pull/100

@mrBliss with this, ouroboros-consensus still depends on 3893f21db1665e7bab9e8c6504c547fc7c28f98c of prelude, but uses the resolver of fe76ec64f6b45259cc407a6d840dad79ee6063b6. Do you think this is an inconsistency we should fix? I just though bumping also the dependency could mean more cascading changes.

@kderme Yes, it's an inconsistency that should be fixed.

stack and cabal work on windows

bors r+

bors r+

bors r+

FYI, the test failure on Hydra is transient and the sign of an overloaded CI machine (the test involves time).


Question about dependencies

Hi,
I maintain package for Archlinux and I was wondering if cffi is still required once pyspotify is build.
Or is it only required to make the package ?

Currently cffi is required for both building and running the package.
cffi upstream has done some work towards splitting in two packages; cffi and cffi-runtime or similar. Once that is in place, a much smaller dependency is all that is needed at runtime.

Ok, thanks.


Clements pixart

comfort: 4.5
completeness: 1-3
still working through info on this, will update soon.

Sounds good. Closing this now just to mark it as submitted, but let me know if you have any questions about this assignment -- I'll keep an eye on Github notifications / Slack.


Back off from the homeserver when there's a sync error, or a rate limit error

as much fun as it is to see logs scream by while it desperately tries to sync

Hey everyone :wave:
I'm having a look to see if I can add optional "request retry and backoff" to the client because this is something that we think would be useful for Mjolnir. Now I feel like my way of going about this could be embarrassingly bad so I want to get some consultation on the right approach that could also benefit everyone else. So I have listed the ideas I have come up with here, I apologise if i have missed something obvious or have butchered some terminology.

Use something that explicitly manages request scheduling that takes the request in a callback (that it may call multiple times) with some parameters about how backoff and retry should work and another callback to be called each time it retries (e.g. so a warning can be sent to the mjolnir management room about a slow request). This is nice because it doesn't complicate any existing code, it's generally isolated but the downside is there's a lot of refactoring to do for people who want to use it depending on how much code wants to opt in.

Got seems to have some options for handling this built in (and maybe other libraries?) and is managed by adding hooks, but this seems like a very disruptive option and I am in no position to estimate how much of an undertaking that is. Particularly if people have built error handling code and other things based on the current http requests library. Seems like there is already a fork for this https://github.com/Sorunome/matrix-js-bot-sdk .

Add some sort of event listener/hooks (like option 2?) to MatrixClient.ts that allows a callback to be registered and called when a request fails for any reason. This could be problematic though because while it maintains API compatibility, if a request gets "retried" you in end up causing requests to fail later rather than sooner.

Related #92 and #90


PhpStorm doesn't see connection

I Restart terminal
I Check Xdebug in PhpStorm Setting
I disable firewall

But PhpStorm still doesn't see connection
It`s xdebug log:
[22] Log opened at 2022-03-23 10:47:01 [22] I: Connecting to configured address/port: <IP_ADDRESS>:9004. [22] I: Connected to client. :-) [22] -> <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" fileuri="file:///var/www/html/index.php" language="PHP" xdebug:language_version="7.2.34" protocol_version="1.0" appid="22" idekey="16813"><engine version="2.7.2"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[https://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2019 by Derick Rethans]]></copyright></init> [22] [22] -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" status="stopping" reason="ok"></response> [22] [22] Log closed at 2022-03-23 10:47:01
Help please!

I tried to change xdebug port, but catch error:
[21] W: Creating socket for '<IP_ADDRESS>:9009', poll success, but error: Operation now in progress (29).


Start travis for this repo

Earlier the better
/cc @sils @jayvdb

I have a PR adding .travis.yml here https://github.com/coala/corobo/pull/43

Done


Extend Security Scheme Object to support DPoP token specification

In response to evolving security requirements and practices in web API design, and after thorough analysis of the current OpenAPI Specification version 3.0.3 and relevant RFCs, specifically RFC 9449, I am proposing an enhancement to the OpenAPI Specification in the upcoming v3.0.4-dev branch. This proposal is aimed at incorporating a more nuanced approach to token-based authentication, particularly addressing the implementation of Demonstration of Proof-of-Possession (DPoP) tokens.
Proposed Modifications in the PR:

Extend the scheme Field's Application: Suggest that the application of the scheme field within the Security Scheme Object includes both http and oauth2 types. This extension is essential for describing the authentication methods with greater accuracy and aligns with the authentication scheme differentiation as described in RFC 9449.

Refinement on the Use of bearer and dpop Schemes:

When type is set to oauth2 and scheme to bearer, it indicates the traditional bearer token usage without employing DPoP mechanisms, aligning with standard OAuth 2.0 practices.
When type is oauth2 and scheme is dpop, it explicitly indicates the utilization of DPoP, necessitating the format Authorization: DPoP token. Furthermore, in accordance with RFC 9449, this setup mandates the inclusion of a DPoP header in the request, providing a DPoP proof.

Rationale Behind the Proposal:
The motivation for these modifications is grounded in the detailed examination of the DPoP authentication scheme as outlined in Section 7.1 of RFC 9449. DPoP introduces a more secure method for handling tokens by binding them to a particular HTTP request and a cryptographic key pair owned by the client. This mechanism significantly mitigates the risk associated with token theft and replay attacks, as the token is no longer a standalone bearer token but requires accompanying proof of possession.
By integrating dpop as a specified scheme within the OAuth 2.0 security scheme in OpenAPI, we acknowledge the necessity for APIs to adopt more secure authentication methods in light of increasing security challenges. This proposal ensures that the OpenAPI Specification remains relevant and capable of describing modern, secure API architectures.
Furthermore, the explicit distinction between bearer and dpop within the specification allows for clear documentation and implementation of APIs that require enhanced security measures. It encourages API designers to consider and implement DPoP where applicable, fostering a more secure ecosystem of web APIs.
Examples of Usage:
Bearer Token Example for OAuth 2.0
Here's how you can specify the use of standard OAuth 2.0 bearer tokens in an OpenAPI document:
components:
  securitySchemes:
    oauth2Bearer:
      type: oauth2
      scheme: bearer
      flows:
        authorizationCode:
          authorizationUrl: https://example.com/oauth/authorize
          tokenUrl: https://example.com/oauth/token
          scopes:
            read: Read access
            write: Write access
      description: Standard OAuth2 bearer token usage.

DPoP Token Example for OAuth 2.0
For specifying OAuth 2.0 with DPoP tokens, indicating enhanced security by binding the tokens to a specific HTTP request:
components:
  securitySchemes:
    oauth2DPoP:
      type: oauth2
      scheme: dpop
      flows:
        authorizationCode:
          authorizationUrl: https://example.com/oauth/authorize
          tokenUrl: https://example.com/oauth/token
          scopes:
            read: Read access
            write: Write access
      description: OAuth 2.0 with DPoP tokens for enhanced security, binding tokens to specific requests.

Conclusion:
This PR aims to enhance the OpenAPI Specification by providing clear, structured means to specify the use of DPoP tokens alongside traditional bearer tokens. By doing so, it contributes to the broader goal of improving security practices within the API design community, ensuring that OpenAPI remains at the forefront of technological and security advancements.
Closes #3612.

In submitting this PR, my aim was to maintain consistency with the original discussion, hence the title and description chosen. However, it's important to highlight that the proposed modification opens up possibilities not only for describing DPoP but also for incorporating other authentication schemes, both existing and potentially new ones in the future. This flexibility ensures that the OpenAPI Specification can evolve alongside advancements in security protocols, maintaining its relevance and utility for API designers and developers.

Thanks for adding this, we're agreed as a group that this (and many other OAuth things) would be excellent additions, but as @LasneF already mentioned, it won't be added to the 3.0.x branch. I'm closing this pull request since it can't merge as-is, but let's continue discussion on the issue to move forward with this feature.


Add possibility to pass HTTPoison options on snapshot create

We also observed timeouts here. Repeat of #62

Merging in, some unrelated tests are failing randomly on build, seems to be a race condition on es index creation which should be fixed in another pr.


Features, which are not shown in examples so far

Pesto can compute confidence intervals and, as far as I know but please correct me if I'm wrong, also profile for multimodal objective functions. Since this is a useful feature, we should implement this in one example.
Are there any other useful features, which are not covered by examples or which I might not know so far?

To my knowledge multimodal objective functions (where profile calculation starting from multiple modes is required) are not supported for profile calculation.
The transfection example is a good starting point there as The separation between the modes can be easily tuned.

The profile calculation routine allows for the specification of the starting point (using the index), an automatic integration of profiles from multiple runs is currently however not supported.

Okay, I will write a little routine which does that...
Should it be part of the publication, or rather of a later version?

A later version is in my opinion sufficient. in the case of multi-modal distributions, standard confidence intervals are anyhow problematic.

I added a little "example for bimodality" part in the transfection example. At least, this feature is now shown, a later version with merged profiles and confidence intervals will come at some point.


[Feature Request] Show how much time overspent

Hi,
Thanks for such a nice and useful plugin.
I have a real pleasure to use it.
Sometime it happens that I don't stop working even when Pomodoro says to break.
Sometimes my breaks take more that the time I set.
Every time this happens I loose track of time.
It would be nice to start some timer when Pomodoro fires and show how much time I overspent for work break.
Maybe it can be done somehow now?
If not I'd be glad to contribute to the project.
Is anybody else interested in this function?
Will it be possible to include it into an official release on Google Market?
Many thanks
Andrii

Please see https://github.com/schmich/marinara/issues/75
That should handle your case right?


Keyboard controls

For testing TerraLegion on my computer I don't like using the joystick. When I press "A" or "D" the character moves to the left or to the right. When I press space I jump only sometimes when I'm not completely standing on a block. Do you understand what I mean?

Yeah I believe there is a small bug for the jumping which doesn't work when the space bar is pressed although it works with the joystick. It's very strange, but it needs to be looked at.

When I comment out this (https://github.com/jmrapp1/TerraLegion/blob/1030fe0be7483a22488b2a64444c0a2f0df64c04/core/src/com/jmrapp/terralegion/engine/world/PhysicsWorld.java#L175) and the line after jumping with the keyboard is working but then the player falls down very fast in some cases.

Yeah that needs to remain. We may need to add some special case to check if the player is trying to jump and if they are, don't do "some case" in the physics logic.

 After that you normally fall down.


fix: DG/UG TOC not being generated by Kramdown

Closes #84
Interesting bug. GH Pages uses Kramdown (a markdown interpreter) to automatically help people generate Table of Contents, but prettier (our md code formatter) adds whitespaces before the {:toc} token, which breaks the TOC.
Fixed by making prettier ignore the whole section of TOC markup.

Codecov Report

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

@@            Coverage Diff            @@
##             master      #85   +/-   ##
=========================================
  Coverage     72.44%   72.44%
  Complexity      423      423
=========================================
  Files            74       74
  Lines          1339     1339
  Branches        136      136
=========================================
  Hits            970      970
  Misses          324      324
  Partials         45       45

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 65c3417...e6aaddb. Read the comment docs.

Skipping code review as this is urgent. Merging.


fix(server): fix model version in generated POM

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1602
#1601  👈
#1600
#1599
#1598
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Vampire and the rest of your teammates on  Graphite

Merge activity

Aug 31, 1:09 PM EDT: @krzema12 started a stack merge that includes this pull request via Graphite.


Documentation button go to files.community/docs

Description
Documentation button go to files.community/docs instead https://files-community.github.io/docs/#/

Steps To Reproduce
No response
Expected behavior
The button will open the docs site.
Files Version
Version: <IP_ADDRESS>
Windows Version
OS Version: 10.0.19043.1237
Relevant Assets
No response

@steam3d the new website will be going live on October 4th.


Clean dependencies

Removes a few unused dependencies, some pretty heavy. Also gets rid of the unused selenium scrapping module.

I'm surprised opencv isn't used, I guess I used it before but eventually switched everything to Pillow. 😅
Anyway you're right, removing the unused code will make things cleaner. We just need to resolve the conflicts with your previous PR and this should be good.

All fixed :)


Some README Links are 404 Not Found

The following links in the README are 404 Not Found:
C# Examples

Awaiting in Tests
Watching Signals in Tests

Resolved by a19a10fe29e506bbf69c3665424b60386b3069db and f1b3f88f91e151cd7145263477fafc92ff1c498d


Unknown option: termguicolors

I get the following error when I install this plugin and add colorscheme nova to my .vimrc.  I'm using the Janus vim distribution on Ubuntu 16.04

I'm using GNOME Terminal version 3.18.3 as well.

@Xaeroxe Thanks for using Nova. As mentioned in the documentation, "You'll need True Color support (latest Vim, Neovim, or GUI Vim)";
If you run vim --version it should be at least 8.0:

So since you are on Ubuntu, I believe you will need to do this:
sudo apt-get update
sudo apt-get install vim

Hope this helps.

Although I don't use Janus or know much about it, it may need to be updated to upgrade Vim. Either way, your Vim version needs to be latest for True Color support.

I thought of that, so I checked to see if my Vim had true color support using this
awk 'BEGIN{
    s="/\\/\\/\\/\\/\\"; s=s s s s s s s s;
    for (colnum = 0; colnum<77; colnum++) {
        r = 255-(colnum*255/76);
        g = (colnum*510/76);
        b = (colnum*255/76);
        if (g>255) g = 510-g;
        printf "\033[48;2;%d;%d;%dm", r,g,b;
        printf "\033[38;2;%d;%d;%dm", 255-r,255-g,255-b;
        printf "%s\033[0m", substr(s,colnum+1,1);
    }
    printf "\n";
}'

And it did display correctly.  I am also able to use this vim color theme: http://vimcolors.com/626/spring-night/dark with the same setup.

However it did just occur to me that just because the terminal has true color support doesn't mean that Vim does.  I'll check that next time I'm at this box.

@Xaeroxe That is correct, both your terminal and Vim itself need true color support - so along with your terminal which sounds like it is ok, you'll need to upgrade Vim to latest.

Ah, yes Ubuntu default vim doesn't have TrueColor support.  I got a version of Vim on my computer that does though and we're all good now.  Thanks for helping me, sorry for noob issue.

@Xaeroxe No worries, glad you got it figured out :)


[Bug]: printing should always be done in "light" mode

Currently, if a user tries to print package documentation, the rendered docs use the current theme. Hence, if in dark mode, the print document will also be in dark mode. This is likely not desired (e.g., imagine printing 10 pages with black backgrounds).
Presumably, the fix here is to always switch the application to "light" mode, generate the print docs, and then revert to theme back to its original value before printing.

Hmm, that shouldn't be the case, see https://github.com/stdlib-js/www/blob/c3d227a0eb8a0f2db66a429c61cb40e9d324a7e6/src/components/readme/print_button.jsx#L85
For me, printing via the button does indeed switch to light mode and then back?

This should also already work when directly invoking the print dialog window (e.g., via Ctrl + P on Chrome).

I did this on mobile, so maybe it only happens there?

Cannot reproduce myself: Has worked on all my browsers on laptop, Android phone, and on an iPad on Safari / Chrome.
Judging from above screenshot, formatting is also off with no left margin.

Not able to reproduce on MacOS Safari.

Is this an older iPhone? Per MDN, onbeforeprint has been supported in Safari since v13 (see: https://developer.mozilla.org/en-US/docs/Web/API/Window/beforeprint_event).

It is an older iPhone. Not sure what Safari version it's running though.

Ah...seems as though the Safari version should match the iOS version. I am on iOS 12.5.5, so don't have beforeprint support, it seems.

Given that users are unlikely to want to print on mobile devices, especially older iOS devices, I'll close this out.

Yeah, Apple doesn't provide updates for their browsers on older devices. Starting with version 13, things work:

Thanks for checking!

I also noticed various other rendering issues when viewing the stdlib docs on my phone, and I'm wondering if some of them are just due to it being an older Safari version.


fix absolute path reference

with some boy scout code clean up 👦

@kajal-alpha. Now that everything is green you can merge the change 👍

PS: Code review is good way to learn. Everyone should do code review

@kajal-alpha Don't forget to delete the branch after merging changes.


BUG: [turbo] npm install command also installs install package

Describe the bug:

Running npm install -S packageName also installs<EMAIL_ADDRESS>as a dependency. Similarly, npm i -S packageName also installs the i package.
Link to the blitz that caused the error:
https://stackblitz.com/edit/turbo-install-bug?file=package.json
Steps to reproduce:

Open Node.js starter.
In Terminal, enter npm install -S vue.
See install listed under dependencies in package.json (in addition to the intended vue package).
See the install package installed in node_modules/install.

Expected behavior:

Only the package specified on the command line (i.e., after the install or i command) is installed.
Screenshots:

Desktop (please complete the following information):

OS: macOS BigSur
Browser Chrome
Version 91

Smartphone (please complete the following information):

Device: n/a
OS: n/a
Browser n/a
Version n/a

Additional context:
none

Hi @tony19 ! We are aware of this bug and it will be fixed soon. Thanks for reporting 🙏 !

This is fixed now.


Enable HTTPS for the docs

@pfitzseb can you enable HTTPS for these docs or get me access to the Juno Lab org on GitHub?

Done.

Thank you!


[CELEBORN-1678] Add Celeborn CLI User guide in README

What changes were proposed in this pull request?
adding user guide to README for cli
Why are the changes needed?
better user experience when using CLI.
Does this PR introduce any user-facing change?
no
How was this patch tested?
N/A

cc @FMX @SteNicholas

Please update mkdocs.yml to add navigation for CLI user guide.

@SteNicholas  updated


Add option for AM/PM

I like the idea, thought I am 24h format person, but some people like 12h+AM/PM.
Here is a few thoughts I have

I noticed you added a few issues for new features, are they part of
v1.0.0, I hope not, since you already tagged. Either way, I think we
can utilize Roadmap to help track what we really want for next
version.
Some of the issues are directly related the date/time format string.
I think you need to outline the exactly all the date/time
functionality/feature and code at once (not literally), so there
wouldn't be foobar here to patch a date, dummy there to workaround
something foobar does. It's more like a guideline and we can have the
whole picture in mind while coding.
Also about the AM/PM, I use en_us locale, and I am sure some locale
won't use "AM" and "PM", so the font definitely can't render those.
This will need to take into consideration to make sure the date/time
string can be rendered properly, which I believe it's regardless the
locale, users always get "AM"/"PM" style.

thought I am 24h format person, but some people like 12h+AM/PM.

Yeah, I don't have a use for it myself, but it will be nice for the sake of completeness.

are they part of v1.0.0

Nah, I'm thinking most of the planned stuff will be at least v1.1.0.

I think you need to outline the exactly all the date/time functionality/feature

I was going to keep the date format separate from the time format. Since it'll just be plaintext, it can be formatted however the user wants. Whereas the time format is very specific.

This will need to take into consideration to make sure the date/time
string can be rendered properly, which I believe it's regardless the
locale

I'm thinking it'll just be an optional bool to turn the feature on and it'll just be AM/PM in plaintext. Nothing fancy that can break.

I was going to keep the date format separate from the time format. Since it'll just be plaintext, it can be formatted however the user wants. Whereas the time format is very specific.

I see, I was wondering if date would be another big text.

I'm thinking it'll just be an optional bool to turn the feature on and it'll just be AM/PM in plaintext. Nothing fancy that can break.

Good, I was thinking too much.

I was wondering if date would be another big text.

Maybe if someone requests it. For now it'll just be the bare minimum.


Update uuid.js

fixes #134

Any updates on if this is going to be merged?

What does @broofa think?

I just did a check, this reports a jsdom environment as a browser which leads to printing the false warning in a test runner like Jest.
I've always used detect-node for these tests which always worked pretty well.
What do you think @broofa ?

@amannn I've also realized this a while ago, totally forgot about this MR. Agreed though, detect-node or similar would be much better.
BTW @broofa, there is not a lot of maintaining activity on this project recently and that's pity because it's quite popular. Have you considered adding new maintainers to this project or maybe transfering the maintenance to another namespace (e.g. a company with OSS activities actively using this)?
(cc @coolaj86)

It would be great to get this merged. This makes testing extremely noisy


[Release-1.22] - secrets-encrypt reencrypt gets stuck in reencrypt_active

Backport fix for secrets-encrypt reencrypt gets stuck in reencrypt_active

#5489

Validated using v1.22.9-rc3+k3s1

Followed the same steps mentioned in the PR:

$ sudo k3s secrets-encrypt reencrypt
reencryption started

$ sudo k3s secrets-encrypt status
Encryption Status: Enabled
Current Rotation Stage: reencrypt_active
Server Encryption Hashes: All hashes match

Active  Key Type  Name
------  --------  ----
 *      AES-CBC   aescbckey-2022-04-25T20:49:00Z
        AES-CBC   aescbckey

$ k annotate node/ip-172-31-10-213 foo=bar
node/ip-172-31-10-213 annotated

$ sudo k3s secrets-encrypt status
Encryption Status: Enabled
Current Rotation Stage: reencrypt_active
Server Encryption Hashes: All hashes match

Active  Key Type  Name
------  --------  ----
 *      AES-CBC   aescbckey-2022-04-25T20:49:00Z
        AES-CBC   aescbckey

$ sudo k3s secrets-encrypt status
Encryption Status: Enabled
Current Rotation Stage: reencrypt_finished
Server Encryption Hashes: All hashes match

Active  Key Type  Name
------  --------  ----
 *      AES-CBC   aescbckey-2022-04-25T20:49:00Z