BLD: Fix default GPU toolchain

Fixes:

Currently building GPU package from source fails outside of the docker container. The default toolchain was the one using devtoolset-7 and is specific to that container. See https://github.com/tensorflow/addons/issues/445#issuecomment-524651126. Now the default GPU toolchain will find the include directories for the host compiler and CUDA install.
More recent bazel versions require cc_toolchain to utilize a cc_toolchain_config. It was already being used on the manylinux2010 toolchain: https://github.com/tensorflow/addons/blob/master/build_deps/toolchains/gcc7_manylinux2010-nvcc-cuda10.0/BUILD#L51

Cleans:

Move all toolchains into a single directory
Remove some unnecessary toolchain configs that we do not support.

cc @lukaszgrad would you mind testing this branch for building out of the docker container. I tested on my host and using the release scripts and seems good.

Ping the community here to see if someone else can confirm they're able to build GPU Addons from source with this PR. This isn't needed for any release, but it would be smart to merge/fix this before a full TF2 release.

I'm sorry @seanpmorgan for not reaching earlier. I've tried to build it and got the error during bazel build:
Starting local Bazel server and connecting to it...
................................................................
ERROR: no such package '@local_config_cuda//crosstool': Traceback (most recent call last):
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 1329
                _create_local_cuda_repository(repository_ctx)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 1131, in _create_local_cuda_repository
                _get_cuda_config(repository_ctx)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 942, in _get_cuda_config
                cuda_toolkit_path(repository_ctx)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 419, in cuda_toolkit_path
                auto_configure_fail("Cannot find cuda toolkit path.")
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 343, in auto_configure_fail
                fail(("\n%sCuda Configuration Error:%...)))

Cuda Configuration Error: Cannot find cuda toolkit path.

I have recently installed cuda 10.1 and I don't know if it's a problem, since tf-addons officialy require 10.0 version (I still have cuda 10.0 paths and installation preserved in the system).

Some progress has been made, it has started to build :)
WARNING: /home/lukasz/.cache/bazel/_bazel_lukasz/b35ea0e68412db7d60dbb10fd25e4022/external/local_config_tf/BUILD:3588:1: target 'ensorflow_framework' is both a rule and a file; please choose another name for the rule
ERROR: /home/lukasz/.cache/bazel/_bazel_lukasz/b35ea0e68412db7d60dbb10fd25e4022/external/local_config_tf/BUILD:13:12: in srcs attribute of cc_library rule @local_config_tf//:libtensorflow_framework: '@local_config_tf//:ensorflow_framework' does not produce any cc_library srcs files (expected .cc, .cpp, .cxx, .c++, .C, .c, .h, .hh, .hpp, .ipp, .hxx, .inc, .S, .s, .asm, .a, .lib, .pic.a, .lo, .pic.lo, .so, .dylib, .dll, .o or .pic.o)
ERROR: Analysis of target '//:build_pip_pkg' failed; build aborted: Analysis of target '@local_config_tf//:libtensorflow_framework' failed; build aborted
INFO: Elapsed time: 0.253s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)

Hmmm ensorflow_framework means that the shared object name was not being properly parsed here:
https://github.com/tensorflow/addons/blob/master/configure.sh#L32 (not part of this PR)
Are you running ./configure.sh? It feels like that was ran against  TF1.13 or earlier.

@lukaszgrad Hi, can you try to run ./configure.sh as suggested by @seanpmorgan ? Thank you :-) I'd like to merge the PR if everything is OK.

I can build GPU addons from source with this patch.

(tensorflow-gpu-prev) sebastien@sebastien-desktop:~/Downloads$ git clone https://github.com/seanpmorgan/addons.git Cloning into 'addons'... remote: Enumerating objects: 2706, done. remote: Total 2706 (delta 0), reused 0 (delta 0), pack-reused 2706 Receiving objects: 100% (2706/2706), 1.42 MiB | 615.00 KiB/s, done. Resolving deltas: 100% (1709/1709), done.
(tensorflow-gpu-prev) sebastien@sebastien-desktop:~/Downloads$ cd addons
(tensorflow-gpu-prev) sebastien@sebastien-desktop:~/Downloads/addons$ export TF_NEED_CUDA=1
(tensorflow-gpu-prev) sebastien@sebastien-desktop:~/Downloads/addons$ git checkout bld-fix-and-cleanup Branch 'bld-fix-and-cleanup' set up to track remote branch 'bld-fix-and-cleanup' from 'origin'. Switched to a new branch 'bld-fix-and-cleanup'
(tensorflow-gpu-prev) sebastien@sebastien-desktop:~/Downloads/addons$ ./configure.sh Tensorflow 2.0 will be installed if it is not already. Are You Sure? [y/n] y Installing... Collecting tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802 (from -r build_deps/requirements_gpu.txt (line 2))   Downloading https://files.pythonhosted.org/packages/12/a9/d49b70de8888e8d14e96df9cee131396ecf137d9ce4f56b6d6a9f5351941/tf_nightly_gpu_2.0_preview-2.0.0.dev20190930-cp37-cp37m-manylinux2010_x86_64.whl (393.4MB)      |████████████████████████████████| 393.4MB 117kB/s  Collecting tensorflow-estimator-2.0-preview (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2))   Downloading https://files.pythonhosted.org/packages/db/f5/790508e193121ab301cb40cada7f451c531404051ac9249f21b1f5484450/tensorflow_estimator_2.0_preview-2.0.0-py2.py3-none-any.whl (449kB)      |████████████████████████████████| 450kB 16kB/s  Requirement already satisfied: google-pasta>=0.1.6 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (0.1.7) Requirement already satisfied: wheel>=0.26; python_version >= "3" in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (0.33.4) Collecting keras-applications>=1.0.8 (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2))   Using cached https://files.pythonhosted.org/packages/71/e3/19762fdfc62877ae9102edf6342d71b28fbfd9dea3d2f96a882ce099b03f/Keras_Applications-1.0.8-py3-none-any.whl Requirement already satisfied: opt-einsum>=2.3.2 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (2.3.2) Requirement already satisfied: six>=1.10.0 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (1.12.0) Requirement already satisfied: numpy<2.0,>=1.16.0 in /home/sebastien/.local/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (1.16.4) Requirement already satisfied: wrapt>=1.11.1 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (1.11.2) Requirement already satisfied: absl-py>=0.7.0 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (0.7.1) Requirement already satisfied: protobuf>=3.6.1 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (3.8.0) Collecting tb-nightly<2.2.0a0,>=2.1.0a0 (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2))   Downloading https://files.pythonhosted.org/packages/39/b9/a15725995240548f7b9110890d9014ad5097a64ef7617866ebd86a087de2/tb_nightly-2.1.0a20190930-py3-none-any.whl (3.8MB)      |████████████████████████████████| 3.8MB 609kB/s  Requirement already satisfied: grpcio>=1.8.6 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (1.21.1) Requirement already satisfied: termcolor>=1.1.0 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (1.1.0) Requirement already satisfied: gast==0.2.2 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (0.2.2) Requirement already satisfied: astor>=0.6.0 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (0.8.0) Collecting keras-preprocessing>=1.0.5 (from tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2))   Using cached https://files.pythonhosted.org/packages/28/6a/8c1f62c37212d9fc441a7e26736df51ce6f0e38455816445471f10da4f0a/Keras_Preprocessing-1.1.0-py2.py3-none-any.whl Requirement already satisfied: h5py in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from keras-applications>=1.0.8->tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (2.9.0) Requirement already satisfied: setuptools in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from protobuf>=3.6.1->tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (41.0.1) Requirement already satisfied: markdown>=2.6.8 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tb-nightly<2.2.0a0,>=2.1.0a0->tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (3.1.1) Requirement already satisfied: werkzeug>=0.11.15 in /home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages (from tb-nightly<2.2.0a0,>=2.1.0a0->tf-nightly-gpu-2.0-preview>=2.0.0.dev20190802->-r build_deps/requirements_gpu.txt (line 2)) (0.15.4) Installing collected packages: tensorflow-estimator-2.0-preview, keras-applications, tb-nightly, keras-preprocessing, tf-nightly-gpu-2.0-preview Successfully installed keras-applications-1.0.8 keras-preprocessing-1.1.0 tb-nightly-2.1.0a20190930 tensorflow-estimator-2.0-preview-2.0.0 tf-nightly-gpu-2.0-preview-2.0.0.dev20190930 2019-09-30 09:01:30.317963: E tensorflow/core/platform/hadoop/hadoop_file_system.cc:132] HadoopFileSystem load error: libhdfs.so: cannot open shared object file: No such file or directory 2019-09-30 09:01:32.444936: E tensorflow/core/platform/hadoop/hadoop_file_system.cc:132] HadoopFileSystem load error: libhdfs.so: cannot open shared object file: No such file or directory 2019-09-30 09:01:34.441189: E tensorflow/core/platform/hadoop/hadoop_file_system.cc:132] HadoopFileSystem load error: libhdfs.so: cannot open shared object file: No such file or directory
(tensorflow-gpu-prev) sebastien@sebastien-desktop:~/Downloads/addons$ bazel build build_pip_pkg Starting local Bazel server and connecting to it... WARNING: /home/sebastien/.cache/bazel/_bazel_sebastien/a0ed615a0e9d7b0ded4846f43e78b71b/external/local_config_tf/BUILD:245 3:1: target 'libtensorflow_framework.so.2' is both a rule and a file; please choose another name for the rule DEBUG: /home/sebastien/.cache/bazel/_bazel_sebastien/a0ed615a0e9d7b0ded4846f43e78b71b/external/bazel_tools/tools/cpp/lib_c c_configure.bzl:115:5:  Auto-Configuration Warning: 'TMP' environment variable is not set, using 'C:\Windows\Temp' as default INFO: Analyzed target //:build_pip_pkg (35 packages loaded, 362 targets configured). INFO: Found 1 target... INFO: Deleting stale sandbox base /home/sebastien/.cache/bazel/_bazel_sebastien/a0ed615a0e9d7b0ded4846f43e78b71b/sandbox ERROR: /home/sebastien/.cache/bazel/_bazel_sebastien/a0ed615a0e9d7b0ded4846f43e78b71b/external/local_config_tf/BUILD:17:1:  Executing genrule @local_config_tf//:tf_header_include failed (Exit 1) cp: cannot stat '/home/sebastien/miniconda3/envs/tensorflow-gpu-prev/lib/python3.7/site-packages/tensorflow_core/include/E igen/src/Core/arch/GPU/Half.h': No such file or directory Target //:build_pip_pkg failed to build Use --verbose_failures to see the command lines of failed build steps. ERROR: /home/sebastien/Downloads/addons/tensorflow_addons/custom_ops/activations/BUILD:74:1 Executing genrule @local_confi g_tf//:tf_header_include failed (Exit 1) INFO: Elapsed time: 18.570s, Critical Path: 11.40s INFO: 4 processes: 4 local. FAILED: Build did NOT complete successfully

@SebastienKeroack Did you run those commands in docker container?

@olesalscheider Thanks for your feedback, Niels!

@facaiy No, but i'm using miniconda as environment management

Currently building GPU package from source fails outside of the docker container.

Sorry for my oversight. I'm afraid that it might be not easy to support due to various environment, that's why we use docker container.

Currently got this error, ignore my last error, it was on different environment without some env vars set:
lukasz@grail-gpu2:~/kaggle/kaggle-recursion/tfrec/addons$ bazel build build_pip_pkg
ERROR: no such package '@local_config_cuda//crosstool': Traceback (most recent call last):
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 1329
                _create_local_cuda_repository(repository_ctx)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 1131, in _create_local_cuda_repository
                _get_cuda_config(repository_ctx)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 945, in _get_cuda_config
                _cudnn_version(repository_ctx, cudnn_install_base..., ...)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 606, in _cudnn_version
                _find_cudnn_header_dir(repository_ctx, cudnn_install_base...)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 901, in _find_cudnn_header_dir
                auto_configure_fail(("Cannot find cudnn.h under %s" ...))
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 343, in auto_configure_fail
                fail(("\n%sCuda Configuration Error:%...)))

Cuda Configuration Error: Cannot find cudnn.h under /usr/lib/x86_64-linux-gnu
INFO: Elapsed time: 0.190s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
lukasz@grail-gpu2:~/kaggle/kaggle-recursion/tfrec/addons$ ls /usr/lib/x86_64-linux-gnu/cudnn.h
/usr/lib/x86_64-linux-gnu/cudnn.h

Currently got this error, ignore my last error, it was on different environment without some env vars set:
lukasz@grail-gpu2:~/kaggle/kaggle-recursion/tfrec/addons$ bazel build build_pip_pkg
ERROR: no such package '@local_config_cuda//crosstool': Traceback (most recent call last):
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 1329
                _create_local_cuda_repository(repository_ctx)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 1131, in _create_local_cuda_repository
                _get_cuda_config(repository_ctx)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 945, in _get_cuda_config
                _cudnn_version(repository_ctx, cudnn_install_base..., ...)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 606, in _cudnn_version
                _find_cudnn_header_dir(repository_ctx, cudnn_install_base...)
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 901, in _find_cudnn_header_dir
                auto_configure_fail(("Cannot find cudnn.h under %s" ...))
        File "/home/lukasz/kaggle/kaggle-recursion/tfrec/addons/build_deps/toolchains/gpu/cuda_configure.bzl", line 343, in auto_configure_fail
                fail(("\n%sCuda Configuration Error:%...)))

Cuda Configuration Error: Cannot find cudnn.h under /usr/lib/x86_64-linux-gnu
INFO: Elapsed time: 0.190s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
lukasz@grail-gpu2:~/kaggle/kaggle-recursion/tfrec/addons$ ls /usr/lib/x86_64-linux-gnu/cudnn.h
/usr/lib/x86_64-linux-gnu/cudnn.h

I tried setting CUDNN_INSTALL_PATH directly to my cuda folder, no difference.

Could you tell us where cudnn.h is located on your machine and also what the contents of your .bazelrc file is?


get code to compile on Ubuntu Saucy

A define was forgotten for the codecs and there was a typo for
another.

@vpisarev , that should be the last nail in the coffin for http://code.opencv.org/issues/3986
The CODEC_ID_WNV typo is weird but I cannot see any reference of it on the internet so it has to be a true typo.

:+1:


native debugging does not work for tests in library module type

Running gtest-based tests both with and without native debugger works only for application module type.
When the module is of library type, debugger cannot attach to the native code.
Repro:
In build.gradle of app:

chane id 'com.android.application' -> id 'com.android.library'
comment out applicationId "com.example.myapplication"
try to run NativeTests with debugger

Result:
Depending on version of gradle, AGP etc. sth like:

Task :app:connectedDebugAndroidTest
Starting 0 tests on Pixel 6a - 13

or

Task :nativelib:connectedDebugAndroidTest FAILED
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.2.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
48 actionable tasks: 3 executed, 45 up-to-date
Test run failed to complete. Instrumentation run failed due to Process crashed.
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':nativelib:connectedDebugAndroidTest'.

Expected behaviour: would be great to not be forced to add app boilerplate code (manifest, activity etc.) to strictly library-like modules to enable debugging. On the other hand - the price of that code is not too high, so overall prio is low.

You need to file an Android Studio bug. None of the debugger is implemented here.


check if searchText is null

I add a new action addTopNode to actionList in src\views\inborn\system\CategorySystem\DeptTree.vue.
When I click it, error from the line I have changed.
<template>
  <div class="bg-white m-4 mr-0 overflow-hidden">
    <BasicTree
      title="类别系统列表"
      toolbar
      search
      :actionList="actionList"
      :clickRowToExpand="false"
      :treeData="treeData"
      ref="treeRef"
      :replaceFields="{ key: 'id', title: 'deptName' }"
      @select="handleSelect"
    />
  </div>
</template>

    setup(_, { emit }) {
      const treeRef = ref<Nullable<TreeActionType>>(null);
      function getTree() {
        const tree = unref(treeRef);
        if (!tree) {
          throw new Error('tree is null!');
        }
        return tree;
      }

      function appendNodeByKey(parentKey: string | null = null) {
        getTree().insertNodeByKey({
          parentKey: parentKey,
          node: {
            title: '新增节点',
            key: '3',
          },
          // 往后插入
          push: 'push',
          // 往前插入
          // push:'unshift'
        });
      }
      function handlePlusSquare(node: any) {
        console.log(node);
        // 增加一级节点
        appendNodeByKey(null);
      }

      const actionList: ActionItem[] = [

        {
          // show:()=>boolean;
          render: (node) => {
            return h(PlusSquareOutlined, {
              class: 'ml-2',
              onClick: () => {
                handlePlusSquare(node);
              },
            });
          },
        },
      ];
      onMounted(() => {
        fetch();
      });
      return { treeData, treeRef, handleSelect, actionList };
    },

General

✏ Mark the necessary items without changing the structure of the PR template.

[ ] Pull request template structure not broken

Type

ℹ What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉 Put an x in the boxes that apply.

[ ] My code follows the style guidelines of this project
[ ] Is the code format correct
[ ] Is the git submission information standard?
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

I encountered this error because I dismissed :replaceFields="{ key: 'id', title: 'deptName' }" and supply data with title not the expected deptName


[PECO-1258] Don't fetch results beyond the end of dataset

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (5c5b87f) 89.10% compared to head (9c3dd7e) 88.99%.

Files
Patch %
Lines

lib/result/RowSetProvider.ts
63.63%
2 Missing and 2 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #205      +/-   ##
==========================================
- Coverage   89.10%   88.99%   -0.12%
==========================================
  Files          59       59
  Lines        1377     1381       +4
  Branches      226      230       +4
==========================================
+ Hits         1227     1229       +2
- Misses         99      100       +1
- Partials       51       52       +1

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

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (5c5b87f) 89.10% compared to head (fdaa736) 88.98%.

Files
Patch %
Lines

lib/result/RowSetProvider.ts
63.63%
2 Missing and 2 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #205      +/-   ##
==========================================
- Coverage   89.10%   88.98%   -0.13%
==========================================
  Files          59       59
  Lines        1377     1380       +3
  Branches      226      229       +3
==========================================
+ Hits         1227     1228       +1
- Misses         99      100       +1
- Partials       51       52       +1

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


Decoding returns wrong value.

Describe the bug
When decoding a dbc signal like  SG_ Service M : 11|4@0+ (1,0) [0|15] "" Vector__XXX and data like this payload: [3, 65, 13, 55, 255, 255, 255, 255] the expected output should be 1 not 8.
Additional context
@bit-dream BitUtils#extractBitRange when in big endian mode this function seems to move the start and end bit ranges. Not really sure whats up with that.

Might have an issue with dbc so triple checking first.

@agent6262 Can you possibly provide me the DBC file you are using so I can look into this? Also, could you let me know which version of the library you are using? There was a bug in the decoding function at one point, but that (should of) been fixed at this point.
When I call the extractValFromPayload function directly, with the signal parameter you have above, I get an answer of 1:
// Input parameters, in order: payload, start bit, signal length, endian, signed
let val = can.extractValFromPayload([3, 65, 13, 55, 255, 255, 255, 255],8,4,'Motorola',false)
console.log(val)

returns val = 1

I apologize for the poor wite-up on my part was (3am my time 😅). when I run the test on my dbc file extractValFromPayload gets called like this can.extractValFromPayload([3, 65, 13, 55, 255, 255, 255, 255],11,4,'Motorola',false) not can.extractValFromPayload([3, 65, 13, 55, 255, 255, 255, 255],8,4,'Motorola',false). I am curious where / how you got to startbit 8 from 11?
I am on version 2.1.0 according to the package.json.
My DBC file (line 44)
VERSION ""

NS_ :
	NS_DESC_
	CM_
	BA_DEF_
	BA_
	VAL_
	CAT_DEF_
	CAT_
	FILTER
	BA_DEF_DEF_
	EV_DATA_
	ENVVAR_DATA_
	SGTYPE_
	SGTYPE_VAL_
	BA_DEF_SGTYPE_
	BA_SGTYPE_
	SIG_TYPE_REF_
	VAL_TABLE_
	SIG_GROUP_
	SIG_VALTYPE_
	SIGTYPE_VALTYPE_
	BO_TX_BU_
	BA_DEF_REL_
	BA_REL_
	BA_DEF_DEF_REL_
	BU_SG_REL_
	BU_EV_REL_
	BU_BO_REL_
	SG_MUL_VAL_

BS_:

BU_:

BO_ 2024 OBD2: 8 Vector__XXX
 SG_ S6base : 2|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S5base : 10|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S1_PID_0D_VehicleSpeed m13 : 31|8@0+ (1,0) [0|255] "km/h" Vector__XXX
 SG_ S1_PID_11_ThrottlePosition m17 : 31|8@0+ (0.39216,0) [0|100] "%" Vector__XXX
 SG_ SS1 m1M : 23|8@0+ (1,0) [0|255] "" Vector__XXX
 SG_ Service M : 11|4@0+ (1,0) [0|15] "" Vector__XXX

SG_MUL_VAL_ 2024 S1_PID_0D_VehicleSpeed SS1 13-13;
SG_MUL_VAL_ 2024 S1_PID_11_ThrottlePosition SS1 17-17;
SG_MUL_VAL_ 2024 SS1 Service 1-1;

BO_<PHONE_NUMBER> ExtendedMultiplexMessage: 8 Vector__XXX
 SG_ S6base : 2|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S5base : 10|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S4base : 10|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S6 m2 : 2|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S5 m6 : 10|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S4 m5 : 10|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S3 m4 : 18|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S2 m4 : 10|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S1 m0M : 2|4@1+ (1,0) [0|0] "" Vector__XXX
 SG_ S0 M : 0|2@1+ (1,0) [0|0] "" Vector__XXX

BA_DEF_ BO_  "SingleFrame" INT 0 1;
BA_DEF_ SG_  "DDI" INT 0 65535;
BA_DEF_ SG_  "SigType" ENUM  "Default","Range","RangeSigned","ASCII","Discrete","Control","ReferencePGN","DTC","StringDelimiter","StringLength","StringLengthControl";
BA_DEF_ SG_  "GenSigEVName" STRING ;
BA_DEF_ SG_  "GenSigILSupport" ENUM  "No","Yes";
BA_DEF_ SG_  "GenSigSendType" ENUM  "Cyclic","OnWrite","OnWriteWithRepetition","OnChange","OnChangeWithRepetition","IfActive","IfActiveWithRepetition","NoSigSendType";
BA_DEF_ BO_  "GenMsgFastOnStart" INT 0 100000;
BA_DEF_ SG_  "GenSigInactiveValue" INT 0 0;
BA_DEF_ BO_  "GenMsgCycleTimeFast" INT 0 3600000;
BA_DEF_ BO_  "GenMsgNrOfRepetition" INT 0 1000000;
BA_DEF_ SG_  "GenSigStartValue" INT 0 10000;
BA_DEF_ BO_  "GenMsgDelayTime" INT 0 1000;
BA_DEF_ BO_  "GenMsgILSupport" ENUM  "No","Yes";
BA_DEF_ BO_  "GenMsgStartDelayTime" INT 0 100000;
BA_DEF_ BU_  "NodeLayerModules" STRING ;
BA_DEF_ BU_  "ECU" STRING ;
BA_DEF_ BU_  "NmJ1939SystemInstance" INT 0 15;
BA_DEF_ BU_  "NmJ1939System" INT 0 127;
BA_DEF_ BU_  "NmJ1939ManufacturerCode" INT 0 2047;
BA_DEF_ BU_  "NmJ1939IndustryGroup" INT 0 7;
BA_DEF_ BU_  "NmJ1939IdentityNumber" INT 0 2097151;
BA_DEF_ BU_  "NmJ1939FunctionInstance" INT 0 7;
BA_DEF_ BU_  "NmJ1939Function" INT 0 255;
BA_DEF_ BU_  "NmJ1939ECUInstance" INT 0 3;
BA_DEF_ BU_  "NmJ1939AAC" INT 0 1;
BA_DEF_ BU_  "NmStationAddress" INT 0 255;
BA_DEF_ BO_  "GenMsgSendType" ENUM  "cyclic","NotUsed","IfActive","NotUsed","NotUsed","NotUsed","NotUsed","NotUsed","noMsgSendType";
BA_DEF_ BO_  "GenMsgRequestable" INT 0 1;
BA_DEF_ BO_  "GenMsgCycleTime" INT 0 3600000;
BA_DEF_ SG_  "SPN" INT 0 524287;
BA_DEF_  "DBName" STRING ;
BA_DEF_  "BusType" STRING ;
BA_DEF_  "ProtocolType" STRING ;
BA_DEF_ BO_  "VFrameFormat" ENUM  "StandardCAN","ExtendedCAN","reserved","J1939PG";
BA_DEF_DEF_  "SingleFrame" 1;
BA_DEF_DEF_  "DDI" 0;
BA_DEF_DEF_  "SigType" "Default";
BA_DEF_DEF_  "GenSigEVName" "Env@Nodename_@Signame";
BA_DEF_DEF_  "GenSigILSupport" "Yes";
BA_DEF_DEF_  "GenSigSendType" "NoSigSendType";
BA_DEF_DEF_  "GenMsgFastOnStart" 0;
BA_DEF_DEF_  "GenSigInactiveValue" 0;
BA_DEF_DEF_  "GenMsgCycleTimeFast" 0;
BA_DEF_DEF_  "GenMsgNrOfRepetition" 0;
BA_DEF_DEF_  "GenSigStartValue" 0;
BA_DEF_DEF_  "GenMsgDelayTime" 0;
BA_DEF_DEF_  "GenMsgILSupport" "Yes";
BA_DEF_DEF_  "GenMsgStartDelayTime" 0;
BA_DEF_DEF_  "NodeLayerModules" "";
BA_DEF_DEF_  "ECU" "";
BA_DEF_DEF_  "NmJ1939SystemInstance" 0;
BA_DEF_DEF_  "NmJ1939System" 0;
BA_DEF_DEF_  "NmJ1939ManufacturerCode" 0;
BA_DEF_DEF_  "NmJ1939IndustryGroup" 0;
BA_DEF_DEF_  "NmJ1939IdentityNumber" 0;
BA_DEF_DEF_  "NmJ1939FunctionInstance" 0;
BA_DEF_DEF_  "NmJ1939Function" 0;
BA_DEF_DEF_  "NmJ1939ECUInstance" 0;
BA_DEF_DEF_  "NmJ1939AAC" 0;
BA_DEF_DEF_  "NmStationAddress" 254;
BA_DEF_DEF_  "GenMsgSendType" "noMsgSendType";
BA_DEF_DEF_  "GenMsgRequestable" 1;
BA_DEF_DEF_  "GenMsgCycleTime" 0;
BA_DEF_DEF_  "SPN" 0;
BA_DEF_DEF_  "DBName" "";
BA_DEF_DEF_  "BusType" "CAN";
BA_DEF_DEF_  "ProtocolType" "ISO11783";
BA_DEF_DEF_  "VFrameFormat" "J1939PG";
BA_ "DBName" "ExtendedMultiplexDbc";
BA_ "VFrameFormat" BO_<PHONE_NUMBER> 3;

SG_MUL_VAL_<PHONE_NUMBER> S6 S0 2-2;
SG_MUL_VAL_<PHONE_NUMBER> S5 S1 6-6;
SG_MUL_VAL_<PHONE_NUMBER> S4 S1 5-5;
SG_MUL_VAL_<PHONE_NUMBER> S3 S1 4-4;
SG_MUL_VAL_<PHONE_NUMBER> S2 S1 4-4;
SG_MUL_VAL_<PHONE_NUMBER> S1 S0 0-0, 1-1;

My test
test('DBC_SigMulVal.dbc: Decode Multiplex signal', (done) => {
  const dbc = new Dbc();
  const fileContent = dbcReader('src/__tests__/testFiles/DBC_SigMulVal.dbc');
  const data = dbc.load(fileContent);
  const can = new Can();
  can.database = data;
  const frame = can.createFrame(2024, [3, 65, 13, 55, 255, 255, 255, 255]);
  const bndMsg = can.decode(frame);
});

@tylerbucher did the fix work, so this issue could be closed?

The changes to fix the issue I was seeing was rolled back and not included in the PR. At this time I will close this issue, but I am unsure if this issue was actually resolved or not.


[enhancement] Open link in current tab

You can only open Link in a new tab or new window but not the current tab. Would be cool to have that feature but then with the possibility to middle-click to open in a new tab(like links in pages work in browsers post 2010)

Seconded. I would be willing to donate $50 for this feature to be added.

Should notifications be opened on the current tab as well?

I think similar to how the original poster envisioned. For whatever you interact with, left-click always opens in current tab, middle click opens in new tab. Though, to be fair to current users, ideally you would leave it how it is now by default, then just add a setting so the user can set the functionality to whatever is best for their situation. I'm not sure how difficult that would be to set that up as a changeable setting.

I perfectly understand the initial idea, but I'm asking about how clicking on a "goes online" notification should behave. Should clicking a notification opens the channel in a new tab or in the current tab? I'm asking that because a notification can occur at any point.

Apologies, I misunderstood what you were asking. To your question, imo the best way to avoid the most frustration on the users end is to have notification clicks open in a new tab. Just to avoid situations where they accidentally click the notification while on a tab they are actively working on something else with. As a more general tangent, I think in an ideal scenario, being able to designate a tab as the "active stream" tab, then whenever a stream is accessed from the extension (via a left-click), it would open there. Basically having the ability to browse who's live or click the notification from any monitor, and have it open exclusively in the tab I have designated as my "active stream" tab, with the only exception being a middle click, to open in a new tab. I'm not sure how possible this part is, but would be extremely useful for my specific uses.

It could be possible. Querying tabs and update the first one being on Twitch would work. But doing that would require a new permission (tabs) or a host permission to make it work.
The initial idea is basically done but I needed more info about the notification case but it seems making an exception seems the more reasonable approach.
Anyway, I appreciate your feedback and if changes are needed, I'll update accordingly.

Glad I could be of help. Looking forward to trying it out once you publish.

@Seldszar Saw the new version was published, quick turn around. Donated the $50.   When I try to pack the unzipped file via chrome extension management, it gives an error for it not finding the manifest.json. I found that in the overrides folder for chrome, get a different error. I figured I'd just ask you before delving too far down the rabbit hole, potentially unnecessarily.

If you're trying to download the source repository, that'll not work because you have to build from sources.
If you don't want to build it from sources, you can download one of the Action artifacts (1.15.0 for example: https://github.com/Seldszar/Gumbo/actions/runs/2955960134) or wait until it's available on Chrome Webstore.

Action artifact got it working. Thanks for the help. If you manage to get the other idea I had working, I'll send another $50.


Add the ability to edit karpenter messageKey (message field within message)

Tell us about your request
In configmap-logging.yaml under zap-logger-config, please make the messageKey configurable.
like you did to encoding here: https://github.com/aws/karpenter/pull/1648
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
When using logEncoding json with karpenter the logs look like:
{"level":"DEBUG","time":"2023-04-23T13:40:59.737Z","logger":"controller.node_state","message":"discovered EC2 instance types zonal offerings for subnets","commit":"dc3af1a"}

As you can see, there is a "message" field inside the log, when parsing this field in Logstash, it is overwriting the default message field which contain the full log message.
You can see it is pretty hard to solve that issue in that discussion:
https://discuss.elastic.co/t/message-field-within-message/58051
I think the default value for messageKey shouldn't be "message" but anyway it has to be configurable via values.yaml
Are you currently working around this issue?
I changed the configmap manually in order to change the messageKey:
data:
  zap-logger-config: |
    {
      "level": "{{ .Values.logLevel }}",
      "development": false,
      "disableStacktrace": true,
      "disableCaller": true,
      "sampling": {
        "initial": 100,
        "thereafter": 100
      },
      "outputPaths": [{{ include "karpenter.controller.outputPathsList" . }}],
      "errorOutputPaths": [{{ include "karpenter.controller.errorOutputPathsList" . }}],
      "encoding": "{{ .Values.logEncoding }}",
      "encoderConfig": {
        "timeKey": "time",
        "levelKey": "level",
        "nameKey": "logger",
        "callerKey": "caller",
        "messageKey": "app_message",
        "stacktraceKey": "stacktrace",
        "levelEncoder": "capital",
        "timeEncoder": "iso8601"
      }
    }

Additional Context
No response
Attachments
No response
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

We've chosen to deprecate the logging configuration as part of the v1beta1 migration. In general, we are trying to lean away from surfacing this configuration directly and, instead, are encouraging users to utilize their log streaming pipeline to re-write the message keys if they need to.


fix(launch): only set WANDB_RUN_ID in master of volcano jobs

Fixes
Fixes WB-NNNN
Fixes #NNNN
Description
What does the PR do?

🤖 Generated by Copilot at 700e49d
Summary
🧪🔄📝

This pull request improves the testing and implementation of the KubernetesRunner class, which handles launching wandb runs on Kubernetes clusters. It updates a unit test to cover the WANDB_RUN_ID environment variable, and refactors two functions to use generators instead of recursion. It also adds a docstring comment and a debugging statement.

To test add_wandb_env well
We need WANDB_RUN_ID to tell
If the function is right
And the manifest is tight
With the variables that make wandb swell

Walkthrough

Refactor add_wandb_env and add_label_to_pods functions in kubernetes_runner.py to use generator functions instead of recursive functions (link, link)
Add docstring comment to add_wandb_env function in kubernetes_runner.py to explain the special handling of WANDB_RUN_ID and WANDB_GROUP_ID environment variables (link)
Add WANDB_RUN_ID environment variable to the env dictionary and assert its presence in the manifest in the test_add_env function in test_kubernetes.py (link, link)
Add debugging statement to print the kubernetes argument of the launch_project object in the run function of the KubernetesRunner class in kubernetes_runner.py (link)

Testing
How was this PR tested?
Checklist

[ ] Include reference to internal ticket "Fixes WB-NNNN" and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Ensure PR title compliance with the conventional commits standards

🤖 Generated by Copilot at 700e49d

To test add_wandb_env well
We need WANDB_RUN_ID to tell
If the function is right
And the manifest is tight
With the variables that make wandb swell

/fix-title


Sketch page

[ ] Add about/instructions

What text is too big? I'm using standard gov.uk styling. If we might want to switch design systems or customize it, that's something to figure out sooner.
The choice of radios is questionable here -- a dropdown might be better?

What text is too big?

This text:

👍 to moving to dropdown, that will save some space too


Update the prefer-power-assert rule for AVA assert changes

https://github.com/sindresorhus/ava/commit/e9c6cc2843e9ee6127aebb2843eafec86cb39bfc
https://github.com/sindresorhus/ava/commit/a7f50eb82d8dae4f9a7e70ae33ef71712a8fd69b

Do we want to "maintain" the plugin for previous versions of AVA, or only for the latest version? In this case, should we add t.truthy() and keep t.ok(), or should we replace the latter by the former?

Only latest AVA version. Replace the latter by the former.

Sure, sounds good to me.

It would be nice to take the opportunity to also correct the link, replace in prefer-power-assert.md:
You can do [most things] (https://github.com/sindresorhus/ava#enhanced-asserts) with this one
By:
You can do [most things] (https://github.com/sindresorhus/ava#enhanced-assertion-messages) with this one


How to accelerate inference?

Hi,
I enabled the cublas compilation option.
The problem is that not charge o process all in GRAM memory?
What is the best line command to construct and execute in a CUDA 3090 with 24GB GRAM in the more fast posibility for each model?

Take a look at #15. Minigpt4 model is composed of two models (vision and text). The vision model does not support GPU usage, but the text model (vicuna) does.
Try enabling LLAMA_CUBLAS and see if you can run part of the model on the GPU. I haven't tested these flags before, but I would assume that they would work.

@Maknee
I tried setting option(MINIGPT4_CUBLAS "minigpt4: use cuBLAS" ON) in the CMakeLists.txt.
But when i run cmake --build . --config Release,
i get this error below unfortunately : -

Any advice to deal with is highly appreciated


net: config: Initialize semaphore before it's used

Functions like setup_ipv4 or setup_ipv6 might already use the
counter semaphore, therefore it should be initialized before these
functions are called.
As a result of this issue, the network stack could stall until timeout
under certain circumstances (e.g. when OpenThread was used).
Signed-off-by: Robert Lubos<EMAIL_ADDRESS>

@jukkar This fixes the issue with OpenThread, we've discussed recently on Slack.


Expand * pattern

* would mean all the files in the current directory.
src/* would mean all the files in the src directory.
No glob support planned.

Fixed in d06c9cd.


update to test devstack

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rcrozean
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rcrozean]

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

/test

/test aws-cloud-controller-manager-1-21-presubmit


[PROFILE REVIEW]

GitHub Profile Link:-
https://github.com/VardaanAggarwal
You can also join our Discord community here
Feel free to check out other cool repositories of the Open Source Community here

I'll review it in a livestream

Hey @VardaanAggarwal
Your profile itself looks good.
Kindly note following things for improvement -

Be active on Github
You can put your social links in the center
You can also add an About Me Section


get mouse button state

Hi, I don't know if I should post this here, but I'd like to know if there's a way to know if mouse5 or mouse4 is pressed, a bit like dwForceAttack

Added an example in a1639bea1c114d010f1283ed825b711eee9f501d.
For a complete list of button codes, see my post here https://www.unknowncheats.me/forum/3855779-post889.html.


Finish upgrading to Submariner 0.12

The code dependencies have been handled, but we still need to bump the dependency:

[ ] in pkg/hub/submarineragent/manifests/operator/submariner.io-submariners-cr.yaml (the repository also needs to be changed to registry.redhat.io/rhacm2)
[ ] submver in scripts/deploy.sh

@skitt
For some reason, the issue was not closed after the patch merged.
Could be closed now.

/close


Driver for Universal Resolver

https://github.com/decentralized-identity/universal-resolver
https://medium.com/decentralized-identity/a-universal-resolver-for-self-sovereign-identifiers-48e6b4a5cc3c
https://github.com/decentralized-identity/universal-resolver/blob/master/docs/design-goals.md
https://github.com/decentralized-identity/universal-resolver/blob/master/docs/architecture-drivers.md
https://github.com/decentralized-identity/universal-resolver/blob/master/docs/api-definition.md

The drivers are implemented as docker containers.

https://github.com/decentralized-identity/universal-resolver/blob/master/docs/driver-development.md


CoinCap.io data rate refresh is very low && Missing coins in the first 100 coins (which is bad)

So I've been looking at some coins (Gulden to be exact) for 10 minutes and it stayed the same while in other websites it goes refreshed a lot during that time:

https://www.cryptocompare.com/coins/#/btc
https://www.worldcoinindex.com/coin/gulden
https://coinmarketcap.com/

IMO we should go with the initial release as is and change the provider in the second release
@OmriAharon - FYI

Data refresh seems to suck for all products. We'll close this for now.


Fix comment in parseLexicon, in CCG

Regarding to the target category, In parseLexicon function, in CCG, shouldn't it be "the first one" (or "the first category", or similar) instead of "the first line"?

@bryant1410 – yes you're right, thanks


TileSprite create => destroy => create sequence breaks Phaser

Hello. Here is a minimal reproducer:
    var xxx = game.make.tileSprite(0, 0, 256, 256, 'player');
    game.world.add(xxx);

    setTimeout(function() {
        xxx.destroy();
        setTimeout(function() {
            xxx = game.make.tileSprite(0, 0, 256, 256, 'player');
            game.world.add(xxx);
        }.bind(this), 5000);
    }.bind(this), 5000);

I've pasted it to 'create' tab here https://phaser.io/sandbox/edit/bBXJeYyG run the example and wait 10 seconds to reproduce the bug.
The delays are needed to reproduce the bug. I guess rendering should be done at least once. This bug makes TileSprites unusable for me. It wasn't observed in Phaser 2.2.0
This bug looks hard so I can't help in fixing.

Same problem if you have a tileSprite in a state, you load another state, and reload the first state again. When the tileSprite is added, there is a "Type mismatch error" on the line
"this.__tilePattern = context.createPattern(this.tilingTexture.baseTexture.source, 'repeat');" (PIXI.TilingSprite)
This problems occurs only with the version 2.3.0 of Phaser in canvas mode.
I will try to find which commits add this issue but I think it's a PIXI bug... :-(

With the last version (dev branch), it works!!!

Cool. Hope we have the fix in the next stable Phaser update. Don't known when it is planned to be released.

while waiting the new 2.3.1, should i use 2.2 instead of current version?
this bug really boring.

Yes, I think you should use the 2.2 or compile a dev version.

True the dev version fixes this issue.

Closing as this is now fixed in dev and 2.4 will be out very very soon (this week I hope)


Emojis not showing

Hi @nodeloc ,
What I am doing wrong that the emoji picker is not showing?
https://vimeo.com/1034923018/e37957784b?ts=0&share=copy
Thanks!

You have to add your custom emojis first.

Thanks! Can I import a whole standard set at once?
On Sun, 8 Dec 2024 at 06:25, NodeLoc.com @.***> wrote:

You have to add your custom emojis first.
—
Reply to this email directly, view it on GitHub
https://github.com/nodeloc/flarum-ext-my-emoji/issues/3#issuecomment-2525424648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABJXQ5GUVHOEUQZ2YJIS6D2EPJ5FAVCNFSM6AAAAABSZUQ4RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRVGQZDINRUHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I just tried to import the attached json but getting this error.
array.json


ruby version 2.7 not supported

Please complete the following fields as applicable:
Expected behaviour:
ruby 2.7 should be supported as stated in README,
or the version of big_decimal should be specified in the Gemfile
Actual behaviour:
Steps to reproduce:

switch to ruby 2.7
run migration step `rake upgrade:v2_0_0_part_1``
fails with:

/usr/local/rvm/gems/ruby-2.7.1/gems/bundler-1.17.2/lib/bundler/rubygems_integration.rb:200: warning: constant Gem::ConfigMap is deprecated
  rake aborted!
  NoMethodError: undefined method `new' for BigDecimal:Class
  /home/install/roadmap/vendor/bundle/ruby/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/object/duplicable.rb:111:in `<class:BigDecimal>'

See also https://github.com/rails/rails/issues/34822#issuecomment-608265387

@briri @xsrust we received this comment, should we add this to backlog project?

Apologies for the incorrect ruby version support specified on the Readme @nicolasfranck. The current release of DMPRoadmap 2.x supports ruby 2.4.x.
We will be moving to ruby 2.6.3 along with the upcoming upgrade to Rails 5.2 (due out later this summer)

thanks


Fix more color/ansi issues

This PR fixes #5995. It also does some additional refactoring to ensure that color can be enabled independently from general ansi codes. I tested that color codes and newlines were displayed on travis ci in github.com/swoval/swoval if I published a local version of sbt with these changes in the ci build. Using 1.4.1 reproduced the issue in #5995.  I also tested manually that the sbt interactive shell worked ok with different variations of -Dsbt.color, -Dsbt.log.format and -Dsbt.supershell.

Travis CI supports color codes but not other ansi escape sequences (this is also often true of embedded shells like in intellij or jedit)

In general, could we also try to address https://github.com/sbt/sbt/issues/5269?
We regressed to not display color in CIs (https://github.com/sbt/util/pull/184/commits/53c9b848580376544543b0732848005b37d97fd7), and the users probably shouldn't have to deal with various combination to get this working for common CIs.

I verified that colors now appear on travis without having to set any system properties.

FTR, the colors have reappeared in sbt's ci in the build that dogfoods sbt with a publishlocal: https://travis-ci.org/github/sbt/sbt/jobs/737809980


vue-router-next not support router.back ?

What problem does this feature solve?
I'm upgrading the project vue3，before that, I can use $router.back() , but now  it will error  router.go is not a function
 const router = useRouter();
 const back = () => {
      router.back();
   };
return { back };

What does the proposed API look like?
useRouter?

They have not been added yet because in previous versions, back, go and forward all were just calling their respective functions in window.history. If you were calling $router.back(), you can call history.back() instead


Bug: Neovim does not show the lualine

How to reproduce the problem
Hi guys. I tried to set up the lualine, but faced a bug: it appears only during PlugInstall process.
Actual behaviour
https://user-images.githubusercontent.com/14095146/117869605-ad30c500-b2a3-11eb-9e64-7468d081acb2.mp4

Expected behaviour
I'd like to see the lualine all the time
Aditional information
NVIM v0.5.0-dev+f8173df4d
Build type: Release
LuaJIT 2.1.0-beta3
evil_lualine.lua without changes
My init.vim config to reproduce the issue

" --------------------
" | GENERAL SETTINGS |
" --------------------

"  plugin_manager
call plug#begin()

"  colors
Plug 'tjdevries/colorbuddy.nvim'
Plug 'marko-cerovac/material.nvim', { 'branch': 'colorbuddy' }
if (has("termguicolors"))
	set termguicolors  " this variable must be enabled for colors to be applied properly
endif

" code highlight
" Plug 'nvim-treesitter/nvim-treesitter', {'do': ':TSUpdate'}  " We recommend updating the parsers on update

"  search through folder
Plug 'dyng/ctrlsf.vim'
"             ^--------------- An ack.vim alternative mimics Ctrl-Shift-F on Sublime Text 2
Plug 'kien/ctrlp.vim'
"             ^--------------- Fuzzy file, buffer, mru, tag, etc finder

"  search through file
set hlsearch "highlight search result"

"  folder tree
Plug 'kyazdani42/nvim-tree.lua'
"      file icons
Plug 'kyazdani42/nvim-web-devicons' " for file icons

"Plug 'scrooloose/nerdtree'
"             ^--------------- A tree explorer plugin for vim
"Plug 'jistr/vim-nerdtree-tabs'
"             ^--------------- NERDTree and tabs together in Vim, painlessly
"

"  global clipboard buffer
set clipboard=unnamedplus

"  line numbers
set number

"  tabs to spaces
set tabstop=2 "spaces amount for tab"
set shiftwidth=2 "amount of spaces to shift using >> and << commands"
set smartindent "use the same indent as on the line above. And some smart magic too"
"set lcs+=space:· " visualize spaces with dots

"  upper buffers/tabs line + bottom status line
Plug 'hoob3rt/lualine.nvim', { 'branch': 'master' }

"Plug 'vim-airline/vim-airline'
"Plug 'vim-airline/vim-airline-themes'
"let g:airline#extensions#tabline#enabled = 1
"!!!  git
"
set hidden

" ====================
" ^ GENERAL SETTINGS ^
" ====================

" !!!
set noswapfile
set mouse=a
set ffs=unix
" !!!

   Ruby and Rails
Plug 'tpope/vim-rails'
Plug 'vim-ruby/vim-ruby'
"!!!   rubocop
Plug 'ngmy/vim-rubocop'
Plug 'tpope/vim-obsession'
Plug 'tpope/vim-endwise'
Plug 'hwartig/vim-seeing-is-believing'
"!!!   JS
Plug 'carlitux/deoplete-ternjs'
Plug 'kchmck/vim-coffee-script'
Plug 'pangloss/vim-javascript'
Plug 'maksimr/vim-jsbeautify'
Plug 'chemzqm/vim-jsx-improve'
"   Golang
Plug 'fatih/vim-go', { 'do': ':GoUpdateBinaries' }

" =============================
" ^ LANGUAGE SPECIFIC PLUGINS ^
" =============================

call plug#end()

" ----------------------------
" | GENERAL PLUGINS SETTINGS |
" ----------------------------

" hoob3rt/lualine.nvim
"let g:lualine = {
"    \'options' : {
"    \  'theme' : 'gruvbox',
"    \  'section_separators' : ['', ''],
"    \  'component_separators' : ['', ''],
"    \  'disabled_filetypes' : [],
"    \  'icons_enabled' : v:true,
"    \},
"    \'sections' : {
"    \  'lualine_a' : [ ['mode', {'upper': v:true,},], ],
"    \  'lualine_b' : [ ['branch', {'icon': '',}, ], ],
"    \  'lualine_c' : [ ['filename', {'file_status': v:true,},], ],
"    \  'lualine_x' : [ 'encoding', 'fileformat', 'filetype' ],
"    \  'lualine_y' : [ 'progress' ],
"    \  'lualine_z' : [ 'location'  ],
"    \},
"    \'inactive_sections' : {
"    \  'lualine_a' : [  ],
"    \  'lualine_b' : [  ],
"    \  'lualine_c' : [ 'filename' ],
"    \  'lualine_x' : [ 'location' ],
"    \  'lualine_y' : [  ],
"    \  'lualine_z' : [  ],
"    \},
"    \}
"lua require("lualine").setup()
luafile /Users/mbmist/dotfiles/.config/nvim/evil_lualine.lua

" kyazdani42/nvim-tree.lua
let g:nvim_tree_side = 'left' "left by default
let g:nvim_tree_width = 25 "30 by default
let g:nvim_tree_ignore = [ '.git', 'node_modules', '.cache' ] "empty by default
let g:nvim_tree_gitignore = 1 "0 by default
let g:nvim_tree_auto_open = 1 "0 by default, opens the tree when typing `vim $DIR` or `vim`
let g:nvim_tree_auto_close = 1 "0 by default, closes the tree when it's the last window
let g:nvim_tree_auto_ignore_ft = [ 'startify', 'dashboard' ] "empty by default, don't auto open tree on specific filetypes.
let g:nvim_tree_quit_on_open = 0 "0 by default, closes the tree when you open a file
let g:nvim_tree_follow = 1 "0 by default, this option allows the cursor to be updated when entering a buffer
let g:nvim_tree_indent_markers = 1 "0 by default, this option shows indent markers when folders are open
let g:nvim_tree_hide_dotfiles = 0 "0 by default, this option hides files and folders starting with a dot `.`
let g:nvim_tree_git_hl = 1 "0 by default, will enable file highlight for git attributes (can be used without the icons).
let g:nvim_tree_root_folder_modifier = ':~' "This is the default. See :help filename-modifiers for more options
let g:nvim_tree_tab_open = 1 "0 by default, will open the tree when entering a new tab and the tree was previously open
let g:nvim_tree_width_allow_resize  = 1 "0 by default, will not resize the tree when opening a file
let g:nvim_tree_disable_netrw = 0 "1 by default, disables netrw
let g:nvim_tree_hijack_netrw = 0 "1 by default, prevents netrw from automatically opening when opening directories (but lets you keep its other utilities)
let g:nvim_tree_add_trailing = 1 "0 by default, append a trailing slash to folder names
let g:nvim_tree_group_empty = 1 " 0 by default, compact folders that only contain a single folder into one node in the file tree
let g:nvim_tree_lsp_diagnostics = 1 "0 by default, will show lsp diagnostics in the signcolumn. See :help nvim_tree_lsp_diagnostics
let g:nvim_tree_special_files = [ 'README.md', 'Makefile', 'MAKEFILE' ] " List of filenames that gets highlighted with NvimTreeSpecialFile
let g:nvim_tree_show_icons = {
    \ 'git': 1,
    \ 'folders': 1,
    \ 'files': 1,
    \ }
"If 0, do not show the icons for one of 'git' 'folder' and 'files'
"1 by default, notice that if 'files' is 1, it will only display
"if nvim-web-devicons is installed and on your runtimepath

" default will show icon by default if no icon is provided
" default shows no icon by default
let g:nvim_tree_icons = {
    \ 'default': '',
    \ 'symlink': '',
    \ 'git': {
    \   'unstaged': "✗",
    \   'staged': "✓",
    \   'unmerged': "",
    \   'renamed': "➜",
    \   'untracked': "★",
    \   'deleted': "",
    \   'ignored': "◌"
    \   },
    \ 'folder': {
    \   'default': "",
    \   'open': "",
    \   'empty': "",
    \   'empty_open': "",
    \   'symlink': "",
    \   'symlink_open': "",
    \   },
    \   'lsp': {
    \     'hint': "",
    \     'info': "",
    \     'warning': "",
    \     'error': "",
    \   }
    \ }
nnoremap <C-n> :NvimTreeToggle<CR>
nnoremap <leader>r :NvimTreeRefresh<CR>
nnoremap <leader>n :NvimTreeFindFile<CR>
" a list of groups can be found at `:help nvim_tree_highlight`
highlight NvimTreeFolderIcon guibg=blue

"  marko-cerovac/material.nvim
let g:material_style = 'deep ocean'
let g:material_flat_ui = 1
let g:material_italic_comments = 1
let g:material_italic_keywords = 1
let g:material_italic_functions = 1
let g:material_italic_variables = 0
let g:material_contrast = 1
let g:material_borders = 0
let g:material_disable_background = 0
colorscheme material

"  dyng/ctrlsf.vim
nmap     <C-F>f <Plug>CtrlSFPrompt
nmap     <C-F>n <Plug>CtrlSFCwordPath
nmap     <C-F>p <Plug>CtrlSFPwordPath

"  scrooloose/nerdtree
"let g:NERDTreeMinimalUI = 1
"let g:NERDTreeWinSize = 30
"let g:NERDTreeDirArrows = 0
"let g:NERDTreeShowHidden=1
"let g:NERDTreeIgnore = ['\.git$', '\.DS_Store$', '\.bundle$', '\.vscode$']
"let g:nerdtree_tabs_open_on_console_startup=1
"let g:nerdtree_tabs_focus_on_files = 1
"let g:nerdtree_tabs_autoclose = 1
""    Automaticaly close nvim if NERDTree is only thing left open
"autocmd bufenter * if (winnr("$") == 1 && exists("b:NERDTree") && b:NERDTree.isTabTree()) | q | endif
""    Toggle
"nnoremap <silent> <C-b> :NERDTreeToggle<CR>
"map <Leader>n :NERDTreeTabsToggle<CR>
"
""  jistr/vim-nerdtree-tabs
"let g:nerdtree_tabs_autoclose=1
"
"  kien/ctrlp.vim
let g:ctrlp_map = '<c-p>'
let g:ctrlp_cmd = 'CtrlP'
let g:ctrlp_working_path_mode = 'ra'
set wildignore+=*/tmp/*,*.so,*.swp,*.zip
let g:ctrlp_match_window_reversed = 0
let g:ctrlp_extensions = ['tag']
let g:ctrlp_custom_ignore = 'vendor\|node_modules\|tmp\|DS_Store\|.git'
"                              ^           ^        ^       "
"                             language specific folders     "
map <C-T> :CtrlPBuffer<CR>

" ============================
" ^ GENERAL PLUGINS SETTINGS ^
" ============================

"====================
"|  TIPS AND TRICS  |
"====================

"-----visualize tab with ⇥ symbol-------
"-----(tab becomes an actual tab)-------
"set list
"set listchars=tab:\⇥\ ,trail:·,extends:>,precedes:<,nbsp:+
"---------------------------------------

"-----load local dir .vimrc file--------
"set exrc
"set secure
"---------------------------------------

"====================
"^  TIPS AND TRICS  ^
"====================

happened to me to, started commenting out chunks off my init.vim to isolate the origin of the bug, found that by removing this lines:
" Statusline {{{
set statusline=%.50F\ -\ FileType:\ %y
set statusline+=%=        " Switch to the right side
set statusline+=%l    " Current line
set statusline+=/    " Separator
set statusline+=%L\   " Total lines
set showtabline=2
" }}}
it worked...

i found that setting &background after require('lualine').setup() in configurations will make the lualine disappear on nvim start.

I had the same issue where the statusline would be blank. Tried using evil_lualine with the only effect of having the statusline change background color but still be without any text. I've also tried reverting to old commits and https://github.com/hoob3rt/lualine.nvim/commit/82826ef66111f1bbdcc6f8e5bc2b19d7e0542229 is the one where the statusline breaks.

can you check what's the output of
:verbose set stl

When lualine isn't displayed ?

can you check what's the output of
:verbose set stl

When lualine isn't displayed ?
@shadmansaleh

@DDKatch can you see if you can reproduce this with a minimal config containing vimPlug and lualine only without and nothing else . Maybe some other pkugin is interfereing .
Like: put this in test.vim
call plug#begin()
Plug 'hoob3rt/lualine.nvim'
Plug 'kyazdani42/nvim-web-devicons'
call plug#end()

luafile /Users/mbmist/dotfiles/.config/nvim/evil_lualine.lua

then open nvim with nvim -u test.vim
Try :PlugInstall and see if lualine disappears or not

I have the same issue, I see that only after the update with vim-plug is executed.
My dotfiles are at github.com/mte90/dotfiles
Anyway if I run on neovim :lua require('lualine').setup() I get this:

can you check what's the output of
:verbose set stl

When lualine isn't displayed ?

It returns:
statusline=%!v:lua.require'lualine'.statusline()
        Last set from anonymous :source line 13

Anyway if I run on neovim :lua require('lualine').setup() I get this:

this is expected, you already loaded the config in your lualine config and thus loader fails. We could handle this but there is no reason ( I think ) to call the setup function more than once

@ShinKage that output looks right it should work . Can try if config example in README work . Or maybe try down;oadinga  freash copy of evil_lualine
wget https://gist.github.com/shadmansaleh/cd526bc166237a5cbd51429cc1f6291b/raw/7a4f1d7ebffd3fabe3dc56a955a9101f5d71686d/evil_lualine.lua

Looking at the code of vim plug it seems that it loads plugins after PlugUpdate. I could handle this but I would rather not. Does PlugUpdate affect your vim workflow? Let me know if this is something which makes lualine unusable for you. If so then I can dig into it more and provide a fix.

Anyway if I run on neovim :lua require('lualine').setup() I get this:

this is expected, you already loaded the config in your lualine config and thus loader fails. We could handle this but there is no reason ( I think ) to call the setup function more than once

This is no longer throws an error (https://github.com/hoob3rt/lualine.nvim/commit/9d9ee2d60ed22a603bd92afabd38e10eb15b413b)

To me is not a problem to get the plugin loaded after updating, the point is that as it is now is not working like few weeks ago.
I have a blank line and only with updating works.

I can confirm, it seems like the latest version does not display by default in neovim. I installed the plugin for the first time yesterday using the README and was not able to see the status line.
Oddly enough I did see the statusline when running :checkhealth and then it disappears once checkhealth completes.

Okay then, I will look into vim plug + lualine during the weekend

Not sure if this is helpful, but I noticed that on the latest version https://github.com/hoob3rt/lualine.nvim/commit/9d9ee2d60ed22a603bd92afabd38e10eb15b413b the status line shows up for a split second and then goes away (the status line just becomes black)

Okay I have to say this is really weird, it works perfectly fine on both linux an mac for me.
nvim version
tested with both LuaJit 2.1 & 2.0.5
NVIM v0.5.0-dev+1320-gba04b3d83
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/hubert/.cache/paru/clone/neovim-git/src/build/config -I/home/hubert/.cache/paru/clone/neovim-git/src/neovim-git/src -I/usr/include -I/home/hubert/.cache/paru/clone/neovim-git/src/build/src/nvim/auto -I/home/hubert/.cache/paru/clone/neovim-git/src/build/include
Compiled by hubert@xps

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

minimal.vim
call plug#begin(has('nvim') ? stdpath('data') . '/plugged' : '~/.vim/plugged')
Plug 'hoob3rt/lualine.nvim'
call plug#end()
lua << EOF
require'lualine'.setup{
options = {
	theme = 'nord',
	icons_enabled = false
	},
sections = {
	lualine_b = {'mode'},
	lualine_c = {'mode'}
	},
inactive_sections = {
	lualine_b = {'mode'},
	lualine_c = {'mode'}
	},
extensions = {'quickfix'}
}
EOF

screenshot

Please test it with nvim -u minimal.vim
Also update vim-plug whilte you're at it.

Hmm it works for me with the minimal vim. I'll dig in and see what's going on!

Hmm it works for me with the minimal vim. I'll dig in and see what's going on!

That's most likely a config related issue then. Lmk if you find what's causing it

@hoob3rt I'm so sorry.... I still had galaxyline in my plugins... Once I removed it worked fine.

I get the same problem... blank line for Lualine after pulling down updates. The reason is because I'm calling setup more than once to automatically adjust my colorscheme with macOS light and dark modes.
@hoob3rt what's the recommended way to change the lualine colorscheme or reload lualine at runtime?

@hoob3rt what's the recommended way to change the lualine colorscheme or reload lualine at runtime?

I've discussed this before. I presonally don't see a point to hot reloading themes. But since this came up a lot I will make it possible, preferably you should be able to reload the whole config.
While we're at it, I will also update the auto colorscheme to match your nvim's colorscheme if possible (taking the background variable into account as well)

That would be great, thank you :D
I do think it's a pretty valid use case, at sunset I'd like to have my whole system automatically switch over from day to night themes. I'm using this little plugin dark-notify to automate switching neovim themes when macOS changes between light/dark modes.

I've also have not been able to have the status line show. For debugging purposes I have this setup, where the init.vim is the one suggested by @hoob3rt:

NVIM v0.5.0-dev+nightly
 Build type: Release
 LuaJIT 2.1.0-beta3
 Compilation: /usr/bin/clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNDEBUG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/tmp/neovim-20210220-54451-1px32v0/build/config -I/tmp/neovim-20210220-54451-1px32v0/src -I/usr/local/include -I/usr/local/opt/luv/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include -I/usr/local/opt/gettext/include -I/tmp/neovim-20210220-54451-1px32v0/build/src/nvim/auto -I/tmp/neovim-20210220-54451-1px32v0/build/include
 Compiled by<EMAIL_ADDRESS>
 Features: +acl +iconv +tui
 See ":help feature-compile"

 system vimrc file: "$VIM/sysinit.vim"
 fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-1caf585_1/share/nvim"

 Run :checkhealth for more info

init.vim
call plug#begin(has('nvim') ? stdpath('data') . '/plugged' : '~/.vim/plugged')
Plug 'hoob3rt/lualine.nvim'
call plug#end()
lua << EOF
require'lualine'.setup{
options = {
	theme = 'nord',
	icons_enabled = false
	},
sections = {
	lualine_b = {'mode'},
	lualine_c = {'mode'}
	},
inactive_sections = {
	lualine_b = {'mode'},
	lualine_c = {'mode'}
	},
extensions = {'quickfix'}
}
EOF

Now when I start nvim I always get:
E15: Invalid expression: v:lua.require'lualine'.statusline()

Predictably, this is also what I get when running :lua require'lualine'.setup() in Ex mode.
Does anyone have an idea of what might be happening here?

Just another report that I also cannot get lualine to display. I'm simply using Packer:
use {'hoob3rt/lualine.nvim', config = function() require('lualine').setup({...})}

It seemed to me I had the same problem on my nvim with packer env, but then I found the line 'set laststatus=1' in my init.vim and changing it to 2 helped as expected. Check this as well if you are out of ideas

It seemed to me I had the same problem on my nvim with packer env, but then I found the line 'set laststatus=1' in my init.vim and changing it to 2 helped as expected. Check this as well if you are out of ideas

Unfortunately, I have laststatus=2 by default in all of my tests, so that doesn't fix this for me.

Well, I think I found the issue.
I use Plug as a plugin manager. So there were 2 dirs with plugins: 1) ~/.config/nvim/plugged and 2) ./local/share/nvim/plugged . I put luafiles alongside with the 1 to ~/.config/nvim/lua/lualine.lua.
And when I removed both 1 and 2 dir and reinstalled the Plug, the lualine started to work.

Well I did have one more redundancy here: here was a lua folder with lualine plugin in it (written in lua). So I removed it and installed the plugin via Plug. And It worked. The lualine works good.

I don't get back the line also with the plugins update as few weeks before.
In case can be helpful by dotfiles are there https://github.com/mte90/dotfiles

I did some tests and removing the plugin https://github.com/tjdevries/astronauta.nvim from my plugins let this plugin to works.

Could this possibly be related to the removal of line config = vim.deepcopy(require'lualine.defaults') from function setup() in 82826ef?
There doesn't appear to be any similar functionality in config.lua either, only the once off declaration of the table on module loading: local config = { ....
As the table is being initialized with default values only on module load, as opposed to on each call of setup(), maybe this explains the whacky behavior encountered when setup is called more than once.

I encountered a similar problem when switching from lightline to lualine. After removing all the old stuff from lightline, the problem disappeared. Might be worth a try.

Could this possibly be related to the removal of line config = vim.deepcopy(require'lualine.defaults') from function setup() in 82826ef?
There doesn't appear to be any similar functionality in config.lua either, only the once off declaration of the table on module loading: local config = { ....
As the table is being initialized with default values only on module load, as opposed to on each call of setup(), maybe this explains the whacky behavior encountered when setup is called more than once.

I can confirm migrate to a commit previous that one lualine is working again.

Thanks @Mte90, your suggestion worked for me! I changed the Vim-Plug import to Plug 'hoob3rt/lualine.nvim', {'commit': 'dc2c711'} to use the commit dc2c711.
The statusline used to disappear when reloading init.vim using :so %.

@vivek-dg did you try #311 or shadmansakeh/lualine.nvim ? This bug should be fixed there .

@shadmansaleh I tried shadmansakeh/lualine.nvim and it works as expected.

It seemed to me I had the same problem on my nvim with packer env, but then I found the line 'set laststatus=1' in my init.vim, and changing it to 2 helped as expected. Check this as well if you are out of ideas

Thank you so much! You saved my day.

It seemed to me I had the same problem on my nvim with packer env, but then I found the line 'set laststatus=1' in my init.vim, and changing it to 2 helped as expected. Check this as well if you are out of ideas

Thank you so much! You saved my day.

This also worked for me on a brand new install.

I solved this issue by deleting ${XDG_DATA_HOME:-$HOME/.local/share/nvim} and reseting .vim directory (I tried everything mencioned previously). I don't know if this is the best way to solve the issue, but i'm starting from zero with nvim and lua so delete everything is not a big problem in my case.
By the way it is normal that when you source the init.lua file the status line turns black? (this only happens when i source the file, it's not a big problem anyway because closing and opening nvim shows again the status line).

This is something that has been fixed in shadmansaleh/lualine.nvim #311

man, this is too hard, when i load (source%) lualine.lua  it says:
E5112: Error while creating lua chunk: lualine.lua:1: '=' expected near 'require'
Note: i have putted the word 'lua'  in front of ' require('lualine').setup'
I have also tried everything, i think i have problem with, same thing with galaxyline, and i think i will switch to airline

@artificial-equation  if you want write lua inside vimL files you should ise lua heredocs. like
lua << END
require'lualine'.setup {
  -- Your lualine config here
}
END

I recommend you checkout nvim-lua-guide to get started with lua in neovi,

i still  get an error with sourcing:
Error detected while processing /home/equation/.config/nvim/lua/minnimal.vim:
line   29:
E5108: Error executing lua vim.lua:63: /home/equation/.config/nvim/lua/lualine.lua:1: '=' expected near 'require'

Rename the lualine.lua file to a  different name.
You're causing a namespace clash for require.

It seemed to me I had the same problem on my nvim with packer env, but then I found the line 'set laststatus=1' in my init.vim and changing it to 2 helped as expected. Check this as well if you are out of ideas

Thank you @m8dotpie, you save my day


chore: add additional network logging

Add ip/port info for connected and discovered nodes in debug summary logging.
Add a file log in boot nodes

prnet cleaned-up successfully


mv mysql_pubkey.asc back to default folder

The default folder is only required on Chef < 12 so there shouldn't be any reason to move this back.


CODE RUB: Order Exception Handling and Tests In Chronological Order

Take httpRequestUrlNotFoundException and put it after system validation exception

I take it


RHOAIENG-1179 Verify user can create a workbench with an existing data connection

CI: rhods-ci-pr-test/2271
Task to create the test: https://issues.redhat.com/browse/RHOAIENG-1179
Bug ticket that's tested: https://issues.redhat.com/browse/RHODS-5700

Edit: also, it would be nice to have just one commit with a decent commit message too though 😉

I'm used to doing a squash in GitHub UI when I copy over the issue title into the squashed commit's commit message. Maybe that won't work here, given how the merge checks work and whether squash merge is even enabled in this repo.
I'll squash the commits on my own and forcepush instead.

CI rerun: rhods-ci-pr-test/2282

@jstourac new CI run, rhods-ci-pr-test/2287


changing source_id to SOURCE_ID to match change in Gaia catalog output

I tested this by running compare_catalogs.py on dark and it properly downloaded Gaia catalogs.
I then ran the following to fully calibrate the data:
lscloop.py -n 'WISEAJ075041.08-302027.1' -s psf
lscloop.py -n 'WISEAJ075041.08-302027.1' -s psfmag
lscloop.py -n 'WISEAJ075041.08-302027.1' -s zcat
lscloop.py -n 'WISEAJ075041.08-302027.1' -s mag

This resulted in calibrated r and I band filter - z band doesn't have a zero point from the apass catalog - so this will not get an apparent magnitude

@estefaniapadilla can you please test that this PR works on the supernova machine and then merge it?


Add PHPDoc for properties "request" and "response" in controllers

Add PHPDoc for request and response in web and console controllers for better auto-completion in IDE.

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues
-

No need for it. It's done automatically each release.

Hm... in IDE for web and console controllers for auto-complete use base response and request, but should be web and console response and request. Now it's not work.

OK. Let's have it but I guess it will be overwritten by doc generator anyway...

Why @property-read?


Update README.md

it is not necessary to do delete array[array.length - 1] before array.length--
https://ethereum.stackexchange.com/questions/90082/whether-it-is-necessary-delete-item-before-reduce-array-length-in-solidity/90083#90083

@2608027102 thanks!


npm start issue

I have installed the react-app-rewired package in my project.
Then I changed my start script to react-app-rewired start.
Using npm start, I'm receiving the following from the compiler:
There might be a problem with the project dependency tree.
project | It is likely not a bug in Create React App, but something you need to fix locally.
project |
project | The react-scripts package provided by Create React App requires a dependency:
project |
project |   "webpack": "4.44.2"
project |
project | Don't try to install it manually: your package manager does it automatically.
project | However, a different version of webpack was detected higher up in the tree:
project |
project |   /var/node/app/node_modules/webpack (version: 5.62.1)
project |
project | Manually installing incompatible versions is known to cause hard-to-debug issues.
project |
project | If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
project | That will permanently disable this message but you might encounter other issues.
project |
project | To fix the dependency tree, try following the steps below in the exact order:
project |
project |   1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
project |   2. Delete node_modules in your project folder.
project |   3. Remove "webpack" from dependencies and/or devDependencies in the package.json file in your project folder.
project |   4. Run npm install or yarn, depending on the package manager you use.
project |
project | In most cases, this should be enough to fix the problem.
project | If this has not helped, there are a few other things you can try:
project |
project |   5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
project |      This may help because npm has known issues with package hoisting which may get resolved in future versions.
project |
project |   6. Check if /var/node/app/node_modules/webpack is outside your project directory.
project |      For example, you might have accidentally installed something in your home folder.
project |
project |   7. Try running npm ls webpack in your project folder.
project |      This will tell you which other package (apart from the expected react-scripts) installed webpack.
project |
project | If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
project | That would permanently disable this preflight check in case you want to proceed anyway.
project |
project | P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
project |

My config-overrides.js file:
// const StylelintPlugin = require('stylelint-webpack-plugin');

module.exports = {
  webpack: function (config, env) {
    // if (env === 'development') {
    //   config.plugins.push(
    //     new StylelintPlugin({
    //       // options here
    //     }),
    //   );
    // }

    return config;
  },
};

Help?

What dependencies/devDependencies do you have listed in your package.json file?

For the stylelint-webpack-plugin, it appears that the last version of that package to support webpack 4 was version 2.2.2. If you've installed version 3, it may be pulling in webpack 5 with it. Please try downgrading styleling-webpack-plugin to version 2.2.2.

For the stylelint-webpack-plugin, it appears that the last version of that package to support webpack 4 was version 2.2.2. If you've installed version 3+, it may be pulling in webpack 5 with it. Please try downgrading styleling-webpack-plugin to version 2.2.2.

@dawnmist Why do I need to support webpack version 4 instead of 5?

Because from your original error messages, react-scripts (which holds all the create-react-app build scripts) requires you to use webpack 4, as stated here:
project | The react-scripts package provided by Create React App requires a dependency:
project |
project |   "webpack": "4.44.2"

Have the same issue. Guys, Webpack 5 is the norm in the end of 2021, please update the package to reflect it. I see that react-app-rewired requires old versions of<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>all of which require<EMAIL_ADDRESS>, but all other packages are require for<EMAIL_ADDRESS>Updating these dependencies in **react-app-rewired ** will solve the issue.

@christopanayotovvia All of the dependencies you have highlighted come from Create React App's react-scripts package, not from react-app-rewired itself. I'd suggest that you make your demands to the Create React App project upstream, as we do not have control over what packages they use.
This is the dependencies that react-app-rewired requires: https://github.com/timarney/react-app-rewired/blob/b7b4bea299c9fe67f77b736d10d1f9482dea6459/package.json#L18-L26

Closing --- as it doesn't seem to be a issue with this repo


Alarm always showing

Alarm is always showing on the highest priority even though there is no alarm active and if active alarm is present the time shown is wrong.
To Reproduce
just enable alarm in the at a glance menu
Expected behavior
Expect the alarm to show up once there is any alarm active.

Device: S22 ultra Snapdragon
OS Version: Android 12 (Oneui 4.1)
App Version v2.3.3(139)

Duplicate of #375


after deployed on live using https Bug

after this dependency use local site Working fine but after release on the server deployed the code not clickable Html editor  please find attachment

sshot.

I have the same problem


Transformation distorted for Interactive rendering (Blender 2.83+)

Bug occours with …
OS: Windows and Linux
Blender Version:  2.83 and 2.90
Blenderseed interactive rendering shows distorted transformations. Distortion occours, when  user switches Viewport Shading mode away from Material Preview mode or Render mode.
However, on older Blender 2.82a, Blenderseed interactive rendering works fine.

In Blender support chat, Ankitm mentioned @orientation_helper decorator. Some links …
https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Python_API/Modules#Orientation_Helper
https://docs.blender.org/api/current/bpy_extras.io_utils.html?highlight=orientation_helper#bpy_extras.io_utils.orientation_helper


Outdated link

Issue description
The link to Creating Service Keys is outdated and should be replaced:

Current link: Create Service Keys Using the Cockpit
New link: Creating Service Keys in Cloud Foundry

Feedback Type (Optional)
linking
Page Title on SAP Help Portal (prefilled)
Creating Service Keys
Page URL on SAP Help Portal (prefilled)
https://help.sap.com/docs/btp/sap-business-technology-platform/creating-service-keys

Thank you for your feedback! We’ll look into it and come back to you if we have any questions.

Hi @georgbischoff,
There is a redirection on the page. We can't delete that page because it is being used in many docs.
Kind regards,
Daniel

Hi,
Changed the link per feedback.
Will be released with T12b.
Thank you for your contribution @georgbischoff.


Update dependency @changesets/write to v0.3.2

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@changesets/write
0.1.9 -> 0.3.2

Release Notes

changesets/changesets
v0.3.2
Compare Source
Patch Changes

#1445 52c302a Thanks @bluwy! - Remove unused @babel/runtime dependency

v0.3.1
Compare Source
Patch Changes

#1351 c6da182 Thanks @TheHolyWaffle! - Fix an issue with not applying a custom .prettierrc configuration with prettier@>= 3.1.1

v0.3.0
Compare Source
Minor Changes

#1185 a971652 Thanks @Andarist! - package.json#exports have been added to limit what (and how) code might be imported from the package.

Patch Changes

Updated dependencies [a971652]:

<EMAIL_ADDRESS>

v0.2.3
Compare Source
Patch Changes

Updated dependencies [521205d]:

<EMAIL_ADDRESS>

v0.2.2
Compare Source
Patch Changes

#983 6cc4300 Thanks @Andarist! - Improved compatibility with the alpha releases of Prettier v3 by awaiting the .format result since it's a promise in that version.

v0.2.1
Compare Source
Patch Changes

Updated dependencies [8c08469]:

<EMAIL_ADDRESS>

v0.2.0
Compare Source
Minor Changes

#905 c140171 Thanks @Andarist! - The local version of Prettier is going to be preferred from now on when writing formatted .md files back to disk. At the same time the version of Prettier that we depend on has been upgraded.

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: pnpm-lock.yaml

added 1 package, and audited 2 packages in 695ms

found 0 vulnerabilities
Scope: all 5 workspace projects
Recreating /tmp/renovate/repos/github/OctopusDeploy/util-actions/node_modules
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 24, reused 0, downloaded 20, added 0
Progress: resolved 38, reused 0, downloaded 38, added 0
Progress: resolved 71, reused 0, downloaded 50, added 0
Progress: resolved 127, reused 0, downloaded 102, added 0
Progress: resolved 195, reused 0, downloaded 175, added 0
Progress: resolved 271, reused 0, downloaded 237, added 0
.                                        |  WARN  deprecated<EMAIL_ADDRESS>Progress: resolved 350, reused 0, downloaded 324, added 0
packages/add-changeset                   |  WARN  deprecated<EMAIL_ADDRESS>Progress: resolved 460, reused 0, downloaded 432, added 0
Progress: resolved 577, reused 0, downloaded 548, added 0
packages/add-changeset                   |  WARN  deprecated<EMAIL_ADDRESS>packages/add-changeset                   |  WARN  deprecated<EMAIL_ADDRESS>packages/add-changeset                   |  WARN  deprecated<EMAIL_ADDRESS>packages/add-changeset                   |  WARN  deprecated<EMAIL_ADDRESS>Progress: resolved 690, reused 0, downloaded 666, added 0
Progress: resolved 739, reused 0, downloaded 718, added 0
Progress: resolved 740, reused 0, downloaded 718, added 0
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

packages/add-changeset
└─┬ jest-runner-eslint 1.1.0
  └── ✕ missing peer eslint@"^6 || ^7 || ^8"
Peer dependencies that should be installed:
  eslint@"^6 || ^7 || ^8"

packages/extract-package-details
└─┬ jest-runner-eslint 1.1.0
  └── ✕ missing peer eslint@"^6 || ^7 || ^8"
Peer dependencies that should be installed:
  eslint@"^6 || ^7 || ^8"

packages/find-and-replace-all
└─┬ jest-runner-eslint 1.1.0
  └── ✕ missing peer eslint@"^6 || ^7 || ^8"
Peer dependencies that should be installed:
  eslint@"^6 || ^7 || ^8"

hint: If you want peer dependencies to be automatically installed, add "auto-install-peers=true" to an .npmrc file at the root of your project.
hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.

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

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: packages/add-changeset/package.json
Command failed: npm i -g<EMAIL_ADDRESS>&& pnpm install && pnpm build
npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":">=16.14"} (current: {"node":"14.18.2","npm":"6.14.15"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>


Trouble running on windows

Hi John,
I'm having some trouble running under Windows (10).
Initially, I had trouble getting NODE_ENV set, but I fixed that in package.json by adding 'set' in front of the NODE_ENV directive. Interestingly, i tried using 'cross-env', but it didn't work. Weird.
Now I'm trying to do 'npm run watch', but getting the following:

<EMAIL_ADDRESS>watch C:\xampp\htdocs\koa-notes-api
set NODE_ENV=development & nodemon app.js --exec

[nodemon] 1.12.0
[nodemon] to restart at any time, enter rs
[nodemon] watching: .
[nodemon] starting node app.js
C:\xampp\htdocs\koa-notes-api\src\index.js:3
import Koa from 'koa'
^^^^^^

SyntaxError: Unexpected token import
    at createScript (vm.js:74:10)
    ....
    at Object.<anonymous> (C:\xampp\htdocs\koa-notes-api\app.js:12:13)

I'm running node 8.x, so it shouldn't be an ES2015 thing surely?  I know this is not really your problem, but do you perhaps have any ideas I can try?

No problem. First, I would say to make sure you have the following in your package.json:
"babel": {
    "presets": [
      [
        "env",
        {
          "targets": {
            "browsers": [
              "last 2 versions",
              "safari >= 7"
            ]
          }
        }
      ]
    ]
  },

Perhaps you had deleted that by mistake. If that still doesn't work - then create a .babelrc file in your root directory, delete the above from your package.json, and add this to your newly created .babelrc file:
{
  "presets": [
    [
      "env",
      {
        "targets": {
          "browsers": [
            "last 2 versions",
            "safari >= 7"
          ]
        }
      }
    ]
  ]
}

The reason I'm having you try this is because I figure there may be a chance Windows has an issue reading the babel config from the package.json.
Now, as to why all this is needed - you actually still need babel to use import in node - even in the newer versions. No biggie - just use the babel-preset-env package like I do in this project and it handles it for you. Then, when you build the project and run the project in production with NODE_ENV=production, the app.js file with know to use the files in the generated build folder in the project with the code that's already been transpilled.

Thanks for coming back to me!
I hadn't deleted the "babel": section in packages.json, but I tried what you suggested regardless. It's still not working.
I haven't made any other changes since cloning the project. So 'package.json is the original
I also tried an npm update, after these changes, and strangely enough it produced the following, which I wasn't expecting:
+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>added 169 packages, removed 5 packages and updated 46 packages

But still no luck. I will try a few more things and get back to you.

Hmm, at that point I would delete the entire node_modules folder and npm install again just to be safe. Those updates should be fine. I'll be continuing to research as well.

Good advice, let me try it

@johndatserakis ,
Ok, I tried that, still no joy. Perhaps I can post my configs for you to have a look at?
package.json(.txt):
package.json.txt
.babelrc
{   "presets": [     [       "env",       {         "targets": {           "browsers": [             "last 2 versions",             "safari >= 7"           ]         }       }     ]   ] }
npm-packages:
npm-packages.txt
and, last, the output:

Perhaps I should just put it up in a linux VM ;D

Hmm, strange. One thing I would do is npm uninstall cross-env - as it could be fighting with the babel-present-env and thus not letting the babel-preset-env do its job.
I will say that I get the same error if I remove the babel-json information from my project - so the issue is definitely due to babel not being able to do its thing properly.

Ok, I spun it up in a linux VM, and while that problem has resolved itself... another has surfaced. I'm pretty sure this one isn't your problem, but I'd appreciate it if you could comment.  The error as follows:

I have no idea about how to tackle this one :o

Make sure you have the node version in your vm updated to a latest version. I use nvm in virtual machines if need be.

How's it going with this issue?

Hi John, I never got it sorted out under windows, but it's working great in Ubuntu (which is where it's going to live eventually anyway :) ).
A couple of things that you might want to consider adding to the docs/code (for streamlining the setup):

knex apparently needs to be installed globally in order to be able to run migrations:
$npm install -g knex

The database names in knexfile.js eg (database: process.env.DB_DATABASE + '_testing',
) doesn't have the '_dev' suffix for the development db (so it's the same as the production db name)

The users seed doesn't setup the default demousername user

Thanks for an excellent example on Vue +  koa + jwt auth !

No problem, thanks for the suggestions. I'll be updating the readme soon. I didn't intend to have the demousername/demopassword in the seeding - but that may help users in the future. And as far as the _dev suffix - that's ok (for me) if they share the same name - as they'll be using totally different connections - but perhaps that could help prevent migrating overwrites done by accident.
Thank you!


Signin with GitHub is Missing

+Signin with GitHub is Missing

Please add functionality to sign in with Github.
Newbies will get credits if the project is on Github

I could log in with GitHub but not from the first try.


python3Packages.magic-wormhole-mailbox-server: add patch for Python 3.11

Description of changes
https://github.com/NixOS/nixpkgs/pull/213680#issuecomment-1409608600
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

6 packages built:

gnome-keysign
magic-wormhole (python310Packages.magic-wormhole)
python310Packages.magic-wormhole-mailbox-server
python311Packages.magic-wormhole
python311Packages.magic-wormhole-mailbox-server
tahoe-lafs


Automatic error report

<!---   *** BEFORE SUBMITTING: PASTE CLIPBOARD HERE TO COMPLETE YOUR REPORT ***   ---!>

Hi @williambnn99 seems like you could be using a quite old Spyder version if it let you submit an empty error report. Without further information there is not much we can do, sorry :/ I would suggets you to check if you can update Spyder (latest release is Spyder 5.4.3).
Let us know if updating helps!

Closing due to lack of response


Unable to start the docker image in google cloud run

I just used the gotenberg/gotenberg:8-cloudrun image and started it:
  _____     __           __
 / ___/__  / /____ ___  / /  ___ _______ _
/ (_ / _ \/ __/ -_) _ \/ _ \/ -_) __/ _ '/
\___/\___/\__/\__/_//_/_.__/\__/_/  \_, /
                                   /___/
A Docker-powered stateless API for PDF files.
Version: 8.9.2
-------------------------------------------------------
[SYSTEM] modules: api chromium exiftool libreoffice libreoffice-api libreoffice-pdfengine logging pdfcpu pdfengines pdftk prometheus qpdf webhook
[SYSTEM] chromium: Chromium ready to start
[SYSTEM] libreoffice-api: LibreOffice ready to start
[SYSTEM] prometheus: collecting metrics
[SYSTEM] pdfengines: exiftool libreoffice-pdfengine pdfcpu pdftk qpdf
[SYSTEM] api: server listening on port 3000
Default STARTUP TCP probe failed 1 time consecutively for container "gotenberg-1" on port 8080. The instance was not started.

Listening for requests on the correct port (services):

By default, requests are sent to 8080, but you can configure Cloud Run to send requests to the port of your choice. Cloud Run injects the PORT environment variable into the ingress container.

I would recommend to listen to the PORT environment variable by default.

You may setup this behavior with the flag --api-port-from-env=PORT.
But you're right, it's not clear in the documentation and I may setup default flags.

Thanks for the update.
Using following command i was able to boot up the instance:
gcloud run deploy gotenberg-prod
--image=gotenberg/gotenberg:8-cloudrun
--args=gotenberg
--args="--api-port-from-env=PORT"

If --args=gotenberg is not provided i will run into
[FATAL tini (2)] exec --api-port-from-env=PORT failed: No such file or directory

@gulien If you update the documentation I would suggest to use --memory=1Gi for a better experience, because the default is 512Mi, which caused some issues.
Here the metric of our service running in production:

I was running with default first, then I ran into memory issues.
I increased it to 1Gi since then the memory usage is 55% on average, sometimes peaks to 60%.
And thank you for this smooth plug and play experience. We replaced a chrome headless using CDP with gotenberg, and it runs so smooth

Thanks for the heads up @Fank! The 512 Mo requirement seems to really depend on the type of infrastructure. I'll add it to the documentation 👍

And thank you for this smooth plug and play experience. We replaced a chrome headless using CDP with gotenberg, and it runs so smooth

Glad you appreciate, and thanks for the feedback! Most often than not, I have no idea how users are experiencing with Gotenberg 😄

@Fank I have improved the documentation regarding Cloud Run based on your feedbacks 😉
I think its best to let the users add the flags themselves instead of putting default flags in the image. It's less magic, but it eases the process of adding more flags if needed (e.g., not overriding default ones with the risk that their containers do not work anymore).