std::bad_alloc error when running SYCL code

Hello,
I'm trying to run the miniFE-sycl code compiled using hipSYCL and it throws an error when apparently device code starts. Below is the stdout.
[ri-wshilpage@login-01 src]$ ./miniFE.x
MiniFE Mini-App, OpenMP Peer Implementation
Creating OpenMP Thread Pool...
Counted: 16 threads.
 Any lead to what could be wrong? I built LLVM from source (version 12.0.1) to use when building hipSYCL.

Without further information, I can only guess that it runs out of memory.
Different SYCL implementations may have different allocation and deallocation patterns (i.e. may choose to allocate or free memory at different places), especially when an application uses buffers instead of USM pointers. Because of this, there may be some variance of peak memory consumption. I would recommend to run the application while monitoring memory consumption. Is it already close to max when using DPC++?

FYI this run configuration (no problem size expansion flags) does not use a lot of memory. It should probably be within 10-100 MB range. So I doubt the issue really is about memory limit or allocation. Could there be any shared library version issues? I used GCC 8 or 9 for building LLVM as I can recall and the standard libs (/usr/lib64) in this system are not very updated. I earlier compiled this same application using hipSYCL in a different machine and it didn't give any runtime errors. So I'm not very convinced this is a memory size or allocation error.
Check the valgrind --track-origins=yes ./miniFE.x output below.
==4051349== Memcheck, a memory error detector
==4051349== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==4051349== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==4051349== Command: ./miniFE.x
==4051349==
MiniFE Mini-App, OpenMP Peer Implementation
Creating OpenMP Thread Pool...
==4051349== Syscall param sched_setaffinity(mask) points to unaddressable byte(s)
==4051349==    at 0x5F246ED: syscall (in /usr/lib64/libc-2.28.so)
==4051349==    by 0x410EBE5: __kmp_affinity_determine_capable (in /lustre/home/ri-wshilpage/tools/LLVM/llvm-project/build/lib/libomp.so)
==4051349==    by 0x40D41D1: __kmp_env_initialize(char const*) (in /lustre/home/ri-wshilpage/tools/LLVM/llvm-project/build/lib/libomp.so)
==4051349==    by 0x40BD5AB: __kmp_do_serial_initialize() (in /lustre/home/ri-wshilpage/tools/LLVM/llvm-project/build/lib/libomp.so)
==4051349==    by 0x40BDA4C: __kmp_get_global_thread_id_reg (in /lustre/home/ri-wshilpage/tools/LLVM/llvm-project/build/lib/libomp.so)
==4051349==    by 0x40AEC1F: __kmpc_fork_call (in /lustre/home/ri-wshilpage/tools/LLVM/llvm-project/build/lib/libomp.so)
==4051349==    by 0x409A31: main (in /lustre/home/ri-wshilpage/apps/HeCBench/miniFE-sycl/src/miniFE.x)
==4051349==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==4051349==
Counted: 1 threads.
Running MiniFE Mini-App...
      creating/filling mesh...0.022995s, total time: 0.023175
generating matrix structure...0.317592s, total time: 0.340767
         assembling FE data...0.198965s, total time: 0.539732
      imposing Dirichlet BC...0.0898499s, total time: 0.629582
      imposing Dirichlet BC...0.085681s, total time: 0.715263
making matrix indices local...0.000210047s, total time: 0.715473
Starting CG solver ...
==4051349== Conditional jump or move depends on uninitialised value(s)
==4051349==    at 0x404B0E8: std::vector<std::filesystem::__cxx11::path::_Cmpt, std::allocator<std::filesystem::__cxx11::path::_Cmpt> >::vector(std::vector<std::filesystem::__cxx11::path::_Cmpt, std::allocator<std::filesystem::__cxx11::path::_Cmpt> > const&) (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x404A450: std::filesystem::__cxx11::path::path(std::filesystem::__cxx11::path const&) (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x404937E: (anonymous namespace)::get_plugin_search_paths[abi:cxx11]() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x4047F30: hipsycl::rt::backend_loader::query_backends() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x40464F2: hipsycl::rt::backend_manager::backend_manager() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x40447FF: hipsycl::rt::runtime::runtime() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x4040B4E: hipsycl::rt::application::get_runtime_pointer() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x4040A55: hipsycl::rt::runtime_keep_alive_token::runtime_keep_alive_token() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x42054C: hipsycl::sycl::device::get_devices(hipsycl::sycl::info::device_type) (in /lustre/home/ri-wshilpage/apps/HeCBench/miniFE-sycl/src/miniFE.x)
==4051349==    by 0x41FAF7: std::vector<hipsycl::sycl::device, std::allocator<hipsycl::sycl::device> > hipsycl::sycl::detail::select_devices<hipsycl::sycl::cpu_selector>(hipsycl::sycl::cpu_selector const&) (in /lustre/home/ri-wshilpage/apps/HeCBench/miniFE-sycl/src/miniFE.x)
==4051349==    by 0x41C7AF: hipsycl::sycl::queue::queue<hipsycl::sycl::cpu_selector, 0>(hipsycl::sycl::cpu_selector const&, hipsycl::sycl::property_list const&) (in /lustre/home/ri-wshilpage/apps/HeCBench/miniFE-sycl/src/miniFE.x)
==4051349==    by 0x414C40: void miniFE::cg_solve<miniFE::CSRMatrix<double, int, int>, miniFE::Vector<double, int, int>, miniFE::matvec_std<miniFE::CSRMatrix<double, int, int>, miniFE::Vector<double, int, int> > >(miniFE::CSRMatrix<double, int, int>&, miniFE::Vector<double, int, int> const&, miniFE::Vector<double, int, int>&, miniFE::matvec_std<miniFE::CSRMatrix<double, int, int>, miniFE::Vector<double, int, int> >, miniFE::CSRMatrix<double, int, int>::LocalOrdinalType, miniFE::TypeTraits<miniFE::CSRMatrix<double, int, int>::ScalarType>::magnitude_type&, miniFE::CSRMatrix<double, int, int>::LocalOrdinalType&, miniFE::TypeTraits<miniFE::CSRMatrix<double, int, int>::ScalarType>::magnitude_type&, double*) (in /lustre/home/ri-wshilpage/apps/HeCBench/miniFE-sycl/src/miniFE.x)
==4051349==  Uninitialised value was created by a stack allocation
==4051349==    at 0x4049217: (anonymous namespace)::get_plugin_search_paths[abi:cxx11]() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==
==4051349== Conditional jump or move depends on uninitialised value(s)
==4051349==    at 0x404B0F7: std::vector<std::filesystem::__cxx11::path::_Cmpt, std::allocator<std::filesystem::__cxx11::path::_Cmpt> >::vector(std::vector<std::filesystem::__cxx11::path::_Cmpt, std::allocator<std::filesystem::__cxx11::path::_Cmpt> > const&) (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x404A450: std::filesystem::__cxx11::path::path(std::filesystem::__cxx11::path const&) (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x404937E: (anonymous namespace)::get_plugin_search_paths[abi:cxx11]() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x4047F30: hipsycl::rt::backend_loader::query_backends() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x40464F2: hipsycl::rt::backend_manager::backend_manager() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x40447FF: hipsycl::rt::runtime::runtime() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x4040B4E: hipsycl::rt::application::get_runtime_pointer() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x4040A55: hipsycl::rt::runtime_keep_alive_token::runtime_keep_alive_token() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x42054C: hipsycl::sycl::device::get_devices(hipsycl::sycl::info::device_type) (in /lustre/home/ri-wshilpage/apps/HeCBench/miniFE-sycl/src/miniFE.x)
==4051349==    by 0x41FAF7: std::vector<hipsycl::sycl::device, std::allocator<hipsycl::sycl::device> > hipsycl::sycl::detail::select_devices<hipsycl::sycl::cpu_selector>(hipsycl::sycl::cpu_selector const&) (in /lustre/home/ri-wshilpage/apps/HeCBench/miniFE-sycl/src/miniFE.x)
==4051349==    by 0x41C7AF: hipsycl::sycl::queue::queue<hipsycl::sycl::cpu_selector, 0>(hipsycl::sycl::cpu_selector const&, hipsycl::sycl::property_list const&) (in /lustre/home/ri-wshilpage/apps/HeCBench/miniFE-sycl/src/miniFE.x)
==4051349==    by 0x414C40: void miniFE::cg_solve<miniFE::CSRMatrix<double, int, int>, miniFE::Vector<double, int, int>, miniFE::matvec_std<miniFE::CSRMatrix<double, int, int>, miniFE::Vector<double, int, int> > >(miniFE::CSRMatrix<double, int, int>&, miniFE::Vector<double, int, int> const&, miniFE::Vector<double, int, int>&, miniFE::matvec_std<miniFE::CSRMatrix<double, int, int>, miniFE::Vector<double, int, int> >, miniFE::CSRMatrix<double, int, int>::LocalOrdinalType, miniFE::TypeTraits<miniFE::CSRMatrix<double, int, int>::ScalarType>::magnitude_type&, miniFE::CSRMatrix<double, int, int>::LocalOrdinalType&, miniFE::TypeTraits<miniFE::CSRMatrix<double, int, int>::ScalarType>::magnitude_type&, double*) (in /lustre/home/ri-wshilpage/apps/HeCBench/miniFE-sycl/src/miniFE.x)
==4051349==  Uninitialised value was created by a stack allocation
==4051349==    at 0x4049217: (anonymous namespace)::get_plugin_search_paths[abi:cxx11]() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
==4051349==
==4051349== Process terminating with default action of signal 6 (SIGABRT): dumping core
==4051349==    at 0x5E6570F: raise (in /usr/lib64/libc-2.28.so)
==4051349==    by 0x5E4FB24: abort (in /usr/lib64/libc-2.28.so)
==4051349==    by 0x533D649: __gnu_cxx::__verbose_terminate_handler() [clone .cold] (vterminate.cc:95)
==4051349==    by 0x5349305: __cxxabiv1::__terminate(void (*)()) (eh_terminate.cc:48)
==4051349==    by 0x5349370: std::terminate() (eh_terminate.cc:58)
==4051349==    by 0x5349604: __cxa_throw (eh_throw.cc:95)
==4051349==    by 0x534013A: std::__throw_bad_alloc() (functexcept.cc:54)
==4051349==    by 0x404B135: std::vector<std::filesystem::__cxx11::path::_Cmpt, std::allocator<std::filesystem::__cxx11::path::_Cmpt> >::vector(std::vector<std::filesystem::__cxx11::path::_Cmpt, std::allocator<std::filesystem::__cxx11::path::_Cmpt> > const&) (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x404A450: std::filesystem::__cxx11::path::path(std::filesystem::__cxx11::path const&) (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x404937E: (anonymous namespace)::get_plugin_search_paths[abi:cxx11]() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x4047F30: hipsycl::rt::backend_loader::query_backends() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==    by 0x40464F2: hipsycl::rt::backend_manager::backend_manager() (in /lustre/home/ri-wshilpage/sycl-compilers/hipSYCL/build-cuda/install/lib/libhipSYCL-rt.so)
==4051349==
==4051349== HEAP SUMMARY:
==4051349==     in use at exit: 1,029,720 bytes in 1,284 blocks
==4051349==   total heap usage: 1,717 allocs, 433 frees, 2,259,998 bytes allocated
==4051349==
==4051349== LEAK SUMMARY:
==4051349==    definitely lost: 0 bytes in 0 blocks
==4051349==    indirectly lost: 0 bytes in 0 blocks
==4051349==      possibly lost: 490,504 bytes in 492 blocks
==4051349==    still reachable: 539,216 bytes in 792 blocks
==4051349==         suppressed: 0 bytes in 0 blocks
==4051349== Rerun with --leak-check=full to see details of leaked memory
==4051349==
==4051349== For lists of detected and suppressed errors, rerun with: -s
==4051349== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
Aborted (core dumped)

Right, in this case memory consumption is unlikely. The error seems to occur in the std::filesystem::path copy constructor. std::filesystem was added fairly late to libstdc++, maybe you still have a very early version that contains bugs or so...
Can you maybe look with a debugger what this path constructor wants to do that causes std::bad_alloc?

Yes it was exactly an issue with the std::filesystem symbols in libstdc++. I had to manually link the stdc++fs when building hipSYCL. System GCC version in this machine is GCC 8 so as mentioned here version incompatibility happens.


Ongoing progress on migrating to sbt 1.0

This somewhat compiles and seems to work but it doesn't cross-build with 0.13.x any more. Also it lost the asciiGraph feature and reporting results in the presence of resolution errors.

not sure, but this might be helpful: https://github.com/dwijnand/sbt-compat


Refreshing home screen dropdown on locale change

Fix for the bug 159047, in which the home screen dropdown would not be refreshed automatically when settings changed.

Not seeing where this function is coming from?


Correct the call signature for createQuery

The createQuery function is documented incorrectly as accepting a query object directly, where as it actually only accepts a params object (i.e. object of the shape { query: {...} }.

thanks for the update!  The old behavior is broken since the upgrade of feathers-knex package.

Dangit, I totally missed that this would've been a breaking change and we didn't have tests to cover this.

nvm bro, thanks for bringing this amazing stuff to the world!


0.3.2

Bug fixes and enhancements:

fix excessive CPU memory load from logging
remove unnecessary dependencies between featurizing & scoring methods
fix abstraction violation in projectors
bring back an example of iterative (as opposed to functional) gradient computer
add a ridge regularization option for the computation of the $(X^\top X)^{-1}$ term in the TRAK estimator.

Co-authors of commits: @TheaperDeng @JD-ETH  @heale04


Add fluid simulation example

Finally, fluid simulation example for magnum :heart_eyes:
Please make a WebGL example of this. I don't know how to do it now :)
Let me know if there's anything needs to be changed.

Yay, Xmas come early this year! I need to try this out immediately :)

The ThreadPool stuff is super interesting. :O Thanks for sharing this!

Adding a gif, for easy sharing. :)

https://vimeo.com/368947792

I just pushed new changes:
[X] Add back tbb code.
[X] Limit 60FPS rendering but maximize computation: run a number of simulation steps (which is dynamically computed) per frame.

Thank you, this is great :+1:
Sorry for the lack of action on my side, got a priority thing to work on right now. I'll try to get this merged later this week.

Merged as 4fb94bd7b8e9f97dce9e94b3bc4100dbf12cd45c and ba5000c32329e1c758d3d405f9ffa90f90fe25d1 -- you did some great work, thanks a lot :+1: I didn't look into the WebGL port yet, hopefully soon :)
Docs for the example are at https://doc.magnum.graphics/magnum/examples-fluidsimulation3d.html -- I was not sure what exactly to put there, so if you have some further information, let me know.


Update AEP SDKs to include privacy manifest

At WWDC23 Apple announced that apps and SDKs that make use of certain "required reason" APIs will need to provide a privacy manifest.
It looks like the AEP SDKs will need to do this because, amongst others, they make use of UserDefaults, which is now considered a "required reason" API.
Is this update on the roadmap for the team? I appreciate that enforcement won't happen until Spring 2024 but I wanted to make contact so that we can plan our own app releases to take this into account.
For more info, see:

Describing data use in privacy manifests | Apple Developer Documentation
Describing use of required reason API | Apple Developer Documentation
Get started with privacy manifests - WWDC23 - Videos - Apple Developer

Thanks!

Any update on this please? Deadline is approaching.

+1

We are working on 5.x versions of all our iOS SDKs to address Privacy Manifest. I will update the release date soon.

@praveek When you are releasing the 5.x versions as time is approaching.

We are working on releasing the 5.x SDKs in the latter half of March.

Hey everyone. Here is our public doc on iOS 17 and Privacy Manifests. Thanks for your patience!

The 5.x SDKs have been released. Refer our documentation for more information on this release.


Error: No available formula or cask with the name "azure-cli". - I couldn't install Azure Cli on my MAC , brew command always give same error

Resource Provider

Description of Feature or Work Requested

Minimum API Version Required

Swagger Link

Target Date

Ramkumars-MacBook-Air:casks meghnaram$ brew install azure-cli
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
Error: No available formula or cask with the name "azure-cli".
It was migrated from homebrew/cask to homebrew/core.
Ramkumars-MacBook-Air:casks meghnaram$

Ramkumars-MacBook-Air:casks meghnaram$ brew install --cask azure-cli
Error: Cask 'azure-cli' is unavailable: No Cask with this name exists.
Ramkumars-MacBook-Air:casks meghnaram$

hi @fengzhou-msft , could you pls have a look?

@ramwintel please run brew update first.

Ramkumars-MacBook-Air:casks meghnaram$ brew update && brew install azure-cli
Already up-to-date.
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
Error: No available formula or cask with the name "azure-cli".
It was migrated from homebrew/cask to homebrew/core.
Ramkumars-MacBook-Air:casks meghnaram$

Ramkumars-MacBook-Air:casks meghnaram$ brew update && brew install azure-cli
Already up-to-date.
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
Error: No available formula or cask with the name "azure-cli".
It was migrated from homebrew/cask to homebrew/core.
Ramkumars-MacBook-Air:casks meghnaram$

Ramkumars-MacBook-Air:casks meghnaram$ brew update && brew install kubectl
Already up-to-date.
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
Error: No available formula or cask with the name "kubectl".
==> Searching for a previously deleted formula (in the last month)...
Error: No previously deleted formula found.
==> Searching taps on GitHub...
Error: No formulae found in taps.
Ramkumars-MacBook-Air:casks meghnaram$

I tried all options from GOOGLE :) but no luck, Please help me resolve this issue. Thanks

I even tried upgrade,
Ramkumars-MacBook-Air:casks meghnaram$ brew upgrade
Ramkumars-MacBook-Air:casks meghnaram$ brew install --cask azure-cli
Error: Cask 'azure-cli' is unavailable: No Cask with this name exists.
Ramkumars-MacBook-Air:casks meghnaram$ brew install azure-cli
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
Error: No available formula or cask with the name "azure-cli".
It was migrated from homebrew/cask to homebrew/core.
Ramkumars-MacBook-Air:casks meghnaram$

Ramkumars-MacBook-Air:casks meghnaram$ brew config
HOMEBREW_VERSION: 3.1.3-54-ge651c86
ORIGIN: https://github.com/Homebrew/brew
HEAD: e651c86b45b0c3e22446057dcfb6d501e6c601bb
Last commit: 16 minutes ago
Core tap ORIGIN: https://github.com/Homebrew/brew
Core tap HEAD: e651c86b45b0c3e22446057dcfb6d501e6c601bb
Core tap last commit: 16 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 4
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: quad-core 64-bit broadwell
Clang: 12.0 build 1200
Git: 2.24.3 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 10.15.7-x86_64
CLT: <IP_ADDRESS>.1.1610135815
Xcode: N/A
Ramkumars-MacBook-Air:casks meghnaram$

Ramkumars-MacBook-Air:casks meghnaram$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: Suspicious https://github.com/Homebrew/homebrew-core git origin remote found.
The current git origin is:
https://github.com/Homebrew/brew
With a non-standard origin, Homebrew won't update properly.
You can solve this by setting the origin remote:
git -C "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core" remote set-url origin https://github.com/Homebrew/homebrew-core
Ramkumars-MacBook-Air:casks meghnaram$

I don't know what else command I can try :), I don't wants to wait too long.. I would like to fix it soon. Thanks


⚠ ClamAV has degraded performance

In 8a7a2e0, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 118 ms

Resolved: ClamAV performance has improved in 829943f after 6 minutes.


Syntax mismatch between animate help text and parameter order

The help text for lan:animate states:
Target particular devices::

    lifx lan:animate balls match:label=wall

When I try to run an almost identical command, I get an error:
$ lifx lan:animate balls match:cap=matrix
...
Something went wrong! -- PhotonsAppError
	"Tried to treat a string as a serial but it wasn't valid hex"	error="Error: Odd-length string"	wanted=balls

If I swap the order of the matcher and animation name, I get the error from issue #51 .

I need to make reference on that task more lenient it seems
The new code it uses has more thorough validation than before.
And this task is special and is meant to let you swap artifact and
reference because it's less annoying for this task
On Mon, 5 Apr 2021, 11:09 pm Avi Miller, @.***> wrote:

The help text for lan:animate states:
Target particular devices::
lifx lan:animate balls match:label=wall

When I try to run an almost identical command, I get an error:
$ lifx lan:animate balls match:cap=matrix
...
Something went wrong! -- PhotonsAppError
"Tried to treat a string as a serial but it wasn't valid hex"	error="Error: Odd-length string"	wanted=balls
If I swap the order of the matcher and animation name, I get the error
from issue #51 https://github.com/delfick/photons/issues/51 .
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/delfick/photons/issues/52, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2V5IUXB4YYXUWDDPXAK3THGR6PANCNFSM42MZBFAA
.


Tester feedback: bug

Question ID
eviction_moratorium_intro_screen

Steps to reproduce
1

2

3

Expected behavior
456

What happened instead
A

Other information
B

Variable being sought
eviction_moratorium_intro_screen

Package version
0.0.24

Maturity target
Level 2 - this needs to be fixed to meet expectations of a basic intake

Tester contact info
@nonprofittechy

Test bug

Test bug


Add Wiener first passage time distribution

Add wiener first passage time density. See #469.

This issue was moved to stan-dev/math#35

This was fixed with stan-dev/stan#1218.


CustomElementRegistry Render 2 times

CustomElementRegistry register "ssrs-reportviewer" 2 times and cost error of duplicate registered element during refresh the report page.
File : ngx-ssrs-reportviewer.js : 137

This should be fixed with latest version.


Replace substring with slice

We are counting bytes so this will shave off 8 of them :smile:
Difference between substring and slice is irrelevant here because 0 <= cursor < index

its actually slower for whatever reason. the speed is more important than the bytes saved in this case imo


can't write html to php file?

When is pacify a html file its fine but in a php file it creates
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 00

gulp.task("createfavicons", function () {
    return gulp.src("src/img/ampersand-01.png").pipe(favicons({
        appName: "My App",
        appDescription: "This is my application",
        developerName: "Hayden Bleasel",
        developerURL: "http://penoyreprasad.com",
        background: "#fff",
        path: "favicons/",
        url: "dist/img/",
        display: "standalone",
        orientation: "portrait",
        start_url: "favicons/",
        version: 1.0,
        logging: true,
        online: false,
        html: "header-icons.php",
        pipeHTML: true,
        replace: true
    }))
    .on("error", gutil.log)
    .pipe(gulp.dest("./"));
});

thanks!

Yeah, look like same as my report here #138
Can you specify which versions you use to help developers ?

Close duplicate https://github.com/evilebottnawi/favicons/issues/138


openTun - C version of code to monitor mote

This C code listens to the stats coming from an openMote and displays the results in a friendly format.
This code will develop slowly into code to decode IP packets to pass upwards.

The PR is duplicated. So closed.


SVG Stack link is a 404

SVG Stack link in the readme points to this
http://simurai.com/blog/2012/04/02/svg-stacks/
and it is a 404.

Thanks for reporting @NKjoep. However, this is a duplicate of #69 and has already been fixed in the master branch. I'll hopefully be able to push out a new release soon.

oh cool! :) I tried to use the search but I couldn't find it! 👍

Yeah, it's a little hard to find as it was reported in another repo (the Grunt wrapper). But fortunately my memories jumped in. ;)


Deep Linking Support - iOS

I am curious to know if there are any plans to add support for deep linking on iOS soon.
Note:
As I am in the process of developing my first application using Compose Multiplatform, having deep linking support available ASAP is essential. This feature is particularly important during the initial stages of development to ensure a smooth and efficient workflow.

It's not available in first alphas, but it's in our TODO list

We use Decompose instead of the Navigation lib, but the deeplinking due to the way it works is a little bit different on each platform so you would need to do some of your own lift regardless of if you use jetpack or decompose etc

It's not available in first alphas on adopted Jetpack Navigation, but it's in our TODO list.
If the question is not about navigation library but just about "Compose Multiplatform" - platform APIs are available via KMP and Compose UI framework doesn't prevent usage of it. Also, there are a few 3rd party libraries to simplify the process

@MatkovIvan
Appreciate your reply, I got your point 🙋♂.

We use Decompose instead of the Navigation lib, but the deeplinking due to the way it works is a little bit different on each platform so you would need to do some of your own lift regardless of if you use jetpack or decompose etc

@chrisjenx
Thank you for your interaction, you are right.
In fact, I have looked into Decompose and was impressed by its features, documentation, and developer engagement. However, I wonder if the support will remain at the same level when compared to the official libraries from JetBrains or Google.

I think the same way people use a bunch of different libraries instead of Jetpack offerings (some people don't like the graph definition with Jetpack Nav) so at least for the near term I'm not worried.
It also move's much quicker and it's easy for ourselves to form/modify over the jetpack lib which is at the whim of Google and CMP team pulling upstream changes.
Also it will probably see better integration with iOS/Web/Desktop, which I would take a guess is more lift than Google/Jetbrains could probably offer right now with the other huge backlog of things they need to add to CMP.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Ring working only once after adapter installation

System setup:
iobroker in buanet Docker container
Adapter Version: 1.0.6
npm: 6.13.4
nodejs: 10.18.0
After installation I can ring the doorbell once, after that, no more changes within the states.
Snapshot request is still working and updating pictures.
More information needed?
Reccomondation:
Possibility to auto delete old snapshot files.
Notice:
If users installing ring on buanets Docker image, you also need to install ffmpeg

in the moment I will Not fix anything. The API does not work anymore

This issue on ring-client-api project helped me.
After I set the cameraDingsPollingSeconds from 1 to 2 in the file ringapiclient.js line 129 and 136, I receive the newDing events again. Maybe you can push this workaround until the problem is analyzed and fixed in ring-client-api project.

I have analyzed this issue. The ring-api-client is always initialized when the function ringer() in ring.js is called. This causes multiple instances of the client and somehow the right subscription is not triggered.
I have deleted line 595 in file ring.js and it seems to work.

The ring-api-client is only called in function ring() if no ring instance exist.
The problem shall be fixed now with the new ring-api-client version.
Please download the now ring adapter from GitHub and check. If it does not work, please reopen the issue


INCOMPLETE_CHUNKED_ENCODING when using nginx-proxy

I have a container that has an aspnet5-rc1 application inside, listening on port 5000.  If I make a request to that port, the response is 200 and quick.
If I make a request via nginx-proxy to that application, then the response data comes back immediately, but does not terminate and rather about a minute later the response fails with; (in chrome) ERR_INCOMPLETE_CHUNKED_ENCODING

Error does not occur when using aspnet-beta7.  Still seems to be an issue with nginx-proxy however, considering aspnet-rc1 does not display this behaviour when making requests directly to the port without nginx-proxy.  Headers for both aspnet-beta7 and aspnet-rc1 are the same;
HTTP/1.1 200 OK
Server: nginx/1.9.6
Date: Sun, 08 Nov 2015 04:38:28 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Frame-Options: SAMEORIGIN

Looks specific to KestrelHttpServer.


Adding an empty meta field in Admin / Site unsets earlier metadata.

I have been trying to add an empty "generator" meta field to Admin / Site (as suggested), but this empties meta fields that are listed prior too.
I start with something basic like

After saving the page, I empty the field for generator and save the page which results in

That is indeed a weird bug, and I can confirm that it's also present for me (Grav 1.6.11, Admin 1.9.7).
The workaround for disabling the generator meta tag is to set generator: 0 - the zero is interpreted as false.

@mahagr Still in version 1.7.0-rc.8!


Fine-tuning

Hellor,
Thank you for sharing your code.
Have you tried to fine-tune the bert-like model during the fine-tuning?
If I understood well you don't use the tags when using the bert embeddings, did you try using both?
Also there is 2 minor changes for the char_lstm.py file to work :
Line 42 replace n_embed by n_word_embed and return None with embed to avoid changing the training code.
Thank you in advance.

hi ArijRB.
What exactly do you mean by "return None with embed to avoid changing the training code."?

I run into the same issue while training.
I did fix at line 42 of char_lstm.py the variable from n_embed to n_word_embed, but I didn't realized what "return None with embed" mean. Anyone can elaborate a little more about it?
Thanks in advance.


upgrade datafusion & arrow

upgrade datafusion to 42 and arrow to 53.
the .taplo.toml file is copied from dadafusion.
BTW, I think we don't need datafusion and arrow dependencies, just need subcrates like dadafusion-expr and arrow-array. If you agree, I would do this.

@xhwhis确实，这将有助于减少依赖项数量并减少编译时间。您可以继续这样做。

@hozan23 done

Hey @xhwhis
I am sorry but I believe this is not the ideal way to manage dependencies in rust. I thought you intended to use Cargo features to minimize the dependencies. Your current approach, where you're importing the subcrates, won't make a difference since you're also importing the main crate, datafusion, It will also make it much harder to manage dependencies. It's best to reduce dependencies using Cargo features for the main crate. You can find the available features for datafusion here, which allows you to include only the necessary features (crates) for each crate in our repository.

merge PR #59, close it.


stop building command line with string concat

this would be more secure, suggested by codeql

Ref:
https://wiki.sei.cmu.edu/confluence/display/java/IDS07-J.+Sanitize+untrusted+data+passed+to+the+Runtime.exec()+method
@wangmingliang-ms @Flanker32 take a look when you have time.


Asset locking

What problem does this solve or what need does it fill?
Today, there is no way to access an asset from a thread/async block. The best you can do is clone the asset entirely, or make your asset a wrapper around an Arc with all the data. This is especially painful for #11216, which needs to be able to send assets (and their subassets) away to be serialized.
What solution would you like?
Asset locking! A user can lock an asset, which puts the asset into an Arc. This blocks mutating the asset until the asset is unlocked. Now the asset can be passed to threads and read from there.
Non-goal: being able to mutate an asset from an async block. While we could support this, I don't think we should. This would mean requiring a Mutex or similar around the asset while it's locked, which would slow down everything accessing the asset, not just the async block.
Expected usage

A system takes a ResMut<Assets<A>>.
The system calls let asset_arc = assets.lock(my_handle).
A task or similar is spawned that is given the Arc.
The task reads the Arc to do its processing.
The task finishes its work and drops the Arc.
The asset is automatically (after a world update) unlocked, returning it to normal asset storage.

Design proposal

Both dense and hash storage store an AssetPresence (bikeshedding ready), which looks like:
enum AssetPresence<A> {
    None,
    Unlocked(A),
    Locked(Arc<A>),
}

When inserting an asset into Assets<A>, it begins in the Unlocked state. Note, it's actually totally fine to replace a locked asset. We're not locking the AssetId, we're locking the actual data. So just throwing way the existing Arc and replacing it is fine. This does lead to the slightly odd case that a locked asset may still trigger an AssetEvent::Modified. This seems fine, since relying on an AssetId remaining locked is weird and point 6 also makes this some more reasonable.

Two new functions are added to Assets<A> to lock and unlock assets:
pub fn lock(&mut self, id: impl Into<AssetId<A>>) -> Option<Arc<A>> {
    // Lock the asset if it exists.
}

This either returns None (if the asset doesn't exist of course), moves the asset to the locked state (if the asset was unlocked), or just clones the existing Arc (if the asset was already locked).
pub fn try_unlock(&mut self, id: impl Into<AssetId<A>>) -> Result<(), UnlockAssetError> {
    // Unlock the asset if it exists, and there is only one strong reference to the Arc.
}

This either returns Ok if the asset was successfully, an error if the asset doesn't exist, or an error if the asset is still being used. Unfortunately, this has no way of telling you what is keeping the asset locked. This is because cloning the Arc has no way of reporting "why" it was cloned. We could make our own wrapper around Arc to also record its reason for being cloned so here we can figure out what is locking an asset, but the complexity of this seems non-trivial and I'm not convinced the value is worth it (how often will you really not know why an asset is locked?).
The reason for the unlock function being public is because in theory a system could lock an asset and then unlock the asset in the same frame (if they don't need the lock). Otherwise, the system could only lock the asset, and then have to wait a frame for the asset to become unlocked again. This is likely a rare case, but if we have to implement the next system anyway, this is a nice function to do so.
Optional: try_unlock could also fail if the asset is already unlocked. It's not clear though how this information will benefit you. Maybe you could filter an asset iterator by whether the asset is unlocked?

A new system is added to Assets<A> to automatically unlock assets.
fn unlock_assets(mut assets: ResMut<Self>) {
    // Try unlocking all assets.
}

This system will iterate through all assets and try to unlock them. This system will be automatically added when adding asset types. This way, you don't need to worry about unlocking assets, you just lock them and then some time in the future, they are unlocked.

Assets::get_mut can now return an error (not just None).
pub fn get_mut(&mut self, id: impl Into<AssetId<A>>) -> Result<&mut A, MutableAssetError>

There are now two reasons you can't get an asset mutably: either it's not present, or it's locked. In either case, returning a value doesn't really make sense. This does mean, if you want to handle the case where the asset is locked, you have to do an Assets::get call to get the locked asset, but I bet most of the time you want to get_mut there is no fallback.
Note Assets::get is pretty much unchanged (from an API point of view). If the AssetPresence is None return Option::None. If the asset is unlocked, get a borrow to the asset. If the asset is locked, get a borrow to the value in the Arc. Nothing fancy!

Assets::iter_mut now returns AssetPresenceMut (bikeshedding intensifies).
pub enum AssetPresenceMut<'a, A> {
    Unlocked(&'a mut A),
    Locked(Arc<A>),
}

While for Assets::get_mut I don't think it makes sense to return the Arcd value, for an iterator I think we should provide the Arcd value. It would be incredibly confusing if an asset ID was missing from this iterator if the asset was just locked.

Assets::remove now returns an AssetPresence.
Removing an asset no longer gives you an owned asset. It may give you a locked asset. Therefore, we need to be able to return either the owned asset or the Arcd asset.
We could choose to prevent removing locked assets (and similarly prevent inserting over locked assets), but it's not clear what we're winning here and is just adding more ways to fail.

ReflectAsset needs to match.

get_unchecked_mut and get_mut both need to return Result<&mut dyn Reflect, MutableAssetError> to match Assets::get_mut.

remove needs to return a ReflectedAssetPresence
pub enum ReflectedAssetPresence {
    None,
    Unlocked(Box<dyn Reflect>),
    Locked(Arc<dyn Reflect>),
}

What alternative(s) have you considered?
As discussed at the start, you can clone your data or Arc your data. Both of those are impractical. Assets can be large, so cloning the data is not practical. Arc-ing your data may not be possible if you don't own the type (e.g., Bevy's Mesh asset can't be Arc'ed externally without rewriting ~all of Bevy rendering), and also leads to your data being permanently immutable.
Additional context
This idea came from the Bevy discord!

Great design writeup; I really appreciate it!

I've been thinking for awhile that introducing Arc (or something like it) to the asset system in some way would be good. Arc-ed assets could also help with efficiently passing assets to the render app, although that gets hairy pretty quickly.
In the current form, this seems like a reasonably non-invasive proposal that enables read-only threaded asset scenarios (which I like). The downside is that I don't think this is an ideal systems for navigating something like the "render app situation", as using it there would mean perma-locking all assets of a given type (ex: all meshes).
Introducing the ability for arbitrary code to permanently block mutations to an asset does feel dangerous, as right now asset mutations can be attempted at any moment. In the proposed system, anything wanting to fully safely do a mutation has to write "defensive code" to handle the case where some other arbitrary code has locked it (although in practice most people would probably just choose to fail in those cases). The act of locking in that context, is in effect a promise that I know all user-defined app code, 3rd party plugins, and upstream bevy plugins will not attempt to mutate this in a way that will fail ungracefully for the duration of the lock. Thats a pretty big "promise" for a user to make, and I'm guessing most users won't have the whole system in their head when they make that promise. Practically, in most cases I suspect this will work out ok, but I do expect this to cause problems, and it could cause them in unpredictable / crashy / hard-to-predict-ahead-of-time ways.
In spite of that, I'm not necessarily against this changeset as it does enable important scenarios, and I do really like that this doesn't rock the boat too much. But I'd like us to be thoughtful about a few things first:

Lets seriously consider the effect this will have on people's code. What is the ideal balance between enabling new scenarios and preventing weird / hard-to-predict / outside of user control errors.
Can this in some way make the "render app asset situation" better? Are there any alternative implementations that can solve both problems? If so, which implementation is preferable?
Should "locked" be the default state? Aka we treat the majority of assets as effectively read-only, with clone-on-mutate behaviors encouraged? Should the default state be configured per asset type, per asset instance, neither, or both?

First, your idea of clone-on-mutate is very clever! I think I will actually implement this into the existing PR (for Clone assets). Note that locking an asset does not fully block mutations. That is, replacing the asset is still allowed. So the "promise" you're describing (for Clone types) is more like "I promise nothing locks the asset, otherwise I will pay the cost". This "promise" problem is still relevant for non-Clone types, but those are likely rare.
I don't like locking being the default, since it makes all mutation have a potentially large overhead (cloning the asset). I like clone-on-mutate as a backup solution, but I'd like to keep mutation mostly in ECS-land (as in, if you have mutable access to Assets<T> you should be able to mutate the asset directly).
The render app asset situation could be somewhat improved with asset locking. For assets that want to be in both the MAIN_WORLD and RENDER_WORLD (any other case requires a move, not a clone), we can skip the current implementation's clone and lock instead. I'm not too familiar with how this part works (why I didn't implement this in my PR), but I'd expect that once the data has been copied to the GPU, we can drop the Arc, and then the asset becomes mutable in the MAIN_WORLD again. Even if that's not true, this still just means that the asset can be mutated normally until it gets copied to the RENDER_WORLD, after which, you can still mutate it using copy-on-mutate.
I think enabling new scenarios is worth it here. Today, your only strategy for moving assets into async contexts is to fully clone the asset, and this sucks for the purposes of asset saving.

To summarize, if we make a function like get_mut_or_clone (which does the copy-on-mutate behavior when locked), and make this the front-door for users, we get the benefit of locking, without introducing those weird errors you're suggesting (and thank you for this idea @cart)

We could also piggyback off of RenderAssetUsages, and Arc the resources only when they're RENDER_WORLD only or something.

I decided to write up @cart's idea of just always Arcing assets in #15723 and I feel better about it (especially after finding out about Arc::make_mut). Though I still feel uncomfortable about the disadvantage I wrote.


Magic32 function

The Magic32 function appears to be CRC32. If you examine the lookup table, it's exactly the same as your Magic32_Table.
There is also a bug in your implementation. Replacing that loop with  for (int r = 0; r < high; r++)  should fix it.

Thanks for pointing this out, I didn't recognized it because it looks like a 4-registrers hash algorithm, I think that's caused by compiler optimizations.
Anyway, when I created this method, I'm using euphd as the input, which gives me the correct result (exactly same as CRC32). The bug only occurs for specified length of string tho.


chore(main): release 0.72.2

:robot: I have created a release beep boop
0.72.2 (2024-08-23)
What's Changed

Fix pipeline run user perms by @qgerome in https://github.com/BLSQ/openhexa-app/pull/795

Full Changelog: https://github.com/BLSQ/openhexa-app/compare/0.72.1...0.72.2

This PR was generated with Release Please. See documentation.

:robot: Created releases:

0.72.2
:sunflower:


Any list of the numpy supported functions?

Hi, I'm looking for a list of numpy supported functions to see how I can formulate my problem. Is there any available? Thank you.

Hey @mrrezaie ,
Good news and bad news:
Bad news is that the only formal list, in this thesis (pg. 72), is somewhat out of date.
Good news is that the reason it's out of date is that many new functions have been added since then!
The most up-to-date place to look would be directly in the aerosandbox.numpy source code: https://github.com/peterdsharpe/AeroSandbox/tree/master/aerosandbox/numpy
NumPy functions here are categorized into different modules; if you have a question about a specific function, let me know and I'll try to point you in the right direction.
Best,
Peter

Thanks for your response. I was looking for something like this: https://numba.pydata.org/numba-doc/dev/reference/numpysupported.html
Does this error mean that numpy.gradient has not been supported yet? Or I'm doing something wrong here?
import casadi
import aerosandbox.numpy as np

opti = casadi.Opti()
A = opti.variable(10)
np.gradient(A, 0.01, edge_order=2)

AttributeError: 'MX' object has no attribute 'full'
Exception: Implicit conversion of symbolic CasADi type to numeric matrix not supported. This may occur when you pass a CasADi object to a numpy function. Use an equivalent CasADi function instead of that numpy function.

numpy.gradient is not present in AeroSandbox master branch, but @peterdsharpe added it in the develop branch recently:
https://github.com/peterdsharpe/AeroSandbox/blob/develop/aerosandbox/numpy/calculus.py.
Usually, when you see this kind of error:
Exception: Implicit conversion of symbolic CasADi type to numeric matrix not supported. This may occur when you pass a CasADi object to a numpy function. Use an equivalent CasADi function instead of that numpy function.
It means that you use a non-casadi-supported numpy function

I see; thanks for your help. Great to see you are improving numpy support. I hope casadi will do the same in near future. https://github.com/casadi/casadi/issues/2626

I had some thoughts about this numpy/casadi interactions lately, actually. I'd be happy to have your opinions on that:
https://github.com/peterdsharpe/AeroSandbox/discussions/120

@mrrezaie , AeroSandbox v4.2.0 was just released a few minutes ago which makes the newly-added numpy.gradient() public! pip install --upgrade aerosandbox[full] should pull in the changes.

@peterdsharpe It is working very well, thanks a lot for your help.
@cdhainaut This is indeed a very good proposal. Actually, I know nothing about aerodynamics and aircraft, and casadi-numpy interaction was the only reason I'm using AeroSandbox. So, as a user and a beginner, I like this idea. However, it seems that casadi has already some plans to improve its numpy support. Perhaps you developers could collaborate with each other on this and make something fabulous.
Thanks again.


Final Capstone Project Front-End

What we have done 🔨 :
Student A:
Back-end:

Created Rails API with Postgres database integration
Populated seed.rb with consistent data for cars, reservations, user, and cities
Added methods to fetch all cars, reservations, cities, and users
Added a way to fetch everything related to a reservation in one API call
Added method to POST and DELETE cars (admin only)
Added method to POST and DELETE reservations

Front-end:

Created the React page to show all available cars in the company:

Created carousel styling with 3 cars at a time, similar to the design provided
Added animation to the carousel
Added name, brand, price information, and icons for each car

Used Redux to fetch data from the Rails Back-End

Student B:

Added reservations table with representative data
Added reservedCar() to merge reservations and cars data.
Added reservedCity() to merge reservations and cities data.
Added isActive() to check the status of the reservation.
Added a form to make a new reserve.
Added axios pointing to the API endpoint to fetch all the reservations.
Created the options from for cars and cities based on the redux store.
Added delete btn on the reservations table fully functional
Added cities, reservations reducers.
Added log out btn to clear the current user session

Student C:

When the user clicks the "Add item" link in the navigation panel they can see a form for adding a new item.
When the user selects a specific item, they can see its full description (skip the "Rotate image" button)
If the user is admin and he clicks delete it will see a delete button showing up under each item in the main page.

Back-End Pull Request Link: https://github.com/lfmnovaes/car-rental-back-end/pull/14

Thank @MuriloRoque for the amazing review! We have implemented new features, the requested changes and more styling to the app! 😄

Hi @ramiaquista, @lfmnovaes, @elassis,
In my opinion, your project is ready for the presentation!  There is nothing else to say other than... it's time to merge it :shipit:
Good luck! 🎉
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.


use Jammit.public_root if defined to support Jammit 0.6.5

Jammit version 0.6.5 changed how it sets the public root directory. I just updated middleware.rb to use the new way if defined, Jammit.public_root, otherwise it uses the old PUBLIC_ROOT.

This is one is starting to bite me, too :).

+1


Add dumb-init to base image to help with term signals

This isn't directly a problem for tessera when running a container directly with something like docker run however it's fairly common practice to run a bunch of your own entry scripts (as we do in the dev-quickstart). I suspect a lot of people use them as a template.
The problem with this approach is that SIGTERM signals no longer get passed along to tessera and tessera will be running on a different pid. dumb-init solves this problem.
https://github.com/Yelp/dumb-init
If there is no appetite for adding this to the base image I will update the dev-quickstarts with a custom docker image that will inherit from tessera.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Couple of comments.
https://github.com/Yelp/dumb-init#using-a-shell-for-pre-start-hooks - Does this mean there could be impacts for any users that are using custom CMDs to do some additional work?

Yes, they would need to change the cmd or the entry point. If you had something like:
FROM quorumengineering/tessera:latest
COPY tessera-config.json
CMD ["-configfile", /tessera-config.json"]

you would need to change the Dockerfile to be
FROM quorumengineering/tessera:latest
COPY tessera-config.json
CMD ["/tessera/bin/tessera", "-configfile", /tessera-config.json"]

or
FROM quorumengineering/tessera:latest
COPY tessera-config.json
CMD ["-configfile", /tessera-config.json"]
ENTRYPOINT ["/tessera/bin/tessera"]

What are the size differences by adding dumb-init to the images?

less than a kb

Can you give a bit more detail on what dev-quickstart is doing in its entryscripts and what problems this causes without dumb-init. It would help understand the change and may help others who are searching for solutions if they have the same problem.

It's a combination of problems. In the quick start we're changing the config based on env vars and then starting tessera. The problem with this is that the main entry point becomes the bash script and tessera ends up starting on a non 1 PID.
The main problem with this is that tessera will not react to a sigterm, so you could have strange things like vertx not finishing a response or worse not closing a db cleanly, partial commits that kind of thing.
To be clear, this is not a problem with tessera per se and thinking about it more maybe the right answer is to fix the dev-quick-start to follow better practices.

Update the code in https://github.com/ConsenSys/quorum-dev-quickstart/pull/136 to contain better examples


S/MIME sign and immediate verification fails

Hi,
I've tried my luck on the mail list, assuming the problem to be on my side but after downloading the bc-sources and using the debugger I think I've found an actual bug in BouncyCastle.
I've created a test case - feel free to add it to the sources if useful - that shows the problem
SMIMESigning_Test.zip
I create a MimeBodyPart containing a mail in different combinations, then I sign it (first encapsulated, then as multipart). After that I immediately verify the signature against the certificate. Everything works except when I create a mail that is organized the following way:

A multipart/mixed part containing

A multipart/alternative part containing

A text/plain body part
A text/html body part

A text/plain file attachment with disposition "attachment"

Essentially a mail you regularily see nowerdays containing HTML and an alternate plain text part plus an attachment.
When signing encapsulated the signature verification check succeeds here but using multipart, the check fails with the exception

org.bouncycastle.cms.CMSSignerDigestMismatchException: message-digest attribute value does not match calculated value
at org.bouncycastle.cms.SignerInformation.doVerify(SignerInformation.java:529)
at org.bouncycastle.cms.SignerInformation.verify(SignerInformation.java:613)
at __Run_SMIMESigning.performSignatureCreationAndCheck(__Run_SMIMESigning.java:117)
at __Run_SMIMESigning.testMailSigning(__Run_SMIMESigning.java:75)

I added some debug-infos in my testcase and you can see that the calculated digest is the same for encapsulated and multipart:
signed digest: -602279b7bb1596241f5af136cb025a355ec08b1d895d590ff732aae42fb216cb
[...]
signed digest: -602279b7bb1596241f5af136cb025a355ec08b1d895d590ff732aae42fb216cb
But the verification results into different ones:
digest: -602279b7bb1596241f5af136cb025a355ec08b1d895d590ff732aae42fb216cb
[...]
digest: -e41b571e93a088f1616a4b85b786decd80f703ea3c45d5d8041f501e1c77036
So I downloaded the sources and extended SignerInformation.doVerify the following way:
OutputStream      mydigOut = calc.getOutputStream();
System.out.println("start digesting");
OutputStream digOut = new OutputStream() {
    @Override
        public void write(int b) throws IOException {
            System.out.print((char) (b & 0xff));
//           System.out.print(Integer.toHexString(b & 0xff) + " ");
            mydigOut.write(b);
        }
    };

so the data being digested is printed on STDOUT. This shows a difference in the digested data (stripped down to the relevant part):
Encapsulated:
start digesting
Content-Type: multipart/mixed;
    boundary="----=_Part_22_1902260856.1560873376436"
[...]

Some HTML

Some text with non-ascii: =E2=82=AC

------=_Part_21_1151593579.1560873376436--

------=_Part_22_1902260856.1560873376436
Content-Type: text/plain; charset=utf8; name=filename.txt
[...]
------=_Part_22_1902260856.1560873376436--

Finished digesting

Multipart signing:
start digesting
Content-Type: multipart/mixed;
    boundary="----=_Part_22_1902260856.1560873376436"
[...]

Some HTML

Some text with non-ascii: =E2=82=AC

------=_Part_21_1151593579.1560873376436--
------=_Part_22_1902260856.1560873376436
Content-Type: text/plain; charset=utf8; name=filename.txt
[...]
------=_Part_22_1902260856.1560873376436--

Finished digesting

For some reason an empty line between the end of the multipart/alternative and the multipart/mixed part got lost.
On the producing side I can work around that problem by using encapsulated signing or do compression before signing but I assume that receiving a multipart/signed mail might run into the same problem where such workaround is not available (that would be another testcase but I'll wait for that till I got some feedback here).
Have I found a bug or is it me doing something fundamentally wrong when using BouncyCastle to sign mails?

Which version of JavaMail is this using? I can reproduce the problem but not in the way shown above.

From the manifest.MF file:
Bundle-Version: 1.5.0

Haven't tried it with 1.6, yet because this version currently breaks things here in other (non-mail-related) parts.

Updated to BC 1.62 and JavaMail 1.6.2 has no effect on the outcome of the testcase.

I can reproduce the problem but not in the way shown above.

By that, do you mean that you can reproduce the problem using a different test or that you used my testcase and it failed but differently? If the latter, what's the difference?

I've got some progres here, the effect is created by SMIMEUtils.outputPostamble:
InputStream in;
try
{
    in = ((MimeBodyPart)parent).getRawInputStream();
}
catch (MessagingException e)
{
    return;   // no underlying content rely on default generation
}
[...]

If the given MimeBodyPart throws a MessagingException because of no contained content, the method simply returns. With a content - and even an empty one as far as I understood - you have the output of at least a line break. When changing above block to
InputStream in;
try
{
    in = ((MimeBodyPart)parent).getRawInputStream();
}
catch (MessagingException e)
{
    lOut.writeln();
    return;   // no underlying content rely on default generation
}
[...]

my test cases run through.

Hm, I'd like to give this issue a bump. Is there anything I can provide or help with in order to get progress here?

1,5 years after the initial post, I'd like to give this another bump. Is there anything I can provide or help with in order to get progress here?

1,5 years after the initial post, I'd like to give this another bump. Is there anything I can provide or help with in order to get progress here?

I'd be curious to see if this also happens with our generic SMIME library (see org.bouncycastle.mime in the PKIX jar). We've had a string of problems over the years with the way JavaMail loads and re-encodes it's data.

I'm not sure how to blame JavaMail here. The empty line between two MIME-boundaries is "normal" and even if it weren't, it shouldn't be ignored while calculating the digest for a signature check.

I also faced the behavior using jakarta.mail 1.6.5 and bcmail-jdk18on 1.72 when i tried to verify a created message instantly. Verification of the sent message with Outlook on the other hand was successful.

I've got some progres here, the effect is created by SMIMEUtils.outputPostamble:
InputStream in;
try
{
    in = ((MimeBodyPart)parent).getRawInputStream();
}
catch (MessagingException e)
{
    return;   // no underlying content rely on default generation
}
[...]

If the given MimeBodyPart throws a MessagingException because of no contained content, the method simply returns. With a content - and even an empty one as far as I understood - you have the output of at least a line break. When changing above block to
InputStream in;
try
{
    in = ((MimeBodyPart)parent).getRawInputStream();
}
catch (MessagingException e)
{
    lOut.writeln();
    return;   // no underlying content rely on default generation
}
[...]

my test cases run through.

When creating parts and composing messages no input streams are setup, therefore the MessagingException is thrown and the Bouncy Castle implementation fails. I assume it is not meant for this use case as all examples from bcmail obtain a full message from some input stream. A quick fix that worked for me was to call the copy constructor on the created message (which sets up input streams) and verify the copy instead.

I assume that receiving a multipart/signed mail might run into the same problem

If you also implement the receiving side with Jakarta Mail and Bouncy Castle, I allege no, because both IMAPMessage and POP3Message have reliable getContentStream implementations when the message retrieval is successful. As said earlier, verification with Outlook was successful too.


XCode 11.4 - Crash after objc_copyClassList call

Indeed, I could reproduce the crash running the unit tests.
I will investgate that problem and fix it asap, thanks for reporting !

I pushed a commit that fixes the crash.
It did involve a change though, that might be breaking for people using custom appenders, and references them from a config file:
Previously, the different appenders subclasses were auto-discovered by getting a list of the classes from the runtime. This was the part that was crashing.
I changed it to a static list of types, with the ability to register other types using AppendersRegistry.registerAppender(Appender.Type).
So now, to use a custom appender in configuration files, this method should be called before trying to load the config file.
I still need to work out some problems with the unit tests though: all tests for the AppleUnifiedLoggerAppender are failing, as the reading of the logged messages fails.

I've just build everything with Log4Swift pod targeted to this commit. It works like a charm! And we do have custom appender - it was matter of 1 line change to bring it back (using new registerAppender).
Thank You!

https://developer.apple.com/documentation/xcode_release_notes/xcode_11_4_1_release_notes
Swift
Resolved Issues
Fixed a crash that could occur in Swift code that imported an Objective-C class defined with the objc_runtime_name attribute. (60888835)

FYI: Looks like there is some solution here: https://bugs.swift.org/browse/SR-12344

@jduquennoy Hi! Could you please take a look on my draft PR: https://github.com/jduquennoy/Log4swift/pull/26
I believe that with this fix we don't need AppendersRegistry (or we can do hybrid approach - support "old" way and the new "registry" one).
I tried to compile and run unit tests on xcode 10.3, 11.3.1 and 11.5 - all works ok (no crash, tests are green). Also, I fixed couple of warnings (index → firstIndex) which appear when Swift 5 in use.
I would like to address this issue rather sooner than later - it blocks us to switch to xcode 11.5 (we stuck on 11.3 currently b/c of it). Please let me know what else can I do to help? Thanks!

Hi Sergei,
Thanks millions for this PR !
I'm quite out of time today, i will take a look at your PR tomorrow, beginning of the day.
Sorry for the delay :-(
Jérôme

On 30 May 2020, at 15:35, Sergei<EMAIL_ADDRESS>wrote:
@jduquennoy https://github.com/jduquennoy Hi! Could you please take a look on my draft PR: #26 https://github.com/jduquennoy/Log4swift/pull/26
I believe that with this fix we don't need AppendersRegistry (or we can do hybrid approach - support "old" way and the new "registry" one).
I tried to compile and run unit tests on xcode 10.3, 11.3.1 and 11.5 - all works ok (no crash, tests are green). Also, I fixed couple of warnings (index → firstIndex) which appear when Swift 5 in use.
I would like to address this issue rather sooner than later - it blocks us to switch to xcode 11.5 (we stuck on 11.3 currently b/c of it). Please let me know what else can I do to help? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/jduquennoy/Log4swift/issues/25#issuecomment-636331889, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUE6F3CCC6ALROD4YC3CSTRUEDTBANCNFSM4LTORLWQ.

Jérôme Duquennoy

clef GPG : http://jerome.duquennoy.fr/gpg/jduquennoy.gpg
md5 : c0ff5a8bca033eade512374db18ecb38

Hey @jduquennoy ! Please take a look for unit tests fix PR: https://github.com/jduquennoy/Log4swift/pull/27
Thanks!

@jduquennoy So, it looks like the last thing which should be done is actually implement the "hybrid" approach, namely: clients could use either "old" automatic way of getting appenders, or register an appender explicitly via new api. In such way, I believe, it won't be breaking change, and we can release 1.1.0 (as minor update).
Jacques, what do you think will the right way of doing it? Is it almost as just returning back the objc_copyClassList call? Will it correctly coexist with the new approach?
Thanks!

@jduquennoy Gentle ping about 👆

@jduquennoy And here is the PR about 👆 Please take a look. Thanks
https://github.com/jduquennoy/Log4swift/pull/28

@jduquennoy Hello, any chance to release 1.1.0 to the Cocoapods (see my comment on Jun 13)? Thanks!

Hi Sergei,
I tagged pushed the head of Master to cocoapods, as v1.1.0.
Sadly, I still have tests failing on Travis, for Apple Unified Logs.
I have to rework those tests, to capture the logs in a live stream instead of trying to get them after the tests ran (it is the part that fails in the tests, even if the manual tests I have done shows that it does the logs are issued).

Thanks @jduquennoy !


Add best practices regarding sandbox refreshes

Salesforce allows you to store information in custom settings and other areas which does not pass down to sandboxes upon refresh. Strategies include identifying which Accounts to copy into a sandbox, custom settings, environment-based credentials, etc.

Considerations should include:

How teams should identify parts of their application which do not transfer upon sandbox refresh
How to toggle settings and data on a per-app basis for refreshes
Granting access to users, does it make sense for all Admins to have access on all sandboxes?

@mvogelgesang More very good ideas. Thanks!  Does SF have a list of the settings and other things that do not pass down on refresh?

@virtix I have found a partial list here, https://help.salesforce.com/articleView?id=data_sandbox_implementation_tips.htm&type=0&language=en_US. Some key findings include:

"Customer Portal users aren’t copied. However, the copy process does copy the Customer Portal licenses, so you can create Customer Portal users in these sandboxes as needed." If teams want to have Customer Portal users on the sandbox, they will have to be created manually or by programmatic means.
"User email addresses are appended with an example domain (@example.com), and the original @ sign is replaced with =. This modification ensures that the system ignores these email addresses. For example, a user email of<EMAIL_ADDRESS>in production becomes<EMAIL_ADDRESS>when migrated to sandbox."
Custom Settings
Custom Labels


New package: ResizableArrays v0.1.0

Registering package: ResizableArrays
Repository: https://github.com/emmt/ResizableArrays.jl
Created by: @emmt
Version: v0.1.0
Commit: 04dd3d430b39eff924ce126f2ba75a2843c44aa7
Git reference: master

Needs compat for Julia.

OK I have added a [compat] entry for Julia verisons 0.7 to 1.2 in Project.toml
I guess this is what you meant.

OK I have added a [compat] entry for Julia verisons 0.7 to 1.2 in Project.toml
I guess this is what you meant.

Yes, you also need to retrigger the bot in order to update this PR.

OK done. Thanks for the advice!

Consider enabling TagBot to make sure the release is persistent in your repo, see https://discourse.julialang.org/t/ann-tagbot-creates-tags-and-releases-for-your-julia-packages-when-theyre-registered/23084


fix: remove not needed inputs

ref: https://github.com/reside-eng/workflow-templates-library/pull/66

coverage: 100.0%. remained the same
when pulling d2ebe2b3a3f1fd062d059d91e3b9f37c1baad439 on remove_not_in_use_inputs
into aea852c01020529a231c3c565dc2b1771b1884d6 on main.


Endless loop in cookbook.(*CookbookVersion).resolveDependencies if cookbooks have circular dependencies

We have two cookbooks depending on each other (I know it's pretty bad), and it makes the memory usage explode as soon as a client tries to use these cookbooks. It starts to allocate memory without end until the process is killed. If I break the dependency cycle it works normally.
We are using these same cookbooks with Opscode Chef Server 11, without problems.

Yeah, the depsolver's always been a little weak. I'm surprised that this case (along with the zero byte file in the other issue) isn't covered in the chef-pedant tests, but here we are. I was planning on fixing the depsolver anyway, so I may as well finally get that out of the way too.

At last, I have the rewritten depsolver in a state where I believe it's suitable for testing again. It's now sending back errors in the format chef-pedant expects, although some of the error messages need further refinement.  Of course, since the depsolver's a pretty touchy piece of the software, testing is appreciated.

Awesome! I'll test it today.

I get an error in chef-client:
https://gist.github.com/oker1/6bc2110838d4a1fdd966
I'll try to dig into a bit more.

If you haven't, could you run that with debug on? I have a feeling I know where that's coming from, but if you could try running it with more debug output that'd help narrow it down.

I've been getting back in the goiardi saddle recently, and just duplicated this bug. This should be figured out fairly soon.

 I pushed a fix for this up on the 0.9.1-dev branch. Urk.

And even better, it looks like the circular dependencies no longer makes the memory usage explode. Huzzah! @oker1, if you see this, I believe this problem is finally fixed for you. Sorry for the delay; I got super busy with vacation and various non-goiardi things, and couldn't work on it for a little while.

The fix for this is now in master, and seems to work well.


Full Menu Display Flashes on load/refresh

I don't think this is the same issue described before as #4 Firefox flashing issue, but it sounds similar.  Regardless I'm using the latest rendition of the code.  I've run it in Chrome and Firefox and while Firefox is much worse, there is still a flicker even in Chrome where you see the whole branch of the hidden menu before is collapses into the mega-menu CSS display settings.  Is just my testing environment or do others experience this?  Any ideas in either case?

I found the solution to this elsewhere.  Not sure why it's not been added to the source code though.
`
...

$(document).ready(function () {
$('#lkmcustom').show();
});`


doc/contribute: add examples for finding issues on the issue tracker

For contributors looking for new issues to contribute to it can be
difficult to find issues that need a fix and don't already have a fix
being considered. There are several labels that help guide the way
already, like NeedsFix, HelpWanted. But many issues with this label
will already have a CL. For new contributors this can be especially
difficult.
Fixes #26494

Screenshot of the area of the page that's changing:


Add assertions for root spans

Thanks for making the gem!
I was wondering what you thought of the following idea, to be able to detect root spans.
This is something I have written some matchers for in the org I am part of as it is helpful as a library for framework author to make assertions that certain paths should create new traces.
However, I am unsure about the API for rspec-otel.
Some possibilities I thought of:
expect{ }.to emit_span('child', root: false|true)
expect{ }.to emit_root_span('child')
expect{ }.to emit_span('child').as_root

Please see attached an implementation for the first option. However, I think I prefer expect{ }.to emit_root_span('child') most.
Let me know what you think.

This looks like a great idea. I would prefer the as_root though, as it's more in-line with the other attributes, and would allow chained conditions such as:
with_span('lambda').as_root.with_attributes({'hello' => 'world'})

May main question about .as_root (and general API changes) was what do you think the behaviour should should be when .as_root is not present. Should the matcher:

verify that the span isn't a new trace root, only matching if it is a child of an existing trace
or
should it not care whether or not the span is the trace root or not, and match whether or not it is a trace route or not

If the latter then wanting to test that a trace isn't the span root as well as some attributes of the trace, you would have to:
# First verify the exported span is not a new trace
expect{ }.not_to emit_span('child').as_root

then another test for the attributes you wish to check:
# Verify the exported span has expected attributes
expect{ }.to emit_span('child').with_attributes(foo: 'bar')

However, if the former, then you could have one assertion, which verifies the span isn't the root as well as the attributes it has.
expect{ }.to emit_span('child').with_attributes(foo: 'bar')

But this would be a breaking change in the API as people who are simply testing for spans to be emitted may not care about whether or not they are a trace root or not, and not realise that their spans are trace routes and updating the gem without changes would then cause test failures.

The behavior when no conditions are specified is to retrieve all spans. So by decault, the matcher should retrieve root and non-root spans.
We could have as_root, and as_child ? Then, the default remains the same, but we can specify both whether we want a root, or non-root span.

Alternatively, we could have (in another PR), a new not filter, which would negate the following one.
This would match non-root spans named 'child', with the appropriate attrinutes.
emit_span('child').not.as_root.with_attributes('hello' => 'world')

We could have as_root, and as_child ?

I think this is good, I will see if I can implement it when I have some time.

This is ready for review again @dmathieu

Thank you! The changes look good. Can you fix the linting issues?

Ah yea, should've checked if rubocop was in the repo, all fixed up.


fix(menuselect): use new inputtext for menuselect search inputs

Summary

What: Use an InputText component in MenuSelect instead of a custom input
Why: So that future styling updates are automatically applied, and to bring the component more in line with the spec for styling in active states
Ticket: https://app.shortcut.com/genepi/story/175880/design-review-feedback-location-normalization
Design: https://www.figma.com/file/EaRifXLFs54XTjO1Mlszkg/Science-Design-System-Reference?node-id=642%3A1

Demo

Notes
I also checked consumers of MenuSelect to ensure they weren't adversely impacted. (ComplexFilter and Dropdown)
Checklist

[x] I merged latest main
[x] I manually verified the change
[x] I added labels to my PR
[ ] I tested in multiple browsers
[ ] I added relevant unit tests
[ ] I have notified others of changes they need to make locally (migrations, jobs, package updates, etc)

The InputSearch component should have a PR up shortly, which will save some of the styling for the search icon and event handling. I can make this update to the menuSelect as part of the InputSearch ticket: here, if this isn't time sensitive to today

@mdjmoore it isn't time sensitive. Thank you for tackling this! 🚀


Fix apostrophe in printed output

I should be better to use ' instead of `, to match the closing one.

This was done intentionally to match Make's output exactly.


Changed UI of suggested_coding_site.html

Description
Best and Free Online Websites to Learn Coding for Beginners was not looking good as all the text was in long paragraph style
and also the background gradient colors were not complementary so it not visible also ..
Please include a summary of the change and which issue is fixed.
Fixes #550
The changes made are that the paragraph style text is been changed into responsive cards design made Flex-box and CSS only
List any dependencies that are required for this change
No , Dependencies were required just pure CSS was applied
Type of change
Enhancement of suggested_coding_site.html
How Has This Been Tested?
With the help of developer tools
UI /UX changes
Attach gif or screenshot for changes.

Before :

- After :

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] 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

hey @harikesh409 I have made a PR regarding the enhancement .waiting for your reply

The contact us and the copyright footer is messed up.

The contact us and the copyright footer is messed up.

its done ..

The main content is not proper now.

I have applied  the changes you suggested and its working fine on local machine . i have pushed them also so that you can see the changes

check for this resolution, the responsive is not proper.

Hey actually i don't have monitor of this size so i made keeping in mind of the laptops and mobile screen .. so i am having hard time visualizing it ..so could you help a bit 🙂

@harikesh409 i am actually having hard times figuring media queries for this resolution even using devtools so if you could suggest something that would be good 🙂


Switch between inline and multi-line styles

(This is not a priority for Summer of Haskell.)
One problem with a bunch of inline blocks is that everything ends up on one line.  Using the multi-line style is kind of like deciding to line-wrap the function call, as in:
translated(colored(solidCircle(1), red), 3 * sin(t - 180) + 7, 0)

versus
translated(
    colored(solidCircle(1), red),
    3 * sin(t - 180) + 7,
    0)

It makes sense to me to offer both choices.  It would be great to do this in a consistent way across all CodeWorld blocks, so every block has both an inline and multiline style, and it's easy to switch back and forth (without breaking existing connections to subblocks).  I suspect this shouldn't be too hard, given that we already have a Haskell-based abstraction for defining our blocks.  It should be possible for it to define two underlying blocks, and logic for swapping from one to the other.

Obviously, by "every block", I mean every block with fields

It appears that this is already a feature.  See #331 and #332 for remaining issues, but I'll close this.


[Sass Mixins] Hamburger mixin flooring breaks for rem units

How can we reproduce this bug?

Call hamburger mixin using rem units, like so:

@include hamburger(
            $color: $primary-color,
            $color-hover: $primary-color,
            $width: 1.375rem,
            $height: 1.125rem,
            $weight: 0.2rem
        );

Spacing is floored to 0 in most cases (usually the spacing claculates as smaller than 1rem)

What did you expect to happen?
Didn't expect flooring to get applied when using non-pixel units.
What happened instead?
Spacing floored to 0rem.

Proposed fix here:
https://github.com/zurb/foundation-sites/compare/develop...tbredin:patch-1

Fixed in #9100, will be in 6.2.4, scheduled to be released Oct 20.


(MHRise) Random crash when going from Steelworks to Buddy Plaza

Sadly I lost the REFramework log, will post again some other time. I have the crash dump at least, though. Not easily reproducible either.

If you are able to upload your dmp file along with the dinput8.dll and PDB you compiled, that would help.

Ive got few crashes tonight, do you need to upload anything else? Not sure what PDB is.
MHR Crash report.zip

I'm only using the DLL from the artifact builds, so I don't think I have a PDB available. I did attach the dump here for you.
https://drive.google.com/file/d/13K_4tXiQRzWeztO9pGZg-SEQ040hFqs4/view?usp=sharing (696 MB)

Ive played more today and i could not do two long quest without crashing. If a quest last more than 15min, i got to relaunch the game to be sure it doenst crash on the 2nd one.

Sorry, didn't realize that there was a REFramework crash dump file of its own. I don't have a pdb file unfortunately.
reframework_crash.zip

Random crashes should be fixed in b98758ce3b1c0986e1bae706d92b0ce322fb57d2
Should allow you to use other third party DLLs like reshade now too.


Creating URL-Shortener-Microservice Hint file

🔧 feat: Create a Hint section about shorter URL creation to the database
🔧 feat: Create a Hint section about shorter URL retrieval from the database.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Congrats @ on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝

Thank you so much! I'll keep helping =) See ya!


Need use cases to guide tensorflow installation

Thank you for submitting a TensorFlow documentation issue. Per our GitHub
policy, we only address code/doc bugs, performance issues, feature requests, and
build/installation issues on GitHub.
The TensorFlow docs are open source! To get involved, read the documentation
contributor guide: https://www.tensorflow.org/community/contribute/docs
URL(s) with the issue:
https://www.tensorflow.org/install
Description of issue (what needs changing):
People want tensorflow for different reasons - to play, to learn from, to deploy in this/that/other environment, to integrate into legacy systems, etc.  So far I can find zero guidance on integrating tensorflow inference module that works in python laboratory environment into Windows .exe desktop application built from C++ source. That is: "Install on Windows" is simply too coarse a description that applies to some use cases, but not to others. I've definitely installed something on Windows, and I can definitely use it for python-based explorations... but it is completely unclear to me if I can deploy it in production in the environment I need to, or what exactly the installation contains. I suggest that there needs to be a comprehensive (and growing) list of use cases that lay out how tensorflow can be used in conjunction with various requirements.
Sadly, the modern trend is to offer 2 sentences of introduction, and then say "sign up and get started". That's not helpful if it takes 6 months to realise there is either a dead end to the preferred development path, or a prohibitively expensive redeployment  to a new platform required for a legacy product :-( Right now, I simply cannot tell if either of those is a possibility... or something else.
Correct links
Is the link to the source code correct? n/a
Parameters defined
Are all parameters defined and formatted correctly? n/a
Returns defined
Are return values defined? n/a
Raises listed and defined
Are the errors defined?  n/a
Usage example
Is there a usage example? n/a
See the API guide: https://www.tensorflow.org/community/contribute/docs_ref
on how to write testable usage examples.
Request visuals, if applicable
Are there currently visuals? If not, will it clarify the content? n/a
Submit a pull request?
Are you planning to also submit a pull request to fix the issue? I have no idea what a pull request is, so that would be a no.

@omatai
Please follow instructions here: link, #42367, #36167 [these should guide you]

Ensure you have 64 bit cpu and python [python 3.8 works from tf version 2.2].
check if your AVX is supported (cpu supports AVX instruction sets.)
You have not installed the Microsoft Visual C++ Redistributable package.

Thanks!

Please follow instructions here: link, #42367, #36167 [these should guide you]

2 of those 3 suggestions are an admission that the documentation is insufficient - if the documentation were sufficient, there would be no need for external links. The 3rd link (to the pip install page) makes no mention of "windows" or "C++" or other elements I mentioned in the use case I am interested in. And nor should it - the guidance on what to install depending on the use case that interests you should exist at the top level to guide you towards the lower levels.
The guidance I see as missing is something to answer the question "should I...?" rather than "can I..."? Can I install tensorflow with pip. Yes. From source? Probably. But which SHOULD I do according to my intended use of tensorflow? I think I should probably do both... maybe. But there's a good chance someone will decide that a precompiled tensorflow DLL for Windows would be a good idea, issue that on some future release (or maybe it's already there?) and I shouldn't install and build from source at all because that would be a waste of time. In that utopia, I would only have to include a single header file, link to that DLL, and in literally 5 minutes I would be using tensorflow. (In contrast, see here for an example of what is more likely: a question that was only answered to the asker's satisfaction after 18 months.)
Am I wasting my time currently? I don't know, because there is no guidance to tell me how to install/build/configure tensorflow that is directed towards particular use cases. Only when I get to the end of the install/build/configure mission will I be able to tell if I have done the right thing.
It's not about Windows or C++ or anything so specific - it's about the intended use of tensorflow, and which path(s) one should take to install/build/configure so that (a) one does not waste time exploring non-productive paths and instead (b) choose the correct path confidently from the outset.

There's an uncountable number of possible use scenarios. There's a finite number of developers. We cannot simply document everything.
In general, if you use the Python API and the pip package works for you, you install that. Otherwise, you build from source.
If you need C++ or other language bindings, you build from source again and then use the provided libraries (shared objects)

If I could encourage you to take that last sentence and incorporate it into the "Build from source" documentation under Tensorflow Install instructions, that would be a very useful start. Why?

But what you are saying (that the documentation currently does not say) is that building from source produces libraries. Great! That is guidance that is missing: please document it. And also document where to find what else is built. And what it is useful for.
As it stands, the implicit guidance provided by the documentation ("don't bother") is distinctly unhelpful. And ok: so use cases might be far too fine-grained to be practical. But it would take very little to say things like:

If you need to do any of the following, you will need to build from source:

this platform/application/context
that platform/application/context
other platform/application/context

When you build from source, you will create:

this in this folder
that in that folder
-other in other folder

Reading the "build from source" documentation as it stands, there appears to be no point whatsoever building from source. Similar applies to the API for various languages - there is no hint as to how to access it. Do I go outside and shout tensorflow::ops::fingerprint at the universe? I hope not. But from the documentation, I cannot be 100% certain this is not the case because the documentation fails to tell me what IS the case.

Sorry - I have given up using Tensorflow directly since it is too poorly documented. For a simple network, I have found that coding it from scratch by hand (a) took less time than trying to get TF to build and (b) ran fast enough for my needs. For more complex networks, I am hopeful that I can adapt the Windows DirectML Samples to my needs. I'm not in a position to contribute to the docs because I cannot make anything work where I need it to - integrated into a legacy C++ application on Windows :-(

Sorry - I have given up using Tensorflow directly since it is too poorly documented. For a simple network, I have found that coding it from scratch by hand (a) took less time than trying to get TF to build and (b) ran fast enough for my needs. For more complex networks, I am hopeful that I can adapt the Windows DirectML Samples to my needs. I'm not in a position to contribute to the docs because I cannot make anything work where I need it to - integrated into a legacy C++ application on Windows :-(


Add configuration option to remove/amend start indentation space

Hi, it adds feature required in #345

oops wrong branch.


feat: implement wallet naming, add tests

Summary of Changes
Adds the optional feature of naming your wallet. So far there is no functionality with the name other than storing it in LocalStorage and the store.
Here's what it looks like:

Here's the wallet names showing up to each other after a connection invitation:

Related Issues
N/A
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[x] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[x] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[x] Updated documentation as needed for changed code and new or modified features;
[x] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

Looks great, is there any way that you can make the text field stop receiving characters after 50 characters?

Looks great, is there any way that you can make the text field stop receiving characters after 50 characters?

Their likely is but I'm just going off of the wireframes and specs that KN gave. They want to allow people to type more than 50 characters and then make an error popup when they go to continue. See the 'Errors' section here: https://xd.adobe.com/view/eb9e0945-61d7-40ca-8e8e-bf4bd0c72934-becd/screen/8dcbeef8-7739-483c-bf74-50c8ab219853/specs/


Release 5.39.0 Has IPhysicsEnginePLugin Errors

The 5.39.0 Release introduces new bugs in the Babylon.d.ts
When type to build my lib against the new declaration file using TSC 4.6.2. It gets plenty errors now. It did not get those error before.
[17:25:24] Using gulpfile ~/Documents/Babylon/BabylonToolkit-Share/Manager/gulpfile.js
[17:25:24] Starting 'default'...
[17:25:24] Starting 'compile'...
types/babylon.d.ts(80474,9): error TS2416: Property 'executeStep' in type 'AmmoJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(delta: number, impostors: PhysicsImpostor[]) => void' is not assignable to type '{ (delta: number, impostors: PhysicsImpostor[]): void; (delta: number): void; }'.
types/babylon.d.ts(80497,9): error TS2416: Property 'applyImpulse' in type 'AmmoJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(impostor: PhysicsImpostor, force: Vector3, contactPoint: Vector3) => void' is not assignable to type '{ (impostor: PhysicsImpostor, force: Vector3, contactPoint: Vector3): void; (body: PhysicsBody, location: Vector3, impulse: Vector3): void; }'.
    Types of parameters 'impostor' and 'body' are incompatible.
      Type 'PhysicsBody' is missing the following properties from type 'PhysicsImpostor': object, type, _options, _physicsEngine, and 66 more.
types/babylon.d.ts(80577,9): error TS2416: Property 'setLinearVelocity' in type 'AmmoJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(impostor: PhysicsImpostor, velocity: Vector3) => void' is not assignable to type '{ (impostor: PhysicsImpostor, velocity: Vector3): void; (body: PhysicsBody, linVel: Vector3): void; }'.
    Types of parameters 'impostor' and 'body' are incompatible.
      Type 'PhysicsBody' is not assignable to type 'PhysicsImpostor'.
types/babylon.d.ts(80583,9): error TS2416: Property 'setAngularVelocity' in type 'AmmoJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(impostor: PhysicsImpostor, velocity: Vector3) => void' is not assignable to type '{ (impostor: PhysicsImpostor, velocity: Vector3): void; (body: PhysicsBody, angVel: Vector3): void; }'.
    Types of parameters 'impostor' and 'body' are incompatible.
      Type 'PhysicsBody' is not assignable to type 'PhysicsImpostor'.
types/babylon.d.ts(80786,9): error TS2416: Property 'executeStep' in type 'CannonJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(delta: number, impostors: PhysicsImpostor[]) => void' is not assignable to type '{ (delta: number, impostors: PhysicsImpostor[]): void; (delta: number): void; }'.
types/babylon.d.ts(80788,9): error TS2416: Property 'applyImpulse' in type 'CannonJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(impostor: PhysicsImpostor, force: Vector3, contactPoint: Vector3) => void' is not assignable to type '{ (impostor: PhysicsImpostor, force: Vector3, contactPoint: Vector3): void; (body: PhysicsBody, location: Vector3, impulse: Vector3): void; }'.
    Types of parameters 'impostor' and 'body' are incompatible.
      Type 'PhysicsBody' is not assignable to type 'PhysicsImpostor'.
types/babylon.d.ts(80808,9): error TS2416: Property 'setLinearVelocity' in type 'CannonJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(impostor: PhysicsImpostor, velocity: Vector3) => void' is not assignable to type '{ (impostor: PhysicsImpostor, velocity: Vector3): void; (body: PhysicsBody, linVel: Vector3): void; }'.
    Types of parameters 'impostor' and 'body' are incompatible.
      Type 'PhysicsBody' is not assignable to type 'PhysicsImpostor'.
types/babylon.d.ts(80809,9): error TS2416: Property 'setAngularVelocity' in type 'CannonJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(impostor: PhysicsImpostor, velocity: Vector3) => void' is not assignable to type '{ (impostor: PhysicsImpostor, velocity: Vector3): void; (body: PhysicsBody, angVel: Vector3): void; }'.
    Types of parameters 'impostor' and 'body' are incompatible.
      Type 'PhysicsBody' is not assignable to type 'PhysicsImpostor'.
types/babylon.d.ts(80865,9): error TS2416: Property 'executeStep' in type 'OimoJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(delta: number, impostors: PhysicsImpostor[]) => void' is not assignable to type '{ (delta: number, impostors: PhysicsImpostor[]): void; (delta: number): void; }'.
types/babylon.d.ts(80866,9): error TS2416: Property 'applyImpulse' in type 'OimoJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(impostor: PhysicsImpostor, force: Vector3, contactPoint: Vector3) => void' is not assignable to type '{ (impostor: PhysicsImpostor, force: Vector3, contactPoint: Vector3): void; (body: PhysicsBody, location: Vector3, impulse: Vector3): void; }'.
    Types of parameters 'impostor' and 'body' are incompatible.
      Type 'PhysicsBody' is not assignable to type 'PhysicsImpostor'.
types/babylon.d.ts(80876,9): error TS2416: Property 'setLinearVelocity' in type 'OimoJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(impostor: PhysicsImpostor, velocity: Vector3) => void' is not assignable to type '{ (impostor: PhysicsImpostor, velocity: Vector3): void; (body: PhysicsBody, linVel: Vector3): void; }'.
    Types of parameters 'impostor' and 'body' are incompatible.
      Type 'PhysicsBody' is not assignable to type 'PhysicsImpostor'.
types/babylon.d.ts(80877,9): error TS2416: Property 'setAngularVelocity' in type 'OimoJSPlugin' is not assignable to the same property in base type 'IPhysicsEnginePlugin'.
  Type '(impostor: PhysicsImpostor, velocity: Vector3) => void' is not assignable to type '{ (impostor: PhysicsImpostor, velocity: Vector3): void; (body: PhysicsBody, angVel: Vector3): void; }'.
    Types of parameters 'impostor' and 'body' are incompatible.
      Type 'PhysicsBody' is not assignable to type 'PhysicsImpostor'.
TypeScript: 12 semantic errors
TypeScript: emit succeeded (with errors)
[17:25:38] Finished 'compile' after 14 s
[17:25:38] Starting '<anonymous>'...
[17:25:41] Finished '<anonymous>' after 2.77 s
[17:25:41] Finished 'default' after 17 s

looking into it, thanks a lot for reporting!


webview's new function on message not working

Description
[FILL THIS OUT: webview's new function onmessage not working.]
Reproduction
[FILL THIS OUT:  https://rnplay.org/apps/1RLF9A .]
Solution
[FILL THIS OUT:]
Additional Information

React Native version: [0.39.2]
Platform: [both]
Operating System: [MacOS  Windows]

Above is ok now. but the webview can't load url now .

webview can't place in view label like this:
`import React, { Component } from 'react';
import { WebView,View } from 'react-native';
class MyWeb extends Component {
render() {
return (

<WebView
source={{uri: 'https://github.com/facebook/react-native'}}
style={{marginTop: 20}}
/>

);
}
}`
this not working too.
React Native version: [0.40.0]
Platform: [both]
Operating System: [MacOS Windows]

Closing this issue because it has been inactive for a while. If you think it should still be opened let us know why.


Improve resolution of callees in EtsApplicationGraph

This PR improves the resolution of callees in EtsApplicationGraph. In a perfect world, matching suitable methods by their signature would be enough, however in some cases the available signature is incomplete, e.g. enclosing class might be missing. In order to still be able to resolve such calls, we consequently try to resolve the (single) callee: first, by name only, and next, by name and class. If these lookups fail (for example, if there are still multiple methods with matching names and enclosing classes, which be in the case of a multi-file project), we simply fall-back to the default behavior and match by the whole signature. Overall, we still rely on the signature to uniquely represent a method.

This PR is not necessary anymore, sorry.