Issue with field "subcategory_credit_amount_preceding"

Hi there,
I was trying your csimport.py and ofximport.py scripts. Both come up with the following error:
ERROR:pynYNAB:Encountered field subcategory_credit_amount_preceding in a dictionary to create an entity of type <class 'pynYNAB.budget.Transaction'>
It doesn't matter which csv files, schemas, or ofx files I am using...
Am I doing something wrong?
Thanks for your work and best regards,
Daniel

Hi Daniel,
You did nothing wrong ^^ This is a typical error message to inform us here that the nYnab API changed a bit. It's an unfortunate consequence of using an undocumented internal API as a public API. I can have no guarantee that what I reverse engineered won't change at any time. I'll look into it, there is probably a lot of changes that happened since last time I committed.
Sorry for the inconvenience !

Okay, cool.
Thank you!


Mention 20.04 Install in Documentation

It looks like the install instructions currently only mention 18.04 and 16.04.

Thanks for the prompt reply Brian! I gave it a shot and my main blocking issue seems to be Alvar. From what I can tell, this is what happens:

Ubuntu 20.04 comes with OpenCV 4.x, which is used by ROS noetic packages as well.
Astrobee needs OpenCV 3.x. It seems the main reason for this is Alvar, whose source code depends on legacy (e.g. IplImage), which stopped being supported on opencv versions 4 onwards.
When the Astrobee's configuration files try to build an OpenCV .deb (version 3.x), it fails in my machine because it says that it needs to install the dependency libvtk6-dev, however 20.04 has installed libvtk7-dev. I cannot uninstall libvtk7-dev since a lot of ros packages I use depend on that one.

My new question :) now is : Is Alvar the only reason for using OpenCV version 3? If so, then I could give a shot at patching alvar (the version astrobee uses), so it can be used with OpenCV 4 (and I think the Astrobee's localization package also would need some few updating changes, but it does not seem anything major).  Thanks!

The 'Ubuntu 20.04 install' installs OpenCV 3.3.1 in /usr/local, such that you can have both versions simultaneously. The instructions for all versions are the same though given that the install_debians step detects the ubuntu version automatically.

Hi Marina!
Thanks. Mm, wonder what is the issue with my system then. When I run ./build_install_debians.sh, this is what happens:
ana@strelka:~/ros/astrobee/scripts/setup/debians$ ./build_install_debians.sh
Reading package lists... Done
Building dependency tree
Reading state information... Done
devscripts is already the newest version (2.20.2ubuntu2).
equivs is already the newest version (2.2.0).
libproj-dev is already the newest version (6.3.1-1).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libopencv3.3.1-build-deps : Depends: libvtk6-dev but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

My system has libvtk7-dev installed. If I try to install libvtk6-dev, that uninstalls libvtk7-dev, which I need since that is a dependency for packages like ros-noetic-pcl-ros.

Humm, the install instructions assume a clean OS to begin with. Maybe you can try to replace 'libvtk6-dev' with 'libvtk6-dev | libvtl7-dev' in the control file to see what happens (scripts/setup/debians/opencv/control).

I see, thanks! For reference, this is a  brand new machine, which I set up 5 days ago with 20.04 and Noetic. Before attempting to install Astrobee, I had only installed ros-noetic-desktop-full in this machine (plus some extra ROS packages, but nothing out of ordinary - as in, I didn't add any super new package or ppa that might have messed up my machine).
As for your suggestion (using libvtk7-dev) it helped to make the build progress :). However, it stalled at some point, apparently for a bunch of reasons. The one that caught my eye was this one related to OpenCV:
/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckIncludeFile.c:1:10: fatal error: sys/videoio.h: No such file or directory
    1 | #include <sys/videoio.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.

From what I can see, it seems as if this is not built/installed because libv4l-dev is not being found properly by OpenCV 3.x. I see I have that package installed on my machine. I am guessing the OpenCV CMake is not finding it because it is searching for linux/videodev.h, but from what I read online, it seems that now that file is installed in /usr/include/libv4l1-videodev.h .
I got hundreds of error/warning lines, so it is a bit hard to parse what is exactly failing (besides what I mentioned above). I copied a few last dozen lines of the terminal output of ./build_install_debians.sh for reference. I probably will come back to this at some point soon and will let you know if I figure something out. Thanks for the help!
    1 | #include <sys/videoio.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [CMakeFiles/cmTC_195a6.dir/build.make:66: CMakeFiles/cmTC_195a6.dir/CheckIncludeFile.c.o] Error 1
make[3]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_195a6/fast] Error 2
make[2]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

Determining if the function sgemm_ exists failed with the following output:
Change Dir: /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_96a9d/fast && make[2]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_96a9d.dir/build.make CMakeFiles/cmTC_96a9d.dir/build
make[3]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_96a9d.dir/CheckFunctionExists.c.o
/usr/bin/cc   -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Winit-self -Wno-narrowing -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -DCHECK_FUNCTION_EXISTS=sgemm_ -O3 -DNDEBUG   -o CMakeFiles/cmTC_96a9d.dir/CheckFunctionExists.c.o   -c /usr/share/cmake-3.16/Modules/CheckFunctionExists.c
cc1: warning: ‘-Werror=’ argument ‘-Werror=non-virtual-dtor’ is not valid for C
Linking C executable cmTC_96a9d
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_96a9d.dir/link.txt --verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Winit-self -Wno-narrowing -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -DCHECK_FUNCTION_EXISTS=sgemm_ -O3 -DNDEBUG  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now   -rdynamic CMakeFiles/cmTC_96a9d.dir/CheckFunctionExists.c.o  -o cmTC_96a9d
/usr/bin/ld: CMakeFiles/cmTC_96a9d.dir/CheckFunctionExists.c.o: in function `main':
/usr/share/cmake-3.16/Modules/CheckFunctionExists.c:17: undefined reference to `sgemm_'
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_96a9d.dir/build.make:87: cmTC_96a9d] Error 1
make[3]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_96a9d/fast] Error 2
make[2]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

Determining if the function cheev_ exists failed with the following output:
Change Dir: /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_f122c/fast && make[2]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_f122c.dir/build.make CMakeFiles/cmTC_f122c.dir/build
make[3]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_f122c.dir/CheckFunctionExists.c.o
/usr/bin/cc   -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Winit-self -Wno-narrowing -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -DCHECK_FUNCTION_EXISTS=cheev_ -O3 -DNDEBUG   -o CMakeFiles/cmTC_f122c.dir/CheckFunctionExists.c.o   -c /usr/share/cmake-3.16/Modules/CheckFunctionExists.c
cc1: warning: ‘-Werror=’ argument ‘-Werror=non-virtual-dtor’ is not valid for C
Linking C executable cmTC_f122c
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_f122c.dir/link.txt --verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Winit-self -Wno-narrowing -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -DCHECK_FUNCTION_EXISTS=cheev_ -O3 -DNDEBUG  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now   -rdynamic CMakeFiles/cmTC_f122c.dir/CheckFunctionExists.c.o  -o cmTC_f122c  /usr/lib/x86_64-linux-gnu/libblas.so
/usr/bin/ld: CMakeFiles/cmTC_f122c.dir/CheckFunctionExists.c.o: in function `main':
/usr/share/cmake-3.16/Modules/CheckFunctionExists.c:17: undefined reference to `cheev_'
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_f122c.dir/build.make:88: cmTC_f122c] Error 1
make[3]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_f122c/fast] Error 2
make[2]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

Build output check failed:
    Regex: 'command line option .* is valid for .* but not for C\+\+'
    Output line: 'cc1plus: warning: command line option ‘-Wno-missing-prototypes’ is valid for C/ObjC but not for C++'
Compilation failed:
    source file: '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx'
    check option: ' -Wno-missing-prototypes'
===== BUILD LOG =====
Change Dir: /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_73498/fast && make[2]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_73498.dir/build.make CMakeFiles/cmTC_73498.dir/build
make[3]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_73498.dir/src.cxx.o
/usr/bin/c++    -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -Wno-deprecated  -O3 -DNDEBUG    -Wno-missing-prototypes -o CMakeFiles/cmTC_73498.dir/src.cxx.o -c /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx
cc1plus: warning: command line option ‘-Wno-missing-prototypes’ is valid for C/ObjC but not for C++
/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:1: warning: ignoring #pragma   [-Wunknown-pragmas]
    1 | #pragma
      |
Linking CXX executable cmTC_73498
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_73498.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -Wno-deprecated  -O3 -DNDEBUG  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now   -rdynamic CMakeFiles/cmTC_73498.dir/src.cxx.o  -o cmTC_73498
make[3]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

===== END =====

Build output check failed:
    Regex: 'unrecognized .*option'
    Output line: 'cc1plus: warning: unrecognized command line option ‘-Wno-tautological-undefined-compare’'
Compilation failed:
    source file: '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx'
    check option: ' -Wno-tautological-undefined-compare'
===== BUILD LOG =====
Change Dir: /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_3676e/fast && make[2]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_3676e.dir/build.make CMakeFiles/cmTC_3676e.dir/build
make[3]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_3676e.dir/src.cxx.o
/usr/bin/c++    -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security   -Winit-self -Wpointer-arith   -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -Wno-deprecated -Wno-missing-declarations -Wno-shadow -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-sign-compare -Wno-sign-promo -Wno-undef  -O3 -DNDEBUG    -Wno-tautological-undefined-compare -o CMakeFiles/cmTC_3676e.dir/src.cxx.o -c /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx
/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:1: warning: ignoring #pragma   [-Wunknown-pragmas]
    1 | #pragma
      |
cc1plus: warning: unrecognized command line option ‘-Wno-tautological-undefined-compare’
Linking CXX executable cmTC_3676e
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_3676e.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security   -Winit-self -Wpointer-arith   -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -Wno-deprecated -Wno-missing-declarations -Wno-shadow -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-sign-compare -Wno-sign-promo -Wno-undef  -O3 -DNDEBUG  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now   -rdynamic CMakeFiles/cmTC_3676e.dir/src.cxx.o  -o cmTC_3676e
make[3]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

===== END =====

Build output check failed:
    Regex: 'unrecognized .*option'
    Output line: 'cc1plus: warning: unrecognized command line option ‘-Wno-shorten-64-to-32’'
Compilation failed:
    source file: '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx'
    check option: ' -Wno-shorten-64-to-32'
===== BUILD LOG =====
Change Dir: /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_6b1d0/fast && make[2]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_6b1d0.dir/build.make CMakeFiles/cmTC_6b1d0.dir/build
make[3]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_6b1d0.dir/src.cxx.o
/usr/bin/c++    -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security   -Winit-self -Wpointer-arith   -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -Wno-deprecated -Wno-missing-declarations -Wno-shadow -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-sign-compare -Wno-sign-promo -Wno-undef -Wno-ignored-qualifiers -Wno-extra -Wno-unused-function -Wno-unused-const-variable  -O3 -DNDEBUG    -Wno-shorten-64-to-32 -o CMakeFiles/cmTC_6b1d0.dir/src.cxx.o -c /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx
/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:1: warning: ignoring #pragma   [-Wunknown-pragmas]
    1 | #pragma
      |
cc1plus: warning: unrecognized command line option ‘-Wno-shorten-64-to-32’
Linking CXX executable cmTC_6b1d0
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_6b1d0.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security   -Winit-self -Wpointer-arith   -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -Wno-deprecated -Wno-missing-declarations -Wno-shadow -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-sign-compare -Wno-sign-promo -Wno-undef -Wno-ignored-qualifiers -Wno-extra -Wno-unused-function -Wno-unused-const-variable  -O3 -DNDEBUG  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now   -rdynamic CMakeFiles/cmTC_6b1d0.dir/src.cxx.o  -o cmTC_6b1d0
make[3]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

===== END =====

Build output check failed:
    Regex: 'unrecognized .*option'
    Output line: 'cc1plus: warning: unrecognized command line option ‘-Wno-inconsistent-missing-override’'
Compilation failed:
    source file: '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx'
    check option: ' -Wno-inconsistent-missing-override'
===== BUILD LOG =====
Change Dir: /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_be187/fast && make[2]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_be187.dir/build.make CMakeFiles/cmTC_be187.dir/build
make[3]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_be187.dir/src.cxx.o
/usr/bin/c++    -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden   -O3 -DNDEBUG    -Wno-inconsistent-missing-override -o CMakeFiles/cmTC_be187.dir/src.cxx.o -c /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx
/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:1: warning: ignoring #pragma   [-Wunknown-pragmas]
    1 | #pragma
      |
cc1plus: warning: unrecognized command line option ‘-Wno-inconsistent-missing-override’
Linking CXX executable cmTC_be187
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_be187.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden   -O3 -DNDEBUG  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now    -rdynamic CMakeFiles/cmTC_be187.dir/src.cxx.o  -o cmTC_be187
make[3]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

===== END =====

Build output check failed:
    Regex: 'unrecognized .*option'
    Output line: 'cc1plus: warning: unrecognized command line option ‘-Wno-unused-private-field’'
Compilation failed:
    source file: '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx'
    check option: ' -Wno-unused-private-field'
===== BUILD LOG =====
Change Dir: /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_3d0f3/fast && make[2]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_3d0f3.dir/build.make CMakeFiles/cmTC_3d0f3.dir/build
make[3]: Entering directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_3d0f3.dir/src.cxx.o
/usr/bin/c++    -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -Wno-unused-function -Wno-overloaded-virtual  -O3 -DNDEBUG    -Wno-unused-private-field -o CMakeFiles/cmTC_3d0f3.dir/src.cxx.o -c /home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx
/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:1: warning: ignoring #pragma   [-Wunknown-pragmas]
    1 | #pragma
      |
cc1plus: warning: unrecognized command line option ‘-Wno-unused-private-field’
Linking CXX executable cmTC_3d0f3
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_3d0f3.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wno-narrowing -Wno-delete-non-virtual-dtor -Wno-comment -Wno-implicit-fallthrough -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -Wno-unused-function -Wno-overloaded-virtual  -O3 -DNDEBUG  -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now   -rdynamic CMakeFiles/cmTC_3d0f3.dir/src.cxx.o  -o cmTC_3d0f3
make[3]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

===== END =====

dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_AUTOGEN_VERBOSE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_INSTALL_PREFIX=/usr/local -DINSTALL_C_EXAMPLES=ON -DINSTALL_PYTHON_EXAMPLES=ON -DOPENCV_GENERATE_PKGCONFIG=ON -DOPENCV_EXTRA_MODULES_PATH=/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv/../contrib/modules -DBUILD_EXAMPLES=ON -DOPENCV_ENABLED_NONFREE=YES -DENABLE_PRECOMPILED_HEADERS=OFF "-DCMAKE_SHARED_LINKER_FLAGS_RELEASE=-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now" -DBUILD_SHARED_LIBS=ON -DBUILD_DOCS=ON .. returned exit code 1
make[1]: *** [debian/rules:34: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/home/ana/ros/astrobee/scripts/setup/debians/libopencv/opencv'
make: *** [debian/rules:20: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui failed

Thanks for the info, I'll try to reproduce your setup then :)

Our docker image does install ROS prior to building/installing the debians (https://github.com/nasa/astrobee/blob/develop/scripts/docker/astrobee_base.Dockerfile).
I'm going to close this issue because I just merged in a PR which mentions 20.04 in the documentation, maybe we could open a separate one to sort this out?

That is awesome! Thank you very much :)


Move attribution periodic to run at night

Issue #, if available:
Description of changes:
The attribution periodic runs in the middle of the day, sometimes leading to churn and confusion if we're in the middle of updating base images or changing things. Moving this to the middle of the night (1am PT) should help reduce these events.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


refactor!(fusion-endpoint): align module name, groupId, version

Fixes #450

I don't see any need for the backend prefix in the package name, none these java packages are not supposed for running in the frontend, I think just endpoint is enough. Another option would be hilla-backend to align with the ts folder, but I'd rather endpoint
The same with the hilla-tests module, I would just rename to integration-tests or just tests because hillaprefix is not used anywhere else.
My proposal:

endpoint
tests

Regarding tests folder structure I would remove the hilla and test parts and leave as:

spring
csfr
csfr-context

I’m not sure about dropping the test part. In certain contexts, I’m presented with only the module name, and it is confusing to have IT module names mixed with the rest. Here is the module list in my IDEA, where endpoint and former test-endpoints could easily be mixed up, for example:

Well, that was a proposal. I don't use Idea, but if you think keeping the test- prefix facilitates DX, then go ahead,
The only thing is that all modules are aligned


Display localised names for system folders

Implements and closes #1226

@duke7553 could we put this in the LoadExtendedItemProperties method? It won't hurt performance, only issue is that it will briefly show the untranslated name (maybe acceptable)

@gave92 Actually we can do this from the Win32 component. That's what a tried first.

@Jaiganeshkumaran that would be pretty slow as well I think

@gave92 What should I do then? SHGetLocalizedName is not available for UWP apps.

@Jaiganeshkumaran I think the current method (StorageFolder) is good, and performance issues can be solved by moving this to the LoadExtendedItemProperties() method

@gave92 But then it will not be shown in the folder list.

We can have it as a optional feature

@gave92 Since the name is shown on the files list rather than something like the properties, I'm not going to put this in extended properties. Instead we can have it as an option feature.

@Jaiganeshkumaran of you put it on LoadExtendedItemProperties it will be shown on the file list

@gave92 But what's the difference?

Here's an issue with localization. In English (United States) it's 'localized' but in other regions it is 'localised'. I've added a resource file for en-gb however it will use the en-us version even if it's set to some other en other than en-us or en-uk because Windows provides many en regions. Should I add resource files for each one of en region using MAT?

@Jaiganeshkumaran nope, it's called from GenericFileBrowser and GridViewBrowser to load some file info (e.g. thumbnail, OneDrive sync status, etc)

@gave92 But now the names appear after the page has fully loaded which makes it look bad.

@Jaiganeshkumaran yeah I don't particularly mind that (better that no translated name and better that slow file list loading) but that's my opinion :)
@duke7553 do you have any thoughts on this?

#1424

@Jaiganeshkumaran yeah this is the cause of that issue as well.

We can have it as a optional feature

@Jaiganeshkumaran We should not add an optional feature in this case since it will slow down the app for users who turn it on who might not be aware of the side affects.

@yaichenbaum Then can I close this pull request?

@yaichenbaum Then can I close this pull request?

We would love to include this if you can find a way to implement it without any side effects.


Explosions made with the explosion builder are "CUSTOM" damage type

Explosions made with the explosion builder are set to the "CUSTOM" damage type, rather than being set to the more reasonable "EXPLOSIVE" damage type.

Is it not possible to specify what type during the creation of the explosion?

It is not
---- On Fri, 13 May 2016 19:30:42 -0700<EMAIL_ADDRESS>wrote ----
Is it not possible to specify what type during the creation of the explosion?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Re-test with stable-5 and report back if still an issue and we will re-open.


Script for CVE-2021-42306 appears to be Windows only

The script (https://github.com/microsoft/aad-app-credential-tools/blob/main/azure-automation/CVE-2021-42306-AutomationAssessAndMitigate.ps1) used to determine if Automation accounts are vulnerable to CVE-2021-42306 and mitigate the issue appears to be Windows only.
Running it with PowerShell 7.2 and PowerShell Core gives the error below.
./CVE-2021-42306-AutomationAssessAndMitigate.ps1: The script 'CVE-2021-42306-AutomationAssessAndMitigate.ps1' cannot be run because it contained a "#requires" statement for PowerShell editions 'Desktop'. The edition of PowerShell that is required by the script does not match the currently running PowerShell Core edition.
Please can a cross-platform version of the script be provided.

It would also be nice to clarify why "run as administrator" is required.

Ack the request, we didn't want to impose the PS7 as the requirement to mitigate as most of the customers are on PS5. We will provide the PS7 version on Monday to support across OS flavors.

It appears the only thing that is not possible x-plat is the two lines here:
https://github.com/microsoft/aad-app-credential-tools/blob/main/azure-automation/CVE-2021-42306-AutomationAssessAndMitigate.ps1#L469-L470

Export-PfxCertificate is part of the PKI module which is only available on Windows
[System.Web.Security.Membership]::GeneratePassword() is also Windows only

Password creation is simple enough to replace with another function e.g
https://gist.github.com/indented-automation/2093bd088d59b362ec2a5b81a14ba84e#file-new-password-ps1
Would generating a certificate in a key vault be a sensible option but then there's a requirement to have a pre-existing key vault or create one to utilise.


[ResponseCompression] Compare MimeTypes as case insensitive

Starting on https://github.com/aspnet/BasicMiddleware/issues/108
@JunTaoLuo

@JunTaoLuo Yes, the other parts of #108 are more invasive so I wanted to get this functional issue fixed first.


Don't try to follow relative links in __CFTimeZoneCreateSystem

Discovered this when trying to compile Swift for CentOS 7. I'm not sure if this is the appropriate fix, but it fixes the problem on CentOS.

@swift-ci test

@swift-ci reset

Do you have an example of a symlink on Centos7 for /etc/localtime which is relative?

@spevans ../usr/share/zoneinfo/UTC

Approved.


Failed to enable layernorm kernel

Firstly very appreciate your work! When I try to use the framework to reproduce your work, I noticed the layernorm kernel is not working on my side. Here is the log:
torchrun --standalone --nproc_per_node=1 scripts/dit/train_dit.py \
     --model DiT-XL/2 \
     --batch_size 2 \
     --enable_layernorm_kernel \
     --enable_flashattn \
     --mixed_precision bf16 \
     --num_classes 10
/home/cjinag/code/playground/ColossalAI/colossalai/pipeline/schedule/_utils.py:19: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
  _register_pytree_node(OrderedDict, _odict_flatten, _odict_unflatten)
/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/utils/_pytree.py:254: UserWarning: <class 'collections.OrderedDict'> is already registered as pytree node. Overwriting the previous registration.
  warnings.warn(
/home/cjinag/code/playground/ColossalAI/colossalai/initialize.py:48: UserWarning: `config` is deprecated and will be removed soon.
  warnings.warn("`config` is deprecated and will be removed soon.")
[03/20/24 15:13:27] INFO     colossalai - colossalai - INFO: /home/cjinag/code/playground/ColossalAI/colossalai/initialize.py:67
                             launch
                    INFO     colossalai - colossalai - INFO: Distributed environment is initialized, world size: 1
[2024-03-20 15:13:27] Experiment directory created at ./outputs/018-DiT-XL-2
[2024-03-20 15:13:39] Model params: 642.77 M
No ROCm runtime is found, using ROCM_HOME='/usr/local'
[extension] Compiling the JIT cpu_adam_x86 kernel during runtime now
[extension] Time taken to compile cpu_adam_x86 op: 0.12372970581054688 seconds
[extension] Compiling the JIT fused_optim_cuda kernel during runtime now
[extension] Time taken to compile fused_optim_cuda op: 0.14196491241455078 seconds
/home/cjinag/code/playground/ColossalAI/colossalai/nn/optimizer/hybrid_adam.py:90: UserWarning: The torch.cuda.*DtypeTensor constructors are no longer recommended. It's best to use methods such as torch.tensor(data, dtype=*, device='cuda') to create tensors. (Triggered internally at ../torch/csrc/tensor/python_tensor.cpp:83.)
  self._dummy_overflow_buf = torch.cuda.IntTensor([0])
Files already downloaded and verified
[2024-03-20 15:13:51] Dataset contains 50,000 images (./datasets)
[2024-03-20 15:13:51] Boost model for distributed training
[2024-03-20 15:13:51] Training for 1400 epochs...
[2024-03-20 15:13:51] Beginning epoch 0...
Epoch 0:   0%|                                                                                | 0/25000 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "/home/cjinag/code/project/multimodal/OpenDiT/scripts/dit/train_dit.py", line 324, in <module>
    main(args)
  File "/home/cjinag/code/project/multimodal/OpenDiT/scripts/dit/train_dit.py", line 245, in main
    loss_dict = diffusion.training_losses(model, x, t, model_kwargs)
  File "/home/cjinag/code/project/multimodal/OpenDiT/opendit/diffusion/respace.py", line 90, in training_losses
    return super().training_losses(self._wrap_model(model), *args, **kwargs)
  File "/home/cjinag/code/project/multimodal/OpenDiT/opendit/diffusion/gaussian_diffusion.py", line 708, in training_losses
    model_output = model(x_t, t, **model_kwargs)
  File "/home/cjinag/code/project/multimodal/OpenDiT/opendit/diffusion/respace.py", line 120, in __call__
    return self.model(x, new_ts, **kwargs)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1520, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/cjinag/code/playground/ColossalAI/colossalai/booster/plugin/low_level_zero_plugin.py", line 65, in forward
    return super().forward(*args, **kwargs)
  File "/home/cjinag/code/playground/ColossalAI/colossalai/interface/model.py", line 25, in forward
    return self.module(*args, **kwargs)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1520, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/cjinag/code/project/multimodal/OpenDiT/opendit/models/dit/dit.py", line 213, in forward
    x = block(x, c)  # (N, T, D)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1520, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/cjinag/code/project/multimodal/OpenDiT/opendit/models/dit/dit.py", line 58, in forward
    modulate(self.norm1, x, shift_msa, scale_msa, self.enable_modulate_kernel)
  File "/home/cjinag/code/project/multimodal/OpenDiT/opendit/modules/layers.py", line 33, in modulate
    x = norm_func(x.to(torch.float32)).to(dtype)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1520, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/apex/normalization/fused_layer_norm.py", line 323, in forward
    return fused_layer_norm(input, self.normalized_shape, self.eps, self.memory_efficient)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/apex/normalization/fused_layer_norm.py", line 203, in fused_layer_norm
    return FusedLayerNormFunction.apply(*args)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/autograd/function.py", line 553, in apply
    return super().apply(*args, **kwargs)  # type: ignore[misc]
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/apex/normalization/fused_layer_norm.py", line 149, in forward
    output, mean, invvar = fused_layer_norm_cuda.forward(input_, ctx.normalized_shape, ctx.eps)
RuntimeError: memory format option is only supported by strided tensors
[2024-03-20 15:13:58,980] torch.distributed.elastic.multiprocessing.api: [ERROR] failed (exitcode: 1) local_rank: 0 (pid: 155022) of binary: /home/cjinag/anaconda3/envs/opendit/bin/python
Traceback (most recent call last):
  File "/home/cjinag/anaconda3/envs/opendit/bin/torchrun", line 8, in <module>
    sys.exit(main())
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 347, in wrapper
    return f(*args, **kwargs)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/distributed/run.py", line 812, in main
    run(args)
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/distributed/run.py", line 803, in run
    elastic_launch(
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 135, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/home/cjinag/anaconda3/envs/opendit/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 268, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
scripts/dit/train_dit.py FAILED
------------------------------------------------------------
Failures:
  <NO_OTHER_FAILURES>
------------------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2024-03-20_15:13:58
  host      : 191host040.mobilenet.cse.ust.hk
  rank      : 0 (local_rank: 0)
  exitcode  : 1 (pid: 155022)
  error_file: <N/A>
  traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
============================================================

Please advise possible solutions. Thanks!

its a verison mismatch problem for apex. maybe your apex version is too old or too new. you can first disable enable_layernorm_kernel arg to run the code

its a verison mismatch problem for apex. maybe your apex version is too old or too new. you can first disable enable_layernorm_kernel arg to run the code

When I disabled the layernorm kernel, the code runs fine for me. However, I have conducted a reinstallation of OpenDiT according to the version recommended in your README file and this error log still exists. Is there any other possible reasons?

sorry no clues. i suppose it should be about your enviroment and apex.

sorry no clues. i suppose it should be about your enviroment and apex.

Then may I have a reference for your environment settings?(e.g. torch version, CUDA, etc.), since your requirements.txt does not restricting this... I suspect the new version of PyTorch may have something changed to have this error.

we use cuda 11.8 and torch 2.1.2, good luck

we use cuda 11.8 and torch 2.1.2, good luck

What is the cudnn version on your platform?

cudnn 8.9.7

cudnn 8.9.7

I noticed through your installation guidelines in your README file, it will automatically update the torch and other dependencies to the newest version and cause version mismatch. So I think you probably need to fix the version in your environment settings.

Thanks for providing your settings. I commenced the training successfully.


Reversed logic when enumerating Linux device capabilities

I've been trying to diagnose why I cannot get Flashcap to correctly enumerate a built-in camera on a Raspberry PI (model 3 B+).
During my investigation I think I've discovered a flaw in the logic for enumerating the device capabilities - specifically related to the enumeration of the FramesPerSecond.
As commented in the code, while the V4L2 api reports the value as a time interval, Flashcap inverts this value to a FramesPerSecond value.
The minimum and maximum intervals are converted to their FPS value and used to filter a list of standardised frame rates.
However, the problem is that while the interval values have been inverted, the minimum and maximum values are still treated as a minimum and maximum when filtering the standardised rates. But the minimum and maximum meanings should also be swapped.
For example, if the interval values reported by the V4L2 api is:
min: 10/1
max: 30/1

this would be converted to FPS values of
min: 1/10
max: 1/30

1/10 is a larger value than 1/30 so the minimum and maximum meanings should be reversed:
min: 1/30
max: 1/10

Because the minimum value is larger than the maximum value, the fps >= min && fps <= max filtering constraint can never be true and no FramesPerSecond values are returned.

This will affect devices that report framerates as either Stepwise and Continuous values. Devices that report Discrete values will not be affected since the filtering is not performed.

Thank you send PR, I'll review it in a couple of days!

Thank you, merged!


Moved AssetAdmin variables into framework for reuse

Also delete a ui-theme font family which was causing linting issues trying to override the style.
This needs merging before AssetAdmin linting fix.

Looks good to me. Will merge when green.


[Card] Extra margins show when using ripple

When matRipple is added to a <mat-card>, the card expands on click.
Reproduction: https://stackblitz.com/edit/angular-1mherw?file=app/card-overview-example.html
This is due to the styling rule that says every element in the card except for the last should have bottom margin. When the ripple is added, the last element is no longer last and so it gains the margin bottom.
https://github.com/angular/material2/blob/master/src/lib/card/card.scss#L190

Same for mat-table : https://github.com/angular/material2/issues/11165

@andrewseguin I tried looking into the issue but couldn't find anything that allows us to skip .mat-ripple-element items when querying for the :last-child.
Technically the ripple elements are valid children that can be also the last element. If we try something like: nth-last-child(1):not(.mat-ripple-element) the counter won't reset, and we'd never reach mat-card-content.
I also tried to select the element before the first .mat-ripple-element if there are ripples, but apparently CSS is not providing a selector to query for elements before another one.

Just wanted to summarize my findings real quick. Maybe someone does have some other ideas. I will keep looking into it.

Problem not resolve

Please take a look at this thread: https://github.com/angular/material2/issues/14981 - @devversion explanation is clear, To fix the problem, add this code to your global CSS file:
div.mat-ripple-element {
  position: absolute !important;
}

Work around doesn't work
https://stackblitz.com/edit/angular-material2-card-ripple?file=styles.scss

This fixed my issue. https://github.com/angular/components/issues/12210#issuecomment-486225151

Stumbled on this issue as well. After some inspection, it seems adding and empty (or not empty) <mat-card-footer> as the last child solves the issue.
https://stackblitz.com/edit/angular-material2-card-ripple-adgv8u

The bug appears not only on the <mat-card>, but also on any other container.
Its essence is that during animation matRipple adds side margin to the last element of the container, equal to the gap between the elements inside the container. This means that it ignores the CSS rule: div:last-child {margin-left: 0} (or in case column: div:last-child {margin-bottom: 0}).
A possible workaround is to add the margin to the last element on its own, if design allows it. Or wrap container to other and set matRipple on wrapper.
In this particular topic starter case, the workaround may look like:
<mat-card matRipple>

    <mat-card-content>  Click this card to see it expand  </mat-card-content>

</mat-card>

More details here: https://stackblitz.com/edit/angular-material2-matripple-i5ugtwissie?file=app/app.component.html

I wonder if a ripple solution that uses CSS paint worklet could avoid this issue.

This will be fixed with the new MDC implementation of card. That card implementation does not have any spacing by default (unless wrapped inside of mat-card-content).

The ripple implementation we currently provide, relies on actual HTML elements being added to the DOM. This could indeed be an issue for any container that relies on order (e.g. through CSS last-child).
We are working on MDC components that might also involve a new implementation of ripples. At time of writing, MDC uses pseudo elements for those. That might fix this issue, but could cause other issues due to conflicting pseudo elements. I don't believe there is a good ripple solution that works in all cases though.

I´m some time ago, do this:
<mat-card matRipple class="technologies__card">

         name

</mat-card>

Adding a div inside a mat-card element this problem was fixed but after an update to v9 of angular framework, doesn´t work.
A posible solution is add to global styles the following code:
.mat-ripple-element {
   display: none;
}

But this, delete a ripple effect, so as well im tryed replace display: none; by padding/margin: 0 !important; and doesn´t work...
Somebody have another workaround solution?

Confirming that this is still an issue with the MDC-based card:
https://stackblitz.com/edit/angular-mdc-issue-rqjw6o?file=src%2Fapp%2Fmdc%2Fmdc-example-module.ts
The issue is still the :last-child style that adds margin and the ripple becoming the last-child while active.

I faced the same issue. I managed to avoid it by using an empty mat-card-footer . In this case :last-child won't be applied

Temporary workaround is to add a   as the last child of the matRipple container

margin-bottom: 0 on the last element in a mat-card works fine too.


[chip-tool] the CHIP tool is parsing Thread operational dataset as string but not HEX string.

Problem
The CHIP tool is parsing Thread operational dataset as string but not HEX string. This result in Thread device provisioning failures with the command pairing ble-thread ...
Proposed Solution
parse Thread Operational dataset as HEX string.
It was fixed by #6627 but reverted by #6689

I think this is now resolved?


add helm chart of nfs storage class.

https://github.com/cloudcheflabs/dataroaster/commit/2bd20b65870909626c0b775c314ec4e9388ca018


Runs in docker containers

Type of Contribution

[x] Bugfix (non-breaking change which fixes an issue)
[x] New component
[ ] Refactoring (no functional changes)
[ ] Documentation-only

What does this implement/fix? Explain your changes.
mailbagit now runs in docker and separate dockerfiles (Dockerfile and Dockerfile.production) are available to build dev and prod docker images.
Also refactors setup.py so that pip install mailbag or pip install -e . will always work, and you can also pip install mailbag[pst] or pip install -e .[pst] to install libpff-python and/or pip install mailbag[gui] or pip install -e .[gui] to install the gooey GUI.
Link to issue?
#130 #161

[x] Issue closed
[ ] Remain open

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[x] Make sure you are requesting to the develop branch. Don't PR to main!
[ ] This contribution has sufficient documentation
[ ] Tests for the changes have been added
[x] All tests pass

How has this been tested?
Operating System: win10
Python Version: n/a
Licensing

[x] I agree that the Mailbag Project and the University at Albany, SUNY can release this code under the MIT license.

Can test docker image with
docker pull ualbanyarchives/mailbag:dev
docker run -it ualbanyarchives/mailbag:dev


Cannot handle null objects

Null objects in the old document causes problems even if no changes are made.
Example:
var turboDiff = require("turbo-diff")
var oldDocument = {
    prop3: null
};

var newDocument = {
    prop3: null
};

var diff = turboDiff(oldDocument, newDocument);

Thanks for your feedback, this has been fixed in v1.0.6.


firebase auth methods giving error on not nullable types

Welcome to FirebaseUI and thanks for submitting an issue!
Please take a look at open issues, as well as resolved issues, to see if your issue is either already being addressed, or has been solved by someone else.
If not, please feel free to fill in the following info so we can help faster!
Step 1: Are you in the right place?

For issues or feature requests related to the code in this repository file a GitHub issue.
For general technical questions, post a question on StackOverflow tagged appropriately.
For general Firebase discussion, use the firebase-talk google group
For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel

Step 2: Describe your environment

Android device: _____
Android OS version: _____
Google Play Services version: _____
Firebase/Play Services SDK version: _____
FirebaseUI version: ____

Step 3: Describe the problem:
Steps to reproduce:

Observed Results:

What happened?  This could be a description, logcat output, etc.

Expected Results:

What did you expect to happen?

Relevant Code:
// TODO(you): code here to reproduce the problem

@krishnagandrath we can't help if you don't fill out the issue template!  Please try to provide the required information and try again,


feat: make apiKey optional for elements types

Description

Make apiKey optional for elements types

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.63.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add tag property to tag union

"tag" makes more sense since it's called a tagged union. That it's not a reserved keyword also means we can destructure it to a variable.


fix: issue with css image through webpack

Due to how we are handling our weird multi-compiler publicPath
things were getting messed up. So use a separate config for CSS
in production build to specify publicPath.
Fixes #117

Codecov Report

Merging #121 into master will decrease coverage by 0.77%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master     #121      +/-   ##
==========================================
- Coverage   95.92%   95.15%   -0.78%
==========================================
  Files          10       10
  Lines         221      227       +6
  Branches       52       53       +1
==========================================
+ Hits          212      216       +4
- Misses          4        6       +2
  Partials        5        5

Impacted Files
Coverage Δ

packages/scripts/src/config/WebpackConfigHelper.ts
93.2% <75%> (-1.65%)
:arrow_down:

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 57a88f1...06fee11. Read the comment docs.


Rename arrow/benches/string_kernels.rs to arrow/benches/substring_kernels.rs

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
All benchmarks in string_kernel.rs are related to substring. So we should rename the file substring_kernel.rs

marked as development process as changed code that was never released


Feat/app

Force pushing due to unsigned commits closed https://github.com/canonical/github-runner-image-builder/pull/2 and github currently cannot reopen closed PRs due to foce push, hence a new PR.
Applicable spec: N/A
Overview
Creates an installable python application that will be used by github-runner-image-builder-operator charm to manage building of images.
The application creates a chroot environment from Ubuntu cloud-images and pre-installs and pre-configures executables.
The uploading of images have been omitted deliberately due to the testing overhead that arises from including Openstack.
Rationale
To provide a workload for github-runner-image-builder-operator charm.
Module Changes
The modules are as follows:

cli - provides entrypoint and parsing args
bulider - handles the building of image within the chroot env
chroot - provides a context-managed chroot environment
config - configuration data types
utils - utility functions, e.g. retry

TODO (in a follow up PR):

reorder the functions to be in step down order to cater for recent changes in contributing guide.
Missing repository configurations.

Checklist

[x] The contributing guide was applied
[x] The changes are compliant with ISD054 - Managing Charm Complexity
[x] The documentation is generated using src-docs
[x] The documentation for charmhub is updated.
[x] The PR is tagged with appropriate label (urgent, trivial, complex)

The test is failing due to: https://github.com/canonical/pylxd/pull/580 should be fixed when it lands on pypi.


Supporting disguised mid-circuit measurements

A mid-circuit measurement may appear to be terminal since no other operation happens on the wire, but in reality, it might be used for some upcoming controlled workflow elsewhere in the circuit. This adds a checking condition to catch such scenarios and treat those terminal measurements as mid-circuit measurements.

Thanks @obliviateandsurrender for this quick fix!
One thing I'm confused about, do we need to conceptually treat terminal and mid-circuit measurements differently at all?

@trbromley iirc the main inspiration to treat them differently was the fact that when users provide their own measurements then we would replace the terminal measurements in the circuit while still retaining the mid-circuit ones.


The new gpt-3.5-turbo

Are we going to support the new "gpt-3.5-turbo" soon?
thanks

Done: https://twitter.com/enunomaduro/status/1631221339028684802?s=20.

Thank you so much!


Add asseets/svg/ back to dist in published package

Misskey and Firefish rely on dist/svg being in the NPM package, as it was there in previous versions.

Essentially, we have a /twemoji/*svg route that'll serve the corresponding svg from the dist in node_modules.

This is not supported. Discord's fork will also soon stop supporting this. Please tell me your use case so I can help you find an alternative that is supported.

The use case is that we want to serve Twemoji assets that are hosted on our server(s).

Sharing a related use-case we have for gitify-app/gitify.
We are looking to introduce twemoji parsing to increase our cross-platform compatibility, but ideally would want to source the SVGs locally since we have some offline modes that aren't compatible with using an online CDN.


Make an alias so .stats works with .status also

.status

.stats

Idea to make an alias for it? :-)

Closing along with #73 because it has been added to the suggested features list


chore!: rename collector exporters

Rename collector exporters to otlp exporters.

I updated it to change all exported types/variables from collector to otlp naming. Please take one more look for sanity before i merge.


Fix compiler warnings when LFS_READONLY defined

Without this patch, when defining LFS_READONLY:
littlefs/lfs.c:14:20: warning: unused function 'lfs_cache_drop' [-Wunused-function]
static inline void lfs_cache_drop(lfs_t *lfs, lfs_cache_t *rcache) {
                   ^
littlefs/lfs.c:271:20: warning: unused function 'lfs_pair_sync' [-Wunused-function]
static inline bool lfs_pair_sync(
                   ^
littlefs/lfs.c:283:20: warning: unused function 'lfs_pair_tole32' [-Wunused-function]
static inline void lfs_pair_tole32(lfs_block_t pair[2]) {
                   ^
littlefs/lfs.c:368:20: warning: unused function 'lfs_gstate_hasorphans' [-Wunused-function]
static inline bool lfs_gstate_hasorphans(const lfs_gstate_t *a) {
                   ^
littlefs/lfs.c:372:23: warning: unused function 'lfs_gstate_getorphans' [-Wunused-function]
static inline uint8_t lfs_gstate_getorphans(const lfs_gstate_t *a) {
                      ^
littlefs/lfs.c:376:20: warning: unused function 'lfs_gstate_hasmove' [-Wunused-function]
static inline bool lfs_gstate_hasmove(const lfs_gstate_t *a) {
                   ^
littlefs/lfs.c:391:20: warning: unused function 'lfs_gstate_tole32' [-Wunused-function]
static inline void lfs_gstate_tole32(lfs_gstate_t *a) {
                   ^
littlefs/lfs.c:419:20: warning: unused function 'lfs_superblock_tole32' [-Wunused-function]
static inline void lfs_superblock_tole32(lfs_superblock_t *superblock) {
                   ^
8 warnings generated.

Thanks! Would be good to have this in. Will bring this in next patch release (may be a bit longer).
Out of curiosity, which version of which compiler are you using? I believe both gcc and clang treat static inline functions specially since they are common in header files (otherwise CI should have caught this).

which version of which compiler are you using?

I am using clang+llvm-10.0.0-x86_64-linux-gnu-ubuntu-18.04, so Clang 10.

treat static inline functions specially since they are common in header files (otherwise CI should have caught this).

I'd imagine that clang warns because the definitions are in a .c file, which means that they are definitely dead code. If these were in the header file, they'd still be dead code, but Clang probably wouldn't warn.

Ah interesting, it looks like gcc doesn't have the same check. But nonetheless this is a good change to have.

Thanks for the PR!


Hidden email in profile doesn't hide email from /api/users

Package version (if known): 9.1.2
Describe the bug
Even though a user marked their email as hidden in their profile (and saved preferences), their email is still visible in the autocomplete for another user trying to invite them.
Steps to Reproduce

As one user mark your profile as public and your email as hidden
As another user try to invite the first user to a community
See their email in the autocomplete

Expected behavior
The email shouldn't be show on the auto-complete.
Screenshots (if applicable)

Hello!
Thanks for reporting it.
I remember testing it in the past, and the email was not visible (in fact the field was totally removed from the resource). Are you sure the user was re-indexed after saving the preferences?

Ah, how would I know if the user was re-indexed? Is this a task done on a longer schedule, so I wouldn't see the changes immediately (or within a couple minutes) but rather the day after?

You would see it after few seconds, also there is a log in your console showing the indexing celery task has been completed

Thanks, after an upgrade to 9.1.2, the email visibility seems to be updated appropriately in a way: the error is now that the UI displays "null" for the email when it's hidden:

Closing this in favour of real reason for the problem: https://github.com/inveniosoftware/invenio-communities/issues/789


Astro rewrite

Currently, "Learn More" and "Get Catalyst" redirect to the Github Readme and Releases pages respectively - they'll work until proper pages are implemented


SWD Analyzer plugin improvement

This pull request incorporates changes from #4 and additionally enables the decoding of SWD data and control sequences captured by waveforms, per ARM ADIv5, ADIv5.2, and ADIv6.
A brief list of improvements:

List of available SWD control sequence elements that can be detected:

Line reset ( at least 50 SWCLKTCK cycles with SWDIOTMS HIGH )
JTAG-to-SWD (Legacy)
SWD-to-JTAG (Legacy)
IDLE cycles
DS Pre-Selection Alert (at least 8 SWCLKTCK cycles with SWDIOTMS HIGH)
DS Selection Alert
DS Pre Activation Code
JTAG-Test-Logic-Reset (at least 5 SWCLKTCK cycles with SWDIOTMS HIGH)
DS-to-JTAG (activation code)
JTAG-to-DS
DS-to-SWD (activation code)
SWD-to-DS

Introduced current protocol (SWD/JTAG/DS) state machine
The number of turnaround cycles is set per DLCR register read/write operation
Sticky overrun behaviour is set per CTRL/STAT.ORUNDETECT read/write operation
DP and AP version is detected based on the value that is read from DPIDR
DP and AP register values are decoded according to their version
Configurable initial values of:

Debug Protocol
Last sequence
DP Version
Number of turnaround cycles
Sticky overrun behaviour

I gave this branch a bit of a test whilst debugging my SWD implementation.
A few things I note;

I needed to tell CMake to use C++17
I needed to move definitions of SEQUENCE_JTAG_SERIAL, SEQUENCE_SW_DP and SEQUENCE_JTAG_DP into a cpp file, rather than the h file they are currently in.
TARGETSEL isn't handled properly - it doesn't get ACK'd by the chip by design, whereas the analyzer looks for them:

I had to modify SWDAnalyzer.cpp, GetAnalyzerName so there isn't a conflict with the inbuilt plugin (this is probably expected?)

@HexF,
Thank you for reporting the errors you found.
They should be fixed in the latest commit.
However, the analyzer name should be modified in GetAnalyzerName to avoid conflict with the in-box SWDAnalyzer plugin.
Could you test this on your setup?
Best regards

The latest changes involve parallel recognition of sequence elements, allowing the last transaction to be decoded in sequences, as shown in the screenshot.


Allow deleting gist

For issue #307

Thanks! Just a couple comments.

@joshaber fixed! Please have a look :)

Looks good, thanks!


feat: auto relay

This PR is part of the #699 initiative to add support for AutoRelay.
It includes the initial points described in the issue for connecting with peers with a relay protocol, more precisely, it includes this points:

When a node connects to a peer that announces support for the relay protocol, /libp2p/circuit/relay/0.1.0, it may ask that node if it support HOP.
If the peer supports HOP, libp2p should add it to its list of known relays.
When a known relay is added, libp2p should check to see if it needs a/another relay (to meet some min threshold). If below that threshold, libp2p should bind to that relay and add it to its announced addresses.

It is important to mention the following implementation details:

After a connection is established, the identify protocol will kick in. As a result of the identify protocols, peers will exchange the protocols they support. The auto-relay relies on the change:protocols event from the PeerStore, in order to understand what peers to ask for HOP support
When a peer supports HOP, this information is stored in the metadataBook
When a peer disconnects (or does not support relay protocol anymore - this should not be possible at the moment), remaining open connections with peers supporting HOP will be used to replace the disconnected one

This should be refactored to leverage the new connectionManager as a follow up PR

Already relayed connections, will not be used for auto relay
Regarding 3,  maxListeners was added (happy to reconsider the name) instead the minThreshold. It limits the number of relay addresses to listen on. Each time a node is connected, it will ask if it supports HOP (if peer has the relay protocol). This should be polished with the connectionManagement improvements to have a general approach for the autoDial

@jacobheun your thoughts regarding the current direction of this work are welcome :)
I think this first iteration is almost ready

@jacobheun this is ready for review now. Should we create a base branch for 0.30.x or for the work included in https://github.com/libp2p/js-libp2p/issues/703 ?

Should we create a base branch for 0.30.x or for the work included in #703?

@vasco-santos Yeah let's do that, there are a few things we want to land in conjunction with this so it would be good to gather those outside of master.

I changed it to 0.30.x branch as we might not include all of #703 in the next release

This is ready for review again @vasco-santos , the expected follow up PRs are described in the main post of the PR:

When libp2p updates its addresses, it should update the network - Identify push on add/remove listen + self peer record update on addr change
Query the network if it needs more relays
New connectionManager integration for disconnect improvement

Note: codecov jobs are not working properly atm. I rebuild everything, but it is failing the gcov command. So, some of the annotations in the PR diff are not valid as there are actually tests for that flows, but were added in the last commit

CI is failing, but otherwise I think we can merge once that's fixed and continue work in subsequent PRs

Done @jacobheun ! CI test are good, don't know what happened before, but just removed cache and re-run and everything got good again. However, the codecov CI got broken in this PR and it never ran again 🤷♂


This app is not working?

Samsung S7: I tap the button "Receive file" -> "Create group"
Nexus 6P: I tap the button "Sent file" -> "Search" -> Nothing happen ?

I need to edit some code, it is working


Examine file ctime when checking if files have changed.

What is the purpose of this change? What does it change?
This makes restic compare file ctimes (in addition to all of the existing checks) when it is deciding if a file has been modified.

Was the change discussed in an issue or in the forum before?
Yes, closes #2179.

Checklist

[X] I have read the Contribution Guidelines
[X] I have added tests for all changes in this PR
[ ] I have added documentation for the changes (in the manual)
[X] There's a new file in changelog/unreleased/ that describes the changes for our users (template here)
[X] I have run gofmt on the code in all commits
[X] All commit messages are formatted in the same style as the other commits in the repo
[X] I'm done, this Pull Request is ready for review

It looks like this change is breaking #2205 (or at least its unit tests). How do we want these to interact? The only idea I've had so far is disabling the ctime check if the ignore inode flag is on, but I'm open to anything that makes sense.

The only idea I've had so far is disabling the ctime check if the ignore inode flag is on, but I'm open to anything that makes sense.

The ctime value really only makes sense on the exact same inode, so this seems to me like a reasonable way of handling this.

Codecov Report

Merging #2212 into master will decrease coverage by 4.46%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2212      +/-   ##
==========================================
- Coverage   50.92%   46.46%   -4.47%
==========================================
  Files         178      174       -4
  Lines       14530    14498      -32
==========================================
- Hits         7399     6736     -663
- Misses       6058     6754     +696
+ Partials     1073     1008      -65

Impacted Files
Coverage Δ

internal/fs/stat.go
50% <ø> (ø)
:arrow_up:

internal/archiver/archiver.go
68.78% <100%> (+0.15%)
:arrow_up:

internal/fs/stat_unix.go
89.47% <100%> (+0.58%)
:arrow_up:

internal/backend/b2/b2.go
0% <0%> (-80.69%)
:arrow_down:

internal/backend/swift/swift.go
0% <0%> (-78.83%)
:arrow_down:

internal/backend/gs/gs.go
0% <0%> (-74%)
:arrow_down:

internal/backend/azure/azure.go
0% <0%> (-69.46%)
:arrow_down:

internal/backend/swift/config.go
34.69% <0%> (-57.15%)
:arrow_down:

cmd/restic/cmd_mount.go
13.75% <0%> (-42.5%)
:arrow_down:

internal/archiver/file_saver.go
81.57% <0%> (-7.02%)
:arrow_down:

... and 4 more

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 fad9f65...00b527f. Read the comment docs.

OK, I rebased against master, and it now skips the ctime check when the --ignore-inode option is given. I also updated the text for the changelog entry.

Please excuse me, but should'nt we be giving more warning to users about this problem? Please see my rationale here.


Fine-Grained SBIR Datasets (Chair-V2 & Shoe-V2) download link is broken

Hello,
I've recently come across this work in arxiv and really enjoyed it. Thank you for making the code publicly available so quickly! 😀
I have found that the official download link for the Fine-Grained SBIR Datasets (Chair-V2 & Shoe-V2) in your group's webpage is currently not working:

(The link is broken!)
Thank you so much in advance. 🙂

https://drive.google.com/file/d/1frltfiEd9ymnODZFHYrbg741kfys1rq1/view?usp=sharing
See if it works.

https://drive.google.com/file/d/1frltfiEd9ymnODZFHYrbg741kfys1rq1/view?usp=sharing
See if it works.

It works! (ChairV2 and ShoeV2 has 400 and 2000 images each.)
Thank you so much. :smile:

Hi,  the number of sketch images is 6648/1275 from link https://drive.google.com/file/d/1frltfiEd9ymnODZFHYrbg741kfys1rq1/view?usp=sharing and https://drive.google.com/u/0/uc?id=15s2BR-QwLgX_DObQBrYlUlZqUU90EL9G&export=download, but in your paper is 6730/2000 of Shoev2 and Chairv2.  Did i put down the wrong dataset?  Looking forward to your reply . Thanks.


"describe" command doesnt display results

describe keyspaces and describe tables both return blank when I run it in cqlsh.
Connected to cql-proxy at <IP_ADDRESS>:9042 [cqlsh 6.0.0 | Cassandra <IP_ADDRESS>16 | CQL spec 3.4.5 | Native protocol v4]

I am able to retrieve results on the Astra UI using cql-proxy as well as just using the secure connect bundle, but not when I connect with the proxy.

I'm unable to reproduce the issue:
$ cqlsh
Connected to cql-proxy at <IP_ADDRESS>:9042.
[cqlsh 6.8.0 | Cassandra <IP_ADDRESS>16 | CQL spec 3.4.5 | Native protocol v4]
Use HELP for help.
cqlsh> use sketch ;
cqlsh:sketch> DESCRIBE KEYSPACES ;

system_virtual_schema  system_auth   sketch  datastax_sla        system_traces
system_schema          system_views  system  data_endpoint_auth

cqlsh:sketch> DESCRIBE TABLES ;

sketches  players  game  votes  answers

cqlsh:sketch>

I see you're using cqlsh 6.0.0. Maybe that's the issue?  Where did you install that from (so I can reproduce)?

I see. This is not cql-proxy issue. C* 4.0 added server-side describe: https://issues.apache.org/jira/browse/CASSANDRA-8005 which is not supported by Astra currently.
Before cqlsh handled the DESCRIBE operations by querying the schema tables (keyspace: system_schema), but now the server-side can handle DESCRIBE operations, but Astra doesn't.
The proxy is just forwarding the query to the server-side:
2021-12-21T09:12:28.874-0500	DEBUG	proxy/proxy.go:416	handling query	{"query": "DESCRIBE TABLES ;", "stream": 3}
2021-12-21T09:12:30.485-0500	DEBUG	proxy/proxy.go:416	handling query	{"query": "DESCRIBE TABLES ;", "stream": 4}

If you connect to Astra directly by unzip your secure connect bundle you'll run into the same issue:
unzip secure-connect-bundle.zip -d secure-connect-bundle
cd secure-connect-bundle
/path/to/cqlsh --cqlshrc cqlshrc -u <username> -p <password>

~I see you're using cqlsh 6.0.0. Maybe that's the issue? Where did you install that from (so I can reproduce)?~
Never mind. I see that's the version included with C* 4.0.

Hi there, thanks for all of the info!
So if I use cqlsh 6.8.0 would the DESCRIBE command display properly? In that first example where you tried to reproduce the issue, that was through cql-proxy right?

~I see you're using cqlsh 6.0.0. Maybe that's the issue? Where did you install that from (so I can reproduce)?~
Never mind. I see that's the version included with C* 4.0.

Hi there, thanks for all of the info!
So if I use cqlsh 6.8.0 would the DESCRIBE command display properly? In that first example where you tried to reproduce the issue, that was through cql-proxy right?

Correct, cqlsh 6.8.0 works properly as it's not using server-side DESCRIBE.
Yes, the first example is using cql-proxy.

Interesting, I am having a hard time getting cqlsh 6.8.0 with cql-proxy, any thoughts?

@dougwettlaufer when I would run the describe command, it would basically show nothing. I noticed the difference between my cqlsh and yours is that for some reason, mine is pulling cqlsh 6.0.0 instead of cqlsh 6.8.0 and I cant seem to figure out why

And you downloaded 6.8 from here (the dropdown might default to Astra so you'll want to make sure it says "DataStax Enterprise 6.8")? If you run cql-proxy with --debug you can see what queries are being sent from cqlsh.

Thanks - had to cd into the bin file and then run ./cqlsh
I appreciate the help. I'll close this issue now.


⚠ Spryr has degraded performance

In f49e514, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4293 ms

Resolved: Spryr performance has improved in 6448de1 after 11 minutes.


Add preview for hovering over a bond

Background

Currently the user doesn't see any preview when hovering over a bond in macromolecules mode.
There should be a preview of both monomers that participate in a bond when hovering over a bond. That preview should contain the name, the structure, and the atoms contained within the attachment points for both monomers. If some attachment points that do not participate in that bond are occupied, they should be marked in gray. The attachment points that participate in that bond should be marked in teal.

Requirements

Preview for hovering over a bond should appear with a delay of 0,5 seconds.
.....1.1. The preview should contain information about both monomers:
the name of the monomer,
the structure of the monomer,
the atoms contained within the attachment points,
the attachment point that participates in the bond (that the user is hovering over) should be marked in teal,
and if the monomer has any other attachment points that participate in other bonds (not the bond that the user is hovering over), that attachment point should be marked in gray.

.
.
Preview placement is described bellow.

.....2.1. The preview should appear in relation to the center of the bond (consider that the bond starts in the centers of monomers).
.....2.2. If the bond is vertical, the preview should appear on the left or on the right, depending on availability of space.
.....2.3. If the bond is horizontal, the preview should appear above or bellow, depending on availability of space.
.....2.4. The preview should appear at the appropriate distance from the bond so it doesn't overlap with the monomers who participate in the bond.
..........For example: if the preview shows up on the left side of the bond, the right edge of the preview should be a certain distance from the left edge of the monomer who is further left.

(Image for better understanding)
.
.
4. Hovering over the bond with the select tool should highlight the monomers and the bond the same way it currently is highlighted for hovering over with the bond tool.
Currently, hovering over a bond with the tool bond:

Currently, hovering over a bond with the select tool:

Verified.
Versions

Ketcher Version 2.25.0-rc.1 Build at 2024-09-03; 15:31:03
Indigo Toolkit Version 1.24.0-rc.1.0-gb8f099851-wasm32-wasm-clang-19.0.0
Chrome Version 128.0.6613.120 (Official Build) (64-bit)
Win10


Update documentation for Electron5 changes?

The documentation for webFrame.setSpellCheckProvider does not require a 'true' flag in the second position, anymore.
####### webFrame.setSpellCheckProvider('en-US', true, new SpellCheckProvider('en-US'))
https://electronjs.org/docs/api/web-frame#webframesetspellcheckproviderlanguage-provider
This throws an error in Electron version 5 and higher. I have not tried this with previous versions.

Oh actually I guess this doesn't require a new version of the library at all since it was electron's APIs that changed, not the library. Cool!

I guess technically we should maintain a version of the README for Electron <= 5… I'm fine waiting to see if anyone complains though. :) I don't have a sense of what Electron versions are commonly in use (our company does not use Electron anymore for the moment).

Oh actually I guess this doesn't require a new version of the library at all since it was electron's APIs that changed, not the library. Cool!

Yeah, it's a change in Electron's API. I was just experimenting with spellchecking in an app today and ran into this. I haven't gotten the library to work just yet, but the latest API does not have that autocorrect flag.  node-spellchecker still works, I'll try to see why I couldn't get this to work.

I guess technically we should maintain a version of the README for Electron < 5… I'm fine waiting to see if anyone complains though. :) I don't have a sense of what Electron versions are commonly in use (our company does not use Electron anymore for the moment).

Oh, okay.
Thanks. Cheers


Issue with the process of bruteforcing

When I try to use it I choose the automatic attack, put the username I whant then it doesn't matter how many  passwords I choose it gives me this: "fatal error:: Tor configuration invalid or server down :: [Errno 111] Connection refused".
What's happening? Have I done something wrong? How can I fix it?

https://github.com/marik22354/Instagram-Password-Cracker_V4

Try this out


Include Support For RVT Script

New Language Grammar
Changes

Added RVT Script Language Grammar
Checklist

[X] Added markup tests, or they don't apply here because...
[x] Updated the changelog at CHANGES.md

Changeling entry as well, please. Thanks!

Updated the changelog and and added the alias.


"DB::Exception: No active replicas" after DROP TABLE fails

Hi, this is a bug I've encountered today - after DROP TABLE fails because of max_table_size_to_drop, it leaves the table in a weird state until the table is reattached. How to reproduce:

Attempt to drop a table exceeding max_table_size_to_drop

:) DROP TABLE test

Received exception from server:
Code: 359. DB::Exception: ... DB::Exception: Table test was not dropped.
Reason:
1. Table size (55.83 GB) is greater than max_table_size_to_drop (50.00 GB)
2. File '/clickhouse/flags/force_drop_table' intedned to force DROP doesn't exist
How to fix this:
1. Either increase (or set to zero) max_table_size_to_drop in server config and restart ClickHouse
2. Either create forcing file /clickhouse/flags/force_drop_table and make sure that ClickHouse has write permission for it.
Example:
sudo touch '/clickhouse/flags/force_drop_table' && sudo chmod 666 '/clickhouse/flags/force_drop_table'.

Attempt to drop partitions to make it smaller

:) ALTER TABLE test DROP PARTITION '201706'
Received exception from server:
Code: 254. DB::Exception: Received from 36s154.in.cfops.it:9000, <IP_ADDRESS>. DB::Exception: No active replicas.

It's not either possible to add or modify columns.

:+1: https://github.com/yandex/ClickHouse/pull/872


Connecting Puppeteer to a Chrome-Launcher instance.

Steps to reproduce
Tell us about your environment:

Puppeteer version: v1.5.0
Platform / OS version: Mac OS X El Capitan v10.11.6
URLs (if applicable):
Node.js version: v10.2.1

What steps will reproduce the problem?
1.
const chromeLauncher = require('chrome-launcher');
const puppeteer = require('puppeteer');
const request = require('request');
const util = require('util');
(async() => {
const chrome = await chromeLauncher.launch({
startingUrl: 'http://www.google.com'
});
const resp = await util.promisify(request)(http://localhost:${chrome.port}/json/version);
const {webSocketDebuggerUrl} = JSON.parse(resp.body);
const browser = await puppeteer.connect({
browserWSEndpoint: webSocketDebuggerUrl
});
const page = browser.newPage();
})();
What is the expected result?
Puppeteer connects with the chrome launcher instance and creates a new page.
What happens instead?
Stays on starting url (google.com) unsure if it is actually connected to it or not.

This should work. Make sure chrome launcher launches Chrome 69; otherwise, things won't work.

I am still not getting , how to connect puppeteer with chome instace ? give me live example with that open third-party website using browser instace (if possible !)

There's an example on
https://github.com/GoogleChromeLabs/puppeteer-examples/blob/master/lighthouse/chromelauncher_puppeteer.js
.
I'd use page.goto() to navigate to the URL. IOW use chrome launcher to only
launch a new instance of chrome, use puppeteer for everything else.
On Wed, Dec 12, 2018, 4:08 AM MeetPatel5<EMAIL_ADDRESS>wrote:

I am still not getting , how to connect puppeteer with chome instace ?
give me live example with that open third-party website using browser
instace (if possible !)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/puppeteer/issues/2790#issuecomment-446565678,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOigDKuJihVBv_FFq0rYfGEn17TlTSkks5u4PGogaJpZM4Uy0ME
.


Proposal: Namespaces

Preamble
Currently Elm has two levels of namespaces: modules and packages. The former of which is impossible to nest and the latter a tool outside of the code itself.
The benefits of namespaces
Namespaces enable the reuse of names – which simplifies naming by removing the necessity of overly verbose names to avoid naming collisions – and grouping of code spread across multiple files into one architectural unit – which is useful for human readability.
The proposal
Declaring namespaces
namespace A.Alpha.Utils with
module Helper exposing (..)
.
.

I propose that namespaces:

contain only modules and namespaces.
be implicitly declared, as such the compiler will have to detect possible misspellings.
also be used as file namespaces i.e. directories:

src +
    |- A +
    |    |- Alpha +
    |    |        |- App +
    |    |        |      |- Eval.elm
    |    |        |      |- Print.elm
    |    |        |      \- Read.elm
    |    |        \- Utils +
    |    |                 |- Helper.elm
    |    |                 \- Wrapper.elm
    |    \- Beta +
    |- B +
    |    |- Alpha +
    |    |- Beta +
    |    |- Master.elm
    |    \- Slave.elm
.
.

Importing namespaces
I propose that the import syntax should be the same as for modules with some additions to account for their greater capability.
.
.
import A.Alpha.Utils.Helper as Helper exposing (..)
import A.Alpha.App as App exposing (Read exposing (..), Eval)
import A.Alpha
import B exposing (..)
.
.

Let's go through the list of examples one by one.

The first import statement is importing src/A/Alpha/Utils/Helper.elm with all of its functions and constants available as unqualified imports.
The second statement is importing all modules contained in src/A/Alpha/App/ with qualified alias App and exposes the Read and Eval modules as unqualified imports with Read further exposing all of its content.
The third statement is importing all namespaces contained in src/A/Alpha/ as qualified imports and as such must all be prefaced with A.Alpha.
Example: A.Alpha.Utils.Wrapper.functionOne x
The fourth statement is importing all namespaces and modules contained in src/B/ as unqualified imports.
Example: Master.drive (Slave.newWith Slave.Id 1413)

Avoiding collisions
In my probing questions (#2047) a day ago I was made aware of the problem with namespace collisions (#1625).
On the module level all collisions between modules and namespaces will be introduced by the user and as such will have to be resolved by the user. As namespaces are a new element and not a change their introduction will cause no collisions because no namespaces will exist at that point in time.
On the package level my proposal adds no new collision opportunities to the issue because the implicit declaration will automatically merge identically named namespaces originating from two packages. However the old problem of conflicting module names will still be present. If one import has a module with the same name as a namespace from another that is equivalent to two modules having the same name. :Ü™

We generally try to track specific bugs in issues, and have discussions about proposals in https://discourse.elm-lang.org/ where more people will see it and give feedback.
I have been using Haskell for about a decade now, and have never felt like something like this was missing, but perhaps folks on discourse will reveal other perspectives. So further discussion should happen there.


Multiple Sculk Tombs / Ancient Sculk Nodes Spawning with C2ME installed.

I launched a test world and checked (0,0) for the Sculk Tomb. Inside, I found 2 tombs - one fully generated, and a second one that looks to have been partially generated and then overwritten by the other one. Due to this, I have 2 Ancient Nodes in my world.

This happened right after I installed C2ME (Concurrent Chuck Management Engine), via Sinytra Connector. It may be an unintended side effect of C2ME's method of generating chunks. This is taken directly from their github page:
"C2ME does not sacrifice vanilla functionality or behavior, or alter the vanilla world generation in the name of raw speed by default. However, due to the non-determinism of vanilla world generation, worlds will vary significantly run-to-run even with the same seed. This is not a bug on our side."
I am using the latest version available for 1.20.1 for all these mods.
latest.log

I tested the same seed with C2ME installed, and it happened again. However, the same seed without C2ME generates normally.
I tested a different seed with C2ME installed, and I once again had 2 Sculk Tombs - one split in half, the other fully generated.

Ahh, multi-threading mods, the bane of my modding career. I will investigate to see if there is any way for me to fix this.
The reason it spawns two is because I use a boolean variable to check whether the tomb has spawned. This works fine on single threaded world generation, but defiantly is causing this issue for multi-threaded world gen. My initial idea is to maybe store in the save data instead if the tomb has been spawned, but I fear a race condition with that. We'll see what works out.


Moving To New Project Arabic not supported !!, please i need help

Hi Guys,
i have try to use this library a lot, example is working well in all languages, but when i try to move files to existing project it is make problems when device is arabic !!.
i can't change the language to base language (english) again.
but when i use existing example it is working fine, so please can anyone help me if there is something should i do to work it well without moving all of my files to existing example !!.
waiting your response.
Best,

Hi,
Only arabic?
You did everything according to the tutorial?
With using USE_ON_FLY_LOCALIZATION or not?

yes sure i make eveything like example and i used USE_ON_FLY_LOCALIZATION and i try without it everything working well, but when device is arabic and try to change app lang to english not working.
when i use this example everything working fine.
i guess there is something in build setting ?!!, or in xcode project version !!.

There are no special settings in xcode project, I don't know what the problem is. Your project with public access?

ya i know that, jst guessing :(
here is my project if you please can take a look on it.
https://www.dropbox.com/s/023hvk4wxs4cuq2/LanguageChanger.zip?dl=0

Because your storyboard has not localization file. See the screenshot please. Select a checkmark and the issue will be resolved.

oooooooooh it is working perfect now, thanks a lot :)

Not a problem :)
Please 'star' my repository, I will be very grateful.

sure i ll, u helped me a lot :)


Add information about how to actually use it to the readme

Right now the readme says how to require a module. That's pretty obvious.
What I would like to know is:

usage
configuration
main methods I can call
troubleshooting
caveats

Hey, I am on vacation now but maybe next week I can help you. TBH, I really like this project and wanted to make it a lot better but right now I focused all my energy on pnpm.
Would an example project help you to understand?


feat(rosdep): add libqt5charts5-dev

Please add the following dependency to the rosdep database.
Package name:
libqt5charts5-dev
Package Upstream Source:
See https://doc.qt.io/qt-5/qtcharts-index.html
Purpose of using this:
It is useful when we develop rviz plugin with qt charts.
Distro packaging links:
Links to Distribution Packages

Debian: https://packages.debian.org/

https://packages.debian.org/bookworm/libqt5charts5-dev

Ubuntu: https://packages.ubuntu.com/

https://packages.ubuntu.com/search?keywords=libqt5charts5-dev&searchon=names&suite=all&section=all

Fedora: https://packages.fedoraproject.org/

IF AVAILABLE

Arch: https://www.archlinux.org/packages/

IF AVAILABLE

Gentoo: https://packages.gentoo.org/

IF AVAILABLE

macOS: https://formulae.brew.sh/

IF AVAILABLE

Alpine: https://pkgs.alpinelinux.org/packages

IF AVAILABLE

NixOS/nixpkgs: https://search.nixos.org/packages

OPTIONAL

openSUSE: https://software.opensuse.org/package/

IF AVAILABLE

rhel: https://rhel.pkgs.org/

IF AVAILABLE

Please Add This Package to be indexed in the rosdistro.
ROSDISTRO NAME
The source is here:
http://sourcecode_url
Checks

[ ] All packages have a declared license in the package.xml
[ ] This repository has a LICENSE file
[ ] This package is expected to build on the submitted rosdistro

@clalancette @wjwwood I've submitted #39791 as a followup PR to fix the name of the entry in the rosdep index, all the other Qt5 development packages have the -dev suffix


quic: support in-place filterChainUpdate

Need to add handling in udp case here: https://github.com/envoyproxy/envoy/blob/4706ee01abe191eef73c64d86c1835baf566323c/source/server/connection_handler_impl.cc#L40

lazy-ask: was this not accepting updates to the quic filter chain, or not being able to in-place add/remove quic listeners?

The call to listener.second.tcpListener()->get().updateListenerConfig(config); is guarded by if (config.listenSocketFactory().socketType() == Network::Socket::Type::Stream) {. The ask is to do the same thing for datagram listeners.

OK, I think we need to either support this for alpha or make it really clear in docs it's not yet supported.
It shouldn't be too much work to forward packets for old connections to the old listener and new to the new listener, but it's not trivial.

The ownership of the filter chain is not clear to me: Quic listener need to decide whether the old and new config has filter chain only change.
Also, the per worker thread listener needs to track what connections are bind to the gone filter chain. AFAIK this is done in ActiveTcpListener, the quic listener needs a similar accounting.

Ok, I'm going to note lack of support in the docs PR, so removing this from the Alpha list.


After compile, the file "component" not found.

Hi, I have a problem when I try to use angular.
here is my gulp task:
  var sourceTsFiles = ['./scripts/**/*.ts', './typings/angular2.d.ts'];
    var tsResult = gulp.src(sourceTsFiles)
                       .pipe(sourcemaps.init())
                       .pipe(tsc(tsProject));

        tsResult.dts.pipe(gulp.dest('./app/definitions'));

        return tsResult.js
                        .pipe(sourcemaps.write('.'))
                        .pipe(gulp.dest('./app/js'));
                        cb;

and my typescript file:
import {bootstrap} from 'angular2/platform/browser';
import {Component} from 'angular2/core';
import {TodoInput} from './component';

@Component({
	selector: 'app',
	directives: [TodoInput],
	template: '
hello world, <todo-input></todo-input>
'
})

class App {}
bootstrap(App);

after compile I got a error /js/component 404 (Not Found)
I am not sure what's the problem...

ok, I found my problem. it's about the systemjs config settings.