how to use gps to evaluation

Hi,
I want to use the gps provided by your data sets as the ground truth for evaluation, but its coordinate system and frequency are different from the system output, could you tell me how do you solve this? Thank you very much!

When you launch the system, there is one odometry published at odometry/gps, which is the transformed GPS coordinates in Cartesian space. You can use that for evaluation.

@TixiaoShan Hi,
Thanks for your answer. I have found the topic /odometry/gps, but it can't coincide with the system output. It seems that there is a rotation between /odometry/gps and system output. Besides, during running the system, the gps position changed suddenly. Could you tell me where is the problem? Thank you very much!

You can set the gpsTopic correctly to subscribe to it. The GPS data in the dataset is very bad. It jumps a few hundred meters will corrupt the optimization.

https://github.com/TixiaoShan/LIO-SAM/issues/8

I tried the package on Campus dataset(small). When not using GPS, the package performs very well.
Some results:

On comparing the GPS odometry with the optimized path, both look quite similar. The initial rotation seems to be the only difference between the two.
But when using GPS, there are some serious artifacts in the output PCD.
Some results:

Now I have the following questions:

Can we create correct(with least artifacts) global PCD map with LIO-SAM?
Any method for evaluating LIO-SAM? (I tried evaluating with KITTI ground truth sequences, the elevation data was inconsistent: [LINK)](https://github.com/TixiaoShan/LIO-SAM/issues/35#issuecomment-664587989. But this can be misleading since we don't have correct IMU parameters for KITTI.)
How well does LIO-SAM support car-like vehicles?


Test visualize function

Also auto-detect extension
Also, I had difficulty installing pygraphviz on my local machine.  I think that Dask moved to the graphviz library for this reason.

Yea I was thinking of conda packaging pygraphviz but libcgraph doesn't seem to have source code easily available. I'll move to the direct graphviz networkx interface.

I'm going to pull this in so I can finish the changes


MQTT port missing in profile.json

Hi,
I open this issue due to a unintended breaking change in the last version of HLC (HermesLedControl) : https://github.com/project-alice-assistant/HermesLedControl/issues/100
It's a great piece of code from @Psychokiller1888  to benefit of the LEDs on several board.
HLC last version change the MQTT port to reflect the one use by Rhasspy internal brocker (ie 12183).
To make configuration easy, HLC already get the MQTT external host in the profile.json, but... it may find also the MQTT port to be consistent.
Unfortunatly the MQTT port seems to be missing in the profile.json (whereas it's depicted in https://rhasspy.readthedocs.io/en/latest/reference/#profile-settings  :-)
Maybe a nice enhancement/fix to be considered.
Thanks

I had to search a lot to find out why HLC was not working - the missing port...

Rhasspy's web interface displays the default port number, but does not save it to profile.json unless it is changed. Rhasspy can use port 1883 or 12183 for MQTT depending on whether it's Internal or External, or whether Docker is used.
While Rhasspy works this out correctly, HLC sometimes guesses wrong.
It would make sense for MQTT port to explicitly be written to profile.json ... but it's also not hard to add it in the Advanced menu, as long as we tell people.

Rhasspy writes the settings that are different from defaults.json to the profile. The reasoning is that it lets me change the defaults over time (to get better performance, etc.) while allowing Rhasspy to keep the settings people have purposefully changed. The logic for this is all in rhasspy-profile.
You can use the /api/profile HTTP endpoint to get a complete profile with all of the settings.

Expected behaviour :)


Add DDL support for indices disabling

What changes were proposed in this pull request?
To enable disabling indices using DDL.
Note that only 1 index can be disabled at a time. For example, to disable indexA, indexB:
Two statements: Disable oindex indexA on table & Disable oindex indexB on table are needed.
Due to supporting of multiple indices disabling at a time will cause other queries' parse error.
How was this patch tested?
Test case in IndexSelectionSuite.
Out of date: Test is currently not added, due to this actually depend on PR#596.

can you add a test using the DDL?

@gczsjdy , we also want to ENABLE the index again after DISABLE. LIST all disabled index is also necessary.

LGTM. Merging.


Feedback

@bermannoah @epintozzi @NZenitram
Completes cards:

User can create feedback on a solution
User can see feedback on a solution
User can visit a form to edit their own feedback on a solution
User can update their own feedback
User cannot update feedback left by another user
User can delete their own feedback on a solution
User cannot view/leave feedback on another user's solution to an exercise unless they have submitted their own solution
Instructor feedback has flag by name

Still waiting on authorization to remove some of the logic from views. Merge when ready!

good2merge 🎉


Malcolm X interview not appearing online

This Malcolm X interview from Say Brother is featured in the "From the Vault" Special Collection, and on the AAPB website it appears as "available online at WGBH." But there is no proxy file associated with this asset on Open Vault, and there is no "Digitized" annotation that indicates that it should be online. Should this asset have a proxy file?
http://openvault.wgbh.org/catalog/V_7211FEA594634BC9B984B4AFA493D446
@Muraszko-wgbh

@caseyedavis12 That link to Malcolm X is the entire show.  Here is the record for the interview:
http://openvault.wgbh.org/catalog/V_FE25740F38E943A0986F93AD4A03E425
Must have been a mistake in the AAPB annotation?  Is the AAPB link the whole show or the clip?

@muraszko-wgbh: the AAPB link is to the Say Brother Malcolm X episode: http://americanarchive.org/catalog/cpb-aacip_15-r20rr1pv84

So was it digitized, and I assume LoC or WGBH viewable only.  You can probably just remove the link to Open Vault then.

@muraszko-wgbh: Since the Say Brother Malcolm X episode record on AAPB has a UOI ID, I think this program was downloaded from Artesia as part of the "born digital" phase. Since this record was part of the Pan African Liberation scholar exhibit and From the Vault, are we sure that it was never supposed to be made available online?
Both the Malcolm X Interview from Negro and the American Promise and the Say Brother Malcolm X episode are included in the From the Vault collection. I'm just doing a sampling and haven't found any other assets in the From the Vault collection that do not have media associated with the record.

@sroosa: can you remove the Outside URL annotation from this record: http://americanarchive.org/catalog/cpb-aacip_15-r20rr1pv84
Also, please change the Level of User Access annotation to On Location, and then please reindex.

Done when record appears on AAPB without link to Open Vault and metadata reflects that it is available to view On Location only.
Done


Adding cuda-cudart-dev to requirements/host?

It looks like cuda-cudart-dev is only included in requirements/run. Should it be in requirements/host as well?
https://github.com/conda-forge/cuda-nvcc-feedstock/blob/eb3b0973126c6d8c30cff6237f262cc8a8e7a9b3/recipe/meta.yaml#L39-L43

Suggested this fix ( https://github.com/conda-forge/cuda-nvcc-feedstock/pull/3#pullrequestreview-1392976293 ), which would resolve this issue if included


kernel: 4.5 -> 4.5.1

Things done

[X] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Looks like a nice and simple version bump. I'll test locally later on.

Already bumped that locally. :+1:


Error invalid syntax # on install

Bugs:

[x] Are you using the Python or MEL version? The MEL version is unsupported and only included as legacy.
Using the Phyton version

[x] Is this a bug or a workflow issue?
A bug

Filing a bug:

[x] Version of the Python script
3.0.0
[x] Short description of what is happening

After copying the .py and .png files to the corresponding folders and reestarting Maya, using the code:

import tweenMachine' 'tweenMachine.start()

results in the following error:

# Error: SyntaxError: file E:\Programas\Maya2022\Maya2022\Python37\lib\site-packages\shiboken2\files.dir\shibokensupport\__feature__.py line 142: invalid syntax #

[x] Expected result
Pluging succesfully installed

[x] Actual result
Installation error

[x] Steps to reproduce
Written in the Short description section

[x] Maya version
Maya 2022

A workaround is to init Maya 2022 with the argument:
-pythonver 2
There seem to be a fix waiting to be merged #35


Jaxlib 0.1.68 Fails to Build on Windows

With Python 3.8, Cuda 11.2, Bazel 4.1, build run with the following command
python .\build\build.py --enable_cuda --cuda_path="C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.2" --cudnn_path="C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.2" --cuda_compute_capabilities="7.5" --cuda_version="11.2" --cudnn_version="8.1.0" --noenable_rocm --noenable_tpu
results in the following error.

FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully
b"external/llvm-project/llvm/include\\llvm/Support/type_traits.h(79): warning C4624: 'llvm::detail::copy_construction_triviality_helper<T>': destructor was implicitly defined as deleted\r\n        with\r\n        [\r\n            T=std::string\r\n        ]\r\nC:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.29.30037\\include\\type_traits(631): note: see reference to class template instantiation 'llvm::detail::copy_construction_triviality_helper<T>' being compiled\r\n        with\r\n        [\r\n            T=std::string\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(100): note: see reference to class template instantiation 'std::is_copy_constructible<llvm::detail::copy_construction_triviality_helper<T>>' being compiled\r\n        with\r\n        [\r\n            T=std::string\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/ADT/SmallVector.h(311): note: see reference to class template instantiation 'llvm::is_trivially_copy_constructible<T>' being compiled\r\n        with\r\n        [\r\n            T=std::string\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/ADT/SmallVector.h(1167): note: see reference to class template instantiation 'llvm::SmallVectorImpl<T>' being compiled\r\n        with\r\n        [\r\n            T=std::string\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/Support/Error.h(992): note: see reference to class template instantiation 'llvm::SmallVector<std::string,2>' being compiled\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(86): warning C4624: 'llvm::detail::move_construction_triviality_helper<T>': destructor was implicitly defined as deleted\r\n        with\r\n        [\r\n            T=std::string\r\n        ]\r\nC:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.29.30037\\include\\type_traits(662): note: see reference to class template instantiation 'llvm::detail::move_construction_triviality_helper<T>' being compiled\r\n        with\r\n        [\r\n            T=std::string\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(111): note: see reference to class template instantiation 'std::is_move_constructible<llvm::detail::move_construction_triviality_helper<T>>' being compiled\r\n        with\r\n        [\r\n            T=std::string\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/ADT/SmallVector.h(311): note: see reference to class template instantiation 'llvm::is_trivially_move_constructible<T>' being compiled\r\n        with\r\n        [\r\n            T=std::string\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(79): warning C4624: 'llvm::detail::copy_construction_triviality_helper<T>': destructor was implicitly defined as deleted\r\n        with\r\n        [\r\n            T=tfrt::DebugInfo\r\n        ]\r\nC:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.29.30037\\include\\type_traits(631): note: see reference to class template instantiation 'llvm::detail::copy_construction_triviality_helper<T>' being compiled\r\n        with\r\n        [\r\n            T=tfrt::DebugInfo\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(100): note: see reference to class template instantiation 'std::is_copy_constructible<llvm::detail::copy_construction_triviality_helper<T>>' being compiled\r\n        with\r\n        [\r\n            T=tfrt::DebugInfo\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/ADT/Optional.h(53): note: see reference to class template instantiation 'llvm::is_trivially_copy_constructible<T>' being compiled\r\n        with\r\n        [\r\n            T=tfrt::DebugInfo\r\n        ]\r\nexternal/tf_runtime/include\\tfrt/host_context/location.h(83): note: see reference to class template instantiation 'llvm::Optional<tfrt::DebugInfo>' being compiled\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(79): warning C4624: 'llvm::detail::copy_construction_triviality_helper<T>': destructor was implicitly defined as deleted\r\n        with\r\n        [\r\n            T=std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>\r\n        ]\r\nC:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.29.30037\\include\\type_traits(631): note: see reference to class template instantiation 'llvm::detail::copy_construction_triviality_helper<T>' being compiled\r\n        with\r\n        [\r\n            T=std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(100): note: see reference to class template instantiation 'std::is_copy_constructible<llvm::detail::copy_construction_triviality_helper<T>>' being compiled\r\n        with\r\n        [\r\n            T=std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/ADT/SmallVector.h(311): note: see reference to class template instantiation 'llvm::is_trivially_copy_constructible<T>' being compiled\r\n        with\r\n        [\r\n            T=std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/ADT/SmallVector.h(1167): note: see reference to class template instantiation 'llvm::SmallVectorImpl<T>' being compiled\r\n        with\r\n        [\r\n            T=std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>\r\n        ]\r\nexternal/tf_runtime/include\\tfrt/support/error_util.h(255): note: see reference to class template instantiation 'llvm::SmallVector<std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>,4>' being compiled\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(86): warning C4624: 'llvm::detail::move_construction_triviality_helper<T>': destructor was implicitly defined as deleted\r\n        with\r\n        [\r\n            T=std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>\r\n        ]\r\nC:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.29.30037\\include\\type_traits(662): note: see reference to class template instantiation 'llvm::detail::move_construction_triviality_helper<T>' being compiled\r\n        with\r\n        [\r\n            T=std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(111): note: see reference to class template instantiation 'std::is_move_constructible<llvm::detail::move_construction_triviality_helper<T>>' being compiled\r\n        with\r\n        [\r\n            T=std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/ADT/SmallVector.h(311): note: see reference to class template instantiation 'llvm::is_trivially_move_constructible<T>' being compiled\r\n        with\r\n        [\r\n            T=std::unique_ptr<tfrt::BaseTypedErrorInfo,std::default_delete<tfrt::BaseTypedErrorInfo>>\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(79): warning C4624: 'llvm::detail::copy_construction_triviality_helper<T>': destructor was implicitly defined as deleted\r\n        with\r\n        [\r\n            T=tfrt::DecodedLocation\r\n        ]\r\nC:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.29.30037\\include\\type_traits(631): note: see reference to class template instantiation 'llvm::detail::copy_construction_triviality_helper<T>' being compiled\r\n        with\r\n        [\r\n            T=tfrt::DecodedLocation\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/Support/type_traits.h(100): note: see reference to class template instantiation 'std::is_copy_constructible<llvm::detail::copy_construction_triviality_helper<T>>' being compiled\r\n        with\r\n        [\r\n            T=tfrt::DecodedLocation\r\n        ]\r\nexternal/llvm-project/llvm/include\\llvm/ADT/Optional.h(53): note: see reference to class template instantiation 'llvm::is_trivially_copy_constructible<T>' being compiled\r\n        with\r\n        [\r\n            T=tfrt::DecodedLocation\r\n        ]\r\nexternal/tf_runtime/include\\tfrt/host_context/diagnostic.h(48): note: see reference to class template instantiation 'llvm::Optional<tfrt::DecodedLocation>' being compiled\r\nexternal/tf_runtime/include\\tfrt/host_context/async_value.h(455): error C2338: Unexpected size for AsyncValue\r\n"
Traceback (most recent call last):
  File ".\build\build.py", line 564, in <module>
    main()
  File ".\build\build.py", line 559, in main
    shell(command)
  File ".\build\build.py", line 52, in shell
    output = subprocess.check_output(cmd)
  File "C:\Users\Adam\anaconda3\envs\tensorflow\lib\subprocess.py", line 411, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "C:\Users\Adam\anaconda3\envs\tensorflow\lib\subprocess.py", line 512, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['C:\\bazel\\bazel.EXE', 'run', '--verbose_failures=true', '--config=short_logs', '--config=mkl_open_source_only', '--config=cuda', '--define=xla_python_enable_gpu=true', ':build_wheel', '--', '--output_path=C:\\sdks\\jax-jaxlib-v0.1.68\\dist']' returned non-zero exit status 1.

cross-ref #6637

We didn't actually fix windows build in between 0.1.66 and 0.1.68 due to limited bandwidth, but we did add something to the build script to print out the compilation error -- the long string starting with b"external/llvm-project...
I can now forward the compiler error messages to my TFRT coworkers and see if they can push a fix in TFRT codebase.

the actual error is that this static_assert failed
external/tf_runtime/include\tfrt/host_context/async_value.h(455): error C2338: Unexpected size for AsyncValue
The code is
// We only optimize the code for 64-bit architectures for now.
static_assert(sizeof(AsyncValue) == 16 || sizeof(void*) != 8,
              "Unexpected size for AsyncValue");

https://github.com/tensorflow/runtime/blob/master/include/tfrt/host_context/async_value.h#L455
@oracle3001 unfortunately we can't tell what values does sizeof(AsyncValue) and sizeof(void*) get. Can you tell us what you are seeing for these two values? You can checkout tfrt and just bazel build hostcontext
https://github.com/tensorflow/runtime/blob/master/BUILD#L113

I have built the runtime code. Where do I look for the sizeof(AsyncValue) and sizeof(void*) ?

The new error messages are for some other reasons...you can probably do just bazel build //:hostcontext since JAX doesn't depend on //tools: and get the exact same compilation error.
There might be a simpler way to check. Can you just run this C++ program?
$ cat sc.cc
#include
int main() {
printf("sizeof(void*)=%d\n", sizeof(void*));
}
$ make sc
g++     sc.cc   -o sc
$ ./sc
sizeof(void*)=8
This will help us distinguish sizeof(AsyncValue) == 16 || sizeof(void*) != 8. I suspect it's because sizeof(AsyncValue) != 16 on your machine.
It's likely that on Windows, AsyncValue struct layout isn't exactly the same as we expect on Linux.
I just remembered the issues in https://github.com/google/jax/issues/6637#issuecomment-855164868
If so, we might need a few iterations to fix this issue in TFRT codebase...

Let's also wait for this PR to land: https://github.com/tensorflow/runtime/pull/60
It should fix some of those Windows build issues due to TFRT

From creating the suggested test application.
"sizeof(void*)=8"

I have successfully produce a jaxlib whl with local tensorflow repo] of commit 8557ca660

FYI, jaxlib 0.1.69 now builds out the box for me.

@oracle3001 - How?
Which versions of python, CUDA cuDNN, bazel?
Which command line?
Thanks

@oracle3001 - How?
Which versions of python, CUDA cuDNN, bazel?
Which command line?
Thanks

Python 3.8, Cuda 11.2, cuDNN 8.1.0, Bazel 4.1
Run with the following build command.
python .\build\build.py --enable_cuda --cuda_path="C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.2" --cudnn_path="C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.2" --cuda_compute_capabilities="7.5" --cuda_version="11.2" --cudnn_version="8.1.0" --noenable_rocm --noenable_tpu

Thanks. I tried so many combinations, but here it always fails when trying to download a non-existing TF archive:
UnrecoverableHttpException GET returned 404 Not Found
followed by
ERROR: An error occurred during the fetch of repository 'local_config_cuda':
INFO: Found applicable config definition build:windows in file f:\projects\ai\jax\.bazelrc: --copt=/D_USE_MATH_DEFINES --host_copt=/D_USE_MATH_DEFINES --copt=-DWIN32_LEAN_AND_MEAN --host_copt=-DWIN32_LEAN_AND_MEAN --copt=-DNOGDI --host_copt=-DNOGDI --copt=/Zc:preprocessor --cxxopt=/std:c++14 --host_cxxopt=/std:c++14 --linkopt=/DEBUG --host_linkopt=/DEBUG --linkopt=/OPT:REF --host_linkopt=/OPT:REF --linkopt=/OPT:ICF --host_linkopt=/OPT:ICF --experimental_strict_action_env=true
WARNING: Download from http://mirror.tensorflow.org/github.com/tensorflow/runtime/archive/d29d1ef0a65a8f9c23e1f88067ce4205d3085e87.tar.gz failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException GET returned 404 Not Found
INFO: Repository local_config_cuda instantiated at:
  F:/projects/ai/jax/WORKSPACE:30:10: in <toplevel>
  C:/users/admin/_bazel_admin/avp2whpv/external/org_tensorflow/tensorflow/workspace2.bzl:1085:19: in workspace
  C:/users/admin/_bazel_admin/avp2whpv/external/org_tensorflow/tensorflow/workspace2.bzl:90:19: in _tf_toolchains
Repository rule cuda_configure defined at:
  C:/users/admin/_bazel_admin/avp2whpv/external/org_tensorflow/third_party/gpus/cuda_configure.bzl:1448:33: in <toplevel>
ERROR: An error occurred during the fetch of repository 'local_config_cuda':
   Traceback (most recent call last):
        File "C:/users/admin/_bazel_admin/avp2whpv/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1401, column 38, in _cuda_autoconf_impl
                _create_local_cuda_repository(repository_ctx)
        File "C:/users/admin/_bazel_admin/avp2whpv/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 1239, column 56, in _create_local_cuda_repository
                host_compiler_includes + _cuda_include_path(
        File "C:/users/admin/_bazel_admin/avp2whpv/external/org_tensorflow/third_party/gpus/cuda_configure.bzl", line 364, column 32, in _cuda_include_path
                inc_entries.append(realpath(repository_ctx, cuda_config.cuda_toolkit_path + "/include"))
        File "C:/users/admin/_bazel_admin/avp2whpv/external/org_tensorflow/third_party/remote_config/common.bzl", line 290, column 19, in realpath
                return execute(repository_ctx, [bash_bin, "-c", "realpath \"%s\"" % path]).stdout.strip()
        File "C:/users/admin/_bazel_admin/avp2whpv/external/org_tensorflow/third_party/remote_config/common.bzl", line 230, column 13, in execute
                fail(
Error in fail: Repository command failed
realpath: 'C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.2/include': No such file or directory
ERROR: Error fetching repository: Traceback (most recent call last):

The TF archive download failure is a warning and benign. Ignore it.
The issue is probably related to not finding your CUDA toolkit, which is the fatal error above.

Thanks @hawkinsp, I figured it out: I've been re-using an existing MSYS2 installation which seems to have some conflicting configuration. Installed a fresh MSYS2 and it's building now!
Thanks a lot for your assistance (to both of you)!

@oracle3001 Could you upload the jaxlib.whl file from you last successful build?
Thanks!

Hi guys,
I saw @oracle3001 succefully build the jaxlib with python 3.8, cuda v11.2, cudnn v8.1.
I suspect this is due to the gcc and g++ version from msys2.
If we check the gcc version from msys2 or cmd. We found out that the gcc version show is v10.
I tried install cuda in ubuntu too, with cuda v10.1, cudnn v7.6.5.
I remember the gcc and g++ version must be v8.
It will have error when gcc & g++ version larger than 8.
So I suspect this is the issue if someone try to build jaxlib with cuda v10.1, cudnn v7.6.5 will fail due to incompatible gcc & g++ version.
Maybe cuda v11.2, cudnn v8.1 are running fine with gcc & g++ version 10.
This is my hypothesis only.
Can any experts please verify whether what I claim is correct or wrong?
Is there a ways to install specific version of gcc and g++ in msys2?
I checked and it seems like msys2 didn't keep many archieve.
Thank you very much.

Hi @oracle3001 ,
May I know did you solved the failed to build error at the end?
Thank you very much

@GMCobraz can you share the complete logs from your build?
Note that gcc versions are irrelevant on Windows; JAX should be built with MSVC, per the instructions (https://jax.readthedocs.io/en/latest/developer.html#additional-notes-for-building-jaxlib-from-source-on-windows).

Hi @hawkinsp ,
Good day.
Here attached with my error log.

I built JAX with MSVC, but not sure why it still fail
Please help. thanks.

@GMCobraz Windows is not an officially supported platform (at least currently), so you should not expect support from them. This PR should resolve you problem.

I was trying to set up third party CI for windows build, but lack for compute resource now.
The following are try-out builds last weekend, manually.
CUDA 10.1
contains fix from the previously mentioned PR
https://whls.blob.core.windows.net/cuda101/jaxlib-0.1.70+cuda101-cp37-none-win_amd64.whl
https://whls.blob.core.windows.net/cuda101/jaxlib-0.1.70+cuda101-cp38-none-win_amd64.whl
https://whls.blob.core.windows.net/cuda101/jaxlib-0.1.70+cuda101-cp39-none-win_amd64.whl
CUDA 11.2
https://whls.blob.core.windows.net/cuda112/jaxlib-0.1.70+cuda112-cp37-none-win_amd64.whl
https://whls.blob.core.windows.net/cuda112/jaxlib-0.1.70+cuda112-cp38-none-win_amd64.whl
https://whls.blob.core.windows.net/cuda112/jaxlib-0.1.70+cuda112-cp39-none-win_amd64.whl
If you trust me, use it. Otherwise, leave alone.

Hi @cloudhan ,
Thanks for the reply.
Once I downloaded the .whl file, I can proceed with numpyro v0.7.1 installation right?
May I have the jaxlib-0.1.62+cuda101-cp37-none-win_amd64.whl?
Cause I will need it to install with numypro v0.6.0 and jax v0.2.10.
Thank you very much

You can try it out, that is, new version jaxlib + old version jax, not sure will it works.

I believe this issue is already resolved. Closing. Feel free to open new issues for new problems. Thanks for all the help everyone!


Write "How to define a new plan and performer type" guide

Objective-C equivalent guide: https://github.com/material-motion/material-motion-runtime-objc#how-to-create-a-new-plan-and-performer-type

Fixed in http://codereview.cc/D1791


Nulled/fix web throttling

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.01%. Comparing base (7faca7c) to head (4180317).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #370      +/-   ##
==========================================
- Coverage   66.15%   66.01%   -0.15%
==========================================
  Files         155      155
  Lines        9985     9985
==========================================
- Hits         6606     6592      -14
- Misses       3379     3393      +14

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Incorrect ROM file - No valid ROMs were provided (Verified Checksums)

[x] I have checked the known issues and searched Github to ensure this issue has not already been reported.
[x] This is not a feature request, I know those belong on Discord/Github Discussions.

Description of the bug:

Can you reproduce? If so please list the steps:

[x] Yes, here are the steps to reproduce the bug:

In my case, I compiled from source then had the following in a folder: 2s2h.sh 2s2h.elf gamecontrollerdb.txt 2s2hIcon.png
cd to the folder containing these items via terminal (in my case, extracted from a zip archive)
Run ./2s2h.sh
Encounter the strange behavior (on a first attempt, it may look fine but you'll notice there's only a mods folder; subsequent attempts show the described behavior below)

Expected behavior:

When running the Linux launch script, the Zenity pop-up claims that no valid rom was found and yet also attempts to generate an OTR in a seperate window regardless before eventually closing itself. Additionally, only the mods folder ever seems to get created and I never find the temp directory that's supposed to be made in /tmp despite having user permissions to do so.
Screenshots or videos:

System Information:

OS: x86_64 Gentoo Linux 2.15 (Kernel 6.8.9)
GFX Backend: OpenGL
Game Version: 1.0.2 (LLVM Compiled 57cb5d2b5135a1cbc88ea9a4a94990fba291a11a)
Rom Version: Both NTSC-U and NTSC-U GC

Additional Information:

Shell Output:
cp: cannot stat '/tmp/assets-WRXTD/mm.o2r': No such file or directory
Warning: --window-icon is deprecated and will be removed in a future version of zenity; Treating as --icon.
Warning: --icon-name is deprecated and will be removed in a future version of zenity; Treating as --icon.

(zenity:19440): Gtk-WARNING **: 00:22:00.845: Unknown key gtk-modules in /home/neko/.config/gtk-4.0/settings.ini

(zenity:19444): Gtk-WARNING **: 00:22:00.847: Unknown key gtk-modules in /home/neko/.config/gtk-4.0/settings.ini

(zenity:19440): Adwaita-WARNING **: 00:22:00.909: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

(zenity:19444): Adwaita-WARNING **: 00:22:00.910: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

Hi, are you still encountering this problem?
I think in this case what you are missing is the compiled ZAPD.out binary and the assets folder that contains all the xml files for extraction. Without this, the 2s2h.sh script won't be able to generate an mm.o2r properly. The script is provided as-is and assumes that it is running from the appimage. You can refer to our CMake and CPack steps to see how we are bundling the final appimage.

I'm going to close this issue as stale. If you are still having trouble with whatever you are trying to do, feel free to reach out in our Discord for help.


Wayland: Editor crashes trying to load any project.

Tested versions

Reproducible in Godot 4.3 dev 3

System information
Ubuntu 22.04.3 LTS using Wayland.
Issue description
If configured to use Wayland, the editor crashes when trying to load any project. It works as usual when using x11.
The console output is:
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.3.dev3.official (36e943b6b20cb7a8a89bc30489c4a81c3e149d74)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
 Create a new project and try to load it.
Minimal reproduction project (MRP)
N/A

Thanks for the report.
Could you give a bit more detail on the exact command you run to start Godot, and how you then load the project?
If you run Godot with Godot_v4.3-dev3_linux.x86_64 --display-driver wayland, it should indeed run the project manager with Wayland. But then opening a project from the project manager would actually start an X11/xwayland process, unless you enabled the option to prefer Wayland in the editor (yes it's quirky, we'll improve that eventually).
So it's important to figure out if it's actually trying to open the editor with X11 or Wayland when it crashes.
The stacktrace is also a bit weird as it involves both the OpenGL and Vulkan drivers for your Nvidia GPU. If you're able to compile Godot from source, you could try to compiling with scons dev_build=yes to ensure that you'll get debug symbols, which should give us a better stacktrace.

This had been happening to me for a few months until a day or two ago, though I'm using Kubuntu 23.10 and it only started happening when I switched to it. What seems to have fixed it is the most recent kernel update, at least I haven't seen it since then.
This bug also affected my custom engine (OpenGL) application as well, and in both cases, my whole PC sometimes ended up freezing up. The screen would switch on and off and usually, if I waited long enough, KDE would kind of crash but still be somewhat active (enough that I could either restart the device or restart Kwin through the terminal). But yeah, sometimes it would completely freeze up.
And it wasn't even Nvidia, but an AMD APU (Ryzen 5500U).

Thanks for the report.
Could you give a bit more detail on the exact command you run to start Godot, and how you then load the project?
If you run Godot with Godot_v4.3-dev3_linux.x86_64 --display-driver wayland, it should indeed run the project manager with Wayland. But then opening a project from the project manager would actually start an X11/xwayland process, unless you enabled the option to prefer Wayland in the editor (yes it's quirky, we'll improve that eventually).
So it's important to figure out if it's actually trying to open the editor with X11 or Wayland when it crashes.
The stacktrace is also a bit weird as it involves both the OpenGL and Vulkan drivers for your Nvidia GPU. If you're able to compile Godot from source, you could try to compiling with scons dev_build=yes to ensure that you'll get debug symbols, which should give us a better stacktrace.

The editor crashes when configured with the option to run Wayland enables in the settings. When enabling the option the editor is asked to restart. However it never re-stars as it crashes trying to load the project. As for your explanation, the project manager does not crash neither using x11 nor Wayland. To summarize, the project loader does not crash. But the editor crashes trying to load the project when configured to use Wayland.

I see that you're using an LTS version of Ubuntu, so that might be it. I would try to reproduce this issue on a more bleeding-edge distro with the latest everything.

Tried on an updated version of arch, opened the project both from the command line directly and through setting the wayland preference flag in the editor settings, got the follow error with both attempts:
ERROR: Condition "err != VK_SUCCESS" is true. Returning: ERR_CANT_CREATE
   at: swap_chain_resize (drivers/vulkan/rendering_device_driver_vulkan.cpp:2665)
ERROR: Unable to resize the new swap chain.
   at: screen_create (servers/rendering/rendering_device.cpp:3157)
ERROR: Screen was never prepared.
   at: screen_get_framebuffer_format (servers/rendering/rendering_device.cpp:3226)
ERROR: Screen was never prepared.
   at: screen_get_framebuffer_format (servers/rendering/rendering_device.cpp:3226)
ERROR: Screen was never prepared.
   at: screen_get_framebuffer_format (servers/rendering/rendering_device.cpp:3226)
ERROR: Screen was never prepared.
   at: screen_get_framebuffer_format (servers/rendering/rendering_device.cpp:3226)

ERROR: A swap chain was not created for the screen.
   at: screen_prepare_for_drawing (servers/rendering/rendering_device.cpp:3168)
ERROR: Screen was never prepared.
   at: draw_list_begin_for_screen (servers/rendering/rendering_device.cpp:3272)
ERROR: Parameter "dl" is null.
   at: draw_list_bind_render_pipeline (servers/rendering/rendering_device.cpp:3538)
ERROR: Parameter "dl" is null.
   at: draw_list_bind_index_array (servers/rendering/rendering_device.cpp:3690)
ERROR: Parameter "dl" is null.
   at: draw_list_bind_uniform_set (servers/rendering/rendering_device.cpp:3625)
ERROR: Parameter "dl" is null.
   at: draw_list_set_push_constant (servers/rendering/rendering_device.cpp:3728)
ERROR: Parameter "dl" is null.
   at: draw_list_draw (servers/rendering/rendering_device.cpp:3748)
ERROR: Immediate draw list is already inactive.
   at: draw_list_end (servers/rendering/rendering_device.cpp:3943)
ERROR: A swap chain was not created for the screen.
   at: screen_prepare_for_drawing (servers/rendering/rendering_device.cpp:3168)

System Information
OS: EndevourOS x86_64
Kernel: 6.8.5-arch1-1
GPU: NVIDIA MX450 (and integrated intel)


Add the possibility of ignoring the allowed_resources control

If the allowed_resources is not present in the JWT, it produce this error:
KeycloakGuard\Exceptions\ResourceAccessNotAllowedException: [Keycloak Guard] The decoded JWT token has not a valid resource_access allowed by API. Allowed resources by API:  in file /var/www/html/vendor/robsontenorio/laravel-keycloak-guard/src/KeycloakGuard.php on line 169
It can be really usefull if you want to manage your roles in the app and be more flexible to change the auth keycloak realm for example.
Also, some keycloak realm that you need to be authenticated don't give this param and it's a problem for the package.

Resolved by #77


How does "-m glob" work?

I have benchmarks named things like decode/1kb normal (Vector Int32), etc.  I am familiar with using -m with hspec.    I'd find this very useful.  Ideally it would be the default so that people can use the same matching syntax as with hspec.
In lieu of substring matching, I tried using glob with -m glob *normal*, but it didn't match any benchmarks.  I also tried -m glob '*normal*', but no such luck :(

Yeah, we just use whole names, and come to think of it I'm not sure how/if the glob matching works either.

Glob matching is implemented by the Glob library, which you can find documented here; http://hackage.haskell.org/package/Glob-0.7.13/docs/System-FilePath-Glob.html . Globbing on the benchmarks works as though they were filepaths (I'll bet that's why bos chose to use "/" as the separator), so you need to be mindful of the "matches all except the path separator" mentions there. I don't fully grok it yet, but have been able to do things like:
» dist/build/bench-realistic/bench-realistic -m glob "**/Text**/*"
benchmarking Text/strict/5/siphash64_1_3
...

» dist/build/bench-realistic/bench-realistic -m glob "**/siphash***/*"
benchmarking ByteString/strict/5/siphash64_1_3
...

Thanks @jberryman !  I indeed didn't realize that * wouldn't match the /.


List of all installed Plugins

I wonder how can I see list of ALL installed plugins? It may be quite annoying when u try to find concrete installed plugin from at the whole list.

@werediver it's already implemented in master

Thanks, everybody!

is this filter visible yet? I dont see it :crying_cat_face:

@wfalkwallace have you built from master ?

no - I guess I need to for this feature then... I'll do that.

So, is it done? How to update Alcatraz itself?


Schema validation for 'backupManagementType' is incorrect

When templating the deployment of Microsoft.RecoveryServices/vaults/backupPolicies types, with 2016-12-01 as API version, the values for property backupManagementType are not properly recognized.
The full explanation for that property is somehow missing from the 2016-12-01 API version page:
https://docs.microsoft.com/en-us/azure/templates/microsoft.recoveryservices/2016-12-01/vaults/backuppolicies
However, it can be found in the 2016-06-01 API version page:
https://docs.microsoft.com/en-us/azure/templates/microsoft.recoveryservices/2016-06-01/vaults/backuppolicies
Details for the backupManagementType are as follows:

Name
Type
Required
Value

backupManagementType
string
Yes
This property will be used as the discriminator for deciding the specific types in the polymorphic chain of types. - AzureWorkload, AzureStorage, AzureIaasVM, AzureSql, GenericProtectionPolicy, MAB

However, the only value recognized by the ARM Tools schema validation is AzureStorage, as seen in the following screenshot:

Any other valid value (such as AzureIaasVM) entered for that property is received with a warning, as seen in the screenshot above. That is not a big issue, but for developers aiming to have code that is clean and free of warnings, it may be a nuisance.
More info on that specific schema can be found here:
https://schema.management.azure.com/schemas/2016-12-01/Microsoft.RecoveryServices.json#/resourceDefinitions/vaults_backupPolicies

Same issue with protectedItemType when deploying Microsoft.RecoveryServices/vaults/backupFabrics/protectionContainers/protectedItems types with 2016-12-01 as API version. The ARM Tool schema validation says the value for that property must be AzureIaasVMProtectedItem, but it actually can be a range of different values.

@RaphaelFrancisco Are you using the latest root schema ($schema value at top of template)? If not, try updating to https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json# I'm not able to recreate this, but I may be missing something...

No warnings using AzureIaasVM:

Note: It looks like Microsoft.RecoveryServices RP schema is not yet set up for autogeneration: https://github.com/Azure/azure-resource-manager-schemas/pull/1229
An explanation can be found here: https://github.com/Azure/azure-resource-manager-schemas/wiki/Unrecognized-Resource-API-Version

@RaphaelFrancisco Are you using the latest root schema ($schema value at top of template)? If not, try updating to https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json# I'm not able to recreate this, but I may be missing something...

No warnings using AzureIaasVM:

Note: It looks like Microsoft.RecoveryServices RP schema is not yet set up for autogeneration: https://github.com/Azure/azure-resource-manager-schemas/pull/1229
An explanation can be found here: https://github.com/Azure/azure-resource-manager-schemas/wiki/Unrecognized-Resource-API-Version

@MarcusFelling thanks for taking the time to look into this. Yes, I am using the latest root schema (2019-04-01), but somehow I still see this issue. Values other than "AzureStorage" are not recognized as valid ones and a warning is thrown.
Other than the root schema, is there any other variable that may be responsible for the behavior I am seeing?
My ARM Tools is v0.14.0, that is the latest, right? Not sure whether this is relevant though.

@MarcusFelling thanks for taking the time to look into this. Yes, I am using the latest root schema (2019-04-01), but somehow I still see this issue. Values other than "AzureStorage" are not recognized as valid ones and a warning is thrown.
Other than the root schema, is there any other variable that may be responsible for the behavior I am seeing?
My ARM Tools is v0.14.0, that is the latest, right? Not sure whether this is relevant though.

@RaphaelFrancisco Can you post a small template that repros this?  Thx.

@RaphaelFrancisco Can you post a small template that repros this?  Thx.

I still see this issue with the following single-resource template:
{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "<IP_ADDRESS>",
    "parameters": {
        "rvName": {
            "type": "string"
        }
    },
    "resources": [
        {
            "apiVersion": "2016-12-01",
            "type": "Microsoft.RecoveryServices/vaults/backupPolicies",
            "name": "[concat(parameters('rvName'), '/DailyPolicy')]",
            "properties": {
                "backupManagementType": "AzureIaasVM",
                "timeZone": "UTC",
                "schedulePolicy": {
                    "scheduleRunFrequency": "Daily",
                    "schedulePolicyType": "SimpleSchedulePolicy",
                    "scheduleRunTimes": [
                        "13:00"
                    ]
                },
                "retentionPolicy": {
                    "retentionPolicyType": "LongTermRetentionPolicy",
                    "dailySchedule": {
                        "retentionDuration": {
                          "count": 180,
                          "durationType": "Days"
                        },
                        "retentionTimes": [
                            "13:00"
                        ]
                    }
                }
            }
        }
    ]
}

Here is an image showing the yellow squiggly line characteristic of the warning:

I still see this issue with the following single-resource template:
{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "<IP_ADDRESS>",
    "parameters": {
        "rvName": {
            "type": "string"
        }
    },
    "resources": [
        {
            "apiVersion": "2016-12-01",
            "type": "Microsoft.RecoveryServices/vaults/backupPolicies",
            "name": "[concat(parameters('rvName'), '/DailyPolicy')]",
            "properties": {
                "backupManagementType": "AzureIaasVM",
                "timeZone": "UTC",
                "schedulePolicy": {
                    "scheduleRunFrequency": "Daily",
                    "schedulePolicyType": "SimpleSchedulePolicy",
                    "scheduleRunTimes": [
                        "13:00"
                    ]
                },
                "retentionPolicy": {
                    "retentionPolicyType": "LongTermRetentionPolicy",
                    "dailySchedule": {
                        "retentionDuration": {
                          "count": 180,
                          "durationType": "Days"
                        },
                        "retentionTimes": [
                            "13:00"
                        ]
                    }
                }
            }
        }
    ]
}

Here is an image showing the yellow squiggly line characteristic of the warning:

@RaphaelFrancisco Thanks for bringing this to our attention!  We've ported to bug to the Azure schemas repo.


Can't seem to use probot-config in tests

What
I can't seem to be able to mock probot-config in order to fix the tests

Ah, finally found an example that works https://github.com/probot/autolabeler/blob/master/test/index.test.js


Vitest + Coverage

In current main branch, when generating app, using React or Svelte, the coverage is well displayed.
Anyway, if the coverage is under some value, there is no error output, so the mvn clean verify is success, and it should not

it was detected by https://github.com/jhipster/jhipster-lite/pull/3866

cc @qmonmert

@pascalgrimaud we can close this ticket?

yes !


Readme fixes.

Thank you

@kukabi thank you for your contribution! Can you please update your branch to be up-to-date with dev so we can merge it

My pleasure @valentunn, it should be rebased now.


[WIP] add training_data field to upload form

dublicate PR to https://github.com/FynnBe/bioimage.io/pull/4

netlify build fails on fork: https://github.com/FynnBe/bioimage.io/pull/4#issuecomment-1054211562

after having signed up with netlify, also a fresh PR can't trigger the test build: https://github.com/bioimage-io/bioimage.io/pull/245#issuecomment-1054215949

To make this work, we will need to also implement the logic for automatically extracting the dataset so we make sure every dataset is selectable.


Having a GPU CI agent

How do I have a GPU buildkite agent using GKE? What are the configuration steps needed for that?

Hy @RajathSwaroop! We don't have a specific tutorial for GPU, but we have users that set it up with no issue.
You can check out the section in our docs on how to run the agent on Google Kubernetes Engine
Maybe you can find this example useful: https://github.com/JuliaGPU/buildkite Julia wrote all their experience on configuring Buildkite.
Thanks!


Open New Note in New Pane

Hi. Love the plugin. Is there anyway you can add an option to open the new note in a new pane, and focus on the pane?

Hi @anoriginalmoniker,
thank you for the feedback and the feature request.
This sounds useful, will work on it.

Thank you for this plug-in, @marcjulianschwarz ! +1 on this request. When I add a new podcast note, I intend to start taking notes on it, so it would be helpful to have the newly created note in focus/edit mode.


No Mobile or EXE

Add it

we're not adding mobile port if you keep telling us

we're not adding mobile port if you keep telling us

💀

we're not adding mobile port if you keep telling us

💀

get a PC for once :moyai:


bug: Incomplete Pod for KubeFlex

Describe the bug
I am trying to get everything set for Kubernetes but I am having trouble setting up KubeFlex. I need all 3 of my pods running to continue with downloding Kubeflex and 1/3 of my pods constantly says it's running and not completed.
Steps To Reproduce

Expected Behavior
My overall expected outcome is to create a Kubernetes cluster for Kubeflex and then continue the rest of the steps of the Getting Started guide on Kubestellar that requires Kubeflex. In order to do this, I need all 3 of my pods running for the Nginx Ingress Controller to be fully set up. I have tried accessing the ingress-nginx namespace to delete the pod and have a new one created, only for the same result to keep saying "running".
Additional Context
No response

Hi @milanahrae could you please provide more details on your environment - OS, memory, CPU, docker version, kind version? At first sight, it seems that there might not be enough resources in your system.

Hi @milanahrae could you please provide more details on your environment - OS, memory, CPU, docker version, kind version? At first sight, it seems that there might not be enough resources in your system.

This is what I have.

@milanahrae seems like you may have enough resources, however, based on your screenshot above, it looks like the check_pre_req.sh fails for KubeFlex. Did you go over https://docs.kubestellar.io/release-0.24.0/direct/pre-reqs/ to install all pre-reqs?
It is normal to see those 2 pods (ingress-nginx-admission-create-rhh2c and ingress-nginx-admission-patch-jf42w) as completed (these are created by 2 jobs - ingress-nginx-admission-create and ingress-nginx-admission-patch). As for the 3rd one, that should stay in running state as that is a controller, and controllers in Kubernetes are long-running.  It may take some time (up to 120 s) for that pod to get to 'READY' (the row for ingress-nginx-controller-xxx-xxx should show 1/1 for the READY column) - does it ever gets to that state ?
If not, could you please show the logs for that controller pod (if you restarted the install, that name may have changed)
kubectl logs -n ingress-nginx ingress-nginx-controller-dcf8d6f6d-4p4fb

@milanahrae : you are welcome. Closing the issue.


Clientvalidation for numbers with decimals are wrong, when using comma as separator

Apparently the Client validation, used by the MVC system, doesn't support comma as separator for decimals.
Unfortunately, the browser does, which results in being unable to enter values correctly.
Values are displayed correctly (with a comma), but validation rejects the value, when saving.

Definition in the datamodel:
public decimal Price { get; set; }
I've tried Edge, Firefox and Chrome - same issue for all.
It's an annoying problem, that makes it difficult to create otherwise simple pages

@ClausSuperusers ?

Sorry about the first version - was confused by the layout....

https://stackoverflow.com/a/48247324/8778560

@SIkebe You are right, this IS a third party problem, BUT the MVC template applies this by default, effectively making a simple task quite a lot more difficult, for a lot of people.
Microsoft has made a lot of nice work, in order to support different cultures, but unfortunately missed this one.

Thanks for contacting us. We're closing this issue as there was no community involvement here for quite a while now.


Add containerized build for Linux-based development

This uses a Fedora-based container image to build the application
It defaults to Podman:
$ make containerized

or to use Docker
$ CONTAINER_RUNTIME=docker make containerized

The binaries are copied to the ./bin folder as expected from a regular build

Screenshot of this working:

Note: binaries can be invoked locally, but have also been tested on the actual host.

I wondered why it wasn't published as a single file as the csproj explicitly specifies this...
$ cp ./bin/Release/net5.0/win-x64/publish/\$.exe /mnt/c/Users/gbraad/.local/bin/\$.exe

... because I was using the wrong file; the unpublished one. Here you can see it works:

Looks great, thanks!


Fix issue #67: Optionally add HttpHeaders parameter in methods

Proposal to fix issue #67. The approach used for testing is quite brutal (basically copy/paste of existing tests). Let me know if there is a better way.

Imho copy pasting test is better than having conditional tests.

Except my comment on paramsRule the code looks fine to me. You'll become the pr king of the month :)

Thanks for your comment. Code is far cleaner like this.

Thanks for taking the time to implement and review this @tofcoder @aweisser
I have only 2 points:

We need to also Update the README.md to reflect the new configuration parameter in the Mojo
My initial concern is that we are adding this injection variable in the model at an action level (ApiActionMetadata), when currently is only configurable globally. I don't mind starting off like this but if we see that we are not going to add features to control this in a more fine grained way (eg, only show headers for certain resources/calls) then we need to move it outwards, at least to the ResourceLevel, or even better make the MethodParamRule a ConfigurableRule and then pass it in as a parameter

Any thoughts before i merge this?

@kurtpa Would be nice to have a new release on Maven Central that includes this change, and the other expected features and bug fixes.

definitely - on my todo list for today :)


Paging only visible when total number of rows > number of rows per page

Is there a way to make the paging visible only when total number of rows > number of rows per page ?

hi @clemorphy you could achieve this by using TableFilter's API, I'll get back with an example.
cheers


Shift Method

I have started to contribute and noticed that there is no page for the Shift method in the Array category on documentation.
Please update it.

The repo with the documentation is the following: https://github.com/rayepps/radash-docs

The repo with the documentation is the following: https://github.com/rayepps/radash-docs

Check this out https://radash-docs.vercel.app/docs/getting-started

Yes, I've seen it is missing.
What I meant is open the issue on the docs repo instead of here
Cheers

Yes, I've seen it is missing. What I meant is open the issue on the docs repo instead of here
Cheers

Do you have any information about the implementation of documentation?
I have several questions about that.

Unfortunately, I have no info on that. For details related to the documentation wait for @rayepps

I'm currently working on new docs that are simpler to manage and live in the radash repo.
Until then, if you wanted to add a shift page to the docs app you're looking for the src/pages/docs directory to add a new docs page and the src/navs/documentation.js file to add that page to the sidebar.

I'm currently working on new docs that are simpler to manage and live in the radash repo.
Until then, if you wanted to add a shift page to the docs app you're looking for the src/pages/docs directory to add a new docs page and the src/navs/documentation.js file to add that page to the sidebar.

Sure, I will do that


Update puma config

This is needed for when our apps are re-platformed to Kubernetes and are run on puma in production.
A similar change has been made to Collections in this PR

The code change looks good.
However you've got a rogue .DS_Store file in here.
You can configure your machine to ignore all .DS_Store files (for reference we use .gitignore file in repos to only ignore files created by codebase not those on local dev machines) as an example: https://stackoverflow.com/questions/7335420/global-git-ignore
For me I have a file ~/.gitignore_global which has contents of:
.DS_Store
.byebug_history

and then I add that globally with git config --global core.excludesFile '~/.gitignore_global'

Ah yes, I didn't see that. Thanks Kevin. I've updated it now to exclude the .DS_Store file and set up a global ignore on my machine.


weird issue occuring after deployment to pother environment

I have the following Route

.EnableSwaggerUi("documentation/{*assetPath}", c =>

Which works perfectly on my machine, no problems at all.
But when I deploy to our test environment - I get the following message

500 : { "Message": "An error has occurred." } /api/swagger/docs/v1

The deployment is to default web site/api
Any help as to why this happens?

Which works perfectly on my machine, no problems at all.
But when I deploy to our test environment - I get the following message
 500 : { "Message": "An error has occurred." } /api/swagger/docs/v1
The deployment is to default web site/api
Any help as to why this happens?

Same error for me as well when I deployed the API project to server. Locally it works perfect.
On the server, I checked that XmlComments.xml file is not getting generated in my case. I am still looking for the actual cause.

I can't really help here without additional information. Can you provide the full stack trace for the exception?

There is no exception. The header is just not added when pressing "try it out"  so the api returns a 401 on all responses. Checked fiddler and other inspectors.
On Tue, Jan 26, 2016 at 9:35 AM -0800, "domaindrivendev"<EMAIL_ADDRESS>wrote:
I can't really help here without additional information. Can you provide the full stack trace for the exception?
—
Reply to this email directly or view it on GitHub.

It was my fault all along, I had not named my security scheme uniformly..

Hi... I have the same problem.
What did you mean by "It was my fault all along, I had not named my security scheme uniformly.."  ? @VisualBean  ?


[ISSUE #2024] Enhance the ability of cryptor plugin

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #2118 (401ca64) into master (5bae6f7) will decrease coverage by 0.05%.
The diff coverage is 64.44%.

@@             Coverage Diff              @@
##             master    #2118      +/-   ##
============================================
- Coverage     59.84%   59.78%   -0.06%
- Complexity     4030     4037       +7
============================================
  Files           613      612       -1
  Lines         18146    18151       +5
  Branches       1738     1739       +1
============================================
- Hits          10859    10852       -7
- Misses         6408     6417       +9
- Partials        879      882       +3

Impacted Files
Coverage Δ

...e/shenyu/plugin/cryptor/dto/CryptorRuleHandle.java
35.29% <44.44%> (ø)

...plugin/cryptor/response/CryptorResponsePlugin.java
59.37% <57.14%> (-9.20%)
:arrow_down:

...u/plugin/cryptor/request/CryptorRequestPlugin.java
58.82% <60.00%> (+1.68%)
:arrow_up:

...lugin/cryptor/strategy/CryptorStrategyFactory.java
40.00% <60.00%> (+3.63%)
:arrow_up:

...g/apache/shenyu/plugin/cryptor/utils/HttpUtil.java
44.44% <66.66%> (+17.77%)
:arrow_up:

...yptor/handler/CryptorRequestPluginDataHandler.java
70.00% <100.00%> (ø)

...ptor/handler/CryptorResponsePluginDataHandler.java
70.00% <100.00%> (ø)

...g/apache/shenyu/plugin/cryptor/utils/JsonUtil.java
61.22% <100.00%> (+15.39%)
:arrow_up:

...ache/shenyu/client/tars/common/dto/TarsRpcExt.java
0.00% <0.00%> (-30.77%)
:arrow_down:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
70.58% <0.00%> (-23.53%)
:arrow_down:

... and 6 more

Continue to review full report at Codecov.

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


Using a different loss function than MSE

I am using Lassonet for my thesis, but I want to do so with a quantile loss function instead of Mean Squared Error. After going through the code and found a variable self.criterion set to MSE loss by default (interfaces.py, class LassoNetRegressor, line 566). After instantiating the class, I manually changed it self.criterion = quantile loss and trained the lassonet.
However, the loss didn't converge and remains high even after several epochs and the train assertion becomes false and it exits with error line 316, interfaces.py.
Can someone suggest a solution?

Can you print the full error message? In particular give the full traceback so that we can know whether it's a dense model or not.
How did you implement quantile loss?
Does a simple MLP work correctly?

The quantile loss is defined as follows:
def qloss(preds:torch.Tensor, target:torch.Tensor, quantile:float) -> torch.Tensor:
   error = target - preds.squeeze(1) # to make preds shape = (n, )
   return torch.max((quantile - 1) * error, quantile * error).sum()

Normal MLP Architecture (which is kind of replicating the residual network concept of lassonet):
class MLP(nn.Module):
  def __init__(self, input_dim, hidden_dim):
    super(MLP, self).__init__()
    self.layer1 = nn.Sequential(nn.Linear(input_dim, hidden_dim),
                                nn.ReLU())
    self.layer2 = nn.Linear(hidden_dim, 1)
    self.skip = nn.Linear(input_dim, 1)

  def forward(self, x):
    x_skip = self.skip(x)
    x = self.layer1(x)
    x = self.layer2(x)
    x = x + x_skip
    return x

Upon training with above architecture it returns satisfactory results with final quantile loss of 3.65 which is also cross checked with other models.

---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
 in ()
      4 y_train = torch.Tensor(y)
      5
----> 6 hist_obj = model.path(X_train, y_train)

5 frames
/usr/local/lib/python3.9/dist-packages/lassonet/interfaces.py in path(self, X, y, X_val, y_val, lambda_seq, lambda_max, return_state_dicts, callback)
    470             if self.model.selected_count() == 0:
    471                 break
--> 472             last = self._train(
    473                 X_train,
    474                 y_train,

/usr/local/lib/python3.9/dist-packages/lassonet/interfaces.py in _train(self, X_train, y_train, X_val, y_val, batch_size, epochs, lambda_, optimizer, return_state_dict, patience)
    329                     return ans
    330
--> 331                 optimizer.step(closure)
    332                 model.prox(lambda_=lambda_ * optimizer.param_groups[0]["lr"], M=self.M)
    333             print("epoch:", epoch)

/usr/local/lib/python3.9/dist-packages/torch/optim/optimizer.py in wrapper(*args, **kwargs)
    138                 profile_name = "Optimizer.step#{}.step".format(obj.__class__.__name__)
    139                 with torch.autograd.profiler.record_function(profile_name):
--> 140                     out = func(*args, **kwargs)
    141                     obj._optimizer_step_code()
    142                     return out

/usr/local/lib/python3.9/dist-packages/torch/optim/optimizer.py in _use_grad(self, *args, **kwargs)
     21         try:
     22             torch.set_grad_enabled(self.defaults['differentiable'])
---> 23             ret = func(self, *args, **kwargs)
     24         finally:
     25             torch.set_grad_enabled(prev_grad)

/usr/local/lib/python3.9/dist-packages/torch/optim/sgd.py in step(self, closure)
    128         if closure is not None:
    129             with torch.enable_grad():
--> 130                 loss = closure()
    131
    132         for group in self.param_groups:

/usr/local/lib/python3.9/dist-packages/lassonet/interfaces.py in closure()
    324                             f"l2_regularization_skip: {model.l2_regularization_skip()}"
    325                         )
--> 326                         assert False
    327                     ans.backward()
    328                     loss += ans.item() * len(batch) / n_train

AssertionError:

Your traceback is incomplete. Can you set verbose = 2? You should have some message "Initialized dense model" along with information about the dense model.

Yeah so this is the information.

epoch: 927
loss: 29672.576171875
epoch: 928
loss: 29670.18359375
Initialized dense model
929 epochs, val_objective 2.97e+04, val_loss 2.97e+04, regularization 1.42e+00, l2_regularization 2.15e-01
epoch: 0
loss: 29667.796875
epoch: 1
loss: 6788969.5
Loss:<PHONE_NUMBER>5808.0
l2_regularization: 78822872.0
l2_regularization_skip: 6728.37109375
Loss is<PHONE_NUMBER>5808.0
Did you normalize input?
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
[](https://localhost:8080/#) in ()
      4 y_train = torch.Tensor(y)
      5
----> 6 hist_obj = model.path(X_train, y_train)

5 frames
[/usr/local/lib/python3.9/dist-packages/lassonet/interfaces.py](https://localhost:8080/#) in path(self, X, y, X_val, y_val, lambda_seq, lambda_max, return_state_dicts, callback)
    470             if self.model.selected_count() == 0:
    471                 break
--> 472             last = self._train(
    473                 X_train,
    474                 y_train,

[/usr/local/lib/python3.9/dist-packages/lassonet/interfaces.py](https://localhost:8080/#) in _train(self, X_train, y_train, X_val, y_val, batch_size, epochs, lambda_, optimizer, return_state_dict, patience)
    329                     return ans
    330
--> 331                 optimizer.step(closure)
    332                 model.prox(lambda_=lambda_ * optimizer.param_groups[0]["lr"], M=self.M)
    333             print("epoch:", epoch)

[/usr/local/lib/python3.9/dist-packages/torch/optim/optimizer.py](https://localhost:8080/#) in wrapper(*args, **kwargs)
    138                 profile_name = "Optimizer.step#{}.step".format(obj.__class__.__name__)
    139                 with torch.autograd.profiler.record_function(profile_name):
--> 140                     out = func(*args, **kwargs)
    141                     obj._optimizer_step_code()
    142                     return out

[/usr/local/lib/python3.9/dist-packages/torch/optim/optimizer.py](https://localhost:8080/#) in _use_grad(self, *args, **kwargs)
     21         try:
     22             torch.set_grad_enabled(self.defaults['differentiable'])
---> 23             ret = func(self, *args, **kwargs)
     24         finally:
     25             torch.set_grad_enabled(prev_grad)

[/usr/local/lib/python3.9/dist-packages/torch/optim/sgd.py](https://localhost:8080/#) in step(self, closure)
    128         if closure is not None:
    129             with torch.enable_grad():
--> 130                 loss = closure()
    131
    132         for group in self.param_groups:

[/usr/local/lib/python3.9/dist-packages/lassonet/interfaces.py](https://localhost:8080/#) in closure()
    324                             f"l2_regularization_skip: {model.l2_regularization_skip()}"
    325                         )
--> 326                         assert False
    327                     ans.backward()
    328                     loss += ans.item() * len(batch) / n_train

AssertionError:

It looks like your objective is already not good in the dense model.Initialized dense model: val_loss 2.97e+04. Maybe you need to start from there to understand what is wrong? Compare your training with our _train function.

Okay I will look into the paper once again to get a better clarity of the internal procedures and also see my loss function and other stuffs. I will get back if there is anything more which can be discussed. Thank you for your help and time.

My point is precisely that you don't need to dive deep in the paper. LassoNet starts the optimization from a dense model. This dense model seems to be badly fitted. Try to figure out why!

Hi Louis,
I figured it out, probably there was a problem with the batch size. Initially the whole dataset was passed but when I switched to mini batches loss began to stabilize and converged at the end. I also obtained the path information in history object for various lambdas.
Thank you for your help. I guess this issue can be closed.

Nice, I'm happy if I could help you!


Chore/95 add python type annotations

I finally finished with the type annotations!
This is what they say about using type annotation on decorators
I think I might have missed some annotations on the **args, because I recently discovered they can also be annotated, so if you ever encounter in any of them please just add a :Any and it should be ok.
If you guys are happy with the merging we can close this issue.
I will open another issue for adding the ruff check on the annotation. (Actually this might help find the args).

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (f721d7c) 86.20% compared to head (77bf239) 86.28%.
Report is 12 commits behind head on main.

:exclamation: Current head 77bf239 differs from pull request most recent head e365b66. Consider uploading reports for the commit e365b66 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #132      +/-   ##
==========================================
+ Coverage   86.20%   86.28%   +0.07%
==========================================
  Files          54       54
  Lines        4075     4098      +23
==========================================
+ Hits         3513     3536      +23
  Misses        562      562

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Just figured out that infrastructure is missing (it was empty when I started if I recall correctly, and I haven't checked it since, but with ruff I got many warning ahah). I will solve and commit to the other branch.

@GiorgioCerro - I would just commit to this same branch. Then we can review the lot together :)

Everything is fixed: added infrastructure and checked with ruff.
Though, I allowed only 10 checks out of 11 and wanted your opinion on the last, which is whether we allow for type Any for the arguments or not.


Micronaut  Example Main class was not found, perhaps you should add a mainClass configuration to jib

Description of the issue:
Micronaut example not compiling
Expected behavior:
create docker image
Steps to reproduce:
./gradlew jibDockerBuild
Environment:
Linux, gralde, JDK 11
jib-gradle-plugin Configuration:
plugins {
    id 'application'
    id 'groovy'
    id 'io.spring.dependency-management' version '1.0.6.RELEASE'
    id 'net.ltgt.apt-idea' version '0.18'
    id 'com.google.cloud.tools.jib' version '1.0.0'
}

version '0.1'
group 'example.micronaut-jib'
sourceCompatibility = 1.8

repositories {
    mavenCentral()
    maven { url 'https://jcenter.bintray.com' }
}

dependencyManagement {
    imports {
        mavenBom 'io.micronaut:micronaut-bom:1.0.3'
    }
}

dependencies {
    annotationProcessor 'io.micronaut:micronaut-inject-java'
    compile 'io.micronaut:micronaut-http-client'
    compile 'io.micronaut:micronaut-http-server-netty'
    compile 'io.micronaut:micronaut-runtime-groovy'
    compile 'io.micronaut:micronaut-inject'
    compile 'io.micronaut:micronaut-runtime'
    compileOnly 'io.micronaut:micronaut-inject-groovy'
    compileOnly 'io.micronaut:micronaut-inject-java'
    runtime 'ch.qos.logback:logback-classic:1.2.3'
    testCompile 'io.micronaut:micronaut-inject-groovy'
    testCompile('org.spockframework:spock-core:1.2-groovy-2.5') {
        exclude group: 'org.codehaus.groovy', module: 'groovy-all'
    }
    testCompile 'io.micronaut:micronaut-inject-java'
}

compileJava.options.compilerArgs += '-parameters'
compileTestJava.options.compilerArgs += '-parameters'
run.main = 'example.micronaut.Application'

Log output:
./gradlew jibDockerBuild  --image=test

Task :jibDockerBuild FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':jibDockerBuild'.

com.google.cloud.tools.jib.plugins.common.MainClassInferenceException: Main class was not found, perhaps you should add a mainClass configuration to jib

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Additional Information:

Hmm this seems to be deeper than jib:
$ ./gradlew build
> Task :startScripts FAILED

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':startScripts'.
> No value has been specified for property 'mainClassName'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s
4 actionable tasks: 1 executed, 3 up-to-date

I have to added below section in my build.gradle file
jib {     container.mainClass = "webapp.Application" }
still registry authentication fails, but image build works.

But l think the bigger problem is that the application itself does not build, even before attempting Jib.

Hi @grailsweb, we fixed an issue with finding the main class for a Groovy application in version 1.0.1 - if you update the version of Jib, I believe the build should work.

Yes, it complies now. Thanks

Reopnenning since there is a build and run problem in the application itself.


Documentation: Add reference information on capabilities which can be added/dropped

Currently the documentation notes that "In addition to --privileged, the operator can have fine grain control over the capabilities using --cap-add and --cap-drop. By default, Docker has a default list of capabilities that are kept." (ref: https://github.com/docker/docker/blame/master/docs/sources/reference/run.md#L632-L636)
However, at that point a few examples are given, but no information is provided on what that list of capabilities are, making it hard for users to search/find what those capabilities and, specifically, their names, are.
The current capabilities list in Docker is here: https://github.com/docker/docker/blob/master/daemon/execdriver/utils.go
They can be mapped to these additional descriptions here: http://linux.die.net/man/7/capabilities
Potentially a table might be a nice way to list this information if we agree that's how we want to display, or if we want an external pointer that may be reasonable as well.  The docs team may have guidance here (ping @SvenDowideit @moxiegirl @fredlf @jamtur01)

#dibs We're writing a cap table in a  PR to solve this.

@resouer Please remember to add this issue also to the fixes or closes keyword so, this issue can be tracked cleanly. Thanks!


Syntax highlighting gets confused if return type ends with a number

From @kayahr on July 4, 2016 11:9

VSCode Version: 1.2.1
OS Version: Debian GNU/Linux 8.5

Steps to Reproduce:

Open new TypeScript file.
Copy/Paste the following code:

class Vector2 {
    public foobar(): Vector2 {
        return this;
    }
}

class Vector2D {
    public foobar(): Vector2D {
        return this;
    }
}

The method in the class Vector2D is properly colored but in the class Vector2 the syntax highlighting gets confused. Looks like this has something to do with the class name ending with a number.
Here is a screenshot showing a wrong color of the return and thiskeywords:

In larger source code this gets quite confusing because subsequent methods in the same class are also affected.
Copied from original issue: Microsoft/vscode#8720

By the way: The same problem can be reproduced right here on Github when formatting source code with language=typescript:
class Vector2 {
    public foobar(): Vector2 {
        return this;
    }
}

class Vector2D {
    public foobar(): Vector2D {
        return this;
    }
}

Duplicate of #188 and #153.

Fixed by #257


Unable to remove annotation when wildcard import is used

I have the following class:
import java.lang.annotation.*;
@Retention(RetentionPolicy.CLASS)
@Target(ElementType.METHOD)
public @interface MyAnnotation {
}

I want to remove Retention annotation, but I can't do that with Jurand.
None of the calls I tried worked.
What arguments should I pass to Jurand to remove Retention?

You need to specify -a to also remove annotations found in code. Without -a it only removes import statements. Wildcard import should not prevent it from working. It only prevents associating the FQN with the simple name of the symbol. But it is still possible to specify matchers to match what you want. When you remove imports by pattern and specify -a, the tool also attempts to remove all annotations whose imports were removed even if they would not match by the pattern.
For matching Retention only:
$ jurand MyAnnotation.java -a -n Retention or
$ jurand MyAnnotation.java -a -p Retention
For matching the import:
$ jurand MyAnnotation.java -p [*] or
$ jurand MyAnnotation.java -p annotation[.][*] or
$ jurand MyAnnotation.java -p annotation\.\*
These flags can be merged.
Note that -n '*' does not match anything because * is not a simple class name. Wildcard imports can only be matched with -p.


TransportClient adaptions for use with Elasticsearch 5.X aviable in the future?

Hello,
as I read the major version of the TransportClient must be the as the major version of Elasticsearch. I am highly interested to use this sink together with ES 5.0. Will there be adaptions made to this new major verison of Elasticsearch?
Many Thanks.
Regards

I met the problem too .....

same here

same here


Autogluonts

Issue #, if available:
Description of changes:
Add AutoEstimator combined with autogluon package
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hey @YuntianYeAWS there appear to be several modules in this PR, are you sure that all of them are supposed to be included?
For example, the AutoEstimator folder seems weird, since it's not within src/gluonts. Also src/gluonts/autogluonts./ has a weird name ending with a dot.
Could you make sure that the intended code is included in the PR?

@YuntianYeAWS could you also expand a bit on the PR description? Especially when changes are large (many lines or modules affected) it is good to have some guidance on what the intended content of the pull request is.
For example, a description of where the core modules of the feature are, where to look for examples on how to use the feature (if there is any), what else is being included/addressed in the PR, and so on.
This serves a double purpose: it helps you make sure that the content of the PR is as intended, and helps reviewers navigate through the changes more efficiently.

Hey @YuntianYeAWS there appear to be several modules in this PR, are you sure that all of them are supposed to be included?
For example, the AutoEstimator folder seems weird, since it's not within src/gluonts. Also src/gluonts/autogluonts./ has a weird name ending with a dot.
Could you make sure that the intended code is included in the PR?
I think only the autoestimator is needed and other modules should remain the same. I am not sure why there's conflicting estimator? I will change to be consistent with the latest one.

I have created a new folder of AutoEstimator in gluonts.model and an example file in examples folder. Is that ok?
Thank you for the comments!

The test failures are unrelated to the changes in this PR: there is (at least) one flaky test that should be (for now) marked as such: https://github.com/awslabs/gluon-ts/blob/6ac4cc6b2beef045453b58ab10876e96fbd9f502/test/torch/modules/test_torch_distribution_inference.py#L273
You can mark it as "flaky" by decorating it with e.g.
@pytest.mark.flaky(max_runs=5, min_passes=1)


Update newrelic.yml for manual installations

The setupConfig.yaml file within the nerdlet to setup Ruby houses the default configuration file users download when adding data to their application through the UI.
To turn log forwarding on by default for all new installations, let's update the file to include uncommented configuration to turn log forwarding on by default with a snippet explanation.
Resources (Internal)

PR here: https://source.datanerd.us/external-devbridge/setup-nerdlets/pull/57

The aforementioned PR has been merged!


Bugfix #6025 introduces exception in GridLayer._tileReady - a parameter check is missing

Leaflet 1.3.2/1.3.3 has a fix that does not check a parameter for null/undefined and crashes in my scenario because GridLayer._tileReady(coords, err, tile) gets called with tile = null.
By fix #6025 GridLayer.js line 845 is changed to:
if (!this._map || tile.getAttribute('src') === Util.emptyImageUrl) { return; }
but tile is not checked.
I propose fixing this by
if (!this._map || (tile && tile.getAttribute('src') === Util.emptyImageUrl)) { return; }
I fear I can't give a fiddle because I have a complicated scenario involving a subclassed leaflet.vectorgrid. The code worked fine with Leaflet 1.3.1 that didn't have the second condition in the if statement.

I concur with this, same situation, running Leaflet 1.3.3 with Leaflet.VectorGrid.
Works fine in 1.3.1 and 1.2.0

Same problem here in combination with the leaflet plugin "Leaflet.TileLayer.PouchDBCached"

Any idea if there will be a release soon incorporating this fix?

Finally find this.. expect for next release.

Leaflet 1.3.4 is out! :rocket:
https://github.com/Leaflet/Leaflet/releases/tag/v1.3.4


Additional Typescript/ESLint rules

This PR addresses the rules that we have decided to enable from #3. It also adds new rules from our updated plugin and updates the no-multiline-var-declarations rule to allow multiline const declarations.

Also:
9d9e237 - Commit message has a typo: tpescript
475f971 - Commit message first line is too long


[ModTranslation]: AI Controlled Rockets

What mod is that translation for?
AI controlled Rockets
Additional Comments
In the game it says on the AI Brain Module that it should be built on top of the rocket like the AI Nosecone, but the AI Brain Module builds anywhere other than the top and I can build a basic nosecone. I couldn't find the line "{BRAINNAME} is a {BRAINXPSTATE} ({BRAINBOOST}% total rocket speed)" in the game, so I might have translated it wrong.
translation file
ru.zip

thx for noticing the brain module line, will fix that
strings that have {Something} need to keep whatever is between those brackets, as those are replacement tags


"set to not considered" button viewable together with the "validate submission" button

 "set to not considered" button viewable together with the "validate submission" button


Some accounts not scraping follower counts

Hello! I found this library a while back and have been using it to scrape Instagram followers from about 15 accounts. In the last several months, several (4) accounts that I track have started not working properly.
This one is working and returns a value (as of today) of 3,436 followers:
url <- get_page_user('tuftsmedicalcenter')
fw <- get_count_follower(url)
This one returns the following error after running the get_page_user function. I've checked that I have the account name correct and I do (https://www.instagram.com/cancercenter/?hl=en).
Warning message: In get_page_user("cancercenter") :
Username cancercenter did not return a valid web page.
url <- get_page_user('cancercenter')
fw <- get_count_follower(url)
This one returns the following error after running the get_count_follower function. The get_page_user function seems to have worked properly.
Error in if (stringr::str_detect(count_value, "k")) mlpy <- 1000 :
missing value where TRUE/FALSE needed
url <- get_page_user('brighamandwomens')
fw <- get_count_follower(url)

Updated. Please reinstall and try again.


Add tags to organization and membership models

Just as we can apply tags to workshops, we would like to apply tags to organizations and memberships.

Do you want to have functionality of looking up organizations or memberships by tags? Do you want to have a single page to lookup anything tagged with specific tag? Would these tags on organizations or memberships somehow impact existing logic or workflows?

We are still discussing some of these features.  We would like to consider whether it is better to have a list of tags to apply or if each item should be a distinct field in the table.
@pbanaszkiewicz  from a technical perspective, what are the advantages to having one or the other?

For me there's little difference, but I think list of tags is more feature-proof (and allows to easily scale down to 1 tag if we need to).


Incorrect Plural Forms Mapping for Latvian (lv) Locale

🐛 Bug Report
The plural forms mapping for the Latvian (lv) locale appears to be incorrect. The current mapping does not correctly convert between CLDR and internal representations.
To Reproduce

Go to https://i18next.github.io/i18next-v4-format-converter-web/
Use the following JSON object as input:

{
  "myKey_0": "one key",
  "myKey_1": "other {{count}} keys",
  "myKey_2": "no keys"
}

Observe the result.

The result that I got:
{
  "myKey_one": "one key",
  "myKey_zero": "no keys"
}

Screenshot

Expected behavior
I should have received the following result:
{
  "myKey_one": "one key",
  "myKey_other": "other {{count}} keys",
  "myKey_zero": "no keys"
}

Your Environment
URL: i18next-v4-format-converter-web

thanks... should be fixed now


[bootstrap] Fix typo in comment

Fixes a typo in a comment within the Python bootstrap script.

LGTM, Thanks!


Fatal error in launcher: Unable to create process

Issue description
I am a first time user of pip and pipenv. pipenv is failing to launch when trying to install a library. I have fully installed and updated pip, and python 3.
Expected result
Expected to have pipenv install the "requests" library. When using the pipenv install requests command. Note: I am able to get it to run when using the following command: python -m pipenv install requests
Actual result
The following is returned when attempting to run pipenv:
Fatal error in launcher: Unable to create process using '"c:\python37\python.exe"  "C:\Users\drtri\AppData\Roaming\Python\Python37\Scripts\pipenv.exe" install requests --verbose
Steps to replicate
Run the following within cmd on windows: pipenv install requests --verbose

Support request:
Fatal error in launcher: Unable to create process using '"c:\python37\python.exe"  "C:\Users\drtri\AppData\Roaming\Python\Python37\Scripts\pipenv.exe" --support'
Additional notes
I noticed that using python -m pipenv install requests seems to work. However, once I try and use import requests within a python script, I get a "No module names 'requests' found" error.

@Drtrider Can you still reproduce the issue after you uninstall and reinstall pipenv?

However, once I try and use import requests within a python script, I get a "No module names 'requests' found" error.

The script should be run in virtualenv. or pipenv run python script.py

@frostming Looks like uninstalling it, and re-installing it did the trick. Very odd behavior. Thank you.

I solved this issues of Unable to create process using in venv with this forum answers. This will surely help you and fix your issues.


fix https

Resolves #245

Thank you @fogleman
This is my first PR. Happy to help you

Hi how r u I'm new here


Formatting media.datetime

In the documentation for themes, you mention formatting datetime like this:
{% if media.exif.datetime %}
    {{ media.exif.datetime.strftime('%A, %d. %B %Y') }}
{% endif %}
However, media.exif.datetime does not appear to be a Python datetime object.  When I attempt this in the colorbox index.html, I get the following error
File "/media/cams/themes/colorbox/templates/index.html", line 44, in template
    data-date=", {{ media.exif.datetime.strftime('%c') }}"
jinja2.exceptions.UndefinedError: 'unicode object' has no attribute 'strftime'
Am I missing something?
Thank you.

The documentation is wrong (sorry!), datetime is indeed a formatted string (with strftime('%A, %d. %B %Y')), but there is also a dateobj key with the Python datetime object:
https://github.com/saimn/sigal/blob/master/sigal/image.py#L303-L316
Can you check if it works for you ? (And if you want to fix it, you're welcome :wink: )


Why not return errors immediately after validation? (and remove ajv.errors)

Thanks for the great library! I've recently started migrating from tv4 to ajv, primarily because of the promised speed improvements. Thus far AJV appears to be very feature complete and I like pre-registering all schemas in a single instance beforehand; keeps my schemas managed centrally in the codebase which is nice.
I noticed one thing that might be a cause of tricky and hard to reproduce bugs when using the library improperly.
When accessing ajv.errors (or ajv.errorsText I presume as well) in a callback, promise or any tick after the one in which you've called ajv.validate there is no guarantee that ajv.errors contains the set of errors you might expect.
Example:
var async = require('async');
var Ajv = require('ajv');

var ajv = new Ajv();
ajv.addSchema({'type': 'string'}, 'testSchema');

function test(name, timeout, data, done) {
  var valid = ajv.validate('testSchema', data);
  console.log(name, 'valid =', valid + ', ajv.errors =', ajv.errors);
  setTimeout(function() {
    console.log(name + ' timeout', ' valid =', valid + ', ajv.errors =', ajv.errors);
    done();
  } , timeout);
}

async.parallel([
  function(cb) {
    test('Test 1', 100, false, cb);
  },
  function(cb) {
    test('Test 2', 50, 'test', cb);
  },
]);

This outputs:
Test 1 valid = false, ajv.errors = [ { keyword: 'type', dataPath: '', message: 'should be string' } ]
Test 2 valid = true, ajv.errors = null
Test 2 timeout  valid = true, ajv.errors = null
Test 1 timeout  valid = false, ajv.errors = null

Notice in the last line Test 1 is not valid but contains no errors anymore.
The cause is fairly obvious but it is an easy mistake made given how the library currently works. Why not have var valid = ajv.validate('testSchema', data); return a result object containing errors, errorText etc. (a sort of ValidationResult object)?
Another option to avoid misuse of the function is to rename ajv.errors to ajv.lastErrors. Not that I like that name, but it makes its intended use more clear.
I understand these changes would be backwards incompatible, but it might be worth a thought if planning a big new release.
But overall; thanks for the great library! :+1:

Thank you very much for the feedback!

When accessing ajv.errors (or ajv.errorsText I presume as well) in a callback, promise or any tick after the one in which you've called ajv.validate there is no guarantee that ajv.errors contains the set of errors you might expect.

That is correct, the errors are overwritten every time ajv.validate is called. If you plan using these errors you need to copy the reference to some var in the same tick before the next validation is called.

Why not have var valid = ajv.validate('testSchema', data); return a result object containing errors, errorText etc. (a sort of ValidationResult object)?

For performance reasons - it would be slower. In most validation calls the data is valid so you don't need to access errors. Creating a wrapper object every time you need to return the result makes it substantially slower.
Also, you may have seen in readme that although there is ajv.validate method for convenience, it is faster using precompiled validating function (ajv.validate calls it anyway but it has the cost of the lookup plus an extra function call, so if the schema is large the difference can be negligible but on the small schemas it can be more than twice faster). If you use one ajv instance per app with all schemas in one place it could be more convenient to use ajv.getSchema method (that accepts the schema ref) than ajv.compile(that needs the schema itself) - they both return the same compiled schema function (it only gets compiled once in all cases).

Another option to avoid misuse of the function is to rename ajv.errors to ajv.lastErrors. Not that I like that name, but it makes its intended use more clear.

I understand these changes would be backwards incompatible, but it might be worth a thought if planning a big new release.

You are right here. Maybe on the next major version change... I will make it clearer in readme that ajv.errors (and validate.errors) are overwritten and have to be used in the same tick.
Thanks again

I added note in readme. errors is the same property name that is used in other validators returning boolean rather than the object (e.g., is-my-json-valid and in jsen), so I will keep it like this for consistency sake.

Fair enough.
Good work!

This library and all the work @epoberezkin is amazing, but this is an incredibly strange deviation from what most users expect. I'd love to submit a pull request if you're open to any of these suggestions:

Allow .validate(data) to accept a second parameter which is a callback in the typical node.js style of (err, data) => void... so if err = null then you know your validation was successful.

Allow .validate(data) to either return true or an instance of Error, then users would simply be able to do something like this following:

const result = schema.validate(data)
if (result === true) {
  console.log('valid schema')
} else if (result instanceof Error) {
  console.log(result)
}

Please see https://github.com/epoberezkin/ajv/blob/master/FAQ.md#ajv-api-for-returning-validation-errors

@epoberezkin Apologies for the noise of the notification, my fault for missing the FAQ -- you've definitely had to address the issue plenty of times.
Looks like the async validation is exactly what I need. Thank you so much!

Just be aware that async requires a non standard keyword in the schema at the moment.