Slicer configuration button: Unknown option: gui-mode

I'm using a GNU/Linux-x86_64
My Repetier-Host version is V1.6.2
I  load the slicer gui with "--gui" there is no "--gui-mode" in Slic3r.
All seems to work as expected except I can't open slic3r configuration from slicer tab:
18:29:50.835 : <Slic3r> Unknown option: gui-mode
18:29:50.838 : <Slic3r> Slic3r 1.3.0-dev is a STL-to-GCODE translator for RepRap 3D printers
18:29:50.838 : <Slic3r> written by Alessandro Ranellucci<EMAIL_ADDRESS>- http://slic3r.org/
18:29:50.838 : <Slic3r> Usage: slic3r.pl [ OPTIONS ] [ file.stl ] [ file2.stl ] ...
18:29:50.838 : <Slic3r>     --help              Output this usage screen and exit
18:29:50.838 : <Slic3r>     --version           Output the version of Slic3r and exit
18:29:50.838 : <Slic3r>     --save <file>       Save configuration to the specified file
18:29:50.838 : <Slic3r>     --load <file>       Load configuration from the specified file. It can be used
18:29:50.838 : <Slic3r>                         more than once to load options from multiple files.
18:29:50.838 : <Slic3r>     -o, --output <file> File to output gcode to (by default, the file will be saved
18:29:50.838 : <Slic3r>                         into the same directory as the input file using the
18:29:50.838 : <Slic3r>                         --output-filename-format to generate the filename.) If a
18:29:50.838 : <Slic3r>                         directory is specified for this option, the output will
18:29:50.838 : <Slic3r>                         be saved under that directory, and the filename will be
18:29:50.838 : <Slic3r>                         generated by --output-filename-format.
18:29:50.838 : <Slic3r>
18:29:50.838 : <Slic3r>   Non-slicing actions (no G-code will be generated):
18:29:50.838 : <Slic3r>     --repair            Repair given STL files and save them as <name>_fixed.obj
18:29:50.838 : <Slic3r>     --cut <z>           Cut given input files at given Z (relative) and export
18:29:50.838 : <Slic3r>                         them as <name>_upper.stl and <name>_lower.stl
18:29:50.838 : <Slic3r>     --split             Split the shells contained in given STL file into several STL files
18:29:50.838 : <Slic3r>     --info              Output information about the supplied file(s) and exit
18:29:50.838 : <Slic3r>
18:29:50.838 : <Slic3r>     -j, --threads <num> Number of threads to use
18:29:50.838 : <Slic3r>   GUI options:
18:29:50.838 : <Slic3r>     --gui               Forces the GUI launch instead of command line slicing (if you
18:29:50.838 : <Slic3r>                         supply a model file, it will be loaded into the plater)
18:29:50.838 : <Slic3r>     --autosave <file>   Automatically export current configuration to the specified file
18:29:50.838 : <Slic3r>   Output options:
18:29:50.838 : <Slic3r>     --output-filename-format
18:29:50.838 : <Slic3r>                         Output file name format; all config options enclosed in brackets
18:29:50.838 : <Slic3r>                         will be replaced by their values, as well as [input_filename_base]
18:29:50.838 : <Slic3r>                         and [input_filename] (default: [input_filename_base].gcode)
18:29:50.838 : <Slic3r>     --post-process      Generated G-code will be processed with the supplied script;
18:29:50.838 : <Slic3r>                         call this more than once to process through multiple scripts.
18:29:50.838 : <Slic3r>     --export-svg        Export a SVG file containing slices instead of G-code.
18:29:50.838 : <Slic3r>     -m, --merge         If multiple files are supplied, they will be composed into a single
18:29:50.838 : <Slic3r>                         print rather than processed individually.
18:29:50.838 : <Slic3r>
18:29:50.838 : <Slic3r>   Printer options:
18:29:50.839 : <Slic3r>     --nozzle-diameter   Diameter of nozzle in mm (default: 0.5)
18:29:50.839 : <Slic3r>     --print-center      Coordinates in mm of the point to center the print around
18:29:50.839 : <Slic3r>                         (default: 100,100)
18:29:50.839 : <Slic3r>     --z-offset          Additional height in mm to add to vertical coordinates
18:29:50.839 : <Slic3r>                         (+/-, default: 0)
18:29:50.839 : <Slic3r>     --z-steps-per-mm    Number of full steps per mm of the Z axis. Experimental feature for
18:29:50.839 : <Slic3r>                         preventing rounding issues.
18:29:50.839 : <Slic3r>     --gcode-flavor      The type of G-code to generate (reprap/teacup/repetier/makerware/sailfish/mach3/machinekit/smoothie/no-extrusion,
18:29:50.839 : <Slic3r>                         default: reprap)
18:29:50.839 : <Slic3r>     --use-relative-e-distances Enable this to get relative E values (default: no)
18:29:50.839 : <Slic3r>     --use-firmware-retraction  Enable firmware-controlled retraction using G10/G11 (default: no)
18:29:50.839 : <Slic3r>     --use-volumetric-e  Express E in cubic millimeters and prepend M200 (default: no)
18:29:50.839 : <Slic3r>     --gcode-arcs        Use G2/G3 commands for native arcs (experimental, not supported
18:29:50.839 : <Slic3r>                         by all firmwares)
18:29:50.839 : <Slic3r>     --gcode-comments    Make G-code verbose by adding comments (default: no)
18:29:50.839 : <Slic3r>     --vibration-limit   Limit the frequency of moves on X and Y axes (Hz, set zero to disable;
18:29:50.839 : <Slic3r>                         default: 0)
18:29:50.839 : <Slic3r>     --pressure-advance  Adjust pressure using the experimental advance algorithm (K constant,
18:29:50.839 : <Slic3r>                         set zero to disable; default: 0)
18:29:50.839 : <Slic3r>
18:29:50.839 : <Slic3r>   Filament options:
18:29:50.839 : <Slic3r>     --filament-diameter Diameter in mm of your raw filament (default: 3)
18:29:50.839 : <Slic3r>     --extrusion-multiplier
18:29:50.839 : <Slic3r>                         Change this to alter the amount of plastic extruded. There should be
18:29:50.839 : <Slic3r>                         very little need to change this value, which is only useful to
18:29:50.839 : <Slic3r>                         compensate for filament packing (default: 1)
18:29:50.839 : <Slic3r>     --temperature       Extrusion temperature in degree Celsius, set 0 to disable (default: 200)
18:29:50.839 : <Slic3r>     --first-layer-temperature Extrusion temperature for the first layer, in degree Celsius,
18:29:50.839 : <Slic3r>                         set 0 to disable (default: same as --temperature)
18:29:50.839 : <Slic3r>     --bed-temperature   Heated bed temperature in degree Celsius, set 0 to disable (default: 0)
18:29:50.839 : <Slic3r>     --first-layer-bed-temperature Heated bed temperature for the first layer, in degree Celsius,
18:29:50.839 : <Slic3r>                         set 0 to disable (default: same as --bed-temperature)
18:29:50.839 : <Slic3r>
18:29:50.839 : <Slic3r>   Speed options:
18:29:50.839 : <Slic3r>     --travel-speed      Speed of non-print moves in mm/s (default: 130)
18:29:50.839 : <Slic3r>     --perimeter-speed   Speed of print moves for perimeters in mm/s (default: 60)
18:29:50.839 : <Slic3r>     --small-perimeter-speed
18:29:50.839 : <Slic3r>                         Speed of print moves for small perimeters in mm/s or % over perimeter speed
18:29:50.839 : <Slic3r>                         (default: 15)
18:29:50.839 : <Slic3r>     --external-perimeter-speed
18:29:50.839 : <Slic3r>                         Speed of print moves for the external perimeter in mm/s or % over perimeter speed
18:29:50.839 : <Slic3r>                         (default: 50%)
18:29:50.839 : <Slic3r>     --infill-speed      Speed of print moves in mm/s (default: 80)
18:29:50.839 : <Slic3r>     --solid-infill-speed Speed of print moves for solid surfaces in mm/s or % over infill speed
18:29:50.839 : <Slic3r>                         (default: 20)
18:29:50.839 : <Slic3r>     --top-solid-infill-speed Speed of print moves for top surfaces in mm/s or % over solid infill speed
18:29:50.840 : <Slic3r>                         (default: 15)
18:29:50.840 : <Slic3r>     --support-material-speed
18:29:50.840 : <Slic3r>                         Speed of support material print moves in mm/s (default: 60)
18:29:50.840 : <Slic3r>     --support-material-interface-speed
18:29:50.840 : <Slic3r>                         Speed of support material interface print moves in mm/s or % over support material
18:29:50.840 : <Slic3r>                         speed (default: 100%)
18:29:50.840 : <Slic3r>     --bridge-speed      Speed of bridge print moves in mm/s (default: 60)
18:29:50.840 : <Slic3r>     --gap-fill-speed    Speed of gap fill print moves in mm/s (default: 20)
18:29:50.840 : <Slic3r>     --first-layer-speed Speed of print moves for bottom layer, expressed either as an absolute
18:29:50.840 : <Slic3r>                         value or as a percentage over normal speeds (default: 30)
18:29:50.840 : <Slic3r>
18:29:50.840 : <Slic3r>   Acceleration options:
18:29:50.840 : <Slic3r>     --perimeter-acceleration
18:29:50.840 : <Slic3r>                         Overrides firmware's default acceleration for perimeters. (mm/s^2, set zero
18:29:50.840 : <Slic3r>                         to disable; default: 0)
18:29:50.840 : <Slic3r>     --infill-acceleration
18:29:50.840 : <Slic3r>                         Overrides firmware's default acceleration for infill. (mm/s^2, set zero
18:29:50.840 : <Slic3r>                         to disable; default: 0)
18:29:50.840 : <Slic3r>     --bridge-acceleration
18:29:50.840 : <Slic3r>                         Overrides firmware's default acceleration for bridges. (mm/s^2, set zero
18:29:50.840 : <Slic3r>                         to disable; default: 0)
18:29:50.840 : <Slic3r>     --first-layer-acceleration
18:29:50.840 : <Slic3r>                         Overrides firmware's default acceleration for first layer. (mm/s^2, set zero
18:29:50.840 : <Slic3r>                         to disable; default: 0)
18:29:50.840 : <Slic3r>     --default-acceleration
18:29:50.840 : <Slic3r>                         Acceleration will be reset to this value after the specific settings above
18:29:50.840 : <Slic3r>                         have been applied. (mm/s^2, set zero to disable; default: 0)
18:29:50.840 : <Slic3r>
18:29:50.840 : <Slic3r>   Accuracy options:
18:29:50.840 : <Slic3r>     --layer-height      Layer height in mm (default: 0.3)
18:29:50.840 : <Slic3r>     --first-layer-height Layer height for first layer (mm or %, default: 0.35)
18:29:50.840 : <Slic3r>     --infill-every-layers
18:29:50.840 : <Slic3r>                         Infill every N layers (default: 1)
18:29:50.840 : <Slic3r>     --solid-infill-every-layers
18:29:50.840 : <Slic3r>                         Force a solid layer every N layers (default: 0)
18:29:50.840 : <Slic3r>
18:29:50.840 : <Slic3r>   Print options:
18:29:50.840 : <Slic3r>     --perimeters        Number of perimeters/horizontal skins (range: 0+, default: 3)
18:29:50.840 : <Slic3r>     --top-solid-layers  Number of solid layers to do for top surfaces (range: 0+, default: 3)
18:29:50.840 : <Slic3r>     --bottom-solid-layers  Number of solid layers to do for bottom surfaces (range: 0+, default: 3)
18:29:50.840 : <Slic3r>     --solid-layers      Shortcut for setting the two options above at once
18:29:50.840 : <Slic3r>     --fill-density      Infill density (range: 0%-100%, default: 20%)
18:29:50.840 : <Slic3r>     --fill-angle        Infill angle in degrees (range: 0-90, default: 45)
18:29:50.840 : <Slic3r>     --fill-pattern      Pattern to use to fill non-solid layers (default: stars)
18:29:50.840 : <Slic3r>     --fill-gaps         Fill gaps with single passes (default: yes)
18:29:50.840 : <Slic3r>     --external-infill-pattern Pattern to use to fill solid layers.
18:29:50.840 : <Slic3r>                         (Shortcut for --top-infill-pattern and --bottom-infill-pattern)
18:29:50.840 : <Slic3r>     --top-infill-pattern Pattern to use to fill top solid layers (default: rectilinear)
18:29:50.840 : <Slic3r>     --bottom-infill-pattern Pattern to use to fill bottom solid layers (default: rectilinear)
18:29:50.841 : <Slic3r>     --start-gcode       Load initial G-code from the supplied file. This will overwrite
18:29:50.841 : <Slic3r>                         the default command (home all axes [G28]).
18:29:50.841 : <Slic3r>     --end-gcode         Load final G-code from the supplied file. This will overwrite
18:29:50.841 : <Slic3r>                         the default commands (turn off temperature [M104 S0],
18:29:50.841 : <Slic3r>                         home X axis [G28 X], disable motors [M84]).
18:29:50.841 : <Slic3r>     --before-layer-gcode  Load before-layer-change G-code from the supplied file (default: nothing).
18:29:50.841 : <Slic3r>     --layer-gcode       Load layer-change G-code from the supplied file (default: nothing).
18:29:50.841 : <Slic3r>     --toolchange-gcode  Load tool-change G-code from the supplied file (default: nothing).
18:29:50.841 : <Slic3r>     --seam-position     Position of loop starting points (random/nearest/aligned, default: aligned).
18:29:50.841 : <Slic3r>     --external-perimeters-first Reverse perimeter order. (default: no)
18:29:50.841 : <Slic3r>     --spiral-vase       Experimental option to raise Z gradually when printing single-walled vases
18:29:50.841 : <Slic3r>                         (default: no)
18:29:50.841 : <Slic3r>     --only-retract-when-crossing-perimeters
18:29:50.841 : <Slic3r>                         Disable retraction when travelling between infill paths inside the same island.
18:29:50.841 : <Slic3r>                         (default: no)
18:29:50.841 : <Slic3r>     --solid-infill-below-area
18:29:50.841 : <Slic3r>                         Force solid infill when a region has a smaller area than this threshold
18:29:50.841 : <Slic3r>                         (mm^2, default: 70)
18:29:50.841 : <Slic3r>     --infill-only-where-needed
18:29:50.841 : <Slic3r>                         Only infill under ceilings (default: no)
18:29:50.841 : <Slic3r>     --infill-first      Make infill before perimeters (default: no)
18:29:50.841 : <Slic3r>
18:29:50.841 : <Slic3r>    Quality options (slower slicing):
18:29:50.841 : <Slic3r>     --extra-perimeters  Add more perimeters when needed (default: yes)
18:29:50.841 : <Slic3r>     --avoid-crossing-perimeters Optimize travel moves so that no perimeters are crossed (default: no)
18:29:50.841 : <Slic3r>     --thin-walls        Detect single-width walls (default: yes)
18:29:50.841 : <Slic3r>     --detect-bridging-perimeters  Detect bridging perimeters and apply bridge flow, speed and fan
18:29:50.841 : <Slic3r>                         (default: yes)
18:29:50.841 : <Slic3r>
18:29:50.841 : <Slic3r>    Support material options:
18:29:50.841 : <Slic3r>     --support-material  Generate support material for overhangs
18:29:50.841 : <Slic3r>     --support-material-threshold
18:29:50.841 : <Slic3r>                         Overhang threshold angle (range: 0-90, set 0 for automatic detection,
18:29:50.841 : <Slic3r>                         default: 60%)
18:29:50.841 : <Slic3r>     --support-material-pattern
18:29:50.841 : <Slic3r>                         Pattern to use for support material (default: pillars)
18:29:50.841 : <Slic3r>     --support-material-spacing
18:29:50.841 : <Slic3r>                         Spacing between pattern lines (mm, default: 2.5)
18:29:50.841 : <Slic3r>     --support-material-angle
18:29:50.841 : <Slic3r>                         Support material angle in degrees (range: 0-90, default: 0)
18:29:50.841 : <Slic3r>     --support-material-contact-distance
18:29:50.841 : <Slic3r>                         Vertical distance between object and support material (0+, default: 0.2)
18:29:50.841 : <Slic3r>     --support-material-interface-layers
18:29:50.841 : <Slic3r>                         Number of perpendicular layers between support material and object (0+, default: 3)
18:29:50.841 : <Slic3r>     --support-material-interface-spacing
18:29:50.841 : <Slic3r>                         Spacing between interface pattern lines (mm, set 0 to get a solid layer, default: 0)
18:29:50.841 : <Slic3r>     --raft-layers       Number of layers to raise the printed objects by (range: 0+, default: 0)
18:29:50.841 : <Slic3r>     --support-material-enforce-layers
18:29:50.841 : <Slic3r>                         Enforce support material on the specified number of layers from bottom,
18:29:50.841 : <Slic3r>                         regardless of --support-material and threshold (0+, default: 0)
18:29:50.841 : <Slic3r>     --support-material-buildplate-only
18:29:50.841 : <Slic3r>                         Only create support if it lies on a build plate. Don't create support on a print. (default: no)
18:29:50.842 : <Slic3r>     --dont-support-bridges
18:29:50.842 : <Slic3r>                         Experimental option for preventing support material from being generated under bridged areas (default: yes)
18:29:50.842 : <Slic3r>
18:29:50.842 : <Slic3r>    Retraction options:
18:29:50.842 : <Slic3r>     --retract-length    Length of retraction in mm when pausing extrusion (default: 2)
18:29:50.842 : <Slic3r>     --retract-speed     Speed for retraction in mm/s (default: 40)
18:29:50.842 : <Slic3r>     --retract-restart-extra
18:29:50.842 : <Slic3r>                         Additional amount of filament in mm to push after
18:29:50.842 : <Slic3r>                         compensating retraction (default: 0)
18:29:50.842 : <Slic3r>     --retract-before-travel
18:29:50.842 : <Slic3r>                         Only retract before travel moves of this length in mm (default: 2)
18:29:50.842 : <Slic3r>     --retract-lift      Lift Z by the given distance in mm when retracting (default: 0)
18:29:50.842 : <Slic3r>     --retract-lift-above Only lift Z when above the specified height (default: 0)
18:29:50.842 : <Slic3r>     --retract-lift-below Only lift Z when below the specified height (default: 0)
18:29:50.842 : <Slic3r>     --retract-layer-change
18:29:50.842 : <Slic3r>                         Enforce a retraction before each Z move (default: no)
18:29:50.842 : <Slic3r>     --wipe              Wipe the nozzle while doing a retraction (default: no)
18:29:50.842 : <Slic3r>
18:29:50.842 : <Slic3r>    Retraction options for multi-extruder setups:
18:29:50.842 : <Slic3r>     --retract-length-toolchange
18:29:50.842 : <Slic3r>                         Length of retraction in mm when disabling tool (default: 10)
18:29:50.842 : <Slic3r>     --retract-restart-extra-toolchange
18:29:50.842 : <Slic3r>                         Additional amount of filament in mm to push after
18:29:50.842 : <Slic3r>                         switching tool (default: 0)
18:29:50.842 : <Slic3r>
18:29:50.842 : <Slic3r>    Cooling options:
18:29:50.842 : <Slic3r>     --cooling           Enable fan and cooling control
18:29:50.842 : <Slic3r>     --min-fan-speed     Minimum fan speed (default: 35%)
18:29:50.842 : <Slic3r>     --max-fan-speed     Maximum fan speed (default: 100%)
18:29:50.842 : <Slic3r>     --bridge-fan-speed  Fan speed to use when bridging (default: 100%)
18:29:50.842 : <Slic3r>     --fan-below-layer-time Enable fan if layer print time is below this approximate number
18:29:50.842 : <Slic3r>                         of seconds (default: 60)
18:29:50.842 : <Slic3r>     --slowdown-below-layer-time Slow down if layer print time is below this approximate number
18:29:50.842 : <Slic3r>                         of seconds (default: 5)
18:29:50.842 : <Slic3r>     --min-print-speed   Minimum print speed (mm/s, default: 10)
18:29:50.842 : <Slic3r>     --disable-fan-first-layers Disable fan for the first N layers (default: 3)
18:29:50.842 : <Slic3r>     --fan-always-on     Keep fan always on at min fan speed, even for layers that don't need
18:29:50.842 : <Slic3r>                         cooling
18:29:50.842 : <Slic3r>
18:29:50.842 : <Slic3r>    Skirt options:
18:29:50.842 : <Slic3r>     --skirts            Number of skirts to draw (0+, default: 1)
18:29:50.842 : <Slic3r>     --skirt-distance    Distance in mm between innermost skirt and object
18:29:50.842 : <Slic3r>                         (default: 6)
18:29:50.842 : <Slic3r>     --skirt-height      Height of skirts to draw (expressed in layers, 0+, default: 1)
18:29:50.842 : <Slic3r>     --min-skirt-length  Generate no less than the number of loops required to consume this length
18:29:50.842 : <Slic3r>                         of filament on the first layer, for each extruder (mm, 0+, default: 0)
18:29:50.842 : <Slic3r>     --brim-width        Width of the brim that will get added to each object to help adhesion
18:29:50.843 : <Slic3r>                         (mm, default: 0)
18:29:50.843 : <Slic3r>     --interior-brim-width  Width of the brim that will get printed inside object holes to help adhesion
18:29:50.843 : <Slic3r>                         (mm, default: 0)
18:29:50.843 : <Slic3r>
18:29:50.843 : <Slic3r>    Transform options:
18:29:50.843 : <Slic3r>     --scale             Factor for scaling input object (default: 1)
18:29:50.843 : <Slic3r>     --rotate            Rotation angle in degrees (0-360, default: 0)
18:29:50.843 : <Slic3r>     --duplicate         Number of items with auto-arrange (1+, default: 1)
18:29:50.843 : <Slic3r>     --duplicate-grid    Number of items with grid arrangement (default: 1,1)
18:29:50.843 : <Slic3r>     --duplicate-distance Distance in mm between copies (default: 6)
18:29:50.843 : <Slic3r>     --dont-arrange      Don't arrange the objects on the build plate. The model coordinates
18:29:50.843 : <Slic3r>                         define the absolute positions on the build plate.
18:29:50.843 : <Slic3r>                         The option --print-center will be ignored.
18:29:50.843 : <Slic3r>     --xy-size-compensation
18:29:50.843 : <Slic3r>                         Grow/shrink objects by the configured absolute distance (mm, default: 0)
18:29:50.843 : <Slic3r>
18:29:50.843 : <Slic3r>    Sequential printing options:
18:29:50.843 : <Slic3r>     --complete-objects  When printing multiple objects and/or copies, complete each one before
18:29:50.843 : <Slic3r>                         starting the next one; watch out for extruder collisions (default: no)
18:29:50.843 : <Slic3r>     --extruder-clearance-radius Radius in mm above which extruder won't collide with anything
18:29:50.843 : <Slic3r>                         (default: 20)
18:29:50.843 : <Slic3r>     --extruder-clearance-height Maximum vertical extruder depth; i.e. vertical distance from
18:29:50.843 : <Slic3r>                         extruder tip and carriage bottom (default: 20)
18:29:50.843 : <Slic3r>
18:29:50.843 : <Slic3r>    Miscellaneous options:
18:29:50.843 : <Slic3r>     --notes             Notes to be added as comments to the output file
18:29:50.843 : <Slic3r>     --resolution        Minimum detail resolution (mm, set zero for full resolution, default: 0)
18:29:50.843 : <Slic3r>
18:29:50.843 : <Slic3r>    Flow options (advanced):
18:29:50.843 : <Slic3r>     --extrusion-width   Set extrusion width manually; it accepts either an absolute value in mm
18:29:50.843 : <Slic3r>                         (like 0.65) or a percentage over layer height (like 200%)
18:29:50.843 : <Slic3r>     --first-layer-extrusion-width
18:29:50.843 : <Slic3r>                         Set a different extrusion width for first layer
18:29:50.843 : <Slic3r>     --perimeter-extrusion-width
18:29:50.843 : <Slic3r>                         Set a different extrusion width for perimeters
18:29:50.843 : <Slic3r>     --external-perimeter-extrusion-width
18:29:50.843 : <Slic3r>                         Set a different extrusion width for external perimeters
18:29:50.843 : <Slic3r>     --infill-extrusion-width
18:29:50.843 : <Slic3r>                         Set a different extrusion width for infill
18:29:50.843 : <Slic3r>     --solid-infill-extrusion-width
18:29:50.843 : <Slic3r>                         Set a different extrusion width for solid infill
18:29:50.843 : <Slic3r>     --top-infill-extrusion-width
18:29:50.843 : <Slic3r>                         Set a different extrusion width for top infill
18:29:50.843 : <Slic3r>     --support-material-extrusion-width
18:29:50.844 : <Slic3r>                         Set a different extrusion width for support material
18:29:50.844 : <Slic3r>     --infill-overlap    Overlap between infill and perimeters (default: 55%)
18:29:50.844 : <Slic3r>     --bridge-flow-ratio Multiplier for extrusion when bridging (> 0, default: 1)
18:29:50.844 : <Slic3r>
18:29:50.844 : <Slic3r>    Multiple extruder options:
18:29:50.844 : <Slic3r>     --extruder-offset   Offset of each extruder, if firmware doesn't handle the displacement
18:29:50.844 : <Slic3r>                         (can be specified multiple times, default: 0x0)
18:29:50.844 : <Slic3r>     --perimeter-extruder
18:29:50.844 : <Slic3r>                         Extruder to use for perimeters and brim (1+, default: 1)
18:29:50.844 : <Slic3r>     --infill-extruder   Extruder to use for infill (1+, default: 1)
18:29:50.844 : <Slic3r>     --solid-infill-extruder   Extruder to use for solid infill (1+, default: 1)
18:29:50.844 : <Slic3r>     --support-material-extruder
18:29:50.844 : <Slic3r>                         Extruder to use for support material, raft and skirt (1+, default: 1)
18:29:50.844 : <Slic3r>     --support-material-interface-extruder
18:29:50.844 : <Slic3r>                         Extruder to use for support material interface (1+, default: 1)
18:29:50.844 : <Slic3r>     --ooze-prevention   Drop temperature and park extruders outside a full skirt for automatic wiping
18:29:50.844 : <Slic3r>                         (default: no)
18:29:50.844 : <Slic3r>     --standby-temperature-delta
18:29:50.844 : <Slic3r>                         Temperature difference to be applied when an extruder is not active and
18:29:50.844 : <Slic3r>                         --ooze-prevention is enabled (default: -5)
18:29:50.844 : <Slic3r>

When we wrote 1.6.2 slic3r 1.2.9 was the newest version and there the option was --gui-mode. Looks like this was now changed making it incompatible with old calls. So we will add a new version in manager for next release to select --gui for next release.
Thanks for the hint.

Glad to know will be fixed.
Until then, I did create a patch to slic3r.pl:
30c30
<         'gui'                   => \$opt{gui},
---
>         'gui|gui-mode=s'          => \$opt{gui},

With it i'm able to open slic3r via configuration button, but i need to open the file manually from ~/.local/share/RepetierHost/composition.stl

It is actually composition.amf that gets created when you try to slice with slic3r. stl is used for CuraEngine.


Page break & blank page issue on safari

While using pdf.js, i am facing issues like page breaks, margin issue, font issue and alignment issues on Safari. then i tried in pdf.js demo link that's showing alternate blank page issue. Kindly help on this. Could you please help on this..

Without a sample PDF file and more information about your configuration (OS name and version, browser version) there is not much we can do. Does it happen with printing or also with regular rendering?

Hi @timvandermeij,
Issues are mostly able to reproduce in all Safari browser versions, I have checked in OS X Yosemite - 10.10.5  / Safari 9.0.  while rendering its looking good, but we are facing issue on print the page.
Its automatically print the page URL on the top(header) of the printed page. But page URL's not printing on any other browsers.
I have big confusion on pdf.js demo link, why its printing alternate page blank in safari.  But here i am getting page breaking ratio is based on header pageurl/page number. Please find below pdf screen shot. Most of my customer are using safari browser only.... :(

Closing as duplicate of #6248.

@timvandermeij
I am not getting proper solution from your side., But you simply closed like dupicate of #6248. I am Getting stuck on this from past 4 month . #6248 issue something different from my issue., Please compare two screen shots.
And also, there is no solution available for #6248  issue, That is opened from last 5 months. Is PDF.js not supported for Safari browser??
below pdf.js demo link also not supported  in safari print..,
https://mozilla.github.io/pdf.js/web/viewer.html

You had added a comment on that issue saying that the problem described there was the same as this one. There are already multiple issues open regarding page breaks and font issues for printing for all browsers, so if there is nothing new here we can work with those.


Missing support for List of EmbeddedJsonModel

We miss the support of defining a JsonModel with a field that is defined as a List of EmbeddedJsonModel .
It is highly required to support our DB modeling to enable RedisSearch with a single index on a JsonModel and all its EmbeddedJsonModel fields, whether they are a single field or a List.

@oren-twigo Can you give me a base example of how you're looking to use it. Is the idea that this would be extensible (i.e a List contains a List, contains a List...), are you looking for a single level of depth?
I'd actually love to see the combination of your model and Search query if you're willing! For my own curiosity, I'd like to know if you're using async or sync - but it's less important.
Thanks again!

@chayim I am looking for two levels of depth, but it is a fixed and strict depth, not dynamic depth.
find below my code example.
We collect data about users from external platforms.
so the main model is "ExternalUsersData".
each user contains data from one or more platforms.
so we have a list of "UserPlatformData".
each user platform data can contain data of one or more social media platforms this user is linked to - "SocialMediaProfile".
so we have 3 levels of depth:
ExternalUsersData -> (1:N) -> UserPlatformData -> (1:N) -> SocialMediaProfile
I did not get to the point of doing the search queries, so neither "async" or "sync" (yet)  :)
I hope it helps.
`class SocialMediaProfile(BaseEmbeddedJsonModel):
social_media_name: SocialMediaNameField = Field(index=True)
profile_id: str = Field(min_length=1,max_length=100,index=True)
class UserPlatformData(MyBaseModel):  #  <- Should be BaseEmbeddedJsonModel when Python OM will support list of EmbeddedJsonModel
platform_id: int = PlatformField(index=True)
external_platform_user_id: str = Field(min_length=1,max_length=100,index=True)
user_name: str = EnglishOnlyTextField(index=True, full_text_search=True)
display_name: str = UnicodeTextField(min_length=1, max_length=250, index=True, full_text_search=True)
description: str = UnicodeTextField(min_length=0, max_length=500, index=True, full_text_search=True)
location: Optional[Location]
social_media_profiles: List[SocialMediaProfile]
profile_media_file: MediaFile
cover_media_file: MediaFile
email: Optional[EmailStr] = Field(index=True)
phone_number: Optional[str] = PhoneNumberField(index=True)
website_url: Optional[AnyHttpUrl] = Field(index=True)
joined_platform_date_utc: date
created_timestamp_utc: datetime
updated_timestamp_utc: datetime
class ExternalUsersData(BaseJsonModel):
class Meta:
model_key_prefix = "external-users-data"
index_name = "external-users-data.index"
@property
def external_user_uuid(self):
    return self.pk

external_user_platform_data: List[UserPlatformData]
created_timestamp_utc: datetime
updated_timestamp_utc: datetime

`

@simonprickett I believe this has been added?

@simonprickett I believe this has been added?

Not at multiple depth levels IIRC.


Using third party libraries with Mediapipe

Hello, I apologize if this question is more related to Bazel than Mediapipe, but is there a proper way to include third party libraries with Mediapipe? I have the third party library stored as a folder within the same folder that I run the build command and was wondering if there was a simpler way to include this library rather than creating a BUILD file for each subfolder within the library. This library further depends on other libraries which contain many files and creating multiple BUILD files for these dependencies seems inefficient.
I should mention that I was able to build static library files(.a) for the third party library. I was considering an approach similar to how OpenCV is included (including a build file within the third_party folder that references the shared library files and references the header files), but I am unsure if this will work.
Thank you!

If you already have the static libraries, you can follow the OpenCV solution that we have in the workspace file. In theory, it should work. However, to use your libraries in MediaPipe with Bazel, you still need to write a BUILD file for your libraries. Hope this helps.

@jiuqiant
Mediapipe is very useful.
How can I add in third party library like https://github.com/felHR85/UsbSerial to mediapipe?
For normal Android Studio project, I just need to add in
allprojects {
repositories {
jcenter()
maven { url "https://jitpack.io" }
}
}
to build.gradle.
And add the dependency to module's build.gradle:
implementation 'com.github.felHR85:UsbSerial:6.1.0'
But for mediapipe, how can I add in to interface usbserial?


How to verify app-thinning actually works?

We enabled app-thinning in the Fastfile.
gym(
     workspace: "MyApp.xcworkspace",
     scheme: "MainApp",
     export_options: {
        method: "app-store",
        thinning: “<thin-for-all-variants>”
     }
   )

Result: App went from 45.2MB compressed size to 87.9MB compressed size according to Testflight. Also the device specific sizes in Testflight shows increase from 87.8MB install size to 149MB install size for iPhone 5c.
So is Testflight wrong or did those options make our app crazy big?
The app thinning size report said it could reduce our app to 53MB uncompressed and 25MB compressed. Is there any chance of verifying this is the case without submitting the app to the AppStore?

As far as I know, gym is just a pass-through on this app thinning topic. It just forward export_options to the xcodebuild -exportOptionsPlist file. Your configuration seems to fit what's required by xcodebuild -help:

thinning : String
For non-App Store exports, should Xcode thin the package for one or more device variants? Available options: <none> (Xcode produces a non-thinned universal app), <thin-for-all-variants> (Xcode produces a universal app and all available thinned variants), or a model identifier for a specific device (e.g. "iPhone7,1"). Defaults to <none>.

So, for me this is not a fastlane issue.
I think you can take a look at this doc from Apple (especially the Getting an App Size Report part).

Kind of agree I guess. Think I just have to trust the docs and close my eyes and hope for the best.


Donut: metamask guide added

Description
Added the metamask guide to notion
Related issues

Fixes #7887

Documentation

Added 5 new docs pages, under the "wallets" section in the sidebar.

LGTM - Let's implement @aslawson and merge this 💪


Adding value with existing API information

Looking through the list of filters for notifications, I think there's some definite value that can be added by working enabling that information to be displayed outside of the filters.
For example, if there's a PR that I authored and there's a state change on it (two filters in Reasons), it would be sweet to be able to know that by looking at the notification rather than needing to find it out by selecting the correct filters and interpreting the notifications that are displayed based on those filters.

Sure, this can be looked at. This would require pulling in the full Issue/PR and seeing what data we have available. I also worry about cluttering the initial feed, so would be interesting to see how to does this without getting too messy.
I currently have an idea of being able to double click on the notification which will pull in all the information you mentioned above, and more, including the thread etc.

Closing this as a dupe of #11.


Handle parallax plus scaling more gracefully

When the viewport is scaled and layers have special x/y response values, it's somewhat complicated to handle correctly.
This replaces the previous broken logic with a "correct" approach. Under the new transform, a zoom in on the center of the viewport correctly keeps layers from moving relative to each other. This uniquely constrains the properties under other camera movements.
I also switched the canvas and dom layers to use the _viewportRect helper to establish the necessary transforms.
I believe this fixes #1064

It was actually a bit complicated to get the result, and too length a digression for an in-code comment.  So here's the logic that leads to the correct transform... feel free to ignore this.  :)
The problem to solve: given the camera and layer settings, find the corresponding x/y/w/h for the layer that needs to be displayed in the viewport.
Since the axes are independent, just solve the problem for the x-axis.  First define the variables

The scale is s
The x-response factor is r
The viewport coordinates are x_v and w_v
The resulting top-left coordinates in the layer are x_0 and w_0

Any given point x in the layer can be expressed as x = x_0 + \lambda w_0, and will be displayed at viewport position x_v + \lambda w_v.
Varying \lambda between 0 and 1 restricts us to the visible area.
Define the behaviors in a few simple, special cases:

If s and r are both 1, the solution is trivial: x_0 = x_v and w_0 = w_v.
If s = 1 but r does not, then x_0 = r * x_v, w_0 = w_v.
If r = 1 but s does not, then x_0 = x_v, w_0 = w_v / s.

When both s and r are not equal to 1, then we have some freedom about what the transformation will look like.
Two obvious constraints are:

We should preserve the relation w_0 = w_v / s (otherwise the scale factor loses it's meaning)
When either s or r are set to 1, the previous behavior should emerge

To uniquely determine the transform, we need to pick some additional behavior we wish to preserve.   Consider a layer where r=1.  Imagine zooming in on the center of the viewport -- altering the s and vx such that  the point corresponding to the center of the viewport remains at the center of the viewport as we zoom.  It turns out that if we  demand the same behavior for any value of r, it uniquely determines the transformation.
First, what change in vx actually corresponds to such a transformation?  If the middle of the viewport should be fixed, and r=1, then that corresponds to saying that (using 1 and 2 for before and after)
x_1 = x_v1 + 0.5 w_v = x_2 = x_v2 + 0.5 w_v/s.
This then gives us:
x_v1 = x_v2 - 0.5 (1/s - 1) w_v.
Second, what does that tell us about the case when r is not 1?
We get a similar constraint for x_2_0, by comparing the middle of the viewport before and after the very same transformation, and then subbing in the above expression for x_v1 in terms of x_v2.
(x_1 = r * x_v1 + 0.5 w_v) = (x_2 = x_2_0 + 0.5 w_v / s)
  x_2_0 = r * x_v1 + 0.5 w_v - 0.5 w_v / s
        = r * (x_v2 - 0.5(1/s - 1)w_v) + 0.5 w_v - 0.5 w_v / s
        = r * x_v2 + (1 - r) ( 1 - 1/s) w_v

This is the final result; x_0 = r * x_v + (1-r)(1-1/d)w_v.  We can see that when either r = 1 or s = 1 the second term vanishes,  leaving results consistent with those special cases.


Docs cleanup and typo fixes

Closes: #1556
What's Changed

I've gone through the documentation and fixed the following as they were found:

Grammatical errors
Typographical errors
Incorrect or inconsistent markdown formatting

Examples:

Use both * and - for unordered lists in the same document
Not providing alternative text to images
Using HTML attributes for formatting instead of proper Markdown formatting

Cleanup unnecessary/extra whitespacing
etc

In the non-documentation files, I fixed any grammatical or typographical errors as I found them.
There are a few files where I renamed a variable for typographical reasons, but was refactored throughout the file entirely.

@glennmatthews Yeah I can work on those items you mentioned.  I've addressed all specific PR feedback so far.  I'll work on those tasks shortly.

@glennmatthews I specifically did not clean up any of the .md files in docs/release-notes, though there are multiple linting errors in them.
I'm not sure how they are generated.  Do you want these files cleaned up and added to the linter also, or should I ignore them?

@glennmatthews I specifically did not clean up any of the .md files in docs/release-notes, though there are multiple linting errors in them. I'm not sure how they are generated. Do you want these files cleaned up and added to the linter also, or should I ignore them?

They're manually authored at present (though I'd love to see that change in the future) so if you're willing to take them on that would be awesome. I'm also fine with deferring that to a future PR if that's easier for you.

@glennmatthews I specifically did not clean up any of the .md files in docs/release-notes, though there are multiple linting errors in them. I'm not sure how they are generated. Do you want these files cleaned up and added to the linter also, or should I ignore them?

They're manually authored at present (though I'd love to see that change in the future) so if you're willing to take them on that would be awesome. I'm also fine with deferring that to a future PR if that's easier for you.

@glennmatthews I will get the release-notes updated for this PR, but will make the automatic markdown linting and CI pipeline integration in a separate PR.

Release notes are cleaned up.  I think for now, with how they are generated and the nature of the files themselves, disabling the rule MD024 - No Duplicate Headings is acceptable for the files in this folder.


Optional delay when showing spinner

Bug, feature request, or proposal:
Feature Request
What is the expected behavior?
I would be amazing if the spinner would have some delayed show capability. In most cases this would be outside the scope of the control but given its ubiquitous use it might make sense to incorporate directly. E.g. when visibility changes the spinner should show after X ms
What is the current behavior?
Spinner is shown immediately.
What are the steps to reproduce?
n/a
What is the use-case or motivation for changing an existing behavior?
The reason for this is better UI. We don't want to show a spinner when the loading time is less than ~250ms - it only distracts.
Which versions of Angular, Material, OS, browsers are affected?
Is there anything else we should know?
We have 75 degrees in Santa Monica today, which totally beats San Francisco...

This isn't a responsibility that really belongs in the component; the app can be responsible for showing the spinner at the appropriate time.


[release-0.17] Patch CAPI to include rate limit arguments

Issue #, if available:
https://github.com/aws/eks-anywhere-build-tooling/issues/2463
Description of changes:
This change was released into CAPI 1.5.1. Backporting change to our version of CAPI. This patch should be removed when updating to 1.5.1.
Change exposes arguments to increase qps and burst. They set the defaults that were before this change.
/approve
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Partial Fix for Windows Build

Fixes a couple of issues with the Windows build. There are other issues beyond these fixes that are still breaking the build.

Under Windows the recursive deletion of directories containing bundles throws an IOException during the test tearDown phase causing tests to fail. Tests now use an new static method FileUtil.deleteDirectory() that deletes the directory and logs, rather than throws, any IOException.
maven-compiler-plugin was using the incorrect syntax for configuring compiling of groovy souce code. This wasn't breaking the build, but was a simple fix.
Add a @DisableOnWindows annotation for TestNG that will ignore test methods with this annotation. The annotation requires a reason be given to explain why. This reason is included in log output indicating that the test is disabled.
Disable tests in BashCommandsIntegrationTest that require features not typically available in a normal Windows environment: i.e. an SSH server on localhost, the bash command line, the whoami command.

@tbouron / @richardcloudsoft: Could you review this? Would tag Juan, but don't know his GitHub account.


exceptions: evaluate needed exceptions in upstream

This is largely a more speculative issue. According to analysis of sections within compilation units, most source files end up having a not insignificant size proportion in exception tables. @Reflejo recommended analyzing cases where exceptions might lead to irrecoverable conditions.
Size Win
per https://github.com/lyft/envoy-mobile/issues/17#issuecomment-504290445

On the stripped binary there is also at least 1MB of exception tables. I don't know how many of them are exceptions we recover from vs we terminate. So we might investigate adding the nothrow specifier on methods so the except table is not created (not sure how we'll do this in an elegant way only for mobile, nor how we use exceptions, just throwing this here as a thought)

FWIW I would just skip tracking/looking into this. Every exception we throw today needs to be caught somewhere and I don't think we are going to reasonably be able to do anything major here. I think our time is better spent elsewhere.

Sounds like a dead end then. So if that's the case I'm ok not tracking/working on it

coming back to this it's still a pretty big gain to build without exceptions.  From cce99bf8b0
-rwxr-x--- 1 alyssar primarygroup 18953104 Mar 14 09:40 bazel-bin/test/performance/test_binary_size_stripped
-rwxr-x--- 1 alyssar primarygroup 19M Mar 14 09:40 bazel-bin/test/performance/test_binary_size_stripped
-rwxr-x--- 1 alyssar primarygroup 17513048 Mar 14 09:37 bazel-bin/test/performance/test_binary_size_stripped
-rwxr-x--- 1 alyssar primarygroup 17M Mar 14 09:37 bazel-bin/test/performance/test_binary_size_stripped

In my working PR I largely replace throw with throwEnvoyExceptionOrPanic which would be defined to PANIC for E-M
on start-up we already catch all exceptions and replace with panic.  sans-XDS, any other exceptions would be on the data plane which is disallowed and theoretically doesn't happen.
The big gotcha here, is that jbeder_yaml_cpp also has exceptions which means loadFromYaml and friends don't work.  Google was already hoping to move away from yaml for E-M since udp doens't support yaml loading, so I'd say that's a prereq for this reduction.

running PR here:  https://github.com/envoyproxy/envoy/compare/main...alyssawilk:envoy:size_exceptions?expand=1
down to ~90 files


Replication suspended

In my server logs I can the message "Outgoing replication to the client is suspended because there are 30 unacked transactions" constantly. Also changes stoped syncing across clients. I don't really know how to track the issue down or to give more context right now. Help is appreciated a lot!

Resetting or switching to a new database locally solves it but if a client has unsynced changes they obviously get lost. :/

Hey @andrezimpel . Which versions of the client and the server are you using?
Could you enable debug logging on the client and share the log output from the browser console leading up to the moment when replication gets suspended? Thanks!

👋 we've been working the last month on a rebuild of the Electric server over at a temporary repo https://github.com/electric-sql/electric-next/
You can read more about why we made the decision at https://next.electric-sql.com/about
We're really excited about all the new possibilities the new server brings and we hope you'll check it out soon and give us your feedback.
We're now moving the temporary repo back here. As part of that migration we're closing all the old issues and PRs. We really appreciate you taking the time to investigate and report this issue!


Display the name of the person to which the TODO is assigned

Hi,
Great plugin dude! +1
It will will be great to add another functionality to your plugin. It will great to display the name of the person to which the TODO is assigned.
An example :
#From any source file
TODO(first-developer): Blah Blah Blah

On the the review result page, I should get this :
# TODO (1)
1. source_file:X              [first-developer] Blah Blah Blah

I don't think it will to difficult to do this. I look at your code source and I'm wondering if the part of the code must change to achieve the result :
https://github.com/jonathandelgado/SublimeTodoReview/blob/master/TodoReview.py#L107-L109

Or you I make use of the pattern settings for that?

If you agree with the number [1.] I will make a PR to add this ;)
Thanks a lot

Any reason why assigning tasks would be on inline code and not done through something like github issues?
I more think of this tool as a temporary note finder before committing.
Not saying no, just trying to understand the use-case. I try to keep this project lean, since one more regex match on a 5k file project is another twenty seconds of searching.

Hi,
You're right, Github issues works well for that :). My bad!
Thanks


Update wanted books

Removing the commented out Heretics, which has been produced now. Also recommend The Sport of the Gods (https://www.gutenberg.org/ebooks/17854) by Dunbar as a possible easy production. I looked at the html and the formatting looks very straightforward at first glance. The book is about 41k words by my count, so a little on the short side but perfect for a first production.

Thanks!


http works https does not.

This correctly works:
./ttyd -p 8129 top
This does not. On the webpage it displays "400".
./ttyd --ssl --ssl-cert /etc/letsencrypt/live/zibri.org/cert.pem --ssl-key /etc/letsencrypt/live/zibri.org/privkey.pem -p 8129 top
log follows:

[2019/04/12 14:29:08:0909] NOTICE: ttyd 1.4.2-7ed537a (libwebsockets 3.1.99)
[2019/04/12 14:29:08:0911] NOTICE: tty configuration:
[2019/04/12 14:29:08:0912] NOTICE:   start command: top
[2019/04/12 14:29:08:0913] NOTICE:   close signal: SIGHUP (1)
[2019/04/12 14:29:08:0913] NOTICE:   terminal type: xterm-256color
[2019/04/12 14:29:08:0914] NOTICE:   reconnect timeout: 10s
[2019/04/12 14:29:08:0936] NOTICE:  SSL ciphers: 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4:!HMAC_SHA1:!SHA1:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES128-SHA256:!AES128-GCM-SH...
[2019/04/12 14:29:08:0937] NOTICE:  Using SSL mode
[2019/04/12 14:29:08:0941] ERR: lws_tls_server_vhost_backend_init: SSL_CTX_load_verify_locations unhappy
[2019/04/12 14:29:08:0946] NOTICE:  SSL ECDH curve 'prime256v1'
[2019/04/12 14:29:08:0948] NOTICE: created client ssl context for default
[2019/04/12 14:29:08:0950] NOTICE:    vhost default: cert expiry: 88d

I just did a git clone then compiled libwesockets from it's repository.
The released binary works... something goes wrong (incompatible libraries?) when compiling on ubuntu server 18.04.2.

ERR: lws_tls_server_vhost_backend_init: SSL_CTX_load_verify_locations unhappy

This can be safely ignored, did you try the https url with a browser?

Same issue here, tried with the latest libwebsockets master as well. Just displays "400" (I suppose it's a HTTP 400?).

@escalade ttyd will return a 400 code if the http request method is not GET.

I'm simply entering the address in a browser, which I assume will result in a GET request. Seeing as there is two reports about it here I think there might be an issue. It works fine without SSL enabled.

libwebsockets may enable http2 on the server side when ssl is on, but ttyd did not support it well.
Fixed on master.


Expose the incoming Request object as context.req

For example, enables custom hooks to know things about the triggering request:
keystone.createList('User', {
  fields: { ... },
  mutations: [{
    schema: 'startPasswordRecovery(email: String!): ForgottenPasswordToken',
    resolver: async (obj, args, context, info, { query }) => {
      // Can now access context.req.ip to log this request
    }
  }]
});

Am going to force-merge this PR as the failing test is unrelated (and an ongoing issue with all PRs).


Working Gossip Prototype

Monitors can Broadcast + Acknowledge Messages to other monitors

just double checked everything, lmk if you have any thoughts!


The tag parameter isn't honored when passing JSON configuration in stream creation

I noticed the --tag parameter isn't honored when passing a JSON config.  Other parameters like --subjects will overrides the config. I have servers tagged as region1, region2, or region3.
 $ cat test.json
{ "name":"test", "subjects":["bar"], "retention":"limits", "max_consumers":-1, "max_msgs":1000000, "max_bytes":-1, "max_age":0, "max_msg_size":-1, "storage":"file", "discard":"old", "num_replicas": 3 }

 $ nats s create mystream --tag=region2 --config=test.json --user a_user --password password --subjects=foo.d
Stream mystream was created

Information for Stream mystream created 2022-11-04 17:47:20

             Subjects: foo.d
             Replicas: 3
              Storage: File

Options:

            Retention: Limits
     Acknowledgements: true
       Discard Policy: OldOld
     Duplicate Window: 2m0s
    Allows Msg Delete: true
         Allows Purge: true
       Allows Rollups: false

Limits:

     Maximum Messages: 1,000,000
  Maximum Per Subject: unlimited
        Maximum Bytes: unlimited
          Maximum Age: unlimited
 Maximum Message Size: unlimited
    Maximum Consumers: unlimited

Cluster Information:

                 Name: region1
               Leader: r1_a
              Replica: r1_b, current, seen 0.00s ago
              Replica: r1_c, current, seen 0.00s ago

State:

             Messages: 0
                Bytes: 0 B
             FirstSeq: 0
              LastSeq: 0
     Active Consumers: 0

This succeeds:
$ nats s create mystream2 --tag=region2 --user a_user --password password
? Subjects lskdfj
? Storage file
? Replication 3
? Retention Policy Limits
? Discard Policy Old
? Stream Messages Limit -1
? Per Subject Messages Limit -1
? Total Stream Size -1
? Message TTL -1
? Max Message Size -1
? Duplicate tracking time window 2m0s
? Allow message Roll-ups No
? Allow message deletion Yes
? Allow purging subjects or the entire stream Yes
Stream mystream2 was created

Information for Stream mystream2 created 2022-11-04 17:48:23

             Subjects: lskdfj
             Replicas: 3
              Storage: File
       Placement Tags: region2

Options:

            Retention: Limits
     Acknowledgements: true
       Discard Policy: OldOld
     Duplicate Window: 2m0s
    Allows Msg Delete: true
         Allows Purge: true
       Allows Rollups: false

Limits:

     Maximum Messages: unlimited
  Maximum Per Subject: unlimited
        Maximum Bytes: unlimited
          Maximum Age: unlimited
 Maximum Message Size: unlimited
    Maximum Consumers: unlimited

Cluster Information:

                 Name: region2
               Leader: r2_c
              Replica: r2_a, current, seen 0.00s ago
              Replica: r2_b, current, seen 0.00s ago

State:

             Messages: 0
                Bytes: 0 B
             FirstSeq: 0
              LastSeq: 0
     Active Consumers: 0
$

https://github.com/nats-io/natscli/pull/643 allows tags, cluster, description and replicas to be set.  Not perfect probably need to redo how config is obtained entirely to make it more flexible.


Update 0.18.md

objectN becomes mapN isn't quite true as there is no map1. object1 becomes map

Duplicate of https://github.com/elm-lang/elm-platform/pull/183, right?

@jvoigtlaender. Correct. Sorry about that :)


Manifest file

I think it would be useful, when running impact, to keep track of "state" information in a file.  I think this should be separate from the impact.json file.  I see impact.json as something that library developers include in a repository to act as a "roadmap" to the contents of the repository.
What I'm talking about is really like a "project" file that provides information about their current project.  It is different from the impact.json file because that is stored with libraries.  This project file is higher level than that.
Here are examples of things that I think should be stored in this "project" file:

Names (and potentially version numbers) of libraries that the project depends on.
Disambiguation of library names (e.g., Noise means the Noise library at https://github.com/DLR-SR/Noise, not the one at https://github.com/modelica-3rdparty/Noise).
Libraries to be checkout from version control systems (i.e., libraries whose active development is part of the current "project").  I think this is aligned with @casella's goals.

The idea here would be that this "project" file could be version controlled and whenever somebody wants to work on the project, they check out the "project" file and any other version controlled resources and then just run impact install in that directory and it should be able to put everything in place to being working on the project.
Comments?

Assuming people don't have objections, then we need to come up with a name as well.  I propose impact.proj.  I'm inclined to make it Denada format just like the impactrc file.
It is worth pointing out that disambiguation information is currently stored in impactrc.  Moving it to projects makes much more sense since these are settings that people might want to control on a project level.

I think impact.proj is fine. Also I like the whole idea of the project file as this makes impact very similar to a dockerized approach. I.e., being able to configure a development setup with all dependencies in a single human readable configuration file. Impact then will do the hard lifting of pulling together all the resources needed.


NO SUPPORT FOR SCHEDULES

I think this only works when app is open and that's why schedule features is not working. Please look into it.

Also a request, can you make same kind of module for One sync? it would be wonderful.

I think that they should work, but haven't used them, maybe your android version is killing Swift Backup for "battery optimizations"?
Also for OneSync - I don't use OneDrive, I don't trust my data with microsoft's OneDrive, so it won't happen.

but won't this app run in background uselessly ?

How else would schedules work if the app isn't running?


Support for Symfony3

There is a bug, which breaks the support for Symfony3: The service jgm.table_factory depends on the @request, which is not available in Symfony3. Use @request_stack to fix it.

Further adjust the composer.json, add "symfony/symfony": ">=2.5" instead of "symfony/symfony": "~2.5".


Huge Blush Gibbon

Hotspot Name
Huge Blush Gibbon
Hotspot b58 Address
11RzgSbsqjHGWJD83ZNygxDVh2UrPC5TpphXffzd88KqwqPFXks
Discord Handle
No response
Hotspot Manufacturer
panther
Removal Reason
This is a very painful thing. Hey, friends and family have been discussing this matter and how to do it Now it has to be redeployed, even so. Then I will share this hot spot with my friends. You can check and verify this through your technical test methods. Please remove it from the deny list for me, thank you.
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
No response

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


SDA-4489 (Use init for auto updater component)

Description

Use init for auto updater component

Closing this to create a fresh PR with other commits


How do I customize my language in options ?

The only choice in the language is ‘cn, ru’, how do I add a custom language like this:

The gantt will have more white space at the bottom and popup cannot be closed by clicking in the space:

I hope to add the feature of fixing the text on the left:

#117


Remove GPR TLS API

Use c++11 thread_local everywhere. Use proper types everywhere.
An alternative to #26942.
@veblush

I believe it's not ready to replace all TLS variants with c++11 thread_local yet. (ref: #24572)

Yep, see discussion in https://github.com/grpc/grpc/pull/26942#issuecomment-896056588.
Is there test coverage for that simulator version? It seems that #26912 introduced "naked" thread_local usage but still passed tests.

I believe there is but not sure CI tests for the PR cover it. (There are more tests running on master branch only)

Where can I see the results of those tests?

Oh, I didn't realize #26912 hasn't landed yet.

#26912 isn't landed... would like to sort this out beforehand :)

Indeed, no dice.
Tue Aug 10 10:29:55 PDT 2021 - /Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/src/core/lib/iomgr/exec_ctx.h:249:10: error: thread-local storage is not supported for the current target
Tue Aug 10 10:29:55 PDT 2021 -   static thread_local ExecCtx* exec_ctx_;
Tue Aug 10 10:29:55 PDT 2021 -          ^
Tue Aug 10 10:29:55 PDT 2021 - /Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/src/core/lib/iomgr/exec_ctx.h:370:10: error: thread-local storage is not supported for the current target
Tue Aug 10 10:29:55 PDT 2021 -   static thread_local ApplicationCallbackExecCtx* callback_exec_ctx_;


MyFirstBlazzorApp

URL
https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-cli-tutorial/try
Operating system
windows
More information about your system
No response
Description
MyFirstBlazzorApp
dotnet --info
MyFirstBlazzorApp

Can you describe the issue you're having with the tutorial?


Can we redefined the color and icon, based on some properties.

Can we redefined the color and icon, based on some properties.
See configuration object. If the visualization ask everything to the configuration, then it is
easy to redefine all these.

Done


fix: --save-dev for semantic-release

[x ] Commit history is tidy & follows Contributing guidelines ℹ

What this does
adds --save-dev to semantic-release install to avoid getting scanned for issues

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow overriding exception text

Inheriting from ClickException has a small problem: It always appends Error:  to the front of the exception text.
https://github.com/pallets/click/blob/9da166957f5848b641231d485467f6140bca2bc0/src/click/exceptions.py#L43
Overriding that would be useful if you are trying to maintain a consistent style and/or color scheme with log messages and warnings/errors

Could easily make a somewhat backwards-compatible update to allow overriding the prepended string via the following:
    def format_message(self) -> str:
        return f"Error: {self.message}"

    ...

    def show(self, file: t.Optional[t.IO] = None) -> None:
        if file is None:
            file = get_text_stderr()

        echo(_(self.format_message()), file=file)

we now wrap everything with gettext, which means that could be used to substitute the string.

Can you explain more what this means?

Yes, set up translations with gettext and you can substitute whatever you want, for multiple languages even.


rewrite problems

I read your code and find that it's a fantastic work. So I rewrite the code , but the accuracy get around 0.2. I have spent several days with my code , but still  had no idea what is wrong with my code. Will you help me to point out the problems? Thank you! BTW, may I have your email for communicating? My email is<EMAIL_ADDRESS>my code is as follow:
https://github.com/zhaoyu611/LSTM-Human-Activity-Recognition/blob/master/lstm_copy.py

Hi to you, from what I see you renamed and moved many things, from a first reading I can't find the bug.
You might want to see this previous version of my project, where the training time is probably 6 times faster but sacrificing a bit of accuracy:
https://github.com/guillaume-chevalier/LSTM-Human-Activity-Recognition/commit/3bacfe9b5a7e7d2b4dab3fa2f339408eeff3402b
The difference with what I have now is that there were no stacked LSTM cells (only one LSTM "cell" layer was there, not two), and we were looping only 100 times the dataset rather than 300 times. Also, in this previous version, I was using no L2 loss, which may simplify things more. Also, I was using 28 for n_hidden rather than 32 now. Undoing those changes might be useful for debugging.
I'll send you an email in case you want to contact me.

I am testing your code now, from what I see, you changed the batch_size from 1500 to 25. This parameter is really important relatively to other parameters, you may need to change some settings on the optimizer. I remember having read somewhere that batch sizes are very important in RNNs.
As an example, you might want to play with momentum techniques to simulate keeping a trace of past batches for current step during training if you keep a small batch_size. I would be tempted to use an RMSProp optimizer in your case, or to train with CPU to keep the old batch_size.
Yet I tried to change the batch_size in your code and the accuracy does not go up, there might be another problem or critic change somewhere. By the way, I see that you do not use state_is_tuple=True in the LSTM cells compared to what I did. I am not sure of what that does.
About this line in your code:
lstm_cells = tf.nn.rnn_cell.MultiRNNCell([lstm_cell]*2, state_is_tuple=True)
I often see it on the web, but am doubtful whether or not doing *2 would share the weights of the two LSTM cells, which would not be a trivial change. I never verified it, so I prefer to do the following just to be sure the weights aren't shared between the two cells:
lstm_cells = tf.nn.rnn_cell.MultiRNNCell([lstm_cell_1, lstm_cell_2], state_is_tuple=True)
I hope this helps you!

Dear Guillaume ,
I appreciate that you are so warmhearted to help me and point out my
fault.
*1. I corrected *"lsmt_layers" to "lstm_cell" just as you wrote, it was my
mistaken.
2. I made a stacked LSTM as yours, but there was no difference. And I ever
read other code wrote "[LSTM_cells]*2".
3. I changed batch_size as 1500, and kept Adam optimizer, and got all
ohter hyperparameters
as yours ,but nothing better.  :(
4. I read doc about "state_is_tuple=True". It said "True" is default value
in tensorflow version >= 0.10
Thanks anyway, and I am going to restore to your code and figure out which
step get wrong. And I will send you latest news.
BTW, I have another question:
why not change all "y_train" to one hot before run, but change each batch
y_train in loop?
as your code:
while step * batch_size <= training_iters:
batch_xs =         extract_batch_size(X_train, step, batch_size)
batch_ys = one_hot(extract_batch_size(y_train, step, batch_size))
and I get one_hot before batch loop:
train_label_mat = load_Y(train_Y_path)

train_label_mat = one_hot(train_label_mat)  # convert to one-hot
# test_label_mat: ndarray [sample_num,1]=[2947,1],label range 0-5
test_label_mat = load_Y(test_Y_path)
test_label_mat = one_hot(test_label_mat)  # convert to one-hot
On Wed, Nov 23, 2016 at 8:07 PM, Guillaume Chevalier <
<EMAIL_ADDRESS>wrote:

I am testing your code now, from what I see, you changed the batch_size
from 1500 to 25. This parameter is really important relatively to other
parameters, you may need to change some settings on the optimizer. I
remember having read somewhere that batch sizes are very important in RNNs.
As an example, you might want to play with momentum techniques to simulate
keeping a trace of past batches for current step during training if you
keep a small batch_size. I would be tempted to use an RMSProp
https://www.tensorflow.org/versions/r0.11/api_docs/python/train.html#RMSPropOptimizer
optimizer in your case, or to train with CPU to keep the old batch_size.
Yet I tried to change the batch_size in your code and the accuracy does
not go up, there might be another problem or critic change somewhere. By
the way, I see that you do not use state_is_tuple=True in the LSTM cells
compared to what I did. I am not sure of what that does.
About this line in your code:
lstm_cells = tf.nn.rnn_cell.MultiRNNCell([lstm_cell]*2,
state_is_tuple=True)
I often see it on the web, but am doubtful whether or not doing *2 would
share the weights of the two LSTM cells, which would not be a trivial
change. I never verified it, so I prefer to do the following just to be
sure the weights aren't shared between the two cells:
lstm_cells = tf.nn.rnn_cell.MultiRNNCell([lstm_cell_1, lstm_cell_2],
state_is_tuple=True)
I hope this helps you!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/guillaume-chevalier/LSTM-Human-Activity-Recognition/issues/2#issuecomment-262496923,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATdzDRNqSBpUhMlP3e4PDAXgCHgzV7iqks5rBCyUgaJpZM4K6Of0
.

train_label_mat = load_Y(train_Y_path)
train_label_mat = one_hot(train_label_mat)  # convert to one-hot
test_label_mat: ndarray [sample_num,1]=[2947,1],label range 0-5
test_label_mat = load_Y(test_Y_path)
test_label_mat = one_hot(test_label_mat)  # convert to one-hot
in my lstm_copy.py  from line 154 to 158:
https://github.com/zhaoyu611/LSTM-Human-Activity-Recognition/blob/master/lstm_copy.py
On Thu, Nov 24, 2016 at 11:28 AM, Zhao Yu<EMAIL_ADDRESS>wrote:

Dear Guillaume ,
I appreciate that you are so warmhearted to help me and point out my
fault.
*1. I corrected *"lsmt_layers" to "lstm_cell" just as you wrote, it was
my mistaken.
2. I made a stacked LSTM as yours, but there was no difference. And I ever
read other code wrote "[LSTM_cells]*2".
3. I changed batch_size as 1500, and kept Adam optimizer, and got all
ohter hyperparameters as yours ,but nothing better.  :(
4. I read doc about "state_is_tuple=True". It said "True" is default value
in tensorflow version >= 0.10
Thanks anyway, and I am going to restore to your code and figure out which
step get wrong. And I will send you latest news.
BTW, I have another question:
why not change all "y_train" to one hot before run, but change each batch
y_train in loop?
as your code:
while step * batch_size <= training_iters:
batch_xs =         extract_batch_size(X_train, step, batch_size)
batch_ys = one_hot(extract_batch_size(y_train, step, batch_size))
and I get one_hot before batch loop:
train_label_mat = load_Y(train_Y_path)

train_label_mat = one_hot(train_label_mat)  # convert to one-hot
# test_label_mat: ndarray [sample_num,1]=[2947,1],label range 0-5
test_label_mat = load_Y(test_Y_path)
test_label_mat = one_hot(test_label_mat)  # convert to one-hot
On Wed, Nov 23, 2016 at 8:07 PM, Guillaume Chevalier <
<EMAIL_ADDRESS>wrote:

I am testing your code now, from what I see, you changed the batch_size
from 1500 to 25. This parameter is really important relatively to other
parameters, you may need to change some settings on the optimizer. I
remember having read somewhere that batch sizes are very important in RNNs.
As an example, you might want to play with momentum techniques to
simulate keeping a trace of past batches for current step during training
if you keep a small batch_size. I would be tempted to use an RMSProp
https://www.tensorflow.org/versions/r0.11/api_docs/python/train.html#RMSPropOptimizer
optimizer in your case, or to train with CPU to keep the old batch_size.
Yet I tried to change the batch_size in your code and the accuracy does
not go up, there might be another problem or critic change somewhere. By
the way, I see that you do not use state_is_tuple=True in the LSTM cells
compared to what I did. I am not sure of what that does.
About this line in your code:
lstm_cells = tf.nn.rnn_cell.MultiRNNCell([lstm_cell]*2,
state_is_tuple=True)
I often see it on the web, but am doubtful whether or not doing *2 would
share the weights of the two LSTM cells, which would not be a trivial
change. I never verified it, so I prefer to do the following just to be
sure the weights aren't shared between the two cells:
lstm_cells = tf.nn.rnn_cell.MultiRNNCell([lstm_cell_1, lstm_cell_2],
state_is_tuple=True)
I hope this helps you!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/guillaume-chevalier/LSTM-Human-Activity-Recognition/issues/2#issuecomment-262496923,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATdzDRNqSBpUhMlP3e4PDAXgCHgzV7iqks5rBCyUgaJpZM4K6Of0
.

Hi,
Have you published any papers about HAR ? If not ,I think we can cooperate
for it .
On Thu, Nov 24, 2016 at 11:31 AM, Zhao Yu<EMAIL_ADDRESS>wrote:

train_label_mat = load_Y(train_Y_path)
train_label_mat = one_hot(train_label_mat)  # convert to one-hot
test_label_mat: ndarray [sample_num,1]=[2947,1],label range 0-5
test_label_mat = load_Y(test_Y_path)
test_label_mat = one_hot(test_label_mat)  # convert to one-hot
in my lstm_copy.py  from line 154 to 158:
https://github.com/zhaoyu611/LSTM-Human-Activity-
Recognition/blob/master/lstm_copy.py
On Thu, Nov 24, 2016 at 11:28 AM, Zhao Yu<EMAIL_ADDRESS>wrote:

Dear Guillaume ,
I appreciate that you are so warmhearted to help me and point out my
fault.
*1. I corrected *"lsmt_layers" to "lstm_cell" just as you wrote, it was
my mistaken.
2. I made a stacked LSTM as yours, but there was no difference. And I
ever read other code wrote "[LSTM_cells]*2".
3. I changed batch_size as 1500, and kept Adam optimizer, and got all
ohter hyperparameters as yours ,but nothing better.  :(
4. I read doc about "state_is_tuple=True". It said "True" is default
value in tensorflow version >= 0.10
Thanks anyway, and I am going to restore to your code and figure out
which step get wrong. And I will send you latest news.
BTW, I have another question:
why not change all "y_train" to one hot before run, but change each
batch y_train in loop?
as your code:
while step * batch_size <= training_iters:
batch_xs =         extract_batch_size(X_train, step, batch_size)
batch_ys = one_hot(extract_batch_size(y_train, step, batch_size))
and I get one_hot before batch loop:
train_label_mat = load_Y(train_Y_path)

train_label_mat = one_hot(train_label_mat)  # convert to one-hot
# test_label_mat: ndarray [sample_num,1]=[2947,1],label range 0-5
test_label_mat = load_Y(test_Y_path)
test_label_mat = one_hot(test_label_mat)  # convert to one-hot
On Wed, Nov 23, 2016 at 8:07 PM, Guillaume Chevalier <
<EMAIL_ADDRESS>wrote:

I am testing your code now, from what I see, you changed the batch_size
from 1500 to 25. This parameter is really important relatively to other
parameters, you may need to change some settings on the optimizer. I
remember having read somewhere that batch sizes are very important in RNNs.
As an example, you might want to play with momentum techniques to
simulate keeping a trace of past batches for current step during training
if you keep a small batch_size. I would be tempted to use an RMSProp
https://www.tensorflow.org/versions/r0.11/api_docs/python/train.html#RMSPropOptimizer
optimizer in your case, or to train with CPU to keep the old batch_size.
Yet I tried to change the batch_size in your code and the accuracy does
not go up, there might be another problem or critic change somewhere. By
the way, I see that you do not use state_is_tuple=True in the LSTM
cells compared to what I did. I am not sure of what that does.
About this line in your code:
lstm_cells = tf.nn.rnn_cell.MultiRNNCell([lstm_cell]*2,
state_is_tuple=True)
I often see it on the web, but am doubtful whether or not doing *2
would share the weights of the two LSTM cells, which would not be a trivial
change. I never verified it, so I prefer to do the following just to be
sure the weights aren't shared between the two cells:
lstm_cells = tf.nn.rnn_cell.MultiRNNCell([lstm_cell_1, lstm_cell_2],
state_is_tuple=True)
I hope this helps you!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/guillaume-chevalier/LSTM-Human-Activity-Recognition/issues/2#issuecomment-262496923,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATdzDRNqSBpUhMlP3e4PDAXgCHgzV7iqks5rBCyUgaJpZM4K6Of0
.

I checked my code carefully, and found out that I made a silly mistake.
In load_X() function, I use listdir() to get file , but that is not read data by specify.
So I correct my code , and pull a request. Thanks for your greatful help!

Hi,
Nice to see that your bug is fixed! Well seen for the one_hot() function.
I'll take a look at the pull request soon.
I have not done any paper on HAR, I would like to see how we could cooperate. Let's move this conversation to email.
Thanks,
Guillaume


[Question/Suggestion] do missile turrets replace existing normal turrets?

Are missile turrets additional hazards, or do they replace existing normally-spawned turrets?
It would be great (imo) if at random (up to a cap), a specific number of normal turrets were converted to missile turrets. That way the map still controls the difficulty of hazards. Also could work in combination with something like HazardsOutside (a mod which can spawn turrets outside.) Converting just a couple of them (perhaps by recording position/rotation of the original turret, and spawning a missile turret with that same transform) would be super nice.

Missile turrets do not currently replace normal turrets. I don't think that they should because I don't necessarily want to lower the spawns of normal turrets. I do want to work more on the spawning mechanics and this could be an option, but I definitely want to make them more dynamic somehow.
I tested and it does work with HazardsOutside.


Expression prediction tutorial

Description of feature

[X] Get draft tutorial in
[ ] Add functions to pertpy
[ ] adapt tutorial with pertpy functions

Relevant PR: https://github.com/theislab/pertpy/pull/502


nz-submenu incomplete display

Reproduction link
https://stackblitz.com/edit/angular-rxxezh
Steps to reproduce
Move your mouse to the 'there' menu
What is expected?
The first option of the sub-menu is completely displayed
What is actually happening?
Incomplete display of the first option in the sub-menu

Environment
Info

ng-zorro-antd
8.5.2

Browser
Google   Version 80.0.3987.116 (Official Build) (64-bit)

Hi Vthinkxie, could you help me?

when nzMode='horizontal' is displayed vertical，why?

duplicated #4743


fs/vfs/fs_epoll: fix epoll_wait function

Summary
epoll_wait() must loop until "maxevents" to fill output evs array
Impact
Testing

It seems that some of part conflict with the https://github.com/apache/incubator-nuttx/pull/1582

@anchao yes indeed, there is a conflit regarding the modification of sys/epoll.h.
The modification from #1582 looks good so I can rebase on top of your patch.

@spiriou could you rebase your patch?

@xiaoxiang781216 could you take a look here please.

LGTM.


unixPB: Remove devtoolset-7 and require Adopt's GCC7.5

Need to make sure this doesn't break anything before merging, hence WIP
Signed-off-by: Stewart Addison<EMAIL_ADDRESS>

Testing at https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/

https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/374/
Running again, as the branch was put in incorrectly...

The above run showed that CentOS6 and CentOS7 is now trying to install gcc_7 (I believe the intended purpose of this PR). It did fail, as the checksum was incorrect, though this should already be fixed with  https://github.com/AdoptOpenJDK/openjdk-infrastructure/pull/1160


Change Newsroom menu item to News

User on Twitter reports that menu is cut off when viewing on an iPad Mini. Probably needs to be addressed in the Design System, which @xjensen will do. In the meantime, we'll save some pixels by changing the Newsroom menu item to News.

Updated menu at 9AM on 5/6/22.


Bypass no-floating-promises with void operator?

I'm currently using TSLint 4.5.1.
With the no-floating-promises rule, I get Promises must be handled appropriately messages for code like this:
    public activate(): void {
        this.loadSiteSections(); // *** Problem here ***
    }

    private async loadSiteSections(): Promise<void> {
        try {
            const siteSections = await this.serviceSiteSections.getSupportedSiteSections(
                new Query().setFields("id,name")
            );

            this.siteSections = siteSections.data;
        } catch (e) {
            this.handleError(e);
        }
    }

If I await the call, then the activate method will block until the site sections are loaded, but I want to display the view/form while the list is loading.
Would it make sense to turn off this message if you use the void operator, as mentioned here? Like this:
    public activate(): void {
        void this.loadSiteSections(); // Intentional.
    }

I thought that I tested this, but it seems now that this already works! Closing.

This error is so dumb to begin with


Azure throttling requests

When moving a large VM (this VM has 16 disks attached) I get errors from Azure saying that I'm being throttled.
Get-AzureRmStorageAccount : TooManyRequests: The request is being throttled.
At C:\Users\Denny\asm2arm\asm2armStorage.ps1:52 char:32

        $storageAccounts = Get-AzureRmStorageAccount

                           ~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : CloseError: (:) [Get-AzureRmStorageAccount], CloudException
FullyQualifiedErrorId : Microsoft.Azure.Commands.Management.Storage.GetAzureStorageAccountCommand

This is with Azure PowerShell 1.1.0.

Are you seeing this from the portal or from a script your running?  If a script can you post the code?

I'm getting them when doing a migration using the script that are generated.  I don't have any of the scripts handy that it generated that have the issue as that was 9 months ago.


Grab bag

@pweil- @kargakis @mjudeikis sorry this is a grab bag commit.  A few things of interest:

returned openshift pod and service network ranges back to their defaults
changed all the addon Secrets to use stringData rather than data (as long as the contents are valid utf-8)
clean imagePullPolicy by default - at least for now would rather use kubernetes' default logic for this rather than getting it wrong ourselves when we override image names and versions
don't record service IPs (except for the registry, whose IP gets baked into its cert -- can we stop doing that? --); have service IPs in clusters dynamically generated
remove lots of default values from our addons files to make them easier to work with
don't persist the kubernetes service
don't persist autogenerated rolebindings
log when sync.go updates an object - in the future we should be tracking the updates made both when a cluster is created and when sync.go runs twice to ensure that it is idempotent.


revert runc and containerd in kind image

Issue #, if available:
Description of changes:
I tested on an al2 node using a combo of upstream and our custom builds of kind + node image. I think the updated runc appears to be the problem, even tho the 0.20 release of kind added a fix to workaround the misc controller issue.
The main problem comes in when installing cilium.  Creating a bootstrap cluster with kindnetd does not appear to have the same issues. I tested the eksa 1.12 clium as well as the upstream 1.12 and 1.13 cilium, all of which show the issue.  Upstream 1.14 cilium does not have the same problem.
I am not completely convinced there is nothing some other way to work around this, but this seems to the simplest for now.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disk space issue in presubmit.. I'll fix it a follow-up


New package: Microsoft.AzureMonitorAgent version <IP_ADDRESS>

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.
closes #157431

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335226
2024-06-13 16:27:23.624 [CLI ] ShellExecute installer failed: 1603
CustomAction CheckInstallationConditions returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (44:08) [16:27:23:181]: Product: Azure Monitor Agent -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CheckInstallationConditions, entry: CheckInstallationConditions, library: C:\Windows\Installer\MSI6795.tmp
Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CheckInstallationConditions, entry: CheckInstallationConditions, library: C:\Windows\Installer\MSI6795.tmp
Property(S): ErrorDialog = ErrorDlg

Automated error analysis suggests -1978335226 may mean Install successful but system restart may be required.
Automated error analysis suggests 1603 may mean Install successful but system restart may be required. Should this be add as an InstallerSuccessCode` or similar?
(Automated response - build 885.)

Verify:

I had difficulty figuring out which was the EXE to verify.Here's one that shows some sort of version number:

Service runs:

Registry:

The Uninstall using 'C:\WINDOWS\system32\msiexec.exe' with arguments '/x{0e61117d-ebf1-4920-bf23-36be5edd2c70} /passive /norestart' will fail with exit code: 1601 if AzureMonitorAgent service is running.


operator project-quay (3.9.0-nightly.20230505)

Add 3.9.0-nightly.20230505 to community operators

/merge possible

/merge possible


MimicExplainer does not work -- deprecate?

The MimicExplainer class currently defined in shap/explainers/mimic.py has alot of undefined names (flagged out by ruff linting).

which will result in errors if the code is executed at any point during runtime.
What I find surprising is that, the original MimicExplainer code was introduced by slundberg 5 years ago (!) and has practically remained unchanged since then:

And yet, a quick search of issues on slundberg/shap on Github shows no evidence of anyone complaining / raising a bug report.

From which, I conclude that really no one is using this piece of code. Shall we delete mimic.py, so we have less to maintain?
ps. (Honestly, I have no idea how to fix even if we wanted to keep it. E.g. what is link that is being passed into the convert_to_link() function in the image above?)
ps. There is also no tests for MimicExplainer currently.

Some links that may be relevant:

https://github.com/MicrosoftDocs/azure-docs/issues/108498
https://learn.microsoft.com/en-us/azure/machine-learning/how-to-machine-learning-interpretability?view=azureml-api-2

There seems to be some effort going on at Microsoft for supporting SHAP - just no idea why they don't touch the main repository...

Thanks for the links and context, it didn't occur to me to check external links.
I'll add on that the SHAP docs don't include MimicExplainer, and it isn't included in the top-level imports (__all__) which probably explains why it hasn't been brought up by the SHAP users as a problem thus far.
Considering that there's still some buzz around this at Microsoft, I see two options

Deprecate and delete the MimicExplainer code here, and only add it back in when we are ready to make the API public (most likely only when we have upstream support by Microsoft). I don't think we need a deprecation cycle because MimicExplainer isn't even in the public API. And direct future queries about MimicExplainer support in shap to this issue, and we'll discuss from there.
Keep the  MimicExplainer code around. Add a file exclusion of this file for ruff, black and probably any other linters we might add in the future. Because as it stands, the python file is not even executable (undefined names), so any tools that rely on executing the file will necessarily fail.

I'm personally more for 1 (don't keep code that is not being used; else it is just a burden to maintain). Wdyt @dsgibbons @connortann ?

I'm happy with 1. so long as we keep an open issue for implementing MimicExplainer.


Update package.json

Fix not found module jshint during gulp build , jshint needs to be installed with gulp-jshint.

Please do not make PRs to the master branch, PRs are only accepted to the dev branch.
Please read through our Contributing Guide which details how to make good PRs and Issues.
Additionally this was already fixed in dev: #2449

Thank you. I appreciate your advice on this matter.


Add docs for how type inference/solving/ability specialization works

I find myself reading through a lot of PRs I submitted months ago to re-contextualize. Let's add two types of documentation:

High-level documentation on the strategies we use today

How open/closed tag unions get solved
How we do open by default unions
Recursive tag unions
Recursive lambda sets
lambda set specialization (https://github.com/roc-lang/roc/blob/main/crates/compiler/solve/docs/ambient_lambda_set_specialization.md)
handling polymorphic-optional records
avoiding admission of polymorphic recursion
solving opaque type arguments

More doc comments

I'll do this in https://github.com/roc-lang/roc/pulls


[BUG] Arrays of geo_shape are broken after v2.8.0

Describe the bug
While investigating whether a product I work on could migrate from ElasticSearch to OpenSearch, I found that OpenSearch support for ingesting arrays of geo_shape objects is broken after v2.8.0.
Specifically, the error message I get back during ingest is:
{
  "error" : {
    "type" : "illegal_argument_exception",
    "reason" : "DocValuesField \"location\" appears more than once in this document (only one value is allowed per field)"
  }
}

I created a YAML test and used git bisect between v2.8.0 and v2.9.0 commits to track the issue to commit ebe6f2c2878f036cb4c1147683c30091747d7632, introduced in PRs #4266 and #8301.
Related component
Other
To Reproduce

[!NOTE]
I've opened PR #14196 using a branch containing the YAML test file that demonstrates this issue. An OpenSearch maintainer can pull the changes, add fix commits, and push back to the associated PR.

I'm running the test suite using the following command with an additional YAML file that demonstrates the problem.
./gradlew :modules:geo:yamlRestTest

YAML file location:
modules/geo/src/yamlRestTest/resources/rest-api-spec/test/geo_shape/300_array_of_geo_shapes.yml

YAML file contents (with comments added only here):
Details

setup:
  - do:
      indices.create:
        index: test
        body:
          settings:
            number_of_replicas: 0
          mappings:
            properties:
              location:
                type: "geo_shape"

---
# This works across all git commits in 2.8.0..2.9.0
"Single shape":
  - do:
      bulk:
        refresh: true
        body:
          - index:
              _index: test
              _id: 1
          - location:
              type: "polygon"
              coordinates: [
                [
                  [ -87.0, 41.0 ],
                  [ -88.0, 41.0 ],
                  [ -88.0, 42.0 ],
                  [ -87.0, 42.0 ],
                  [ -87.0, 41.0 ],
                ]
              ]

  - match: {errors: false}

---
# This fails starting at commit ebe6f2c2878f036cb4c1147683c30091747d7632
"Array of shapes":
  - do:
      bulk:
        refresh: true
        body:
          - index:
              _index: test
              _id: 1
          - location:
              - type: "polygon"
                coordinates: [
                  [
                    [ -87.0, 41.0 ],
                    [ -88.0, 41.0 ],
                    [ -88.0, 42.0 ],
                    [ -87.0, 42.0 ],
                    [ -87.0, 41.0 ],
                  ]
                ]
              - type: "polygon"
                coordinates: [
                  [
                    [ -97.0, 41.0 ],
                    [ -98.0, 41.0 ],
                    [ -98.0, 42.0 ],
                    [ -97.0, 42.0 ],
                    [ -97.0, 41.0 ],
                  ]
                ]

  - match: {errors: false}

Expected behavior
I expected that I could creating a "location" field with a geo_shape mapping and then ingest an array of geo_shape objects. The product I work on uses ElasticSearch 7.10 and arrays of geo_shape objects can be ingested, and this also is how arrays are documented to work:

There is no dedicated array field type in OpenSearch. Instead, you can pass an array of values into any field.

Additional Details
None. I'm just running the test suite with an additional YAML file.

Thank you for a very detailed report, a YAML REST test, and a bisect, this is super helpful @kurtmckee.  Unfortunately I won't be able to dive in to fix this (I lack experience with Java). I'm grateful you double-checked, though, to avoid possible duplication of effort!

[Triage - attendees 1 2 3 4]
Thanks for filing. Looks like a clear bug. @kurtmckee thanks for the investigation and detail provided!

@navneet1v Could you take a look?

@kurtmckee on which version of Opensearch you are facing the issue? Can you switch to 2.11/2.13 version of Opensearch?

@navneet1v

which version of Opensearch you are facing the issue

This bug is present in all versions of OpenSearch after v2.8.0. I opened a PR, #14196, based off main, that demonstrates this issue.
The Jenkins run for that PR shows that STDOUT contains the error I described in this bug report.
I backtracked through the Docker images provided by OpenSearch in our test suite until I found that 2.8.0 worked; I then cloned the OpenSearch repo, created the YAML test case, and used git bisect to find the commit that introduced the regression.

@navneet1v

which version of Opensearch you are facing the issue

This bug is present in all versions of OpenSearch after v2.8.0. I opened a PR, #14196, based off main, that demonstrates this issue.
The Jenkins run for that PR shows that STDOUT contains the error I described in this bug report.
I backtracked through the Docker images provided by OpenSearch in our test suite until I found that 2.8.0 worked; I then cloned the OpenSearch repo, created the YAML test case, and used git bisect to find the commit that introduced the regression.

Can you try one thing, for the geo_shapes field can you try disabling the doc_value using "doc_values": false in mappings.
I will go ahead and look into what part of code is creating the issue, because I do know that we can index more than 1 geo_shape in 1 field.

@navneet1v Thanks for that suggestion. It appears that if doc_values: false is set in the mapping then arrays of geo_shape can be ingested.
I've added an additional commit that also tests doc_values: false to PR #14196 to both demonstrate that this avoids the problem, and to ensure that the test suite guards against future regressions. You should have permissions to push commits to that PR branch.
# Using the GitHub CLI
gh co 14196

# Using git
git remote add kurtmckee git@github.com:kurtmckee/pr-OpenSearch.git
git fetch kurtmckee
git checkout -b fix-arrays-of-geo_shape-issue-14193 kurtmckee/fix-arrays-of-geo_shape-issue-14193


bosh-bootstrap 0.11.4 results in error

just upgraded to 0.11.4 and get the error below
i also tried to clean all gems and reinstall again but same problem occurs
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- bundler (LoadError)
	from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
	from /var/lib/gems/1.9.1/gems/bosh-bootstrap-0.11.4/bin/bosh-bootstrap:5:in `<top (required)>'
	from /usr/local/bin/bosh-bootstrap:23:in `load'
	from /usr/local/bin/bosh-bootstrap:23:in `<main>'

I am having the same problem again. Can you provide some help?

Fixed it with sudo gem install bundler

Perhaps we need to install bundler as part of the gem install. Lots of people already have it so I forgot some don't.
On Fri, Sep 11, 2015 at 9:58 AM, lanzalibre<EMAIL_ADDRESS>wrote:

Fixed it with sudo gem install bundler
Reply to this email directly or view it on GitHub:
https://github.com/cloudfoundry-community/bosh-bootstrap/issues/207#issuecomment-139600105

Maybe I am too much of a newbie, but I wonder if you could help me with the fourth step. It says it does not recognize "cf" as a command. This image shows the current status of my installation.

I think you're now trying to use the old bosh-cloudfoundry project. It's unmaintained and looks like it no longer works - I'm sorry.
Now look to the CF & bosh.io docs to learn more about deploying CF

I had never worked with bosh or cf before this. All I did was install bosh
as per the instructions (same as in bosh.io):
gem install bosh_cli
By the way, my version of bosh says
bosh -v
BOSH 1.3069.0
2015-09-12 8:11 GMT+02:00 Dr Nic Williams<EMAIL_ADDRESS>
I think you're now trying to use the old bosh-cloudfoundry project. It's
unmaintained and looks like it no longer works - I'm sorry.
Now look to the CF & bosh.io docs to learn more about deploying CF
—
Reply to this email directly or view it on GitHub
https://github.com/cloudfoundry-community/bosh-bootstrap/issues/207#issuecomment-139727175
.

Attempting to run :
./scripts/generate-bosh-lite-dev-manifest
I was getting the following:
"_**vagrant@bosh-lite:~/workspace/cf-release$ ./scripts/generate-bosh-lite-dev-manifest
/usr/local/lib/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler/setup (LoadError)
    from /usr/local/lib/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'

/usr/local/lib/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler/setup (LoadError)
    from /usr/local/lib/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'

Can only target Bosh Lite Director. Please use 'bosh target' before running this script.**_"
Running:
sudo apt-get install bundler ruby-bundler
resolved this for me.
I've seen posts in the past, where this might have been resolved, however this post is of course 03/18/2016
My occurrence was on a new / clean pc, following the CF instructions.
Downloaded the latest of everything that was suggested. Using vagrant 1.8, cf project / stem cell 232, etc on a new pc.