[libigl] build failure

Host Environment

OS: Windows
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
.\vcpkg.exe install libigl[imgui,embree,opengl,glfw,png] --recurse
Failure logs
Building package libigl[core,embree,glfw,imgui,opengl,png]:x64-windows...
-- Using cached C:/Libraries/vcpkg/downloads/libigl-libigl-f6b406427400ed7ddb56cfc2577b6af571827c8c.tar.gz
-- Using source at C:/Libraries/vcpkg/buildtrees/libigl/src/f571827c8c-b1a8caf56b
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: ninja -v
    Working Directory: C:/Libraries/vcpkg/buildtrees/libigl/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      C:\Libraries\vcpkg\buildtrees\libigl\config-x64-windows-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:296 (vcpkg_execute_required_process)
  ports/libigl/portfile.cmake:46 (vcpkg_configure_cmake)
  scripts/ports.cmake:94 (include)

Error: Building package libigl:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: libigl:x64-windows
  Vcpkg version: 2019.09.12-nohash

Additional context
This related to issue: https://github.com/microsoft/vcpkg/issues/8809
After removing nanovg, and install libigl, I got this build failure.

The content of config-x64-windows-out.log:
[1/2] cmd /c "cd ../../x64-windows-dbg && "C:/Users/zhma/scoop/apps/cmake/3.15.4/bin/cmake.exe" "C:/Libraries/vcpkg/buildtrees/libigl/src/f571827c8c-b1a8caf56b" "-DLIBIGL_WITH_EMBREE=ON" "-DLIBIGL_WITH_OPENGL=ON" "-DLIBIGL_WITH_OPENGL_GLFW=ON" "-DLIBIGL_WITH_OPENGL_GLFW_IMGUI=ON" "-DLIBIGL_WITH_PNG=ON" "-DLIBIGL_WITH_XML=OFF" "-DLIBIGL_WITH_PYTHON=OFF" "-DLIBIGL_BUILD_TESTS=OFF" "-DLIBIGL_BUILD_PYTHON=OFF" "-DLIBIGL_EXPORT_TARGETS=ON" "-DLIBIGL_USE_STATIC_LIBRARY=OFF" "-DLIBIGL_WITH_COMISO=OFF" "-DLIBIGL_WITH_TETGEN=OFF" "-DLIBIGL_WITH_TRIANGLE=OFF" "-DLIBIGL_WITH_PREDICATES=OFF" "-DLIBIGL_BUILD_TUTORIALS=OFF" "-DPYTHON_EXECUTABLE=" "-DCMAKE_MAKE_PROGRAM=C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Libraries/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/Libraries/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/Libraries/vcpkg/packages/libigl_x64-windows/debug""
FAILED: ../../x64-windows-dbg/CMakeCache.txt
cmd /c "cd ../../x64-windows-dbg && "C:/Users/zhma/scoop/apps/cmake/3.15.4/bin/cmake.exe" "C:/Libraries/vcpkg/buildtrees/libigl/src/f571827c8c-b1a8caf56b" "-DLIBIGL_WITH_EMBREE=ON" "-DLIBIGL_WITH_OPENGL=ON" "-DLIBIGL_WITH_OPENGL_GLFW=ON" "-DLIBIGL_WITH_OPENGL_GLFW_IMGUI=ON" "-DLIBIGL_WITH_PNG=ON" "-DLIBIGL_WITH_XML=OFF" "-DLIBIGL_WITH_PYTHON=OFF" "-DLIBIGL_BUILD_TESTS=OFF" "-DLIBIGL_BUILD_PYTHON=OFF" "-DLIBIGL_EXPORT_TARGETS=ON" "-DLIBIGL_USE_STATIC_LIBRARY=OFF" "-DLIBIGL_WITH_COMISO=OFF" "-DLIBIGL_WITH_TETGEN=OFF" "-DLIBIGL_WITH_TRIANGLE=OFF" "-DLIBIGL_WITH_PREDICATES=OFF" "-DLIBIGL_BUILD_TUTORIALS=OFF" "-DPYTHON_EXECUTABLE=" "-DCMAKE_MAKE_PROGRAM=C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Libraries/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/Libraries/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/Libraries/vcpkg/packages/libigl_x64-windows/debug""
-- The C compiler identification is MSVC 19.23.28106.4
-- The CXX compiler identification is MSVC 19.23.28106.4
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- MSVC -> forcing use of statically-linked runtime.
-- Looking for pthread.h
-- Looking for pthread.h - not found
-- Found Threads: TRUE
-- Creating target: igl::core (igl)
-- Creating target: igl::embree (igl_embree)
-- Creating target: igl::opengl (igl_opengl)
-- Found OpenGL: opengl32
-- Creating target: igl::opengl_glfw (igl_opengl_glfw)
-- Creating target: igl::opengl_glfw_imgui (igl_opengl_glfw_imgui)
-- Creating target: igl::png (igl_png)
CMake Error at cmake/libigl.cmake:398 (target_include_directories):
  target_include_directories may only set INTERFACE properties on INTERFACE
  targets
Call Stack (most recent call first):
  CMakeLists.txt:46 (include)

-- Configuring incomplete, errors occurred!
See also "C:/Libraries/vcpkg/buildtrees/libigl/x64-windows-dbg/CMakeFiles/CMakeOutput.log".
See also "C:/Libraries/vcpkg/buildtrees/libigl/x64-windows-dbg/CMakeFiles/CMakeError.log".
[2/2] cmd /c "cd ..  && "C:/Users/zhma/scoop/apps/cmake/3.15.4/bin/cmake.exe" "C:/Libraries/vcpkg/buildtrees/libigl/src/f571827c8c-b1a8caf56b" "-DLIBIGL_WITH_EMBREE=ON" "-DLIBIGL_WITH_OPENGL=ON" "-DLIBIGL_WITH_OPENGL_GLFW=ON" "-DLIBIGL_WITH_OPENGL_GLFW_IMGUI=ON" "-DLIBIGL_WITH_PNG=ON" "-DLIBIGL_WITH_XML=OFF" "-DLIBIGL_WITH_PYTHON=OFF" "-DLIBIGL_BUILD_TESTS=OFF" "-DLIBIGL_BUILD_PYTHON=OFF" "-DLIBIGL_EXPORT_TARGETS=ON" "-DLIBIGL_USE_STATIC_LIBRARY=OFF" "-DLIBIGL_WITH_COMISO=OFF" "-DLIBIGL_WITH_TETGEN=OFF" "-DLIBIGL_WITH_TRIANGLE=OFF" "-DLIBIGL_WITH_PREDICATES=OFF" "-DLIBIGL_BUILD_TUTORIALS=OFF" "-DPYTHON_EXECUTABLE=" "-DCMAKE_MAKE_PROGRAM=C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Libraries/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v142" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/Libraries/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=C:/Libraries/vcpkg/packages/libigl_x64-windows""
-- The C compiler identification is MSVC 19.23.28106.4
-- The CXX compiler identification is MSVC 19.23.28106.4
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.23.28105/bin/Hostx64/x64/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- MSVC -> forcing use of statically-linked runtime.
-- Looking for pthread.h
-- Looking for pthread.h - not found
-- Found Threads: TRUE
-- Creating target: igl::core (igl)
-- Creating target: igl::embree (igl_embree)
-- Creating target: igl::opengl (igl_opengl)
-- Found OpenGL: opengl32
-- Creating target: igl::opengl_glfw (igl_opengl_glfw)
-- Creating target: igl::opengl_glfw_imgui (igl_opengl_glfw_imgui)
-- Creating target: igl::png (igl_png)
CMake Error at cmake/libigl.cmake:398 (target_include_directories):
  target_include_directories may only set INTERFACE properties on INTERFACE
  targets
Call Stack (most recent call first):
  CMakeLists.txt:46 (include)

-- Configuring incomplete, errors occurred!
See also "C:/Libraries/vcpkg/buildtrees/libigl/x64-windows-rel/CMakeFiles/CMakeOutput.log".
See also "C:/Libraries/vcpkg/buildtrees/libigl/x64-windows-rel/CMakeFiles/CMakeError.log".
ninja: build stopped: subcommand failed.

Will fix it after #8813 merge.

@JackBoosY libigl doesn't depend on nanovg, does it?
It is just me that have both installed on my system.

@xarthurx Fix nanovg so the CI system will not report that error anymore.

have you solved this problem @xarthurx ?

@mfxu  The https://github.com/microsoft/vcpkg/pull/8813 is still not merged yet. And I guess libigl can only be fixed after that. @JackBoosY  Correct?
And it seems the CI system is down again.
I'm using the source version from igl repo directly, with other libs from vcpkg. Quite straightforward to compose the cmakelist file.

@xarthurx Yep, I'm waiting for #8813 merge then I will fix this issue.

#8813 has been merged, I will fix this issue later.

Will this issue be fixed any longer?

@xarthurx Fixing... we have lots of issues need to resolved.


https://github.com/base-org/node/releases/tag/v0.10.2

https://github.com/base-org/node/releases/tag/v0.10.2

Originally posted by @amethystens in https://github.com/pararang/gostein/issues/37#issuecomment-2380563982

https://github.com/base-org/node/releases/tag/v0.10.2

Originally posted by @amethystens in https://github.com/pararang/gostein/issues/37#issuecomment-2380563982


hyper upgrade to v1

https://hyper.rs/guides/1/upgrading/
https://hyper.rs/guides/1/server/hello-world/
https://docs.rs/hyper/latest/hyper/index.html
https://docs.rs/hyper-util/latest/hyper_util/index.html
https://docs.rs/http-body-util/0.1.1/http_body_util/
https://github.com/hyperium/hyper/blob/master/examples/web_api.rs

fixed w/ #62


Foam event spreads way too much foam

Description
Foam random event radius can be over 10 tiles long, leading to scenarios where it can be literally impossible to avoid the foam

In this image the black foam is coming from a vent below the firelocks behind the wall. This foam killed a service worker and flooded the entire room.

I'm refactoring smoke atm to use the same spreader code as kudzu / puddles so this should be looked at after that.

Anyone looking at this - wait for sloth's refactor then go off of that.


Can you make a css framework?

I dont know how to use it with "react".
But I still want to use this perfet framework.
Pls make a css framework.
So many thanks~

@haohao066 You may want to check out http://www.getmdl.io/ or http://materializecss.com/ for css material design frameworks.
Also related to #262


Front end/ga virtual page views

This is done. Will need to review it with Trent and possibly make tweaks.


Remove negations

I think we should add a new function modify_constant that does the modifications you implemented. I.e, negating a constant or adding 1 to it. We can than add this to the random choice on line 65. That would mean you don't have to walk trough expression tree again in the modification function.
Same holds for the remove_negation
These are certainly good cases or "bugs" we can introduce!
However, modifying constraints inplaces is tricky as they may occur in different subexpressions and are thus changed there as well.


WCA Live Suggestions

As a scoretaker, I have a few suggestions for how to improve WCA live in order to make data entry much easier. First, I believe that in addition to the recently added bulk quitting feature, one should be able to enter a competitor's id or name as if they were entering their times, and a button to quit them should come up along with the time slots. The other suggestion I have is being able to see completion ids in non-scoretaker mode to make writing scorecards easier, so you don't have to sign in.

one should be able to enter a competitor's id or name as if they were entering their times, and a button to quit them should come up along with the time slots

I think what we can do is have an option to see the same menu as when clicking result in the table. I opened #185.

The other suggestion I have is being able to see completion ids in non-scoretaker mode to make writing scorecards easier, so you don't have to sign in.

The ids are not really relevant for the general public, so I wouldn't do that. I'm fine with showing the id on the specific competitor page, but not sure if that helps much for your use case.


Funcs break init method

Given the following canister:
import { bool, Canister, Func, init, nat16 } from 'azle';

const SimpleFunc = Func([bool], nat16, 'query');

export default Canister({
    init: init([SimpleFunc], () => {})
});

When running dfx build,
Then the following canister is generated:
service: (func (bool) -> {

}

Resulting in the following error:
Building canisters...
Executing 'npx azle canister'

Building canister canister

Done in 3.41s

🎉 Built canister canister at .azle/canister/canister.wasm

error: parser error
  ┌─ /src/index.did:1:26
  │
1 │ service: (func (bool) -> {
  │                          ^ Unexpected token
  │
  = Expects "("

Error: Failed while trying to build all canisters.
Caused by: Failed while trying to build all canisters.
  The post-build step failed for canister 'bkyz2-fmaaa-aaaaa-qaaaq-cai' (canister) with an embedded error: Candid file check failed for /src/index.did.: Candid parser error: Unrecognized token `LBrace` found at 25:26
Expected one of "(": Unrecognized token `LBrace` found at 25:26
Expected one of "("

To clarify the candid we would expect to be generated from this canister is
service: (func (bool)) -> {

}

So we're just missing an extra ) after bool

The actual problem was that it was dropping everything after the -> because of how the service visitor works, after updating that I think it should work


Remove unnecessary govuk class

You can preview this change here:
Built with commit dbe3c66d8517bce026ecd6817b65d60adef6e0cf
https://deploy-preview-170--govuk-design-system-preview.netlify.com


ARROW-514: [Python] Automatically wrap pyarrow.io.Buffer in BufferReader

This is a very minor change. +1


debug: fix ISDEBUG checking

Describe your PR, what does it fix/add?
ISDEBUG macro is always defined so checking it with #ifdef is a bug. Use #if ISDEBUG instead.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
No.
Is it ready for merging, or does it need work?
Ready to merge.


add arrow in relation instead of lines

From<EMAIL_ADDRESS>on March 29, 2013 12:35:54
What steps will reproduce the problem? 1. Create relation via foreing key between two elements
2. Line between two elements appeared What is the expected output? What do you see instead? Expected: Arrow that come from owner of foreing key to related entity What version of the product are you using? On what operating system? appVersion: "5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22"
platform: "Win32"
Original issue: http://code.google.com/p/wwwsqldesigner/issues/detail?id=171

From ondrej.zara on March 29, 2013 06:31:40
Status: Duplicate
Mergedinto: 60


Use Case Save Itinerary - Save as .md

Updated the Save functionality to save a markdown file instead of the .txt file. It will output the below:

Also removed a bunch of commented lines.

LGTM!

LGTM


Further separation of code and data

Further separation of code and data

The sqrS is taken now from the MetaData
Also a bugfix: the sqrtS is now has a consistent value in the whole code.

Should be merged after #91

This works after the update of reference.


HRM issue after changing one character in default setup

Description
What I did:
In a WSL-2 Terminal (Win 10) with Ubuntu-22-04 and node v18.14.2:
pnpm create @batijs/app --vue --tailwindcss --express --eslint --prettier
cd my-app/
pnpm install
code .
pnpm run dev
In VSCode I changed

Rendered to HTML.

to

Rendered to HTML!

After <Ctrl-S> I got:
Error<EMAIL_ADDRESS>You stumbled upon a Vike bug. Go to https://github.com/vikejs/vike/issues/new and copy-paste this error. A maintainer will fix the bug (usually under 24 hours).
at getFilePathAbsoluteUserRootDir (file:///home/wulf/projekte/bati/my-app/node_modules/.pnpm/vike@0.4.168_vite@5.2.7/node_modules/vike/dist/esm/node/plugin/shared/getFilePath.js:90:5)
at getFilePathResolved (file:///home/wulf/projekte/bati/my-app/node_modules/.pnpm/vike@0.4.168_vite@5.2.7/node_modules/vike/dist/esm/node/plugin/shared/getFilePath.js:18:39)
at reloadConfig (file:///home/wulf/projekte/bati/my-app/node_modules/.pnpm/vike@0.4.168_vite@5.2.7/node_modules/vike/dist/esm/node/plugin/plugins/importUserCode/index.js:122:50)
at listener (file:///home/wulf/projekte/bati/my-app/node_modules/.pnpm/vike@0.4.168_vite@5.2.7/node_modules/vike/dist/esm/node/plugin/plugins/importUserCode/index.js:77:13)
at FSWatcher. (file:///home/wulf/projekte/bati/my-app/node_modules/.pnpm/vike@0.4.168_vite@5.2.7/node_modules/vike/dist/esm/node/plugin/plugins/importUserCode/index.js:66:50)
at FSWatcher.emit (node:events:525:35)
at FSWatcher.emit (node:domain:489:12)
at FSWatcher.emitWithAll (file:///home/wulf/projekte/bati/my-app/node_modules/.pnpm/vite@5.2.7/node_modules/vite/dist/node/chunks/dep-C-KAszbv.js:45880:8)
at FSWatcher._emit (file:///home/wulf/projekte/bati/my-app/node_modules/.pnpm/vite@5.2.7/node_modules/vite/dist/node/chunks/dep-C-KAszbv.js:45972:8)
at NodeFsHandler._handleFile (file:///home/wulf/projekte/bati/my-app/node_modules/.pnpm/vite@5.2.7/node_modules/vite/dist/node/chunks/dep-C-KAszbv.js:44557:14)
at NodeFsHandler._addToNodeFs (file:///home/wulf/projekte/bati/my-app/node_modules/.pnpm/vite@5.2.7/node_modules/vite/dist/node/chunks/dep-C-KAszbv.js:44794:21)
 ELIFECYCLE  Command failed with exit code 1.
Thx!

Insert the following before line 90 of /home/wulf/projekte/bati/my-app/node_modules/.pnpm/vike<EMAIL_ADDRESS>and report back. (It seems to be a Windows issue but I don't have a Windows setup atm.)
+ console.log('filePathAbsoluteFilesystem', filePathAbsoluteFilesystem);
+ console.log('userRootDir', userRootDir);
+ console.log('filePathRelative', filePathRelative);
    assert(!filePathRelative.startsWith('.') && !filePathRelative.startsWith('/'));

Thanks for this super fast response!
I don´t expect a Windows-issue. WSL is the "Windows subsystem for Linux" and provides a native Linux-VM including original Filesystem similar to what you get inside a docker container. So the developement is done in Ubuntu 22.04.
After inserting the thee new commands I see this log between server start end error exit:
Server listening on http://localhost:3000
filePathAbsoluteFilesystem /home/wulf/projekte/bati/my-app/.history/pages/index/+Page_20240402105314.vue
userRootDir /home/wulf/projekte/bati/my-app
filePathRelative .history/pages/index/+Page_20240402105314.vue
Error<EMAIL_ADDRESS>You stumbled upon a Vike bug. Go to https://github.com/vikejs/vike/issues/new ...

Indeed, it isn't a Windows issue.
What is the .history/ directory and the +Page_20240402105314.vue file? Is that a Tailwind thing?

line 90 of /home/wulf/projekte/bati/my-app/node_modules/.pnpm/vike<EMAIL_ADDRESS>
If you remove the assertion    assert(!filePathRelative.startsWith('.') && !filePathRelative.startsWith('/')); does it work then?

Bingo! That´s it. No issues anymore after removing the assertion!
Great work! I did not notice .history in the error message.
.history is created by VS-Code local history plugin and should not be included.
But expect this to be present on many machines. It can be extremely useful even if git is active.
After removing .history and editing +Page.vue with another editor, HMR was working fine.
I investigated if adding .history to .gitignore helps. Some tools respect these entries.
But here it did not show any effect. HMR still crashed the dev-server.
So it should be possible to restrict the directories that were parsed during HMR, right?

Fix pre-released as<EMAIL_ADDRESS>
adding .history to .gitignore

That should actually make Vike ignore .history.
Related: https://github.com/vikejs/vike/issues/1593.
Let me know if you still run into issues.
In case that's something your company be up for, we're looking for sponsors — it makes a massive difference.

Thank your for your quick help!
I will continue to evaluate vike and see if we can use it for our project.
Currently our company is a bit too far away from break even to think about sponsoring.
But I will keep it in mind!

Makes sense and thanks for circling back on this.
Grüße zurück :)


Update helm to v3.5.1

This commit uses our updated helm fork on top of v3.5.1
closes: #1037
Signed-off-by: knrt10<EMAIL_ADDRESS>

Weird, make build passes locally for me

@knrt10 some of those deps might be saved in your local go mod cache.

Closing in favour of #1358


[python3] update to 3.10.5

Library name: python3
New version number: 3.10.5
https://docs.python.org/3/whatsnew/changelog.html#python-3-10-5-final
https://www.python.org/downloads/release/python-3105/
https://www.python.org/ftp/python/3.10.5/
https://github.com/microsoft/vcpkg/blob/0cf5b4305ba811d069d3ce328261eeb54bf61c3a/scripts/vcpkgTools.xml#L1-L6

#25105

The python3 tool and port need to match exactly. Please update them together, see my PR.


Null safety support

I will make a PR with null safety support implementation

Thanks @leynier
If it helps, this is done for the search_choices plugin.

Looks like the PR is failing some tests.

Looks like the PR is failing some tests.

yes, but this is a problem just if you want to use it for linux platform

I was just checking out the https://github.com/lcuis/search_choices fork, so I assume we should be going with that fork?

I was just checking out the https://github.com/lcuis/search_choices fork, so I assume we should be going with that fork?

you can do whatever you want

Hi guys, anybody know how to fix this issue in the searchable_dropdown flutter plugin? or anybody can tell me please which other dropdown with search can i to use ?


add default options in README.md

Type of change

[x] Docs

Hey! These seem like sensible changes! Thanks!


🐛 Bug Report: TechDocs backstage-auth cookie set failure

📜 Description
"This attempt to set a cookie via set-cookie header was blocked because its domain attribute was invalid with regards to the current host url." So my company is using 2 different url for ui and backend. For ui, its something like xxx.company.com and for backend, it's xxx-backend.company.com. When I navigate to any documentation page, there is an api call to /api/techdocs/.backstage/auth/v1/cookie and the response header includes set-cookie with backstage-auth and domain. The domain value is xxx-backend.company.com. But since it does not match the domain of the ui, it is failing to set the cookie with above error and because of that, api call to /stylesheets/main.min.css is getting 401. How should I fix this issue?
👍 Expected behavior
backstage-auth cookie to be set
👎 Actual Behavior with Screenshots
Fails to set backstage-auth cookie with the above error
👟 Reproduction steps
Navigate to any page with documentations.
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

What domain is the /stylesheets/main.min.css and /api/techdocs/.backstage/auth/v1/cookie requests towards? The host for the cookie being xxx-backend.company.com is correct, since the cookie is needed for requests to the backend rather than frontend. The TechDocs resource requests should also be towards xxx-backend.company.com too, as should the request to /api/techdocs/.backstage/auth/v1/cookie. It almost seems like those requests are towards xxx.company.com, but in that case I wouldn't expect them to work at all?

All the plugins are making api calls to xxx.company.com url, but they get routed to xxx-backend.company.com eventually, so they are working

@jhl0214 ah, well in that case the xxx-backend.company.com is just an internal detail, you should configure your backend.baseUrl to use xxx.company.com in both the frontend and backend


Remove hardcoded placeholder encryption key.

Changes

Removes hardcoded placeholder encryption key.

For review: @angaither @jonuy

:+1:


Parse HTML in order to find anchors (like #tomato) in the same document

markdown-link-check doesn't parse HTML, so it can't find #tomato in your test, but it is something I'm planning on adding.
Originally posted by @tcort in https://github.com/tcort/markdown-link-check/issues/193#issuecomment-1076250098

This would be nice to have back again. It used to work in 3.8.7 and no longer works in 3.9.3 or 3.10.2.

Hello! Was curious about the status of this because anchor links are valid markdown but they are all currently broken when checking if links are valid

@Shocktrooper
This issue is about anchor links defined in HTML. Is that the same issue that you have?
Steps to reproduce failure
195.md file contains:
- [Open Issues](#issue_list)
Open Issues

npm install<EMAIL_ADDRESS>npx markdown-link-check ./195.md

FILE: ./195.md
[✓] #issue_list

1 links checked.

Now update to latest version:
npm install<EMAIL_ADDRESS>npx markdown-link-check ./195.md

FILE: ./195.md
  [✖] #issue_list

  1 links checked.

  ERROR: 1 dead links found!
  [✖] #issue_list → Status: 404

Steps to reproduce correct checking of anchor links
If the anchor link is defined through Markdown (no use of HTML in Markdown file), then the check works:
[link to issues](#issues)
# issues

FILE: ./195-b.md
  [✓] #issues

  1 links checked.

Oh my apologies my issue is plain anchor links in markdown. Not html

@Shocktrooper

... my issue is plain anchor links in markdown. Not html

Perhaps you could give an example of a failing test? Also which version of markdown-link-check are you using? Does my example give an error or does it work for you?
[link to issues](#issue-list)
# issue list

I am still stuck with using "markdown-link-check": "~3.8.7" due to this regression. Is there any chance of getting it fixed in 3.10.* or later?

@MikeMcC399 It appears that I had an issue with my syntax that was not apparent and it is not an issue with the tool

@Shocktrooper would you be able to give an example of what the syntax issue was and how it was fixed? just in case that's what i or others are running into.

for ## Architecture-Diagram
[Architecture Diagram](#_Architecture_Diagram)
was changed to
[Architecture Diagram](#architecture-diagram)
and for ## Access and authentication
[Authentication](#_Authentication)
was changed to
[Authentication](#access-and-authentication)
The first example was an old and valid way that anchor links worked in an older version of markdown and the second example was just a rename someone forgot I believe

@MikeMcC399 Sorry to revive an old conversation, but just to be clear, versions 3.8 and prior reported "success" on internal anchor links, but the fact is, it was an unproven positive. Try to change the fragment to any gibberish, and it will pass with flying colours. The solution I see at the moment, until the issue is fixed, is to ignore URLs that consist entirely of fragments. This way they will remain explicitly unchecked, showing up in the report as ignored.

@jhvhs
No need to apologize for responding to an open issue, however old it is!
Shockingly you are correct!
A bad anchor link is not detected in 3.8.7. All pass.
An anchor link which is not embedded in HTML passes in 3.10.3. - correct
An anchor link which is embedded in HTML fails in 3.10.3. - subject of this issue. Would expect to pass but it fails.
An anchor link to a non existent target fails in 3.10.3 - correct
Tested with:
- [Good regular link](#link1)
- [Good link in HTML](#link2)
- [Bad link](#link3)
# link1
Link 2

You can try https://github.com/lycheeverse/lychee

@tcort
Do you have any comments on this thread?

Has there been any progress on this issue?

I have created a PR to solve the issue.

#331

Rreviews or suggestions for improvement are welcome.

It looks like this issue is resolved, since https://github.com/tcort/markdown-link-check/pull/331 is now merged.


I keep on getting this error every time my terminal tries to load a theme

/Users/Felipe/.oh-my-zsh/oh-my-zsh.sh:source:110: no such file or directory: /Users/Felipe/.oh-my-zsh/themes/“robbyrussell”.zsh-theme
It´s weird though, because all the files are where they are supposed to be, and the code in oh-my-zsh.sh which loads the themes seems also correct.
if [ "$ZSH_THEME" = "random" ]; then
  themes=($ZSH/themes/*zsh-theme)
  N=${#themes[@]}
  ((N=(RANDOM%N)+1))
  RANDOM_THEME=${themes[$N]}
  source "$RANDOM_THEME"
  echo "[oh-my-zsh] Random theme '$RANDOM_THEME' loaded..."
else
  if [ ! "$ZSH_THEME" = ""  ]; then
    if [ -f "$ZSH_CUSTOM/$ZSH_THEME.zsh-theme" ]; then
      source "$ZSH_CUSTOM/$ZSH_THEME.zsh-theme"
    elif [ -f "$ZSH_CUSTOM/themes/$ZSH_THEME.zsh-theme" ]; then
      source "$ZSH_CUSTOM/themes/$ZSH_THEME.zsh-theme"
    else
      source "$ZSH/themes/$ZSH_THEME.zsh-theme"
    fi
  fi
fi

If anyone could help me out I would really appreciate it.

I'm getting the same error, anyone have an idea how to fix it?

Check out the double quotes of the ZSH_THEME variable in your zshrc file. It seems they are smart quotes (“”) instead of simple quotes ("").

Did you copy that line from somewhere?

if [ "$ZSH_THEME" = "random" ]; then
  themes=($ZSH/themes/*zsh-theme)
  N=${#themes[@]}
  ((N=(RANDOM%N)+1))
  RANDOM_THEME=${themes[$N]}
  source "$RANDOM_THEME"
  echo "[oh-my-zsh] Random theme '$RANDOM_THEME' loaded..."
else
  if [ ! "$ZSH_THEME" = ""  ]; then
    if [ -f "$ZSH_CUSTOM/$ZSH_THEME.zsh-theme" ]; then
      source "$ZSH_CUSTOM/$ZSH_THEME.zsh-theme"
    elif [ -f "$ZSH_CUSTOM/themes/$ZSH_THEME.zsh-theme" ]; then
      source "$ZSH_CUSTOM/themes/$ZSH_THEME.zsh-theme"
    else
      source "$ZSH/themes/$ZSH_THEME.zsh-theme"
    fi
  fi
fi

The quotes in my oh-my-zsh.sh file are fine but I'm still getting the same error

Check out the double quotes of the ZSH_THEME variable in your zshrc file.

That fixed it, thanks mcornella!


fix "Adding Dynamic Endpoints" link in endpoint-types.md

Purpose

Link Adding Dynamic Endpoints was wrong.

Goals

fix the link.

Approach

I search the original linked file in history and I found a commit that rename it. https://github.com/wso2/docs-apim/commit/aac8439e16f532537893e15e688dd7eacbaa1c7a?short_path=8a7ac90#diff-8a7ac90b31ab0df21ef79aea7729afc3a6c85ede1cc4becf392ec6aacf89f111

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

I've sign Licence Agreement and add email address of commit to my account.


allow node pool overrides from a variable

It's surprisingly difficult to create a good structure for node pools & their overrides. I don't want to re-specify all the node pools when changing one variable and I don't have a way of doing that at the moment. Terraform 0.15 seems to be addressing this, but we're not there yet.
Goal is to override the platform VM size.

@steved Just curious, what's the upgrade plan for v0.15 and/or any blockers?

@steved Just curious, what's the upgrade plan for v0.15 and/or any blockers?

At the moment, it's the existing stuff out there that would need to automatically transition past 0.13 (or stay on 0.12).

Its more than that for 0.15.  Most of the deprecation that occurred in 0.12 and 0.13 are now removed as required.


[freealut] Code review for PR 20851 at ConanCenterIndex

Remove patches
Use cmake defines instead of patching find_package
Remove not desired artifacts instead of patching
Use only official defines for dll export
Update project URL according to AUR and Brew
Add system libraries listed in upstream's CMakeLists.txt

[ ] I've read the contributing guidelines.
[ ] I've used a recent Conan client version close to the currently deployed.
[ ] I've tried at least one configuration locally with the conan-center hook activated.

It is easy to make it build as a shared lib for Windows, maybe the best is to drop the static build for now. The old Alut was delivered as a shared lib to windows anyways.

thanks


feat: POST for document search requests

This refactors the ietf.doc.search() view and some adjacent views to require a POST, including a CSRF key, before executing a document search. Search parameters are expected in the request body instead of the URL query string.
If a GET request with a query string is received the search is not executed. The user is sent back to the search page with the form pre-filled using the values from their request and an error box at the top of the page indicates that the GET interface is deprecated. (Maybe there's a better term - it's actually been retired - so suggestions on phrasing are welcome.)
I've refactored the cache key calculation and moved it into the SearchForm since it depends on details internal to the form. This helps with a circular import problem.
The SearchForm and results cache is reused in the stats module. I've so far refactored this to use the updated form but not to switch it over to POST. I haven't seen anything actually hit that endpoint in over 30 days (though I haven't exhaustively searched logs), so maybe it's better to drop it. That'd allow removal of an additional helper function that really doesn't need to exist.
A few things left before taking this out of draft:

[x] check / update tests
[x] rephrase the messages.error() notice to reflect that the GET interface is retired, not just deprecated
[x] confirm that the expensive forms of /doc/<some-value> are all covered by this patch

The search_for_name view is probably in need of a refactor, but it's really a separate task so I'm not going to change it here.
When no simple match is found, a redirect to the GET-based search is returned. I think that's ok - we want to wean people away from using /doc/whatever as an alias for searching.

It'd also be nice to update the search_form.html template to display form validation errors. I'm on the fence as to whether that's a separate feature or belongs here. Thinking it is probably separate and that the better fix should also handle opening the "Additional search criteria" accordion when non-default options are selected.

Marking as draft until #8210 is merged. I'll pull that into this branch and do cleanup here.


Unable to load InceptionV3 model (npm<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Hi,
When I try to load inceptionV3 model in keras-js I get following error:
Error: cwise: Arrays do not all have the same shape!
at assign_cwise_thunk (eval at createThunk (backgroundscript.js:113190), <anonymous>:8:71)
at Object.assign_ndarrayops [as assign] (eval at makeOp (backgroundscript.js:2705), <anonymous>:3:43)
at Conv2D._padInput (backgroundscript.js:31435)
at Conv2D._callCPU (backgroundscript.js:31502)
at Conv2D.call (backgroundscript.js:31393)
at Model._traverseDAG (backgroundscript.js:102501)
at Model._traverseDAG (backgroundscript.js:102515)
at <anonymous>

The model is prepared in a following manner:
1: The model is loaded and then exported in keras using following code:
keras.applications import InceptionV3
inceptionModel = InceptionV3(weights="imagenet", include_top=False)
model.save(myPath)

2: The model is than encoded using latest(see the commit below) keras-js encoder.py
commit df999159284abc5de0b92bc0f801375c08bf9008 (HEAD -> master, origin/master, origin/HEAD)
Author: Leon Chen<EMAIL_ADDRESS>Date:   Fri Feb 9 10:15:28 2018 -0500
update demos build

The aforementioned error is generated when the model is loaded by keras-js using following code:
var KerasJS = require('keras-js');
let model = new KerasJS.Model({
    filepath: modelPath,
    gpu: false
})

What I find peculiar is that the inceptionv3 model loaded in keras-js example differs than the one that I generate.
small part of configuration part of model generated by me:
$b7dfac6a-dd00-4849-bb31-769a6397f93dmodel2.1.2"
tensorflow*˙ö{"class_name": "Model", "config": {"layers": [{"class_name": "InputLayer", "config": {"sparse": false, "dtype": "float32", "batch_input_shape": [null, null, null, 3], "name": "input_1"}

full model configuration here -> https://www.dropbox.com/s/o42oc243huqqlbk/myModel.txt?dl=0
small part of configuration part of model used in example:
$7db1fe5f-c96e-4804-b1bc-f399146eaa0cinception_v32.0.9"
tensorflow*ýö{"class_name": "Model", "config": {"name": "inception_v3", "layers": [{"name": "input_1", "class_name": "InputLayer", "config": {"batch_input_shape": [null, 299, 299, 3], "dtype": "float32", "sparse": false, "name": "input_1"}

full model configuration here -> https://www.dropbox.com/s/7ld1pmbjsj5g8fo/exampleModel.txt?dl=0
Issue happens in following environment
npm<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I've spent whole day on this issue and couldnt find the solution. Any help would by greatly appreciated.

Maybe you should specify your model input to be (None, 299, 299, 3).

KerasJS doesn't support None, internally model with shape let say  (None, 299, 299, 3) would be represented as  (299, 299, 3).

Thanks,
Loading model in a following way did the trick:
inceptionModel = InceptionV3(weights="imagenet", include_top=False, input_shape=(299, 299, 3))


[Bug]: Possible isolated analysis bug when using alternate wait on workers

Description
The compiler incorrectly exits with an error when I use alternate wait with named workers.
Steps to Reproduce
Sample code
isolated function foo() returns string|error {
    worker A returns string {
        return "Hello from A";
    }

    worker B returns string {
        return "Hello from B";
    }

    worker C {
        string c = wait A | B; // line 11
        c -> function;
    }

    return <- C;
}

bal build output
Compiling source
        sameera/hello_world:0.1.0
ERROR [main.bal:(11:25,11:26)] invalid access of mutable storage in an 'isolated' function
ERROR [main.bal:(11:29,11:30)] invalid access of mutable storage in an 'isolated' function
error: compilation contains errors

Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

I suspect worker references are not treated as isolated variables. In the implementation, each worker is desuggered into a top-level function. So for the wait action, those variable references are global, which results mentioned error. This needs to be fixed from the compiler side.

Same with single wait.
This actually isn't allowed since the reference to A (and/or B) is considered a captured variable and the type is not a subtype of readonly|isolated object {}. I think the current behaviour is correct and in-line with the spec.
https://ballerina.io/spec/lang/master/#isolated_functions

A variable reference to a captured variable must refer to variables that are both final (either explicitly or implicitly) and have a static type that is a subtype of readonly|isolated object {}, where a variable reference is captured if it occurs within an anonymous-function-expr or named-worker-decl and refers to a variable declared within the function but outside of that anonymous-function-expr or named-worker-decl.

A, which is treated as a captured variable, is considered final, but the type is not a subtype of readonly|isolated object {}.
Similar to
isolated function foo() returns string|error {
    final future<string> A = start fn(); // final, but not immutable or an isolated object

    worker C {
        string c = checkpanic wait A; // also invalid access error for `A`
        c -> function;
    }

    return <- C;
}

isolated function fn() returns string => "Hello from A";

Closing this issue since the current behaviour is in line with the spec, and there's a spec issue (https://github.com/ballerina-platform/ballerina-spec/issues/1275) to check on the possibility of allowing this.


[stable/prometheus-operator] grafana graphs are broken again

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes:
helm version
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

Which chart: stable/prometheus-operator
What happened: updated from 5.1.0 to 5.3.0
How to reproduce it (as minimally and precisely as possible):
values.yaml> http://paste.openstack.org/show/750115/
helm install stable/prometheus-operator --namespace kube-system --name prometheus-operator --version v5.3.0 --values values.yaml

I might be having this issue myself, though the original description is a bit vague.
Installed prometheus-operator via helm with the values.yaml provided in the repo. I'm able to access and query prometheus without issue when port-forwarding 9090, however when port-forwarding grafana, all the pre-built queries time out.
Oddly I tested this chart out a few weeks ago and it all worked very well out-of-the-box, it wasn't until I went to actually install it in my real cluster that this issue appeared.
Info
Helm Version:
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

K8S Version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T15:23:04Z", GoVersion:"go1.9.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.8-gke.6", GitCommit:"394ee507d00f15a63cef577a14026096c310698e", GitTreeState:"clean", BuildDate:"2019-03-30T19:31:43Z", GoVersion:"go1.10.8b4", Compiler:"gc", Platform:"linux/amd64"}

Chart Version: 5.5.0

For me the graphs Most of the charts are ok. But some of them are missing values (mainly the last 2 from the grafana defaults). I suspect it's the new time series created by the evaluation rules

with chart stable/prometheus-operator:5.5.0 works for me.
Closing


[Feature request] Volume support

I just pushed an update here (not to PyPi yet) that will allow you to override the default key mappings and add new key mappings.
In your ~/.config/roku/roku.config file create a new section called keymap, and add the new and overridden key/value pairs, where the key is one of the strings here (I don't think case matters, but when in doubt, lowercase).
for example, if you wanted the keys 1, 3, 5, and 7 to be your directions:
[keymap]
up=1
down=3
left=5
right=7

All other keys will remain defaulted.
I do not have a Roku TV and so can't test the volume controls, but theoretically it should work with volumeup, etc. Additional keys should respond, but won't visually appear as part of the remote.
Let me know how you make out!


Fix transient cryptography dependency in testing.test_client.client

PR Checklist

[ ] Have you followed the guidelines in CONTRIBUTING.md?
[ ] Have you got 100% test coverage on new code?
[ ] Have you updated the prose documentation?
[ ] Have you updated the reference documentation?

Closed in favor of #711


[iOS] crash with latest release

Current behavior
Fatal Exception: NSInternalInconsistencyException
0  CoreFoundation                 0x1a2975ea4 __exceptionPreprocess
1  libobjc.A.dylib                0x1a1b45a50 objc_exception_throw
2  CoreFoundation                 0x1a287c484 -[NSCache init]
3  Foundation                     0x1a33eb938 -[NSObject(NSKeyValueObserving) observeValueForKeyPath:ofObject:change:context:]
4  Klarna                         0x100d95068 -[RCTVideo observeValueForKeyPath:ofObject:change:context:] (RCTVideo.m:696)
5  Foundation                     0x1a33eba9c NSKeyValueNotifyObserver
6  Foundation                     0x1a33edf30 NSKeyValueDidChange
7  Foundation                     0x1a33eb324 NSKeyValueDidChangeWithPerThreadPendingNotifications.llvm.11394337073705085640
8  AVFoundation                   0x1a89ec848 __avplayeritem_fpItemNotificationCallback_block_invoke
9  libdispatch.dylib              0x1a23ad6c8 _dispatch_call_block_and_release
10 libdispatch.dylib              0x1a23ae484 _dispatch_client_callout
11 libdispatch.dylib              0x1a235a9a4 _dispatch_main_queue_callback_4CF$VARIANT$mp
12 CoreFoundation                 0x1a2905ce4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
13 CoreFoundation                 0x1a2900bac __CFRunLoopRun
14 CoreFoundation                 0x1a29000e0 CFRunLoopRunSpecific
15 GraphicsServices               0x1a4b79584 GSEventRunModal
16 UIKitCore                      0x1cfb10c00 UIApplicationMain
17 Klarna                         0x10097e8cc main (main.m:14)
18 libdyld.dylib                  0x1a23bebb4 start

Reproduction steps
just has a crash log.
Expected behavior
No Crash
Platform

iOS

Which version of Xcode? Which version of macOS? Which version of iOS? Simulator? Device? Could you try to reproduce this with react-native init and install into a new project. Also try cleaning the build.

Crash log is from crashlytics/firebase/sentry. Latest xcode, latest macos.
version in project that works fine: "react-native-video": "^2.0.0"
Android part works fine, iOS produce a crash on end-user devices. We cannot reproduce it on the local devices. So its some kind of corner cases.

Which version of react-native-video is crashing?

We can try and track this down but need the version of react-native-video to be able to match the line number from the crash to the right line of code in a given release.

used latest release 4.4.0 @FullstackJack

https://stackoverflow.com/questions/6574714/whats-wrong-with-this-observevalueforkeypathofobjectchangecontext-implement

If I'm not mistaken, the super classes of this class do not implement the method observeValueForKeyPath method. It's probably safe to remove it.

Can anybody create/commit a fix for the crash?

check 5.0.2


Fix: Remove var.region

what

Remove var.region variable.
Add count meta-attributes to data sources.
Use aws_region data source in place of var.region.

why

Modules do not usually contain var.region, only components do.
Adding a count meta-attribute to all resources and data sources based on module.this.enabled is best-practice as it prevents Terraform from populating the Terraform state needlessly if the module is disabled.

references

N/A

/test all

/test all

/test all

test/bats are failing because terraform validate . doesn't take into account that the provider is pinned to 3.x
https://github.com/cloudposse/terraform-aws-mwaa/blob/4c53a71676c1aba98afd453bb9546113580939c4/test/Makefile#L36-L38
± |fix/region-var ?:1 ✗| → terraform validate .
╷
│ Error: Unsupported attribute
│
│   on .terraform/modules/mwaa_s3_bucket/main.tf line 166, in resource "aws_s3_bucket" "default":
│  166:         for_each = local.s3_replication_rules == null ? [] : local.s3_replication_rules
│
│ This object does not have an attribute named "s3_replication_rules".

/test all

/test all


green screen, everything in right folder

From experience this usually happens because the gamestate_integration_drweissbrot_hud.cfg isn't in the right spot. To be clear, it should be inside the C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg directory (unless you changed Steam's or the game's install location).
There should be files like boot.vcfg, gamemode_competitive.cfg, and user_keys_default.vcfg in the same folder.
The file needs to be named exactly gamestate_integration_drweissbrot_hud.cfg; maybe there's a .txt in there?
The page will also just stay green as long as you're not either watching a demo, watching a live CSTV match, or on a map and in the spectators team. It may also stay green if the warmup hasn't started yet.
If none of that helps: Could you start a demo, open the HUD page in your browser, press Ctrl+Shift+J, then post a screenshot of the console window?

I have the same problem, my cs2 is located on D:/SteamLibrary, i dont have space enough to store it at C disk, i dont know what to do anymore, since it just doesnt work.

my cs2 is located on D:/SteamLibrary

In your case, the right directory should be D:\SteamLibrary\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg.
If it still doesn't work:

Could you start a demo, open the HUD page in your browser, press Ctrl+Shift+J, then post a screenshot of the console window?

Hi, same trouble

cs2 located on C:/

@MngkLrd Looks like it's working as it should for you; the website in your browser can't actually show the game itself. I do see that that's not entirely obvious from the docs, thanks for pointing it out! :D
To get the game and the HUD in the same place, you need to use either an OBS browser source, or the separate overlay EXE, see https://github.com/drweissbrot/cs-hud/blob/c8f8a93574fe74eb756e46a2d7f6f16a692d4559/readme.md#obs-browser-source for OBS and https://github.com/drweissbrot/cs-hud/blob/c8f8a93574fe74eb756e46a2d7f6f16a692d4559/readme.md#fullscreen-windowed for the overlay app.

@drweissbrot
The "full screen in window" overlay method actually works well. But I think it would be useful to specify what should be run first:

CS2 + match
cs-hud-win
Electron (cs-hud.exe)
Here is my result :)

It would be cool to add the ability to scale the radar via hud settings.

Gonna close this one for now; if you're still having trouble, feel free to comment with a screenshot if you're still having trouble.

Hi, sorry for late response, let me grab you what i see

Ok, looks like it's mostly working for you now. The browser source probably needs to be a different size, and you'll need a Game Capture or so behind it, but I'm sure you can figure that out yourself :D
If this works for you (I personally just look at OBS while recording), you don't really need to do anything else.
If you want to overlay the HUD on top of the game, follow the instructions under Fullscreen Windowed in the readme.

i have tried them all
wont work

Not sure what you mean by "tried them all"?

game captuire, everything u suggested

Ah, I see -- that sounds like an issue with OBS then. Don't think I can help you out with that, I don't know much about how their software works, sorry.

on obs what should the height etc be?

i have game capture on and its not being transparent

on obs what should the height etc be?

Width and height should be the same as the Base (Canvas) Resolution, as set under File, Settings, Video.

i have game capture on and its not being transparent

The browser source needs to be on top of the game capture.

Make sure that in the browser source's properties, the URL is set to http://localhost:31982/hud?transparent and Custom CSS is completely empty.

that was the issue tysm, also one more thing, do u know how to remove all the ui's in the demo's?

https://github.com/drweissbrot/cs-hud/blob/bcecde36b9d08bfe1b32e995bcbcacd6c716ca4a/docs/cvars.md#cl_draw_only_deathnotices


Follow the example of rocPRIM custom types example but compile failed.

Have tried to write some custom float16 type code by following the example: rocPRIM/test/rocprim/test_utils_custom_test_types.hpp. But after including the header files of rocprim as the following:
#include <rocprim/type_traits.hpp>
#include <rocprim/detail/radix_sort.hpp>

, it shows the following compilation error:
...
/opt/rocm/include/rocprim/types.hpp:164:21: error: ‘_Float16’ does not name a type; did you mean ‘bfloat16’?
 using native_half = _Float16;
                     ^~~~~~~~
                     bfloat16
...

Wonder what has been missing? Should there be any parameters wrongly configured? Or if rocPRIM has been wrongly installed? What could be the cause? Please help! Thanks in advance!

_Float16 is a compiler built-in type that is provided by clang, which is bundled by ROCm. That means that there may be something wrong with the compiler setup that you are using. Could you share how you are compiling the example?
From the compile error, Im guessing that you may be accidentally using g++ to compile, as I get a similar error message (along with a bunch of warnings) if I try that. HIP programs require special compilers support (besides _Float16), so the proper way to compile them is by either using hipcc to compile the executable (hipcc -otest test.cpp), or by using the CMake HIP language support.

error: ‘_Float16’ does not name a type; did you mean ‘bfloat16’?

Thank you! You solved the problem!


Should grammar generation use eval?

I'm wondering if there is a better way to load the Nearly parser generated from the template grammar.
In addition complicating the security analysis, the corresponding code seems also quite brittle:
https://github.com/accordproject/cicero/blob/f79abd8c37d01def5e3525270e3889dc5a405c3e/packages/cicero-core/src/parsermanager.js#L421
E.g., The reliance on the module variable seems to trip certain versions of Babel.
The generated code for<EMAIL_ADDRESS>the generated code is the intended:
      const module = (cov_23ep5x5niw.s[152]++, {
        exports: {}
      });
      cov_23ep5x5niw.s[153]++;
      eval(grammarJs);
      cov_23ep5x5niw.s[154]++;
      return module.exports;

While with<EMAIL_ADDRESS>the code escapes the module variable to _module so the grammar is not extracted properly:
      var _module = (cov_23ep5x5niw.s[152]++, {
        exports: {}
      });

      cov_23ep5x5niw.s[153]++;
      eval(grammarJs);
      cov_23ep5x5niw.s[154]++;
      return _module.exports;

Note that there is an open issue on babel about this module question https://github.com/babel/babel/issues/5718

The new parser no longer uses JavaScript eval for parser construction (or nearley for that matter)...


Adds govukcli to PATH

We have documentation that makes you do this manually. We
should change this documentation after merge:
https://docs.publishing.service.gov.uk/manual/get-ssh-access.html#3-access-remote-environments

We have documentation that makes you do this manually. We
should change this documentation after merge:
https://docs.publishing.service.gov.uk/manual/get-ssh-access.html#3-access-remote-environments

I'm not sure this is the case, if you're referring to [1], that relates to the host machine, which isn't managed by govuk-puppet (which is a guest on the host machine).
1:
Run ln -s ~/govuk/govuk-aws/tools/govukcli /usr/local/bin/govukcli on your host machine to be able to use the govukcli tool from any directory.

Ah, yeah, the first line at least


Not getting into VR mode on quest browser

Not getting into VR mode on quest browser
Description
-just set up the scene project and the camera to use VR

exported the project as html
served locally
pc version correctly shows the vr button
quest browser shows the site correctly in 2d
clicked the vr button but its stuck in the black void and the cursed white ring of loading
uploaded the site to the surge to test it but same result (no immersion mode whatsoever)
project has like one mesh with two materials and the skybox, sub 8k verts, 2k skybox no fancy shaders.

Version

 0.97.8

Platform

Web Version [X]
Oculus Web [X]

Hello
This seems to be a bug i will try to fix it ASAP.
Thanks a lot!

No problem if You need additional info and testing on device let me know.

Same problem here (using oculus quest)

Hello
I have been going crazy trying to figure out what is happening here. The app seems to work fine on the webxr spec emulator for some reason is does not work on mobile devices o.O
Will be trying alternative solutions in the next days.
Thanks a lo!

this is especially weird cause some of the old examples work without any problems like the rollercoaster.
Maybe because of the old api dunno.

After im done with my current task i will start working on this one, to figure out whats going on. It might be related with the post processing stack but i have to test is careful to be sure.
Its weird because i pulled my old oculus DK2 and its seems to work there o.O well i hope i can figure this one out soon. Thanks!

Hello
The VR issues have been solver in the new version 0.98.12 available on the web. I have tested them in android with cardboard and on desktop seems to be working fine now.
Thanks a lot for your patience.
Cheers


Explicit MVD state

Description
First in a series of PRs, with the overall goal being to allow the webapp to load up either an "MVD"-style Node, or a "Gnosis Safe"-style Node.
Notes
This First PR makes absolutely no functional changes, but it does 4 things (as indicated by the 4 commits):

Fixes a typo in a README lol
Removes an unused file
Wraps the top level state returned from useFractal in an object called mvd, to make room for more pieces of top level state
Renames some things up in that state management layer to differentiate between a "DAO" and an "MVD"-style DAO

In the next couple of PRs, reviewers will see the other "top level state" objects that are going to be added, namely:

node, which will be very light, simply holding a property that describes what "kind" of DAO Node this is, either MVD or GNOSIS.
gnosis, which will include state/information about the Gnosis Safe itself.

Issue (if applicable)
n/a
Testing
n/a, no functional changes here. Things should work exactly the same as before this PR.
Screenshots (if applicable)
n/a

Code changes lgtm. One question though. Is the ultimate goal still removing MVD, its contracts and its support from the codebase?

Yeah, that's the ultimate endpoint, removing MVD altogether.  The thought is that adding Gnosis DAO support rather than refactoring the whole thing will make changes easier to review.

@Da-Colon Yes, ultimately.
But the approach I'm taking with these PRs is to "add Gnosis Safe support", rather than "replace MVD support with Gnosis support".
Reason is mostly so that code reviews can go smoother. Also kinda so that if adding Gnosis support takes longer than expected, the whole app isn't broken in the meantime.


Reduce complexity of FullProps type

Effectively reverting #12.
Hey there Codecademy/open-source people!
Recently I was using this in a project that had primarily functional components, ie:
type Props = {
  a: string;
  b?: number
};

export const ConditionalShowField = ({a, b}: Props) => {
  return <div />;
}

And the inferred type of the props for the component and subsequent types down the chain of uses (renderView callback, missing/overriding props, the prop return value) were all coming back as unknown.
It would seem that TS's ability to determine if a passed component extends React.ComponentProps is not as strong as React.ComponentProps's ability to parse the props from functional components.
In my testing, reverting this line fixed everything (and didn't break anything).

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


[TS] authorizationStatus or authorizedStatus

According to the documentation: https://notifee.app/react-native/docs/ios/permissions after requesting permission to display notifications we check settings.authorizationStatus, but for me always returns undefined. There is however settings.ios.authorizationStatus.
Checked settings and there is a settings.authorizedStatus with the expected value.
Typescript says authorizedStatus doesn't exist on type 'NotificationSettings'

Oh no! This sounds like an issue with #237 - sounds like -

the types need to agree of course on key  name (authorizationStatus vs authorizedStatus)
settings.ios.authorizationStatus I don't think should exist anymore? As it would duplicate the parent information, but I'm less sure on that

I assume you are using the current version, this would only happen in v5 unless my mental model of what the root cause should be is busted ?

Seems like I'm using 5.0.1.
This is the output from settings:
{
   "authorizedStatus":1,
   "ios":{
      "alert":1,
      "announcement":0,
      "authorizationStatus":1,
      "badge":1,
      "carPlay":-1,
      "criticalAlert":-1,
      "inAppNotificationSettings":0,
      "lockScreen":1,
      "notificationCenter":1,
      "showPreviews":1,
      "sound":1
   }
}

I think it's pretty clear this is an issue with the PR I linked, and it will be located here in this library - I've queued it for a look later this afternoon after I get out of meetings (couple hours yet...). The information you've provided is perfect, I really appreciate it

#335 will fix this when merged+released, thanks @andrepaulo-bit

Sounds good! Thanks for taking a look!

@andrepaulo-bit Hi, thanks for reporting the issue. Fix is now in the latest release 5.0.2


Code cleanups/refactoring

Per the comment on #493, I'm opening this issue to discuss a pending cleanup that I'm working on. This is in an effort to a) improve code hygiene and b) fix bugs in the process. PR #493 above has:

Make this a proper Python package (moving files around + ~15 lines of change)
Add a test suite with a battery of tests (no-op) + tox.ini

On top of it, I have the following:

Cleanup/rewrite/refactor of almost every file (code structure)
Bunch of bugfixes
Improving human-readable output (logging etc.)
Standardizing on the syntax (PEP8, black etc.)
Comments/documentation

Via linting and code testing, hopefully this will also ensure (via all of the above) that bugs don't get introduced in the future :)
You can see the work so far in my GitHub fork.
There are a couple more modules pending -- I wanted to wrap this up this week and then open issues/PRs, but I'm opening it a bit early given the feedback on the issue above :)

To the first points, this is a single purpose application, not a general framework or library. I don't think it's appropriate to convert into a package.
I also don't see why you renamed files unless there is a specific functional issue being addressed here. Renaming without a very good reason is additional maintenance overhead.
I will not merge a rewrite of every file at this point. As I mentioned there are a number of outstanding branches and a refactor going on behind the scenes. I wish you had started a discussion before doing all of this work...
Logging is part of the ongoing refactor/redesign.
We are not PEP8 and thus not black compatible. Notably, we use tabs, % operator for formatting strings, and don't split arrays into one element per line if not necessary. #330 #415
You are welcome to maintain your own fork of course, but unfortunately it doesn't seem like it fits entirely with project philosophy/style and other things happening here. We can discuss further down the line if there are individual parts which need improvement.

To the first points, this is a single purpose application, not a general framework or library. I don't think it's appropriate to convert into a package.

This is not as much a package, as it is moving them to individual modules. The reason is so that one can do from smarthack import registration etc. Notably, this is the only way the test suite can import the code and to be able to test it - hence why I bundled it up. (This is typical for Python single purpose applications that are comprised of multiple files.)
In the future it could also allow running a single executable that runs all the different parts (e.g. in the asyncio/Tornado event loop) rather than running os.system("mqtt.py") and os.system("pkill -f smartconfig.py"). I can experiment with that and let you know where I end up.

I also don't see why you renamed files unless there is a specific functional issue being addressed here. Renaming without a very good reason is additional maintenance overhead.

The original motivation was for the same reason:
>>> from smarthack import fake-registration-server
  File "<stdin>", line 1
    from smarthack import fake-registration-server

Granted, some of them are cosmetic (mq_pub_15 would work), but given we have the opportunity while we move files around I thought I'd take it (I suppose 15 stands for some older protocol version or something). What kind of maintenance overhead are you fearing of here?

I will not merge a rewrite of every file at this point. As I mentioned there are a number of outstanding branches and a refactor going on behind the scenes. I wish you had started a discussion before doing all of this work...

Sorry about that... Happy to rebase on top of your work though. The codebase in the refactor branch is in an excellent point right now: lots of bugs fixes, homogeneous, clean, entirely lint clean, fully type-hinted, 81% code coverage etc. Setting up CI would be the natural next step.

We are not PEP8 and thus not black compatible. Notably, we use tabs, % operator for formatting strings, and don't split arrays into one element per line if not necessary. #330 #415

That's pretty idiosyncratic... PEP8 is a core Python standard -- pretty much all code bases adhere to it these days. The point is to avoid having a spaces vs. tabs discussion in every project and has been fairly successful! black takes it one step further.
As a data point, it was extremely for me hard to even understand, let alone start contributing to the codebase -- and I'm quite used to looking at third-party codebases.

You are welcome to maintain your own fork of course, but unfortunately it doesn't seem like it fits entirely with project philosophy/style and other things happening here. We can discuss further down the line if there are individual parts which need improvement.

I'd prefer to have as many of my changes merged upstream as possible. Do you think there's a way to find some common ground here?

In the future it could also allow running a single executable that runs all the different parts (e.g. in the asyncio/Tornado event loop) rather than running os.system("mqtt.py") and os.system("pkill -f smartconfig.py").

This is part of the refactor being worked on.

Granted, some of them are cosmetic (mq_pub_15 would work), but given we have the opportunity while we move files around I thought I'd take it (I suppose 15 stands for some older protocol version or something).

Seems like you have your own vision what this software should look like. Again, you are welcome to maintain your own fork. 15 is the upgrade command over Tuya's MQTT protocol.

That's pretty idiosyncratic...

Be that as it may, this is our style.

PEP8 is a core Python standard -- pretty much all code bases adhere to it these days.

That's not a good reason, just because everyone else does it doesn't make it right

The point is to avoid having a spaces vs. tabs discussion in every project and has been fairly successful! black takes it one step further.

There is no discussion. We use tabs.

As a data point, it was extremely for me hard to even understand, let alone start contributing to the codebase -- and I'm quite used to looking at third-party codebases.

Because of the tabs? :laughing: It is perfectly valid Python

I'd prefer to have as many of my changes merged upstream as possible. Do you think there's a way to find some common ground here?

I would hope so, but I ask that you do not try to take over the project with your own style and organization ideals. If you have specific functional issues you'd like to address and can keep the diff small and easy to understand that would make it quick to review and merge.

Great to hear about your upcoming refactor! Could you perhaps share more about your ideas or plans? I'm curious to hear how you're thinking of approaching this!
You've mentioned a couple of times that I am welcome to make my own fork. I'm (obviously) aware of that, but repeating it makes me feel a bit dismissed and like I'm overstaying my welcome here. I'm happy to have a discussion and figure out a way to collaborate, but if you feel there are no chances of that and I'm more of a nuisance than help, I can go away.
This is not a tabs vs. spaces issue by the way -- I have zero interest in having that conversation. This issue is about having a healthy codebase that one can change and contribute to easily and with confidence, to find and identify bugs and avoid regressions. There are a number of code health issues right now that have resulted in real bugs. Not blaming anyone -- it's natural for a codebase of this size, and to have e.g. str/bytes bugs in a codebase that has gone through a py2/py3 transition.  FWIW, pylint scores the development branch at -4.78/10. Ignoring the mixed-indentation check (which is not a "tabs" check) bumps that to 3.17/10. flake8 identifies 242 issues, without counting W191 "indentation contains tabs". Type hints revealed a number of other issues as well during the process of adding them.
IMHO, these should be addressed structurally, with modern coding practices that would ensure this continues to be the case: that includes test suites & regression checks, linters, CI etc. That's what this effort was about :)
Tooling like this is invaluable in making improvements and identifying bugs, but it doesn't play well if your code is as idiosyncratic as this codebase is. In other words, yes, "because everyone else does it" doesn't make it necessarily right, but it makes significantly easier to leverage an entire ecosystem, one that is built around what everyone else is doing!
Concretely, if you're working on a refactor yourself, the test suite can help identify any regressions. I'd be happy to take your branch and run it through the suite and pinpoint any issues found, if that's helpful. The suite itself is pretty standalone, with the only requirement being that the code is importable.

If I may offer my two cents:
I think it's awesome that you have a grand vision for this project, and it's obvious you want to help make this project be as rock solid as possible with pylint, tests, CI, community standards, etc.
However, I think all of that might be viewing this project to be bigger than it really is.
My (admittedly minimal) experience with code standards and CI tools is that they do indeed make maintaining large projects with dozens or hundreds of regular contributors much less frustrating. They probably make a ton of lives easier and have probably prevented hundreds of critical-or-worse bugs from being introduced in important software.
CI can even work for small projects where the maintainers (or just the one dev) are comfortable with configuring and operating it. However, I feel gains are not quite as high compared to what large, very active projects gain from CI.
Tuya-convert is small. Its primary use case is rather ephemeral: a user downloads it once, runs it a few times, and then it's never run again. At worst, a bug in tuya-convert just means a user can't easily flash a cheap object. An issue is submitted and a fix comes shortly after.
However, it does have a high maintenance cost separate from the software due to the nature of hardware reverse engineering. Because of this, the one (or more?) maintainer might not have the time or resources to learn how to operate CI, and the gains CI and large code standards provide might not make sense in the context of other maintenance costs. It needs to serve the maintainer, not burden.
Right now, despite it being messy, tuya-convert's code format and standards do serve the maintainer.
Still, there is room to improve. Perhaps the direction to go with this discussion is learning the maintainer's frustrations with the current code base, or small incremental changes that stick close to methods and standards the maintainer already uses but still improve the stability and quality of the code (i.e. a manually run suite of tests that doesn't require a refactor).
/2¢


Feature Request: Redo and Rotate Image

Hi, the plugin works great! Thanks.
Could you please add redo and rotate image please?
Thank you in advance.

Get the paths
<SketchCanvas
style={{flex: 1}}
strokeColor={col}
strokeWidth={7}
// touchEnabled={false}
ref={ref}
onStrokeEnd={() => {
var path = ref?.current?.getPaths();
setPaths(path);
}}
/>
and   onPress={() => {
paths.map(e => {
ref?.current?.addPath(e);
});
}}>


update to version 1.11.0

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

waiting on {MatchSpec("django-jsonstore")
https://github.com/conda-forge/staged-recipes/pull/21132

@conda-forge-admin, please restart ci

@cshaley can you please review


Path routing doesnt work properly

Description
Looks like there are multiple problems after enabling path routing. Please find the steps to reproduce using our luigi-sample-app
Steps to reproduce
Bundle luigi from master branch
lerna bootsrap
lerna run bundle

go to sample application folder and start it
npm run buildWebpack
npm run startWebpack

Go to localhost:4200
If you are already logged in, please notice that you cannot really navigate anywhere in the application.
Log out/Log in again
You will see an error.

Two problems identified:
[ ] missing proper file-copy entry in webpack configuration for logout.html file; hence the logout.html was not found. This is easy to fix.
[ ] routing doesnt work at all (besides context switcher)


bug: iOS document picker not pulling the latest code from the repository

Bug Report
Ionic version:

[x] 4.x
Current behavior:
Plugin iOS DocumentPicker is not pulling the latest code from the GitHub repo which is causing issues in compiling the code in Xcode 9.4.1 or in Xcode 10.2
Expected behavior:
While adding plugin, it should pull the latest code from the Github repo.
Steps to reproduce:

Create a new blank Ionic project
Add the plugin using commands
ionic cordova plugin add cordova-plugin-documentpicker and
npm install --save @ionic-native/document-picker@4
Add the platform iOS using command
ionic cordova platform add ios
If there is any error for '../cordova/platform_metadata' then remove the plugin
cordova plugin rm cordova-plugin-add-swift-support --force
After removing add the plugin again using command
cordova plugin add cordova-plugin-add-swift-support
Build the project using command
ionic cordova build ios
Open the project in Xcode 9.4.1 or in Xcode 10.2, It selects the default swift compile version as 4.1. Now run command to build the project. Error is generated in DocumentPicker.swift file as displayed in attachment

Other information:
If the plugin is added directly as mentioned in the GitHub repository then the issue is not there as it pulls the latest code base.
Command to add plugin directly - cordova plugin add https://github.com/iampossible/Cordova-DocPicker.git
Ionic info:
Ionic:

   ionic (Ionic CLI)             : 4.12.0 (/usr/local/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.2.0
   @angular-devkit/build-angular : 0.13.8
   @angular-devkit/schematics    : 7.2.4
   @angular/cli                  : 7.3.8
   @ionic/angular-toolkit        : 1.4.1

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : ios 4.5.5
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 3.1.2, (and 6 other plugins)

System:

   Android SDK Tools : 26.1.1 (/Users/ankit/Library/Android/sdk)
   ios-deploy        : 2.0.0
   NodeJS            : v8.11.1 (/usr/local/bin/node)
   npm               : 6.9.0
   OS                : macOS High Sierra
   Xcode             : Xcode 9.4.1 Build version 9F2000

Hi there,
I am going to close this as this is not an Ionic issue. Running cordova plugin add [plugin name] will pull the plugin from npm. It looks like the plugin author has not updated their npm listing with the latest version of the plugin:
GitHub: https://github.com/iampossible/Cordova-DocPicker
NPM: https://www.npmjs.com/package/cordova-plugin-documentpicker
If you want to pull the latest from the GitHub repo instead of npm run cordova plugin add https://github.com/iampossible/Cordova-DocPicker.git.
Thanks!


Update README.md

Hey @tino097 ,
Thank you so much for this great plugin. 👏
As promised, I am creating a PR which I am adding some images for the README file as “eye catchers” for people who are looking for nice plugins.
I hope this helps.
Kind regards,
Marija

Thanks @MarijaKnezevic !!!


feat: Added the BackToTopButton

Hi! @rupali-codes I added the back-to-top button. I saw that you added a back-to-top button to the projectmate repo. I worked based on this button and made some changes.
Fixes Issue
Should closes #127

@rupali-codes Thanks for the feedback! I`ll fix it.

@rupali-codes Hi! In my latest commit I made the following fixes.

The button has rounded-full class.
The white border is displayed in small size, because the 'Visit site' button's color is the same.
The monster is smaller, hidden by default and appers on the other side. The monster's color is similar to the 'Visit site' button's color.

thank u


[sync materialized view]not refresh after truncate base table

Steps to reproduce the behavior (Required)
CREATE TABLE `t2` (
                                            `k1` date,
                                            `k2` int,
                                            `k3` int
                                        ) ENGINE=OLAP
                                        DUPLICATE KEY(`k1`)
                                        COMMENT "OLAP"
                                        DISTRIBUTED BY HASH(`k1`) BUCKETS 3;
INSERT INTO t2 VALUES ("2020-11-10",3,3);
CREATE MATERIALIZED VIEW mv1
                             DISTRIBUTED BY HASH(k1) BUCKETS 10
                             REFRESH ASYNC
                             AS SELECT k1,k2 from t2;
TRUNCATE TABLE t2;
select * from mv1;

Expected behavior (Required)
Empty set (0.01 sec)
Real behavior (Required)
+------------+------+
| k1         | k2   |
+------------+------+
| 2020-11-10 |    3 |
+------------+------+

StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()

+----------------------------+
| current_version()          |
+----------------------------+
| BRANCH-2.4-RELEASE f823e8b |
+----------------------------+

LGTM @Astralidea


https://github.com/hungbom0409/https-bake.io-ref-0971435.git

[
Duplicate of #](url)

Uploading explore-main.zip…


bug: month name array cannot be changed after ion-datetime created

Bug Report
Ionic version:
4.11.10
Current behavior:
After component init, change of month name does not reflect in the date picker
Expected behavior:
when date picker is being opened, month name is the newest value from input
Steps to reproduce:
Change monthNames after page loaded and open date picker again to see if monthNames changed
Related code:
https://stackblitz.com/edit/ionic-v4-datetime-monthname
Other information:
This is an issue across ionic 2/3/4.
In ionic 3, my workaround is to force user to reenter the page with date picker again when language changed.
In ionic 4, from https://github.com/ionic-team/ionic/blob/master/core/src/components/datetime/datetime.tsx,
line 162: @Prop() monthNames?: string[] | string;
line 168: @Prop() monthShortNames?: string[] | string;

my wide guess is without @Prop({ mutable: true }), the new value does not reflect in the picker.
And
Cause:
this.locale.[monthNames/monthShortNames/dayNames/dayShortNames]  updated by convertToArrayOfStrings() is only loaded once in componentWillLoad()
One solution may be convertToArrayOfStrings() on the fly when open() called

if i misunderstand the mutable in stencil and the value is actually updated in ion-datetime,
just copy line 241-247 to generatePickerOptions()
p.s. small performance defect applying the change
To ionic ion-datetime development member:
this is question raised in ionic 2/3 and the logic remains,
hope to see member to add some inputs here,
maybe explaining why not apply simple fix on it

@Wingzzzzz did you figure out a way to work around this? Same issue, updating an array of monthShortNames in angular does not reflect when the ion-datetime is opened. This happens in an instance when switching languages and we need to re-render the ion-datetime months.

@antoinecfmws no, users currently accept the behavior.

@Wingzzzzz I pushed a PR to fix it, hopefully the ionic team can take a look at it and merge it. Thank you for replying.

Thanks for the issue. This has been resolved via https://github.com/ionic-team/ionic/pull/20826, and a fix will be available in an upcoming release of Ionic Framework.


New extractor ? telerama

Hello,
is it possible this one ?
http://www.telerama.fr/cinema/films/plus-tard-tu-comprendras,352042.php
Many thx

@jaimeMF Fully works as of now, Digiteka embed. This should be closed.

Many thanks to @TRox1972!


[Update Request]: DindeGDPS Launcher

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
DimisAIO.DindeGDPS
Package Version
2<IP_ADDRESS>
Please describe the changes you would like to see
I updated DindeGDPS from 2<IP_ADDRESS> (previous) to 2<IP_ADDRESS> (now)
Download link still is https://cdn-dinde.141412.xyz/DindeGDPS.exe

tyvm :D


Terraform: An argument named "docker_image_name" is not expected here.

Hey there,
I'm attempting to use the Terraform code. With or without modification to dev.tfvars I run the following:
terraform init
terraform plan -var-file='dev.tfvars'
And I get the following errors:
╷
│ Error: Unsupported argument
│
│   on main.tf line 116, in resource "azurerm_linux_web_app" "wordpress_web_app":
│  116:       docker_image_name   = "${var.wordpress_container_linux_fx_version}:8.2"
│
│ An argument named "docker_image_name" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on main.tf line 117, in resource "azurerm_linux_web_app" "wordpress_web_app":
│  117:       docker_registry_url = var.app_service_docker_registry_url
│
│ An argument named "docker_registry_url" is not expected here.
I am running Terraform 1.6.0 on Windows 11. Same occurs with Terraform 1.5.7. Same happens in Ubuntu 22.04.3 under WSL2 with:
Terraform v1.6.1
on linux_amd64

provider registry.terraform.io/azure/azapi v1.9.0
provider registry.terraform.io/hashicorp/azurerm v3.30.0
provider registry.terraform.io/hashicorp/random v3.5.1

Reverting this commit https://github.com/Azure/wordpress-linux-appservice/commit/a8c3eb872200afa564e1a30ae903da57cad4333e gets me there by the looks.
Odd though, I'm running terraform 1.6.1


Regular expression parsing error when listing versions

Provide environment information
OS:
Linux funnie 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

SHELL:
zsh 5.9 (x86_64-ubuntu-linux-gnu)

BASH VERSION:
5.2.15(1)-release

ASDF VERSION:
v0.13.1-0586b37

ASDF INTERNAL VARIABLES:
ASDF_DEFAULT_TOOL_VERSIONS_FILENAME=.tool-versions
ASDF_DATA_DIR=/home/bruno/.asdf
ASDF_DIR=/home/bruno/.asdf
ASDF_CONFIG_FILE=/home/bruno/.asdfrc

ASDF INSTALLED PLUGINS:
nodejs                       https://github.com/asdf-vm/asdf-nodejs.git master c5b7c40
php                          https://github.com/asdf-community/asdf-php.git master 1eaf4de

To Reproduce
asdf list all php
Describe the Bug
When typing this command below:
asdf list all php
I receive the error:

Plugin php's list-all callback script failed with output:
awk: line 1: regular expression compile failed (bad interval expression)
({})

This is a crystal clean Ubuntu 23.10 installation.
Expected Behaviour
List all latest PHP versions, eg:
...
8.3.0beta1
8.3.0beta2
8.3.0beta3
8.3.1RC1-clean
8.3.1
8.3.1RC1
8.3.1RC2
8.3.1RC3
...

I just found how to fix the issue. It seems that in Ubuntu 23.10 version it's using 'mawk' instead of 'gawk'. The easy and quick fix would be just installing 'gawk' with the command below:
sudo apt install -y gawk
I don't know how this impact the whole system, but you can still switch easily between awk versions with the update-altenatives command, eg:
update-alternatives --config awk


Unable to connect azure databricks in Optscale.

Describe the bug
i have hosted optscale in Ubuntu 24.04, i can connect azure account. i'm trying to connect azure databricks(https://accounts.azuredatabricks.net/) getting invalid request error. but i can connect databricks community(https://accounts.cloud.databricks.com/). both URL are diffeent.
i checked in thet file "databricks.py" located at (tools/cloud_adapter/clouds) . in that file "DATABRICKS_HOST = 'https://accounts.cloud.databricks.com' "  mentioned.
i have deployed optscale with public image (hystax/arcee:2024090501-public) from docker repo.
where i need to update the databricks host URL. if i updated i can connect azure databricks?
kindly help me to fix the issue. Thanks.

Hi @thameem2195! OptScale doesn't support Azure Databricks now, but you may try to update DATABRICKS_HOST in tools/cloud_adapter/clouds/databricks.py file and build custom images with the updated host value.
From optscale folder run the following commands:
. build.sh diworker
. build.sh rest_api

to build custom diworker:local and rest_api:local images and use kubectl delete pod to delete running diworker and restapi pods.


readme-contribute

Thanks, but I don't feel things brings added value to our README.md entrypoint.


Update README.md

remove grammatical mistakes

I am a GSSOC participant. Can I work on this issue

please check my pull request


Optimize and omit duplicate pattern matches

Continuation of #64, this time with an included test to showcase the problem and why the changes are necessary.

Optimize pattern sub-matches

With the current implementation of needle search + "truncate right" to handle sub-matches, we end up re-scanning the same regions multiple times. In some cases, this is negligible, in others, it's really bad. There's probably a better way to handle this, but to fix the most basic cases, we now cache each region (start + end address), and skip regex matching if the exact same address was processed before.
 This is used for unit tests but would also be useful for users in general, as there is otherwise no way to get the end index with variable length patterns.

Deduplicate and sort results

This is workaround for the 1st issue above.

With the changes made in https://github.com/mandiant/GoReSym/commit/54a6712945cd980dcf720c162c1347e14f078155 to address memory overhead this cache size is no longer a major concern and so I am merging

live in https://github.com/mandiant/GoReSym/releases/tag/v3.0.1


reorg docs nav (no style changes)

overview
this issue is tracking reorging the docs nav as quickly as possible ahead of larger changes.
the top-level groupins were decided on by myself, Anita, Luke, Christian, Eli, and Aaaron.

later on, Luke asked that we maintain the current support grouping at the bottom
rough draft of how pages fit into that

parts of

nav styles
design file
figma preview

thx for adding ux design details @anita-trimbur!!


No Gradient for VerticalLine and HorizontalLine

On fl_chart v0.65.0, the FlLine constructor contains an argument for a gradient, however the VerticalLine and HorizontalLine classes which extend it do not allow passing a gradient.

Added in 0.66.0


Explicit width type usage for numPoints?

The size of int can be platform specific. Is there any possibility of defining https://github.com/nianticlabs/spz/blob/main/src/cc/splat-c-types.h#L14 as a type of explicit width like int32_t or uint64_t or something?

@hobu Agreed.

@hobu happy to update this (or approve a merge request), question: should  antialiased be uint8_t instead of bool?


No Country Taxonomy for Kosovo

We have a narrative for Kosovo, but it is not included in the country taxonomy.

ain regions taxonomy (FYI Countries isn't used and is as of now officially deprecated)

Just to take into account that Kosovo has NOT an ISO3 code (yet).
The ISO 2 code XK is being used by the European Commission, Switzerland, the Deutsche Bundesbank, SWIFT, and other organizations as a temporary country code for Kosovo.


let the diff alias print decoded message

when using python 3, diff alias prints byte array instead of formatted text

Thanks for your contribution. We don't use pull requests--all code changes should go on https://reviews.reviewboard.org/
We also have a pending change to fix this at https://reviews.reviewboard.org/r/10289/


configurable shutdownTimeout for Kakfa supervisor

Allow the shutdownTimeout to be configured if tasks are taking a long time to gracefully shutdown. Also increased the default from 15 seconds to 80 seconds which is greater than the default task client retry period which should give tasks lots of time to respond to the pause/publish commands.
Fixes #3495

@pjain1 let me know if this works for you guys

hey @pjain1, if you have a chance to review this we can try to get it into the 0.9.2 RC

@dclim configurable timeout looks good to me however I was wondering if we need to kill the tasks in case of a timeout as it may happen that supervisor may not get change to resume the tasks and those tasks will never finish. What do you think ?

@pjain1 that makes sense to me, probably if they haven't responded by the timeout they're not in the best of states and we don't expose the chat handler endpoints for the task so all the user would be able to do anyway is to kill it manually; @gianm any concerns?

Killing tasks that the supervisor believes to be in a bad state is probably a good idea.
The worst that can happen is a rogue supervisor killing tasks inappropriately, although we could address that in the future with some epoch stuff. Even without that, though, I think the benefits of killing nonresponsive tasks outweigh the risks.

btw, by "some epoch stuff" I mean #3498.

@pjain1 to kill the tasks properly after the timeout (basically logic to avoid killing tasks that have already started publishing) requires a little more invasive changes than I first thought; could I post those changes in another PR so that this one can get in sooner?

@dclim IMO it's fine to do that in a different PR

btw, @dclim, your comment about avoiding killing tasks that are publishing makes me wonder: what kind of supervisor shutdown are we talking about here?
If it's a shutdown that is actually a restart, where we expect the supervisor to come back at some point, then it's probably better to not kill tasks at all. The new supervisor can do that if it wants to. If it's a shutdown that is meant to be final, I'm comfortable with killing tasks that are publishing. We want ingestion to stop, and it shouldn't really be useful to let publishing tasks finish.
So it seems to me that there may not be any cases where we want to treat publishing tasks specially. Unless I'm missing something.

@gianm hm, restarts / shutdowns currently use the same logic.
If the shutdown is a 'final' shutdown, I think there's value in letting running tasks finish and publish. That would allow someone to use shutdown as a way to do an early stop without waiting for taskDuration to elapse - i.e. they spin up a supervisor, pump 1000 messages into it, and then shutdown the supervisor to publish those segments regardless of what taskDuration was set to.
Although maybe your point is more that if some tasks are in a bad state and they don't all publish their segments (therefore triggering the shutdown timeout), then having incomplete output is the same or worse than having no output at all and it doesn't matter if we kill the publishing tasks in this case - which I agree with.

I think it's a mistake, API-wise, to conflate "shutdown" and "flush". If we want to satisfy that use case you mentioned, we could introduce a "flush" API. This has a few advantages over combining them:

callers that want to shutdown quickly without flushing data can just call "shutdown", and all inflight data will be dropped
callers that want to flush data and then shutdown supervising can call "flush" followed by "shutdown" after all the data is flushed (which I guess the caller would check with some other API).
avoids the awkward question of: if someone calls "shutdown" and that waits for tasks to publish, what happens if a task fails? Really, we should respawn it, or else this isn't a very useful flush API. But respawning tasks during shutdown mode is a bit strange and can delay shutdown by quite some time…

Similarly it's probably also a mistake to conflate "shutdown forevers" and "shutdown for the purposes of restarting soon". For the first probably the best experience is to nuke all inflight data, for the latter we definitely don't want to do that.

@gianm that API sounds good to me, I'll write it up as a separate issue

@dclim separate PR for these changes should be fine

👍


[1355] include opted in attr on user endpoint

Context
Changes proposed in this pull request
Guidance to review

 Publish whether user is "opted_in?" or not.