Uintah updates

Merge of Uintah updates from develop to the 3.0RC

I think this merge isn’t correct. It looks like you are picking up all the changes from develop. You need to pick up just the changes you made. Are you trying to get the 3 changed files from #3736, from earlier today?
From: ARSanderson<EMAIL_ADDRESS>Sent: Wednesday, August 7, 2019 1:44 PM
To: visit-dav/visit<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [visit-dav/visit] Uintah updates (#3740)
Merge of Uintah updates from develop to the 3.0RC

You can view, comment on, or merge this pull request online at:
https://github.com/visit-dav/visit/pull/3740
Commit Summary

Fix warning _GNU_SOURCE multiple definitions. (#3502)
2019 05 build visit tweaks for 3.0.1 (#3508)
Disable C-spec from cinema code until it is fixed. (#3516)
Make setting of BelowMin/AboveMax color conditional (#3517)
blueprint plugin: bugfix for reading sidre group children (#3518)
Task/maguire7/2019 01 mili plugin rewrite 3.0 rc (#3512)
Allow cell-centered data for coloring/scaling glyphs. (#3536)
Feature/rusu1/rc/visit 3324 reverse cli docs generation mechanism (#3553)
Modified the LLNL customlauncher for launching on Sierra type systems. (#3560)
Merge of Dave Pugmire's adios2 changes from develop to 3.0RC. (#3561)
Backport 3.0.1 fixes from develop to 3.0RC
sync with 3.0RC
Fix --alt-adios2-dir option of build_visit script (#3506) (#3563)
Update Expression::GetTypeString returned string.
Fake commit
Revert "Fake commit"
Update release notes.
Merge branch '3.0RC' into bugfix/biagas/fix_expressions_window_30RC
Restored removed functions (#3569)
Merge branch '3.0RC' into bugfix/biagas/fix_expressions_window_30RC
Fixed glyphed points getting wrong color when transparency turned on. (#3570)
Resolve merge conflict.
Merge branch '3.0RC' into bugfix/biagas/fix_expressions_window_30RC
Merge branch 'bugfix/biagas/fix_expressions_window_30RC' into 3.0RC
Modify several files for 3.0.1 release. (#3575)
A couple of ADIOS2 changes to build_visit and building ADIOS2 on several LLNL systems. (#3578)
Update the binary translation files for the GUI. (#3582)
Task/maguire7/2019 06 known volume rendering differences (#3587)
remove obsolete redmine tools (#3595)
Increased number of characters allowed in names in XDMF reader. (#3598)
Add host profiles for the LLNL cmax system. (#3600)
Removed lfsconfig file (#3568)
Update patch for vtkOpenGLSphereMapper to correct crash when (#3593)
removing duplicate test (#3610)
Bugfix/maguire7/chgcar volume rendering test failures (#3609)
Bugfix/maguire7/chgcar volume rendering test failures (#3612)
Resolves 3484. Added the QT_XCB_NATIVE_PAINTING env var.
Merge pull request #3617 from visit-dav/griffin28/toolbar_fix
Added additional comments on why the QT_XCB_NATIVE_PAINTING env var was
Merge pull request #3618 from visit-dav/griffin28/toolbar_fix
rebasing and commenting out zbuffer error handling (#3622)
Add support for cell-scalars in the filters used by Pseudocolor plot's line geometry features. (#3625)
Update the date on the splash screen to July, 2019. (#3627)
Update release notes with adios2 changes. (#3589) (#3630)
Cleaned up the 3.0.1 release notes. (#3632)
Update the regression suite to git lfs pull the test baselines. (#3635)
Updates for building and running on Cori. (#3624)
Enable launch of single-processor parallel engines (#3629)
Removed the CCM reader. (#3640)
Remove CCM reference from quartz386.cmake. (#3641)
Rebaseline databaseVsInstall result from removing CCM. (#3643)
Modify FindADIOS2 to handle ADIOS2 libraries installed in lib64. (#3646)
resolving repeat shared vars (#3651)
Corrected ADIOS2 issues with running it from a distribution. (#3654)
Update the 3.0.1 release notes. (#3657)
Correct a typo spelling Fortran in bv_adios2.sh. (#3663)
Task/brugger1/2019 06 20 web site update (#3666)
Updated several config site files for 3.0.1. (#3668)
Correct some ADIOS2 reader compile errors for Sierra like systems. (#3671)
Update several config site files for 3.0.1. (#3673)
Update several config site files for 3.0.1. (#3676)
check file before reading (#3662)
Changes for building 3.0.1 on trinity. (#3692)
Port VisIt to Summit. (#3703)
Have vertex normals filter not process datasets containing triangle strips. Resolves #3698 (#3710)
adding ospray patch from Johannes Guenther (#3701)
Remove IDX from lassen, rzansel and sierra config site files. (#3715)
Remove shortname (8dot3name) reliance. (#3717)
sci notation safety (#3723)
Docs/rusu1/visit 3705 awkward tables in gui doc (#3729)
Update zlib version to 1.2.11. (#3734)
merge from develop

File Changes

D .lfsconfighttps://github.com/visit-dav/visit/pull/3740/files#diff-0 (2)
M data/mili_test_data.7zhttps://github.com/visit-dav/visit/pull/3740/files#diff-1 (4)
D data/mili_test_data2.7zhttps://github.com/visit-dav/visit/pull/3740/files#diff-2 (3)
M docs/WebSite/pages/visit.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-3 (6)
M docs/WebSite/pages/visit/executables.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-4 (52)
M docs/WebSite/pages/visit/new.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-5 (28)
M docs/WebSite/pages/visit/releases.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-6 (8)
A docs/WebSite/pages/visit/releases/release-notes-3.0.1.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-7 (68)
M docs/WebSite/pages/visit/source.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-8 (24)
A scripts/git-hooks/check_cli_doc.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-9 (67)
M scripts/git-hooks/pre-commithttps://github.com/visit-dav/visit/pull/3740/files#diff-10 (3)
M src/CMake/FindADIOS2.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-11 (20)
D src/CMake/FindCCMIO.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-12 (48)
M src/CMake/FindOSPRay.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-13 (40)
M src/CMake/PluginVsInstall.cmake.inhttps://github.com/visit-dav/visit/pull/3740/files#diff-14 (7)
M src/CMake/SetUpThirdParty.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-15 (18)
M src/CMake/ThirdPartyInstallLibrary.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-16 (4)
M src/CMakeLists.txthttps://github.com/visit-dav/visit/pull/3740/files#diff-17 (11)
M src/INSTALL_NOTEShttps://github.com/visit-dav/visit/pull/3740/files#diff-18 (18)
M src/VERSIONhttps://github.com/visit-dav/visit/pull/3740/files#diff-19 (2)
M src/avt/Database/Formats/avtFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-20 (45)
M src/avt/Database/Formats/avtFileFormat.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-21 (8)
M src/avt/Expressions/General/avtZoneTypeLabelExpression.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-22 (13)
M src/avt/Filters/avtLineoutFilter.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-23 (2)
M src/avt/Filters/avtMassVoxelExtractor.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-24 (52)
M src/avt/Filters/avtOSPRayRayTracer.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-25 (6)
M src/avt/Filters/avtPolylineAddEndPointsFilter.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-26 (57)
M src/avt/Filters/avtPolylineCleanupFilter.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-27 (23)
M src/avt/Filters/avtPolylineToRibbonFilter.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-28 (80)
M src/avt/Filters/avtPolylineToTubeFilter.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-29 (95)
M src/avt/Filters/avtValueImageCompositer.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-30 (10)
M src/avt/Filters/avtVertexNormalsFilter.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-31 (23)
M src/avt/Filters/avtWholeImageCompositerWithZ.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-32 (12)
M src/avt/Pipeline/Data/avtCommonDataFunctions.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-33 (88)
M src/avt/Pipeline/Data/avtCommonDataFunctions.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-34 (27)
M src/avt/Pipeline/Data/avtCompositeRF.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-35 (72)
M src/avt/Pipeline/Data/avtCompositeRF.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-36 (6)
M src/avt/Plotter/avtVariableLegend.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-37 (37)
M src/avt/Plotter/avtVariableLegend.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-38 (6)
M src/avt/Plotter/vtk/vtkPointGlyphMapper.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-39 (25)
M src/avt/Queries/Pick/avtPickByNodeQuery.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-40 (6)
M src/avt/VisWindow/Colleagues/VisWinRendering.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-41 (35)
M src/bin/CMakeLists.txthttps://github.com/visit-dav/visit/pull/3740/files#diff-42 (2)
M src/bin/internallauncherhttps://github.com/visit-dav/visit/pull/3740/files#diff-43 (14)
D src/bin/makemilihttps://github.com/visit-dav/visit/pull/3740/files#diff-44 (1)
A src/bin/makemili_driverhttps://github.com/visit-dav/visit/pull/3740/files#diff-45 (0)
M src/bin/visit.chttps://github.com/visit-dav/visit/pull/3740/files#diff-46 (103)
M src/bin/visitcinema.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-47 (64)
M src/common/state/Expression.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-48 (16)
M src/common/state/Expression.codehttps://github.com/visit-dav/visit/pull/3740/files#diff-49 (16)
M src/config-site/ash1.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-50 (5)
M src/config-site/beetlehunter.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-51 (5)
M src/config-site/borax5.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-52 (5)
M src/config-site/carver.nersc.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-53 (5)
M src/config-site/convertconfigs.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-54 (2)
M src/config-site/cooleylogin2.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-55 (47)
D src/config-site/cori.nersc.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-56 (162)
D src/config-site/cori.shared.gcc.4.9.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-57 (102)
A src/config-site/cori08.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-58 (271)
M src/config-site/coruscant.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-59 (5)
M src/config-site/cyclonus.llnl.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-60 (5)
D src/config-site/edison.nersc.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-61 (178)
M src/config-site/ember1.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-62 (5)
M src/config-site/ferment.sci.utah.edu.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-63 (5)
M src/config-site/floyd.llnl.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-64 (5)
M src/config-site/ifyou.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-65 (5)
M src/config-site/ion.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-66 (5)
M src/config-site/ironhide.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-67 (5)
M src/config-site/jade188.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-68 (23)
M src/config-site/kickit.llnl.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-69 (25)
M src/config-site/lassen708.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-70 (24)
A src/config-site/login1.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-71 (217)
M src/config-site/optimusprime.local.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-72 (5)
M src/config-site/quartz1922.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-73 (5)
M src/config-site/quartz386.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-74 (23)
M src/config-site/rhea.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-75 (5)
M src/config-site/rzansel61.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-76 (22)
M src/config-site/rztopaz194.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-77 (23)
M src/config-site/scratlantis.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-78 (5)
M src/config-site/sierra4358.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-79 (24)
M src/config-site/spencer.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-80 (5)
M src/config-site/thembisa.llnl.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-81 (5)
M src/config-site/tr-fe1.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-82 (172)
M src/config-site/ubuntu1104-64.sqalab-llnl.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-83 (5)
M src/config-site/ubuntu1404-64.sqalab-llnl.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-84 (5)
M src/config-site/updraft1.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-85 (5)
M src/config-site/warpath.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-86 (5)
M src/config-site/whoopingcough.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-87 (31)
M src/config-site/windows.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-88 (5)
M src/config-site/winnipeg.llnl.gov.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-89 (25)
M src/config-site/wortchiller.sci.utah.edu.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-90 (28)
M src/config-site/zin497.cmakehttps://github.com/visit-dav/visit/pull/3740/files#diff-91 (5)
M src/databases/ADIOS2/ADIOS2.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-92 (19)
A src/databases/ADIOS2/ADIOS2HelperFuncs.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-93 (31)
A src/databases/ADIOS2/ADIOS2HelperFuncs.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-94 (11)
M src/databases/ADIOS2/ADIOS2PluginInfo.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-95 (5)
M src/databases/ADIOS2/CMakeLists.txthttps://github.com/visit-dav/visit/pull/3740/files#diff-96 (20)
M src/databases/ADIOS2/avtADIOS2BaseFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-97 (407)
M src/databases/ADIOS2/avtADIOS2BaseFileFormat.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-98 (80)
M src/databases/ADIOS2/avtADIOS2FileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-99 (118)
M src/databases/ADIOS2/avtADIOS2SSTFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-100 (2)
M src/databases/ADIOS2/avtGTCFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-101 (103)
M src/databases/ADIOS2/avtGTCFileFormat.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-102 (21)
M src/databases/ADIOS2/avtLAMMPSFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-103 (106)
M src/databases/ADIOS2/avtLAMMPSFileFormat.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-104 (26)
M src/databases/ADIOS2/avtMEUMMAPSFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-105 (86)
M src/databases/ADIOS2/avtMEUMMAPSFileFormat.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-106 (20)
A src/databases/ADIOS2/avtSpecFEMFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-107 (1979)
A src/databases/ADIOS2/avtSpecFEMFileFormat.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-108 (145)
A src/databases/ADIOS2/platePoints.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-109 (1580)
M src/databases/Blueprint/avtBlueprintTreeCache.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-110 (7)
D src/databases/CCM/CCM.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-111 (17)
D src/databases/CCM/CCMCommonPluginInfo.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-112 (89)
D src/databases/CCM/CCMEnginePluginInfo.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-113 (60)
D src/databases/CCM/CCMMDServerPluginInfo.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-114 (47)
D src/databases/CCM/CCMPluginInfo.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-115 (193)
D src/databases/CCM/CCMPluginInfo.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-116 (100)
D src/databases/CCM/CMakeLists.txthttps://github.com/visit-dav/visit/pull/3740/files#diff-117 (81)
D src/databases/CCM/PolygonToTriangles.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-118 (2)
D src/databases/CCM/avtCCMFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-119 (2978)
D src/databases/CCM/avtCCMFileFormat.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-120 (223)
M src/databases/CMakeLists.txthttps://github.com/visit-dav/visit/pull/3740/files#diff-121 (5)
M src/databases/Mili/CMakeLists.txthttps://github.com/visit-dav/visit/pull/3740/files#diff-122 (3)
M src/databases/Mili/Mili.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-123 (13)
M src/databases/Mili/MiliCommonPluginInfo.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-124 (16)
M src/databases/Mili/MiliPluginInfo.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-125 (1)
M src/databases/Mili/avtMiliFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-126 (6888)
M src/databases/Mili/avtMiliFileFormat.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-127 (445)
A src/databases/Mili/avtMiliMetaData.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-128 (3151)
A src/databases/Mili/avtMiliMetaData.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-129 (644)
M src/databases/Uintah/avtUintahFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-130 (48)
M src/databases/VisItXdmf/avtVisItXdmfFileFormat.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-131 (27)
M src/databases/VisItXdmf/avtVisItXdmfFileFormat.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-132 (6)
M src/databases/paraDIS/RC_cpp_lib/RC_c_lib/gprof-helper.chttps://github.com/visit-dav/visit/pull/3740/files#diff-133 (4)
M src/databases/paraDIS_tecplot/RC_c_lib/gprof-helper.chttps://github.com/visit-dav/visit/pull/3740/files#diff-134 (4)
M src/doc/cli_manual/attributes.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-135 (5263)
M src/doc/cli_manual/events.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-136 (2)
M src/doc/cli_manual/functions.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-137 (3564)
M src/doc/cli_manual/intro.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-138 (4)
D src/doc/cli_manual/preambles/functions_preamblehttps://github.com/visit-dav/visit/pull/3740/files#diff-139 (2)
A src/doc/functions_to_method_doc.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-140 (299)
M src/doc/gui_manual/Animation/Movie_tools.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-141 (98)
M src/doc/gui_manual/Building/Common_Build_Scenarios.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-142 (118)
M src/doc/gui_manual/MakingItPretty/View.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-143 (137)
M src/doc/gui_manual/Quantitative/DataLevelComparisonsWizard.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-144 (10)
M src/doc/gui_manual/Quantitative/Expressions.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-145 (29)
M src/doc/gui_manual/Quantitative/Query.rsthttps://github.com/visit-dav/visit/pull/3740/files#diff-146 (561)
M src/doc/sphinx_cli_extractor.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-147 (512)
M src/gui/QvisCinemaWizard.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-148 (2)
M src/gui/SplashScreen.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-149 (8)
M src/mdserver/main/MDServerConnection.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-150 (4)
M src/plots/Pseudocolor/Pseudocolor.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-151 (2)
M src/plots/Pseudocolor/PseudocolorAttributes.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-152 (4)
M src/plots/Pseudocolor/avtPseudocolorPlot.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-153 (35)
M src/plots/Surface/Surface.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-154 (2)
M src/plots/Surface/SurfaceAttributes.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-155 (4)
M src/plots/Volume/QvisVolumePlotWindow.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-156 (6)
M src/plots/Volume/avtDefaultRenderer.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-157 (31)
M src/plots/Volume/avtVolumeFilter.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-158 (7)
M src/resources/help/en_US/relnotes2.12.0.htmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-159 (2)
M src/resources/help/en_US/relnotes2.12.1.htmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-160 (6)
M src/resources/help/en_US/relnotes2.12.2.htmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-161 (6)
M src/resources/help/en_US/relnotes2.12.3.htmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-162 (2)
M src/resources/help/en_US/relnotes2.13.0.htmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-163 (4)
M src/resources/help/en_US/relnotes2.13.3.htmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-164 (2)
M src/resources/help/en_US/relnotes3.0.0.htmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-165 (8)
M src/resources/help/en_US/relnotes3.0.1.htmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-166 (22)
A src/resources/help/en_US/relnotes3.0.2.htmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-167 (48)
M src/resources/hosts/llnl/customlauncherhttps://github.com/visit-dav/visit/pull/3740/files#diff-168 (41)
A src/resources/hosts/llnl_closed/host_llnl_closed_cmax.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-169 (108)
M src/resources/hosts/nersc/customlauncherhttps://github.com/visit-dav/visit/pull/3740/files#diff-170 (30)
M src/resources/hosts/ornl/customlauncherhttps://github.com/visit-dav/visit/pull/3740/files#diff-171 (74)
R src/resources/hosts/ornl/host_ornl_summit.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-172 (48)
M src/resources/translations/visit_fr.qmhttps://github.com/visit-dav/visit/pull/3740/files#diff-173 (0)
M src/resources/translations/visit_jp.qmhttps://github.com/visit-dav/visit/pull/3740/files#diff-174 (0)
M src/resources/translations/visit_la-pig.qmhttps://github.com/visit-dav/visit/pull/3740/files#diff-175 (0)
M src/resources/translations/visit_nl.qmhttps://github.com/visit-dav/visit/pull/3740/files#diff-176 (0)
M src/resources/translations/visit_sv-chef.qmhttps://github.com/visit-dav/visit/pull/3740/files#diff-177 (0)
M src/test/tests/databases/mili.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-178 (438)
M src/test/tests/plots/volumePlot.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-179 (42)
M src/test/tests/plugins/databasesVsInstall.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-180 (4)
M src/test/tests/queries/pick.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-181 (55)
M src/test/tests/queries/queriesOverTime.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-182 (15)
A src/third_party_builtin/rapidjson/allocators.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-183 (284)
A src/third_party_builtin/rapidjson/cursorstreamwrapper.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-184 (78)
M src/third_party_builtin/rapidjson/document.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-185 (0)
A src/third_party_builtin/rapidjson/encodedstream.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-186 (0)
A src/third_party_builtin/rapidjson/encodings.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-187 (0)
A src/third_party_builtin/rapidjson/error/en.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-188 (0)
A src/third_party_builtin/rapidjson/error/error.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-189 (0)
A src/third_party_builtin/rapidjson/filereadstream.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-190 (0)
A src/third_party_builtin/rapidjson/filewritestream.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-191 (0)
A src/third_party_builtin/rapidjson/fwd.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-192 (0)
A src/third_party_builtin/rapidjson/internal/biginteger.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-193 (0)
A src/third_party_builtin/rapidjson/internal/diyfp.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-194 (0)
A src/third_party_builtin/rapidjson/internal/dtoa.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-195 (0)
A src/third_party_builtin/rapidjson/internal/ieee754.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-196 (0)
A src/third_party_builtin/rapidjson/internal/itoa.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-197 (0)
A src/third_party_builtin/rapidjson/internal/meta.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-198 (0)
M src/third_party_builtin/rapidjson/internal/pow10.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-199 (0)
A src/third_party_builtin/rapidjson/internal/regex.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-200 (0)
M src/third_party_builtin/rapidjson/internal/stack.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-201 (0)
M src/third_party_builtin/rapidjson/internal/strfunc.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-202 (0)
A src/third_party_builtin/rapidjson/internal/strtod.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-203 (0)
A src/third_party_builtin/rapidjson/internal/swap.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-204 (0)
A src/third_party_builtin/rapidjson/istreamwrapper.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-205 (0)
A src/third_party_builtin/rapidjson/memorybuffer.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-206 (0)
A src/third_party_builtin/rapidjson/memorystream.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-207 (0)
A src/third_party_builtin/rapidjson/msinttypes/inttypes.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-208 (0)
A src/third_party_builtin/rapidjson/msinttypes/stdint.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-209 (0)
A src/third_party_builtin/rapidjson/ostreamwrapper.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-210 (0)
A src/third_party_builtin/rapidjson/pointer.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-211 (0)
M src/third_party_builtin/rapidjson/prettywriter.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-212 (0)
M src/third_party_builtin/rapidjson/rapidjson.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-213 (0)
M src/third_party_builtin/rapidjson/reader.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-214 (0)
A src/third_party_builtin/rapidjson/schema.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-215 (0)
A src/third_party_builtin/rapidjson/stream.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-216 (0)
M src/third_party_builtin/rapidjson/stringbuffer.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-217 (0)
M src/third_party_builtin/rapidjson/writer.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-218 (0)
M src/tools/data/CMakeLists.txthttps://github.com/visit-dav/visit/pull/3740/files#diff-219 (0)
D src/tools/data/makemili/CMakeLists.txthttps://github.com/visit-dav/visit/pull/3740/files#diff-220 (0)
D src/tools/data/makemili/MakeMili.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-221 (0)
M src/tools/dev/masonry/bootstrap_visit.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-222 (0)
M src/tools/dev/masonry/opts/mb-3.0.0b-darwin-10.13-x86_64-release.jsonhttps://github.com/visit-dav/visit/pull/3740/files#diff-223 (0)
D src/tools/dev/redmine/pyrmine/setup.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-224 (0)
D src/tools/dev/redmine/pyrmine/setup_tests.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-225 (0)
D src/tools/dev/redmine/pyrmine/src/Connection.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-226 (0)
D src/tools/dev/redmine/pyrmine/src/Issue.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-227 (0)
D src/tools/dev/redmine/pyrmine/src/init.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-228 (0)
D src/tools/dev/redmine/pyrmine/tests/test_issues.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-229 (0)
D src/tools/dev/redmine/visit_redmine_query_report.pyhttps://github.com/visit-dav/visit/pull/3740/files#diff-230 (0)
M src/tools/dev/scripts/build_visithttps://github.com/visit-dav/visit/pull/3740/files#diff-231 (0)
M src/tools/dev/scripts/bv_support/bv_adios2.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-232 (0)
D src/tools/dev/scripts/bv_support/bv_ccmio.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-233 (0)
M src/tools/dev/scripts/bv_support/bv_conduit.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-234 (0)
M src/tools/dev/scripts/bv_support/bv_embree.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-235 (0)
M src/tools/dev/scripts/bv_support/bv_ispc.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-236 (0)
M src/tools/dev/scripts/bv_support/bv_llvm.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-237 (0)
M src/tools/dev/scripts/bv_support/bv_pidx.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-238 (0)
M src/tools/dev/scripts/bv_support/bv_python.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-239 (0)
M src/tools/dev/scripts/bv_support/bv_qt.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-240 (0)
M src/tools/dev/scripts/bv_support/bv_uintah.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-241 (0)
M src/tools/dev/scripts/bv_support/bv_visit.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-242 (0)
M src/tools/dev/scripts/bv_support/bv_vtk.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-243 (0)
M src/tools/dev/scripts/bv_support/bv_zlib.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-244 (0)
M src/tools/dev/scripts/bv_support/helper_funcs.shhttps://github.com/visit-dav/visit/pull/3740/files#diff-245 (0)
M src/tools/dev/scripts/bv_support/modules.xmlhttps://github.com/visit-dav/visit/pull/3740/files#diff-246 (0)
M src/tools/dev/scripts/regressiontest_pascalhttps://github.com/visit-dav/visit/pull/3740/files#diff-247 (0)
M src/tools/dev/scripts/visit-create-chksumshttps://github.com/visit-dav/visit/pull/3740/files#diff-248 (0)
M src/tools/third_party/qtssh/unix/uxpeer.chttps://github.com/visit-dav/visit/pull/3740/files#diff-249 (0)
M src/visit_vtk/full/vtkVisItGlyph3D.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-250 (0)
M src/visitpy/common/MethodDoc.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-251 (0)
M src/visitpy/common/MethodDoc.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-252 (0)
M src/visitpy/common/visitmodule.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-253 (0)
M src/winutil/VariableMenuPopulator.Chttps://github.com/visit-dav/visit/pull/3740/files#diff-254 (0)
M src/winutil/VariableMenuPopulator.hhttps://github.com/visit-dav/visit/pull/3740/files#diff-255 (0)
M test/baseline/databases/chgcar/chgcar_09.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-256 (0)
M test/baseline/databases/chgcar/chgcar_10.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-257 (0)
D test/baseline/databases/mili/mili_01.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-258 (0)
D test/baseline/databases/mili/mili_02.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-259 (0)
D test/baseline/databases/mili/mili_03.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-260 (0)
D test/baseline/databases/mili/mili_04.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-261 (0)
D test/baseline/databases/mili/mili_05.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-262 (0)
D test/baseline/databases/mili/mili_06.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-263 (0)
D test/baseline/databases/mili/mili_07.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-264 (0)
D test/baseline/databases/mili/mili_08.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-265 (0)
D test/baseline/databases/mili/mili_09.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-266 (0)
D test/baseline/databases/mili/mili_10.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-267 (0)
D test/baseline/databases/mili/mili_11.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-268 (0)
D test/baseline/databases/mili/mili_12.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-269 (0)
D test/baseline/databases/mili/mili_13.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-270 (0)
D test/baseline/databases/mili/mili_14.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-271 (0)
D test/baseline/databases/mili/mili_15.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-272 (0)
D test/baseline/databases/mili/mili_16.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-273 (0)
D test/baseline/databases/mili/mili_17.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-274 (0)
D test/baseline/databases/mili/mili_18.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-275 (0)
D test/baseline/databases/mili/mili_19.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-276 (0)
D test/baseline/databases/mili/mili_20.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-277 (0)
D test/baseline/databases/mili/mili_21.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-278 (0)
D test/baseline/databases/mili/mili_22.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-279 (0)
D test/baseline/databases/mili/mili_23.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-280 (0)
D test/baseline/databases/mili/mili_24.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-281 (0)
D test/baseline/databases/mili/mili_25.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-282 (0)
D test/baseline/databases/mili/mili_26.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-283 (0)
D test/baseline/databases/mili/mili_27.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-284 (0)
D test/baseline/databases/mili/mili_28.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-285 (0)
D test/baseline/databases/mili/mili_29.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-286 (0)
D test/baseline/databases/mili/mili_30.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-287 (0)
D test/baseline/databases/mili/mili_31.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-288 (0)
D test/baseline/databases/mili/mili_32.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-289 (0)
D test/baseline/databases/mili/mili_33.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-290 (0)
D test/baseline/databases/mili/mili_34.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-291 (0)
A test/baseline/databases/mili/mili_beam_comp.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-292 (0)
A test/baseline/databases/mili/mili_brick_comp.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-293 (0)
A test/baseline/databases/mili/mili_from_sci_not.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-294 (0)
A test/baseline/databases/mili/mili_mat_var_01.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-295 (0)
A test/baseline/databases/mili/mili_mat_var_02.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-296 (0)
A test/baseline/databases/mili/mili_materials_00.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-297 (0)
A test/baseline/databases/mili/mili_materials_01.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-298 (0)
A test/baseline/databases/mili/mili_multi_dom_01.pnghttps://github.com/visit-dav/visit/pull/3740/files#diff-299 (0)

Patch Links:

https://github.com/visit-dav/visit/pull/3740.patch
https://github.com/visit-dav/visit/pull/3740.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/visit-dav/visit/pull/3740?email_source=notifications&email_token=AAING7WXDJWW47SXB4LE4ITQDMXYPA5CNFSM4IKEDOSKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HD7WJ7A, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAING7UVBQUJSH4EQZNVSRLQDMXYPANCNFSM4IKEDOSA.

Yes that is correct.  I create the branch after checking out the 3.0RC. So I thought my may branch would be reflective of it. Perhaps my push was not correct???

I just created a new pull request with you as a reviewer that has just those 3 files you changed. You can review and approve them if they are correct and then delete this pull request.
From: ARSanderson<EMAIL_ADDRESS>Sent: Wednesday, August 7, 2019 1:55 PM
To: visit-dav/visit<EMAIL_ADDRESS>Cc: Brugger, Eric<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [visit-dav/visit] Uintah updates (#3740)
Yes that is correct. I create the branch after checking out the 3.0RC. So I thought my may branch would be reflective of it. Perhaps my push was not correct???
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/visit-dav/visit/pull/3740?email_source=notifications&email_token=AAING7XT4P77W45QZPJTBQDQDMZDDA5CNFSM4IKEDOSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3ZVZBI#issuecomment-519265413, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAING7XZ5SYT3SVXUBJU5NDQDMZDDANCNFSM4IKEDOSA.

I seemed to have pooched this and Eric has bailed me out so I am closing the request.


fatal error LNK1181: cannot open input file 'kernel32.lib'

Hi. I'm trying to install bcrypt on my Windows 7 machine. I've installed all dependencies from the manual. But when I do:
>  npm install bcrypt

I'm getting the error message: fatal error LNK1181: cannot open input file 'kernel32.lib'
Help please.

Hi guys,
I am facing the same issue: LINK : fatal error LNK1181: cannot open input file 'kernel32.lib' [D:\conduco-d
evelop\conduco-develop\node_modules\zombie\node_modules\jsdom\node_modules\cont
extify\build\contextify.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: C:\windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe  failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules
npm\node_modules\node-gyp\lib\build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:807:
12)
Please help me to resolve this issue. Thanks in advance


How can you clear the cache of the exllamav2?

I am loading 2 7 B models. The cache problem only occurs when I use autosplit to load these models. The first model prediction works fine, but when I ask subsequent questions, it keeps returning the previous response to every subsequent request/question.
Issue:
When the model caches the response, the subsequent request doesn't clear the cache and the model returns the previous responses to all the next questions.
Question:
How do you clear the cache after every request to model?
Code:
Model 1:
  model_directory =  "./TheBloke_Genz-70b-GPTQ"

  config = ExLlamaV2Config()
  config.model_dir = model_directory
  config.prepare()
  model = ExLlamaV2(config)
  model.load([1,5,20,17])
  tokenizer = ExLlamaV2Tokenizer(config)
  cache = ExLlamaV2Cache(model)
  generator = ExLlamaV2StreamingGenerator(model, cache, tokenizer)
  inferencer = ExLlamaV2BaseGenerator(model, cache, tokenizer)

Model 2:
  model_directory = "./TheBloke_dolphin-2.2.1-mistral-7B-GPTQ"

  config2 = ExLlamaV2Config()
  config2.model_dir = model_directory
  config2.prepare()
  model2 = ExLlamaV2(config2)
  cache2 = ExLlamaV2Cache(model2, lazy = True)
  model2.load_autosplit(cache2)
  tokenizer2 = ExLlamaV2Tokenizer(config2)
  generator2 = ExLlamaV2BaseGenerator(model2, cache2, tokenizer2)
  streamer2 = ExLlamaV2StreamingGenerator(model2, cache2, tokenizer2)

@turboderp  Any suggestions?

Could you share the code that calls the generator functions? The problem is likely with those rather than with how the models are loaded.


fix a bug that the search bar can not work in react native 0.9.0

I found the search-bar cannot work in React Native 0.9.0, as in the issue:
https://github.com/umhan35/react-native-search-bar/issues/15
Inspired by RCTTextField.m, I modified RNSearchBar.m to make it able to work.
Then I realized that it may not work under 0.9.0, hence I changed the package.json.

Thank you @chengs . I was just thinking to see how RCTTextField.m works. I tried yours and it works.
I'll just give one comment for the version you modified. I changed to ^0 earlier because npm will download another copy of react native (rn) of the version specified (for now 0.9) after your change. I found ^0 basically means using whatever version of rn along with react-native-search-bar. It's been discussed in issue #3.
I'll try merge RNSearchBar.m only for now. Feel free to discuss with me. :)

Just merged RNSearchBar.m only.

OK. I close this request.


How to pass output of a keras model as input of other model

I am trying to use the output of one keras model as the input of another model. As the output is type Tensor, it can not be used in model.predict() method as it wants numpy array
How can i do this

You'll probably get a cleaner answer on StackOverflow as this is not a Keras issue/bug related question. In short, models are like any other layer but with added loss and optimiser. You can use the first model like a layer when building the second one. There are examples in the functional API documentation, the shared vision model for example. Hope that helps.

@nuric in my case it gives an error like this.
ValueError: The shape of the input to "Flatten" is not fully defined (got (None, None, 736). Make sure to pass a complete "input_shape" or "batch_input_shape" argument to the first layer in your model
I am trying to use a pre-trained model as a loss function.
nn4_small2_pretrained = create_model()
nn4_small2_pretrained.trainable = False
nn4_small2_pretrained.load_weights('weights/nn4.small2.v1.h5')
def face_recognition_loss(img, pred):
return K.sum(K.square(nn4_small2_pretrained(img) - nn4_small2_pretrained(pred)))

You'll probably get a cleaner answer on StackOverflow as this is not a Keras issue/bug related question. In short, models are like any other layer but with added loss and optimiser. You can use the first model like a layer when building the second one. There are examples in the functional API documentation, the shared vision model for example. Hope that helps.

There is no documentation that says "Models are layers with added loss and optimiser." explicitly. Is this inferred knowledge ?


Full working example?

Hi,
i still got problems to run scssphp successfully.
Is there anywhere a full working example to download?
This would help to find out failures by myself.
Thx.

Refer to the docs and try one of the simpler examples to test your integration with this library.
http://leafo.github.io/scssphp/docs/
Alternatively, use a wrapper like assetic.
https://github.com/kriswallsmith/assetic


Support with quectel m95 gprs module

is it possible to implement websocket in arduino mega with a gprs module as internet provider?

Sorry, i don't plan to support GPRS modules.


Crashing While saving/ loading in builds

---- Minecraft Crash Report ----
// I bet Cylons wouldn't have this problem.
Time: 18/04/16 15:41
Description: Updating screen events
java.lang.NoSuchMethodError: net.minecraftforge.fml.common.registry.FMLControlledNamespacedRegistry.getObject(Lnet/minecraft/util/ResourceLocation;)Ljava/lang/Object;
at com.github.lunatrius.schematica.world.schematic.SchematicUtil.getIconFromName(SchematicUtil.java:52)
at com.github.lunatrius.schematica.proxy.CommonProxy.saveSchematic(CommonProxy.java:188)
at com.github.lunatrius.schematica.client.gui.save.GuiSchematicSave.func_146284_a(GuiSchematicSave.java:157)
at net.minecraft.client.gui.GuiScreen.func_73864_a(GuiScreen.java:452)
at com.github.lunatrius.core.client.gui.GuiScreenBase.func_73864_a(GuiScreenBase.java:44)
at net.minecraft.client.gui.GuiScreen.func_146274_d(GuiScreen.java:540)
at net.minecraft.client.gui.GuiScreen.func_146269_k(GuiScreen.java:509)
at net.minecraft.client.Minecraft.func_71407_l(Minecraft.java:1694)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:1051)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:366)
at net.minecraft.client.main.Main.main(SourceFile:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:
-- Head --
Stacktrace:
at com.github.lunatrius.schematica.world.schematic.SchematicUtil.getIconFromName(SchematicUtil.java:52)
at com.github.lunatrius.schematica.proxy.CommonProxy.saveSchematic(CommonProxy.java:188)
at com.github.lunatrius.schematica.client.gui.save.GuiSchematicSave.func_146284_a(GuiSchematicSave.java:157)
at net.minecraft.client.gui.GuiScreen.func_73864_a(GuiScreen.java:452)
at com.github.lunatrius.core.client.gui.GuiScreenBase.func_73864_a(GuiScreenBase.java:44)
at net.minecraft.client.gui.GuiScreen.func_146274_d(GuiScreen.java:540)
at net.minecraft.client.gui.GuiScreen.func_146269_k(GuiScreen.java:509)
-- Affected screen --
Details:
Screen name: com.github.lunatrius.schematica.client.gui.save.GuiSchematicSave
-- Affected level --
Details:
Level name: MpServer
All players: 1 total; [EntityPlayerSP['GalaxyCloud'/308, l='MpServer', x=-245.35, y=64.00, z=83.25]]
Chunk stats: MultiplayerChunkCache: 49, 49
Level seed: 0
Level generator: ID 00 - default, ver 1. Features enabled: false
Level generator options:
Level spawn location: World: (-248,64,144), Chunk: (at 8,4,0 in -16,9; contains blocks -256,0,144 to -241,255,159), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Level time: 572 game time, 572 day time
Level dimension: 0
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: false
Forced entities: 1 total; [EntityPlayerSP['GalaxyCloud'/308, l='MpServer', x=-245.35, y=64.00, z=83.25]]
Retry entities: 0 total; []
Server brand: fml,forge
Server type: Integrated singleplayer server
Stacktrace:
at net.minecraft.client.multiplayer.WorldClient.func_72914_a(WorldClient.java:409)
at net.minecraft.client.Minecraft.func_71396_d(Minecraft.java:2647)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:387)
at net.minecraft.client.main.Main.main(SourceFile:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
-- System Details --
Details:
Minecraft Version: 1.9
Operating System: Mac OS X (x86_64) version 10.11.3
Java Version: 1.8.0_74, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 394012032 bytes (375 MB) / 756903936 bytes (721 MB) up to<PHONE_NUMBER> bytes (1011 MB)
JVM Flags: 5 total; -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
FML: MCP 9.23 Powered by Forge <IP_ADDRESS>5 5 mods loaded, 5 mods active
States: 'U' = Unloaded 'L' = Loaded 'C' = Constructed 'H' = Pre-initialized 'I' = Initialized 'J' = Post-initialized 'A' = Available 'D' = Disabled 'E' = Errored
UCHIJAAAA	mcp{9.19} [Minecraft Coder Pack] (minecraft.jar)
UCHIJAAAA	FML{<IP_ADDRESS>} [Forge Mod Loader] (forge-1.9-<IP_ADDRESS>5-1.9.jar)
UCHIJAAAA	Forge{<IP_ADDRESS>5} [Minecraft Forge] (forge-1.9-<IP_ADDRESS>5-1.9.jar)
UCHIJAAAA	LunatriusCore{<IP_ADDRESS>} [LunatriusCore] (LunatriusCore-1.9-<IP_ADDRESS>-universal.jar)
UCHIJAAAA	Schematica{<IP_ADDRESS>} [Schematica] (Schematica-1.9-<IP_ADDRESS>-universal.jar)
Loaded coremods (and transformers):
Launched Version: 1.9-forge1.9-<IP_ADDRESS>5-1.9
LWJGL: 2.9.2
OpenGL: ATI Radeon HD 2600 OpenGL Engine GL version 2.1 ATI-10.0.40, ATI Technologies Inc.
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because ARB_framebuffer_object is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.
Using VBOs: Yes
Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Packs:
Current Language: English (US)
Profiler Position: N/A (disabled)
CPU: 8x Intel(R) Xeon(R) CPU E5462 @ 2.80GHz

This is the crash report it gives me whenever i save even a small area or try to load in a building, sorry if I'm being stupid and missing something clear but i am new to this. Thanks

UCHIJAAAA LunatriusCore{<IP_ADDRESS>} LunatriusCore
UCHIJAAAA Schematica{<IP_ADDRESS>} Schematica

Update LunatriusCore and Schematica because this version of Schematica has a problem with versions of Forge newer than 1816. (reported in  #119)

RedNesto, is the updated version of LunatriusCore and Schematica compatible with Mac OS?
Thanks for replying

There are no reasons Schematica and LunatriusCore updates are incompatible with Mac ^^.

Okay thank you, lastly, whats the link to the updated schematic and lunatriuscore, I'm hopeless at this kind of stuff!

Direct download for LunatriusCore: http://minecraft.curseforge.com/projects/lunatriuscore/files/2294062/download
and for Schematica:
http://minecraft.curseforge.com/projects/schematica/files/2294072/download

I can't thank you enough, you've helped a lot!

:3

If it fixes the problem, don't forget to close this issue

Yes it fixes it! Thanks again


Hi can anyone clarify if the level3 test case...?

Summary
Hi can anyone clarify if the level3 test case is supposed to have no output? because shouldnt it show the log of the map occurring?
jshell> five.flatMap(x -> Logger.of(x + 1))
$.. ==> Logger[6]

Based on the test cases, I don't think calling flatMap will return the ? -> ? statement. That will only be for the map function.
For  five.flatMap(x -> Logger.of(x).map(y -> y + 2)). flatMap(y -> Logger.of(y).map(z -> z * 10)), it will have the output since map is being called. But when doing flatMap( x -> logger.of(x)) there shouldnt be the output.

I think flatmap is just there to prevent the existence of Logger of Logger. so it will not update the log

flatMap shouldn't have the log as you're simply wrapping the Logger around the new value. There's also the part where flatMap should be lazily evaluated (see level 5's predicate methods). I didn't observe it enough and had to re-implement almost my entire lab8 after realising i had to use lazy evaluation

flatMap shouldn't have the log as you're simply wrapping the Logger around the new value. There's also the part where flatMap should be lazily evaluated (see level 5's predicate methods). I didn't observe it enough and had to re-implement almost my entire lab8 after realising i had to use lazy evaluation

Does your flatMap have a copy of the log?

btw anyone used suppliers for the log? or did yall just use arraylists

flatMap shouldn't have the log as you're simply wrapping the Logger around the new value. There's also the part where flatMap should be lazily evaluated (see level 5's predicate methods). I didn't observe it enough and had to re-implement almost my entire lab8 after realising i had to use lazy evaluation

Does your flatMap have a copy of the log?

i just made it continue using its own log, but i didnt add anything new to it. With regards to the next qn, instead of using ArrayList, i used a new Pair class which Paired the value with the log.
So something like Pair<T, String>, and have my supplier wrap around this. Supplier<Pair<T, String>>. Then i made the supplier do everything (updating the log and getting the value). in that way everything becomes lazy

btw anyone used suppliers for the log? or did yall just use arraylists

I think it's best to store the logs within a data structure (eg. ArrayList). In my case I used an ArrayList<Supplier<...>>

btw anyone used suppliers for the log? or did yall just use arraylists

For this one, I tried using ArrayList<Supplier> and also ArrayList for the log and both work fine.

flatMap shouldn't have the log as you're simply wrapping the Logger around the new value. There's also the part where flatMap should be lazily evaluated (see level 5's predicate methods). I didn't observe it enough and had to re-implement almost my entire lab8 after realising i had to use lazy evaluation

Does your flatMap have a copy of the log?

For this one, my flatMap will take the current log and also the log from mapper.apply(value)

from what I understand, you basically take the log of five and add it to the log of the lambda function. In this case, Logger.of does not produce any logs, but if the lambda was a logger.of(5).map(x -> x + 1) it would have a log which needs to be combined with the original objects one.

Hi ezeAng,
I think the flatmap here is basically "combining" the value to the Logger behind, such that there is no adding of extra string in its list.
Logger.of(5).flatmap(x -> x + 1) is basically saying that the logger in front will become the new logger at the back
As such, when you implement it, the only things that you need to do are to change the Logger variable value, combine the elements in Logger list (without adding anything new)


docs: add java un/marshalling reference to docs

Description

Added java un/marshalling reference to examples/README.md

@jonaslagoni Kindly review the PR :)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2525

Relevant Lines:
2576

💛  - Coveralls

/rtm


Notifications / Backend Integration Testing

#952
I think that existing scripts written in scripts/firebase-admin/ can be used for end-to-end testing.
Manual testing needs to be done to confirm functioning of deliverNotifications cloud function and its sending of emails and updating of newsfeeds.

Added notificationFrequency and email fields to dev environment via script, added index for nextDIgestAt field, so email testing should be good to go.

#1296 Will need to complete 1296 to spawn events organically, otherwise, will need to run seed scripts to test email function.


Add missing  include

Include header <numeric> for std::accumulate when JSON_DIAGNOSTICS is enabled.
Fixes #3717.
Closes #3718.

Coverage remained the same at 100.0% when pulling af54422c4aae0191e6edc95e9e18c8a2d73bed17 on falbrechtskirchinger:missing-include into bed648ca552258fa7b1d3065c2fa612877fa0918 on nlohmann:develop.


adding batch 7

An explanation regarding the numbering:

batch 5 was bigger than this current batch, so the transcription takes longer and is still in progress in eScriptorium
batch 6 is printed and in the process of being filled by volunteers

Hence batch 7.
Note that batch 7 is a bit special: it was filled by teenagers only (between 11 and 13 years old).

All good for the quality control so I merge


Tag and release new version

We should release the updated debian package to be included into the upcoming image. Mostly because of #288. Do we need to do anything else before that?

When using the develop version I get one issue:
Feb 02 13:35:31 ev3dev openrobertalab[11037]: Traceback (most recent call last):
Feb 02 13:35:31 ev3dev openrobertalab[11037]: File "/usr/lib/python3/dist-packages/roberta/lab.py", line 277, in _exec_code
Feb 02 13:35:31 ev3dev openrobertalab[11037]: exec(compiled_code, scope)
Feb 02 13:35:31 ev3dev openrobertalab[11037]: File "/home/robot/NEPOprog.py", line 36, in <module>
Feb 02 13:35:31 ev3dev openrobertalab[11037]: main()
Feb 02 13:35:31 ev3dev openrobertalab[11037]: File "/home/robot/NEPOprog.py", line 26, in main
Feb 02 13:35:31 ev3dev openrobertalab[11037]: run()
Feb 02 13:35:31 ev3dev openrobertalab[11037]: File "/home/robot/NEPOprog.py", line 21, in run
Feb 02 13:35:31 ev3dev openrobertalab[11037]: hal.driveDistance('C', 'B', False, 'foreward', 30, 20)
Feb 02 13:35:31 ev3dev openrobertalab[11037]: File "/usr/lib/python3/dist-packages/roberta/ev3.py", line 383, in driveDistance
Feb 02 13:35:32 ev3dev openrobertalab[11037]: ml.stop_command = 'brake'
Feb 02 13:35:32 ev3dev openrobertalab[11037]: AttributeError: 'NoneType' object has no attribute 'stop_command'

Here is the related code:
https://github.com/OpenRoberta/robertalab-ev3dev/blob/develop/roberta/ev3.py#L382..L388
This shows that commit
4a85fd2 Error on non-existing arguments/parameters (#278)
is effective and that we did a bad job on communicating all the motor api changes. I'll release another openroberta update.

Main issue why this release is breaking things (and we should communicate this well) is that I added two custom attributes to the motors:
https://github.com/OpenRoberta/robertalab-ev3dev/blob/develop/roberta/ev3.py#L49..L50
and this now causes an exception. Will figure a hotfix, but this is meh :/

You could inherit from motor and add the attributes to the child.

I have pushed fixes. Will also push another release now. Please mention this change in the RELEASE-NOTES though to make sure people are aware of it. Thanks. Everything else looks good. So thumbs up to release.

I'm supportive of a release too. I don't have time do draft release notes ATM but should be able to tomorrow if it hasn't already been done.

I think I'll only have time for this tomorrow anyway.

For reference, here's the diff since our last release: https://github.com/rhempel/ev3dev-lang-python/compare/master...develop

One can also go to releases page and press
the " commits to develop" link there:

That's too much work :wink: I've just learned the URL for GitHub's compare page and typed it in; I used the develop branch while you used the release tag.

Yes. Yes. Yesterday I started using ev3dev-lang-python in classes oriented to high school students. It worked well. 👍  I would like to take advantage of the latest improvements in ev3dev and the openroberta connector. A new updated debian package would be very welcome. Please. :-)

I've tagged 0.8.1 and pushed the packages to the server. I've also created a draft of the release notes here; @WasabiFan, could please check that out?

That looks good; can you note the compatible kernel version and briefly explain the change relating to nonexistent properties? I'm on my phone right now and can't edit the release properly.
Thanks for doing that! I had hoped to find time earlier in the week but evidently failed.

Done.


Consider adding the ability for user to change their own password

iCommands provide iadmin which allows rodsadmins to change any user's password.
iCommands also provide ipasswd which allows non-rodsadmins to change their own password.
Should the HTTP API provide an op that allows a user to change their own password without needing a rodsadmin?
How does this play into password reset UIs built on top of the HTTP API?

And how does this play alongside OIDC, LDAP, where passwords are not stored within iRODS at all?   Do we need to have a per-call, per-user setting that says this is not-allowed?   Or discouraged?

IMO, this is specifically a native authentication thing. I think OIDC, etc are out of scope for this because they are their own thing with facilities for managing credentials.
Keep in mind I've never managed OIDC, LDAP, etc, so my knowledge of that space is very limited.

Yes, if we can scope this to native, then I agree we should be able to open/access/manipulate this functionality via HTTP.
My question is whether the server knows that this particular user should not be allowed to set a password because it should only get accessed via LDAP/OIDC/etc...

Hmm. Have to think about that. Perhaps it's a config file thing?
At the moment, the config file is defined so that multiple auth schemes can be enabled. With that, the HTTP API relies on the Authorization HTTP header to determine which auth scheme logic should run.
Not sure LDAP is mapped to an authorization header value. We can always invent names, but if there's one that is standardized, I'm sure that's what we'd want to try and use.


Update config.sample.yaml

Minor fix for talos folder moved to .... Just updating the comment with new directory for users trying my patch from https://github.com/onedr0p/cluster-template/pull/1320.

Whoops sorry about that!


tcp connection not established

When I'm running the networking example code below it does not establishing a connection.
var messages = require("bitmessage").messages;
var TcpTransport = require("bitmessage-transports").TcpTransport;

var tcp = new TcpTransport({
  dnsSeeds: [["bootstrap8444.bitmessage.org", 8444]],
});

tcp.bootstrap().then(function(nodes) {
  var remoteHost = nodes[0][0];
  var remotePort = nodes[0][1];
  console.log("Connecting to", nodes[0]);
  tcp.connect(remotePort, remoteHost);
});

tcp.on("established", function(version) {
  console.log("Connection established to", version.userAgent);

  tcp.on("message", function(command, payload) {
    console.log("Got new", command, "message");
    var decoded;
    if (command === "addr") {
      decoded = messages.addr.decodePayload(payload);
      console.log("Got", decoded.addrs.length, "node addresses");
    }
  });
});

An initial syn package is sent followed by 6 re-transmissions and than it just sits until it crashes with the output below.
node test_code.js
Connecting to [ '<IP_ADDRESS>', 8444 ]
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: connect ETIMEDOUT
    at exports._errnoException (util.js:746:11)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)

Everything is fine if I'm running the tests for the library, no problem with establishing a tcp connection with localhost. Do you have any idea of why it's not working?
Many thanks.

Sorry for the delay.
Well, the problem is bootstrap seeds return too many dead nodes. There was bitmessage.mobi service which contained alive seeds but now it's unavailable. I suggest you to look at PyBitmessage log and try to connect to recent nodes. Note: PyBitmessage accepts only one connection per IP so you need to either shutdown your PyBitmessage client if it's running and connected to that node or look for some elder node.
I was able to successfully connect to <IP_ADDRESS>:8444 by passing seeds: [["<IP_ADDRESS>", 8444]] option to TcpTransport instead of dnsSeeds but it might be dead when you'll try to connect.

Hi,
Thanks for your reply. It makes more sense to me now. This can be a nasty bug. Do you think it's possible to do a bootstrap connection to a good node. Maybe have a timeout limit in the connection process. If it can't establish a connection within a time frame, drop the connection and try another node from the list generated during the bootstrap.
What's your thought?

Maybe have a timeout limit in the connection process. If it can't establish a connection within a time frame, drop the connection and try another node from the list generated during the bootstrap.

Correct, this is how you should manage connection logic inside your application. But it's high-level logic and bitmessage-transports provides only tiny primitives which allows you to implement this logic by yourself. If you want example of high-level application on top of bitmessage/bitmessage-transports, take a look at bitchan-node.
Have you managed to connect to non-localhost node with bitmessage-transports?

Thanks. You're right. Thanks for the implementation example. Connecting to active nodes works.


TooltipWithBounds rendering sometimes jittery in Firefox with fractional offsets

When non-integer top and left offsets are used for TooltipWithBounds, the tooltip rendering can be jittery in Firefox. If the chart is re-rendering regularly, the tooltip text position may oscillate noticeably. I have observed this to happen in practice when using @data-ui/xy-chart (https://github.com/williaster/data-ui/blob/949f310e19f1858a65a0177eae6b2c5ee419f319/packages/xy-chart/src/enhancer/WithTooltip.jsx#L39 uses localPoint from @vx/event, which can return fractional coordinates in Firefox.)
Codesandbox example based on your existing demo: https://codesandbox.io/s/62xx2jx76r

On Ubuntu Linux, I see an up-down oscillation; on MacOS (Firefox 63.0.3), I see a subtler left-right oscillation.
A simple fix for this issue is to round the values passed to translate (#389).


Remove RHC credentials from the system after registration (HMS-3814)

This PR swaps out the org.osbuild.first-boot stage with an org.osbuild.systemd.unit.create stage that runs the same commands and explicitly adds the rm command for the condition file as the last command.  The file name and service description are changed to describe the purpose of the service.
The stage is functionally identical with the previous one with one main difference: the organisation ID and the activation key are not included in the service file but in a separate environment file in /etc which also acts as the condition file and gets removed after the service runs for the first time.
Not that on ostree-based systems, putting the environment file in /etc prior to building the commit and then rming it on boot means that the file remains in /usr/etc, in the base system, until a system update removes it.

This will need to be rebased once #632 is merged.


in report, include links to failure logs

queued: https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/5113/

https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/5113/artifact/report.log has correct failure URLs for the failed projects, but the browser doesn't render the links; I guess we need to output a report.html instead of a report.log

also the report isn't included anymore at https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/5113/console — need to tee it to stdout I guess

maybe look into https://wiki.jenkins.io/display/JENKINS/HTML+Publisher+Plugin in the future


Drag to scrool whole website

I try like
new ScrollBooster({
    viewport: $('body')[0],
    scrollMode: 'native',
    textSelection: true,
});

But not work, is possible in this lib ?

ok it works

ok it works


[Request] Scripts running during player control

I'm wondering if I can run a script parallel to the player. For example, I want to make a time system, but currently, while that's running, the player cannot move. Is there a way to run a script while the player has control?

I second this request. I have a game that I would like to make that requires a timer system to run in the background, and any implementation on this would be extremely useful.

This would come in handy with animating sprites. But I can that it would put more pressure on the RAM. It's already limited. But the emulator can me make a couple of times stronger then the actual gameboy

This would come in handy with animating sprites. But I can that it would put more pressure on the RAM. It's already limited. But the emulator can me make a couple of times stronger then the actual gameboy

But the goal is for cross-platform support, which means that all games have to be playable on an actual Game Boy.

I know. That's what I meant with my last comment. That the emulator is more powerful than the actual hardware. But flashing it on a GB card and putting it in a actual still working Game boy is expensive. And I think the majority would play it on a emulator running on their pc's or on their RPi's.
But I agree it has to work on a actual Game boy and we won't know if it doesn't work unless we try it.


Update cats-effect, cats-effect-laws, ... to 3.3.0

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws
org.typelevel:cats-effect-testkit

from 3.1.1 to 3.3.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Scalafix Migrations

org.typelevel:{cats-effect,cats-effect-laws}:3.3.0 (created no change)

github:typelevel/cats-effect/v3_3_0?sha=series/3.x

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, early-semver-minor, semver-spec-minor, scalafix-migrations

Codecov Report

Merging #129 (1510ed9) into master (9698733) will increase coverage by 1.21%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #129      +/-   ##
==========================================
+ Coverage   92.68%   93.90%   +1.21%
==========================================
  Files           2        2
  Lines          82       82
==========================================
+ Hits           76       77       +1
+ Misses          6        5       -1

Impacted Files
Coverage Δ

...ala/com/vladkopanev/cats/saga/SagaTransactor.scala
86.84% <0.00%> (+2.63%)
:arrow_up:

Continue to review full report at Codecov.

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


CNF-14656: CNF-14653: ClusterRequest to ProvisioningRequest and make it cluster scoped

Rename ClusterRequest to ProvisioningRequest
Make ProvisioningRequest cluster coped

/lgtm

Now that ProvisioningRequest is cluster-scoped, shouldn't we have templateNamespace field?
spec:
	templateRef:
	    name: clustertemplate-a
	    version: v1
	    namespace: cluster-templates-a-4.16

Now that ProvisioningRequest is cluster-scoped, shouldn't we have templateNamespace field?
spec:
	templateRef:
	    name: clustertemplate-a
	    version: v1
	    namespace: cluster-templates-a-4.16

@sudomakeinstall2 , no, unfortunately. The current direction of the ORAN provisioning spec is to not include the namespace of the ClusterTemplate. The provisioning controller will choose the first valid ClusterTemplate with the specified name/version. The clusterTemplate controller will make sure to only allow unique ClusterTemplate names across the cluster. See @edcdavid 's latest PR.

/lgtm

The provisioning controller will choose the first valid ClusterTemplate with the specified name/version.

Can you clarify "first"? We plan to sort them by namespace or creation time or some combination of different things?

/lgtm

/lgtm

/approve


how to stop preventDefault？

how to use it with stop preventDefault？

It has been a while since i worked on this ( and i mainly just fixed a few things to make it work in vue 3
Just to I better understand, do you want to prevent the keyboard combination to be sent to the element with focus ?

When I use it, it triggers the browser default event, just like pressing F5 will refresh the page. I want to prevent it from refreshing the page

Thanks

I use vue2

I see the original repo is update for vue3 support as well. But either way, you could try asking there https://github.com/fgr-araujo/vue-shortkey

Thanks


Consecutive actions within short amount of time fail on multiple types of Nuki devices

PROBLEM DESCRIPTION
Not sure if that's a 9.0 problem or it was couple of releases before, but I've noticed my door won't open as fast as before.
When i trigger open action on the opener, first one is successful every time. My buzzer duration is usually about 6 seconds. So if i try to open again, also after 6 seconds, the request will fail with 4 retries. Then in about 30 seconds i can try again and it will work again. But not sooner.
I've tried updating opener to latest firmware, nuki hub to 9.01, but same behavior. Haven't tried to roll back to 8 though, but if that helps with debugging, i can do it.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

[x] Read the Contributing Guide and Policy and the Code of Conduct
[x] Searched the problem in issues
[x] Searched the problem in discussions
[x] Searched the problem in the docs
[x] Searched the problem in the chat
[x] Device used (e.g., ESP32-S3): ESP32 Dev Kit
[x] Nuki Hub binary firmware version number used: 9.01

[x] Pre-compiled
[ ] Self-compiled

[x] Provide the output of http://nukihubIP/info:

System Information
------------ NUKI HUB ------------
Version: 9.01
Build:<PHONE_NUMBER>1.2.1
Build type: Release
Build date: 2024-10-15
Updater version: 9.01
Updater build:<PHONE_NUMBER>1.2.1
Updater build date: 2024-10-13
Uptime (min): 963
Config version: 901
Last restart reason FW: RequestedViaWebServer
Last restart reason ESP: ESP_RST_SW: Software reset via esp_restart.
 Open again. Try multiple times.
EXPECTED BEHAVIOUR
Lock should be opened second+ time and not fail.
SCREENSHOTS

ADDITIONAL CONTEXT
First call (starts at 4:28:16) is ok, second one fails (starts at 4:28:52).
Logs:
4:28:53 Opener: Maximum number of retries exceeded, aborting.
4:28:52 Opener: Last command failed, retrying after 100 milliseconds. Retry 4 of 3 4:28:52 Opener action result: error
4:28:52 Opener: Last command failed, retrying after 100 milliseconds. Retry 3 of 3 4:28:52 Opener action result: error
4:28:52 Opener: Last command failed, retrying after 100 milliseconds. Retry 2 of 3 4:28:52 Opener action result: error
4:28:52 Opener: Last command failed, retrying after 100 milliseconds. Retry 1 of 3 4:28:52 Result (attempt 2): Result (attempt 3): Result (attempt 4): Opener action result: error
4:28:52 Result (attempt 1): Opener action received: electricStrikeActuation
4:28:22 Opener action result: success
4:28:16 Opener action received: electricStrikeActuation

(Please, remember to close the issue when the problem has been addressed)

PR #508 and https://github.com/I-Connect/NukiBleEsp32/pull/77 have some changes that might be able to fix this. Preliminary testing shows commands to no issues sending multiple consecutive commands in short order.

PR's have been merged.
I can't reproduce this issue anymore in 9.02-master9 on a Nuki Lock 4.0 (Pro) and Nuki Opener
Please try 9.02-master9 or 9.02-beta2 or the final release of 9.02 (beta and final not released yet)

Thanks, that works now blazing fast and if i don't make it in 6 seconds to the door, i can trigger it after 4 seconds again for another electric strike.
p.s. I was building via docker for about an hour... and then realized the master9 must mean something and remembered that updater allows development updations now. Oh well, at least some tips for someone building on windows via docker, use the // for the paths in build_with_docker_pio.sh and winpty:
winpty docker run --rm -it -v //d/Projects/nuki_hub/Docker/..://src -w //src ${IMAGE_NAME} //bin/bash -c "make deps && make updater && make release"

Confirmed great work @iranl


Change mail icon

Details
Updates the mail icon.
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/164436
Tests / QA Steps (web/desktop)

Hover over a chat.
Verify that the ReportActionContextMenu that appears displays a closed envelope icon instead of an open one.
Hover over the closed envelope icon, and verify that the Tooltip says 'Mark as Unread'
Right-click on a chat.
Verify that the Mark as Unread menu item displays a closed envelope icon.

Tests / QA Steps (iOS/Android/mWeb)

Long-press a chat.
Verify that the Mark as Unread menu item displays a closed envelope icon.

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[ ] Android

Screenshots

Web

Mobile Web
(ignore the highlight bugs that are present on main)

Desktop

iOS

Android

@deetergp I'm going to merge this. I just changed an image asset so there's not much to review here.


[pipeline] make one scan operator able to commit multiple i/o tasks

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Problem Summary：
The small query has too little scan operators, and the bottleneck of small query is at scan i/o task. Therefore, the workgroup with larger cpu_limit cannot get more i/o tasks to execute, which causes there isn't resource isolation between different workgroups for small query.
In this PR, we make one scan operator able to commit at most 4 i/o tasks.
In this way, we increment the concurrency of i/o tasks of a ScanOperator, so maybe we could revert PR #2571
Changes

Make one scan operator able to commit at most 4 i/o tasks.
Revert PR #2571.
Assign range of tablets to the different ScanOperator instances in ScanOperatorFactory::create(), to avoid one ScanOperator consumes all the tablets, which reduces the degree of parallelism.

TODO
This PR assigns each ScanOperator instance with a different range of tablets in BE. In the future, we could assign the range of tablets in FE to eliminate the local shuffle between scan and bucket shuffle join or colocate join.

run starrocks_be_unittest

run starrocks_be_unittest


question 2

Ever thought about adding it a mode where you can edit rivers?

I haven't really thought about adding a rivers map mode to the editor. For my purposes, I've only ever needed MapGen to generate river textures. I'm not very familiar with what makes a river texture valid/invalid either.


Editing dungeon JournalEntry inside TinyMCE converts it to html

This might be easier to address in v9, which I believe allows setting different journal entry sheet types.

I don't think hand-editing the JSON is viable in Foundry, and I'm considering giving up on Journal Entries and just saving the JSON to the scene directly. Marking this issue as Will Not Implement.


Landing Zones management groups design

We are looking for feedback on this proposed change.  We will target this change for December release (v0.6.0). Please share any alternative solutions via comments.
Landing Zones management groups are defined in this reference implementation as DevTest, QA and Prod to create alignment to various environments a customer might have.  These are provided as examples and can be modified by each customer based on their preferred structure.
From Azure Portal:

We are considering to change the management groups from environment focused to data sensitivity focused.
The proposed target definition will enable us to customize Azure Policies (used for guardrails) based on data classification of subscriptions such as Unclassified, Protected A, Protected B, etc..
All subscriptions will be kept in these management groups and we would not add another level to break it out by environments.
Therefore, the change would be:
From current definition
pubsec
 |- Landing Zones
    |- DevTest
    |- QA
    |- Prod
 |- other management groups removed for simplicity

To proposed target definition
pubsec
 |- Landing Zones
    |- Unclassified
    |- Protected A
    |- Protected B
 |- other management groups removed for simplicity

IMO I prefer the current structure.
creating landing zones by sensitivity I think will first all landing zones and workloads to the most restrictive sensitivity
or you'll end up seeing, something like
pubsec
|- Landing Zones
|- Unclassified
|- DevTest
|- Protected A
|- Protected B
|- Prod
|- other management groups removed for simplicity

IMO I prefer the current structure.
creating landing zones by sensitivity I think will first all landing zones and workloads to the most restrictive sensitivity
or you'll end up seeing, something like
pubsec
 |- Landing Zones
    |- Unclassified
        |- DevTest
    |- Protected A
    |- Protected B
        |- Prod
 |- other management groups removed for simplicity

Thanks for the feedback @KingBain.  We don't want to have environments sprawl under each classification since policies/guardrails for all environments will be the same.

I agree with @KingBain; in my experience working mostly with cloud data science projects, most projects would correlate Protected B data and join with unclassified data for feature engineering purposes. Having the top level of the hierarchical start with Dev, Test, Prod makes sense in my opinion as this is a common pattern in public sector.
The curse of multiplication as discussed here: https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/enterprise-scale/faq#what-about-our-management-group-hierarchy doesn't really apply here as the current structure simply breaks down the hierarchical starting with dev, test, prod, etc. but does not suggest branching workloads into dev, test, prod.

I recommend keeping the current approach focused on environments, and the use of tags to identify data sensitivity as one of the attributes for each workload. An application can be unclassified in dev and test, but become PBMM when its in the Production environment when "real" data is stored in the environment. We used the current approach for a new application that was launched and did not run into any issues.

I have no strong opinion either way, however my preferred approach is to treat each environment (dev, test, prod) as identical across the board so that if prod is PB we treat all other environments the same way and they should abide by all the same policies so that environment drift doesn't become a problem.
However we also are unique in that we don't silo off functionality in our organization so if you work on dev or test you also need to manage the prod environment.

Thank you all for the feedback.  Based on the suggestions & on the conversations I've had with CSAs, it's best to stay the course with the current management group structure until there's another suitable path solution.  I'm going to remove it from being our v0.6.0 release (December) but leave the issue open.

I agree with @KingBain; in my experience working mostly with cloud data science projects, most projects correlate Protected B data and join with unclassified data for feature engineering purposes. In addition, having the top level of the hierarchical start with Dev, Test, Prod makes sense in my opinion as this is a common pattern in public sector.
The curse of multiplication as discussed here: https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/enterprise-scale/faq#what-about-our-management-group-hierarchy doesn't really apply here as the current structure simply breaks down the hierarchical starting with dev, test, prod, etc. but does not suggest branching workloads into dev, test, prod.

Have you seen this part of the FAQ article where we talk about how to split subscriptions for workloads? https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/enterprise-scale/faq#how-do-we-handle-devtestproduction-workload-landing-zones-in-enterprise-scale-architecture

I personally feel that Dev, Test, Prod should all match.  Although Dev and Test do not usually have sensitive data, you do not want to wait until production to realize that something you scripted is now blocked by policies.  Good development practice is all your environments should be a mirror of each other.  Most departments will not want to assume all of Production is PBMM so having a classification structure makes more sense to me.  Without it you end up having to apply the PBMM policies at the subscription levels.

Completely agree @nephinj 👍
From a policy perspective what in PBMM would make it restrictive to not wanting to apply to all of the environments and therefore under a single "archetype" management group for simplicity and scale? (apologies but PBMM is not something I have a lot of exposure to)
Maybe @SenthuranSivananthan can assist here also with my understanding to assist?

@jtracey93 in a non-PBMM environment you may not want to restrict locations to Canada only, enforce data encryption at rest, enabling various Defender solutions, enable Azure P2, enable Sentinel, having alternate storage sites, boundary protection, advanced data security, etc....  Some items maybe too restrictive for the use cases or they may just be cost prohibitive to turn on.

Awesome thanks for the reply.
Would it be fair that most of these landing zone subscriptions could be placed under the sandbox?

Microsoft's guidance on Management Group Hierarchy talks about why you should not have dev/test/prod.
@jtracey93 looking back at the policy implementation it is mainly auditing so maybe it would not be as big of deal to just apply it to all environments.

Completely agree and I actually wrote that dev/test/prod guidance for Azure Landing Zones 👍😎
Good to hear you think actually there isn't a difference in policy assignments required between environments now upon review. This is what we see commonly across various customers of all industries and types 👍

Just to twist the conversation a bit, I suspect we're looking at this base layer of mgmt groups from the perspective of developers and the development process lifecycle.
A developer tests in dev, finishes and pushes to QA. QA/Test test approves the request and notifies change mgmt and the code can go into Production, ops pushes into production.
In the original CAF, this lower level of mgmt groups was grouped by workload. There was Online and Corp with makes for a network zoning kind-of archetype. Which is one way of structuring work and honestly I don't know why you moved away from that.
That said, the other way of organizing hierarchies is by Business Function. Like in Enterprise architecture that's how you would do the grouping. Technology doesn't exist by itself, it serves the business, so things get structured around the business function, business user and business processes.
So at that lower layer under landing zones, you'd mgmt. groups by business function.
Production Services
Testing Services
Development services
We're basically aggregate similar workloads by their behaviour, and not by their lifecycle.

I want to add our experience after running Azure for a couple years.

Please note, these are not the real names of the MGs but their function/division

We had started (back before CAF) with almost top level dev/prod split.

Prod where the full PBMM rules / policies / quotas , etc are in place.
Dev was where very little was enforced but cherry picked things. (Also the shared sandbox was also in here)

As we are moving away from shared subs (CAF) we have gone full hub and spoke.
Cloud Ops only maintains the Core of Azure and central services while the Client manages their subscription spokes( typically dev, test/uat/qa, and prod) fully.
Here is the MG structure we are moving to and some details about where the workloads go.
FinOps, Hub, Ops and Security are subscriptions under Core and not management groups
AllSubs is just a substitute for the root tenant.
This is to allow giving, for example, a global RBAC permission (eg. Reader) but without giving access to the actual tenant root.
Major projects:

In DEV; DEV/MAJOR-PROJECT/MAJOR-DIVISION/solution subscription
In PROD; PROD/MAJOR-PROJECT/MAJOR-DIVISION/solution subscription

Minor projects:

In DEV; DEV/project subscription
In PROD; PROD/project subscription

Core projects:

Core Infra projects; (DEV in DEV/core-dev subscription, PROD in CORE/HUB/location subscription or CORE/Ops subscription)
FinOps; DEV in DEV/finops-dev dub, PROD in CORE/FinOps subscription
Security; DEV in DEV/sec-dev sub, PROD in CORE/Sec subscription

Overview

AllSubs
╠Core
║   ╚HUB
╠Dev
║   ╚Major Project
║       ╠Major Division
║       ╚Major Division
║
╠Prod
║   ╚Major Project
║       ╠Major Division
║       ╚Major Division
╚Quarantine

The Quarantine MG is for the default place the subscriptions get made as it is easy for our users to make the mistake of using their work credentials for their VS Subscriber Azure credits benefits.
To handle this, the Quarantine MG would have almost all the ability to deploy resources blocked by policy with messages and information on how to correct their state to get their own tenant.
I am not saying this will work for everyone but this is based off of experience of 2-3 other org's experience.
Hopefully I have explained the 'why' enough to help with this structure discussion!

A slight tweak on the first approach would be to base it on the cloud profiles 1 (experimental), 2 (non-sensitive), 3+(sensitive up to PB).  https://www.gcpedia.gc.ca/gcwiki/images/8/84/GC_Cloud_Guardrails.pdf

Is there an opportunity here to try and change how the management groups are configured in CALZ?
My group renamed all of the mgmt groups(but we kept the basic structure) in CALZ and it ultimately broke the subscription pipelines. We were able to fix it with a work around, but it begs the question. When configuring management groups in CALZ in, why are we setting displayname and name to the same value ?
I dont know how you could impliment it, but I feel it wouldmake it easier for targetting subscription via code and allow humans to have readable mgmt group names.
Usind the screenshot above as the example
I understand why youre doing it...or i think i do; avoiding name collision/reusing mgmt group names
and I think targetting a guid would also make it easier deep in the code where your doing the name concatenation and string splitting

Thanks for raising this @KingBain.  I've created 2 separate GitHub issues to improve this experience:
Please see #167 and #168

Thanks to everyone for the feedback.  We've learned that majority of the structure stays consistent with differences within the child management groups under Landing Zones.  This is based on how each organization operates, organizes their subscriptions and prefers to apply Azure Policies.
Therefore, instead of trying to fit all organization into a single structure, we will be updating our automation so that management group structure can be configured through configuration.  This will allow for:

Flexible management group hierarchy
Flexible management group ids & display names

As a result, you will be able to design your management group hierarchy any way you prefer as long as you limit the depth to 6.  See constraints in Azure Docs.  This means, the structure can:

Follow the recommendation from Cloud Adoption Framework & Azure Landing Zone Reference Architecture
Follow the design based on data classifications
Follow the design based on environment lifecycles (dev, qa, prod, etc.)
Something else that you prefer

Work will be completed as part of #153.


[OUTPUT].txt overwritten when mixing [VAPT/BB] with [URL Mode]

Hello Seth :)
When executing an initial scan and then add tasks by attempting to execute something like
./celerystalk scan -u http://<IP_ADDRESS>/secret_folder/

then some [OUTPUT].txt files are overwritten. This case would occur often when gobuster/proton detect new URLs that are worth looking into.
A dirty workaround would be appending something to [OUTPUT].
Cheers & Happy new year!

Thanks for this Shadi. Great bug find, I should have realized this. I'll look into this shortly and push a fix!

Hi,
so that it's also addressed, the same issue occurs when only using URL Mode multiple times with different URLs in the same workspace, which eventually overwrites previous [OUTPUT] files.
Regards

Awesome.  Thanks and Noted!

Sorry for being off the grid :)
I will let you know if it doesn't work, however, I doubt that and believe you will not be hearing from me ;-)
👍


access library files using jsdelivr instead of google

A simple PR mentioned at #9
Jsdelivr has good speed in china and global. If there is better CDN provider, please let me know 😄

cc @colin-scott


Change the title of the GitHub Commands page

Now the page title looks like this.

We need to change it to GitHub commands .

I can contribute @Rajdip019

You are already to assigned to one!

@Rajdip019 I raised a PR to it. please review it #241

Yup that is merged now. You can work on this! @saimaheshtaduri

U meant the title of the page right ? or the url ? @Rajdip019

The title on the tab section of the browser. @saimaheshtaduri

ok, done raised the pr #242


Environment settings

Thanks for the great job. I had some trouble with my environment settings. but I could not find the environment settings requirement in your article or in your code ,could you please give me a brief introduction about you settings(GPU memory.)
Looking foward to your reply.Thanks again for your job.

Hi @mumu-chen, thanks for your interest in our work. Our network was trained on a PC with two GTX 2080Ti GPUs (22G memory).

My solution：
CUDA 10.0
Python 3.7
PyTorch == 1.1.0
numpy==1.14.*
skimage
imageio
matplotlib
cv2
python -m pip install numpy==1.14.* scikit-image imageio matplotlib opencv-python


Expando/collapso should be inactive while editing custom tiers and RF levels

There are a couple of scenarios where the Expando/collapso buttons need to be inactive:

[ ] 1. While editing custom tiers. (Getting to this state requires setting up a program with a custom template, then saving some RF levels, and then hitting the "Settings" button. Here's one already done: https://tola-activity-qa.mercycorps.org/indicators/results_framework_builder/489)

[ ] 2. While editing any RF level form.

@jennyhavah #2 makes sense to me.  But I'm curious if you think there might be interest in navigating the level hierarchy while editing the custom tiers.  It seems like that could be a useful thing to be able to do.  If it's not, should we also disable the expandos on each card, not just the Expand all and Collapse all?

@sanjuroj Glad you called that out... The more I think about it, the more I think we should inactivate ALL expando-collapso icons when you are:

Editing Custom Template settings; and

Editing an RF level.

Here's where it gets weird for me, in either case: I have all levels expanded. I click "Edit" on an RF level somewhere in the middle. I click a collapso for the level I'm editing or one of the ones above. Weird stuff happens.
I think we should treat editing as a true modal experience and not let you navigate the hierarchy -- neither using the expand/collapse all (which you've fixed) OR the individual expando collapso icons (still operative). Thoughts?

Agreed, it would get really weird if you collapso'd the card you were editing.  I work on disabling the individual card expandos/collapsos.

PASSED. I can no longer expando or collapso while editing custom tiers or rf levels.


core: move strict notifications check under HFBasilisk

Follow the https://github.com/neo-project/neo/pull/2884. A part of the https://github.com/neo-project/neo/pull/2810.
Draft until the reference PR is settled.

I'd reorder test fixes and Basilisk enabling just to have green tests at every commit.

I've squashed them.


Deployment configuration structure.

Need to build functionality to get user deployment structure and perform deployment steps on basis of this.

PR for this change https://github.com/airdot-io/airdot-Deploy/pull/4


Emojis disappear when clicking on a category during scrolling

On iPad and iPhone, if I swipe down the emojis list and tap on a category before the momentum scrolling stops, the picker empties.
I've tested it on iOS 15 and 16.
The problem can be easily reproduced in the storybook, see the video below.
Issue.webm
Thanks.

Wow, good catch! This was a tricky one to track down but the just released 5.7.5 should resolve it. Please feel free to re-open if you still have issues.


Generic optimizer to handle different/hybrid parameter optimization techniques

Not all free parameters need to be optimized using a "minimizer" as we have envisioned it (something achievable with a simple call to scipy.optimize.minimze()). For example, some free parameters could be optimized quickly and accurately using the Fisher method or by simply scanning over several values.
Furthermore, if different parameters are optimized with different techniques (or using the same technique but with different settings), the minimization over all parameters must be handled carefully. I'll term this hybrid optimization when different techniques and/or settings are used to optimize different subsets of the free param values.
E.g., for hybrid optimization, with techniques/settings (1) through (N), I think we would need to optimize with all parameters that make use of technique/settings (1), then those that make use of technique/settings (2), and so on through to parameters that make use of technique/settings (N). Then we have to re-start at technique/settings (1) and go through (N) again, until some max_supersteps is exceeded or a full pass from (1) to (N) changes the metric by less than tol_supersteps tolerance in the match metric.
To implement "non-standard" optimization, we have a couple of options that I can think of right now:

Make a callable that is passable to scipy.oiptimize.minimize() via its method argument (which otherwise takes strings to denote the "standard" minimizer methods already implemented within Scipy). For simplicity for now, say that this callable will just handle the non-standard optimization technique(s) individually (and not handle what I've termed "hybrid" optimization).
Make a more generic Optimizer interface/object that can handle non-standard optimization techniques.
Use 1. above for non-standard techniques, and make the Optimizer object in 2. instead to understand how to deal with hybrid optimization--as well as the simple sub-case of that, where there's a single optimization technique used to optimize all parameters.

I guess this has ultimately been addressed with the recursive optimization strategies that are now in PISA.


nodejs-esm: added some textarea to  customize CSS

This look like this (with some custom values):

If you have suggestions

I can't get Collabora Online to cooperate on either the UITheme or UIMode.

Update, apparently my local storage had values it shouldn't have, that prevailed.