Openfast compilation using visual studio

Hi,
I have the following errors during installation. I saw some previous solutions and tried them but the issue are still the same

Is there a way to make them same, as I didn't change it myself. It has been here like this.

I made them both IFX, still didnot solve the issue. The output is as follows:
Build started...
1>------ Build started: Project: FASTlib (IFX), Configuration: Release_Double x64 ------
Performing Pre-Build Event...
Running Registry for SeaState_Interp
----- FAST Registry --------------
input file: ....\modules\seastate\src\SeaState_Interp.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\seastate\src/SeaState_Interp_Types.f90
Registry for SeaState_Interp completed.

Running Registry for SeaState
----- FAST Registry --------------
input file: ....\modules\seastate\src\SeaState.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\seastate\src/Current.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Waves.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Waves2.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\seastate\src/SeaState_Types.f90
Registry for SeaState completed.

Running Registry for ExtPtfm_MCKF
----- FAST Registry --------------
input file: ....\modules\extptfm\src\ExtPtfm_MCKF_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\extptfm\src/ExtPtfm_MCKF_Types.f90
Registry for ExtPtfm_MCKF completed.

Running Registry for MoorDyn
----- FAST Registry --------------
input file: ....\modules\moordyn\src\MoorDyn_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\moordyn\src/MoorDyn_Types.f90
Registry for MoorDyn completed.

Running Registry for AirfoilInfo
----- FAST Registry --------------
input file: ....\modules\aerodyn\src\AirfoilInfo_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\aerodyn\src/AirfoilInfo_Types.f90
Registry for AFI completed.

Running Registry for Lidar
----- FAST Registry --------------
input file: ....\modules\inflowwind\src\Lidar.txt
generating ....\modules\inflowwind\src/Lidar_Types.f90
Registry for Lidar completed.

Running Registry for SS_Radiation
----- FAST Registry --------------
input file: ....\modules\hydrodyn\src\SS_Radiation.txt
generating ....\modules\hydrodyn\src/SS_Radiation_Types.f90
Registry for SS_Radiation completed.

Running Registry for UnsteadyAero
----- FAST Registry --------------
input file: ....\modules\aerodyn\src\UnsteadyAero_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\aerodyn\src/UnsteadyAero_Types.f90
Registry for UA completed.

Running Registry for Map
----- FAST Registry --------------
input file: ....\modules\map\src\Map_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\map\src/MAP_Fortran_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\map\src/MAP_Types.f90
Registry WARNING: derived data type LinInitInp of type lin_initinputtype is not passed through C interface
Registry WARNING: derived data type LinInitInp of type lin_initinputtype is not passed through F-C interface
Registry WARNING: derived data type Ver of type progdesc is not passed through C interface
Registry WARNING: derived data type LinInitOut of type lin_initoutputtype is not passed through C interface
Registry WARNING: derived data type Ver of type progdesc is not passed through F-C interface
Registry WARNING: derived data type LinInitOut of type lin_initoutputtype is not passed through F-C interface
Registry WARNING: derived data type LinParams of type lin_paramtype is not passed through C interface
Registry WARNING: derived data type LinParams of type lin_paramtype is not passed through F-C interface
Registry WARNING: derived data type PtFairDisplacement of type meshtype is not passed through C interface
Registry WARNING: derived data type PtFairDisplacement of type meshtype is not passed through F-C interface
Registry WARNING: derived data type ptFairleadLoad of type meshtype is not passed through C interface
Registry WARNING: derived data type ptFairleadLoad of type meshtype is not passed through F-C interface
generating ....\modules\map\src/MAP_Types.h
----- FAST Registry --------------
input file: ....\modules\map\src\MAP_Fortran_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\map\src/MAP_Fortran_Types.f90
Registry for Map completed.

Running Registry for SCDataEX
----- FAST Registry --------------
input file: ....\modules\supercontroller\src\SC_DataEx_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\supercontroller\src/SCDataEx_Types.f90
Registry WARNING: derived data type Ver of type progdesc is not passed through C interface
Registry WARNING: derived data type Ver of type progdesc is not passed through F-C interface
generating ....\modules\supercontroller\src/SCDataEx_Types.h
Registry for SCDataEX completed.

Running Registry for InflowWind_IO
----- FAST Registry --------------
input file: ....\modules\inflowwind\src\InflowWind_IO.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
generating ....\modules\inflowwind\src/InflowWind_IO_Types.f90
Registry for InflowWind_IO completed.

Running Registry for IfW_FlowField
----- FAST Registry --------------
input file: ....\modules\inflowwind\src\IfW_FlowField.txt
generating ....\modules\inflowwind\src/IfW_FlowField_Types.f90
Registry for IfW_FlowField completed.

Running Registry for Conv_Radiation
----- FAST Registry --------------
input file: ....\modules\hydrodyn\src\Conv_Radiation.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\hydrodyn\src/Conv_Radiation_Types.f90
Registry for Conv_Radiation completed.

Running Registry for ElastoDyn
----- FAST Registry --------------
input file: ....\modules\elastodyn\src\ElastoDyn_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\elastodyn\src/ElastoDyn_Types.f90
Registry for ElastoDyn completed.

Running Registry for DWM
----- FAST Registry --------------
input file: ....\modules\aerodyn14\src\Registry-DWM.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\inflowwind\src/InflowWind.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind_IO.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/Lidar.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\aerodyn14\src/DWM_Types.f90
Registry for DWM completed.

Running Registry for Waves
----- FAST Registry --------------
input file: ....\modules\seastate\src\Waves.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\seastate\src/Waves_Types.f90
Registry for Waves completed.

Running Registry for SS_Excitation
----- FAST Registry --------------
input file: ....\modules\hydrodyn\src\SS_Excitation.txt
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\hydrodyn\src/SS_Excitation_Types.f90
Registry for SS_Excitation completed.

Running Registry for BEMT
----- FAST Registry --------------
input file: ....\modules\aerodyn\src\BEMT_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/DBEMT_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\aerodyn\src/BEMT_Types.f90
Registry for BEMT completed.

Running Registry for IceFloe
----- FAST Registry --------------
input file: ....\modules\icefloe\src\interfaces\FAST\IceFloe_FASTRegistry.inp
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\icefloe\src\icefloe/IceFloe_Types.f90
Registry for IceFloe completed.

Running Registry for AeroDyn
----- FAST Registry --------------
input file: ....\modules\aerodyn\src\AeroDyn_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/BEMT_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/DBEMT_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/FVW_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AeroAcoustics_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\aerodyn\src/AeroDyn_Types.f90
Registry for AeroDyn completed.

Running Registry for Waves2
----- FAST Registry --------------
input file: ....\modules\seastate\src\Waves2.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\seastate\src/Waves2_Types.f90
Registry for Waves2 completed.

Running Registry for IceDyn
----- FAST Registry --------------
input file: ....\modules\icedyn\src\Registry_IceDyn.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\icedyn\src/IceDyn_Types.f90
Registry for IceDyn completed.

Running Registry for BeamDyn
----- FAST Registry --------------
input file: ....\modules\beamdyn\src\Registry_BeamDyn.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\beamdyn\src/BeamDyn_Types.f90
Registry for BeamDyn completed.

Running Registry for FAST
----- FAST Registry --------------
input file: ....\modules\openfast-library\src\FAST_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\elastodyn\src/ElastoDyn_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\beamdyn\src/Registry_BeamDyn.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\servodyn\src/ServoDyn_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\servodyn\src/StrucCtrl_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn14\src/Registry-AD14.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn14\src/Registry-DWM.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind_IO.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/Lidar.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AeroDyn_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/BEMT_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/DBEMT_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/FVW_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AeroAcoustics_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\subdyn\src/SubDyn_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Current.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Waves.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Waves2.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/HydroDyn.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/Conv_Radiation.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Radiation.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Excitation.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/WAMIT.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/Conv_Radiation.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Radiation.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Excitation.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/WAMIT2.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/Morison.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Current.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Waves.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Waves2.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\icefloe\src\interfaces\FAST/IceFloe_FASTRegistry.inp in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind_IO.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/Lidar.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\supercontroller\src/SC_DataEx_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\icedyn\src/Registry_IceDyn.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\feamooring\src/FEAM_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\map\src/MAP_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\map\src/MAP_Fortran_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\moordyn\src/MoorDyn_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\orcaflex-interface\src/OrcaFlexInterface.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\extptfm\src/ExtPtfm_MCKF_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
Registry warning: type ExtInfw_InputType used before defined for u
Registry warning: type ExtInfw_OutputType used before defined for y
Registry warning: type ExtInfw_ParameterType used before defined for p
Registry warning: type ExtInfw_MiscVarType used before defined for m
Registry warning: type ExtInfw_InitInputType used before defined for InData_ExtInfw
Registry warning: type ExtInfw_InitOutputType used before defined for OutData_ExtInfw
generating ....\modules\openfast-library\src/FAST_Types.f90
Error running FAST Registry for FAST.

Running Registry for AeroAcoustics
----- FAST Registry --------------
input file: ....\modules\aerodyn\src\AeroAcoustics_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\aerodyn\src/AeroAcoustics_Types.f90
Registry for AA completed.

Running Registry for Current
----- FAST Registry --------------
input file: ....\modules\seastate\src\Current.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\seastate\src/Current_Types.f90
Registry for Current completed.

Running Registry for Map
----- FAST Registry --------------
input file: ....\modules\map\src\Map_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\map\src/MAP_Fortran_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\map\src/MAP_Types.f90
Registry WARNING: derived data type LinInitInp of type lin_initinputtype is not passed through C interface
Registry WARNING: derived data type LinInitInp of type lin_initinputtype is not passed through F-C interface
Registry WARNING: derived data type Ver of type progdesc is not passed through C interface
Registry WARNING: derived data type LinInitOut of type lin_initoutputtype is not passed through C interface
Registry WARNING: derived data type Ver of type progdesc is not passed through F-C interface
Registry WARNING: derived data type LinInitOut of type lin_initoutputtype is not passed through F-C interface
Registry WARNING: derived data type LinParams of type lin_paramtype is not passed through C interface
Registry WARNING: derived data type LinParams of type lin_paramtype is not passed through F-C interface
Registry WARNING: derived data type PtFairDisplacement of type meshtype is not passed through C interface
Registry WARNING: derived data type PtFairDisplacement of type meshtype is not passed through F-C interface
Registry WARNING: derived data type ptFairleadLoad of type meshtype is not passed through C interface
Registry WARNING: derived data type ptFairleadLoad of type meshtype is not passed through F-C interface
generating ....\modules\map\src/MAP_Types.h
----- FAST Registry --------------
input file: ....\modules\map\src\MAP_Fortran_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\map\src/MAP_Fortran_Types.f90
Registry for Map completed.

Running Registry for AeroDyn14
----- FAST Registry --------------
input file: ....\modules\aerodyn14\src\Registry-AD14.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\aerodyn14\src/Registry-DWM.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind_IO.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/Lidar.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\aerodyn14\src/AeroDyn14_Types.f90
Registry for AeroDyn14 completed.

Running Registry for SubDyn
----- FAST Registry --------------
input file: ....\modules\subdyn\src\SubDyn_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\subdyn\src/SubDyn_Types.f90
Registry for SubDyn completed.

Running Registry for ServoDyn
----- FAST Registry --------------
input file: ....\modules\servodyn\src\ServoDyn_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\servodyn\src/StrucCtrl_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\servodyn\src/ServoDyn_Types.f90
Registry for ServoDyn completed.

Running Registry for HydroDyn
----- FAST Registry --------------
input file: ....\modules\hydrodyn\src\HydroDyn.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\hydrodyn\src/Conv_Radiation.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Radiation.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Excitation.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/WAMIT.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/Conv_Radiation.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Radiation.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Excitation.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/WAMIT2.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/Morison.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Current.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Waves.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/Waves2.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\hydrodyn\src/HydroDyn_Types.f90
Registry for HydroDyn completed.

Running Registry for FVW
----- FAST Registry --------------
input file: ....\modules\aerodyn\src\FVW_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\aerodyn\src/FVW_Types.f90
Registry for FVW completed.

Running Registry for StrucCtrl
----- FAST Registry --------------
input file: ....\modules\servodyn\src\StrucCtrl_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\servodyn\src/StrucCtrl_Types.f90
Registry for StrucCtrl completed.

Running Registry for FEAMooring
----- FAST Registry --------------
input file: ....\modules\feamooring\src\FEAM_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\feamooring\src/FEAMooring_Types.f90
Registry for FEAMooring completed.

Running Registry for Morison
----- FAST Registry --------------
input file: ....\modules\hydrodyn\src\Morison.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\hydrodyn\src/Morison_Types.f90
Registry for Morison completed.

Running Registry for ADI
----- FAST Registry --------------
input file: ....\modules\aerodyn\src\AeroDyn_Inflow_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\aerodyn\src/AeroDyn_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/BEMT_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/DBEMT_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/FVW_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/UnsteadyAero_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AeroAcoustics_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\aerodyn\src/AirfoilInfo_Registry.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind_IO.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/Lidar.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\aerodyn\src/AeroDyn_Inflow_Types.f90
Registry for ADI completed.

Running Registry for OrcaFlex Interface
----- FAST Registry --------------
input file: ....\modules\orcaflex-interface\src\OrcaFlexInterface.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\orcaflex-interface\src/OrcaFlexInterface_Types.f90
Registry for OrcaFlexInterface completed.

Running Registry for InflowWind
----- FAST Registry --------------
input file: ....\modules\inflowwind\src\InflowWind.txt
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/InflowWind_IO.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\inflowwind\src/IfW_FlowField.txt in usefrom mode
opening ....\modules\inflowwind\src/Lidar.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\inflowwind\src/InflowWind_Types.f90
Registry for InflowWind completed.

Running Registry for DBEMT
----- FAST Registry --------------
input file: ....\modules\aerodyn\src\DBEMT_Registry.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
generating ....\modules\aerodyn\src/DBEMT_Types.f90
Registry for DBEMT completed.

Running Registry for WAMIT
----- FAST Registry --------------
input file: ....\modules\hydrodyn\src\WAMIT.txt
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt
opening ....\modules\hydrodyn\src/Conv_Radiation.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Radiation.txt in usefrom mode
opening ....\modules\hydrodyn\src/SS_Excitation.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
opening ....\modules\seastate\src/SeaState_Interp.txt in usefrom mode
opening ....\modules\nwtc-library\src/Registry_NWTC_Library.txt in usefrom mode
generating ....\modules\hydrodyn\src/WAMIT_Types.f90
Registry for WAMIT completed.

Running Registry for OpenFOAM
----- FAST Registry --------------
input file: ....\modules\openfoam\src\OpenFOAM_Registry.txt
Registry program cannot open ....\modules\openfoam\src\OpenFOAM_Registry.txt for reading. Ending.
Error running FAST Registry for OpenFOAM.

Project : error PRJ0019: A tool returned an error code from "Running Registry for OpenFOAM"
Build log written to  "file://C:/mkdir%20NREL/openfast/vs-build/FASTlib/x64/Release_Double/BuildLog.htm"
FASTlib - 3 error(s), 0 warning(s)
2>------ Skipped Build: Project: OpenFAST-Simulink (IFORT), Configuration: Release_Matlab x64 ------
2>Project not selected to build for this solution configuration
3>------ Build started: Project: FAST (IFX), Configuration: Release_Double x64 ------
Compiling with Intel® Fortran Compiler 2023.2.0 [Intel(R) 64]...
FAST_Prog.f90
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(34): error #7002: Error in opening the compiled module file.  Check INCLUDE paths.   [FAST_SUBS]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(39): error #6683: A kind type parameter must be a compile-time constant.   [DBKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(39): warning #8586: Implicit type is given to allow out-of-order declaration. Non-standard extension.   [DBKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(39): error #6592: This symbol must be a defined parameter, an enumerator, or an argument of an inquiry function that evaluates to a compile-time constant.   [DBKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(39): error #6975: A kind-param must be a digit-string or a scalar-int-constant-name.   [DBKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(40): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(43): error #6457: This derived type name has not been declared.   [FAST_TURBINETYPE]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(45): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(46): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(47): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(48): warning #8586: Implicit type is given to allow out-of-order declaration. Non-standard extension.   [ERRMSGLEN]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(48): warning #6187: Fortran 2003 requires an INTEGER data type in this context.
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(54): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(179): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(184): error #6683: A kind type parameter must be a compile-time constant.   [INTKI]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(61): error #6404: This name does not have a type, and must have an explicit type.   [PROGNAME]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(61): warning #6931: Fortran 2003 does not allow this assignment statement.   ['OpenFAST']
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(65): error #6632: Keyword arguments are invalid without an explicit interface.   [FLAG]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(65): error #6632: Keyword arguments are invalid without an explicit interface.   [ARG2]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(68): error #6404: This name does not have a type, and must have an explicit type.   [TURBINE]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(77): error #6404: This name does not have a type, and must have an explicit type.   [ERRID_NONE]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(77): error #6632: Keyword arguments are invalid without an explicit interface.   [SKIPRUNTIMEMSG]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(122): warning #6187: Fortran 2003 requires an INTEGER data type in this context.   [N_TMAX_M1]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(128): error #6363: The intrinsic data types of the arguments must be the same.   [MOD]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(128): error #6460: This is not a component name that is defined in the encompassing structure.   [FOUNDSTEADY]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(128): warning #6188: Fortran 2003 requires a LOGICAL data type in this context.   [FOUNDSTEADY]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(128): warning #6188: Fortran 2003 requires a LOGICAL data type in this context.
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(128): warning #6192: Fortran 2003 does not allow this data type conversion.
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(128): warning #6188: Fortran 2003 requires a LOGICAL data type in this context.
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(129): error #6362: The data types of the argument(s) are invalid.   [TRIM]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(129): error #6404: This name does not have a type, and must have an explicit type.   [NUM2LSTR]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(129): error #6362: The data types of the argument(s) are invalid.   [TRIM]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(132): error #6404: This name does not have a type, and must have an explicit type.   [ABORTERRLEV]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(132): error #6404: This name does not have a type, and must have an explicit type.   [ERRID_SEVERE]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(133): error #6363: The intrinsic data types of the arguments must be the same.   [MIN]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(134): error #6404: This name does not have a type, and must have an explicit type.   [NEWLINE]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(134): error #6054: A CHARACTER data type is required in this context.   [NEWLINE]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(152): warning #6188: Fortran 2003 requires a LOGICAL data type in this context.   [FOUNDSTEADY]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(152): error #6341: A logical data type is required in this context.   [FOUNDSTEADY]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(158): warning #6188: Fortran 2003 requires a LOGICAL data type in this context.   [CALCSTEADY]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(158): warning #6188: Fortran 2003 requires a LOGICAL data type in this context.   [FOUNDSTEADY]
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(158): warning #6188: Fortran 2003 requires a LOGICAL data type in this context.
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(158): warning #6188: Fortran 2003 requires a LOGICAL data type in this context.
C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90(159): error #6404: This name does not have a type, and must have an explicit type.   [ERRID_FATAL]
C:\Users\kanwa\AppData\Local\Temp\337635.i90(211): catastrophic error: Too many errors, exiting
compilation aborted for C:\mkdir NREL\openfast\glue-codes\openfast\src\FAST_Prog.f90 (code 1)
Build log written to  "file://C:/mkdir%20NREL/openfast/vs-build/FAST/x64/Release_Double/BuildLog.htm"
FAST - 31 error(s), 14 warning(s)
========== Build: 0 succeeded, 2 failed, 2 up-to-date, 1 skipped ==========

Are you using the latest dev branch? It looks like the last commit to that branch broke the Visual Studio build. I will try to get a fix for that soon. Otherwise you could use an earlier version of that branch or the main branch.

Does this mean that I need to reinstall OpenFast again and an earlier version of it.
Sorry, but I can't understand what is meant by dev branch?
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Bonnie Jonkman @.>
Sent: Wednesday, July 19, 2023 7:03:08 PM
To: OpenFAST/openfast @.>
Cc: Zulfiqar Kanwar @.>; Author @.>
Subject: Re: [OpenFAST/openfast] Openfast compilation using visual studio (Issue #1697)
Are you using the latest dev branch? It looks like the last commit to that branch broke the Visual Studio build. I will try to get a fix for that soon. Otherwise you could use an earlier version of that branch or the main branch.
—
Reply to this email directly, view it on GitHubhttps://github.com/OpenFAST/openfast/issues/1697#issuecomment-1642362397, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBLO7AONVNEQPIZOYIK62MTXRAALZANCNFSM6AAAAAA2QBNMWU.
You are receiving this because you authored the thread.Message ID: @.***>

I downloaded from here...
https://github.com/OpenFast/openfast
Also, i used the video to download whats required
https://www.youtube.com/watch?v=K4lOK1gUqzI

@bjonkman Is there a way to solve these or Should I start everything again

The pull request is now merged in dev.


non-library Components should generate classes

This is great for creating simple views that are not part of a window layout.
Everything that is a component should have a generated class. We also should not rely on quotation marks "" for marking a class to be generated. Generate code from all components unless ignored with "//" or "#".
TODO: discuss this in more detail.

We should probably only export to a class if using both quotation marks "" and it's a component.


Import Wizard doesn't save name as property

I have imported geofence.json from poracle. Property name, eg. "name": "london", got saved as geofence's name but not as a database name property so in fact in api and in export geofences won't have a name

I can't seem to replicate this.
Have you deleted your name/database property?
Do you have a custom name/string property?
^Shouldn't technically matter since this is the db query but asking anyway.
        let record = Entity::find()
            .filter(property::Column::Name.eq("name"))
            .filter(property::Column::Category.eq("database"))
            .one(db)
            .await?;

Reread your comment and I guess you must be referring to a name/string property. I added a name/string prop to my koji and imported some fences from a poracle style json but it still saved them as a name/database property so I'm not sure what happened for you.

Ideally #144 is replacing the need to have a custom name/string property anyway.


[Feature] backups utilize xz compression

It would be nice if, in addition to gzip, bzip2, and snappy, the backup system also supported xz compression.
https://cloudnative-pg.io/documentation/1.19/backup_recovery/#compression-algorithms
related to : https://github.com/EnterpriseDB/barman/issues/754

Hi @jcpunk when that it's supported on Barman, we can work on this, before that, as you can guess, we can't =), doesn't seem like they will put some work on this, so I'm closing this issue, it can be opened in the future for sure! hopefully they will support xz.
Regards!


Fixed the topic_entity_tag create_tag end point to check for existing tag and return the tag data (curie+name)

Thanks @azurebrd


Charts plugins development integration in Superset

Hello,
I successfully implemented a custom chart which work inside a storybook following the repo here: https://github.com/apache-superset/superset-ui-plugins-template.
Now, I'm trying to integrate that custom chart into a superset instance.
Update; I found some indication at https://github.com/apache-superset/superset-ui/blob/master/docs/debugging.md which mention npm link to hook plugins into a Superset instance.
So I did this as follow:

Start all services but superset-node from incubator-superset/docker/
In incubator-superset/superset-frontend/ trigger npm run dev-server
In superset-plugins-template/package/superset-ui-plugin-chart-dummy hit npm link
In incubator-superset/superset-frontend/ hit npm link superset-ui-plugin-chart-dummy
In incubator-superser/superset-frontend/src/visualizations/presets/MainPreset.js add below the others import DummyChartPlugin from 'superset-ui-plugin-chart-dummy/src';

Now the last step make the dev server return an error:
ERROR in ./node_modules/superset-ui-plugin-chart-dummy/src/DummyChart.tsx 42:16
Module parse failed: Unexpected token (42:16)
You may need an appropriate loader to handle this file type.
|     DummyChart.prototype.render = function () {
|         var _a = this.props, data = _a.data, height = _a.height, width = _a.width;
>         return (<svg style={{ backgroundColor: '#ffe459', borderRadius: 8, height: height, width: width }}>
|         {data.map(function (_a) {
|             var x = _a.x, y = _a.y;
 @ ./node_modules/superset-ui-plugin-chart-dummy/src/index.ts 47:88-111
 @ ./src/visualizations/presets/MainPreset.js
 @ ./src/setup/setupPlugins.ts
 @ ./src/addSlice/App.jsx
 @ ./src/addSlice/index.jsx
 @ multi (webpack)-dev-server/client?http://localhost:9000 (webpack)/hot/dev-server.js babel-polyfill ./src/preamble.js ./src/addSlice/index.jsx

It appears that incubator-superset/superset-frontent/webpack.config.js needs to be adapted to match what superset-ui-plugins-template in its own webpack.config.js; added the following rule:
--- a/superset-frontend/webpack.config.js
+++ b/superset-frontend/webpack.config.js
@@ -211,6 +211,27 @@ const config = {
         ],
       },
       {
+        test: /\.(jsx|tsx)?$/,
+        include: /node_modules\/superset\-ui\-plugin\-chart\-dummy\/src/,
+        use: [
+          {
+            loader: 'babel-loader',
+            options: {
+              presets: [
+                ['@babel/preset-env', { useBuiltIns: 'entry', corejs: 3 }],
+                '@babel/preset-react',
+                '@babel/preset-typescript',
+              ],
+              plugins: [
+                '@babel/plugin-proposal-object-rest-spread',
+                '@babel/plugin-proposal-class-properties',
+                '@babel/plugin-syntax-dynamic-import',
+              ]
+            },
+          },
+        ],
+      },
+      {
         test: /\.css$/,
         include: [APP_DIR, /superset[-]ui.+\/src/],
         use: [

Did you get a message about missing @babel/preset-typescript?

Did you get a message about missing @babel/preset-typescript when you're trying to run npm run dev-server in Superset itself?

I dont recall that but you might need to trigger npm run build before...

Did you get a message about missing @babel/preset-typescript when you're trying to run npm run dev-server in Superset itself?

I got the same.
It also complained about another package: plugin-proposal-export-default-from.  I did:
npm install @babel/plugin-proposal-export-default-from --save-dev
npm install @babel/preset-typescript --save-dev

I also did an npm run build for good measure and compiled without issue.
@trepmag  your posts were really helpful.
I've been poking around the superset repos looking to see what needs to be done to get a make a functional visualization plugin.
Aside from adding to MainPreset.js were there other changes required to get it to appear as an option in the ui chart list?
Looks to me like setupPluginsExtra.ts is where they intend viz plugins to be registered, as opposed to adding to MainPreset.js, but the whole registration/preset flow isn't very clear to me yet.
Have you

Things did not really work out that well for me, partly cause I was importing .less files, of which I edited the webpack configs for Storybook. But I resolved my issue now.
I decided to do what the official plugins do, which is to let the main entry be lib/index.js instead of src. This is already specified in package.json. Then in Step 5 above, instead of ending the import with /src, we can have import DummyChartPlugin from 'superset-ui-plugin-chart-dummy'. Letting superset-frontendimport your plugin fromlibshould also remove the need for additional dependencies (like@babel/preset-typescript`, unless if your plugin somehow requires that (despite the build process).
Though to get this to work, you must first build your plugins by running npm run build at the root of the repo, so that it builds your src files into lib (and esm). You might run into the following error:
... Duplicate identifier 'LibraryManagedAttributes'.

This will appear if you have already did npm link in your plugin, which will then create a node_modules file with the dependencies that your plugin needs.

Aside from adding to MainPreset.js were there other changes required to get it to appear as an option in the ui chart list?
Looks to me like setupPluginsExtra.ts is where they intend viz plugins to be registered, as opposed to adding to MainPreset.js, but the whole registration/preset flow isn't very clear to me yet.

I agree. It's not the best, not especially if you want to just package things up in docker. I'm keeping an eye out on item 4 in SIP-38.
But for now, editing the MainPreset.js file should immediately do what you want (getting the viz to show up in the ui chart list).

Thanks @japorized  that's great, I've got it compiling now.

I agree. It's not the best, not especially if you want to just package things up in docker. I'm keeping an eye out on item 4 in SIP-38.

Same here.
While tinkering around with the plugin I'm running yarn babel --watch, and over in the superset-frontend directory I'm running the dev server. So edits made in the plugin folder get compiled and then trigger a hot reload over in the superset frontend. There's probably a more efficient way to do it but it works and removes a manual build step.

Little follow up:
I ended up reverting my changes to MainPreset.js as I was able to get the dummy chart plugin appearing in the chart list via the setupPluginsExtra.js hook:
import DummyChartPlugin from 'superset-ui-plugin-chart-dummy'

// For individual deployments to add custom overrides
export default function setupPluginsExtra() {
    new DummyChartPlugin()
        .configure({ key: 'dummychart' })
        .register();
}

Interesting @spatialbits. Thanks for the follow up. Will give that a try on my end as well.
Just a side question, though still on the topic; how does one get the data from the Flask backend into our visualizations? I've poked around with the viz.py file (and I think one other file that I can't remember) but Flask kept telling me that I've made only an empty query.

I was getting that too.  I ended up adding some controls to the control panel in the DummyChart plugin:
export default class DummyChartPlugin extends ChartPlugin {
  constructor() {
    // What is loaded here is an object that implements the ChartPluginConfig interface
    super({
      // loadChart: () => import('./DummyChart'), // lazy load it.
      Chart: DummyChart,
      controlPanel: {
        controlPanelSections: [
          {
            label: t('Query'),
            expanded: true,
            controlSetRows: [
              ['all_columns_x', 'all_columns_y'],
              ['adhoc_filters'],
              ['row_limit', null]
            ],
          },
        ]
      },
      metadata,
      transformProps,
    });
  }
}

Then the all_columns_x and all_columns_y selections get passed into the viz.py backend as form_data kwargs.
Now I'm still not a 100% clear on how query the syntax goes, I think you have to hunt around the other viz.py classes, but in your viz class, you need to override the query_obj metho, and define the query you want there. Mine looks like:
   def query_obj(self):
        form_data = self.form_data
        d = super().query_obj()

        d["is_timeseries"] = self.form_data.get("time_series_option", "not_time")
 for x, y and size"))

        d["columns"] = [form_data.get("all_columns_x"), form_data.get("all_columns_y")]
        return d

Which seems to tell the query builder to select those columns from the db.
You also need to override the get_data method and return something that your chart will understand on the frontend:

def get_data(self, df: pd.DataFrame) -> VizData:
    data = # do something to your dataframe to get the data you want, make it json serializable
    return {'somedata': data}

Then lastly, and back in your plugin, you see the transformProps property on the DummyChartPlugin declaration. That function receives the data returned by api (what you produced in get_data) and puts that into the chart. It's defined in transformProps.ts:
export default function transformProps(chartProps: ChartProps) {
  console.log('Transforming props for Dummy Chart', chartProps);
  const { width, height, formData, queryData } = chartProps;
  const { color } = formData;
  const { data } = queryData;

  return {
    width,
    height,
    color,
    data,
  };
}

Then lastly, in DummyChart.tsx, you modify the DummyChartProps to accept the modified incoming viz data object and use those props in the chart itself:
export type DummyChartProps = {
  height: number;
  width: number;
  data: { somedata: number };
};

export default class DummyChart extends React.PureComponent<DummyChartProps> {
  render() {
    const { data, height, width } = this.props;
    return (

        {data.somedata}

    );
}

There's a lot I still have to work out. Please feel free to point out anything you see wrong there.

Hi, I took a dab and made importing ts files from plugins work more smooth: https://github.com/apache/incubator-superset/pull/9326
There's still some issue related to React hot reloading that I wasn't able to resolve. The PR has more details. If someone could help me debug or have ideas for directions, that would be great!

Hi All,
I'm trying to integrate a plugin within Superset but I'm not succeeding.
I followed the steps listed in the readme  to add a new plugin created by me.

created a plugin
run yarn install && build (in the my plugin)
enabled the link in the plugin and in the local package to superset-frontend(using a name of the package plugin)
insert in the setupPluginsExtra.js file the my plugin
new MapChartPlugin().configure({ key: 'map' }).register();
run the npm run dev-server command
went to the Create a new superset chart page and chose my plugin.

Unfortunately in the explore page i don't see my plugin.
After this I have followed your updates posted in this page: https://github.com/apache/incubator-superset/pull/9326 but nothing.
I always have the same error, in the exploration shows me the name of the key with which I registered the plugin and in the console of the browser in the url

localhost:8088/superset/explore_json

returns 500 INTERNAL SERVER ERROR
This is my view after the created of the new chart:

Could someone help me?
Thank you

That really is where the readme ends and we're sort of left with digging around. I apologize that I don't have a clean answer for you, but try looking at the viz.py file in incubator-superset/superset/. You'll see how the other visualizations are hooked up to the Python-side of Superset from there. We can't really help you out too much here cause it depends on the data that your viz needs.
You may run into an empty_query? problem. You can check out @spatialbits' attempt here. Unfortunately, I haven't had a chance to try this myself, so I'm not sure if it will completely resolve the empty_query? problem.

Hi @japorized,
thanks for answering me.
I am a little confused because I have not read anywhere that the viz file should be modified when I want to add my plugin. I thought it was automatic and the data was mapped using the information present in transformProps file.
I'll try your suggestion!
I'm new to superset and I'm trying to learn how to use it.
Thanks :)

Yeah, I get how you feel cause I was in the same boat. I think the discussion right now on the main Superset repo is that the project is trying to figure out how to easily let 3rd party visualizations be added to Superset without them having to modify Superset in any way, so a plugin system. However, this is not so much of a priority for the project right now, so things on this front are moving at a slower pace.
I apologize that I can’t be of much help but good luck!


Uncaught TypeError: Cannot read property 'remove' of undefined

[Enter steps to reproduce:]

...
...

Atom: 1.40.1 x64
Electron: 3.1.10
OS: Ubuntu 18.04.3
Thrown From: script package 3.25.0
Stack Trace
Uncaught TypeError: Cannot read property 'remove' of undefined
At /home/paul/.atom/packages/script/node_modules/atom-message-panel/lib/MessagePanelView.js:189

TypeError: Cannot read property 'remove' of undefined
    at ScriptView.MessagePanelView.remove (/packages/script/node_modules/atom-message-panel/lib/MessagePanelView.js:189:30)
    at ScriptView.detach (/packages/open-in-browsers/node_modules/jquery/dist/jquery.js:5357:15)
    at ScriptView.removePanel (/packages/script/lib/script-view.js:89:10)
    at Object.closeScriptViewAndStopRunner (/packages/script/lib/script.js:161:21)
    at HTMLElement.scriptCloseView (/packages/script/lib/script.js:94:39)
    at CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app/static/<embedded>:11:349123)
    at CommandRegistry.dispatch (/usr/share/atom/resources/app/static/<embedded>:11:347598)
    at ScriptView.close (/packages/script/lib/script-view.js:99:19)
    at /packages/open-in-browsers/node_modules/space-pen/lib/space-pen.js:220:36)
    at HTMLDivElement.dispatch (/packages/open-in-browsers/node_modules/jquery/dist/jquery.js:4435:9)
    at HTMLDivElement.elemData.handle (/packages/open-in-browsers/node_modules/jquery/dist/jquery.js:4121:28)

Commands
  4x -0:24.8.0 core:save (input.hidden-input)
     -0:22.7.0 core:close (input.hidden-input)
     -0:22 editor:consolidate-selections (input.hidden-input)
     -0:22 core:cancel (input.hidden-input)
     -0:21.4.0 editor:consolidate-selections (input.hidden-input)
     -0:21.4.0 core:cancel (input.hidden-input)
     -0:21.2.0 editor:consolidate-selections (input.hidden-input)
     -0:21.2.0 core:cancel (input.hidden-input)
     -0:21.1.0 editor:consolidate-selections (input.hidden-input)
     -0:21.1.0 core:cancel (input.hidden-input)
     -0:20.9.0 editor:consolidate-selections (input.hidden-input)
     -0:20.9.0 core:cancel (input.hidden-input)
     -0:20.7.0 editor:consolidate-selections (input.hidden-input)
     -0:20.7.0 core:cancel (input.hidden-input)
     -0:14.3.0 core:close (atom-pane.pane.active)
     -0:05.7.0 script:close-view (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)

Non-Core Packages
emmet 2.4.3
open-in-browsers 0.0.30
script 3.25.0

when ever I try to run my code by pressing keys ctrl + shift + B. The down pane opens up and shows output of the code. When ever I try to close the pane it raises an error. Please look into this issue, it's very irritating.

Im trying to fix this, but for know fou can use ctrl-shift-f5. And i know, it's not solution

when ever I try to run my code by pressing keys ctrl + shift + B. The down pane opens up and shows output of the code. When ever I try to close the pane it raises an error. Please look into this issue, it's very irritating.

I am getting the same error. It was fine until yesterday. I think there is something wrong with the library that deals with MessagePanelView

This shows up on other keyboard shortcuts not dealing with the module as well. Not able to close active tabs using cmd + w is really annoying

When the output window is stuck already, i also get an error thrown when I press ESC

This same issue is happening in Mac OS as well.
Atom: 1.41.0
OS : Catalina 10.15.1.

The same error occurs when I try to kill this process.
Atom 1.41.0 x64，win10

Same issue here

This same issue is happening in Mac OS as well.
Atom: 1.41.0
OS : Catalina 10.15.1.

+1

+1

Same issue here. Windows 10, Atom 1.41.0 x64

Same issue, also occurs when I press ESC. Ubuntu 18.04, Atom 1.40.0

same with @AStartledRaccoon

Still no solution to this issue? :(

Here's a temporary solution. Modify line 89 in
.atom\packages\script\node_modules\atom-message-panel\lib\MessagePanelView.js to
MessagePanelView.prototype.remove = function (index) {   this.messages.splice(-index, 1);   this.body.children()[index].remove(); };
to
MessagePanelView.prototype.remove = function (index) {   $('.native-key-bindings.script-view').remove(); };

@medardm 's solution worked for me!

@AStartledRaccoon I'm glad it worked. :)

It works also for me thanks

[Enter steps to reproduce:]

...
...

Atom: 1.41.0 x64
Electron: 4.2.7
OS: Mac OS X 10.15
Thrown From: script package 3.25.0
Stack Trace
Uncaught TypeError: Cannot read property 'remove' of undefined
At /Users/jasonli/.atom/packages/script/node_modules/atom-message-panel/lib/MessagePanelView.js:188

Thank's @medardm for the fix !
Maybe you could made a pull request to include it ?

I will when I find a long term solution. Because the solution I introduced was an adjustment with one of the dependencies, not with the actual package.

When I press escape and or try to close the output panel I get this error.

@medardm Could you tell us which dependecy you used? So we can use your fix. Thanks!

@medardm Thanks for the fix!!!

@medardm thanks I hadn't seen that solution. It works

same issue here, please fix it!
Windows 10 | Atom 1.41.0 x64

I didn't change any of the dependencies, just modified a line of code on one of the dependencies of this package, but this is not a long term solution.

Here's a temporary solution. Modify function in line 187 under
.atom\packages\script\node_modules\atom-message-panel\lib\MessagePanelView.js
from
MessagePanelView.prototype.remove = function (index) {
  this.messages.splice(-index, 1);
  this.body.children()[index].remove();
};

to:
MessagePanelView.prototype.remove = function (index) {
  $('.native-key-bindings.script-view').remove();
};

Just downloaded this package and found this bug, please fix it!

@Fellox . There's already a PR to fix this issue (#2004). You can review it on your side. I already checked it and it works

Here's a temporary solution. Modify function in line 187 under
.atom\packages\script\node_modules\atom-message-panel\lib\MessagePanelView.js
from
MessagePanelView.prototype.remove = function (index) {
  this.messages.splice(-index, 1);
  this.body.children()[index].remove();
};

to:
MessagePanelView.prototype.remove = function (index) {
  $('.native-key-bindings.script-view').remove();
};

That is the solution for now. Thanks for it. :)

nice bro, works for me.
Thanks!

This hasn't worked for me :(
Also, editing the files seems to have no effect, even if I intentionally add syntax errors or just comment out the code. I'm looking in <Username>\.atom\packages\script\node_modules\atom-message-panel\lib.

This hasn't worked for me :(
Also, editing the files seems to have no effect, even if I intentionally add syntax errors or just comment out the code. I'm looking in <Username>\.atom\packages\script\node_modules\atom-message-panel\lib.

I had a similar problem. Gave up on it for now.

I also still have this issue. Panel could be removed after modifying the source as you suggested, but it was only working one time. I mean, if I removed the panel before and run again the script, then I cannot remove the panel.

@junepark6  I had a similar problem.

@wesgt That appears to have worked for me as well. Thanks!

It fixed itself for me... Didn't make any changes, but all's good now! :)

@wesgt  I now have a problem after your fix where i cant run the program after i close the script window

@wesgt thanks!


Admin forced password reset tests

Test case was added with https://github.com/wso2/product-is/pull/817. Therefore closing this PR.


Get File add option to compress data

Originally submitted to Google Code by Marcin.Koperski on 4 Mar 2013

It would be useful to add option to compress files before downloading them and later  decompress to save network usage.
I would be especially use full for text files.
Option could specify how to compress data for example zip, tar etc.

This issue is more than 10 years old and did not create any attention. Closing this issue until further feedback.


[type:improve] Get rid of the dead code and add some improvements

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

@Aias00 pls, review this pr, tks


How to evaluate local model with local-completions?

I installed lm_eval on my laptop and would like to evaluate local model running on another server. Could anyone help me on how to run the command? Any parameters I set in wrong? Or any other information I should provide? Thanks a lot!
The command I ran like below:
lm_eval --model local-completions --tasks mmlu_college_biology --model_args model=Meta-Llama-3.1-8B-Instruct,base_url=http://:/v1/completions,num_concurrent=1,max_retries=3,tokenized_requests=False
While I got below output:
2024-10-14:11:53:33,690 INFO     [main.py:279] Verbosity set to INFO
2024-10-14:11:54:14,581 INFO     [main.py:376] Selected Tasks: ['mmlu_college_biology']
2024-10-14:11:54:14,639 INFO     [evaluator.py:164] Setting random seed to 0 | Setting numpy seed to 1234 | Setting torch manual seed to 1234 | Setting fewshot manual seed to 1234
2024-10-14:11:54:14,640 INFO     [evaluator.py:201] Initializing local-completions model, with arguments: {'model': 'Meta-Llama-3.1-8B-Instruct', 'base_url': 'http://<IP_ADDRESS>:9997/v1/completions', 'num_concurrent': 1, 'max_retries': 3, 'tokenized_requests': False}
2024-10-14:11:54:14,640 INFO     [api_models.py:111] Using max length 2048 - 1
2024-10-14:11:54:14,640 INFO     [api_models.py:114] Concurrent requests are disabled. To enable concurrent requests, set num_concurrent > 1.
2024-10-14:11:54:14,640 INFO     [api_models.py:124] Using tokenizer huggingface
Traceback (most recent call last):
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\utils_http.py", line 406, in hf_raise_for_status
response.raise_for_status()
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\requests\models.py", line 1024, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://huggingface.co/Meta-Llama-3.1-8B-Instruct/resolve/main/tokenizer_config.json
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\transformers\utils\hub.py", line 402, in cached_file
resolved_file = hf_hub_download(
^^^^^^^^^^^^^^^^
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\utils_deprecation.py", line 101, in inner_f
return f(*args, **kwargs)
^^^^^^^^^^^^^^^^^^
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\utils_validators.py", line 114, in _inner_fn
return fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\file_download.py", line 1232, in hf_hub_download
return _hf_hub_download_to_cache_dir(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\file_download.py", line 1339, in _hf_hub_download_to_cache_dir
_raise_on_head_call_error(head_call_error, force_download, local_files_only)
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\file_download.py", line 1854, in _raise_on_head_call_error
raise head_call_error
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\file_download.py", line 1746, in _get_metadata_or_catch_error
metadata = get_hf_file_metadata(
^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\utils_validators.py", line 114, in _inner_fn
return fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\file_download.py", line 1666, in get_hf_file_metadata
r = _request_wrapper(
^^^^^^^^^^^^^^^^^
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\file_download.py", line 364, in _request_wrapper
response = _request_wrapper(
^^^^^^^^^^^^^^^^^
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\file_download.py", line 388, in _request_wrapper
hf_raise_for_status(response)
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\huggingface_hub\utils_http.py", line 454, in hf_raise_for_status
raise _format(RepositoryNotFoundError, message, response) from e
huggingface_hub.errors.RepositoryNotFoundError: 401 Client Error. (Request ID: Root=1-670c95e9-16fbdf657452e8740053bb10;b1f41d63-9a3c-4e63-ac5c-0a51d0718275)
Repository Not Found for url: https://huggingface.co/Meta-Llama-3.1-8B-Instruct/resolve/main/tokenizer_config.json.
Please make sure you specified the correct repo_id and repo_type.
If you are trying to access a private or gated repo, make sure you are authenticated.
Invalid username or password.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\transformers\utils\hub.py", line 425, in cached_file
raise EnvironmentError(
OSError: Meta-Llama-3.1-8B-Instruct is not a local folder and is not a valid model identifier listed on 'https://huggingface.co/models'
If this is a private repository, make sure to pass a token having permission to this repo either by logging in with huggingface-cli login or by passing token=<your_token>
python-BaseException

Hi! It uses the model name to look up the tokenizer from huggingface, where the repo address is meta-llama/Llama-3.1-8B-Instruct. You can also provide a different one by passing in  tokenizer=..., if your API requires the model name in a particular format.

@baberabb Thanks a lot for the answer. And I've tried while met another issue wish you can help.
Let me clarify my evironment. We have a server A on which the model "Meta-Llama-3.1-8B-Instruct" is loaded through Xinference. And I set up lm_eval on my laptop. I wish using lm_eval on my labtop to evaluate the model on server A through openai completions API.
Now I use below command (any parameters wrong?):
lm_eval --model local-completions --tasks mmlu_college_biology --model_args model=Meta-Llama-3.1-8B-Instruct,tokenizer="d:/llm/model/Meta-Llama-3.1-8B-Instruct",base_url=http://:/v1/completions
And get below output:
2024-10-21:17:49:43,923 INFO     [main.py:279] Verbosity set to INFO
2024-10-21:17:50:26,636 INFO     [main.py:376] Selected Tasks: ['mmlu_college_biology']
2024-10-21:17:50:26,702 INFO     [evaluator.py:164] Setting random seed to 0 | Setting numpy seed to 1234 | Setting torch manual seed to 1234 | Setting fewshot manual seed to 1234
2024-10-21:17:50:26,702 INFO     [evaluator.py:201] Initializing local-completions model, with arguments: {'model': 'Meta-Llama-3.1-8B-Instruct', 'tokenizer': 'd:/llm/model/Meta-Llama-3.1-8B-Instruct', 'base_url': 'http://<IP_ADDRESS>:9997/v1/completions'}
2024-10-21:17:50:26,702 INFO     [api_models.py:111] Using max length 2048 - 1
2024-10-21:17:50:26,702 INFO     [api_models.py:114] Concurrent requests are disabled. To enable concurrent requests, set num_concurrent > 1.
2024-10-21:17:50:26,702 INFO     [api_models.py:124] Using tokenizer huggingface
2024-10-21:17:50:31,040 WARNING  [model.py:422] model.chat_template was called with the chat_template set to False or None. Therefore no chat template will be applied. Make sure this is an intended behavior.
2024-10-21:17:50:31,045 INFO     [task.py:415] Building contexts for mmlu_college_biology on rank 0...
100%|██████████| 144/144 [00:00<00:00, 221.67it/s]
2024-10-21:17:50:31,715 INFO     [evaluator.py:489] Running loglikelihood requests
Requesting API:   0%|          | 0/576 [00:00<?, ?it/s]2024-10-21:17:50:32,327 WARNING  [api_models.py:347] API request failed with error message: Internal Server Error: 1 validation error for CreateCompletionRequest
prompt
str type expected (type=type_error.str). Retrying...
2024-10-21:17:50:34,457 WARNING  [api_models.py:347] API request failed with error message: Internal Server Error: 1 validation error for CreateCompletionRequest
prompt
str type expected (type=type_error.str). Retrying...
2024-10-21:17:50:36,686 WARNING  [api_models.py:347] API request failed with error message: Internal Server Error: 1 validation error for CreateCompletionRequest
prompt
str type expected (type=type_error.str). Retrying...
Traceback (most recent call last):
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\concurrent\futures_base.py", line 449, in result
return self.__get_result()
^^^^^^^^^^^^^^^^^^^
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\concurrent\futures_base.py", line 401, in __get_result
raise self.exception
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\tenacity_init.py", line 478, in call
result = fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^
File "D:\pythonProject\EleutherAI\lm-evaluation-harness\lm_eval\models\api_models.py", line 350, in model_call
response.raise_for_status()
File "C:\Users\zhuotao.liu\AppData\Local\miniforge3\envs\EAI_env\Lib\site-packages\requests\models.py", line 1024, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http://<IP_ADDRESS>:9997/v1/completions
python-BaseException
Requesting API:   0%|          | 0/576 [04:00<?, ?it/s]
I checked that the REST API request.body is like below. It's not wrapped into the requested openai completions API format.
{"model": "Meta-Llama-3.1-8B-Instruct", "prompt": [[791, 2768, 527, 5361, 5873, 4860, 320, 4291, 11503, 8, 922, 7926, 34458, 382, 32, 19646, 1481, 5620, 98486, 706, 17551, 1202, 19335, 304, 279, 4219, 315, 264, 220, 20, 4771, 6418, 7732, 52346, 11, 323, 279, 19335, 617, 15196, 67, 1139, 83861, 13, 763, 6300, 2015, 320, 42450, 311, 4994, 705, 1148, 39881, 323, 20438, 13918, 1053, 279, 83861, 13123, 439, 814, 8343, 872, 1648, 9017, 279, 4994, 315, 279, 52346, 30, 320, 2520, 40075, 11, 9855, 430, 279, 4248, 1814, 34965, 706, 2736, 21536, 1022, 6724, 29275, 32, 13, 393, 411, 26, 6156, 865, 982, 76, 26, 14580, 865, 982, 76, 26, 64603, 25113, 2411, 26, 6156, 1343, 385, 336, 26, 14580, 1343, 385, 336, 26, 49370, 198, 33, 13, 393, 411, 26, 14580, 865, 982, 76, 26, 6156, 865, 982, 76, 26, 64603, 25113, 2411, 26, 14580, 1343, 385, 336, 26, 6156, 1343, 385, 336, 26, 49370, 198, 34, 13, 393, 411, 26, 14580, 865, 982, 76, 26, 6156, 865, 982, 76, 26, 64603, 25113, 2411, 26, 6156, 1343, 385, 336, 26, 14580, 1343, 385, 336, 26, 49370, 198, 35, 13, 393, 411, 26, 6156, 865, 982, 76, 26, 14580, 865, 982, 76, 26, 64603, 25113, 2411, 26, 14580, 1343, 385, 336, 26, 6156, 1343, 385, 336, 26, 49370, 198, 16533, 25, 356]], "temperature": 0, "max_tokens": 1, "logprobs": 1, "seed": 1234, "echo": true}'

looks like your API requires a str prompt. You can set tokenized_requests=False in the model args (the tokens will be decoded back to strings). Also might want to add --apply_chat_template (optionally with --fewshot_as_multiturn) to wrap the prompt in a chat template. Some more explainations here


Adds spacefarm.digital to list of websites

Great site! Looks like there is now a merge conflict. Could you please rebase so I can merge? Thanks!

Added


Getting C code also C++ compilable

Getting C code also C++ compilable

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Failing Tests
ASAN C++ : #11737
Basic Tests C & C++ Linux [opt] : #11737
Basic Test Windows : #12201
Basic Test Windows (Internal CI) : #12245
Cloud To Prod Interop : #10763
Msan C : #12201
Msan C (Internal CI) : #10894
UBsan C : #12312
UBsan C (Internal CI) : #12312
gRPC interop Pull requests : #10763


Installation woes

Hello,
I would really like to give hypothesis a whirl within logseq.
However I get the following error when trying to install
[Error] :unexpected EOF
Any pointers appreciated? Can you tell me if there is somewhere I can take a look at richer logs?
Cheers
Jem

Well, after reading your README.md I realised I needed to install hypothesis pnmn etc first..and then the plugin.
Closing. Its not very obvious though if you are just a logseq user..


configure project with --yes option does not suppress "Which setting do you want to configure?" question

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm i -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
14.15.3
Amplify CLI Version
5.1.2
What operating system are you using?
Ubuntu
Amplify Categories
hosting
Amplify Commands
configure project
Describe the bug
When running the project configure command with the --yes param I keep getting prompted with the "Which setting do you want to configure?" question. Because of this I can't automate deployment.
Expected behavior
When using the --yes param I expect the question to not be prompted and the default option "Project information" to be chosen.
Reproduction steps
Running the project configure example script (with valid config) from https://docs.amplify.aws/cli/usage/headless#sample-script-1 should trigger the question prompt.
GraphQL schema(s)
No response
Log output
No response
Additional information
No response

It looks like this is coming from headless containers flow, since headless flow for containers is not currently supported.
Marking this is an enhancement. Will review with the team if we can provide an option to go through just project configuration without container hosting setup.


Error while executing JUnit Test Reports

i was enabled postbuild JUnit text reports but i got bellow error in console output and build was successful complted .
ERROR: Step ‘Publish JUnit test result report’ aborted due to exception:
org.dom4j.DocumentException: Error on line 1 of document  : Content is not allowed in prolog. Nested exception: Content is not allowed in prolog.

it was path issue, finally i got solution.

i it was path issue finally i got solution.


Better integration of standard markdown links within Dendron functionalities

Please select if your request is either something new or an enhancement

[ X] Enhancement of an existing Feature.
[ ] Request of a new feature.

Please select the area your request applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[X ] Workspace - VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup - Dendron's Lookup Command
[ ] Views - Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema - Dendron Schemas
[ ] Pod - Data import from / export to Dendron
[ ] Publish - External Site Publish
[ X] Markdown - Markdown features, such as syntax support and features

Is your feature request related to a problem? Please describe
I use classical markdown link syntax [the text I want to see on the link](the_filename.md). This syntax is more widely supported and notably by Pandoc, which I use a lot to create pdfs via LaTeX.

Currently Dendron refactoring doesn't affect these files. If I rename a note, the markdown links are not updated.
The hoover preview does not work on these links.
The ![[a_dendron_note]] does not work with a classical markdown link

Describe the solution you'd like
I would like that the classical markdown link syntax equipped with the same features as the wikilinks:

automatic renaming upon refactoring
hoover preview
embed note content using a syntax like ![text](markdown_file.md)

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thanks @mcaruel - it makes sense to treat markdown links the same as wikilinks for Dendron functionality.  Adding this one to our backlog.

Related/overlapping issue:
#2828 Recognize Internal Markdown Links as Backlinks


Updating namespaces for #nanoframework/nanoFramework.DependencyInjection/pull/33

Description
Updating namespaces for https://github.com/nanoframework/nanoFramework.DependencyInjection/pull/33
Motivation and Context
These changes are required once the PR is merged.
How Has This Been Tested?
It compiles.
Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a sample)
[X] Bug fix (fixes an issue with a current sample)
[ ] New Sample (adds a new sample)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)

Checklist:

[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I'll update this PR once https://github.com/nanoframework/nanoFramework.DependencyInjection/pull/33 is merged.

A quick check shows there are still changes required in the following paths:

nanoFramework.Samples\samples\Hosting
nanoFramework.Samples\samples\Webserver\WebServer.DI

I'll do a more comprehensive check and complete all these changes once the DI PR is merged.

Believe this covers all the samples that reference nanoFramework.DependencyInjection


Problems downloading freetype in build scripts

See: https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-s390x-openj9/395/console
Causing problems on all platforms when downloading freetype (consistent with wget as well)
curl: (7) Failed connect to download.savannah.gnu.org:443; No route to host
A curl error code 7 occurs when a connection is unavailable to a host or proxy, so this is before any checksum checks. Site seems to be accessible and I had no problems downloading the source so I would assume this is a problem with DNS/proxy setup?

Appears to be fine in the subsequent run so I assume the download servers were offline last night.


Create Privacy

Steph, please take a look.  Thanks!

I pushed a few lil updates (you're welcome to check the update to see the dif!), I purposely didn't include it in the sidebar at the moment though. Where would you like it to be ideally? @CarlosTorres415

@obadiaa thanks! ideally it would be at the top of the page as a separate folder beneath "guides," " jobs" and "projects"


Correct wrong warning when tmp bucket lifecycle policy has no prefix

This PR just avoid having a warning with a stacktrace when the used tmp bucket is configured with a lifecycle without prefix.

Codecov Report

Merging #30 into master will decrease coverage by 0.02%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
- Coverage   73.92%   73.89%   -0.03%
==========================================
  Files          15       15
  Lines         767      770       +3
  Branches      103      105       +2
==========================================
+ Hits          567      569       +2
- Misses        200      201       +1

I did the requested changes and now we even have an increase in test coverage 😄.

Any chance we can get this merged and approved and deployed to maven?  Say version 4.0.1?


zeroctl copy requires tlog config when parity and data shards args are not passed

There was an optional arguments was added to zeroctl copy vdisk command parityShards and dataShards. I understand when they're provided zeroctl try to copy tlog data but when they're not provided the zeroctl copy only copies the metadata, it should not require tlog config as far as I understand
Command: /bin/zeroctl copy vdisk —config <IP_ADDRESS>:2379 template:ubuntu-1604 vdisk2 st
t=2017-09-19T09:47:04+0000 lvl=info msg="parsing positional arguments..." module=global caller=vdisk.go:48
t=2017-09-19T09:47:04+0000 lvl=info msg="generating tlog data for target vdisk `vdisk2`" module=global caller=vdisk.go:108
t=2017-09-19T09:47:04+0000 lvl=eror msg="key 'vdisk2:vdisk:conf:storage:tlog' was not found on the ETCD server" module=global caller=source_etcd.go:63
t=2017-09-19T09:47:04+0000 lvl=eror msg="received invalid etcd config 'vdisk2:vdisk:conf:storage:tlog' (vdisk:'')" module=global caller=source_etcd.go:151
{"status":403,"subject":"etcd","data":{"endpoints":["<IP_ADDRESS>:2379"],"key":"vdisk2:vdisk:conf:storage:tlog"}}
Error: failed to create tlog generator: failed to create flusher: config is not available in source
Usage:
  zeroctl copy vdisk source_vdiskid target_vdiskid [target_clusterid] [flags]

Flags:
      --config SourceConfig   config resource: dialstrings (etcd cluster) or path (yaml file) (default config.yml)
      --data-shards int       data shards (K) variable of erasure encoding (default 4)
  -h, --help                  help for vdisk
  -j, --jobs int              the amount of parallel jobs to run the tlog generator (default 16)
      --parity-shards int     parity shards (M) variable of erasure encoding (default 2)
      --priv-key string       private key (default "12345678901234567890123456789012")
      --same                  enable flag to force copy within the same nbd servers

Global Flags:
  -v, --verbose   log available information

failed to create tlog generator: failed to create flusher: config is not available in source

please update to last master.
If you don't want to also copy tlog data, please make sure you don't have tlog cluster configured for the target vdisk

By tlogcluster configured you mean {vdiskid}:vdisk:conf:storage:tlog?

By tlogcluster configured you mean {vdiskid}:vdisk:conf:storage:tlog?

Not sure, i mean it should doesn't have tlogServerClusterID as described below
vdisks:
  myimg:
    blockSize: 4096
    readOnly: false
    size: 10
    type: boot
    nbd:
      storageClusterID: mycluster
      #tlogServerClusterID: main

the fix is on fix-copyvdisk-alpha-8, could you try it?

has been fixed in  alpha-8 branch

Looks like the new addition checks on the value of tlogServerClusterID not just the existence of the key
When I had this config
vd6:vdisk:conf:storage:nbd
storageClusterID: myblockcluster
templateStorageClusterID: 87ec688e821f5f0006619b7207d656bd
tlogServerClusterID: ''

It only copied the metadata and skipped the tlog data and when I used random data in the value
vd7:vdisk:conf:storage:nbd
storageClusterID: myblockcluster
templateStorageClusterID: 87ec688e821f5f0006619b7207d656bd
tlogServerClusterID: 'dfadsdsafa'

It worked

@khaledkbadr your last comment doesn't make any sense. If in your last example dfadsdsafa does not exist, than you shouldn't be able to boot up vdisk vd7 at all, due to an invalid config.

It only copied the metadata and skipped the tlog data

Isn't that what you want? You want it to not try to generate tlog data in case you didn't specify the tlogServerClusterID, no? Or am I missing something here?

than you shouldn't be able to boot up vdisk vd7 at all, due to an invalid config.

It started copying the vdisk without any errors for sometime, anyway I don't think we use tlogServerClusterID value in any way in the zeroctl copy since we don't have any tlogservers running. On the other hand {vdiskid}:vdisk:conf:storage:tlog will have correct configuration in there which will allow the copying of tlog data.

Isn't that what you want?

Yup exactly, but to allow the other behavior which will allow me to copy the tlog data I have to put a value that I don't have tlogServerClusterID value at that stage. Hence, I fixed it by putting "temp" to that value and it wont effect anything either way.
Anyway, It's tested with the "temp" value for both behaviours (copying metdata only, and copying metadata+tlog data)
My question then, does it make sense that I have to add that random string to the key?

My question then, does it make sense that I have to add that random string to the key?

random value is working because zeroctl copy doesn't use tlog server at this stage

random value is working because zeroctl copy doesn't use tlog server at this stage

Ooooh right, a random value does work as long as you never try to actually read that value. But please don't ever add a random value, as this will trigger tlog to be used and thus operations will/should fail.
So if you don't want/have a tlogServerCluster, than don't specify the TlogServerClusterID either (or give explicitly the empty string value).

please don't ever add a random value, as this will trigger tlog to be used and thus operations will/should fail.

It's alright actually, I override that config with the proper config when I create a VM. So tlogServerCluster will be correct when it's being used

So if you don't want/have a tlogServerCluster, than don't specify the TlogServerClusterID either

I already do that :)
BTW, feel free to close this issue since it's been tested by QA. and @iwanbk can you notify me when this is fixed on master so I can update our flist

Fixed by PR #479.

Not sure why this was assigned to alpha-8, but OK I merged it into master as well using a merge commit 1641c88659b7915192079a0b86ce9a8cdfa35209 (@iwanbk could you review this merge commit, as there was a merge conflict and I moved your logic to the tlog/copy module).
@khaledkbadr, you should be able to get latest master and have this fix.

but OK I merged it into master as well using a merge commit 1641c88 (@iwanbk could you review this merge commit

It failed on travis, looks like conflict with recent changes about IYO variables.
https://travis-ci.org/zero-os/0-Disk/jobs/277611980
invalid ZeroStorClusterConfig: Org: non zero value required;;Org: non zero value required;;

I actually already prepared another PR for the master #480

It failed on travis, looks like conflict with recent changes about IYO variables.

I'm already fixing that travis fail.

I actually already prepared another PR for the master #480

Ah sorry, wasn't clear to me from this issue. Please next time link to this issue and communicate about it.


feat: add adaptive widget skeleton

Jira: LF-7886
This present an adaptive Widget Skeleton that adapt adapt to different themes and configurations.
As discussed I've tried to do this without using the Mui's ThemeProvider - I have still had to use the createTheme function to generate the correct theme data. It should adapt to the existing themes in the playground.
It should also adapt to 'refuel' subvariant and take in to consideration RequireUI (toAddress), HiddenUI ('poweredBy and walletMenu) and also navigation.edge from theme. I don't think it would take much to support the 'split' subvariant also.
The functions I have written here to adapt to component definitions from the theme feel a little brittle - if we were to do this using Mui's themeProvider I think the complexity of this code would be reduced and also broader use of Mui's theme would be supported relatively easily - comparison an be found on the spike branch https://github.com/lifinance/widget/pull/242
I've set this up so that you can play with this in the Widget Playground, and I've also added this to the Next playground to see it work there.

https://github.com/lifinance/widget/assets/7836726/806d22dc-2955-41ad-8a7a-b70e732acff4
https://github.com/lifinance/widget/assets/7836726/231887c4-b071-42c0-84cb-cbd776fe1ffe

Development for this feature has moved to - https://github.com/lifinance/widget/pull/242


[NativeAnimated] Support the Slow Animations option of the iOS simulator

RN animations currently ignore the Slow Animations option on the iOS simulator because we don't use UIKit animations directly. This uses a private api to get the slow coefficient and use it in the native animated driver. We only compile the private api code on simulator so this won't cause issues for app store approval. One possible issue is that the api changes in new iOS versions but I think it's reasonable to do this.
Note that this won't work with JS driven animations, we could expose the slow coefficient as a constant and use that in JS but I decided not to implement it.
Test Plan:
Tested that animations are properly slowed like native UIKit ones in RNTester native animated example.
Release Notes:
[IOS] [ENHANCEMENT] [NativeAnimated] - Support the Slow Animations option of the iOS simulator

cc @kmagiera
Could be nice to integrate this in reanimated too.

Including a video in your test plan would be cool

@janicduplessis: we're seeing animated test failures after merging this - any idea why that could be? e.g.
RCTNativeAnimatedNodesManagerTests/testSpringAnimationLoop:
Failure: ((didComeToRest) is true) failedRNTester/RNTesterUnitTests/RCTNativeAnimatedNodesManagerTests.m:484
RCTNativeAnimatedNodesManagerTests/testAnimationCallbackFinish:
Failure: ((endCallbackCalls) equal to (1)) failed: ("0") is not equal to ("1")
RNTester/RNTesterUnitTests/RCTNativeAnimatedNodesManagerTests.m:514