[AARCH64] Building TF 2.15.0 from sources failed with undefined __Int8x8_t

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
2.15.0
Custom code
Yes
OS platform and distribution
RHEL 8
Mobile device
No response
Python version
3.9
Bazel version
6.1.0
GCC/compiler version
GCC 12.3
CUDA/cuDNN version
Cuda 12.2 , cuDNN 8.8.0
GPU model and memory
No response
Current behavior?
Building TF 2.15.0 from sources for aarch64 fails with error like [a]. Note that building TF 2.15.0 from sources for x86_64 worked fine.
[a]
ERROR: <path>/tensorflow-2.15.0/tensorflow/core/kernels/BUILD:5131:18: Compiling tensorflow/core/kernels/sparse_tensor_dense_matmul_op_gpu.cu.cc failed: (Exit 4): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target //tensorflow/core/kernels:sparse_tensor_dense_matmul_op_gpu)

    TF2_BEHAVIOR=1 \
    TF_CUDA_COMPUTE_CAPABILITIES=compute_60,compute_70,compute_75,compute_80,compute_89 \
    TF_CUDA_PATHS=<path>/cudnn/<IP_ADDRESS>-7bc7095db72117b743b32c95e6e3687e \
    TF_CUDA_VERSION=12.2 \
    TF_SYSTEM_LIBS=absl_py,boringssl,com_github_grpc_grpc,curl,cython,eigen_archive,flatbuffers,gif,libjpeg_turbo,org_sqlite,pasta,png,pybind11,zlib \
  external/local_config_cuda/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -MD -MF bazel-out/aarch64-opt/bin/tensorflow/core/kernels/_objs/sparse_tensor_dense_matmul_op_gpu/sparse_tensor_dense_matmul_op_gpu.cu.pic.d '-frandom-seed=bazel-out/aarch64-opt/bin/tensorflow/core/kernels/_objs/sparse_tensor_dense_matmul_op_gpu/sparse_tensor_dense_matmul_op_gpu.cu.pic.o' -DEIGEN_MPL2_ONLY '-DEIGEN_MAX_ALIGN_BYTES=64' -DHAVE_SYS_UIO_H -DTF_USE_SNAPPY '-DBAZEL_CURRENT_REPOSITORY=""' -iquote . -iquote bazel-out/aarch64-opt/bin -iquote external/com_google_absl -iquote bazel-out/aarch64-opt/bin/external/com_google_absl -iquote external/nsync -iquote bazel-out/aarch64-opt/bin/external/nsync -iquote external/com_google_protobuf -iquote bazel-out/aarch64-opt/bin/external/com_google_protobuf -iquote external/local_tsl -iquote bazel-out/aarch64-opt/bin/external/local_tsl -iquote external/com_googlesource_code_re2 -iquote bazel-out/aarch64-opt/bin/external/com_googlesource_code_re2 -iquote external/farmhash_archive -iquote bazel-out/aarch64-opt/bin/external/farmhash_archive -iquote external/fft2d -iquote bazel-out/aarch64-opt/bin/external/fft2d -iquote external/highwayhash -iquote bazel-out/aarch64-opt/bin/external/highwayhash -iquote external/gif -iquote bazel-out/aarch64-opt/bin/external/gif -iquote external/libjpeg_turbo -iquote bazel-out/aarch64-opt/bin/external/libjpeg_turbo -iquote external/zlib -iquote bazel-out/aarch64-opt/bin/external/zlib -iquote external/eigen_archive -iquote bazel-out/aarch64-opt/bin/external/eigen_archive -iquote external/ml_dtypes -iquote bazel-out/aarch64-opt/bin/external/ml_dtypes -iquote external/local_config_cuda -iquote bazel-out/aarch64-opt/bin/external/local_config_cuda -iquote external/snappy -iquote bazel-out/aarch64-opt/bin/external/snappy -iquote external/double_conversion -iquote bazel-out/aarch64-opt/bin/external/double_conversion -iquote external/nccl_archive -iquote bazel-out/aarch64-opt/bin/external/nccl_archive -iquote external/local_config_rocm -iquote bazel-out/aarch64-opt/bin/external/local_config_rocm -iquote external/local_config_tensorrt -iquote bazel-out/aarch64-opt/bin/external/local_config_tensorrt -iquote external/local_xla -iquote bazel-out/aarch64-opt/bin/external/local_xla -Ibazel-out/aarch64-opt/bin/external/ml_dtypes/_virtual_includes/float8 -Ibazel-out/aarch64-opt/bin/external/ml_dtypes/_virtual_includes/int4 -Ibazel-out/aarch64-opt/bin/external/local_config_cuda/cuda/_virtual_includes/cuda_headers_virtual -Ibazel-out/aarch64-opt/bin/external/nccl_archive/_virtual_includes/nccl_config -Ibazel-out/aarch64-opt/bin/external/local_config_tensorrt/_virtual_includes/tensorrt_headers -isystem external/nsync/public -isystem bazel-out/aarch64-opt/bin/external/nsync/public -isystem external/com_google_protobuf/src -isystem bazel-out/aarch64-opt/bin/external/com_google_protobuf/src -isystem external/farmhash_archive/src -isystem bazel-out/aarch64-opt/bin/external/farmhash_archive/src -isystem external/gif/include -isystem bazel-out/aarch64-opt/bin/external/gif/include -isystem external/libjpeg_turbo/include -isystem bazel-out/aarch64-opt/bin/external/libjpeg_turbo/include -isystem external/zlib -isystem bazel-out/aarch64-opt/bin/external/zlib -isystem external/eigen_archive/include/eigen3 -isystem bazel-out/aarch64-opt/bin/external/eigen_archive/include/eigen3 -isystem external/ml_dtypes -isystem bazel-out/aarch64-opt/bin/external/ml_dtypes -isystem external/ml_dtypes/ml_dtypes -isystem bazel-out/aarch64-opt/bin/external/ml_dtypes/ml_dtypes -isystem external/local_config_cuda/cuda -isystem bazel-out/aarch64-opt/bin/external/local_config_cuda/cuda -isystem external/local_config_cuda/cuda/cuda/include -isystem bazel-out/aarch64-opt/bin/external/local_config_cuda/cuda/cuda/include -isystem external/local_config_rocm/rocm -isystem bazel-out/aarch64-opt/bin/external/local_config_rocm/rocm -isystem external/local_config_rocm/rocm/rocm/include -isystem bazel-out/aarch64-opt/bin/external/local_config_rocm/rocm/rocm/include -isystem external/local_config_rocm/rocm/rocm/include/rocrand -isystem bazel-out/aarch64-opt/bin/external/local_config_rocm/rocm/rocm/include/rocrand -isystem external/local_config_rocm/rocm/rocm/include/roctracer -isystem bazel-out/aarch64-opt/bin/external/local_config_rocm/rocm/rocm/include/roctracer -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -fPIC -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -fno-omit-frame-pointer -no-canonical-prefixes -fno-canonical-system-headers -DNDEBUG -g0 -O2 -ffunction-sections -fdata-sections -Wno-all -Wno-extra -Wno-deprecated -Wno-deprecated-declarations -Wno-ignored-attributes -Wno-array-bounds -Wunused-result '-Werror=unused-result' -Wswitch '-Werror=switch' '-Wno-error=unused-but-set-variable' -DAUTOLOAD_DYNAMIC_KERNELS '-march=armv8-a' -mno-outline-atomics -Wno-sign-compare '-std=c++17' '-std=c++17' -x cuda '-DGOOGLE_CUDA=1' '--cuda-include-ptx=sm_60' '--cuda-gpu-arch=sm_60' '--cuda-include-ptx=sm_70' '--cuda-gpu-arch=sm_70' '--cuda-include-ptx=sm_75' '--cuda-gpu-arch=sm_75' '--cuda-include-ptx=sm_80' '--cuda-gpu-arch=sm_80' '--cuda-include-ptx=sm_89' '--cuda-gpu-arch=sm_89' '-Xcuda-fatbinary=--compress-all' '-nvcc_options=expt-relaxed-constexpr' -DEIGEN_AVOID_STL_ARRAY -Iexternal/gemmlowp -Wno-sign-compare '-ftemplate-depth=900' -fno-exceptions '-DGOOGLE_CUDA=1' '-DTENSORFLOW_USE_NVCC=1' -pthread '-nvcc_options=relaxed-constexpr' '-nvcc_options=ftz=true' -c tensorflow/core/kernels/sparse_tensor_dense_matmul_op_gpu.cu.cc -o bazel-out/aarch64-opt/bin/tensorflow/core/kernels/_objs/sparse_tensor_dense_matmul_op_gpu/sparse_tensor_dense_matmul_op_gpu.cu.pic.o)
# Configuration: b904123c2caf5d17d0cded6e4d2ae3e922ea3a81ef7f2bc493d95e1ad6f05410
# Execution platform: @local_execution_config_platform//:platform
In file included from external/local_xla/xla/stream_executor/device_options.h:27,
                 from external/local_xla/xla/stream_executor/platform.h:27,
                 from external/local_xla/xla/stream_executor/cuda/cuda_platform_id.h:19,
                 from ./tensorflow/core/platform/stream_executor.h:19,
                 from ./tensorflow/core/util/gpu_launch_config.h:27,
                 from ./tensorflow/core/util/gpu_kernel_helper.h:28,
                 from tensorflow/core/kernels/sparse_tensor_dense_matmul_op_gpu.cu.cc:24:
external/com_google_absl/absl/log/check.h:57: warning: "CHECK" redefined
   57 | #define CHECK(condition) ABSL_CHECK_IMPL((condition), #condition)
      |
In file included from external/local_tsl/tsl/platform/logging.h:26,
                 from external/local_tsl/tsl/platform/refcount.h:23,
                 from ./tensorflow/core/platform/refcount.h:20,
                 from ./tensorflow/core/lib/core/refcount.h:19,
                 from ./tensorflow/core/framework/resource_base.h:23,
                 from ./tensorflow/core/framework/resource_handle.h:21,
                 from ./tensorflow/core/framework/register_types.h:21,
                 from tensorflow/core/kernels/sparse_tensor_dense_matmul_op_gpu.cu.cc:21:
external/local_tsl/tsl/platform/default/logging.h:308: note: this is the location of the previous definition
  308 | #define CHECK(condition)              \
      |
external/com_google_absl/absl/log/check.h:65: warning: "QCHECK" redefined
   65 | #define QCHECK(condition) ABSL_QCHECK_IMPL((condition), #condition)
      |
external/local_tsl/tsl/platform/default/logging.h:542: note: this is the location of the previous definition
  542 | #define QCHECK(condition) CHECK(condition)
      |
external/com_google_absl/absl/log/check.h:88: warning: "DCHECK" redefined
   88 | #define DCHECK(condition) ABSL_DCHECK_IMPL((condition), #condition)
....
....
<gcc-12.3>/bin/../lib/gcc/aarch64-redhat-linux-gnu/12.3.1/include/arm_neon.h(40): error: identifier "__Int8x8_t" is undefined
  typedef __Int8x8_t int8x8_t;
          ^
<gcc-12.3>/bin/../lib/gcc/aarch64-redhat-linux-gnu/12.3.1/include/arm_neon.h(41): error: identifier "__Int16x4_t" is undefined
  typedef __Int16x4_t int16x4_t;
          ^
<gcc-12.3>/bin/../lib/gcc/aarch64-redhat-linux-gnu/12.3.1/include/arm_neon.h(42): error: identifier "__Int32x2_t" is undefined
  typedef __Int32x2_t int32x2_t;
          ^
<gcc-12.3>/bin/../lib/gcc/aarch64-redhat-linux-gnu/12.3.1/include/arm_neon.h(43): error: identifier "__Int64x1_t" is undefined
  typedef __Int64x1_t int64x1_t;

Standalone code to reproduce the issue
it is a build/configure issue

Relevant log output
No response

I have the same build problem on the Arm64 with CPU:
processor	: 0 model name	: ARMv8 Processor rev 1 (v8l) BogoMIPS	: 62.50 Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp uscat ilrcpc flagm CPU implementer	: 0x41 CPU architecture: 8 CPU variant	: 0x0 CPU part	: 0xd42 CPU revision	: 1
The CPU doesn't have the NEON feature at all.  It needs to turn off Arm-neon support at this platform.  Any suggestion to turn off?

Still broken on 2.16.1

This seems to work around the issue for me - built on grace hopper, TF 2.16.1 using spack.
Change to TF:
diff --git a/third_party/absl/workspace.bzl b/third_party/absl/workspace.bzl
index 06f75166ce4b..56d146d65abe 100644
--- a/third_party/absl/workspace.bzl
+++ b/third_party/absl/workspace.bzl
@@ -42,6 +42,7 @@ def repo():
         build_file = "//third_party/absl:com_google_absl.BUILD",
         system_build_file = "//third_party/absl:system.BUILD",
         system_link_files = SYS_LINKS,
+       patch_file = ["//third_party/absl:absl_neon.patch"],
         strip_prefix = "abseil-cpp-{commit}".format(commit = ABSL_COMMIT),
         urls = tf_mirror_urls("https://github.com/abseil/abseil-cpp/archive/{commit}.tar.gz".format(commit = ABSL_COMMIT)),
     )

Patch for absl:
diff --git a/absl/base/config.h b/absl/base/config.h
index 5fa9f0efe5a4..741e320fe40c 100644
--- a/absl/base/config.h
+++ b/absl/base/config.h
@@ -962,7 +962,7 @@ static_assert(ABSL_INTERNAL_INLINE_NAMESPACE_STR[0] != 'h' ||
 // https://llvm.org/docs/CompileCudaWithLLVM.html#detecting-clang-vs-nvcc-from-code
 #ifdef ABSL_INTERNAL_HAVE_ARM_NEON
 #error ABSL_INTERNAL_HAVE_ARM_NEON cannot be directly set
-#elif defined(__ARM_NEON) && !defined(__CUDA_ARCH__)
+#elif defined(__ARM_NEON) && !defined(__CUDACC__)
 #define ABSL_INTERNAL_HAVE_ARM_NEON 1
 #endif

This was fixed in the latest version of absl: https://github.com/abseil/abseil-cpp/pull/1732. Can we bump the vendored copy of absl before the next release? Then we can finally close this issue.


Vim crashes (SEGV) after creating popup with invalid popup mask

Describe the bug
Vim may crash (SEGV) after creating many popups with invalid popup mask.
To Reproduce
$ vim --clean
:call popup_create('test', #{mask: [[0, 0, 0, 0]]})
@:
@@
@@
@@
" ~ repeat over ~
@@
@@
@@
@@
" Vim: Caught deadly signal SEGV
" Vim: Finished.

Expected behavior
Vim does not crash.
Environment

Vim 8.2.2150
macOS Catalina (version 10.15.7)
iTerm2

Regression introduced in 8.1.1753 and 8.1.1754.

backtrace
valgrind log
asan log


docs: reporting.Title best practices

Require Title to be generic for reports of the same
semantics.
Also some minor refactor of reporting section has been
done.

Can one of the admins verify this patch?


New Release

I've noticed that https://github.com/splunk/splunk-sdk-javascript/pull/69 was a major overhaul and fixes some security vulnerabilities. Can we get a release with this patch included? Thanks.

Hi @jirwin, we are waiting on the release to fix some test issues against Splunk 7.2. We'd love some help if you're interested. You can see our progress so far in #70

Hi @shakeelmohamed, did you make some progress on this issue?

Hi @amelcharai, appreciate your follow up. Unfortunately we haven't gotten a release out yet.
If you folks need to use what's in progress so far, you can pull from the develop branch. Let me know if you need guidance around how to do that with npm

Hey folks, wanted to give you all an update. I'll get a release out by next week, just tying off some loose ends, thanks for your patience.

Thanks for you patience @jirwin @amelcharai. I've just released v1.9.0 on npm, give it a try!

Perfect, thank you!


Fix mypy errors

Fixed type errors found by the mypy.
Sorted imports with isort.
Removed unused args in the _get_entries_path, _get_class_ids_path, _get_class_names_path
Added missed requirements (PLW, which gets numpy, setuptools)
Added missed versions to some requirements.
Added exclude = venv to setup.cfg

NOTE: Please check comments marked with LG TODO. I'm not sure how to fix these errors.

Can anybody review this, please? :)

Anybody here???

@patricklabatut Please, review it.

@facebook-github-bot  "We actively welcome your pull requests." - it sounds like a joke. Can anybody, please, review it?

Hey @leo-gan,
Each individual change may be simple, this PR is nevertheless still touching a large percentage of the codebase. Also, as you described it, it is mixing a number of different modifications:

adjustments to project configuration,
re-ordering imports (BTW, we used to apply isort, but I don't recall now why we ended up disabling it),
whitespace removal,
correcting incorrect mypy annotations,
reducing the number of mypy warnings (sometimes by introducing exceptions).

We sincerely appreciate the efforts and the willingness to contribute. If you want to get this PR reviewed and hopefully merged, I think it would make better sense to split it into simpler and more targeted PRs.

Closing now. I'll split this PR to several PRs as requested by @patricklabatut


crop can't be change after componentDidMount

Hello,
first, nice tool, that you've there. thanks for it.
My issue is:
I cannot execute the crop function without getting this error:
Uncaught Error: prop: crop can't be change after componentDidMount     at eval (react-cropper.js:114)     at Array.forEach (<anonymous>)     at ReactCropper.componentWillReceiveProps (react-cropper.js:112)     at eval (ReactCompositeComponent.js:610)     at measureLifeCyclePerf (ReactCompositeComponent.js:75)     at ReactCompositeComponentWrapper.updateComponent (ReactCompositeComponent.js:609)     at ReactCompositeComponentWrapper.receiveComponent (ReactCompositeComponent.js:546)     at Object.receiveComponent (ReactReconciler.js:124)     at Object.updateChildren (ReactChildReconciler.js:109)     at ReactDOMComponent._reconcilerUpdateChildren (ReactMultiChild.js:206)
My src-Image is MobX @observable. Any clue?
Thanks in advance,
Regards,
Lance

ok, seems that the sovled issue#80 "change checked value toString if unchangeable props is a function" is fixing the problem. when will you merge in a next release?

Still got this error with version 1.3.0


[BUG] how to log-in, when I am running kotaemon with docker

Description

I am running this app with docker. but I can not log in. how to login it?
Reproduction steps
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots
![DESCRIPTION](LINK.png)

Logs
No response
Browsers
Chrome
OS
Linux
Additional information
No response

Did you change the default username and passowrd? If not, you can login with admin / admin. Please refer to the following document.
https://github.com/Cinnamon/kotaemon

@tknrych
Thank you! I got it.


more test changes

Problem
Need tests like foundry.
Solution
Make them.
Docs Update
TODO
Notes
TODO

This adds a test/ dir for chat, echo, and fib. It has been tested for rust no-ui specifically.
Still TODO:

add file_transfer test
make sure everything works for non-rust
add docs discussion


python3-x64.osx build failure

Host Environment

OS: OSX
Compiler: revision

Package: python3:x64-osx
Vcpkg version: 2020.06.15-unknownhash
To Reproduce
Steps to reproduce the behavior:
./vcpkg install python3
Failure logs
-Cut and past the appropriate build messages from the console output.
-Please attach any additional failure logs mentioned in the console output.
Building package python3[core]:x64-osx...
-- Using cached /Users/puppuluri/projects/br/core/build/vcpkg/downloads/python-cpython-v3.8.3.tar.gz
-- Extracting source /Users/puppuluri/projects/br/core/build/vcpkg/downloads/python-cpython-v3.8.3.tar.gz
-- Using source at /Users/puppuluri/projects/br/core/build/vcpkg/buildtrees/python3/src/v3.8.3-43b03f2bf0
-- Configuring x64-osx-rel
-- Building x64-osx-rel
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
Command failed: make install -j 9
Working Directory: /Users/puppuluri/projects/br/core/build/vcpkg/buildtrees/python3/src/v3.8.3-43b03f2bf0-x64-osx-release
See logs for more information:
/Users/puppuluri/projects/br/core/build/vcpkg/buildtrees/python3/make-build-x64-osx-release-out.log
/Users/puppuluri/projects/br/core/build/vcpkg/buildtrees/python3/make-build-x64-osx-release-err.log
Call Stack (most recent call first):
ports/python3/portfile.cmake:150 (vcpkg_execute_build_process)
scripts/ports.cmake:76 (include)
Error: Building package python3:x64-osx 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: python3:x64-osx
Vcpkg version: 2020.06.15-unknownhash
Additionally, attach any relevant sections from the log files above.
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.

Hi @puppuluri
Thanks for posting this issue.
Could you please provide the error info from /Users/puppuluri/projects/br/core/build/vcpkg/buildtrees/python3/make-build-x64-osx-release-out.log and /Users/puppuluri/projects/br/core/build/vcpkg/buildtrees/python3/make-build-x64-osx-release-err.log?

I cannot reproduce this issue on my local.
I'm closing this issue for now since no active in a long time.


The latest version of Swift doesn't support empty manifest files.

When I'm trying to include the project on Debian Jessie, the cGTK package doesn't work anymore and I'm getting errors on swift build.

Can confirm this:
$ swift --version
Apple Swift version 3.0.1 (swiftlang-8<IP_ADDRESS> clang-8<IP_ADDRESS>)
Target: x86_64-apple-macosx10.9

$ cat Package.swift
import PackageDescription
let package = Package(
    name: "MyGtkProject",
    dependencies: [
        .Package(url: "https://github.com/TomasLinhart/SwiftGtk", majorVersion: 0, minor: 1)
    ]
)

$ swift build
Cloning https://github.com/TomasLinhart/SwiftGtk
HEAD is now at 50a8cad Copy resources to build folder when build with makefile
Resolved version: 0.1.0
Cloning https://github.com/TomasLinhart/CGtk-OSX
HEAD is now at dc05608 Add a reference for SwiftGtk
Resolved version: 1.0.0
Empty manifest file is not supported anymore. Use 'swift package init' to autogenerate.
error: The package at '/Users/myUser/Documents/Work/MyGtkProject/Packages/CGtk-OSX' has no Package.swift for the specific version: 1.0.0

ubuntu got same error "empty manifest".

same here

This issue should be resolved. Although I had some problems building it on Linux. If you have also some issue please open a new issue.


#45 Fixing bugs with publishReplay

Pull Request Test Coverage Report for Build 252

50 of 58 (86.21%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 87.845%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/rx/operators/internals/PublishReplay.mon
46
54
85.19%

Totals

Change from base Build 249:
0.06%

Covered Lines:
2054

Relevant Lines:
2327

💛  - Coveralls


Treesitter issues

Ideally, treesitter grammars should be installed through Nix, but even with the experimental nixGrammars setting, this isn't happening and for some reason it's downloading and managing the grammars by itself. This leads to issues when updating, because now the grammars were built for an older config and might not work anymore.

This has been fixed w/ #39


Add unit tests of the PlatformBridgeCertValidator

Risk Level: Low
Testing: Yes :)
Docs Changes: N/A
Release Notes: N/A

@alyssawilk PTAL


compatible usb type A cables

Hello,
I lost my official USB type A to power and USB type A to type C cables.
Does anyone have a reference for two compatible USB type A cables?
Thank you in advance,
Pierre

The documentation discusses this https://docs.microsoft.com/en-us/azure/kinect-dk/hardware-specification#power-device
What questions more do you have?

@diablodale Yes indeed I have read the information, such as "The power connector is a 4.5mm OD with 3.0mm ID and a pin diameter of 0.6mm". However I can't find the desired cables on sites like Amazon.
So I wanted to know if the community has any weblinks to cables that work with the kinect (Power to Usb type A and Usb type C to Usb type A).

Amazon has many https://www.amazon.com/s?k=usb-a+to+usb-c&ref=nb_sb_noss_2
https://www.amazon.com/s?k=usb-a+to+power+barrel&ref=nb_sb_noss_2
I recommend you ensure the size and polarity +/- is correct on the barrel cable.


switch names in tests to be inclusive

ran unit tests

merged into https://github.com/ilyar/near-nft

incompatible now with current code


Disable ensure_ascii when dumping to json tool responses

Related Issues

fixes deepset-ai/haystack#8170

Proposed Changes:
Set ensure_ascii=False when dumping to JSON tool or function calls, this way special chars like emojis are not lost.
How did you test it?
I tested manually.
Notes for the reviewer
N/A
Checklist

I have read the contributors guidelines and the code of conduct
I have updated the related issue with new insights and changes
I added unit tests and updated the docstrings
I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.
I documented my code
I ran pre-commit hooks and fixed any issue

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
9 unchanged lines in 4 files lost coverage.
Overall coverage remained the same at 89.551%

Files with Coverage Reduction
New Missed Lines
%

components/tools/tool_invoker.py
1
93.67%

components/tools/openai/function_caller.py
2
92.86%

components/generators/chat/openai.py
3
97.16%

components/tools/openapi/openapi_tool.py
3
58.43%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
1894

Relevant Lines:
2115

💛  - Coveralls


Tiny changes

👷 Deploy Preview for shopify-blog processing.

Name
Link

🔨 Latest commit
8db122a6f0253dc7fefe3c1349b96902aa7703b8

🔍 Latest deploy log
https://app.netlify.com/sites/shopify-blog/deploys/6321419defc0f80008df9c54


chore: migrate to eslint

tslint will be deprecated and projects should be migrated to eslint
See npx https://github.com/palantir/tslint/issues/4534
This PR is still WIP.

I have not much time, someone else can take over.

Ok, closing this PR for now


Add cmd/update-kubernetes-release-version

Fixes: https://github.com/cncf/apisnoop/issues/612
Adds a small Go program to update the version of Kubernetes that is known by the repo as latest and a GitHub action to automate it and make PRs for the changes

Addressed comments from the meeting this morning. Merging!


Translate: Test Utilities

I've done translating Test Utilities to Spanish. #4 @alejandronanez @dmoralesm @carburo
I'm a bit hesitant with the code example translations: Should I translate the method's argument names too?

@icarlossz Thanks! I've just fixed them in a new commit.


Compile Errors on 4.0.0 for Swift v3

Is anyone else getting syntax errors for v4.0.0?

Hey @devdebonair, 4.0.0 is a Swift 2.3 release so it's not surprising this doesn't build yet for Swift 3. We will create another major release for Swift 3 soon.
See https://github.com/lyft/mapper/pull/73 for some more details.

Ok. I should've taken a deeper read.

In the meantime, since the Swift 3 branch wasn't building anymore, here's a PR/branch that once merged will make it build again: https://github.com/lyft/mapper/pull/75.

Please follow along at https://github.com/lyft/mapper/pull/76 now for Swift 3.0 compat!

Not sure if I should comment here or on #76 but is there any ETA on when this will land in Cocoapods @keith? I'm using it in a podspec so I'm unable to point to a specific branch.

We are holding off from releasing an update on CocoaPods right now to give dependencies some more time to migrate their codebases from Swift 2.3 to Swift 3. I did just push a 5.0.0 tag that can be used in podspecs to specify the Swift 3 version of the library.
Let me know if you're running into problems!

@sberrevoets little prob on Swift 3 branch: s.version on podspec is still 4.0.0 :)

Thanks, updated now to be 5.0.0-beta.2.

I've pushed 5.0.0 with Swift 3 support to CocoaPods! Please open new issues for any problems you have! Thanks everyone!


chore: fix logging middleware

Description
Fix logging of ctx tags in the logging middleware by adding the ctx fields to the logged message even if there isn't a stream response. For example, if a StreamedListObjects call is made that doesn't result in any streamed responses, then this PR ensures the store_id and authorization_model_id fields still get logged.
https://user-images.githubusercontent.com/2899204/223250084-65aa718d-47f5-4555-9dba-a61eff4b6fb4.mov
References

Review Checklist

[ ] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[ ] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.14 :tada:

Comparison is base (58591cd) 84.53% compared to head (525e8ed) 84.68%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #608      +/-   ##
==========================================
+ Coverage   84.53%   84.68%   +0.14%
==========================================
  Files          86       86
  Lines       13758    13768      +10
==========================================
+ Hits        11631    11659      +28
+ Misses       1748     1734      -14
+ Partials      379      375       -4

Impacted Files
Coverage Δ

pkg/middleware/logging/logging.go
81.53% <100.00%> (+0.28%)
:arrow_up:

tests/check/check.go
100.00% <100.00%> (ø)

tests/listobjects/listobjects.go
90.40% <100.00%> (+3.33%)
:arrow_up:

internal/graph/check.go
90.41% <0.00%> (+0.22%)
:arrow_up:

pkg/server/server.go
59.32% <0.00%> (+0.28%)
:arrow_up:

pkg/storage/memory/memory.go
94.25% <0.00%> (+0.39%)
:arrow_up:

pkg/server/commands/list_objects.go
87.79% <0.00%> (+5.16%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


安卓构建失败

Could not determine the dependencies of task ':app:processDebugResources'.

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not find any matches for com.facebook.react:react-android:+ as no versions of com.facebook.react:react-android are available.
Searched in the following locations:
- file:/D:/ReactNativeProject/VipApp/node_modules/react-native/android/com/facebook/react/react-android/maven-metadata.xml
- file:/D:/ReactNativeProject/VipApp/node_modules/jsc-android/dist/com/facebook/react/react-android/maven-metadata.xml
- https://dl.google.com/dl/android/maven2/com/facebook/react/react-android/maven-metadata.xml
- https://www.jitpack.io/com/facebook/react/react-android/maven-metadata.xml
Required by:
project :app > project :react-native-mmkv

I have the same issue with
"react-native": "0.70.6",
"react-native-mmkv": "^2.8.0",


Search fails with non latin characters

If searchQuery contains any non latin characters e.g., cyrillic, the search will yield no relevant results. This is due to double encoding of the searchQuery.
https://github.com/appit-online/youtube-search/blob/e2602779dd43d2444c7e645ff64cacae6e954b5c/src/lib/search.ts#L12

should be fixed with version 1.0.7, if not feel free to contact us


Need broadcast support for ttnn.div

Describe the bug
Need broadcast support for ttnn.div.
To Reproduce
Steps to reproduce the behavior:

Run the following code snippet

import torch
import ttnn
import pytest

@pytest.mark.parametrize("device_params", [{"l1_small_size": 24576}], indirect=True)
def test_div(device):
    a=torch.randn(3,1)
    a_ttnn=ttnn.from_torch(a,layout=ttnn.TILE_LAYOUT,device=device)
    b=torch.randn(1,2)
    torch_output=a/b # output_shape = [3,2]
    b_ttnn=ttnn.from_torch(b,layout=ttnn.TILE_LAYOUT,device=device)
    ttnn_output=ttnn.div(a_ttnn,b_ttnn)

Expected behavior
To run without any error
Screenshots
   def __call__(self, *function_args, **function_kwargs):
>       return self.function(*function_args, **function_kwargs)
E       RuntimeError: TT_THROW @ ../ttnn/cpp/ttnn/operations/eltwise/binary/device/broadcast_height_multi_core_program_factory.cpp:25: tt::exception
E       info:
E       BinaryOpType cannot be mapped to BcastOpMath
E       backtrace:
E        --- /home/ubuntu/punith/tt-metal/ttnn/ttnn/_ttnn.so(+0x5d7a09) [0x7f5dc8676a09]
E        --- ttnn::operations::binary::BinaryDeviceOperation::BroadcastHeightMultiCore::create(ttnn::operations::binary::BinaryDeviceOperation::operation_attributes_t const&, ttnn::operations::binary::BinaryDeviceOperation::tensor_args_t const&, tt::tt_metal::Tensor&)

Please complete the following environment information:

OS:  Ubuntu 20.04
Device: WH-n150

Additional context
Used in PETR model, in pos2posemb3d method.

fyi @saichandax

Reopening this as similar issue in SinePositionalEncoding3D class of petr model

I ran into this issue as well.


Vendor dependencies

Extracting everything except k8s+helm dependency updates from https://github.com/giantswarm/resource/pull/6

Going with a ping


Cannot connect to MySQL with JDBC in v9.2.1

Which version and edition of Flyway are you using?
Community Edition 9.2.1
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using? (Type & version)
MySQL 8.0
Which operating system are you using?
flyway:9.2.1-alpine Docker image
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
flyway -connectRetries=20 -url=jdbc:mysql://<host>/<db>?allowPublicKeyRetrieval=true&useSSL=false -user=<user> -password=<password> migrate

What did you expect to see?
Database: jdbc:mysql://<host>/<db> (MySQL 8.0)
Successfully validated 128 migrations (execution time 00:00.126s)
Current version of schema `<db>`: <IP_ADDRESS>
Schema `<db>` is up to date. No migration necessary.

(Note: This is what I see when I use the flyway:9.2.0-alpine Docker image)
What did you see instead?
ERROR: Unable to connect to jdbc:mysql://smr-mysql/smr_live?allowPublicKeyRetrieval=true&useSSL=false
ERROR: 1

I'm seeing the same issue using both the homebrew installed v9.2.1 on a local copy of mysql as well as with between flyway & mysql docker containers.  Downgrading to 9.2.0 works in both cases.

Also seeing the same issue here, only saw it because of a docker system prune and then re-pulling flyway broke the database connection.

This should now be fixed in 9.2.2

I can confirm this is working again with version 9.2.2. Thanks for the quick fix!

Looks like this got broken again in 10.7.1, and works in 10.6:
initialize-db-1          | Flyway OSS Edition 10.7.1 by Redgate
initialize-db-1          |
initialize-db-1          | See release notes here: https://rd.gt/416ObMi
initialize-db-1          | ERROR: Unable to connect to jdbc:mysql://db?allowPublicKeyRetrieval=true&useSSL=false
initialize-db-1 exited with code 1

while with 10.6.0 it works:
initialize-db-1          | WARNING: This version of Flyway is out of date. Upgrade to Flyway 10.7.1: https://rd.gt/3rXiSlV
initialize-db-1          |
initialize-db-1          | Flyway OSS Edition 10.6.0 by Redgate
initialize-db-1          |
initialize-db-1          | See release notes here: https://rd.gt/416ObMi
initialize-db-1          | Database: jdbc:mysql://db (MySQL 8.0)
initialize-db-1          | Successfully validated 2 migrations (execution time 00:00.068s)
initialize-db-1          | Current version of schema `local_application`:<PHONE_NUMBER>0000
initialize-db-1          | Schema `local_application` is up to date. No migration necessary.

Not sure it it is related to this breaking change in 7.0.1
The 'flyway-dev' command-line now requires a license to be set in order to use it. If you are licensed with a Flyway license key, you will need to set this in an environment variable called 'FLYWAY_LICENSE_KEY'. If not, you can follow this documentation on how to set an offline license as an environment variable - https://documentation.red-gate.com/fd/licensing-164167730.html

but I'm not using it to deploy to production environment, it's for local development.

Looks like this got broken again in 10.7.1, and works in 10.6:
initialize-db-1          | Flyway OSS Edition 10.7.1 by Redgate
initialize-db-1          |
initialize-db-1          | See release notes here: https://rd.gt/416ObMi
initialize-db-1          | ERROR: Unable to connect to jdbc:mysql://db?allowPublicKeyRetrieval=true&useSSL=false
initialize-db-1 exited with code 1

while with 10.6.0 it works:
initialize-db-1          | WARNING: This version of Flyway is out of date. Upgrade to Flyway 10.7.1: https://rd.gt/3rXiSlV
initialize-db-1          |
initialize-db-1          | Flyway OSS Edition 10.6.0 by Redgate
initialize-db-1          |
initialize-db-1          | See release notes here: https://rd.gt/416ObMi
initialize-db-1          | Database: jdbc:mysql://db (MySQL 8.0)
initialize-db-1          | Successfully validated 2 migrations (execution time 00:00.068s)
initialize-db-1          | Current version of schema `local_application`:<PHONE_NUMBER>0000
initialize-db-1          | Schema `local_application` is up to date. No migration necessary.

Not sure it it is related to this breaking change in 7.0.1
The 'flyway-dev' command-line now requires a license to be set in order to use it. If you are licensed with a Flyway license key, you will need to set this in an environment variable called 'FLYWAY_LICENSE_KEY'. If not, you can follow this documentation on how to set an offline license as an environment variable - https://documentation.red-gate.com/fd/licensing-164167730.html

but I'm not using it to deploy to production environment, it's for local development.

This is a compatibility issue in the latest version of the MariaDB driver, which the Flyway CLI uses for both MariaDB and MySQL connections (the issue being that it no longer supports MySQL URLs by default). While we investigate a proper solution, here are some possible workarounds:

Add &permitMysqlScheme=true onto the end of your URL.
Download the MySQL driver and add it to the drivers folder in the docker container.

@tjs145 - Thanks, adding &permitMysqlScheme=true worked
initialize-db-1          | Flyway OSS Edition 10.7.1 by Redgate
initialize-db-1          |
initialize-db-1          | See release notes here: https://rd.gt/416ObMi
initialize-db-1          | Database: jdbc:mariadb://db/ (MySQL 8.0)
initialize-db-1          | Successfully validated 2 migrations (execution time 00:00.023s)
initialize-db-1          | Current version of schema `local_application`:<PHONE_NUMBER>0000
initialize-db-1          | Schema `local_application` is up to date. No migration necessary.
initialize-db-1 exited with code 0


feat(terminate): add one yocto check in terminate

require one yocto when terminating contract, as it is done in other enpdpoints that transfer money.

@evgenykuzyakov rebased on top of main and fixed conflicts


Turning off GPC signal from popup page automatically logs user out from their Google / Github Account

Currently, attempting to turn off the GPC signal through the popup will automatically logs the user out from Google/Github account that they are currently logged in. Based on my inspection of the code base, it appears to be due to fact that turning off the signal invokes removeFromDomainlist function, which in turn invokes deleteDomainCookies function. The deleteDomainCookies function is probably not implemented properly and accidentally deletes the user login information, thus resulting in the bug.
A quick fix is by commenting out the deleteDomainCookies from removeFromDomainlist and we can observe that the bug no longer happens. However, I would imagine that it defeats the purpose of deleteDomainCookies. I am personally not familiar with what  deleteDomainCookies is trying to do so maybe someone who is more familiar with this code base can take a look and see if we can fix the bug by changing deleteDomainCookies.
Adding @kubagithub and @SebastianZimmeck to this thread as suggested by the developer who currently works on refactoring of the extension.

Thanks @chunyuema, this is a great catch! Yes, I remember we had discussed this earlier in the year. If I remember correctly, deleteDomainCookies should remove the opt-out cookies associated with a domain, since our intention with the extension is to signal a user's opt-out intent via all possible methods, i.e., if someone opts-out, we should remove all opt-out signals.
Now that this is on our minds we can take a look at which cookies deleteDomainCookies deletes. I can take a look later today to see if I can catch this by glimpsing at the code when I have a moment.

Great, indeed, @chunyuema!

I took a second look at this code and I think we need to find a way to save which cookies preserve your login session. That way we can wipe all of the cookies placed on a domain that is logged out (it will be hard to record all opt-out cookies that exist) except for those. This is because the deleteDomainCookies function just deletes all of those cookies associated with a domain.
Alternatively we can iterate over those cookies that we place and remove those.
These are the two ways I see of implementing a fix for this. I will wait until the refactor to implement something along these lines.

Looking this over again at this point in time, I think we will either need to discuss this or keep this open for a little bit longer. Since this is related to deleting all cookies of a domain, this is still an issue because we actually have not reimplemented the functionality that deletes all the Do-Not-Sell cookies off a domain when a user switches Do-Not-Sell off for a domain. As a result, if we ever reimplement this functionality we still need abide by my comments from above.
Let's discuss today whether or not we want to fully reimplement that or not. That will determine what we do here.

Very good observation, @kalicki1!

I will go ahead and reimplement this functionality as it was prior to refactoring as discussed in today's meeting.

I just pushed some changes to reimplement this functionality. Everything seems to be working as intended; I added a check whether something is being modified in the domainlist right into storage.js, which calls functions to carry out setting/removing the cookies via storageCookies.js's exports.
As a side note related to our IAB cookie implementation, at the moment the IAB cookie for a domain is removed only when all of the 3rd party domains, in addition to the 1st party domain, are chosen to not receive do not sell signals. Regardless of whether the 1st part is off or on, the one IAB cookie is still set to the 1st party domain regardless.

Since cookies will be removed in a future OptMeowt release, I will go ahead and close this issue related to the original bug.


Create and document UI lo-fi diagrams for application

These diagrams should describe to team members roughly how all the features are accessed and fit together. They should provide a base for development going forward.

Have been documented in the wiki. Marking this issue as done.


onSuccess operations when ux_mode is redirect

Hello, I'm using redirection instead of popup to login. The the onSuccess prop doesn't seem to be triggered. Am I using this wrong or is this just the expected behavior?
const googleLogin = useGoogleLogin({
    flow: 'auth-code',
    select_account: true,
    ux_mode: "redirect",
    redirect_uri: "http://localhost:3000/preview/",
    onSuccess: async ({ access_token }) => {
      {...}
    },
    onError: () => {...},
});

Thanks!

Please have a look at this:
https://github.com/anthonyjgrove/react-google-login/issues/165

Hello @dmdum, onSuccess will not be triggered in redirect mode.
instead, Google will redirect you back to the given URL with query param code
like that http://localhost:3000/preview/?code=xxxxxxxxxxxxxxxxxx&scope=email+profile+openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email&authuser=0&prompt=consent
You can get code from query parameters in the URL


Site footer markup & styles

testing notes
designs
desktop / tablet / mobile

footer should be "sticky" (pushed to the bottom of the page on short pages, but accommodates longer pages normally). try going to the homepage vs the about page to see this in action.
links in the footer should go to the correct places, if those places exist (accessibility links, clicking on the logos, etc).
arrangement of items won't be pixel-perfect; I used flexbox to come up with a reasonably spaced approximation. trying to make it match spec exactly would have taken far too much time and css.
order of items in the last line doesn't match spec; there's no way to reorder them without using grid and doing a lot of extra stuff that we don't need. I think we can live with this order.

dev notes

includes the main site nav, which isn't user-editable (first column in the footer)
includes a mocked version of the user-editable secondary nav (second column in the footer)

looks good!


Mining a Mox Reactor results in a Nuclear Reactor

Mod source
Factorio Mod Portal
Which mod are you having an issue with?

[ ] pyalienlife
[X] pyalternativeenergy
[ ] pycoalprocessing
[ ] pyfusionenergy
[ ] pyhightech
[ ] pyindustry
[ ] pypetroleumhandling
[ ] pypostprocessing
[ ] pyrawores

Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[ ] Pypostprocessing failure
[X] Other

What is the problem?
This line here (and the 02, 03, 04) need mox in the mined result:
https://github.com/pyanodon/pyalternativeenergy/blob/8135b4b2c0d939c689fae4ed6cd86b29c65cf83f/prototypes/buildings/nuclear-reactor-mox-mk01.lua#L32
Steps to reproduce
Put down a mox nuclear reactor
Mine it - you get a normal reactor back.
Additional context
No response
Log file
No response

Good catch, thanks!


Make a proper folder structure for the project

Folders:-

public include folders:-

css
js
img

view includes files:-

index.html
resources.html
updates.thml
team.html
contactus.html
-login/signup.html

Change the index.js file to app.js file(outside the folders)

I would like to work on this issue

Folders:-

public include folders:-

css
js
img

view includes files:-

index.html
resources.html
updates.thml
team.html
contactus.html
-login/signup.html

Change the index.js file to app.js file(outside the folders)

I want to work on this

Do I have to put the HTML, CSS, and js file in the respective folders? Also, I have to add an empty app.js file, or do I need to put the code inside it?

Do I have to put the HTML, CSS, and js file in the respective folders? Also, I have to add an empty app.js file, or do I need to put the code inside it?

Add all the HTML files in view folder and CSS and JS in the respective folders inside the public folder. Change index.js file's name to app.js and leave it empty for now!!


Feature Request: Interaction hint

Hi,
great library and more up-to-date than some other components regarding current react depracations. In another library though, there is little nice feature "interaction hint" which adds nice UX for users to see that there is interaction possibility without accidentally hovering the image. https://ethanselzer.github.io/react-image-magnify/#/hint
Would be great to see something similar in this library :-)

Thanks! I will keep this in mind for the next release. In the meantime, if you need a solution now, all of the magnifier components have a renderOverlay render prop that could be used for this purpose. Here's an example:
<Magnifier      imageSrc="./image.jpg"      renderOverlay={active =>           !active && <InteractionHint>Click to zoom</InteractionHint>      } />
No default styling is provided for the render prop content, so in the above example, the InteractionHint component would need absolute position and a z-index of 1 or higher.

Sounds like a reasonable solution. Thanks 👍🏻


Configure pytest to run on staging by default + flags in config

This PR updates pytest configuration:

HUGGINGFACE_CO_STAGING=1 is now automagic :tada: (using pytest-env)
-sv --log-cli-level=INFO is set by default
use --durations=0 to measure and print execution time of each test (I am curious to know where we can improve)

Basically it guarantees that local tests are run the same way as CI tests:
# no more flags !
pytest tests

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Very nice Quality of Life improvement for developing!

Very nice Quality of Life improvement for developing!
Exactly what I thought when googling for a solution :smile:


TextLayer placed wrong on canvas

https://s3.eu-central-1.amazonaws.com/lix-production-public-storage/262.pdf
Configuration:

Version 46.0.2490.86 (64-bit)
Ubuntu (x86_64)
pdfjsVersion = '1.5.477'
pdfjsBuild = '9e927de'

Steps to reproduce the problem:

Just loaded the pdf attached in the viewed.

What is the expected behavior?

I expected the text to be placed correctly.

What went wrong?

Text is not placed the right way.
Also "exponent -" is parsed as the number 2.
Se this link https://s3.eu-central-1.amazonaws.com/lix-production-public-storage/Screenshot_from_2016-09-21_11%3A13%3A16.png

The text is colored red everywhere and I have marked the word "value" -> here it is very wrong.

The "value" part is fixed by recent patches. The "exponent" issue remains.

Closing since the file is no longer available.


Sample app crashes right away on HoloLens 2

I cloned the repo and followed the documentation steps:
https://learn.microsoft.com/en-us/samples/microsoft/mixedreality-sceneunderstanding-samples/microsoftmixedrealitysceneunderstandingsamples---unitysample/
I'm able to build and sideload the app package without issue or error, but it displays an odd image of a room before crashing
I took a video and put it on my YouTube:
https://youtu.be/ZKlBIe1FhJU
Any help is appreciated! I'd love to get this working in my app

I meet with the same issue.  Have you already resolved it?

I faced the same issue.
I solved it by changing the build setting from Debug ARM64 to Release ARM64 in VS 2019.
After creating a new app package with that setting, the app worked as expected.

I met the same problem. And I ran the demo by remoting connect to Hololens2, and even changing the build setting cannot solve the problem.


chore(Netlify): trigger CI

Description
Music year: 2007

List of changes

Issue(s)
Fixes #
How to test

Go to https://deploy-preview-2498--oak-web-application.netlify.thenational.academy
Click on ______
You should see ______

Screenshots
How it used to look (delete if n/a):
{screenshots}
How it should now look:
{screenshots}
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

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


Very minor issue with method placement

Hey, nice work.
Tiny non-issue really, in mechanicalsoup/browser.py
Line 88
Method: submit
That's a public method?  Should it be placed with the other public methods above the private methods,  _build_request and _prepare_request?  I'm assuming those are 'private' methods anyway.
Anyway, this looks pretty great.  Thanks!

Hello from Lilliput! It doesn't bother me. Glad the library is useful to you, thanks for the compliment.


dalfox: 2.5.4 -> 2.6.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/hahwul/dalfox/releases.
meta.description for dalfox is: "Tool for analysing parameter and XSS scanning"
meta.homepage for dalfox is: "https://github.com/hahwul/dalfox"
meta.changelog for dalfox is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/fyhc5jcpww7a7qsm1q0w2bcdw7h1lzwl-dalfox-2.6.1/bin/dalfox passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.6.1 with grep in /nix/store/fyhc5jcpww7a7qsm1q0w2bcdw7h1lzwl-dalfox-2.6.1
found 2.6.1 in filename of file in /nix/store/fyhc5jcpww7a7qsm1q0w2bcdw7h1lzwl-dalfox-2.6.1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
dalfox
docbookrx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fyhc5jcpww7a7qsm1q0w2bcdw7h1lzwl-dalfox-2.6.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dalfox https://github.com/r-ryantm/nixpkgs/archive/95c9e45744c95f38236b6404e5103c960ed2ca76.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fyhc5jcpww7a7qsm1q0w2bcdw7h1lzwl-dalfox-2.6.1
ls -la /nix/store/fyhc5jcpww7a7qsm1q0w2bcdw7h1lzwl-dalfox-2.6.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dalfox

Maintainer pings
cc @fabaff @kalbasit for testing.

Result of nixpkgs-review pr 148993 run on x86_64-linux 1

1 package built:

dalfox


bump torch-mlir to 76209db

Bump to llvm/torch-mlir@76209db

closing. See https://github.com/iree-org/iree/pull/18897


centrifugo: 5.3.2 -> 5.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for centrifugo is: Scalable real-time messaging server
meta.homepage for centrifugo is: https://centrifugal.dev
meta.changelog for centrifugo is: https://github.com/centrifugal/centrifugo/releases/tag/v5.4.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.4.0 with grep in /nix/store/vfg5q7kq80qv2psy0gc5kx157781k9a6-centrifugo-5.4.0
found 5.4.0 in filename of file in /nix/store/vfg5q7kq80qv2psy0gc5kx157781k9a6-centrifugo-5.4.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

centrifugo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vfg5q7kq80qv2psy0gc5kx157781k9a6-centrifugo-5.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A centrifugo https://github.com/r-ryantm/nixpkgs/archive/fc8dbe2ca08679a4a4f387510e5f9d6126628c22.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fc8dbe2ca08679a4a4f387510e5f9d6126628c22#centrifugo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vfg5q7kq80qv2psy0gc5kx157781k9a6-centrifugo-5.4.0
ls -la /nix/store/vfg5q7kq80qv2psy0gc5kx157781k9a6-centrifugo-5.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

centrifugo

Maintainer pings
cc @tie for testing.

Result of nixpkgs-review pr 316458 run on aarch64-linux 1

1 package built:

centrifugo


Asynchronous Pmod_IO or Arduino_IO?

I have a coroutine (implemented using the asyncio library) that polls temperature values in a background-ish way from sensors on a 1-Wire bus. If a read temperature is too high or too low, the coroutine will open or close a pilot gas valve that I have connected via PMOD.
However, whenever Pmod_IO's write() function is called for the device, it incurs a RuntimeError from pmod_devmode.py like this:
File "/opt/python3.6/lib/python3.6/site-packages/pynq/lib/pmod/pmod_io.py", line 131, in write     PMOD_DIO_DATA_OFFSET)   File "/opt/python3.6/lib/python3.6/site-packages/pynq/lib/pmod/pmod_devmode.py", line 263, in read_cmd     raise RuntimeError("PmodDevMode read_cmd() not acknowledged.") RuntimeError: PmodDevMode read_cmd() not acknowledged.
The same occurs with Arduino_IO. Is it possible to use these I/O modules with asyncio?
EDIT: Just wrote a script to toggle a valve with Pmod_IO in an asynchronous coroutine and it worked, so perhaps the library isn't at fault.
It is worth mentioning that I am using pynq's Clocks class to scale fclk0 to 33.33333 MHz for 1-Wire comms, and am using the Arduino header's pin 0 as the 1-Wire inout data port (assigned in VHDL).
Could modifying the base overlay's fclk0 frequency somehow disrupt the way that Pmod_IO reads its "mailbox"? What are some possible causations for this particular RuntimeError?

So I have now confirmed that Pmod_IO will work when instantiating BaseOverlay using "base.bit" and my custom overlay (an extended base design), and will also work for "base.bit" after changing Clocks.fclk0_mhz to 33.33333.
However, Pmod_IO breaks for my custom overlay only after modifying fclk0's frequency, even after setting it back to 100.0 MHz again! It may be something within the custom IP that I've added, but I can't imagine why changing a function clock frequency would raise an error when PmodDevMode read_cmd()? Is this indicating that the cmd_mailbox is never idle??

When you change the clock, does it mean you keep the overlay on PL and only change the clock frequency? That might be disruptive to the microblaze processors?

Hi @VicerExciser, I need to kindly ask you to redirect your question to our forum: https://discuss.pynq.io
That's the dedicated place to receive support from the community.
The issue tracker here is to report bugs in the codebase.
Closing this now, thanks in advance for your collaboration.


Doesn't run

I have the following in my settings.json
{
"ctags-companion.command": "ctags -R --fields=+nKz -f .vscode/.tags --langmap=SystemVerilog:+.v -R rtl /opt/uvm-1.2/src",
"ctags-companion.readtagsEnabled": true,
}
In order to run it the docs say to run "Terminal > Run Task... > Ctags Companion: rebuild tags" but I have no task with that name
I do get an option in the menu for "Ctags Companion: reindex", but when I run it I get an error "Command 'ctags-companion.reindex' not found"

Hi,
When using the latest version of the extension, please try the following settings:
{
    "ctags-companion.command": "ctags -R --fields=+nKz --langmap=SystemVerilog:+.v -R rtl /opt/uvm-1.2/src",
}

Specifically:

Remove -f .vscode/.tags
Remove "ctags-companion.readtagsEnabled": true,

To find the task you may need to select "Show All Tasks":

For convenience you may want to add the following setting:
"task.quickOpen.showAll": true

Perfect, thanks!


hover tooltip not working for journal entries

Thanks for this module.
mouse hover over an icon is not showing the 'tooltip' name popup for journal entries

I notices this issue on some windows (but not all) but didn't had time to fix it yet. I'll try to free some time this week or next one to fix this.

This issue has been fixed in release v1.3.5.


Adding labels for accessibility to dynamically generated inputs.

Do you have a hook to add custom HTML or labels to the dynamically generated inputs such as choices__input/choices__input--cloned ?

Hey, you can manipulate the markup by using the callbackOnCreateTemplates callback


TextFeaturizer component is unable to handle np.nan values

In running the car_sales.csv dataset, an error is thrown

I think this is a duplicate of #2054, #2000, #1587. @dsherry @chukarsten I think we should close some of these out?

Very true, I'll close this one out. I'll add more info to #2054


missing deposit

Hi,
My deposit is missing since 15 hours or so since yesterday.Also need to notify that the address of your wallet yesterday was different that the one you have today for making deposits.Is this the cause that my deposit hasnt been credited still and hence my funds will be lost?
My TX id is 68c931bc0205d52c9f7d6dbe6a6bd688cb76cee0d87c564a989278561d902ca8.
Thanks

for your evaluation the deposit address in monyx's website yesterday was this one 3P8tr1t2KeEyr5Sk16eT97zx28w1SJhM29,where i sent tmy btc.Hope this helps and finally my deposit got credited later today.

@kalpanos1 don't worry, we keep all the addresses assigned to users, so no deposits will be lost.
The deposit should be credited soon, I'll get back to you once the next batch of missing deposits is processed.

@kalpanos1 check your balance, new batch was processed.


k-sigma Transform

Thanks for your great work! The k-sigma parameter in the code seems to be the same for whole CFA. Is it better to use 3 different parameters for R/G/B arrays?

You can try estimating channel-wise noise parameters.
According to my experience, different CFA channels have different noise-params, but the difference is small.
In practice, it is OK to set different params for RGB channel. However, Gr and Gb should use the same param, or it may cause maze artifact in demosaicking due to different denoising strength causing green-imbalance.

You can try estimating channel-wise noise parameters.
According to my experience, different CFA channels have different noise-params, but the difference is small.
In practice, it is OK to set different params for RGB channel. However, Gr and Gb should use the same param, or it may cause maze artifact in demosaicking due to different denoising strength causing green-imbalance.

OK, Thanks  a lot~

OK, Thanks  a lot~


Add Linux prebuilt binaries for armv7 and arm64 and other improvements

This PR adds multiple new features and improvements.

Added armv7 prebuilt binaries for Alpine
Added both armv7 and arm64 prebuilt binaries for Linux (very useful for Raspbian users)
All the jobs that runs on Qemu containers now uses checkout action which supports correct trigger ref
Added publish job completion requirement to all jobs

As always, all these changes were tested on multiple releases, for weeks at better-sqlite3-multiple-ciphers.

Could maintainers comment here? Would be nice to know what to expect - any hope of this getting merged or is this going to be stalled?

sorry for the latency, github didn't send me a notification. LGTM, thanks for the work, @m4heshd, and for the ping, @tkurki
@JoshuaWise are you ok with merging this?

Hey there! There have been no updates in the past 15 days so posting here to bump it.

Thanks for the contribution!


Clarification for authentication in the auth code flow in the Identity and consent management (r0.20.0-rc2)

Problem description/clarification needed
In the Identity and consent management (r0.20.0-rc2) CAMARA Security and Interoperability Profile,
https://github.com/camaraproject/IdentityAndConsentManagement/blob/r0.2.0-rc.2/documentation/CAMARA-Security-Interoperability.md
It is mentioned in the section of “Client Authentication”, this CAMARA document allows one client authentication method, private_key_jwt.
While in the section of “OIDC Authorization Code Flow”, CAMARA RECOMMENDS PKCE for CSRF protection. CAMARA Authorization Servers SHOULD implement PKCE. If PKCE is not used by the Client then the CAMARA AZ must handle state and nonce as defined in OAuth2.
Looking at the “Authorization Code Flow (Frontend Flow)” defined in the “CAMARA APIs Access and User Consent Management”, it is not clear where the private_key_jwt and PKCE are used to secure the API flow.
https://github.com/camaraproject/IdentityAndConsentManagement/blob/r0.2.0-rc.2/documentation/CAMARA-API-access-and-user-consent.md
Question 1:  where the private_key_jwt will be used to authenticate API request, is it on step 11 in the sequence diagram?
Queston 2: How should the PKCE be employed in the front-end auth code flow? Detail description will be appreciated.
Expected action
Please help answer above questions to bring clarity to the documentation.
Additional context

@mingshiwork

In the Identity and consent management (r0.20.0-rc2) CAMARA Security and Interoperability Profile,
https://github.com/camaraproject/IdentityAndConsentManagement/blob/r0.2.0-rc.2/documentation/CAMARA-Security-Interoperability.md

ICM r0.2.0 public release is available, please use it as reference instead of the previous release candidate versions: https://github.com/camaraproject/IdentityAndConsentManagement/blob/r0.2.0/documentation/CAMARA-Security-Interoperability.md

Question 1: where the private_key_jwt will be used to authenticate API request, is it on step 11 in the sequence diagram?
Queston 2: How should the PKCE be employed in the front-end auth code flow? Detail description will be appreciated.

Both private_key_jwt and PKCE (Proof Key for Code Exchange) are mechanisms used in OAuth 2.0 and OpenID Connect to enhance the security of authorization flows, but they serve different purposes and are typically used in different contexts.
The private_key_jwt is a client authentication method as defined in https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication. It is used by clients to authenticate to the authorization server when using the token endpoint. It is the only client authentication method allowed by CAMARA. The client generates a JWT (JSON Web Token) which is signed with its private key. This signed JWT is sent to the authorization server to prove the identity of the client.
You may want to take a look at https://github.com/camaraproject/IdentityAndConsentManagement/blob/r0.2.0/documentation/CAMARA-ICM-examples.md for some usage examples.
Instead, PKCE (Proof Key for Code Exchange by OAuth Public Clients) provides an additional layer of security for the authorization code flow, but it is unrelated to client authentication. PKCE is a mechanism used in the authorization code grant flow to prevent attacks such as authorization code interception, especially when dealing with public clients. The client generates a random code verifier and its corresponding code challenge (usually a hashed version of the verifier). These are used during the authorization and token exchange process to bind the authorization code to the original client request.See https://datatracker.ietf.org/doc/html/rfc7636 for more details.
CC @AxelNennker @sebdewet Please add any other comments you may have.

Question 1: where the private_key_jwt will be used to authenticate API request, is it on step 11 in the sequence diagram?

Yes.
OIDC defines the Token Request in the authorization code flow. Camara defines that the client authentication method is private_key_jwt.

Question 2: How should the PKCE be employed in the front-end auth code flow? Detail description will be appreciated.

Please choose a library or SDK that supports PKCE and meets your other requirements. The OpenId Foundation maintains a list of certified tools. https://openid.net/developers/certified-openid-connect-implementations/
In general, do not implement an openid provider yourself. There are several opensource implementations for which you can also buy support. Please do your own research which best fits your needs.
In case you notice that Deutsche Telekom has its own implementation of an OpenId Provider and call my a hypocrite, let me state that Deutsche Telekom is a very early supporter of the OpenId Foundation and a member of OIDF for many years. We have a long history in participating in IAM standardization and our current end customer-facing OP was implemented before OIDC existed. We are also using other certified OPs in production but requirements change over time and an OP you picked some years ago might not be your choice today.
The same is true for mobile applications and relying party software. Pick an SDK that supports PKCE and fits your requirements.
Avoid implicit flow.
Read OAuth 2.0 Security Best Current Practice
Have a look at the Financial API Security Profile

Hi @jpengar @AxelNennker , thank you for your response
Allow me to join the discussion, as both @mingshiwork  and I are currently working on the CAMARA integration. I believe @mingshiwork is confused about when to use private_key_jwt and when to use PKCE.
Please correct me @jpengar @AxelNennker :
OpenID Connect (OIDC) supports two authentication flows: 2-legged and 3-legged.

CAMARA uses OIDC, and for 2-legged flows (also known as client credentials or client authentication flow), CAMARA only allows the private_key_jwt method.
For 3-legged flows (also known as authorization code flow), CAMARA recommends using the PKCE method.

When to use 2-legged or private_key_jwt?
The term "2-legged" come from 2 legs, refers to a flow where only two parties are involved:

Client: An entity that needs to access resources from the resource server.
Resource Server: A server that stores resources and legally owns them.

In this scenario, you should use private_key_jwt.
GSMA uses this for authentication in Telco FInder, refer to this: https://github.com/GSMA-Open-Gateway/Open-Gateway-Documents/blob/main/Chapters/Chapter 05.md#api-end-points
When to use 3-legged or PKCE?
The term "3-legged" come from 3 legs, refers to a flow where three parties are involved:

Client: An entity that needs to access resources from the resource server.
Resource Server: A server that stores resources but does not legally own them; it only stores the resources on behalf of the resource owner.
Resource Owner: The person who owns the resources stored on the resource server.

In this scenario, you should use PKCE.
Authorization Process Using PKCE
In this case, the client must initiate user authorization by calling the /authorize endpoint with the following parameters:

client_id: The unique identifier for the client application.
response_type: Specifies the type of response expected from the authorization server. Value: code (indicating that the authorization code flow is being used, which will return an authorization code).
redirect_uri: The URI where the user will be redirected after authorization. This URI must match one of the URIs registered with the client.
scope: Defines the level of access the application is requesting. Multiple scopes are space-separated.
state: A unique value to ensure that the authorization response is linked to the correct request. Example: unique-state-value-3.
code_challenge_method: Specifies the method used for the Proof Key for Code Exchange (PKCE). The value S256 indicates that the SHA-256 hash algorithm is used.
code_challenge: A base64-encoded, URL-safe string representing the hashed code_verifier, which is later used to exchange the code for a token.

Redirect After Successful Authentication and Consent
After the user successfully authenticates and grants consent, they are redirected to the specified redirect URI with query parameters, including the authorization code and state.
Query Parameters Breakdown:

code: The authorization code that the client will use to exchange for an access token. This code is short-lived and must be used immediately.
scope: The scopes that were granted during the authorization process. These scopes are space-separated and should match or be a subset of the requested scopes.
state: The same state value that was sent in the original authorization request. This ensures the response corresponds to the correct request. Example: unique-state-value-3.

Token Exchange Process
The client exchanges the authorization code for an access token by making a POST request to the /token endpoint. This request must include the code, redirect URI, client ID, and the PKCE code_verifier.
Parameters Breakdown:

grant_type: Specifies the type of OAuth2 flow. In this case, it’s authorization_code to indicate that the client is exchanging an authorization code for tokens. Example: authorization_code.
code: The authorization code received in the redirect URI after the user’s authorization.
redirect_uri: The same redirect_uri that was used in the original authorization request. This ensures the request is coming from the same client that initiated the flow.
client_id: The same client ID used in the request to /authorize.
code_verifier: The original code verifier used to generate the code_challenge when making the request to /authorize.

@yudaprama and @mingshiwork,
I think there is some confusion about what authentication mechanisms are used and whether they are related to the number of legs of the flow being executed.
PKCE is not a client authentication method, it was originally designed to mitigate code interception attacks in an authorization code flow.
In the CAMARA profile, for all server-to-server calls from the application backend, private_key_jwt is the only method for those endpoints that require authentication. For example, for the token, bc-authorize, revocation or introspection endpoints. There are only confidential clients.
This means that for the token endpoint call in the authorization code flow, private_key_jwt authentication is required, regardless of whether a PKCE code_challenge was used in the previous authorize call.

So, you're essentially mixing 2-legged with 3-legged flows. Is this based on the OIDC spec or is it your own custom specification?
If you're creating a standard, please ensure that it aligns with common specifications. This will allow developers to build using libraries. If you create a standard using your own spec, it means development will have to be done from scratch, leading to significant development costs and time!
I propose to review and revise it to use the common specification in the OIDC spec, which is supported by libraries.

@yudaprama is your question on how to protect ans secure the /authorize endpoint?

@mingshiwork @yudaprama Can we close this issue?


[TASK] Implement the unified Orchestration Core in the 8.7 Alpha chart

Related to
Epic: https://github.com/camunda/distribution/issues/331
Overview
Implement the unified Orchestration Core in the 8.7 Alpha chart and remove the following individual components:

Zeebe / Zeebe Gateway
Operate
Optimize
Tasklist
Execution Identity (it was disabled by default in 8.6)

Actions

### Sub-tasks
- [ ] The new component should use [camunda/camunda](https://hub.docker.com/r/camunda/camunda) image.
- [ ] The new component is called `core`.
- [ ] The new component should be a `StatefulSet` .

@aabouzaid could you give progress update here and answer the following questions?
cc. @Zelldon

What was our plan for migrating or keeping the values files for the Helm charts? Will we have a breaking change in how we configure the different components?

We will definitely make breaking changes. We have planned the ones since 8.5, and the new ones will come with the 8.7 unified release.
Regarding the updates, I reached a state today where I can render the chart with the new structure, and I will give it a live test on Monday.

Closing this PR as all tasks are done.
The Connectors component has a known limitation, which the team has discussed. The Connectors app doesn't work with the new setup (It should be fixed in 8.7 Alpha 2.)


Scroll projector to a given line

see #3008 (PR) and #2636 (Issue)

@normanjaeckel I have an idea how to solve this issue: With notify, the client can send a request to the one projector to scroll to query the position. The Projector responds and the client post a request to /set_scroll/. For this we need to pass notifies to projectors, like we do this for users. Can you implement this?

Hm. But which projector should be called if we have more than one?

There is just one projector, where the motion can be projected. If e.g. in two tabs the projector is open, the client gets 2 responses, so we will take the first one coming, because the projector should always give the same answer, because it should display the motion always the same.

So you mean that if we have 1 manager that clicks on "highlight and scroll to line xy", this client sends the message to all of the 3000 projector clients that are open at the moment. Then it receives 3000 answers and just handle the first one for the HTTP POST request 'set_scroll'. Right?

In this extreme situation, yes. The server may send this request just to one projector, because we know that all projectors (with the same id) are equal..

@normanjaeckel What is about this proposal?
https://github.com/FinnStutzenstein/OpenSlides/tree/scrollProjectorToLine

Hm. And what if no projector is active at the moment? The callback remains registered and is triggered if later someone opens a projector and hits the button again ...
I feel that this way is somehow hacky ... but I am not completely against it.

We should merge this into the master. It's hacky, yes, but better then nothing. We can change the implementation, if we find a better solution.

Should be fixed with OpenSlides 3. Just ensure that that projectors do not ask each other about the scroll heigth.

As @normanjaeckel this should be fixed.


crash from compile in android.

Unknown source file : UNEXPECTED TOP-LEVEL EXCEPTION:
Unknown source file : com.android.dex.DexException: Multiple dex files define Landroid/support/v7/appcompat/R$anim;
Unknown source file : 	at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
Unknown source file : 	at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
Unknown source file : 	at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
Unknown source file : 	at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
Unknown source file : 	at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
Unknown source file : 	at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:502)
Unknown source file : 	at com.android.dx.command.dexer.Main.runMonoDex(Main.java:334)
Unknown source file : 	at com.android.dx.command.dexer.Main.run(Main.java:277)
Unknown source file : 	at com.android.dx.command.dexer.Main.main(Main.java:245)
Unknown source file : 	at com.android.dx.command.Main.main(Main.java:106)

what version gradle, node.js, react-native and react?
"npm cache clear", try to remove "node_modules\react-native-svg\android\build" and re-build

I have this problem with:

Gradle 2.4 (via the Gradle wrapper installed by react-native init).
node.js 6.9.1
react 15.4.1
react-native 0.39.0

npm cache clear
rm -rf node_modules android/build android/app/build
npm install
react-native run-android

eventually yields the same error as pasted by the OP.

(In my previous comment I determined my Gradle version by running ./android/gradlew.bat --version, does that answer your question? I don't have Gradle installed globally on my system, I'm only using the Gradle wrapper.)

It seems that the cause of this problem is that react-native init adds the following dependency in android/app/build.gradle:
    compile "com.android.support:appcompat-v7:23.0.1"

react-native-svg also depends on this library and so it gets included in the build twice, which causes the above error.
To be honest I am confused about why this happens. I thought that Gradle was supposed to notice when two modules depend on the same library, and only include that library once. I am not really sufficiently familiar with Gradle to know what the correct solution is.
For now I have worked round the problem by removing the dependency on appcompat-v7 from my project. That seems to get things working, but it doesn't feel like the correct solution.

I found a better workaround.
In android/app/build.gradle, I changed:
    compile project(':react-native-svg')

to read:
    compile(project(':react-native-svg')) {
        exclude group: "com.android.support", module: "appcompat-v7"
    }

Thus excluding the extra copy of appcompat-v7 from the build.
For anyone else needing to work round this problem: you will probably also need to delete the following directories to force gradle to rebuild everything:

android/build
android/app/build
node_modules/react-native-svg/android/build

@djcsdy - Thanks this worked for me as well.

@djcsdy Thanks for answering this.


Is there any tutorials?

Only the examples? Is there any tutorials for beginners?

Hi @littlehegemon thanks for your interest. Once you have a working installation (docker is easiest), there is just a single command (see README) to run it. The output are FreeSurfer conform, so anyone who is familiar with FreeSurfer should be able to immediately understand/process the outputs.
For FastSurfer we have an online tutorial on google collab :
https://github.com/deep-mi/FastSurfer/tree/stable/Tutorial
For FreeSurfer see their webpage for tutorials, YouTube videos and workshops:
https://freesurfer.net
I hope this gets you started.

ups, I did not realise we are in the Lapy Repo . My answer was related to FastSurfer. I am sorry. @kdiers can maybe help you.

Also can you describe more clearly what you want to do? You can compute eigenvalues and eigenvectors from a shape. You can represent the coordinates of the shape as a linear combination of the eigenvectors and filter the shape (or any function on the shape). What you cannot do is:

calculate 2D shapes from a set of eigenvectors
use eigenvectors and eigenvalues alone to reconstruct the shape

Thanks. I understand.
I have surface annotation files. It contains individualized parcellations different for each individual. I want to extract the shape DNA for the each of the parcellations and may be parcellation of the brain as a whole and run a GWAS to find associated genetic locus (real DNA now!). Although brain is 3D, I want to try 2D first. so I need to convert the annotation to vtk format I guess?

@kdiers How do you think?

Hi @littlehegemon, and sorry, at the moment we can only provide the jupyter notebooks as examples and do not have specific tutorials yet.
In general, we would suggest to start the analysis with structures that are distinct anatomical entities - such as the subcortical structures as returned by the 'aseg' segmentation or maybe the whole GM or WM surface. These represent 'natural' shapes, whereas the shape of individual cortical parcellations will to a large extent also be driven by the boundaries imposed by the atlas that was used for the analysis. This may introduce additional, and possibly unwanted, variability, and we have less experience with  these analyses.
Exporting data to VTK format and importing using lapy's TriaIO library is one feasible option, but not the . It is possible to use other formats (see functions in the TriaIO module), and it is also possible to directly construct tria meshes (see Test_TriaMesh.ipynb or TriaMesh.py).

kdiers, Thank you!

Hi @littlehegemon , I will close this now, as it is really not a lapy issue. You need to cut your surface into patches based on your annotations and store those smaller surfaces in a format that lapy can read. Lapy can then compute the Laplace spectra as demonstrated in our examples. You would need to decide what boundary condition to use (Neumann or Dirichlet), as that will affect the eigenvalues a lot. For full hemisphere (without boundary) you don't need to make this decision.
Assuming you speak about FreeSurfer cortical annotations:
For cutting a label from a surface, see FreeSurfer command as we called them in our legacy brain print code: https://github.com/Deep-MI/BrainPrint-legacy/blob/6c7e6cbd04c2ece32aa71bad2b9fc076af84c553/fs_shapeDNA.py#L419
For aparc parcellations convert it to a label first: https://github.com/Deep-MI/BrainPrint-legacy/blob/6c7e6cbd04c2ece32aa71bad2b9fc076af84c553/fs_shapeDNA.py#L493
you can then also merge labels and convert those to surfaces with mris_convert


ScopedEventBus serializable problem

ListenerCollection implements Serializable but not WeakHashMap.
As a consequence ListenerCollection is NOT Serializable because of weakListeners property.

@peholmst Hey Petter, is your side project applicable for BFP? We currently ran into the same issue using your eventbus addon in one of our applications (V8 + addon 2-0-0).

I'll add a pull request, the idea is here but it needs testing


Proper Labels

As currently it's almost ambiguous if something is meant to be for the syntax of thenew language or stuff that we will use to implement it.
Suggest:

synt tag
impl tag

Done


Fix closing modal when pressed ESC while editing environment

While editing an environment variable, if user presses ESC key the modal closes and variable is saved.
Modal shouldn't be closed and variable shouldn't be saved.
I've added noEscape prop as true to the Modal in WorkspaceEnvironmentsEditModal to prevent Modal from catching ESC key press. (_handleKeyDown method was catching ESC key.)
Also removed a TODO comment written 3 years ago by resetting environment variable to default if user hasn't saved while editing (presses ESC key).
Closes #2029

Would this PR disable the ability to close the modal with escape?  I believe the "Manage Environments" modal should save and be closed on escape.  I personally use that feature on a daily basis.  The linked issue is regarding editing the name of an environment and hitting escape to discard the name.

@baleeds Yes, turns out this would disable the close with escape key functionality on modal. I updated PR to set noEscape prop conditionally.

I haven't looked at the code so I could be wrong, but could we stop propagation on the escape key event during field edit mode? That would isolate the behavior of the field from it's context.

Stop event propagation while editing/finish editing was what came to my mind when I first check this issue actually but I couldn't able to stop bubbling.

I think I was able to figure it out: #2039.
My limited understanding is that the KeydownBinder is not respecting React's SyntheticEvents, based on the fact that the keydown event in the modal doesn't have a persist() function.  This would be why stopping propagation in the editable component didn't work, because it would stop the SyntehticEvent, which has no bearing on the actual DOM event (I think!).
In order to fix the issue I used the KeydownBinder to "line up" the events, so both are using raw DOM events (I think!).
That could all be wrong, but it does appear to work 😆


Do not add development dependencies to the nuspec of a target nupkg while paket packing

Motivation:
It was observed on some systems that paket pack adds development dependencies to the nuspec of a target nuget package.
The root cause for this has been documented here. This PR aims to fix issue #3723
Description of fix:
If a nupkg does not exist in the local nuget cache, try to load the nuspec from the DefaultPackagesFolder before returning a Nuspec.All

thanks a lot for taking care of this

You are welcome


Python: set a 15s read timeout.

Set the timeout to 10s, and fixed the type warning when instantiating the client.

Redoing #374, I accidentally merged it into an existing branch and dropped everything. :|


Create closing end when writing do

I'm currently playing a bit around with this plugin and was wondering how difficult it would be to implement auto-adding of end once you write do.
I come from emacs where this stuff happens automagically so I'm probably a bit spoiled

I'd like this as well!

+1


DataCloneError on Windows 10 Pro version 1607

I'm running into a DataCloneError exception when opening a PDF document on Windows 10 version 1607 (aka "Anniversary Update") with IE Edge (38.14393). This error does not occur with Windows 10 version 1709. This error occurs with any PDF document, including the PDF.js sample document (download, then try to view it with the demo's "open" feature.)
The obvious answer here is to upgrade to Windows 1709 or later, but I have a situation where that's not possible.
Attach (recommended) or Link to PDF file here: See PDF.js demo page (download demo PDF document, then open it).
Configuration:

Web browser and its version: IE Edge 38.14393
Operating system and its version: Windows 10 Pro version 1607
PDF.js version: Latest (demo site)
Is a browser extension: No

Steps to reproduce the problem:

Visit PDF.js demo website using Windows 1607/Edge 38.x
Note the sample document loads without errors
Download the sample document to local filesystem
Open the sample document from the local filesystem
Note the document never appears
Open debugging tools and enable exception breakpoints
Reload Demo and attempt to open document
Eventually you'll hit a DataCloneError exception in PDF.js

What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): https://mozilla.github.io/pdf.js/web/viewer.html

A bit more investigation into this reveals the exception is reported on line 1309 of util.js, however this looks like a symptom of reporting a preceding TypeMismatchError that may be thrown while handling the ReaderHeadersReady event in api.js.

FWIW it's my best guess this is related to the ReadableStreams polyfill, but the state of Edge debugging tools makes it impossible for me to narrow down the exact cause. The code that led me to this issue was passing PDF data into PDF.js as a data URI which triggers the TypeMismatch exception. Passing the PDF data to getDocument as Base64-encoded string (simply by stripping off the leading "data:...;base64,") is enough for me to work around the issue.

I'm running into a DataCloneError exception when opening a PDF document on Windows 10 version 1607 (aka "Anniversary Update") with IE Edge (38.14393). This error does not occur with Windows 10 version 1709.

Given that the bug has apparently been fixed upstream, in newer versions of Edge, the likelihood of PDF.js maintainers wanting to add a version specific browser compatibility hack might not be that great unfortunately. (Especially when it's not entirely easy to pin-point exactly where the issue occurs.)

FWIW it's my best guess this is related to the ReadableStreams polyfill, but the state of Edge debugging tools makes it impossible for me to narrow down the exact cause.

If it's an issue with the ReadableStream polyfill itself, then that would need to be reported upstream in https://github.com/whatwg/streams/tree/master/reference-implementation. However, I do appreciate  that doing is difficult without being able to come up with a reduced test-case.
For reference, please also note that based on reports of completely broken ReadableStream support in older versions of Edge, PR #8744 added better feature detection for native ReadableStream support.

I'm going to close this issue because it doesn't look like there is anything we can do about this on the PDF.js side based on the above.


chore: bdd-spring-1574287442 to 0.0.1

chore: Promote bdd-spring-1574287442 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Can not be published as Nuget package

When it is published to Nuget package it gives the following error and publish fails

Pushing MongoDB.Driver.Extensions.Ledger.1.0.0.nupkg to 'https://www.nuget.org/api/v2/package'...
PUT https://www.nuget.org/api/v2/package/
Conflict https://www.nuget.org/api/v2/package/ 515ms
To skip already published packages, use the option --skip-duplicate
error: Response status code does not indicate success: 409 (This package ID has been reserved. Please request access to upload to this reserved namespace from the owner of the reserved prefix, or re-upload the package with a different ID. Go to https://docs.microsoft.com/nuget/reference/id-prefix-reservation learn more about Package ID prefix reservation.).

There are other already published projects with similar naming. Need to find the exact reason or need to find another naming for this extension.

Following PR #3 is created within Copilot Workspace

Unverified packages with MongoDB.* might be uploaded before reservation of the prefix. Once the prefix is reserved for an owner, others will not be able to upload a package with the same prefix ID.

Received some additional info from Nuget support...Package name is revised and published


unity win phone 10 deploy: ios notification stuff error in il2cpp deploy

So i'd like to deploy a unity app to win phone 10 using il2cpp as backend since that is supposed to allow using more of the mono C# api than when deploying with mono backend but when trying that then on deploy attempt it throws an error stating:
System.Exception: Error processing method: 'System.Void Parse.PlatformHooks/<>c__DisplayClass28::b__26()' in assembly: 'Parse.Unity.dll' ---> Mono.Cecil.ResolutionException: Failed to resolve System.Byte[] UnityEngine.iOS.NotificationServices::get_deviceToken()
so it looks like when doing win phone 10 deploy wih il2cpp setting then in the Parse Unity dll it goes into iOS specific code.

We don't technically support windows phone via unity, as it will fail due to tasks existing already as well. We're in the process of modularizing the SDK to allow support of windows platforms, but there's still a good amount of work to be done until we can support this.

Cool regarding modularizing the sdk, regarding technically not supporting windows phone, well, i thought in il2cpp deploy more of the mono C# api is supported for win 10 universal deploy than with C# backend setting hence why i tried that as work around. The error i got there to me sounds like it would maybe just need a platform dependent compiler flag like #if UNITY_IPHONE around that code block there since right now it seems to go into iOS specific code there for notifications when deploying to win 10 universal with il2cpp setting

@UgurIster FWIW, on master you should be able to use Parse without Push, if you have access to Visual Studio (building the SDK from Xamarin is currently not supported).

Closing as we don't plan on necessarily supporting this.


when will kubernetes.io be updated for 1.30，I want to cjheck feature-gate updated？

This is a Feature Request

What would you like to be added

Why is this needed
when will kubernetes.io be updated for 1.30，I want to cjheck feature-gate updated？
Comments

/language en

Hi @13567436138, as it seems like a support request you can post your question on the Kubernetes Slack or the Discuss Kubernetes forum.
/kind support

You can also visit this page for more information.

when will kubernetes.io be updated for 1.30

@13567436138 The website has already been updated for the v1.30 release, this was done on the day of release. For details on the features gates, please check out Feature Gate page (click here) and for the removed feature gates, visit here. You can find the v1.30 release blog here.

@13567436138 : Will be closing this issue since the English site has been updated. For other languages, please raise an issue with the relevant label applied/or reach out to the relevant team on Slack.
/close


Edit Users , profile pic dose not change.

Describe your problem
while navigating to Edit Users , the user has an image, but when to chose another one, gets previewed but after click on save, the old image shows up.
Bludit version
3.4.0

It was cache issue.

I added a version controler to prevent the cache.


fix: Removes explicit delay on form evaluations

Description

Removes local variables used in the form evaluations logic
Removes explicit delay used here.

Fixes #14965
Type of change

Bug fix (non-breaking change which fixes an issue)
Perf improvement

How Has This Been Tested?

Manual

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/ok-to-test sha=fe53829


Fix link to Homebrew installation script (rebased onto dev_5_0)

This is the same as gh-1091 but rebased onto dev_5_0.

With the migration of the script to the omero-install repository, the
link on the documentation page needs to be updated

--rebased-from #1091

See https://github.com/ome/omero-install/pull/11

This also looks fine.  Please merge.

Actually, the docs merge build has broken link for me: https://github.com/snoopycrimecop/openmicroscopy/blob/merge/dev_5_0/latest/https://github.com/ome/omero-install/tree/master/homebrew  (in http://www.openmicroscopy.org/site/support/omero5-staging/sysadmins/unix/server-install-homebrew.html)

My bad. Pushed a fix.

Thanks, that's much better.

Looks good to merge.
Note that this page is quite outdated and could do some work for 5.1:

OSX/Xcode section describes the old CI setup which was replaced a while back
"Java..comes as standard on OS X" has not been true since 10.6 and could be removed.
System vs. homebrew python.  Rather than detailing all the various combinations which are possible, maybe just recommend use of homebrew python and leave it at that?

Most of this is duplication what's already on the main unix installation page, which also covers installing the prerequisites with homebrew.  Could this page be cut down to just how to do the install and delegate the rest of the detail to the main page?

Great suggestion @rleigh-dundee - I'll stick a card on the Docs board for that, if you or Seb want to volunteer, please go ahead :)


Remove required branch from branch protection rules and use default

This makes it so that branch protection rules no longer have a
required parameter. Instead, this is replaced by a default value of
""
Signed-off-by: Juan Antonio Osorio<EMAIL_ADDRESS>

@JAORMX - Let's merge it once we confirm the CI job passes successfully, wdyt? 👍