RB package - code overlap?

In reviewing recent updates to the RB tutorial on develop, I noticed there appears to be some code duplication between rbresults.py and rbobjs.py. rbobjs contains the RBResults object, which is also present in rbresults. Given the commit history, I'm assuming rbobjs is meant to supercede rbresults. (rbresults was last worked on in commit 9689a748dd8 on 10/6, while robjs came into existence as part of the refactor in commit 025bf1b8a704f on 10/10.)
If this is indeed the case, I would propose we delete rbresults.

Yes, rbresults.py should have been removed as it was replaced by rbobjs.py  -- now it is.


AutoUic subprocess error

[ 33%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/Flipper.cpp.o
[ 33%] Building C object third-party/JCQP/CMakeFiles/JCQP.dir/amd/src/amd_control.c.o
[ 33%] Building CXX object third-party/ParamHandler/CMakeFiles/dynacore_yaml-cpp.dir/src/stream.cpp.o
[ 33%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/Indexlist.cpp.o
[ 33%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/LAPACKReplacement.cpp.o
[ 34%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/Matrices.cpp.o
[ 34%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/MessageHandling.cpp.o
[ 35%] Building CXX object third-party/ParamHandler/CMakeFiles/dynacore_yaml-cpp.dir/src/tag.cpp.o
[ 35%] Building CXX object third-party/lord_imu/CMakeFiles/test_imu.dir/test/lord_test.cpp.o
[ 35%] Building CXX object third-party/ParamHandler/CMakeFiles/dynacore_yaml-cpp.dir/src/contrib/graphbuilder.cpp.o
[ 35%] Building CXX object third-party/ParamHandler/CMakeFiles/dynacore_yaml-cpp.dir/src/contrib/graphbuilderadapter.cpp.o
[ 35%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/OQPinterface.cpp.o
[ 35%] Linking CXX shared library libdynacore_yaml-cpp.so
[ 36%] Linking CXX executable test_imu
[ 36%] Built target test_imu
[ 36%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/Options.cpp.o
[ 36%] Built target dynacore_yaml-cpp
[ 37%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/QProblem.cpp.o
[ 37%] Building CXX object googletest-build/googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.o
[ 37%] Building C object third-party/JCQP/CMakeFiles/JCQP.dir/amd/src/amd_defaults.c.o
[ 37%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/QProblemB.cpp.o
[ 38%] Building C object third-party/JCQP/CMakeFiles/JCQP.dir/amd/src/amd_info.c.o
[ 39%] Building CXX object user/MIT_Controller/Controllers/WBC/WBIC/CMakeFiles/WBIC.dir/KinWBC.cpp.o
[ 39%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/SQProblem.cpp.o
[ 40%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/SQProblemSchur.cpp.o
[ 40%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/SolutionAnalysis.cpp.o
[ 40%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/SparseSolver.cpp.o
[ 40%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/SubjectTo.cpp.o
[ 41%] Building CXX object third-party/qpOASES/CMakeFiles/qpOASES.dir/src/Utils.cpp.o
[ 41%] Linking CXX shared library libs/libqpOASES.so
[ 41%] Built target qpOASES
[ 41%] Building CXX object user/MIT_Controller/Controllers/WBC/WBIC/CMakeFiles/WBIC.dir/WBIC.cpp.o
[ 41%] Building C object third-party/JCQP/CMakeFiles/JCQP.dir/amd/src/amd_order.c.o
[ 41%] Building C object third-party/JCQP/CMakeFiles/JCQP.dir/amd/src/amd_post_tree.c.o
[ 42%] Building C object third-party/JCQP/CMakeFiles/JCQP.dir/amd/src/amd_postorder.c.o
[ 42%] Building C object third-party/JCQP/CMakeFiles/JCQP.dir/amd/src/amd_preprocess.c.o
[ 42%] Building C object third-party/JCQP/CMakeFiles/JCQP.dir/amd/src/amd_valid.c.o
[ 42%] Building C object third-party/JCQP/CMakeFiles/JCQP.dir/amd/src/SuiteSparse_config.c.o
[ 43%] Linking CXX shared library libJCQP.so
[ 43%] Built target JCQP
[ 43%] Building CXX object third-party/ParamHandler/CMakeFiles/dynacore_param_handler.dir/ParamHandler.cpp.o
[ 44%] Linking CXX shared library libdynacore_param_handler.so
[ 44%] Built target dynacore_param_handler
[ 44%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/auxil.c.o
[ 44%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/cs.c.o
[ 45%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/ctrlc.c.o
[ 45%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/kkt.c.o
[ 46%] Linking CXX static library ../../lib/libgtest.a
[ 46%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/lin_alg.c.o
[ 46%] Built target gtest
[ 46%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/lin_sys.c.o
[ 47%] Building C object third-party/osqp/CMakeFiles/osqp_demo.dir/examples/osqp_demo.c.o
[ 47%] Linking C executable out/osqp_demo
[ 48%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/osqp.c.o
[ 48%] Built target osqp_demo
[ 48%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/polish.c.o
[ 48%] Building C object third-party/osqp/lin_sys/direct/qdldl/qdldl_sources/CMakeFiles/qdldl_example.dir/examples/c/example.c.o
[ 49%] Linking C executable out/qdldl_example
[ 49%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/proj.c.o
[ 49%] Built target qdldl_example
[ 50%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/scaling.c.o
[ 50%] Building CXX object googletest-build/googlemock/CMakeFiles/gmock.dir/src/gmock-all.cc.o
[ 50%] Building C object third-party/osqp/CMakeFiles/osqp.dir/src/util.c.o
[ 50%] Building C object third-party/osqp/CMakeFiles/osqp.dir/lin_sys/lib_handler.c.o
[ 50%] Linking C shared library out/libosqp.so
[ 50%] Built target osqp
[ 50%] Building CXX object googletest-build/googletest/CMakeFiles/gtest_main.dir/src/gtest_main.cc.o
[ 50%] Linking CXX static library ../../lib/libgtest_main.a
[ 50%] Built target gtest_main
[ 50%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Collision/CollisionBox.cpp.o
[ 51%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Collision/CollisionMesh.cpp.o
[ 52%] Linking CXX static library ../../lib/libgmock.a
[ 52%] Built target gmock
[ 52%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Collision/CollisionPlane.cpp.o
[ 52%] Building CXX object googletest-build/googlemock/CMakeFiles/gmock_main.dir/src/gmock_main.cc.o
[ 52%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Collision/ContactConstraint.cpp.o
[ 53%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Collision/ContactImpulse.cpp.o
[ 53%] Linking CXX static library ../../lib/libgmock_main.a
[ 53%] Built target gmock_main
[ 53%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Collision/ContactSpringDamper.cpp.o
[ 53%] Building CXX object common/CMakeFiles/biomimetics.dir/src/ControlParameters/ControlParameterInterface.cpp.o
[ 53%] Building CXX object common/CMakeFiles/biomimetics.dir/src/ControlParameters/ControlParameters.cpp.o
[ 54%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Controllers/ContactEstimator.cpp.o
[ 54%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Controllers/DesiredStateCommand.cpp.o
[ 54%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Controllers/FootSwingTrajectory.cpp.o
[ 55%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Controllers/GaitScheduler.cpp.o
[ 55%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Controllers/LegController.cpp.o
[ 55%] Linking CXX shared library libWBIC.so
[ 55%] Built target WBIC
[ 55%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Controllers/OrientationEstimator.cpp.o
[ 55%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Controllers/PositionVelocityEstimator.cpp.o
[ 56%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Dynamics/DynamicsSimulator.cpp.o
[ 56%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Dynamics/FloatingBaseModel.cpp.o
[ 56%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Dynamics/Quadruped.cpp.o
[ 57%] Building CXX object common/CMakeFiles/biomimetics.dir/src/SimUtilities/ImuSimulator.cpp.o
[ 57%] Building CXX object common/CMakeFiles/biomimetics.dir/src/SimUtilities/SpineBoard.cpp.o
[ 57%] Building CXX object common/CMakeFiles/biomimetics.dir/src/SimUtilities/ti_boardcontrol.cpp.o
[ 57%] Building CXX object common/CMakeFiles/biomimetics.dir/src/SparseCMPC/OsqpTriples.cpp.o
[ 58%] Building CXX object common/CMakeFiles/biomimetics.dir/src/SparseCMPC/SparseCMPC.cpp.o
[ 58%] Building CXX object common/CMakeFiles/biomimetics.dir/src/SparseCMPC/SparseCMPC_Math.cpp.o
[ 58%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Utilities/PeriodicTask.cpp.o
[ 59%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Utilities/SegfaultHandler.cpp.o
[ 59%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Utilities/Utilities_print.cpp.o
[ 59%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Utilities/filters.cpp.o
[ 59%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Utilities/save_file.cpp.o
[ 60%] Building CXX object common/CMakeFiles/biomimetics.dir/src/Utilities/utilities.cpp.o
[ 60%] Linking CXX shared library libbiomimetics.so
[ 60%] Built target biomimetics
[ 61%] Automatic MOC and UIC for target sim
[ 62%] Building CXX object common/FootstepPlanner/CMakeFiles/footstep_planner.dir/GraphSearch.cpp.o
AutoUic subprocess error
The uic process failed to compile
"SRC:/sim/src/SimControlPanel.ui"
into
"SRC:/mc-build/sim/sim_autogen/include/ui_SimControlPanel.h"
included by
"SRC:/sim/src/SimControlPanel.cpp"
Command
/opt/Qt5.10.0/5.10.0/gcc_64/bin/uic -o /media/ray/work/Github/Cheetah-Software/mc-build/sim/sim_autogen/include/ui_SimControlPanel.h /media/ray/work/Github/Cheetah-Software/sim/src/SimControlPanel.ui
Output
/opt/Qt5.10.0/5.10.0/gcc_64/bin/uic: relocation error: /opt/Qt5.10.0/5.10.0/gcc_64/bin/uic: symbol _ZdlPvm, version Qt_5 not defined in file libQt5Core.so.5 with link time reference
AutoUic subprocess error
The uic process failed to compile
"SRC:/sim/src/JoystickTest.ui"
into
"SRC:/mc-build/sim/sim_autogen/include/ui_JoystickTest.h"
included by
"SRC:/sim/src/JoystickTest.cpp"
Command
/opt/Qt5.10.0/5.10.0/gcc_64/bin/uic -o /media/ray/work/Github/Cheetah-Software/mc-build/sim/sim_autogen/include/ui_JoystickTest.h /media/ray/work/Github/Cheetah-Software/sim/src/JoystickTest.ui
Output
/opt/Qt5.10.0/5.10.0/gcc_64/bin/uic: relocation error: /opt/Qt5.10.0/5.10.0/gcc_64/bin/uic: symbol _ZdlPvm, version Qt_5 not defined in file libQt5Core.so.5 with link time reference
[ 62%] Building CXX object common/CMakeFiles/test-common.dir/test/test_ControlParameters.cpp.o
[ 62%] Building CXX object robot/CMakeFiles/robot.dir/src/HardwareBridge.cpp.o
AutoUic subprocess error
The uic process failed to compile
"SRC:/sim/src/MiniCheetahDebug.ui"
into
"SRC:/mc-build/sim/sim_autogen/include/ui_MiniCheetahDebug.h"
included by
"SRC:/sim/src/MiniCheetahDebug.cpp"
Command
/opt/Qt5.10.0/5.10.0/gcc_64/bin/uic -o /media/ray/work/Github/Cheetah-Software/mc-build/sim/sim_autogen/include/ui_MiniCheetahDebug.h /media/ray/work/Github/Cheetah-Software/sim/src/MiniCheetahDebug.ui
Output
/opt/Qt5.10.0/5.10.0/gcc_64/bin/uic: relocation error: /opt/Qt5.10.0/5.10.0/gcc_64/bin/uic: symbol _ZdlPvm, version Qt_5 not defined in file libQt5Core.so.5 with link time reference
sim/CMakeFiles/sim_autogen.dir/build.make:60: recipe for target 'sim/CMakeFiles/sim_autogen' failed
make[2]: *** [sim/CMakeFiles/sim_autogen] Error 1
CMakeFiles/Makefile2:2410: recipe for target 'sim/CMakeFiles/sim_autogen.dir/all' failed
make[1]: *** [sim/CMakeFiles/sim_autogen.dir/all] Error 2
make[1]: *** 正在等待未完成的任务....
[ 62%] Building CXX object robot/CMakeFiles/robot.dir/src/JPosInitializer.cpp.o
[ 62%] Linking CXX shared library libfootstep_planner.so
[ 62%] Built target footstep_planner
[ 63%] Building CXX object robot/CMakeFiles/robot.dir/src/RobotRunner.cpp.o
[ 64%] Building CXX object common/CMakeFiles/test-common.dir/test/test_ImuSimulator.cpp.o
[ 64%] Building CXX object robot/CMakeFiles/robot.dir/src/SimulationBridge.cpp.o
[ 64%] Building CXX object common/CMakeFiles/test-common.dir/test/test_JCQP.cpp.o
[ 64%] Building CXX object common/CMakeFiles/test-common.dir/test/test_LegController.cpp.o
[ 64%] Building CXX object robot/CMakeFiles/robot.dir/src/main_helper.cpp.o
[ 64%] Building CXX object robot/CMakeFiles/robot.dir/src/rt/rt_ethercat.cpp.o
[ 64%] Building CXX object common/CMakeFiles/test-common.dir/test/test_actuatorModel.cpp.o
[ 65%] Building CXX object robot/CMakeFiles/robot.dir/src/rt/rt_rc_interface.cpp.o
[ 66%] Building CXX object common/CMakeFiles/test-common.dir/test/test_casadi.cpp.o
[ 66%] Building CXX object robot/CMakeFiles/robot.dir/src/rt/rt_sbus.cpp.o
[ 66%] Building CXX object common/CMakeFiles/test-common.dir/test/test_cheetah3_model.cpp.o
[ 66%] Building CXX object robot/CMakeFiles/robot.dir/src/rt/rt_serial.cpp.o
[ 67%] Building CXX object robot/CMakeFiles/robot.dir/src/rt/rt_spi.cpp.o
[ 67%] Building CXX object robot/CMakeFiles/robot.dir/src/rt/rt_vectornav.cpp.o
[ 67%] Building CXX object common/CMakeFiles/test-common.dir/test/test_dynamics.cpp.o
[ 67%] Linking CXX shared library librobot.so
[ 67%] Built target robot
[ 68%] Building CXX object common/CMakeFiles/test-common.dir/test/test_filters.cpp.o
[ 68%] Building CXX object common/CMakeFiles/test-common.dir/test/test_footswing.cpp.o
[ 68%] Building CXX object common/CMakeFiles/test-common.dir/test/test_goldfarb.cpp.o
[ 68%] Building CXX object common/CMakeFiles/test-common.dir/test/test_math.cpp.o
[ 69%] Building CXX object common/CMakeFiles/test-common.dir/test/test_mini_cheetah_model.cpp.o
[ 69%] Building CXX object common/CMakeFiles/test-common.dir/test/test_orientation_tools.cpp.o
[ 69%] Building CXX object common/CMakeFiles/test-common.dir/test/test_osqp.cpp.o
[ 70%] Building CXX object common/CMakeFiles/test-common.dir/test/test_periodic_tasks.cpp.o
[ 70%] Building CXX object common/CMakeFiles/test-common.dir/test/test_sharedMemory.cpp.o
[ 70%] Building CXX object common/CMakeFiles/test-common.dir/test/test_spatial.cpp.o
[ 70%] Building CXX object common/CMakeFiles/test-common.dir/test/test_utilities.cpp.o
[ 71%] Building CXX object common/CMakeFiles/test-common.dir/test/test_yaml.cpp.o
[ 71%] Linking CXX executable test-common
[ 71%] Built target test-common
Makefile:132: recipe for target 'all' failed
make: *** [all] Error 2

Hi, how did you solve this problem?


Soundboard is showing under mixer instead of next to it

Using the soundboard module with the game system "Das Schwarze Auge" (German; the english version ic called "the dark eye"), the soundbord is not showing next to the mixer as intended but under it instead:

It makes it much more difficult to handle it.
Maybe there is an easy fix possilbe in the css?
Would appreciate it very much.
Thx in advance!

At first glance I think it's because the system changes the core Foundry styling for common elements. This probably makes either the mixer or soundboard section too wide. I remember I was having some difficulties with it, but I should probably have it automatically set the width of the soundscape window instead of hardcoding it. I'll see what I can do.

The problem was fixed in the css of the game system! 😉


Extract Hermite-y stuff into a module

Codecov Report

Merging #13 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #13   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      4    +1
  Lines         229    252   +23
=====================================
+ Hits          229    252   +23

Impacted Files
Coverage Δ

src/tests.rs
100% <ø> (ø)
:arrow_up:

src/lib.rs
100% <ø> (ø)
:arrow_up:

src/hermite.rs
100% <100%> (ø)

Continue to review full report at Codecov.

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

Ah yes, I need to add tests for the nascent acceleration stuff. Incoming!


Update dashboard search styles

Use typeahead from design system and replace the custom one in the dashboard.
https://www.figma.com/file/bMhG3KyrJF8vIAODgmbeqT/Design-System?node-id=1533%3A260040

This is updated in feature/4960-dashboard-header (#6434)
No new functionality, just regression testing on search in dashboard my stories

Horizontal scroll not appearing:

Was on PC/Chrome 88.0.4324.190

I"m having a heck of a time reproducing this bug, Claudio. Can you try again? Is it not scrolling or is that a horizontal scrollbar doesn't appear?
It doesn't show a scrollbar horizontally, it should just scroll when you scroll.

Verified in QA


Include conv layers with same padding from MUGEN

Summary:
Ported SamePadConv3D layers from MUGEN codebase, with small changes for mypy and an added rule to ignore for flake8.
Test plan:
pytest -vv

Codecov Report

Merging #56 (b6a5ba7) into main (1a07ed1) will decrease coverage by 0.34%.
The diff coverage is 25.00%.

:exclamation: Current head b6a5ba7 differs from pull request most recent head 31b2d5c. Consider uploading reports for the commit 31b2d5c to get more accurate results

@@            Coverage Diff             @@
##             main      #56      +/-   ##
==========================================
- Coverage   88.40%   88.06%   -0.35%
==========================================
  Files          30       30
  Lines        1484     1491       +7
==========================================
+ Hits         1312     1313       +1
- Misses        172      178       +6

Impacted Files
Coverage Δ

torchmultimodal/utils/common.py
63.63% <25.00%> (-9.34%)
:arrow_down:

Continue to review full report at Codecov.

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

How about matching MUGEN when kernel = 3 ,stride = 2?
https://github.com/mugen-org/MUGEN_baseline/blob/main/lib/models/video_vqvae/vqvae.py#L344


Updated to MM4 but SSL not working

Trying to run a simple middleman init which works fine, until I get the following error:
Could not load OpenSSL. You must recompile Ruby with OpenSSL support or change the sources in your Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using RVM are available at rvm.io/packages/openssl.
I'm aware it may be $PATH related but I don't know how to change that. When I run which openssl I get /usr/bin/openssl
So what I think I need to do is update my openssl version, somehow, someway which will then allow me to perform a successful middleman init and bundle install afterwards.
Where should I start? Any help would be amazing :) thanks.

This appears to be an RVM-related issue, and not MM’s. I would start by upgrading RVM to the latest version and reinstalling Ruby afterwards. Newer RVM versions should be smart enough to detect the installation of OpenSSL (or the lack of).

No luck. I ran rvm get stable which, after execution, showed the following via rvm version:
rvm 1.29.0 (latest) by Michal Papis, Piotr Kuczynski, Wayne E. Seguin [https://rvm.io/]
Then, I ran rvm install 2.4.0 which ensures I was running the latest version of Ruby.
But I'm still seeing the OpenSSL issue.

Does ruby -v also say that you are indeed using the newly installed version?

Yep. Check it out:  https://imgur.com/a/wQwTe

What about which middleman and middleman version? I’m just throwing out things I would check.

Last login: Tue Feb 14 10:23:37 on ttys000
Beaus-MacBook-Pro:~ beau$ which middleman
/Users/beau/.rvm/rubies/ruby-2.4.0/bin/middleman
Beaus-MacBook-Pro:~ beau$ middleman version
Middleman 4.2.1
Beaus-MacBook-Pro:~ beau$

Can you try this command?
rvm osx-ssl-certs update all

It fixed an OpenSSL issue for me in the past (but with a different error message).

The command seemed to work, but the error persists. FWIW here's how I'm generating the error, while trying to get middleman into a folder:
Beaus-MacBook-Pro:untitled folder beau$ middleman init
         run  git clone --depth 1 https://github.com/middleman/middleman-templates-default.git /var/folders/_z/nr8vt7gs2r1g0hwlsvlnx72m0000gn/T/d20170214-44963-iusqrb from "."

The dependency wdm (~> 0.1.0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mswin32, x86-mingw32. To add those platforms to the bundle, run `bundle lock --add-platform x86-mswin32 x86-mingw32`.
The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mswin32, x86-mingw32, java. To add those platforms to the bundle, run `bundle lock --add-platform x86-mswin32 x86-mingw32 java`.
Could not load OpenSSL.
You must recompile Ruby with OpenSSL support or change the sources in your
Gemfile from 'https' to 'http'. Instructions for compiling with OpenSSL using
RVM are available at rvm.io/packages/openssl.
Beaus-MacBook-Pro:untitled folder beau$

I really appreciate all your help on this. Means a lot and is inching me closer to getting MM up and running so I can push a ton of updates to a site I run and manage :)

I’m out of ideas here. :-/ See if this post can help you: http://railsapps.github.io/openssl-certificate-verify-failed.html

:'( well I'm officially screwed hah. All good, thanks for all your help anyway :) I tried the link but still no resolve.

From what I can tell, you've essentially found the "conical" post for this specific issue -- if none of that works for you one options you could try would be to try changing the ruby gem source in the Gemfile to http:// to avoid using openssl. That said I would not suggest this, as you lose any protection from man-in-the middle, tracking, etc.
Every time I've had this issue personally, I've reinstalled the specific ruby verison via rvm and that has resolved it, but clearly YMMV.

On mac I usually also
brew install openssl
and force link this version
http://stackoverflow.com/questions/15185661/update-openssl-on-os-x-with-homebrew
You can give this a go maybe - what OSX you on?

Cool, I'll give it a shot. I'm on macOS Sierra(10.12.3)

P.S. I think we've come across one another before @iwarner...probably a while back now. Thanks for helping me out again :)

Sounds mysterious.
On sierra actually I did not need to do this openssl trick this time, but who knows
I also use Rbenv - just easier to control I think
/Users/ianwarner/.rbenv/shims/ruby
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin16]
/Users/ianwarner/.rbenv/shims/gem
gem 2.6.8

This whole thing is mysterious. It's doing my head in :(
Odd, my Ruby is way behind yours
Beaus-MacBook-Pro:test beau$ ruby -v
ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin16]

Yeah I always keep mine up to date.
Switch to Rbenv perhaps and install the stable version
# Variables
VERSION=2.3.1

# Header
header "RBENV Installation Script"

log "Continue (y/Y)"
read RBENV_CONTINE

if [[ $RBENV_CONTINE == y || $RBENV_CONTINE == Y ]] ; then

    subheader "Brew Update"
    brew update

    subheader "Install Rbenv, Rbenv Gem and Ruby Build"
    brew install rbenv ruby-build

    eval "$(rbenv init - --no-rehash)"

    # Install Ruby Version
    subheader "Install Ruby Version"

    CONFIGURE_OPTS="--disable-install-doc --with-readline-dir=$(brew --prefix readline)" rbenv install $VERSION

    rbenv global $VERSION
    rbenv rehash

    # Remove User Gems folder
    rm -r ~/.gem

fi

Cool. Official rbenv documentation is suggesting this as a way to update to a specific version:
rbenv install <version>
After running rbenv install -l it looks as though 2.4.0 is the latest. All good?

Indeed thats how I install outside the script - the script just helps with the initial added options.

Well this is confusing. I just did a fresh install of 2.4.0 but then a ruby -v returns
ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin16]
Full output as follows:
Beaus-MacBook-Pro:test beau$ rbenv install 2.4.0
ruby-build: use openssl from homebrew
Downloading ruby-2.4.0.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.4/ruby-2.4.0.tar.bz2
Installing ruby-2.4.0...
ruby-build: use readline from homebrew
Installed ruby-2.4.0 to /Users/beau/.rbenv/versions/2.4.0

Beaus-MacBook-Pro:test beau$ ruby -v
ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin16]

Yeah the universal means you are using the Ruby provided by the OS
do - echo $PATH and make sure homebrew is in the path and in the correct place.
Oherwise ammend your Path - maybe reinstall Homebrew also
see if this brings up anything
brew doctor

echo $PATH didn't reveal anything to do with Brew, oddly enough:
Beaus-MacBook-Pro:test beau$ echo $PATH
/Users/beau/.rvm/gems/ruby-2.4.0/bin:/Users/beau/.rvm/gems/ruby-2.4.0@global/bin:/Users/beau/.rvm/rubies/ruby-2.4.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/beau/.rvm/bin

Running brew doctor worked and suggested pruning, which is what I did:
Beaus-MacBook-Pro:test beau$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: Broken symlinks were found. Remove them with `brew prune`:
  /usr/local/bin/openssl
Beaus-MacBook-Pro:test beau$ brew prune
Pruned 1 symbolic links and 4 directories from /usr/local

So it looks as though Brew isn't even in the path...if that is a thing? Do you suggest completely removing and re-installing Brew?

Gotcha - if you are not familiar with Path manipulation then I would point you towards reading up on dotfiles.
It will also open a new world for you in terms of terminal usage - https://dotfiles.github.io/ - you probably dont have ZSH and auto complete etc... ??
Below is my entry in my .zshrc file - after reading above you will know what that means :)
Homebrew
PATH=/usr/local/sbin:
PATH=$PATH/usr/local/bin:
Default
PATH=$PATH/usr/bin:
PATH=$PATH/usr/sbin:
PATH=$PATH/bin:
PATH=$PATH/sbin:
Laravel
PATH=$PATH~/.composer/vendor/bin:
Android SDK Path - generic for Homebrew install - brew install android-sdk
PATH=$PATH/usr/local/opt/android-sdk
Export path
export path

On further looking at your path - /usr/local/bin - this is what homebrew needs.

Cool, I'll read up on the dotfiles. Looks like there's a lot of managers to choose from. Do you recommend one? Any no - I don't have ZSH or auto complete. I'm only a part time front-end developer on the side of my full time job as a UI/product manager. So I'm a bit of a rookie...yet somehow I've been able to roll with Middleman seemingly unscathed for the better of the last 3 or os years. All of a sudden I'm stuck eh!

P.S. I'm in Australia so will be heading off soon, but will post back with how I go in the morning and when your back in action in London town we can go from there. Thanks again for your help. I really appreciate it :)

Hi everyone. I ended up solving most of the issues described above by completely removing all my gems, and uninstalling rbenv and rvm which, I'm guessing, was the root of a lot of my problems (as in the two being installed and modified at once)
After using rbenv to update Ruby versions, and switching to that instead of the OS X system Ruby version, I was able to do something that I haven't been able to do in two weeks; install middleman!
Thanks a bunch to everyone above who helped me achieve this. Seeing this community step up and help folks like me really means a lot and keeps my faith in the dev community shining bright :) I've come up against another little snag but I'll open a new ticket for that one which, relatively speaking, isn't as curly as the issue here.
Thanks again!


Model-driven Power Apps don't retain their icon in the office.com experience

Model-driven Power Apps don't retain their icon in the office.com experience when compared to home.dynamics.com
Only Canvas Power Apps bring over their icon to the office.com experience. The page should explain how a consistent user experience can be achieved in which icons for all apps regardless of Power Apps type can be rendered visible.

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

ID: 71a027bf-62d9-07f6-c15c-fc0e4d5b8686
Version Independent ID: f88d00be-be73-a187-c287-66f151073abb
Content: Quickly navigate with the Microsoft 365 app launcher - Power Platform
Content Source: power-platform/admin/quickly-navigate-office-365-app-launcher.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@TrutzS
Thanks for the feedback. I've made the product group aware of this for them to take action on it.


feat: NR-10056 adding sumary metrics to Key transaction entity

Relevant information
Describe what you have done and any details that you think are relevant or that you might want to discuss with us.
I have created summary metrics for Key Transaction with using golden metrics attributes
Checklist

[x] I've read the guidelines and understand the acceptance criteria.
[ ] The value of the attribute marked as identifier will be unique and valid.
[ ] I've confirmed that my entity type wasn't already defined. If it is I'm providing an
explanation above.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


HELP WHEN BUILDING

wHEN I COMPILE IT ALWAYS SHOW "PlayState.hx:537: characters 4-8 : Expected }"
i already removed these } and {, it's not working
kade engine 1.3.1

wHEN I COMPILE IT ALWAYS SHOW "PlayState.hx:537: characters 4-8 : Expected }"
i already removed these } and {, it's not working
kade engine 1.3.1

verify that the indentation of everything is correct
also this may mean you need to add a new } after line 536

Now it says
"PlayState.hx:538: characters 4-8 : Expected }"

Now it says
"PlayState.hx:538: characters 4-8 : Expected }"

"expected }" means there should be another } before it

like this

no, we mean after the code
}
else if (song.song.tolowercase() == 'test4')
}
(cool bg shit)
{

PlayState.hx:538: characters 4-8 : Expected }

now it says PlayState.hx:538: characters 13-17 : Expected }


"serverless-plugin-typescript" not found

My project is set as yarn zero install so I thought this plugin was about it.
I did the steps in README:
yarn add --dev serverless-plugin-typescript typescript

# Add the following plugin to your serverless.yml:
plugins:
  - serverless-plugin-typescript

But when I try sls deploy -s test it throws:
Serverless plugin "serverless-plugin-typescript" not found. Make sure it's installed and listed in the "plugins" section of your serverless config file. Run "serverless plugin install -n serverless-plugin-typescript" to install it.

Well, I know if I do that above it will install in node_modules but this conflicts with yarn zero install and the folder is automatically removed if I issue e.g. yarn.
So, what am I missing?

same problem here. I have installed     "serverless": "^2.72.3" and  "serverless-plugin-typescript": "^2.1.2", and I don't get why I get this error message while deyploying via Github workflow to AWS.


Leaflet plugin: don't call _resetOrigin in onAdd

Avoid drawing the heatmap in onAdd before we check is the _heatmap property is set. The fact that _resetOrigin was called was triggering errors for me when allowing the user to dynamically add/remove the heatmap layer from the map.
This PR simply takes the line that actually resets the origin in resetOrigin and uses that instead of calling the actual method (which in turns calls _draw, which caused the issues, since _heatmap was undefined when _draw was called).
This should fix #130.
PS. my editor cleaned up some trailing whitespace as well, made for a somewhat more messy commit, but figured I could leave those changes in there.

This just got in with https://github.com/pa7/heatmap.js/commit/1c47578cedca5a3037ebcdc2777fab005101ec0b and will be part of the next version. Thank you

@pa7 cool, looking forward to the next release then!


hi,how to add wake word :alexa,i want to say alexa,then i can talk with it without tap it

I don't know much about it but as the documentation says that your application should be run only with Alexa wake word which means that there should be a background service which continuously should run and the microphone too. As the microphone is given Alexa word as an input , the app should run but that would very costly (in my view) with respect to android hardware resource as you would have to run a background service which is continuously taking input voices and checking for wake word in it. Plus you also might have to run a continuously a Speech-to-Text conversion for checking the Alexa wake word.


Removing a software package fails when triggered from the c8y cloud

Describe the bug
When the request to remove a software package is triggered from c8y cloud
It fails to remove the package that is present in the system.
Once the operation is complete the response is not visible on the cloud UI.
To Reproduce
connect to "basic.stage.c8y.io"
Add a software package to the repository (Rolldice)
Trigger the install from the c8y UI
After successfully installed
Trigger request to remove the package  from the UI
Expected behavior
The package remove request  has to be completed successfully and update the UI with the result and the remaining software list should appear on the UI.
Environment (please complete the following information):

OS [incl. version]
Hardware [incl. revision]
System-Architecture [e.g. result of "uname -a"]
thin-edge.io version [0.5.3]

Additional context
Add any other context about the problem here.

@PradeepKiruvale Is this still an issue in tedge 0.8.0?

Not sure, Need to verify with the recent thin-edge version.

It's not reproducible in the 0.8.0 version. So, I will close this ticket.


Update the submodule repo readme

Description
[ What changed? Feel free to be brief. ]
The URL behind the contributing in read me
Checklist

[ ] The base branch of this PR is preview, rather than main

TYSM!


specificity values > 1 for certain kmers

When using the following kmer file:
id,sequence,pam,chromosome,position,sense
AAGACTGTGCGCTAATCTCT_1,AAGACTGTGCGCTAATCTCT,NGG,unknown,0,+

with guidescan enumerate against hg38_noalt.index (mismatches 3 and alt-pam NAG), we get the following sam line:
AAGACTGTGCGCTAATCTCT_1	0	unknown	0	100	23M	*	0	0	AAGACTGTGCGCTAATCTCTNGG	*	k0:i:1	k1:i:0	k2:i:0	k3:i:3	of:H:c53bf70d00000000000000000000000092ef3a47ffffffff010000000000000092ef3a47ffffffff020000000000000092ef3a47ffffffff9ba7545c000000009c2c699e000000002afe3c2000000000030000000000000092ef3a47ffffffff	sp:f:2.391802

or the following csv lines (succinct mode):
id,sequence,match_chrm,match_position,match_strand,match_distance,specificity
AAGACTGTGCGCTAATCTCT_1,AAGACTGTGCGCTAATCTCTNGG,chr1,234306480,+,0,2.391802
AAGACTGTGCGCTAATCTCT_1,AAGACTGTGCGCTAATCTCTNGG,chr9,12562870,+,3,2.391802
AAGACTGTGCGCTAATCTCT_1,AAGACTGTGCGCTAATCTCTNGG,chr19,3281519,+,3,2.391802
AAGACTGTGCGCTAATCTCT_1,AAGACTGTGCGCTAATCTCTNGG,chr3,49718166,+,3,2.391802

There's clearly something wrong here since specificity is reported > 1.

The actual sequence found in the fna using grep is AAGACTGTGCGCTAATCTCTTAG (i.e. with the alt-pam), indicating that the match reported in both the csv/sam cases is incorrect (the NGG was automatically added). All such detected cases of specificity > 1 seem to be with matches that have the NAG pam.


Sticky scrollspy styling not covering full width; creates horizontal scroll

I think this is actually caused by the absolute-positioned "hidden" tooltips.

Yup. We're facing this issue:
https://github.com/sir-dunxalot/ember-tooltips/issues/111

@allthesignals,  I don't like it but this fixes it:
html {
  overflow: hidden;
}

html, body {
  width: 100%;
  height: 100%;
  overflow-x: hidden;

  @include breakpoint(large) {
    height: 100%;
    overflow: hidden;
  }
}

Also, it's not just a "small screens scroll horizontal" problem. Large screens also scroll vertically past the profile so that the header moves out of the window. 😢

Should this have margin?

"stuck" state classes: sticky-element sticky-element--sticky sticky-element--sticky-top

It's full-width now. ;)

@chriswhong Feel free to merge #91 now. 🎉


Add documentation how to create a SwiftSyntax release

This is mostly internal documentation but it might be interesting to share with everyone how the SwiftSyntax releases, which include the parser library as a binary dependency, are created.

@swift-ci Please smoke test

@swift-ci Please test


Flickering on stack space when animations are enabled

Hey, I've a stack space and I'm running multiple instances of IntelliJ in that space but whenever I click anywhere on the app. App looses, gets focus back and it flickers. It's only happening when animations are enabled.
https://github.com/buraksirma/dotfiles/blob/main/yabairc

I am noticing this behavior as well. Heavily slows Discord and Slack for me with noticeable flickering.
https://github.com/maxmwang/dotfiles/blob/main/.yabairc

@buraksirma @maxmwang I'm having this issue too, but now at least I have a solution which is setting window_animation_duration to 0.0 - thank you both!

Same as #1493


Broken list formatting in the Requirements section

Broken list formatting in the Requirements section

Enable the device account with Skype for Business Server. To enable the device account your environment will need to meet the following prerequisites:

You'll need to have Skype for Business Online (Plan 2) or higher in your Office 365 plan. The plan needs to support conferencing capability.

If you need Enterprise Voice (PSTN telephony) using telephony service providers for Microsoft Teams Rooms you need Skype for Business Online (Plan 3).

Your tenant users must have Exchange mailboxes.

Your Microsoft Teams Rooms account does require a Skype for Business Online (Plan 2) or Skype for Business Online (Plan 3) license, but it does not require an Exchange Online license.

Assign a Skype for Business Server license to your Microsoft Teams Rooms account.

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

ID: 91cd0219-b3b0-da60-6416-c6b5a67623e3
Version Independent ID: 983d08b5-4a2c-838a-52eb-821045d2c9df
Content: Deploy Microsoft Teams Rooms with Exchange on premises
Content Source: Teams/room-systems/with-exchange-on-premises.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@shivtorov Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@shivtorov, thank you for your input. @dariomws306, thanks for the fix, I've merged the changes.


Add must-gather logs in case openshift-install fails

This will helpful for debuging issue directly getting the logs from
CI run.

/retest

/cherry-pick 4.7


Add a variety of tags

It would be nice to have tags to determine which custom stories are voice acted or if a custom story is actually canon to the Starcraft universe.
For example, Enslavers Redux, even though it was made by a fan, is actually a canon story and follows real events happening in the starcraft universe.
As for voice acting, the only 2 custom campaigns that I know of that are voice acted are Mass Recall, and The Antioch Chronicles.

Sounds like a good idea indeed.
I wouldnt mind suggestions for tag labels tbh.
As you say the more obvious ones are "based on lore" which Enslavers, Mass Recall and Shadows of the XelNaga fit, and voice acting (which also includes Wrath of the Taldarim and Unification of the Purifiers, and I am surely forgetting some other). I wanted to add other tags like Work in Progress as well.


Suggestion: move symfony/intl to 'suggest'

From what I can tell, symphony/intl is only used if ext-intl is not present. However, it is a huge package, and almost single-handedly prevents deployment to Laravel Vapor due to its size, when in all likelihood it's not even used.
Perhaps it should be moved to suggest in composer.json, in order to make that process smoother?

FWIW, the only way I was able to deploy to Vapor is to add all of symphony/intl's files to vapor.yml's undocumented 'ignore property.

I can see your problem and would be inclined to go with your suggestion. However, we can't make such a change anymore since it'll break everyone's apps who are using v10 and have not installed the ext-intl extension. Such a change can only be done in the next major release.

@driesvints Hmm, that's a good point. Is there maybe a way to install the package without intl? A seperate branch of version tag maybe?

@hipsterjazzbo you'll need to fork the package and maintain your own version unfortunately.

I'm gonna close this as I think it's better to keep the package. It's unfortunate that it's so large but I think it's better than having people to not have a working installation from the getgo.

Also: no-one else has posted any problems with this yet.


INC-805 - Get behaviour counts based on last review date

What does this do?

Calls a new endpoint in prison api which returns a list of case note counts group by type/subtype for a list of prisoners but also filters by a fromDate which is the last review date
This is used to then calculate the number of positive (POS) and negative (NEG) case note behaviours raised since the last review.

Last Review Date Calculation
The last review date is as follows:

find the latest Real Review (REVIEW/MIGRATED) incentive review.  If found - this is the review date
if no Real Review found then use the review date 3 month before today
if this review date is over 3 month old then make the review date 3 month before today

@xoen update PR based on your very good suggestions!


Upgraded Android support version to 23.+

Fixes mauron85/react-native-background-geolocation#116

Nice, let's try to get this merged ASAP. 👍

Sorry guys. Any attempt to lock dependencies version will not be merged. Already talked about it in https://github.com/mauron85/cordova-plugin-background-geolocation/pull/313

Makes sense, however what's currently the proper way forward to fix #116?

Seriously I don't know. This is creepy problem of projects such as react-native where many plugins have to coexists and agree somehow on shared dependencies versions.
Maybe there is clean way how to override plugin settings on a project level.

@MichielDeMey but you can still fork project and lock android support lib version. The only downside I see is that you will have to install it from github (instead of npm) and merge upstream changes from time to time. But hopefully we can find better solution.

I kinda like @alexdunne suggested solution: https://github.com/mauron85/react-native-background-geolocation/issues/116#issuecomment-356575145
Didn't tested it myself. But seems I like adequate solution to this problem.

I tried that, but that did not seem to work at first.
Found out that you need to place this in the build.gradle of the app module.
Had to restart my Android Studio as well to pick up the changes for some reason.
Thanks, this does seem like the proper way forward. Feel free to close this issue.


Migrate the database id's from sequential bigint to UUID

The tables currently use sequential bigint to set the id. This change modifies the behaviour to use uuid instead.
The pgcrypto gem sets uuid as the default for all future tables that are created.
The webdack gem converts existing id fields to uuid and can be removed once the migrations have been run
Add foreign keys to existing references
Converts foreign keys on existing references to uuid
Convert all other id's (that are not foreign keys) to uuid
Checklist
Before you ask people to review this PR:

[x] Tests and rubocop should be passing: bundle exec rake
[x] Github should not be reporting conflicts; you should have recently run git rebase master.
[x] There should be no unneccessary whitespace changes. These make diffs harder to read and conflicts more likely.
[x] The PR description should say what you changed and why, with a link to the JIRA story.
[x] You should have looked at the diff against master and ensured that nothing unexpected is included in your changes.
[x] You should have checked that the commit messages say why the change was made.

It would be good to understand a bit more about why you're changing this. Neither the PR description nor the commit message on ca3e4cdb7592fd28119f9635886ed52de3eae85b make this very clear.

💁  The drive among other things, was to stop creating extra columns in the table that define a UUID identifier for the models, where with this setup by default, both the primary keys and the foreign keys would provide that out of the box.
More so, by converting the sequential IDs to UUIDs, when they're being used in the web pages, they're unique and someone can't just replace the ID with its precedent number.
Not to claim this article is by any means the truth, but some more info about the subject can be found [here|https://medium.com/@Mareks_082/auto-increment-keys-vs-uuid-a74d81f7476a].
@bleach I'm happy to discuss this offline, if you have any concerns about it.


meson

also pkgconfig, some format fixes

systemd-unit-prefix. And a default if the option is not specified.

Nit: it would be nice to make qrtr-ns optional and maybe even skip it by default in the followup.

Nit: it would be nice to make qrtr-ns optional and maybe even skip it by default in the followup.

that was my idea for the next pr.. and then a new tagged release right after it - sounds good?

SGTM


Camouflage takes a long time to start up with a size-able number of proto files

Describe the bug
Camouflage takes a long time to start up with a size-able number of proto files - say about 25+ files
To Reproduce
Steps to reproduce the behavior:
Unsure if I can fully describe how. Our proto files are organised in multiple directories and sub-directories.
Expected behavior
Camouflage should start up in less time - a wait for 20 mins doesn't bode well especially when we wish to include it as a part of a CI/CD pipeline
Desktop (please complete the following information):

OS: MacOS Catalina
Version - 0.5.6

@ankitanallana-livongo : Could you please confirm if you still see the issue in 0.5.7?

@shubhendumadhukar Just tried it - it's been 12 mins so far and Camouflage hasn't fully started up yet 😔

It might take some time to come up with a fix, since it's complicated to replicate this issue. I'd recommend using .protoignore for the time being as discussed earlier.

Create a .protoignore file at the root of your project.
Specify the absolute path or relative path (from root), of any/all protofiles which have been imported to other protofiles. Refer to Mocking gRPC in documentation for a more detailed explanation.

I am not sure if this will make the startup significantly faster, but it should reduce it to a certain extent.

@shubhendumadhukar Surely, I'll work with a .protoingnore until then - many thanks!


style: styled swagger apps

closes #3041

:tada: This PR is included in version 5.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


In document spring.cloud.stream.bindings.input.group=hello will not work

In document it is talking about reset the queue name

Go to the RabbitMQ management console or any other RabbitMQ client and send a message to input.anonymous.CbMIwdkJSBO1ZoPDOtHtCg. The anonymous.CbMIwdkJSBO1ZoPDOtHtCg part represents the group name and is generated, so it is bound to be different in your environment. For something more predictable, you can use an explicit group name by setting spring.cloud.stream.bindings.input.group=hello (or whatever name you like).

(https://github.com/spring-cloud/spring-cloud-stream/blame/528eaf041a7fb86c6c778c33ddc09c3881641009/docs/src/main/asciidoc/preface.adoc#L141)
It will not work. In case you have a method name log
public Consumer<Person> log() {

it will work when you
spring.cloud.stream.bindings.log-in-0.group=hello

Or if you define
spring.cloud.stream.function.bindings.log-in-0=input

and then
spring.cloud.stream.bindings.input.group=hello

Should probably update the document, and link to the section about "function binding names".

That is correct, with functional programming model the binding names derive from function names, so in your case log-in-0 is the binding name that should be referenced in properties spring.cloud.stream.bindings.log-in-0.group=hello.
However if you don't like the derived name you can remap it to something more meaningful to you - spring.cloud.stream.function.bindings.log-in-0=input and from that point on you should use that binding name instead of derived binding name = spring.cloud.stream.bindings.input.group=hello.
So I don't see any issue here, but please feel free to re-open it if you believe there is something more to discuss.


txt2tags: 2.6 -> unstable-2022-10-17

Motivated by https://github.com/NixOS/nixpkgs/pull/201859.
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

2 packages marked as broken and skipped:

qgis
qgis-ltr

6 packages built:

grml-zsh-config
libixp
thunderbolt
txt2tags
wmii
xdgmenumaker


chore: add permissions for tgp

Fixes #N/A
Description
Adds the missing pod delete permissions
How was this change tested?
make apply and set pod deployment terminationGracePeriod higher than the nodepool termination graceperiod
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 78.126%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
8836

Relevant Lines:
11310

💛  - Coveralls


Docs translated to english (#13)

Deleted old documentation
Moved russian documentation to README_RUS.md file
README.md file translated to english

Corresponds to #13 .


Scorecard shows warnings from k8s API response when Operator making requests to deprecated REST APIs

Feature Request
Describe the problem you need a feature to resolve.
I'd like to see in the default Scorecard tests results about the deprecation/removal of APIs in the next versions.
Goal
The goal is to check if Scorecard could gathering the info that is already provided by Kubenertes API when the operator is running on the cluster does request using deprecated APIs.
No Goal

Implement any logic which will check if a deprecated API is or is not used by the operator. It is already done by the k8s api
Implement any logic that will lint the files/manifests. Statics checks on the manifests are already addressed via the OperatorHub validator on the bundle validate command.
Implement a new feature that allows performing tests on the Operator running on the cluster. That is addressed by Scorecard already.

Motivation
The Scorecard is the SDK feature that is capable of running tests on the cluster. In the same way that is recommended to perform regression tests on the projects and then, check its events/metrics to see if any warnings about deprecated APIs were raised it would be gathered by Scorecard default tests and appended to its results.
Use Case
I am as operator author, I would like to be able to gather the warnings raised by the k8s API when my operator is running and tested by Scorecard on the cluster then, I would be able to be easily informed beforehand that my operator is using/doing requests to deprecated APIs
Describe the solution you'd like.
Implementation in the Scorecard checks to looking for the raised events/metrics in the  K8S API to gathering its WARNINGS and return as a result of its tests. More info: https://kubernetes.io/blog/2020/09/03/warnings/#deprecation-warnings. E.g:

Run Scorecard tests to trigger the reconcile by for example applying its CRs on the cluster
Then, gathering the metrics raised by K8s API and append its result in the Scorecard results. (e.g We can check the warnings by looking at the events e.g kubectl get events --field-selector="reason=AppliedWithWarnings" --all-namespaces) :

OR
kubectl get --raw /metrics | prom2json | jq '
.[] | select(.name=="apiserver_requested_deprecated_apis").metrics[].labels
'

Appending the WARNINGs to the Scorecard results

Aditional Context:
OCP introduce Prometheus alerts using k8s metrics
Two alerts have been introduced with OpenShift 4.8

APIRemovedInNextReleaseInUse - for APIs that will be removed in the next release.
APIRemovedInNextEUSReleaseInUse - for APIs that will be removed in the next EUS release.

More information on alerts, how to retrieve them or how to get notified is available in OpenShift documentation.
/language go
/language ansible
/language helm

It could be just me, but this “reporting the deprecated/removed APIs” sounds like a really handy scorecard test that is worth becoming a default test and benefits all Operators

/lifecycle frozen

Following is aditional information that can help us to do that as a proposed solution.
Proposed solution
Develop a Scorecard custom test to identify the deprecated APIs using the k8s metrics and raise warnings based on the Operator Services (CRs) usages. This test ought to work dynamically and without the need to be updated and supplemented every time an API is flagged as deprecated.
What value does it can bring?

This solution would allow us to notify the Operator authors without spending effort for each new version/deprecation made in the k8s API.
Provide a functional example with Scorecard. Currently, we have no Scorecard doing tests that effectively are functional or using the cluster. The Scorecard tests available are mainly liting the files used in the bundles such as we do with the static validators.

TL'DR: Technical Details
Is it enough just to install the operator?
It probably requires applying all CRs to ensure that the operator will hit the deprecated apis in 1.25, 1.26 for e.g and trigger the Kube metrics.
How to use the Kube metrics/alerts?
We are able to run the following command. But that is not good because we are not removing the requests that were not done by the operator.
We can shape/develop a command such as follows to get the metrics but we need to find out how to try to exclude what was not done by the operator.
kubectl get --raw /metrics | prom2json | jq '
  # set $deprecated to a list of deprecated APIs
  [
    .[] |
    select(.name=="apiserver_requested_deprecated_apis").metrics[].labels |
    {group,version,resource}
  ] as $deprecated

  |

  # select apiserver_request_total metrics which are deprecated
  .[] | select(.name=="apiserver_request_total").metrics[] |
  select(.labels | {group,version,resource} as $key | $deprecated | index($key))
'

We might be able to:

combine these metrics (https://github.com/kubernetes/kubernetes/blob/d7545437267be8cd162e76b81c0cf4a47dd33208/test/instrumentation/testdata/stable-metrics-list.yaml#L241-L266) into a query to give you something specific to your operator (see the Kubernetes Deprecation Policy section on API resources, see: https://kubernetes.io/docs/reference/using-api/deprecation-policy/#rest-resources-aka-api-objects).
if we look at the queries used to define in the OCP alerts, we check that it uses the system_client label to exclude some operators/controllers, so we might be able to use it, see: https://github.com/openshift/cluster-kube-apiserver-operator/blob/release-4.10/bindata/assets/alerts/api-usage.yaml

Have we an example scenario?
An operator that is using these removed APIs in 1.25 for we use to test is https://github.com/keycloak/keycloak-operator.
See: https://github.com/keycloak/keycloak-operator/blob/996c21bca9f1d948e784d4f1ef5caaba5088944e/pkg/model/postgresql_aws_periodic_backup.go#L6 the deprecated/removed API will be called to reconcile the KeycloakBackup CR because it will create the batch resource on the cluster using k8s.io/api/batch/v1beta1
How to create a custom Scorecard test?
https://sdk.operatorframework.io/docs/testing-operators/scorecard/custom-tests/
What this custom Scorecard would need to be able to do?

The test ought to identify all CR's available and apply them
The test should verify the k8s apis deprecated and verify the metrics in order to produce warnings


[WIP] Create an integration test

Create an obi_base.owl product (see https://github.com/ontodev/robot/pull/570) *
Retrieve BFO classes, RO core, and IAO metadata
Merge these together and run HermiT reasoner
If reasoning fails, dump unsatisfiable module (build/unsatisfiable.owl) & create explanations (robot explain) for unsatisfiable classes (build/explain/*.md)

* This may not be complete as it is only including stuff in the OBI namespace. If there are other classes that should be included in the "base" product (e.g., stuff OBI has adopted), we can add those in.
This is not run on Travis due to use of the HermiT reasoner. I have included it as part of the release (make all) and it can be run on its own using make verify-integration.
Right now it fails with one unsatisfiable class (see #1067), but you can see a full explanation in build/explain/OBI_0000234.md (after running this test). This might be a little overkill, but it's a cool use of robot explain 🙂

@beckyjackson On Monday's call we agreed to spend some time improving OBI's ROBOT report and OBO Dashboard score. For that we need a proper obi-base.owl file. I'd appreciate your help with that, either by reviving this PR or creating a new one.


Legend Tooltip not working. Not even in docs.

tooltip: true is set and works great on the main chart but nothing appears when hovering over the legend.
Even if you go to the documentation page for the legend the tooltip for the legend doesn't show up.
I'm using a modern Chrome browser. Maybe somebody else can verify as well.
Thanks!
(Great library!)
Joshua

Tooltip is not implemented in the legend yet

@wa0x6e Thanks for verifying! Is that something you would be interested in seeing and accepting a PR for?

Yes


WithAuthenticationRequired hoc on protected routes sends request for fetching tokens each time

import { withAuthenticationRequired } from '@auth0/auth0-react';

const ProtectedComponent = ({ component, ...propsForComponent }) => {
  const Cp = withAuthenticationRequired(component);
  return <Cp {...propsForComponent} />;
};

export default ProtectedComponent;

Above setup on muliple protected routes cause https://dev-gmdm3--a.us.auth0.com/oauth/token  to call every time? Is that any proper way to handle this?

Hi @KaushikSathvara
Assuming you're not storing the Access Token in local storage (using the cacheLocation localstorage) and not using refresh tokens. Then I would expect a silent login on every page reload.
As long as the page isn't reloading and the access token is not expired, than the SDK shouldn't do a silent login.
If you think there's an issue, please share an example app that demonstrates the issue and I can debug it.

That's great explained, Thank you for the answer. Issue resolved.


Added the IPV6PrefixLength field

Signed-off-by: Vinod K L Swamy<EMAIL_ADDRESS>

Is this just fixing an omission from #818?

Is this just fixing an omission from #818?

Yes, It was omitted from #818


Made minor changes to get_started_with_custom_training_pipeline_components file

Made minor changes to get_started_with_custom_training_pipeline_components file

[x] This notebook has been added to the CODEOWNERS file under the # Community Notebooks section, pointing to the author or the author's team.
[x] Passes all the required formatting and linting checks. You can locally test with these instructions.

Added colab link and colab related content

ran fine in colab and workbench


Improvements for complex select statements when using new object expression

My update allows you to alias objects created with the "new" object expression, as well as the ability to create queries that allow you to have multiple "new" object expressions and mixed scalar results.
Suppose you create a query as such:
SELECT new UserDTO(u.id,u.name) as user,new AddressDTO(a.street,a.postalCode) as address, a.id as addressId FROM User u INNER JOIN u.addresses a WITH a.isPrimary = true

upon executing this query, you'll end up with a result set that looks like the following:
array(
    0=>array(
        0=>{UserDTO object},
        1=>{AddressDTO object},
        2=>{u.id scalar},
        3=>{u.name scalar},
        4=>{a.street scalar},
        5=>{a.postalCode scalar},
        'addressId'=>{a.id scalar},
    ),
    ...
)

My changes fix that so you'd end up with a more usable result set:
array(
    0=>array(
        'user'=>{UserDTO object},
        'address'=>{AddressDTO object},
        'addressId'=>{a.id scalar}
    )
    ...
)

@jaimz22 seems good overall, could you still add the UPGRADE.md notes?

That's funny, I was looking at this today, curious about when something would happen. I completely forgot about the upgrade.md.
I'll put something as soon as I get the opportunity.

Upgrade comment added through https://github.com/doctrine/doctrine2/commit/c49b0795dba932e9a758639f10e5d6c12737d202

@guilhermeblanco thanks for making that change


[SPARK-32755][SQL] Maintain the order of expressions in AttributeSet and ExpressionSet

What changes were proposed in this pull request?
This PR changes AttributeSet and ExpressionSet to maintain the insertion order of the elements. More specifically, we:

change the underlying data structure of AttributeSet from HashSet to LinkedHashSet to maintain the insertion order.
ExpressionSet already uses a list to keep track of the expressions, however, since it is extending Scala's immutable.Set class, operations such as map and flatMap are delegated to the immutable.Set itself. This means that the result of these operations is not an instance of ExpressionSet anymore, rather it's a implementation picked up by the parent class. We also remove this inheritance from immutable.Set and implement the needed methods directly. ExpressionSet has a very specific semantics and it does not make sense to extend immutable.Set anyway.
change the PlanStabilitySuite to not sort the attributes, to be able to catch changes in the order of expressions in different runs.

Why are the changes needed?
Expressions identity is based on the ExprId which is an auto-incremented number. This means that the same query can yield a query plan with different expression ids in different runs. AttributeSet and ExpressionSet internally use a HashSet as the underlying data structure, and therefore cannot guarantee the a fixed order of operations in different runs. This can be problematic in cases we like to check for plan changes in different runs.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Passes PlanStabilitySuite after regenerating the golden files.

ok to test

Test build #128101 has started for PR 29598 at commit 5afdedb.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32726/
Test PASSed.

Test build #128102 has started for PR 29598 at commit 5afdedb.

Test build #128110 has started for PR 29598 at commit f235b53.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32734/
Test PASSed.

Test build #128101 has finished for PR 29598 at commit 5afdedb.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128101/
Test FAILed.

Test build #128102 has finished for PR 29598 at commit 5afdedb.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128102/
Test FAILed.

Test build #128110 has finished for PR 29598 at commit f235b53.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128110/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32770/
Test PASSed.

Test build #128145 has started for PR 29598 at commit f3a79a3.

Test build #128149 has started for PR 29598 at commit b0478f3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32774/
Test PASSed.

Test build #128145 has finished for PR 29598 at commit f3a79a3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128145/
Test FAILed.

Test build #128149 has finished for PR 29598 at commit b0478f3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128149/
Test FAILed.

jenkins retest this please

Test build #128153 has started for PR 29598 at commit b0478f3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32778/
Test PASSed.

Test build #128156 has started for PR 29598 at commit 9590555.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/32781/
Test PASSed.

Test build #128153 has finished for PR 29598 at commit b0478f3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128153/
Test FAILed.

Test build #128156 has finished for PR 29598 at commit 9590555.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128156/
Test PASSed.

Sorry to leave a message in a completed issue. @cloud-fan @dbaliafroozeh This patch seems to bring about some different behavior between use Scala 2.12 and Scala 2.13.
I found that the number of failed cases increased with this patch of the sub-suites of  PlanStabilitySuite.
For example, if we execute
mvn clean test -pl sql/core -Dtest=none -DwildcardSuites=org.apache.spark.sql.TPCDSV2_7_PlanStabilitySuite -Pscala-2.13 -am

The test result with out this patch is
Tests: succeeded 32, failed 0, canceled 0, ignored 0, pending 0
All tests passed.

and with this patch is
Tests: succeeded 1, failed 31, canceled 0, ignored 0, pending 0
*** 31 TESTS FAILED ***

I haven't found the root cause yet. Do you have any good ideas for fix this problems?

This should have been merged before we have PlanStabilitySuite, as the query plans in golden files were kind of random previously. That's why this PR updates PlanStabilitySuite.
If your spark fork has different golden files for PlanStabilitySuite, you should just re-generate golden files after this patch.

@cloud-fan Maybe I didn't describe it clearly, now I use the master of spark-source to execute  maven test with Scala 2.12
mvn clean test -pl sql/core -Dtest=none -DwildcardSuites=org.apache.spark.sql.TPCDSV2_7_PlanStabilitySuite -am

All tests passed.
execute  maven test with Scala 2.13
mvn clean test -pl sql/core -Dtest=none -DwildcardSuites=org.apache.spark.sql.TPCDSV2_7_PlanStabilitySuite -am -Pscala-2.13

31 TESTS FAILED
without this patch execute  maven test , both Scala 2.12 and Scala 2.13 All tests passed

So always need to re-generate golden files  with Scala 2.13? Or we need to use different golden files for different Scala verision, feels a little unreasonable...

Interesting. So AttributeSet and ExpressionSet behave differently under scala 2.12 and 2.13.  @Ngone51 can you take a look?

@Ngone51 need some simple fix on compilation for Scala 2.13 , QueryPlan and  ShuffleBlockFetcherIterator.

@LuciferYang do you have a branch that contains the compilation fix?

@cloud-fan @Ngone51  we can use https://github.com/apache/spark/pull/29660

@cloud-fan @Ngone51 I think the reason for the problem is
https://github.com/apache/spark/blob/e7d9a245656655e7bb1df3e04df30eb3cc9e23ad/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/AttributeSet.scala#L106-L113
The -- of LinkedHashSet method is different between Scala 2.12 and Scala 2.13.
The impl of Scala 2.12(SetLike.scala) as follow:
override def --(xs: GenTraversableOnce[A]): This = clone() --= xs.seq

The impl of Scala 2.13(Set.scala)  as follow:
def -- (that: IterableOnce[A]): C = fromSpecific(coll.toSet.removedAll(that))

From the above code we can found that after baseSet -- otherSet.baseSet, the result order changed .
Maybe we can use baseSet.diff(otherSet.baseSet) instead of baseSet -- otherSet.baseSet, but I need to confirm the feasibility.

@cloud-fan @LuciferYang we can also try to use Java's LinkedHashSet here if there is a difference between different versions of Scala's mutable.LinkedHashSet.

@dbaliafroozeh -- returns a set, which gets converted into linked set by AttributeSet.apply(..). The 2.12 implementation will actually return a linked set, whereas the new probably returns a set.
@LuciferYang can you open a PR that basically uses 2.12 implementation inside AttributeSet?

@LuciferYang can you open a PR that basically uses 2.12 implementation inside AttributeSet?

Ok ~ I will give a new followup pr

@hvanhovell use clone() --= xs.seq instead of --?

I'd prefer diff if it works, as it's simpler.

Anything that explicitly maintains the insertion order (i.e. returns a LinkedHashSet) will do :).

diff returns a set and does not fall in that category.


patch: 修复部分字词读音

close #230

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (1f42aa7) to head (d14db75).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main      #232   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           23        23
  Lines        13193     13176   -17
  Branches       417       417
=========================================
- Hits         13193     13176   -17

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


Fix signal handling by replacing process

Fixes #85
rspec handles signals properly so instead of calling rspec as subprocess current process is replaced with rspec and make the current process signals aware

+1 for the fix

@2rba Thank you for PR. I've just released a new version of knapsack.
BTW If you would like to learn how dynamic test suite split works to cut down the CI build time, even more, you can learn https://docs.knapsackpro.com/2018/improve-circleci-parallelisation-for-rspec-minitest-cypress
or check video about Queue Mode in Knapsack Pro https://youtu.be/hUEB1XDKEFY


Minor fixes that fixes JSON schema write issue

This has no impact on the output packed file so no impact on the workflow itself

@alexiswl - out of curiosity - what's the rationale for the proposed update?

Adds compatibility to https://github.com/common-workflow-language/cwl-utils/pull/288


Removal of availablePlugins breaks addons

A number of older addons break with ember-cli-preprocess-registry versions 4.0+ with the following error:
Cannot read properties of undefined (reading '...')

We've traced it down to the removal of availablePlugins from registry.
We've seen this problem with the following plugins:

ember-basic-dropdown
ember-power-select
ember-side-menu
and there seem to be more...

Is this an intended breaking change?

Any news on this?


How to deploy freshmaker for MBS on fedora28

@qixiang
Hi Qixiang:
I need to deploy freshmaker for MBS on fedora28.
The version of freshmaker  on my fedora28 is freshmaker-0.0.4-5.fc28.noarch.(through dnf install -y freshmaker)
I have the following doubts about the deploying of freshmaker for MBS on fedora28.

Can I deploy freshmaker on a independent server(neither MBS server nor distgit server )?
Is “/etc/freshmaker/config.py” the only file I need to modify according to my envrionment(GIT_BASE_URL, MBS_BASE_URL,,,)?
I am not really understand the meaning and function of PDC_URL in config.py. Do I need my own PDC？
The docs about freshmaker is not for freshmaker-0.0.4. Would you please give me some information that can help me to modify config.py and deploy freshmaker for MBS on fedora28?

Hi @Cav4ever , as I mentioned in #80 Freshmaker dropped the plan of supporting rebuilding modules a long time ago, so it was just on the initial plan and  we have never reached that goal.

Thank you for your quick reply and kind help.


col_exists handling of multiple columns

The description for col_exists implies that it can handle multiple columns. However the method for doing this is not apparent.
col_exists(column = c(start_date, age)) looks for a column called "c(start_date, age)"
col_exists(column = c("start_date", "age")) looks for a column called c('start_date', 'age')
Given this function isn't fully documented I'm not sure if I'm missing something. Is there a way to pass a vector of column names to this function?

Sorry it took awhile to get to this. I've modified this function to accept multiple columns. However, the implementation is quite different than in the other functions. In cols_exist() (renamed to imply that the standard case is to check for multiple columns), we can pass multiple column names (cols) as a vector, or, as bare names in vars() (reexported from dplyr).
library(pointblank)

df <-
  structure(list(A = c(NA, 2L, 3L, 4L, 5L, 6L, NA, 8L, 9L, NA),
                 B = c(11L, 12L, 13L, NA, NA, NA, 17L, 18L, 19L, 20L),
                 C = c(NA, NA, NA, 24L, NA, 26L, NA, 28L, NA, 30L)),
            .Names = c("A",  "B", "C"), row.names = c(NA, -10L),
            class = "data.frame")

# Test with a vector of columns
agent_1 <-
  create_agent() %>%
  focus_on(tbl_name = "df") %>%
  cols_exist(cols = c("A", "B", "C", "D")) %>%
  interrogate()

agent_1

# Test with a column names in `vars()`
agent_2 <-
  create_agent() %>%
  focus_on(tbl_name = "df") %>%
  cols_exist(cols = vars(A, B, C, D)) %>%
  interrogate()

agent_2

In both cases, we get 3 passing validations and 1 failing.
I'm also thinking that the other functions should adopt vars() to express column names. It's pretty standard in dplyr and ggplot and wouldn't be surprising to most users.


[Issue 6170][functions] add custom property option to functions

Fixes #6170
Motivation
Allow users set custom system properties while submitting functions. This can be used to pass credentials via system property.
Modifications

pulsar-admin client tool to accept multiple --custom-property options while creating the function
function's java runtime to append these provided properties.

Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): no
The public API: no
The schema: no
The default values of configurations: no
The wire protocol: no
The rest endpoints: no
The admin cli options: yes
Anything that affects deployment: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

Now we can submit a function with multiple custom properties as follows:
./bin/pulsar-admin functions create \
--custom-property prop1="hello_world" --custom-property success=1 \
--jar ./pulsar-functions/java-examples/target/pulsar-functions-api-examples.jar \
--classname org.apache.pulsar.functions.api.examples.ExclamationFunction \
--tenant public --namespace default --name exclamation \
--inputs persistent://public/default/my-topic \
--output persistent://public/default/exclamation

After a discussion with @sijie , the way this options works is as follows now:
./bin/pulsar-admin functions create \
--custom-property prop1=PROP1_VALUE --custom-property prop2=PROP2_VALUE \
--jar ./pulsar-functions/java-examples/target/pulsar-functions-api-examples.jar \
--classname org.apache.pulsar.functions.api.examples.ExclamationFunction \
--tenant public --namespace default --name exclamation \
--inputs persistent://public/default/my-topic \
--output persistent://public/default/exclamation

both PROP1_VALUE and PROP2_VALUE would be replaced with the actual system property value when the function process is being started.

@nlu90 Hi, thanks for the work you did here :).

So PROP2_VALUE must be a system env var? What if it's undefined? Does the system throws an exception on boot?

All these options are defined using pulsar-admin with arguments. Does the creation via YAML function configuration supports these features?

@KannarFr Thanks for your feedback

I added check for whether the property is set in broker/worker. If it's not set, an IllegalArgumentException will be thrown and the function submission will be failed.

Yes, this change also works with YAML configuration. For my previously example submission command, you can also use the following YAML file as a configuration file to submit:

jar: ./pulsar-functions/java-examples/target/pulsar-functions-api-examples.jar
className: org.apache.pulsar.functions.api.examples.ExclamationFunction
tenant: public
namespace: default
name: exclamation
customProperties:
  - prop=HELLO
inputs:
  - persistent://public/default/my-topic
output: persistent://public/default/exclamation

and the submission command is:
./bin/pulsar-admin functions create --function-config-file ~/func-conf.yaml

@nlu90 the change looks very good. although I think it might be worth thinking of the extensibility of this approach. We might be looking into some more generic variable binding approach that allows user dynamically generating the properties or values through variable bindings. Serverless provides a good example of how to load variable bindings through different formats (e.g. environment variables,  cli options, and etc).

@sijie We can create a new issue for the yaml file variable extension feature and add it in a separate PR.

@nlu90 sounds good. do you want to create an issue for that?

@nlu90 actually looked into the description of #6170, I think what @KannarFr is looking for might be similar to a variable binding approach. Maybe let's ask @KannarFr for some clarifications.

The goal is to use system env var defined and pass them to functions via
the yaml configuration file. Like myProp: $MY_PROP.
Le mar. 18 févr. 2020 à 20:40, Sijie Guo<EMAIL_ADDRESS>a
écrit :

@nlu90 https://github.com/nlu90 actually looked into the description of
#6170 https://github.com/apache/pulsar/issues/6170, I think what
@KannarFr https://github.com/KannarFr is looking for might be similar
to a variable binding approach. Maybe let's ask @KannarFr
https://github.com/KannarFr for some clarifications.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/pulsar/pull/6348?email_source=notifications&email_token=ABZLQJIO756ZVJTA6SNUK6LRDQ2RBA5CNFSM4KWWN7P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMD7FCY#issuecomment-587723403,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZLQJIFEPS37EJEDGMK6PLRDQ2RBANCNFSM4KWWN7PQ
.

Hi @KannarFr, Just want to confirm if the following solution meet your needs (Notice the last line of customRuntimeOptions):
tenant: "test"
namespace: "test-namespace"
name: "example"
className: "org.apache.pulsar.functions.api.examples.ExclamationFunction"
inputs: ["test_src"]
userConfig:
  "PublishTopic": "test_result"
output: "test_result"
autoAck: true
parallelism: 1
customRuntimeOptions: "-DmyProp=${MY_PROP}"

and when you create function with this yaml file, the variable ${MY_PROP} will be automatically replaced with the actual system property value.
Let me know your thoughts.

That's it! All seems perfect then.
Le mar. 18 févr. 2020 à 23:17, Neng Lu<EMAIL_ADDRESS>a écrit :

Hi @KannarFr https://github.com/KannarFr, Just want to confirm if the
following solution meet your needs (Notice the last line of
customRuntimeOptions):
tenant: "test"namespace: "test-namespace"name: "example"className: "org.apache.pulsar.functions.api.examples.ExclamationFunction"inputs: ["test_src"]userConfig:
"PublishTopic": "test_result"output: "test_result"autoAck: trueparallelism: 1customRuntimeOptions: "-DmyProp=${MY_PROP}"
and when you create function with this yaml file, the variable ${MY_PROP}
will be automatically replaced with the actual system property value.
Let me know your thoughts.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/pulsar/pull/6348?email_source=notifications&email_token=ABZLQJIUSGWBTOZJTEDKAXTRDRM5ZA5CNFSM4KWWN7P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMFR7PQ#issuecomment-587931582,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZLQJLM6ZDOB4UCTQBVIH3RDRM5ZANCNFSM4KWWN7PQ
.

@sijie  @KannarFr Now you can submit a function with the following yaml file:
jar: ./pulsar-functions/java-examples/target/pulsar-functions-api-examples.jar
className: org.apache.pulsar.functions.api.examples.ExclamationFunction
tenant: public
namespace: default
name: exclamation
inputs:
  - persistent://public/default/my-topic
output: persistent://public/default/exclamation
customRuntimeOptions: "-Dprop1=${MY_PROP1} -Dprop2=${MY_PROP2}"

One more question is currently if fetch function info with the cli, it will show the actual value of ${MY_PROP1} and ${MY_PROP2}, is this expected? Or should we hide the actual value in the cli result?

@nlu90 Well considering logs are often exported to external services, I think we must hide them from logs. Thats being said, we can log the env var name like: injecting $PROP as prop foreach prop. WDYT?

@KannarFr Now no actual variable value will be logged into files.

@nlu90 Perfect! Thanks for all the work you did here :).

@sijie can we merge this?

@nlu90 oh, there few tests issues, can you check them?

/pulsarbot run-failure-checks

@sijie Can you merge it? :)

What is the status of this PR?

@KannarFr Sorry for the late reply, I was busy with some other projects.
After a discussion with @sijie , now the changes enable you put the env variable in userConfig and get the actual value via context.getUserConfigValue
an example yaml would be:
jar: ./pulsar-functions/java-examples/target/pulsar-functions-api-examples.jar
className: org.apache.pulsar.functions.api.examples.ExclamationFunction
tenant: public
namespace: default
name: exclamation
inputs:
  - persistent://public/default/my-topic
output: persistent://public/default/exclamation
userConfig:
  "prop1": "$MY_PROP"

and you can access the actual value for prop1 in your function code like this:
context.getUserConfigValue("prop1")

@nlu90 Thanks for your answer.
So
  "prop1": "$MY_PROP"

reads $MY_PROP from system env vars? Right?

@nlu90 Thanks for your answer.
So
  "prop1": "$MY_PROP"

reads $MY_PROP from system env vars? Right?

Yes.

Awesome!

Docs have been added here.
Will copy to Pulsar later.


V8 usability

Description

Made things more readable for various themes
Fixed the annoying editor tool tips.
Fixed consistency issues with the welcome frame
Fixed annoying things with changelog

Motivation and Context

Fixes #236
How Has This Been Tested?

Works on this:
IntelliJ IDEA 2020.1 (Ultimate Edition)
Build #IU-201.6668.121, built on April 8, 2020
Licensed to Alex Simons
Subscription is active until February 21, 2021
Runtime version: 11.0.6+8-b765.25 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-101-generic
GC: G1 Young Generation, G1 Old Generation
Memory: 512M
Cores: 12
Non-Bundled Plugins: io.acari.DDLCTheme
Current Desktop: ubuntu:GNOME

Types of changes

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[X] My code follows the code style of this project (./gradlew check passes clean).

Tip: If you have lint issues just run ./gradlew :ktlintMainSourceSetFormat.

[X] I updated the version.
[X] I updated the changelog with the new functionality.


add my first file

I have created a branch, created a file, and made a commit! And now I appear to be creating another file?

Completes the learn tutorial. Mayhaps I can now do some stuff.


How to do pagination in MVC

Description
In the page I read "This tutorial has not been updated for ASP.NET Core 6 or later."
For an initiation to pagination with MVC in 2024, what platform would you recommend?
Page URL
https://learn.microsoft.com/en-us/aspnet/core/data/ef-mvc/intro?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/data/ef-mvc/intro.md
Document ID
8daf79df-eac4-358b-e6f0-6def45bd54da
Article author
@tdykstra

Associated WorkItem - 286792

@tdykstra  @wadepickett  can we clean up titles? That's really important for Azo too.

For an initiation to pagination with MVC in 2024, what platform would you recommend?

Hello @Gluups. If you follow the tutorial directions and create a .NET 5 project, the tutorial should still work. The Program.cs code will be out of date, but the pagination section code should work the same in the current release.


Allow BigInteger up to 33 bytes in order to store UINT256_MAX ?

In the current goloop version, we can't deploy the following statement without raising an exception:
BigInteger MAX_UINT256 = new BigInteger("ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff", 16);

Caused by: java.lang.ArithmeticException
       at s.java.math.BigInteger.isValidLength(BigInteger.java:399)
       at s.java.math.BigInteger.setUnderlying(BigInteger.java:362)
       at s.java.math.BigInteger.<init>(BigInteger.java:28)
       at s.java.math.BigInteger.<init>(BigInteger.java:32)
       at u.x.x.x.HelloWorld.<init>(Unknown Source)

Indeed, the underlying BigInteger bytearray is 33 bytes long as it stores the number sign.
https://github.com/icon-project/goloop/blob/bfeb09683738396986311407875eba209ffb1b77/javaee/rt/src/java/s/java/math/BigInteger.java#L396-L402
That makes things complicated for 256 bits unsigned int arithmetic. That's something usual in other smart contract programming languages, so porting becomes problematic with that limitation.
Would it be possible to increase that limit ?

I agree to support at least uint256 range.
19cdc39c4e25af2085fb68069f26d991ad80f362 allows java contract to use BigInteger in the closed range [int256 min, uint256 max].
Thank you.


This pkg appears abandoned. I recommend switching to "ws", it's a very similar implementation

This pkg appears unfortunately abandoned, not a word from devs, not a commit in 4 years, and the only action in 2023 has been 2 closed issues. A shame, after I have relied on it since 2017.
I recommend switching to npm "ws", it's a very similar implementation and takes almost no effort to switch from "websocket" to "ws" because the events and syntax is almost identical.
Just wanted to post for anyone else wondering why their ws implementation isn't staying up with the newer versions and specs as they gradually are enforced as minlimits in newer services.

Hi, whilst I understand your opinion I would personally hesitate on recommending one or another package based upon your experience.  We have been working with Brian on this since 2011, and whilst you may consider it abandoned, it most certainly is not in our opinion.  The lack of updates to this module are in part due to it's extremely stable and reliable code, upon which we have relied upon for our own business.  We have this actively deployed today with well over 100k 24x365 always on clients and server instances regularly handling 32k concurrent connections per process.  I personally was involved in the process that finally led to the WebSocket RFC (indeed the 120+ attempts to come to an agreement on the standard) and have built our offering based upon it's functionality, and for the most part this module has remained stable and fully functional for the global scale production deployments we have today.
Our own experience with ws (which we regularly evaluate for our use case) was less than successful; whilst it offers out of the box support for advanced functionality like perMessageDeflate, it consumed all available server resources and did not scale to the 512k connections per server we support today.  Whether you choose to stay or go with this package is your own choice, but I just don't agree with you being in the position to publicly recommend others to follow your lead; ultimately it is up to everyone to make their own choice on suitability and act accordingly.

@rgillan thanks for jumping in here, I appreciate your coming to my defense, and the stellar review as well.
Indeed, it has been a little while since I've published an update. There haven't been any glaring issues requiring it, things have been pretty stable for a while. It wouldn't hurt to do a bit of a revision, update some of the code style to more modern JS -- this library was written in ES3 -- and at the very least, expose it a more modern API option that would fit in a little more nicely with current language capabilities. Async iterables, for example, so you can use for await...of to loop over incoming messages.
We'll see if I can get time to work on that soon.

I just don't agree with you being in the position to publicly recommend others to follow your lead;

I have not switched to ws, I am not advising others to "follow my lead", and I still use websocket for my biggest personal projects. I wanted to offer a helpful pointer to newcomers finding this repo and choosing what pkg to use. If it ain't broke, don't fix it mentality.
In general, the best (and indeed sometimes only) metrics that can be used to determine how well maintained any pkg is are latest commit date and issues. I can see that this could be an edge case where a finished package without need for updates (and therefore issues) could seem deceptively unmaintained.
I would like to extend an apology to @theturtle32 if my issue seemed like an attack of any sort, it was not intended to be one. My projects dependent on websocket have been stable without need for changes since their codebases were born in 2017. I am pleased to hear that you intend to maintain the package, as that will doubtlessly save me and countless others from having to migrate to other less performant alternatives.
In addition - Thank you @Rgillan for including your personal benchmarks. I was under the impression that ws is only a minor performance downgrade from websocket, so I appreciate the correction there. I do wish you hadn't switched straight into tribal defense mode regardless when a single "hey, no it's not, it's currently fully stable" would have sufficed, but this is the internet. This is still the most civil conversation I've seen today.

Sorry, 'I recommend switching to npm "ws"' was a little misleading then :). Happy to help, just maybe next time don't raise a NPM issue on someone else's module, you could always ask the maintainer directly.  Cheers


SciPy endorsement for SPEC-0

The discussion on SciPy's mailing list was opened here<EMAIL_ADDRESS>Lazy consensus applying, that means we are endorsing. I will send another email to SciPy's list with a week's additional RFC.

Thank you all for the thumbs up and Ralf for your message. Let's merge then.


link_parsers don't generate links

Describe the bug
link_parsers don't generate links.
To Reproduce
Steps to reproduce the behavior:

Clone this repository
Copy the config/cliff.toml file to the repository root
Run git cliff --latest. The commit_preprocessors will convert issues to links.
Remove the commit_preprocessors config and add (sourced from the README.md):

link_parsers = [
    { pattern = "#(\\d+)", href = "https://github.com/orhun/git-cliff/issues/$1"},
]

Run git cliff --latest. Links will not be rendered.

Expected behavior
The regex pattern of the link_parsers should be honoured.
Screenshots/Logs
If applicable, add screenshots to help explain your problem.
System (please complete the following information):

OS Information: Ubuntu 20.04
Project Version: 0.7.0

In order to use the links parsed by link_parsers, you need to update your changelog template. It does not work the same as commit_preprocessors, it is only for extracting the links, not for replacing the given regex with them.
As stated in README.md, you can use the links fields from the context:
"commits": [
    {
      "id": "e795460c9bb7275294d1fa53a9d73258fb51eb10",
      "message": "<description>",
      "..."
      "links": [{"text": "(set by link_parsers)", "href": "(set by link_parsers)"}]
    }
  ]

An example would be:
[changelog]
body = """
{% if version %}\
    ## [{{ version | trim_start_matches(pat="v") }}] - {{ timestamp | date(format="%Y-%m-%d") }}
{% else %}\
    ## [unreleased]
{% endif %}\
{% for group, commits in commits | group_by(attribute="group") %}
    ### {{ group | upper_first }}
    {% for commit in commits %}
        - {% if commit.breaking %}[**breaking**] {% endif %}{{ commit.message | upper_first }}\
        {%- if commit.links %} ({% for link in commit.links %}[{{link.text}}]({{link.href}}){% endfor -%}){% endif %}\
    {% endfor %}
{% endfor %}\n
"""

[git]
link_parsers = [
    { pattern = "#(\\d+)", href = "https://github.com/orhun/git-cliff/issues/$1"},
]

Pay attention to this line:
{%- if commit.links %} ({% for link in commit.links %}[{{link.text}}]({{link.href}}){% endfor -%}){% endif %}\

This will result in:
## [0.6.0] - 2022-02-12

### Bug Fixes

- Only drop previous releases if skipped (#44) ([#44](https://github.com/orhun/git-cliff/issues/44))

I think you were expecting link_parsers to do something different. Let me know if there is another thing that I can help you with! 🐻