Fix apps test

Tekton has failed to run the apps task.
invalid input params for task apps: missing values for these params which have no default values: [kubeconfig-path]

https://tekton.giantswarm.io/#/namespaces/test-workloads/pipelineruns/339ae76e-a121-11eb-b460-0ada3b9a0011?pipelineTask=create-release&step=chown-releases
And sonobuoy test as well.
time="2021-04-19T16:17:25Z" level=error msg="error attempting to run sonobuoy: failed to get namespace sonobuoy: namespaces \"sonobuoy\" not found"

@giantswarm/team-ludacris Anyone can review this? Thanks

Tested already in gorilla last night :)


Labels are not automatically added for new bug & enhancement issues

@michaelstaib I think it's an issue, that the tag used for bugs in this repo, does not include the actual emoji, but rather :beetle:.

vs.

I was wondering, since a bug report of mine was not correctly labeled, even after the attached PR had been merged. I validated the behavior before in a private repo, so I think this is the issue.
The fix would be that a maintainer edits the bug label to include the actual emoji: 🐞 bug.
I could also submit another PR, but that would be too much noise around a thing that could be changed within the repo, without consequence.

done

Thanks, but now it's :bug: instead of the actual emoji :D

From one of your presentations I know that you're using MacOS, so maybe it's a weird Safari/MacOS quirk.
I'm on Linux + Firefox and I can paste the actual emoji from my comment above into a label in a private repository of mine...

Ok... misunderstood you :) now it is the bug emoji and I used the proper utf8 character.

is:open label:"🐛 bug"


Solicit external feedback

https://www.reddit.com/r/haskell and/or #haskell on fp slack, lambdaconf, etc.

Posted to reddit, FP slack coming soon.

Actually reddit is good enough for now.


freeRTOS on SweRB

All,
Because the current test bench is too simple for me to learn the sweRV, thus I use FreeRTOS as the target to learn how to control this great design. With small modification of original test bench, the simple demo from FreeRTOS can be tested using RTL simulation.
It's a good start for me and hope it can also help others to get more familiar with sweRV.
github path:
https://github.com/ycyang0508/FreeRTOS_on_SweRV
Ya-Chau

Ya-Chau - great job. You should probably keep looking into Chipsalliance.org, to see notifications about working groups. There will be a group on RISC-V cores, and also workgroup on tools, creating more opportunities for collaboration and work.
I am closing this Issue - as there is no issue, but just wanted to let you know it is very interesting.


[Bug]: longer instructions

What happened?
If you write the instruction with the complete word (for example, mul will be multiply), it doesn't detect a syntax error and write it as instruction and function name
Operating System
Windows
If other was selected
No response
Relevant log output
==========================================================
Instruction: subtract
Name: act
Parameter 1: rd
Parameter 2: 1
Line: 8
==========================================================

priority
Should be done quickly

Fixed


Error of access level while saving default.json after trying to change color scheme

Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

This appears at the top of defaults.json:
// THIS IS AN AUTO-GENERATED FILE! Changes to this file will be ignored.

defaults.json is not intended to be edited. You can set "default" settings in your own settings.json file by putting them in the "defaults" section.


README is very out of date

We should wipe the README of this repo clean and have it focus more directly on rmf_traffic instead of being about RMF broadly.
We should also update the README of https://github.com/osrf/rmf_core to redirect users towards https://github.com/open-rmf/rmf

Updating the old repository READMEs is on my list as soon as we finish the final repository's migration.
I'm probably not the right person to write a README for rmf_traffic, though. I will say that I think the content of the README should be the same as the front page of the package's documentation at open-rmf.readthedocs.io.

Would it be feasible/desirable for the front page readthedocs documentation for this package to simply display the README contents?

I believe that it is possible, because the README location is fixed relative to the documentation source location.


"maxVersion" is not respected by "winget configure"

Brief description of your issue
The winget configured command does not respect the maxVersion parameter in a configuration file.
It works correctly if I use the cli command to do it.
PS> winget install OpenJS.NodeJS -v "18.11.0"
Found an existing package already installed. Trying to upgrade the installed package...
Found Node.js [OpenJS.NodeJS] Version 18.11.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://nodejs.org/dist/v18.11.0/node-v18.11.0-x64.msi
  ██████████████████████████████  29.2 MB / 29.2 MB
Successfully verified installer hash
Starting package install...
Successfully installed

Steps to reproduce
I have the following resource defined in my configuration file:
- resource: Microsoft.WinGet.DSC/WinGetPackage
      id: npm
      directives:
        description: Install Node version 18.11.x
        allowPrerelease: true
        maxVersion: "18.11.0"
      settings:
        id: OpenJS.Nodejs
        source: winget

Expected behavior
I expect it to install a version no higher than 18.11.0.
Actual behavior
When winget configure runs, it installs the latest version.
PS> npm version
{
  npm: '10.7.0',
  node: '22.2.0',
  acorn: '8.11.3',
  ada: '2.7.8',
  ares: '1.28.1',
  base64: '0.5.2',
  brotli: '1.1.0',
  cjs_module_lexer: '1.2.2',
  cldr: '45.0',
  icu: '75.1',
  llhttp: '9.2.1',
  modules: '127',
  napi: '9',
  nghttp2: '1.61.0',
  nghttp3: '0.7.0',
  ngtcp2: '1.3.0',
  openssl: '3.0.13+quic',
  simdjson: '3.9.2',
  simdutf: '5.2.8',
  tz: '2024a',
  undici: '6.13.0',
  unicode: '15.1',
  uv: '1.48.0',
  uvwasi: '0.0.21',
  v8: '<IP_ADDRESS>-node.12',
  zlib: '<IP_ADDRESS>-motley-7d77fb7'
}

Environment
machine is a fresh VM on Azure

Windows Package Manager v1.7.11261
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.3593
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.11261.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

nevermind.. I figured out I had the version in the wrong place.
should be
- resource: Microsoft.WinGet.DSC/WinGetPackage
      id: npm
      directives:
        description: Install Node version 18.10.x
        allowPrerelease: true
      settings:
        id: OpenJS.Nodejs
        source: winget
        version: "18.10.0"


Add Pie Chart Type to UI

Summary: Adds a pie chart. Give it one column to group/label with, and another to sum values from, and it'll output something like this.

Fixes #873
Relevant Issues: #873
Test Plan: Run this script with this vis spec.
Try hovering the individual pie slices. Compare the results to what's in the data drawer.
Try resizing the window so that the pie chart resizes to fit its container.
Try running the script more than once, to see how the color assignment behaves.
It should never be able to put two slices of the same color next to each other.
import px
import pxviews

ns_per_ms = 1000 * 1000
ns_per_s = 1000 * ns_per_ms
# Window size to use on time_ column for bucketing.
window_ns = px.DurationNanos(10 * ns_per_s)

def process_stats_by_namespace(start_time: str):
    ''' Gets a summary of process stats by namespace since `start_time`.
        Computes the total I/O consumption across the namespace since `start_time`.

    Args:
    @start_time Start time of the data to examine.
    '''
    df = pxviews.pod_resource_stats(start_time, px.now())
    df = df.groupby('namespace').agg(
        vsize=('vsize', px.sum),
        rss=('rss', px.sum),
        actual_disk_read_throughput=('actual_disk_read_throughput', px.sum),
        actual_disk_write_throughput=('actual_disk_write_throughput', px.sum),
        total_disk_read_throughput=('total_disk_read_throughput', px.sum),
        total_disk_write_throughput=('total_disk_write_throughput', px.sum),
    )

    return df[[
        'namespace',
        'vsize',
        'rss',
        'actual_disk_read_throughput',
        'actual_disk_write_throughput',
        'total_disk_read_throughput',
        'total_disk_write_throughput',
    ]]

{
    "variables": [
        {
            "name": "start_time",
            "type": "PX_STRING",
            "description": "The relative start time of the window. Current time is assumed to be now",
            "defaultValue": "-5m"
        }
    ],
    "widgets": [
        {
            "name": "VSize by Namespace",
            "position": {
                "x": 0,
                "y": 0,
                "w": 3,
                "h": 2
            },
            "func": {
                "name": "process_stats_by_namespace",
                "args": [
                    {
                        "name": "start_time",
                        "variable": "start_time"
                    }
                ]
            },
            "displaySpec": {
                "@type": "types.px.dev/px.vispb.PieChart",
                "pie": {
                    "value": "vsize",
                    "label": "namespace"
                }
            }
        }
    ],
    "globalFuncs": []
}

Type of change: /kind feature
Changelog Message:
New chart type: pie

Signed-off-by: Nick Lanam<EMAIL_ADDRESS>

Minor note: the color palette given to Vega here isn't quite what it used. Vega's docs don't seem to mention this, giving it a scheme of ['#FF0000', '#00FF00', '#0000FF'] ends up using every shade of red, green, and blue except the ones given, and it even puts a brown in there.

This also holds if giving it one of the predefined color schemes: it uses them as an inspiration, instead of using them directly.
It seems like using their builtin color schemes it does the right thing without interpolation: https://github.com/vega/vega/blob/7dbec7ddd0e94c8150e0f90857d851c72776ad0e/packages/vega-encode/src/Scale.js#L317-L323

We could just register our color scheme with vega with https://vega.github.io/vega/docs/api/extensibility/#scheme

It seems that isn't the code path it ends up using (at least, that isn't the entire story). When I gave it the builtin scheme category20, for instance, it used a combination of the colors in that theme and a few that it interpolated from there. It didn't need to do that: there are 20 colors in that scheme, but only eight slices to colorize in that test. Whatever it's doing, it's more complex than it looks.

When I look at category20 here It only uses the colors in the color scheme and doesn't interpolate

Closing the loop: it seems that the demo does as you say - where it only uses the colors in the theme if it's a named one - but something about our setup makes it interpolate anyway.
Registering a custom theme, however, does use only the given colors. That isn't ideal either, though, because it then sometimes gives the same color to two neighboring slices:

I could probably fix that, but the hsl-interpolated colors already do the right thing and look okay. Perhaps it's best to let it interpolate.


[qt5-webengine] assert vc_lib_atlmfc_path AssertionError

Host Environment

OS: Window 10 (x64-windows)
Compiler: The CXX compiler identification is MSVC 19.25.28614.0. Visual Studio 2019 Developer Command Prompt v16.5.4. Windows SDK version 10.0.18362.0 to target Windows 10.0.18363.

To Reproduce
vcpkg install qt5-base:x64-windows qt5-webengine:x64-windows
Failure logs
package-build-x64-windows-rel-out.log :
cd src\ && ( if not exist Makefile D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\src.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile
	cd buildtools\ && ( if not exist Makefile D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\buildtools\buildtools.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile
	( if not exist Makefile.ninja D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile.ninja D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\buildtools\ninja.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.ninja
	cd webengine\ui\ && ( if not exist Makefile D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\webengine\ui\ui.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile
	D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.Release
	D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -install qinstall D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\webengine\ui\qmldir ..\..\..\qml\QtWebEngine\Controls1Delegates\qmldir
	cd webengine\ui2\ && ( if not exist Makefile D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\webengine\ui2\ui2.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile
	D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.Release
	D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -install qinstall D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\webengine\ui2\qmldir ..\..\..\qml\QtWebEngine\Controls2Delegates\qmldir
build.cc
build_log.cc
clean.cc
clparser.cc
debug_flags.cc
depfile_parser.cc
deps_log.cc
disk_interface.cc
edit_distance.cc
eval_env.cc
graph.cc
graphviz.cc
lexer.cc
line_printer.cc
manifest_parser.cc
metrics.cc
state.cc
string_piece_util.cc
util.cc
version.cc
subprocess-win32.cc
includes_normalize-win32.cc
msvc_helper-win32.cc
msvc_helper_main-win32.cc
minidump-win32.cc
getopt.c
ninja.cc
Generating code
Finished generating code
[1/29] CXX build\debug_flags.obj
[2/29] CXX build\version.obj
[3/29] CXX build\depfile_parser.obj
[4/29] CXX build\edit_distance.obj
[5/29] CXX build\clparser.obj
[6/29] CXX build\deps_log.obj
[7/29] CXX build\manifest_parser.obj
[8/29] CXX build\build_log.obj
[9/29] CXX build\clean.obj
[10/29] CXX build\graphviz.obj
[11/29] CXX build\eval_env.obj
[12/29] CXX build\graph.obj
[13/29] CXX build\lexer.obj
[14/29] CXX build\string_piece_util.obj
[15/29] CXX build\subprocess-win32.obj
[16/29] CXX build\getopt.obj
[17/29] CXX build\state.obj
[18/29] CXX build\build.obj
[19/29] CXX build\line_printer.obj
[20/29] CXX build\metrics.obj
[21/29] CXX build\disk_interface.obj
[22/29] CXX build\util.obj
[23/29] CXX build\minidump-win32.obj
[24/29] CXX build\msvc_helper_main-win32.obj
[25/29] CXX build\msvc_helper-win32.obj
[26/29] CXX build\ninja.obj
[27/29] CXX build\includes_normalize-win32.obj
[28/29] LIB build\ninja.lib
[29/29] LINK ninja.exe
Generating code
Finished generating code
bootstrapping ninja...
warning: A compatible version of re2c (>= 0.11.3) was not found; changes to src/*.in.cc will not affect your build.
wrote build.ninja.
bootstrap complete.  rebuilding...
	D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.ninja.Release
	( if not exist Makefile.gn D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile.gn D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\buildtools\gn.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.gn
[1/172] CXX base/files/file_path_constants.obj
[2/172] CXX base/callback_internal.obj
[3/172] CXX base/files/scoped_file.obj
[4/172] CXX base/files/file.obj
[5/172] CXX base/files/scoped_temp_dir.obj
[6/172] CXX base/json/json_parser.obj
[7/172] CXX base/environment.obj
[8/172] CXX base/files/file_path.obj
[9/172] CXX base/files/file_enumerator.obj
[10/172] CXX base/command_line.obj
[11/172] CXX base/memory/ref_counted.obj
[12/172] CXX base/memory/weak_ptr.obj
[13/172] CXX base/json/json_writer.obj
[14/172] CXX base/md5.obj
[15/172] CXX base/json/string_escape.obj
[16/172] CXX base/strings/string_util_constants.obj
[17/172] CXX base/json/json_reader.obj
[18/172] CXX base/files/file_util.obj
[19/172] CXX base/third_party/icu/icu_utf.obj
[20/172] CXX base/strings/stringprintf.obj
[21/172] CXX base/strings/string_piece.obj
[22/172] CXX base/sha1.obj
[23/172] CXX base/timer/elapsed_timer.obj
[24/172] CXX base/strings/string_split.obj
[25/172] CXX base/logging.obj
[26/172] CXX base/strings/string_util.obj
[27/172] CXX base/strings/utf_string_conversion_utils.obj
[28/172] CXX base/value_iterators.obj
[29/172] CXX base/strings/string_number_conversions.obj
[30/172] CXX base/strings/utf_string_conversions.obj
[31/172] CXX base/values.obj
[32/172] CXX base/strings/sys_string_conversions_win.obj
[33/172] CXX base/files/file_enumerator_win.obj
[34/172] CXX base/win/scoped_process_information.obj
[35/172] CXX base/files/file_win.obj
[36/172] CXX base/win/scoped_handle.obj
[37/172] CXX base/win/registry.obj
[38/172] CXX base/files/file_util_win.obj
[39/172] CXX tools/gn/action_values.obj
[40/172] CXX tools/gn/action_target_generator.obj
[41/172] CXX tools/gn/args.obj
[42/172] CXX tools/gn/analyzer.obj
[43/172] CXX tools/gn/builder_record.obj
[44/172] CXX tools/gn/bundle_file_rule.obj
[45/172] CXX tools/gn/binary_target_generator.obj
[46/172] CXX tools/gn/bundle_data.obj
[47/172] CXX tools/gn/build_settings.obj
[48/172] LIB base.lib
[49/172] CXX tools/gn/c_include_iterator.obj
[50/172] CXX tools/gn/bundle_data_target_generator.obj
[51/172] CXX tools/gn/builder.obj
[52/172] CXX tools/gn/command_args.obj
[53/172] CXX tools/gn/command_check.obj
[54/172] CXX tools/gn/command_clean.obj
[55/172] CXX tools/gn/command_format.obj
[56/172] CXX tools/gn/compile_commands_writer.obj
[57/172] CXX tools/gn/command_analyze.obj
[58/172] CXX tools/gn/command_ls.obj
[59/172] CXX tools/gn/command_desc.obj
[60/172] CXX tools/gn/command_gen.obj
[61/172] CXX tools/gn/config_values.obj
[62/172] CXX tools/gn/command_refs.obj
[63/172] CXX tools/gn/exec_process.obj
[64/172] CXX tools/gn/config_values_extractors.obj
[65/172] CXX tools/gn/command_path.obj
[66/172] CXX tools/gn/command_help.obj
[67/172] CXX tools/gn/copy_target_generator.obj
[68/172] CXX tools/gn/commands.obj
[69/172] CXX tools/gn/escape.obj
[70/172] CXX tools/gn/err.obj
[71/172] CXX tools/gn/eclipse_writer.obj
[72/172] CXX tools/gn/create_bundle_target_generator.obj
[73/172] CXX tools/gn/config.obj
[74/172] CXX tools/gn/config_values_generator.obj
[75/172] CXX tools/gn/function_template.obj
[76/172] CXX tools/gn/function_foreach.obj
[77/172] CXX tools/gn/function_forward_variables_from.obj
[78/172] CXX tools/gn/deps_iterator.obj
[79/172] CXX tools/gn/desc_builder.obj
[80/172] CXX tools/gn/function_process_file_template.obj
[81/172] CXX tools/gn/filesystem_utils.obj
[82/172] CXX tools/gn/function_exec_script.obj
[83/172] CXX tools/gn/function_get_target_outputs.obj
[84/172] CXX tools/gn/function_set_defaults.obj
[85/172] CXX tools/gn/function_get_label_info.obj
[86/172] CXX tools/gn/function_rebase_path.obj
[87/172] CXX tools/gn/function_get_path_info.obj
[88/172] CXX tools/gn/function_read_file.obj
[89/172] CXX tools/gn/function_set_default_toolchain.obj
[90/172] CXX tools/gn/functions_target.obj
[91/172] CXX tools/gn/functions.obj
[92/172] CXX tools/gn/group_target_generator.obj
[93/172] CXX tools/gn/item.obj
[94/172] CXX tools/gn/label.obj
[95/172] CXX tools/gn/function_toolchain.obj
[96/172] CXX tools/gn/json_project_writer.obj
[97/172] CXX tools/gn/input_file.obj
[98/172] CXX tools/gn/input_file_manager.obj
[99/172] CXX tools/gn/lib_file.obj
[100/172] CXX tools/gn/inherited_libraries.obj
[101/172] CXX tools/gn/import_manager.obj
[102/172] CXX tools/gn/location.obj
[103/172] CXX tools/gn/header_checker.obj
[104/172] CXX tools/gn/label_pattern.obj
[105/172] CXX tools/gn/function_write_file.obj
[106/172] CXX tools/gn/operators.obj
[107/172] CXX tools/gn/input_conversion.obj
[108/172] CXX tools/gn/ninja_bundle_data_target_writer.obj
[109/172] CXX tools/gn/ninja_action_target_writer.obj
[110/172] CXX tools/gn/loader.obj
[111/172] CXX tools/gn/ninja_target_command_util.obj
[112/172] CXX tools/gn/ninja_group_target_writer.obj
[113/172] CXX tools/gn/ninja_binary_target_writer.obj
[114/172] CXX tools/gn/ninja_copy_target_writer.obj
[115/172] CXX tools/gn/pool.obj
[116/172] CXX tools/gn/ninja_create_bundle_target_writer.obj
[117/172] CXX tools/gn/ninja_utils.obj
[118/172] CXX tools/gn/output_conversion.obj
[119/172] CXX tools/gn/ninja_toolchain_writer.obj
[120/172] CXX tools/gn/ninja_writer.obj
[121/172] CXX tools/gn/pattern.obj
[122/172] CXX tools/gn/parse_node_value_adapter.obj
[123/172] CXX tools/gn/ninja_target_writer.obj
[124/172] CXX tools/gn/output_file.obj
[125/172] CXX tools/gn/parser.obj
[126/172] CXX tools/gn/ninja_build_writer.obj
[127/172] CXX tools/gn/parse_tree.obj
[128/172] CXX tools/gn/path_output.obj
[129/172] CXX tools/gn/scope.obj
[130/172] CXX tools/gn/qt_creator_writer.obj
[131/172] CXX tools/gn/scheduler.obj
[132/172] CXX tools/gn/scope_per_file_provider.obj
[133/172] CXX tools/gn/qmake_link_writer.obj
[134/172] CXX tools/gn/standard_out.obj
[135/172] CXX tools/gn/substitution_pattern.obj
[136/172] CXX tools/gn/source_dir.obj
[137/172] CXX tools/gn/runtime_deps.obj
[138/172] CXX tools/gn/switches.obj
[139/172] CXX tools/gn/substitution_list.obj
[140/172] CXX tools/gn/settings.obj
[141/172] CXX tools/gn/substitution_type.obj
[142/172] CXX tools/gn/substitution_writer.obj
[143/172] CXX tools/gn/token.obj
[144/172] CXX tools/gn/string_utils.obj
[145/172] CXX tools/gn/setup.obj
[146/172] CXX tools/gn/source_file.obj
[147/172] CXX tools/gn/source_file_type.obj
[148/172] CXX tools/gn/xml_element_writer.obj
[149/172] CXX tools/gn/variables.obj
[150/172] CXX tools/gn/tool.obj
[151/172] CXX tools/gn/template.obj
[152/172] CXX tools/gn/target.obj
[153/172] CXX tools/gn/visual_studio_utils.obj
[154/172] CXX tools/gn/target_generator.obj
[155/172] CXX tools/gn/value_extractors.obj
[156/172] CXX tools/gn/tokenizer.obj
[157/172] CXX tools/gn/toolchain.obj
[158/172] CXX tools/gn/value.obj
[159/172] CXX tools/gn/trace.obj
[160/172] CXX tools/gn/xcode_object.obj
[161/172] CXX tools/gn/visual_studio_writer.obj
[162/172] CXX util/worker_pool.obj
[163/172] CXX util/sys_info.obj
[164/172] CXX util/ticks.obj
[165/172] CXX util/exe_path.obj
[166/172] CXX tools/gn/visibility.obj
[167/172] CXX tools/gn/xcode_writer.obj
[168/172] CXX util/msg_loop.obj
[169/172] CXX util/semaphore.obj
[170/172] CXX tools/gn/gn_main.obj
[171/172] LIB gn_lib.lib
[172/172] LINK gn.exe
Generating code
Finished generating code
	D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.gn.Release
	cd core\ && ( if not exist Makefile D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\core\core.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile
	( if not exist Makefile.core_headers D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile.core_headers D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\core\core_headers.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.core_headers
	D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.core_headers.Release
	( if not exist Makefile.core_generator D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile.core_generator D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\core\core_generator.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.core_generator
	D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.core_generator.Release
	( if not exist Makefile.gn_run D:\app\vcpkg\installed\x64-windows\tools\qt5\bin\qmake.exe -o Makefile.gn_run D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\core\gn_run.pro "CONFIG-=debug" "CONFIG+=release" "CONFIG-=static" "CONFIG*=shared" -qtconf D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/qt.conf ) && D:\app\vcpkg\downloads\tools\jom\jom-1.1.3\jom.exe -f Makefile.gn_run
ERROR at //build/toolchain/win/BUILD.gn:432:24: Script returned non-zero exit code.
  x64_toolchain_data = exec_script("setup_toolchain.py",
                       ^----------
Current dir: D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/x64-windows-rel/src/core/release/
Command: "D:\app\vcpkg\downloads\tools\python\python-2.7.16-x64\python.exe" D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/src/5.12.7-0f8fbdda3a/src/3rdparty/chromium/build/toolchain/win/setup_toolchain.py win x64 environment.x64
Returned 1 and printed out:

vc_bin_dir = "D:\\Programs\\MSVS2019\\VC\\Tools\\MSVC\\14.25.28610\\bin\\HostX64\\x64"
include_flags_I = "/ID:\\Programs\\MSVS2019\\VC\\Tools\\MSVC\\14.25.28610\\include \"/IC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\ucrt\" \"/IC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\shared\" \"/IC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\um\" \"/IC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\winrt\" \"/IC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\cppwinrt\""
include_flags_imsvc = "-imsvcD:\\Programs\\MSVS2019\\VC\\Tools\\MSVC\\14.25.28610\\include \"-imsvcC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\ucrt\" \"-imsvcC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\shared\" \"-imsvcC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\um\" \"-imsvcC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\winrt\" \"-imsvcC:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\cppwinrt\""
vc_lib_path = "D:\\Programs\\MSVS2019\\VC\\Tools\\MSVC\\14.25.28610\\lib\\x64"

See //BUILD.gn:62:1: which caused the file to be included.
group("gn_all") {
^----------------

package-build-x64-windows-rel-err.log :
jom 1.1.3 - empower your cores

Project MESSAGE: Running: D:\app\vcpkg\buildtrees\qt5-webengine\x64-windows-rel\src\3rdparty\gn\out\Release\gn.exe gen D:\app\vcpkg\buildtrees\qt5-webengine\x64-windows-rel\src\core\release --script-executable=D:\app\vcpkg\downloads\tools\python\python-2.7.16-x64\python.exe --args="use_qt=true is_component_build=false is_shared=true enable_message_center=false enable_mus=false enable_nacl=false enable_remoting=false enable_reporting=false enable_web_speech=false enable_widevine=true has_native_accessibility=false use_allocator_shim=false use_allocator=\"none\" v8_use_external_startup_data=false treat_warnings_as_errors=false enable_swiftshader=false use_custom_libcxx=false enable_basic_printing=true enable_print_preview=true enable_pdf=true enable_plugins=true enable_spellcheck=true enable_webrtc=true enable_precompiled_headers=false is_official_build=true is_debug=false symbol_level=0 remove_webcore_debug_symbols=true remove_v8base_debug_symbols=true v8_use_snapshot=true use_kerberos=true is_clang=false use_sysroot=false enable_session_service=false ninja_use_custom_environment_files=false is_multi_dll_chrome=false win_linker_timing=true com_init_check_hook_disabled=true is_win_fastlink=false use_incremental_linking=false visual_studio_version=2019 visual_studio_path=\"D:/Programs/MSVS2019\" windows_sdk_path=\"C:/Program Files ^(x86^)/Windows Kits/10\" target_cpu=\"x64\" qtwebengine_target=\"D:\app\vcpkg\buildtrees\qt5-webengine\x64-windows-rel\src\core\release:QtWebEngineCore\"" --root=D:\app\vcpkg\buildtrees\qt5-webengine\src\5.12.7-0f8fbdda3a\src\3rdparty\chromium
Traceback (most recent call last):
  File "D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/src/5.12.7-0f8fbdda3a/src/3rdparty/chromium/build/toolchain/win/setup_toolchain.py", line 303, in <module>
    main()
  File "D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/src/5.12.7-0f8fbdda3a/src/3rdparty/chromium/build/toolchain/win/setup_toolchain.py", line 290, in main
    assert vc_lib_atlmfc_path
AssertionError
Traceback (most recent call last):
  File "D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/src/5.12.7-0f8fbdda3a/src/3rdparty/chromium/build/toolchain/win/setup_toolchain.py", line 303, in <module>
    main()
  File "D:/bluehawk/bhawk/vcpkg/buildtrees/qt5-webengine/src/5.12.7-0f8fbdda3a/src/3rdparty/chromium/build/toolchain/win/setup_toolchain.py", line 290, in main
    assert vc_lib_atlmfc_path
AssertionError
Project ERROR: GN run error!
jom: D:\app\vcpkg\buildtrees\qt5-webengine\x64-windows-rel\src\core\Makefile [sub-gn_run-pro-make_first] Error 3
jom: D:\app\vcpkg\buildtrees\qt5-webengine\x64-windows-rel\src\Makefile [sub-core-make_first] Error 2
jom: D:\app\vcpkg\buildtrees\qt5-webengine\x64-windows-rel\Makefile [sub-src-make_first] Error 2

Additional context
Building qt5-webengine:x64-windows fails with Project ERROR: GN run error! this is for Qt 5.12.7 (The default version of Qt in vcpkg.)
The same error also occurs if vcpkg install qt5-base[latest]:x64-windows qt5-webengine:x64-windows is used instead. But there's more. When qt5-base[latest]:x64-windows is selected, the build will fail before the error reported here and will do so at the point when the patches are applied to the extracted source archive. The folks at Qt decided to change the locations of some of the files which need to be patched in Qt version 5.14.2. I was able to work around this to check if the issue reported here persisted to the latest Qt version and it does.
My guess here is that gn is looking for vc_lib_atlmfc_path. According to https://doc.qt.io/qt-5/qtwebengine-platform-notes.html#windows

On Windows, the following additional tools are required:
Active Template Library (ATL), usually included in the Visual Studio installation

I tried building with and without ATL installed and the build error still persists. Although I didn't add it to the environment path. If the atlmfc port needs to be added to the control file as a dependency, is there a way atl needs to be added to the build environment?
I'm fairly sure this issue is unrelated to https://github.com/microsoft/vcpkg/issues/11019 as, from my testing it happens to qt5-base[latest] also.

https://github.com/Neumann-A/vcpkg/tree/fix_qt5_latest_webengine_patches
dbg build currently at [15426/27434] but I know that it wont finish since my machine does not have enough RAM for the rel build

@Neumann-A

Did you also select MFC in the VS Installer?

Yep:

but I know that it wont finish since my machine does not have enough RAM for the rel build

https://chromium.googlesource.com/chromium/src/+/master/docs/windows_build_instructions.md

A 64-bit Intel machine with at least 8GB of RAM.

4GB Surface Pro? https://www.microsoft.com/en-us/p/surface-pro/8nkt9wttrbjk?activetab=pivot:techspecstab
And:
https://github.com/Neumann-A/vcpkg/blob/7d7e0591e702e6e52cb0d8dbabcbf1dbfb0c100a/ports/qt5-webengine/portfile.cmake#L22
get_filename_component(NINJA_DIR "${GPERF}" DIRECTORY )
Do you mean? :
get_filename_component(NINJA_DIR "${NINJA}" DIRECTORY )
Also, I've been using powershell instead of patch files here:
## Timestamp announce to console
string(TIMESTAMP B_TS1 "Build started at %H:%M:%S on %d-%m-%y")
message(STATUS "* Build QtWebEngine from source begin:")
message(STATUS "* ${B_TS1}")
message(STATUS "* The process will take several hours")
message(STATUS "* (4-6 on average) to complete.")
message(STATUS "* Please be patient whilst the software is built")

if(QT_MAJOR_MINOR_VER STREQUAL "5.14")

    qt_download_submodule(OUT_SOURCE_PATH TARGET_SOURCE_PATH ${ARGV})

    if(EXISTS ${TARGET_SOURCE_PATH}/src/3rdparty/chromium/README.md)

        message(STATUS "* Patching the source tree...")
        ### ------------------------------------------------------
        ##                  "Fixes"
        ### ------------------------------------------------------

        file(READ ${TARGET_SOURCE_PATH}/src/buildtools/config/common.pri COM_PRI)
        ## "Fix" the "Ninja does not see existing precompiled header" error https://bugreports.qt.io/browse/QTBUG-65677
        ## Compiling the headers means the build takes significantly longer to complete
        string(REPLACE "gn_args += enable_precompiled_headers=true" "gn_args += enable_precompiled_headers=false" COM_PRI "${COM_PRI}")
        ##
        ## Write out the file
        file(WRITE ${TARGET_SOURCE_PATH}/src/buildtools/config/common.pri "${COM_PRI}")
        ## "Fix" the "chromium\ui\gl\gl_bindings_autogen_gl.h(401): error C2061: syntax error: identifier 'GLeglImageOES'" error message
        ## when compiling without precompiled headers
        file(READ ${TARGET_SOURCE_PATH}/src/3rdparty/chromium/ui/gl/gl_bindings_autogen_gl.h GLB_H)
	    string(REPLACE "class GLContext;" "class GLContext;\n\ntypedef void *GLeglImageOES;" GLB_H "${GLB_H}")
	    file(WRITE ${TARGET_SOURCE_PATH}/src/3rdparty/chromium/ui/gl/gl_bindings.h "${GLB_H}")
        file(REMOVE_RECURSE ${TARGET_SOURCE_PATH}/src/3rdparty/ninja) # QtWebEngine ships with a version of ninja, comment this line out if you want to use it

        ### ------------------------------------------------------

        ## Prevent patching twice upon rebuilds
        file(REMOVE ${TARGET_SOURCE_PATH}/src/3rdparty/chromium/README.md)

        message(STATUS "* Source tree patched")

    else()

        message(STATUS "* Source tree is already patched...")

    endif()
    ## Add some includes to the INCLUDEPATH
    set(ENV{INCLUDEPATH} "${TARGET_SOURCE_PATH}/include/;$ENV{INCLUDEPATH}")
    set(ENV{PATH} "${TARGET_SOURCE_PATH}/src/3rdparty/gn/);$ENV{PATH}")

    if(QT_UPDATE_VERSION)
        SET(VCPKG_POLICY_EMPTY_PACKAGE enabled PARENT_SCOPE)
    else()
        qt_build_submodule(${TARGET_SOURCE_PATH} ${ARGV})
        qt_install_copyright(${TARGET_SOURCE_PATH})
    endif()

else()

qt_submodule_installation(PATCHES
                                common.pri.patch
                                gl.patch)

endif()

string(TIMESTAMP B_TS2 "Build completed at %H:%M:%S on %d-%m-%y")
message(STATUS "* ${B_TS2}")

You installed the spectre mitigated ATL/MFC libs those are only used if you also switch the toolset to be spectre mitigated. VCPKG uses the default toolset if not changed by the triplet

@Neumann-A

You installed the spectre mitigated ATL/MFC libs those are only used if you also switch the toolset to be spectre mitigated.

You are absolutely right. I noticed before I read your comment. Thanks.
I installed the unmitigated ATL/MFC libs and it looks like the build picked them up.
Observations:
If you only install the spectre mitigated ATL/MFC libs then the atlmfc port is picking them up. I say this because I had no ATL/MFC libs installed and due to the atlmfc dependency of qt5-translations, a different workload (which does not depend upon webengine) failed and asked for ATL/MFC to be installed. I installed only the spectre mitigated ATL/MFC libs and the qt5-translations build completed. Is this the expected behaviour of the atlmfc port?

VCPKG uses the default toolset if not changed by the triplet
Would you mind please sharing with me how to set this in a triplet? I wasn't aware that this was a thing.

It seems odd to me that spectre mitigated libs are not the default. Spectre is a serious problem for me being all Intel here.

At least the release link step runs up and above 32 GB for me

Running 16 GB here and I've had release only builds of QtWebEngine going for 6 months+.

Would you mind please sharing with me how to set this in a triplet? I wasn't aware that this was a thing.

set VCPKG_PLATFORM_TOOLSET to whatever the toolset is called in the triplet file. Don't know how well vcpkg handles non default VS platform toolset but could be that you need to use the LLVM toolset workaround which is:
if(DEFINED VCPKG_PLATFORM_TOOLSET)
  set(VCPKG_PLATFORM_TOOLSET llvm)
endif

(exchange llvm with whatever platformtoolset you require if it is not working without the if/endif)
You might also need to set additional build flags for spectre mitigation?

Running 16 GB here and I've had release only builds of QtWebEngine going for 6 months+.

But i assume that is not within vcpkg or is it? I assume it has to do with the debug info in all the libraries vcpkg installs

set VCPKG_PLATFORM_TOOLSET to whatever the toolset is called in the triplet file.

I think I can explain what has happened. The atlmfc port worked using just the spectre mitigated libraries because I use:
powershell -command " & {(Get-Content %VCPKGDIR%\scripts\toolchains\windows.cmake).replace('/DNDEBUG /Z7', '/DNDEBUG /Qspectre /Qpar /Ot /MP /std:c++14 /arch:AVX') | Set-Content %VCPKGDIR%\scripts\toolchains\windows.cmake}"
powershell -command " & {(Get-Content %VCPKGDIR%\scripts\cmake\vcpkg_configure_meson.cmake).replace('/DNDEBUG /Z7', '/DNDEBUG /Qspectre /Qpar /Ot /MP /std:c++14 /arch:AVX') | Set-Content %VCPKGDIR%\scripts\cmake\vcpkg_configure_meson.cmake}"

to remove an arbitrary compiler flag and to add some that I want. I had forgot I was doing that (it is scripted.)
So it would appear that the QtWebEngine port might be ignoring compiler flags being passed to it by vcpkg unless I'm missing somewhere else to set that /Qspectre flag where QtWebEngine's build would pick it up?

You might also need to set additional build flags for spectre mitigation?

Yep. Here's how I'm doing it using cmake for the applications I build:
        message ("Setting spectre mitigation")
        set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /Qspectre")
        set (CMAKE_C_FLAGS "${CMAKE_C_FLAGS} /Qspectre")

But i assume that is not within vcpkg or is it?

Yeah. I have had a port of QtWebEngine for over six months now. Build machine has 16GB of RAM.
I just successfully completed a release only build using your new patches using it today for:
vcpkg install angle:x64-windows qt5-base[latest]:x64-windows  qt5-winextras:x64-windows qt5-translations:x64-windows qt5-tools:x64-windows qt5-webengine:x64-windows ecm:x64-windows openssl-windows:x64-windows gettext:x64-windows
Fastest build time so far at three and a half hours. vcpkg folder ended up at 18.5 GB total size on disk. I'm switching to your port for maintainability. Most of the stuff I was maintaining seperately, you have implemented apart from removing the libpq dependency from QtBase to reduce build times.
-- Performing post-build validation
-- Performing post-build validation done
Building package qt5-webengine[core]:x64-windows... done
Installing package qt5-webengine[core]:x64-windows...
Installing package qt5-webengine[core]:x64-windows... done
Elapsed time for package qt5-webengine:x64-windows: 3.687 h

So, this report can be closed once your patches are merged into master as they solve the qt5-base[latest] build failure.
Also, you should add:
file(REMOVE_RECURSE ${TARGET_SOURCE_PATH}/src/3rdparty/ninja)

to your port if you want QtWebEngine to pickup and use vcpkg's ninja. It always prefers the ninja (and gn) which ships with the source and will always build and use them if they are found. The reason is that there can be some severe breakage between versions of gn, ninja and chromium and I have seen newer versions of gn and ninja not be able to compile older QtWebengine code.It is a bit of a mess. I honestly think using vcpkg's copy of ninja is the way to go though.
Thanks for the help! The application code I have compiled against the result of your patches looks to be working very well.

So it would appear that the QtWebEngine port might be ignoring compiler flags being passed to it by vcpkg unless I'm missing somewhere else to set that /Qspectre flag where QtWebEngine's build would pick it up?

Qt is currently completely in control of all compiler flags using qmake via the used mkspec. You could try passing these flags via the qt.conf but it seems at least for qt5-base the mkspec needs to be patched at mkspecs/common/msvc-desktop.conf or apparently added to the configure call according to the config_help.txt (ports/qt5-base/cmake/configure_qt.cmake):
It is also possible to manipulate any QMAKE_* variable, to amend the values
from the mkspec for the build of Qt itself, e.g., QMAKE_CXXFLAGS+=-g3.

We probably want to pass VCPKG_CXX_FLAGS etc there to the corresponding QMAKE_ variables
file(REMOVE_RECURSE ${TARGET_SOURCE_PATH}/src/3rdparty/ninja) gives me an error since vcpkg tries to use the VS instance of ninja for me which is on a path with spaces and does not handle it correctly.

Build machine has 16GB of RAM.

wonder how you do it... my machine has at least 25 GBs of free ram for the build an still tells me it runs out of memory. Maybe related with the number of threads working or the used HDD? I saw something similar with VTK that on my 32 GB machine the linker runs out of memory and vcpkg retries without parallelism while on my 8 GB work machine the ram nearly tops out but the build continues fine.... Don't know whats happening here

Thanks for the help! The application code I have compiled against the result of your patches looks to be working very well.Thanks for the help! The application code I have compiled against the result of your patches looks to be working very well.

Good to know !

Add into configure_qt at line 99
        macro(setup_compile_flags lang langqt)
            if(VCPKG_${lang}_FLAGS)
                list(APPEND BUILD_OPTIONS "QMAKE_${langqt}FLAGS+=${VCPKG_${lang}_FLAGS}")
            endif()
            if(VCPKG_${lang}_FLAGS_DEBUG)
                list(APPEND BUILD_OPTIONS "QMAKE_${langqt}FLAGS_DEBUG+=${VCPKG_${lang}_FLAGS_DEBUG}")
            endif()
            if(VCPKG_${lang}_FLAGS_RELEASE)
                list(APPEND BUILD_OPTIONS "QMAKE_${langqt}FLAGS_RELEASE+=${VCPKG_${lang}_FLAGS_RELEASE};QMAKE_${langqt}FLAGS_RELEASE_WITH_DEBUGINFO+=${VCPKG_${lang}_FLAGS_RELEASE}")
            endif()
        endmacro()
        setup_compile_flags(C C)
        setup_compile_flags(CXX CXX)
        setup_compile_flags(LINKER L)

might also be needed in vcpkg_configure_qmake

wonder how you do it... my machine has at least 25 GBs of free ram for the build an still tells me it runs out of memory.

I would suspect an underlying hardware issue or a software misconfiguration somewhere. It's annoying when you get those kind of issues and I guess you could confirm a hardware problem with a full software reload. Including Windows. :confounded:

vcpkg tries to use the VS instance of ninja

That's weird and unexpected behaviour imo. I looked and couldn't find ninjabuild in the VS installer. Did you install it from there?

Maybe related with the number of threads working or the used HDD?

This is what I have:
https://ark.intel.com/content/www/us/en/ark/products/75124/intel-core-i7-4770s-processor-8m-cache-up-to-3-90-ghz.html 8MB Cache, 4 cores, 8 threads but it's quite old and still uses DDR3. I have Win 10 Pro on a Crucial SSD and build software on a WD 1TB mechanical disk drive. Both HDDs are SATA 6.0 Gb/s. All Windows temp files are set to use a separate partition on the mechanical drive. I built the machine quite a few years ago to do RHSCA and then put Windows 10 on it so I could game via Steam.
Funnily enough, it has an oldish Radeon GPU in there too and the way Windows 10 isolates GPU and CPU tasks means that whilst vcpkg was building webengine, the GPU was decoding 1080p 60fps h.264 streaming video in New Edge (Chromium)  and displaying it on a second screen with no visible jitter or lag. Quite impressive utilisation of memory and isolation of hardware acceleration imo.
No fancy clustering or cabinet based blade servers here. Just off the shelf consumer parts put together a while ago by me. :smiley:


SSL error

On https://refgenomes.databio.org/ I get Error code: SSL_ERROR_INTERNAL_ERROR_ALERT

Yes we haven't set up https:// yet on that server.
try: http://refgenomes.databio.org

Thanks for the answer. I remember that I clicked on a link somewhere in the docs (can't recall where) and got to the https page. Maybe there is somewhere a link that does not have the http:// ?

could be. I'll look around.
we'll enable https soon and then the link will work! I'll leave this issue open till we get it sorted out.

btw, are you having trouble pulling assets right now? See #169

I just discovered this project and started reading when I stumbled over this one. Have not tried to pull yet :(


Probably cache issues after update

After the last flutter stable update, the album cover is not showing anymore for any song I've tried. It goes with the following error message:
I/flutter ( 2965): ══╡ EXCEPTION CAUGHT BY IMAGE RESOURCE SERVICE ╞════════════════════════════════════════════════════
I/flutter ( 2965): The following FileSystemException was thrown resolving an image codec:
I/flutter ( 2965): Cannot open file, path =
I/flutter ( 2965): '/storage/emulated/0/Android/data/com.android.providers.media/albumthumbs/1571389004003' (OS Error:
I/flutter ( 2965): No such file or directory, errno = 2)
I/flutter ( 2965): When the exception was thrown, this was the stack:
I/flutter ( 2965): #0      _File.open.<anonymous closure> (dart:io/file_impl.dart:364:9)
I/flutter ( 2965): (elided 13 frames from package dart:async)
I/flutter ( 2965): ...
I/flutter ( 2965): Path: /storage/emulated/0/Android/data/com.android.providers.media/albumthumbs/1571389004003
I/flutter ( 2965): ════════════════════════════════════════════════════════════════════════════════════════════════════

Hello buddy, recently I am very busy with job coding but I'll provide fixes soon as possible for all the problems. Thanks for your feedback means a lot.

Hello buddy, recently I am very busy with job coding but I'll provide fixes soon as possible for all the problems. Thanks for your feedback means a lot.

No problem, I'm just working with your library on a daily basis currently, so I report what I see...

Similarly sometimes I don't get any list of songs at all, therefore I think this could be a cache issue.

Seems no longer relevant (haven't seen the issue for a while)


Latest iteration

renamed guides to docs
rendering markdown to html via github api on server start
doc navigation
syntax highlighting

:shipit:


jax.random.randint silently ignores dtype of int64 instead of generating warning

Description
import jax.numpy as jnp
import jax.random as jr
k = jr.PRNGKey(0)
a = jr.randint(k, (10,), minval=10, maxval=20, dtype=jnp.int64)  # no warning is printed!
assert a.dtype == jnp.int32
a = a.astype(jnp.int64)  # warning is printed

What jax/jaxlib version are you using?
3.17
Which accelerator(s) are you using?
CPU
Additional System Info
macos

Thanks for the report - it looks like we forgot to call _check_user_dtype_supported.

It looks like this has been fixed.


How do ui-dropdown work with not string variables?

Hello.
I can't figure out how to work the ui-dropdown.
# controllers/index.js
 sexs: [
    Ember.Object.create({name: "Not pick", value: null}),
    Ember.Object.create({name: "Man", value: true}),
    Ember.Object.create({name: "Woman", value: false})
  ],
  actions: {
    setSex: function (component, id, value) {
      console.log(component, id, value);
      this.set('model.sex', value);
    }
}

# templates/index.hbs
{{#ui-dropdown class="selection" disabled=isNotEditable onChange=(action 'setSex')}}

	{{#if (eq model.sex true)}}
Man
{{/if}}
	{{#if (eq model.sex false)}}
Woman
{{/if}}
	{{#if (eq model.sex null)}}
Not pick
{{/if}}

		{{#each sexs as |sex|}}

{{sex.name}}

		{{/each}}

{{/ui-dropdown}}

When I change dropdown I see in console
Class {...} "true" "Man"
Class {...} "false" "Woman"
Class {...} "not pick" "Not pick"

How better to do to get true, false and null?

ui-dropdown used to allow value binding (in Semantic-UI), then it was changed to only allow string binding to better align with html. Because of this, we created a new dropdown called UI-Dropdown-Array. That will let you bind to an object. I'll add a ticket to update the readme, but you can look at the example in the dummy app.

@aaronbhansen thanks for the reply, but as far as I understand, ui-dropdown-array will return a whole object, not on a specific value? How do I use ui-dropdown-array?

Ah I thought you wanted the whole object. We use value binding for most of our dropdowns today. Here is the example of our country dropdown
    {{#ui-dropdown class="fluid selection" selected=card.country}}
      <input type="hidden" name="country" value={{card.country}}>

      {{#each countries as |content|}}

{{content.name}}

      {{/each}}

    {{/ui-dropdown}}

With your action binding though, if you look at the semantic documentation, it should pass the value into the action and you can parse it from there on the standard dropdown. As I mentioned in my first comment, everything is a string to semantic, so even though you have true as the data value, you would need to parse it back to false in your action. We are looking at possibly adding some transformers in the 2.0 branch to convert the string back to a boolean for example in the action, but nothing definite yet.
I'd say for now your best approach is to do something like
setSex(component, value, text) {
  if (value === "true") {
    this.set('property', true);
 }
 ...
}


How to debug backend code?

I am using gulp to run the project, how can I debug the backend code?

You can run the server in debug mode with gulp debug, there should be more information about it in our README.


[5.1] constructor auto dependency injection not working in controller

Trying to inject dependency through controller __construct gives error:
Object of class App\Services\FooService could not be converted to string
Simple test controller:
<?php namespace App\Http\Controllers;

use App\Services\FooService;

class TestController extends Controller
{
    protected $foo;

    public function __construct(FooService $foo)
    {
        $this->$foo = $foo;
    }

    //method injection works as expected
    // public function foo(FooService $foo)
    // {
    //     return $foo->fire();
    // }

}

Simple FooService class:
<?php

namespace App\Services;

class FooService {
    public function fire()
    {
        return "Hello from FooService.";
    }
}

That's because you assign it like this:
$this->$foo = $foo;

That should read:
$this->foo = $foo;

Oh wow. Sorry, didn't see that typo.


Fails on Safari

When trying on Safari Version 9.0.2 (11601.3.9):
PDK.login({scope: 'read_public'})

it fails with error:
TypeError: undefined is not an object (evaluating 'd.location')

Hey Nikita, thanks for reaching out! I see the error you're talking about, and it should be an easy fix. I wish we had the JS SDK up on github as well and then I could just have you fix it! I'll merge in the change today and let you know.

cool thanks! ;)

What is the status of this? Is it being fixed?
Many thanks
Tom

FYI this is caused by popup blockers. Disable your popup blocker during development and it runs fine.


More robust netlist extraction

For GDS imported from GDS where some of the instances  are not part of the PDK, this PR fixes the extraction to ignore instances that are not created using the cell decorator and therefore are not registered in the PDK

Looks good to me


Dicyclics 30 and 42, wordgroup and semi-direct product are not isomorphic

Dicyclics 30 and 42 bugs, wordgroup and semi-direct product are not isomorphic for the first faithfull action which is choosen by default for semi-direct product.
https://github.com/aidevnn/FastGoat/blob/1316cfb955eae1e6b3f256251eecc8b266cca331/FastGoat/Program.cs#L34-L47
Semi-direct product is faster than word group or than permutation group but has many problems for choosing the right group action.

Quartenion groups have two generators, and a default action with identity and inverse automorphism is enough for dicyclic groups of order less than 200.


Old version for Belgium EID

Just discover that Belgium authority is delivering new EID software than the one in the cask.
It can be downloaded from here: https://eid.belgium.be/fr
I.e. in the tap we have:
4.1.18
The newest one is:
4.2.7

https://github.com/caskroom/homebrew-eid/pull/24

Arrrgh ... it was so quick - you need to upgrade also
be-eid-viewer - from the same link
be-eid-midleware - for that one don't know


Custom number of acks

I noticed the exported methods to set the Acks only allow 0, 1 an -1 to be set - is there any reason to not allow custom values for when say I'd like 2 acks?
https://github.com/twmb/franz-go/blob/3e9dc14/pkg/kgo/config.go#L862-L890

Looked in the source,
https://issues.apache.org/jira/browse/KAFKA-1697
Acks != -1, 0, or 1 was removed in 0.9.
See this commit:
https://github.com/apache/kafka/commit/eab4f4c9f43
Specifically this function:
  private def isValidRequiredAcks(requiredAcks: Short): Boolean = {
    requiredAcks == -1 || requiredAcks == 1 || requiredAcks == 0
  }


Support readOnly property from latest validation draft

Reasons for making this change
Since the readOnly property now is available in the latest validation draft (previously it was in hyper schema only), it makes sense to use this property to signal read only for fields.
Fixes #976
Replaces PR https://github.com/mozilla-services/react-jsonschema-form/pull/888
Checklist

[x] I'm updating documentation

[x] I've checked the rendering of the Markdown text I've added

[x] I'm adding or updating code

[x] I've added and/or updated tests
[x] I've updated docs if needed
[x] I've run npm run cs-format on my branch to conform my code to prettier coding style

[ ] I'm adding a new feature

[ ] I've updated the playground with an example use of the feature

Would it be possible to have a new release with this included soon?

Is there any plan for a new release soon? I really need this feature.


[bug] GIT hooks synchronization not working on windows under git bash

Describe the bug

I'm trying to setup git hooks via moon on windows under GIT bash.
The issue is that under GIT bash, moon sync hooks will deploy under .git/hooks/pre-commit, a hook that is calling the .\.moon\hooks\pre-commit.ps1 (powershell) file instead of .\.moon\hooks\pre-commit (bash):
#!/bin/sh
powershell.exe -NoLogo -NoProfile -ExecutionPolicy Bypass -File ".\.moon\hooks\pre-commit.ps1" $1 $2 $3

Steps to reproduce

Create your hook under .moon/hooks/pre-commit.
Add the hook config under .moon/workspace.yml

...
vcs:
  manager: 'git'
  syncHooks: true
  hooks:
    pre-commit:
      - 'pre-commit run'
...

Run moon sync hooks under GIT bash
Add and commit `git commit -am "test"

error:
pre-commit : The term 'pre-commit' is not recognized as the name of cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:........moon\hooks\pre-commit.ps1:7 char:1
Expected behavior
Under windows & GIT bash, when syncing hooks, the hook that should be used is the bash one instead of the powershell one.

Screenshots

Environment

moon --version
moon 1.23.1

Additional context
Here also the file pre-commit.ps1 generated
#!/usr/bin/env powershell
$ErrorActionPreference = 'Stop'

# Automatically generate by moon. DO NOT MODIFY!
# https://moonrepo.dev/docs/guides/vsc-hooks

pre-commit run

EDIT:
I think I misunderstood how it work. I didn't notice that the file generated by moon sync hooks was based on the vcs.hooks. commands.
But the issue remains the same, the sync generate the ps1 that is called from git hooks. But as I'm using GIT bash, it'd be better to generate the bash version of the hook and not the ps1.

Yah right now Windows assumes powershell. Let me add a setting to force it to Bash.

Sorry this took so long, it got buried.
I've added a new setting in v1.29 to support this https://moonrepo.dev/docs/config/workspace#hookformat


[4.X] Fix button variable name

Also while working on this I noticed we have:
public function addButton($stack, $name, $type, $content, $position = false, $replaceExisting = true)
    {
        if ($replaceExisting) {
            $this->removeButton($name, $stack);
        }

        return new CrudButton($name, $stack, $type, $content, $position);
    }

Even if we setup $replaceExisting = false, if the button has the same name of some previously added button it will be replaced:
    private function save()
    {
        $itemExists = $this->collection()->contains('name', $this->name);

        if (! $itemExists) {
            if ($this->position == 'beginning') {
                $this->collection()->prepend($this);
            } else {
                $this->collection()->push($this);
            }

            // clear the custom position, so that the next daisy chained method
            // doesn't move it yet again
            $this->position = null;
        } else {

            $this->collection()->replace([$this->getKey() => $this]); // <------ HERE IF ITEM WITH
                                                                    // NAME EXISTS WE REPLACE
        }

        return $this;
    }

Should the $replaceExisting be removed and the docs updated to reflect that change ?
ATM you can't have 2 buttons with same name.
Let me know @tabacitu

A new inspection was created.

The inspection completed: No new issues

Ouch! Looks like it got lost in the v4.1 fluent rewrite. Obviously not many people have been using $replaceExisting since it wasn't documented and nobody cried yet, but... it is a breaking change now that you mention it.
I imagine if the parameter is there it should help put two buttons in one go, then. Maybe if $replaceExisting == false and the button name already exists, it sets the name to false, so that the name for the second button would be randomly assigned?

So something like:
public function addButton($stack, $name, $type, $content, $position = false, $replaceExisting = true)
    {
+       // i'm not sure this block is needed at all TBH
        if ($replaceExisting) {
            $this->removeButton($name, $stack);
        }

-        return new CrudButton($name, $stack, $type, $content, $position);
+        return new CrudButton($replaceExisting ? $name : false, $stack, $type, $content, $position);
    }

Wouldn't that be a solution to adding a button twice? Granted, the second (or third) one that gets added will not have the same name, but at least it'll be there, right? It'd be visible.


Prompt for Lagoon Variable

Is your feature request related to a problem? Please describe.
When people add password variables using the Lagoon CLI, they have to type the password on the command line.
Describe the solution you'd like
The Lagoon CLI will prompt you to enter a value for the variable, and not echo it as you type
Describe alternatives you've considered
None
Additional context
Possible ideas include:

Prompt for a value if none is given, or at least if someone passes --value-prompt true
Allow a --value-prompt secret option that makes it not echo anything at all

Possibly should be a security bug instead of a feature request.
HTH,

The problem though is that not all variables are passwords or secrets.
Will have to have a think about this a bit.

Oh, agreed.  That's why my plan is that we use the --value-prompt as follows:

Not specified -- current behaviour
Matches /^(secret|hidden)$/ -- treats it as a password/secret
true -- treats it as a non-secret, but will prompt for the value

HTH,

Oh, agreed. That's why my plan is that we use the --value-prompt as follows:

Not specified -- current behaviour
Matches /^(secret|hidden)$/ -- treats it as a password/secret
true -- treats it as a non-secret, but will prompt for the value

HTH,

Can you show how you think this would work with a complete command line example please

$ lagoon add variable --project master-project --environment staging --scope runtime --name MY_PASSWORD --value-prompt secret
Please enter the value:
success!

In the example above, the value was entered but not echoed.  While it's traditional for programs like SSH not to accept passwords on STDIN, this might be a case where the password should be accepted on STDIN.
$ lagoon add variable --project master-project --environment staging --scope runtime --name MY_VARIABLE --value-prompt true
Please enter the value: Hi!  I'm a value
success!

In the second example, above, the value "Hi!  I'm a value"  was entered, and is visible at the prompt.  This is visible because --value-prompt was not "secret" or "hidden".  It may be that it should've rejected it for containing invalid characters; if so, feel free to adjust the example so it doesn't.
The third case I won't give an example of, because it's just using --value instead of --value-prompt, and things working the way they do now.
HTH,

Yeah, I don't know about this whole prompt switch thing like that.
If this was going to be something we support, I would have --value-secret or --value as the only supported flags. and you provide one or the other.
The --value-secret flag would prompt you to enter the secret like you suggest while hiding the input, while --value would require the user to use the cli as they do now.
Like this then:
lagoon add variable --project master-project \
  --environment staging \
  --scope runtime \
  --name MY_VARIABLE \
  --value-secret
Please enter the value:
success!

And then the default behaviour
lagoon add variable --project master-project \
  --environment staging \
  --scope runtime \
  --name MY_VARIABLE \
  --value "my value"
success!

If a user did something like this, it would have to ignore the --value-secret flag.
lagoon add variable --project master-project \
  --environment staging \
  --scope runtime \
  --name MY_VARIABLE \
  --value "my value" \
  --value-secret

Not 100% what I wanted, but definitely close enough to keep me happy :) .  Satisfies the security requirement, and I can add my own scripting for the non-secret case.
I'd suggest a warning in the last case, when both options are specified.
HTH,

Not 100% what I wanted, but definitely close enough to keep me happy :) . Satisfies the security requirement, and I can add my own scripting for the non-secret case.

I don't see a reason to have hidden|secret|true as the prompt if you're wanting to protect the stdin and one of the options still makes the input visible. If the idea is to keep them "secret" then why even bother having a prompt that still displays it as plain text in the prompt? It is also more work and logic to have the individual cases to support hidden text and visible text and I think makes it more complicated over all.

I'd suggest a warning in the last case, when both options are specified.

Warning why? When the user presses enter in the case both are specified its going to run the command and perform some work. So the act of trying to preserve the secret is already lost in that case.

For the purpose of protecting STDIN, you're right, you don't need the other options.  It was more a convenience for the user, but thinking about it more, it's probably not as useful as I thought it might be.
The reason I suggest the warning is because it means that someone made a mistake.  For a single run, that's not a problem, but if that mistake has eg. been pasted into documentation, or is used in a script, then it'd be nice for people to know about it.  I mean, still change the variable and be successful, but let people know that the --value-secret flag was ineffectual.

HTH,


Cherry pick some patches to 7.1

Cherry pick #843, #923, #911, #942 to 7.1 branch.

Fix the inbalance issue of replica read request when store is down and up by reloading the latest region in background.
For replica read, when leader is busy, fallback to follower.
Set max retry for replica read.
Add test of replica selector's state for stale read.

/cc @crazycs520


dnt from npm to ts/js deno module

thank you for this project
it seems node and deno will coexist for long time.
dnt will allow in some situation to write js universal library with ts-deno ecosystem but we need need think in other direction I mean convert npm package ( may be without deps ) to deno.land/x registry in a way we can convert any nodejs project to js code working on deno.
I know skypack convert npm modules to esm and deno std/node and deno compat try to solve this problem but I don't see any integration/mixing all those for global solution

dnt will allow in some situation to write js universal library with ts-deno ecosystem but we need need think in other direction I mean convert npm package ( may be without deps ) to deno.land/x registry in a way we can convert any nodejs project to js code working on deno.

We've thought about this and it's much harder to create a tool like dnt for going from node to deno. Probably esm.sh and skypack are the best bet.


Implement mailbox changes

Fixed in https://github.com/AugurProject/augur/pull/767
The removal of mailbox went hand-in-hand with no longer using ether as denomination token


Trying new PM

Get to go from here....

Testing comment

Hi maengkom,
I am trying to integrate box api in laravel but i am not able to auth box app so please can you help me what mistak i do there.

Hi @sureshwininfo, what version of laravel do you use ? I'll try to check. Please create new issue, I'll close this.

I am using laravel 5.2 version.

use BoxSU;
After Above I Call Below Method
$boxInfo = BoxSU::getFolderInfo('0', true);

If error of stat filesize : try to update package or update your exising code with this little bit fix  https://github.com/maengkom/boxapi/commit/12b647fdd0f4b521de5a12bdc3c3f49ced2d1b95
If other error, may be your configuration. Get client id, client secret and set redirect url in https

And open config/boxapi.php and set it those values for su_client_id, su_client_secret, and redirect_uri. Done you can use box standard user.

Okay Thanks For Your Support But I am Not Success Because I am Call This API In My Local System And Setup Setting Like As Your Give In Help.

'su_client_id'      => '4nnn7egp....',
'su_client_secret'  => 'm00Pae0t....',
'redirect_uri'  	=> 'http://localhost'

Above Is My boxapi.php file settings.


Add tracking options to sharding

Keep track of the set of shards a model is saved on. If the set of shards changes (because getShardForModel is not based on ID) then make the necessary calls (removes and creates).
Think about how this will impact users with stale or overwritten values which decide the shard.

On create, all, get, and query we try to set the shards the model exists on.
On update we call the necessary create/update/remove methods for each shard cached on the model and newly determined by the method.
On remove we try to use the cached shards instead of newly determined ones.


feat: support admin enable user sms and email mfa

fix: #2215
https://github.com/casdoor/casdoor/assets/71440988/37566cc9-12f1-4a06-b1e8-ca28a5664f4b

@leo220yuyaodog demo video?
and what issue does this PR fix?

fix: #2215
https://github.com/casdoor/casdoor/assets/71440988/37566cc9-12f1-4a06-b1e8-ca28a5664f4b

@leo220yuyaodog fix e2e:

@leo220yuyaodog fix e2e:

yarn start time out, may need to increase the wait time.


Make the track authors' life easier

This is a meta-ticket to collect problems we find when creating tracks and to gather some ideas to make the track authors' life easier.
Here are some problems we are already aware of:

[ ] Docs are a bit light w.r.t to structuring custom runners (what is the root package when you want to use multiple files and need to import stuff, etc.?)
[ ] No support for unit-testing custom runners
[X] No support for benchmarking custom runners or gathering timing info (-> potential client-side bottlenecks). Ideally we'd have some sort of profiling support for that (resolved by #216)
[x] The git workflow gets overly complex when contributing to Rally's default tracks via pull requests. (solved by --track-path so there is no need for git anymore)
[ ] We could provide a tool to create track data files from existing indices (see e.g. https://gist.github.com/HonzaKral/0fb3f76da529ee380d08).

Closing as too unspecific. I also created #444 in favour of the last item.


CodeGen error: sample data in Consoleapp.Program.cs can't handle NaN value.

The correct code for float.NaN should be float.NaN instead of NaNF.

Not fixed

@zewditu Could you take a look

Not repro this issue on main build: <IP_ADDRESS>7701


build: remove unused boost libraries

test via git grep "boost/chrono" and git grep "boost/system"
additionally tested via doing a rebuild of depends and src build
This should speed up build times of depends.

Looks better :) What about removing all mentions of libboost-chrono-dev/libboost-system-dev (also like in 18264)?


Fix: Even border thickness

2023-05-08.13-39-57.mp4
It's a little weird during the animation on firefox, but maybe thats fine

Looks the same on Chrome for me. So, think it's fine unless @rikaznismi doesn't agree.

Looks the same on Chrome for me.

Weird, I don't get that in chrome

And to be clear I'm talking about the border thickness during the transition

I am also getting the same issue, chrome as well. Probably because duration is applied to thickness as well. I am having some problems with targeting transition on height, does not seem to work so far.

@mathiasmagnusson updated the transition a bit, so the transition does not look weird in the sides of the border. And on the top of border, I removed the transition to it, since adding transition to it gave the weird effect. I think this looks better.


Fix router docker file

Seems when I raised the PR with a Dockerfile I had only checked the binary ran; since then I've tried to call our graph & uncovered the following issues fixed by this PR:

[x] Fix entrypoint was wrapped in shell, so args are not passed direct
[x] CA bundle wasn't available so TLS requests failed
[x] Drop RUST_BACKTRACE

@kamilkisiela @n1ru4l Any chance you could take a look at this PR? 🙏🏻
Currently, the container is unusable

Any chance this could be looked at? @kamilkisiela @n1ru4l
We've built this image to our own registry for now, but would be good to use an official one.

Thanks @rcrowe
Sorry for the delay on this one, we'll try to review and get this in soon :)

@kamilkisiela I think we can close this one, since it was already fixed?

https://github.com/kamilkisiela/graphql-hive/pull/972 not merged yet

Hi @rcrowe
Thank you for this PR, there was some more fixes needed to get this fully working, so @kamilkisiela created this PR: https://github.com/kamilkisiela/graphql-hive/pull/972
We are looking for feedback if you are interested in giving it a try. we plan to get this merged by next week.


Delete An Order API has no not found response

Describe the bug
Delete An Order API doesn't respond with 404_NOT_FOUND when the order is not in the database.
To Reproduce
Steps to reproduce the behavior:
Open the project in a container
Start service
Try deleting an unexisting order id
The result shown is 'Order has been Deleted!'
Observed behavior
The result shown is 'Order has been Deleted!'

This behavior is not required for DELETE order. Delete API will always return 204 NO CONTENT.


Update FastbootLocation service

📖 Description
Update FastBoot location service to ensure that path is returning a value even if there is no query/hash are present in the URL.
With the actual code, location.path returns an empty string even if the URL is localhost:4200/en.
🦀 Dispatch

#dispatch/ember

🦀 Requesting reviewers for this pull request:

@charlesdemers (contributor with 0 commits in the last 90 days and 117 commits overall)
@lewazo (reviewer for the ember stack)

🦀 Mentionning users for this pull request:

@JeremyAube (learner for the ember stack)


Add Median Absolute Deviation rules

This commit adds Median Absolute Deviation (MAD) calculation rules to the project. It introduces new entries in JSON, PHP, and YML schema examples, updates related tests and includes a new class for Median Absolute Deviation. The updated rules counter badge and documentation in README file reflect these additions.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.004%) to 94.953%

Totals

Change from base Build<PHONE_NUMBER>:
0.004%

Covered Lines:
1223

Relevant Lines:
1288

💛  - Coveralls


request.context['user'] = token_info.get('sub', token_info.get('uid')) - AttributeError: 'str' object has no attribute 'get'

Description
We have a vuejs frontend talking to a connexion-based REST API. We use jwt tokens. Sometimes, without any obvious trigger, we get the following exception:
File "venv/lib/python3.8/site-packages/flask/app.py", line 2464, in call return self.wsgi_app(environ, start_response)
File "venv/lib/python3.8/site-packages/flask/app.py", line 2450, in wsgi_app response = self.handle_exception(e)
File "venv/lib/python3.8/site-packages/flask/app.py", line 1867, in handle_exception reraise(exc_type, exc_value, tb)
File "venv/lib/python3.8/site-packages/flask/_compat.py", line 39, in reraise raise value
File "venv/lib/python3.8/site-packages/flask/app.py", line 2447, in wsgi_app response = self.full_dispatch_request()
File "venv/lib/python3.8/site-packages/flask/app.py", line 1952, in full_dispatch_request rv = self.handle_user_exception(e)
File "venv/lib/python3.8/site-packages/flask/app.py", line 1821, in handle_user_exception reraise(exc_type, exc_value, tb)
File "venv/lib/python3.8/site-packages/flask/_compat.py", line 39, in reraise raise value
File "venv/lib/python3.8/site-packages/flask/app.py", line 1950, in full_dispatch_request rv = self.dispatch_request()
File "venv/lib/python3.8/site-packages/flask/app.py", line 1936, in dispatch_request return self.view_functionsrule.endpoint
File "venv/lib/python3.8/site-packages/connexion/decorators/decorator.py", line 48, in wrapper response = function(request)
File "venv/lib/python3.8/site-packages/connexion/decorators/security.py", line 325, in wrapper request.context['user'] = token_info.get('sub', token_info.get('uid'))
AttributeError: 'str' object has no attribute 'get'
<IP_ADDRESS> - - [21/Jul/2020 07:13:34] "GET /v0.0.1/gateway/11 HTTP/1.0" 500 -

Expected behaviour
It works without exception.
Actual behaviour
A 500 error with the above stack trace.
Steps to reproduce
Using the frontend for some time (sorry, can't be more specific)
Additional info:
A possibly related issue may here.
Output of the commands:

python --version
3.8.0

pip show connexion | grep "^Version\:"
Version: 2.6.0

This may or my not apply to your situation, but I encountered this error when the function I specified for x-bearerInfoFunc returned something other than a dict.
Here is a sample adapted from the JWT example that throws AttributeError: 'bool' object has no attribute 'get' when you try to access /secret with a token (valid or invalid).
openapi.yaml
openapi: 3.0.0
info:
  title: JWT Example
  version: '1.0'
paths:
  /secret:
    get:
      summary: Return secret string
      operationId: app.get_secret
      responses:
        '200':
          description: secret response
          content:
            'text/plain':
              schema:
                type: string
      security:
      - jwt: ['secret']

components:
  securitySchemes:
    jwt:
      type: http
      scheme: bearer
      bearerFormat: JWT
      x-bearerInfoFunc: app.decode_token

app.py
import connexion

def decode_token(token):
    return True

def get_secret(user, token_info) -> str:
    return '''
    You are user_id {user} and the secret is 'wbevuec'.
    Decoded token claims: {token_info}.
    '''.format(user=user, token_info=token_info)

if __name__ == '__main__':
    app = connexion.FlaskApp(__name__)
    app.add_api('openapi.yaml')
    app.run(port=8080)

Thank you @Tsubashi , this was the hint that helped me.
My decode_token() function returned a string as part of the Exception handling (e.g. token expired).
Would be helpful for others to cover this in the docs imho.

Thanks for the report @gitttt @Tsubashi. We should clarify in the docs (currently the return type is only documented for Oauth2) and see if we can catch the exception to provide a better error message.

Hi I am facing the same issue. Would there be a fix  ?

Added to documentation in #1764


Unhandled rejection ReferenceError: merge is not defined

I try to use addFolder method of collection, and recieve the error.
I think the mistake may be on the line 57 of util.js.

Oops! the merge function used to be part of the client module. When I moved it to util I must have forgotten to update the recursive call. Will be fixed in the next update.

Never knew this was allowed http://stackoverflow.com/a/7065175
I'm at work now and no dev environment at home, so I hope this quick fix works.

Works fine for me :+1:


Repair and add

I hope to add these Arabic manga site.                        (1)https://team11x11.com                                (2)https://flixscans.com/webtoons/hoome                   (3)https://mangaflame.org                                     I hope the Swat and Azura manga will be fixed       (1)https://goldragon.me                                     (2)https://azoramoon.com

make separate issues for separate source requests or source issues


check that window.removeEventListener is a function

this was throwing an error for us, because window.removeEventListener was not defined for some reason.

What browser is window.removeEventListener not defined in?


Do not fail on startup in case of network error

Bot may be used in different setups. There may be no network or there may be telegram api error on startup - in this case bot will fail and will not start. This PR fixes this.

I don't see any issues with failing to start due to network problems: supervisor should take care of restarting the bot.
However I expect bot to fail sending notification in a way that prometheus would try to resend them. So I'm going to accept this.


Release version 0.3.1

Hi folks, it's the middle of the month again! :)
I looked back through git history since 0.3.0 branched, and it looks like the following are in master and not 0.3.0:

#359 (exit as soon as worker threads are done) and #239 (include est time remaining) via #316
#362 update mongo driver version to 3.0.3
#366 enforce checkstyle for mongo
#381 fix hdrhistogram recorder/logger initialization timing issue.
#389 use the container based infrastructure for Travis Builds

The things I'd like to make sure get out in a timely manner are #362 and #381. None of these changes indicate a need for "0.4.0".
What do folks think about a quick turn around for 0.3.1? Since it'd be a patch release, I'd be fine only needing to test bindings that are actually touched (i.e. mongo) and leaving everyone else's "tested" status as in the 0.3.0 release.

Barring additional feedback, I'm going to spin up on a 0.3.1 release this evening.

0.3.1 RC1 is available now.
Since this is a patch release, the only thing I'm concerned with verifying is the new driver used in the mongodb binding.
@allanbank got time to run this one through the MongoDB gauntlet? If not, could you post your test script and I'll take care of it?
I'd like to have things packaged and out the door early next week.

MongoDB looks good. Ran through the standard suite with version 3.0.5, 2.6.11, 2.4.14, 2.2.7, 2.0.9, and 1.8.5. Everything looks good except the return=1 values for Workload D which is #327.
I need to get more testing time in on the fix @tlopatic started in #364 so I feel comfortable merging it. (not for 0.3.1)
Rob.

awesome. thanks for checking things out so fast Rob. barring other issues, I'll run through a rat check and then push the release tomorrow.

Proposed release notes: https://gist.github.com/busbey/1680c0133761263e595a

Proposed release notes:
https://gist.github.com/busbey/1680c0133761263e595a

Looks good to me.

:+1:  0.3.1 Release Notes

My apologies. I went on vacation and didn't realize I had forgotten to actually push the release tag and artifacts. :/
The release is live now: https://github.com/brianfrankcooper/YCSB/releases/tag/0.3.1


Fix or suppress information lint warnings

🐛 Summary
The PowerShell linter in the workflow is reporting failed when "informational" severity level rules violated.
To reproduce
Steps to reproduce the behavior:

Run "Lint Check for PowerShell" workflow

Expected behavior
Expect to pass if no identified errors or warnings
Any helpful log output or screenshots

Add any screenshots of the problem here.

I tried to reproduce this bug, but when I ran Lint Check for PowerShell workflow and it didn't provide me any issues/errors. I think this bug is already fixed by James when he reworked the Github automations and shifted to MegaLinter.


Port CI configuration from ITKVkFFTBackend

There should be few, if any, changes required. We will have to enable CiRun -- I already enabled on the dashboard, but @tbirdso you should now have admin on this repository to make any additional changes.

Thanks @thewtex , I've copied over CI files and will debug as necessary.
Cirun was not enabled for ITKCLEsperanto on my cirun dashboard and runners are not launching even after enabling it, I think the missing step is to install the app to our Github repo. I've submitted a request through the Cirun dashboard, please let me know if it doesn't come through.

They seem to be running, but failing quickly with the following in the log:
{
    "creation_response": {
        "error": "'NoneType' object has no attribute 'get'"
    }
}

Interesting, I'm not getting any output on my cirun dashboard. Maybe try adding the access key that you previously mentioned?


Font compression

Since character image consist mostly of 0x00 and 0xff, it is easy to compress it to save flash memory. Small (10 or 12) font with only ASCII charset does not occupy much size, but large (20 or 24) fonts with multiple codepages (Russian, Greek, Chinese, etc) will occupy very much space.
I implemented modified version of RLE algorithm. It is fast, and it allows to unpack characters on-the-fly without significant speed loss.
Comparison with uncompressed fonts (only contents were compared without ELF headers):

Font
No
mRLE

font-UbuntuMonoR-10.c:
9256
8648

font-UbuntuMonoR-12.c:
11624
9832

font-UbuntuMonoR-16.c:
15336
12872

font-UbuntuMonoR-24.c:
29768
18024

font-UbuntuMonoR-40.c:
75272
28840

font-UbuntuMonoR-72.c:
230216
49960

Very nice!


Add theme

I have added a theme.

Install using npm i list-theme.
Add the information present in index.html in the theme's index.html
Deploy on a Heroku App.
Create a PR.
Add the deployed app link.
Take the credentials from me.
Deploy in my Heroku account.

@tapaswenipathak I would love to work on this

Sure, go for it!

So npm i list-theme
returns a 404 error can
https://registry.npmjs.org/list-theme
@tapaswenipathak

I didn't publish the code. Run npm install && npm link. You can put the code in the repository without installing anything as well.

Can I work on this issue, @tapaswenipathak?

On Fri, May 10, 2019 at 2:06 PM Parul<EMAIL_ADDRESS>wrote:

Can I work on this issue, @tapaswenipathak?

Sure!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

--
Tapasweni

Alright! Working on this one.
On Fri, 10 May 2019, 5:59 pm Tapasweni Pathak<EMAIL_ADDRESS>wrote:

On Fri, May 10, 2019 at 2:06 PM Parul<EMAIL_ADDRESS>wrote:

Can I work on this issue, @tapaswenipathak?

Sure!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

--
Tapasweni
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tapaswenipathak/Open-Source-Internships/issues/112#issuecomment-491271553,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG77SNTNSFUSFK7M5KWSXSTPUVTA3ANCNFSM4HK2QBCA
.

Alright! Working on this one.


Windows: Cannot update global npm version after using setup-node

Description:
This bug already happened in the past (#411), but appears to be happening again.
Up until now, updating the global npm version after setting up the node version using npm install -g npm worked on all operating systems without issues.
Now I'm receiving the following errors:

Log output
npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): EPERM: operation not permitted, lstat 'C:\npm\prefix\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli'
npm ERR! code EPERM
npm ERR! syscall rename
npm ERR! path C:\npm\prefix\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@npmcli
npm ERR! dest C:\npm\prefix\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, rename 'C:\npm\prefix\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@npmcli' -> 'C:\npm\prefix\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli'
npm ERR!  [OperationalError: EPERM: operation not permitted, rename 'C:\npm\prefix\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@npmcli' -> 'C:\npm\prefix\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli'] {
npm ERR!   cause: [Error: EPERM: operation not permitted, rename 'C:\npm\prefix\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@npmcli' -> 'C:\npm\prefix\node_modules\npm\node_modules\node-gyp\node_modules\@npmcli'] {
npm ERR!     errno: -4048,
npm ERR!     code: 'EPERM',
npm ERR!     syscall: 'rename',
npm ERR!     path: 'C:\\npm\\prefix\\node_modules\\npm\\node_modules\\.node-gyp.DELETE\\node_modules\\@npmcli',
npm ERR!     dest: 'C:\\npm\\prefix\\node_modules\\npm\\node_modules\\node-gyp\\node_modules\\@npmcli'
npm ERR!   },
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'rename',
npm ERR!   path: 'C:\\npm\\prefix\\node_modules\\npm\\node_modules\\.node-gyp.DELETE\\node_modules\\@npmcli',
npm ERR!   dest: 'C:\\npm\\prefix\\node_modules\\npm\\node_modules\\node-gyp\\node_modules\\@npmcli',
npm ERR!   parent: 'npm'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR!      C:\npm\cache_logs\2022-11-14T05_03_05_672Z-debug.log
Error: Process completed with exit code 1.

Action version:
Pinned at v3
Platform:

[ ] Ubuntu
[ ] macOS
[X] Windows

Runner type:

[X] Hosted
[ ] Self-hosted

Tools version:
Node.js 14, potentially also failing for other node versions.
Repro steps:
See failed job in public repo.
Expected behavior:
npm should install and update the global version correctly.
Actual behavior:
Updating the npm version fails.

Hello @peterjuras, thanks for your input. We are starting to investigate the problem.

Thanks! It might be related to the file permission changes with npm@9

@peterjuras it looks the problem is there's no pre-build @npmcli package of 9th version for node14 and node-gyp fails to build it from source code.
While i am looking for the proof of this hypothesis please try to skip the combination of node14/npm9 as a workaround if possible.

@peterjuras yes, the problem exists with the native node binary and does not depend on the action.
https://github.com/akv-demo/setup-node-test/actions/runs/3463429592/jobs/5783651246#step:2:24
The npm team should be addressed with the issue of installing npm9 with node 14 to solve.

I created a new issue in the npm cli repo: https://github.com/npm/cli/issues/5856

Hello @peterjuras. Could you please try to use this npm i -g npm@8 && npm i -g npm@latest command.

This is the right suggestion.  npm 6 has an issue installing some newer versions of npm in windows because of a bug in how it tries to shuffle directories around.  We had to work around this ourselves when developing 7: node images that shipped with npm 6 had to be leapfrogged from a lower version of 7 that npm 6 could install, and from there we could install the latest npm.
We used to have a pinned issue about this in npm 7, looks like we'll need another one to help folks updating from npm 6.  https://github.com/npm/cli/issues/5862 will be updated as we go along.

Hello @peterjuras , i am closing the issue because it does not relate to setup-node repo, but please feel free to reopen it or create another one in case if feel the problem still should solved by us.

Hello @peterjuras. Could you please try to use this npm i -g npm@8 && npm i -g npm@latest command.

This is the right suggestion. npm 6 has an issue installing some newer versions of npm in windows because of a bug in how it tries to shuffle directories around. We had to work around this ourselves when developing npm 7: node images that shipped with npm 6 had to be leapfrogged from a lower version of 7 that npm 6 could install, and from there we could install the latest npm.
We used to have a pinned issue about this in npm 7, looks like we'll need another one to help folks updating from npm 6. npm/cli#5862 will be updated as we go along.

Thanks, this worked for me 👍


How to make Full text search working?

Is it possible? For now I only have
All documents removed.
Indexing 92 titles

And so the index only contains cms.title objects.
How is it possible to index the djangocms_text_ckeditor plugin instances. I suspect it it supported in this app?

The index will actually contain all plugins on those pages. The "Indexing 92 titles" is an unfortunate way haystack reports succes. It's just called "titles" because the main Model in django-cms, representing a Page in a certain language is called Title.
See https://github.com/aldryn/aldryn-search/blob/master/aldryn_search/search_indexes.py#L51-53 for where the individual plugins on each Page are added to the index.


incorrect permissions analysis

The following is a valid Rust program (compiles without errors). Why doesn't the *n path have the write permission?

Fortunately, Aquascope is telling you the truth, that this program is not valid. Here's a playground link.
On line 3, n is a shared reference, meaning that memory behind the reference cannot be mutated. Aquascope indicates this by saying *n gains read (R) permission but neither write (W) nor own (O) permission. This leads to the permissions violation on line 4.
However, the interpreted program shows that it runs without error. That is, if Rust did allow the program to run it doesn't crash. For understanding references and borrowing please refer to Chapter 4 in The Rust Book Experiment.


updatedAt not a property of query as shown in documentation

updatedAt not a property of query as shown in the documentation:
https://github.com/tannerlinsley/react-query/blob/master/README.md#initial-data-from-cache

:tada: This issue has been resolved in version 1.5.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Stop using 'lib/emitter' and use an external library

it's implemented with the same interface here: https://github.com/medikoo/event-emitter

Also, it would be nice to use Backbone Events because it has .listenTo(Object, event, callback) and stopListeningTo(Object, [event]) methods, that allow to stop listening to a specific object in a much simpler way.

+1
I'm ashamed of that. The problem is that we can't import clases written in ES6 (Babel bug? Browserify bug? -- We have to do a little research here). So, in order to mantain the class Foo extends Emitter syntax, I had to get the module and import it locally.
I have doubts with the Backbone Events stuff. I think this implies to rewrite all the Views and I can't see what's the trade here. Are we having a serious problem here?

Neither Backbone Events nor AmpersandJS Events have a smooth way to be used with ES6 classes.

Not really, listenTo() It's mostly a hip dev-love stuff. It's more semantic, and useful when you want to stop listening several objects all at once.
Without listenTo:
B.on('sarasa', cb, A)
B.on('pepepe', cb, A)
C.on('sarasa', cb, A)

B.off(null, null, A)
C.off(null, null, A)

With listenTo:
A.listenTo(B, 'sarasa', cb)
A.listenTo(B, 'pepepe', cb)
A.listenTo(C, 'sarasa', cb)

A.stopListening()

Edit: Changed my recomendation from Backbone Events to AmpersandJS's

Still not seeing the trade. We are bundling a whole new library just to make code a little bit more readable, having to rewrite the 100% of the Views.
I think I'm missing something.
How would you rewrite the CommentsFilter class using AmpersandJS Events?
export default class CommentsFilter extends View {
  constructor () {
    super();
    this.refresh();
    super(template, { label: this.get().label, sorts: sorts });
  }

  /**
   * Switch on events
   *
   * @api public
   */

  switchOn () {
    bus.on('page:change', this.bound('switchOff'));
    this.bind('click', 'li a', 'onsortclick');
    this.on('change', this.bound('onsortchange'));
    user.on('load', this.bound('refresh'));
    let dropdownBtn = this.find('.btn');
    this.dropdown = new ToggleParent(dropdownBtn[0]);
  }

  switchOff () {
    bus.off('page:change', this.bound('switchOff'));
    user.off('loaded', this.bound('refresh'));
    if (this.dropdown) {
      this.dropdown.destroy();
      this.dropdown = null;
    }
  }

Bummer about babel, let's discuss it more later.
Yup, It's not that much gain. It would be:
  switchOn () {
    this.bind('click', 'li a', 'onsortclick');

    this.listenTo(bus, 'page:change', this.bound('switchOff'))
    this.listenTo(user, 'load', this.bound('refresh'))
    this.on('change', this.bound('onsortchange'))

    let dropdownBtn = this.find('.btn');
    this.dropdown = new ToggleParent(dropdownBtn[0]);
  }

  switchOff () {
    this.stopListening()
    if (this.dropdown) {
      this.dropdown.destroy();
      this.dropdown = null;
    }
  }

The really nice thing is that for every event we add on switchOn, we don't have to add it on switchOff. Avoids repetition.

It's not a solution, but at least we don't have to maintain Emitter:
import EventsPrototype from 'ampersand-events'

var Events = function(){}
Events.prototype = EventsPrototype

export default class Mirtha extends Events {
  insult () {
    this.trigger('insult')
  }
}

Here's how I tested it: https://github.com/mjlescano/test-es6-class-extension
Should also work with https://github.com/component/emitter this way (not tested):
import ComponentEmitter from 'component-emitter'

function Emitter(){}
ComponentEmmiter(Emitter)

export default class Mirtha extends Emitter {
  // ...
}

Mango/emitter worked with babel!

Install it
npm i Mango/emitter --save

Extend it

  import Emitter from 'emitter'
  export default class Piringulete extends Emitter {
    ...
  }

Profit it (?)

  let pirin = new Piringuelete;
  pirin.on('fired', function() { console.log('Wow. Such event. So profit.') })
  pirin.emit('fired') // Wow. Such event. So profit.