Error: Subtype of "axilite_vvc_master_if" is not fully constrained.

Getting this error in my small UVVM testbench. Don't understand why. Does someone have a solution?
I am using Questasim to compile the design.
`
-- History
--     Date
-- (YYYY/MM/DD) Author          Rev.  Change Description
--  ==========  ==============  ====  ==========================================
--  2021/00/00  320123287  0.0   generated file (HDL Designer design)

-- Design Description

LIBRARY ieee;
USE ieee.std_logic_1164.ALL;
USE ieee.numeric_std.ALL;
ENTITY uvvm_axi4dut_tb IS
-- Declarations
END ENTITY uvvm_axi4dut_tb ;
--   generated file (HDL Designer Block Diagram)
LIBRARY ieee;
USE ieee.std_logic_1164.ALL;
USE ieee.numeric_std.ALL;
--CONTEXT bitvis_vip_axilite.vvc_context;
LIBRARY bitvis_vip_axilite;
USE bitvis_vip_axilite.axilite_bfm_pkg.all;
USE bitvis_vip_axilite.transaction_pkg.all;
USE bitvis_vip_axilite.axilite_channel_handler_pkg.all;
USE bitvis_vip_axilite.vvc_methods_pkg.all;
USE bitvis_vip_axilite.vvc_cmd_pkg.all;
LIBRARY uvvm_util;
USE uvvm_util. types_pkg.all;
CONTEXT uvvm_util.uvvm_util_context;
LIBRARY uvvm_vvc_framework;
USE uvvm_vvc_framework.ti_vvc_framework_support_pkg.all;
LIBRARY Axi4dutlib;
LIBRARY Axi4dutlib_tb;
LIBRARY bitvis_vip_clock_generator;
ARCHITECTURE struct OF uvvm_axi4dut_tb IS
-- Architecture declarations
CONSTANT GC_ADDR_WIDTH : natural :=32;
CONSTANT GC_DATA_WIDTH : natural := 32;
-- Internal signal declarations
SIGNAL I2F_WaitIn            : std_logic                    := '0';
SIGNAL ImageIn               : tFullInternalFormat4         := zero_tFullInternalFormat4;
SIGNAL ImageOut              : tFullInternalFormat4;
SIGNAL RndW8Tst              : std_logic_vector(0 DOWNTO 0) := "0";
SIGNAL WaitOut               : std_logic;
SIGNAL axi4Clk               : std_logic;
SIGNAL axi4Rst               : std_logic;
SIGNAL axiM2s                : t_axi4l_m2s;
SIGNAL axiS2m                : t_axi4l_s2m;
SIGNAL axilite_vvc_master_if : t_axilite_if                 := init_axilite_if_signals(32, 32);
SIGNAL dout_dut             : std_logic_vector(31 DOWNTO 0);
SIGNAL empty                 : std_logic;
SIGNAL ipShellDbg            : std_logic_vector(31 DOWNTO 0);
SIGNAL ip_clk                : std_logic;
SIGNAL ip_rst                : std_logic;
-- Component Declarations
COMPONENT axi4dut_top
GENERIC (
g_dut_BASE_ADDR   : std_logic_vector (15 downto 0) := (others => '0');    --
g_dut_FUNCTION_ID : integer                        := 0;                  --
g_NrMappers        : integer                        := 1;
g_NrInputs         : integer                        := 1
);
PORT (
I2F_WaitIn : IN     std_logic ;
ImageIn    : IN     tFullInternalFormat4 ;
RndW8Tst   : IN     std_logic_vector (0 DOWNTO 0);
axi4Clk    : IN     std_logic ;
axi4Rst    : IN     std_logic ;
axiM2s     : IN     t_axi4l_m2s ;
ip_clk     : IN     std_logic ;
ip_rst     : IN     std_logic ;
ImageOut   : OUT    tFullInternalFormat4 ;
WaitOut    : OUT    std_logic ;
axiS2m     : OUT    t_axi4l_s2m ;
dout_dut  : OUT    std_logic_vector (31 DOWNTO 0);
empty      : OUT    std_logic ;
ipShellDbg : OUT    std_logic_vector (31 DOWNTO 0)
);
END COMPONENT axi4dut_top;
COMPONENT dut_stimul
PORT (
axi4Rst : OUT    std_logic;
ip_rst  : OUT    std_logic
);
END COMPONENT dut_stimul;
COMPONENT axi_splitter
GENERIC (
GC_ADDR_WIDTH : integer := 32;
GC_DATA_WIDTH : integer := 32
);
PORT (
axiS2m                : IN     t_axi4l_s2m ;
axiM2s                : OUT    t_axi4l_m2s ;
axilite_vvc_master_if : INOUT  t_axilite_if
);
END COMPONENT axi_splitter;
COMPONENT axilite_vvc
GENERIC (
GC_ADDR_WIDTH                            : integer range 1 to C_VVC_CMD_ADDR_MAX_LENGTH := 8;
GC_DATA_WIDTH                            : integer range 1 to C_VVC_CMD_DATA_MAX_LENGTH := 32;
GC_INSTANCE_IDX                          : natural                                      := 1;                               -- Instance index for this AXILITE_VVCT instance
GC_AXILITE_CONFIG                        : t_axilite_bfm_config                         := C_AXILITE_BFM_CONFIG_DEFAULT;    -- Behavior specification for BFM
GC_CMD_QUEUE_COUNT_MAX                   : natural                                      := 1000;
GC_CMD_QUEUE_COUNT_THRESHOLD             : natural                                      := 950;
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY    : t_alert_level                                := WARNING;
GC_RESULT_QUEUE_COUNT_MAX                : natural                                      := 1000;
GC_RESULT_QUEUE_COUNT_THRESHOLD          : natural                                      := 950;
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY : t_alert_level                                := WARNING
);
PORT (
clk                   : IN     std_logic;
axilite_vvc_master_if : INOUT  t_axilite_if  := init_axilite_if_signals(GC_ADDR_WIDTH, GC_DATA_WIDTH)
);
END COMPONENT axilite_vvc;
COMPONENT clock_generator_vvc
GENERIC (
GC_INSTANCE_IDX                          : natural       := 1;
GC_CLOCK_NAME                            : string        := "clk";
GC_CLOCK_PERIOD                          : time          := 10 ns;
GC_CLOCK_HIGH_TIME                       : time          := 5 ns;
GC_CMD_QUEUE_COUNT_MAX                   : natural       := 1000;
GC_CMD_QUEUE_COUNT_THRESHOLD             : natural       := 950;
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY    : t_alert_level := WARNING;
GC_RESULT_QUEUE_COUNT_MAX                : natural       := 1000;
GC_RESULT_QUEUE_COUNT_THRESHOLD          : natural       := 950;
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY : t_alert_level := warning
);
PORT (
clk : OUT    std_logic
);
END COMPONENT clock_generator_vvc;
-- Optional embedded configurations
-- pragma synthesis_off
FOR ALL : dut_stimul USE ENTITY Axi4dutlib_tb.dut_stimul;
FOR ALL : axi4dut_top USE ENTITY Axi4dutlib.axi4dut_top;
FOR ALL : axi_splitter USE ENTITY Axi4dutlib_tb.axi_splitter;
FOR ALL : axilite_vvc USE ENTITY bitvis_vip_axilite.axilite_vvc;
FOR ALL : clock_generator_vvc USE ENTITY bitvis_vip_clock_generator.clock_generator_vvc;
-- pragma synthesis_on
BEGIN
-- Instance port mappings.
i_axi4dut_top : axi4dut_top
GENERIC MAP (
g_dut_BASE_ADDR   => (others => '0'),      --
g_dut_FUNCTION_ID => 8,                    --
g_NrMappers        => 1,
g_NrInputs         => 1
)
PORT MAP (
I2F_WaitIn => I2F_WaitIn,
ImageIn    => ImageIn,
RndW8Tst   => RndW8Tst,
axi4Clk    => axi4Clk,
axi4Rst    => axi4Rst,
axiM2s     => axiM2s,
ip_clk     => ip_clk,
ip_rst     => ip_rst,
ImageOut   => ImageOut,
WaitOut    => WaitOut,
axiS2m     => axiS2m,
dout_dut  => dout_dut,
empty      => empty,
ipShellDbg => ipShellDbg
);
i_dut_stimul : dut_stimul
PORT MAP (
axi4Rst => axi4Rst,
ip_rst  => ip_rst
);
i_axi_splitter : axi_splitter
GENERIC MAP (
GC_ADDR_WIDTH => 32,
GC_DATA_WIDTH => 32
)
PORT MAP (
axiS2m                => axiS2m,
axiM2s                => axiM2s,
axilite_vvc_master_if => axilite_vvc_master_if
);
i_axilite_vvc : axilite_vvc
GENERIC MAP (
GC_ADDR_WIDTH                            => 32,
GC_DATA_WIDTH                            => 32,
GC_INSTANCE_IDX                          => 1,                                 -- Instance index for this AXILITE_VVCT instance
GC_AXILITE_CONFIG                        => C_AXILITE_BFM_CONFIG_DEFAULT,      -- Behavior specification for BFM
GC_CMD_QUEUE_COUNT_MAX                   => 1000,
GC_CMD_QUEUE_COUNT_THRESHOLD             => 950,
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY    => WARNING,
GC_RESULT_QUEUE_COUNT_MAX                => 1000,
GC_RESULT_QUEUE_COUNT_THRESHOLD          => 950,
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY => WARNING
)
PORT MAP (
clk                   => axi4Clk,
axilite_vvc_master_if => axilite_vvc_master_if
);
i_clock_generator_vvc : clock_generator_vvc
GENERIC MAP (
GC_INSTANCE_IDX                          => 1,
GC_CLOCK_NAME                            => "clk",
GC_CLOCK_PERIOD                          => 10 ns,
GC_CLOCK_HIGH_TIME                       => 5 ns,
GC_CMD_QUEUE_COUNT_MAX                   => 1000,
GC_CMD_QUEUE_COUNT_THRESHOLD             => 950,
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY    => WARNING,
GC_RESULT_QUEUE_COUNT_MAX                => 1000,
GC_RESULT_QUEUE_COUNT_THRESHOLD          => 950,
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY => warning
)
PORT MAP (
clk => ip_clk
);
i_clock_generator_vvc1 : clock_generator_vvc
GENERIC MAP (
GC_INSTANCE_IDX                          => 1,
GC_CLOCK_NAME                            => "clk",
GC_CLOCK_PERIOD                          => 10 ns,
GC_CLOCK_HIGH_TIME                       => 5 ns,
GC_CMD_QUEUE_COUNT_MAX                   => 1000,
GC_CMD_QUEUE_COUNT_THRESHOLD             => 950,
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY    => WARNING,
GC_RESULT_QUEUE_COUNT_MAX                => 1000,
GC_RESULT_QUEUE_COUNT_THRESHOLD          => 950,
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY => warning
)
PORT MAP (
clk => axi4Clk
);
END ARCHITECTURE struct;
`

When you declare the axilite_vvc_master_if you need to constrain it, e.g.
signal axilite_vvc_master_if : t_axilite_if( write_address_channel(awaddr(C_ADDR_WIDTH-1 downto 0)),
                                             write_data_channel(wdata(C_DATA_WIDTH-1 downto 0),
                                             wstrb((C_DATA_WIDTH/8)-1 downto 0)),
                                             read_address_channel(araddr(C_ADDR_WIDTH-1 downto 0)),
                                             read_data_channel(rdata(C_DATA_WIDTH-1 downto 0)));

You can find some information about it in the Quick Reference section 7.

erick166, thanks for your comment.
On the toplevel the following definition can be found "SIGNAL axilite_vvc_master_if : t_axilite_if := init_axilite_if_signals(32, 32);"
So this looks constrained.
I don't understand what's wrong.
Can you give me another hint?

The function init_axilite_if_signals(32,32) will return a constrained type, however the signal axilite_vvc_master_if is still unconstrained. You can try:
signal axilite_vvc_master_if : t_axilite_if( write_address_channel(awaddr(C_ADDR_WIDTH-1 downto 0)),
                                             write_data_channel(wdata(C_DATA_WIDTH-1 downto 0),
                                             wstrb((C_DATA_WIDTH/8)-1 downto 0)),
                                             read_address_channel(araddr(C_ADDR_WIDTH-1 downto 0)),
                                             read_data_channel(rdata(C_DATA_WIDTH-1 downto 0))) := init_axilite_if_signals(C_ADDR_WIDTH, C_DATA_WIDTH);

Erick166, Thanks again.
I managed to get this problem solved.
Now I get an error for the identifier "C_VVC_CMD_DATA_MAX_LENGTH" which is defined in two packages. bitvis_vip_axilite/transaction_pkg.vhd and in bitvis_vip_clock_generator/vvc_cmd_pkg.vhd. Why is this identifier placed in both package files? Removing it from the clock_generator/vvc_cmd_pkg.vhd give me a lot of other errors. Should I overwrite this value in the generics from the axilite_vvc block.  Documentation seems to be very poor on this.

That's great 👍
The constant C_VVC_CMD_DATA_MAX_LENGTH is specific for each VIP library, they share the name because their purpose is the same, usually they are not referenced in the testbench.
You could try using the complete path of the constant in the generics of the axilite_vvc block, e.g. bitvis_vip_axilite.transaction_pkg.C_VVC_CMD_DATA_MAX_LENGTH or remove the component declaration of the VVCs and leave only the instantiation, unless there is a special reason why you need to declare the components in your testbench.

erick166,
tried several solutions but did not manage to get it done in a nice way. I did not want to touch the original bitvis files but finally after a lot of frustration I changed the original axilite_vvc file. Set the range for ADDR_WIDTH and DATA_WIDTH to a fixed value of 32. When I now compiles I get the error message during the Questasim VCOM command that some pkg files are changed. Very strange. "Recompile work.axilite_vvc because work.vvc_methods_pkg, work.vvc_cmd_pkg have changed."
Some articles and some powerpoints tell me that I could create a UVVM testbench in half a hour. Well, I am an experienced VHDL programmer with more then 20 years experience, but I am already working for 3 days to get a simple testbench running. Terrible.
Sorry to bother you with my frustration.

Found out that vvc_methods_pkg is in the clock and in the axi library. Two the same named packages files! The same counts for the vvc_cm_pkg file. Do I only need one file? BTW I compile by  means of a batch script and I use one work library. Is this correct?
`
Rem Build automatic test with Questasim
rem ==================== define PC name
rem
set PROJECT_HOME=%CD%
set FDCSIB_USER_HOME=%PROJECT_HOME%..
IF %COMPUTERNAME% == XXXX goto PC_ALBERT
GOTO ERROR
rem ============== define paths to tools for every PC
rem
:PC_ALBERT
rem
set QUESTASIM_EXE=C:\pldtools\questasim64_2020.2\win64
set XILINX_VENDOR_LIBS=C:\pld\Vendor_libs\questasim64_2020.2\vivado_2020.2
rem
GOTO START
:START
set  TEST_FILES=%FDCSIB_USER_HOME%\Questasim_batch\Special_Test_files
set  WORK_DIR=%FDCSIB_USER_HOME%\Questasim_batch
Rem
Rem Make new work diretories
Rem
if not exist work goto skip_work
rmdir /Q /S work
:skip_work
Rem
Rem Creat physical directories
Rem
md work
cd work
rem md axi4adpclib
rem md axi4adpclib_tb
rem md uvvm_util
rem md uvvm_vvc_framework
rem md bitvis_vip_scoreboard
rem md bitvis_vip_axilite
rem md bitvis_vip_clock_generator
rem md ipshelllib
rem md axi4componentslib
rem md flashlitelib
rem md work
rem
cd..
rem
rem  Create work libraries. Every library will gets its own directory
rem
rem %QUESTASIM_EXE%/vlib -type directory %WORK_DIR%\work\axi4adpclib\work
rem
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\axi4adpclib\work
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\axi4adpclib_tb\work
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\uvvm_util\work
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\uvvm_vvc_framework\work
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\bitvis_vip_scoreboard\work
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\bitvis_vip_axilite\work
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\bitvis_vip_clock_generator\work
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\ipshelllib\work
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\axi4componentslib\work
rem %QUESTASIM_EXE%/vlib %WORK_DIR%\work\flashlitelib\work
%QUESTASIM_EXE%/vlib %WORK_DIR%\work
rem
rem %MODELSIM_EXE%/vlib %WORK_DIR%/work/nios_model/work
rem
rem  Map libraries to directories
rem
rem %MODELSIM_EXE%/vmap work          %WORK_DIR%/work
rem %QUESTASIM_EXE%/vmap axi4adpclib                   %WORK_DIR%/work/axi4adpclib/work
rem %QUESTASIM_EXE%/vmap axi4adpclib_tb                %WORK_DIR%/work/axi4adpclib_tb/work
rem %QUESTASIM_EXE%/vmap uvvm_util                     %WORK_DIR%/work/uvvm_util/work
rem %QUESTASIM_EXE%/vmap uvvm_vvc_framework            %WORK_DIR%/work/uvvm_vvc_framework/work
rem %QUESTASIM_EXE%/vmap bitvis_vip_scoreboard         %WORK_DIR%/work/bitvis_vip_scoreboard/work
rem %QUESTASIM_EXE%/vmap bitvis_vip_axilite            %WORK_DIR%/work/bitvis_vip_axilite/work
rem %QUESTASIM_EXE%/vmap bitvis_vip_clock_generator    %WORK_DIR%/work/bitvis_vip_clock_generator/work
rem %QUESTASIM_EXE%/vmap ipshelllib                    %WORK_DIR%/work/ipshelllib/work
rem %QUESTASIM_EXE%/vmap axi4componentslib             %WORK_DIR%/work/axi4componentslib/work
rem %QUESTASIM_EXE%/vmap flashlitelib                  %WORK_DIR%/work/flashlitelib/work
rem %QUESTASIM_EXE%/vmap work                          %WORK_DIR%/work
rem
%QUESTASIM_EXE%/vmap axi4adpclib                   %WORK_DIR%/work
%QUESTASIM_EXE%/vmap axi4adpclib_tb                %WORK_DIR%/work
%QUESTASIM_EXE%/vmap uvvm_util                     %WORK_DIR%/work
%QUESTASIM_EXE%/vmap uvvm_vvc_framework            %WORK_DIR%/work
%QUESTASIM_EXE%/vmap bitvis_vip_scoreboard         %WORK_DIR%/work
%QUESTASIM_EXE%/vmap bitvis_vip_axilite            %WORK_DIR%/work
%QUESTASIM_EXE%/vmap bitvis_vip_clock_generator    %WORK_DIR%/work
%QUESTASIM_EXE%/vmap ipshelllib                    %WORK_DIR%/work
%QUESTASIM_EXE%/vmap axi4componentslib             %WORK_DIR%/work
%QUESTASIM_EXE%/vmap flashlitelib                  %WORK_DIR%/work
%QUESTASIM_EXE%/vmap work                          %WORK_DIR%/work
rem
Rem
Rem Compile source file (first package files)
Rem
Rem  Compile uvvm_util files
Rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/types_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/adaptations_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/string_methods_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/protected_types_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/license_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/global_signals_and_shared_variables_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/hierarchy_linked_list_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/alert_hierarchy_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/methods_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/generic_queue_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/data_queue_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/data_stack_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/data_fifo_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/bfm_common_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_util/uvvm_util/hdl/uvvm_util_context.vhd
rem
rem Compile uvvm_vvc_framework files
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/ti_data_queue_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/ti_data_stack_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/ti_data_fifo_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/ti_protected_types_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/ti_generic_queue_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/ti_vvc_framework_support_pkg.vhd
rem
rem Compile bitvis_vip_scoreboard files
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_scoreboard/bitvis_vip_scoreboard/hdl/generic_sb_support_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_scoreboard/bitvis_vip_scoreboard/hdl/generic_sb_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_scoreboard/bitvis_vip_scoreboard/hdl/predefined_sb.vhd
rem
rem Compile bitvis_vip_axilite
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_axilite/bitvis_vip_axilite/hdl/axilite_bfm_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_axilite/bitvis_vip_axilite/hdl/transaction_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_axilite/bitvis_vip_axilite/hdl/vvc_cmd_pkg.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/td_target_support_pkg.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_axilite/bitvis_vip_axilite/hdl/vvc_methods_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_axilite/bitvis_vip_axilite/hdl/axilite_channel_handler_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_axilite/bitvis_vip_axilite/hdl/vvc_context.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/td_queue_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/td_vvc_framework_common_methods_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/td_vvc_entity_support_pkg.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_axilite/bitvis_vip_axilite/hdl/axilite_vvc.vhd
rem
rem
rem
rem Compile bitvis_vip_clock_generator files
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_clock_generator/bitvis_vip_clock_generator/hdl/vvc_cmd_pkg.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/td_target_support_pkg.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_clock_generator/bitvis_vip_clock_generator/hdl/vvc_methods_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_clock_generator/bitvis_vip_clock_generator/hdl/vvc_context.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/td_queue_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/td_vvc_framework_common_methods_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/uvvm_vvc_framework/uvvm_vvc_framework/hdl/td_vvc_entity_support_pkg.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/bitvis_vip_clock_generator/bitvis_vip_clock_generator/hdl/clock_generator_vvc.vhd
rem
rem Compile the files of the Flashlite library
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/FlashLiteLib/FlashLiteLib/hdl/real_time_clock_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/FlashLiteLib/FlashLiteLib/hdl/project_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/FlashLiteLib/FlashLiteLib/hdl/image_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/FlashLiteLib/FlashLiteLib/hdl/viper_pkg.vhd
rem
rem Compile the files of the axi4components library
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/axi4_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/axi4l_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/Axi4BusMuxTypes_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/Axi4BusMux_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/axi4ClkXing_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/Axi4Reg16_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/Axi4Reg16wRst_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/Axi4Reg16wSet_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/Axi4Reg32_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/Axi4Reg_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/Axi4Reg_wRst_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/Axi4Reg_wSet_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/axi4ResponseControl_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/axi4TemplateAddressMap_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4componentslib/axi4componentslib/hdl/axi4Xing_pkg.vhd
rem
rem Compile the files of the IPshell library
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/ipshelllib/ipshelllib/hdl/ipshell_i2f_image_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/ipshelllib/ipshelllib/hdl/ipshell_databuf_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/ipshelllib/ipshelllib/hdl/ipshell_trlinsert_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/ipshelllib/ipshelllib/hdl/ipshell_control.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/ipshelllib/ipshelllib/hdl/ipshell_front.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/ipshelllib/ipshelllib/hdl/ipshell_mux.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/ipshelllib/ipshelllib/hdl/ipshell_mapperctrl.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/ipshelllib/ipshelllib/hdl/ipshell_top_struct.vhd
rem
rem Now the files on the toplevel
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4adpclib/axi4adpclib/hdl/axi4adpc_regs_pkg.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4adpclib/axi4adpclib/hdl/axi4adpc_addr_pkg.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4adpclib/axi4adpclib/hdl/axi4adpc_prm.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4adpclib/axi4adpclib/hdl/axi4adpc_iif.vhd
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4adpclib/axi4adpclib/hdl/axi4adpc_top_struct.vhd
rem
rem testbench files
rem
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4adpclib/axi4adpclib_tb/hdl/adpc_stimul.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4adpclib/axi4adpclib_tb/hdl/axi_splitter.vhd
%QUESTASIM_EXE%/vcom -2008 -work work -cover sbcef -coverNoSub %CD%/../fpga1/axi4adpclib/axi4adpclib_tb/hdl/uvvm_axi4adpc_tb_struct.vhd
pause
`

Sorry that you feel frustrated, it should be easy enough to start using the VVCs by reading the Quick Reference document, perhaps it needs better examples.
Just to be clear, neither of the 2 solutions I mentioned worked for you?

Remove the component declaration in the testbench
Use the full path of the constant: bitvis_vip_axilite.transaction_pkg.C_VVC_CMD_DATA_MAX_LENGTH

You might also try looking at the UVVM supplementary repository, there you can find the testbenches for every library and perhaps some useful examples.
Yes, each VIP library has files with common names: vvc_methods_pkg, vvc_cmd_pkg, etc. However, they must be compiled into different libraries so that there's no conflicts between them. This is explained in the VVC QuickRef Section 9.
If you have a look at the compile_order.txt file under bitvis_vip_axilite\script you can see the files needed for that specific library. You can find the same compile_order.txt file in every VIP library.
I hope this helps.

erick166, Yes I managed to get things running in Questasim. Checked the order of compilation and the work libraries. Found some errors and after correcting them I has zero compilation errors.
But now (of coarse) the next problem arise. When I run my testbench in Questasim (64 bit version 2020.04) the design seems to get stuck somewhere. Message = "# ** Error (suppressible): (vsim-3601) Iteration limit 10000000 reached at time 0 ps." It is not in my sequencer, because if I remove all the commands this loop still exist. The DUT I am testing worked already in a plain VHDL testbench. Must be somewhere in the UVVM blocks.
Any idea or suggestion?

It's good that you managed to compile without errors.
I can see in your testbench file that there are two clock generator VVCs with the same instance index, the indexes should be unique among VVCs of the same type, try changing one of them. Otherwise there's nothing else that looks strange in the testbench file that you copied here. Remember also to use await_uvvm_initialization(VOID); at the beginning of your sequencer.

erick166, I changed the number of the GC_INSTANCE_IDX indexes already in the last days. Every uvvm block has a different index. Also the statement await_uvvm_initialization(VOID); is in my seqeuncer.

Have you instantiated the following in your testbench?
i_ti_uvvm_engine : entity uvvm_vvc_framework.ti_uvvm_engine;

erick166, sorry for my very very late replay. Due to some other work and some holidays it took a while. After adding the block "ti_uvvm_engine" everything started. Thanks for that remark! Simulation is now running, although I get an error message on some AxiLite read actions, Looks like if they are coming to fast after each other. Still figuring out what is really happening.

I found out that after an axilite_check a short delay is needed before the next axilite_check (or read/write) starts. I tried to use the insert_delay() command but did not get it working. Could not find that procedure for some reason . Correct libraries are compiled for Questsim (td_vvc_framework_common_methode_pkg.vhd & ti_vvc_framework_support_pkg.vhd). Then I used a "wait for 50 ns;" line after each axilite_check and that worked. Now my simulation ends nicely with a summary of all alerts.

That's alright, it's good to hear that your testbench works now.
It's difficult to know why you are having problems with the axilite_check() without looking at the testbench. These procedures have been tested even with back-to-back commands so they should work without the need for delays. Perhaps you can look at the UVVM supplementary repository and check the bitvis_vip_axilite/tb/maintenance_tb/axilite_vvc_simple_tb.vhd to compare.

erikc166, I think that it is not a problem of the uvvm code. It think that it is a failure in the VHDL that I am testing. It is from a project that we took over from another department. They have build a clock crossing inside the AXILite interface. I think, but I have to investigate this further, that the clock crossing is given extra delayed and that ruin's the timing of the valid signals in the AXILite interface. No problem if read or write action are seperated by (in my case) 50 ns. But the UVVM read or write action are close together, which showed this problem in the VHDL. Clockcrossing should not be used in the valid signals but in the register signals after the AXILIte interface.

Alright, then I guess we can close this issue.

Yes, you may close this issue. Thanks for the help


Assets non-relative path with timestamp

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues
#18529

👍

Thanks @bizley!


Update README file

Ironically this is a PR against master. I think default should become the default branch, and this PR should be against that. Also, if we're updating the README to reflect the new flow, we should have something that states how things are managed in this repo in addition to that 1 line in the contributing section.

@paddybyers LOL. All of this just because I forgot to click

:)


Infowindow html editor

This PR fixes #7851.
Todo:

[x] Undo redo history
[x] Tooltip customs templates
[x] Render custom templates in the map

cc @xavijam

@matallo @alonsogarciapablo I need some help here in order to save and load the custom templates in the map. Basically I have this code https://github.com/CartoDB/cartodb/blob/c2c5d5bc03c2046e7b3ffc0a2948afc2667aa409/lib/assets/javascripts/cartodb3/editor/layers/layer-content-views/infowindow/infowindow-view.js#L47-L73, but I need some info about how custom templates are managed in cartodb.js.
Also, when a custom templates is applies, which carousel item should be selected? I guess "none", right?

I suppose in that case the "html" sould be checked and show the custom template, then clicking on the toggle would show something similar to the current editor where you'd lose your changes
I'll check the integration tomorrow, if you don't mind :)

Ready for review.
cc @xavijam @matallo
I've found some issues:

It's not possible to add inline style to pseudo elements. Because of that, the user won't be able to style the tip's color, not sure if we should change that @piensaenpixel
The custom html includes functionality classes like js-whatever. Should we keep them?

That's a good one, @piensaenpixel, would you mind to open a ticket for trying to solve that in the future?

Yes, we need them, if not the infowindow will not work. That reminds me that we need to add some needed info for the users, like: "if you don't add that class, infowindow will not work..."

@nobuti, could we add the button as the design below?. Clicking over it should reset the custom html and apply the simple one?
https://cloud.githubusercontent.com/assets/14546701/16274733/2a096360-38a7-11e6-8070-c6fff60fd1bb.png
And when clicking,

@xavijam what a cliffhanger...

what? :joy:

And when clicking,

The intrigue is killing me!

That has been edited!!! check the comment now :joy:

🙌  I'd wait to merge until infowindows migrations are, though (some templates are renamed) https://github.com/CartoDB/cartodb/pull/8085
/cc @juanignaciosl

Uncaught Error: Content property for codemirror is required.
str

create new map
add point and infowindow in old editor
go to new builder and popup panel

expected behaviour

infowindow light to be selected

actual behaviour

none is selected
when trying to go to html editor the previous error arises

@matallo The problem is in that case template_name is table/views/infowindow_light, I'm going to make a fix but not sure if the issue belongs to this. AFAIK the template name should be ìnfowindow_light`, right?

after https://github.com/CartoDB/cartodb/pull/8085 migrations, looks 👌 (tested locally)

Last minute CR?

BOOM


I got an error when trying to open the MacBook again and stop recording "Kap".

**macOS Version: 10.12
**Kap Version: 2.2.0
MacBook closed during recording.
I got an error when trying to open the MacBook again and stop recording "Kap".
Is there a way to recover it?

Related to #414

@cerori We have rewritten Kap to be more stable. Would you be able to try out the beta and see if you still can reproduce this issue?


[Event Hubs] MaxListenersExceededWarning when stopping a subscription

Package Name: @azure/event-hubs
Package Version: 5.11.4
Operating system: Windows
[x] nodejs

version: v20.11.1

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
Node reports MaxListenersExceededWarning when stopping a subscription with more than 10 partitions.
To Reproduce
Steps to reproduce the behavior:

Install @azure/event-hubs, @azure/eventhubs-checkpointstore-blob,  @azure/storage-blob, and ws
Save the javascript code below as repro.js
Run node repro.js

repro.js contents
const { EventHubConsumerClient } = require('@azure/event-hubs');
const {
  BlobCheckpointStore,
} = require('@azure/eventhubs-checkpointstore-blob');
const { ContainerClient } = require('@azure/storage-blob');
const { WebSocket } = require('ws');

const connectionString = '[REDACTED]';
const checkpointStorageConnectionString = '[REDACTED]';
const consumerGroup = '[REDACTED]';
const checkpointStorageContainerName = '[REDACTED]';

const containerClient = new ContainerClient(
  checkpointStorageConnectionString,
  checkpointStorageContainerName,
);
const checkpointStore = new BlobCheckpointStore(containerClient);

const client = new EventHubConsumerClient(
  consumerGroup,
  connectionString,
  checkpointStore,
  {
    webSocketOptions: {
      webSocket: WebSocket,
    },
    loadBalancingOptions: {
      strategy: 'greedy',
      partitionOwnershipExpirationIntervalInMs: 5000,
      updateIntervalInMs: 1000,
    },
  },
);

const subscription = client.subscribe(
  {
    processInitialize: async (context) => {
      console.log(`Starting to read from partition ${context.partitionId}`);
    },
    processEvents: async (events, context) => {
      console.log(
        `Received ${events.length} for partition ${context.partitionId}`,
      );
      await context.updateCheckpoint(events[events.length - 1]);
    },
    processError: async (err, context) => {
      console.log(
        `Error when processing partition ${context.partitionId}:`,
        err,
      );
    },
    processClose: async (reason, context) => {
      console.log(
        `Stopped reading from partition ${context.partitionId}, reason: ${reason}`,
      );
    },
  },
  {
    maxBatchSize: 10,
    skipParsingBodyAsJson: true,
  },
);

setTimeout(() => {
  console.log('Stopping...')
  subscription
    .close()
    .then(() => client.close())
    .catch(console.log);
}, 10000);

Expected behavior
No node warnings.
Actual behavior
Node reports a warning:
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 disconnected listeners added to [Connection]. Use emitter.setMaxListeners() to increase limit

Screenshots

Console output
❯ node --trace-warnings repro.js
Starting to read from partition 0
Starting to read from partition 1
Starting to read from partition 2
Starting to read from partition 3
Starting to read from partition 4
Starting to read from partition 5
Starting to read from partition 6
Starting to read from partition 7
Starting to read from partition 8
Starting to read from partition 9
Starting to read from partition 10
Starting to read from partition 11
Starting to read from partition 12
Starting to read from partition 13
Starting to read from partition 14
Starting to read from partition 15
Starting to read from partition 16
Starting to read from partition 17
Starting to read from partition 18
Starting to read from partition 19
Starting to read from partition 20
Stopping...
(node:23636) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 disconnected listeners added to [Connection]. Use emitter.setMaxListeners() to increase limit
    at _addListener (node:events:592:17)
    at Connection.addListener (node:events:610:10)
    at Connection.once (node:events:654:8)
    at C:\Code\azure-max-listeners-repro\node_modules\rhea-promise\dist\lib\link.js:247:43
    at new Promise (<anonymous>)
    at Receiver.<anonymous> (C:\Code\azure-max-listeners-repro\node_modules\rhea-promise\dist\lib\link.js:191:34)
    at Generator.next (<anonymous>)
    at C:\Code\azure-max-listeners-repro\node_modules\tslib\tslib.js:169:75
    at new Promise (<anonymous>)
Stopped reading from partition 19, reason: Shutdown
Stopped reading from partition 20, reason: Shutdown
Stopped reading from partition 0, reason: Shutdown
Stopped reading from partition 1, reason: Shutdown
Stopped reading from partition 2, reason: Shutdown
Stopped reading from partition 3, reason: Shutdown
Stopped reading from partition 4, reason: Shutdown
Stopped reading from partition 5, reason: Shutdown
Stopped reading from partition 6, reason: Shutdown
Stopped reading from partition 7, reason: Shutdown
Stopped reading from partition 8, reason: Shutdown
Stopped reading from partition 9, reason: Shutdown
Stopped reading from partition 10, reason: Shutdown
Stopped reading from partition 11, reason: Shutdown
Stopped reading from partition 12, reason: Shutdown
Stopped reading from partition 13, reason: Shutdown
Stopped reading from partition 14, reason: Shutdown
Stopped reading from partition 15, reason: Shutdown
Stopped reading from partition 16, reason: Shutdown
Stopped reading from partition 17, reason: Shutdown
Stopped reading from partition 18, reason: Shutdown

Additional context
The warning stems from rhea-promise subscribing to the disconnected event for every partition at the same time: https://github.com/amqp/rhea-promise/blob/e37362a3df7ce9661ff6b7f20980a093596963b1/lib/link.ts#L296
Related PR (in draft since 2021):
https://github.com/amqp/rhea-promise/pull/78/files

Hi @the-ress,
Thanks for opening this report! I did some debugging today and I traced the issue to the rhea library. The problem is that the Connection event emitter installs one listener per partition/topic and currently Event Hubs has a limit of up to 1024 partitions and Service Bus has a limit of up to 10k topics. I created this commit raising the limit to 10k https://github.com/deyaaeldeen/rhea/commit/493b34b8460604635240d50518e76bd4f97f7896 but I would like to discuss it internally with the team first.
Now that we determined this problem is in rhea, I'll go ahead and close this issue.

I opened https://github.com/amqp/rhea/pull/418.


Possible extension to SalesOrderLines?

I absolutely love this feature for opportunities and I know our sales team will find it helpful.  However, we do have a team that could use this for sales order line entry since they do not typically have orders that originate from opportunities/quotes.  Would it be possible to have this extensible to the sales order creation process?

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

ID: b4df288e-9a0b-6e28-3932-fc373c3501cf
Version Independent ID: bb6fba1e-7c15-11ce-df5c-f726513f60f7
Content: Preview: Add products to an opportunity by using the enhanced experience
Content Source: ce/sales-enterprise/add-products-enhanced-experience.md
Service: dynamics-365-sales
GitHub Login: @shubhadaj
Microsoft Alias: shujoshi

@neilshelley: Thank you for reaching out to us. The enhanced experience of adding products is now extended to quote, order, and invoice entities, and the feature is released in preview. You can find more information here: https://docs.microsoft.com/dynamics365/sales-enterprise/add-products-qoi-enhanced
Hope this helps!

@neilshelley: Thank you for reaching out to us. The enhanced experience of adding products is now extended to quote, order, and invoice entities, and the feature is released in preview. You can find more information here: https://docs.microsoft.com/dynamics365/sales-enterprise/add-products-qoi-enhanced
Hope this helps!


I'm trying to build for macOS and I'm pulling my hair out over this.

Describe your problem here.
 I don't know what to do... I reinstalled discord-rpc a thousand times with no luck. I don't want to remove Discord functionality and no one else seems to have this error!

Are you modding a build from source or with Lua?
Source
What is your build target?
Mac
Did you edit anything in this build? If so, mention or summarize your changes.
No.

 All my homes hate macOS.


fix some docs

After this is merged, I'll upload the package to Hackage using my personal Hackage account, then add Bellroy to the list of maintainers. It this process correct?

Done. I'm merging


Feature: logging

What extent of logging are you considering?
Better error messages? (Instead of only returning the error from the twitch api, add some extra info like if there is an error being returned for connecting, console.log('Issues that may cause this: invalid client id, oauth token is invalid, username is spelled incorrectly.');)
Be more verbose at all times? (Ex. console.log everything that seems relevant)
Full blown logging system? (Global logger object, different log levels, maybe use chalk to colour output, dev can specify the log level they want to see by specifying in the constructor object (ex. { debug: { loglevel: warn } } shows all log levels up to warn, or none can be put if they dont want to see any, or default it to info when left blank) and then end up logging everything that would need to be logged with proper log levels)

I was actually thinking about adding something like winston or bunyan (no sense reinventing the wheel 😆). By default, we would log instantiation, methods and errors to the console, but you could also provide your own transports and stream logs to files or databases.
I really like your idea of helpful error messages; we should definitely do that ... but yeah, I'm leaning towards winston. What do you think?

I was looking at packages and found one called Signale. I used to use Tracer with my discord bot. you can look at my djStapleton repo and see the usage of signale. it's really neat to be honest

sent from my flip phone

--
Taylor Stapleton(587) 447-9036
twitch-apis/twitch-js wrote:
I was actually thinking about adding something like winston or bunyan (no sense reinventing the wheel 😆). By default, we would log instantiation, methods and errors to the console, but you could also provide your own transports and stream logs to files or databases.
I really like your idea of helpful error messages; we should definitely do that ... but yeah, I'm leaning towards winston. What do you think?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I speculate that having some suggestions in the error messages would be handy to clean out some issue spam such as "Error: " (I couldnt think of an error off the top of my head) There will still be people making issues and being vague like "she 🅱roke"


Broken Link

https://docs.substrate.io/rustdocs/latest/pallet_contracts/index.html

@jjmiranda, we moved Rust documentation out from under the docs.substrate.io umbrella. You can find the latest here:
https://paritytech.github.io/substrate/master/pallet_contracts/index.html


Transmitting the Input to the Decoder

Hi all,
I was looking at the code released to generate predictions with CodeT5+
from transformers import AutoModelForSeq2SeqLM, AutoTokenizer
import torch

checkpoint = "Salesforce/instructcodet5p-16b"
device = "cuda" # for GPU usage or "cpu" for CPU usage

tokenizer = AutoTokenizer.from_pretrained(checkpoint)
model = AutoModelForSeq2SeqLM.from_pretrained(checkpoint,
                                              torch_dtype=torch.float16,
                                              low_cpu_mem_usage=True,
                                              trust_remote_code=True).to(device)

encoding = tokenizer("def print_hello_world():", return_tensors="pt").to(device)
encoding['decoder_input_ids'] = encoding['input_ids'].clone()
outputs = model.generate(**encoding, max_length=15)
print(tokenizer.decode(outputs[0], skip_special_tokens=True))

and I was wondering what would it be the difference if we factor out the following instruction encoding['decoder_input_ids'] = encoding['input_ids'].clone() ?
What changes under the hood of the model?
Thanks in advance for any help you can provide on this.

Hi there, by setting encoding['decoder_input_ids'] = encoding['input_ids'].clone(), we also feed the text prompt to decoder to better provide the prefix contexts for the models. We find that this is very helpful for CodeT5+ models >=2B, as these models have a deep decoder initilized from frozen GPT-style LLMs, doing this can have a better compatibility with the default behaviours of GPT models. Noth that for CodeT5+ 220M and 770M, they do not need such additional prefix prompts as they are pretrained from scratch.

@yuewang-cuhk
Crystal clear!
Many thanks :)


Fix issue with Remote Clipboard (#451)

Signed-off-by: Aleksandr Muravja<EMAIL_ADDRESS>

Work is done, but I found strange behaviour that on Grid click won't trigger ClipboardUtils callback at all.
Locally it works, remotely - not.
It seems like I spending too much time here. Void....


Replace node.obmSettings with obms collection.

Create new obms model and tests.
Remove obmSettings property from nodes resource.
Add 1-N relation from nodes to OBMs

Supports:
https://github.com/RackHD/on-http/pull/312
https://github.com/RackHD/on-tasks/pull/243
https://github.com/RackHD/on-http/pull/334
@RackHD/corecommitters

+1

@benbp I pushed a new patch to address your comments.

:+1:

:+1:


TOTK update 1.2.1

update 1.2.1 available.
Can you update cheat file ?

+1, your repo is normally fastest to update for new patches, but I guess you're probably on break from doing this atm, so whenever you return :D

Check pull requests. I posted the updated codes for TOTK 1.2.1 you should be able to see my edits in there. At least till he approves a merge to his main branch

Oh i already grabbed them from PR moment i saw it :D

Thx for the answer, i will test this right now 😊


cdn.crowdtwist line blocks the Borderlands Insider Program pages images from loading

Title tells it all, you can see it for yourself.
https://borderlands.com/en-US/vip-rewards/

@AkiraJkr  the domain in question is a tracker and that is why it's blocked:
script.src = '//cdn.crowdtwist.com/trck/prod/2/'
On my end(chromium browser) nothing showing up when trying to open it and there are bunch of errors in  dev tools so.Most likely there is a problem with the website and the cdn.crowdtwist is not the culprit here.

Thanks Dan @dnmTX.
Closing.


[top/testplan] Add some description to csrng test items

Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

i added some description to one of the tests, let me know if this makes sense.


fix scrolling on frozen columns

fix issue #1423 and #1417
will also handle scrolling for normal records as well and normalize scrolling across browsers, in order to ensure the same scrolling behaviour and eliminate synchronicity issues between frozen and unfrozen columns.

damnit, I messed up my branches... =/ let's see how I can fix this.


merge MMM-Wallpaper with WallberryTheme

its would be so awesome to merge the inputs/sources here to wallberrytheme
https://github.com/kolbyjack/MMM-Wallpaper
its able to show much more than unsplash, especially iCloud is very powerful :)

Yeah, I was just looking if WallberryTheme can display wallpapers from reddit :)


Problem connecting to ic2 machines

It seems like the flux point won't connect to any ic2 machines. The only exception being the reactor chamber which connects without a problem to flux plugs. Flux points also seem to connect to ic2 cables but won't transmit eu.

It's not an issue, as flux points aren't a part of IC2 energy network, you can connect it to MFSU and use IC2 cables, or directly use mekanism cables. I'm not likely to support for it.


[T3A3][W15-A2] Wang Ce

Some comments added. Feel free to add more comment if you have any questions. Once you are done, you may close the PR after reading comments.


Added initial support for StopActions

I added the option to select a stop action for a scene in the SpeedDialWindow.
This allows me to switch between scenes/chases without the pan/tilt channels to reset.
This is very useful when controlling QLC+ live.
See the discussion on the forum:
https://sourceforge.net/p/qlcplus/discussion/general/thread/5717245b
Regards,
Joep Admiraal

Hi Joep, thanks for investigating this.
However, I won't merge it as this is a workaround for the specific case you found and it's not a generic solution. Plus, it's very invasive.
I've investigated a similar behaviour in the past too, and I concluded that the real problem is that transactions between QLC+ functions don't happen in the same Mastertimer tick.
So basically what happens is:

function running (several ticks)
function stop: in this tick (if fade out is set to 0) QLC+ will commit to reset all the values to 0
new function start: this happens the next tick after stop, but it's too late since values are considered to be 0.

This involves also HTP channels and I noticed it a while back on some sequences, where I had lights going black for 1 tick. Quite annoying.
Now many changes have been done on QLC+ since then and I just noticed that when a function is stopped, LTP channels are reset to 0 as well. In the original QLC code, they were staying at the last value. Only HTP channels were reset to 0.
I believe this is the main problem and I think we should fix that.
The fix must be done at a very low level. Any "high level" change, is my opinion, is a workaround and doesn't solve the real issue.

Hi Massimo,
Thanks voor your detailed comment.
Fixing this issue low level would solve my problem with the pan/tilt functions. However I think it would also change the way the system currently works. I think a lot of people are now relying on this behaviour. Therefore I think we still need to provide an option to choose between resetting to 0 and keeping the last value. That being said, fixing the issue low level seems like a good plan. I can take a look at it but it will take some (a lot) of time. Since I almost have no free time at the moment :)

A reminder for me:
[MasterTimer] *********** tick: 2022 **********
[MasterTimer] ticking DMX source 0
[MasterTimer] ticking fader (channels: 0 )
Function start(). Name: "New Chaser 3" ID:  3 , startTime: 0
Function stop(). Name: "New Chaser 2" ID:  2
[MasterTimer] *********** tick: 2023 **********
void ChaserRunner::postRun(MasterTimer*, QList<Universe*>)
Function stop(). Name: "middle" ID:  0
Function postRun. Name: "New Chaser 2" ID:  2
void Function::resetElapsed()
Function postRun. Name: "middle" ID:  0
void Function::resetElapsed()
Function preRun. Name: "New Chaser 3" ID:  3
Function start(). Name: "up" ID:  1 , startTime: 0
[MasterTimer] ticking DMX source 0
[MasterTimer] ticking fader (channels: 2 )
[MasterTimer] *********** tick: 2024 **********
Scene preRun. ID:  1
Function preRun. Name: "up" ID:  1
[MasterTimer] ticking DMX source 0
[MasterTimer] ticking fader (channels: 0 )
Joep, this is worse than I thought. The switch between two chasers happens in 3 ticks...not 2 :(
I don't know if the debug messages I've added caused that, but we definitely need the switch to happen in a single tick.

Hey Joep, I think I have good news !
This change: https://github.com/mcallegari/qlcplus/commit/829bb9384399b685a890e10ec6c5b052eda71452
Seems to fix your zero test project as well.
Can you please confirm and eventually report if I broke anything else that I'm not aware of ATM ?
Thanks

Hi Massimo,
Great news!
I'll check it out and do some tests today and tomorrow.

I tested it and did not see any problems with the commit.

Great, thanks for the feedback !


Feature 2373- move widgets to all locations

Changes Made

Moved the following widgets from road_segment_widgets to all_location_widgets:

killed_and_injured_count_per_age_group
killed_and_injured_count_per_age_group_stacked
injured_count_by_severity

Fixed the /api/infographics-data endpoint's news_flash_id argument (reflects the update in the Swagger documentation).

Resolved a bug in the histogram within the killed_and_injured_count_per_age_group widget. Previously, when there were no accidents with the "unknown" type, the widgets crashed. This issue can be observed in the production logs. For instance, the following API call was successful:

https://www.anyway.co.il/api/infographics-data?lang=he&news_flash_id=154488&years_ago=5

However, the same API call with a 3-year parameter instead of 5 resulted in a crash:

https://www.anyway.co.il/api/infographics-data?lang=he&news_flash_id=154488&years_ago=3

The issue arises when there are no accidents with an "unknown" type within the last 3 years, as all the accident ages are known during that period.

Codecov Report
Attention: 13 lines in your changes are missing coverage. Please review.

Comparison is base (dfca9c4) 52.98% compared to head (2bcd172) 53.27%.

Files
Patch %
Lines

...ed_and_injured_count_per_age_group_widget_utils.py
60.00%
6 Missing :warning:

...ations_widgets/injured_count_by_severity_widget.py
80.00%
3 Missing :warning:

anyway/widgets/widget_utils.py
71.42%
2 Missing :warning:

...s/killed_and_injured_count_per_age_group_widget.py
83.33%
1 Missing :warning:

...ously_injured_killed_in_bicycles_scooter_widget.py
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #2511      +/-   ##
==========================================
+ Coverage   52.98%   53.27%   +0.29%
==========================================
  Files         117      117
  Lines        9645     9674      +29
==========================================
+ Hits         5110     5154      +44
+ Misses       4535     4520      -15

Flag
Coverage Δ

unittests
53.27% <74.50%> (+0.29%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


We need a way to define UserBoundInterface close behavior

Right now it just automatically closes if you get too far away from the entity the UserBoundInterface is on (i.e. too far away from the computer), but we should be able to override some function to write our own checks that run every tick (or something along those lines)
For instance, the reason I bring this up is that I want to make the scalpel UserBoundInterface close if you drop the tool or get too far away from the person you're operating on. Right now, it will only close if you drop the scalpel and walk away from it.

activatableui handles most of this on the content side


Incorrect error messages while parsing (non-existent) logical operators or, and, and xor

Tested on dartpad.dev, but the issue is probably very old.
  int x=0, y=0;
  x = x or y;
  if (x==0 or y==0) {

  }

Error messages:
Binary operator 'or' is written as '|' instead of the written out word.
Try replacing 'or' with '|'
Binary operator 'or' is written as '||' instead of the written out word.
Try replacing 'or' with '||'
There's some confusion about what is written how and instead of what.

Looks like this is working as intended: The first occurrence of or has operands of type int, hence | could be used; the second occurrence has operands of type bool, hence || could be used. It is true that | is defined for the type bool today, but the vastly most common case is probably that a developer who writes or between two boolean expressions would want to use || rather than |.

"is written" should be written as "should be written" or "must be written".
"Is written", as written in the dart error message, doesn't have the intended modality.
The issue is small and rare, and I might have been the only user who has ever seen this message though :-)


chest cooldown timer

yes it's real the long awaited chest cooldown timer
i didn't actually test if it works after transferring the code to pickaxe mod-

i forgot to add some parenthesis AAA pain

oh wait it was a bunch of other things tabnine did a big oops

small nitpick
Testing env

main env

weird, for me it works perfectly fine (just tested), check console or try disabling other mods you're using

weird, for me it works perfectly fine (just tested), check console or try disabling other mods you're using

oh sry, i meant that it would overlap with my FPS counter


dialog.json

Add double quotes around names please. This is not valid JSON and looks here ugly.
https://github.com/jwa107/Photoshop-Export-Layers-to-Files-Fast/blob/master/dialog.json

As long as it's parsed by the Photoshop and does what it needs to, I don't really care. The convention was chosen according to the Ps documentation. If it really bothers you so much, why don't you add the quotes yourself, test it and then make a push request? I'd be happy to review and merge it if it works. It's github -- everyone can contribute.


Added kubelet parameters to configure cpu manager policy

Based on the design discussion with stake holders i have raised this PR. This is related to the PR
https://github.com/opennetworkinglab/aether-k8s/pull/4.

Thanks!


Feature/daemonset

What this PR does / why we need it:
Which issue this PR fixes
Support for DaemonSet in Traefik (see #9797)
Special notes for your reviewer:
hostNetwork:
enabled: true
deployType: "DaemonSet"
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md

Thanks for that, there is a very minor issue with this but it got me, in the Readme it is hostNetwork.enable while in the config hostNetwork.enable*d* is used

LGTM!

When can we expect this to be reviewed and merged? :-)

It's a shame that this isn't merged yet.

Activity!

It's a bit annoying how the bot marks it stale when it's waiting on Helm devs themselves rather than the community.

@sylvainblot @nmengin 🔢
just a notification reminder,
expected this feature 2 years ago

Hello everyone,  Should we make assign this PR to the chart owners? Please fix the conflicting, I'd like to help on this, thanks.

Any reviewers able to allocate time on this issue? (Or reject PR if this is out of scope for the chart)
cc'ing all reviewers from https://github.com/helm/charts/blob/master/stable/traefik/OWNERS
@emilevauge
@dtomcej
@timoreimann
@vdemeester
@nmengin
@mmatur
@ldez
@Juliens
@jbdoumenjou
@geraldcroes
@SantoDE
@errm

Hello All,
Despite not posting on this PR, we have been discussing this question a lot within the Traefik team.
I will share some of our conclusions here.
Traefik version 1 is in maintenance mode, and the v2 release will be imminent. This is why work on the v1 helm chart has been minimal since the spring, as most people will want to upgrade to v2 once it is GA. For this reason, we are hesitant to make any large changes to this chart.
Traefik v2 will not support LetsEncrypt in multi-node mode, so the option of a daemonset will not work if users want to use LE. For this reason, it makes more sense to use a deployment with anti-affinity to push pods to all nodes instead of using a daemonset.
Due to issues with root users, privileged ports, etc, it is unlikely that we will want to use host networking, or host ports on a public and production-recommended chart.
It is more likely that the v2 chart will move in the opposite direction, and move entirely to non-root, and non-privileged ports, with the option to override if your environment supports them.
Another reason against a daemonset is that many users don't require the same number of Traefik pods as they have nodes to handle traffic. Usually a few will suffice. If not, then the resource limits should be tweaked, or run a few more replicas. With people running on public clouds, resources = $$$. We should be aiming to be efficient, and scale up when needed, not down.
Finally, the examples in the Traefik v2 documentation etc will be deployment only (for the reasons above). It would make sense to keep the configuration similar to assist users with their needs. We haven't come across a compelling reason to add a daemonset requirement for v2, so until that time, we will proceed with deployment only.
I hope this gives some clarity into this issue, and how we view it moving forward.
Thanks,
The Traefik Team.

@dtomcej Thanks for the clear follow-up.
Waiting for Traefik v2 seems like the better option, and using anit-affinity should work quite well.
The only issue I see is that you might end up with 2 traefik pods on a node if you use a deployment and the number of replicas are same as number of nodes. There is an option that will be implemented in kubernetes 1.15 that will solve this (https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20190221-even-pods-spreading.md)
Since you are deprecating multi-node setup with LetsEncrypt. I'm guessing the replacement option will be to run cert-manager + and have traefik point to cert-manager certificates?

not stale

@sylvainblot
Could you rebase and resolve conflict files please? Thank you.
stable/traefik/Chart.yaml
stable/traefik/README.md
stable/traefik/templates/deployment.yaml
stable/traefik/templates/service.yaml
stable/traefik/values.yaml

Is the only thing needed to rebase and solve conflicts? i can do it now.
This would be really usefull

Happy New Year!

The deployment defaults to 1 replica, which has the full feature support. This was one of the main reasons to use the deployment in the first place.

Yes of course, but I guess no all users of Traefik use Lets Encrypt and set 1 to replica isn't for production.

it makes more sense to use a deployment with anti-affinity to push pods to all nodes instead of using a DaemonSet

It's exactly the same (let's encrypt not supported too), except the config is more complex

that many users don't require the same number of Traefik pods as they have nodes to handle traffic

So not all users, plus like i say earlier, i've already experiment issue when you don't have enough replica or well spread in the cluster with compute autoscaling. DaemonSet ensure you always have one pod (if your cluster still have one node)

Agree with @Eraac and other posters here (inc me above :slightly_smiling_face:).
The decision to ignore / move away from (additional) daemonset support is not a good one. The project owners appear to only be considering one specific use case, but others do need the ability to run as a daemonset for at least the several reasons / scenarios given above.
Traefik maintainers, is there any harm in allowing this feature that people need?

Hello All,
Despite not posting on this PR, we have been discussing this question a lot within the Traefik team.
I will share some of our conclusions here.
Traefik version 1 is in maintenance mode, and the v2 release will be imminent. This is why work on the v1 helm chart has been minimal since the spring, as most people will want to upgrade to v2 once it is GA. For this reason, we are hesitant to make any large changes to this chart.
Traefik v2 will not support LetsEncrypt in multi-node mode, so the option of a daemonset will not work if users want to use LE. For this reason, it makes more sense to use a deployment with anti-affinity to push pods to all nodes instead of using a daemonset.
Due to issues with root users, privileged ports, etc, it is unlikely that we will want to use host networking, or host ports on a public and production-recommended chart.
It is more likely that the v2 chart will move in the opposite direction, and move entirely to non-root, and non-privileged ports, with the option to override if your environment supports them.

This is a valid argument for hostNetwork assumming the node running traffic doesn't have an additional firewall (or securityGroup). Firewall or not, hostNetwork opens the admin port, which is not good.
hostPort support in this chart or the v2 chart would be great (with or without daemonset). There is no security risk in opening hostPort 80/443. In a cloud environment, it is not the best option but there are other use cases that need it.

Another reason against a daemonset is that many users don't require the same number of Traefik pods as they have nodes to handle traffic. Usually a few will suffice. If not, then the resource limits should be tweaked, or run a few more replicas. With people running on public clouds, resources = $$$. We should be aiming to be efficient, and scale up when needed, not down.
Finally, the examples in the Traefik v2 documentation etc will be deployment only (for the reasons above). It would make sense to keep the configuration similar to assist users with their needs. We haven't come across a compelling reason to add a daemonset requirement for v2, so until that time, we will proceed with deployment only.
I hope this gives some clarity into this issue, and how we view it moving forward.
Thanks,
The Traefik Team.


Prevent silent updates of Miniconda during installation

Specify exact Miniconda version in the installer to prevent issues like #3240
Simplify installer code (toward #3191)
Update Conda repo URL

Thanks! This is a good  idea.


Maptile Settings in Global Options

As discussed in #714 and also in the early days of Wavelog, there were always the wish or necessarity to change the maptile server or specific configurations, like the subdomain system (a chinese maptile provider uses 1234 instead abc)
I would be happy if @violarulan could test this aswell
This PR brings a new point in the global options to change these configurations. There is one change in the leaflet.js where I replaced the hardcoded abc subdomain system with a variable.
All Maps are tested.
Static Map is tested.
You can test the option by setting the chinese map provider of autonavi
Maptiles Server URL
https://webrd0{s}.is.autonavi.com/appmaptile?lang=zh_cn&size=1&scale=1&style=7&x={x}&y={y}&z={z}
Subdomain System of Maptile Server
1234
URL of the Copyright Source
https://autonavi.com/ (probably not reachable from EU internet, but tileserver is reachable)
Name of the Copyright Source
AutoNavi

I added a "Reset to default" Button to go back easily. Also I added a link to the Wiki where we can collect tested and working maptile Servers.
I kindly ask @violarulan to complete the information for the chinese servers
Here: https://github.com/wavelog/wavelog/wiki/Maptile-Server

Works as expected perfectlly.

Thanks for the feedback

Other than error the first time I enter the option (because no option exists), it's working.

@AndreasK79 fixed

hello, this option does not work for me. Here is my config. And the map is blank.

After I reset to the default, the map shows up.
: )

Hello, maybe there is a bug.
After I set the new server and return to the dashboard, I need to force-refresh the page with ctrl + F5. Otherwise, the map is blank.

This is related to the caching of your browser and normal behaviour :)


[More Library Icons] amount is drastically reduced when enabled

Because how steam loads library, there is an issue with  selecting a game with dpad/L stick.
Only 4 rows are loaded.
If use a touch screen it seems like it loads a group of 6 games every time

It may be because of scroll size doesn't changed... (maybe...)

Duplicate issue of #5


What does use_previous_artifact mean and do ?

This is a question about the parameter use_previous_artifact, for job upgrade.
What does it mean and what does it do ?
A github search gave nothing relevant.

Trello card: [#125] What does use_previous_artifact mean and do ?

Hi @Andromelus
This parameter indicates whether :

you want to upload a new package for your new job version (use_previous_artifact=false)
you want to keep the package of the existing job version and just update the command line for this new version for instance (use_previous_artifact=true)

Thanks.
It would be nice if this was written in the documentation.

Agreed, we'll try to improve our documentation with more details about each attribute.


Add new feature Double Y Axis Lines

One can apply two different scales of data on the same linear plot.
Description
This plot will display two lines with different y axis. Hence, it will help in plot two different arrays with different values together on the same plot.
Motivation and Context

I want to compare my training and testing data. But that was not feasible using the single line plot. Hence, introduced a new feature.
How Has This Been Tested?

Here is the code, that I have used for testing it:
import visdom
import numpy as np
import time
viz = visdom.Visdom()
viz.delete_env("testing")
viz.env = "testing"
opts=dict(
    side='right',
    nameY1='Training',
    nameY2='Testing',
)
while True:
    X=np.arange(20)
    Y1=np.random.randint(0,20,20)
    Y2=np.random.randint(100,200,20)
    viz.double_yaxis_Lines(X,Y1,Y2,win="test",opts=opts)
    time.sleep(2)

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] For JavaScript changes, I have re-generated the minified JavaScript code.

Hi @ubaidsworld - thanks for the contribution. Before I review, can you please put the commits of #717 and #718 into this PR? They shouldn't be separate

Hello @JackUrb Thank you for your response. I am new to this sort of process, so I did not know how to put the mentioned commit in one. Hence,I created separate  one. Can you please help me, so I can put them together and next time I will keep that in mind.
Also, please review my this suggestion : #715

I see this:

I do not know the reason for this.

You'll need to first merge the other branches into this one, by changing the revision you are trying to merge into. The other PRs should read "wants to merge 1 commit into ubaidsworld:patch-2 from <other_branch>" if you've done this correctly, and then you'll be allowed to merge those commits into this branch.
If you're making these patches locally in a terminal through git, you can rebase the commits on top of each other in one stack and then push the highest part of the stack.

Thank you @JackUrb . I will close these PRs and create new one with all in one PRs.


[Feature] Don't open all synced files as working files

Every time you sync, every single file is opened as a working file. This isn't always desired. It would be better if only the working files from the host are opened on the client as working files. Additionally, all the files are also opened on the host as working files, even if they weren't before.

Good idea. Will probably improve performance as well.


Remove MB and GB from lines in the report

Remove MB and GB from lines in the report.
These mess up importing the data into Excel when I do copy/paste, text to data.
They are already identified as MB and GB in the Item Name, so it's redundant.

Where are you seeing the redundancy?
FolderName : Packages
SizeBytes  :<PHONE_NUMBER>0
SizeKB     : 14733819.87
SizeMB     : 14388.5
SizeGB     : 14.05
FullPath   : C:\Users\thegn\AppData\Local\Packages
HostName   : njarzr

I tested the output and exporting to CSV myself and do not see it.

Thank you for looking at this.  In the example, it says:
| .EXAMPLE  |
|  |  |
|  |  Get-FolderSize | Format-Table -AutoSize |
|  |  |
|  |  |
|  |  FolderName SizeBytes SizeMB SizeGB |
|  |   |
|  |  $GetCurrent 193768 0.18 MB 0.00 GB |
|  |  $RECYCLE.BIN 20649823 19.69 MB 0.02 GB |
|  |  $SysReset 53267392 50.80 MB 0.05 GB |
|  |  Config.Msi 0.00 MB 0.00 GB |
|  |  Documents and Settings 0.00 MB 0.00 GB |
|  |  Games<PHONE_NUMBER>1 46,274.36 MB 45.19 GB |
The "MB" and "GB" on each line is redundant since the title already says SizeMB and SizeGB.
I keep the number of things that I know about PowerShell to a minimum, so I don't remember how to export to a .csv file.  If I need to do that in a script then I will look it up, but I won't do that if I have a result that I want in a spreadsheet.  I will do a copy/paste which is easy to remember.  I will also do an Excel Text to Columns which is also easy.  The "MB" and "GB" end up as an extra column.  I took these out of Get-FolderSize after I downloaded it.  It looks like you already fixed this but didn't update the .EXAMPLE.
😷 Andy Young 😷
@.***
On Tuesday, January 31, 2023 at 12:37:09 p.m. EST, Mike Roberts<EMAIL_ADDRESS>wrote:

Where are you seeing the redundancy?
FolderName : Packages
SizeBytes  :<PHONE_NUMBER>0
SizeKB     : 14733819.87
SizeMB     : 14388.5
SizeGB     : 14.05
FullPath   : C:\Users\thegn\AppData\Local\Packages
HostName   : njarzr
I tested the output and exporting to CSV myself and do not see it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


bake known checkpoints

I'd like to remove the serialization for this, and turn it into rust code, probably using something like databake, but that's a little heavyweight - we could then just
struct KnownBlocks<'a> {
    calibnet: &'a [(i64, Cid)],
    mainnet: &'a [(i64, Cid)],
}
const KNOWN_BLOCKS: KnownBlocks<'static> = todo!();

Unfortunately, multihash and cid aren't there yet:
https://github.com/multiformats/rust-cid/issues/138
https://github.com/multiformats/rust-multihash/issues/330
Originally posted by @aatifsyed in https://github.com/ChainSafe/forest/pull/3220#discussion_r1267382019

Those issues are closed as wrong, we can proceed with this, see https://github.com/multiformats/rust-multihash/pull/331#issuecomment-1660013138


It always sent the spawn notice with WSL setting

Summary
When I open yml files, the VS code always sent me a notice with "spawn C:\WINDOWS\system32\cmd.exe ENOENT", and doesn't get any extension features work.
I have specified the WSL path for the vscode-ansible settings like these:
"ansible.ansibleLint.path": "\\wsl$\\Ubuntu-20.04\\usr\\bin\\ansible-lint",
"ansible.ansible.path": "\\wsl$\\Ubuntu-20.04\\usr\\bin\\ansible",
"ansible.ansiblePlaybook.path": "\\wsl$\\Ubuntu-20.04\\usr\\bin\\ansible-playbook",
"ansible.python.interpreterPath": "\\wsl$\\Ubuntu-20.04\\usr\\bin\\python3",

Does the extension not support the setting like this way?
Extension version
0.4.5
VS Code version
1.59.1
Ansible Version
# ansible --version
ansible 2.9.6
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/kaol/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.8.10 (default, Jun  2 2021, 10:49:15) [GCC 9.4.0]

OS / Environment
Windows 10, WSL (Ubuntu 20.04.3 LTS), ansible-lint 4.2.0
Relevant log output
No response

I am experiencing same issue ...

Same here

Same issue here, but only when running vscode in Windows (outside WSL).  If I disable ansible-lint (setting id ansible.ansibleLint.enabled), the error goes away.  Looks like the plugin might be trying to run linting on a Windows machine (without Ansible/ansible-lint installed)

Hey- Thanks for this. The code base is currently going through a major refactoring effort. We don't expect this to be an issue when that work is done. This will remain open until sometime after the new version is released. Please check back in the next month or so.

Same issue here, but only when running vscode in Windows (outside WSL). If I disable ansible-lint (setting id ansible.ansibleLint.enabled), the error goes away. Looks like the plugin might be trying to run linting on a Windows machine (without Ansible/ansible-lint installed)

Yes, if we disable the ansible-lint, the error will disappear. But we still cannot get any extension features worked.

There's a high chance that this will get fixed after https://github.com/ansible/ansible-language-server/pull/5 is merged.

After update on 3 Nov 21 and above pull request was merged - this issue persists
spawn C:\WINDOWS\system32\cmd.exe ENOENT

After a cursory look I guess this error could be due to child_process.exec calling cmd.exe and cmd not being able to call or find the executable in WSL. Therefore the error ENOENT (No such file or directory).
I think the commandRunner.runCommand won't ever find the ansible executable on Windows with WSL.
C:\>cd \\wsl$\Ubuntu\usr\bin\
'\\wsl$\Ubuntu\usr\bin\'
CMD does not support UNC paths as current directories.

You would need to call ansible via wsl.exe <path to ansible in WSL> (e.g. wsl.exe /usr/bin/ansible), which is not possible to set via the ansible.ansible.path setting.
After researching for a while and installing WSL Remote I found this in the README:

For Windows users, this extension works perfectly well with extensions such as
Remote - WSL and Remote - Containers.

Oh well. I should've read more carefully.
Configuring Remote WSL.

@1p1eq11 did it work for you with WSL2 or WSL1?

@webknjaz I am using WSL2.

Oh, interesting. I wasn't sure if we would be able to run tests in such an env (GitHub Actions does not support WSL2).


Fixes 9875: supporting gcp secret manager

Describe your changes:
Fixes 9875

I worked on support the gcp secret manager.

Type of change:

[x] New feature

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My PR title is Fixes <issue-number>: <short explanation>
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[x] The issue properly describes why the new feature is needed, what's the goal, and how we are building it. Any discussion
or decision-making process is reflected in the issue.
[x] I have updated the documentation.
[x] I have added tests around the new logic.

Thanks @nakaken-churadata for the PR

I'm fixing some errors in pytest. Wait a moment, please.

I'm investigating errors in pytest. Wait a moment, please.

@harshach @akash-jain-10
I have fixed some errors. Could you review this PR?


Apply validation rules before saving models

Models should allow to specify validation rules, like {range:1..5} for integers, {isSigingUser} for usernames.
These rules should be validated before saving an object.

Would be great to be able to execute custom functions for the models on the server 👍

I am in favor of doing this in the way that is described in the Radiks decentralization proposal - this would have less reliance on custom server code, and include validation that other servers could validate.
https://forum.blockstack.org/t/radiks-decentralization-proposal/8400


Try out Keptn with cert-manager.io

Goal
Try out how to set up Keptn with cert-manager.io.
Details

try out setup with self signed certs
try out setup with issued, fully valid certs
after the research, update https://github.com/keptn/lifecycle-toolkit/issues/1622 so that any needed updates will get implemented

Results
Keptn does not work with cert-manager.io out-of-the-box without further action. There are multiple problems we should try to solve.
Problem No.1
The first problem when disabling keptn-cert-manager is that in metrics-operator and lifecycle-operator we are still using parts of its library to actually check for existence of keptn-certs Secret in the system. This should not be happening as keptn-cert-manager is disabled and because this checks only for secret named keptn-certs, where there should not be any rule for users to the need to name their Secret containing the certificates to keptn-certs.
Problem No.2
When using the Keptn with cert-manager.io with keptn-cert-manager being disabled, we can see cert-manager.io/inject-ca-from: 'helmtests/keptn-certs' annotations on mutating webhooks, validating webhooks and CRDs. This annotation according to cert-manager.io docs means, cert-manager.io is awaiting a Certificate CR named keptn-certs located in keptn-system namespace. This CR additionally awaits Issuer CR, which defines what type of certificate will be used (self-signed, CA,... more info here). The current solution to this problem is to manually create Cerificate and Issuer CRs and apply them to the cluster. Be aware that it is needed that the Ceritficate CR is named keptn-certs and located in the Keptn namespace (by default keptn-system), see here.
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: keptn-certs
  namespace: keptn-system
spec:
  dnsNames:
  - lifecycle-webhook-service.keptn-system.svc
  - lifecycle-webhook-service.keptn-system.svc.cluster.local
  - metrics-webhook-service.keptn-system.svc
  - metrics-webhook-service.keptn-system.svc.cluster.local
  issuerRef:
    kind: Issuer
    name: klt-selfsigned-issuer
  secretName: keptn-certs
---
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: klt-selfsigned-issuer
  namespace: keptn-system
spec:
  selfSigned: {}

Applying those CRs will cause the creation of keptn-certs Secret, which will satisfy the keptn-cert-manager check in lifecycle-operator and metrics-operator -> this is describled in Problem No.1

Thanks for the nice write up of the problem. Most likely, the problem was introduced by creating the common lib in the Keptn Cert Manager to watch for the secrets to be mounted. See https://github.com/keptn/lifecycle-toolkit/blob/main/lifecycle-operator/main.go#L403.
If the Keptn Cert Manager is not deployed, we should disable this 🤔

Thanks for the nice write up of the problem. Most likely, the problem was introduced by creating the common lib in the Keptn Cert Manager to watch for the secrets to be mounted. See https://github.com/keptn/lifecycle-toolkit/blob/main/lifecycle-operator/main.go#L403. If the Keptn Cert Manager is not deployed, we should disable this 🤔

Yes absolutely, but that isn't the full solution for the problem, there still need to be a Certificate CR present in the system, as the cert-manager.io/inject-ca-from annotation is pointing to it

The research is done and the result are the 3 tickets that are referenced above.


Lab clean up

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Jemiah Sius seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Twitter Security Warning

Zombie has working great for testing Passport with a Twitter strategy.
The only problem is, every time I use it to login, I get an email warning me that there is an unusual login. I want to receive these alerts, just not from Zombie/Passport.
How can I get around this with Zombie?

Aren't you running the test on a remote server? This could be caused by the different IP location.

Another reason could be the user agent


Global error handlers as dedicated bundle (resolve #28)

Global error handlers transpiled separately from the main bundle. (resolve #28)


1318: Setup backend test database

Short description
To add integration tests for the backend (#1532), we need to setup a database.
In my opinion, using test containers library is the most convenient way to implement that.
Proposed changes
Add IntegrationTest base class, where database setup is performed.
To add new tests that require a database, new test classes must extend the IntegrationTest class.
Side effects
Would be nice to check if everything works on different OS.
I have only tested it on Ubuntu 22.04.4 LTS.
Resolved issues
Fixes: #1318

@f1sh1918
All backend tests are run with ./gradlew test, so the new tests are also included in CI already

@f1sh1918 try gradlew instead of gradle, it means “gradle wrapper”

@ztefanie could you please also check that you can run the new tests locally?

maybe @steffenkleinle can test it, since steffi will be on vacation

@f1sh1918 try gradlew instead of gradle, it means “gradle wrapper”

doesn't help. its my local jvm config. nevermind


Fix/no account overwrite

Temporary workaround while we wait for this to be fixed and released: https://github.com/stellar/stellar-cli/issues/1380
This makes it so that generate will not be run if the account already exists. I used keys fund because its the only command under keys that actually hits the network. Presumably if one is testing on a local instance of stellar then their local identity files might be out of date so using fund is the only way to guarantee they actually exist on the network that I'm aware of. If there is a better command to query the network for the existence of the key let me know and I will use that.

Addressed Willem's comment, should be good to go!


Add eslint, restructure tests and update to ES2015

I understand this is a very large change. If you want any different linting or to not merge it at all I totally understand.
Am planning to make a lot more contributions in the future just wanted to modernize things a bit first.

Hello, thanks for the PR! I agree this package could use some love in cleaning up code and modernizing it like this. In fact I started doing something similar in a branch a while ago but never got to finish it. One thing I would request is to use StandardJS for code style and linting for all the reasons they list. You can still set env's similarly to how you have already:
"standard": {
    "env": {
      "node": true,
      "mocha": true
    }
  }

Maybe address that and I'll look over everything and we'll try and get this merged.
Thanks

Sure is your project will switch

@bojand Done

Thanks for this! Published as 0.14.0.


custom optimization

I'm using dense_vnet for segment  ct data. Its working fine. But , I need to customize optimization, loss function and activation function. I got error like no object takes no parameters for optimization. I used AdaBound optim in engine and call get instance & return without tf.train.[optim].

We're need more information than this to see where the issue is. Do you have a log output? Is an actual exception being raised somewhere we have a trace for? Do you have the ini file you used?

And I tried to solve above error, new error as appear.
TypeError: compute_gradients() missing 1 required positional argument: 'loss'
training_nifty_log:
INFO:niftynet:2019-08-08 14:11:05,840: starting segmentation application
INFO:niftynet:2019-08-08 14:11:05,840: csv_file =  not found, writing to "/home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/naso-Gtv.csv" instead.
INFO:niftynet:2019-08-08 14:11:05,841: Overwriting existing: "/home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/naso-Gtv.csv".
INFO:niftynet:2019-08-08 14:11:05,841: [naso-Gtv] search file folders, writing csv file /home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/naso-Gtv.csv
INFO:niftynet:2019-08-08 14:11:05,847: csv_file =  not found, writing to "/home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/label.csv" instead.
INFO:niftynet:2019-08-08 14:11:05,847: Overwriting existing: "/home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/label.csv".
INFO:niftynet:2019-08-08 14:11:05,847: [label] search file folders, writing csv file /home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/label.csv
INFO:niftynet:2019-08-08 14:11:05,852:
Number of subjects 50, input section names: ['subject_id', 'naso-Gtv', 'label']
-- using all subjects (without data partitioning).
WARNING:niftynet:2019-08-08 14:11:05,854: From /home/poornesh/my-projects/new-Nifty/niftynet/layer/base_layer.py:26: The name tf.make_template is deprecated. Please use tf.compat.v1.make_template instead.
WARNING:niftynet:2019-08-08 14:11:05,856: From /home/poornesh/my-projects/new-Nifty/niftynet/io/image_loader.py:107: The name tf.logging.debug is deprecated. Please use tf.compat.v1.logging.debug instead.
INFO:niftynet:2019-08-08 14:11:06,020: Image reader: loading 50 subjects from sections ('naso-Gtv',) as input [image]
INFO:niftynet:2019-08-08 14:11:06,020: Image reader: loading 50 subjects from sections ('label',) as input [label]
INFO:niftynet:2019-08-08 14:11:06,024: reading size of preprocessed images
INFO:niftynet:2019-08-08 14:11:06,028: initialised resize sampler {'image': (1, 152, 144, 144, 1, 1), 'image_location': (1, 7), 'label': (1, 152, 144, 144, 1, 1), 'label_location': (1, 7)}
INFO:niftynet:2019-08-08 14:11:06,031: using DenseVNet
INFO:niftynet:2019-08-08 14:11:06,034: Initialising Dataset from 50 subjects...
WARNING:niftynet:2019-08-08 14:11:06,357:
niftyreg_image_resampling is not installed; falling back onto
niftynet.layer.resampler.ResamplerLayer. To allow fast resampling,
please see installation instructions in
niftynet/contrib/niftyreg_image_resampling/README.md
WARNING:niftynet:2019-08-08 14:11:08,032: From /home/poornesh/my-projects/new-Nifty/niftynet/layer/linear_resize.py:60: The name tf.image.resize_bilinear is deprecated. Please use tf.compat.v1.image.resize_bilinear instead.
WARNING:niftynet:2019-08-08 14:11:08,595:
niftyreg_image_resampling is not installed; falling back onto
niftynet.layer.resampler.ResamplerLayer. To allow fast resampling,
please see installation instructions in
niftynet/contrib/niftyreg_image_resampling/README.md
WARNING:niftynet:2019-08-08 14:11:08,741: From /home/poornesh/my-projects/new-Nifty/niftynet/engine/AdaBound.py:10: The name tf.train.Optimizer is deprecated. Please use tf.compat.v1.train.Optimizer instead.
CRITICAL:niftynet:2019-08-08 14:11:08,741: ModuleNotFoundError("No module named 'dense_vnet_abdominal_ct'",)
CRITICAL:niftynet:2019-08-08 14:11:08,741: segmentation loss: Could not import object"dice" from "dense_vnet_abdominal_ct.dice_hinge"
INFO:niftynet:2019-08-08 14:12:25,742: starting segmentation application
INFO:niftynet:2019-08-08 14:12:25,743: csv_file =  not found, writing to "/home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/naso-Gtv.csv" instead.
INFO:niftynet:2019-08-08 14:12:25,743: Overwriting existing: "/home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/naso-Gtv.csv".
INFO:niftynet:2019-08-08 14:12:25,743: [naso-Gtv] search file folders, writing csv file /home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/naso-Gtv.csv
INFO:niftynet:2019-08-08 14:12:25,749: csv_file =  not found, writing to "/home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/label.csv" instead.
INFO:niftynet:2019-08-08 14:12:25,749: Overwriting existing: "/home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/label.csv".
INFO:niftynet:2019-08-08 14:12:25,749: [label] search file folders, writing csv file /home/poornesh/my-projects/new-Nifty/models/naso-Gtv-selubound/label.csv
INFO:niftynet:2019-08-08 14:12:25,755:
Number of subjects 50, input section names: ['subject_id', 'naso-Gtv', 'label']
-- using all subjects (without data partitioning).
WARNING:niftynet:2019-08-08 14:12:25,757: From /home/poornesh/my-projects/new-Nifty/niftynet/layer/base_layer.py:26: The name tf.make_template is deprecated. Please use tf.compat.v1.make_template instead.
WARNING:niftynet:2019-08-08 14:12:25,760: From /home/poornesh/my-projects/new-Nifty/niftynet/io/image_loader.py:107: The name tf.logging.debug is deprecated. Please use tf.compat.v1.logging.debug instead.
INFO:niftynet:2019-08-08 14:12:25,923: Image reader: loading 50 subjects from sections ('naso-Gtv',) as input [image]
INFO:niftynet:2019-08-08 14:12:25,923: Image reader: loading 50 subjects from sections ('label',) as input [label]
INFO:niftynet:2019-08-08 14:12:25,927: reading size of preprocessed images
INFO:niftynet:2019-08-08 14:12:25,931: initialised resize sampler {'image': (1, 152, 144, 144, 1, 1), 'image_location': (1, 7), 'label': (1, 152, 144, 144, 1, 1), 'label_location': (1, 7)}
INFO:niftynet:2019-08-08 14:12:25,934: using DenseVNet
INFO:niftynet:2019-08-08 14:12:25,937: Initialising Dataset from 50 subjects...
WARNING:niftynet:2019-08-08 14:12:26,260:
niftyreg_image_resampling is not installed; falling back onto
niftynet.layer.resampler.ResamplerLayer. To allow fast resampling,
please see installation instructions in
niftynet/contrib/niftyreg_image_resampling/README.md
WARNING:niftynet:2019-08-08 14:12:27,937: From /home/poornesh/my-projects/new-Nifty/niftynet/layer/linear_resize.py:60: The name tf.image.resize_bilinear is deprecated. Please use tf.compat.v1.image.resize_bilinear instead.
WARNING:niftynet:2019-08-08 14:12:28,506:
niftyreg_image_resampling is not installed; falling back onto
niftynet.layer.resampler.ResamplerLayer. To allow fast resampling,
please see installation instructions in
niftynet/contrib/niftyreg_image_resampling/README.md
WARNING:niftynet:2019-08-08 14:12:28,651: From /home/poornesh/my-projects/new-Nifty/niftynet/engine/AdaBound.py:10: The name tf.train.Optimizer is deprecated. Please use tf.compat.v1.train.Optimizer instead.
INFO:niftynet:2019-08-08 14:12:28,652: Import [dice] from /home/poornesh/niftynet/extensions/dense_vnet_abdominal_ct/dice_hinge.py.


'NoneType' object is not subscriptable

Hi,
I tried using "bare_extraction" and "extract" to fetch some news websites but for some URLs , I got this error:
'NoneType' object is not subscriptable
example_url= 'https://www.isna.ir/news/1400070704627/تصاویر-خارق-العاده-از-زمین-که-توسط-ماهواره-لندست-ثبت-شده-اند'
any idea?

Hi @ReySadeghi, I cannot reproduce the bug with standard extraction, are you using the latest version of the software and are you using particular options?

yes, I used version of 1.3.0
my code is this:
`import trafilatura
downloaded = trafilatura.fetch_url(url)
json_file=trafilatura.bare_extraction(downloaded, include_links=True)
#json_file= trafilatura.extract(downloaded, output_format='json')
date=json_file['date']`

Hi again,
thanks for your response.
also I tried both methods : "bare_extraction" and "extract",
but I couldn't download and got the Error.
I tried download section that you mentioned, but nothing happen.
I think maybe my URL is under restriction by trafilatura.
I also tried with vpn but it doesn't solve.
could you please try to download this URL:
url="https://www.isna.ir/news/1400070704627/تصاویر-خارق-العاده-از-زمین-که-توسط-ماهواره-لندست-ثبت-شده-اند"

Hi @ReySadeghi I have trouble downloading the page as well with Python, I'm afraid this problem exceeds the scope of the library.
This solution works on the command-line:
wget -O - "https://www.isna.ir/news/1400070704627/%D8%AA%D8%B5%D8%A7%D9%88%DB%8C%D8%B1-%D8%AE%D8%A7%D8%B1%D9%82-%D8%A7%D9%84%D8%B9%D8%A7%D8%AF%D9%87-%D8%A7%D8%B2-%D8%B2%D9%85%DB%8C%D9%86-%DA%A9%D9%87-%D8%AA%D9%88%D8%B3%D8%B7-%D9%85%D8%A7%D9%87%D9%88%D8%A7%D8%B1%D9%87-%D9%84%D9%86%D8%AF%D8%B3%D8%AA-%D8%AB%D8%A8%D8%AA-%D8%B4%D8%AF%D9%87-%D8%A7%D9%86%D8%AF" | trafilatura