static build failed

/rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -S/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK -B/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build --check-build-system CMakeFiles/Makefile.cmake 0
/rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -E cmake_progress_start /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/CMakeFiles /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[1]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make -f ThirdParty/LBFGS/CMakeFiles/LibLBFGS.dir/build.make ThirdParty/LBFGS/CMakeFiles/LibLBFGS.dir/depend
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
cd /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build && /rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -E cmake_depends "Unix Makefiles" /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/ThirdParty/LBFGS /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/ThirdParty/LBFGS /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/ThirdParty/LBFGS/CMakeFiles/LibLBFGS.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make -f ThirdParty/LBFGS/CMakeFiles/LibLBFGS.dir/build.make ThirdParty/LBFGS/CMakeFiles/LibLBFGS.dir/build
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make[2]: Nothing to be done for 'ThirdParty/LBFGS/CMakeFiles/LibLBFGS.dir/build'.
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
[  0%] Built target LibLBFGS
make -f Modules/Common/src/CMakeFiles/LibCommon.dir/build.make Modules/Common/src/CMakeFiles/LibCommon.dir/depend
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
cd /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build && /rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -E cmake_depends "Unix Makefiles" /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/Common/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/Common/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/Common/src/CMakeFiles/LibCommon.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make -f Modules/Common/src/CMakeFiles/LibCommon.dir/build.make Modules/Common/src/CMakeFiles/LibCommon.dir/build
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make[2]: Nothing to be done for 'Modules/Common/src/CMakeFiles/LibCommon.dir/build'.
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
[  5%] Built target LibCommon
make -f Modules/Numerics/src/CMakeFiles/LibNumerics.dir/build.make Modules/Numerics/src/CMakeFiles/LibNumerics.dir/depend
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
cd /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build && /rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -E cmake_depends "Unix Makefiles" /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/Numerics/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/Numerics/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/Numerics/src/CMakeFiles/LibNumerics.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make -f Modules/Numerics/src/CMakeFiles/LibNumerics.dir/build.make Modules/Numerics/src/CMakeFiles/LibNumerics.dir/build
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make[2]: Nothing to be done for 'Modules/Numerics/src/CMakeFiles/LibNumerics.dir/build'.
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
[ 15%] Built target LibNumerics
make -f Modules/Image/src/CMakeFiles/LibImage.dir/build.make Modules/Image/src/CMakeFiles/LibImage.dir/depend
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
cd /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build && /rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -E cmake_depends "Unix Makefiles" /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/Image/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/Image/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/Image/src/CMakeFiles/LibImage.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make -f Modules/Image/src/CMakeFiles/LibImage.dir/build.make Modules/Image/src/CMakeFiles/LibImage.dir/build
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make[2]: Nothing to be done for 'Modules/Image/src/CMakeFiles/LibImage.dir/build'.
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
[ 31%] Built target LibImage
make -f Modules/IO/src/CMakeFiles/nifticlib.dir/build.make Modules/IO/src/CMakeFiles/nifticlib.dir/depend
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
cd /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build && /rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -E cmake_depends "Unix Makefiles" /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/IO/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/IO/src/CMakeFiles/nifticlib.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make -f Modules/IO/src/CMakeFiles/nifticlib.dir/build.make Modules/IO/src/CMakeFiles/nifticlib.dir/build
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make[2]: Nothing to be done for 'Modules/IO/src/CMakeFiles/nifticlib.dir/build'.
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
[ 31%] Built target nifticlib
make -f Modules/IO/src/CMakeFiles/gifticlib.dir/build.make Modules/IO/src/CMakeFiles/gifticlib.dir/depend
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
cd /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build && /rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -E cmake_depends "Unix Makefiles" /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/IO/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/IO/src/CMakeFiles/gifticlib.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make -f Modules/IO/src/CMakeFiles/gifticlib.dir/build.make Modules/IO/src/CMakeFiles/gifticlib.dir/build
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make[2]: Nothing to be done for 'Modules/IO/src/CMakeFiles/gifticlib.dir/build'.
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
[ 32%] Built target gifticlib
make -f Modules/IO/src/CMakeFiles/metaio.dir/build.make Modules/IO/src/CMakeFiles/metaio.dir/depend
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
cd /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build && /rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -E cmake_depends "Unix Makefiles" /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/IO/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/IO/src/CMakeFiles/metaio.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make -f Modules/IO/src/CMakeFiles/metaio.dir/build.make Modules/IO/src/CMakeFiles/metaio.dir/build
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make[2]: Nothing to be done for 'Modules/IO/src/CMakeFiles/metaio.dir/build'.
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
[ 33%] Built target metaio
make -f Modules/IO/src/CMakeFiles/LibIO.dir/build.make Modules/IO/src/CMakeFiles/LibIO.dir/depend
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
cd /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build && /rds/bear-apps/2020a/EL8-p9/software/CMake/3.16.4-GCCcore-9.3.0/bin/cmake -E cmake_depends "Unix Makefiles" /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/IO/src /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/IO/src/CMakeFiles/LibIO.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make -f Modules/IO/src/CMakeFiles/LibIO.dir/build.make Modules/IO/src/CMakeFiles/LibIO.dir/build
make[2]: Entering directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
[ 33%] Building CXX object Modules/IO/src/CMakeFiles/LibIO.dir/IOConfig.cc.o
cd /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/Modules/IO/src && /rds/bear-apps/2020a/EL8-p9/software/GCCcore/9.3.0/bin/c++  -DHAVE_EXPAT -DHAVE_MIRTK_Common -DHAVE_MIRTK_Image -DHAVE_MIRTK_Numerics -DHAVE_PNG -DHAVE_VTK -DHAVE_ZLIB -DMIRTK_IO_STATIC_DEFINE -DMIRTK_WITH_PROFILING -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/src -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/include -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build/include -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/src -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/include -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/Common/include -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/Numerics/include -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/Image/include -I/rds/bear-apps/2020a/EL8-p9/software/libpng/1.6.37-GCCcore-9.3.0/include -I/rds/bear-apps/2020a/EL8-p9/software/zlib/1.2.11-GCCcore-9.3.0/include -I/rds/bear-apps/2020a/EL8-p9/software/expat/2.2.9-GCCcore-9.3.0/include -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/src/meta -I/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/ThirdParty/LBFGS/include -isystem /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/library/include/vtk-9.0  -O3 -DNDEBUG -fPIC   -std=c++11 -o CMakeFiles/LibIO.dir/IOConfig.cc.o -c /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/src/IOConfig.cc
In file included from /rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/src/IOConfig.cc:35:
/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/include/mirtk/MetaImageReader.h:46:13: error: ‘MetaImage’ was not declared in this scope; did you mean ‘MetaIamge’?
46 |   UniquePtr _MetaImage;
|             ^~~~~~~~~
|             MetaIamge
/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/include/mirtk/MetaImageReader.h:46:22: error: template argument 1 is invalid
46 |   UniquePtr _MetaImage;
|                      ^
/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/Modules/IO/include/mirtk/MetaImageReader.h:73:25: error: ‘MetaImage’ does not name a type; did you mean ‘MetaIamge’?
73 |   void CopyHeader(const MetaImage &);
|                         ^~~~~~~~~
|                         MetaIamge
make[2]: *** [Modules/IO/src/CMakeFiles/LibIO.dir/build.make:63: Modules/IO/src/CMakeFiles/LibIO.dir/IOConfig.cc.o] Error 1
make[2]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'
make[1]: *** [CMakeFiles/Makefile2:1523: Modules/IO/src/CMakeFiles/LibIO.dir/all] Error 2
make[1]: Leaving directory '/rds/projects/d/duanj-ai-in-medical-imaging/castles/.share/2020a-gcc9.3/download/MIRTK/build'

There's been a typo in MetaImageReader.h. Changed class MetaIamge; to class MetaImage;.


Split jsons per pack so we don't end up with a super json nightmare

The key change here is that now each pack must have its own json files in a folder named the pack class but all lowercase (so DownfallPack goes in the folder downfallpack). The only exception is for card packs of entirely base game cards, which are listed in a central place and skipped over. This is all implemented by piggy-backing off the very helpful reflection logic in AutoAdd.
Alongside that, packs are now automatically registered -- once I hooked up AutoAdd to load per-pack JSON, hooking it up to register the packs was very easy. I'll add a few comments in specific areas of interest.

Great explanation and contribution, thank you. I think requiring people to create empty files may be the wrong decision here though. I don't know if there will be a compile time impact or not, but I think this can be easily fixed.
I'll make that addition to the system myself though.

Great explanation and contribution, thank you. I think requiring people to create empty files may be the wrong decision here though. I don't know if there will be a compile time impact or not, but I think this can be easily fixed.
I'll make that addition to the system myself though.
Yeah it's easy enough to change that if you want. Just check for the existence of each file and skip any that aren't there. IMO it doesn't make much of a difference; the upside is trivial (anyone making a pack should just copy over another pack's folder), the downside is that issues with misnamed or missing files are less clear.

I'd suggest still requiring a cards JSON file for every pack, because I don't think there's any legitimate use case for a pack not having any cards. Also, that will mean you get an error on load if you name your folder or your cards json file incorrectly, which is better because it makes the problem clear.


Ajax request error - React App

Hi,
I'm in the process of creating a client where the user inputs their business phone number and the app creates their profile using the phone number search results . I'm currently trying to do a get request as follows, but I get this error:
XMLHttpRequest cannot load https://api.yelp.com/v3/businesses/search/phone?phone=<PHONE_NUMBER>0. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://<IP_ADDRESS>:8080' is therefore not allowed access. The response had HTTP status code 500.
here is the code:
var settings = {
"async": true,
"crossDomain": true,
"url": "https://api.yelp.com/v3/businesses/search/phone?phone=<PHONE_NUMBER>0",
"method": "GET",
"headers": {
"authorization": "Bearer mytoken",
}
}
$.ajax(settings).done(function (response) {
console.log(response);
});
I am working locally from my machine. What am I missing?
Thank you for your help!

@matiasironyard : Sounds like you're trying to do cross-origin resource sharing (CORS); we don't support that flow.
See https://github.com/Yelp/yelp-fusion/issues/44 for details and alternatives.

Hi,
may you clarify a few things for me please. I am building an app and need to get Hours of operation. I noticed only yelp v3 has it. So, I tried it using angularjs and I got into this same issue with jsonp.
I have tried $httpProvider.interceptors , $sceDelegateProvider.resourceUrlWhitelist, and $http.dafults.headers.common but I had no luck.
Even though, this works perfectly :
curl   -X GET   -H "Authorization: Bearer "access_token"    "https://api.yelp.com/v3/businesses/
in terminal why is it not allowed in a web app or hybrid mobile app. Last thing is,  I haven't tried that yet but on corss-platform like ionic will it work ? or it will be the same issue.?
I would like to point that the v2 with Ouath works with no problem on ionic; however, is it troubling or risky to provide Hours of operation on v2 ?
Thanks in advance.


Fixing squid:S1854  Dead stores should be removed

This pull request is focused on resolving occurrences of Sonar rule
squid:S1854 - “ Dead stores should be removed ”.
This PR will remove 135 min of TD.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S1854
Please let me know if you have any questions.
Fevzi Ozgul

Hi, in this commit a few lines are removed that should be there:
byte reserved             = buffer.get();

This line should not be removed, otherwise the buffer is in the wrong position. To remove dead stores, this can be changed to simply
buffer.get();

This would remove the warning about dead stores, but it would reduce the clarity of the code. The readers would wonder why do you do buffer.get(), and assignment to reserved clarifies it. (well, a comment might clarify that too, but I prefer a clear assignment).


Add feature flag that uses on spiffe id validation in certificates and uses spiffe id for Identity

This can't be done at same time in backwards compatible way with out re-issuing all the Service Certificates.
It might be possible to automate this but might be just as easy to just wait given time frame to flip a switch or start a new deployment with this enabled. Another option is creating a cli helper tool that can verify the certs are set through the Mesh

Since we can rely on the MRC handing rotation of the certificate for us we don't need an additional flag to insure the Serivce certs are all generated properly. #5160 uses the MRC rotation approach. Closing.


gflags is incorrectly packaged with CPack. First, it should be splitted into multiple packages with the names libgflags-dev and libgflags.  using CPackComponent. Second, the libraries are compiled for concrete architecture, so should be installed into CMAKE_INSTALL_LIBDIR.

Thanks for the suggestions, @KOLANICH, and sorry for the late reply. The default CPack configuration is not intended to be "correct" with regards to a specific packaging standard, which likely depends on your OS distribution (Debian/Ubuntu, Fedora, etc.). The CPack support exists merely to give some convenience to binary package maintainers. It can be fully configured by them to match the requirements of the different target distributions. The repository here is concerned only with the source code distribution.

How should I understand this? Are PRs fixing welcome or will they be rejected?
P.S. distro maintainers usually use own tools and bash scripts for separation. CPack is usually used to install software that has not landed into distros.

Any PR will be considered. The question in this particular case is what one considers in need of fixing.
To be clear, I don't mind modifying the CPack related parts. As you noted yourself, distro maintainers are likely using their own tools. So there doesn't seem to be any meaningful use case for CPack for this library in the first place.
Regarding your second point, the destination of architecture specific libraries, this can already be adapted to any specific need using LIBRARY_INSTALL_DIR. Regarding the main point of creating separate packages from subsets of components, I belief you can provide your own declaration of CPack components in a CPACK_PROJECT_CONFIG_FILE to achieve this.
Maybe if you elaborate on what you think would be an appropriate change?


Fix VSB phase update loop

Due to the current change in OADP 1.2 regarding not cleaning up the ReplicationSource CRs from cluster the phase VSB phase update needed some fixes. This PR makes those fixes. Basically what was happening due to the code which cascades status from ReplicationSource to VSB, the VSB phase was looping between cleanup -> completed -> snapshotbackupDone, this PR breaks the loop if the vsb is in complete state and fixes the phase cascade code. Also, skips steps from reconcile batch if the vsb is in complete state.
dataMoverImageFqin: 'quay.io/spampatt/volume-snapshot-mover:fix-phase-loop'

/cherry-pick oadp-1.2


remove entry

what is this change for? we pull some packages from that feed, i.e. Microsoft.DotNet.MSBuildSdkResolver

@filipw This was random flailing to try to understand some travis flakiness the mac machines were having last night. Please disregard :)


CVE-2007-4559 Patch

Patching CVE-2007-4559
Hi, we are security researchers from the Advanced Research Center at Trellix. We have began a campaign to patch a widespread bug named CVE-2007-4559. CVE-2007-4559 is a 15 year old bug in the Python tarfile package. By using extract() or extractall() on a tarfile object without sanitizing input, a maliciously crafted .tar file could perform a directory path traversal attack. We found at least one unsantized extractall() in your codebase and are providing a patch for you via pull request. The patch essentially checks to see if all tarfile members will be extracted safely and throws an exception otherwise. We encourage you to use this patch or your own solution to secure against CVE-2007-4559. Further technical information about the vulnerability can be found in this blog.
If you have further questions you may contact us through this projects lead researcher Kasimir Schulz.

Archive safety is already being checked:
https://github.com/dgilland/shelmet/blob/8d8fba708515ec5f50c02e08e8fe159b3fbfad53/src/shelmet/archiving.py#L575-L578
https://github.com/dgilland/shelmet/blob/8d8fba708515ec5f50c02e08e8fe159b3fbfad53/src/shelmet/archiving.py#L623-L636


Bug: Custom context menu can cover titlebar buttons like minimize/maximize/close.

I right-clicked the titlebar buttons and they got covered by the custom context menu.

I right-clicked the titlebar buttons and they got covered by the custom context menu.

https://github.com/Gaoyifei1011/WinUI3WindowMenuStyle/commit/0a22b0df7bd4c27a91a14c42d588cfedc3adbab6

WM_NCRBUTTONUP 错误的消息已经修复
WM_NCRBUTTONUP error message has been fixed

Now the app just crashes

Nvm, i fixed the crash


Leaf - N-Connecta 2022 (UK)

Just linked our 2022 Leaf N-Connect and works perfectly.
THANK YOU very much for this excellent tool.
One annoyance with the LEAF is being unable to set 80-85% charge stop to protect the battery. I can now create Automations to start charging at off-peak and stop at 85%.

Glad its working well for you.
How are you stopping the charge? One major limitation with the Nissan API and app is that there's no pause/stop charge function. Personally I have an Ohme charger and stop it through this.

Your add-in is one of the last key parts of the puzzle.
I owe you a coffee..
By reading the Leaf battery level prior to charge commence, our Leaf if 40kw, therefore 10% is 4kwh of charge.
Example:
Battery SOC - 55%
So a helper calculated 85% - 55% = 30%
Multiply 30 by 0.4 to give 12kwh.
Using the Zappi Integration, I have a manual Boost Automation which I can slide from 1 to 36. At midnight, an automation is triggered then sets the Zappi to Boost by whatever amount was set.
By creating an automation that triggers when the car is plugged in, this automation sets the amount of Boost needed from midnight to bring to 85%.
I could monitor the battery SOC using your add-in but to avoid overshooting due to Internet or other issue the SOC isn't updated, I set the amount ar start.
I can try posting the automations and helpers if they help.
So basically
Get home and pluggcar in HA detects plug in
Hone Assistant reads EV SOC and calculates amount
At midnight this is sent to the EV to start charge
ZAPPI stops once Boost amount reached
This will give the battery a long and happy life.
Hope this helps..

Just to expand on this:
I assemble Lithium Batteries for domestic Solar and off-peak storage and know plenty on longevity of Battery Cells.
Many manufacturers of EVs are now building in "Battery saver" settings which is stop charging at 80% although this can be overridden.
I was playing last night and made the target value Variable. Ideally a battery likes to sit around 50% and not below 20%. Therefore is possible to add just enough to commute with some reserve and over Winter, likely set ours to 65%.
The absolute worst thing for an EV is nightly charging from and already high level to 100% every night. At 65%, ours will last 3 days to 20% - so every 3 days it will be charged back to 65%.
Every two weeks, I'll run a nighttime 100% charge to balance the Cells in the battery.
On the dashboard- I have "Solar Charge", "Night Charge 100%" and "Limit Charge" and depending on which is selected- the Zappi will run as told.


Allow bots to buy a specific quantity of items for a set amount

Is your feature request related to a problem? Please describe.
No.
Describe the feature you'd like
Allow the bot to buy a select quantity of items for a set amount.
eg: Bot buys increments of 10 crates for 1 scrap.
Describe alternatives you've considered
There are no alternatives to automating this with the bot.
Got any bounty as a reward for anyone fulfills your request?
Do not have anything right now, this is just a suggestion.

Duplicate of #414


Create icons as svgs

We have some icons that are only available as png, as svgs are way smaller, these should also be provided as svgs. See the attached files. These are the icons that are needed as svgs

Icons (svgs) can be found 📍 here

Hey @hauf-toni, sorry to bother you and not think about that sooner but there is a few more icons we'd need a svg version from:

![app-logo](https://github.com/digitalfabrik/integreat-app/a

ssets/29095487/c7f6da5a-16d4-4e88-840d-740a6954e063)

I have added the svgs for Integreat + Malte ✅
Unfortunately, the only version of the "Hallo Aschaffenburg" Logo I could find is very poor quality. I can rebuild the svg as close to the original as possible but a high resolution image of the original logo would really help to archieve a better result. 🔍

Thank you!
@FritjofK do you know if we perhaps still have a high quality version of this icon?

If not, this is not a problem I guess, then we'll just keep the current .png icon. In the end aschaffenburg is also not paying us for this optimization.


[feature] Ignore django.security.DisallowedHost by default

Ignore django.security.DisallowedHost errors by default.

This shouldn't happen in the first place if nginx is configured correctly.


Implementation of custom methods in blueprints

I am following this guide to make my API as simple and standard as possible:
https://cloud.google.com/apis/design/custom_methods
I see this method is quite common as also I could found it at API Design Patterns and it has sense.
However, I see currently in a flask blueprint it is not possible to use ':' separator for the root path resources.
For example:
from flask.views import MethodView
from flaskimport Blueprint

blp = Blueprint('benchmarks', 'benchmarks')

@blp.route('')
class Benchmarks(MethodView)

    def get(self, query_args):
        ....

    def post(self, body_args):
        ....

This would create the following routes:

GET /benchmarks
POST /benchmarks

However, there is no simple way to create the following routes inside the blueprint:

GET /benchmarks:search
POST /benchmarks:my_custom_method

The main issue relies here
https://github.com/pallets/flask/blob/main/src/flask/blueprints.py#L93
where the only available separator after the blueprint url_prefix is '/', leading to strange combinations:

GET /benchmarks/:search
POST /benchmarks/:custom

Why not to use a resource path?
If I configure the following route:

GET /benchmarks/search
Then it might conflict with my id resource

GET /benchmarks/string:name
Threfore I cannot create a benchmark with name "search".
This is a design issue, the ':' convention was created to avoid this type of issues.

Solution?
Maybe just accept the ':' as an optional start character?

        if self.url_prefix is not None:
            if not rule:
                rule = self.url_prefix
            elif rule[0] == ':' and 'somethingelse:
                rule =  ":".join((self.url_prefix.rstrip("/"), rule.lstrip("/")))
            else:
                rule = "/".join((self.url_prefix.rstrip("/"), rule.lstrip("/")))

Although there sure might be better ways.

I don't quite understand what's being asked here, but I don't want to make the separator for blueprint prefixes configurable. You can probably subclass, or use another API library besides blueprints, to create more custom URLs.


Flex-based layout

Flexbox gives us more screen estate and less bytes (407 -> 352)! Win-win!

Closing to clean up my PR list ✌


Clone not working using the mssql flavour

Hi
I am getting the following error when doing a clone using the mssql flavour

TypeError: Cannot read property 'options' of undefined

Below doesn't work
var squel = require('squel').useFlavour('mssql');
squel.select().from('Test').clone()
But this does
var squel = require('squel')
squel.select().from('Test').clone()
It looks like the error is from MssqlLimitOffsetTopBlock constructor

This looks like a bug, thanks for reporting this. Will look into it for the next release.

Out of interest, is there a rough timeline for the next release?


Cache data into Elasticsearch

When an address is searched, store the returned json from the Rapid API & HTML from the scraper into Elasticsearch.
When a similar search is made for the same address, check Elasticsearch and return the data from there instead of making extra API calls

Done in b8bbf3cb40e3a2258aff17d41eb4e494a2fa7b0a


Bad file descriptor (Errno::EBADF) - individual tests

What
Error running individual tests
ruby -I test test/functional/[file].rb
Anything else
Similar issue: https://github.com/rails/rails/issues/41176
Run options: --seed 59036

# Running:

.Traceback (most recent call last):
	26: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:68:in `block in autorun'
	25: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:138:in `run'
	24: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `start'
	23: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `map'
	22: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `each'
	21: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `times'
	20: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:37:in `block in start'
	19: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:15:in `start'
	18: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:27:in `fork'
	17: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	16: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	15: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:10:in `block in fork'
	14: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:27:in `block in start'
	13: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:38:in `work_from_queue'
	12: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:53:in `perform_job'
	11: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:60:in `safe_record'
	10: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1138:in `method_missing'
	 9: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1158:in `with_friend'
	 8: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1139:in `block in method_missing'
	 7: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `open'
	 6: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `synchronize'
	 5: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `block in open'
	 4: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `each'
	 3: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1218:in `block (2 levels) in open'
	 2: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1262:in `alive?'
	 1: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `alive?'
/Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `wait_readable': Bad file descriptor (Errno::EBADF)
	24: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:68:in `block in autorun'
	23: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:138:in `run'
	22: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `start'
	21: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `map'
	20: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `each'
	19: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `times'
	18: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:37:in `block in start'
	17: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:15:in `start'
	16: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:27:in `fork'
	15: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	14: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	13: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:10:in `block in fork'
	12: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:32:in `block in start'
	11: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:32:in `ensure in block in start'
	10: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1138:in `method_missing'
	 9: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1158:in `with_friend'
	 8: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1139:in `block in method_missing'
	 7: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `open'
	 6: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `synchronize'
	 5: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `block in open'
	 4: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `each'
	 3: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1218:in `block (2 levels) in open'
	 2: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1262:in `alive?'
	 1: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `alive?'
/Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `wait_readable': Bad file descriptor (Errno::EBADF)
Traceback (most recent call last):
	26: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:68:in `block in autorun'
	25: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:138:in `run'
	24: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `start'
	23: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `map'
	22: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `each'
	21: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `times'
	20: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:37:in `block in start'
	19: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:15:in `start'
	18: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:27:in `fork'
	17: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	16: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	15: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:10:in `block in fork'
	14: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:27:in `block in start'
	13: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:38:in `work_from_queue'
	12: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:53:in `perform_job'
	11: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:60:in `safe_record'
	10: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1138:in `method_missing'
	 9: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1158:in `with_friend'
	 8: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1139:in `block in method_missing'
	 7: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `open'
	 6: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `synchronize'
	 5: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `block in open'
	 4: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `each'
	 3: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1218:in `block (2 levels) in open'
	 2: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1262:in `alive?'
	 1: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `alive?'
/Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `wait_readable': Bad file descriptor (Errno::EBADF)
	24: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:68:in `block in autorun'
	23: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:138:in `run'
	22: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `start'
	21: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `map'
	20: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `each'
	19: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `times'
	18: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:37:in `block in start'
	17: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:15:in `start'
	16: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:27:in `fork'
	15: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	14: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	13: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:10:in `block in fork'
	12: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:32:in `block in start'
	11: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:32:in `ensure in block in start'
	10: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1138:in `method_missing'
	 9: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1158:in `with_friend'
	 8: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1139:in `block in method_missing'
	 7: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `open'
	 6: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `synchronize'
	 5: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `block in open'
	 4: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `each'
	 3: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1218:in `block (2 levels) in open'
	 2: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1262:in `alive?'
	 1: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `alive?'
/Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `wait_readable': Bad file descriptor (Errno::EBADF)
Traceback (most recent call last):
	26: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:68:in `block in autorun'
	25: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:138:in `run'
	24: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `start'
	23: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `map'
	22: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `each'
	21: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `times'
	20: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:37:in `block in start'
	19: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:15:in `start'
	18: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:27:in `fork'
	17: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	16: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	15: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:10:in `block in fork'
	14: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:27:in `block in start'
	13: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:38:in `work_from_queue'
	12: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:53:in `perform_job'
	11: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:60:in `safe_record'
	10: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1138:in `method_missing'
	 9: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1158:in `with_friend'
	 8: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1139:in `block in method_missing'
	 7: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `open'
	 6: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `synchronize'
	 5: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `block in open'
	 4: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `each'
	 3: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1218:in `block (2 levels) in open'
	 2: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1262:in `alive?'
	 1: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `alive?'
/Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `wait_readable': Bad file descriptor (Errno::EBADF)
	24: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:68:in `block in autorun'
	23: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:138:in `run'
	22: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `start'
	21: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `map'
	20: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `each'
	19: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:36:in `times'
	18: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:37:in `block in start'
	17: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:15:in `start'
	16: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:27:in `fork'
	15: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	14: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:8:in `fork'
	13: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/fork_tracker.rb:10:in `block in fork'
	12: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:32:in `block in start'
	11: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/worker.rb:32:in `ensure in block in start'
	10: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1138:in `method_missing'
	 9: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1158:in `with_friend'
	 8: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1139:in `block in method_missing'
	 7: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `open'
	 6: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1213:in `synchronize'
	 5: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `block in open'
	 4: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1216:in `each'
	 3: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1218:in `block (2 levels) in open'
	 2: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1262:in `alive?'
	 1: from /Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `alive?'
/Users/[username]/.rvm/rubies/ruby-2.6.6/lib/ruby/2.6.0/drb/drb.rb:1005:in `wait_readable': Bad file descriptor (Errno::EBADF)
^CTraceback (most recent call last):
	4: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:68:in `block in autorun'
	3: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:145:in `run'
	2: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization.rb:46:in `shutdown'
	1: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/server.rb:62:in `shutdown'
/Users/[username]/.rvm/gems/ruby-2.6.6/gems/activesupport-<IP_ADDRESS>/lib/active_support/testing/parallelization/server.rb:62:in `sleep': Interrupt

^CTraceback (most recent call last):
	12: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:64:in `block (2 levels) in autorun'
	11: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/minitest-5.13.0/lib/minitest.rb:64:in `reverse_each'
	10: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-0.21.2/lib/minitest/simplecov_plugin.rb:11:in `block in plugin_simplecov_init'
	 9: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-0.21.2/lib/simplecov.rb:179:in `at_exit_behavior'
	 8: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-0.21.2/lib/simplecov.rb:189:in `run_exit_tasks!'
	 7: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-0.21.2/lib/simplecov/configuration.rb:197:in `block in at_exit'
	 6: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-0.21.2/lib/simplecov/result.rb:51:in `format!'
	 5: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-0.21.2/lib/simplecov/formatter/multi_formatter.rb:8:in `format'
	 4: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-0.21.2/lib/simplecov/formatter/multi_formatter.rb:8:in `map'
	 3: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-0.21.2/lib/simplecov/formatter/multi_formatter.rb:9:in `block in format'
	 2: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-html-0.12.3/lib/simplecov-html.rb:28:in `format'
	 1: from /Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-html-0.12.3/lib/simplecov-html.rb:28:in `open'
/Users/[username]/.rvm/gems/ruby-2.6.6/gems/simplecov-html-0.12.3/lib/simplecov-html.rb:28:in `initialize': Interrupt

Couldn't reproduce this with current Whitehall. All the tests in test/functional/* now seem to work fine when run in this way. Please feel free to reopen if I've missed something or if it still doesn't work for you.
In case it's useful, here's my (unsuccessful) attempt to reproduce the issue:
rbenv install
bundle install
brew services start mysql redis
export TEST_DATABASE_URL=mysql2://localhost:3306/whitehall
export DATABASE_URL=$TEST_DATABASE_URL
bundle exec rails db:reset

for f in test/functional/*.rb; do
  bundle exec ruby -I test $f
end

Example output

warning: parser/current is loading parser/ruby31, which recognizes 3.1.3-compliant syntax, but you are running 3.1.2.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
Running 2 tests in a single process (parallelization threshold is 50)
Run options: --seed 17981

# Running:

..

Finished in 0.165612s, 12.0764 runs/s, 12.0764 assertions/s.
2 runs, 2 assertions, 0 failures, 0 errors, 0 skips
warning: parser/current is loading parser/ruby31, which recognizes 3.1.3-compliant syntax, but you are running 3.1.2.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
Running 2 tests in a single process (parallelization threshold is 50)
Run options: --seed 61882

# Running:

..

Finished in 1.361546s, 1.4689 runs/s, 1.4689 assertions/s.
2 runs, 2 assertions, 0 failures, 0 errors, 0 skips
warning: parser/current is loading parser/ruby31, which recognizes 3.1.3-compliant syntax, but you are running 3.1.2.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
Running 3 tests in a single process (parallelization threshold is 50)
Run options: --seed 25128

# Running:

...

Finished in 0.824055s, 3.6405 runs/s, 4.8540 assertions/s.
3 runs, 4 assertions, 0 failures, 0 errors, 0 skips
...

Oh wait, I managed to get it happen by running the whole suite.
bundle exec rake test

warning: parser/current is loading parser/ruby31, which recognizes 3.1.3-compliant syntax, but you are running 3.1.2.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
warning: parser/current is loading parser/ruby31, which recognizes 3.1.3-compliant syntax, but you are running 3.1.2.
Please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
Running 6419 tests in parallel using 6 processes
Run options: --seed 61521

# Running:

..#<Thread:0x00000001199751c0 ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1259 run> terminated
 with exception (report_on_exception is true):
..#<Thread:0x00000001199751c0 ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1259 run> terminated
 with exception (report_on_exception is true):
~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1002:in `wait_readable': Bad file descriptor (Errn
o::EBADF)
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1002:in `alive?'
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1334:in `alive?'
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1270:in `block (3 levels) in make_pool'
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1268:in `each'
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1268:in `block (2 levels) in make_pool'
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1239:in `block in _execute'
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/monitor.rb:202:in `synchronize'
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/monitor.rb:202:in `mon_synchronize'
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1237:in `_execute'
  from ~/.rbenv/versions/3.1.2/lib/ruby/3.1.0/drb/drb.rb:1262:in `block in make_pool'

Interestingly this doesn't seem to be happening in CI 🧐

Looks like it's fixed now, on latest:
$ cd ~/govuk/govuk-docker

$ make whitehall

$ cd ~/govuk/whitehall

$ govuk-docker-run bundle exec rake test


PHP 5.5.0 as minimum requirements ?

Is PHP 5.5.0 really the minimum compatible PHP version ?
Compatibility with PHP 5.4 could be great.

Yes it is really required because we use finally and Class::class. As PHP 5.4 is not supported anymore by the PHP team and will not receiving security updates in 2 months (http://php.net/supported-versions.php) and as Debian stable includes PHP 5.6 by default, we do not plan add 5.4 support except if someone has very good reasons.

OK, thanks for this information.


Disable mouse follow when using touch screen

Description of the new feature / enhancement
With multiple monitors, one being a touch screen, the ability to disable mouse jumping to used location on the touch screen.
Leave the mouse cursor where it was last positioned using the mouse controller when the touch screen is used.
Scenario when this would be used?
I have user inter active windows open on my touch screen, allowing interaction with many instruments in a flight simulator which runs on the primary monitor. Maps etc also run on other (non touch) monitors where the mouse is used to interact with the map features.
When touching the touch monitor, that action jumps the mouse cursor to the touch monitor, away from the used postion on other monitors. This unwanted action is it able to be blocked?
Supporting information
I have a total of 4 monitors, however many flight simmers have 5 or more and once the mouse jumps away from where it is wanted that is a lot of monitor real estate to negotiate (while flying a plane) to get it back to where it is needed.

Hello and thanks for your message. I have an all-in-one pc with touch-screen and when I leave the mouse pointer in a place, then touch the screen, and then move the mouse again, the pointer re-appears at the place it was left.

Thanks Jay-o-Way. I'm guessing your all-in-one pc is a one screen setup. If you can, what would happen if you had multiple screens? And I also suspect that as your primary monitor is a touch screen this may also make a difference.
In my case I have 3 standard PC monitors, one of these being the primary display (WIN11 OS) and the touch screen is #4 .
I did find references to this problem as far back as 2015, but any possible solutions related to using programming with mouse hook commands, which is well beyond my capabilities. Therefor the request to have this programmed as a feature in Power Toys.

Mine has the internal screen + 1 external via hdmi.
Other then that I don't know much about how it works, haha. Just saying.

Also: looks like it depends on the app or something. Because what I describe works only on Chrome. Not in Windows.

/dup https://github.com/microsoft/PowerToys/issues/15427

/dup #15427

@crutkas This is not a duplicate of referenced issue; this issue is regarding the use of touchscreen display along with a multi-monitor setup with a mouse. I experience the same as OP: If the mouse cursor is positioned on my main monitor, touching anywhere on my laptop touch screen moves the cursor to that position. In a multi-monitor touch/mouse hybrid setup, it would be nice if PowerToys could help to avoid having to manually move the mouse cursor back in place to the latest used position (in this case on a separate monitor) after using the touchscreen. This is the same issue OP is describing.
My understanding is that the referenced duplicate issue refers to a shortcut for fully disabling touch screen and/or the mousepad.
Is it okay to re-open this issue?

Touch Mouse Tools solves this problem.

It does. But be aware that it is a paid tool after a 30 days trial.


Import fails with Remix Server

I'm not sure, but there might be a problem with the packaging of the lib or something similar. I've encountered a problem with the following import:
import {useCombobox, autocomplete} from "@szhsin/react-autocomplete";
Running locally via Vite this works fine. However, in a production build, the Remix server fails with the following:
web-1       | import { useCombobox, autocomplete } from "@szhsin/react-autocomplete";
web-1       |                       ^^^^^^^^^^^^
web-1       | SyntaxError: Named export 'autocomplete' not found. The requested module '@szhsin/react-autocomplete' is a CommonJS module, which may not support all module.exports as named exports.
web-1       | CommonJS modules can always be imported via the default export, for example using:
web-1       |
web-1       | import pkg from '@szhsin/react-autocomplete';
web-1       | const { useCombobox, autocomplete } = pkg;
web-1       |
web-1       |     at ModuleJob._instantiate (node:internal/modules/esm/module_job:146:21)
web-1       |     at async ModuleJob.run (node:internal/modules/esm/module_job:229:5)
web-1       |     at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)
web-1       |     at async getBuild (file:///app/build/server/index.js:400:101)
web-1       |     at async build (file:///app/build/server/index.js:412:32)
web-1       |     at async requestHandler (/app/node_modules/@remix-run/server-runtime/dist/server.js:65:44)
web-1       |     at async /app/node_modules/@remix-run/express/dist/server.js:41:22
web-1       | Error creating build: file:///app/build/server/remix.js:30

The issue was fixed by marking the package as an ES module, released in v1.0.2.


DeepLab: output_tensor = "ResizeBilinear_3:0"

Hi Matthijs,
I downloaded, fine-tuned and froze the model "deeplabv3_mnv2_dm05_pascal_trainval_2018_10_01.tar.gz" from the DeepLab's model zoo.
I am using 'deeplab.py' to convert the model I trained to CoreML format. In your example code in 'deeplab.py', you show how to convert the model "deeplabv3_mnv2_pascal_trainval/frozen_inference_graph.pb". When I inspect the frozen graph of "deeplabv3_mnv2_dm05_pascal_trainval_2018_10_01.tar.gz" with Netron I find that there is no "Bilinear_3:0" layer (it goes up to bilinear_2) and that the mul_1 is called "mul".
May I ask you from what link you downloaded the model you used in your example? I would like to compare that version with the version I downloaded to understand what has changed between them.
Thanks a lot
Kind regards

The link from the book is http://download.tensorflow.org/models/deeplabv3_mnv2_pascal_trainval_2018_01_29.tar.gz

I downloaded the model from that link, but the model ends at "ResizeBilinear_2", there is no layer named "ResizeBilinear_3". Instead, there is a "ResizeNearestNeighbours" layer at the end (I am not sure if this layer was there in the previous graph).
If I run deeplab.py I get:
ValueError: output name: ResizeBilinear_3:0, was provided, but the Tensorflow graph does not contain a tensor with this name
Perhaps the model was updated (e.g., "Mul_1" seems to be "Mul" now)?

I just downloaded the one from the link I provided and it definitely has a ResizeBilinear_3 and a mul_1. It's possible this got changed in more recent versions, but 2018_01_29 still has them.

Yes, you are right. That version has the ResizeBilinear_3. The newer versions changed that to a "ResizeNearestNeihgbor" layer. Thanks a lot for the response and the link, I can compare the graphs of the two models now.
The newest model also has layers "Slice" and "Shape" that seem not yet supported for conversion with coreml. So the old version is very useful to me right now
Thanks a lot for you fast response


Fix the group creation of the opam user

-g means GECOS whereas -G means group
Issue observed in https://github.com/ocaml/opam-repository/pull/17882

good catch!

good catch!

Should be good to go now.
Btw are there any news about the move to the ocurrent org for this repo?

Should be good to go now.
Btw are there any news about the move to the ocurrent org for this repo?

No worries. Glad I could be of help. Another version of ocsigenserver is coming up soon.

No worries. Glad I could be of help. Another version of ocsigenserver is coming up soon.

This PR breaks the build in docker-base-images. Investigating...
addgroup: group 'opam' in use
The command '/bin/sh -c addgroup -S -g 1000 opam' returned a non-zero code: 1

This PR breaks the build in docker-base-images. Investigating...
addgroup: group 'opam' in use
The command '/bin/sh -c addgroup -S -g 1000 opam' returned a non-zero code: 1

fixed in c916c7ea8a8b3deb5eda53babeb130ec5f88cc1d

fixed in c916c7ea8a8b3deb5eda53babeb130ec5f88cc1d

Sorry about that

Sorry about that


require ++ppn with ++mpiexec-no-n for smp charmrun

Let's suppose a user types "charmrun ++mpiexec-no-n ++remote-shell srun +p12 +ppn 6 namd2 ..." and then get this error:
Charmrun does not recognize the flag '+ppn'.
Charm++'s flags need to be placed *after* the program name.

So they change to "charmrun ++mpiexec-no-n ++remote-shell srun +p12 namd2 +ppn 6 ..." (or make this mistake in the first place), and try again to find that they get a hang during startup, and adding ++verbose only gives something like this:
Charmrun> scalable start enabled.
Charmrun> charmrun started...
Charmrun> added host "<IP_ADDRESS>", IP:<IP_ADDRESS>
Charmrun> Charmrun = <IP_ADDRESS>, port = 42037
Charmrun> Sending "$CmiMyNode <IP_ADDRESS> 42037 24046 0" to client 0.
Charmrun> find the node program "/shared/home/jim/NAMD_2.14b1_Linux-x86_64-netlrts-smp-CUDA/namd2" at "/shared/home/jim" for 0.
Charmrun> Starting srun ./charmrun.220654
Charmrun> mpiexec started
Charmrun> node programs all started
Charmrun> Waiting for 0-th client to connect.
Charmrun remote shell(<IP_ADDRESS>.0)> remote responding...
Charmrun remote shell(<IP_ADDRESS>.0)> remote responding...
Charmrun remote shell(<IP_ADDRESS>.0)> starting node-program...
Charmrun remote shell(<IP_ADDRESS>.0)> starting node-program...
Charmrun> Waiting for 1-th client to connect.

If they use ++mpiexec instead of ++mpiexec-no-n the behaviour is a little more reasonable:
Charmrun> scalable start enabled.
Charmrun> charmrun started...
Charmrun> added host "<IP_ADDRESS>", IP:<IP_ADDRESS>
Charmrun> Charmrun = <IP_ADDRESS>, port = 36637
Charmrun> Sending "$CmiMyNode <IP_ADDRESS> 36637 24185 0" to client 0.
Charmrun> find the node program "/shared/home/jim/NAMD_2.14b1_Linux-x86_64-netlrts-smp-CUDA/namd2" at "/shared/home/jim" for 0.
Charmrun> Starting srun ./charmrun.220793
Charmrun> mpiexec started
Charmrun> node programs all started
Charmrun> Waiting for 0-th client to connect.
srun: error: Unable to allocate resources: Requested node configuration is not available
Charmrun> Timeout waiting for node-program to connect

Also, the timeout actually works when the 0-th client fails to connect, while charmrun seems willing to wait forever for the 1-th client to connect.
Basically, if the user says "trust me, mpiexec/ibrun/srun/etc. will do the right thing" but they use +ppn instead of ++ppn, charmrun will wait forever for processes that will never launch because it is expecting one process per pe and the number of processes is derived via +p/++ppn rather than being specified directly. The easiest way to avoid exposing the user to this hang is to require an explicit ++ppn when ++mpiexec-no-n is used with an smp layer, and maybe to also have charmrun print the number of pes, nodes, ppn, etc. before attempting to launch them.

This is not an issue if ++n is used instead of +p, so the rule should be to require ++ppn whenever ++mpiexec-no-n is used with +p on an smp layer.


Crash occurs when viewing recipes with REI (any version) Create: 1.20.1-0.5.1-f

Describe the Bug
Game crashes when viewing certain recipes that require a mixer, press, or basin. The crash occurs when hovering over the ingredient in the second slot of the recipe. Some recipes do not trigger a crash (such as the chocolate or mud recipe) while others do (like andesite/andesite alloy mixing recipe). Issue does not seem to be related to items being from create mod since the andesite mixing recipe has diorite and cobblestone and the crash still occurs. I believe it has to do with the second slot of the recipe in the GUI.
Reproduction Steps

Open game using create 0.5.1-f and any version of REI
Search any recipe that requires a basin/press/mixer (such as andesite alloy)
Hover over the second ingredient needed for the recipe (for andesite alloy, the nugget)
Game crashes unexpectedly
...

Expected Result
Game should function as normal and not crash. You should be able to hover over the ingredient.
Screenshots and Videos
https://youtu.be/fuFkbECRp0o
Crash Report or Log
https://docs.google.com/document/d/1oJljl49J0NzxjARdi91LiBKE2kYpHAK4VuMgEVhdbhs/edit?usp=sharing
Operating System
Windows 10
Mod Version
0.5.1f
Minecraft Version
1.20.1
Other Mods

Additional Context
Downgrading to create fabric version 0.5.1-d fixes the crash. Issue is also being tracked on REI issue tracker (https://github.com/shedaniel/RoughlyEnoughItems/issues/1597). Issue does not persist when using JEI.

known issue fixed in dev

gathering this may also affect sandpaper recipe. glad to know its fixed pending update. in the mean time i will be careful what i mouse over in recipe's from create. would appreciate an update here when the fixed version is released :)


Support uuid in json output

Coverage increased (+0.2%) to 99.565% when pulling f211b11784d6d992618696a39043c3ecb4f09f2a on Omniflux:output_uuid into 9cac91105b3384030221b9187d15a5754eb3fc03 on timothycrosley:develop.

Coverage increased (+0.2%) to 99.565% when pulling f211b11784d6d992618696a39043c3ecb4f09f2a on Omniflux:output_uuid into 9cac91105b3384030221b9187d15a5754eb3fc03 on timothycrosley:develop.

Coverage increased (+0.2%) to 99.565% when pulling f211b11784d6d992618696a39043c3ecb4f09f2a on Omniflux:output_uuid into 9cac91105b3384030221b9187d15a5754eb3fc03 on timothycrosley:develop.

Coverage increased (+0.2%) to 99.565% when pulling f211b11784d6d992618696a39043c3ecb4f09f2a on Omniflux:output_uuid into 9cac91105b3384030221b9187d15a5754eb3fc03 on timothycrosley:develop.

Coverage increased (+0.2%) to 99.565% when pulling f211b11784d6d992618696a39043c3ecb4f09f2a on Omniflux:output_uuid into 9cac91105b3384030221b9187d15a5754eb3fc03 on timothycrosley:develop.

Coverage increased (+0.2%) to 99.565% when pulling f211b11784d6d992618696a39043c3ecb4f09f2a on Omniflux:output_uuid into 9cac91105b3384030221b9187d15a5754eb3fc03 on timothycrosley:develop.

Looks perfect, thank you!


Error messages

I get an error when opening Office 2013 documents after upgrading from Windows 7 to Windows 10, such as Word encountered an error trying to open the file or The file is corrupted and cannot be opened.

Closing since the issue is unrelated to .NET.

Closing since the issue is unrelated to .NET.


Integration problem with django.contrib.auth.models.User

Hello, I'm trying to integrate dry-rest-permissions with django.contrib.auth.models.User.
All my custom models have the permissions defined at models.py, but User isn't defined there.
What's the proper way of adding DRY REST permissions to django.contrib.auth.models.User?
Here's the error when I try to access the API:
AssertionError at /api/usuarios/
'<class 'django.contrib.auth.models.User'>' does not have 'has_read_permission' or 'has_list_permission' defined.
Request Method: 	GET
Request URL: 	http://localhost:8000/api/usuarios/
Django Version: 	1.9.2
Exception Type: 	AssertionError
Exception Value:
'<class 'django.contrib.auth.models.User'>' does not have 'has_read_permission' or 'has_list_permission' defined.
Exception Location: 	/usr/local/lib/python3.4/site-packages/dry_rest_permissions/generics.py in has_permission, line 123
Python Executable: 	/usr/local/bin/python3.4
Python Version: 	3.4.4
Python Path:
['/home/mib/workspace/turnosya',
'/usr/local/lib/python34.zip',
'/usr/local/lib/python3.4',
'/usr/local/lib/python3.4/plat-openbsd5',
'/usr/local/lib/python3.4/lib-dynload',
'/usr/local/lib/python3.4/site-packages']
Thanks in advance!

Hi Mariano,
There are two ways I know of doing this -- one I have tried and one that I haven't.
There are usually extra fields and methods you want on a user model, so I usually make a new model (called user_profile) that has those extra fields and methods and then has a one to one relationship back to the default user model. Then I point my serializers at user_profile, which will have the permissions methods. This is the standard way to extend user, without rolling your own user model.
Another way you may be able to achieve this -- but I have not tried yet -- is by creating a proxy model for User. This will allow you to create additional methods and you should be able to point the serializer at that proxy model.
Let me know which one you try.

I usually create the proxy model for User. I've found it to help avoid a lot of headaches.
@mbaragiola you could also take a look at http://stackoverflow.com/questions/15526858/how-to-extend-a-class-in-python. That might let you extend the User class and add those permissions you're looking for.

@dbkaplan @abeniwal
Thank you for your quick replies.
I also use the extended model feature for adding an user profile. But I happend to make use of the User model for fields such as 'created_by' and 'last_modified_by' because it's easier to write them reading from 'request.user'.
I haven't heard about proxy models before, and I just tested it and works fine that way to add the permissions. I guess the problem is solved.
If you have further suggestions, I'm all ears. Thanks again!


Project Page - Deviation View - Process Data

Problem -

Project Budget / Cost is not processed, so deviation view gives all project, and at design time it shows Problem on Project
Requirement is Just show Project which have deviation
End user will try to narrow down count on this View
Owners can see Problem Project and Take action Accordingly

Solution -

Show Projects that have problem
Deviation meaning is -
a. Project which are over Budget, that comes from Timesheet filled vs allowed Budget
b. Project which are over time, ie(NSIP is larger than allowed time on Service Page)
Budget and NSIP current standing should be calculated regularly on some frequency ie.(Weekly)

Technical details-

this is too much data to process on regular basis, ie(Pending Project count = 500 * All Accounting Companies 70) on single Server
We might create new system that process this on which timesheet is updated,
To stop frequent Updating, system cloud wait for 2 hour, if no timesheet is filled in last 2 hours then Update deviation metric on Project on which last timesheet is filled
this would prevent schedule base update deviation metric
NSIP should also need to be updated regularly,
NSIP must be done on schedule basis, because of no user related trigger to calculate days

Initially reported by - @vinpahilwani

Due date related deviation is not covered in this View, just Budget and Time span

On Deviation page

can we display action button to change the contract? and change the invoice which directly takes to invoice page?

On project lisg page

So will you be able to display deviation signs on project list as well - where all projects gets displayed?
clicking icon can we open side panle to show reasons of deviation

Rest all things looks fine we can proceed


Fixed wrong git clone and small markdown bug

Was cloning the v2 sample.

Hi @danieldobalian, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (dadobali). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@danieldobalian : Thanks for your contribution to the Azure documentation! The author, @brandwe, has been notified to review your proposed change.

#sign-off


Add support for Python 3.8

Should rebase after https://github.com/poliastro/poliastro/pull/785 is merged.

Blocked until SciPy releases Python 3.8 wheels.

Next step: numba/llvmlite, see https://github.com/numba/llvmlite/issues/527.


[Messaging > ErrorResponse] Method withDefaultHeader > securityToken

Since the current implementation of the ErrorResponse class dynamically builds the JWT-token with the default value "rejected!" within the withDefaultHeader Method, the receiving Connector/IDS-Framework of the RejectionMessage in turn fails the filter-check of the DapsVerifier class. Thus, the DAT cannot be checked at the receiver of such a RejectionsMessage.

Currently placed on hold for security reasons. (contact bilaterally for details)

The DAT is not sent, as of now, when RejectionMessages are sent automatically via the IDS-Framework. This issue will be addressed in the context of the Unified-Lib project with extended DAT validation-routines.


140 issues on fresh clone

On a fresh clone and npm install I am seeing the following output after npm start
[at-loader] Checking finished with 140 errors
All of the errors are apparently @types/lodash. I have another previously cloned copy of this project with changes working fine without these errors. Screenshot of part of the console below:

What could be going wrong? Do I have the wrong version of something globally?

No, you are not. Count to 5 and fresh clone again.

Okay, I just re-cloned and am seeing the same issue. Is there a reason you believe I'm not seeing these errors?

you didn't count to 5!
Try again. There was some params on tsconfig that are quite aggresive.

@Foxandxss I was confused for a second! lol.
Sadly, the config updates doesn't seem to have gotten rid of the errors for me. It's almost like I have wrong versions of something installed globally

for the sake of trying, could you bump typescript to 2.1.5?

Thank you for your speedy responses. Seems to have fixed it!
[at-loader] Checking started in a separate process...
[at-loader] Ok, 2.01 sec.

Will bumping this to 2.1.x cause any other issues? I saw in another issue that you said there are some incompatibilities between Angular and 2.1.x

Yes, AOT + TS2.1 is a no-no.
I just created a conversation around this issue at the angular slack.

Okay, cool. So should I not proceed with 2.1.5 and wait? Ignore those errors? I can't seem to find a previous commit that works on a fresh clone (even though my previous project is OK), and I'm confused about what is throwing those errors

@Foxandxss this appears to be a regression introduced upstream: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/13994
More discussion in another issue: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/14338
Running the command npm install<EMAIL_ADDRESS>immediately fixed all issues for me with a fresh clone of this project (using Typescript 2.0.10)
As someone else pointed out, it's a bummer that a small patch level semver issue causes this issue and requires TS 2.1 or to manually roll back to 4.14.50.
Maybe for now, it's worth locking<EMAIL_ADDRESS>in package.json

Did removing the tsconfig options help?  A shame that we can't use those to prohibit unused names. The console screen shot above seems to point to the lodash typings being too new (the 'no-no' 2.1) which I believe is a different issue than the compiler options.

No @GaryB432 tsconfig wasn't the issue here. It is<EMAIL_ADDRESS>causing the issue.
If you do a fresh clone, you have to manually roll back to<EMAIL_ADDRESS>to get the errors to stop.

I just really like those compiler options and if they stay removed from master here, even though not causing a problem, I'll just have to maintain my own branch which is a minor inconvenience that I have not had to take yet.

Yeah, I did wrong. Open a PR and rererevert it. Too many things erroring today

Just went ahead and added the tsconfig changes back into the PR I just opened. This PR also locks the @types/lodash version properly to avoid any errors. I will keep a close eye here and submit any additional PRs needed as changes happen upstream :)


dpkg build element

See original issue on GitLab
In GitLab by [Gitlab user @jonathanmaw] on Jun 6, 2017, 13:47
The specification (from Tristan) is:
This should be a regular BuildElement derived element which will
consist of a yaml file and a little bit of additional code.
The yaml will define how to build and install the software into
the %{install-root} directory, using the debian/rules API, it assumes
that the staged Source in question is a module that contains
a debian subdirectory.
The python BuildElement derived class will additionally have to
inspect some of the build results and populate the split-rules
public data so that another dpkg deployment element will know the
correct file manifests for the packages it creates.
This should come with a separate test case added to the .gitlab-ci.yml

In GitLab by [Gitlab user @tristanvb] on Jul 27, 2017, 16:13
assigned to [Gitlab user @jonathanmaw]

In GitLab by [Gitlab user @tristanvb] on Jul 27, 2017, 16:14
Can we close this ?

In GitLab by [Gitlab user @jonathanmaw] on Jul 27, 2017, 16:33
I'm currently waiting on https://gitlab.com/BuildStream/buildstream-tests/merge_requests/11 being merged, which itself is pending a CI run (because last time it was run there was a problem with buildstream stopping the test from working correctly).

In GitLab by [Gitlab user @tristanvb] on Sep 17, 2017, 03:13
So, can we now close this ?

In GitLab by [Gitlab user @jonathanmaw] on Sep 18, 2017, 15:08
Yes, we can :)

In GitLab by [Gitlab user @jonathanmaw] on Sep 18, 2017, 15:08
closed


Reference BPA output in Advanced Scripting

Is it possible to reference the BPA output (rules which have been broken) via Advanced Scripting? For example, the ability to loop through the rules and extract all the objects which violate each rule.

I think the best way to do this would be to use the -Analyze parameter of TE via command line.
Tabular Editor Command Line Options
That generates an output that looks something like this:

Tabular Editor 2.16.0 (build 2.16.7781.40242)
--------------------------------
Loading model...
Running Best Practice Analyzer...
=================================
Column 'Athena Access'[RoleId] violates rule "Provide format string for visible numeric columns"
Column 'Athena Access'[GroupId] violates rule "Provide format string for visible numeric columns"
Column 'Athena Access'[WWID] violates rule "Provide format string for visible numeric columns"
Column 'HANA Security Table'[Finance Entity] violates rule "Provide format string for visible numeric columns"
Column 'Audit Table'[Access Rank] violates rule "Provide format string for visible numeric columns"

From there you could read that in via an Advanced script doing something like this:
// Read a text file line by line.

string[] lines = System.IO.File.ReadAllLines(@"C:\Users\alwortma\Downloads\BPAOutput.txt");
var bpaoutput = "";
foreach (string line in lines){
    bpaoutput += line + System.Environment.NewLine;
}

Output(bpaoutput);

Not sure what your exact workflow looks like for this, but that should be a start.

Interesting, thanks. Was curious if there is a way to do this without using the command line option.

There's a better way. You can run a Best Practice Analysis through a script. The following script produces a list of AnalyzerResult objects. Each AnalyzerResult specifies a TOM object in violation of a specific rule:
using TabularEditor.BestPracticeAnalyzer;

var bpa = new Analyzer();
bpa.SetModel(Model);

var results = bpa.AnalyzeAll().ToList(); // List<AnalyzerResult>

Info("BPA violations: " + results.Count.ToString());
Info("Violation 1, rule: " + results[0].RuleName + ", object: " + results[0].ObjectName);
Output(results[0].Object);

This is precisely what I was looking for - thanks Daniel! Just one more thing - can we get the RuleCategory, Severity and other rule properties within this? I don't see these within the AnalyzerResult class.
Thank you!

These exist as properties on the Rule property (which is of type BestPracticeRule):
Info(results[0].Rule.Category);

Perfect! Thanks so much!

Thanks for all the knowledge drops @otykier !! Helpful as always 👍

@otykier can we run the bpa inside of tabular editor (not using the command line) against a .bim file (not against the model loaded into tabular editor)?

@m-kovalsky technically, yes. You could always do something like
var process = Process.Start("tabulareditor.exe model.bim -A > output.txt");
process.WaitForExit();

and then parse the output file in the script.
If you could add a few more words on what you need this for, maybe we can come up with a better solution?

I'd like to have a script/program which can run the BPA against a folder of .bim files (or pbip files) and save the output into a file.

I see. Well, the following should work, at least in TE2:
using TabularEditor.BestPracticeAnalyzer;
var bpa = new Analyzer();

var model = new TabularModelHandler(@"C:\Users\DanielOtykier\Desktop\model.bim").Model;
bpa.SetModel(model);
var results = bpa.AnalyzeAll().ToList(); // List<AnalyzerResult>

Here, I've hardcoded the path of the model to load, so you'd have to put it into a loop, iterating the model.bim, database.json or model.tmd files you'd want to analyze. How you want the result to be outputted is also up to you.

Ah, TabularModelHandler is the key. Thanks Daniel!

Is it possible to run the command line to run a command line to run a c# script without referencing a .bim file or server/database? Just want the script to run against tabular editor (without the program opening).

No, you would have to create a minimal/empty model.bim file to use in the CLI, as a workaround.

Ah, ok. Thanks Daniel

Has something changed in the analyzer output? This script doesn't work anymore (object, category, severity)
using TabularEditor.BestPracticeAnalyzer;

var bpa = new Analyzer();
bpa.SetModel(Model);

var results = bpa.AnalyzeAll().ToList(); // List<AnalyzerResult>

Info("BPA violations: " + results.Count.ToString());
Info("Violation 1, rule: " + results[0].RuleName + ", object: " + results[0].ObjectName);
Output(results[0].Object);

It seems a bug was introduced after we changed this property to be init-only (which is a relatively new C# language feature).
Could you use Output(results[0].ObjectName]); for the last line of your script, as a workaround for now?

Thank Daniel, the code below works. However, it seems that something has changed with category and severity. It used to be Rule.Category & Rule.Severity but that code doesn't work anymore.
using TabularEditor.BestPracticeAnalyzer;

var bpa = new Analyzer();
bpa.SetModel(Model);

var results = bpa.AnalyzeAll().ToList(); // List<AnalyzerResult>

Info("BPA violations: " + results.Count.ToString());
Info("Violation 1, rule: " + results[0].RuleName + ", object: " + results[0].ObjectName);
Output(results[0].ObjectName);

Apologies for the delay in getting back to this. However, the issue was fixed a while ago, and your original script should now work fine.

Thanks Daniel!


Site support request: Collab.inc video list (vl.collab.inc)

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a new site support request
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that none of provided URLs violate any copyrights or contain any DRM to the best of my knowledge
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and am willing to share it if required

Region
United States
Example URLs

Single video: https://vl.collab.inc/videos/553891

Provide a description that is worded well enough to be understood
After examining the site in devtools, the video ID after /videos/ in the URL can be used in a GET request to https://dashboard.collab.inc/api/public_video_library/<VIDEO_ID_HERE> with what looks like no custom headers. This GET request returns some JSON, which includes a hls_stream key which points to a watermarked m3u8 video. The m3u8 links look like this: https://collab-media-assets.s3-us-west-2.amazonaws.com/watermarked_hls/3fefae2f-3d21-4a6b-bb45-3899023ce0cb/5548610291_collab_clips_mpugc_getting_ducks_out_of_garage.m3u8. Getting the un-watermarked hls stream link is simple: Replace watermarked_hls with hls in the URL so that the link reads as follows: https://collab-media-assets.s3-us-west-2.amazonaws.com/hls/3fefae2f-3d21-4a6b-bb45-3899023ce0cb/5548610291_collab_clips_mpugc_getting_ducks_out_of_garage.m3u8. Then, simply download the hls stream (like yt-dlp has been doing for millenia) and the video has been downloaded!
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://vl.collab.inc/videos/553891']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [12b248ce6] (zip)
[debug] Python 3.10.1 (CPython arm64 64bit) - macOS-14.5-arm64-arm-64bit (OpenSSL 1.1.1l  24 Aug 2021)
[debug] exe versions: ffmpeg 7.0.1 (setts), ffprobe 7.0.1, phantomjs 2.1.1, rtmpdump 2.4
[debug] Optional libraries: certifi-2024.02.02, mutagen-1.47.0, sqlite3-3.35.5
[debug] Proxy map: {}
[debug] Request Handlers: urllib
[debug] Loaded 1820 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp)
[generic] Extracting URL: https://vl.collab.inc/videos/553891
[generic] 553891: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] 553891: Extracting information
[debug] Looking for embeds
ERROR: Unsupported URL: https://vl.collab.inc/videos/553891
Traceback (most recent call last):
  File "/usr/local/bin/yt-dlp/yt_dlp/YoutubeDL.py", line 1606, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/bin/yt-dlp/yt_dlp/YoutubeDL.py", line 1741, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/common.py", line 734, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/yt-dlp/yt_dlp/extractor/generic.py", line 2514, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://vl.collab.inc/videos/553891

I would implement it myself but I'm more of a javascript guy.


Code from ADT section of documentation not compiling

On this page you have the following code snippet:
implicit val decodeEvent: Decoder[Event] =
    List[Decoder[Event]](
      Decoder[Foo].widen,
      Decoder[Bar].widen,
      Decoder[Baz].widen,
      Decoder[Qux].widen
    ).reduceLeft(_ or _)

as far as I can tell it only compiles with the below changes:
implicit val decodeEvent: Decoder[Event] =
    List[Decoder[Event]](
      Decoder[Foo.type].widen,
      Decoder[Bar.type].widen,
      Decoder[Baz.type].widen,
      Decoder[Qux.type].widen
    ).reduceLeft(_ or _)

Can you provide a complete example showing the failure you saw? The version on the page is correct and adding .type should not even compile.
The following should compile on all recent circe versions:
sealed trait Event

case class Foo(i: Int) extends Event
case class Bar(s: String) extends Event
case class Baz(c: Char) extends Event
case class Qux(values: List[String]) extends Event

import cats.syntax.functor._
import io.circe.{ Decoder, Encoder }, io.circe.generic.auto._
import io.circe.syntax._

object GenericDerivation {
  implicit val encodeEvent: Encoder[Event] = Encoder.instance {
    case foo @ Foo(_) => foo.asJson
    case bar @ Bar(_) => bar.asJson
    case baz @ Baz(_) => baz.asJson
    case qux @ Qux(_) => qux.asJson
  }

  implicit val decodeEvent: Decoder[Event] =
    List[Decoder[Event]](
      Decoder[Foo].widen,
      Decoder[Bar].widen,
      Decoder[Baz].widen,
      Decoder[Qux].widen
    ).reduceLeft(_ or _)
}

Sure
My master branch currently does what I expect it to while using the Decoder[Foo.type].widen version of ADT decoding, and it does not compile when I try to remove the .type part.
For reference, the code I ended up with is based on a stackoverflow discussion from a while ago.

@TomPoczos Right, case objects only have singleton types, but since the doc example uses case classes I don't think this is really a matter for the issue tracker, no?

You are of course right, thanks for your explanation. Since I didn't figure out what makes the difference between my code and what's in the documentation, I wanted to make sure this doesn't potentially slow down others just getting familiar with Circe and Scala, in case the issue was with the documentation. Turns out it's just me having to learn more about the language.
I think this can be closed, thanks for your time.


Migrate blueprints/data-solutions/vertex-mlops to google_workbench_instance

│ Warning: Deprecated Resource
│
│   with module.test.google_notebooks_instance.playground,
│   on [...]/cloud-foundation-fabric/blueprints/data-solutions/vertex-mlops/vertex.tf line 82, in resource "google_notebooks_instance" "playground":
│   82: resource "google_notebooks_instance" "playground" {
│
│ `google_notebook_instance` is deprecated and will be removed in a future major release. Use `google_workbench_instance` instead.
│
│ (and one more similar warning elsewhere)

@wiktorn shall we

keep this open and find someone to work on it?
deprecated and remove the blueprint?

I would prefer not to keep this issue open indefinitely, WDYT?

The same change need to be done in the Data-playground blueprint.
gioconte did a PR (to be finalized).
gioconte, can you work on fixing the 2 blueprints?

@gioconte , any comment?


Dependabot security alert for PY

Objective of issue: Fix Dependabot alert

Lava-DNF version:

[x] 0.1.0 (current version)

Lava version:

[x] 0.4.0 (current version)

I'm submitting a ...

[X] bug report

Current behavior:

Dependabot alerts that the py dependencies has a vulnerability.

Expected behavior:

Dependabot does not alert that any dependencies have vulnerabilities.

Steps to reproduce:

Review Dependabot issues.

Related code:

insert short code snippets here

Other information:

insert the output from lava debug here

Resolved with Pull request #48


feat(testing): Initial tests

I've written tests similar to Old-School Essentials here, utilizing the Quench module. (https://github.com/Ethaks/FVTT-Quench).
If this type of testing is relevant, I'd gladly spend more time writing tests for Shadowdark too.
Added tests for Actor documents, and Item documents.

Thanks a lot for this, it's looking really good.  There's a couple of things I'd like you to do before I merge it though.

Can you add /* eslint-disable no-unused-expressions */ to the top of each actual test file?  eslint doesn't like the way Mocha/Chai does some things, and I'd rather not disable it globally.
You have a typo in the Gem test (free_cary instead of free_carry).

Again, thanks for this.  :)


Try command

Can 'try' command be supported by jit?

thanks for your question @sergiysavelyev . Yes there is support for try. The details of what syntax is supported can be found in the documentation here
For the future, if you have a question, Gitter or Discource are a better place to ask (in this case of a simple question Gitter is best). That way you get a faster response from the community as there are more eyes there. Issues are more adequate for bugs/feature requests/etc.