Specifying aspect with only width or height does not initialize the cropper area

Your documentation specifies that when using aspect to only specify width OR height (or neither). Currently, when passing in the following crop, no cropper area is initialized but it does draw the cropper with aspect appropriately. If I pass both a height and a width than the cropper area is displayed but then the aspect isn't necessarily correct (based on the image dimensions) since width and height are percentages.
crop: {
  aspect: 1,
  width: 50,
  x: 0,
  y: 0
}

If I remove aspect and specify width, height, x and y than the cropper area initializes correctly. This is working as expected.
We used to be able to display an initial cropper area with aspect ratio but this doesn't seem to be the case anymore.

Hi, can you clarify what you mean by this bit "no cropper area is initialized but it does draw the cropper with aspect appropriately."?
If you take a look over here it does draw an aspect on the image you load in: https://codesandbox.io/s/72py4jlll6

Your example does appear to load the image with the crop area initially on it. I had run a basic test specifying only two props (src and crop) where the src was hard coded as a string and the crop similar to the above with aspect ratio and it did not load initially with the crop area; I had to drag to crop.

Hm are you able to replicate with this? https://codesandbox.io/s/k3233k2ov3

I dug into it further and noticed that I was not using the latest 6.x.x version. After updating, I was able to track down the bugs on our end. We have an avatar component that utilizes a cropper component which wraps this cropper. We had a few issues: one was that we were declaring with and height with the aspect which caused the aspect to not be the expected value and we did not have x and y declared which for some reason caused the cropper area to not be movable. Then within the cropper code, we were calling getPixelCrop directly within onImageLoaded and it was returning NaN when our crops had aspect and only one dimension specified. I saw from your example that pixelCrop is passed into onImageLoaded, so removed that direct call. The final thing that was causing the preview to not have a cropper initially was because we were calling onChange(crop, pixelCrop) again from onImageLoaded and it seemed to be resetting the crop width/height with the initial values again. I'm not sure why the initial test I ran directly using ReactCrop with a static src, hardcoded crop, and empty change function did not render properly with the initial crop but it was likely something I did on my end. Thanks for your time!

Ok glad you fixed it! I would like to automatically fix invalid crops in the future even if both width and height are specified, I wrote the code tonight but just need to test it carefully as it's quite easy to cause an infinite loop.


Cpptools configuration issue after building

I'm not sure if I should open a new issue, but I also have this issue. It happens randomly and there's nothing special in the C++ extension logs. IntelliSense works perfectly, but then after triggering a build by pressing F7, it sometimes starts to fail and I get the "#include errors detected" error. Resetting the IntelliSense database works sometimes, and restarting extension host seems to fix it 100% of the time.
Originally posted by @grigorig in https://github.com/microsoft/vscode-cmake-tools/issues/1563#issuecomment-762669090

Interesting scenario, I didn't see this happen before. Let's start with the logs, even if you said nothing interesting seems to be recorded there.
Set both cmake.loggingLevel and C_Cpp.loggingLevel to "Debug".
Then try to reproduce your scenario. When you see the red squiggles you can copy the output channels of the CMake and Cpp Tools extensions and share within this GitHub issue.

Interesting scenario, I didn't see this happen before. Let's start with the logs, even if you said nothing interesting seems to be recorded there.
Set both cmake.loggingLevel and C_Cpp.loggingLevel to "Debug".
Then try to reproduce your scenario. When you see the red squiggles you can copy the output channels of the CMake and Cpp Tools extensions and share within this GitHub issue.

Happens to me, too. Didn't manage to reproduce this reliably, and couldn't find something interresting in the logs when it happened, neither.
Currently trying if using compile_commands.json directly is a reliable workaround for now.

Happens to me, too. Didn't manage to reproduce this reliably, and couldn't find something interresting in the logs when it happened, neither.
Currently trying if using compile_commands.json directly is a reliable workaround for now.

I switch to using compile_commands.json directly, too, and this seems to work reliably for me. I'll try to reproduce the problem nonetheless.

I switch to using compile_commands.json directly, too, and this seems to work reliably for me. I'll try to reproduce the problem nonetheless.

Thank you for helping us fix this by providing a repro. Ideally you wouldn't use compile_commands.json, but CMake Tools provider.

Thank you for helping us fix this by providing a repro. Ideally you wouldn't use compile_commands.json, but CMake Tools provider.

OK, I did quite a bit of testing. The problem still seems to be completely random. Is it some kind of race condition perhaps? Any kind of build command has a good chance of triggering the problem. Build, clean build, clean, etc, doesn't seem to matter.
Here's what I observed:

When everything works right, I see a message "Custom configurations received:" in the C/C++ log for a given file, which then lists a JSON build configuration that includes all the right include paths, defines, and so on extracted from CMake.
When stuff breaks, this doesn't happen. It looks CMake Tools fails to send the right information to the C/C++ extension.
When stuff breaks, I only see "sending compilation args for /path/to/bla.cpp". The configuration listed after that doesn't include the custom configuration (like include paths etc.) from CMake at all.
Maybe an IntelliSense shutdown is involved. Before the problem occurs, I see "Shutting down IntelliSense server: /path/to/bla.cpp" in the logs, but I'm not sure if that is consistent.
It looks like the file needs to be active at some point while the build command is running to trigger the problem. Interacting with the file (scrolling seems to be enough) might raise the chance to trigger the problem.

Hope that helps.

OK, I did quite a bit of testing. The problem still seems to be completely random. Is it some kind of race condition perhaps? Any kind of build command has a good chance of triggering the problem. Build, clean build, clean, etc, doesn't seem to matter.
Here's what I observed:

When everything works right, I see a message "Custom configurations received:" in the C/C++ log for a given file, which then lists a JSON build configuration that includes all the right include paths, defines, and so on extracted from CMake.
When stuff breaks, this doesn't happen. It looks CMake Tools fails to send the right information to the C/C++ extension.
When stuff breaks, I only see "sending compilation args for /path/to/bla.cpp". The configuration listed after that doesn't include the custom configuration (like include paths etc.) from CMake at all.
Maybe an IntelliSense shutdown is involved. Before the problem occurs, I see "Shutting down IntelliSense server: /path/to/bla.cpp" in the logs, but I'm not sure if that is consistent.
It looks like the file needs to be active at some point while the build command is running to trigger the problem. Interacting with the file (scrolling seems to be enough) might raise the chance to trigger the problem.

Hope that helps.

OK, here's a hopefully correct reduced trace of what I can see in the logs:
Checking for syntax errors: file:///path/to/bla.cpp
Queueing IntelliSense update for files in translation unit of: /path/to/bla.cpp
cpptools/finishUpdateSquiggles
Error squiggle count: 0
Update IntelliSense time (sec): 0.255
[...]
[Build event triggered]
[...]
cpptools/didChangeCustomConfiguration
Attempting to get defaults from C++ compiler in "compilerPath" property: '/usr/bin/clang++-11'
sending compilation args for /path/to/bla.cpp
  include: /usr/include/c++/10
  include: /usr/include/c++/10/x86_64-redhat-linux
  include: /usr/include/c++/10/backward
  include: /usr/local/include
  include: /usr/lib64/clang/11.0.0/include
  include: /usr/include
[...]
[notably, project-specific include paths are missing!]
[...]
Checking for syntax errors: file:///path/to/bla.cpp
Queueing IntelliSense update for files in translation unit of: /path/to/bla.cpp
cpptools/queryTranslationUnitSource: file:///path/to/bla.cpp (id: 1583)
cpptools/finishUpdateSquiggles
Error squiggle count: 22
Error squiggles will be disabled in: file:///path/to/bla.cpp
Update IntelliSense time (sec): 7.104

OK, here's a hopefully correct reduced trace of what I can see in the logs:
Checking for syntax errors: file:///path/to/bla.cpp
Queueing IntelliSense update for files in translation unit of: /path/to/bla.cpp
cpptools/finishUpdateSquiggles
Error squiggle count: 0
Update IntelliSense time (sec): 0.255
[...]
[Build event triggered]
[...]
cpptools/didChangeCustomConfiguration
Attempting to get defaults from C++ compiler in "compilerPath" property: '/usr/bin/clang++-11'
sending compilation args for /path/to/bla.cpp
  include: /usr/include/c++/10
  include: /usr/include/c++/10/x86_64-redhat-linux
  include: /usr/include/c++/10/backward
  include: /usr/local/include
  include: /usr/lib64/clang/11.0.0/include
  include: /usr/include
[...]
[notably, project-specific include paths are missing!]
[...]
Checking for syntax errors: file:///path/to/bla.cpp
Queueing IntelliSense update for files in translation unit of: /path/to/bla.cpp
cpptools/queryTranslationUnitSource: file:///path/to/bla.cpp (id: 1583)
cpptools/finishUpdateSquiggles
Error squiggle count: 22
Error squiggles will be disabled in: file:///path/to/bla.cpp
Update IntelliSense time (sec): 7.104

I didn't try to reproduce this again this week but in general, we never saw this, it would help if you can send us a repro, maybe some special situation triggers it. If the trigger is in your system, we'll have to work with you to debug on your side. But it's worth to try a project repro first, in case the trigger is in the project.

I didn't try to reproduce this again this week but in general, we never saw this, it would help if you can send us a repro, maybe some special situation triggers it. If the trigger is in your system, we'll have to work with you to debug on your side. But it's worth to try a project repro first, in case the trigger is in the project.

In the cpptools log, any of the cpptools/* events that have the word "custom" in them would be relevant to us.  It would be good to know whether cpptools is clearing the configuration already sent by CMake Tools.

In the cpptools log, any of the cpptools/* events that have the word "custom" in them would be relevant to us.  It would be good to know whether cpptools is clearing the configuration already sent by CMake Tools.

I have the same problem, all information aren't set to cpptools. In fact my problem is only in the headers, and I noticed that the cmake configuration isn't provided for the headers files. It looks like this :
envoi des arguments de compilation pour D:\DOCUMENTS\PROG PERSO\REPRO BUG CPPTOOLS + CMAKETOOLS\SRC\SUBFOLDER1\UTILS3.H
  inclusion : C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\ENTERPRISE\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  inclusion : C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\ENTERPRISE\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  inclusion : C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\UM
  inclusion : C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\UCRT
  inclusion : C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\SHARED
  inclusion : C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\WINRT
  inclusion : C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\CPPWINRT
  définition : _DEBUG
  définition : UNICODE
  définition : _UNICODE
  autre : --header_only_fallback
  stdver: ms_c++17
  intelliSenseMode: windows-msvc-x64

while in a source file, in the same project than the header file, it looks like this :
envoi des arguments de compilation pour D:\DOCUMENTS\PROG PERSO\REPRO BUG CPPTOOLS + CMAKETOOLS\SRC\MAIN.CPP
  inclusion : D:\DOCUMENTS\PROG PERSO\REPRO BUG CPPTOOLS + CMAKETOOLS\BUILD\CMAKE_UTILS
  inclusion : C:\PROGRAM FILES\LLVM\LIB\CLANG\11.0.1\INCLUDE
  inclusion : C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\ENTERPRISE\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  inclusion : C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\ENTERPRISE\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  inclusion : C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\UCRT
  inclusion : C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\SHARED
  inclusion : C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\UM
  inclusion : C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\WINRT
  définition : __llvm__=1
  définition : __clang__=1
  définition : __clang_major__=11
  définition : __clang_minor__=0
  définition : __clang_patchlevel__=1
  définition : __clang_version__="11.0.1 "
  [...]
  définition : HELLO <- define added manually in cmakelists.txt
  définition : _DEBUG
  définition : _DLL
  définition : _MT
  définition : _DEBUG
  définition : _DLL
  définition : _MT
  autre : --ms_extensions
  autre : --clang
  autre : --clang_version=110001
  stdver: c++17
  intelliSenseMode: windows-clang-x64

I configured cmake tool to run with clang. And in the config given to the header file, it gives the includes of msvc instead, with no defines made by cmake.

@BluTree the issue you are likely seeing is that you didn't add your header files to your CMakeLists.txt, so CMake doesn't report them as having their own configuration.  CppTools likely asked for a configuration, but CMake Tools didn't have one available so CppTools used the default configuration.

@grigorig , @Torgee , do you happen to reproduce this on a project that is already open source or which can be easily shared on GitHub? It would help us find the root cause faster.

Unfortunately, I'm only working with this on a proprietary project right now. It's a few million lines c++ and configures about 60s and builds 20min, so makes it a little hard to parse any logs - even if I would have more time to look into it ...
C++17 with vs2019 and ninja.
All I can say for now is:

setup is a bit weird, as the CmakeList.txt is not at the toplevel of the project
I'm using some "empty" workspacefolders where I only specify the cmake build path (this alows me to switch the "active folder" for different kits/variants)
I'm currenlty using the workaround with compile_commands, which is "usable" for me
cpp_tools still crashes from time to time, reloading vscode and reconfiguring is a workaround
Even without re-builing, it's often failing to find headers after clean configure (if not using compile_commands)

I'll see if I can check whether I also have this issue on linux with the same project - this will take a few days, tho

Same here, I don't have any OSS project that is affected, sorry.

I have an OSS project which (I believe) exhibits this problem reliably. I've been unable to produce a minimum code sample, but at the very least you can reproduce the issue by configuring this project in VSCode, then opening Engine/include/Enterprise/Graphics.h directly.
Here's what I've been able to determine about the issue:

The issue occurs sometimes when opening header files before opening a source file that includes them.

In my experience, it most often occurs with header files that are shared between multiple targets.

Some headers only exhibit the issue sporadically, but others exhibit it consistently.
After the issue occurs, opening a CPP file that includes the affected header temporarily resolves it.
Whenever the issue occurs, all #include statements in the header are affected except for standard headers.
Including the headers in the targets' source lists does not affect the issue.
I've observed this issue using the MSVC, Clang for MSVC, and AppleClang kits (both Mac and PC).

Here's the C/C++ debug diagnostics when an affected file is opened:

(diagnostics)

-------- Diagnostics - 8/31/2022, 1:26:16 PM
Version: 1.12.3
Current Configuration:
{
    "name": "Win32",
    "includePath": [
        "${workspaceFolder}/Engine/include",
        "${workspaceFolder}/Engine/vendor/CTSpookyHash/include",
        "${workspaceFolder}/Engine/vendor/cxx-prettyprint",
        "${workspaceFolder}/Engine/vendor/Glad/include",
        "${workspaceFolder}/Engine/vendor/spdlog/include",
        "${workspaceFolder}/Engine/vendor/stb_image/include",
        "${workspaceFolder}/Engine/vendor/glm",
        "${workspaceFolder}/Engine/vendor/yaml-cpp/include",
        "${workspaceFolder}/Engine/vendor/imgui"
    ],
    "defines": [
        "_DEBUG",
        "EP_CONFIG_DEBUG",
        "EP_EDITOR",
        "_USE_MATH_DEFINES",
        "UNICODE",
        "_UNICODE",
        "NOMINMAX",
        "GLAD_GLAPI_EXPORT",
        "GLM_FORCE_LEFT_HANDED",
        "YAML_CPP_STATIC_DEFINE",
        "HC_RELOADING_ON",
        "EP_BUILD_CORE",
        "GLAD_GLAPI_EXPORT_BUILD"
    ],
    "windowsSdkVersion": "10.0.19041.0",
    "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe",
    "cStandard": "c17",
    "cppStandard": "c++17",
    "compileCommands": "${workspaceFolder}/build/compile_commands.json",
    "configurationProvider": "ms-vscode.cmake-tools",
    "compilerPathIsExplicit": true,
    "cStandardIsExplicit": true,
    "cppStandardIsExplicit": true,
    "intelliSenseModeIsExplicit": false,
    "mergeConfigurations": false,
    "browse": {
        "path": [
            "${workspaceFolder}/Engine/include",
            "${workspaceFolder}/Engine/vendor/CTSpookyHash/include",
            "${workspaceFolder}/Engine/vendor/cxx-prettyprint",
            "${workspaceFolder}/Engine/vendor/Glad/include",
            "${workspaceFolder}/Engine/vendor/spdlog/include",
            "${workspaceFolder}/Engine/vendor/stb_image/include",
            "${workspaceFolder}/Engine/vendor/glm",
            "${workspaceFolder}/Engine/vendor/yaml-cpp/include",
            "${workspaceFolder}/Engine/vendor/imgui",
            "${workspaceFolder}"
        ],
        "limitSymbolsToIncludedHeaders": true
    }
}
Custom browse configuration:
{
    "browsePath": [
        "e:/software/enterprise/editor/src",
        "e:/software/enterprise/engine/include",
        "e:/software/enterprise/engine/vendor/ctspookyhash/include",
        "e:/software/enterprise/engine/vendor/cxx-prettyprint",
        "e:/software/enterprise/engine/vendor/glad/include",
        "e:/software/enterprise/engine/vendor/spdlog/include",
        "e:/software/enterprise/engine/vendor/stb_image/include",
        "e:/software/enterprise/engine/vendor/glm",
        "e:/software/enterprise/engine/vendor/imgui",
        "e:/software/enterprise/engine/vendor/hotconsts/include",
        "e:/software/enterprise/engine/vendor/yaml-cpp/include",
        "e:/software/enterprise/editor/vendor/nativefiledialog/src/include",
        "e:/software/enterprise/editor/src/application",
        "e:/software/enterprise/editor/src/window",
        "e:/software/enterprise/editor/src/file",
        "e:/software/enterprise/editor/src/views",
        "e:/software/enterprise/editor/src/layouts",
        "e:/software/enterprise/editor/resources",
        "e:/software/enterprise/editor/content",
        "e:/software/enterprise/editor/content/licenses",
        "e:/software/enterprise/engine/src",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen",
        "e:/software/enterprise/build/engine/vendor/freetype/include",
        "e:/software/enterprise/engine/vendor/freetype/include",
        "e:/software/enterprise/build/engine/cmakefiles/engine_dyn.dir",
        "e:/software/enterprise/engine/src/core",
        "e:/software/enterprise/engine/src/application",
        "e:/software/enterprise/engine/src/file",
        "e:/software/enterprise/engine/src/graphics",
        "e:/software/enterprise/engine/src/systems",
        "e:/software/enterprise/engine/src/systems/renderer2d",
        "e:/software/enterprise/engine/src/editor",
        "e:/software/enterprise/engine/src/time",
        "e:/software/enterprise/engine/src/input",
        "e:/software/enterprise/engine/vendor/ctspookyhash/src",
        "e:/software/enterprise/engine/vendor/stb_image/src",
        "e:/software/enterprise/engine/vendor/imgui/backends",
        "e:/software/enterprise/engine/vendor/glad/src",
        "e:/software/enterprise/engine/vendor/ctspookyhash/include/ctspookyhash",
        "e:/software/enterprise/engine/vendor/glad/include/glad",
        "e:/software/enterprise/engine/vendor/glad/include/khr",
        "e:/software/enterprise/build/engine/cmakefiles/engine_dyn.dir/debug",
        "e:/software/enterprise/build/engine/cmakefiles/engine_dyn.dir/dev",
        "e:/software/enterprise/build/engine/cmakefiles/engine_dyn.dir/release",
        "e:/software/enterprise/build/engine/cmakefiles/engine_lib.dir",
        "e:/software/enterprise/build/engine/cmakefiles/engine_lib.dir/debug",
        "e:/software/enterprise/build/engine/cmakefiles/engine_lib.dir/dev",
        "e:/software/enterprise/build/engine/cmakefiles/engine_lib.dir/release",
        "e:/software/enterprise/launcher/src",
        "e:/software/enterprise/testgame/src",
        "e:/software/enterprise/testgame/resources",
        "e:/software/enterprise/testgame/content",
        "e:/software/enterprise/engine/vendor/hotconsts/src",
        "e:/software/enterprise/engine/vendor/hotconsts/include/hotconsts",
        "e:/software/enterprise/build/engine/vendor/freetype/include/freetype/config",
        "e:/software/enterprise/engine/vendor/freetype/src/autofit",
        "e:/software/enterprise/engine/vendor/freetype/src/base",
        "e:/software/enterprise/engine/vendor/freetype/src/bdf",
        "e:/software/enterprise/engine/vendor/freetype/src/bzip2",
        "e:/software/enterprise/engine/vendor/freetype/src/cache",
        "e:/software/enterprise/engine/vendor/freetype/src/cff",
        "e:/software/enterprise/engine/vendor/freetype/src/cid",
        "e:/software/enterprise/engine/vendor/freetype/src/gzip",
        "e:/software/enterprise/engine/vendor/freetype/src/lzw",
        "e:/software/enterprise/engine/vendor/freetype/src/pcf",
        "e:/software/enterprise/engine/vendor/freetype/src/pfr",
        "e:/software/enterprise/engine/vendor/freetype/src/psaux",
        "e:/software/enterprise/engine/vendor/freetype/src/pshinter",
        "e:/software/enterprise/engine/vendor/freetype/src/psnames",
        "e:/software/enterprise/engine/vendor/freetype/src/raster",
        "e:/software/enterprise/engine/vendor/freetype/src/sdf",
        "e:/software/enterprise/engine/vendor/freetype/src/sfnt",
        "e:/software/enterprise/engine/vendor/freetype/src/smooth",
        "e:/software/enterprise/engine/vendor/freetype/src/svg",
        "e:/software/enterprise/engine/vendor/freetype/src/truetype",
        "e:/software/enterprise/engine/vendor/freetype/src/type1",
        "e:/software/enterprise/engine/vendor/freetype/src/type42",
        "e:/software/enterprise/engine/vendor/freetype/src/winfonts",
        "e:/software/enterprise/engine/vendor/freetype/builds/windows",
        "e:/software/enterprise/engine/vendor/freetype/include/freetype",
        "e:/software/enterprise/engine/vendor/freetype/include/freetype/config",
        "e:/software/enterprise/engine/vendor/freetype/include/freetype/internal",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen/include",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/artery-font-format",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdf-atlas-gen",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen/core",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen/ext",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen/lib",
        "e:/software/enterprise/engine/vendor/yaml-cpp/src",
        "e:/software/enterprise/engine/vendor/yaml-cpp/src/contrib",
        "e:/software/enterprise/editor/vendor/nativefiledialog/src"
    ],
    "compilerPath": "c:/program files (x86)/microsoft visual studio/2019/community/vc/tools/llvm/x64/bin/clang.exe",
    "compilerArgs": [],
    "compilerFragments": [
        "-g -Xclang -gcodeview -O0 -D_DEBUG -D_DLL -D_MT -Xclang --dependent-lib=msvcrtd",
        "-g -Xclang -gcodeview -O0 -D_DEBUG -D_DLL -D_MT -Xclang --dependent-lib=msvcrtd"
    ]
}
Translation Unit Mappings:
[ E:\Software\Enterprise\Engine\include\Enterprise\Graphics.h ]:
    E:\Software\Enterprise\Engine\include\Enterprise\Graphics.h
Translation Unit Configurations:
[ E:\Software\Enterprise\Engine\include\Enterprise\Graphics.h ]:
    Process ID: 17052
    Memory Usage: 12 MB
    Compiler Path: c:/program files (x86)/microsoft visual studio/2019/community/vc/tools/llvm/x64/bin/clang.exe
    Includes:
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\LLVM\X64\LIB\CLANG\12.0.0\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.29.30133\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.29.30133\ATLMFC\INCLUDE
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\UCRT
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\SHARED
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\UM
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\WINRT
    Standard Version: c++17
    IntelliSense Mode: windows-clang-x64
    Other Flags:
        --clang
        --clang_version=120000
        --ms_compatibility
        --header_only_fallback
Total Memory Usage: 12 MB
Browse Paths from compile_commands.json, from workspace folder: E:\Software\Enterprise
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_DYN.DIR
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_DYN.DIR\DEBUG
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_DYN.DIR\DEV
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_DYN.DIR\RELEASE
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_LIB.DIR
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_LIB.DIR\DEBUG
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_LIB.DIR\DEV
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_LIB.DIR\RELEASE
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\VENDOR\FREETYPE\INCLUDE
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\VENDOR\FREETYPE\INCLUDE\FREETYPE\CONFIG
    E:\SOFTWARE\ENTERPRISE\EDITOR\CONTENT
    E:\SOFTWARE\ENTERPRISE\EDITOR\CONTENT\LICENSES
    E:\SOFTWARE\ENTERPRISE\EDITOR\RESOURCES
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\APPLICATION
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\FILE
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\LAYOUTS
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\VIEWS
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\WINDOW
    E:\SOFTWARE\ENTERPRISE\EDITOR\VENDOR\NATIVEFILEDIALOG\SRC
    E:\SOFTWARE\ENTERPRISE\EDITOR\VENDOR\NATIVEFILEDIALOG\SRC\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\APPLICATION
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\CORE
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\EDITOR
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\FILE
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\GRAPHICS
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\INPUT
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\SYSTEMS
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\SYSTEMS\RENDERER2D
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\TIME
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CTSPOOKYHASH\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CTSPOOKYHASH\INCLUDE\CTSPOOKYHASH
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CTSPOOKYHASH\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CXX-PRETTYPRINT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\BUILDS\WINDOWS
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\INCLUDE\FREETYPE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\INCLUDE\FREETYPE\CONFIG
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\INCLUDE\FREETYPE\INTERNAL
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\AUTOFIT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\BASE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\BDF
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\BZIP2
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\CACHE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\CFF
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\CID
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\GZIP
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\LZW
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PCF
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PFR
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PSAUX
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PSHINTER
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PSNAMES
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\RASTER
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\SDF
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\SFNT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\SMOOTH
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\SVG
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\TRUETYPE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\TYPE1
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\TYPE42
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\WINFONTS
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLAD\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLAD\INCLUDE\GLAD
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLAD\INCLUDE\KHR
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLAD\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLM
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\HOTCONSTS\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\HOTCONSTS\INCLUDE\HOTCONSTS
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\HOTCONSTS\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\IMGUI
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\IMGUI\BACKENDS
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\ARTERY-FONT-FORMAT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDF-ATLAS-GEN
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN\CORE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN\EXT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN\LIB
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\SPDLOG\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\STB_IMAGE\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\STB_IMAGE\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\YAML-CPP\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\YAML-CPP\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\YAML-CPP\SRC\CONTRIB
    E:\SOFTWARE\ENTERPRISE\LAUNCHER\SRC
    E:\SOFTWARE\ENTERPRISE\TESTGAME\CONTENT
    E:\SOFTWARE\ENTERPRISE\TESTGAME\RESOURCES
    E:\SOFTWARE\ENTERPRISE\TESTGAME\SRC
------- Workspace parsing diagnostics -------
Number of files discovered (not excluded): 7341

Here's the diagnostics after opening a CPP file that includes the affected header (when the issue goes away)

(diagnostics)

-------- Diagnostics - 8/31/2022, 1:33:02 PM
Version: 1.12.3
Current Configuration:
{
    "name": "Win32",
    "includePath": [
        "${workspaceFolder}/Engine/include",
        "${workspaceFolder}/Engine/vendor/CTSpookyHash/include",
        "${workspaceFolder}/Engine/vendor/cxx-prettyprint",
        "${workspaceFolder}/Engine/vendor/Glad/include",
        "${workspaceFolder}/Engine/vendor/spdlog/include",
        "${workspaceFolder}/Engine/vendor/stb_image/include",
        "${workspaceFolder}/Engine/vendor/glm",
        "${workspaceFolder}/Engine/vendor/yaml-cpp/include",
        "${workspaceFolder}/Engine/vendor/imgui"
    ],
    "defines": [
        "_DEBUG",
        "EP_CONFIG_DEBUG",
        "EP_EDITOR",
        "_USE_MATH_DEFINES",
        "UNICODE",
        "_UNICODE",
        "NOMINMAX",
        "GLAD_GLAPI_EXPORT",
        "GLM_FORCE_LEFT_HANDED",
        "YAML_CPP_STATIC_DEFINE",
        "HC_RELOADING_ON",
        "EP_BUILD_CORE",
        "GLAD_GLAPI_EXPORT_BUILD"
    ],
    "windowsSdkVersion": "10.0.19041.0",
    "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe",
    "cStandard": "c17",
    "cppStandard": "c++17",
    "compileCommands": "${workspaceFolder}/build/compile_commands.json",
    "configurationProvider": "ms-vscode.cmake-tools",
    "compilerPathIsExplicit": true,
    "cStandardIsExplicit": true,
    "cppStandardIsExplicit": true,
    "intelliSenseModeIsExplicit": false,
    "mergeConfigurations": false,
    "browse": {
        "path": [
            "${workspaceFolder}/Engine/include",
            "${workspaceFolder}/Engine/vendor/CTSpookyHash/include",
            "${workspaceFolder}/Engine/vendor/cxx-prettyprint",
            "${workspaceFolder}/Engine/vendor/Glad/include",
            "${workspaceFolder}/Engine/vendor/spdlog/include",
            "${workspaceFolder}/Engine/vendor/stb_image/include",
            "${workspaceFolder}/Engine/vendor/glm",
            "${workspaceFolder}/Engine/vendor/yaml-cpp/include",
            "${workspaceFolder}/Engine/vendor/imgui",
            "${workspaceFolder}"
        ],
        "limitSymbolsToIncludedHeaders": true
    }
}
Custom browse configuration:
{
    "browsePath": [
        "e:/software/enterprise/editor/src",
        "e:/software/enterprise/engine/include",
        "e:/software/enterprise/engine/vendor/ctspookyhash/include",
        "e:/software/enterprise/engine/vendor/cxx-prettyprint",
        "e:/software/enterprise/engine/vendor/glad/include",
        "e:/software/enterprise/engine/vendor/spdlog/include",
        "e:/software/enterprise/engine/vendor/stb_image/include",
        "e:/software/enterprise/engine/vendor/glm",
        "e:/software/enterprise/engine/vendor/imgui",
        "e:/software/enterprise/engine/vendor/hotconsts/include",
        "e:/software/enterprise/engine/vendor/yaml-cpp/include",
        "e:/software/enterprise/editor/vendor/nativefiledialog/src/include",
        "e:/software/enterprise/editor/src/application",
        "e:/software/enterprise/editor/src/window",
        "e:/software/enterprise/editor/src/file",
        "e:/software/enterprise/editor/src/views",
        "e:/software/enterprise/editor/src/layouts",
        "e:/software/enterprise/editor/resources",
        "e:/software/enterprise/editor/content",
        "e:/software/enterprise/editor/content/licenses",
        "e:/software/enterprise/engine/src",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen",
        "e:/software/enterprise/build/engine/vendor/freetype/include",
        "e:/software/enterprise/engine/vendor/freetype/include",
        "e:/software/enterprise/build/engine/cmakefiles/engine_dyn.dir",
        "e:/software/enterprise/engine/src/core",
        "e:/software/enterprise/engine/src/application",
        "e:/software/enterprise/engine/src/file",
        "e:/software/enterprise/engine/src/graphics",
        "e:/software/enterprise/engine/src/systems",
        "e:/software/enterprise/engine/src/systems/renderer2d",
        "e:/software/enterprise/engine/src/editor",
        "e:/software/enterprise/engine/src/time",
        "e:/software/enterprise/engine/src/input",
        "e:/software/enterprise/engine/vendor/ctspookyhash/src",
        "e:/software/enterprise/engine/vendor/stb_image/src",
        "e:/software/enterprise/engine/vendor/imgui/backends",
        "e:/software/enterprise/engine/vendor/glad/src",
        "e:/software/enterprise/engine/vendor/ctspookyhash/include/ctspookyhash",
        "e:/software/enterprise/engine/vendor/glad/include/glad",
        "e:/software/enterprise/engine/vendor/glad/include/khr",
        "e:/software/enterprise/build/engine/cmakefiles/engine_dyn.dir/debug",
        "e:/software/enterprise/build/engine/cmakefiles/engine_dyn.dir/dev",
        "e:/software/enterprise/build/engine/cmakefiles/engine_dyn.dir/release",
        "e:/software/enterprise/build/engine/cmakefiles/engine_lib.dir",
        "e:/software/enterprise/build/engine/cmakefiles/engine_lib.dir/debug",
        "e:/software/enterprise/build/engine/cmakefiles/engine_lib.dir/dev",
        "e:/software/enterprise/build/engine/cmakefiles/engine_lib.dir/release",
        "e:/software/enterprise/launcher/src",
        "e:/software/enterprise/testgame/src",
        "e:/software/enterprise/testgame/resources",
        "e:/software/enterprise/testgame/content",
        "e:/software/enterprise/engine/vendor/hotconsts/src",
        "e:/software/enterprise/engine/vendor/hotconsts/include/hotconsts",
        "e:/software/enterprise/build/engine/vendor/freetype/include/freetype/config",
        "e:/software/enterprise/engine/vendor/freetype/src/autofit",
        "e:/software/enterprise/engine/vendor/freetype/src/base",
        "e:/software/enterprise/engine/vendor/freetype/src/bdf",
        "e:/software/enterprise/engine/vendor/freetype/src/bzip2",
        "e:/software/enterprise/engine/vendor/freetype/src/cache",
        "e:/software/enterprise/engine/vendor/freetype/src/cff",
        "e:/software/enterprise/engine/vendor/freetype/src/cid",
        "e:/software/enterprise/engine/vendor/freetype/src/gzip",
        "e:/software/enterprise/engine/vendor/freetype/src/lzw",
        "e:/software/enterprise/engine/vendor/freetype/src/pcf",
        "e:/software/enterprise/engine/vendor/freetype/src/pfr",
        "e:/software/enterprise/engine/vendor/freetype/src/psaux",
        "e:/software/enterprise/engine/vendor/freetype/src/pshinter",
        "e:/software/enterprise/engine/vendor/freetype/src/psnames",
        "e:/software/enterprise/engine/vendor/freetype/src/raster",
        "e:/software/enterprise/engine/vendor/freetype/src/sdf",
        "e:/software/enterprise/engine/vendor/freetype/src/sfnt",
        "e:/software/enterprise/engine/vendor/freetype/src/smooth",
        "e:/software/enterprise/engine/vendor/freetype/src/svg",
        "e:/software/enterprise/engine/vendor/freetype/src/truetype",
        "e:/software/enterprise/engine/vendor/freetype/src/type1",
        "e:/software/enterprise/engine/vendor/freetype/src/type42",
        "e:/software/enterprise/engine/vendor/freetype/src/winfonts",
        "e:/software/enterprise/engine/vendor/freetype/builds/windows",
        "e:/software/enterprise/engine/vendor/freetype/include/freetype",
        "e:/software/enterprise/engine/vendor/freetype/include/freetype/config",
        "e:/software/enterprise/engine/vendor/freetype/include/freetype/internal",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen/include",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/artery-font-format",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdf-atlas-gen",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen/core",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen/ext",
        "e:/software/enterprise/engine/vendor/msdf-atlas-gen/msdfgen/lib",
        "e:/software/enterprise/engine/vendor/yaml-cpp/src",
        "e:/software/enterprise/engine/vendor/yaml-cpp/src/contrib",
        "e:/software/enterprise/editor/vendor/nativefiledialog/src"
    ],
    "compilerPath": "c:/program files (x86)/microsoft visual studio/2019/community/vc/tools/llvm/x64/bin/clang.exe",
    "compilerArgs": [],
    "compilerFragments": [
        "-g -Xclang -gcodeview -O0 -D_DEBUG -D_DLL -D_MT -Xclang --dependent-lib=msvcrtd",
        "-g -Xclang -gcodeview -O0 -D_DEBUG -D_DLL -D_MT -Xclang --dependent-lib=msvcrtd"
    ]
}
Custom configurations:
[ E:\Software\Enterprise\TestGame\src\TestState.cpp ]
{
    "includePath": [
        "e:/software/enterprise/engine/include",
        "e:/software/enterprise/engine/vendor/ctspookyhash/include",
        "e:/software/enterprise/engine/vendor/cxx-prettyprint",
        "e:/software/enterprise/engine/vendor/glad/include",
        "e:/software/enterprise/engine/vendor/spdlog/include",
        "e:/software/enterprise/engine/vendor/stb_image/include",
        "e:/software/enterprise/engine/vendor/glm",
        "e:/software/enterprise/engine/vendor/imgui",
        "e:/software/enterprise/engine/vendor/hotconsts/include",
        "e:/software/enterprise/engine/vendor/yaml-cpp/include"
    ],
    "defines": [
        "EP_BUILD_GAME",
        "EP_CONFIG_DEBUG",
        "GLM_FORCE_LEFT_HANDED",
        "HC_RELOADING_ON",
        "NOMINMAX",
        "UNICODE",
        "YAML_CPP_STATIC_DEFINE",
        "_UNICODE",
        "_USE_MATH_DEFINES"
    ],
    "compilerPath": "c:/program files (x86)/microsoft visual studio/2019/community/vc/tools/llvm/x64/bin/clang.exe",
    "compilerArgs": [],
    "compilerFragments": [
        "-g -Xclang -gcodeview -O0 -D_DEBUG -D_DLL -D_MT -Xclang --dependent-lib=msvcrtd",
        "-std=gnu++17"
    ]
}
Translation Unit Mappings:
[ E:\Software\Enterprise\TestGame\src\TestState.cpp ]:
    E:\Software\Enterprise\TestGame\src\TestState.cpp
    E:\Software\Enterprise\Engine\include\Enterprise\Graphics.h *
Translation Unit Configurations:
[ E:\Software\Enterprise\TestGame\src\TestState.cpp ]:
    Process ID: 8992
    Memory Usage: 403 MB
    Compiler Path: c:/program files (x86)/microsoft visual studio/2019/community/vc/tools/llvm/x64/bin/clang.exe
    Includes:
        E:\SOFTWARE\ENTERPRISE\ENGINE\INCLUDE
        E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CTSPOOKYHASH\INCLUDE
        E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CXX-PRETTYPRINT
        E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLAD\INCLUDE
        E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\SPDLOG\INCLUDE
        E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\STB_IMAGE\INCLUDE
        E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLM
        E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\IMGUI
        E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\HOTCONSTS\INCLUDE
        E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\YAML-CPP\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\LLVM\X64\LIB\CLANG\12.0.0\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.29.30133\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.29.30133\ATLMFC\INCLUDE
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\UCRT
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\SHARED
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\UM
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.19041.0\WINRT
    Defines:
        EP_BUILD_GAME
        EP_CONFIG_DEBUG
        GLM_FORCE_LEFT_HANDED
        HC_RELOADING_ON
        NOMINMAX
        UNICODE
        YAML_CPP_STATIC_DEFINE
        _UNICODE
        _USE_MATH_DEFINES
        _DEBUG
        _DLL
        _MT
    Standard Version: c++17
    IntelliSense Mode: windows-clang-x64
    Other Flags:
        --clang
        --clang_version=120000
        --ms_compatibility
Total Memory Usage: 403 MB
Browse Paths from compile_commands.json, from workspace folder: E:\Software\Enterprise
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_DYN.DIR
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_DYN.DIR\DEBUG
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_DYN.DIR\DEV
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_DYN.DIR\RELEASE
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_LIB.DIR
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_LIB.DIR\DEBUG
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_LIB.DIR\DEV
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\CMAKEFILES\ENGINE_LIB.DIR\RELEASE
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\VENDOR\FREETYPE\INCLUDE
    E:\SOFTWARE\ENTERPRISE\BUILD\ENGINE\VENDOR\FREETYPE\INCLUDE\FREETYPE\CONFIG
    E:\SOFTWARE\ENTERPRISE\EDITOR\CONTENT
    E:\SOFTWARE\ENTERPRISE\EDITOR\CONTENT\LICENSES
    E:\SOFTWARE\ENTERPRISE\EDITOR\RESOURCES
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\APPLICATION
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\FILE
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\LAYOUTS
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\VIEWS
    E:\SOFTWARE\ENTERPRISE\EDITOR\SRC\WINDOW
    E:\SOFTWARE\ENTERPRISE\EDITOR\VENDOR\NATIVEFILEDIALOG\SRC
    E:\SOFTWARE\ENTERPRISE\EDITOR\VENDOR\NATIVEFILEDIALOG\SRC\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\APPLICATION
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\CORE
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\EDITOR
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\FILE
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\GRAPHICS
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\INPUT
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\SYSTEMS
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\SYSTEMS\RENDERER2D
    E:\SOFTWARE\ENTERPRISE\ENGINE\SRC\TIME
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CTSPOOKYHASH\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CTSPOOKYHASH\INCLUDE\CTSPOOKYHASH
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CTSPOOKYHASH\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\CXX-PRETTYPRINT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\BUILDS\WINDOWS
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\INCLUDE\FREETYPE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\INCLUDE\FREETYPE\CONFIG
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\INCLUDE\FREETYPE\INTERNAL
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\AUTOFIT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\BASE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\BDF
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\BZIP2
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\CACHE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\CFF
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\CID
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\GZIP
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\LZW
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PCF
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PFR
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PSAUX
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PSHINTER
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\PSNAMES
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\RASTER
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\SDF
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\SFNT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\SMOOTH
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\SVG
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\TRUETYPE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\TYPE1
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\TYPE42
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\FREETYPE\SRC\WINFONTS
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLAD\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLAD\INCLUDE\GLAD
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLAD\INCLUDE\KHR
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLAD\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\GLM
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\HOTCONSTS\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\HOTCONSTS\INCLUDE\HOTCONSTS
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\HOTCONSTS\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\IMGUI
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\IMGUI\BACKENDS
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\ARTERY-FONT-FORMAT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDF-ATLAS-GEN
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN\CORE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN\EXT
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\MSDF-ATLAS-GEN\MSDFGEN\LIB
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\SPDLOG\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\STB_IMAGE\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\STB_IMAGE\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\YAML-CPP\INCLUDE
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\YAML-CPP\SRC
    E:\SOFTWARE\ENTERPRISE\ENGINE\VENDOR\YAML-CPP\SRC\CONTRIB
    E:\SOFTWARE\ENTERPRISE\LAUNCHER\SRC
    E:\SOFTWARE\ENTERPRISE\TESTGAME\CONTENT
    E:\SOFTWARE\ENTERPRISE\TESTGAME\RESOURCES
    E:\SOFTWARE\ENTERPRISE\TESTGAME\SRC
------- Workspace parsing diagnostics -------
Number of files discovered (not excluded): 7341

To avoid this issue, I've been disabling CMake Tools as my C/C++ configuration provider and providing include paths in c_cpp_properties.json. Does this align with what you all have experienced? And is there any other information I can provide?

Hi @theOtherMichael I was unable to get started with your repo.  Configure fails with a bunch of messages like this:
[cmake] Cloning into 'D:/test/Enterprise/Editor/vendor/nativefiledialog'...
[cmake] Host key verification failed.
[cmake] fatal: Could not read from remote repository.
[cmake]
[cmake] Please make sure you have the correct access rights
[cmake] and the repository exists.
[cmake] fatal: clone of 'git@github.com:theOtherMichael/nativefiledialog.git' into submodule path 'D:/test/Enterprise/Editor/vendor/nativefiledialog' failed

Any tips to get past this so we can try the repro?

@bobbrow Whoops! The issue is probably caused by my .gitmodules using SSH URLs. You'd need an SSH key set up to clone the submodules correctly.
This was an oversight on my part; I've now updated the gitmodules to use HTTPS URLs. If you try cloning again, I believe it should work.

Does anyone know of a fix for this? Using compile_commands.json didn't work for me.


Exception derived class created

i'm trying to create custom error.

help me to create the custom error :D


TestSANEDIPartyMissing failing

Running unittests on master with go version go1.10 linux/amd64:
asn1: structure error: explicitly tagged member didn't match
--- FAIL: TestSANEDIPartyMissing (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x530 pc=0x6a2855]

goroutine 262 [running]:
testing.tRunner.func1(0xc4202e93b0)
        /home/jsha/go1.10/src/testing/testing.go:742 +0x29d
panic(0x76d1e0, 0xa73cb0)
        /home/jsha/go1.10/src/runtime/panic.go:505 +0x229
github.com/zmap/zlint/util.IsServerAuthCert(0x0, 0x785ac0)
        /home/jsha/gopkg/src/github.com/zmap/zlint/util/ca.go:48 +0x5
github.com/zmap/zlint/lints.(*Lint).Execute(0xc4202cf500, 0x0, 0x8060a3)
        /home/jsha/gopkg/src/github.com/zmap/zlint/lints/base.go:103 +0x117
github.com/zmap/zlint/lints.TestSANEDIPartyMissing(0xc4202e93b0)
        /home/jsha/gopkg/src/github.com/zmap/zlint/lints/lint_ext_san_edi_party_name_present_test.go:33 +0x9e
testing.tRunner(0xc4202e93b0, 0x81e750)
        /home/jsha/go1.10/src/testing/testing.go:777 +0xd0
created by testing.(*T).Run
        /home/jsha/go1.10/src/testing/testing.go:824 +0x2e0
FAIL    github.com/zmap/zlint/lints     0.060s

It looks like SANOtherName.pem is actually malformed -- neither OpenSSL nor Windows can decipher the SAN.
Poking around at the SAN (https://lapo.it/asn1js/#3016A00B06025303130568656C6C6F8207646E732E636F6D)
30 16
     A0 0B
          06 02 53 03
          13 05 68 65 6C 6C 6F
     82 07
          64 6E 73 2E 63 6F 6D

the first part (otherName 2.3.3 = hello) is weird, but looks valid; the second though, if my memory of DER serves, looks like it's a DNSName "dns.com" encoded as an integer (0x80 = context-specific, 0x02 = integer).
It also seems to have some empty RDN SETs in the RDNSequences, which may or may not strictly be valid -- but that doesn't seem to be causing this issue.

I see the problem -- it doesn't have the [0]EXPLICIT tag on the OtherName content:
30 16
     A0 0B
          06 02 53 03
          13 05 68 65 6C 6C 6F
     82 07
          64 6E 73 2E 63 6F 6D

I do recall seeing certificates like this in the wild, but it is definitely wrong:
   OtherName ::= SEQUENCE {
        type-id    OBJECT IDENTIFIER,
        value      [0] EXPLICIT ANY DEFINED BY type-id }

This looks like it was resolved by #214; closing.


Fails on profiling when handling exception on opening the output profiling file.

self = <cProfile.Profile object at 0x7f8b27f3ea70>
file = '/usr/src/app/prof/test_graphene[{_query__ _fragment VideoFields on Video { xid title thumbnails { x240 } duration des...VideoFields  relatedVideos { edges { node { ...VideoFields } } } } }_, _variables__ { _video_xid__ _xxxxxx_ } }].prof'

    def dump_stats(self, file):
        import marshal
>       with open(file, 'wb') as f:
E       OSError: [Errno 36] File name too long: '/usr/src/app/prof/test_graphene[{_query__ _fragment VideoFields on Video { xid title thumbnails { x240 } duration description updatedAt createdAt channel { xid name } stats { views { total } likes { total } } topics { edges { node { xid name } } } } query($video_xid_ String!) { video(xid_ $video_xid) { ...VideoFields  relatedVideos { edges { node { ...VideoFields } } } } }_, _variables__ { _video_xid__ _xxxxxx_ } }].prof'

/usr/local/lib/python3.5/cProfile.py:46: OSError

During handling of the above exception, another exception occurred:

self = <pytest_profiling.Profiling object at 0x7f8b2d03b780>
item = <Function 'test_graphene[{"query": "fragment VideoFields on Video { xid title thumbnails { x240 } duration description... ...VideoFields  relatedVideos { edges { node { ...VideoFields } } } } }", "variables": { "video_xid": "xxxxxx" } }]'>

    @pytest.hookimpl(hookwrapper=True)
    def pytest_runtest_call(self, item):
        prof_filename = os.path.abspath(os.path.join("prof", clean_filename(item.name) + ".prof"))
        prof = cProfile.Profile()
        prof.enable()
        yield
        prof.disable()
        try:
            prof.dump_stats(prof_filename)
        except EnvironmentError as err:
            if err.errno != errno.ENAMETOOLONG:
                raise

            if len(item.name) < LARGE_FILENAME_HASH_LEN:
                raise

>           hash_str = md5(item.name).hexdigest()[:LARGE_FILENAME_HASH_LEN]
E           TypeError: Unicode-objects must be encoded before hashing

/usr/local/lib/python3.5/site-packages/pytest_profiling.py:76: TypeError

To avoid that, i've named my test instead of using the automatically generated name based on the pytests.mark.parametrize parameters value.
Maybe it should be cool not to fail during the hanlding of this error.
python : 3.5.2
ubuntu 17.04
pytest 3.0.7
pytest-profiling 1.2.6

Thank you.

I've opened a PR that will address the secondary issue you raised (failing to hash the string due to unicode)

@abusi Hi this should be fixed now, can you check?

I'll look at it, as soon as I can. Don't hesitate to ping me if I don't. Looking at the fix you did seems that it should be corrected thou.


cannot ssh to scaleway server

Yesterday i was using the server without problems but today when i try to ssh into the server its bringing me this error ;
fred@fred-HP-Compaq-8200-Elite-CMT-PC:/etc/init.d$ ssh<EMAIL_ADDRESS>ssh: connect to host <IP_ADDRESS> port 22: Connection refused

Hi @menty44,
This IP is assigned to a CentOS server, are you sure that it's your IP ?

sure thats is out IP address, I managed to sort out the problem by logging in to the dashboard and using the web console to flush out the iptables. After that everything work out just fine.


Virus total Scan results = negative

Hello, the binaries included in the msi installer file are built directly from the source code using PyInstaller in a fresh Windows VM.
If you would like to run the source code directly, the instructions are included here. Thanks!


Magic number in the code

I find a magic number 163 here:
https://github.com/prometheus/prometheus/blob/ef567ceb7dfab609dda4328ff6eeddb58d90493d/scrape/scrape.go#L151
@fabxc I notice that you wrote the original code. Could you please explain a bit about this number? I guess 163 might be a typo and it should be 1e3. If so, I'd like to sent a patch to fix it :)

Yea, that's a typo and was supposed to be 1e3 similar to the second argument.

@fabxc thanks for confirmation! PR https://github.com/prometheus/prometheus/pull/3968 sent :)


AsyncRelayCommand.NotifyCanExecuteChanged() must be run on the main thread

Type of issue
Missing information
Description
In multiple instances, after calling MyAsyncRelayCommand.NotifyCanExecuteChanged() my Android app was crashing because this call needs to be run on the main thread.
Page URL
https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/asyncrelaycommand
Content source URL
https://github.com/MicrosoftDocs/CommunityToolkit/blob/main/docs/mvvm/AsyncRelayCommand.md
Document Version Independent Id
708935cd-5970-b89b-8443-2e758f35a54b
Article author
@Sergio0694
Metadata

ID: 708935cd-5970-b89b-8443-2e758f35a54b
Service: dotnet-communitytoolkit
Sub-service: mvvm-toolkit

Not sure I see the issue here. That method should be called on the UI thread, yes. Same as OnPropertyChanged. ...Yes?

OnPropertyChanged is called from any thread so that the main thread can update the UI. In Xamarin forms the equivalent command to NotifyCanExecuteChanged is RaiseCanExecuteChanged which can be called from any thread so that the main thread can update the UI.

If this call is not going to be changed to be safely called from a thread that is not the UI thread, I think it would be good to put a warning that it needs to be called from the UI thread.

It's worth considering that this toolkit is agnostic to UI frameworks and therefore it can't dispatch to the UI thread.

"to be safely called from a thread that is not the UI thread"

There is nothing about that call that makes it not safe to be called from a non-UI thread. The reason why it's crashing in some UI frameworks is because they are invoking a handler on the same thread while requiring the UI thread to run the actual callback code. It's their responsibility to dispatch the handlers back on the UI thread if they need that. Or, if you want to work around that yourself, you can of course just make sure to set those properties and call those methods from the UI thread from the start. But this is just the expected behavior. That said, sure, we can add a note just as an FYI in case it helps 🙂

Ok, that makes sense.  I didn't realize that the framework needed to handle that. Thanks for the responses!


Getting "TypeError: 'NoneType' object is not iterable" when translating word "stripper"

Googletrans version: 4.0.0rc1
OS: Ubuntu, Win10

Current behavior:
When translating the word "stripper" from English to German or to French this error occurs. Translation of the same word to other languages such as Spanish, Russian, Romanian or Italian works.
>>> translator = Translator(service_urls=['translate.google.com','translate.google.at'])
>>> translator.translate("Stripper",src="en",dest="fr").text
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\Pegler\Miniconda3\lib\site-packages\googletrans\client.py", line 222, in translate
    translated_parts = list(map(lambda part: TranslatedPart(part[0], part[1] if len(part) >= 2 else []), parsed[1][0][0][5]))
TypeError: 'NoneType' object is not iterable

i get the same error when trying to translate the word "right" from english to portuguese

The same for
translator.translate('German', src='en', dest='es')

Translating "Miscellaneous" to lang=es triggers the same error.

This seems to be the cause, when it gives back a feminine and masculine form of the word when performed manually.

For anyone who is still facing the issue, I had to use the try block as discussed in this thread. It seems to be working for me after adding the try.


Aggregate string before printing in the visualize function

This is not really necessary. Closing this for now.


Adding unit test for function-generation

Codecov Report

Merging #90 into master will increase coverage by 1.72%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #90      +/-   ##
==========================================
+ Coverage   81.96%   83.69%   +1.72%
==========================================
  Files          70       70
  Lines        3937     3937
  Branches      623      623
==========================================
+ Hits         3227     3295      +68
+ Misses        604      540      -64
+ Partials      106      102       -4

Impacted Files
Coverage Δ

...ture-operations/scripts/lib/function-generation.js
90.36% <0%> (+81.92%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b132ce...1f37e99. Read the comment docs.


Initial Metadata project and API design

No implementation. Just the API design so I can get everyone's thoughts and see if I'm headed in the right direction.

My only hesitation with adding GetCustomIntanceMetadataValue is that it exposes a 2nd way to do the same thing, which might be slightly confusing, but I've added them for now and we can see how it feels.
Also, I was thinking about this some more and I don't like the fact that this design does not provide good support for the fingerprint required for optimistic locking when setting custom metadata, so I'd like to propose two alternate solutions:

Store the fingerprint on the Instance/ProjectMetadata classes, move the modification methods to them, and have them return boolean values indicating whether the modification succeeded due to a fingerprint match. The downside here is that this would require a 2nd request to get the fingerprint and metadata at the same time, but there could be a race condition there. Also, that 2nd request requires authentication, so we would need to ask the metadata server for an access token, which means a 3rd request.
Remove all Remove/Set custom metadata methods and instead have a ModifyCustomInstanceMetadata(Action<IDictionary<string,string>>) method (with associated project and async versions as well). This method would get the fingerprint and metadata in one API call, pass a dictionary of the custom metadata into the supplied delegate instance and push any modifications back to the server using the fingerprint. If that fails, it would perform the process again in a loop (and terminate after X iterations, perhaps specified by optional settings).

I'm leaning towards option 2.
Google.Apis.Auth is added so the project can use ConfigurableHttpClient and TokenResponse.

Forgot to say PTAL...PTAL.

Unfortunately I'm snowed under trying to get other bits done before I head off to Sydney on Friday - will take another pass if I get time!

No worries. Just wanted everyone to know I wasn't still working on addressing comments.

(As discussed with Ivan offline) Having ModifyCustomInstanceMetadata take a delegate with a mutable object may cause other issues, like if someone stores a reference to the collection and modifies it later or on a different thread. Ivan suggested a way to specify change descriptions that we repeatedly try to apply, which is better, but doesn't allow the changes to be based off the current state of things. So I suggested instead having an immutable object passed into ModifyCustomInstanceMetadata and having the delegate return the change descriptions, perhaps like this:
client.ModifyCustomInstanceMetadata(currentMetadata =>
{
    return new[] {
        MetadataChange.Remove("X"),
        MetadataChange.AddOrUpdate("Y", "Y-value"),
        MetadataChange.AddOrUpdate("Z", currentMetadata["Z"] + "-updated"),
    };
});

Or we could use something like Roslyn where everything is immutable but there are modification methods that return a new object (and reuse as much as possible from the original):
client.ModifyCustomInstanceMetadata(currentMetadata =>
{
    return currentMetadata
        .Without("X")
        .With("Y", "Y-value")
        .With("Z", currentMetadata["Z"] + "-updated");
});

I know is taking a dependency when none is preferable but, what is we took a dependency on the Google.Apis.Compute.v1 package so we can re-use the same types when describing VM instances, disks, etc... from the metadata server. This way we can use the same types, instead of copying them. Now not sure if the dependency is worth it though... What do you think?

The types in Google.Apis.Compute.v1 are slightly different than those for the metadata library. They have a lot more information, so that would be unused for this. Also, some things are in different places: the licenses ids in the metadata server are on the instance, whereas in the Compute API, they are on the disks. I feel like we would have to shoehorn things in a bit too much here.

PTAL. Support for .NET Core and as per offline discussion with Ivan, removed metadata modification methods. Trying to manage getting the fingerprint from the Compute API but everything else from the metadata server in a way that seems clean and consistent just doesn't seem very easy at this point. For now, it will just support reading metadata.

The fact that the types from the metadata server are different from the Compute.v1 API is an accident that we can remediate here but using the Compute.v1 APIs as the universal format. I would like us to try to use it as much as possible so we don't have two ways to look at what is in essence the same information.
See the .NET Framework design guidelines for the reason to use the 0 value in enums for the None value (Unknown in your case).

Looking really good. Concentrating on the read side makes things much easier.

I've updated the Unkowns to be zeros, but this does make things a bit weird for the MaintenanceStatus enum, which now has a Unknown value of 0 and a None value of 1.
As far as the Compute.v1 API classes, it still feels a bit weird to me just looking at the Project class. Perhaps it would be better to just start replacing the leaves of the instance's hierarchy of information and then move up until things stop fitting so nicely. Although the downside there is then we would have a mix of classes.

As I start changing over to Compute.v1 classes, I'm liking this approach less and less:

Every class has info that will be unused, like ETag and SelfLink. And some classes have a lot of unused info. For example, Disk (Compute.V1) has 24 properties but the DiskMetadata class I defined only needs 4. Users of the metadata library may get lost in a sea of unnecessary clutter when looking for information that will actually be available. And since the Compute.v1 classes are auto-generated, we can't help with triple-slash comments unless we subclass everything.
Everything is mutable, which goes against the read-only nature of this library.
All ids are nullable ulongs, which are not CLS-compliant.

I understand the desire for consistency, but this really seems like trying to force something where it doesn't belong.

@ivannaranjo ok, I just had a thought about how we might be able to have something specific to the metadata server but also allow someone to use common logic for both this library and the compute library. What if we have a set of extension methods that convert between to two sets of classes as best as possible. So if you have a DiskMetadata instance, you can call disk.ToComputeDisk() (or something like that) to get the equivalent instance in the Compute.v1 Disk class. How does this sound?

Well, that would certainly alleviate things, but I still think it is better if we just use the same data layer as Compute for this so we don't have to make this conversion visible to the user. I think that having a common set of types is the main benefit for this.

@ivannaranjo Ok, I will move ahead with this then and subclass where necessary to add in missing information from the Compute data layer.

FYI, I've done the source reorg I mentioned before - hopefully it won't be too hard for you to rebase, but as the change is mostly additions, you may find it's simplest to copy the code away somewhere, start a new branch from master, and just put the files in the new location.

Actually, I just rebased without issue. I'm going to push what I have so far and then change over to using the Compute data layer.

@ivannaranjo So I was able to sub-class Project and Instance cleanly enough, but there are two other types: ServiceAccount and NetworkInterface, which are also missing some properties (aliases for the former and forwarded IP addresses, alias IP ranges, and the MAC address for the latter) but which are not so easy to subclass. Collections of these types are both exposed off Instance with an IList<X>, so I would need to shadow those properties so we could return an list of the derived type and then keep the same instances in two separate collections so callers to the shadowed property can still get the instances.
Do you think it would be better to drop this info for now and see if anyone requests it in the future, or just go with the sub-class approach?

Well, what sort of information is missing from the Compute layer? I think that we can drop adding new information not present there if necessary. The important thing I think is to share the types, not extend the Compute types. That can lead to fragile state should they choose to add the missing properties themselves for us. I think that we should just expose what is already there, no more.

Here is what is missing:

Project: SSH keys.
Instance: SSH keys, license ids (although these could be the same licenses exposed off AttachedDisk).
ServiceAccount: aliases.
NetworkInterface: forwarded IP addresses, alias IP ranges, MAC address.

@ivannaranjo PTAL, the project is now updated to use the Compute data layer for everything.

(updated some comments which were still referring to the manually defined metadata classes)

Looking now, sorry for the delay, heads down on VS extension.

Added a couple of comments, is looking really good now.

PTAL, added wait for changes support.

Ok, I think is good to go :).

@ivannaranjo Thanks, I will add the comments I mentioned above, merge with the latest, and submit a bit later today.


Unlockers seems to not work if ran as command override in a docker-compose

First thing is to try to replicate the issue with docker compose

Create a compose like the following

version: "3.7"

services:
  # TDEX daemon connected to Blockstream.info explorer
  tdexd:
    container_name: "tdexd"
    image: ghcr.io/tdex-network/tdexd:latest
    restart: unless-stopped
    environment:
      - TDEX_LOG_LEVEL=5
      - TDEX_NETWORK=testnet
      - TDEX_BASE_ASSET=144c654344aa716d6f3abcc1ca90e5641e4e2a7f633bc09fe3baf64585819a49
      - TDEX_NATIVE_ASSET=144c654344aa716d6f3abcc1ca90e5641e4e2a7f633bc09fe3baf64585819a49
      - TDEX_EXPLORER_ENDPOINT=https://blockstream.info/liquidtestnet/api
    ports:
      - "9945:9945"
      - "9000:9000"
    #### Unlocker with file ####
    # Uncomment to override default command and start tdexd and unlockerd.
    # You need to uncomment also the volume down that mount the path used here.
    command: /bin/bash -c "(sleep 1 && unlockerd --password_path=/pwd.txt --interval=10 >& /dev/null &) && /tdexd-linux"

    volumes:
      - ./tdexd:/home/user/.tdex-daemon
      - ${PWD}/pwd.txt:/pwd.txt

Run it with docker-compose up

initialize with seed and password and put it in the pwd.txt file in local path

check status with docker exec -it tdexd tdex status

Restart the Docker engine (or Docker Desktop if on Mac)

Is it unlocker working?

To prevent this, should maybe the tdexd "pulls" the password IN instead of being a separated service?
LND does the same apparently, we can have an ENV VAR to specify where the password is.
https://github.com/lightningnetwork/lnd/blob/master/docs/wallet.md#auto-unlocking-a-wallet
TODO:

[ ] move unlocker functionalities inside tdexd
[ ] add new ENV VAR
[ ] change tdex-box docker-compose and mount the volume with pwd.txt inside according to new ENV VAR
[ ] change documentation in the Dev Portal

First thing is to try to replicate the issue with docker compose

Create a compose like the following

version: "3.7"

services:
  # TDEX daemon connected to Blockstream.info explorer
  tdexd:
    container_name: "tdexd"
    image: ghcr.io/tdex-network/tdexd:latest
    restart: unless-stopped
    environment:
      - TDEX_LOG_LEVEL=5
      - TDEX_NETWORK=testnet
      - TDEX_BASE_ASSET=144c654344aa716d6f3abcc1ca90e5641e4e2a7f633bc09fe3baf64585819a49
      - TDEX_NATIVE_ASSET=144c654344aa716d6f3abcc1ca90e5641e4e2a7f633bc09fe3baf64585819a49
      - TDEX_EXPLORER_ENDPOINT=https://blockstream.info/liquidtestnet/api
    ports:
      - "9945:9945"
      - "9000:9000"
    #### Unlocker with file ####
    # Uncomment to override default command and start tdexd and unlockerd.
    # You need to uncomment also the volume down that mount the path used here.
    command: /bin/bash -c "(sleep 1 && unlockerd --password_path=/pwd.txt --interval=10 >& /dev/null &) && /tdexd-linux"

    volumes:
      - ./tdexd:/home/user/.tdex-daemon
      - ${PWD}/pwd.txt:/pwd.txt

Run it with docker-compose up

initialize with seed and password and put it in the pwd.txt file in local path

check status with docker exec -it tdexd tdex status

Restart the Docker engine (or Docker Desktop if on Mac)

Is it unlocker working?

@sekulicd We need to coordinate all documentation and tdex-box reference with new ENV VAR


Use required and optional attributes to determine whitelisted attributes

Ticket
https://jira.bqsoft.com/browse/ATOM-5829
What this does
This changes the whitelisted attributes to be based on the required and optional attributes listed in the action. This prevents superfluous parameters from being sent into braintree in some cases.
Why we did this
It was broken if you sent in extra attributes to create_customer
I'd like the reviews to pay special attention to:
NA
The original feature connected to this bug fix is:
NA
We'll have to do this manual step
NA
Special rollback steps:
NA
Overall, I feel this way about this code
Green

Hot damn.

Does this pass customer info as well?

@georgeismike it passes everything that's listed in the create_customer action, we are not currently populating them in connect however: https://github.com/Hello-Labs/connect_api/blob/master/app/services/payment_processing/customer.rb#L18


rustbot failed to ping people in a PR

In https://github.com/rust-lang/rust/pull/115972 rustbot should have pinged some people due to the files that were changed (mentions rules), but somehow that didn't happen. I would understand if it missed the PR entirely due to github not running the hook or whatever, but it did auto-assign a reviewer, so clearly the PR was visible -- it just somehow skipped the part where it is supposed to ping people.

After you force-pushed pings were fired. I wonder if it was just a spurious hiccup (either on the github end or the triagebot), even though the autoassignment worked (as you correctly point out). Perhaps the triagebot logs might give more insights.
Did something like that happened in the past? (just curious)

The same happened again in https://github.com/rust-lang/rust/pull/127907: the PR mutates builtin derives, but no ping for that was done on PR creation, nor on the first force-push. The second force-push a few days later then triggered that ping.
(I've seen this more often but I don't always report that here.)

This still happens regularly, see https://github.com/rust-lang/rust/pull/132492 for another recent example.

Which mentions would you have expected those PRs to trigger?

This one for library/core/src/intrinsics.
... oh damn, the main intrinsics.rs file is not in that folder. oops sorry for the noise


Add path-based fingerprint override for method/class offenses

This PR implements path-based fingerprints for method and class-based offenses, reconstructing the behavior of the soon to be replaced default fingerprint (details).
Ideally the fingerprint would also include the appropriate method or class name within the digest, but I couldn't find a reasonable way to do include that. We're already using numerous monkey patches for location adjustments and I went down a frustrating path of additional monkey patching before bailing.
This seems like a good first step towards supporting the new default fingerprinting behavior.
@codeclimate/review :mag_right:

Do I understand correctly that these fingerprints would be identical to the current default?
I'd like to dig a bit more into the monkey patching before we bail entirely on that. Maybe a good thing to pair on.

Do I understand correctly that these fingerprints would be identical to the current default?

That's correct.

I'd like to dig a bit more into the monkey patching before we bail entirely on that. Maybe a good thing to pair on.

Sounds good to me!

@wfleming Ready for another :mag_right:

LGTM


PR : Sprint 3

#9 #8

Work in progress does not been finished during the sprint, work has been report to sprint 4 #54
PR is closed without merge.


Behavior of a change in retention

If I set up retention in a Storage Account for a certain amount (say 30 days) and then changed the setting, does the setting apply retroactively?
In other words, what happens in these two situations?

Change retention from 30 days to 10 - will logs older than 10 days all get deleted whenever the next cleanup happens?
Change retention from 30 days to 0 (persistent) - will the logs that are currently there be kept forever? Or would the ones that were collected during the 30 day retention still get deleted after 30 days?

Thanks!

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

ID: 39bd6875-8c82-02ff-5b74-86bc9ce5b902
Version Independent ID: d9d36752-ac83-89b1-e22d-32ba6a41d7e5
Content: Azure Active Directory activity logs in Azure Monitor (preview)
Content Source: articles/active-directory/reports-monitoring/concept-activity-logs-azure-monitor.md
Service: active-directory
GitHub Login: @priyamohanram
Microsoft Alias: priyamo

Thanks for the question! We are investigating and will update you shortly

Any progress here? I'm in ProDirect support and there is a customer waiting on this issue. Thanks!

Thanks @ManojReddy-MSFT. Is there a recommended method to preserve logs if the initial replication period was too short? In this case they are actually changing from 365 days to 0 (persistent).
Can they maybe copy the logs to a different container or storage account where the cleanup job would not run?

Thanks @ManojReddy-MSFT. I'll let you determine if this information is worth adding to the FAQ in the document or if you just want to close out.

@dcbrown16 I will work with the author to get this content added to the doc.


Authentication

Pages -

Login Page
Sign Up page

Components -

Input Field
Alert
Prevented & Protected Routes

Functionalities -

Input Validation
Conditional routing

Try to keep your PR small as it makes reviewer's life less hell


PromQL queries with binary operators after an or operator result in error

What type of bug is this?
Unexpected error
What subsystems are affected?
Query Engine
Minimal reproduce step
On a metric with data in the given time range, execute
 {__name__="my_metric"} or {__name__="my_metric"} + 5

The actual query I want to run is
(delta({__name__="my_metric"}[1m] offset 15s) * 60) > 100
or
({__name__="my_metric"} * 0)

As a way to default missing/filtered values to 0. Usually I would use ... or label_replace(vector(0), ...), but label_replace isn't supported yet.
What did you expect to see?
The left query values being ORed with 0
What did you see instead?
PlanQuery: Internal error during building DataFusion plan: No field named my_metric."greptime_value * Float64(0)". Valid fields are my_metric.my_tag, my_metric.greptime_timestamp, "greptime_value * Float64(0)".
What operating system did you use?
Mac OS 15.1
What version of GreptimeDB did you use?
0.11.0
Relevant log output and stack trace
No response

Thanks for reporting this. It seems caused by column name mismatching, let me file a fix.
BTW, does this work for you as a workaround? (delta({__name__="my_metric"}[1m] offset 15s) * 60) > 100 or vector(0)

Thanks for getting on that so quickly.

BTW, does this work for you as a workaround? (delta({name="my_metric"}[1m] offset 15s) * 60) > 100 or vector(0)

No, because we expect the delta portion to return a series (or multiple series) with labels, which then won't match the vector(0) portion. This is a workaround because label_replace isn't ready.


High contrast + custom theme ?

Hi,
is it possible to have vscode use high contrast, but with a custom theme ?
if yes, how ?

When creating a new theme, set the uiTheme to 'hc_black'.
See here for an example:
https://github.com/Microsoft/vscode/blob/master/extensions/theme-defaults/package.json#L33


Branch list book command

Create List Book Command functionality with sufficient testing to make sure the feature works well
Add book list command and tests.
Notable changes and files created:
ListBookCommand : Create a List Book Command Class
BookCommandParser : Add the case for list book command
ListBookCommandTest: Create Tests for the list book command
EditBookCommandTest and EditBokDescriptorTest: Refactored them into the correct package (book package under the book package in the logic package) for Tests.

Codecov Report

Merging #69 (bede03c) into master (3a65cc3) will increase coverage by 0.02%.
The diff coverage is 80.00%.

@@             Coverage Diff              @@
##             master      #69      +/-   ##
============================================
+ Coverage     71.92%   71.94%   +0.02%
- Complexity      542      544       +2
============================================
  Files            89       90       +1
  Lines          1713     1718       +5
  Branches        208      208
============================================
+ Hits           1232     1236       +4
- Misses          421      422       +1
  Partials         60       60

Impacted Files
Coverage Δ

...u/address/logic/parser/book/BookCommandParser.java
0.00% <0.00%> (ø)

...u/address/logic/commands/book/ListBookCommand.java
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3a65cc3...bede03c. Read the comment docs.


Custom data points are not shown on web

Description
Hello!
While this library is quite extensive, it is very buggy.
I am copying the exact code sample to generate a line chart, LineChart, with a vertical strip and custom data points.
However, the custom data points are not shown on the web. I must be misunderstanding something.
Thank you!
Steps to reproduce

The source of the code sample is from the documentation, and can be found at:
https://gifted-charts.web.app/areachart/#customDataPoints

I've provided a reference to the Expo Snack:
https://snack.expo.dev/@jeanniton.mnr/custom-data-points-and-vertical-strip?platform=web

Snack or a link to a repository
https://snack.expo.dev/@jeanniton.mnr/custom-data-points-and-vertical-strip?platform=web
version of react-native-gifted-charts

React Native version

Platforms
Web
Workflow
Expo Go
PS: I have installed react-gifted-charts, I have the same bad results.

When I examine the rendered SVG element code, I notice that the custom data points appear as DIV objects inserted directly into the SVG.
However, SVG only renders other XML or HTML content if it is embedded within the SVG foreignObject.
Would that be a way of approaching and fixing this issue?

Hi @jeanniton-mnr Thanks for reporting it and suggesting the fix. Your suggestion to use <ForeignObject> worked like a charm!
It has been fixed from versions 1.4.48 onwards. Please use the latest version of the library.


Use multithreading in batch gradient computation

Add the Threads.@threads macro to the for-loop in gradients_wrt_batch:
https://github.com/adrhill/ExplainableAI.jl/blob/f1b89ab9c784ff2a86de9997efa904580b2af6dd/src/gradient.jl#L5-L16

Not required due to more general implementation using VJPs in #144.


Empty arrays in JSON

Suppose there are 2 items on a page, but only one is populated, the JSON would show the populated item and an empty array. Should that empty array not be there at all?
  "content": [
    [
      [],
      "139993245373310"
    ]
  ],

@swang2013 Could you please verify that the latest code drop fixes this issue?
Please verify using branch :https://github.com/Esri/briefing-book/tree/develop_2.0
Also, please note the configuration file has some new options. You will now need to define, if you are searchin all of AGOL, just an organization or only a group.

@LindsayThomas - verified as fixed.


Fixing The Mobiile UI

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The mobile ui of the website has some white line line comming in the right of the screen, and the images are also not alligned prooperly.
Use Case
I will fix thses so the website becomes usable on the phone screen layout also
Benefits
No response
Add ScreenShots
https://github.com/user-attachments/assets/7834a7cb-4787-4feb-977e-d8c0f89ad848
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

@samar12-rad its too resolved


Scanner.Scan must return error if result is empty

Using pREST as package the function Scanner.Scan must return an error if result is empty and Scan is receiving an object to be populated.
Example:
type item struct {
	Value string
}
sc := postgres.Query("SELECT * FROM itens items WHERE id=$1, itemID)
i:=item{} // <- only one item not an array
if err = sc.Err(); err != nil {
	return
}
err = sc.Scan(&i)
if err = sc.Err(); err != nil {
	if err==postgres.ErrEmptyResult { // my suggestion that it should return
		fmt.Println("empty result")
		return
	}
	fmt.Println(err) // something else went wrong.
	return
}

This is necessary because there is no way to know if the result is empty or if the record matches with the empty object.
A workaround is to pass an array instead of an empty object and then use len() to check if the result is empty.
iaux:=[]item{}
...
if len(i) == 0 {
	fmt.Println("empty result")
	return
}
i=iaux[0]

one other way that i like more than return an error is return the number of rows returned just following the io.Reader ideia that return the number of bytes readed


Alert component

Hello,
I would be good idea to have alert component.

https://picturepan2.github.io/spectre/components.html#toasts
Can work like alert.


build-script: ensure module group is used only when building SwiftSyntax library.

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - b0fc24fc795272bb8a351f20dd0dae0a4429d40b


Index is out of range at assembling loop

When the option 'loopAdditionalSlides' is set, there is a JavaScript
error that the object (_this.slides) does has no 'innerHTML'. This
happens because the 'loopedSlides' is a sum from 'slidesPerView' and
'loopAdditionalSlides'. This error occurs as well if either are set to
higher than the number of actual slides.
Also changed the assembly a bit, so it is no longer mixed up.

Closing as new Swiper 3 released with different API and rewritten core


Please add translation plugin

Because there are many non-English users, some actually Chinese users, want to add an automatic translation plug-in, you can use the mouse to select the document to get the translated content.

Because there are many non-English users, some actually Chinese users, want to add an automatic translation plug-in, you can use the mouse to select the document to get the translated content.

We are ready to help with the development of a translation plugin.
Is there such a possibility?

What is the translation plugin? Does the current Mendeley have the function?


Manual script fails

After installation, I am unable to manually run the script.  I consistantly get the following error:
Audio bitrate was invalid, defaulting to 256 per channel
Traceback (most recent call last):
File "C:\sickbeard_mp4_automator\manual.py", line 18, in
settings = ReadSettings(os.path.dirname(sys.argv[0]), "autoProcess.ini")
File "C:\sickbeard_mp4_automator\readSettings.py", line 225, in init
self.artwork = config.getboolean(section, "download-artwork") # Download and embed artwork
File "C:\Python27\lib\ConfigParser.py", line 370, in getboolean
raise ValueError, 'Not a boolean: %s' % v
ValueError: Not a boolean: Poster
Any assistance would be greatly appreciated.
Bill

Have you installed all the pip stuff from the readme?

Your config file is corrupted probably.
Sent from my iPhone

On Sep 2, 2016, at 19:26, shpankey<EMAIL_ADDRESS>wrote:
Have you installed all the pip stuff from the readme?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I have run all the pip commands.  I'll check the config file. Is that autoProcess.ini?

Yep!  THANKS!!!!!!


Trigger event after component is connected and rendered?

I would like to trigger a function once my component is added to the DOM and completely rendered. How can I achieve this using lit-element?
Right now I set a timeout of 200 ms within ConnectedCallback and call my function. I also use await updateComplete as I thought this ment waiting until the render process completes.
  async connectedCallback() {
    super.connectedCallback()
    await this.updateComplete;
    // Apply scalling
    setTimeout(_=>{this.scaling()},200)
  }

The component is completely rendered when the updateComplete promise resolves. You should not need the setTimeout.

The component is completely rendered when the updateComplete promise resolves. You should not need the setTimeout.

Does that include the sub-components contained in the <slot></slot> ?
My function this.scalling() checks the height of my component in pixels and then adds a transform: scale(...) to the styling of the component. However the height in pixels is wrong hence the timeOut to make sure the component is completely drawn.

No, it does not. For children in your shadowRoot, you can implement _getUpdateComplete() to await any specific elements you care about. However, this is probably not great for slotted content. Rather than use setTimeout, it's better to use requestAnimationFrame which should be sufficient.
async connectedCallback() {
  super.connectedCallback()
  await new Promise((resolve) => requestAnimationFrame(resolve));
  this.scaling()
}

Hope that helps. Feel free to re-open if more info is needed.

It did not solve my issue, but if I combine it with a setTimeout of 0 ms It does work:
async connectedCallback() {
  super.connectedCallback()
  await new Promise((resolve) => requestAnimationFrame(resolve));
  setTimeout(_=>{this.scaling()},0)
}

I found thesetTimeout(_=>{this.scaling()},0) hack somewhere else, which doesn't work on it's own, only with your proposed solution.

Generally, unless some scheduling is customized, firstUpdated() should be called before the requestAnimationFrame after connectedCallback.
In this case if you're trying to respond to the size of the element, I'd use ResizeObserver so that it happens dynamically any time the size changes.
Otherwise, it'd be good in any particular case to debug and see what order connected/rAF/paint is done in (it should be that order), and see what else is effecting the size, but I know that a lot of times with async issues, people try to just be "more async". In that case you could wait an setTimeout(0). If that isn't working and you have to go back to setTimeout(200), then there's something really late happening that's messing with the size like a font or CSS loading, and then ResizeObserver is the only robust way to handle it.


Typo 8.3.11

/tex/mainmatter/fo-language.tex:

On line 560 once at $(r,1,2)$ and once at $(r,1,2,1,1,2,1)$: should be once at $(r,1,1)$ and once at $(r,1,2,1,1,2,1)$:

On line 590 to be able to distinguish the occurrence of $R(x,y)$ at $(r,1,2)$ from the occurrence at $(r,1,2,1,1,2,1)$. should be to be able to distinguish the occurrence of $R(x,y)$ at $(r,1,1)$ from the occurrence at $(r,1,2,1,1,2,1)$.

Maybe more an error than a typo

Thanks @coenvdam . Classifying it as a typo since there's no reasoning error here and the problem can be fixed by changing symbols. (Probably a bit generous as a classification, quite possible I made an error here in walking through the tree).

@jkorb Please note that there are two instance of the same error. Your commit that closed this issue only fixes the first.

Oh, my bad! Will fix asap! Thanks @coenvdam !


set raw_power_state to unknown on disconnect_inv

before it was not set due to a typo of comparing raw_power_state
instead of setting it

@djberg96 @agrare @bronaghs copy paste strikes back :smile:
does this make sense in azure and google context?

@miq-bot add_labels bug, providers/amazon, providers/azure, providers/google

LGTM :+1:

:+1:

LGTM

@blomquisg merge?


Updated layout

Now including a layout for a second chip with additional test structures.

Approved. Check whether it's merged.


fix(events): only display events you are going to. Fixes HELP-1477

The events on the dashboard should now only be displayed if you have not cancelled them, and got accepted to that event. Needs to be merged together with two other PR's for the backend.
Fixes HELP-1477

:tada: This PR is included in version 1.22.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


We should agree upon a style guide

Noticed that we don't seem to have an official style guide that we adhere to.  I think it would be nice if we could pick one as we could encode at least parts of it into linting rules and ideally wouldn't have to look for examples in other Swift projects.

We have SwiftLint integrated into the project. But lint warnings or error won't showing on pull requests. Only on the build logs. I am currently working on an enhancement to the Package Builder project to include a reporting feature for SwiftLint on pull requests. Once I get that up and running, we could integrate Package Builder into the CI for this project, which can then report style issues on pull requests.

in the meantime, can you post instructions on how to run the linting locally and what the settings are (and maybe where they come from?)

On some projects I actually add a git precommit hook that runs swiftlint, which can prevent you from commiting with style violations.


Reintroduce VisitDirectoryProvider and update in preprocessor

Have verified this works on p38. Unfortunately the filenames currently look like this:
BL38P-1d11-hdf.h5
BL38P-2d11-hdf.h5
which is a bit confusing and I think it actually originates from ophyd-async and how it propagates down the information from directory provider... I'll investigate but the easiest solution is probably a quick ophyd-async PR.


This may be a problem with a HTTPS certificate. Make sure you have the right certificate

Category

[x] Bug

Describe the bug
We have developed few web parts using SharePoint Framework SPFX for one of our portal that is powered by SharePoint Online and was working fine. Until 27 March,, there is an issue in loading the web parts. Please refer to the attached screenshot of the error.

OS: [e.g. Windows 10, MacOS 10.15.x]
Framework: [e.g. .NET Framework v3.x, .NET Core v3.x, Node.js v6/v8/v10/v12]
Browser(s): [e.g. Chrome v79, Safari v22, FireFox v31, IE v11, Edge, Chromium Edge v79]
Tooling: [e.g. VS Code, SPFx v1.10.0, Visual Studio 2019]

Thanks for your contribution! Sharing is caring.

Those look more like 404's than cert issues. Few questions:

have you verified the files in question are reachable via the browser (directly, not via the web part)?
have you verified the component is still deployed & installed?
have you checked the /ClientSideAssets library to see if the files are there?

In your original post, you didn't edit the context bullet points at all... those are there for a reason to provide context with the browser/platform. Please update that/

Those look more like 404's than cert issues. Few questions:

have you verified the files in question are reachable via the browser (directly, not via the web part)?
have you verified the component is still deployed & installed?
have you checked the /ClientSideAssets library to see if the files are there?

In your original post, you didn't edit the context bullet points at all... those are there for a reason to provide context with the browser/platform. Please update that/

The component is deployed and installed. All the files are reachable via browser. Below are the errors found from the browser console log. Not sure if there are any changes made by Microsoft to the SharePoint Online environment recently. The error is intermittent.

Few more points of clarification:
@EY2023 said:

Until 27 March,, there is an issue in loading the web parts.

Are you saying the error STARTER on March 27 or happened UNTIL March 27 and no longer happens
Also, at the end of the OP, there was a section for you to provide context, but you apparently didn't do anything with it. Please add that in your reply or update the OP... context is key for issue reports.
With all that said, if you can get to the files & the error is intermittent, it might be related to the extra load SPO has had on it since the cloud demand skyrocketed in March/April across the world. If so, there's not much we can do about it here... but they are aware and working on these issues.

Hello,
I do have the same issue, its work fine in workbench, other than IE.
Stuck with this issue for a while, is there any solution for this?
I have deployed it in  Appcatalog site.
those files are accessible via browser
https://publiccdn.sharepointonline.com//sites//ClientSideAssets/ff82b95b-2168-474c-b8e4-a72de48366d7/spfx-student-search-web-part_6f14a2d1a811d0dcd4010788bfa0b558.js, but it still says
There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.
***CALLSTACK: