*.cu not supported. Example fails.

The example fails to build.
lshamis@dev [14:56:34 37 (git:main)]
~/github/rules_cuda
$ bazel build //examples:main
INFO: Build options --crosstool_top and --define have changed, discarding analysis cache.
ERROR: /home/lshamis/github/rules_cuda/examples/BUILD:3:1: in srcs attribute of cc_library rule //examples:vectorAdd: source file '//examples:vectorAdd.cu' is misplaced here (expected .cc, .cpp, .cxx, .c++, .C, .c, .h, .hh, .hpp, .ipp, .hxx, .h++, .inc, .inl, .tlh, .tli, .H, .S, .s, .asm, .a, .lib, .pic.a, .lo, .lo.lib, .pic.lo, .so, .dylib, .dll, .o, .obj or .pic.o). Since this rule was created by the macro 'cuda_library', the error might have been caused by the macro implementation in /home/lshamis/github/rules_cuda/examples/BUILD:3:1
ERROR: /home/lshamis/github/rules_cuda/examples/BUILD:3:1: in srcs attribute of cc_library rule //examples:vectorAdd: '//examples:vectorAdd.cu' does not produce any cc_library srcs files (expected .cc, .cpp, .cxx, .c++, .C, .c, .h, .hh, .hpp, .ipp, .hxx, .h++, .inc, .inl, .tlh, .tli, .H, .S, .s, .asm, .a, .lib, .pic.a, .lo, .lo.lib, .pic.lo, .so, .dylib, .dll, .o, .obj or .pic.o). Since this rule was created by the macro 'cuda_library', the error might have been caused by the macro implementation in /home/lshamis/github/rules_cuda/examples/BUILD:3:1
ERROR: Analysis of target '//examples:main' failed; build aborted: Analysis of target '//examples:vectorAdd' failed; build aborted
INFO: Elapsed time: 0.171s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 87 targets configured)

lshamis@dev [14:57:04 38 (git:main)]
~/github/rules_cuda
$ bazel build --config cuda //examples:main
INFO: Build options --crosstool_top and --define have changed, discarding analysis cache.
ERROR: /home/lshamis/github/rules_cuda/examples/BUILD:3:1: in srcs attribute of cc_library rule //examples:vectorAdd: source file '//examples:vectorAdd.cu' is misplaced here (expected .cc, .cpp, .cxx, .c++, .C, .c, .h, .hh, .hpp, .ipp, .hxx, .h++, .inc, .inl, .tlh, .tli, .H, .S, .s, .asm, .a, .lib, .pic.a, .lo, .lo.lib, .pic.lo, .so, .dylib, .dll, .o, .obj or .pic.o). Since this rule was created by the macro 'cuda_library', the error might have been caused by the macro implementation in /home/lshamis/github/rules_cuda/examples/BUILD:3:1
ERROR: /home/lshamis/github/rules_cuda/examples/BUILD:3:1: in srcs attribute of cc_library rule //examples:vectorAdd: '//examples:vectorAdd.cu' does not produce any cc_library srcs files (expected .cc, .cpp, .cxx, .c++, .C, .c, .h, .hh, .hpp, .ipp, .hxx, .h++, .inc, .inl, .tlh, .tli, .H, .S, .s, .asm, .a, .lib, .pic.a, .lo, .lo.lib, .pic.lo, .so, .dylib, .dll, .o, .obj or .pic.o). Since this rule was created by the macro 'cuda_library', the error might have been caused by the macro implementation in /home/lshamis/github/rules_cuda/examples/BUILD:3:1
ERROR: Analysis of target '//examples:main' failed; build aborted: Analysis of target '//examples:vectorAdd' failed; build aborted
INFO: Elapsed time: 0.229s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded, 92 targets configured)

lshamis@dev [14:57:36 39 (git:main)]
~/github/rules_cuda
$ bazel build --config cuda_clang //examples:main
INFO: Build option --define has changed, discarding analysis cache.
ERROR: /home/lshamis/github/rules_cuda/examples/BUILD:3:1: in srcs attribute of cc_library rule //examples:vectorAdd: source file '//examples:vectorAdd.cu' is misplaced here (expected .cc, .cpp, .cxx, .c++, .C, .c, .h, .hh, .hpp, .ipp, .hxx, .h++, .inc, .inl, .tlh, .tli, .H, .S, .s, .asm, .a, .lib, .pic.a, .lo, .lo.lib, .pic.lo, .so, .dylib, .dll, .o, .obj or .pic.o). Since this rule was created by the macro 'cuda_library', the error might have been caused by the macro implementation in /home/lshamis/github/rules_cuda/examples/BUILD:3:1
ERROR: /home/lshamis/github/rules_cuda/examples/BUILD:3:1: in srcs attribute of cc_library rule //examples:vectorAdd: '//examples:vectorAdd.cu' does not produce any cc_library srcs files (expected .cc, .cpp, .cxx, .c++, .C, .c, .h, .hh, .hpp, .ipp, .hxx, .h++, .inc, .inl, .tlh, .tli, .H, .S, .s, .asm, .a, .lib, .pic.a, .lo, .lo.lib, .pic.lo, .so, .dylib, .dll, .o, .obj or .pic.o). Since this rule was created by the macro 'cuda_library', the error might have been caused by the macro implementation in /home/lshamis/github/rules_cuda/examples/BUILD:3:1
ERROR: Analysis of target '//examples:main' failed; build aborted: Analysis of target '//examples:vectorAdd' failed; build aborted
INFO: Elapsed time: 0.187s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 91 targets configured)

Tested within docker image nvidia/cuda:10.2-cudnn8-devel-ubuntu18.04.
Git diff
diff --git a/.bazelrc b/.bazelrc
index b9e726b..ca86993 100644
--- a/.bazelrc
+++ b/.bazelrc
@@ -16,10 +16,7 @@ build --action_env CLANG_CUDA_COMPILER_PATH="/usr/bin/clang"
 build --action_env GCC_HOST_COMPILER_PATH="/usr/bin/gcc"

 build --action_env CUDA_TOOLKIT_PATH="/usr/local/cuda"
-build --action_env TF_CUDA_VERSION="11.0"
-build --action_env TF_CUDNN_VERSION="7"
 build --action_env CUDNN_INSTALL_PATH="/usr"
-build --action_env TF_CUDA_COMPUTE_CAPABILITIES="7.5"
 build --action_env COMPUTECPP_TOOLKIT_PATH="/usr/local/computecpp"
 build --action_env TMP="/tmp"

@lshamis your Bazel version seems to be outdated, only 2.2 and above supported .cu suffix. See: https://github.com/bazelbuild/bazel/commit/64a1326c7cfd66f597c290613b9ffdf8fabd4b17

@lshamis your Bazel version seems to be outdated, only 2.2 and above supported .cu suffix. See: https://github.com/bazelbuild/bazel/commit/64a1326c7cfd66f597c290613b9ffdf8fabd4b17


Handle jsonlines being mixed with other output

Cargo needs this for testing cargo test. This was found while testing the fix for #348.

Could you point out the specific tests needing this?

https://github.com/rust-lang/cargo/blob/7f2079838ac6e0a3cb05b1b9dac4401a76572855/tests/testsuite/test.rs#L4365-L4420
We could look into other ways of solving that but I hadn't yet

Could we pass --no-run?
We could read the output and do our own filtering before doing a direct call to assert_e2e().eq

--no-run seems like a viable solution for Cargo. In an ideal world everything should be JSON under --message-forma=json. I don't really think snapbox is responsible for this misfortune.

I don't really think snapbox is responsible for this misfortune.

If only the world was so clean.
For example, I was looking at cargo's compilation for other reasons and cargo emits json on stderr and we only parse lines starting as { as json, forwarding the  rest on to stderr.

rust-lang/cargo#14297 dropped the priority of this


Bubble Preset effect animated transition

Feature Request

Why it is needed

Hi @gorhom , as you requested I have opened a separate ticket.
it is based on the bubble Preset, only that you see the transition animation effect from one tab to another.

@gorhom ,  is there any news?

@gorhom ,  is there any news?

currently working on v3 that will help this and other custom presets to be added, no expected date yet

@gorhom , is there any news?

@gorhom , is there any news?


Kindle Fire FireOS permissions issue with implied autofocus

Expected Behaviour
Applications built with this plugin should be supported on modern Kindle Fire FireOS tablets.
Actual Behaviour
I'm using the BarCode Scanner plugin and porting a working Android project to Kindle Fire (FireOS). When submitting to the Amazon store, their compatibility tester fails for most recent devices because it states that my manifest file requires the android.hardware.camera.autofocus permission, but that recent devices don't support that permission. So far as I can tell, the plugin does not specifically request this permission (it only requests Camera permission), however according to Android docs, the autofocus permission is "implied" by default when the camera permission is requested. (https://developer.android.com/guide/topics/manifest/uses-feature-element.html#permissions(https://developer.android.com/guide/topics/manifest/uses-feature-element.html#permissions))
I am working around this at present by manually adding
(https://developer.android.com/guide/topics/manifest/uses-feature-element.html#permissions)
<config-file mode="merge" parent="/*" target="AndroidManifest.xml">
        <uses-feature android:name="android.hardware.camera.autofocus" android:required="false" />
    </config-file>

to my config.xml  file, but I'm wondering if the plugin itself should explicitly declare this permission not required, so that most recent Kindle Fire devices can be supported out of the box?
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Kindle Fire FireOS
Cordova CLI version and cordova platform version
cordova --version

cordova --version
7.0.1
cordova platforms

cordova platforms
Installed platforms:
android 6.2.3
ios 4.4.0
Available platforms:
blackberry10 ~3.8.0 (deprecated)
browser ~4.1.0
osx ~4.0.1
webos ~3.7.0
Plugin version
cordova plugin version | grep phonegap-plugin-barcodescanner
phonegap-plugin-barcodescanner 6.0.6 "BarcodeScanner"
Sample Code that illustrates the problem
Logs taken while reproducing problem

Closing as duplicate of https://github.com/phonegap/phonegap-plugin-barcodescanner/issues/374

@jcesarmobile thanks for catching that dupe, didn't see it.


Support Visual Studio 2019 with CMake Toolchain file

Trying to build a cmake project linking to a vcpkg installed library, VS 2019 cannot be found, and the build skips vcpkg. Looking at the vcpkg.cmake file, it looks like it doesn't check for 2019 at all. Should just adding 2019 to the list checks be enough?

For example building boost 1.70 fails to build with Visual Studio 2019.
I am using cmake 3.14.2 (build from sources)
C:\dev\vcpkg>vcpkg install boost-system
The following packages will be built and installed:
    boost-system[core]:x86-windows
Starting package 1/1: boost-system:x86-windows
Building package boost-system[core]:x86-windows...
-- Using cached C:/dev/vcpkg/downloads/boostorg-system-boost-1.69.0.tar.gz
-- Using source at C:/dev/vcpkg/buildtrees/boost-system/src/ost-1.69.0-9d1d01900c
-- Building x86-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:56 (message):
    Command failed: C:/dev/vcpkg/installed/x86-windows/tools/boost-build/b2.exe;--stagedir=C:/dev/vcpkg/buildtrees/boost-system/x86-windows-rel/stage;--build-dir=C:/dev/vcpkg/buildtrees/boost-system/x86-windows-rel;--user-config=C:/dev/vcpkg/buildtrees/boost-system/x86-windows-rel/user-config.jam;-j8;--debug-configuration;--debug-building;--debug-generators;--disable-icu;--ignore-site-config;--hash;-q;-sZLIB_INCLUDE="C:/dev/vcpkg/installed/x86-windows/include";-sBZIP2_INCLUDE="C:/dev/vcpkg/installed/x86-windows/include";threading=multi;threadapi=win32;runtime-link=shared;link=shared;address-model=32;architecture=x86;toolset=msvc-14.1;-sZLIB_BINARY=zlib;-sZLIB_LIBPATH="C:/dev/vcpkg/installed/x86-windows/lib";-sBZIP2_BINARY=bz2;-sBZIP2_LIBPATH="C:/dev/vcpkg/installed/x86-windows/lib";variant=release;debug-symbols=on
    Working Directory: C:/dev/vcpkg/buildtrees/boost-system/src/ost-1.69.0-9d1d01900c/build
    Error code: 1
    See logs for more information:
      C:\dev\vcpkg\buildtrees\boost-system\build-x86-windows-rel-out.log

Call Stack (most recent call first):
  installed/x86-windows/share/boost-build/boost-modular-build.cmake:270 (vcpkg_execute_required_process)
  ports/boost-system/portfile.cmake:14 (boost_modular_build)
  scripts/ports.cmake:71 (include)

Error: Building package boost-system:x86-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: boost-system:x86-windows
  Vcpkg version: 2018.11.23-nohash

Additionally, attach any relevant sections from the log files above.


Windows11用docker跑3.5.9wechat-assistant立刻EXIT0，npm ERR! ERESOLVE unable to resolve dependency tree

2021年11月1日8点开始，通过Windows PowerShell多次运行docker都立刻EXIT0退出，npm ERR! ERESOLVE unable to resolve dependency tree。npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
PS C:\Users\Administrator> docker run -d -e AIBOTK_KEY="xxx" -e AIBOTK_SECRET="xxx" --name=wechatBot aibotk/wechat-assistant

docker logs
Windows PowerShell
版权所有（C） Microsoft Corporation。保留所有权利。
安装最新的 PowerShell，了解新功能和改进！https://aka.ms/PSWindows
PS C:\Users\Administrator> docker run -d -e AIBOTK_KEY="b603d509ba8ba9cac6c441088f4bee7ed942f383" -e AIBOTK_SECRET="2b93799e9920bda45e986fb7b29e880ad8cd3d7c" --name=wechatBot aibotk/wechat-assistant
e0a17359738eeeee51815c62911fcef88309a611c635cf96f73fdac035ce774a
PS C:\Users\Administrator> docker ps -a
CONTAINER ID   IMAGE                     COMMAND                  CREATED         STATUS         PORTS     NAMES
e0a17359738e   aibotk/wechat-assistant   "/wechaty/bin/entryp…"   5 seconds ago   Up 2 seconds             wechatBot
PS C:\Users\Administrator> docker logs -f --tail=200 e0a17359738e

\ \      / /__  | |   __ | | _   _
\ \ /\ / / _ / _| ' \ / ` | __| | | |
\ V  V /  / (| | | | (| | || || |
_/_/ _|_|| ||_,|_|_, |
|__/

        https://www.chatie.io

/ |  _ __  _ __   ___  | |() __   __ _
| |   / _ | '_ | '_ \ / _ / | | | ' \ / _` |
| || () | | | | | | |  / (| || | | | | (| |
__/|| ||| ||_|_|_||| ||_, |
|_/

/ | |   __ | || __ )  ___ | | ___
| |   | '_ \ / ` | __|  _ \ / _ | _/ |
| || | | | (| | || |) | () | |__
_|| ||_,|_|/ ___/ _|/
WECHATY Environment Variables: 1
WECHATY_DOCKER=1
Starting Docker Container for Wechaty v0.77.3 with Node.js v16.11.1 ...

<EMAIL_ADDRESS>start
node index.js

使用环境变量中的 aibotkKey
使用环境变量中的 aibotkSecret
08:14:08 INFO PuppetManager<EMAIL_ADDRESS>please wait ...
npm: npm notice
npm:
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm: npm ERR! code ERESOLVE
npm: npm ERR! ERESOLVE unable to resolve dependency tree
npm
npm:  ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet-wechat
npm ERR!   wechaty-puppet-wechat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR!
npm:  this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /bot/.npm/eresolve-report.txt for a full report.
npm:
npm ERR!
npm:  A complete log of this run can be found in:
npm ERR!     /bot/.npm/_logs/2021-11-01T00_14_24_371Z-debug.log
Error: Command failed: npm install<EMAIL_ADDRESS>--no-save
npm notice
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet-wechat
npm ERR!   wechaty-puppet-wechat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /bot/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /bot/.npm/_logs/2021-11-01T00_14_24_371Z-debug.log
at ChildProcess.exithandler (node:child_process:397:12)
at ChildProcess.emit (node:events:390:28)
at ChildProcess.emit (node:domain:475:12)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) {

killed: false,
code: 1,
signal: null,
cmd: 'npm install<EMAIL_ADDRESS>--no-save'
}
08:14:24 ERR Wechaty start() exception: Command failed: npm install<EMAIL_ADDRESS>--no-save
npm notice
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet-wechat
npm ERR!   wechaty-puppet-wechat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /bot/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /bot/.npm/_logs/2021-11-01T00_14_24_371Z-debug.log
错误 Error: Command failed: npm install<EMAIL_ADDRESS>--no-save
npm notice
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet-wechat
npm ERR!   wechaty-puppet-wechat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /bot/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /bot/.npm/_logs/2021-11-01T00_14_24_371Z-debug.log
at ChildProcess.exithandler (node:child_process:397:12)
at ChildProcess.emit (node:events:390:28)
at ChildProcess.emit (node:domain:475:12)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) {

killed: false,
code: 1,
signal: null,
cmd: 'npm install<EMAIL_ADDRESS>--no-save'
}
08:14:24 WARN Wechaty stop() puppet.stop() exception: Cannot read properties of undefined (reading 'stop')
接口https://api-bot.aibotk.com/open/v1/api/wechat/qrerror请求失败 undefined
推送错误成功 Commandfailed:npminstallwechaty-puppet-wechat@>=0.28--no-savenpmnoticenpmnoticeNewminorversionofnpmavailable!8.0.0->8.1.2npmnoticeChangelog:https://github.com/npm/cli/releases/tag/v8.1.2npmnoticeRunnpminstall-gnpm@8.1.2toupdate!npmnoticenpmERR!codeERESOLVEnpmERR!ERESOLVEunabletoresolvedependencytreenpmERR!npmERR!Whileresolving:wechaty@0.68.1npmERR!Found:wechaty-puppet@0.41.9npmERR!node_modules/wechaty-puppetnpmERR!wechaty-puppet@"^0.41.1"fromtherootprojectnpmERR!npmERR!Couldnotresolvedependency:npmERR!peerwechaty-puppet@"^1.0.1"fromwechaty-puppet-wechat@1.0.1npmERR!node_modules/wechaty-puppet-wechatnpmERR!wechaty-puppet-wechat@"*"fromtherootprojectnpmERR!npmERR!Fixtheupstreamdependencyconflict,orretrynpmERR!thiscommandwith--force,or--legacy-peer-depsnpmERR!toacceptanincorrect(andpotentiallybroken)dependencyresolution.npmERR!npmERR!See/bot/.npm/eresolve-report.txtforafullreport.npmERR!Acompletelogofthisruncanbefoundin:npmERR!/bot/.npm/_logs/2021-11-01T00_14_24_371Z-debug.log
npm notice
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice

\ \      / /__  | |   __ | | _   _
\ \ /\ / / _ / _| ' \ / ` | __| | | |
\ V  V /  / (| | | | (| | || || |
_/_/ _|_|| ||_,|_|_, |
|__/

        https://www.chatie.io

| | () |   / _
|  | \ / / | | | | | |
| | >  <| | |  | || |
|___//__|_|  _/
PS C:\Users\Administrator>

12:50在ArchLinux运行docker的wechat-assistant与Windows11的Docker Desktop报错信息相同：
npm: npm ERR! code ERESOLVE

npm: npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!

npm: npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm
npm:  ERR! node_modules/wechaty-puppet-wechat
npm ERR!   wechaty-puppet-wechat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /bot/.npm/eresolve-report.txt for a full report.

docker logs
[ht@arch ~]$ sudo docker run -d -e AIBOTK_KEY="b603d509ba8ba9cac6c441088f4bee7ed942f383" -e AIBOTK_SECRET="2b93799e9920bda45e986fb7b29e880ad8cd3d7c" --name=wechatBot aibotk/wechat-assistant
[sudo] ht 的密码：
对不起，请重试。
[sudo] ht 的密码：
97bc81a75c0be266b02a38380b9598a86cf450be371b7fced83dd693d8b1f8bc
[ht@arch ~]$ sudo docker ps
CONTAINER ID   IMAGE                     COMMAND                  CREATED         STATUS         PORTS     NAMES
97bc81a75c0b   aibotk/wechat-assistant   "/wechaty/bin/entryp…"   4 seconds ago   Up 3 seconds             wechatBot
[ht@arch ~]$ sudo docker logs -f --tail=200 97bc81a75c0b

\ \      / /__  | |   __ | | _   _
\ \ /\ / / _ / _| ' \ / ` | __| | | |
\ V  V /  / (| | | | (| | || || |
_/_/ _|_|| ||_,|_|_, |
|__/

        https://www.chatie.io

/ |  _ __  _ __   ___  | |() __   __ _
| |   / _ | '_ | '_ \ / _ / | | | ' \ / _` |
| || () | | | | | | |  / (| || | | | | (| |
__/|| ||| ||_|_|_||| ||_, |
|_/

/ | |   __ | || __ )  ___ | | ___
| |   | '_ \ / ` | __|  _ \ / _ | _/ |
| || | | | (| | || |) | () | |__
_|| ||_,|_|/ ___/ _|/
WECHATY Environment Variables: 1
WECHATY_DOCKER=1
Starting Docker Container for Wechaty v0.77.3 with Node.js v16.11.1 ...

<EMAIL_ADDRESS>start
node index.js

使用环境变量中的 aibotkKey
使用环境变量中的 aibotkSecret
12:50:07 INFO PuppetManager<EMAIL_ADDRESS>please wait ...
npm: npm notice
npm:
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm: npm ERR! code ERESOLVE
npm: npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm: npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm
npm:  ERR! node_modules/wechaty-puppet-wechat
npm ERR!   wechaty-puppet-wechat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /bot/.npm/eresolve-report.txt for a full report.
npm:
npm ERR!
npm:  A complete log of this run can be found in:
npm ERR!     /bot/.npm/_logs/2021-11-01T04_50_53_110Z-debug.log
Error: Command failed: npm install<EMAIL_ADDRESS>--no-save
npm notice
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet-wechat
npm ERR!   wechaty-puppet-wechat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /bot/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /bot/.npm/_logs/2021-11-01T04_50_53_110Z-debug.log
at ChildProcess.exithandler (node:child_process:397:12)
at ChildProcess.emit (node:events:390:28)
at ChildProcess.emit (node:domain:475:12)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) {

killed: false,
code: 1,
signal: null,
cmd: 'npm install<EMAIL_ADDRESS>--no-save'
}
12:50:53 ERR Wechaty start() exception: Command failed: npm install<EMAIL_ADDRESS>--no-save
npm notice
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet-wechat
npm ERR!   wechaty-puppet-wechat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /bot/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /bot/.npm/_logs/2021-11-01T04_50_53_110Z-debug.log
错误 Error: Command failed: npm install<EMAIL_ADDRESS>--no-save
npm notice
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/wechaty-puppet-wechat
npm ERR!   wechaty-puppet-wechat@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /bot/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /bot/.npm/_logs/2021-11-01T04_50_53_110Z-debug.log
at ChildProcess.exithandler (node:child_process:397:12)
at ChildProcess.emit (node:events:390:28)
at ChildProcess.emit (node:domain:475:12)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) {

killed: false,
code: 1,
signal: null,
cmd: 'npm install<EMAIL_ADDRESS>--no-save'
}
12:50:53 WARN Wechaty stop() puppet.stop() exception: Cannot read properties of undefined (reading 'stop')
接口https://api-bot.aibotk.com/open/v1/api/wechat/qrerror请求失败 undefined
推送错误成功 Commandfailed:npminstallwechaty-puppet-wechat@>=0.28--no-savenpmnoticenpmnoticeNewminorversionofnpmavailable!8.0.0->8.1.2npmnoticeChangelog:https://github.com/npm/cli/releases/tag/v8.1.2npmnoticeRunnpminstall-gnpm@8.1.2toupdate!npmnoticenpmERR!codeERESOLVEnpmERR!ERESOLVEunabletoresolvedependencytreenpmERR!npmERR!Whileresolving:wechaty@0.68.1npmERR!Found:wechaty-puppet@0.41.9npmERR!node_modules/wechaty-puppetnpmERR!wechaty-puppet@"^0.41.1"fromtherootprojectnpmERR!npmERR!Couldnotresolvedependency:npmERR!peerwechaty-puppet@"^1.0.1"fromwechaty-puppet-wechat@1.0.1npmERR!node_modules/wechaty-puppet-wechatnpmERR!wechaty-puppet-wechat@"*"fromtherootprojectnpmERR!npmERR!Fixtheupstreamdependencyconflict,orretrynpmERR!thiscommandwith--force,or--legacy-peer-depsnpmERR!toacceptanincorrect(andpotentiallybroken)dependencyresolution.npmERR!npmERR!See/bot/.npm/eresolve-report.txtforafullreport.npmERR!Acompletelogofthisruncanbefoundin:npmERR!/bot/.npm/_logs/2021-11-01T04_50_53_110Z-debug.log
npm notice
npm notice New minor version of npm available! 8.0.0 -> 8.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice

\ \      / /__  | |   __ | | _   _
\ \ /\ / / _ / _| ' \ / ` | __| | | |
\ V  V /  / (| | | | (| | || || |
_/_/ _|_|| ||_,|_|_, |
|__/

        https://www.chatie.io

| | () |   / _ \
|  | \ / / | | | | | |
| | >  <| | |  | || |
|___//__|_|  _/
[ht@arch ~]$

拉一下最新的docker 版本3.6.2已经解决问题

@leochen-g 牛，比上个版本快了百倍。


Get rid of goog.dom.getNextElementSibling

closure-library code:
https://github.com/google/closure-library/blob/v20160822/closure/goog/dom/dom.js#L1252-L1262

That seems to be handled by all modern browsers. See https://developer.mozilla.org/en-US/docs/Web/API/NonDocumentTypeChildNode/nextElementSibling.
Thanks and please merge.


Changelog fixes for 1.6.0-rc.1

bcd0d4d896d0dfdd988ff4f849c1d40366125858

"If you don't have time to migrate the code at the moment, you can flip the
setting back to true"
$compileProvider.preAssignBindingsEnabled(true);

7bc71a
"Now, all traditionally false JavaScript values are treated as failing the validator, as one would naturally expect."

There is only one false value, the expression "traditionally false" doesn't make sense. It should say "falsy" or "falsey" (not sure what's the best spelling).

fc0c11db845d53061430b7f05e773dcb3fb5b860

It says "fc0c11): camelCase keys in jqLite#data"; the weird paren needs to be removed

acb545ec3ebf099db68561033645941c900973b5

In the "After" code snippet the ampersand is incorrectly encoded:
// URL: /foo/42?bar=baz&toString=hmm

Am I missing something, or can we introduce these changes right away? The title makes it sound like we have to wait for 1.6.0-rc.1

I think you're right that we can do it at this very moment. I think the title just meant that it's sth we plan to do before releasing rc.1 but that doesn't seem to be a blocker.

For commits that have not been released yet we can't yet update the changelog for them. This issue is supposed to track those things


OSX Memory Leak

Just noticed that Electron is up to 4.4 GB memory usage on my Mac while YakYak is running.  Feels like a memory leak to me.
El Capitan, YakYak Version 0.37.4

Could be an electron bug. In version 1.2.2 (currently a pre-release) i have updated electron version significantly. Can you check again please ?

The leak is still present

@ckald @gamut is the leak still present?
in ubuntu it remains stable at 65-74MB (depending on the process).. granted that seems too much, but electron has a big overhead

Honestly, I’m not sure.  It’s at 175 MB at the moment, and i routinely have to restart the app — maybe once per day, because it stops sending messages.  I haven’t bothered to check memory when that happens.   I will do so the next time.

On Dec 22, 2016, at 19:48, André Veríssimo<EMAIL_ADDRESS>wrote:
@ckald https://github.com/ckald @gamut https://github.com/gamut is the leak still present?
in ubuntu it remains stable at 65-74MB (depending on the process).. granted that seems too much, but electron has a big overhead
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/yakyak/yakyak/issues/182#issuecomment-268922331, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEGD99ZilfrYgoXY_v0JZMbzgxFt8v9ks5rKxpRgaJpZM4IvB9n.


[Feature request]: Scaling Playwright "out" to multiple services/hosts

Your question
How can I run my tests on remote vm or several vm, like we did it with selenium grid? I am using .NET version of playwright.
Now I have selenium grid with 15 windows10 agents (CI - TeamCity). I would like to use it for playwright tests too.

At the moment, this isn't something we provide.

In 1.15 BrowserType.Connect gets added, then you can build your own grid (launchServer via Node.js and Connect() via .NET). See also https://github.com/microsoft/playwright-dotnet/issues/1291 for BrowserType.ConnectOverCDP support.


Easymotion incorrect jump to search

When using https://github.com/asvetliakov/vim-easymotion, and doing <leader>/ for search, when I type the search then choose the target, it jumps to the first non-whitespace col in the line below the target instead of directly to the target.

The problem here is the automatically accepting return prompt caused by easymotion. But for easymotion search it's "autoaccepted" already

Hi,
is it possible, that this bug is still persisting? I have the exact same problem that is showcased above.

I'm having the same issue as well.


fix: Full fix QuickGene

Reviewers
Functional:
Readability:

Changes

Add return statement 🤦 That's the only diff between the Seamless Experience commit and this one!
Add return type to this function, so no one will forget the return statement ever again
This is totally my bad, I refactored this code to follow React best practices, but totally forgot about the return statement when converting from an implicitly returned function 😭 SO SORRY! 🙏 🙏 🙏

Only merge this after prod deploy is done ✅

Actually changed this to merge into hotfix/oct-14th, so it will go out with other hot fixes tomorrow 👌 Thank you!


merge parent properties with child properties instead of the other way round

The method 'readClassProperties' has been written in such a way if the annotations are defined in a parent class and not in the child class, the annotations in the parent class is taken into consideration with those in the child class.
The problem is that if I have the same property in a parent and child class and only the one in the child class has the annotation, the property will not be index.
For example, am using FOSUserBundle and I need to index username and username is defined in FOSUserBundle, one way to make SolrBundle index username is to place username in my child class and add the appropriate annotations to it.  The problem is that the annotation on the overridden property is not take into consideration.
Regards,

Indeed, I confirm the problem with FOSUserBundle.

@chellem thanks for your patch!


Reset reasoner

@maxeeem could you review the changes? I guess some tests are needed.

The reset() method of class Reasoner  is implemented. The command ''reset can be used to reset the reasoner in Console.

I'll take a look. Old code in rule_map_two_premises called reset() which is probably causing some issues.

@bowen-xu I updated the tests to use reset() and as an added bonus, all tests now run 5x faster! because we no longer have to construct the whole Reasoner object on each run! Great Work!
147 test now passing compared to 140 before :)


why the initial value of alpha_init  is 1/layer_num

https://github.com/lucidrains/nGPT-pytorch/blob/5e76aac45044e065afd792006a0751b0f470f852/nGPT_pytorch/nTransformer.py#L324
hi, I want to know why the initial value of alpha_init  is 1/layer_num， Thanks for your reply

i'm following point 3 in section 2.6

i'm following point 3 in section 2.6

thank you very much，and I will close this issue


Request: Filter by FUTBIN BIN for when searching the transfer market

Hi, I've only just started using your script and it's great, really nice work.
I was just wondering if you are able to add the ability to search the transfer market by filtering the FUTBIN BIN? Much like you can set min/max Bid or Buy Now price through the web app.
Thanks a lot!

Thanks for the kind words.
Currently the scripts look up the Futbin price for a specific player. Unfortunately Futbin does not provide any API that we could use to implement this request, as far as I am aware of.
However, I'm open for suggestions on how this could be accomplished.

Since Futbin doesn't provide any API for this, it can't be accomplished.


documentation url?

The documentation is well-written. Does it happen to be hosted at a different url, for ease of navigation?
mkdocs.yml contains the line ""https://noudart.github.io/PyBWE" but the url appears to be defunct.

The documentation is well-written. Does it happen to be hosted at a different url, for ease of navigation? mkdocs.yml contains the line ""https://noudart.github.io/PyBWE" but the url appears to be defunct.

@kathlandgren This was a typo, the actual URL is "https://nicoudart.github.io/PyBWE". I updated the mkdocs.yml file. Thank you for finding this mistake!

Awesome! Perhaps it would be helpful to add this link under Documentation in README.md? I struggled to find the url, and it's nicer to interact with a website rather than click through docs/

@kathlandgren I agree, the website will be easier to find that way. The link is now given at the beginning of the README.md.


[bug] Unable to marshal native value to JS

Using react-native-auth0 2.17.0 as example case, appears NSError is not properly handled.
Might be better to use @nativescript/core 8.4+ Utils.dataDeserialize(data) instead of custom handling there. The throw is likely unnecessary on this line - rather can just return the data object "as-is" which is what core Utils does in this case.
  NativeScript encountered a fatal error: Uncaught Error: Unable to marshal native value to JS: NSError:Error Domain=com.apple.AuthenticationServices.WebAuthenticationSession Code=2 "Cannot start ASWebAuthenticationSession without providing presentation context. Set presentationContextProvider before calling -start." UserInfo={NSDebugDescription=Cannot start ASWebAuthenticationSession without providing presentation context. Set presentationContextProvider before calling -start.}
  at
  toJSValue(file: src/webpack:/node_modules/@open-native/core/src/ios/converter.js:325:10)
  at toJSValue(file: src/webpack:/node_modules/@open-native/core/src/ios/converter.js:305:23)

Good catch! I will take a look and handle this properly. Seems like we are missing this.

Fixed in 1.0.0-alpha.23.


TOOLS_WORKSPACE_INSTALL_DIR should be configurable

Currently its hard coded to ".embuild".  It would be nice if it were configurable via an environment variable.
Maybe my use case is not common.  I have the project on a shared filesystem on multiple systems.   Manually managing the the IDF and tools installs across many systems will be problematic when it's time to upgrade IDF versions or tools.

I may not be understanding your issue, but the (workspace) install dir is already configurable. If you set ESP_IDF_TOOLS_INSTALL_DIR to custom:<path> you can configure the name and location of the install dir (if its a relative path, it's relative to the workspace dir).
I.e. just setting it to custom:.my_special_folder would install the tools in <workspace-dir>/.my_special_folder (instead of <workspace-dir>/.embuild/<builder-name>).

This is perfect! Thank you!


🪲 Bug Report - InvalidAuthenticationToken Error when running mgDiagSettingsAll.bicep

Describe the bug
I'm setting up a new ALZ based on the bicep development flow using Powershell. I've set the parPlatformMgAlzDefaultsEnable = false for my scenario. All was working well until step 4.1 Management Groups Diagnostic Settings when I encountered the following 3 errors:
Status Message:  (Code:InvalidAuthenticationToken)
To Reproduce
Steps to reproduce the behaviour:
I run this:
New-AzManagementGroupDeployment   -TemplateFile infra-as-code/bicep/orchestration/mgDiagSettingsAll/mgDiagSettingsAll.bicep
-TemplateParameterFile infra-as-code/bicep/orchestration/mgDiagSettingsAll/parameters/mgDiagSettingsAll.parameters.all.json   -Location australiaeast
-ManagementGroupId alz
Expected behaviour
Complete with no errors.
Correlation ID
938b8666-a410-428b-ba99-d3598090d3ca
Additional context
Obviously I have modified the mgDiagSettingsAll.parameters.all.json file. And I believe I have this param correct
"parLogAnalyticsWorkspaceResourceId": {
"value": "/subscriptions//resourceGroups/rg-alz-logging-001/providers/Microsoft.OperationalInsights/workspaces/alz-log-analytics"
},
Where  is the subscription id of my platform management groups LAW. I found this in the JSON view of the LAW.
Any help appreciated.

Looks like youve got a double // after subscriptions @teamlittman

Also @teamlittman we had this in issue #470 and it turned out to be the RP wasn't registered on the management subscription.
Are you able to confirm that the subscription that hosts the Log Analytics Workspace has the Microsoft.Insights resource provider registered? You can run Get-AzResourceProvider -ProviderNamespace 'Microsoft.Insights' | FT to check.
If it isn't, can you run Register-AzResourceProvider -ProviderNamespace 'Microsoft.Insights' and wait for it to succeed and finish and then re-run the mgDiagSettingsAll.bicep deployment and let me know the results?

Thanks Jack. Yes I had obfuscated the LAW id incorrectly when I pasted it in.. it is like this:
"parLogAnalyticsWorkspaceResourceId": {
"value": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/rg-alz-logging-001/providers/Microsoft.OperationalInsights/workspaces/alz-log-analytics"
},
I also checked the RP registration and it was 'NotRegistered'.. so I registered as suggested and waited for the status to change to 'Registered', however the issues remains:
CorrelationId: 9fc20394-d71b-4768-948c-056d037307a9
(Really appreciated the prompt turn around btw!)

Please try it again after giving the RP time to register
Sent from my iPhone
On 29 May 2023, at 09:07, Steve Littman @.***> wrote:

Thanks Jack. Yes I had obfuscated the LAW id incorrectly when I pasted it in.. it is like this:
"parLogAnalyticsWorkspaceResourceId": {
"value": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/rg-alz-logging-001/providers/Microsoft.OperationalInsights/workspaces/alz-log-analytics"
},
I also checked the RP registration and it was 'NotRegistered'.. so I registered as suggested and waited for the status to change to 'Registered', however the issues remains:
CorrelationId: 9fc20394-d71b-4768-948c-056d037307a9
(Really appreciated the prompt turn around btw!)
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/ALZ-Bicep/issues/544#issuecomment-1566730928, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJ2BVP7RKGXIAG3CA7ZMZR3XIRKNHANCNFSM6AAAAAAYSOMMWA.
You are receiving this because you commented.Message ID: @.***>

Thank Jack.. I figured out that I had registered the MS Insights in the wrong subscription.. not my platform subscription, so I changed to the correct one using:
Set-AzContext -Subscription 'xxxx'
and then registered using:
Register-AzResourceProvider -ProviderNamespace 'Microsoft.Insights'
and then waited a few hours, and its working now.
So I'm officially proving my newb status in Azure :(
Thanks again for all your help.


MIss

Version
4.0.0-alpha.5
Test Case
https://react-router.now.sh/Miss
Steps to reproduce
Navigate to the missed route.
Expected Behavior
location is passed to the Miss component
Actual Behavior
No params/location available
An error is thrown attempting to access location.pathname since location is undefined.
index.js:259 Uncaught TypeError: Cannot read property 'pathname' of undefined(…)
Here's the JS I was using
import React from 'react'
import { render } from 'react-dom'
import Match from 'react-router/Match'
import Miss from 'react-router/Miss'
import Link from 'react-router/Link'
import Router from 'react-router/BrowserRouter'

const App = () => (
  <Router>

<Link to="/missed">Home</Link>

      <Match pattern="/foo"/>
      <Match pattern="/bar"/>
      <Miss render={({ location }) => (

Nothing matched {location.pathname}.

      )}/>

  </Router>
)

render(<App/>, document.querySelector('#root'))

{
  "name": "react-router-v4",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "react-scripts": "0.7.0"
  },
  "dependencies": {
    "react": "^15.3.2",
    "react-dom": "^15.3.2",
    "react-router": "^4.0.0-alpha.5"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test --env=jsdom",
    "eject": "react-scripts eject"
  }
}

I used create-react-app to get started but I've only been running through the examples and Miss was the only issue I bumped up against. I realize this is alpha code, but I expect this has been working since it's documented and the embedded example works in the docs.

Should work after 3423b1d, just hasn't been published yet.

I had the same issue. Spent a lot of time on this, thinking I had done something wrong. Upgraded to alpha.6 and this is working.


added stored value data retrieval

make sure this is merged after the changes to the library are completed
https://github.com/osisoft/sample-ocs-sample_libraries-python/pull/23

/azp run


 was  here

added some emojis to the previous code

Hi @swaraj961, I appreciate the contribution but I think I'd prefer to keep the README headings plain for now.


Add a way to disable console logging

I'd like a way how to disable debug and warning output from the console log:
2016-05-19 15:46:23.038 8fit Debug[26445:3229567] [Branch Warning] You are using your test app's Branch Key. Remember to change it to live Branch Key for deployment.
2016-05-19 15:46:23.039 8fit Debug[26445:3229567] [Branch Warning] Cannot use cookie-based matching while setDebug is enabled
2016-05-19 15:46:23.043 8fit Debug[26445:3229567] [BNCServerInterface.m:196] using url = https://api.branch.io/v1/open

Since there's no way how to do that directly on the Branch class, I wanted to set debug and suppressWarningLogs on the BNCPreferenceHelper singleton. However I'm using it in a swift project and because of the unique way how Swift interoperates with ObjC, I can't call the preferenceHelper class method to get the singleton instance.
Can you please add a way how to disable this console output?

@milancermak both methods should be called from your Branch instance.
suppressWarningLogs (https://github.com/BranchMetrics/iOS-Deferred-Deep-Linking-SDK/blob/master/Branch-SDK/Branch-SDK/Branch.h#L422) and setDebug (https://github.com/BranchMetrics/iOS-Deferred-Deep-Linking-SDK/blob/master/Branch-SDK/Branch-SDK/Branch.h#L370)
setDebug is not called by default as well so you you could just remove it from your code and you won't see the debugging logs. You shouldn't need to call BNCPreferenceHelper since it is intended for internal use.

That cleared it up for me. Cheers!


Bounty - Forced setup mode

Forced setup mode is intended for operators and individuals who may be putting these boards into dedicated setups and do not want the ability to change options once installed.
This bounty would be either an add-on or an addition to the settings page.
It will allow you to:

Lock a mode (holding P1, P2, K1, K2 on boot no longer changes modes from the set mode)
Remove any or all hotkey combos (this is already in, not sure if we want to wrap it all together)

It might be worth a quick discussion at some point if the "Function" key (#239) ought to solve this problem by essentially claiming mode selection, web configurator at boot, etc. are hotkeys, and then the setup mode requested here would be enabled by defining the pin for Fn (which is unset by default, but could be set to a pin only populated via a jumper or on a button/switch not accessible by users). Function (currently a core button) could change --- it's in a WIP waiting for at least protobuf to merge, right now, anyway --- so we have time to redesign it before it goes in.
And to be fair, it's equally possible that "Function" serves as a runtime alternate function key (modifiers e.g. tilts, as BRP said on Discord), but what I was envisioning was more of a "disabling hot keys" thing than a "changing behavior" thing (though both are valuable). If we want "Function" to be runtime then I may un/redo #239 and take this on separately.
Or maybe "forced setup mode" is different than "disabling hot keys" in which case we have three buttons?? I don't know. Anyone with opinions, ping me. =)

This work has been completed.


Rules reformat

Updated Rules compendium to use V10 Journals.
Moved Skills from Skills compendium to Rules
Updated links to Rules and Skills through system.

Cleaned up


Fullrecord timeline -- rectangles processing

@jread-usgs how does this look?
Next, I use the NMRectangles.rds in a visualize script.
@ldecicco-USGS here's what I've got for rectangles. I think the naming is the same as you've been using

:+1:

self-merging since jread gave it the thumbs up and make build is working

associated w/ #25


BigValue Component

Adds a beloved BI feature: the Big Number Viz™ to Evidence.
Includes:

Number
Sparkline
Comparison
Comparison is configurable for "down is good"
Multiple Big Numbers stack into a row
Smart enough defaults that only the data prop is required

Love this feature!
Defaults

Not sure the default behaviour is working perfectly here. Or maybe it is but the results are a bit puzzling:

Eg1
```orders
select * from orders limit 10
```

<BigValue data={orders}/>

Eg2

Eg3

Visual Nits (for considerations)

It looks a bit like the sparkline is cropped at the bottom (but actually I think it is to do with the svg "brushstroke", rather than margins etc?)

For a BigValue, the Value could be a bit Bigger, perhaps closer to H1 than H2 size - cant remember exactly how em vs rem work but 1.5em looks like this:

Not sure this is an issue but the error message bleeds out rather than truncates. Also other components label what they are in this error message (eg LineChart)

File structure

Any reason this is not in the Viz folder with other chart / value components?

Thanks @archiewood, excellent feedback as always. Just consolidating here:

[ ] Drop the default system
[ ] Tidy up error messages
[ ] Move the component to viz, and add it to the preprocessor default imports
[ ] Take one more look at sizing and consider nudging up

@archiewood updates in the branch, except for the size changes. Take a look, and feel free to merge if you're comfortable.
Once you get the actual value close to H1, two things happen:

They compete with the H1 Headers, so it's harder to understand where they necessarily fit.
Just a lot less space for these.

I'd propose shipping at the current size and seeing how that feels in practice.
Current Size:

H1 Sized:

Will have a play around with the new lack of defaults
Re sizing: happy to ship as is:

I was probably thinking of making just the number sized H1, not the title of the . Agree above definitely competing with actual H1s

Ah got it
Yeah looks pretty good IMO

I noticed that if you are in a wide enough viewport to see it, the TableofContents shows "Big Value" every time there is one, as the logic in this displays all the H1 elements.
Solved this by using the <ErrorChart/> component for Big Value's error message, which styles the Error differently.

Thank you @archiewood 🚢


Docker registry(v2) uses too much disk space

Hi I have offline private registry. I set it up with default docker run -d -p 5000:5000 --name registry registry:2 command.
Although our images' size is 28.45 GB, docker registry uses 215 GB of disk space.  I am not sure whether it is normal behaviour or not.
I tried to run garbage collector manually with /bin/registry garbage-collector /etc/docker/registry/config.yml command and it returns 25634 blobs marked, 0 blobs eligible for deletion.
Would you please help me?

Where did you see image size as 28GB?

Closing as wildly outdated with no further updates from the reporter.


[Native File Dialog] Add support for using native dialogs in the editor.

Add support for using native dialogs in the editor, in case https://github.com/godotengine/godot/pull/79313 used by https://github.com/godotengine/godot/pull/79316 UI, export options are shown as a separate dialog before showing native file dialog.

Adds support for using native dialogs to the EditorFileDialog.
Adds support for custom options to the EditorFileDialog (same as in the normal FileDialog) and use it instead of custom checkboxes in the various editor places.
Adds interface/editor/use_native_file_dialogs editor setting to enable native dialogs (also automatically enabled if editor is sandboxed).

Thanks!


Provide proper types

Description
Components are not properly typed:

form property on <UInput> works, but is not typed
id property on <UForm> works, but is not typed
submit method on Form<...> works, but is not typed
autocomplete property on <UInput> works, but is not typed
I guess there are many more.

Cf: #668 #634
Additional context
No response

Found this issue looking at https://ui.nuxt.com/forms/form#backend-validation
I would love to be able to d something like
const form = ref<UForm|undefined>(undefined)

import type { Form } from '@nuxt/ui/dist/runtime/types/form'

const form = ref<Form<any>|undefined>(undefined)

```ts

@some-user123

My point is that the type exists, but is not correct.
(form.value as any).submit() works. form.value.submit() causes a type error.
<UForm id="..."> works. But causes a type error if you enable vueCompilerOptions.strictTemplates.
The types don't match the actual implementation.

I stumbled upon this thread while searching how to import types and getting errors with the explicit import mentioned above:
error TS2307: Cannot find module '@nuxt/ui/dist/runtime/types' or its corresponding type declarations.

I wanted to mention that the (new?) way is:
import type { Form } from '#ui/types'

@romhml Do you think all of these are fixed in v3? 🤔

I'm not @romhml but I can comment, that so far I didn't find a similar issue in v3 🥳
However, it could be I've missed such an error as there are many other type errors (#2532) and in app.config.ts.

Found another one:
<UInput type="submit" form="ref" />

works, but fails type check:

Object literal may only specify known properties, and 'form' does not exist in type 'Partial<{}> & Omit<{ readonly disabled?: boolean | undefined; readonly icon?: string | undefined; readonly variant?: "link" | "solid" | "outline" | "soft" | "subtle" | "ghost" | undefined; ... 36 more ...; readonly loadingIcon?: string | undefined; } & VNodeProps & AllowedComponentProps & ComponentCustomProps, never>'.

I could not reproduce any type issues mentioned except for the Form component using the v3  branch and useTemplateRef . I submitted a fix for the form component which types the  $el  attribute in order to access the form  element attributes without typing errors.

@some-user123 Could you summarize what exactly doesn't work? I couldn't reproduce the last two examples you sent.
I'd like to close this if everything's fine 😊

I think, this should be a minimal reproduction: https://github.com/some-user123/nuxt-ui-issue731.
If you run npx nuxi typecheck on it:
app.vue:2:12 - error TS2353: Object literal may only specify known properties, and 'onInput' does not exist in type 'NonNullable<{ readonly modelValue?: string | number | undefined; readonly id?: string | undefined; readonly name?: string | undefined; readonly type?: InputTypeHTMLAttribute | undefined; ... 22 more ...; readonly onBlur?: ((event: FocusEvent) => any) | undefined; } & VNodeProps & AllowedComponentProps & ComponentCus...'.

2   <UInput @input="() => console.log('hi')"></UInput>
             ~~~~~

app.vue:3:26 - error TS2353: Object literal may only specify known properties, and 'form' does not exist in type '{ readonly label?: string | undefined; readonly color?: "error" | "primary" | "secondary" | "success" | "info" | "warning" | "neutral" | undefined; readonly variant?: "link" | "solid" | ... 4 more ... | undefined; ... 36 more ...; readonly inactiveClass?: string | undefined; } & VNodeProps & AllowedComponentProps & ...'.

3   <UButton type="submit" form="ref">Hello</UButton>
                           ~~~~

If you disable strictTemplates in tsconfig.json (which I would consider bad practice), you can avoid these type errors , but you also don't get any hints that these properties are available:

Nor do you get errors if you use these properties wrongly, e.g.
  <UInput @input="123">Hello</UInput>
  <UButton type="submit" :form="() => console.log('foo')" />

Does this help?

So this is related to strictTemplates (nuxt/ui#2562) and we can close this?

No, these are separate issues. #2562 is that already the pure installation of @nuxt/ui (without using any component of it) causes type errors when strictTemplates is enabled.
This issue is that @nuxt/ui components are not properly typed. More specifically some properties are missing, e.g. form of UButton and @input of UInput.
This problem manifests itself in different ways:

type errors if these properties are used and strictTemplates is enabled
there are no hints in the IDE
if properties are used with the wrong type and strictTemplates is disabled there are no warnings/errors

There are thousands of possible props on the <input> element. There is no way we can type them all: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attributes
It's the same about events, what do you need the @input for in the first place? Why not use v-model or @update:model-value or even @change? 🤔
https://ui3.nuxt.dev/components/input#emits

There are thousands of possible props on the <input> element. There is no way we can type them all: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attributes

<input> elements are properly typed as HTMLInputElement. I don't think you need to re-invent the wheel. If UInput accepts the same parameters, you can inherit those. Types are available in vue, e.g. InputHTMLAttributes (https://github.com/vuejs/core/blob/76c43c6040518c93b41f60a28b224f967c007fdf/packages/runtime-dom/src/jsx.ts#L518). I don't think you should hardcode all of them...

what do you need the @input for in the first place? Why not use v-model or @update:model-value or even @change? 🤔

Both @change and @update:model-value have a different signature and don't provide the actual event as parameter like @input does.
Of course there are always ways around it. Ultimately, I could build my own component that wraps <input>, but that's the whole point of using a library, making live easier, not harder...
If I already have full type support on <input> incl. error checks and IDE support, I'd hope to get the same (and some more) from <UInput>.


Question: Is it possible to dump the final webpack config?

When using laravel-mix with 3rd party plugins, if I run in to an issue is there a way to extract the webpack config to show them?

Mix dispatches a configReady event with the webpackConfig object.
You should be able to listen for it using something like this:
Mix.listen('configReady', function(webpackConfig) {
    // Add code here to output the webpack config or dump it to a file.
})

This is awesome! Thanks @kohenkatz, I never would have found that.

You can also use:
mix.dump()

listen is no more exposed! There is after() or then(). Is it possible to extract the config from them ?


ImageJob not in Completed or Failed stage

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
When ImageJob reaches "imagejob not in completed or failed phase" , the ImageJob should be cleaned up so other jobs can still run.
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Eraser version:
Kubernetes version: (use kubectl version):

Closing issue - reached out to AKS team to disable ImageCleaner add-on when Eraser is already present.
cc @WilliamRockwellEvans


Filler character

Hi, what is the recommended way to fill the rest of statusline with a single character? I know that it is possible to do with spaces, but what if I want to use other character than space?
There are two possible solutions I could think of:

Using flexible components with a looot of children (providing all possible lengths of the fill), and
manually computing the length based on other components and window width, which seems that it will be much more efficient.

Thanks!

You are looking for :h 'fillchars' stl field

Thanks for the quick reply :)
I know about fillchars, which works fine for "global" fillchars. However, I can't hide statusline e.g. in NvimTree buffers
vim.api.nvim_create_autocmd("FileType", {
    pattern = "NvimTree",
    callback = function()
        local set = vim.opt_local
        set.fillchars = { stl = " ", stlnc = " "  }
    end
})

It looks like fillchars is really a global option, however, I managed to hide the statusline in NvimTree like this:
condition = function()
    return not conditions.buffer_matches {
        filetype = { "NvimTree " },
    }
end,

Thanks for the help!


(man): Update puppet.conf.5

I fixed this typo error. I think the right location would be this Ronn tool maybe?!

Hi @0xflotus thanks for your contribution! The man page is autogenerated from lib/puppet/defaults.rb. Could you update your PR?

Can one of the admins verify this patch?

Hi @0xflotus thanks for your contribution! The man page is autogenerated from lib/puppet/defaults.rb. Could you update your PR?

Of course :) there is now a new PR #8121


Promote BuildStream 2.0

This is a non-development task, we might want to track it in a different manner but .. let's start with a Github issue.
Now that Bst 2.0 is ready for release, we should consider how to promote its use.
Talks

OSSEU 2022 - done, video
ApacheCon 2022 - done, writeup
FOSDEM 2023 - ?
other ideas... ?

Articles

LWN - ?
Opensource.com - ?
Codethink blog - ?
other ideas ... ?

Merchandise

Stickers (to be handed out at conferences, etc.)
T-shirts ? (these are logistically tricky due to size)

Videos

Convert some of the BuildStream 2.0 examples as screencasts on YouTube

BuildStream needs to get related to some killer projects. For example, to bootstrap Debian/Fedora/OpenWRT with BuildStream, based on Freedesktop SDK.


yarn build --since | not building anything.

Describe the bug
yarn build --since with commit hash or number of commits are not working
Also, it shouldn't build the dependencies. Instead it should do other way round (Let's say if package file got changed, then we should build whoever(apps) using the package
To Reproduce
Steps to reproduce the behavior:
yarn build --since |
yarn build --since 2
[ Summary ]---------------------------------------------------------------------
Success: 0
Fail: 0
Skipped: 0
Up to date: 0
Total: 0
Runtime (wall): 0.01s
[ build finished ]--------------------------------------------------------------
➤ YN0000: Done in 0s 12ms
Expected behavior
build should happen
Desktop (please complete the following information):

OS:  macOS

@ojkelly
It looks by adding --relative as an argument to git diff, it started to partially work. However, building dependencies is still an issue
https://github.com/ojkelly/yarn.build/blob/main/packages/plugins/shared/src/changes.ts#L14
https://github.com/ojkelly/yarn.build/blob/main/packages/plugins/shared/src/changes.ts#L17
    if (options.commit) {
      cmd = `git diff --name-only ..${options.commit}`;
    }
    if (options.sinceBranch && options.sinceBranch.length > 0) {
      cmd = `git diff --name-only ${options.sinceBranch}...`;
    }

maybe we can pass git diff options ?


multiple tabs on one side

Hello there,
you can display multiple tabs on a page?
example:

1
2
3

4
5
6

Do you mean having multiple instances? In that case you can just reference them with a jQuery selector. Example:

...

...

$('#tabs1,#tabs2').responsiveTabs();

yes thanks!

Btw, you could of course also use

...

...

$('.tabs').responsiveTabs();

Which is a bit more scalable :)


Injector: Add support for optional launcher arguments

Currently, if you write:
@ExecuteBefore(STARTED)
void onStarted(FooComponent foo) {
    // Do something on started
}

this will add a hard dependency on the FooComponent and if no implementation of it exists, then an exception will be thrown. If the foo instance is optional, you would have to write:
@ExecuteBefore(STARTED)
void onStarted(Injector injector) {
    Optional<FooComponent> oFoo = injector.get(FooComponent.class);
    if (oFoo.isPresent()) {
        FooComponent foo = oFoo.get();
        // Do something on started if foo is present
    }
}

It would be a lot more readable and you wouldn't have to expose the Injector interface if there was an @Optional annotation in the injector like this:
@ExecuteBefore(STARTED)
void onStarted(@Optional FooComponent foo) {
    // Do something on started if foo is present
}

The api has been modified slightly to avoid collisions between the proposed @Optional annotation and the java Optional-interface. Instead of:
@ExecuteBefore(STARTED)
void onStarted(@Optional FooComponent foo) {
    // Do something on started if foo is present
}

You can now write:
@ExecuteBefore(value=STARTED, orThrow=false)
void onStarted(FooComponent foo) {
    // Do something on started if foo is present
}

onStarted will either be invoked with a valid FooComponent or not at all.


[1.12]How reload scripts?

Why did not you add a command to restart the scripts?
MC 1.12 and CT CraftTweaker2-1.12-4.0.3
Not work:
/ct reload
/mt reload

https://www.reddit.com/r/feedthebeast/comments/6oxjtd/lets_talk_crafttweaker_reload/


API: move ostypeid from DB id to DB uuid

Description
I think it's the last entity represented as a Long in the API which hasn't been yet moved to an UUID. It will be painful for API tools to move from int to String but changing the attribute name looks weird too. Let's do this last change of attribute type and we should be able to close the story of ID -> UUID for good.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

GitHub Issue/PRs
Fixes #2528
Screenshots (if appropriate):
How Has This Been Tested?

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
Testing
[ ] I have added tests to cover my changes.
[x] All relevant new and existing integration tests have passed.
[ ] A full integration testsuite with all test that can run on my environment has passed.

This will also align the attribute type which is already an uuid in listTemplates.

totally agree this should happen @marcaurele . Just wondering why it is only a db id on output?
@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✖debian. JID-1975

debian packaging failed
@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1978

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-2549)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 94529 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2608-t2549-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_certauthority_root.py
Intermitten failure detected: /marvin/tests/smoke/test_vm_life_cycle.py
Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py
Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
Smoke tests completed. 63 look OK, 4 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_secured_vm_migration
Error
38.41
test_vm_life_cycle.py

test_02_not_secured_vm_migration
Error
37.52
test_vm_life_cycle.py

test_03_secured_to_nonsecured_vm_migration
Error
37.39
test_vm_life_cycle.py

test_04_nonsecured_to_secured_vm_migration
Error
37.39
test_vm_life_cycle.py

test_11_migrate_volume_and_change_offering
Error
127.73
test_volumes.py

test_01_redundant_vpc_site2site_vpn
Failure
227.77
test_vpc_vpn.py

test_hostha_enable_ha_when_host_in_maintenance
Error
4.54
test_hostha_kvm.py

I'm seeing some new errors, can you check @marcaurele
@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian.  Merging this based on reviews and tests.


cc-metric-store invalid timestamp: line-protocol value out of range

When trying to configure cc cc-metric-collector sends the following line
cpu_system,cluster=testcluster,hostname=hpc-dev-cpu01,type=node,unit=Percent value=0.399993142477566<PHONE_NUMBER>204515557

This leads to this problem in cc-metric-store
 /api/write error (decoding line protocol for cluster 'testcluster'): timestamp : 0x3 with error : "invalid timestamp: line-protocol value out of range"

When trying to take a closer look at the situation I tried to add some debugging code to decodeLine in https://github.com/ClusterCockpit/cc-metric-store/blob/main/internal/api/lineprotocol.go
For instance https://github.com/ClusterCockpit/cc-metric-store/blob/main/internal/api/lineprotocol.go#L267
and I realize that there are many unknown tags and most of the time when this error occurs a unknown tag is present as well.
Is this the intended behavior?

Hi @BlackLotus,
The epoch timestamp you specify is in nanoseconds. CCMS only supports epoch timestamp in seconds as of now.
Could you please specify the epoch timestamp in seconds and then try again ?

Switched to developer branch for it to work. It would be really nice to either merge it or write all of this into the documentation.
Should I keep the issue open until it is merged/documented or should I close the issue?
Anyway thank you so much for the help

As of now there should be no difference between main branch or devel branch because main branch was merged from devel branch a few days ago. Both should function exactly the same way. =)
The current problem is with the timestamp handling, so regardless of the tags, it will fail.
However, I am kind of skeptical with the assertion that specifying unknown tags also throws this error.
I will check and create an issue myself if I find it that it fails with unknown tags. It should not in general.
Also, I would rather open an enhancement to support nanoseconds or seconds automatically from influxDB line protocol. It is documented here with an example but still it specifies nanoseconds. We will get it done.


Add prompt_text

Enable custom prompt by allowing the prompt_text argument in the query API

I think we'll also want to add support for prompt_name.


Notebook getting started profiles

Testing #125014
Instead of setting a whole set of settings individually, why not introduce a new setting that is a profile, that could evolve more easily. Users can still override specific behavior with individual settings, but the profile will becomes the base. IMO, it would declutter the all the changes made here and allow more flexibility going forward.

This is one possibility for evolving https://github.com/microsoft/vscode/issues/122481

We experimented with this in the past, have moved away from it for now, may revisit at some point in the future though.


Clicking a view twice on the repeater removes the header.

Not happening in default implementation: http://getfuelux.com/javascript.html#repeater

Not happening in snippets: http://fuelux-snippets.herokuapp.com/repeater-views

Implementation bug. Up to implementor to disable button after clicked.


Add Kubernetes manifests.

I'm happy to change anything here, answer questions, or add more comments; let me know.

Looks good to me 👍


Is it possible to make an entire form read-only?

Use case - using schema form for editing objects.   Some users cannot
edit these objects but should be able to view them.
Another use case - some objects are predefined in the system and cannot be edited,
would like to use the same schema and layout for these objects.
Would like to set something on the form via script or binding where I can make the whole
form read-only including disabling the submit button.
Is this possible?
Thanks.

I made this happen by putting
`  <fieldset [disabled]="item.readonly">
<json-schema-form [form]="itemForm".... >

`

I made this happen by putting a fieldset wrapper around the json schema form:
          <fieldset [disabled]="item.readonly">               <json-schema-form [form]="itemForm" ... >           </fieldset>

Yes, there's a fairly straightforward way to do this. Just add "readonly": true to your defaultOptions object, which will make it the default for every widget.
In your site, set angular2-json-schema-form's options input to the following:
{
  "defaultOptions": { "readonly": true }
}

Or, in the demonstration playground (which uses the combined form input), to make any schema read-only, add the following, starting on the second line:
  "options": {
    "defaultOptions": { "readonly": true }
  },

@dschnelldavis Did you mean like this?
It does not work, though, I was able to modify attributes, look for "(changed)" in them.

It is ignored it seems.


An 1250 osmo transfers

I am not seeing any IBC transfers into OSMO in the table output.  Here is my FTT transaction showing ATOM transfer into osmo wallet
https://www.mintscan.io/osmosis/txs/5D39EC9700494FBA63023CCC5C37050CA02D4B4B4EC17D882B96EBBA28C8E109
select * from osmosis_dev.silver.transfers where sender not like 'osmo%';

Looks like we got some where we are showing delegations as transfers?
9170DFA36B6F21EAFBC92B9B51C8456C52D203A7FB6204102B9E9704B9365E2E
This one looks like it has an extra record?
0C16E045F226FFE7C3E037D946E1CF7318827C2DC7409F51074F7BDE01953628

Looks like we got some where we are showing delegations as transfers?
9170DFA36B6F21EAFBC92B9B51C8456C52D203A7FB6204102B9E9704B9365E2E
This one looks like it has an extra record?
0C16E045F226FFE7C3E037D946E1CF7318827C2DC7409F51074F7BDE01953628

Seems like the extra 6500 in the 2nd transaction is actually the fee


Option to disable on links with many descenders

Words like “piggy” may look worse with descender-awareness
Source

Closing as works as designed, since I believe that even in this extreme situation, SU wins.


Unnamed (tuple) enum variants are unsupported for internally tagged enums

Defining the following enum:
#[derive(serde::Serialize, utoipa::ToSchema)]
#[serde(tag = "type")]
enum Foo {
    Bar,
    Baz(Payload),
}

#[derive(serde::Serialize)]
struct Payload {
    a: String,
}

I get the following error from utoipa:

Unnamed (tuple) enum variants are unsupported for internally tagged enums using the tag =  serde attribute
Try using a different serde enum representation

While this works fine:
#[derive(serde::Serialize, utoipa::ToSchema)]
#[serde(tag = "type")]
enum Foo2 {
    Bar,
    Baz { a: String },
}

Both produce the same JSON, so why is it not possible to derive the schema in the first case?

This is a serde.rs limitation unfortunately.

This representation works for struct variants, newtype variants containing structs or maps, and unit variants but does not work for enums containing tuple variants. Using a #[serde(tag = "...")] attribute on an enum containing a tuple variant is an error at compile time.

Quote from serde.rs enum representation docs https://serde.rs/enum-representations.html

Thanks for your quick answer!

This representation works for struct variants, newtype variants containing structs

and that's what I am doing in my example. So serde is not the limiting factor here.
Also, in utoipa 1.1.0 the following did work:
#[derive(serde::Serialize, utoipa::Component)]
#[serde(tag = "type")]
enum Foo {
    Bar,
    Baz(Payload),
}

but if I upgrade to 2.0.0 and replace Component with ToSchema, it no longer works.

Right, it might be because of mistakenly taking Baz(Payload) as tuple type, when it actually should be error when Baz would have more arguments to it like so Baz(Payload, AnotherType) This should produce the error you encountered. I need to investigate this and is regression since there has been quite a few changes since the last release. I hope to resolve this asap. Thanks for your input. :slightly_smiling_face:


Add test case to test rewind of cached streams

This test case tests the following block:
https://github.com/slimphp/Slim-Psr7/blob/23015a8814382c244315602d44cb02d412b6b059/src/Stream.php#L158-L161

Coverage remained the same at 99.738% when pulling 1fa1a1f950ef4a36d647f9cdbdd3806bfdd6be61 on adriansuter:patch-stream-test into 23015a8814382c244315602d44cb02d412b6b059 on slimphp:master.


Fixed a redundant error check in Test-PackageDependency.Tests.ps1

/azp run

/azp run

Thanks for fixing this instance. Is the similar instance in Test-MsixDynamicDependency.Tests.ps1 being intentionally skipped?

Same redundancy. No surprise as the cmdlet tests were derived from the function tests.
Fixed to match

/azp run

/azp run

/azp run


great prompt issue with fish shell

My default shell is fish and when I run great prompt I am getting the error below.
🦔 You are now in a great child shell. Type `exit` to return to your great previous shell!
/bin/fish: option requires an argument -- 'f'

Apparently fish doesn't like the -f flag, and it's not actually opening a new shell due to the error.
Thought I'd let you know.

I can't work on this issue now, but I'll start work tomorrow. Thanks for your issue!
In the mean time you can just cd into ~/.greatness/pack/git and run your commands there.

Understood... no rush. Being able to cd into the directory is plenty good for me!

Just got the changes into the mainline, and I gotta say.... Wow, is fish colourful!

Note that its not in the crates.io repo yet, that'll happen later once I get more features done.


Applying wrong PoiTypes to CategoricalLocationDictionary

There seams to be an issue with the newly added methode

PoiEnums.CategoricalLocationDictionary.apply(poiType: PoiTypeDictionary.Value)

The issue occures when a PoiTyp that can not be applied to CategoricalLocationDictionary is applied.

Well leisure does not have a CategoricalLocationDictionary equivalent, so this should not work, right?

Well leisure does not have a CategoricalLocationDictionary equivalent, so this should not work, right?

The issue occures die to another reason. (See #42 )

Well leisure does not have a CategoricalLocationDictionary equivalent, so this should not work, right?

The issue occures due to another reason. (See #42 )


Add basic test_package example

Goes with: https://github.com/conan-io/docs/pull/2853

Using test_package as package name collides with the test_package folder. I would rename it to avoid that duplication.

Using test_package as package name collides with the test_package folder. I would rename it to avoid that duplication.

I changed the name from test_package to testing_packages so there's no misunderstanding


feat: support diffusion dpo and sft

Description
We support SFT and DPO for diffusion models.
An example of diffusion model trained with DPO:

A photo of beautiful mountain with realistic sunset and blue lake, highly detailed, masterpiece

[x] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds core functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide. (required)
[x] My change requires a change to the documentation.
[x] I have updated the tests accordingly. (required for a bug fix or a new feature)
[x] I have updated the documentation accordingly.

LGTM.


Feat: first class preact support

to be able to use mage without having to add preact/compat into your build configuration

@developit
A little help here, while using the makeReactive with the h jsxPragma it still fails to assign currentComponent in the
preact/hooks sub library/package.
and this is specifically with the returned HOC from makeReactive, do you need me to add something else for the translation to work?

Found the issue,
it's that the injected hooks cannot figure out what the parent component is and so setting up _component is impossible for preact to do right now.
I can however extend that and fix this but then that adds a patch that the library shouldn't be doing since any updates to preact would mean updating this library with it making it much harder for me to keep tabs on each update.
While this was necessary to make it easier to keep codebase same for preact and react, I'm going to have to leave it to the user to have to add in preact/compat to their bundler's configuration.


feat: landing page UI

We need to create the landing page UI in Figma as we discussed in the meeting.
Anyone who wants to contribute just comment here and also in the discord.
All the best 🚀

May I work on this issue

Sure @Ankit62042 , I have also invited you to the Figma project.

I would like to contribute to this too.

I'd like to work on this issue

Assigned you @analoguelonewolf @dikshagupta1511

May I work on this issue too?

Sure @Priiyaa , added you to the Figma project. All the best.

I want to work on this issue too

May i work on this issue too? Plz


Harmonize description of crosslink and persistent committee selection

Both phase 0 and phase 1 have code for committee selection that seems to be doing a fundamentally almost identical task, but where code is arguably needlessly duplicated.
The two use different patterns to express what is ultimately the same logic. In crosslink committee selection (phase 0), the logic is in get_shuffling which is used exactly once:
    shuffling = get_shuffling(
        seed,
        state.validator_registry,
        shuffling_epoch,
    )
    offset = slot % SLOTS_PER_EPOCH
    committees_per_slot = committees_per_epoch // SLOTS_PER_EPOCH
    slot_start_shard = (shuffling_start_shard + committees_per_slot * offset) % SHARD_COUNT

    return [
        (
            shuffling[committees_per_slot * offset + i],
            (slot_start_shard + i) % SHARD_COUNT,
        )
        for i in range(committees_per_slot)
    ]

In persistent committee selection (phase 1), the core function is instead get_shuffled_committee, which returns only a single committee instead of a split of the entire validator set.
One way to harmonize the two by having functions as follows (note that this is a non-substantive change; it is purely a change in presentation):
def get_shuffled_committee(validator_indices: [int],
                           seed: Bytes32,
                           index: int,
                           total_committees: int) -> List[ValidatorIndex]:
    """
    Return shuffled committee.
    """
    validator_indices = get_active_validator_indices(state.validator_registry, committee_start_epoch)
    start_offset = get_split_offset(len(validator_indices), total_committees, index)
    end_offset = get_split_offset(len(validator_indices), total_committees, index + 1)
    return [
        validator_indices[get_permuted_index(i, len(validator_indices), seed)]
        for i in range(start_offset, end_offset)
    ]

In phase 0, we now replace the code with:
    indices = get_active_validator_indices(state.validator_registry, shuffling_epoch)
    committee_count = get_epoch_committee_count(len(indices))
    committees_per_slot = committee_count // EPOCH_LENGTH
    return [
        (
            get_shuffled_committee(indices, seed, committees_per_slot * offset + i, committee_count)
            (slot_start_shard + i) % SHARD_COUNT,
        )
        for i in range(committees_per_slot)
    ]

In phase 1, we now replace the code with:
def get_persistent_shuffled_committee(state: BeaconState,
                                     shard: Shard,
                                     committee_start_epoch: Epoch) -> List[ValidatorIndex]:
    seed = generate_seed(state, committee_start_epoch)
    return get_shuffled_committee(state.validator_registry, seed, shard, SHARD_COUNT)

This also allows us to remove the split function, as with the removal of get_shuffling we no longer use it.

Addressed in #776 I believe :)


Segmentation fault on Ubuntu 18.04 on docker

gridcoin v<IP_ADDRESS>(custom build no modification)
Ubuntu 18.04 on docker
Using Boost 1.65.1
root@938cbaa1a5c6:/# gridcoinresearchd list rsa
[
//normal output
]
//a few hours has passed
root@938cbaa1a5c6:/# gridcoinresearchd list rsa
error: couldn't connect to server
[1]+  Segmentation fault      (core dumped) gridcoinresearchd

gridcoin v<IP_ADDRESS> still has the same issue.

<IP_ADDRESS> has been released

Now it seems to be fixed.


Add entity client unit tests

I hav to refactor this part using Vue-class-component prior to write unit tests. I'll handle this.


Updated Navbar Design and Added Responsiveness

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #(issue no.)
Description
[Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.]
Refactored the existing navbar to improve structure and styling.
Implemented responsive design using CSS media queries for better compatibility across devices.
Navbar now adjusts to a single-column layout on smaller screens (below 768px).
Ensured consistency in text alignment and padding for an improved user experience on both desktop and mobile.

Issue No- #160
Type of PR

[ ] Feature enhancement

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes. Make sure to attach before & after screenshots in your PR.]

Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes..                                                                              Please look into it as early as possible as there are no merge conflicts now, and merge it . Thank You

@kekubhai Please see the conflicts . Resolve the conflicts . Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


SecAuditLogType HTTPS How to configure

modsecurity.conf   What parameters need to be set for the file

Hello @zxp2mmy ,
For that ModSecurity v3 functionality, you need to:

set the SecAuditLogType HTTPS (as described https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-(v2.x)-Configuration-Directives#secauditlogtype)
and then set the address with SecAuditLogType parameter. E.g.: SecAuditLog http://xxx.xxx.xxx.xxx:port


[DOC] new phone number analyzer plugin

What do you want to do?

[ ] Request a change to existing documentation
[x] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request.
i'm adding a new plugin (optional, not installed by default) to OpenSearch (starting with 2.18.0) for phone numbers. see the description of the PR for more information and examples: https://github.com/opensearch-project/OpenSearch/pull/15915
*Version: 2.18.0
What other resources are available?
see the PR: https://github.com/opensearch-project/OpenSearch/pull/15915

since you assigned this to me: am i expected to provide the PR for this or will someone else do it based on the commit message in the linked PR (once it's merged)?

@rursprung usually implementors of the feature provide the documentation update, the documentation team will help to shape it properly, thank you.


Implement glide

Implement glide for sprites, similar to Scratch.
This might done using Evan's idea for a blocks thread, but it might be simpler and better to just do the glide on a separate thread, similar to how sprites move under setSpeed.
Note that Scratch's Glide command is a blocking command, so we would do presumably do this using Evan's blocks thread.

Implementing a non-blocking guide was trivial but would probably confuse the user. Should we offer a non-blocking option or just make it always blocking? A pro argument is so someone can have multiple glides take place at the same time. A con argument is that it's confusing to have multiple options. Let me know what you think and if I should post to the list.
In either case, we have to figure out what to do with collisions while gliding.
@ewpatton could you please point me to your blocks thread or other relevant technology?

Just off the top of my head, I think glide should block.  But I could be
convinced otherwise.
== Hal
Hal Abelson
<EMAIL_ADDRESS>Prof. of Comp. Sci. and Eng.
MIT Dept. of Elec. Eng. and Comp. Sci.
On Fri, Aug 16, 2019 at 6:21 PM Ellen Spertus<EMAIL_ADDRESS>wrote:

Implementing a non-blocking guide was trivial but would probably confuse
the user. Should we offer a non-blocking option or just make it always
blocking? A pro argument is so someone can have multiple glides take place
at the same time. A con argument is that it's confusing to have multiple
options. Let me know what you think and if I should post to the list.
In either case, we have to figure out what to do with collisions while
gliding.
@ewpatton https://github.com/ewpatton could you please point me to your
blocks thread or other relevant technology?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mit-cml/appinventor-sources/issues/1062?email_source=notifications&email_token=AAGAXNZRP32N2THYV2LWCJTQE4R5BA5CNFSM4EJKGRV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4P2U3Q#issuecomment-522168942,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGAXN3QOHT7LJW7KDNR7FLQE4R5BANCNFSM4EJKGRVQ
.

See proposal: https://docs.google.com/document/d/1fMbRtCLAjDqLaNrAlnHLa7fC5QvPGDKBBtTt554p1jU/edit?usp=sharing


parse sitemap

It would be useful to parse a sitemap of a domain to test all subpages / onsite links.

Koa11y 4 is will be a complete redesign. It is planned to include a project based system so you can have a site and multiple pages under it.
This feature request would not meet MVP for the new version, but could go in to a later release after 4.0.0.

Right. I'll probably provide a PR with the feature based on v4 and join the design discussions later this year to help with the integration of it.


Improve matrix solver UI

The matrix solver UI is pretty unintuitive, and there's ideas to improve it that I should be able to do. Below are some suggestions by users.

So I am now aware the matrix solver is probably not adjustable, but depending on the interface with it, some of these might be feasible.
UI - In the popup, give details on the ranges for each possible resource, if it will increase or decrease, and specifically let you choose one of those. I don't mind producing extra petroleum, but I can't exactly consume more of it since I have zero.
Linearly Dependent - When this goes off from you selecting the "Wrong" unrestricted items, you can't unselect that last unrestricted item, but must either remove recipes or or turn the matrix solver off, which removes any void recipes or previously chosen unrestricted items.
Also, I would prefer being able to have a list of those recipes and be able to say "I prefer Recipe A over Recipe B, use A as much as you can then switch to B" or something like that.
Isolation. Subfactories, currently, are mere organization tools. They only make things look nicer, by hiding complexity, but don't actually act as seperate subfactories. Suggestion that the inside of a subfactory is treated entirely like a encapsulating class, such that its insides are completely blackboxed to any higher level factory. So for instance, you put a Koverox process in there, matrix solver on, and it figures out the loop. You go back up a level, and it just treats that subfactory as a "virtual recipe" which consumes 2 depleted uranium to make 1 enriched uranium.
Locking. Allow recipes to be "Locked" such that the matrix solver can't touch them, but has to work around them. As far as it is concerned, a locked "Gear" recipe just adds a demand to the system of producing 2 iron and consuming 1 gear.
Minimax. - Instead of absolute values of whatever, have ranges. All resources are +- infinite by default, but if you demand an output, it defaults to a minimum value given, You can lock that by adding a max. Inputs are the same, where you are inputing at least this amount. The matrix solver then runs inside those constraints, which you can narrow down until it is trapped at one chosen solution.

More stuff

More ideas

Try to prevent user from adding recipes that would make the situation linearly dependent. It still can by removals maybe? Or not. Still probably possible.
Add warning when solver produces bad result (0 or negative numbers)

I improved the ergonomics a bit with this commit, but there is more that could be done.


Fix TeraMath version to 1.1.0

This avoids checking repeatedly for new versions, which is not necessary.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/198/
Hooray Jenkins reported success with all tests good!


Support ObservedGeneration for Status

Describe the feature request
In Knative, we'd like to use Istio VirtualService's Status field to determine if a user service is ready to receive traffic.
However, there currently is no good way for us to know whether the Status we get is the latest one. We can't know if Istio has successfully reconciled all patches we've made.
ObservedGeneration is the best way to go about this as it's an established pattern. It simply involves keeping a property on the Status that is set to the resource's metadata.Generation after the controller has finished reconciling the resource. When status.ObservedGeneration == metadata.Generation, we know that all updates have been applied.
Describe alternatives you've considered
We've considered using lastTransitionTime for this, but there are a few issues:

We don't currently track a lastUpdateTime for our resources, so this would require additional work.
This opens us up to clock skew issues.

[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure
Additional context

@therealmitchconnors @jrbancel


[skip-ci] rpm: aardvark-dns is a hard dep across the board

@Luap99 ready for merge. thanks

/lgtm

Did we enable merge pool for netavark? tide status says in merge pool.

I think @cevich changes to actually enforce the merge protection on the Total Success task broke [skip-ci] as Total Success is not run here. @cevich can you fix this?
I guess for now I just merge manually.


switch: do not mask systemd unit

If we mask it we won't be able to start the OSD container since now the
osd container use the osd ID as a name such as: ceph-osd@0
Fixes the error:  Failed to execute operation: Cannot send after transport endpoint shutdown
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>

Need BZ

jenkins test pipeline

jenkins test pipeline

jenkins test pipeline