Task input variables not resolved in command inputs

Issue Type: Bug
Given this task
        {
            "label": "Show Localhost",
            "command": "${input:showLocalhost}",
            "problemMatcher": []
        }

and these inputs

        {
            "id": "showLocalhost",
            "type": "command",
            "command": "simpleBrowser.show",
            "args": "http://localhost:${input:port}"
        },
        {
            "id": "port",
            "description": "Port to hit",
            "type": "promptString",
            "default": "8009"
        }

It does display the Simple Browser view, but the URL it is pointed to is http://localhost:${input:port} instead of prompting me to enter a port.
Documentation here is slightly vague in that it says "Specifically, only command, args, and options support variable substitution." but it doesn't mention if args from "Tasks" vs args from "Inputs" will have variable substitution. Taking the documentation literally, input args should also have variable substitution.
VS Code version: Code 1.67.1 (da15b6fd3ef856477bf6f4fb29ba1b7af717770d, 2022-05-06T12:37:03.389Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
Remote OS version: Linux x64

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.81GB (2.94GB free)

Process Argv
-n --crash-reporter-id 5c6bfb0a-e814-44a2-a3e1-2a6e7807d072

Screen Reader
no

VM
0%

Item
Value

Remote
SSH:

OS
Linux x64

CPUs
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz (16 x 3099)

Memory (System)
62.03GB (25.95GB free)

VM
0%

Extensions (36)

Extension
Author (truncated)
Version

project-manager
ale
12.5.0

beardedicons
Bea
0.18.0

custom-plain-text
und
1.0.0

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

remote-ssh
ms-
0.80.0

remote-ssh-edit
ms-
0.80.0

remote-wsl
ms-
0.66.3

vs-qalc
nor
0.1.10

material-product-icons
PKi
1.3.0

vscode-jsp
pth
0.0.3

vscode-autohotkey
sle
0.2.2

codesnap
adp
1.3.4

vscode-json
and
1.5.0

vscode-lombok
Gab
1.0.1

beautify
Hoo
1.5.0

vscode-brazil
mar
0.46.0

vscode-uuid-generator
mot
0.4.1

date-hover-preview
nor
1.0.3

quick-regex-replacer
nor
1.0.5

vscode-configurable-shortcuts
nor
1.0.3

smithy-vscode
pep
0.9.0

errorlens
Phi
1.1.3

polacode
pnp
0.3.4

java
red
1.6.0

partial-diff
ryu
1.4.3

vscode-taskexplorer
spm
2.9.1

code-spell-checker
str
2.2.0

sort-lines
Tyr
1.9.1

vscodeintellicode
Vis
1.2.21

vscode-java-debug
vsc
0.40.1

vscode-java-dependency
vsc
0.19.1

vscode-java-pack
vsc
0.22.4

vscode-java-test
vsc
0.35.0

vscode-maven
vsc
0.35.1

markdown-all-in-one
yzh
3.4.3

(3 theme extensions excluded)

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Reproduced on 1.67.2 as well.
Alternatively... is there a better way to have a VSCode task open up the Simple Browser view with a specific URL? I've been scouring the internet for a couple hours, and this is the ONLY solution I have found to be able to pass the URL to the simpleBrowser.show command.

I've also tried the ${env:VARIABLE} syntax to access an environment variable in the args of an input. No luck with that either. Just results in http://localhost:${env:PORT}

We don't support nesting input variables like this. Ideally, simple browser would expose a command that lets you input a port number.

Can we get the documentation updated to reflect that?

Doc update done: https://github.com/microsoft/vscode-docs/pull/5374
We will not support input variable nesting. Argument is the same as the one here: https://github.com/microsoft/vscode/issues/80219#issuecomment-721624198. You can always write an extension or a script if you need more than simple substitution.


(DX) make axios package part of the module

I am not sure what is the reason for having axios as an external library because in many scenarios when I have tried the storyblok/nuxt module I needed to install axios separately.
I think, it could be improved by just shipping axios with the module or just use fetch instead.
What do you think?

If a library is needed for the package to work, then it should be in the dependencies list. Also, I notice that if I include the latest version of axios (v1.x.x) then everything goes to pot.

@chrisnoden
This would have been even better but I suppose that the general Storyblok JS client is using Axios under the hood so it wont be that easy to replace (not to mention that it is a breaking change for all current projects).
I also encountered the issues you mentioned with the most modern version of axios. That is why, I think it would be beneficial to freeze certain version of axios in the module so that it will be installed with it and not cause issues.

Looks like axios needs to be included and frozen to version 0.27.2 since v1.1.3 breaks everything as stated above.
Please consider switching to $fetch to better conform to the nuxt3 standard.

Hi @Baroshem, @chrisnoden and @bkuri, the axios package was added as an external library because the product team was refactoring the js-client to not use it. In the latest version, it is no longer used, we are working on updating all SDKs with the new version of the js-client, once it is included bye-bye problems, bye-bye axios 👋
I hope this clears up the problem, it was an internal debate for a long time, but now is ready!

Hi @Baroshem, @chrisnoden and @bkuri, the axios package was added as an external library because the product team was refactoring the js-client to not use it. In the latest version, it is no longer used, we are working on updating all SDKs with the new version of the js-client, once it is included bye-bye problems, bye-bye axios 👋
I hope this clears up the problem, it was an internal debate for a long time, but now is ready!

That's great to hear @Dawntraoz. However, right now anyone leveraging your library won't know they are required to add a pinned version of axios to their own project to make Storyblok integration work. Axios is still currently required and presumably the next version, being a breaking change by the sounds of it, will have a semver that clearly distinguishes it?

IMHO this issue shouldn't be closed until ther axios package has actually been removed, which is not the case as of @storyblok/nuxt v4.4.2.

Let's add some guidelines about the axios version to be used in the v4, and once the v5 is ready without axios let's close the issue, sounds like a plan @alexjoverm @manuelschroederdev?

@Baroshem latest version doesn't rely on Axios anymore, @Dawntraoz I will close this issue. Please feel free to open again if needed.


Fixes #2146 - invite user convert email to lower case

This is an imperfect solution.  The better solution will be after the new validation code is released, and we will be able to add a constraint to make sure lower case User.email never gets into the system.

coverage: 94.327% (+0.001%) from 94.326% when pulling 2098dae566fb2ccbf85f516f77548b8cf81c8ad1 on cody-invite-user-capitalized-email into 720eb346cf2d6c675c118c556c19983058642d1c on main.


Replace Nashorn with GraalVM JS Engine

Pull Request type

[x] Feature

Changes in this PR
Issue https://github.com/Netflix/conductor/issues/2312 replace Nashorn with GraalVM JS Engine
Nashorn is deprecated in JDK 11 and removed in JDK 15, resulting in runtime errors (and test failures) on JDK 15+

This is an updated version of my previously closed MR on the same topic (https://github.com/Netflix/conductor/pull/3233).
I have updated it to the latest version of GraalVM. Otherwise there is no substantial change.

This is an updated version of my previously closed MR on the same topic (#3233).
I have updated it to the latest version of GraalVM. Otherwise there is no substantial change.

@BlasiusSecundus
As much as I would personally like this change to happen, GraalJS is not fully compatible with Nashorn, and this change will break existing workflows of users. A better way would be to mark it as deprecated and do something with UI so that ECMAScript UI label corresponds to "graaljs" evaluator (and is selected as default for new workflows), at the same time we can still have old Nashorn on Java 15+ if it is included as external library from openjdk.
OpenJDK security EOL ends in 3 years
Coretto in 4 years
Eventually (hopefully sooner than later) Conductor will move to Boot 3 and Java 17+

Alternatively, since the script engine is selected at runtime,  if Nashorn engine could not be retrieved (i. e. Conductor runs on a JDK where it is already removed), then automatically create GraalVM engine instead of failing. And perhaps do some logging there which engine was selected ( + update docs to reflect this change in behaviour).
This would not require UI change.

@BlasiusSecundus I am trying to merge this but the builds are failing - can you run splotlessApply on the code?

I ran spotlessApply, it seems there were indeed some minor things like import ordering. Spotless check should now pass.

@BlasiusSecundus upon further testing we found that some of the scripts changes the behavior with graalvm.  A good example is how maps are accessed with nashorn and graalvm.
We have two options:

Replace nashorn completely, add a warning for users who are updating to the later versions that they should test their workflows for graalvm compatibility before upgrading.
Add it behind a feature flag, we already merged the PR that adds nashorn has a library and upgrades to JDK17, so we should be able to support both.  Maybe graalvm could be a another type of script?

cc: @c4lm
Other than this, the PR looks good.

If it causes backward compatibility issues, I would certainly not just replace it (as it would be essentially a breaking change).
In this case I think that the feature flag approach would be more appropriate.

As for inline task and switch operator:

evaluatorType
Type of the evaluator. Supported evaluators: value-param, javascript which evaluates javascript expression.

This could be easily extended with javascript-graalvm whilst the old  javascript would continue to use Nashorn
For Do-While loopCondition, Nashorn seems to be hard-coded:

Condition to be evaluated after every iteration. This is a Javascript expression, evaluated using the Nashorn engine.

Therefor introducing GraalVM there (without forcing it) could be more tricky. (Maybe a viable solution would be to  introduce the evaluatorType parameter there, defaulting to Nashorn to keep the existing behavior by default)

how about we introduce a new evaluator type graaljs and if specified will use graal to evaluate the script.
This will ensure existing javsascript continues to work and there is a safe path to upgrade to graalvm.

how about we introduce a new evaluator type graaljs and if specified will use graal to evaluate the script.
This will ensure existing javsascript continues to work and there is a safe path to upgrade to graalvm.

Yes, @v1r3n this is what I was also intended to suggest in my last comment.

This PR is stale, because it has been open for 45 days with no activity. Remove the stale label or comment, or this will be closed in 7 days.

Do not close.


Xcode 7 beta 6 fixes

:metal: Thanks!

Sweet!
By the way, I have another branch ready that updates SwiftBox to the latest
css-layout changes. Interested in taking a look?
On Mon, Aug 31, 2015 at 9:40 AM, Josh Abernathy<EMAIL_ADDRESS>wrote:

Merged #20 https://github.com/joshaber/SwiftBox/pull/20.
—
Reply to this email directly or view it on GitHub
https://github.com/joshaber/SwiftBox/pull/20#event-396853501.

Absolutely!

Sweet. Before I send it, one thing I noticed is that you use tab-based
whitespace. Is that intentional?
On Mon, Aug 31, 2015 at 9:42 AM, Josh Abernathy<EMAIL_ADDRESS>wrote:

Absolutely!
—
Reply to this email directly or view it on GitHub
https://github.com/joshaber/SwiftBox/pull/20#issuecomment-136424540.

Yup! I follow https://github.com/github/swift-style-guide.

Sounds good. I'll send it over as soon as I convert my spaces to tabs :)
On Mon, Aug 31, 2015 at 9:47 AM, Josh Abernathy<EMAIL_ADDRESS>wrote:

Yup! I follow https://github.com/github/swift-style-guide.
—
Reply to this email directly or view it on GitHub
https://github.com/joshaber/SwiftBox/pull/20#issuecomment-136425917.


Ospray does not build without TBB

On develop branch I can't find a way to build the ospray if TBB is not present on the system.

This is not a bug as TBB is now being used as the main tasking system for OSPRay. It is a very common library, as it can be found packaged with the Intel compiler, in almost every Linux distro's package manager, and on OS X via Homebrew or MacPorts.
It is possible to build OSPRay using OpenMP by specifying the CMake variable OSPRAY_TASKING_SYSTEM=OpenMP. We have not done any tuning with OpenMP and thus it does not perform as well as TBB. Continuing to support OpenMP as an option has not be decided, but it exists for now.

I have set OSPRAY_TASKING_SYSTEM=OpenMP and it still does not build, hence the bug report.

CMakeCache.txt
# This is the CMakeCache file.
# For build in directory: /home/pk/pool/ospray/build
# It was generated by CMake: /usr/bin/cmake
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//Path to a program.
CMAKE_AR:FILEPATH=/usr/bin/ar

//Choose the build type.
CMAKE_BUILD_TYPE:STRING=Release

//Enable/Disable color output during build.
CMAKE_COLOR_MAKEFILE:BOOL=ON

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++

//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds.
CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG

//C compiler
CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc

//Flags used by the compiler during all build types.
CMAKE_C_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_C_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds.
CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG

//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=/usr/local

//Path to a program.
CMAKE_LINKER:FILEPATH=/usr/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/gmake

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm

//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy

//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=OSPRay

//Path to a program.
CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib

//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries.
CMAKE_STATIC_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_STRIP:FILEPATH=/usr/bin/strip

//Enables verbose mode.
CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE

//Graphviz Dot tool for using Doxygen
DOXYGEN_DOT_EXECUTABLE:FILEPATH=DOXYGEN_DOT_EXECUTABLE-NOTFOUND

//Doxygen documentation generation tool (http://www.doxygen.org)
DOXYGEN_EXECUTABLE:FILEPATH=DOXYGEN_EXECUTABLE-NOTFOUND

//32vs64 bit addressing in ispc
EMBREE_ISPC_ADDRESSING:STRING=32

//Experimental new block/bricked volume layout
EXP_NEW_BB_VOLUME_KERNELS:BOOL=ON

//GCC Version
GCC_VERSION:STRING=5.3.0

//Path to a file.
GLUT_INCLUDE_DIR:PATH=/usr/include

//Path to a library.
GLUT_Xi_LIBRARY:FILEPATH=/usr/lib64/libXi.so

//Path to a library.
GLUT_Xmu_LIBRARY:FILEPATH=/usr/lib64/libXmu.so

//Path to a library.
GLUT_glut_LIBRARY:FILEPATH=/usr/lib64/libglut.so

//Path to the ISPC executable.
ISPC_EXECUTABLE:FILEPATH=/home/pk/.local/bin/ispc

//ISPC Version
ISPC_VERSION:STRING=1.8.2

//Path to a file.
OPENGL_INCLUDE_DIR:PATH=/usr/include

//Path to a library.
OPENGL_gl_LIBRARY:FILEPATH=/usr/lib64/libGL.so

//Path to a library.
OPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so

//Path to a file.
OPENGL_xmesa_INCLUDE_DIR:PATH=OPENGL_xmesa_INCLUDE_DIR-NOTFOUND

//Build ospModelViewer application.
OSPRAY_APPS_MODELVIEWER:BOOL=OFF

//Build ospParticleViewer application.
OSPRAY_APPS_PARTICLEVIEWER:BOOL=ON

//Build ospQtViewer (Qt-based model viewer)
OSPRAY_APPS_QTVIEWER:BOOL=OFF

//Build ospStreamLineViewer application.
OSPRAY_APPS_STREAMLINEVIEWER:BOOL=OFF

//Build ospVolumeViewer application.
OSPRAY_APPS_VOLUMEVIEWER:BOOL=OFF

//Enable experimental 'Knights Landing' build?
OSPRAY_BUILD_ENABLE_KNL:BOOL=OFF

//Target ISA (SSE, AVX, AVX2, or ALL)
OSPRAY_BUILD_ISA:STRING=SSE

//Build OSPRay with KNC Support?
OSPRAY_BUILD_MIC_SUPPORT:BOOL=OFF

//Add MPI Remote/Distributed rendering support?
OSPRAY_BUILD_MPI_DEVICE:BOOL=OFF

//Build DisplayCluster tiled display support
OSPRAY_DISPLAYCLUSTER:BOOL=OFF

//Build loaders for common file types.
OSPRAY_MODULE_LOADERS:BOOL=OFF

//Build OpenGL utility functionality
OSPRAY_MODULE_OPENGL_UTIL:BOOL=OFF

//Build seismic volume file support module
OSPRAY_MODULE_SEISMIC:BOOL=OFF

//Build 'TACH' (tachyon model viewer)
OSPRAY_MODULE_TACHYON:BOOL=OFF

//Must be multiple of largest vector width *and* <= OSPRAY_TILE_SIZE
OSPRAY_PIXELS_PER_JOB:STRING=64

//Use TBB or OpenMP as for per-node thread tasking system
OSPRAY_TASKING_SYSTEM:STRING=OpenMP

//Tile size
OSPRAY_TILE_SIZE:STRING=64

//Move 'voxelrange' computations to app?
OSPRAY_VOLUME_VOXELRANGE_IN_APP:BOOL=OFF

//Value Computed by CMake
OSPRay_BINARY_DIR:STATIC=/home/pk/pool/ospray/build

//Value Computed by CMake
OSPRay_SOURCE_DIR:STATIC=/home/pk/pool/ospray

//C++ compiler flags for OpenMP parallization
OpenMP_CXX_FLAGS:STRING=-fopenmp

//C compiler flags for OpenMP parallization
OpenMP_C_FLAGS:STRING=-fopenmp

QT_QMAKE_EXECUTABLE:FILEPATH=NOTFOUND

//Path to a file.
TBB_INCLUDE_DIR:PATH=TBB_INCLUDE_DIR-NOTFOUND

//Path to a file.
TBB_INCLUDE_DIR_MIC:PATH=TBB_INCLUDE_DIR_MIC-NOTFOUND

//Path to a library.
TBB_LIBRARY:FILEPATH=TBB_LIBRARY-NOTFOUND

//Path to a library.
TBB_LIBRARY_MALLOC:FILEPATH=TBB_LIBRARY_MALLOC-NOTFOUND

//Path to a library.
TBB_LIBRARY_MALLOC_MIC:FILEPATH=TBB_LIBRARY_MALLOC_MIC-NOTFOUND

//Path to a library.
TBB_LIBRARY_MIC:FILEPATH=TBB_LIBRARY_MIC-NOTFOUND

//Root of TBB installation
TBB_ROOT:PATH=TBB_ROOT-NOTFOUND

//Use ImageMagick for ModelViewer's Texture loaders.
USE_IMAGE_MAGICK:BOOL=OFF

//Value Computed by CMake
embree2_BINARY_DIR:STATIC=/home/pk/pool/ospray/build/builddir/ospray/intel64/embree-v2.7.1

//Value Computed by CMake
embree2_SOURCE_DIR:STATIC=/home/pk/pool/ospray/ospray/embree-v2.7.1

//Dependencies for the target
embree_LIB_DEPENDS:STATIC=general;embree_sse42;general;sys;general;simd;general;lexers;

//Dependencies for target
embree_avx2_LIB_DEPENDS:STATIC=

//Dependencies for target
embree_avx_LIB_DEPENDS:STATIC=

//Dependencies for target
embree_sse42_LIB_DEPENDS:STATIC=

//Dependencies for the target
lexers_LIB_DEPENDS:STATIC=general;sys;

//Dependencies for the target
ospray_LIB_DEPENDS:STATIC=general;dl;general;embree;general;TBB_LIBRARY_MALLOC-NOTFOUND;general;TBB_LIBRARY-NOTFOUND;

//Dependencies for the target
ospray_glut3d_LIB_DEPENDS:STATIC=general;ospray;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;general;glut;general;GLU;general;m;

//Dependencies for the target
ospray_minisg_LIB_DEPENDS:STATIC=general;ospray_xml;

//Dependencies for the target
ospray_module_loaders_LIB_DEPENDS:STATIC=general;ospray;

//Dependencies for the target
ospray_module_opengl_util_LIB_DEPENDS:STATIC=general;ospray;general;/usr/lib64/libGLU.so;general;/usr/lib64/libGL.so;

//Dependencies for the target
ospray_xml_LIB_DEPENDS:STATIC=general;ospray;

//Dependencies for target
simd_LIB_DEPENDS:STATIC=

//Dependencies for the target
sys_LIB_DEPENDS:STATIC=general;dl;

########################
# INTERNAL cache entries
########################

//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//STRINGS property for variable: CMAKE_BUILD_TYPE
CMAKE_BUILD_TYPE-STRINGS:INTERNAL=Debug;Release;RelWithDebInfo
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=/home/pk/pool/ospray/build
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=4
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=3
//ADVANCED property for variable: CMAKE_COLOR_MAKEFILE
CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=/usr/bin/cmake
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=/usr/bin/cpack
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=/usr/bin/ctest
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=0
//ADVANCED property for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=/usr/bin/ccmake
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Unix Makefiles
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Have symbol pthread_create
CMAKE_HAVE_LIBC_CREATE:INTERNAL=1
//Have include pthread.h
CMAKE_HAVE_PTHREAD_H:INTERNAL=1
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=/home/pk/pool/ospray
//Install .so files without execute permission.
CMAKE_INSTALL_SO_NO_EXE:INTERNAL=0
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MAKE_PROGRAM
CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_NM
CMAKE_NM-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=19
//ADVANCED property for variable: CMAKE_OBJCOPY
CMAKE_OBJCOPY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_OBJDUMP
CMAKE_OBJDUMP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RANLIB
CMAKE_RANLIB-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=/usr/share/cmake
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STRIP
CMAKE_STRIP-ADVANCED:INTERNAL=1
//uname command
CMAKE_UNAME:INTERNAL=/usr/bin/uname
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=0
//ADVANCED property for variable: DOXYGEN_DOT_EXECUTABLE
DOXYGEN_DOT_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DOXYGEN_EXECUTABLE
DOXYGEN_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: EMBREE_ISPC_ADDRESSING
EMBREE_ISPC_ADDRESSING-ADVANCED:INTERNAL=1
ENABLE_INSTALLER:INTERNAL=OFF
//Build Embree with support for ISPC applications.
ENABLE_ISPC_SUPPORT:INTERNAL=ON
//Build Embree as a static library.
ENABLE_STATIC_LIB:INTERNAL=OFF
//Enable to build Embree tutorials
ENABLE_TUTORIALS:INTERNAL=OFF
//Generates code path for Xeon Phi.
ENABLE_XEON_PHI_SUPPORT:INTERNAL=OFF
//ADVANCED property for variable: EXP_NEW_BB_VOLUME_KERNELS
EXP_NEW_BB_VOLUME_KERNELS-ADVANCED:INTERNAL=1
//Details about finding GLUT
FIND_PACKAGE_MESSAGE_DETAILS_GLUT:INTERNAL=[/usr/lib64/libglut.so][/usr/include][v()]
//Details about finding OpenGL
FIND_PACKAGE_MESSAGE_DETAILS_OpenGL:INTERNAL=[/usr/lib64/libGL.so][/usr/include][v()]
//Details about finding Threads
FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()]
//ADVANCED property for variable: GCC_VERSION
GCC_VERSION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GLUT_INCLUDE_DIR
GLUT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GLUT_Xi_LIBRARY
GLUT_Xi_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GLUT_Xmu_LIBRARY
GLUT_Xmu_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GLUT_glut_LIBRARY
GLUT_glut_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ISPC_EXECUTABLE
ISPC_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ISPC_VERSION
ISPC_VERSION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_INCLUDE_DIR
OPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_gl_LIBRARY
OPENGL_gl_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_glu_LIBRARY
OPENGL_glu_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_xmesa_INCLUDE_DIR
OPENGL_xmesa_INCLUDE_DIR-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OSPRAY_APPS_MODELVIEWER
OSPRAY_APPS_MODELVIEWER-MODIFIED:INTERNAL=ON
//MODIFIED property for variable: OSPRAY_APPS_PARTICLEVIEWER
OSPRAY_APPS_PARTICLEVIEWER-MODIFIED:INTERNAL=ON
//MODIFIED property for variable: OSPRAY_APPS_QTVIEWER
OSPRAY_APPS_QTVIEWER-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: OSPRAY_APPS_STREAMLINEVIEWER
OSPRAY_APPS_STREAMLINEVIEWER-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OSPRAY_APPS_VOLUMEVIEWER
OSPRAY_APPS_VOLUMEVIEWER-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: OSPRAY_BUILD_ENABLE_KNL
OSPRAY_BUILD_ENABLE_KNL-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OSPRAY_BUILD_ISA
OSPRAY_BUILD_ISA-MODIFIED:INTERNAL=ON
//STRINGS property for variable: OSPRAY_BUILD_ISA
OSPRAY_BUILD_ISA-STRINGS:INTERNAL=ALL;SSE;AVX;AVX2
//ADVANCED property for variable: OSPRAY_DISPLAYCLUSTER
OSPRAY_DISPLAYCLUSTER-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OSPRAY_MODULE_LOADERS
OSPRAY_MODULE_LOADERS-MODIFIED:INTERNAL=ON
//MODIFIED property for variable: OSPRAY_MODULE_OPENGL_UTIL
OSPRAY_MODULE_OPENGL_UTIL-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: OSPRAY_PIXELS_PER_JOB
OSPRAY_PIXELS_PER_JOB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OSPRAY_TASKING_SYSTEM
OSPRAY_TASKING_SYSTEM-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OSPRAY_TASKING_SYSTEM
OSPRAY_TASKING_SYSTEM-MODIFIED:INTERNAL=ON
//STRINGS property for variable: OSPRAY_TASKING_SYSTEM
OSPRAY_TASKING_SYSTEM-STRINGS:INTERNAL=TBB;OpenMP
//ADVANCED property for variable: OSPRAY_TILE_SIZE
OSPRAY_TILE_SIZE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OSPRAY_VOLUME_VOXELRANGE_IN_APP
OSPRAY_VOLUME_VOXELRANGE_IN_APP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OpenMP_CXX_FLAGS
OpenMP_CXX_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OpenMP_C_FLAGS
OpenMP_C_FLAGS-ADVANCED:INTERNAL=1
//Test OpenMP_FLAG_DETECTED
OpenMP_FLAG_DETECTED:INTERNAL=1
//Enables backface culling.
RTCORE_BACKFACE_CULLING:INTERNAL=OFF
//Enables buffer strides.
RTCORE_BUFFER_STRIDE:INTERNAL=ON
//Enables ray stream logger.
RTCORE_ENABLE_RAYSTREAM_LOGGER:INTERNAL=OFF
//Lets Embree library export all symbols.
RTCORE_EXPORT_ALL_SYMBOLS:INTERNAL=ON
//Ignores invalid rays.
RTCORE_IGNORE_INVALID_RAYS:INTERNAL=OFF
//Enables intersection filter callback.
RTCORE_INTERSECTION_FILTER:INTERNAL=ON
//Enables ray mask support.
RTCORE_RAY_MASK:INTERNAL=ON
//Enabled support for ray packets.
RTCORE_RAY_PACKETS:INTERNAL=ON
//Enables statistic counters.
RTCORE_STAT_COUNTERS:INTERNAL=OFF
//STRINGS property for variable: RTCORE_TASKING_SYSTEM
RTCORE_TASKING_SYSTEM-STRINGS:INTERNAL=TBB;INTERNAL
RTCORE_TASKING_SYSTEM:INTERNAL=Internal
//Enable triangle pairs.
RTCORE_TRIANGLE_PAIRS:INTERNAL=OFF
//ADVANCED property for variable: TBB_INCLUDE_DIR_MIC
TBB_INCLUDE_DIR_MIC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TBB_LIBRARY_MALLOC_MIC
TBB_LIBRARY_MALLOC_MIC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: TBB_LIBRARY_MIC
TBB_LIBRARY_MIC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: USE_IMAGE_MAGICK
USE_IMAGE_MAGICK-ADVANCED:INTERNAL=1
//STRINGS property for variable: XEON_ISA
XEON_ISA-STRINGS:INTERNAL=SSE2;SSE3;SSSE3;SSE4.1;SSE4.2;AVX;AVX-I;AVX2;AVX512
XEON_ISA:INTERNAL=SSE4.2

Oops, definitely a bug. :)
I should be able to get this fixed today. I'll post here when it's ready....sorry for jumping to the wrong conclusion!

The fix should now be in both 'release-0.9' and 'devel'. Please let me know if you continue to have issues.

No worries. Anyhow, it is not fixed; look at this commit version of the CMakeLists.txt
https://github.com/ospray/OSPRay/blob/3acde31056aa23fade7216733162be2634209287/ospray/CMakeLists.txt
There is OpenMP option working. Now if you look at the recent version of the same file and go to line 313, there are two variables TBB_LIBRARY and TBB_LIBRARY_MALLOC which are not found if the TBB is not set. These two are the culprits.

The latest changes I did this morning unset TBB_LIBRARY and TBB_LIBRARY_MALLOC (and their mic equivalents) if the OpenMP backend is selected. I've successfully used the following steps in an environment which does not have TBB:

configure OSPRay in a blank build directory (fails to find TBB)
change OSPRAY_TASKING_SYSTEM to OpenMP in ccmake
configure OSPRay again (succeeds)

You can also specify -DOSPRAY_TASKING_SYSTEM=OpenMP on the initial configuration if you want to configure OSPRay from scratch all in one go without TBB.
Perhaps you are asking for OSPRay to automatically use OpenMP if TBB is not found? If so, we want users to explicitly choose OpenMP right now because of performance issues (a.k.a. we want to steer users to build with TBB).

Sorry, I forgot to pull your commit. All works now, thank you.


Multiple labels should not be shown: has parthas_part

Copied from #104

This happens because in OWL more than 1 label is given. I think we should use the first label. This should also be the first label for a given language when multi-lang is used.

This is an easy one for once!


help me!

(base) [root@localhost terraform-proxmox-k3s]# terraform plan
var.authorized_keys_file
Path to file containing public SSH keys for remoting into nodes.
Enter a value: /root/.ssh/authorized_keys
var.control_plane_subnet
Enter a value: <IP_ADDRESS>/29
var.lan_subnet
Subnet used by the LAN network. Note that only the bit count number at the end
is acutally used, and all other subnets provided are secondary subnets.
Enter a value: <IP_ADDRESS>/16
var.master_node_settings
Enter a value:
var.network_gateway
IP address of the network gateway.
Enter a value: <IP_ADDRESS>
var.node_pools
Node pool definitions for the cluster.
Enter a value: name = "default",size = 2,subnet = "<IP_ADDRESS>/28"
var.node_template
Proxmox vm to use as a base template for all nodes. Can be a template or
another vm that supports cloud-init.
Enter a value: Ubuntu18.04
var.proxmox_node
Proxmox node to create VMs on.
Enter a value: pve1
var.support_node_settings
Enter a value:
╷
│ Warning: Experimental feature "module_variable_optional_attrs" is active
│
│   on versions.tf line 14, in terraform:
│   14:   experiments = [module_variable_optional_attrs]
│
│ Experimental features are subject to breaking changes in future minor or patch releases, based on feedback.
│
│ If you have feedback on the design of this feature, please open a GitHub issue to discuss it.
╵
╷
│ Error: Missing expression
│
│   on  line 1:
│   (source code not available)
│
│ Expected the start of an expression, but found the end of the file.
╵
╷
│ Error: Extra characters after expression
│
│   on  line 1:
│   (source code not available)
│
│ An expression was successfully parsed, but extra characters were found after it.
╵
╷
│ Error: Missing expression
│
│   on  line 1:
│   (source code not available)
│
│ Expected the start of an expression, but found the end of the file.
╵
╷
│ Error: No value for required variable
│
│   on variables.tf line 63:
│   63: variable "support_node_settings" {
│
│ The root module input variable "support_node_settings" is not set, and has no default value. Use a -var or -var-file command line argument to provide a value for this variable.
╵
╷
│ Error: No value for required variable
│
│   on variables.tf line 83:
│   83: variable "master_node_settings" {
│
│ The root module input variable "master_node_settings" is not set, and has no default value. Use a -var or -var-file command line argument to provide a value for this variable.
╵
╷
│ Error: No value for required variable
│
│   on variables.tf line 95:
│   95: variable "node_pools" {
│
│ The root module input variable "node_pools" is not set, and has no default value. Use a -var or -var-file command line argument to provide a value for this variable.
╵

Can you provide a sample implementation

Hey @niukekkk thanks for giving this module a try!
I wrote a quick example project with a README to walk you through the process in the linked MR above. Give it a look to see if it helps you deploy your cluster! Feel free to leave comments on the MR if there is something that did not go well for you and I can clarify it.
Let me know when your issue is resolved so we can close this issue and merge the example to master!


Redesigning the ui of contact form

i amm a gssoc23 contributor . please assign this issue to me @codervivek5

do not need to redesigned ......some one is working on it


Docs issues

Some problems in the documentation detected using closure_verify
Why? I looked the way than the compiler can detect the misuse of deprecated code. The result was that I saw nothing except:
..\build\temp\lib\OpenLayers\Tile\Image.js:145: WARNING - Property getBoundsFromBaseLayer never defined on OpenLayers.Tile.Image
                this.bounds = this.getBoundsFromBaseLayer(this.position);
                              ^

and it seems an issue controlled.
But along the way I was fixing the incorrect documentation of this pull request.

I thinks it's good to merge. @ahocevar, do you agree?

@fredj and @ahocevar: Regarding "context", from my point of view, no matter what words are used. What matters is that there is a structure that allows verification by an automatic process.
Most of these annotations have been detected by Closure Compiler, and "context" is no exception (It has been using a precompilation process that converts Natual Docs to JsDoc)


Increase size of IIS stored logs

This is necessary after #111 - single runs of full are taking up many log files because of all the output from the parser and generator.

:+1: though i do not get why 16 MB specifically for max total size.

That allows us to store at least 8 logs (if they are all at the maximum individual size).

:+1:


Question: dotnet Global Tool, Update Installed Browsers to latest?

I started using the NuGet package 0.142.2 last week in my asp.net core application.  Couple of days ago when 0.151.0 went live I updated my NuGet packages to the latest.  When I attempted to run against playwright I had the following error:
Failed to launch chromium because executable doesn't exist at C:\\Users\\benh\\AppData\\Local\\ms-playwright\\chromium-815036\\chrome-win\\chrome.exe
I went down the path of wanting to avoid downloading the browsers at runtime, so I started using the dotnet global tool, playwright-sharp install-browsers.

Re-ran it...nothing happened, chromium-799411 still installed
Deleted the browsers, re-ran the tool, chromium-799411 installed.

Questions

I don't see a method to tell the global tool to update the browsers 'to latest', did I miss something somewhere?
Not knowing the NuGet package upped the required version without a notification caught me off guard.  What is expected by the end developer if they decide they DO NOT want to install browsers at runtime?  Every NuGet update need to install browsers?

I don't see a method to tell the global tool to update the browsers 'to latest', did I miss something somewhere?

We have this issue for that #917 I think we should implement it for the next version.
If you update the dotnet to the latest version you should get the latest browsers.

Not knowing the NuGet package upped the required version without a notification caught me off guard. What is expected by the end developer if they decide they DO NOT want to install browsers at runtime? Every NuGet update need to install browsers?

What if:

You run playwright-sharp install-browsers inside the web project.
playwright-sharp could try to find a PlaywrightSharp.dll and get the version from it.
Download the browsers for that version?

#917 will for sure fix the install issue for the donet global tool.

I'm ok if it is 'on me' to go and rev the versions of the browsers.

Possibly a documentation change to let people know, "Hey if you don't want to install the browsers at run time you are on your own to update the browsers, and they update on every new NuGet release."

If it is documented I can work it into my workflow to update the browsers on every new NuGet, or I can pin it and always tell playwright "Use this version"

@benhysell I would personally expect new browsers if I update Playwright. Most new features require new wires on the browser side.

Possibly a documentation change to let people know, "Hey if you don't want to install the browsers at run time you are on your own to update the browsers, and they update on every new NuGet release."

Definitely.
cc @arjunattam

I would personally expect new browsers if I update Playwright. Most new features require new wires on the browser side.

Do new versions of playwright require new versions of Chrome or is the thinking "Let's always ship the latest and greatest" ?
I would have thought, naively, yes Chrome adds new things, but core functionality is there and rather static at this point.
I understand if Chrome releases a new bleeding edge feature I need to go get latest, but minor version bumps I would expect new NuGet packages of playwright would work with whatever version of Chrome I point it at, as long as it is 'recent'.

Thanks for opening this issue, @benhysell.
At this stage, Playwright versions have a 1-1 mapping with browser versions. This is a combination of requiring browser-side code (e.g. we recently added support for touchscreen taps, which required browser-side changes) and shipping the latest versions (to manage browser upgrades under the Playwright version).
This behavior is influenced by how NPM works in the JS ecosystem. NPM provides a postinstall hook to run browser installation whenever the package is installed or updated. This avoids the need for a runtime API (like InstallAsync). The dotnet-tool brings this experience to NuGet, but it is independent from the dependency itself.

@benhysell Added deployment docs for the upcoming v0.162.0. We will rely on the CLI instead of a dotnet tool to install browsers as part of an app.
Feedback is welcome.

@kblok

is the global tool getting deprecated?

Was the .exe always part of the built application?  I'm not seeing it in the version I'm using

How large is the .exe?  The DLL is already at 50mb, not looking forward to a larger deploy :-)

is the global tool getting deprecated?

We wouldn't use the global tool for this anymore. Although, I think it would be cool to use the dotnet tool as a bridge to the CLI codegen tool.

Was the .exe always part of the built application? I'm not seeing it in the version I'm using

It was. But we were unzipping that inside a playwright-driver directory at run-time. We would be removing all that boilerplate on v0.162.0.

How large is the .exe? The DLL is already at 50mb, not looking forward to a larger deploy :-)

We are taking the drivers out of the DLL. That will give us a 500kb DLL file on the next version :-)

I think this will work.

Will I have the ability to dictate where the browsers are installed via the cli?  I'm deploying to an onprem machine and my user account can only write to certain directories, I want to make sure I can still tell the cli "put your stuff in this directory."

I know asking for stability in a pre 1.0 package is asking for a lot, but modifying a bunch of deployment scripts on the next NuGet version is also not desirable on my part.  Kindly asking if 'this is the way', excellent I believe it will work for me.

Will I have the ability to dictate where the browsers are installed via the cli? I'm deploying to an onprem machine and my user account can only write to certain directories, I want to make sure I can still tell the cli "put your stuff in this directory."

You can set the env variable PLAYWRIGHT_BROWSERS_PATH before calling the CLI, and then pass that to the CreateAsync method.

I know asking for stability in a pre 1.0 package is asking for a lot, but modifying a bunch of deployment scripts on the next NuGet version is also not desirable on my part. Kindly asking if 'this is the way', excellent I believe it will work for me.

I know it might be quite painful for you as an early adopter, and I really really appreciate your patience. As an early adopter, your feedback is super appreciated. We are trying to provide the best experience for most use case scenarios :)

@kblok appreciate it, appreciate all the effort/hard work!

I would push, not too hard, but hard, for an input flag on the cli to tell the .exe where to place the browsers much like one can with the dotnet global tool today.  Messing about with environment variables on CI/CD pipelines can be a pain, or has been a pain for me in the past, and I rather not go down that route.  Or allow both...again I'm working on machines where I have limited permissions, the less steps I have to take/things I have to modify the better.

Anyway, I'm happy to close this issue at this point with a 'not going to fix' and point people to the update documents.

@benhysell would you mind creating an issue here https://github.com/microsoft/playwright-cli ?


Use current stable release for docs on pandas.sourceforge.net

This is just a suggestion, but I think that the documentation on the site should be the current stable release instead of the current development version.  Perhaps put the bleeding edge version on /dev?  Just a thought from a user perspective as most people will be downloading the version that is on PyPi / debian.  Either that, or provide links to alternative versions of the docs.

Closing this issue. Will have stable snapshot at time of 0.7.0 final (soon)


Short term memory leak from static ObjectType.builtinObject

After compiling my codebase, 130mb of memory is occupied by the AST nodes reachable from ObjectType.builtinObject -> rawType -> namespaces -> ....
buildinObject is a static member that is assigned with Compiler instance-related data during compilation.
I run the compiler many times within the same JVM process, but it's not really a problem for me since the next run of the compiler presumably replaces that static property.
But I'm flagging this as a potential issue for other users, and also presumably an unintentionally unsafe approach (from threading and memory perspective).

It is indeed unsafe, but it wasn't unintentional. We took a shortcut.
https://github.com/google/closure-compiler/blob/master/src/com/google/javascript/jscomp/newtypes/ObjectType.java#L74
Leaving the issue open because it'd be good to go back at some point and replace the static fields with instance fields.

Presumably this means it is unsafe to run concurrent compilations in the same JVM?

Yes. It will happen to work if they are all using the same externs for core objects (which should be true in most cases). But we will make it actually safe at some point.

OK - presumably it's just the NTI pass that is affected, so using the compiler for anything else (e.g. parsing) is unaffected? I'm using reflection to erase these fields (non-concurrently with compilation) as part of a test for memory leaks in our wider build process' test suite.

yes, this is NTI specific

Closed by cc1ea4c4a1f67dd637de504d8e96dd5f873e5667


Release 0.9.0

A new release is required for REview to communicate with Hog by applying the added field (https://github.com/petabi/review-database/pull/51).

Released.


The plugin is great but documentation is incomlete!

The plugin is great but documentation is incomlete? Yes it is true. Author is very lazy :)
I am doing my best to finish all the docs but I don't have enough free time.

In the Example the path:
use PawelLen\DataTablesListing\Filters\FilterBuilderInterface;
need to be
use PawelLen\DataTablesListing\Filter\FilterBuilderInterface;
and the path
use PawelLen\DataTablesListing\Listing\ListingBuilderInterface;
does not exitst at all!


Why define a function inside of another function???

https://github.com/kevkevs/JADE191.jl/blob/6befd665dcd2f34d79dd10baf4c7fed7c68231ba/src/JadeAlgo.jl#L25

You can do that in Julia, but I'm not sure you need to in this case


How to add extensions?

I'm trying to port the Nunjucks markdown extension to Twing but I'm still figuring out some stuff.

I'm reading the docs and it seems pretty simple, I've made some PHP classes in the past but I've never used TypeScript before TBH. Maybe a Twing Extension Boilerplate would be a nice repo idea?

@zomars, Yes, a boilerplate would be great. A Yeoman generator would be even better.
Did you succeed by the way? Do you need help on anything?

I've got busy with other project right now but I'll revisit it soon enough.

Here is an example https://github.com/nedkelly/twing-markdown there is a little more to do but I hope this helps.


KolibriOS link dont work

This link to image is broken, but file is downloading successfully
https://copy.sh/v86/?profile=kolibrios
Error:

Downloads:

Can you look at the browser console for errors?

Opera 43.0.2442.1144

Thanks for reporting. You can use this as a fallback for now: http://copy.sh/v86/?profile=kolibrios
@XVilka @yogev1978 Can one of you set up https on builds.kolibrios.org so that this url works: https://builds.kolibrios.org/eng/data/data/kolibri.img

Here's a fallback with https: https://copy.sh/v86/?profile=kolibrios-fallback

Fixed by temporarily loading from my server on https.


Scrollable belowTimeText layout not correct on square devices

Repro https://github.com/yingding/timeText/blob/de169ab70e76d19e0d5368237c926800fc9e3872/app/src/main/java/com/example/android/wearable/composeforwearos/MainActivity.kt

Low priority given Wear 3 devices are currently all round.


PostSonarr fail - File "/sickbeard_mp4_automator/postSonarr.py", line 23, in

MP4 conversion are failing with the following error... attempted redeploying the container - but still, same error happens.
Manual.py works fine.
postSonarr.py  IOError: [Errno 13] Permission denied: '/var/log/sickbeard_mp4_automator/index.log' | 11:37am
-- -- | --
   postSonarr.py | stream = open(self.baseFilename, self.mode) | 11:37am
   postSonarr.py | File "/usr/lib/python2.7/logging/init.py", line 943, in _open | 11:37am
   postSonarr.py | StreamHandler.init(self, self._open()) | 11:37am
   postSonarr.py | File "/usr/lib/python2.7/logging/init.py", line 913, in init | 11:37am
   postSonarr.py | logging.FileHandler.init(self, filename, mode, encoding, delay) | 11:37am
   postSonarr.py | File "/usr/lib/python2.7/logging/handlers.py", line 64, in init | 11:37am
   postSonarr.py | BaseRotatingHandler.init(self, filename, mode, encoding, delay) | 11:37am
   postSonarr.py | File "/usr/lib/python2.7/logging/handlers.py", line 117, in init | 11:37am
   postSonarr.py | h = klass(*args) | 11:37am
   postSonarr.py | File "/usr/lib/python2.7/logging/config.py", line 163, in _install_handlers | 11:37am
   postSonarr.py | handlers = _install_handlers(cp, formatters) | 11:37am
   postSonarr.py | File "/usr/lib/python2.7/logging/config.py", line 85, in fileConfig | 11:37am
   postSonarr.py | fileConfig(os.path.join(os.path.dirname(sys.argv[0]), 'logging.ini'), defaults={'logfilename': os.path.join(logpath, 'index.log')}) | 11:37am
   postSonarr.py | File "/sickbeard_mp4_automator/postSonarr.py", line 23, in  | 11:37am
   postSonarr.py | Traceback (most recent call last): | 11:37am

Looks like you've got a permission issue
Make sure you're setting up your PUID and PGID environment variables appropriately and double check your write permissions for the index.log file

I'm currently encountering the same issue.
I'm running manual.py and postSonarr.py in parallel.
Maybe the index.log file is locked by one process and the other can't open it in write mode again?
Maybe manually specifying a log output when running manual.py could solve the issue?
Not sure it's possible.. Is it?

i did a chown 1000:1000 -R on /sickbeard_mp4_automator/ and on /config
things are running again. not sure how those permission got impacted on deployed a fresh container install

That is strange considering the error was a problem with /var/log/sickbeard_mp4_automator/index.log which is not related to the root or the config directory
The dockerfile sets the group owner to 'users' which abc (the default user) is a member of
You can check what UID the user abc is assigned and make sure it corresponds to your UID and that ABC is in groups
A fresh container install does still depend on a config directory with appropriate permissions granted so that part at least makes sense


Added "go up" link to browse template

In order to have directly a link within the browse listing I have added
a link to the top of the table to get one level up in the tree. Added
that after a chat with @mholt.
Signed-off-by: Thomas Boerger<EMAIL_ADDRESS>

 You should sign our Contributor License Agreement in order to get your pull request merged.

Looking visually good! :+1:

@mholt applied your comment

Thank you Thomas!


Release v0.0.1a4

Updated the Copyright 2022-2023

Signed-off-by: Kairo de Araujo<EMAIL_ADDRESS>

Codecov Report
Base: 93.60% // Head: 93.60% // No change to project coverage :thumbsup:

Coverage data is based on head (d8a5634) compared to base (560fe8f).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #241   +/-   ##
=======================================
  Coverage   93.60%   93.60%
=======================================
  Files          16       16
  Lines         594      594
=======================================
  Hits          556      556
  Misses         38       38

Impacted Files
Coverage Δ

app.py
88.46% <ø> (ø)

repository_service_tuf_api/__init__.py
81.48% <ø> (ø)

repository_service_tuf_api/api/bootstrap.py
100.00% <ø> (ø)

repository_service_tuf_api/api/config.py
100.00% <ø> (ø)

repository_service_tuf_api/api/targets.py
100.00% <ø> (ø)

repository_service_tuf_api/api/tasks.py
100.00% <ø> (ø)

repository_service_tuf_api/api/token.py
100.00% <ø> (ø)

repository_service_tuf_api/bootstrap.py
100.00% <ø> (ø)

repository_service_tuf_api/config.py
85.29% <ø> (ø)

repository_service_tuf_api/metadata.py
50.00% <ø> (ø)

... and 6 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


partially initialized structs in local variables, similar to partially moved structs, perhaps should be possible

Here are two examples where currently a dummy value for a struct field is needed, but the compiler could allow it to be safely left uninitialized by noticing that it's always initialized before being used externally.  This is quite analogous to partially moved structs, where the compiler currently allows moving out fields as long as you put them back before using the struct externally (even if the latter is in a loop, as in the second example); but in this case the struct would start in a "partially moved" state.
Even though I think this is a fairly unusual use case (at least, as long as it doesn't allow calling methods in the partially uninitialized state), the added semantic complexity is pretty minimal, so I think it's worth considering.
use std::cell::RefCell;
struct Foo<'a> {
    a: RefCell<int>,
    b: &'a RefCell<int>,
}
struct Bar {
    a: int,
    // assume some other stuff
}
fn main() {
    // Case 1: assigning a reference to point to the struct itself (somewhat
    // limited since the struct can't be moved, but potentially useful)
    let mut foo = Foo {
        a: RefCell::new(1),
        b: /* dummy */ &RefCell::new(1),
    };
    foo.b = &foo.a;

    // Case 2: assigning inside a loop
    let mut bar = Bar {
        /* dummy */ a: 0,
    };
    for &a in [1, 2, 7].iter() {
        bar.a = a;
        // call some method on bar
    }
}

Now we have MaybeUninit, which covers these use cases. Maybe this can be closed now. @Centril

OP is about doing so safely, while MaybeUninit is doing so unsafely.

See also Goal: Accept partial initialization + use of records created via such #54987


puppet: Extract the wal-g configuration from the backups.

This will allow it to be used for monitoring, to check the state in S3
rather than just trusting the backups when they said they ran.

Merged, thanks @alexmv!


add consultation storage

Pull Request Test Coverage Report for Build 1234

6 of 11 (54.55%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 71.813%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/clinicio/storage/XmlSerializableClinicIo.java
6
11
54.55%

Totals

Change from base Build 1230:
-0.05%

Covered Lines:
3386

Relevant Lines:
4715

💛  - Coveralls


Add report name to the tab title

title : Talk to the City - {report-name}

I went with {report-name} directly (without Talk to the City) as this provides more information. When the user has many tabs open, the width of the tab does not accommodate the entire width of "Talk to the City - {report-name}".
I'm hoping @colleenm can create a better looking favicon than i did, to make the tab easily recognizable.
Let me know if that's OK. If not, feel free to re-open this issue.

Update: use slug instead

LGTM. I'll file a separate bug for the favicon.
@theboldzoey if this looks good to you I think this issue can be closed

LGTM!


Source code for Maximum Index Product in Java

Related Issue
Closes: #671
Describe the changes you've made
Adding source code for Maximum Index Product in Java
Describe if there is any unusual behavior of your code(Write NA if there isn't)
NA
Language used for coding
Java
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have documented the code.
[x] New and existing unit tests pass locally with my changes.

Kindly review my PR ;-)


Feat: Nudge for any required action, not just OS updates

Nudge is looking fairly nice these days.
🥧 / ☁ feature request
It would be neat if Nudge could be adapted to prompt users towards an action that's not an OS update. For instance: enable SIP, logout for Filevault, fill out a form in Workday.
Nudge would need to support executing user-defined scripts for conditions and actions. It would also need to handle and alert for multiple simultaneous configs.
Anyways, just an idea.

@w0de I think you're better using a tool like Dialog for user-facing notifications. You would then just have multiple scripts that would call Dialog based on your criteria.

It's definitely something I've discussed with a few interested parties but would take a ton of effort to accomplish.
Maybe one day if someone pays me in some capacity ;)

If this is unlike-to-implement, can it be closed?  @erikng .


Push these images to another registry in addition to Docker Hub?

Docker is making some questionable decisions of late w/r/t open source software. Should we push these images to another registry (GitHub? RedHat/Quay? others?) in addition to Docker Hub to hedge our bets / help folks get around Docker Hub's rate limits?

It seems Docker have reversed their questionable decision. https://www.docker.com/blog/no-longer-sunsetting-the-free-team-plan/

👍🏻

Would it be valuable to apply for the Docker-sponsored Open Source program anyway? https://www.docker.com/community/open-source/application/

I’m not sure it gets us much? Since we’re an Official Image we don’t interact with Docker Hub in the usual way. We merge manifest files via PRs to the docker-library/official-images repo. The Docker folks then build and publish our images.

I'm going to close this for now, but please feel free to comment further if you think it should still be considered.


Laravel 9 install

Hi
When I installed the package and I'm going to execute php artisan down, php artisan horizon:terminate  I got this exception php artisan horizon:terminate
It is necessary to install horizon?

I would like your help, thanks

Hi @redencion, yes, this package is about adding support for Laravel Horizon, so you indeed need this one install. You can run composer require laravel/horizon and php artisan horizon:install.

Hi @redencion, yes, this package is about adding support for Laravel Horizon, so you indeed need this one install. You can run composer require laravel/horizon and php artisan horizon:install.
Thanks for supporting me. So Is it need configured services redis?  I mean Horizon


Refactoring Codebase to Gradle Convention Plugin: Enhancing Build Efficiency and Maintainability

In this pull request, we present a comprehensive refactoring of our legacy codebase, transitioning it to a more modern and efficient build system using Gradle Convention Plugin. This refactoring effort aims to streamline the build process, improve maintainability, and foster a more structured development environment.

@VahidGarousi Welcome to the club! 💪😎


Support custom styling for line plots

+1 -> is there any way to apply coloring to the background of the chart or change axis label text color?

@mtcliatt, anything yet with regards to @JayPerfetto's question?

Sorry for the late reply, that functionality doesn't exist yet but wouldn't be difficult to add.
There's another charting package which does have that functionality (I'm pretty sure), which may suit your needs better: https://github.com/imaNNeoFighT/fl_chart
I haven't added this yet because I've been working on scrolling, panning, and zooming, which turns out to be a really hard problem with labeling and keeping the view zoomed to fit. I'm almost done, but because that other package looks like it works so nicely, I may turn the focus of this package to charting for stocks and related data.
Let me know if FL_Chart works for y'all.

Yeah. I've tried using Fl_Chart but it doesn't really give me the stocks feel. Another thing is having a segment under the line chart which can have a gradient colour with opacity  @mtcliatt. How quick are we going to get a modification in that regard, because I'm currently working on a project that needs stuff around that?

I can probably do that this week.


Update readme

there is no transition AddFunds in README cus not sure about it's function
Acceptance transition and Callback transition are both called Callback transition in README

fixed above

Some high level review to answer your comments
there is no transition AddFunds in README cus not sure about it's function -> this is for the smart contract to accept Zilliqa funds in case it is being used to hold ZILs in multi sig, without that the multi sig can't hold native ZIL tokens, the keywords inside the transition is specific for explicitly accepting ZIL tokens
Acceptance transition and Callback transition are both called Callback transition in README -> split them up into 3, acceptance callback, proxy callback and initiator callback, they all have different purposes, we discussed this in one of our earlier calls

@junhaoyap update all above

One other comment, could you please check all the callable when paused column, we recently did a change on one of the transitions and it may be out of sync

checked that, looks all fine


🌱 Disable scheduled workflows from running in forks

Workflows use resources that are only available when run in the metal3-io/cluster-api-provider-metal3 repository, so workflow run would always fail when they run in a forked repository. They are of no value to fork repositories. They are triggered by the schedule event, so they cause regular annoying and confusing workflow failure notifications for every fork owner. Rather checking these workflows only in upstream repo is enough. This PR is inspired by https://github.com/arduino/arduino-cli/pull/888

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

/test gomod

/test markdownlint
/test shellcheck

/cherry-pick release-1.3


update_automation: drop symlinks

Instead jenkins jobs either need to call mkcloud from the real path
or have the checkout dir in $PATH

The recreation of the symlinks caused breakages today again. We need to urgently merge this.

+1

+1


[BUG] List of broken things in ACF at the moment

Title says it all.

HEAT does not respect the damage permissions when it comes to damaging the ammoboxes. it just doesnt. i dont know why.
Procedural armor probably has negative health from the start, or if i put it straight it doesnt die really.
you can get past the 50t limit and have armor more dense than  lead
updating procedural armor causes in any way, even without changing dimensions, causes it to have mass of 1kg.
procedural armor can be shot through and the shell will ignore everything but the world.
HEATFS and missile HEAT do comicaly high amount of postpen damage.
not really a bug, but i just want to point out that a 300mm piledriver, which weights at 3.6t has spike mass of only ~50kg. you are telling me that a 300mm in diameter spike with a length of almost 3.5m only weights 50kg?
also not a bug, but autoloaders beign 3x heavy as a regular cannon makes them worthless, pls make them a bit lighter.

might update with more bugs if i remember smth

edit 1: server version is Git-master-11fefdc

I'm really not concerned with pArmor, it was an experiment and we're not really going anywhere with it at the moment.
 Is it actually heavier than 50k or is this some kind of calculation bug inside ACF?

it could be that its not heavier than 50t, bcuz when you look at that prop w/ weight tool it says that it weight 50t. on how to reproduce - im not sure, i just maxed out both armor and ductility and it works.

Procedural armor probably has negative health from the start, or if i put it straight it doesnt die really.

procedural armor can be shot through and the shell will ignore everything but the world.

These are happening because you have procedural armor disabled in your settings (it's disabled by default now).

you can get past the 50t limit and have armor more dense than lead

updating procedural armor causes in any way, even without changing dimensions, causes it to have mass of 1kg.

Should be fixed in the current dev branch.


Need a standard way to get token from repoclient/modifier.

Job service need a way to get token of resource by calling token service.
Currently the code scattered in modifier and authorizer.
Looks it maybe easy to refactor and let modifer has capability to return a token

The authorizer(modifier) authorizes a request by adding a token according to the resources that the request want to access, so refactor the authorizer to return a token doesn't make sense. As discussed, I'm going to close this issue.


Error... please help

Pas install lewat composer error ini mas
Problem 1
- Root composer.json requires agungsugiarto/boilerplate ^1.1 -> satisfiable by agungsugiarto/boilerplate[v1.1.0].
- agungsugiarto/boilerplate v1.1.0 requires myth/auth dev-develop -> found myth/auth[dev-develop] but it does not match your minimum-stability.

Solved by using CI-4 Appstarter


fix(platform): performance metric loading error state

can we make it easier? It's a little mess.

can we make it easier? It's a little mess.

I can have a try but it is hard, the loading and data is calculated by several state, just like a waterfall and each state affect the appearence.


Add coveralls

🚀 Feature Proposal
Add coveralls.
Motivation
See how well the tests are doing.

@tehKapa what we need to add this also to server?

I already added the Coveralls variable on Travis.
I think that's enough. Do we use node-tap, right?

Something's wrong.
[error] "2019-10-15T15:35:13.714Z"  'error from lcovParse: ' 'Failed to parse string'
308[error] "2019-10-15T15:35:13.716Z"  'input: ' ''
309[error] "2019-10-15T15:35:13.717Z"  'error from convertLcovToCoveralls'
310
311/home/travis/build/HospitalRun/hospitalrun-server/node_modules/coveralls/bin/coveralls.js:18
312        throw err;
313        ^
314Failed to parse string

So, quickly recap:

I've set environment variable COVERALLS_REPO_TOKEN on Travis
Update package.json and travis.yml but once they run the tests, they still don't show up on coveralls


Theme toggle button position fixed

Fixes Issue🛠
Closes #1916 Theme Toggle Button Positioning Issue
The theme-changing button currently appears inside the hamburger menu at last on small devices. It should be placed beside the hamburger icon for better accessibility and visibility on small devices.
Description👨💻
This PR moves the theme toggle button next to the hamburger icon on small screens for better accessibility. Previously, the toggle was hidden inside the hamburger menu, making it harder to access. The layout has been adjusted using CSS to align both elements side by side, ensuring a more user-friendly experience on mobile devices.
Changes:
Repositioned theme toggle next to the hamburger icon on small screens.
Adjusted CSS for better alignment and responsiveness.
Issue Fixed:
Improved the visibility and accessibility of the theme toggle on small screens.
Type of Change📄

[ ] Bug fix (non-breaking change which fixes a bug)

Checklist✅

[ ] I am an Open Source contributor
[ ] I have performed a self-review of my code
[ ] My code follows the style guidelines of this project

Screenshots/GIF📷

The navbar items are centered which should not, no changes to the other existing styles, please fix by making the new commits in this same PR @SHRUTISINHA250714

@Rakesh9100 Made the required changes. Please review.


Importing to Resolve Error

Bug description
When importing into Resolve the timeline is very...odd. I believe the image does a better job of explaining it than words.
I've tried a few ways of importing into Resolve, but my primary way is:

Right click the Media Pool
Hover over Timelines
Hover over Import
Select the AAF / EDL / XML / etc option
Select the .fcpxml file

Once the Load XML... screen pops up, I do not adjust any of the settings.

What's your platform?
Python Version: 3.11.5 64-bit
Platform: Windows 10 amd64
FFmpeg Version: N-110322-g0c25da5a28-g1440bf15e2+1
FFmpeg Path: C:\Users\X\AppData\Local\Programs\Python\Python311\Lib\site-packages\ae_ffmpeg\Windows\ffmpeg.exe
Auto-Editor Version: 24w03a

What command did you use
"C:\Users\X.mp4" --margin 0.05s,0.15s --edit audio:stream=0,threshold=-40dB,mincut=7,minclip=1 --export resolve

What properties does your input video have?

video:

track 0:

codec: h264
fps: 87169000/2905633
resolution: 1920x1080
aspect ratio: 16:9
pixel aspect ratio: 1
duration: 2905.633
pix fmt: yuv420p
color range: tv
color space: bt709
color primaries: bt709
color transfer: bt709
timebase: 1/90000
bitrate: 731771
lang: und

audio:

track 0:

codec: aac
samplerate: 48000
channels: 2
duration: 2905.578
bitrate: 106048
lang: und

track 1:

codec: aac
samplerate: 48000
channels: 2
duration: 2905.578
bitrate: 159882
lang: und

track 2:

codec: aac
samplerate: 48000
channels: 2
duration: 2905.578
bitrate: 2274
lang: und

track 3:

codec: aac
samplerate: 48000
channels: 2
duration: 2905.578
bitrate: 2277
lang: und

track 4:

codec: aac
samplerate: 48000
channels: 2
duration: 2905.578
bitrate: 2274
lang: und

track 5:

codec: aac
samplerate: 48000
channels: 2
duration: 2905.578
bitrate: 2274
lang: und

container:

duration: 2905.633
bitrate: 1041338

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\X.mp4':
Metadata:
major_brand     : isom
minor_version   : 512
compatible_brands: isomiso2avc1mp41
encoder         : Lavf60.16.100
Duration: 00:48:25.63, start: 0.000000, bitrate: 1041 kb/s
Stream #0:00x1: Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 731 kb/s, 30 fps, 30 tbr, 90k tbn (default)
Metadata:
handler_name    : VideoHandler
vendor_id       : [0][0][0][0]
Stream #0:10x2: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 106 kb/s (default)
Metadata:
handler_name    : SoundHandler
vendor_id       : [0][0][0][0]
Stream #0:20x3: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 159 kb/s
Metadata:
handler_name    : SoundHandler
vendor_id       : [0][0][0][0]
Stream #0:30x4: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 2 kb/s
Metadata:
handler_name    : SoundHandler
vendor_id       : [0][0][0][0]
Stream #0:40x5: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 2 kb/s
Metadata:
handler_name    : SoundHandler
vendor_id       : [0][0][0][0]
Stream #0:50x6: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 2 kb/s
Metadata:
handler_name    : SoundHandler
vendor_id       : [0][0][0][0]
Stream #0:60x7: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 2 kb/s
Metadata:
handler_name    : SoundHandler
vendor_id       : [0][0][0][0]
At least one output file must be specified
Comments
This happens both with the CLI & GUI versions.

Hello, sorry you're having problems.
For the CLI, try using the latest version. I've changed how the Resolve export works since then.
pip install -U auto-editor

Hey, that did solve this thanks. Although, an issue I'm not encountering is that the video clips aren't linked with their audio tracks. Would that be something you'd consider looking into? If so, should I open a separate issue?
Also, unrelated to the issue... I am using the GUI with Mincut & Minclip set using decimals, so 0.7 / 0.4 in my case, but the CLI only seems to use whole numbers. I considered using 7 / 4 for the CLI would give me the same results, but they did not.

Sure, you can make a separate issue.
For the CLI, mincut and minclip are in "timebase" units. If you wanted to set 0.7 seconds, the value in "timebase" units would multiply 0.7 by your video's fps.
fps = 30
round(0.7 * fps)
>>> 21  # This is the number you would set


📘 [issue] - README.md file is not configured and visible in the repository's main branch

Related page
README.md
Kind of issue
Other
Issue Description
Update the README.md file so that it can be visible in the repository's main branch and make the README file more informative by including the steps, features etc.

Context
I was trying to look into the code after the release, and then I came across this issue.
Scale of problem
1 - Not annoying

I noticed it before but hadnt time to fix it, today all will be fine :)

Ok !


Add Ventura and Monterey installers to builtInAcceptableApplicationBundleIDs

Add Ventura and Monterey installers to builtInAcceptableApplicationBundleIDs as requested in https://github.com/macadmins/nudge/issues/412

the other PR I merged has this.


Revert "[Frontend] Add Span filling for frontends to Relay (#9723)"

Because of the failure the LSTM conversion from Pyotrch
https://github.com/apache/tvm/pull/9723
This reverts commit ce108c1f53235a483eb11dffffb8770642907642.
Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

Thanks for identifying this and raising the revert quickly @chunit-quic :smile_cat:

Thanks for identifying this and raising the revert quickly @chunit-quic 😸
Hi @Mousius,
No problem, my pleasure. :)

Sorry that didn't identify this at the very begging.
Based on the test_lstm.py, it's very surprising to me that we obtain the same execution result compared with pytorch outputs (using == but not isclose()). Even the RelayIR graph are different.
I am digging into it now. Will update status here once I find any solution or clues.  :D


Deprecate old SODA data types

Socrata has released a new version of its API, and a few existing data types are now deprecated:

[ ] Phone replaced by simple Text
[ ] URL replaced by simple Text
[ ] Location replaced by Point, and sub-components (address, city, etc.) broken out into separate Text columns

These will be marked as Deprecated in the next release (currently scheduled as 0.5.0) and removed in a subsequent release.

Socrata has announced that for the upcoming maintenance window (2018-06-16), they will be officially changing the Phone datatype to Plain Text, and removing the ability to get/set the Phone.Type sub-property.
This was never marked as deprecated, but now certainly should be.


I can't fetch by  entity ID

Using v0.7 on node 7.
Looking here:
https://cloud.google.com/datastore/docs/concepts/queries
it says
const query = datastore.createQuery('Task')
  .filter('__key__', '>', datastore.key(['Task', 'someTask']))

What I need is, given an id for an entity, ex id = '5709436928655360' and entity 'bla'

Make a key for that entity using an id
Fetch a row, using that key.

My code :
https://github.com/topseed/topseed-bp/blob/master/dserver/ds/ContentDS.js
to make a key is ~ line 37.
Is that right? It's not working.
The code to fetch is ~ line 15. Also not working but could be due to key not correct.
There are no examples to fetch a row by key id, I looked and googled.
(Separate part 2, I want to update new columns, but not delete old ones, so first I fetch so I can merge).
Help/hints please.

For an ID, make sure you don't send it as a string, so:
datastore.key(['Task', 123])

that appears to fix it.
THANK YOU.
(now i have an unrelated nested promise thing that I'll solve)

OK, I'm sure I found a bug, but I have to explain. The method is save()
here: https://github.com/topseed/topseed-bp/blob/master/dsrv/ds/ContentDS.js
(it's called by Smoke.js https://github.com/topseed/topseed-bp/blob/master/dsrv/smoke.js.
When I give it a valid ID, it works. But when the ID is wrong - as a part of testing, it does a ' Unhandled Rejection at: Promise'.
The reason that is a problem is that it is called by Express, a  'unhandled rejection' is global, I never return an error to the html user!
What the method does is give an ID, it does a fetch, merges the fields (so I don't lose columns) and then updates.  It works when ID is found. But again, when no ID, I expect it to reject 'inline' so I can handle the rejection. Insert and select methods there work fine.
So if rejection is global, it creates a problem, I need to trap the rejection in flow. Worst case if I have to do call back, but I don't know how to get around this - and I need to put in production.

I'm not very sure where to plug in to your app, but if there's an error from here, this doesn't appear to be handling it in a catch block or another then.

I have put a catch block there and no joy.
(My code starts at 'smoke.js')
I think this would be a good example  to have:
update kind by ID - but don't delete any columns. ( I do that by fetch and merge before update there ). But make sure if the ID is wrong or something wrong to notify inline. I think this is common operation and I don't know how to do that. Can you please just do a sample hello world update(lossless) by id that also rejects?

@callmehiphop can you take a look through that code?
I'm not very well versed in promises, so he'll likely be more help. We do have a number of issues on backlog though, so please also ask on StackOverflow and link here, so others can follow along.
If you can boil it down to a simple test case without any external dependencies, maybe we can clear up what's going on.

So in ContentDS.js I think your save method should handle failure cases as @stephenplusplus points out.
Then in smoke.js you should also handle failure cases.

I have put catch in both places and it did not catch or handle.

I pushed the code,  even if it does nothing - as per your suggestions. Errors get handled outside of the loop creating leaks of sorts each time there is an error. An easy exploit on www.
I think this is a common need, to update via key and 'merge' fields - it takes me 50 lines of code and... it does not handle errors. Like I said insert and load work fine on errors, just update does not handle errors.
Your code does promises and if there is no fix coming soon, then I'd like to know if there is a way to update using callbacks?

@puppetmaster3 I think the error handling is just in the wrong spot, your save method should look more like this
save: function(dom, id, jDObj) {
        return _save(dom, id, jDObj).then(function(res) {
        	return res[0].mutationResults[0];
        });
}

I fixed it. I was not catch, but the other syntax used instead of catch - you can see code in git.
I suspect something is wrong deep in your code and at some point when you fix it, it will break my working code. Proof: insert and load test out bad path w/ catch. But update (w/ merge) works w/ 	}, function (err).
I can use it, but I'll be very worried when you guys do new releases.  You should have example of update by key and merge fields as a test case.

@puppetmaster3 I'm looking at your code a little closer and I think there might be an issue with your _save function as well. If you were to refactor it to resemble something like this
function _save(dom, id, JDObj) {
  const key = _makeKey(id);

  return DS.get(key).then(function(data) {
    const row = data[0];

    Object.assign(row, jDObj);

    const entity = {
      key: key,
      data: row
    };

    return DS.update(entity);
  }).catch(function(err) {
    console.log('_save CDS err ' + err);
    return Promise.reject(err);
  });
}

I think you might see some different results! (The provided code is untested though.).

I have committed that code and I still have to use , function(er){
in 2 places (not needed for load or insert).
If I don't have it, I get the unhandled error out of the path.
If the test is positive, all works no matter what, but when I test a fail,  I get the unhandled w/o ,function(er) {

@puppetmaster3 can you condense your code to the smallest possible use case without any external dependencies? Ideally a single file that serially runs commands up until they fail. That will help us figure out the root cause in the quickest way possible.

Yes, I will do that, I need to stabilize my code and then work up the example.
For now, I have it working the way I want.
The main issue is that the save code looks weird, relative to insert for example.
Until I make it single code, you can glance the 3 files, or wait:
a) https://github.com/topseed/topseed-bp/blob/master/ssrv/smokeRMemb.js
Look at save() vs signUp() smoke tests, like I said, it works/looks OK.
b) https://github.com/topseed/topseed-bp/blob/master/ssrv/routes/ds/MembDS.js
The smoke test files calls that file, the implementation.
The signup 'selects' first to see if there is duplicate email and then insert.
The save does a fetch so It can merge/update vs replace.
But notice that in save I have to catch, but not in  'signUp'.
The reason is that I do negative tests that fail, and I need to know it failed but it has to be in the methods and not a unhandled outside leak.
c) https://github.com/topseed/topseed-bp/blob/master/ssrv/routes/ds/BaseGDS.js
The save calls _save above.
Again, it looks strange. I am not expert on promise either. Here are the 3 files together just pasted for save. The goal is for smoke test to catch a fail inline, and what I have works, other than it should look simpler. :

save()
function save() {
const dat = {}
dat.id = '57292010259742702' // I pass a bad key
const auThoPro = A.getAuThoB('aa' ) //return role promise
auThoPro.then(function(autho){
		return autho
	}).then(function(autho) {

		return membDS.save(dat.id, dat, autho)
	}).then(function(res) {
		console.log('smoke')
		console.log(res)
		//A.setReturnToken(autho, res) // sets return headers

	}).catch(function (er) {
		console.log('Smoke err')
		console.log(er)
})//pro

}
save(id, jDObj) {
MembDS._removePasswordFields(jDObj)
const ipro = super._save(TABLE, id, jDObj)
ipro.then(function(res){
console.log('res')
//console.log(JSON.stringify(res))
//console.log(res)
	return (res)
})
.catch(function (er) { // I have to do this
	console.log('save er')
	console.log(er)
})
return ipro

}//s
save(table, id, jDObj) {
const key = BaseGDS.makeKey(table, id)
const jD = jDObj
jD.id = id
jD.lastDate = U.getDt()//store date of change

return DS.get(key).then(function(data) {
	const row = data[0]
	Object.assign(row, jD)//merge

	const entity = {
		key: key,
		data: row
	}
	return DS.update(entity)//2
}).then(function(res) {
	//console.log('_save3')
	return (res[0].mutationResults[0])
}
, function(er){ // I have to do this
	console.log('_save er '+ er)
	throw new Error(er)
})

}//_s
Again, the scope is to select so I can merge/update and if it fils (for example bad key) to fail inline. I think this is needed often and should be part of your tests and examples. If you just write an example of that from scratch, that would help also.
But I will put it on my to do to create a single file example, above code is just cut/paste from 3.

The automatic formatting messed it up, makes it hard to read for you... you are better of at glancing at the 3 files for now, my code should be easy to follow.

@puppetmaster3 I'm sorry, but we'll need to work from a smaller reproduction case. It's understandable that it will take time for you to come up with one, so whenever you get to it, please let me know and we will re-open this issue.

OK, you closed it quick while I was working on it, within 1 hour:
https://github.com/topseed/topseed-bp/blob/master/ssrv/routes/ex.js

Your previous replies, now deleted, were suggesting we look through the repo. Sorry for misunderstanding, I'm happy to re-open so we can keep working on it.
Tried running, currently stuck at:
const auThoPro = A.getAuThoB('aa' ) //return role promise
                   ^
ReferenceError: A is not defined

My note also said I'll be working on an example but you can't just give me an hour.
Updated:
https://github.com/topseed/topseed-bp/blob/master/ssrv/routes/ex.js
Again, this code works as I need it to, and using it is clean. Just the implementation promises looks weird relative to other code that does not save.

$ node .
aa
Smoke err
ReferenceError: U is not defined

From this line: jD.lastDate = U.getDt()//store date of change
I commented that line out, now I get:
$ node .
aa
_save er TypeError: Cannot convert undefined or null to object
save er
Error: TypeError: Cannot convert undefined or null to object
    at index.js:86:11

Just to confirm, is that the error we're trying to fix?

The example is good and works well and gets used well.
The result you have is a good one: that id does not exists and the smoke test is able to catch the error.
The issue is that the implementation code to get it to work is 'strange'. For example catch and er handlers are not needed when I do checks on insert and inserts work as I expect promise to work. But when I update I have to add a ', err' handler and a catch in middle for it to say inline on a fail. You nsert follows promise proper use. But using update requires jumps. What I am doing is quite simple, a merge. Again, I have no issues, and using it works. Also I have base class that handles it, so when you guys do refactor, my code will not be affected.

I'm glad to hear it's working well, so there's at least no immediate need to come to a resolution.
So I believe what you're asking for is a convenience method in our API that can replace these steps you have to go through with one single method call. Can you show how you'd like that to look?

Correct, there is no immediate need.
But I am not needing a convenience method either, I should implement update like I implement insert, observe the insert implementation line, 97:
https://github.com/topseed/topseed-bp/blob/master/ssrv/routes/ex.js
Notice that I don't have a catch() or , errror. As per promise spec, I just have a catch when I use it, in my route. The insert first checks to see if a record exists.
But to do a realistic update, I require both!   Line 89 and 53. Both are needed. That is not per promise spec! I should only need line 36 when I use it! Do you see the diff btwn how insert works and how update works?
So, I don't need line 89 or 53 if I test using the happy path. But when I test a 'failed' update, both are needed, else I get a unhandledRejection resource like in node on any browser side error passed to node - outside of my  handlers.
But the implementation issue is abstracted in my code so that when you fix it it won't affect my code. You should have docs, examples or tests that touch on common/realistic uses cases.

I believe this is a matter of how you are writing the promises. I condensed your code further, keeping the same amount of functions and the execution path. An error from any promise is returned in the singular catch handler.

It's possible. Do you have an example of similar?

Sorry, forgot to include the link: https://gist.github.com/stephenplusplus/2f25ad7272d45612a9e8c1d920469be4

Sorry, that is not a userful examples
The tst code you have does not have a catch - and it must: In my router I have to know did it work or not.  That is using the implementation, and no catch there to handle.


400 Bad Request - aborted pulling info URL

Starting over the weekend, Instaloader has begin giving an error.    Prior to that, no error was being generated and initial downloads were all completed succesfully.
The command line I am running is:
/usr/local/bin/instaloader --latest-stamps .stamps/.stamp --login <my_user> --no-metadata-json --no-captions --stories --no-video-thumbnails --abort-on=302,400,429 ''
Here is what I am seeing:
Using latest stamps from .stamps/<profile>.stamp.
Loaded session from /home/<user>/.config/instaloader/session-<user>.
Logged in as <user>.
Traceback (most recent call last):
  File "/usr/local/bin/instaloader", line 33, in <module>
    sys.exit(load_entry_point('instaloader==4.9.1', 'console_scripts', 'instaloader')())
  File "/usr/local/lib/python3.10/site-packages/instaloader/__main__.py", line 471, in main
    _main(loader,
  File "/usr/local/lib/python3.10/site-packages/instaloader/__main__.py", line 212, in _main
    }.get(target[0], 'username')
IndexError: string index out of range

If I run it with --quiet, I get a different error:
Download aborted: Query to https://i.instagram.com/api/v1/media/<profile_ID>/info/ responded with "400 Bad Request".

It appears to be doing this for all of the profiles I am downloading ( ~6 ).
I am getting some of the images and stories images/videos, but it doesn't look like I am necessarily getting them all.
Instaloader version: 4.9.1
Any suggestions or is anything else seeing something like this?

similar thing happens to me

As quickly as this issue came on, it has also left.   I am assuming the change or issue was on the Instagram side.   I will leave this open for a few more days and then close

This issue is back again today and it definitely is leading to missed stories.   Is there any other information that might help debug this?

Since yesterday evening this is happening on all my accounts (6) when downloading stories.
After 1 or 2 downloads the error400 occurs. (The account is not locked)
I tried scraping only 1 account for stories but when downloading the second file (of 2) the error 400 occurred again.

yeah this is happening to me too lately, any way to fix it????

I was having this same issue. When I tried to log in manually I was asked to change my password because of my unusual activity, Instagram determined that my account was compromised. After I changed my password, everything started working again.

This issue persists for me.   I am running instaloader across ~10 profiles and I usually only get this error on a couple of accounts.  For those accounts, I seem to be getting the normal posetd pictures, but not all the stories

Warning: If error 400 occurs and you continue using your account with instaloader or any scraper this will lead to suspension of your account. My account got suspended today. I was downloading my saved posts but Instagram randomly gave error 400 and then when I logged into my account in the Instagram app I found that my account is suspended. So please continue scraping with fake or temporary Instagram account.

Description too vague / unclear to track it purposefully as a bug. The first problem is not reproducible, for the 400 Bad Request response we already have a bug ticket.

remove --abort-on=400 command should fix this


Migrate to JSON internal schema.

It's wasteful and slow to convert CSV to JSON every time the annotation page is loaded.  We probably shouldn't read bytes from disk at all on the server, and instead let the client directly request a girder file.
IMO, the internal representation of tracks should be some JSON schema.  It would be simple enough to do a copy-on-read the first time the client requests a VIAME csv, then maintain the JSON data for annotation, and add export endpints to convert back to CSV if the user wants it.
This would also allow us to support other necessary annotation data types, like kw18 and kpf, which are needed for general adoption within kitware.

When it comes to training, there's currently no supported JSON format for annotation in the training step of viame (it supports csv, kw18, and HABCAM). So we'd definitely need to have the conversion in place for training.

I should add though I'm definitely in favor of us doing this.

I fully expect that any interaction with external systems would involve conversion in and out of our internal schema.

Training now supports json, the main issue is it needs to auto-detect json vs csv as csv is still in production (and probably always will be as we have some contracts which require it for excel users doing analytics on the output).
No objection to changing what is used internally as long as we always have optional support for csv at input (initial upload) and output (download through GUI) time as well.

Semi-related:
Ive been thinking a lot about how detections and tracks are represented in the client, and I think we may want to migrate to a track-centric data structure.

representing tracks as a global detection array cannot ever support interpolation
a flat detection array is efficient O(1) for frame lookup, but bad for almost everything else.
For example, update/insert is always O(N) (where N is detection count)
This O(N) cost is multiplied in practice because there are several different "views" of the data needed that all get computed on update: like the unfiltered track list for the left pane, the filtered detection list for rendering, etc.
Right now the lookup cost for figuring out a track's start and end frames is also O(N) which is why  gotoTrackFirstFrame is such a pain:

function gotoTrackFirstFrame({ trackId }) {
      setTrackEditMode(trackId, false);
      const _frame = eventChartData.value.find((d) => d.track === trackId)
        .range[0];
      seek(_frame);
    }

This function uses eventChartData, which has an update cost of O(N), and isn't correct to use here because it doesn't have info about tracks that were filtered out due to low confidence.
It is necessary to have a list of tracks that looks something like this:
{
  'min_confidence': Number,
  'max_confidence': Number,
  'begin': Frame,
  'end': Frame,
  'detections': Array<Detection>,
}

This is an issue because the lookup cost, depending on the track/detection ratio, which is 1:1 for pipelines where only detections were run, can be up to O(N) instead of O(1).
Changing the structure like this would flip the update/insert cost to something roughly constant, and lookup cost could be made roughly logarithmic if we had something like an interval tree: https://www.cs.cmu.edu/~ckingsf/bioinfo-lectures/intervaltrees.pdf
It would be easy enough to construct a simple tree, but a self-balancing tree would be better, like a balanced interval tree or a red-black interval tree.
Having previously implemented the idiot-version (iterate over tracks, filtering by range), I know that worst-case performance is actually already pretty good, so I feel pretty confident that the tree would perform well.

closed in #137