Services map support for traces and fields mapping sample

Description
added a service mapping support for both the traces correlation between

Metrics.serviceName <-> services.name
Traces.serviceName <-> services.name

This will allow for simple and common integrations of data-prepper proprietary schemas
This PR is also addressing the fields mapping aliasing for similar semantic  meaning fields that have different names -
Issues Resolved

https://github.com/opensearch-project/observability/issues/1473

Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[x] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

How did you test this/what is this concrete deliverable this PR is doing? I couldn't really comprehend on first pass. Also can you make sure all of the PRs you are doing are aimed at Main branch? Or at least back ported in a timely fashion? If they are not it will create a big headache with conflicts later on when other changes are needed

the PR is aiming for adding documentation and description sample of the services concept support for the Integration schema
In addition

adding fields mapping support sample (using data-prepper)
adding Observability Correlation using serviceName
sample of data-prepper dashboard for serviceMap integration

concluded with - https://github.com/opensearch-project/observability/pull/1494
removing ..


How to force webpack not to use eval in production

Do you want to request a feature or report a bug?
Baiscally a question, but it might be a bug, I'm not sure.

What is the current behavior?
I'm having the csp error because webpack is using eval in one of my bundles.
I've tried to use all the options available for source mapping and canceling devtools.
Also I've tried configuring the compression using Webpack.optimize.UglifyJsPlugin in which you can set sourceMap: false. but I'm still getting the same error and I can see there's a line in my bundle:
t.exports=function(t){"undefined"!=typeof execScript?execScript(t):eval.call(null,t)}

which is calling eval.
If the current behavior is a bug, please provide the steps to reproduce.

In your configuration set devtool to any possible option even devtool: false
run webpack -p
Search your bundles for eval.call
You'll find an occurance

What is the expected behavior?
I was expecting that we have an option that creates bundles without using eval.
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
I'm using webpack 2.4.1, on node 6.10.0 and npm 3.10.10 . but I've tried it with differen versions of webpack 2.x.x and on npm 3 and npm 4 on OSX and Ubuntu.
Thank you

@alihaghighatkhah can your provide minimal reproducible test repo? very interesting

This is caused by the script-loader. Don't use the script-loader.

@sokra exactly. I found the issue and fixed it. Thank you

@evilebottnawi As Sokra said I was using script loader, i just removed it and used a combination of exports/imports loaders instead.

Can you please tell what to use instead of script-loader?

There's still an eval causing CSP errors: #5627

@reyraa can you show your webpack config please. I tried to use script loader (not babel), but still see evals

@dcsaszar https://github.com/webpack/webpack/issues/5627#issuecomment-362543814

I have the same issue when building a browser extension where eval() is not allowed. The config is
const merge = require("webpack-merge");
const common = require("./webpack.common.js");

module.exports = merge(common, {
  // devtool: "inline-source-map"
});

When using "inline-source-map", the eval()s disappear. Is this the recommended setting?

inline-source-map is not for production, please read docs https://webpack.js.org/configuration/devtool/

@evilebottnawi I understand that it isn't meant for production, but unfortunately I couldn't find any other way of removing eval() from the output. The link you provide isn't explicit about it either.

Use devtool: "source-map"

You can turn off devtool at all, it will not generate map for script files.
devtool: flase

You can turn off devtool at all, it will not generate map for script files. devtool: flase
yes, I tried this. This doesn't create map file and also stops generating bundle with the eval function. Thanks. but I don't know is it a good setting for preventing generating eval();

You can turn off devtool at all, it will not generate map for script files. devtool: flase

yes, I tried this. This doesn't create map file and also stops generating bundle with the eval function. Thanks. but I don't know is it a good setting for preventing generating eval();

You can turn off devtool at all, it will not generate map for script files. devtool: flase

Sadly, this doesn't work in NextJS - it literally ignores/overrides it to set it back on in the dev environment. Anyone find a solution to getting devtools off? Causing a nightmare for CSP for our secure app.
Maybe we simply can't use NextJS as out frontend?

Experiencing this in Vue 3 using webpack and magic comments.. as webpack require chunks in it uses eval which then throws a CSP error because we don't want to be using unsafe-eval.
I've been hunting around for 2 days trying to correct this:

I'd really love some insight. My webpack config modifications from the standard vue-cli are like so:
const { defineConfig } = require('@vue/cli-service');
const path = require('path');

module.exports = defineConfig({
    publicPath: process.env.ENTRY === 'serve' ? '' : `${process.env.SOME_ENV_VAR}/`,
    transpileDependencies: true,
    filenameHashing: false,
    css: {
        extract: process.env.ENTRY !== 'serve'
    },
    pages: {
        'referrals-app': {
            entry: 'src/main.ts',
            template: 'public/index.html',
            filename: 'index.html',
            chunks: ['xxx-api']
        }
    },
    configureWebpack: {
        mode: 'production',
        devtool: 'source-map',
        entry: {
            'referrals-api': './src/entry.xxxApi.ts'
        },
        optimization: {
            splitChunks: false
        },
        module: {
            rules: [{
                test: /\.scss$/,
                use: ['sass-loader', {
                    loader: 'style-resources-loader',
                    options: {
                        patterns: [
                            path.resolve(__dirname, './src/assets/styles/_variables.scss'),
                            path.resolve(__dirname, './src/assets/styles/_mixin.scss')
                        ]
                    }
                }]
            }]
        }
    }
});


Create/Edit Page - Add "Singleton" to the Details section

Add a toggle to indicate whether or not this listing is a "Singleton" in Webtop
Is not a Singleton

Is a Singleton

This works

On ci-master, staging and prod there is a problem with the descriptive text on initial load when Singleton is set to true.  A fix for this is already available on ci-develop and will be included in the next release.

This was working in STG and now it is not.  Ticket 579 address that the wrong error message was displayed.

@kgordon-1 can you give me more context to an error message (#579 cannot be found) this ticket is in regards to adding a toggle to enable or disable singleton mode for submissions, there should be no error reporting associated because there is no way to have an invalid input for this component, Since it is not required and only shows on, or off. Also it will default to an acceptable value of off / false.

@wski Not sure what the bug from above is but the filed was not added to the tree on the left side under intents meaning you can't navigate to it from the accordion menu.

@wski, I'm not exactly sure what to test here. As for the last few comments regarding "Singleton" appearing in the accordion menu, I can confirm that it's there on ci-develop, but it's also present on ci-master, so I'm not sure what is being fixed. As for this ticket as a feature request for the addition of a Singleton listing area on the create/edit page, I believe that's already been tested?

Ok, looks like the change has been around for a while. Moving to CI-QA.

Verified the ticket in staging with all of the browsers.
I did find a bug in where the activity is not getting recorded. The issue is 88 in ozp-rest.


Mobile UI Revise

Actually all entity pages should be revised for different devices

workflow page mobile revise can be imposible. There is a lot buttons, text and descriptions

nothing is impossible with me


fix: fixed the Tabs attribute from style to variant

Issue Reference #1256
this PR fixes the omitting attribute of style and now it's been replaced with variant attribute in order to allow the usage of style attribute.

Summary by CodeRabbit

New Features

Updated <Tabs> component to use variant instead of style for specifying tab styles.
Supported variants include underline, pills, and fullWidth.

Refactor

Renamed style property to variant across all examples and documentation for consistency and clarity.

Documentation

Updated documentation to reflect the new variant property in the <Tabs> component.

Looks good, only thing left is to create a changeset (patch)

Looks good, only thing left is to create a changeset (patch)

Pardon!. but can you help from where & how I need to create this changeset (patch)?

Looks good, only thing left is to create a changeset (patch)

Please have a look, the changeset I've added is correct...


Make sure dimensions for UMAPs exist

When trying to generate the test data, I came across this error in the cell type report, where the dimensions set in the chunk options don't always exist. For each cell type annotation method, we have a chunk that is evaluated only if that method exists. Here was where we were defining the dimensions to use to create the UMAP in the following chunk. The problem with this approach is that if a method doesn't exist, then the dimensions don't get assigned to a variable. Then in the chunk where we create the UMAP we define the figure height and width with variables that don't exist. So here I'm just setting all the dimensions to a dummy set of dimensions in the event that a cell type method wasn't used. That way the variable exists when going to the UMAP chunk, even if that chunk doesn't get evaluated.

I don't really know which is better. I love the verbosity of variable names to make sure things are in the right spot, but the option I suggested above reduces the amount of code. So...pick your favorite!

Hmmm I think I like being explicit since the dims could be different based on the number of cell types. So instead of overwriting them, we should name them separately.


Error installing dependencies for MNIST example

Describe the bug
I am trying to launch the MNIST example on a single machine on AWS. The dependencies fail to install. Likely to do something with Rust. Am I missing dependencies?
Environment

Your operating system and version: Ubuntu 20.04.4 LTS
Your python version: 3.8.10
Your PyTorch version: not installed
How did you install python (e.g. apt or pyenv)? Did you use a virtualenv?: Preinstalled Ubuntu
Have you tried using latest bagua master (python3 -m pip install --pre bagua)?: No

Reproducing

Launch g4dn.xlarge instance with AMI: ami-00a2823259d140f46 (Deep Learning AMI GPU CUDA 11.3.1 (Ubuntu 20.04) 20220303, Built with NVIDIA CUDA, cuDNN, NCCL, GPU Driver, Docker, NVIDIA-Docker and EFA support)

check CUDA version: nvcc --version -> version 11.3

install rust: curl https://sh.rustup.rs -sSf | sh -s -- --default-toolchain stable -y

install bagua package: pip install bagua-cuda113 -> exits successfully.

clone bagua repo: git clone https://github.com/BaguaSys/bagua.git && cd bagua/examples/mnist

install requirements: pip install -r requirements.txt -> error, see below.

           Running `/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-65d17bb237c18142/build-script-build`
      The following warnings were emitted during compilation:

      warning: nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' and 'sm_50' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
      warning: nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' and 'sm_50' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).

      error: failed to run custom build command for `bagua-core-internal v0.1.2 (/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal)`

      Caused by:
        process didn't exit successfully: `/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-65d17bb237c18142/build-script-build` (exit status: 101)
        --- stdout
        TARGET = Some("x86_64-unknown-linux-gnu")
        OPT_LEVEL = Some("3")
        HOST = Some("x86_64-unknown-linux-gnu")
        CXX_x86_64-unknown-linux-gnu = None
        CXX_x86_64_unknown_linux_gnu = None
        HOST_CXX = None
        CXX = None
        NVCC_x86_64-unknown-linux-gnu = None
        NVCC_x86_64_unknown_linux_gnu = None
        HOST_NVCC = None
        NVCC = None
        CXXFLAGS_x86_64-unknown-linux-gnu = None
        CXXFLAGS_x86_64_unknown_linux_gnu = None
        HOST_CXXFLAGS = None
        CXXFLAGS = None
        CRATE_CC_NO_DEFAULTS = None
        DEBUG = Some("false")
        CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
        running: "nvcc" "-ccbin=c++" "-Xcompiler" "-O3" "-Xcompiler" "-ffunction-sections" "-Xcompiler" "-fdata-sections" "-Xcompiler" "-fPIC" "-m64" "-I" "cpp/include" "-I" "third_party/cub-1.8.0" "-I" "/home/ubuntu/.local/share/bagua/nccl/include" "-Xcompiler" "-Wall" "-Xcompiler" "-Wextra" "-std=c++14" "-cudart=shared" "-gencode" "arch=compute_35,code=sm_35" "-gencode" "arch=compute_37,code=sm_37" "-gencode" "arch=compute_50,code=sm_50" "-gencode" "arch=compute_52,code=sm_52" "-gencode" "arch=compute_53,code=sm_53" "-gencode" "arch=compute_60,code=sm_60" "-gencode" "arch=compute_61,code=sm_61" "-gencode" "arch=compute_62,code=sm_62" "-gencode" "arch=compute_70,code=sm_70" "-gencode" "arch=compute_72,code=sm_72" "-gencode" "arch=compute_75,code=sm_75" "-gencode" "arch=compute_80,code=sm_80" "-gencode" "arch=compute_86,code=sm_86" "-o" "/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-a571c95913d0ee58/out/kernels/bagua_kernels.o" "-c" "kernels/bagua_kernels.cu"
        cargo:warning=nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' and 'sm_50' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
        exit status: 0
        AR_x86_64-unknown-linux-gnu = None
        AR_x86_64_unknown_linux_gnu = None
        HOST_AR = None
        AR = None
        running: "ar" "cq" "/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-a571c95913d0ee58/out/libbagua_kernels.a" "/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-a571c95913d0ee58/out/kernels/bagua_kernels.o"
        exit status: 0
        running: "nvcc" "-ccbin=c++" "-Xcompiler" "-O3" "-Xcompiler" "-ffunction-sections" "-Xcompiler" "-fdata-sections" "-Xcompiler" "-fPIC" "-m64" "-I" "cpp/include" "-I" "third_party/cub-1.8.0" "-I" "/home/ubuntu/.local/share/bagua/nccl/include" "-Xcompiler" "-Wall" "-Xcompiler" "-Wextra" "-std=c++14" "-cudart=shared" "-gencode" "arch=compute_35,code=sm_35" "-gencode" "arch=compute_37,code=sm_37" "-gencode" "arch=compute_50,code=sm_50" "-gencode" "arch=compute_52,code=sm_52" "-gencode" "arch=compute_53,code=sm_53" "-gencode" "arch=compute_60,code=sm_60" "-gencode" "arch=compute_61,code=sm_61" "-gencode" "arch=compute_62,code=sm_62" "-gencode" "arch=compute_70,code=sm_70" "-gencode" "arch=compute_72,code=sm_72" "-gencode" "arch=compute_75,code=sm_75" "-gencode" "arch=compute_80,code=sm_80" "-gencode" "arch=compute_86,code=sm_86" "--device-link" "-o" "/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-a571c95913d0ee58/out/bagua_kernels_dlink.o" "/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-a571c95913d0ee58/out/libbagua_kernels.a"
        cargo:warning=nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' and 'sm_50' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
        exit status: 0
        running: "ar" "cq" "/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-a571c95913d0ee58/out/libbagua_kernels.a" "/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-a571c95913d0ee58/out/bagua_kernels_dlink.o"
        exit status: 0
        running: "ar" "s" "/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-a571c95913d0ee58/out/libbagua_kernels.a"
        exit status: 0
        cargo:rustc-link-lib=static=bagua_kernels
        cargo:rustc-link-search=native=/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/target/release/build/bagua-core-internal-a571c95913d0ee58/out
        CXXSTDLIB_x86_64-unknown-linux-gnu = None
        CXXSTDLIB_x86_64_unknown_linux_gnu = None
        HOST_CXXSTDLIB = None
        CXXSTDLIB = None
        cargo:rustc-link-lib=stdc++
        cargo:rustc-link-search=native=/usr/local/cuda/bin/../targets/x86_64-linux/lib
        cargo:rustc-link-lib=cudart_static
        CMAKE_TOOLCHAIN_FILE_x86_64-unknown-linux-gnu = None
        CMAKE_TOOLCHAIN_FILE_x86_64_unknown_linux_gnu = None
        HOST_CMAKE_TOOLCHAIN_FILE = None
        CMAKE_TOOLCHAIN_FILE = None
        CMAKE_GENERATOR_x86_64-unknown-linux-gnu = None
        CMAKE_GENERATOR_x86_64_unknown_linux_gnu = None
        HOST_CMAKE_GENERATOR = None
        CMAKE_GENERATOR = None
        CMAKE_PREFIX_PATH_x86_64-unknown-linux-gnu = None
        CMAKE_PREFIX_PATH_x86_64_unknown_linux_gnu = None
        HOST_CMAKE_PREFIX_PATH = None
        CMAKE_PREFIX_PATH = None
        CMAKE_x86_64-unknown-linux-gnu = None
        CMAKE_x86_64_unknown_linux_gnu = None
        HOST_CMAKE = None
        CMAKE = None
        running: "cmake" "/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum" "-DCMAKE_CXX_STANDARD=17" "-DALUMINUM_ENABLE_NCCL=YES" "-DCUB_INCLUDE_PATH=/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/cub-1.8.0" "-DNCCL_LIBRARY=/home/ubuntu/.local/share/bagua/nccl/lib/libnccl.so" "-DNCCL_INCLUDE_PATH=/home/ubuntu/.local/share/bagua/nccl/include" "-DBUILD_SHARED_LIBS=off" "-DCMAKE_INSTALL_PREFIX=/tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/../../../bagua_core/.data" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -std=c++17 -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_ASM_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_ASM_COMPILER=/usr/bin/cc" "-DCMAKE_BUILD_TYPE=Release"
        -- The CXX compiler identification is GNU 9.3.0
        -- Detecting CXX compiler ABI info
        -- Detecting CXX compiler ABI info - done
        -- Check for working CXX compiler: /usr/bin/c++ - skipped
        -- Detecting CXX compile features
        -- Detecting CXX compile features - done
        -- NCCL support requested but no GPU runtime enabled. Assuming CUDA support.
        -- Performing Test CXX_COMPILER_HAS_FALIGNED_NEW
        -- Performing Test CXX_COMPILER_HAS_FALIGNED_NEW - Success
        -- Performing Test CXX_COMPILER_HAS_G3
        -- Performing Test CXX_COMPILER_HAS_G3 - Success
        -- Performing Test CXX_COMPILER_HAS_OG
        -- Performing Test CXX_COMPILER_HAS_OG - Success
        -- Found MPI_CXX: /opt/amazon/openmpi/lib/libmpi.so (found suitable version "3.1", minimum required is "3.0")
        -- Found MPI: TRUE (found suitable version "3.1", minimum required is "3.0") found components: CXX
        -- Looking for C++ include pthread.h
        -- Looking for C++ include pthread.h - found
        -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
        -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
        -- Check if compiler accepts -pthread
        -- Check if compiler accepts -pthread - yes
        -- Found Threads: TRUE
        -- Found HWLOC: /usr/lib/x86_64-linux-gnu/libhwloc.so
        -- Found CUDA: /usr/local/cuda (found suitable version "11.3", minimum required is "9.0")
        -- The CUDA compiler identification is NVIDIA 11.3.109
        -- Detecting CUDA compiler ABI info
        -- Detecting CUDA compiler ABI info - done
        -- Check for working CUDA compiler: /usr/local/cuda/bin/nvcc - skipped
        -- Detecting CUDA compile features
        -- Detecting CUDA compile features - done
        -- Found NCCL: /home/ubuntu/.local/share/bagua/nccl/lib/libnccl.so (found suitable version "2.9.9", minimum required is "2.7.0")
        -- Found CUB: /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/cub-1.8.0
        -- Configuring done
        -- Generating done
        -- Build files have been written to: /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/bagua_core/.data/build
        running: "cmake" "--build" "." "--target" "install" "--config" "Release" "--parallel" "4"
        [  7%] Building CXX object src/CMakeFiles/Al.dir/Al.cpp.o
        [ 15%] Building CXX object src/CMakeFiles/Al.dir/mempool.cpp.o
        [ 23%] Building CXX object src/CMakeFiles/Al.dir/mpi_impl.cpp.o
        [ 30%] Building CXX object src/CMakeFiles/Al.dir/profiling.cpp.o
        [ 38%] Building CXX object src/CMakeFiles/Al.dir/progress.cpp.o

        --- stderr
        CMake Warning (dev) in src/CMakeLists.txt:
          Policy CMP0104 is not set: CMAKE_CUDA_ARCHITECTURES now detected for NVCC,
          empty CUDA_ARCHITECTURES not allowed.  Run "cmake --help-policy CMP0104"
          for policy details.  Use the cmake_policy command to set the policy and
          suppress this warning.

          CUDA_ARCHITECTURES is empty for target "Al".
        This warning is for project developers.  Use -Wno-dev to suppress it.

        CMake Warning:
          Manually-specified variables were not used by the project:

            CMAKE_ASM_COMPILER
            CMAKE_ASM_FLAGS

        make: warning: -j4 forced in submake: resetting jobserver mode.
        In file included from /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/include/Al.hpp:1221,
                         from /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/src/mpi_impl.cpp:28:
        /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/include/aluminum/nccl_impl.hpp: In function ‘ncclRedOp_t Al::internal::nccl::ReductionOperator2ncclRedOp(Al::ReductionOperator)’:
        /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/include/aluminum/nccl_impl.hpp:143:12: error: ‘ncclAvg’ was not declared in this scope; did you mean ‘nccl’?
          143 |     return ncclAvg;
              |            ^~~~~~~
              |            nccl
        In file included from /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/include/Al.hpp:1221,
                         from /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/src/Al.cpp:35:
        /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/include/aluminum/nccl_impl.hpp: In function ‘ncclRedOp_t Al::internal::nccl::ReductionOperator2ncclRedOp(Al::ReductionOperator)’:
        /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/include/aluminum/nccl_impl.hpp:143:12: error: ‘ncclAvg’ was not declared in this scope; did you mean ‘nccl’?
          143 |     return ncclAvg;
              |            ^~~~~~~
              |            nccl
        make[2]: *** [src/CMakeFiles/Al.dir/build.make:104: src/CMakeFiles/Al.dir/mpi_impl.cpp.o] Error 1
        make[2]: *** Waiting for unfinished jobs....
        make[2]: *** [src/CMakeFiles/Al.dir/build.make:76: src/CMakeFiles/Al.dir/Al.cpp.o] Error 1
        In file included from /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/include/Al.hpp:1221,
                         from /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/src/progress.cpp:31:
        /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/include/aluminum/nccl_impl.hpp: In function ‘ncclRedOp_t Al::internal::nccl::ReductionOperator2ncclRedOp(Al::ReductionOperator)’:
        /tmp/pip-install-z14bsv9q/bagua_b1ea10d6927a48eab006199d1dfaa765/rust/bagua-core/bagua-core-internal/third_party/Aluminum/include/aluminum/nccl_impl.hpp:143:12: error: ‘ncclAvg’ was not declared in this scope; did you mean ‘nccl’?
          143 |     return ncclAvg;
              |            ^~~~~~~
              |            nccl
        make[2]: *** [src/CMakeFiles/Al.dir/build.make:132: src/CMakeFiles/Al.dir/progress.cpp.o] Error 1
        make[1]: *** [CMakeFiles/Makefile2:958: src/CMakeFiles/Al.dir/all] Error 2
        make: *** [Makefile:146: all] Error 2
        thread 'main' panicked at '
        command did not execute successfully, got: exit status: 2

        build script failed, must exit now', /home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.48/src/lib.rs:975:5
        note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
      error: cargo failed with code: 101

      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for bagua
Failed to build bagua
ERROR: Could not build wheels for bagua, which is required to install pyproject.toml-based projects

Additional context
The provided Bagua AMI is outdated, therefore I'm not using it.

I got it to work – had to remove the bagua>=0.6 dependency.


ENH: Allow Dockerfile input from stdio

Description
This is a feature request/enhancement discussion.  The below is a IRC chat that I'd with @pixdrift the other night.  I wanted to capture the thoughts so we could discuss further here.
<pixdrift> not sure if it's been discussed, but has anyone raised buildah bud taking Dockerfile input from stdin?
<tsweeney> I don't recall a discussion on Dockerfile input from stdio, but I was buried in e-mails may have slipped my noggin.
<pixdrift> I just had a use case raised by a user, and thought it was worth mentioning
<tsweeney> It's not an issue/enhancement yet is it?
<pixdrift> they have a pipeline that constructs the Dockerfile from environmental information, and want to remove the temporary step of writing it to disk
<tsweeney> hmm, interesting.
<pixdrift> nope, was wondering if it had been discussed/dropped.. before I raise it
<pixdrift> so something like
<pixdrift> echo "<dockerfile contents>" | buildah bud --stdin
<pixdrift> the other alternative is to switch them to native buildah commands, but they want the option to output the file in some scenarios

@pixdrift feel free to add additional details or whack me if I mis-represented our discussion

@pixdrift @TomSweeneyRedHat Does
buildah bud -f /dev/stdin ~
Work?

Yeah I tried a couple of things without luck.  After that thought I'd throw this up here for a discussion.

@TomSweeneyRedHat The patch only checks size on regular files, since this is a pipe it will allow it to proceed in my patch.

Addressed by #888, closing


dispatch_sync called on queue already owned by current thread

Describe the bug
I received a crash report with that message: "dispatch_sync called on queue already owned by current thread."
It seems that the library is blocking it's own queue inside of resetKeepAlive function, calling to dispatch a task using sync method instead of async.
Enable logging at the debug level and attach/past to the issue
HubConnection.resetKeepAlive() + 460
closure #1 in HubConnection.sendKeepAlivePing() + 541
ReconnectableConnection.send(data:sendDidComplete:) + 356
protocol witness for Connection.send(data:sendDidComplete:) in conformance ReconnectableConnection + 20
HubConnection.sendKeepAlivePing() + 668
Please, let me know if you need more info.

Which version are you using?

I'm using SwiftSignalRClient (0.9.1)

Looks like a regression to https://github.com/moozzyk/SignalR-Client-Swift/pull/244. I refactored the code and moved the the async scheduling to HubConnection but the sendKeepAlivePing method is skipping this part and if the connection is reconnecting the error callback is being invoked synchonously causing the deadlock.

actually 0.9.2 was showing with Pre-release tag thats why I considered 0.9.1.


could you release the test dataset in your experiment?

You can check our notebook, the datasets are imported from hf.


724 create an ophyd device for apple 2 undulator and add i10 as a beamline

Fixes #724
Instructions to reviewer on how to test:

Confirm connection.
Confirm test pass.

Checks for reviewer

[ ] Would the PR title make sense to a scientist on a set of release notes
[ ] If a new device has been added does it follow the standards
[ ] If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
[ ] Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}

@stan-dot Thanks for all the commons, I had made all the changes except the two I had questions over.

@Relm-Arrowny please rebase, and mark outdated conversations as resolved and I think this will be ready to merge soon :)

overage XML written to file cov.xml
=========================== short test summary info ============================
FAILED tests/devices/unit_tests/test_apple2_undulator.py::test_gap_time_out_error - asyncio.exceptions.TimeoutError: mock_id_gap-gate didn't match <UndulatorGateStatus.close: 'Closed'> in 1.002s, last value <UndulatorGateStatus.open: 'Open'>
FAILED tests/devices/unit_tests/test_apple2_undulator.py::test_phase_time_out_error - asyncio.exceptions.TimeoutError: mock_phaseAxes-gate didn't match <UndulatorGateStatus.close: 'Closed'> in 1.0s, last value <UndulatorGateStatus.open: 'Open'>
FAILED tests/devices/unit_tests/test_apple2_undulator.py::test_jaw_phase_time_out_error - asyncio.exceptions.TimeoutError: mock_jaw_phase-gate didn't match <UndulatorGateStatus.close: 'Closed'> in 1.0s, last value <UndulatorGateStatus.open: 'Open'>
=========== 3 failed, 724 passed, 3 skipped, 30 deselected in 51.05s ===========
ERROR: InvocationError for command /opt/hostedtoolcache/Python/3.10.15/x64/bin/pytest -m 'not s03' --cov=dodal --cov-report term --cov-report xml:cov.xml (exited with code 1)

very odd failing test, just in python3.10.
also rebasing does not work

overage XML written to file cov.xml
=========================== short test summary info ============================
FAILED tests/devices/unit_tests/test_apple2_undulator.py::test_gap_time_out_error - asyncio.exceptions.TimeoutError: mock_id_gap-gate didn't match <UndulatorGateStatus.close: 'Closed'> in 1.002s, last value <UndulatorGateStatus.open: 'Open'>
FAILED tests/devices/unit_tests/test_apple2_undulator.py::test_phase_time_out_error - asyncio.exceptions.TimeoutError: mock_phaseAxes-gate didn't match <UndulatorGateStatus.close: 'Closed'> in 1.0s, last value <UndulatorGateStatus.open: 'Open'>
FAILED tests/devices/unit_tests/test_apple2_undulator.py::test_jaw_phase_time_out_error - asyncio.exceptions.TimeoutError: mock_jaw_phase-gate didn't match <UndulatorGateStatus.close: 'Closed'> in 1.0s, last value <UndulatorGateStatus.open: 'Open'>
=========== 3 failed, 724 passed, 3 skipped, 30 deselected in 51.05s ===========
ERROR: InvocationError for command /opt/hostedtoolcache/Python/3.10.15/x64/bin/pytest -m 'not s03' --cov=dodal --cov-report term --cov-report xml:cov.xml (exited with code 1)

very odd failing test, just in python3.10.
also rebasing does not work

This was cause by this https://github.com/python/cpython/issues/86579 but the strange thing for me is, the test should have never passed before.


Document default for proxied on cloudflare_record

This was originally requested in #4/fixed in b09befa, but was lost in the move to autogen docs (0813d55).

thanks for the PR! unfortunately, there is a little confusion here as the value from the schema does not default to false which is why this doesn't exist in the autogen'd docs (if it did, it would be automatically appended). the proxied field is not sent at all unless it is explicitly defined.

Ah, I see what you mean. I wonder if there's a way we can document this that makes sense as to the underlying behavior? When creating a record manually in your browser, the proxied field is checked by default (until you change record type to something that can't be proxied) -- so one could assume the Terraform provider would do the same barring docs to the contrary?

the provider mimics the API, not the UI. the reason is that the UI has different behaviour to account for some of the complexities in the APIs and commonly covers sharp edges for users.


DCC/CI hotkey support

I have a Logitech MX Keys keyboard, and I'd love to be able to control my monitor's brightness using its keys.  This can be achieved through DDC/CI, and indeed there are already control applications out there (which even include changing volume, contrast, input, etc.) but I haven't found any [free] ones that allow me to remap or use the brightness keys specific to the MX Keys.
ClickMonitorDDC is the closest one, but its hotkeys must include ctrl-shift.  Monitorian looks like a proper Windows 10 app.
Especially in winter when the sunlight changes so much, it'd be nice to adjust my display's brightness without having to go through annoying monitor OSD menus.
On an unrelated note, the PowerToys Keyboard Manager was a game changer -- thank you!  I frequently switch back and forth between Mac and Windows, so to be able to map the Mac keyboard shortcuts to their Windows equivalent (e.g. cmd-c to ctrl-c) has been a godsend.  And finally I can change the infuriating Firefox ctrl-d miskey to ctrl-f!

Tracked via https://github.com/microsoft/PowerToys/issues/1052

Tracked via https://github.com/microsoft/PowerToys/issues/1052

Also thanks for the kind words :)  Exactly why we built KBM

Also thanks for the kind words :)  Exactly why we built KBM


more customization and support for ios11

hmmm like you can choose whether facebook login is enabled, and rules to validate the username/password?
and there has been a change in api of CGFont
public /not inherited/ init?(_ provider: CGDataProvider)
returns an optional in ios11 sdk now

Yes, will look into this for the next version. Adding more customization is definitely the way I want to go.
Any more ideas welcome.
I think the CGFont has been changed back to NOT using optional in the newest beta.
Thanks!


Latest commit wrongly reporting binary_sensors as active

Version of the custom_component

Main with latest commit (doesn't happen with latest released version)
Installation method (hacs / manual)
hacs
Installation method of hass (venv, docker, hassio,...)
docker
Configuration

NA

Describe the bug
All binary_sensors which are not reported by the VW API are shown in HA as active.

Looking at the binary_sensors added by the integration and the related extracted information with weconnect-cli:
[climatisation] Elements: 3 items
        [climatisationStatus] (last captured 2022-10-26T13:46:55+00:00)
                State: off
                Remaining Climatization Time: 0 min
        [climatisationSettings] (last captured 2022-10-26T13:46:55+00:00)
                Target Temperature in °C: 22.0 °C
                Target Temperature in °F: 72.0 °F
                Temperature unit in car: celsius
        [windowHeatingStatus] (last captured 2022-10-26T13:46:55+00:00)
                Windows: 2 items
                        front: off
                        rear: off
[charging] Elements: 5 items
        [batteryStatus] (last captured 2022-10-26T13:46:57+00:00)
                Current SoC: 65%
                Range: 267km
        [chargingStatus] (last captured 2022-10-26T13:46:57+00:00)
                State: notReadyForCharging
                Mode: manual
                Charge Power: 0.0 kW
                Charge Rate: 0.0 km/h
                Charge Type: invalid
                Charging Settings: default
        [chargingSettings] (last captured 2022-10-26T13:46:56+00:00)
                Maximum Charge Current AC: maximum
                Auto Unlock When Charged: off
                Auto Unlock When Charged AC: off
                Target SoC: 90 %
        [chargeMode]
                Preferred charge mode: manual
                Available charge modes: [manual]
        [plugStatus] (last captured 2022-10-26T14:05:23+00:00)
                Plug: disconnected, unlocked, External Power: unavailable, Led color: none
[readiness] Elements: 1 items
        [readinessStatus]
                Connection State:
                        Is online: True
                        Battery power level: comfort
                        Daily Power Budget Available: True
                Connection Warning:
                        Insufficient Battery Level Warning: False
                        Daily Power Budget Warning: False

it seems clear that not all the information reported by HA via these binary sensors is correct according to what is reported by the VW api.
Can this please be fixed before next release?
Debug log

Add your logs here.

@mitch-dc I just updated the version and this issue still exists (and not on version 0.0.13).
I have 2 separate HA systems, one with v0.0.13 and one with v0.0.14 and this issue only happens on v0.0.14 (as it did already with main branch directly).
Not sure if this is an issue in the custom component or in the weconnnect library (or interaction between both?).
Thanks in advance for reopening this issue.


Block new music released on YouTube this week

What website(s) would this filter apply to?
youtube.com
What content should be blocked?
YouTube is showing a new section that lists new music released this week. I've not seen this before.

What options should be offered?
A filter to block this section for poeple who are not interested in music on YouTube.
Did you write a custom uBlock filter already?
No.
Additional notes
No response

Although I have not the exact same banner, the banner I see is blocked by uBlock filters.
Also, as you are logged in you can discard this message. (Click on the cross at the right top of the banner).
If the last doesn't work properly and the message keeps showing, I would advise first reporting it to uBlock.

Heya @3DWORX-SA, is that on the homepage? I don't have much experience with that page, I only use the subscriptions page.
Looks like there's no semantic information to target this specific section, and there's so many of them that maintaining specific options would be a nightmare. The following rule should remove all these dismissable sections, only keeping the classic grid:
www.youtube.com##ytd-browse[page-subtype="home"] ytd-rich-section-renderer

Hi - it's the home page but dismissing the message (X) seems to work until logging out, clearing cookies and logging in again, but it doesn't always appear immediately - perhaps only after having searched for specific music or having visited a music video page. I'll try the code and see how it works.
I thought I had got the correct semantic info for such a message - I got the best I could, but learning... If you can give me some tips I'll try send better info in future. Thanks

I thought I had got the correct semantic info for such a message - I got the best I could, but learning... If you can give me some tips I'll try send better info in future. Thanks

The fault is not yours, it's the website's authors'. All of these homepage sections use the exact same markup, so the only option would be to match on the section's title, which I refuse to do because our userbase is international. That's why I suggested a rule to remove them all, as they are all equally noisy in my opinion.

Thanks Xavier
From: Xavier Vello @.>
Sent: Friday, July 14, 2023 3:41 PM
To: letsblockit/letsblockit @.>
Cc: 3DWORX-SA @.>; State change @.>
Subject: Re: [letsblockit/letsblockit] Block new music released on YouTube this week (Issue #502)
I thought I had got the correct semantic info for such a message - I got the best I could, but learning... If you can give me some tips I'll try send better info in future. Thanks
The fault is not yours, it's the website's authors'. All of these homepage sections use the exact same markup, so the only option would be to match on the section's title, which I refuse to do because our userbase is international. That's why I suggested a rule to remove them all, as they are all equally noisy in my opinion.

Reply to this email directly, view it on GitHubhttps://github.com/letsblockit/letsblockit/issues/502#issuecomment-1635883315, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH3GLKKZBF6EROV4JELHRILXQFD7NANCNFSM6AAAAAA2DPBWKQ.
You are receiving this because you modified the open/close state.Message ID: @.***>


How to treat the output as a number?

Summary
This is not strictly an operation request as there may be a way to achieve this; I just don't know how.
I want to treat a hash output value as a hexadecimal number and represent the number in standard base64. Values are handled by default as utf-8 so "To Base64" turns the text interpretation to base64, which is not appropriate for me. Neither can I achieve this with a "From Base" (16) and a "To Base" (64), because the maximum base this operation handles is 36. Even if it were 64, there's no option to specify which base64 alphabet is used so I can't be sure of the result.
I believe the higher-level need here is to be able to treat values as numbers and not utf-8 strings, thus my title. But I'm open to any suggestion.
Example Input
apple
after a round of MD2:
8015c9542cac74759f9f7196394cc25d
Current Output with "To Base64"
ODAxNWM5NTQyY2FjNzQ3NTlmOWY3MTk2Mzk0Y2MyNWQ=
(the frequency of the M/N/W characters alone tells you the value has been interpreted as utf-8)
Desired output
gBXJVCysdHWfn3GWOUzCXQ==
(value generated with this tool)

The way we have achieved this functionality in other operations was to add an input format argument.

Would this achieve your desired functionality?

I don't know which operations have it so I couldn't try it yet, but yes, I think this would achieve the desired functionality.

@leafcutterant if you need a really bad hack in the interim this recipe might suit. Essentially regexing the hash and the converting it back. I do like your idea.
[{"op":"MD2","args":[]},{"op":"Regular expression","args":["User defined","([A-Fa-f0-9]{2})",true,true,false,false,false,false,"List matches"]},{"op":"Find / Replace","args":[{"option":"Extended (\\n, \\t, \\x...)","string":"\\n"}," ",true,false,true,false]},{"op":"From Hex","args":["Space"]},{"op":"To Base64","args":["A-Za-z0-9+/="]}]

There's a reasonably simple solution to this by using From Hex and then To Base64: https://gchq.github.io/CyberChef/#recipe=MD2()From_Hex('Auto')To_Base64('A-Za-z0-9%2B/%3D')&input=YXBwbGU
From Hex will convert the hex string output by the MD2 operation to raw bytes. To Base64 then takes those bytes and represents them as Base64.
Since the Base64 operations are so central to CyberChef, I am wary of bloating them too much with excess options. I think in this case I will close the PR without merging, but thanks to @n1073645 for implementing a solution.


digitalRead does not work

Hi there,
As an alternative to mbed-os, i wanted to try this Arduino core (with Arduino IDE v1.8.11) for the MAX32630FTHR.
This code works on an Arduino Uno, however on the MAX32630FTHR the state of the user button never changes:
`void setup() {
Serial.begin(9600);
// initialize digital pin P2_3 (User button) as an input.
pinMode(P2_3, INPUT);
}
// the loop function runs over and over again forever
void loop() {
int myValue = digitalRead(P2_3);
Serial.print("Button logic level = " );
Serial.println(myValue);
delay(1000);                       // wait for a second
}`
I am absolutely sure P2_3 is the name of the user button pin.
I wonder what i might b doing wrong?

Please configure your button pin as:
pinMode(P2_3, INPUT_PULLUP);


add 20170831 event

i don't have tool to modify the small.png file,
also have no idea about "report" function.
sorry that all i can do is these.

Thank you for your contribution.
Your code worked perfectly.
The timer will be updated soon.
Goddess bless you!

Done.


Flakey test: Model w/ valid src does not always dispatch load event in Safari 12 desktop

https://github.com/GoogleWebComponents/model-viewer/blob/master/src/test/model-viewer-element-base-spec.js#L64

Also witnessed on Firefox 62


Added purpose and requirements to readme

These sections towards the top of the readme clarify the purpose and scope of embedded-hal. It's intended to show users new to rust embedded how this project fits into the ecosystem.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @eldruin (or someone else) soon.
Please see the contribution instructions for more information.

I agree - didn't read the Rust docs.

Ok, I'll prepare a proposal about this, then.


Runtime attributes

This pull request adds readnone to 1 runtime function and readonly to a bunch of unicode functions that compare/hash arrays.

@swift-ci Please test

@swift-ci Please test

Mishal asked me to close/reopen b/c of CI issues.

Actually he just wanted me to wait a second ; ).

@swift-ci Please test

@swift-ci Please test

I should have just asked for the OS X check. I compiled and ran the tests myself.


use new ufo::Locations

Description
Update to use new ufo::Locations interface
closes #503

In soca_getvalues_mod.F90 there are two logical declarations with kind c_bool.  They are illegal in the Fortran 90 and newer versions of the standard.  Use instead:
logical(kind=1), allocatable :: time_mask(:)

In soca_getvalues_mod.F90 there are two logical declarations with kind c_bool. They are illegal in the Fortran 90 and newer versions of the standard. Use instead:
logical(kind=1), allocatable :: time_mask(:)

It's also used in ioda and ufo and probably other jedi repos, do you have a link to the documentation? Our google-fu isn't returning anything.


Bugsnag android builds

Issue Description
On the Bugsnag dashboard all the builds for android seem to be coming from production. This causes some confusion when trying to filter bugs that are just in production vs bugs that are in development.
The task is complete when we Bugsnag is successfully able to distinguish production and development builds on the dashboard.

This issue is being closed due to platform migration and may be revisited at a later date.


Add read/write PubSub integration example fhirio pipeline

Add a sample fhirio package pipeline to demonstrate usage of Read and ExecuteBundles transforms as well as integration with pubsubio.
Fixes #22305

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @msbukal

Run GoPortable PreCommit

I'm currently busy with a conference in Berlin, but the rest of my team should be helpful!

assign to next reviewer


Added images for Deploy using UI section

Added images for Deploy using UI section. I have added 8 image files.

This change is

/assign

Thank you for suggesting these new screenshots! I have a few comments for
discussion:

For the YAML file: we should use a textual code block rather than an
image. - ok, I will do this change
For the screenshot of the Kubeflow deployment UI, let's use just the
part of the screenshot that shows the input fields, as the current doc
does. That will make the screenshot smaller, make it easier to read, and
future-proof us against changes to the help text on the left. Plus, the
help text is out of date and missing some fields. - ok, I put the full
image because we write in the text that there are instructions on the left,
but we don't really show them. but if it looks too big, we can revert to
the old image
For the three login options, I'm not sure it's a good idea to have a
separate screenshot for each one, though I'm happy to hear arguments. :)
The screenshots take up a lot of room, and are subject to rapid change.
Instead, one screenshot with a clear textual guide to the options should be
enough? - the three login options will be three different sections which
will not be part of the original text. in the original text I will just
mention the three options and link them to their descriptions. see below:
  [Login with GCP Iap](#Login_with_GCP_IAPSection)
  -

  [Login with Username Password](#Login_with_UsernamePassword_Section)
  -

  [Setup Endpoint later](#Setup_endpoint_later_Section) . The reason is
  that there are different input requirements for all three options.
  -

Similarly, I don't think we need separate screenshots of buttons and
menu drop down options. Just bold text in the instructions to indicate the
button names. - I can just point the user to the image of the form and we
can remove these.
Overall, we'd like to keep the guide as short and concise as possible, but
without sacrificing clarity.
*Jayana Saldanha | *Technical Writer (Akorbi) | Cloud AI Platform Docs
*From: *Sarah Maddox<EMAIL_ADDRESS>*Date: *Wed, May 8, 2019 at 6:33 AM
*To: *kubeflow/website
*Cc: *Jazz4Code, Mention
@sarahmaddox requested changes on this pull request.

Thank you for suggesting these new screenshots! I have a few comments for
discussion:

For the YAML file: we should use a textual code block rather than an
image.
For the screenshot of the Kubeflow deployment UI, let's use just the
part of the screenshot that shows the input fields, as the current doc
does. That will make the screenshot smaller, make it easier to read, and
future-proof us against changes to the help text on the left. Plus, the
help text is out of date and missing some fields.
For the three login options, I'm not sure it's a good idea to have a
separate screenshot for each one, though I'm happy to hear arguments. :)
The screenshots take up a lot of room, and are subject to rapid change.
Instead, one screenshot with a clear textual guide to the options should be
enough?
Similarly, I don't think we need separate screenshots of buttons and
menu dropdown options. Just bold text in the instructions to indicate the
button names.
Overall, we'd like to keep the guide as short and concise as possible, but
without sacrificing clarity.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/website/pull/683#pullrequestreview-235058038,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI4UU37WC7QGEY5GGGTQED3PULJBHANCNFSM4HLLT4DA
.

I'm cc-ing @ccarpentiere, because I'll be getting on a plane tomorrow for the long trip back home, arriving Saturday morning. Christa may be able to help with reviews during that time.
/cc @ccarpentiere

Instead of continuing with this PR, how about instead uploading the required image(s) to your PR that updates the doc. That will solve the problems you're having referencing the images in that PR. Then you can just close this PR.

@jay-saldanha How are you going with this PR - are you planning to keep the images in a separate branch from the related textual changes?
On the image names: capital letters are significant - a file with caps in the name is a different file from one without caps although the letters may be the same. Please would you change all caps to lower case in all the file names. For example:
Kubeflow-deployment.PNG -> kubeflow-deployment.png
And the same for the other 2 images, for consistency.

@sarahmaddox
https://github.com/jay-saldanha/website/pull/2 I sent this PR and assigned it to you and Kunming 5 days ago.
This is the new PR with the changed images:
https://github.com/jay-saldanha/website/pull/2
About the images, they are opening fine now, so we should be good? Also the extension .PNG is capitalized by my computer and I can't really change it. It shouldn't matter, right?

https://github.com/jay-saldanha/website/pull/2 I

Hallo @jay-saldanha that PR is on your fork of the repo. Please would you update the current PR on the kubeflow/website repo (https://github.com/kubeflow/website/pull/683) rather than a PR on your own fork.

/assign @kunmingg @sarahmaddox

jay-saldanha and I have chatted about this PR and decided that I'll take this work over, making use of the content from the two PRs mentioned in the comments. Thanks so much for your contributions @jay-saldanha - the material you've added will be very useful in creating a followup PR!
/close


Incorrect airport names

KSFO = "International Airport", so does KLAX. They look to be defined wrong in stations.json.

I'm currently looking for a new downloadable source for the base dataset. Also working on a script to pull data from APOA for that info and runways, but that will only work for airports in the US.
And the data can be cleaned up in general. The airport elevation is in meters, but the runway lengths are in feet.

What was the original source? I also noticed that some newer airports are not included, like LTFM.

I believe I grabbed it from a GeoNames server in 2015/16 but the link has been lost to me

Same with Newark

The station list has been updated with d31ca0e using http://ourairports.com/data/ as the airport and runway data source. There are some new keys minor changes. For example:
{
    "city": "San Francisco",
    "country": "US",
    "elevation_ft": 13,
    "elevation_m": 4,
    "iata": "SFO",
    "icao": "KSFO",
    "latitude": 37.61899948120117,
    "longitude": -122.375,
    "name": "San Francisco International Airport",
    "note": "QSF, QBA",
    "runways": [
        {
            "ident1": "10L",
            "ident2": "28R",
            "length_ft": 11870,
            "width_ft": 200
        },
        {
            "ident1": "10R",
            "ident2": "28L",
            "length_ft": 10602,
            "width_ft": 200
        },
        {
            "ident1": "01R",
            "ident2": "19L",
            "length_ft": 8648,
            "width_ft": 200
        },
        {
            "ident1": "01L",
            "ident2": "19R",
            "length_ft": 7500,
            "width_ft": 200
        }
    ],
    "state": "CA",
    "type": "large_airport",
    "website": "http://www.flysfo.com/",
    "wiki": "http://en.wikipedia.org/wiki/San_Francisco_International_Airport"
}

This is currently part of 1.1b2 pending an update to the documentation.

Released in v1.1


fix: use from   __future__   import annotations

Reference Issues/PRs
Closes #83
What does this implement/fix? Explain your changes.
This PR adds a from __future__ import annotations import to all files so that we can avoid using string-typed annotations

@eddiebergman is this how you envisioned things when you created #83 ? I added a ruff rule (as in amltk) that automatically adds the from __future__ import annotations import  & fixed the relevant annotation

Sure, looks good, although there'd be some effort to update the typing then. I've had success with using things like pyupgrade before... but ruff has it too and can apply it automatically ;)


🐞 [BUG_LP] - Footer Company Section buttons direct to the top of the page not to the different sections it is meant to

Description of the bug. ✍🏻
Normally, in the footer section, there are buttons that should direct users to different sections or areas of the page when clicked. However, in this case, when these buttons are clicked, instead of navigating to the intended sections, they redirect users to the top of the page.
Current Behaviour
The button when clicked redirects to the top of the page, not to the sections intended.
Expected Behaviour
When the button is clicked it should redirect us to the particular sections in the page as intended.
Reproduction Steps
1. Scroll down the landing page to 'Footer'
2. Click on 'buttons in the Company section'
3. See error

Screenshots

Additional information
No response
Contributor terms

[X] I agree to follow the Contributing Instructions

Please assign me this issue under GSSoc'23


Restore tar prereq for hypershift

Restores a prerequisite for running the Hypershift log dump.
ref: https://issues.redhat.com/browse/ACM-16255

/cc @dislbenn

/cherry-pick backplane-2.7

/cherry-pick backplane-2.6

/cherry-pick backplane-2.5


Remove temporary vtk files generated

Need a strategy to create temporary files (in particular .vtk) to save some CPU memory and space during Data Assimilation of ERT data.
ERT data assimilation generate:

a vtk file for the converted mesh ER attribute
a vtk file for the converted and interpolated mesh ER attribute

Those file are not used except for checking interpolation quality.
Same apply to the CATHY outputs. Would be interesting to store them in a tmp folder especially when running simulation on a Jupyter Notebook/ binder environement.

All vtk files from mapping operations are now removed by default


Pytest Warnings: SQLAlchemy Deprecated Features

Description
SQLAlchemy deprecated features are being used and pytest gives us warnings about it.
Expected Behaviour
No warnings are present in pytest
Actual Behaviour
tests/adventureworks/conftest.py:80
  /home/neal/workspace/pypreql/tests/adventureworks/conftest.py:80: DeprecationWarning: invalid escape sequence '\S'
    connection_string = f"Trusted_Connection=YES;TrustServerCertificate=YES;DRIVER={{ODBC Driver 18 for SQL Server}};SERVER={gethostname()}\SQLEXPRESS"

tests/adventureworks/test_adventureworks.py::test_finance_queries
  /home/neal/workspace/pypreql/tests/adventureworks/conftest.py:87: RemovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings.  Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
    engine.engine.execute("select 1").fetchall()

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================================================== 34 passed, 2 warnings in 17.45s ===========================================================```

## Steps to Reproduce

pytest test -m tests/..

## Checklist

<!-- TODO: Update the link below to point to your project's contributing guidelines -->
- [ ] I have read the [contributing guidelines](https://github.com/wayfair-incubator/oss-template/blob/main/CONTRIBUTING.md)
- [ ] I have verified this does not duplicate an existing issue

Currently blocked on resolving all of these by the BQ dialect, which is <2.0 only -> https://github.com/googleapis/python-bigquery-sqlalchemy

Kidding, have a PR up.


About test store

have any idea what can possible test a store (someone like redux-mocha-test-generators)?

for react, use redux-devtools
for dva, maybe just console.log


Docs regarding setState are in direct conflict with one another

In Introducting Hooks, and several other places, there is a simple counter example that illustrates how to use the useState hook.
function Example() {
  // Declare a new state variable, which we'll call "count"
  const [count, setCount] = useState(0);

  return (

You clicked {count} times

      <button onClick={() => setCount(count + 1)}>
        Click me
      </button>

  );
}

However, there happens to be another counter example in the Hooks API Reference for useState.
function Counter({initialCount}) {
  const [count, setCount] = useState(initialCount);
  return (
    <>
      Count: {count}
      <button onClick={() => setCount(initialCount)}>Reset</button>
      <button onClick={() => setCount(prevCount => prevCount - 1)}>-</button>
      <button onClick={() => setCount(prevCount => prevCount + 1)}>+</button>
    </>
  );
}

In this second example, a callback is being passed into the setState function, and the code is accompanied by the following language...

The ”+” and ”-” buttons use the functional form, because the updated value is based on the previous value.

This would imply that the first example (which is in a very prominent location in the docs by the way), is actually incorrect and is encouraging an anti-pattern.
I hope you can see how these two examples are in direct conflict with one another and might be causing confusion in the community!

Yeah, we're addressing this in the ongoing docs rewrite.

test comment

hey

hey

fe


from future import absolute_import

Modify the import statements to be compatible with Python 3's requirement for absolute imports.

Also ran isort on the modified files to standardized the order of imports to improve readability.

Postponing this to the next sprint.

Due to an another project moving this to the next sprint.

Closing as these issues seem to have been fixed elsewhere.


Matching jwt token against a regex

When creating a JwtSecurityToken from a json string, we match it against a regex. Investigate whether that matching is required or just validating the max length of token and base64 decoding is good enough.

To allow for base64 encoded JWT with equals signs and RS256 signatures, the JsonCompactSerializationRegex in JwtConstants.cs should be set to:
    /// <summary>
    /// Token format: 'header.payload.signature'. Signature is optional, but '.' is required.
    /// </summary>
    public const string JsonCompactSerializationRegex = @"^[A-Za-z0-9-_=]+\.[A-Za-z0-9-_=]+\.?[A-Za-z0-9-_.+/=]*$";

The comment says that the second period is required, but my reading of the spec says otherwise, so the above regex allows for optional second period.
7.2. Validating a JWT
When validating a JWT, the following steps are performed. The order of the steps is not significant in cases where there are no dependencies between the inputs and outputs of the steps. If any of the listed steps fail, then the JWT MUST be rejected -- that is, treated by the application as an invalid input.
Verify that the JWT contains at least one period ('.') character.

To handle this condition, JwtSecurityToken.cs Decode method could be modified to append trailing period, of there is only one present:
   /// <summary>
    /// Decodes the string into the header, payload and signature
    /// </summary>
    /// <param name="jwtEncodedString">Base64Url encoded string.</param>
    internal void Decode(string jwtEncodedString)
    {
        if (jwtEncodedString.Split(new char[] { '.' }).Length == 2)
        {
            jwtEncodedString += ".";
        }
        string[] tokenParts = jwtEncodedString.Split(new char[] { '.' }, 4);

We are past RC1, pushing it to RC2.

This seems like a pretty critical bug to me.  There are many correctly formatted tokens that currently cannot be read or validated by the JwtSecurityTokenHandler (and incorrectly formatted tokens that will pass).
What is the timeframe for RC2?

@tgitchel RC2 is scheduled for early Feb 2016. We got to know the tentative dates yesterday only.

The original issue was to investigate whether we need to have regex or not. If we do, then what should be the default timeout? Based on our discussion, it seems that we need the regex to find out if the incoming token is a valid base64url encoded string before we actually try to decode it because of perf reasons. Also, we changed the default timeout to be 100 ms from 2 s. We don't think there is a need to have this setting configurable. 100 ms looks good. Closing this issue as fixed. @brentschmaltz


Glossary link in Ionic V2 Tools documentation points to the wrong url

From @thepiyush13 on March 5, 2017 20:14
Ionic version:  (check one with "x")
[ ] 1.x
[X ] 2.x
I'm submitting a ...  (check one with "x")
[ X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Navigating to https://ionicframework.com/docs/v2/resources/#/tools and then clicking Glossary opens up the http://localhost:3003/docs/v2/resources/what-is/ which seems to be invalid. The page looks like a development url and was probably accidentally injected within the documentation.
Expected behavior:

The link should open a public page and not a localhost page
Steps to reproduce:

Related code:
insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here

Copied from original issue: driftyco/ionic#10656

From @AlQuraian on March 5, 2017 21:46
There's a repo specifically for the ionic website over here:
https://github.com/driftyco/ionic-site/

Already fixed.


Make prelaunch prompt for option when used with a group

I've setup 3 different build tasks that are interchangeable and put them in a group build. I don't want any of them to be default, but I do want to run (any) one of them at prelaunch. I haven't found a way to get vscode to prompt for the task to use at prelaunch. I was thinking something like:
prelaunch: "build"
where "build" is the name of the group instead of the name of a task, to make vscode prompt to choose one of them (pretty much like Task: Run Build Task but at prelaunch).

With 1.39 we now support ${defaultBuildTask}! If you don't have a default build task or if you have multiple default build tasks then it shows you a quick pick to choose which one.


Make a Casdoor Android SDK for Android apps to use

Assigned to @1340908470

Done at: https://github.com/casdoor/casdoor-android-sdk


Qemu version revert 6.0 to 4.2

Issue with Qemu 6.0 in TPY branch.So changing back to qemu4.2.
Tracked-On: OAM-102241
Signed-off-by: gollarx<EMAIL_ADDRESS>

Hello<EMAIL_ADDRESS>and<EMAIL_ADDRESS>please review this PR.

I have conflict when try to apply this PR on top of latest tpy branch. Please correct me if my TPY manifests is not correct.
repo init -u https://github.com/intel-innersource/os.android.bsp.manifests -b celadon/r/tpy/vertical -m r2
Here are the conflicts:
Project ./device/intel/civ/host/vm-manager
Conflicts               0003-SDE-FRP-vm-manager-start_civ.sh-changes.patch
Conflicts               0004-vm-manager-Add-BLKDISCARD-BLKDISCARDZEROES-ioctl-sup.patch
Conflicts               0006-Revert-Upgrade-the-qemu4.2-to-6.0-and-add-SRIOV-chan.patch
Project ./vendor/intel/utils
Conflicts               0001-Revert-Upgrade-the-qemu-4.2-to-6.0-patches.patch
Project ./device/intel/civ/host/vm-manager
Conflicts               0012-Support-keybox-provisioning-over-vsock.patch
Conflicts               0013-Update-start_flash_usb.sh-for-keybox-provisioning.patch
I also noticed that the changes you revert are for ADL. They should not be in TPY branch by default.

please check with this manifest PR
celadon/r/tpy/vertical --> https://github.com/intel-innersource/os.android.bsp.manifests/pull/490

In the commit message, please include the revert PR link.
https://github.com/projectceladon/vendor-intel-utils/pull/1406
https://github.com/projectceladon/vm_manager/pull/171
Also please update JIRA to give more details. Attach the email you forwarded to me.

Updated the Commit message.


Remove duplications across DebugUtils.lean, Pretty.lean and FromLean.lean

Why
#53 added some debugging API but there was also some duplicated functions across some files.
How

[ ] Separate printer functions from compilation functions
[ ] Get rid of DebugUtils.lean as it's superseded by Pretty.lean
[ ] Extract CompileM monad to a separate file to avoid cyclic import
[ ] Add the printing logic to the buildEnv function via an extra boolean parameter

Afaiu, DebugUtils.lean is for directly printing the Lean types, and Pretty.lean is for printing the Yatima types. Both are probably useful

Thanks for pointing that out! Let me fix the description


Page item and label header markup has some quirks

There's too much margin above the titles at large sizes (should probably be margin below thumbs instead).
We should override padding on labels in case a project doesn't (they are a <ul> currently).
We should allow pattern titles to wrap (not sure why we aren't).

Small

Hey @tylersticka, could I get some clarification from you on these tasks? Maybe some screenshots?

There's too much margin above the titles at large sizes (should probably be margin below thumbs instead).

Not sure what this is describing. :)

We should override padding on labels in case a project doesn't (they are a  currently).

This isn't clear to me either. :P

We should allow pattern titles to wrap (not sure why we aren't).

Is this referring to the <pre> code?
Thanks!

There's too much margin above the titles at large sizes (should probably be margin below thumbs instead).

Currently the page titles have margin above them. This is fine at small sizes:

But at larger sizes when the layout shifts, the upper margin looks kinda funky. This isn't super noticeable until you have a longer description, which we do in other projects:

We should override padding on labels in case a project doesn't (they are a <ul> currently).

The labels are inside of a <ul> element, but we aren't overriding the list display of that element in our Drizzle CSS. But if we disable or change toolkit.css, they get excess padding on the left:

This is because our toolkit.css removes padding-left from all <ul> elements. But that's fairly uncommon in our projects, so ideally our <ul> would have its left padding removed (perhaps with a utility class) to avoid this issue.

We should allow pattern titles to wrap (not sure why we aren't).

Is this referring to the <pre> code?

Nope, the pattern headings. They have a white-space: nowrap utility on them, which means longer titles won't break at narrow widths:

@mrgerardorodriguez Responses above, let me know if you have more questions.

Cool, thanks @tylersticka! 😀


Mocking not working

I try to mock an expect/actual class that implements MultiDexApplication on Android.
@Mock
val application = mock(classOf<Application>())

init {
     given(application).invocation { applicationContext }
         .thenReturn(ApplicationProvider.getApplicationContext())
}

When i try to run the code it says that no mock was generated but there is no more info about why and how to fix it.
A mock for the type Application was not generated.

    Make sure the property holding the mock is annotated with @Mock:

        @Mock
        private val myMock = mock(classOf<Application>())

io.mockative.NoSuchMockError: A mock for the type Application was not generated.

    Make sure the property holding the mock is annotated with @Mock:

        @Mock
        private val myMock = mock(classOf<Application>())

	at app//io.mockative.MocksKt.mock(Mocks.kt:17)

Hi @Nailik
Thanks for reporting this issue.
I have just released version 1.2.0 of Mockative, which features a complete rewrite of the code generation using KotlinPoet. I included code to verify the case using expect/actual interfaces, which appear to work, although I did not include adding the actual modifier to the generated interfaces.
Please try version 1.2.0 and let me know if the problem remains, in which case I'll make sure the code generator includes actual modifiers for applicable generated interfaces.

Hi @Nailik
I discovered an issue in 1.2.0 causing the generated code to be invalid. I have resolved this issue in 1.2.1, which is on its way out.

Hi again @Nailik
The reason you're not seeing any mock generated is because Mockative is only capable of generating mocks for interfaces, while you appear to be attempting to mock an open class, and there just hasn't been enough demand for implementing mock code generation for open classes yet.

So if my coder under test consumes instances of an external class I have no way to give it a mock?

I am receiving the same error.
Version: 1.2.3 (also 1.2.6 tested)
I am mocking an Interface, not the implementation.
I have still one problem, that is not similiar to the documenation. I was not able to import this plugin

id("com.google.devtools.ksp")

Stacktrace:
`io.mockative.NoSuchMockError: A mock for the type IRSAEncryptionService was not generated.
Make sure the property holding the mock is annotated with @Mock:

    @Mock
    private val myMock = mock(classOf<IRSAEncryptionService>())

at app//io.mockative.MocksKt.mock(Mocks.kt:17)
at app//de.trinamix.nirs.ssf.CommonGreetingTest.<init>(commonTest.kt:16)
at java.base@11.0.12/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base@11.0.12/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base@11.0.12/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base@11.0.12/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at app//org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:250)
at app//org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:260)
at app//org.junit.runners.BlockJUnit4ClassRunner$2.runReflectiveCall(BlockJUnit4ClassRunner.java:309)
at app//org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at app//org.junit.runners.BlockJUnit4ClassRunner.methodBlock(BlockJUnit4ClassRunner.java:306)
at app//org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at app//org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at app//org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at app//org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at app//org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at app//org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at app//org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at app//org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at app//org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at app//org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at app//org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at java.base@11.0.12/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base@11.0.12/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base@11.0.12/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base@11.0.12/java.lang.reflect.Method.invoke(Method.java:566)
at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at org.gradle.api.internal.tasks.testing.worker.TestWorker$2.run(TestWorker.java:176)
at org.gradle.api.internal.tasks.testing.worker.TestWorker.executeAndMaintainThreadName(TestWorker.java:129)
at org.gradle.api.internal.tasks.testing.worker.TestWorker.execute(TestWorker.java:100)
at org.gradle.api.internal.tasks.testing.worker.TestWorker.execute(TestWorker.java:60)
at org.gradle.process.internal.worker.child.ActionExecutionWorker.execute(ActionExecutionWorker.java:56)
at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:133)
at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:71)
at app//worker.org.gradle.process.internal.worker.GradleWorkerMain.run(GradleWorkerMain.java:69)
at app//worker.org.gradle.process.internal.worker.GradleWorkerMain.main(GradleWorkerMain.java:74)`

Hi @androideo
You mention that you're not able to import the KSP plugin. Without the KSP plugin you will not be able to use Mockative. Please ensure you can import the KSP plugin first, e.g. by reading through KSP quickstart | Kotlin.

Hi @Nillerr
I was able to import the KSP library by adding the following lines to my build.gradle.
dependencies {
    ...
    testImplementation("com.google.devtools.ksp:symbol-processing-api:1.6.21-1.0.6")
    ...
}

KSP quickstart does not help me, since I want to use your processor and not my own processor in my project. Or am I thinking wrong here?

You don't need to "import" the KSP library. You need to import the KSP plugin.
Which errors are you seeing when you've added ths KSP plugin to your build.gradle file?
plugins {
    id("com.google.devtools.ksp")
}

Thanks for the support. It is working now.
I had to explictly name the version:

id("com.google.devtools.ksp") version "1.6.21-1.0.6"


Consider moving react-scripts to devDependencies in the generated package

It is a common convention for build tools to be in devDependencies instead of dependencies. I have noticed that create-react-app generates a package.json with only dependencies, and I think the react-scripts dependency counts as a build and testing tool which can be moved to devDependencies. If this hasn't already been discussed and it's possible for us to try it, I can start a PR on the template generator.
Note that even though react-scripts generates production code, npm still considers it a build tool that is not necessary in production environments because it does not produce code that relies on native Node bindings in production. Users can still safely install devDependencies in production environments if they can't build outside of their production environment, though I feel this is uncommon with GitHub Pages and Travis being so popular.
According to the npm docs for devDependencies:

If someone is planning on downloading and using your module in their program, then they probably don't want or need to download and build the external test or documentation framework that you use.

In this case, it's best to map these additional items in a devDependencies object.

These things will be installed when doing npm link or npm install from the root of a package, and can be managed like any other npm configuration param. See npm-config for more on the topic.

For build steps that are not platform-specific, such as compiling CoffeeScript or other languages to JavaScript, use the prepare script to do this, and make the required package a devDependency.

It's been discussed numerous times before, see https://github.com/facebook/create-react-app/issues/2696.
TLDR: this solves issues for some users, and doesn't make any difference for other people. Those who don't like it can always move it to devDependencies themselves.
I don't think npm's advice is very relevant here. It is primarily concerning Node apps. CRA doesn't give you a Node app. From that perspective, all dependencies (including React) are "dev" dependencies because they're only necessary for the build: once you build the app, it has no deps at all. But putting react and react-dom in devDependencies will be just as confusing, and create those additional problems for some hosting providers. So instead we put them all in dependencies.

Thanks, what changed my mind is knowing that the react-scripts package includes polyfills that are used in production.


Question-Does SDK support broadcast two camera source at same time?

My case is the host maybe want to open both back and front camera, I tried to use Mixer to bind two cameras, but got error:
2023-08-07 15:25:34.857 12446-12817 AmazonIVS            E  Cannot attach camera device because another device is currently attached
2023-08-07 15:25:34.857 12446-12817 AmazonIVS            E  Failed to attach device 0

Hi @KunNiu, the SDK does not current support broadcasting with two camera sources at the same time. You may still be able to achieve your goal by writing your own application logic to capture the camera output and input those frames into custom image sources. We have a guide for using custom image sources that may help.


Variable explorer randomly stops updating

Description of your problem
Variable explorer randomly stops updating
What steps will reproduce the problem?
Finding a way to reproduce this problem reliably is a problem in itself
What is the expected output?
Variables in variable explorer
What do you see instead?
Variable explorer shows no variable at all, than starts working, the stops again, randomly.
Please provide any additional information below
I'm more asking for help in order to understand where the problem comes from rather than a bug fix as I'm not sure spyder is at fault here.
The setup is the following:
100+ users, each one on a PC running CentOS Linux release 7.4.1708, each user has its home directory mounted as a NFS share exported by redundant NFS servers (windows).
There is one user per PC.
Spyder is installed locally on each PC, the only remote data come from the users' NFS home directory.
When all these users start using spyder at the same time the variable explorer works randomly, sometimes it won't update at all for hours, sometimes it works like a charm, sometimes it starts and stops working automagically between two runs of the very same python script.
Reseting spyder via --reset or deleting spyder data in .config does nothing.
It seems that when the network is not under load (i.e when there are just a few users in parallel rather than 100 or more) logging in using an user account who had problems with the variable explorer, running the same script, on the same PC, will usually result in a variable explorer working as expected.
Worse than that, if an user with a non working variable explorer logs at the same time on another PC (same hardware, same software) and runs the same script, there is no correlation between the behavior of the variable explorer on these two computers.
That's why I deeply suspect that there is some weird interaction between the new variable explorer/iPython console integration and the remote NFS shares used as home directories. With the old style variable explorer/python console we never had any problem with the reload button, but unfortunately this setup is not an option anymore.
Do you have any idea on where to look at to isolate this problem and hopefully find a solution ?
Thanks!
Versions and main components

Spyder Version: 3.2.3
Python Version: Python 3.6.1
Qt Version: Qt 5.6.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 4.8.5 20150623 (Red Hat 4.8.5-16))
PyQt Version:

pipdeptree -fl | grep -i qt
PyQt5==5.8.2
python-qt==0.50
QtAwesome==0.4.4
QtPy==1.3.1
qtconsole==4.3.1
QtPy==1.3.1

Operating system:
CentOS Linux release 7.4.1708

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:
IPython >=4.0    :  6.2.0 (OK)
cython >=0.21    :  None (NOK)
jedi >=0.9.0     :  0.11.0 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
numpy >=1.7      :  1.13.1 (OK)
pandas >=0.13.1  :  0.20.2 (OK)
psutil >=0.3     :  5.3.1 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pyflakes >=0.6.0 :  1.6.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pylint >=0.25    :  1.7.2 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
rope >=0.9.4     :  0.10.7 (OK)
sphinx >=0.6.6   :  1.6.3 (OK)
sympy >=0.7.3    :  1.0 (OK)

That's why I deeply suspect that there is some weird interaction between the new variable explorer/iPython console integration and the remote NFS shares used as home directories.

We haven't tested this use case, so yes, this could be the problem.
Where is Python installed? Is it installed for each user in his/her home directory? Or are they using a global, unique Python to run Spyder and IPython?

This has happened to me sometimes but I thought it was something with my work PC because I've never seen it happen on my home desktop or laptop. Just like OP, I have no clue how to reproduce it since it happened very randomly.
When it happened, it messed up the V Explorer inside one specific console tab and restarting the kernel would usually solve it. In general, the other console tabs behaved normally.
If I recall correctly, checking any of the options in the cog menu on the V Explorer had no effect whatsoever.
Spyder version: as far as I remember, it has been happening since 3.2+ or maybe a bit older
Python version: 3.6.x
IPython >=4.0    :  6.1.0 (OK)
cython >=0.21    :  0.26.1 (OK)
jedi >=0.9.0     :  0.10.2 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
numpy >=1.7      :  1.13.3 (OK)
pandas >=0.13.1  :  0.20.3 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pyflakes >=0.6.0 :  1.6.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pylint >=0.25    :  1.7.4 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
rope >=0.9.4     :  0.10.5 (OK)
sphinx >=0.6.6   :  1.6.3 (OK)
sympy >=0.7.3    :  1.1.1 (OK)

Where is Python installed? Is it installed for each user in his/her home directory? Or are they using a global, unique Python to run Spyder and IPython?

Every PC has a full-fledge Centos installation, only the users' accounts are network dependents. Everything is configured as on a standard desktop computer, if you had a local user account on these PC you could login and notice no difference at all with any other Centos installation, and there is only one user at a time per PC.
In ~4 hours I'll have ~50 users using spyder, in the meantine if you can think of any test I could perform please tell me. Unfortunately the next opportunity to perform such test will be many weeks away (around mid november iirc).

Well, you can run this command to see what results you get after detecting a failing Variable Explorer:
get_ipython().kernel.get_namespace_view()

@ccordoba12  Aww ! I saw your comment too late ! I won't be able to give you the output of this command before mid november.
Anyway restarting the kernel seems to work, thanks @gabrielclow

My variable explorer stops updating after using "Run current cell".

@lampuiho, are you running %reset -f in your cell?

This no longer applies.


interop: deprecated @libp2p/multidim-interop in favour of @libp2p/transport-interop

With the rename that took place in https://github.com/libp2p/test-plans/pull/308 we should deprecate the previous npm package and create a new one, as well as rename the test script

Would it be possible to instead have one interop test module that contains multiple tests rather than multiple modules with a single test each?
It's a lot of boilerplate otherwise.

Good idea, I suppose we only need rename the script then.


Update themes.toml

My style, made it some time ago for my code editor and decided to post here 👍🏻. Also, nice app, found some really cool designs in it.

Sorry for the late response.
Thank you for contributing. :heart:


Error occurred while trying to proxy request after installing AGM

Hi there guys, I need some help im kinda noob at this. I am using MEAN.io boilerplate and when I run npm install @agm/core --save I get a lot of warnings related to angular/core , angular/common and also zone.js saying "You must install peer dependencies yourself.".  This is what I get after running npm install @agm/core --save :
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>butnone is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must installpeer dependencies yourself.npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependenciesyourself.npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>butnone is installed. You must install peer dependencies yourself.
+<EMAIL_ADDRESS>1 package and removed 19 packages in 16.716s

But the main problem is that when I run npm start I API connection stops working and then this error is displayed on the console:

HPM] Error occurred while trying to proxy request /api/earthquakes/date/2008-12-17 from localhost:3000 tohttp://localhost:4040 (ECONNREFUSED)

On chrome:

Failed to load resource: the server responded with a status of 504 (Gateway Timeout)

When I uninstall the package everything goes back to normal, but I cant understand what i need to do to fix this. AGM is very easy to use but i have been trying to make this work with MEAN for 2 days..

I actually managed to install the peer dependencies that where required and then AGM loaded properly, but had to be different versions from the ones that where recommended by npm. I modified the following dependencies on the package.json:
"@angular/common": "~4.3.0",
"@angular/core": "~4.3.6",
"zone.js": "^0.8.4"

This can be closed now. Btw this is my latest project running AGM:
https://github.com/miguelsaferreira/earthquakesPortugal


[ParHIP] Optimizations in parhip algorithm

This PR adds some optimization in parhip algorithm.
Reduced working time of full algorithm by ~2%.
Here are main points of this PR:

Optimized access to m_fuzzy_block_weights map by adding vector for small values
Optimized linear_probing_hashmap. Now clear method works in O(1) instead of O(|distinct keys|)
Added counting sort in node ordering functions (in sparse graphs difference can be more noticeable)
Solved one TODO. Replaced linear search in getting PEID function with upper_bound

Hi,
thanks for your input. Since 2% will most likely not be statistically significant, I will not merge the PR.
Best
Christian


Refactor cache dropout

Move rdb_cache to rdb_port
Not to recreate rdb_port on storage init
Not to rollback on new proposal

https://imgur.com/9x4bbWi.png

Or to add flag into dbcontext, that shows if changes were made. If so to drop cache, otherwise skip.


fix: improve sidebar navigation collapse logic

Key changes made:

Added a new isPathActive helper function that checks if a link or any of its children match the current path
Modified the initial state logic to:
-- Always keep top-level items expanded (level 0)
-- For nested levels, expand items only if they or their children are active
-- Recursively process all nested levels

This solution will:

Keep top-level sidebar headings open by default
Collapse nested levels by default
Expand the entire path to the currently active page
Maintain the existing collapse/expand toggle functionality

The changes focus on the initial state calculation while preserving all other functionality. The solution uses the normalized path comparison that was already in place and works with the existing navigation structure.

This gives me consistent collapse logic, which is a major improvement over what we had before. It also successfully expands the active page. It could use 2 improvements though.
Right now it appears that second level items (the first nested level, which can have href or children) default to expanded. On the build tree, this makes the ARIO Class item take up the entire sidebar and user's have to scroll to see any other categories. Second level items should default to closed unless a user is in one of those nested pages.
When clicking to a new page, the "sections" for that page start collapsed. They do expand if you then refresh the page. The "sections" should default to expanded.

Right now it appears that second level items (the first nested level, which can have href or children) default to expanded. On the build tree, this makes the ARIO Class item take up the entire sidebar and user's have to scroll to see any other categories. Second level items should default to closed unless a user is in one of those nested pages.

Changes Made
1. Improved Initial State Logic

Modified setInitialStates function to handle different navigation levels appropriately:

Top-level items remain expanded by default
Second-level items now default to collapsed unless they contain the active page
Deeper nested levels expand only when containing the active page

2. Fixed Section Expansion

Moved section handling logic into a dedicated useEffect hook
Ensures sections stay expanded when navigating between pages

3. Code Cleanup

Removed unnecessary comments
Improved some of the code organization


Ships are rendered incorrectly

On the left is the server-side version of me (with debug mode):

As you can see, the ship's glow layer should be all the way in the back.

see comment in #33


Dependency test failures fix for Reflections from 0.9.11 to 0.10.2

Fix for failures in https://github.com/apache/pinot/pull/9076
#12880
Include, Exclude are no longer supported. They are deprecated in 0.10.2. Used suggested method includePattern instead

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 0.00%. Comparing base (59551e4) to head (605d870).
Report is 281 commits behind head on master.

Files
Patch %
Lines

...g/apache/pinot/spi/utils/PinotReflectionUtils.java
0.00%
3 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #12885       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2427        -9
  Lines        133233   132771      -462
  Branches      20636    20556       -80
=============================================
- Hits          82274        0    -82274
- Misses        44911   132771    +87860
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <0.00%> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <0.00%> (ø)

java-11
?

java-21
0.00% <0.00%> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <0.00%> (-61.75%)
:arrow_down:

skip-bytebuffers-true
?

temurin
0.00% <0.00%> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


【export error】模型推理，预先可以导出onnx，插入act量化算子后导出失败

Exporting the operator _fake_quantize_learnable_per_tensor_affine to ONNX opset version 9 is not supported.

@imyzx2017  Hi, have you already solved this problem? I met the same problem.


Don't send InvalidQuery exceptions to Errbit

This exception is triggered by a user error and should not be sent to errbit. Currently it is, causing unnecessary emails to developers and error-blindness.
Ignores errors like:
https://errbit.publishing.service.gov.uk/apps/539849ba0da115be230008b7/problems/56fd109165786342b80e1a00
Trello: https://trello.com/c/MC4qYvTV

cc @MatMoore

:+1:


Store command statuses

Current coverage is 75.80%

Merging #114 into master will decrease coverage by -1.46% as of 0f79f49

@@            master   #114   diff @@
=====================================
  Files           71     73     +2
  Stmts         2278   2327    +49
  Branches       271    273     +2
  Methods
=====================================
+ Hit           1760   1764     +4
  Partial         97     97
- Missed         421    466    +45

Review entire Coverage Diff as of 0f79f49

Powered by Codecov. Updated on successful CI builds.

@AlexanderLitus, please see TODOs related to storages. If you can address them in this PR, it would be good.

@alexander-yevsyukov, PTAL. If it is OK, then this PR can be merged.

@AlexanderLitus, please have checkTimestamp() in Validate class.